I'm all for JA but we don't have time to install and experiment with the
pre-release right now.
Danny
On 9/5/2016 6:10 PM, John Thornton wrote:
> Oh I forgot to say I gave up on the gantry component once the JA branch
> could home a gantry correctly and now it is in master.
>
> JT
>
> On
Oh I forgot to say I gave up on the gantry component once the JA branch
could home a gantry correctly and now it is in master.
JT
On 9/5/2016 4:14 PM, Danny Miller wrote:
> On 9/5/2016 9:24 AM, John Thornton wrote:
>> Sounds like your home switches for the gantry are not connected
>> correctly
oh you're using the gantry component not the joint axes master branch...
never mind. If you were using the joint axes I'd copy you a working
config...
JT
On 9/5/2016 4:14 PM, Danny Miller wrote:
> On 9/5/2016 9:24 AM, John Thornton wrote:
>> Sounds like your home switches for the gantry are
On 9/5/2016 4:14 PM, Danny Miller wrote:
>
> On 9/5/2016 9:24 AM, John Thornton wrote:
>> Sounds like your home switches for the gantry are not connected
>> correctly in hal. You do have one switch for each joint right?
>>
>> JT
> Yep my HAL's right there. And I've watched switches-x1 and
On 9/5/2016 9:24 AM, John Thornton wrote:
> Sounds like your home switches for the gantry are not connected
> correctly in hal. You do have one switch for each joint right?
>
> JT
Yep my HAL's right there. And I've watched switches-x1 and switches-x2
on the HAL monitor while I triggered them.
Sounds like your home switches for the gantry are not connected
correctly in hal. You do have one switch for each joint right?
JT
On 9/5/2016 7:34 AM, Danny Miller wrote:
>
> On 9/2/2016 9:45 AM, Charles Steinkuehler wrote:
>> On 9/1/2016 9:28 PM, dan...@austin.rr.com wrote:
>>> Well, wait-
On 9/2/2016 9:45 AM, Charles Steinkuehler wrote:
> On 9/1/2016 9:28 PM, dan...@austin.rr.com wrote:
>> Well, wait- just rechecked the gantry man page: "When the system is
>> homing and a joint home switch activates, the command value sent to
>> that joint is "frozen" and the joint offset value
On 9/1/2016 9:28 PM, dan...@austin.rr.com wrote:
>
> Well, wait- just rechecked the gantry man page: "When the system is
> homing and a joint home switch activates, the command value sent to
> that joint is "frozen" and the joint offset value is updated
> instead"
>
> It unambiguously DOES say
dan...@austin.rr.com wrote:
>
> Andy Pugh wrote:
> >
> >
> > > On 1 Sep 2016, at 08:17,
> > > wrote:
> > >
> > > Is "2.8 pre" stable enough to consider reliable?
> >
> > I would use it myself (and do) but I
Andy Pugh wrote:
>
>
> > On 1 Sep 2016, at 08:17,
> > wrote:
> >
> > Is "2.8 pre" stable enough to consider reliable?
>
> I would use it myself (and do) but I wouldn't sell a system with it.
>
> I haven't seen any
> On 1 Sep 2016, at 08:17, wrote:
>
> Is "2.8 pre" stable enough to consider reliable?
I would use it myself (and do) but I wouldn't sell a system with it.
I haven't seen any problems in several years of using various JA flavours. With
the
On Thursday 01 September 2016 01:17:40 dan...@austin.rr.com wrote:
> Gene Heskett wrote:
> > On Wednesday 31 August 2016 20:49:22 dan...@austin.rr.com wrote:
> > > I'm using the LinuxCNC 2.7.4 with the realtime support.
> > >
> > > Does the "2.8 pre" have the same RT
Gene Heskett wrote:
> On Wednesday 31 August 2016 20:49:22 dan...@austin.rr.com wrote:
>
> > I'm using the LinuxCNC 2.7.4 with the realtime support.
> >
> > Does the "2.8 pre" have the same RT support?
> >
> > Danny
>
> First, please don't top post, and second, yes.
On Wednesday 31 August 2016 20:49:22 dan...@austin.rr.com wrote:
> I'm using the LinuxCNC 2.7.4 with the realtime support.
>
> Does the "2.8 pre" have the same RT support?
>
> Danny
First, please don't top post, and second, yes.
And the 2.7.4 you are running is quite old. If you have not
I'm using the LinuxCNC 2.7.4 with the realtime support.
Does the "2.8 pre" have the same RT support?
Danny
John Thornton wrote:
> Yup
>
> On 8/30/2016 1:56 AM, dan...@austin.rr.com wrote:
> > So, I have to switch to 2.8-pre for JA?
> >
> > Danny
> >
> > Charles
So, I have to switch to 2.8-pre for JA?
Danny
Charles Steinkuehler wrote:
> On 8/25/2016 11:38 AM, dan...@austin.rr.com wrote:
> >
> > So I guess it does do that. Now if one home was physically
> > installed where it trips 0.53" before physical end-of-travel,
On 25 August 2016 at 19:41, John Thornton wrote:
> A couple of vids showing my testing of JA
> https://www.youtube.com/watch?v=1OtWNuLWfwc
> https://www.youtube.com/watch?v=wgNLd6A34Vo
They both claim to be using the gantry component?
--
atp
"A motorcycle is a bicycle with a
Having "messed with" both the gantry component and thanks for writing
that and JA now Master. I much prefer JA homing. Much more straight
forward to me.
A couple of vids showing my testing of JA
https://www.youtube.com/watch?v=1OtWNuLWfwc
https://www.youtube.com/watch?v=wgNLd6A34Vo
JT
On
I floundered around with other components while trying to set this up, and was
told "WTH are you doing just use 'gantry'". So I went with gantry component,
and it's worked ok. But if I need something else, I'm open to it.
I have the RT version of LinuxCNC. Will that update with this JA stuff
On 8/25/2016 11:38 AM, dan...@austin.rr.com wrote:
>
> So I guess it does do that. Now if one home was physically
> installed where it trips 0.53" before physical end-of-travel, if
> this were NOT the gantry axis I'd just give its final machine coord
> as 0.53" and its machine coord is correct
On 25 August 2016 at 17:38, wrote:
> Which would mean the joints are racked by 0.15" and will forever be locked
> like that because future moves are in axis mode, not joint mode.
So, you are saying that you want to square a gantry to non-square switches?
Use JA, you know
OK, well the gantry man page says:
"All controlled joints track the commanded position (with a per-joint offset)
unless in the process of homing. Homing is when the commanded position is
moving towards the homing switches (as determined by the sign of search-vel)
and the joint home switches
Here is the .hal i'm using with the gantry comp.
https://forum.linuxcnc.org/forum/47-hal-examples/30818-gantry-hal-example
//Peter
2016-08-25 18:10 GMT+02:00 Charles Steinkuehler :
> On 8/25/2016 11:00 AM, dan...@austin.rr.com wrote:
> > What's that mean? Does it
On 8/25/2016 11:00 AM, dan...@austin.rr.com wrote:
> What's that mean? Does it just drive both in tandem until both
> switches are TRUE, then call it homed? That wouldn't work, I need
> independent homing for sure.
No, it doesn't just drive both motors. It stops the first motor to
hit the home
What's that mean? Does it just drive both in tandem until both switches are
TRUE, then call it homed? That wouldn't work, I need independent homing for
sure.
Not sure what the Probotix code is saying but I'll try it out later:
# join the home switch signals so that both switches have to be
On 8/24/2016 11:25 PM, dan...@austin.rr.com wrote:
> I have a gantry router with 2x X motors. I'm using the "gantry"
> component.
>
> Installing homing switches. Got the Y working right off the bat.
> I can see the X1 and X2 switches trigger in HAL Scope so I'm good
> to go. This is a wide
26 matches
Mail list logo