I admit he comma guess was stupid. Not because I have any Python knowledge, but the Amps are "pointed" also...
Next step is to discharge the battery to 3.4V/Cell and reinstall the driver with an unaltered utils.py.
Thanks for your patience, I'll report next weekend hopefully (with good news)...
Hello, first post...
I'm desperately trying to get the driver running but no success so far.
JBD BMS connected with original JBD UART to USB box. Connects flawlessly to JBD Tools in Windows so I don't think it's a matter of cabling.
Running a PI with Venus v2.87. Version 2.72 no success either...
No step further so far. "object has no attribute 'min_battery_voltage' " still persisting. Is there anything else I can log to provide additional information to you?
- cellvoltages are within LiFePo range
- unaltered utils.py
- DVCC on
I'll try this evening, still at work.
But I haven't touched the utils.py at all after the installation, as you said the voltages make no difference except the BMS will stop charging at 3,45V.
Little hope therfore...
This little Pi drives me crazy. Discharged the Powerwall to 3.0V/cell. Clean install of Venus 2.89. Installed the driver as shown in your new video. (great effort, thanks). But nothing, even the logfiles are looking worse. Seems it shall not be for me...
Hi Louis,
didn't get it done to copy the utils.py to the raspi. My Linux commands knowledge is not nearly sufficient...
Untouched utils.py though.
But I recognized some anomalies during the installation process of the serialbatterymonitor: "Omitting directory". Perhaps is this the reason for the...
Wow, the maestro himself! Thanks alot!
Actually I connected to the Pi with Linux Mint via Putty and then used the nano editor (took me quite some reading and learning the shortcuts).
Screenshot attached.
I spent weekends installing the driver, even complete Venus in different Versions over and...
For the voltages I used a "Point" as decimal seperator. Perhaps it has to be a "comma"?
Ok another idea: I will discharge "The Wall" to 3.4V/cell (within the LiFePo range) and reinstall the driver with original utils.py settings. Keeping my fingers crossed...