Show HN: Cygnus-X1 – A Thrust Vectoring Model Rocket Flight Computer
github.com
github.com
It was launched at the 5th Annual Scottish International Rocket Weekend, in Kelburn Country Park, Largs, Scotland. [0]
I was 17 years old and a member of the Paisley Rocketeer's Society [1] - one of the oldest model rocket clubs in the world, led by the late John Stewart.
Gyroc 1's vectoring was accomplished by controlling a model rocket engine by way of 2 axes controlled by a gyroscope. Subsequent Gyrocs have been made and flown. [2] (Note: the article states 1995 but the 5th IRW was in 1996 ;) )
The model rocket launched to a height of about 1-2 metres, and only managed to hover for a couple of seconds before the model rocket engine was spent, but at the time it was a glorious flight.
[0] https://www.gbnet.net/orgs/staar/report.html
[1] https://www.paisley.org.uk/paisley-history/paisley-rocketeer...
https://photos.google.com/share/AF1QipOiNJAihxhEA67VCx54dzVX...
I’m not sure what the defined red lines are in the US, but most people building rockets big enough for the feds to worry about are following the model rocketry code and associated with NAR/Tripoli, so at least have access to more expertise to help follow the rules.
Getting the big motors requires multiple certs from those orgs, so the system tends to be self regulating to some extent, since you can’t test your code without the hardware.
I know Joe Barnard of BPS has mentioned a few times that he doesn’t release his code because the laws are unclear, and lawyers familiar with them are expensive.
The issue isn't you building a rocket big enough for the feds to care about, but the people who can build (and use) big rockets using your designs. Iran for example relies heavily on open source for its drone program.
HP for example is still heavily involved in the investigation of Huawei's export of HP hardware to Iran. They didn't get to just point and say "go talk to them."
[0] https://www.justice.gov/usao-az/pr/former-raytheon-engineer-...
I think I’ve made the emotional pivot to UAVs instead because swarming and autonomous guidance & control is one of the more interesting parts to me and even if it weren’t likely to draw ’attention’, the development process for rocket is stymied by the characteristics of rocket propulsion.
I've thought about getting back into the hobby and it looks like all the hybrid systems have disappeared. The ATF permitting for solid fuel motors seemed pretty onerous back in the late 90s (I always flew at launches where I could purchase reloads for my Aerotech RMS on-site so I didn't have to deal with transporting motors) and I assume it got worse after 9/11.
Anybody know what ever happened to the hybrid systems? Aerotech's website looks like it stopped being updated about the time I left the hobby. Same goes w/ their competitor Hypertek (which I thought had a ridiculous ground-support system).
This is such a hilarious phrasing but it nicely captures the feeling!
Surprised there’s no mention of Joe and his “AVA” on the git.
I will say that I am seriously impressed with folks that are able to combine so many disciplines, especially when each domain seems to have its own set of unique hard challenges.
The first major challenge is procurement! I was able to get gunpowder from a friend who has contacts in a fireworks shop. Constructing it required minimal machining and was a lot of fun. Finding parts and machining timing for liquid fueled rockets is harder!
I spent a long time in Kerbal Space Program trying to increase delta-V by using oxygen breathing jet engine boosters.
Do petrol propellers work for model rockets, to at least get a boost to a thinner atmosphere?
I know nothing about thrust or vectoring, so that's my only feedback.
Tivoization is only defined as "They can modify or execute arbitrary code, you cannot." If neither they or you can modify the end product due to technical reasons, it's not Tivoization. FSF said:
> Tivoization: Some companies have created various different kinds of devices that run GPLed software, and then rigged the hardware so that they can change the software that’s running, but you cannot. If a device can run arbitrary software, it’s a general-purpose computer, and its owner should control what it does. When a device thwarts you from doing that, we call that tivoization.
The anti-tivoization clause basically says "the necessary technical information and data (Installation Information) must be provided to the user, so that the user can run whatever software they want, just like the developer can", for example, if firmware update is supported, the protocol must be documented and provided to the users. If signature check is used, there must be a way to get a key or bypass it. However, if nobody can modify the system in its final form (e.g. if the firmware is in OTP ROM, if the JTAG interface has been permanently disabled), it's not Tivoization, no action is needed. Arguably, when you disable EEPROM write via an one-time fuse, it ceases to be a general-purpose computer at that moment.
Thus, you can still create a product that has been completely locked down, if it has been really locked down with no backdoor to ever be unlocked again.
GPL says,
> Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
> If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).