Home › Forum › Support › Unit offline

Log In Register Lost Password
Viewing 13 posts - 16 through 28 (of 28 total)
1 2
  • Author
    Posts
  • July 4, 2018 at 12:33 pm #5897
    Bjorn Roesbeke
    Participant

    Port forwards / DNAT do not influence the uradmonitor device as it does not need to be accessed from outside your network, the uradmonitor device initiates the connection.
    SNAT rules must be valid but most SOHO routers don’t even offer options to change this.
    Afaik the uradmonitor can use any outgoing port from 1 to 65535
    going to port 53 for 8.8.8.8 or 8.8.4.4
    going to port 80 for data.uradmonitor.com
    going to port 80 for uradmonitor.com
    broadcast to port 67

    Can you bypass your router at all? I feel like we’re going in circles here.

    July 4, 2018 at 7:13 pm #5898
    Kiwirad
    Participant

    Hi all

    I’ve been through router setting very carefully, there are no firewall rules (other than port forwarding to other devices) and the device has full access to 8.8.8.8

    What port does the uRad use? I’m wondering if a port is being forwarded to another device that it needs?

    July 6, 2018 at 8:26 pm #5899
    uRADMonitor
    Keymaster

    It’s just a basic HTTP call, with a TCP/IP socket opening port 80 on the remote server.

    Is it possible to try it on a different network just as a quick test to rule out some of the possible issues?

    July 12, 2018 at 8:11 am #5918
    Kiwirad
    Participant

    Hi all, I can’t see any obvious firewall issues and the unit has access to 8.8.8.8

    I’m wondering what port the uRad uses, I have a number of ports forwarding settings in the router. Only thing I can think of

    Thoughts?

    July 14, 2018 at 7:55 am #5952
    Kiwirad
    Participant

    Doh – please ignore the repeated question on ports. I didn’t see it coming up in the thread for some reason so posted it again.
    Silly of me…apologies….thanks for all your help….

    July 14, 2018 at 12:49 pm #5953
    uRADMonitor
    Keymaster

    No problem. Can you run a few tests on a different network?

    July 19, 2018 at 7:50 pm #5963
    Kiwirad
    Participant

    Hi there (all again).

    I’ve tried a few additional things with no luck, even changed the router with no setting other than those needed to get the internet working.
    In all cases 8.8.8.8 and 8.8.4.4 are accessible, all other devices on the home network function perfectly. It’s difficult to take to another site / network as it’s been hard installed but think this is going to be needed.

    Using my Ubiquiti router I captured the following. I’d be interested if anyone can spot anything unusual.
    I’m still getting http:0 0/0 on the :80 web page fro the device.

    I recently upgraded the f/w from a very old version (Thanks Radhoo)…wondering if something related in going from very old>new using early hardware?

    uRADMonitor 11000007
    type:1 hw:107 sw:130 SBM20
    radiation:6CPM
    temperature:8.75C

    inverter:377V 62%
    uptime:14s wdt:13s/240s

    ip:192.168.1.200
    server:45.79.179.145
    interval:60 http:0 0/0

    07:34:15.525411 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:34:15.531724 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:34:15.535116 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46
    07:34:15.535240 ARP, Reply 192.168.1.1 is-at f0:9f:c2:0c:ad:a2, length 28
    07:34:15.549799 IP 192.168.1.105.57345 > 8.8.8.8.53: 6657+ A? data.uradmonitor.com. (38)
    07:34:15.606737 IP 8.8.8.8.53 > 192.168.1.105.57345: 6657 1/0/0 A 45.79.179.145 (54)
    07:34:20.613073 ARP, Request who-has 192.168.1.105 tell 192.168.1.1, length 28
    07:34:20.614145 ARP, Reply 192.168.1.105 is-at 02:00:11:00:00:07, length 46
    07:34:41.423629 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:34:41.429891 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:34:41.433216 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46
    07:34:41.433340 ARP, Reply 192.168.1.1 is-at f0:9f:c2:0c:ad:a2, length 28
    07:34:41.447922 IP 192.168.1.105.57345 > 8.8.8.8.53: 6657+ A? data.uradmonitor.com. (38)
    07:34:41.511103 IP 8.8.8.8.53 > 192.168.1.105.57345: 6657 1/0/0 A 45.79.179.145 (54)
    07:35:08.002901 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:35:08.008976 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:35:08.012160 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46
    07:35:08.012236 ARP, Reply 192.168.1.1 is-at f0:9f:c2:0c:ad:a2, length 28
    07:35:08.026777 IP 192.168.1.105.57345 > 8.8.8.8.53: 6657+ A? data.uradmonitor.com. (38)
    07:35:08.096508 IP 8.8.8.8.53 > 192.168.1.105.57345: 6657 1/0/0 A 45.79.179.145 (54)
    07:35:13.109031 ARP, Request who-has 192.168.1.105 tell 192.168.1.1, length 28
    07:35:13.110114 ARP, Reply 192.168.1.105 is-at 02:00:11:00:00:07, length 46
    07:35:34.357893 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:35:34.363976 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:35:34.367168 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46
    07:35:34.367243 ARP, Reply 192.168.1.1 is-at f0:9f:c2:0c:ad:a2, length 28
    07:35:34.381760 IP 192.168.1.105.57345 > 8.8.8.8.53: 6657+ A? data.uradmonitor.com. (38)
    07:35:34.450794 IP 8.8.8.8.53 > 192.168.1.105.57345: 6657 1/0/0 A 45.79.179.145 (54)
    07:36:00.814122 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:36:00.820202 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:36:00.823408 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46
    07:36:00.823484 ARP, Reply 192.168.1.1 is-at f0:9f:c2:0c:ad:a2, length 28
    07:36:00.837581 IP 192.168.1.105.57345 > 8.8.8.8.53: 6657+ A? data.uradmonitor.com. (38)
    07:36:00.886253 IP 8.8.8.8.53 > 192.168.1.105.57345: 6657 1/0/0 A 45.79.179.145 (54)
    07:36:05.893093 ARP, Request who-has 192.168.1.105 tell 192.168.1.1, length 28
    07:36:05.894489 ARP, Reply 192.168.1.105 is-at 02:00:11:00:00:07, length 46
    07:36:27.368350 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:36:27.374441 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:36:27.377614 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46
    07:36:27.377686 ARP, Reply 192.168.1.1 is-at f0:9f:c2:0c:ad:a2, length 28
    07:36:27.391797 IP 192.168.1.105.57345 > 8.8.8.8.53: 6657+ A? data.uradmonitor.com. (38)
    07:36:27.466714 IP 8.8.8.8.53 > 192.168.1.105.57345: 6657 1/0/0 A 45.79.179.145 (54)
    07:36:53.723983 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:36:53.730076 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
    07:36:53.733259 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46
    07:36:53.733334 ARP, Reply 192.168.1.1 is-at f0:9f:c2:0c:ad:a2, length 28
    07:36:53.747892 IP 192.168.1.105.57345 > 8.8.8.8.53: 6657+ A? data.uradmonitor.com. (38)
    07:36:53.811781 IP 8.8.8.8.53 > 192.168.1.105.57345: 6657 1/0/0 A 45.79.179.145 (54)
    07:36:58.821033 ARP, Request who-has 192.168.1.105 tell 192.168.1.1, length 28
    07:36:58.822151 ARP, Reply 192.168.1.105 is-at 02:00:11:00:00:07, length 46

    July 20, 2018 at 10:05 pm #5965
    Kiwirad
    Participant

    Sorry, the 192.168.1.200 was me trying a different IP in case there was some address conflict. Back to .105 now.
    Oddly it sometimes come up with 200 / 1 / 1 or similar (200 / 3 / 3) then goes back to 0 / 0 / 0 again

    radiation:26CPM
    temperature:9.25C

    inverter:377V 71%
    uptime:25s wdt:24s/240s

    ip:192.168.1.105
    server:45.79.179.145
    interval:60 http:0 0/0

    July 22, 2018 at 6:53 am #5967
    uRADMonitor
    Keymaster

    @Wolferl is right, and his comment made me look at something else. I don’t know how I checked this first, because I had it on my mind: https://www.uradmonitor.com/tools/dashboard-04/?open=11000007

    The duty cycle is too high. The firmware reboots the unit when the duty cycle reaches 80% . So this is why it appeared as having network issues, the reboot happened right after Ethernet initialisation (including DHCP lease), just to take everything all over again.
    This is not the true duty cycle received by the switching transistor because there is a second blocking transistor that quick closes the gate so it is not dangerous for the parts even if the value seems high.

    The model A doesn’t have a voltage multiplier, so the inverter works harder to jump from 5V to 380V needed for the tube. The ferrite core’s permeability is affected by temperature, but I see the weather is chill there. Replacing the inductor would help, but let’s put software first: I can provide a modified firmware that lowers the switching frequency and achieves higher voltage with less effort. It will also remove It approaches the audible spectrum though, as we are already at about 15.5KHz

    Please check your mail.

    Thanks both for your help and patience!

    July 23, 2018 at 5:26 am #5969
    Kiwirad
    Participant

    Thanks all for your help. The new firmware (v1.35) is working well now (or so it seems :o)

    I am getting constant http 200 returns and online on the https://www.uradmonitor.com/ site.
    I’ll keep an eye on this as the temp drops overnight (winter here)

    Glad I wasn’t going mad…

    uRADMonitor 11000007
    type:1 hw:107 sw:135 SBM20
    RAD:28CPM
    VOL:377V 60%
    T:12.00C

    UP:977s WDT:15s/180s

    IP:192.168.1.105
    SERVER:45.79.179.145
    INT:60s http:200 16/16

    July 23, 2018 at 7:30 pm #5973
    Kiwirad
    Participant

    Ohh and now it’s failed again overnight

    Was running very well, but as Radu suspected as the temp dropped the unit has gone offline and rebooting.
    At least it’s working better, but still not 100% right.

    At least I think we know what the issue is (and isn’t)

    uRADMonitor 11000007
    type:1 hw:107 sw:135 SBM20
    RAD:9CPM
    VOL:378V 65%
    T:7.50C

    UP:42s WDT:40s/180s

    IP:192.168.1.105
    SERVER:45.79.179.145
    INT:60s http:0 0/0

    July 24, 2018 at 9:48 pm #5979
    uRADMonitor
    Keymaster

    Please try the new firmware I sent you before anything else.

    July 27, 2018 at 7:23 am #5984
    Kiwirad
    Participant

    Thank you, the new firmware is working well and the unit remains online overnight (when the temp dips).

    Thread closed, happiness is a working geiger counter….

  • Author
    Posts
Log In Register Lost Password
Viewing 13 posts - 16 through 28 (of 28 total)
1 2
  • You must be logged in to reply to this topic.