After several hours of trying to make Spindle-at-speed work as set up with stepconfig I finally figured out that the custom_postgui.hal file that stepconfig builds has a built-in error. The file compares spindle velocity before scaling and before the absolute value is taken with the spindle commanded speed which is in filtered absolute rpms. This will of course only result in a spindle-at-speed signal when both the command and the velocity are at zero.
The fix is shown below. You need to delete or comment out the spindle-velocity input to near.0.in2 and replace it with spindle-fb-filtered-abs-rpm so that the values being compared are in the same units. I hope this helps anyone trying to make the spindle-at-speed signal work. Cecil Gedit the custom_postgui.hal file thusly: # **** set up spindle at speed indicator **** net spindle-cmd => near.0.in1 #****DELETE or COMMENT OUT THIS LINE!!!! #net spindle-velocity => near.0.in2 #*****USE THIS LINE INSTEAD!!!!!!! net spindle-fb-filtered-abs-rpm => near.0.in2 net spindle-at-speed <= near.0.out setp near.0.scale 1.500000 net spindle-at-speed => pyvcp.spindle-at-speed-led ------------------------------------------------------------------------------ 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_mar _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
