From 8d8088641c97785cef9f73ccb4f72bbcd51d5fa7 Mon Sep 17 00:00:00 2001 From: Brendan Haines Date: Fri, 22 Nov 2024 21:32:47 -0700 Subject: [PATCH] fix newlines --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 6be67e9..029c163 100644 --- a/README.md +++ b/README.md @@ -9,23 +9,23 @@ From here on I'm using the firmware pre-installed on the framegrabber and camera ``` 21:14:02.172 [WARNING] Device open with warnings: W: Firmware update required ``` -This is the what the framegrabber reports for firmware: +This is the what the framegrabber reports for firmware: ![1731817045545](image/README/1731817045545.png) -And for the camera: +And for the camera: ![1731817117549](image/README/1731817117549.png) -It looks like order of operations is very important in Vision Point. This camera comes up as 1608x400 pixels at 500fps: +It looks like order of operations is very important in Vision Point. This camera comes up as 1608x400 pixels at 500fps: ![1731817401898](image/README/1731817401898.png) -If I stream data and then decrease the resolution to increase frame rate, the preview goes crazy and I just get a bunch of garbage: +If I stream data and then decrease the resolution to increase frame rate, the preview goes crazy and I just get a bunch of garbage: ![1731817483859](image/README/1731817483859.png) This looks to me like desyncronization of the camera and framegrabber. -Similarly increasing resolution after streaming data causes mayhem as well: +Similarly increasing resolution after streaming data causes mayhem as well: ![1731817591941](image/README/1731817591941.png) -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. +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.