Autoleveller AE 0.8.5
Posted: Fri May 26, 2017 9:51 am
Thought this update may need extra explanation, so here goes…
This update includes the option to add a Custom controller, which means you can add support for controllers which are not part of the existing list of supported ones. Or you can use the Custom controller to insert additional commands and macros to the probing routine to work around an issue or perform an additional action.
To do this, select ‘Custom’ as your controller and click Options -> Custom Controller Options.
This brings up the custom controller options dialog box where you can make modifications to affect the resulting GCode output.
All the fields here can be changed and experimented with and an example GCode text area shows how AE might render the results in GCode.
The real GCode output from AE will appear different to this example text area because not all words and commands will be needed depending on whether you use standard or 2-stage levelling. For example, when using a PFG to probe, the results are written to a file and therefore the parameter settings (#600 and #2002 in this case) are not needed and will not appear in the PFG even though it appears in the text area. The text area provides a useful guide which shows a sort of combination of standard and 2-stage levelling probe GCode.
It should also be noted that if you leave a field blank then the entire line containing that field will not appear in the text area or any output GCode. This may or may not be what you want. Experiment with these custom controller options if you need this feature and let me know if further clarity is needed or you want something added or changed in this regard.
This update includes the option to add a Custom controller, which means you can add support for controllers which are not part of the existing list of supported ones. Or you can use the Custom controller to insert additional commands and macros to the probing routine to work around an issue or perform an additional action.
To do this, select ‘Custom’ as your controller and click Options -> Custom Controller Options.
The real GCode output from AE will appear different to this example text area because not all words and commands will be needed depending on whether you use standard or 2-stage levelling. For example, when using a PFG to probe, the results are written to a file and therefore the parameter settings (#600 and #2002 in this case) are not needed and will not appear in the PFG even though it appears in the text area. The text area provides a useful guide which shows a sort of combination of standard and 2-stage levelling probe GCode.
It should also be noted that if you leave a field blank then the entire line containing that field will not appear in the text area or any output GCode. This may or may not be what you want. Experiment with these custom controller options if you need this feature and let me know if further clarity is needed or you want something added or changed in this regard.
