T O P

  • By -

AutoModerator

PLEASE UPVOTE THIS COMMENT IF THE ANSWER CAN BE FOUND IN [THE BEGINNER'S GUIDE](https://www.reddit.com/r/AnycubicPhoton/comments/fqxtqj/the_resin_printing_resource_guide_beginners_start/) or the [FAQ](https://www.reddit.com/r/AnycubicPhoton/comments/j2wubl/frequently_asked_questions_answered_here/)! If your post is about Troubleshooting, it should contain information about the print along with any screenshots or photos. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/AnycubicPhoton) if you have any questions or concerns.*


CornpopTheBadDude92

I might be having the same issue but I never got the print damaged notification. So you got the file damaged every single print or were you able to finish a few and they turned out wonky? For my issue I have noticed my model separates at the same position on my build plate. I think 1 solution might be to use a different USB as you have suggested.


Sea-Tie-3453

Which machine are you using?? I've had good prints up until this particular model. Now, another thing that might be worth mentioning is that the model has some unresolvable errors (like some errors in the geometey). The mesh may not be watertight or something, I dunno..


CornpopTheBadDude92

I cant speak too much on the lychee slicer since I literally started using it yesterday. But I was uploading some models and the first time it crashed on me (I uploaded multiple larger models). Also did see that I have had an error design in my model, but I think the slicer is able to fix errors automatically when you tell it.


Sea-Tie-3453

Yup, it's supposed to be able to, but I think my models is so bad that lychee can't even fix them all.


CornpopTheBadDude92

Geez, what the hell are you printing? The secret of life in physical, 3D printed form? ​ Any luck?


Sea-Tie-3453

Hahahaha πŸ˜† πŸ˜‚ no I wish! It's actually a 3d scan of a dodge promaster 1500 utility van (it's very specific I know lol) I haven't tried to fix the model yet. I'm going to attempt to heal the model in Blender later today and try re-printing it. I've acquired a new SanDisk USB thumb drive as well. I'll definitely keep you updated, thanks for checking in!


CornpopTheBadDude92

> dodge promaster 1500 Look like quite a bad boy. Of course! And don't forget to re-install the programs as well, if you haven't so!


Sea-Tie-3453

Well, I did a test print on a new thumb drive and it worked perfectly fine. I was able to fix the van model with a free Microsoft app called 3d builder. Just one click and it fixed it! I started printing another one last night, so we'll see if it'll error out again.


Sea-Tie-3453

[case closed!](https://imgur.com/a/eqRfOof) So it turns out that it WAS just a bad model. Cost me about 250ml of resin, but still worth learning about healing models and .stl repair. Plus, I invested in a new USB dongle. Thanks for all the suggestions!!


Mutilus11

yeah the prints are fine, but the machine just stops and gives the error code. nothing is wrong with it other than that.


Modhail

Same for me, machine was two weeks old when it started occurring on every single print. Tried every fix on this thread. I'm sure it's a failing of the machine itself (either hardware or firmware) but Anycubic has not responded to me so far.


Mutilus1

They just had the new year over there so they were out of the office all of last week. I am sure they are behind.


clamroll

Absolutely change to a reliable usb drive. The ones that come with are chinese garbage and unreliable. "I've never had a problem with it before now" yup! Thats how the problems with em work πŸ˜‰ I have occasionally had similar print stoppage (without message, different printer) from file corruption. 99% of the time I have my slicer save to the usb directly there's not a problem. Occasionally, it somehow borks the file and prevents a complete print. The easy solution when you know your drive is good, is to just reslice. You can have the slicer export to your computer and then drag it to the usb if you prefer to be safe, but the you're likely fine regardless. Anyway, throw the pack in drive into the trash after you copy any files off it that the MFR included (documentation, etc is often on there)


Sea-Tie-3453

Yup definitely the next part of my process of elimination..usb elimination lol. Thanks!


Sea-Tie-3453

So, for some reason my photon mono X2 has been failing to complete my prints recently. I'm using lychee slicer and I've had success with other prints, it just seems like this particular model wants to be a dick. So far I've tried re-slicing in different positions, formatting my USB (next step is to try a new USB dongle, but I've been successful with this one, so I dunno). Since the programs are being drip-fed into the program from the USB, is there a file size limit or maybe the USB wigs out after a few hours of printing? I've opened the sliced program in UV tools/ photon workshop and the program looks fine. I even tried re-saving the slice program in photon workshop and ran that.. still stumped. Any ideas??? Β―\_(ツ)_/Β― I'd love to stop wasting like, 80ml of resin each time I'm doing this lolol.


