I think I found a bug

[RKS7204]

Hello,

My printer is a delta printer
Board: Duet 2 Ethernet (2Ethernet)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta7 (2021-12-16)

I have to run M999 after startup. If I don't do that I get errors, and the head won't move.

23/12/2021 23:02:49 G28
23/12/2021 23:02:38 Connection established
23/12/2021 23:02:31 Connection interrupted, attempting to reconnect...
HTTP request timed out
23/12/2021 23:02:22 M999
23/12/2021 23:02:14 Error: G0/G1: insufficient axes homed
23/12/2021 23:02:13 Warning: Driver 1 warning: phase A may be disconnected, phase B may be disconnected
Warning: Driver 2 warning: phase A may be disconnected, phase B may be disconnected
Warning: Driver 0 warning: phase A may be disconnected, phase B may be disconnected
23/12/2021 23:01:45 G28
Warning: Driver 1 warning: phase A may be disconnected, phase B may be disconnected
Warning: Driver 2 warning: phase A may be disconnected, phase B may be disconnected
Warning: Driver 0 warning: phase A may be disconnected, phase B may be disconnected

Steve

[Phaedrux]

@rks7204 said in I think I found a bug:

phase A may be disconnected, phase B may be disconnected

Are you certain your motors don't have a bad crimp?

Can you send M122 and M98 P"config.g" and post the results?
Can you also share your config.g and homedelta.g?

[RKS7204]

@Phaedrux

After sending M999 all motors are moving. If I don't send M999 I get the "disconnected" error. I believe that if it is a bad crimp, sending M999 wouldn't solve it.

23/12/2021 23:14:33 M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta7 (2021-12-16 12:22:11) running on Duet Ethernet 1.02 or later
Board ID: 08DGM-95BNL-MGPSN-6JKFJ-3S86L-12XRX
Used output buffers: 3 of 24 (19 max)
=== RTOS ===
Static ram: 23804
Dynamic ram: 68812 of which 0 recycled
Never used RAM 19344, free system stack 136 words
Tasks: NETWORK(ready,26.3%,230) HEAT(notifyWait,0.0%,330) Move(notifyWait,0.0%,305) MAIN(running,73.6%,440) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:12:10 ago, cause: software
Last software reset at 2021-12-23 23:02, reason: User, GCodes spinning, available RAM 19320, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 22.6, current 24.9, max 25.2
Supply voltage: min 24.2, current 24.4, max 24.5, 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
Events: 0 queued, 0 completed
Driver 0: pos 81255, standstill, SG min 0
Driver 1: pos 80409, standstill, SG min 15
Driver 2: pos 80836, standstill, SG min 49
Driver 3: pos 0, standstill, SG min n/a
Driver 4: pos 0, standstill, SG min n/a
Driver 5: pos 0
Driver 6: pos 0
Driver 7: pos 0
Driver 8: pos 0
Driver 9: pos 0
Driver 10: pos 0
Driver 11: pos 0
Date/time: 2021-12-23 23:14:31
Cache data hit count 4294967295
Slowest loop: 13.25ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 5, maxWait 22861ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 5, completed 5, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 17.56ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex

TripodMaker
Status
Idle
Mode: FFF
Tool Position
X
0.0
Y
0.0
Z
500.60
Extruder Drives
Drive 0
0.0
Speeds
Requested Speed
0 mm/s
Top Speed
0 mm/s
Sensors
Vin
24.4 V
MCU Temperature
24.8 °C
Z-Probe
542
Tools
Extra
Control Heaters
Tool Heater Current Active Standby Tool 0
T0 - Load Filament Heater 1
active 18.5 °C

Bed Heater 0
off 18.1 °C

Temperature Chart
23/12/2021 23:15:50 M98 P"config.g"
HTTP is enabled on port 80
FTP is enabled on port 21
TELNET is disabled

Config.g :

; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Dec 21 2021 21:14:01 GMT+0100 (Midden-Europese standaardtijd)

; General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"TripodMaker" ; set printer name
M665 R167.220 L350.3926 B160 H505.578 X0.345 Y0.210 Z0; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0.38 Y-0.02 Z-0.36 ; Put your endstop adjustments here, or let auto calibration find them

; Network
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; enable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X100.00 Y100.00 Z100.00 E166.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 Z0 S1 ; set minimum Z

; Endstops
M574 X2 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop" ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin zstop

; Z-Probe
M558 P1 C"!zprobe.in" H5 F120 T6000 R1 A5 X0 Y0 Z0 ; set Z probe type to unmodulated and the dive height + speeds
G31 P800 X0 Y0 Z-0.1 ; set Z probe trigger value, offset and trigger height
M557 R145 S20 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 R0.228 K0.256:0.000 D3.08 E1.35 S1.00 B0 ; enable PID mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"fan0" Q250 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q250 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
;M950 F2 C"fan2" Q250 ; create fan 2 on pin fan2 and set its frequency
;M106 P2 S2 H100:101:102 T44:65 L0.3 ; set fan 2 value. Thermostatic control is turned on
M308 S2 Y"drivers" A"DRIVERS" ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet
M308 S3 Y"mcu-temp" A"MCU" ; configure sensor 3 as on-chip MCU temperature sensor
M950 F2 C"fan2" Q100 ; create fan 2 on pin fan2 and set its frequency
M106 P2 H2:3 L0.15 X1 B0.3 T40:70 ; set fan 2 value

; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X9 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
T0 S0 ; select first tool
M912 P0 S3.2 ; calibrate MCU temp

HomeDelta.g :

; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Dec 21 2021 22:18:44 GMT+0100 (Midden-Europese standaardtijd)
G91 ; relative positioning
G1 H1 X805 Y805 Z805 F1800 ; move all towers to the high end stopping at the endstops (first pass)
G1 H2 X-5 Y-5 Z-5 F1800 ; go down a few mm
G1 H1 X10 Y10 Z10 F360 ; move all towers up once more (second pass)
G1 Z-5 F6000 ; move down a few mm so that the nozzle can be centred
G90 ; absolute positioning
G1 X0 Y0 F6000 ; move X+Y to the centre

Steve

[Phaedrux]

Ok so you're resetting the printer and getting these errors. I think that's actually normal. Or am I not understanding again?

[RKS7204]

@phaedrux
When i power on the printer. Ik get these errors. And the motors don't move. After I reset the printer with M999 the errors are gone. I can start printing.

Steve

[rjenkinsgb]

Out of curiosity, what happens if you add

G4 S5

(a five second delay) near the top of your config, between the general and network sections?

[RKS7204]

@rjenkinsgb

That doesn't make a difference

Steve

[rjenkinsgb]

OK. Is the 24V (or 12v) power permanently on, or controlled somehow by the Duet board?

[RKS7204]

@rjenkinsgb
The power is not controlled by the duet bord.
I use a physical switch on the printer.
When the printer is off, there is no power suplied to the board.

Steve

[natthapol.v]

@rks7204 looks like a similar issue here.
https://forum.duet3d.com/topic/26261/3-4-0beta6-home-limit-switch-bug

It happened to me on the new 3.4 firmware as well. But only if I set acceleration to a high value (>8000-10000mm/min)
Funny is, this number works on 3.3 without Phase disconnected warning.

[RKS7204]

@rks7204 said in I think I found a bug:

M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2)

My accelerations (as listed above) are not even near those high numbers.