I'm polling a BMV-702 through the VE.Direct port using HEX "GET" commands to read device registers.
I recently ran it overnight and found that the SOC dropped much more quickly than it should have. After some poking around, I noticed that when my polling code is active the current value reads much higher than when it isn't.
I can verify this by watching the on-device display change as I activate/deactivate my polling code while keeping the actual load current constant.
I'm requesting four registers every 2 seconds, and there's a delay of 50ms between each of those requests. Also I have a dummy request every 0.5 seconds to keep the TEXT protocol from activating. (Note 1: I'd love a way to disable reversion to the automatic TEXT output entirely, but I haven't found a way documented anywhere. Note 2: Longer delays between reads seem to have less effect, but it's still significant)
I'm very disappointed by this discovery as the comm port was the main reason for selecting this product over competitors. Even if this was expecting too much from the device, which is unlikely, I should NOT be able to affect the main function of it by requesting data through the serial port regardless of how I do it.
If I'm doing something wrong, I'd love to know how to rectify the problem. If I've discovered a bug/defect then everyone should know and something should be done about it.