ueye usb cmos camera

classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|

ueye usb cmos camera

aaevans
Does anybody have any experience in getting the ueye usb cameras from IDS working with micro manager? I have the UI-1460-CM camera. Any help would be welcome. Thanks
FS
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

FS
Hi,
Did you manage to get your camera to work with Micromanager? I also have one (different model: UI-5240CP-NIR-GL) which I'd like to use with Micromanager.
Cheers,
Francois
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

aaevans
Hi Francois,

No. I'm glad to see that there is twice the number of people now
searching to be able to do this. I will make sure I let you know
if/when I do figure it out.

all the best,

Adrian

On Wed, Oct 3, 2012 at 2:15 AM, FS [via Micro-Manager]
<[hidden email]> wrote:

> Hi,
> Did you manage to get your camera to work with Micromanager? I also have one
> (different model: UI-5240CP-NIR-GL) which I'd like to use with Micromanager.
> Cheers,
> Francois
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://micro-manager.3463995.n2.nabble.com/ueye-usb-cmos-camera-tp5502765p7578773.html
> To unsubscribe from ueye usb cmos camera, click here.
> NAML
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

Arthur D. Edelstein
Hi Francois and Adrian,

Have you tried the OpenCVadapter? If either of those cameras are
DirectShow-compatible, it might work.

Best regards,
Arthur


On Wed, Oct 3, 2012 at 1:21 AM, aaevans <[hidden email]> wrote:

> Hi Francois,
>
> No. I'm glad to see that there is twice the number of people now
> searching to be able to do this. I will make sure I let you know
> if/when I do figure it out.
>
> all the best,
>
> Adrian
>
> On Wed, Oct 3, 2012 at 2:15 AM, FS [via Micro-Manager]
> <[hidden email]> wrote:
>
>> Hi,
>> Did you manage to get your camera to work with Micromanager? I also have
>> one
>> (different model: UI-5240CP-NIR-GL) which I'd like to use with
>> Micromanager.
>> Cheers,
>> Francois
>>
>> ________________________________
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://micro-manager.3463995.n2.nabble.com/ueye-usb-cmos-camera-tp5502765p7578773.html
>> To unsubscribe from ueye usb cmos camera, click here.
>> NAML
>
> ________________________________
> View this message in context: Re: ueye usb cmos camera
>
> Sent from the Micro-Manager mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> micro-manager-general mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/micro-manager-general
>

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

manamana8014
This post was updated on .
In reply to this post by aaevans
Hello to everyone!

I'd like to reanimate this thread, 'cause I have the same problem now - I have uEye USB camera from IDS, model UI-1480-SE-M. I have followed the suggestion given here:
http://micro-manager.org/wiki/IDS_uEye
Downloaded latest drivers from IDS, version 4.30, camera is monochrome. When I try to open configuration file "MMConfig_uEye.cfg" results in the error message:

I cannot create the new configuration file either while the IDS is not listed in the list of supported devises and there are no files in the MM folder which would contain IDS or uEye in the file name.
Any suggestions?
Thanks,

Yaroslav.

PS. Here is the CoreLog:

LOG(2013-11-19T10:20:52.867379, 3720, 000DC8A0:): -------->>
LOG(2013-11-19T10:20:52.867379, 3720, 000DC8A0:): Core session started on 2013-11-19T10:20:52.867379 by IMPB on TEM410
LOG(2013-11-19T10:20:52.867379, 3720, 000DC8A0:): Debug logging disabled
LOG(2013-11-19T10:20:52.867379, 3720, 000DC8A0:): Debug logging disabled
LOG(2013-11-19T10:20:52.867379, 3720, 000DC8A0:): > MM Studio version: 1.4.6  20110722
LOG(2013-11-19T10:20:52.867379, 3720, 000DC8A0:): > MMCore version 2.3.1
LOG(2013-11-19T10:20:52.867379, 3720, 000DC8A0:): > Device API version 45, Module API version 6
LOG(2013-11-19T10:20:52.867379, 3720, 000DC8A0:): > Operating System: Windows 7 6.1
LOG(2013-11-19T10:20:54.907382, 3720, 000DC8A0:): > Attempting to install plugin org.micromanager.browser.Data_Browser
LOG(2013-11-19T10:20:54.907382, 3720, 000DC8A0:): > Error: Data_Browser fails to implement static String menuName.
LOG(2013-11-19T10:20:54.907382, 3720, 000DC8A0:): > Attempting to install plugin org.micromanager.multicamera.MultiCamera
LOG(2013-11-19T10:20:54.907382, 3720, 000DC8A0:): > Attempting to install plugin org.micromanager.pixelcalibrator.PixelCalibratorPlugin
LOG(2013-11-19T10:20:54.907382, 3720, 000DC8A0:): > Attempting to install plugin org.micromanager.projector.ProjectorPlugin
LOG(2013-11-19T10:20:54.907382, 3720, 000DC8A0:): > Attempting to install plugin org.micromanager.recall.RecallPlugin
LOG(2013-11-19T10:20:54.907382, 3720, 000DC8A0:): > Attempting to install plugin org.micromanager.slideexplorer.SlideExplorerPlugin
LOG(2013-11-19T10:20:54.907382, 3720, 000DC8A0:): > Attempting to install plugin org.micromanager.stagecontrol.StageControl
LOG(2013-11-19T10:20:54.907382, 3720, 000DC8A0:): > Attempting to install autofocus plugin Autofocus
LOG(2013-11-19T10:20:54.907382, 3720, 000DC8A0:): > Attempting to install autofocus plugin OughtaFocus
LOG(2013-11-19T10:20:54.907382, 3720, 000DC8A0:): > Attempting to install autofocus plugin AutofocusDuo
LOG(2013-11-19T10:20:54.907382, 3720, 000DC8A0:): > Attempting to install autofocus plugin AutofocusTB
LOG(2013-11-19T10:20:54.907382, 3720, 000DC8A0:): > Attempting to install autofocus plugin OughtaFocus
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): All devices unloaded.
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Error occured. Device MMCore::loadDevice. The given module is not found.

 IDS_uEye
