BLtouch 3.1 on Duet 2 WiFi 1.05 does not work
-
Hi
First the information about hardware and software - and thanks in advance for your help
Duet 2 WiFi V1.05
BLtouch V3.1
Duet Web control 3.3.0
Repair firmware for duet 2 wifi/Ethernet 3.3 ( 2021-06-15)Wiring as shown in the picture, checked with a multimeter and OK
When the printer is switched on, the BLtouch runs a self-test, which runs very slowly.
The individual homing of X and Y runs normally, when you start Z homing, the following error message appears.
G28 Z
Error: in file macro line 9: G30: Z probe 0 not found
Error: G0/G1: insufficient axes homedHere our config.g
; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jan 22 2022 15:09:21 GMT+0100 (Mitteleuropäische Normalzeit)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"HEVO-RS Dave" ; 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 P0 S0 ; physical drive 0 goes backwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z800.00 E409.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z600.00 E1200.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z15.00 E250.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1300 E800 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 X300 Y300 Z300 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"^xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"!ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z
; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H12 R1.0 F500:F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X20:280 Y40:300 S50 ; 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 B1 S1.00 ; enable 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 100C
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
M143 H1 S270 ; set temperature limit for heater 1 to 270C
; 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"Hemera" 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
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
-
Can you please send M122 and M98 P"config.g" and post the results?
If you send M401 and M402 does the probe pin deploy and retract?
-
Hi Phaedrux
Here the info to M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6M2-NWNS0-7JKD0-3S86J-KB3VL
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 75128 of which 320 recycled
Never used RAM 12236, free system stack 98 words
Tasks: NETWORK(ready,14.0%,243) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,303) MAIN(running,85.1%,411) IDLE(ready,0.8%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:53 ago, cause: power up
Last software reset at 2022-02-13 18:54, reason: User, GCodes spinning, available RAM 12236, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 31.5, current 34.8, max 35.1
Supply voltage: min 19.0, current 23.8, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/16/16, gc cycles 0
Driver 0: position 16000, standstill, SG min/max 0/89
Driver 1: position 0, standstill, SG min/max 0/62
Driver 2: position 8000, standstill, SG min/max 0/82
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2022-02-15 16:08:27
Cache data hit count 4061530282
Slowest loop: 3.93ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 5.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 42290ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 14, completed moves 14, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.59ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address f4:cf:a2:68:48:1a
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 2097152, free heap 26104
WiFi IP address 192.168.178.43
WiFi signal strength -44dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
And here too M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Pin 'zprobe.in' is not free
Error: Invalid Z probe index
Heater 0 is disabled because its model is undefinedI don't understand where the errors come from ??
Greetings Michael
- WiFi -
-
@schotte do any of your other system files (e.g. homeall.g) contain a M558 command, or a command that refers to pin zprobe.in ?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
The M-code M558 does not occur, here are the contents of homeall.g and homez.g
homeall.g
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jan 22 2022 15:09:21 GMT+0100 (Mitteleuropäische Normalzeit)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-305 Y-305 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-305 ; home X axis
G1 H1 Y-305 ; home Y axis
G1 X5 Y5 F6000 ; go back a few mm
G1 H1 X-305 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-305 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X100 Y100 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 Z10 F100 ; lift Z relative to current position
G90 ; absolute positioninghomez.g
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jan 22 2022 15:09:21 GMT+0100 (Mitteleuropäische Normalzeit)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X100 Y100 F6000 ; go to first probe point
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 Z10 F100 ; lift Z relative to current position
G90 ; absolute positioning -
Can you confirm that all of your files are located in the system folder?
If you power on the board and immediately run M98 P"config.g" does it produce the same errors?
-
Same error right after turning it on. Files are all in the system directory
-
Can you upload your actual gcode files from the system folder? Download them from DWC or copy them from the SD card and then drag and drop the files onto a post window on the forum.
config.g, homeall.g, homez.g, homex.g, homey.g, bed.g, config-override.g, deploy-probe.g, retract-probe.g, and start.g, mesh.g if they exist.
Perhaps a screen shot of the folder structure of the SD card? Something seems off.
-
deployprobe.g config.g bed.g retractprobe.g homez.g homey.g homex.g homeall.g
The Config-Override.g, Start.g, Mesh.g are not yet available
-
If I squint hard and use my imagination I can almost make out the files listed in those images.
One other thing to try while I check over your files. Can you download a fresh copy of the 3.3 firmware package and upload the zip file via DWC? Just to reflash the firmware and make sure everything is present as it should be.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
-
I see no errors in those files.
How are you initiating the homing process? Are you sending G28 or clicking on the DWC homing buttons or are you running a macro?
-
Firmware reinstalled, error is still displayed after M98 P"config.g".
We click on the DWC homing buttons
-
Can you send M558 P9 by itself and report back what it says?
-
m558 p9
Error: M558: Missing Z probe pin name(s) -
Can you copy and paste this line into the gcode console and report back what it says?
M558 P9 C"^zprobe.in" H5 F120 T6000 -
-
Did a test, pressure plate goes up, but the pin from the Bltouch doesn't go out
-
And if you send
M950 S0 C"exp.heater3"does M401 and M402 work? -
Unfortunately not
-
Do you get an error from sending that M950?
If you replace the M558 line in your config with the one you manually sent, does it stop the error message you were getting before?
M558 P9 C"^zprobe.in" H5 F120 T6000
