<div dir="ltr"><div><div><div>Hi, <br></div>I just wanted to say that I also have been experiencing the errors and removal of all components when I try to edit an existing configuration file, as Veli-Pekka mentions, but I am however able to add the stage and all components back, and I can add them to a new configuration file as well. So I haven't worried about this problem. I attach a corelog and recently created configuration file. <br>
</div>Also, the strange noise that my x,y, and z stages were making has disappeared, I'm not sure when. But thanks Luke, in case you fixed that. <br><br></div>Aurelia<br><br><div><br><div><div class="gmail_extra"><br>
<br><div class="gmail_quote">On Mon, Aug 18, 2014 at 11:18 AM, <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: Picard stage error after update (Veli-Pekka Ronkainen)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 18 Aug 2014 10:18:09 +0000<br>
From: Veli-Pekka Ronkainen <<a href="mailto:veli-pekka.ronkainen@oulu.fi">veli-pekka.ronkainen@oulu.fi</a>><br>
To: Luke Stuyvenberg <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>>, "<a href="mailto:openspim@openspim.org">openspim@openspim.org</a>"<br>
<<a href="mailto:openspim@openspim.org">openspim@openspim.org</a>><br>
Subject: Re: [OpenSPIM] Picard stage error after update<br>
Message-ID: <<a href="mailto:bb240d237c444885b514db787456243c@nippu12.univ.yo.oulu.fi">bb240d237c444885b514db787456243c@nippu12.univ.yo.oulu.fi</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hi Luke,<br>
<br>
<br>
Thanks for your reply! I attach here different CoreLogs created by two different software versions:<br>
<br>
<br>
The first CoreLog pid3156 is generated by the latest SW version. Here we tried to make a new configuration and adding/editing Picard Z-stage is not possible [IFO,dev:Picard Z Stage] Could not initialize motor -1 (PiUsb error code 1).<br>
<br>
<br>
The next one pid4032 is generated by the same SW version, and we tried to modify an existing older .cfg-file which is also attached here.<br>
<br>
<br>
The last CoreLog (no pid number) is generated by the non-updated SW version downloaded from <a href="http://openspim.org" target="_blank">openspim.org</a>. Here everything is fine.<br>
<br>
<br>
<br>
There is no possibility to edit the old .cfg-file with notepad like you suggested, since there is no mention about the Twister step size. Maybe because there is no possibility to edit step sizes in the older SW version, only serial numbers?<br>
<br>
<br>
Regards,<br>
<br>
Veli-Pekka<br>
<br>
<br>
________________________________<br>
L?hett?j?: <a href="mailto:openspim-bounces@openspim.org">openspim-bounces@openspim.org</a> <<a href="mailto:openspim-bounces@openspim.org">openspim-bounces@openspim.org</a>> k?ytt?j?n puolestaLuke Stuyvenberg <<a href="mailto:stuyvenberg@wisc.edu">stuyvenberg@wisc.edu</a>><br>
L?hetetty: 16. elokuuta 2014 4:10<br>
Vastaanottaja: <a href="mailto:openspim@openspim.org">openspim@openspim.org</a><br>
Aihe: Re: [OpenSPIM] Picard stage error after update<br>
<br>
Hi Veli-Pekka,<br>
<br>
On 8/14/2014 7:01 AM, Veli-Pekka Ronkainen wrote:<br>
However, now after using the Fiji updater Picard USB-stage rotation angle coordinates are not right anymore. Changing angle from -180 deg to 180 deg rotates the sample holder only ~180 degrees, and rotation in general spins the sample much less than indicated by the slider. In addition, we can not access and modify old .cfg-files, so that it would be possible to change step size of the twister from 1.8 to 1, as it was discussed earlier: <a href="http://openspim.org/pipermail/openspim/2014-July/000482.html" target="_blank">http://openspim.org/pipermail/openspim/2014-July/000482.html</a> .<br>
As you suspected, this is because of the change in step size.<br>
<br>
Modification of an existing configuration starts with an error "Error in device Picard Z Stage: Unable to communicate with the device" followed by lots of COM and "No device with label _device name_" -errors. Creating a new configuration doesn't help since it is not possible to add Picard stage z-axis to the config file or modify the serial number.<br>
The error when modifying a configuration or creating new configurations is a different problem entirely, and one I wasn't aware of. If you could, please, attach a CoreLog or two from after the update, when you've received these errors. (If you can't tell which one contains these errors, you can open them and search, or just run the program again and produce a new one.) This would go a long way towards figuring out what's causing this problem.<br>
<br>
But in the meantime, an easy, dirty solution to the problem interfering with your experiments is to open a working configuration file in Notepad. You should see a line in there that reads something like<br>
<br>
"Device,Picard Twister,StepSize,1.8"<br>
<br>
Changing the 1.8 to 1 should resolve at least the rotational stage problem.<br>
<br>
<br>
We've tried to copy the latest Picard .dll-files from the recent Micro-Manager nightly build but the problem persists. Are there some other files we should copy and replace as well? Of course we can still download and configure the non-updated package from <a href="http://openspim.org" target="_blank">openspim.org</a> and be happy using that older version without any problems. Still it would be nice to be up-to-date. Anyone having the same problems or some solutions? Thanks!<br>
<br>
You shouldn't need any other files; hopefully the above is all it takes to get things running until I can figure out what's causing the trouble with editing configurations.<br>
<br>
Hope this helps,<br>
Luke Stuyvenberg<br>
<br>
P.S. If you get a few moments, please feel free to update <a href="http://openspim.org/Who_has_an_OpenSPIM%3F" target="_blank">http://openspim.org/Who_has_an_OpenSPIM%3F</a> with your location and information! We love hearing about people using the system.<br>
<br>
On 8/14/2014 7:01 AM, Veli-Pekka Ronkainen wrote:<br>
<br>
Dear all,<br>
<br>
<br>
We've been scanning some mouse tissue test samples with our dual-side illumination OpenSPIM for a short while now, and we are very happy with the first results!<br>
<br>
<br>
We have used the original software package downloaded from <a href="http://openspim.org" target="_blank">openspim.org</a> without any updates, and it has been working fine. However, now after using the Fiji updater Picard USB-stage rotation angle coordinates are not right anymore. Changing angle from -180 deg to 180 deg rotates the sample holder only ~180 degrees, and rotation in general spins the sample much less than indicated by the slider. In addition, we can not access and modify old .cfg-files, so that it would be possible to change step size of the twister from 1.8 to 1, as it was discussed earlier: <a href="http://openspim.org/pipermail/openspim/2014-July/000482.html" target="_blank">http://openspim.org/pipermail/openspim/2014-July/000482.html</a> . Modification of an existing configuration starts with an error "Error in device Picard Z Stage: Unable to communicate with the device" followed by lots of COM and "No device with label _device name_" -errors. Creating a new configuration doesn't help since it is not possible to add Picard stage z-axis to the config file or modify the serial number.<br>
<br>
<br>
We've tried to copy the latest Picard .dll-files from the recent Micro-Manager nightly build but the problem persists. Are there some other files we should copy and replace as well? Of course we can still download and configure the non-updated package from <a href="http://openspim.org" target="_blank">openspim.org</a> and be happy using that older version without any problems. Still it would be nice to be up-to-date. Anyone having the same problems or some solutions? Thanks!<br>
<br>
<br>
Regards,<br>
<br>
Veli-Pekka Ronkainen<br>
<br>
Light Microscopy Core Facility<br>
<br>
Biocenter Oulu, University of Oulu<br>
<br>
Finland<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
OpenSPIM mailing list<br>
<a href="mailto:OpenSPIM@openspim.org">OpenSPIM@openspim.org</a><mailto:<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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://openspim.org/pipermail/openspim/attachments/20140818/dd77ec35/attachment.html" target="_blank">http://openspim.org/pipermail/openspim/attachments/20140818/dd77ec35/attachment.html</a>><br>
-------------- next part --------------<br>
An embedded and charset-unspecified text was scrubbed...<br>
Name: CoreLog20140818T092148_pid3156.txt<br>
URL: <<a href="http://openspim.org/pipermail/openspim/attachments/20140818/dd77ec35/attachment.txt" target="_blank">http://openspim.org/pipermail/openspim/attachments/20140818/dd77ec35/attachment.txt</a>><br>
-------------- next part --------------<br>
An embedded and charset-unspecified text was scrubbed...<br>
Name: CoreLog20140818T094233_pid4032.txt<br>
URL: <<a href="http://openspim.org/pipermail/openspim/attachments/20140818/dd77ec35/attachment-0001.txt" target="_blank">http://openspim.org/pipermail/openspim/attachments/20140818/dd77ec35/attachment-0001.txt</a>><br>
-------------- next part --------------<br>
An embedded and charset-unspecified text was scrubbed...<br>
Name: CoreLog20140818.txt<br>
URL: <<a href="http://openspim.org/pipermail/openspim/attachments/20140818/dd77ec35/attachment-0002.txt" target="_blank">http://openspim.org/pipermail/openspim/attachments/20140818/dd77ec35/attachment-0002.txt</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: twolasers_2_calibrated.cfg<br>
Type: application/octet-stream<br>
Size: 1813 bytes<br>
Desc: twolasers_2_calibrated.cfg<br>
URL: <<a href="http://openspim.org/pipermail/openspim/attachments/20140818/dd77ec35/attachment.obj" target="_blank">http://openspim.org/pipermail/openspim/attachments/20140818/dd77ec35/attachment.obj</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 16, Issue 5<br>
***************************************<br>
</blockquote></div><br></div></div></div></div>