Thanks rdc-Green (and Robert and Brian) for the info on configuring the three phase sketch with direct serial connection to a rpi running emoncms. As a first time user of this equipment (but some experience with other Arduino and RPi projects), the documentation available for this process seems quite scattered across countless pages and forum posts with possibly crucial details missing. There is also a lot of conflicting info relating to ostensibly similar configurations which makes it more confusing than it probably needs to be. Can I suggest a definitive step-by-step guide be included somewhere as a Guide or on the Learn section of the website? Once I get this sorted I’ll be writing it up for my own purposes (memory like a sieve) so happy to contribute…
From lots of reading on the forums, guides and docs etc I formed the interpretation that the EmonHubSerialInterfacer [SerialDirect] was an older/less ideal/supported method than the EmonHubTx3eInterfacer [SerialTx3e] (eg: @glyn.hudson Direct connection emonTx V3 3-phase to RaspberryPi - #11 by glyn.hudson). There’s another explanation of the difference between the two by either @glyn.hudson or @TrystanLea somewhere (that currently I can’t find across the 64,000 OEM browser tabs I currently have open…) which I think suggests that for the current emonTx/firmware we should really go with the [SerialTx3e] option.
rdc-Green - it looks like you’ve just kept the [SerialTx3e] title for the interfacer but changed it to match the [SerialDirect] way of doing it…?
I too cannot get EmonCMS to receive any Input from the [SerialTx3e] interfacer over /dev/ttyAMA0, but it is received just fine in the EmonHub log. I’d like to make sure I set this up in the most optimal way - is there any downside to reverting to the [SerialDirect] interfacer instead of sticking with [SerialTx3e]?
My setup is functionally identical to the one described by rdc-Green.
(As a new user I’m only allowed to 'mention two users in a message - hope all the relevant people see this anyway…)
Many thanks!