This is a template for the hands-on-lab description for IO3.
This document overviews a laboratory, not a scenario (hands-on lab).
Scenarios are in different document, see template here: [[en:iot-open:remotelab:templates:scenariotemplate]]
<note important>Use it as copy-paste. Do not edit this file, please!</note>
<note important>Italic text below should be replaced with yours. Italic text below is just to let you find out easily, what chapters are to be covered when creating a document - to distinguish from yours, regular text.</note>
<note warning>Paragraphs below (in regular, non-italic) should be left as is, eventually adapted if necessary. Project information section should be left as is.</note>

Everything above this line (and including this line) is to be removed in the final version.


===== [Laboratory name] =====
//Give an information, where laboratory is located (partner name) and very short description (like one sentence).//

==== Introduction  ====
//Here provide some general idea of the laboratory. Do not use very complicated phrases. It is to be understood by people with limited understanding of the technology. Photos, schematic and drawings may be attached as well.
Write objectives for the laboratory i.e. "its purpose is to model ...." or "simulate", or simply to "practice". Write some objectives. Provide a link to the live video stream (if any).//

==== Prerequisites ====
//Describe prerequisite readings, software, hardware (if any) - note - only those that apply to ALL scenarios, knowledge necessary to understand. I case single scenario requires some extra knowledge/prerequisites, provide it with scenario document, not here.//

==== Technical details ====
//Provide technical details on the construction of the laboratory, both hardware, and software. Use technical words and sentences. It is to be understood by technology-related people. Consider it as a kind of laboratory hardware and eventually software implementation. Sections below (remove section if not present) present details. Provide circuit, essential mechanical schema, if necessary to use the laboratory and understand its physics/mechanics, etc.//

=== Sensors ===
//Describe sensors (if any). Provide details on measured values, connection details, accuracy, protocols, its relation to the physical/mechanical part of the laboratory (if any). Add photos and schematics, where the sensor is located. In case the sensor is virtual, do not expose it - present as physical until it is essential to know it regarding study (i.e. code implementation, timings, etc.). Provide links to external resources regarding i.e. necessary libraries, protocol definition, etc.//

=== Actuators ===
//Describe actuators, their impact on the physical/mechanical part of the laboratory device, limits, connections, etc. Add photos and schematics, where the actuator is located. In case actuator is virtual, do not expose it - present as physical until it is essential to know it regarding study (i.e. code implementation, timings, etc.). Provide links to external resources regarding i.e. necessary libraries, protocol definition, etc.//

=== Software, libraries and externals ===
//Provide a list of software, software libraries and external resources (i.e. files) necessary during code development. Please note, write here only common for all hands-on-labs scenarios (there is a relevant section in scenario template. Remove this section if empty.//

=== Communication ===
//Describe communication if it is implemented and sealed (not intended to be implemented by students, or provided i.e. as default code). Present data flow. Describe protocols and details i.e. key-value pairs, etc. Provide how exceptions are handled.//

=== Limits ===
//Provide information about limits on usage, i.e. need for maintenance/service break, access mode (parallel, booking, etc.), manual mechanical reset, etc.//

==== Hands-on labs ====
//List study scenarios (hands-on labs), linking to the Dokuwiki pages with hands-on labs descriptions (there should be a separate page for each scenario). Classify each scenario and refer to the target group using starting keywords:
  * Beginners
  * Undergraduates
  * Masters
  * Professionals
Note, assume that more professional group automatically contains less professional ones. Note - use language and as appropriate to the target group, i.e.://
<code>
  * Beginners: Elementary operations on the Arduino 2x16 LCD screen.
  * Undergraduates: Visualizing temperature and humidity on the remote screen.
  * Masters: Using power saving states to limit power consumption.
</code>
==== Support ====
//Give some information on how to access help, how to get support in case of the trouble etc.//