Reference Guide – DOC. 7150B
3-Series Control Systems
•
49
and then compared to the previous hash that is cached locally on the
control system.
If the hash in this file has changed, then the file defined in
fileUrl
will be downloaded and installed.
If the has in this file has not changed, then the file defined in
fileUrl
will not be downloaded and installed.
If no local hash cache exists, then the file will be downloaded.
The client must support parsing a full URL and downloads over HTTPS
and SFTP:
[http or ftp]://username:password@[hostname or
ip]:port/path/file
o
fileType
: Determines how the control system will handle the file
once it is downloaded. The value of this parameter must be one of the
following predefined types; undefined types are ignored by the client:
"firmware"
: Firmware update file (.puf or .zip)
"project"
: Standard VTZ project file
"config"
: Text file containing a list of console commands to be
executed
"UserProgram"
: Indicates a user program
Description of Manifest Parameters
ControllerHostName
This parameter indicates the hostname of the control system. The controller
must support wildcard characters "*" and "?", where "*" matches
x number of
characters and "?" matches exactly one character. A "*" indicates that all
controllers will act upon a manifest schema, while a partial match can be used to
limit the schema to a subset (for example, PRO-
??).
Using these wildcard characters, the same manifest can be used across multiple
control systems, which means that all control systems will try to update the
devices specified based on the details in the manifest. While this method is
recommended for Cresnet devices and devices on an internal gateway (since it is
controller-specific), it could cause issues with Ethernet devices, as they can be
accessed from multiple control systems.
