Clarity 7.4 Configuration Shimadzu GC 17A

[jriefkohl]

Dear All;\

GC has a Serial Board on the back of the GC. A Serial 9 pin to 25 pin cable that came with the GC is connected to Port 6 on the MultiCom.

Configured Function 15 on the GC with the paramaters indicated on the Clarity Shimadzu Manual. Turn OFF and Turn ON GC as indicated.

A Colibrick box is required for data acquisition???/

Clarity Configuration does not recognized the GC.

Please review and advice.

[Lenka Diblikova]

Dear Jorge,

just from your description we're not able to locate the reason of the problem. Please send us the Clarity diagnostic files (as listed below) for analysis to Support@dataapex.com

Clarity version 6.2 and older:
C:\Clarity\clarity.cfg
C:\Clarity\clarity.dsk
C:\Clarity\systeminfo.txt
C:\Clarity\others.ini
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)

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
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)

We can also help you using TeamViewer built-in Clarity. Is the PC with Clarity online?

Thank you.

[jriefkohl]

See enclosed files.

[Lenka Diblikova]

Dear Jorge,

thank you for the requested files, we will analyse them and let you know the findings.

Best Regards,

[Lenka Diblikova]

Dear Jorge,

nothing suspicious was found during the analysis of the diagnostics files you have send.The record of communication on RS232 might be helpful. 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 corresponding COM port. Record will be stored in the file named as in line "filename", in default it will be CommDrvCOM1_Current_Date.txt.
An optimal sequence is:
1/ Turn communication recording on for the device causing trouble
2/ Try to invoke the error or trouble you experiencing
3/ After successfully invoking the error, close the Clarity
4/ Copy out CommDrv___.txt and send it to us.

If you need any help with the recording settings, let us know.
Best Regards,
Lenka Diblíková

[Lenka Diblikova]

Dear Jorge,

was the problem with GC communication solved?