Date   

locked Re: FT8 & FT4 transmission intermittent problem

Bob Davet
 

PTT toggles.

I understand it is not a JTAlert issue.

Just didn't know where to start so I thought I would start here to see if anyone else had the issue and where they went from her to fix it.

Bob
W8RID


locked Re: 73/RR73

HamApps Support (VK3AMA)
 

On 7/12/2020 11:58 pm, F8RZ wrote:

I just installed the last JTalert and I see that now  RR73 and 73 are on a dark green background.

Interesting feature, but as far as I know, it is not mentioned anywhere... or at least I did not see it.

 I should like to change the color, but how ?


73 to all.

F8RZ

See the Release Notes.

The RR73 coloring was introduced with 2.16.8 and then later modified with 2.16.16 to remove the CQ Alert requirement. The colors still use the colors you have set for the CQ Alert.

2.16.8 (19-Jun-2020)

  New Features:

    - WSJT-X decode highlighting: If the JTAlert CQ Alert is enabled than WSJT-X
       decodes ending in "73" or "RR73", indicating that the DX station has ended
       their QSO, will have the "73" or "RR73" colored with the CQ Alert colors.

2.16.16 (18-Nov-2020)

  Changes:

    - WSJT-X Decode Highlighting: "73" or "RR73" decode highlighting no longer
       require the CQ Alert to be enabled. A dedicated setting is now available.
       See the "Applications -> WSJT-X / JTDX" section of the Settings window.
       Note: This and other color highlighting is not available for JTDX.

de Laurie VK3AMA


locked Re: FT8 & FT4 transmission intermittent problem

Michael Black
 

Not really JTAlert related...

Do you mean PTT toggles or that power level fluctuates?  

Mike W9MDB




On Tuesday, December 8, 2020, 11:07:16 AM CST, Bob Davet <davet354tfd@...> wrote:


Not sure if I should post this here or not. So I thought I would start here and go from there.

I have been running FT8 and FT4 for a long time now. Enjoy the mode very much.

I am running a IC746Pro with a USB interface with HRD Rig control.

Have been pilling up the contacts.

Been trying to track down this issue for a while now without any success.

Randomly, during my transmissions it will rapidly fluctuate in and out of transmission.

I have checked the cables from the Signalink and they are good.(actually used several different cables and it happens)
Not sure where to look next. Guessing that it is probably the signalink that may be the issue.
If I turn the TX knob on it rapidly back and forth then set it back where I normally have it it seems to run OK for a while.
Seems like the TX knob could be "dirty"?

None of this seems to be affecting my transmission that I know of. No one has let me know about any possible issues.

Bob
W8RID


locked FT8 & FT4 transmission intermittent problem

Bob Davet
 

Not sure if I should post this here or not. So I thought I would start here and go from there.

I have been running FT8 and FT4 for a long time now. Enjoy the mode very much.

I am running a IC746Pro with a USB interface with HRD Rig control.

Have been pilling up the contacts.

Been trying to track down this issue for a while now without any success.

Randomly, during my transmissions it will rapidly fluctuate in and out of transmission.

I have checked the cables from the Signalink and they are good.(actually used several different cables and it happens)
Not sure where to look next. Guessing that it is probably the signalink that may be the issue.
If I turn the TX knob on it rapidly back and forth then set it back where I normally have it it seems to run OK for a while.
Seems like the TX knob could be "dirty"?

None of this seems to be affecting my transmission that I know of. No one has let me know about any possible issues.

Bob
W8RID


locked 回复: [HamApps] 73/RR73

Zhang Hong
 

Its usefull. I like it.

 

发送自 Windows 10 邮件应用

 

发件人: F8RZ
发送时间: 2020127 20:58
收件人: Support@HamApps.groups.io
主题: [HamApps] 73/RR73

 

H

 


locked Re: 2.16.16 crashes

Coy Day
 

Laurie,

Looks like that did the trick.  I went to C:\Users\n5ok\Appdata\Local and found the HamApps folder there and deleted it.  It has been running for about 30 minutes and not a single error.  I'm a happy camper!

I'll let it run all night here on 40m.  That should be a good test.

Thanks a bunch!

73, Coy

On Mon, Dec 7, 2020 at 8:27 PM Laurie, VK3AMA <hamapps.support@...> wrote:


On 8/12/2020 12:29 pm, Coy Day wrote:
> It came up with almost all of my settings.  They must be kept in a
> separate folder somewhere.  If I knew where they were, I would try
> deleting them.
>

The only setting JTAlert should have remembered after you removed the
HamApps directory is your Callsign. All other settings will have
defaulted. Sounds to me like you didn't delete the correct directory.

