For more information, visit iniVation support
This user guide covers the DVS128 camera:
For specifications see the specifications page
This information applies to DVS128 and DVS128_PAER, but not to the eDVS, which has an M12x0.5mm lens). The lens mount shown above for the integrated lens mount in the DVS128 camera and the DVS128_PAER is designed for CS mount lenses. If you have a C-mount lens (which can be identified from a marking on the lens), you need to use the C to CS converter adapter ring (normally supplied with the device) that moves the lens further from the chip. The chip requires lens designed for 1/2 inch imagers (die size is 6.0x6.3mm and active area is 5.12×5.12mm. In any case, the field of view is larger than that of common 1/3 inch imagers for which many lens are sold.
The field of view (FOV) depends on the focal length L of the lens and the size W of the pixel array. The angular FOV (AFOV) is given by:
The linear FOV (LFOV) at a distance D from the lens is given simply by similar triangles:
The pixel array measures 128 pixels x 40 um/pixel = 5.12 mm.
The following table shows the horizontal and vertical field of view in degrees and its size at various distances for different common focal lengths.
|Lens focal length (mm)||AFOV horizontal or vertical (deg)||AFOV diagonal (deg)||LFOV (cm)|
|dist. 10 cm||dist. 30 cm||dist. 100 cm|
You need to load a set of biases. The jAER user guide explains how to do this, in the section on “biasing”. In order to get the best performance out of your device for your application, in terms of speed, noise etc, you need to adjust the biases. The biasing guide explains how to do this.
For the DVS128, You can find the standard bias sets under:
The default biases DVS128Slow.xml or DVS128Fast.xml are suitable for many situations.
By choosing the AEChip DVS128StereoPair as shown below, you can plug in two DVS128 by separate USB interfaces and they will be treated as a stereo pair. Recording, playback, control of biases, common filtering, etc are applied to the resulting stereo stream.
The events are internally represented as objects of type BinocularEvent.
Look for usages of this class for examples.
The rendering of stereo recordings uses the convention red=Right, green=Left. (remember “red right”). However this choice is arbitrary. The assignment of left / right is made by lexicographic comparison of the serial number strings. (This assignment is likely to be changed without notice.)
Internally, the raw stereo addresses presently use bit 15 to mark the right eye, i.e. 1=right, 0=left. However this assignment is also likely to change without notice.
The hardware interface class for the stereo pair allows the optional ordering of incoming events so that time increases monotonically. This sorting has significant cost in computation and latency. See usages of the class StereoHardwareInterface for examples of the use of the setIgnoreTimestampNonmonotincity() flag. This option is controlled by the File/Check for non-monotonic time in input streams option, as shown below:
The DVS128 firmware (CypressFX2 software and CPLD configuration) can be updated easily (although firmware updates always have some element of risk).
firmware updates were previously broken when running jAER using the standard JRE. Make sure you have updated your working copy before attempting firmware update!
Firmware updates have only been tested with a single DVS128 plugged in.
You can check which firmware version you have and then optionally update. Do this by using the USB menu (with the DVS128 plugged in):
Updating firmware always has an element of risk and if something goes wrong you may need to return the camera for a new EEPROM. If you elect to update, you should see a progress bar followed by success:
A close-up photo of the DVS128 sensor is shown below. On the back, the upper LED, is a blinking “heartbeat” LED, which shows that the camera’s controller is running. The lower LED, is on as long as the DVS128 is time-stamp master; it turns off if the DVS128 is clocked externally - see the synchronisation guide.
This chapter covers DVS128_PAER devices:
The DVS128_PAER is a bare-board camera that offers parallel AER connectors for direct interfacing of the DVS sensor to other AER systems, supporting two connector standards (Rome and CAVIAR). It has a full-speed USB2.0 controller that allows configuration of the camera biases and sniffing of AER data up to 100keps. However, the USB function is only intended to monitor the camera output because the USB interface is designed to passively monitor (“sniff”) the AER bus without affecting communication with other hardware.
The DVS128_PAER uses a Silicon Laboratories C8051F320 microcontroller. On the host side, the same USB driver that communicates with the DVS128 is also used to communicate with the DVS128_PAER. However the DVS128_PAER USB communication bandwidth is much more limited (to a maximum of about 100k EPS) and the main use of the jAER USB interface is for sensor bias setting and “sniffing” the events sent on the AER bus to another device.
Specifications for this and other DVS models can be seen on the specifications document.
The DVS128_PAER board can be biased and monitored using JAER in just the same way as with the DVS128. Information about optics is also equivalent. Therefore, please refer to the Optics part of DVS128 user guide for optics, the jAER user guide for software, and the biasing guide for how to bias the device in order to get the best performance out of your device for your application, in terms of speed, noise etc.
To use the DVS128_PAER in jAER, use the AEChip DVS128, and load the biases biasgenSettings/DVS128/DVS128_PAER.xml. Make sure that the REQ/ACK jumper is shorted (see below).
There are two LEDs, L1 and L2 at the top center of the PCB:
There are also two important jumpers:
USB_PS/EXT_PS: (left of the tmpdiff128 DVS sensor) This jumper powers the board from USB VBUS (5V) power or from the external power supply.
REQ/ACK: (top right of the tmpdiff128 DVS sensor) This jumper connects the AER request and acknowledge signals so that the DVS chip handshakes with itself. If this jumper is left unconnected, no data will appear in jAER. Disconnect the jumper if the DVS chip is handshaking with a receiver device.
The AER header pins are documented in AERHardwareAndCabling.pdf. The 20 pin header uses the so-called Rome standard, and the 40-pin IDE header uses the CAVIAR standard.