pE4000 Coolled issue

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

pE4000 Coolled issue

Jean-Michel Peyrin
Hello,

While trying to control a pE4000 Coolled device on a Win7 Pro 32 bit PC
we noticed a consistents bugs that looks intrinsic to the device adapter.

1) pE4000 controls dramatically slows down Micromanager when using (as
suggested) the default port COM value in the hardware Configuration
Wizard. Shifting "port timeout" to 15ms instead of 500ms seems to
ameliorates the situation (yet this sometime generates a time ou error
message when launching). Checking the corelog file consistently shows an
Error message on the Coolled COM port no matter the timeout is set to
15ms or 500 ms. As suggested in a previous message from the mailing list
we launches MM as administrator, and shutted down any Win7 energy saving
preset (especially on COM port)

2) A major bug that prevent any utilization of pE4000 with Micromanager
is that the ON/OFF light control of pE4000 is not working. Inded, In the
Preset editor, turning the pE state to "1" actually turns the light (and
state) ON on the pE control PAD, yet the "PreciExcite-State" in
Micromanager control windows will consistently returns to "0".

3)  Changing wavelengths in the same LED channel is not possible.

COOLLED technical service returned me that the problems arise for the
fact that the driver was written for the pE2 – an earlier system – and
the pE4000 was modified to work with this driver, but it is not ideal,
especially on 32 bits PC.  According to them 64 bits PC may solves some,
but not all  of theses issue, and they cannot fix these issues.

Does anyone encountered these problem and found a solution for those.

Thank you very much for your help

JM


------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________
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: pE4000 Coolled issue

sjunek
Dear all,

I encountered the same issues that Jean-Michel described (see below) and
was wondering whether there's any solution, in particular to the lack of
control over switching the light on/off (point 2 below - arguably the
most important control and one of the main reasons to use a LED light
source).

Any suggestions are welcome!

Many thanks
Stephan

Am 01.12.2015 um 10:36 schrieb Jean-Michel Peyrin:

> Hello,
>
> While trying to control a pE4000 Coolled device on a Win7 Pro 32 bit PC
> we noticed a consistents bugs that looks intrinsic to the device adapter.
>
> 1) pE4000 controls dramatically slows down Micromanager when using (as
> suggested) the default port COM value in the hardware Configuration
> Wizard. Shifting "port timeout" to 15ms instead of 500ms seems to
> ameliorates the situation (yet this sometime generates a time ou error
> message when launching). Checking the corelog file consistently shows an
> Error message on the Coolled COM port no matter the timeout is set to
> 15ms or 500 ms. As suggested in a previous message from the mailing list
> we launches MM as administrator, and shutted down any Win7 energy saving
> preset (especially on COM port)
>
> 2) A major bug that prevent any utilization of pE4000 with Micromanager
> is that the ON/OFF light control of pE4000 is not working. Inded, In the
> Preset editor, turning the pE state to "1" actually turns the light (and
> state) ON on the pE control PAD, yet the "PreciExcite-State" in
> Micromanager control windows will consistently returns to "0".
>
> 3)  Changing wavelengths in the same LED channel is not possible.
>
> COOLLED technical service returned me that the problems arise for the
> fact that the driver was written for the pE2 – an earlier system – and
> the pE4000 was modified to work with this driver, but it is not ideal,
> especially on 32 bits PC.  According to them 64 bits PC may solves some,
> but not all  of theses issue, and they cannot fix these issues.
>
> Does anyone encountered these problem and found a solution for those.
>
> Thank you very much for your help
>
> JM
>
>
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
> _______________________________________________
> micro-manager-general mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/micro-manager-general

--
________________________________________

Dr. Stephan Junek
Head of the imaging facility
Max Planck Institute for Brain Research
Max-von-Laue-Str. 4
60438 Frankfurt am Main
Germany

[hidden email]
T: +49 69 850033 – 2531 (Office)
T: +49 69 850033 – 1409 (Lab)
F: +49 69 850033 – 2102


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
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: pE4000 Coolled issue

