I should probably give some background to this. I have some macros that perform common lathe operations: https://forum.linuxcnc.org/forum/41-guis/26550-lathe-macros
The "Go" button in the macros is a GladeVCP Action Widget: http://linuxcnc.org/docs/2.7/html/gui/gladevcp.html#_vcp_action_widgets which is set up to issue O<turning> CALL [a] [b] [c] [d]... In this case the parameters passed to the O-word sub are filled in by a substitution scheme, and the actual MDI command is O<turning> CALL [${turn.x-f}] [${turn.sf-f}] [${turn.cut-f}] [${turn.feed-f}] [${turn.z-f}] [${turn.rad-f}] [${turn.angle-f}] [${turn.tool-s}] where the ${hallpin} substitutes the actual current value of a HAL pin, in this case the value of one of the spinboxes in the GUI. For some reason not well understood by me, setting the taper angle of the turning tab to a non-zero value then setting it back to zero puts a value on the HAL pin that the Python handler chooses to format in an exponent notation. So: The value can be any value that can be held on a HAL pin. At this point in time it can only be a numeric value. The value is passed as a parameter to a G-code subroutine. At the moment this can only ever be a floating-point representation. No human will ever see the string that is passed. So, I think that it probably makes sense to pass the full 17 decimal digits that are representable in decimal format of a double-precision. -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1916 ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
