VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Accessing the bus3.1.2.1 Controller statesThe following diagram shows the various states of a controller.canControlOpencanControlResetundefinedcanControlInitializecanControlDetectRateofflinecanControlInitializecanControlStart(...,TRUE)canControlStart(...,FALSE)onlineFig. 3-2: Controller statesAfter opening the control unit, the controller is normally in a non-initialized state.This state is exited by calling one of the functions canControlInitialize or canControlDetectBitrate.The CAN controller is then in “offline” state.If the function canControlInitialize returns an “access denied“ error code, theCAN controller is already used by another application.With canControlInitialize, the operating mode and bitrate of the CAN controllerare set. The values for the bus timing register in the parameters bBtr0 and bBtr1correspond to the values of the registers BTR0 and BTR1 of the Philips SJA 1000CAN controller with a cycle frequency of 16 MHz.More detailed information on setting the bitrate is given in the data sheet for SJA1000 in section 6.5. A summary of the bus timing values with all CiA- or CANopen-compliantbitrates is given in the following table.16Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Accessing the busBitrate (kbit) Pre-defined constants for BTR0, BTR1 BTR0 BTR110 CAN_BT0_10KB, CAN_BT1_10KB 0x31 0x1C20 CAN_BT0_20KB, CAN_BT1_20KB 0x18 0x1C50 CAN_BT0_50KB, CAN_BT1_50KB 0x09 0x1C100 CAN_BT0_100KB, CAN_BT1_100KB 0x04 0x1C125 CAN_BT0_125KB, CAN_BT1_125KB 0x03 0x1C250 CAN_BT0_250KB, CAN_BT1_250KB 0x01 0x1C500 CAN_BT0_500KB, CAN_BT1_500KB 0x00 0x1C800 CAN_BT0_800KB, CAN_BT1_800KB 0x00 0x161000 CAN_BT0_1000KB, CAN_BT1_1000KB 0x00 0x14If the CAN connection is connected to a running system whose bitrate is unknown,the current bitrate can be determined with the function canControlDetectBitrate.The bus timing values determined by the function can then be appliedinto the function canControlInitialize.The CAN controller is started or stopped by calling the function canControlStart.When the function is successfully called with the value TRUE in the parameterfStart, the controller is in “online” state. In this state the CAN controller is activelyconnected to the bus. Incoming CAN messages are forwarded to all active messagechannels, or transmit messages are output to the bus by the message channels.Calling the function canControlStart with the value FALSE in the parameter fStartswitches the CAN controller to “offline” mode. The message transfer is interruptedand the controller disabled.The function canControlReset switches the CAN controller to “not initialized” status.In addition, the function resets the controller hardware and the set messagefilters. Please note that resetting the controller hardware leads to false messagetelegrams on the bus if a transmit process is aborted in the middle of transmissionwhen a function is called.17Copyright 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 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

Create successful ePaper yourself

Delete template?

Save as template?