You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing firstname.lastname@example.org.
We are experiencing playback issues from our video hosting provider. Please check back shortly.
3:52What is Ignition
1:42Understanding Ignition's Basic Flow
1:52About Ignition's Modular Architecture
4:53About Ignition's Modules
Take topic challenge
Understanding Ignition's Basic Flow
The basic flow in Ignition is to first launch the Designer from the Gateway, then you configure your project in the Designer and save it back to the Gateway/Server. You will then launch the Client, there are no limits to the number of Clients you can launch.
Video recorded using: Ignition 7.7
Transcript(open in window)
[00:00] Ignition is installed as server software and is web-based, so you can install Ignition in a single place designated as the server. Ignition is cross-platform. It can run any flavor of Windows, Linux, and Mac OS 10. Since Ignition is web-based, you can access Ignition anywhere in your network, by using your web browser. Any web browser will work, such as Firefox, Chrome, IE, Safari, and more. Once you access the Ignition Gateway Webpage, configuring Ignition is easy. The basic flow is to first open the Designer from the webpage. The Designer is web-launched, and will be downloaded onto your machine from the server. The Designer is included with the product and as a single place to configure your project. Once you configure your project, you simply save your changes in Designer, and the project is sent back to the Ignition server or Gateway. You can configure HMI and SCADA screens, the Historian, Alarms, Recipe Management, Reporting, KPI Monitoring, Database Applications, and more. Once the project is saved on the server, it's available to launch as a runtime for a client. You can open a runtime as easily as the Designer. There is no installation needed on the client machine to launch the runtime. You just simply click on the link to open the client. There's no limit on how many clients you can launch, as well. So the basic flow to open the Designer, configure your project, save your changes, and open the runtime. Another benefit on being server-based is that when you make a change to the project in the Designer, the change is automatically sent and updated on all the running clients. You don't have to worry about restoring a backup on all your client machines. We will show you all of this flow in an upcoming course.