v0.99.5b prerelease feedback only

[decay71]

Please report how it works.

[mrmikejackson]

works! Flashed image from postapocalyptic-diy no issues. Stock feeder for T1/T2. Using a Head ACEv2 unit on T3, and Head ACEv1 unit on T4.

Observation: If Slot 1 is loaded, and press "Load" button under Slot2, it will run the Tool Auto Unload of loaded slot and then stop with both unloaded from tool. Must press "Load" on Slot2 a 2nd time to trigger actual load. This is a big improvement from pre-prerelease version where double loading was allowed in Head mode and would cause Jam. Maybe add or rename to "Unload Head" button. Maybe add option to bundle macros to do 1) Unload active slot (or just "Swap" length retract) 2) Load selected new slot.

Thanks. Will keep testing.

[decay71]

Hm, the intented function is to unload whats loaded and load the selected slot, never noticed that, but will look into it. You can always unload via Unload in the Toolhead card? Or did i get you wrong?
IF you want unloads to do just swap lenght retract, just edit the normal retract to that length..

[r3ferrei]

Trying out a print now to test out the BG function, ran into a MCU timer too close during the start of the print. Will restart the printer and give it another try.

19:39:40.695:mcu 'mcu': Timer too close, wsysclock

I ran into this with the prior version "occasionally", particularly while homing when running a print, but I usually just restarted the printer and it didn't happen again.

Attaching logs just in case you wanted to see what the issue might be.

Installed the bin version of 0.99.5.

Also just in case I'm an idiot, for the BG function, you simply remove the small rubber stopper to allow it to purge through the metal hole, right? Reason I ask is I had a print attempted, and it seemed to have pushed material into the stopper, leading it to get clogged and having to restart.

logs-20260713-154644.zip

[decay71]

All right, never had that error, i will check the logs.

Unfortunately you have to snap the whole plastic tongue for now, still somewhat experimental but the nozzle wipers are cheap. Will try to build a print version and look into better ideas to solve this.

[prettycode2022]

https://www.youtube.com/watch?v=lu0_4XRlX6w

https://makerworld.com/en/models/3040955

The filament storage box gets stuck when I push the PEI sheet all the way in—it hits the two round stainless steel rods. I'll probably adjust it a little. Also, I'm curious, why didn't you make it extend all the way to the back of the machine?

[decay71]

Well, i use the Glacier Plate and it did not happen one time. I guess i have to find my pei plate to test this.
To be honest: I built it and it catched the bg poop. I did not spend time to improve it then because my time is limited and there was so much other stuff to do. I will online the cad file today if you or soneone else want to alter it.

[decay71]

Step file for the Box is on makerworld

[decay71]

19:39:40.695:mcu 'mcu': Timer too close, wsysclock

I ran into this with the prior version "occasionally", particularly while homing when running a print, but I usually just restarted the printer and it didn't happen again.

Hi, i checked the logs..

To narrow it down, a few questions:

Did you install anything else on the printer after flashing the bin (SSH installs, mods, other tools)?

Does /oem/.debug exist on your machine?

If it exists: could you try turning advanced mode OFF, then rm /oem/.debug, reboot, and reflash the bin? On my machine that exact state the file changes where the system stores its writable layer, and i suspect that's the actual trigger for these timer errors.

Are you running a camera / timelapse (or anything else extra) during prints?

[r3ferrei]

The printer only has the firmware installed, nothing else installed on top of it. I do enable various paxx firmware features, like tailscale, panda breath and TMC AutoTune, no additional USB camera.

As well, no /oem/.debug.

Ill try at least reflashing it to see how it holds up since i just came from script installed version before.

And thanks for the info on the BG. Will have to wait until I can order a replacement wiper as they are out of stock in my region, but will test once I have one on order just in case I need to roll back.

[decay71]

Yes, please try that. And maybe a test run with these features disabled.

I will build a wiper replacement in Fusion soon.

[decay71]

Observation: If Slot 1 is loaded, and press "Load" button under Slot2, it will run the Tool Auto Unload of loaded slot and then stop with both unloaded from tool.

Hi, i could not replicate this behaviour. On my machine having Slot 1 loaded and pressing Load on Slot 2 unloads Slot 1 and then loads Slot 2.

Can you try to replicate that and send me logs? And what does the command history (bottom of the browser) show after hitting load?

[prettycode2022]

I'm having the same issue. The printer runs fine for about 15 hours, then it suddenly throws this error. I was at work and no one was home, so nobody touched the printer or interfered with it. When I got back, it was already showing the error.

Do you happen to know what might be causing this, or have you seen this issue before?

[decay71]

Do you happen to know what might be causing this, or have you seen this issue before?

Yes, I know this one. It is almost certainly an ACE firmware issue: the FORBIDDEN comes straight from the ACE unit refusing to arm feed assist on that slot, not from multiACE itself. On my side it has always cleared after 1 to 3 times, so it recovered on its own and I never caught it with a pause. That is exactly why yours ran into trouble, it did not recover and right now nothing stops the print when a lane stays unfed, so it just keeps going. I am going to change that so it pauses instead of quietly continuing, and that fix will go into the standard version as well.

Could you send me the logs from around the time it failed, klippy.log and multiace_fa.log? That would let me confirm whether the slot actually went empty or the ACE dropped it after a comms hiccup, and make sure the pause catches your exact case or i can solve it without pausing. It usually happens if a transport did not end before trying to start FA, but i have to look into it.

[Juppi1977]

Ich versuche mit einem ACE 2 Pro am Toolhead 4 zu drucken im Head-Modus. Filamentschläuche gekürzt und in der Konfiguration die Ladelänge, Rückzuglänge und die Transportgeschwindigkeit noch erhöht, trotzdem schafft es das ACE nicht das Filament zum Toolhead zu transportieren bevor er wieder losfährt um das Filament zu purgen. Er druckt dann erst einmal in der Luft und irgendwann kommt das Filament dann durch. Wenn er dann zum wechseln wegfährt zieht er das Filament nicht weit genug zurück und schiebt das nächste schon wieder vor. Schlauchlänge ACE ca. 40 cm + original Bambulab 4 in 1 Feeder + original U1 Schlauchlänge. Ich sehe auch keinerlei Veränderung wenn ich etwas an den Werten ändere. Selbst wenn ich beim Override noch zusätzlich etwas verändere ändert sich zumindest an der Transportgeschwindigkeit nichts. Getestet mit zwei verschiedenen ACE 2 Pro.

Grüße Sascha.