@Phaedrux One additional test: I plugged the P-switches into IO4in and IO5in with the same result: the DCS is not started. One final observation, the Diagnostic LED is flashing red about once per second with the P-switches disconnected, even though I have the inputs "Not Assigned". I'm hopeful that some of these details well shine a light on the issue... I'm befuddled. Thanks for your help!!
Best posts made by BARN-Metal-Fab
-
RE: Pi4Duet3 DCS not started & Proximity inputs into IOx.in
-
RE: Pi4Duet3 DCS not started & Proximity inputs into IOx.in
@Phaedrux I'm getting a SPAM block when I try to send all I typed, so I've broken this up:
I have dug further and done some testing. As stated before, the Z proximity switch doesn't cause the fault, just X & Y. I did some testing with a meter (both resistance and voltage) and the three sensors all act in the same fashion. These switch as expected when metal is near, and each outputting nearly the same 24V (27.2) as is supplied, less a couple of tenths, when the sensor switches.
It appears that Spam detection is stopping my post when I include the dot between IO4 & in.
-
RE: Pi4Duet3 DCS not started & Proximity inputs into IOx.in
@Phaedrux Thanks for your input on that... It seemed to me that I had seen other M122 logs that had more info. That coupled with the message: "Response too long, see console" led me to believe I wasn't seeing it all, but that probably simply means to look in the Console, which is what I was already doing. Noob ignorance!!