A lot of developers think an Arduino project is just software. WRONG.
If you approach it any other way, you’ll inevitably come to an the conclusion.
SOFTWARE NEEDS HARDWARE!
Even with a simple text-only serial project, you need consider how you’re powering the project.
These tips assume you’re using a pre-built processor module. If you’re making your own, there are extra things to consider.
As soon as you plug anything into ANY of the header pins, you’re entering a new world.
FIRST, the Arduino isn’t a power supply for anything but minimal small sensors or LEDs.
A servo, high power LEDs or lamps, motors or relays - almost always require additional external power to support the extra voltages and/or current needed by the extra hardware.
SECOND, you must be aware of ground and other voltages that are used by your circuit. Arduinos NEVER allow negative voltages on any pin.
Connecting 0V/ Ground connections across your project is almost always a good idea.
A simple understanding of voltage and/or potential difference is a good thing.
THIRD: once you have #1 above sorted, the processor can only ‘drive’ very little CURRENT. Perhaps 20-40 milliamps at most from a pin or group of pins… this is not much ! A motor, or relay will want 10-50 times that amount of current. To handle these, you’ll need a driver of some sort. That could be a small transistor, or larger, like a stepper controller scaled to the motor you’re planning to use.
The bottom line is SOFTWARE NEEDS HARDWARE! there’s no getting around it.
If your hardware doesn’t work, the software never will.
Not a valid reference.
Simulation is NOT your project, it’s a fragile sandbox that won’t turn your motors, send an SMS or perform any real world actions.
Maybe if you’re offering Hardware-as-a- Service, that should be discussed in a new thread,
Imperfect, indeed. There have been instances where we have seen issues with simulators*. It usually happens that we are several posts of time wasted in before we find out that a sim is involved
** mostly TikerCad
I think that the forum guideline should have an instruction to specifically mention if a sim is used.
And did I lay claim to said project? Heck no!
It is an ever evolving project and I strongly suspect it may be capable of more peripheral soon; but I am not privledged to any timelines.
But back to my original response to the thread's author:
It is highly advantageous to have real hardware on the bench when a programmer writes code. But, using creatitivity, intellect, consulting hardware technical manuals, and avoiding stupidity and human PROPENSITY for creating accidents, hardware is not necessary to write software.
What is necessary is to have hardware available to do compliance testing and acceptance testing.
Having hardware available is a nicety not a necessity and this is the common way that industry works. This is why SpaceX launchs test rockets and does static firings. It is why the experimental pilot flies a new jet design. It is why Uncle Sam blew up an atomic bomb in the desert during the Manhattan Project.
Imagine a programmer saying: "Boss, I cannot write that safety interlock code unless I have the nuclear safeguard hardware on my desk."
Boss says, "You are fired pathetic little programmer." "Next applicant."
No, I did.
The o original post specifically mentioned the word PROJECT several times.
I have seen your contributions to the forum, and respect your demonstrated experience.
This
Absolutely, and I congratulate beginners that try to learn and experience code. development in a simulation.
What works in a. simulator might not (probably not) work in the real world that involves power supplies, drivers etc.
I did say… As soon as you plug anything into ANY of the header pins, you’re entering a new world.
