Probably somewhere between 150 & 200$ for few units order.
@jesus : CAN bus is the method to communicate such info with other devices. Davega has implemented BMS readings recently with VESC connected. There is simply no SPI output. ISOSPI/isolated SPI output is only available on the master/slave BMS configuration. I don’t see a reason offering ISOSPI output on XLITE even if it is used between both 12S monitoring IC
can you make xlite with LTC6812 30s?
Which chargers can we buy communicate with ennoidbms?
Haven’t seen this until now, great read!
I wrote that blog long time ago. Still valid today. LTC6812 are now getting expensive and scarce due to the global part shortage. I had hundreds of them at the beginning of this year, but almost all gone now. That is the reason I’m moving to multiple 12S IC such as LTC6804 & LTC6811 for XLITE & SS-24. I’m planning to use a single PCB design for all possible configuration instead of having multiple PCB design & components for 15, 18 & 24S in the future. The new design might eventually make sourcing components a lot easier for me and even cheaper to manufacture for large batches.
It could be possible to use 3 IC to get up a design able to manage up to 36S
damn bro, you seem really ennoid at him
That’s funny, but everyone can ask any questions even if I seem to be ennoid
Can a vesc or other controller ever fail super catastrophically? Destroying more than itself?
Once I had an ebike controller with stupid high current limits “explode”(pop)… potted in epoxy…
This question is likely better served in another thread…
But in the context of an electric skateboard, catastrophic failures can happen to any component. Nothing is perfect.
As for this new BMS, I’m definitely in for one.
A humidity sensor sounds useful, especially if the sensor values can be communicated to telemetry devices over CAN. It would be even better if the sensor wasn’t directly on the board though. Personally, I build all the electronics into the deck and use the enclosure only as a cover (it doesn’t carry any weight). The advantage is that if I get a little water in the enclosure (which does happen occasionally), it remains at the bottom of the enclosure and unless there’s a lot of it (which does not happen), none of the electronics get wet.
For me, when the BMS gets wet, it’s already a bit late for an alarm. If I could be alarmed that the bottom of my enclosure is wet though, that would be helpful.
Is there any possibility to connect an external humidity sensor?
For humidity readings, the actual IC is board mounted
Yes, it is in theory well possible to add an external humidity sensor through the use of the I2C connector that is normally used for the display &/or expansion ADC128D818 based temp module.
Small firmware changes might be required to enable an additional external HDC1080 or SI7020 sensors. The code is already functional for those IC, it would simply require to define a non-conflicted specific I2C address for the external module and include it in the firmware I2C reading loop.
I’m definitely interested in a charge only 12-15s bms that will fit in the onewheel battery box.
I finally got to testing my ENNOID-BMS today. I successfully complied the v1.4 Ennoid Tool on Mac OS (here it is in case anybody else needs it: ENNOID-BMS-ToolV1.4.app.zip (3.3 MB)) and the firmware update went smoothly as well. One slightly confusing bit was that I needed to check “show non-default firmwares” to get the firmware file listed.
I haven’t been able to get the CAN communication working though. I set the “Emit status over CAN” to True (not sure if that’s necessary) and all other CAN settings looked good at default.
I don’t have the EN pin connected on the CAN port but I was testing while having the BMS connected to the USB to make sure it’s not in the sleep mode. I do have both 5V and GND connected.
Is there a good way to troubleshoot this? Is it maybe possible to log incoming CAN communication?
BTW, I got a little confused by the fact the master branch does not contain the latest code version, which is unusual. Other than that, I like it a lot. Clearly a lot of time and work went into this.
Update: I split the 5V wire going from the VESC and connected it to both 5V and EN on the Ennoid BMS. Now the BMS wakes up (starts LED-flashing and beeping) as I turn the VESC on, which I believe is expected. Still no CAN communication though. I even tried swapping CANH/CANL in a desperate try but no joy.
Just in case this is relevant (though I don’t think so): I have the 18S ENNOID-BMS-SS-LITE and I’m testing it with an 8S pack. I only connected the balance lead pins 0-8 though I did read in the user guide I should connect all other BMS balance lead pins to the positive terminal. I didn’t do that since it’s too much work. 
I’m still getting correct readings for the first 6 cells (in the Ennoid Tool), which is good enough for testing purposes.
I dont know what canbus IC the ennoid BMS’ are using but having CANH and CANL swapped is generally a death sentence for the chip, definitely is the case with canbus ICs used in VESC4.12s and onward (SN65HVD232DR).
CAN IC is isolated, so it requires 5V+GND from esc to work. The additionnal 5V EN pin is for waking up the BMS from the ESC. It can be used for “push to start” BMS function.
I’m now moving back to standard non-isolated CAN bus IC on the future boards due to the global part shortage…
V1.4.0 has been tested and seemed to work well, but I’m still working on VESC CAN & VESC command integration. There is now the “emit status protocol =VESC”" option in the app to enable it. I just added this new features last week. It might still contain bugs. V1.3.5 was working fine with CAN comm AFAIK, but with EBMS protocol. I will check back later this week to see if there is issue with 1.4 on that topic.
I finished to include a compressed XML file into the EBMS firmware this morning. I will test next week if everything works as expected. XML file will allow VESC app to load a custom user interface when an EBMS hardware gets connected. The idea is to have the same functionnalities as the not yet completely finished/released VESC BMS. So, basically VESC will connect to EBMS over CAN bus and will get the same datas as if it was connected to a VESC BMS. Also, you will be able to get ENNOID-BMS data from CAN forward on VESC tool & also get a custom user interface when connecting EBMS over USB or CAN forward. The EBMS tool will still have more feature rich configuration options, but VESC tool will be good for 90% of use case.
You should use a CAN tool like busmaster, PCANVIEW or even an scope in other to see if there is CAN data coming to the IC.
@Prism Which ENNOID firmware version have you used for that test? I tested with both v1.4 and v1.3 and no joy.
Kind of surprised of my improving coding/hacking skills…Seems to work fine on VESC tool at first try. XML file is loading fine & real time data as well. Just SOC seems to be off a bit…
I’m on v1.3
this is fabulous thanks for sharing. can’t wait to ditch discharge BMS. with that integration it would be possible to do it safely 
Ive got a few of these XT90i connectors, just wondering the use, either with this BMS or just creative applications to use a XT90i Over a XT90 (noob question)
I have read that the the extra 2 pins can be used for ESC/GND but im thinking preahps thats more for drones.
Able to shed some light?
The user manual which is available on the website for SS boards explain one particular use case for an xt90i connector with the actual BMS, but why this question out of nowhere?