Use Windows File Explorer and navigate to %localappdata% then delete the
HamApps directory.

de Laurie VK3AMA








--
Coy C Day, N5OK
20685 SW 29
Union City, OK 73090
H(405) 483-5632 C(405) 448-2368


locked Re: 2.16.16 crashes

Laurie, VK3AMA
 

On 8/12/2020 12:29 pm, Coy Day wrote:
It came up with almost all of my settings.  They must be kept in a separate folder somewhere.  If I knew where they were, I would try deleting them.
The only setting JTAlert should have remembered after you removed the HamApps directory is your Callsign. All other settings will have defaulted. Sounds to me like you didn't delete the correct directory.

Use Windows File Explorer and navigate to %localappdata% then delete the HamApps directory.

de Laurie VK3AMA


locked Re: 2.16.16 crashes

Coy Day
 

Laurie,

The short answer is no.  I tried upgrading to 2.16.17 first but that didn't help.  Next I ran the uninstall program and deleted the folder HamApps.  I did a new install of 1.16.17, the sound files and the callsign database.  It still comes up with the error.

It came up with almost all of my settings.  They must be kept in a separate folder somewhere.  If I knew where they were, I would try deleting them.

Not sure what to do now.  It seems strange that it will run without the error as long as no callsigns are being sent from WSJT-X.  When I turn the monitor back on or turn up the receive gain so that signals are being copied, it will populate the array several times before I get the error.

I appreciate your efforts!

73, Coy


On Sun, Dec 6, 2020 at 12:42 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 6/12/2020 11:45 am, Coy Day wrote:
> I've tried re-installing 2.16.16 but that doesn't help at all.  I'm at
> the point of deleting the HamApps folder and doing a completely new
> install.
>
> Hope things are going better for you.
>
> 73, Coy

Did that help, deleting the HamApps folder?

de Laurie VK3AMA








--
Coy C Day, N5OK
20685 SW 29
Union City, OK 73090
H(405) 483-5632 C(405) 448-2368


locked Feature Request - Automatic Clearing of Alert Triggers

David - AK2L
 

Using JTAlert 2.16.7 with WSJT-X 2.3.0-rc2
 
I worked the FT Roundup contest this past weekend.  For the contest, I relied on WSJT-X to log the contacts and JTAlert to inform me when a new state, VE province or DXCC was decoded.
 
To stop JTAlert from triggering on a state once I had a QSO with that state, I checked the "Auto clear triggered Alert entity after logging" option on the appropriate settings panel.  I did the same for VE provinces and DXCC settings.  This feature worked well and was very helpful in focusing my attention on new multipliers.
 
Each time a QSO was completed with an alert-able entity, JTAlert would display a pop-up telling me that the alert trigger had been cleared for that entity.
 
Problem:  JTAlert would show the pop-up every time I had a QSO even if the trigger had already been cleared.  For example, I had 30 QSOs with Texas stations.  JTAlert correctly alerted only once prior to the first Texas QSO.  But, the pop-up indicating that the alert trigger had been cleared appeared 30 times.
 
Request:  Do not display the pop-up if the trigger conditions are no longer set.  Or, add a user-settable option to stop all appearances of the pop-up.
 
Thank you.
 
David, AK2L
 


locked Re: 2.16.17 fails

Steve, N3SL
 

Fascinating....  The new url worked perfectly.   THANKS, Laurie!


On Sun, Dec 6, 2020 at 10:10 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 7/12/2020 12:24 pm, Steve, N3SL wrote:
I can't believe (or don't want to) that I'm the only one with this finding, but I've not seen any other messages....   I now have downloaded 2.16.17 on three different PCs, and every one of them gives me a near immediate message that the setup files are corrupted, and I need to get a new version.  Am I the only one?  I'm at a loss as to the cause.  I should probably mention that each machine tells me the download is suspect/potentially harmful, and do I want to continue....  Of course, that's been the case with JTAlert files for a LONG time....

Thanks for any guidance,
N3SL

Steve,

Sorry, but your the only one reporting this. The problem will be something common to all 3 of your PCs. Very likely your ISP internet connection.

Many ISPs, in order to reduce their bandwidth costs, utilize a transparent cache and will cache downloaded files, images, etc, and when another user on their network requests the exact same file they deliver the copy from their cache rather than the from the source location. My guess is that your ISP has a corrupt copy of the JTAlert setup file  in its cache that it keeps delivering it to you when requested from your other PCs.

