Microcontrollers > Data Logging

Arduino for beginners

(1/8) > >>

Bruce S:
I'm starting this post so that people like OperaHouse and DamonHD can assist people like me who can fix darn near anything, but are keyboard afflicted when it comes to coding.

It's not that it's hard, but there seems to be so many different ways to do things.
Here's a link to one of the websites I now go to when I get overwhelmed with all the different possibilities. I know it's dated but it help me.
https://makezine.com/2014/01/06/skill-builder-arduino-101/

This is the original site for all things Arduino
https://www.arduino.cc/

At one time I thought I had doing these solidly in my mindset,,,, but then while trying to get a handle on bigger projects I got lost.

I am time limited for now so if someone wants to post links to some of OperaHouse's stuff and other who've posted their code that  would be awesome.

Cheers
Bruce S

JW:
Here's a thread on another forum I started today about Arduino.

https://steamautomobile.com:8443/ForuM/read.php?1,26164

Worth checking out.

 

SparWeb:
Thanks Bruce.
I'm in the middle of a complicated Arduino project myself (500 lines of code so far).

I'm frequently jumping to the Arduino reference page: https://www.arduino.cc/en/Reference/HomePage

Surprisingly, it is not a comprehensive list of all commands that are supported by any vanilla Arduino.
I've discovered many other commands that run on the Uno and Mega.  They help simplify coding and make clunky code run better.
My latest discovery is this command:  dtostrf() which cleans up the format of numbers to display neatly on LCD's or serial output.

I visit these often:
https://forum.arduino.cc/index.php?board=4.0
http://www.electro-tech-online.com/forums/arduino/

I also have a (secret) crush on Lada Ada:
http://ladyada.net/make/index.html
 :D

OperaHouse:
One secret is to create a boilerplate program with the general things you need.  If you don't program all the time you will have a heck of a time remembering what things go where in the standard setup of a program. I hate doing this overhead stuff and like getting straight to the actual program logic.

I'm not sure this is a secret, but it is always your fault.  Just accept that and don't get frustrated.  Come back to it the next day.  I still see things that stump me.  The other day I changed just a couple lines of code and got the strangest result. Did a Serialprintln ( " B ");. What printed out was 5482 and no B.  I have a habit of hitting some wrong keys sometimes and I believe non printable characters are entered.  I can comment out the line and retype the same thing.  That will work.  If you are used to quickly scanning reading material, you will have a lot of problems proof reading your code.

SparWeb:
Something I wrote recently about programming in another thread, that also belongs here:


--- Quote ---...Another thing I did was to write pseudocode before trying to write the code itself (my teachers from long ago would be so proud).
This helped a lot to figure out the program flow - even I was surprised.
Writing pseudocode kept me from bogging down in the syntax of commands, and explained in plain language what I wanted the program to do.
--- End quote ---

Navigation

[0] Message Index

[#] Next page

Go to full version