Peter;
I had to do an is_inverted to the 2 gpio's that were stepgen 3's outputs.
But the waveform indicates its open drain, so the off, top of the
waveform is being left open to get back to high, taking several tens of
microseconds. Is there something I can put into hal file to restore the
act
On Saturday 12 September 2015 01:39:46 TJoseph Powderly wrote:
> On 09/11/2015 10:50 PM, Gene Heskett wrote:
>
>
> > I was feathered, sorta resembling a chicken, so I called in a scale
> > module, which once configured worked really well.
> >
> > But in the 2.8.0-pre's I have a bitch, a loud one.
On 09/11/2015 10:50 PM, Gene Heskett wrote:
>
> I was feathered, sorta resembling a chicken, so I called in a scale
> module, which once configured worked really well.
>
> But in the 2.8.0-pre's I have a bitch, a loud one. The halmeter is shown
> forground for as long as it exists, and that is ni
On Friday 11 September 2015 10:01:34 TJoseph Powderly wrote:
> On 09/11/2015 03:59 AM, andy pugh wrote:
> > On 11 September 2015 at 05:33, Gene Heskett
wrote:
> >> One hopefully last question then Andy, can hal or axis do the math
> >> such that there is one master place to specify this "scale",
On 09/11/2015 03:59 AM, andy pugh wrote:
> On 11 September 2015 at 05:33, Gene Heskett wrote:
>> One hopefully last question then Andy, can hal or axis do the math such
>> that there is one master place to specify this "scale", and set the
>> pid's maxoutput to 0.98 * scale?
>
>
> No, but yes.
>
>
On Friday 11 September 2015 04:59:55 andy pugh wrote:
> On 11 September 2015 at 05:33, Gene Heskett wrote:
> > One hopefully last question then Andy, can hal or axis do the math
> > such that there is one master place to specify this "scale", and set
> > the pid's maxoutput to 0.98 * scale?
>
> N
On 11 September 2015 at 05:33, Gene Heskett wrote:
> One hopefully last question then Andy, can hal or axis do the math such
> that there is one master place to specify this "scale", and set the
> pid's maxoutput to 0.98 * scale?
No, but yes.
Mathematical expressions are not allowed in a HAL fi
On Thursday 10 September 2015 22:10:50 Gene Heskett wrote:
> On Thursday 10 September 2015 20:46:50 andy pugh wrote:
> > On 11 September 2015 at 01:44, andy pugh wrote:
> > > I think you should use RPM all the way to the pwmgen and limit the
> > > pid to 98% of the pwmgen.scale
> >
> > Actually,
On Thursday 10 September 2015 20:46:50 andy pugh wrote:
> On 11 September 2015 at 01:44, andy pugh wrote:
> > I think you should use RPM all the way to the pwmgen and limit the
> > pid to 98% of the pwmgen.scale
>
> Actually, given that encoder velocity is returned in RPS then use RPS
> all the w
On 11 September 2015 at 01:44, andy pugh wrote:
> I think you should use RPM all the way to the pwmgen and limit the pid
> to 98% of the pwmgen.scale
Actually, given that encoder velocity is returned in RPS then use RPS
all the way, from motion.spindle-speed-out-rps all the way through the
pid to
On 11 September 2015 at 00:56, Gene Heskett wrote:
> So if I am using a scale factor there, to tame the axis big jumps when
> clicking on the + and - buttons, it seems to me that the value I apply
> to a limit2 in front of your 5i25 pwmgen should also be scaled up by
> this same scale factor.
I t
Peter;
I am attempting to setup a new control chain for my lathes spindle. One
that will be a bunch simpler in the hal file.
The 5i25's pwmgen actually has a duty cycle range from about 1% to 98% of
so.
So if I am using a scale factor there, to tame the axis big jumps when
clicking on the +
12 matches
Mail list logo
