I think the use of RS ID and detection is important.  The issue still
remains...will others try it?

Andy K3UK

On Tue, Apr 21, 2009 at 7:02 PM, Tony <d...@optonline.net> wrote:
>
>
> Thank you Patrick...
>
> Tony -K2MO
>
> ----- Original Message -----
> From: "Patrick Lindecker" <f6...@free.fr>
> To: <digitalradio@yahoogroups.com>
> Sent: Tuesday, April 21, 2009 5:06 PM
> Subject: Re: [digitalradio] Random Hour instead of MOTD
>
>> Hello Tony and all,
>>
>> Here is an old proposal of Mike Pastorcich KF5HEY done several years ago.
>> http://f6cte.free.fr/Tom_modes.doc
>>
>> For possible ideas.
>>
>> 73
>> Patrick
>> ----- Original Message -----
>> From: Tony
>> To: digitalradio@yahoogroups.com
>> Sent: Tuesday, April 21, 2009 10:16 PM
>> Subject: [digitalradio] Random Hour instead of MOTD
>>
>>
>>
>>
>>
>> All,
>>
>> The mode-of-the-day may not be the best for what we want to achieve since
>> it tends to put the emphasis on a single mode. A Random Hour on the other
>> hand would promote the use of any mode starting at a specific time each
>> day.
>>
>> With the help of RSID and video identification, operators can randomly
>> select the keyboard mode of their choosing. The ID would be an essential
>> part of random hour since it takes the guess work out of which mode is
>> being used.
>>
>> It might be best to have both a local and universal start time. The
>> meteor scatter group uses local time to promote their random hour efforts
>> but they are dealing with a propagation mode that is limited to one or two
>> time zones so it's not the same as HF. The time issue is open for
>> suggestion.
>>
>> Fldigi and Multipsk have both the Reed Solomon and video ID. Simon
>> Brown's DM-780 has video ID only, but that may change soon. MixW has video
>> for MT63 only.
>>
>> Fldigi................ http://www.w1hkj.com/
>> HRD (DM780)
>> http://www.ham-radio-deluxe.com/Downloads/tabid/54/Default.aspx
>> Multipsk........... http://f6cte.free.fr/index_anglais.htm
>>
>> So there you have it. Suggestions welcome...
>>
>> Tony -K2MO
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
> 

Reply via email to