BlogIgnitionIgnition Explained

Ignition WebDev Module

By January 18, 2019 July 23rd, 2019 No Comments

Ignition WebDev Module

Picture this:

You want to use Ignition’s Scripting engine to expose data to a third party service you can access using a URL. For example If you have the WebDev Module this is a solved problem.

Say you want to send alarms to Ignition then send a message to Slack to alert your team something has gone awry. This is use case is perfectly suited to the WebDev Module. Done.

Ignition as a Web Server

The WebDev module allows you to interact with Ignition’s web server as if it were a component on a screen and you were using the scripting engine to do something when the user interacts with the component.

Let that sink in for a second. Using the WebDev Module you can interact with an Ignition system using anything that can access a URL, as if it were a component on a screen. Same scripting engine, same capabilities with historical data, reports, images, you name it.

This takes things to the next level.

Let’s say you have a report. On a window, you would allow an operator to view the report by pressing a button. Instead of pressing a button, what if you could view the report by going to, then your browser would display the report with the time period of fromHere to toThere. Want to do this on your phone? Done. Just set up and endpoint in the WebDev module, add your scripting, and you are good to go.

Dream Bigger

The possibilities with the WebDev Module are pretty well endless. Anything you can do in the Ignition scripting environment can be done in this module. One fun use case we have done is to take an arbitrary number of PDF files and merge them all together into a single report, viewable on any device. Simply by passing in a desired lot number into the WebDev module.

Want to send an email to someone from Ignition, or a Slack message? Easy. You are working at a facility in Asia and want to send a WeChat message from Ignition? Done. (Check our API post for more info there)

WebDev, put simply, turns Ignition into an API. Anything you can do in scripting you can do here. We use it for the backbone to CorsoCare. We use it to expose reports to internal software management systems, and as a way to populate data for remote monitoring systems.

Want to do some comparisons with Siemens? Check out Corso’s take on Siemens Web Server!

Want more Ignition? Check out the full Ignition Explained series: here.