Hi all, I ran into an unfortunate incident a few days back while band-hopping WSPR (RX only). I came home to find my rig had locked up and was no longer responding to CAT control, and WSJTX of course had the popup asking if I wanted to reconfigure. It had continued decoding while the rig wasn't responding which is fine. But it had reported each of those decodes as belonging to the band it was trying to switch to -- even though it didn't succeed at switching. This of course resulted in a bunch of bogus reports, including some impressive 6 meter "DX".
What do you think is the best solution here: stop reporting when there's a rig error? Or keep track of the last successful CAT frequency independent of what the desired frequency is and report using that? I'm leaning towards the former, i.e. a band change sequence would be "disable reporting -> change frequency -> confirm change -> enable reporting". I'm willing to work on a patch but wanted some initial feedback before I dove in. -- mike NF4E ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
