VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Interface description4.3.3 Cyclic transmit listWith the transmit list, up to 16 different CAN message objects can be transmittedcyclically. These interfaces provides functions to configure, start and stop the cyclictransmit messages.4.3.3.1 canSchedulerOpenThe function opens the cyclic transmit list of a CAN connection on a CAN interfaceboard. The complete syntax of the function is:HRESULT canSchedulerOpen(HANDLE hDevice,UINT32 dwCanNo,PHANDLE phScheduler )Parameters:hDevice[in] Handle of the CAN interface board.dwCanNo[in] Number of the CAN connection of the transmit list to be opened. Thevalue 0 selects the first connection, the value 1 the second connection andso on.phScheduler[out] Pointer to a variable of type HANDLE. If run successfully, the functionreturns the handle of the opened transmit list in this variable. In the eventof 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 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 expects the handle of a higher orderwindow, or the value ZERO if no higher order window is available, in theparameter hDevice and not the handle of the CAN interface board.70Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Interface description4.3.3.2 canSchedulerCloseThe function closes an opened cyclic transmit list. The complete syntax of thefunction is:HRESULT canSchedulerClose( HANDLE hScheduler )Parameter:hScheduler[in] Handle of the transmit list to be closed. The handle specified here mustcome from a call of the function canSchedulerOpen .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 hScheduler is no longer validand must no longer be used.4.3.3.3 canSchedulerGetCapsThe function determines the features of the CAN connection of the specified cyclictransmit list. The complete syntax of the function is:HRESULT canSchedulerGetCaps (HANDLEhScheduler,PCANCAPABILITIES pCaps );Parameters:hScheduler[in] Handle of the opened transmit list.pCaps[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.71Copyright 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 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?