Duet3+SBC random restart while printing "AssertionFailed"
-
Hi @Phaedrux, I publish file. I have yet to check but I think it could be a similar issue to this:https://forum.duet3d.com/topic/19346/duet3-6hc-restart-loop-when-connecting-with-web-browser. Yesterday I formatted sd card and I reinstalled everything from scratch but after 20 minutes of printing the sbc disconnected and restarted.
-
@Phaedrux, I managed to do a test without the web page and the problem occurred again. Do you have any ideas about that?
-
Can you try sending M98 P"config.g" and posting the results please?
-
@Phaedrux, i can do it tomorrow evening.
Just out of curiosity is there a guide with listed error code matches? -
-
@Phaedrux, I saw that one, but I can't find the meaning of "AssertionFailed."
Sorry but if possible I would just like to know the meaning of the error since it appeared suddenly -
I've brought it to @DC42's attention, so we'll have to wait for his reply. I've never seen that one either.
-
@Phaedrux , ok, thanks
-
@Marco-Bona, were you using M701 or M702? There's a known issue in 3.2beta that causes assertion failures if you use those commands. It's fixed in the forthcoming 3.2beta3.
-
@dc42, I was using Rrf3.2b1. After formatting sd card I switched to stable firmware version Rrf3.1.1 which gave me the same error. I am not using M701 / M702 commands. Could you please give me a more detailed description regarding the meaning of the error? I can't find any explanation in the documentation.
-
@Phaedrux , I tried to send M98 P"config.g". Everything seems ok
-
An issue has recently been found with the SBC interface that may explain those errors. That issue has now been fixed, so it will be included in 3.2beta3.
-
@dc42, thanks.
When do you think you can release the next update? Is there anything I can do in the meantime to fix the problem? -
@Marco-Bona said in Duet3+SBC random restart while printing "AssertionFailed":
@dc42, thanks.
When do you think you can release the next update? Is there anything I can do in the meantime to fix the problem?Very soon I hope, I'm just waiting for @chrishamm to confirm whether DSF and DWC 3.2 are ready.
-
@dc42, can you confirm that the restart caused by "assertion failed" also occurs with firmware version RRF3.1.1?
I had never had these problems before.
I read in another thread that RRF3.2 b3 will be released next week, is there any solution to fix this problem currently?
Thanks
Marco -
"Assertion failed" means that an internal check on the correct operation of the firmware failed. This usually indicates a firmware bug, but it can also be caused by a hardware fault.
-
@dc42, if it was a hardware error how can i run a diagnostic to correct the error?
I'm not convinced it's a firmware issue. Yesterday I tried to format the sd card and after reinstalling firmware, it worked correctly, instead today the problem occurred. -
@dc42,I'm having another problem, I wanted to test with a newer firmware version, but I can't get the updates with "sudo apt-get update \ sudo apt-get upgrade". Do you have any idea?
-
@Marco-Bona said in Duet3+SBC random restart while printing "AssertionFailed":
@dc42,I'm having another problem, I wanted to test with a newer firmware version, but I can't get the updates with "sudo apt-get update \ sudo apt-get upgrade". Do you have any idea?
@chrishamm is the expert on that area.
-
@dc42, @chrishamm, I update the situation:
-I managed to install the 3.2 beta2 package (sorry but I missed a key point in the guide) and the problem occurred again.
-I ran firmware in standalone mode and printer works surprisingly well indeed I dare say it works better than with SBC connected. The printer seems to respond better to the gcode and I noticed that all messages are displayed on paneldue that were not present with the SBC connected.
Not to argue and also seeing the problems that other users encounter the question that arises is are you sure that duet3 + SBC works as it should?
Are you sure that no changes have been made to what is currently the 3.1.1 revision that was not problematic before?
I am now doing a test print in standalone mode and it seems the printer is working fine.
I will keep you updated if the problem occurs again even in this condition.
