Balls 22 Projects

The Rocketry Forum

Help Support The Rocketry Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Awesome Eric! I wish I would have had more time to do some sight seeing, but being the pizza delivery boy I had to be there before LDRS started. Next time I go I'll do some more sight seeing. It's a bummer that you weren't able to fly, but at least you hadn't succumbed to go-fever like I had. At least now maybe I'll have a chance to see these bad boys fly in real life!

Manny

P.S Are you going to Bong this weekend? I'm coming home to visit and I'll be stopping by the launch and I'd love to hear more about your big BALLS adventure.
 
Awesome Eric! I wish I would have had more time to do some sight seeing, but being the pizza delivery boy I had to be there before LDRS started. Next time I go I'll do some more sight seeing. It's a bummer that you weren't able to fly, but at least you hadn't succumbed to go-fever like I had. At least now maybe I'll have a chance to see these bad boys fly in real life!

Manny

P.S Are you going to Bong this weekend? I'm coming home to visit and I'll be stopping by the launch and I'd love to hear more about your big BALLS adventure.

Hey Manny,

Sorry I didn't make it to Bong; I wanted to but it was too close to Balls for me to attend without getting divorce papers! Looking forward to seeing you at MWP!!! Hope all is well at IAState.

-Eric-
 
Apologies for this being such a long and drawn out process! I need to close this chapter of the book so I can move on to the next chapter (Midwest Power 11 and beyond!).

Day 2 of the trip was another travel day. The purpose of Wednesday 9/18 was simply to drive from Cheyenne, WY to Fernley, NV; really that’s all there is to it! The Plains hotel is directly across the street from a downtown park with fancily painted giant cowboy boots resting just shy of “The Wrangler” Ranchwear storefront.

207a_zps2b15db0f.jpg


Moving on out, we traveled across the rolling plains of Wyoming encountering thousands of antelope, lots of beef, a bit of mutton, and a pair of elk. Eventually we crossed into Utah, then traversed the whirly twirly road (my boys’ description) into Salt Lake City. Outside of the City, I can’t say we were awestruck with the Great Salt Lake; it’s presentation was less than glorious and its size not so impressive to those in our caravan who live on one of the other Great Lakes. That said, we did not get off of I-80, so I’ll merely call this a first impression and not a final ruling! Stopping for a short break at a rest stop before the road straightens onto the Salt Flats, us ‘Sconsin boys were amused by this sign; not one we see every day here. Ain’t no scorpions over here and our snakes don’t rattle!

212a_zpsd3a44b07.jpg


Didn’t see either at the rest stop, but I had my encounter out at Smoke Creek…to be covered a bit later. We continued the westward venture and took an obligatory photo of the awkward balls monument as we zoomed past. One individual was pondering life amidst the flooded area while another half pipe skateboarded in one of the quarter-balls.

215a_zps356a51b9.jpg


Shortly thereafter we took notice of our launch site destination for Monday’s return adventure; hmmm the salt flats appears a bit wet.

218a_zps6087da03.jpg


Finally, into Nevada we went, navigating through the valleys and occasional mountains. 2 hours shy of our evening destination, we stopped at a prescribed location for supper: The Pig BBQ in Winnemucca. Tripadvisor and others give The Pig mixed reviews and we did as well. The service was fantastic; the food arrived possibly faster than any restaurant I’ve ever been to, the pulled chicken and pork were great, the brisket and sauces were good, the ribs weren’t bad nor great, but the beans were excessively peppered. Overall, for Winnemucca, NV, not bad BBQ! Didn’t compare to Pig In Pig Out in Wichita, KS however…try that one next time you go to Argonia; you can thank me later!

Back on the road for a short stint, the old guys in the car had to stop for a bathroom break; we stopped in Lovelock, NV. Not a lot of love for Lovelock; we made several stops just to find one working restroom and left town scared. Leaving relieved to still be alive and relieved of bladder pressure, getting to Fernley was easy; getting to the hotel was an offroad adventure. Note; do not turn onto the gravel road at the late night taco stand, it will get you to an pothole filled railroad yard parallel to the Comfort Suites with few options to get in or out; it will not get you to the Comfort Suites. I'll admit to being excited about the taco stand.

...to be continued (in a more timely fashion)

-Eric-
 
Thursday, 9/19: Balls setup & Hamster Dance

This was a big day; lots of places to visit and work to be done. Fortunately, there was less driving involved. For the first time in two days, we headed a direction other than West. Turning North on 447, we pulled off for a moment to take a photo of the eroded Truckee River Valley in the early morning. Purdy…

054_zps138e6f71.jpg


