tobintin
New Member
- Joined
- Feb 22, 2021
- Messages
- 4
@Hubba your battery driver is being started on ttyUSB1 and you are reading the log file under ttyUSB0. That is why it cannot find the log file. Just ready the matching path and see what it says.But nothing, even the logfiles are looking worse
The driver is installed and is being started. Just check the log file for ttyUSB1 to see what is happening (see troubleshooting section on the wiki how to do that)Please help
Thx, I'm going to order some to hardwire the bms's. I did succeed in getting them read out by jkbms (from the mpp-solar dev) via bluetooth and having it post to mqtt for ingest. It works great
I think you will need an USB cable for that too :Thx, I'm going to order some to hardwire the bms's. I did succeed in getting them read out by jkbms (from the mpp-solar dev) via bluetooth and having it post to mqtt for ingest. It works great
Looks like it might nog be reading your cell data and cell count. Or it is the min cell voltage and max cell voltage that it cannot read. I'll add some more log messages in the next beta that should help trouble shooting.object has no attribute 'min_battery_voltage'
You charge and discharge current is changing dynamicly depending on your SOC. If the battery is full charge current is reduced. If the batter is close to empty discharge current is limited. You can disable CCCM by setting CCCM_ENABLE = False in utils.pyHow can i setDCL is always 60A?
RS485 works with a 2 wire bus which is marked A / B or H / L. If your converter is marked R / T that would be receive / transmit and it would be for RS232 or TTL. It will not work. The CH340 with 3.3V and 5V options is normally TTY.Any idea if this can work and to which pins A and B need to be connected?
will watch on git
INFO:SerialBattery:Testing LltJbd
INFO:SerialBattery:Connection established to LltJbd
INFO:SerialBattery:DeviceInstance = 1
INFO:SerialBattery:com.victronenergy.battery.ttyUSB1
INFO:SerialBattery:Battery connected to dbus from /dev/ttyUSB1
INFO:SerialBattery:=== Settings ===
INFO:SerialBattery:> Connection voltage 49.29V | current 0.0A | SOC 50%
INFO:SerialBattery:> Cell count 15 | cells populated 15
INFO:SerialBattery:> CCL Charge 50.0A | DCL Discharge 60.0A
INFO:SerialBattery:> MIN_CELL_VOLTAGE 2.9V | MAX_CELL_VOLTAGE 3.45V
I see your system fails before it gets to the settings log.New screenshot v.0.12b2
tar -zxf utils.zip-C /data/etc/dbus-serialbattery
Just reboot and then check the GUI if it picks up else check the log files. It seems that those folders did copy in one of your tries.A complete noob here. Never in my life have I worked with code nor used SSH but trying my best to get this awesome feature installed. I have a JK BMS and Cerbo GX running firmware v.2.89. Using Putty for the first time, I followed the steps in the install github page as well as the Youtube video. Logged into Putty using host name root@venus.local, then entered the password. I then copied and pasted this into the command field (wget https://raw.githubusercontent.com/L...ster/etc/dbus-serialbattery/installrelease.sh). Everything up to this point was going well according to the video. Next, I entered this (sh installrelease.sh) and then it got stuck. Messages say "cant create directory," "no such file or directory," "omitting directory." One thing I later read about is creating SSH keys which I didnt do, but I didnt see that in the install video. Not sure what else I could do differently. Any help would be greatly appreciated.
Another thing I also dont quite understand is how to edit the battery parameters and get those uploaded into the Cerbo using SSH since my understanding is that everything gets downloaded and installed from the internet via the link in the wget command. I did download the folder venus-data.tar.gz and edited the utils file. Now how to get that edited file onto the Cerbo?
The Daly is not suppose to go to sleep while the driver is querying it. Is there perhaps a setting that you can change for this in the BMS?the Daly falling a sleep
The BMS that people have the least querries/issues are the JBD or JKBMS (JKBMS is also a good option but it seems that the SOC calc for the JBD is a little bit smarter/better. The JKBMS app is easier and less complex).What is in your opinion the best BMS which works with your solution
The problem is that a BMS will adjust it's SOC when some issues inside the battery occur. For instance if one of your cells go over the cell protection voltage the BMS will show 100% SOC (correctly) while any external shunt (like SmartShunt) will think the SOC is perhaps 85% and push in more charge current. So it is not the best option.use the Soc of the SmartShunt