want your opinions: Kawa, R-Series, AD language, controllers, functions

[TygerDawg]

A situation has developed that makes me consider Kawasaki robots for an application, and I have no experience with Kawa.  They seem very impressive.

I'd would very much like to see some opinions from actual users:  the new R-Series arms, reliability, Kawa service & support, Kawa applications engineering support, "strength & power" of the programming language for Keyboard programming not Pendant programming, controllers, path accuracy for precision path applications, multitasking, arm stiffness, advanced programming functions, relative price compared to similar arms, networking, integration ease,....those types of topics.  Both good stuff and bad stuff, would like to see it all.

Many Thanks

[roboperson]

The R series is the latest robot replacing the F series. The R series. It is attached to the E controller. From what I worked with the R series is a fast and reliable robot. It has a small footprint and in many respects reminds me of the motoman. The E controller is pretty nice. It has several features that are nice, and K logic can run a small cell without a secondary PLC if done right. AS language is a powerful language if you understand it. It is based off of C and is an advanced version of VAL. You can program in what Kawasaki calls blocks step which is line for line, AS language which is more like Ccommands, or a combination of both. The E controller finally stepped up and uses USB instead of flash cards, but they have pretty decent computer interfacing programs. Controlnet, devicenet are available but everything comes with a price, if you go in knowing what you want you will probably be ok, but run the possiblilty of getting many bells and whistles you dont want that could complicate it to the point of irritation. Phone support is a phone call away for free, but depending on how complicated it gets, they will try and get you to get a service call. im not sure on time of service calls, but production emergencies come first, then everything else is first come first serve. post your email and i will try to reply more one on one about things beyound this. Best of luck.

[rdixiemiller]

 I am quite fond of the D and  D+ controllers, the E controllers are upgraded a bit. The software is quite powerful, and easy to program offline. I do 99% of my programming on a laptop, only using the TP to set points. Most of my program loads (software only, not including data or variables) run about 5000 lines. I mostly do material handling, with lots of branches and subroutines.
 I have had some mechanical issues with the F series robots, mainly gear reducer failures. The R series are supposed to be improved, we shall see.

[TygerDawg]

Many thanks Guys, please keep the comments coming. 

My work is primarily developing very complex intricate accurate paths with RobotWorks software, usually impossible to do so with a teach pendant.  So teach pendant programming is only for teaching frame setup and transition points.  I prefer to do all the programming offline.  With lots of experience with Staubli and their Staubli Robotics Studio programming environment, I'm spoiled rotten by the VAL3 language power, TP menu writing capability, networking, multitasking capabilities, and integrated programming environment.  I'm trying to get a feel for how Kawasaki's offerings stack up against those expectations.  That is, without having to call Kawa directly and suffer through a sales pitch (yet).

[roboperson]

AS Language is based on VAL. AS stands for Advanced Superior. I think you would flow right into writing with AS and programming. Kawasaki uses block Step (TP) AS(Commands) and a combination of both. I programmed in VAL@ in college and it was basically all the same. Just some minor modifications.

[rdixiemiller]

 I find the Kawasakis are much easier to program than a Fanuc using RoboGuide. I can do a Kawasaki in about 1/3 the time. I generally write all the code, and drop in some transition points. The transition points, and the basic frame reference points are all that actually get taught with the pendant. I use UltraEdit on the Kawasakis, then just dump the program in. Fanuc is not as easy or quick. That being said, RoboGuide is great if you have good drawings of the cell and want to do your pathwork offline. Kawasaki has PCRoset, their version of RoboGuide. It is slow, clunky, and loves to lock up when you least want it to. I spent 3 months working with PCRoset before I gave up on it. I don't know of anyone other than a couple of engineers at Kawasaki that actually use it. I have not tried any of the aftermarket offline packages, my company is too cheap for that!
 My opinion is that Fanuc builds a better robot. I have had more mechanical breakdowns with Kawasakis that were a year old than I ever have with Fanucs that were 10 or older. The controllers are about the same between the two. Kawasaki software is easier to use, and I think more powerful out of the box. I understand you can do a lot with Karel, I just never used it.
 Never used a Staubli, so I can only compare the two robots I have the most experience with.