In the VESC Tool set:
- App Settings > General > App to Use: PPM and UART
- App Settings > UART > Baudrate: 115200 bps
Assembly and mounting to a deck
If you purchased a kit please read the assembly instructions.
Installing assembled DAVEGA is straightforward. On boards with a bottom mounted VESC, you will typically want to make a small hole in the deck to route the cable. You may want to unpin the crimps from the cable connector to be able to route through a smaller hole.
On boards with a top mounted VESC, consider printing the following spacer so that you can easily route the cable out of the housing.
See the installation section in the gallery for examples of how people installed DAVEGA on their boards.
Note that the DAVEGA baseplate is made of aluminum and thus is fairly soft. When mounting the housing to the baseplate, be sure not to overtighten the bolts, otherwise you'll strip the threads.
Connecting to VESC
Each DAVEGA pin connects to the equally labeled VESC pin. For example, GND connects to GND, RX connects to RX, 3.3V connects to 3.3V or VCC, etc.
If you have DAVEGA X v1.1, it’s critical that you don’t accidentally connect it to the 5V input. This would destroy it instantly.
DAVEGA software consists of two parts referred to as bootloader and firmware. They can be thought of as a (simple) operating system and an application. You can have multiple versions of the firmware installed and switch between them. You can't have multiple bootloaders though.
For the firmware to be compatible with the bootloader, the major version must agree, i.e. the first number must be the same. For example, firmware v2.0.1 is compatible with bootloader v2.3 but not with bootloader v1.1.
If you accidentally installed an incompatible firmware, you can always switch back to the previous version by holding the down button while the device is booting up.
Updating firmware over WiFi
Press the middle button to enter the menu. First, you need to set the WiFi SSID and password in the WiFi submenu.
Then, go to the Firmware submenu and select check for updates. You will get the listing of the available firmware versions. Select the one you want to install and choose download and use.
Firmware updates often lead to recoverable memory errors. If this happens, you'll get the error details and will be asked to press any button. After that the device will reboot and re-attempt to download the firmware, which almost always succeeds without further errors.
Updating bootloader and firmware over USB
Before updating the bootloader, make sure you know your device ID. Enter the menu, choose About, and take a note of your device ID. Alternatively, you can retrieve the device ID using the DAVEGA X Tool (see below).
Download and install the CP2102 drivers for your operating system.
Next, download the bootloader and firmware from the downloads page. The bootloader file is device specific; the firmware file is not. From the same page, you will also want to download and extract the DAVEGA X Tool. Make sure you put the executable, the bootloader .bin file and the firmware .dfs file all in the same directory.
To access the USB port, you will need to remove the DAVEGA from your board and loosen the 4 bolts holding the PCB to the housing. Then carefully lift the side of the PCB away from the buttons and plug into the microUSB port.
Now you are ready to run the DAVEGA X Tool. You will need to run it repeatedly, once for each action. Start with detecting the DAVEGA port or enter it manually. Next, it's a good idea to create a backup of your filesystem. After that, update the bootloader and firmware. Please remember that the major version of the bootloader and firmware must agree to be compatible.
Starting from v1.2.0, data can be backed up to cloud over WiFi. Enter the Backup submenu and select backup config & data. (In v3.x.x, go to Update & Backup first.)
Alternatively you can make an offline backup over USB using the DAVEGA X Tool.
The offline backup can be restored using the Import files action in the DAVEGA X Tool.
Online backup can be downloaded from the backups page and restored the same way as the offline backup.