Topics created by trulm

@chrishamm That solution wont work completely, I tested it. By putting the files on read only mode, they are not protected from the user dwc. DWC (I might be wrong about whi is doing this ) open the files, reads them, and I have seen they are modified on their atributes.

What I did and worked @trulm (my situation is the same as you) is changing the sticky bits on the files;

sudo chattr +i /opt/dsf/sd/sys/*.g
sudo chattr -i /opt/dsf/sd/sys/config-override.g

This bit makes the files imposible to be modified. Do the same with the macros and the filaments directories.
Also, I have modified the html files on DWC deleting the links to the areas I didnt want my student even look, like for example I deleted the posibility to manually introduce a temperature for the hotend and I also deleted the fill area in the console . In that way students can modified temperature, can not enter gcode comands either ,)

@jay_s_uk Thank you for the really helpful information. You were absolutely right, this was the solution.

@dc42 @gloomyandy Thanks to both of you for your help!

It's nice to see that the community here helps each other. This is no longer the case in many other forums

@trulm to do that you have to start the macro (very rudementary explained) with splitting the z steppers into individual axis. Then assign the movement you want on each of those three axis, then when the movement is done you make each of the axis return to the starting point and combine all the threesteppers back into being Z. And "hide" the two axis you created in step 1.

Hi,

Thanks for your quick support.
The main issue was the misplaced termination jumpers and the unnamed toolboards. Now the boards are talking to each other.

Thank you