可以

答案是肯定的。

目前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. [转帖]Ceph优化系列(四):RocksDB 使用 ARM 64 位 CRC32C 硬件优化指令

    一.前言 CRC32(A cyclic redundancy check 32)应用于校验,为了保证数据的正确性,采用的一种检错手段. CRC32C (CRC32 Castagnoli)  与 CRC ...

  2. SQLSERVER2008R2 本地客户端无法连接的问题

    sqlserver 数据库无法连接问题. 1. 问题现象与简单分析 今天同事找我说一个 SQLSERVER2008R2的测试环境无法连接了. 提示信息为: 当时猜测是 数据库的 配置出问题了. 去查看 ...

  3. SAP Gateway Trace

    最近在SAP PE项目上遇到一个需求要求记录所有的ODATA(含S4/CLOUD API)的报文. Below T-codes recording logging and tracing: /IWFN ...

  4. 【行云流水线】满足你对工作流编排的一切幻想~skr

    流水线模型 众所周知,DevOps流水线(DevOps pipeline)的本质是实现自动化工作流程,用于支持软件开发.测试和部署的连续集成.交付和部署(CI/CD)实践.它是DevOps方法论的核心 ...

  5. echarts饼状图不要中间的文字提示

    饼状图不要中间的文字提示信息 emphasis: { label: { show: false, //将这个设置为false }, }, 为什么饼状图不要中间的问题提示信息 因为有些时候,在文字很多的 ...

  6. MySQL数据库精选(从入门使用到底层结构)

    基本使用MySQL 通用语法及分类 DDL: 数据定义语言,用来定义数据库对象(数据库.表.字段) DML: 数据操作语言,用来对数据库表中的数据进行增删改 DQL: 数据查询语言,用来查询数据库中表 ...

  7. 【6】VScode 无法在终端输入问题,提示:无法在只读编辑器中编辑

    相关文章: [1]VScode中文界面方法-------超简单教程 [2]VScode搭建python和tensorflow环境 [3]VSCode 主题设置推荐,自定义配色方案,修改注释高亮颜色 [ ...

  8. Walrus 实用教程|Walrus + Gitlab,打通CI/CD 自动化交付!

    Walrus file 是 Walrus 0.5 版本推出的新功能,用户可以通过一个非常简洁的 YAML 描述应用或基础设施资源的部署配置,然后通过 Walrus CLI 执行 walrus appl ...

  9. 遥感图像处理笔记之【Automatic Flood Detection from Satellite Images Using Deep Learning】

    遥感图像处理学习(7) 前言 遥感系列第7篇.遥感图像处理方向的学习者可以参考或者复刻 本文初编辑于2023年12月29日 2024年1月24日搬运至本人博客园平台 文章标题:Automatic Fl ...

  10. 目录 - JavaScript指南

    目   录 第一章.  JavaScript概述 第二章.  JavaScript语法基础 第三章.  JavaScript编程规范 第四章.  JavaScript工具集合 第五章.  JavaSc ...