Unable to load library: file not accessible or corrupted.

LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Starting initialization sequence for 0 devices...
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Auto shutter ON.
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Resolution ID 1.67um: for device IDS uEye defined as Sensor pixel size=1.6700
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Pixel size 1.670000 um set for resolution ID: 1.67um
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Resolution ID 2.20um: for device IDS uEye defined as Sensor pixel size=2.2000
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Pixel size 2.200000 um set for resolution ID: 2.20um
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Resolution ID 3.45um: for device IDS uEye defined as Sensor pixel size=3.4500
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Pixel size 3.450000 um set for resolution ID: 3.45um
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Resolution ID 3.75um: for device IDS uEye defined as Sensor pixel size=3.7500
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Pixel size 3.750000 um set for resolution ID: 3.75um
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Resolution ID 4.40um: for device IDS uEye defined as Sensor pixel size=4.4000
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Pixel size 4.400000 um set for resolution ID: 4.40um
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Resolution ID 4.65um: for device IDS uEye defined as Sensor pixel size=4.6500
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Pixel size 4.650000 um set for resolution ID: 4.65um
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Resolution ID 5.20um: for device IDS uEye defined as Sensor pixel size=5.2000
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Pixel size 5.200000 um set for resolution ID: 5.20um
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Resolution ID 5.30um: for device IDS uEye defined as Sensor pixel size=5.3000
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Pixel size 5.300000 um set for resolution ID: 5.30um
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Resolution ID 6.00um: for device IDS uEye defined as Sensor pixel size=6.0000
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Pixel size 6.000000 um set for resolution ID: 6.00um
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Resolution ID 7.40um: for device IDS uEye defined as Sensor pixel size=7.4000
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Pixel size 7.400000 um set for resolution ID: 7.40um
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Resolution ID 8.30um: for device IDS uEye defined as Sensor pixel size=8.3000
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Pixel size 8.300000 um set for resolution ID: 8.30um
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Resolution ID 9.90um: for device IDS uEye defined as Sensor pixel size=9.9000
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Pixel size 9.900000 um set for resolution ID: 9.90um
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Resolution ID 10.00um: for device IDS uEye defined as Sensor pixel size=10.0000
LOG(2013-11-19T10:21:02.977393, 3720, 000DC8A0:): Pixel size 10.000000 um set for resolution ID: 10.00um
LOG(2013-11-19T10:21:02.987393, 3720, 000DC8A0:): >
java.lang.Exception: Line 7: Device,IDS uEye,IDS_uEye,IDS uEye
the given module is not found.

 IDS_uEye
Unable to load library: file not accessible or corrupted.

Line 21: Property,Core,Camera,IDS uEye
Attempted to set "Core-Camera" to "IDS uEye".
Core property is read-only or the requested value is not allowed.


 in Thread[AWT-EventQueue-0,6,main]
  at mmcorej.MMCoreJJNI.CMMCore_loadSystemConfiguration(Native Method)
  at mmcorej.CMMCore.loadSystemConfiguration(CMMCore.java:192)
  at org.micromanager.MMStudioMainFrame.loadSystemConfiguration(MMStudioMainFrame.java:3519)
  at org.micromanager.MMStudioMainFrame.access$600(MMStudioMainFrame.java:150)
  at org.micromanager.MMStudioMainFrame$38.windowOpened(MMStudioMainFrame.java:1771)
  at java.awt.AWTEventMulticaster.windowOpened(Unknown Source)
  at java.awt.AWTEventMulticaster.windowOpened(Unknown Source)
  at java.awt.Window.processWindowEvent(Unknown Source)
  at javax.swing.JFrame.processWindowEvent(Unknown Source)
  at java.awt.Window.processEvent(Unknown Source)
  at java.awt.Component.dispatchEventImpl(Unknown Source)
  at java.awt.Container.dispatchEventImpl(Unknown Source)
  at java.awt.Window.dispatchEventImpl(Unknown Source)
  at java.awt.Component.dispatchEvent(Unknown Source)
  at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
  at java.awt.EventQueue.access$200(Unknown Source)
  at java.awt.EventQueue$3.run(Unknown Source)
  at java.awt.EventQueue$3.run(Unknown Source)
  at java.security.AccessController.doPrivileged(Native Method)
  at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
  at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
  at java.awt.EventQueue$4.run(Unknown Source)
  at java.awt.EventQueue$4.run(Unknown Source)
  at java.security.AccessController.doPrivileged(Native Method)
  at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
  at java.awt.EventQueue.dispatchEvent(Unknown Source)
  at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
  at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
  at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
  at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
  at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
  at java.awt.EventDispatchThread.run(Unknown Source)








