{ "BPVLVersion": 20000, "Copyright": "Copyright (c) 2020-2025 Basler AG", "FirmCode": "6001460", "InfoFileVersion": 20000, "InfoSignature": "5dbe45a7057631695e763351389c91461eb4622693ce777ea5428d358c521d2f07e3436cc8f3d3348d47e3f378d7bcf4bce89db26e63d8fc2ac79633ff98abad72b7616e504b0f055bf33585378f7a8458aeaac1e9fa54a092bb3903851d739fc8edcecf0c87782f90d2d3a5cd05677143291aa57b00207cbb45c36cdac0fc6cef7b37881a63347b31b2c2ffa3391b365f08ae20588ce13dec7aa3f451e8299750b8f26e7f63f95aa334fd52fc815a11e375cccd227f3ec2d729e86dcdba3930a0dde3431c46a3bf2c147817d502e230867bc19eb9b25c3e872919587287aba163e886b91a492d51c33106ea2fe86bac45eadc38577ab67d022e50ce10af4fe173a833f26e983baac85958095de1f6e961e10770f90021aab5bf198bff87eebbda44e03216496c7476c28f2aafefb9436af86638964f44e833cb29a3db9cabaab855aaadb2801a16290dac5e9f145d3e90ff0ec663eab5ec8e2a239076b1f88ecce77d7e8cdcfd1abeca3ef037f3c0f360c03eae9da370cf59ba5aecda18bbb40dc01d78fb62b748c79c54457a469a86109e79d10b14db2298e5eb39d075c2b7dd9536eab83cd303477a8087a478adc0372122ea8e79d8d933c843f5b80cea9f9ed2a865b16c0507cc4460fd1f964ebce9c6003ab2a20c2b96498d078564b7c99407278e301885d373935a53a2c6403eb3c5a4a093d7fae10e0060c0bd4f8f7a", "LibraryPublicKey": "30820222300d06092a864886f70d01010105000382020f003082020a0282020100a3e71e6067567d2f7ff34cdc2360aa65befd348f6e2bc24648a34c3823edaaaf5516373f25efee3940e3ec00538169cc8b650dd5cbde7d5c8704cc8ccd8802b135de9d67f924371335d3068eb55ad27f9d386a0e4f0b862655badbc1a51cefdd1a27b817329e15cd37176a4b5b15f2ecfbe75f9e579c2f79b68fd685e76977989d3419963925ac36dd1c66a5656dfc8c03ee9fd7cf159b130455eef03d75aab8ca7178a5a85d703376a52758ccd0cd1bc44fdd1bc1758c69776389a1b444ba1e9d81f308e0d7deed66d0c111da93f141939cbc500602e30640aa6d438ba392f4e4658aa420fffd7419e80f55916b2d9e13161e03cf70ff94daf947e08124b0e762c4ee3018fe6f85f6e738b2631f8c45ee95be0aef9ba09e980beaafba4ed0a9250d6fc29045d85e32968e4d6a1c0602c5c6d8f103dd5dad20f7798ce5007d809c05603410b9ab8f681a246bc7c181b83812cb3b260acaa1f3b218603757f8419d180a0c1fe96ca08d591a409445198ba706c3cc84d9043a7cd6595c070eb6f4b1dbb3098f7513a72338dd4f8d24b0a312e6e85cc1ce7b8fed8fe5e09491fa187c6b9b573135578387ad0689f83aac35183a663cf1508b2be481e00ff46b2977d4a55dbdd56b160c01d756a3ff734597baa1904f3754a4818ccc690da811983518c20af8118f4ff2ea2f0694e84fc35b7a34ee894d93ea3df3d43d609ed12b4d0203010001", "LibrarySignature": "8571491ee09137d350cf1bc63d4eacfe64849815439251f6bf3846f60dafd82387e7dfa4ed652ce4e948e4b11f9d46b8e43f73c0e43e87ad1429d6f8892eb2cb143eebe2765ee8cd10ab3da8e6fe2170cac5aa6a99799cee048fb8f7abc323047fb2dd46998da8f92259396851b008cb26fab00934e28d9aea331c280ca2c6a9a5e445c7708b1960664ea3959f93a91961819774660bdc8c313a2c1a575fc435de4e233e4aa1d899961b45b18124311d5667cbefc5e4b88c5b5d162b44d829ee9c1292d86f75f954f49f2ff31907376c7714478d3070dbc5bf8a7e47c9e05f2e43b2d57ec4d75c5a6396b56e4965913433a51dd642373ca3e2374f0d226f2ecddb51e8c15110861f8f8eebad060de57e805b6eb131f5256270a4fccb72806b55cb6bdfe1901d6e1441138cb520a62e55ee19509d7b93e19f1a4e2dff0b0eabbeb7fb0e3407721529c4e84bb2a3e325579f9e0bf5c5dbac6113d5996268b72cfb8e83a7596349bb620bd16822baac4ba59bc17b5423a8d56c1d1eda6cf28a9e169234da3474487814b1b661238d6ba8aa3537e008237e41d586da3f419eb817025fdd768af5fbde12745a3f02c24111e448f1022192f442565d06ba62510224cadeb1613d1d4ffae726260acd3c47ced4cb7138933125a14ebe480742845ac5ff05fc691213d3ff59eac4020876e3261a648dbdaadf0800cfdf908aa57f0402aa", "License": "Basler AG internal use only!", "Modules": [ { "DetailedDescription": "\n\n

OPC UA Client

\n\n

The OPC UA Client vTool allows you to use the data output of other vTools in your recipe as input for the next step in your machine vision environment using the OPC UA standard. You can add as many input pins as you like via the nodemap of the OPC UA Client vTool. The data types of the inputs don't have to be identical (see note below on allowed data types and pin type mapping).\n

\n\n

\n Note: The OPC UA Client accepts the following data types as input which are mapped to the corresponding OPC UA data types:\n

\n

\n\n

\n Adding Inputs\n

\n
    \n
  1. Select the OPC UA Client vTool in the Workbench.
  2. \n
  3. Open the Features - All pane.
  4. \n
  5. Go to the vTool group.
  6. \n
  7. Execute the Input Pin Add command.
  8. \n
  9. In the Input Pin Configuration field, enter the configuration of the input pin you want to add. Use the following syntax:
  10. \n MyPinName.Type=MyPinType.EndPointNode='OpcUaNodeIdentifier'
    \n where:
    \n MyPinName = Name of the new input pin
    \n MyPinType = Data type of the new input pin (allowed values: Boolean, Float, Integer, and String)
    \n OpcUaNodeIdentifier = Name of the node on your OPC UA server\n
  11. Press Enter.
  12. \n The new pin appears in the vTool.\n
\n\n

\n Configuration Example\n

\n

\n Assume you want to create an input pin with the name Exposure and the data type Integer that connects to a node called ExposureEnd on your OPC UA server. To do this, enter the following string:
Exposure.Type=Integer.EndPointNode='ExposureEnd'\n

\n\n


\n

\n Configuring the vTool\n

\n

\n You can configure the vTool via the pylon API and the Features - All pane of the pylon Viewer.\n All parameters listed there can be set via the pylon API. To study the effects of a parameter, change the parameter\n values in the Features - All pane and watch the results in a pin data view when running the recipe.\n For more details about parameters, select a parameter and check the Feature Documentation pane.\n

\n\n


\n

\n Get help\n

", "DisplayName": "OPC UA Client", "MinRequiredFileVersion": "2.0.0", "MinRequiredSoftwareVersion": "2.0.0", "Name": "OpcUaClient", "ObjectVersion": "2.0.0", "ProductCodeDemo": "10000101", "ProductCodeEval": "10000110", "ProductCodeFull": "30005000", "ShortDescription": "Send inputs to OPCUA server", "SupportedUuids": [ "3c1b06a5-148b-40b4-bd1f-8926dc45a900" ], "Tags": [ "UseCaseIdentifier=DataManagement", "LicenseGroup=Free", "OperationLevelGroup=Low", "AlgorithmTypeGroup=Classical" ], "Type": "VTool", "Uuid": "3c1b06a5-148b-40b4-bd1f-8926dc45a900" } ], "Vendor": "Basler AG", "Version": "2.0.0" }