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: Lambda EMS mismatch errors |
From: | Anthony Andrews <[email protected]> |
To: | Rod Nussbaumer <[email protected]> |
Cc: | Yujong Kim <[email protected]>, [email protected] |
Date: | Thu, 25 Oct 2012 17:44:36 -0600 |
Tony:
It looks like the power supply echoes the commands that are sent to it. You will need to craft your protocol(s) to read these echoed commands, or there may be a way to turn off the echoes.
Rod Nussbaumer
ISAC Controls, TRIUMF
Vancouver, Canada
On 10/23/2012 05:17 PM, Anthony Andrews wrote:
###########################################################################
## Start any sequence programs
#seq sncxxx,"user=tonyHost"
epics> 2012/10/23 18:05:13.924 xxx.yyy.zzz.aaa:4008 write 3
MC\n
2012/10/23 18:05:13.936 xxx.yyy.zzz.aaa:4008 read 5
MC\n\r\000
2012/10/23 18:05:13.936 P8 LamEMS:ADDR:CURR_M: Input "MC" mismatch after
0 bytes
2012/10/23 18:05:13.936 P8 LamEMS:ADDR:CURR_M: got "MC" where "Current =
" was expected
2012/10/23 18:05:13.936 xxx.yyy.zzz.aaa:4008 write 3
MV\n
Attachment:
telnet.png
Description: PNG image
Attachment:
EMS_01.vdb
Description: Binary data
Attachment:
EMS_01.proto
Description: Binary data