Retraction mid print... why?
-
This is the file from the SD Card: https://drive.google.com/open?id=0B8esATZjqHgvSG5E...
And this is the file printed from the mac: https://drive.google.com/open?id=0B8esATZjqHgvX0N4...
Thanks Ryan, I had performed prints in the past from the SD Card but in the last few days it has started doing this.
-
@JA88AtheHUTT said:
I had performed prints in the past from the SD Card but in the last few days it has started doing this.
With the same file, or a new file that you sliced?
-
With the same file. I have also tried slicing the file again incase it was corrupted during the process but end up with the same result.
-
If the difference occurred whilst printing with the same file, then logically it doesn't seem possible that the G-Code has anything to do with it, then.
Does it happen at exactly the same point in the print, or is it random?
The Vector 3 runs Sprinter firmware, which we're not entirely familiar with. Our guess, though, is that the issue is more related to firmware than to G-Code.
-
Yes it is happens at exactly the same point each time.
-
-
We're kind of at a loss... there's nothing in the G-Code that seems to command a retraction at layer 94.
We might be able to find something from a tool we have to analyze our terminal output. Can you print again with the Mac and export the Terminal Log after the print is completed? I know the issue occurs only when printing from the SD card, but if there's a command that's being sent as a result of the slicer, it should appear when printing with the Mac, too. It might just be that MatterControl is suppressing the naughty move.
http://wiki.mattercontrol.com/Send_Debugging_Information#Other_Useful_Files
-
Here is the log, printed with no issues. https://drive.google.com/open?id=0B8esATZjqHgvRWJO...
-
Thanks-- I had the development team generate a G-Code file based on what the log output (we have a tool that does this) an everything looks normal on our side. Granted, that was generated for the computer, which you say never has this same problem, yet the G-Code generated for both should be the same; ergo, the issue is likely to do with the printer or the printer's firmware, but most likely not MatterControl.
Basically, everything looks normal and appears to be working normally on our side, which logically if everything was indeed working correctly, would only leaves the printer as far as we can tell.
-
Thanks for helping me narrow down the issue Ryan. I'll check into the firmware and see if I can resolve the issue.