Closed squowse closed 1 month ago
Please remove the quotes from EXTERNAL_CURRENT_SENSOR_DBUS_DEVICE
and EXTERNAL_CURRENT_SENSOR_DBUS_PATH
. I wrongly inserted them in the example.
Thanks. The current display is closer to the Victron Connect App now. The VRM display still rounds to the nearest .1A though. Eg 1.40A compared to 1.46A on the app. Would this be expected?
The rounding doesn't seem particularly consistent eg down, nearest, up. The delay between readings could be confusing this though.
; --------- Externcal current sensor ---------
; Specify the dbus device and path where the external current sensor is connected to
; You can find it by executing the dbus-spy command
; Example for a external current sensor connected to the VE.Bus port:
; EXTERNAL_CURRENT_SENSOR_DBUS_DEVICE = com.victronenergy.vebus.ttyS3
; EXTERNAL_CURRENT_SENSOR_DBUS_PATH = /Dc/0/Current
EXTERNAL_CURRENT_SENSOR_DBUS_DEVICE = com.victronenergy.battery.ttyS6
;smart shunt 1
EXTERNAL_CURRENT_SENSOR_DBUS_PATH = /Dc/0/Current
Please check with the dbus-spy
or in the Remote Console/GUI.
The smartshunt current in Remote Console is rounded to 0.1A. The app shows to 0.01A
dbus-spy also shows current rounded to 0.1A
The rounding is normal, but how much is it delayed?
VRM? Maybe a second or two. Yes I think you are right - although the VE.Direct interface seems to get higher precision current measurements, the Cerbo only processes them at 0.1A. Thanks for your help with this
But is there also a delay in the dbus-spy or Remote Console/GUI? If yes, how much?
No real delay between the app and dbus-spy or remote console. Half a second or less.
Describe the problem
I have successfully enabled SOC_CALCULATION in the driver config.ini file. This seems to be working and resetting to 100% correctly.
I changed the EXTERNAL_CURRENT_SENSOR_DBUS_DEVICE to the path found by dbus-spy. First time after reboot, VRM came up with the warning "realtime connection disabled due to gx device overload". The VRM interface did not update.
I disabled the external current sensor in the config.ini, rebooted, tested and then re-enabled it exactly the same. Now it appears to be working but the current displayed in VRM does not match the current shown using Victron Connect app simultaneously. The rounding is also wrong and is reminiscent of the BMS current reading.
Please see attachments
Driver version
v1.3.20240510passthrough
Venus OS device type
Cerbo GX
Venus OS version
v3.30
BMS type
JKBMS / Heltec BMS
Cell count
16
Battery count
1
Connection type
Bluetooth
Config file
Relevant log output
Any other information that may be helpful