topic_unsolved Height sensor functionality lost (DWC3.2-RC2, Toolboard)
TL; DR: mini IR probe suddenly does not talk to toolboard, despite seemingly initializing and working sensor. Toolboard recognizes simple mechanical switch. Is the probe dead?
I have for a long time successfully used a dc42 mini IR probe, but today it stopped working properly.
Here is how it's configured:
M558 P8 C"10.io1.in" H5 F120 T3600 ; set Z probe type to unmodulated and the dive height + speeds G31 P500 X-35 Y0 Z1.465 ; set Z probe trigger value, offset and trigger height
Previously when the probe triggered, the green LED on the Toolboard lit up in sync with the probe's red LED.
After a nozzle change during adjustment of the Z trigger height, the probe stopped working:
G30 S-1failed due to "probe already being triggered" when Z was at 10mm height.
The probe did not light up at this time, so it was no misreading by the sensor.
In DWC I see the probe continuously reporting "1000" (triggered for the digital probe).
Testing with my finger, I saw the probe light up at the expected ~2mm distance, so the sensor circuitry seems to be intact.
I did the sensible thing and powercycled the board, at which time the toolboard would not sync with the main board. When I disconnected the mini IR probe, the toolboard returned to life.
Reconnecting the probe, it blinked once, had a short pause, and then blinked twice. It still would not be recognized by the toolboard (probe level 1000, no syncing LED blinking with the finger trigger test).
I tried manually configuring the probe running the M558 command from my config.g. The first time I got the error message that the toolboard does not have handle 3000, but this error did not repeat, even after full power cycles of the printer (including the SBC).
Testing with a simple mechanical switch (Makerbot endstop replica), the probe is detected as triggered in both normally-open and normally-closed configurations, so it looks like io1.in is still working (provides 3.3v, and reads signal off a simple mechanical switch). I do note though that the green LED does not turn on during this test, but DWC and M119 report the trigger state of the mechanical switch.
Does it mean my probe is toast?
(Ironically, I gave another mini IR probe I had lying around but didn't use away the other week, or I would easily have been able to check with another...)
Connecting to the v0.6 Toolboard's IO0.in (screw terminal on the right hand side) worked once in testing and stopped working when the board was installed in it's usual place. (I triple checked the wiring).
Connected to the Duet3 board's IO3 port, the probe works both with 3.3v and 5v (but I don't have long enough cables to install that right now).
Now, I could jury-rig something by soldering cables , but it already almost doubles the wires from the toolhead to the board (tool distribution board notwithstanding).
Any help how to further debug the toolboard's IO ports which seem to be working with simple switches are more than welcome.
This is still an issue with 3.3b2. the 1LC IO1 port powers the probe, it blinks twice, and the LED turns on if I put something close below it, but it's not triggering on the RRF side.
Again, connecting the probe to IO0.in worked once and then stopped after a reset.
config.g for completeness sake.
And with IO0 in config.g, the probe works ... for now. IO1 is still not working.