Page 1 of 2

Retraction is not working anymore with 3.1

Posted: Wed Jun 08, 2016 2:58 am
by SvenZHB
Hello,

retraction does not work for me anymore with version 3.1.

Code: Select all

08:41:24
Error: invalid M Code: M103
08:41:24
Error: invalid M Code: M103
08:41:23
Error: invalid M Code: M103
08:41:23
Error: invalid M Code: M103
Error: invalid M Code: M103
Error: invalid M Code: M103
08:41:22
Error: invalid M Code: M103
08:41:21
Error: invalid M Code: M103
08:41:20
Error: invalid M Code: M103
The option is unchecked at the settings page.
Settings
Settings
I reported this error already to the support.
I don't think I did something wrong as I used the Factory-file from version 3.02 and changed nothing special.

Best regards,

Sven

Re: Retraction is not working anymore with 3.1

Posted: Wed Jun 08, 2016 4:21 am
by dkightley
I think retraction IS working....but there's an issue with the code that generates the M101 - M103 alternative retraction codes. With the option set to off, you're getting M103 commands.

Re: Retraction is not working anymore with 3.1

Posted: Wed Jun 08, 2016 6:41 am
by SvenZHB
But this results in a not working retraction for my printer.

Re: Retraction is not working anymore with 3.1

Posted: Wed Jun 08, 2016 7:07 am
by CompoundCarl
Why would this cause anything different with the printer? It's just sending you a warning saying it doesn't know what that command is. It should still do it's retractions the exact same as before, except it sends one extra response over serial saying it doesn't know what to do with the M103.

So my guess would be that retractions are happening the exact same as they would normally, but you're just seeing some extra messages from the firmware.

To confirm, I tried this with a few of my printers and added a bunch of random commands it wouldn't know (M123456, G3843298, etc). It sends the same types of messages back saying it doesn't know what that command is, but still keeps printing just fine. I don't see any difference in what the printer actually does.

Re: Retraction is not working anymore with 3.1

Posted: Wed Jun 08, 2016 7:19 am
by mroek
I wonder which setting is causing those M103 commands to be sent. I'm using a different printer (Duplicator i3), and I also have that check box unchecked, and I'm not seeing any M101-M103 in the generated G-code. That implies that there is some other setting that is causing/affecting the software to emit those commands.

But as CompoundCarl quite correctly states, the printer should simply ignore any commands that it doesn't recognize, and no real harm is done.

Re: Retraction is not working anymore with 3.1

Posted: Wed Jun 08, 2016 7:21 am
by mroek
On second thought, could it be that they are (erroneously) sent only when printing directly from Simplify3D? Could you try to save a G-code file and check if the file also contains those M103 commands?

Re: Retraction is not working anymore with 3.1

Posted: Wed Jun 08, 2016 7:40 am
by SvenZHB
I always store my files to SD-card. As my printer doesn't know the M103-command no retraction is done by the printer.

Re: Retraction is not working anymore with 3.1

Posted: Wed Jun 08, 2016 7:58 am
by CompoundCarl
Again, even if the printer doesn't understand the M103 command, it doesn't change anything else in the file. It will just ignore that line.

So if you still have retraction commands in the file (which I confirmed your file does), then it will still retract. To take it a step further, I even ran part of your gcode file on a printer that doesn't understand M103 commands, and it sent back the same messages saying it was ignoring those lines, but still retracted exactly as I would expect. So your file is working fine for me.

Re: Retraction is not working anymore with 3.1

Posted: Wed Jun 08, 2016 10:19 am
by SvenZHB
Yes you are right.
I did a short test print with my old settings for retraction behaviour. I tried to reduce the amount of retraction and maybe this was too much.
The support will change this problem hopefully within the next version.

Re: Retraction is not working anymore with 3.1

Posted: Sat Jun 25, 2016 1:36 pm
by kokop76
Definitely seeing the unneeded M103 codes with the option unchecked. This is definitely the kind of error that should be caught in testing.