Upgrading an Inductive Automation Ignition installation is a very straightforward process. Generally, if you download and run the installer for the version you want to upgrade to, it will be good to go. Corso Systems has performed a number of upgrades from various combinations of version 7.3 all the way through the newest nightly build, and we’ve learned a few things along the way. First, here’s a link to the official documentation for installing and upgrading Ignition—it’s recommended if you are installing on Linux as it contains the commands you need to make the executable able to run.

Step 1 - Make a Gateway Backup

Before you touch anything, the best approach is to take an Ignition gateway backup first. This will let you restore your current configuration if anything goes wrong, or in the case of some minor and most major version upgrades, it will let you restore the backup in a newly installed Ignition gateway without any headaches.

Step 1a (Optional) - Copy/Rename the Ignition Directory

In addition to an Ignition Gateway backup, you can also make a copy of your machine’s Ignition directory and rename it something like Ignition_BAK. This will let you get back to where you were without having to restore a gateway backup. You will only need to stop the existing gateway, delete the Ignition install directory, then rename Ignition_BAK to Ignition, then restart the gateway. This strategy will allow you to return to the starting point with no issues if something goes wrong with the upgrade.

Step 2 - Do You Need to Update Your License?

If you are doing a major version upgrade (e.g. going from version 8.0 to 8.1) you will need an updated license from your Inductive Automation sales rep. Reach out to them for a license refresh for your version upgrade. If you forget to do this step, it’s not a problem, but you will be put into a 7 Day Emergency Activation mode when you apply the old license after the upgrade. …And you will still need to reach out to your sales rep. ***NOTE*** The 7 Day Emergency Activation mode requires that your license has upgrade protection support, which you can add to your system if you didn’t include support in your original Ignition purchase.

Step 3 - Download the Appropriate Installer (and modules if necessary)

Visit the Ignition Downloads page and get the version of Ignition you would like to install along with any modules you might need, especially 3rd Party Modules. ***NOTE*** if you are using Sepasoft’s MES modules, you should also visit the Sepasoft Downloads page to verify the version of Ignition you are using is compatible with the version of the Sepasoft modules you are using. You might run into problems if you are using MES Platform 1 or 2, or if you are trying to upgrade to the newest version of Ignition shortly after it is released and hasn’t been tested by Sepasoft for their platform 3 modules yet.

Step 4 - Run the Ignition Installer

Next, run the Ignition installer. It should recognize that you already have Ignition installed and are upgrading, then it will take the appropriate actions. Depending on what version you have installed, the operating system you are running, and what version you are upgrading to, you might run into some errors. A common example is when upgrading an Ignition gateway installed on Linux from a version prior to 8.0.14 to one that’s 8.0.14 or above. The file system structure changed on Linux and the installer will fail.

If you run into any errors, the easiest solution is to take a backup and/or copying and renaming your install directory before uninstalling Ignition from your machine. Next, do a fresh install of the new version, then restore your Ignition gateway backup into the new gateway. This will ensure that your file structure is correct and everything works as expected. We know this procedure from experience having run into this issue with a subsequent tech support call!

Step 5 - Commission the Gateway

When the installer finishes, you should automatically land on the gateway webpage. If not, you will need to navigate to it in a web browser. On the page, accept the license terms, and click the version of Ignition you are using (Edge, Standard, or Maker). Run through the commissioning process, which should be short if you have a previously configured gateway. If you are restoring a backup into this gateway, you can use the defaults to start—they will be overwritten when you do the restore.

Step 6 - Refresh Your License

Next, go to the licensing page and click the “Update License” button to get the latest and greatest license version from the Ignition servers. Or you can use the offline mode if necessary on your machine. After your license has updated to the new version, you are on your way.

Step 7 - Install Additional Modules As Needed

Next, go to the Modules page and add any modules you need that weren’t automatically upgraded as part of the Ignition installation. When you are done, all of the modules you have licensed should appear as “Activated” and “Running.”

Step 8 - Validate Functionality

The final steps in the upgrade process are to validate that the new system works as expected.

• First, we generally look at PLC communications, tags, alarms and UDTs.

• Next, we inspect any gateway network connections and remote tag providers, database connectivity, third party or other web-services, client functionality, and graphics.

• Then, we test and use the new screens to operate equipment.

• Finally we’ll dig into reporting and alarm notifications. If there are any issues, you will find them quickly and can address them at that time.

Generally there aren’t many things to fix, especially if you are only upgrading minor versions.

The issues we’ve seen with major version upgrades can include UDT parameters not working properly (which was fixed in a subsequent minor version release), and minor issues with tag bindings or database queries in scripting where the requirement to specify the database name or the tag provider name was enforced instead of just using the project default. None of these problems were showstoppers, we simply had to go correct a few things in the project.

Redundant Gateways

If you are using a redundant gateway, we recommend upgrading the master gateway first, then the backup—unless you are using the EAM module, in which case we recommend upgrading the backup first then the master, otherwise the process is the same as spelled out above.

Need Help with your Upgrade?

We hope this guide was helpful for your Ignition upgrade, but if you need additional help, or would rather have Corso Systems handle the upgrade for you, we’re happy to help! Complex systems can require additional expertise and we love a challenge!