DWC and Paneldue does not show the actual print status

smoki3

Hi,

I have an issue with my Duet 2 SBC. I am on the latest official release 3.2.

My problem is that if I cancel a print an start a new one afterwards, Duet Web control and the Paneldue doesn't jump into print mode.

The both tell "busy" but if I go to the "Status" page I get a button with "print again". On the Panel due also the micro stepping buttons are hidden in this case.

Veti

what version of the web control are you running?
which version of the paneldue firmware?

smoki3

@Veti

The latest official versions:
DWC 3.2
Paneldue 3.2.9

chrishamm

Are you using cancel.g? If yes, please share its content. M122 should show you what command the firmware is waiting for.

smoki3

@chrishamm

No i don't have a cancel.g

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 SBC version 3.2 running on Duet 2 1.02 or later + SBC (SBC mode) + DueX5
Board ID: 08DLM-996RU-N85T0-6J1F2-3S46L-1UTMP
Used output buffers: 5 of 24 (24 max)
=== RTOS ===
Static ram: 17008
Dynamic ram: 62532 of which 60 recycled
Never used RAM 32480, free system stack 110 words
Tasks: Linux(ready,68) HEAT(blocked,295) DUEX(blocked,35) MAIN(running,468) IDLE(ready,20)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 03:40:48 ago, cause: power up
Last software reset at 2021-01-15 13:44, reason: User, none spinning, available RAM 32968, slot 1
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x04
Aux0 errors 567,567,567
MCU temperature: min 19.5, current 30.8, max 31.4
Supply voltage: min 24.1, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 16581, ok, SG min/max 0/1023
Driver 1: position 6097, standstill, SG min/max not available
Driver 2: position 9830, standstill, SG min/max not available
Driver 3: position 4500, standstill, SG min/max 0/115
Driver 4: position 800, standstill, SG min/max 0/109
Driver 5: position 7228, ok, SG min/max 0/1023
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, ok, SG min/max 0/1023
Driver 8: position 0, standstill, SG min/max 0/1023
Driver 9: position 0, standstill, SG min/max 0/27
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-01-21 11:25:16
Cache data hit count 4294967295
Slowest loop: 156.14ms; fastest: 0.13ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
DMs created 83, maxWait 4364841ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 2803, completed moves 2798, hiccups 2, stepErrors 0, LaErrors 0, Underruns [0, 0, 3], CDDA state 3
=== 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, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File* is doing "G1 X132.850006 Y95.878998 E0.532420" 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
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== DueX ===
Read count 1, 0.00 reads/min
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 15ms ago
RX/TX seq numbers: 58070/58070
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x0d8dc
Buffer RX/TX: 1776/3288-0
=== Duet Control Server ===
Duet Control Server v3.2.0
File:
Buffered code: G1 X132.850 Y95.879 E0.53242
Buffered code: G1 X132.537 Y95.879 E0.00688
Buffered code: G1 X115.671 Y79.013 E0.52269
Buffered code: G1 X115.671 Y79.327 E0.00688
Buffered code: G1 X132.223 Y95.879 E0.51297
Buffered code: G1 X131.909 Y95.879 E0.00688
Buffered code: G1 X115.671 Y79.641 E0.50324
Buffered code: G1 X115.671 Y79.955 E0.00688
Buffered code: G1 X131.595 Y95.879 E0.49351
Buffered code: G1 X131.281 Y95.879 E0.00688
Buffered code: G1 X115.671 Y80.269 E0.48378
Buffered code: G1 X115.671 Y80.583 E0.00688
Buffered code: G1 X130.967 Y95.879 E0.47406
Buffered code: G1 X130.653 Y95.879 E0.00688
Buffered code: G1 X115.671 Y80.897 E0.46433
Buffered code: G1 X115.671 Y81.211 E0.00688
Buffered code: G1 X130.339 Y95.879 E0.45460
Buffered code: G1 X130.026 Y95.879 E0.00688
Buffered code: G1 X115.671 Y81.524 E0.44487
Buffered code: G1 X115.671 Y81.838 E0.00688
Buffered code: G1 X129.712 Y95.879 E0.43515
Buffered code: G1 X129.398 Y95.879 E0.00688
Buffered code: G1 X115.671 Y82.152 E0.42542
Buffered code: G1 X115.671 Y82.466 E0.00688
Buffered code: G1 X129.084 Y95.879 E0.41569
Buffered code: G1 X128.770 Y95.879 E0.00688
Buffered code: G1 X115.671 Y82.780 E0.40596
Buffered code: G1 X115.671 Y83.094 E0.00688
Buffered code: G1 X128.456 Y95.879 E0.39624
Buffered code: G1 X128.142 Y95.879 E0.00688
Buffered code: G1 X115.671 Y83.408 E0.38651
Buffered code: G1 X115.671 Y83.721 E0.00688
==> 1528 bytes
Code buffer space: 1656
Configured SPI speed: 8000000 Hz
Full transfers per second: 9.44
Maximum length of RX/TX data transfers: 5239/1696
File /opt/dsf/sd/gcodes/Display_Housing.gcode is selected, processing

chrishamm

Thanks for the diagnostics output, it looks like it's still printing a file and busy processing a G1 code. Did you send M122 when it was stuck in the "busy" state? And did you cancel/restart the print from PanelDue? Does it make any difference when you cancel/restart the print from the web interface?

smoki3

@chrishamm

So yes, the printer is actually printing. But the DCW and PanelDue is not showing on the Status Page that it is printing. So I can not cancel my print on the "soft way" (just by doing an emergency stop).

I canceled and started a new print via panel due.

smoki3

If I do an emergency stop and start a new print the DWC is showing "printing" instead of "busy".

It doesn't make any difference if I cancel the print from the Paneldue or the DWC.

Once I cancel one file the printer doesn't go to "printing again" always only "busy". It also doesn't make any difference if I use the "print again" button or select the job again from the list.

This also happens if try to start another gcode.

chrishamm

Please ZIP up your sys directory and upload it, then I'll try to reproduce your problem.

smoki3

@chrishamm

Sure:

https://drive.google.com/file/d/12BHjItNynpZUoFNisMo6L-Hr6kTsQpC1/view?usp=sharing