Just freshly did a git pull on one of my 3.2 odrive boards.
I updated the code to reflect my hardware setup, it compiles and flashes just fine. right after the make flash, the odrive does its initialization sequence (beep), and then the motors slighly turns back and forth (about a quarter of a turn i’d say). then the tools/demo.py does work as intended, the motor turns as expected. But if i power off/on the odrive. nothing works: the initialization sequence is not done at all (no beep, no motor turning), and usb communication does not seem to happen. it’s as if the board was dead. However, if i reflash it => it works again until i power off the odrive.
Any idea what could cause this behavior ?
some details below.
root@MTBD00694:~/ODriveFirmware/Firmware# git show commit be53d965fbc7262a4abb9022b227e4115b554e47 Merge: a26224f bb9d4f5 Author: Oskar Weigl <email@example.com> Date: Fri Feb 23 17:17:42 2018 -0800
using a turnigy aerodrive SK3 6374 149 and a CUI encoder 490-AMT102-V
I followed the readme instructions
- changed Inc/main.h to set HW_VERSION_MINOR to 2
- let the usb values as default (i just want to use tools/demo.py for now)
- i check the CUI dip swiches, they are all on the down position, which according to documentation refers to 2048 (see page 4 on the data sheet), which is the default value used for ENCODER_CPR
- i counted the POLE_PAIRS, there are indeed 14 magnets, so the default value in the code (7) does work
- brake_resistance is 0.47f and i use a CGS HSA50 R47 J 1634 that i beleive originates from the odrive shop (or maybe a mouser reference that i found on the forum)
- for motor_drive, the default value is ok for my motor i believe
What could be wrong ? could it be related to the code or my hardware setup ?