•  
  • Home
    • Sign In
    • Register
  •  
  • About
    • Kepware
    • Partners
    • Trade Organizations
    • Contact Kepware
    • Career Opportunities
  •  
  • News
    • Press Releases
    • Articles & Sightings
    • Solution Chronicles
    • Awards & Quotes
    • Travel & Events
    • Upcoming Products
  •  
  • Products
    • Kepware Products
    • Pricelist
    • Downloads
    • Product Initiatives
  •  
  • Support & Services
    • Support Center
    • Search Knowledge Base
    • Technical Support

Kepware's U-CON Protocol OPC Server U-CON Protocol Server.  The reliable way to connect OPC client applications to a range of serial and Ethernet devices.
Begin Here
Step 1: Determine manufacturer and model number for the device or system.  What serial or Ethernet communication options exist? Step 2: Obtain protocol documentation for the device.  Many vendors provide a protocol manual with the device or make them available in .pdf format. Step 3: Determine a specific list of data you need to access from the device.  Choose a sample data value you would like to read.  Learn the transaction details for the sample data value.
Step 1: Determine manufacturer and model number for the device or system.  What serial or Ethernet communication options exist? Step 2: Obtain protocol documentation for the device.  Many vendors provide a protocol manual with the device or make them available in .pdf format. Step 3: Determine a specific list of data you need to access from the device.  Choose a sample data value you would like to read.  Learn the transaction details for the sample data value.
       
Next, build your tags
Step 4: Using a basic understanding of device communications and refer to the hardware manafacturer's protocol document to build tags for your communication profile. The Transaction Editor is the integrated development environment of the U-CON Protocol Server. It provides an easy and intuitive means for configuring the driver. Then, run your tags through our reliable OPC Server
Step 5: The Transaction Editor will validate your transactions then upload them to the OPC server as tags.  The server then makes tag data available to OPC clients.
Step 4: Using a basic understanding of device communications and refer to the hardware manafacturer's protocol document to build tags for your communication profile.
Download Free Demo of U-CON
U-CON Product Page
U-CON Tutorial Part 1
U-CON Tutorial Part 2
U-CON Tutorial Part 3
Contact Sales
Typical Applications
Step 5: The Transaction Editor will validate your transactions then upload them to the OPC server as tags.  The server then makes tag data available to OPC clients.
Complete U-CON licenses have the following: No device limits, no tag limits, no OPC client limits.  Sample device types include Balances, Bar Code Scanners, Counters, Meters, Readers, Recorders, RFID Devices and Weigh Scales.





Home | My Kepware | Products | Support | Partners | News | About | Contact | Legal | Sitemap

Copyright © 2008 Kepware Technologies, Inc. All rights reserved.