Date   

locked Re: JTAlert alternate gui display

HamApps Support (VK3AMA)
 

On 16/03/2021 7:35 am, bill@... wrote:
Can anyone tell me how to toggle between the full-screen display with all functions and the reduced display which only displays calls?

Probably something simple but not documented that I could find.

tnx K2PAA bill

JTAlert has never offered a full-screen display. Its size is hard-coded and only adjusts (vertically) if additional views are enable , like additional Callsign display rows, the Log Fields and the Confirmed Band display. Visibility of all these is controlled under the "View" menu of JTAlert.

de Laurie VK3AMA


locked Re: "Any Digital Mode" and Wanted Zone

HamApps Support (VK3AMA)
 

On 14/03/2021 1:57 pm, Joe Subich, W4TV wrote:
I think there is an error in "Any Digital Mode" in Wanted Zones.

It appears that "Any Digital Mode" includes RTTY.  However, the
rules for CQ WAZ *exclude* RTTY from "Digital" (there is a separate
award for RTTY).

I noticed DXLab/SpotCollector calling out FT8 spots from my own
JTAlert feed on 30 meters but no alerts from JTAlert.  I tracked
it down (apparently) to a RTTY confirmation on that band.

73,

   ... Joe, W4TV

Joe,

The "Any Digital Mode" tracking does exclude RTTY if the required checkbox is enabled for the CQ Zone Alert under the "Rebuild Alert Database" section of the Settings window.

   

This has been in place for many years now. If I recall correctly this was first suggested by yourself.

I just now ran some tests. and cannot fault the behavior.
  • With an empty log, I ran the rebuild and all CQ zones were correctly set as needed.
  • A single RTTY QSO was added to the log and the rebuild rerun (without the ignore checkbox ticked). The zone was correctly flagged as no longer need under the "Any Mode" & "Any Digital Mode" sections of the CQ Alert.
  • The JTAlert setting for ignoring RTTY was enabled and the rebuild rerun. The "Any Digital Mode" section correctly changed accounting for the changed setting with the zone being flagged as needed.

My only thoughts as to why JTAlert is not Alerting on a CQ zone that DXLab is is that JTAlert is looking at a different filtered view of your Log compared to what DXLab is using. While the Log file may be the same, if you have multiple myQTH ID available in DXKeeper, you need to ensure that JTAlert is set to use myQTH IDs similar to DXLab. If you have no myQTH IDs set in JTAlert than the entire log is used for the rebuild.

Assuming you have the "Ignore RTTY" checkbox ticked, a search your log will likely uncover a digital mode QSO (not RTTY) for the Band that JTAlert did not alert on.

de Laurie VK3AMA


locked Re: Start problem Subscript used on non-accessible variable

Frank IZ7AUH
 

thank you for your answer, I apologize for the delay in my reply, this error does not appear often, I wish I could solve it and I am aware that it is not a JTALERT error I am looking for a solution and I update you on this, thanks, I hope one day  you can also support MSHV other nice software

IZ7AUH 


On Wed, Mar 3, 2021 at 03:57 PM, HamApps Support (VK3AMA) wrote:

This is a new type of error. I don't recall ever seeing this specific error reported.
The line number referenced is within the block of code that gets a list of running processes on the PC in order to find the wsjt-x processes and assign the JTAlert instance to the appropriate wsjtx instance (based on how long the wsjtx process has been running). This code has not changed for many years now, so I am reasonably confident the error is not caused by a coding error. Deleting files in the users appdata directory will have no effect as this block of code doesn't access any files.

My best guess is that your PC protection software is interfering. You may need to take steps to mark JTAlert and its files/directories as safe.


locked JTAlert alternate gui display

bill@...
 

Can anyone tell me how to toggle between the full-screen display with all functions and the reduced display which only displays calls?

Probably something simple but not documented that I could find.

tnx K2PAA bill


locked Re: DX Atlas

Dave Garber
 

I was kind of wondering what fhis had to do with hamapps or dxatlas