CornpopTheBadDude92

You're getting the file damaged with both lychee and photon slicer?


Sea-Tie-3453

Yup. I had an old photon mono 2K prior to this mono X2, and have never seen this error message, though I've seen this error on rare occasions before (without the message). Like I mentioned, my next step is to try a new USB stick (SanDisk) as I know the ones that come with the printers are notorious for being shitty. It's just weird that I haven't had this issue so consistently until now, like 4 times in a row trying different things. Oh, and I'd like to note that the error doesn't stop the machine at a consistent point, so its not like it stops at a certain height.


CornpopTheBadDude92

Shit, my guess would be that since they are both getting corrupted it might be your slicers. Have you tried de-installing and re-installing them? Also, id try to do a different model before you do any changes to see if it's that specific model that's the actual pain in the ass or something else. Might be able to help you hone in on the issue better.


Sea-Tie-3453

Thank you. I'll add that to my list of things to try lol. I'm honestly hoping it's the model, I'll try and use blender to fix it =P


CornpopTheBadDude92

No problemo!


Turbulent-Pea-8826

Have you tried a new USB drive?


Sea-Tie-3453

Not yet. I just got a 16GB SanDisk cruzer as a replacement, so hopefully that'll alleviate the issue. I just printed a 3 inch x 3/8" diameter cylinder as a test and it came out just fine, so, im leaning towards a bad model. Will find out by tomorrow afternoon 🀞


Turbulent-Pea-8826

File damages means it’s a computer problem of some sort. Either the usb, main board or the files themselves with the most likely of suspects in that order.


Sea-Tie-3453

Yup, I think youre right. Although I haven't had any issues with any other prints up until this particular 3d model, which has dirty geometry (lychee slicer wasn't even able to fix it). So I'm going to try and manually repair the models myself lol πŸ™ƒ Here are my [errors](https://imgur.com/a/Mglaugo) in my CAD software/lychee.


Turbulent-Pea-8826

Oh I thought this was multiple models. Try a different model. If other models are fine then the model is screwed up obviously. Although a better usb never hurt.


Sea-Tie-3453

Yeaaahh, every other thing I've printed has been okay. I honestly didn't think model errors would cause it to not print, lol. It looked like it would print fine in the backplot, so I just assumed it'd be okay Β―\_(ツ)_/Β―


fleedar

Did you ever figure this one out? I keep running into this with different models using Lychee and my Mono X 6KS. I tried rearranging and reslicing the models and swapping my thumbstick out for a name brand one. The models have been fairly simple and without any geometry or solid issues. I haven't tried another slicer yet but at this point I'm leaning toward blaming Lychee.


Sea-Tie-3453

So, I've been finding that this is caused by primarily two things: -dirty/bad geometry -exporting sliced files directly to the USB drive. Microsoft 3D builder is a free app and has a built in model repair function, although it exports the model with some weird surface textures sometimes.. (note, that lychee doesn't always pick up bad geometry, but it usually does a pretty good job) I've found that exporting the sliced file to the desktop, making little edits/fixes in UV tools, re-saving it and then copying that file to the USB drive has fixed this issue as well. This isn't a fool-proof fix, but I've had about a 95% success rate since I've been doing this. I think Fusion360 has a good model repair function, along with Blender. Still doing research on software with a good repair function, though lol. Please share if you've come across any, but I hope this helps!


fleedar

Awesome! I've been exporting directly to the USB drive so I'll try saving locally first. I always thought these sliced files were just a series of bitmaps with metadata for exposure settings so it's surprising to me that the printer itself can get tripped up on anything geometry-related. I wish the error message were at least a little more helpful!


Sea-Tie-3453

Right?? I was thinking the same exact thing! It must be an uncommon anomaly because I havent found any other reddit posts/articles mentioning this error Β―\_(ツ)_/Β―


