Date   

locked Re: Error updating Jtalert

FastWeb
 


After further testing I think that the error reported as due to JTAlert instead depends on SportCollector not connecting with wsjt-x since I mistakenly try to start SportCollector before Wsjt-x.
Changing the boot order the JTAlert error does not appear but the SpotCollector connection failure remains. Two Messages received: "SpotCollector not connected WSJT-X not connected" "SC_WSJTX has reported an error; the WSJT-X spot source has been disabled"


Ivan


locked Re: settings - filters

Michael Black
 

You need to ask on the JTDX forum...it is responsible for filtering such things out.

Mike W9MDB




On Friday, March 12, 2021, 05:22:54 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 13/03/2021 6:24 am, Matthias Bellmann wrote:
i am using jtdx for some month, but some days ago jtdx filters dont work.
In register "filters" i can mark "hide messages from continents" and "hide messages from countries" or "show cq messages only" (same with rrr/rr73/73),
but filtering doesn take place. 
All other functions are ok, communication with logger32 via udp, jtaler/logger32 with tcp, loggin etc.
what is my fault? Using 2.2.0-rc155
73 Matthias dk4wd

I don't use JTDX, except for JTAlert testing, so am unable to provide an informed/accurate response, sorry.

If you don't get an answer here from another member of this group try posting this question on the JTDX support group
 https://jtdx.groups.io/g/main.


de Laurie VK3AMA


locked Re: settings - filters

HamApps Support (VK3AMA)
 

On 13/03/2021 6:24 am, Matthias Bellmann wrote:
i am using jtdx for some month, but some days ago jtdx filters dont work.
In register "filters" i can mark "hide messages from continents" and "hide messages from countries" or "show cq messages only" (same with rrr/rr73/73),
but filtering doesn take place. 
All other functions are ok, communication with logger32 via udp, jtaler/logger32 with tcp, loggin etc.
what is my fault? Using 2.2.0-rc155
73 Matthias dk4wd

I don't use JTDX, except for JTAlert testing, so am unable to provide an informed/accurate response, sorry.

If you don't get an answer here from another member of this group try posting this question on the JTDX support group
 https://jtdx.groups.io/g/main.


de Laurie VK3AMA


locked Re: Double Logging Issue

HamApps Support (VK3AMA)
 

On 12/03/2021 3:31 pm, Russ Ravella via groups.io wrote:
The only s/w I have running at this point is: SSDR, DXL. FRStack (which has no logging features), WSJT-X (FT8) and JTAlert.  That's it !  And again, I haven't made any setting changes in any of them.  I'm at a total loss.  Any suggestions would be much appreciated.

Thanks,
Russ KR6W

OK, we need to determine if the duplicate logging instruction is coming from JTAlert. Do the following...
  • Enable JTAlert debug recording, via the settings menu.
  • Log a dummy QSO in WSJT-X so that you get the double logging in DXKeeper.
  • Leave JTAlert running for 3 minutes so that it has time to run the capture of your operating environment.
  • Then use the JTAlert "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis. Include a note of the Callsign logged that produced the double logging and the UTC Time when you logged the QSO.
  • Disable JTAlert debug recording.

Once I get your support request I will be able to identify if JTAlert is the source of the duplicate logging instruction.

de Laurie VK3AMA




locked settings - filters

Matthias Bellmann
 

i am using jtdx for some month, but some days ago jtdx filters dont work.
In register "filters" i can mark "hide messages from continents" and "hide messages from countries" or "show cq messages only" (same with rrr/rr73/73),
but filtering doesn take place. 
All other functions are ok, communication with logger32 via udp, jtaler/logger32 with tcp, loggin etc.
what is my fault? Using 2.2.0-rc155
73 Matthias dk4wd


locked Double Logging Issue

Russ Ravella
 

Hi Laurie,

I believe Dave might have just contacted you about an issue I'm having.  The issue is as follows:

After about 3 weeks away I just fired things up and there were a couple of DXL s/w updates which I installed.  Now, when I complete a WSJT-X QSO and log from JTAlert, I receive several error messages/ notifications as follows:

An error box appears saying:
"No QSOs were uploaded to LoTW",
"no QSOs were processed because some QSOs were duplicates or invalid"

Then a Notepad screen appears titled "LoTWResult.txt" with several lines including:
"Already uploaded QSO surpassed on line 5" and further down,
"Signing aborted.  All QSOs are already uploaded; Aborted", "No records to upload", "Final Status: No QSO written(8)"

