On Apr 2, 2009, at 10:45 AM, Jon Elson wrote:
> Dave Engvall wrote:
>>
>>
>> Indeed that ( + and - ) would be the intuitive way to do it but it
>> doesn't work.
>>
>> I tried changing the sign on INPUT SCALE and the sign on
>> OUTPUT_SCALE
>> independently but that doesn't work either. Axis mo
Dave Engvall wrote:
>
>
> Indeed that ( + and - ) would be the intuitive way to do it but it
> doesn't work.
>
> I tried changing the sign on INPUT SCALE and the sign on OUTPUT_SCALE
> independently but that doesn't work either. Axis moves on command and
> then
> faults on following error.
> S
On Thu, 2009-04-02 at 09:59 -0700, Dave Engvall wrote:
... snip
> Now that things are running I can relax a bit. Many thanks to all
> those that offered
> advise on my problem(s).
>
> Dave
Oops, looks like you are way ahead of me on this.
Kirk
http://www.wallacecompany.com/machine_
On Apr 2, 2009, at 9:16 AM, Kirk Wallace wrote:
> On Wed, 2009-04-01 at 22:18 -0700, Dave Engvall wrote:
> ... snip
>> Indeed that ( + and - ) would be the intuitive way to do it but it
>> doesn't work.
>>
>> I tried changing the sign on INPUT SCALE and the sign on
>> OUTPUT_SCALE
>> independe
On Wed, 2009-04-01 at 22:18 -0700, Dave Engvall wrote:
... snip
> Indeed that ( + and - ) would be the intuitive way to do it but it
> doesn't work.
>
> I tried changing the sign on INPUT SCALE and the sign on OUTPUT_SCALE
> independently but that doesn't work either. Axis moves on command and
On Apr 1, 2009, at 7:34 PM, Kirk Wallace wrote:
> On Wed, 2009-04-01 at 18:43 -0700, Dave Engvall wrote:
>>
>>
>> Am back from the beach and have tried things again.
>>
>> Finally found a fundamental mistake. 1525BR amps expect a
>> differential input; so battery boxes give the expected result.
On Wed, 2009-04-01 at 18:43 -0700, Dave Engvall wrote:
>
>
> Am back from the beach and have tried things again.
>
> Finally found a fundamental mistake. 1525BR amps expect a
> differential input; so battery boxes give the expected result.
> However, the dacs are ground referenced. After I fin
Am back from the beach and have tried things again.
Finally found a fundamental mistake. 1525BR amps expect a
differential input; so battery boxes give the expected result.
However, the dacs are ground referenced. After I finally caught on I
wired the 1525 inputs with gnd to gnd and + dac t
ine Controller (EMC)" > us...@lists.sourceforge.net>
>> Subject: Re: [Emc-users] m5i20_pidtest.hal
>>
>>
>> On Mar 26, 2009, at 5:52 PM, Stephen Wille Padnos wrote:
>>
>>
>>> If a bare HAL setup won't do it, then it's unlikely that the f
On Fri, 27 Mar 2009, Dave Engvall wrote:
> Date: Fri, 27 Mar 2009 12:20:01 -0700
> From: Dave Engvall
> Reply-To: "Enhanced Machine Controller (EMC)"
>
> To: "Enhanced Machine Controller (EMC)"
> Subject: Re: [Emc-users] m5i20_pidtest.hal
>
>
On Mar 26, 2009, at 5:52 PM, Stephen Wille Padnos wrote:
> If a bare HAL setup won't do it, then it's unlikely that the full EMC
> setup will either. (but you knew that)
>
> - Steve
OK, I've regrouped and downloaded 2.3 pre-beta 2 as a deb from Matt's
site,
installed it and modified the hal
dave wrote:
>[snip]
>
>I'm on 2.2.8 and I cannot find a hm2_5i20_pidtest.hal. But can find one
>under m5i20 which is what I'm using. So I think I'm still stuck about
>how to pet/feed the dog.
>
>Show all *dog* does reveal an m5i20.0.watchdog-reset which is set to
>FALSE. I've been unable to set
On Thu, 2009-03-26 at 18:56 -0400, Stephen Wille Padnos wrote:
> [snip]
>
> >Things are automagically better!
> >Scripts runs after fixing the period.
> >I do need to set the enable manually but that is minor. note: enable is
> >for dacs and pid.
> >DACS now show signal.
> >
> >Watchdog code;
>
[snip]
>Things are automagically better!
>Scripts runs after fixing the period.
>I do need to set the enable manually but that is minor. note: enable is
>for dacs and pid.
>DACS now show signal.
>
>Watchdog code;
># enable a 16ms watchdog and DAC auto reset
>setp m5i20.0.watchdog-timeout 16000
On Thu, 2009-03-26 at 17:42 -0400, John Kasunich wrote:
> dave wrote:
> > Hi all,
> >
> > CPU is a 1200 Duron, with an m5i20/7i33. The encoders show movement when
> > I rotate the ballscrew and scale properly.
>
> Good.
>
> > I'm attempting to bring up an m5i20 with the hm2 driver.
> >
> >
On Mar 26, 2009, at 2:50 PM, Stephen Wille Padnos wrote:
> dave wrote:
>
>> Script started on Thu 26 Mar 2009 01:53:54 PM PDT
>> ^[]0;d...@cinci:
>> ~/emc2-trunk/configs/m5i20^gd...@cinci:~/emc2-trunk/configs/m5i20$
>> halrun -I m5i20-p^G^H^[[K^H^[[K_pidtest.hal ^M
>> insmod: error inserting '/ho
dave wrote:
>Script started on Thu 26 Mar 2009 01:53:54 PM PDT
>^[]0;d...@cinci:
>~/emc2-trunk/configs/m5i20^gd...@cinci:~/emc2-trunk/configs/m5i20$
>halrun -I m5i20-p^G^H^[[K^H^[[K_pidtest.hal ^M
>insmod: error inserting '/home/dave/emc2-trunk/rtlib/threads.ko': -1
>Unknown symbol in module^M
>m5
dave wrote:
> Hi all,
>
> CPU is a 1200 Duron, with an m5i20/7i33. The encoders show movement when
> I rotate the ballscrew and scale properly.
Good.
> I'm attempting to bring up an m5i20 with the hm2 driver.
>
> I've been thru the battery box servo setup and am getting good response
> out
Hi all,
CPU is a 1200 Duron, with an m5i20/7i33. The encoders show movement when
I rotate the ballscrew and scale properly.
I'm attempting to bring up an m5i20 with the hm2 driver.
I've been thru the battery box servo setup and am getting good response
out of the servo amps.
However, my tr
19 matches
Mail list logo
