On 8/12/2013 10:58 AM, Gene Heskett wrote: > That said, even with the latest 2.5.3, I see a realtime error advisory, but > it may not show up until the next day of uptime for LCNC itself. And I > have never detected that the machine itself, if in motion at the time, was > ever affected.
I've had these on both x86 and on the ARM, and in both instances they appear to be harmless. It seems that LinuxCNC considers any latency over 25.000 uS to be a real-time error, but I expect latencies worse than that using Preempt-RT (x85) and Xenomai on the ARM. LinuxCNC can operate just fine with these errors (worst case is 50-75 uS or so, which is fine for running a 1mS servo thread). So far it hasn't been enough of a nuisance for me to crawl through the code and figure out how to change the warning to a different threshold. Anyone know how to do this? I *WOULD* like to see errors reported if latency was over about 80 uS or so, but don't know what configuration setting (or chunk of code?) to change. -- Charles Steinkuehler char...@steinkuehler.net
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
