Hi Jon. What you are telling me maybe is a part of what I'm seeing . I do believe that the same thing is happening also for an M66 call . I'm saying this becase the M1xx is called only during the first o<named> sub call and disabled during the other 3 calls. But what I can see is that the disk access is done during the whole NC program execution. Inside the subroutine there are M66 calls that trigger each axis movement and my feeling is that also this can cause a disk access. I don't know why this should happen , maybe I'm wrong but this is what I can see . In any case these custom M1xx function management (access to hard drive) it is strange too. I don't know what can be the latency (aka systematic delay) that this kind of management can produce. In my case the M1xx execution should be as fast as possible same as M66 (in my case M66 P0 L3 Q1).
Alex On Sat, Sep 13, 2014 at 6:07 PM, Jon Elson <el...@pico-systems.com> wrote: > On 09/13/2014 02:56 AM, alex chiosso wrote: > > When I load or reload the NC program into Axis UI the interpreter is > > scanning the NC file and detecting also the internal (subroutine) calls > to > > custom M1xx codes. > > But what I can see is that when NC program is running LCNC is always > > accessing to the hard drive with a frequency very similar to the dynamic > > path calculation and machine movements. > > > It is the M1xx functions that cause the disk access. These > are essentially > subroutines that are fetched from disk every time they are > called. > Disk caching may help speed that up, but maybe that is > disabled to > make sure the M100 function is refreshed every time it is > called. > > Jon > > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
