![]() ![]() G10 P1 X-11 Y0 Z0 S0 R0 Set tool 1 offset, operating and standby temperatures I have the following in my config.g file: It seems to work OK on my machine although I have yet to do a full print with it. I have put a test version of firmware with G10 nozzle offset support at. Large delta printer, E3D tool changer, Robotdigg SCARA printer, Crane Quad and OrmerodÄisclosure: I design Duet electronics and work on RepRapFirmware. And at present, a G92 command has to be used when homing the Y axis on an Ormerod 2 even when using my firmware fork, because the Y endstop is configured in the firmware as a high endstop but it is actually a low endstop. But it won't work with RRP's homing files, which rely on sending a G92 command after an endstop is presumed to have been hit. This will work OK for people who use homing files based on my own, which don't contain G92 commands. Does G92 define the position of a tool with no offset, or the actual tool in use? When sending G92 manually, it makes sense that it defines the position of the tool in use. When homing, the endstops define the positions of a nozzle with no offset So axis limits need to be applied after adjusting the requested position for the tool offset. When applying axis limits, the stored axis limits are valid for a nozzle with no offset. So far I've just added the code to have G10 store and retrieve the nozzle offsets for each tool. Seeing that at least two people are running into problems because of the lack of support for nozzle offsets in the Duet firmware, I've started adding it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |