[3dem] 3dem Digest, Vol 154, Issue 49

朱子慧 zihuizhu at 126.com
Mon Jun 29 02:49:46 PDT 2020



unsubscribe
On 6/25/2020 16:08,<3dem-request at ncmir.ucsd.edu> wrote:
Send 3dem mailing list submissions to
3dem at ncmir.ucsd.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem
or, via email, send a message with subject or body 'help' to
3dem-request at ncmir.ucsd.edu

You can reach the person managing the list at
3dem-owner at ncmir.ucsd.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of 3dem digest..."


Today's Topics:

1. Re: Gatan K3 reliability issues (Marcus FISLAGE)
2. Re: Gatan K3 reliability issues (Farzad)


----------------------------------------------------------------------

Message: 1
Date: Thu, 25 Jun 2020 07:03:31 +0000
From: Marcus FISLAGE <Marcus.Fislage at vub.be>
To: "Dokland, Terje" <dokland at uab.edu>
Cc: 3DEM mailing list <3dem at ncmir.ucsd.edu>
Subject: Re: [3dem] Gatan K3 reliability issues
Message-ID: <85426D3E-4766-4355-8412-2F819B4E76F6 at vub.be>
Content-Type: text/plain; charset="utf-8"

Hi Terje,

I made end of last year a similar survey and from that it seems that it?s a game of hit and miss sometimes.
Plenty of people reported no problems whatsoever, while other (although the minority) reported mainly problems with the chip.
We are currently waiting for our third chip to be installed (luckily all were just still in warranty). And I think with a waiting time of 1-2 month you are on the faster side.
The biggest problem is that we always have one channel (or parts of it) which return only a  black bar in the final image. However, the strength of this ?blackness? seems to vary by frame.

And as Craig mentioned, the K2 was definitely not without flaws either and even with the defect we have more usable area on our K3 than with the K2.

Cheers
Marcus
_______________________________
Dr. Marcus Fislage

EM Manager
VIB-Center for Structural Biology
VUB (Vrije Universiteit Brussel)
Building P1T, room 0.02
Pleinlaan 2
1050 BRUSSELS

Phone: +32 2 629 1807
https://urldefense.com/v3/__http://www.becm.be__;!!Mih3wA!XgTljZP8ww29gGirQIdFgEmyW8QCc3IzMv8Tl4J760sjRBx3xdRZai-xUwI6VD6yuA$ <https://urldefense.com/v3/__http://www.becm.be__;!!Mih3wA!XgTljZP8ww29gGirQIdFgEmyW8QCc3IzMv8Tl4J760sjRBx3xdRZai-xUwI6VD6yuA$ >
https://urldefense.com/v3/__https://twitter.com/BECM_VIB__;!!Mih3wA!XgTljZP8ww29gGirQIdFgEmyW8QCc3IzMv8Tl4J760sjRBx3xdRZai-xUwI0gL0Z9Q$








On 25 Jun 2020, at 00:25, Craig Yoshioka <yoshiokc at OHSU.EDU<mailto:yoshiokc at OHSU.EDU>> wrote:

Hi Terje,

Sounds like a dud?

My own opinion is I much prefer the overall reliability and quirks of the K3 to the K2.

Issues we?ve seen with K3?s:

1) Strange pixel defects on our first K3 installed Oct 2018. Even with these, the K3 was an upgrade in every area over the K2 (including reliability).  I have not seen this problem on any other K3.  These days, it now seems almost completely fixed: at some point I made a guess that the issue was in the communication between the FPGA boards, I pulled all the boards and moved the ?unhappiest" board to the end of the chain (so it only connected to one FPGA neighbor).  I also cleaned and reseated all the SATA cables connecting the FPGAs, and cleaned and reseated all the FPGA DIMMs.

2) FPGAs reporting memory errors or losing sync: only robust fix seems to be a _full_ power cycle of the PC- I suspect the FPGAs are a fairly independent subsystem, and don?t re-initialize properly unless they lose power.

3) Other errors that show up in quick status, ie. Losing the i2C communication, etc. often seem to require rebooting the camera power supply.  These seem very rare compared to how often we?d have to power cycle the K2 digitizer and FPGAs.   In two years I can count on one hand the number of times we?ve had to power cycle the K3 power supply.

