I plan on using closed loop communication between server rack batteries capable of closed loop communication - reporting SoC, voltages, all kinds of things to the Cerbo... but I am also planning on using the Lynx system for connection of batteries and fusing all of the distribution DC wires.
If I were to also put in a Lynx Shunt between the Power In and the Distributors, AND I have the closed loop communication, how does Cerbo handle it when two different methods of measuring the same thing disagree? Who "wins" when, say, the Lynx Shunt is saying the SoC is 85%, but the batteries are reporting 95%, and you have AC in conditional disconnection set to 95%?
Obviously, deviation should, hopefully, be insignificant... but, the readings on the closed loop of the batteries will be about as exact as you can get (because the electronics reporting on these items are physically attached to battery cells), whereas the Lynx Shunt will be apart from the batteries by the wires from battery to server rack cabinet bus bar, bus bar to Power In, and then Power In to Shunt... even with dual 4/0 to each rack and solid crimps/lugs with proper torque (which is my plan), there will technically be SOME difference which could cause deviation of portions of a volt.
Should I:
- "Trust" closed loop the best because it's closest to the batteries, and not get the Shunt?
- Not do closed loop and only do the Shunt, so there's no confusion?
- Do both, in which case I would like to better understand how the Cerbo handles possible conflicts between reporting tools?
