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

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

Controller Tool Help

Product

Controls > Control Tools > Controller Configuration Tool

Document type

User Guide

Document number

LIT-12011147

Version

13.1

Revision date

2019-12-04

Table 1. Application Functionality Troubleshooting
Problem	Solution
When making changes to an application in commissioning mode an Alert dialog box displays the following information: `Unable to save view: java.lang.Runtime.Exception:RemoteRequestfailed`	This specific behavior can be observed when making certain changes to a 6.2 application in commissioning mode without having the 6.2.2 firmware patch installed. Always apply the latest patch of firmware if you configure your applications with newer tool versions.
Applications configured as VAV type fail download at 99% and the controller shows a status of `Instances Deleted`	Check your CFM values for control and application configuration. VAV applications limit the MAX CFM Flow to 9,999 with a maximum 9.9 inch inlet connection. CCT does not support VAV applications where Box sizes are greater than the above stated flow and inlet size. Any attempt to configure applications for VAV Box sizes 10 inches or larger with 10,000 CFM air flow or greater will result in an application download failure to the configured controller. To accomplish a successful configuration for this VAV Box size the application will require customized or modified logic with related modules and connections.
The Zone Temperature control does not seem to react as quickly as expected when it is in unoccupied mode. The zone temperature overshoots the unoccupied heating or cooling setpoint during unoccupied operation. See Figure 1.	The Satisfied Timer Duration value of the Unoccupied Sequencing (VAV) is set to too high. Reduce this value to decrease the overshoot. The Satisfied Timer Duration works as follows: When unoccupied, the zone temperature is monitored to determine when the temperature exceeds the band specified by the two unoccupied temperature setpoints. When this occurs, the Unocc Status is set to the appropriate heating or cooling state. The module remains in this state until the appropriate setpoint has been satisfied for the Satisfied Timer Duration. After that period of time, the status is set to Satisfied.
Figure 1. Changing Satisfied Timer Duration
The zone temperature cycles too frequently during unoccupied operation, and the Unocc Status changes too frequently.	The Satisfied Timer Duration is set too low. Increase this value to reduce the cycling. The Satisfied Timer Duration works as follows: When unoccupied, the zone temperature is monitored to determine when the temperature exceeds the band specified by the two unoccupied temperature setpoints. When this occurs, the Unocc Status is set to the appropriate heating or cooling state. The module remains in this state until the appropriate setpoint has been satisfied for the Satisfied Timer Duration. After that period of time, the status is set to Satisfied.
While making connections, one of the following error messages appears: `Loop found in logic flow.` `A component is connected in an unsupported loop configuration.`	Add a Last Value block to break the unsupported loop. This process provides the information to the controller regarding where to start calculating values in this loop. Note: Within a state in a Hybrid Activity, you can create a loop without a Last Value block when connecting an output of the state back to an input of a block within that state.
There are no Pressure Dependent VAV Control paths to let you easily apply the VMA16 or PCV16. This path is used when no internal VP transducer for airflow control is needed. No airflow measurement.	Set the Min Value for the VP input to a value greater than zero. This causes this input to always be unreliable, and the standard Pressure Independent application reverts to Pressure Dependent operation.
There is no path for Constant Volume VAV airflow control with CO² sensor reset only. An example of using a Single Duct VAV application with a constant volume of airflow would be when the VAV Box is providing Ventilation Air to fan coil units. In this scenario, the VAV Box does not have a temperature control requirement.	Set the Min Flow = Max Flow.
There is no VAV Heat or Cool Switchover Mode path VAV heating or cooling action based on AHU supply air temperature.	This option is available as the Warmup Mode. This mode can be implemented with a network input for supply air temperature or an supply air temperature analog input.
The controller is not able to maintain setpoint.	If the controller is operating while the physical system cannot respond appropriately, the controller tunes to unrealistic values. Use the Network Input Tuning Reset to set the tuning parameters to the initial values.
The Mixed Air Damper does not open. See Figure 2.	Due to a change in the Mixed Air Low Limit operation, the Low Limit PID starts at 0%. When Low Limit is not present, the Low Limit Process Variable and the Low Limit setpoint are the same. Because of this, the Low Limit PID does not integrate to 100%, and the output to the Mixed Air Damper is set at 0%. By changing the Low Limit Process Variable to 13 °C, 55 °F, it is now above the Low Limit Setpoint. The Low Limit PID integrates to 100%, and the damper is allowed to modulate. Select one of the following modules in your application: Proportional OA Damper Control V50 Damper Control for Economize V50 Damper Control for Relief Fan V50 Proportional OA Damper Control for Relief Fan V50 Damper Control for Volume Match V50 Proportional EA Damper Control for Volume Matching V50 Note: Only one of the module options is available in your application. Open Details View to view the module details. Set the Low Limit Process Variable to 13 °C, 55 °F. Note: This fix is relevant for Release 6.0 and earlier. Release Mode 10.0 / Firmware 6.1 and later include the fix.
Figure 2. Adjusting the Proportional OA Damper Control V50
When simulating or commissioning a custom application in version 5.0 or later, one of the output modules shows ???? and the module details indicate an initialization error.	Manually update custom applications and modules that include the PID block or PID pre-processor to reflect version 5.0 and later. Write down any custom settings in the current PID. Delete the existing PID from the module and replace it with the PID block from the pallet in version 5.0 and later. Update the PID block settings. Export the updated module to save it. You will not have to modify the module when you import it again. Note: To modify Timer block modules, delete the current Timer block, and replace it with a Timer block from the pallet.
More information about Adaptive Tuning is needed.	The following guidelines should be followed when using PRAC+ Adaptive Tuning: Heating and cooling media must be available and enabled. Air and water systems must be balanced and able to provide the required capacity. Valves and dampers must be selected, installed correctly, and able to perform. Valve and damper actuators must be mounted, wired correctly, calibrated, and able to operate. VFD must be calibrated and in Auto (the low limit of the PID should match the minimum of the drive). Sensors must be wired and located properly. For more information, see PID/PRAC Commissioning Overview section.