VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Types and structures5.2.7 CANCYCLICTXMSGThe data type describes the structure of a cyclic CAN transmit message.typedef struct{UINT16 wCycleTime;UINT8 bIncrMode;UINT8 bByteIndex;UINT32 dwMsgId;CANMSGINFO uMsgInfo;UINT8 abData[8];} CANCYCLICTXMSG, *P CANCYCLICTXMSG;wCycleTime:[in/out] Cycle time of the transmit message in ticks. The cycle time can be calculatedwith the fields dwClockFreq and dwCmsDivisor of the structure CAN-CAPABILITIES in accordance with the following formula.cycle time [s] = (dwCmsDivisor / dwClockFreq) * wCycleTimeThe maximum possible cycle time is restricted to the value in the fielddwCmsMaxTicks of the structure CANCAPABILITIES.• bIncrMode:[in/out] This field defines whether part of the cyclic transmit message is automaticallyincremented after every transmit process.CAN_CTXMSG_INC_NO:No automatic increment of a message field occurs.CAN_CTXMSG_INC_ID:Increments the field dwMsgId of the message after every transmit process by 1. If the fieldreaches the value 2048 (11-bit ID) or 536.870.912 (29-bit ID), there is an automatic overrunto 0.CAN_CTXMSG_INC_8:Increments an 8-bit value in the data field abData of the message. The data field to be incrementedis defined in the field bByteIndex. If the maximum value 255 is exceeded, there isan automatic overrun to 0.CAN_CTXMSG_INC_16:Increments a 16-bit value in the data field abData of the message. The least significant byteof the 16-bit value to be incremented is defined in the field bByteIndex. The most significantbyte is in abData[bByteIndex+1]. If the maximum value 65535 is exceeded, there is an automaticoverrun to 0.100Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Types and structures• bByteIndex:[in/out] If the value CAN_CTXMSG_INC_8 is specified in the field bIncrMode,this field defines the index of the data byte in the data field abMsgData that isto be automatically incremented after every transmit process. If the valueCAN_CTXMSG_INC_16 is specified for bIncrMode, this field defines the indexof the least significant byte (LSB) of the 16-bit value in the data field abMsgData.The most significant byte (MSB) of the 16-bit value is in the data fieldabMsgData[bByteIndex+1].• dwMsgId:[in/out] ID of the message (CAN-ID) in Intel format (right-aligned) without RTRbit.• 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.5.3 LIN-specific data typesThe declarations of all LIN-specific data types and constants are found in the file.5.3.1 LINCAPABILITIESThe data type describes the properties of a LIN connection. The structure is as follows:typedef struct _LINCAPABILITIES{UINT16 dwFeatures;UINT32 dwClockFreq;UINT32 dwTscDivisor;} LINCAPABILITIES, *PLINCAPABILITIES;• dwFeatures:[out] Supported properties. The value is a combination of one or more of thefollowing constants:LIN_FEATURE_MASTER:The LIN controller supports the “master” mode.LIN_FEATURE_AUTORATE:The LIN controller supports automatic bitrate detection.LIN_FEATURE_ERRFRAME:The LIN controller supplies error messages.LIN_FEATURE_BUSLOAD:The LIN controller supports calculation of the bus load.101Copyright 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 98 and 99: Types and structuresCAN_MSGTYPE_STA
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?