VCI - Virtual CAN Interface - Ixxat

More documents

Recommendations

Info

Accessing the busAs the example shows, only individual IDs or groups of IDs can be activated withthe simple acceptance filter. However, if the required IDs do not correspond to acertain bit sample, the acceptance filter quickly reaches its limits. This is where thesecond filter stage with the ID list comes into play. Each list can contain up to2048 IDs, or 4096 entries.Individual IDs or groups of IDs can be added to the list via the function canControlAddFilterIdsand removed again with the function canControlRemFilterIds. Theparameters dwCode and dwMask have the same format as with the acceptancefilter.If the function canControlAddFilterIds is called, for example, with the values fromthe previous example, the function adds the IDs 100h to 103h to the list. If onlyone single ID is to be added when the function is called, the required ID (includingRTR-bit) is entered in dwCode and dwMask set to FFFh or 3FFFFFFFh.The acceptance filter can be completely blocked by calling the function canControlSetAccFilterif the value CAN_ACC_CODE_NONE is entered for dwCode andthe value CAN_ACC_MASK_NONE for dwMask. Further filtering thereafter is onlycarried out based on the ID list. Calling the function with the valuesCAN_ACC_CODE_ALL and CAN_ACC_MASK_ALL, on the other hand, opens theacceptance filter completely. The ID list therefore has no effect in this case.3.1.3 Message channelA message channel is generated or opened by calling the function canChannelOpen.The parameter fExclusive defines whether the connection is to be usedexclusively. If the value TRUE is entered here, no further message channels can beopened after the function has been successfully run. If the CAN connection is notused exclusively, any number of message channels can theoretically be created.In the case of exclusive use of the connection, the message channel is directlyconnected to the CAN controller. The following diagram shows this configuration.20Copyright IXXAT Automation GmbH C-API Programming Manual, Version 1.5
Accessing the busMessage channelCAN ControllerCAN BusFig. 3-4: Exclusive use of a CAN connectionIn the case of non-exclusive use of the connection (fExclusive = FALSE), a distributoris connected between the controller and the message channels. The distributorforwards incoming messages from the CAN controller to all message channelsand transfers the transmit messages of the channels to the controller. The messagesare distributed in such a way that no channel receives preferential treatment.The following diagram shows a configuration with three channels on oneCAN connection.Message channelMessage channelMessage channelDistributorCAN ControllerCAN BusFig. 3-5: CAN message distributor21Copyright 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 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

Create successful ePaper yourself

Delete template?

Save as template?