M6 Remap for ATC with carousel

Michael wrote:

Already got a window that said:

pycall(remap.change_prolog) fail

Not sure what different results I would get from a terminal. Nor do I know how to do that.

 

Open a terminal and go to your linuxcnc config machine directory. type in :   linuxcnc (machinename).ini

This is an invaluable tool when doing remaps. you can put print statements and track what your remap is doing. When the interpreter ignores you, you can sometimes at least see why, 

The last paragraph of Section 4   Upgrading existing system for Remapping  shows you how to do it.

A quick video for documentation purposes

Trying to figure out the last little error I have in this operation. This is a 22 pocket tool changer and index is at pocket 1.

When changing tools the changer is counting pockets 2-23 with mechanical pocket 1 being pocket "23" as far as linuxcnc is concerned.

So my tool table entries are linear T1 is in P1; T2 is P2 etc.

When I request M6T1 the carousel rotates to mechanical pocket 2 and picks up that tool showing T1 as being loaded now.

Any ideas?

Answering my own question. For a non random tool changer it ignores pocket number in the tool table and goes in order of the actual tool.tbl file. So you would need to remove the entry for T0 in the table.

Now that being said I added a 23 tool entry and called it via MDI and the tool changer wrapped around and went to pocket 1 to grab that tool. It also rewrote the tool.tbl file and kicked T1 to the next line on the file. This change didn't show up in the tool table editor however. I would imagine this behavior is a bug in the tool table editor reading the file.

Is there anyway to make a non random tool changer actually use the pocket number in the table and not go by list order? I would love to leave a bunch of tool entries in the table and designate what pocket they are in when I load them into the changer.

iov2 uses the same process for determining pockets on a non random changer. The pocket is based on the order of the tool.tbl list and not the pocket written into the file.

What part of linuxcnc controls those variables being read. Would it be an easy switch to make it use the pocket number listed in the tool table?

You could drop the component and use classicladder for operating your magazine  and python to control the tools in the corresponding pockets, or use pure python remap. I think you can do an ngc remap with clasicladder and just use classic ladder for operating your magazine. This should be no problem if you can pass arguments to classicladder.

Apparently on a random tool changer the pocket number matters but a non random tool change uses the tools as listed in order on the tool.tbl file not the tool table editor.

linuxcnc.org/docs/2.8/html/code/code-not...able_and_toolchanger

• When LinuxCNC is configured for a nonrandom toolchanger, the pocket number in the tool file can be any positive integer (pocket 0 is not allowed). LinuxCNC silently compactifies the pocket numbers when it loads the tool file, so there may be a difference between the pocket numbers in the tool file and the internal pocket numbers used by LinuxCNC-with-nonrandom-toolchanger.