You are here

VESCTOOL - Multiple VESC simultaneous configuration (Same CANBUS ID issues)

3 posts / 0 new
Last post
Filcas
Offline
Last seen: 3 weeks 3 days ago
VESC Free
Joined: 2019-06-03 21:16
Posts: 17
VESCTOOL - Multiple VESC simultaneous configuration (Same CANBUS ID issues)

Hello,

I have some questions about the use of VESCTOOL in terms of optimizing the configurations so it can easier to access in all cases.

Sometimes the connected VESCs needs to be reset or firmware upgrade and often (not sure why) the VESC ID of different hardware appears the same. For example, hardware A have ID 32, hardware B have ID 120 and hardware C have ID 32. This makes the hardware A and C to be seen as "same" by the VESCTOOL. The workaround is to connect each individual hardware to USB and rename the ID, but this is quite complicated when you are doing it remotely and the parts can only be accessed by CANBUS.

 

For this reason, my questions are if it is possible, either by the user interface or by terminal command line to do:

A) rename all VESC connected by CANBUS by the UUID and not by the app defined ID (this should overcome the problem of having the same repeated ID and so the CANBUS list can show them all)

B) Measure RL and FLUX from all connected motors and apply the readings to all motors (similar to the FOC wizard setup)

C) Measure hall sensors table and apply to all motors on CANBUS

D) Load different APP and MOTOR settings simultaniously to all hardware connected by CANBUS.

 

Let me know what you think and if this could be achieved. Solving the issue of same ID after reset/firmware upload will solve 90% of the issues, as the other things can still be done manually.

Thank you.

 
TheFallen
Offline
Last seen: 2 weeks 2 days ago
VESC FreeVESC Original
Joined: 2017-09-11 11:46
Posts: 222

The only problem with A) I can see is that the lower 11bits of the UUID will end up repeating every 2048 STM32F405s produced. So if you're exceptionally unlucky it's possible to buy two VESCs with the same lower UUID bits. Should be solveable by letting you change it in firmware.

I imagine that having all motors on one CANbus simultaneously re-measuring RL/FLUX/Halls could be quite dangerous/noisy but couldn't you trigger this by sending the CAN commands in quick succession?

It's an open source project, you're welcome to fork the code and add new code & commands that set teh default UUID and will enable you to re-measure parameters.
 

Filcas
Offline
Last seen: 3 weeks 3 days ago
VESC Free
Joined: 2019-06-03 21:16
Posts: 17

Thank you for the comments. 

Any ideas on how to get the A) sorted, or some way to rename the IDs if they are the same? 

For the other options, I was thinking the tasks to be done one after de other, no in parallel so this could avoid other issues.