Continuing on, we stopped to visit Snoopy. Awestruck moment number one of the trip: there was a complete lack of sound here. No cars for miles, no wildlife for perceivable distance, no wind; there was a complete lack of sound….until someone started peeing on the roadside shoulder.

226a_zpsabca428d.jpg


Arriving in Empire, we were disappointed to see that the “Welcome to Nowhere” sign accompanied by the Monsters, Inc. artwork was gone. We tried to stop at the Empire Store for a few last minute supplies, but found they were closed (not permanently). Furthermore, we explored the new ghost town status of Empire. The entire town is surrounded by a chain link “Company” fence; which was secured by not one, but three locks at the gate to the city. Aside from the store, there is absolutely nothing available for use in Empire. At the bar at Bruno’s later in the weekend, I met the oldest inhabitant of Empire, learning that the only people still living in Empire are him and the family that runs the Empire Store….that’s it! Sad, really.

Down the hill, across the tailings of the playa, and around the bend into Gerlach, we arrived at Bruno’s to check in. We met Bruno, negotiated pricing for a case of bottled water, and unloaded a few items into our dorm room styled accommodations. Then out to the Black Rock playa for the first time! The Burner’s were in their final stages of cleaning up the playa, and thus detoured playa traffic further out once pulled onto the 12 mile entrance. We found the flightline without issue (great markings guys!), and set up near on East end of the line alongside Jim and Gloria Jarvis. After a few greetings and a quick unloading of chairs and tables, we headed out to set up our tower and launch pad about ½ mile out. I took a moment to breathe in the environment. Yes, finally arrived!

230a_zpse2a4b18c.jpg


062_zps3be73200.jpg


Enough looking around, back to work! We assembled the pad and tower. Then we tweaked the tower; we took too long tweaking the tower and were late for the Tripoli Gerlach sponsored Hamster Dance! Nevertheless, off one playa, onto 447 North towards Cali, then onto the gravelly Smoke Creek Road and back onto another playa via a ridiculously deteriorated washed out access “road”. Arriving late but determined, we quickly set up camp and put some rockets on the pad. Quick rules recap for the launch: all motors must be single use, non-metal cased; rockets must weigh under 5 lbs ready to fly.

068_zps70b51085.jpg


First on the pad for the Sconnies was Marc with his Jart. 29-3G XX phenolic cased 150-G60. The nozzle fractured and spit out at ignition. Out of 136 “Sconnie” motors, this is the second to fail, the first in a public setting….could this be a sign of things to come over the long weekend at Black Rock….they do say that the place has a way of humbling you! Sorry Marc, the motor static tested just fine; fractured nozzle…really? I was/am flabbergasted! No damage to the Jart at least.

071_zps5252c5dc.jpg


Tom loaded up his 2.27” Wildman Jr. while I loaded up ISPy. Tom’s rocket sought the award for heaviest rocket flown (while staying under the 5 lb max); unfortunately the scale wasn’t available after our late arrival. Nevertheless, the 4.9 pounder took to the skies on a 38-5G baby J186. A solid boost to respectable altitude was foiled by separation at apogee.

As soon as Tom’s Wildman landed, ISPy ripped off the pad angling slightly to the East. Here she is on the pad before flight.

072_zps34251a14.jpg


Gerald caught a picture of it, but I'm not smart enough to post a direct link to Picasaweb.:eyepop: I had a solid signal from the Com-Spec Transmitter throughout the flight; even had a decent, but reduced signal after touchdown to the East of the launch site. More on that later.

Tom Blazanin called “last call” for any last flights, so I quickly grabbed the Alpha Hamster, while Ken Good grabbed his 3 stage rack rocket. Ken’s rocket popped the chute on the pad (magnetic switch issue?) and so the Alpha was to be the last (and smallest/lightest) flight of the launch. The little 19mm F38 spit its igniter and thus didn’t light; it wasn’t given a chance to recycle and Hamster Dance was called complete. We cleaned up while they took care of a gallon of tannerite. Now, launch was over, of the four rockets we attempted to fly, two were out on the range someone, one in separate pieces, and two failed to launch….one spit nozzle and one spit igniter. I am not used to this kind of lousy performance!:confused2:

