Posts made by Phaedrux

Unfortunately that doesn't tell me much.

Can you try setting a range for T in your commands? T25:50 for instance.

Can you send M98 P"config.g" and M122 in the gcode console and share the results?

No problem at all.

; Home X-Axis 
G91                     ; relative positioning
G1 H2 X0             ; set axes position explicitly to Zero i.e move X and Y-axis Minimum Homing endstop and stop there
G1 H2 X40 F10000     ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X-40  F10000   ; go back a few mm
G1 H2 X0             ; move X and Y-axis Minimum Homing endstop and stop there (first pass)
G90                  ; absolute positioning

G1 H2 doesn't do what you think it does here.

G1 H2 X0 means to do a zero movement move regardless if the axis is homed or not. G1 H2 moves are meant to leat you move the axis away from an endstop slightly before a homing move, or to raise the z axis before making an X Y move to prevent scraping.

An actual homing move is done with a G1 H1 movement which needs to be long enough to strike the endstop even from the farthest opposing position. It also must be in the direction of the endstop.

@Stanislav said in PanelDue 7 loses macros after homing or moving rotary axes A/B:

Version of the firmware PanelDueFirmware-5.0i-7.0i.bin

If you look at the setup page on the PanelDue it should say the actual version.

Can you work through this and see how far you can get? Mainly what LEDs are illuminated on the board itself?

https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond

@fcwilt said in Mini 5+ Wifi Problem Revisited:

Any ideas why the older board WiFi works fine with firmware 3.5.4 while the newer board doesn't.

I have the same experience with my Duet 2 and wifi server 1.27. I lose connection constantly on anything beyond 1.27. I think it is likely my very old router that I use for the printer network.

@fcwilt said in Mini 5+ Wifi Problem Revisited:

Now that I managed to mess up the newer board so I cannot connect is there anyway to restore the firmware back to 3.4.6 from the USB connection?

You can flash the main firmware with Bossa. To reflash the wifi server you would need to put the desired version in the firmware folder and then send M991 S1 to flash it.

@thomasvanderwal said in Duet 2 v1.02 not responding:

@dc42 I upgraded to 3.5.4. I have adjusted the homedelta.g many times. This was my last.

; homedelta.g
; called to home all towers and extra axes
;
; generated by RepRapFirmware Configuration Tool v3.5.10 on Mon Feb 24 2025 14:22:27 GMT+0100 (Midden-Europese standaardtijd)

; home linear delta
G91 ; relative positioning
G1 H1 X650 Y650 Z650 F3000 ; move all towers to the high end stopping at the endstops
G1 H2 X-3 Y-3 Z-3 ; go down a few mm
G1 H1 X6 Y6 Z6 F250 ; move all towers to the high end once more stopping at the endstops
G1 Z-5 F2000
G90 ; absolute positioning
G1 X0 Y0 F2000 ; move X and Y to the centre

So what happens when you send G28 to home all axis? (which will run the homedelta.g macro)

; Configuration file for RepRapFirmware on Duet 2 WiFi
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.5.10 on Mon Feb 24 2025 14:22:26 GMT+0100 (Midden-Europese standaardtijd)

; General
G90 ; absolute coordinates
M83 ; relative extruder moves
M550 P"my printer" ; set hostname

; Accessories
M575 P1 S0 B57600 ; configure PanelDue support

; Network
M552 S1 ; configure WiFi adapter
M586 P0 S1 ; configure HTTP

; Smart Drivers
M569 P0 S1 D2 ; driver 0 goes forwards (X axis)
M569 P1 S1 D2 ; driver 1 goes forwards (Y axis)
M569 P2 S1 D2 ; driver 2 goes forwards (Z axis)
M569 P3 S1 D2 ; driver 3 goes forwards (extruder 0)

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

; Axes
M584 X0 Y1 Z2 ; set axis mapping
M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation
M906 X800 Y800 Z800 ; set axis driver currents
M92 X80 Y80 Z80 ; configure steps per mm
M566 X1200 Y1200 Z1200 ; set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z18000 ; set maximum speeds (mm/min)
M201 X1000 Y1000 Z1000 ; set accelerations (mm/s^2)

