OPC UA device information The Device Integration (DI) namespace In compliance with the “OPC UA for Devices” OPC UA Companion Specification, the eUA server provides the following nodes: Node Meaning DeviceManual Path or URL to the user manual. DeviceRevision General revision status of… Read More
OPC UA PubSub Available from firmware 2022.0 LTS on all PLCnext Control devices Configurable in PLCnext Engineer from software release 2022.0 LTS Starting with firmware 2022.0 LTS, the PLCnext Technology firmware has an implementation of the OPC UA® Publish and Subscribe specification (PubSub) as a new communication protocol. This enables the data exchange in a… Read More
Further information on OPC UA® in PLCnext Technology See these additional topics for further reference: Profile and facets shows all currently implemented facets, linked to the respective specifications Feature roadmap OPC UA shows which OPC UA® feature was implemented with which PLCnext Technology firmware release. Device-specific OPC UA settings shows the differences in… Read More
REST data interface – Sessions If desired, the web server can track the set of active client stations based on their corresponding session information. Otherwise, the web server automatically considers each station to be anonymous. Here’s how session reports are managed. Note: Phoenix Contact reserves the right to make changes and additions… Read More
REST data interface – Authentication This topic shows how to use the authentication service for protected resources on the PLCnext Engineer embedded HMI web server in order to use this service for making the REST data interface a protected service as well. Note: Phoenix Contact reserves the right to make changes and additions in further versions that might lead to… Read More
REST data interface – Groups If desired, the web server can manage the registered groups in order to make it easier to read a pre-defined list of variables. Otherwise, one can simply use the web server to read the variables directly. Note: Phoenix Contact reserves the right to make changes and additions in… Read More
REST data interface Introduction In this topic you will learn about the REST-based approach of PLCnext Technology which is utilized to exchange data via HTTP with the PLCnext Control’s firmware and with data in the Global Data Space (GDS). REST, or REpresentational State Transfer, is a software architecture style consisting of guidelines and best practices for… Read More
REST data interface – Variables Note: Phoenix Contact reserves the right to make changes and additions in further versions that might lead to incompatibilities. Therefore it is highly recommended to call this REST data interface out of your application explicitly with the version used during development, not with the latest key. Read Variable(s) This command… Read More
Modbus TCP client Available from firmware 2024.6 Modbus is a long-living communication standard in industrial automation. It has been developed to communicate via TCP and meeting security needs. There are different Modbus implementations available, e.g. as a function block (available in the PLCnext Store). But using a… Read More
Querying notifications via RSC INotificationLoggerService Notifications that have been saved by means of the Notification Logger can be queried via RSC interfaces, and one that is already provided with the PLCnext Runtime System is thisINotificationLoggerService. With the release of the PLCnext Control RFC 4072R which is the first PLCnext Control device made for system redundancy, an additionalINotificationLoggerService2 is provided… Read More