Now to track down ISPy and the Wildman Jr. I turned on my receiver, waved the yagi around, turned up the volume, and received nothing but static. Huh, that’s weird. We drove East on the playa in hopes of seeing ISPy layed out. The Smoke Creek playa was a bit softer than Black Rock with some major cracks in the surface, so we turned around after ½ mile or so; not wanting to get stranded alone, since everyone had left by now. Disappointed, we drove out to Smoke Creek Road in search of Wildman parts. Tom picked up a good signal on his rocket, but it was well East of where we thought it had landed. I turned on my receiver and was pleasantly surprised to find that the signal from the tracker had returned! We drove along Smoke Creek Road until we honed in and found Tom’s Wildman Jr. payload. The 1/8” tubular Kevlar severed as well as the 3/16” quick link bent into a funny shape causing the separation and subsequent loss of the booster section. On down the road we went until I was at a right angle to ISPy’s signal, where I decided to take a walk. Equipped with a 2 way radio, several bottles of water, and the tracking receiver/antenna, off I trotted into the rolling hills toward the playa. After walking for a while, I heard a baby rattle, which I took as a warning from a rattler to stay away. Changing directions, I continued on until I heard another rattle. This continued until I had walked the ~1 mile trek from Smoke Creek Rd. back onto the playa on an Easterly heading. Finally, I spotted ISPy lying out on the playa. Other than melting the drogue streamer and main chute (no room for wadding and couldn’t find the nomex on Wednesday night), she was in good working order. The Adept 22 beeped out 13,030’; good enough for the highest altitude at Hamster Dance! The lower airframe showed some obvious signs of heat resultant of both high speed and a linerless motor! The graphite filled epoxy nose tip also melted and slumped over….sorry the camera focused on the wrong thing..it is definitely bent however!

237a_zps50217c37.jpg


073_zpsa1710efe.jpg


Since I had walked from the base of the mountain in the background onto the playa, dodging rattles, man eating jackrabbits, and ferocious field mice along the way, I put a call in to the home base fighter van who came to my rescue. Interestingly, van tracks from the earlier playa drive in search of ISPy came within ¼ mile of the rocket’s landing site…turning around 30 seconds later would’ve saved an hour of searching…oh well: hindsight!

231a_zpsb229d9b3.jpg


239a_zps965c31e5.jpg


We learned that the moisture in the alkali playa makes the surface somewhat conductive, therefore absorbing RF signals once the rockets are on the ground. Smoke Creek Road was at the foothills of the surrounding mountains, therefore was elevated above the playa, and somewhat allowed for successful signal transmission. I was warned of this and had GPS tracking capabilities on the Balls projects, but no room in the small HamsterDance airframes. Interesting phenomena; keep this in mind if you’re attempting RF tracking on the playa!!!

We returned to Bruno’s for supper and some rocket prepping before calling it a night. Initial impression of Bruno’s restaurant: very well done! For a place in the remote location of Gerlach, there is little-to-no competition, yet the food and service was quite good!

To be continued...
 
Fri 9/20/13 Balls Day 1

Honest apologies for this taking so long!:facepalm: Here we are a month after Balls, and I need to put this beast to bed! I just couldn't turn the page to the end of the chapter until I had some sort of closure on what went wrong at Balls; I think I have the answer(s) now.

Friday: Day 1 of Balls dawned a perfect morning! Low winds, clear skies, and a vast open range. We got an early start and were on the field by 8. I had some issues with the avionics in the nosecone of 20 Year Itch (more on that later), and therefore would have to wait until later in the day or weekend to fly. Tom finished final prep of his Air Train on the playa, posed for a photo, then we headed off to the flyer’s meeting. After the meeting, we drove out to our pads and turned the bird to vertical. After arming we retreated to the control box and called in our “flight ready” status.

079_zpsc321d38e.jpg


242a_zps5e472059.jpg


A nice TonyA To100K cone tops it off!
084_zps75a0909a.jpg


Right before Tom's flight, Skippy's O25,000 leaps off the pad; too fun not to repost!
100_zps7660080b.jpg


Some time later, the flight was announced. Air Train ripped off the pad on the Sconnie M1060 “Superballs” motor during the first salvo of Balls flights. Straight and true, the train hauled the freight outta site.

106_zpsca10b794.jpg


107_zps3995eda2.jpg


Much like the previous day at Smoke Creek, we tracked the rocket via Com-Spec transmitter past apogee and during the long descent. Without regaining visual, the signal dropped once the rocket landed. Tom was pleased with the flight and made a comment predicting what he thought would be a fairly easy recovery:eyepop:. Thus, we took off to the North-Northwest in search of the train. Paralleling our experience at Smoke Creek, we now had no percievable signal from the tracker. After driving around for some time, finding three separate pieces of the Bill Good 2 stager in totally different areas of the playa, we temporarily gave up and returned to home base. Huh.

Marc whipped out his Blue Balls and placed them...errr it on the rail while Crazy Jim and company loaded up the tower.

119_zps44910e05.jpg


115_zpsf45f3a21.jpg


135_zps3eedd23e.jpg


After entering the que, Blue Balls took to the skies on a Sconnie L900 searching for 15,000'+.

136_zps0c71e4b7.jpg


