ex-VAT pricing shown

Now open for trade ordersGent, Morley-IAS & Xtralis stock added weekly — open to the trade.

VESDA Software

Xtralis VSW-356 VSM4 VESDAnet Detector Connection

Ordering code description
VSW-356 VESDAnet Detector Connection per detector
Licensing basis
One required per monitored detector

Overview

What it is and how it fits the system.

The Xtralis VSW-356 is the per-detector network connection ordering code for connecting a VESDA ECO or VESDA Sensepoint XCL detector to the VSM4 monitoring software via VESDAnet. One licence is required per monitored detector.

Technical overview

The Xtralis VSW-356 is the ordering code that provides per-detector network connection capacity within the VESDA Software range. It is used to link a single VESDA ECO or VESDA Sensepoint XCL detector to the VSM4 monitoring software across the VESDAnet infrastructure, bringing that detector under central supervision.

Because the code is licensed on a per-detector basis, one instance of VSW-356 must be ordered for each detector that is to be monitored. A site running several detectors therefore requires a matching number of these connection licences, scaling the VSM4 deployment as further detectors are brought online.

Falling under the Capacity ordering category, VSW-356 defines how many detectors the software may connect and monitor rather than supplying any physical hardware. It establishes the logical link that allows compatible detectors to report into VSM4 through VESDAnet, forming part of the wider integration between field devices and the monitoring platform.

For guidance on the physical wiring and mounting of the detectors themselves, refer to the installation manual, which covers the connection details that sit outside the scope of this ordering code.

Specifications

Full technical data for this part.

Ordering code descriptionVSW-356 VESDAnet Detector Connection per detector
Licensing basisOne required per monitored detector

Specifications sourced from manufacturer documentation.

Specifications per manufacturer documentation, subject to change — E&OE. Spotted an inaccuracy? Let us know