Please note that at this time it is not possible to integrate JTalert with Log4OM
However direct connection to WSJT is working well including display of the WSJT station in Log4OM during the QSO with worked before indication and on line lookup.
JTalert and Log4OM version 2
- G4POP
- Log4OM Alpha Team
- Posts: 10807
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
JTalert and Log4OM version 2
73 Terry G4POP
Re: JTalert and Log4OM version 2
Can you customize an indication for a wanted station (state, DXCC, etc...) similar to JTAlert?
Also, this seems like an exciting feature! Can't wait to see the full WSJT-X integration features (and the Fldigi integration as well).
73,
Brian WB8AM
Also, this seems like an exciting feature! Can't wait to see the full WSJT-X integration features (and the Fldigi integration as well).
73,
Brian WB8AM
- G4POP
- Log4OM Alpha Team
- Posts: 10807
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: JTalert and Log4OM version 2
WSJT provides that facility for the displayed list, log4OM supplies detailed worked/confirmed details for the selected station.
Fldigi integration is similar to version 1
73 Terry G4POP
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: JTalert and Log4OM version 2
Hi Terry, as you know we have tested a Beta of JTalert in the past with V2 compatibility.
Think if Lele is rolling out V2 Laurie will be implementing V2 connectivity soon.
Think if Lele is rolling out V2 Laurie will be implementing V2 connectivity soon.
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.
- IW3HMH
- Site Admin
- Posts: 2926
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: JTalert and Log4OM version 2
Laurie has access to latest alpha releases since some months.
We also added some changes to make his life easier when parsing native JSON database fields in sqlite. I think he will add support soon
We also added some changes to make his life easier when parsing native JSON database fields in sqlite. I think he will add support soon
Daniele Pistollato - IW3HMH
Re: JTalert and Log4OM version 2
I do hope the support gets added to JT-Alert soon. I have to admit it has become part of my FT-8/FT-4 work flow. Logging from WSJT-X is working as expected though which is great. With the digital modes being so popular now, I hope JT-Alert gets an update out soon.
Aside JT-Alert not working, I am liking the new look and feel so far.
Aside JT-Alert not working, I am liking the new look and feel so far.
73 de Bill W1WRA
Re: JTalert and Log4OM version 2
This part is not working for me unfortunately. Read Manual and tried configuration but to no avail. See my related post in Error reports.
Santiago
HI8SMX
______________
73 de Santiago
HI8O (former HI8SMX) + KB8SM
web: www.hamworld.online
YouTube: hamworldonline
Twitter: @hamworldonline
Instagram: hamworldonline
73 de Santiago
HI8O (former HI8SMX) + KB8SM
web: www.hamworld.online
YouTube: hamworldonline
Twitter: @hamworldonline
Instagram: hamworldonline
- G4POP
- Log4OM Alpha Team
- Posts: 10807
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: JTalert and Log4OM version 2
The port may be being used by something else on your computer, you don't have JTalert running do you?
Try changing the port number in WSJT and in Log4OM
73 Terry G4POP
Re: JTalert and Log4OM version 2
I'm having the same issue
Info is not populating in the call entry window during a QSO ??
I changed the default port as well in case it was a conflict,
16-Jan-20 7:27:14 PM * [#=zmWK4$oZeN8eoeD6RqBN2foU=][MoveNext][10 ms] : Error in ADIF import, returning empty log
[EXCEPTION] StartIndex cannot be less than zero.
Parameter name: startIndex
doing some digging in the log file that ADIF error is on port 2237 I changed the other port to 2323
Info is not populating in the call entry window during a QSO ??
I changed the default port as well in case it was a conflict,
16-Jan-20 7:27:14 PM * [#=zmWK4$oZeN8eoeD6RqBN2foU=][MoveNext][10 ms] : Error in ADIF import, returning empty log
[EXCEPTION] StartIndex cannot be less than zero.
Parameter name: startIndex
doing some digging in the log file that ADIF error is on port 2237 I changed the other port to 2323
Last edited by EI2GLB on 16 Jan 2020, 20:13, edited 1 time in total.
Re: JTalert and Log4OM version 2
Official response
If your installing Log4OMV2 as soon as it is available, then you will be running without JTAlert as it currently does not support V2.
The next release of JTAlert, 2.15.7, due tomorrow, also DOES NOT support V2.
There are enough differences between V1 and V2, incompatible config files and log schemas, that JTAlert will be treating V2 as a separate logger.
Initially JTAlert will only support the sqlite log of V2.
There is an issue with V2 MySQL log schema that impose a significant performance hit with real-time access to the log records. MySQL logs may never be supported.
de Laurie VK3AMA
If your installing Log4OMV2 as soon as it is available, then you will be running without JTAlert as it currently does not support V2.
The next release of JTAlert, 2.15.7, due tomorrow, also DOES NOT support V2.
There are enough differences between V1 and V2, incompatible config files and log schemas, that JTAlert will be treating V2 as a separate logger.
Initially JTAlert will only support the sqlite log of V2.
There is an issue with V2 MySQL log schema that impose a significant performance hit with real-time access to the log records. MySQL logs may never be supported.
de Laurie VK3AMA
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team