|
locked
Slow path to logging
By
Radio K0HB
· #33339
·
|
|
locked
Slow path to logging
Thanks for “hanging with me” on this Lauri. Here are those screen shots. Notice on the Log4OM “Configuration screen” I have an additional inbound at port 1240, not seen on your example. I have uncheck
Thanks for “hanging with me” on this Lauri. Here are those screen shots. Notice on the Log4OM “Configuration screen” I have an additional inbound at port 1240, not seen on your example. I have uncheck
|
By
Radio K0HB
· #33333
·
|
|
locked
Slow path to logging
Forgot to include: Using SQLite, and my log size is about 98,000 QSO’s. Sent from Mail for Windows 10
Forgot to include: Using SQLite, and my log size is about 98,000 QSO’s. Sent from Mail for Windows 10
|
By
Radio K0HB
· #33327
·
|
|
locked
Slow path to logging
File enroute.
By
Radio K0HB
· #33326
·
|
|
locked
Slow path to logging
I ran some experiments, Laurie, and it appears that JTAlert is involved. First, as a benchmark, I took JTAlert offline and logged directly from WSJT-X to Log3OM. From the time I pressed “Log it” until
I ran some experiments, Laurie, and it appears that JTAlert is involved. First, as a benchmark, I took JTAlert offline and logged directly from WSJT-X to Log3OM. From the time I pressed “Log it” until
|
By
Radio K0HB
· #33322
·
|
|
locked
Slow path to logging
Interesting. My app versions: Log4OM 2.11.0 WSJT-X 2.3.0 JTAlert 2.16.17 My WSJT-X is newer than yours, but this problem pre-dates that upgrade. Sent from Mail for Windows 10
Interesting. My app versions: Log4OM 2.11.0 WSJT-X 2.3.0 JTAlert 2.16.17 My WSJT-X is newer than yours, but this problem pre-dates that upgrade. Sent from Mail for Windows 10
|
By
Radio K0HB
· #33316
·
|
|
locked
Slow path to logging
I am experiencing what I think is exceptionally long transfer of contact information from WSJT-X to Log4OM via JTAlert. Here’s my setup. Computer is a very capable I7 windows machine, 16Gig RAM, SSD d
I am experiencing what I think is exceptionally long transfer of contact information from WSJT-X to Log4OM via JTAlert. Here’s my setup. Computer is a very capable I7 windows machine, 16Gig RAM, SSD d
|
By
Radio K0HB
· #33314
·
|
|
locked
Receive Lock
That feature would apply to WSJT, 73, de Hans, KØHB “Just a Boy and his Radio”
That feature would apply to WSJT, 73, de Hans, KØHB “Just a Boy and his Radio”
|
By
Radio K0HB
· #26019
·
|
|
locked
JT ALERT locks up
I had a similar issue — locked up after a couple hours of use — had to shut down via ctrl-alt-delete 73, de Hans, KØHB “Just a Boy and his Radio”
I had a similar issue — locked up after a couple hours of use — had to shut down via ctrl-alt-delete 73, de Hans, KØHB “Just a Boy and his Radio”
|
By
Radio K0HB
· #25804
·
|
|
locked
Minor persistent glitch
This is from the normal (red icon) version. I haven’t installed alternates. 73, de Hans, KØHB “Just a Boy and his Radio”
This is from the normal (red icon) version. I haven’t installed alternates. 73, de Hans, KØHB “Just a Boy and his Radio”
|
By
Radio K0HB
· #25793
·
|
|
locked
Minor persistent glitch
Installed 2.14.5. Works as announced! Still one minor glitch at my station. The “#” column in the bottom (US State) line still reflects the same total as the “DXCC” line. 73, de Hans, KØHB "Just a boy
Installed 2.14.5. Works as announced! Still one minor glitch at my station. The “#” column in the bottom (US State) line still reflects the same total as the “DXCC” line. 73, de Hans, KØHB "Just a boy
|
By
Radio K0HB
· #25780
·
|
|
locked
Great Support
One mark of an excellent company is how they treat a customer AFTER the product is delivered. Now I know that Laurie VK3AMA HamApps is not a “company” in the strictest interpretation of the word, but
One mark of an excellent company is how they treat a customer AFTER the product is delivered. Now I know that Laurie VK3AMA HamApps is not a “company” in the strictest interpretation of the word, but
|
By
Radio K0HB
· #25045
·
|
|
locked
"US State" line
I’ve sent a ZIP of my Log4OM log. Seems to have passed through. Hope you got it. I’ve also updated JtAlertX to 2.14.1. Regarding your note below, I just tried to work K0MAN (First QSO). I followed the
I’ve sent a ZIP of my Log4OM log. Seems to have passed through. Hope you got it. I’ve also updated JtAlertX to 2.14.1. Regarding your note below, I just tried to work K0MAN (First QSO). I followed the
|
By
Radio K0HB
· #25010
·
|
|
locked
"US State" line
Here are two screen captures. In the first I am attempting to work N2BJ, who I have previously worked on another band. Note that the bottom line is populated with the bands that I have previously work
Here are two screen captures. In the first I am attempting to work N2BJ, who I have previously worked on another band. Note that the bottom line is populated with the bands that I have previously work
|
By
Radio K0HB
· #24985
·
|
|
locked
"US State" line
Currently running JTAlertX 2.13.10. The behaviour of the bottom line ("US State :") is inconsistent. If I have previously worked a station (on any band) and I am now working them again that line is po
Currently running JTAlertX 2.13.10. The behaviour of the bottom line ("US State :") is inconsistent. If I have previously worked a station (on any band) and I am now working them again that line is po
|
By
Radio K0HB
· #24982
·
|
|
locked
FT4 on 7047
I’m not on that list, so missed the thread. In the meantime, waiting until the next release is completely UNSAT. If an operator is competent to test FT4, then (we must hope) that they are competent to
I’m not on that list, so missed the thread. In the meantime, waiting until the next release is completely UNSAT. If an operator is competent to test FT4, then (we must hope) that they are competent to
|
By
Radio K0HB
· #24090
·
|
|
locked
FT4 on 7047
The selection of 7047 as a test QRG couldn’t be worse for our relationship with other hams. It is smack-dab on top of the W1AW morse bulletins and code practice at 7047.5. That usage of the QRG goes b
The selection of 7047 as a test QRG couldn’t be worse for our relationship with other hams. It is smack-dab on top of the W1AW morse bulletins and code practice at 7047.5. That usage of the QRG goes b
|
By
Radio K0HB
· #24087
·
|
|
locked
WSJT-X RC5
Sorry you spent so much money on JTAlert, and now it’s all wasted. FT4 is new, just a few days old, and “supporting” programs will not be 100% out of the gate. Go code your own damn solution. 73, de H
Sorry you spent so much money on JTAlert, and now it’s all wasted. FT4 is new, just a few days old, and “supporting” programs will not be 100% out of the gate. Go code your own damn solution. 73, de H
|
By
Radio K0HB
· #24032
·
|
|
locked
Linking WSJT, JT Alert, and Log4OM
Somewhere I saw a tutorial for linking WSJT, JT Alert, and Log4OM to be able to pass QSO data from WSJT (FT8 mode) into my station log (kept on Log4OM). It had to do with UDP port numbers, and similar
Somewhere I saw a tutorial for linking WSJT, JT Alert, and Log4OM to be able to pass QSO data from WSJT (FT8 mode) into my station log (kept on Log4OM). It had to do with UDP port numbers, and similar
|
By
Radio K0HB
· #24002
·
|