- This topic has 27 replies, 3 voices, and was last updated 3 years, 2 months ago by DonZalmrol.
-
AuthorPosts
-
May 21, 2021 at 11:59 am #28866DonZalmrolParticipant
So If I remove the 0x from my ID it becomes 13000212, then I need to convert 13000212 to hex which should be C65E14 (Hex number) or 00C65E14 (Hex signed 2’s complement) correct?
Bit odd when I use Postman to test the x-headers with just the number 13000212 it works and data is posted.
If I add 0x or convert it to either HEX number it fails with the exact same error response:{ "error": "Invalid Device ID" }
May 21, 2021 at 1:04 pm #28867DonZalmrolParticipantOk, I’m an idiot… looks like not x-headers are pushed at all…
Strange as it should be pushed by my httpclient.Trying to look at my code.
May 21, 2021 at 1:54 pm #28868DonZalmrolParticipantHa found the following culprit ‘:’
Original:
client.sendHeader(“X-User-id:“, USER_ID);
client.sendHeader(“X-User-hash:“, USER_KEY);
client.sendHeader(“X-Device-id:“, DEVICE_ID);Changed to:
client.sendHeader("X-User-id", USER_ID); client.sendHeader("X-User-hash", USER_KEY); client.sendHeader("X-Device-id", DEVICE_ID);
In Wireshark I now see my x-headers being posted.
I still get an issue with the x-device-id, I reckon that still has to do with the number not being translated to HEX…May 21, 2021 at 2:18 pm #28869DonZalmrolParticipantGot it!
16:15:32.405 -> Connection to uradmonitoring platform succeeded! 16:15:32.405 -> created EXP code = /api/v1/upload/exp/01/1621606532/02/25.10/03/0/04/32.00/0B/76/0C/406.39/0E/106/0F/123/10/6 16:15:57.899 -> Response = {"success":"ok"} 16:15:58.413 -> Connection to uradmonitoring platform Disconnected.
In my setup I may not use the CRLF as looks like it messes up the connection towards the API.
May 23, 2021 at 6:19 pm #28871WolferlModeratorHi,
I made a recording with Wireshark of my unit #13000070. I hope it helps you finding out what happens.
Cheers,
WolferlAttachments:
May 25, 2021 at 7:01 am #28876DonZalmrolParticipantHi Wolferl, thanks for all the help!
I managed to get it working on my ESP32, now unit 13000212 is uploading nicely to uradmonitoring 🙂
See attached image for the result.One issue that I still need to resolve is that my timers are off with almost 5 seconds…
In short, when almost reaching 60 seconds (e.g. 55 seconds) my uploads prematurely start instead of after 60 seconds (if function set to 61).
So this means it uploads the data gathered over 55 sec. instead of 60 sec…If I comment my upload functions the timer works perfectly, its like these functions are called too soon.
Attachments:
May 27, 2021 at 8:35 am #28884WolferlModeratorHi,
You’re welcome, great you got it to work!
There is no atmospheric pressure reading on your new sensor, is that intended?Cheers,
WolferlMay 27, 2021 at 12:40 pm #28885DonZalmrolParticipantYes, intentional.
Currently awaiting the delivery of it and a LUX sensor 🙂PS: My timing issues are also resolved, it now keeps each count of both tubes in an moving average array for 60 seconds and uploads the calculated MA to uradmonitor.
May 27, 2021 at 2:35 pm #28886WolferlModeratorHi,
Great, thanks for the feedback!
Would you mind posting the project’s code somewhere (github or whatever you prefer), so other people (including me) can replicate what you achieved?Cheers,
WolferlMay 30, 2021 at 3:21 pm #28892DonZalmrolParticipantSure!
You can find my code on my GitHub page: https://github.com/DonZalmrol/GM_SI-22G_Stationary_Logger
Currently still testing it out and waiting for other parts, but all seems to be working stable for the moment.If you see things that can be improved let me know 🙂
July 10, 2021 at 7:25 pm #28933uRADMonitorKeymasterUp for writing a short blog post on this ?
July 12, 2021 at 4:41 pm #28939DonZalmrolParticipantSure, I’ve send you a pm with my details.
-
AuthorPosts
- You must be logged in to reply to this topic.