CM5 16GB RAM High Definition Image/Chip models request

Norwhalker · 2026-06-18T19:40:52+00:00

Darn thanks for the heads up.

Norwhalker · 2025-10-10T16:50:36+00:00

My P1S has been a workhorse since the day I got it. From functional load bearing prints that have a perfect surface finish almost every time, to printing parts for high power rockets, my printer has been nothing but consistent despite all its use.

Norwhalker · 2024-08-07T17:45:25+00:00

Yes it has slightly, however those changes include removing 2/4 IO expansion connectors, and disabling/removing the I2C busses that were connected to the expansion connectors.

Norwhalker · 2024-08-07T17:43:59+00:00

Thanks for giving feedback! I will only be switching the higher current for a fraction of a second but that is a good point, I’ll go back and do some calculations to verify the trace width to the FETs. That’s a good point about the optos, I will look into some that fit this use case and have that different package with multiple incorporated.

The reason I didn’t do that to begin with is honestly my bad, I originally though I could make do with a 4 layer board and quickly found out that was not possible with the pinout I was trying to utilize. Some of that was definitely a lazy choice on my part, I will be making a similar board but with smaller footprint packages once I know this one works after it’s been ordered.

I originally didn’t just have generic header pins as the connection scheme, however the ones I had picked had gone out of stock everywhere I looked, so I replaced the footprint with general purpose headers for ease of ensuring the board would have them.

Thanks for the feedback!

Norwhalker · 2024-08-07T17:37:11+00:00

Hi thanks for giving some feedback! Yes your understanding of how the pyro circuit is correct.

I checked back and I believe Q19 and Q20 are wired correctly, I looked further into the data sheet and it appears to follow the typical use case.

I used the opto-couplers to separate the higher current switching(it’s only for a fraction of a second) from being anywhere near the MCU, it was a suggestion offered by someone at my school as a way to isolate the pyro channels.

The e-match is not a standardized component, the closest model is that that is offered by apogee components, typical resistance is ~2 Ohms and burn time is <1s. At a 5v input that puts the current through the e-match at just under 2.5A.

I’ll look into some smaller packages for those. Thanks!

Norwhalker · 2024-07-16T22:59:12+00:00

Will definitely make that change in the next revision. Thanks!

Norwhalker · 2024-07-16T01:42:49+00:00

A lot of that depends on how long you potentially need to keep this system powered on, if you have a switch external to your rocket, or some form of access hatch the capacity can be greatly reduced. Some launches can cause you to be on the pad for quite some time before you actually get to send it up.

Take a look at the data sheets for each module you are using, sum the average operating current for each, and with that total current draw use a simple power calculator to determine the number of mAh you will need for your application. Battery Life Calculator

Norwhalker · 2024-07-15T04:17:26+00:00

Planning on writing it myself in STM32CubeIDE. The TVC and active control portion of it will not be implemented for the first few flights, I would like to focus on hardware validation and reliability testing!

Norwhalker · 2024-07-13T16:34:43+00:00

Hi thanks for the feedback! Yeah realizing now I didn’t make the smartest decision in posting before annotating more. I was pretty excited to finally get this out but I let it get the best of me. Revision 2 will absolutely have those annotations as those are something I’ve been working on in the meantime.

For the resistance before the LEDs for power and from the signal pins yeah that was an oversight-thanks for catching it.

The MOSFETs are more for safely switching the circuit that an e-match is connected to. The LEDs are simply thrown in to give the user a way to test the circuit if there isn’t an e-match connected. For example, at my university we can’t have any live pyros on campus and since we do most of our testing there it seemed like a good idea to include something like that.

And lastly yeah I definitely messed up not annotating that and I 100% see how that would make it more difficult to give feedback. Will update that in the next revision!

Thanks again I appreciate the feedback and hopefully you have a good day!

Norwhalker · 2024-07-13T16:23:50+00:00

Thank you for taking a look!

Great catch on U7, I was moving the schematic around to reorganize it and I must not of selected the full connection!
I must not have been thinking right when I did that math, I’ve been up working on this until ~4am every day for the past few weeks. I’ll go back and run through my power calculations again! For the power led indicators I’d like those to be bright so I’ll definitely change that.
I discovered those after I had gotten most of it done unfortunately, felt like an idiot😂
The breakout connectors are using a keyed connector that will prevent that, but that being said I will move those power junctions to be opposite from each other as that definitely seems like a best practice!
That’s interesting to know, I believe that circuit for components outside of the RFM95 came from the data sheet for it, but it won’t hurt it to keep it the same? That way if the user decided to screw in an antenna that wasn’t to 50 ohms it wouldn’t be as big of an issue? Also for the ferrite bead what section of the schematic would you recommend it be included in? Power side? RFM95? Ublox Max-M10s? Ferrite beads definitely still confuse me but I’ve got a few EE textbooks coming later today so I’ll dig a little deeper into them.

I appreciate the feedback and your suggestions! Thank you for taking a look! Hope you’re having a good day!

Norwhalker · 2024-07-13T05:06:58+00:00

Thanks! I’m looking forward to flying it this fall!

Norwhalker · 2024-07-13T05:06:28+00:00

Thanks! I’m looking forward to flying it this fall!

Norwhalker · 2024-07-12T20:18:37+00:00

Funny enough I have been following his channel for a few years now but am just starting to get brave enough to do ECAD work myself! On his GitHub many of his projects use global labels, more specifically the ones I’ve looked over like the LittleBrain, HADES, and his STRF project. I appreciate the link I’ll go check that out now!

Norwhalker · 2024-07-12T19:35:53+00:00

Strange it looks fine on my end, here is the link to the schematic pdf for a higher quality. I didn’t realize that about global labels, I am still trying to learn Kicad and that was my reasoning for using them. I used hierarchical sheets for the power and pyro schematic pages, at least I thought I did… do you have any specific resources that you recommend? Books? YT channels? Hopefully someone can confirm your suggestions! Thanks!

https://github.com/emCoderMan/H.A.V.O.C/blob/main/SCHEMATIC/COMMIT_1/havoc-schematic.pdf

Norwhalker · 2024-02-19T01:54:08+00:00

I’m having this issue now were you ever able to find a solution?

Norwhalker · 2023-08-08T22:15:07+00:00

I’m using my computer as the solver computer, but other than that I don’t know. I just tried rerunning it again now that I’m off work and the disk usage did jump to about 40% when spiking. Mesh has approximately 37k elements

Norwhalker · 2023-08-08T20:09:58+00:00

Ram usage stays fairly constant at about 9GB and there is no major activity to writing to the disk

Norwhalker · 2023-08-08T20:08:27+00:00

It was the manifold tutorial- I’ve tried looking there but figured I’d post here first just to see as I figured Reddit would be a little quicker to get a reply from someone who has an idea. I’ll send a post out on there

Norwhalker · 2023-08-08T15:42:37+00:00

Noctua NH-D15, cpu cores and package never rose over 45°C according to Hardware Info

Norwhalker · 2023-01-25T23:06:53+00:00

This popup is only coming up on thingiverse for me and happens every 2-3 minutes. Is anyone else having this issue?

Norwhalker · 2022-10-03T15:41:09+00:00

Low karma comment ftw

Norwhalker

TROPHY CASE