Issue with configuration NI device

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

Issue with configuration NI device

Micro-Manager mailing list

Hi All,

We try to use uManager for our experiment and started with Hardware configuration.

uManager 2.0 was installed on Windows 10. NI USB-6008 device was connected and NI MAX shows as Dev2.

Here are steps in uManager:

  • Launch Hardware Configuration Wizard
  • Create new configuration
  • Chose NI100X -> DigitalIO: NI digital IO
  • Click button “Add…” and “Device:DigitalIO; Library: NI100X” dialog shows up
  • Property AutoDetectedOutputPort allows to chose “Dev2/Port0”, “Dev2/Port1” or “Use custom”. This works because usage of another NI USB module as Dev1 shows “Dev1/Port0”, “Dev1/Port1” , “Dev1/Port2”  or “Use custom”.
  • Click button OK and message “Error in device “DigitalIO”: (Error message unavailable) (-200220) shows up

Changing of any property or “Device name” doesn’t help. The same story with NI100X -> AnalogIO.

 

Any suggestion?

 

Thanks!

 

 

 

 



_______________________________________________
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: Issue with configuration NI device

Nico Stuurman-2
Hi Liu,

> We try to use uManager for our experiment and started with Hardware
> configuration.
>
> uManager 2.0 was installed on Windows 10. NI USB-6008 device was
> connected and NI MAX shows as Dev2.
>
> Here are steps in uManager:
>
>   * Launch Hardware Configuration Wizard
>   * Create new configuration
>   * Chose NI100X -> DigitalIO: NI digital IO
>   * Click button “Add…” and “Device:DigitalIO; Library: NI100X” dialog
>     shows up
>   * Property AutoDetectedOutputPort allows to chose “Dev2/Port0”,
>     “Dev2/Port1” or “Use custom”. This works because usage of another
>     NI USB module as Dev1 shows “Dev1/Port0”, “Dev1/Port1” ,
>     “Dev1/Port2”  or “Use custom”.
>   * Click button OK and message “Error in device “DigitalIO”: (Error
>     message unavailable) (-200220) shows up
>
> Changing of any property or “Device name” doesn’t help. The same story
> with NI100X -> AnalogIO.
>

For what it is worth, I managed to reproduce the exact same problem with
a USB-6002 using 2 different versions of NiDaqmx (19.5 and 18.0, this is
a beast to install b.t.w., takes about an hour or so...).  The NI
documentation of NiDaqmx 18.0 does not list error -200220, but I assume
that it is related to using a USB device. Next step would be to debug
the device adapter code, figure out when the NI code returns this error
code, but I do not have the luxury to spend my time on that.  Hopefully
someone here has advice, or you could ask NI to trouble shoot this for you.

Best,


Nico



_______________________________________________
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: Issue with configuration NI device

Micro-Manager mailing list
Hi Nico,

I also tried old NI USB-6008 device. Does any NI device work fine for you?

Here is -200220 error explanation https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019PCxSAM&l=en-US 
All NI errors could be find from this link http://digital.ni.com/public.nsf/allkb/01d50d3f86ee67d8862576cf00745e78/$FILE/NI-DAQmxErrorCodes.PDF

Thanks, Andrey.

-----Original Message-----
From: Nico Stuurman <[hidden email]>
Sent: Friday, January 3, 2020 10:44 AM
To: Micro-Manager General <[hidden email]>
Subject: Re: [micro-manager-general] Issue with configuration NI device

Hi Liu,

> We try to use uManager for our experiment and started with Hardware
> configuration.
>
> uManager 2.0 was installed on Windows 10. NI USB-6008 device was
> connected and NI MAX shows as Dev2.
>
> Here are steps in uManager:
>
>   * Launch Hardware Configuration Wizard
>   * Create new configuration
>   * Chose NI100X -> DigitalIO: NI digital IO
>   * Click button "Add." and "Device:DigitalIO; Library: NI100X" dialog
>     shows up
>   * Property AutoDetectedOutputPort allows to chose "Dev2/Port0",
>     "Dev2/Port1" or "Use custom". This works because usage of another
>     NI USB module as Dev1 shows "Dev1/Port0", "Dev1/Port1" ,
>     "Dev1/Port2"  or "Use custom".
>   * Click button OK and message "Error in device "DigitalIO": (Error
>     message unavailable) (-200220) shows up
>
> Changing of any property or "Device name" doesn't help. The same story
> with NI100X -> AnalogIO.
>

