Generic_Teco is a project designed to demonstrate how a communication protocol is implemented and how a device is connected via the Generic communication driver. In this example project, the EPSNET protocol of the Tecomat PLC is chosen.

A device named Generic1 is defined via the Device Manager. Within the device, several special tags whose values are used for the communication are defined.

The InCount tag's value specifies the number of characters (bytes) received by the tag of type Input buffer.

The InBuffer tag is an array of bytes containing received data.

The OutCount tag's value specifies the number of characters (bytes) sent from the tag of type Output buffer.

The OutBuffer tag is an array of bytes containing data to send.

The Control tag's value is used to control sending data.

The PacketName tag provides an easy way to identify the communication packet in the communication statement or in the log file. If this tag is not used, its default name Packet is displayed in the statement.

In addition, an internal tag named Ethernet is defined. Its value determines whether a serial cable or Ethernet is used for communication. The value should be reflected when creating custom communication packets.

The main visualization window contains several controls intended for configuring and controlling the communication itself. The following communication packets can be sent: a packet for establishing communication, a packet for reading a data block from any register and address, a packet for reading/writing data from/to a tag of the selected data type from any address. By pressing the respective button, a communication packet will be created via a script according to the specified configuration settings and sent to the communication channel.

In the middle part of the window, sent and received data is displayed in a tabular format. In the top right corner, the control and status tags' values are shown.

In the bottom right corner, the checking tags' values read from the PLC by the Teco native communication driver are displayed (these tags lie on randomly selected addresses).

In order for the example project to be fully functional, it is necessary that the Ethernet option's value be set in compliance with the channel type specified through the Project Structure Manager.