|
locked
Time sync error
Hummm, it was already checked and set for a threshold of 1.5. I changed the colors and left it turned on I also turned off the parameter directly below it: Highlight Signal dB Level. 73, Bill "Setting
Hummm, it was already checked and set for a threshold of 1.5. I changed the colors and left it turned on I also turned off the parameter directly below it: Highlight Signal dB Level. 73, Bill "Setting
|
By
Bill - AA4M
· #28341
·
|
|
locked
Time sync error
I brought up the decode history but did not see how to turn on the DT difference alert. I checked the docs which told me to hover over the DT field, which did not resolve my problem. This is with vers
I brought up the decode history but did not see how to turn on the DT difference alert. I checked the docs which told me to hover over the DT field, which did not resolve my problem. This is with vers
|
By
Bill - AA4M
· #28338
·
|
|
locked
Time sync error
Rats, that was a VERY useful item for me. Do you have any idea why it was removed? 73, Bill AA4M
Rats, that was a VERY useful item for me. Do you have any idea why it was removed? 73, Bill AA4M
|
By
Bill - AA4M
· #28335
·
|
|
locked
Time sync error
It's not there, unless it is there and I don't recognize the phrasing of the option. 73, Bill
It's not there, unless it is there and I don't recognize the phrasing of the option. 73, Bill
|
By
Bill - AA4M
· #28334
·
|
|
locked
Time sync error
At one time if a station's time was 1.5 or more seconds out of sync from mine, the error was highlighted. That is no longer happening and I've dug through settings and alerts but cannot see where to t
At one time if a station's time was 1.5 or more seconds out of sync from mine, the error was highlighted. That is no longer happening and I've dug through settings and alerts but cannot see where to t
|
By
Bill - AA4M
· #28326
·
|
|
locked
Needed AK & HI states not flagged
I've searched but did not see any posts discussing this problem. I have HI and AK marked as needed on 15M FT8 but I've seen these states on the band and they are not being flagged. So I tested against
I've searched but did not see any posts discussing this problem. I have HI and AK marked as needed on 15M FT8 but I've seen these states on the band and they are not being flagged. So I tested against
|
By
Bill - AA4M
· #28246
·
|
|
locked
Worked B4
Is there any way to remove the B4 QSO's from the grid but still leave them highlighted in WSJT-X? 73, Bill AA4M
Is there any way to remove the B4 QSO's from the grid but still leave them highlighted in WSJT-X? 73, Bill AA4M
|
By
Bill - AA4M
· #27819
·
|
|
locked
Alaska
The grids are all there. 73, Bill AA4M
The grids are all there. 73, Bill AA4M
|
By
Bill - AA4M
· #27789
·
|
|
locked
Alaska
Just the same as yours: I reinstalled 2.15.8 which solved the problem. BTW - I'm a retired computer programmer - I know what you're going through, hi! 73, Bill AA4M
Just the same as yours: I reinstalled 2.15.8 which solved the problem. BTW - I'm a retired computer programmer - I know what you're going through, hi! 73, Bill AA4M
|
By
Bill - AA4M
· #27786
·
|
|
locked
Audio Error?
That worked, thanks Laurie! 73, Bill AA4M
That worked, thanks Laurie! 73, Bill AA4M
|
By
Bill - AA4M
· #27782
·
|
|
locked
Alaska
OK, I just worked a JA who was calling CQ. My QSO was successfully logged into DXKeeper. Then the same JA popped up again calling CQ and was NOT shown as B4. I closed JTAlert and WSJT-X, restarted the
OK, I just worked a JA who was calling CQ. My QSO was successfully logged into DXKeeper. Then the same JA popped up again calling CQ and was NOT shown as B4. I closed JTAlert and WSJT-X, restarted the
|
By
Bill - AA4M
· #27781
·
|
|
locked
Alaska
DXLab's DXKeeper is my logger. JTAlert successfully sent both Alaska QSO's to my logger. 73, Bill
DXLab's DXKeeper is my logger. JTAlert successfully sent both Alaska QSO's to my logger. 73, Bill
|
By
Bill - AA4M
· #27768
·
|
|
locked
Alaska
I neglected to mention that I had just installed 2.15.9. So after reading Ron's message, I rebooted but both Alaskans had left the band. 73, Bill
I neglected to mention that I had just installed 2.15.9. So after reading Ron's message, I rebooted but both Alaskans had left the band. 73, Bill
|
By
Bill - AA4M
· #27765
·
|
|
locked
Alaska
I don't understand your question! Maybe if I re-phrase my question. When JTAlert sees a call outside of CONUS, it colors the call red with a yellow background. When I work these stations, JTAlert then
I don't understand your question! Maybe if I re-phrase my question. When JTAlert sees a call outside of CONUS, it colors the call red with a yellow background. When I work these stations, JTAlert then
|
By
Bill - AA4M
· #27762
·
|
|
locked
Audio Error?
I installed the virtual cable, rebooted, then assigned Windows to my usual sound driver and WSJT-X to its CODEC driver. The good news is that I now have Windows sounds when working FT8, but the bad ne
I installed the virtual cable, rebooted, then assigned Windows to my usual sound driver and WSJT-X to its CODEC driver. The good news is that I now have Windows sounds when working FT8, but the bad ne
|
By
Bill - AA4M
· #27761
·
|
|
locked
Alaska
I just worked 2 different Alaskan stations on 17M FT8, but they continue to be displayed in my NOT "Worked-B4" color scheme. All others on the band seem to be identified OK by JTAlert. What does the p
I just worked 2 different Alaskan stations on 17M FT8, but they continue to be displayed in my NOT "Worked-B4" color scheme. All others on the band seem to be identified OK by JTAlert. What does the p
|
By
Bill - AA4M
· #27757
·
|
|
locked
Audio Error?
Every time I start a JTAlert / WSJT-X session, I get this message: Because of hearing problems, I have audio turned off in JTAlert, so why must I see this error message over and over and over . . . FW
Every time I start a JTAlert / WSJT-X session, I get this message: Because of hearing problems, I have audio turned off in JTAlert, so why must I see this error message over and over and over . . . FW
|
By
Bill - AA4M
· #27665
·
|
|
locked
Message dates
I just received a message through JTAlert and I responded. Then I noticed both were dated 2019-13-05 . . . the 13th month of 2019! An easy fix, I'm sure. 73, Bill - AA4M Tucson, AZ
I just received a message through JTAlert and I responded. Then I noticed both were dated 2019-13-05 . . . the 13th month of 2019! An easy fix, I'm sure. 73, Bill - AA4M Tucson, AZ
|
By
Bill - AA4M
· #27103
·
|
|
locked
B4 not all tagged
Hello Laurie, Yes, I'm talking about the WSJT-X display. P49X is showing as having 3 signals on a band but only 1 of these is identified with my color scheme (black text, red background) as "B4". Actu
Hello Laurie, Yes, I'm talking about the WSJT-X display. P49X is showing as having 3 signals on a band but only 1 of these is identified with my color scheme (black text, red background) as "B4". Actu
|
By
Bill - AA4M
· #27093
·
|
|
locked
B4 not all tagged
Right now P49X is on 40M calling CQ in 3 spots. I've worked the station on this band, but only 1 of their 3 signals is being tagged as "B4". Is this as intended or is it an oversight. FWIW, I consider
Right now P49X is on 40M calling CQ in 3 spots. I've worked the station on this band, but only 1 of their 3 signals is being tagged as "B4". Is this as intended or is it an oversight. FWIW, I consider
|
By
Bill - AA4M
· #27050
·
|