Random Station Disconnect (Nano SD)

[staze]

Just had my Nano SD, which is in an Envoy, report "Station Disconnect 0 (Vantage)".

Never had this happen before. Thankfully Weathercat told me about it (saying station data hadn't changed in 12 minutes).

Any idea why this would have happened? Anything I should investigate?

I lost it, but I think I was on Sept 4 or 8th firmware.

Thanks!

[BigAlT]

Sounds like your Vantage Vue ISS is not communicating with your envoy. You might trying to remove both the power supply and batteries from your envoy and then reinstall both so you will get a cold start reboot.
If that doesn’t fix the problem, try replacing the battery in your Vantage ISS ( CR123A ).
Unfortunately, the Nano SD firmware doesn’t appear to report the battery condition of the ISS which is displayed on the Vantage Vue and Vantage Pro 2 consoles as a low batt warning.

[staze]

Soft reboot of Nano SD fixed it. So I wouldn't think it's the envoy or the VSS. Seems more like the Nano just dropped the connection for some reason.

Is there anything I can look at if it happens again to help figure out WHY?

[Mattk]

Network?

[staze]

Network... what?

The nano says it disconnected from the Envoy (seemingly). I did adjust my network a bit before the time it happened, which would have caused a wireless outage, but I'd never seen that before. =/

[staze]

So this just occurred this morning. I did reboot my router at this time. So maybe meteobridge losing network connectivity (wifi stayed up) is somehow freaking it out in other ways? I didn't do anything to fix it, it resolved itself. It's just odd that losing network would cause it to lose connectivity with the station... or does it just go into a "something is wrong, let's reset" mode? Uptime shows it's been up 12 days.

logger (01.10.2019 07:33:08): child process received timeout signal (14).
logger (01.10.2019 07:33:08): disconnect station 0 (Vantage): exit
logger (01.10.2019 07:33:08): disconnect station 9 (System Data): exit
logger (01.10.2019 07:33:09): data logger stopped.
logger (01.10.2019 07:33:09): databases disconnected.
logger (01.10.2019 07:33:10): databases connected. Update interval 3600 seconds.
logger (01.10.2019 07:33:10): data logger (version 5.1b, build 2430) started.
logger (01.10.2019 07:33:10): connect station 0 (Vantage via USB serial).
logger (01.10.2019 07:33:10): connect station 9 (System Data via Plug-in).
logger (01.10.2019 07:33:10): wakeup sent.
logger (01.10.2019 07:33:12): no need to update console date/time.
logger (01.10.2019 07:33:12): setup script executed.
logger (01.10.2019 07:33:13): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (01.10.2019 07:33:13): services paused.
logger (01.10.2019 07:33:13): internal logger activated.
logger (01.10.2019 07:33:13): syncing.
logger (01.10.2019 07:33:23): gettime request sent.
logger (01.10.2019 07:33:23): no Vantage time offset.
logger (01.10.2019 07:33:23): eeprom request sent.
logger (01.10.2019 07:33:23): rain collector size 0.01 inch per tick.
logger (01.10.2019 07:33:23): transmitter 1 active as station type #0 "ISS" (via repeater A).
logger (01.10.2019 07:33:23): firmware version request sent.
logger (01.10.2019 07:33:23): firmware version 3.15 (supports LOOP2)
logger (01.10.2019 07:33:23): no reading of Vantage's internal logger.
logger (01.10.2019 07:33:25): 10.0.2.16's request on port 22222 accepted.
logger (01.10.2019 07:33:32): sensors are now providing data.
logger (01.10.2019 07:33:32): services started.

[admin]

Data logging process restarts itself, when no data coming in from station for a couple of minutes. As the NANO is directly plugged in to the console connection should be fine. Sometimes the data port of the console hangs-up, but this only happens when installing the plugin during ongoing operation of the console and if so the connection stays dump all the time until console is power-cycled. Here it looks like operation starts again.

As you are running the NANO as a slave logger, it does not poll data from the console by itself. This needs to be done from your PC program which acts as master. If that stops requesting data for a few minutes, Meteobridge will run into the logger restart mode. I really dislike NANO being the slave, it can infuse tons of problems. Do you really need that mode? What PC-program are you running that you cannot afford to miss?

[staze]

I’m running WeatherCat on my Mac. At this point, mainly for the iOS app.

I’m confused by the answer though. Are you saying that weathercat is controlling when the Nano queries the console when the Nano is in slave mode, and then when I restart WiFi, weathercat loses connection to the nano (expected) but then the nano stops updating?

I seem to recall when slave mode was created. Was there a need there rather than just letting PC programs poll? Is there a way to tell the nano not to be in slave mode and just respond to Weathercat over 22222?

Thanks!

[admin]

That is not possible as just one can send commands to the Vantage. The PC or the NANO. When both do, answers will be in disorder and a total mess. As your PC program cannot listen only (not build for slave operation) the NANO has to do when both are operating the console.

[staze]

Not understanding.

Weathercat worked before the initial slave implementation.(that is, it still works now, but it also worked before the slave implementation).

Anyway, so the issue is that Wifi going down is breaking weathercat talking to the Nano, and that's stalling out the data polling, so the Nano resets that process?

Thanks!

[admin]

Sorry, I can't explain better.

[staze]

's okay.

Long and short of it, stop using Weathercat, or just accept that the Nano will restart it's logging process when wireless goes down and Weathercat loses connectivity to the Nano?