For what it is worth, I managed to reproduce the exact same problem with a USB-6002 using 2 different versions of NiDaqmx (19.5 and 18.0, this is a beast to install b.t.w., takes about an hour or so...).  The NI documentation of NiDaqmx 18.0 does not list error -200220, but I assume that it is related to using a USB device. Next step would be to debug the device adapter code, figure out when the NI code returns this error code, but I do not have the luxury to spend my time on that.  Hopefully someone here has advice, or you could ask NI to trouble shoot this for you.

Best,


Nico



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


_______________________________________________
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: Issue with configuration NI device

Nico Stuurman-2
On 1/3/20 3:29 PM, Liyu, Andrey V via micro-manager-general wrote:
> I also tried old NI USB-6008 device. Does any NI device work fine for you?
I never willingly work with NI devices.  Their interface was (and
apparently still is)  such a horrendous spaghetti monster that I wrote
the Arduino device firmware and adapter in about a day after struggling
with the NI interface for more than a week.  This error description
points to something similar horrible going on.  It needs more knowledge
on the NI side of things (for instance, what is Traditional NI-DAQ and
what is NI-DAQmx, and why does that latter thing need an hour to
install?), but I have the feeling that there is a simple solution... Not
very helpful if I don't know what it is.

Nevertheless, others surely have had success with NI devices, certainly
with PCIe-based boards, but I thought that the USB-based devices also
used to work.

Best,

Nico





>
> Here is -200220 error explanation https://urldefense.proofpoint.com/v2/url?u=https-3A__knowledge.ni.com_KnowledgeArticleDetails-3Fid-3DkA00Z0000019PCxSAM-26l-3Den-2DUS&d=DwIFAw&c=iORugZls2LlYyCAZRB3XLg&r=UwP8SWqih8VHO1LwZpgcx83I4o21yLj6V6QD-25Dt4I&m=J7nNb2nTJ2e2hWaWNXugXM95JwmeoqORYtnJjwjhu5M&s=8m_FRhuJa47Rkc3w-nTthcE78RzUexp2IS6__ofeDWQ&e=
> All NI errors could be find from this link https://urldefense.proofpoint.com/v2/url?u=http-3A__digital.ni.com_public.nsf_allkb_01d50d3f86ee67d8862576cf00745e78_-24FILE_NI-2DDAQmxErrorCodes.PDF&d=DwIFAw&c=iORugZls2LlYyCAZRB3XLg&r=UwP8SWqih8VHO1LwZpgcx83I4o21yLj6V6QD-25Dt4I&m=J7nNb2nTJ2e2hWaWNXugXM95JwmeoqORYtnJjwjhu5M&s=C9YiJyCl5dCHYFFoYQ606oifJ0BWdBj-4FgXka88ccc&e=
>
> Thanks, Andrey.
>
> -----Original Message-----
> From: Nico Stuurman <[hidden email]>
> Sent: Friday, January 3, 2020 10:44 AM
> To: Micro-Manager General <[hidden email]>
> Subject: Re: [micro-manager-general] Issue with configuration NI device
>
> Hi Liu,
>
>> We try to use uManager for our experiment and started with Hardware
>> configuration.
>>
>> uManager 2.0 was installed on Windows 10. NI USB-6008 device was
>> connected and NI MAX shows as Dev2.
>>
>> Here are steps in uManager:
>>
>>    * Launch Hardware Configuration Wizard
>>    * Create new configuration
>>    * Chose NI100X -> DigitalIO: NI digital IO
>>    * Click button "Add." and "Device:DigitalIO; Library: NI100X" dialog
>>      shows up
>>    * Property AutoDetectedOutputPort allows to chose "Dev2/Port0",
>>      "Dev2/Port1" or "Use custom". This works because usage of another
>>      NI USB module as Dev1 shows "Dev1/Port0", "Dev1/Port1" ,
>>      "Dev1/Port2"  or "Use custom".
>>    * Click button OK and message "Error in device "DigitalIO": (Error
>>      message unavailable) (-200220) shows up
>>
>> Changing of any property or "Device name" doesn't help. The same story
>> with NI100X -> AnalogIO.
>>
> For what it is worth, I managed to reproduce the exact same problem with a USB-6002 using 2 different versions of NiDaqmx (19.5 and 18.0, this is a beast to install b.t.w., takes about an hour or so...).  The NI documentation of NiDaqmx 18.0 does not list error -200220, but I assume that it is related to using a USB device. Next step would be to debug the device adapter code, figure out when the NI code returns this error code, but I do not have the luxury to spend my time on that.  Hopefully someone here has advice, or you could ask NI to trouble shoot this for you.
>
> Best,
>
>
> Nico
>
>
>
> _______________________________________________
> micro-manager-general mailing list
> [hidden email]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_micro-2Dmanager-2Dgeneral&d=DwIFAw&c=iORugZls2LlYyCAZRB3XLg&r=UwP8SWqih8VHO1LwZpgcx83I4o21yLj6V6QD-25Dt4I&m=J7nNb2nTJ2e2hWaWNXugXM95JwmeoqORYtnJjwjhu5M&s=8cJVfSPXGrIicDpQnCVJWGEOGmMd3sRSgdPjwd4Xprw&e=
>
>
> _______________________________________________
> micro-manager-general mailing list
> [hidden email]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_micro-2Dmanager-2Dgeneral&d=DwIFAw&c=iORugZls2LlYyCAZRB3XLg&r=UwP8SWqih8VHO1LwZpgcx83I4o21yLj6V6QD-25Dt4I&m=J7nNb2nTJ2e2hWaWNXugXM95JwmeoqORYtnJjwjhu5M&s=8cJVfSPXGrIicDpQnCVJWGEOGmMd3sRSgdPjwd4Xprw&e=
> .