Following a spectacular boost, the Blue Balls disappeared for the last time. The Falconry tracker chirped at us through the remainder of the flight before ceasing once it met terra-firma. Off we ventured to the North in search of another muted rocket; another case of deja-vu: no signal from the transmitter. We drove around the playa for an unprescribed amount of time finding a nosecone densely populated with cameras and circuitry, and a Rocketman chute (both turned in to the RSO), but returned without our beloved Blue Balls.

We may be slow, but we were beginning to catch on that our directional transmitter devices may indeed not work so well out on the playa. We had been warned, but some of us didn't listen, fully believe it, or whatever.:facepalm: Ironically, I did believe it, chose the alternative GPS, and that is what ended up grounding my efforts over the weekend; read on!

Following Marc's flight, I returned to tent city to do some prepping of the 20 Year Itch. We learned that our new friend James from the neighboring Oregon camp had GPS coordinates for the landing location of Air Train. Therefore, as I worked on prepping, Marc and Tom took off in search of Air Train. I got about 45 minutes of work in until the dust/wind storm rolled in around 2. That marked the end of prepping and flying efforts for us for the day. Marc and Tom returned without Air Train. Tom, James, and I later drove out to the coordinates and found Air Train upwind a ways after being dragged for 1/4 mile or so. We were thrilled to have the train back and Tom was very happy to smash his previous best altitude with a reported altitude of 23,400'! Well done, Dad!

143_zps10e252ab.jpg


145_zpsda3c6949.jpg


The train had a bit more character post flight than it did pre-flight; I like it!
147_zps422a2b67.jpg


With the winds and dust sustaining their play time, we retreated to Gerlach, washed up and headed to Bev’s Miners club for a drink. Bev is a lovely lady that moved West from nearby (for us anyway) Marinette, WI in the 40’s. She has a basic selection of beer and carefully pours the local favorite of whiskey sweet (or whatever they call it there). The Miner’s Club is touted as the friendliest bar in Gerlach; probably a true statement. On Friday night, the locals were having a pot luck there; every brought a dish to pass, displayed nicely on the covered pool table. Not wanting to crash their party, we soon moved next door to Bruno’s for another drink before the Tripoli Gerlach member’s meeting commenced.

The Tripoli Gerlach's meeting was a really nice event. A nice meal with spaghetti and meatballs, (potent) garlic bread, salad, and even wine, it was a great meal in a nice setting. Tom Blazanin did a great job keeping things brief and interesting, and even gave out a few awards/prizes. Thanks Tom! New members joined and old members renewed; it was a pleasant end to the first day of Balls 22!

...more to follow...soon...really I promise!:bangpan:
 
On Saturday, the rock was moving and wet; but not white.
067_zpsfe7622bd.jpg


We awoke early once again, looking outside to partly cloudy skies and a solid wind. We soon ventured out onto the playa, but turned around and left even before arriving at the flightline as we saw the rain come over the crest of the mountains to the South.

Rainbow
153_zpsfe75255c.jpg


Rainbow on the edge
155_zpsebdf78fe.jpg


Not wanting to become stuck and stranded, we headed back to Bruno’s for breakfast. After breakfast, we decided to return to the playa where we hung out until the clouds grew denser, winds grew stronger, and it looked of rain.

Again, we left the playa and headed toward Smoke Creek to visit Planet X pottery. John and Rachel Bogard make their living by selling their art on their homestead. Their pottery is crafted well and is priced accordingly. We each picked out a few smaller items, had a sip of moonshine, said hi to Art Upton and Tony Haga, then returned to Gerlach. I have a new favorite Mountain Dew mug (none of that coffee stuff here:no:) with a desert motif.

We all watched the "Couples Retreat" movie through our eyelids in the afternoon before making the trek from Bruno's Hotel to Bruno's Country Club, Casino, Restuarant, Banquet Facilities, Souvenir Stand, Smoke Shop, Lounge, General Store, and Bar. On a rainy Saturday afternoon in Gerlach on a rocket weekend, it's a busy place. We all enjoyed Bruno's world famous ravioli!
245a_zpsa829341a.jpg


I may have failed to mention earlier that when I test armed the AIM XTRA 2.0 after hooking up the initiators earlier in the weekend, it immediately fired the apogee charge. Thankfully, not yet loaded with powder. Nevertheless, I hooked it up to the laptop, everything tested fine and the settings appeared correct, so I completed reprepping the system(s) on the rainy Saturday afternoon into the evening.

After fully prepping the Itch, I looked around for a place to put this thing. You see, it was in the 40's outdoors and I didn't want to subject the batteries to the cold (even inside the Black Rock van).

Let's see, cubby behind the door: occupied.
248a_zps9fc5fd25.jpg


