tinfever
commented
1 year ago That's awesome! I'm glad to hear you've had so much success!
On your notes:
- That's a very interesting finding. I broke a few of the ISL94208 chips as well during development but usually didn't know why. It was almost always a short circuit to GND on the 3V3 regulator control pins of the IC. Leaving VDD disconnected entirely, not waking up the pack, and just using VPP is interesting. I've never tried that but I'm kind of surprised it worked since why else would Microchip recommend connecting VDD for programming?
I think I may have mentioned at some point, somewhere, that I don't recommend having the PicKit supply VDD and I was suggesting people wake up the battery pack instead for VDD. Leaving VDD disconnected makes perfect sense in either case, as long as the programmer doesn't complain about being unable to detect it. I'm going to add a note in the instructions about that. Then I'll pin a comment on the YouTube video and update the EEVBlog forum post to refer anyone to the GitHub page for the latest information.
I wonder if VPP is forward biasing the internal ESD protection diodes to VCC inside the PIC and that is how it is getting powered? Then again, PICs can use high voltage programming so that would be dumb.
-
That's a good point. Without digging in to it again, PACK_CHARGE_NOT_COMPLETE_THRESH_mV could probably always be set to like 100mV below MAX_CHARGE_CELL_VOLTAGE_mV automatically. Or just add a note like you said haha
-
Good catch. I haven't run in to that personally but someone else saw similar symptoms using a third party programmer and eventually determined it was the config bits like you saw. Although for them it was a software setting error vs an application bug.
NeilMarley
KerOzenn44
torsoreaper
Hi, first of all many thanks to you & other contributors to this project - it has proved invaluable for my own project of salvaging a number of these battery packs to repurpose (primarily as e-bike power packs). For fun - see my current batch below:
3 x 61462 1 x 228499 2 x 188002 1 x 180207.
All reprogrammed with the new firmware & working perfectly.
A few notes from my experiences which may help others:
I did initially manage to brick a few BMS boards (the ISL94208 chip) while re-programming the firmware with PicKit3. It's clear that the BMS circuitry isn't designed for an external application of VDD, particularly while in sleep mode. I've since found that the most safe and reliable method is to not connect VDD from the PicKit at all, and also to not wake-up the battery pack. The programming works fine & reliably with only VPP from the PicKit.
I altered the MAX_CHARGE_CELL_VOLTAGE_mV setting to 4100 in the interests of extending cell life but initially this caused a cycling error by interacting with PACK_CHARGE_NOT_COMPLETE_THRESH_mV which was also set at 4100. It might be worth a side-note that the latter should be lower than the former with a bit of margin for charging voltage rises?
On occasion a reprogrammed board would work fine functionally but the LED blinking patterns were really slow. It could usually be fixed by reprogramming again. I have noticed that the slow condition has the PIC Config bits set at 3FFF 3703 while the working version is 3FFC 3703. I think this is a PicKit application bug which sometimes sets the operating frequency config of the PIC back to default even when re-loading the same HEX file.