Interface

SUMMARY

Via Udp2Av the sending of data, live sign control und the data transfer from and to the visualization is monitored.

CONTENTS

  1. Introduction
  2. PLC Send:
  3. PLC Receive:
  4. Os Send / OS Receive

Introduction

Interface Sockets


The communication works optionally on Multicast or Broadcast and is processed via 4 sockets; there port numbers as well as the multicast address are defined in the Vision2000.ini.
Note:
If there is no multicast address defined in the Vision2000.ini, it is automatically switched to broadcast.

Any of the sockets serves a specific transfer type, whereas both OS-Sockets (OS = Operator Station) respectively both PLC-Sockets may use a common port number.
Default values:

If there are no actual data, any station sends live-sign telegrams on the ports which are monitored by the sockets and, dependent of the entries in the Vision2000.ini file, displayed by the Udp2Av.

To detect the loss of a telegram any station keeps a telegram counter which is verified on system start and on a General Request. In case a telegram is missing a Rollback-Request is send to the station in question; if that request fails a station specific General-Request is initiated.

PLC Send:

 This port serves the Data transfer from Operator stations to PLCs. All telegrams of an OS are send to the PLC specified in the telegram header. On a General Request any PLC receives an according Request telegram.

PLC Receive:

 This port serves the Data transfer from PLCs to Operator stations. For reasons of data integrity the telegrams of a PLC are send to the Operator Stations per Multicast/Broadcast. For the same consideration any Operator Station reports a newly set Control-Value as set, after the addressed PLC has send the according acknowledge telegram.

Os Send / OS Receive

 The whole data transfer between Operator stations is done via the OS-Ports. Depending on the type a telegram is send per Multicast/Broadcast or to an Operator Station specified in the telegram header.