I've applied to the JTALERT support group, but had no idea how long the approval takes. Decided to post here. My apology if this is not permitted.

I’ve been using LOG4OM V2 for about a week and decided last night to get WSJT / JTALERT running. I upgraded both programs to their latest versions. My Flex 6500 was on and both WSJT and JTALERT were open and running. Proper operation was verified with Log4OM V1.

Ø  Started the installation procedure described in the LOG4OM manual (below)

Ø  When I get to Step #5 below, I get Fatal Error, "MY SQL Start Failure"

Ø  Posted the problem on the LOG4OM forum and was told that it is a known JTALERT bug.  I found this strange since I’ve seen others say it’s working fine.

Ø  Last night I got to thinking and now wonder if the radio needs to be off, and perhaps also LOG4OM?

Ø  LOG4OM needs to be run in an ADMIN mode – how about JTALERT?

I appreciate any suggestions on how to get this running.

 

(The steps below refer to page 142 in the latest LOG4OM manual dated 5 FEB 2020)

 

1.Enable the Remote Control port in Log4OM V2 with a UDP Port number of 2241- OK

2.Create an "ADIF_MESSAGE" inbound connection in Log4OM V2 with a UDP Port number of 2235 - OK

3. Create a "JT_MESSAGE" inbound connection in Log4OM V2 called JTALERT REBROADCAST with a UDP Port number of 1240 - OK

4. In WSJT-X/WSJT-Z File/Settings/reporting check the boxes and set the ports as shown below. - OK

5.In JTAlert in settings/manage settings/Logging/Log4OM V2 in JTAlert, enable the "Send WSJT-X DX call to Log4OM" and "Enable Log4OM V2 Logging"

When I tried to do step #5 above, I got “Fatal Error, "MY SQL Start Failure"

I was unable to proceed beyond this point.

6.Set the Control port in JTAlert to match the port used in Log4OM V2 (Step 1.)

7.Set the ADIF_MESSAGE port in JTAlert to match the port used in Log4OM V2 (Step 2.)

8. In settings/manage settings/applications/WSJT-X/JTDX in JTAlert enable "Rebroadcast WSJT-X UDP Packets (received only)" and set the IP Address to 127.0.0.1 and UDP Port number to match that set in Log4OM V2 step 3

Hello all,
"Manage setting" --> Wanted Prefix
Why I can't  input some prefix in the field ?

Thanks for all  and have good hunt 73 Jpierre

Thank you, Sir!

I have apparently optioned JTAlert to pop tp the foreground on top of whatever is there. When I uncheck Enable Dock it unchecks but when I put it and WSJT-X down on the task bar, it and WSJT-X pop back up to the forground docked. Can someone tell me where and how I can change that?

Thanks,
Paul
N5DUP

"Applications -> WSJT-X / JTDX" section of the Settings window.

de Laurie VK3AMA

I have apparently optioned JTAlert to pop tp the foreground on top of whatever is there. When I uncheck Enable Dock it unchecks but when I put it and WSJT-X down on the task bar, it and WSJT-X pop back up to the forground docked. Can someone tell me where and how I can change that?

Thanks,
Paul
N5DUP

I rebooted a few more times, and it started working again. Don't know why it did this, but it's working again. I don't have anything except for W10 Defender running.

Charlie 

Thanks Laurie - I should have used the SEARCH functions prior - apologies - will roll back and hang on.
73/Greg
K9IG

Just getting to 2.15.8 install - installed fine.  Once the program spawns, I wanted to tweak some items so click on SETTINGS and I get this error.  Up to me selecting SETTINGS - the program seems to be running and displaying info as expected.  I get this error on both WSJTx and JTDX versions.
Greg
K9IG

Know problem affecting a very small number of users and discussed in this group many times.
The fix is to wait until the next JTAlert release due in a day or two or install an updated VC 32bit runtime package.
See https://hamapps.groups.io/g/Support/message/27654

de Laurie VK3AMA

Just getting to 2.15.8 install - installed fine.  Once the program spawns, I wanted to tweak some items so click on SETTINGS and I get this error.  Up to me selecting SETTINGS - the program seems to be running and displaying info as expected.  I get this error on both WSJTx and JTDX versions.
Greg
K9IG

Laurie,  I have no idea.  Have not changed any clocks or settings.  Can't make a connection, but I did have an initial problem with future cluster spots when I first installed the new Log4OM V2.  I was sending screen shots to the Log4OM Forum while trying to figure out the problem.  One of the testers was able to replicate it, so they know I'm not crazy.  I was going to do some testing for them when it corrected itself.  

I've had the rig and computer off and on several times today, and so far the future decodes remain.  I'll keep an eye on them to see if they clear when their real time passes.

You really might have a market for software that can predict future DX. LOL

73, Herb WB8ASI

Herb,

