Could someone help me to merge several working sketches.
1.-Distance measuring with ultrasonic sensor.
2.-Temperature with humidity sensor
3.-Reed relais using in pluviometer.
Goal is to write all this logs to one file on the sd card.
If someone i will sent the sketches.
Louis
If you want someone to do programming for you then you should ask in the Gigs and Collaborations section and be prepared to pay.
If you want to do it yourself this Simple Merge Demo may give you some ideas. The important thing is to eliminate multiple use of a resource - such as an I/O pin.
...R
. . . and, if any of the bits of code have made use of delay(), you may need to recode those sections to make the combined application usable.
It's difficult for me to understand why so much difficulty in merging sketches. I normally test each functionality in different sketches. While coming up with the final sketch I will combine all these pieces together in my final sketch.It's painful but not that difficult either.
sarouje:
It's difficult for me to understand why so much difficulty in merging sketches. I normally test each functionality in different sketches. While coming up with the final sketch I will combine all these pieces together in my final sketch.It's painful but not that difficult either.
For people who have some experience, understand the possible areas of conflict, and have a systematic approach, it is not difficult. That is correct. For others, the guideline mentioned in the posts above can help to get started.
Has someone don this. i would appreciatie to get an example with the separate sketches and the final merged sketch.
Louis
Has someone don this. i would appreciatie to get an example with the separate sketches and the final merged sketch.
Did you ever read @Robin2 's reply #1 ????
louisluyckxtelenetbe:
Has someone don this. i would appreciatie to get an example with the separate sketches and the final merged sketch.
See Reply #1
...R
supertechqc:
Robin2 and rpt007 are only newbee haglers.
Please explain?
If you really want to be helpful to newbies why don't you post your code in this Forum.
IMHO, an 827 line example is not the sort of thing to encourage newbies.
Where did you get the idea that "Eggspurts are still recommending resistance" - please provide a link to the evidence.
You may note, elsewhere, that many people (including me) recommend AGAINST using delay().
...R
John, why are you being such a douche? Is your code written to make newbies feel like they can never understand Arduino programming? Someone new to the way Arduino works doesn't get most of what you have written. If they learn to read a low-side switch using a resistor, then it's a no-brainer when the learn about INPUT_PULLUP. If you just push it on them, it's merely an incantation.
Perhaps YOU should read and study Robin's merge demo. THAT is how you write a tutorial. Take the time to understand how learning happens, rather than just writing a complex program to fan you ego.
supertechqc:
This is your lucky day!!!I have designed a menu driven program that can hold up to ten (10) TEN sketches.
Circuit uses a 16x2 lcd with an I2C interface, a 20Kohm pot, switches, and an led board. (<$20)
Also at power up, the program sends the file name of the program and the lcd I2C address
to the serial monitor. GREAT for trouble shooting!!! Oh yeah, I also use the INPUT_PULLUP classification
so you don't have to use those stupid pull up resistors. (I can't believe Eggspurts are still recommending resistance).
I don't think rpt007 has actually contributed anything for what its worth.
Here's my code at github: GitHub - mrjohnposton/Arduino: Arduino Code Projects
Showing off some thing you did will not help any one and in particular a newbie. Here all of us trying to help each other.
From @supertechqc opus magnus
void readSwitches(){ //Evaluates the States of the four Switches
swAval = digitalRead(swA);
swBval = digitalRead(swB);
//delay(300);
}
Four switches?
The purpose of this file is to have many sketches run on one program.
Nonsense
The core menu code would be, I estimate, about an eighth to a quarter the size it is, if function pointers and arrays were employed.
The RAM footprint of this sketch is also excessive.
And there's a subtle bug in "I2Cscan".
Your do this while (swBval == 1){ in each of your menus. It's pointless, you may as well just do while (1){
I can't recommend it as a good example of programming practice.
I also use the INPUT_PULLUP classification so you don't have to use those stupid pull up resistors. (I can't believe Eggspurts are still recommending resistance).
I have no idea what that means.
I have no idea what that means.
Our dear friend John is indeed an eggspurt.
It seems he doesn't understand that there are conditions (e.g. long wires which result in capacities which grow with the kind of cable and the distance) when internal pullups are no good idea because they will simply fail.
That's the time when external pullups come into play.
Whenever short distances are given, I also prefer to use the internal pullup resistors as they save devices, space and add'tl wiring