1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: C863 can't answer the PI GCS commands |
From: | "Goetze, Kurt A." <[email protected]> |
To: | Mi Qingru <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Wed, 13 Nov 2013 14:52:14 +0000 |
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: [email protected] [mailto:[email protected]]
On Behalf Of Mi Qingru 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 |