Another status box also appears titled "DXKeeper Club Log Upload" which says:
"Upload QSO to Clublog Succeeded: Dupe"

When I click off this later, a second entry for the same QSO is placed in DXKeeper

I checked JTAlert and sure enough there was a newer version which I also installed but it had no effect on the above.  I haven changed any settings in any software, or added or deleted any software since before the issue started.

Dave forwarded a suggestion I think you made that perhaps I had a zombie JTAlert process running with a suggestion I shut down the computer and restart.  I'd actually already done that but I tried it again - no help.  Another thing I tried is shutting down GridTracker which I usually also run via multicast.  I have all its' logging features disabled anyway but I thought I'd try - no help.  The only s/w I have running at this point is: SSDR, DXL. FRStack (which has no logging features), WSJT-X (FT8) and JTAlert.  That's it !  And again, I haven't made any setting changes in any of them.  I'm at a total loss.  Any suggestions would be much appreciated.

Thanks,
Russ KR6W

DXL all current
Win10 Pro 20H2
No third party AV
TQSL V2.5.7
WSJT-X V2.3.0
JTAlert V2.16.17


locked Re: {SPAMFILTER} Re: [HamApps] DX SPOT BEACON REMOVAL

Anthony W. DePrato
 

Joe:
thank you that is what i thought but wanted to make sure. i understand about doing anything about these spots . i will just turn off the spot with - # in their call sign

have a great weekend
73 Tony WA4JQS



Spotting stations that end in "-#' are RBN nodes. You are being spotted
when the digital RBN stations see your CQ and there is nothing you can
do to prevent those spots except *NOT* call CQ.

If you don't want to see RBN spots for digital modes (RTTY, FT8, FT4,
etc.) or CW, in SpotCollector -> Config -> Special Callsigns, *Check*
"Discard spots from spotting station callsigns ending in -#"

73,

... Joe, W4TV
j


locked Re: {SPAMFILTER} Re: [HamApps] DX SPOT BEACON REMOVAL

HamApps Support (VK3AMA)
 

On 12/03/2021 7:22 am, HamApps Support (VK3AMA) via groups.io wrote:
This is the correct group to get an authoritative answer as to how to do that, assuming it is possible.

Correction, that should of read... This DXLab group is the correct group to get an authoritative answer as to how to do that, assuming it is possible.

de Laurie VK3AMA


locked Re: DX SPOT BEACON REMOVAL

Joe Subich, W4TV
 

i have noticed this happen 3 times in the past two days. as i was on
20 mts and got spotted on 40 and 80 mts also. i will be checking
settings again in spot collector and WSJT. for self spotting. i will
see a spot for me right after i send a CQ on FT8 and then i will see
the spotting station change maybe 15 to 20 times in the next 2 mins.
with a # after each call sign.
Spotting stations that end in "-#' are RBN nodes. You are being spotted
when the digital RBN stations see your CQ and there is nothing you can
do to prevent those spots except *NOT* call CQ.

If you don't want to see RBN spots for digital modes (RTTY, FT8, FT4,
etc.) or CW, in SpotCollector -> Config -> Special Callsigns, *Check*
"Discard spots from spotting station callsigns ending in -#"

73,

... Joe, W4TV


On 2021-03-11 11:36 AM, Anthony W. DePrato wrote:
AL:
thank you very much for the kind reply . that  i can understand. i have noticed this happen 3 times in the past two days. as i was on 20 mts and got spotted on 40 and 80 mts also. i will be checking settings again in spot collector and WSJT. for self spotting. i will see a spot for me right after i send a CQ on FT8
and then i will see the spotting station change maybe 15 to 20 times in the next 2 mins. with a # after each call sign. i though it might be a rev beacon at first now i am thinking it could be skimmers . thinking back trying to recall when this started i keep thinking it was after i updated WSJT to the lasterst RC version. so i am going back to check setting again.
Al thank you and Neil for the kind help sadly of the 4 replys i received you two were the only ones with any help and NOT telling me i needed to go QRT or Learn how to use my software.
73 Tony WA4JQS /VP8SSI /3Y0PI/ V31SS
At 10:20 AM 3/11/2021, you wrote:
Tony,
That can happen if the spotting station loss CAT and the radio is no longer on the same band as WSJT.
WSJT will continue to send spots after CAT is lost.

AL, K0VM


