Dual bipod winch foam cutter

bvandiepenbos wrote:

aaaggghh, I am more confused than ever..
seems steplen is always 1, stepspace is always 0
I entered 1000 in stepconf, so how was 3600 calculated

What is your base period?
If the step length is less than the base period, then there is no point worrying about the exact number.

Though I am a bit surprised, because I thought that "reset" needed a real time.

I don't suppose you might be putting in timings in uS rather than nS (I am not too sure what is needed)

bvandiepenbos wrote:

I am still confused.

I have been looking at the stepgen source, and I am now a little less confused.
git.linuxcnc.org/gitweb?p=emc2.git;a=blo...1742086cfbb5;hb=HEAD
Line 709 onwards.

Basically stepgen chooses a base period such that the period is long enough to not need more than one thread period per step. This makes sense, as the base period can be adjusted to nanoseconds, whereas if you are using multiple thread periods per step the resolution is in tens of uS. Whilst step_time is nominally in nS, setting it to 1 just means that it is set high when stepgen runs and there is a step request, and then low next thread execution.
In practice actual step time isn't set by the stepgen step_len parameter, but by the parport reset_time parameter. There is a function of the parport driver where a programmable time after setting the pins to the new configuration it sets pins in the reset mask back to zero. stepconf uses this (line 805) as it means you can have double the step rate.

The setup and hold time parameters are calculated in line 719/720 and seem to be the number you put in the boxes + the latency you put in the latency box. Does that fit?