On Mon., Mar. 15, 2021, 2:38 p.m. Larry Banks via groups.io, <larryb.w1dyj=verizon.net@groups.io> wrote:
I assume you were discussing DXMaps.

73 -- Larry -- W1DYJ

 
From: Craig
Sent: Monday, March 15, 2021 14:07
Subject: Re: [HamApps] DX Atlas
 
Hi Larry - where is that specific  "Select Options" located? Which App?
Thanks,

Craig
NZ4CW


locked Re: DX Atlas

Larry Banks
 

I assume you were discussing DXMaps.

73 -- Larry -- W1DYJ

 

From: Craig
Sent: Monday, March 15, 2021 14:07
Subject: Re: [HamApps] DX Atlas
 
Hi Larry - where is that specific  "Select Options" located? Which App?
Thanks,

Craig
NZ4CW


locked Re: DX Atlas

Craig
 

Hi Larry - where is that specific  "Select Options" located? Which App?
Thanks,

Craig
NZ4CW


locked Re: DX Atlas

Larry Banks
 

Hi Craig, (call?),
 
Do you have Select Options >> Only last 15 minutes selected?

73 -- Larry -- W1DYJ

 
 
 

From: Craig
Sent: Monday, March 15, 2021 13:48
Subject: [HamApps] DX Atlas
 
The DX Atlas map is showing a huge number of QSO paths as backdrop to a current plot that I have selected from DXKeeper.  How can I remove the large number of prior QSO's that are showing on the map?  Selecting Plot on DXKeeper plots the current QSO with all of the others showing.


locked Re: Double Logging Issue

Duncan Campbell
 

I found that if I have the JTAlert sending my spots to spot collector AND having JTAlert doing my logging to DXKeeper, I also got the double logging.  I turned off the spot collector dump and it corrected the problem for me.

73 de duncan, KF6ILA


locked Re: problem decoding with Flex 6400M

JoAnn Donaldson <joannplano2005@...>
 

The 6400M front panel is Maestro. So I turned off SmartSDR, switched DAX Control to Maestro, SmartSDR CAT to Maestro and WSJT started decoding. I have now made 1/2 dozen contacts. i am going to report this problem to Flex Support Team.

JoAnn Donaldson
AB8YZ

On Sunday, March 14, 2021, 6:38:51 PM CDT, Bill Barrett <billbarrett174@...> wrote:


Open a browser and type in "Time.IS" in the url

On Sun, Mar 14, 2021 at 3:30 PM AB8WD-Willie via groups.io <AB8WD=yahoo.com@groups.io> wrote:
check time sync on pc to time is on internet



--
Bill Barrett
352-437-4758


locked Re: problem decoding with Flex 6400M

Bill Barrett
 

Open a browser and type in "Time.IS" in the url


On Sun, Mar 14, 2021 at 3:30 PM AB8WD-Willie via groups.io <AB8WD=yahoo.com@groups.io> wrote:
check time sync on pc to time is on internet



--
Bill Barrett
352-437-4758


locked Re: problem decoding with Flex 6400M

Craig
 

Make sure your DAX setting align in your slice and DAX. C


On Mar 14, 2021, at 2:50 PM, JoAnn Donaldson via groups.io <joannplano2005@...> wrote:

I got WSJT-X to interface with my Flex 6400M. The Cat Test Button turns Green and the PTT Button turns Red and the Radio goes into Transmit. I have Incoming Audio set to RX1 and outgoing audio set to TX. I see signals on the WSJT-X waterfall but nothing gets decoded.


locked Re: problem decoding with Flex 6400M

AB8WD-Willie
 

check time sync on pc to time is on internet


locked problem decoding with Flex 6400M

JoAnn Donaldson <joannplano2005@...>
 

I got WSJT-X to interface with my Flex 6400M. The Cat Test Button turns Green and the PTT Button turns Red and the Radio goes into Transmit. I have Incoming Audio set to RX1 and outgoing audio set to TX. I see signals on the WSJT-X waterfall but nothing gets decoded.


locked Re: Double Logging Issue

Laurie, VK3AMA
 

