ok, that means the Motor Controller tunning is OK.

have you tryed to reduce the spindle acceleration/deceleration in CSMIO plugin Setup ?

6000rpm/s is pretty high.

Will try that now
 

Hmm,

I have been conversing a lot with member lion_rapid, great guy as you all are

We have managed to get the spindle tuned now, also I can get orientation to work perfectly in the CSMIO plugin config page. I have it set so I can insert a locking pin into my spindle shaft to allow me to unlock collets etc.

BUT

In M3/M5 and M20 calls orientation fails every time, M20 throws up angle errors every time. Having "stop at position" turned on in config  just makes the spindle stop at random locations every M5 call.

Baffled now - so near but so far away

ok did a Little bit of reading about M20.

from the Manual (https://www.en.cs-lab.eu/technical-support/download/addons-macros/macro-m20-for-spindle-positioning/)

1.Settings:
a.Using M20 macro for spindle positioning, you can’t use „Align at stop” function at the same time (plugin „Spindle” tab) and reversely


3. The M20 macro verifies the set and real position after spindle positioning.
If the difference between those two values is higher than „Const Offset = 1” parameter value, the „M20 ERROR Offset !!!„ error will appear.
The „Const Offset” value can be reasonably adjusted to our needs (the value of 1 is usually optimal).


that means you can "Play" (increase) a bit with the

Const Offset = 1

in M20.M1S macro.


btw:
I can get orientation to work perfectly in the CSMIO plugin config page

how did you do this?

Yes i read the bit about the M20 and align at stop, i have turned off AOS but M20 still fails.

The get it to work in config all we did was tune the servo better. I have no idea what to look for but lion_rapid did, we went through it on the phone and it runs much better now, apart from this M20 thing.

and what angledifference does the M20 errormessage Show?

Different error every time, can't see any pattern to it at all.

It's bugging me that it works 100% in the config window, but 0% in Mach3 - makes me think it could be a Mach3 or Interface problem, it wouldn't be the first one 

well sounds like it is time to contact CS Lab.

Yep,
I have an ongoing chat with a guy there, i have forwarded this last bit info to him.

Usually takes a week or two for a reply 

At least it proves it can work.

CS-LAB have found the issue

In the CS-MIO plugin config, under spindle axis, do not use "reversed direction" - there is a firmware bug that stops spindle alignment working

I had to untick that box, tick "encoder reversed direction" and also reverse the motor direction inside the servo drive itself.

All working now, very accurate and also with the shared encoder ( i didn't tell them that though )