Does Profiles Break Persistence?

  • 1
  • Problem
  • Updated 4 years ago
  • Solved
  • (Edited)
Colleagues,

I use a 6700 and installed SmartSDR 1.3 as soon as it was available. I mostly operate the digital modes JT65 and JT9 with WSJT-X, so I created global profiles for all bands and a transmit profile for digital modes. When I select one of these profiles, the 6700 seems to operate normally on the selected band.

I believe that there is an issue between profiles and persistence, however, that can be best illustrated by a recent example.

Last night, I was operating on 40 meter JT65 after selecting the corresponding profile. The 6700 was operating normally. I then shut down for the evening by closing SmartSDR and then powering-down the 6700. I also shut down the power supply. This is my normal scenario in the evening when I am done playing radio.

I got up fairly early this morning and decided to try to make a few contacts on 40 meters JT65 before daylight. I powered-up the 6700 and the computer and started PowerSDR. Because of persistence, the radio came-up in what appeared to be the same state that I left it in the previous evening. I clicked the TUNE button in PowerSDR to tweak my antenna a bit and everything seemed normal. I then clicked the TUNE button in WSJT-X and noted that the power output from the 6700 was much lower than what I had been running the previous evening. I also noted that I was not hearing any signals.

I decided to re-invoke the profile for that band and mode (40 meters, JT65) and voila about six strong signals appeared in the WSJT-X waterfall and when I clicked on the WSJT-X TUNE button, the power output was normal.

I have seen various comments on the Community regarding low power output and wonder if those issues could have been caused by a scenario similar to the above? I have not tested for the above issue on the other bands, but I doubt if it is only a 40 meter problem.

The fix is easy...just select your desired profile and ignore persistence, but I do believe that a "bug" is crawling around somewhere in SmartSDR 1.3.

Ed, K0KC
Photo of Ed, K0KC

Ed, K0KC

  • 255 Posts
  • 19 Reply Likes

Posted 4 years ago

  • 1
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9052 Posts
  • 3435 Reply Likes
Official Response
This isn't a persistence bug, but a defect in the way transmit profiles are initialized.  This issue will be fixed in the next release of SmartSDR.