Troubleshooting

common issues that may be encountered and where to seek further information a channel is not turning on when sending an "on" can command message the main unit led is blinking yellow by default, the unit requires the dronecan armingstatus message to be sent periodically with the "fully armed" status for the micro flux to be armed by default, each channel will only respond to can command messages when the micro flux is armed if the led is blinking yellow the micro flux is disarmed arming the vehicle should turn the led to blinking aqua, and allow it to be commanded "on" the "channel x command message response" setting can be set to "always respond" so that "on" commands will always be handled regardless of arm status alternatively, arming can be disabled with the "dronecan require armed msg" setting and the unit will be considered always armed the main unit led is solid orange the unit is in communications only mode and channels can only be turned off please restart the device or enter the control page of the hargrave configurator to leave communications only mode the main unit led is blinking red the unit is in an error state and no channels can be enabled the error state may have been caused by a configuration corrupt or invalid configuration state, or a system wide error threshold being exceeded with the error response "turn all channels off" selected to resolve configuration errors connect the unit to the hargrave configurator if the error is caused by a software protection being active, resolve the condition that is causing the error to be active the channel led is blinking red the channel is locked out by an error and cannot be turned on this could mean that a channel software protection with the response "turn channel off" is active, or a bus/system wide software protection is active that is configured to turn this channel off the led will switch from blinking to solid red when all error conditions clear, and can then be turned on relevant section a channel voltage is lower than expected or zero while "on" if the voltage is lower than expected check that the output current is within the datasheet limit specified for the channel if excessive current is drawn, including short circuits, the hardware overcurrent protection will reduce the output voltage to protect the device if the current is within limit, ensure that input voltage is at least 2v above the set channel voltage the buck topology of micro flux means it cannot output a voltage above the input voltage a channel did not turn on on startup/upon arming despite being configured to if a channel was configured to turn on at a given event, startup or upon device arming, and didn’t, it was likely caused by an error being active on that channel this could mean that a channel software protection with the response "turn channel off" is active, or a bus/system wide software protection is active that is configured to turn this channel off the led will switch from blinking to solid red when all error conditions clear, and can then be turned on with a can command message relevant section an error condition cleared by the channel did not turn back on channels will not automatically turn on after an error condition that caused it to turn off has cleared relevant section the main led is blinking red on power on a fault was detected on start up connect to the configuration tool to see further details about the detected error the error will need to be resolved before normal operation can continue the errors are also reported to the dronecan debug message system if using dronecan signalling relevant section the main led is solid red on power up an unrecoverable error was detected, either in the unit's hardware or firmware the unit should be returned relevant section