Update 2015 system emonTx v3.4, emonGLCD v1.4 to add emonPi
I would like to update my system and add an emonPi.
While there is a great deal of usefull information and guides, when it comes to Arduino Verify/Compile I get many lines of errors. I feel sure this will be due to the libraries being wrong.
I uninstalled my old version of Arduino, and starting at the Learn section, Installed Arduino and Libraries for Ubuntu 64 bit. I am using Linux Mint 19.3. Renamed the folders as per the guide screenshot.
emonGLCD v1.4 with SolarPV sketch the links https://github.com/jcw/rtclib and https://github.com/jcw/glcdlib both fail.
Updating âemonTx v3.4 with emonTxV3_4_continuous_kwhtotalsâ to the EmonTxV3CM [v1.7 library v2.03] produces approx 20 lines of errors,
config.ino: In function âvoid wipe_eeprom()â:
config.ino: In function âvoid readConfigInput()â:
some in emonLibCM.cpp and more in rfm.ino
But after these errors it produces a downloadable file, so can these errors be ignored?
Most of my problems are solved by a google search of your site, but on this occasion I would appreciate a list or pointer to the correct versions of the required libraries.
âemonTxV3_4_continuous_kwhtotalsâ and âEmonTxV3CMâ are two completely different sketches, the only commonality is theyâre for the emonTx V3.4. Are you saying youâve tried to merge them? If so, Iâd strongly advise reading the emonLibCM documentation and looking at the examples that come with emonLibCM as a starting point and then incorporate the necessary parts of the emonLibCM API into your old sketch.
(And note, V1.7 of the EmonTxV3CM sketch is faulty, I understand an update to V1.8 was published late yesterday. I havenât yet checked it myself.)
What sort of errors - my crystal ball is too hot to handle today, so I canât use it. So I canât tell what the problem might be.
Just as a note in case you find a problem when you update your emonTx,
Iâve found that the GLCD I bought was running the standard HomeEnergyMonitor sketch and did not support the RF whitening which was configured on my emonTx v1.4 CM.
If youâre looking to upgrade to start using the CM code you may find the same - I recommend using it though in terms of monitoring it captures fine for me.
I think if you do see this crop up, you can fix it by configuring by the rf_whitening (setting âwâ) setting which was set to â2â to a different number. If you read the docs its a 1 I think but I decided to keep it set to 2 as a form of grey coding transmitted data is not a bad idea.
So instead I added the RF whitening code to the emonGLCD which is fairly trivial and I can find it out from what I had if you do come across it.
It may not affect you though but just in case I thought it might be something you come across once updated (and if not ignore it )
Thanks
I was not trying to merge âemonTxV3_4_continuous_kwhtotalsâ with âEmonTxV3CMâ.
I was loading EmonTxV3CM v1.7 library v2.03, to see if it Verified/Compiled without errors, before making any changes for my setup.
The fact that it produced so many errors, but still compiled, made me think/hope, they did not matter.
I appreciate this is a community run forum, so would not expect a line by line solution for so many.
I didnât know if errors that allowed the compilation to produce a downloadable file could be ignored.
There must be something wrong with my setup as it is. I will install afresh. Thanks.
I donât think I believe you. If they were âerrorsâ, it wouldnât produce an executable version, so I think they might have been warnings, which you can probably ignore. But if you post the first couple, Iâll look. (Iâm not interested in any more - they probably are generated by the first few.)
Thankyou @Tim5000, this is worth knowing about.
For some time I had been running two emonBases , separete ip address and node No., backing up one from the other as microSD cards failed/corrupted. This served me well until recently, when I lost everthing local. When I saw an emoPi shield was now available I thought it would be a good upgrade.
Iâm not sure what Timâs on about: âwhiteningâ (it isnât true whitening) is there to prevent the radio modules losing sync on long streams of zeros. All thatâs done is each byte is xor'ed with 0x55 at each end. Itâs not intended as a form of coding, much less encryption.
In the emonTxV3CM sketch, whitening has 3 values: 0 = no rf at all, only serial output, 1 = rf on, no whitening, 2 = rf on, whitened. In the emonPi/emonBase, itâs 0 = unchanged (no whitening expected), 1 = de-whitened.
You are correct @Robert.Wall, they are warnings, my mistake. Because it produced a download file the âCopy to clipboardâ is not available. Screenshot of first 3, to show its in other areas, â/home/???â removed from beginning of each line.
Thanks for your interest.
I will have to try Ubuntu, Iâm on Mint 19.3, Arduino 1.8.13 . Retried, sketch window works as expected, reporting window will allow text to be highlighted, cannot copy or cut.
Thereâs no right-click etc, but ctrl-C works just fine:
Sketch uses 27594 bytes (85%) of program storage space. Maximum is 32256 bytes.
Global variables use 1248 bytes (60%) of dynamic memory, leaving 800 bytes for local variables. Maximum is 2048 bytes.
And the compiler warnings are all OK. Theyâll get corrected eventually.
Iâve found that only protected .pdf files canât have the text copied by highlighting and ctrl-C. But they are not immune to a screenshot. A terminal window needs ctrl-shift-C.
It does actually use a âclipboardâ (or buffer), just you donât do anything to load it into the buffer except highlight it - just like PuTTY on my Win PC. on PuTTY a right click pastes the buffer. On Windows 10, the Powershell window works differently.
How it happens is dependent on the application rather than the OS.
That was in inverted commas to point out that I didnât click on/execute a command labelled "Copy to clipboardâ, because in that situation, there isnât one; but not just that - I almost always still use ctrl-c & ctrl-v for copy and paste operations. Old habits die hard. Of course itâs using the Linux equivalent of a clipboard, it isnât labelled as such. So your point is pedantic.
)