Klicky Probe gets attached but then Error occurs
I am really sorry to bother you guys already again but I cant find the error with my Klicky. Its getting picked up properly moves back and then stops and the error "Shutdown due to expected probe state to be deployed but is stowed (1)" appears.
I already set up the printer.cfg again as in another thread mentioned. But it seems to keep failing.
Do I have to config something else for the homing to make the Klicky work? As far as I understood I only had to "activate" it.
Didn´t want to mess anything up so I just changed the pick up position.
best regards
Tri-D
24 Replies
fair-rose•17mo ago
Morning! I fucked around a little and figured out that the Probe and Z-Endstop always were shown as triggered.
So I activated this one in the printer.cfg
Probe
[probe]
#pin: ^toolboard:probe_pin # For NPN NC probes such as the SuperPinda / Vinda / SupCR / Decoprobe probes.
#pin: ^!toolboard:probe_pin # NPN NO (refer to the specs on your probe)
pin: toolboard:probe_pin # PNP NO (refer to the specs on your probe)
#pin: !toolboard:probe_pin # PNP NC (refer to the specs on your probe)
Now the probe is being attached and Z is Homing. But as soon as the probe is going to be stored again, the Error
Also after Z-Tilt I get Errors:
Error evaluating 'gcode_macro _ASSERT_PROBE_STATE:gcode': gcode.CommandError: expected probe state to be stowed but is deployed (0)
09:47
Error evaluating 'gcode_macro _ASSERT_PROBE_STATE:gcode': gcode.CommandError: expected probe state to be stowed but is deployed (0)
09:47
Error evaluating 'gcode_macro _ASSERT_PROBE_STATE:gcode': gcode.CommandError: expected probe state to be stowed but is deployed (0)
09:47
Error evaluating 'gcode_macro _ASSERT_PROBE_STATE:gcode': gcode.CommandError: expected probe state to be stowed but is deployed (0)
I think something is still something messed up.
Also Z-Home only sometimes is working
This is probably a wiring issue. Stowable probes don't work with NO probes and AFAIK all of them are NC
The state check that results in shutdown is preventing damage to your printer from a nozzle crash, so it's doing it's job at least 🙂
fair-rose•17mo ago
So I should change it to PNP NC did I get this right? I measured the wires, they seem fine
Happy to hear it saves me money 😊
Yes, indeed, also if you could show the wiring on both ends, maybe some pins are swapped or something. Microswitches also often have 3 legs, gnd, nc and no.
Also you want NPN NC not PNP NC. The circuit is floating when not triggered, hence the need for a pull up resistor
^fair-rose•17mo ago
Ok i will try NPN NC with the Klicky
NPN NC is what i use with my Euclid
eastern-cyan•17mo ago
@miklschmidt : I am currently facing the exact same issue: After picking up the Probe, an emergency shutdown occurs. Is there anything else, that needs to be configured for the Klicky to work on the EBB42?
eastern-cyan•17mo ago
eastern-cyan•17mo ago
I checked the connector with a mulitmeter and it shows a closed connection in the normal state and no connection when the probe is manually triggered (so electrically working as expected)
The probe is connected to GND and PA5
test with QUERY_ENDSTOPS to confirm your wiring and configuration
Configuring RatOS | RatOS
RatOS only needs minimal configuration to work, but comes with a lot of optional functionality that you can enable manually.
eastern-cyan•17mo ago
Thanks, I did that, but I was not sure if the one for Z also applies for a klicky
But anyways, it does not work for Z (so something is wrong)
It does, because you're supposed to wire it like a probe: https://os.ratrig.com/docs/toolboards/btt/ebb-42-12
eastern-cyan•17mo ago
Ok, with Pin 1&3 it works now. The strange thing is: On the octopus (with 2.0 alpha) I had it running with Pin 1&5
Might be a good idea, to add that to the documentary - as on the klicky page, the Probe Pin is recommended (which is Pin5) 🙂
different wiring