Log4OM+JTDX+JTAlert+GridTracker setup

[F6EXV]

Hi all
Wanting to install GridTracker, I messed up my previous set up without it, and now nothing works...
JTAlert no longer gets the decodes, GridTracker does not link to the log....

Is there anywher either a Youtube video or a webpage describing the entire setup ?
Using Log4OM version 2.14.1.0, JTDX version 2.2.0-rc152, JTAlert version 2.50.2 and GridTracker version 1.21.0601
As always, I am lost with which port must match which port, and so on....

Help will be appreciated.

[KI5IO]

Hi all
Wanting to install GridTracker, I messed up my previous set up without it, and now nothing works...
JTAlert no longer gets the decodes, GridTracker does not link to the log....

Is there anywher either a Youtube video or a webpage describing the entire setup ?
Using Log4OM version 2.14.1.0, JTDX version 2.2.0-rc152, JTAlert version 2.50.2 and GridTracker version 1.21.0601
As always, I am lost with which port must match which port, and so on....

Help will be appreciated.

Paul,

FYI - The current release of Log4OM is: v 2.15.0.0 You might put that on your agenda to update when you can.

As for the JTxx connections. Download the most current User Guide dated: 02/07/2021 1:25PM ...

Go to Page 201 and all the JTxx connections/combinations start on that page.

[F6EXV]

Hi Nolan
Thanks for your answer.
I did the Log4OM upgrade.
I downloaded the manual.
I followed the instructions step by step, and... it does not work...
JT alert does not receive the callsigns (the header shows ??? for the band), and after a while, I get an error message as shown in the attachment.
What have I missed ?

The manual says (top of page 208) "UDP port number to match that set in Log4OM... Which one ?

error.jpg (32.81 KiB) Viewed 3161 times

Which ports must match which ports ?
Are the ports shown in the manual a solution to follow absolutely identically ?
In other words, if ALL screens shown in the manual from page 203 to page 208are set that way, will it work, or are these screenshots from adifferent setups ?

[F6EXV]

Which UDP Inbound connections must be thicked ?
At one point, we are asked to create connections, then later they are not ticked...
Or I misread something...

[G4POP]

Hi Nolan
Thanks for your answer.
I did the Log4OM upgrade.
I downloaded the manual.
I followed the instructions step by step, and... it does not work...
JT alert does not receive the callsigns (the header shows ??? for the band), and after a while, I get an error message as shown in the attachment.
What have I missed ?

The manual says (top of page 208) "UDP port number to match that set in Log4OM... Which one ?

error.jpg

Which ports must match which ports ?
Are the ports shown in the manual a solution to follow absolutely identically ?
In other words, if ALL screens shown in the manual from page 203 to page 208are set that way, will it work, or are these screenshots from a different setups ?

If you follow the instructions starting on page 205 for setting up Log4OM, what you do is set up Log4OM part first.

Then you select from the following parts which external programs you want to use (JTalert, WSJT-X or JTDX)

When you see the instruction to 'to match that set in Log4OM V2 step 3' its refering to the Log4OM set up that you should have done first - Step 3 on page 206

[F6EXV]

Terry
I want to use both JTDX and JTAlert , simultaneously...

[F6EXV]

I have done EXACTLY the same port numbers as shown in the manual, to no avail...
All the manual screens as the same as my own screens... No luck... JTAolert gets nothing...

[F6EXV]

Further my previous email, let me add this...
I have 2 configurations for 2 different callsigns.I do not run them simultaneously. On Log4OM, I just switch callsigns. I have 2 different shortcouts for both JTDX and JTAlert, one for each callsign.
All configurations on Log4OM, JTDX and JTAlert are ABSOLUTELY identical.
It works fine for one callsign, it does not for the other one.

Any idea why ??

[F6EXV]

Somebody must have come to the shack in the middle of the noght... Now both callsigns work...
Oh well, sorry for bandwidth !