For documentation purposes, I figured the issue out. The issue was that the potentiometer was rotated 180 degrees. Had some back and forth emails with Idris @Precision Piezo and he confirms that it's a super hard thing to diagnose. I just got lucky and gave it a shot.
The Orion is working flawlessly now.
@droftarts I do have crimpers. I used to do a lot of network cables back in the day. I have the tools/skills, I just hate those connectors. Home-Made, Pre-Made, or otherwise. I also don't want to have to unsheath a pre-made cable if I don't have to. Plus, a pre-made cable will end up costing almost as much as a big bag of connectors and won't end up lost in my bin-o-cables to be thrown away in 15 years when I finally dig through them. 
@fcwilt OG is "original gangster". Means old school.
I guess I just have hope that there would be a fancy new way that works better. Guess not. Boo.
@fcwilt I just can't do it. I have BL touches on my other printers... But it's just such an OG.method. I wanted something fancier.... I guess nothing exists... Klicky? Lol
@fcwilt Are you just referring to the Duet3D Scanning Z Probe/SZP/Coil? That's what I'm using too. I just don't consider it a viable touch probe. Yet.
@fcwilt what makes that an E3D scanning probe?
@fcwilt unfortunately my z probe is the scanning probe, and consistent it is not for single "touch" probes.
@fcwilt So you recommend having a hard min stop adjusted to nozzle height for the actual bed itself, rather than a nozzle style? I liked the concept of having a nozzle tip = zero every time probing method. Regardless of nozzle. The way you describe would need offset tweaking every time I swapped nozzles and such.
I do like the simplicity of your method and I even started designing mounts around that, but veered off into the method I have now.
Either way, that document needs to be updated.
@jay_s_uk Also, odd setup or not, that link is severely misleading and just plain incorrect. Worth updating.
@jay_s_uk said in Dual Z endstops and G30:
@micaheli Use M574 and G1 H1 commands.
Ignore probes and G30's
That won't work. I've tried. It only stops the corresponding stepper and continues to plow the other one up, jacking the bed all slanted and jamming the stepper. The ONLY way the other one will stop is if the nozzle moves over to it.
I did, however, just get it working with M558 and G30's. I just had the indexing wrong on those during the while true loop. It's now working and probing correctly.
Once I get it all working, I'll return with my full configs.
@fcwilt They are sexbolt style endstops. So the nozzle touches each of them, then moves to the other and back, etc.. To level the bed. Each endstop has it's own input io3.in and io7.in. Each ties to it's own stepper for the corresponding side.
I'm noticing that if I just do a G1 H1 to home, it only stops the corresponding stepper.... which is undesirable as well.
I feel that if I did an individual G30 (if that worked) it would stop both steppers for the z-axis movement, but not sure if that's the right thing to do as I'm not having luck implementing it.
Hey there. My annoying self again.
I'm implementing dual z endstops at the leadscrew positions and I found the following doc:
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_auto_levelling#axis-levelling-using-endstops
This document is very misleading... if you follow it, you'll get G30 failures because it does not define a probe. Instead I feel like I need to do a G1 H1 move during the "while true" auto leveling sequence?
Should I instead of M574, be using M558 for each endstop? Give them K0/K1 designations and push the scanning probe to K2?
I'd love to know what I'm doing wrong here. Attached are my config.g, bed.g and homeall.bed.g config.g homeall.g