A couple of things to try.
  1. Download the setup file using another ISP say from your Cell service if it is different provider.
  2. Fool the ISP cache into downloading and delivering what it thinks is a different file by manipulating the download url. Try appending "?v=1" to the url. I just now tested and this will still provide the file for download despite the url being changed.
    https://dnl.hamapps.com/JTAlert/eda319ab9017e7af6f5962d54a823a94?v=1

de Laurie VK3AMA



locked 73/RR73

F8RZ
 

Hello...

I just installed the last JTalert and I see that now  RR73 and 73 are on a dark green background.

Interesting feature, but as far as I know, it is not mentioned anywhere... or at least I did not see it.

 I should like to change the color, but how ?


73 to all.

F8RZ


locked Re: JTAlert not playing nice with LOG4OM V2

Laurie, VK3AMA
 



On 7/12/2020 4:47 pm, earlwg@... wrote:
Unable to confirm QSO Logged."
Is coughed up by JTAlert after logging a QSO about 2 times out of three. The QSO logs always get to LOG4OM even when the above error happens.
Sounds like confirmation of the QSO log is not reliably getting back to JTAlert somehow.
Any suggestions?

If QSOs are correctly being logged and JTAlert intermittently reports it is unable to confirm the QSO was logged then you will need to adjust the "Check QSO Log Record" time. Log4OMV2 takes much longer to log a QSO than the V1 so an increase in the time is typically needed. Try setting it to 10secs.
See the "Logging" section of the Settings window.


de Laurie VK3AMA


locked Re: LoTW FT4 download

Jacques Corbu
 

sorry Laurie I thought I had edited this post or removed it but did sort it out just after posting  the logbook is current version but had forgoten to do one step when creted the new logbook  apologies to all 

Stay safe Jacques F1VEV


locked Re: JTAlert not playing nice with LOG4OM V2

Earl
 

No. I am using SQLite database.


locked Re: JTAlert not playing nice with LOG4OM V2

Michael Black
 

Do you have Use MySQL Server checked?

Inline image






On Sunday, December 6, 2020, 11:47:06 PM CST, earlwg@... <earlwg@...> wrote:


OK...it still isn't completely fixed. The error message:
"LOGGING WARNING:
Error Message: LOG4OM V2 SQLITE:
Unable to confirm QSO Logged."
Is coughed up by JTAlert after logging a QSO about 2 times out of three. The QSO logs always get to LOG4OM even when the above error happens.
Sounds like confirmation of the QSO log is not reliably getting back to JTAlert somehow.
Any suggestions?
Maybe this needs a new thread?


locked Re: JTAlert not playing nice with LOG4OM V2

Earl
 

OK...it still isn't completely fixed. The error message:
"LOGGING WARNING:
Error Message: LOG4OM V2 SQLITE:
Unable to confirm QSO Logged."
Is coughed up by JTAlert after logging a QSO about 2 times out of three. The QSO logs always get to LOG4OM even when the above error happens.
Sounds like confirmation of the QSO log is not reliably getting back to JTAlert somehow.
Any suggestions?
Maybe this needs a new thread?


locked Re: AutoIT error , what to do ?

ed.n5dg@...
 

Yes you'll see me on pskreporter , I have more then on radio setup . It's working for now 
I was following along with LOG4OM , I have it seeing my log and sending the correct alerts but for the life of me I can't log a contact ... Followed ur help in jtalert https://prnt.sc/vx76g6
Thanks Ed N5DG


locked Re: AutoIT error , what to do ?

ed.n5dg@...
 

was 2.16.16. when I sent the message . Now it 1.16.17 .  I deleted the hamapps in appdata/ local , JTalerts is staying up , maybe that fixed it 
Ed N5DG


locked Re: AutoIT error , what to do ?

HamApps Support (VK3AMA)
 

On 7/12/2020 11:17 am, ed.n5dg@... wrote:
This error pops up each time I executer JTAlert ,  Is their a fix for this or a setting ? with this error JTAlert will not work . Using windows 10 64 
Thanks Ed N5DG
Ed,

I see your sending spots to HamSpots from JTAlert. So it looks to me like your running fine. What version are you running and what changes did you make that prevented the error you reported?

de Laurie VK3AMA


locked Re: AutoIT error , what to do ?

Laurie, VK3AMA
 

On 7/12/2020 11:17 am, ed.n5dg@gmail.com wrote:
This error pops up each time I executer JTAlert ,  Is their a fix for this or a setting ? with this error JTAlert will not work . Using windows 10 64
Thanks Ed N5DG
What version of JTAlert?

de Laurie VK3AMA

2401 - 2420 of 34867