I re-checked and I have the same values for speed and acceleration in joints and axes. The thing that was limiting my velocity was the OFFSET_AV_RATIO entry. I had it near 0.9 and once I homed the axis started to cause the effect. Reducing it to 0.1 solved the problem. If I don't remember wrong this happened with and without the eoffset enabled. I'll check it again in a few moments.
I planned to start the conversion but due to the quarantine that started today here in Argentina I'll have to wait at least until March 31st. :( Anyway... In the meantime I'll be testing and polishing all the config so it's more or less plug and play when we install the new hardware. Thanks as always guys! El mié., 18 mar. 2020 20:04, Jon Elson <el...@pico-systems.com> escribió: > On 03/18/2020 02:14 PM, Gene Heskett wrote: > > > > I'm in that same boat Jon, but its axis and joint settings that it forces > > me to match or its showstopper exit at init time. I have wondered but > > haven't asked why it doesn't do away with the axis setting and use he > > joint for everything. But in that regard, I'm a big dummy. > > > > > In trivial kinematics systems (lathes and mills) there is an > exact concordance between axes and joints. > In other systems (hexapods, SCARA and delta machines, for > instance) axes are orthogonal, but joints > can be any combination of swivels and linear components. On > those, you need different limits on > each. > > Jon > > > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
