@dc42 I did check the console and it had no errors reported. But I’m not clear that it captures anything when my laptop is asleep. I feel like it skips over anything incoming while asleep.

Is there a mode I can set the treats M0 like M1? I can’t ever think when I’d use M0. I never have before. More likely I think is your theory on SD read error (though I don’t know what that would happen either, just more likely). But wouldn’t that get captured in M122? Also the failure mode there should be a pause by firmware to allow for restart, e.g don’t turn off bed heater or motors and send warning. I was lucky that I happened to catch it. I was about to go to bed and it would have been ruined the next morning.

It is fixed in B7+2 🙂
see my post here 🙂

https://forum.duet3d.com/topic/25720/g30-stop-values-increasing-each-time/26?_=1641577026578

to confirm, Z is back on 3HC and multiprobing each point is giving good results again.

1ff898ec-e00f-498a-85ec-5bfe6c70528d-image.png

5fdb28ba-84da-43a8-8c68-edcaa5b31450-image.png

Thankyou @Phaedrux and @dc42

@alex-cr thanks, the "All averaging filters OK" was what I wanted to see, to eliminate a possible cause.

RRF 3.4b7:

I first calibrated my PA.

IMG_0801.jpg

Then some real world testing with PA set to 0.064 and

IMG_0872.jpg

To get rid of the bulging I would need to increase to very high PA values which does impact all other areas whilst printing like starving infill ends etc. (see pictures above).

Used input shaper: M593 P"zvdd" F54.32

With RRF 3.3 I had similar PA values but no overshooting corners.

@alankilian
The board
https://a.aliexpress.com/_mOkoSpq

And yup standing in front and x is +x and z is pointing to -y is what I meant to say

Thanks

@dc42 said in Heater fault on heated bed ...rising to slow. since beta7:

@joeko please try the 3.4.0beta7+2 build of RRF at https://www.dropbox.com/sh/5ubjszy9fmlvzwu/AAAeOMGP-Yi-Gn9LZwQoPfita?dl=0 that I linked to in the other thread.

the link is for beta3.47+1 and not +2
i cant find beta 3.47+2

With the exception of the PID warning "heater behaviour was not consistent during tuning" which might be caused by my tick bed everything appears to know be fine with b7+1, from my perspective I think this issue can be marked as resolved.

@phaedrux Thanks. I’ve just downloaded files from GitHub and replaced ones on the spare SD card. Didn’t have everything on GitHub so fingers crossed. I’ll try it tomorrow.

@rks7204 said in I think I found a bug:

M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2)

My accelerations (as listed above) are not even near those high numbers.

@phaedrux :
I have rooted the issue and its not a problem with the firmware version 3.4beta3. X motor stopped and seemed like some over current issue . I have replaced some cables and will confirm if that is indeed the root cause.

@dc42
Actually, the documentation doesn't conform to either syntax you have given.

@dc42 It always happens when trying to home the machine after a software reset. Right now I can easily reproduce it:

power on the whole machine do a homing cycle - everything is OK during this run if none of the end-stops is triggered do an emergency reset through the web interface try to home again the machine - the errors start popping up

I can't blame it any of the connectors because the errors do not come up after the initial power on. Also, if instead of trying to do a complete homing sequence I try to home a specific axis, the errors will come up for that axis. Even more, as I have a dual-Y setup, when I try homing the Y axis, the errors come up for both drivers/steppers.

Once the machine is homed, I can used for days with no errors!

More to that: the machine is a QueenBee mechanics (similar to WorkBee), with high torque steppers left from the original WorkBee - 3A, 4mH, 1.2Ohm.

If the slicer doesn't provide a layer count DWC calculates the layers from the total height and layer changes, which can get confused by the shorter layer heights.

@chrishamm Hi and thanks for the update. I've just updated to the new web controls from 3.3 but have lost any information about machine and work positions at the top of the dashboard. I am using CNC Mode. I can see it returns in Printer Mode. Is it also possible to have the option to see this information for advanced users, and to also remove the Go To Zero button under the movement buttons. If someone is using the wasteboard as Z0 and material has been fixed, moving to zero will crash the bit.

@owend thanks for reporting this. I have added it to my list to investigate.

btw you could use the S parameter in your echo command:

echo {param.S}

This should display all the information about the error.

I can confirm that this is now fixed in 3.4-b7. Thanks @dc42

@jay_s_uk Yes, AFAIR this already worked in previous versions but it's broken again in the latest one. I'll add more checks to the plugin service to ensure read-only plugins (like DuetPiManagementPlugin) cannot be removed using the web interface.

@jltx said in 12864 stopped working in 3.4b6:

I cut and paste each step from the wiki into ssh on pi. when I pulled the SD and looked at the contents I see all empty directories with just a template config.g in sys.

If you're using a raspberry pi, the SD card is not a readable format in a windows computer. The config files are located in the linux file system on the pi.