After a 'few' more hours, we have got quite a bit further with getting the system running. Basically we scrapped PNCConfig and started editing the files directly.
We set all the velocities, accelerations, following errors to huge values so the system would run and then we started tweaking the values to get to control it. Basically, the Copley drives and LinuxCNC and low interia drives and no velocity feedback don't work. The drive output is too rapid for LinuxCNC to follow. On moving from say 0 to 40 mm, the motor basically sawtooths till it gets to the final position. PS We now learned to use the halscope which makes measurement much easier. Ok So what we need to do now is trim the velocities, acc, errors etc on the run to get the best results. The feed rate on the screen and the PID is great but we need to get access to the balance of the INI bits. Opening and closing LinuxCNC with each mod is just too slow. Doing it real time is great. Can this be done ? Thanks Wallace ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
