Many years ago I purchased a Pi + EmonTX solution from here and used it successfully for may years.
I know have re-found the parts and have setup the EmonTXv3 which all looks to be working fine and have put a new copy of the EMONCMS software onto an SD card and fired up a Raspberry Pi 3 model B with the RFM12B expansion.
The CMS boots fine and I have created an account BUT in the Setup > Inputs screen nothing shows despite my patience… I seem to remember something about there being baud rates to set somewhere but no idea how to achieve this or where to look!
I have a feeling that another baud rate was used for a short time - but I can’t remember what it was. I’d suggest trying different values from 9600 up. 57600 has been mentioned.
Did you buy the RFM card and the EmonTX at the same time? Are the frequencies of the 2 items the same (I accidentally was sent 2 different ones when I bought mine many moons ago). Worth checking.
This is where it gets confusing. The emonPi and the emonBase are more or less the same. If an “emonBase” update is done on an emonPi, the update to the RFM12B/69CW should fail because it’s the wrong baud rate. The converse is also true. So yes, I suspect that might have happened. But I don’t know what symptoms that might produce to give an indication that it has happened.
I’m not a RPi or emonCMS expert, so I’m not the right person to ask.
I think from the picture that RFM12B is a 433 MHz version, so the frequency of the RFM12Pi is correct.
AFAIR all rfm12b’s were originally 9600, only when we moved to rfm69cw did the baud get changed to 57600 and then to 38400. And since then the later rfm12b firmware has now been changed to 38400 too since it is the same fw as the rfm69cw but with “compat” set.
I’m less sure of the current status as there are a lot of changes to the update procedure in the last month or so and there is no build guide for the current image, but prior to Oct 2018, I believe the firstboot script that auto runs when an image is first installed will assume it’s an emonpi and try to update the emonpi FW, failing to do so on a emonBase regardless of rfm 12or69.
So it is only IF the “update emonbase” button has been used that it will have updated the FW and over written the rfm12 FW with rfm69 FW (same FW but compiled with the compat setting). I strongly suspect that is the case. IIRC when the wrong FW is installed, the LED might stay on since the rfm cannot be initialised. It looks like the led is on in the picture, that could just be a fluke capture, but that combined with the error and no data, plus the updates, it’s a very strong possibility.
If that is the case you will need to ssh in and run a manual command to reflash the rfm12 FW. unless you might be able to switch branches in emoncms (to master) and maybe @TrystanLea’s new multi-button setup might allow reflashing an rfm12pi via the GUI? I’m not sure how far that’s progressed, or if it’s any easier to switch branches over manually flashing (assuming avrdude etc is still there on the oct 2018 image?)
@alunr - can you confirm if you updated via the “update emonbase” button and/or if the rfm12pi’s LED is permanently lit?
And before any corrections start, YES an RFM12Pi can be either rfm12 or rfm69! The RFM69Pi’s (PCB with additional IO broken out) are all rfm69cw, but the RFM12Pi’s (no additional IO) are either rfm12b (9600 or 38400) or rfm69cw (57600 or 38400). The add-on board model does not directly map to rfm device or baud other than all RFM69Pi’s are rfm69cw and 38400 baud, but that doesn’t help us here RFM12Pi’s can be almost anything!!!
I “think” this was the culprit but even after running this flash it was all still not working so I gave it one last chance and rebuilt the server from scratch again and BOOM! it all works!!
