RE: Core One crash/restart
Fell for it again. Burning through ~1kg of ASA gave me 0 reboots, but doing 3 hours of PLA on structural profile I already got ~4 reboots, J guess it is PSU acting weird on low temps and it has to be replaced. (I got replacement, just didn't install it yet)
Hi everyone, before the PSU came to me, I tightened all the cable ties in printer (learned that the connectors vibrating is a big nono and need to be arrested when researching building voron) and I also moved printer a bit to the left and started printing voron parts....
And magic happened! 25+ hours of various printing with no restarts.
Really hope it helps anyone.
Returning the printer anyway due to other hardware flaws with the machine that I paid 1000€ for.
RE: Core One crash/restart
Fell for it again. Burning through ~1kg of ASA gave me 0 reboots, but doing 3 hours of PLA on structural profile I already got ~4 reboots, J guess it is PSU acting weird on low temps and it has to be replaced. (I got replacement, just didn't install it yet)
Hi everyone, before the PSU came to me, I tightened all the cable ties in printer (learned that the connectors vibrating is a big nono and need to be arrested when researching building voron) and I also moved printer a bit to the left and started printing voron parts....
And magic happened! 25+ hours of various printing with no restarts.
Really hope it helps anyone.
Returning the printer anyway due to other hardware flaws with the machine that I paid 1000€ for.
For what it's worth, I replaced my PSU and it did not change the behavior.
RE: Core One crash/restart
Hello, I've been following this thread since I got my Core One. I have the same issue. Mine sounds most similar to darkmattermaker where it reboots primarily during long engagements of the x axis motor. If I let it sit there and reboot enough times, it will eventually throw a puppy error where it can't communicate with the xbuddy extension board.
I also have my printer hooked up to a UPS for troubleshooting - mine measures power draw. I didn't think it was PSU related because it's not rebooting when it draws the most power (when it's heating up the bed and element). I checked all of the cable connections I could get to easily and all of that seems to be fine.
After being able to trigger 2 reboots by simply touching the X axis motor while printing, I got to thinking that this may be a grounding issue. The chassis is powdercoated it looks like, and there are specific spots masked off to allow contact.
Using a multimeter, I looked for continuity between the X motor and the chassis ground. On my unit, there is no continuity measured from the bright screws at the top of the motor to the chassis on the X motor - but there is continuity from the same spot on the Y motor.
I hooked up a jumper between one of the X motor screws and the exposed chassis ground right below where the X motor is mounted on the left side of the unit. I have my left panel removed to make troubleshooting easier - this might not be as easy to do with the panel installed. I would include a picture, but the 'Add Media' button in the editor does not appear to do anything.
I've been checking on it regularly and I don't believe the printer has rebooted since I did this yesterday morning. My theory is that a static charge is building up in the X axis motor chassis due to the belt motion, and because it isn't grounded, eventually discharges somewhere that triggers the power panic. This is my first 3D printer, so maybe this doesn't make sense, but either way it seems to have helped. The issue has been intermittent and seems to be project-dependent, so I'm hesitant to say it's fixed for certain. I'm in the middle of a long print, but there are other projects I can print when I'm done that would more reliably trigger a reboot.
I am curious whether anyone else with a multimeter can confirm whether their working or non-working Core One has continuity between the X motor top screws and chassis ground.
Andrew
RE: Core One crash/restart
Hello, I've been following this thread since I got my Core One. I have the same issue. Mine sounds most similar to darkmattermaker where it reboots primarily during long engagements of the x axis motor. If I let it sit there and reboot enough times, it will eventually throw a puppy error where it can't communicate with the xbuddy extension board.
I also have my printer hooked up to a UPS for troubleshooting - mine measures power draw. I didn't think it was PSU related because it's not rebooting when it draws the most power (when it's heating up the bed and element). I checked all of the cable connections I could get to easily and all of that seems to be fine.
After being able to trigger 2 reboots by simply touching the X axis motor while printing, I got to thinking that this may be a grounding issue. The chassis is powdercoated it looks like, and there are specific spots masked off to allow contact.
Using a multimeter, I looked for continuity between the X motor and the chassis ground. On my unit, there is no continuity measured from the bright screws at the top of the motor to the chassis on the X motor - but there is continuity from the same spot on the Y motor.
I hooked up a jumper between one of the X motor screws and the exposed chassis ground right below where the X motor is mounted on the left side of the unit. I have my left panel removed to make troubleshooting easier - this might not be as easy to do with the panel installed. I would include a picture, but the 'Add Media' button in the editor does not appear to do anything.
I've been checking on it regularly and I don't believe the printer has rebooted since I did this yesterday morning. My theory is that a static charge is building up in the X axis motor chassis due to the belt motion, and because it isn't grounded, eventually discharges somewhere that triggers the power panic. This is my first 3D printer, so maybe this doesn't make sense, but either way it seems to have helped. The issue has been intermittent and seems to be project-dependent, so I'm hesitant to say it's fixed for certain. I'm in the middle of a long print, but there are other projects I can print when I'm done that would more reliably trigger a reboot.
I am curious whether anyone else with a multimeter can confirm whether their working or non-working Core One has continuity between the X motor top screws and chassis ground.
Andrew
I checked mine with a multimeter. I do not get continuity between the bright screws on the top of either motor and the chassis ground. Shouldn't the green wire in the motor cable provide ground? Forgive me, I'm not an electronics engineer so I'm not super familiar with this sort of thing.
RE: Core One crash/restart
@noumenonsense, that's a promising idea and observation! On my Core One, both motors are grounded to the chassis. But that must just be luck, not by design -- looking at the build instructions, and if I recall correctly from my own build, none of the areas where the mountings screw heads meet the frame has been masked off before powder coating.
For what it's worth, I have not experienced any random crashes on this printer. But take that with a grain of salt: While I have done a couple of large prints, these did not involve long, straight, fast motor runs. So I might just not have gotten into the "danger zone"...
@darkmattermaker -- the four motor cables only connect to the internal motor windings, two windings with two connections each. These windings are isolated from the body of the motor (and the shaft with the pulley). Hence, if the belt movement would cause some buildup of static electricity, that could only be discharged via a separate ground connection to the motor body -- or via a spark discharge through the powder coating, which might derail the microcontroller or the "power panic" logic.
RE: Core One crash/restart
@noumenonsense, that's a promising idea and observation! On my Core One, both motors are grounded to the chassis. But that must just be luck, not by design -- looking at the build instructions, and if I recall correctly from my own build, none of the areas where the mountings screw heads meet the frame has been masked off before powder coating.
For what it's worth, I have not experienced any random crashes on this printer. But take that with a grain of salt: While I have done a couple of large prints, these did not involve long, straight, fast motor runs. So I might just not have gotten into the "danger zone"...
@darkmattermaker -- the four motor cables only connect to the internal motor windings, two windings with two connections each. These windings are isolated from the body of the motor (and the shaft with the pulley). Hence, if the belt movement would cause some buildup of static electricity, that could only be discharged via a separate ground connection to the motor body -- or via a spark discharge through the powder coating, which might derail the microcontroller or the "power panic" logic.
RE: Core One crash/restart
@noumenonsense, that's a promising idea and observation! On my Core One, both motors are grounded to the chassis. But that must just be luck, not by design -- looking at the build instructions, and if I recall correctly from my own build, none of the areas where the mountings screw heads meet the frame has been masked off before powder coating.
For what it's worth, I have not experienced any random crashes on this printer. But take that with a grain of salt: While I have done a couple of large prints, these did not involve long, straight, fast motor runs. So I might just not have gotten into the "danger zone"...
@darkmattermaker -- the four motor cables only connect to the internal motor windings, two windings with two connections each. These windings are isolated from the body of the motor (and the shaft with the pulley). Hence, if the belt movement would cause some buildup of static electricity, that could only be discharged via a separate ground connection to the motor body -- or via a spark discharge through the powder coating, which might derail the microcontroller or the "power panic" logic.
RE: Core One crash/restart
@noumenonsense, that's a promising idea and observation! On my Core One, both motors are grounded to the chassis. But that must just be luck, not by design -- looking at the build instructions, and if I recall correctly from my own build, none of the areas where the mountings screw heads meet the frame has been masked off before powder coating.
For what it's worth, I have not experienced any random crashes on this printer. But take that with a grain of salt: While I have done a couple of large prints, these did not involve long, straight, fast motor runs. So I might just not have gotten into the "danger zone"...
@darkmattermaker -- the four motor cables only connect to the internal motor windings, two windings with two connections each. These windings are isolated from the body of the motor (and the shaft with the pulley). Hence, if the belt movement would cause some buildup of static electricity, that could only be discharged via a separate ground connection to the motor body -- or via a spark discharge through the powder coating, which might derail the microcontroller or the "power panic" logic.
RE: Core One crash/restart
Sorry about the quadrupled post. The server had stopped responding just when I clicked "Submit", so I clicked another time after 15 seconds or so. Not sure where the third and fourth post come from? I have asked the moderators to clean up.
RE: Core One crash/restart
This is a good theory. I'm wondering if mine sitting on carpet played any role too regarding static buildup. I had it on the floor for a few weeks until I could get a table sturdy enough for it as I was afraid it would tip the dresser I initially put it on. I'll have to try one of the offending prints with those movements (in my case it was organizer baskets) again and see how it does. The partial nozzle clogs seem to correlate with it in my case too from what I can tell.
Hello, I've been following this thread since I got my Core One. I have the same issue. Mine sounds most similar to darkmattermaker where it reboots primarily during long engagements of the x axis motor. If I let it sit there and reboot enough times, it will eventually throw a puppy error where it can't communicate with the xbuddy extension board.
I also have my printer hooked up to a UPS for troubleshooting - mine measures power draw. I didn't think it was PSU related because it's not rebooting when it draws the most power (when it's heating up the bed and element). I checked all of the cable connections I could get to easily and all of that seems to be fine.
After being able to trigger 2 reboots by simply touching the X axis motor while printing, I got to thinking that this may be a grounding issue. The chassis is powdercoated it looks like, and there are specific spots masked off to allow contact.
Using a multimeter, I looked for continuity between the X motor and the chassis ground. On my unit, there is no continuity measured from the bright screws at the top of the motor to the chassis on the X motor - but there is continuity from the same spot on the Y motor.
I hooked up a jumper between one of the X motor screws and the exposed chassis ground right below where the X motor is mounted on the left side of the unit. I have my left panel removed to make troubleshooting easier - this might not be as easy to do with the panel installed. I would include a picture, but the 'Add Media' button in the editor does not appear to do anything.
I've been checking on it regularly and I don't believe the printer has rebooted since I did this yesterday morning. My theory is that a static charge is building up in the X axis motor chassis due to the belt motion, and because it isn't grounded, eventually discharges somewhere that triggers the power panic. This is my first 3D printer, so maybe this doesn't make sense, but either way it seems to have helped. The issue has been intermittent and seems to be project-dependent, so I'm hesitant to say it's fixed for certain. I'm in the middle of a long print, but there are other projects I can print when I'm done that would more reliably trigger a reboot.
I am curious whether anyone else with a multimeter can confirm whether their working or non-working Core One has continuity between the X motor top screws and chassis ground.
Andrew
RE: Core One crash/restart
I had similar problem for two weeks. Tried all the things mentioned in the earlier replays - did not help. Small prints, like calicat were ok but larger ones got so many restarts that quality dropped beyound acceptable even if the printer continued printing. But now I have two good quality 15 hour prints at my desk together with some smaller ones. Not a single failure anymore. I just replaced the official, fancy metal USB stick with my old one - that was it.
RE: Core One crash/restart
I just replaced the official, fancy metal USB stick with my old one - that was it.
Just to add to this: I had a few USB stick related errors too. Just to be extra safe, I've bought the SanDisk MobileMate (really small microSD reader) and a SanDisk Max Endurance microSD card. I'm using two of these in my dashcam for a few years now and didn't have a single error.
Not the cheapest storage solution for the Core One, but also not really expensive and definitely worth it for me to be as safe as possible.
I just wish for a black edition of these SD cards... Maybe I'll paint it..
RE: Core One crash/restart
I have the same problem. Printer dies and restarts on diagonal movements. Prusa support is clueless. Printer is basically bricked now.
RE:
I just replaced the USB and I'm printing a file that has consistently restarted 20-30 mins into the print. It's currently at 1 hour and 24 mins. So it looks like after all this troubleshooting and replacing parts, it might be as basic as a USB issue. 🤣
I'll keep you guys updated, it's a 7 hour 41 mins print. Hopefully I can get back to printing as I have a fairly big backlog due to the printer downtime. 🤣
RE: Core One crash/restart
False alarm. 3 hours 30 mins in it restarted. I thought it might be too good/easy to be true. Back to square one. Sigh.
RE: Core One crash/restart
False alarm. 3 hours 30 mins in it restarted. I thought it might be too good/easy to be true. Back to square one. Sigh.
Bummer! I tried swapping the USB stick early on, I didn't have any luck either.
Has anyone heard back from support with potential causes or solutions?