Date   

locked Re: Missing Calls in grid

Ron W3RJW
 
Edited

Take a look at the post from Laurie right next to yours ...  Above or below depending on your setup.

https://hamapps.groups.io/g/Support/topic/new_jtalert_beta_available/74527969?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,74527969
--
73
Ron, W3RJW


locked Missing Calls in grid

Tom Melvin
 

Hi

Just noticed a little issue -  JTAlert 2.16.5 - Wsjt-x RC3

6m has been going mad just now - I have the wanted grid alert enabled.  Few times I have heard the alert, looked at the screen and no coloured call.  First few times put it down to imagination - then while looking at screen I see the call highlited briefly  and then gone - it appears the wanted grid was on the 1st row of calls but then the JTAlert screen was quickly re-drawn and that 1st line disappeared. 

It may have been fixed already but thought I would mention it. I will enable debug just incase I catch it again and have something to go on.

Tom

--
73

Tom
GM8MJV (IO85)






locked Re: Worked B4 sometimes not working

Steve Weeks AA8SW
 

Laurie - I have noted two different anomalies repeatedly since loading rc3.  

1.  The one previously discussed in other messages, where JTAlert shows B4 entries colored correctly (grey in my case) but the coloring sporadically shows up on some, but not all, of the corresponding entries in the WSJT-X Band Activity list.

2.  Not all of the time, but not rarely either, the first 1 to 3 entries in the Band Activity window for a cycle do not show up at all in the JTAlert boxes.  Typically this happens when such early entries are very strong (+15 dB or higher) and I am guessing it may be a timing issue.  rc3 now displays decodes as they are decoded rather than collecting all of them for a phase of decoding and putting them in frequency order to display, and it starts the first phase of decoding (of the 3 phases that it now uses) before the 12.6 second Tx window is even completed.  If there are strong signals, they are decoded first and come out much earlier in the cycle than in prior versions, possibly (just a guess) before JTAlert is expecting them.

Maybe these issues are related.

Thank you for your amazing efforts in developing and maintaining this essential product.

73, Steve AA8SW





locked Re: Worked B4 sometimes not working

Tony Dixon G4CJC
 

On Mon, Jun 1, 2020 at 02:22 AM, HamApps Support (VK3AMA) wrote:
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

Sorry Laurie,
I don't remember and obviously that's important. I'll keep looking. 
Suddenly, I have a feeling I'm not seeing what I think I'm seeing.
In Settings, worked B4 if I tick Ignore Band, Ignore Mode, Ignore Gridsquare then if I've worked a station anywhere, any mode any band it will show as B4 in JTAlert. But not necessarily in WSJT-X? 
What effect does Clear B4 Cache have.
Cheers
Tony G4CJC

Cheers Tony G4CJC


locked Re: Field Day Operation

Dave Garber
 

you just have to change Jtalert to reflect logging to the FD contest log file.   at least that is what I have done in the past


then of course, change it back to the regular Aclog file when the contesting is done



Dave Garber
VE3WEJ / VE3IE


On Sun, May 31, 2020 at 9:26 PM Laurie, VK3AMA <hamapps.support@...> wrote:


On 1/06/2020 11:14 am, Larry wrote:
> N3FJP has updated his field day program. I will use that. WB2UFO

Unless Scott has changes the API used with his Contest Loggers, JTAlert
should still work with his new release.

de Laurie VK3AMA





locked Re: Incorrectly Identifying DXCC Entities Worked

Jeff - G4IUA
 
Edited

Meanwhile I'm just manually going to 'Wanted DXCC/Individual Bands', highlighting the band,  finding the incorrectly identified prefix for that particular band and sending it from the 'Wanted' column to 'Not Wanted'.  Not so much a problem now that I have a reasonably large number already worked but for someone starting out it would be a real pain.

BTW updated to WSJT-X 2.2.0 rc3 and JTAlert 2.16.6 r2

Jeff - G4IUA


locked Re: Worked B4 sometimes not working

neil_zampella
 

DOH .... I just remembered.   I turned that off because it was more of a distraction than assistance.    I had forgotten about it as I believe it was removed as an option for the clone.

Neil, KN3ILZ


locked Re: Worked B4 sometimes not working

Stephen Taylor - K6SJT
 

Laurie,

(1) I cleared the B4 cache.

(2) I have not observed the condition repeat over the weekend.

(3) FT4 has been very slow during this period, so if the issue is exacerbated by a high volume of calls (as mentioned in this blog) then that may be why I haven't observed it?

I'll keep watching and report any details of importance - Thank you,
Stephen Taylor - K6SJT 


locked Re: Field Day Operation

Laurie, VK3AMA
 

On 1/06/2020 11:14 am, Larry wrote:
N3FJP has updated his field day program. I will use that. WB2UFO
Unless Scott has changes the API used with his Contest Loggers, JTAlert should still work with his new release.

de Laurie VK3AMA


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.

5561 - 5580 of 35446