BLTouch Reset Error CMD- building it into the web interface

punamenon

It is quite popular to use DUET boards for Delta printers. It is also popular to use BLTouch sensors on these same printers. This is a setup that comes stock on the TEVO Little Monster. Delta printers have a tendency to settle to the point where the nozzle rests on the print surface when they are turned off. Although rare, this can also happen with a Cartesian printer. If the printer is powered on with the nozzle touching the bed, the BLTouch runs through it's self test and because it can't fully deploy it pops an error, and the red LED starts blinking. If you then try to run an auto-calibration routine, the sensor won't deploy, and your nozzle will collide with the bed. To avoid this, you must first clear the error with a "M280 P3 S160 I1" command. However, this lengthy bit of G-Code can be difficult to remember for all users. Because that bit of G-code is benign to printers which have no BLTouch sensor, and will affect nothing, I am suggesting that the command be incorporated into the "Home All" button. At the very least, it should preface the auto-calibration routine when the user presses that button. Perhaps the web interface could be made intelligent where it will look for the tell tale signs of a BLTouch in the config.g file and only then alter the behavior of the "Home All" and/or "Auto Delta Calibration" buttons.

Phaedrux

Since you have control of the contents of the homeall.g macro, you can add the BLTouch command to the start of it. I do that for all my homing files just in case because there are times when the pin can drop below the edge of the bed and if the head moves it will damage the pin. I even have the command at the end of config.g so that if the pin is out when the printer turns on or the head is too close to the bed for the self test to complete as you describe it will reset automatically.

You can also create a macro with the command that will show up in the DWC or PanelDue.

alt text

punamenon

@phaedrux EXCELLENT! It didn't occur to me to go see if I had access to the homedelta.g file. Now I feel dumb for suggesting this as an implemented feature for all users. Thank you for your help!

Phaedrux

@punamenon no problem at all. The power of the macro system is hard to grasp all at once sometimes.

pro3d

@phaedrux
I hope someday I also will look at the macro world as a resource rather than a time thive trying to fix stuff. Just not a coding nerd

Phaedrux

@pro3d said in BLTouch Reset Error CMD- building it into the web interface:

@phaedrux
I hope someday I also will look at the macro world as a resource rather than a time thive trying to fix stuff. Just not a coding nerd

I just look at it as customization. The rest of the printer is customized to my liking, so why not the control software? It does take some getting used to. And it can be frustrating. I basically spent 6 months reading the gcode wiki and documentation pages before even powering up the Duet, and even then it was a couple months of getting things going. But in the end I now have a printer that behaves like a commercial printer with menus and buttons and routines that behave as expected every time.

Of course I realize not everyone has the time or desire to spend it on all the configuration necessary to get that. But I also had a very workable printer pretty soon after starting. The extra stuff like macros for automating things came after.

T3P3Tony

@pro3d said in BLTouch Reset Error CMD- building it into the web interface:

@phaedrux
I hope someday I also will look at the macro world as a resource rather than a time thive trying to fix stuff. Just not a coding nerd

The macro system, at its simplest, just saves you from manually having to type the same set of gcodes to achieve some action. They can get quite length and complicated but alot are very short and simple. For example I might not remember that to reset a temperature fault on the hotend is M562

However I can write a macro with 1 line in it:

M562 P1

And name it "ResetE0TempFault" or whatever I like.

Of course we could add loads more buttons to the web interface to do all these sorts of things - but not everyone wants the same things!