But....  as mentioned earlier in this thread.. the average person you
are training has no clue about digital modes and hence the fact that
they get stumped on the 3583 'thing".  This issue is not really FLdigi
related but it reveals the fundamental problem associated with
emcomms...  use by competent operators.  Twenty years ago, I was in a
air-plane crash simulated disaster and all the ambulance and police
communications failed because they jammed their frequencies and were
not adept enough to figure out what to do next.  My PK232 and small
Icom 2M rig adapted to the conditions and got all the traffic through.
 Twenty years later we have numerous emcomm hams that are being
trained in use of NBEMS but there is a danger that we turn them in to
appliance operators just like the ambulance drivers.  When NBEMS was
first introduced a few years back, Skip espoused a belief that NBEMS
had some advantages over other systems in that it it required no
special training and employed methods used by digital hams in their
everyday casual QSOs.  I will argue that while wanting to keep it
simple is a laudable idea, hams being trained should also be trained
on how to get frequency readout to work .

Andy K3UK


On Sat, May 1, 2010 at 8:29 AM, David Kleber <[email protected]> wrote:
>
>
> Gary Wescom wrote:
>
> Gary,
>
> The point here is that Harry and I, here in WPA, are training TONS of people
> on NBEMS for use in EmComm.  We travel within (and occasionally beyond) the
> WPA ARES section to do demo's, training and occasional station setups.
>
> The 3583 thing is obviously not that big of a deal, but it comes up as a
> question over and over again and neither the instructions or the
> explanations for it here make much sense to me or the people we're training.
> It just winds up being a waste of our time having to continually address
> this issue.
>
> One thing we're getting ready to do after the next major release is to do a
> fresh install on the various platform versions and standardize all the
> settings and macros for our current and future volunteers. We will have the
> extended characters checked, long interleave for MT63, auto detection and
> extraction, RSID for only our selected modes of operations, etc. Then we'll
> copy and save the program files that hold this data and simply have our
> members copy our standardized files and overwrite the ones in their folders.
>  We'll have the CAT/Loggin display set to be hidden as it serves no useful
> purpose for the vast majority of our operations here in WPA.
>
> -Dave, KB3FXI
>
>
>
>> For the folks who manually enter a frequency, starting with zeros on the
>> initial load should not be any different than starting with 3.580.  Or am
>> I
>> missing something here and everyone does actually operate on 80 meter
>> psk31 all the time  : -)
>>
>> I dunno, just my spin on this subject.
>>
>> Gary - N0GW
>>
>> ----- Original Message ----- From: "w1hkj" <[email protected]>
>> Cc: <[email protected]>
>> Sent: Friday, April 30, 2010 8:21 PM
>> Subject: Re: Rig Control/Freq Display request
>>
>>
>>> I understand that new users might be confused, especially if they do not
>>> take the time to read the on-line help.  My wife thinks I am a perfectly
>>> anal engineer because I always read the manual for a new car ... from front
>>> to back and then from back to front.  She never opens one up.  I know how to
>>> use every control on the car.  She constantly asks me how to work the
>>> windshield wipers and the lights.
>>>
>>> The frequency control reads 3580.000 because I decided that was a proper
>>> default value.  It is detailed in the owner's manual.  Just read it and
>>> insist that your new users do so also.  If they want to fly the airplane
>>> they should understand what the controls are for and how they work.  They
>>> may never fly loops but they better know how to handle a stall.
>>>
>>> It stays as is.
>>>
>>> Dave, W1HKJ
>>>
>>> David Kleber wrote:
>>>>
>>>> Disagreed with all...
>>>>
>>>> My point is only on the initial startup and why in the world you would
>>>> display a frequency that is neither entered by the user or pulled from 
>>>> their
>>>> rig???
>>>>
>>>> 3.583 display upon the load of the software implies that there is some
>>>> sort of rig control being deployed, and it's confusing to new users. It 
>>>> even
>>>> confuses people who are not complete idiots.
>>>>
>>>> Upon start up on a new install, what in the world would be the problem
>>>> with having what appears to be a rig control display show all zeros when
>>>> there is no rig control being deployed???????????????????????
>>>>
>>>> From there, if a user changes the frequency, by all means... have it
>>>> save that figure... but why have a random frequency appear in the display
>>>> when there is no rig control deployed.
>>>>
>>>> -Dave, KB3FXI
>>>>
>>>>
>>>> Rick Kunath wrote:
>>>>>
>>>>> On Friday 30 April 2010 07:00:16 pm Mike Haynes wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I can see where this might be confusing to a lot of people.
>>>>>>
>>>>>> I do not wish to see it disappear.  It is an important function to set
>>>>>> when
>>>>>> using logging and QSO frequency
>>>>>> instead of calculating from the waterfall.
>>>>>
>>>>> I agree. The frequency display should remain as it is.
>>>>>
>>>>>> Personally I set it up each time I start fldigi and each time I do a
>>>>>> band
>>>>>>  or freq change on the radio.  I do not use
>>>>>> rig control and on my home shack rig that isn't possible anyway.
>>>>>
>>>>> The same for me.
>>>>>
>>>>> The rest is a training issue.
>>>>>
>>>>>> So if it is a big issue then perhaps default to all zeros might be the
>>>>>> option.  Then the QSO frequency displayed would
>>>>>> reflect that of the waterfall.
>>>>>
>>>>> No, don't set to zeros. Because if I enter the correct rig frequency in
>>>>> the freq display, then the logged frequency is the rig plus the waterfall
>>>>> offset, as it should be.
>>>>>
>>>>> This is all working as it should an das it was designed.
>>>>>
>>>>> Rick Kunath, k9ao
>>>>>
>>>>> _______________________________________________
>>>>> fldigi-alpha mailing list
>>>>> [email protected]
>>>>> https://lists.berlios.de/mailman/listinfo/fldigi-alpha
>>>>>
>>>>>
>>>> _______________________________________________
>>>> fldigi-alpha mailing list
>>>> [email protected]
>>>> https://lists.berlios.de/mailman/listinfo/fldigi-alpha
>>>>
>>>
>>> _______________________________________________
>>> fldigi-alpha mailing list
>>> [email protected]
>>> https://lists.berlios.de/mailman/listinfo/fldigi-alpha
>>
>> _______________________________________________
>> fldigi-alpha mailing list
>> [email protected]
>> https://lists.berlios.de/mailman/listinfo/fldigi-alpha
>>
>>
> _______________________________________________
> fldigi-alpha mailing list
> [email protected]
> https://lists.berlios.de/mailman/listinfo/fldigi-alpha
>
_______________________________________________
fldigi-alpha mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/fldigi-alpha

Reply via email to