1 / 32

TOP Server 5 User Configurable (UCON) Driver Training

TOP Server 5 User Configurable (UCON) Driver Training. Lauren Conrad. Agenda. UCON Overview Example Messages Simple Read Transaction Simple Write Transaction Complex Transaction Unsolicited Transaction Resources. UCON Overview when and why to use it. Why Use UCON?.

denzel
Download Presentation

TOP Server 5 User Configurable (UCON) Driver Training

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TOP Server 5 User Configurable (UCON) Driver Training Lauren Conrad

  2. Agenda • UCON Overview • Example Messages • Simple Read Transaction • Simple Write Transaction • Complex Transaction • Unsolicited Transaction • Resources

  3. UCON Overview when and why to use it

  4. 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, WonderwareSuitelink, DDE, or GE iFIXPDB/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.)

  5. 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?

  6. Example Messages sample commands and protocols 30 31 2D 39 31 38 2D 31 0D 0A 02 03 00 00 00 01 84 0A 02 30 2C 50 46 2C 46 03 07 06 00 00 00 02 87 0A 02 35 2A 50 46 2B 09 30 2C 46 03 30 31 2D 39 31 34 37 4E 38 2D 31 0D 0A

  7. Example Command Formats • Read Command Format <STX><Device ID><Command><ETX> • Read Response Format <STX><Device ID><Command>,<Data1>,<Data2>,...<ETX> • Write Command Format <STX><Device ID><Command><Data><ETX> • Write Response Format <STX<Device ID><Command><Response><ETX>

  8. 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

  9. Simple Read Transaction creating a single read request 13.56 GPM 13.53 GPM 13.57 GPM 13.56

  10. Creating a Project

  11. Creating a Read Transaction

  12. Read Transaction Summary

  13. Simple Write Transaction creating a single write request 13.56 13.56

  14. Creating a Write Transaction

  15. Write Transaction Summary

  16. Updating the Server

  17. Complex Transaction reading multiple items in one request Station 1 256.05 °C 44 bar

  18. Adding Multiple Tags

  19. Creating the Transactions

  20. Buffer Pointer • Location of buffer pointer after the Read buffer is updated (Byte 1) • Pointer position after first seek command(Byte 5) • Pointer position after first move command (Byte 6) • Pointer position after second seek command (Byte 11) • Pointer position after second move command (Byte 12) • Pointer position after third seek command(Byte 19) • Pointer position after third move command (Byte 20) • Pointer position after fourth seek command (Byte 24) • Pointer position after fourth move command (Byte 25) • Pointer position after fifth seek command (Byte 27) • Pointer position after fifth move command (Byte 28) Quantity Product Name Product Code Units Unit Price

  21. Transaction Summary

  22. Tag Group

  23. Unsolicited Transaction processing unsolicited data 52,435 lbs. 65,456 lbs. 60,347 lbs.

  24. 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

  25. Creating an Unsolicited Device • Wait Time- how long the device waits for an unsolicited message before triggering the _UnsolicitedPcktRcvdOnTime system tag

  26. Adding Unsolicited Tags

  27. Creating Unsolicited Transactions

  28. Unsolicited Transaction Summary

  29. Unsolicited Tag Group

  30. Resources online information and contacting support

  31. Online • toolboxopc.com • Driver specific page: http://toolboxopc.com/html/ucon1.html • Support tab: http://toolboxopc.com/html/support.asp

  32. Contacting Software Toolbox Support • Questions? • Phone: +1 704 849 2773 • Email: support@softwaretoolbox.com • Fax: +1 704 849 6388

More Related