My notes say 9600, 38400 & 57600 have all been used at some point, so it’s worth trying each in turn.
You haven’t had the radio module off the RPi and put it back on the wrong pins? It should be right up to the end nearest the corner of the board, and not drooping so that it touches any of the other GPIO pins further along.
Not necessarily. I recall Robert mentioning (fairly recently) doorbells that had some of their stored parameters change bacause of a power hit.
Commercial power failures can, and often do, produce large voltage spikes that can cause some
pretty wild/weird stuff to happen. From altering memory contents to complete destruction of the
device and many things between those extremes.
I’m not saying this is what happened, but 45+ years of ET experience says it can’t be ruled
This isn’t a stored parameter. It is in a text file. A power spike editing a text file to change a specific parameter to a different, but potentially valid parameter, is impossible (and I don’t say that lightly).
I’m not suggesting otherwise. But to offer changing the text file baud rate as a solution is nonsensical. if an update had been done, then yes there is a potential mismatch when older hardware is involved.
Well it’s all now working again but I’m not sure what the exact solution was. I shutdown the emonbase over a remote command line and then retrieved it from near the consumer unit some time later. Took the lid off and made sure the wireless unit was mounted firmly on the gpio pins (which it seemed to be). Took out and reinserted the SD card, took it back to the CU, plugged it in and by the time I got back to my desk the feeds had started up again.
Thanks for all the suggestions.
I’m now going to take an image of the SD card in the next day or two so it it stops working again I can get a new emonbase and perhaps a fresh card to work with and hopefully minimum downtime.
I should probably get a surge protected extension too.
That’s half-good to know. Those faults are the ones I really, really hate.
I’d surmise that either something somewhere got corrupted, and survived all previous attempts to restart, or by pure coincidence a bad contact had made its presence known at the wrong time. Nasty either way.