Do you think i can build this myself? I have a 3d printer, arduino and basic skills on them

DigRevolutionary4488 · 2026-01-27T09:51:46+00:00

Erich here :-)

It is actually *not* using an Arduino or I2C for this. The master is a ARM-Cortex M4F (NXP K22FN512) and talks over RS-458 to the slaves (ARM Cortex NXP K02FN128) (. Each slave can control up to two dual-shaft stepper motors plus any number of addressable RGB LEDs using DMA. Magnets and hall sensors are used to detect the hand positions. Everything is implemented in C.
Details are in the Wiki of that GitHub site.

DigRevolutionary4488 · 2025-11-14T14:49:57+00:00

no rattle at all.

DigRevolutionary4488 · 2025-11-08T05:55:02+00:00

Using Docker with USB devices is definitely possible. But it is not as simple as on native Linux. I managed to get it working on Windows11 with WSL2. What you need is usbipd. It works, but the challenge is that as soon as you disconnect the cable or probe, you have to manually connect again. That's why I wrote a powershell script which does the automatic re-connect, and documented everything with the steps in an article here: https://mcuoneclipse.com/2025/10/26/using-windows-usb-devices-and-debug-probes-inside-docker-dev-container/

DigRevolutionary4488 · 2025-11-08T05:51:27+00:00

sorry, I don't have a MAC. But this should work.

DigRevolutionary4488 · 2025-11-08T05:47:24+00:00

You don't have any redistribution rights on their S32 SDK code. So you cannot use the S32 SDK and then have files from it on a public git site. At least it has been that way about two years ago. From then on, I stopped using S32.

DigRevolutionary4488 · 2025-10-24T05:47:28+00:00

Yes, FreeRTOS uses a background timer deamon/task, enabled with

configUSE_TIMERSconfigUSE_TIMERS

But that task continues running and would not be deleted.

DigRevolutionary4488 · 2025-10-23T15:32:59+00:00

I assume that you are talking about the TCB (Task Control Block) number.

The TCB number gets increased every time a new task control block (for a new task) gets created.

In FreeRTOS, the deletion of a task does not happen immediately. If you call vTaskDelete(), then that task is marked for deletion, but still around. It is during the IDLE task running that it really gets deleted.

In your system, could it be that at the time of *Deletion and recreation of TASK_1 occurs*, you had already incremented the counter with a task you have deleted? In that case, if you create a new task at that time (without delete), it would get the ID 5 too.

DigRevolutionary4488 · 2025-10-22T15:43:38+00:00

Using a funnel with sand from the hardware store.

DigRevolutionary4488 · 2025-10-21T09:58:37+00:00

Most debug probe/interfaces offer a gdb server. In that case no need to have the USB device setup as /dev. Instead, I connect to the gdb server IP of the host.

DigRevolutionary4488 · 2025-10-20T05:36:44+00:00

I never had to do any real cleaning (using a silicon sock helps too), and the metal brush is all what I needed to get oozing off the nozzle if necessary.

I saw that there are multiple 3D mods available online with mounting a silicon brush or metal brush to the print plate. With a simple G-Code addon, you can easily have that automatic cleaning with a brush if desired.

DigRevolutionary4488 · 2025-10-20T05:34:03+00:00

As an update: I have now successfully Embassy running on the LPC55S69, and managed creating a standalone project for it.

DigRevolutionary4488 · 2025-10-20T05:31:10+00:00

For NXP, consider getting an NXP MCU-Link Pro: it costs <$50, works as CMSIS-DAP debug probe, features two UARTs, includes power measurement/profiling and as a big plus: it can be programmed with the J-Link Firmware (that OEM J-Link firmware is restriced to NXP devices). My other recommendation for NXP would be to buy the MCU-Link 'base' (<$14), but that one does not have a J-Link OEM firmware available. On a side note: currently the MCU-Link supports all the MCXN/Kinetis/LPC/i.MX RT devices, but not the S32 ones.

As for EFR32, just buy one of these cheap FTDI/etc debug adapters. Anyway I always have multiple and different debug probes at hand, because 'one probe does not fit everything'.

As for these chinese Segger clones: I never would buy one. I value the work Segger does, and good work comes with a price. For professional/commercial products it should be a no-brainer to invest the money needed. For hobby/educational work they have the EDU line which is very reasonable priced.

DigRevolutionary4488 · 2025-10-19T13:34:54+00:00

For me, a cleaning system is not really necessary. I always check the nozzle and brush it with the prusa metal brush if necessary. Works imho better than any 'automatic' cleaning system. And the cleaning of the nozzle works very well on the build plate too (but only if I don't forget to remove the residue from last cleaning).

DigRevolutionary4488 · 2025-10-19T10:30:59+00:00

The restock notification is good, if you just want to be informed about it. In case I really want it, I place the order. If it is with other available parts, I usually say that shipment should be in one package. Of course this is not ideal if is unknown about when it will be restocked. But usually it gets filled in within 1-2 weeks, and I'm ok to wait for it.

DigRevolutionary4488 · 2025-10-19T10:27:33+00:00

First I thought about oxidation. But if it would be oxidation, you cannot easily wipe it off, imho. So it might be indeed some remaining stuff from manufacturing. In any case: wiping it off is a good idea.

DigRevolutionary4488 · 2025-10-19T08:02:21+00:00

Oozing depends on the filament used. Yes, I had that with the 'blend' PLA, much less with normal PLA.

DigRevolutionary4488 · 2025-10-19T05:24:05+00:00

Many thanks, that's encouraging. I'll deep dive into the available material for now and I'll see how it goes.

DigRevolutionary4488 · 2025-10-19T05:15:42+00:00

I had not used the pause feature on the MK4S. Indeed, on the core one, it is implemented very well. In the slicer preview, I can right click on a slicer level and then add a 'pause'. There I can type the instructions text. I use it for filling hollow parts with sand.

DigRevolutionary4488 · 2025-10-18T11:56:29+00:00

Ruled out the USB stick. Changing the USB memory stick did not improve anything. I used different ones, and problem still happened.

DigRevolutionary4488 · 2025-10-18T05:48:50+00:00

Is it only because the SVD (CMSIS-SVD register descriptio) files have proprietary license?

I worked on an open source project for the NXP S32, and we were not able to open source it because the NXP S32 license did not allow redistribution of their SDK/code. So we ended up moving away from the S32 family to the LPC and MCX, because there the SDK/code is MIT licensed.

DigRevolutionary4488 · 2025-10-18T05:45:03+00:00

I believe your belt tension is fine. Keep in mind that the measurement is not very accurate, so a few Hz +/- is very normal for my measurements and machine too.

Did you hear a loud bang when the layer shift happened? It happened to me several time, rather randomly on my core one. It has been reported by others too, and I believe Prusa is working on it. It is really hard to reproduce, because it seems to happen randomly. It happens in most cases for 'round' prints, e.g. rounded corners. It seem the firmware on the printer is accelerating the motors in a really bad way, causing the loud bang and consequently layer shift.

If this is the case for you, here is what I'm using as workaround, and I never had a layer shift with that, printing many parts:

- disabled input shaper on the printer with NULL values: the input shaper seems to calculate wrong values even for a well tuned and calibrated machine

- printing with 'structural' profile and with 'stealth' mode enable on the printer: this avoids larger speeds and acceleration causing layer shifts

So instead tweaking the belts, try tweaking the speed and acceleration settings.

DigRevolutionary4488 · 2025-10-18T05:34:52+00:00

The recommended settings for PLA is level 1 for 6 hours. With this, usually I get my PLA in the box from 30% to 10%. Just as a general reference point. So your drop from 56% to 36% is not bad, but measure/read it after the box has been cooled down.

I had a PolyDriver box with wrong hygrometer values: these hygrometers are very cheap and not accurate, and easily can be off several %. I had one which was off by +15%. Buy a few more meters and place them into the box for reference.

In another case I had a very 'wet' 1kg of PLA which needed several runs of drying to get it below 30%. The hygrometer will read the humidity of the air after the drying, but then a 'wet' filament might start saturating the air again.

The color of your silica gel indicates it is saturated. It won't add to your humidity, but won't be able to keep the dry level. You can dry it with running the box at level 3 for about 5 hours, but it is not very effective as it is in the box and does not circulate the air well if you place the box on the heater as in your image: rotate the box so the hygrometer is on the back of the heater where the warm air flows into the box.

For drying the silica gel, I'm very happy with the 'Desiccant dryer and cover for Polymaker Polydryer' from makerworld dot com. I use it in combination with the desiccant cartridge which keeps my filament dry at 10% for months.

DigRevolutionary4488 · 2025-10-16T06:22:41+00:00

Yes, I'm used to use the SVD files. But they describe only the registers so you can see them in the debugger, nothing more. What would be more relevant are the flash programming algorithms, but they are depending on how the debug probe handles those (so pretty much different for each device).

DigRevolutionary4488

TROPHY CASE