update README

This commit is contained in:
Brendan Haines 2024-11-22 21:31:55 -07:00
parent 327837492b
commit c90a3ce995
2 changed files with 9 additions and 1 deletions

View File

@ -25,5 +25,13 @@ This looks to me like desyncronization of the camera and framegrabber.
Similarly increasing resolution after streaming data causes mayhem as well:
![1731817591941](image/README/1731817591941.png)
If I instead change the resolution to 640x200 (which based on the label I think should give me 8000fps) as the very first thing after connecting, then I do see an increase in frame rate to 1000fps. This isn't the 8000 I expect but indicates that this is the right way to do this.
If I instead change the resolution to 1696x1710 immediately after power cycle and starting Vision Point (before streaming any data) then I get full resolution at nearly 500fps.
![1732166650577](image/README/1732166650577.png)
For this screenshot I also set `PixelCorrectSetMode = Raw`. It looks like the black (and maybe white too) correction data is bad.
It is also interesting to note that there is a focus gradient vertically across the image. This makes sense since the sensor is physically slanted in the camera housing. I'm really not sure why they did this.
If I set resolution to 640x200 (which based on the label I think should give me 8000fps) as the very first thing after connecting, then I do see an increase in frame rate to 1000fps. This isn't the 8000 I expect but indicates that frame rate should adjust automatically with resolution.
I'm now updating the firmware on the framegrabber from 4.9 to 4.11. The changelog indicates that "the FPS indicator is stable" as a change in 4.11 so maybe some of the FPS numbers I've been seeing so far are wrong.

Binary file not shown.

After

Width:  |  Height:  |  Size: 701 KiB