Okay, I admit some serious problems in the "vesa" display driver which was
loaded by default. Like: if you switched between tty1 and tty2 small delay
of ~5000ns could be introduced, but switching from tty1 to tty7 to graphical
interface induced ~340000 nanoseconds delay each time during CRT monitor
resync period. UGLY! I tried to install nvidia-glx with no luck, but at
least I got the MAGMA driver "nv" working and the delays are lower than
ever. Only simultaneous launching of 3 firefoxes and started loading of 3
different web pages on a slow internet line could bring it to knees od 19337
ns. (Solar winds screensaver preview still running and loading CPU to 100%
already).
But the FEED OVERRIDE problem still remained. Jumping the slider left and
right resulted in time between calls to motion controller of 0.957ms, 1ms,
1ms, 1ms, 1ms and last one 1.053ms. If you change CPU speed it still keeps
the time :-)
That was true for the canon-presny.ini setup. With the setup file
canon-volny.ini I had to move the Jog Speed slider up to cause the error. It
occured at less that 50% of allowed joint movement speed.
Possible explanation: asynchronous updating of variables?
On 12/25/06, Mario. < [EMAIL PROTECTED]> wrote:
Emmm, thinking about it. I dont't think the graphics generate anything
with exactly one milisecond. And the drawing in AXIS runs just fine, it only
happens when the value above the slider actually changes. I have to ask: did
any of you get that attachment I have sent yesterday? This problem MAY have
something to do with my high requirements as is in the INI file.
On 12/25/06, Jon Elson < [EMAIL PROTECTED]> wrote:
>
> Jeff Epler wrote:
>
> >Moving the "feed override" slider does not modify the 'period' of the
> >HAL functions. 'period' is the approximate number of ns between
> >invocations of a realtime thread, and does not change during an emc2
> >run.
> >
> >
> >
> That's what made me think it has to do with updating the screen. RTAI
> should
> have priority over the grapics driver UNLESS the driver is disabling
> interrupts
> during some critical code sections. Ghastly if they are disabling ints
> for a
> millisecond!
>
> I wonder if forcing X to use a default VGA driver might cause it to act
> differently?
>
> Jon
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
>
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
