Date   

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


locked Re: Worked B4 sometimes not working

Tony Dixon G4CJC
 

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


locked Re: No sound v 2.16.6

neil_zampella
 

Based on what you've said about getting 'viruses', what Laurie has said about the manager process, and the fact that its still not working.  I suspect that your antivirus is quarantining needed JT-Alert executables.  

Waiting the next six months or more for v3 will not do any good, as your antivirus will probably keep doing it with the new version, so you may as well try get it working with the current version.

Again, have you setup the c:\program files (x86)\HAMAPPS\ directory in your antiviruses whitelist??    If not you're not going to get anything working, possibly not even when v3 comes out.

Neil, KN3ILZ


locked Re: Worked B4 sometimes not working

Paul AC9O
 

Hi Laurie,

FT8. I haven't delved into FT4 yet.

I did clear the cache multiple times. And restarted JTAlert, and at one point, did a system restart too. Still seeing the issue.

Just noticed something today. I was on 15m when there was little activity, only 2 or 3 decodes. I worked multiple stations on this quite band and the Worked B4 functioned fine on all.

Perhaps it's something in the way of a timing issue when the second or third decode pass takes place? That wouldn't happen on a quite band too often I presume.

Just a thought.

Thanks and 73
Paul, AC9O


locked Re: Worked B4 sometimes not working

Laurie, VK3AMA
 



On 27/05/2020 1:03 pm, Paul AC9O wrote:
Definitely in the log. When I display the pop-up, it shows as worked too. In ACLog, when I start a contact, it lists the prior contacts so I can see it right away. 

Doesn't happen all the time, but seems to be more frequent. Very intermittent. Perhaps it some kind of a timing issue with the multiple decode passes in the new version of WSJT-X?

Thanks for looking.

73
Paul, AC9O

Paul,
  1. What Mode, FT4 or FT8 or is it both?

  2. Does clearing the B4 cache (via the Alerts menu near the top) correct this B4 non-display?

  3. If clearing the B4 cache does not correct the B4 non-display, please as a test restart JTAlert, does the affect Callsign correctly show the B4 after the JTAlert restart?

Let me know the answer to these three questions.

de Laurie VK3AMA


locked Re: Worked B4 sometimes not working

Gerald Klotz
 

I had this happen once but at the time I was doing major multitasking. Besides having the regular four programs running for FT 8, I had several web sites open as well as some other programs. I also had my weather station running which is a draw on the graphics card. I shut everything down and rebooted and didn’t see it again, figured it was a glitch or windows problem.

Gerry Klotz

On May 29, 2020, at 3:51 PM, Charles Ristorcelli <nn3vham@...> wrote:

I too have the same problem.

How is it possible that NO ONE ELSE has experienced this problem AND found a solution?

Is it possible that NO ONE else uses JT Alert, or everyone has the problem but does not care?

If someone has an answer, how about a detailed explanation of the solution.

73 de NN3V


locked Re: Worked B4 sometimes not working

Laurie, VK3AMA
 



On 27/05/2020 12:06 pm, Stephen Taylor - K6SJT wrote:
As I listed in my original message, the QSO is logged to HRD via JTAlert and JTAlert does confirm with "SUCCESS: QSO Logged" to HRD 

The windows then clears and can show several additional cycles, yet the WSO station still does not show as worked before in JTAlert -

PS - I run FT4 predominantly

Stephen Taylor - K6SJT

Stephen,
  1. Does clearing the B4 cache (via the Alerts menu near the top) correct this B4 non-display?

  2. If clearing the B4 cache does not correct the B4 non-display, please as a test restart JTAlert, does the affect Callsign correctly show the B4 after the JTAlert restart?
Let me know the answer to these two questions.

de Laurie VK3AMA


locked Re: HELP

HamApps Support (VK3AMA)
 

On 30/05/2020 6:46 am:
My JTAlert does not show Worked Before (B4) status.

When I work a station, it continues to show that staion as not worked.

Why?

Why?  Why do you expect support when you have provided zero information regarding your JTAlert operating environment?

Please don't post a new message thread when you have already asked the same question in another thread. This one has now bee locked.

de Laurie VK3AMA



locked Re: Worked B4 sometimes not working

HamApps Support (VK3AMA)
 

On 30/05/2020 6:51 am:
I too have the same problem.

How is it possible that NO ONE ELSE has experienced this problem AND found a solution?

Is it possible that NO ONE else uses JT Alert, or everyone has the problem but does not care?

If someone has an answer, how about a detailed explanation of the solution.

73 de NN3V

OM,

It is a bit hard to provide help when you have avoided providing any information regarding your operating environment in this post and your recently started "HELP" message.

  • What version of JTAlert?
  • What Logger is being used with JTAlert?
  • What Windows version?
  • WSJT-X or JTDX and what version?
  • Is this a recent problem, if so what was the last JTAlert version that worked for you?