_______________________________________________
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: Issue with configuration NI device

Micro-Manager mailing list
        Thank you for explanation.
        NI had weird things during long history but I do like NI devices and drivers because NI supports wide signal variety with unification and it is easy to develop different data acquisition and controls. Usually, programs (LabVIEW, C#, etc.) don't care about device type and interface if device supports such signal.
        We have connected Thorlabs camera and Zaber stage. At this moment, we will need to check how uManager will find centers of cells and be able autofocusing. If those would work we will need to write our library due tricky synchronization of few devices. It is doubtful that NI100 is able to support that. Maybe I will have a chance to look into NI error ...

        Have a nice evening - Andrey.


-----Original Message-----
From: Nico Stuurman <[hidden email]>
Sent: Friday, January 3, 2020 3:46 PM
To: Micro-Manager General <[hidden email]>
Subject: Re: [micro-manager-general] Issue with configuration NI device

On 1/3/20 3:29 PM, Liyu, Andrey V via micro-manager-general wrote:
> I also tried old NI USB-6008 device. Does any NI device work fine for you?
I never willingly work with NI devices.  Their interface was (and apparently still is)  such a horrendous spaghetti monster that I wrote the Arduino device firmware and adapter in about a day after struggling with the NI interface for more than a week.  This error description points to something similar horrible going on.  It needs more knowledge on the NI side of things (for instance, what is Traditional NI-DAQ and what is NI-DAQmx, and why does that latter thing need an hour to install?), but I have the feeling that there is a simple solution... Not very helpful if I don't know what it is.

Nevertheless, others surely have had success with NI devices, certainly with PCIe-based boards, but I thought that the USB-based devices also used to work.

Best,

Nico





>
> Here is -200220 error explanation
> https://urldefense.proofpoint.com/v2/url?u=https-3A__knowledge.ni.com_
> KnowledgeArticleDetails-3Fid-3DkA00Z0000019PCxSAM-26l-3Den-2DUS&d=DwIF
> Aw&c=iORugZls2LlYyCAZRB3XLg&r=UwP8SWqih8VHO1LwZpgcx83I4o21yLj6V6QD-25D
> t4I&m=J7nNb2nTJ2e2hWaWNXugXM95JwmeoqORYtnJjwjhu5M&s=8m_FRhuJa47Rkc3w-n
> TthcE78RzUexp2IS6__ofeDWQ&e= All NI errors could be find from this
> link
> https://urldefense.proofpoint.com/v2/url?u=http-3A__digital.ni.com_pub
> lic.nsf_allkb_01d50d3f86ee67d8862576cf00745e78_-24FILE_NI-2DDAQmxError
> Codes.PDF&d=DwIFAw&c=iORugZls2LlYyCAZRB3XLg&r=UwP8SWqih8VHO1LwZpgcx83I
> 4o21yLj6V6QD-25Dt4I&m=J7nNb2nTJ2e2hWaWNXugXM95JwmeoqORYtnJjwjhu5M&s=C9
> YiJyCl5dCHYFFoYQ606oifJ0BWdBj-4FgXka88ccc&e=
>
> Thanks, Andrey.
>
> -----Original Message-----
> From: Nico Stuurman <[hidden email]>
> Sent: Friday, January 3, 2020 10:44 AM
> To: Micro-Manager General
> <[hidden email]>
> Subject: Re: [micro-manager-general] Issue with configuration NI
> device
>
> Hi Liu,
>
>> We try to use uManager for our experiment and started with Hardware
>> configuration.
>>
>> uManager 2.0 was installed on Windows 10. NI USB-6008 device was
>> connected and NI MAX shows as Dev2.
>>
>> Here are steps in uManager:
>>
>>    * Launch Hardware Configuration Wizard
>>    * Create new configuration
>>    * Chose NI100X -> DigitalIO: NI digital IO
>>    * Click button "Add." and "Device:DigitalIO; Library: NI100X" dialog
>>      shows up
>>    * Property AutoDetectedOutputPort allows to chose "Dev2/Port0",
>>      "Dev2/Port1" or "Use custom". This works because usage of another
>>      NI USB module as Dev1 shows "Dev1/Port0", "Dev1/Port1" ,
>>      "Dev1/Port2"  or "Use custom".
>>    * Click button OK and message "Error in device "DigitalIO": (Error
>>      message unavailable) (-200220) shows up
>>
>> Changing of any property or "Device name" doesn't help. The same
>> story with NI100X -> AnalogIO.
>>
> For what it is worth, I managed to reproduce the exact same problem with a USB-6002 using 2 different versions of NiDaqmx (19.5 and 18.0, this is a beast to install b.t.w., takes about an hour or so...).  The NI documentation of NiDaqmx 18.0 does not list error -200220, but I assume that it is related to using a USB device. Next step would be to debug the device adapter code, figure out when the NI code returns this error code, but I do not have the luxury to spend my time on that.  Hopefully someone here has advice, or you could ask NI to trouble shoot this for you.
>
> Best,
>
>
> Nico
>
>
>
> _______________________________________________
> micro-manager-general mailing list
> [hidden email]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge
> .net_lists_listinfo_micro-2Dmanager-2Dgeneral&d=DwIFAw&c=iORugZls2LlYy
> CAZRB3XLg&r=UwP8SWqih8VHO1LwZpgcx83I4o21yLj6V6QD-25Dt4I&m=J7nNb2nTJ2e2
> hWaWNXugXM95JwmeoqORYtnJjwjhu5M&s=8cJVfSPXGrIicDpQnCVJWGEOGmMd3sRSgdPj
> wd4Xprw&e=
>
>
> _______________________________________________
> micro-manager-general mailing list
> [hidden email]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge
> .net_lists_listinfo_micro-2Dmanager-2Dgeneral&d=DwIFAw&c=iORugZls2LlYy
> CAZRB3XLg&r=UwP8SWqih8VHO1LwZpgcx83I4o21yLj6V6QD-25Dt4I&m=J7nNb2nTJ2e2
> hWaWNXugXM95JwmeoqORYtnJjwjhu5M&s=8cJVfSPXGrIicDpQnCVJWGEOGmMd3sRSgdPj
> wd4Xprw&e=
> .



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

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