Not that this is an issue itself, naturally the polling will fault but the report probably could be suppressed if the reason is that the modem is in a disconnected state because it was invoked by the user. I'm not being picky, I just noticed that this was showing up in the log and may cause confusion for some. In the following log I started VarAC, Clicked the button and disconnected the modem, and then clicked and reconnected the modem. -jon 23/12/2022 19:36:26 - Connected to VARA modem 23/12/2022 19:36:26 - Setting Bandwith to 500Hz 23/12/2022 19:36:26 - Change frequency: to last frequency used before shutdown. 23/12/2022 19:36:26 - PSKReporter self report: Logged successfully 23/12/2022 19:36:26 - VarAC base directory: C:\VarAC\ 23/12/2022 19:36:26 - VARA version: VARA HF v4.6.9 23/12/2022 19:36:36 - Disconnecting VARA modem... 23/12/2022 19:36:36 - Disconnected! 23/12/2022 19:36:36 - Error in mailbox_send_outbox_thread 23/12/2022 19:36:36 - Error: Unable to read data from command stream of VARA modem. Disconnecitng modem command stream. 23/12/2022 19:36:36 - Error: processing Modem data stream: Thread was being aborted. at System.Net.UnsafeNclNativeMethods.OSSOCK.recv(IntPtr socketHandle, Byte* pinnedBuffer, Int32 len, SocketFlags socketFlags) at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode) at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at VarAC.VarAC.<button_connect_varahf_Click>b__629_2() 23/12/2022 19:36:36 - Thread was being aborted. at System.Net.UnsafeNclNativeMethods.OSSOCK.recv(IntPtr socketHandle, Byte* pinnedBuffer, Int32 len, SocketFlags socketFlags) at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode) at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at VarAC.VarAC.<button_connect_varahf_Click>b__629_0() 23/12/2022 19:36:36 - Thread was being aborted. at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout) at System.Threading.Thread.Sleep(Int32 millisecondsTimeout) at VarAC.VarAC.<button_connect_varahf_Click>b__629_5() 23/12/2022 19:36:36 - Unable to read data from data stream of VARA modem. Disconnecitng modem data stream. 23/12/2022 19:37:01 - Connecting VARA Main Modem Command interface... 23/12/2022 19:37:01 - Connecting VARA Main Modem data stream... 23/12/2022 19:37:01 - Connecting VARA Main Modem KISS Command interface... 23/12/2022 19:37:01 - Connecting VARA Monitor Modem Command interface... 23/12/2022 19:37:01 - Connecting VARA Monitor Modem data stream... 23/12/2022 19:37:01 - Connected to VARA modem 23/12/2022 19:37:01 - Setting Bandwith to 500Hz 23/12/2022 19:37:01 - VARA version: VARA HF v4.6.9

Just thinking, I wonder if it would be possible to incorporate a monitor window in the VarAC client itself. This would eliminate the need to have the VaraHF modems maximized and organized taking up valuable desktop real estate. We could run them minimized and still be able to view the active QSO's from within the VarAC client. Not sure how well that would work out but it could be something that can potentially be enabled or disabled. a window that can be docked or detached?

I would like to submit for consideration that all timestamps are maintained in UTC and not the local QTH timezone. This may also help with keeping logging contacts straight. Alternate seasonal time shifts that are observed in some regions can compound confusion with the issue of local timestamps.

Embed control characters into custom messages to send on select. i.e. "This is a test message &crlf " to automatically queue the canned message on select. Speaking with K1DOW he mentioned that he would prefer the canned message be sent after selection instead of requiring a manual submission to the queue.