I don't know if this is a bug, but the frequency tracking has stopped working for me. When v3.7.9 came out, I check the box to turn it on. I thought it odd that once the box was checked, it turned grey and can no longer be changed. It worked though.
I noticed today, the frequency tracking simply doesn't work. All of the rest of VarAC works as it should.
It hasn't failed the entire time Debug was on. I wasn't sure if Debug would self-truncate. I turned Debug off.
Debug has a downside. overall performance impact and a HUGE log file
ok. next thing to try - put it back on 100ms and change on the settings screen the polling interval... to 4 seconds. lets see if that works.
I made the change and the problem still exists. Funny how if I turn on Debug, I never see it happen. What's with that? I turn on Debug and 100% of the time Freq Trk starts working immediately. Any downside to leaving Debug on?
Try to increase this value in the VarAC.ini file to 200 and let me know how it goes
PortWaitTimeMs=200
I understand. However, as long as debug is enabled, Freq Trk works. When debug is disabled, Freq Trk will stop working at some point. If I enable debug, it immediately starts working again. I will keep trying to capture it not working while debug is enabled. Maybe I should just leave debug enabled ;)
I need a debug log to analyze. If it is now not reading please enable debug and send me a few minutes of log so i can see thr attempts.
The Freq Trk stopped working again and in the VarAC log status box, it says the below. When I open settings and check Debug, Save and Exit, then Frequency Tracking suddenly starts working again. Something jogs the Freq Trk function when the settings refresh after saving.
15:24:23 - Debug mode disabled
15:24:24 - FREQ Schedule disabled
15:24:24 - Setting away status to true (load)
15:24:24 - Opening com port
15:24:25 - Unable to send CAT command to Com port. Closing port until next try.
15:24:25 - Opening com port
15:24:25 - Unable to send CAT command to Com port. Closing port until next try.
There doesn't seem to be anything to do right now. It's working when I got up this morning. Go figure.
Frequency tracking had stopped working at least a couple days ago. I wasn't able to toggle the Freq Trk setting because it was greyed out.
I downloaded and installed the new CAT file. Stopped and restarted VarAC, then the Freq Trk option was no longer greyed out, so I toggled it off and back on. Freq Trk still didn't work, but the option wasn't greyed out - I turned Freq Trk off and left VarAC in Beacon all night.
I get up to Irad's email with debug instructions. I enable Freq Trk and debug. Cycle VarAC. Now Freq Trk is working and no error about com port. I let debug run a few minutes and the com port seems to Open as it should in the running log. I disabled debug and am letting it run with Freq Trk enabled to see what happens.
I have no explanation except that overnight, the VarAC Fairies have fixed it.
Pse do this so I can analyze :
Enter debug mode (under settings), run VarAC for a few minutes and send me the VarAC.log of those minutes so I can see the failing frequency reading.
Send me your VarAC.ini file
to my email: iradirad@gmail.com
Update: I downloaded and installed the latest CAT file, restarted VarAC. At that point the frequency tracking check box was now available to be checked/unchecked. I unchecked and re-checked it. Frequency tracking still didn't work.
I noticed in the VarAC Log that there was a message of unable to send command to com port. I unchecked the Frequency tracking box and they error went away. Obviously, the frequency tracking is having trouble sending CAT commands to the com port that is working fine for all other commands. VarAC seems to work fine other than the Frequency Tracking. I hope this helps.