Errors

there are several errors and warnings that the unit tracks these errors are saved to internal non volatile memory and will persist until they are manually reset these errors are viewable in the configuration tool these errors persist even when the unit is power cycled seeing an error present in the configuration tool is an indication that the error occurred since the errors were last reset and not necessarily that it happened the last time the unit was powered the possible errors are listed below error description corrupt configuration configuration of onboard unit settings is corrupt potential firmware update occurred, or hardware fault configuration invalid an invalid configuration was saved onto the unit and the unit entered an error state bootloader error the bootloader is reporting an error within either firmware or recovery section firmware error active the system encountered an invalid device configuration or generated a hard error watchdog reset occurred a software crash was detected, causing unit to restart logged data cleared the logging system reported a change in data types the stored data was cleared logging system read only the logging system is forced into a read only state no new data will be logged but existing data can be read logging system error the logging system is in an error state the unit will not log any data while in this state mcu overtemperature limit the main unit processor temperature limit was exceeded bus undervoltage limit the minimum voltage for the unit was exceeded bus overtemperature limit the input bus maximum temperature was exceeded bus overcurrent limit the configured maximum input current for the unit was exceeded bus overvoltage limit the maximum voltage for the unit was exceeded 3v3 deviation/brownout the internal 3v3 rail deviated from the nominal value or experienced a brown out mcu absolute overtemperature occurred the system entered an error state because the main unit processor exceeded the maximum hardware limit bus absolute overtemperature occurred the system entered an error state because the input power bus exceeded the maximum hardware limit channel overcurrent limit a channel output current exceeded the configured current limit channel overvoltage a channel output voltage exceeded the overvoltage deviation limit channel undervoltage a channel output voltage exceeded the undervoltage deviation limit channel gpio configuration error a channel’s configured and actual state do not match channel power sensor lost communication was lost with one of the channel power sensors this could indicate a hardware issue or excessive emi flash corrupted the errors saved to the device were cleared due to corruption or a firmware update channel absolute overtemperature occurred a channel was shut off because the channel temperature exceeded the maximum hardware limit external clock failure the primary device clock source has failed this is indicative of unit failure please contact support warm boot detected the unit has detected a warm reboot this could indicate the unit has recovered from a software crash configuration errors there are the following additional errors triggered by invalid device configurations code error description cfg 0x2d node id invalid 0 is not a valid dronecan node id and therefore force node id cannot be enabled cfg 0x38 duplicate bus/channel ids all bus/channel ids must be unique