Posts: 2
Threads: 1
Joined: Aug 2019
Reputation:
0
Hi,
I encountered a problem when printing objects with more than 4028 layers. The two times i tried to print such an object the printer just stopped mid print at layer 4028 and lifts the plattform up
like it is finished with the object.
Both times that happend around 22h in. I tried to resume the print by pressing the pause and play button a few times. The press of the button itself is registered by the printer
as the icon changes. However the print is not resumed.
I am using Chitubox V1.5.0 on Linux for slicing. I have verified the integrity of the cbddlp file by calculating a sha1 hash of both the file generated by the slicer as well as the file on the usb stick.
The installed firmware on the printer is V4.2.16_LCD /1440x2560 /F2.7 which was already installed when I received the unit.
Do you have any hints how I can avoid this problem?
Posts: 97
Threads: 8
Joined: Jul 2019
Reputation:
15
What is the layer thickness it's set to?
Posts: 1
Threads: 0
Joined: Aug 2019
Reputation:
0
I'm also having the same issue at layer 4099 with .02 height... Please help!
Posts: 25
Threads: 0
Joined: Nov 2019
Reputation:
0
Had a tall print (different files) stop around the same height (didn't check exactly on the first one)
Version V4.2.18_LCD/1440x2560 /F2.9
Applied the gcode to stop fan when print is not running. Applied version that also had some changes to Z movement (from thread here)
File sizes: First 642MB, Second 651MB. Sliced with ChiTuBox V1.5.0 and applied automatic fixes in PhotonValidator.
Layer height: 0.03mm
Second print stopped at layer 3473/4386. UV light is off, fan is also off, and the print platform was raised, just like its done after print / on pause. Progress bar at 79%, and the preview shows last layer.
It seemed to be possible to get the print running again. First, press the gear button on bottom right. Go back. Then press the play/pause button and print started again. NOTE: Fan did NOT start, and the printer would go to same state again after few layers (wouldn't have dared to leave it running without fan anyway)
After testing the same thing a few times over and over again, I tried pushing the play/pause button without touching the gear button, and the printer went back to the main menu. no error, no "print completed". Just directly to the main menu.
NOTE: Previously, I have successfully printed prints taller than this, don't remember if the last one was before of after the "fan patch", and whether or not I used PhotonValidator. I definitely used the same layer height though.
(after that, I got some damage on the display, and concentrated doing smaller prints, with which I could avoid the damaged areas).
Just before these new prints, I changed the display to a new one.
Hope this helps.
Oh, I think I saw elsewhere speculation, that the firmware would have 2GB file size limit. The max file size of fat32 is 4 gigs, and that's also the max size indexable with 32 bits.
BUT if for some reason you use SIGNED integer instead, that effectively halves the range (as half of it is now negative), so the actual 2GB limit could well be because of this.
Posts: 25
Threads: 0
Joined: Nov 2019
Reputation:
0
Same settings with different files. Failed on layer 3562/4353. Only one model exceeding the "might fail here" limit (just for testing).
Posts: 25
Threads: 0
Joined: Nov 2019
Reputation:
0
01-05-2020, 08:16 AM
(This post was last modified: 01-06-2020, 05:48 AM by Jupp3.)
Different project (with same high part), 0.03mm layer height, 139MB file, 4353 layers sliced with chitubox 1.61, NOT post processed with PhotonValidator, print finished successfully without errors. Usual "Print complete OK" requester.
Another 4832 layer print successful, Chitubox 1.61, no PhotonValidator.
Posts: 25
Threads: 0
Joined: Nov 2019
Reputation:
0
Actually the previously mentioned two taller parts were sliced without antialiasing (should have noticed that it went back to defaults after upgrade), so that might be the reason for success.
However, my prints are well under 2 gigabytes, so that's not the issue either. At least for me.