VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Types and structures• dwStatus:[out] Current status of the CAN controller. The value is a combination of one ormore of the following constants:CAN_STATUS_TXPEND:The CAN controller is currently sending a message to the bus.CAN_STATUS_OVRRUN:A data overrun in the receive buffer of the CAN controller has taken place. This status canonly be reseted through a CAN controller reset ( see §4.3.1.7).CAN_STATUS_ERRLIM:An overrun of an error counter of the CAN controller has taken place.CAN_STATUS_BUSOFF:The CAN controller has changed to the “BUS-OFF” status.CAN_STATUS_ININIT:The CAN controller is in the stopped status.5.2.3 CANCHANSTATUSThe data type describes the current status of a CAN message channel. The structureis as follows:typedef struct{CANLINESTATUS sLineStatus;BOOL32fActivated;BOOL32fRxOverrun;UINT8bRxFifoLoad;UINT8bTxFifoLoad;} CANCHANSTATUS, *PCANCHANSTATUS;• sLineStatus:[out] Current status of the CAN controller. Further information is given in thedescription of the data structure CANLINESTATUS.• fActivated:[out] Indicates whether the message channel is currently active (TRUE) or inactive(FALSE).• fRxOverrun:[out] Indicates with the value TRUE whether an overrun of the receive buffer ofthe CAN controller has taken place. (see §5.2.2 CAN_STATUS_OVRRUN).• bRxFifoLoad:[out] Current level of the receive buffer in per cent.• bTxFifoLoad:• [out] Current level of the transmit buffer in per cent.94Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Types and structures5.2.4 CANSCHEDULERSTATUSThe data type describes the current status of a cyclic transmit list. The structure isas follows:typedef struct{UINT8 bTaskStat;UINT8 abMsgStat[16];} CANSCHEDULERSTATUS, *PCANSCHEDULERSTATUS;• bTaskStat:[out] Current status of the transmit task.CAN_CTXTSK_STAT_STOPPED:The transmit task is currently stopped, or deactivated.CAN_CTXTSK_STAT_RUNNING:The transmit task is running, or is active.• abMsgStat:Table with the status of all 16 transmit objects. Each table entry can have oneof the following values:CAN_CTXMSG_STAT_EMPTY:The entry is not allocated a transmit object, or the entry is not currently being used.CAN_CTXMSG_STAT_BUSY:The transmit object is currently being used.CAN_CTXMSG_STAT_DONE:Processing of the transmit object is completed.95Copyright 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 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 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?