Facility Explorer FX80 Initial Setup Checklist

Facility ExplorerFX80Johnson Controlssetupchecklist
April 20, 2026|7 min read

The Johnson Controls Facility Explorer FX80 supervisory controller ships fully commissioned and licensed from the factory, but it arrives with default credentials and a generic network configuration that must be changed before the controller goes into production. At a minimum, you need to update the station password, platform password, and system passphrase, assign a static IP address appropriate for the building network, and configure the BACnet driver for the field controllers on the job. Skipping any of these steps leaves the controller vulnerable to unauthorized access or unable to communicate with downstream devices.

What Is the FX80

The FX80 is Johnson Controls' current-generation supervisory controller in the Facility Explorer product line. It is built on the Niagara 4 Framework and serves as the central hub for managing networks of field controllers—including FX-PC, BACnet, LonWorks, and N2 devices—across a building or campus. The FX80 provides a graphical system interface through an HTML5 web profile, meaning technicians and operators can access dashboards, schedules, alarms, and trend data from any modern web browser without installing dedicated client software.

From a hardware standpoint, the FX80 includes two 10/100 Mbps Ethernet ports labeled PRI (LAN1) and SEC (LAN2), a built-in RS-485 port for BACnet MS/TP trunks, a USB Type-A port for station backup and restore, and a Micro-USB port for serial debug connections. Optional communication modules (up to four RS-232 cards) can be added for legacy protocol integration. The controller requires FX Supervisory Software Release 14.1 or later and runs the Niagara 4 runtime internally, which means it shares architectural concepts—stations, platforms, drivers, and networks—with other Niagara-based products like the Tridium JACE 8000.

Johnson Controls positions the FX80 as a drop-in supervisory controller for small to mid-size buildings. It handles scheduling, trending, alarm management, and integration with upstream enterprise systems. For larger campuses, multiple FX80 controllers report to an FX Supervisory server (the software-based supervisor), which aggregates data across buildings.

Pre-Deployment Checklist

Before the FX80 leaves the staging bench or gets mounted in a panel, walk through this checklist to confirm the controller is ready for the job site:

  1. Inspect the hardware. Unpack the FX80 and verify all components are present and undamaged. Confirm you have the correct model variant for your project (base model, Wi-Fi model, etc.).
  2. Plan the mounting orientation. Horizontal mounting is strongly recommended by Johnson Controls. Mounting the FX80 vertically or in any other orientation reduces the operating temperature upper limit, which can cause reliability issues in warm electrical panels.
  3. Verify the power supply. The FX80 requires a dedicated 24 VAC transformer. This transformer must not power any other equipment. Sharing a transformer with actuators, relays, or other controllers causes voltage sag and erratic behavior.
  4. Confirm software release. The FX80 ships with FX Supervisory Software pre-installed. Verify the installed release version meets or exceeds the project specification. If an upgrade is needed, download the appropriate release from the Johnson Controls partner portal before going to the job site.
  5. Prepare network credentials. Decide on the static IP address, subnet mask, default gateway, and DNS servers the controller will use on the building network. Also have new passwords ready for the station login, platform login, and system passphrase.
  6. Gather field controller documentation. Know the BACnet device instance numbers, MS/TP addresses, and trunk wiring topology for every field controller the FX80 will manage. Having this information ready prevents delays during driver configuration.
  7. Load your FX Workbench license. FX Workbench is the engineering tool used to configure the FX80. Make sure your laptop has a current FX Workbench installation with valid licensing before connecting to the controller.

Changing Default Credentials

The FX80 ships with three sets of default credentials that must all be changed at initial login. Leaving any of these at their factory defaults is a serious security risk and violates Johnson Controls' own commissioning requirements.

Station Credentials

The station login controls access to the FX80's web interface and FX Workbench station connections. The factory default username is admin and the default password is FacilityExpl0rer (note the zero replacing the letter "o"). When you log in for the first time, the Facility Explorer Station Login screen forces you to change this password before proceeding. Choose a strong password that meets the complexity requirements: minimum 10 characters, at least one uppercase letter, one lowercase letter, one digit, and one special character.

Platform Credentials

