On Wed, 2 Feb 2011 21:08:09 -0800 (PST)
"Peter C. Wallace" wrote:
> It was pretty surprising. I was using Matt Shavers velocity mode test
> hal file with halrun, so the effect was not masked by a FE as it
> would be under EMC. If we had any integral gain and put enough load
> on the motor that it
On Thu, 3 Feb 2011, Matt Shaver wrote:
> Date: Thu, 3 Feb 2011 13:18:03 -0500
> From: Matt Shaver
> Reply-To: EMC developers
> To: emc-developers@lists.sourceforge.net
> Cc: d...@smithy.com
> Subject: Re: [Emc-developers] pid bug
>
> On Wed, 2 Feb 2011 21:08:09 -0800 (PST)
> "Peter C. Wallace"
On Wed, Feb 02, 2011 at 07:58:56AM -0800, Kirk Wallace wrote:
> Should a parallel port comp claim and release a port(s) with parport?
> Usually the port addresses are assigned manually to each comp so claim
> jumping should not be a problem?
Ideally, you'd use the routines from "parport_common.h"
On Thu, 3 Feb 2011 10:46:03 -0800 (PST)
"Peter C. Wallace" wrote:
> OK the first thing thats needed is to connect pid.n.enable to
> bldc.0.init-done so the integrator does not wind up during motor
> initialization.
I would, but when the the bldc component is loaded with a "cfg"
parameter that in
On Thu, 3 Feb 2011, Matt Shaver wrote:
> Date: Thu, 3 Feb 2011 14:21:49 -0500
> From: Matt Shaver
> Reply-To: EMC developers
> To: emc-developers@lists.sourceforge.net
> Subject: Re: [Emc-developers] pid bug
>
> On Thu, 3 Feb 2011 10:46:03 -0800 (PST)
> "Peter C. Wallace" wrote:
>
>> OK the fi
On 3 February 2011 19:21, Matt Shaver wrote:
> I would, but when the the bldc component is loaded with a "cfg"
> parameter that includes "h" (you have Hall sensors), there is no
> bldc.0.init-done pin created.
In that case there is no init stage, so that isn't the cause of the
integral windup.
I
On Thu, 2011-02-03 at 13:37 -0600, Jeff Epler wrote:
... snip
> Ideally, you'd use the routines from "parport_common.h" in the source
> distribution. These routines can cooperate with Linux parport detection
> (which means the user can specify 0 to use parport0, etc) as well as the
> traditional w
Oh, I think I understand better what you're asking now.
Are you asking whether a hardware driver that uses a parport must be
built on the hal component called "hal_parport"? Absolutely not! The
interface of hal_parport (17 or so 'bit' pins that can be read or
written once per period) is pretty i
On Thu, 2011-02-03 at 15:00 -0600, Jeff Epler wrote:
> Oh, I think I understand better what you're asking now.
>
> Are you asking whether a hardware driver that uses a parport must be
> built on the hal component called "hal_parport"?
Not really.
> Absolutely not! The
> interface of hal_parpo
On Thu, 3 Feb 2011 19:49:05 +
andy pugh wrote:
> Is 8i20.N.N.amp-enable being set at the same time as pid-enable?
Yes, they're all in one net in the .hal file:
net amp-enable 8i20.enable hm2_5i20.0.8i20.0.0.amp_enable
<...>
### IF cfg==*h* uncomment these lines
net amp-enable pid.0.enabl
10 matches
Mail list logo
