You are not logged in.
Pages: 1
I installed the latest firmware from the NanoDLP website, and updated to the latest version.
During printing, the printer freezes on the same model arbitrarily with an error:
fatal error: sync: unlock of unlocked mutex
nanodlp.debug.986477027.zip
Tell me how to fix it?
Last edited by somik (2019-10-15 18:03:07)
Offline
Synchronization has been changed on the latest beta. Hopefully it does not cause any movement issue.
Offline
I upgraded to beta 2386. The printer generally stopped working.
In the printer settings, the Start of Print Code field:
G1 F500; (Start of Print Gcode [[PlateName]])
[[WaitForDoneMessage]]
Z {[[LayerPosition]] - 3}
[[WaitForDoneMessage]]
[[Delay {[[LayerPosition]] / 1000 * 60}]]; Delay {[[LayerPosition]] / 1000 * 60}
Only the first line is sent to ramps terminal:
G1 F500; (Start of Print Gcode)
And does not print.
The Force Stop button also does not work.
If you install firmware 1852 then the printer is working properly
Offline
Please, share a debug file.
Offline
I can’t give a debug beta version - I immediately upgraded to stable
Offline
On another thread there was enough info to troubleshoot it. Please, try the latest beta.
Offline
After updating the firmware on beta 2399, it printed well.
During printing, I monitored the size of free memory using the TOP command. The average memory leak was 12 kb per layer. when printing a model with 5425 layers, the leakage was 209 mb. When you start printing, it takes up almost 100 mb.
I suppose that all the "fatal error: sync: unlock of unlocked mutex" failures were caused by the exhaustion of memory, and after that NanoDLP and / or Raspberry Pi rebooted
I think that the reason for the failure from the post https://www.nanodlp.com/forum/viewtopic.php?id=2108
also a memory leak.
My printer can print with a layer height of 10 microns. These are almost 20,000 layers. With measured leakage, the printer freezes and cannot print the model.
We need to fix the memory leak problem.
The memory indicator on the NanoDLP main screen does not display free memory correctly. For example, the indicator shows 30%, and the TOP team says that 66 mb of 811mb is free. those. correct reading 92%
Offline
Is the internal report on dashboard persistent on 30%?
Go does release memory to OS only in high memory usage but it not used on go side, so it is pretty normal to have inconsistency.
Offline
Pages: 1