DAMNED CRASH - Stuck in spin loop

[gate546]

This post is deleted!

[gate546]

@dc42 said in DAMNED CRASH - Stuck in spin loop:

@gate546 said in DAMNED CRASH - Stuck in spin loop:

I do not know if it can help you, but maybe it could be a problem on the WEB Server part, the only thing I did was to connect with a browser (local) to see the progress
the printer was printing autonomously and never connected before.

Did the reset occur immediately after you connected the web browser, or some time later?

Immediately, or better, immediately as soon as have launched the browser, in fact the browser was not connected, remain on connecting status then I look the printer and I see that the printer was stopped, crashed, without any apparent problem, only stopped.

[dc42]

Thanks, it does sound that connecting the browser may have triggered the problem. I'll do some more tests on connecting a browser while a print is in progress.

[gate546]

@gate546 said in DAMNED CRASH - Stuck in spin loop:

@dc42 said in DAMNED CRASH - Stuck in spin loop:

@gate546 said in DAMNED CRASH - Stuck in spin loop:

I do not know if it can help you, but maybe it could be a problem on the WEB Server part, the only thing I did was to connect with a browser (local) to see the progress
the printer was printing autonomously and never connected before.

Did the reset occur immediately after you connected the web browser, or some time later?

Immediately, or better, immediately as soon as have launched the browser, in fact the browser was not connected, remain on connecting status then I look the printer and I see that the printer was stopped, crashed, without any apparent problem, only stopped.

One more info, the involved gcode file is over a normal SD card that is installed on the 7" Panel and NOT on the micro SD Card that is inside the Duet Wifi board

[Phaedrux]

@gate546 How long was the cable between the panel and the Duet? What type of cabling is used?

[gate546]

@dc42 said in DAMNED CRASH - Stuck in spin loop:

Thanks, it does sound that connecting the browser may have triggered the problem. I'll do some more tests on connecting a browser while a print is in progress.

this sound goods....
I hope that you are able to replicate the issue.

[gate546]

@phaedrux said in DAMNED CRASH - Stuck in spin loop:

@gate546 How long was the cable between the panel and the Duet? What type of cabling is used?

Hello,
the TFT panel and the board are very close, 25 cm. of wire, 1 inch.
the cable is a normal quadripolar cable, single wires, with connectors on both sides.
However we need to remember a point, this printer worked from a couple of years without any problems, and I also have printed very long files without difficulty.

This thing happened only now, in conjunction with the firmware change.
Since the new firmware is RTOS, then with separate tasks, I'm trying to provide DC42 as much information as possible because, maybe, they are useful for help it for troubleshooting this issue.

[Phaedrux]

@gate546 Yes, of course. Merely chasing down possibilities.

[dc42]

@gate546 said in DAMNED CRASH - Stuck in spin loop:

One more info, the involved gcode file is over a normal SD card that is installed on the 7" Panel and NOT on the micro SD Card that is inside the Duet Wifi board

That may be very relevant. The SPI link to the SD card on the PanelDue doesn't have the same hardware timeout mechanisms as the interface to the micro SD card. Also if the ribbon cable is too long then the signal integrity may be degraded. For best reliability, I recommend printing from the micro SD card.

Do you have any other SPI-connected devices, for example a PT100 or thermocouple daughter board?

[gate546]

@dc42 said in DAMNED CRASH - Stuck in spin loop:

@gate546 said in DAMNED CRASH - Stuck in spin loop:

One more info, the involved gcode file is over a normal SD card that is installed on the 7" Panel and NOT on the micro SD Card that is inside the Duet Wifi board

That may be very relevant. The SPI link to the SD card on the PanelDue doesn't have the same hardware timeout mechanisms as the interface to the micro SD card. Also if the ribbon cable is too long then the signal integrity may be degraded. For best reliability, I recommend printing from the micro SD card.

Do you have any other SPI-connected devices, for example a PT100 or thermocouple daughter board?

@dc42

the cable is very short, 25cm plus or minus and yes there is a PT100 daughter board installed.
You suggest to use the micro SD instead? I have some doubts with the micro SD Card due to their structure....

[gate546]

@gate546 said in DAMNED CRASH - Stuck in spin loop:

@dc42 said in DAMNED CRASH - Stuck in spin loop:

@gate546 said in DAMNED CRASH - Stuck in spin loop:

One more info, the involved gcode file is over a normal SD card that is installed on the 7" Panel and NOT on the micro SD Card that is inside the Duet Wifi board

That may be very relevant. The SPI link to the SD card on the PanelDue doesn't have the same hardware timeout mechanisms as the interface to the micro SD card. Also if the ribbon cable is too long then the signal integrity may be degraded. For best reliability, I recommend printing from the micro SD card.

Do you have any other SPI-connected devices, for example a PT100 or thermocouple daughter board?

@dc42

the cable is very short, 25cm plus or minus and yes there is a PT100 daughter board installed.
You suggest to use the micro SD instead? I have some doubts with the micro SD Card due to their structure....
@dc42
David, just for information, to close the circle.
The same long print that caused the crash I wrote before, ended happily without any kind of problems
Same machine, same SD card, all the same, the difference is that I never tried to connect to printer with the browser.
Perhaps we should investigate very well in this field.