Reads a CAN message from the receive queue of a FD capable PCAN Channel.
TPCANStatus __stdcall CAN_ReadFD( TPCANHandle Channel, TPCANMsgFD* MessageBuffer, TPCANTimestampFD *TimestampBuffer);
Parameters |
Description |
Channel |
The handle of a FD capable PCAN Channel (see TPCANHandle). |
MessageBuffer |
A TPCANMsgFD buffer to store the CAN message. |
TimestampBuffer |
A TPCANTimestampFD buffer to get the reception time of the message. |
The return value is a TPCANStatus code. PCAN_ERROR_OK is returned on success. The typical errors in case of failure are:
PCAN_ERROR_ILLPARAMVAL: |
Indicates that the parameters passed to the function are invalid. Check the value of the MessageBuffer; it should point to a TPCANMsgFD structure. |
PCAN_ERROR_ILLOPERATION: |
Indicates that the PCAN Channel passed to the function was not initialized using CAN_InitializeFD (class-method: InitializeFD). |
PCAN_ERROR_INITIALIZE: |
Indicates that the given PCAN channel was not found in the list of initialized channels of the calling application. |
PCAN_ERROR_BUSWARNING: |
Indicates a bus error within the given PCAN Channel. The hardware is in bus-warning status. |
PCAN_ERROR_BUSPASSIVE: |
Indicates a bus error within the given PCAN Channel. The hardware is in bus-passive status. |
PCAN_ERROR_BUSOFF: |
Indicates a bus error within the given PCAN Channel. The hardware is in bus-off status. |
PCAN_ERROR_QRCVEMPTY: |
Indicates that the receive queue of the Channel is empty. |
Specifying the value of NULL for the parameter TimetampBuffer causes reading a message without timestamp, when the reception time is not desired. An "Illegal Parameter Value" error will be returned when the MessageBuffer is wrong or the TimestampBuffer contains a value different than NULL and provokes an internal error, eg. accessing its memory.
The use of CAN_Read and CAN_ReadFD are mutually exclusive. The PCAN Channel passed to this function must be initialized using CAN_InitializeFD (class-method: InitializeFD). Otherwise the error PCAN_ERROR_ILLOPERATION is returned.
The CAN_ReadFD function returns received messages or status messages from the receive queue. It is important to call CAN_ReadFD repeatedly until the queue is empty. In case there are no more messages in queue, the value PCAN_ERROR_QRCVEMPTY is returned. The error code PCAN_ERROR_QRCVEMPTY is also returned if the reception of messages is disabled. See Receive Status Parameter for more information.
The receive queue can contain up to 32767 messages.
There are two possibilities for reading messages from the receive queue of a Channel:
Time-Triggered Reading: Consists in periodically calls to the CAN_ReadFD function. Typically, an application start a timer that every 50 or 100 milliseconds check for messages, calling the CAN_ReadFD function in a loop until the value of PCAN_ERROR_QRCVEMTY or another error condition is reached.
Event-Triggered Reading: Consists in reacting to a notification sent by the PCAN driver to a registered application, when a message is received and inserted in its receive queue. See Using Events to obtain more information about reading with events.
About bus errors / Status messages
If a bus-off error occur, an application cannot use the channel to communicate anymore, until the CAN controller is reset. With PCAN-Basic it is not possible to reset the CAN controller through a function directly. Consider using the PCAN-Basic property PCAN_BUSOFF_AUTORESET which instructs the API to automatically reset the CAN controller when a bus-off state is detected.
Another way to reset errors like BUSOFF, BUSWARNING, and BUSPASSIVE, is to uninitialize and initialise again the channel used. This causes a hardware reset.
The message type (see TPCANMessageType) of a CAN message indicates if the message is a 11-bit, 29-bit, FD, RTR, Error, or Status message. This value should be checked every time a message has been read successfully.
If the bit PCAN_MESSAGE_ERRFRAME is set in the TPCANMsg.MSGTYPE field, the message is an Error frame (see Error Frames).
If the bit PCAN_MESSAGE_STATUS is set in the TPCANMsg.MSGTYPE field, the message is a Status message. The ID and DLC fields do not contain valid data. The first 4 data bytes of the message contain the Error Code. The MSB of the Error Code is in data byte 0, the LSB is in data byte 3. If a status message was read the return value of CAN_ReadFD is also the error code.
Examples:
Data0 |
Data1 |
Data2 |
Data3 |
Error |
Error Code |
Description |
00h |
00h |
00h |
02h |
PCAN_ERROR_OVERRUN |
0002h |
CAN controller has been read out too late. |
00h |
00h |
00h |
08h |
PCAN_ERROR_BUSWARNING |
0008h |
Bus error: An error counter reached the 'warning' limit. |
00h |
04h |
00h |
00h |
PCAN_ERROR_BUSPASSIVE |
40000h |
Bus error: the CAN controller is error passive. |
00h |
00h |
00h |
10h |
PCAN_ERROR_BUSOFF |
0010h |
Bus error: CAN Controller is in 'Bus Off' state. |
The following example shows the use of CAN_ReadFD on the channel PCAN_USBBUS1. In case of failure, the returned code will be translated to a text (according with the operating system language) in English, German, Italian, French or Spanish, and it will be shown to the user.
Note: It is assumed that the channel was already initialized using CAN_InitializeFD and that the following code is an OnTimer event handler function.
C++:
TPCANMsgFD msg; TPCANTimestampFD timestamp; TPCANStatus result; char strMsg[256]; do { // Check the receive queue for new messages // result = CAN_ReadFD(PCAN_USBBUS1,&msg,×tamp); if(result != PCAN_ERROR_QRCVEMPTY) { // Process the received message // MessageBox("A message was received"); ProcessMessage(msg) } else { // An error occurred, get a text describing the error and show it // and handle the error // CAN_GetErrorText(result, 0, strMsg); MessageBox(strMsg); // Here can be decided if the loop has to be terminated (eg. the bus // status is bus-off) // HandleReadError(result); } // Try to read a message from the receive queue of the PCAN-USB, Channel 1, // until the queue is empty // }while((result & PCAN_ERROR_QRCVEMPTY) != PCAN_ERROR_QRCVEMPTY);
Copyright © 2017. PEAK-System Technik GmbH. All rights reserved.
|
Send feedback to this documentation
|