VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Types and structures5.2.5 CANMSGINFOThe data type summarizes various information on CAN messages in a 32-bit value.The value can be addressed either byte-wise or via individual bit fields.typedef union{struct{UINT8 bType;UINT8 bReserved;UINT8 bFlags;UINT8 bAccept;} Bytes;struct{UINT32 type: 8;UINT32 res : 8;UINT32 dlc : 4;UINT32 ovr : 1;UINT32 srr : 1;UINT32 rtr : 1;UINT32 ext : 1;UINT32 afc : 8;} Bits;} CANMSGINFO, *PCANMSGINFO;The information of a CAN message can be addressed byte-wise via the elementBytes. The following fields are defined for this:• Bytes.bType:[in/out] Type of the message. See also Bits.type.• Bytes.bReserved:Reserved. See also Bits.res.• Bytes.bFlags[in/out] Various flags. See also Bits.dlc, Bits.ovr, Bits.srr, Bits.rtr and Bits.ext.• Bytes.bAccept:[out] With receive messages displays which filter has accepted the message.See also Bits.afc.The information of a CAN message can be accessed bit-wise with the elementBits. The following bit fields are defined:• Bits.type:[in/out] Type of the message. The types listed in the following are defined forreceive messages. For transmit messages, only the message typeCAN_MSGTYPE_DATA is currently defined. Other values are not permittedhere.96Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Types and structuresCAN_MSGTYPE_DATA:Normal message. All regular receive messages are of this type. The field CANMSG.dwMsgIdcontains the ID of the message, the field CANMSG.dwTime the time of reception. The fieldsCANMSG.abData contain according to length (see Bits.dlc) the data bytes of the message.With transmit messages the IDs are to be entered in the field CANMSG.dwMsgId and thedata bytes according to length in the fields CANMSG.abData. The field CANMSG.dwTime isnormally set to 0, unless the message is to be transmitted with a delay. In this case the delaytime is to be specified in ticks. See also the description of the structure CANMSG, or section3.1.3.3.CAN_MSGTYPE_INFO:Information message. This message type is entered in the receive buffers of all activatedmessage channels with certain events or with changes to the status of the controller. Thefield CANMSG.dwMsgId of the message always has the value 0xFFFFFFFF. The field abCANMSG.Data[0] contains one of the following values:Constant MeaningCAN_INFO_START The CAN controller was started. The fieldCANMSG.dwTime contains the relative start time (normally0).CAN_INFO_STOP The CAN controller was stopped. The fieldCANMSG.dwTime contains the value 0.CAN_INFO_RESET The CAN controller was reset. The field CANMSG.dwTimecontains the value 0.CAN_MSGTYPE_ERROR:Error message. This message type is entered in the receive buffers of all activated messagechannels when bus errors occur if the flag CAN_OPMODE_ERRFRAME was specified in theparameter CANMSG.bMode when the function canControlInitialize was called. The fieldCANMSG.dwMsgId of the message always has the value 0xFFFFFFFF. The time of the eventis marked in the field CANMSG.dwTime of the message. The field abData[0] contains one ofthe following values:ConstantMeaningCAN_ERROR_STUFF Bit stuff errorCAN_ERROR_FORM Format errorCAN_ERROR_ACK Acknowledge errorCAN_ERROR_BIT Bit errorCAN_ERROR_CRC CRC errorCAN_ERROR_OTHER Other unspecified errorThe field CANMSG.abData[1] of the message contains the least significant byte of the currentCAN status (see also CANLINESTATUS.dwStatus). The contents of the other data fieldsare undefined.97Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Page 8 and 9:
System overviewThe VCI server runni
Page 10 and 11:
Device management and device access
Page 12 and 13:
Device management and device access
Page 14 and 15:
Accessing the bus3 Accessing the bu
Page 16 and 17:
Accessing the bus3.1.2.1 Controller
Page 18 and 19:
Accessing the bus3.1.2.2 Message fi
Page 20 and 21:
Accessing the busAs the example sho
Page 22 and 23:
Accessing the busAfter a message ch
Page 24 and 25:
Accessing the busHRESULT hResult;HA
Page 26 and 27:
Accessing the bust zTransmit object
Page 28 and 29:
Accessing the busNormally, the tran
Page 30 and 31:
Accessing the bus3.2.2.1 Controller
Page 32 and 33:
Accessing the busIf the connection
Page 34 and 35:
Accessing the busAfter a message mo
Page 36 and 37:
Interface description4 Interface de
Page 38 and 39:
Interface descriptionReturn value:I
Page 40 and 41:
Interface descriptionpszGuid[out] P
Page 42 and 43:
Interface description4.2.1.2 vciEnu
Page 44 and 45:
Interface descriptionComments:The c
Page 46 and 47: Interface descriptionpVciidDevice[o
Page 48 and 49: Interface descriptionComments:After
Page 50 and 51: Interface descriptionphControl[out]
Page 52 and 53: Interface descriptionReturn value:I
Page 54 and 55: Interface description4.3.1.6 canCon
Page 56 and 57: Interface description4.3.1.8 canCon
Page 58 and 59: Interface description4.3.1.10 canCo
Page 60 and 61: Interface description4.3.2 Message
Page 62 and 63: Interface descriptionpCaps[out] Poi
Page 64 and 65: Interface description4.3.2.6 canCha
Page 66 and 67: Interface description4.3.2.9 canCha
Page 68 and 69: Interface description4.3.2.11 canCh
Page 70 and 71: Interface description4.3.3 Cyclic t
Page 72 and 73: Interface description4.3.3.4 canSch
Page 74 and 75: Interface description4.3.3.7 canSch
Page 76 and 77: Interface description4.3.3.10 canSc
Page 78 and 79: Interface description4.4.1.3 linCon
Page 80 and 81: Interface description4.4.1.6 linCon
Page 82 and 83: Interface description4.4.2.1 linMon
Page 88 and 89: Interface descriptionReturn value:I
Page 90 and 91: Types and structures• VciObjectId
Page 92 and 93: Types and structures• wBusCouplin
Page 94 and 95: Types and structures• dwStatus:[o
Page 98 and 99: Types and structuresCAN_MSGTYPE_STA
Page 100 and 101: Types and structures5.2.7 CANCYCLIC
Page 102 and 103: Types and structures• dwClockFreq
Page 104 and 105: Types and structuresThe information
Page 106: Types and structures• Bits.ovr:[o
show all

VCI - Virtual CAN Interface - Ixxat

Create successful ePaper yourself

Delete template?

Save as template?