The following list includes prerequisites for successfully installing and using a Video Driver. The contents of this list and the exact implementation of the items may vary depending on the particular type of Video Driver, and the particular types of devices that are installed under the Video Driver network.
-
NiagaraAX-3.2 or later
From your PC, use WorkbenchAX 3.2.nn (or later) installed with the “installation tool” option selected (“This instance of Workbench will be used as an installation tool”). This option installs the needed distribution files (.dist files) for commissioning various models of remote JACE® platforms. The dist files are located under your NiagaraAX installation directory under a “sw” subdirectory. For details, see “About your software database” in the NiagaraAX Platform Guide.
-
NiagaraAX license feature for “video driver”, “remote video”, and specific video vendor driver.
In addition to the “videoDriver” feature entry in the license file, (see Figure 1), you also need a vendor-specific (for example, “dedMicrosDvr”) feature entry in the license. Other device limits or point limits may exist in your license as properties associated with those features.
Starting in NiagaraAX-3.4, an Enterprise Video feature “remoteVideo” is available as a licensed feature as well.
-
The following jar files (version 3.2.22.6 or later) must be present in your NiagaraAX installation (or already on the target station’s JACE).
-
devDriver.jar
-
devHttpDriver.jar
-
devIpDriver.jar
-
devVideoDriver.jar
-
videoDriver.jar
-
remoteVideo.jar (required for Enterprise Video features, NiagaraAX-3.4 and later)
-
In addition, you need a driver module for the CCTV equipment associated with the purchased driver. For example, dedicatedMicros.jar is used for Dedicated Micros equipment.
-
-
Network access
Network access between the station and all video devices. This includes the following:
-
Device IP address and port number
The device IP address and port number are used to configure UDP communications for the device.
-
User name and password for access to all devices, as required.
Credentials are required for http access to devices for configuration, as specified by each individual driver.
-