4) The USB-Ethernet adapter bundled with the system for scope comms is flaky.  I bought a bunch of $20 1Gbe NICs that I dropped into the K3 PCs when possible.  So far these are much more reliable.

To the above, I?ll add that Gatan moving to a commodity Supermicro server chassis is greatly appreciated from my perspective.  It has yielded some really nice benefits:

1) I feel way more empowered to troubleshoot issues related to the PC hardware
2) The troubleshooting cycle is so much faster without waiting for upload of gain references
3) The Supermicro chassis has a full RMU.  I can power cycle the PC remotely, if needed, to address occasional FPGA problems.






On Jun 24, 2020, at 1:43 PM, Dokland, Terje <dokland at uab.edu<mailto:dokland at uab.edu>> wrote:

I wanted to poll the community for others? experience with the reliability of the Gatan K3 camera. We got ours installed in March last year, and In our experience the reliabilty has been appalling.

So far we have had to send it back to the factory for repair THREE times, all within one year. Each time it takes 1-2 months before we get it back, during which we are not able to do any imaging. This is in addition to problems with the computer, the capture cards and the MIB (shutter control) that have all failed at least once in the past year.

My question is whether this is typical for the K3, or did we receive a dud?

I can imagine and accept a few initial teething problems, but this is getting ridiculous. We had the K2 for somewhat over a year before we got the K3, and had no problems with it. Before that, we had a Gatan CCD, which did not have any problems at all in its 10 year lifetime. Did Gatan run out an unfinished product, or have we just been unlucky?

Any insights would be appreciated.

Terje


_______________________________________________
3dem mailing list
3dem at ncmir.ucsd.edu<mailto:3dem at ncmir.ucsd.edu>
https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem

_______________________________________________
3dem mailing list
3dem at ncmir.ucsd.edu<mailto:3dem at ncmir.ucsd.edu>
https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ncmir.ucsd.edu/pipermail/3dem/attachments/20200625/e89b60a5/attachment-0001.html>

------------------------------

Message: 2
Date: Thu, 25 Jun 2020 10:08:25 +0200
From: Farzad <farzaad at gmail.com>
To: Marcus FISLAGE <Marcus.Fislage at vub.be>
Cc: 3DEM mailing list <3dem at ncmir.ucsd.edu>
Subject: Re: [3dem] Gatan K3 reliability issues
Message-ID:
<CAM-VoOny-aMb+kvuiwXLCc2M--9o2EHCofCqmTwhonoR6KGsVw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi all,

The black stripes was also present in K2, as we have it here. Some people
say it is from digitizer, some say it happens when switch between linear
and counting repeatedly and our experience shows we have more chance for
black stripes in higher frame rates. There is a DM script for finding these
stripes.

Best regards

Ferrie

University of Halle

On Thu, Jun 25, 2020, 09:03 Marcus FISLAGE <Marcus.Fislage at vub.be> wrote:

Hi Terje,

I made end of last year a similar survey and from that it seems that it?s
a game of hit and miss sometimes.
Plenty of people reported no problems whatsoever, while other (although
the minority) reported mainly problems with the chip.
We are currently waiting for our third chip to be installed (luckily all
were just still in warranty). And I think with a waiting time of 1-2 month
you are on the faster side.
The biggest problem is that we always have one channel (or parts of it)
which return only a  black bar in the final image. However, the strength of
this ?blackness? seems to vary by frame.

And as Craig mentioned, the K2 was definitely not without flaws either and
even with the defect we have more usable area on our K3 than with the K2.

Cheers
Marcus
_______________________________
Dr. Marcus Fislage

EM Manager
VIB-Center for Structural Biology
VUB (Vrije Universiteit Brussel)
Building P1T, room 0.02
Pleinlaan 2
1050 BRUSSELS

