The rule is that two MUX8 boards can be wired in parallel but not in series. So don't try and place one downstream off of another MUX8.
Connecting MUX8 in series is not recommended as daisy chaining will add signal skew and will cause comm problem. Since the mux8 has strong biasing (pull up/pull down) to maintain signal marking when not driven, more than two of them connecting in parallel will overload the RS485 transceiver.
The relays are dry contacts.
A dry contact output on a device like a relay means that the contacts have no voltage or potential difference across the two contacts. The contacts simply provide an open or closed state to another device.
A wet contact output on a device like a relay means that when the relay is activated, the relay output contacts supply a voltage to whatever device is connected to the relay output contacts, say for example a light or motor.
What is it?
Controller Data at Rest is encryption inside the Controller. When enabled, data that is stored is encrypted.
How do you enable the encryption?
1. Login to the controllers webpage
2. Check the checkbox on the Security Options webpage. Note: If a configuration is already in the controller the configuration will be deleted and a new one will have to be sent down.
3. Apply Settings and Reboot
Things to Note:
1. Firmware upgrades will keep encryption intact
2. If you want to disable encryption the only way to do this is to bulk erase the controller.
Note it is possible that the provisioned certificate will be removed during this process. Should this occur the OEM partner will need to contact Mercury to have a replacement certificate issued.
3. When enabling encryption, if the configuration is already present in the controller the configuration will be deleted.
HID Global / Mercury Security access control solutions are cyber tested and do not contain components from those companies prohibited under NDAA 2019 Section 889. Compliant Controllers and downstream boards include (but are not limited to) the following:
Mercury part number LP2500
Mercury part number LP1502
Mercury part number LP4502
Mercury part number LP1501
Mercury part number MR50-S3
Mercury part number MR52-S3
Mercury part number MR62e
Mercury part number MR16in-S3
Mercury part number MR16out-S3
Yes, SNMP (Simple Network Management Protocol) is supported on Mercury products with an Ethernet port except for the MR51e and MR62e. The EP series controllers supported v2c and the EP4502 and LP Series support both v2c as well as v3.
SNMP is off by default but can be enabled via the web configuration pages.
Mercury does not provide a custom MIB file. The products just use some of the standard networking MIB files. The MIB files include:
Mercury does have a Conflict Minerals policy. Please see the attached document.
The Mean Time Between Failure (MTBF) calculations can be found in the "MTBF Calculations" file.
Mercury products are tested against the Federal Communications Commission (FCC) Part 15, Class A specifications. For the list of conforming products please refer to the associated certification file.
Regarding the Waste Electrical and Electronic Equipment (WEEE) Directive, Mercury Security believes it is exempt based on the definition of “components and sub-assemblies” in the directive. The WEEE standard refers to finished products only.