On Oct 17, 2011, at 3:41 PM, andy pugh wrote: > On 17 October 2011 20:12, Tom Easterday <tom-...@bgp.nu> wrote: >> I take this all back. This doesn't seem to work. I am not sure what I was >> seeing last night, but it was late. I just tried this again and I can't get >> it to use these values if I name them anything other than MAX_ACCELERATION >> (and MAX_VELOCITY). > > You need both the MAX_ACCELERATION and MAX_VELOCITY in the INI file > section. You can also add other tags, such as your MMAX_ACELLERATION, > and use them in the .hal file. > > You do still need the MAX_ACCELERATION and MAX_VELOCITY in the .ini > file, as other parts of EMC2 use those.
So, I assume you are saying I would need something like below. It does seem to work, though (unfortunately) it makes no improvement in the issue at hand... .hal setp hm2_7i43.0.stepgen.01.maxaccel [AXIS_1]MMAX_ACCELERATION setp hm2_7i43.0.stepgen.01.maxvel [AXIS_1]MMAX_VELOCITY .ini #******************** # Axis Y (Y1) #******************** [AXIS_1] MAX_VELOCITY = 75 MAX_ACCELERATION = 360 MMAX_VELOCITY = 75 MMAX_ACCELERATION = 360 ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
