Also install tooling, swear when a tap or drill inevitably breaks and gets stuck in a very expensive part, etc.
2,296 karma · joined May 2, 2014
Get in touch:
frtherien@gmail.com github.com/auxym
Also install tooling, swear when a tap or drill inevitably breaks and gets stuck in a very expensive part, etc.
arm-none-eabi-gcc changing its behavior for bitfields would probably break 99% of existing arm MCU codebases.
For one thing, you can chain queries, SQL style. IE, you can use the table that is the result of a query as input to another query.
Low pay, but enough for a good lifestyle in a LCOL small university town.
Non-phd doctorates I'm aware of would be MD, Psy. D, JD.
It's definitely a huge brick though, can be intimidating. I think he picked the Ferguson book because it's more approachable, cheaper and covers the essentials for the class (and not too much else).
For ICEs we used Ferguson and Kirkpatrick when I took a graduate level ICE class. It's concise but good. I'm not sure it's exactly what you're looking for as a hobbyist though, it's a lot of thermodynamics and associated math, not a lot on practical implementation of engines.
If you're looking to rebuild engines and such "mechanical engineering" is probably the wrong road to go down. I don't have specific recommendations, but maintenance manuals or trainings for mechanics, millwrights a d metal workers might be closer to what you want.
You can create a complex, nonlinear, numerical model of the full system in as much detail as you want (eg implemented in a block sim like Simulink, or MBD software like ADAMS, or just A and B matrices derived manually but incorporating nonlinearities like sin, etc).
From that you can evaluate a whole bunch of finite differences around an arbitrary state (linearization point), which are the components of the A and B matrices. This is an approximate, linear model which is "close enough" in behaviour to your real model for states that are "close" to your linearization point.
In practice if you're moving far away from your linearization point (eg a 6 DOF robot arm with large displacement of all joints), you'll need to re-compute the linearization each timestep, around the current state, and re-compute the LQR or MPC solution from this "new" approximate model.
Here's some linearization code I wrote for a library that's used to teach controls and robotics in undergrad. It takes as a input a "model" that's an arbitrary function that generates the next state from a given state, and computes the jacobian matrices by finite differences: https://github.com/SherbyRobotics/pyro/blob/43dcb112427978ff...
Not convinced it's the best, as I didn't really enjoy the class, but that was mostly due to a poor lecturer. I'm also not convinced that it's the most relevant for you, as you seem to be looking more into "small batch prototyping", rather than mass scale manufacturing.
Still, it's a good book for getting an overview of what is out there in terms of processes and figuring out what would be appropriate for your needs. It's not a good book for getting into the nitty of, say, injection mold design, which is highly specialized.
I do believe Protolabs offers small batch injection molding for "reasonable" cost, probably as reasonable as you'll get for small batch. From my memory they also have a design guide PDF that you can download or they send when you register. That's probably a good place to start. Also try searching reddit r/mechanicalengineering for "injection mold" and similar queries, I do remember a few people asking for resources and getting good replies.
Neither is retirement, obviously, but you are correct that being financially independent gives you the freedom do do what you want. Whether that is time off between jobs, working on independent projects, etc.
Then I found a job which pays significantly under market but that I actually enjoy doing. My priorities have changed a lot.
Unfortunately said job is highly unstable and provides little opportunity for transferrable skills, so I still aim for a 50% savings rate, for peace of mind.
The definition of fatigue is a small crack (in fact microscopic in the beginning) that grows through the application of cyclical loading (typically about 10k cycles is the lower bound for high cycle fatigue, which does not involve macro yielding).
Thus a fatigue failure would look like a fully ruptured part , usually with two distinct zones of the fracture face: one smooth zone from crack growth ( sometimes with characteristic "beach marks") and the final sudden rupture which is usually rough.
Especially on a prototype I'd recommend them. Prototypes are really expensive, a complete supply of Nord locks for your project is probably less than a single one-off CNC part.
Note that Nord locks are specced to be single use. Not that I've never reused some on prototypes, but, well, I'd never do it on a life-critical joint that is meant to be taken apart often.
Emphasis on properly torqued: in the field threads or bolt heads might be dirty, or torque wrenches might be out of calibration, adding even more uncertainty.
One advantage over C++ is that you don't need to learn make, IDEs or a complex build system. The nim compiler and the nimble package manager just takes care of building for you. "nim c main.nim" and off you go, ending up with a single executable, no matter how many imports, modules, etc you have.
I do recommend this as a gentle introduction: https://nim-by-example.github.io/ and recommend you use VS Code with the Nim extension by saem.
For the other 20% where I don't even know where to start, I look up a solution on reddit, try to understand it and re-implement it myself, and learn something new. The 2020 day 13 problem mentioned by GP was indeed one of those for me last year.
Develop a new ceramic material for advanced turbofan engines? Not tech.
Web front end? Oh yeah, tech.