VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Types and structuresCAN_MSGTYPE_STATUS:Status message. This message type is entered in the receive buffers of all activated messagechannels when the controller status changes. The field CANMSG.dwMsgId of the messagealways has the value 0xFFFFFFFF. The time of the event is marked in the field dwTime of themessage. The field CANMSG.abData[0] contains the least significant byte of the currentCAN status (see also CANLINESTATUS.dwStatus). The contents of the other data fields areundefined.CAN_MSGTYPE_WAKEUP:Not currently used, or reserved for future extensions.CAN_MSGTYPE_TIMEOVR:Timer overrun. Messages of this type are generated when an overrun of the 32-bit timestamp of CAN messages occurs. The time of the event (normally 0) is given in the fieldCANMSG.dwTime of the message and the number of timer overruns after the last timeroverrun message in the field CANMSG.dwMsgId. The contents of the data fields abData areundefined.CAN_MSGTYPE_TIMERST:Not currently used, or reserved for future extensions• Bits.res:Reserved for future extension. For reasons of compatibility, the field should alwaysbe set to 0.• Bits.dlc:[in/out] Data length code. Defines the number of valid data bytes in the fieldsCANMSG.abData of the message.• Bits.ovr:[out] Data overrun. The bit is set to 1 if the receive buffer is full after this messageis entered.• Bits.srr:[in/out] Self reception request. If the bit is set for transmit messages, the messageis entered in the receive buffer as soon as it has been transmitted on thebus. With receive messages, a set bit indicates that it is a received self- receptionmessage.• Bits.rtr:[in/out] Remote transmission request.• Bits.ext:[in/out] Message with extended 29-bit ID.• Bits.afc:[out] Acceptance filter code. With receive messages, this field specifies the filterthat let the message through.98Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Types and structures5.2.6 CANMSGThe data type describes the structure of a CAN message telegram.typedef struct{UINT32 dwTime;UINT32 dwMsgId;CANMSGINFO uMsgInfo;UINT8 abData[8];} CANMSG, *PCANMSG;• dwTime:[in/out] With receive messages, this field contains the relative reception time ofthe message in ticks. The resolution of a tick can be calculated from the fieldsdwClockFreq and dwTscDivisor of the structure CANCAPABILITIES in accordancewith the following formula:Resolution [s] = dwTscDivisor / dwClockFreqAn overrun of the 32-Bit dwTime value is received with a Timer Overrun messages( CAN_MSGTYPE_TIMEOVR $5.2.5)With transmit messages, the field defines with how many ticks delay the messageis to be transmitted to the bus. The delay time between the last messagetransmitted and the new message can be calculated with the fields dwClock-Freq and dwDtxDivisor of the structure CANCAPABILITIES in accordance withthe following formula.delay time [s] = (dwDtxDivisor / dwClockFreq) * dwTimeThe maximum possible delay time is defined by the field dwDtxMaxTicks of thestructure CANCAPABILITIES.• dwMsgId:[in/out] CAN ID of the message in Intel format (right-aligned) without RTR bit.• uMsgInfo:[in/out] Bit field with information on the message type. A description of the bitfield is given in section 5.2.5.• abData:[in/out] Array for up to 8 data bytes. The number of valid data bytes is definedby the field uMsgInfo.Bits.dlc.99Copyright 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 96 and 97: Types and structures5.2.5 CANMSGINF
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?