Gregg :
thanks for the detailed answer .
I'm understanding something more about the LCNC work process.
I did believed that the realtime kernel was invoked also in simulation mode
and I was wrong.
My believed was that due to the hal files processing (not for the postgui
hal files) the realtime was always working doesn't matter if you are
running on real hardware or sim .

Jon:
The NC program I'm testing have a main body with the call to o<named>
subroutine with 4 parameter called 4 times with different input parameter
values.
Inside the parametric subroutine there is a runtime calculating path for
the machine axis mvements.
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.
My personal and poor opinion is that this is "strange" anyway.
First because the NC program is small .
Secondary this approach (if it is still present on a running machine using
the real time kernel) slow down the block to block processing speed.

If I'm doing something wrong , please help me to understand .

Alex




On Sat, Sep 13, 2014 at 4:18 AM, Jon Elson <el...@pico-systems.com> wrote:

> On 09/12/2014 12:03 PM, alex chiosso wrote:
> > Hi Jon.
> > Thank you for the replay .
> > The part program is not so big (120 lines code , it is parametric style
> > with Named Parameters) so it is strange .
> > It is clear now the cpu hogg.
> > I did believe that the real time is always enabled also in sim mode.
> > Maybe this is why the hal file execution seems to have a sort of latency.
> > Can you explain me why only a part of the NC program is loaded (as you
> say
> > "only few K bytes"), what is the bottle neck ?
> >
> No, for a very small program, it WILL all be loaded into memory.
> Remember, this is not a dedicated CNC computer, this is a
> multi-user,
> multi-tasking, general purpose operating system.  At the command
> prompt, do :
> ps xa
> and you will be AMAZED to see how many tasks are running, I
> see 164 on my system.  All real-time parts of LinuxCNC are
> locked in memory when they start, but in the sim version, they
> are all capable of being swapped out, or causing page faults.
> The non-real time part of LinuxCNC is always capable of being
> swapped or paged.
>
> 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

Reply via email to