On 11 Jan 2008 at 6:33, [EMAIL PROTECTED] wrote: Thanks for the information Alex, I just assumed that M66 was real time...
I still wish I had an example of it so I could see why it won't work for me... Thanks John > I can't think of any possible reason why it would work with a pyvcp > button, but not when using the parport. > > > > Has anyone used M66 with a parport input? > > > > I seem to be unable to make it work with a hardware input. > > I have made it work using a pyVCP button. > > I'm told that it works so I must not be able to figure it out. > > > > What I have done so far is documented here: > > http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Mword > > > > If anyone can point out where I failed that would help. > > > > I think that M66 would be better for plasma control than using > > the spindle on/off as the spindle is not real time. > > M66 is way further away from realtime than spindle control. > It causes the interpreter to halt and wait for an input, and once that > comes (checked by task which is not realtime), it starts interpreting, > putting things back on the queue, which then get executed, etc. If for > example the harddrive happened to spin down during the M66 wait, the > interpreter *can* take a long time before it starts resuming.. > > > > Thanks > > John > > Regards, > Alex ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
