Smart effector not triggering on G30
-
I've just installed the smart effector, and hooked it up to my Duet Wifi.
I tap the hot-end, and the green light blinks, but when I run the G30, it doesn't stop heading down.
Where is my problem likely to be?
-
Can you post your config.g and homing files?
-
; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool on Sun Feb 11 2018 10:18:09 GMT-0800 (Pacific Standard Time)
G91 ; use relative positioning
G1 S1 X650 Y650 Z650 F8000 ; move all carriages up 650mm, stopping at the endstops
G1 S2 X-4 Y-4 Z-4 F1800 S2 ; move all carriages down 4mm
G1 S1 X8 Y8 Z8 F360 ; move carriages slowly up 8mm, stopping at the endstops
G1 Z-5 F6000 ; down a few mm so that we can centre the head
G90 ; back to absolute positioning
G1 X0 Y0 F6000 ; centre the head and set a reasonable feed rate;config.g
; Configuration file for Duet WiFi (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Sun Feb 11 2018 10:18:09 GMT-0800 (Pacific Standard Time); General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin; Automatic saving after power loss is not enabled
;M665 L480.687 R262.460 H385.081 B150.0 X-0.297 Y-0.297 Z0.000 ;M665 L494.726 R266.961 H386.657 B150.0 X-0.265 Y-0.243 Z0.000 ; Set delta radius, diagonal rod
M665 L454.184 R254.97 H380 B150.0 X-1.06 Y-1.74 Z0.000
M666 X-2.09 Y-0.62 Z0 A0.00 B0.00 ;Put your endstop adjustments here, or let auto calibration find them
length, printable radius and homed heightM208 Z0 S1 ; Set minimum Z
; Endstops
M574 X2 Y2 Z2 S1 ; Set active high endstops
M558 P5 R0.4 H5 F1200 T6000 ; Set Z probe type to switch and the dive height + speeds
G31 p100 X0 Y0 Z-0.1 ; Set zprobe trigger height x36 y-17 Set Z probe trigger value, offset and trigger height
M557 R150 S20 ; Define mesh grid; Network
M550 PBigDelta ; Set machine name
M552 S1 ; Enable network
M587 S"" ; Configure access point. You can delete this line once connected
M587 S""
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S1 ; enable Telnet; Drives
M569 P0 S1 ; Drive 0 goes forwards
;M569 P1 S1 ; Drive 1 burned out
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
M569 P5 S1 ; Drive 5 goes forwards
M584 X0 Y4 Z2 E3 ; Apply custom drive mapping
M350 E16:16 I0 ; Configure microstepping without interpolation for extruder
M350 X32 y32 Z32 I1 ; Configure microstepping with interpolation
M92 X160 Y160 Z160 E150 ; Set steps per mm
M566 X72000 Y72000 Z72000 E1200 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z18000 E1200 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z1000 E1000 ; Set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Heaters
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S80 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4725 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C
;M305 P2 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 2
;M143 H2 S280 ; Set temperature limit for heater 2 to 280C; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X-7.5 Y8 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M563 P1 D1 H2 ; Define tool 1
G10 P1 X40 Y5 Z0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C; Fans
M106 P0 S.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S0 I0 F500 H T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on;Heaters
M307 H0 G118.4 C996.4 D1.0 S1.0 V12.6 B1
M307 H1 A249.9 C101.0 D2.8 S1.00 V12.6 B0
M307 H2 A567.4 C282.6 D5.1 S1.00 V12.6 B0; Custom settings are not configured
M501
T0 -
@stoop said in Smart effector not triggering on G30:
I've just installed the smart effector, and hooked it up to my Duet Wifi.
I tap the hot-end, and the green light blinks, but when I run the G30, it doesn't stop heading down.
Where is my problem likely to be?
Possibly a short between the Z probe IN and GND pins on the Duet, or between OUT and GND on the effector, or in the cable. If you unplug the 8-way cable from the effector, the Z probe reading should jump to 1000. Does it?
-
no shorts in cable, checked all the runs. I'll check for shorts while everything is plugged in, z-probe is currently returning 0.
-
unplugging 8 way cable returns 1000
-
P parameter in G31 is p in your config. Shouldnt it be P ? I mean capital letter or how you call it in english...
-
@stoop said in Smart effector not triggering on G30:
unplugging 8 way cable returns 1000
Check the underside of the Smart Effector for a solder bridge between the pins of the 8-way connector.
-
4k ohms between zprobe in and gnd on duet (tested from 8-way plug)
Aidar, changed, I'll test. I think duet handles this though.
-
no solder bridge. nothing reading as a short anyway.
-
Aidar - No change after capitalization.
-
DC42 - Is there any way to log the zprobe hit? like can I just put a LED between 2 pins and see if it blinks?
I also can hook up my oscilliscope if I know what I'm looking for. -
@stoop, yes you can connect an LED between output and ground.
The schematic is is at https://github.com/T3P3/SmartEffector/blob/master/SmartEffector/SmartEffector_v1.3/SmartEffector_Schematic_v1.3.pdf. You will see that same pin of the attiny MCU drives the LED through a 150 ohm resistor, and the output pin through a 1K resistor. If the 1K resistor was open circuit then you would get a Z probe reading of 1000 all the time because of the pullup resistor in the Duet.
-
@dc42 I get a v+(3,3?) blip on z_probe_in on the duet wifi board when I tap the hot end.
So, either Duet wifi board, or config is wrong.
How can I see what the firmware is seeing?Can I run the Z_Probe_in to somewhere else?
-
Maybe I'll start the config.g from scratch.. But you see what I have there, nothing misconfigured?
-
@stoop said in Smart effector not triggering on G30:
M558 P5 R0.4 H5 F1200 T6000 ; Set Z probe type to switch and the dive height + speeds
Please send M558 without parameters, and check that the values it reports match those values in config.g. Also send G31 T5 to check that the G31 parameters are correct.
-
M558
Z Probe type 5, invert no, dive height 5.0mm, probe speed 1200mm/min, travel speed 6000mm/min, recovery time 0.40 sec, heaters normal, max taps 1, max diff 0.03G31 T5
Threshold 100, trigger height -0.10, offsets X0.0 Y0.0 -
Ok, Been farting around.
When I tap the hot-end, the Zprobe on the web interface DOES go to 1000.
But it doesn't stop diving on the G30.What the heck?
I just re-updated the firmware to the latest 2.02
Same thing. -
Most strange:
- You have verified that you are getting a 3.3v pulse on that signal
- If you disconnect the Smart Effector from the Z probe input, the Z probe reading changes from 0 to 1000, so the Z probe input is working
You could try using P8 instead of P5 in the M558 command to get a faster response; but the pulse should be plenty long enough for P5 to work too.
-
Yes, I can SEE the pulse on the web interface, I can't imagine its not long enough, but I'll try that now.
I USED to have a mechanical z-probe, is there some other setting I might have changed?
