RLA wrote: So then it does not matter about controller(pc)...it is the drive ...so what I have should work on mach 3 making realtime compensations when encoder says so..is that right?..I appreciate your patience!!
No it will not compensate.
With the drives you have, as SLC said, mach or LinuxCNC will send them some steps so the drives will forward those steps to the motor and if the motor stalls only the drives knows about it, so software is not aware of it and can not compensate.
For that you will need to have the loop closed in LinuxCNC, meaning the encoder feedback has to go to LinuxCNC also.
The difference between LinuxCNC and Mach is that mach does not know if the timing for creating steps is right or that it can not make the steps requested at all, it will just try to send steps at the speed requested not knowing if they are actually being sent to the parallel port. That is why mach needs other hardware to do the stepping correctly.
LinuxCNC will warn if the steps requested are to fast so you can correct that, and when set up correctly it will always send the requsted steps to the parallel port or other hardware.
In general, what you are asking for requires having the loop closed in LinuxCNC, that way LinuxCNC is always aware of what is going on with the machine and will compensate for the loss of position, if the drives are capable of doing that. And that brings us to the other issue, that the stepper drives and motors are quite limited at correcting lost position.
If you want actual real time and compensation, use analogue servo drives with a Mesa 7i92/7i77 combo with LinuxCNC, or Lam Technologies stepper drives that have a "boost" input so they will push more current to the motors whenever LinuxCNC detects that the position is lagging behind.
You are overcomplicating things, find a PC with a parallel port and install LinuxCNC, wire the drives and start using the machine, then you can think about this stuff.