??? 05/17/07 16:57 Read: times |
#139450 - supply them Responding to: ???'s previous message |
Andrew Ayre said:
The drivers supplied with these cables make the cable look exactly like a COM port in windows, therefore all the same functions for COM ports are available. If you can't read something from a COM port then I don't think you can read it from a virtual COM port. I'll do some digging to see if the driver could be queried directly. Well, I suspected something similar. As I said, I am no Win expert (and for a user, a bad one, too). But, couldn't you interrogate the system on which USB devices are plugged in, and guess somehow the connection between them and the virtual COM? Andy Ayre said:
However I think it's only really useful to do this if in the end we can tell people exactly what to buy. After all you can't go to the store and start opening the cases to examine the devices. In most of the places I would buy such "cables", they would let me try it first. I don't say this is the case everywhere. --- There IS a definitive solution to the problem. Or at least sort of. Build a cable based on the FTDI chip and sell it. I've never heard anything wrong about the FTDI-based solutions. The trouble is, you cannot get nowhere near the "fast eastern" price. It's not wonder most of the cheap "cables" ARE based on the Prolific chip (not that there are many producers of such chips). JW |
Topic | Author | Date |
Program AT89S52 using usb port? | 01/01/70 00:00 | |
using a programmer... | 01/01/70 00:00 | |
WRONG! and a note to Andy | 01/01/70 00:00 | |
Maybe, but... | 01/01/70 00:00 | |
the key word | 01/01/70 00:00 | |
Tuning of Flash Magic | 01/01/70 00:00 | |
not quite | 01/01/70 00:00 | |
nondefinitive conclusions | 01/01/70 00:00 | |
Thanks | 01/01/70 00:00 | |
collecting data? | 01/01/70 00:00 | |
Data | 01/01/70 00:00 | |
supply them![]() | 01/01/70 00:00 | |
It is already here | 01/01/70 00:00 |