Re: [chirp_users] chirp_users Digest, Vol 117, Issue 16
Indeed, so why are we indirectly promoting the use of counterfeit devices then?
If the chip is "Genuine", the currently available "Official" driver, /will/ work.
Yes, I too have accumulated some dodgy chip driven adapters, just as everyone I suspect has. I am slowly replacing them as I find them, not because they don't work (they work just fine under Linux, for now.) But because they all have the same identity and no serial number, making the use of multiple devices and nailing their feet to the numeric floor with Udev rules, rather troublesome.
I prefer FTDI parts, as by default they all have a unique serial number, making Udev rules easy and reliable.
SiLabs parts are a close second choice*, with Prolific only if there is absolutely no other alternative. Even the genuine Prolific chips don't seem to have a "unique" identity. (Unless I've not yet seen a "Genuine" chip!)
General Linux trick: What I've found is that if you build a Udev table for regularly connected devices, starting from /dev/ttyUSB1 (or higher) then anything else that is randomly connected later, will always show up as ttyUSB0 or 2 etc, as they is still vacant.
End.
73.
Dave G0WBX.
On 23/09/18 20:00, chirp_users-request@intrepid.danplanet.com wrote:
I don't think you will find the older v3.2.0.0 driver available for download on the Prolific site.
I think the problem is that folks have paid good money for these cables, so expect them to just work. I'm fairly certain that if vendors were flying the Jolly Roger then most here would find another vendor. And getting rid of dodgy cables only because they don't play well with Linux doesn't directly promote the use of only genuine devices!
V/R
(Peter)
On 9/24/2018 12:55 AM, Dave B via chirp_users wrote:
Indeed, so why are we indirectly promoting the use of counterfeit devices then?
If the chip is "Genuine", the currently available "Official" driver, /will/ work.
Yes, I too have accumulated some dodgy chip driven adapters, just as everyone I suspect has. I am slowly replacing them as I find them, not because they don't work (they work just fine under Linux, for now.) But because they all have the same identity and no serial number, making the use of multiple devices and nailing their feet to the numeric floor with Udev rules, rather troublesome.
[...]
On 23/09/18 20:00, chirp_users-request@intrepid.danplanet.com wrote:
I don't think you will find the older v3.2.0.0 driver available for download on the Prolific site.
They do play well with Linux. They don't play well with Microsoft and Apple.
On 24 September 2018 at 04:05 Peter ptlambert@sbcglobal.net wrote:
. And
getting rid of dodgy cables only because they don't play well with Linux doesn't directly promote the use of only genuine devices!
.
On 09/24/2018 02:55 AM, Dave B via chirp_users wrote:
Indeed, so why are we indirectly promoting the use of counterfeit devices then?
If the chip is "Genuine", the currently available "Official" driver, /will/ work.
Actually not true. Documented on Prolific site. There are certain genuine chips that they have elected to not support in Windows 10. Yet the old drivers work (not documented by them). I have been bitten by this in the past.
Yes, I too have accumulated some dodgy chip driven adapters, just as everyone I suspect has. I am slowly replacing them as I find them, not because they don't work (they work just fine under Linux, for now.) But because they all have the same identity and no serial number, making the use of multiple devices and nailing their feet to the numeric floor with Udev rules, rather troublesome.
I prefer FTDI parts, as by default they all have a unique serial number, making Udev rules easy and reliable.
SiLabs parts are a close second choice*, with Prolific only if there is absolutely no other alternative. Even the genuine Prolific chips don't seem to have a "unique" identity. (Unless I've not yet seen a "Genuine" chip!)
General Linux trick: What I've found is that if you build a Udev table for regularly connected devices, starting from /dev/ttyUSB1 (or higher) then anything else that is randomly connected later, will always show up as ttyUSB0 or 2 etc, as they is still vacant.
End.
Dave G0WBX.
On 23/09/18 20:00, chirp_users-request@intrepid.danplanet.com wrote:
I don't think you will find the older v3.2.0.0 driver available for download on the Prolific site.
-- Created on and sent from a Unix like PC running and using free and open source software. ::
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Paul AC0HY at ac0hy@wpmills.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
participants (4)
-
Dave B -
Nigel A. Gunn G8IFF/W8IFF -
Peter -
W Paul Mills