Excellent question.

A/KIT1/A3 compute CPM counting all pulses during every minute. Then they send the data online.

Assuming the radiation field would be above the background level, you would sense the source if the one-minute average would also be above the background level. But keep in mind the inverse square law, which leaves little detection space if your speed increases distance from source very quickly.

I’ll write it down in an equation if I find the time.

Hello Urs,

While this feature is not available, it is definitely worth some additional research. I will keep it in mind for a next firmware update.

Hello Wolferl,

Please see the files attached, and use them as a starting point. I am using CrossAVR over Eclipse for the AVR Toolchain, and the Makefile is auto generated.

This is great stuff, Wolferl, thank you!

I agree, we’ll have that in place once the notifications are implemented. As a first step, all unit owners received an account here. That account will be used for the notifications.

The code runs with errors:
[Error] TypeError: $ is not a function. (In ‘$(“#status”)’, ‘$’ is undefined)
downloadUnits (radiation-monitoring:325)
Global Code (radiation-monitoring:424)

You will need to add JQuery too, it is also in JSFiddle, top-left of the screen. But easier, here is what you need to add to the blog’s headers:

  	<link rel="stylesheet" href="http://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css">
  	<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.12.2/jquery.min.js"></script>
  	<script src="http://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/js/bootstrap.min.js"></script>
	<script src="http://cdnjs.cloudflare.com/ajax/libs/dygraph/1.1.1/dygraph-combined.js"></script>

Apparently if works in Safari right away, while Chrome says “Failed to load resource: net::ERR_INSECURE_RESPONSE” and the code only shows the purple “Loading”.

“Your resource probably use a self-signed SSL certificate over HTTPS protocol. Chromium, so Google Chrome block by default this kind of resource considered unsecure. ”

You can bypass this this way :

Assuming your frame’s URL is https://www.domain.com, open a new tab in chrome and go to https://www.domain.com.
Chrome will ask you to accept the SSL certificate. Accept it.
Then, if you reload your page with your frame, you could see that now it works
The problem as you can guess, is that each visitor of your website has to do this task to access your frame.

You can notice that chrome will block your URL for each navigation session, while chrome can memorise for ever that you trust this domain.

This problem will be fixed in a more elegant way, as soon as the entire site moves to HTTPS, soon.

LE: if you can use the code , changing the HTTPS to HTTP in the api calls in the javascript code (not on JSFiddle), then it will work as well.

@nox built the uRADMonitor-X, it is close to what you want: https://www.uradmonitor.com/topic/uradmonitorx/