Notices by aleksorsist (aleksorsist@fosstodon.org)

This is the silliest little buck boost, I love it so

https://www.ti.com/lit/ds/symlink/tps631012.pdf

I can't wait to smoke test this thing

@azonenberg @whitequark @urja guess we doin HDL now. Once I finish these damn boards

@azonenberg @whitequark @urja I joked about it being a quasi CPU and it is quickly becoming straight up a CPU, I love it

@urja @azonenberg Yup! It would have edge modules, slope and delay timers. Basically you feed it code (a list of conditions really) and the PC increments every time a condition is met. Here's a napkin sketch:

@azonenberg @urja I wouldn't want to hard code any protocols. I'm trying to find the core modules that everything is built on and make those into atomic instructions. Then a compiler can take the current state of the scope (i.e. what is an ADC code in volts, what's a sample in time units) as well as a description of the desired protocol, and spit these instructions out.

@azonenberg @urja that's actually more what I'm thinking. Basically the modules are always looking at the data, it's just new parameters that get clocked in once the previous condition is met. I can't think of a trigger that doesn't need a sequential list of conditions (with commands across channels treated kinda like multi-threading)

@azonenberg @urja ah, you want to clock off the signals, gotya. I was thinking of basing everything off of counting samples so it'll work more generally for say, analog / power sequencing stuff

@azonenberg @urja it will never clock at 1 GHz because we'd be doing this on the output of the 8:1 serdes. Just need a very simple module to track where exactly the sample was and then spit it back out another 8:1 serdes to the trigger output (that way it should be a fixed 8 cycle delay plus hardware delays)

Caution! Entry into the fediverse will expose you to 100x the background level of ΘΔ radiation.

This is still perfectly safe for short and infrequent exposures. If you suspect you've had prolonged or frequent exposure to the fediverse, contact your veterinarian.

I went to download KiCad 9 stable and saw the big "far field exploits" badge on their donation drive since they're matching donations.

Ok, so it's some infosec thing, wireless stuff maybe?

I click on the badge and get this shit. You can't really stop your open source project from being used by these types, but you don't have to accept them as a sponsor and advertise them.

My intention was to make it a design for folks to learn from and build upon.

Using Altium didn't align with this intention, but it was what I was most productive in and helped me get the design past the finish line with what little energy I had every evening.

This "just get it out" mindset affected the schematic too - I had a long look at it one day and realized that I wasn't proud of it.

So with the move to KiCad, I wanted to make something artful, not just functional - my return to form

It's official, ThunderScope has now fully moved over to KiCad!

https://github.com/EEVengers/ThunderScope/blob/master/Hardware/KiCad/Thunderscope_Rev5/Thunderscope_Rev5.pdf

And this is why I don't believe in judging a open source project on how open the tools/software it uses are.

What matters is that you are taking time in your life to share your knowledge and skills freely and openly with the rest of the world.

If using the tools you're familiar with makes that possible for you - use them!

Manager: What should we call this circuit?
Engineer 1: "Clock Noise Rejection"
Engineer 2: "SCL Transient Suppressor"
Engineer 3: *giggling uncontrollably* "PULSE GOBBLER"

Years of working on open source and I still don't know who the sign is for??

And here we see a flock of pelicans laying in wait for their polyurethane prey. After their foamy feast, these majestic creatures will migrate to lab benches all around the world, where they will face their natural predators - hackers, makers and engineers.