PCW wrote: Alternatively, you could free up a pin by sharing the Y and Z
home/limits allowing gantry squaring when homing.
Ok, I
think I
may have sorted out how to do this...
If I've got it right (which will come as a huge surprise), I can just hang the Z switch in parallel with the Y (they're all NO because... reasons... don't ask), and then in the HAL switch this bit:
Code:
net min-home-x <= parport.0.pin-10-in-not
net min-home-y <= parport.0.pin-11-in-not
net max-home-z <= parport.0.pin-12-in-not
to something like this:
Code:
net min-home-x <= parport.0.pin-10-in-not
net min-home-y <= parport.0.pin-11-in-not
net max-home-z <= parport.0.pin-11-in-not
net max-home-xx <= parport.0.pin-12-in-not
net probe-in <= parport.0.pin-13-in-not
I assume (read: hope, but don't really believe) the .ini can be left largely alone, as long as Y & Z are separately sequenced.
If it sounds like I'm guessing rather than trying any of this out, it's... err.... because I'm guessing rather than trying any of this out. I had to put in an order for a few more connectors & switches, which won't show up until... well... these days who knows?
In the meantime (assuming my guesswork doesn't set off too many "what the %$^$ were you thinking???" alarms), my next project is trying to get a simple Z touchplate working - which is the last piece I need to have a roughly functional system that I can try to start working with instead of working on. Unfortunately all the howtos I've been able to find require axis (I'm running gmoccapy) and about all I've managed is getting probe-in detected. Any chance there's a simple way to go about this?
Or am I about to fall down the sort of rabbit hole that needs a new thread?
-Bats
(I still haven't recovered from the last rabbit hole... do you have any idea how hard those little buck teeth can bite?)
