Range XL-GL Drops Frames or Fails to Receive Complete Data During Acquisition

You are currently viewing the documentation for a pre-release version (2.7.0). To access documentation for other versions, click the "Switch Version" button located in the upper-right corner of the page.

■ If you're unsure about the version of the product you are using, please contact Mech-Mind Technical Support for assistance.

Symptom

When acquiring data with Range XL-GL, you may frequently lose frames or fail to receive all the data.

Possible Causes

  • The network link does not provide Gigabit Ethernet.

  • Jumbo frames are not enabled on the computer’s network port.

  • The computer’s network adapter does not provide sufficient receive performance.

Solution

The procedures in this section that require operations on the computer apply only to Windows. If you use Ubuntu, contact Technical Support.

Follow these steps to troubleshoot the issue:

  1. Check whether the network link between Range XL-GL and the computer provides Gigabit Ethernet.

    • If not, replace the switch, router, network adapter, or cable with one that supports Gigabit Ethernet. Connect Range XL-GL directly to the computer if possible. Then check whether the issue persists.

      • If the issue is resolved, troubleshooting is complete.

      • If the issue persists, go to Step 2.

    • If it does, go to Step 2.

  2. Check whether jumbo frames are enabled on the computer’s network port connected to Range XL-GL. For details, see Enable Jumbo Frames.

    • If not, enable jumbo frames and check whether the issue persists.

      • If the issue is resolved, troubleshooting is complete.

      • If the issue persists, go to Step 3.

    • If they are enabled, go to Step 3.

  3. Check whether the computer’s network adapter can receive data at the required rate and has sufficient bandwidth.

    • If it does not, replace the network adapter. If you need to add a network port, use a native PCIe network adapter where possible. Then check whether the issue persists.

      • If the issue is resolved, troubleshooting is complete.

      • If the issue persists, go to Step 4.

    • If it does, go to Step 4.

  4. If a longer acquisition time is acceptable, increase the packet delay parameter GevSCPD through the Mech-Eye API. Start at 10 μs and adjust it gradually based on acquisition stability and time. Then check whether the issue persists.

    scanner.currentUserSet().setIntValue("GevSCPD", 10000); // 10000 ns = 10 μs
    GevSCPD can currently be set only through the API. Set it before starting acquisition. If the longer acquisition time affects the production cycle, improve the network environment first, for example by replacing the network adapter or optimizing the network connection.
    • If the issue is resolved, troubleshooting is complete.

    • If the issue persists, contact Technical Support.

The following issues may have the same cause. If you encounter any of them, check whether they are also resolved after troubleshooting the issue in this section.

Is this page helpful?

You can give a feedback in any of the following ways:

We Value Your Privacy

We use cookies to provide you with the best possible experience on our website. By continuing to use the site, you acknowledge that you agree to the use of cookies. If you decline, a single cookie will be used to ensure you're not tracked or remembered when you visit this website.