VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Accessing the bus3.1.2.2 Message filtersEach control unit has a two-stage message filter. Messages received are filteredonly according to their ID (CAN-ID), data bytes are not considered.If the ‘Self reception request’ bit on a transmit message is set, the message is enteredin the receive buffer as soon as it has been transmitted on the bus. In thiscase the message filter is bypassed.CAN messageID notacceptedAcceptancefilterID acceptedID listID foundID notfoundMessagerejectedMessageacceptedFig. 3-3: Filter mechanismThe first filter stage, consisting of an acceptance filter, compares the ID of a receivedmessage with a binary bit sample. If the ID correlates with the set bit sample,the message is accepted, otherwise it is passed to the second filter stage. Thesecond filter stage consists of a list with registered IDs. If the ID corresponds tothe message of an ID in the list, the message is also accepted, otherwise it is rejected.The CAN controller has separate filters for 11-bit and 29-bit Ids, which are independentof each other. When the controller is reset or initialized, the filters areset so that all messages are let through.The filter settings can be changed with the functions canControlSetAccFilter,canControlAddFilterIds and canControlRemFilterIds. The functions expect two bitsamples as input values in the parameters dwCode and dwMask that define theID or the group of IDs that the filter lets through. However, a call of the functionsis only successful when the controller is in “offline” state.18Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Accessing the busThe bit samples in the parameters dwCode and dwMask define which IDs the filterlets through. The value of dwCode defines the bit sample of the ID, whereasdwMask defines which bits in dwCode are used for the comparison. If a bit indwMask has the value 0, the corresponding bit in dwCode is not used for thecomparison. If on the other hand it has the value 1, it is relevant for the comparison.With the 11-bit filter, only the lower 12 bits are relevant. With the 29-bit filter,bits 0 to 29 are used. The other bits must be set to 0 before calling the functions.The following tables show the relationship between the bits in the parametersdwCode and dwMask and the bits of the message ID (CAN ID):• Meaning of the bits for the 11-bit filter:Bit 11 10 9 8 7 6 5 4 3 2 1 0ID10 ID9 ID8 ID7 ID6 ID5 ID4 ID3 ID2 ID1 ID0 RTR• Meaning of the bits for the 29-bit filter:Bit 29 28 27 26 25 ... 5 4 3 2 1 0ID28 ID27 ID26 ID25 ID24 ... ID4 ID3 ID2 ID1 ID0 RTRThe bits 11 to 1 or 29 to 1 correspond to the ID bits 10 to 0 or 28 to 0. Bit 0 alwayscorresponds to the Remote Transmission Requests bit (RTR) of a message.The following example shows the parameter values for dwCode and dwMask, inorder to accept only the messages in the range 100h to 103h, with RTR-bit notset (= 0):dwCode: 001 0000 0000 0dwMask: 111 1111 1100 1Valid IDs: 001 0000 00xx 0ID 100h, RTR = 0: 001 0000 0000 0ID 101h, RTR = 0: 001 0000 0001 0ID 102h, RTR = 0: 001 0000 0010 0ID 103h, RTR = 0: 001 0000 0011 019Copyright 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 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 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?