Search found 21 matches

by NS8K
06 Jan 2018, 22:23
Forum: User Support
Topic: LoTW weirdness
Replies: 41
Views: 5939

Re: LoTW weirdness

Tom, You haven't missed an update. I think Terry was just providing a "status update" saying that the programmer(s) had come up with a solution to the state issue and the next project at hand was to develop a similar fix for the county field. When this new code is ready and tested I think we might s...
by NS8K
04 Jan 2018, 13:57
Forum: User Support
Topic: LoTW weirdness
Replies: 41
Views: 5939

Re: LoTW weirdness

Jim, Mike's SQL statement does fix the state field of records that have the characters // in positions 4 and 5 so you understand that correctly. It is the county and not the country field that also has a problem. That was probably a typo on your part. Mike's statement does not do anything with the c...
by NS8K
03 Jan 2018, 03:27
Forum: General discussions
Topic: Fake calls on FT8
Replies: 6
Views: 1377

Re: Fake calls on FT8

Rich, I think it would have taken another round with AP off and that is a nice example where AP did it's job. If I understand it correctly, the a3 indicates your call and K5SDR were assumed. When it was all done, the program must have been quite confident in the outcome because there are no ?'s (unl...
by NS8K
02 Jan 2018, 22:54
Forum: General discussions
Topic: Fake calls on FT8
Replies: 6
Views: 1377

Re: Fake calls on FT8

Rich, Here's where it is described in section 12. http://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-1.7.1-devel.html Basically, assumptions are made about what is contained in the message (which may be your callsign or other parts of the message) and if the assumption plus what is actual...
by NS8K
02 Jan 2018, 20:31
Forum: General discussions
Topic: Fake calls on FT8
Replies: 6
Views: 1377

Re: Fake calls on FT8

Rich, If you are running WSJT-X, check the settings under the Decode Menu. You probably have Enable AP checked. With that checked, it "works harder" at decoding and will make a mistake every once in a while. You will see a few extra letters in the receive window to the right of the normal informatio...
by NS8K
02 Jan 2018, 03:00
Forum: User Support
Topic: CW Skimmer and Log4OM.
Replies: 6
Views: 1292

Re: CW Skimmer and Log4OM.

Maybe I'm stating the obvious here and if so, I apologize. I had a similar situation with Log4OM, Omnirig, WSJT-X and JTAlert. I'm using a 2 cable connection with an IC-7300. Log4OM has always been run as Administrator and I discovered that JTAlert/WSJT-X also had to be run as Administrator or CAT c...
by NS8K
02 Jan 2018, 02:30
Forum: Feature suggestions
Topic: Selecting Default Mode and Band
Replies: 0
Views: 872

Selecting Default Mode and Band

I think it is not possible to change the default Mode from SSB or the default band from 20m. I have wanted to do that and read a post that said it is not possible. In some of the setup files like ReportListCW.txt, the default selection is designated with a *. Could this method also be incorporated f...
by NS8K
02 Jan 2018, 02:03
Forum: User Support
Topic: reportlistjt.txt missing +00 entry
Replies: 0
Views: 687

reportlistjt.txt missing +00 entry

I log FT-8 contacts using JTAlert along with WSJT-X like many folks do. When a signal report of 0 is sent or received, it is logged as +00. The default reportlistjt.txt file that comes with Ver 1.30 does not have +00 as a value although it does have 00. QSO's log ok with +00 but if you open one to d...
by NS8K
19 Dec 2017, 02:41
Forum: User Support
Topic: LoTW weirdness
Replies: 41
Views: 5939

Re: LoTW weirdness

I am glad I ran into this thread since I am having the same problem. I am not a programmer and do not particularly want to mess with the database. So what should I do? Has the lotw staff been made aware of this problem and if so are they going to fix it? Should I just on saving FT8 contacts and doi...
by NS8K
15 Dec 2017, 02:26
Forum: User Support
Topic: LoTW weirdness
Replies: 41
Views: 5939

Re: LoTW weirdness

If you download the sqlite3 command line utility you can fix this util LOTW or Log4OM fixes this. Just run 'sqlite3 database.sqlite' with whatever your database name is and do this: update log set state=SUBSTR(state,1,2); de Mike W9MDB Mike, That was easy but yesterday I had a QSO with VK2DX in New...