VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Types and structuresThe information of a LIN message can be accessed bitwise with the element Bits.The following bit fields are defined:• Bits.pid:[in/out] Protected identifier of the message.• Bits.type:[in/out] Type of message. The types listed in the following are defined for receivemessages. For transmit messages, only the message typesLIN_MSGTYPE_DATA and LIN_MSGTYPE_WAKEUP are currently defined, othervalues are not allowed hereLIN_MSGTYPE_DATA:Normal message. All regular receive messages are of this type. The field LINMSG.bPid containsthe ID of the message, the field LINMSG.dwTime the receive time. The fieldLINMSG.abData contains, depending on the length (see Bits.dlen), the data bytes of themessage. In master mode, messages of this type can also be transmitted. The ID must beentered in the field LINMSG.bPid and in the field LINMSG.abData, depending on the length(Bits.dlen), the data to be transmitted. The field LINMSG.dwTime is set to 0. To transmit onlythe ID without data, Bits.ido is set to 1.LIN_MSGTYPE_INFO:Information message. This message type is entered in the receive buffer of all activated messagemonitors for certain events or in the event of changes in the status of the controller.The field LINMSG.bPid of the message always has the value 0xFF. The fieldLINMSG.abData[0] contains one of the following values:ConstantLIN_INFO_STARTLIN_INFO_STOPLIN_INFO_RESETMeaningThe controller was started. The field LINMSG.dwTimecontains the relative start time (normally 0).The controller was stopped. The field LINMSG.dwTimecontains the value 0.The controller was reset. The field LINMSG.dwTime containsthe value 0.104Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Types and structuresLIN_MSGTYPE_ERROR:Error message. This message type is entered in the receive buffer of all activated messagemonitors when bus errors occur, as far as the flag LIN_OPMODE_ERRORS was defined at initializationof the controller. The field LINMSG.bPid of the message always has the value0xFF. The time of the event is recorded in the field LINMSG.dwTime of the message. Thefield LINMSG.abData[0] contains one of the following values:ConstantMeaningLIN_ERROR_BIT Bit errorLIN_ERROR_CHKSUM Checksum errorLIN_ERROR_PARITY Parity error of the identifierLIN_ERROR_SLNORE “Slave” does not respondLIN_ERROR_SYNC Invalid synchronization fieldLIN_ERROR_NOBUS No bus activityLIN_ERROR_OTHER Other, unspecified errorThe field LINMSG.abData[1] of the message contains the low value byte of the current status(see also LINLINESTATUS.dwStatus). The content of the other data fields is undefined.LIN_MSGTYPE_STATUS:Status message. This message type is entered in the receive buffer of all activated messagechannels at changes in the controller status. The field LINMSG.bPid of the message alwayshas the value 0xFF. The time of the event is recorded in the field LINMSG.dwTime of themessage. The field LINMSG.abData[0] contains the low value byte of the current status (seealso LINLINESTATUS.dwStatus). The content of the other data fields is undefined.LIN_MSGTYPE_WAKEUP:Only for transmit messages. Messages of this type generate a wake-up signal on the bus.The fields LINMSG.dwTime, LINMSG.bPid and LINMSG.bDlen have no significance.LIN_MSGTYPE_TMOVR:Counter overrun. Messages of this type are generated in the event of an overrun of the 32bit time stamp of LIN messages. The field LINMSG.dwTime of the message contains thetime of the event (normally 0) and in the field LINMSG.bDlen the number of timer overruns.The content of the data fields LINMSG.abData is undefined, the field LINMSG.bPid alwayshas the value 0xFF.LIN_MSGTYPE_SLEEP:Goto Sleep message. The fields LINMSG.dwTime, LINMSG.bPid and LINMSG.bDlen have nosignificance.• Bits.dlen:[in/out] Number of valid data bytes in the field LINMSG.abData of the message.• Bits.ecs:[in/out] Enhanced checksum. The bit is set to 1 if it is a message with extendedchecksum in accordance with LIN 2.0.• Bits.sor:[out] Sender of response. The bit is set with messages which the LIN controlleritself has transmitted, i.e. with messages for which the controller has an entryin the response table.105Copyright 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 100 and 101: Types and structures5.2.7 CANCYCLIC
Page 102 and 103: Types and structures• dwClockFreq
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?