Этот сайт использует кукис. Пользуясь сайтом, вы соглашаетесь с тем, что мы используем кукис-файлы. Переспросить позже Больше сведений

PLC Engine Data Sheet

PLC Engine Data Sheet

Created by Werner Krings, Tani GmbH
Date: 2019.7.1

Technical Data PLC Engine

С первого взгляда

PLC Engine позволяет обрабатывать данные на производственных линиях.
Он соединяет контроллеры, устройства, SCADA системы и базы данных различных производителей. Он обрабатывает данные и передает их между подключенными устройствами и другими системами. Он собирает данные, управляет ими и создает обзоры для OEE приложений.
Все дополнительные данные могут быть обработаны через OPC. Это обрабатываемые данные и все данные от подключенных контроллеров, устройств, систем OPC и баз данных.

PLC Engine является идеальным компонентом для использования в коммуникациях Индустрии 4.0.

Вы будете реализовывать важные случаи использования с PLC Engine
Optimize PLC Communication
Ускоряет обмен данными с PLCс помощью логической оптимизации запросов. Часто это происходит с текстами ошибок от контроллеров. Сообщения должны быть извлечены нормально, если изменяется соответствующий код ошибки и новое состояние ошибки становится верным. Без каких-либо изменений в Вашей SCADA системе связь ускоряется. Основной причиной является меньшая нагрузка на линию связи.
Copy PLC Data
Обмен данными между контроллерами и устройствами без программирования PLC или функциональности SCADA.. Вот как это делается: Двигатель PLC Engine считывает данные с контроллера или устройства и записывает их в другой контроллер или устройство. Запись обычно выполняется, если данные меняются. С помощью настраиваемых триггеров могут быть определены данные, которые зависят от других условий записи. При необходимости данные будут преобразованы. Это важно, если оба контроллера разные: Один Siemens S7, другой Rockwell Control Logix.
Более сложное управление тоже возможно: Сбор данных с одного или нескольких контроллеров, выполнение некоторых расчетов с данными и запись результата в контроллер или устройство. Конечно, любая OPC совместимая система может также использовать те же данные.
Collect Data
Сбор и обработка данных
PLC Engine считывает данные с одного или нескольких контроллеров.
Данные собираются и, возможно, рассчитываются или нормализуются.
If all data are in place they are ready to process for other systems or OPC access.
During the logical processing the data are blocked for access.
Syncronous data access are waiting until the collection is finished.
Configurable error conditions are configurable: If one of the controllers is not available constant data are used, or an error number is processed.
PLC to Database
Exchanges data with common databases. You can read data from controllers and write them directly into common databases - with optional calculations. Data readed from databases can be written into controllers, too. All the data are available for OPC systems also.
Overall Equipement Effectiveness
Collects data over long time for OEE into a local or external database. So easily OEE applications can be build. The integrated websites are offering the collected and calculated data directly as curves or other. Additionally the data can be handled over OPC.

Functionality

With logic tables you define all the things your plant will need:

Online diagnostics for shortening the configuration time

Configuration

The configuration works in graphical style or with simple lists.

Lot of Wizards simplify this.

The example logs from barcode reader, adds a timestamp and writes both into a .csv file.

Logging to CSV file


This example reads a barcode, gets the print data from a database and prints the result.

Read database with a barcode, add print data and send them to the printer

Diagnostics boost the startup in plants. Use Your smartphone or tablet and all of the status displays.

Online diagnostics of logging to CSV file

Журнал диагностики предназначен для более длительного сбора информации.

Diagnostics logger

OPC Interfaces

Максимальное количество OPC клиентов зависит только от используемых ресурсов. С 2014 года один ПК может обрабатывать несколько сотен соединений.
Все интерфейсы OPC работают локально на одном ПК или по сети.
в случае Classic OPC Classic, пожалуйста, не используйте DCOM по сети, но он будет поддерживаться.
OPC UA поддерживает быстрый двоичный протокол. Безопасность поддерживается во всех вариантах. Поддерживается многоадресное обнаружение.
Элементы данных для доступа к данным поддерживаются до 200 000 штук каждый.

OPC UA functionality and limitations

The OPC UA implementation conforms to the specification 1.04.
The OPC UA Standard Model is supported, some extensions exist.
An internal discovery server is active on standard, it supports multicast discovery also. It can be used as a global discovery server. Alternatively an external discovery server can be configured.

The session timeout will be limited to one hour.
The server and client certificate will be renewed if the Tani self signed certificate is used. All other certificates remain unaffected on expiring. The certificate validity is checked all 12h. It will be renewed seven days before it expires. Running connections will not be affected, new connections will use the new certificate.
AddNodes is supported with the following restrictions:

Поддерживается трафик между различными интерфейсами OPC (туннелирование). Он будет использоваться для туннелей OPC DA.

Controller Interfaces

All controllers will be connected over network. Often this is Ethernet, WLAN or other networks. All serial Ethernet and MPI Ethernet gateways for industrial controllers usage are supported.

Configuration Interfaces

The configuration can be done with the shipped configuration software or over OPC with the System topic.
The connection  for the configuration is encrypted with TLS 1.2. The encryption can be switched off for usage in countries where encryption is forbidden.

Network Redundancy for connections to controllers and devices

Connections to devices and controllers are supporting network redundancy.
Double and triple redundancy can be selected.
Two redundancy operation modi are possible.
In dynamic redundancy any of the connections is working as master. If it breaks another connection becomes the master connection.
In static redundancy the first connection is the master. If it breaks another connection becomes the master. If the first connection works again it will become the master connection again.

