<div dir="ltr">Hi all (mainly to Ke),<div><br></div><div>Just a word from my experience using Win7/64bit. Ke - in order for Picard's own application to work, you need to have the serial numbers for the XY, Z and R components exactly right. I didn't receive any documentation on what to do. I just copied the serial numbers that i saw in some simple documentation that came with it... but using these never got the Picard application to work. However, the OpenSPIM system worked fine. Anyway, after having this for some months (and just putting down the Picard program not working to some weird bug), I only realised today when the serial number stickers on the 4d stage itself jumped out at me (which aren't hidden, they're pretty obvious actually now that I look at them!). Anyway, entering in *those* number, *ding* the Picard application worked, and I could control the application from that piece of software. FWIW, our serials were 198, 199, 200. R was much lower, 60-something. :)</div>
<div>What I've also found, is that the "home" position was never set correctly until I managed to get the 4D stage to properly talk to its own software. X and Y were extending far too much into the sample chamber. Now that we could properly 'Home' the stage in its own software once, it's much better now and we have much better range. :)</div>
<div><br></div><div>Other comments about Win7/6: In our hands the Fiji/ImageJ and the Micromanager>OpenSpim plugin work fine. I launch it as a WindowsXP/32 bit compatibility application and it seems to be happy so far. It didn't like being opened natively. I also tried compiling a Win7/64 build from GIT, but I never spent the time to properly work out how to roll the plugins for the hardware into it, so on that basis it never worked properly. As for the system itself, we still haven't actually captured anything yet as we've had all sorts of fun getting the sample chamber right -- and we're just aligning/calibrating it now. But the stage, camera, and laser are all happily being controlled by the OpenSPIM micromanager plugin.</div>
<div><br></div><div>cheers,</div><div>Kieran</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 27, 2014 at 11:05 PM, Luke Stuyvenberg <span dir="ltr"><<a href="mailto:stuyvenberg@wisc.edu" target="_blank">stuyvenberg@wisc.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Ke, Mark, Johannes,<br>
<br>
<br>
On 06/26/14, Mark Tsuchida wrote:<br>
<div class="">> Johannes, I also found the cause: OnSerialGeneric() is calling the<br>
> Initialize() function, which fails. This happens before the Hardware<br>
> Wizard calls Initialize (actually, when the wizard is trying to get<br>
> the initial values of the pre-init properties), so the wizard has no<br>
> chance to display the configuration dialog.<br>
> <br>
> Simply taking out the calls to Initialize (PicardStage.cpp lines<br>
> 243-245, 258) seems to fix this, but I'm not sure if that is all that<br>
> needs to be done (since I don't have a Picard stage and cannot figure<br>
> out what the intent of calling Initialize() at this point was).<br>
> Johannes, can you take a look at this?<br>
<br>
<br>
<br>
</div>The intent of the Initialize call was to test the serial number received from the Pi-detector, but I didn't account for the possibility of CPiDetector returning DEFAULT_SERIAL_UNKNOWN, which it does if the requested device hadn't been found. I'm preparing a fix for this that I will submit via SVN as soon as possible.<br>
<br>
<br>
The ultimate issue is this: The Pi-detector only tested serial numbers up to 250. I've doubled this for now, but this is a stop-gap measure that causes an ugly pause in the device adding process while it probes the serial numbers; I will need to seek a different approach to detecting the motors.<br>
<br>
<br>
I'll report back after fixing/testing and committing/uploading the device adapter.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
Luke<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 06/26/14, Mark Tsuchida wrote:<br>
> Hi Ke and Johannes,<br>
><br>
> On Thu, Jun 26, 2014 at 11:57 AM, Mark Tsuchida <<a href="mailto:marktsuchida@gmail.com">marktsuchida@gmail.com</a>> wrote:<br>
> > On Wed, Jun 25, 2014 at 10:27:54PM -0400, Ke Li wrote:<br>
> >> 1. I still can't add the Z stage when I create the hardware configuration.<br>
> >> I tried both 64-bit and 32-bit Windows system, neither can work. Since the<br>
> >> problem report doesn't give much info, I'm not sure whether there are other<br>
> >> ways to solve this problem? And what possible reasons can cause the<br>
> >> problem?<br>
> ><br>
> > Are you sure you have the correct serial number for the Z stage (as<br>
> > Johannes suggested)? In the problem report you sent us, it looked like<br>
> > you had not set the serial number when adding the Z stage in the<br>
> > Hardware Configuration Wizard. This causes the device adapter to use the<br>
> > serial number "-1", which always results in an error.<br>
> ><br>
> > Do you see a field to enter the serial number for the Z stage? If you cannot<br>
> > get it to work even when entering the correct serial number, could you try<br>
> > sending another Problem Report?<br>
><br>
> Sorry, I hadn't seen your reply to Johannes that answered that question of mine.<br>
><br>
> I can reproduce the problem: with no Picard hardware connected to the<br>
> computer, no configuration dialog for the pre-initialization settings<br>
> (including the serial number) is displayed in the hardware<br>
> configuration wizard. This is the case for the Twister and Z stage,<br>
> but not the XY stage (at least on my computer).<br>
><br>
> Johannes, I also found the cause: OnSerialGeneric() is calling the<br>
> Initialize() function, which fails. This happens before the Hardware<br>
> Wizard calls Initialize (actually, when the wizard is trying to get<br>
> the initial values of the pre-init properties), so the wizard has no<br>
> chance to display the configuration dialog.<br>
><br>
> Simply taking out the calls to Initialize (PicardStage.cpp lines<br>
> 243-245, 258) seems to fix this, but I'm not sure if that is all that<br>
> needs to be done (since I don't have a Picard stage and cannot figure<br>
> out what the intent of calling Initialize() at this point was).<br>
> Johannes, can you take a look at this?<br>
><br>
> Best,<br>
> Mark<br>
><br>
> --<br>
> Mark Tsuchida<br>
> Micro-Manager Team (UCSF Vale Lab)<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>
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>
</div></div></blockquote></div><br></div></div>