6150B positive.u error.

I am getting the following error when switching from the method tab to the tuning tab:

 

Error loading file: File c:\chem32\1\6150btun\positive.u
does nto exist or is missing values for the desired polarity.

 

It doesn't mention the negative mode. I have tried all of my tricks. I have used msdiag command to check parameters and have found nothing wrong. I have autotuned, saved, reset, used previous tunes, used tunes and files from another 6150b, and reloaded chemstation, etc,etc. Nothing has worked yet.
Any ideas?

 

 

As a follow up: We were able to finally rid the system of this error by updating the firmware.

  • Good Morning gebauman,

     

    Have you got the software installed on any other computer? We have tried something similair before, not with the positive.u file but with other files that have been corrupted.

    If you have it, you can always copy the file from another computer and replace the positive.u tune file. This should sort out your problem.

     

    I have never used a 6150B but on the 5975 and 5975T there is a directory that contains default tune files:

    You can click on the device you are after and find the default tune files.

    I'm not sure on the directory on your MS though but I'm sure there will be something similair.

  • Hello gebaumann

     

    The previous reply from my colleague is on the right track. Basically for the G6150B, the tune files reside at C:\Chem32\1\6150btun\atunes.tun. The \1\ in this string refers to the instrument number so if you ave multiple instruments configured you may see a different number:

     

     

    If you see this error again, let us know and we can send you the missing file or complete directory.

     

    Or maybe, once you have tune files that you are satisfied with you can make a backup of these files just in case.

     

    Regards,

    Danny

  • I tried multiple times to replace the atunes file both from saved files on the same machine and also from other 6150's. We even reinstalled Chemstation on a new computer. In the end we were able to finally rid the system of this error by updating the 6150 firmware.

Was this helpful?