FW 3.2 (11146) - Appeared to have died **solved**

[Mattk]

May be coincidence with the recent run of screen/updates/bug fixes but following update to 3.2 (11146) April 29 system has completely failed, no screen, no lights, not a thing, have just changed power supply, no change.

[Mattk]

Appears now to be some sort of display failure (or display has been locked out for some reason?) smack bang in between updating 3.2 from 11144 to 11146 but there was certainly something also funny on rebooting as there were no lights for a good 8-10 minutes which gave an impression of a failed box / no power etc. Boot delay had been set to 4 minutes but taking way way longer then this to see the first LED light up. Now occasionally seeing Rebooting .... during a reboot but rather irregular, otherwise display is always blank (Display control: a Always on), no initial display, no 3 sec display every 60 seconds, nothing.

Have checked/re-connected the top/bottom boards etc and nothing else was visually broke.

[Mattk]

logger (30.04.2017 13:05:30): services paused.
test5m (30.04.2017 03:05:30): oled daemon stalled, will be restarted now.
test5m (30.04.2017 03:05:47): oled daemon stalled, will be restarted now.
database (30.04.2017 13:06:15): database sync done (53 tables, 186/1730 writes)
logger (30.04.2017 13:07:27): give up waiting for sensors after 120 secs.
logger (30.04.2017 13:07:27): services activated.
test5m (30.04.2017 03:10:23): oled daemon stalled, will be restarted now.
test5m (30.04.2017 03:16:22): oled daemon stalled, will be restarted now.
test5m (30.04.2017 03:20:48): oled daemon stalled, will be restarted now.
test5m (30.04.2017 03:25:22): oled daemon stalled, will be restarted now.

Don't normally see much reference to the oled as above?

[MeteoLeudal]

Hi,

I have the same problem. No display today!!!

database (30.04.2017 13:27:57): process started.
wnetd (30.04.2017 13:27:59): process started.
system (30.04.2017 11:27:59): start of logging process initiated.
logger (30.04.2017 13:27:59): databases connected. Update interval 3600 seconds.
logger (30.04.2017 13:28:00): historical data loaded (0 records).
logger (30.04.2017 13:28:00): data logger (version 5.0v, build 11146) started.
logger (30.04.2017 13:28:02): connect station 0 (Vantage via USB serial).
logger (30.04.2017 13:28:02): connect station 9 (System Data via Plug-in).
logger (30.04.2017 13:28:02): wakeup sent.
logger (30.04.2017 13:28:02): internal logger activated.
logger (30.04.2017 13:28:02): syncing.
test5m (30.04.2017 11:28:04): oled daemon stalled, will be restarted now.
logger (30.04.2017 13:28:05): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (30.04.2017 13:28:05): services paused.
logger (30.04.2017 13:28:12): gettime request sent.
logger (30.04.2017 13:28:12): no Vantage time offset.
logger (30.04.2017 13:28:12): eeprom request sent.
logger (30.04.2017 13:28:12): rain collector size 0.2 mm per tick.
logger (30.04.2017 13:28:12): transmitter 1 active as station type (#0) "ISS".
logger (30.04.2017 13:28:12): transmitter 2 active as station type (#4) "Wind".
logger (30.04.2017 13:28:12): firmware version request sent.
logger (30.04.2017 13:28:12): firmware version 1.90
logger (30.04.2017 13:28:12): no reading of Vantage's internal logger.
logger (30.04.2017 13:28:17): sensors are now providing data.
logger (30.04.2017 13:28:17): services started.
database (30.04.2017 13:28:23): database sync done (41 tables, 143/1682 writes)
test5m (30.04.2017 11:30:46): oled daemon stalled, will be restarted now.
test5m (30.04.2017 11:35:58): oled daemon stalled, will be restarted now.
test5m (30.04.2017 11:40:29): oled daemon stalled, will be restarted now.

Greetings,
Peter.

[Mattk]

April 30 fix appears to be back to as expected.

[admin]

Sorry that I needed some iterations to get it right. It was more tricky than expected in the first place