Busy? With what?

[wmmc01]

Just got my CoreXY running with Duet Wifi, and have been able to heat the hotend and bed, and extrude, and print a couple of items - however now after changing to a diff nozzle, I heat it up (225) which is fine. But then I want to extrude some filament and the printer shows "Busy" on the web and the panel due - and it does nothing. This keeps happening now. Can't control anything. FW: 2.02(RTOS) (2018-12-24b1)

[dc42]

If you send M122 from a different channel, it will tell you what command(s) the other input channels are busy executing.

[wmmc01]

@dc42 said in Busy? With what?:

M122

Here is the output - not sure where the issue would be. I see Scheduled Moves is 1, Completed moves is 0. Is this the extrude I am trying? Once I am at temp, and hit Extrude it goes busy, but extrudes nothing. I can't even turn off the heater.:
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9568A-F23SD-6J1F2-3S46R-KVPMF
Used output buffers: 1 of 20 (15 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98560 of which 0 recycled
Exception stack ram used: 328
Never used ram: 6660
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3788) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:06:28 ago, cause: power up
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 6660 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 35.6, current 35.9, max 36.1
Supply voltage: min 12.0, current 12.2, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2019-01-08 16:29:39
Cache data hit count 1474374868
Slowest loop: 1.89ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 239, MinFreeDm: 239, MaxWait: 363691ms, Underruns: 0, 0
Scheduled moves: 1, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is ready with "M122 " in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 167.44ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0

[dc42]

@wmmc01 said in Busy? With what?:

=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is ready with "M122 " in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0

Looks like nothing is active except the move that you mentioned. Is it executing a move very slowly?

[wmmc01]

It doesn't do anything. I set the temp, it reaches temp, I tell it to extrude, the screen/web states Busy, and it does nothing. I am trying to calibrate e-steps and this keeps happening. I can print an stl, but this process continues to do nothing, and I know I am way under extruded. No motion at all. And the only way to get Busy to go away is turn it off. This happens with Both the Web interface and the PanelDue i7.

Edit: Ok, I have to Home each Axis before I can manually extrude. Is this normal? Seems an odd constraint.

[dc42]

@wmmc01 said in Busy? With what?:

Ok, I have to Home each Axis before I can manually extrude. Is this normal? Seems an odd constraint.

No, that's not a constraint. To extrude you need to select a tool that uses that extruder (e.g. by sending a T command), and either heat the tool to above minimum extrusion temperature or enable cold extrusion. If those conditions are not met, the Extrude button in DWC will be deactivated. If you try to extrude directly by sending a G1 Ennn Fnnn command, an error message will be returned.

[wmmc01]

I am using the interfaces, not gcode commands. I use either web interface or the PanelDue to set the extruder temp. When it gets to the set temp is when I hit extrude 100mm (or whatever) in either the web or PanelDue - that doesn't enable the same thing? I still have to manually send a T gcode command?

[wmmc01]

Just checking, any thoughts?

[aidar]

Hi.

In your original post, what you mean by" changing to diff nozzle" ? Did you cange just nozzle of your hotend or trying to use other hotend? Can you post your config.g file?

[wmmc01]

@aidar I replaced one nozzle with another. Not related to this. Please see notes above.