The platform daemon runs underneath the Niagara station and handles low-level operations like firmware updates, station start/stop, and certificate management. Platform credentials are separate from station credentials. When connecting to the FX80's platform via FX Workbench (on HTTPS port 5011), you will be prompted to create a new platform username and password. The default password jci is explicitly blocked and cannot be reused. Record the new platform credentials securely—losing them requires a factory reset of the controller.

System Passphrase

The system passphrase is used to encrypt sensitive data within the FX80's station database, including stored passwords for downstream device integrations. The factory default passphrase is explorer. The Commissioning Wizard prompts you to change this during initial setup. Like the platform credentials, a forgotten passphrase requires a factory reset, so document it in your project's credential management system immediately after changing it.

Change all three credentials before connecting the FX80 to any production network. A controller sitting on a building network with factory-default passwords is an open door for anyone with a web browser and knowledge of the Facility Explorer platform.

Network Configuration

The FX80's primary Ethernet port (PRI / LAN1) ships with a default IP address of 192.168.1.149. The secondary port (SEC / LAN2) is disabled by default and has no assigned address. To connect to the FX80 for the first time, set your laptop's Ethernet adapter to a static IP in the 192.168.1.x range (avoiding .149) and connect a patch cable directly to the PRI port.

Assigning a Production IP Address

  1. Open a web browser and navigate to https://192.168.1.149. Accept the self-signed certificate warning.
  2. Log in with the station credentials (or change them if this is your first login).
  3. In FX Workbench, open a platform connection to the controller on port 5011.
  4. Navigate to Platform > Platform Administration > Network Settings.
  5. Change the IP address, subnet mask, default gateway, and DNS server fields to match the building network's addressing scheme.
  6. Save the configuration and reboot the controller when prompted.
  7. Reconnect your laptop to the building network (or change your static IP to the new subnet) and verify you can reach the FX80 at its new address.

Dual Ethernet Port Usage

The FX80's two Ethernet ports can be configured for network segmentation. A common architecture places the PRI port on the building's IT/OT backbone (for operator access, alarm routing, and integration with upstream systems) and the SEC port on an isolated BACnet IP subnet dedicated to field controller traffic. This keeps BACnet broadcast traffic off the corporate network and improves security by separating supervisory access from field-level communication. If you enable the SEC port, assign it a static IP on a different subnet from the PRI port and configure routing or firewall rules as needed.

BACnet Driver Setup

The FX80 supports both BACnet IP and BACnet MS/TP communication with field controllers. The BACnet driver is configured through FX Workbench and must be set up before the controller can discover or communicate with downstream devices.

BACnet IP Configuration

  1. In FX Workbench, open the station and navigate to the Drivers container in the Nav tree.
  2. Add a new BACnet Network (sometimes listed as NiagaraBacnetNetwork or BacnetNetwork depending on the software release).
  3. Under the network, configure the Local Device properties. Set the BACnet device instance number to a unique value that does not conflict with any other device on the BACnet internetwork. Set the network number and the UDP port (default is 47808, which corresponds to the standard BACnet IP port 0xBAC0).
  4. Bind the BACnet IP driver to the appropriate Ethernet interface. If you are using the SEC port for field controller traffic, bind to the LAN2 interface.
  5. Run a device discovery to scan the BACnet IP network for field controllers. Discovered devices appear in the Nav tree and can be added to the station's database.

BACnet MS/TP Configuration

For field controllers connected via RS-485 trunks (BACnet MS/TP), the FX80's built-in RS-485 port or optional RS-232 communication modules are used.

  1. Wire the RS-485 trunk in a daisy-chain topology using shielded, twisted-pair cable (18–22 AWG). Connect the shield wire to earth ground at one end only.
  2. In FX Workbench, add an MS/TP Port under the BACnet network driver. Set the MS/TP MAC address for the FX80 (typically 0 or 1 for a supervisory device).
  3. Set the baud rate to match all devices on the trunk. The most common baud rate for FX-PC controllers is 38400 or 76800 bps.
  4. Configure the Max Master value to match the highest MS/TP MAC address on the trunk. Setting this value too high wastes poll cycles; setting it too low prevents the FX80 from communicating with devices that have higher MAC addresses.
  5. Verify end-of-line (EOL) termination. FX-PC controllers at the physical ends of each trunk should have their EOL jumpers or DIP switches enabled. The FX80 should be in the middle of the trunk (MID position) with FX-PC controllers at the ends.

