No Axis Movement

1d1

Done. Homing moves X and Y - no Z. Here is M122:

Q5
Send code...
Status
Idle
Mode: FFF
Tool Position
X
0.0
Y
0.0
Z
210.00
Extruder Drives
Drive 0
0.0
Speeds
Requested Speed
0 mm/s
Top Speed
0 mm/s
Sensors
Vin
24.2 V
MCU Temperature
32.8 C
 Tools
 Extra
 Control All
Tool	Heater	Current	Active	Standby
Tool 0
T0 - Load Filament	Heater 1
off	20.7 C	
0
0
Bed	Heater 0
off	20.9 C	
0
0
Temperature Chart
M122
9/16/2020, 11:12:11 AM	M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-956GU-DJMSN-6JTDA-3S46Q-TUQHH
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 92916 of which 56 recycled
Exception stack ram used: 264
Never used ram: 9856
Tasks: NETWORK(ready,292) HEAT(blocked,1224) MAIN(running,1824) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:41 ago, cause: software
Last software reset at 2020-09-16 11:10, reason: User, spinning module GCodes, available RAM 9624 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 31.2, current 32.7, max 33.0
Supply voltage: min 24.1, current 24.2, max 24.4, 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: 2020-09-16 11:12:09
Cache data hit count 168900657
Slowest loop: 2.20ms; fastest: 0.13ms
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.3ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, 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, chamberHeaters = -1 -1 -1 -1
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.75ms; fastest: 0.00ms
Responder states: HTTP(2) 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.23
WiFi MAC address 5c:cf:7f:76:71:a9
WiFi Vcc 3.29, reset reason Unknown
WiFi flash size 4194304, free heap 24616
WiFi IP address 192.168.1.54
WiFi signal strength -48dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
9/16/2020, 11:11:59 AM	M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-05-19b2
9/16/2020, 11:10:38 AM	Connection established
9/16/2020, 11:10:36 AM	Connection interrupted, attempting to reconnect...
9/16/2020, 11:10:28 AM	G28
Error: G0/G1: insufficient axes homed
9/16/2020, 11:10:28 AM	Emergency stop, attemping to reconnect...
9/16/2020, 11:10:11 AM	Connection established
9/16/2020, 11:08:50 AM	Connection interrupted, attempting to reconnect...
HTTP request timed out
9/16/2020, 11:08:37 AM	Upload of config.g successful after 1s
9/16/2020, 10:48:26 AM	M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-05-19b2
9/16/2020, 10:06:42 AM	G28
Error: Failed to enable endstops
9/16/2020, 10:00:42 AM	G28
Error: Failed to enable endstops
9/16/2020, 10:00:05 AM	Connection established
9/16/2020, 10:00:04 AM	Connection interrupted, attempting to reconnect...
HTTP request timed out
9/16/2020, 9:59:44 AM	Upload of config.g successful after 1s
9/16/2020, 9:59:12 AM	G28
Error: Failed to enable endstops
9/16/2020, 9:59:02 AM	Connection established
9/16/2020, 9:59:02 AM	Connection interrupted, attempting to reconnect...
HTTP request timed out
9/16/2020, 9:58:49 AM	Upload of config.g successful after 1s
9/16/2020, 9:57:32 AM	G28
Error: Failed to enable endstops
9/16/2020, 9:56:58 AM	Connection established
9/16/2020, 9:56:58 AM	Connection interrupted, attempting to reconnect...
HTTP request timed out
9/16/2020, 9:56:18 AM	Upload of config.g successful after 1s
9/16/2020, 9:38:32 AM	Connected to 192.168.1.54

code_text

droftarts

@1d1 Does your config.g have M584 X0 Y1 Z4 E3 in it now? And you'll need to reset after changing this.

Is your homedelta.g unchanged from the one you posted earlier in the thread?
Please send M98 P"config.g" and post the response (this checks for errors in config.g).

Ian

1d1

@droftarts said in [No Axis Movement](/post/179087):
> M584 X0 Y1 Z4 E3

Yes it is

; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Sep 16 2020 09:55:20 GMT-0400 (Eastern Daylight Time)
G91                        ; relative positioning
G1 H1 X215 Y215 Z215 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

	M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Invalid Z probe type 4
Error: Invalid Z probe index
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C

droftarts

@1d1 Change

M558 P4 C"^zprobe.in" H5 F120 T6000            ; set Z probe type to switch and the dive height + speeds

to

M558 P5 C"^zprobe.in" H5 F120 T6000            ; set Z probe type to switch and the dive height + speeds

(Probe type 4 is not supported in RRF3, use either 5 or 8.)

Still not sure why it's not activating the endstops. What EXACTLY happens when you press HOME ALL? If the X and Y motors are moving (the Z may not be, but I think that's possibly a wiring issue), how far do they move? They should move 215mm up towards the endstops. If they don't move that far (which may be why the endstops are not being triggered and you get the error message) it's possible that your steps per mm on XY and Z are incorrect.

Ian

1d1

Well, until I can get some homing done, I haven't even configured or connected my z probe. Or done a PID tune for the hot end either.
What happens right now is that X and Y push the extruder up and out between the X and Y towers. Z doesn't move at all. I hit emergency stop. If the Z went up, it would center the movement. I'll check the Z connections.
Z motor works fine when driven from another driver (X) so the wiring is good. Right now, I think that the endstops not working despite clear triggering when manually pushed. They just don't stop the motors, and end up banging away at the endstop switches. I need to look at the board while this is happening to see if they are actually being hit.
Everything worked perfectly on the MKS Base board that the printer shipped with. However, I wanted the Duet as I use a direct drive extruder and Duets on my other two printers.
I go do some more checks and see if I get any farther.

Veti

@1d1 said in No Axis Movement:

Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C

i am confused
i dont think there is anything in the config.g you posted that would create this output.

did you post the correct output?

1d1

I found it.. finally.... and terribly embarrassing: X and W were reversed at the drivers. It is now homing perfectly. Now I'm going to work on the Z probe setup and will introduce a new topic if I can't get it right. For now, and to all of you who helped, Major Thanks!!! I was lost and have now been found...

1d1

Oh - and PID tune too. It will be fine ... or else.