From 7ac01ca387bb02a0e336bcc167b740c18680e09f Mon Sep 17 00:00:00 2001 From: Brendan Haines Date: Sun, 1 Dec 2024 14:12:20 -0700 Subject: [PATCH] misc comments --- README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 029c163..5ad3a09 100644 --- a/README.md +++ b/README.md @@ -28,10 +28,14 @@ Similarly increasing resolution after streaming data causes mayhem as well: 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. +For this screenshot I also set `PixelCorrectSetMode = Raw`. It looks like the black (and maybe white too) correction data is bad. If I don't do this there are large horizontal bars of dark/light across the image. 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. \ No newline at end of file +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. + +## Cabling + +Triggering the framegrabber with a 3V3 rising edge. I want to use isolated inputs because they're there so J1 pin 13 (DB25 pin 7) with J1 pin 17 (DB25 pin 9) as GND. \ No newline at end of file