diebieengineering / diebiems Goto Github PK

The Readme could be improved with a couple of quick typo fixes and removes some trailing white space. Feel free to use the upcoming PR or just close this Issue and PR and wrap the changes into your own work :)

What are the specifications for this board? specially compared to http://electrodacus.com/SBMS100/manual/SBMSmanual.pdf

Hello!

The last days I have seen your BMS.
Fully interested I have looked at the scematic.

Is there anywhere a description of the different parts or can you answer me few questions?

Now one question. For what is R39, its look like shorting the cell.
Should it a solder brigde? It isn't in BOM.
I don't have enough experience in altium for "understanding the whole schematic".

When you say BMS from 6S to 12S.
When I am connection different series of packs need i have to solder R39 on unused cells?
Or is this only software config?

Why is 6S the minimum?
Or isn't it? Only 12V?

I hope you can help me.
Thank you a lot.
Regards
Andy

there are many ebike use 20s 72v battery.

It is resistors very power. Why do we need R6, R7?

Hello,

first of all really nice project! I am currently making a special Version for a custom battery pack.
So thank you very much for sharing!

I have a question:
What is the purpose for connecting the SAFETY signal to GPIO2 of the LTC6803?
I guess its for the reason when something went wrong with communication due to a uC brownout for example?
But why did you use GPIO2 for that? I think the WDTB pin is a better choice for that?
Like the datasheet suggests on page 15:

WATCHDOG TIMER CIRCUIT
The LTC6803 includes a watchdog timer circuit. The watchdog timer is on for all modes except CDC = 0. The watchdog timer times out if no valid command is received for 1 to 2.5 seconds. When the watchdog timer circuit times out, the WDTB open-drain output is asserted low and the configuration register bits are reset to their default (power-up) state. In the power-up state, CDC is 0, the S outputs are off and the IC is in the low power standby mode. The WDTB pin remains low until a valid command is received. The watchdog timer provides a means to turn off cell discharging should communications to the MPU be interrupted. There is no need for the watchdog timer at CDC = 0 since discharging is off. The open-drain WDTB output can be wire ORd with other external open-drain signals. Pulling the WDTB signal low will not initiate a watchdog event, but the CNFGO bit 7 will reflect the state of this signal. Therefore, the WDTB pin can be used to monitor external digital events if desired.

If using GPIO2 and the uC sets this pin to zero, the power stage can be switched on. When the uC gets stucked or something went wrong the pin of the LTC6803 stays at low level, so the power stage will remain enabled!?
This would not happen if SAFETY is connected to the WDTB pin, which uses the LTC6803 internal watchdog?

Or is there any special purposes why you used GPIO2?

Here is my current implementation of the WDTB watchdog feature:

This also has the additional advance that the ISL28022 can also interrupts discharge/charge if an error occurs. (Overcurrent for example).
I think this should be much faster than doing this with the uC.
And once the ISL28022 is successfully configured and the software later stucks the overcurrent protection is still available.

Kind Regards
Danie

Hi again,

i see that BOOT 0 pin is used for selecting which memory the MCU reads from. Connecting that pin to GND forces the MCU to read from the main flash memory while setting it to 3v3 allows the MCU to read from the system memory. Could you please tell me why you did not use the option for system memory (BOOT0=3v3)? In this mode you have a default bootloader for the MCU.

Where is version 0.8 in GIT?
There is 0.7, then 0.9.

Hi. I assembled the device.
HW 0.8
I connected battery. I upload firmware. Device connecting in DieBieMSTool.
I connect pin J14:2 to GND. Terminal DieBieMS says the button is pressed.

-----Battery Pack Status-----
Pack voltage : 24.52V
Pack current : 0.04A
Low current : 0.04A
High current : 0.00A
State of charge : 0.0%
Remaining capacity : 0.00Ah
Operational state : Power down
Load voltage : 0.00V
Cell voltage high : 3.506V
Cell voltage low : 3.503V
Cell voltage average : 3.505V
Cell voltage mismatch : 0.003V
Discharge enabled : False
Charge enabled : False
Power button pressed : True
---End Battery Pack Status---

But BMS not connected LOAD and battery. OpState remains Power down.

How turn on this BMS?

When running on the bench, everything works fine but the moment I step on the board, power is cut off to the vescs and the board dies. Checked all the wiring and updated to v.27. running 16Ah 10s6p Li-ion pack with DBMS

Hi,
I am TOM from China. I am interested in BMS. Are you interested in our cooperation in developing a commercial BMS?

I see in the readme file:

With this fully opensource project I would like to contribute to a more safe and affordable Lithium based electric vehicle (or possible other usage) future.

But under which licence are these materials available? In other words - what can we do the materials? As per https://ohwr.org/licences

Copyright law defaults to 'all rights reserved', and other IP rights are similarly restrictive, so designers need to provide certain freedoms to users explicitly.

Hi Danny,
Big comliments on this. It looks really nice, and I thought I might give it a try to build this myself.

When I looked at the schematic, I had some questions.

• When a charger is plugged in, Chargedetect is pulled low. The voltage difference between charger and battery will turn on the optocoupler D2. First I thought D5 was some Zener Voltage Regulator diode, but then I saw that it isn't a zener. Why is D5 there then?

• Also, in the schematic you have R11 and R64 as shunt resistors (1mOhm), but on the pictures I only see one shunt placed on your boards. R11 is rated for 5W. Isn't that short when using proper discharge loads (electric board)? If R64 is added, does this imply a software setting that has to be changed?
  

Thanks in advance

Hi,

first of all i'd like to congratulate you for this awesome proyect, really really cool.
I have been analyzing the project and i have a doubt about the temperature in different mode: charging and discharging. In charging mode the information says "if desired enable the switch to allow current to flow from CHARGE+ to PACK+". I do not know how much current flows through the pcb for charging but i think is about 2-10 amps if this BMS is used for electrical vehicles. For discharging mode there is an 80 amps fuse between B+ and Batt+ all connected with poligon pours so i guess is designed for high current. Anyway, my question is: with high current what temperature reaches the PCB?

Thank you and best regards

The photo shows a large fuse, but it is not in bom.
What fuser are you using?

I saved motor configuration in DieBieMS tool, but after reconnect battery my config set to default.