VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Accessing the busIf the connection is operated as a master, in addition to the control messagesLIN_MSGTYPE_SLEEP and LIN_MSGTYPE_WAKEUP, data messages of typeLIN_MSGTYPE_DATA can also be transmitted directly.If the connection is configured as a slave, only LIN_MSGTYPE_WAKEUP messagescan be transmitted. With all other message types, the function returns an errorcode.Messages of type LIN_MSGTYPE_SLEEP generate a Goto-Sleep frame on the bus,messages of type LIN_MSGTYPE_WAKEUP on the other hand a WAKEUP frame.Further information on this is given in the LIN specification in the section “NetworkManagement”.In the master mode, the function linControlWriteMessage is also used to sendIDs. For this, a LIN_MSGTYPE_DATA message with a valid ID and data length istransmitted, where the bit uMsgInfo.Bits.ido simultaneously has the value 1. Furtherinformation is given in section 5.3.4 in the description of the data structureLINMSGINFO.The function linControlWriteMessage always returns immediately to the callingprogram, irrespective of the value of the parameter fSend, without waiting fortransmission to be completed. If the function is called again before the lasttransmission is completed or before the transmit buffer is free, the function returnswith a corresponding error code.3.2.3 Message monitorA message monitor is generated or opened by calling the function linMonitorOpen.The parameter fExclusive defines whether the connection is to be used exclusively.If the value TRUE is entered here, no further message monitors can beopened after successful running of the function. If the LIN connection is not usedexclusively, any number of message monitors can in principle be created. This isonly limited by the installed memory.32Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Accessing the busIn the case of exclusive use of the connection, the message monitor is directlyconnected to the LIN controller. The following diagram shows this configuration.MonitorLIN controllerLINFig. 3-11: Exclusive use of a LIN connectionIn the case of non-exclusive use of the connection (fExclusive = FALSE), a distributoris connected between the controller and the message monitors.The distributor forwards incoming messages from the LIN controller to all monitors.The messages are distributed in such a way that no monitor is treated preferentially.The following diagram shows a configuration with three monitors onone LIN connection.MonitorMonitorMonitorDistributorLIN controllerLINFig. 3-12: LIN message distributor33Copyright 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 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?