VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Accessing the busNormally, the transmit task is disabled after opening the transmit list. The transmittask does not transmit any messages in the disabled state, even if the list containscreated and started transmit objects.The transmit task of a transmit list can be enabled or disabled by calling the functioncanSchedulerActivate.The function can be used to start all transmit objects simultaneously by first startingall transmit objects with canSchedulerStartMessage and only then enablingthe transmit task. It is also possible to stop all transmit objects simultaneously, bysimply disabling the transmit task.The transmit list can be reset with the function canSchedulerReset. The functionstops the transmit task and removes all registered transmit objects from the specifiedcyclic transmit list.3.2 Accessing the LIN bus3.2.1 OverviewThe following diagram shows an example of an IXXAT interface board with oneLIN and two CAN connections.IXXAT interface boardCAN controller 1CAN controller 2 LIN controller 1Control unitMonitorCAN 1CAN 2LIN 1Fig. 3-8: IXXAT interface board with one LIN and 2 CAN connections.As shown in Fig. 3-8 for the LIN connection 1, this consists of a control unit andone or more message monitors. The CAN connections available in addition to theLIN connection do not play a role in the following description.The control unit of the LIN connection is accessed with the function linControlOpen.The function linMonitorOpen opens a message monitor.Both functions expect the handle of the device or of the interface board in thefirst parameter and in the second parameter the number of the LIN connection.For connection 1 the number 0 is defined, for connection 2 the number 1 and soon.28Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Accessing the busTo save system resources, after opening a component the handle of the device orof the interface board can be released again. For further accesses to the connection,only the handle of the control unit or of the message monitor is required.The functions linControlOpen and linMonitorOpen can be called in such a waythat a dialogue window is presented to the user where he can select the device orthe interface board or the LIN connection. This is done by entering the value0xFFFFFFFF for the connection number. In this case, the functions expect the handleof the higher order window (parent) or the value NULL, if no higher orderwindow is available, in the first parameter and not the handle of the device or theinterface board.If run successfully, all three functions return a handle to the opened component.If an error or an access conflict occurs, the functions return a corresponding errorcode.If an opened component is no longer required, it can be closed again by callingone of the functions linControlClose and linMonitorClose.The possibilities offered by a LIN connection, or how the LIN connection is to beused, is described in more detail in the following sub-sections.3.2.2 Control unitThe control unit provides functions for configuring the LIN controller and itstransmission properties as well as functions for requesting the current controllerstatus.The component is designed in such a way that it can always only be opened byone application. Simultaneous opening of the component by different programsis not possible. This prevents situations where, for example, an application wantsto start the LIN controller but another wants to stop it.The control unit is opened by calling the function linControlOpen. If the functionreturns an error code “Access denied”, the LIN controller is already being used byanother program.This generally only represents a problem if an application cannot be run withoutdirect control by the LIN controller. In all other cases, however, the applicationshould be able to continue working normally.With the function linControlClose, an opened control unit is closed again and istherefore available for other applications. A program should thus only release acontrol unit when it is no longer required.29Copyright 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 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 52 and 53: Interface descriptionReturn value:I
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 82 and 83:
Interface description4.4.2.1 linMon
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Interface descriptionReturn value:I
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?