Upgraded to V2. Like the looks, but unable to log from JTAlert/JTDX. Everything working previously.
Reviewed manual and it looks like everything matches. I've attached a log file and screenshots of the configs.
I tried logging a bogus qso with callsign N6NJY. You can see where it receives it, but it doesn't go into the log.
Running JTAlert/JTDX and Log4OM all under admin rights.
Would really appreciate your help.
Thanks and 73's de N6GAT
Lost logging from JTDX
Lost logging from JTDX
- Attachments
-
- Log4om config 3 jtdx.JPG (95.35 KiB) Viewed 3391 times
-
- Log4om config 3 JT Alert.JPG (76.63 KiB) Viewed 3391 times
-
- LOG4OM2_log_UI_20210516.log
- (254.12 KiB) Downloaded 170 times
- G4POP
- Log4OM Alpha Team
- Posts: 10817
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Lost logging from JTDX
Are you sure you have selected the correct database it's unusual for it to be located in a backup folder
73 Terry G4POP
Re: Lost logging from JTDX
It appears to be correct. I did not change anything between revisions.
Thanks,
Gary
Thanks,
Gary
Re: Lost logging from JTDX
Gary,
You said you upgraded to V2 ... was that a change from Log4om V1 to Log4OM V2? Or, have you already been using V2 and just do an incremental update to the current Log4OM V 2.13.0.0 ?
Regardless ... download the most current User Guide dated: 03/05/2021 7:58 AM and starting on Page 205 is the list of specifics for setting up either WSJTx or JTDX and JTAlert to Log4OM V2. Those settings work and should get you back in order.
You might have a typo, but just step through those settings to verify your configuration. One step at a time and you will uncover the hiccup.
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: Lost logging from JTDX
Did you have set the correct UDP Inbound as ADIF_Message in Log4OM settings
at the Configuration Tab ? Log4OM V2 is looking for UDP Inbound from JTalert.
I see that you have logging to V2 enabled in JTalert so please only set UDP
inbound for JTalert. If you set it up also to UDP Inbound from JTDX you will
have double entries.
at the Configuration Tab ? Log4OM V2 is looking for UDP Inbound from JTalert.
I see that you have logging to V2 enabled in JTalert so please only set UDP
inbound for JTalert. If you set it up also to UDP Inbound from JTDX you will
have double entries.
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
- G4POP
- Log4OM Alpha Team
- Posts: 10817
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Lost logging from JTDX
You say revisions? So did this happened after the move from V1 to V2 or after updating from a previous version of V2?
Does a manual insertion of a QSO work? like entering a call directly into log4OM no external programs involved?
73 Terry G4POP
Re: Lost logging from JTDX
Thank you for the replies. Yes upgrade from V1 to V2. Manual insertion worked from log5om.
I went through the setup again disabled everything from before and tried again. Now, it does update the log in Log4om, but JTalert gives me an error each time. Will keep reading it line by line and try again tomorrow.
Really like the interface!
I went through the setup again disabled everything from before and tried again. Now, it does update the log in Log4om, but JTalert gives me an error each time. Will keep reading it line by line and try again tomorrow.
Really like the interface!
- G4POP
- Log4OM Alpha Team
- Posts: 10817
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Lost logging from JTDX
In JTAlert there is a menu setting to set the delay of a failure to log message, set it to a long duration because sometimes logging is queued while other procedures are carried outN6GAT wrote: ↑18 May 2021, 03:55 Thank you for the replies. Yes upgrade from V1 to V2. Manual insertion worked from log5om.
I went through the setup again disabled everything from before and tried again. Now, it does update the log in Log4om, but JTalert gives me an error each time. Will keep reading it line by line and try again tomorrow.
Really like the interface!
73 Terry G4POP
Re: Lost logging from JTDX
Interesting. I started with the delay at 5 secs and tried all the way to 20. Seems like their timer is actually almost double. The log entry would only appear in log4om after I clicked the okay acknowledging the error. Then the entry would appear in the log.
(I verified my laptop is not overtaxed.)
I've gone through the help file line by line and can't see any differences between my setup and the help file.
73 de Gary
N6GAT
(I verified my laptop is not overtaxed.)
I've gone through the help file line by line and can't see any differences between my setup and the help file.
73 de Gary
N6GAT