theacodes

This license is so laughably bad I had a hard time writing a parody of it [1]. It's not open source, it doesn't accomplish any of its goals, it's not novel in any way. It's a joke, a smokescreen for Prusa and it won't do anything to save him from competition. Good luck, Josef. I'd encourage everyone else to avoid this like it's radioactive.

[1]: https://github.com/theacodes/socl

I only ever directly interacted with Kris once, and that's all I needed. She was so kind to me when I reached out for advice and support during an extremely difficult time in my life.

She will be missed so much.

Sure, it's blog.thea.codes. I write about open source, synthesizers, 3d printers, and PCB design.

As the person who implemented the -t flag and knows the horrendously sharp edge cases that it fails on, all I can say is bless your heart.

that "political spat" was actually targeted harassment towards a former PyPA member the last time someone actively working on packaging.python.org tried to be remotely opinionated. Since this ended with them stepping away and no one else has volunteered, it remains unopinionated.

I think you're working on some outdated assumptions. As mentioned in the article, the LumenPNP project is successful. Myself and many others have been successfully assembling boards with it since earlier this year. Lumen isn't my project, it's just the machine that the board I designed is intended to work with.

https://github.com/opulo-inc/lumenpnp

You're not wrong, but it's also not the focus of the article. There's a lot of complexity in a pick and place system, for example I didn't even touch on the entirely separate board that's controlling the tool head. If I tried to capture all that at once, I'd be writing an entire textbook, not an article.

If you're interested in how the LumenPnP handles vision, you can check out the OpenPNP project which handles all of the computer vision involved.

https://openpnp.org/

Thank you for the kind words! I'm glad it was useful.

> why not get it from 24V?

There are DC-DC converters in that same family that can do 4.75~36V -> 3.3V, but since I needed the 5V anyway for the LEDs and I/Os, tossing an inexpensive and small LDO for 5V -> 3.3V is an easy call.

That one seems a bit cumbersome. Drawing schematics and drawing layouts have much different hurdles in terms of performance, it would definitely be a fun challenge. :)

Thank you! For the board layers I just used macOS's screenshot utility, though I would like to do something fancier in the future. The schematics are rendered using code I wrote specifically for this article, but I am planning to publish it as an open source library so others can use it. It needs a little bit more polishing before it's ready, though! You can follow me on Twitter if you wanna get updates about it.

Great question! It really depends. If I'm working with a part I haven't ever worked with before, I'll often make a minimal breakout board that I can talk to with a devboard like an Arduino or Feather.

If I'm pretty familiar with everything, I generally dive into a rough PCB layout and debug from there. If I absolutely can't get anything to work, I'll go back to the drawing board and possibly do some little breakouts, for example: https://twitter.com/theavalkyrie/status/1457845661370568709

Edit: for this specific project I did make breakouts for testing the MOSFETs and solenoid drivers. I'm glad I did, since I was able to try out a couple of different options for each: https://twitter.com/theavalkyrie/status/1550878465876004865

I'll echo sibling's comment about just doing it. Theory only takes you so far, it's important to actually build and experiment, even if it's just in a simulator.

I can recommend Practical Electronics for Inventors as a solid base of projects to experiment with and learn from. If you want to learn how to improve circuits and optimize for specific behaviors, there is a wealth of information in manufacturer application notes. A lot of the protection circuitry used in my article follows advice found in application notes.

Hi! I'm planning on talking about that in an upcoming post. There's options - you can run 3d printer firmware like Marlin (C++/Arduino) or Klipper (Python & C), the tricky bit is getting those to talk to the vacuum sensors. Communication is via gcode commands sent over USB serial. Most folks are running their Lumen with OpenPNP on the host.

I'm actually running completely custom firmware that I wrote specifically for this board that's written in C and uses Raspberry Pi's pico SDK. It's similar to Marlin/Klipper in that the host communicates via gcode over USB serial and that movement commands are more or less done the same, but it gives me the flexibility to simplify the whole host view of the pneumatics. It absolutely wasn't necessary for me to this, I just wanted to.

Author here, thank you for the kind words! My goal is always to write the thing I would've wanted to have when I started out.

You're correct. The pulse-width of the saw wave is very dependent on the amplitude of the saw, so when there's a 1 volt deficit in the saw wave's amplitude you lose about 8% of the pulse width. It's really not that noticeable in practice, though, and if anything it adds to the sonic character of the juno.

Yes, all of the waveforms out of the waveshaper have a DC offset. The synthesizer removes that when mixing them and sending them through the filter.

I hand-drew the illustrations using an iPad pro & photoshop. The code highlighting is using Sphinx + witchhazel.thea.codes.

Okay, it's updated to use OAEP and PSS padding. Thank you!

Yeah! My blog is actually on GitHub if you want to follow or whatever. It's theacodes/blog.thea.codes.

Oh, and we use asym because it's useful for us to be able to inspect the token (and see stuff like it's permissions and expiration client side). I only kinda mention this a bit later, but I might make that a bit clearer.

This great feedback. I'm definitely not a crypto expert. I'm happy to update the post with a different padding algorithm if you want to suggest one. I'm a little hesitant on swapping out RSA because I intentionally picked something relatively simple and familiar to folks, but yeah, will still do some research. Others had suggested ECC which I think is totally worth noting in the post one way or another.

Thank you!

I actually just aimed for simplicity and stuff folks might be semi-familiar with. It might be worth adding a little note that EC would be more efficient all around.

Thank you so much, I really appreciate the kind words!

Because JWT is well specified and supported and it's useful in our case for proxy users to be able to inspect the token.