I will check if BLE can work with V1 later this week and try to find a way to get it working. There is always the CAN bus option for configuring through a VESC if you have trouble with the USB
Sometimes residue can block the USB contact or need some cleaning with isopropyl alcool to get back on track.
Not that sure about your results, values seems to be quite offâŚ
Probably some bit scaling issue when âautoâ scaling function is used in the firmware with float, e.g.: âlibBufferAppend_float32_auto()â instead of libBufferAppend_float32() and/or also when the cell count varies.
It would be a bit easier to manage with the other CAN bus message type
I did not pay attention on data types yet. Only on byte sises.
My BMS is not connected to battery or battery equivalent.
It would be a bit easier to manage with the other CAN bus message type
What do you mean?
The original DieBieMS/ENNOID protocol can be chosen for CAN bus packets instead of VESC protocol.
You can also disable Elcon charger related CAN bus packet with the ENNOID-BMS tool
The original DieBieMS protocol do not use floatXX_auto(), but instead it uses a fix scaling for floats. The involved functions in the firmware are modCANSendStatusSlow() and modCANSendStatusFast() function. It also had only cell average, high and cell low reported to keep CAN bus traffic a bit lower when the cell count is high.
Benjamin Vedder also confirmed to me:
They have implemented âcustom configâ support for the next VESC tool mobile version⌠This means that it will soon be possible to configure the parameters of the XLITE-V2 over Bluetooth on top of the actual real time data capabilityâŚ
The nice thing about direct bluetooth over CAN bus is the fact that users will not have to care about the connection order between CAN bus and main power wires because GND reference is not and issue. The only drawback I see is no comm with VESC, so no SOC tracking and the VESC is not aware of the cell status+ pack temp during the discharge process.
Can you clarify how you would configure the xlite for 20s use using can/VESC tool solely? My usb c is definitely janky - and I tried opening my box again and this time connected my xlite fully rather than just the xt30 battery connection and usbc - which indeed failed - I have heard that the connnection order is important despite what it said on the site - I did power from the battery and charger first -then
Thermistors, then
Balance leads - 13 pin first - 12 pin second - then
Can bus (using 4 pins - can l, can h, ground, and 3 volt -
No fires 
or popping so I assume that was ok - after some futzing around in VESC tool I was able to get some can data - but it doesnât look like my xlite or my VESC tool is defaulting to 20s - I see only 16 cells - 1-10 are green - then what would be only cells 11-16 (13-19) are orange - charger is not connected so I donât think they are balancing - also Iâm missing 4 cells of the series - almost 100% certain the balance leads are wired to the pack correctly
Connection order between balance and battery xt 30 is not a big deal on the XLITE, but the CAN bus IC being non-isolated on the XLITE and also since a while on the SS boards due to the part shortage makes the CAN bus quite vulnerable to connection order when connecting any other devices on the CAN bus. For instance, if you keep CAN bus connected to the VESC and disconnect completely the battery- on the VESC (GND reference), you will likely kill the CAN bus IC. Iâd like to use isolated CAN bus IC to remove this potential issue, but I cannot get the isolated IC right now⌠The best I can do for now is improving the documentation around CAN bus connection. Note that the same can also happen on the USB port.
There is the XLITE PINOUT file on the website that explain how to wire the balance cables and also warn the user about CAN bus. If it is wired up properly you simply have to set in VESC tool the parameter: Number of cells=20 & Number of monitor IC = 2
Also, you can try uploading firmware again with VESC tool. Take the latest firmware on the website. I just updated it with the latest tweaks.
A quite bad video, but I think it can help you:
how long do you think till you can source some isolated can Chips
would it be possible to use something like this CAN Isolator
actually couldnât you just add optical/galvanic isolators before the CAN chip and have the CAN chip powered by the motor controller. effectively eliminating the need for a special CAN chip
https://au.mouser.com/ProductDetail/Maxim-Integrated/MAX22291CASA-V%2B?qs=Rp5uXu7WBW8%252BYtSC5H1U7w%3D%3D could work basically put it before the CAN ic
I was able to grab a thousand ISO1050 IC lately. They are big, isolated and I have been using those for while on my Master-LV & Master-HV board. My preferred IC would have been ISO1044, but not until mid-2023âŚ
It was a bit hard to get ISO1050 on the XLITE layout, but I was finally able to do it and added a Bluetooth module at the same time instead of UART connectorâŚI will try this out soon.
Probably an external CAN isolator would do the job as well, but it is not really needed if you plug in the CAN bus last and unplug it first.
i made an order for the late December Batch will that have the big isolated can tranciever.
If you want to test it, yes why not
i would be willing to test that hardware layout.
Just learned from @TheBoardGarage that it is possible to use wireless bridge to computer (TCP) function in VESC tool mobile to configure the XLITE-V2 with VESC deskptop⌠just specify the phone IP address to VESC tool desktop, connect and there you go.
So, it is possible right now to configure XLITE-V2 with a BLE module
VESC tool is just an awesome piece of software.
Testing new boards today⌠. Same size as XLITE-24-V2, 95x35mm. isolated CAN bus IC + Bluetooth module minus the UART connector. Remark the large CAN bus IC on the right and BLE module a bit under left, it was not easy to fit them there. You donât really need UART if you have BLE.
Configuration with VESC tool over BLE TCP bridge explained :
Once balance, battery and charger are plugged in, connect over the XLITE Bluetooth with your phone, enable TCP bridge in VESC tool mobile:
Then connect in VESC tool desktop with the IP address provided in VESC tool mobile:
You can configure the XLITE:
And stream real time data, enable/disable charging at will:
Once sealed, the battery pack datas can now be accessed and configured wirelessly, which is quite convenient. CAN bus IC being isolated, we wonât need to care about CAN bus connection order with this boardâŚbut only if you still decide to use CAN bus with your VESC, which is not really essential by the way.
