Stepper Jogging Causing Shutdown Due to Webhooks Request

General Discussion
1

Custom Printer
Octopus v1.1 pro

Let me start by saying I know what the E-stop button looks like in mainsail.

I am setting up a new custom core xy printer with TMC5160 drivers using an octopus pro v1.1. with some rather hefty Nema 23s running at 36v rated for 3 amps.

After homing the z axis I am trying to jog and I get the “Shutdown due to webhooks error”. The issue is repeatable however, it does not always happen in the same position and seems to happen on ramp up or rampdown.

moonraker.log (391.9 KB)
klippy (1).log (4.9 MB)

…

2

I’m not sure the root cause, but the Klipper log definitely shows it received a shutdown request and properly responded to it:

webhooks client 281472843887328: New connection
webhooks client 281472843887328: Client info {'program': 'Moonraker', 'version': 'v0.
8.0-204-gfb15b2a'}
...
Transition to shutdown state: Shutdown due to webhooks request
...
Dumping 20 requests for client 281472843887328
...
Received 5696.786799: b'{"id": 281472879477232, "method": "emergency_stop", "params": {}}'

-Kevin

3

Very Puzzling. I am not that familiar with klipper or mainsail yet. Is there a method for troubleshooting the outgoing requests?

4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.