48v LL Battery cluster overloading charge amps modbus register

I can't find a way to edit the original post while it is in a pending state, but one solution that EG4 could employ without increasing the register size, would be in change the unit of measure from 10mA to 100mA.  This would then allow for a reading of up to 3,276.7amps.  Im not sure if that would break any kind of unit standard being used by the closed loop communications.  I do know that the Insight Facility unit only displays amps to 1 decimal point, so having a 2 decimal point granularity is overkill/ignored by this particular platform.

J

Here is a graph from yesterday showing how this effects the tracking of data.  That sudden big drop in the amps is when the register overflowed and wrapped around to a negative number.  When that happens the system begins counting those amps as discharge / load, so the longer it goes on the more inaccurate the data for that day will be.

Since it's been 2 weeks with no response from EG4... I figured I'd give a bit more info to show that this is NOT a problem with the Insight Facility device.

The register I am reading from the facility devise its self is #515 which is a 32bit signed integer, so the storage space is more than enough for the numbers we are talking about.  The only logical conclusion I can come up with is the BMS of the LL batteries is reporting the wrong amps when using modbus with such a high total amp draw or charge, especially given that such a small storage space was given to that register.

Insight Facility document showing the info for the register I am pulling and what is being used by the facility unit its self for graphing.

Registers 519, 521, 523, and 525 all use the info from 515.  So if the amps provided by the LL's BMS is wrong, then 4 other register values are directly effected, on top of the tracking/stats registers as they are going to be summing the battery charge and invert power over time.

To further add, when looking at the BMS data reported to the facility device through the web interface, the BMS is reporting that it could handle 3600 discharge amps or 1800 charge amps, which is accurate for the number of batteries installed in this cluster, however the BMS is not able to report a real time amperage number even remotely close to those maximums.

J

Hey @ anyone with EG4... I need to dig this back up because the problem is STILL on going with no one even trying to troubleshoot or gather info....

Now that temps are getting warmer and we are getting more sun this issue is popping back up and more observations are being made... It appears that when the BMS overloads the amps register that something else is getting stuck in the BMS.  Example is today the register overloaded, the BMS then started to report a discharge when it was actually charging, but it continued to report a crazy high discharge after the amps dropped below the register overload threshold.

Output from the BMS into Connext Insight:  The BMS is reporting a crazy high discharge when it is actually charging, but is ALSO well below the max value for the amps register.  We are getting lots of moving cloud cover today which means lots of cloud edge lensing going on.  The total output of the equipment I have connected could possibly reach 375 charge amps but in reality even with the cloud lensing we should only be reaching around 335-340'ish charge amps.

Charge values are jumping all over the place, but there is enough DC input into the bus bars to keep charging the batteries and not actually need to draw from the batteries for loads.

Basically what it looks like is when the register overloads the amps change from pos to neg, but then are remaining neg values even after dropping well below the register limit.  The register then needs to overload again to allow the value to report as pos again or the charge amps needs to drop way way down before the BMS starts reporting the correct amps again.

This is what it is doing to the graphs...

And of course any energy use tracking gets thrown out the window when this happens.

Can someone at least acknowledge that this is being looked into, or something, anything.  I've been tracking and reporting this issue for over 6 months with complete radio silence from EG4 support and Signature Solar support.

Attached is the CSV output from the graph above, you can see some very rapid very high amp charge to discharge then eventually back to charging numbers.