<div dir="ltr"><div>Hi everyone, <br></div>Today, while looking at my calibration grid, I find that the x, y,and z stages behave normally, but that the rotation stage is acting odd. I can't rotate only one step; the stage doesn't move unless I click two steps. Also, the numbers that show up in the angle readout box are surprising; the angle changes in steps of 3.24 instead of 1.8, so it goes from 0 to 3.24, then 6.48, etc. The information in the configuration file seems to be correct, and the stage reacts normally to the Picard controller. <br>
<div>Any ideas? No error appears in my core log. </div><div>Thanks, <br>Aurelia</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 2, 2014 at 10:55 PM, <span dir="ltr"><<a href="mailto:openspim-request@openspim.org" target="_blank">openspim-request@openspim.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send OpenSPIM mailing list submissions to<br>
<a href="mailto:openspim@openspim.org">openspim@openspim.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://openspim.org/mailman/listinfo/openspim" target="_blank">http://openspim.org/mailman/listinfo/openspim</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:openspim-request@openspim.org">openspim-request@openspim.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:openspim-owner@openspim.org">openspim-owner@openspim.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of OpenSPIM digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: OpenSPIM Digest, Vol 14, Issue 20 (Aurelia Honerkamp-Smith)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 2 Jul 2014 16:04:24 +0100<br>
From: Aurelia Honerkamp-Smith <<a href="mailto:aureliaomega@gmail.com">aureliaomega@gmail.com</a>><br>
To: Luke Stuyvenberg <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>><br>
Subject: Re: [OpenSPIM] OpenSPIM Digest, Vol 14, Issue 20<br>
Message-ID:<br>
<CAHAw+8aj-ehCPEv-azUKx9nPGm2k6f=<a href="mailto:LBqiukZg-cdhquJdQvg@mail.gmail.com">LBqiukZg-cdhquJdQvg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi again,<br>
<br>
Yes, setting the pixel size lets the camera work again! I also had to<br>
switch the Picard serial numbers in the configuration file to their actual<br>
values, as I had switched them around initially to get the focus stage to<br>
be the correct one. The plugin is now functional. I can create a<br>
configuration file, start the SPIM plugin, then save it to get a pixel<br>
size. I still need to remove the extra COM3 line from the configuration<br>
file manually, and when I start live view there is a MicroManager error:<br>
Error:<br>
org.micromanager.MMStudioMainFrame.updateCenterAndDragListener(MMStudioMainFrame.java.2240)<br>
<br>
but when I dismiss it, everything seems to function normally. I am still<br>
getting sporadic Acquiring: null errors when I start acquisition, but that<br>
predated this change. Let me know if I should send any more info.<br>
Thanks very much Luke!<br>
<br>
Aurelia<br>
<br>
<br>
On Tue, Jul 1, 2014 at 7:12 PM, Luke Stuyvenberg <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>><br>
wrote:<br>
<br>
> There certainly seems to be something odd about the camera adapter right<br>
> now. Specifically,<br>
><br>
> 2014-07-01T18:07:18.997408 tid6872 [IFO,dev:Camera-1] PVCAM API error:<br>
> "C0_CAM_NAME_NOT_FOUND This is not a valid name for opening the camera",<br>
> code: 14<br>
><br>
> Do you get this error opening only the live view, without starting the<br>
> SPIM Acquisition plugin? The core log seems to suggest that the camera<br>
> works fine until the plugin is launched. Most likely, when the plugin<br>
> defines an automatic pixel size, some sort of reset occurs in the core, but<br>
> the camera adapter doesn't tolerate it well (I feel like I've encountered<br>
> this issue before with a different camera adapter... I'll have to look into<br>
> this; it might be a report for the MM team to look at.). As a short-term<br>
> workaround, you can define a pixel size before launching the software,<br>
> using Tools -> Pixel Size Calibration. (If a pixel size is predefined, the<br>
> SPIM plugin won't try to add one.) After defining a pixel size, save the<br>
> configuration (Tools -> Save Configuration Settings As...) so you won't<br>
> need to re-make the pixel size definition each time.<br>
><br>
><br>
> Please try that workaround and let me know if you still have issues; I'll<br>
> add the immediate fixes on the update sites and see what I can do about<br>
> tracking down this bug.<br>
><br>
><br>
> Thanks!<br>
> Luke<br>
><br>
> On 07/01/14, Aurelia Honerkamp-Smith wrote:<br>
> > Hi again,<br>
> ><br>
> ><br>
> > Yep, the COM3 messages stop when I get rid of the extra line in the<br>
> configuration file. Oh! This is exciting! After I start up and load the<br>
> configuration file without the extra COM3 line, I can start the plugin, and<br>
> move the stage! However, when I try to start live view, I then get a<br>
> Micro-Manager error: "Error in device Camera-1: The device cannot set this<br>
> property at the moment." Trying to use Snap gives "Error Acquiring: null."<br>
> ><br>
> > Well, it was exciting for me anyhow. Another corelog is attached.<br>
> ><br>
> ><br>
> > Aurelia<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > On Tue, Jul 1, 2014 at 5:32 PM, Luke Stuyvenberg <<a href="mailto:aureliaomega@gmail.com">aureliaomega@gmail.com</a><br>
> <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>')" target="1"><a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>> wrote:<br>
> ><br>
> > > Hi Aurelia,<br>
> > ><br>
> > > > Thanks! I've replaced rsyntaxtextarea.jar. I can now configure<br>
> all 3 components, although I still get the COM3 error messages. The shutter<br>
> and camera then seem to function, but I can't start the SPIM plugin to<br>
> see if the stage is working. I don't get an error message that says my<br>
> setup is invalid, the plugin just fails to start. I attach the<br>
> configuration file that I have just made, and a corelog showing an attempt<br>
> to start the plugin.<br>
> > ><br>
> > > The COM3 error message is happening because of the duplicate line in<br>
> the configuration file -- though, if the configurator is generating this<br>
> file each time, there is probably an underlying issue that requires<br>
> investigation. (Unfortunately, it isn't obvious to me why this might<br>
> happen; finding this out could take time.) A quick fix would be to edit the<br>
> config file in a text editor and remove line 7 or 8<br>
> ("Device,COM3,SerialManager,COM3").<br>
> > ><br>
> > ><br>
> > > The SPIM plugin won't start because the stage configuration is<br>
> confusing it. Two possibilities: Either the COM3 error is leaving the<br>
> stages only partially initialized, so the stage position is invalid (out of<br>
> the stage's range, according to its properties), or a stage (usually<br>
> the twister) was left in a position outside its accepted range. Given the<br>
> PVCAM exception earlier in the CoreLog, I would assume the former -- but to<br>
> be sure, before starting the system, please try using the Picard software<br>
> to home the three linear stages and zero the rotational stage, leaving them<br>
> all inside the usual position range.<br>
> > ><br>
> > ><br>
> > > On 07/01/14, Aurelia Honerkamp-Smith wrote:<br>
> > > > My system info is:<br>
> > > ><br>
> > > > --------------- S Y S T E M ---------------<br>
> > > ><br>
> > > > OS: Windows 7 Build 7601 Service Pack 1<br>
> > > ><br>
> > > > CPU:total 12 (6 cores per cpu, 2 threads per core) family 6 model 45<br>
> stepping 7, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2,<br>
> popcnt, ht<br>
> > > ><br>
> > > > Memory: 4k page, physical 66506940k(61696496k free), swap<br>
> 133012024k(127977948k free)<br>
> > > ><br>
> > > > vm_info: Java HotSpot(TM) Client VM (19.1-b02) for windows-x86 JRE<br>
> (1.6.0_24-b07), built on Feb 2 2011 17:44:41 by "java_re" with MS VC++ 7.1<br>
> (VS2003)<br>
> > > ><br>
> > > ><br>
> > > > Is that the system information you need?<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > Yes, thank you! It doesn't reveal much about the problem, but at<br>
> the very least it confirms that the system should be working...<br>
> > ><br>
> > ><br>
> > > Just to keep track of what we've done so far (so I know what to<br>
> change in the next update):<br>
> > > - Updated mmgr_dal_SerialManager.dll and all system DALs to the latest<br>
> versions.<br>
> > > - Replaced rsyntaxtextarea.jar with Micro-Manager's preferred<br>
> version.<br>
> > ><br>
> > ><br>
> > > Nearly there, I think!<br>
> > > Luke<br>
> > ><br>
> > ><br>
> > > On 07/01/14, Aurelia Honerkamp-Smith wrote:<br>
> > > > Hi again,<br>
> > > ><br>
> > > ><br>
> > > > Thanks! I've replaced rsyntaxtextarea.jar. I can now configure<br>
> all 3 components, although I still get the COM3 error messages. The shutter<br>
> and camera then seem to function, but I can't start the SPIM plugin to<br>
> see if the stage is working. I don't get an error message that says my<br>
> setup is invalid, the plugin just fails to start. I attach the<br>
> configuration file that I have just made, and a corelog showing an attempt<br>
> to start the plugin. My system info is:<br>
> > > ><br>
> > > > --------------- S Y S T E M ---------------<br>
> > > ><br>
> > > > OS: Windows 7 Build 7601 Service Pack 1<br>
> > > ><br>
> > > > CPU:total 12 (6 cores per cpu, 2 threads per core) family 6 model 45<br>
> stepping 7, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2,<br>
> popcnt, ht<br>
> > > ><br>
> > > > Memory: 4k page, physical 66506940k(61696496k free), swap<br>
> 133012024k(127977948k free)<br>
> > > ><br>
> > > > vm_info: Java HotSpot(TM) Client VM (19.1-b02) for windows-x86 JRE<br>
> (1.6.0_24-b07), built on Feb 2 2011 17:44:41 by "java_re" with MS VC++ 7.1<br>
> (VS2003)<br>
> > > ><br>
> > > ><br>
> > > > Is that the system information you need?<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > ><br>
> > > > On Mon, Jun 30, 2014 at 7:37 PM, Luke Stuyvenberg <<br>
> <a href="http://openspim.org/mailman/listinfo/openspim(java_script:main.compose('new(java_script:main.compose('new(http://openspim.org/mailman/listinfo/openspim(java_script:main.compose('new(java_script:main.compose('new)'(java_script:main.compose('new(javascript:main.compose('new" target="_blank">http://openspim.org/mailman/listinfo/openspim(java_script:main.compose('new(java_script:main.compose('new(http://openspim.org/mailman/listinfo/openspim(java_script:main.compose('new(java_script:main.compose('new)'(java_script:main.compose('new(javascript:main.compose('new</a>',<br>
> 't=<a href="mailto:aureliaomega@gmail.com">aureliaomega@gmail.com</a>> <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a> <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>>')"<br>
> target="1"><a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a> <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>>> wrote:<br>
> > > ><br>
> > > > > Hi,<br>
> > > > ><br>
> > ><br>
> > > > > One further thought -- the Java error at the top of the log file<br>
> comes from a conflict in rsyntaxtextarea.jar (some e-mails on the MM<br>
> mailing list discuss this issue, and we're working on porting Fiji/IJ2<br>
> to a newer version of the jar) -- I expected that having these in conflict<br>
> would only disable the Micro-Manager script editor, but some testing<br>
> suggests it might be more disruptive than that. Another fix you can try<br>
> without waiting on me: From vanilla MM, copy:<br>
> "plugins/Micro-Manager/rsyntaxtextarea.jar" -> (in OpenSPIM.app)<br>
> "jars/rsyntaxtextarea.jar"; then, move, rename, or delete<br>
> "jars/rsyntaxtextarea-2.0.4.1.jar".<br>
> > > > ><br>
> > > > ><br>
> > > > > Thanks again,<br>
> > > > > Luke<br>
> > > > ><br>
> > > > > On 06/30/14, Luke Stuyvenberg wrote:<br>
> > > > > > Hi Aurelia,<br>
> > > > > ><br>
> > ><br>
> > > > > > Could you attach your configuration file, and report your system<br>
> specs (OS version/architecture) as well? The core log certainly seems to<br>
> suggest it is attempting to load COM3 multiple times (it also seems to<br>
> reset the serial port properties with each stage loaded from PicardStage),<br>
> but short of that, I'm still not entirely certain what's going on.<br>
> If the 24 June device adapters weren't correct, they probably<br>
> wouldn't load at all, so presumably you've already copied all the<br>
> right DLLs. (SerialManager and ThorlabsSC10 are self-contained, so just<br>
> those files should be enough to run those devices; PVCAM has an external<br>
> DLL, but your core log suggests the camera initializes without a problem.)<br>
> > > > > ><br>
> > > > > ><br>
> > > > > > Thanks,<br>
> > > > > > Luke<br>
> > > > > ><br>
> > > > > > On 06/30/14, Aurelia Honerkamp-Smith wrote:<br>
> > > > > > > Sorry, I meant to also say that I can't load individual<br>
> components, I get the same error messages about COM3. The only<br>
> configuration I can actually complete is the shutter on its own, but it<br>
> doesn't function.<br>
> > > > > > ><br>
> > > > > > ><br>
> > > > > > ><br>
> > > > > > ><br>
> > ><br>
> > > > > > > On Mon, Jun 30, 2014 at 6:55 PM, Aurelia Honerkamp-Smith <> ><br>
> > > > On Mon, Jun 30, 2014 at 6:01 PM, Luke Stuyvenberg <<br>
> <a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a> <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>> <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a> <<br>
> <a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>>>(java_script:main.compose()> wrote:<br>
> > > > > > > ><br>
> > > > > > > > > Hi Aurelia,<br>
> > > > > > > > ><br>
> > > > > > > > > On 06/30/14, Aurelia Honerkamp-Smith wrote:<br>
> > > > > > > > > > Thank you! I am still having a problem, probably because<br>
> I'm using a nonstandard setup. There seems to be a conflict in loading<br>
> my camera (a PVCam one) and the shutter I use to block the laser (Thorlabs<br>
> SC10); when I try to configure, I get a message "the specified label COM3<br>
> is already in use" before anything has been configured, and then several<br>
> times after I load both, one that says "Line8: device, COM3, serialmanager,<br>
> COM3." The shutter should be on COM3 but not the camera, and I don't<br>
> run into this conflict when I load both shutter and camera in the vanilla<br>
> MM from 24 June. I attach a core log showing an attempt to load shutter and<br>
> camera.<br>
> > > > > > > > ><br>
> > > > > > > > ><br>
> > > > > > > > ><br>
> > > > > > > > > Do the devices work individually in OpenSPIM? i.e. if only<br>
> one is loaded, do you ever get that message? It sounds like a problem with<br>
> the SerialManager, a device adapter which I hadn't updated -- you might<br>
> try pulling mmgr_dal_SerialManager.dll from the 24 June nightly build.<br>
> I'll also be looking into this.<br>
> > > > > > > > ><br>
> > > > > > > > ><br>
> > > > > > > > > On 06/30/14, Aurelia Honerkamp-Smith wrote:<br>
> > > > > > > > > > The Picard stage now appears in the list of available<br>
> hardware, but when I try to load all three the computer bluescreens.<br>
> > > > > > > > ><br>
> > > > > > > > ><br>
> > > > > > > > ><br>
> > > > > > > > > Load all three devices (camera, shutter, stage), or load<br>
> all three stages? Does it bluescreen reliably? (I've not seen/heard of<br>
> this happening before...)<br>
> > > > > > > > ><br>
> > > > > > > > ><br>
> > > > > > > > > I'll let you know what I work out. Thanks again!<br>
> > > > > > > > > Luke<br>
> > > > > > > > ><br>
> > > > > > > > ><br>
> > > > > > > > > On 06/30/14, Aurelia Honerkamp-Smith wrote:<br>
> > > > > > > > > > Hi Luke,<br>
> > > > > > > > > ><br>
> > > > > > > > > ><br>
> > > > > > > > ><br>
> > > > > > > > > > Thank you! I am still having a problem, probably because<br>
> I'm using a nonstandard setup. There seems to be a conflict in loading<br>
> my camera (a PVCam one) and the shutter I use to block the laser (Thorlabs<br>
> SC10); when I try to configure, I get a message "the specified label COM3<br>
> is already in use" before anything has been configured, and then several<br>
> times after I load both, one that says "Line8: device, COM3, serialmanager,<br>
> COM3." The shutter should be on COM3 but not the camera, and I don't<br>
> run into this conflict when I load both shutter and camera in the vanilla<br>
> MM from 24 June. I attach a core log showing an attempt to load shutter and<br>
> camera. The Picard stage now appears in the list of available hardware, but<br>
> when I try to load all three the computer bluescreens.<br>
> > > > > > > > > ><br>
> > > > > > > > > ><br>
> > > > > > > > > > Thanks again,<br>
> > > > > > > > > > Aurelia<br>
> > > > > > > > > ><br>
> > > > > > > > > ><br>
> > > > > > > > > ><br>
> > ><br>
> > > > > > > > > > On Mon, Jun 30, 2014 at 3:03 PM, Luke Stuyvenberg <<br>
> <a href="mailto:openspim@openspim.org">openspim@openspim.org</a> <<a href="mailto:openspim@openspim.org">openspim@openspim.org</a>> <<a href="mailto:openspim@openspim.org">openspim@openspim.org</a> <<br>
> <a href="mailto:openspim@openspim.org">openspim@openspim.org</a>>>(java_script:main.compose() <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a> <<br>
> <a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>> <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a> <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>>>(java_script:main.compose()')"<br>
> target="1"><a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a> <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>> <<br>
> <a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a> <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>>>(java_script:main.compose()><br>
> wrote:<br>
> > > > > > > > > ><br>
> > > > > > > > > > > Hi Aurelia,<br>
> > > > > > > > > > ><br>
> > > > > > > > ><br>
> > > > > > > > > > > Sorry about that; it seems a lot more had changed than<br>
> I had expected. I've updated the update site again, with a number of<br>
> changes (new MMCore, new versions of the device adapters). It tested okay<br>
> on my virtual machine, but if there's still a problem, please let me<br>
> know. If you run into other device adapter problems (i.e. not with<br>
> PicardStage), try getting updated device adapter versions from the nightly<br>
> build as of 24 June or so.<br>
> > > > > > > > > > ><br>
> > > > > > > > > > ><br>
> > > > > > > > > > > Thanks!<br>
> > > > > > > > > > > Luke<br>
> > > > > > > > > > ><br>
> > > > > > > > > > > On 06/29/14, Aurelia Honerkamp-Smith wrote:<br>
> > > > > > > > > > > > Hello,<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > > I am afraid that after updating to the newest<br>
> PicardStage dll, my previous configuration is unable to load the stage. I<br>
> get an error message:<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > > Line 8: Device,Picard Twister,PicardStage,Picard<br>
> Twister<br>
> > > > > > > > > > > > Failed to load device adapter "PicardStage" from<br>
> "C:\Users\ah659\Desktop\OPENSP~1\OpenSPIM.app\mm\win32\mmgr_dal_PicardStage.dll"<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > > Line 9: Device,Picard Z Stage,PicardStage,Picard Z<br>
> Stage<br>
> > > > > > > > > > > > Failed to load device adapter "PicardStage" from<br>
> "C:\Users\ah659\Desktop\OPENSP~1\OpenSPIM.app\mm\win32\mmgr_dal_PicardStage.dll"<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > > Line 10: Device,Picard XY Stage,PicardStage,Picard<br>
> XY Stage<br>
> > > > > > > > > > > > Failed to load device adapter "PicardStage" from<br>
> "C:\Users\ah659\Desktop\OPENSP~1\OpenSPIM.app\mm\win32\mmgr_dal_PicardStage.dll"<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > > Line 22: Property,Picard Twister,Serial Number,60<br>
> > > > > > > > > > > > No device with label "Picard Twister"<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > > Line 23: Property,Picard Z Stage,Serial Number,181<br>
> > > > > > > > > > > > No device with label "Picard Z Stage"<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > > Line 24: Property,Picard XY Stage,Serial Number<br>
> (X),182<br>
> > > > > > > > > > > > No device with label "Picard XY Stage"<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > > Line 25: Property,Picard XY Stage,Serial Number<br>
> (Y),180<br>
> > > > > > > > > > > > No device with label "Picard XY Stage"<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > > Line 26: Property,Picard XY Stage,X-Max,8000<br>
> > > > > > > > > > > > No device with label "Picard XY Stage"<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > > Line 27: Property,Picard XY Stage,X-Min,1<br>
> > > > > > > > > > > > No device with label "Picard XY Stage"<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > > Line 28: Property,Picard XY Stage,Y-Max,8000<br>
> > > > > > > > > > > > No device with label "Picard XY Stage"<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > > Line 29: Property,Picard XY Stage,Y-Min,1<br>
> > > > > > > > > > > > No device with label "Picard XY Stage"<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > > Line 44: Property,Core,Focus,Picard Z Stage<br>
> > > > > > > > > > > > Cannot set Core property Focus to invalid value<br>
> "Picard Z Stage"<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > ><br>
> > > > > > > > > > ><br>
> > > > > > > > > > ><br>
> > > > > > > > > > > > I can still load the camera and my shutter. The<br>
> Picard Stage now appears unavailable in the hardware configuration wizard.<br>
> I am also using 32-bit Fiji on a 64-bit machine, but haven't had<br>
> trouble loading the stage before (it appeared to work normally, with the<br>
> exception of the occasional communication delay that I mentioned earlier).<br>
> I attach a core log.<br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > ><br>
> > > > > > > > > > > ><br>
> > > > > > > > ><br>
> > > > > > > > ><br>
> > ><br>
> > ><br>
> > > > > > > > > > > > On Sat, Jun 28, 2014 at 6:00 PM, <><br>
> _______________________________________________<br>
> > > > > > OpenSPIM mailing list<br>
> > > > > > <a href="mailto:OpenSPIM@openspim.org">OpenSPIM@openspim.org</a> <<a href="mailto:OpenSPIM@openspim.org">OpenSPIM@openspim.org</a>> <<br>
> <a href="mailto:OpenSPIM@openspim.org">OpenSPIM@openspim.org</a> <<a href="mailto:OpenSPIM@openspim.org">OpenSPIM@openspim.org</a>>><br>
> > > > ><br>
> > > > > > <a href="http://openspim.org/mailman/listinfo/openspim" target="_blank">http://openspim.org/mailman/listinfo/openspim</a><br>
> > > > ><br>
> > ><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://openspim.org/pipermail/openspim/attachments/20140702/b98d2e53/attachment.html" target="_blank">http://openspim.org/pipermail/openspim/attachments/20140702/b98d2e53/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
OpenSPIM mailing list<br>
<a href="mailto:OpenSPIM@openspim.org">OpenSPIM@openspim.org</a><br>
<a href="http://openspim.org/mailman/listinfo/openspim" target="_blank">http://openspim.org/mailman/listinfo/openspim</a><br>
<br>
<br>
End of OpenSPIM Digest, Vol 15, Issue 5<br>
***************************************<br>
</blockquote></div><br></div>