Log4OM

Hi guys,
I play JT65 mode, I work now with JT65HF-Comfort + JTAlert + HRDeluxe (Simon version).

Now I would to change the logging software to Log4OM and I wish will work all togheter.

Can someone help me to work all togheter?

My Windows is W7 64bit, my radio is FT897, my separate sound card is one cheap USB stick, my pc interface is USB made by DK4MX.

Thanks, Camillo iz6gvc

Ciao Camillo, we have discussed a lot about this in the forum.
Argument is covered there: http://www.pisto.it/forum/viewtopic.php ... jt65#p2765
there: http://www.pisto.it/forum/viewtopic.php ... =jt65#p858

and there is a chapter on the manual (page 150) that covers this implementation.

Basically you need to start log4om external services and follow the instructions (step by step, it's very easy and plenty of descriptive images)
The manual covers the whole process in all softwares.

You can download it here: http://www.pisto.it/LogOm/Log4OM_enu.pdf

Ask for help if you're in troubles

Hi Daniele, how are you?

I tried with this two "guides" but I've some litle trouble.

1) - I start for first JT65HF-Comfort 3.8 with Admin Privileges, Omnirig selected for CAT; but the QRG changes is very slow and the decode (after the 50") is show about a the 53/55 seconds.
The remaining time for Call selecting is very short.

2) - For second I start JTAlert also with Admin Privileges, and work perfectly (without Admin Privileges JTAlert not work B4 and call info); integration with Log4OM is OK via port 2236.

3) - For last start Log4OM also with Privileges, without CAT controll, but some times the setting page freeze and I made Ctrl+Alt+Canc!

Can I help with some screeshoot?

73s, Camillo iz6gvc

I'm not expert about those modes, never used, but this setup is very popular and probably there is someone there in the forum that could help you better than me with comfort. Anyway screen shot help.
About point 3, it's Log4OM that freezes? If yes I wish to investigate more on that. Is that situation reproducible? Can you freeze it again?

Daniele

Hi Daniele and guys, some screen.

Many sreenshoots.

Other many many.

Many many many.

End!

In Log4OM communicator you do not want to point to the JT65 path in

Temporary ADIF file polling
or
ADIF file polling

Please leave them blank

Because that is not how the contact is logged from JTAlert!

As the JT65 instructions say's it sends the contact to the Log4OM SQLite file

You must enter the path to your Log4OM SQLite file into JTAlert something like the screen shot below

Also in JTalert ensure that the Server IP address and UDP Port as as shown in my screenshot, unless you are using it across a network.

I don't use JT65 but I set up JTAlert to check everything works and it is working 100% OK with Log4OM so the issue is in the set up at your end.

I need to talk with JT-ALERT author about the "log4om bug" he stated in his form...