Tried running JT65-HF HB9HQX (0.9.98.00) and JTAlert (2.6.15) for the first time since upgrading to v 1.23. Log QSO to Log4OM failed. These are the same versions I was running with v 1.22 without issue. I start JT65/JTAlert after Log4OM has been started (once again no change over what had worked previously). I know there are updated versions of both programs, but I'm not ready to make the change yet - unless there is a known bug.
JTAlert messages displayed on screen:
FAILURE: QSO Not logged!
ERROR Message: LOG4OM File : Unable to confirm QSO logged
Bill WB9KPT
JTAlert issue with v1.23
Re: JTAlert issue with v1.23
Hi Bill,
Quite often when I see that error message, the QSO has been logged, it is just that it takes a little longer than usual to get into the log. I have noticed that the logging screen does not auto-refresh in v1.23, so it could be there, just manually refresh the log screen and see if it really is there or not.
Cannot be of much more help until somebody gets back to me with my issue.
73 de Guy G4DWV/4X1LT
Quite often when I see that error message, the QSO has been logged, it is just that it takes a little longer than usual to get into the log. I have noticed that the logging screen does not auto-refresh in v1.23, so it could be there, just manually refresh the log screen and see if it really is there or not.
Cannot be of much more help until somebody gets back to me with my issue.
73 de Guy G4DWV/4X1LT
You've never known happiness until you're married; but by then it is too late.
Re: JTAlert issue with v1.23
After some more investigation, I have found that Communicator is not starting (yes- everything is set for administrator), so I'm going to start a new topic.
Bill - WB9KPT
Bill - WB9KPT
Re: JTAlert issue with v1.23
I've not seen an error msg, but I have noted a delay of up to 1 minute to see the DX CLUSTER listing indicate a worked status.
-
IW3HMH
- Site Admin
- Posts: 2988
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: JTAlert issue with v1.23
please NOTE:
JT65-HF is pushing QSO directly into Log4OM database *without* using Log4Om functions.
Log4OM uses an OPEN SOURCE database, and the database structure is simple and clear, so everyone can work with it.
Anyway, when you directly put informations into Log4Om database, the main user interface is NOT AWARE about a new QSO has been pushed into the database, and cannot react (aka refresh statistics) if nothing happens on Log4OM itself (a statistic refresh or a new QSO logged from Log4OM or something else).
A simple example:
You have an empty room (our database). You're watching the door (Log4OM interfaces), because this is the only access to the room.
If you see an english man entering the room (a new QSO), you know that there is 1 man inside the room, without need to see into the room, because there is only one way to enter.
If another man from italy enters through the door you know there are 2 peoples inside the room and that those are 1 from UK and 1 from ITA.
JT65 is pushing peoples in the room from the window, instead than from log4om functions, and Log4Om is not aware about that.
Occasionally Log4OM does a "recheck" of the database consistency, effectively looking inside the room and counting all peoples. This is when Log4Om reacts to new QSO pushed into the database.
It's a simple and probably ugly example (with a A+ grade english
) but i hope it's clear enough
JT65-HF is pushing QSO directly into Log4OM database *without* using Log4Om functions.
Log4OM uses an OPEN SOURCE database, and the database structure is simple and clear, so everyone can work with it.
Anyway, when you directly put informations into Log4Om database, the main user interface is NOT AWARE about a new QSO has been pushed into the database, and cannot react (aka refresh statistics) if nothing happens on Log4OM itself (a statistic refresh or a new QSO logged from Log4OM or something else).
A simple example:
You have an empty room (our database). You're watching the door (Log4OM interfaces), because this is the only access to the room.
If you see an english man entering the room (a new QSO), you know that there is 1 man inside the room, without need to see into the room, because there is only one way to enter.
If another man from italy enters through the door you know there are 2 peoples inside the room and that those are 1 from UK and 1 from ITA.
JT65 is pushing peoples in the room from the window, instead than from log4om functions, and Log4Om is not aware about that.
Occasionally Log4OM does a "recheck" of the database consistency, effectively looking inside the room and counting all peoples. This is when Log4Om reacts to new QSO pushed into the database.
It's a simple and probably ugly example (with a A+ grade english
) but i hope it's clear enoughDaniele Pistollato - IW3HMH
