可以

答案是肯定的。

目前CXP共有2个发布版本:

2011年发布CXP1.1

2021年发布CXP2.1,向后兼容,新标准增加了同步功能、数据率放大了一倍。

只要是符合CXP标准、接插件匹配,那么CXP2.1是向前兼容CXP1.1的;

借用别人的总结,详细说明参考 https://www.qualitymag.com/articles/95138-what-should-i-know-about-coaxpress-20? :

    1. All cameras and frame grabbers will start up in CXP1.1, only switching to CXP2.0 when both the frame grabber and the camera support CXP2.0.
    1. The CXP2.0 can reach up to 12.5 Gbit/s. This 12.5 Gbit/s mode is referred to as CXP12.
    1. The CXP2.0 standard will support the new micro BNC connector.
    1. CXP2.0 supports configurations where one camera is used with multiple frame grabbers in multiple computers such that the calculations can be performed in parallel.
    1. GenICam features such as heartbeat (allows synchronization between cameras), events and timestamps (actively pushed from the camera to the frame grabber) will now be supported by CXP2.0.
    1. CXP2.0 will allow a higher upstream data rate when operating at CXP10 and CXP12.

1. CoaXPress 2.0 is compatible with CoaXPress 1.1

All cameras and frame grabbers will start up in CXP1.1, only switching to CXP2.0 when both the frame grabber and the camera support CXP2.0.

This means that a CXP1.1 camera works on both the CXP1.1 and CXP2.0 frame grabber. This also means that a CXP2.0 camera works on a CXP1.1 frame grabber, although you will not be able to benefit from the advantages CXP2.0 has to offer.

2. Doubling of the maximum speed

The most obvious improvement is the increased data rate. As previously mentioned the CXP2.0 can reach up to 12.5 Gbit/s. This 12.5 Gbit/s mode is referred to as CXP12. Due to overhead the actual effective bandwidth is approximately 9.6 Gbit/s.

Just to give an example of what would become possible, let’s consider a sensor resolution of 5120x5120 and a bit depth of 10 bit. With four CXP2.0 channels at CXP12 the theoretically possible frame rate could be about 146 FPS. CXP1.1 with 4 channels at CXP6 would only achieve up to 73 FPS in this case.

One thing that needs attention from a system engineer’s point of view would be that while for CXP1.1 PCIe gen2 x8 or gen3 x4 is sufficient for most cases, for CXP2.0 PCIe gen3 x8 will become a minimum common requirement.

3. New connector type

The CXP2.0 standard will support the new micro BNC connector. CoaXPress started with the normal BNC connector, being a big connector, than the smaller DIN 1.0/2.3 connector became more commonly used. Unfortunately the DIN 1.0/2.3 connector resulted in some complaints from the market and it does not support the CXP12 high frequency signals.

Switching to the micro BNC connector does solve these issues. The micro BNC is in size comparable to the DIN connector, while retaining the robustness of the normal BNC connector. The micro BNC supports the required high frequency signals for CXP12 and even can achieve a smaller pitch if needed when placed next to each other. Furthermore the micro BNC connector is a well-established industry standard in the broadcast industry. Although being slightly more expensive compared to the DIN connector, it will give you a very reliable connector being able to do CXP12 speeds.

4. Stream to multiple hosts

Sometimes the computer is the limiting factor in processing speed. This can be the case if a lot of calculations have to be performed on the images. For these situations CXP2.0 supports configurations where one camera is used with multiple frame grabbers in multiple computers such that the calculations can be performed in parallel. This is an optional part of the standard, so ask the camera/frame grabber manufacturer which configurations they support.

The main supported configurations are:

Duplicate one image to multiple frame grabbers/PCs

Example: camera has four CXP connectors; each connector is connected to a different frame grabber in a different PC. One image is recorded by the camera and the complete image is sent to all four PCs.

Divide one image in parts and send to multiple frame grabbers/PCs

Example: camera has four CXP channels, each channel is connected to a different frame grabber in a different PC. The image can be divided in four horizontal or vertical stripes such that each stripe can be sent to a single PC for further processing.

5. Heartbeat, events and timestamps

Missing from CXP1.1, but being part of GenICam for many years is the heartbeat, events and timestamp. These GenICam features will now be supported by CXP2.0.

Heartbeat

The heartbeat allows for synchronization between cameras. Each camera has its own clock and timing. With the heartbeat message, the frame grabber can compute the exact actual time of the camera and link this to its own time clock. Often, the frame grabber clock can be synchronized with the Precision Time Protocol (PTP) IEEE 1588. When multiple cameras are connected to the frame grabber, the frame grabber can use the heartbeat to calculate the relative timing between the cameras and when synchronized with the PTP IEEE 1588, timing between cameras connected to different frame grabbers can be calculated as well. The heartbeat is required to allow for determining the exact moment an event occurred with respect to an event in another camera.

Events and timestamps

Events allow the camera to inform the frame grabber about the occurrence of certain events at a certain time. The time the event occurred is indicated by a timestamp as made possible by the heartbeat. Example events are start or end of exposure or reaching a too high temperature. Events are actively pushed from the camera to the frame grabber. No requests have to be sent to the camera (no polling is required) to monitor for the occurrence of events.

6. Faster Trigger

CXP2.0 will allow for a higher upstream data rate when operating at CXP10 and CXP12. CXP6 and lower use the CXP1.1 upstream data rate. This higher upstream data rate directly reduces the minimum trigger latency by half compared to CXP1.1. From a latency of 3.4 µs it goes to a latency of 1.7µs.

Here the latency is defined as the delay between the moment a trigger is being send and the actual moment the camera has received the trigger and can start the exposure.

