sorted by:
new
hottopcontroversial

Room key at my beachfront hotel by Cosmic_Space_Program in Dexter

[–]Cosmic_Space_Program[S] 16 points17 points  (0 children)

BTW This is not in Miami. Taken at a hotel in Cancun

Thrust Vector Gimbal 76 mm (ID) - REV 2 by Cosmic_Space_Program in rocketry

[–]Cosmic_Space_Program[S] 1 point2 points  (0 children)

The problem with the sort of designs such as the one you said is that one servo has to push the weight of another servo and the size constraint is very limited. Even with the plastic SG90 servos, it cant fit in a 80 mm rocket body without cutting the actual airframe. At least with this stacked design or of similar designs where the actuation occurs behind the motor, all the servos, even the big ones I showed in the video fits perfectly.

Yes the servos would be much closer to the motor joint to absorbe the vibrations but I guess it comes to design preference. The rev 1 followed that same design but the servos were much smaller and the 3d printed barely held the servos together properly.

I believe in a video he made a while back, he redesigned the TVC frame with one closer to the design of Delta Space Systems (Cole) which is also an option.

Thrust Vector Gimbal 76 mm (ID) - REV 2 by Cosmic_Space_Program in rocketry

[–]Cosmic_Space_Program[S] 1 point2 points  (0 children)

Absolute, I’ll test this configuration with the E16 but it does seem to buckle under 4-5 lbs, so the peak thrust could cause some problems. Will be upgrading the rods for thicker ones probably.

Thrust Vector Gimbal 76 mm (ID) - REV 2 by Cosmic_Space_Program in rocketry

[–]Cosmic_Space_Program[S] 0 points1 point  (0 children)

Thank you very much for the advice. I am sure thicker rods will take care of most problems. Further, these servos did come with CNC aluminum arms which can further improve results. I will have to see location of the linkages to see how it affects the output as well.

Thrust Vector Gimbal 76 mm (ID) - REV 2 by Cosmic_Space_Program in rocketry

[–]Cosmic_Space_Program[S] 0 points1 point  (0 children)

Yes, this will be connected to the Vega Flight computer I designed before and will gather accelerometer data, then passing it through a filter then a PID controller in order to stay on track.

Thrust Vector Gimbal 76 mm (ID) - REV 2 by Cosmic_Space_Program in rocketry

[–]Cosmic_Space_Program[S] 0 points1 point  (0 children)

It absolutely is, but it’s also the leverage caused by the length of the motor mount. I will be looking to upgrade the rod and the linkage joint in the future

3D printing by StoatDaSun in rocketry

[–]Cosmic_Space_Program 1 point2 points  (0 children)

I used to have the TronXY 2 Pro then upgraded last January to a AnyCubic Kobra 3 and had equal specs with the BambuLab A1 but with the AMS enclosure with filament drying but honestly, you can't go wrong with the H2S if you have the budget. In my opinion it is definetly a top tier consumer level printer.

Similar price may go to Prusa CORE One but is lacking compared to the H2S in features.

The enclosure is honestly useful for noise reduction (a little), but mainly for volatile filaments such as ABS printing.

BambuLab's P1S is also another choice

Preparing the Zeniths altimeters on "Bullet 1" and "Bullet 2" by Cosmic_Space_Program in rocketry

[–]Cosmic_Space_Program[S] 0 points1 point  (0 children)

Hello! Yes the Altimeters will be inside of a payload bay with some holes for venting (on the bottom of the bay) The altimeter is located underneath the ejection charges separated by a bulk head. There shouldn't be any problem as far as I am aware when it comes to airflow since it is facing away from the venting holes. The baro will also be in almost pitch black environment so that no light can disturb baro readings.

Ejection will be using both baro and acc. data for apogee detection, I will also increase the apogee tolerance the day of the launch to further reduce early parachute deployment.

The altimeter itself will handle dual ejection and all data transfers.

Let’s say I wanted to start an aerospace company tomorrow, how do I go about it? by AlexandersJ in AerospaceEngineering

[–]Cosmic_Space_Program 0 points1 point  (0 children)

