I can not move the stepper
-
@T3P3Tony Hi tony yes that did the trick, thanks.
Another question I got 4 independent z Axis, could you check if its right in the config.I got connected in the duet 3 6 XD
Driver 0 - X
Driver 1 - Y
Driver 2 - Z1
Driver 3 - Z2
Driver 4 - Z3
Driver 5 - Z4And the extruder in the expansion Board with the Can Address 122
Best
Alvaro -
@Makergal3D that's how the config file is setup.
-
@T3P3Tony Should I config anything else for that, because Z is not moving at all, XY moves correctly
-
@Makergal3D said in I can not move the stepper:
M574 Z1 S1 P"io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin io2.in
it would be normal to have one endstop per z axis motor so the individual axes can be trammed to the overall Z axis however AFAIK thats not mandatory.
what happens when you send M98 P"0:sys/config.g"
-
The drivers in Z has breakes, because the ammount of weight of the gantry, I read in the manual that I need a relay to open the break, but could I connect the break to an output in the board??
Best
Alvaro -
@T3P3Tony said in I can not move the stepper:
M98 P"0
I was thinking in using a probe to detect the bed, so I don't need extra endstops.
When I type M98 P0, the control panel said this "M98 P0 Warning: Macro file 0 not found"
-
@T3P3Tony said in I can not move the stepper:
M98 P"0:sys/config.g"
you need to have the "", what this command is doing is running the config file again to see if there are errors in it that i did not notice - those will be shown in the console on DWC
I did not realise the drivers had brakes, you need to setup the brake control. You can control the brakes from the board
https://docs.duet3d.com/User_manual/Reference/Gcodes#m5697-configure-motor-brake-port
-
This post is deleted! -
Hi @T3P3Tony to last questions I think i'm almost ready to test.
Just 2 question. with the M98 is gives me back this.
M98 P"0:sys/config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Setting not available for external driversWhen I start up the machine it said this all the times I power UP
Warning: Discarded std reply src=122 RID=3 exp=4 "Setting not available for external drivers"
Ans last, how do I select PIN from the 1XD board, I gor 4 heaters in my assembly and I would like to control 1 heater from the 1XD board. But I can not find in the forum how to set it up. The heater is in the Out 0 of the 1XD, it will control an SSR
Thanks in advance
-
@Makergal3D said in I can not move the stepper:
Warning: Discarded std reply src=122 RID=3 exp=4 "Setting not available for external drivers"
I expect this error is caused by trying to set the stepper drive current for the external drivers in the M906 line:
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per centRemove X, Y and Z parameters.
Ans last, how do I select PIN from the 1XD board, I gor 4 heaters in my assembly and I would like to control 1 heater from the 1XD board. But I can not find in the forum how to set it up. The heater is in the Out 0 of the 1XD, it will control an SSR
It is not ideal to run a heater from the 1XD. One of the limitations of RRF is that any heater has to be connected to the same board as the temperature sensor that controls it. While the 1XD does have a thermistor input, it is lower resolution than the temperature inputs on other Duet boards. It was originally intended for monitoring the temperature of connected motors. However, if it is enough for your application, yes, you should be able to control the heater. Note that the OUT0 and OUT1 are limited to 2A, and are driven at the input voltage (up to 48V) so if using an SSR, check the voltage limits. If it works with 3.3V signalling, you can use an io.out pin to control it.
Ian
-
@droftarts So I should move the thermistor also to the 1XD boards.
But I got the same question how do I say here that the pin is in the 1XD board
I supoose that in with the M950 but what number should I use for defining the pin in the 1XD board??; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp3
M950 H0 C"out0" T0 ; create bed heater output on out3 and map it to sensor 0
M307 H0 B0 S1.00 ; disable 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 100C4Thanks
-
@Makergal3D prefix the pin name with the CAN address, eg
M308 S0 P"122.temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp3See https://docs.duet3d.com/en/User_manual/Machine_configuration/CAN_connection#using-can-addresses
Ian
-
@droftarts Yes you mean putting in this line the 122 address I suppose
M950 H0 C"122.out0" T0
-
I got another question. I got my extruder in the 1XD board, I change the can Address to 40, I can comunicate correctly with the board. But I'm not shure if I configure correctly the extruder.
Should I select in anyway that in the tool section in config, that my driver is in the can Address 40¿¿
But If I try to move the extruder from the DWC, i configure a filament to be able to extrude, but if a click in retract, or in extrude, it doesn't do anything. No movement at all.
Extruder is a 240 degrees so it should not be related with the minimum extrusion temperature.
Thanks
; Configuration file for Duet 3 MB 6XD (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.16 on Fri Aug 11 2023 20:50:08 GMT+0200 (hora de verano de Europa central); General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"GM200" ; set printer name; Wait a moment for the CAN expansion boards to start
G4 S2; Network
M551 P"Makergal" ; set password
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.0 T1:1:2:0
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.1 T1:1:2:0
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.2 T1:1:2:0
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M569 P0.3 T1:1:2:0
M569 P0.4 S1 ; physical drive 0.4 goes forwards
M569 P0.4 T1:1:2:0
M569 P0.5 S1 ; physical drive 0.5 goes forwards
M569 P0.5 T1:1:2:0
M569 P40.0 S1 R1 ; physical drive 121.0 goes forwards
M569 P40.0 T1:1:2:0
M584 X0.0 Y0.1 Z0.5:0.4:0.3:0.2 E40.0 ; set drive mapping
M671 X50:50:1100:1100 Y250:1850:1850:250 S0.5 ; leadscrews at rear left, front middle and rear right
M92 X16.00 Y16.00 Z320.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00 Z30.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X3000.00 Y3000.00 Z200.00 E1200.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z5.00 E250.00 ; set accelerations (mm/s^2)
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X1200 Y2000 Z995 S0 ; set axis maxima; Endstops
M574 X1 S1 P"io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io0.in
M574 Y1 S1 P"io0.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io1.in
M574 Z1 S1 P"io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin io2.in; Z-Probe
M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M557 X15:215 Y15:195 S20 ; define mesh grid; Heaters
M308 S0 P"40.temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin 121.temp0
M950 H0 C"40.out0" T0 ; create bed heater output on out3 and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang 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"spi.cs1" Y"rtd-max31865" ; configure sensor 1 as PT1000 on pin temp0
M950 H1 C"out0" T1 ; create nozzle heater output on out0 and map it to sensor 1
M307 H1 R0.952 K0.203:0.000 D38.46 E1.35 S1.00 B0 V24.3 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M308 S2 P"spi.cs2" Y"rtd-max31865" ; configure sensor 2 as PT1000 on pin temp1
M950 H2 C"out1" T2 ; create nozzle heater output on out1 and map it to sensor 2
M307 H2 R0.747 K0.166:0.000 D26.47 E1.35 S1.00 B0 V24.3 ; disable bang-bang mode for heater and set PWM limit
M143 H2 S280 ; set temperature limit for heater 2 to 280C
M308 S3 P"spi.cs3" Y"rtd-max31865" ; configure sensor 3 as PT1000 on pin temp2
M950 H3 C"out2" T3 ; create nozzle heater output on out2 and map it to sensor 3
M307 H3 R0.972 K0.189:0.000 D19.35 E1.35 S1.00 B0 V24.3 ; disable bang-bang mode for heater and set PWM limit
M143 H3 S280 ; set temperature limit for heater 3 to 280C; Fans
M950 F0 C"out4" Q500 ; create fan 0 on pin out4 and set its frequency
M106 P0 S0 H1:2:3:0 T45 ; set fan 0 value. Thermostatic control is turned on; Tools
M563 P0 S"PULSAR" D0 H1:2:3 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
M302 S120 R110; Custom settings are not defined
-
I try to use G91 and then G1 H2 X10 but not movement at all. Even if I use G92 X0 Y0 Z0 I can press the movement button in the dashboard, the numbers change in the status area, but the machine is not moving at all.
-
This post is deleted! -
@charlie323a Use M564 H0, that should allow you to move without homing. without homing you can move the axis, that command allows you to move without it, but be carefull
-
Hi i'm comming back this issue agian.
Because I'm having troubles, everything works unless the extruder driver.
I have an 6XD board and a 1XD, the extruder is in the 1XD, but I'm not able to move it.this is my config.g
; Configuration file for Duet 3 MB 6XD (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.4.1 on Tue Jun 04 2024 19:55:09 GMT+0200 (hora de verano de Europa central) ; General preferences M575 P1 S1 B57600 ; enable support for PanelDue G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Printer" ; set printer name ; Wait a moment for the CAN expansion boards to start G4 S2 ; Network M551 P"Soon2020" ; set password M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.0 T1:1:2:0 M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.1 T1:1:2:0 M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.2 T1:1:2:0 M569 P0.3 S1 ; physical drive 0.3 goes forwards M569 P0.3 T1:1:2:0 M569 P0.4 S1 ; physical drive 0.4 goes forwards M569 P0.4 T1:1:2:0 M569 P0.5 S1 ; physical drive 0.5 goes forwards M569 P0.5 T1:1:2:0 M569 P45.0 S0 R0 ; physical drive 121.0 goes forwardsM569 M569 P45.0 T5:5:10:10 M350 X16 Y16 Z16 E16 I1 M584 X0.0 Y0.1 Z0.5:0.4:0.3:0.2 E45.0 ; set drive mapping M671 X60:60:1160:1160 Y174:1069:1069:174 S5 ; leadscrews at rear left, front middle and rear right M92 X64.00 Y64.00 Z160.00 E225.00 ; set steps per mm M566 X3000.00 Y3000.00 Z600.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X5000.00 Y5000.00 Z1200.00 E1200.00 ; set maximum speeds (mm/min) M201 X1000.00 Y1000.00 Z5.00 E250.00 ; set accelerations (mm/s^2) M84 S30 ; Set idle timeout ; Axis Limits M208 X-8:1060 Y-43:1200 Z0:1027 S1 ; set axis minima ; Endstops M574 X1 S1 P"io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io0.in M574 Y1 S1 P"io3.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io1.in M574 Z1 S2 ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin io2.in ; Z-Probe M558 P1 C"^io4.in" B1 H5 F600:60 T6000 ; set Z probe type to switch and the dive height + speeds G31 P500 X-40 Y0 Z1 ; set Z probe trigger value, offset and trigger height M557 X100:1050 Y100:1050 S200 ; define mesh grid ; Heaters M308 S0 P"45.temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin 121.temp0 M950 H0 C"45.out0" T0 ; create bed heater output on out3 and map it to sensor 0 M307 H0 R0.383 K1.328:0.000 D14.73 E1.35 S1.00 B0 ; disable bang-bang mode for the bed heater and set PWM limit M570 H0 P10 T15 M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"spi.cs1" Y"rtd-max31865" ; configure sensor 1 as PT1000 on pin temp0 M950 H1 C"out0" T1 ; create nozzle heater output on out0 and map it to sensor 1 M307 H1 R0.876 K0.099:0.000 D36.88 E1.35 S1.00 B0 V24.3 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C M308 S2 P"spi.cs2" Y"rtd-max31865" ; configure sensor 2 as PT1000 on pin temp1 M950 H2 C"out1" T2 ; create nozzle heater output on out1 and map it to sensor 2 M307 H2 R0.747 K0.166:0.000 D26.47 E1.35 S1.00 B0 V24.3 ; disable bang-bang mode for heater and set PWM limit M143 H2 S280 ; set temperature limit for heater 2 to 280C M308 S3 P"spi.cs3" Y"rtd-max31865" ; configure sensor 3 as PT1000 on pin temp2 M950 H3 C"out2" T3 ; create nozzle heater output on out2 and map it to sensor 3 M307 H3 R0.972 K0.189:0.000 D19.35 E1.35 S1.00 B0 V24.3 ; disable bang-bang mode for heater and set PWM limit M143 H3 S280 ; set temperature limit for heater 3 to 280C ; Fans M950 F0 C"out4" Q500 ; create fan 0 on pin out4 and set its frequency M106 P0 S0 H1:2:3:0 T45 ; set fan 0 value. Thermostatic control is turned on ; Tools M563 P0 S"PULSAR" D0 H1:2:3 F0 T0 ; 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 M302 P1 ; Custom settings are not definedMy 122
m122 === Diagnostics === RepRapFirmware for Duet 3 MB6XD version 3.5.1 (2024-04-19 14:39:48) running on Duet 3 MB6XD v1.01 or later (standalone mode) Board ID: 0JD2M-999AL-D25SW-6JTDD-3S06Q-T4ZB1 Used output buffers: 1 of 40 (19 max) Error in macro line 37 while starting up: in file macro line 37 column 20: M350: array too long, max length = 0 === RTOS === Static ram: 153624 Dynamic ram: 120392 of which 16 recycled Never used RAM 69032, free system stack 192 words Tasks: NETWORK(1,ready,32.8%,183) ETHERNET(5,nWait 7,0.1%,317) HEAT(3,nWait 6,0.1%,323) Move(4,nWait 6,0.0%,211) CanReceiv(6,nWait 1,0.0%,797) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,351) MAIN(1,running,67.0%,444) IDLE(0,ready,0.0%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:17:28 ago, cause: software Last software reset at 2024-06-09 13:57, reason: User, Gcodes spinning, available RAM 69600, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU temperature: min 28.7, current 30.4, max 30.5 Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0 Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/80/0, gc cycles 0 Events: 2 queued, 2 completed Driver 0: ok Driver 1: ok Driver 2: ok Driver 3: ok Driver 4: ok Driver 5: ok Date/time: 2024-06-09 14:15:25 Slowest loop: 38.55ms; fastest: 0.07ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 8.9ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 3, maxWait 122441ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 7, completed 7, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 7], CDDA state -1 === DDARing 1 === 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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Movement locks held by null, 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 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000000 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 9457, received 16788, lost 0, errs 1, boc 0 Longest wait 2ms for reply type 6053, peak Tx sync delay 322, free buffers 50 (min 49), ts 5244/5243/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 8.23ms; fastest: 0.03ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 = Ethernet = Interface state: active Error counts: 0 0 0 0 0 0 Socket states: 5 5 2 2 2 0 0 0 === Multicast handler === Responder is inactive, messages received 0, responses 0M122 B45
Diagnostics for board 45: Duet EXP1XD firmware version 3.5.1 (2024-04-19 14:42:58) Bootloader ID: SAMC21 bootloader version 2.8 (2023-07-25) All averaging filters OK Never used RAM 6016, free system stack 136 words Tasks: Move(3,nWait 7,0.0%,135) HEAT(2,nWait 6,0.2%,129) CanAsync(5,nWait 4,0.0%,55) CanRecv(3,nWait 1,0.0%,71) CanClock(5,nWait 1,0.0%,59) MAIN(1,running,78.1%,433) IDLE(0,ready,0.0%,40) AIN(2,nWait 2,21.6%,112), total 100.0% Owned mutexes: Last reset 00:01:11 ago, cause: power up Last software reset data not available Driver 0: pos 0, 225.0 steps/mm, steps req 0 done 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxLate 0 maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00 Peak sync jitter 1/5, peak Rx sync delay 208, resyncs 0/0, no timer interrupt scheduled VIN voltage: min 24.2, current 24.2, max 24.2 MCU temperature: min 24.3C, current 24.6C, max 24.8C Last sensors broadcast 0x00000001 found 1 162 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 1145, send timeouts 0, received 648, lost 0, errs 0, boc 0, free buffers 18, min 18, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0We use 2 diferrent drivers but we had the same problem with both, right now we are using a DM556T form stepperonline.
https://www.omc-stepperonline.com/download/DM556T_V4.0.pdf
If we connect the stepper motor to other driver, that is connected to the main board, it works, but in a driver connected to the expasion board I can not make it work.We check all of this
Both boards has the same firmware version.
There is can comunication.
The wires are properly connected ( we try both +signals, and -signals just in case)
We try in M569, diferents timmings.
T2.5:2.5:5.0
T5:5:10:10
even T4:4:4:4If we send M569 P45.0
Driver 45.0 runs in reverse, active low enable, step timing 5.0:5.7:10.7:11.0us
it gives this back with the T in 5:5:10:10We dont have the enable pin connected.
I'm dont know what else to look for, or to change.
We even create a new config file but I can not make it work.I hope you can help me
Best Alvaro -
@Makergal3D Can you send M98 P"config.g" and report the result?
-
@Makergal3D The 6XD and 1XD have different wiring schemes, and have different ways of enabling the drive. Please post a picture showing how the drive is wired at both ends.
Ian
