VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Interface description4.4.2.1 linMonitorOpenThe function creates a message monitor for the LIN connection of a device or ofan interface board. The complete syntax of the function is:HRESULT linMonitorOpen (HANDLE hDevice,UINT32 dwLinNo,BOOL fExclusive,PHANDLE phLinMon );Parameter:hDevice[in] Handle of the opened device or of the interface board.dwLinNo[in] Number of the LIN connection of the control unit to be opened. Thevalue 0 selects the first LIN connection, the value 1 the second LINconnection and so on.fExclusive[in] Determines whether the LIN connection is used exclusively for themonitor to be generated. If the value TRUE is entered here, no furthermonitors can be created after a successful call of the function until thegenerated monitor has been released again. With the value FALSE, anynumber of message monitors can be created for the LIN connection.phLinMon[out] Pointer to a variable of type HANDLE. If run successfully, the functionreturns the handle of the opened monitor in this variable. In the event of anerror, the variable is set to the value NULL.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.If the value TRUE is entered in the parameter fExclusive, no further messagemonitors can be opened after a successful call of the function. This means thatthe first program to call the function with the value TRUE in the parameterfExclusive has exclusive control over the message reception of the LIN connection.Comments:If the parameter dwLinNo is set to the value 0xFFFFFFFF, the function displaysa dialogue window on the screen to select a device or an interface board anda LIN connection. In this case the function expects the handle of a higher orderwindow or the value NULL if no higher order window is available and notthe handle of the device in the parameter hDevice.If the message monitor is no longer required, the handle returned in phLin-Mon should be released again with the function linMonitorClose.82Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Interface description4.4.2.2 linMonitorCloseThe function closes an opened message monitor for the LIN connection. Thecomplete syntax of the function is:HRESULT linMonitorClose ( HANDLE hLinMon );Parameter:hLinMon[in] Handle of the message monitor to be closed. The handle used heremust come from a call of the function linMonitorOpen.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:When the function was called, the handle specified in hLinMon is no longer validand may no longer be used.4.4.2.3 linMonitorGetCapsThe function determines the properties of the LIN connection of the specifiedmessage monitor. The complete syntax of the function is:HRESULT linMonitorGetCaps (HANDLEhLinMon,PLINCAPABILITIES pLinCaps );Parameter:hLinMon[in] Handle of the opened LIN message monitor.pLinCaps[out] Pointer to a structure of type LINCAPABILITIES. If run successfully, thefunction saves the properties of the LIN connection in the memory areadefined 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 LINCAPABILITIES in section 5.3.1.83Copyright 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 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 84 and 85: Interface description4.4.2.4 linMon
Page 86 and 87: Interface description4.4.2.7 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?