Video_EXposure_Analyzer V E X A 2.0 |
Seite in Deutsch | Frameless version of this page |
The current version VEXA 2.0 was developed in the year 2007 from previous version 1.0. The first version VEXA 1.0 was developed 2006 primary for video mode only. But in version 2.0 two additional modes, the pulse mode and the running light mode, were implemented. Therefor only little circuit changes were necessary. The two additional functions were implemented by a new software mainly. So it is relative simple to upgrade a VEXA 1.0 to a VEXA 2.0.
Function comparison of the versions | ||
Mode | VEXA 1.0 | VEXA 2.0 |
Video mode | Yes | Yes |
Pulse mode | No | Yes |
Running light mode | No | Yes |
Upgrade from VEXA 1.0 to VEXA 2.0 | ||
Mode | Software | Hardware |
Video mode | No change | No change |
Pulse mode | Change | Change |
Running light mode | Change | No change |
Hardware upgrade suggestion for the use of pulse mode:
Here is a simple suggestion about a hardware modification to upgrade a VEXA 1.0 to version 2.0. For the use of the new pulse mode it is necessary to have an additional input for the 1PPS signal. In VEXA 2.0 this input is pin 9 of the microcontroller. But in VEXA 1.0 the pin 9 of the microcontroller is connected to ground via the Printed Circuit Board.
Pin 9 of the uC is also used during reprograming. So after the uC was reflashed with new VEXA 2.0 software the pin 9 of the uC can be bended horizontal. Soldering a 4k7 resistor and a piece of wire on pin 9 is all what have to be done. A second wire for ground potential connection to the 1PPS device is also needed. The ground potential is available on several points of the VEXA 1.0 PCB. Contact 9 from the IC socket naturally also has ground potential. But be sure that this two wires are fixed against movement otherwise the pin 9 of uC would break off very soon.
Here you can see the modification on Pin 9 of the microcontroller with resistor and wire.
Ground potential can be used from Pin 9 of IC socket of the microcontroller.
The result is a VEXA 1.0 upgraded to a VEXA 2.0.
Link to previous version VEXA 1.0
Contents of this VEXA 2.0 page and some links
Note: Download and use of this information and files is free, but on your own risk and only allowed for uncommercial use. Copyrights are hold by the author of this site. It is possible that files and their contents are modified from time to time.
FAQ - Frequently Asked Questions
VEXA video mode - detailed functional description
Signal measurements on a VEXA prototype
VEXA measurements in video mode - CCIR video modul SK1004XC/SO
VEXA measurements in video mode - CCIR video camera WAT-120N
Download of VEXA 2.0 description of function and hardware (PDF-470kB)
Download of VEXA 2.0 software as Intel Hex and binary file (ZIP-3kB)
Thanks to and copyright advices
1.) What does VEXA mean? VEXA is an abbreviation of Video_EXposure Analyzer. VEXA consists of free available hardware components and of by me programed software for functions control.
2.) What can be done with VEXA?
3.) Which cameras can be tested and measured with VEXA?
4.) Is it possible to test also video cameras in integration mode with VEXA?
5.) Is it possible to test also USB-cameras or Fire-Wire cameras?
6.) How are measurements taken with VEXA?
7.) Is it possible to make a direct check of Video Time Inserter (VTI) accuracy with VEXA?
8.) Can I order VEXA as a ready device or as a kit?
9.) How much are the costs of material for self-constructing a VEXA?
10.) Which power supply is needed for VEXA? |
VEXA video mode
Overview:
VEXA is using a row of 10 synchronised and switched LEDs to show the position and duration of the optical exposure window in the video fields. To measure exposure time one has only to record the 10 LEDs of VEXA with the camera in test. The ideal distance will depend on used camera-lenses. You should vary the brightness of the environment in the field of camera view to see how the camera change exposure time window.
For exactly measurements 32 modes can be selected with a DIP-switch. Read the file from the download section about VEXA 2.0 Description (PDF-470kB) carefully and you will grasp how to use different modes for exact measurements.
With a potentiometer the LED brightness can be adjusted over a wide range. CCD or CMOS cameras are able to record the glow of red Leds although they seem to appear dark to the human eye. So on the other side to much LED brightness will outshine the 10 single positions of lit LEDs.
VEXA needs a power supply in the range of 7 - 15 Volt DC and 30mA for working. You need a right AC/DC power supply adapter. With a new 9 volt battery an operation of 3 - 4 hours also should be possible. Connect the camera output with VEXA Video Input and to record or see exposure and regulation of exposure in realtime you have to connect VEXA Video Output to a monitor, a Videorecorder or a Videograbber useing a PC or Notebook for recording or monitoring.
VEXA is using the extracted Vsync impulses from the analog video signal to synchronise the internal starts of the LED row runs. After a start always only one single LED (01 - 10) after another is lit. The delay between Vsync and start of LED 01 and the time steps between the single lit LEDs are controlled by selected mode (00-31). VEXA can also distinguish the odd and even fields of PAL or NTSC video signals. So one can choose a LED row run only in odd, only in even or in both fields.
Example - idealised timing:
In our example we assume the exposure automatic of our camera exposures a duration of 12ms every field. The starting point is 8ms after the Vsync. The exposure window is lasting to the end of the video field at 20ms. If we would darken the field of view of our camera the automatic would start exposure window some milliseconds earlier than in our example.
What will we see in our example on a recorded PAL video sequence or on a monitor showing the live video of recorded LEDs? No exposure was done during lit of LED 01, 02, 03 and 04. So LED 01 to LED 04 are dark (0-8ms) and LED 05 to LED 10 (8ms - 20ms) are lit during exposure window and are shining bright in recorded video or on a monitor. We are able to determine the lasting (6 x 2ms = 12ms) and additionally the exact position of exposure in every video field. See the image below with idealised video timing for graphical description of this results.
Example - real timing:
How can we see such an offset time between the camera video field signal output (Vsync) and the internal exposure sequence using VEXA? A real value for this offset time is less than one millisecond. Lets take a look at the following image about real timing assuming an offset time of one millisecond. Remember, we are runing VEXA in Mode 00. So LED 01 is lit immediately after Vsync for 2 ms. Due to the offset at this time point the internal exposure window has not finished and is still going on for about another 1 ms.
What will we see on records or on a monitor showing the video of recorded LEDs? LED 01 in half brightness because it is captured only for 1 ms at the end of exposure field, no exposure was done during lit of LEDs 02, 03 and 04 so they look as complete dark, LED 05 is captured only for 1 ms at the start of exposure field and shine in half brightness like LED 01 does. Only the LEDs 06, 07, 08, 09 and 10 are captured each for 2ms and so are full lit. If we add all the lit times 1ms + 5 x 2ms + 1ms we get again the right exposure duration of 12ms.
Now we can use other VEXA-modes to determine this results with a higher resolution in time. The only thing we have to consider is, if LED 01 is lit also on short exposure times, an internal time offset between the camera video field signal output (Vsync) and the internal exposure field exists. And in this case LED 01 shows us the End of the exposure window and not the Start. The existing and the values of offset times are different and depends always on video camera or modul types.
Additional Note for use of NTSC cameras:
Now, after reading all this theoretical descriptions you should additionally take a look on the images of real Vexa-measurements accomplished with my CCIR video module SK1004XC/SO and video camera WAT-120N.
VEXA measurements in video mode - CCIR video modul SK1004XC/SO
VEXA measurements in video mode - CCIR video camera WAT-120N
This measurements of internal signals on a Vexa prototype are only for additional technical information. This images and the knowledge about are not needed for building and use of a Video EXposure Analyzer - VEXA.
functional description
VEXA is a simple microcontroller-circuit for showing and testing the exposure duration of a video camera or a video modul. VEXA is a tool to show the beginning and the end of optical exposure within every single video field. This tool was designed to test cameras with an exposure duration of a field or shorter. Modern cameras are able to vary exposure time-window from as long as all the field time (PAL=20.00000ms, NTSC=16.68335ms) to the shortest time in the range of only about 10 microseconds. The exposure window mostly starts at a variable timepoint in a field lasting to the end of the field. But some video modules are starting exposure time on a fixed timepoint and then variegate the exposure end in the field.
Video EXposure Analyzer - VEXA
(functional diagram)
We are using a PAL camera with 20ms video field duration and VEXA runing in Mode 00. Vexa waits on Vsync impuls and starts LED row immediately with LED 01. In Mode 00 every LED from 01 to 10 is lit one after another for exactly 2 ms. After 20ms all ten LEDs had lit each for 2 ms and now the next video field will start with the next Vsync impuls. The same cycle starts again and so on.
Note: The maximum exposure time in a single video field is nearly 20ms for a PAL video camera and would be nearly 16.68ms for a NTSC video camera.
Example video timing - idealised
Live video image of all 10 Vexa-LEDs on a monitor
And now the same example as before but with real camera timing. The exposure duration is the same (12ms) as in our example before. But in reality there mostly is an offset time between the camera video field signal output (Vsync) and the internal exposure sequence. This little offset was detected by Geoff Hitchcox on some of my earlier measurements on video modul SK-1004XC using my KIWI-OSD with 1PPS LED and an oscilloscope. And this was the reason for me to start developing a device like VEXA to be able to measure the exact exposure behaviour of video cameras and video modules.
Example video timing - real
Live video image of all 10 Vexa-LEDs on a monitor
A LED row run always ends at the latest on the next Vsync impulse or earlier after the 10 LED lit-times are over depending on the selected mode. The maximum selectable run time is Mode00 with 10 x 2ms = 20ms. This is the full time of a PAL field. But if you use a NTSC camera in this mode you will see that the LED run ends at LED 09 due to the next Vsync after 16.68335ms. So with signal from a NTSC camera LED 10 will never be lit in this mode.
Signal measurements on VEXA prototype
Time delay Vsync and Even/Odd signal
Starting time of LED 01
Time delay between Even/Odd signal (Pin7) and Vsync (Pin3) of LM1881 |
The delay between Vsync and signal "Odd field start" is 2 us.
|
Light of LED 01 never starts earlier than 9us after Vsync |
LED 01 in Modes 00, 03, 08, 14, 21 and 31 |
Many thanks to:
Many thanks to Geoff Hitchcox and to Dave Gault (Australia) for assembling the first "external" VEXAs and performing very useful measurements. Additionally many thanks to Geoff Hitchcox for good ideas in VEXA circuit design.
In the meantime after VEXA was used in Austria, New Zealand and Australia it was also used in California by astronomers. Many thanks to all of them and especially for sharing the measurement results about their video camera.
Copyright notes:
Geoff Hitchcox (New Zealand), the developer of Video time inserter KIWI-OSD,
used some VEXA measurements for A detailed look at KIWI OSD video timestamps.
Download and use of this informations and files is free, but on your own risk and only allowed for uncommercial use.
Copyrights are hold by the developer of VEXA and author of this site - Gerhard Dangl.
Top of page
September 07, 2008 |
Questions and suggestions to => Gerhard Dangl |
Site Home |