Thank you for the info. I’m trying to build the latest ENNOID Tool to test the sumOfIndividualCellVoltage setting. The setting is not available in VESC Tool and ENNOID Tool v5.04 doesn’t work well with the FW v5.05.
BTW, your GitHub repo is a bit confusing. I’m on a Mac so I can’t use the pre-built files. I instead grabbed the source files at the v6.00 release. But it turns out these are actually the v5.04 sources. I guess the problem is you release from the ENNOID branch rather than from master. Maybe it’s time to merge?
Also, the build always fails because of the missing firmware files. Is there a quick fix? So far I always grabbed one firmware file and copied it at the location where all firmware files are expected to get it to build.
Edit: Actually the ENNOID branch also only has v5.04. Are the latest sources not available in the repo?
@janpom Hey, I’d recommend upgrading to firmware 6.00 before proceeding, 5.05 is pretty buggy especially on V1s. I had to downgrade to 5.04 until 6.0 came out, which fixed all my problems.
There is a 5.05 version of Ennoid tool but it’s hard to find because it’s on a different page than 5.04 and 6.0.
Furthermore you have to reboot the BMS for it to go into the charge state when it’s plugged in to USB and showing the “powered down” opstate like it is in your video. Go to the terminal tab and type “reboot”. If nothing happens after typing reboot then click disconnect and re-connect in the Ennoid tool and it should work after that.
On VESC tool mobile or desktop, you can use the “Allow charging” button to see if it charges.
If it still not charge after pressing this button, there is an issue with the configuration and the XLITE goes into Power down mode.
Yes firmware 5.05 on github was compiled with another compiler (keil uvision instead of GCC) and turned out to be sometimes buggy depending on user configuration. Issue with memory allocation or similar. 6.00 is back to GCC compiler
The compiled firmware is available on the website folder for using with VESC tool or bundled in the ENNOID-BMS-tool software directly.
I’d be glad to share the latest version of firmware and software code for compiling a MacOS version. I simply don’t know how to do this myself. I have enough at maintaining windows and linux ENNOID-BMS-Tool.
Working with Ennoid V3 connected to LilFoc 3.1. Stock XR pack and known good charger. Other settings seem right. I cannot for the life of me get the BMS to enter the Charge State. When the charger is plugged in it attempts to initiate but then shuts down after timing out. If trying to “Allow Charge” from the VESC tool it powers down immediately. @ENNOID , any thoughts?
It’s a discourse anti-spam feature. You just have to do this to be able to post images
Trust Level 1 – Basic
At Discourse, we believe reading is the most fundamental and healthy action in any community. If a new user is willing to spend a little time reading, they will quickly be promoted to the first trust level.
This is a very strange behaviour, it should reboot and not just shut itself down. Any picture showing your setup. Something might not properly be connected. The BMS goes into charging state, but no current is flowing in, so the XLITE shuts down itself.
@ENNOID, thanks. I agree its seems weird. Here are some pics of my test setup. I assume I should not need to have the motor connected to test the battery side. Relatively new to this, but perhaps not a complete novice and didn’t hit any obvious snaps on setting it up thus far. Let me know what other info may help you.
Could you try without any accessories connected. Button, display, CAN. I think your button might not be wired properly and shuts down the charge process. Hard to see exactly from the picture
With everything unplugged.
I think I see 9 LED flashes upon pressing “Allow Charging” in VESC tool.
The BMS stays on and does not disconnect or restart, but not getting current from the charger. Charger LED stays green.
I assume I don’t need to worry about the temps being reported? This is with 0 sensors per IC. I think I have all the Limits set to not allow Temps to prevent charging.
yes, that is weird, maybe you could share your settings in PM so we can try to troubleshoot this in private.
For now, 9 Blink is error code #9 which is FAULT_CODE_CELL_SOFT_UNDER_VOLTAGE. That is possible that a low cell is blocking the charge process due to soft over voltage setting, but it could be something else as well.
@ENNOID I have questions regarding CAN wires shielding.
xlite v3 to be used in one wheel balance vehicle - CAN wire length 70-80cm. Cable will be routed away from motor phase wires, but with very close proximity to charge wires and main discharge wires. Battery configuration 18S2P, short current battery draw spikes should not exceed 40-50A. I would like to adjust balancing algorithm parameters while riding based on BMS data, so having reliable data is important.
What would be your recommendations for shielding CAN wires?
Do I need the wires to be shielded or twisted pair would be enough in this case (away from motor phase wires)
If not, should the shield be grounded?
If so, should I ground it to GND or vehicle aluminum frame?
Hard to says which one is the best option, but here is what I can tell:
Having some shielding helps against noise.
Having twisted pair also helps against noise
Having a shield which is grounded on the frame/conductive mass might also help, but it should not be connected on both ends or connected over two different spot otherwise you will create other problems. You can likely skip connecting the shield to anything to avoid any downside.
Connecting a shield to the board electrical GND (battery-) is not a good practice.
