442 karma · joined April 6, 2020
My research shifted, and I start making sensors using fibre and similarly sized capillary tube. It all got cleaved, spliced to assemble, cleaved some more, spliced again, then polished to spec. Getting the he process down was a pain, but the results were super satisfying.
I haven't had this much time off in over a decade and it's amazing. I've been hoping to get inspire for some outdoors or running related mechanical design/prototyping projects, but nothing yet.
For keeping challenged long term, I've got a few products I finally have the time to do prototypes for and some chances to work in new areas.
It worked brilliantly for a while, but since things were getting done fast, well, and cheap, the expectations increased. I gave notice two weeks ago without a job lined up.
On a week of vacation leave, I went and helped an extended family member in their home business. It combines the best aspects of my past three jobs. High tech, optics, design and manufacture, it's hard, and it's fascinating. There's a clear path to profit, with demand. Might be weeks, might be months, but in the meantime I can't make enough to cover my costs.
I can't risk my family's security. Having loved out of my car while studying, despite over a decade passing, the memory is fresh.
A pay cut would be fine, worth it, but the risk feels so high.
I've just taken a week off to help extended family with a project, and it's reminded me what a good job is.
As others have mentioned, the 200amps of this case could be reduced substantially by running filaments in series (can be done with 6.3v heaters as the error from a common 5v or 9v supply is more than if you pair them up and use a 12V supply) though this introduces the failure mode of old Christmas tree lights.
Source: I make vacuum tubes.
The UV light method worked fine, came out to about $600US per fibre with 32 gratings each, not exactly cheap. The measurement unit was on the order of $20k US though.
Well done completing the Phd!
The algorithm I figured out was mostly equivalent, though about 3x slower than implementing Goertzel. In my use case, it was already a win hitting the product requirements, but implementing Goertzel allowed background functionality to operate better while capturing data.