Catastrophic error when printing #150
Comments
|
Hmm.. sorry you are having issues. I think you're the first person I've seen who is using Repetier, so maybe this is connected somehow. I ran your code through two different visualizers to see if I could figure out what's going on, but didn't see anything obvious, which doesn't mean this is not a problem with ArcWelder itself. Here is simplify3D's visualization:
And the PrettyGcode viewer (it uses marlin's arc interpolation algorithm, so it is very accurate):
Can you see if you can pinpoint exactly where on your print the issue happened? I see that little string, but I'm wondering if we can tie it to a specific piece of gcode somehow. Also, if you have calipers, can you measure the exact height? I have to go through this gcode by hand to figure it out, and narrowing it down will save hours of work. Next, would you be willing to try installing the latest version of the console application and run your original gcode through that and send me the results (or just post the original and I can do it). I did not write, nor do I maintain the cura plugin, so its simpler for me if you use the console version. I added a bugfix for one issue that could cause problems (however, I would expect the issue to be obvious, but maybe not). If I can find changes, or pinpoint the gcode, we might be able to run a (highly) supervised test on your printer. I'd like to know if the gcode is bad, but looks good, or if the firmware has some issues running arcs (I can add those to the firmware tester). Thanks for posting! |
|
|
|
Awesome photos, thanks! I should be able to narrow it down quite a bit from this. I will also look at the firmware source and add it to the inverse processor. That should give us a lot more info. |
|
The control board is an MKS Robin Mini. I think it is a custom firmware developed by the manufacturer, and sadly closed source. |
|
@Troutzorz, the bin is not particularly useful, but thanks for posting it! I might be able to glean some info from it. The thought of decompiling it or working out the assembly makes me shudder, lol! Still, if it is a fork of Repetier (I have some connections into that world), I might be able to figure out what is going on. However, I don't want to get ahead of myself. Step one is to make figure out of there is some obvious gcode issue at or near the point of failure. If the gcode is accurate and valid, the next step is to figure out why the firmware had problems. If the gcode is broken, I will be able to fix the issue myself. This is no small task, but I will take it one step at a time and will do whatever I can to fix any issues that I discover. |
|
I have the same printer having the same issue with ArcWelder. |
|
Can one of you send an M115 command to your printer and paste in the results? I can update my firmware Library at least and warn others that way hopefully. |
|
Because I got my QQ-S last week and because I'm curious like hell I tried to print @Troutzorz gcode, running a telnet monitor to the printer. Error at 23.35mm... Maybe it helps a bit to find the reason... |
|
Ok, I have it down to an exact layer now, and i was able to find that error in the Repiter github: Not sure what is going on yet, but it looks like i have yet another firmware interpolation routine to integrate into ArcStraightener to figure this out :) We can ALMOST safely label this a firmware issue now, but I'm going to try to run this on my hardware if possible first, to make sure it prints well on at least one printer. If it fails, then it's a gcode problem. |
|
Hope this is helpful. Send: M115 |
|
Quick update: I'm doing some work on ArcStraightener, and am planning to add two new interpolation routines, one of which will be Repiter. I will also add Klipper, and potentially some marlin forks. I'm hoping this will lead to a better understanding as to why you are seeing these failures. |
|
@Troutzorz this may seem a strange question but are you printing from USB or SD card? If USB, does the same problem occur if you print from SD card? It may be completely unrelated but I'm having similar (ish) issues with my Sidewinder. Not got the bottom of it yet. I need to try out the latest bugfix branch when I get a moment. |
|
Just wanted to add me to the list with my flsun q5 (very similar to the qq-s).
|
|
Same "catastrophic" behavior here while using Arc Welder as a Cura 4.9.1 plugin or as an OctoPrint plugin, I keep all my software and plugins constantly updated. All runs under Arch Linux. The same G-Code without the Arc Welder treatment completes regularly, same behaviour with 5 different objects until now. My printer is a stock hardware TwoTrees Sapphire Plus v1, firmware upgraded with Marlin v2.0.7.2 pre-built by AuroraTech (configs: https://auroratechchannel.com/download/ep10.zip , explanatory video: https://www.youtube.com/watch?v=GbHsNCDrTpY). I suspect that the same arcwelded-gcode may give the problem almost randomly at different printing points, but I don't have a sacrificial printer, so I prefer to keep Arc Welder disabled to keep my puppy-printer safe :-) while hoping the RX buffer is enough to not underrun on long arcs. |
|
Just had same issue, half way through print and arm flew off the board. Any updates on this issue? Also this issues aside, smashing plugin, usually good results. Great work very much appreciated! |
|
Usually producing good results. However, like others I find the effector flying off the print and colliding with the edge of the bed. Printer: Flsun Q5 |
Cura 4.8, ArcWelder Cura plugin 3.5.1
Printer FLSUN QQ-S Pro
I tried ArcWelder for the first time, using the cura plugin. The print was going great until a little over 23mm Z when the effector swung wildly off course and crashed into the tower. When I tried to stop the print, it seemed frozen so I had to cut the power to recover. If I was not there to cut the power, this could have badly damaged the printer.
I am including the gcode file which caused the error.
Roller Handle.gcode.txt
And an image of the incident.
The text was updated successfully, but these errors were encountered: