Jeff Stillinger

Please review Section 11 of the instruction manual. There is no magic, the logger simply polls gqrx on the TCP port. If you have changed the TCP port number in your configuration, in needs to be changed back to the gqrx default. Please also review the Rolling Release Support Policy in the instruction manual.

.exe will not open

Disposition of ticket number 16. Ticket closed with the problem resolved. End user had a left over corrupted configuration file from a previous installation. The fail safe built for upgrading versions did work as intended by preserving the previous configuration, however generated an error when it was discovered the left over config file had a corrupted path. Pointing to a non existent directory. Recommendation is to address this issue in the instruction manual so that end users are aware this could...

Yep, that old config file would be the problem, it somehow got corrupted. Your database path is off. The logger is currently looking for the database in: C:\Users\gregh\Downloads\KB6IBB-SWLLogger500-3LTS-Win64\KB6IBB-SWLLogger500-3LTS-Win64\ Simply edit the ~\AppData\Roaming\KB6IBB-SWLog5.cfg files path field using Notepad and replace it with: C:\Users\gregh\Documents\KB6IBB-SWLLogger\ Be careful not to delete the semi-colon field seperators. Other options include deleting the config file. When the...

First and foremost, ensure you don't have any security software getting in the way. It appears that you did not install according to instructions. If you wish to use One Drive, then section 4.3 of the instructions applies. Which first requires a working standard installation to be completed. Either way, One Drive does work, just depends how you configured your system. You can lean about all the One Drive features and configuration option on the Microsoft Knowledge Base so that you don't have to use...

Date and time entry is confusing

No error. Logger is performing as intended. Reference: Section 5.6 of the Instruction Manual.

Bug - DatabaseException not handled