Attempting to extrude with no tool selected - During Print

dc42

@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

@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

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

@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

@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

@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

@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

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

jaurand

@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

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

@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

@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

@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.

jaurand

@dc42 No issues with the print from tool selection with paneldue unplugged. I'll look into updating the firmware next and determine if this reduces the checksum errors

jaurand

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

So you could upgrade your firmware to 2.03RC4 and see whether the checksum errors reduce or go away.

upgraded to 2.03RC5 and still getting checksum errors

dc42

What sort of cable do you have between the PanelDue and the Duet? Is it running close to stepper motor wires for any appreciable distance?

jaurand

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

What sort of cable do you have between the PanelDue and the Duet? Is it running close to stepper motor wires for any appreciable distance?

I'm running the 4 pin wire. The cable is not close to any stepper motor wires

dc42

It sounds to me like a signal quality issue, but it could possibly be caused by an overloaded MCU. Are you using unusually high microstepping?

jaurand

@dc42 just x16 with interpolation

dc42

I am surprised you are getting checksum errors. I don't recall seeing see any reported on my delta for over a year, and the PanelDue cable is about 1.3m long.

You could try reducing the baud rate to 38400 or 19200 at both ends, to see if the checksum errors go away.