[aprssig] APRS Radiation sensor

Bob Bruninga bruninga at usna.edu
Tue Mar 22 15:27:58 EDT 2011

How about this for Radiation Telemetry:

- 3 digits.  Either in a WX report or in a Telemetry channel.
- In a weather report the identifying byte would be "X".
- So X123 would be 12 times 10^3rd nanoseverts

Using Tapio's idea (below) of 2 digits of precision and one digit of decade.


-----Original Message-----
From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On Behalf
Of Tapio Sokura
Sent: Thursday, March 17, 2011 4:40 PM
To: TAPR APRS Mailing List
Subject: Re: [aprssig] Clarification of APRS weather station data flow.


On 03/17/2011 05:29 AM, Scott Miller wrote:
> Also, unsurprisingly, there's been a big surge of interest in Geiger
> counter interfacing.  Bob, can we get a standard for sending ionizing
> radiation levels in weather reports?

I'm not Bob, but I'm sticking my spoon into the soup anyway after a
little IRC chatting.. so here goes: Anyone who's familiar with radiation
levels knows they can hugely vary in scale. So using a plain, say
three-digit, number isn't going to scale very well (i.e. 001 = 1 uSv/h,
999 = 999 uSv/h).

I'm suggesting the following: three digits, where the first two are the
significant digits (mantissa) and the last one is an exponent. Base unit
could be nSv/h, nanosieverts per hour (Sievert is the SI-unit for
ionizing radiation dose equivalent).

If abc represents the digits, the resulting radiation level would be
calculated using the formula ab * 10^c nSv/h. A few examples:

000 = special case for "reading unavailable"
010 = special (theoretical) case of 1 nSv/h or under
020 = 2 nSv/h
150 = 15 nSv/h
990 = 99 nSv/h
321 = 320 nSv/h
123 = 12 uSv/h
654 = 650 uSv/h
456 = 45 mSv/h
987 = 980 mSv/h
989 = 98 Sv/h
999 = special case for 99 Sv/h or over

So that's the digit part sorted out, now we just need a letter
identifier/tag for it..


aprssig mailing list
aprssig at tapr.org

More information about the aprssig mailing list