https://www.thingiverse.com/thing:5881008

Summary The PCB Workstation Kit V1 with Micro Needle Probes is the ideal tool for hobby or professional work on small or medium sized electronic boards (PCB width from 10 to 156 mm).

UPDATED! Now you can buy the new 2025 kits at ingegnotech.com

The haxagonal base is equipped with sliding supports (PCB Holders), having a flat front and an angled front, which allow the positioning of even irregularly shaped electronic boards.

The base can also be equipped with "flat PCB holders" having a flat vertical front, on which a non-slip rubber adhesive can be applied, to easily hold taller and bulkier electronic boards.

In addition, the base features 18 custom sockets along the edge for the assembly of articulated arms or other specific attachments.

Thanks to its articulated crane arms, it is very easy to connect electronic instruments even to the smallest components of a circuit board. Each articulated arm has adjustable extension and ends with a custom holder for an acupuncture needle (0.30 x 30 mm) that is held in position on the test points of the electronic card thanks to a slightly flexible pressing arm.

https://www.thingiverse.com/thing:7191309/files

Looks small. Around 1.25kg of filament + 0.5kg for a stand. 12 servos, Rπ 4, Arduino. No link to software that I saw, and no real pictures of a verified print. Model was posted to thingiverse November 5th 2025.

Like how would I find the entry point in memory, and then capture the returned values. Or for instance, how would I determine the input variables locations that the compiled C code is expecting as inputs, albeit special registers or the stack?

This is an abstract conceptual question with no actual goal or project application at the moment. It would be nice to utilize Arduino libraries in FORTH by writing a function and then encapsulating the compiled binary in a FORTH Dictionary Word definition.

Obviously measures must be taken to preserve the FORTH interpreter's pointers, stacks, and special registers. Is this ever worth the effort as opposed to sucking it up and rewriting the whole thing from scratch, delving into all the underlying mess of peripheral hardware documentation, or is there some typical way to streamline?

As a further aside, does one ever do this within a Unix like system? Like let's say I want to only use a single python method present in llama.cpp in the source that has been compiled and cached in another directory. I want to call this method from inside a function written in my .bashrc file. I have called Python executables from bash functions many times, but never some random subroutine.

California fuckwit OS age verification means I'm going offline soon. How do I get an archive of all of GNU, Python libraries, and C with all documentation? What about all of fedora dnf, and arch's aur? I need all documentation and source.

I stopped using piefed a week ago when I got a message some random quack banned my account in some community I had never engaged with but I could not figure out who did it or where it happened. Any lack of modlog accountability for mods and admin with full transparency are an absolute no-go for me.

Maybe I am just dumb and not seeing where to find these. I only use the web browser front end.

Looking through my regular SRAM chips, most have a standby mode with just a few micro amps of current draw and function down to 2 volts. So, a perfect match for one of these and a coin cell. That makes programming from scratch easy, and one can iterate without a ROM programmer. Once a subroutine is verified, it can be transferred to an EEPROM. Then there is no fussing with paged erasure, not that erasure is a big deal. It just requires the subroutine and a 12 volt source.

Anyways, the battery backed SRAM on the board is the plan for tomorrow. I might have expanded the real estate a bit today, and built a custom breadboard for the 68k Hershey bar. I don't know if I will mess with the 68k stuff as all chips I have are NMOS, and I think that means they cannot single step through code. Reading up on the Z80, that thing is really really nice compared to the 6502.

I've been watching the Solder Smoke direct conversion receiver challenge build and thinking of maybe building it from parts I already have laying around... assuming I wind my own toroids. I haven't noticed anyone talking about antenna stuff. What is the deal here?

This is the principal video series primer: https://www.youtube.com/watch?v=rLjxU2rMeXw

It is also on hackaday too.

Is there some rule about antenna where a more specialized element is required at specific frequencies? I know I'm missing fundamental practical information here as the wave length for 7 MHz is around 43 meters. Even a quarter wave length would involve a house spanning wire. So what gives, what high school fundamental have I forgotten?

Sorry for my nude unisocks.

ZX Spectrum, NES, and Super NES... Si Si Si pew pew pew.

IMO we have had decades of iterative change and exploration, but no major shifts or innovations. Like there have been many takes on the sounds of a guitar, but when do we get to the age of distortion piano-ish thing but entirely different? It seems like most major cultural shifts come from the cauldron or crucible of hard times. We may be near such a nightmare, so what do our kids create from the ashes?

I figured one of y'all would just know seeing how ubiquitous the 6502 is. I'm not following any tutorial at the moment and it has been too long since I last mucked around in assembly. I have the programming manual but it is convoluted between the 6502 and 65C816 stuff.

I'm messing with the little Easy 6502 emulator (Flatpak/FlatHub). I want to nest a couple of loops. I should probably just use the stack, but I went down this rabbit hole and damn it I want to find the rabbit!

I want something like (crude):

define lineL $1000
define lineH $1001

LDA $00
STA $lineL
LDA $02
STA $lineH

Hopefully I have that endian right... So now I have a 2 byte word starting at address 0×1000 and loaded with 0x0200. I want to increment this value as a 16 bit variable up to 0x05FF. What I am struggling with is which addressing mode indexes like this or if this must be manually implemented (– which does not seem right to me).

I'll figure it out on my own in the next couple of hours regardless. It is more fun to chat and see the spectrum of knowledge here, or maybe not, either way, ya don't know if ya don't try. Skool me Woz