[BUG] Octoprint receives error "kill()" from printer about marlin

[Sebazzz]

Which firmware?

[Marow]

Which firmware?

sry..

firmware-20201109-211912-hotfix3.bin

[Sebazzz]

Try adjusting the strain gauge please, like mentioned in this issue: #41 (comment)

Next time, please read the release notes thoroughly, because it has instructions on troubleshooting and how to collect logging and report issues. Help us help you 😉

[eagleeyedpixel]

Hi team,

Just a bit of further information on this one, have worked out it will consistently kill, at least on mine if you initiate home while the optical sensor is triggered.

To fix I just always ensure the z is high enough that the optical sensor is clear, at that point will home fine.

Have confirmed from my own testing now related to strain gauge, I had that issue as well fixed by removing clips.
This is just homing, either as part of beginning a print or beginning levelling.

Latest firmware without the hot fix.

[Sebazzz]

Can you reproduce it on the hotfix firmware?

[eagleeyedpixel]

Installing now, will let you know.

[eagleeyedpixel]

So, decided to try and replicate it again on non hot fix first. Tl.Dr: Strain Gauge likely did it.
Results:
Turned on printer, moved z down by hand to trigger optical then homed via screen - it now worked fine.
Moved it via screen to trigger optical, then homed via Octo - also worked fine.

Moved back to trigger optical, reset printer and then tried to home, no issues again.

Tried a couple more things, but now not happening at all.

I had already been careful of the optical before I fixed my strain gauge and been making sure it wasn't triggered before my prints so had not had the issue for a couple of days, so guessing the kill had something to do with the strain gauge being more sensitive and giving a confusing reading when optical was triggered, as I can't replicate it now and the only thing I have changed is removing the printed clips and making it slightly less sensitive.