General questions about BitFlow.
The Axion can capture all defined Camera Link configurations. You can do specify this directly in the BFML file, or using our BFML file editor CamML.
The Axion’s Camera Link tap re-formatter is capable of handling more than just the pre-defined CL formats. It’s not completely open-ended, but is quite flexible. The out-of-spec formats are also specified in the BFML file (CamML can help here as well)
In the case where you have an older BitFlow frame grabber (Neon/Karbon family), and you are upgrading to the Axion-CL family, you do need to convert your .r64 file to a .BFML file. Simple email the .r64 file to BitFlow.Support@Advantech.com and we will create the equivalent .BFML file for you.
There are two versions of the Windows SDK: free and paid. The free version is all that is need to use BitFlow’s frame grabbers with a 3rd party Machine Vision application such as LabVIEW, VisionPro and HALCON. The paid version is needed for users developing their own applications that will acquire from BitFlow frame grabbers. The paid version provides header files, libraries and copious quantities of example programs with source code. All of the APIs in each support language are fully documented.
The BitFlow SDK supports Windows 7/Windows 8/Windows 10/11 in both 32-bit and 64-bit versions. APIs are available for C/C++/C# (.NET).
There is also a BitFlow SDK for Linux, 32-bit and 64 bit. Most current major distros kernel versions are supported. Both Intel and ARM processors are supported.
The Linux SDK is similar to the WIndows SDK. It’s important to note that the API is not the same between Windows and Linux, but they are similar. The Linux SDK contains a kernel driver, libraries, examples and utilities. Some of the high level utilities (CamML, Ximilon, BitFlow Preview) are the same between Windows and Linux. The Linux API is documented on line here .
While we have created thousands upon thousands of cameras files, there are new cameras emerging every month and it’s not always possible to keep fully up to date with a specific mode for each and every one. Your best approach here is to send an email to support@bitflow.com and provide them with the following information.
The maximum baud rate is 921,600 bits/second.
We do support OpenCV, however it is not through the use of a OpenCV specific driver. Because our frame grabbers can acquire directly into user allocated memory, we can work directly with OpenCV by simply using the BitFlow API to program the board to DMA images directly into OpenCV image buffers. You can then process them normally using OpenCV functions.
When you receive your new board it comes with a postcard which directs you to our site to download the SDK. If this card is missing, please go to https://www.bitflow.com/current-downloads/ and download the SDK. Unzip the file, open the pdf and follow the instructions. If you run into any issues, please go to the last page of the pdf. Here you will see a list of items to include when you contact support via email.
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
The Neon supports up to 256 kb . You can modify the baud rate in BFCom via the File > Com properties menu command.
The command to make the same change in the camera depends on the camera protocol. It’s different for every make of camera. You need to change the camera, then change BFCom to match.