aaevans wrote
Does anybody have any experience in getting the ueye usb cameras from IDS working with micro manager? I have the UI-1460-CM camera. Any help would be welcome. Thanks
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

Mark Tsuchida-2
Hi Yaroslav,

On Tue, Nov 19, 2013 at 6:51 AM, manamana8014 <[hidden email]> wrote:

> I'd like to reanimate this thread, 'cause I have the same problem now - I
> have uEye USB camera from IDS, model UI-1480-SE-M. I have followed the
> suggestion given here:
> http://micro-manager.org/wiki/IDS_uEye
> Downloaded latest drivers from IDS, version 4.30, camera is monochrome. When
> I try to open configuration file "MMConfig_uEye.cfg" results in the error
> message:
> <http://micro-manager.3463995.n2.nabble.com/file/n7581576/snapshot.jpg>
> I cannot create the new configuration file either while the IDS is not
> listed in the list of supported devises and there are no files in the MM
> folder which would contain IDS or uEye in the file name.

When you install the IDS uEye software, make sure to check "USB Device
drivers and tools". If this is not selected, IDS_uEye will appear as
"unavailable".

Also make sure that you are using the 64-bit version of Micro-Manager
if you installed the 64-bit version of the uEye software (and likewise
for 32-bit).

Micro-Manager is currently being built against version 4.22. Hopefully
4.30 will work, but let me know if you have further problems.

Best,
Mark

------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

manamana8014

Hi, Mark!


Thanks for the help! But the cure was even simpler - complete re-installation of current version of Micro-Manager.

Though I have now the other problem - the maximum exposure that I can use is limited to 332.smth ms and this value is not getting any bigger if to change the pixel clock value. The same is true for framerate - the lowest value is about 1.7, the highest - 3.1. Same time if you use original software from IDS, depending on the pixel clock you can have the exposure up to 3 s and the framerate also varies much better. Any ideas?

Best regards,


Yaroslav.


20 лист. 2013 00:10, користувач "Mark Tsuchida-2 [via Micro-Manager]" <[hidden email]> написав:
Hi Yaroslav,

On Tue, Nov 19, 2013 at 6:51 AM, manamana8014 <[hidden email]> wrote:

> I'd like to reanimate this thread, 'cause I have the same problem now - I
> have uEye USB camera from IDS, model UI-1480-SE-M. I have followed the
> suggestion given here:
> http://micro-manager.org/wiki/IDS_uEye
> Downloaded latest drivers from IDS, version 4.30, camera is monochrome. When
> I try to open configuration file "MMConfig_uEye.cfg" results in the error
> message:
> <http://micro-manager.3463995.n2.nabble.com/file/n7581576/snapshot.jpg>
> I cannot create the new configuration file either while the IDS is not
> listed in the list of supported devises and there are no files in the MM
> folder which would contain IDS or uEye in the file name.
When you install the IDS uEye software, make sure to check "USB Device
drivers and tools". If this is not selected, IDS_uEye will appear as
"unavailable".

Also make sure that you are using the 64-bit version of Micro-Manager
if you installed the 64-bit version of the uEye software (and likewise
for 32-bit).

Micro-Manager is currently being built against version 4.22. Hopefully
4.30 will work, but let me know if you have further problems.

Best,
Mark

------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general



If you reply to this email, your message will be added to the discussion below:
http://micro-manager.3463995.n2.nabble.com/ueye-usb-cmos-camera-tp5502765p7581579.html
To unsubscribe from ueye usb cmos camera, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

Mark Tsuchida-2
Hi Yaroslav,

On Wed, Nov 20, 2013 at 2:08 AM, manamana8014 <[hidden email]> wrote:
> Thanks for the help! But the cure was even simpler - complete
> re-installation of current version of Micro-Manager.

Great!

> Though I have now the other problem - the maximum exposure that I can use is
> limited to 332.smth ms and this value is not getting any bigger if to change
> the pixel clock value. The same is true for framerate - the lowest value is
> about 1.7, the highest - 3.1. Same time if you use original software from
> IDS, depending on the pixel clock you can have the exposure up to 3 s and
> the framerate also varies much better. Any ideas?

