For the most part, yes.
Read the ADC as fast as you can, compute the data later if you can, otherwise it'll take away from the time that could be used to capture another sample.
For the most part, yes.
Read the ADC as fast as you can, compute the data later if you can, otherwise it'll take away from the time that could be used to capture another sample.
Skimask what bandwith should I use ,between 1Hz to 2Khz ?
I use this for the moment:
Main:
ADCIN 0, adval[0]
Pause 1
ADCIN 1, adval[1]
pause 1
hserout ["A",DEC3 Adval[0],"B",DEC3 Adval[1],13,10]
Pause 50
Goto Main
Maybe I can use this
Main:
ADCIN 0, adval[0]
ADCIN 1, adval[1]
hserout ["A",DEC3 Adval[0],"B",DEC3 Adval[1],13,10]
Pause 30
Goto Main
Regards Pesti
Last edited by Pesticida; - 21st August 2008 at 22:28.
Ok,
Now when I correct understand I must the first Acceleration Change to measure How long the Acceleration is during then I know the distance for that Time for ex. 1 Seconds.
And I can now found the distance for one second,when the speed is constant then is the Acceleration = 0 and after 10 Seconds I can found the final Distance!
I hope is my thinking correct!
Regards
Hello,
Ok I'm coming now to the conclusion that the G sensor is not the really thing for measure if a Elevator is moving and how fast is moving ! :-)
Maybe have some one another better Ideas,I'm using for the moment current measurement to see if the Elevator is moving,but I'm searching for a Modern Solution that give me more Information like ~speed,Movement,Vibration and so on.
Thanks
Regards Pesti
You can add optical encoder to the main motor shaft for speed, acceleration measurement . Vibration can be measured with accelerometer
An accelerometer will just measure the time is takes to go from one speed to another speed, not the distance. It has no way of knowing how far it has traveled unless it is constantly accelerating and decelerating.
Actually, there are ways of calculating the distance using accelerometer data.
The only important point is that you should not turn the device ON/OFF while it is moving.
1. The user must make sure that the device is first powered up when its speed is zero.
2. Then, you can log the data until it tells you that the device is no longer speeding up.
3. Then you know the formula to calculate the speed with the last data you received. Start a timer here.
a. If the subject hits somewhere, and stops suddenly you should time its speed to understand that it hit something and stopped.
4. Stop the timer when the device tells you that device speed is decelerating.
5. When the device tells you that device is no longer decelerating then
a. the subject is either stopped or
b. the subject speed is constant.
You can use basic math to distinguish between a and b.
____________________________________
Last edited by sayzer; - 25th August 2008 at 17:24.
"If the Earth were a single state, Istanbul would be its capital." Napoleon Bonaparte
Hi, KKKid
Not really true ...
if you integrate accel*time, starting from zero ... you will be stopped for integrated result = 0 ...
But, as in real life, there are always calc. roundings and little sensor errors ... you never get a true detection.
The Proof : Model planes Heading Lock Gyros ... Yess !!! The Heading is good ( or considered good ) for a Zero integration sum ...
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Bookmarks