The connections of the redundancy should work on different netaork adapters.The adapters need different IP subnets for proberly work..

Типы контроллеров и протоколы контроллеров

Общается через Ethernet.

BACnet

BACnet will be used over IP / UDP.
Maximum length of strings: 256 Byte
Status text elements are supported (state_text)
Supported charsets: UTF-8, UTF-16, Latin-1
Unions ("Choice") and structures ("Sequence") are existing for important values. All unimplemented instances will not be shown.
Enum values are represented as UINT32. Some special enum are handled as bool.
Values in "Octet-String" and "Bit-String" can be written in whole only.

BBMD (BACnet Broadcast Management Device) details

BBMD will be used during the connection establishing and the device search if the devices do not be all in the same collision domain. BACnet uses broadcast during ist connection establishing.
There are several procedures in BBMD:

Additionally BBMD can be used connecting older serial only installations to the IP network.

COV (Change Of Values) details

COV represents the event subsystem of BACnet. Events will be offered in browsing the variables, they will be subscribed. If the device will send the data the event will be generated.
Because BACnet is working with UDP the COV receive can not be guaranteed. Tani is offering an option: If no event will be received during the reconnection time from the configured connection it will be polled. If the value did not change no event is send for this polling.

BACnet - Writing values with priority-array

These object types have a priority-array in addition to their present-value property: The BACnet spec says: The Tani implementation works as follows:

This mechanism was chosen to allow choosing the write priority via OPC without changing the read syntax for present-value property. This also allows writing NULL values via OPC.

Databases

PLC Engine is a database client. It connects with user and password to the database.
The standard SQL statements INSERT INTO, UPDATE, SELECT, DELETE, FUNCTION and PROCEDURE will be used over the wizards. Other statements will be configured directly.
Supported are:

Multiple databases can be handled simultanously.
In one database multiple sub databases can be used.
During the configuration the databases will be browsed. This will require depending on the type of the database or the interface a username and a password, possibly more.
The database itself need to be configured that it can be accessed.
PLC-Engine will need an account on each database.

For using PLC Engine on a PC the locally installed databases can be used also.
On PLC Engine Device a My SQL database is installed. This database will be managed completely by PLC Engine.

Logger for diagnostics

The OPC Server contains a logger for diagnostics purposes during plant startup. The logger can be configured. The system load can be big if all controller data in big plants are logged.

Limits

Maximum number of configurable client connections: 4000.
Maximum length of a single item: 4GB.
Maximum number of elements each connection: 1 million.
Maximum number of elements (Items): 16 million.
Maximum OPC groups each connection: 100.
Maximum number of passive connection for each port is 999.
The OPC synchronous functions returning a bad quality immediately if the PLC connection is not established.
Changes in controller configuration will be checked all 10 seconds if the PLC does not offer a mechanism for this check during write.
Fields can be up to 64K in length each.
Multi dimensional arrays can have up to six dimensions.

Fields can be up to 64K in length each.The maximum amount of configurable logic tables is 60000.
The maximum length of one logic table is 4GB.
Maximum number of entries on a logic element 60000.
File operations can handle up to 64K in each request. Adding data to a file is limited only by the space on the disk.
Multi dimensional arrays can have up to seven dimensions.

Depending on the license the limits can be less.

Speed

The throughput will be mainly limited by the controller speed or the reaction time of OPC applications.
Read requests to the controller will be optimized as much the controller is supporting this. For that elements will be collected to blocks reading more than requested, but not for inputs and outputs. These optimizing can be affected by configuration separately for each connection. Optimizing can be switched off, too.
Write requests to the controller are collected or handled in that order the application did called the system.
On OPC all optimizing the individual OPC uses is supported.
The normal time in cyclic controller requests is 50ms.It can be faster if the controller polling interval is set to zero.
Only data are sent to OPC which did change in the controller between two read requests.

The throughput of one logic table normally will be handled below 10ms. Lot amounts of logic tables containing much of mathematics functions may rise the 10ms. This is true especially on embedded devices without a mathematical co processor.
No handling can be faster than the controller and device data acquisition. The same is true for database access.

Функции

Логические таблицы

Логические таблицы построены для линейной логики. Петли(Loop) сделать невозможно.

Sequence chains (Цепи последовательности)

Цепь последовательностей поддерживает не более 65535 шагов каждая.

Обработка ошибок в логических таблицах

Все логические элементы, функции которых могут давать сбой, поддерживают бит OK. Пользователь должен разобраться с этим, чтобы предотвратить неожиданное поведение во время выполнения.

Переменные и структуры

Конструкции не могут содержать циклов/петли (Loop).
Размер структуры или переменной может составлять до 4 Гб.

Status Diagnostics Lists

The status diagnostics lists are supporting arrays up to 100 values each. If an array is longer than 100 values the first 100 elements are shown only. Writing this array is not possible.

Field and text optimizings

The from version 1.8 existing field optimizings will prevent reading the long fields too often, the index is requested on standard only.This optimizing bases of the fact that the index does net changed too frequently.

Usage of memory

Usage of computation time

The consumed computation time is depending on the load with communication. Most the time it will be waited for controller data or OPC application reaction.
All software is working with events. This maximizes the throughput and minimizes the usage of computation time.
Multiple CPU are supported. Up to ten CPU will be used, the main work will be handled by three CPU.

Installation

The installation does depending on the product install multiple parts separately. On uninstall not all products are deleted automatically. But all installed products can be deleted over the menu or the software part in the system control manager.
The user settings will be preserved and not deleted during uninstall.

Операционные системы