Search options (Page 50 of 129)

Hi,
Yes they are UVC compliant and you can configure and drive them in Kinovea.

Note that there are a lot of models from this vendor, with a few baseline hardware and a lot of variations on top of them for lenses.
For the high framerate you'll be looking at the ones based on OV2710 sensor (ELP-USBFHD01M).

I wrote a review of this model on my personal blog here.

In my experiments it doesn't do 120fps but 100fps, and only at lower resolution (640x480). 1280×720 @ 60 fps is nice though but there are other shortcomings.

I reproduce a problem but I'm not sure it's the same.

For me it's the video that is 29.97 fps that is further along the timecodes, not the other way around.
It is running too fast by a bit less than 1% which is the expected error from the rounding issue mentioned earlier.

The issue only occurs during playback itself, as soon as I pause and restart playback the synchronization error is reset to zero. There is no issue when using the common slider to set the common time. It also has no impact on time-dependent computations like chronometer, kinematics, etc.

I ack the problem with timer precision. I'll have to think about the proper way to fix it.

Yes it will work. It doesn't matter that you film from 10cm or 5cm. The program knows the expected geometry of the checkerboard and it compares it to what the image shows. Whether the squares occupy 25 pixels or 100 is not important for this. It is however important that all parts of the image are mapped to take into account asymmetries, so it should be from various angles.

It may appear that the distortion changes when you move the camera closer or farther away from the screen but in reality it does not. The periphery of the image still has the same amount of distortion. If you filmed a checkerboard ten times bigger from ten times farther away you would get the same image.

If you do the calibration several times you will see that the coefficients are not exactly the same. It should still work accurately and this margin of error is probably lower than the error introduced during digitization of points/objects positions.

The calibration of distortion works on the projected image so once calibrated it will work no matter how far the subject is.

Here are some notes I wrote last year regarding lens calibration. They should still be relevant I think, let me know if it works.

Summary : film checkerboard pattern, import 5 images to Agisoft, export calibration file, import calibration in Kinovea.

1. In Agisoft Lens: Tools > Show chessboard.
2. Film the screen with the camera from up close. About 10 cm for a GoPro. Film from 5 different angles: one central and the others from the corners. This assumes a flat screen. See example images below.
3. Open the video in Kinovea.
4. In Kinovea: Find 5 clear images (no motion blur) corresponding to the 5 various points of view and export them as images.
5. In Agisoft Lens: Tools > add photos. Add the 5 images.
6. In Agisoft Lens: Tools > Calibration. Check every checkbox except "skew" and "k4". Run calibration.
7. In Agisoft Lens: File > Save calibration…
8. In Kinovea: Image > Camera calibration. File > Import > Agisoft Lens. Import the file and Apply.

Done.

You can reuse the same calibration file for all videos filmed with this camera with the same lens settings. (If you change from wide angle to normal, another calibration file is needed.) Other cameras of the same model will have similar calibration files, but for the most accurate result you'll want to use a file specific to your camera.

The calibration computes the focal length, the misalignment of the lens center with regards to the sensor center, optical axis orientation with regards to the sensor plane, and distortion coefficients.

Verification

1. Go into the image tab in the calibration window and check the rectified image.

2. With a perspective plane.
- Reopen the checkerboard video in Kinovea.
- Add a perspective grid on the checkerboard and verifies that the lines are correctly distorted.
- Zoom to the max, adjust corners of the perspective grid and then calibrate the grid by the number of blocks covered horizontally and vertically.
- Display the coordinate system and check that it is correctly distorted. You can see the error accumulating at the periphery.
- Add a line covering a number of blocks, display its measurement and check that it matches.

My calibration images looked like this:

Hi,
There is usually two ways to connect to industrial cameras, through a generic DirectShow filter or through special code based on an SDK provided by the vendor.

The DirectShow interface is simple and doesn't have all the options that the camera exposes and usually doesn't provide the same performance either. The SDK is the proper way to go but requires special code and most importantly an actual camera for testing.

Unfortunately currently Kinovea only supports IDS cameras through the DirectShow filter.

Thank you.

Thanks for the logs.
I'm mostly interested in the logs for 0.8.24. There won't be any modifications on top of 0.8.15.
Fortunately, log.txt.1 is new to recent versions so it contains 0.8.24 log.

The error there is the following:
System.Exception: Environment variable PYLONC_ROOT not found. Install the pylon C Runtime.
   at PylonC.NET.Bootstrapper.Initialize()
   at PylonC.NET.Pylon..cctor()

The way it is supposed to work is: Kinovea embeds a "wrapper" library published by Basler that acts as a bridge between the program and the rest of the Pylon stuff installed on the machine. This library looks for the environment variable to know where the rest of the Pylon DLL are located.

Please check if you have such an environment variable, I imagine it should be set during Pylon installation. (Right click My Computer > Properties > Advanced system settings > Advanced > Environment variables). I will look on my machine tonight to confirm.

By thumbnails I was referring to the camera thumbnails from the camera explorer. Considering the nature of the failure I would guess there is no thumbnail at all though.