Log4OM

Hi, I tried to add the MSK144 mode to the ModeList_user.csv file as follows. MSK144 is replacing FSK441 for Meteor Shower contacts.

MFSK16;MFSK16;MFSK;MFSK16
MSK144;MSK144;MSK144
MT63;MT63;MT63

However, after I launched the program I'm not seeing any modes at all. I used MSWorks to edit the CSV file. I reset back to the defaults, and now I see modes again.

Also, how would I enable the proper range of RST values for this mode (assuming I can get it added to the list)? They are of the form -xx to +xx.

Bill, WB9KPT

wb9kpt wrote:Hi, I tried to add the MSK144 mode to the ModeList_user.csv file as follows. MSK144 is replacing FSK441 for Meteor Shower contacts.

MFSK16;MFSK16;MFSK;MFSK16
MSK144;MSK144;MSK144
MT63;MT63;MT63

However, after I launched the program I'm not seeing any modes at all. I used MSWorks to edit the CSV file. I reset back to the defaults, and now I see modes again.

Also, how would I enable the proper range of RST values for this mode (assuming I can get it added to the list)? They are of the form -xx to +xx.

Bill, WB9KPT

Bill,

MSK144 is not a recognised ADIF mode at this time so be aware that any QSO's uploaded to award programs like DXCC will probably be rejected. See the current ADIF mode list below.
However if you still want to change it, try editing the csv file using notepad and of course just save it don't use save as.

You can edit the RST values for Digi mode, CW Mode, Voice Mode & JTxx Mode by going to options/select config tab and enabling expert mode, same as for editing the modes list etc

Thanks Terry, it turns out the the MSWorks spreadsheet software was corrupting the ModeList_user.csv file on a Save. I used Excel and all is well now...

Understand your comment about ADIF "compatibility" with award programs, my biggest concern is with LOTW where I can assign MSK144 to DATA or MSFK using TQSL (suggestions I got from other hams on Ping Jockey).

Regarding the RST values is there a way to indicate that MSK144 belongs with the JTxx Mode of values (uses same range as JT9)?

Bill, WB9KPT

wb9kpt wrote: Regarding the RST values is there a way to indicate that MSK144 belongs with the JTxx Mode of values (uses same range as JT9)?

Bill, WB9KPT

Log4OM recognises the authorised ADIF Data modes as data so try using MSK144 as a sub mode of FSK441, like.............

FSK441;MSK144;MSK144

or a sub mode of MFSK, like............

MFSK;MSK144;MSK144

Hi Terry, thanks for the suggestion but that didn't work. MSK144 has signal reporting similar to JT9 (+XX to -XX). So I tried associating it as a sub mode of JT9, but that didn't work either. I wonder if because I have it listed as main mode (so it shows up in the mode drop down list), it can't also be a sub mode.

Do you know if there is a configuration I can change to associate MSK144 directly with the reportlistJT.txt file?

Bill WB9KPT

Hi Bill, we have a new release ready, i'll check if we can fix that

Added a long awaited file: RSTMode.csv
It maps modes with the relative RST list as follow:

PHONE>SSB|USB|LSB|AM|FM
CW>CW
JT>JT|ROS|FSQ|MSK

If mode start with SSB the loaded RST set will be the voice set.
If mode start with CW the loaded RST set will be the CW set

If nothing matches will be loaded the DIGITAL set

Daniele, sounds like a good idea, with flexibility for the future. Let me know if I can help with testing this feature for MSK144.

Otherwise, I will look forward to the release!

Bill WB9KPT

Thanks, the V1.27 release resolved my problems with RST and MSK144!
Note that I added +01 to +25 to the "reportlistJT.txt" file to accommodate positive signal report values.

Bill WB9KPT