In essence, this Technical Note (TN) is very similar to [[MISC-TN-024: Automated test equipment (ATE) monitoring with SBCSPG gateway and ThingsBoard IoT platform|this one''MISC-TN-024: Automated test equipment (ATE) monitoring with SBCSPG gateway and ThingsBoard IoT platform'']]. There is a noticeable difference, however, as a different software stack was used on the edge device. In this case, [https://www.lfedge.org/projects/fledge/ LF EdgeFledge] was utilized.

As described in [[MISC-TN-024: Automated test equipment (ATE) monitoring with SBCSPG gateway and ThingsBoard IoT platform|''MISC-TN-024'']], the PLC we want to talk to is connected to a different subnet, namely 192.168.30.0/24. For testing the connection to the PLC, after adding the required subnet configuration, the <code>modbus</code> command line tool was used, which is provided by the <code>modbus_cli</code> package. In the following example, the register mapped ad the address 300 is read.

We then configured Fledge in order to read periodically a couple of PLC's registers. Please note that this is a no-code operation as it is carried out with the help of the native web-based Fledge UI. To access PLC exposed data, the Fledge's <code>modbustcp </code> South plugin was used. Please note that also we had to patch it manually to solve a bug that prevented it from working properly. The patch is detailed [https://github.com/fledge-iot/fledge-south-modbustcp/pull/26/files here]. To make the change effective, we disabled and re-enabled the plugin via the web interface.

[[File:SBCSPG-Fledge-12.png|center|thumb|600x600px|Installing the <code>modbustcp </code> South plugin.]][[File:SBCSPG-Fledge-23.png|center|thumb|600x600px|Configuring the plugin]][[File:SBCSPG-Fledge-4.png|center|thumb|600x600px|Configuring the plugin.]][[File:SBCSPG-Fledge-5.png|center|thumb|600x600px|The plugin is enabled.]] Riavviare south plugin disable/enable per via grafica[[File:SBCSPG-Fledge-6.png|center|thumb|600x600px|Fledge provides a native web interface to visualize collected data.]]

You can think about this This Technical Note (TN) as an evolution of the article "[[MISC-TN-021: SBCSPG and ThingsBoard IoT]]"from fledge. The use case described here is a real-world application based on the same elements: common import logger* [[MISC-TN-004: Running Debian (armbian) on SBCSPG#The hardware platform|The ''SBCSPG'' industrial gateway]] * [https://thingsboard.io/docs/ ''ThingsBoard IoT platform''] * [https://thingsboardfrom fledge.io/docs/iot-gateway/what-is-iot-gateway/ ''ThingsBoard IoT gateway'']plugins. The application is to monitor robotized DAVE Embedded Systems' ATEs like the one shown [https://youtunorth.be/OoNiKgJXq00?t=409 here]common.common import *

__author__ ="Andrea Marson"__copyright__ = Implementation "Copyright (c) 2023 DAVE Srl"__license__ ="Apache 2.0"__version__ =The implementation is suitable for a production environment. Unlike what we did for [[MISC-TN-021: SBCSPG and ThingsBoard IoT|this TN]], in this case the ThingsBoard IoT platform was installed on the cloud, specifically on an AWS EC2 instance running Ubuntu Linux. The following diagram shows the complete solution."${VERSION}"

[[File:ATE monitoring SBCSPG ThingsBoard_LOGGER = logger.png|center|thumb|1000x1000px]]setup(__name__)

_DEFAULT_CONFIG === { 'plugin': { 'description': 'ThingsBoard North Plugin', 'type': 'string', 'default': 'thingsboard', 'readonly': 'true' }, "tb_iot_platform_host": { "description": "ThingsBoard IoT configuration ===platform host.", "type": "string", "default": "put the public name of your host here", "order": "2",To install "displayName": "ThingsBoard IoT platform on an EC2 instancehost" }, "tb_mqtt_topic": { "description": "MQTT topic", "type": "string", [https "default":"v1/devices/me/thingsboardtelemetry", "order": "3", "displayName": "MQTT topic", 'readonly': 'true' }, "tb_device_access_token": { "description": "Device's access token.", "type": "string", "default": "put your device's token here", "order": "4", "displayName": "Device's access token" }, "source": { "description": "Source of data to be sent on the stream.io/docs/user-guide/install/cluster/aws-self-hosted-setup/ these instructions", "type": "enumeration", "default": "readings", "options": ["readings"] were followed. , "order": "5", "displayName": "Source", 'readonly': 'true' }}

=== ThingsBoard IoT gateway configuration ===To run this esample, the most important module to configure was the [https://thingsboard.io/docs/iot-gateway/config/modbus/ Modbus connector]. The following box shows the resulting configuration file needed to poll some variables of the arm's joints def plugin_info(namely temperatures and currents).<syntaxhighlight lang="json">armbian@sbcspg:~$ cat /etc/thingsboard-gateway/config/modbus.json{ "master": return { "slaves" 'name': ['thingsboard', { "host"'version': "192'2.1681.30.42"0', "port": 502, " 'type"': "tcp"'north', "method": "socket", "timeout": 35, "byteOrder": "BIG", "retries": true, "retryOnEmpty": true, "retryOnInvalid": true, "pollPeriod": 5000, "unitId" 'interface': '1.0', "deviceName": "UR5", "sendDataOnlyOnChange": true, "connectAttemptTimeMs": 5000, "connectAttemptCount": 5, "waitAfterFailedAttemptsMs": 300000, "timeseries": [ { "tag": "base_joint_temperature_deg_C", "type": "16int", "functionCode": 3, "objectsCount": 1, "address": 300 }, { "tag": "shoulder_joint_temperature_deg_C", "type": "16int", "functionCode": 3, "objectsCount": 1, "address": 301 }, { "tag": "base_joint_current_mA", "type": "16int", "functionCode": 3, "objectsCount": 1, "address": 290 }, { "tag": "shoulder_joint_current_mA", "type": "16int", "functionCode": 3, "objectsCount": 1, "address": 291 }, { "tag": "elbow_joint_current_mA", "type": "16int", "functionCode": 3, "objectsCount": 1, "address": 292 }, { "tag": "wrist1_joint_current_mA", "type": "16int", "functionCode": 3, "objectsCount": 1, "address": 293 }, { "tag": "wrist2_joint_current_mA", "type": "16int", "functionCode": 3, "objectsCount": 1, "address": 294 }, { "tag": "wrist3_joint_current_mA", "type" 'config': "16int", "functionCode": 3, "objectsCount": 1, "address": 295 } ] } ]_DEFAULT_CONFIG

def plugin_init(data): _LOGGER.info('Initializing ThingsBoard North Python Plugin') global thingsboard_north, config thingsboard_north = ThingsBoardNorthPlugin() config = data _LOGGER.info(f'config = {config}') return config """Example of payload [{'reading': {'base_joint_temperature_deg_C': 34, 'base_joint_current_mA': 2042}, 'asset_code': 'Modbus TCP', 'id': 35613, 'ts': '2023-02-22 16:33:49.961000+00:00', 'user_ts': '2023-02-22 16:33:47.126849+00:00'}, {'reading': {'base_joint_temperature_deg_C': 34, 'base_joint_current_mA': 2045}, 'asset_code': 'Modbus TCP', 'id': 35614, 'ts': '2023-02-22 16:33:49.961000+00:00', 'user_ts': '2023-02-22 16:33:48.126817+00:00'}, {'reading': {'base_joint_temperature_deg_C': 34, 'base_joint_current_mA': 2060}, 'asset_code': 'Modbus TCP', 'id': 35615, 'ts': '2023-02-22 16:33:49.961000+00:00', 'user_ts': '2023-02-22 16:33:49.126827+00:00'}] Example of upload mosquitto_pub -d -q 1 -h "$THINGSBOARD_HOST_NAME" -t "v1/devices/me/telemetry" -u "$ACCESS_TOKEN" -m '{"base_joint_temperature_deg_C":33}'"""async def plugin_send(data, payload, stream_id): try: _LOGGER.info(f'ThingsBoard North Python - plugin_send: {stream_id}') _LOGGER.info(f'data = {data}') _LOGGER.info(f'payload = {payload}') _LOGGER.info(f'host = {data["tb_iot_platform_host"]["value"]}') for reading in payload: _LOGGER.info(f'reading = {reading}') _LOGGER.info(f'reading[reading] = {reading["reading"]}') s = 'mosquitto_pub -d -q 1 -h "' + data["tb_iot_platform_host"]["value"] + '" -t "' + data["tb_mqtt_topic"]["value"] + '" -u "' + data["tb_device_access_token"]["value"] + '" -m \'' + str(reading["reading"]) + "\'" _LOGGER.info(f's = {s}') os.system(s) except asyncio.CancelledError as ex: _LOGGER.exception(f'Exception occurred in plugin_send: {ex}') else: _LOGGER.info('payload sent successfully') return True, payload[len(payload-1)]["id"], len(payload) def plugin_shutdown(data): pass # TODO: North plugin can not be reconfigured? (per callback mechanism)def plugin_reconfigure(): pass class ThingsBoardNorthPlugin(object): """ North ThingsBoard Plugin """  

 == Dashboards Visualization of uploaded data ==ThingsBoard IoT allows Similarly to create easily custom dashboards to visualize data. At what we did in [[http://ec2-15-160-47-190.euMISC-southTN-1.compute.amazonaws.com024:8080/dashboard/1178fb20Automated test equipment (ATE) monitoring with SBCSPG gateway and ThingsBoard IoT platform|''MISC-e56dTN-11ec-8592-e3cb29424137?publicId=28967df0-e56d-11ec-8592-e3cb29424137 this link024'']] such , we created a simple dashboard is available showing some temperatures and currents of to visualize in real-time on cloud side collected data as shown in the arm's jointsfollowing example.[[File:ATE monitoring SBCSPG ThingsBoard dashboard1-Fledge-8.png|center|thumb|600x600px|Visualization of uploaded data.]]