Topics created by omtek

I will confirm that changing from /?action=stream to /?action=snapshot in the webcam URL and setting an update interval (I chose 500ms), you can get something resembling a webcam slideshow in the window.

af77bca3-3b8b-426a-b5bd-7c9a53809039-image.png

@omtek i don't think these is a way to induce that hard fault other than by you being able to reproduce it.

@Phaedrux It looks like the error was in one of the nested macros I use to lower motor current during homing as after running the blank operations I mentioned above on the files in the /sys folder, the error no longer appears. I guess SBC-mode was acting as an additional filter and caught it which was why I never encountered the errors before.

Thanks for the help!

@omtek Okay, thanks, this might be one for @chrishamm to have a look at, in that case.

Ian

This appears to be fixed with v3.5.2. I'm no longer getting the error message using the above steps. Additionally the 3 macros in the upper right corner of the 'Control' page have returned.

Marking as solved.

@omtek thanks for reporting this, and I'm sorry that you suffered a broken nozzle.

I have created issue https://github.com/Duet3D/RepRapFirmware/issues/978 to be resolved in RRF 3.5.1. Meanwhile I have added a new entry in the Upgrade Notes for RRF 3.5.0 to say that any use of M400 in deployprobe.g or retractprobe.g or macros that they call need to have the S1 parameter added.

dc42 created this issue in Duet3D/RepRapFirmware open Using M400 in deployprobe.g causes machine to try to move outside limits #978