Originally posted by fozrun
View Post
Seqanswers Leaderboard Ad
Collapse
Announcement
Collapse
No announcement yet.
X
-
Originally posted by firefly2280 View PostThanks, yes the primers were in the right wells and Im not using the experiment manager so I dont think that was it either.
Code:[Settings] CustomRead1PrimerMix C1 CustomIndexPrimerMix C2 CustomRead2PrimerMix C3
Comment
-
Originally posted by firefly2280 View PostThe error message
"Object reference not set to an instance of an object”
came up and that was it, so didnt even get as far as cluster densities.
Illumina thought it was the concentration of my library but It was definately at 2nM to start with then denatured and diluted correctly as per their protocol
Recently we had a bad piercing motor that was ending runs when the straws met the least resistance. When I dug down into the log file I found the following cogent message:
13-05-24 12:21:47.780 -04 000000101 INF: FPGA: Recv ^SIPDOWN sip: down sensor error
13-05-24 12:21:47.788 -04 000000110 WRN: FPGA: The FPGA reported an error while executing command "SIPDOWN"; error message: "sip: down sensor error"
13-05-24 12:21:47.788 -04 000000110 WRN: !!!!! Exception occurred, base exception type = "Illumina.Instrument.Bolt.Logic.Mainboard.FPGAErrorResponseException"
13-05-24 12:21:47.788 -04 000000110 WRN: !!!!! The FPGA reported an error while executing command "SIPDOWN"; error message: "sip: down sensor error"
13-05-24 12:21:47.789 -04 000000110 WRN: !!!!! Stack trace for exception type "Illumina.Instrument.Bolt.Logic.Mainboard.FPGAErrorResponseException":
13-05-24 12:21:47.803 -04 000000110 WRN: !!!!! at Illumina.Instrument.Bolt.Logic.Mainboard.FPGA.SendCommandGetResponse(), file FPGA.cs, line 1189
13-05-24 12:21:47.806 -04 000000110 INF: =================== Error, Exiting Run ===================
I finally decided to write the issue up and email it to Illumina Tech support with a request that it be submitted as a bug report to MCS. Am hoping it will be fixed in the next version...
--
Phillip
Comment
-
Originally posted by pmiguel View PostTo add to what McNelson wrote upthread, note that this error is actually a software bug, presumably in the error reporting code for MCS. So you should interpret it as "there has been an error, and MCS has stopped the run, but I can't report the error here because the code that should propagate that error from the sub-system that generated it, is broken. If you are really curious you can see the actual error out of the instrument run log."
Recently we had a bad piercing motor that was ending runs when the straws met the least resistance. When I dug down into the log file I found the following cogent message:
Note that the problem is clearly noted! So if you have written a bit of code yourself, it is immediately apparent that the error message being produced refers to the code itself, rather than the actual issue. Nevertheless, the tendency is to think "must be some sort of computer issue". Many a wild goose chase ensues. Up to an including engineers being sent on-site only to discover that the piercing motor is the culprit (in our case) and having to stay an extra day waiting for the necessary parts to be FeExed to him.
I finally decided to write the issue up and email it to Illumina Tech support with a request that it be submitted as a bug report to MCS. Am hoping it will be fixed in the next version...
--
Phillip
thanks again
Comment
-
Originally posted by mcnelson.phd View PostHey Phillip, can you list which specific files you dug through to find that error message? We just had a run fail and I can't find anything that gives an error message like you showed in the log files that I looked through.
Comment
-
Originally posted by GenoMax View PostMost likely "Flow_Cell_Folder/Logs/*.log" files. There is one log for each cycle but you can quickly "grep" through the files.
For future reference for others, I found what I wanted inCode:D:/Illumina/MiSeqTemp/<RunFolder>/Logs/<Cycle_that_run_failed_at.log>
Comment
-
I've gotten that error a few times, right at the beginning. We've usually been able to 1) take out our essentially 'unused' flow cell and replace it with a used one 2) run the post run wash 3) power cycle the machine 4) successfully re-start the run with the same reagents/flowcell. Now, this happened a few times and we eventually had the hard drive replaced in our Miseq, but this did seem to be a fairly non-specific software related error, as mentioned above.
Comment
Latest Articles
Collapse
-
by seqadmin
Proteins are often described as the workhorses of the cell, and identifying their sequences is key to understanding their role in biological processes and disease. Currently, the most common technique used to determine protein sequences is mass spectrometry. While still a valuable tool, mass spectrometry faces several limitations and requires a highly experienced scientist familiar with the equipment to operate it. Additionally, other proteomic methods, like affinity assays, are constrained...-
Channel: Articles
04-04-2024, 04:25 PM -
-
by seqadmin
Despite advancements in sequencing platforms and related sample preparation technologies, certain sample types continue to present significant challenges that can compromise sequencing results. Pedro Echave, Senior Manager of the Global Business Segment at Revvity, explained that the success of a sequencing experiment ultimately depends on the amount and integrity of the nucleic acid template (RNA or DNA) obtained from a sample. “The better the quality of the nucleic acid isolated...-
Channel: Articles
03-22-2024, 06:39 AM -
ad_right_rmr
Collapse
News
Collapse
Topics | Statistics | Last Post | ||
---|---|---|---|---|
Started by seqadmin, 04-11-2024, 12:08 PM
|
0 responses
31 views
0 likes
|
Last Post
by seqadmin
04-11-2024, 12:08 PM
|
||
Started by seqadmin, 04-10-2024, 10:19 PM
|
0 responses
32 views
0 likes
|
Last Post
by seqadmin
04-10-2024, 10:19 PM
|
||
Started by seqadmin, 04-10-2024, 09:21 AM
|
0 responses
28 views
0 likes
|
Last Post
by seqadmin
04-10-2024, 09:21 AM
|
||
Started by seqadmin, 04-04-2024, 09:00 AM
|
0 responses
53 views
0 likes
|
Last Post
by seqadmin
04-04-2024, 09:00 AM
|
Comment