Date   

locked Re: WSJT-X multible instances

John P
 

On Sat, Jun 9, 2018 at 04:33 pm, HamApps Support (VK3AMA) wrote:
See the JTAlert Settings, Applications -> WSJT-X section to enable the Rebroadcast setting.
Thanks Laurie! Not sure I'll understand it, but I'll take a look!
 
--
John P.
WA2FZW


locked Re: Distance way off

John
 

Thanks Laurie,

That has to be it, as I was not in contest mode.
Was really funny when one Florida station was 1103 miles away and another one in the next box JTAlert  was 12.300 miles away.

And I did check the WSJT-X grid setting and it was correct, just like the JTAlert one was.

73
John W3ML


locked Re: Alerts - EZ On/Off?

Charles Jessee
 

Hi Laurie,
I was able to go back to a saved config file 7 days ago and found that my changes were saved on close/re-open of JTAlerts. But then if I did a Scan & Rebuild I found that all reverted to Checked again. Is that supposed to happen?
BRET


locked Re: Question about ARRL Grid Chase / Worked B4 flag

HamApps Support (VK3AMA)
 

On 10/06/2018 8:59 PM, Mark Steele wrote:
Good morning all,

I currently have the ARRL Grid Chase option set to on. But I also have the 'Ignore B4 status before this date' set and I move it to the beginning of the month each month. Is that a redundant setting for me (meaning that the ARRL Grid Chase setting does the ignore B4 for me already)?

Best regards,

73, Mark - KD2NOM
Mark,

The ignore B4 status before this date is not needed and the setting is ignored by JTAlert when the Grid Chase is enabled.

See the JTAlert Help File, "Tutorials -> ARRL International Grid Chase 2018" topic for instructions on correct setup.

de Laurie VK3AMA


locked Re: Question about ARRL Grid Chase / Worked B4 flag

Michael Black
 

Yes...that's redundant...you just need to "Scan log and rebuild" at the beginning of month.

de Mike W9MDB


On Sunday, June 10, 2018, 5:59:44 AM CDT, Mark Steele <kd2nom@...> wrote:


Good morning all,

I currently have the ARRL Grid Chase option set to on. But I also have the 'Ignore B4 status before this date' set and I move it to the beginning of the month each month. Is that a redundant setting for me (meaning that the ARRL Grid Chase setting does the ignore B4 for me already)?

Best regards,

73, Mark - KD2NOM
10-10: 77596, FHC: 5930


locked Re: Before mode

Rich McCabe
 

Laurie, for contest purposes.  Yesterday I wanted to work stations for a contest that I had worked before but did not want to have dups for the contest. 

 

What file do you need from LogforOM?

 

Rich

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, June 9, 2018 8:48 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Before mode

 

On 10/06/2018 11:21 AM, Rich McCabe wrote:

The last time I worked this guy below was 5/5/2018


This is just an example but everyone I have worked B4 is still showing up as B4.

 

I doubt it matters but I am logging with LOG4OM

Rich

Rich,
It may be due to you setting the B4 date to todays (UTC) date, I'll need to investigate further.
Please send me direct your Log4OM log file so I can see what is happening your end. Send the file to vk3ama.ham.apps [at] gmail.com

BTW, the Date setting is really designed for those who are happy to work a Station again (so not get the B4) if they haven't been worked for a number of months/years. It was never designed for such short terms, but should still work.

Out of curiosity, why are your setting the Date to such a recent date, what are you trying to achieve?

de Laurie VK3AMA


locked #TIP : Simple taking of screen captures of individual windows, the desktop or arbitrary areas. #TIP

HamApps Support (VK3AMA)
 

If you want to take captures of individual windows, the entire desktop or arbitrary areas of your screen, it is extremely easy using a tool built into Windows since Vista. The Snipping Tool its called.

Screen/Window captures are the preferred method of capturing images for posting to the forum. Taking a digital photo using your cell/mobile phone is not suitable and takes far longer (more steps)  and often produces oversized/slanted images

A couple of simple online tutorials...
https://support.microsoft.com/en-au/help/13776/windows-use-snipping-tool-to-capture-screenshots
https://computertutorflorida.com/2011/10/windows-7-built-in-screenshot-tool/

de Laurie VK3AMA


locked Re: B4 Not Working for Some of Us

HamApps Support (VK3AMA)
 

