Der zweite Treiber hat bis jetzt noch nicht rumgezickt, war aber auch nur einmal im Einsatz vor der langen Trockenheit hier im Südwesten von Deutschland. Ich habe aktuell die Firmware von Svolo auf dem Ardu
// ----- gear motors --------------------------------------------------
// for
brushless motors, study the sections (drivers, adapter, protection etc.) in the Wiki (
https://wiki.ardumower.de/index.php?title=DIY_Brushless_Driver_Board)
#define MOTOR_DRIVER_BRUSHLESS 1 // uncomment this for new
brushless motor drivers
//#define MOTOR_DRIVER_BRUSHLESS_MOW_DRV8308 1 // uncomment for
brushless DRV8308 driver and mowing
motor
#define MOTOR_DRIVER_BRUSHLESS_MOW_A4931 1 // uncomment for
brushless A3931 driver and mowing
motor
//#define MOTOR_DRIVER_BRUSHLESS_MOW_BLDC8015A 1 // uncomment for
brushless BLDC8015A driver and mowing
motor
//#define MOTOR_DRIVER_BRUSHLESS_MOW_JYQD 1 // uncomment for
brushless JYQD driver and mowing
motor (
https://forum.ardumower.de/threads/jyqd-treiber-und-sunray.24811/)
#define MOTOR_DRIVER_BRUSHLESS_GEARS_DRV8308 1 // uncomment for
brushless DRV8308 driver and gear/traction motors
//#define MOTOR_DRIVER_BRUSHLESS_GEARS_A4931 1 // uncomment for
brushless A4931 driver and gear/traction motors
//#define MOTOR_DRIVER_BRUSHLESS_GEARS_BLDC8015A 1 // uncomment for
brushless BLDC8015A driver and gear/traction motors
//#define MOTOR_DRIVER_BRUSHLESS_GEARS_JYQD 1 // uncomment for
brushless JYQD driver and gears/traction
motor
#define MOTOR_FAULT_CURRENT 6.0 // gear motors fault current (amps)
#define MOTOR_OVERLOAD_CURRENT 0.8 // gear motors overload current (amps)
#define MAX_MOTOR_ERROR_COUNTER 3 // max retrys in case of
motor errors until mower gives up
// ----- mowing
motor -------------------------------------------------
// NOTE:
motor drivers will indicate 'fault' signal if
motor current (e.g. due to a stall on a molehole) or temperature is too high for a
// certain time (normally a few seconds) and the mower will try again and set a virtual obstacle after too many tries
// On the other hand, the overload detection will detect situations the fault signal cannot detect: slightly higher current for a longer time
// choose ticks per cutting disc revolution :
#define MOW_TICKS_PER_REVOLUTION 12 / 2 // odometry ticks per cutting disc revolution
#define MOW_FAULT_CURRENT 8 // mowing
motor fault current (amps)
#define MOW_OVERLOAD_CURRENT 2.0 // mowing
motor overload current (amps)
// should the direction of mowing
motor toggle each start? (yes: true, no: false)
#define MOW_TOGGLE_DIR true
//#define MOW_TOGGLE_DIR false
// should the error on
motor overload detection be enabled?
#define ENABLE_OVERLOAD_DETECTION true // robot will stop on overload
//#define ENABLE_OVERLOAD_DETECTION false // robot will slow down on overload
// should the
motor fault (error) detection be enabled?
#define ENABLE_FAULT_DETECTION true
//#define ENABLE_FAULT_DETECTION false // use this if you keep getting '
motor error'
#define ENABLE_RPM_FAULT_DETECTION true // use mow rpm signal to detect a
motor fault (requires mowing
motor with rpm output!)
//#define ENABLE_RPM_FAULT_DETECTION false // do not use mow rpm signal to detect a
motor fault
// should the robot trigger obstacle avoidance on
motor errors if
motor recovery failed?
#define ENABLE_FAULT_OBSTACLE_AVOIDANCE true
Ja, hatte den JYQD Treiber am Mower Anschluss.