OK, the results I gave you were correct: The servo moved with data entry from 00000
> 00400 but then it didn't move from 00500
> 04000. When I ran it again it moved with data entry at all altitudes, with both data sets. Here's why:
The first two tests I left the BOE on and simply uploaded the program with the BOE's power "ON". The servo didn't move with data entry at 00500
> 04000.
This time I turned off the BOE between data set entry and the servo moved at every altitude (00000
> 00400 and 00500
> 04000)
This is very confusing... For the servo to move at all if HAS to have alteast 6 inputs of over 01000 and then at least 9 readings of 00000.
PJ has manually overidden (changed) the program to move with any altitude/ data entry. He's trying to find what's causing the servo to twitch. I think.
There was something else.
Please turn off the BoE. Then turn it back on and re-program it with the attached program.
There should be no twitching, except some brief little shudder at the beginning which is unavoidable (not unusual.)
Please enter the following data when prompted, and note any servo activity with each:
No program movement when reset button is pushed and when 00000 ----> 00400 are entered. Switch is in the #2 position. I lost the screen shot and I'm doing it again.
Mrs. K says 10 minutes until bedtime; I have to be at Harvard at 8 AM...!
OK, here's the screen shot. The movement portion of the program did not work after I pressed the reset button; it did the first run through the data set. When I entered 00000
> 00400 (after I depressed the reset button) I got only altitude, but no movement...
I'll be on-line tomorrow evening about the same time. But I certainly don't want to monopolize your valuable time PJ. You've been so gracious in sharing your time and expertise already, and very helpful.
I'm not sure where we're leaving things tonight. It seems like we've backtracked, but it also seemed necessary. I got lost as to the "why" about halfway through but you and Dylan seems to have a handle on things. I'm content to be the bench lacky and simply test your programs!
.
M. Kibler is off to Slumberland (Harvard? Slumberland?) See you all tomorrow around 7 PM EST. "It was fun" seems so trite. How can I say how much fun it REALLY was?1
Like clockwork. Back from Harvard (but just barely),
PJ, can you help us understand why we were doing what we were last night in short and simple terms? Some of the other team members and parents were following along on the forum and they were trying to understand what we were doing. I tried to explain it by PM, but words failed me because I lost continuity about halfwat through.
How does last night's work fit in with getting the rover to move and collect data after in lands? I think that's what they would like to understand.
1) All data outputs to the GUI as it's supposed to: correct temperature, humidity, elapsed time, CO2 (mV). Altitude is the same what was entered by user. No servo movement wnatsoever; no twitches ;-)
2) At 00000, no servo movement.
3) At the second 00000, the servo moved for ~ 1 second.
4) Each time after that, when 00000 was entered the servo moved for 1 second.
5) 00000
> servo movement (1 sec)
> 00000
> servo movement
> 00000
> movement, etc.
Comments
> 00400 but then it didn't move from 00500
> 04000. When I ran it again it moved with data entry at all altitudes, with both data sets. Here's why:
The first two tests I left the BOE on and simply uploaded the program with the BOE's power "ON". The servo didn't move with data entry at 00500
> 04000.
This time I turned off the BOE between data set entry and the servo moved at every altitude (00000
> 00400 and 00500
> 04000)
OK?
I'm looking at the program.
Hang on.
PJ has manually overidden (changed) the program to move with any altitude/ data entry. He's trying to find what's causing the servo to twitch. I think.
I think because of the way he's writing the program-- to find what's causing P14 to move-- this function has been "overridden" too. At least for now.
Please turn off the BoE. Then turn it back on and re-program it with the attached program.
There should be no twitching, except some brief little shudder at the beginning which is unavoidable (not unusual.)
Please enter the following data when prompted, and note any servo activity with each:
00000
00100
00200
00500
01010
02020
03030
04040
05050
06060
07070
and then report back with your findings and I will give you more data.
MK
I had been referring to movement as twitching.
I changed the movement routine by adding a PAUSE 18 (for the servo refresh timing).
Mark,
Can you push the reset button on the BoE and enter the first 4 set of numbers and screenshot that?
Mrs. K says 10 minutes until bedtime; I have to be at Harvard at 8 AM...!
> 00400 (after I depressed the reset button) I got only altitude, but no movement...
???
I'd like to get your cellphone#. We need to talk.
I'll be on-line tomorrow evening about the same time. But I certainly don't want to monopolize your valuable time PJ. You've been so gracious in sharing your time and expertise already, and very helpful.
I'm not sure where we're leaving things tonight. It seems like we've backtracked, but it also seemed necessary. I got lost as to the "why" about halfway through but you and Dylan seems to have a handle on things. I'm content to be the bench lacky and simply test your programs!
What do you think?
I don't keep my cell phone on much at all. I'm more of an on-line, "ET Phone Me At Home" person (evenings).
You're probably just as well off calling Dylan. He's already surpassed my skillset....!
It's doing what it ought to at this point, nothing, it thinks it's flying, no movement. Yippee!
OK, what time tomorrow?
What time tomorrow, I think we're there, but you're off to Slumberland (Harvard.)
OK?
M. Kibler is off to Slumberland (Harvard? Slumberland?) See you all tomorrow around 7 PM EST. "It was fun" seems so trite. How can I say how much fun it REALLY was?1
Over and out,
MK
Punched the time clock at 10:36 PM
Are You Ready?
PJ, can you help us understand why we were doing what we were last night in short and simple terms? Some of the other team members and parents were following along on the forum and they were trying to understand what we were doing. I tried to explain it by PM, but words failed me because I lost continuity about halfwat through.
How does last night's work fit in with getting the rover to move and collect data after in lands? I think that's what they would like to understand.
:cool:
Got it downloaded A-Ok and it's waiting for me to enter 5 digits.
00000
00100
00500
01010
02020
03030
04040
05050
06060
05050
04040
03030
02020
01010
00500
00100
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
! !
Results:
1) All data outputs to the GUI as it's supposed to: correct temperature, humidity, elapsed time, CO2 (mV). Altitude is the same what was entered by user. No servo movement wnatsoever; no twitches ;-)
2) At 00000, no servo movement.
3) At the second 00000, the servo moved for ~ 1 second.
4) Each time after that, when 00000 was entered the servo moved for 1 second.
5) 00000
> servo movement (1 sec)
> 00000
> servo movement
> 00000
> movement, etc.
Looks good!
We've turned the corner.
I'm glad it's turning out.
I think you guys can start packing
your suitcases for Nevada.
(Don't forget: Hats.)