Forum Replies Created
-
AuthorPosts
-
uRADMonitor
KeymasterHello Marco!
I’ve seen it myself. Currently the Android App is on hold due to resources being directed to other directions (server: backend/frontend, hardware: model A3 & Model D), but we’ll see a new version of the app as well before the end of the year. Meanwhile feel free to post suggestions, requirements for features you’d like to have, or even pictures from other apps to show things you like.
Thank you!
RaduKeymasterMike, can you share more details on your setup?
KeymasterI’m happy to report this functionality is already implemented, both in firmware and in server backend, and it is now entering testing phase.
KeymasterIt looks fine, the inverter’s frequency on KIT 1.1 units is set to 12.5kHz .
KeymasterExcellent! Really happy to hear that
KeymasterGreat feedback Dustin, hope the other guys will stick to the voltage requirements too. Please post a few of your great pics on this topic as well: https://www.uradmonitor.com/topic/soldering-the-kit1/ , as the winner of the A2 will be picked from that topic.
KeymasterI had the chance to meet Sigfox at MWC 2016 in Barcelona , and established a few contacts . The only issue is that their terms are not very friendly, asking a lot of money from day 1, including the test period. So I had decided not to follow this direction anymore, going instead for the more approachable LoRaWAN technology.
uRADMonitor A3 is the first unit that will feature a LoRA modem, allowing for Low Power energy transmissions.
KeymasterThis will use great suggestions posted by @jeff and @vinz in https://www.uradmonitor.com/topic/automated-device-ids/
KeymasterIn progress. Will have this in place for the new devices to be shipped out.
KeymasterJust to let everyone now that the development section has just been opened to general public, also merged with the security section of the forum, now also open.
KeymasterA new firmware revision will drop hardcoded device IDs, instead, when a unit is first connected to the internet, it will receive its ID from the server and store it in its EEPROM. When the station owner opens the webportal, the server will match his IP with the new station, and present a registration dialog. This window will appear until the station is fully configured (user details, email, station ID, a Boolean for configuration done, all stored in a DB table). The user will then see his new station (and any other he has) in the station admin panel where more options are available
KeymasterSome very good ideas. The units can be flagged as mobile, for instance the A3 is a fixed unit, yet the first 10 units installed on buses in Cluj Napoca function as mobile units. The busses also provide real time GPS coordinates via separate HTTP Posts. So this would be possible for the KIT1 as well.
Also I’m working on a new frontend, that will show mobile units separately. There there is also a switch to toggle offline units off.
Finally, we’ll slowly move to dynamic IDs, and that implies the need for an expiration time before an unused ID can be re-assigned, taking the unused stations off the map automatically.
Lots of lines of code for all this, but getting there.KeymasterThere was an API some time ago, then it was dropped with the new backend implementation, while pending some additional work to have it back. So stay tuned on this, and feel free to ping me from time to time to check status.
Keymaster@Scherheinz sweet setup you got there!
@Keld Norman congrats on the excellent installation, right by the book!
Keymasternice experiment!
160ms 65KV 7.5mA resulting in an accumulated total dose of 0.038uSv? What was the distance from the head to the detector?
-
AuthorPosts