Relief Valves

Not a particularly exciting topic, but relief valves are very necessary to most rocket designs. They come in two major flavors: resettable (usually called relief valves) and non-resettable  (usually called burst disks). Both exist to protect your system from inadvertent over pressurization and the related failure: either burst, leak, or component failure.

The first thing you need to do is figure out where they go. A good rule of thumb is that if it can be closed off, it needs to have a relief valve. If you have a small line, <1/2″, and a propellant incapable of increasing in pressure (i.e. not a cryogenic liquid or a monopropellant), you can skip the relief valve in that section. On tanks or other large volume containers, you always need a relief device; if you look at commercial devices like dewars or gas bottles, you will see that they usually have relief valves or burst disks.

Burst Disks – I have always bought commercial burst disks and I would recommend purchasing the disks. They are hard to make as the exact thickness and mounting is important and you have to do batch testing to verify. Use burst disks on things you don’t expect to ever overpressure, like gas pressurant bottles, and be warned they can be VERY loud when they go off.

Relief valve – Lots of designs exist for these, both commercially from places like McMaster or Swagelok and designs from sources like NASA SP-8080. They are good if you need to adjust the relief pressure or if you expect frequent overpressuizations, like on cryogenic vessels. One note is they have some hystorisis, that is to say that if set to 100 psi, they will start hissing at 95 psi, flow fully at 100 psi, then vent down to 90 psi, or something similar.

Remember that safety is the most important thing when you are testing, because if you are not safe, you may not be around to finish the test. And while good procedures and 100% functional devices are good to strive for, relief valves are great to have for when something goes a little wrong with the system.

For reference this is what we are planning to use for relief devices:

– On the Earendel vehicle there will be a burst disk on the pressurant tanks (paintball style) and relief valves on both propellant tanks (McMaster Carr 9137K11).

– On the engine test stand, there will be a burst disk on the Nitrogen Cylinder, a relief valve and a burst disk on the LOX Dewar, relief valves on the propellant tanks, and a relief valve between the isolation valve and the run valve on the LOX run lines.

– On the igniter stand, there is only one relief valve and that is built into the GOX bottle.

3D Printing Rocket

Rockets are perfect for 3D printing technologies, well at least parts of rockets. Bodytubes, maybe not so much, control electronics, also a no, but rocket engines – there’s the ticket. They are relatively small parts with complex internal features and are manufactured in low quantity. Now for the bad news: they get very hot and very cold; they have small features; they are highly stressed. This means, in general, you can only use metal as a material. This limits us to DMLS, Casting and Infused metal.

DMLS is awesome; you send out a part as an stl file and you get a solid metal part back in a couple of weeks. While I have built various 3D printed parts, sadly none of them are mine to show, so instead check out this awesome work at Rocket Moonlighting. For rockets, DMLS materials are usually Inconel or PH 15-5 with other high temperature alloys such as Cobalt Chrome available as well as lightweight aluminum.

Infused metal is somewhat different from DMLS in that a porous version of the model is made, then infused with another alloy. Usually this is 420 SS fill with bronze. It is cheaper and quicker turn around than DMLS but at the expense of detail, only going down to around 40 mil holes vs DMLS 16 mil. Infused metal is also better with overhangs than DMLS. For these reasons, we are using Infused Metal for our igniter and injector, but if we were to make a regen engine we would probably use DMLS.

3D printed (infused metal) igniter as printed. Spark on top; from left to right fuel, pressure, oxidizer.
3D printed (infused metal) igniter as printed. Spark on top; from left to right fuel, pressure, oxidizer.

Casting is just like any other casting method, but it uses 3D printed wax. This technology has been around for decades now and is very common in low volume parts. It is a good technology, but it has a hard time dealing with long passages and thin walls, as well as only being commercially used with easy-to-cast alloys so we are not using it.

Rules of thumb:

If you can machine it, just machine it; it will probably be better, cheaper, and most likely faster.

Infused metal seems to build up more than the stl; allow for a ~4 mil growth.

You will have to tap most threads and, frankly, the surface finish is much improved by taping.

O-rings work fine with any of the 3D printed parts.

On DMLS, limit overhangs to 45 degrees or live with added supports during build.

ASK YOUR VENDOR about what post machining / supports they are adding.

Have a build direction in mind when you design the model; it really helps.

Surface finish isn’t great on DMLS or infused.

