RE: C863 can't answer the PI GCS commands

["Goetze, Kurt A." <goetze@aps.anl.gov>]

Hi Qingru,

 

I would say yes, the DLL would be required if your C863’s firmware does not support PIGCS2.  If that’s the case, you should be able to work with PI to update your firmware.  Then the PIGCS2 support in motorR6-8 should work. 

 

Kurt

 

From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Mi Qingru
Sent: Wednesday, November 13, 2013 12:50 AM
To: tech-talk epics
Subject: C863 can't answer the PI GCS commands

 

Hi,

    I applied the PIGCS2Src in motorR6-8 to the C863 motor controller.

    There was an error as starting up:

        drvAsynIPPortConfigure(“C863”, "192.168.127.1:4001",0,0,0)

        PI_GCS2_CreateController(“PI”,"C863","1”,"","","100”,"1000”)

        PIGCSController: sendAndReceive error calling writeRead, output=*IDN? error=192.168.127.12:4001 timeout:Resource temporarily.

        read from C863:

        PIasynController: unknown controller type C863:

 

    I have tested C863 with old PI module . It worked well.

    It seemed that  C863 hadn’t answer the command.

 

    PI GCS manual has an introduce  “With current Mercury™ firmware, GCS command support is implemented by a Windows DLL which translates the GCS commands to the native commands the current firmware understands”.

    Does that mean: sending GCS command to C863 must use PI_Mercury_GCS_DLL.lib instead asynOctetSyncIO->write?

   

 

Qingru Mi

SSRF