The screenshots
PA3DJY
Setup using VSP problem
Re: Setup using VSP problem
- Attachments
-
- JTAlert logging.PNG (50.29 KiB) Viewed 6962 times
-
- JTAlert main.PNG (178.51 KiB) Viewed 6962 times
-
- JTAlert error.PNG (9.99 KiB) Viewed 6962 times
Re: Setup using VSP problem
Screenshots part 2
- Attachments
-
- Wsjt-x rig setting.PNG (49.09 KiB) Viewed 6962 times
-
- Log4OM Communicator.PNG (74.72 KiB) Viewed 6962 times
-
- Log4OM communicator settings.PNG (91.23 KiB) Viewed 6962 times
Re: Setup using VSP problem
Screenshots part 3
Re: Setup using VSP problem
Sorry screenshots part 3
Anyone an idea ?
73's
Gerrit
PA3DJY
Anyone an idea ?
73's
Gerrit
PA3DJY
- Attachments
-
- Log4OM communicator activity log.PNG (84.7 KiB) Viewed 6962 times
- G4POP
- Log4OM Alpha Team
- Posts: 10817
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Setup using VSP problem
I believe that you will find the alert was re an unsaved QSO?
If you check your log I am sure that the QSO was saved but JTAlert has a habit of doing this is something slows down the save process
In JTAlett somewhere you can set the alert delay, set it to the longest possible to reduce these unwarranted alerts
If you check your log I am sure that the QSO was saved but JTAlert has a habit of doing this is something slows down the save process
In JTAlett somewhere you can set the alert delay, set it to the longest possible to reduce these unwarranted alerts
73 Terry G4POP
- G4POP
- Log4OM Alpha Team
- Posts: 10817
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Setup using VSP problem
You don't have to post for each screen shot you can have multiple screen shots on one forum post
73 Terry G4POP
Re: Setup using VSP problem
Good day Terry,
I have tried your advice:
I have set the time for the alert delay to a higher number, that only results in a longer time for the error message box to be displayed.
After the 73's in a QSO it takes about 8 to 10 secons for JTAlert to come up with the not logged message.
After checking the file is not been written to the log.
Gerrit
PA3DJY
I have tried your advice:
I have set the time for the alert delay to a higher number, that only results in a longer time for the error message box to be displayed.
After the 73's in a QSO it takes about 8 to 10 secons for JTAlert to come up with the not logged message.
After checking the file is not been written to the log.
Gerrit
PA3DJY
- G4POP
- Log4OM Alpha Team
- Posts: 10817
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Setup using VSP problem
The fact that it was logging OK and suddenly it is not indicates that something changed on your computer......
Moved the logbook file
Firewall or virus protection changed through update perhaps
Change of settings in JTAlert
Server or UDP address changed in JTAlert or Log4OM communicator or both
Something got corrupted in JTAlert or WSJTX - a fresh install could have caused this or could cure it - Perhaps you upgraded to WSJT RC 3 or the latest JTAlert?
So many possibilities but for sure the issue is with your set up notLog4OM because Log4OM is passive during log writing, its JTAlert that does all the heavy lifting
Moved the logbook file
Firewall or virus protection changed through update perhaps
Change of settings in JTAlert
Server or UDP address changed in JTAlert or Log4OM communicator or both
Something got corrupted in JTAlert or WSJTX - a fresh install could have caused this or could cure it - Perhaps you upgraded to WSJT RC 3 or the latest JTAlert?
So many possibilities but for sure the issue is with your set up notLog4OM because Log4OM is passive during log writing, its JTAlert that does all the heavy lifting
73 Terry G4POP
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: Setup using VSP problem
Hi Terry,
on my end i also got a "QSO not logged" message from JTAlert. On my side this error occurs when
Internet connection is to slow. Log4OM sends to eQSL, HamQTH, Clublog and HRDlog (if this is
entered in the settings) and Log4OM will update a new entry only if those uploads are complete.
On my side every QSO will be logged (i don´t lost any) but from time to time with a bigger latency.
So in fact a slow Internet kann force this "error" which isn´t one
on my end i also got a "QSO not logged" message from JTAlert. On my side this error occurs when
Internet connection is to slow. Log4OM sends to eQSL, HamQTH, Clublog and HRDlog (if this is
entered in the settings) and Log4OM will update a new entry only if those uploads are complete.
On my side every QSO will be logged (i don´t lost any) but from time to time with a bigger latency.
So in fact a slow Internet kann force this "error" which isn´t one
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.
Re: Setup using VSP problem
Hi Terry and Juergen,
At this time all logging okay.
What i did is remove JTAlert and Log4OM and reinstalled the whole bunch.
All seems to doing fine now.
Gerrit
PA3DJY
At this time all logging okay.
What i did is remove JTAlert and Log4OM and reinstalled the whole bunch.
All seems to doing fine now.
Gerrit
PA3DJY