Line 0 following error
25 Jul 2014 21:03 #49126
by skvallab
Line 0 following error was created by skvallab
When i set my maximum velocity over 75 mm /min . i get this error message.
how do i rectify this?
thanks in advance
vallab
how do i rectify this?
thanks in advance
vallab
Please Log in or Create an account to join the conversation.
25 Jul 2014 21:22 #49127
by PCW
Replied by PCW on topic Line 0 following error
Its a bit difficult to answer that question because you are not providing any background information.
Assuming you mean "joint following error" and also assuming you have a step/dir machine
this error often means you don't have the required headroom in the stepgen maxvel setting
(it should be about 25% greater than the machine max velocity for each axis)
It may also be that you have run in to the maximum velocity limits of your current step-time and step-space settings.
Assuming you mean "joint following error" and also assuming you have a step/dir machine
this error often means you don't have the required headroom in the stepgen maxvel setting
(it should be about 25% greater than the machine max velocity for each axis)
It may also be that you have run in to the maximum velocity limits of your current step-time and step-space settings.
The following user(s) said Thank You: skvallab
Please Log in or Create an account to join the conversation.
25 Jul 2014 21:43 - 25 Jul 2014 21:44 #49130
by skvallab
Replied by skvallab on topic Line 0 following error
yes it is joint following error.
i am using servo run by step and direction using pico univ stepper controller.
will try this and update
thanks
i am using servo run by step and direction using pico univ stepper controller.
will try this and update
thanks
Last edit: 25 Jul 2014 21:44 by skvallab.
Please Log in or Create an account to join the conversation.
28 Jul 2014 16:32 #49211
by skvallab
Replied by skvallab on topic Line 0 following error
I changed the following settings in ini configuration file.
still getting the same joint 0 following error.
& i couldnt find the stepgen_max_vel setting in the ini configuration.
where do i find that setting?
DEFAULT_VELOCITY=0.0167 (unchanged)
MAX_VELOCITY=25.20 (old value = 1.20)
DEFAULT_ACCELERATION =15.0(unchanged)
MAX_ACCELERATION =20.0 (unchaged)
AXIS 0
MAX_VELOCITY=15.20 (old value =1.20)
MAX_ACCELERATION=20.0 (unchanged)
PID_MAX_VEL=20.20 (old value = 1.25)
My max motor speed is 3000RPM, I set my scale as 1 rpm = 1mm linear movement.
so my max velocity = rpm directly.
i couldnt move the motor over 430 rpm
still getting the same joint 0 following error.
& i couldnt find the stepgen_max_vel setting in the ini configuration.
where do i find that setting?
DEFAULT_VELOCITY=0.0167 (unchanged)
MAX_VELOCITY=25.20 (old value = 1.20)
DEFAULT_ACCELERATION =15.0(unchanged)
MAX_ACCELERATION =20.0 (unchaged)
AXIS 0
MAX_VELOCITY=15.20 (old value =1.20)
MAX_ACCELERATION=20.0 (unchanged)
PID_MAX_VEL=20.20 (old value = 1.25)
My max motor speed is 3000RPM, I set my scale as 1 rpm = 1mm linear movement.
so my max velocity = rpm directly.
i couldnt move the motor over 430 rpm
Please Log in or Create an account to join the conversation.
29 Jul 2014 09:02 #49235
by jmelson
is an all electronic servo, where the encoder counter function is fed the step pulses, and
the PID component adjusts the step rate to zero out the error. If you are running in
open-loop mode (DIP switches 1-4 are OFF) then you may need to adjust the
P term in the .ini file to help the loop keep up. You can use Halscope to observe
signals ppmc.0.encoder.00.velocity and pid.0.error and see how your adjustments
improve the response. The calibration menu allows you to adjust the parameters
while LinuxCNC is running. If you have problems, I can run your settings here
and then send you back optimized values.
If you are reading your encoders back to the USC (switches 1-4 would be ON)
then you are having your servo motors lag behind your commanded position.
Again, Halscope is the tool you need to see what is happening. I have a Wiki
page that can be helpful in tuning the servo response.
Jon
Replied by jmelson on topic Line 0 following error
Oh, that gets a bit more complex. The universal stepper controller in the open-loop modeyes it is joint following error.
i am using servo run by step and direction using pico univ stepper controller.
will try this and update
thanks
is an all electronic servo, where the encoder counter function is fed the step pulses, and
the PID component adjusts the step rate to zero out the error. If you are running in
open-loop mode (DIP switches 1-4 are OFF) then you may need to adjust the
P term in the .ini file to help the loop keep up. You can use Halscope to observe
signals ppmc.0.encoder.00.velocity and pid.0.error and see how your adjustments
improve the response. The calibration menu allows you to adjust the parameters
while LinuxCNC is running. If you have problems, I can run your settings here
and then send you back optimized values.
If you are reading your encoders back to the USC (switches 1-4 would be ON)
then you are having your servo motors lag behind your commanded position.
Again, Halscope is the tool you need to see what is happening. I have a Wiki
page that can be helpful in tuning the servo response.
Jon
The following user(s) said Thank You: skvallab
Please Log in or Create an account to join the conversation.
30 Jul 2014 17:43 - 30 Jul 2014 17:46 #49284
by skvallab
Replied by skvallab on topic Line 0 following error
thank you so much jon for your offer.
i am attaching my univstep.ini file with this post
and pics of error messages.
and servo pulse input screenshot
regards
vallab
i am attaching my univstep.ini file with this post
and pics of error messages.
and servo pulse input screenshot
regards
vallab
Last edit: 30 Jul 2014 17:46 by skvallab.
Please Log in or Create an account to join the conversation.
31 Jul 2014 10:53 #49321
by jmelson
P = 2000
I = 1
D = 0.25
FF1 = 0.98
FF2 = 0.0002
Deadband = 0.00005
These are for a scale of 10000, the numbers might have to change if you change that scale
factor.
Jon
Replied by jmelson on topic Line 0 following error
here are some PID settings that looked very good.thank you so much jon for your offer.
i am attaching my univstep.ini file with this post
P = 2000
I = 1
D = 0.25
FF1 = 0.98
FF2 = 0.0002
Deadband = 0.00005
These are for a scale of 10000, the numbers might have to change if you change that scale
factor.
Jon
The following user(s) said Thank You: skvallab
Please Log in or Create an account to join the conversation.
31 Jul 2014 14:09 - 31 Jul 2014 14:17 #49325
by skvallab
Replied by skvallab on topic Line 0 following error
Getting joint 3 following error. I am not using that axis.
what might be the reason. i suspect EMI problem.
If i set P =2000
i am getting the joint following error at the start.
reduced it to 200 it is working ok.
getting occasional errors though.
regards
vallab
what might be the reason. i suspect EMI problem.
If i set P =2000
i am getting the joint following error at the start.
reduced it to 200 it is working ok.
getting occasional errors though.
regards
vallab
Last edit: 31 Jul 2014 14:17 by skvallab.
Please Log in or Create an account to join the conversation.
31 Jul 2014 21:59 #49352
by jmelson
You would have to go through all the .hal files and remove anything that refers
to the 4th axis. But, a quick fix would be to set the MIN_FERROR on that axis
to a large number, like 1000.
You can also turn up the value of MIN_FERROR, it is currently set to .001, which is
pretty small in mm units.
Replied by jmelson on topic Line 0 following error
If you are not using the A axis, then you ought to remove it from the configuration.Getting joint 3 following error. I am not using that axis.
what might be the reason. i suspect EMI problem.
You would have to go through all the .hal files and remove anything that refers
to the 4th axis. But, a quick fix would be to set the MIN_FERROR on that axis
to a large number, like 1000.
You need to learn how to use Halscope to view what is happening as you move the axes.
If i set P =2000
i am getting the joint following error at the start.
reduced it to 200 it is working ok.
You can also turn up the value of MIN_FERROR, it is currently set to .001, which is
pretty small in mm units.
getting occasional errors though.
regards
vallab
The following user(s) said Thank You: skvallab
Please Log in or Create an account to join the conversation.
Time to create page: 0.174 seconds