Micro switch switching frequency testing measures how many complete operating cycles occur in a stated time. A reliable result depends on distinguishing the actuator’s actual movement from the test controller’s command and from the electrical transitions recorded at the contacts. Those counts can differ, particularly when the contacts bounce or the test does not observe the actuator directly.
A frequency measurement is not, by itself, a rated operating limit or an endurance result. Compare it with the switch’s documented conditions and limits, and report the method and conditions so another person can understand what was measured. The method below focuses on a controlled check of mechanical cycling and electrical contact state, not a full life-cycle qualification.
Micro switch switching frequency testing: define the quantity before measuring
Define one complete operating cycle before collecting data. For this test, count a cycle as one full repeat of the intended actuator motion and switching sequence. State the direction or sequence used so that the count is unambiguous. Report frequency as cycles per second or cycles per minute, and identify the observation interval. For example, a count over a fixed interval can be divided by the duration of that interval to calculate the observed cycle rate; do not report the interval’s total cycle count as a frequency without stating the duration.
Make and break are contact-state transitions, not separate complete cycles. If a test sequence includes one make and one break during a complete cycle, count the sequence as one cycle, not two. Record the contact transitions separately when they are relevant to the check. That distinction matters because transition counts may not match mechanical cycle counts.
Keep four quantities separate in notes and conclusions:
- Commanded test rate: the rate requested by the controller or actuator system.
- Observed cycle rate: the rate calculated from cycles actually observed during the measurement interval.
- Rated maximum operating frequency: a documented boundary, when the applicable switch documentation provides one. It is not established by the test merely because a particular rate was achieved.
- Endurance-cycle total: the accumulated number of cycles in an endurance test. A total count is not a frequency unless paired with a time interval, and a frequency result does not establish endurance.
An electrical-life endurance count must be read with its stated load, operating sequence, and test conditions. Do not use an isolated operation count as though it were a universal operating-frequency value or proof that the switch will perform similarly under other conditions.
Set up a test that captures mechanical and electrical behavior
Use a controlled actuator that can apply a repeatable motion, together with a way to observe actual actuator movement or cycle timing. The controller’s set rate is useful as a test input, but it is not evidence that the switch completed each requested cycle. The observation method should let you compare commanded cycles with the actuator’s actual movement over the same measurement interval.
Monitor the electrical contact state with instrumentation appropriate to the circuit and the expected transition speed. Arrange the measurement so the contact state and mechanical observation can be associated in time. If the instrument cannot resolve changes at the speed being tested, the transition record may be incomplete or ambiguous. State this limitation rather than treating the displayed transition count as definitive.
Record the test conditions that bear on interpretation, including the electrical load and conditions, actuator travel, duty cycle, and temperature. Use the switch documentation to determine which conditions and limits apply; do not assume a universal test setting. For travel terminology, pretravel runs from free position to operating position, while overtravel runs from operating position to the extreme permitted actuator position. If travel is measured or controlled, report the reference points and the measured values rather than using “travel” without qualification.
Before running the test, document the instrument and observation method, the planned rate or rate range, the measurement window, and how a complete cycle will be counted. These details make it possible to distinguish a genuine change in cycling behavior from a change in how the test was commanded or recorded.
Run the frequency check and inspect contact transitions
Start within the operating conditions documented for the switch. Set or increase the test rate only within stated limits. If the applicable documentation does not establish a limit or a condition needed for the intended comparison, leave that point unresolved rather than inferring a safe or valid rate from a short successful run.
During each measurement interval, compare three records where available: the commanded cycles, the observed mechanical cycles, and the recorded electrical contact transitions. Calculate the observed frequency from the mechanical cycle count and the interval duration. Keep transition counts separate. A controller command can exceed the number of completed mechanical cycles, while the electrical record can contain more transitions than the mechanical record.
Inspect the electrical trace or state log for contact bounce. Bounce is a sequence of rapid contact-state changes associated with a switching event. It can cause the instrument to register several electrical transitions around one mechanical operation, so counting every transition as a separate operating cycle would overstate the mechanical frequency. The evidence available here does not specify a universal bounce threshold or a required sampling rate. Use an observation method suited to the expected transition speed, document its limitations, and avoid claiming that bounce was absent if the method could not resolve it.
Also note discrepancies such as missed operations or unclear timing. Repeat measurements using the same stated conditions and counting method to assess whether the result is consistent. If the mechanical observation and electrical record disagree, report the discrepancy and investigate the measurement record before interpreting the frequency. Do not silently substitute the commanded rate for an observed result.
Interpret results against the micro switch’s documented limits
Compare the measured result with the applicable documentation, using the same relevant load, operating sequence, travel references, and test conditions where those are specified. A documented maximum operating frequency is a limit to compare against, not a value that can be inferred from the test. If documentation does not state a relevant boundary, report that no comparison was established rather than supplying a general threshold.
A short frequency check shows behavior only under the conditions and during the interval observed. It does not establish endurance, service life, or performance under different electrical loads, actuator travel, duty cycle, temperature, or other conditions. In particular, an endurance-cycle total and an observed cycle rate answer different questions. A cycle total describes accumulated operations in its stated test; a rate describes operations per unit time. Neither should be presented as the other.
Make the report auditable. Include the switch identification used in the test records, the commanded rate, observed mechanical cycle count and calculated rate, observation duration, electrical transition count, count definitions, and any observed bounce, missed operations, or timing ambiguity. Record the load and electrical conditions, actuator travel and reference points, duty cycle, temperature, applicable documented limits, instruments or observation method, sampling limitations, deviations, and outcome. If a condition was not measured or was unknown, mark it as such instead of filling the gap by assumption.
Related guides
Keep frequency testing safe and within scope
Treat the energized measurement as an electrical test, not merely a mechanical timing check. De-energize the circuit before changing wiring, and protect against exposed live parts during energized measurements. Consider hazards associated with the switching load and use measurement and isolation methods appropriate to the circuit. The particular load and wiring determine the relevant precautions, so this method does not prescribe a universal circuit arrangement.
Keep conclusions within the test’s scope. Frequency testing alone does not establish switching capacity or long-term reliability, and a result under one set of conditions does not demonstrate performance under different conditions. Report what the actuator did, what the electrical measurement recorded, and how those observations compare with the switch’s documented limits. When the documentation or instruments leave a question unresolved, state that limitation explicitly. This keeps the reported micro switch switching frequency testing result distinct from a controller setting, a rated boundary, and an endurance-cycle total.
Sources and references
- Defense Logistics Agency ASSIST: MIL-PRF-8805K: Switches and Switch Assemblies, Sensitive, Snap Action, General Specification For