should be the transitive dependencies, not just top-level (so the lock file or equiv) or you just reward the "barely wrap it and give it a new name" js crowd even more.
What’s the deal with 5v, 3.3v and 24v “standards” for sensors? It seems like there are really three different markets and it sucks because crossing “lanes” is really annoying. I like how you all made the qwik connectors “just work”, but now that I’m trying more industrial stuff I’m having a hard time figuring out how to get my 24v world to play nicely with the 3.3v world but of course my 24v world only wants to do SPI over 5v.
Anyhoo, sorry we can’t just stick to the technical drama.
Those levels are based on the electronics themselves. Earlier circuits used TTL which needed higher voltages to signify a "High". Newer CMOS based electronics need less voltage.
Lower voltages help with power savings. Higher voltages can and do work better in high power, high noise environments though! 24V as you see is still very popular and useful inany applications.
great question! so historically microcontrollers (and sensors) were 5V 'CMOS' power and logic. this was way better than the up-to-12V for TTL logic but over time the desire for higher clock speeds / faster IO / lower power means the voltage needs to drop (since power = current * voltage lower voltage is lower power) the next voltage standard became 3.3V. these days, even 3.3V is a 'bit high' and we're seeing lots of device that are 1.8V or 1.65V or even 1.2V max (yeek!) one thing we do for all of our sensor breakouts is add level shifting up/down as necessary so they work with EITHER 5V older boards (yay no need to throw them out!) or with the newer 3.3V boards (woo forward compatibility) level shifting and regulation also reduces the risk of damage from over/under volting or plugging stuff in backwards. this is documented here: https://learn.adafruit.com/introducing-adafruit-stemma-qt/st...
maybe someone from sparkfun could post advice for you here too...
Ooh thank you! I often forget that everything is a capacitor/resistor/inductor all at once and i see how at higher frequencies that starts to matter! I think the 24v stuff is also more low frequency signaling over longer distances so rise/fall time is less of a worry but voltage drop / noise is perhaps more of one. Thanks!
Fwiw, I’m team adafruit on this. Hope it works out for y’all
> What’s the deal with 5v, 3.3v and 24v “standards” for sensors?
Historical garbage and different manufacturing technologies. Be happy if you can get away with only 5V and 3V3 rails in your project. 24V is usually to interface with industrial sensors. And sometimes you see 12V as well, for stuff that's RS232 based.
And on top of that you got a fifth standard, 4..20 mA current loops. That one is used for long range transmission of analog values of a single sensor per wire pair, with 4-20 mA being seen as the value (4 mA = 0%, 20 mA = 100%), and anything less being seen as a cable break, anything higher as a short circuit somewhere.
4 to 20mA signaling is only the start of a very specific rabbit hole. Someone had the brilliant idea to encode digital signals on top of the analog current loop. The result is the HART communication protocol, which is old, bloated, confusing, quirky - and it is really popular in industrial automation.
Ah, yep. Did conflate coal with oil. I guess my nice analogy doesn't quite hold, but the point stands that plastic originally came from organic matter and is technically biodegradable.
They have a strange business model. Their chips are massive. So they necessarily only sell them to large customers. Also because of the way they’re built (entire wafer is a single chip) no two chips will be the same. Normally imperfections in the manufacturing result in some parts of the wafer being rejected and other binned as fast or slow chips. If you use the whole wafer you get what you get. So it’s necessarily a strange platform to work with - every device is slightly different.
Yes! It gives me quite a bit of confidence and makes refactoring easier. Pure rust backend is basically hassle free now with LLMs. Frontend still ts / svelte because of ecosystem and training set.
Elm is a great front end language for LLMs, its simple and safe and the entire language is in the training set and its not under active development right now so no breaking changes.
The idea of doing a thing (or having done the thing) and the actual DOING of the thing are very different. See this a lot where people think they want to be a woodworker or a baseball player or an author, but the actual _work_ of sweeping dust, doing 200 hits a day off a tee or grinding out words by deadlines are not as appealing as the halo or mystique of the final product once made the activity seem. this doubles on the effect that humans are terrible at predicting what will make us happy. so, i am glad this author was self aware enough to follow their bliss, but the last paragraph made me wonder if their introspection was fully resolved.
Every writing group has that person the keeps restarting their project, or abandoning a project when it gets hard, to start another one with another 'great' idea.
The upshot is, they don't want to do the hard part - continuity editing, developmental editing, hell, just finishing the dang thing. Even the boring chapters you didn't really have any idea what was going to go on there.
Writing, as an occupation, is a whole lotta schmoozing, attending conferences, volunteering, promoting. Maybe 1 month of writing a year, for 11 months of the hard stuff.
I have a buddy who says he always wanted to start a bar. I said, You like budgeting? Taxes? Hiring? Firing? Stocking? Remodeling? Promoting?
Nah; turns out, he just likes to hang out in bars.
The only reason you start a business is, because you like to run a business.
The only reason you become a writer is, because you like the business of writing.
there was a funny joke that chatgpt removes the critical part of being a writer which is hours staring at a blank screen, then deleting everything you've done on a weekly basis.
reply