https://www.dropbox.com/s/he8bvi9dxezxfnz/enshutoolchange.comp?dl=0
This is a link to the tool change component I wrote for the Enshu. Side mount change matrix Random tool changer Z axis moves up to tool change position The matrix moves the pot into position. The tool matrix is hydraulic and air driven. The chain selects the tool pot in a unidirectional manner. The hydraulic motor rotates the chain to the requested pot number taking into account the random nature of the tool number positions. When the requested number is counted the chain stops and reverses slowly until the tool change dog runs against a stop to position the pot accurately. The pot rotates down. The arm rotates to engage the tool in the spindle and the tool in the pot. The pot releases the tool and the spindle releases the tool. The arm moves down. The arm rotates to exchange tools. The arm raises to insert the tool into the pot and the spindle. The arm returns to ready position. Tool change recovery in any position except tool change arm down and rotated is to restart the machine. The component reads the tool change sensors and performs a recovery/reset on machine startup. Use it Modify it Have fun thanks Stuart On Fri, Aug 16, 2019 at 11:08 AM Dave Cole <linuxcncro...@gmail.com> wrote: > My answer is.... it depends. > > If you already have I/O that you can use, and you can do the logic in > Classic Ladder or a component, then that will work. > If you need to add high current I/O or need 120 or 220 volt AC I/O then > you might as well buy a cheap PLC. The Click PLC with the Modbus TCP > interface is about as inexpensive as they come. You usually can't buy > remote I/O for what the entire PLC costs. I've used them as I/O > connected to a dedicated PC for a custom data/control system. In that > case the only logic in the PLC is an end statement so the PLC will > cycle. Then I just write and read to the PLC via Modbus TCP. I've > done the same thing with the older serial Modbus PLCs. I've never had > a Click PLC fail yet but I also avoid relay outputs. No matter what you > do, relay outputs will eventually fail depending on how frequently you > cycle the relays. > > Just remember that if you do use an external PLC and put a program in > it, you still need to do the config in LinuxCNC to get the data back and > forth to the PLC so the PLC can interact. But you can keep the > interface simple. Pass it an integer for the tool number required and > then tell it to get that tool, etc. Wait for the tool fetch to > complete, then continue, etc. > > Programming a dedicated PLC like the Click PLC is easier for me than > programming in Classic Ladder. And some tool changers can be very > complex logically. > > Dave > > On 8/16/2019 7:29 AM, andrew beck wrote: > > Hi guys > > > > I am currently running 2.7 linuxcnc. I think it is the stretch iso but I > > am not sure. how to I tell if I have linuxcnc stretch iso. would love > it > > if someone could show me a simple way to tell what i have. there must be > > some show command. > > > > I just wondered what is involved in changing to 2.8 and is there a iso > that > > I can just flash the computer with or do I have to build from source. > as I > > saw 2.9 is out now so I guess 2.8 must be getting a lot of use. > > > > Also I was wondering what most people use for all the toolchanger logic > > nowdays. I have seen reference to components and all sorts of stuff > > recently. I was wondering what is the best way. I currently know of > three > > options that people use. > > > > 1 just use the onboard classic ladder which is not very nice to use and > > hard to learn. advantages are everything is contained within linuxcnc > > > > 2 just use a external click PLC. advantages are easy setup and probably > > rock solid > > > > 3 use toolchanger components and remapped G codes. > > > > If people could reply to these comments with what they vote best and > > ideally a link to the best way to complete the option, I would really > > appreciate it. > > > > Regards > > > > Andrew > > > > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > > Virus-free. > > www.avast.com > > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > > > _______________________________________________ > > Emc-users mailing list > > Emc-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/emc-users > > > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > -- Addressee is the intended audience. If you are not the addressee then my consent is not given for you to read this email furthermore it is my wish you would close this without saving or reading, and cease and desist from saving or opening my private correspondence. Thank you for honoring my wish. _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
