Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

2x Mightex USB 3.0 DirectShow Cameras not Enumerating Properly

My Mightex USB 3.0 cameras are not enumerating properly in NI MAX.  The first camera will enumerate fine, but the second will not show up in MAX.  

 

The cameras will enumerate in amcap, but only one of two cameras will show up in NI MAX.

 

http://www.mightexsystems.com/family_info.php?cPath=1_252_273&categories_id=273

 

I have spoken at length with the customer support at Mightex and they assure me that this is only a problem with the most recent version of LabVIEW & MAX.  So they have directed me to the customer support agents at NI to see if we can come up with a solution.

 

The batch file referred to in the attached pdf only has one line in it, the i:1 is changed to i:2 if you want two cameras to enumerate (not in LabVIEW):

regsvr32 /n /i:2 "%~dp0\Mightex_SSClassicSource.ax"

0 Kudos
Message 1 of 7
(6,161 Views)

Hi Matthew,

 

Does the order of cameras seem to matter? For instance, do both cameras enumerate if they are plugged in first, or do they need to be attached in a specific order for this behavior to show up?

 

Also, which version of the Vision Acquisition Software do you have?

0 Kudos
Message 2 of 7
(6,052 Views)

Check the read-only values exposed by MAX, and see if there are duplicates where there should be none, such as a serial number.  I have seen where two different cameras with the same vendor device id will not play nice.  Your problem may be of a similar nature.

Machine Vision, Robotics, Embedded Systems, Surveillance

www.movimed.com - Custom Imaging Solutions
0 Kudos
Message 3 of 7
(6,043 Views)

Hi guys, thanks for the replies.

 

The order of plugging in the cameras does not matter.  The USB cameras enumerate in Windows fine, and amcap is able to distinguish Mightex_SSClassicSource Filter1 from Mightex_SSClassicSource Filter2.  The problem is that when Mightex opens, it only pops up only cam0 : Mightex_SSClassicSource Filter1 shows up listed.

 

Interesting point about the serial numbers though.  They do seem to be duplicates.  I will check with the vendor and see if I can modify one of the serial numbers.

 

Thanks for the help and I'll keep the thread updated!

0 Kudos
Message 4 of 7
(5,991 Views)

Can anyone explain how the serial number field is created in the MAX program?  Below is the information reported by the camera, but the serial number reported in MAX is not the same as what is labeled on the camera and reported in the Mightex OEM software.  So, I need to find the source of the x1505 serial number below to see if changing one of the camera's will get rid of the conflict on the USB bus.

 

Name: cam0

Vendor: Mightex_SSClassicSource Filter1

Model: <BLANK>

Serial Number: 0x0000000000001505

Bus Type: DirectShow

 

Thanks guys.

0 Kudos
Message 5 of 7
(5,948 Views)
DirectShow doesn't expose the serial number. What it does give is a unique identifier string that is specific to the PnP instance of the device (and if the device and bus allow, should stay constant as the device is moved). This string is then hashed by IMAQdx to form a 64-bit serial number for our API purposes.
0 Kudos
Message 6 of 7
(5,839 Views)
Note that it sounds like Mightex ships a pure software DirectShow filter driver that sits on top of their actual driver rather than a native DirectShow driver. Because it is not tied directly to a hardware instance, these are notoriously hard to work with when multiple cameras are involved.
0 Kudos
Message 7 of 7
(5,838 Views)