- Joined
- Aug 13, 2014
- Messages
- 930
- Reaction score
- 45
I have come up with a long list of pie in the sky project ideas that merge some of my interests in robotics with my new passion for rocketry, to allow my to test them I need a decent diameter rocket that I can reliably send to 1500-2000 ft on inexpensive motors. My father offered to let me rework his 4" quantum tube scratch build he used for his level two cert. The rocket is 4" diameter and currently stands about 7ft tall, it weighs 7lbs and has a 54mm motor mount though I will likely adapt it to 38mm for early test flights.
I plan to take this development slowly with lots of intermediate testing, but I want to rebuild the rocket with all of the space allocated for the eventual final configuration. I will be keeping the motor section and lower section mostly stock, the upper section will require rework due to a bulkhead approximately half way down the tube. The plan right now is to use the existing rear compartment for a traditional backup chute and rework the upper tube for my av-bay and main chute(s).
Here is the rocket in it's current state:
On my list of ideas for this rocket:
1) Arduino based Altimeter / GPS with live telemetry
2) Wireless deployment to allow seperation of the altimeters and charges
3) Remote deployment of backup chutes
4) Active stabilization / attitude control
5) Controlled reefing of a main parachute for use as a drogue replacement
6) Steerable GPS guided parachute recovery with remote control override
As I have mentioned the project will be completed in steps with each phase building on the last. I will begin by completely the physical build. I will then test launch the rocket with traditional electronics and chutes in a standard-ish dual deploy configuration. The altimeters will be stored in the area that will eventually house the wireless deployment board. All launches will also carry the flight computer that will eventually run the project to allow me to start understanding the data collection capabilities and test my programming as I go and to use it's GPS telemetry for tracking. Next, I will develop and test the remote deployment electronics and move the commercial altimeters to the primary av-bay. I should also be able to test triggering the backup chute via ground remote at this stage. Hopefully by this point I will have had enough test flights on my altimeter software to switch to using my altimeter to run the actual deployment. I could then move on to the stabilization and controlled recovery parts of the project.
I have decided to base this project around the proven APM 2.6 uav/drone controller package with my own branch of the standard firmware and potentially my own PC software or ground control unit. I have ordered a APM mini and high performance GPS/compass unit and a 915 MHz telemetry unit based on the same module as the eggfinders use. This package will give me an accelerometer (up to 16Gs), gyro, GPS, compass, and precision barometer. The unit also 8 inputs and 8 outputs for pwm R/C servo channels and auxilary analog and digital inputs and outputs, and current and voltage sensing. This package should be able to handle all of my project plans without much additional hardware work. I will have to design something for the wireless deployment.
I will post more about the specifics of the design plans a little later.
I plan to take this development slowly with lots of intermediate testing, but I want to rebuild the rocket with all of the space allocated for the eventual final configuration. I will be keeping the motor section and lower section mostly stock, the upper section will require rework due to a bulkhead approximately half way down the tube. The plan right now is to use the existing rear compartment for a traditional backup chute and rework the upper tube for my av-bay and main chute(s).
Here is the rocket in it's current state:
On my list of ideas for this rocket:
1) Arduino based Altimeter / GPS with live telemetry
2) Wireless deployment to allow seperation of the altimeters and charges
3) Remote deployment of backup chutes
4) Active stabilization / attitude control
5) Controlled reefing of a main parachute for use as a drogue replacement
6) Steerable GPS guided parachute recovery with remote control override
As I have mentioned the project will be completed in steps with each phase building on the last. I will begin by completely the physical build. I will then test launch the rocket with traditional electronics and chutes in a standard-ish dual deploy configuration. The altimeters will be stored in the area that will eventually house the wireless deployment board. All launches will also carry the flight computer that will eventually run the project to allow me to start understanding the data collection capabilities and test my programming as I go and to use it's GPS telemetry for tracking. Next, I will develop and test the remote deployment electronics and move the commercial altimeters to the primary av-bay. I should also be able to test triggering the backup chute via ground remote at this stage. Hopefully by this point I will have had enough test flights on my altimeter software to switch to using my altimeter to run the actual deployment. I could then move on to the stabilization and controlled recovery parts of the project.
I have decided to base this project around the proven APM 2.6 uav/drone controller package with my own branch of the standard firmware and potentially my own PC software or ground control unit. I have ordered a APM mini and high performance GPS/compass unit and a 915 MHz telemetry unit based on the same module as the eggfinders use. This package will give me an accelerometer (up to 16Gs), gyro, GPS, compass, and precision barometer. The unit also 8 inputs and 8 outputs for pwm R/C servo channels and auxilary analog and digital inputs and outputs, and current and voltage sensing. This package should be able to handle all of my project plans without much additional hardware work. I will have to design something for the wireless deployment.
I will post more about the specifics of the design plans a little later.
Last edited: