Skip to content

Latest commit

 

History

History
76 lines (47 loc) · 2.56 KB

README.MD

File metadata and controls

76 lines (47 loc) · 2.56 KB

Device Interface Services

Table of contents

Introduction

The PLCnext Runtime provides four RSC services related to the device interface - Device Info service, Device Status service, Device Settings service, and Device Control service. This example shows how to use the methods on these four services to access and change information, status, and settings data in a PLCnext Control device.

Guide details

Description Value
Created 27.09.2024
Last modified 05.06.2025
Controller AXC F 2152
FW 2025.0
SDK 2025.0
PLCnext Technology Toolchain 2025.0

References

A complete description of the these services is available in the PLCnext Technology Info Center:

Quick-start example

This example demonstrates each of the methods on the four Device Interface services.

It is assumed that the user has some experience building C++ Components and Programs for PLCnext Control.

Prerequisites:

  • AXC F 2152 controller with firmware 2025.0.

  • PLCnext Technology Command Line Interface (CLI) tool, version 2025.0.

  • A Software Development Kit (SDK) for the AXC F 2152 PLCnext Control, version 2025.0.

  • (optional) Eclipse IDE, with the PLCnext Technology add-in installed.

  • (optional) Visual Studio, with the PLCnext Technology extension installed.

Procedure:

  • Clone this repository, e.g.

    git clone https://github.com/PLCnext/CppExamples.git

  • Create a new ACF project using either the PLCnext CLI tool, or Eclipse, or Visual Studio, with the following settings:

    • Project name: DeviceInterface
    • Component name: DeviceInterfaceComponent
    • Project namespace: DeviceInterface

  • Copy the contents of the Examples/DeviceInterface/src directory in this repository, to the src directory of the ACF project. Replace the existing source files with the same name.

  • Build the ACF project.

  • Deploy the ACF project to the PLC.

  • Restart the PLCnext Runtime.

  • Check the contents of the file /opt/plcnext/logs/Custom.log. It should contain messages from your ACF component.