This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:iot-open:remotelab:itt:efficiency [2018/10/29 20:43] – pczekalski | en:iot-open:remotelab:itt:efficiency [2020/07/20 09:00] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Production efficiency | + | ===== OLED screen module |
| - | Please | + | //Give an information, |
| - | Copy/paste it, then replace | + | |
| + | ==== 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 " | ||
| + | |||
| + | ==== 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/ | ||
| + | |||
| + | ==== 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/ | ||
| + | |||
| + | === Sensors === | ||
| + | //Describe sensors (if any). Provide details on measured values, connection details, accuracy, protocols, its relation to the physical/ | ||
| + | |||
| + | === Actuators === | ||
| + | //Describe actuators, their impact on the physical/ | ||
| + | |||
| + | === Software, libraries and externals === | ||
| + | //Provide a list of software, software libraries and external resources (i.e. files) necessary during code development. | ||
| + | |||
| + | === 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/ | ||
| + | |||
| + | ==== 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.:// | ||
| + | < | ||
| + | * 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.// | ||