Bureaucrats, dave_user, Administrators
4,650
edits
Changes
no edit summary
The edge device is the [[MISC-TN-004:_Running_Debian_(armbian)_on_SBCSPG#The_hardware_platform|SBCSPG gateway]] running Debian Bullseye. To deploy this distribution onto the target, the same approach described [[ORCA-TN-001_—_Running_Armbian_Bullseye_(Debian_11)|here]] was used. Unlike Orca SBC, SBCSPG is based on a 32-bit ARM Cortex-A7 processor, though. As such, a [https://mirrors.dotsrc.org/armbian-dl/tritium-h3/archive/Armbian_22.11.1_Tritium-h3_bullseye_current_5.15.80_minimal.img.xz different image] was used.
To install Fledge, the <code>apt</code>-based approach described [https://fledge-iot.readthedocs.io/en/latest/quick_start/installing.html here] was followed. It is worth to remember that some dependencies were handled manually. For instance, <code>autoconf</code> and <code>libtool</code> packages were installed manually.
===Enabling the connection to the PLC===
As described in MISC-TN-024, the PLC is connected to a different subnet, namely 192.168.30.0/24. To test 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.
<pre class="board-terminal">
root@sbcspg:/usr/local/fledge/python/fledge/plugins/north# ip addr add 192.168.30.253/24 dev eth0 label eth0:1
root@sbcspg:/usr/local/fledge/python/fledge/plugins/north# history | grep mosq
205 history | grep mosq