<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=220094881825886&amp;ev=PageView&amp;noscript=1">
Skip to content
  • There are no suggestions because the search field is empty.

Verify and Troubleshoot Machine Signal Connections

Learn how to check machine signal connections in GS Desktop, identify common configuration problems, and verify that Good Solutions receives accurate production data.

Overview

Correct machine data is essential for reliable production monitoring.

If a machine signal is missing, incorrectly configured, or connected to the wrong Measure Point, the resulting production information may be inaccurate.

This can affect:

  • Produced quantities
  • Running and stopped time
  • OEE calculations
  • Scrap and rework quantities
  • Production reports and dashboards

This article provides a practical checklist for validating machine signal connections and investigating common problems.

1. Understand the Data Collection Chain

When troubleshooting machine data, it is useful to understand how the information reaches Good Solutions.

A typical IoT-based connection follows this sequence:

Machine → Sensor or PLC → IoT Device → Signal Connection → Measure Point → Good Solutions

Each part of the chain must work correctly.

For example, a machine might generate a valid production pulse, but Good Solutions will not associate it with the correct production equipment if the signal connection points to the wrong Measure Point.

The same principle applies to other supported interfaces, such as OPC connections, although the configuration details differ.

2. Check the Physical Machine Signal

Start by confirming that the machine generates the expected signal.

Questions to investigate:

  • Is the sensor or PLC output functioning?
  • Is the signal connected to the intended input?
  • Does the signal change when the expected production event occurs?
  • Is the signal type suitable for the intended measurement?

Example:

If a machine is expected to generate one pulse per completed product, verify that this actually happens.

If one cycle generates multiple pulses, the registered production quantity may be too high.

3. Verify the IoT Device Configuration

For IoT-connected machines:

  1. Open GS Desktop.
  2. Navigate to Settings → Machine Data.
  3. Open RS-IoT/RSBlackBox.
  4. Select the relevant IoT device.
  5. Open Inputs.
  6. Find the input you want to investigate.

Check that:

  • The input has the correct name.
  • The correct physical input is being used.
  • The input type matches its purpose.

Check the Input Settings

Signal type Setting to verify
Cycle Signal IsCounterInput
Production Time Signal Pulse Input Status
Scrap Signal Correct input and Scrap Signal connection
Rework Signal Correct input and Rework Signal connection

4. Use Debug to Verify Incoming Signals

The IoT device configuration includes a Debug function.

This can be used to confirm that the device receives signal changes.

  1. Open the relevant IoT input.
  2. Enable Debug.
  3. Trigger the signal from the machine.
  4. Check whether the expected rising and falling signal edges are detected.
  5. Disable Debug when testing is complete.

Important: Do not leave Debug enabled after testing. The original technical documentation warns that doing so can cause unnecessary server load.

If the signal is not detected, investigate the machine output, physical connection, and selected input before changing higher-level production settings.

5. Verify the Signal Connection

Once you know the IoT device receives the signal, check its configuration in GS Desktop.

Navigate to Settings → Machine Data and open the relevant connection type:

  • Cycle Signal Connections
  • Production Time Signal Connections
  • Scrap Signal Connections
  • Rework Signal Connections

Check that:

  1. The correct I/O interface is selected.
  2. The correct input is selected.
  3. The connection is associated with the intended Measure Point.
  4. The configuration has been saved.

For Scrap and Rework Signals, also check the configured reason and quantity factor.

6. Validate Production Quantities

A signal can be received correctly while still producing inaccurate quantities.

This is often caused by an incorrect factor or a mismatch between machine pulses and actual production.

Example:

A machine produces four units per cycle.

During a test, the machine completes 25 cycles.

Expected production:

25 cycles × 4 units = 100 units

If Good Solutions registers only 25 units, review the amount factor.

If Good Solutions registers 200 units, investigate whether the machine generates more than one pulse per cycle or whether the factor is incorrect.

The same principle applies to Scrap Factors and Rework Factors.

7. Verify Running and Stopped States

For machines using a Production Time Signal, verify that the registered operating state matches actual machine behavior.

When the Machine Is Running

  • The running signal should indicate the expected active state.
  • Good Solutions should register running time.

When the Machine Stops

  • The signal should change to the expected stopped state.
  • Good Solutions should register the stopped period.

Review the relevant Measure Point in the Good Solutions Timeline to check the resulting production history.

If the machine appears to be running when stopped, or stopped when running, review the signal configuration and how the input state is interpreted.

8. Check the Measure Point Association

One common configuration problem is connecting a valid signal to the wrong Measure Point.

For example, the cycle signal from Packaging Line 1 might accidentally be associated with Packaging Line 2.

The signal itself may be functioning correctly, but the production data will appear under the wrong equipment.

To investigate:

  1. Open the signal connection in GS Desktop.
  2. Check the associated Measure Point.
  3. Confirm that it matches the physical machine.
  4. Correct the association if necessary.
  5. Save the configuration.

9. Common Problems and Possible Causes

Problem What to check
No production is registered Machine signal, I/O input, signal connection, Measure Point
Production quantities are too high Duplicate pulses, incorrect amount factor
Production quantities are too low Missing pulses, incorrect amount factor
Machine always appears stopped Running signal, Pulse Input Status, signal state
Machine always appears running Running signal changes, input configuration
Scrap is not registered Scrap input, Scrap Signal connection, Measure Point
Scrap quantity is incorrect Scrap Factor, number of pulses
Rework is not registered Rework input, Rework Signal connection
Data appears under the wrong machine Measure Point association
Incorrect Scrap or Rework Reason Reason assigned to the signal

10. Recommended Validation Procedure

Whenever a new machine connection is configured, perform a short controlled test.

  1. Confirm the machine signal. Verify that the expected signal is generated.
  2. Check the I/O input. Use Debug where appropriate to confirm incoming signal changes.
  3. Verify the signal connection. Confirm that the correct input and Measure Point are selected.
  4. Run a known production test. Record the actual number of cycles or produced units.
  5. Compare the results. Check the registered quantities and running/stopped periods.
  6. Test quality signals. If applicable, verify scrap and rework registrations.
  7. Review Good Solutions Web. Check the Timeline and relevant production information.
  8. Disable Debug. Make sure temporary debugging is switched off.

If a test fails, investigate one part of the connection chain at a time.

Key Takeaways

  • Reliable production data depends on correct configuration throughout the data collection chain.
  • Always verify the physical signal before troubleshooting higher-level settings.
  • The I/O input and Measure Point association are essential.
  • Incorrect quantity factors can cause inaccurate production, scrap, and rework figures.
  • Debug is useful for signal validation but must be disabled afterward.
  • Controlled production tests are the best way to confirm that collected data matches reality.