VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

System overviewThe VCI server running in the kernel of the operating system mainly handles managementof the VCI device drivers, controls access to the CAN interface boardsand provides mechanisms for the exchange of data between the application leveland the operating system level.The programming interface shown below consists of the following subcomponentsand functions.Native VCI programming interfaces (VCINPL.DLL)Device management anddevice accessCAN control CAN message channels Cyclic CAN transmit listvciEnumDeviceOpen canControlOpen canChannelOpen canSchedulerOpenvciEnumDeviceClose canControlClose canChannelClose canSchedulerClosevciEnumDeviceNext canControlGetCaps canChannelGetCaps canSchedulerGetCapsvciEnumDeviceReset canControlGetStatus canChannelGetStatus canSchedulerGetStatusvciEnumDeviceWaitEvent canControlDetectBitrate canChannelInitializecanSchedulerActivatevciFindDeviceByHwid canControlInitialize canChannelActivate canSchedulerResetvciFindDeviceByClass canControlReset canChannelPeekMessage canSchedulerAddMessagevciSelectDeviceDlg canControlStart canChannelPostMessage canSchedulerRemMessagevciDeviceOpen canControlSetAccFilter canChannelWaitRxEvent canSchedulerStartMessagevciDeviceOpenDlg canControlAddFilterIds canChannelWaitTxEvent canSchedulerStopMessagevciDeviceClose canControlRemFilterIds canChannelReadMessagevciDeviceGetInfovciDeviceGetCapscanChannelSendMessageLIN controlLIN message channelslinControlOpen linMonitorOpenlinControlClose linMonitorCloselinControlGetCaps linMonitorGetCapslinControlGetStatus linMonitorInitializelinControlInitialize linMonitorActivatelinControlReset linMonitorPeekMessagelinControlStart linMonitorWaitRxEventlinControlWriteMessage linMonitorReadMessage8Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Device management and device access2 Device management and device access2.1 OverviewThe device management of VCI enables listing and primary access to the CAN interfaceboards logged into the VCI server. The functions shown in the followingdiagram are available:vciEnumDeviceClosecloses the device listvciEnumDeviceNextprovides the next entryof the listvciEnumDeviceWaitEventwaits on the changesof the listresets the list indexvciEnumDeviceResetvciEnumDeviceOpenopens the device listDevice listopens a device of the listvciDeviceOpen,vciDeviceOpenDlgvciFindDeviceByHwidvciFindDeviceByClassvciSelectDeviceDlgsearches for deviceswith a certain propertiesdisplays a dialogfor device selectionPC/I04-PCIUSB-to-CANcloses a opened devicedetermines informationsof a opend devicevciDeviceClosevciDeviceGetInfovciDeviceGetCapsUser ModeThe change of the listeKernel ModeVCI Serverlog into the serverlog out from the serverPC-I04-PCIUSB-to-CANFig. 2-1: Components and functions of the device managementThe VCI server manages all CAN interface boards in a system-wide global list,which is referred to in the following as device list.A CAN interface board logs into the server automatically when the computer isbooted or when a connection is established between the computer and the CANinterface board. If a CAN interface board is no longer available, for example becausethe connection was interrupted, it is automatically removed from the devicelist.9Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
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 84 and 85:
Page 86 and 87:
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 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?