Differences

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

--- oak:tutorials:ultrasonic [2016/07/29 16:42]
brohan
+++ oak:tutorials:ultrasonic [2017/01/10 00:04]
Rover#18 [Components] cross-referencing to tutorial for HC-SR04
@@ Line 1: / Line 1: @@
 ===== Oak: Using an Ultrasonic Sensor=====
-** Currently a Work in Progress **
@@ Line 7: / Line 5: @@
 {{http://digistump.com/wiki/_media/oak/tutorials/us-100_ultrasonic_2.png?500}}
-In this lesson, we will connect an ultrasonic sensor to the Oak. An ultrasonic sensor, using the properties of sound, not only detect an object, but also how far away the object is. The sensor generates a high frequency sound, then listens to the echo received back to the sensor. The time interval from send to receive allows you to calculate the distance.
+In this lesson, we will connect an ultrasonic sensor to the Oak. An ultrasonic sensor, using the properties of sound, not only detects an object, but also detects how far away the object is. The sensor generates a high frequency sound, then listens for an echo received back to the sensor. The time interval from send to receive allows you to calculate the distance.
 ===== Components =====
@@ Line 18: / Line 16: @@
-**Note:** The HC-SR04 sensor is __**NOT**__ being used in this tutorial as it uses 5v. Instead a US-100 sensor, which operates from 3v - 5v is used.
+**Note:** The HC-SR04 sensor is __**NOT**__ being used in this tutorial as it uses 5v. Instead a US-100 sensor, which operates from 3v - 5v is used.  However, two methods for connecting the more common HC-SR04 range sensor are provided in a separate tutorial, [[https://digistump.com/wiki/oak/tutorials/ultrasonic_2|here]].
-Particle.publish will be used to send the sensor data to the cloud. To view the data, you will need a free Particle account, which you can get here if you done have one already: [[https://build.particle.io/signup]].
+Particle.publish will be used to send the sensor data to the cloud. To view the data, you will need your free Particle account. You most likely created one when you first set up your Oak. If you don't have one already get yours here: [[https://build.particle.io/signup]].
 ===== Concepts =====
-=== pulseIn ===
+==== pulseIn ====
-===Particle.publish ===
+pulseIn() can be thought of as a specific timer. pulseIn() takes at least 2 parameters, and up to 3, which are: pin, HIGH or LOW, and timeout. pulseIn() reads the pulse width value for the designated pin during a signal HIGH or LOW condition (designated by the state parameter). Pulse width value is the length of time the pin’s voltage remains HIGH or LOW.
+For example, when the state parameter is set to HIGH, the pulseIn() function waits for the pin’s voltage change to HIGH and measures the length of time the pin’s voltage remains HIGH until it changes to LOW. The length of time is measured in millisecond. The maximum pulse width is 71 minutes. If nothing is detected within the specified time-out period, the function abandons the read attempt and returns 0.
+==== Particle.publish ====
+The Particle.io cloud offers many features that Oak users can take advantage of, some of which are quite in depth, and allow various devices to "communicate" with each other by passing information (like Particle.variable). If you just need something simple, such as a notification when something has happened, Particle.publish() may be what your looking for.
+Particle.publish() can either be public (available to anyone who has the event name and uses Particle.subscribe) or private (only visible to you, your devices, etc).
+Particle.publish() takes the name of the event, the data (char or String), TTL (length of time the data is good for), and if its private.
@@ Line 116: / Line 124: @@
 </code>
+Now that we have our data, let's use it:
+<code>
+//Send distance to cloud for viewing by Particle dashboard, and OakTerm
+ sprintf(post_Distance, "%04d", Len_mm); //convert int to string for Particle.publish
+  Particle.publish("distance in mm:", post_Distance); //invoke Particle.publish
+/*
+Use onboard LED for visual feedback, adjust values based on what you see via Particle.publish
+Could attach an RGB LED to change colors based on distance
+*/
+ if((Len_mm < 3000) && (Len_mm > 1)) {   // Length effective range (1, 3000).
+digitalWrite(LEDPin, HIGH);
+ }
+ else {
+ digitalWrite(LEDPin, LOW);
+ }
+ delay(1000);
+}
+</code>
+Our setup in action:
 {{http://digistump.com/wiki/_media/oak/tutorials/ultrasonic.gif?200|
@@ Line 121: / Line 155: @@
 ===== Conclusion =====
+You did it. You properly connected, and used an ultrasonic sensor to your Oak, and sent the data to the cloud. Make sure that you log in, and visit your Oak's logs at [[https://dashboard.particle.io/user/devices]]. If you have registered multiple Oaks (why wouldn't you have more than one?), be sure to view the logs for the correct Oak.
+Look into other Particle functions at your disposal, such as Particle.variable, that allow you to post your variable, and even access it with another (read 2nd or 3rd oak) device.
+What can **you** use an ultrasonic sensor for?
+  * "eyes" to keep a robot from running into something
+  * Connect an RGB, put in your garage for a parking distance guide

Digistump Wiki

User Tools

Site Tools

Differences

Page Tools