Versions Compared

Version Old Version 1 New Version Current
Changes made by

SolidRun

Yazan Shhady

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
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.

SolidSense OOB purpose and overview

...

With just some configurations using Kura the gateway can:

  1. Interface a Wirepas network with a cloud interface via MQTT

  2. Perform BLE operation either via a default BLE client or via Kura

  3. Manage the gateway configuration via Kura web interface

  4. Manage the cellular interface

  5. Develop visually application with Kura

  6. Connect to Kapua for supervision and data collection

  7. Manage software via Mender

  8. Develop additional Python 3 applications

  9. Run you Docker application containers

So that is a lot that you can already do on the basis of our standard image. However, to be in full control this image can be customized using our Yocto recipes that are available in our List of SolidSense software repository

SolidSense OOB Software roadmap

...

Download links for upgrades

SolidSense version 1.1a

Full eMMC flashing image

Mender upgrade artifact (Dual Core)

SolidSense version 2.0 Beta

Full eMMC flashing image

Mender upgrade artifact (Dual Core)

Upgrade constraints and recommendation

...

Upgrade from 1.1 to 2.0 needs a new Kura database, so by default all your settings will be lost and the new configuration will be the default one. To avoid that issue please create a provisioning file with your own default configuration. Configuration provisioning of the SolidSense gateways . The provisioning file is reapplied upon upgrade.

...

SolidSense gateways are delivered with 8Gb eMMC as hard disk with a specific partitioning to support all features. Here is the disk map implemented by the SolidSense image

Device

Purpose

Size

Mounted as

/dev/mmcblk2boot0

Boot

N/A

/dev/mmcblk2rpmb

RPMB

N/A

/dev/mmcblk2p1

ROFS Part a

1.5GB

/media/rfs/ro*

/dev/mmcblk2p2

ROFS Part b

1.5GB

/media/rfs/ro*

/dev/mmcblk2p3

Overlay FS

64MB

/media/rfs/rw

/dev/mmcblk2p4

Data

4.2GB

/data

Only one of the ROFS partitions is mounted as a given time. This the active partition containing the running read-only root file system. The partition not mounted is the backup one that can be used by Mender either to:

  1. Rollback to previous system in case of problems

  2. Download the new version in the background

The overlay file system is recording all changes made on the system and in particular all configuration changes. The interesting point is that the changes made in the configuration are surviving a root fs change required for an upgrade. On the other hand the overlay file system can be wiped out and the gateway restart like fresh from factory but with the latest installed release.

The Data partition is never directly impacted by upgrades and shall contain the stable part of the application. It can also be used to add additional features to the system. The following directories are created (and used by the system)

/data/solidsense

SolidSense configuration files. Can be extended by user

/data/docker

Docker sub-system files

/data/mender

Mender files (but not static configuration)

/data/u-boot

U boot environment

/data/.var/log

System log files (/var/log)

Application developers can add any additional directory in /data.