Unit reboots every 4 minutes

uRADMonitor

Home &rsaquo; Forum &rsaquo; Support &rsaquo; Unit reboots every 4 minutes This topic has 3 replies, 2 voices, and was last updated 5 months ago by uRADMonitor. Log In Register Lost Password Viewing 4 posts - 1 through 4 (of 4 total) Author Posts May 18, 2026 at 11:14 am #30259 brotulixParticipant Hi, I just noticed my unit (Model A) stopped reporting to the network about a month ago. Currently running on a bench lab supply to rule out power supply issues (as that seems to be a common issue for others in the forum). When checking its IP, it does produce output (see example below), but when the wdt counter reaches 240, the unit reboots. I have checked that I can at least reach the stated server IP using traceroute, but not knowing what to look for in the communication I haven’t yet run Wireshark. Is there anything I can do to troubleshoot further? Sample output: uRADMonitor 110000BC type:1 hw:108 sw:126 SBM20 radiation:12CPM temperature:23.75C voltage:378V duty:19% frequency:15.50kHz uptime:23s wdt:22s/240s ip:192.168.13.37 server:66.228.41.43 interval:60 http:0 0/0 JSON [345] May 18, 2026 at 4:06 pm #30260 uRADMonitorKeymaster Unit seems ok , but traffic to the server is blocked. Do you ever get anything else than http:0 0/0 ? This means HTTP post return code (must be 200 to reset Watchdog), and x/y is number of successful packets (that got 200) / total packets attempted. Check the router security , it must be blocking the sensor’s traffic. May 19, 2026 at 9:06 pm #30267 brotulixParticipant You’re right, of course. Something was blocking the traffic. Neither my ISP or my firewall were configured to do any blocking, but a reboot of both firewall and router seems to have solved it. Thanks! May 21, 2026 at 8:16 am #30268 uRADMonitorKeymaster Interesting . The traffic itself is a simple HTTP Post to send the data, not unlike a browser opening a webpage. Good that the problem is gone! Author Posts Log In Register Lost Password Viewing 4 posts - 1 through 4 (of 4 total) You must be logged in to reply to this topic. Log In Username: Password: Keep me signed in Antispam 2x(3+4)=? Log In

This topic has 3 replies, 2 voices, and was last updated 5 months ago by uRADMonitor.

Viewing 4 posts - 1 through 4 (of 4 total)

Author

Posts
May 18, 2026 at 11:14 am #30259

brotulix
Participant

Hi,

I just noticed my unit (Model A) stopped reporting to the network about a month ago.
Currently running on a bench lab supply to rule out power supply issues (as that seems to be a common issue for others in the forum).

When checking its IP, it does produce output (see example below), but when the wdt counter reaches 240, the unit reboots.

I have checked that I can at least reach the stated server IP using traceroute, but not knowing what to look for in the communication I haven’t yet run Wireshark.

Is there anything I can do to troubleshoot further?

Sample output:

uRADMonitor 110000BC
type:1 hw:108 sw:126 SBM20
radiation:12CPM
temperature:23.75C

voltage:378V
duty:19%
frequency:15.50kHz
uptime:23s wdt:22s/240s

ip:192.168.13.37
server:66.228.41.43
interval:60 http:0 0/0
JSON [345]

May 18, 2026 at 4:06 pm #30260

uRADMonitor
Keymaster

Unit seems ok , but traffic to the server is blocked.

Do you ever get anything else than http:0 0/0 ? This means HTTP post return code (must be 200 to reset Watchdog), and x/y is number of successful packets (that got 200) / total packets attempted.

Check the router security , it must be blocking the sensor’s traffic.

May 19, 2026 at 9:06 pm #30267

brotulix
Participant

You’re right, of course. Something was blocking the traffic.
Neither my ISP or my firewall were configured to do any blocking, but a reboot of both firewall and router seems to have solved it.

Thanks!

May 21, 2026 at 8:16 am #30268

uRADMonitor
Keymaster

Interesting . The traffic itself is a simple HTTP Post to send the data, not unlike a browser opening a webpage. Good that the problem is gone!
Author

Posts

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.