AN-339 Trio Controllers Communication option

This document consists on a summarized guide of the whole range of communication protocols supported by Trio motion controllers.

After reading this document the user would be able to communicate with the controller through its different interfaces and built in communication protocols, as well as building a custom application layer by using BASIC code.

• Related Articles

• Ethernet IP between controllers

  No, it is not possible to set up EthernetIP between Motion Coordinators because our EthernetIP can only be the server side and we have no Client (Scanner) function. There are other protocols which can be used, for example Modbus TCP/IP can be set up ...

• AN-353 Trio Ethernet/IP

  This document describes Trio controller support for the EtherNet/IP protocol. The controller can act as a Class 1, 2 and 3 adapter (server) on an EtherNet/IP based network. The Motion Coordinator series 4 and above provide this support.

• AN-312 Ethernet UDP connection

  UDP is a connectionless transport protocol designed to operate over IP. Typical applications in Industrial Control includes fast data transfer from cameras and cyclic “Process Data” from PLCs. UDP does not guarantee the delivery of packets but ...

• AN-326 Connecting to TCP/UDP client

  It is possible to open one or more communication channels with remote devices using the TCP and UDP protocols via the controller’s main Ethernet port. This document explain and provide example of doing this

• Modbus TCP and Ethernet IP on Flex-6-Nano

  Q. Can we run and use Modbus TCP server and Ethernet IP server on Flex-6-Nano at the same time? A. Yes you can use both in parallel. They open different "port" numbers on the Ethernet communications but have the same IP Address. For example Modbus is ...