Posts made by psyfor

@Phaedrux Thank you. I will give it a go now.

@Phaedrux

Axis limits X0.0:290.0, Y0.0:290.0, Z-0.2:280.0
Current reading 0, threshold 25, trigger height 2.490, offsets X2.0 Y42.0

Hi,
I am trying to get some mesh bed parameters set on my railcore. I want the the mesh to start at at X:290 and Y:5 with a spacing of 20 on the X and 70 on the Y. When I input the starting point for Y as 5 it will jump and start at 33.

How would I set the M557 parameter to get this result?

I recently updated to Firmware 3.0 and swapped by bed out on the railcore. Everything is working properly except for mesh bed compensation. I have running a 4 point leveling and mesh compensation. Bed is slightly tilted in one spot which used to be able to be corrected by enabling mesh bed compensation. I have redefined the heatmap and enabled compensation but it doesnt look like it is doing any compensation.

Any ideas as to what might be going on?

Ok let me try that first. Thank you.

Out of the blue I am getting bed thermistor faults due to open circuit. The temperature will read 2000 c intermittently. Nothing has changed on the printer and wiring looks good. Would this indicate that the thermistor itself is bad and needs to be changed?

All the sudden out of nowhere I am getting connection interruption issues with a code of 503. I am running web version 2.0.4 and firmware 2.05. Any thoughts as to why this might be happening?

I am noticing that my Z Offset is slightly high. Is it better to go through the BLTouch calibration again or make small adjustment to the Z Value in G31 directly in config?

I switched it and still having the same issue.

here is a pic

I am configuring my Duet2 Wifi with a BLTouch and am having some issues. I've looked at most of the guides and troubleshooting guides with no luck.

Probe will do a self test and pass. When I run either the deploy or retract gcode nothing happens. Probe also doesn't deploy when trying to home z. PWM is plugged into Duex PWM 1

Here is the config code I am using.

; Z probe and compensation definition
;*** If you have a switch instead of an IR probe, change P1 to P4 in the following M558 command
; IR PRobe - uncomment the following 2 lines if you have a and IR Probe, and comment out the BLTouch section below
;M558 P1 X0 Y0 Z1 ; Z probe is an IR probe and is not used for homing any axes
;G31 X0 Y30 Z2.00 P500 ; Set the zprobe height and threshold (put your own values here)

;BLTouch - comment out the following 3 lines if using a IR Probe
M307 H3 A-1 C-1 D-1
M558 P9 X0 Y0 Z1 H5 F50 T6000 A5 S0.02
G31 X2 Y42 Z2.65 P25 ; Customize your offsets appropriately - do a paper test, and put the probed value in the Z value here

Bed.g Code
M561 ; clear any existing bed transform
G1 Z5 S2
G30 P0 X15 Y45 Z-99999
G30 P1 X15 Y275 Z-99999
G30 P2 X275 Y150 Z-99999 S3
G1 X0 Y0 F5000 ; move the head to the corner (optional)

;old points
;G30 P0 X30 Y45 Z-99999 ; define 4 points in a clockwise direction around the bed, starting near (0,0)
;G30 P1 X30 Y215 Z-99999
;G30 P2 X225 Y215 Z-99999
;G30 P3 X225 Y45 Z-99999
;G30 P4 X125 Y125 Z-99999 S0 ; finally probe bed centre, and calculate compensation

Deploy Probe Using M280 P3 S10

Retract Probe Using M280 P3 S90

Perfect. I was able to downgrade to 2.05. Thank you so much for the support.

Tried that and when I send code M997 I receive the following.

Error: In-application programming binary "Duet2CombinedIAP.bin" not found

@dc42 Thank you. Since I am new to the board and building my first Railcore I think the best option would be to go down to firmware 2.05 for now. Let me try to get that going. To step down in firmware does anything special need to be done and can it be done through YAT?

@dc42 I have not and not sure if I know how.

Configuring my duet on a new build. Was able to get wifi connected and upgrade the firmware to 3.0. After Update I am getting the following. Anyone know how to fix?