On 10/06/2018 12:20 PM, David wrote:
You know, I can accept a certain amount of angst from developers as I used to be one myself in a long dead script.  However, I find your comments to be a bit out of line in helping the rest of us understand how to resolve problems that we see.  Nor did I see mention of that fix that in the forums, but frankly there is just too much to read.  I like to use my radio equipment not try to digest the internet.

Thank you for your assistance in any case.

K
Sorry you feel that way. Your original post had as its second line.. "I am offering up proof that this is NOT the case". You were wrong and I was a bit defensive, sorry.

Keeping it short for you...
Turn off the Grid Chase unless you are participating in the Chase then the B4 behaviour your experiencing is valid and correct.

BTW, Grid Chase apparent B4 anomalies have been discussed numerous times within the forum.

Good Luck.
de Laurie VK3AMA


locked Re: B4 Not Working for Some of Us

David <k6dma@...>
 

You know, I can accept a certain amount of angst from developers as I used to be one myself in a long dead script.  However, I find your comments to be a bit out of line in helping the rest of us understand how to resolve problems that we see.  Nor did I see mention of that fix that in the forums, but frankly there is just too much to read.  I like to use my radio equipment not try to digest the internet.

Thank you for your assistance in any case.

K


locked Re: Distance way off

HamApps Support (VK3AMA)
 

On 10/06/2018 12:07 PM, Kevin Utzy wrote:

Probably a function of the VHF contest mode being used this weekend.

73, Kevin, KX4KU

Kevin,

That is likely the case.

It is my understanding (I am open for correction) that when WSJT-X is operating in VHF contest mode, special Grids are used to allow passing of contest exchanges normally not possible within the 13 character restrictions of a free-form message. If a user is using WSJT-X not in contest mode, Grids in the decodes will be all wrong pointing to far-off locations with no land-mass resulting incorrect distances. This would be why WSJT-X is prompting the user to switch to VHF Contest Mode.

de Laurie VK3AMA


locked Re: B4 Not Working for Some of Us

HamApps Support (VK3AMA)
 

On 10/06/2018 11:21 AM, David wrote:
Laurie and company,

I have seen this topic flash by several times with all the comments basically saying that there is something wrong with your logging software - in my case Ham Radio Deluxe, current version.

I am offering up proof that this is NOT the case. 

The two screen shots are showing JT Alert where the check boxes show CO8LY as being working on 18 mhz, but not showing B4.

Originally the log showed that I had worked CO8LY on four separate bands, including 18 mhz.  I did try updating the log entry manually using the tool in HRD.  Nothing really changed of course.  No change in the B4 display (or lack of).

Then I re-worked CO8LY and got the fifth log entry showing him again and now the station shows up as "B4".

OBTW:  WSJT-X did show the station in green as having been worked.

I agree that the station is (probably) not in the B4 database.  Please do not try to tell me that there is something wrong with HRD Logging.

There are those of us who have this problem with certain (seemingly) random stations.  How do we fix it without reworking ever contact.  I haven't actually made a tally of those showing incorrectly, but I'd guess somewhere around 20 to 30 percent, so the number is not all that small.

Any help or ideas.

PS:  I did see something about running an ADIF import, but I see no where to import anything into JT Alert without having some sort of knowledge of MS Access.

PSS:  All programs (except HRD) have been completely deleted and reinstalled at least twice, with reboots.  No change.  All software is at the most recent version(s).

Thank you and 73,
David K6DMA
San Diego, CA, USA

David,

Firstly, get the idea of a B4 database and importing out of your head. There is one, but it doesn't apply to you or anyone else running JTAlert against one of the supported Loggers, it only applies to those NOT using a logger. Your logging to HRD and that is where the B4 checks are done, always has and always will.

Secondly, don't take hires pictures of the different Windows using you mobile phone, take a screen-capture of the window directly (this facility has been part of Windows since the first Windows version (pre win 95)), Google if you don't know how. It is often difficult to view photos that of off-centre and tilted. and if the pictures are too high-res, the Forum software will try and rescale and often make them unreadable.

Thirdly, repeated uninstall and reinstall of multiple software packages is not going to fix your problem and has the potential to break software if care is not taken.

Fourthly, I make no claim there is a problem with HRD with respect to B4 reporting. Hundreds of JTAlert /HRD users have no B4 reporting problems.