It looks like the device adapter sets the maximum exposure to the
maximum reported by the IDS driver, or 1000 ms, whichever is smaller
(I'm not sure what the reason for the 1000 ms limit is).

It also looks like the allowed range for the exposure is only updated
(1) on startup and (2) when the ROI changes. It is not updated when
the Pixel Clock changes. Perhaps this is the problem. Using IDS's
software, are there any Pixel Clock settings that cause the exposure
to be limited to 332 ms?

If so, it should be straightforward to update the allowed exposure
range when the Pixel Clock changes. While we are at it, do you see any
other settings (other than ROI and pixel clock) that may affect the
allowed exposure range?

Best,
Mark

------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

wenjarose
Hi Mark, Hi Yaroslav,

thanks for the notice!

You are right, at the moment the ranges of the properties are set only once at the startup. Thus they become inconsistent if one of the parameters is changed. Hence, the maximal exposure is basically the inverse of the default frame rate. The 1000 ms limit was introduced just to avoid occasional setting of too large values which freezed the interface.
Making these parameters consistent is (as you may have noticed) the first point on my todo list for the driver. Though I am quite busy with the rest of the project, I will try to address this issue asap. If there are other issues/comments, do not hesitate to contact me.

@Mark: by the way, I have noticed that in the current revision of Micro-Manager the corresponding lines for IDS_uEye are missing in Makefile.am and configure.in files in DeviceAdapters directory, thus no Makefile is created and the driver is not built by default in Linux environment. Can this be corrected? Thanks!

Best regards

Wenjamin



On Wednesday, November 20, 2013 10:33 PM, Mark Tsuchida <[hidden email]> wrote:
Hi Yaroslav,

On Wed, Nov 20, 2013 at 2:08 AM, manamana8014 <[hidden email]> wrote:
> Thanks for the help! But the cure was even simpler - complete
> re-installation of current version of Micro-Manager.

Great!

> Though I have now the other problem - the maximum exposure that I can use is
> limited to 332.smth ms and this value is not getting any bigger if to change
> the pixel clock value. The same is true for framerate - the lowest value is
> about 1.7, the highest - 3.1. Same time if you use original software from
> IDS, depending on the pixel clock you can have the exposure up to 3 s and
> the framerate also varies much better. Any ideas?

It looks like the device adapter sets the maximum exposure to the
maximum reported by the IDS driver, or 1000 ms, whichever is smaller
(I'm not sure what the reason for the 1000 ms limit is).

It also looks like the allowed range for the exposure is only updated
(1) on startup and (2) when the ROI changes. It is not updated when
the Pixel Clock changes. Perhaps this is the problem. Using IDS's
software, are there any Pixel Clock settings that cause the exposure
to be limited to 332 ms?

If so, it should be straightforward to update the allowed exposure
range when the Pixel Clock changes. While we are at it, do you see any
other settings (other than ROI and pixel clock) that may affect the
allowed exposure range?

Best,
Mark



------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

Mark Tsuchida-2
Hi Wenjamin,

On Mon, Nov 25, 2013 at 9:35 AM, Wenjamin Rosenfeld <[hidden email]> wrote:
> You are right, at the moment the ranges of the properties are set only once
> at the startup. Thus they become inconsistent if one of the parameters is
> changed. Hence, the maximal exposure is basically the inverse of the default
> frame rate. The 1000 ms limit was introduced just to avoid occasional
> setting of too large values which freezed the interface.
> Making these parameters consistent is (as you may have noticed) the first
> point on my todo list for the driver. Though I am quite busy with the rest
> of the project, I will try to address this issue asap. If there are other
> issues/comments, do not hesitate to contact me.

Great!

> @Mark: by the way, I have noticed that in the current revision of
> Micro-Manager the corresponding lines for IDS_uEye are missing in
> Makefile.am and configure.in files in DeviceAdapters directory, thus no
> Makefile is created and the driver is not built by default in Linux
> environment. Can this be corrected? Thanks!

It looks like it was never added to the Unix build. To add it, we
would need to write code (in DeviceAdapters/configure.in) to detect
whether the IDS uEye library (-lueye_api) is available, so that the
build works in the absence of that library. Do you know if the library
provides a method for detection, or, if not, can you tell us the
install location of all the necessary headers and libraries?

Best,
Mark

------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

Philipp Linke
In reply to this post by wenjarose

Hi everyone,

 

I also have the issue of a limited exposure time with the ueye cam (model: UI-3420CP-M-GL). The maximum exposure time I can get is around 66.6 ms. Has there been any progress in the newer revisions? I am using 1.4.15 right now.

Best Regards,

Philipp

 

From: Wenjamin Rosenfeld [mailto:[hidden email]]
Sent: Montag, 25. November 2013 18:35
To: Mark Tsuchida; Micro-Manager General; manamana8014
Subject: Re: [micro-manager-general] ueye usb cmos camera

 

Hi Mark, Hi Yaroslav,

thanks for the notice!

You are right, at the moment the ranges of the properties are set only once at the startup. Thus they become inconsistent if one of the parameters is changed. Hence, the maximal exposure is basically the inverse of the default frame rate. The 1000 ms limit was introduced just to avoid occasional setting of too large values which freezed the interface.
Making these parameters consistent is (as you may have noticed) the first point on my todo list for the driver. Though I am quite busy with the rest of the project, I will try to address this issue asap. If there are other issues/comments, do not hesitate to contact me.

@Mark: by the way, I have noticed that in the current revision of Micro-Manager the corresponding lines for IDS_uEye are missing in Makefile.am and configure.in files in DeviceAdapters directory, thus no Makefile is created and the driver is not built by default in Linux environment. Can this be corrected? Thanks!

Best regards

Wenjamin

 

 

On Wednesday, November 20, 2013 10:33 PM, Mark Tsuchida <[hidden email]> wrote:

Hi Yaroslav,

On Wed, Nov 20, 2013 at 2:08 AM, manamana8014 <[hidden email]> wrote:
> Thanks for the help! But the cure was even simpler - complete
> re-installation of current version of Micro-Manager.

Great!

> Though I have now the other problem - the maximum exposure that I can use is
> limited to 332.smth ms and this value is not getting any bigger if to change
> the pixel clock value. The same is true for framerate - the lowest value is
> about 1.7, the highest - 3.1. Same time if you use original software from
> IDS, depending on the pixel clock you can have the exposure up to 3 s and
> the framerate also varies much better. Any ideas?

It looks like the device adapter sets the maximum exposure to the
maximum reported by the IDS driver, or 1000 ms, whichever is smaller
(I'm not sure what the reason for the 1000 ms limit is).

It also looks like the allowed range for the exposure is only updated
(1) on startup and (2) when the ROI changes. It is not updated when
the Pixel Clock changes. Perhaps this is the problem. Using IDS's
software, are there any Pixel Clock settings that cause the exposure
to be limited to 332 ms?

If so, it should be straightforward to update the allowed exposure
range when the Pixel Clock changes. While we are at it, do you see any
other settings (other than ROI and pixel clock) that may affect the
allowed exposure range?

Best,
Mark


------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

Mark Tsuchida-2
Hi Philipp,

On Fri, Jan 17, 2014 at 7:15 AM, Philipp Linke <[hidden email]> wrote:
> I also have the issue of a limited exposure time with the ueye cam (model:
> UI-3420CP-M-GL). The maximum exposure time I can get is around 66.6 ms. Has
> there been any progress in the newer revisions? I am using 1.4.15 right now.

Wenjamin made a fix for this issue, and the fix is in nightly builds
since 20131227. Could you try a recent build?

Best,
Mark

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

Philipp Linke
In reply to this post by wenjarose

Hi Wenjamin,

 

I heard about your fix for the uEye camera. Today I tried the nightly build from 17.01.2014 (camera model: UI-3240CP-M-GL). The exposure time now changes correctly when changing the frame rate or pixel clock. Unfortunately the exposure time only changes in the device property window, not in the main frame. Also, increasing the frame rate without changing the exposure time leads to darker images which should not happen.

When  changing the exposure time in the device property window, it changes correctly in the main window, but it is not updated for the acquisition window, since all new snapshots look the same until the exposure time is changed directly in the main window.

The problem can be avoided by always setting the exposure time in the main window after changing the pixel clock or frame rate.

 

Also I noticed that the pixel depth (8-bit) cannot be changed (to 10-/12-bit), which is possible in the software from the company (only when using USB3.0).

Best Regards,

Philipp

 

From: Wenjamin Rosenfeld [mailto:[hidden email]]
Sent: Montag, 25. November 2013 18:35
To: Mark Tsuchida; Micro-Manager General; manamana8014
Subject: Re: [micro-manager-general] ueye usb cmos camera

 

Hi Mark, Hi Yaroslav,

thanks for the notice!

You are right, at the moment the ranges of the properties are set only once at the startup. Thus they become inconsistent if one of the parameters is changed. Hence, the maximal exposure is basically the inverse of the default frame rate. The 1000 ms limit was introduced just to avoid occasional setting of too large values which freezed the interface.
Making these parameters consistent is (as you may have noticed) the first point on my todo list for the driver. Though I am quite busy with the rest of the project, I will try to address this issue asap. If there are other issues/comments, do not hesitate to contact me.

@Mark: by the way, I have noticed that in the current revision of Micro-Manager the corresponding lines for IDS_uEye are missing in Makefile.am and configure.in files in DeviceAdapters directory, thus no Makefile is created and the driver is not built by default in Linux environment. Can this be corrected? Thanks!

Best regards

Wenjamin

 

 

On Wednesday, November 20, 2013 10:33 PM, Mark Tsuchida <[hidden email]> wrote:

Hi Yaroslav,

On Wed, Nov 20, 2013 at 2:08 AM, manamana8014 <[hidden email]> wrote:
> Thanks for the help! But the cure was even simpler - complete
> re-installation of current version of Micro-Manager.

Great!

> Though I have now the other problem - the maximum exposure that I can use is
> limited to 332.smth ms and this value is not getting any bigger if to change
> the pixel clock value. The same is true for framerate - the lowest value is
> about 1.7, the highest - 3.1. Same time if you use original software from
> IDS, depending on the pixel clock you can have the exposure up to 3 s and
> the framerate also varies much better. Any ideas?

It looks like the device adapter sets the maximum exposure to the
maximum reported by the IDS driver, or 1000 ms, whichever is smaller
(I'm not sure what the reason for the 1000 ms limit is).

It also looks like the allowed range for the exposure is only updated
(1) on startup and (2) when the ROI changes. It is not updated when
the Pixel Clock changes. Perhaps this is the problem. Using IDS's
software, are there any Pixel Clock settings that cause the exposure
to be limited to 332 ms?

If so, it should be straightforward to update the allowed exposure
range when the Pixel Clock changes. While we are at it, do you see any
other settings (other than ROI and pixel clock) that may affect the
allowed exposure range?

Best,
Mark


------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

wenjarose
Hi Philipp, hi Mark,

I have also noticed the issue that changing the exposure value in the property browser updates the according input field in the main acquisition window, but this value is not used until you press enter in the input field. To my understanding this happens at a level above the actual device adapter.
Mark, can you confirm this?
A somehow related issue is also that for certain ranges of framerate/exposure time, etc., in the property browser selecting the minimal or maximal value (by using, e.g., the slider) triggers a range-check error ("Error in device... Invalid property value... Error code:3). Whether this happens seems to depend on the actual values, so I suppose this has to do with rounding of float numbers.

Philipp, I could not reproduce the problem of darker images for different frame rates. When changing frame rate  at constant exposure, the brightness was exactly the same in my case. Also, the frame rate parameter is actually a property of the internal "live" mode of the camera which is not used in the live-mode of micro manager. So it will not always determine the actual frame rate (although for some models it surprisingly does). It should be rather taken as a parameter defining the exposure range.

Finally, at the moment, the highest available bit depth is automatically selected. The possibility to select the bit depth, as well as support for color modes are currently work in progress.

Best regards

Wenjamin


On Monday, January 20, 2014 12:19 PM, Philipp Linke <[hidden email]> wrote:
Hi Wenjamin,
 
I heard about your fix for the uEye camera. Today I tried the nightly build from 17.01.2014 (camera model: UI-3240CP-M-GL). The exposure time now changes correctly when changing the frame rate or pixel clock. Unfortunately the exposure time only changes in the device property window, not in the main frame. Also, increasing the frame rate without changing the exposure time leads to darker images which should not happen.
When  changing the exposure time in the device property window, it changes correctly in the main window, but it is not updated for the acquisition window, since all new snapshots look the same until the exposure time is changed directly in the main window.

The problem can be avoided by always setting the exposure time in the main window after changing the pixel clock or frame rate.
 
Also I noticed that the pixel depth (8-bit) cannot be changed (to 10-/12-bit), which is possible in the software from the company (only when using USB3.0).

Best Regards,
Philipp
 
From: Wenjamin Rosenfeld [mailto:[hidden email]]
Sent: Montag, 25. November 2013 18:35
To: Mark Tsuchida; Micro-Manager General; manamana8014
Subject: Re: [micro-manager-general] ueye usb cmos camera
 
Hi Mark, Hi Yaroslav,

thanks for the notice!

You are right, at the moment the ranges of the properties are set only once at the startup. Thus they become inconsistent if one of the parameters is changed. Hence, the maximal exposure is basically the inverse of the default frame rate. The 1000 ms limit was introduced just to avoid occasional setting of too large values which freezed the interface.
Making these parameters consistent is (as you may have noticed) the first point on my todo list for the driver. Though I am quite busy with the rest of the project, I will try to address this issue asap. If there are other issues/comments, do not hesitate to contact me.

@Mark: by the way, I have noticed that in the current revision of Micro-Manager the corresponding lines for IDS_uEye are missing in Makefile.am and configure.in files in DeviceAdapters directory, thus no Makefile is created and the driver is not built by default in Linux environment. Can this be corrected? Thanks!

Best regards

Wenjamin
 
 
On Wednesday, November 20, 2013 10:33 PM, Mark Tsuchida <[hidden email]> wrote:
Hi Yaroslav,

On Wed, Nov 20, 2013 at 2:08 AM, manamana8014 <[hidden email]> wrote:
> Thanks for the help! But the cure was even simpler - complete
> re-installation of current version of Micro-Manager.

Great!

> Though I have now the other problem - the maximum exposure that I can use is
> limited to 332.smth ms and this value is not getting any bigger if to change
> the pixel clock value. The same is true for framerate - the lowest value is
> about 1.7, the highest - 3.1. Same time if you use original software from
> IDS, depending on the pixel clock you can have the exposure up to 3 s and
> the framerate also varies much better. Any ideas?

It looks like the device adapter sets the maximum exposure to the
maximum reported by the IDS driver, or 1000 ms, whichever is smaller
(I'm not sure what the reason for the 1000 ms limit is).

It also looks like the allowed range for the exposure is only updated
(1) on startup and (2) when the ROI changes. It is not updated when
the Pixel Clock changes. Perhaps this is the problem. Using IDS's
software, are there any Pixel Clock settings that cause the exposure
to be limited to 332 ms?

If so, it should be straightforward to update the allowed exposure
range when the Pixel Clock changes. While we are at it, do you see any
other settings (other than ROI and pixel clock) that may affect the
allowed exposure range?

Best,
Mark




------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

Mark Tsuchida-2
Hi Wenjamin and Philipp,

On Mon, Jan 20, 2014 at 3:19 AM, Philipp Linke <[hidden email]> wrote:
> Unfortunately the exposure time only changes in the device property window,
> not in the main frame.
[...]
> When  changing the exposure time in the device property window, it changes
> correctly in the main window, but it is not updated for the acquisition
> window, since all new snapshots look the same until the exposure time is
> changed directly in the main window.

On Mon, Jan 20, 2014 at 10:31 AM, Wenjamin Rosenfeld
<[hidden email]> wrote:
> I have also noticed the issue that changing the exposure value in the
> property browser updates the according input field in the main acquisition
> window, but this value is not used until you press enter in the input field.
> To my understanding this happens at a level above the actual device adapter.
> Mark, can you confirm this?

Note that the main window uses the SetExposure() function, while the
Property Browser sets the "Exposure" (g_Keyword_Exposure) property
(not sure why we ended up with these redundant mechanisms, but that's
how it is for the present). It is currently the responsibility of the
device adapter to keep these two in sync. (With the DemoCamera,
setting the "Exposure" in the Property Browser works correctly.)

It looks like the IDS_uEye adapter doesn't register an action handler
for the "Exposure" property (see IDS_uEye.cpp, line 402), which is
probably the reason for setting the Exposure in the Property Browser
not working.

The fact that the Exposure displayed in the main window gets updated
has to do with the extra things done by the Property Browser GUI to
attempt to keep things up to date; the quickest way to test properties
in isolation is to call mmc.setProperty("mydevice", "myproperty",
myvalue); in the Script Panel.

> A somehow related issue is also that for certain ranges of
> framerate/exposure time, etc., in the property browser selecting the minimal
> or maximal value (by using, e.g., the slider) triggers a range-check error
> ("Error in device... Invalid property value... Error code:3). Whether this
> happens seems to depend on the actual values, so I suppose this has to do
> with rounding of float numbers.

The error should be a result of the value exceeding the limits set by
SetPropertyLimits(). What you describe might be a bug, either in the
GUI or in the internal property value handling. Do you have examples
of the actual limit values and the values that trigger an error?

Best,
Mark

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

wenjarose
Hi Philipp, hi Mark,

I have implemented an extra exposure handler, now changing exposure in the property browser updates and sets the exposure in the main window (the other way round one still needs to click the "refresh" button).
The code is in the repository (rev. 12637).

Mark, thePropertyLimits error seems to be tricky. When some lower limit for e.g. frame rate (0.10000) is set, sometimes I can select this value without error (or even lower value which is then automatically corrected) and sometimes not. This seems to depend (in my case) on  pixel clock, although for its whole range the low limit for the frame rate for my camera is the same (0.10000).  I currently do not understand the system behind the error, will need to look at it closer.

Best regards

Wenjamin


On Tuesday, January 21, 2014 8:44 PM, Mark Tsuchida <[hidden email]> wrote:
Hi Wenjamin and Philipp,

On Mon, Jan 20, 2014 at 3:19 AM, Philipp Linke <[hidden email]> wrote:
> Unfortunately the exposure time only changes in the device property window,
> not in the main frame.
[...]
> When  changing the exposure time in the device property window, it changes
> correctly in the main window, but it is not updated for the acquisition
> window, since all new snapshots look the same until the exposure time is
> changed directly in the main window.

On Mon, Jan 20, 2014 at 10:31 AM, Wenjamin Rosenfeld
<[hidden email]> wrote:
> I have also noticed the issue that changing the exposure value in the
> property browser updates the according input field in the main acquisition
> window, but this value is not used until you press enter in the input field.
> To my understanding this happens at a level above the actual device adapter.
> Mark, can you confirm this?

Note that the main window uses the SetExposure() function, while the
Property Browser sets the "Exposure" (g_Keyword_Exposure) property
(not sure why we ended up with these redundant mechanisms, but that's
how it is for the present). It is currently the responsibility of the
device adapter to keep these two in sync. (With the DemoCamera,
setting the "Exposure" in the Property Browser works correctly.)

It looks like the IDS_uEye adapter doesn't register an action handler
for the "Exposure" property (see IDS_uEye.cpp, line 402), which is
probably the reason for setting the Exposure in the Property Browser
not working.

The fact that the Exposure displayed in the main window gets updated
has to do with the extra things done by the Property Browser GUI to
attempt to keep things up to date; the quickest way to test properties
in isolation is to call mmc.setProperty("mydevice", "myproperty",
myvalue); in the Script Panel.

> A somehow related issue is also that for certain ranges of
> framerate/exposure time, etc., in the property browser selecting the minimal
> or maximal value (by using, e.g., the slider) triggers a range-check error
> ("Error in device... Invalid property value... Error code:3). Whether this
> happens seems to depend on the actual values, so I suppose this has to do
> with rounding of float numbers.

The error should be a result of the value exceeding the limits set by
SetPropertyLimits(). What you describe might be a bug, either in the
GUI or in the internal property value handling. Do you have examples
of the actual limit values and the values that trigger an error?


Best,
Mark



------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

Mark Tsuchida-2
Hi Wenjamin,

On Thu, Jan 23, 2014 at 11:06 AM, Wenjamin Rosenfeld
<[hidden email]> wrote:
> I have implemented an extra exposure handler, now changing exposure in the
> property browser updates and sets the exposure in the main window (the other
> way round one still needs to click the "refresh" button).
> The code is in the repository (rev. 12637).

Great!

> Mark, thePropertyLimits error seems to be tricky. When some lower limit for
> e.g. frame rate (0.10000) is set, sometimes I can select this value without
> error (or even lower value which is then automatically corrected) and
> sometimes not. This seems to depend (in my case) on  pixel clock, although
> for its whole range the low limit for the frame rate for my camera is the
> same (0.10000).  I currently do not understand the system behind the error,
> will need to look at it closer.

It sounds like something is getting out of sync, but I'm not sure
where. I'll try and take a look at this next week - I happen to have a
uEye camera here but am waiting for the correct USB cable to be
delivered.

Best,
Mark

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

Mark Tsuchida-2
Hi Wenjamin,

On Thu, Jan 23, 2014 at 3:54 PM, Mark Tsuchida <[hidden email]> wrote:

> On Thu, Jan 23, 2014 at 11:06 AM, Wenjamin Rosenfeld
> <[hidden email]> wrote:
>> Mark, thePropertyLimits error seems to be tricky. When some lower limit for
>> e.g. frame rate (0.10000) is set, sometimes I can select this value without
>> error (or even lower value which is then automatically corrected) and
>> sometimes not. This seems to depend (in my case) on  pixel clock, although
>> for its whole range the low limit for the frame rate for my camera is the
>> same (0.10000).  I currently do not understand the system behind the error,
>> will need to look at it closer.
>
> It sounds like something is getting out of sync, but I'm not sure
> where. I'll try and take a look at this next week - I happen to have a
> uEye camera here but am waiting for the correct USB cable to be
> delivered.

You were right: an upper limit of 99.92475 was causing the issue,
because a property value of 99.92475 is truncated to 99.9248, which is
greater than the upper limit.

I've made a fix (r12694) so that the upper limit is reported as
99.9247 in such cases.

Thanks for finding this!

Best,
Mark

------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

mchon
Hi list,

First off, thanks for all your work on developing for the uEye cameras.

I am having an issue where micro-manager is unable to detect my uEye (UI-154x series) using the CFG file written by Wenjamin and I get the following message when I try to load the configuration:

"Error: failed to load hardware configuration.
Line 16: Property,Core,Intialize,1
Error in device "IDS uEye": uEye camera not found (103)"

My current configuration is:
Windows 7 64-bit Pro
uEye driver ver: 4.80.10.00 (64-bit)
micro-manager ver: 1.4.23, 64-bit (08/22/2016 nightly build)

I am 100% sure that the device drivers are installed, as I am able to operate the camera via the uEye Cockpit software without issue. I have tried an earlier driver version (4.40) and stable build of micro-manager (1.4.22). I am running into this same issue with MM 2.0 beta (08/22/2016 build). In every one of these configurations, I am able to use the camera in the Cockpit software.

One thing I noticed is that the camera shows up under "USB Controllers" in device manager instead of "Imaging devices". I recall reading in another thread that my device needs to show up under "Imaging Devices" in order for it to work with micro-manager. Can anyone confirm this and is there any way around this? I presume that where a device appears in the device tree is determined by its driver, but is it in any way possible to change the location of a device within Device manager?

Thanks in advance,

Michael
Reply | Threaded
Open this post in threaded view
|

Re: ueye usb cmos camera

Erwan C.
Hello Michael,

I was experiencing the same problem than you: an IDS uEye camera that could
be used with its native software but not found by MicroManager.
Then I read one of the notes in the wiki of the IDS uEye configuration file
for MicroManager: "If several cameras are connected, currently only the
first camera in the list will be addressed".
Because in the past, I have used my uEye camera on an setup with another IDS
camera, I thought that it was possible that its ID has been modified.
So I opened the IDS camera manager ( here
<https://en.ids-imaging.com/ids-camera-manager.html>   shown as example from
IDS website) and I saw that the Camera ID was set on 2 and its Device ID on
1 . After changing the Camera ID to 1 the uEye camera was finally found by
MicroManager.

I hope it will help you (even if it's a bit late...)

Erwan



--
Sent from: http://micro-manager.3463995.n2.nabble.com/


_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general