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

Controller Tool Help

Brand
Johnson Controls
Metasys
Product name
Controller Configuration Tool
Document type
User Guide
Document number
LIT-12011147
Version
13.1
Revision date
2019-12-04
Language
English
Table 1. Tool Functionality Troubleshooting

Problem

Solution

Updating the static IP address of a controller via Direct Ethernet or NxE Passthru, causes the following issues in CCT:
  • During Transfer to Device (Download), the error message Operation failed: Updating device with New Information Attributes appears.
  • In commissioning mode, IP address reads time-out.
Updating the static IP address of a device causes an expected loss of communication in CCT. However, the issue does not prevent the static IP address of the device from being updated. For example, if you repeat the Transfer to Device (Download) process after obtaining the initial error, the controller displays the correct static IP address and the download completes successfully.
When performing a NxE Passthru Transfer to Device (Download), the following error message displays in the Transfer Summary screen:

Operation Failed: Failed Operation. Details: Unable to start Transfer To Device session for [controller name]. Invalid load type. - Transfer to Device (0%)

This issue may occur if the engine you are connecting through does not support background transfer. Check the version of the engine for compatibility with the controller. Engines running Metasys Release 9.0 and newer support background transfer.

Simulation fails to start when the Point Schedule is transferring to the device and the following error occurs:

Error starting Simulation MCE.

Only one of these processes may run at a time. Do not run Simulation while transferring to the device with the Point Schedule.

While transferring to a device or transferring an application from a device to a computer, one of the following errors occur:

Error generating MOI file for device xxxx

Error generating MOZ file for device xxxx

(where xxxx is the type of device being transferred from to the computer or transferred to)

Repeat the same transferring to a computer or transferring to a device operation for the same device. The transfer completes successfully the second time.

If the error occurs again, contact regional technical support.

When transferring an application from a device to a computer, a PREMATURE TERMINATION message appears.

  1. Close the Tool.
  2. Browse to C:\ProgramData\Johnson Controls\MetasysIII\CCT\UI\ApplicationConfiguration.properties.
  3. Find the line that contains the key da.PssConversionMode. If the key does not exist, add the key to the file.
  4. Set the key to one of the following values:
    • 0 - the transfer fails if there are any conversion issues with persistent storage data.
    • 1 - the transfer attempts to use any converted persistent storage data, but may still fail if data is corrupt. If this succeeds, but the configuration value of 0 did not succeed, this could mean that the resulting CAF may not have all the updated attributes from the controller that were changed during Commissioning or during runtime of the Field Controller.
    • 2 - the transfer does not use any persistent storage data. If this succeeds, but the other configuration values did not, then the resulting CAF may not have all the updated attributes from the controller that were changed in Commissioning or during runtime of the Field Controller.
  5. After a successful transfer, update the file and change da.PssConversionMode back to 0, or remove the line from the file. Doing this allows you to see errors if they occur.
  6. Report all issues to regional technical support for further analysis.

The transfer to a wireless device fails.

Adjust the following before repeating the application transfer to the device using Wireless Commissioning Converter:

  • Disconnect the field bus from the ZFR1810 Coordinator.
  • Connect your Wireless Commissioning Converter into the FC Bus Out jack on the ZFR 1810 coordinator.
  • Reduce the number of transfers to devices. If you are transferring to a large number of devices, attempt transferring to your devices in segments.
  • Select the same model type when you transfer to devices on a mixed-model network.
    Note: Do not use the ZigBee® dongle to transfer to a wireless device.
    Note: See for transferring to device recommendations.

You are experiencing problems transferring to multiple devices through an SA Bus connection.

Transfer to devices over the SA Bus using the following sequence:

  1. Individually transfer the Main Code to each connected device.
  2. Individually transfer the Application Code to each connected device.
  3. Continue with transferring to other devices using multiple transfers to the devices, where applicable.

You are experiencing problems transferring to multiple devices at once.

Use the FC Bus to transfer to multiple devices at once using the following rules:

  • Devices can be connected wired or wirelessly.
  • Devices can be transferred to in any order.
  • The tool processes the transfer in any order.
  • When transferring to wireless devices, disconnect the MS/TP Trunk (Field Bus) between the ZFR1810 Coordinator and the NxE, and then connect the Wireless Commissioning Converter to the FC Bus Out Jack of the ZFR1810 Coordinator.
  • Transfer to wireless controllers through the Wireless Commissioning Converter connection to your laptop.

You are experiencing slow speeds while transferring to multiple devices at once.

