As i needed a complete overview over all can Messages, i started doing things properly following an accepted industry standard.
So i started building a dbc file for VESCs (and ofc. all other projects with the same or similar Firmware....).
Right now, there are not all messages in there, but the rest will follow over the course of this week. Also for now, the messages are only in there for one VESC with ID 1. So, it is far from done, but i wanted to share it anyways. If there are any thougths about posible improvements, please share them.
The most recent state can always be founde here:
https://gitlab.com/jonasbareiss/vesc-dbc
What are the plans for the Future?
- Complete all messages and signals
- Add additional nodes (2/4/8)
- Release CANoe Project with Simulation setup
- Use Resources to build automated testbench
First of all thanks for some great work, I've found it really useful! It seems there's now another status message (status 6) with signals ADC1, ADC2, ADC3 and PPM and I'm trying to include it in my version of your dbc-file.
According to the vesc documentation (https://github.com/vedderb/bldc/blob/master/documentation/comm_can.md) the scaling factors are supposed to be 1000 for all four of them, but using that seems to give the wrong output. The same documentation also claims that the scaling factors for status 1 (rpm, current and duty cycle) are 1, 10 and 1000, which you've instead set as 1, 0.1 and 0.1 to get reasonable results. Did you figure that out by experimenting or how did you do it?
Also, I've found there are typos in the signals for status 4 (says "staus" instead of "status")