Phone: +32 2 629 1807
https://urldefense.com/v3/__http://www.becm.be__;!!Mih3wA!Rt3EuDIsRfVkwrjNr9bl4xUk-y2pz5pwS5Bti88zxRfbjRe1-87Uz2uLNHg8Joig_w$
<https://urldefense.com/v3/__http://www.becm.be__;!!Mih3wA!XgTljZP8ww29gGirQIdFgEmyW8QCc3IzMv8Tl4J760sjRBx3xdRZai-xUwI6VD6yuA$>
https://urldefense.com/v3/__https://twitter.com/BECM_VIB__;!!Mih3wA!Rt3EuDIsRfVkwrjNr9bl4xUk-y2pz5pwS5Bti88zxRfbjRe1-87Uz2uLNHiObmmSLg$
<https://urldefense.com/v3/__https://twitter.com/BECM_VIB__;!!Mih3wA!XgTljZP8ww29gGirQIdFgEmyW8QCc3IzMv8Tl4J760sjRBx3xdRZai-xUwI0gL0Z9Q$>








On 25 Jun 2020, at 00:25, Craig Yoshioka <yoshiokc at OHSU.EDU> wrote:

Hi Terje,

Sounds like a dud?

My own opinion is I much prefer the overall reliability and quirks of the
K3 to the K2.

Issues we?ve seen with K3?s:

1) Strange pixel defects on our first K3 installed Oct 2018. Even with
these, the K3 was an upgrade in every area over the K2 (including
reliability).  I have not seen this problem on any other K3.  These days,
it now seems almost completely fixed: at some point I made a guess that the
issue was in the communication between the FPGA boards, I pulled all the
boards and moved the ?unhappiest" board to the end of the chain (so it only
connected to one FPGA neighbor).  I also cleaned and reseated all the SATA
cables connecting the FPGAs, and cleaned and reseated all the FPGA DIMMs.

2) FPGAs reporting memory errors or losing sync: only robust fix seems to
be a _full_ power cycle of the PC- I suspect the FPGAs are a fairly
independent subsystem, and don?t re-initialize properly unless they lose
power.

3) Other errors that show up in quick status, ie. Losing the i2C
communication, etc. often seem to require rebooting the camera power
supply.  These seem very rare compared to how often we?d have to power
cycle the K2 digitizer and FPGAs.   In two years I can count on one hand
the number of times we?ve had to power cycle the K3 power supply.

4) The USB-Ethernet adapter bundled with the system for scope comms is
flaky.  I bought a bunch of $20 1Gbe NICs that I dropped into the K3 PCs
when possible.  So far these are much more reliable.

To the above, I?ll add that Gatan moving to a commodity Supermicro server
chassis is greatly appreciated from my perspective.  It has yielded some
really nice benefits:

1) I feel way more empowered to troubleshoot issues related to the PC
hardware
2) The troubleshooting cycle is so much faster without waiting for upload
of gain references
3) The Supermicro chassis has a full RMU.  I can power cycle the PC
remotely, if needed, to address occasional FPGA problems.






On Jun 24, 2020, at 1:43 PM, Dokland, Terje <dokland at uab.edu> wrote:

I wanted to poll the community for others? experience with the reliability
of the Gatan K3 camera. We got ours installed in March last year, and In
our experience the reliabilty has been appalling.

So far we have had to send it back to the factory for repair THREE times,
all within one year. Each time it takes 1-2 months before we get it back,
during which we are not able to do any imaging. This is in addition to
problems with the computer, the capture cards and the MIB (shutter control)
that have all failed at least once in the past year.

My question is whether this is typical for the K3, or did we receive a
dud?

I can imagine and accept a few initial teething problems, but this is
getting ridiculous. We had the K2 for somewhat over a year before we got
the K3, and had no problems with it. Before that, we had a Gatan CCD, which
did not have any problems at all in its 10 year lifetime. Did Gatan run out
an unfinished product, or have we just been unlucky?

Any insights would be appreciated.

Terje


_______________________________________________
3dem mailing list
3dem at ncmir.ucsd.edu
https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem


_______________________________________________
3dem mailing list
3dem at ncmir.ucsd.edu
https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem


_______________________________________________
3dem mailing list
3dem at ncmir.ucsd.edu
https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ncmir.ucsd.edu/pipermail/3dem/attachments/20200625/b75b0b23/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
3dem mailing list
3dem at ncmir.ucsd.edu
https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem


------------------------------

End of 3dem Digest, Vol 154, Issue 49
*************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ncmir.ucsd.edu/pipermail/3dem/attachments/20200629/eae859bd/attachment-0001.html>


More information about the 3dem mailing list