Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:iot-open:remotelab:sut:generalpurpose:b2 [2019/01/02 22:19] gdrabiken:iot-open:remotelab:sut:generalpurpose:b2 [2020/07/20 09:00] (current) – external edit 127.0.0.1
Line 1: Line 1:
-==== Controling flap position using servo ==== +==== B2: ==== 
-//Easy scenario. Students should move the flap in the lab//+//Give few words about this scenario. Provide some objectives and impact on the students.//
 === Target group === === Target group ===
-//This hands-on lab guide is intended for the Beginners.//+//This hands-on lab guide is intended for the Beginners/Undergraduates/Masters/Professionals. Choose appropriate.//
  
 === Prerequisites === === Prerequisites ===
-//Generally students need skill using servoFor realising scenariostudents need access to documentation for servo and understanding PWM control method.+//Provide prerequisite readings/hardware/software/software libraries/skills if other than stated in the Laboratory DescriptionIf noneremove along with the header. Please note some of those may be common for all scenarios (i.e. MQTT library), so provide it in the laboratory description level, not in the scenario level.//
  
 === Scenario === === Scenario ===
-//  - using schematic, check servo connection, +//Describe scenario to let the user understand its idea and process. Write information about the approachalgorithmetc(depends on the lab)Provide useful information about protocolsassumptions, addresses (i.e. communication servers), credentials, etc.//
-  - using ESP documentation check registers with PWM controling, +
-  - write the program which: +
-  * send value 0 as duty of PWM, +
-  * wait 15 seconds, +
-  * send value 50 as duty of PWM, +
-  * wait 15 seconds, +
-  * send value 100 as duty of PWM. +
-  - using the camera observe display flap position +
-  - You can use other wait time and value of dutybut wait time should allow observe effect by camera (against net lag) //+
  
 === Result === === Result ===
 +//Describe expected result when scenario is finished.//
  
 +=== Start ===
 +//Write starting conditions, i.e. what to do at the beginning, what to pay attention before beginning, how the mechanical part should look like,  etc.//
  
-//On display should be visible flap closed, middle position, full open.//+=== Steps === 
 +// Write some extra information if i.e. some steps are optional otherwise cancel this paragraph (but do not remove header).// 
 +== Step 1 == 
 +//Describe activities done in Step 1.//
  
-== === Start === == +...
- +
-//Check the start flap position.// +
- +
-=== Steps ===+
  
 +== Step n ==
 +//Describe activities done in Step n.//
  
 === Result validation === === Result validation ===
-Only way for validation is check flap position by camera.+//Provide some result validation methods, for self assesment.//
  
 === FAQ === === FAQ ===
en/iot-open/remotelab/sut/generalpurpose/b2.1546467583.txt.gz · Last modified: 2020/07/20 09:00 (external edit)
CC Attribution-Share Alike 4.0 International
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0