Prosilica Driver

Please ask about problems and questions regarding this tutorial on answers.ros.org. Don't forget to include in your question the link to this page, the versions of your OS & ROS, and also add appropriate tags.
Description:

Starts a PR2 Prosilica camera in polled mode. This file exists mainly for backwards compatibility. Starts a PR2 Prosilica camera in streaming mode. Select the subfolder 'driver' and replace the file AVT1394DSPCamera.inf with the same-named file from the hotfix. Hotfix for Direct Stream Package Legacy Apps. GigE Sample Viewer. Legacy viewer application for Allied Vision GigE cameras. Downloads: GigE Sample Viewer for Windows v1.26 SmartView. Legacy viewer application for Allied Vision 1394.

Allied Vision Prosilica Firewire SDK revision 1.22 Allied Vision Prosilica GigE Allied Vision GigE SampleViewer (PvAPI SDK revision 1.28). Sumix 12A2 driver. IDS, AVT/Prosilica and Basler fast cameras (external link) ASCOM drivers for IDS, AVT/Prosilica and Basler fast cameras. You can find the compatibility matrix on Genika Astro web site (button on the right). They support Binning 1 and 2, AoI and gain setting in 8 bits mode. AVT requires UNI SDK 2.1; Basler the Pylon 3.2 and IDS the uEye SDK 4.2. Prosilica provides a range of software, drivers, and software tools for use with Prosilica cameras - all free of charge. Customers can download Viewer programs to operate and configure their Prosilica cameras, download software development kits (SDK) for camera control and image acquisition.

This tutorial will show you how to determine the prosilica camera's IP address if you do not remember it.
Keywords: Prosilica, IP, camera
Ros prosilica driverTutorial Level: BEGINNER
Next Tutorial:ProsilicaConfiguring the Prosilica gigE for a desktop

Contents

Compiling

Start by getting the dependencies and compiling the driver.

Powered On and Plugged in

Make sure that your Prosilica camera is powered at 12V, connected to your computer, and the green and orange network lights are lit.

Making Sure the Network is Configured for IPv4 Networking

Before you can find a camera on the network, the network adapter to which the camera is connected must be configured for IPv4 networking. In many cases this will be done already, so try skipping to the next section of this tutorial, and come back here if the discover command can't find your camera.

Configuring a network adapter is beyond the scope of this tutorial. The following tips may allow you to get started, but may get you in trouble with your network administrator. Moreover, the setup you get by following these tips will not persist when the computer is rebooted.

Ros Prosilica Driver

To check that an adapter is configured for IPv4 networking, use the ifconfig command. For example if your camera is connected to eth0, do:

In this case, the camera has an inet6 addr, but no inet addr, so it is not configured for IPv4 networking.

Prosilica Camera Driver Ros

We can give the adapter an IPv4 address with the following command (this address probably won't get you in trouble):

Now we can check that the computer does indeed have an inet addr:

Capturing the IP address

Run:

where ethx is the interface the camera is connected to. This will be listening for traffic and return the IP address of our camera.

In another window run:

The tcpdump command will output a line similar to this one:

The address of the camera is 10.68.0.20. (Note that ListCameras will probably not see the camera.)

You can now configure the network interface (or an alias) in such a way that the camera is on the same subnet, and you can set the camera's IP address as described in the configuring the Prosilica gigE for a desktop tutorial.