FWIW, the current JTAlert user-base exceeds 10,000 unique Callsigns active a Month.

de Laurie VK3AMA



locked Re: Worked B4 sometimes not working

Charles Ristorcelli
 

I too have the same problem.

How is it possible that NO ONE ELSE has experienced this problem AND found a solution?

Is it possible that NO ONE else uses JT Alert, or everyone has the problem but does not care?

If someone has an answer, how about a detailed explanation of the solution.

73 de NN3V


locked HELP

Charles Ristorcelli
 

My JTAlert does not show Worked Before (B4) status.

When I work a station, it continues to show that staion as not worked.

Why?


locked Re: Linux Question

Joe Subich, W4TV
 

Can JTAlertX run in Linux?
No. JTAlert is a Windows application.


73,

... Joe, W4TV


On 2020-05-29 3:34 PM, Robert Rampolla via groups.io wrote:
Thanks for your thoughts but this still has not answered the question  Can JTAlertX run in Linux?


locked Re: No sound v 2.16.6

Jesus
 

Good afternoon Laurie, in the end I have made the decision to temporarily suspend the JTAlert program (I miss it already), but I think the right thing to do is wait for version 3 when you can launch it.
I usually work with WSJT-X and Log4OmV2 and now I have them directly reported.
I hope to be able to use JTAlert again when it is stable for me, since the information it transfers in real time is extraordinary for those of us dedicated to digital communication ...
I am very attentive to future changes that I hope will come soon.
Thank you, Laurie, thank you for your work on behalf of all radio amateurs.
Cordially,
Jesus, EA1YR


El mié., 27 may. 2020 a las 2:11, HamApps Support (VK3AMA) (<vk3ama.ham.apps@...>) escribió:
On 25/05/2020 3:08 am, Jesus wrote:
Good afternoon, I have performed the sound check with the card of the laptop itself ... negative.
I have for JTAlert, its own external sound card but there is no way to get audio.
The option of TX / RX callsign per band does not inform me of data either.
I appreciate some idea to see if I can activate the sound, preferably.

Cordially,
Jesus, EA1YR

Jesus,

If Sound are not working AND the band activity is not being updated, that indicates a problem with the JTAlertV2.Manager process. It handles both those functions (as well as several others). Very likely your PC protection software is interfering or blocking the UDP communications from JTAlert and blocking the Internet access to get the Band Activity data.

I may see something in your JTAlert session data. Please use the "Help" (or "? ") -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA




locked Re: More than 36 decodes

John L. Broughton
 

Dave,

Thank you for your consideration. I wish more fold did the same. However, without being a Authenticated User on eQSL, QSLs with you cannot be counted by the other station toward awards; it is just personal satisfaction for them working you if you are in one of their needed states.

I, too, am an ARRL VE. We had a session a couple of weeks ago that observed social distancing protocols. I did not participate in it, but it went well according to reports.

73,

John, WB9VGJ
--
John L. Broughton
wb9vgj@arrl.net
2sliverhondas@gmail.com
www.wb9vgj.us

On 5/27/2020 1:10 PM, Dave Cole wrote:
Hi John,
I don't use either, only LoTW.  I do however always upload to all three as a courtesy to those that do.  It takes almost no time for me to upload to the other two...

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 5/27/20 12:05 PM, John L. Broughton wrote:
One consideration.

I started using eQSL, I hadn't been aware of it, when I got an email from a guy who worked me and told me he needed Arizona for an award on eQSL and asked me to join. I did join and then he informed me I had to be an Authenticated User for our QSO to count for an award, so I became one. I'm glad I did.

<soapbox>
Personally, I wish everyone used eQSL, LoTW and QRZ as I really like collecting awards on all three (check out my QRZ page).

My pet peeve is hams that refuse to use LoTW, eQSL or QRZ. I exchanged email with a ham in Europe who brags about all his DXCC awards on his QRZ page, but who refuses to QSL online. One would think he could appreciate what it means to other hams to get a QSL for a needed country, state, etc.
--
John L. Broughton
wb9vgj@arrl.net
2sliverhondas@gmail.com
www.wb9vgj.us

On 5/27/2020 7:07 AM, Jim Nuytens via groups.io wrote:
I agree. For example, I filter out anyone who is not on eQSL. Makes life a lot easier.

On 5/27/2020 00:47, HamApps Support (VK3AMA) wrote:

IMHO, 36 displayed Callsigns is too many. It is a chaotic mess of multiple colored callsigns. A better option is to filter out most of the unwanted Callsigns. Use the Alert Filters to help reduce the number displayed.

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>     Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


locked Worked B4 Erratic

Charles Ristorcelli
 

I run JTAlert with Ham Radio Deluxe.

Operation is normal, and automatic logging in HRD Logbook works fine.

However, over the past week the Worked Before feature stopped working.

After I worl a station, the station continues to show up as not worked before.

Any ideas as to what setting I am missing?

73 de NN3V

7121 - 7140 of 36983