On Wednesday 10 April 2019 21:36:09 Jon Elson wrote:
> On 04/10/2019 10:05 AM, Gene Heskett wrote:
> > And if I copy the ini to one with no A references in it, do I also
> > have separate .hal files, or does hal ignore the A references? Or
> > do you have 3 hal files? A basic, and a load
On 04/10/2019 10:05 AM, Gene Heskett wrote:
And if I copy the ini to one with no A references in it, do I also have
separate .hal files, or does hal ignore the A references? Or do you
have 3 hal files? A basic, and a load vertical and a load horizontal?
Yes, you would have an .ini and at least
On Wednesday 10 April 2019 13:29:54 Gene Heskett wrote:
> On Wednesday 10 April 2019 12:47:23 John Dammeyer wrote:
> > Hi Andy,
> > See below.
> > [...]
> > > > The question then is whether or not the system, when starting
> > > > can/will
> > > recognize an input which is a unit present signal.
> Exactly what I'm doing. Except no endoder, stepper driven and likely
> needs a bigger motor, and more speed reduction to improve the holding
> power. Thats a downright puny motor on it now, and I have a 270 oz/in
> currently holding down a stepladder step. 8 wire so slower top speed but
> easy
On Wednesday 10 April 2019 12:47:23 John Dammeyer wrote:
> Hi Andy,
> See below.
>
> > -Original Message-
> > From: andy pugh [mailto:bodge...@gmail.com]
> > Sent: April-10-19 2:46 AM
> > To: Enhanced Machine Controller (EMC)
> > Subject: Re: [Emc-users] Leaving an axis out of the home
Hi Andy,
See below.
> -Original Message-
> From: andy pugh [mailto:bodge...@gmail.com]
> Sent: April-10-19 2:46 AM
> To: Enhanced Machine Controller (EMC)
> Subject: Re: [Emc-users] Leaving an axis out of the home sequence AND
> (continued:)
>
> On Wed, 10 Apr 2019 at 04:49, John
On Wednesday 10 April 2019 11:33:05 Jon Elson wrote:
> On 04/09/2019 10:47 PM, John Dammeyer wrote:
> > The question then is whether or not the system, when
> > starting can/will recognize an input which is a unit
> > present signal. Can not the HAL files be set up to
> > #include other files? So
On Wednesday 10 April 2019 11:28:41 Jon Elson wrote:
> On 04/09/2019 10:16 PM, Gene Heskett wrote:
> > And the interlock needs to know if the loaded code
> > contains an A|B|C move.
>
> OK, now this is going beyond the capabilities of LinuxCNC as
> it is. I think the best way to handle this is to
Carbon is soluble in iron, which is why you can't
use diamond to machine steel. When the steel
heats up, it just starts absorbing carbon from the
diamond particles. Your high carbon steel becomes
higher carbon steel and your diamond goes away.
-- Ralph
On Wed, 10 Apr 2019 at 16:07, Gene Heskett wrote:
> So I don't see a tasty way to do it as I'd still have two pairs of files
> to keep in synch with such as MAX_VELS etc. With the sheer number of
> variables to keep synched, the N! could rapidly exceed 69, the maximum
> my now elderly ti-51
On Wednesday 10 April 2019 11:21:11 Jon Elson wrote:
> On 04/09/2019 08:31 PM, Gene Heskett wrote:
> > Greetings all;
> >
> > out of the logic that determines whether the machine will run gcode
> > when that A axis has not been homed because its unplugged, off the
> > machine and stored and
On 04/09/2019 10:47 PM, John Dammeyer wrote:
The question then is whether or not the system, when
starting can/will recognize an input which is a unit
present signal. Can not the HAL files be set up to
#include other files? So based on an input select one of
two HAL sub files to load. One
On 04/09/2019 10:16 PM, Gene Heskett wrote:
And the interlock needs to know if the loaded code
contains an A|B|C move.
OK, now this is going beyond the capabilities of LinuxCNC as
it is. I think the best way to handle this is to have two
configs. If you ever load a G-code file with an A move
On 04/09/2019 08:31 PM, Gene Heskett wrote:
Greetings all;
out of the logic that determines whether the machine will run gcode when
that A axis has not been homed because its unplugged, off the machine
and stored and either is unhomed, or was never homed since this power
up.
How is this best
On Wednesday 10 April 2019 06:00:50 andy pugh wrote:
> On Wed, 10 Apr 2019 at 10:50, Gene Heskett
wrote:
> > Two separate configs means it will be hard to keep them in synch,
>
> Two configs (ie INI files) can share the same folder, so the HAL
> files, .var file and tool table are all shared.
>
On Wed, 10 Apr 2019 at 10:50, Gene Heskett wrote:
> Two separate configs means it will be hard to keep them in synch,
Two configs (ie INI files) can share the same folder, so the HAL
files, .var file and tool table are all shared.
I do this with my mill to switch between horizontal and
On Tuesday 09 April 2019 23:47:24 John Dammeyer wrote:
> I believe I'll have a similar problem.
>
> > > Assuming you unplug the rotary axis when you remove it, you could
> > > simply use a normally closed homing switch that unplugs with the
> > > axis. Problem with this is it wouldn’t let you use
On Wed, 10 Apr 2019 at 04:49, John Dammeyer wrote:
> Since my Harmonic Drive/STMBL are an AC Servo
...
> The question then is whether or not the system, when starting can/will
> recognize an input which is a unit present signal.
This is a solved problem :-) (I have exactly the same 4th axis as
On Tuesday 09 April 2019 23:40:54 Thaddeus Waldner wrote:
> On Apr 9, 2019, at 10:26 PM, Gene Heskett wrote:
> > On Tuesday 09 April 2019 23:02:46 Thaddeus Waldner wrote:
> >> Assuming you unplug the rotary axis when you remove it, you could
> >> simply use a normally closed homing switch that
Maybe I am thinking too simplistically, but my approach would be:
Start with my 3-axis config
Copy it
add the fourth axis information to the copy
change the name of he config to 4 axis.
The steppers I used cannot have the motor connected while powered. So this
method suits me.
--J. Ray Mitchell
I believe I'll have a similar problem.
> > Assuming you unplug the rotary axis when you remove it, you could
> > simply use a normally closed homing switch that unplugs with the axis.
> > Problem with this is it wouldn’t let you use the fast approach, slow
> > home sequence with a single switch.
On Apr 9, 2019, at 10:26 PM, Gene Heskett wrote:
>
> On Tuesday 09 April 2019 23:02:46 Thaddeus Waldner wrote:
>
>> Assuming you unplug the rotary axis when you remove it, you could
>> simply use a normally closed homing switch that unplugs with the axis.
>> Problem with this is it wouldn’t let
On Tuesday 09 April 2019 23:02:46 Thaddeus Waldner wrote:
> Assuming you unplug the rotary axis when you remove it, you could
> simply use a normally closed homing switch that unplugs with the axis.
> Problem with this is it wouldn’t let you use the fast approach, slow
> home sequence with a
On Tuesday 09 April 2019 22:31:26 andy pugh wrote:
> On Wed, 10 Apr 2019 at 02:33, Gene Heskett
wrote:
> > out of the logic that determines whether the machine will run gcode
> > when that A axis has not been homed because its unplugged, off the
> > machine and stored and either is unhomed, or
Assuming you unplug the rotary axis when you remove it, you could simply use a
normally closed homing switch that unplugs with the axis. Problem with this is
it wouldn’t let you use the fast approach, slow home sequence with a single
switch.
Thaddeus Waldner
Newdale School
Elkton, SD 57026
On Wed, 10 Apr 2019 at 02:33, Gene Heskett wrote:
> out of the logic that determines whether the machine will run gcode when
> that A axis has not been homed because its unplugged, off the machine
> and stored and either is unhomed, or was never homed since this power
> up.
The simplest is
26 matches
Mail list logo