k.de_vos@sheffield.ac.uk
In reply to this post by Jean-Michel Peyrin
I am running on 64-bit and don't have an on-off problem.
I do however don't see how to make a preset for all wavelenghts, the only ones showing are the ones selected on the pad (with pre 1-4) at startup of MM.
Is there any way to change the Pre1-4 using MM?

Kurt
Reply | Threaded
Open this post in threaded view
|

Re: pE4000 Coolled issue

Bruno
Hi all,

I am running the pE4000 on MM 1.4.23 via MATLAB 2018b

When I run time series experiments eventually MATLAB freezes and the corelog
clearly shows that there is a TIMEOUT issue with the pE4000, see below.
Did any of you solve this timeout issue or had the same?
When running MM not from MATLAB but directly, it works fine.

Best,
Bruno


COM15 is the pE4000 in my case
2019-10-03T13:12:10.179434 tid8708 [IFO,Core] Default shutter set to pE4000
2019-10-03T13:12:10.734434 tid3808 [IFO,dev:COM15] TERM_TIMEOUT error
occured!
2019-10-03T13:12:10.734434 tid3808 [ERR,Core] Error occurred in device
COM15: Error in device "COM15": (Error message unavailable) (107)
2019-10-03T13:12:11.234434 tid3808 [IFO,dev:COM15] TERM_TIMEOUT error
occured!
2019-10-03T13:12:11.234434 tid3808 [ERR,Core] Error occurred in device
COM15: Error in device "COM15": (Error message unavailable) (107)



--
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
Reply | Threaded
Open this post in threaded view
|

Re: pE4000 Coolled issue

nanthony
Hi Bruno,

I'm not sure if this is the cause of your issue but I have found that sometimes issues that only occur when micromanager is run from MATLAB can be caused by MATLAB not allocating enough memory for Java.

Try following these directions and see if your problem is solved. https://www.mathworks.com/help/matlab/matlab_external/java-heap-memory-preferences.html

If you continue to have problems I would recommend updating to Micromanager 2.0 Gamma.

--Nick

-----Original Message-----
From: Bruno <[hidden email]>
Sent: Monday, October 7, 2019 7:51 AM
To: [hidden email]
Subject: Re: [micro-manager-general] pE4000 Coolled issue

Hi all,

I am running the pE4000 on MM 1.4.23 via MATLAB 2018b

When I run time series experiments eventually MATLAB freezes and the corelog clearly shows that there is a TIMEOUT issue with the pE4000, see below.
Did any of you solve this timeout issue or had the same?
When running MM not from MATLAB but directly, it works fine.

Best,
Bruno


COM15 is the pE4000 in my case
2019-10-03T13:12:10.179434 tid8708 [IFO,Core] Default shutter set to pE4000
2019-10-03T13:12:10.734434 tid3808 [IFO,dev:COM15] TERM_TIMEOUT error occured!
2019-10-03T13:12:10.734434 tid3808 [ERR,Core] Error occurred in device
COM15: Error in device "COM15": (Error message unavailable) (107)
2019-10-03T13:12:11.234434 tid3808 [IFO,dev:COM15] TERM_TIMEOUT error occured!
2019-10-03T13:12:11.234434 tid3808 [ERR,Core] Error occurred in device
COM15: Error in device "COM15": (Error message unavailable) (107)



--
Sent from: https://urldefense.proofpoint.com/v2/url?u=http-3A__micro-2Dmanager.3463995.n2.nabble.com_&d=DwICAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=VOzx3RPoFiAnEjWZNVKllozJBWVHbhKhbit0V1WrFG2kkO7riI9lwQ0usSmhFkzq&m=wLhNSLTR_bkTHKOPsibIoXNfF-en-lRiiERMM97NhQ0&s=pBIdEnXoiBETk_bN7yYlCi_Fg7rVV0aBXjjgvLai3i4&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=DwICAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=VOzx3RPoFiAnEjWZNVKllozJBWVHbhKhbit0V1WrFG2kkO7riI9lwQ0usSmhFkzq&m=wLhNSLTR_bkTHKOPsibIoXNfF-en-lRiiERMM97NhQ0&s=T_Lt-rLzh0iuBBr_804vtFRN0_JIWPZyUDxyCh7_e4s&e= 


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