CXP2.0的相机是否可以使用CXP1.1的Grabber
可以
答案是肯定的。
目前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? :
- 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.
- The CXP2.0 can reach up to 12.5 Gbit/s. This 12.5 Gbit/s mode is referred to as CXP12.
- The CXP2.0 standard will support the new micro BNC connector.
- 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.
- 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.
- 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的更多相关文章
- iOS 判断相机权限是否被限制,判断相机是否可以使用
判断相机权限是否被限制 需要导入 AVFoundation 类 [objc] view plain copy #import <AVFoundation/AVFoundation.h> ...
- swift3.0自定义相机界面
这是公司上上上一个项目的自定义相机界面,原来是swift2.0写的,今天改为swift3.0,记录一下. 效果图如下: ...
- Android 7.0 之后相机/文件读写等权限获取方式改变,导致开启相机闪退
在 Android 7.0 之前 Google 提供的动态申请权限的 API,可以调用相机拍照,访问SDcard等操作都只需要申请对应的权限,如下: <uses-permission andro ...
- [转]opencv3.0 鱼眼相机标定
[原文转自]:http://blog.csdn.net/qq_15947787/article/details/51441031 前两天发表的时候没注意,代码出了点错误,所以修改了一下,重新发上来. ...
- 【温故知新】——BABYLON.js学习之路·前辈经验(二)
前言:在上一篇随笔BABYLON.js学习之路·前辈经验(一)中回顾了组内同事们长时间在Babylon开发实践中的总结出的学习之路和经验,这一篇主要对开发中常见的一些功能点做一个梳理,这里只作为温故知 ...
- 与众不同 windows phone (41) - 8.0 相机和照片: 通过 AudioVideoCaptureDevice 捕获视频和音频
[源码下载] 与众不同 windows phone (41) - 8.0 相机和照片: 通过 AudioVideoCaptureDevice 捕获视频和音频 作者:webabcd 介绍与众不同 win ...
- 与众不同 windows phone (42) - 8.0 相机和照片: 通过 PhotoCaptureDevice 捕获照片
[源码下载] 与众不同 windows phone (42) - 8.0 相机和照片: 通过 PhotoCaptureDevice 捕获照片 作者:webabcd 介绍与众不同 windows pho ...
- 与众不同 windows phone (43) - 8.0 相机和照片: 镜头的可扩展性, 图片的可扩展性, 图片的自动上传扩展
[源码下载] 与众不同 windows phone (43) - 8.0 相机和照片: 镜头的可扩展性, 图片的可扩展性, 图片的自动上传扩展 作者:webabcd 介绍与众不同 windows ph ...
- Android7.0调用系统相机拍照、读取系统相册照片+CropImageView剪裁照片
Android手机拍照.剪裁,并非那么简单 简书地址:[我的简书–T9的第三个三角] 前言 项目中,基本都有用户自定义头像或自定义背景的功能,实现方法一般都是调用系统相机–拍照,或者系统相册–选择照片 ...
- Android Camera 相机程序编写
Android Camera 相机程序编写 要自己写一个相机应用直接使用相机硬件,首先应用需要一个权限设置,在AndroidManifest.xml中加上使用设备相机的权限: <uses-per ...
随机推荐
- killall 以及 pkill 等命令
https://zhidao.baidu.com/question/1500084252693125099.html // 通过 killall 命令killall nginx// 通过 pkill ...
- [转]流程自动化机器人(RPA)概念、原理与实践
[转]流程自动化机器人(RPA)概念.原理与实践 http://blog.sina.com.cn/s/blog_be0833d00102yho9.html 大多数人每天都会使用到一些机器人流程自动化工 ...
- 验证功能访问Redis的次数和命令
背景 公司内部在进行性能调优, 调优有多个方法. 应用Redis方面主要的调优有: 1. 进行redis键值对大小的处理. 2. 进行redis键值对过期时间的处理. 3. 减少连接数,减少网络带宽. ...
- 【K哥爬虫普法】倒计时21天!事关爬虫er们能否平安回家过年!
我国目前并未出台专门针对网络爬虫技术的法律规范,但在司法实践中,相关判决已屡见不鲜,K 哥特设了"K哥爬虫普法"专栏,本栏目通过对真实案例的分析,旨在提高广大爬虫工程师的法律意识, ...
- Docker 完整指南
欢迎来到 Docker 的完整指南!在这个教程中,我们将深入研究 Docker 的各种特性,从基础的容器操作到高级的网络配置和数据管理.让我们一步步地探索 Docker 的丰富功能. 1. 安装 Do ...
- windwos使用FRP方式
FRP使用方法 流程图如下 建议查看流程图哦 访问FRP官方项目 https://freefrp.net 下面是windwos演示 进入网站选择客户端下载 客户端版本选择 windwos是adm64 ...
- 【OpenIM原创】简单轻松入门 一文讲解WebRTC实现1对1音视频通信原理
什么是 WebRTC ? WebRTC(Web Real-Time Communication)是 Google于2010以6829万美元从 Global IP Solutions 公司购买,并于20 ...
- 7.5 C/C++ 实现链表队列
链表队列是一种基于链表实现的队列,相比于顺序队列而言,链表队列不需要预先申请固定大小的内存空间,可以根据需要动态申请和释放内存.在链表队列中,每个节点包含一个数据元素和一个指向下一个节点的指针,头节点 ...
- Python 实现专属字典生成器
编写一个密码生成工具,这里我们使用弱密码与个性化数组组合形成一个定制字典,例如收集用户的姓名,昵称,QQ号手机号等资源,然后通过Python对搜集到的数据与弱密码进行结合,从而定制出属于某个人的专属密 ...
- 推荐一款开源的Diffy自动化测试框架
1. 前言 软件测试是软件开发生命周期一个十分重要的环节,测试工作开展的好坏,很大程度上决定了产品质量的好坏,但软件产品随着版本的持续迭代,功能日益增多,系统愈加复杂,而从质量保障的角度,除了要保障好 ...