VARAC works as expected. I can also start a CQ on a different slot and qrg is changed automagically. But: If I decide to use "slot sniffer" to check the slot VARAC blocks and I have to kill it via Task manager. (Using Windows 10)
73
Rupert DL3NO
top of page
bottom of page
Hi Rupert. Sorry for the late reply. Can you please shoot a video (with your cellphone) and send either here or by mail to iradirad@gmail.com ? I want to see the whole incident. maybe it will give me additional clues as I am still unable to understand what is going on. Thank you !
Thank you.
Can you please send me a screenshot of the task manager showing the VarAC.exe process with its CPU/IO once you are in hang ? and also include a screenshot of total memoryt and CPU status of your PC during the hang.
I want to see if VarAC is consuming CPU while in hang and what is the overall status of the PC.
Please also tell me what is your email so I can send you a test version for debugging.
Thank you,
It is the screen, where you click for the "slot sniffer" and everything freezes. Not changing the screen, nothing. Cannot choose anything in VarAC, just start the Task manager by <ctrl><alt><del> .
I see by the log that you did a SLOT SNIFFER but then you returned back.
Can you send a screenshot of the hang (entire screen). Does VarAC goes into "not responding" ?
Hi, Irad, and good morning..
Log Data as requested:
19/10/2024 05:49:57 - End of Load_configuration
19/10/2024 05:50:08 - Starting write_command_stream_log
19/10/2024 05:50:08 - Writing event to command stream log
19/10/2024 05:50:08 - End of write_command_stream_log
19/10/2024 05:50:09 - Unchecking I'm away due to CQ Call
19/10/2024 05:50:09 - Away status set to false
19/10/2024 05:50:17 - SLOT sniffer: Changing frequency to slot frequency
19/10/2024 05:50:17 - Frequency converted value:01410350
19/10/2024 05:50:17 - Opening COM port
19/10/2024 05:50:17 - Writing to com port
19/10/2024 05:50:17 - Cat command (HEX): 0A00000007
19/10/2024 05:50:17 - CAT cmd result: 00
19/10/2024 05:50:17 - Writing to com port
19/10/2024 05:50:17 - Cat command (HEX): 0141035001
19/10/2024 05:50:18 - CAT cmd result: 00
19/10/2024 05:50:18 - Change combobox freq text to: 14.103.500
19/10/2024 05:50:18 - Playing sound: Frequency change
19/10/2024 05:50:18 - SLOT sniffer: Changing frequency back to calling frequency
19/10/2024 05:50:18 - Frequency converted value:01410500
19/10/2024 05:50:18 - Writing to com port
19/10/2024 05:50:18 - Cat command (HEX): 0A00000007
19/10/2024 05:50:18 - CAT cmd result: 00
19/10/2024 05:50:18 - Writing to com port
19/10/2024 05:50:18 - Cat command (HEX): 0141050001
19/10/2024 05:53:41 - Shutting down VarAC...
19/10/2024 05:53:41 - Exiting - Kiling VARA modem instances
19/10/2024 05:53:41 - Writing to com port
19/10/2024 05:53:41 - Cat command (HEX): 0000000088
19/10/2024 05:53:41 - CAT cmd result: f0
19/10/2024 05:53:41 - Exiting - Closing main command stream connection
19/10/2024 05:53:41 - Exiting - Closing main KISS command stream connection
19/10/2024 05:53:41 - Exiting - Closing main data stream connection
19/10/2024 05:53:41 - Exiting - Closing CAT command COM port
19/10/2024 05:53:41 - Exiting - Closing monitor data stream connection
19/10/2024 05:53:41 - Exiting - Closing monitor command stream connection
Put your VarAC in debug mode (under settings -> MISC2.
perform the action that make the hang.
Wait for 2 minutes in the hang and kill VarAC.
Paste here the log data - maybe we will find a hint there