Duet constantly "busy" and repeatedly homing axes
-
Hello,
I'm having an issue where my duet 3 is constantly "busy" but I'm not sure with what. When I send commands the response is hit or miss and sometimes just does not go through. Also, when I home Y or X it will get stuck in a loop and just keep homing over and over, as if the duet is running the command again and again. Not sure if the two issues are related.
I'm using a duet 3 with a Jubilee CoreXY printer. Attached is my config file config.g
And here is the output from the M122 command:
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.01-RC9 running on Duet 3 MB6HC v1.01 or later
Board ID: 08DJM-956BA-NA3TJ-6JTDJ-3S06S-1T82TUsed output buffers: 1 of 40 (11 max)
=== RTOS ===
Static ram: 154572
Dynamic ram: 162480 of which 24 recycled
Exception stack ram used: 216
Never used ram: 75924
Tasks: NETWORK(ready,2084) HEAT(blocked,1184) CanReceiv(suspended,3412) CanSender(suspended,1484) CanClock(blocked,1432) TMC(blocked,216) MAIN(running,4856) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:18:24 ago, cause: software
Last software reset at 2021-04-15 23:39, reason: User, spinning module LinuxInterface, available RAM 75924 bytes (slot 2)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 35.3, current 36.5, max 36.6
Supply voltage: min 24.2, current 24.3, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Driver 0: standstill, reads 25148, writes 15 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 25148, writes 15 timeouts 0, SG min/max 0/0
Driver 2: standstill, reads 25149, writes 15 timeouts 0, SG min/max 0/0
Driver 3: standstill, reads 25148, writes 16 timeouts 0, SG min/max 0/0
Driver 4: standstill, reads 25149, writes 16 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 25150, writes 15 timeouts 0, SG min/max 0/0
Date/time: 2021-04-16 00:20:53
Slowest loop: 299.81ms; fastest: 0.14ms
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 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 ready with "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 0 0, running macro
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
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 2.73ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8- Ethernet -
State: disabled
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 4416, longest wait 1ms for type 6021
=== Linux interface ===
State: 0, failed transfers: 1
Last transfer: 14ms ago
RX/TX seq numbers: 36722/36722
SPI underruns 1, overruns 1
Number of disconnects: 0
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.2
Trigger:
Buffered code: M98 P"/sys/Toffsets.g" ; Set tool offsets from the bed
Buffered code: M501 ; Load saved parameters from non-volatile memory
==> 64 bytes
Executing macro config.g, started by system
Next stack level
Code buffer space: 4076
Configured SPI speed: 8000000 Hz
Full transfers per second: 92.72
Maximum length of RX/TX data transfers: 3112/352 - Ethernet -
-
@eadiecd I suggest you upgrade the firmware as you're way out of date. You're on 3.01-RC9 whereas 3.2.2 is the latest stable version
Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@jay_s_uk said in Duet constantly "busy" and repeatedly homing axes:
@eadiecd I suggest you upgrade the firmware as you're way out of date. You're on 3.01-RC9 whereas 3.2.2 is the latest stable version
Ah OK I'll give that a shot later today and update the post with how it goes, thank you
-
@jay_s_uk So I tried updating to 3.2.2 by following the instructions here:
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware
Typing Sudo apt update and suso apt upgrade into the terminal. That seemed to work but then I boot up the duet and it says I'm still running 3.01RC9.Am I updating the firmware incorrectly? That would explain why I thought I was using the latest firmware, because I've already done this process once before.
Thanks!
Chris -
Try sending M997 to in the gcode console to flash the firmware in place. If that doesn't work, you can manually flash the firmware with USB and BOSSA to get back into sync.
-
@phaedrux M997 seems to have worked. I'm not sure exactly what the issue was with the old firmware but the printer is now homing correctly and is displaying "Idle" as a status.
https://drive.google.com/file/d/10fzywBkVRxp7CDl_rvN-dk83wXclh5Gd/view?usp=sharing
Thank you!
Chris -
Sometimes when using a release candidate or beta things can get out of sync. Was this the firmware that came on the board originally or were you using the RC via the unstable branch update method on the Pi?
