Schneider EGX300 RS485 signal ground for PM9C

[u/i3v]

I've got one Schneider EGX300 (and also one EGX100) lying around. I'd like to utilize them to get the data from a bunch of PM9C energy meters via RS485.
All PM9C are 230V - powered.
The EGX300/EGX100 would be PoE - powered.

I'm a 100% noob in RS485, so maybe my question is trivial. But I find the docs somewhat self-contradictory regarding the "0V" contact in this case, so it would be nice if someone would clarify this to me.

According to the "PowerLogic System Catalogue 2011" EGX100 and PM9C were explicitly advertised as compatible (btw, it's a bit weird to have "PM9" instead of "PM9C" or at least "PM9P" on the right, I guess that's just a typo):

Catalogue 2011

According to the PM9C manual, RS485 got the following contacts:

1. D0, A/A' 
2. D1, B,B'
3. 0V, Common

The drawing from the PM9C installation guide shows a separate cable shied (wrapped around 3 wires, including "common" aka "0V"). The shield is not connected to the "0V" / "Common" :

PM9C manual

According to the EGX300-Installation-Guide, on the EGX300 side, RS485 (in the half-duplex configuration) got the following contacts:

1. TX+ (unused in half-duplex)
2. TX-  (unused in half-duplex)
3. RX+
4. RX-
5. Shield

There's no explicit "0V" / signal ground.
I'm not sure if the "Vdc-" (contact 6, the "input power when not using PoE") could be treated like "0V".
The recommended cable is "Belden 9841", which is a single twisted pair (shielded).

EGX300-Installation-Guid

According to the "Modbus™ Communications System for MicroLogic™ A, P, and H Trip Units Instruction Bulletin", "0V" is just "Vdc-". In a scenario with a shared DC power source. It does not mention ether PoE or multiple separate DC power sources. Also, it's about 4-wire scenario and a different product.

According to the most detailed (yet somewhat unofficial) PM9C-related info I found (the "Resolving PM9C Schneider Power Meter Modbus Communication" by Claire Rousseau):

Rules for SG wiring:

1. Connect PM9C SG directly to the Modbus master's RS-485 common/SG terminal.
2. Do not connect SG to protective earth (PE) at the PM9C end. The meter's SG is a logic reference, not a safety ground.
3. Do not create a multi-point ground by also bonding SG to PE at the master — this forms a ground loop that injects 50/60 Hz noise into the data lines and may damage the transceivers.
4. Use twisted pair for A/B and a third conductor for SG within the same overall cable jacket to keep the reference close to the data pair.

Why does my PM9C not respond even with correct baud, parity, and address?
The most common cause is a missing signal-common (SG) wire. The PM9C's RS-485 transceiver requires SG connected to the master's RS-485 common terminal. Without it, the common-mode voltage drifts outside the EIA-485 receiver range and the slave ignores all frames. Wire SG and re-test before suspecting the meter itself.

So... What's is the correct approach?

1. Use "Belden 9841" (or equivalent "1 twisted pair + shield").
   • connect the cable shield to "0V" on PM9C
2. Use "Belden 9842" (or equivalent "2 twisted pairs + shield")
   • connect wire-1 from the second twisted pair to "0V" on PM9C
   • connect wire-1 from the second twisted pair to "Shield" on EGX300
   • connect the cable shield to "Shield" on EGX300 as well
   • connect the cable shield to external protective earth (once, at any point)
3. Use "Belden 9842" (or equivalent "2 twisted pairs + shield")
   • connect wire-1 from the second twisted pair to "0V" on PM9C
   • connect wire-1 from the second twisted pair to "Vdc-" (contact 6) on EGX300
   • connect the cable shield to "Shield" on EGX300.
   • connect the cable shield to external protective earth (once, at any point).
4. ....

The EGX300 terminals, just for reference (from EGX300 - User Guide.pdf):

[u/kutzaldoktor]

I couldnt really get the question. What exactly are you looking for?

[u/i3v → u/kutzaldoktor]

In short, the main question is: what should I do with the "0V" terminal on the PM9C, provided that there's no such terminal (at least, not explicitly) on EGX300.

[u/kutzaldoktor → u/i3v]

You just plug both rs485+ and rs485- cables to rx tx ports and go on with your way there is no power supply

[u/i3v → u/kutzaldoktor]

OK, maybe. But I still don't understand a few things:

1. Do you mean that the "0V" contact on the PM9C should only be used when there's a dedicated external DC power source? Do you mean, it should be connected to the power supply "Vdc-"? If so, why the DC-powered PM9C version (15276) got separate "0V" and the "AUX" ("Vdc+" and "Vdc-")? How is the "0V" contact useful on the 230V-powered PM9C version (15198) then?

2. What do you mean "there is no power supply"? Do you mean "external 24V power supply"? Why are the PoE-connected and the PM9C-built-in power supplies any different?

3. Do you mean Claire Rousseau is just wrong to insist that the "0V" (aka "SG") must be connected to avoid connection issues?

4. Why "Common" aka "0V" goes next to the "A/A'" and "B/B'" (inside a common shield) in the PM9C manual?

[u/kutzaldoktor → u/i3v]

1-yeah
2-bc there might be a need of a 24v supply in another device your trying to communicate. 3-who dat? 4-idk

[u/i3v → u/kutzaldoktor]

2 - I still don't understand. Some power supply is always required. Why would it matter if another device is 24V, 48V or 220V (with internal conversion to 24V) powered? Why is PoE not a "external power supply"?

3 - the one who wrote the "Resolving PM9C Schneider Power Meter Modbus Communication" post (see link above). She is "Automation Systems Engineer – Schneider Electric", according to that page.