SmartSDR v3.8.19 and the SmartSDR v3.8.19 Release Notes | SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes
Power Genius XL Utility v3.8.8 and the Power Genius XL Release Notes v3.8.8
Tuner Genius XL Utility v1.2.11 and the Tuner Genius XL Release Notes v1.2.11
Antenna Genius Utility v4.1.8
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
interesting anomaly after upgrading to new version
I thought the upgrade went to easy. LOL
Here is what I'm up against.
I work a lot of modes, but now I'm trying to work dxcc and WAS using Jt modes.
I use DXLab suite and have DDuT which normally isn't needed in this quest. (barefoot only)
A qsy initiated by Commander will result in an instantaneous qsy of Commander, Smart SDR (latest) and WSJT-x.
A qsy initiated by WSJT will result in an instantaneous qsy of Smart SDR (latest) and Commander.
But a qsy initiate by SSDR does not always result In what I asked for. LOL usually it's the frequency that is in error while the mode and filter not changing or changing to something other than what was expected.
SmartSDR will qsy to the correct band occasional but the other two apps, Commander and WSJT-x will switch to someo ther wsjt frequency, usually they both switch to the same frequency, but I've seen it where all 3 elements are displaying different band-frequencies. LOL
as long as I initiate the qsy from WSJT-x, the band, mode and filter will be correctly qsyed and if a qso results, the log is saved with the correct data.
I experienced this to a lesser degree (it only happened occasionally) with the SSDR version 1.
I'm betting it's somethin in my setup. Does anyone experience anything similar to this and if so, have they found a fix.
Again so I make it clear, all qsy attempts by selecting a band-mode from WSJT-x properly result in those settings being changed in SmartSDR, and Commander, and of course the log.
It's not a deal breaker...I just have to remember to watch the log.
Answers
-
Hi Bill,
Coincidentally, I posted this morning, on the DDUtil Yahoo group, a qsy and TX selection problem with 1.6.17 that may be related. DDUtil is not always seeing TX slice frequency changes made in SSDR. I saw it on slice B, but it is not consistent. I am still trying to find a way to reliably duplicate the problem.
Here is the post:
https://groups.yahoo.com/neo/groups/DDUtil/conversations/messages/7523
73, Bob, N7ZO0 -
Bill, I had the similiar problems when I tried the DXLab suite and DDUtil3.
Now I'm back to HRD DM780 and HRD Logbook with WSJT-X and JTAlertX.
This setup works well with a MiniDeluxe server.
Trying out DDUtil3 I never have had any problems with HRD, only with WSJT-X...
73, Alex DH2ID
0 -
Remove DDUtil from the mix and see if the problem still exists. The first step in troubleshooting is to divide and conquer.0
Leave a Comment
Categories
- All Categories
- 283 Community Topics
- 2.1K New Ideas
- 526 The Flea Market
- 7.5K Software
- 6K SmartSDR for Windows
- 145 SmartSDR for Maestro and M models
- 352 SmartSDR for Mac
- 249 SmartSDR for iOS
- 228 SmartSDR CAT
- 169 DAX
- 352 SmartSDR API
- 8.7K Radios and Accessories
- 7K FLEX-6000 Signature Series
- 6 FLEX-8000 Signature Series
- 840 Maestro
- 43 FlexControl
- 845 FLEX Series (Legacy) Radios
- 788 Genius Products
- 414 Power Genius XL Amplifier
- 274 Tuner Genius XL
- 100 Antenna Genius
- 242 Shack Infrastructure
- 166 Networking
- 403 Remote Operation (SmartLink)
- 127 Contesting
- 624 Peripherals & Station Integration
- 125 Amateur Radio Interests
- 860 Third-Party Software