Page 1 of 1

Seemingly Random Faults/Error during program that usually works

Posted: Fri Jul 11, 2025 5:13 am
by vincent_konglomerat
Hello team,

the other day I faced a more or less critical error in the middle of a program which stopped and seemingly reset the machine (and homing). Unfortunately the error message is quite cryptic and I have no idea what could have caused this
ERROR: InvalidzrNyjwg0h/FnOQ2h/FnOQ3HHLwNg4h/FnOQ6h/FnOQ
After hard restarting the controller, the program ran through fine. Out of 5 20min runs I encountered this error twice. As far as I remember its the first time I am seeing this error, so I wonder if its connected to the latest firmware update (2.0.4). Maybe someone here faced the same error before and can point me into a direction

the related log section looks like this:

Code: Select all

.....
I:Planner:Cmd:{"type": "line", "id": 1742, "target": {"x": 1363.49, "z": -81.93}, "entry-vel": 154.6, "exit-vel": 154.6, "max-vel": 2828.43, "max-accel": 989949493.66, "max-jerk": 1414213562.37, "rapid": true, "times": [13.27, 0.0, 13.27, 0.43, 13.27, 0.0, 13.27]}
I:Comm:< #id=1742\nlO5kaQwuQVsTgX5aoTgxw2+qRAzrNyjwg0h/FnOQ2h/FnOQ3HHLwNg4h/FnOQ6h/FnOQ
I:Comm:> {"firmware":"Buildbotics AVR"}
I:Comm:AVR firmware rebooted
I:Planner:20250709-193708:Program reset
I:Comm:I2C: S b=None w=None d=None
I:AVR:I2C: S b=None w=None d=None
I:Comm:< c
I:Comm:< h
[color=#FF8000]W:AVR:Serial: 'utf-8' codec can't decode byte 0xd5 in position 10: invalid continuation byte
I:Comm:> {"level":"error","msg":"InvalidzrNyjwg0h/FnOQ2h/FnOQ3HHLwNg4h/FnOQ6h/FnOQ","code":8,"where":"src/command.c:200"}
E:Comm:InvalidzrNyjwg0h/FnOQ2h/FnOQ3HHLwNg4h/FnOQ6h/FnOQ[/color]
I:Planner:20250709-193715:Program reset
I:Comm:I2C: S b=None w=None d=None
Attached are the full log and a screenshot of the error

Re: Seemingly Random Faults/Error during program that usually works

Posted: Fri Jul 11, 2025 7:53 pm
by Doug
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 to reboot. I am wondering if such an overload could also cause the AVR to reboot. Please list any usb devices that you have attached. Also, do you have any other loads on the 5V supply such as relays or active limit switches or an active touch plate?

Re: Seemingly Random Faults/Error during program that usually works

Posted: Mon Jul 14, 2025 2:59 pm
by vincent_konglomerat
hm interesting, thanks for letting me know! I am still wondering why that would occur in the middle of a program though, where none of these loads changed? When the error came up only 2 USB ports were occupied: one with the original Logitech gamepad and the other one with an empty USB extension cord.

We do use a couple sensors and relays via a custom breakout board thats connected to the 25-pin connector, but I am not certain if and how they are supplied by 5V, thats not my expertise.
List of whats connected:
- fixed tool length sensor (Sorotec WLS2)
- inductive limit switches for all axis (10...30 V 2 mm NPN NC)
- external relays for vacuum table and dust collection (Load 1 and 2)
- 2 e-stops in series

I attached the diagram for our custom breakoutboard, unfortunately its in german

Re: Seemingly Random Faults/Error during program that usually works

Posted: Mon Jul 14, 2025 7:48 pm
by Doug
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 plugged into your usb ports, including any usb hubs.

Doug