Ed,

I did ask them to set the "ID" to check "Detector searches entire passband"
and "Mark previous frequency and mode", and to set all modes on
for the RX and TXid. Everything else is unchecked.

Since we are on a MARS net the frequency is ours, there should
not be any adjacent modes to cause the RSID to hunt around.
We have the AFC turned off also.

As for the "Notifications" page, I am not sure what they have set.
I presumed it was default to "Enabled". I will check that with them.

I am trying to get a standard setup for all MARS members in Ohio to use,
so were all on the same page. I would like it to be automatic,
with no extra manual intervention, and have it work every time.
It now seems we have to "cycle" the RxID and TXID off then on
to get it to work. Were just not sure because it has been working erratically.



On Sun, Mar 7, 2010 at 7:12 AM, Ed <[email protected]> wrote:
> Donald Kemp wrote:
>>
>> Just tested the RSID on the 3.20.0b3 this morning
>> with another station using the same version.
>> We could not get RSID to work between us,
>> but others with 3.20.0b2 did get our RSID and it
>> changed mode/freq as it should.
>
> Have all the testers done this::
>
>> http://www.w1hkj.com/FldigiHelp-3.20/ConfigID.html
>
> My question is whether this also needs to be set up in the Notifier tab. If
> so the Help file is missing this information and it is not enabled on a new
> default install. I'm not sure why we even put it in the Notifier tab, must
> have been a good reason somewhere at some time.
>
> Don, I would make sure the testers have also set this in the Notifier tab
> and see what results you get then.
>
> Ed W3NR
>



-- 
73,
Don, NN8B / NNN0VJM OH
_______________________________________________
fldigi-alpha mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/fldigi-alpha

Reply via email to