[Guide] Creating And Running A Niagara Station

:mag: Overview

In this guide we will teach you how to create and run a Niagara station locally on your PC.

:warning: In order to complete this guide you’ll need a licensed copy of Tridium Workbench installed on your PC


Lets Get Started

In order you run a station on your PC, you’ll need to ensure that the Platform Daemon for the version of workbench your using is installed and running.

How to check if the platform daemon is running?

You can check the status of the platform daemon by navigation to windows services and looking for the service “Niagara”. If the status is running, then you’re daemon is ready to be connected to.

How to start the platform daemon?

If your platform is not up and running you can start it by navigating to the workbench bin folder. For example D:\Software\Niagara\4.13\bin and running the console as administrator. Once the console is open, type plat installdaemon and hit enter.

The console can also be opened from within Workbench itself and you can use the same command plat installdaemon.

Once the platform is installed and running, you will be able to see it in your windows services.

Connect to the platform

Think of the platform as container, and within this container we can house stations, a platform can run multiple stations at a time as long as the stations are assigned unique fox ports.

To connect to the platform select the folder icon and then Open Platform. You can also use the keyboard shortcut Ctrl+Shift+P.

This will open a platform connection dialogue. In the Host field you will want to enter localhost, your computers hostname or IP address. Because we are running this locally on our PC localhost should work fine. The default connection type Platform TLS Connection and port 5011 should also be fine for this guide, unless you have changed it.

:notebook: If you were connecting to a remote platform, you would enter IP or hostname of the remote PC or Jace device

Select ok and the authentication dialogue will appear. Generally speaking when running a platform locally on your PC, the username and password with be your windows username and password.

Enter your credentials and select ok. If all worked OK then you will be taken to the platform view in workbench, which will look something like this.

Create a station

Now that our platform is up and running and we have a place where we can run our station, lets go ahead and create one!

To do this, navigate to Tools > New Station

This is going to open the New Station Wizard. Follow the prompts to create your station:

For the purpose of this guide select NewControllerStation as the template and give the station a name MyStation.

Next select Set Password and follow the promts to create a new password. Make sure you remember the password as this is how you will authenticate to the station!

Tick the selection copy it to secure platform for "localhost" with Station Copier this is going to automaticall copy our station to the platform we got up and running earlier.

This could be skipped and the station can be coppied to the platform manually using the platforms station copier. However, lets keep things simple and have the New Station Wizzard do the work for us!

Select Finish and follow the prompts. On completion you’ll see a dialogue window Transferring station that should indicate that the transfer of the station to the platform is complete.

You can select Close Window. This will automatically navigate you to the platforms Application Director. Here you will see a list of all stations that reside in the platform. If this is your first time then you should only have one station MyStation.

The application director allows you to see the current status of the station as well as the console logs which is useful for diagnosing a problematic station.

If all went well you should see Running in the status column next to your station as well as the fox port it’s running on. Take note of this port as we will use it in the next step to connect to our station.

Connect to the station

Now that our station is up and running in our platform, lets connect to it!

To do this, navigate to the Folder Icon > Open Station

This will open a dialogue similar to the one we saw earlier when connecting to our platform. Leave or select the Type as Station TLS Connection and enter the ip/hostname of your PC locahost should work fine here. Remember our station is runing within our platform which is running on our localhost. For Port enter the station fox port we noted down in the previous step seen in the Application Director. Generally, the default port 4911 will be used when creating a new station unless otherwise changed.

Select OK and enter the username and password we configured when we created the station.

:information_source: The station credentials are NOT the same as the platform credentials

Accept certificates

When using TLS connection type, you will be prompted to accept the station certificates the first time you connect to the station. Accept these and with success you will now be connected to the station! :partying_face: :partying_face: :partying_face:

:interrobang: If you have any issue please leave a comment and we will be more than happy to assist you in getting up and running!

3 Likes

It’s going to be brilliant to learn how to do this correctly, and not just hack at it, as I’ve been doing! It’s a testament to this site how prolific you are and how you reach down to the next guy!!!

2 Likes

Nicely written! :muscle:
I can see I need to teach you how to change the theme :stuck_out_tongue_winking_eye:

1 Like

It’s going to be a sad day when they force zebra upon us!

This was excellent. I’ve been doing this from the navigation tree (right clicking My Host and it gives me similar options) but I like this direct approach better. I also liked learning how to start the platform from the console. If for some reason my station wasn’t running already, I would have had no idea how to do this. I did run into two additional screens (probably different versions of Niagara). One asked me to select options when starting the station (either/or/and: Start Station after Install, and Auto start) and another menu after it (to choose yes or no to open the Application Director).


image
I choose not to Auto-Start as I have more than one station and I’m not sure I want all of them Auto-Starting at the same time, and not sure if that is a good idea… Thanks again for all the good content.

1 Like

This is certainly another good method and the one I probably use myself the most. As you keep learning Workbench you will find there are several ways to do most things :smiley:. Over time you will have your own workflow that works best for you.

These will certainly pop up for beginners so thanks for pointing these out!

Start After Install: Means the station will immediately be run after its copied to the platform.

Auto-Start: If this box is ticked anytime the platform starts the station will immediately start. You probably don’t want this box ticked for your personal workbench however if this was a JACE or a site supervisor you would want to tick this box to ensure the station starts if the jace or pc re-boots.

2 Likes

This makes a lot of sense. Thanks for the clarification. I have another question (in reality, I should just dig in and do the research, but…I’m a bit lazy today). What would be the difference in creating the station as say as a NewControllerStation or a NewJACEProvisioningStation, or as a Supervisor Station? Would it change the options of the Wire Sheet? I ask because I have in the past used the Supervisor option and didn’t see any huge differences.

1 Like

There’s a little difference in how they are set up. You can try to create one of each and see what the differences are. Most of the differences are in the services.

You can actually make your own station templates pretty easily.
If, for instance, you always use a specific tag dictionary setup, hierarchy, user setup or company logos in the station files, you can customize a station and save it as a template, so it shows up on the list, when you click “New station”.

Open Niagara, press Ctrl + L, paste this module://docTemplates/doc/CreatingAStationTemplate-09EC43D.html and hit Enter to read more :wink:

3 Likes

Interesting…looks like something you might use to deploy a bunch of identical VAV terminal box’s in a large project?

I will say this. If you’re working on stations on your laptop only, I would be very careful keeping Auto-Start Checked. As a matter of fact, I tell my students to NOT do it. Reason being is that if you start your platform and you have 100 stations with AutoStart selected… Chaos ensues.

On a Customer PC (Supervisor) and a Niagara Controller (JACE, Edge10, Lynxspring’s Edge Product Line, etc) you will always want AutoStart.

2 Likes

lol…this was only a hunch I had that I shouldn’t auto start…just cause it felt like too much happening out of my control. (I think it was discussed in a Nordicity or One Sight YouTube. You’ve given me more justification for my suspicions.

2 Likes