So, what the problem was: 1) I made a new computer and a fresh install Ubuntu 6.06LTS, +EMC2.0.5, +axis 2) The Geforce 6100 VGA was installed as vesa in xorg.conf 3) When I changed the VGA to GeForce 7300 GT, all problems/features remained exactly the same. 4) Meanwhile... I made 2 new setup configurations (canon.ini), all went OK 5) I discovered a bug: when trying to move the slider of Feed Override to even 105%, I got message "Unexpected realtime delays, check dmesg for...." Tried tkemc and axis - same results. 6) dmesg said that there were numerous delays of about (recalculated) 1 milisecond 7) I changed processor frequency up/down - the delay and bug remained the same - 1 milisecond...
8) When changed the video driver to "nv" for magma core, deleted many useless input devices in xorg.conf, the bug is much, much harder to cause. Two minutes playing with the slider and system loaded to 100% by other applications. I suspect that the bug *could* be caused by issuing too many feed override commands in short time. Will try this... Chenge servo period to some long time... On 12/26/06, Alex Joni <[EMAIL PROTECTED]> wrote: > > > Hello Mario, > > I still don't think I understand your problem. > I've been reading through all your emails (at least the ones I have), and it > seems like one email at least got lost. > There is no email describing what the actual problem is. Sure you talk about > 1ms something.. but it's not clear at all what the problem is. > > Regarding the 1msec, I see you have the SERVO_PERIOD set to 1000000 nsec = > 1msec > So any change you send to the motion controller would happen at 1msec > (including the feed override changes). > > Maybe try again (from the beginning, and with assuming we know nothing) to > explain what exactly the problem is, and what you are doing to show it. > > Regards, > Alex > > PS: when you move the slider (either AXIS or tkemx, or any other GUI), a NML > message gets composed then sent to task (emctask), this one queues it, and > when it's ok it send it to the motion controller, which sets the new value > by calling a TP specific function. > The other way (display of the current feed override) happens by means of the > status structure, and later on with a NML status message. > There is _absolutely no way_ the moving of the slider per se to cause the > glitch (if that's what your problem is). What can be, and I am not ruling it > out, is a problem when applying the new feed_override in TP, maybe some > accel which is too high, and causes motors to stall (if your setting of 450 > mm/s^2 is not appropriate). I also notice you have some BACKLASH configure > in there, might want to take that out during testing (to rule out every > possible cause of problems). > > ------------------------------------------------------------------------- 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