How about the floor? The other bed? Occupied.
247a_zps36192026.jpg


Not sure how it happened, but the rocket and I ended up in bed together.:y: It's the first time that I can remember sleeping overnight in a bed with an O motor:confused:
249a_zps2d62347a.jpg


Lying in bed with a polished aluminum fin can, weird things man, weird things.
255a_zps4a93f4eb.jpg


Overnight, we had planned to head out of town to stargaze; alas the rock was moving and did not have a shadow.

-Eric-
 
Sunday morning, the rock was wet but drying; it swung gently; it was cold, but not white.

After a vast amount of rain the day before, we were skeptical of playa driving conditions, but headed out anyway. We found the playa to be a bit damp, but easily navigable. Upon arriving at the flightline, we immediately proceeded out to our set of pads to set up 20 Year Itch.

161_zps8108f51c.jpg


162_zps466ef913.jpg


163_zps398d6323.jpg


After fine tuning the tower, the stack was raised to vertical. I took time to take a single photo before arming the desert rat.

164_zps8baad2bf.jpg


As I moved in to arm the electronics, I paused as I remembered the charge that fired upon power-up earlier in the weekend. Before proceeding, I warned my partners in crime that I was arming the charges, then proceeded. Akin to the premature firing earlier, as soon as the first pair of wires was twisted to arm the AIM Xtra 2.0; the apogee charge fired, the nose blew, and thus ended my efforts to fly at Balls 22. There wouldn't be enough time to reprep, and even if there was, I had lost all faith in the avionics.

Well, that sucks!
165_zps9671799a.jpg


166_zps4076d3d0.jpg


I encouraged Tom and Marc to return to the flightline to get Marc’s next rocket ready while I took down the tower in solitude. They did, and upon their return the tower had been disassembled and Marc's Bambulance was loaded up on the rail.

Bambulance turned in an interesting flight; the small fins lent to a bit of a wobbly boost.
196_zps3460f64d.jpg


Soon after, the winds picked up and the dust flew.

219_zps23af2a07.jpg


We packed up and bid farewell to the vast playa en route to the long road home just before noon.

...more to come...
 
I hate to say it...but did you have the wires backwards running from your battery to the altimeter? I really think that you would have checked that, but I know that the Adept22 would behave the same way when the battery is hooked up backwards. Don't ask me how I know...

These reports are like Christmas morning. Your narration and pictures are great!
 
The really crappy part about driving 2100 miles to a launch is that you have to drive 2100 miles back home. The really long drive home began Sunday around noon as we left the Black Rock Desert. The sun setting over the ranges made for some pleasant scenery.

259a_zps5d4a27eb.jpg


We made it to the NV/UT border on Sunday evening, staying at one of the Wendover casinos and enjoying prime rib while there. In the morning, we fed the van some Sinclair, then headed for the Bonneville Salt Flats for a quick Class 1 launch.

Welcome to Bonneville!
221_zps84185975.jpg


If it looks and tastes like salt, it might just be salt!
260a_zpsb8465ada.jpg


Yep; still wet. At least it makes for a nice photo:
261a_zps31aa0445.jpg


Marc was first up with his Jart. He flew it on a G80; of the Blue Thunder single use variety:
224_zps52683806.jpg


225_zpsf5543f9a.jpg


And landed it right next the pad. Showoff!:clap:
227_zps3ea2578b.jpg


228_zps1e8f53e6.jpg


I went next with one of my boys' Jarts:
230_zpseb90e67d.jpg


233_zps8be2739d.jpg


On a G80; this of the Skidmark variety:
235_zps97873dfa.jpg


237_zpsc6d6ca75.jpg


Tom liked the G80/Jart trend, so he flew the pair too.
242_zpsa070d091.jpg


Skiddy:
244_zpsa22cf30d.jpg


246_zps582c3a91.jpg


Tom wanted a photo of his Jart landing on a mountain. He missed the mountain, so this was the best I could do:
251_zps2577c64b.jpg


Tom's landing site:
253_zps4641a3ea.jpg


Eric's landing site:
257_zps9a2d155f.jpg


The salt was wet and our feet got wet; but the rockets stayed out of the moving lake, so all was well. A nice little visit to another unique launch site!

After our salty little launch, we hit the road again. Utah flew by pretty quick, Wyoming is a wide state and the gassy town of Sinclair is less than stellar, and Nebraska was darn near never ending:eek:. We tried the Runzas; a poll would show mixed reviews. We stayed in Omaha overnight before parading into Iowa the next morning.

