Frustrating SD Card Error
Quick update on this, so I've now run probably 30+ hours of prints through with my "super-clean-every-possible-cause-removed" setup...
So far no failures (other than the wierd spaz-out that happened a couple days ago from my earlier post).
That said, after replacing the SD card in the past, it would make it upwards of 80+ hours of printing without failures, then the SD card failures seem to accumulate more rapidly, starting maybe every 10+ prints, and increasing to every 5 prints, then eventually every 2nd print, or every print.
So I'll continue testing. Just posting the update that so far I've not been able to re-create the error using this setup. Unfortunately this isn't a workable long-term setup, I'll need to re-introduce some of those potential causes eventually, but first I want to be 100% sure that it's holding up in this config, then I'll slowly re-introduce other factors, and again test extensively. Hopefully that will let me (eventually) nail down the root cause. Unless it fails in the next 40-50 hours of prints, in which case none of the eliminated factors are the root cause.
@bhudson Ok so prints have been working well, continued testing in my 100% clean environment. Today I decided that I've put enough prints through it, that it seems to be working in the clean setup...
So I removed the PLA, ran 2 purges to be sure. That all worked fine.
When I queued up the print job and started it, it started transferring, and then all of a sudden the printer disconnected and I got the error again that said the job failed to transfer, reconnect and try again. A few seconds later the printer suddenly started emitting a loud beeping noise, and all the fans ramped up to 100%, and the LED on the filament spool button turned purple. I couldn't connect to it with my PC, I tried the Root, it also couldnd't detect it, I didn't know what to do so I powered it off... Let it sit a few minutes, and now if I power it back on, it immediately resumes the loud beep and purple LED...
No idea what to do now. Will update my Ticket with CEL UK as well with this info, but I have to leave for work now, so will have to resume this evening. I just wanted to fire this off in case someone had some suggestions on that one. (for now the printer is unplugged, and sitting idle).
@glasswalker The printer doesn't have a speaker or a way to make a beeping sound. I suggest you look at another source. If it is indeed the printer you are looking at a short causing the printer mainboard to restart, protect itself and shut down, and then restart in a loop. It may be a PSU failure, though I haven't seen this exact behavior before.
Purple/pink LED on the spool button is usually a short on the 5VDC circuit.
@bhudson It was definitely the printer, or directly related to the printer (turning the printer off with the power switch instantly kills the beeping sound, and turning it back on instantly resumes the beeping).
I'll investigate further when I get home. But thanks, at least knowing the Purple/Pink LED means a short would seem to indicate that's something to look into...
Will post again later this evening once I've looked into it further to have more concrete information.
@bhudson the printer is plugged into a simple "dumb" power strip which plugs straight into the wall (as part of our other troubleshooting). I was holding off on buying a UPS until I had nailed down that it is definitely power related for example... There is a (very small) chance that the power strip has some kind of beep circuit in it, but that again would indicate a fairly major power issue (short on the AC line or something) causing it to trip.
Anyway, I can't explore further until I'm back home. For now it's 100% unplugged for safety until I get home.
@bhudson, ok, home now, and after being powered off for the afternoon and disconnected, I tentatively reconnected power to the robox, and powered it on. No beeping, no purple/pink LED.
So I hooked it back up and tried a test print, and it's printing fine now... This is bloody weird behavior.
So I'm not 100% sure it was the printer, but I'm still like 99% sure. The beeping appeared to be coming from the printer itself, it's plugged into a simple "dumb" power strip which goes straight into the wall, and nothing else in that area (aside from my PC) is capable of making that noise. The PC isn't connected to the Robox at all.
And as I said when I killed the power, it immediately stopped, and when I powered it back on before it immediately started (within only a couple ms of hitting the switch kind of thing).
Anyway, beeping aside, as you suggested pink/purple means 5V short, which is disturbing...
I'm wondering if there is some kind of intermittent failure/damage in the power supply itself, causing all these strange intermittent errors I've been seeing (including the SD card errors?)
Anyway, running another test now... Will let you know if the wierd beeping comes back. (and I'll try a bit harder to narrow down it's exact source)
@glasswalker I have no idea. I suspect that you have local power issues that caused the PSU to go into some type of loop and you were actually hearing a capacitor whine, but that is total guesswork. I would look into a filter. A good battery backup will act as a filter, but if you aren't ready to afford that you can look into a stand-alone filter that will clean up the power. I have one on my system and that may be part of the reason I have never had a power issue on my PC or printers.
Another quick update, after that one time, the "Purple LED + Beeping" thing hasn't repeated.
It has however repeated the "Transmission Error" a couple more times. Each time it ends up in that wierd loop of not being able to cancel the job, where it repeats errors, and the state gets messed up essentially.
Restarting the printer, AND automaker, seems to solve the problem, failure to do BOTH of those tasks results in the same error over and over again on the same print until both tasks are completed.
No more SD card failures so-far. Will start re-introducing factors soon that may have been causing the SD card errors, however I'm wondering as I mentioned in my earlier post, if this is all related somehow, perhaps to a power supply problem.
Will keep at it.
@glasswalker I had the same problem, where I received constant SD card errors on a 4 hour build (in Draft) in Software version 3.0. Since it would not work in draft I wasn't about to try it in 8 hour 'Normal' mode, but I accidentally did and it worked without SDCard errors almost all of the time. I occasionally found that if I turned my model 90 degrees, sometimes it would get an SDCard error in Normal. So, I have no proof but, I strongly suspect that the SDCard problem is either/and/or mathematical/software related (divide by zero, out of bounds etc), or a real error is falling through to the SDCard error response (improperly handled error), which is why changing many SDCards, 3 computers, new high-priced cables etc would not solve the issue, but a resolution-mode change would. So, I updated just now to 3.02 with Firmware r765 and did a successful build in Draft. Here's the Cel-Robox link to 3.02 http://www.cel-robox.com/downloads/ I'd be interested in hearing if 3.02 solves your problem.