Forum Replies Created
-
AuthorPosts
-
uRADMonitor
KeymasterThat is correct, and thanks for pointing out there is no description for this parameter. I need to fix that.
I should be the altitude above sea level.
KeymasterPlease see detailed API description and the examples on the Dashboard, API tab.
To get the readings you will use:
https://data.uradmonitor.com/api/v1/devices/5100001F/cpmfor the last 24h of “cpm” data. Instead of CPM you can use any of the sensor labels supported by your device (you already got that list):
{“cpm”:”Radiation”,”voltage”:”Voltage”,”duty”:”Duty cycle”,”all”:”All”}Finally you can call
https://data.uradmonitor.com/api/v1/devices/5100001F/cpm/timestart/timestopand
https://data.uradmonitor.com/api/v1/devices/5100001F/cpm/lastAll this is explained in the API documentation, please check it out. All these calls require X-User-id and X-User-hash in headers.
KeymasterHi Pat,
You will need to send authentication data via the headers. Please see the instructions in the Dashboard, under API tab.
Let me know if this helps.
Thanks!
KeymasterThank you for this excellent contribution.
SI8B was added with a linear factor of 0.001108
It will be added to the KIT1 repo soon too!
Direct unit link: https://www.uradmonitor.com/?open=13000208&sensor=cpm
Merry Christmas!
KeymasterHi guys,
Indeed the new tube needs to be defined on the server side too, I am perfectly ok to allocating 0xC for this excellent pancake tube.
I do have one and can run the tests to determine the approximative conversion from CPM to eq dose rate, but only in a few weeks from now.So instead, we might put some approximative values in place, if @ortoSystem can help me with that. I would need background radiation readings on two units, one with the standard SBM20 tube and next to it the unit with SI8B.
Radu
KeymasterThanks for the excellent suggestions!
For the temperature, the components in your model A generate some extra heating. The server has a calibration / compensation layer , common across the various hardware models. This layer is adaptive. The correct value is the one returned by the server, this is why I encourage everyone to use the API for data access.
KeymasterYou have a CO2 sensor on your KIT1 unit? AWESOME! Can you share a few pics?
I’ll check what’s happening with the NaN on the Radiation option. Can you share your upload code sequence?
Thanks,
RaduKeymasterWhat is the IP you get? 192.168.4.XXX? Can you ping 192.168.4.1
Is your unit already connected for your Internet Router (I assume it is), do you see it in the DHCP list, on your Internet Router?
How many beeps does it produce? These are used to indicate various codes.
KeymasterAbsolutely, see this: https://www.uradmonitor.com/topic/uploading-data/
Let me know if you need any additional help.
KeymasterWe’ll need to keep an eye on this. Spikes can be triggered by high energy cosmic radiation, but technical issues (related to the compensation capacitor) can also do this.
KeymasterI just fixed it. For some reason I reverted the previous fixes commit. Sorry!
KeymasterThis idea was discussed in the past, but nothing came out of it. The radioactive@home is an excellent initiative, I could call it a predecessor for what uRADMonitor is today, however there seems to be very little activity now. Do you have any contacts there?
KeymasterIt looks great, congrats on getting this online!
KeymasterThe problem was on the frontend, it didn’t have the settings for the SI22G tube, I added them now.
Please add a HW version and a SW version too:
+’/0E/1/0F/1/’+ , this would be version 1 on both SW and HW.
Looking good! https://www.uradmonitor.com/?open=13000213&sensor=cpm
Would you post a few pictures with your device?
KeymasterAbsolutely,
I was planning to write a guide on the EXP protocol and all the upload details, but with so many things on my head I didn’t get the chance. I am showing you how to do it here, and maybe if you have the time, you can contribute with a proper article on the blog.
The EXP protocol is nothing but a sequence of :
<SENSOR IDENTIFIER>/<VALUE>that allows you to concatenate readings from multiple sensors in one upload.Method: POST
Headers:
X-User-id:<number>, is your user ID as presented on the dashboard API tab.
X-User-hash:<string>, is your user KEY, again on the dashboard.
X-Device-id:<string>, this is an 8 digit hex number. On your first call, it must be 13000000 . The server will respond with a json containing {“setid”:”13000XXX”} where XXX are also hex digits. Save this to a file, and use it every time from now on, as it is your dynamically allocated ID.URL:
https://data.uradmonitor.com/api/v1/upload/exp/01/<total seconds>/0B/<counts in CPM>/10/<tube id>Call this every minute or less (once per 10minutes, etc)
The
<total seconds>can be your linux system epoch unix time, in seconds!
The<counts in CPM>is a number
The<tube id>is defined here:
https://github.com/radhoo/uradmonitor_kit1/blob/master/code/geiger/detectors.hOther EXP constants are here, should you want to add more sensors: https://github.com/radhoo/uradmonitor_kit1/blob/master/code/misc/expProtocol.h
-
AuthorPosts