@MaxGyver You can find updated DSF packages on our internal dev package feed (not documented, use dev instead of unstable) - however use at your own risk! To update, you probably need to reinstall the duetcontrolserver and duetruntime packages.

@moth4017 It works OK on my setup with the second fan. AFAIR the sliders don't update if they are still selected. Can you spot any errors in the JS console (open via F12 -> JS Console)?

This issue was solved with RRF 3.5.0 b2 🙂 👍

Issue still exists in 3.5.0b2

I can confirm this bug and it's fixed now. I've also added a unit test to make sure it doesn't happen again. Here are new DWC builds with this bug fix for standalone and SBC mode.

@dc42

The speeds reported in DWC are not matching the Prusa values

29e4fb8e-ba72-4270-bff5-1d4312f46875-image.png

69de585a-6f55-43e1-8258-5f140887daaa-image.png
38cc9277-5487-403e-ad28-c0463adee727-image.png

@dc42 Hmm, I wish I remebered which tool I printed the prints with issue with....
Two of my tools use extruders on a slave Mini 5 board while the other two tools are connected to the 6HC... Maybe it has to do with the extruders not being on the main board?

I just went back to older builds (specifically the one where you fixed the Mini 5 Slave OoM error) and I can see hints of the issue appearing again when I use one of the tools with an extruder on the Mini 5. It's not as bad as before, but maybe other things play a role.

I'll keep experimenting...

@MaxGyver I've got another machine with an HDMI screen and it works there as well. Perhaps check if the button isn't removed by some kind of browser extension.

@moth4017 I don't know why it does that. RRF just asks the ESP firmware what mode it is using, and if it reports multiple modes then RRF just reports the fastest one.

@moth4017 just don't enable reporting of stalls in the first place. I'm guessing that you use R1 in the M915 command that sets up stall detection for homing. Use R0 there instead.

@Diamondback If your "art" becomes too big, you could still offload it to an SBC plugin in the next v3.5-b2. If a third-party SBC plugin exposes plugin data and you reference it in expressions (e.g. via plugins.myArtPlugin.data.foo), that data is replaced in expressions before it is evaluated by RRF.

@MaxGyver Thanks, confirmed. I'll fix it in the next version.

@chrishamm Alright, I will cut some names down in length then and see if I can make it work. As mentioned, at some point this issue should solve itself for me since I then can simply convert a lot of the x4 globals into an array and do some other cleanups.

Thank you 🙂

@dc42 happy to report, no further resets over the day 🙂 Many thanks!

@dc42
That binary does not change any of the behaviours noted above.

@OwenD this is a known issue, fixed in the next beta.

@dc42 This seems to fix it the memory leak 👍 Now it only resets after a while due to the issue mentioned here (same behavior as without using the local arrays all the time)
https://forum.duet3d.com/topic/31168/3-5b1-reset-reason-stuckinspinloop

@Stefanvh Thanks, this may be a duplicate of https://forum.duet3d.com/topic/31129/dwc-3-5-0-b1-button-speed-is-stuck-at-0-5mm-s/4 I'll have a look at it.

PS: Confirmed and fixed in the upcoming 3.5-b2.

@dc42 said in [3.5.0 b1+] M291 causes a reset if more than 3 choices are given:

@OwenD said in [3.5.0 b1+] M291 causes a reset if more than 3 choices are given:

I've noticed a couple of times that bad commands can just "fail" without giving any messages and also without terminating the macro.

Is this in SBC mode or in standalone mode?

In my case stand alone.
I'll see if I can replicate it before the weekend

@Nightowl said in Software bundle 3.5beta1 released:

Just out of curiosity @dc42, did you manage to implement any improvements for Power Loss/Resume for CNC machines, please?

It was a while ago, but we discussed it here.

Yes, commands to restore the spindle speed and direction are now included in resurrect.g.