Search Results

As most other answers, I would go for method 2. But I would try to avoid the call, by Arduino library, to an an empty loop() that makes the Atmel consume "a lot" of current for nothing. Edit: As so …

One important problem in your code is concurrent access to dimming variable. That may not be the only problem you have though. Indeed, deeming is accessed for writing in your loop(), but it can be sim …

This variable is declared volatile which is generally meaning that it can be modified by an Interrupt Service Routine (ISR). So it is perfectly possible that this ISR gets called before your setup() …

Using an initialize() method to a class is contrary to the principle of a class constructor, i.e. once a class instance has been constructed, it should be "ready to use". As suggested by Ignacio's an …

It seems you have a problem of concurrent access to duration and pulsecount variables which are inter-related; with your code, it is possible that (and I guarantee that it will): loop() reads durati …

Here is a datasheet I found that seems a better macth for your display model (that's the datasheet for a display that I use): http://www.play-zone.ch/en/fileuploader/download/download/?d=1&file=custo …

I think the last expression is performed exclusively as an int expression and converted to long only at the end, i.e. before assignment to l. long l = buf[0] | (buf[1] << 8) | (buf[2] << 16) | (buf …

Another option in your situation is to not use String at all (which is preferrable for reasons I won't explain here) and exclusively use plain old C strings and their associated functions: // Define …

If you really want to recurse (and as @jippie said it is a bad idea; subliminal message: don't do it) and want to know how much you can recurse, then you will have to perform some calculation and exp …

The problem you have is that you never reset Timer1 counter (TCNT1) when you stop a note and then play another one. Also, changing the clock divider selection to "no clock" by clearing bits CS10 and …

In Modbus protocol, coils are bits and registers are 16-bit unsigned integers. Hence if you ask Modbus to read your au16data array as coils, and not as registers (which is what they actually are), th …

In C and in C++, #define is not an instruction of the language, but a directive of the pre-processor. What it does is define a "macro" which will be replaced everywhere it appears later on in the sou …

From what I guess in your code, here is how you want your class declared: class Habitaculo { public: Habitaculo(int refrate, int luzpin, int dhtpin); //Values from Indoor Sensors int …

#define XYZ class XYZ { }; The first line tells the "C preprocessor" (called before C and C++ compilers) to replace XYZ with nothing everywhere it happens, hence after preprocessing, and before com …

The behavior you describe is symptomatic of a floating input. I guess you have directly wired your buttons between input pins and +5V (or GND, that won't change the observed behavior). The problem i …