VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Interface description4.3.1.6 canControlInitializeThe function sets the operating mode and bitrate of a CAN connection. Thecomplete syntax of the function is:HRESULT canControlInitialize (HANDLE hControl,UINT8 bMode,UINT8 bBtr0,UINT8 bBtr1 );Parameters:hControl[in] Handle of the opened CAN controller.bMode[in] Operating mode of the CAN controller. For the operating mode, acombination of the following constants can be specified:CAN_OPMODE_STANDARD:Accepts CAN messages with 11-bit identifiers.CAN_OPMODE_EXTENDED:Accepts CAN messages with 29-bit identifiers.CAN_OPMODE_LISTONLY:CAN controller is operated in “List only“ mode.CAN_OPMODE_ERRFRAME:Errors are indicated to the application via special CAN messages.CAN_OPMODE_LOWSPEED:CAN controller uses low speed coupling.bBtr1[in] Value for the bus timing register 0 of the CAN controller. The valuecorresponds to the BTR0 register of the Philips SJA 1000 CAN controllerwith a cycle frequency of 16 MHz.bBtr1[in] Value for the bus timing register 1 of the CAN controller. The valuecorresponds to the BTR1 register of the Philips SJA 1000 CAN controllerwith a cycle frequency of 16 MHz.Return value:If run successfully, the function returns the value VCI_OK, otherwise an errorcode not equal to VCI_OK. Further information on the error code is providedby the function.The function resets the controller hardware internally according to the functionComments:canControlReset and then initializes the controller with the specified parameters.The function can be called from every controller status.54Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Interface descriptionFurther information on the bus timing values in the parameters bBtr0 andbBtr1 is given in the datasheet of the Philips SJA 1000 CAN controller.The following table shows the bus timing values for all bitrates specified bythe CiA or CANopen.Bitrate (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 0x144.3.1.7 canControlResetThe function resets the controller hardware and the set message filters of a CANconnection. The complete syntax of the function is:HRESULT canControlReset ( HANDLE hControl );Parameter:hControl[in] Handle of the opened CAN controller.Return value:If run successfully, the function returns the value VCI_OK, otherwise an errorcode not equal to VCI_OK. Further information on the error code is providedby the function.The function resets the controller hardware, removes the set acceptance filter,deletes the contents of the filter lists and switches the controller “not initialized”.At the same time, the message flow between the controller and themessage channels connected to it is interrupted.Comments:When the function is called, a currently active transmit process of the controlleris aborted. This may lead to transmission errors or to a faulty message telegramon the bus.Further information is given in section 3.1.2.55Copyright 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 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 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?