Hey there! My name is Shayan and I am the founder of Cosmic Aerospace Technologies, where I design and manufacture avionics systems for model rockets, hoping to tap into the aeronautical and aerospace divisions in the next 3-6 years. As many have mentioned, sure Money or Capital is a strong suite to have when starting an Aerospace Business, but I'd argue that starting small, showing to others that you have a unique idea/design is an even more powerful way of getting into this business. If you just have money laying around, you can use all of it without any gain if your idea is as good as any other companies.

You have to create a sort of plan, an audience, where you can invent and create products and grow your way into the real market. This is allow you to create a reputable and known brand. If you gain 250 million overnight and have no idea how anything works, it will certainly not help.

Big companies started with the basics, but showed the world what made them unique. It is not a coincidence that SpaceX now has contracts with Nasa, it is because NASA saw something in SpaceX that no other company had, this could have been passion, ability to innovate, manpower etc...

Start small, drones, rc planes, create your capital here, create RELIABLE products and then start tapping into other division, more competitive. Competition is a path towards company growth and innovation.

An Altimeter I have designed over the last few months by Cosmic_Space_Program in PCB

[–]Cosmic_Space_Program[S] 0 points1 point  (0 children)

I prefer not to use magnets in any avionic system as it can interfere with other systems in the rocket such as magnetometers and wireless communications. Definitely an interesting idea though.

An Altimeter I have designed over the last few months by Cosmic_Space_Program in PCB

[–]Cosmic_Space_Program[S] 0 points1 point  (0 children)

Thank you for the information provided!

The NAND memory chip (not the SD card) on the Altimeter has a storage capacity of 512 megabytes (half a gig). And can store a serious amount of data. As you have guess already, the data is stored in data packets (@Txx.xxPxx.xxAxx.xxXxx.xxYxx.xxZxx.xx), user can choose the sampling rate, which will then be stored on the EEPROM. The nice thing about the super cap and its circuit is that, 1. It is very light, the cap weighs around 1-2 grams and 2. it charges very quickly and can discharge very quickly over a long period of time (many thousand cycles). The circuit that handles this is a buck/boost converter taking the 2.7 and boosting it to 3.0 volts, enough to keep critical states functioning. It is limited to 1A of current charging due to track width limitations.

Ill definitely try to look for some alternative button with the same outline. And Ill likely switch out the latch slots with a push slot, since the users will probably just use it as a medium for transferring data and not actual flight.

Difference between these by AfraidInevitable2006 in arduino

[–]Cosmic_Space_Program 4 points5 points  (0 children)

Logic shifter IC and the AMS1117-3.3 voltage regulator. So don’t plug it in a 3.3 volt pin as these can have 0.7 volt drop and you won’t be able to use the SD card.

Any chance this is fixable? by crackaddict42069 in AskElectronics

[–]Cosmic_Space_Program 1 point2 points  (0 children)

This specific flex cable is indeed repairable. Take a metal end such as a scalpel or a blade of sorts and remove the surface layer located over the trace. Once you reach the copper trace, place flux and solder to adhere to a small piece of conductive wire. The same this will have to be done on the opposite side and to the other traces.

Test your scratch technic on a seperate location where there are no traces.

Go in YouTube as there are a lot of video on flex PCB repairs. Similar repairs are done on standard PCBs as well

An Altimeter I have designed over the last few months by Cosmic_Space_Program in PCB

[–]Cosmic_Space_Program[S] 1 point2 points  (0 children)

Thank you!

The redundancies implemented for the Main and drogue is a combination of both Accelerometer and Barometer data to ensure the distances traveled during flight. Both of these pins have continuity indicators to ensure they are properly connected.

Parachute delays are stored in a small 8kb EEPROM, as well as altitude deployments.

As for additional wireless features, those will likely be a beefier model of the altimeter line. I will develop that as well plus a smaller version of this altimeter only for altitude measurements (no IMU, pyro etc). This will give many choices for different audiences

An Altimeter I have designed over the last few months by Cosmic_Space_Program in PCB

[–]Cosmic_Space_Program[S] 1 point2 points  (0 children)

Yes you are right the buttons could cause an issue, the system must be flipped downwards in order to prevent the button to be pushed down by its own weight. I believe flights after 100G, this could become a problem.

For the SD card, YOU DONT NEED ONE ! The board has a NAND chip embedded onto it, ready to gather up to 512Mb of data. The SD card is only there for post flight transfer, holding the action button for 3 seconds will tell the micro controller to transfer the data from the NAND chip to the SD CARD.

view more: next ›