Transferring to a Device - Johnson Controls - Metasys - LIT-12011147 - Software Application - Controller Configuration Tool - 16.0

Changes to the workflow and general transfer tips are as follows:

• The Transfer to Device feature is disabled for unlicensed devices.
• If you attempt to transfer an application to a device, the tool detects the versions of the Boot, Main, and Radio Code versions currently running in the field controller. If the Boot or Main Code version in the controller does not match the software version, or a newer version for the same release is available in your packages, the Boot or Main Code check box is selected.
• If you are transferring code to N2 supported applications, you must be connected to a field device via the SA Bus. In addition, with the Transfer Wizard, the Main Code initially transfers to device over MS/TP (Wired Field Bus), but switches to N2 (N2 Slave Field Bus) when you select the Switch Communication Mode check box on the Transfer Summary screen. This step is not necessary if the device supports background transfer, because the transfer of N2 applications to such devices does not require explicit communication switching.
• Supported field controllers are capable of updating boot and main code of Point Expansion Modules attached on the Sensor/Actuator Bus using the SA Bus Provisioning feature. The SA Bus Provisioning feature allows updating firmware of devices attached on the Sensor/Actuator Bus without requiring you to manually connect and update each one. The feature automatically sends the necessary data to the controllers, which are capable of performing updates of SA Bus devices independently.
• When you upgrade field controllers with Point Expansion Modules on the SA Bus, you may need to upgrade certain devices to the latest release before you transfer the application to a device. If this workflow is required, an alert appears that indicates which devices require an upgrade.
• When you transfer application code to a field controller that has a Point Expansion Module without points, the Point Expansion Module LED fault light may be on steady. This is expected behavior and does not affect the functionality of the controller. The Point Expansion Module LED fault light remains on until you reconfigure the device with input/output points. For immediate workaround solutions, see Troubleshooting.
• If you are transferring to devices over the SA Bus, first transfer the application to the individual device to which you are connected. Then, transfer to the remaining devices.
• Transferring Main Code into a Point Expansion Module over the SA Bus with a Bluetooth connection is 1 to 2 minutes (30%) faster than doing so over an FC bus connection. It typically takes three to three-and-a-half minutes to transfer to an SA Bus device and nearly five minutes for an FC Bus connection.

To transfer to a device:

1. Click Transfer > Transfer to Device (Download). The Transfer to Device Wizard appears.
   Note: The Transfer to Device feature is disabled for unlicensed devices. If you opt to transfer an application to an unlicensed device, a dialog box informs you that the tool is not licensed to transfer CAFs to the device.
2. In the Connection Type section, select the connection type: Supervisor Passthru, Bluetooth, MAP 4.2+ / BACnet Router, ZigBee, or Direct Ethernet connection. For more information about connection types, see Connections.
3. In the Connection Parameters section, enter the connection parameters as follows:
   • For Supervisor Passthru connections, enter the device host name or IP address, your user credentials, and click Login. Select the correct supervisory device and the trunk.
   • For Bluetooth connections, enter the baud rate and COM port information. We recommend you keep the Baud Rate default of 38400.
   • For MAP 4.2+ / BACnet Router connections, specify the following:
     • IP address and UDP port of the router.
     • Network number of the MS/TP trunk (1-65,534).
       Note: Do not use 1001 for the MS/TP Network Number. The MS/TP Network Number 1001 is reserved for Johnson Controls IP network connections.
     • An available Ethernet network interface adapter to use.
       Note: If you select an available Ethernet network interface, all IP traffic intended for the MAP 4.2+/ BACnet Router travels through this interface.
     When you first open the wizard, the default connection parameters for connecting to a MAP Gateway at version 4.2 are automatically displayed. If the connection parameters are modified, the values are stored in the wizard for future use. To restore the connection parameters to the default values, click the MAP 4.2 Default button.

     Note: For further information about the MAP and common troubleshooting issues, refer to the Mobile Access Portal Gateway User's Guide (LIT-12011999).
   • For ZigBee connections, enter the PAN offset.
   • For Direct Ethernet connections, enter the UDP port of the device and an available Ethernet network interface adapter to use. If you select an available Ethernet network interface, verify you are on the same subnet as your IP controllers.
     Note: Do not use 1001 for the MS/TP Network Number. The number 1001 is reserved for Johnson Controls BACnet IP network connections.

4. Click Next. The Device Selection Screen appears.

   Note: The Discover option is not available on the MS/TP trunk during the transfer process.
5. Select the device you want to transfer to and click Next. The Transfer Summary Screen appears.
   1. Use the When to activate options to control when the transferred files are activated on the controller. If you select After Transfer, the application is activated after the transfer process completes. If you select Wait for manual activation, the application is not activated when the transfer process completes. To manually activate the transferred files, use the Activate pending files action in Tools > Online Operations. See the Online Operations Wizard for more information.
   2. Use the When activated options to modify the behavior of transferred files when activated on the controller. Select the Enable logic or Disable logic options to enable or disable the logic of activated files on supported devices. If you opt to disable the logic of an application, you can enable it later by selecting the Enable logic action in Tools > Online Operations. See the Online Operations Wizard for more information.
      Note: If you select the Wait for manual activation option, the Enable logic and Disable logic options do not take effect on the controller until you activate the application using the Activate pending files feature in the Online Operations Wizard.
   3. The appropriate code required to load your application is automatically determined. To view or modify code transfer options, click Advanced Transfer Options. For information about code options, see Codes.
      Notes:

      • The tool automatically selects Switch Communication Mode if it is available. If the mode is required but not possible, a message appears and you can not proceed.
      • If the communication modes of the controller and the application are not compatible, you must select Switch Communication Mode to transfer the application to the device.
   4. Select Modify open application with New Information column to update the open application to reflect the values going into the device.
      Note: When you select this option, the Controller Number is also updated.

6. Click Finish. The selected device code transfers to the device.

   Note: The Status bar displays information on the transfer progress and other status indicators.

   When the transfer completes, the Finish button changes to Done. This change does not happen if you select the Close wizard after successful transfer check box on the Transfer Summary screen. Instead, the wizard closes.

7. Click Done.

If you experience difficulty transferring an application to a device, see Troubleshooting.