• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 12 replies
  • Subscribers 118 subscribers
  • Views 2361 views
  • Users 0 members are here
Related

Agilent Knowledge Portal

Find maintenance, best practice, and troubleshooting articles.

Agilent Knowledge Portal

Partial calibration in real time openlab CDS

ALAZ

(method partially calibrating on one column and not at all on the other)

Hey all,

I have not been able to figure out why I am getting a partial calibration in real time with my brand new method.  I am doing HS-GC-FID dual column analysis.

I have six analyte levels with an internal standard. 

I have properly populated the "Calibration" under my processing method with identifying my internal standards and associating my analytes of interest with their proper internal standard.  I put in the concentrations of all six levels.

Then, on my sequence I designate my calibration levels of 1-6 and use the "Clear all calibrations" from the dropdown for the first cal.std type so that a new curve should be generated.  However, I am only getting a two point calibration (my two highest standards) on only one of my columns.  The other column's curve is totally blank. 

All the peaks/data are present in all six calibrators and when I reprocess that sequence with the method I used in the sequence in the first place, it properly calibrates and all six points are present on both columns!  How is this not working in real time, but its working in reprocessing?

(note successful 6-point calibration from reprocessing of the exact same method)

  • 0 in reply to ALAZ

    Let me summarize... 

    Everything that you 've shared with us looks perfectly normal, except the calibration on one of the FID channels doesn't show all of the calibration levels.

    I'm now completely out of ideas.  You've done everything that I would have done. 

    I would now be heading down one of two routes:

    1. Contact your local Agilent customer support team to see if they can identify what's going on.
    2. Create a new processing method from scratch, just in case the problem is with this method.

    If you wanted to share the data with me, I'd be more than happy to take a look!  You've got me hooked on this one, because I can't explain what you're seeing!

    /Andy

  • 0 in reply to Andy Wright

    Well, a more accurate summary is that the calibration on one channel doesn't show all of the levels and none of the levels on the other channel.

    I built a new processing method from scratch and got the same exact results. I have put in a call to Agilent and am waiting for a call back from someone who knows OpenLab CDS 2.5. 

    I don't mind sharing my data if it will help figure this out.  I don't have anything other than standards (calibrators and controls).  Tell me what you'd like to look at and how I would get that to you.

  • 0 in reply to ALAZ

    I wonder if you could export the result set as an .olax file and attach it to a post, unless the file is too big or that would be too public.  Calibrators and controls are perfect.

    I can't actually see anywhere to attach a file, though.

    Andy

  • 0 in reply to Andy Wright

    I was extremely optimistic after my hours-long technical support webex session yesterday.  I got several other questions answered and assistance with other stuff.  But regarding this calibration issue, they were confident I just needed to "Reprocess All" and then "Save All Results" before updating the master method.  As you know from here, I had only reprocessed the calibrators and didn't save all the results before updating the master method.  We didn't think the results needed to be saved.

    But guess what?  This didn't work either!  I ran a new batch yesterday afternoon after the latest update and got the same exact 2 point calibration on one column and nothing on the other. But now I've got another problem...the batch aborted toward the end of my sequence due to a vial jam, so now I need service.

    I will look into exporting an .olax file.  That's not something I'm familiar with.

  • +1

    The problem is being caused by the peak names from both channels are the same except for the capital letter on one channel.   Change the name of the peaks on one channel to have a "-", '2", or "*" after the name and then it will work as expected. 

  • 0 in reply to Dan_OTS

    YES!  This resolved the issue.  Apparently just differentiating the identical compound names between the two channels with just a capital letter vs all lower case was not sufficient.  I added an "*" to second channel compound names and now have full curves on both columns in real time. 

Was this helpful?
Privacy Statement
Terms of Use
Contact Us
Site Help