micromanager "reboot" error

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

micromanager "reboot" error

StevenF
Hello micromanager community,

I have encountered various frustrating errors when i need to "reboot"
micromanager. To explain a bit i am using micromanager's python API for my
acquisitions at the moment but i do all my "setup" using the GUI. So things
go like this :

1)Launch GUI
2)Setup Acquisition parameters and find Positions
3)Close GUI
4)Launch my custom script using the same configuration.

Unfortunately i have witnessed some errors upon trying to launch the 4th
step. These errors don't always appear but seem to be more and more
frequent. Needless to say but they are very frustrating to encounter and i
can't really find an explanation as to why they occur.

*typical error:*
/"Traceback (most recent call last):
 
File ".\core_threader.py", line 393, in <module>
    event=False)
#etiher False or events_list
  File ".\core_threader.py", line 100,
in __init__
    mmconfiguarion =
mms.Loader(micromanager_paramters['micromanagerlocation'],
micromanager_paramters['mmconfig'], self.folder_manager_obj)
 
File "C:\Users\lifeware\workspace\MMwrapper\scripting.py", line 41,
in __init__
    self.mmc.loadSystemConfiguration(configurationPath)
 
File "C:\Program Files\Micro-Manager-1.423.nightlyTEST\MMCorePy.py", line
3648,
in loadSystemConfiguration
   
return _MMCorePy.CMMCore_loadSystemConfiguration(self, *args)
MMCorePy.CMMError: Line 85:
Property,Core,Initialize,1
Error in device "Scope": (Error message unavailable) (10012)" /


in order to resolve the error i can :
1) brute force it by relaunching as many times as it takes to work which it
eventually does
2) reboot the microscope

I am using a Leica DMI8 microscope.

If you need further info i can provide more.

Thanks in advance,

Steven



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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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: micromanager "reboot" error

Kyle Douglass-2
Hi Steven,

Have you taken a look at the CoreLogs to see whether there is more information there? On Windows, these are usually stored in C:\Program Files\Micro-Manager\CoreLogs (change the first part to point to your MM folder).

You can also make the logging more verbose for debugging. In the GUI, you would navigate to Tools > Options... and then check "Enable debug logging". I'm not sure how you would enable debug logging via the Python API, but there is likely a method to do so.

Write back if you find anything more descriptive about your error.

Cheers,
Kyle

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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: micromanager "reboot" error

StevenF
CoreLog20180601T095626_pid10556.txt
<http://micro-manager.3463995.n2.nabble.com/file/t396958/CoreLog20180601T095626_pid10556.txt>  

so here is a Corelogs file with some details, its hard for me to understand
where this error is coming from.

Thanks in advance,

Steven



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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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: micromanager "reboot" error

Kyle Douglass-2
Hi Steven,

On Fri, Jun 1, 2018 at 10:13 AM, StevenF <[hidden email]> wrote:

so here is a Corelogs file with some details, its hard for me to understand
where this error is coming from.


I'm sorry but I do not know the cause of this error. Looking at the CoreLog, it appears that the key part starts at the following line:
2018-06-01T09:56:40.711970 tid10424 [dbg,dev:COM10] Read <- (hex) ...

After reading a few byte strings, the device adapter then sends a few commands over the COM port and retrieves the response from the microscope's serial port buffer.

2018-06-01T09:56:40.715472 tid10424 [dbg,dev:COM10] SetCommand -> 70001\r 2018-06-01T09:56:40.737973 tid10424 [dbg,dev:COM10] GetAnswer <- $48023 31024.0700\r 2018-06-01T09:56:40.737973 tid10424 [dbg,dev:COM10] SetCommand -> 70001\r 2018-06-01T09:56:40.737973 tid10424 [dbg,dev:COM10] GetAnswer <- 70001 DMI8 40 48 50 58 59 70 71 74 76 77 78 80 82 83 84 86 98\r 2018-06-01T09:56:40.737973 tid10424 [dbg,dev:COM10] SetCommand -> 70002\r 2018-06-01T09:56:40.756997 tid10424 [dbg,dev:COM10] GetAnswer <- 70001 DMI8 40 48 50 58 59 70 71 74 76 77 78 80 82 83 84 86 98\r 2018-06-01T09:56:40.756997 tid10424 [ERR,Core:dev:Scope] Error in device "Scope": (Error message unavailable) (10012)

Since the error occurs during serial port communications, I would focus my debugging efforts around this part. I am by no means an expert on this topic, so these suggestions might be a bit naive (maybe someone else could help):

- Check that the baud rate and terminating characters are set correctly for the microscope's device adapter in Micro-Manager's hardware configuration wizard
- Check that the baud rate is set correctly in the Windows device manager (I don't think this really matters, but it's worth a shot)
- Try a different USB port
- Try sending the same serial commands to the microscope via another program, such as the Arduinio IDE's serial port console. If you can reproduce the bug, then the problem is likely to be isolated to serial communications with the scope.
- Try using a port sniffer to monitor the messages being sent over the COM port and verify that they match the microscope's serial port API

I hope that one of these suggestions points you in the right direction, or that someone else can chime in with suggestions.
Cheers,
Kyle


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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: micromanager "reboot" error

StevenF
Thanks for the suggestions Kyle!

i'll be trying to debug this error, the issue is that its pretty
inconsistent as in sometimes it'll happen, other times it wont with it being
very frequent lately. Anyway ill see if i can solve the issue!

Cheers,

Steven



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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general