Trying to understand the condition: For aux output controls I see the first condition as rocket must launch, which starts timer. then altitude must be >= (is this correct?) acvx100 with a value of 8, so 800 feet. So it checks at Timer Interval=1.5 seconds for altude >=800 feet . So,check at 1.5 seconds for an altitude >=800 feet, if so fire the Aux? This would have to reach 800 feet faster (by a half second) than your previous flight condition right?
Also, what is the value in the top left Arming x10 with a value of 30. So it is 300 something or other?
Last question first - the RRC3 does not arm itself until the rocket is at or above 300 feet. That is your ARMING x10 and 30 (or 300 feet which is the default setting). It must also be known that at 300 feet, this is where the actual timing within the RRC3 begins (RRC3 time = 0.0 seconds although the rocket is acutally 300 feet off the pad.) Actual flight time for my rocket at 300 feet was 1.05 seconds, BUTas stated earlier, this is RRC3 Time = 0.So getting to first question, yes - your interpretation is correct, HOWEVER, at 800 feet, flight time was actually 2.05 seconds. My original timer was 1.0 second but at the 1.0 second timer mark, rocket was only 715 feet. By adjusting it to 1.5 seconds, rocket will now be at 900' (this is ASSUMING I use same motor for next flight)!
Clear as mud?
When planning the staging, really need to pay close attention to sim for motor selected as this value needs to be adjusted for every motor (plus if shooting for high altitude, delay can be longer if you have lots of coast time before sustainer attitude changes off vertical. In this case my sustainer was straight & true up to 2000 feet. 2 stage is really cool & fun when it works but probably 10 times more complex!
esotericdude on 2017-10-24 00:05:34Z wrote:
Ok, so I see main deploy at 500 feet (5x100).
Trying to understand the condition: For aux output controls I see the first condition as rocket must launch, which starts timer. then altitude must be >= (is this correct?) acvx100 with a value of 8, so 800 feet. So it checks at Timer Interval=1.5 seconds for altude >=800 feet . So,check at 1.5 seconds for an altitude >=800 feet, if so fire the Aux? This would have to reach 800 feet faster (by a half second) than your previous flight condition right?
Also, what is the value in the top left Arming x10 with a value of 30. So it is 300 something or other?
And agreed, staging is much more prone to entropy type issues Rockets and software have a lot in common. With software it equates to more lines of code, the more failure points, nearly squared.
Comments
Ok, so I see main deploy at 500 feet (5x100).
Trying to understand the condition: For aux output controls I see the first condition as rocket must launch, which starts timer. then altitude must be >= (is this correct?) acvx100 with a value of 8, so 800 feet. So it checks at Timer Interval=1.5 seconds for altude >=800 feet . So,check at 1.5 seconds for an altitude >=800 feet, if so fire the Aux? This would have to reach 800 feet faster (by a half second) than your previous flight condition right?
Also, what is the value in the top left Arming x10 with a value of 30. So it is 300 something or other?
Last question first - the RRC3 does not arm itself until the rocket is at or above 300 feet. That is your ARMING x10 and 30 (or 300 feet which is the default setting). It must also be known that at 300 feet, this is where the actual timing within the RRC3 begins (RRC3 time = 0.0 seconds although the rocket is acutally 300 feet off the pad.) Actual flight time for my rocket at 300 feet was 1.05 seconds, BUT as stated earlier, this is RRC3 Time = 0.So getting to first question, yes - your interpretation is correct, HOWEVER, at 800 feet, flight time was actually 2.05 seconds. My original timer was 1.0 second but at the 1.0 second timer mark, rocket was only 715 feet. By adjusting it to 1.5 seconds, rocket will now be at 900' (this is ASSUMING I use same motor for next flight)!
Clear as mud?
When planning the staging, really need to pay close attention to sim for motor selected as this value needs to be adjusted for every motor (plus if shooting for high altitude, delay can be longer if you have lots of coast time before sustainer attitude changes off vertical. In this case my sustainer was straight & true up to 2000 feet. 2 stage is really cool & fun when it works but probably 10 times more complex!
esotericdude on 2017-10-24 00:05:34Z wrote:
Yes, the values make sense now, much appreciated.
And agreed, staging is much more prone to entropy type issues
Rockets and software have a lot in common. With software it equates to more lines of code, the more failure points, nearly squared.