SOLVED 3.2-RC1 "Error: Attempting to extrude with no tool selected"



  • Duet3 with SBC and toolboard running 3.2-RC1. During a simulation run of a gcode file I get repeated errors "Error: Attempting to extrude with no tool selected"

    22.12.2020, 23:33:34	Connected to 192.168.86.30
    22.12.2020, 23:33:52	M37 P"0:/gcodes/Orbiter_Mount_Top.gcode"
    Simulating print of file 0:/gcodes/Orbiter_Mount_Top.gcode
    22.12.2020, 23:33:53	Error: Attempting to extrude with no tool selected.
    22.12.2020, 23:33:54	Download of Orbiter_Mount_Top.gcode successful after 2s
    22.12.2020, 23:33:56	Error: Attempting to extrude with no tool selected.
    [some repetitions elided]
    22.12.2020, 23:37:40	Error: Attempting to extrude with no tool selected.
    22.12.2020, 23:37:44	Error: Attempting to extrude with no tool selected.
    22.12.2020, 23:37:47	File 0:/gcodes/Orbiter_Mount_Top.gcode will print in 3h 25m plus heating time
    22.12.2020, 23:37:48	Error: Attempting to extrude with no tool selected.
    22.12.2020, 23:37:59	M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.2-RC1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
    Board ID: 08DGM-9T66A-G63SJ-6J1D6-3SD6R-9U0BA
    Used output buffers: 1 of 40 (21 max)
    === RTOS ===
    Static ram: 149788
    Dynamic ram: 62480 of which 152 recycled
    Never used RAM 146412, free system stack 130 words
    Tasks: Linux(ready,99) HEAT(blocked,277) CanReceiv(blocked,829) CanSender(blocked,352) CanClock(blocked,352) TMC(blocked,19) MAIN(running,694) IDLE(ready,19)
    Owned mutexes: HTTP(MAIN)
    === Platform ===
    Last reset 07:15:27 ago, cause: software
    Last software reset at 2020-12-22 16:22, reason: User, none spinning, available RAM 146380, slot 1
    Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
    Error status: 0x00
    Aux0 errors 0,0,0
    Aux1 errors 0,0,0
    MCU temperature: min 31.7, current 33.2, max 33.4
    Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
    Driver 0: position -1600, standstill, reads 61059, writes 24 timeouts 0, SG min/max 0/997
    Driver 1: position -46400, standstill, reads 61059, writes 24 timeouts 0, SG min/max 0/869
    Driver 2: position 10344, standstill, reads 61072, writes 11 timeouts 0, SG min/max 0/0
    Driver 3: position 0, standstill, reads 61064, writes 19 timeouts 0, SG min/max 0/127
    Driver 4: position 0, standstill, reads 61064, writes 19 timeouts 0, SG min/max 0/108
    Driver 5: position 0, standstill, reads 61064, writes 19 timeouts 0, SG min/max 0/137
    Date/time: 2020-12-22 23:37:57
    Slowest loop: 170.81ms; fastest: 0.03ms
    === Storage ===
    Free file entries: 10
    SD card 0 not detected, interface speed: 37.5MBytes/sec
    SD card longest read time 0.0ms, write time 0.0ms, max retries 0
    === Move ===
    DMs created 125, maxWait 25693583ms, bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves 309651, completed moves 309651, hiccups 0, stepErrors 0, LaErrors 0, Underruns [43, 0, 1], CDDA state -1
    === AuxDDARing ===
    Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === Heat ===
    Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP* is doing "M122" in state(s) 0
    Telnet is idle in state(s) 0
    File* is idle in state(s) 0
    USB is idle in state(s) 0
    Aux is idle in state(s) 0
    Trigger* is idle in state(s) 0
    Queue* is idle in state(s) 0
    LCD is idle in state(s) 0
    SBC is idle in state(s) 0
    Daemon is idle in state(s) 0 0, running macro
    Aux2 is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty.
    === CAN ===
    Messages queued 104542, send timeouts 0, received 313542, lost 0, longest wait 2ms for reply type 6049, free buffers 47
    === SBC interface ===
    State: 4, failed transfers: 0
    Last transfer: 0ms ago
    RX/TX seq numbers: 10719/10719
    SPI underruns 0, overruns 0
    Number of disconnects: 0, IAP RAM available 0x2c8a8
    Buffer RX/TX: 0/0-0
    === Duet Control Server ===
    Duet Control Server v3.2.0-rc1
    Code buffer space: 4096
    Configured SPI speed: 8000000 Hz
    Full transfers per second: 38.04
    Maximum length of RX/TX data transfers: 3240/1664
    

  • administrators

    If you do not select a tool in the start G-code of your print and if you do not have a tool selected before you start the simulation, this error message can be expected. RRF needs to know the print tool during a simulation in order to work out the extrusion times.

    If you somehow select the tool in the start G-code, please share the file.



  • @oliof That'll be because you haven't selected a tool. If you only have a single tool, then the simplest thing to do is put T0 somewhere in your config.g file. If you have multiple tools, put T(n) at the start of you slicer gcode to select whichever tool it is that you want to use.


Log in to reply