Base Period Jitter Manual Changes (without StepConf)

More
20 Jul 2021 13:42 #215414 by fernandosf
Hey Guys,
 
I'm trying to understand how to setup Base Jitter manually on LinuxCNC files.
First thing done was to change a test config using StepConf and see the differences generated.
StepConf has a box called Base Period Max Jitter, it was the only config changed.
I got this:
$ diff my-mill.stepconf my-mill2.stepconf
37c37
<   <property name="latency" type="float" value="30000.0"/>
---
>   <property name="latency" type="float" value="10000.0"/>
$ diff my-mill/my-mill.hal my-mill2/my-mill.hal
1c1
< # Generated by stepconf 1.1 at Tue Jul 20 09:27:06 2021
---
> # Generated by stepconf 1.1 at Tue Jul 20 09:26:14 2021
57,58c57,58
< setp stepgen.0.dirhold 50000
< setp stepgen.0.dirsetup 50000
---
> setp stepgen.0.dirhold 30000
> setp stepgen.0.dirsetup 30000
69,70c69,70
< setp stepgen.1.dirhold 50000
< setp stepgen.1.dirsetup 50000
---
> setp stepgen.1.dirhold 30000
> setp stepgen.1.dirsetup 30000
81,82c81,82
< setp stepgen.2.dirhold 50000
< setp stepgen.2.dirsetup 50000
---
> setp stepgen.2.dirhold 30000
> setp stepgen.2.dirsetup 30000
$ diff my-mill/my-mill.ini my-mill2/my-mill.ini
1c1
< # Generated by stepconf 1.1 at Tue Jul 20 09:27:06 2021
---
> # Generated by stepconf 1.1 at Tue Jul 20 09:26:14 2021

So when Base Jitter is 10.000, StepConf changes dirhold and dirsetup to 30.000
Changing Base Jitter to 30.000, StepConf changes dirhold and dirsetup to 50.000

That's it? Or am I missing something?

I have DM556 Drivers and had found a minimum value of 10.000 and 5.000 for dirhold/dirsetup that worked.
But I had no idea that it was the only config related to Base Jitter and I am afraid I can face strange errors in the future.

Please, advise, thanks.
 

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

More
21 Jul 2021 09:00 #215466 by tommylight
Stepconf is meant to make a usable config, and it does that perfectly.
For changing the timings and fine tuning, editing the .hal and .ini files in the config filder is the way to go.
In the ini file there will be
-base period - set this depending on the jitter value plus 50% to be on the safe side
-step time and step space- set this to 5000 and lower it gradually to where you are sure there are no missed steps from the drives, forget what drive manufacturers say about this
-dir setup and dir hold- set this to 20000, it does not matter much if you go lower or higher, but to low can cause very strange missed steps
The following user(s) said Thank You: DougM, fernandosf

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

More
21 Jul 2021 17:45 #215509 by fernandosf
Thanks tommylight, looks like experienced advise.
It intrigues me why Stepconf did not changed anything else besides dirhold and dirstep.
But life goes on...
The following user(s) said Thank You: tommylight

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

More
22 Jul 2021 00:45 #215541 by BigJohnT
Stepconf does have some limits and once you get a basic configuration editing the files is the way to go.

JT

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

More
08 Aug 2021 14:36 #217237 by fernandosf
Hey Guys,
I have searched DM-556 timings and read about DoubleStep (I'm using parport).
So I added a 10% margin and set INI and HAL accordingly.
But, somehow, stepgen values are set to 60000 (which is the setting I've defined for BASE_PERIOD)

I was expecting dirsetup, dirhold and steplen to be the ones I defined.
Can someone explain why LinuxCNC is not following my settings? 

Attachments:

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

More
08 Aug 2021 15:39 #217246 by fernandosf
Following TommyLight advice above, does not seem to get any better:
 
Attachments:

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

More
11 Aug 2021 00:17 - 11 Aug 2021 00:18 #217446 by andypugh
There is no advantage in having dirhold and dirsetup short. The machine is by definition moving at zero speed at that point.

If you want shorter step lengths, then edit the INI file.

The chances are that the max speeds that you have configured mean that Stepconf sees no need to use a short step length, as the max required step rate can be achieved without. 
 
Last edit: 11 Aug 2021 00:18 by andypugh.
The following user(s) said Thank You: fernandosf

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

More
13 Aug 2021 13:58 #217679 by fernandosf

The chances are that the max speeds that you have configured mean that Stepconf sees no need to use a short step length, as the max required step rate can be achieved without. 

Absolutely convinced LinuxCNC programmers are way more intelligent than me 

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

Time to create page: 0.110 seconds
Powered by Kunena Forum