Both myself and WD9DUI have had multiple instances of VarAC becoming "unresponsive" or simply crashing (and leaving Vara-HF running) over the past couple of weeks. This happens during a QSO, but not while the program is idle.
We've had this happen while in QSO with different stations.
We both are running the latest VarAC and VARA-HF (VarAC 3.0.2, Vara-HF 4.5.5). and have no (or in my case ONE other program running (Log4OM).
We both are running robust computers, with plentiful RAM (in my case 16 GIG).
We've both set VarAC to run in "real time" in Windows 10.
73, Joe WD4KAV
I have had this happen a few times while in qso, the handshaking just stops, goes on for over a minuet most times the other station just drops the connection and starts up again. The db readings are ok , not sure if other sigs/ noise are taking it down or?? I would think that the watch dog timer would kick in after 10-20 sec of inactivity and start up the handshaking???
Hi Joe @wd4kav , @gw4ozuand all
In order for me to pinpoint the problem I will appreciate your help:
1. Please put VarAC in Debug mode. This will spill plenty of messages. once the Application Freeze or crash, before restarting it, please send me the VarAC.log file so I know what was the last thing that happened.
in VarAC.ini change :
2. If the application crashes, please get the crash report from the windows event viewer and send it to me so I can inspect. Most likely you will find it under applications windows logs --> applications. see screenshot.
This will help alot !
I have not had this happen here.
I admit that I have not been really active with it yet but have had a qso or two.
I will try it out today and see if I can get this to happen here.
73 de w8nsi Jim
I have had this issue as well.