Clarity discussion forum

Hi everybody,

I have a question about autobalance with Clarity 7.4.1.88 and Agilent ICF Drivers on a 1100 machine. The point is, that the autobalance feature simply don't work... I installed Clarity 7.4.1.88 on a new PC and chose to use the ICF drivers for compatibility reasons to our other HPLC Systems.

Any suggestions what I can/ have to do for activating autobalance?

Greetings,
Roman

Hi Roman,
can you please let us know on which module you are trying to perform the zeroing? Some modules (such as FLD detector) may have the option in the user interface, but does not zero by design. This was acknowledged by Agilent and will be mentioned in the ICF help in some of the future ICF releases.
Zeroing VWD/DAD should work.

Best regards,
Daniel

Hi Daniel,

the problem occurred on an Agilent DAD, G7112B. I am lucky if you can help!

Greetings
Roman

Dear Roman,

Daniel is out of office this week on Pittcon Conference. Is it possible to perform a TeamViewer session? Is the PC with Clarity connected to internet?

Diagnostic files will be helpful as well as a communication record.
Please send us following files:

Clarity version 6.2 and older
C:\Clarity\clarity.cfg
C:\Clarity\clarity.dsk
C:\Clarity\systeminfo.txt
C:\Clarity\others.ini
C:\Clarity\badtrace.txt
all *.dmp files (may not be present, they are created during some problems only)
C:\Clarity\log\*.audit for the days the problem appeared (file format is YYYY_MM_DD.audit => ‘2017_08_29.audit’ is audit trail file for 29th August 2017)
chromatogram (*.prm)
method (*.met) and
sequence (*.seq)
files related to the problem

Clarity version 7.0 and newer
C:\Clarity\CFG\clarity.cfg
C:\Clarity\CFG\clarity.dsk
C:\Clarity\CFG\systeminfo.txt
C:\Clarity\CFG\others.ini
C:\Clarity\CFG\Debug_Logs\badtrace.txt
all *.dmp files from C:\Clarity\CFG\Debug_Logs (may not be present, they are created during some problems only)
C:\Clarity\CFG\Audit_Trails\*.audit for the days the problem appeared (file format is YYYY_MM_DD.audit => ‘2017_08_29.audit’ is audit trail file for 29th August 2017)
chromatogram (*.prm)
method (*.met) and
sequence (*.seq)
files related to the problem
Located in the C:\Clarity\DataFiles

Best Regards,

Dear Lenka,

I am sorry, but the system is not connected to the internet. I will send you the nessery Files, when you provide me with a E-Mail address.

Greetings,
Roman

Sure, please send the files to Support@dataapex.com.

We also need the record of communication on RS232 (serial COM port) lines. Recording is turned off as default, so at first you need to turn it on.
In the file C:\Clarity\CFG\CommDrv.ini there is a block for every COM port used for communication (you can edit it with Notepad or any other simple text editor):

[COM1]
echo=OFF
textmode=ON
filename=CommDrvCOM1_%D.txt
reset=ON

You have to change line "echo=OFF" to "echo=ON" for every COM port, which communication you want to record. Record will be stored in the file named as in line "filename", in default it will be CommDrvCOM1_Current_Date.txt (so you will get one file per every port and day.)

In summary:
1/ Turn communication recording on for the device causing trouble (as listed above)
2/ Try to invoke the error or trouble you experiencing
3/ After successfully invoking the error, close the Clarity
4/ Copy out all the files needed ( all the files listed above + CommDrv___.txt files with communication) and send it to us. (You can pack them before into the .zip file if its more convenient for you).


Best Regards,

I have answered via email.