- We often ask questions before offering solutions.
Please respond with the appropriate information requested.
- Questioners know what their hardware and software looks like but the volunteers here do not. You need to fully explain what’s not working, and how it is supposed to work.
- Before asking your questions, please read all the posting guidelines, follow these guidelines when you post your questions.
Hardware
- Schematic diagrams are the universal language of electronics.
- We use schematics to communicate hardware design. All components and connections are illustrated.
- As always, show us a good schematic of your proposed circuit. Hand drawn schematics are acceptable.
- Show us several good image views of your actual wiring.
- Give WEB links to your major components.
Software
- For readability, place { and } on separate lines by themselves, place each line of code on a separate line.
- In the Arduino IDE, use Ctrl T or CMD T to format your code, then copy the complete sketch.
- Use the < CODE / > icon from the ‘posting menu’ to attach your copied sketch
- Examining a variable for HIGH/LOW or true/false makes your code very difficult to follow.
- Avoid magic numbers in your sketches.
- Something like this documents your code for you and tells others what is happening:
#define ENABLED true
#define DISABLED false
//
#define CW 0xB847FF00
#define CCW 0xB847FFA3
//
#define LEDon HIGH
#define LEDoff LOW
//
#define PRESSED HIGH
#define RELEASED LOW
- When you follow the posting guidelines, volunteers can be more effective.
- When we have a schematic we can speak the schematic language in helping you.
- More volunteers will help when you properly post your questions.
Homework
Some elements will be above where you are now, they will make sense in the future.