Cy API不保证附加FX3设备的独占性？

嗨，你试过了吗？HTTP://www. CyPress？COM/？ID＝4和；RID＝40554
当做，
阿南德



     以下为原文
   Hi,
Have you tried this?
http://www.cypress.com/?id=4&rID=40554
    Regards,
    Anand

谢谢，但在大多数情况下，这不是一个可以接受的解决方案。典型地，可以连接两个或多个相同类型的设备（EX 2或3凸轮）。同一应用程序的2个实例应该能够通过设计来打开不同的凸轮并与它们交互而不产生问题或干扰它们自身。
塞浦路斯用哪种机制来克服这个问题？
谢谢，乔尔



     以下为原文
  Thanks but this isn't a acceptable solution in most of the cases. Typically one could attach two or more devices of the same type (ex 2 or 3 cams). 2 instances of the same Application should be able by design to open different Cams and interact with them without generating problems or interfere between them self.
    Which kind of mechanism is Cypress using for overcome this problem ?
    Thanks, Joel

嗨，乔，
我所提供的KB文章也能达到同样的效果。一旦打开句柄，特定设备就不会对其他应用程序可见。句柄关闭后，其他应用程序也可见。
如果这样的特性需要用除此之外的方法来实现，则驱动程序必须维护一个变量来表示这个（Cy***.系统一个实例，而不管连接到它的设备的数量，而不是CyAPI.LIB的情况），并将其提供给CyAPI.lib。还有一大堆需要讨论和理解的场景。请创建一个技术支持的细节，为什么你需要这个特点，什么是需要满足的具体场景。这样我们的团队可以在内部讨论并找出需要做的事情。当做，
阿南德



     以下为原文
   Hi Joe,
    The KB article that I provided is capable of acheiving the same. Once a handle is opened that particular device will not be visible to other applications. After the handle is closed it will be visible to other applications too.
    If a feature like this needs to be implemented in a method other than that, the driver has to maintain a variable to represent this (CyUSB.sys one instance irrespective of number of devices connected to it, not the case for CyAPI.lib) and provide that to CyAPI.lib. There are also a whole bunch of scenarios that need to be discussed and understood. Please create a tech support with details on why you need this feature and what are the specific scenarios that need to be met. This way our team can internally discuss and figure out what needs to be done.
Regards,
    Anand

嗨，这不正确。我添加了“独家”注册表条目，你告诉我，我得到以下行为：
只有一个CyPress设备（我认为排他性与使用CyPress驱动程序的设备有关）即使在它们有不同的PIDs（EX:BooT和Turror固件）时也是可见的。Windows 7设备管理器告诉：“Windows无法加载硬件的设备驱动程序，因为设备驱动程序的前一个实例仍在内存中。（代码38）当我移除2个设备中的一个（例如，具有不同的PID）时，剩余的设备能够将驱动程序加载到存储器中。这意味着在您的修改（Windows 7 64位OS）下，只有一个设备可以使用。这个诅咒解决了并发访问特定设备的问题，因为它只允许在系统上存在1个设备，但我认为您可以同意这不是专业产品可接受的解决方案。
目标场景非常简单，一旦他们出售基于FX3的产品，就会发生在每个人身上。我有两个相同的USB 3产品（相同的PID和VID，可能只有序列号是不同的）。然后将两个设备连接到PC的USB 3树上。人们期望的是，相同或不同应用的两个实例能够打开并使用两个FX3设备中的一个。这两个应用程序不可能使用同一个FX3设备打开广告（不是吗？）.
在MS Windows下，不可能打开和使用给定的串行端口两次。我也期望USB设备也有同样的行为。我希望共享机制能够在比驱动程序更高的层次上实现。
我需要的是一种机制，它允许我以一种排他性的方式处理2个基于FX3的设备，它们同时连接到同一台主机PC。它们都可用。
最好的问候，JoeBre



     以下为原文
  Hi, this isn't correct. I added the "exclusive" registry entry which you told me and I got the following behaviour:
    only one Cypress device ( I suppose that exclusivity is related to devices which are using the Cypress driver) is visible at the time even if they have different PIDs (ex: boot and streamer firmware). The windows 7 device manager tells: "Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)". As soon as I remove one of the 2 devices (which for instance have different PID) the remaining device is able to load the driver into the memory. This means with your modification (under Windows 7 64 bit OS) only one device can be in use. This of curse solves the issue of concurrent access to a particular device since it allows only 1 device to be present on the system, but I think you can agree that this isn't an acceptable solution for a professional product.
     
    The target scenario is very simple and is going to happen to everybody as soon as they sell an FX3 based product. I have two identical USB 3.0 products (Same PID and VID, maybe only the serial number is different). Both devices are then connected to the USB 3.0 tree of a PC. What one would expect is that two instances of the same or a different application are able to open and use one of the two FX3 devices. It shouldn't be possible that the  two applications are opening ad using the SAME FX3 device (isn't it?).
    Under MS windows  it isn't possible to open and use twice a given serial port. I would expect the same behaviour also for a USB device. I would expect a sharing mechanism to be implemented at a higher level than the driver.
    What I need is a mechanism which allows me to handle in an exclusive manner 2 FX3 based devices both connected at the same time to the same host PC. Both of them shall be usable.
    Best regards, JoeBre