OK Eddie, after yours mail the combo N1MM-FLDIGI deserve an extensive
check at all. It may be that I tried it too early with N1MM. The combo,
so N1MM, is the key. I think I have got the sense of yours mail. FLDIGI
stand alone doesn't sound to me, i tried it several times and no way to
have it working as I would like. But when I wrote my first mail I wasn't
thinking to it as an engine for N1MM. I was was just comparing MMTTY
and FLDIGI stand alone, no way from my standpoint.
Now I would like to put at work my proposition to check out the new
combo. Here are some assorted thoughts, sorry for the bandwidth. It is
not a real test with a FLEX due the lack of time by me.
After half one hour of setup the combo works, even without RTFM. Now if
I just could find how to have the RX log I would be more happy. The RX
log it's a vital asset for any RTTY post contest debug on my mind. MMTTY
have it. FLDIGI seems not to have it when in engine mode.
BTW, the offsets are to be done at all trough N1MM and POWERSDR(TM). I
have done only the N1MM side by now.
Now some hours after I am pretty interested in checking out FLDIGI
inside N1MM. Looking a 3 KHz pile up with a traditional transceiver
looks pretty nice. Having the Align button inside N1MM moving the radio
QRG to the center of any filter and closing the filter, all together
with the same commands set, it's a nice thing. All the N1MM functions
are, of course, still retained.
Having tested two setups, one from scratch and one from another
N1MM+MMTTY working installation, let me say that we need to be somewhat
carefully decommissioning MMTTY. I mean that the software setup side of
N1MM will give some bad results doing all the things together. There is
something to read on how to install Fldigi fist time under N1MM on the
logger site. But there is nothing on how to decommission MMTTY and
install Fldigi. Simply do it in a two fold way. Define to null the now
in use MMTTY pointer and get rid of the sound interface. Save and close
than go back and define the sound interface to sound and set up the
fleshy installed Fldigi. Now proceed to the Fldigi setup ... and
several other things. BTW FLDIGI was already installed and it is not a
stand alone package as MMTTY. FLDIGI knows and use the user files
behavior of W7. I would retry also scratching it from the roots.
Now, if I am able to get a TXT log of the RX windows I would bet on the
usability of FLDIGI inside N1MM. In stand alone it log, in engine mode
it doesn't log, a classic two folded configuration file problem that I
hope could be easy solved without any code leve intervention.
I have some weeks to test the new setup and ask anything I could need to
the FLDIGI yahoo group before to run some programmed contests.
I will try it also with POWERSDR(tm). If the the modded combo will work
with standard radio it could only work better with the FLEX. There is
the Radio, isn't it?
I don't trust numbers ... just noisy, evanescent and weak signals will
tell what's up. Anyway the DSP filters in FLDIGI doesn't not seems to be
a wardrobe for all the seasons. Having VAC and another MMTTY instance
will tell something more. Not to have unrepeatable tests.
Let's the journey to continue . TU Eddie for yours advices and perseverance.
73 de iw1ayd Salvo
_______________________________________________
FlexRadio Systems Mailing List
[email protected]
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/
Knowledge Base: http://kc.flexradio.com/ Homepage: http://www.flexradio.com/
