FAQ

BitFlow offers cameras files for almost all of the current Camera Link and CoaXPress cameras that are on the market. In addition to this, you can have camera files for various options that the cameras offer, things like triggers (HW and SW), free running, different ROI to what the sensor offers etc.  In the part we have offered camera files for Analog and Differential cameras.  These files are still available today.

The table here shows which camera files are associated with with frame grabbers

When you download the SDK the camera files will be stored on your hard drive in the following folder
C:\BitFlow SDK 6.30\Config\FRAME GRABBER TYPE FILE\FILES
The naming convention is as follows
Manufacturer-Model-Resolution-BitTap-Mode.EXTENSION

Where:
Manufacturer – Camera maker
Model – Camera model
Resolution – Size of acquired image
BitTap – Bitdepth (E = 8 bits, T = 10 bits, W = 12 bits, F = 14 bits, S = 16 bits) and Number of taps (2 – 10)
Mode – Triggered and/or encoder mode

An example would be the following
Hitachi-KP-FM400WCL-E8-TTLTrigger.r64

BitFlow currently makes Frame Grabbers for acquiring  data from cameras with the following interfaces

• Camera Link
• CoaXPress
• Differential (LVDS/RS-422)

Each CoaXPress board has one Tri LED per link. Tri LED1 refers to VFG0, Tri LED2 refers to VFG1 etc. Typically all boards flash together if one camera is connected.

Note the following color/flash rate meanings

Blinking Red – Problem with the PCIe interface
Blinking Blue – Looking for a link to see if it needs power
Solid Blue – Link is powered, but not aligned
Blinking Green – Link is aligned and receiving packets
Solid Green – Link is aligned

For the Aon, Cyton (2 and 4) – DIN 1.0/2.3
For the Claxon – Micro BNC

CXP has several different speeds (data rates) and these determine the length of cable required.

For CXP1 or CXP 2.5 or CXP3, the max cable length is 105m
For CXP6 or CXP12, the max cable length is 40m