Re: FLDigi problem with SO2V Operation
toggle quoted messageShow quoted text
When I get back home this afternoon I will find where I made the mistake. It sounds like I just didn’t change the EW2 code in the Fldigi routine..
73 Rick n2AMG
From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Sunday, June 26, 2016 7:35 AM
Subject: Re: [N1MMLoggerplus] Re: FLDigi problem with SO2V Operation
I can duplicate the problem. It only happens with fldigi, and only in DI2 - the offset frequency is correct when using MMVARI or MMTTY, but when the digital engine is fldigi, the offset in DI2/VFO B has the wrong sign in both PSK and RTTY.
Older versions of N1MM+ are available at the N1MM Logger web site at <http://n1mmplus.hamdocs.com/tiki-list_file_gallery.php?galleryId=15>. The error was introduced in version 1.0.5698 - version 1.0.5674 displays the correct frequency when used with fldigi.
My thoughts exactly - I have checked and rechecked all the settings and, for both VFOs and DI Windows the settings are identical
In the 'Mode Control' section I have changed it all to USB for both RTTY and PSK for both VFOs (just in case I had an issue with modes on the rig)
Also the two VFOs on the rig are both set to USB and to 14070.
Still getting the same results with:
Entry Window 2 (VFO B) shows 14068.5
If I now Turn off 'Auto TRXUpdate' in both DI Windows then both EW's show the correct rig freq (14070) and that is what is sent to the log (without the +ve 1500 Hz offset).
I'm leaning towards a possible coding error for the way DI2 handles the audio offsets. Would it be worth trying an older version of N1MM+ and if so, where would I get one?