VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Interface description4.3.2.11 canChannelReadMessageThe function reads the next CAN message from the receive buffer of a messagechannel. The complete syntax of the function is:HRESULT canChannelReadMessage(HANDLE hChannel,UINT32 dwMsTimeout,PCANMSG pCanMsg );Parameters:hChannel[in] Handle of the opened message channel.dwMsTimeoutMaximum waiting time in milliseconds. The function returns to the callerwith the error code VCI_E_TIMEOUT if no message was read or receivedwithin the specified time. With the value INFINITE (0xFFFFFFFF), the functionwaits until a message has been read.pCanMsg[out] Pointer to a structure of type CANMSG. If run successfully, thefunction saves the read CAN message in the memory area specified here.Return value:If run successfully, the function returns the value VCI_OK. If the time periodspecified in the parameter dwMsTimeout has elapsed without a messagehaving been received, the function returns the error code VCI_E_TIMEOUT. Inthe event of an error, the function returns an error code not equal to VCI_OKor VCI_E_TIMEOUT. Further information on the error code is provided by thefunction vciFormatError.If the value ZERO is specified in the parameter pCanMsg, the function removesthe next CAN message from the receive buffer.Comments:If the handle specified in hChannel is closed from another thread, the functionends the current function control and returns with a return value not equal toVCI_OK.68Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Interface description4.3.2.12 canChannelSendMessageThe function waits until a message channel is ready to receive a message andthen writes the specified CAN message in the transmit buffer of the messagechannel. The complete syntax of the function is:HRESULT canChannelSendMessage (HANDLE hChannel,UINT32 dwMsTimeout,PCANMSG pCanMsg );Parameters:hChannel[in] Handle of the opened message channel.dwMsTimeoutMaximum waiting time in milliseconds. The function returns to the callerwith the error code VCI_E_TIMEOUT if the message could not be entered inthe transmit buffer within the specified time. With the value INFINITE(0xFFFFFFFF), the function waits until the transmit event occurs and themessagehas been written in the transmit buffer.pCanMsg[in] Pointer to an initialized structure of type CANMSG with the CANmessage to be transmitted.Return value:If run successfully, the function returns the value VCI_OK,. If the time periodspecified in the parameter dwMsTimeout has elapsed without the messagehaving been written in the transmit buffer, the function returns the error codeVCI_E_TIMEOUT. In the event of an error, the function returns an error codenot equal to VCI_OK or VCI_E_TIMEOUT. Further information on the errorcode is provided by the function vciFormatError.The function only waits until the message has been written in the transmitbuffer, but not until the message has been transmitted on the bus.Comments:If the handle specified in hChannel is closed from another thread, the functionends the current function control and returns with a return value not equal toVCI_OK.69Copyright 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 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 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?