Synview Explorer

	SynView is a NET-created development environment based on GenICam/GenTL standards. It contains a high-performance and user-friendly API to make it easier to create applications. Application engineers can concentrate fully on developing your solution. More information can be found under the following link.
	The SynView package contains the SynView Explorer tool, which allows to enumerate, connect and configure camera, acquire images or generate sample source code for SynView API. It is a useful tool for testing both the SynView and camera functionality.

SynView is preinstalled on the camera under the location /opt/synview/bin/

To learn more how to use Synview explorer we refer to the Synview Explorer manual.

Testing the camera

Capture an image or test new camera settings with Synview Explorer. There are two ways:

Using the iAMGigEServer with iam and receiving the image data with Synview Explorer on a host system. iam acts like a normal GigE Vision camera.
Native: Using the OpenSSH connection with -server forwarding. From the commandline it is possible to start the sv.explorer bye the command below.

Since the iAMGigEServer is executed via autostart, stop iAMGigEServer before using Synview Explorer native on camera (option 2). See section iAMGigEServer

The latest version of Synview Explorer is required for iam. For this, update the host system. Download link is at the end of section Download latest Synview Prerelease .

ssh -Y root@192.168.1.10 "/opt/synview/bin/sv.explorer"

	Connect the camera to be tested. Select it in the list of found cameras and press the Connect camera button.
	Configure the camera features. Pay attention especially to features in Image Format Control and Acquisition Control categories.
	When prepared, click the Start acquisition button. The camera should start acquiring. If not, verify again, if the camera was not set to triggered mode, while no trigger was attached.
	While the acquisition is active, the runtime parameters can be adjusted, such as exposure time or gain. Basic acquisition parameters, such as pixel format or trigger mode get locked when the acquisition starts.
	When finished, click the Stop acquisition button and exit.

It is an common source of error to operate a monochrom sensor in the color space. In case of a monochrome sensor change the Pixel Format to Mono 8 .

Live view performance

From the line just above the live image, the frames count per second on the iam camera system is visible. Displaying the images remote over an OpenSSH connection will impair the performace very much and will add some delay as well. In the example below, the sensor runs with 147 frames per second and 1.8 frames per second if displayed remotely.

See what your camera model can achieve by looking up the maximum frame rate at Camera Model Overview table.

An OpenSSH session using live imaging has a poor performance but can help to change camera parameters or test new features.

Please be aware of the low frame refresh rate with this type of connection. A better refresh rate will be achieved with the "GigE Vision server of Synview" in the future.

Basic camera features

This section shows the most essential camera features relevant for the basic tests.

The SynView Explorer displays by default only the “basic” camera features intended to handle the most common tasks. To display also the more advanced features, switch to the “expert” feature level. Note that the third available level, “guru”, is intended just for debugging and should not be used for normal operation.

feature category	feature name
Image format The basic properties of the acquired image can be configured through features in the Image Format category.	Pixel format The Pixel Format feature is an enumeration allowing to specify the type of image data delivered to the application buffer. The available pixel formats differ among camera models. In general, they can be - Monochrome, with various number of bits per pixel, eg. Mono 8 or Mono 12. - Bayer encoded, with sensor-dependent Bayer formats, eg. Bayer GR 8 or Bayer BG 8. In this case the application needs to decode the Bayer encoded image buffer to get a proper color image — SynView API provides functions for this. - RGB color format, providing true RGB output, in this case the Bayer decoding is performed directly by the camera. Image size The camera will acquire full size image by default. The acquired image size can be reduced using the Width and Height features, which set the acquired image size in pixels. The field of view will be automatically centered within the full sensor image.
Acquisition parameters The luminance of the acquired image can be controlled either explicitly through exposure time and gain functions, or automatically through corresponding auto-functions.	Exposure time The Exposure Time feature in Acquisition Control category configures the length of the exposure in microseconds. Analog gain Analog gain to be applied on the sensor during acquired image digitization can be configured through corresponding features in Analog Control category. Verify that the Gain Selector feature is set to Analog (some cameras models support also digital gain). Now the Gain feature controls the desired analog gain value in decibel. Auto-functions Selected camera models support automatic gain and/or automatic exposure functions, when the camera keeps adjusting given parameter automatically, to maintain constant image luminance. The features will be displayed in the feature tree only if the camera supports them. To switch the auto function on, navigate to corresponding control feature, Automatic Exposure in Acquisition Control category or Automatic Gain in Analog Control category and switch them from Off to Continuous.
Triggered acquisition The camera starts by default in “free running” mode — acquiring continuous stream of image frames. On the other hand in the triggered mode, the acquisition of individual frames can be explicitly controlled by hardware or software triggers. The trigger related features are located in the Acquisition Control category.	Triggered mode To switch the camera to triggered mode, open the Trigger Selector subtree and set Trigger Mode to On. After starting the acquisition again, the camera will acquire images only when explicit trigger signal arrives. Trigger source The Trigger Source enumeration allows to select where should the camera “listen for triggers”. You can select either Software or one of the camera's I/O lines. The assignment of the I/O lines to the connector pins is described in Section, Connector and cable description. Software triggering The software triggers can be issued during active acquisition in triggered mode, regardless whether the trigger source is set to Software or a physical I/O line. To apply the software trigger, select the Generate Software Trigger feature and click the button in the tool bar. Strobe The strobe can be configured using features in the Digital I/O Control category, after switching the feature visibility level to “expert”. Select the desired output line, where the strobe pulses should be applied through Line Selector (the I/O line mapping to interface connector pins is described in Section, Connector and cable description). Switch the strobe on for the selected line by setting Line Source to Exposure Active. The camera will issue a strobe pulse aligned with the exposure for every acquired frame. The strobe output is available only in triggered mode. In case the camera has an integrated Strobe Ring, its Strobe can be controlled through the Strobe Control category. Select which Clusters to use with Strobe Enable. Strobe Duration sets the length of the Strobe Pulse.
Device Control Information about the camera. It is frequently necessary to query the basic information about the camera. The information is available through features in the Device Control category.	Device identity The most important features identifying the camera are Vendor Name and Model Name. The camera's serial number is stored as string in feature Device ID (available only in “expert” feature level). Finally, the “nick-name” used to identify the device is accessible (read/write) in DeviceUser ID. Firmware version The version of the firmware loaded on the camera is accessible as string in feature Device Firmware Version.