>________________________________________ >From: andy pugh [bodge...@gmail.com] >Sent: Friday, February 01, 2013 7:17 PM >To: EMC developers >Subject: Re: [Emc-developers] Python Library for the BeagleBone PRUSS
[snip] >The point is that LinuxCNC as it currently exists handles hardware >physical limitations internally. What this means is that the >millisecond-by-millisecond servo-thread position updates match the >programmed velocity and (especially) acceleration limits of the >hardware. Any jitter in the position updates due to the update not >being on-schedule is likely to lead to a physical F=ma type problem. What's a typical hardware configuration for LinuxCNC then? I see a lot of mention of x86 Atom machines being used. How are you interfacing LinuxCNC with high powered MOSFETs to drive servos for example, especially if USB is not an option? ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers