Response time vs switching frequency compares a time interval with a repeated-event rate. Keep each field’s definition and conditions attached to its value. A sensor’s frequency entry alone does not describe every short signal that an installed system needs to detect.
For an aluminum machine inquiry, describe the event being detected and the receiving input. Ask the controls provider to review the actual pulse pattern and complete signal path. This makes the timing requirement clear before a device is selected.
On this page
1. Read response time vs switching frequency by definition
SICK’s switching-frequency glossary describes the number of sensor switching operations over a stated time interval. Read the applicable product document for the conditions behind its frequency entry.
The SICK W9-3 product information dated February 21, 2011 provides a historical example of those conditions. Its technical table treats response time and switching frequency as separate entries. The notes associate response time with signal transit under a resistive load and frequency with a 1:1 light/dark ratio.
That catalog example explains why footnotes matter. Obtain the applicable current datasheet for the actual offered sensor. No numerical rating from that historical document is assigned to a JiurunCut machine here.
A time field needs its beginning and end identified. Ask the provider whether the quoted entry describes a particular sensor response, another delay or a configured feature. Retain the original heading and its definition.
A frequency field needs its event convention and unit retained. Hertz expresses a rate per second, while milliseconds express a duration. Converting a period to a frequency does not turn it into the provider’s differently defined response time.
If a comparison sheet gives only “speed,” ask for the complete field names. Two values can look compatible while describing different parts of the signal behavior.
2. Describe the active and inactive durations
Define the physical event in the application brief. It could be a presented feature passing a detection point or another identified machine condition. State which event the proposed device is intended to report.
Ask the controls reviewer to identify the shortest relevant active duration and the interval between events. Keep the detection definition connected to those durations rather than using overall machine cycle time as a substitute.
Include the target geometry and path where they affect the review. For a workpiece detection task, identify the relevant presented feature. An overall aluminum bar length may leave that feature’s passage undefined.
If the application includes several profiles or changing spacing, include those cases in the brief. The reviewer needs to know the conditions the proposed arrangement is expected to cover.
The sensor operating-distance guide addresses the separate target-and-distance question. Here the review concerns the timing pattern after the actual detection task has been identified.
Keep equal active and inactive durations distinguishable from unequal ones. A repeated pattern can retain the same overall rate while having a much shorter active interval.
Two fictional patterns at the same rate
Imagine an idealized timing record, P46. A rectangular presented feature travels at an assumed constant 1,000 mm per second. Feature starts are 20 mm apart. For this arithmetic exercise, assume the active event lasts exactly while the feature passes the reference point.
These are invented geometry and timing inputs. They do not describe a real sensor’s optical response, detection boundary, approved machine setting or successful test.
The interval between feature starts is 20 ÷ 1,000 seconds: 0.020 seconds, or 20 milliseconds. That repeated-start pattern has a frequency of 1 ÷ 0.020 = 50 Hz.
Pattern A has an assumed 10 mm presented length. Its active interval is 10 milliseconds and the remaining inactive interval is 10 milliseconds. Pattern B has an assumed 2 mm presented length: 2 milliseconds active and 18 milliseconds inactive.
| Pattern | Timing in each 20 ms period |
|---|---|
| A: 10 mm feature | 10 ms active, 10 ms inactive; 50 Hz repeated-start rate. |
| B: 2 mm feature | 2 ms active, 18 ms inactive; 50 Hz repeated-start rate. |
The equal 50 Hz entries leave the active-duration difference hidden. Retaining the complete pattern gives the controls reviewer the information needed to assess the actual selected arrangement.
The example cannot approve a sensor or receiving input. A real review needs their applicable specifications and the actual detection conditions. Keep that review separate from this idealized arithmetic.
3. Review which input must receive the event
Ask the machine or controls provider to identify the complete receiving path. Name the sensor output, receiving input and relevant processing arrangement in the review record.
Request the applicable input timing requirements and any relevant configured processing. Have the responsible specialist explain how the proposed combination recognizes the required event.
The PNP versus NPN guide explains another compatibility field. Correctly identifying the electrical output still leaves the timing requirement to be reviewed.
If evidence includes a captured signal, ask where the capture was taken and which event it represents. A sensor-output observation and a recorded controller event need their observation points identified.
For an acceptance trial, define the relevant configuration, event pattern and requested observation before the work begins. Retain the resulting evidence with the reviewed scope and sample or setup identity.
This article does not provide a live wiring test, input-filter setting or controller modification. Use the approved system review and authorized personnel for actual implementation.
Prepare a useful timing inquiry
State the detection function in plain language. Add the actual target or event description, relevant motion or duration information and receiving-interface identity. Ask the provider to list any unresolved assumption.
Keep the complete device reference and current supporting document with the reply. Record response and frequency information in separately named fields with their conditions and units.
When an alternative sensor is proposed, ask which application cases the comparison covers. A higher headline frequency does not complete a review of the supplied configuration.
Send JiurunCut the aluminum section and intended cutting workflow for a machine discussion. Identify any material-presence or integration event that the proposal needs to explain, together with the requested documentation and verification scope.
Questions about response time vs switching frequency
Does 50 Hz define the shortest active pulse?
It defines a rate under its stated convention. The fictional example has the same repeated-start rate with two different active durations.
Can I take the reciprocal of a response-time field to obtain its rated switching frequency?
Read the manufacturer’s definitions and conditions for both fields. A reciprocal calculation alone does not establish the separate product rating.
Does the sensor datasheet prove that the controller recorded every event?
Identify the complete receiving path and its applicable evidence. Keep a component entry in its stated scope.
What information should remain beside the timing value?
The field definition, unit, device reference, relevant conditions and observation point. For a repeating event, retain the active and inactive portions of its pattern.