hbot homes correctly but prints mirrored ,
-
got it !!!
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Sun Aug 30 2020 09:00:14 GMT-0600 (Mountain Daylight Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Duet2" ; set printer name
M669 K1 ; select CoreXY mode; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P5 S1 T5 R1 ; physical drive x goes forwards
M569 P6 S1 T5 R1 ; physical drive y goes forwards
M569 P7 S1 T5 R1 ; physical drive z goes forwards
M569 P8 S1 T5 R1 ; physical drive U goes forwards
M569 P3 S1 ; physical drive extruder goes forwards
M584 X6 Y5 Z7:8 E3 ; set drive mapping
M671 X-50:490 Y330:330 S5 ; x leadscrew position left to right from o,o on y axis , S5 means can adjust up to 5 mm
M350 X16 Y16 Z16 E16 I1 ; configure micro stepping with interpolation
M92 X200.00 Y200.00 Z800.00 E138.23 ; set steps per mm
M566 X200.00 Y200.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X25000.00 Y25000.00 Z1000.00 E2400.00 ; set maximum speeds (mm/min)
M201 X400.00 Y400.00 Z20.00 E400.00 ; set accelerations (mm/s^2)
M906 X300 Y300 Z300 E800 I30 ; set motor currents (mA)
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X440 Y535 Z900 S0 ; set axis maxima; Endstops
M574 X1 S1 P"!xstop" ; configure active-low endstop for high end on X via pin xstop
M574 Y2 S1 P"!ystop" ; configure active-low endstop for high end on Y via pin ystop
M574 Z1 S1 P"!zstop+!e0stop" ; configure active-high endstops for low end on Z via pins zstop and e0stop; Z-Probe
;M950 S0 C"exp.heater7" ; create servo pin 0 for BLTouch
M950 S0 C"!exp.heater7" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T24000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y0 Z0.445 ; set Z probe trigger value, offset and trigger height
M557 X70:400 Y180:500 S100 ; 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 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"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 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
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; Tools
M563 P0 S"swiss" 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
; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss -
@tracar said in hbot homes correctly but prints mirrored ,:
G31 P500 X0 Y0 Z0.445 ; set Z probe trigger value, offset and trigger height
Don't forget to set your XY offsets for the BLtouch. As it is now, it thinks the BLtouch is exactly where the nozzle is.
-
@Phaedrux
i have not set that yet, but i will after the printer is rebuilt Squared and finalized .and again Thankyou for your patience and help on this !!!!
-
No problem.
-
@Phaedrux
are you aware of anywhere i can download differnt macro files for differnt things, fully auto scripts, manual stuff.... dont care what they are, just want to find, learn, modify , try things out see what i can do with this printer. if you have any stuff you can pass on to me , please send me a file with a side of everything
-
You can take a look at mine if you like.
https://www.dropbox.com/s/td86jdrztubq2dg/macros.zip?dl=0
https://www.dropbox.com/s/k25fuhdrr7c3miy/Config V22.zip?dl=0
-
@Phaedruxnice, Thanks this gives me hours of hair pulling fun
-
after upgrading to 3xx this wont save its probe data
what needs to be changed?; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Sun Aug 02 2020 19:54:07; BLTOUCH PREP
;
M400
G4 S1
M280 P0 S160 I1 ; Alarm Release and Push-Pin UP just in case it's in alarm and deployed
G4 S1
M402 ; Retract probe just in case it's down
M400
M561 ; clear all bed compensation
G28 ; home all axis
G90 ; absolute positioning
G1 X220 Y330 Z10 ; move probe to center of the bed
G30 ; set Z0 position with the probe
;G1 Z25 ; return to 25mm height
G30 P0 X440 Y330 Z-99999 ; probe near a leadscrew, half way along Y axis
G30 P1 X0 Y330 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
G1 X220 Y330 Z25 ; move probe to center of the bed
M500 P31; save results
M501 ; load new data
G30 ; set Z0 position with the probe
M280 P7 S90
M402 ; retract probe -
@tracar said in hbot homes correctly but prints mirrored ,:
M280 P7 S90
If you're on RRF3 P7 should be P0
@tracar said in hbot homes correctly but prints mirrored ,:
M500 P31; save results
Does it work if you put a space between the P31 and the ; ?
The only issues I am aware of with M500 is that it's currently not supported with the Duet 3 when used with a Pi.
Do you get any error messages if you send M500 by itself?
If you delete your config-override.g and send M500 does it get created?'
Actually, looking again, it doesn't look like you're using G30 S-3 to measure the probe offset with this macro, so M500 P31 isn't going to do anything here. What are you expecting it to save?
-
@Phaedrux
i moved the m500 and m501 below the line under the 501, seens to work and generate the correct offset and save it in a newly created config override file correctly......as i deleted to test with m32
verified by homing z, droping the table and baby stepping up till the probe is triggered. the z axis ,matches what was automatically storedno error message when send m500.
; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Sun Aug 02 2020 19:54:07; BLTOUCH PREP
;
M400
G4 S1
M280 P0 S160 I1 ; Alarm Release and Push-Pin UP just in case it's in alarm and deployed
G4 S1
M402 ; Retract probe just in case it's down
M400
M561 ; clear all bed compensation
G28 ; home all axis
G90 ; absolute positioning
G1 X220 Y330 Z10 ; move probe to center of the bed
G30 ; set Z0 position with the probe
G30 P0 X440 Y330 Z-99999 ; probe near a leadscrew, half way along Y axis
G30 P1 X0 Y330 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
G1 X220 Y330 Z25 ; move probe to center of the bed
M500 P31; save results
M501 ; load new data
G30 ; set Z0 position with the probe
M280 P0 S90
M402 ; retract probe
G28 ; home all axis -
@tracar said in hbot homes correctly but prints mirrored ,:
i moved the m500 and m501 below the line under the 501, seens to work and generate the correct offset and save it in a newly created config override file
Since you haven't changed it with a G30 S-1 it's just saving the same value as before. There is no reason in this macro to have M500 or M501
-
This post is deleted! -
@Phaedrux
; bed.g
; called to perform automatic bed compensation via G32
;
M400 ; Finishes all current moves and clears the buffer
G4 S1 ; wait 1 second
M280 P0 S160 I1 ; Alarm Release and Push-Pin UP
G4 S1 ; wait 1 second
M402 ; Retract probe just in case it's down
M400 ; Finishes all current moves and clears the buffer
M561 ; clear all bed compensation
G28 ; home all axis
G90 ; absolute positioning
G1 X220 Y330 F8000 Z10 F800 ; move probe to center of the bed
G30 S-1 ; set Z0 position with the probe
G30 P0 X440 Y330 Z-99999 ; probe near a leadscrew, half way along Y axis
G30 P1 X0 Y330 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
G1 X220 Y330 F8000 Z10 F800 ; move probe to center of the bed
G30 S-1 ; set Z0 position with the probe
M402 ; retract probewhat im trying to do is have this auto level the bed. and figure out how to keep this new probed info after another homez or homeall is called, say like starting a print.
-
@tracar said in hbot homes correctly but prints mirrored ,:
figure out how to keep this new probed info after another homez or homeall is called, say like starting a print.
Well it will stay in effect until the motors are de-energized. It should stay leveled through a G28 unless you're changing the position of individual motors in your homeall.
G30 S-1 ; set Z0 position with the probe M402 ; retract probeDon't do that. The G30 S-1 is only for determining your trigger height. You don't need or want to do that after you've done the tilt correction. Just do a single G30 at the center of the bed to redefine the Z0 position because the tilt correction will change it slightly. Trigonometry and all that.
If your G28/homeall homes the Z axis, you don't need to do that again at the start of the leveling points. Just after.
; bed.g
; called to perform automatic bed compensation via G32
;
M400 ; Finishes all current moves and clears the buffer
G4 S1 ; wait 1 second
M280 P0 S160 I1 ; Alarm Release and Push-Pin UP
G4 S1 ; wait 1 second
M402 ; Retract probe just in case it's down
M400 ; Finishes all current moves and clears the buffer
M561 ; clear all bed compensation
G28 ; home all axis
G90 ; absolute positioning
G30 P0 X440 Y330 Z-99999 ; probe near a leadscrew, half way along Y axis
G30 P1 X0 Y330 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
G1 X220 Y330 F8000 Z10 F800 ; move probe to center of the bed
G30 ; set Z0 position with the probe
M402 ; retract probeAlso keep in mind that the tilt correction for the bed is only in one axis. It can't correct for tilt along Y. You might also need to run the G32 a couple times to get the tilt completely corrected, and depending on the repeatability of the probe you might end up bouncing around in the noise. So try and get it leveled up as best as you can manually to begin with.
After it's all leveled you may want to run a G29 to get a heightmap of the bed surface itself to see how it looks.
-
@Phaedrux said in hbot homes correctly but prints mirrored ,:
to get a heightmap of the bed surface itself to s
flawless !!!
you rock.
