Connect Cycle and Counter Signals to a Measure Point
Learn how to connect a machine's production counting signal to a Measure Point in GS Desktop so that Good Solutions can register production cycles and produced amounts.
Overview
A Cycle Signal registers pulses generated by a machine during production.
For example, a machine may generate one pulse every time a product is completed.
Good Solutions uses these signals to collect production information, including:
- Production cycles
- Produced amounts
- Cycle times
- Production interruptions, when cycle-based stop detection is appropriate
A Counter Signal also registers production quantities, but without using the signal itself for stop detection.
Both approaches require the incoming machine signal to be correctly connected to the relevant Measure Point.
Before You Begin
Make sure that:
- The machine is connected to Good Solutions through a supported data collection interface.
- The appropriate input has been configured.
- The Measure Point has been created in GS Desktop.
- You know which I/O interface and input carry the production signal.
For an IoT connection, first complete the steps in Configure an IoT Device in Good Solutions.
Step 1: Open Cycle Signal Connections
- Open GS Desktop.
- Navigate to Settings → Machine Data.
- Select Cycle Signal Connections.
- Click Create.
A new signal connection is created.
Step 2: Select the Machine Input
- Locate the I/O-Interface Input field.
- Click the connection icon next to the field.
- A list of available I/O interfaces and signals opens.
- Select the correct I/O interface and machine input.
- Click Save and Close.
Important: Make sure you select the input that actually registers production cycles.
If you are using the vibration function of an IoT device, the original configuration guide specifies selecting Analyze Input.
Step 3: Connect the Signal to a Measure Point
Once the machine input has been selected:
- Locate the Measure Point connection field.
- Click its connection icon.
- Select the Measure Point that should use the signal.
- Click Save and Close.
The signal is now associated with the selected Measure Point.
This tells Good Solutions which part of production the incoming cycle pulses belong to.
Step 4: Save the Signal Connection
Review the selected I/O input and Measure Point.
Save and close the connection configuration.
The Cycle Signal connection is now configured.
Understanding Cycle Signals and Counter Signals
Although both signals can register produced amounts, they serve slightly different purposes.
Cycle Signal
A Cycle Signal can be used to register production cycles and support stop detection.
For machines with short and regular production cycles, Good Solutions can use the time between cycle pulses to determine whether production has stopped.
Counter Signal
A Counter Signal registers produced quantities without using the counter itself to determine running or stopped states.
It is commonly combined with a separate Production Time Signal.
Example:
A machining center takes three minutes to complete a product.
- The Counter Signal registers each completed product.
- The Production Time Signal indicates whether the machine is running.
This allows production quantities and machine availability to be measured separately.
The detailed procedure above follows the documented Cycle Signal Connections workflow. The supplied source does not describe a separate Counter Signal configuration screen; the exact setup for counter-only operation should therefore be confirmed for the installation.
Understanding Amount Factors
A single production cycle does not always produce one unit.
For example, an injection molding machine might produce four parts during each cycle.
| Registered cycles | Units per cycle | Produced amount |
|---|---|---|
| 100 | 1 | 100 |
| 100 | 2 | 200 |
| 100 | 4 | 400 |
Good Solutions supports amount factors to translate registered cycles into produced quantities.
Make sure the relevant production quantity settings reflect the machine's actual output.
Verify Your Configuration
After creating the connection, verify that Good Solutions receives the correct production information.
Check the Production Count
- Record the current production count.
- Run a known number of production cycles.
- Check the registered production amount.
- Compare the result with the expected quantity.
For example, if a machine produces four units per cycle, ten cycles should correspond to 40 produced units.
Check the Measure Point
Verify that production is registered against the intended Measure Point.
Check the Timeline
Open the Timeline in Good Solutions Web and review the production activity.
For a Cycle Signal used for stop detection, check that the displayed running and stopped periods correspond to actual machine behavior.
Common Problems
No production is registered
Check the IoT input, signal connection, and Measure Point association.
Production is registered against the wrong machine
Verify that the correct Measure Point was selected.
The produced amount is incorrect
Review the amount factor and the relationship between machine cycles and produced units.
Normal production is interpreted as a stop
Check whether cycle-based stop detection is appropriate for the machine's cycle time. A separate Production Time Signal may be needed.
Key Takeaways
- Cycle Signals collect production pulses from machines.
- The signal connection associates an I/O input with a Measure Point.
- Cycle Signals can support both production counting and stop detection.
- Counter Signals count production without independently determining machine availability.
- Amount factors are important when one cycle produces several units.
- Always validate production counts against actual machine output.