VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Interface description4.3.2 Message channelThe interfaces provides functions to configure message channels between theapplication and the CAN bus . General information on the message channels isgiven in section 3.1.3.4.3.2.1 canChannelOpenThe function opens or creates a message channel for a CAN connection of a CANinterface board. The complete syntax of the function is:HRESULT canChannelOpen (HANDLE hDevice,UINT32 dwCanNo,BOOL fExclusive,PHANDLE phChannel );Parameters:hDevice[in] Handle of the CAN interface board.dwCanNo[in] Number of the CAN connection for which a message channel is to beopened. The value 0 selects the first connection, the value 1 the secondconnection and so on.fExclusive[in] Defines whether the connection is used exclusively for the channel to beopened. If the value TRUE is specified here, the CAN connection is usedexclusively for the new message channel. With the value FALSE, more thanone message channel can be opened for the CAN connection.phChannel[out] Pointer to a variable of type HANDLE. If run successfully, the functionreturns the handle of the opened CAN message channel in this variable. Inthe event of an of an error, the variable is set to ZERO.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 vciFormatError.Comments:If the value TRUE is specified in the parameter fExclusive, no more messagechannels can be opened after a successful call of the function. This means thatthe program that first calls the function with the value TRUE in the parameterfExclusive has exclusive control over the message flow on the CAN connection.60Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Interface descriptionIf the value 0xFFFFFFFF is specified in the parameter dwCanNo, the functiondisplays a dialog window to select a CAN interface board and a CAN connectionon the screen. In this case the function does not expect the handle of theCAN interface board in the parameter hDevice, but the handle of a higher orderwindow, or the value ZERO if no higher order window is available.If the message channel is no longer required, the handle returned in phChannelshould be released again with the function canChannelClose.4.3.2.2 canChannelCloseThe function closes an opened message channel. The complete syntax of thefunction is:HRESULT canChannelClose( HANDLE hChannel )Parameter:hChannel[in] Handle of the message channel to be closed. The handle specified heremust come from a call of the function canChannelOpen .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 vciFormatError.Comments:After the function is called, the handle specified in hChannel is no longer validand must no longer be used.4.3.2.3 canChannelGetCapsThe function determines the features of a CAN connection. The complete syntaxof the function is:HRESULT canChannelGetCaps (HANDLEhChannel,PCANCAPABILITIES pCaps );Parameters:hChannel[in] Handle of the opened message channel.61Copyright 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 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 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

Create successful ePaper yourself

Delete template?

Save as template?