Mark,
Is there more data preceding that which you've shown? It's showing Movn, but the zerocounter = 9 and the thousandcounter = 6, so that all looks right to me.
Mark,
Is there more data preceding that which you've shown? It's showing Movn, but the zerocounter = 9 and the thousandcounter = 6, so that all looks right to me.
It is just a adapter for the 9-pin wire that is extremely flat that we could fit under the bell jar to use DEBUGS and still be able to simulate altitude.
A flat 9-pin serial cable would be handy for vacuum chamber testing for sure.
So then it has to be an issue with the subroutines being inserted into the main program.
I agree. But where? Nothing else uses P14. In fact, the only place the number 14 appears in the program is in the date in the comments at the top (June 14) and in the PULSOUT 14, 850 command.
I have mawdsimulation3 running on the bench here and instead of a DEBUG it goes to a servo routine, but the servo only moves when it's supposed to. (a gentle F-Y-I)
OK... so what's different about PJ's mawdsimulation3
> Dylan? that makes the servo only run when it's called on in the program? Is it a DEBUG statement causing the servo to be "frisky"?
Now, wait. I requested that you not enter any data and to report back.
I'm sorry if that seems scolding but I'm trying to get a baseline
I need to ask more questions.
Please let me know when you have the Stamp/asp-bot underway.
When it prompts you for data, please do not enter.
Then report back that it's ready and note any servo movement you may have observed.
You added movement to the program didn't you? The servo moves right on cue when each of the "altitudes" (above) were entered and it ran for ~ 1 second. No ancillary twitching whatsoever (by the servo or by the User).
If it moved with each of those altitudes, that's not good, because it is still in flight.
If didn't move with any of the first, but it did with each of the second set?
Yes, it didn't move on the first altitudes (00000
> 00400) but it DID move at 00500
> 04000. Let me test both data sets again to confirm. Hold on.... (or get a cookie or two =====> 2 trials)
Comments
Is there more data preceding that which you've shown? It's showing Movn, but the zerocounter = 9 and the thousandcounter = 6, so that all looks right to me.
Yes:
1Movn
2Movn
3Movn
etc,
A flat 9-pin serial cable would be handy for vacuum chamber testing for sure.
V 1.5? ~ Or ~ MAWD_DEBUGIN_only_v1.bse ?
I don't recall that it twitched but I'll test again.
============================
No twitch whatsoever as the program waits for data input (MAWD_DEBUGIN_only_v1.bse)
Run the program, let it sit, don't enter anything. Does it twitch then?
No twitch whatsoever as the program waits for data input (MAWD_DEBUGIN_only_v1.bse)
I agree. But where? Nothing else uses P14. In fact, the only place the number 14 appears in the program is in the date in the comments at the top (June 14) and in the PULSOUT 14, 850 command.
Then report back.
OK... so what's different about PJ's mawdsimulation3
> Dylan? that makes the servo only run when it's called on in the program? Is it a DEBUG statement causing the servo to be "frisky"?
Let's leave that go for now and stay the course.
Aye, aye. Staying the course. Full speed ahead with ==============> Main_Prgrm_w_Controlled_Altit_040611_PJ.bse
Stand by.....
1) GUI prompts for 5 digit number
2) Number is entered as an altitude
3) GUI shows all data (CO2, temp, altitude that entered, etc.) correctly.
4) Servo moves at the very same time data is entered, for about 1 second.
This is good. Dylan, this is what we want the ASP-BOT to do when it lands on the desert floor: move and collect data as it moves.
see screen shot
Standing by,
MK
I'm sorry if that seems scolding but I'm trying to get a baseline
I need to ask more questions.
Here! Here! Can you clarify how you want me to run the program?
I'll run the program and NOT enter any data, then report back. Oops.
When it prompts you for data, please do not enter.
Then report back that it's ready and note any servo movement you may have observed.
1) No servo twitch whatsoever at power-up
2) Program prompts user (me) to enter 5 digit number. User does not enter a number. Neither did I.
End of bench test. Program and User are both standing by.
Sincerely Yours,
:blank: <
> :cool:
Program <
> User
Vote for your favorite icon: Program? or User?
Please enter the following series of "altitudes"
After each, please note any servo activity after each
00000
00100
00200
00300
00400
Entered all the "altitudes" as above and the servo did not move a twitch. So what did you find PJ? What's causing the twitch? What's the variable?
All will be explained.
Same drill as before, different numbers, more of 'em.
00500
00600
00700
00800
00900
01010
01500
02000
03000
04000
> 00400. We'll see here in a segundo.
Here we (Program and User) go
You added movement to the program didn't you? The servo moves right on cue when each of the "altitudes" (above) were entered and it ran for ~ 1 second. No ancillary twitching whatsoever (by the servo or by the User).
Standing by.
Did Dylan fall asleep?
If didn't move with any of the first, but it did with each of the second set?
> 00400) but it DID move at 00500
> 04000. Let me test both data sets again to confirm. Hold on.... (or get a cookie or two =====> 2 trials)