There is a nice PSKReporter SDK already bundled up to make this easier. https://pskreporter.info/pskreporter.zip

Ahh. i see. Yeah no need to rock the boat for ‘good to have’ things.

@minicowman The one line that stands out is: 2021-11-30 16:24:44 WARNING: VARA is not connected to any App via TCP Port 8300 Please visit the setting page and ensure that your path and port settings are the same as defined in the VARAHF config. In the second set of messages, I can see you are trying to RX a CQ with an SSID. I have seen the errors myself at times while doing this. I have yet to confirm that having an SSID suffix works 100%. if you want to try it you can switch to CAT control and use the Kenwood TX;/RX; commands for PTT.. At least IIRC the TS-590s uses the same protocol as the TS2k. and manually select USB and tune

Excellent

I have seen this as well. I run my bandpass ony Flex slightly wider than 500 to allow for the correction but anything beyond 50hz seems to be a lost cause. I have recalibrated my rig a few times against WWV to ensure It wasn't me. Some older superhet rigs are just off a bit and VARA is pretty finicky about that. Rightly so with the number of carriers it tries to pack into that tight space

Hey Tom. Yes, that means that there is an incoming connection. The "NO LUCK" message simply shows that the connection wasn't able to be negotiated. On a related note.. our last QSO had been cut off due to a lock-up on my side. I did try to reconnect but was unable. Was this incoming connection request you are talking about from after our QSO? (I was trying to reconnect but heard nothing in reply) And to answer your question, Yes. Your machine will answer automatically. and if you are away you can set the away box to have it reply with a canned answering machine message.

I realized after posting that the logger does use UTC. I guess my confusion comes from when I review the beacon and CQ history. my suggestion still stands, but forget I mentioned anything about the logger. Irad already has a handle on that one.

I'll be adding this challenge to my portable setup

Hey man, no rush and no worries. this is just a small quirk due to the real estate available under lower resolution screens. no biggie

Ahh, reviewing the image itself the problem lies in the amount of real estate the actual form takes up. Clearly, it’s been modeled on a larger screen with a ton more space to play with. This limitation is my issue and not the problem of the application. I think the only place we can reclaim space from would be the data stream windows vertical height. if that element was able to auto-resize and scroll when the form height was adjusted I think we’d be in good shape. The width can be reclaimed from the status boxes. I think that main form resize ability with auto-resize on the message queue, the message being sent and command stream and log boxes would make that doable.