Skip to main content

How to Update Robot Config Files

Follow these instructions after updating ForgeOS on the READY pendant.

caution

Updating the robot controller configuration files is crucial to ensure that the robot behaves as expected with the new ForgeOS version.

Getting Config Files

Open the Device Configuration app.


Select your configured robot and tap Edit.


Insert a FAT32 USB drive with at least 2GB of available storage into the IPC.

Tap ​Start Transfer​.


Wait for the transfer to finish​, then remove the USB drive.

Connecting your Computer to the Controller

Open RobotStudio on your workstation/laptop.

If you have not purchased a RobotStudio license, click Cancel in the "Activate RobotStudio" pop-up. You can perform these steps with the basic RobotStudio version.

info

You don't need to install RobotWare on RobotStudio for this setup. Click No if you see the below pop-up.

Use an Ethernet cable to connect your RobotStudio computer to the ABB controller service port: X2.

note

Refer to ABB documentation for more information on Ethernet routing. Depending on your setup, you may need to plug this cable into a different port.

Configuring IP Settings

On your computer, configure the IP settings to connect with the controller:

note

The below substeps assume that your computer is a Windows computer. If you are not using a Windows computer, follow your computer's procedure for configuring IP settings.

  • Open the Run box by pressing Windows key + R on the keyboard or right-click the Start Menu button and select Run. In the Run pop-up, type "ncpa.cpl" (Network Connections panel) and click OK.

  • On the Network Connections window, double-click the Ethernet connection that you are using on the computer. For computers with one Ethernet port, it's the Ethernet option.

  • In the Ethernet Properties Networking tab, double-click Internet Protocol Version 4 (TCP/IPv4).

  • In the IPv4 Properties pop-up General tab, select Obtain an IP address automatically. This allows the DHCP server to automatically assign your computer an IP address for communicating with the robot controller.

  • Click OK to save these settings.
info

Selecting Use the following IP address instead is also valid, but make sure that the IP address that you are manually entering is compatible with the robot controller and doesn't interfere with other devices. For example, try setting the static IP address to 192.168.125.3 and the Subnet mask to 255.255.255.0. If you get errors later on, come back to this screen to try different settings.

Connecting to the Controller in RobotStudio

Select the Controller tab at the top of the screen.

Click the Add Controller dropdown and select One Click Connect.

info

If the controller doesn't connect, follow the instructions in the error pop-up for checking your Ethernet cable connection and your IP configuration settings.

note

If you see the following pop-up, click Log in as Default User if you don't have a Username and Password.

Backing Up the Controller

Click Backup at the top of the screen, then select Create Backup.

Choose where to save your backup, then click OK to start the backup. Wait for it to finish.

Factory Resetting the Controller

With the mode switch on the ABB controller set to AUTO, click Request Write Access. This allows you to edit settings on the controller.

Reset the controller to its factory default settings:

caution

A factory reset (I-start) is recommended because it kills all currently-running programs and guarantees that there will be no conflicts during the ForgeOS file transfer. You could try skipping this factory reset step, but if you get errors later on in the setup process that prevent ForgeOS from communicating with the robot controller, come back to this step to do the factory reset. Before performing the factory reset, take note of any settings that you have set in RobotStudio that you do not want to lose, and make sure that your backup files are stored in a safe place. Later on in this guide are instructions for restoring the backup EIO.cfg file (if applicable).

  • In the Controller tab, click the Restart dropdown at the top of the screen, then select Reset system (I-start).
tip

If the Restart menu is unavailable, try pressing the ABB controller's E-Stop to stop motion programs.

  • Click OK to confirm the factory reset. Wait for the controller to restart and reconnect to RobotStudio.

Transferring Files

Click Request Write Access to regain access.

Connect the USB drive with the ForgeOS robot driver files to your RobotStudio computer.

Follow these steps to copy the ForgeOS robot driver files onto the controller:

  • Select the File Transfer button.

  • In the PC Explorer, find the ForgeOS robot driver files on the USB flash drive in forge_os\ready-abb-driver. Select all of the .sys and .mod files.

  • In the Controller Explorer, find the HOME directory. Open the new READY folder that you created when initially setting up ForgeOS.

  • Click the arrow that's pointing to the right to transfer all of the driver files into that folder.

info

If you don't delete the existing files in the "READY" folder before the file transfer process, click Yes in the pop-up that asks you if you want to overwrite these existing files.

Follow these steps to copy the controller parameters onto the controller:

  • Select the Load Parameters button.

  • At the bottom of the Open window, select Delete existing parameters before loading.

  • Open the folder named Config in the USB drive. Select all of the .cfg files, and then click Open to load them.

  • If RobotStudio warns you that existing parameters will be deleted, press OK.

  • If RobotStudio asks you to restart the controller, press OK to clear the pop-up. However, to save time, wait to reboot until you do the next section (if applicable).

Restoring IO Signals

(Optional) If you have a previous IO configuration that you wish to restore from a backup, follow these substeps.

info

These substeps assume that the backup EIO.cfg file already consists of the default ForgeOS signals followed up your custom signals (from previously following either Configuring Robot IO From Scratch or Restoring IO During Initial ForgeOS Setup).

  • Click Load Parameters.

  • In the Open window, select the EIO.cfg file from the SYSPAR folder in your backup folder. Select Load parameters and replace duplicates then Open to load your new signals.
info

This option will reload your new signals to the bottom of the EIO.cfg file (below the default ForgeOS signals). Because your backup file already includes the default ForgeOS signals, these signals are considered "duplicates" to the ForgeOS signals that you loaded in the previous step.

  • If RobotStudio warns you that duplicate parameters will be replaced, press OK.

  • If RobotStudio asks you to restart the controller, press OK to clear the pop-up.


Restarting the Controller

Restart the ABB controller by selecting Restart (Warmstart) in the Restart dropdown. Wait for the restart to finish. Keep the ABB controller set to AUTO mode.

tip

If the Restart menu is unavailable, try pressing the READY pendant E-Stop or the ABB controller E-Stop to stop motion programs. This will allow you to be able to warm-restart from RobotStudio. Then, after the controller finishes booting back up, release the E-Stop and press RESET to clear any errors on the READY pendant. (You can also use the power switch on the robot controller instead.)

info

If you restored a previous IO configuration from a backup file, follow these steps to resolve the ForgeOS IO configuration mismatch warning:

The ABB pendant now displays a message that says, "An update has been ordered. An update of program configuration is done." Acknowledge that message to clear it.

The READY pendant displays an “I/O Configuration Mismatch” warning. This section covers how to clear this warning and use the new IO signals that you created.

In Device Configuration, complete these substeps:

  • Select your robot device and tap Edit.

  • Tap ROBOT IO CONFIGURATION to edit the robot’s IO configuration.

  • Tap ACCEPT NEW to accept the new IO configuration.

  • Verify that your new signals appear at the bottom of the table.

Check if you need to re-add the Display Names of your signals, then check if the signals correctly re-populated to Task Canvas tasks and Rule Engine rules.