Upload - Metasys - LIT-12011964 - Software Application - System Configuration Tool - 13.2

Metasys SCT: System Configuration Tool Help

Brand
Metasys
Product name
System Configuration Tool
Document type
User Guide
Document number
LIT-12011964
Version
13.2
Revision date
2020-01-21
Language
English

The Manage Archive wizard upload option transfers a copy of the engine or Metasys server archive database into the archive database of SCT. Perform an upload to update the SCT archive database with changes made in the online mode. The engine or Metasys server database overwrites the SCT archive database for the device being loaded. The direction of an upload is from the engine or Metasys server to SCT.

Note: You can schedule uploads for various devices at a specific time. However, the software can only run one device upload simultaneously until the request is completed.

Upload options include:

  • Include Field Controllers

    The upload function lets you upload the .caf files from field controllers into the archive database. If you want to upload the .caf files from field controllers reporting to the engine, the supervisory device must be at Release 6.0 or later. During the upload process, SCT creates or updates the Resource extension for the field controller. The View Status window in ActionQ reports the field controllers whose .caf files were uploaded successfully or unsuccessfully. After a .caf file is imported, you can use the Export .Caf File option to export the file to a location on your computer, then edit or commission the file with CCT.

    Note: When you perform an upload from an ADS, do not select the Include Field Controllers check box. To upload a full site, include field controllers in a separate upload to any upload that includes ADSs.
  • Include Security

    SCT gives you the option to include the security database when you perform an upload. To include a security database upload, select the Include Security box. By default, the box is selected for a standard device upload.

  • Include HTTPS Certificates

    The upload function lets you upload HTTPS certificates from a network engine. By default, the box is not selected for an engine upload. If no engine certificate is currently stored in the archive, the upload adds the certificate to the archive if one exists.

Note: If the field controller contains Metasys Release 6.5 or later code, the Focus view of the field controller records the date and time of the most recent .caf file upload.
Figure 1. Manage Archive wizard - Upload

Figure 2. Upload Workflow Diagram

To Upload from a Device:

Notes:
  • A Site Director's archive-defined software version must match the physical versions, or the upload fails.
  • At Release 11.1 and later, supervisory devices with firmware at an earlier release than what is specified in the SCT are automatically upgraded to the SCT archive database release during the upload. For example, a device listed as Release 8.0 in the SCT that is actually loaded with Release 7.0 firmware will convert the Release 7.0 data to Release 8.0 as specified in the SCT. Following the conversion, perform a code download to synchronize the device firmware release to the SCT archive database release so that you can execute future downloads to the device.
  1. On the Tools menu, select Manage Archive. The Manage Archive wizard appears.

  2. Select Upload from Device.

  3. If you want to upload the .caf files from all field controllers defined on the engine, click Include Field Controllers.

    Notes:
    • When you select the Include Field Controllers option, an indication of the field controller upload progress appears in the Actions in Progress window.
  4. If you want to exclude the security database, click the Include Security check box to deselect the option.

    Note: By default, the Include Security check box is selected.
  5. If you want to include supervisory device certificates, click the Include HTTPS Certificates check box.

  6. Select the devices to upload and click Next.

  7. Select the upload Schedule method and click Next.

  8. Select the Site Login method.

    Figure 3. Site Login Screen

    To communicate through the Site Director:
    1. Select the Communicate via Site Director check box.
    2. Enter the username and password for an administrator account for the Site Director.
    3. Click Test Login. When login has passed, click Next.
    To communicate through individual devices:
    1. Enter the username and password for an administrator account on each physical device.
    2. Select the check box for the devices you want to communicate with.
    3. Click Test Login. If the Status column contains Login ID is not OK for any devices, repeat steps 8a through 8c until all devices have a Login ID is OK status. Devices with a blank status indicate that you have not attempted Site Login through the Manage Archive wizard.
      Note: Successful logins are no longer able to be re-checked after they have reached a Login ID is OK status.
  9. Select upload reoccurrences and click Next.
  10. Review the upload Summary and click Finish to perform the upload.
  11. After the upload process is complete, verify that the Completed Actions window reports OK in the Completion Status column.
    Note: After the upload process completes, the View Status window in ActionQ reports the number of field controllers whose .caf files were uploaded successfully or unsuccessfully.
Table 1. Manage Archive wizard Screens

Screen

Purpose

Action

Select Upload From Device as the type of action and select the upload options.

Select Devices

Select one or more devices to upload. Use the Ctrl and Shift keys to select more than one device.

Schedule

To upload now, click Upload Now. To upload a device at a later date, click Schedule Upload and select the date and time you want to upload the device.

Site Login

Select Communicate via Site Director if the destination device is not accessible on the SCT server's local area network.

Note: This option slows down the operation if used unnecessarily.

If a different user name and password are required, enter the user name and password.

Repeat Upload

If you want the upload process to automatically repeat, enter the number of days between uploads. Enter 0 if you do not want to automatically repeat uploads.

Note: Use this option only if all changes made to the device are online.

Summary

View the basic parameters of the device or devices just uploaded.

ActionQ Processing of Uploads:
Figure 4. Upload Process

Table 2. Upload Process Callouts and Description

Number

Process Description

1

After you configure an upload in the Manage Archive wizard, the Manage Archive wizard sends the upload command to the ActionQ feature in the SCT.

3

  1. The ActionQ begins the upload process at the time defined for uploading the engine or Metasys server database.
  2. The engine or Metasys server creates an archive file of its database.

4

  1. The ActionQ transfers the engine or Metasys server archive file to the SCT archive database. If you selected the Include Field Controllers option, ActionQ also copies the .caf file of each field controller into the archive for engines at Release 6.0 or later. If you selected the Include HTTPs Certificates option, ActionQ also copies the certificate file of the supervisory device into the archive for engines at Release 8.1 or later.
  2. The ActionQ replaces the existing archive database with the engine or Metasys server archive file.

5

The final status of the upload is displayed in the ActionQ.