Tag device id with transport to avoid GEV/U3V id collision#1085
Closed
circuitvalley wants to merge 1 commit into
Closed
Tag device id with transport to avoid GEV/U3V id collision#1085circuitvalley wants to merge 1 commit into
circuitvalley wants to merge 1 commit into
Conversation
A camera that reports the same vendor/model/serial over both GigE Vision
and USB3 Vision produced an identical device id on each interface. Because
arv_open_device() returns the first matching interface and USB3Vision is
enumerated before GigEVision, selecting the GigE device silently opened the
USB one.
Append a transport tag ("-eth" / "-usb") to the id built in each interface
so the two are distinct and each resolves to the intended device.
Contributor
|
Hi. Thanks for the patch. Unfortunately, it is a breaking change. Also, it is already possible to select the right device, by using one of the other names it is register under. For example, you can use the MAC address or the ip address of a GigEVision camera, or the USB guid for a USB3Vision device. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A camera that reports the same vendor/model/serial over both GigE Vision and USB3 Vision produced an identical device id on each interface. Because arv_open_device() returns the first matching interface and USB3Vision is enumerated before GigEVision, selecting the GigE device silently opened the USB one.
Append a transport tag ("-eth" / "-usb") to the id built in each interface so the two are distinct and each resolves to the intended device.