search for: cm11a

...; got no reasonable response from the devices. > > Jim > The cure Jim, is eliminate the prolific by replacing it with a FTDI dongle. Prolific has a bug in its wakeup, throwing away the first byte rx'd. I threw mine into the out bin 2 decades ago. Was trying to use it to talk to a cm11a for a heyu interface. Failed miserably. Encourage owners to toss it and get the FTDI-usb<->serial which Just Works. > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-...

...e from the devices. >> >> Jim >> > The cure Jim, is eliminate the prolific by replacing it with a FTDI > dongle. Prolific has a bug in its wakeup, throwing away the first byte > rx'd. I threw mine into the out bin 2 decades ago. Was trying to use it > to talk to a cm11a for a heyu interface. Failed miserably. Encourage > owners to toss it and get the FTDI-usb<->serial which Just Works. THAT would explain a LOT of past issues with trying to use a Microsoft DeLorme GPS receiver as a stratum-1 time source. Unfortunately since the Prolific chip was bui...

Got a community question at https://github.com/networkupstools/nut/issues/2466 with at least two users (and UPSes) in trouble. Curiously, they identify as 067b:2303 Prolific Technology like a common USB-Serial dongle brand. Experiments with blazer and nutdrv-qx got no reasonable response from the devices. Jim -------------- next part -------------- An HTML attachment was scrubbed... URL:

Got a community question at https://github.com/networkupstools/nut/issues/2466 with at least two users (and UPSes) in trouble. Curiously, they identify as 067b:2303 Prolific Technology like a common USB-Serial dongle brand. Experiments with blazer and nutdrv-qx got no reasonable response from the devices. Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: