Has the behavior of the runaway TX watchdog timer intentionally changed in 1.5.0-rc1? (Or, I perhaps what I really want to ask is what resets the timer now?)
With the 1.4 series I could call CQ 3 or 4 times without the watchdog timer firing. With 1.5.0-rc1, it *occasionally* hits me after 2 or even 1 CQ. I haven't been able to figure out what causes the different behavior to make a proper bug report. But for what its worth just now, I called CQ a couple of times unsuccessfully on JT65... went off and did something else for 15 minutes, came back and tried calling CQ in JT9 and the watchdog disabled TX after the first CQ. 0550 Tx 776 # CQ 7J1AJH PM95 0552 Tx 776 # CQ 7J1AJH PM95 0554 Tx 776 # CQ 7J1AJH PM95 (manually disabled) 0627 Tx 799 # CQ 7J1AJH PM95 0629 Tx 799 # CQ 7J1AJH PM95 (manually disabled) 0644 Tx 2610 @ CQ 7J1AJH PM95 (runaway watchdog fired) Jim -- Jim Tittsler 7J1AJH/ZL2IA/AI8A Tokyo GPG: 0x01159DB6 http://OnJapan.net/ham/ QRP/Satellites/APRS AMSAT-NA/AMSAT-ZL/NZART ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
