30 lines
1.5 KiB
Markdown
30 lines
1.5 KiB
Markdown
# Coaxpress High Speed Camera
|
|
|
|
## Getting Started
|
|
|
|
First issue was installing the framegrabber in a PCIEx4 slot. It seemed to work but was complaining about not having x8 so I moved it.
|
|
I'm not sure if cable order matters for the coax connections but I found an order that does and I'm sticking to it.
|
|
|
|
From here on I'm using the firmware pre-installed on the framegrabber and camera. The framegrabber indicates it needs a firmware update and I'll get to that at some point.
|
|
```
|
|
21:14:02.172 [WARNING] Device open with warnings: W: Firmware update required
|
|
```
|
|
This is the what the framegrabber reports for firmware:
|
|
![1731817045545](image/README/1731817045545.png)
|
|
|
|
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:
|
|
![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:
|
|
![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:
|
|
![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.
|
|
|