THIS PROJECT IS NO LONGER MAINTAINED, either in Github or in the PLCnext Store.

For examples of how to develop ACF Components for the PLCnext Runtime, please see the C Examples repository on Github.

For MQTT Client solutions on a PLCnext Control device, please search the PLCnext Store for suitable apps.

Unfortunately there is currently no publicly available procedure for developing a custom RSC service for the PLCnext Runtime, similar to the one demonstrated here. If this is a requirement for your project, please get in touch through the PLCnext Community.

MQTT Client is a PLCnext Technology component that allows PLCnext Control applications to use MQTT Client functions through a Remote Service Call (RSC) interface.

Contributions to this project are welcome.

Building from source requires the PLCnext SDK for your target. It is strongly recommended that you use the PLCnext Command Line Interface (CLI) to install and manage PLCnext SDKs on your host. Assistance with this is available from the PLCnext Info Center.

An example of a build session is as follows:

$ git clone https://github.com/PLCnext/MqttClient
$ cd MqttClient
$ cmake -G "Ninja" 
> -DCMAKE_TOOLCHAIN_FILE=/opt/pxc/sdk/AXCF2152/2019.3/toolchain.cmake
> -DBUILD_TESTING=OFF
> -DUSE_ARP_DEVICE=ON
> -DCMAKE_STAGING_PREFIX=/home/tcs-user/Documents/projects/MqttClient/bin/axcf2152
> -DCMAKE_INSTALL_PREFIX=/usr/local
> -DCMAKE_PREFIX_PATH=/home/tcs-user/Documents/projects/MqttClient/external/deploy/axcf2152
> -DCMAKE_EXPORT_COMPILE_COMMANDS=ON
> -DARP_TOOLCHAIN_ROOT=/opt/pxc/sdk/AXCF2152/2019.3
> -DARP_DEVICE=AXCF2152 "-DARP_DEVICE_VERSION=2019.3 (19.3.0.18161)"
> -S . -B ./build/axcf2152-2019.3
$ cmake --build /home/tcs-user/Documents/projects/MqttClient/build/axcf2152-2019.3 --config Debug --target all -- -j 3
$ cmake --build /home/tcs-user/Documents/projects/MqttClient/build/axcf2152-2019.3 --config Debug --target install -- -j 3

Copy the contents of external/deploy/axcf2152 to /usr/local on the target.

Copy libPxceTcs.Mqtt.Client.so to /usr/local/lib on the target.

Copy libs/MqttClientService/intermediate/config/MqttClient.acf.config to /opt/plcnext/projects/Default on the target.

Reboot the target.

Basic steps for using the MQTT Client RSC service in a PLCnext C component:

• Include Arp/System/Rsc/ServiceManager.hpp and IMqttClientService.hpp
• Declare a variable of type PxceTcs::MqttClient::Services::IMqttClientService::Ptr
• In the component's SubscribeServices method, call ServiceManager::GetService<IMqttClientService>("PxceTcs"), and assign the result to the pointer variable.
• Using the assigned pointer, call the CreateClient method to create an MQTT Client.

The complete API for the MQTT Client service is available here.

The CreateClient method must always be called before any other MQTT operation. This method returns a unique ID that must be used in all other method calls. In this way, it is possible to create multiple MQTT Client instances.

The DestroyClient method should always be called when an MQTT client instance is no longer required, for example during component shutdown.

The MQTT Client service wraps parts of the open-source Paho MQTT C library (specifically, some methods of the Paho client class), so users the documentation for the Paho library will also be useful in understanding the behaviour of this service.

Client-side message persistence has not been implemented in this version.

One example of a PLCnext Component that uses the MQTT Client service is the MQTT GDS Connector which, together with this project, was used to create the MQTT Client Function Extension app in the PLCnext Store.

This code requires:

1. The Paho C library Copyright (c) 2013-2017 Frank Pagliughi.

   All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

2. The Paho C library by Ian Craggs Copyright (c) 2013-2018, IBM Corp.

   All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 and Eclipse Distribution License v1.0 which accompany this distribution.

   The Eclipse Public License is available at http://www.eclipse.org/legal/epl-v10.html and the Eclipse Distribution License is available at http://www.eclipse.org/org/documents/edl-v10.php.