88d623bedb
* Add vitepress tree * Update existing workflows so they dont trigger on changes in the docs path * Add nojekyll, package.json, LICENCE etc * Add crowdin docs upload/download scripts * Add docs flaw checker workflows * Used docs prefix for docs workflows * Crowdin obvious fixes * ci: docs move to self hosted runner runs on a beefy server for faster builds Signed-off-by: Ramon Roche <mrpollo@gmail.com> * ci: don't run build action for docs or ci changes Signed-off-by: Ramon Roche <mrpollo@gmail.com> * ci: update runners Signed-off-by: Ramon Roche <mrpollo@gmail.com> * Add docs/en * Add docs assets and scripts * Fix up editlinks to point to PX4 sources * Download just the translations that are supported * Add translation sources for zh, uk, ko * Update latest tranlsation and uorb graphs * update vitepress to latest --------- Signed-off-by: Ramon Roche <mrpollo@gmail.com> Co-authored-by: Ramon Roche <mrpollo@gmail.com>
2.6 KiB
VESC ESCs (DroneCAN)
The VESC project is a fully open source hardware and software design for advanced FOC motor controllers. While it can be controlled using traditional PWM input, it also supports being connected over CAN bus using DroneCAN.
구매처
하드웨어 설정
배선
ESCs are connected to the CAN bus using the VESC CAN connector. Note that this is not the Pixhawk standard 4 pin JST GH connector. For more information, refer to the CAN Wiring instructions. ESC order does not matter.
Firmware Setup
The preferred tool for motor enumeration is the VESC tool. In addition to the normal motor configuration that you will have to setup in the VESC tool, you will also need to properly setup the app configuration. The recommended app setup is as follows:
| 매개변수 | Option |
|---|---|
| App to use | No App |
| VESC ID | 1,2,... |
| Can Status Message Mode | CAN_STATUS_1_2_3_4_5 |
| CAN Baud Rate | CAN_BAUD_500K |
| CAN Mode | UAVCAN |
| UAVCAN ESC Index | 0,1,... |
VESC ID should have the same motor numbering as in PX4 convention, starting at 1 for top-right motor, 2 for bottom-left motor etc.
However the UAVCAN ESC Index starts from 0, and as such it is always one index lower than the VESC ID.
For example, in a quadcopter the bottom left motor will have VESC ID = 2 and UAVCAN ESC Index = 1.
Finally the CAN Baud Rate must match the value set in UAVCAN_BITRATE.
Flight Controller Setup
Enable DroneCAN
Connect the ESCs to the Pixhawk CAN bus. Power up the entire vehicle using a battery or power supply (not just the flight controller over USB) and enable the DroneCAN driver by setting the parameter UAVCAN_ENABLE to 3 to enable both dynamic node ID allocation and DroneCAN ESC output.
PX4 설정
Assign motors to outputs using the Acutator configuration screen.
추가 정보
- VESC Project ESCs
- Benjamin Vedder's blog (project owner)