VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Interface descriptionpCaps[out] Pointer to a structure of type CANCAPABILITIES. If run successfully, thefunction saves the features of the CAN connection in the memory areaspecified here.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:Further information on the data provided by the function is given in the descriptionof the data structure CANCAPABILITIES in section 5.2.1.4.3.2.4 canChannelGetStatusThe function determines the current status of a message channel as well as thecurrent settings and the current status of the controller that is connected to thechannel. The complete syntax of the function is:HRESULT canChannelGetStatus (HANDLEhChannel,PCANCHANSTATUS pStatus );Parameters:hChannel[in] Handle of the opened message channel.pStatus[out] Pointer to a structure of type CANCHANSTATUS. If run successfully,the function saves the current status of the channel and controller in thememory area specified here.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:Further information on the data provided by the function is given in the descriptionof the data structure CANCHANSTATUS in section 5.2.3.62Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Interface description4.3.2.5 canChannelInitializeThe function initializes the receive and transmit buffers of a message channel. Thecomplete syntax of the function is:HRESULT canChannelInitialize (HANDLE hChannel,UINT16 wRxFifoSize,UINT16 wRxThreshold,UINT16 wTxFifoSize,UINT16 wTxThreshold );Parameters:hChannel[in] Handle of the opened message channel.wRxFifoSize[in] Size of the receive buffer in number of CAN messages.wRxThreshold[in] Threshold value for the receive event. The event is triggered when thenumber of messages in the receive buffer reaches or exceeds the numberspecified here.wTxFifoSize[in] Size of the transmit buffer in number of CAN messages.wTxThreshold[in] Threshold value for the transmit event. The event is triggered when thenumber of free entries in the transmit buffer reaches or exceeds the numberspecified here.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.A value greater than 0 must be specified for the size of the receive and of thetransmit buffer, otherwise the function returns an error code according to“Invalid parameter“.Comments:The values specified in the parameters wRxFifoSize and wTxFifoSize define thelower limit for the size of the buffers. The actual size of a buffer may be largerthan the specified value, as the memory used for this is reserved page-wise.If the function is called for an already initialized channel, the function firstdeactivates the channel, then releases the available FIFOs and creates two newFIFOs with the required dimensions.63Copyright 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 60 and 61: Interface description4.3.2 Message
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?