Thank you, Wayne. Changing the retry interval from 50ms to 250ms seems to fix the problem I encountered, which in more detail was this: When an unrelated program strobes the RS232 ports (looking for compatible devices) it gets the K3 out of sync. With the longer retry delay it gets back in sync with the rig control command stream.
Should I default the update the fldigi rigcat defaults for the K3 to 250ms retry, 10 retries, 100ms write delay? We're presently shipping 50ms timeout, 5ms write delay, 2 retries with fldigi rigcat control. Leigh/WA5ZNU -- View this message in context: http://elecraft.365791.n2.nabble.com/K3-MCU-4-47-serial-recovery-tp7235321p7235356.html Sent from the Elecraft mailing list archive at Nabble.com. ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