On 14/03/2021 3:29 pm, Russ Ravella via groups.io wrote:
Since sending the request for help, I’ve had to travel to attend to a family issue.  I brought my Flex Maestro and computer to attempt to work the problem remotely and amazing, it doesn’t seem to be happening here.  I’m running the same s/w on the same computer as before, just remotely.  It would seem that either running it remotely breaks whatever the double log condition is, it is intermittent or whatever changed has changed back.

If the issue returns when I get back, I’ll excuse these instructions and send you the files.  Thanks again for you help !
Russ KR6W
Interesting. Sounds like something on your home network may be repeating the TCP instructions that JTAlert is sending to DXKeeper. If that is the case I would expect the problem to resurface once you return home.

de Laurie VK3AMA


locked Re: Disappearing B4's in FT4

HamApps Support (VK3AMA)
 

On 14/03/2021 3:48 pm, Richard Preece wrote:
I have had a good search and can't seem to find reference to my issue but apologies if it's been covered already. I have never had any issues with B4 until I started using FT4, if I make and log a contact it correctly shows as B4, if I then change band and come back the B4 tag disappears. This only happens with Ft4, no other mode. I'm logging with HRD and have latest versions of JT Alert and WSJTX running. All the solutions that have been suggested to me would affect other modes too such as rebuild log, like I said they are all fine.

Thanks

Rich

What version of HRD?

Broken FT4 behavior suggests either an old HRD version, pre 6.7.0.269, or a HRD Log that has not been updated to be ADIF 3.1 compliant.
If your HRD log is ADIF 3.1 compliant (has been upgraded using  the HRD instructions) than likely you have not told JTAlert that the Log has been made compliant. See the JTAlert Help File, "HRD 6.7.0.269, JTAlert Settings" topic at the root level.

de Laurie VK3AMA


locked Re: Disappearing B4's in FT4

neil_zampella
 
Edited

Rich,

and you have 'ignore band' checked or unchecked ?   What about 'ignore mode' ??   

If ignore band is checked, uncheck it.   This 'should' restore B4 by band.   How about ignore mode?   I'm sure you don't want to do that during normal operations.

If that doesn't work, I'd use the 'CONTACT SUPPORT' link on the HELP menu so Laurie will get the JT-Alert files and see what's going on.

Neil, KN3ILZ


locked Disappearing B4's in FT4

Richard Preece
 

Hi

I have had a good search and can't seem to find reference to my issue but apologies if it's been covered already. I have never had any issues with B4 until I started using FT4, if I make and log a contact it correctly shows as B4, if I then change band and come back the B4 tag disappears. This only happens with Ft4, no other mode. I'm logging with HRD and have latest versions of JT Alert and WSJTX running. All the solutions that have been suggested to me would affect other modes too such as rebuild log, like I said they are all fine.

Thanks

Rich


locked Re: Double Logging Issue

Russ Ravella
 

Hi Laurie,

Thanks for the help - much appreciated !

Since sending the request for help, I’ve had to travel to attend to a family issue.  I brought my Flex Maestro and computer to attempt to work the problem remotely and amazing, it doesn’t seem to be happening here.  I’m running the same s/w on the same computer as before, just remotely.  It would seem that either running it remotely breaks whatever the double log condition is, it is intermittent or whatever changed has changed back.

If the issue returns when I get back, I’ll excuse these instructions and send you the files.  Thanks again for you help !
Russ KR6W


On Mar 12, 2021, at 2:58 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

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 "Any Digital Mode" and Wanted Zone

Joe Subich, W4TV
 

Laurie,

I think there is an error in "Any Digital Mode" in Wanted Zones.

It appears that "Any Digital Mode" includes RTTY. However, the
rules for CQ WAZ *exclude* RTTY from "Digital" (there is a separate
award for RTTY).

I noticed DXLab/SpotCollector calling out FT8 spots from my own
JTAlert feed on 30 meters but no alerts from JTAlert. I tracked
it down (apparently) to a RTTY confirmation on that band.

73,

... Joe, W4TV

2981 - 3000 of 36363