<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head>
<meta charset="utf-8">
<style>body{font-family:-apple-system,Helvetica,Arial,sans-serif;}blockquote{margin:0;padding:0 0 0 12px;border-left:1px solid #aaa;color:#aaa;}hr.unibox-forward{border:0;color:#888;background-color:#888;height:1px;}</style>
</head>
<body>
<div>Hi Alexis,</div>
<div><br></div>
<div>unfortunately, the corelog doesn’t shed too much light onto the problem.</div>
<div>However, you could do the following:</div>
<div><br></div>
<div>1) Update to a more recent MM version (corelog indicates you’re using 1.4.18, which is a little dated… the problem may have been fixed in the meantime).</div>
<div><br></div>
<div>2) Try narrowing the problem down to a specific device by creating a config where you replace stage, shutter, cam one-by-one with the respective option from the DemoCamera class and see if that config works.</div>
<div><br></div>
<div>cheers!</div>
<div><br></div>
<div>ulrik</div>
<blockquote type="cite" class="unibox-hidden">
<div>On Nov 18, 2016, at 12:55 PM, Alexis Maizel <alexis.maizel@cos.uni-heidelberg.de> wrote:</div>
<div><br></div>
<div style="font-family: -webkit-standard; font-variant-caps: normal;">Sorry for the missing CoreLog… here it is.<br>It happens in general.</div>
<div style="font-family: -webkit-standard; font-variant-caps: normal;"><br></div>
<div style="font-family: -webkit-standard; font-variant-caps: normal;">Best,</div>
<div style="font-family: -webkit-standard; font-variant-caps: normal;"><br></div>
<div style="font-family: -webkit-standard; font-variant-caps: normal;">Alexis</div>
<div style="font-family: -webkit-standard; font-variant-caps: normal;"><br></div>
<div style="font-family: -webkit-standard; font-variant-caps: normal;"></div>
<blockquote style="font-family: -webkit-standard; font-variant-caps: normal;">
<div><br></div>
<div>On 18 Nov 2016, at 11:40, Ulrik Günther <guenther@mpi-cbg.de> wrote:</div>
<div><br></div>
<div>Hi Alexis,</div>
<div><br></div>
<div>does this only happen with certain imaging configurations, or in general when using Multi-D?<br>Also, the corelog is not attached to your email (only your GPG signature). Could you resend it please?</div>
<div><br></div>
<div>cheers!</div>
<div><br></div>
<div>ulrik</div>
<div><br></div>
<div></div>
<div><br></div>
<div>—<br>Ulrik Günther, Dipl.-Phys.<br>PhD Student<br>MOSAIC Group & Tomancak Lab, Center of Systems Biology Dresden<br>Max Planck Institute of Molecular Cell Biology and Genetics<br>Pfotenhauerstr. 108, D-01307 Dresden, Germany</div>
<blockquote>
<div><br></div>
<div>On Nov 18, 2016, at 11:33 AM, Alexis Maizel <alexis.maizel@cos.uni-heidelberg.de> wrote:</div>
<div><br></div>
<div>Hi everyone,</div>
<div><br></div>
<div>I recently exchanged the computer driving our T-openSPIM. On the new computer, almost everything is working perfectly. Very strangely, I get an error when I want to trigger an image acquisition using MicroManager’s "Multi-Dimensional Acquisition” module: "Error in device "Cobolt": Invalid state (position) requested (12)”.<br>I have no problem to acquire image otherwise (live mode, SPIMAcquisition plugin). The problem only seems to be with the MM MultiD module.</div>
<div><br></div>
<div>I attach the Corelog.</div>
<div><br></div>
<div>I have of course, created a brand new config file and reinstalled the drivers for the laser but that did not solve the issue. I am totally clueless, as this config had been working seamlessly for ages. When migrating to the new computer I took care of zipping Fiji/MM bundle and transfer it "as is” to the new machine.</div>
<div><br></div>
<div>If anyone has an idea of what could have gone wrong…</div>
</blockquote>
</blockquote>
<blockquote style="font-family: -webkit-standard; font-variant-caps: normal;">
<div></div>
<blockquote>
<div><br></div>
<div>Many thanks in advance.</div>
<div><br></div>
<div></div>
<div><br></div>
<div></div>
<div><br></div>
<div></div>
<div><br></div>
<div>—<br>Prof. Dr. Alexis Maizel<br>Developmental Plasticity in Plants<br>Center for Organismal Studies<br>University of Heidelberg<br>Im Neuenheimer Feld 230<br>69120 Heidelberg<br>Germany</div>
<div><br></div>
<div>Office: +49 6221 54 64 56<br>Fax: +49 6221 54 64 24<br>Cell: +49 151 40 10 23 28<br>Email: alexis.maizel@cos.uni-heidelberg.de<br>URL: www.maizel-lab.org<br>Orcid: http://orcid.org/0000-0001-6843-1059<br>_______________________________________________<br>OpenSPIM mailing list<br>OpenSPIM@openspim.org<br>http://openspim.org/mailman/listinfo/openspim</div>
</blockquote>
</blockquote>
<div style="font-family: -webkit-standard; font-variant-caps: normal;"><br></div>
<div style="font-family: -webkit-standard; font-variant-caps: normal;"></div>
<div style="font-family: -webkit-standard; font-variant-caps: normal;">_______________________________________________<br>OpenSPIM mailing list<br>OpenSPIM@openspim.org<br>http://openspim.org/mailman/listinfo/openspim</div>
</blockquote>
</body>
</html>