; Extruders
M584 E3 ; set extruder mapping
M350 E16 I1 ; configure microstepping with interpolation
M906 E1000 ; set extruder driver currents
M92 E663 ; configure steps per mm
M566 E1200 ; set maximum instantaneous speed changes (mm/min)
M203 E3600 ; set maximum speeds (mm/min)
M201 E1000 ; set accelerations (mm/s^2)

; Kinematics
M665 L230 R165 B100 H315 ; set delta radius, diagonal rod length, printable radius and homed height
M208 Z0 S1 ; set minimum Z
M666 X0 Y0 Z0 A0 B0 ; endstop adjustments and XY tilt, can be determined using auto calibration as well

; Probes
M558 K0 P1 C"zprobe.in" H5 F120 T6000 ; configure analog probe via slot #0
M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X0 Y0 Z0.7 ; set Z probe trigger value, offset and trigger height

; Endstops
M574 X2 P"xstop" S1 ; configure X axis endstop
M574 Y2 P"ystop" S1 ; configure Y axis endstop
M574 Z2 P"zstop" S1 ; configure Z axis endstop

; Sensors
M308 S0 P"bedtemp" Y"thermistor" A"Heated Bed" T100000 B4725 C7.06e-8 ; configure sensor #0
M308 S1 P"e0temp" Y"thermistor" A"Nozzle" T100000 B4725 C7.06e-8 ; configure sensor #1

; Heaters
M950 H0 C"bedheat" T0 ; create heater #0
M143 H0 P0 T0 C0 S140 A0 ; configure heater monitor #0 for heater #0
M307 H0 R2.43 D5.5 E1.35 K0.56 B1 ; configure model of heater #0
M950 H1 C"e0heat" T1 ; create heater #1
M143 H1 P0 T1 C0 S285 A0 ; configure heater monitor #0 for heater #1
M307 H1 R2.43 D5.5 E1.35 K0.56 B0 ; configure model of heater #1

; Heated beds
M140 P0 H0 ; configure heated bed #0

; Fans
M950 F0 C"fan0" ; create fan #0
M106 P0 S0 L0 X1 B0.1 ; configure fan #0
M950 F1 C"fan1" ; create fan #1
M106 P1 S0 B0.1 H1 T45 ; configure fan #1

; Tools
M563 P0 D0 H1 F0 ; create tool #0
M568 P0 R0 S0 ; set initial tool #0 active and standby temperatures to 0C

Maybe some more details about the project.

I'm kind of at a loss for your probe issue. It's confusing why M401 would work to deploy the pin manually but not during the homing move.

Have you tried manually positioning he probe at the center of the bed and then sending M401 and G30 to deploy and start probing?

The lite image does not have a desktop environment if that's what you're expecting?

There has been one report of probing speed not honoring the limit set by M203, so this may be related. Would be great if you could test on beta 4.

Could you verify in 3.6 beta 4?

You're getting no LED lights at all when only 24v is supplied?

Are you printing over USB connection to the Duet? You should be uploading the gcode file directly to the Duet to print it. No PC required after that.

firmware version?

@dc42 said in Smart Effector v4 z probe not lighting up:

@vmog23 thanks, as the SE was working before I think it must have been knocked off. The 3.3V power passes through L1 so that explains why the LED doesn't light up at all. Has the SE collided with anything?

Is L1 user replaceable?

Can you share your most up to date homing files?

Can you capture and share the exact error messages you get and exactly when?

Are you able to home X and Y independantly successfully?

Need to get that sorted first. If you want to pretend the axis are homed, you can move them manually to the correct location and then send G92 X0 Y0 to force the axis to be homed and at that position.

You can try adding M401 and M402 commands to deploy/retract the probe right before and after you send G30 in your homing files.

@Timothee-Leblond said in Z configuration for sensors:

I'm using a BTT not a BlTouch, and it is advised to use ^!io6. in apparently.

understood.

Can you show a photo of your probe wiring at the board?

When you send G30 manually, the Z axis moves, but the probe does not deploy? But M401/M402 do work?