Link to USB adapters
08-22-2013, 07:37 PM
#42
Newb
Join Date: Dec 2011
Posts: 37
Total Cats: 0
I have a 1992 1.6 turbo car with the LINK from flyin miata. I only have the handheld device, not the "data cable" or whatever they called it.
Is this what I need to start data logging and tuning using a pc?
If so I would like one please!
Is this what I need to start data logging and tuning using a pc?
If so I would like one please!
Reply
0
0
09-25-2013, 03:30 PM
#52
i will advise that if you cna get your hands on a laptop that has a serial port, do.
being a network administrator and having to console into devices i gotta say.. **** USB ADAPTERS.
unreliable pieces of ****.
when the company went from dell D630's and D830's i kept like 3 laptops...
the new laptops don't have serial ports.
they still think i'm stupid..until they try a usb adapter..then they come begging for my laptop.
again, D630's should be going for about 100 bucks
they are dual core and very capable of running windows7 and even better when XP is running....
being a network administrator and having to console into devices i gotta say.. **** USB ADAPTERS.
unreliable pieces of ****.
when the company went from dell D630's and D830's i kept like 3 laptops...
the new laptops don't have serial ports.
they still think i'm stupid..until they try a usb adapter..then they come begging for my laptop.
again, D630's should be going for about 100 bucks
they are dual core and very capable of running windows7 and even better when XP is running....
Reply
0
0
09-25-2013, 04:59 PM
#53
Elite Member
Thread Starter
iTrader: (10)
Join Date: Oct 2008
Location: Rhode Island
Posts: 1,770
Total Cats: 31
i will advise that if you cna get your hands on a laptop that has a serial port, do.
being a network administrator and having to console into devices i gotta say.. **** USB ADAPTERS.
unreliable pieces of ****.
when the company went from dell D630's and D830's i kept like 3 laptops...
the new laptops don't have serial ports.
they still think i'm stupid..until they try a usb adapter..then they come begging for my laptop.
again, D630's should be going for about 100 bucks
they are dual core and very capable of running windows7 and even better when XP is running....
being a network administrator and having to console into devices i gotta say.. **** USB ADAPTERS.
unreliable pieces of ****.
when the company went from dell D630's and D830's i kept like 3 laptops...
the new laptops don't have serial ports.
they still think i'm stupid..until they try a usb adapter..then they come begging for my laptop.
again, D630's should be going for about 100 bucks
they are dual core and very capable of running windows7 and even better when XP is running....
Now, having said that, the device at my day job (speaking over ftdi usb->serial) communicates at ~1mbit with 0 drop out. And the protocol is a fuckton more complicated than any serial terminal
The failures I've seen with USB->Serial adapters on Windows have stemmed from the serial communication layer of the software relying on win32 events and the FTDI driver playing nicely together (they don't) which caused random errors manifesting themselves in the form of several bits in a given packet (usually in the last byte or two) being corrupted. This mode of failure is also present with USB audio devices, leading me to believe that the windows USB stack is beyond fucked (USB audio operates via isochronous endpoints, which require timed events). We overcame this issue by simply not using the win32 event mechanism and writing our software accordingly.
TL;DR: If you set it up properly, it'll work properly.
Reply
0
0
09-25-2013, 08:57 PM
#55
in other words..
unless someone like you who know about drivers sets it up correctly, the rest
of us humble windows users are fucked.
lol
but i see what you did there...
unless someone like you who know about drivers sets it up correctly, the rest
of us humble windows users are fucked.
lol
but i see what you did there...
As someone who writes device drivers and designs products (at my day job) which ship with an FTDI on the board, I will admit that they have their quirks. Since they act as an intermediary and buffer the traffic, incorrect settings can absolutely **** all over your good times if the software you're using was written to use some shitty windows specific features. FTDI generally allows you to modify both the internal buffer maximum and minimum latency settings which affect how the device driver (and by extension, the software using it) will react to IO events. (I've found that setting latency timer to 1ms, buffer size to 4k and using 0 as a minimum latency is a pretty good fit for 115200 <= baudrate <= 921600)
Now, having said that, the device at my day job (speaking over ftdi usb->serial) communicates at ~1mbit with 0 drop out. And the protocol is a fuckton more complicated than any serial terminal
The failures I've seen with USB->Serial adapters on Windows have stemmed from the serial communication layer of the software relying on win32 events and the FTDI driver playing nicely together (they don't) which caused random errors manifesting themselves in the form of several bits in a given packet (usually in the last byte or two) being corrupted. This mode of failure is also present with USB audio devices, leading me to believe that the windows USB stack is beyond fucked (USB audio operates via isochronous endpoints, which require timed events). We overcame this issue by simply not using the win32 event mechanism and writing our software accordingly.
TL;DR: If you set it up properly, it'll work properly.
Now, having said that, the device at my day job (speaking over ftdi usb->serial) communicates at ~1mbit with 0 drop out. And the protocol is a fuckton more complicated than any serial terminal
The failures I've seen with USB->Serial adapters on Windows have stemmed from the serial communication layer of the software relying on win32 events and the FTDI driver playing nicely together (they don't) which caused random errors manifesting themselves in the form of several bits in a given packet (usually in the last byte or two) being corrupted. This mode of failure is also present with USB audio devices, leading me to believe that the windows USB stack is beyond fucked (USB audio operates via isochronous endpoints, which require timed events). We overcame this issue by simply not using the win32 event mechanism and writing our software accordingly.
TL;DR: If you set it up properly, it'll work properly.
Reply
0
0
