I was working with 3 MaxSonic range finders and arduino duemilanove, getting a good quality ranging, and suddenly stop working, I mean is reading unsense reading.
I`m in a bit a a hury... any idea why or most important how to solve this...
forgotten resistor, pull up or current restriction
MCU overloaded
shortcut
timing error
micros() overflow
reentrant IRQ
exploding stack due to recursion
out of SRAM
ignoring arraybounds
integer, byte etc overflow
float rounding errors
uninitialized variable
bug in libraries used
deadlock,
starvation
sorcerers apprentice syndrome
sensor internal protection
dirt in the sensor -> no range to detect
interference with * washing machine, coffeemaker, mixer, boy next door RC car, ...
EMP, lightning, cosmic ray bitflip,
sensors strike ...
....
I mean is reading unsense reading
Maybe the readings are correct but we don't understand the meaning. Some rangefinders have a curve that allows you to operate in 2 different distance ranges. You expect to work in one but get the other.
...
An interpretation of the second law of thermodynamics states: "there are far more ways to go wrong than to go right"
URGENT....
If it is really urgent you should provide far more information than you did. The chance of finding causes is proportional to the amount of information provided.
goal of the project, what do you want to accomplish
CrossRoads, robtillaart, AWOL, cyclegadget thanks to all for the replys, just now I´m be able to response and thanks all for the tips. I agree with the lack of info that I posted, I was in a hurry. Finally I solved the problem, it was a bad wire thats was affecting the hole connection.
Thanks again for the quick replys, always great support from the arduino forum.