Skip to content
Toleron
Grindingsegmentationgatinggrinding

Gating a grinding cycle: why raw channels cannot gate and windows must

Compared against a level, a raw current waveform crosses it on every cycle. A reduced window crosses it where the cut begins and ends. That difference is the whole design.

Toleron Engineering · 24 August 2026 · 3 min read

Segmenting a process into the intervals that matter sounds like a threshold. It is not. At native sampling rate a current waveform is exactly that — a waveform — and comparing it against a level produces a crossing on every cycle of the signal, not one at the start and one at the end of the cut.

Reduce, then gate

The platform's window operators exist for this reason. A short window over a raw channel turns a waveform into a clean level that can be gated. Reduced signals are ordinary signals with a declared temporal class, and the type system refuses to wire a raw block stream into a gate directly — it names the reduction that is missing.

Two levels

  • The pass. The machine's own trigger says when a pass is running. It is the outer gate.
  • The cut. Inside the pass, a gate on the physical process marks when the wheel is actually in contact with the workpiece. Everything outside it — approach, spark-in, spark-out — stays out.

Both levels are evaluated at the edge, on the data's own clock. Which signal gates the cut is chosen per process, on real recorded passes: the gate must produce exactly one window per pass, with a clear margin, every time.

The unit of comparison

The result is exactly one in-cut window per pass, comparable across parts and days — the unit every feature and every model on the platform is computed on.

Next step

Bring intelligence to your machines.

Connect existing CNC equipment without replacing the machine or the controller. We start with one machine, real data and an honest acceptance run.