A few questions regarding switching to Duet
-
@siblues can you post your current config.g and homing files? Also the deployprobe and retractprobe files.
What firm ware version are you using?
I can take a look and see if anything else needs changing.
There are 5 wires for the BLTouch. They need to go to the right place and the wires and crimps need to be working obviously. Wiring ends up being the culprit often. A multimeter to check continuity is helpful.
-
@siblues said in A few questions regarding switching to Duet:
I am Following the documentation to set up my machine and Duet but when using a BlTouch is it recommended to not use a Zmin endstop? I am asking because I have both wired up at the moment and I figured I would ask if it is common practice to eliminate the Zmin endstop when using the BlTouch sensor?
It's entirely up to you whether you home Z using the Z probe or using an endstop switch. Set up the homing files according to your choice. See https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_Z.
Having the option to home to Z max can be useful if you want to be able to resume a print after a power failure.
-
I have the BlTouch wired up how it is pictured here
firmware version
2.0(RTOS) (2018-06-05b3)
config.g
; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Tue Oct 30 2018 20:32:38 GMT-0400 (Eastern Daylight Time); General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves; Network
M550 PTony's P3 Steel ; Set machine name
M551 ; Set password
M552 S1 ; Enable network
;*** Access point is configured manually via M587
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z400 E420 ; Set steps per mm
M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180 E1200 ; Set maximum speeds (mm/min)
M201 X500 Y20 Z250 E250 ; Set accelerations (mm/s^2)
M906 X1200 Y1200 Z1200 E1200 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X220 Y220 Z200 S0 ; Set axis maxima; Endstops
M574 Y1 Z1 S0 ; Set active low endstops
M574 X1 S1 ; Set active high endstops; Z-Probe
M307 H8 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds
G31 P25 X0 Y0 Z5 ; Set Z probe trigger value, offset and trigger height
M557 X15:205 Y15:205 S20 ; Define mesh grid; Heaters
M307 H0 B0 S1.00 ; Disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S290 ; Set temperature limit for heater 1 to 290C; Fans
M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H0:1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H0:1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on; Tools
M563 P0 D0 H1 ; 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; Automatic saving after power loss is not enabled
; Custom settings are not configured
deploy probe
; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool on Tue Oct 30 2018 20:32:38 GMT-0400 (Eastern Daylight Time)
M280 P7 S10 I1retract probe
; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool on Tue Oct 30 2018 20:32:38 GMT-0400 (Eastern Daylight Time)
M280 P7 S90 I1home all
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Tue Oct 30 2018 20:32:38 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 X-225 Y-225 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 X5 Y5 F6000 ; go back a few mm
G1 S1 X-225 Y-225 F360 ; move slowly to X and Y axis endstops once more (second pass)
G1 S1 Z-205 F1800 ; move Z down stopping at the endstop
G90 ; absolute positioning
G92 Z0 ; set Z to axis minimum (you may want to adjust this); Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 S2 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioningHome x
; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool on Tue Oct 30 2018 20:32:38 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 X-225 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000 ; go back a few mm
G1 S1 X-225 F360 ; move slowly to X axis endstop once more (second pass)
G1 Z-5 F6000 S2 ; lower Z again
G90 ; absolute positioninghome y
; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool on Tue Oct 30 2018 20:32:38 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 Y-225 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y5 F6000 ; go back a few mm
G1 S1 Y-225 F360 ; move slowly to Y axis endstop once more (second pass)
G1 Z-5 F6000 S2 ; lower Z again
G90 ; absolute positioninghome z
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Tue Oct 30 2018 20:32:38 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 Z-205 F1800 ; move Z down until the endstop is triggered
G92 Z0 ; set Z position to axis minimum (you may want to adjust this); Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 S2 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
If you're wired up the way its shown in that diagram you've got the wrong heater pin unbound. You've got 8 instead of 7 in M307.
Heater pin 3 is also commonly used. Either way, check your config-override.g to see if there is a heater binding being applied after you've removed it.
-
You'll also have to modify your homeall and home z files to use G30 instead of G1 S1 Z-200
-
Thanks for all the help so far Phaedrux
I have no idea where the config-override.g file is.I checked in the settings / system editor where all of the other folders are but it isn't there.
I would like to ask if I am using G30 to replace the entire line G1 S1 Z-200 or just replacing the G1 line with G30 S1 Z-200.
I am guessing the way I am setting it up now with your guidance is to use both the Zmin endstop and BlTouch?
-
@siblues You may not have one. It'll only be created if you've used M500 to save a parameter. Similar to how older firmwares use EEprom saving. M501 is used in config.g to load it.
G30 will replace the entire G1 line. It tells the firmware to find z min with the probe.
-
Phaedrux after I changed things around how you pointed out how do I go about checking to see if the probe is actually working as it should?
I tried
M280 P7 S10 I1
M280 P7 S90 I1The BlTouch is going through the self test at startup and then gives a constant on led.
-
What happens when you send those command? Does the pin deploy and retract?
-
No it doesn't move I even tried both codes without the l1 just to check.
-
I hope I didn't destroy this board but it was working fine and after adjusting a few things in the config now the only thing I can get the board to do is heat the bed.I get this error message whenever I try to move any of the axis
M120
G91
G1X-1 F6000
M121G0/G1 insufficient axes homes
error pop -
Add a S2 to the end of the G1 gcode line. You can't move an axis before homing.
-
Please excuse my very limited know how on the subject but what I posted was the error message that popped up where would I need to add that S2?What folder because I looked and I don't see that anywhere?
-
@siblues change the G1 line to G1 S2 X-1 F6000 or put a M564 H0 in config.g
https://duet3d.dozuki.com/Wiki/Gcode#Section_G0_G1_Move
Scroll down to the G0/G1 S and H parameter table.https://duet3d.dozuki.com/Wiki/Gcode#Section_M564_Limit_axes
-
@stephen6309 thanks for helping out I really appreciate it.I think adding M564 H0 would be best or simpler for me but where in the config.g should I add that line?
-
@siblues It can go anywhere you like. Maybe add it near your axis minima and maxima to keep it together.
-
@phaedrux Ok thanks I have almost everything ironed out but the BlTouch whenever I try to home the z axis it tells me that the probe is already triggered at start and states a
G28 ZThe BlTouch shows a reading of 1000 on the DWC.I figured I would mention that just in case that information is relevant to helping me solve my issues.
-
Does that mean you have the BLTouch responding to deploy and retract commands now?
Probe triggered at start of move may mean your white wire isn't connected properly. Check the crimps.
-
Ok so let me ask a few questions first if the wire isn't connected or the crimp on the terminal is bad after issuing the probe commands would the dwc give an error message?I have tried a few of the commands for the BlTouch and they all seem to be accepted by the Duet and show up as green commands in the g-code console.The probe goes through the self test and the led is constantly on and the DWC reads 1000 for the probe.I mentioned that when I home the Z axis I get the triggered from start error for the probe.I can post the files again if you need them.
-
@siblues sure post your files again as they are now.
I don't think there is a specific error message if something isn't connected right other than maybe the error you're getting now since it thinks the probe is already trigger before you've actually probed.
It's still not clear if the probe is responding to the deploy and retract commands. What happens if you send M401 and M402? Does the pin deploy/retract?
Try adding the servo commands to clear errors and retract the probe pin to the start of your homeall and homez.
