Device Available with Operational Issues

This section considers issues with cabling, Ethernet switches, multiple cameras, and camera exposure. All information concerning the Teledyne DALSA Network Configuration Tool and other networking considerations, is available in the Sapera LT Getting Started Manual for GigE Vision® Cameras & 3D Sensors (pdf) and the Teledyne GigE Vision Interface User Manual & Network Optimization Guide (pdf).

Firmware Updates

Typically, any Nano-10G installation must include the firmware update procedure (see File Access Control Category). Nano-10G camera firmware that does not match a newer version of installed Sapera LT software is likely to have unpredictable behavior.

Problems might be:

  • Nano-10G is not found by the device discovery process.

  • Nano-10G is found by the Sapera GigE Server but an application such as CamExpert does not see the camera.

  • A Nano that had a fault with a firmware update will automatically recover by booting with the previous firmware version.

NOTE

New Nano cameras installed in previously deployed systems are fully backward compatible with the older vision application.

Power Failure during a Firmware Update–Now What?

Don’t panic! There is far greater chance that the host computer OS is damaged during a power failure than any permanent problems with the Nano. When electrical power returns and the host computer system has started, follow this procedure.

  • Connect power to the Nano. The Nano-10G processor knows that the firmware update failed.

  • The Genie Nano-10G will boot with the previous version of firmware and will operate normally.

  • The Self Status (deviceBISTStatus) will return that the last firmware update failed.

  • Perform the firmware update procedure again (see Updating Firmware via File Access in CamExpert).

Cabling and Communication Issues

With only two cables connected to Nano, possible cabling issues are limited.

Power supply problems

  • If the Nano-10G status LED is off, the DC power supply is not connected or faulty. Verify the power supply voltage.

Communication Problems

  • Use a shielded cable where the connector shell electrically connects the Nano-10G chassis to the power supply earth ground. This can eliminate trigger issues in a high EMI environment.

  • Check that the Ethernet cable is clipped both to the Nano-10G and the NIC or switch on the other end.

  • Verify the Ethernet cabling. Poor cables will cause connections to auto-configure at lower speeds. 

  • Use a secured Ethernet cable when the Nano-10G is in a high vibration environment. See Ruggedized RJ45 Ethernet Cables.

  • Check the Ethernet status LEDs on the NIC used with the camera. The Link Status indicator is on, and the activity LED should flash with network messages.

  • Verify that the Ethernet cable is CAT6. This is very important with long cable lengths.

  • When using very long cables, up to the maximum specified length of 100 m for gigabit Ethernet, different NIC hardware and EMI conditions can affect the quality of transmission.

  • Minimum recommended Ethernet cable length is 3 feet (1 meter).

  • Use the Teledyne Log Viewer to check on packet resend conditions: open Sapera Log Viewer, then start the Nano-10G acquisition program, such as CamExpert. There should not be any “packet resend” messages, else this indicates a control or video transmission problem due to poor connections or extremely high EMI environments. 

Acquisition Error Without Timeout Messages

Streaming video problems range from total loss of image data to occasional loss of random video data packets. The following section describes conditions identified by Teledyne DALSA engineering while working with Nano-10G in various computers and setups. See the Teledyne GigE Vision Interface User Manual & Network Optimization Guide (pdf) for information on network optimizations.

Grab Has Random Bad Data or Noise

The problem is seen as random noise and missing sections of video data from the acquisition. All configuration parameters seem correct, and the Ethernet cable is secure. The following image shows an example of this type of bad acquisition while testing a Genie installation with CamExpert.

C:\Users\spisan\Documents\work tmp4 Genie Nova\pics\corrupted grab.png

  • This problem has been seen with network adapters that do not support jumbo frames but still report a false maximum packet frame size.

  • Test for a good acquisition by reducing the camera packet size used. Set the value to the default value of 1500 to verify acquisition before trying a higher value.

  • Other marginal NIC boards or ports can cause problems with packet transfers. Try alternative NIC adapters.

No Camera Exposure when Expected

  • Verify by using the camera in free-running mode. Do not use external trigger mode when testing a camera setup.

  • If using free-running mode, verify that the exposure period is set to the maximum possible for the set frame rate.

  • Load the factory default from the Power-up Configuration Dialog in CamExpert. This will reset the camera to its nominal acquisition rate.

Camera Acquisition Is Good, but Frame Rate Is Lower than Expected

  • While running CamExpert and grabbing in free run mode, check the GigE Vision Transport Layer Control to verify and possibly increase the Interpacket Delay. In multi-camera setups using a Gigabit Ethernet switch, the Device Link Throughput may need to be reduced so that each camera can equally share the available bandwidth.

  • While running CamExpert and grabbing in free-run mode at the maximum frame rate, start the Sapera Monitor tool from the Sapera Tools installed with Sapera.

  • Make sure the Overflow event monitor is enabled.

  • Continue grabbing from the Nano-10G at maximum frame rate. If any memory overflow events are counted, then the Nano-10G internal buffer could not be transmitted on time and was discarded. Such a condition may occur with large frame color or high frame rate Nano-10G cameras.

  • Note that the Sapera CamExpert tool has limits to the maximum frame rate possible due to CamExpert generating an interrupt for each acquired frame. The Sapera Grab Demo may be better suited for testing at higher frame rates.

  • Verify that network parameters are optimal as described in the Teledyne GigE Vision Interface User Manual & Network Optimization Guide (pdf). Ensure the host computer is not executing other network intensive tasks. Try a different Gigabit NIC.

  • Note that a changed acquisition frame rate becomes active only when the acquisition is stopped and then restarted.

  • If using an external trigger, verify the trigger source rate and Nano-10G parameters such as trigger to exposure delay.

  • USB-to-Ethernet adapters are not recommended nor guaranteed. Even in cases where the camera seems to be connected and transferring images, reports of random disconnections are common. If the user wishes to try such an interface, limit this to just one high quality unit, never more. Multiple units have not worked in a machine vision environment.

Camera Is Functional, Frame Rate Is as Expected, but Image Is Black

  • Verify that the lens iris is open.

  • Aim the Nano-10G at a bright light source.

  • Check that the programmed exposure duration is not too short or set it to maximum.
    See Sensor Control Category.

  • Using CamExpert, set the Nano-10G to output its internal test pattern generator. This step is typically done for any camera installation to quickly verify the Nano-10G and its software package. See Internal Test Pattern Generator for information on using CamExpert to select internal patterns from Nano.

Intel X550 T2 NIC: Low Connection Speed After Camera Reset

When connected directly to the Intel X550 T2 NIC (not through a switch), following a camera reset and subsequent link speed negotiation, the GigE link speed is set to 1 GigE instead of higher speeds (10, 5 or 2.5 GigE).

To correct the problem, connect to the Intel X550 T2 through a 5G capable switch, or replace the NIC with a different model, such as the ASUS XG-C100C, which does not exhibit this behavior.