On the way out to Balls we discussed the upcoming Wildman drag race at Midwest Power 11. We all determined that none of us needed a 3" rocket, so we'd all pass. Somehow, before we got out of Nevada on Sunday, we had already decided that we'd swing by Tim's place on the way home and pick up a trio of Competitors. What happened???? So on Tuesday morning, we crossed Iowa, and hopped a puddle into Illinois. Upon jumping the puddle, the old guys had to pee again, so we stopped at the welcome center. Nice stop with a nice view, but the longest driveway EVER:surprised:!

269a_zpsdcaf4fc5.jpg


Around noon, we ambushed Van Orin acquiring 3 Competitor 3's and some other goodies; thanks to Tim, Jackie, Doofus, and other dog for the hospitality!

A short skip later and we were finally at home. Now to unload:
270a_zpsa3a9bd86.jpg


I was happy to see my boys and they were happy to see their Jarts.
272a_zpsd3b8e160.jpg


We put on about 5000 miles; the van got a PDQ Wacky Wednesday cleaning before returning to Hertz. On a positive note: unlimited miles really means unlimited miles with Hertz (a point I verified before renting).
271a_zps783b317b.jpg


Postlude/Lessons Learned to follow....
 
I hate to say it...but did you have the wires backwards running from your battery to the altimeter? I really think that you would have checked that, but I know that the Adept22 would behave the same way when the battery is hooked up backwards. Don't ask me how I know...

These reports are like Christmas morning. Your narration and pictures are great!

Thanks Dan!!!!!

After she popped the charge the first time, I figured I had somehow miswired something. So I double and triple checked everything, then hooked it back up to the laptop to verify settings and continuity before proceeding once again.

We figured out what the problem with the unit was; it resulted in a firmware update, full details coming in the postlude here shortly.

Thanks again for following along, and your patience!!!!

-Eric-
 
Are we there yet?

Here's a cap on the efforts so far. More or less could be said.

The Positives: What went right?
1. I finally got to Black Rock; for that I am truly grateful!
2. Got to meet Bruno, visit Guru road, launch at Smoke Creek, meet a bunch of great people, eat world famous ravioli, etc.
3. A lot of truly wonderful people helped with these projects. In no particular order: Thanks Dave, Eric, Eric, Scott, Tom, Marc, Jim, Gary, Judy, Gary, Ed, and all the others I forgot to mention.
4. Dad's rocket did great; 23,400' is a nice altitude for someone not interested in altitude. Glad I could help just a little bit on that project!
5. Both of my Balls projects came home in the same fashion they left; true they didn't launch, but they're ready to serve another day!
6. I have several unburned motors that I can fly closer to home (one is loaded up in a rocket for Midwest Power in a week!)

The Negatives: What went wrong:
1. I went all the way to Black Rock and didn't launch a thing! Really? I suck!
2. I ran out of time; I wasn't as prepared as I'd like to have been. Rarely if ever do I go to a launch without rockets 95% prepped. I simply ran out of time and went without significant prep work done in advance. If I had been further along in the process, I may have discovered the issue with the AIM XTRA and supplemented functionality with a different unit. I'll never know; should've been further along in the process before leaving for Gerlach!
3. Twice over the same weekend, the AIM XTRA 2.0 fired the apogee charge immediately upon power up. Both times, it was after carefully wiring up the system, testing for channel continuity and verifying systems via the system's program on the laptop. I didn't have an answer until yesterday; when I got a message from Gary at OffWeGo, and an associated firmware update for the XTRA system. Gary's explanation is as follows, and makes sense why the charges fired when they did for me:

I ran across the same issue a week ago and working with the manufacturer found an issue in the launch detect software. Essentially when the rocket is horizontal the barometric sensor readings provide an altitude reading and when the GPS begins to lock it provides an altitude reading as well. Since the rocket is horizontal the accelerometers do not come into play. If the discrepancy between the GPS and Barometric sensor readings is large enough the altimeter was sensing this as a velocity and detected launch. Then of course since the rocket is horizontal and due to minor fluctuations in altitude readings apogee is detected and the charge fires. The altimeter state machine has been updated to prevent this from happening

I prep my rockets in a horizontal fashion; then before filling any charges with powder, I power up the unit to check for the correct continuity, battery voltage, etc. This is done horizontally. When all is swell, I power down the unit, load charges, and complete the remainder of prep work. Based upon the description above, it makes sense that a discrepancy must have existed sufficient for the unit to falsely detect apogee and kick the charge. This issue was addressed in the latest firmware update that Gary sent out yesterday; something to the tune of:

This releases addresses the following items:

1. Allows user selection of either imperial or metric units for the display of graphs and flight data either during or reviewing past flights in the XTRA and the BASE software
2. Corrects identified graphing issues
3. Updated launch detect state machine
4. Fixed flight emulation issues
5. Automatic capture of major flight parameters in notes tab

