Welcome, Guest. Please login or register.
Did you miss your activation email?
February 09, 2012, 03:50:53 AM
Home Help Login Register
News: Any Problems or Experience with Industrial Robots ?
Register and place your Question / Answer to worldwide Robotexperts right here !

+  Robotforum | Support for Robotprogrammer and Users
|-+  Industrial Robot Help and Discussion Center
| |-+  Stäubli & Bosch Robot Forum (Moderators: Werner Hampel, Jim Tyrer, Martin H, Fabian Munoz)
| | |-+  Transitioning from CS7's to the CS8's
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Print
Author Topic: Transitioning from CS7's to the CS8's  (Read 1124 times)
RoboFutbol
Newbie
*
Offline Offline

Gender: Male
Posts: 16



« on: May 18, 2010, 04:28:17 PM »

We have three CS7A's and five CS7B's. I have been getting great support to date but know time is running out.

For those who made the transition, what were the biggest hurdles to overcome? What advice can you give me as we make the change?

Thank you in advance...
Logged
TygerDawg
Full Member
***
Offline Offline

Posts: 205


« Reply #1 on: May 18, 2010, 07:05:21 PM »

TX Arms are mechanically stiffer than equivalent RX arms, not as delicate.

Primary user interface is teach pendant, no more "keyboard & monitor" on the shop floor.

User software suite 'Staubli Robotics Studio' contains programming environment 'VAL3 Studio'.  Once mastered, is a joy to use.  But can still use pendant for programming in a pinch.  Pendant highly programmable for custom text-based user menus.

VAL3 language has a lot of "object oriented programming" aspects, so is powerful and more complex than V+.  For one example, to extract the RY value from a location in V+ it would be necessary to DECOMPOSE the location into an array of elements, then use that element.  In VAL3 the location variable is a data structure composed of a transform structure 'trsf' and other parts.  The RY component is directly accessible:  'myRYvalue=locationName.trsf.ry'

Infinite tasks available in the operating system.  Once you get the hang of multitasking, makes your application so much easier to manage different things going on.  Robot motion, pendant menu handling, ESTOP monitoring, TCP/IP communications, could all be separate tasks easily.

Makes extensive use of 'library' programming concept (if desired), unknown in V+.  For example, can write a single application for load/unload of machine with 'generic' part, tool, location names.  If need multiple different parts, then create multiple 'library' applications (that are loaded/unloaded by the main app) containing specific part, tool, location data.   Very clean solution, just requires more thought beforehand.

V+ language is old and mature, also very well documented over the years.  I think this is Staubli's major failure point.  Their VAL3 language documentation is complete, but weak for newbies.

Where are you located?  I have a friend who has asked me to keep an eye out for older CS7 equipment.  If your company is interested in selling, send me message and I'll get you into contact.
Logged

TygerDawg
Blue Technik
Virtuoso Robotics Engineering
www.bluetechnik.com
Juggernaut
Newbie
*
Offline Offline

Posts: 16


« Reply #2 on: August 18, 2010, 08:22:29 AM »

V+ is a programmers language shoved into a robot. Val3 is a robotics language made by programmers. Big difference and 100x better to use a language like Val3 for long term ownership. Much easier to learn and maintain val3 on the shop floor.   
Logged
Pages: [1] Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!