No Axis Movement
-
Done. Nothing lost but nothing gained. Goes up on all axes, hits endstops and then bangs away until I hit Emergency Stop.
-
M115: FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-02-09b1
-
Alright, when you manually trigger the endstops do they register on the LED light on the Duet board?
What kind of endstops are they? Can you post a photo? How are they wired to the board? Does the status change if you send M119 before it's pressed compared to while it's depressed?
https://duet3d.dozuki.com/Wiki/Gcode#Section_M119_Get_Endstop_Status
-
@1d1 identify which motor is X, Y and Z (using G1 H2 X/Y/Z moves) then check that each endstop is connected on the correct axis (it sounds like you may have two swapped), and all are triggering. Despite moving Z to driver 4, the endstop should still be plugged into z endstop pins. Check triggering with
M117M119 or the endstop display in DWC.Ian
-
-
OK. Motors and endstops all correspond to their identified axes and are mounted in their proper spots. Each endstop light on the board is lit and goes off when manually triggered at the switch. The switches are just buttons pushing in and triggering when the carriage hits. Two wires, black and red, so, open or closed. Placing the Z connector back on the Z driver location gives a "no" when not triggered and" yes" when activated. They do not all trigger at once, only individually. They each behave properly when trying the M119 method as well as the machine properties read out in the UI.
-
The Z endstop should still be on the Z endstop connector even though the Z driver is now the E1 driver. RRF2 is pretty rigid about that.
At this point it's tempting to just upgrade you to RRF3.0 and then 3.1.1 and get a fresh config from the configurator for a delta and go from there.
Upload this zip: https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
Then upload this zip: https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip
Then get a config set from here and upload the resulting zip file as well: https://configtool.reprapfirmware.org/General
-
OK, back again... thanking you again. I downloaded in the order given and all uploads were successful. This is where we are now:
G28
Error: Failed to enable endstopsSo we're back to no movement but much closer, I think, as we know that all motors, drivers and endstops function. I still have the z endstop connected at the z position though the z motor is connected at P4.
-
@1d1 Check your firmware version with M115, and post response, and please also post your current config.g.
For forum ease-of-use, copy the text from DWC and paste it in your reply post. For extra points, format it as 'code', by highlighting the copied text and clicking </> in the formatting bar. Should looks something like:
My config.g here!If you do this with all pasted text (eg M122 responses) it makes it MUCH easier to troubleshoot, and will probably make it easier for other forum members to help.
Ian
-
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 Q5Delta Send code... Status Idle Mode: FFF Tool Position X 0.0 Y 0.0 Z 201.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.1 C Tools Extra Control All Tool Heater Current Active Standby Tool 0 T0 - Load Filament n/a n/a 0 0 Temperature Chart No Data System Directory 0:/sys/config.g ; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Sep 16 2020 09:55:19 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Q5" ; set printer name M665 R104.3 L215 B52 H210 ; Set delta radius, diagonal rod length, printable radius and homed height M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S0 ; physical drive 1 goes backwards 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 X80.00 Y80.00 Z80.00 E663.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 X800 Y800 Z800 E600 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 active-high endstop for high end on X via pin xstop M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop M574 Z2 S1 P"zstop" ; configure active-high endstop for high end on Z via pin zstop ; Z-Probe M558 P4 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height M557 R52 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 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S100 ; set temperature limit for heater 0 to 100C M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; 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 ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S1 H T45 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"fan1" Q500 ; 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" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S1 H1 T45 ; set fan 2 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 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 Remove a space Z0 ; -
Well, that didn't quite work right. I'll try again just get it the way it should be. Learning a lot here.... Q5Delta Send code... Status Idle Mode: FFF Tool Position X 0.0 Y 0.0 Z 201.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.1 C Tools Extra Control All Tool Heater Current Active Standby Tool 0 T0 - Load Filament n/a n/a 0 0 Temperature Chart No Data System Directory 0:/sys/config.g ; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Sep 16 2020 09:55:19 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Q5" ; set printer name M665 R104.3 L215 B52 H210 ; Set delta radius, diagonal rod length, printable radius and homed height M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S0 ; physical drive 1 goes backwards 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 X80.00 Y80.00 Z80.00 E663.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 X800 Y800 Z800 E600 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 active-high endstop for high end on X via pin xstop M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop M574 Z2 S1 P"zstop" ; configure active-high endstop for high end on Z via pin zstop ; Z-Probe M558 P4 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height M557 R52 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 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S100 ; set temperature limit for heater 0 to 100C M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; 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 ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S1 H T45 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"fan1" Q500 ; 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" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S1 H1 T45 ; set fan 2 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 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 Remove a space Z0 ; 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 -
@1d1 said in No Axis Movement:
though the z motor is connected at P4.
this is not reflected in your config
M584 X0 Y1 Z2 E3 ; set drive mapping
-
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.54code_text
-
@1d1 Does your config.g have
M584 X0 Y1 Z4 E3in 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 sendM98 P"config.g"and post the response (this checks for errors in config.g).Ian
-
@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 -
@1d1 Change
M558 P4 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speedsto
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
-
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. -
@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?
-
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...
-
Oh - and PID tune too. It will be fine ... or else.
