I got it. I double checked the produced and consumed tag values with the EDS again, and I guess I did have it backwards. I have communication now. Thank you again for the support!
Posts by dohlfhauldhagen
-
-
Thanks for the replies guys. That last picture of the Balluff config is just from the manual, so that IP address is not reflective of what I'm actually using. All are on the same subnet and I can ping all devices from my PC. I do have the EDS as well and did verify that producing and consuming values were correct. Like I said, I'm extremely new to the Kawasaki system and right now I'm just using equipment we have around the shop to teach myself.
Unfortunately, I am on the road now for a different job and can't look into some of your suggestions right now. Hopefully I will be able to later this week and provide an update.
-
Hello all. I'm very new to Kawasaki after being used to ABB and Fanuc for most of my career. I have an MX350L robot on an E controller, and right now I'm just playing around trying to familiarize myself with the programming environment.
Right now I have a small test network setup with an Allen Bradley PLC, a Balluff input block, and the robot. I have the robot connected to my switch via port 2, and everything is assigned a 192.168.11.xxx address. I was able to establish comms between the PLC and robot as an adapter, however I am really struggling getting the robot to communicate with the IO block as a scanner.
Attached is a pic of my PLC config to talk to the robot, my network setup for the adapter, and my config settings for the scanner device. The pic also shows the assembly and input/output instance settings for the Balluff block from the manual. If I make the PLC the owner of the Balluff block with these settings, it works just fine. But I want the robot to have control over this device, not the PLC, and that's where I'm running into trouble. After I set this all up and run the TYPE EIPSTATUS(1) command in KRterm, I always get a 0 indicating that there are no communications between the robot and the Balluff block.
I should mention that I am referencing the General Fieldbus I/O Usage Manual. And I should also say that it is somewhat confusing for me. I don't really understand what the manual means when it talks about allocating signals as master or slave. I'm not used to seeing this terminology anywhere except for when I've worked with Devicent in the past. I also cannot seem to get the ZSIGSPEC command to work, as KRterm says the operation is not allowed. On top of that, I don't really even understand what this command does, as the manual does not do the best job spelling it out in layman's terms.
Any direction on this would be super appreciated, thank you.
-
So about half a year ago ABB updated RobotStudio and removed all colors from the interface. Normally I'm not one to complain about UI changes, but the fact that they removed all color has made it difficult to navigate and find what I'm looking for at a glance. I've messaged ABB and looked on their forums to similar threads where people have protested the change, and they seems completely uninterested in reverting this change or even giving an option to.
Does anyone know of a way I could restore the icons to the old style without downgrading my RobotStudio version? I tried digging around the program files for the program, but I was unsuccessful in finding any of the icons to replace. I'm guessing that they're embedded in some dll file that I cannot edit, unfortunately.
I know it's a long shot, but doesn't hurt to ask. Thanks.
-
I figured it out, for anyone else with this question, yes you do need some sort of external brake control in addition to DCS, at least that's what I'm gathering from my conversations with Fanuc. I did find one made by Fanuc already integrated into the controller with part number A05B-2605-C400.
-
I am designing a cell that has an R-30b Plus Controller. This contains a dial table with a trunnion on each side. I'd like to be able to disable one of the trunnions and the dial while the operator is loading one side of the table, and keep the other trunnion active that the robot is working on. Do I need to use a local stop to accomplish this? I was under the impression that DCS would be able to handle this, but I'm being told by my customer that I wont have individual brake control over each axis, and that I need to have a separate brake control unit to do this. I talked with Fanuc, and they weren't very helpful. They told me that the local stops are "out of the scope of the robot" and to contact my vendor about it, who I'm still waiting to hear back from. According to a doc shared with me, local stops are interfaced with the CRM97 connector on the 6-axis servo amplifier.
This just threw me in for a loop because I have worked on similar systems to this before, and I don't recall ever seeing an external brake control box on any of those cells. Does anyone here with experience on this have some input? Can I get by with this using just DCS? Or do I need DCS in conjunction with the local stop? Thank you.
-
Hello. I'm wondering if Nachi has a tool where you can enter in mass and CoG values of your end of arm tool and have it calculate if the robot is capable of carrying the tool. Fanuc has an Excel spreadsheet that can do this, and ABB has a program that can, and I'm wondering if Nachi does as well. Thank you!
-
Hi, maybe i'm late to answer this question, but i just found out that by clicking the simulation button you can increase the Run-Time Refresh Rate.
About six years late! Haha. I still have performance issues with this software. Unfortunately I'm not talking about what that slider does. All that does is change how often the sim updates the robot's position during simulation playback. What I'm talking about is raw performance while programming a simulation. When I add large CAD files to Roboguide, performance can get very choppy. I recently upgraded to a new computer with a 3080Ti that I had hoped would help fix the issue, but unfortunately, Roboguide is so old and terribly optimized that I don't think it's able to take advantage of newer hardware. Gotta love that we pay thousands of dollars for this crap.
-
Pretty much what is happening is whenever we get a weld error with our spot weld guns, or a DCS joint speed error, the collision guard on the robot turns off automatically and has to be put back into T1 mode to manually re-enable it. I've never seen anything like this before, and support so far has been unhelpful. Has anyone seen something like this before?
Thanks.
-
Thank you so much! I will check those out!
-
It all depends on where you are located. I know of a few places in the UK that I purchased robots from or commissioned robots that they supplied, but I am not sure if the rules here permit me to mention any of them.
Thank you for the suggestion, but unfortunately I'm in Michigan in the US! So the UK probably wouldn't be very practical.
-
I'm looking for a small used robot like a Fanuc LR-Mate or something similar (Abb, Kawasaki, or any other manufacturer really) for as cheap as possible for a personal project. Does anyone know of a reputable dealer or any advice on ways to find older used equipment for cheaper? Thanks!
-
In program PlaceWarmTray, are you referencing .arg1 at all?
Yes. Here is the full program:
-
Hey all. I'm working with a Duaro 2 robot.
I am trying to pass an argument to a program via a subroutine call from an AS program. The AS program I am calling looks like this:
.PROGRAM PlaceWarmTray(.Arg1)
<code here>
.END
I try to call it from my main program like this:
CALL PlaceWarmTray(1)
Every time I try to run the program, I get “Error Code 2018 Check the argument settings in macro pg” on the tablet. The confusing thing is, when I call the program from a tablet program and enter in an argument that way, it works just fine. It just doesn’t work when the program is called from an AS program. Has anyone run into this before?
Thanks!
-
You are absolutely correct! I removed my license key and opened my program with the Duaro robot. It powered up and connected the controller just fine. I then tried re-adding the license file and the error came back. So it would appear that my trial license is limited. Hah!
Thank you for the help. I will have to get in contact with Kawasaki to get a new trial key.
-
Here is my version. It appears to be slightly newer, but I find it hard to believe Kawasaki would remove this functionality in such a minor revision update. I am in contact with the Kawasaki employee who gave me the software, so hopefully we can work through it.
That is what I have been doing. Open robot file, navigate to that directory, add the robot. It loads the model in just fine but always gives me that error.
I tried reinstalling the software today and on the install dialogue, I did a custom install and made sure that the handling(special) option was installed. It still isn't showing up under my add robot screen though.
-
Duaro has been included as standard since version 1.7.2, and the fact it is present in the standard robots folder suggests it is there.
Are you using the 'Lite' version or have you got a trial license or using a USB Key?
Can you post some screenshots of your robot selection process you are attempting?
I am using a trial version that I got directly from Kawasaki to run a simulation on a robot that they supplied to our customer. I definitely do not have that Handling(Special) category on my install. I'll attach a picture of what I do have for selection, and also the error I am getting when I manually open the robot file.
-
Have you looked in the Kawasaki/Hisui/Documents folder for the Duaro Handling project manual?
- This is normally installed as standard with KROSET.
- It goes through the setup of this.
- It normally resides in Handling(Special) in the application drop down window when you add a robot.
Thank you for the reply. I do not have a Handling(Special) section in the drop down windows for adding a robot. I was able to find the robot file in the C:\Program Files (x86)\Kawasaki\K-ROSET\Hisui\KHIlibraries\Robots\Standard folder. However, whenever I load in any variation of a Duaro robot, it gives me a "cannot connect to controller" error, and all of my settings on the bottom of the screen in the controller tab are greyed out.
-
Pretty much as the title states, I am using K-Roset 1.8.1 and I am trying to simulate a Duaro 2 robot. I know it can be done, as I've seen videos of it. I can't find this robot anywhere in the list of robots, however.
-