Second flight went a bit better. Booster recovery strategy was better and seems to work good. Probably going to shelve it until LDRS.
hey what did you use for adding the velocity and altitude gauge on your video?
Second flight went a bit better. Booster recovery strategy was better and seems to work good. Probably going to shelve it until LDRS.
Hey there, I use RaceRender 3 on my MAC. It isn't the greatest, but gets the job done.hey what did you use for adding the velocity and altitude gauge on your video?
A stratologgers can also be directly programmed to have an apogee delay without having to set an altitude higher than what you will achieve. This will also result in a long constsnt beep during the start up sequence. I know this is an older post but thought id give my 2 cents. Im looking at making a 2 stage as well and this is a very good reference for me, thank you.I am going to use a StrattologgerCF to handle the cute deploy on the booster and I'll have a chute release on that. I also stuck a spare EggFinderTX in it as well. **Neat find: If you set the Strattologger's main deploy altitude to something greater than will be achieved, it will fire at 1 sec after apogee.** So, I have two charges, one set at apogee (Drouge) and the other set at 9999' (Main). This should fire each at apogee but one with a 1s delay. That is my only redundancy for the booster. 1 computer, 1 battery but 2 chances to fire the deploy.
There is some serious epoxy going on in the IC that you'll notice. That is to hold the bulkplate in place. I've blown coupler bulkplates out with charges on my pistons in the past so I went a little crazy here hoping to prevent that.
I was always targeting a static stability of 2.5ish for the whole stack but I had designed it around using 2 CTI 4 grain motors. An interesting oversight on my part was the stability once I used a heavy 75mm CTI motor in the booster and then a lighter 2 grain 54mm in the sustainer. It was back heavy and the stability fell to below 2 (I think it was ~1.8-1.9). So, we get creative. I am using a 2 grain 54mm motor in a 4 grain case with 2 spacers and an Aeropack MD Fwd Closure adapter. I'm pretty sure it accepts 5/16th threads. I was already planning to use this for providing the forward retention of the motor into the sustainer. I ended up make a few ~550g weights out of the CTI 54mm packaging, some lead shot and aeropoxy with a plastic center tube. I was able to bolt these onto the all thread supplying the forward retention to simulate a larger motor and manipulate the sustainer's (and ultimately whole stack's) weight and CG. This moved loaded stack to 2.26 and the sustainer to 3.19. It will work much easier when I get to using 2 larger motors of the same weight. In the picture you'll see two weights. I ultimately went with just one. Two improved the stability even further but hey, we do still have to go high right? If I had planned better I guess I could have added both and went with a 3 grain 54mm for the sustainer. Here are some photos of that:
View attachment 357761 View attachment 357762 View attachment 357763 View attachment 357764 View attachment 357765 View attachment 357766
A stratologgers can also be directly programmed to have an apogee delay without having to set an altitude higher than what you will achieve. This will also result in a long constsnt beep during the start up sequence. I know this is an older post but thought id give my 2 cents. Im looking at making a 2 stage as well and this is a very good reference for me, thank you.
I misunderstood what you were doing with the stratologger. That is actually really smart! Little bit of a loophole but hey whatever works. Have you done that method reliably? I didn't realize that stratologgers had that backup. IIRC stratologgers can only have drogue programmed to 9999ft as you had it, so a project over 10kft wouldn't work for this application as a 1s delay.Hey there!
Yep, I use the programmable apogee delay on my SLs that are used as a backup in the sustainer. With the booster, I was trying to get 2 separate charges to fire with one SL. For this to work correctly, I set the main to an unattainable altitude. On this channel, it will fire at apogee with a 1 second delay. Thus, you get get one charge go off at apogee (from the apogee channel with no delay) and then you will get a second charge (from the Main channel) one second later. Not totally redundancy but it gives me a little extra protection.
I misunderstood what you were doing with the stratologger. That is actually really smart! Little bit of a loophole but hey whatever works. Have you done that method reliably? I didn't realize that stratologgers had that backup. IIRC stratologgers can only have drogue programmed to 9999ft as you had it, so a project over 10kft wouldn't work for this application as a 1s delay.
Enter your email address to join: