This is about a minor "problem" I saw in SmartSDR 2.4.9 with a utility that I wrote for myself and have used over a year now. It has an AutoCQ function that I use for SSB operation. It entails playing .wav files that I record in the Audacity program. It, among other things, programmatically activates the DAX TX Stream and then plays the wave file.
It HAD worked perfectly until I installed firmware 2.4.9 but now works almost perfectly EXCEPT I can NOT monitor the audio using the MON button (in the P/CW tab of the settings). It transmits the audio but I just can't monitor it now with the MON button activated.
I have a 6400 (NOT the M model) which otherwise runs well with the 2.4.9 firmware and installed with no problems. I also reverted to previous firmware version and the "problem" went away. Then again installed 2.4.9 and the problem came back.
I did "fix" the problem, however. I figured out that activating the DAX TX Stream via code with the 2.4.9 firmware had approximately 20-40 millisecond delay before it ACTUALLY started which caused the code after that (which relied on DAX TX Stream being up and running) to not entirely do what was expected. It did not cause any error messages or exceptions but it made the monitoring of the TX audio inoperative.
Anyhow, I "fixed" it by just setting up a timer so it would wait 50 milliseconds before it executed the rest of the code after activating DAX TX Stream.
I just wanted to pass this on in case someone else runs into similar problems with their coding.
---Gary WB8ROL
It HAD worked perfectly until I installed firmware 2.4.9 but now works almost perfectly EXCEPT I can NOT monitor the audio using the MON button (in the P/CW tab of the settings). It transmits the audio but I just can't monitor it now with the MON button activated.
I have a 6400 (NOT the M model) which otherwise runs well with the 2.4.9 firmware and installed with no problems. I also reverted to previous firmware version and the "problem" went away. Then again installed 2.4.9 and the problem came back.
I did "fix" the problem, however. I figured out that activating the DAX TX Stream via code with the 2.4.9 firmware had approximately 20-40 millisecond delay before it ACTUALLY started which caused the code after that (which relied on DAX TX Stream being up and running) to not entirely do what was expected. It did not cause any error messages or exceptions but it made the monitoring of the TX audio inoperative.
Anyhow, I "fixed" it by just setting up a timer so it would wait 50 milliseconds before it executed the rest of the code after activating DAX TX Stream.
I just wanted to pass this on in case someone else runs into similar problems with their coding.
---Gary WB8ROL
Posted 8 months ago
Be the first to post a reply!