CXP2.0的相机是否可以使用CXP1.1的Grabber的更多相关文章

  1. iOS 判断相机权限是否被限制,判断相机是否可以使用

    判断相机权限是否被限制 需要导入   AVFoundation 类 [objc] view plain copy #import <AVFoundation/AVFoundation.h> ...

  2. swift3.0自定义相机界面

    这是公司上上上一个项目的自定义相机界面,原来是swift2.0写的,今天改为swift3.0,记录一下. 效果图如下:                                         ...

  3. Android 7.0 之后相机/文件读写等权限获取方式改变,导致开启相机闪退

    在 Android 7.0 之前 Google 提供的动态申请权限的 API,可以调用相机拍照,访问SDcard等操作都只需要申请对应的权限,如下: <uses-permission andro ...

  4. [转]opencv3.0 鱼眼相机标定

    [原文转自]:http://blog.csdn.net/qq_15947787/article/details/51441031 前两天发表的时候没注意,代码出了点错误,所以修改了一下,重新发上来.  ...

  5. 【温故知新】——BABYLON.js学习之路·前辈经验(二)

    前言:在上一篇随笔BABYLON.js学习之路·前辈经验(一)中回顾了组内同事们长时间在Babylon开发实践中的总结出的学习之路和经验,这一篇主要对开发中常见的一些功能点做一个梳理,这里只作为温故知 ...

  6. 与众不同 windows phone (41) - 8.0 相机和照片: 通过 AudioVideoCaptureDevice 捕获视频和音频

    [源码下载] 与众不同 windows phone (41) - 8.0 相机和照片: 通过 AudioVideoCaptureDevice 捕获视频和音频 作者:webabcd 介绍与众不同 win ...

  7. 与众不同 windows phone (42) - 8.0 相机和照片: 通过 PhotoCaptureDevice 捕获照片

    [源码下载] 与众不同 windows phone (42) - 8.0 相机和照片: 通过 PhotoCaptureDevice 捕获照片 作者:webabcd 介绍与众不同 windows pho ...

  8. 与众不同 windows phone (43) - 8.0 相机和照片: 镜头的可扩展性, 图片的可扩展性, 图片的自动上传扩展

    [源码下载] 与众不同 windows phone (43) - 8.0 相机和照片: 镜头的可扩展性, 图片的可扩展性, 图片的自动上传扩展 作者:webabcd 介绍与众不同 windows ph ...

  9. Android7.0调用系统相机拍照、读取系统相册照片+CropImageView剪裁照片

    Android手机拍照.剪裁,并非那么简单 简书地址:[我的简书–T9的第三个三角] 前言 项目中,基本都有用户自定义头像或自定义背景的功能,实现方法一般都是调用系统相机–拍照,或者系统相册–选择照片 ...

  10. Android Camera 相机程序编写

    Android Camera 相机程序编写 要自己写一个相机应用直接使用相机硬件,首先应用需要一个权限设置,在AndroidManifest.xml中加上使用设备相机的权限: <uses-per ...

随机推荐

  1. [转帖]记录一次spring-boot程序内存泄露排查

    现象 spring boot项目jvm启动配置-Xms4g -Xmx4g,然而很不幸的是程序所占的内存越来越高,都达到了12个多G,只能临时重启服务 常用命令 jstat -class PID jst ...

  2. [转帖] 这grep咋还不支持\d呢(BRE,ERE,PCRE)

    https://www.cnblogs.com/codelogs/p/16060372.html 简介# 对于刚使用Linux不久的同学,肯定会遇到这个问题,就是用grep匹配数字时,发现\d匹配不了 ...

  3. 手写一个Promise完成resolve 和 reject状态的改变和修改属性

    1.手写 Promise 1 创建一个文件 Promise.js:内容 function Promise(){ } 2 引入 Promise.js 这个文件 <script src=" ...

  4. Liunx网络配置

    1.安装精简版:CentOS-7-x86_64-Minimal-2009.iso 2.进入配置文件:  vi /etc/sysconfig/network-scripts/ifcfg-ens33 3. ...

  5. 缩小ios的包体

    不选全部兼容设备 在xcode中导出ipa时,不勾选导出全部兼容性设备,这样导出的ipa包含两种架构:armv7和64 打包压缩 unity提供三种压缩模式可以选择,默认选择的是:default不压缩 ...

  6. SqlSugar跨库查询/多库查询

    一.跨库方式1:跨库导航 (5.1.3.24) 优点1:支持跨服务器,支持跨数据库品种, 支持任何类型数据库 优点2:   超级强大的性能,能达到本库联表性能 缺点:不支持子表过滤主表 (方案有ToL ...

  7. 应用实践:Paddle分类模型大集成者[PaddleHub、Finetune、prompt]

    相关文章: Paddlenlp之UIE模型实战实体抽取任务[打车数据.快递单] Paddlenlp之UIE分类模型[以情感倾向分析新闻分类为例]含智能标注方案) 项目连接: 应用实践:分类模型大集成者 ...

  8. 8.4 C++ 运算符重载

    C/C++语言是一种通用的编程语言,具有高效.灵活和可移植等特点.C语言主要用于系统编程,如操作系统.编译器.数据库等:C语言是C语言的扩展,增加了面向对象编程的特性,适用于大型软件系统.图形用户界面 ...

  9. 8.10 TLS线程局部存储反调试

    TLS(Thread Local Storage)用来在进程内部每个线程中存储私有的数据.每个线程都会拥有独立的TLS存储空间,可以在TLS存储空间中保存线程的上下文信息.变量.函数指针等.TLS其目 ...

  10. Python 实现 WebSocket 通信

    WebSocket 协议主要用于解决Web前端与后台数据交互问题,在WebSocket技术没有被定义之前,前台与后端通信需要使用轮询的方式实现,WebSocket则是通过握手机制让客户端与服务端建立全 ...