VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Accessing the bus3.2.2.1 Controller statesThe following diagram shows the various states of a controller.linControlOpen()undefinedlinControlInitialize()linControlReset()offlinelinControlInitialize()linControlStart(...,TRUE)linControlStart(...,FALSE)linControlReset()onlineFig. 3-9: Controller statesAfter opening the control unit, the controller is normally in an uninitialized state.This state is exited by calling the function linControlInitialize. Then the LIN controlleris in “offline” state.With linControlInitialize, the operating mode and the bitrate of the LIN controllerare set . The bitrate in bits per second is defined in the parameter wBitrate. Validvalues for the bitrate are between 1000 and 20000, or betweenLIN_BITRATE_MIN and LIN_BITRATE_MAX. If the connection supports automaticbitrate detection, this can be activated with LIN_BITRATE_AUTO in the field wBitrate.The following table shows some recommended bitrates:Slow (Bit/Sec) Medium (Bit/Sec) Fast (Bit/Sec)2400 9600 19200The LIN controller is started or stopped by calling the function linControlStart.After successfully calling the function with the value TRUE in the parameter fStart,the controller is in “online” state. In this state the LIN controller is actively connectedto the bus. Incoming LIN messages are forwarded to all active messagemonitors.Calling the function linControlStart with the value FALSE in the parameter fStartswitches the LIN controller “offline”. Message transport is interrupted and thecontroller deactivated.30Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Accessing the busThe function linControlReset also switches the LIN controller to the “offline”state. In addition, the function resets the controller hardware. Note that faultytelegrams may be produced on the bus if a transmit process is interrupted duringtransmission when the function is called.3.2.2.2 Transmission of LIN messagesWith the function linControlWriteMessage, messages can either be transmitteddirectly or entered in a response table in the controller. For better understanding,please refer to the following diagram.Response TableID0ID1ID2::ID59ID60ID61ID62ID63Transmit BufferIDxFig. 3-10: Internal structure of the control unitThe control unit contains an internal response table with the response data forthe IDs transmitted by the master. If the controller detects an ID on the buswhich is assigned to it and has been send by the master, it transmits the responsedata entered in the table at the corresponding position. The contents of the tablecan be changed or updated with the function linControlWriteMessage by enteringthe value FALSE in the parameter fSend. The message with the response datain the field abData of the structure LINMSG is transferred to the function in theparameter pLinMsg. Note that the message is of type LIN_MSGTYPE_DATA andcontains a valid ID in the range 0 to 63. The table must be initialized before thecontroller is started, irrespective of the operating mode (master or slave), but canbe updated at any time without stopping the controller. The response table isemptied when the function linControlReset is called.With the function linControlWriteMessage messages can also be transmitted directlyto the bus. For this, fSend must be set to the value TRUE. In this case themessage is not entered in the response table but instead in the transmit bufferand transmitted to the bus, as soon as it is free, by the controller.31Copyright 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 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

Create successful ePaper yourself

Delete template?

Save as template?