Attempting to extrude with no tool selected.
-
You've got some problems in your config.g to sort out.
M98 P"config.g" Error: in file macro line 14 column 29: M551: string too long
Password command is missing a closing quote "
Error: in file macro line 32 column 22: M350: array too long, max length = 1
You define 2 Extruder drives but only have values for 1 extruder.
Error: in file macro line 68: M591: parameter 'D' too high
You've got pressure advance for two extruder drives, but only a single extruder was properly configured.
Error: Fan number 2 not found Error: Fan number 8 not found
Phantom fans.
Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.
Remove the M375 at the end of config.g. You should only load the heightmap after you've defined Z0 by probing.
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 241C Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 1000C
These are just warnings about what your max temps could be in a runaway condition.
-
Okay. I changed some of the things in the config.g, but the change I made to homeall.g appears to have resolved the problem. Apparently somewhere along the line homing the tool coupler axis was removed from the scene. Odd as it would do it with a G28 or clicking the home all button.
homeall.g
; homeall.g ; called to home all axes ; G91 ; relative positioning G1 Z5 F6000 H2 ; lift Z relative to current position ; Tool changer we want to home Y first to pull away from tools. ; Home Y M98 P"homey.g" ; Home X M98 P"homex.g" ; Home Z M98 P"homez.g" ; Home C (Tool Coupler) M98 P"homec.g" G90 ; absolute positioning G1 X200 Y200 F6000 ; Move to center of bed. ;Load height map from file G29 S1
I wasn't sure where the best place to move the M375 command. But I placed it in the movez.g so it executes after a Z homing.
homez.g
; homez.g ; called to home the Z axis ; G91 ; relative positioning G1 Z5 F6000 H2 ; lift Z relative to current position G90 ; absolute positioning ; Z-Axis probe likely triggers beyond tool height. ; If we have an active tool we need to drop it now. if state.currentTool >= 0 M28 "/sys/tprevious.g" T{state.currentTool} M29 M98 P"/sys/tactive.g" > null ; Delete the register file so we don't try to dock again. M30 "/sys/tactive.g" G1 X200 Y200 F6000 ; go to first probe point G30 ; home Z by probing the bed ;; Points are not related to bed coordinates, but rather probe coordinates. ;; 2 Point G30 P0 X29 Y200 Z-9999 ; Left Center G30 P1 X373 Y200 Z-9999 S2 ; Right Center ; Load previous tool M98 P"/sys/tprevious.g" M30 "/sys/tprevious.g" ; Load Height Map M375
-
Okay. I remember removing it from the homeall.g on purpose as I can't check to see if my tool is loaded upon startup without being able to check for the existence of my tactive.g file. My understanding is this ability to check for a file existence within the system will be coming in a future firmware update...
I'm just going to have to be cautious. This is why I tell the system to unload the tools at the end of prints. Some tools are going to be taller than my probe and it could be quite disastrous if I can't be sure how the system responds.
-
Well, I jumped too soon. Still having the problem. It's not consistent but does happen more so after a print. I have had it happen just after a restart as well.
I'm going to keep messing around to see if I can get some consistency...
-
It's still not clear to me when and where those errors are being thrown.
-
I can understand the confusion as it's a head scratcher for me.
I still need more testing, but so far this appears to only happen when running a Job.
It appears to occur when I run G28.
TC-Basics.gcode
T-1 G28 ; home all axes
and I will get different results. I would expect if it was related to a short, there be some indication of what the system was detecting.
If I run G28 from the web console it executes, so far every time.
Only seems bomb when I run it within a Job.
-
Here is the output from the console when I run those two lines of code within a job:
3/14/2021, 3:45:09 PM Printing paused at X200.0 Y200.0 Z6.0 C123.0 3/14/2021, 3:45:05 PM Resume state saved Duet3D rotating magnet filament monitor v3 on pin e0stop, enabled, sensitivity 25.50mm/rev, allow 40% to 180%, check every 3.0mm, version 3, mag 133 agc 102, measured sensitivity 24.86mm/rev, min 98% max 102% over 258.5mm Error: Attempting to extrude with no tool selected. 3/14/2021, 3:44:58 PM Leadscrew adjustments made: -0.045 0.001, points used 2, (mean, deviation) before (-0.022, 0.014) after (0.000, 0.000) Warning: Macro file /sys/tprevious.g not found 3/14/2021, 3:44:21 PM Warning: Macro file /sys/tactive.g not found 3/14/2021, 3:44:02 PM M32 "0:/gcodes/TC-Basics.gcode" File 0:/gcodes/TC-Basics.gcode selected for printing
-
@Gamefanatic3D said in Attempting to extrude with no tool selected.:
; Home C (Tool Coupler) M98 P"homec.g"
What's in homec? And how bout your tool change files?
Can you also post the first 50 lines or so of a sliced gcode file so we can see what it's doing during a job?
-
Homec is for the E3D Tool Changer motor.
homec.g
M400 G91 ; Relative coordinates ; M913 C80 ; Crash fallback: Set C motor to lower current, but <= 80 was unstable low. G1 H1 C10 F5000 ; Space min end or stall at max end, needed for acceleration towards near min end. G1 H1 C-1000 F5000 ; Try to stall at min end, reset to min-axis M203 = 0 coordinate M400 G92 C0 ; Crash fallback: coordinates reset to 0 in case stall did not reset to min-axis M203 coordinate G90 ; Back to absolute coordinates M913 C100 ; Set C motor 100% current ;Open Coupler M98 P"/macros/Tools/Tool-Unlock"
Tool-UnLock
; Unlock tool M400 M906 C600 ; Raise motor current a bit. M400 if !move.axes[3].homed && move.axes[3].userPosition==0 ; We are assuming a tool is loaded and we want to unload it. ; G1 C-83 F2500 H1 else G1 C123 F2500 H1 M400 M906 C400 ; Put it back to normal M400
-
Tpre tpost tfree?