Features, discussions, tips, tricks, questions, problems and feedback

Adroit SUI connection to Toyopuc PLC CPU

#1

Adroit SUI connection to Toyopuc PLC CPU

Introduction
A small write-up regarding the communication connection between Adroit SCADA and Toyopuc PLC. The possibilities, constraints, limitations, considerations, and possible solutions are briefly discussed.

Toyopuc PLC built-in communication capabilities
The Toyopuc PLC supports the following communication protocols:
image

These run on the following ports (built-in on the CPU)
image
image

Adroit SCADA communications connection capabilities\possibilities
The following cannot be used to interconnect with the Adroit SCADA:

  • CMP-Link (Computer Link) in Toyopuc PLCs is a serial or Ethernet-based communication protocol designed for connecting Toyopuc PLCs to computers or HMIs for data exchange and programming.

  • PC-link is a proprietary communication protocol used for high-speed data exchange between Toyopuc PLCs or between a PLC and a computer.

  • FL-NET is a network protocol that enables peer-to-peer communication between PLCs, CNCs, and other devices from different manufacturers.

Other communication protocols on the PLC:
As for the communication protocols that can be used to transfer data to external devices:
Ethernet communication standards:

  • EtherCAT:
  1. Requires a special card on PC
  2. There is no Adroit communication driver for it. (thus direct connection is not possible)
  • Ethernet\IP:
  1. There is no Adroit communication driver for it. (thus direct connection is not possible)

If these are required to interface with an Adroit SCADA, then an OPC server is to be considered as an intermediary middleware bridge. (3rd Party OPC servers can be considered)

Serial communication standards: (RS-485)
Modbus-RTU (slave).
a. Adroit does have a Modbus-RTU serial driver. This can work.

image
image.png963×463 44.7 KB

However, note that a PC does not by default have an RS-485 serial communication port.
Either such a card is to be installed, or a communication standard converter is to be introduced (RS-485 to Ethernet standard conversion).
Note that this is a communication standard converter, not a protocol converter. The result would be Modbus RTU serial over ethernet. (MOXA has such options.)

Additional Notes:

• A PLC communicates to a SCADA via communication protocols, (not communication ports).
Protocols run communication standards, and they are classified by the communication standards (e.g. serial or ethernet)

• Communication standards for the most part have predetermined communication ports associated with them (e.g. RJ-45)

• However, the communication port does not determine the communication standard, necessarily. (e.g. RJ-45 can also be used to run serial communication).

• Thus, even if a PLC CPU (or module) has an RJ-45 communication port, that does not mean by default that this communication port is an ethernet standard communication port.

• Furthermore, even IF the port is for ethernet standard communication, that does not mean that it can be connected to a SCADA, by default.

• The communication protocols must be supported by both nodes (e.g. PLC and SCADA).
These communication protocols usually come in the form of installed drivers. However, not all nodes support all drivers, as not all nodes are compatible with all communication drivers. These are predetermined and relate to firmware on the PLC side and developed driver files (.dll) on the SCADA side.