Mario. wrote: >It is not dependent on CPU frequency, at 1600MHz, dmesg reports that >at least the last 6 interrupts took ~1600000 cycles, and at 1920MHz >CPU frequency it reports 1759264 to 2099646 cycles between calls to >the motion controller. I did this mostly in AXIS, but it happened in >the other interface too. > > > I don't use axis much, but I don't think this has anything to do with which GUI you use. Since this RT monitoring has been put into EMC, I have seen the message pop up occasionally on two Dell systems with modest CPUs in the 600-666 MHz range. I don't think it has anything to do with raw CPU speed.
One interesting observation is if I run EMC remotely through an SSH session, I get a LOT of these messages. That leads me to think that some ethernet interfaces may cause this problem, by tying up memory. Both of these systems have the I 810 chipset, I think. I am not using Ubuntu, but a system derived from Paul Corner's BDI 4.30 >It is almost instant with the slower CPU configuration, you jut move >the slider 5% up or down and he message pops. > > > That sounds a LOT like it is related to the screen updates. 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
