Differences

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

Link to this comparison view

Next revision
Previous revision
en:iot-open:remotelab:itt:servo [2018/11/15 06:21] – created rim.puksen:iot-open:remotelab:itt:servo [2020/07/20 09:00] (current) – external edit 127.0.0.1
Line 1: Line 1:
-===== Servo module ===== +===== ITT Servo module ===== 
-//Give an information, where laboratory is located (partner name) and very short description (like one sentence).//+This laboratory is located in the office of ITT Group in Tallinn, Estonia.
  
 ==== Introduction  ==== ==== 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+This laboratory can be used to practice controlling the servo motor attached to the controller
-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).//+ 
 +{{:en:iot:examples:servopicture2.jpg?300|}}
  
 ==== Prerequisites ==== ==== Prerequisites ====
-//Describe prerequisite readingssoftware, hardware (if any) - note - only those that apply to ALL scenarios, knowledge necessary to understand. I case single scenario requires some extra knowledge/prerequisitesprovide it with scenario documentnot here.//+For this laboratorythe student should understand basic MQTT concepts like topicsbrokersubscribing and publishing.
  
 ==== Technical details ==== ==== 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.//+This laboratory consists of a servo with the add-on module attached to the ITT IoT controller module
  
 === Sensors === === 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.//+This laboratory does not have any sensors.
  
-=== Actuators === +=== Specifications === 
-//Describe actuatorstheir impact on the physical/mechanical part of the laboratory devicelimitsconnectionsetc. Add photos and schematicswhere the actuator is located. In case actuator is virtualdo not expose it present as physical until it is essential to know it regarding study (i.ecode implementation, timings, etc.). Provide links to external resources regarding i.e. necessary libraries, protocol definition, etc.//+<table Ref.Tab.1.1> 
 +<caption>Servo specifications</caption> 
 +^ Specification ^ Value ^ 
 +| Speed at 6V | 0,07 sec/60°| 
 +| Stall torque at 6V | 0,042 N-m | 
 +| Speed at 4,8V | 0,09 sec/60°| 
 +| Stall torque at 4,8V | 0,028 N-m | 
 +</table> 
 + 
 +=== Electrical connection === 
 + 
 +The signal lead of the servo is connected to D3 pin of the controller.
  
 === Software, libraries and externals === === 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.//+  * ITTIoT libary - used to program the controller module. 
 +  * Servo libary used to control the servo.
  
 === Communication === === 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.//+The user can connect and program this controller using the Distancelab environment.
  
 === Limits === === Limits ===
-//Provide information about limits on usagei.eneed for maintenance/service break, access mode (parallel, booking, etc.), manual mechanical reset, etc.//+At the same timeonly one user can program the controllerBut all users connected to the Distancelab MQTT broker can subscribe and publish to topics specified.
  
 ==== Hands-on labs ==== ==== 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 +=== Example code === 
-  * Undergraduates + 
-  * Masters +<code c> 
-  * Professionals +/
-Note, assume that more professional group automatically contains less professional onesNote - use language and as appropriate to the target group, i.e.:// + * IoT Servo example 
-<code> + * 
-  * Beginners: Elementary operations on the Arduino 2x16 LCD screen+ * This example subscribe to the "servo" topic. When a message received, then it 
-  * Undergraduates: Visualizing temperature and humidity on the remote screen+ * change servo position 
-  * Masters: Using power saving states to limit power consumption.+ * 
 + * Created 11 Sept 2017 by Heiko Pikner 
 + */ 
 + 
 +#include <Arduino.h> 
 +#include <Servo.h> 
 +#include <ittiot.h> 
 + 
 +//Pin definition for the Servo (D3) 
 +#define SERVO_PIN            D3 
 + 
 +Servo myservo;  // create servo object to control a servo 
 + 
 +// Change the servo position (value between 0 and 180) 
 +// mosquitto_pub -u test -P test -t "RL/esp-{ESP-ID}/servo" -m "51"  
 +// = this calls servo motor to change position  
 + 
 +void iot_received(String topic, String msg) 
 +
 +  Serial.print("MSG FROM USER callback, topic"); 
 +  Serial.print(topic); 
 +  Serial.print(" payload: "); 
 +  Serial.println(msg); 
 + 
 +  Serial.print("Servo: "); 
 +  Serial.println(msg); 
 + 
 +  myservo.write(msg.toInt()); 
 +
 + 
 +// Function started after the connection to the server is established 
 +void iot_connected() 
 +{ 
 +  Serial.println("MQTT connected callback"); 
 +  // Subscribe to the topic "servo" 
 +  iot.subscribe("servo"); 
 +  iot.log("IoT Servo example!"); 
 +
 + 
 +void setup() 
 +
 +  Serial.begin(115200); 
 +  Serial.println("Booting"); 
 + 
 +  // Print json config to serial 
 +  iot.printConfig(); 
 +  // Initialize IoT library 
 +  iot.setup(); 
 + 
 +  myservo.attach(SERVO_PIN); 
 +
 + 
 +void loop() 
 +
 +  // IoT behind the plan work, it should be periodically called 
 +  iot.handle(); 
 +  delay(200); 
 +
 </code> </code>
 +
 ==== Support ==== ==== Support ====
-//Give some information on how to access help, how to get support in case of the trouble etc.//+info@ittgroup.ee
  
en/iot-open/remotelab/itt/servo.1542262873.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