ExternalVendorCode/OpenMTC
1
0
Fork 0
mirror of https://github.com/OpenMTC/OpenMTC.git synced 2025-01-30 15:43:51 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

fix broken links

Browse Source
This commit is contained in:
Ronald Steinke 2018-06-18 14:57:40 +02:00
parent 71e6b5c175
commit 0597cc409b
1 changed files with 12 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/training/training-index.md
View File

@ -2,14 +2,14 @@
## Introduction ## Introduction
OpenMTC is delivered with some incremental demo applications which can be consulted for further understanding or as template for other applications. The oneM2M demo applications can be found in [/doc/training/apps/onem2m/](/doc/training/apps/onem2m/). OpenMTC is delivered with some incremental demo applications which can be consulted for further understanding or as template for other applications. The oneM2M demo applications can be found in the [OpenMTC Repository on Github](https://github.com/OpenMTC/OpenMTC/tree/master/doc/training/apps/onem2m).
The training is subdivided into examples for GUI-applications and IPE-applications. Both of these provide incremental demo applications for either sensor-actuator-applications or only sensor-applications. These are explained in the following sections. The training is subdivided into examples for GUI-applications and IPE-applications. Both of these provide incremental demo applications for either sensor-actuator-applications or only sensor-applications. These are explained in the following sections.
## The start-app Script ## The start-app Script
The [training folder](/doc/training) contains the [start-app.sh](/doc/training/start-app.sh) script. This script allows to run one of the four complete demo applications: The [training folder](https://github.com/OpenMTC/OpenMTC/tree/master/doc/training) contains the [start-app.sh](https://github.com/OpenMTC/OpenMTC/blob/master/doc/training/start-app.sh) script. This script allows to run one of the four complete demo applications:
```sh ```sh
user@host:/git$ ./openmtc-open-source/doc/training/start-app.sh user@host:/git$ ./openmtc-open-source/doc/training/start-app.sh
@ -82,7 +82,7 @@ To run the sensor-actuator demo application, you will also need four consoles. P
IPE stands for Interworking Proxy Application Entity. The IPE demo applications attaches (virtual) sensors and (virtual) actuators to the CSE by sending (simulated) sensors readings and receiving and processing commands meant for (virtual) actuators attached to the hardware this IPE demo app is running on. IPE stands for Interworking Proxy Application Entity. The IPE demo applications attaches (virtual) sensors and (virtual) actuators to the CSE by sending (simulated) sensors readings and receiving and processing commands meant for (virtual) actuators attached to the hardware this IPE demo app is running on.
The [IPE demo applications](/doc/training/apps/onem2m/ipe/) are available as sensor-actuator-applications or only as sensor-applications. The [IPE demo applications](https://github.com/OpenMTC/OpenMTC/tree/master/doc/training/apps/onem2m/ipe) are available as sensor-actuator-applications or only as sensor-applications.
**Incremental IPE demo applications** **Incremental IPE demo applications**
* [ipe-sensors](training-ipe-sensors.md) provides virtual sensors * [ipe-sensors](training-ipe-sensors.md) provides virtual sensors
@ -93,9 +93,8 @@ The [IPE demo applications](/doc/training/apps/onem2m/ipe/) are available as sen
GUI stands for Graphical User Interface. This is somewhat misleading, as these demo apps do not provide a real GUI. These GUI demo applications rather provide a textual user interface which receives (and eventually displays to the user) the (virtual) sensor data provided by the ipe-demo-apps. Further, they send commands to the (virtual) actuators attached to the ipe-demo-apps. GUI stands for Graphical User Interface. This is somewhat misleading, as these demo apps do not provide a real GUI. These GUI demo applications rather provide a textual user interface which receives (and eventually displays to the user) the (virtual) sensor data provided by the ipe-demo-apps. Further, they send commands to the (virtual) actuators attached to the ipe-demo-apps.
The [gui demo applications](/doc/training/apps/onem2m/gui/) are available as sensor-actuator-applications or only as sensor-applications. The [GUI demo applications](https://github.com/OpenMTC/OpenMTC/tree/master/doc/training/apps/onem2m/gui) are available as sensor-actuator-applications or only as sensor-applications.
**Incremental GUI demo applications** **Incremental GUI demo applications**
* [GUI-sensors](training-gui-sensors.md) receives and displays sensor data * [GUI-sensors](training-gui-sensors.md) receives and displays sensor data
* [GUI-sensors-actuators](training-gui-sensors-actuators.md) receives and displays sensor data and issues commands to actuators * [GUI-sensors-actuators](training-gui-sensors-actuators.md) receives and displays sensor data and issues commands to actuators