Controller Functionality - Johnson Controls - Metasys - LIT-12011147 - Software Application - Controller Configuration Tool - 16.0

When changing or upgrading a field device, points are incorrectly mapped or unassigned in the CAF.

When changing or upgrading a field device, ensure that you verify all network settings and point assignments. See Point Assignment Tab for further information. If the signal type is incompatible with the device, follow the instructions in Modifying an Input or Output Signal to modify the signal information.

The Proportional OA Damper Control is in T Control, but the output is not changing.

The PID in the Proportional OA Damper Control Output Module or Proportional OA Damper Control for Relief Fan Output Module is Unreliable or indicates a Math Error.

The Output Module Damper Min Reset by OA Flow requires you to set a Process Range for the application.

You can set the Process Range manually, or link it to an input attribute. It has only two rules: it must be greater than 0, and the Minimum Tune Band must be greater than 1% of the Process Range. If the range is set incorrectly, it can result in a failure of the PID to calculate, or cause the PID to calculate when it should not. For example, if the range is not based on real values, the PID may incorrectly find that the Minimum Tune Band is greater than 1% and allow the PID to calculate when it should not.

To resolve the issue, set the Minimum OA Flow Range for the Damper Min Reset by OA Flow to the maximum expected value for minimum Outside Air for the application. For example, if the minimum OA Flow sensor is scaled to read 0 to 10,000 CFM, but the maximum expected minimum Outside Air Flow is expected to be 8,000 CFM, change the default value of the Minimum OA Flow Range from the default of 5,000 CFM to 8,000 CFM. The range should be the result of subtracting the minimum process variable value from the maximum process variable value. For example, if the process variable (in this case, flow) is expected to vary between a minimum of 100 CFM and a maximum of 8000 CFM, the resulting Process Range would be 7900 CFM. You can do this by viewing the details of the Damper Min Reset by OA Flow Output Module, and changing the Default Value.

In Commissioning mode, a Wireless Sensor that is Offline or Unreliable appears as Unreliable along with its last known value.

The following list provides some possible causes and solutions for an Offline or Unreliable Wireless Sensor.

My Point Expansion Module displays a solid fault light despite being on the SA Bus.

This is expected behavior. However, if you want to workaround this behavior, you can use one of the following solutions:

• Transfer a Monitoring Supervisory Control Only application directly to the Point Expansion Module. See Custom and Monitoring Supervisory Control Only Applications and Transferring to a Device.

• Add a placeholder point to the main application that is mapped to the Point Expansion Module, and transfer to the field controller. If desired, the point could then be removed from the main application and transferred again to the field controller.

• For Point Expansion Modules that are connected to the SA Bus for the purpose of future expansion only, consider turning off the device power and configuring the device at the time when expanding the system.

Peer-to-peer functionality is lost on Field Controllers after a power failure.

You must configure peer-to-peer communication in the Configuration mode, not in the Commissioning mode.

If you change peer-to-peer references in Commissioning mode, the communication works until the controller loses power.

When the controller resets, the peer-to-peer reference changes are lost.

To resolve this problem, make the necessary peer-to-peer communication changes in the Configuration mode, then transfer the application to the controller.

See Peer-to-Peer Communication and Setting Up Peer-to-Peer Communication in the Configuring a System section for more information.

The behavior of a binary input versus a universal input differs when used with a dry contact.

The BI reports based on an event (for example, a contact closure). The UI is scanned once per second. There may be a delay of up to one second in reading a contact status change.

When you restart a field equipment controller, the modifications to network inputs objects are lost.

You experience poor SA Bus performance.

See SA Bus Diagnostics for details and solutions.

When transferring an N2 application to an N2 controller, the communication mode is MS/TP (Wired Field Bus) instead of N2.

To switch communication to N2, transfer the application code to the device and select the Switch Communication Mode check box on the Load Summary screen. Use a Wireless Commissioning Converter that is connected to the SA Bus of the controller.

When transferring to a field controller configured as N2, the FC bus port does not work with the Bluetooth commissioning converter.

Once a field controller is configured for N2 communication, the only port available for the Bluetooth commissioning converter is the SA bus port. The FC bus port is configured as N2 and cannot be used by the Bluetooth commissioning converter.

When you map points to a supervisory device, some points are not refreshed in the supervisory device configuration tool user interface.

For controllers with more than 100 analog value (AV) objects, set the Use COV Min Send Time attribute to False.

When you attempt to discover an MS/TP device on the NAE Field Bus while using CCT Controller Information or Autodiscovery, the device does not respond.

The controller is stuck in Boot Mode if the red LED comes on immediately after power is applied and the comm LEDs come on and stay on. This indicates that the Main or Application code is corrupted.

As long as the MS/TP controller has valid boot code and the controller tool knows what address to send the messages to, the controller tool can communicate with the MS/TP controller. An MS/TP controller with boot code only will not respond to the BACnet Who_Is request.

Recover the device by individually transferring the Main Code and Application Code to each MS/TP controller using a Wireless Commissioning Converter that is connected to the controller you are transferring to.

If you do not know the device address, manually discover it before starting the device recovery.

To recover your device:

1. Connect the Wireless Commissioning Converter to the MS/TP device.
2. Open the controller tool application.
3. Click Define Hardware and add the address of the device the Wireless Commissioning Converter is connected to.
4. Save the file.
5. Click Transfer to Device, and then follow the Wizard to the Transfer to Device Summary screen.
   • If the summary status is Main Code Transfer to Device Required, check Main and Application, and then click Finish.
   • If the summary status is Operational, check Application, and then click Finish.

The Main Code and Application transferred to device normally. Additional transfer to device of Boot, Main, and Application to the device will occur without problems.