[chirp_users] FTDI good - not FTDI bad
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
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 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 http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to M.Sc. Pavel Milanes Costa at pavelmc@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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 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 http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to M.Sc. Pavel Milanes Costa at pavelmc@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 http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to K2SON at jimmcc@mccorison.com mailto:jimmcc@mccorison.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
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
I use my usb to serial adapter to connect to and program Fire alarm panels. I picked up a fantastic adapter recently, works with everything. It's from usconverters.com
-----Original Message----- From: "Richard B. Emerson" pavilion@pinefields.com To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Mon, 29 Aug 2016 15:53 Subject: Re: [chirp_users] FTDI good - not FTDI bad
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
On 8/27/16 7:42 PM, Richard B. Emerson wrote:
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.
This is true for Windows, and for OSX - for the most part. I've had wacky behavior and performance with the knock-off Prolific things on OSX.
However crappy the Prolific chips are, they seem to work just fine with all of the different Linux distributions I've tried. Simply plug them in, and they work. For this reason, I usually buy the Prolific $1.40 knock-off usb/serial dongles from EBay.
I simply can't get the Prolific cable to work with my new Btech uv-2501. I've tried all the drvrs from the old 2007 drvr recommended on the Miklor site to the very latest one from Prolific's site. Both of them satisfy my Windows 7 (no yellow flag). But they all give the "failed to enter clone mode" error. So, I've ordered a FTDI cable and have crossed fingers that there isn't actually some problem with the transceiver.
On 8/29/2016 12:01 PM, Drew from Zhrodague wrote:
On 8/27/16 7:42 PM, Richard B. Emerson wrote:
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.
This is true for Windows, and for OSX - for the most part. I've had wacky behavior and performance with the knock-off Prolific things on OSX.
However crappy the Prolific chips are, they seem to work just fine with all of the different Linux distributions I've tried. Simply plug them in, and they work. For this reason, I usually buy the Prolific $1.40 knock-off usb/serial dongles from EBay. _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to john at parrotdise13@att.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
While I've spent some time with Linux (mostly SuSE and some Red Hat), I've never tried serial/USB converters at all. However, based on zero experience with the application, I'll take a guess and say it may be the Linux drivers are more "cooperative". In fact, do you know if you loaded drivers that came with the cable or relied on native Linux drivers? My point being that perhaps the Prolific drivers are as much to blame as anything. The logical conclusion is to build a Linux machine to support CHIRP and Prolific cables - talk about reinventing the Zippo to light a campfire...
73 de KC3DOO Rick
On 8/29/2016 1:01 PM, Drew from Zhrodague wrote:
On 8/27/16 7:42 PM, Richard B. Emerson wrote:
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.
This is true for Windows, and for OSX - for the most part. I've had wacky behavior and performance with the knock-off Prolific things on OSX.
However crappy the Prolific chips are, they seem to work just fine with all of the different Linux distributions I've tried. Simply plug them in, and they work. For this reason, I usually buy the Prolific $1.40 knock-off usb/serial dongles from EBay. _______________________________________________ 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
On Mon, 29 Aug 2016 14:05:58 -0400 "Richard B. Emerson" pavilion@pinefields.com wrote:
While I've spent some time with Linux (mostly SuSE and some Red Hat), I've never tried serial/USB converters at all. However, based on zero experience with the application, I'll take a guess and say it may be the Linux drivers are more "cooperative". In fact, do you know if you loaded drivers that came with the cable or relied on native Linux drivers? My point being that perhaps the Prolific drivers are as much to blame as anything. The logical conclusion is to build a Linux machine to support CHIRP and Prolific cables - talk about reinventing the Zippo to light a campfire...
73 de KC3DOO Rick
For me, using both Fedora and Linux Mint (Ubuntu), the serial/USB converters I have just work. Plug n play. No brand info on either, one came from Amazon, one from Best Buy. That was on a Kenwood & Yaesu. My Baofeng & Icom both have direct to USB cables which just work also, Did have to whittle down the end of the Baofeng connector to get to seat correctly.
I also have tried the linux live iso file with chirp installed which makes a bootable cd, or with a bit more work, a bootable thumb drive for use on Windows.
Fred
On 8/29/16 2:05 PM, Richard B. Emerson wrote:
While I've spent some time with Linux (mostly SuSE and some Red Hat), I've never tried serial/USB converters at all. However, based on zero experience with the application, I'll take a guess and say it may be the Linux drivers are more "cooperative". In fact, do you know if you loaded drivers that came with the cable or relied on native Linux drivers? My point being that perhaps the Prolific drivers are as much to blame as anything. The logical conclusion is to build a Linux machine to support CHIRP and Prolific cables - talk about reinventing the Zippo to light a campfire...
It's actually the drivers written by Prolific which detect a genuine or knock-off Prolific chip, and will either work or not work depending on that. Prolific wants to make sure only their chips work with their driver. The solution is to install an older Prolific driver version, and then prevent Windows from updating it to the latest version.
Linux developers want their stuff to work, so they make sure that it does. The pl2303 driver for linux doesn't do any checking on the authenticity of the usb/serial chips, as far as I understand.
Also, I didn't have to install any kind of driver for Linux, with the exception of OpenWRT, which needs the kmod-pl2303 package installed before it will work.
I've tested a few sub-generic pl2303 knock-offs with TinyCore, CentOS, Fedora, OpenWRT, and Ubuntu. I do not use Windows.
(Really happy about hearing we have IC-7100 support, and can't wait to try CHIRP tonite with ubuntu on this thin-client I've been using as a radio-workstation)
This is what a Raspberry Pi is for! I have one with Chirp just to reconfigure various HT's that I own. Steve kb1chu
On 08/29/2016 02:05 PM, Richard B. Emerson wrote:
The logical conclusion is to build a Linux machine to support CHIRP and Prolific cables - talk about reinventing the Zippo to light a campfire...
73 de KC3DOO Rick
The logical choice is to do this: Build a Progr Cable - Miklor | | | | | | | | | | | Build a Progr Cable - MiklorBuild a Progr Cable - Miklor | | | | View on www.miklor.com | Preview by Yahoo | | | | |
Get aCP2102 USB to TTL UART chip.VERY cheap $2 ish device and install it to your cable. NEVER worry about any driver again.
From: Stephen Black via chirp_users chirp_users@intrepid.danplanet.com To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Monday, August 29, 2016 3:17 PM Subject: Re: [chirp_users] FTDI good - not FTDI bad
This is what a Raspberry Pi is for! I have one with Chirp just to reconfigure various HT's that I own. Steve kb1chu
On 08/29/2016 02:05 PM, Richard B. Emerson wrote:
The logical conclusion is to build a Linux machine to support CHIRP and Prolific cables - talk about reinventing the Zippo to light a campfire...
73 de KC3DOO Rick
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to KD8DVR at jl_wilkerson@att.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
participants (9)
-
David Buss -
Drew from Zhrodague -
Fred -
Jim McCorison -
John Bryant -
John W. -
Pavel Milanes (CO7WT) -
Richard B. Emerson -
Stephen Black