On 10/15/2011 9:46 PM, Peter C. Wallace wrote: > On Sat, 15 Oct 2011, Tom Easterday wrote: > > >> Date: Sat, 15 Oct 2011 20:53:44 -0400 >> From: Tom Easterday<tom-...@bgp.nu> >> Reply-To: "Enhanced Machine Controller (EMC)" >> <emc-users@lists.sourceforge.net> >> To: "Enhanced Machine Controller (EMC)"<emc-users@lists.sourceforge.net> >> Subject: Re: [Emc-users] config without encoders >> >> >> On Oct 15, 2011, at 8:46 PM, Peter C. Wallace wrote: >> >>> I would check carefully that you do not have something, likely a velocity or >>> steplen/stepspace setting that limits the maximum stepgen speed. >>> >>> at your scale and speed you have a fairly slow step rate (82 KHz) which is >>> less than 1% of the step generators maximum speed (12.5 MHz) so the >>> ghardware >>> is not the limiting factor, some setup option must be set incorrectly >>> >> Here is the ini file settings that we have currently. Peter (who is working >> with me) is going to try setting steplen and stepspace up a little higher to >> see if that helps. He thinks he already tried that but will do it again to >> be sure... >> > > Setting steplen or stepspace longer can only make the stepgens maximum > velocity _lower_ not higher, so that cannot help (unless you have an interface > speed problem but this would not show up as a following error but rather as > missed steps) > > Following errors in a pure open loop step generator system mean that something > is limiting the driver code from setting a high enough velocity in the > step generator hardware. Maybe something has been omitted causing a scale > error so you have a un-obvious velocity limit. > > > > > >> #******************** >> # Axis Y (Y1) >> #******************** >> [AXIS_1] >> NAME = Y1 >> TYPE = LINEAR >> HOME = 0.0 >> HOME_SEQUENCE = 0 >> FERROR = 0.5 >> MIN_FERROR = 0.5 >> MAX_VELOCITY = 39 >> MAX_ACCELERATION = 120 >> #STEPGEN_MAXACCEL = 220 >> #MAX_ACCELERATION = 10 >> #STEPGEN_MAXACCEL = 30 >> #Encoder/PID >> P=0.0 >> I=0.0 >> D=0.0 >> FF0=0.0 >> FF1=1.0 >> FF2=0.0 >> BIAS=0.0 >> DEADBAND=0.0 >> MAX_OUTPUT=0 >> # these are in nanoseconds >> DIRSETUP = 200 >> DIRHOLD = 200 >> STEPLEN = 200 >> STEPSPACE = 200 >> #500 encoder ppr (2000 quad) >> #SCALE = -1273.239544735163 >> #INPUT_SCALE = -1273.239544735163 >> #1000 encoder ppr (4000 quad) >> #SCALE = 2546.479089470325 >> #INPUT_SCALE = 2546.479089470325 >> #10x after setting Granite to 10:1 ratio >> SCALE = 25464.79089470325 >> INPUT_SCALE = 25464.79089470325 >> MIN_LIMIT = -0.01 >> MAX_LIMIT = 53.0 >> HOME_OFFSET = 0.0 >> >> ------------------------------------------------------------------------------ >> 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 >> >> > Peter Wallace > Mesa Electronics > > (\__/) > (='.'=) This is Bunny. Copy and paste bunny into your > (")_(") signature to help him gain world domination. > > Peter,
Is there any reason not to open up the stepgen limits on accel and velocity so they cannot possibly be a limiting factor? Make them 1.0EE6 or so? Dave ------------------------------------------------------------------------------ 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
