Versions Compared

Old Version 6

changes.mady.by.user Marcos Moreno

Saved on

compared with

New Version Current

changes.mady.by.user Carsten Fenneker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Section


Column
width500px

ARTIK Forums


Column
width400px


Panel
borderColorlightgrey
bgColor#f0f0f0
titleOn this page:

Table of Contents



...

This document will describe the Initial setup of Site Controller on an Samsung Artik board running Fedora 24. The steps are also valid for the Krita 520 platform (see troubleshooting steps to avoid limitations if they are still there when you use the platform).

Prerequisites

You will need to know the IP of the system and to have access via ssh.

...

Warning

Current SiteController version (1.3.7) does not automatically install the SiteController as service on Fedora. This means it will not be auto started on boot up. To do so follow this steps:

  1. Download the file SiteController and transfer it to the gateway

  2. Copy it to /etc/init.d

    Code Block
    languagebash
    [root@localhost ~]# cp SiteController /etc/init.d/


  3. Change the permissions to be able to execute it

    Code Block
    languagebash
    [root@localhost init.d]# chmod +x /etc/init.d/SiteController


  4. Install it as a service

    Code Block
    languagebash
    [root@localhost init.d]# systemctl enable SiteController



Starting the system

  1. Start the SiteController, it will start the mosquitto automatically if necessary 

    Code Block
    [root@localhost ~]# /opt/azeti/SiteController/run_SiteController.py start


    Tip

    Please stay 2 minutes in the terminal after the start of the site controller. If there is a problem in the system the modules will launch an exception. If no exception came in 2 minutes, the system is up and running with no issues.


  2. Once everything is started, you can use the following command to check that all modules are up and running:

    1. SiteController Status, note that required modules should be marked green and running

      Code Block
      [root@localhost SiteController]# ./run_SiteController.py status
Time zone set to: Etc/UTC
Serial of this installation: Samsung_Artik_7
Main version of this installation: 1.3.6
Host type: Unknown
External Broker set to: cloud-master.azeti.net:1883, TLS disabled
Connection to External Broker established.
OK: Integrity check passed.
OK: Module mosquitto is running with PID (13755)
OK: Module Watchdog.py is running with PID (13777)
OK: Module data_store.py is running with PID (13765)
OK: Module JobProcessor.py is running with PID (13790)
OK: Module ConfigProvider.py is running with PID (13771)
OK: Module RawResultsDeMux.py is running with PID (13791)
OK: Module CalibResultsEvaluator.py is running with PID (13761)
OK: Module virtual_sensor_provider.py is running with PID (13813)
WARNING: Module VS_fill_quantity.py is not running.
WARNING: Module VS_flow_rate.py is not running.
WARNING: Module VS_tank_simulator.py is not running.
WARNING: Module VS_access_control.py is not running.
WARNING: Module VS_battery_details.py is not running.
WARNING: Module VS_HistoryAnalyser.py is not running.
WARNING: Module VS_filesize.py is not running.


  3. Once the system is up and running, and if no errors are appearing in your command line or in the logs, you can proceed to delete the installation compressed files and uncompressed folders to save space in the device. 

Troubleshooting

Kitra 520 platform

In the current Kitra 520 platform, you have just 512 MB of memory and no swap. /tmp is also limited in space. 

...