- This topic has 70 replies, 14 voices, and was last updated 3 years, 7 months ago by Beniamin Ciuta.
-
AuthorPosts
-
May 14, 2016 at 8:20 am #2933SteveParticipant
1.1.0 works well for me, including the logging.
August 23, 2016 at 8:05 pm #3333Mads BarnkobModeratorVoltage is not updated in uRADMonitorX for my old A1 model, now with 118 firmware. Maybe due to different prefix spelling? “vol:” vs “voltage:”
webserver:
URADMONITOR 11000003
type:1 hw:100 sw:118 SBM20radiation:18CPM (22.76CPM)
temperature:29.00Cvol:379V (46%/15.50kHz)
uptime:2764s wdt:3seth:10.0.0.24 (23.239.13.18)
http:200 46/46JSON: {“data”:{ “id”:”11000003″,”type”:”1″,”detector”:”SBM20″,”voltage”:378,”cpm”:27,”temperature”:29.89,”uptime”: 160}}
My KIT1 which reports voltage fine in uRADMonitorX
webserver:
uRADMonitor 51000042
type:5 hw:103 sw:115 SBM20radiation:14CPM
average:21CPM
voltage:378V (69%)
ip:10.0.0.23
http:200JSON: {“data”:{ “id”:”51000042″,”type”:”5″,”detector”:”SBM20″,”cpm”:18,”temperature”:0.00,”uptime”: 70203}}
August 23, 2016 at 9:08 pm #3334cristianst85 (nox)ModeratorHi, @Mads Barnkob.
You are right. Instead of pasting is here can you attach it as a HTML page? For example, open the device web page in your browser > choose File > Save Page As…
Thank you.
August 24, 2016 at 7:52 am #3337uRADMonitorKeymasterHi guys! I added an example from an A3 unit, that also contains data recorded by A / A2. It might be safer to use the JSON content, as that doesn’t change.
Also please let me know if you think we should stick to the previous mini-webpage labels, we can still do that, as with the exception of Mads, v118 is not yet released.
Attachments:
August 25, 2016 at 5:10 pm #3343cristianst85 (nox)ModeratorThe reason I choose to parse only the data from the web page was because it provided more information about the device itself including the response status (HTTP Code) received from uRADMonitor server. Keeping the labels somewhat consistent would be nice.
P.S. Many thanks for the samples from A3 unit.
August 25, 2016 at 5:44 pm #3344cristianst85 (nox)ModeratorOne quick question, what is the meaning of
15/15
in the sample you provided?August 25, 2016 at 9:38 pm #3345uRADMonitorKeymasterok nox, I’ll revert the labels for consistency. Mads, time for an update! 🙂
15/15 is packets OK (that received http 200) / total packets sent . Normally, these should be equal.
August 26, 2016 at 7:57 am #3349Mads BarnkobModeratorOk 🙂
Just send me the hex file and i’ll flash it tonight
September 18, 2016 at 6:13 pm #3529Pat MolloyParticipantHi, just installed a new A3; all working fine – sitting at 192.168.254.11 on local network.
uRadMonitorX (running v0.37.0.39201) on Windows 10 64bit, and getting “Device data fetch error”
This is in the logfile (a lot of times!)
[2016-09-18 19:10:10] Device data fetch error. Exception: System.ArgumentOutOfRangeException: Length cannot be less than zero.
Parameter name: length
at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
at uRADMonitorX.Core.Device.DeviceDataReader.internalParse(String rawText)
at uRADMonitorX.Core.Device.DeviceDataHttpReader.Read()
at uRADMonitorX.Core.Fetchers.DeviceDataFetcher.doWork(Object o, EventArgs e)September 18, 2016 at 10:13 pm #3530cristianst85 (nox)ModeratorHi, @Pat Molloy.
Currently, A3 model is not supported, but I need some time to add at least some partial implementation…
Btw, you are using an older version of the app. Please check the official release page on GitHub for the latest version.
P.S. It seems that due some security rules (error code 15) I cannot post messages with links. 🙁
September 19, 2016 at 9:16 am #3531Pat MolloyParticipantHi there,
Ok. thanks for the quick reply. Thought that might be the case. I’ll grab the right version in the meantime !
Pat
September 21, 2016 at 5:35 pm #3533cristianst85 (nox)ModeratorI’ve just released a new version (1.1.1) with partial support (i.e. radiation, temperature, pressure) for A3 model.
September 22, 2016 at 10:13 am #3534Pat MolloyParticipantVery cool! Thanks 🙂 I will give it a go.
Pat
September 22, 2016 at 10:23 am #3535Pat MolloyParticipantHi, no luck I’m afraid ..
[2016-09-22 11:22:18] Device data fetch error. Exception: System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at uRADMonitorX.Core.Device.DeviceDataReader.internalParse(String rawText)
at uRADMonitorX.Core.Device.DeviceDataHttpReader.Read()
at uRADMonitorX.Core.Fetchers.DeviceDataFetcher.doWork(Object o, EventArgs e)September 22, 2016 at 10:43 am #3536cristianst85 (nox)ModeratorI’ll need a sample from your device readings. For example, open the device web page in your browser > choose File > Save Page As… and then attach it here.
-
AuthorPosts
- You must be logged in to reply to this topic.