Q: From my engineering workstation, I need to support different jobs at different software release levels (for example: 3.7, 3.8, 4.0). Is there a recommended method to do this?

A : You can install different release levels on your workstation, and keep them separate by installing them in different locations. To run stations locally, remember to check which platform daemon is running at the time (from command prompt: services.msc and look at Niagara service). As needed, use the shortcut Install Platform Daemon to start the appropriate platform daemon.

Q: Is it possible to select which modules are installed?

A: By default, the installer installs all modules in your !modules folder. These include all the online versions of software documents, such as (Getting Started with Niagara) and so on, various lexicon modules, and all the software modules, including ones for drivers and other features.

Q: Does Niagara require changes to my Windows Firewall?

A: Most configurations work with the default ports. You would make changes to your firewall to run a station locally on a PC with other remote stations connected to it, or to allow a remote Workbench client to connect to the station and platform on this host.

Q: When installing Niagara on a Supervisor, is the software supposed to be installed with the “use as install tool” box checked? Is there any reason not to check this box?

A: This box is optional because the installation is 200MB bigger when it is selected. You need to have it checked if the Supervisor will be using provisioning to install software to subordinate controllers, or if you want to use Workbench from that computer to upgrade software on a controller.

Q: What is the difference between wb_w.exe and wb.exe?

A: Starting Workbench using wb.exe starts an associated console window that provides debug information for the client Workbench application in much the same way that the application director provides server-side debug information for the station. It is typical to start Workbench using wb.exe when trouble shooting client side issues.

Starting Workbench using wb_w.exe launches the program without a console window. You may prefer to use wb.exe because of the console. If Workbench freezes with a console open, you can quickly terminate the program by closing the console window.

Q: I’ve got different versions of Workbench installed. When is it really necessary to start the platform daemon?

A: You only need to start the platform daemon when you are planning to run a station locally. However, it does not hurt to get in the habit of loading the platform daemon for the current release each time you launch Workbench. Some customers use batch files for starting the platform daemon followed by starting the program. This simplifies things because you can just double-click the shortcut icon for the particular version and brand of Workbench you need. Customers share such solutions on Niagara-Central.