Version 3.5.2 is giving me issues!
-
@infiniteloop
Oops, forgot about that. Below is the file.
Freeze_Pipe_Joint_Adapter.gcode -
@Jered
So this ghost run of the file above worked fine with no problems, so now I am going to run it again with filament. -
Below is the file.
Looked through this: Commas only occur within comments, so the GCodes are clean.
What I'm not sure about is which comments are picked-up and parsed by RRF or DWC. Then the error message mentions "line 0" - should be somewhere at the beginning of the file, the first two entries are indeed not commented out. ATM, I can't run the header on my machine due to a broken controller, so maybe @Phaedrux or @droftarts could step-in?
-
@infiniteloop
I can get rid of the comments if it helps.
Here it is without comments;
Freeze_Pipe_Joint_Adapter.gcodeThis file gave that error 75% of the way through the print. So the "line 0" part of the error doesn't even make sense.
-
This file gave that error 75% of the way through the print. So the "line 0" part of the error doesn't even make sense.
Is it still the message "Illegal parameter letter ','"? In this case, I have no clue: in the latest iteration of the file, there is not a single comma (",") to be found…
-
@infiniteloop
There error is this
Error: in job file (channel File) line 0: Illegal parameter letter ','and yes to your question.
I removed the quotes I had put around it. That being said, yes I agree, the error does not make sense. It was weird when this happened. It automatically canceled my job. Not sure if, due to the many nozzle heater faults I was having due to the bad autotune that somehow caused it.
I have never seen code with a line zero . -
@Jered one for @chrishamm
-
@Jered As this problem happened after a pause/resume event, I suspect it is the same problem as reported in another thread. Can you please run the following command on the SBC (via SSH or in a Linux terminal) and send me the output?
journalctl -u duetcontrolserver | grep -e Selected -e paused -e Illegal -
@chrishamm
I typed this in the terminal window, hit enter, and nothing happened. It didn't error either, just nothing. Would the output be in the terminal or does it store that somewhere else? -
@Jered
This finished again with no issues so I guess there is no problem. -
@Jered It should be written straight to the terminal, not sure why it didn't output anything for you.
