821
Show"N"Tell ( Your Machines) / Re: Success! Mini Machining Center under Mach3 control - Video link
« on: April 29, 2010, 01:27:40 PM »Current Hi/low is an ouput signal that can be mapped to pin/port, look in config,pin/port,output. BUT it signals on ANY axis movement and is WAY too far behind the data stream time wise.I'm not familiar with the 'current hi/low', but my ignorance there is irrelevant since by your description, it would be unusable in any case. Sounds like you have a visual on the challenges.
I have seen this done from a motion card and a realtime system. I cannot fathom it working from mach(;-( WITHOUT the use of a macro. You would have to be able to TAP the function into the DRIVER level. AND as Art said once "That aint gonna happen".
In order to function, it seems to me that the trigger must come from the servo drive. So I would need a drive that has or will have some function that identifies a condition where the lock should be applied and released. Custom firmware is certainly one path. A 'position reached' function looks like a promising possibility.
Another poster mentioned the need to disable the drive while the spindle is locked. The 4th axis has a belt drive and the lock is on the spindle and *so far* there is enough 'give' in the belt that the drive is not too unhappy with a count of two off an 1800 line encoder . . . BUT . . I am also pursuing the solution mentioned where the drive is disabled during the lock event and re enabled. I am waiting to get one question answered by a vendor to determine the feasibility of that solution.
Overloaded: you are exactly correct. Right now I have to manually insert the macros int the G-code. Automating that process would require messaging a post processor, as you correctly point out. I want to avoid this. That is what drives the goal to make it automatic and transparent.