On 3/10/2021 3:09 PM, Anthony W. DePrato wrote:
Can anyone tell me why the below is showing up on the dx cluster also i would like to know how to stop this..

YES I am running the latest versions of WSJT and JTALERT.and DXLAB

YES I have all psk beacons and any think i could find that said anything about reverse beacons and broadcasting turned off.

also i never was on 14.080 so why does this false spot show upEmacs!

Thanks for any help
73 Tony WA4JQS


locked Re: {SPAMFILTER} Re: [HamApps] DX SPOT BEACON REMOVAL

HamApps Support (VK3AMA)
 

On 12/03/2021 3:36 am, Anthony W. DePrato wrote:
NOT telling me i needed to go QRT or Learn how to use my software.

73 Tony WA4JQS /VP8SSI /3Y0PI/ V31SS

The go QRT response (from me) was an attempt at levity. Sorry you took it literally.

Your problem is that you don't want to see spots of your Callsign from other FT8 users.

You can't force everyone else to turn off their PSKReporter spotting or Cluster spotting, so your only option is to configure SpotCollector to avoid showing these spots. This is the correct group to get an authoritative answer as to how to do that, assuming it is possible.

de Laurie VK3AMA
(JTAlert author)


locked Re: {SPAMFILTER} Re: [HamApps] DX SPOT BEACON REMOVAL

Anthony W. DePrato
 

AL:
thank you very much for the kind reply . that  i can understand. i have noticed this happen 3 times in the past two days. as i was on 20 mts and got spotted on 40 and 80 mts also. i will be checking settings again in spot collector and WSJT. for self spotting. i will see a spot for me right after i send a CQ on FT8
and then i will see the spotting station change maybe 15 to 20 times in the next 2 mins. with a # after each call sign. i though it might be a rev beacon at first now i am thinking it could be skimmers . thinking back trying to recall when this started i keep thinking it was after i updated WSJT to the lasterst RC version. so i am going back to check setting again.

Al thank you and Neil for the kind help sadly of the 4 replys i received you two were the only ones with any help and NOT telling me i needed to go QRT or Learn how to use my software.

73 Tony WA4JQS /VP8SSI /3Y0PI/ V31SS


At 10:20 AM 3/11/2021, you wrote:
Tony,
That can happen if the spotting station loss CAT and the radio is no longer on the same band as WSJT.
WSJT will continue to send spots after CAT is lost.

AL, K0VM


On 3/10/2021 3:09 PM, Anthony W. DePrato wrote:
Can anyone tell me why the below is showing up on the dx cluster also i would like to know how to stop this..

YES I am running the latest versions of WSJT and JTALERT.and DXLAB

YES I have all psk beacons and any think i could find that said anything about reverse beacons and broadcasting turned off.

also i never was on 14.080 so why does this false spot show upEmacs!

Thanks for any help
73 Tony WA4JQS


[]  Virus-free. www.avg.com


locked Re: DX SPOT BEACON REMOVAL

Anthony W. DePrato
 

Thanks Neil i will check out spot collector.
73 Tony


At 06:46 PM 3/10/2021, you wrote:

That looks like a screen cap from SpotCollector.  Check your SpotCollector settings to see if you're inadvertently spotting yourself somehow.

Neil, KN3ILZ
[]  Virus-free. www.avg.com


locked Re: DX SPOT BEACON REMOVAL

Al Groff
 

Tony,
That can happen if the spotting station loss CAT and the radio is no longer on the same band as WSJT.
WSJT will continue to send spots after CAT is lost.

AL, K0VM


On 3/10/2021 3:09 PM, Anthony W. DePrato wrote:
Can anyone tell me why the below is showing up on the dx cluster also i would like to know how to stop this..

YES I am running the latest versions of WSJT and JTALERT.and DXLAB

YES I have all psk beacons and any think i could find that said anything about reverse beacons and broadcasting turned off.

also i never was on 14.080 so why does this false spot show upEmacs!

Thanks for any help
73 Tony WA4JQS


locked Re: DX SPOT BEACON REMOVAL

HamApps Support (VK3AMA)
 

On 11/03/2021 10:46 am, neil_zampella wrote:

That looks like a screen cap from SpotCollector.  Check your SpotCollector settings to see if you're inadvertently spotting yourself somehow.

Neil, KN3ILZ


Doesn't look like self spotting to me. He was spotted (I assume as column headings are missing) by N8YQX & VE4PER.

If the op doesn't want to be spotted by other stations he needs to go QRT or setup his software (is it SpotCollector?) to not display spots of his Callsign, assuming that is a supported function of the software.

