Version 3.5.2 is giving me issues!
-
What firmware version were you using before?
Did your expansion boards get updated as well?
Standalone or SBC mode?After the print has errored, can you gather a M122 report for the mainboard and any expansion boards?
Does it happens at the same spot?
Maybe do a dry run test print.@Jered said in Version 3.5.2 is giving me issues!:
"Error: in job file (channel File) line 0: Illegal parameter letter ','"
Can you share that job file?
-
@Phaedrux
I believe the last version was 3.3, but honestly I never updated this data in the config.
I am running in SBC mode and I did update all boards. The thing that is really getting me is the temp overshoot. It seems the new autotune sucks. I found my old values before using the latest method from your site and now it works fine. It was over shooting be 15 deg then faulting out. The autotune process itself works fine, but the values for R is way off.Here is the M122 dataM122 Info.txt
Currently I am running the gcode with no filament as you suggested. This run has the old autotune values and has not faulted as of yet. If it finishes, I will consider this good and will run the file again with filament.
I do really appreciate this forum and your help. You guys are the best! And because of your dedication, I never really get worried that problems with your products will get fixed. I am still wondering what caused this error "Error: in job file (channel File) line 0: Illegal parameter letter ','". Any ideas?
-
I am still wondering what caused this error "Error: in job file (channel File) line 0: Illegal parameter letter ','". Any ideas?
In the post above, @Phaedrux asked you to share the job file in question:
Can you share that job file?
Either that, or you start looking for a comma (”,”) in some wrong place within the job file yourself.
-
@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.
