I tried restarting the Emonhub on the web, and then, compiling through ./compile.sh but the measurements remain the same as before. So, I would like to know how to calibrate the emonpi not with the scales in the emonhub, but with the source code.
As you mentioned, my problem was that I had to upload the file I was compiling. I achieved this through the command ./upload.sh and everything went well with my calibration (yesterday). However, as I continued working with the modified-emonpi I realized that it no longer identified the values of the emontx that it had associated with it.
But back to my original question, the best option to calibrate is through the emonHub and the scales. Thank you so much
The only reasons I can think of to explain that are either that you had inadvertently removed the part of the code that operates the RFM69CW radio receiver and sends the received values through to emonhub, or you had changed the wrong part of emonhub.conf.
Changing the calibration constants should not have done anything to other parts of your system.
As I told you in a previous post, I also edited the emonpi/firmware/src/src.ino because I was calibrating the devices in a more accurate way, due to the EmonHub didn’t allow me to be so accurate (I modified Ical1, Ical2, Vcal_USA) and it’s was great. However, when I compiled and uploaded the src.ino I realised that my EmonPi was no longer reading the EmonTx. Only when I rebooted it, but the emonpi read the Tx for 20 seconds and then it did not read anymore.
Did you know why it happens? It looks like if the RF was disabled !!
As far as I’m aware, those should work.
Am I right to think that you are seeing the emonPi’s own readings in emonHub/emonCMS, but not the remote emonTx?
Have you accidentally reconfigured the receiver to a different frequency band or group? you might have done this by sending something like “8b” (868 MHz band) or “123g” (Network Group 123) on the serial interface from the Pi. Those should be “4b” and “210g” for 433 MHz / 210, in order to receive from a standard emonTx.
Does the emonHub log tell you anything useful?
But if you have only changed the voltage and current amplitude calibration constants, I don’t see why you did this, because those can be adjusted equally effectively in emonHub (though “power1_plus_power2” must be a compromise). It is only the phasecal constant which cannot be changed there, and that is the one thing you have not adjusted.
If you cannot find out what you have done wrong, the easy solution is to update your emonPi, which should overwrite your changes and get it working again.