I was able to produce future decodes by opening a previously saved wav file in WSJT-X. The wave files contain time stamps of the decodes (no dates).

Your only solution is to set the Decodes window (temporarily) to delete all entries on startup, restart Decodes then once started set the delete entries setting back to you previous setting.

The clearing of decodes in the Decodes window is not a true clear, the decodes remain in the database. The clear method applies a date/time filter expression to the sql used to display the decodes and this filter remains in effect until the Refresh menu is used. This allows you to clear the display and only display any newly incoming decodes without the old decodes reappearing. The date/time filter is set to the current UTC data/time when the Clear is used normally resulting in only new decodes after that date/time to be displayed.

de Laurie VK3AMA

Thanks for those suggestions, however it doesn't help.  One of the first things I thought of was that the window popped up somewhere and I couldn't see it, but it doesn't seem to be "popping" anywhere.

All of the other windows appear correctly when selected.

Laurie- in Task Manager, should I see the Decodes running as a Process?  I thought I saw it running at one point but it's not there now.  Now when I click on the View Decodes Window, nothing at all happens.

Thanks for the help !

John K2ZJ

The Decodes window should appear as a Window (obviously) and its entry in TaskManager will be "JTAlertV2.Decodes.exe"

If there is a TaskManager entry there should be a button (is that what they are called?) in the taskbar.

If there is no TaskManager entry, the Decodes window will not load if "Decodes" being disabled in JTAlert. See the "Windows -> Decodes" section of the Settings.

If this is recent behavior, I strongly suggest your perform a PC restart especially if your on WIn10.

Have you recently run any sort of cleanup software that removes directories from your local app data directory tree or a registry cleaner?

de Laurie VK3AMA

Every time I start a JTAlert / WSJT-X session, I get this message:



Because of hearing problems, I have audio turned off in JTAlert, so why must I see this error message over and over and over . . . FWIW, this problem is fairly new, older versions of JTAlert did not show this error.

73, Bill  AA4M

Bill,

This was a deliberate design decision made to prevent JTAlert using the same sound device as WSJT-X causing alert sounds to be transmitted.

To avoid this error, choose an different sound device for JTAlert.

This has been previously discussed with a free solution. See https://hamapps.groups.io/g/Support/message/26856

de Laurie VK3AMA

Thanks for those suggestions, however it doesn't help.  One of the first things I thought of was that the window popped up somewhere and I couldn't see it, but it doesn't seem to be "popping" anywhere.

All of the other windows appear correctly when selected.

Laurie- in Task Manager, should I see the Decodes running as a Process?  I thought I saw it running at one point but it's not there now.  Now when I click on the View Decodes Window, nothing at all happens.

Thanks for the help !

John K2ZJ

Every time I start a JTAlert / WSJT-X session, I get this message:



Because of hearing problems, I have audio turned off in JTAlert, so why must I see this error message over and over and over . . . FWIW, this problem is fairly new, older versions of JTAlert did not show this error.

73, Bill  AA4M

Haven't seen this before.....Tried clearing the Decodes Window, but 10 spots remain.  They are all in the future?   Hoping they will clear themselves in about 4 hours.  73, Herb WB8ASI

How did you get spots with future dates?

de Laurie VK3AMA

I have been using V2.15.7 successfully for the past few months, the Decodes History Window is especially useful because of the filters by Continent.  However today, quite randomly the window would not load.  I select it from the menu, and I can see the spinning disc for a few seconds but nothing appears on the screen.

This window has always worked for me over the past 6 months. All of the other windows work, like Text box etc.

I have rebooted the PC, rebooted JTAlert, reinstalled JTAlert etc with no success.

In the Task Manager of windows I see that the Decodes function is there- but nothing shows on the screen.

Any help with troubleshooting?  

Thanks John K2ZJ

Google "windows Recover off-screen window" for a solution. This is a very common problem with Windows resulting in many millions of search results.

This one works
https://www.howtogeek.com/howto/windows/bring-misplaced-off-screen-windows-back-to-your-desktop-keyboard-trick/

de Laurie VK3AMA

This morning I did work VK9NK on Norfolk Is. 17m. This was my first QSO. I did upload it to LoTW and download LoTW  on Log4OMV2. I did later Scan the log on JTAlert and was surprised to find that Norfolk Is. Is reported as "Not wanted" on DXCC 17m. I did later find that Log4OMV2 does report all entries as LoTW confirmation Received as "Yes" and Received Date of some entries, not including VK9NK 17m of today, with the reporting received date.

So why did my JTAlert report 17m Norfolk Is. as "not wanted" and how does JTAlert find "Not Wanted" DXCC/LoTW in general?

 

Amos 4X4MF

If Log4OM2 is showing VK9NK as Lotw Received = "Yes" than JTAlert will consider that as LoTW confirmed. JTAlert doesn't look at the Date entry, only the Received entry.

de Laurie VK3AMA