On Sunday, February 19, 2017 at 4:12:51 PM UTC-5, Günther Zinsberger wrote: > > > Feb 19 07:39:12 rasp3 weewx[19064]: fousb: unstable read: blocks differ > for ptr 0x000000 > Feb 19 07:39:12 rasp3 weewx[19064]: fousb: unrecognised magic number 0000 > Feb 19 07:39:12 rasp3 weewx[19064]: fousb: magic number changed old=55aa > new=0000 > Feb 19 07:39:12 rasp3 weewx[19064]: fousb: get_observations failed: bad > pointer: 0x0000 > Feb 19 07:39:43 rasp3 weewx[19064]: fousb: get_observations failed: bad > pointer: 0x0000 > Feb 19 07:40:20 rasp3 weewx[19064]: fousb: get_observations failed: bad > pointer: 0x0000 > Feb 19 07:40:51 rasp3 weewx[19064]: fousb: get_observations failed: bad > pointer: 0x0000 > > unstable read is not a problem - that happens from time to time.
bad pointer is not ok - that indicates that the firmware is in a bad state. a changed magic number is also an indicator that firmware is not ok. when the firmware gets mixed up like this, the solution is to power cycle the station. you do not have to power cycle the computer or restart weewx. some people power cycle the station this using a usb hub that has power control. some of these hubs are listed here: https://github.com/weewx/weewx/wiki/FineOffset%20USB%20lockup and this thread has more: https://groups.google.com/forum/#!topic/weewx-user/WmVO-VKqF9g m -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
