Good Morning Gentleman,
Is it possible, to call an m-code using a classicladder output?
Now that I have my tool changer working, I am trying to work into my
ladder logic the ability to call a M40, and it will put the tool that is
in the spindle back into the carousel, and then when the logic is
I just have to wonder why your not using iocontrol.0.tool-change and
iocontrol.0.tool-changed or am I totally off track and not understanding
the application?
JT
On 11/11/2015 7:13 AM, Rick Lair wrote:
> Good Morning Gentleman,
>
> Is it possible, to call an m-code using a classicladder output?
On 11 November 2015 at 13:13, Rick Lair wrote:
> The M40 is going to "sets return-tool true", and I was going to use the
> the M39 to "sets return-tool false". Unless there is a better way to
> reset the signal without calling the M39?
Why not net a classic ladder output directly to whatever pin
I did answer my own question, I added a dwell time, then called the m39
from the m40, using subroutines.
John,
I am not sure how to use the M6 command to put the currently loaded tool
away, back into the carousel.
I am just doing this that way if the operator knows he needs to shut
linuxcnc d
On 11 November 2015 at 13:38, Rick Lair wrote:
> I am not sure how to use the M6 command to put the currently loaded tool
> away, back into the carousel.
M6 T0
--
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto
---
So far I know you use a MDI_COMMAND in the .ini file and then you
connect that through halui.mdi-command-01
-- Original Message --
From: "Rick Lair"
To: "Emc Users"
Sent: 2015-11-11 15:13:57
Subject: [Emc-users] Call an M Code from a Classic ladder output
>
How will your carousel component handle that "0"?
On 11/11/2015 8:42 AM, andy pugh wrote:
> On 11 November 2015 at 13:38, Rick Lair wrote:
>> I am not sure how to use the M6 command to put the currently loaded tool
>> away, back into the carousel.
>
> M6 T0
>
--
Thanks
Rick Lair
Superior R
On 11 November 2015 at 13:54, Rick Lair wrote:
> How will your carousel component handle that "0"?
I don't actually know...
This is the problem with writing components that you don't actually need.
Looking at the code, it will enter state 1 then not move. Which is
probably about right.
enable g