SEQanswers

Go Back   SEQanswers > Sequencing Technologies/Companies > Illumina/Solexa



Similar Threads
Thread Thread Starter Forum Replies Last Post
Samtools "is recognized as '*'" "truncated file" error axiom7 Bioinformatics 3 11-26-2014 02:53 AM
BWA installation failed after "make" command in Linux rzeng Bioinformatics 2 09-05-2013 03:04 AM
DEXSeq error in estimateDispersions: match.arg(start.method, c("log(y)", "mean")) fpadilla Bioinformatics 14 07-03-2013 02:11 PM
base quality encoding changed after "bwa samse" command tomjan Bioinformatics 4 02-26-2013 12:23 PM
cufflinks "waiting for 1 threads to complete" letusgo Bioinformatics 6 01-17-2013 11:07 AM

Reply
 
Thread Tools
Old 08-25-2016, 01:45 AM   #1
Lovro
Member
 
Location: Slovenia

Join Date: Mar 2015
Posts: 19
Default myseq error "waiting for FPGA command CAMDBLSNAP"

Hi,

I would appreciate any help in regard to the following MySeq error:

Timeout of 70.000 seconds exceeded while waiting for FPGA command "CAMDBLSNAP 390 390 188 188 34390 150" to complete.

see image:



The error emerges any time after the run is started and ruins the run. It first appeared a year ago and now the fifth time since.

The only advice we are continually getting from Illumina support is that we should reboot our myseq prior to the run (we are doing that since the first time the error occurred) and that the error is "very unlikely to repeat".
Unfortunately, the error is repeating and keeps ruining runs.

The MySeq's warranty has expired.

If anybody had experienced the problem himself or has any information regarding the error (what does the code mean?), we would be very happy to hear from you.

Thank you,
Lovro
Lovro is offline   Reply With Quote
Old 08-25-2016, 03:50 AM   #2
GenoMax
Senior Member
 
Location: East Coast USA

Join Date: Feb 2008
Posts: 7,075
Default

If your MiSeq is not under a maintenance contract then you are living dangerously (or you just don't use it enough to justify the contract).

This error may be due to some sort of hardware issue that can only be fixed by a visit from an Illumina engineer. You may have to bite the bullet and pay for that visit.
GenoMax is offline   Reply With Quote
Old 08-25-2016, 09:12 AM   #3
Jessica_L
Senior Member
 
Location: Washington, D.C. metro area

Join Date: Feb 2010
Posts: 118
Default

What Genomax said.

I'd add that if you don't have your MiSeq under a maintenance agreement, you may want to consider getting one first, as the service visit and repair can easily exceed the cost of a contract. There are usually some hoops to jump through, but that's probably the cheapest way to get your instrument fixed.

An initial visit with an FSE might be a good idea, at least, and if you have a decent relationship with them, they could give you a ballpark idea of how much repairs might cost and how that would compare to the cost of a service agreement.
Jessica_L is offline   Reply With Quote
Old 08-30-2016, 04:37 AM   #4
Lovro
Member
 
Location: Slovenia

Join Date: Mar 2015
Posts: 19
Default

Hi, thanks for the answers.
We have considered the latter.
However, I was more interested in finding out the meaning of the error code.

We had a hardware problem with a moveable mirror part (bouncing while snapping into position) while the machine was still under warranty. It was replaced by illumina and might still be under warranty.
"CAMDBLSNAP" sounds a lot like some part of the camera snapping into position, so I want to investigate the issue.

The error codes descriptions might be impossible to get a hold of though...?

tnx
Lovro is offline   Reply With Quote
Old 08-31-2016, 06:06 AM   #5
Jessica_L
Senior Member
 
Location: Washington, D.C. metro area

Join Date: Feb 2010
Posts: 118
Default

Your best bet on that score is probably your field support from Illumina, for a MiSeq probably your FAS. The error codes aren't closely guarded secrets, but I'm not aware of a collection of codes with descriptions that's accessible in any kind of searchable format.
Jessica_L is offline   Reply With Quote
Old 08-31-2016, 09:07 PM   #6
misterc
Member
 
Location: Livermore, CA

Join Date: Jan 2016
Posts: 44
Default

CAMDBLSNAP is an FPGA or cabling issue on one of the 2 USB cables to the cameras internally. You can try re-seating the USB cables to the cameras to prevent/reduce the frequency of these errors. The ones you want to re-seat are on the inside of the MiSeq, facing the front of the instrument, up on the top right (behind the monitor), readily accessible when you take the top skin/panel off.
misterc is offline   Reply With Quote
Old 09-01-2016, 08:25 AM   #7
Lovro
Member
 
Location: Slovenia

Join Date: Mar 2015
Posts: 19
Default

Thank you very much. I will mention this to their representative.
Lovro is offline   Reply With Quote
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off




All times are GMT -8. The time now is 12:46 PM.


Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
Single Sign On provided by vBSSO