| Note |
|---|
The documentation for SolidSense software is not maintained by SolidRun and the information herein is not actual with the latest version of the software, please contact our partner SolidSense Connect who is now developing the SolidSense software. Here is the Solidsense-Connect WiKi (documentation page) |
Prerequisite and installation
...
The Wirepas are connected to the CPU via UART. Here is the device mapping
Gateway type | Sink 1 | Sink 2 |
|---|---|---|
N6 Indoor | /dev/ttymxc1 | /dev/ttymxc2 |
N6 Outdoor | /dev/ttymxc1 | /dev/ttymxc2 |
N6 Industrial | /dev/ttymxc1 | /dev/ttymxc2 |
N8 Compact | /dev/ttymxc3 | N/A |
Specific installation steps
...
If the Wirepas configuration services do not appear on the Kura interface, then the following step have to be applied:
Download the Wirepas sample configuration file. This can be done either on your PC or directly from the gateway.
Copy the file in /data/solidsense/config/SolidSense-conf-custom.yml. That file can be edited first so you can directly enter your parameters. Otherwise you can always program them via Kura/Kapua
Restart the gateway for reconfiguration (being su) /opt/SolidSense/bin/restart –config. Warning all network parameters will fall back to factory default.
Exemple using ssh directly on the gateway connected to Internet
...
Up to 3 communication channels, working simultaneously, can be configured via the Wirepas Data Configuration screen in Kura:
Main MQTT transport
Optional MQTT transport
Local micro service on gRPC
...
Each MQTT transport has the following configuration items
...
The sink service ensure the communication with the Wirepas software running on the Nordic chips. This a systemd service that is automatically started when configured. There are 2 services:
wirepasSink1 for the sink#1 (/dev/ttymxc1)
wirepasSink2 for the sink#2 (/dev/ttymxc2)
After the Sink(s) is (are) configured the gateway is connected to the Sink and as soon the data transport is configured the data are sent to the MQTT broker(s)
...