Hi All,
Using MSHV (2.60) under linux with Cqrlog logger, has been av bit challenging due to the fact that the cqrlog wsjt-x CQ-monitor window does not monitor UDP packages from MSHV. Logging QSOs from MSHV into Cqrlog using UDP works OK, however.
I am no programmer, but reading a post from PA5KT Henk on this forum a few days ago (msg # 2734) gave me av clue. I learned that MSHV uses mode identifiers in header that differs from WSJT-X and JTDX. With this information I ventured into the cqrlog source code that I have downloaded from github, and I think I found a solution.
In cqrlog/src/fMonWsjtx.pas line 1894 onwards converts wsjtx binary mode identifiers to text:
function TfrmMonWsjtx.getCurMode(sMode: String): String;
// function getCurMode converts a wsjtx binary mode in human readable ham mode
begin
getCurMode:='';
case sMode of
chr(36) : getCurMode := 'JT4';
'#' : getCurMode := 'JT65';
'@' : getCurMode := 'JT9';
'&' : getCurMode := 'MSK144';
':' : getCurMode := 'QRA64';
'+' : getCurMode := 'FT4';
chr(126) : getCurMode := 'FT8'; // ~
chr(96) : getCurMode := 'FST4'; // `
//'+' : getCurMode := 'T10';
end;
end;
As I only operate FT8 and FT4, i added two lines to the code.
function TfrmMonWsjtx.getCurMode(sMode: String): String;
// function getCurMode converts a wsjtx binary mode in human readable ham mode
begin
getCurMode:='';
case sMode of
chr(36) : getCurMode := 'JT4';
'#' : getCurMode := 'JT65';
'@' : getCurMode := 'JT9';
'&' : getCurMode := 'MSK144';
':' : getCurMode := 'QRA64';
'+' : getCurMode := 'FT4';
'FT4' : getCurMode := 'FT4'; // For MSHV added by LB2EG nov 7th 2021
chr(126) : getCurMode := 'FT8'; // ~
'FT8' : getCurMode := 'FT8'; // For MSHV added by LB2EG nov 7th 2021
chr(96) : getCurMode := 'FST4'; // `
//'+' : getCurMode := 'T10';
end;
end;
And Viola, it works!
73 de LB2EG Richard
