A little help understanding what's going on with the pncconf wizard...

More
3 years 1 month ago #281658 by cmorley
see my advice above.

units in Pncconf are in per minute
units in the INI are per second
960 Inches per minute = 16 inches per second x 60 seconds

Pncconf writes the INI from your selections.
Pncconf defaults to 60 inches a minute (if you are using imperial, something close in metric) which is 1 inch per second.

Please Log in or Create an account to join the conversation.

More
3 years 1 month ago #281662 by Sparkman61

units in Pncconf are in per minute
units in the INI are per second
960 Inches per minute = 16 inches per second x 60 seconds

Thank you! I clearly missed that in my previous. I'll give it a try and see where I'm at. I am less certain about the follow error I am seeing when jogging. Any thoughts?

Please Log in or Create an account to join the conversation.

More
3 years 1 month ago #281663 by cmorley
I don't see anything obvious for following error but wait till others look = Peter is pretty good at spotting that stuff.

I missed that your X axis max velocity is 66 per second - so the numbers I quoted will still limit that axis in jogging. The same principles apply to change it further.

Hold out ! you will get there :)

Please Log in or Create an account to join the conversation.

More
3 years 1 month ago #281665 by PCW
I don't see anything obvious in the hal/ini files that would
cause a following error.

What joint(s) get following errors?

Please Log in or Create an account to join the conversation.

More
3 years 1 month ago #281689 by Sparkman61
I was getting the following errors mainly on the synced Y, although I also got it on the X during a couple of tests. I've' been playing with this thing most of the evening and am still not happy with the way it is running. I have a configuration that I am more comfortable with than I was before but... (there's always a "but") I am suspicious that the little mini pc that I am running this on may have some issues. I have noticed that after a certain number of times running, stopping, running linuxcnc to test, the performance starts to degrade. A restart of the pc helps but I don't know that I trust this OS install (done way back in May). I am tempted to wipe it and start from scratch - I remember getting it running was a bit of a pain (at the time) and I read elsewhere on this forum that there is a bookworm distro that may be easier to get working that what I went through. On the other hand, it is (mostly) stabile. Maybe I need to dig into stepper tuning further?

I guess I am still unsure about this being a good enough baseline before moving on to Qtplasmac? I guess for starters, I'm going to make a backup of the system so at least I have a starting point if I screw something up badly.

Please Log in or Create an account to join the conversation.

More
3 years 1 month ago #281730 by PCW
I don't understand why you are getting following errors, especially with such
huge limits (0.5" and 0.05")

I would plot the commanded position, commanded velocity and following error
and perhaps trigger on  errored with halscope to try and diagnose the issue.

That is plot

joint.0.motor-pos-cmd
joint.0.f-error
joint.0.vel-cmd

and trigger on

joint.0.f-errored

Please Log in or Create an account to join the conversation.

Moderators: cmorley
Time to create page: 0.181 seconds
Powered by Kunena Forum