Date   

locked Re: Field Day Operation

Larry <larry@...>
 

N3FJP has updated his field day program. I will use that. WB2UFO


On May 31, 2020 7:54:26 PM CDT, Marlo Montanaro - KA2IRQ <ka2irq@...> wrote:

So, I'm planning on using FT8/FT4 for Field Day, along with JTAlert.

Is there any special set up?  My normal logging program is ACLog.  I'm planning on switching to the Field Day ACLog program.  As long as that is what's running while WSJT-X and JTAlert are both running will it all be seamless, or do I need to do anything special?

Thanks,

Marlo- KA2IRQ


--
Larry WB2UFO


locked Re: Worked B4 sometimes not working

HamApps Support (VK3AMA)
 

On 31/05/2020 12:53 am, Tony Dixon G4CJC wrote:
I seem to have the same problem, sometimes.
Using WSJT-X2.2.0 -rc3, JTAlert 2.16.6, W10 64bit with all updates current. The attached snip is of receiving FT4, EA1A having worked on FT8 with mode ignored. I have not researched this extensively but will make more note of seeming anomalies. Clearing the B4 cache does not seem to make any difference. Can I help in any way?
Cheers
Tony G4CJC
Tony,

Your screen-grab shows WSJT-X not showing the JTAlert coloring, but you didn't include an image of what JTAlert was displaying. Was JTAlert correctly showing the coloring and it is only WSJT-X that is not?

de Laurie VK3AMA


locked Re: Worked B4 sometimes not working

HamApps Support (VK3AMA)
 

On 31/05/2020 5:28 am, Paul AC9O wrote:
Can't say for sure but the problem seems to go away when there aren't too many decodes, less than 7 or 8 for example. 

73
Paul, AC9O
I wonder if WSJT-X is ignoring or not receiving UDP coloring messages when it is busy? Perhaps the colors not being displayed are for decodes received in an earlier decode pass and WSJT-X at the time is busy with the new decode pass. This is speculation as I don't know how WSJT-X is working internally.

de Laurie VK3AMA


locked Re: Worked B4 sometimes not working

HamApps Support (VK3AMA)
 

On 31/05/2020 1:43 am, Paul AC9O wrote:
Came across another, perhaps related, alert issue. Note that K1NOX properly alerted as a new state, etc., but is not highlighed in the list above. Also WQ1H is alerted on prefix, but not highlighted above.

Thanks and 73
Paul, AC9O
This is starting to look like a problem within WSJT-X release candidates. I do know that the new 2.2.0 release candidates included internal changes involving decode coloring. I am only guessing that may be the problem as I can't see how JTAlert is not sending the coloring instructions as they are always sent immediately after JTAlert colors the callsign in its own display.

de Laurie VK3AMA


locked Re: Worked B4 sometimes not working

HamApps Support (VK3AMA)
 

On 31/05/2020 7:04 pm, Norbert Graf - DD3KF wrote:

 

unfortunately I have an issue with your very useful program JTAlert.

 

My working environment:

- Windows 10, 64 bit

- WSJT-X 2.2.0 RC3

- JTAlert 2.16.6

- HRD Log 6.7.0.277, logging via JTAlert.

 

Problem:

- Stations logged and worked B4 are correctly displayed in JTAlert.

- Unfortunately, the information worked B4 randomly is not displayed in the WSJT-X Band Activity window.

- Occasionally, this indicator is missing for a station , although it was displayed correctly in other slots.

- I have cleared the B4 cache. This will not cause any changes.

 

I include a screen shot of a typical situation. Pse see CT3MD.

 

What can I do?

 

TU for your help.

 

73!

 

______________

Norbert Graf

D D 3 K F


Norbet,

The lack of B4 coloring in WSJT-X when the corresponding Callsign in JTAlert does get colored is very likely an issue within WSJT-X or a disruption to the coloring UDP message sent from JTAlert to WSJT-X. I do know that the new 2.2.0 release candidates included internal changes involving decode coloring. I am only guessing that may be the problem as I can't see how JTAlert is not sending the instruction as it is always sent immediately after JTAlert colors the callsign in its own display.

de Laurie VK3AMA


locked Re: Add ARRL Sections

HamApps Support (VK3AMA)
 

On 1/06/2020 3:30 am, Thomas Webb wrote:
Any potential to add ARRL Sections to the 'Wanted XXX' listings?

Tom WA9AFM/5

