Forum Replies Created
-
AuthorPosts
-
entaro
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
KeymasterHi Jarle,
You can send it back to me for resoldering.
I will send you my address by mail.
KeymasterThey are called “USB to DC 2.1mm” cable , here’s an example: http://www.ebay.com/itm/302420642414
Keymaster@Mads exposed his two units to Tesla Coils.
KeymasterAwesome!!!
Yes, please do a post on this when you find the time. You can post it directly on the blog.
KeymasterThe temperature and humidity values are being compensated on the server. This is needed because of internal heating caused by various electronic components.
KeymasterHi Guys,
Thanks for your excellent feedback.
There is a field of improvement in the recognition of “offline” state.
There are two distinct things here. One is the device seeing itself connected to the Wifi, and a separate thing is the server seeing the device as online. The former works by checking if there is a local IP allocated in the LAN, while the second checks if any data was received not older than 30minutes. After 30minutes of not receiving data, the server will mark any unit as offline, and you would see it on the map accordingly.
Regardless of the two, all data is collected on the SDCARD in the CSV files. But indeed, this is not used for SYNC. I will enforce this for the next SYNC implementation and you will have it with the new firmware.Build quality really isn’t what I’d expect from such a relatively pricy device: the screws were rusting at delivery, at least one of the devices had the beginnings of rust on the tube and the shielding internally, both lost the cap on the GPS antenna (double sided tape seems to have solved that), both have creaking touch screen enclosures that don’t quite align the screen, one of the switch plastic was just damaged.
I agree with you on this and I regret it myself. I will probably be able to provide updated plastic bezels and mail them to you when available. The lack of time in finalising this already delayed project contributed to the outcome.
Your other suggestions are excellent and some are already on the todo list for the new firmware. Some are only possible with hardware modifications, such as turning off charging leds or using the soft button for power down. For the location, the only option is to mark your unit as hidden in the dashboard, but more options will be added to address this.
@sjmcinness
You will need tweezers. Open the end panel, facing the radiation sensor and GPS led. Be extra careful not to damage the sensitive LND712 Geiger tube, as it has a very thin mica window that can be punctured in an instant.
Use the tweezers to open the IPEX connector (just drag it) and release the GPS Antenna cable. Carefully put the new cable’s connector over the motherboard connector and press it with the tweezers. This is an easy replacement, you just need to be careful with the LND712 tube.
For a first test, don’t force the IPEX connector through the tiny hole (yes, it can be done), first decide on the antenna replacements.
Please keep us informed on the results!
edit/ps: quoted text size changed.September 3, 2017 at 5:34 pm in reply to: Unit 11000003(model A) vs. Unit 51000042 (KIT1) noise sensitivity #4828KeymasterThis is great Mads, we should do more tests on this, however I think getting the right protection to the monsters you’ve built will not be easy. They should include Tesla Coil RF Testing at the CE lab where they got me the certifications 🙂
What happens if you put vacuum tubes on your top-load while close to the detectors?
KeymasterHi Alex,
How did you solve the router problem?
Link to your unit: https://www.uradmonitor.com/?open=82000094
Thanks,
Radu -
AuthorPosts