Monnit Dry Contact Missed a Repeat Event? Test the Re-Arm Wait
A dry-contact input reports the first operation during a commissioning test, but a second operation produces no new event. Later, the sensor checks in and shows the expected contact state. That combination can look like an intermittent radio fault. Before moving the gateway or replacing the sensor, compare the event spacing with the configured Time to Re-Arm.
The practical answer is to test two separate requirements: whether the sensor reports the present state, and whether it captures repeated operations at the spacing your process needs. A correct present-state reading does not prove that every intervening operation was recorded.
What the re-arm setting changes
Monnit’s ALTA dry-contact configuration guide defines Time to Re-Arm as a wait after a triggering event before further triggering events are recognised. Its five-input guide also documents this setting, with Open, Closed or Changed trigger choices for contacts 1–5. Check the guide for the actual sensor family; do not transfer menu assumptions between ALTA, PoE and Next Wi-Fi products.
Monnit separately describes an event sensor’s heartbeat as a routine report of current state and device health. Its re-arm guidance explains the trade-off: shorter waits allow more frequent event detection, while longer waits reduce activity and battery demand. Changing the routine heartbeat is therefore a different adjustment from changing the event re-arm wait.
Identify the actual contact and sensor
The pictured ProSense catalogue item is the MONNIT Industrial 5-Input Wireless Dry Contact Sensor, model MNS2-4-IN-DC-05-L03. Record the supplied model, gateway arrangement, firmware information available in the portal and the settings actually accepted by the device. Verify the matching regional radio configuration before specifying replacements.

Confirm that the proposed output is a suitable voltage-free contact. Monnit warns that external AC or DC voltage damages these dry-contact inputs. A powered alarm output is not automatically suitable. Have a competent person review electrical interfaces and any common connections; this guide does not authorise work inside an energised panel or modifications to a safety circuit.
Run a controlled spacing test
Use an authorised bench arrangement or a site-approved test method that cannot operate machinery. Review attached rules and control actions before creating events. Record the input number, physical state, selected trigger condition, re-arm setting, device event record and notification outcome separately.
First prove one deliberately slow cycle on the chosen input. Confirm that the displayed contact meaning agrees with the physical test and that the intended transition is the trigger. If this fails, resolve input mapping, contact suitability and configuration delivery before investigating repeated events.
Next repeat the triggering transition with a clear interval longer than the configured re-arm period. Then run a separate trial with a shorter interval. Keep a timestamped observation sheet for the physical operations. Avoid testing exactly at the boundary: stopwatch uncertainty and system timing make a marginal result difficult to interpret.
A hypothetical acceptance example
Suppose an operational status contact must record two separate closures 20 seconds apart. For illustration only, assume the sensor has accepted a 60-second re-arm setting and uses Closed as its trigger. Close the test contact at time zero, reopen it after five seconds, then close it again at 20 seconds. The second closure falls inside the stated wait, so an additional event must not be assumed.
Repeat a comparable cycle after a clear margin beyond the re-arm period. If this later operation reports while the earlier repeated operation did not, the results support a timing explanation. They are not proof of a defective radio. A later heartbeat showing Closed cannot reconstruct the missing chronology or establish how many closures occurred.
Set the requirement before changing the wait
For occasional equipment-status changes, a deliberate wait may be acceptable. For cycle counts, short fault pulses or closely spaced operations, write down the minimum event separation and acceptable loss before choosing the input technology. Do not promise complete production counts merely because one contact test succeeded.
On a five-input unit, include tests involving different inputs as well as repeated operations on one input. The cited definition does not establish a separate independent re-arm timer for every channel. Confirm the actual cross-input behaviour with the supplier and test record rather than assuming it.
Common mistakes are shortening the heartbeat to fix event suppression, treating an email count as a physical operation count, changing several settings together and signing off after only one transition. If the device event exists but a notification is absent, investigate the rule and delivery chain separately.
Retain the before-and-after settings and test evidence. Ask ProSense to review the exact model, contact interface, required event spacing and observed results before a wider rollout. Wireless status monitoring is not a certified machine safety function.
Need help with your application?
ProSense Instruments - discuss instruments and communications hardware: sales@prosenseinstruments.com.au or 1800 560 854.
ProSense Solutions - discuss system integration: sales@prosense.com.au. ProSight Software - discuss software requirements: info@prosightsoftware.com. Device integration must be confirmed for your application.




Comments