Ate shit at around 22mph with a self built battery and figured it was my shoddy work, with an xlite, so I’m glad it wasn’t just my work that made me nose dive. Thanks for the heads up!
I was one of the first to nosedive for this reason back in 5.3 version and I am glad I did not miss to uncheck this when updating. But why is such a deadly trap function not off by default? I feel like many will still nosedive because of it.
This explains so much! I have nose dived a few times when my battery gets low. I was wondering why it felt like the board cut off instead of how a low voltage nose dive feels like on a FM board.
I remember asking about the SOC calculation algorithm on Ennoid´s enddles-sphere thread because I could not imagine how the Xlite bms could calculate the battery percentage any differently than based on voltage, due to no current sensor in the HV+ or HV-. If I remember correctly, it is based on the lowest single cell voltage .
Hi, this isn't relevant to this specific video but I was wondering if it would be possible to add more batteries to the front of the board. If you minimized the size of the VESC and wire routing there could be enough space to have quite a few more cells, but that might be very complicated with having to run all the BMS cables for those extra cells through the side of the board. Also I'm not sure you'd have enough to get to a full 18-20s 3p number and I think 84v is pretty close to the limits of most VESC so 2p would likely not work. Have you seen anyone try this or thought about it yourself? I think it could make for a pretty legendary range if it's actually feasible.
Damn thanks for reminding me! I remember you disabled it in your CFW but forgot that all changed when we moved to packages. Would it be possible for the package to override that setting by default??
Do these setting take effect if you only have the CAN wires connected? i.e. no power wires so the ennuid is basically "off" unless it's charging and plugged in?
@@davidpatterson1398 ah sorry, no idea if that is safe or not - but the software functionality is the same. So you would also be subject to SOC based current limiting