On 20 May 2015 at 01:47, Christian Stöveken <[email protected]> wrote: > Also I don't like that the model scripts (python) don't use the parameters > from the LinucCNC config files, but instead need to be hardcoded and don't > reside in the machine config folder.
They could, and they can. There is nothing to prevent the Vismach script from reading data from the INI file, other Python scripts do using inifile.find http://www.linuxcnc.org/docs/html/common/python-interface.html#_reading_ini_file_values_a_id_sec_python_reading_ini_values_a You could argue that making the INI match the "hardware" is part of all configuration, the limits are very "hardcoded" when the machine is iron rather than pixels:-) The VMC + toolchanger I have been experimenting with here: http://www.linuxcnc.org/index.php/english/forum/24-hal-components/29153-vmc-related-hal-questions#58732 has the Vismach script and models in the config directory. It is just a matter of setting the paths. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
