Technical Data PLC Engine
The PLC Engine allows data processing in production lines.
It connects controllers, devices, SCADA systems and databases from various
manufacturers. It processes the data and dispatches them between the
connected devices and other systems. It collects data, manages them and
creates overviews for OEE applications.
Additional all the data can be handled over OPC. This are processed data and all data from the connected controllers, devices, OPC systems and databases.
PLC Engine is the perfect component for using it for communications in Industrie 4.0.
FunctionalityWith logic tables you define all the things your plant will need:
- Read and write data from industrial controllers and devices.
- Exchange data with databases. Read, write, update, delete.
- Read and write files, check for changes, create files, delete files.
- Send emails.
- Read and write data over OPC UA and Classic OP.
- Sequence chains with conditions for changing the actual step.
- Calculate data. Round, basic calculations, constants, conversions, reinterpretations.
- Check data. AND OR XOR NOT. Comparisons for equal, less, greater. Float number plausability.
- Manage data structures. Create them, decode structures.
- Collect data. Combine and separate texts. Combine and separate binary data.
- Lots of triggers: Time trigger, data change trigger, bit trigger, file create trigger, file modify trigger, directory change trigger.
- Handle UPC UA function calls (RPC).
- Generate OPC UA events.
Online diagnostics for shortening the configuration time
- Watch connections and their state.
- Watch variables. Status, value, who needs them.
- Watch logic tables and their behaviour.
- Watch and modify single variables (Status variable).
- Diagnostics logger for long term watching.
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.
This example reads a barcode, gets the print data from a database and prints the result.
Diagnostics boost the startup in plants. Use Your smartphone or tablet and all of the status displays.
The diagnostics logger handles longer running information collecting.
- OPC Pipe Open interface
- OPC UA (Unified Architecture)
- OPC DA (Classic OPC over DCOM, available under Windows only)
The maximum number of OPC clients is depending on used resources only. A PC
from 2014 can handle multiple hundred connections.
All OPC interfaces are working locally in one PC or over network.
in case of Classic OPC Classic please do not use DCOM over networks, but it will be supported.
OPC UA supports the fast binary protocol. Security is supported in all variants. Multicast discovery is supported.
Data access data items are supported up to 200K each.
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:
- AddNodes is possible only in Objects.Topics.Memory tree
- Reference type must be OpcUaId_Organizes
- NodeId can't be specified
- BrowseName can't contain a dot
- NodeClass must be Variable or Object
- NodeAttributes for Variable:
- DisplayName: unspecified or equal to BrowseName
- Description: unspecified or any text
- Value: is ignored; new variables will always be initialized to 0 (if numeric) or "" (if string type)
- OpcUaType_SByte, OpcUaType_Byte
- OpcUaType_Int16/32/64, OpcUaType_UInt16/32/64
- OpcUaType_Float, OpcUaType_Double
- OpcUaType_LocalizedString. This will be handled outside OPC UA as a normal string. The LocaldId always is a null string
- OpcUaType_ExtendedObject, OpcUaType_ExtendedObjectEx. Mostly this are structures. One of the structure types under Types -> DataTypes -> BaseDataType -> Structure -> UserStructures; these are the structures known to the PLC Engine core.
- if the structure is given both here and via TypeDefinition, both settings must match
- if unspecified, OpcUaType_Byte or the structure type of the TypeDefinition is used
- ValueRank, ArrayDimensions: unspecified (= scalar), scalar or a one-dimensional array of any size
- AccessLevel, UserAccessLevel: unspecified or (OpcUa_AccessLevels_CurrentRead | OpcUa_AccessLevels_CurrentWrite)
- MinimumSamplingInterval: unspecified or 0
- Historizing: unspecified or 0
- WriteMask, UserWriteMask: unspecified or OpcUa_NodeAttributesMask_Value
- NodeAttributes for Object:
- DisplayName: unspecified or equal to BrowseName
- Description: unspecified or any text
- EventNotifier, WriteMask, UserWriteMask: unspecified or 0
- TypeDefinition for Variable:
- one of the structure types under Types -> VariableTypes -> BaseVariableType -> BaseDataVariableType -> UserStructures; these are the structures known to the PLC Engine core.
- TypeDefinition for Object:
- Each RPC as a calling queue of 10. If the requests are coming faster before handled they will return a memory error.
Traffic between different OPC interfaces (tunneling) is supported. It will be used for the OPC DA tunnels.
- MQTT Client if a station need to be a device
- MQTT Broker, the server
MQTT comes from the Internet of Things world. It is simple and fast.
A device can simultanously send data to multiple devices.
You can use the client and broker on the same device at the same time.
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 InterfacesThe 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..
Controller Types and Controller Protocols
- Siemens S7 1200 and 1500 family. The optimized data blocks are supported, all symbols and comments are browsed online.
- Siemens S7 over RFC1006 and Sinec H1. Supported are S7 200, 300 and 400, Logo 8. Siemens CP or the Ethernet interface onboard the CPU can be used. Mainstream MPI Gateways as Hilscher Netlink, Helmholz Netlink, IBH Softec Netlink, INAT Echolink, Process Informatik S7Lan or Softing Netlink are supported, too. S7 compatible systems as VIPA Speed7 can be used, too.
- Siemens S5 over RFC1006, PLC Header, RAW or Sinec H1. Supported are Siemens CPs, INAT CPs, Helmholz CPs, IBH Softec S5Net, Process Informatik S5Lan.
- Rockwell Compact Logix, Control Logix and GuardLogix, all firmware versions.
Rockwell Micro 8 series as the 800, 810, 820 and more.
Rockwell PLC5 and SLC series, all firmware versions.
Routing is fully supported. This enables connecting to any PLC and accessing other PLC connected to an internal bus as DH+. So you will reach a PLC5 as example over another Rockwell as a CompactLogiX as router.
- GE PACSystems from General Electric. This controller family works with CIP from Rockwell.
- Mitsubishi Melsec Q, QL and FX5 family using the SLMP protocol (3E protocol).
- BACnet devices. BACnet is common used in building automation. BBMD and COV are supported.
- Devices using the Modbus TCP protocol.
- Phoenix Contact
- All systems and devices which can be accessed with OPC UA or Classic OPC.
- Raw data. This are data which do not have any format by a standard.
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 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:
- Search ussing broadcast.
- Search using the IP device address, receive the BACnet ID.
- Search using the BACnet id, receice the IP address.
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-arrayThese object types have a priority-array in addition to their present-value property:
- priority-array is read-only and contains 16 entries (that can be a valid value or NULL).
- present-value is read-write and contains 1 value (the non-NULL value with the lowest priority from priority-array, or the value from relinquish-default if no non-NULL value in priority-array exists).
- Writing to present-value uses an optional priority parameter to write to the correct entry in priority-array.
- priority-array is read-write and contains 16 structure entries with 2 fields:
* Value: the data value in this entry (or 0 if no valid value is present)
* ValueValid: a boolean value; 1 if Value is valid, 0 if not (NULL value).
- Writing to an element of priority-array implicitly uses a "write present-value with priority" operation to change the desired value.
- Writing to priority-array[i].Value always creates a non-NULL entry.
- Writing 0 to priority-array[i].ValueValid creates a NULL entry.
- Writing 1 to priority-array[i].ValueValid creates a non-NULL entry with value 0 (this is usually not very useful).
- Writing to priority-array[i] (as a structured data type) creates a NULL entry when ValueValid is 0. Else a non-NULL entry with the specified Value is created.
- present-value is read-write and contains the value obtained by BACnet protocol.
- Writing to present-value doesn't transfer the priority parameter. The BACnet device will implicitly write to priority entry 16 in this case.
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.
KNX will be used over IP / TCP and IP / UDP.
The symbol import is using the standarized ESF files.
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.
- My SQL (from version 1.9 not under Windows XP)
- PostGre Sql (not for Windows XP)
- Microsoft SQL
- Sybase SQL Server, Sybase ASE, SAP ASE (Adaptive Server Enterprise)
- Oracle can be used with ODBC
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.
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.
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.
No handling can be faster than the controller and device data acquisition. The same is true for database access.
Logic tables are constructed for linear logic. Loops are not possible.
A sequence chain supports the maximum of 65535 steps each.
Error Handling in Logic Tables
All logic elements which functions can fail are supporting an OK bit. The user need handle this preventing unexpected run-time behavior.
Variables and Structures
Structures can not contain loops.
A structure or variable can be up to 4GB in its size.
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
- Program code: A minimum of 6MB is used. The exactly memory usage is depending of the internal behavior of the operating systems. So dynamic libraries are loaded once for all running instances using them. Example: If the standard library is not loaded already it will use additional 4MB of memory.
- User data: The minimum data usage is 2MB internally. Additional the controller data are held in memory for comparing new data. Each item uses the length of data and additional 64 bytes. Each configured connection occupies 4KB.
- 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.
- Depending on the license the limits can be less.
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
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.
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.
- Windows 7, 8, 8.1, 10 (all versions). Older versions as Vista and Windows 7/8 also. 64 and 32 bit.
- Windows Server 2008, 2012, 2016, 2019.
- Windows XP 32 bit. This is a special installer for the OPC core product.
- Linux on the Raspberry and Odroid computers (64 and 32 bit).
- Linux on many Phytec devices.
- Linux on the Wiesemann & Theis pure.box 3, pure.box 5.
- Linux on a PC with Debian, Ubuntu, Suse, Arch, Centos, Redhat and other Distributions.
- Linux 64 Bit as Docker or Kubernetes or Containerd Container.
- OPC DA will require Microsoft Windows. All from Microsoft supported operating systems for Intel and all user languages will be supported. The latest service pack must be present.
- OPC DA will require minimum of 2 CPU cores for a good performance.
- Under Windows the OPC server are working as service, Linux runs them as daemon.
- The Raspberry version supports all Linux distributions offered for this platform.
- All other will run under lot of operation systems also, mostly Linux based.
- Under Linux the OPC Server needs a POSIX compatible System. The Standard Library needs V2.2 as minimum. The configuration software is bases on KDE 5 and is needing the kdelibs. Please use actual distributions like Debian, Ubuntu, Suse, Redhat or similar. Tested is: Windows Intel 32 and 64 bit, Linux Intel 32 and 64 Bit, Linux MIPS 32 CPU, Linux ARM 32 and 64 Bit CPU.
- Running in virtual machines is supported. Docker or Kubernetes containers are supported, too.
- Windows 7 needs as minimum service pack 1 for using the drivers. All Windows service packs for SHA512 must be installed.
All configurations are compatible to all OPC servers, also over mixed operating systems.