Solutions for Vision-Guided Motion

TCP/IP allows the ORION controller and DVT SmartImage sensor to communicate effectively.ORMEC is pleased to announce a strategic marketing relationship with DVT Corporation --- a leading supplier of stand-alone, fully-integrated machine vision systems with headquarters in Norcross, GA  (www.dvtsensors.com).

The key technology link between the two companies is Ethernet TCP/IP communications ... plus support for the Modbus TCP applications protocol ... which together are used to create a simple, straightforward software interface between DVT SmartImage Sensors and ORION Motion Controllers in Vision-Guided Motion applications.

The ORMEC - DVT combination delivers a number of key advantages:

  • High speed Ethernet communications is faster and more effective than RS-485 serial communications commonly used between the motion controller and the vision system.
  • Information from the vision system is communicated to the ORION controller using Modbus TCP variables, eliminating the need for the application programmer to write extra code to parse and convert ASCII strings.
  • An ORION controller can open a Modbus TCP connection as a client, and request information as needed.
  • Multiple SmartImage sensors can be interfaced to the ORION controller using a standard Ethernet hub and a single connection to the ORION controller.
  • Implementing an Ethernet TCP/IP machine control network creates a way to unite other subsystems on the machine (I/O, HMIs, PC-based applications including SCADA, SPC and SQC) and allows easy access to information from the motion and/or vision systems.
  • Since TCP/IP is the "de facto" protocol of choice for corporate and telecommunications networks, access to the machine control network information including the vision and servo systems is available for remote development, maintenance, monitoring and/or reporting using standard tools such as a web browser.
  • ORMEC and DVT products have been applied in a number of applications  ... with a track record of success.

How the Software Interface Works

Modbus TCP application protocol creates a simple, straightforward software interface between ORMEC controllers and DVT SmartImage SensorsA powerful benefit that any "true" open standard provides is connectivity. When suppliers design products to comply with a standard, it creates built-in compatibility and synergy with other products designed for the standard.  An example of this is an ORMEC motion controller and a DVT SmartImage Sensor.  Both provide Ethernet TCP/IP communications; both support the Modbus TCP protocol.

As a result, the interface between the products is straightforward and simple. In DVT’s FrameWork software, variables related to vision are mapped to a selection of Modbus TCP registers. While in the corresponding MotionBASIC program on the ORMEC side, variables are mapped to the same registers.  During operation, the ORION controller simply acts as a "client" and opens a communications channel to the DVT and requests information as needed ... a software interface that’s elegant, fast and easy to implement.


Additional Links of Interest --- Adobe Acrobat Files 

  • For information on ORMEC and DVT's strategic marketing relationship, click here    (Adobe Acrobat file, 19k)
  • To view a press release covering the interface between ORMEC and DVT products, click here    (Adobe Acrobat file, 78k)
  • For an Application Note, "Communication between DVT and ORMEC Via Ethernet",  documenting the interface between ORION motion controller and DVT SmartImage Sensors,  click here.     (Adobe Acrobat file, 103k)

 

 

  © ORMEC Systems Corp and/or its suppliers. 
All rights reserved.  Revised:  September 10, 2007
Comments, questions or problems: send email to webmaster@ormec.com