Why Use UCON? Allows user to easily create a device driver for devices with no off-the-shelf driver solution Is completely integrated into the TOP Server just like other TOP Server drivers Allows user to configure a set of “transactions” through the user interface based on the protocol format required by the device Makes device data available to any OPC DA, OPC UA, Wonderware Suitelink, DDE, or GE iFIX PDB/NIO Client Requires no programming experience Provides access to barcode readers, scales, gauges, etc. Eliminates need for expensive and unreliable alternatives (i.e. custom driver development, manual data entry, interfacing device to a PLC, etc.)
Evaluating the Protocol How Complex is it? How is the data presented? How many items will the driver be requesting? How are the packets terminated? How do we connect to the device? Is the device a slave or a master?
Example Command Formats Read Command Format Read Response Format,,,... Write Command Format Write Response Format
Example Protocol Types Binary – Modbus Holding Register Request Hex ASCII – Modbus ASCII Holding Register Request ASCII – Unsolicited Packet Sent from Bar Code Reader – Unsolicited Multiple Data Packet Sent from Inspection System
Buffer Pointer 1.Location of buffer pointer after the Read buffer is updated (Byte 1) 2.Pointer position after first seek command (Byte 5) 3.Pointer position after first move command (Byte 6) 4.Pointer position after second seek command (Byte 11) 5.Pointer position after second move command (Byte 12) 6.Pointer position after third seek command (Byte 19) 7.Pointer position after third move command (Byte 20) 8.Pointer position after fourth seek command (Byte 24) 9.Pointer position after fourth move command (Byte 25) 10.Pointer position after fifth seek command (Byte 27) 11.Pointer position after fifth move command (Byte 28) QuantityProduct NameProduct CodeUnits Unit Price
Creating an Unsolicited Channel Enable Unsolicited mode by checking the box Receive timeout- the amount of time the driver should wait for the unsolicited message to come in Dead time- allows TOP Server to re-synchronize itself with the device(s) after receiving a message with an unknown key Key length- tells the driver how many characters to use as transaction keys (must be the first characters in a message) Log unsolicited message timeouts- places a message in the event log when the "Receive timeout" period expires while receiving an unsolicited message
Creating an Unsolicited Device Wait Time- how long the device waits for an unsolicited message before triggering the _UnsolicitedPcktRcvdOnTime system tag