Ok. I’ve pulled everything apart and looked at schematics and worked out what’s going on…
Metering across the emonVs R9 I can see 300mV as expected. However, when I connected it to the emonPi2 ti gets pulled down to 136mV… Hmm…
So it seems that recently there’s been a change from RJ11 to RJ45 with the connectors. I have an emonVs with RJ11 and a emonPi2 with RJ45. Even though pyhsically they’re compatible, rather than keep pin compatibility the pins have been re-assigned…
This is what happens when you connect the two :
n/c -> emonPi2 v2.0.1 Pin 1 (VS1)
emonVs 1.1 RJ11 pin 1 (GND) -> emonPi2 v2.0.1 Pin 2 (VS2)
emonVs 1.1 RJ11 pin 2 (5v) -> emonPi2 v2.0.1 Pin 3 (VS3)
emonVs 1.1 RJ11 pin 3 (n/c) -> emonPi2 v2.0.1 Pin 4 (+5v)
emonVs 1.1 RJ11 pin 4 (VS3) -> emonPi2 v2.0.1 Pin 5 (+5v)
emonVs 1.1 RJ11 pin 5 (VS2) -> emonPi2 v2.0.1 Pin 6 (GND - LINK)
emonVs 1.1 RJ11 pin 6 (VS1) -> emonPi2 v2.0.1 Pin 7 (GND)
n/c -> emonPi2 v2.0.1 Pin 8 (GND)
Hence, my VS1 is getting pulled down to ground. This seems like a fundamental oversight and Im kinda surprised that this hasn’t been spotted before! I’m glad nothing went pop…
Unless Im missing something really obvikous, the emonPi2 RJ45 pinnings would be the following to allow backwards compatibility with emonTx :
n/c -> emonPi2 v2.0.1 Pin 1 (GND)
emonVs 1.1 RJ11 pin 1 (GND) -> emonPi2 v2.0.1 Pin 2 (GND)
emonVs 1.1 RJ11 pin 2 (5v) -> emonPi2 v2.0.1 Pin 3 (+5v)
emonVs 1.1 RJ11 pin 3 (n/c) -> emonPi2 v2.0.1 Pin 4 (GND - LINK)
emonVs 1.1 RJ11 pin 4 (VS3) -> emonPi2 v2.0.1 Pin 5 (VS3)
emonVs 1.1 RJ11 pin 5 (VS2) -> emonPi2 v2.0.1 Pin 6 (VS2)
emonVs 1.1 RJ11 pin 6 (VS1) -> emonPi2 v2.0.1 Pin 7 (VS1)
n/c -> emonPi2 v2.0.1 Pin 8 (+5v)
This would give identical functionality and pin compatibility.
Where’s the best place to fire this into the projects workflow, a github issue I guess?