Regarding the specific of your apparent B4 inconsistencies.
  • You have your first 17m QSO with C08LY in March 2018 and the second in June 2018 which didn't show the B4. The explanation for this is you have the ARRL Grid chase enabled in JTAlert. The Grid Chase rules allow for working the same Station/Grid every month so JTAlert wont flag the March QSO as a B4 because it is now June and CO8LY can be worked again for Grid Chase credit.

  • After your June logging, he correctly shows as a B4 (as you reported), but come July, he will not. Turn off the Grid Chase unless you are participating in the Chase then the B4 behaviour your experiencing is valid and correct.

de Laurie VK3AMA


locked Re: Distance way off

Kevin Utzy
 

Probably a function of the VHF contest mode being used this weekend.

73, Kevin, KX4KU


On 09-Jun-18 9:43 PM, HamApps Support (VK3AMA) wrote:
On 10/06/2018 11:01 AM, w3ml@... wrote:

All of a sudden with 2.11.3 Build 0000 Build Date 5 June 2018 the distances are showing up several thousand miles away.

Example, a Florida station should be around 903 miles from me, but JTAlert is showing 11.297 miles and keeps asking me if I should be using the VHF contest mode.

Any ideas as to why?  All settings are accurate.

73
John W3ML
John,

The prompt for enabling VHF contest mode is coming from WSJT-X NOT JTAlert and is likely due to the distance calculations within WSJT-X using your Grid you have set in WSJT-X.

Very likely you have an incorrect Grid setup in WSJT-X and this is flowing through to JTAlert, thus the incorrect distances.

de Laurie VK3AMA



locked Re: Before mode

HamApps Support (VK3AMA)
 

On 10/06/2018 11:21 AM, Rich McCabe wrote:

The last time I worked this guy below was 5/5/2018


This is just an example but everyone I have worked B4 is still showing up as B4.

 

I doubt it matters but I am logging with LOG4OM

Rich

Rich,
It may be due to you setting the B4 date to todays (UTC) date, I'll need to investigate further.
Please send me direct your Log4OM log file so I can see what is happening your end. Send the file to vk3ama.ham.apps [at] gmail.com

BTW, the Date setting is really designed for those who are happy to work a Station again (so not get the B4) if they haven't been worked for a number of months/years. It was never designed for such short terms, but should still work.

Out of curiosity, why are your setting the Date to such a recent date, what are you trying to achieve?

de Laurie VK3AMA


locked Re: Distance way off

HamApps Support (VK3AMA)
 

On 10/06/2018 11:01 AM, w3ml@... wrote:

All of a sudden with 2.11.3 Build 0000 Build Date 5 June 2018 the distances are showing up several thousand miles away.

Example, a Florida station should be around 903 miles from me, but JTAlert is showing 11.297 miles and keeps asking me if I should be using the VHF contest mode.

Any ideas as to why?  All settings are accurate.

73
John W3ML
John,

The prompt for enabling VHF contest mode is coming from WSJT-X NOT JTAlert and is likely due to the distance calculations within WSJT-X using your Grid you have set in WSJT-X.

Very likely you have an incorrect Grid setup in WSJT-X and this is flowing through to JTAlert, thus the incorrect distances.

de Laurie VK3AMA


locked Distance way off

John
 

Hello,

All of a sudden with 2.11.3 Build 0000 Build Date 5 June 2018 the distances are showing up several thousand miles away.

Example, a Florida station should be around 903 miles from me, but JTAlert is showing 11.297 miles and keeps asking me if I should be using the VHF contest mode.

Any ideas as to why?  All settings are accurate.

73
John W3ML


locked B4 Not Working for Some of Us

David <k6dma@...>
 

Laurie and company,

I have seen this topic flash by several times with all the comments basically saying that there is something wrong with your logging software - in my case Ham Radio Deluxe, current version.

I am offering up proof that this is NOT the case. 

The two screen shots are showing JT Alert where the check boxes show CO8LY as being working on 18 mhz, but not showing B4.

Originally the log showed that I had worked CO8LY on four separate bands, including 18 mhz.  I did try updating the log entry manually using the tool in HRD.  Nothing really changed of course.  No change in the B4 display (or lack of).

Then I re-worked CO8LY and got the fifth log entry showing him again and now the station shows up as "B4".

OBTW:  WSJT-X did show the station in green as having been worked.

I agree that the station is (probably) not in the B4 database.  Please do not try to tell me that there is something wrong with HRD Logging.