I also don't see how Beacons come into this. I don't see any Beacon callsigns in that image.

de Laurie VK3AMA


locked Re: JT Alert still shows worked B$ stations

HamApps Support (VK3AMA)
 

On 11/03/2021 10:04 am, Tim Davis KJ4DHF via groups.io wrote:
If I worked the station on FT4,FT8,JT9,JT65 they were always blacked out
per the mode I was using at the time. ( I did not need a duplicate qso)

Then you need to tick the "Ignore Mode" checkbox. Your original image showed it was un-ticked.

de Laurie VK3AMA


locked Re: DX SPOT BEACON REMOVAL

neil_zampella
 

That looks like a screen cap from SpotCollector.  Check your SpotCollector settings to see if you're inadvertently spotting yourself somehow.

Neil, KN3ILZ


locked Re: JT Alert still shows worked B$ stations

Tim Davis KJ4DHF
 

Laurie,
Ok I give that a try and see how it goes.
All I want it to do is like in previous versions. It was a great little program when you first started with JT Alert. It has come a long ways over the years.

I had it set so that all Worked B4 stations were blacked out per mode. If I worked the station on FT4,FT8,JT9,JT65 they were always blacked out
per the mode I was using at the time. ( I did not need a duplicate qso) If I had not worked them they would be displayed in the JT Alert window for that particular mode.


locked Re: JT Alert still shows worked B$ stations

Laurie, VK3AMA
 



On 11/03/2021 8:32 am, Laurie, VK3AMA wrote:

On 11/03/2021 8:07 am, Tim Davis KJ4DHF via groups.io wrote:
That did not fix the problem. It looks as if something not reading the logbook after I switch modes. Started great FT8 switched to FT4 still blanking out all the Worked B4 stations. Switched back to FT8 displaying all calls including the Worked B4.

Its rather confusing what your describing from your messages.

Do you want B4 callsigns displayed, yes or no?
  • if yes then don't use the hide B4 filter
  • if no, then use the hide B4 filter.

What are you expecting to see when you change modes from FT8 to FT4 with respect to B4 display. Are you expecting previously worked FT8 callsigns (but not in FT4) to show as a B4, yes or no?
  • If yes then you need to tick the Ignore Mode checkbox under the Worked B4 settings.
  • If no, that is you want to consider Ft4 as separate from FT8 with respect to B4 status, then leave the "Ignore Mode" checkbox unticked.

de Laurie VK3AMA



I neglected to mention, B4 checking is done against your log, one time only for the current JTAlert session with the results stored in a fast memory-based cache. Reading the B4 status from a log is orders-of-magnitude slower than from memory, thus the use of a cache. If you are changing the basis of the B4 checks, like "Ignore Mode" or "Ignore Band" or "Ignore Grid" than the cached status will be wrong, you will need to restart JTAlert. Note: there is NO need to restart JTAlert when you change Mode or Band, it is only needed if you change the criteria for B4 checking that a restart is needed.

de Laurie VK3AMA



locked Re: JT Alert still shows worked B$ stations

Laurie, VK3AMA
 


On 11/03/2021 8:07 am, Tim Davis KJ4DHF via groups.io wrote:
That did not fix the problem. It looks as if something not reading the logbook after I switch modes. Started great FT8 switched to FT4 still blanking out all the Worked B4 stations. Switched back to FT8 displaying all calls including the Worked B4.

Its rather confusing what your describing from your messages.

Do you want B4 callsigns displayed, yes or no?
  • if yes then don't use the hide B4 filter
  • if no, then use the hide B4 filter.

What are you expecting to see when you change modes from FT8 to FT4 with respect to B4 display. Are you expecting previously worked FT8 callsigns (but not in FT4) to show as a B4, yes or no?
  • If yes then you need to tick the Ignore Mode checkbox under the Worked B4 settings.
  • If no, that is you want to consider Ft4 as separate from FT8 with respect to B4 status, then leave the "Ignore Mode" checkbox unticked.

de Laurie VK3AMA




locked Re: JT Alert still shows worked B$ stations

Laurie, VK3AMA
 

On 11/03/2021 8:16 am, Herschel Hall wrote:
Have you ran the rebuild alert database feature ?
WA9KIA
That wont help. The Alert database rebuild does not affect B4 reporting. B4s reporting comes directly from log lockups.

de Laurie VK3AMA

3001 - 3020 of 36363