cyanoacry
Joined 14 years ago
Joined 14 years ago
We're building a medical device that allows us to measure BP continuously, in real time. (We're a Caltech spin-out and found some new physics that we want to get to market.)
Desires:
- Experience with FPGAs / FPGA integration
- Experience with Linux on an embedded system
- Have dealt with real-time systems
- Experienced in Rust / Python
.. but honestly, if you can tell me what a GPIO is and how it relates to the userspace I/O driver, we'll probably get along.Here's the official job listing: https://esperto.health/careers/sr_firmware.html
If you think this is interesting, email me, I'm the CTO: [email protected]
Best of luck, and I'm looking forward to your next venture!
I see now that the US gets to take GPS (and the fact that the Air Force pretty much runs it single-handedly) for granted. We are seeing _some_ problems (like the GPS III block upgrade and OCX, ahah), but the org chart seems to be considerably simpler than what Galileo's got to deal with.
Frustratingly, both of these groups have great content (manuals, tips, documentation) uploaded to Yahoo Groups. It's going to be a real loss.
But for lasers, I thought the frequency was driven by the energy difference between electron states for a given species? How do you synthesize an arbitrary frequency for a laser without something crazy like a FEL?
But, Wolfspeed's SiCFETs /do/ have a published SOA (see fig 22[2]), so maybe I should revisit this...
[1] Figure II-3: "Visual Image of the IRF1405Z failure. This type of visual pattern is more attractive when observed on the surface of the moon, instead of on the surface of parts that are trying to land there." http://www.irf.com/technical-info/appnotes/an-1155.pdf
[2] https://www.wolfspeed.com/downloads/dl/file/id/145/product/1...
The places I've worked have pretty rigorous style guides, and I personally try my best to make schematics readable and understandable. I suppose this is the same thing as code quality guidelines: you can set expectations and examples, but folks don't necessarily have to follow them.
My cooler projects are all stashed away somewhere in a company drawer, but here's one that I did early on: https://bitbucket.org/cyanoacry/ee91/raw/5d934fdc18e556938dc...
I have to nitpick at this a little bit as a professional EE who works in high-reliability electronics. Wearout rates absolutely do depend on temperature (and thus heat), and thus the chips used here will have a shorter lifetime than those with active cooling. Now, whether that lifetime will be long enough for the common user is another question (maybe it's 1 million hours of life that get reduced to 100,000 hours, so not normally noticable).
As the old Apollo-generation engineers start to retire in the space industry, there _is_ fresh blood coming in, and even at larger companies, I've found young folks in top positions. It's just not widely advertised.
A typical builder's log: http://www.cozy.simpex.com/
source: I, too, am building a plane in my garage. https://twitter.com/acozyplane
Lots of content (made mostly for themselves), but the writing style is pretty nice and there's a large variety of projects.
Caltech, Dabney House. Currently CTO of Esperto Medical (a medtech startup), focusing on blood pressure measurement.
Formerly SpaceX, Boeing Satellite Systems, and Phase Four. So far, I've somehow I landed 3 spaceships without incident... :) (I was reentry Mission Director for CRS-10, 11, and 12)
http://wsyntax.com