Connecting to FX Supervisory

In multi-building or campus deployments, individual FX80 controllers report to an FX Supervisory server that aggregates alarms, trends, schedules, and graphics into a single management interface. Connecting an FX80 to its supervisor involves establishing a Fox protocol connection between the two platforms.

  1. Ensure the FX80 and the FX Supervisory server have IP-level reachability to each other. Both devices must be able to reach each other on TCP port 4911 (the default Niagara 4 Fox port). Verify that no firewall or VLAN boundary blocks this traffic.
  2. In FX Workbench, open the FX Supervisory server's station.
  3. Navigate to the Station > Config > Drivers > NiagaraNetwork (or FoxNetwork, depending on the release).
  4. Add a new NiagaraStation component. Enter the FX80's IP address, Fox port (4911), and the station credentials you configured during initial setup.
  5. Once the connection is established, the FX Supervisory server can subscribe to the FX80's points, pull alarm and trend data, push schedule changes, and display the FX80's graphics within the supervisor's web interface.

If the FX80 sits behind a NAT boundary or a restricted firewall, you may need to configure port forwarding or a VPN tunnel to allow the Fox protocol connection. The FX80 can also initiate an outbound connection to the supervisor if the network topology requires it—consult Johnson Controls documentation on "station-to-station" Fox connections for details.

Common FX80 Setup Mistakes

Platform Compatibility

The FX80 operates within the Facility Explorer ecosystem and interacts with several related hardware and software components. The following table summarizes compatibility across the most common configurations:

ComponentCompatibilityNotes
FX Supervisory SoftwareRelease 14.1 or laterMinimum required version. Later releases add features and security patches. Check the release notes before upgrading to confirm backward compatibility with existing field controllers.
FX WorkbenchMust match FX Supervisory releaseFX Workbench version must align with the FX Supervisory Software release running on the FX80. A version mismatch causes connection failures or feature incompatibilities.
FX-PC Field ControllersAll FX-PC modelsConnected via BACnet MS/TP (RS-485) or BACnet IP. The FX80 discovers and manages FX-PC controllers natively through the BACnet driver.
Third-Party BACnet DevicesBACnet IP and MS/TPAny BACnet-compliant device can be integrated. Use device discovery in FX Workbench to scan for third-party devices and manually map points as needed.
LonWorks ControllersSupported via optional moduleRequires a LonWorks communication module and the appropriate Facility Explorer LonWorks driver license.
N2 Controllers (Legacy JCI)Supported via optional moduleIntegrates legacy Johnson Controls N2 bus devices. Requires an RS-485 or RS-232 communication module and the N2 driver license.
Web BrowsersHTML5-compatible browsersThe FX80's web interface works with Chrome, Firefox, Edge, and Safari. Internet Explorer is not supported on current FX Supervisory releases.
FX Supervisory ServerFox protocol over TCP 4911The FX80 connects to FX Supervisory servers for campus-wide aggregation. Both devices must run compatible FX Supervisory Software releases.

When planning a Facility Explorer deployment, standardize on a single FX Supervisory Software release across all FX80 controllers on the project. Mixed software versions create FX Workbench compatibility issues, complicate firmware updates, and make it harder to maintain consistent security policies. If you are upgrading existing FX60 or FX70 controllers to FX80 hardware, consult the FX Supervisory Controller Upgrade and Migration Instructions Technical Bulletin (LIT-12011441) for migration procedures and compatibility matrices.

Source Attribution

This guide draws on technical documentation and product literature from the following sources:

FX80Johnson ControlssetupchecklistFacility Explorer

Was this article helpful?

Related Articles

Need to do this remotely? SiteConduit replaces VPN configuration with one-click encrypted sessions. No port forwarding, no certificate management. Join the waitlist.

SC

SiteConduit Technical Team

Idea Networks Inc.

SiteConduit builds managed remote access for building automation. Our knowledge base is maintained by BAS professionals with hands-on experience deploying and troubleshooting BACnet, Niagara, Modbus, and Facility Explorer systems.