Re: [chirp_users] Hesenate vhf/uhf
It probably uses a fake Prolific chipset, all too common sadly.
Windows will not use those now, unless you roll back the driver, but then Windows will "update" it to the latest again at the next opportunity. If you turn Windows updates off, then you are potentially vulnerable for other troubles as they are found later.
They still work OK on most Linux's though, as does Chirp just fine.
Solution, use a FTDI based cable (if you can find a seller to guarantee that they are genuine too) or build your own cable with a known genuine USB<>Serial chip. The "Genuine" Prolific chips are OK in Windows.
Silicon Lab's chips are OK too, but you'll have to install drivers yourself for them, except on Linux, where they "just work" without issue on most distro's.
Note: The "Fake" chips, are actually micro-controllers programmed to emulate Prolific or FTDI chips. The emulations are quite good, but can be detected by the "official" drivers. The current official Prolific drivers will not use the Fakes. Similarly, FTDI drivers will not use the fakes either. Earlier FTDI drivers would "brick" them by resetting the VID/PID values to zero. Caused a lot of bad press that did. (But they can be un-bricked!)
The fake FDTI chips can be identified as being unable to re-assign the auxiliary I/O pin functions. Well, the software is happy, but the change doesn’t actually happen. That's how I found one, I needed to invert the TXD line, but no change happened.
I have also personally come across a chip that was marked up as FTDI, but identified itself to the PC as Prolific! I suspect there are undocumented ways to "configure" the emulation.
Take care.
73.
Dave G0WBX.
On 28/11/17 20:00, chirp_users-request@intrepid.danplanet.com wrote:
Subject: Re: [chirp_users] Hesenate vhf/uhf To: chirp_users@intrepid.danplanet.com Message-ID: 15fff22b39a-171e-13cb3@webjas-vaa246.srv.aolmail.net Content-Type: text/plain; charset="utf-8"
shows error under other devices usb port no drivers available. I will have to find a driver for the cable. Ray
updating cab be avoided
2017-11-29 11:04 GMT+02:00 Dave B g8kbv@uku.co.uk:
It probably uses a fake Prolific chipset, all too common sadly.
Windows will not use those now, unless you roll back the driver, but then Windows will "update" it to the latest again at the next opportunity. If you turn Windows updates off, then you are potentially vulnerable for other troubles as they are found later.
They still work OK on most Linux's though, as does Chirp just fine.
Solution, use a FTDI based cable (if you can find a seller to guarantee that they are genuine too) or build your own cable with a known genuine USB<>Serial chip. The "Genuine" Prolific chips are OK in Windows.
Silicon Lab's chips are OK too, but you'll have to install drivers yourself for them, except on Linux, where they "just work" without issue on most distro's.
Note: The "Fake" chips, are actually micro-controllers programmed to emulate Prolific or FTDI chips. The emulations are quite good, but can be detected by the "official" drivers. The current official Prolific drivers will not use the Fakes. Similarly, FTDI drivers will not use the fakes either. Earlier FTDI drivers would "brick" them by resetting the VID/PID values to zero. Caused a lot of bad press that did. (But they can be un-bricked!)
The fake FDTI chips can be identified as being unable to re-assign the auxiliary I/O pin functions. Well, the software is happy, but the change doesn’t actually happen. That's how I found one, I needed to invert the TXD line, but no change happened.
I have also personally come across a chip that was marked up as FTDI, but identified itself to the PC as Prolific! I suspect there are undocumented ways to "configure" the emulation.
Take care.
Dave G0WBX.
On 28/11/17 20:00, chirp_users-request@intrepid.danplanet.com wrote:
Subject: Re: [chirp_users] Hesenate vhf/uhf To: chirp_users@intrepid.danplanet.com Message-ID: 15fff22b39a-171e-13cb3@webjas-vaa246.srv.aolmail.net 15fff22b39a-171e-13cb3@webjas-vaa246.srv.aolmail.net Content-Type: text/plain; charset="utf-8"
shows error under other devices usb port no drivers available. I will have to find a driver for the cable. Ray
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to amnon at amnon.zohar@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
Thanks Amnon for your help. I got my problem resolved by going to Baofeng and downloading a driver for the genuine Baofeng PC03 cable I had bought. The driver matched the chipset in the cable. I was now able to get into the CHRIP program and setup for a Boafeng radio UV-5R. It is working fine. Thanks Ray W3EGG
-----Original Message----- From: Amnon Zohar amnon.zohar@gmail.com To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Wed, Nov 29, 2017 4:24 am Subject: Re: [chirp_users] Hesenate vhf/uhf
updating cab be avoided
2017-11-29 11:04 GMT+02:00 Dave B g8kbv@uku.co.uk:
It probably uses a fake Prolific chipset, all too common sadly.
Windows will not use those now, unless you roll back the driver, but then Windows will "update" it to the latest again at the next opportunity. If you turn Windows updates off, then you are potentially vulnerable for other troubles as they are found later.
They still work OK on most Linux's though, as does Chirp just fine.
Solution, use a FTDI based cable (if you can find a seller to guarantee that they are genuine too) or build your own cable with a known genuine USB<>Serial chip. The "Genuine" Prolific chips are OK in Windows.
Silicon Lab's chips are OK too, but you'll have to install drivers yourself for them, except on Linux, where they "just work" without issue on most distro's.
Note: The "Fake" chips, are actually micro-controllers programmed to emulate Prolific or FTDI chips. The emulations are quite good, but can be detected by the "official" drivers. The current official Prolific drivers will not use the Fakes. Similarly, FTDI drivers will not use the fakes either. Earlier FTDI drivers would "brick" them by resetting the VID/PID values to zero. Caused a lot of bad press that did. (But they can be un-bricked!)
The fake FDTI chips can be identified as being unable to re-assign the auxiliary I/O pin functions. Well, the software is happy, but the change doesn’t actually happen. That's how I found one, I needed to invert the TXD line, but no change happened.
I have also personally come across a chip that was marked up as FTDI, but identified itself to the PC as Prolific! I suspect there are undocumented ways to "configure" the emulation.
Take care.
73.
Dave G0WBX.
On 28/11/17 20:00, chirp_users-request@intrepid.danplanet.com wrote:
Subject: Re: [chirp_users] Hesenate vhf/uhf To: chirp_users@intrepid.danplanet.com Message-ID: 15fff22b39a-171e-13cb3@webjas-vaa246.srv.aolmail.net Content-Type: text/plain; charset="utf-8"
shows error under other devices usb port no drivers available. I will have to find a driver for the cable. Ray
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to amnon at amnon.zohar@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
participants (3)
-
Amnon Zohar -
Dave B -
Ray Nicholson