"G28 Error: G0/G1: insufficient axes homed" after months of use

ignacmc

Hello to all

Today I was going to print in my Predator Delta (Duet3Mini5+ with optical endstops) but just after start up and connecting to the network, when I try to home the axes, the motors didn't even energize and I got the error "G28 Error: G0/G1 insufficient axis homed". What can it be? I have not touched anything in the wiring or electronics for months, and I have not upgraded the firmware since 3.3.0 release. I have been printing all this time without problems.

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: ZBNF5-FV9RL-D65J0-40KM8-1NW2Z-RTPTG
Used output buffers: 7 of 40 (19 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 105912 of which 24 recycled
Never used RAM 35044, free system stack 196 words
Tasks: NETWORK(ready,12.2%,240) HEAT(notifyWait,0.0%,366) Move(notifyWait,0.1%,334) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(delaying,0.6%,115) MAIN(running,85.6%,426) IDLE(ready,0.8%,29) AIN(delaying,0.8%,273), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:30 ago, cause: power up
Last software reset at 2022-01-05 20:50, reason: User, GCodes spinning, available RAM 35044, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 30924, completed 30924, timed out 0, errs 0
Step timer max interval 752
MCU temperature: min 19.5, current 22.0, max 22.0
Supply voltage: min 24.1, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 129195, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 1586, writes 11, timeouts 0, DMA errors 0
Driver 1: position 129195, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 1586, writes 11, timeouts 0, DMA errors 0
Driver 2: position 129195, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 10, reads 1587, writes 10, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 1588, writes 9, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 1588, writes 9, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2022-01-06 00:18:10
Cache data hit count 58914266
Slowest loop: 6.82ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle 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
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 274, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 154/0/0
Tx timeouts 0,0,153,0,0,119 last cancelled message type 30 dest 127

=== Network ===
Slowest loop: 13.41ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address 8c:aa:b5:f7:d1:82
WiFi Vcc 3.31, reset reason Power up
WiFi flash size 2097152, free heap 23360
WiFi IP address 192.168.1.73
WiFi signal strength -45dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

bot

Did the way you call G28 change at all? There are different macros for G28 X, or Y, or all of them, etc. Maybe one of your macros is not playing nicely with a new slicer start g-code.

ignacmc

@bot No, in fact if i just issue G28 from the console, the error appears

giostark

@ignacmc
Hi,
If you didn't touch anything (and before was working) it sound as the endstop are not read correctly.
Try to clean all of them. Look if the red light are operational.
Have you checked all the endstop? Try a singular independent move to see if all of them work regularly:
Testing the motors and endstops individually
https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareDeltaPrinter#Section_Testing_the_motors_and_endstops_individually

Not related now because you receive the error soon as you try to move, but it could be useful in future: When the head was placed on the extreme part of the bed and try to home is also happened that in the home.g this line had the X Y Z parameters too small and received your same error:
; Move all towers to the high end stopping at the endstops (first pass)
G1 X640 Y640 Z640 F2500 H1

I'm at shortage of other ideas... hope some more expert can provide more suggestions

Phaedrux

Can you check your endstop state with M119 and post your full config? Also please send M98 P"config.g" for good measure and share the results?

jay_s_uk

@ignacmc post your config.g please

ignacmc

@phaedrux

ignacmc

@jay_s_uk config.g

Here you have it...sorry for the verbosity of my comments

jay_s_uk

@ignacmc nothing i can see if your config file.
can you post homedelta?

ignacmc

@jay_s_uk homedelta.g

jay_s_uk

@ignacmc nothing in there either that would cause issue

ignacmc

@jay_s_uk Yes, I have been printing with these config files for months without issues. I suspect some hardware problem. As I was going to replace my LDO 0.9 motors for OMC equivalents, I will do it and recheck all wiring at the same time...

dc42

@ignacmc here's the problem, in your homedelta.g file:

G1 X0.01 Y0.01 Z0.01

Either add H2 to that line, or replace it by:

M17 X Y Z ; enable motors for stealthChop tuning

M17 is implemented in RRF 3.3 and later.

ignacmc

@dc42 David....you are a father to me! It did the trick...

Stupid me, I forgot I have made that change a few days ago while researching here how to tune Stealthchop and didn't print since then so I was not aware of the problem I had just created.

Today in Spain is the Fairy Kings day, when tradionally Christmas presents arrived. This has been a very nice one!

Thanks for your outstanding support!

Ignacio