Ok, thanks for your help (Chris too), I seem to have it working now. In the ini file I have AXES = 8 COORDINATES = X Y U V HOME = 0 0 0 0
And [AXIS_6] and [AXIS_7] sections instead of the 2 and 3 I had before. And in my "core_foam_stepper.hal" I changed all refences to "axis.[23]...." to "axis.[67]...." etc. And of course I updated the references to the [AXIS_x] parts of the ini file to match the new settings. and I left all the "stepgen.[23]" references as they where. Axis now loads up and I can jog XYUV and they all work. (I am not at the machine at the moment but the front end seems to be doing the right thing). A question about feed rates. From the quick testing I have just done it looks like it always tries to apply the feed rate to the XY axes, and scales the feed rate for the UV to match so that they all reach their end point at the same time. Unless your feed rate at XY causes the UV to overrun the max, or any individual axis to overrun its max speed, then the XY is scaled down until UV are running at their max. Does this sound correct? Seems like the right thing to do to me. Just wanted to make sure that it is treating the XY and UV as two separate pairs from which to calculate 2 separate combined feed rates to apply the max. And I am assuming that the feed rate shown in the Axis display is always the feed rate for XY, and not some algorithmic combination of XY + UV or something. With any luck I will be cutting up some foam tonight. I need to hand code some g-code so that I can make a table of kerf width at different feed rates and wire temperatures. I am planning on cutting circles (cylinders) at different speeds, and then comparing the diameters to what the commanded diameters where. I am assuming that cutter compensation to handle a variable width kerf depending on feed rate, and applying it to 2 different sets of axes is not handled by standard g-code? So I am planning on incorporating it into my g-code generator. Ryan On Mon, 2007-08-20 at 15:01 -0500, Jeff Epler wrote: > On Mon, Aug 20, 2007 at 02:59:39PM -0500, Jeff Epler wrote: > > [TRAJ]AXES should probably be set to 8. Here's the explanation from the > > documentation: > > One more than the number of the highest joint number in the system. > > For an XYZ machine, the joints are numbered 0, 1 and 2; in this case > > AXES should be 3. For an XYUV machine using ``trivial kinematics'', > > the V joint is numbered 8 and therefore AXES should be 9. For a > > machine with nontrivial kinematics (e.g., scarakins) this will > > generally be the number of controlled joints. > > > > http://linuxcnc.org/docs/devel/html/config/ini_config/index.html#hue432 > > Just as I was posting this, another developer noticed that the > documentation was incorrect. The corrected text reads: > the V joint is numbered 7 and therefore AXES should be 8. > > I think the rest of what I said in my message is correct. > > Jeff > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
