KB6IBB SWL Logger Activity
A shortwave listening logger for shortwave and amateur radio.
Brought to you by:
kb6ibb
Activity for KB6IBB SWL Logger
-
Jeff Stillinger posted a comment on ticket #17
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.
-
Chloe Stratton created ticket #17
Trouble connecting GQRX with KB6IBB SWL Logger
-
.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...
-
Greg Hemmings posted a comment on ticket #16
Thank you so much! All should be fine now!🙂 [signatureImage] From: tickets@kb6ibbswllogger.p.re.sourceforge.net tickets@kb6ibbswllogger.p.re.sourceforge.net on behalf of Jeff Stillinger kb6ibb@users.sourceforge.net Sent: Monday, January 27, 2025 5:55:39 PM To: [kb6ibbswllogger:tickets] 16@tickets.kb6ibbswllogger.p.re.sourceforge.net Subject: [kb6ibbswllogger:tickets] Re: #16 .exe will not open Yep, that old config file would be the problem, it somehow got corrupted. Your database path is off. The...
-
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...
-
Hi Jeff! I am attaching a screenshot of the locations of KB6IBB-SWLLogger and SWLog51. Also attaching the config file, it appears to be old information. The version listed is not the one I downloaded. I had an older version about a year ago on an older computer. Could that be the problem? Should I delete the config file and reinstall? [cid:78dbc836-e81b-44bc-991f-c4729eca0a8a] From: tickets@kb6ibbswllogger.p.re.sourceforge.net tickets@kb6ibbswllogger.p.re.sourceforge.net on behalf of Jeff Stillinger...
-
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...
-
.exe will not open
-
KB6IBB SWL Logger released /SWL Logger-V5/README
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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
-
Expected error, one that was not trapped intentionally as per the instruction manual.
-
Feature enhancement: Add Aoki database import in addition to HFCC
-
Date and time entry is confusing
-
secretlondon created ticket #14
Date and time entry is confusing
-
Bug - DatabaseException not handled
-
Feature enhancement: Add Aoki database import in addition to HFCC
-
Feasibility Study Complete After careful consideration of adding the AOKI database to our shortwave database, we have found the addition to not be feasible at this time. The AOKI master database, NC<season>.txt, has several formatting errors throughout the database. The misaligned data fields cause data to not be present at the exact same location in the data string for every single record. Line 161 of the current file is a example. More specifically, the time field is not correctly read, causing...
-
Older MacOS version?
-
The MacOS version has been discontinued. There are no current plans to revisit MacOS at this time.
-
Anna M Kucharski created ticket #12
Older MacOS version?
-
Feature enhancement: Add Aoki database import in addition to HFCC
-
Will process and take under advisement.
-
Hugh Whelan created ticket #11
Feature enhancement: Add Aoki database import in addition to HFCC
-
-
-
-
-
-
-
-
-
-
Log import from version 4
-
2024-03-05 - Version 4.6.1-4 update released that fixes the reported bug. Instructions for a resolution was given to the reporting party, no further problems reported. At this time, issue is resolved and the ticket is closed. //KB6IBB
-
-
-
-
James Darrow posted a comment on ticket #10
That did it. All records imported and working on version 5. Thanks again!! 73 Jim, KB9MMC On 02/03/2024 17:26, Jeff Stillinger wrote: Found it!! Exactly what I though it was. A rouge date that somehow made it in. Note the March 12th Date End, missing a "/" character which caused the date to not be saved in the long date format. I found about 10 of them. This is going to be time consuming, but, no other way to do it. You just have to look at the Date End and correct the dates that are not in long...
-
Thanks Jeff, I'll go back and take a look. It sounds like that may have been the time when I was transferring things from my old logging software, transferring 500 files by hand wasn't fun. Thanks again for the help. 73 Jim, KB9MMC On 02/03/2024 17:26, Jeff Stillinger wrote: Found it!! Exactly what I though it was. A rouge date that somehow made it in. Note the March 12th Date End, missing a "/" character which caused the date to not be saved in the long date format. I found about 10 of them. This...
-
2024-03-02 - Received the end users database file and reviewed it for errors. Several date format errors were noted. Provided corrective action instructions to the end user. Issued a HIGH PRIORITY bug fix for version 4.6 to ensure mis-formatted dates will not be saved to the database. Update pending. Support ticket will remain in Pending status until the 4.6 update is issued. //KB6IBB
-
Found it!! Exactly what I though it was. A rouge date that somehow made it in. Note the March 12th Date End, missing a "/" character which caused the date to not be saved in the long date format. I found about 10 of them. This is going to be time consuming, but, no other way to do it. You just have to look at the Date End and correct the dates that are not in long date format record by record using Version 4.6. At least you have less than a 1,000 records to review. Once they are all saved accordingly,...
-
Hey Jeff, Here are both ways name changed to a PDF and a compressed version. Yes I'm using the February 28th release. After a few attempts I went to the beta version but when I got the same error message I went back to the latest release. It also appeared at a quick glance it looked like there wasn't as many catagories in version 5 for the type of station. I'll look again. Thanks!! Jim, KB9MMC On 02/03/2024 15:02, Jeff Stillinger wrote: Hi James, I don't see the attachment. Possibly being filtered...
-
Hi James, I don't see the attachment. Possibly being filtered by one of our ISPs. See if you can try sending it as a zip file or rename it to a .pdf to fool the A.I. I really do need to see the file. I suspect there may be a rouge date entry in the data somewhere. I appreciate your patients during our growing pains as we move the logger from a smaller U.S. user base to a much larger world wide user base. Date/Time in a international format was the biggest feature request from our new and developing...
-
Hi Jeff, Attached is a copy of my version 4 database as requested. Thanks for the help. You have a great piece of software! 73 Jim, KB9MMC On 02/03/2024 03:26, Jeff Stillinger wrote: Hi James, Would it be possible for you to email me your version 4 database? Looking over the code, and our test runs, databases going all the way back to version 2 import without error. I would really need to take a look at yours specifically to track it down. When all is said and done, I will send you back either a...
-
Log import from version 4
-
2024-03-01 - Contact made with end user by private email. Awaiting response from user to email me his Version 4 database for inspection. Conducted a retest in the lab with version 2, 3, and 4 databases with no errors generated. It will be vital to see the version 4 problematic database to troubleshoot the issue. //KB6IBB
-
Hi James, Would it be possible for you to email me your version 4 database? Looking over the code, and our test runs, databases going all the way back to version 2 import without error. I would really need to take a look at yours specifically to track it down. When all is said and done, I will send you back either a database you can import, or just a nice pretty version 5. Whichever you would like. On 3/1/24 19:23, James Darrow wrote: [tickets:#10] Log import from version 4 Status: open Milestone:...
-
Log import from version 4
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1 >
