On Fri, 2007-12-07 at 14:15 -0800, Kirk Wallace wrote:
> I would like to run AXIS remotely. I wrote some notes:
>
> http://www.wallacecompany.com/machine_shop/EMC2/remote_notes.html
>
> to help me keep things sorted out. I am going to give it a try, but if
> anyone has comments or corrections, pl
John,
When using stepconf, the BASE_PERIOD is chosen for you. If the required
step rate is low, stepconf chooses a high BASE_PERIOD, capped at
10ns. In the case of Alan Condit's machine, the maximum required
step rate is 3500Hz which is one step per 285us or so.
Do you see any reason why th
On 9 Dec 2007 at 9:10, [EMAIL PROTECTED] wrote:
> >Thanks for all the help...
> >
> >John
> >
> And thank you, John.
>
> --
> Cheers, Gene
Your welcome Gene
John
-
SF.Net email is sponsored by:
Check out the new Source
The step length requirement of 25000ns is much longer than for other
stepper drivers I am familiar with. Doublestep is predicated on the
idea that the step pulse is fairly short (e.g. less than say 4000ns).
Doublestep uses a "busy wait" to create short output pulses; if
BASE_PERIOD is very large
On Sat, Dec 08, 2007 at 11:12:28PM -0500, xtra209 wrote:
> My experience with stepconfig are mixed... The homing is screwed. I
> fixed that by commenting out the sequence = lines in the .ini and now it
> will home individual axes just fine.
What home sequence is required for your machine? Or is
Jeff Epler wrote:
> John,
>
> When using stepconf, the BASE_PERIOD is chosen for you. If the required
> step rate is low, stepconf chooses a high BASE_PERIOD, capped at
> 10ns. In the case of Alan Condit's machine, the maximum required
> step rate is 3500Hz which is one step per 285us or so.
I don't know of anyone running AXIS remotely; I've never done it.
AXIS assumes that it can create HAL pins and access (read) the var file
from the filesystem. This may be causing problems.
Look on the terminal for any errors AXIS prints.
Jeff
---
On Monday 10 December 2007, Kirk Wallace wrote:
>On Fri, 2007-12-07 at 14:15 -0800, Kirk Wallace wrote:
>> I would like to run AXIS remotely. I wrote some notes:
>>
>> http://www.wallacecompany.com/machine_shop/EMC2/remote_notes.html
>>
>> to help me keep things sorted out. I am going to give it a
On Monday 10 December 2007, Jeff Epler wrote:
>I don't know of anyone running AXIS remotely; I've never done it.
>
On this house machine, from a shell after starting x:
[EMAIL PROTECTED]:xhost +192.168.71.4 (is address of shop.coyote.den)
My username on the emc box is gene, so on this machine from
[snip]
>How are you trying to do the remote, Kirk?
>
>
This is the crux of the problem :)
Kirk is trying to use the remote UI features of EMC2, which allow you to
have the UI communicate with the machine controller using NML. What
you're describing is using remote X, which isn't even close t
On Mon, 2007-12-10 at 09:23 -0600, Jeff Epler wrote:
> I don't know of anyone running AXIS remotely; I've never done it.
>
> AXIS assumes that it can create HAL pins and access (read) the var file
> from the filesystem. This may be causing problems.
>
> Look on the terminal for any errors AXIS p
On Mon, 2007-12-10 at 13:14 -0500, Gene Heskett wrote:
> On Monday 10 December 2007, Kirk Wallace wrote:
> >On Fri, 2007-12-07 at 14:15 -0800, Kirk Wallace wrote:
> >> I would like to run AXIS remotely. I wrote some notes:
> >>
> >> http://www.wallacecompany.com/machine_shop/EMC2/remote_notes.html
On Mon, 2007-12-10 at 13:44 -0500, Stephen Wille Padnos wrote:
> [snip]
>
> >How are you trying to do the remote, Kirk?
> >
> >
> This is the crux of the problem :)
>
> Kirk is trying to use the remote UI features of EMC2, which allow you to
> have the UI communicate with the machine controlle
On Monday 10 December 2007, Stephen Wille Padnos wrote:
>[snip]
>
>>How are you trying to do the remote, Kirk?
>
>This is the crux of the problem :)
>
>Kirk is trying to use the remote UI features of EMC2, which allow you to
>have the UI communicate with the machine controller using NML. What
>you
Jeff Epler <[EMAIL PROTECTED]> writes:
> So here's what I would try: Edit my-mill.ini to set BASE_PERIOD to
> 15 so that the delay can actually be 25000ns. If that still doesn't
> work, also edit my-mill.hal to increase the delay above 25000ns.
> Perhaps your break-out board creates an addit
FYI. My latest Remote_Notes is here:
http://www.wallacecompany.com/machine_shop/EMC2/remote_notes.html
--
Kirk Wallace (California, USA
http://www.wallacecompany.com/machine_shop/
Hardinge HNC lathe,
Bridgeport mill conversion, doing XY now,
Zubal lathe conversion pending)
---
On Mon, 2007-12-10 at 09:23 -0600, Jeff Epler wrote:
> I don't know of anyone running AXIS remotely; I've never done it.
>
> AXIS assumes that it can create HAL pins and access (read) the var file
> from the filesystem. This may be causing problems.
>
> Look on the terminal for any errors AXIS p
--
>
> Message: 1
> Date: Mon, 10 Dec 2007 07:49:26 -0600
> From: Jeff Epler <[EMAIL PROTECTED]>
> Subject: Re: [Emc-users] Stepconf problems
> To: "Enhanced Machine Controller (EMC)"
>
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=us-asc
Jeff Epler <[EMAIL PROTECTED]> writes:
> So here's what I would try: Edit my-mill.ini to set BASE_PERIOD to
> 15 so that the delay can actually be 25000ns. If that still doesn't
> work, also edit my-mill.hal to increase the delay above 25000ns.
> Perhaps your break-out board creates an additi
19 matches
Mail list logo
