[ARDF] ARDF Digest, Vol 90, Issue 4

Sun Jan 9 14:29:23 PST 2011

 Any cellphones are banned and cannot be used. Most of the WC class competitions have cell jamming equipment at the start location. To avoid violation of the rules application can be runned on iPod instead of iPhone. But anyway GPS is another prohibited item. 
I doubt it ever will be allowed, but I like a general idea of SDR. I would include navigation mechanism with autopilot to get a user to fox location after athlete have a valid bearings. I have developed a prototype for iphone and it works with exception of iPhones compass is too bad. Otherwise everything is working perfectly. I have submitted code an application to Charles. I hope we can incorporate it.

73,
Vadim

Sent from iPhone

Jan 9, 2011, в 15:00, ardf-request at kkn.net написал(а):

> Send ARDF mailing list submissions to
>    ardf at kkn.net
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>    http://www.kkn.net/mailman/listinfo/ardf
> or, via email, send a message with subject or body 'help' to
>    ardf-request at kkn.net
> 
> You can reach the person managing the list at
>    ardf-owner at kkn.net
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ARDF digest..."
> 
> 
> Today's Topics:
> 
>   1. Musings on an ARDF user interface (Charles Scharlau)
>   2. Re: Musings on an ARDF user interface (Jay Hennigan)
>   3. Smart phones and stupid cheaters (Charles Scharlau)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sat, 8 Jan 2011 22:54:03 -0500
> From: Charles Scharlau <charles.scharlau at gmail.com>
> Subject: [ARDF] Musings on an ARDF user interface
> To: ardf at kkn.net
> Message-ID:
>    <AANLkTim2Tk5mCRYme8Oe8QgsoEaE+=Wm=iS8KRoXoQrw at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> I would be interested to hear others comments and suggestions regarding
> ideas for new ARDF receiver features and interface design. Below are some
> ideas that should be achievable in the first version of a software defined
> ARDF receiver. Maybe you have some other/better ideas?
> 
> 1. Instead of an "S-meter" the ARDF receiver will feature a "D-meter".
> Instead of just relative signal strength, the D-meter will display
> approximate distance (in meters/km) to the fox. The D-meter can be
> calibrated by the user during ARDF practice sessions, and the calibration
> will be stored non-volatilely.
> 
> 2. An internal clock can be synchronized to the fox schedule whenever it is
> convenient, including long before the event starts if timing information is
> available. For example, if it is known that the foxes will by synchronized
> to UTC.
> 
> 3. The ARDF receiver will devote a full display to each fox, and
> automatically switch between displays at the synchronized time. (Display
> transitions can be overridden if desired.)
> 
> 4. Each fox display will provide the following information:
> a. Time of day
> b. Seconds remaining in the fox transmission
> c. Fox number
> d. Battery level
> e. Real-time signal strength (average and peak)
> f. Signal strength history chart (maximum average-signal-strength observed
> during each minute of previous transmission intervals for the past 60
> minutes
> g. Real-time bearing (if digital compass is available)
> 
> 5. Some kind of audio tone signal-strength indicator (aka, whoopee mode). It
> seems that quite a few new and old ideas might be incorporated here. Russian
> receivers have long used a tone mode that could be simulated in software,
> and the Australian sniffers incorporate a one-ear
> rising-pitch-with-rising-signal-strength paradigm. Perhaps both can be
> accommodated, and something new as well, and have them user selectable...
> with an "off" selection for the purists.
> 
> Comments, suggestions?
> 
> 73,
> Charles
> NZ0I
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Sat, 08 Jan 2011 20:47:57 -0800
> From: Jay Hennigan <jay at west.net>
> Subject: Re: [ARDF] Musings on an ARDF user interface
> To: ardf at kkn.net
> Message-ID: <4D293DFD.5020108 at west.net>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> On 1/8/11 7:54 PM, Charles Scharlau wrote:
>> I would be interested to hear others comments and suggestions regarding
>> ideas for new ARDF receiver features and interface design. Below are some
>> ideas that should be achievable in the first version of a software defined
>> ARDF receiver. Maybe you have some other/better ideas?
> 
> I can't get the ARDF signals to appear.  The finger tap sequence doesn't
> work for me.  It's like the first tap is ignored.  I'm usung an iPhone
> 3GS.
> 
> --
> Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net
> Impulse Internet Service  -  http://www.impulse.net/
> Your local telephone and internet company - 805 884-6323 - WB6RDV
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Sun, 9 Jan 2011 11:52:45 -0500
> From: Charles Scharlau <charles.scharlau at gmail.com>
> Subject: [ARDF] Smart phones and stupid cheaters
> To: ardf at kkn.net
> Message-ID:
>    <AANLkTi=PHEmVK4zFRhmMCqoCkfznmd5sYc7CE77f7Suq at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> The idea of using a smart phone as an ARDF competition receiving device has
> always carried with it the concern that such a device would necessarily be
> banned in competitions. Having developed an app, I conclude that although
> current rules would ban communication-capable devices in competitions, an
> exception SHOULD be made for smart phones. Furthermore, doing so could
> actually PREVENT cheating by the competitor carrying the smart phone, and
> others participating in the competition.
> 
> The last two sentences above probably sound outlandish, and the explanation
> will take a few paragraphs to explain. Please bear with me as I lay out the
> essential points.
> 
> 1. It is very easy to create a smart phone app with the following
> characteristics:
> a. It records the place, date and time when it is launched.
> b. It detects and records whenever it is closed, or it gets put into the
> background in a multitasking OS.
> c. It provides the above information when queried by an external device.
> 
> 2. Rules could be put into place allowing (even encouraging) competitors to
> register their smart phones for carrying in the competition, provided that
> they agree to run a program described in (1) during the entire time that
> they are competing. (Perhaps their smart phones would also be impounded with
> their receive equipment. But even that might not be necessary.)
> 
> 3. Anyone found to possess an unregistered cell phone, or one not running a
> "certified" app, would be disqualified under the same rules as today.
> 
> 4. At the end of the competition, all competitors with registered smart
> phones would be required to download their app's data to the official
> database for analysis. Failing to do so, or if the data shows that their
> phone exited the monitoring app at any point during the competition, could
> get the competitor (and perhaps their team)  disqualified from the
> competition.
> 
> A very simple app as described above, then, could allow smart phones to be
> carried in ARDF competitions, and in any other competition in which they are
> currently banned due to cheating concerns. The main sticking point is how to
> certify, and verify, the apps that monitor the phone's use. But I don't
> think that is an insurmountable obstacle.
> 
> If smart phones continuously running an appropriate app are allowed in
> competition, then that opens up the possibility of using them to enhance
> rules enforcement. Consider that a monitoring app might also support camera
> function, and sending photos along with GPS location and time of photo
> directly to an official competition monitoring e-mail address? In that case,
> all competitors armed with smart phones could potentially provide evidence
> of cheating while on the course, but could not utilize their cell phones for
> other purposes without being disqualified.
> 
> There are many other possibilities this concept opens up. I think it is
> definitely time to start the discussion.
> 
> 73,
> Charles
> NZ0I
> 
> 
> ------------------------------
> 
> _______________________________________________
> ARDF mailing list
> ARDF at kkn.net
> http://www.kkn.net/mailman/listinfo/ardf
> 
> 
> End of ARDF Digest, Vol 90, Issue 4
> ***********************************