Hi John, I've reworked this branch to make it a single commit and it is rebased on master now.
so either picking http://git.mah.priv.at/gitweb/emc2-dev.git/commit/4e6577497aee1a5f9ec5db8504fe4dd9b52ec1ab or merging http://git.mah.priv.at/gitweb/emc2-dev.git/shortlog/refs/heads/add-missing-osubdemo-ui-file-fixed should work sorry for this -m Am 18.03.2011 um 13:07 schrieb John Thornton: > Hi Michael, > > I tried to get the patch but ran into problems so I'll wait for you to > commit the gladevcp ui file. I look forward to seeing that work. > > Thanks > John > > Michael Haberler wrote: >> Hi John, >> >> actually this is in place in master already. I'm currently writing the >> documentation for all that toolchange stuff, but the code+example works. >> >> There is a complete example with Tx and M6 remapped to o-word subroutines, >> as well as o-word procedure called on abort to fixup state as needed. A >> gladevcp panel shows the pins and has buttons to acknowledge them - sort of >> manually stepping through the change process. >> >> try emc owordm6-ui.ini in configs/sim >> >> The nc_files/m6demo.ngc file attempts to model the existing >> M6-through-iocontrol as closely as possible - it should be straightforward >> to add your toolchanger specifics here, or in the corresponding prepare(Tx) >> procedure in nc_files/tdemo.ngc . >> >> (unfortunately I forgot to add the gladevcp UI file - you need to pull it >> from here until it's merged: >> http://git.mah.priv.at/gitweb/emc2-dev.git/commit/4a67f60b742a17a69aa4d49868a5e3585047bb08 >> ) >> >> I'd be happy to help and am very curious to see some use! >> >> -Michael >> >> >> Am 17.03.2011 um 13:09 schrieb John Thornton: >> >> >>> Hi Michael, >>> >>> While it will be nice to be able to orientate the spindle for various >>> operations a tool changer needs be be somehow a defined set of >>> operations that is called by M6. On my lathe I do it via classic ladder >>> but there is no Z movement needed so it works fine. On my VMC the Z has >>> to move so it would be more difficult in ladder. >>> >>> The sequence for my carousel type tool changer is: >>> >>> Rapid to absolute Z pickup/drop off position >>> Orientate spindle >>> Extend tool carousel >>> Release pull stud clamp >>> Move to absolute Z clear position >>> Rotate carousel to next tool via shortest path >>> Move to absolute Z pickup/drop off position >>> Clamp pull stud >>> Retract tool carousel >>> >>> If you could incorporate a tool change script that can be customized by >>> the integrator that would be cool and make tool changers easy to do. I >>> hope the M19 leads us to that point someday before my 386 dies on the >>> Discovery... >>> >>> John Thornton >>> >>> Michael Haberler wrote: >>> >>>> spindle orientation looks useful for toolchanging and maybe other stuff, >>>> and some people even have done it with VFD's; some infrastructure already >>>> exists in NML although it isnt fully implemented. >>>> >>>> I'm looking at adding an M19 command similar to the Fanuc spindle-orient >>>> like: >>>> >>>> M19 [R<orientation in degrees; defaults to 0>] [L<orientation cw/ccw>] >>>> >>>> this is how I'd do it: >>>> - turn off the spindle >>>> - set a HAL pin spindle-orientation line to convey the degrees value >>>> - set a HAL pin spindle-direction line to convey the cw/ccw direction >>>> - assert a HAL pin orient-spindle line >>>> - wait for a spindle-oriented HAL pin line to become true >>>> >>>> Further HAL logic would take care of actually driving the spindle motor, >>>> taking feedback from the spindle encoder into a PID loop and assert the >>>> spindle-oriented pin when done (still making sense?) >>>> >>>> my question: >>>> >>>> all spindle commands go through motion which is realtime; the above >>>> sequence doesnt look to me like it has strict realtime requirements so I >>>> would rather go through iocontrol-v2 to do this. >>>> >>>> Is this sound or am I overlooking something? >>>> >>>> -m >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Colocation vs. Managed Hosting >>>> A question and answer guide to determining the best fit >>>> for your organization - today and in the future. >>>> http://p.sf.net/sfu/internap-sfd2d >>>> _______________________________________________ >>>> Emc-developers mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/emc-developers >>>> >>>> >>> ------------------------------------------------------------------------------ >>> Colocation vs. Managed Hosting >>> A question and answer guide to determining the best fit >>> for your organization - today and in the future. >>> http://p.sf.net/sfu/internap-sfd2d >>> _______________________________________________ >>> Emc-developers mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/emc-developers >>> >> >> ------------------------------------------------------------------------------ >> Colocation vs. Managed Hosting >> A question and answer guide to determining the best fit >> for your organization - today and in the future. >> http://p.sf.net/sfu/internap-sfd2d >> _______________________________________________ >> Emc-developers mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/emc-developers >> > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
