›

Update 1.4.1 and Filament Runout - M600 error

DonSonsiDonSonsi
edited August 2022 in Repetier-Server
Hi. 
Since the update to 1.4.1, the runout sensor and the associated script in Marlin (2.1.1 and 2.0.9.3) no longer work.
When the runout sensor is triggered the M600 script is normally triggered, but since the update to 1.4.1 this does not happen anymore.
With the old repetier-server version it ran and runs as desired.
It seems that the repeater server somehow intervenes here.
I can still trigger the M600 manually via the console without any problems.

Is there a workaround?

Comments

  • DonSonsiDonSonsi
    Same Error also on 1.4.0
    Back to 1.3.0 an everything works fine again.

    It seems the bug is come in with 1.4.0. update
  • RepetierRepetier
    We now send
    M412 S1 H1
    to activate filament sensor with host control. So it should send a message to server and trigger the server out of filament solution. You can add a new M412 to enable different behaviour in printer configuration->G-Codes->Event Dependent->Run on connect. With M600 you surely mean internal filament change handling so that would be
    M412 S1 H0

  • DonSonsiDonSonsi
    Repetier said:
    We now send
    M412 S1 H1
    to activate filament sensor with host control. So it should send a message to server and trigger the server out of filament solution. You can add a new M412 to enable different behaviour in printer configuration->G-Codes->Event Dependent->Run on connect. With M600 you surely mean internal filament change handling so that would be
    M412 S1 H0

    Thnx this workaround works :-)
Sign In or Register to comment.