open estuary
I keep having this error with my Voron 2r 350 recently. Printer stops printing around 90% into print. Perhaps not same % each time. Printer stays on but cools down.
'Unable to parse move G1 x260.454 Y73.743(E0.0273'
Any ideas how to solve. I would hate to have a printer I can no longer use.
blazing ravine
I don't think Gcode is supposed to have random open brackets
try replacing it with a simple space
open estuary
I don't think Gcode is supposed to have random open brackets
try replacing it wi...
Thank you. Any Idea how that happened? How would I go about doing that?
blazing ravine
no clue how but .gcode files are just text so you can search for the caracter in any plaintext editor and replace it
open estuary
I did not know that. This seems to be happening everytime I sliced a file now using Cura. Trying an updated version of Cura to see if that helps.
blazing ravine
weird that it only occurs rarely in the file then, not like a bunch of times where it ends up occuring at the start
open estuary
weird that it only occurs rarely in the file then, not like a bunch of times whe...
I am so frystrated about it as the Voron is my fav printer and it feels like a massive paperwight right now.
blazing ravine
you should check your inserted Gcode for stuff like print start, end or nozzle parking, those settings are just text fields for Gcode that gets inserted directly in to the file for those actions
Is it always the exact same line or do the coordinates change?
blazing ravine
try some random small trinkets to see if they fail too
open estuary
Think my start and end is okay.(?)
blazing ravine
yeah that looks fine, there isn't even an G1 in there, which would be the problem
open estuary
used text editor and yeah there is the bracket. changing to a space. Probably should try printing it now?
blazing ravine
worth a try, I'd print something small first as a test
or try slicing something new and immediately checking the output for brackets
blazing ravine
np 👍
open estuary
Got a print on, will update if issue is still happening.
stuck pebble
Last time I’ve seen that kind of issue the SD card was dying and randomly corrupting bits
blazing ravine
Very plausible
SD cards are extremely low write cycles compared to stuff like SSDs
open estuary
Last time I’ve seen that kind of issue the SD card was dying and randomly corrup...
Problem is the error is occuring before it is being sent to the SD card. I save directly to the computer first then to the Voron but I checked the computer file.
