FT8 mode

You may post here if you are having problems with Winlog32 that others may be able to help you with. You may also report bugs so that the author may act upon them.

FT8 mode

Postby mm0amw » Sun Jul 09, 2017 12:38 pm

The new FT8 mode seems to cause a problem in WL32 when uploading to Clublog. When I try to upload a qso directly to CL , it fails and the message 'CL error in data' appears above the Callsign input box. However, if I export a qso or group of FT8 qso's as a Clublog ADIF file then upload it, it is accepted and processed as normal, anyone else seen this problem?
mm0amw
Bit of a boffin
 
Posts: 56
Joined: Sat Mar 04, 2006 4:15 am
 

Re: FT8 mode

Postby G0CUZ » Mon Jul 10, 2017 9:13 pm

Both real-time API and specific export for Clublog use same mode validation in Winlog32, so if there are any differences in handling -it is on the C/L end.
As off this time 'FT8' is NOT a valid ADIF mode and may or may not be rejected by various importing services or log programs, depending on how stringent their mode validating is.
Most of the invented 'new' modes are added to the ADIF specification in time, however I have preempted this and added it to the accepted ADIF modes in Winlog32 EXCEPT for LoTW where upon export it is mapped as DATA, as I know that the LoTW validation is very stringent and QSOs WILL be rejected at this time unless mapped in TQSL (I don't want that hassle)
The changes take effect with 7.3 build #7 available now.
73 Colin, G0CUZ
G0CUZ
Site Admin
 
Posts: 1585
Joined: Wed Jan 02, 2002 7:12 am
 

Re: FT8 mode

Postby mm0amw » Tue Jul 11, 2017 11:02 am

Hi Colin and thanks for the fix, all seems to be working fine now. I had already mapped FT8 to DATA in TQSL for LOTW.
Thanks again,
73
David, MM0AMW
mm0amw
Bit of a boffin
 
Posts: 56
Joined: Sat Mar 04, 2006 4:15 am
 

Re: FT8 mode

Postby DL4KG » Fri Aug 18, 2017 3:28 pm

Hi all,

meanwhile FT8 is an accepted mode in Lotw. Actually you have to upload your QSO manually with TQSL to get them in Lotw. Automatic upload by WL32 will lead to a DATA entry.
I am sure Colin will update WL32 soon :-)
73 de Gerald - DL4KG
DL4KG
Complete Boffin
 
Posts: 257
Joined: Wed Jan 09, 2002 5:09 am
Location: Stuttgart, Germany
 

Re: FT8 mode

Postby G0CUZ » Mon Aug 21, 2017 9:05 pm

Thanks for the info Gerald

I will add the FT8 mode for LoTW for next release, which may also feature autologging from WSJT-X which is at testing stage ATM
73 Colin
G0CUZ
G0CUZ
Site Admin
 
Posts: 1585
Joined: Wed Jan 02, 2002 7:12 am
 

Re: FT8 mode

Postby DL4KG » Sat Sep 16, 2017 4:46 pm

Hi Colin,

thanks for the new release. The WSJT-X interface works nicely. That´s really simplifying the logging process. :D
73 de Gerald - DL4KG
DL4KG
Complete Boffin
 
Posts: 257
Joined: Wed Jan 09, 2002 5:09 am
Location: Stuttgart, Germany
 

Re: FT8 mode

Postby 9a5cw » Thu Sep 21, 2017 4:19 pm

Hi Colin,
have a question about JTalert-x with Winlog32 ;)
Tryied to configure both 3 programs to comunicate together but without succes.
Followed what you have wrote on the help pages but didnt work for me (METHOD 2).
Not sure if lastqso.adi its monitored by UDP or Winlog32 check the file location?
Here its where is my lastqso.adi located:
C:\Documents and Settings\Patrik\Local Settings\Application Data\HamApps\9A5CW\logs
In JTalert-X the following port its enabled 2333. Maybe its a wrong UDP port number?

Btw WSJT-x and Winlog32 comunicate very well alone, just when i try to run also JTalert nothing happens.

Maybe i am doing something wrong ;)

best regards and 73,
Pat 9A5CW
9a5cw
New user
 
Posts: 3
Joined: Mon Jan 06, 2014 10:00 pm
 

Re: FT8 mode

Postby G0CUZ » Fri Sep 22, 2017 8:06 am

Hi Pat

Thanks for the feedback.

Method 2 uses the file capture method (lastqso.adi), so it looks like the file pointer is not correct.

Is your user name in Winlog32 '9A5CW''? as this is used to automatically generate the correct path to the lastqso.adi file.

Menu/File/Maintenance/File Maintenance - Debug, enable this option, disable and re-enable JT-Alert, inspect the 'errorlog.txt' file in your Winlog32 folder for any clues.

What operating system are you using?

73 Colin
G0CUZ
G0CUZ
Site Admin
 
Posts: 1585
Joined: Wed Jan 02, 2002 7:12 am
 

Re: FT8 mode

Postby 9a5cw » Fri Sep 22, 2017 1:23 pm

Hi Colin,
thanks for fast reply,

path to the lastqso.adi its incorrect, using here WIN XP SP3

ERROR.LOG
7.3 revision 11 21/09/17 14:48:52 frmFileChangeNotify_sub_UsernameJTAlert folder NOT found: C:\Documents and Settings\Patrik\appdata\local\HamApps\9A5CW\logs\ : C:\Users\Patrik\AppData\local\HamApps\9A5CW\logs\ 0

Its should e like this for WIN XP users:
C:\Documents and Settings\Patrik\Local Settings\Application Data\HamApps\9A5CW\logs

Well, i have made a "hard link" to a lastqso.adi JTalert original folder and i pasted it in a self made
C:\Documents and Settings\Patrik\appdata\local\HamApps\9A5CW\logs folder and now it works.

Didnt test it on other Win systems 7,8,10... maybe there its working ok.

Btw, any chance to import exact freq from lastqso.adi ?

73,
Patrik 9A5CW
9a5cw
New user
 
Posts: 3
Joined: Mon Jan 06, 2014 10:00 pm
 

Re: FT8 mode

Postby G0CUZ » Fri Sep 22, 2017 2:21 pm

Thanks for the feedback Patrick

I have sent just you an email regarding this.

73 Colin
G0CUZ
G0CUZ
Site Admin
 
Posts: 1585
Joined: Wed Jan 02, 2002 7:12 am
 
 
Next

Return to Help and Support

cron