top of page

Monnit Pulse Counter Below 40 Hz but Missing Counts? Check Pulse Width

Nov 7
5 min read

A pulse counter can miss valid events even when the average frequency looks comfortably below its filter rating. The missing detail is often pulse width: a short electrical pulse followed by a long pause is not the same waveform as a square wave at the same frequency. Check both before changing the meter factor or accepting a low-speed demonstration.


This guide uses Monnit’s ALTA single-input pulse-counter datasheet. It concerns acceptance of the input waveform, rather than accumulator resets or retained totals. Confirm the exact supplied model and firmware; do not transfer settings from the dual-input counter simply because both products count pulses.


Original conceptual illustration of Monnit Pulse Counter Below 40 Hz but Missing Counts? Check Pulse Width. Unbranded engineering concept, not a specific product or customer installation.

Original ProSense illustration. Equipment forms and signal paths are conceptual; use the supplied product documentation for actual specifications.


Key takeaways


Check event rate and minimum pulse width together. A valid frequency alone does not establish a valid waveform; compare raw counts before changing engineering-unit scaling.


Read the two limits together


Monnit lists three single-input filter choices: no filter, 40 Hz and 4 Hz. Its technical table pairs the 40 Hz filter with an approximate 25 ms minimum pulse width, and the 4 Hz filter with approximately 250 ms. The accompanying note requires input rate below the stated maximum and pulse width above the stated minimum. Treat those as simultaneous conditions, not alternative ways to qualify a signal.


The manufacturer describes filtering pulses shorter than the reciprocal of the filter frequency. That explains why counting can fail at a seemingly modest frequency: the period between events can be long while each individual pulse remains too short. The no-filter option removes noise rejection; it is not an automatic cure for an unverified interface.


Monnit industrial single-input pulse counter in a grey mounting enclosure with black antenna and coiled input lead
Monnit industrial single-input pulse counter with antenna and input lead - ProSense catalogue product photograph, not a customer installation.


A hypothetical signal that passes one check and fails another


Suppose an isolated test source produces ten pulses per second. Each cycle lasts 100 ms, but the active pulse lasts only 10 ms, followed by 90 ms inactive. Ten hertz is below the nominal 40 Hz filter rate. However, the 10 ms pulse is shorter than the table’s approximate 25 ms minimum. The frequency comparison alone therefore does not establish compatibility.


Now suppose the same ten-hertz test waveform has an active duration of 40 ms and an inactive duration of 60 ms. The active duration is longer than 25 ms, so it clears that particular screening check. This is still not proof of an accepted installation: electrical levels, selected detection edge, actual count and behaviour across the operating envelope must also be verified. These numbers are illustrative test conditions, not recommended settings for a plant.


Rate and width are separate. Hypothetical source: 10 Hz. Period: 100 ms per cycle. Active pulse: 10 ms. 40 Hz filter: about 25 ms minimum. Rate alone does not qualify the pulse. Original explanatory infographic; examples are hypothetical.

Original explanatory diagram. It summarises the checks described in this article; it is not a wiring drawing, product screenshot or customer test result.


Build a waveform acceptance record


Ask the meter supplier for the output waveform at the highest intended operating rate. Record whether pulse width is fixed or varies with rate, the shortest stated active duration, the interval between pulses and the electrical output type. If the output can be configured, retain its current settings before proposing a change. An unspecified duty cycle should remain an open question.


Record the exact counter model, filter, detection type and reporting mode. The single-input datasheet allows positive-edge, negative-edge or both-edge counting. Define what one process event should produce in the reported count; selecting both edges changes the interpretation. Verify the installed settings rather than inferring them from a screenshot of a different sensor.


Have a competent person confirm the electrical interface and arrange an authorised test method. The published single-input specification includes passive switches and compatible active signals up to 15 VDC. Do not connect a 24 V industrial output directly on the assumption that every industrial counter accepts it. Hazardous-area suitability and any isolation requirements need their own application-specific review.


Test a known count across the required conditions


Use a permitted isolated test arrangement or an approved process test. Introduce an independently known number of valid events. Keep a record of the waveform used, expected count and reported raw count before applying engineering-unit scaling. Include the shortest expected pulses and the highest required event rate; a slow hand-operated contact test cannot demonstrate either condition.


Check reporting mode when comparing results. An interval count and an accumulated value require different comparisons. Allow the documented reporting sequence to complete, preserve raw observations and separate an input-count failure from a delayed display update. Repeat the same known-count test after an authorised configuration change so that the improvement is measurable.


Avoid hiding a counting problem with calibration


Do not increase the volume-per-pulse multiplier to compensate for losses that grow with speed. That can make one operating point look correct while making another worse. Likewise, reducing the filter without assessing noise can exchange missing events for extra counts. If the required waveform does not meet the input specification, review the meter output configuration or a suitable interface with the responsible integrator.


A useful support enquiry includes the exact counter model, meter output specification, peak rate, shortest pulse width, selected filter and a before-and-after known-count comparison. Exclude passwords and device security codes. Retain any untested operating conditions in the handover record; this monitoring check does not establish a certified safety or revenue-metering function.


Manufacturer reference




Diagnostic comparison


Symptom

Next evidence

Counts fall as speed rises

Compare shortest pulse width and peak rate with the exact input specification.

Slow hand test succeeds

Repeat an approved known-count test across the required waveform envelope.

Scaling fixes one point only

Compare raw counts before altering the K factor.


Recommended equipment / related solutions


Equipment starting point: Monnit industrial single-input pulse counter. Confirm the supplied variant, current documentation and application conditions before selection.


For selection and integration scope, review ProSense technical services and project support. Provide the exact model and the evidence described above; scope and compatibility require confirmation.



Frequently asked question


Should I change the K factor to recover missing pulses?


First verify the raw count against a known event count. A multiplier cannot establish that all events are captured across the operating range.


Send the model and diagnostic record through ProSense Instruments technical enquiries to discuss equipment selection and the appropriate next step.


Need help with your application?

For instruments and product selection, visit ProSense Instruments, email sales@prosenseinstruments.com.au or call 1800 560 854.


For monitoring and automation projects, visit ProSense Solutions or email sales@prosense.com.au.


For software enquiries, visit ProSight Software or email info@prosightsoftware.com. Confirm integration requirements for the exact instruments and system.

Comments


bottom of page