JtAlert does not receive confirmation after logging QSO in through Log4OM_2.
There should be feedback from Log4OM to JtAlert as it was in version 1.
Maybe you need to set some UDP OUT action?
JTAlert problem
- IW3HMH
- Site Admin
- Posts: 2925
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: JTAlert problem
There is nothing returned to JTAlert except the default UDP handshacking.
Daniele Pistollato - IW3HMH
Re: JTAlert problem
That is, it is impossible to make confirmation in JTAlert whether QSO was logged in correctly as it is in ver 1 Log4OM ?
Re: JTAlert problem
A new version of JTAlert which supports Log4OM V2 is pending release, we are told.
If you want to continue to use JTAlert, I recommend that you turn off logging in JTAlert, and log directly from WSJTx or JTDX into V2. Note, if you are using the DX Call forwarding to V2, you will need to setup Rebroadcast of the UDP messages in JTAlert. I covered how to do this in this thread - viewtopic.php?f=33&t=4324&start=10
73,
Doug
W7DRM
If you want to continue to use JTAlert, I recommend that you turn off logging in JTAlert, and log directly from WSJTx or JTDX into V2. Note, if you are using the DX Call forwarding to V2, you will need to setup Rebroadcast of the UDP messages in JTAlert. I covered how to do this in this thread - viewtopic.php?f=33&t=4324&start=10
73,
Doug
W7DRM
Doug - NN7D
Gig Harbor, WA, USA
Gig Harbor, WA, USA
- G4POP
- Log4OM Alpha Team
- Posts: 10753
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: JTAlert problem
Think he is referring to the not logged warning from JTalert due to JTalert not being able to read the version 2 database
73 Terry G4POP
Re: JTAlert problem
Thank you for the information, you have to wait for the JTAlert update.
Login works correctly only JTAlert does not receive confirmation.
Login works correctly only JTAlert does not receive confirmation.