? - SDRC not tracking EXT-Radio with Crash Bug ?
Posted: Tue Jan 11, 2022 7:37 pm
Greetings
Simon Brown has been graciously trying to help me locate the cause of this crashing problem :
Configuration-A was experiencing occasional crashes, but also occasional smooth operation. Simon instructed that this configuration was not intended, and to use Conf-B instead.
After switching to Configuration-B, all worked ok for a few days, then the SDRC Main VFO began failing to track all other VFOs :
WSJT-X, EXT-Radio, & FT817, all tracking together, but not SDRC Main VFO.
Environment :
WIN10, i7-4790
SDRC v3.1 (and all betas since 3AUG, and 3.0.26) + EXT-Radio
+ WSJT-X 2.5.2
+ Yaesu FT817
Configuration-A :
1) EXT-Radio connected to FT817 via Omnirig by USB-Serial adapter
2) WSJT-X communicating with SDRC via Omnirig1 (as radio entry)
Configuration-B :
1) EXT-Radio connected to FT817 via Omnirig by USB-Serial adapter
2) WSJT-X communicating with SDRC via TS2000 emulation (as WSJT-X radio entry) by com0com virtual serial ports
The Conf-B 'non-tracking' issue coincidentally began sometime after the 10JAN22 WIN10 Automatic Update.
We're still sorting through this. If anyone is seeing something similar please reply here.
Thanks & 73
Paul
N8CVW
Simon Brown has been graciously trying to help me locate the cause of this crashing problem :
Configuration-A was experiencing occasional crashes, but also occasional smooth operation. Simon instructed that this configuration was not intended, and to use Conf-B instead.
After switching to Configuration-B, all worked ok for a few days, then the SDRC Main VFO began failing to track all other VFOs :
WSJT-X, EXT-Radio, & FT817, all tracking together, but not SDRC Main VFO.
Environment :
WIN10, i7-4790
SDRC v3.1 (and all betas since 3AUG, and 3.0.26) + EXT-Radio
+ WSJT-X 2.5.2
+ Yaesu FT817
Configuration-A :
1) EXT-Radio connected to FT817 via Omnirig by USB-Serial adapter
2) WSJT-X communicating with SDRC via Omnirig1 (as radio entry)
Configuration-B :
1) EXT-Radio connected to FT817 via Omnirig by USB-Serial adapter
2) WSJT-X communicating with SDRC via TS2000 emulation (as WSJT-X radio entry) by com0com virtual serial ports
The Conf-B 'non-tracking' issue coincidentally began sometime after the 10JAN22 WIN10 Automatic Update.
We're still sorting through this. If anyone is seeing something similar please reply here.
Thanks & 73
Paul
N8CVW