Troubleshoot delayed counts in L2L Connect caused by network interruptions

Last updated: November 19, 2026

Use this guide when a Connect asset appears to miss counts, but the real problem may be network connectivity rather than the count logic itself.

Symptoms

You may see one or more of these symptoms:

  • Counts arrive late in Connect

  • A machine appears to have gaps in count data

  • The asset or gateway shows offline events

  • The issue affects more than one device at the same time

What to check first

1. Review device and gateway history

In L2L Connect, open the affected asset or gateway and review its history for offline, timeout, or reconnect events.

Look for patterns such as:

  • repeated offline/online cycles

  • timeout errors

  • multiple devices dropping at the same times

2. Compare the affected asset with another connection

If you have both:

  • a Wi-Fi asset, and

  • a wired gateway or another nearby device

compare their outage windows.

If both devices lose connection at the same time

This usually points to a site or plant network/uplink problem, not a problem with one specific device.

Recommended next step:

  • ask local IT to investigate the plant internet connection, DNS, firewall, and upstream network equipment

If only one Wi-Fi asset drops while a wired device stays online

This usually points to a local Wi-Fi coverage or access point problem near that machine.

Recommended next step:

  • ask local IT to inspect the nearby access point

  • verify signal strength and AP health

  • check for power or cabling issues on the AP

  • move the device to a stronger access point if possible

  • use a wired connection if that is an option

Why counts can look wrong during network issues

When a Connect device loses network access, data may not reach Connect in real time. That can make counts appear delayed or inconsistent until connectivity is restored.

Because of this, it is best to rule out connectivity problems before changing PLC counter logic or count mappings.

Recommended troubleshooting order

  1. Confirm whether the device was offline during the missing-count window.

  2. Compare the timing against other nearby devices or gateways.

  3. Determine whether the problem is plant-wide or isolated to one asset.

  4. Work with local IT to fix the network issue.

  5. After connectivity is stable, re-check whether the count problem still exists.

When to escalate to L2L

Escalate to L2L Support after network stability has been verified and the asset is staying online, but counts are still missing or incorrect.

Include:

  • the asset name

  • approximate timestamps of the issue

  • whether the device is wired or Wi-Fi

  • screenshots or exports of offline/history events

  • whether nearby devices were affected at the same time