With 2016 well underway it's time for the first update on the state of the stabilization system!
First off, apologies for the massive delays this post has had, was originally slated for mid-Jan launch but between job hunting and other stuff I've been hitting delays and trouble at every turn. Since last semester ended on Dec 18th, I'd been going to TechShop pretty much every day until Jan 18th making massive amounts of progress.
The demonstration mockup was constructed to not only have a physical representation of the final assembly but also to familiarize myself with layout and wiring inside a confined space which is new territory to me. It is constructed out of 3 inch ID cardboard mailing tubes and has fins cut from standard cardboard bolted on, nothing special or lightweight due to this not being the final flight model. The overall mass of this version is 1.48Kg of which 452g is the stabilization system module. Testing and flight versions will be constructed out of "Blue tube" for it's superior durability and lighter weight though at much higher cost ($30/4 feet, whereas the tubes I'm using I salvaged from the scrap pile for free)
Some of my longer term readers may remember how much difficulty I was having with figuring out a method for attaching a fin to the servo spline, trying everything from printing a horn to trying integration of a round arm to no avail. In the end, I decided to stop trying to reinvent the wheel and rework an older design to bolt onto a premade servo horn. These are designed in standard diamond hypersonic form with the axis point 3/4 up the mean aerodynamic chord. Due to the mounting method of fins bolting directly onto the horn, installing these after the servos are in the body tube is impossible, forcing me to have a slot-in module that is held in place with bolts. The slots perform an additional function of being mechanical endstops for the fins to prevent an overcontrol instance(in theory). Sadly, two of the scavenged servos finally kicked the bucket and a full new set is going to cost me $72 ($18/HS82MG) which is FAR out of my frayed kitestring budget which has dwindled to nearly zero as of late. If any of my readers know how to get in contact with Hitec for a sponsorship or how to get parts donated to a student project it would be greatly appreciated if you would drop me a line.
The integration can for my system needed to be reworked due to being a bit too small to fit in the 3 inch inner diameter body tube. I retained the previous method of servo containment and mounting, just upscaled a bit and added bolt holes for attaching to the airframe, in addition to adding a forward riser to hold the control board in place and provide a nose cone mounting flange. Making sure this has a slightly snug fit is key, as internal movement can instigate a self-amplifying and destructive resonant wobble. Two slots with gentle slopes leading up were employed in this version.
The breadboard and connection board of the previous version were not only too hard to set up quickly but also very fragile and annoying to work with. I'd had enough so finally I went and built a nice shield that integrates almost everything while still keeping the Arduino removable so it can be used in other projects. V1 was a first attempt, all wires were red (bad idea) and shoddily laid out which caused a lot of headaches when it simply failed to work when powered up. Debugging when powered up showed the 5V rail hanging around 1.2V and not budging at all even when everything was disconnected. After a few hours of frustration my father walked by and offhandedly remarked to check the ground, much to my chagrin I found that I'd forgotten to connect the ground net to the ground rail which promptly fixed the problems (check for floating grounds). On the second revision the power and ground wires were in standard red and black while signals are in white (I ran out of wire colors okay?) in addition to being MUCH cleaner and better laid out. On the final revison, the IMU will be flipped around 180 degrees since this mount has it offset from the centerline by about 1/4in which may cause control reference issues resulting in the loss of launch vehicle.
Since I will be monitoring this launch from the ground during ascent I needed to get a telemetry solution figured out. Since I had a pair of APC220 wireless UART transceivers laying around after I was gifted them the year prior I decided to use those since they were not only on hand but had good nominal range (2Km LOS). After an initial prototype of a backpack in cardboard and hot glue, I designed and printed a proper backpack that has Velcro to hold down the module and a captive adapter for power and data lines. This assembly bolts onto the back of the control board with two diagonally placed holes as all 4 would interfere with my...not so great point to point soldering.
Powered up 90% completed model The nose cone was quite the interesting design challenge, the total height was 15 inches which surpassed the 6.1 inch maximum vertical print volume of the Makerbot Replicator 2s at TechShop. I decided to print the nose cone in 3 parts that bolted together for modularity and ease of printing. One of the biggest challenges in this was figuring out how to get the bolt interfaces designed on the curved surfaces of the nose cone interior while still being printable without support structure. In the end I opted for simple curved leadup flush connection plates which worked phenomenally with the minimal droop of Hatchbox filament (not sponsored, just freaking love that filament).
Lastly, an update that cannot be shown due to those pesky ITAR restrictons; code revisions! I've started a ground up rewrite of the code, this time with full Kalman filtration of the sensor values and PID to finally ditch the modified example code with shoddy division operators and no tuning ability. So far it's been a challenge as I am unsure as to whether the Kalman should go in front of or after the PID control, has stumped me since the rewrite was on the books. However, I did get some advice from internet friends so the Kalman will be feeding it's output into the PID. In addition to the code upgrade, I've been considering upgrading to a more powerful Arduino or just going ARM, maybe even use the MSP432 that TI sent over for the additional horsepower that will be needed to crunch all the numbers involved in the new code.
On a funny note, the last day I was at TechShop for this month block, had packed everything up and found that the rocket was going to be too hard to carry around in parts. I left it assembled, slung it over my shoulder and walked out the door. Now you'd probably expect raised eyebrows considering it was in a government town but that is not the case on this particular day. It just so happened to coincide with a munitions expo, so while heading out I passed a crew wheeling out a SM3 missile mockup.
Hacker for scale
3 Years apart, it's come a LONG way
Bonus Crystal City late at night after a long day of work at TechShop
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.
I just now saw this post..
First off, good progress! I enjoy projects finally getting going
A few questions and comments for you:
1) What motor will you be flying this on? Are you flying with a club for the FAA waiver, and if so where at?
2) With so much nose weight added from your stabilization system, why the over large rear fins? Surely the CP and CG relationship aren't that wonky?
3) Are you using the microcontroller as a flight controller as well? Ie barometric data for parachute ejection, or using a commercial electronics package for that?
4) Are you planning a control flight (no active stabilization first?
5) What kind of recovery (parachute size, altimeter, etc)?
Sorry for the bazillion questions...
Oh, and be sure to solder, hot glue, epoxy, etc anything that can come apart. For example the microcontroller, APC220 (I think that's what they are) servo connections etc. Launch vibrations do terrible things to unsecured electronics :)
Are you sure? yes | no