Long small holes are much more likely to clog than short small holes.

Make sure you have flats for post machining or wrench tightening.

That’s about it; give it a shot. Nothing says I’m living in the future like 3D printed metal parts arriving in the mail.

Igniter Software

So now we are sitting around with an igniter and test stand all ready to run it, so we’re good, right? Well not so fast, as some software is necessary. I’m not a software engineer or a CS major by any stretch of the imagination, so I apologize in advance for any painful coding mistakes. It is open source code though, so feel free to tell me what to change or just go ahead and change it on your own if it gets too bad.

Since we are using Arduino for the hardware electronics, we will be using the Arduino  programming environment. Rather than me rehashing how to program in Arduino, check out their website which has some awesome tutorials.

The basic program that we will be using consists of the following parts:

– Initiate variables

– Serial Communication
We use this to get the data from the Arduino on to the serial monitor and to send commands to the Arduio. We don’t have a GUI yet so the commands are:

1- turns on GOX valve
2- turns on IPA valve
3- turns on spark exciter
q- turns off GOX valve
s- turns off IPA valve
e- turns off spark exciter
a- arms the autosequence
s- starst the autosequence
z- aborts the autosequence

This is actually surprisingly easy to use, but we will be adding a GUI over the next month or two.

-Autosequence
You manually set times and what valves change state at those times. The code then iterates and, every 20 ms, updates analog inputs and checks to see if it is at the next time yet.

-Analog Input
Arduino takes 3 data samples separated by 1 ms and averages the data. It then converts the voltage signal to a pressure or temperature.

So that is pretty much it, and you can see a picture of an initial data sample below.

A Data Trace! Temperature is going up after the test because the thermistor is on the outside. All good to go and do some testing.
A Data Trace! Temperature is going up after the test because the thermistor is on the outside. All good to go and do some testing.

For those of your that are interested, the code is here as a pdf (originally a *.ino for arduino)  IGNITER_DAQ_LJD_v1 and also in our documentation pages. As with everything else on the site, it is available for use under Creative Commons Attribution-Share Alike.

Igniter Test Stand Electronics

For the igniter test stand, we chose to keep things simple, and, as such, this are our requirements for the electronics:

– 2x Digital Out: Solenoid valve control (12 V)

– 1x Digital Out: Spark exciter (3.3 V)

– 2x Analog In: Pressure transducer  (5 V ratiometric)

– 1x Analog In: Thermistor (10K NTC)

– 1x Serial communication

– Programable autosequence, 10 ms reliability

For this set of requirements, the obvious solution is a microcontroller and it is hard to beat an arduino for accessibility and ease of use. After looking at some spec sheets, we chose the Leonardo due to its native USB communication and the compatibility with Arduino Micro for future flight electronics.

Just like you start a pluming project with a P&ID, you start a electronics project with a circuit diagram. Below is the diagram for the igniter stand as it is currently built in a breadboard configuration.

The schematic gets cluttered in a hurry. It is actually about as complicated to prototype as it was to sketch out.
The schematic gets cluttered in a hurry. It is actually about as complicated to prototype as it was to sketch out.
The pressure transducers and op-amp breadboard. It works well enough in a breadboard, but anything more long term should be soldered.
The pressure transducers and op-amp breadboard. It works well enough in a breadboard, but anything more long term should be soldered.
Arduino, Relay Board, 3.3 V regulator. There is also a 3.3 V channel out of the Arduino, but we need ~0.5 amp so we had to used a stand alone regulator.
Arduino, Relay Board, 3.3 V regulator. There is also a 3.3 V channel out of the Arduino, but we need ~0.5 amp so we had to used a stand alone regulator.

 

Now, everything shown above is sufficient to build a copy of the electronics, but you will need the software which we will post about tomorrow before you can run the stand. Some of the important components are listed below.

Relay Board – SainSmart 4-Channel Relay Module or similar. Note that it is a High Level trigger!

Op Amp – LM358.  And an good site for op amp theory.

Pressure Transducers- TBPDANN150PGUCV This is a non-amplified sensor, which is why the op amp is necessary. It is also very cheap at $20.00, but it really complicates the design. If we were going to do this over, and we will, we would buy some amplified transducers at $60.00 instead.

Thermistor- Finally the thermistor I used and a nice tutorial from adafruit on general thermistor properties.