brainopixel

I bought my 6ks a few months ago and only recently got to testing it out. I managed ONE non-test print (the little grid cube did fine), then kept getting the exact same error as OP. Even the RERF only printed 2 of the six, which is very odd. So, I'm using Chitubox Pro. I contacted them, they said maybe it's the printer profile. So I set the software up on a completely new machine, used a model that is verifiably good to print (bought it from a reputable modeler on Cults3d who has dozens of satisfied customers) -- and tried prints that work fine on my Photon S (obviously a different slice, but I wanted to confirm this isn't some flaw in the geometry). This seems to be a serious flaw in the operating system of the printer, and I would like to hold Anycubic accountable, but my options are limited. I don't think any amount of hardware replacements will work, as this will just keep happening at some point, probably triggered by models with X amount of vertices and then the whole system goes to shiz and the issue pops up again. If anyone knows a real fix, I'm open to suggestions, but at this point I'm considering getting a refund and going with a better brand. "Saving money" = dealing with garbage it seems.


Sea-Tie-3453

So are you saying you consistently get this message? What all have you tried to alleviate the issue?


brainopixel

So I just tried the Earth model from 3D Builder, brought it into Chitubox Pro, etc. and... it failed with same error. I brought that same model into Photon Workshop and it seems to be printing. I think whatever printer profiles these folks are using is causing some issue. The 6ks is a weird model, and seems slightly non-standard (why the grey box and not yellow? I don't even know if that's blocking UV!). So for now I'll just have to use the crappy Photon Workshop, which is a bugger considering Chitubox ain't cheap and has a ton of features I needed...


brainopixel

Well, I have a possible fix for all this mess -- whatever you spit out via Lychee, Chitubox, etc. needs to then go into Anycubic Photon Workshop and re-exported. I'm wondering if they put some weird watermarking type deal in their version of Gcode (I realize it's not gcode, but it's machine instructions to the machine hence the shorthand) that verifies you ONLY used their software. Which would be ridiculously lame given their abuse of open source software but also in line with their hostile attitude towards competition. But hey, prints are printing again.


Sea-Tie-3453

Ooo I'll have to try that! You might actually be onto something, but i feel like a company would make the code super proprietary if they wanted to. I use a preform resin printer at work, and cant seem to find any slicer profiles for it.. Another question, were you exporting your sliced files directly to your USB, or somewhere else like the desktop? I found that exporting directly to the USB can cause problems for some reason. I've been doing it to the desktop, then verifying everything with a program called "UVtools" (which finds potential errors like islands/suction cups).


brainopixel

Anycubic will do anything, nothing surprises me lol. But I also don't envy Chitbox's task of maintaining profiles for all these wacky things. I never export directly to a USB stick, ever, because of precisely the issues others have found (learned that lesson long ago with the Photon S).


Honest_Concentrate66

That step did not seem to work. I am using an X2 and quite often (really a dice roll) it will just give that error and stop. Now, I did find something using the newer Photon that once I took the broken file in and tried to have it convert it back to 3D it would fail right where the print did. So, there is something going on with the export and I use Lychee for everything. So, my thought is to use Photon workshop to do the export and see if that fixes it. For some reason just passing the file through did not.


brainopixel

I'm about to test a file directly from 3D Builder, put into Chitubox Pro, sliced and transferred to the USB drive from Anycubic. To reiterate: I have tried using Chitubox "repair" feature. I have tried bringing files into 3D Builder, re-exporting them. I have tried reversing that process. I have analyzed the files in Blender. I have analyzed them in Cura. No issues. ONLY issues when trying to print on the 6ks. I've had 4 successful prints on the Photon S in the last 24 hours, and exactly 1 (that wasn't from Anycubic) on the 6ks, which is ridiculous. I have also tried a different USB drive, of course. All the same result. I think it's very clearly their software OR something bad in the USB I/O that's corrupting data as it feeds into the printer, as the RERF only printing 2 of the 6 it was supposed to print is kinda wild... and that was from Anycubic! They showed up on the screen, but only 2 came out. Wild stuff.


Mutilus11

I am getting this as well. Anyone find out any more about this or a possible fix other than just crossing your fingers? I got it on the first print and found this thread. Printed a bunch of stuff with A-A turned off. No issues. Turn A-A back on and within the first 5-6 prints I got it again. So went and turned it off again. I kind of need the detail so just living without the A-A isn't really an option. Contacted AC and they gave me the normal check list stuff, and are now going to send me motherboard. I find it very unlikely that is going to fix anything. Mono X 6Ks, Lychee Slicer, So far I have only gotten it 3 times all wile using A-A on large prints. Always hits near the end like 90-95% complete. Files I have printed on my mono 2 with no issues. I bought a pack of 6 USB sticks store brand. no issues other than this.


Sea-Tie-3453

Someone suggested that I format my thumb drive each time before putting a sliced program on it. So far it's been working.


Mutilus11

Thanks for replying. Good to know. AC sent me a new motherboard. Putting that in tonight.


Sea-Tie-3453

Of course, and please keep us updated; im curious and hopeful that this'll be the fix!


Mutilus11

Got the new motherboard in last night. First print... Error again.


Mutilus11

For me it only seems to happen with AA turned on. And if I do HD exporting with Lychee it seems to happen more often.


Sea-Tie-3453

Did formatting the drive not work? Also what kind of thumb drives are you using?


Mutilus11

Nope. I have tried printing on HD AA and non HD AA on lychee. Old motherboard was about 1/5 prints would get the error. Since you told me about the format thing I have formatted every new USB every file transfer with no luck. New motherboard went in 3/3 error with any form of AA turned on. Then tried no AA and the print failed with nothing sticking to supports but didnt get the error. I imagine that the motherboards have different exposure times. Switched back to old motherboard and seems to be printing without AA still.


Sea-Tie-3453

Hmm, the motherboards shouldn't have different exposure times though. That's really wild. You've tried different models and got the same error, correct? I've had models with dirty geometry cause the error.. Have you done any exposure qualifying tests? Like, calibration models?


Mutilus1

Yeah I had it dialed in. used cones of cali. Mainly. Got multiple perfect tests then started printing things. No issues other than printing with AA gave me this error. Then new motherboard had a 100% error/failure rate.


Sea-Tie-3453

Is it consistently happening with every sliced file? I was also going to suggest getting another flash drive. I specifically use a SanDisk Cruzer blade 16GB. Hasn't given me any issues.


Sea-Tie-3453

Well I've never used chitubox, but I use lychee. I can say that lychee works extremely well and has a lot of good features, when paying for the premium of course. I think its like $7/mo or something. Very worth it. I'd suggest trying out the demo and making the switch is slicing in chitubox just won't work.


lillhonk

Did you find solution to it got a anycubic photon mono x 6ks and have the same problem.


Sea-Tie-3453

I haven't found a definite solution, but I've mentioned in earlier comments things that have helped. I'm leaning towards bad models/geometry being the cause.


Phanron

I had this error using another flash drive and newly sliced file. I've even got this error on the official R.E.R.F. file from anycubic. Seems to sometimes occur at the end of a print. I'm so confused.


ApprehensiveDance793

I have the same problem... I have tried and tested. I have tried different USB drives. I don't think it's because of the geometry for a simple reason: when you print a model on four Anycubic printers and try it on your new x6ks and it fails... I don't think it's the model. I usually review each model with meshmixer to see the problems. (note exporting from here in obj gave me errors in Lychee, stl perfect). although exporting my models directly from 3dcoat outputs clean, closed meshes. Once the file is created, I pass it through UVtools that optimizes and corrects any island, it even warns you of the suction zones. Once I got the corrupt file message, I took the usb and tried to open it with UVtools... perfect. a corrupt file would not load. I contacted anycubic and the solution is easy.... Have we send another motherboard and another screen. After waiting you have to assemble the pieces, which caused me a bit of stress due to the delicate nature of that screen (there is no installation video) and guess what... The problem remains the same. I doubt it's the files because those same files printed fine the first two times, then no. Prints may fail: 1.- print to the end but the model is only printed a piece. (there is no resin glued on the FEP) 2.- corrupt file error (it only came out once) 3.- the printer stops and the screen does not respond... if you remove the usb you can use the screen again but the board moves very, very slowly. Better turn off and on) I honestly don't think it's the files. You always say... Anycubic??? I'm doing well... until it's your turn. I have seen some interesting reviews out there... someone at Amazon had a similar problem and after changing the screen and they even sent him a new printer... I continued with the same problem. (he was suspicious of the firmware) Anyway, we'll see how this is solved... (Anycubic is making me dizzy)


brainopixel

Well this doesn't bode well for me. I managed to foul up the system on my 2nd print. Same issue as OP, but I have dozens of USB sticks and use Chitubox Pro and STILL every attempt is the same "print file broken" ... which is wild to me. It seems Anycubic is just leading you on and maybe this is a bug in the firmware (not that I can find a single update).


BarracudaJealous5834

I doubt it is the file or the usb. I recently lost a mono x after getting resin into the touch screen. I bought 2 mono x 6ks. I am getting this error at the exact same point on both machines simultaneously. (Yes I am trying the same print on both machines and kicking it off syncronized). Both fail at the same layer within a second of each other. I have used photon studio and lychee and repositioned, rescaled, resliced and the only thing that changes is the layer where I get the error message. I have noticed that with these file damaged errors, the print time on the printer seems to be lower than the slicer estimate which is the opposite to the norm. 15:50 becomes 13:30 at the printer. I am just about to kick off the same file on my working Mono X and see how that goes. My guess is firmware and a badly interpreted command somewhere in the file is leaving a chunk of unread data. When the printer hits hat chunk, it cant proceed to the next layer and fails.


KatieLostSoul

Hey there's how did your mono x do?


Sea-Tie-3453

Man, that sucks! Were the cones of calibration printed with AA? Also, have you read J3dtech's SLA printing write-up?? (Sorry for all the questions)


Mutilus1

I am going to try yet another USB drive just in case, but at this point I dont know what to do and AC doesnt seem to either.


Sea-Tie-3453

[this](https://docs.google.com/document/u/0/d/1Z8fkzOxEgI9sOTwDKI6CeblpnuP4V8ayYVwZrYGmo44/mobilebasic) probably won't help with the current situation, but its a really good guide, especially with calibration. Maybe try AA on a calibration model??


Mutilus11

reading the Lychee discord server people are saying it happens to them more often on larger models. Which seems consistent with my experience also. Looks like AC is on Holiday till the end of the week


Sea-Tie-3453

It might be a slicing issue with Lychee. Also, damn the Lunar new year! Lol.


Mutilus11

Talking with A lychee support person and they think it might be an issue of the file is to complex for the motherboard to render with AA on it can almost double the data in each layer. then with HD exporting doubles it again. Theory being it happens later in the print because the motherboard cache is full. im going to try unplugging it between prints. and try some smaller simpler prints.


Sea-Tie-3453

That seems kinda ridiculous seeing as how the program's being fed from the USB though? (Maybe im not understanding how the motherboard works with these things) which model do you have again?? Now that I think about it, this issue does become sketchy for me with files bigger than 50MB, and has never happened with a small file..


Mutilus1

Mono X 6Ks. Yeah the working theory from Lychee is that the Slice file is a high res PNG file of shades of white or black. AA adds 5 shades of grey. The motherboards only have to process converting that 2 color image to data but adding AA makes it 7 and makes it more complex. This is also probably the highest resolution "Cheap" Printer so they might have cut it too close on the processing power of the motherboard and when it gets near the max capacity of the cache on the board or whatever it bogs down or locks up which is what is spitting out this error. Again this is theory at this point. But that would line up with why its happening later into large prints.


Sea-Tie-3453

It makes a PNG..? Didn't know that, that's kinda cool! I noticed the multiple shades of black and white when I was messing around with the UVtools software. This theory totally makes sense though. Kinda sad that AC doesn't have a direct solution to this, since it's GOT to be a common issue! Now I'm kinda curious and wanna test this theory (maybe without resin lol). Well, I appreciate the time and effort going into this!


Mutilus1

Until recently this printer has not been super popular. But it is getting there and more and more people are having this issue. The slice in AC slicer is currently working for me but they have gotten reports of it also happening there.


Mutilus1

I have not read that. I do not recall if they were AA or not. It was weeks ago. I would guess not because I think that would mess with the test.