Please follow the below link for the unedited preview:
http://www.allaboutcircuits.com/projects-preview/1172
All feedback greatly appreciated.
http://www.allaboutcircuits.com/projects-preview/1172
All feedback greatly appreciated.
You'd also need a solderless breadboard...Hardware
- 1 x Arduino Uno
- 1 x DHT11 temperature sensor
- 1 x 1k Ohm resistor
- Jumper Wires
This will definitely work. The debate on whether the variables should be declared on setup or loop (which are not essentially different procedures, priviledge-wise) is one on compiler and memory access efficiency.Two comments: first, for readability the list of steps at the end of the article should appear much earlier, probably just before the circuit diagram.
Second, I'm only starting to learn C programming (after 40 years working in assembly language!), but something looks fishy to me: in the code, the two lines in the loop() procedure that say,
// two float type variables to read temperature and humidity
float humidity = dht.getHumidity();
float temperature = dht.getTemperature();
appear to be declaring the two variables and assigning them a value. Is this kosher? I would think it would at least make the code more readable if
// two float type variables to read temperature and humidity
float humidity;
float temperature;
were written above the Setup() procedure, right after
DHT dht;
and then, in the loop() procedure, replace the existing two lines with
humidity = dht.getHumidity();
temperature = dht.getTemperature();
In my view, that would make the code easier to read. If I'm all wet on this, feel free to ignore...
When referring to github libraries, I think it's a good idea to fork the material to a personal repository, just to be sure that it will always be there but also refer to the original, for the sake of updates and reference.Nit-picking...
You'd also need a solderless breadboard...
I do not like when you must download libraries from an external site. What if the site goes down? What if Mark Ruys deletes his account at github.
Some time ago ACC encourage members to host pictures locally, I think libraries also should be stored locally.
IMO, "light" is an understatement: so far, none of the Project articles posted has more than a bare minimum of explanation, whether about how the hardware operates or about what's going on in the code. Many opportunities for education are missed and IMO that's a shame.Once you get beyond your introductory material, the content gets light.
Users who are already familiar with the Arduino IDE would recognize this as the IDE's built-in Serial Monitor, but for those who are not it should always be identified as such.The results section could have a little more meat on its bones. At a minimum, I'd like to see which serial monitor is being used, by explaining in a couple of words where it is? Otherwise I'd might use Putty .
Thanks. I figured the compiler would probably be forgiving of that form. It's just jarring (to me, anyway) to see declarations popping up in the middle of executable code, as I was taught they should always be up top.This will definitely work. The debate on whether the variables should be declared on setup or loop (which are not essentially different procedures, priviledge-wise) is one on compiler and memory access efficiency.
As someone who is primarily a hardware jockey, except for some assembly language code developed on one-man (i.e., me) projects, I would have no idea whatsoever what that means.When referring to github libraries, I think it's a good idea to fork the material to a personal repository...
Think of this declaration as a worse case of:Thanks. I figured the compiler would probably be forgiving of that form. It's just jarring (to me, anyway) to see declarations popping up in the middle of executable code, as I was taught they should always be up top.
As someone who is primarily a hardware jockey, except for some assembly language code developed on one-man (i.e., me) projects, I would have no idea whatsoever what that means.
I see github referred to a lot; is there any explanatory material online on how it works and how to use it, written for n00bs like me?
for (int i; i<MAX; i++) {
do stuff...
}
Sadly, such informality (deviance?) has, increasingly, become 'the order of the day' in 'micro-controller land'It's just jarring (to me, anyway) to see declarations popping up in the middle of executable code
I think declaration in running code is a pain in the ...Thanks. I figured the compiler would probably be forgiving of that form. It's just jarring (to me, anyway) to see declarations popping up in the middle of executable code, as I was taught they should always be up top.
Good call! --- To this I would add (as regards construction articles in general) that it is imperative that all 'special' hardware is expected to be readily sourcable in small quantities for the foreseeable future...Under Arduino, library
add a statement that the link marked, "here" (Arduino Playground) includes information about where to get the unique sensor for this project.
My opinion: every semiconductor component used in a project-- whether diode, or BJT, or MOSFET, or IC-- should have a link to its datasheet as well as a link to at least one hobbyist-friendly source.Good call! --- To this I would add (as regards construction articles in general) that it is imperative that all 'special' hardware is expected to be readily sourcable in small quantities for the foreseeable future...
Just paying attention to what I normally do. I'm a precision analog designer. I couldn't use an Arduino to count my fingers, but I know that, "A part you can't find is every bit as good as a part you don't have."Good call! --- To this I would add (as regards construction articles in general) that it is imperative that all 'special' hardware is expected to be readily sourcable in small quantities for the foreseeable future...
TTFN
HP
Just out of curiosity, did you read this article before you posted the link to it?Please follow the below link for the unedited preview:
http://www.allaboutcircuits.com/projects-preview/1172
All feedback greatly appreciated.
It's actually even worse for me if I have something and can't find it. If I don't have it, I may buy it, but if I know I already have one, I'm too tight to buy another one.Just paying attention to what I normally do. I'm a precision analog designer. I couldn't use an Arduino to count my fingers, but I know that, "A part you can't find is every bit as good as a part you don't have."
That's one of my, "old sayings" that I invented...right after screaming at my nephew about cleaning up after work.
by Duane Benson
by Duane Benson
by Duane Benson