Smart Effector z-probe always on 1000
-
Hello, I have Duet 2 Ethernet (rev. 1.3, soft ver. 3.4) and Smart Effector (rev. 3.0). I tried almost everything to went through auto callibration but always my z-probe value's 1000 and callibration process's end immediately. I'm sure cable wiring is corectly done. Crimps are deep in connectors. I tried tips from similar topic but it doesn't help: https://forum.duet3d.com/topic/2739/z-probe-stuck-at-1000-with-smart-affector (shorting pin of z-probe on duet board give 0 value like it should). I'm fighting with duet 2 and smart effector nearly a month and I'm losing hope it will finally work
My config.g file:
; Configuration file for Duet Ethernet (firmware version 3.4)
; executed by the firmware on start-up
; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Mar 22 2022 21:42:46 GMT+0100 (czas środkowoeuropejski standardowy); General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves; Delta Settings
M665 L440.380 R226.821 H407 B185.0 X0 y0 z0 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 y0 z0 A0.00 B0.00 ; Put your endstop adjustments here, or let auto calibration find them; Network
M550 P"Anycubic Predator" ; Set machine name
M551 P"" ; Set password
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP
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 S1 ; Drive 2 goes forwards
M569 P3 S0 ; 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 Z80.00 E415 ; Set steps per mm
M566 X3000 Y3000 Z3000 E3000 ; Set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z12000.00 E12000 ; Set maximum speeds (mm/min)
M201 X9000.00 Y9000.00 Z9000.00 E6000.00 ; Set accelerations (mm/s^2)
M906 X1400.00 Y1400.00 Z1400.00 E1000.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Retraction
M207 S2.5 F7000 R0.1 T2500 Z0.5 ; Firmware retraction; Axis Limits
M208 Z0 S1 ; Set minimum Z; Endstops
M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop" ; configure active-high endstop for high end on Z via pin zstop; Z-Probe
M558 P5 R0.4 H3 F1200 T6000 C"zprobe.in+zprobe.mod" ; set Z probe type to effector and the dive height + speeds
G31 P100 X0 Y0 Z-0.1 ; set Z probe trigger value, offset and trigger height
M557 R180 S20 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; 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 B3950 ; 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 S280 ; set temperature limit for heater 1 to 280C; 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 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
M591 D0 P2 C4 S1 ; Activate filament sensor
M404 N1.75 ; Set for print monitor
M575 P1 B57600 S1 ; Paneldue baud rate; Miscellaneous
M501 ; Load saved parameters from non-volatile memory -
@akinori said in Smart Effector z-probe always on 1000:
https://forum.duet3d.com/topic/2739/z-probe-stuck-at-1000-with-smart-affector
I assume you're going through this? https://docs.duet3d.com/en/Duet3D_hardware/Accessories/Smart_Effector
Can you send M122 and M98 P"config.g" and post the results?
Can you disassemble the smart effector and take some clear close up photos of both sides?
If you connect it when not mounted does it report differently?
-
@akinori is the green LED on the Smart Effector working normally? It should be off normally, but flash when you tap the nozzle upwards.
-
@phaedrux
Yeah, I go step by step with this guide. I disassemble effector but, probe-z value is still on 1000 :c5.04.2022, 18:17:43 M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: in file macro line 77 column 13: M591: expected string expression
Warning: Macro file config-override.g not found5.04.2022, 18:17:28 M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet Ethernet 1.02 or later
Board ID: 08DJM-9178L-L2MS8-6JTD6-3SS6N-19DLQ
Used output buffers: 6 of 24 (12 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 69092 of which 268 recycled
Never used RAM 18852, free system stack 192 words
Tasks: NETWORK(ready,21.0%,240) HEAT(notifyWait,0.0%,338) Move(notifyWait,0.0%,364) MAIN(running,75.6%,448) IDLE(ready,3.4%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:25 ago, cause: power up
Last software reset at 2022-04-04 19:10, reason: User, GCodes spinning, available RAM 16112, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 26.0, current 29.2, max 29.6
Supply voltage: min 24.0, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2022-04-05 18:17:25
Cache data hit count 938378659
Slowest loop: 5.74ms; fastest: 0.19ms
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 3.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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: 8.50ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(2) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex@dc42 LED is blink 2 times when power on, but it doesn't react when I tap nozzle.
-
When and where was your smart effector purchased?
-
@phaedrux Through this website http://filament23d.dk
It was closest avaible option. I bought it 12/02/2022 and arrived to me in Poland around two weeks later.
I wrote to hobby-store.pl about the chance to buy this part but they did not respond to me -
We shall see if DC42 has any other ideas.
-
@akinori I think you may have a wiring error between the Smart Effector and the Duet. Please post photos of both ends of the cable between the 8-pin connector on the effector and the Z probe connector on the Duet.
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 -
@dc42 You had right! Mi wires was connected in proper order but, for some reason it doesn't work. But I use different wires, crimped again and everything works
-
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved
