I used Keyspan - Tripplite converters, with Coastal Explorer under Win7, for a while. At some point, however, they just didn't get the job done. It's a pity, as they were good when they were Keyspan products. Gotta wonder if Tripplite "improved" things.
73 de KC3DOO Rick
On 8/29/2016 4:10 PM, Jim McCorison wrote:
For years I have used the Keyspan (now Tripplite) USA-19HS serial to USB adapter. It has always worked no matter the operating system or software being used. I have customers (I’m in the marine electronics business) who have bought cheapy knockoffs and can’t get their pc integration to work properly. I sell them a USA-19HS and without any other changes, other than the proper driver install, everything works just fine. While it is more expensive than a $5 Chinese clone, how much do you value your time and peace of mind. Is it really worth the frustration with something that is supposed to be an enjoyment just to save a few dollars?
73s, Jim K2SON
Jim McCorison Orcas Island, WA
On Aug 28, 2016, at 11:11 AM, Pavel Milanes (CO7WT) <pavelmc@gmail.com mailto:pavelmc@gmail.com> wrote:
Yes, I agree.
I recently upgraded my desktop PC board to a Corei5 Asus with zero serial ports, I have tested two usb-serial adapters (linux OS here) with no joy.
One ark and the other ch340 chipset, the ch340 work so so, but some radios does not work with it, the ark is a waste of time, it has only rx/tx and It get stuck easily.
I am looking desperately for a ftdi adapter here un Cuba.
73 Pavel CO7WT
El 27 de agosto de 2016 7:42:45 PM GMT-04:00, "Richard B. Emerson" <pavilion@pinefields.com mailto:pavilion@pinefields.com> escribió:
Following the traffic here, I think the following should be (if it isn't) a FAQ item. Nonetheless it bears repeating here:
FTDI conversion chips and drivers are extremely stable. Anything else, including Prolific, is a gamble with poor odds. It's that simple.
Background: On our sailboat, I do a number of serial/USB conversions. This converts (admittedly ancient) NMEA 183 serial data from instrumentation for a USB port on a laptop running a navigation program
(Coastal Explorer - don't leave port without it). Initially I used Prolific-based convertes (what did I know?). Simply put, it became one non-stop headache. Data wouldn't come through, drivers stopped functioning, etc., etc. I switched to an FTDI-based 10-port serial/USB converter. The only changes to the system was to plug the DB-9 pigtails
into the new converter and load the FTDI driver. End of problems, no crashes, full functionality. To clarify, one port services the full NMEA 183 data stream from the autopilot computer (speed through the water, depth, wind direction and speed, full GPS data stream [position, speed over the bottom, direction, GPS status, time of day)) and the port sends steering information to the autopilot, waypoint location data, and more. Another port sends data to the VHF and SSB radios (position, time of day) and receives data from the VHF (Digital Selective Calling data including emergency data received). Another port sends position, time of day, waypoint location data and receives target data from the radar including Modified Automatic Radar Plotting Aid data. The last active port receives data from the Automatic Identification System and an auxiliary GPS receiver (part of the AIS system). (full translation of "NMEA 183", "waypoint", etc. available off-list)
This is a long and probably very boring summary of what goes through FTDI devices at a mix of data rates (4800 baud for all but the AIS, which works at 38400 baud). If the FTDI part fails, life gets ugly fast
(yes, there are backups). I bet a lot on FTDI and have no cause to regret it. Prolific devices were... my wife wore earplugs when the converters failed.
Again, FTDI good - not FTDI bad.
73 de KC3DOO Rick
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to M.Sc. Pavel Milanes Costa atpavelmc@gmail.com mailto:pavelmc@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
-- Sent from my Android smartphone, please forgive the typos. Enviado desde mi cell Android, disculpe los errores de escritura. _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to K2SON atjimmcc@mccorison.com mailto:jimmcc@mccorison.com To unsubscribe, send an email tochirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to KC3DOO at pavilion@pinefields.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com