We strongly recommend that all users immediately implement the new release. In order to obtain the fix and features please do the following

1. Save all existing XTRA flights onto your PC using the current version of the XTRA software. If you do not do this prior to updating the firmware all existing flight data on the XTRA will be lost!

2. Download and install the new version of the software and firmware from the following web page: https://www.offwegorocketry.com/product_info.php?cPath=220&products_id=1203 and select the hyperlink Firmware 2.04 & Software 2.05 zip


Lessons Learned:
1. Directional Transmitters such as the Com-Spec AT-2B, Falconry, Rockethunter, etc. don't work on the playa. We had been warned, I believed it, but we still tried it. Guess what; they really don't work out there!
2. One significant project is enough; two is probably too many unless everything works perfectly. In our case, collectively we had 8 projects; that was too many for the time slots alotted by weather induced interuptions.
3. The big one: and one of my biggest personal rules with rocketry that I knowingly but apprehensively ignored: don't put untested avionics in significant projects that absolutely depend on it! When the XTRA began misbehaving, I had no back up plan as I had the units slated for use in both projects; both relying upon the units to trigger flight events. I could have installed redundant electronics for flight events and used the XTRA for tracking only, but by the time I discovered there were true issues (preventing flight), it was too late for a back up plan!

I said on August 16th in post #52 of this thread:
Rocket avionics to me are much like a restaurant's reputation: takes several positive experiences to gain a little faith in the product and only one negative experience to kill that faith. Though these projects *should* go higher than my past projects, I'm seeking to keep them as simple and familiar as possible. All motors, initiators, electronics, etc. have been tested on previous projects before employing them on these birds (one exception, but not my first experience with the (personally trusted) manufacturer).

Can you guess what the "one exception" was? Yep, while I had experience and faith in Entacore products, I had not yet flown the AIM XTRA. That bit me! Note: I don't blame Entacore, or OffweGoRocketry; I blame myself for installing a system in which I had not personally tested in both of my projects without a back up plan!

Stick to your guns; live and learn! I went to Balls with the expectation of attending, the intent of launching, the hopes of hitting it big on one of the projects, and the dreams of success of a pair of projects. It was failure to launch, but not a failed event or adventure. I'll be back; hoping for a bit more of a successful reflection next time however!!!!

Oh, and I did actually finish the two stager, just never got around to assembling the full stack at the launch. Here's a photo or three of September Fate-Carbon Slipper ready for another day:

263_zpsc395d587.jpg


264_zps3edee145.jpg


267_zpsea0ce6ca.jpg


Oh well!?!?!?
269_zps4cfafcda.jpg


End Chapter 1.
 
Last edited:
Eric,

Awesome thread. Thank you for taking the time to write all this and share it with us.

Great projects, great write-up, and really good lessons...

Now I have the bug. Must go to Playa....
 
Eric, this has been an awesome write-up/blog thing! It really sucks that you weren't able to fly, but you did a fantastic job on your rockets and got a little taste of the evil that is Black Rock :dark:

For any of you Midwest guys that want to go to the playa next year, a hand full of us (me, possibly Sather, Ben, my room mate) are planning a trip next summer to Aeronaut in August. So Claude, Eric? Maybe we can do a group travel deal?

Manny
 
Hi Eric,

I am really sorry that you were not able to fly at BALLS. The issue you have reported was something which we have never experienced in all of our testing. However, we realise now that there definitely was an issue with the launch detect state machine. Let me explain to you a bit more how this error came about:

The AIM XTRA uses a Kalman filter for altitude, velocity and acceleration estimation. These values are used for launch detection.

When the XTRA first achieves GPS lock, it attempts to calibrate the pressure altitude to the GPS altitude. This is so that we can have a smooth transition from the point where the pressure sensor is no longer reliable to where the GPS becomes the primary source for altitude measurements. The calibration is done automatically and through a low pass filter so that the pressure altitude doesn't jump to the GPS altitude immediately.

Now for the issue:

Firstly, when the altimeter is horizontal, the accelerometer inputs are discarded. The means the altimeters is only relying on pressure and GPS readings. If the pressure altitude is more than 150 meters lower than what the GPS indicates, the calibration routine is too aggressive and attempts to converge the pressure altitude too fast. The Kalman filter sees this as a velocity. This velocity would exceed 30 m/s for 0.5 seconds, which is the launch detect condition for the AIM XTRA.

So, how have we fixed it?

Well, after many emulations with existing data and "prepared" data we decided to decrease the aggressiveness of the calibration. If the pressure and GPS altitudes are very different, the GPS readings will also be less relied on. Only once the two have converged to within 10m, will the GPS readings be used with the standard certainty.