Improve the transfer to device speeds by doing the following:

  1. Disconnect the MS/TP Trunk (Field Bus) between the ZFR 1810 Coordinator and the NxE.
  2. Connect a Wireless Commissioning Converter to the FC Bus output jack of the ZFR1810 Coordinator.
  3. Use the CCT Bluetooth (connection type) to transfer to or upgrade wireless devices.

After selecting items to print from the Summary Report Options dialog box, the Adobe Acrobat window does not open to display the file contents.

Navigate to C:\ProgramData\Johnson Controls\MetasysIII\CCT\UI

The file appears and can be manually opened.

The following security message appears in the Internet Explorer Information Bar when opening Help:

To help protect your security, Internet Explorer has restricted this file from showing active content that could access your computer. Click here for options.

Internet Explorer security settings may prevent Help systems with active content from opening without first verifying it is OK to open. To open the Help:

  1. Click Click here for options and select Allow Blocked Content. A Security Warning dialog box appears stating:

    Allowing active content such as script and ActiveX controls can be useful, but active content might also harm your computer. Are you sure you want to let this file run active content?

  2. Click Yes. The Help system opens.

The Open or Save dialog box appears blank, and you cannot close the dialog box.

Do not add a new folder, rename a file or folder, or delete a file or folder in the Open or Save dialog box. If this problem occurs, use Windows Task Manager to exit. Add or delete files or folders using Windows Explorer.

When working with logic, the following error message appears:

There are blocks and/or connections that are in a non-existent state section. Please remove them.

To remove the blocks and connections:

  1. Right-click the State block and select View > Details. The Details window appears.
    Note: Be sure to make a note of where this State block is connected.
  2. Click Edit.
  3. In the States Text drop-down box, select a value with more States than the current value. For example, if the current value is States (0–1), choose States (0–5).
  4. Click Apply.
  5. Click Close.
  6. Delete any connections or blocks from unused hybrid activity state sections.
  7. View the details of the State block again and change the States Text value back to the original value.
  8. Click Apply, and then click Close.
  9. Return to the event section of the State block, and then reconnect the State block to the logic it was connected to previously.
Note: This issue does not affect the operation of the controller, but causes the application file size to increase.

When in Commissioning or Simulation mode and you modify a constant value in an inactive state section of a hybrid activity, the output of the hybrid activity changes.

A permanent solution for this issue is under development and planned for implementation in a future release.

Until a permanent solution is provided, use caution when modifying the default values of blocks in an inactive state section of a hybrid activity.

The following alert appears when launching the Tool:



Click OK and launch the tool again.

This alert appears for various reasons, such as when there are problems initializing communications with the database and the Tool's data access layer. To see specific information about the cause of the error, consult the application log found here:

C:\ProgramData\Johnson Controls\MetasysIII\CCT\UI\metasys_application.log

In CCT versions prior to Release 10.0, these were common Passthru issues:
  • CCT Release 6.0 and earlier do not have standalone passthru capabilities and must be launched through the SMP or through CCT. When you attempt to launch Passthru for CCT Release 6.0, the launch stalls after the splash screen.
  • Passthru does not function because the hard drive is almost full.
  • Passthru does not function because the user does not have Administrator rights.
  • CCT Release 5.3 does not start when initiating Passthru from SCT or the Site Management Portal tools menu.
  • When launching CCT through the SMP UI connections to an NxE (without installing SCT on the computer first), an error message occurs: You must first install the Passthru components on this machine before running the selected tool.

CCT now allows for standalone use of Passthru features, which eliminates these common issues.

The following message appears when installing the tool: Application and database versions do not match. Please update before restart.

The Controller Tool fails to start due to an application and database version mismatch error.

To clear this error:
  1. Ensure that the SQL browser is running in the Services Control Panel.
  2. Confirm that UDP port 1433 is not blocked in the firewall settings. Contact your IT support specialist if you cannot change the firewall settings on your laptop to open UDP port 1433.
  3. Open the SQL Server Configuration Manager.
  4. Expand the SQL Server Network Configuration.
  5. Select the protocols for the instances of SQL that the Controller Tool is using (there will likely only be one).
  6. Right-click Named Pipes, and then select Enable.
  7. Right-click TCP/IP, and then select Enable.
  8. Restart SQL or reboot the machine.

When you select a field device in the Define Hardware dialog box, a warning box appears stating the controller selection is not permitted.

This message appears when the application includes a primitive not supported by the selected controller.

The Global Sequencer is only supported by Advanced Application Controllers. The Chiller Selector, Pump Selector, Tower Selector, and Heat Exchanger Selector are supported by all devices except some VAV Controllers.