error led blinks 8x, not in the user manual
-
Basicmicro Support
- Posts: 1594
- Joined: Thu Feb 26, 2015 9:45 pm
Updated Error/Warning Blink codes. Not yet updated in the user manual
Updated Error and Warning bit masks.
//errorStatus.lo
#define ERROR_NONE 0x00
#define ERROR_ESTOP 0x01
#define ERROR_TEMP 0x02
#define ERROR_TEMP2 0x04
#define ERROR_MBATHIGH 0x08
#define ERROR_LBATHIGH 0x10
#define ERROR_LBATLOW 0x20
#define ERROR_FAULTM1 0x40
#define ERROR_FAULTM2 0x80
#define ERROR_SPEED1 0x0100
#define ERROR_SPEED2 0x0200
#define ERROR_POS1 0x0400
#define ERROR_POS2 0x0800
#define ERROR_CURRENTM1 0x1000
#define ERROR_CURRENTM2 0x2000
#define ERROR_MBATLOW 0x4000
//warnStatus
#define WARN_NONE 0x000000
#define WARN_OVERCURRENTM1 0x010000
#define WARN_OVERCURRENTM2 0x020000
#define WARN_MBATHIGH 0x040000
#define WARN_MBATLOW 0x080000
#define WARN_TEMP 0x100000
#define WARN_TEMP2 0x200000
#define WARN_S4 0x400000 //HOME, LIMITF, LIMITR
#define WARN_S5 0x800000 //HOME, LIMITF, LIMITR
#define WARN_OVERREGENM1 0x40000000
#define WARN_OVERREGENM2 0x80000000
0x40000000 is a Regen overcurrent warning. During this warning deceleration is limited to reduce regen current. This would not cause a blink error code.
0x10000 is a Over Current warning. During this warning the motor is free wheeled to reduce current. This is done actively so the average current remains at or below the current limit set.
0x1000 Is a Over Current ERROR. This happens if the current in a single cycle(1/20000th of a second excedes 200% of the maximium current limit set. This causes a 9 blink error and shutsdown the motor channels(both). Please double check your blink count.
A 8 blink count would be caused from a Position Error which could only trigger if you have set the Position Error Limit setting and are using Position control.
This assumes you are using the latest firmware.
Please provide a description of your setup(motor models/specs, battery/power source etc). The more infor the better, for example how everything is wired can effect noise.
Changing the speed/power smoothing with a sign wave input(are you using analog inputs or converting that into a RC pulse or sending packet serial commands) shouldn't cause any massive current spikes so unless your load is high this could be a noise problem.
Please list any settings changed you have made that are not the defaults. That may help determine the problem as well.
Also, are you basing the current draw on the Roboclaw readouts or from a current clamp meter of your own(or something similar)? If the later the current at the power source/battery is almost never the current at the motor(only when duty is at 100%). For example if the current at the battery if 40 amps and the duty is 50% the motor is pulling 80 amps. If Duty was 25% the motor is pulling 160amps etc...
//errorStatus.lo
#define ERROR_NONE 0x00
#define ERROR_ESTOP 0x01
#define ERROR_TEMP 0x02
#define ERROR_TEMP2 0x04
#define ERROR_MBATHIGH 0x08
#define ERROR_LBATHIGH 0x10
#define ERROR_LBATLOW 0x20
#define ERROR_FAULTM1 0x40
#define ERROR_FAULTM2 0x80
#define ERROR_SPEED1 0x0100
#define ERROR_SPEED2 0x0200
#define ERROR_POS1 0x0400
#define ERROR_POS2 0x0800
#define ERROR_CURRENTM1 0x1000
#define ERROR_CURRENTM2 0x2000
#define ERROR_MBATLOW 0x4000
//warnStatus
#define WARN_NONE 0x000000
#define WARN_OVERCURRENTM1 0x010000
#define WARN_OVERCURRENTM2 0x020000
#define WARN_MBATHIGH 0x040000
#define WARN_MBATLOW 0x080000
#define WARN_TEMP 0x100000
#define WARN_TEMP2 0x200000
#define WARN_S4 0x400000 //HOME, LIMITF, LIMITR
#define WARN_S5 0x800000 //HOME, LIMITF, LIMITR
#define WARN_OVERREGENM1 0x40000000
#define WARN_OVERREGENM2 0x80000000
0x40000000 is a Regen overcurrent warning. During this warning deceleration is limited to reduce regen current. This would not cause a blink error code.
0x10000 is a Over Current warning. During this warning the motor is free wheeled to reduce current. This is done actively so the average current remains at or below the current limit set.
0x1000 Is a Over Current ERROR. This happens if the current in a single cycle(1/20000th of a second excedes 200% of the maximium current limit set. This causes a 9 blink error and shutsdown the motor channels(both). Please double check your blink count.
A 8 blink count would be caused from a Position Error which could only trigger if you have set the Position Error Limit setting and are using Position control.
This assumes you are using the latest firmware.
Please provide a description of your setup(motor models/specs, battery/power source etc). The more infor the better, for example how everything is wired can effect noise.
Changing the speed/power smoothing with a sign wave input(are you using analog inputs or converting that into a RC pulse or sending packet serial commands) shouldn't cause any massive current spikes so unless your load is high this could be a noise problem.
Please list any settings changed you have made that are not the defaults. That may help determine the problem as well.
Also, are you basing the current draw on the Roboclaw readouts or from a current clamp meter of your own(or something similar)? If the later the current at the power source/battery is almost never the current at the motor(only when duty is at 100%). For example if the current at the battery if 40 amps and the duty is 50% the motor is pulling 80 amps. If Duty was 25% the motor is pulling 160amps etc...