Very strange behavior (Mr. David pse help)

gate546

There are any permanent logs (still present after power off) for to try to understand what's happened to the machine?
This morning I found a nasty surprise.
The machine was printing a long job, about 14 hours of printing.
It was almost at the end of the job, but something must have happened.
I found the nozzle stuck in the piece, and the duet wifi that was booting continuously.
All the leds went on and off continuosly, I have turned off and on the power but the problem was still present, only after the third try all goes normal again.
It's not a power problem supply because it is a professional type and has 30 Amp. and isn't a power line outage because the power line is managed by a UPS.
The print was long but no more than other prints made only a few hours before.
What could have be happened?
The job was launched directky from the SDCard because I have noticed that, after that I am using this firmware version, there are some strange problems with the web interface and so, try to avoiding problems, I prefer to start the print jobs from the touch panel.
Now I tried to launch a small test print and everything seems to work properly, nothing strange.
All suggestions and comments are really appreciated.

Firmware Version: 1.19beta6 (2017-06-10)
WiFi Server Version: 1.19-beta1
Web Interface Version: 1.16

Dommy

dc42

If all the LEDs went off including the blue one, then the power to the Duet kept failing. Possibly causes include:

Bad power in connection. Check that the VIN terminal block screws are tight.
Something drawing more that 30A shortly after power up. But I would expect you to see signs of charring if anything on the Duet was doing this.
A fault in the PSU causing its overload protection to trigger falsely.

gate546

@dc42:

If all the LEDs went off including the blue one, then the power to the Duet kept failing. Possibly causes include:

Bad power in connection. Check that the VIN terminal block screws are tight.

Something drawing more that 30A shortly after power up. But I would expect you to see signs of charring if anything on the Duet was doing this.

A fault in the PSU causing its overload protection to trigger falsely.

Hello Mr. David,
Your suggestions are all right, in fact these are the first things I thought and controlled, unfortunately I find nothing unusual and then, as I wrote before, I launched a test print and everything worked well.
So I guess there's no log, right? If I enable debugging in the firmware what happens?
Do you completely exclude a possible bug under certain conditions?
Are you aware of the slight anomalies with the web interface?

Thank you anyway for support
Dommy