home.social

#veroboard — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #veroboard, aggregated by home.social.

  1. I build #circuits to drive projects, like a kiln controller or a robot. My prototypes are built with bought modules on #veroboard. A module takes Vin and GND, and provides IO as SPI, I²C, 0-5v, etc, so I can ignore the specifics of each chip and work on the fun integration stuff.

    The problem arrives when I want to make a #PCB without modules. I then I have to open a million datasheets and spend a week finding components, fixing footprints and routing.

    🧵 1/2

    #electronics #circuit #kicad #diy

  2. I build #circuits to drive projects, like a kiln controller or a robot. My prototypes are built with bought modules on #veroboard. A module takes Vin and GND, and provides IO as SPI, I²C, 0-5v, etc, so I can ignore the specifics of each chip and work on the fun integration stuff.

    The problem arrives when I want to make a #PCB without modules. I then I have to open a million datasheets and spend a week finding components, fixing footprints and routing.

    🧵 1/2

    #electronics #circuit #kicad #diy

  3. I build #circuits to drive projects, like a kiln controller or a robot. My prototypes are built with bought modules on #veroboard. A module takes Vin and GND, and provides IO as SPI, I²C, 0-5v, etc, so I can ignore the specifics of each chip and work on the fun integration stuff.

    The problem arrives when I want to make a #PCB without modules. I then I have to open a million datasheets and spend a week finding components, fixing footprints and routing.

    🧵 1/2

    #electronics #circuit #kicad #diy

  4. I build #circuits to drive projects, like a kiln controller or a robot. My prototypes are built with bought modules on #veroboard. A module takes Vin and GND, and provides IO as SPI, I²C, 0-5v, etc, so I can ignore the specifics of each chip and work on the fun integration stuff.

    The problem arrives when I want to make a #PCB without modules. I then I have to open a million datasheets and spend a week finding components, fixing footprints and routing.

    🧵 1/2

    #electronics #circuit #kicad #diy

  5. I build #circuits to drive projects, like a kiln controller or a robot. My prototypes are built with bought modules on #veroboard. A module takes Vin and GND, and provides IO as SPI, I²C, 0-5v, etc, so I can ignore the specifics of each chip and work on the fun integration stuff.

    The problem arrives when I want to make a #PCB without modules. I then I have to open a million datasheets and spend a week finding components, fixing footprints and routing.

    🧵 1/2

    #electronics #circuit #kicad #diy

  6. DIY Core Rope Memory Z80 Demonstrator Generating a Fibonacci Sequence - We’ve seen a few retro products using core rope memory, such as telephone autodial... - hackaday.com/2024/10/16/diy-co #fibonaccisequence #coreropememory #computerhacks #veroboard #diy #rom #z80

  7. DIY Core Rope Memory Z80 Demonstrator Generating a Fibonacci Sequence - We’ve seen a few retro products using core rope memory, such as telephone autodial... - hackaday.com/2024/10/16/diy-co #fibonaccisequence #coreropememory #computerhacks #veroboard #diy #rom #z80

  8. DIY Core Rope Memory Z80 Demonstrator Generating a Fibonacci Sequence - We’ve seen a few retro products using core rope memory, such as telephone autodial... - hackaday.com/2024/10/16/diy-co #fibonaccisequence #coreropememory #computerhacks #veroboard #diy #rom #z80

  9. DIY Core Rope Memory Z80 Demonstrator Generating a Fibonacci Sequence - We’ve seen a few retro products using core rope memory, such as telephone autodial... - hackaday.com/2024/10/16/diy-co #fibonaccisequence #coreropememory #computerhacks #veroboard #diy #rom #z80

  10. @hackernews After first excitement i calmed down real quick. This is way to early to use by "a normal user". Using veroboard traces are usually CUT ON A HOLE (with a drill bit) and NOT between two holes. Plus the whole build and compile thing here is way too much for a plain "user" . I don't see this as "usable" just yet. But it can be one day, with some more love put into it. #veroboard #electronics #linux #opensource

  11. @hackernews After first excitement i calmed down real quick. This is way to early to use by "a normal user". Using veroboard traces are usually CUT ON A HOLE (with a drill bit) and NOT between two holes. Plus the whole build and compile thing here is way too much for a plain "user" . I don't see this as "usable" just yet. But it can be one day, with some more love put into it. #veroboard #electronics #linux #opensource

  12. @hackernews After first excitement i calmed down real quick. This is way to early to use by "a normal user". Using veroboard traces are usually CUT ON A HOLE (with a drill bit) and NOT between two holes. Plus the whole build and compile thing here is way too much for a plain "user" . I don't see this as "usable" just yet. But it can be one day, with some more love put into it. #veroboard #electronics #linux #opensource

  13. @hackernews After first excitement i calmed down real quick. This is way to early to use by "a normal user". Using veroboard traces are usually CUT ON A HOLE (with a drill bit) and NOT between two holes. Plus the whole build and compile thing here is way too much for a plain "user" . I don't see this as "usable" just yet. But it can be one day, with some more love put into it. #veroboard #electronics #linux #opensource

  14. @hackernews After first excitement i calmed down real quick. This is way to early to use by "a normal user". Using veroboard traces are usually CUT ON A HOLE (with a drill bit) and NOT between two holes. Plus the whole build and compile thing here is way too much for a plain "user" . I don't see this as "usable" just yet. But it can be one day, with some more love put into it. #veroboard #electronics #linux #opensource

  15. I'll test the TOF sensor in #Forth at first, before moving to the ESP32 in C.

    I did contemplate some low power #555 and #FET switching for transmitter and receiver, that's always fun to play with on some #VeroBoard #StripBoard, especially playing with duty cycles to reduce power usage for transmitter LEDs.

  16. I'll test the TOF sensor in #Forth at first, before moving to the ESP32 in C.

    I did contemplate some low power #555 and #FET switching for transmitter and receiver, that's always fun to play with on some #VeroBoard #StripBoard, especially playing with duty cycles to reduce power usage for transmitter LEDs.

  17. I'll test the TOF sensor in #Forth at first, before moving to the ESP32 in C.

    I did contemplate some low power #555 and #FET switching for transmitter and receiver, that's always fun to play with on some #VeroBoard #StripBoard, especially playing with duty cycles to reduce power usage for transmitter LEDs.

  18. I'll test the TOF sensor in #Forth at first, before moving to the ESP32 in C.

    I did contemplate some low power #555 and #FET switching for transmitter and receiver, that's always fun to play with on some #VeroBoard #StripBoard, especially playing with duty cycles to reduce power usage for transmitter LEDs.

  19. I'll test the TOF sensor in #Forth at first, before moving to the ESP32 in C.

    I did contemplate some low power #555 and #FET switching for transmitter and receiver, that's always fun to play with on some #VeroBoard #StripBoard, especially playing with duty cycles to reduce power usage for transmitter LEDs.