No Z Motion On Probe or Probe Test - DRO Indicates Motion
M3 $0 S1 or Probe Test button begins probe sequence, DRO indicates Z motion until soft limit/error, but Z axis doesn't move.
Activating z switch sensor it passes probe height stops the indicated Z motion, or raises correct error if activated too high.
Any help would be greatly appreciated!
The only issue I see after a quick look is that [AXIS_Z]MAX_VELOCITY should be 2, but I don't think this is causing any problems.
I would suspect maybe a motor power supply or wiring problem, this may cause the first issue as well.
Second issue arises after probe attempts and(?) on-screen E-Stop - keyboard Up/Down keys will often move (only) the second Y (Joint 2) motor.
I am not sure what you mean here.
Limit, Ohmic, E-Stop, and feedhold switches, relays, etc. still attached to ESS/TMC3in1, that Mesa components are replacing, and will latter be moved to 7i96 I/O.
What causes the high pitched noised? Is it just a stepper motor thing? My new steppers make a higher pitched noise when z axis is probing.
Table in use daily with Mach3, ESS, TMS3in1 THC, and large/clean linear power supply. Testing 7i96 involves just cable swap (above) and network cable. Tried other PC's with fresh LinuxCNC/Plasmac installs. Tried second known good cable. Tried other known good ethernet cables. Tried with and without THCAD installed and/or configured. Swapped X and Z stepgen's and issues followed Z. Moved Z to stepgen not on P1 with IMS and Gecko drivers connected and issues followed Z. Tried several know good 5V power supplies - isolated or common ground with rest of electronics. Tried two other known good G540 controllers. Works fine with $2 parallel BOB and Mach3 or LinuxCNC. Tests good with another ESS and a USB SmoothStepper.
Working table, so after troubleshooting while 7i96 is installed for 1-2hrs/day for a week I'm certain that I've eliminated all hardware and wiring. Many, many people successfully running LinucCNC without issues and I suspect only that my configuration (probably something really simple) is to blame as this is first Mesa board install or configuration.
Absolutely have to eliminate Mach3 and SmoothStepper nighmare on plasma and 2 router tables...
Have you customised any of the .hal or .tcl files that come with PlasmaC.
Power it up and Home it
Watch the pins:
axis.L.eoffset-enable Input(bit): enable
axis.L.eoffset-counts Input(s32): input to counts register
axis.L.eoffset Output(float): current external offset
Run a Probe Test
enable should be on permanently
counts and eoffset should begin counting
Trip your probe
counts and eoffset should be stationary
After the timeout counts should be zero and eoffset should be almost zero
Although I suspect because you say the DRO is counting then this will all be correct as well