search

re3Dprinting / touchscreen

GNU Affero General Public License v3.0
3 stars 0 forks source link

Unnecessary filament runout on second extruder #23

Open jim-thompson opened 4 years ago

jim-thompson commented 4 years ago

When printing from Python, the first print works fine, but the second triggers a filament runout on extruder 2 even though that extruder isn't used in the print. (As a workaround, and to confirm it's the runout being triggered, a length of 3mm filament can be inserted into the runout sensor to prevent the problem.)

jim-thompson commented 4 years ago

Much weirdness about this one. Watching the extruders on the second print, I can see the extruder wheel turning for the second extruder, even though the job is coded to use the first extruder.

jim-thompson commented 4 years ago

More weirdness: on third and later print attempts, it still tries to use the second extruder.

jim-thompson commented 4 years ago

A clue: the octoprint event mechanism reports a tool change from 0 to 1.

jim-thompson commented 4 years ago

This happens even when using straight octoprint (not the serverless version I'm trying to create). Suspect it is a problem with the printer profile.

jim-thompson commented 4 years ago

Unable to reproduce. Demoting to DEFCON 3 until reproducible.