Professional Documents
Culture Documents
Release Notes RW 6.08.01
Release Notes RW 6.08.01
RobotWare
6.08.01
GENERAL .................................................................................................................................................................... 2
How to Migrate from RW5.x to RW 6.x ..................................................................................................................... 2
How to Migrate from RW5.6x to RW 6.x ................................................................................................................... 2
How to Migrate from RW6.x to RW 6.08.01 .............................................................................................................. 2
Release Name
The release name is RobotWare 6.08.01
The release contains following:
• RobotWare 6.08.01
• RobotStudio 6.08.01
Controller Hardware Support
Main computer unit:
DSQC1000
DSQC1018
DSQC1024
Flexpendant unit:
SxTPU3
Drivesystem:
DriveSystem 09
Industrial Networks, PCI-express boards
DSQC1006, DeviceNet Master/Slave – 1 channel Option 709-1
Local IO System
DSQC1030 Digital base 16Input, 16Output
• Swedish 1)
• Danish 1)
• Czech 1)
• Hungarian 1)
• Finnish 1)
• Korean 1) 2)
• Japanese 1) 2)
• Russian 1) 2)
• Turkish 1)
• Slovenian 1)
Notes:
1) The language is only supported in the controller and Flex Pendant
2) The language support for Asian languages (Chinese, Korean, Japanese) and Russian has some specific limitations:
- TPWrite, TPRead, and TPPrint do not work – use English text.
- Printing error text from RAPID (instruction ErrWrite) does not work - use English text.
Incompatibility
RobotWare 6.08:
Parameter remove_corner_path_warning replaced
The functionality of the configuration parameter remove_corner_path_warning has been replaced with the
rapid-instruction CornerPathWarning. For example, CornerPathWarning FALSE, will suppress the warning
messages.
For further information, see "RAPID Instructions, Functions and Data" types on the instruction
CornerPathWarning.
CIP Safety Scanner cannot connect to POINT Guard I/O Safety Modules from Allen-Bradley (e.g. 1734-
OB8S, 1734-IB8S)
POINT Guard I/O Safety modules are mounted on an EtherNet/IP Adapter (e.g. A-B 1734-AENTR) and are
not directly accessible from the EtherNet/IP network thus, from our scanner.
To access such modules the scanner should send a special Forward Open request containing CIP Routing
information
(for details see THE CIP NETWORKS LIBRARY Volume 1: Common Industrial Protocol Specification,
Chapter 10: Bridging and Routing).
Note:
On the market exist CIP Safety EtherNet/IP I/O devices of modular construction that don't require CIP
routing information when establishing connection e.g.: ABB Safety Local I/O, PSS u2 P0 F/S EIP.
The ABB CIP Safety Scanner in RW6.08 connects to such.
Backups with the CIP Safety Adapter option (997-3) need migrating to RW6.08
Migration of a backup is necessary before restoring it in RobotWare 6.08.
This applies to backups created in RW systems version 6.05.xx-6.07.xx with the CIP Safety Adapter option
(997-3) present.
In previous versions two separate EtherNet/IP Internal Devices were present in I/O System Configuration
when the option 997-3 was present, one for non-safety EtherNet/IP and the other for CIP Safety
communication.
In RW>=6.08 only one EtherNet/IP Internal Device is necessary.
The migration deletes the unnecessary internal device and remaps safety signals if needed.
Note that after migration the safety signals when viewed in "Controller->Configuration->I/O System-
>Signals" will be mapped outside of the Device Map defined by the Internal device.
This will not affect the checksum or validation status of any configured safety configuration.
To carry out migration perform following steps:
1. Create a backup in the old system, RW<=6.07.XX
2. Install RS6.08/RW6.08
3. Migrate the backup using RobotStudio 6.08
Not possible to have group signals over more than one module
It is not possible to have a group signal mapping over several modules, e.g. over a device with several
modules (device/module/submodule). It is only possible to create a group signal over one module.
RobotWare 6.08.01:
IOC: Configuration of Fast Startup and Portspeed
Configuration of Fast Startup and Portspeed has changed in RW6.08.01, and it is now required to have the
proper GSD file to change it.
On device configurations not created with IO configurator, it is possible to view settings for Fast Startup and
Portspeed, to change it the device has to be created with IO configurator.
New Functionality
RobotWare 6.08:
Activate and deactivate warning 50024
CornerPathWarning is used to activate and deactivate corner path failure warnings (50024 event log).
Syntax:
CornerPathWarning
[ Active' :=' ] < expression (IN) of bool > ';'
In earlier robotware versions it was possible to remove the warning with the configuration parameter
"Remove Corner Path Warning".
The instruction replace this configuration parameter, and makes it possible to activate and deactivate
report of warning in runtime.
The recommendation is to have the corner path warning activated. Turn off the corner path warning only in
situations where a warning sometimes occur. Such situations can be when waiting for some input (from
I/O, cameras, sensors or other external equipment).
A corner path warning can result in bad process performance and will lead to worse cycle times.
All those situations needs to be analyzed before removing the corner path warning.
A corner path failure occurs when the robot is executing a corner zone move instruction and the RAPID
program execution does not provide a new move instruction in time.
This forces the system to convert the programmed fly-by point to a fine point.
motsetdata updated
A new Boolean component corner_path_warn_suppress has been added to motsetdata.
Improved zone behaviour
Functionalities for increasing the utilization of the zones has been added.
See System Parameters manual for "Relative zone size with finepoint" and "Allow asymmetric zones".
Limitations:
- Parameters will not be used at conveyor tracking.
- The function works when the conjunctive move instructions are of the same type (i.e. MoveL to MoveL)
- The function works when the same workobject is used.
- The function does not work in MultiMove.
To disable the message box simply add the attribute SilentMerge="true" to the new project setup file, as:
For apps the following values are affected: ApplicationName, AlertSignalName, ErrorSignalName, ImageName
and Index.
For widgets the following values are affected: WidgetName, OverrideDefer, PageId, Position, PositionLocked,
ZIndex and ControllerBindings.
Note! Project settings are never merged, old settings will remain unless the file is replaced.
RobotWare 6.08.01:
IRC5 OPC Server
Members of Rapid record of one dim array can be read / written as a single variable
BullsEye
BullsEye needs a fast EIO signal to work properly. The recommendation is to configure the input signal from the
BullsEye beam as Change of State (COS) and not as Polled or Cyclic.
From RW 6.08.01, an error elog 111542 will be displayed if the used signal is not configured as Change of State
(COS) when executing the BullsEye instructions.
Information
RobotWare 6.08:
Virtual FlexPendant not loaded in VC due to faulty Temp-folder path
From 6.08 and forward, the local system temp path will be used; hence it will always be there.
Workaround for older systems is to manually create the temp folder on root level if it is not present.
Note that this behavior is by no means new; it has been there way back (meaning, no temp folder
executing in VC = faulty behavior; for most users this will never surface since most are running on C: where
temp usually exists on root level).
The last instruction shall preferable be a comment or something else then a NoStepin-routine.
Changing mode from forward to backward while in the last instruction before ENDPROC, the program pointer will
not be moved to the previous instruction.
Work around: Add comment as last statement in all procedures with NoStepin routines.
Calibration forces
In this release the automatic recalculation of the calibration forces has been removed when running the force
calibration sequence.
DSQC1024 support
The new computer board for IRC5, DSQC1024, is fully supported in RW6.08
CIP Safety Adapter/Scanner
RobotWare with options:
• CIP Safety Adapter (977-3) or
• CIP Safety Scanner and Adapter (997-4)
Does not support CIP Safety multicast connections.
Example in python:
session
= requests.Session()
resp
= session.post(subscription_url , auth=digest_auth, data=payload)
RobotWare 6.08.00.01:
Motion Supervision events on wrist axis
In 6.08 there was a limitation in torque calculations that could cause false Motion Supervision events from wrist
axis on some robots. Eg. IRB1410 and IRB1600.
This has now been solved.
LLDP functionality when Robot Controller acts as both Controller and Device
When running a system with the device option, the Robot Controller will use LLDP version Legacy.
With LLDP_ChassiID in conjunction with MulipleInterfaceMode.NameOfDevice == 0.
According to PROFINET Standard
Technical Specification for PROFINET IO Version 2.3Ed2MU5 – Date: March 2018 Order No.: 2.722
Section 4.11.3 LLDP transfer syntax
The RC will adjust LLDP version when it receives a PDPInterfaceAdjust setting the multipleInterfaceMode = 1.
Note! That the behavior of the Robot Controllers LLDP version is separated from the LLDP version configured
for the controller network. Eg if the user configures a PROFINET network with several external devices using
LLDP version standard, the Robot Controller will still use LLDP legacy mode until an PDPInterfaceAdjust has
been received.
RobotWare 6.08.01:
Option 606-2 Indexing Conveyor Control
Option 606-2 requires DeviceNet option 709-1
Configuration of PROFINET external devices requires the GSD file to be present in the system
The existence of the GSD file is necessary for the configuration of external PROFINET devices to be correctly
configured from the IO Configurator.
If a old configuration must be changed and no GSD file for the current device exist, it may be required to import a
GSD file to be able to change the configuration.
GSD file needed for device with DAP on other slot than slot 0
If there is a DAP on another slot than slot 0, it is necessary to have the GSD file present when configuration is
created.
Corrections
RobotWare 6.08