› ›

Crash on Receiving Action:Prompt

EnnoEnno
edited April 14 in Bug Reports
Hi everyone,

I used Repetier Server years ago. Then I didn't have a printer for a while and wanted to start again.

I have an Elegoo Neptun 3 Pro.
Installed is Repetier Server Pro 1.4.16 on Windows 11

Printing works perfectly.

My problem is that the Neptun 3 Pro has a filament sensor built in.
It also reports this back via USB if the filament runs out.

Unfortunately, the Repetier Server crashes completely at the moment when the printer:
Recv:13:34:22.306: //action:prompt_begin FilamentRunout T0
comes from the printer.
Means, the Windows Service is down after receiving these line.
Could be repeated every time i tried it.


Would like to hear any idea or solution to this problem.

Comments

  • RepetierRepetier
    It's a bug in dialog handling with firmware controlled prompts. Will be fixed in 1.4.17 coming soon.

  • EnnoEnno
    Thanks for the prompt answer.
    Bad to hear it´s a bug. Good to hear it will be fixed imediatly

    Will it be possible to add a Response to Event for this action_prompt?
    e.g. to answer this event with an M600?
  • RepetierRepetier
    Response event could in deed help here to not crash, but you can not send commands to printer in that state only emergency commands will be accepted by firmware as it is the firmware doing the pause and we just want to display the messages. So replace it with nothing or a message is ok and then you must handle pause on printer display.
Sign In or Register to comment.