Buildbotics Forum

I don't see anything any problems in your schematic. Can you describe how your controller is powered? Also, are you using a local monitor or do you connect via a network, or both? What version of software are you running on your Buildbotcs Controller? Please list all of the devices that you have plu...

In looking at your log, it appears that the error occurred right after the avr rebooted.One of the things that 2.0.4 changed was to prevent the controller from getting damaged if the usb bus is overloaded during bootup. We found that if the usb bus is overloaded during bootup, it causes the attiny t...

Version 2.0.4 of the Buildbotics Controller software has been released. This release applies to our Buildbotics Controllers that incorporate the Raspberry Pi 4 which have been available since the fall of 2023. The following improvements are incorporated in this new release: The EM60 VFD now brakes t...

Here another thread in the User Development/Macros board that describes a probing procedure that can protect your probe from crashes.

If you look at all the dents and holes in my probe plate it becomes immediately apparent why this other method is useful.

Nice work Zeke, As an enhancement, you might consider probing on both sides of the probe plate. This allows you to measure the diameter of the probe. For instance: probe from the left and note the position probe from the right and not the position subtract the two positions to get the difference The...

The actions that the Buildbotics Controller will take are programmed into the 'tool-change' box on the SETTINGS->General page. The 'tool-change' box will contain a set of gcode commands that get executed every time a tool change is encountered in the gcode program. If you don't want the program to p...

It's mostly about switch bounce. All mechanical switches bounce and that can lead to subsequent triggering. These settings are meant to give the switch a settling time so the bounces are ignored.

Try putting in a dwell command (G4) just before the second downward probe. For instance 'G4 P2' would cause the system to wait for two seconds. If this works, you can try reducing the pause time the shortest value that works. I think this might have something to do with the 'input-lockout' time that...

Feel free to call me at 707-559-8539 if you want me to help you via the phone.

Doug

Have you tried adjusting the 'input-debounce' setting on the SETTINGS-> I/O page?