Klemen Dovrtel wrote: > Hello, > > I also have a 4 axis hot wire cnc machine, and i have > the same problem as Ryan. I successfully set the > machine to xyza axes and it works fine, but I would > rudder have the correct setup xyuv. I set the .ini > files as described here, but i still get some errors. > > What version/release of EMC Ryan had? There was a > discussion at emc mirc channel, that emc release 1.7 > doesn't support xyuv setup and emc release 2.x (which > can be downloaded from cvs) will.
Close. The current release is "2.1.7", which does not have UVW. The latest version in CVS is "pre-2.2.0", which does have UVW. The next release will be "2.2.0", and will have UVW. EMC version numbers work like this: EMC 2.1.7 the 2 is for EMC2 the .1 is the major release number the .7 is the minor release number Minor releases are for bugfixes only, not for new features. Our criteria for minor releases is that users should not have to change their ini files or other configuration data to move from one minor release to the next. If 2.1.5 worked for you, you can use 2.1.6 or 2.1.7 without changing anything. You should always use the latest minor release (and if you are using Ubuntu you will get automatic updates to the latest minor release). Major releases add new features, and may not be 100% compatible with the previous major release. When there is incompatibility we describe the necessary configuration changes in the wiki. Changes to go from 2.0.x to 2.1.x: http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?UPDATING Changes to go from 2.1.x to the current CVS version: http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?UpdatingConfigurationsForDevelopmentVersions We try to avoid incompatibility between major releases as much as possible, but sometimes new features mean that something MUST change. You should update to a new major release only after considering the benefits of the new features versus any configuration changes that are needed. You will NOT be automatically updated from one major release to another - we leave that decision to you. Release history: "2.0.0" May 2006 - do not use, update to 2.0.5 or 2.1.7 "2.0.1" Jun 2006 - do not use, update to 2.0.5 or 2.1.7 "2.0.2" Aug 2006 - do not use, update to 2.0.5 or 2.1.7 "2.0.3" Aug 2006 - do not use, update to 2.0.5 or 2.1.7 "2.0.4" Oct 2006 - do not use, update to 2.0.5 or 2.1.7 "2.0.5" Dec 2006 - last 2.0 release - use it, or update to 2.1.7 "2.1.0" Jan 2007 - do not use - update to 2.1.7 "2.1.1" Feb 2007 - do not use - update to 2.1.7 "2.1.2" Mar 2007 - do not use - update to 2.1.7 "2.1.3" Mar 2007 - do not use - update to 2.1.7 "2.1.4" Mar 2007 - do not use - update to 2.1.7 "2.1.5" May 2007 - do not use - update to 2.1.7 "2.1.6" Jun 2007 - do not use - update to 2.1.7 "2.1.7" Jul 2007 - latest release, recommended for production machines "pre-2.2 CVS head" - latest unreleased version, new features (and probably new bugs), not recommended for production machines. Use it if you need the new features or want to help test out the latest code before it is released. Note: it is only a coincidence that all 2.0 releases were in 2006 and all 2.1 releases were in 2007. We hope to release 2.2.0 before the end of the year. Regards, John Kasunich ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
