|
typedef enum {
MEICanMessageFIRMWARE_INVALID,
MEICanMessageFIRMWARE_VERSION,
MEICanMessageNOT_INITALIZED,
MEICanMessageCAN_INVALID,
MEICanMessageIO_NOT_SUPPORTED,
MEICanMessageFILE_FORMAT_ERROR,
MEICanMessageUSER_ABORT,
MEICanMessageCOMMAND_PROTOCOL,
MEICanMessageINTERFACE_NOT_FOUND,
MEICanMessageNODE_DEAD,
MEICanMessageSDO_TIMEOUT,
MEICanMessageSDO_ABORT,
MEICanMessageSDO_PROTOCOL,
MEICanMessageTX_OVERFLOW,
MEICanMessageRTR_TX_OVERFLOW,
MEICanMessageRX_BUFFER_EMPTY,
MEICanMessageBUS_OFF,
MEICanMessageSIGNATURE_INVALID,
} MEICanMessage;
|
| |
Change History: Modified in the 03.02.00 |
| MEICanMessageFIRMWARE_INVALID |
| |
The CAN firmware is not valid. This message code is returned by meiCanCreate(...) if the CAN hardware bootloader detects no firmware has been loaded or the firmware signature is not recognized. To correct this problem, download valid firmware with meiCanFirmwareDownload(...). |
| MEICanMessageFIRMWARE_VERSION |
| |
The CAN firmware version does not match the software version. This message code is returned by meiCanCreate(...), meiCanFirmwareDownload(...), or meiCanFirmwareUpload(...) if the CAN firmware version is not compatible with the MPI library. To correct this problem, download the proper firmware version with meiCanFirmwareDownload(...). |
| MEICanMessageNOT_INITIALIZED |
| |
The CAN firmware did not initialize. This message code is returned by meiCanCreate(...) if the controller did not copy the configuration structure from flash to memory after power-on or controller reset. To correct this problem, verify the controller firmware is correct and the controller hardware is operating properly. |
| MEICanMessageCAN_INVALID |
| |
The can network number is out of range. This message code is returned by meiCanCreate(...) if the network number is less than zero or greater than or equal to MEICanNetworkMAX.
|
| MEICanMessageIO_NOT_SUPPORTED |
| |
The CAN node does not support the specified I/O. This message code is returned by CAN methods that read/write to a digital or analog input/output that is out of range. To prevent this problem, specify a supported I/O bit. |
| MEICanMessageFILE_FORMAT_ERROR |
| |
The CAN firmware file format has an error. This message code is returned by meiCanFirmwareDownload(...) if the specified file has an error in its internal headers. This indicates a corrupted file. To correct this problem, use the original CAN firmware file or reinstall the software distribution. |
| MEICanMessageUSER_ABORT |
| |
The CAN firmware loading was aborted. This message code is returned by meiCanFirmwareDownload(...) or meiCanFirmwareUpload(...) when the firmware loading is aborted by the user via the callback function. This message code is returned for application notification. It is not an error. |
| MEICanMessageCOMMAND_PROTOCOL |
| |
The CAN command failed due to a protocol error. This message code is returned by CAN methods that do not get a valid response from a CAN node. To correct this problem, check your CAN nodes for proper operation. |
| MPICanMessageINTERFACE_NOT_FOUND |
| |
The CAN interface is not available. This message code is returned by meiCanCreate(...) if the specified controller does not support a CAN network interface. To correct this problem, use a controller that has a CAN interface. |
| MEICanMessageNODE_DEAD |
| |
The CAN node does not respond. This message code is returned by CAN methods that read/write from a CAN node and the node fails the health check. This message code indicates a node hardware or network connection problem. To correct this problem, verify the node operation and network connections. |
| MEICanMessageSDO_TIMEOUT |
| |
The CAN command failed due to a timeout. This message code is returned by CAN methods that do not get a response from a CAN node within the timeout period. To correct this problem, check your CAN nodes for proper operation. |
| MEICanMessageSDO_ABORT |
| |
The CAN command failed due to a user abort. This message code is returned by CAN methods when an SDO transaction is aborted. |
| MEICanMessageSDO_PROTOCOL |
| |
The CAN command failed due to an SDO protocol error. This message code is returned by CAN methods when an SDO transaction fails because the node did not conform to the CANOpen protocol. |
| MEICanMessageTX_OVERFLOW |
| |
The controller's transmit buffer overflowed. This message code is returned by CAN methods that failed to transmit a message due to an internal memory buffer overflow. |
| MEICanMessageRTR_TX_OVERFLOW |
| |
The controller's transmit buffer overflowed. This message code is returned by CAN methods that failed to transmit a message due to an internal memory buffer overflow. |
| MEICanMessageRX_BUFFER_EMPTY |
| |
The controller's receive buffer is empty. This message code is returned by CAN methods that expected to get a response from a CAN node, but the controller's receive buffer was empty. |
| MEICanMessageBUS_OFF |
| |
The CAN network bus is in the off state. This message code is returned by CAN methods that are not able to use the CAN network because the bus is off. To correct this problem, verify the node operation and network connections. |
| MEICanMessageSIGNATURE_INVALID |
| |
When initialising the CAN system, some tests are performed to make sure that the CAN processor is returning a valid signature value. If an unexpected signature is returned, this error message is returned. A probable cause for this error is that the bootloader is invalid. To correct this problem, you will need to return the controller to MEI to fix the bootloader. |
