No movement with any command

[zecreton]

@cosmowave yea

[shaunppl]

@zecreton How are the AXIS homed ?, you have no end stops wired to the motherboard unless you are using the override g-code command in the console, you need to show us the start-up DWC panel Dashboard after booting that verify and show all the end stops have been triggered and are homed properly, as before it will allow manual movement of the motors these have to be triggered. Without this its very difficult to ascertain what the problem is and how to help you further, Unless anyone else has an ideas.

[o_lampe]

@zecreton I see only one 4-lead cable on the 6XD, but there is no corresponding cable in the CL57 picture?
How are we supposed to troubleshoot this mess?
Please post better pictures and a link to the CL57t manual

PS: It's also a bad idea to use same colors for + and - power wires (the lila wires)

[zecreton]

@o_lampe the white cable on the cl57t picture is the 4-lead cable

[zecreton]

@o_lampe the wires are temporary bc i have to use wire that are like a couple of meters long for the real thing

[o_lampe]

You've bridged PUL+/DIR+/ENA+ on the driver side, but are they connected to 5V?

[droftarts]

@zecreton It looks like the wire that takes 5V from 'DIR+' to the 'PUL+' terminal is not connected:

Disconnect the enable pins, these kind of drivers are usually enabled by default. Get it working, then sort out enabling.

The green power LED on the driver should be on, it is not in the picture. Is the driver getting power?

Please post your config.g.

Ian

[zecreton]

@droftarts yes the driver is getting power, and i posted the config.g

[droftarts]

@zecreton said in No movement with any command:

i posted the config.g

Please post the whole config as text/code, not as a picture. You can copy it from DWC and paste it in your reply.

And is the 5V to PUL+ connected? And have you tried disconnecting the ENA wires?

Ian

[zecreton]

@droftarts idk why but i can't access dwc anymore even tho i haven't touched anything, i get this error: Error: M552: On-board firmware cannot process network-related commands when using an attached Single Board Computer␊

[zecreton]

@zecreton yes the PUL+ was connected

[Phaedrux]

@zecreton said in No movement with any command:

i get this error: Error: M552: On-board firmware cannot process network-related commands when using an attached Single Board Computer

Do you have a raspberry pi connected now?

[zecreton]

@Phaedrux no

[droftarts]

@zecreton You get this message when there's no SD card in the Duet, and it assumes that it is connected to a Raspberry Pi in SBC mode. I guess you're connected over USB? Send M122 to check if the SD card is recognised.

Check SD card and reading it: https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues

Ian

[zecreton]

@droftarts the sd card was not correctly in the slot idk why, but now im getting an ip adress of 0.0.0.0 and even with the ethernet cable disconnected, it says it is enabled

[Phaedrux]

Please copy and paste the text of your config.g into a post here.

[zecreton]

@Phaedrux i can't access dwc

[Phaedrux]

Remove the SD card from the Duet and use your computer to read the config.g file.

[zecreton]

@Phaedrux oops sorry i forgot that

[zecreton]

@Phaedrux ; Configuration file for RepRapFirmware on Duet 3 Main Board 6XD
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.5.3 on Tue Jun 25 2024 21:16:10 GMT-0400 (Eastern Daylight Time)

; General
G90 ; absolute coordinates
M83 ; relative extruder moves
M550 P"Duet 3" ; set hostname

; Network
M551 P"Raphaelbreton2008" ; set machine password
M552 P0.0.0.0 S1 ; configure Ethernet adapter
M586 P0 S1 ; configure HTTP

; Motor Idle Current Reduction
M906 I30 ; set motor current idle factor
M84 S30 ; set motor current idle timeout

; External Drivers
M569 P0.0 S1 R0 T5:5:10:0 ; driver 0.0 goes forwards and requires an active-low enable signal (X axis)
M569 P0.1 S1 R0 T5:5:10:0 ; driver 0.1 goes forwards and requires an active-low enable signal (Y axis)
M569 P0.2 S1 R0 T5:5:10:0 ; driver 0.2 goes forwards and requires an active-low enable signal (Z axis)

; Axes
M584 X0.0 Y0.1 Z0.2 ; set axis mapping
M350 X16 Y16 Z16 I0 ; configure microstepping without interpolation
M92 X80 Y80 Z400 ; configure steps per mm
M208 X0:1200 Y0:200 Z0:200 ; set minimum and maximum axis limits
M566 X900 Y900 Z12 ; set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180 ; set maximum speeds (mm/min)
M201 X500 Y500 Z20 ; set accelerations (mm/s^2)

; Kinematics
M669 K0 ; configure Cartesian kinematics

; Endstops
M574 X1 P"io0.in" S1 ; configure X axis endstop
M574 Y1 P"io1.in" S1 ; configure Y axis endstop
M574 Z1 P"io2.in" S1 ; configure Z axis endstop