If any users are experiencing lockups with LOg4OM while using JTAlert, please uncheck the 'CLEAR CALLSIGN' check box in JTALERT as we suspect this function causes the problem.
Please report to the Log4OM team any comments about this
Lockups with Log4OM and JTALert
- G4POP
- Log4OM Alpha Team
- Posts: 10817
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Lockups with Log4OM and JTALert
73 Terry G4POP
Re: Lockups with Log4OM and JTALert
Where is this "CLEAR CALLSIGN" option in JTAlert that you suspect is having an effect on LoG4OM? JTAlert can send the DX Callsign to Log4OM but does not clear the Callsign.
de Laurie VK3AMA
de Laurie VK3AMA
- G4POP
- Log4OM Alpha Team
- Posts: 10817
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Lockups with Log4OM and JTALert
I will ask Lele to contact you Laurie the instruction came from him, I dont have JTAlert so cant advise
73 Terry G4POP
- IW3HMH
- Site Admin
- Posts: 2927
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: Lockups with Log4OM and JTALert
Sorry Laurie, my fault trasmitting the info to Terry.
It's the "SEND WSJT-X DX Call to Log4OM" function that seems have some troubles with threading while receiving at the same time JT messages from the JT application
It's the "SEND WSJT-X DX Call to Log4OM" function that seems have some troubles with threading while receiving at the same time JT messages from the JT application
Daniele Pistollato - IW3HMH