In that case it's probably statistically slightly more likely that a CAT command (seems like about 5 bytes) would get garbled going across the USB than whatever bit stream went across the USB to turn RTS off. One would be an op-code (probably 8 bits) plus 5 more bytes, versus the other being just an op code. So it's odds of garbling 1 or more bits out of 8 versus 1 or more bits out of ~48. Probably mitigates the problem somewhat, but mostly likely won't make it completely go away.
The best thing still will be attenuating the common mode noise on the USB cable, IMO... keep it out of there in the first place. Nick On 12 January 2017 at 10:41, Don Wilhelm <donw...@embarqmail.com> wrote: > Nick, > > Yes, the K3S connects directly to USB, but inside the K3S is an FTDI USB > to serial converter. It has the RTS and DTR signals and they are properly > routed to the K3S. The RS-232 circuits in the K3S are retained just like > as they were with the K3. > > 73, > Don W3FPR > > On 1/12/2017 1:15 PM, Nicklas Johnson wrote: > >> Unless I'm mistaken, doesn't the K3S connect directly via USB though? If >> the problem is happening because of common mode on the USB cable, there is >> no physical RTS line involved like there would be in an old-style >> COM/RS232 >> device >> > -- *N6OL* Saying something doesn't make it true. Belief in something doesn't make it real. And if you have to lie to support a position, that position is not worth supporting. ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