There are those of us who have this problem with certain (seemingly) random stations.  How do we fix it without reworking ever contact.  I haven't actually made a tally of those showing incorrectly, but I'd guess somewhere around 20 to 30 percent, so the number is not all that small.

Any help or ideas.

PS:  I did see something about running an ADIF import, but I see no where to import anything into JT Alert without having some sort of knowledge of MS Access.

PSS:  All programs (except HRD) have been completely deleted and reinstalled at least twice, with reboots.  No change.  All software is at the most recent version(s).

Thank you and 73,
David K6DMA
San Diego, CA, USA


locked Re: Before mode

Rich McCabe
 

Hi Laurie,

 

Well I am not sure what is going on.

 

This is my setting

 

 

 

The last time I worked this guy below was 5/5/2018


This is just an example but everyone I have worked B4 is still showing up as B4.

 

I doubt it matters but I am logging with LOG4OM

 

 

Rich

 

 

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, June 9, 2018 6:36 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Before mode

 

On 10/06/2018 9:20 AM, HamApps Support (VK3AMA) wrote:

if the B4 date of the Callsign is earlier than the current date the Callsign is not flagged as a B4

Correction, that should have been written as "if the B4 date of the Callsign is earlier than the date set in the B4 setting, the Callsign is not flagged as a B4".

de Laurie VK3AMA


locked Re: Before mode

HamApps Support (VK3AMA)
 

On 10/06/2018 9:20 AM, HamApps Support (VK3AMA) wrote:
if the B4 date of the Callsign is earlier than the current date the Callsign is not flagged as a B4
Correction, that should have been written as "if the B4 date of the Callsign is earlier than the date set in the B4 setting, the Callsign is not flagged as a B4".

de Laurie VK3AMA


locked Re: WSJT-X multible instances

HamApps Support (VK3AMA)
 

On 9/06/2018 10:48 PM, John P wrote:
Laurie, any idea when the multicast capability will be available. I discovered this issue when trying to add the DxMaps - DxAggregator program to the mix. As a service to other folks, it would really be nice to be able to report QSOs to the map, but JT-Alert is too valuable a tool to give up.
 
--
John P.
WA2FZW
John,

Unfortunately, not any time soon. This is not a code design limitation but a fundamental limitation in the TCP/UDP functions of the current JTAlert compiler. Those functions don't support the concept of port reuse (non-exclusive port binding) or joining of a multi-cast UDP group.

JTAlert works around the exclusive binding to the UDP port by providing a UDP re-broadcast of any WSJT-X received UDP packet on a different port. See the JTAlert Settings, Applications -> WSJT-X section to enable the Rebroadcast setting.

This rebroadcast has worked very well for applications like GridTraker which were tying to monitor the WSJT-X traffic but couldn't if JTAlert was running, now it simply monitors the JTAlert rebroadcast port.

FWIW, all the above becomes irrelevant with JTAlert V3 (still months away from release) where multicast joining is supported and binding to the UDP port is non-exclusive (this has already been coded and tested).

de Laurie VK3AMA





locked Re: Before mode

HamApps Support (VK3AMA)
 

On 10/06/2018 6:06 AM, Rich McCabe wrote:
If I go to Alerts/Worked B4 and check the box that says Ignore B4 statues before this date and confirm that the date is correct in the box below shouldn't all my contacts not show B4 assuming I have not worked anyone today?  Checking that box does not seem to do anything for me.  I still see B4. Another local ham has same issue but maybe we don't understand the process.

Rich
Rich,

When JTAlert does a B4 check of a Callsign against your Log, the date returned of the most recent log entry (if present) is compared to the date you have set in the Ignore Date setting (if set) and if the B4 date of the Callsign is earlier than the current date the Callsign is not flagged as a B4.

eg. say VK3AMA in your log at 01-Jun-2015, you have the Date set for the Ignore B4 as 01-01-2017  then when you decode VK3AMA today he will not be flagged as a B4 because your QSO with VK3AMA was before 01-01-2017.

All the above applies for normal JTAlert operation, but if you have the Arrl 2018 Grid Chase enabled for Wanted Grid Alerts, then B4 display doesn't follow the above rules due the rules of the Grid Chase. where B4 checks have to consider the current Calendar Month and the on-air grid decoded.

If your in the Grid Chase, turn off the B4 Date setting. If you have enabled the Grid Chase in error, turn it off.

de Laurie VK3AMA

12761 - 12780 of 33231