Very unlikely unless there is demand for such an Alert AND there is a reliable way to determine ARRL Section from a Callsign (I don't think such an animal exists, but I am willing to be educated).

de Laurie VK3AMA


locked Re: Field Day Operation

HamApps Support (VK3AMA)
 

On 1/06/2020 10:54 am, Marlo Montanaro - KA2IRQ wrote:

So, I'm planning on using FT8/FT4 for Field Day, along with JTAlert.

Is there any special set up?  My normal logging program is ACLog.  I'm planning on switching to the Field Day ACLog program.  As long as that is what's running while WSJT-X and JTAlert are both running will it all be seamless, or do I need to do anything special?

Thanks,

Marlo- KA2IRQ

Marlo,

The only thing special you need to do is read the JTAlert help file and follow the setup instructions. See the "Tutorials -> N3FJP Contest Logs Logging" help topic.

FD setup is very simple, only made difficult by users who fail to read or follow the documented instructions (I have lost count of how many times that has happened).

I also strongly suggest you don't wait until the event day to get this setup and working.

de Laurie VK3AMA



locked Field Day Operation

Marlo Montanaro - KA2IRQ
 

So, I'm planning on using FT8/FT4 for Field Day, along with JTAlert.

Is there any special set up?  My normal logging program is ACLog.  I'm planning on switching to the Field Day ACLog program.  As long as that is what's running while WSJT-X and JTAlert are both running will it all be seamless, or do I need to do anything special?

Thanks,

Marlo- KA2IRQ


locked Add ARRL Sections

Thomas Webb
 

Any potential to add ARRL Sections to the 'Wanted XXX' listings?

Tom WA9AFM/5


locked Re: Worked B4 sometimes not working

Paul A. Ramey
 

I am running the following.

6 core CPU, WIN10. N4PY SW, HRD for logging and WSJT-X and JTalert all current ver.

I operate FT8 and MSK144 most of the time.

While working openings on 6M FT8 I sometimes will work and log a station and do not get a B4 when I see them again.

They are in my log and in some cases already confirmed via LOTW.

gWhen I see them again I click on them like I am going to work them again. I then stop the TX and just log them again. When they are added to my log I just delete the entry. Then the B4 works like it should.

I do not see this very often but I do see it. To me it is more like a bump in the road, not a bug.

-- 
Paul Ramey
WG0G
Those who would give up essential liberty, to purchase a little temporary safety, deserve neither liberty nor safety.


locked Re: Worked B4 sometimes not working

g4wjs
 

Neil,
 
no, but JTAlert does and in this case it appears not to have done some despite it highlighting other callsigns in the WSJT-X Band Activity window.

On 31/05/2020 12:27, neil_zampella wrote:

Paul,

That is not a JT-Alert issue.    WSJT-X does not highlight any decodes unless its a CQ call. 

 

Neil, KN3ILZ

On Sat, May 30, 2020 at 11:43 AM, Paul AC9O wrote:

Hi Laurie,

Came across another, perhaps related, alert issue. Note that K1NOX properly alerted as a new state, etc., but is not highlighed in the list above. Also WQ1H is alerted on prefix, but not highlighted above.

Thanks and 73
Paul, AC9O



--
73
Bill
G4WJS.


locked Re: Worked B4 sometimes not working

neil_zampella
 

Paul,

That is not a JT-Alert issue.    WSJT-X does not highlight any decodes unless its a CQ call. 

 

Neil, KN3ILZ


On Sat, May 30, 2020 at 11:43 AM, Paul AC9O wrote:

Hi Laurie,

Came across another, perhaps related, alert issue. Note that K1NOX properly alerted as a new state, etc., but is not highlighed in the list above. Also WQ1H is alerted on prefix, but not highlighted above.

Thanks and 73
Paul, AC9O


locked JTAlert two instance, two two different resended ports

Robert, SP8SN
 

Hallo. I have some problem. Two instances work well here. Everything works as it should. On the desktop I have two shortcuts with the addition of "--rig-name = ......". However, I have a problem setting two different ports in the "Resend WSJT-X UDP package". I need 2334 on one transceiver and 2335 on the other. I use them for the WSJTDXAggregator application. Currently both instances use 2335. Unstable WSJTDXAggregator is not working properly and does not send spots to DXmap. He receives mixed packages simultaneously from both tracivers. The second instance has unavailable settings window. Is there any possibility to change the config of the second instance in JTAlert? I tried to use "= callsign ..." but giving a parameter other than my callsign here is not suitable for login and spots etc.
Greetings, Robert SP8SN


--
Robert, SP8SN


locked Worked B4 sometimes not working

Norbert Graf - DD3KF
 

Hello, Laurie,

 

unfortunately I have an issue with your very useful program JTAlert.

 

My working environment:

- Windows 10, 64 bit

- WSJT-X 2.2.0 RC3

- JTAlert 2.16.6

- HRD Log 6.7.0.277, logging via JTAlert.

 

Problem:

- Stations logged and worked B4 are correctly displayed in JTAlert.

- Unfortunately, the information worked B4 randomly is not displayed in the WSJT-X Band Activity window.

- Occasionally, this indicator is missing for a station , although it was displayed correctly in other slots.

- I have cleared the B4 cache. This will not cause any changes.

 

I include a screen shot of a typical situation. Pse see CT3MD.

 

What can I do?

 

TU for your help.

 

73!

 

______________

Norbert Graf

D D 3 K F

 


locked Re: Worked B4 Not Working

HamApps Support (VK3AMA)
 

On 31/05/2020 7:46 am, Charles Ristorcelli wrote:

Here is the architecture.

Transceiver YAESU FT-5000MPDX

Intel I9 processor; 16 GB RAM; 1 TB Hard drive

Windows 10 64 bit;   Ham Radio Deluxe V. 6.7.0.269 Release 6.7.0.269;   WSJT-X V 2.100068f9 ;  JT Alert V 2.16.6

The issue I have is that JT Alert does not show Worked Before status, whether I worked the contact last week, or worked it immediately and then the staion continued active but was not so shown.

All the software versions prior to the recent JT Alert upgrade showed the same issue starting about 1 month ago.

The issue continues with JT Alert Version 2.6.16

Looking forward to VK3AMA assist.

73 de NN3V

A month or so ago, HRD changed their log to be ADIF 3.1 compliant with respect to FT4 QSOs. JTAlert released 2.16.4 to accommodate those changes with the following in the Release notes...
  Fixes:

    - HRD 6.7.0.269: All JTAlert FT4 functionality broken, B4 checks, Logging
       confirmations, Log scanning and Callsign QSO History when run against
       HRD 6.7.0.269 with an updated adif 3.1 compliant log.
       See JTAlert help file, "HRD 6.7.0.269, JTAlert settings" topic.

A quick look on HamSpots shows that your primarily running FT4. If you upgraded your HRD Log FT4 QSOs but didn't also update the JTAlert Settings telling it your log is now FT4 compliant than broken FT4 B4 reporting will be the result (as well as some other broken functionality).

See the JTAlert Help File,
"HRD 6.7.0.269, JTAlert settings" topic for the simple changes (along with pictures) needed to be made to JTAlert.

de Laurie VK3AMA


locked Re: New release malfunction

HamApps Support (VK3AMA)
 

On 31/05/2020 4:52 am, wsrmd@... wrote:
I downloaded the new release 2.16.6 today, and it now freezes and no longer displays callsigns once it logs a QSO.  I have to exit the program and the restart it, at which time it works for a few minutes and then quits again.  Again if I relaunch it will work for a while and then quit displaying!!! What is going on?  Help!!  do I need to go back to an older version?

OM (Calls?, Name?)

First, please sign your messages with your Call and Name.

Is this with WSJT-X or JTDX and what version?

If it is WSJT-X and your testing the new 2.2.0 make sure your using the latest rc3.

If it is WSJT-X and not the new 2.2.0 rc, make sure your running the latest General Release which is 2.1.2

de Laurie VK3AMA


locked Worked B4 Not Working

Charles Ristorcelli
 

I posted this issue before.

The reply to my post was that I be more specific on the software I am using.

OK

Here is the architecture.

Transceiver YAESU FT-5000MPDX

Intel I9 processor; 16 GB RAM; 1 TB Hard drive

Windows 10 64 bit;   Ham Radio Deluxe V. 6.7.0.269 Release 6.7.0.269;   WSJT-X V 2.100068f9 ;  JT Alert V 2.16.6

The issue I have is that JT Alert does not show Worked Before status, whether I worked the contact last week, or worked it immediately and then the staion continued active but was not so shown.

All the software versions prior to the recent JT Alert upgrade showed the same issue starting about 1 month ago.

The issue continues with JT Alert Version 2.6.16

Looking forward to VK3AMA assist.

73 de NN3V


locked New release malfunction

wsrmd@...
 

I downloaded the new release 2.16.6 today, and it now freezes and no longer displays callsigns once it logs a QSO.  I have to exit the program and the restart it, at which time it works for a few minutes and then quits again.  Again if I relaunch it will work for a while and then quit displaying!!! What is going on?  Help!!  do I need to go back to an older version?


locked Re: Worked B4 sometimes not working

Paul AC9O
 

Hi Laurie,

I have a couple more observations...

I added some of the calls to the ignore list, and that works ok.

Can't say for sure but the problem seems to go away when there aren't too many decodes, less than 7 or 8 for example. 

73
Paul, AC9O


locked Re: Worked B4 sometimes not working

Paul AC9O
 
Edited

Hi Laurie,

Came across another, perhaps related, alert issue. Note that K1NOX properly alerted as a new state, etc., but is not highlighed in the list above. Also WQ1H is alerted on prefix, but not highlighted above.

Thanks and 73
Paul, AC9O

7021 - 7040 of 36897