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
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.
--
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)
emc-users@lists.sourceforge.net
Message-ID: [EMAIL PROTECTED]
Content-Type: text
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 additional
On Sat, 2007-12-08 at 23:12 -0500, xtra209 wrote:
The Foolproof tester is still at work,
In the old days, if you wanted something tested you sent it to Dave and
Ian. It seems that we have developed quite a good bunch of test-to-fail
guys. One of these times we will have to get round to
Alan Condit wrote:
John Kasunich [EMAIL PROTECTED] writes:
There must be something different between the generated files and the
working files. You will have to figure out what it is. Once you know
what the difference is, then Jeff can figure out if it is a stepconf
error, or if you
Hi:
No offense taken. I think differently than some people and therefore
tend to test differently.
Sometimes this breaks things; and then the developer can go fix it. ;-)
Dave
On Dec 9, 2007, at 11:06 AM, Jon Elson wrote:
Ray Henry wrote:
On Sat, 2007-12-08 at 23:12 -0500, xtra209 wrote:
Jeff,
I tried to use stepconf and couldn't get it to work.
I am using emc2 2.2.2. I have a configuration that works so I know that there is
not a problem with my hardware. I am using a CandCNC miniIO BOB which uses the
Xylotex pinout. All three drives are enabled by the same signal. All three
Alan Condit wrote:
Jeff,
I tried to use stepconf and couldn't get it to work.
I am using emc2 2.2.2. I have a configuration that works so I know that there
is
not a problem with my hardware. I am using a CandCNC miniIO BOB which uses the
Xylotex pinout. All three drives are enabled by the
John Kasunich [EMAIL PROTECTED] writes:
I'd suggest pastebin for the files. Don't send big attachments to the list.
I'd also suggest running diff and posting the diff (on list if short, at
pastebin if long). Since you have a working config, seems like you
should be looking to see
On Sat, 2007-12-08 at 20:26 +, Alan Condit wrote:
My working ini and hal files are derived from stepper_in.ini and
xylotex_pinout.hal and those files are considerably different from the files
generated by stepconf. On the hal files diff basically doesn't find any common
lines to anchor on.
Jeff Epler [EMAIL PROTECTED] writes:
One difference I spotted between the two ini files is that the
configured acceleration is higher in the stepconf file than in the
working file.
Jeff
Jeff,
After testing my working config some more, I upped the acceleration on all three
axii in my
Alan Condit wrote:
Jeff Epler [EMAIL PROTECTED] writes:
One difference I spotted between the two ini files is that the
configured acceleration is higher in the stepconf file than in the
working file.
Jeff
Jeff,
After testing my working config some more, I upped the acceleration on all
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. Also the thing would not load
without a bunch of error messages and quitting. I fixed that by doing a
hard reboot of
16 matches
Mail list logo
