458
« on: August 20, 2017, 11:04:10 PM »
fast89,
What I am struggling with is that you are using a different screen set, and may have different macros in use, an index that's
runs through a bob, and a bunch of things that requires setup via plug-in.
SO
Maybe simplify the whole thing by just testing with basics.
INDEX
I see nothing wrong with your reply about your physical index. It turns on and off per test, you can make the single slot much wider, even a lot wider, than what is calculated per the Mach3 Turn Manual. Wider is better than too narrow. As long as you are getting correct rpm range in DRO all is good. The rpm is based on the index and the index also implements the movement to start threading when mode changes from G94 to G95.
In the simplest way of index configuration the index pulse just goes directly to pp port pin of the computer. Nothing to influence
it's info to Mach, such as going through a bob or whatever. One can actually make a timer circuit ( or use a pulse generator instrument ) for providing different pulses and check the DRO with out a motor running ( click the spindle button to turn on a faked motor which is actually the timer and Mach thinks the motor is turning the spindle / index providing for a dro readout and also threading implementation. It's been years since we tested and fixed the threading cycle.
So what the above would do is isolate the index to setup and confirm, then can be run through the bob or what ever and see if all is the same, and then add some stuff and define the culprit.
Now I know that there have been modified versions of the M1076 done and posted. I would think we want to make sure the original is used as it's been around for years and frankly can't recall any problems in a looooooooong time of it's use. Heck don't even anything and just create some repeating code based on G32 ( which is nothing more than a G01 at a feed with the addition of when to start axis motion )
RICH
Guest
Show Posts
on your face.