Attempting to extrude with no tool selected - During Print

grabercars · 13 Apr 2019, 19:08

@phaedrux said in Attempting to extrude with no tool selected - During Print:

What firmware versions are you running?

M115 returns : Version 2.02(rtos) electronics duet wifi 1.02 or later. Date 2018-12-24b1

Phaedrux · 13 Apr 2019, 19:43

If it happens again, try to scan through the console page to see any other error messages, and send a M122 to get a diagnostic report.

dc42 · 14 Apr 2019, 11:12

Also you might want to turn logging on.

jaurand · 28 May 2019, 10:58

i also am getting these same error messages during a print. really confused as what could be happening as they occur at about 6hrs in two separate prints

dc42 · 28 May 2019, 11:10

@jaurand said in Attempting to extrude with no tool selected - During Print:

i also am getting these same error messages during a print. really confused as what could be happening as they occur at about 6hrs in two separate prints

Have you searched your GCode file for T commands, and checked that they all refer to tools that you have created using M563 commands in config,g?

jaurand · 28 May 2019, 12:08

@dc42 I have not, as the GCode file is 45MB and I was able to successfully complete other smaller prints with no issue. I only have one tool and it starts the print just fine. Would it be better to put the T command in Cura in the startup file section? (sorry at work and not sure of the exact term)

The only odd thing I can think may be an issue is I used Curas "Print on my Printer" selection rather than uploading the file to Duet and then printing from the browser.

jaurand · 28 May 2019, 19:05

@dc42 just ran the same file and completed without any error, only difference was uploading it directly to duetwifi and starting print from web browser.

There must have been an error when having Cura begin the print and the file might have corrupted on the transfer I suppose?

dc42 · 28 May 2019, 20:02

@jaurand said in Attempting to extrude with no tool selected - During Print:

There must have been an error when having Cura begin the print and the file might have corrupted on the transfer I suppose?

It does sound like that. You may have a USB ground loop, see the wiki for details.

jaurand · 30 May 2019, 09:32

@dc42 said in Attempting to extrude with no tool selected - During Print:

USB ground loop

well i got the same error again last night. I'm not even connected via USB is the thing, all over wifi

dc42 · 30 May 2019, 10:25

Do you have logging enabled (M929)? If so, is there anything of interest in the log file?
Did the error occur in the same place as previously?
If you upload the file back to your PC from the Duet, does it compare exactly with the original?

jaurand · 30 May 2019, 12:46

@dc42 said in Attempting to extrude with no tool selected - During Print:

Do you have logging enabled (M929)? If so, is there anything of interest in the log file?

Did the error occur in the same place as previously?

If you upload the file back to your PC from the Duet, does it compare exactly with the original?

I do not have logging enabled on the config file itself, but I did export the console log file and it only thing that states was the error attempting to extrude with no tool selected, literally an hour after i first started the print.
This error occurred much earlier than last time, on layer 2 of the print rather than 8 hours into my previous print.
Comparing the file (checked early in the file since error occurred at layer 2) everything looks the same.

At least positive thing to note since once the error occurs the printer does continue to print just does not extrude so at least I do not have a spaghetti monster mess of filament

deckingman · 30 May 2019, 12:58

@jaurand said in Attempting to extrude with no tool selected - During Print:

........................................................
The only odd thing I can think may be an issue is I used Curas "Print on my Printer" selection rather than uploading the file to Duet and then printing from the browser.

That is the most likley cause IMO. To prove it one way or another, try uploading the file and printing from the SD card.

dc42 · 30 May 2019, 13:09

@jaurand, does your system include a PanelDue, and if so, how long is the cable and what baud rate are you using for its connection?

jaurand · 30 May 2019, 13:15

@dc42 It does include a Paneldue, baudrate is set to 57600 on both the panel and in the config file using M575.

At work at the moment so not able to be exact on cable length but its not super long, maybe 12 to 16 inches.

dc42 · 30 May 2019, 13:41

Please send M575 P1 to your Duet from the console and check that the response includes "requires checksum".

jaurand · 30 May 2019, 18:54

@dc42 said in Attempting to extrude with no tool selected - During Print:

M575 P1

Yep requires check sum

M575 P1
Channel 1: baud rate 57600, requires checksum

dc42 · 31 May 2019, 08:13

We had situations a few years ago in which commands from PanelDue were getting corrupted and causing printing to stop. That's why we set the port to require a valid checksum. Unfortunately it's only and 8-bit checksum, so errors can still get through. In case this is causing the problem, I suggest you test whether the problem goes away if you disconnect the PanelDue. If it does, then check the PanelDue cable for a bad connection. The resistance of the cable must be not more than 0.1 ohm per conductor.

jaurand · 31 May 2019, 11:09

@dc42 i was wondering to myself if it could be the paneldue. I do get some checksum errors still passed on. I'll try out next week a few more prints to see if that it and test the resistance.

dc42 · 3 Jun 2019, 16:15

@jaurand said in Attempting to extrude with no tool selected - During Print:

@dc42 i was wondering to myself if it could be the paneldue. I do get some checksum errors still passed on. I'll try out next week a few more prints to see if that it and test the resistance.

Checksum errors suggest that there is a problem with the PanelDue to Duet link. For every 255 checksum errors reported, there is probably 1 case of data corruption that isn't detected and may cause problems.

What microstepping settings are you using? It's possible the use of high microstepping could increase interrupt latency and give rise to data reception errors. the 2.03 firmware series has some changes to help avoid this happening. So you could upgrade your firmware to 2.03RC4 and see whether the checksum errors reduce or go away.

jaurand · 3 Jun 2019, 16:15

@dc42 Tested connectors on paneldue and all are below 0.1 ohms. Currently unplugged paneldue and printing will see if any issues arise.

I am only running X16 microstepping with interpolation at the moment as my motors are stock with the printer and I did not have very detailed information regarding the specs.