G'day All
Interfacing a Kawasaki robot to controllogix using ethernet IP. Looking for setup logic, maybe eds file.
Thanks
We just have ours set up as generic modules
G'day All
Interfacing a Kawasaki robot to controllogix using ethernet IP. Looking for setup logic, maybe eds file.
Thanks
We just have ours set up as generic modules
Sounds like this unit is a personal one you have at home. If I don't see a video of you utilizing it to flip hamburgers then I will be deeply disappointed.
With a little help from kwakisaki this morning, I got power applied to the robot at least for the first time. The rest of the control cabinet is waiting on components and spare time to finish.
Thank you for clarifying, I assumed as much but with this being my first integration I didn't want to go just off my assumption. By the end of this hopefully I wont be as much of a Rookie!
Working on integrating a RS003N into a training cell for my company. We are at the point of applying power now but ran into a little confusing situation. The XPOW (main 240VAC power) cables connections I have do not match what's listed in the F-series Controller Installation and Connection Manual. In the manual (page 48) it shows the wires as Black/White/Green(ground), My cable has two Black wires labeled 1 and 2 with a Ground. I'm assuming its fine to connect 1 to 240VAC and 2 to 0v common, but there's nothing I can find in the manual that states polarity does or does not matter so you can understand my hesitation to just assume. Any thoughts or suggestions?
You can set dedicated signals for different outputs or inputs :
when autostart1 is on :
alfo useful for teach, cycle start, and so on...
For sure, thank you for the suggestion. Unfortunately I’ve seen where a signals stay “high” after a connection was lost, hence the desire to create a heart beat situation.
This is exactly what I’m looking for. Thank you very much!
Has anyone here ever found a breakout board and pre manufactured cables for the XGPIO connector for the F controller? When I search the connectors manufacturer information (DX40-50p 55 HIROSE) I’m able to locate more connectors and such but not manufactured cables or a breakout board. I’d really like to avoid having to solder my own as these are super small wires (28awg). Any feed back would be appreciated.
You could use the EIPSTATUS command to monitor on the robot to report adapter/scanner status.
Within the PLC, surely there is diagnostic monitoring that can do the same.
Negating any need for any heartbeat exchange.
I cant find anything in the E-series AS Language manual about EIPSTATUS? Am I looking in the wrong manual?
The other aspect to consider (often overlooked is the RUNMASK command).
RUNMASK masks the signal(s) to only be controlled from any program when it's executing.
So simply applied, if you turn the signal on at the start of the PC Task......you know it's running.
Looking at the description of RUNMASK, I appreciate the suggestion but I don't think it will work with the alarm events I'm trying to monitor/send to the plc. Might come in handy at a later date though! Also thanks for clarifying the function of the PULSE command.
Are you using a GSD file for the robot in the PLC program? If the robot is on profinet communication, then you can use some profinet diagnostics in orfer to check If the device is still running or not.
Also, in the robot program you can check If the autostart program is running or not with task function. It is very usefull If you need to exchange information between autostart program and motion program.
No the OEM just has it mapped to a generic ethernet module and write to a I/O array. Nothing actually monitors the connection that I'm aware of. As far as Task Function's, I could read up on those in the Ops manual right? Right now I'm just writing to networked outputs to signal if the robot is Held, if a solenoid is enabled, or if the collision sensor is off. These outputs are used to trigger alarm bit tags in the plc so that there is a trackable alarm on the HMI to "alert" the operator or skilled tradesmen of those events. It in now way interrupts the equipment running.
What protocol is being used?
Ethernet/IP I believe? PLC program is for the line in question. The VTP is just what I had saved on this work station but I believe all our cells are identical besides the actual IP's.
If the ethernet communication between the robot and PLC is working. This autostart is just writing to outputs used to trigger supervisory alarms. They don't stop the process in any way, just aid in troubleshooting physical problems.
I recently created a AutoStart program to monitor certain IO events and its been working well. One thing I noticed the other day is I had forgot to enable the system switch to enable the AutoStart feature (oops, rookie mistake) which I promptly corrected. But that got me thinking about a previous post I read on here about the PULSE command. I seem to remember reading that someone was using a pulsed output as a "heart beat" from the robot, monitored by the plc. If you don't see that output turning on and off then trigger an alarm to alert of a communication interruption. I believe this will be sufficient, I was also planning on setting the time base to 3 sec. Thought or suggestions on best practices?
Thank you sir!
This is a BIRTHDAY + CHRISTMAS + EASTER........... Ericwiz7923.....I'm watching you.
A lot of the Control components are "Scavenged" or coming from our in house stock. As of right now, not including the enclosure or robot I have about 2k spent on my BOM. Everything else has been aquired through "voodo" stockroom economics
Display MoreStop it.........that's like a lingerie shop without a front window to me now......
The table and shelf would allow a more all in one/secured unit then.....cos you know if things are exposed, they tend to grow legs in industry.
All AB route then......I suppose this is what you have sitewide then - be good to implement the fieldbus side then - Devicenet and Ethernet/IP.
Kinco are another good comparison to Weintek HMI's, cheap and cheerful and packed with the usual features.
Yes, I think a vision system would set that off quite nicely indeed, maybe a portable pneumatic generator for simple gripper operations too.
Very interested in watching this develop indeed......
Yes we are an all AB plant, which is nice for when I'm designing curriculum for training. There's definitely days I'm pulling my hair out working with AB's idiosyncrasies though. I've attached my purchased options for the robot. Definitely Going to be utilizing Ethernet/IP. I'll check out Kinco as we are always looking for more equipment options. My boss loves the Weintek screens for their price point so we utilize them alot on smaller pieces of equipment. Problem we have is there is about 6 generations of Weintek screens on our shop floor and they all use different software so our technicians get all turned around on which one to use. I wont lie, I love FTVS ME for HMI work. I've been working on specing out the gripper today. There are so many options its a little over whelming.
A possible addition of a vision system would be nice too, some time down the road.
Display MoreLooking good.....
That's quite a substantial cell indeed, plenty of area for test gear, storage and accessibility.
Will you be adding a small pedestal for the Robot at all - you will get a little more freedom of motion.
I don't know about your overall design, and do not really want to intrude by saying, 'you could have this' or 'you could have that'.....but I have to...
Something that I was going to implement in mine is:
1. Sliding shelf for the Controller and other equipment using
- https://accuride.metrol.com/light-duty-ran…ByABEgIVXfD_BwE
2. Top hinged side table with lockable joints covering the sliding shelf area.
- Folds out to provide a work table for PC, Monitor, Laptops etc and include a lock, so when folded down, locked to secure the storage area.
So much potential there my friend, I find myself clawing at the screen in envy.....
Many thanks for sharing and looking forward to see the further developments......
I've definitely considered adding a pedestal, we'll see what's left in the budget after I get my electrical panel built. Designing that has been my main focus here lately. I love the suggestion of a slider for the controller and a programmers table/nook. We will be utilizing this as a complete automation trainer for our technicians so the control cabinet could be described as excessive, but in a awesome way. We are going to have a Compact Logix PLC with digital +analog IO, and Ethernet cards, a MicroLogix1500, a Kinetix Drive, a Powerflex 40 Drive, PVP7 HMI, a Wientek/Maples HMI. This will be my first complete integration from the ground up so its been a slow process but I think its going well!
I don’t know if anyone is interested in this but I thought I would update everyone on the status of this project. It’s starting to come together slowly.
price please
Please see your private messages.