This has already been incorporated into the latest release (Fw 2.04 and Sw 2.5) available on our website.

In closing, let me just say again how sorry I am that this happened. If you have any questions or comments, please ask. You can email (address on website) or PM me.

Take care,
David de Bruyn (Entacore)
 
Hi Eric,

I am really sorry that you were not able to fly at BALLS. The issue you have reported was something which we have never experienced in all of our testing. However, we realise now that there definitely was an issue with the launch detect state machine. Let me explain to you a bit more how this error came about:

The AIM XTRA uses a Kalman filter for altitude, velocity and acceleration estimation. These values are used for launch detection.

When the XTRA first achieves GPS lock, it attempts to calibrate the pressure altitude to the GPS altitude. This is so that we can have a smooth transition from the point where the pressure sensor is no longer reliable to where the GPS becomes the primary source for altitude measurements. The calibration is done automatically and through a low pass filter so that the pressure altitude doesn't jump to the GPS altitude immediately.

Now for the issue:

Firstly, when the altimeter is horizontal, the accelerometer inputs are discarded. The means the altimeters is only relying on pressure and GPS readings. If the pressure altitude is more than 150 meters lower than what the GPS indicates, the calibration routine is too aggressive and attempts to converge the pressure altitude too fast. The Kalman filter sees this as a velocity. This velocity would exceed 30 m/s for 0.5 seconds, which is the launch detect condition for the AIM XTRA.

So, how have we fixed it?

Well, after many emulations with existing data and "prepared" data we decided to decrease the aggressiveness of the calibration. If the pressure and GPS altitudes are very different, the GPS readings will also be less relied on. Only once the two have converged to within 10m, will the GPS readings be used with the standard certainty.

This has already been incorporated into the latest release (Fw 2.04 and Sw 2.5) available on our website.

In closing, let me just say again how sorry I am that this happened. If you have any questions or comments, please ask. You can email (address on website) or PM me.

Take care,
David de Bruyn (Entacore)

A) Would it not be better to simply offer an option that disables outputs until vertical in the case of vertical mounting?

B) Why does it discard the accel data when horizontal? They're still valid until you launch (at which point they certainly would clip), but you can still use the data to moderate launch detection.
 
A) Would it not be better to simply offer an option that disables outputs until vertical in the case of vertical mounting?

B) Why does it discard the accel data when horizontal? They're still valid until you launch (at which point they certainly would clip), but you can still use the data to moderate launch detection.

A) Yes, I have thought of implementing something like that. What we are going to do with the next release is have another state besides PAD. We will add a state for "PREP". Once the rocket goes vertical it will be in the PAD state. If certain parameters are met, it will revert to the "PREP" state so that you can take the rocket off the rails if you need to.

B) Well, it doesn't "discard" it completely. It just doesn't use it as an input for the Kalman filter. The filter is based on a one dimensional setup, so horizontal inputs for acceleration are incorrect.

I just want to state that this situation is rare. It only happens when the weather creates a condition where the GPS and pressure altitudes differ significantly.
 
B) Well, it doesn't "discard" it completely. It just doesn't use it as an input for the Kalman filter. The filter is based on a one dimensional setup, so horizontal inputs for acceleration are incorrect.

I see. I thought it was 3-D (which would be the most awesome, but needs one of the newer high-range 3-axis digital accels).
 
I see. I thought it was 3-D (which would be the most awesome, but needs one of the newer high-range 3-axis digital accels).

The AIM XTRA does have a triple axis 16g accelerometer. However, a 3D Kalman filter is computationally heavy. We will have to put a more powerful controller to do it. For basic flight control, its not needed.

In the future, we may implement something like that, although we will then be in the domain of missile technology...
 
The AIM XTRA does have a triple axis 16g accelerometer. However, a 3D Kalman filter is computationally heavy. We will have to put a more powerful controller to do it. For basic flight control, its not needed.

In the future, we may implement something like that, although we will then be in the domain of missile technology...

I also thought it was 3D; "why else have all those gyros and accels?". I figured you continuously integrated the IMU-derived 3-D position and compared it to the GPS position. How much more processing power would that need? That's the kind of professional-level avionics that I think some of us who fly really really high would be interested in buying...
 
Quite a bit more... Probably something like a 100 MHz floating point MCU.

The thing is, the 3D position would drift quite a bit over time. Unfortunately the GPS can lose lock during flight which would then make the IMU data very unreliable after a certain point (or if the sensors go out of range). However, it would still be more accurate than a 1D approach.

It is certainly something we want to look at doing in the future, which would then also offer the possibility of vertical stabilization.
 
Back
Top