Fitment issues with D2F-5L microswitch and XY endstop pod #136
Assignees
Labels
Comments
FHeilmann
pushed a commit
that referenced
this issue
May 4, 2021
voidtrance
added a commit
to voidtrance/Voron-2
that referenced
this issue
Nov 8, 2023
…ronDesign#136) The PRINT_END macro in the Octopus config file contains a pair of SAVE_GCODE_STATE/RESTORE_GCODE_STATE command. The purpose of those commands is to allow the macro to perfom actions at the end of the print and then restore the printer state as it was prior to the macro's execution (restore coordinate system and speeds). However, there was some confusion as to the effect of those calls, particularly the RESTORE_GCODE_STATE. What is desired is that the printer state is restored but the toolhead position is not. To clarify the intention and prevent any issues, the "MOVE=0" argument to RESTORE_GCODE_STATE is added as to explicitly prevent any toolhead position changes and a comment is added to describe the purpose of the commands. Since having the commands in the PRINT_END macro is something that is needed, the same commands have also been added to any of the other configs which were missing it.
voidtrance
added a commit
to voidtrance/Voron-2
that referenced
this issue
Nov 22, 2023
…ronDesign#136) The PRINT_END macro in the Octopus config file contains a pair of SAVE_GCODE_STATE/RESTORE_GCODE_STATE command. The purpose of those commands is to allow the macro to perfom actions at the end of the print and then restore the printer state as it was prior to the macro's execution (restore coordinate system and speeds). However, there was some confusion as to the effect of those calls, particularly the RESTORE_GCODE_STATE. What is desired is that the printer state is restored but the toolhead position is not. To clarify the intention and prevent any issues, the "MOVE=0" argument to RESTORE_GCODE_STATE is added as to explicitly prevent any toolhead position changes and a comment is added to describe the purpose of the commands. Since having the commands in the PRINT_END macro is something that is needed, the same commands have also been added to any of the other configs which were missing it.
KiloQubit
pushed a commit
that referenced
this issue
Nov 22, 2023
…) (#452) The PRINT_END macro in the Octopus config file contains a pair of SAVE_GCODE_STATE/RESTORE_GCODE_STATE command. The purpose of those commands is to allow the macro to perfom actions at the end of the print and then restore the printer state as it was prior to the macro's execution (restore coordinate system and speeds). However, there was some confusion as to the effect of those calls, particularly the RESTORE_GCODE_STATE. What is desired is that the printer state is restored but the toolhead position is not. To clarify the intention and prevent any issues, the "MOVE=0" argument to RESTORE_GCODE_STATE is added as to explicitly prevent any toolhead position changes and a comment is added to describe the purpose of the commands. Since having the commands in the PRINT_END macro is something that is needed, the same commands have also been added to any of the other configs which were missing it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have had issues fitting the X and Y microswitches to the endstop pod. I have checked the Omron datasheet for D2F-5L and the distance between fixing hole centre and case outer surface is 1.5mm, however in the V2.4 CAD model, this dimension is only 1.35mm.
The shape of the micro switch locating feature is also different to the D2F-5L linked in the sourcing guide (straight PCB terminals) as it doesn't follow the case profile of the microswitch fully. Perhaps a simple rectangular shaped support feature, 1.5mm from fixing hole centre would work? That way it would allow fitment of both the solder terminal as well as PCB terminal types, while still supporting the micro switch location during use.
en-d2f.pdf
The text was updated successfully, but these errors were encountered: