On Tuesday 18 October 2016 16:10:45 Rene Hopf wrote:
> > On 18 Oct 2016, at 15:21, Gene Heskett wrote:
> >
> > On Tuesday 18 October 2016 08:41:41 Erik Friesen wrote:
> >> Thanks for this info.
> >>
> >> Has anyone implemented spindle load monitoring per tool like the
> >> Haas control? What wou
> On 18 Oct 2016, at 15:21, Gene Heskett wrote:
>
> On Tuesday 18 October 2016 08:41:41 Erik Friesen wrote:
>
>> Thanks for this info.
>>
>> Has anyone implemented spindle load monitoring per tool like the Haas
>> control? What would this take, adding a line in the tool table plus
>> some twe
On Tuesday 18 October 2016 08:41:41 Erik Friesen wrote:
> Thanks for this info.
>
> Has anyone implemented spindle load monitoring per tool like the Haas
> control? What would this take, adding a line in the tool table plus
> some tweaks?
I occasionally put a halmeter on the pid.s.error but have
Thanks for this info.
Has anyone implemented spindle load monitoring per tool like the Haas
control? What would this take, adding a line in the tool table plus
some tweaks?
On Mon, Oct 17, 2016 at 11:03 AM, Stuart Stevenson wrote:
> You can find explanations in the documentation
>
>
> HOME_OF
You can find explanations in the documentation
HOME_OFFSET =0.0 - the amount you want to
table to move from the homed zero position after the index pulse is found
and the encoder position has been set to zero. You don't necessarily need
to know exactly how this wor
On 17 October 2016 at 14:40, Erik Friesen wrote:
> Ok, but what about homing?
I think homing uses the encoder "position" pin, which zeroes when index resets.
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils a
Ok, but what about homing?
On Mon, Oct 17, 2016 at 9:21 AM, andy pugh wrote:
> On 17 October 2016 at 13:43, Erik Friesen wrote:
>> I still don't follow though, how mesa hardware uses the index. Does
>> it zero it the first time, or how does that bubble up to lcnc?
>
> bldc uses the raw counts a
On 17 October 2016 at 13:43, Erik Friesen wrote:
> I still don't follow though, how mesa hardware uses the index. Does
> it zero it the first time, or how does that bubble up to lcnc?
bldc uses the raw counts and holds its own index offset.
--
atp
"A motorcycle is a bicycle with a pandemoniu
I still don't follow though, how mesa hardware uses the index. Does
it zero it the first time, or how does that bubble up to lcnc?
On Mon, Oct 17, 2016 at 8:18 AM, andy pugh wrote:
> On 17 October 2016 at 12:59, Erik Friesen wrote:
>>> The "bldc" component offers a few options. If there are no
On 17 October 2016 at 12:59, Erik Friesen wrote:
>> The "bldc" component offers a few options. If there are no hall
>> signals then using the encoder index (if there is one) is probably
>> best.
>
> So what, blind feed the thing at the beginning?
Yes, the component can just feed a rotating field
> The "bldc" component offers a few options. If there are no hall
> signals then using the encoder index (if there is one) is probably
> best.
So what, blind feed the thing at the beginning?
Also, I don't seen anywhere how to go about using a home switch +
encoder index to accurately home.
On Sa
On 15 October 2016 at 14:54, Erik Friesen wrote:
> #1. What method could be used for a tool change recovery sequence?
That rather depends on what it takes to recover the situation, but
there is scope for reporting tool-changer errors through HAL and a
"magic comment"
If you control the tool chan
12 matches
Mail list logo
