Smart effector not triggering on G30
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?
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.
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.03
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
- 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?
Please confirm that this is the test you are doing:
- Position the effector well above the bed.
- Send G30. [Printer must previously have been homed.]
- Effector moves towards the bed
- Tap the nozzle upwards
- The green LED on the effector should flash, and the downward movement should stop at the same time.
Well, I deleted my config.g override, and changed to p8. It stopped travel.
Changed back to p5, seems to be working now.
Odd, nothing in the config override should have been doing anything, but it seems to be working now.
Thanks for all your help @dc42