List of Errors¶
enum dp_errors {
DP_NO_ERROR = 0,
DP_NO_DATA = 0,
DP_ACCESS_ERROR = -1,
DP_ERROR_NO_RESPONSE = -2,
DP_ERROR_NO_DEVICE = -3,
DP_ERROR_WRONG_PROTOCOL = -4,
DP_ERROR_TIMEOUT = -5,
DP_ERROR_CORRUPTED_DATA = -6,
DP_ERROR_WRONG_SIZE = -7,
DP_ERROR_WRONG_ID_LENGTH = -8,
DP_EEPROM_WARNING = -9,
DP_EEPROM_ERROR = -10,
DP_ERROR_DEVICE_DISCONNECTED = -11,
DP_ERROR_DEVICE_BUSY = -12
};
DP_ERROR_NO_RESPONSE¶
value: -2
Device hasn’t answered on request. Probably busy by computation. If this error remains for long time it might mean disconnection.
DP_ERROR_NO_DEVICE¶
value: -3
There is no device with given identifier on list, couldn’t open connection.
DP_ERROR_WRONG_PROTOCOL¶
value: -4
This error occurs when read data doesn’t fit to the frame-protocol. For end-user it’s communication error.
DP_ERROR_CORRUPTED_DATA¶
value: -6
Transmitted data is corrupted, however message is still stored in buffer, so you can try read this. (That’s why you have to check returned error code when reading from device, because error detection doesn’t trigger flushing buffer)
DP_ERROR_WRONG_SIZE¶
value: -7
Declared size of message and real message size are different. Possible transmission error.
DP_ERROR_WRONG_ID_LENGTH¶
value: -8
Device answered on DP_SEND_ID request, but it’s length doesn’t fit to DigiProtocol standard.
DP_EEPROM_WARNING¶
value: -9
Device sent it’s ID, but it has to use backup sector due to error in first ID sector. It will try repair first sector from backup, but it can be first signal that EEPROM device is in bad condition.
DP_EEPROM_ERROR¶
value: -10
Device tried to send it’s Identifier, but both sectors (normal and backup) are corrupted. Please try burn ID on device with IDBurner.
DP_ERROR_DEVICE_BUSY¶
value: -12
This error means that another process has claimed interface of device. Try again later.