Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20192020  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  <20192020 
<== Date ==> <== Thread ==>

Subject: RE: Weird stream device behavior when using the IOC shell's exit function
From: Abdalla Ahmad via Tech-talk <tech-talk@aps.anl.gov>
To: Mark Rivers <rivers@cars.uchicago.edu>, 'Dirk Zimoch' <dirk.zimoch@psi.ch>
Cc: "'tech-talk@aps.anl.gov'" <tech-talk@aps.anl.gov>
Date: Thu, 7 Feb 2019 08:52:17 +0000

Hello Mark

 

Attached is the output of asyn trace mask on one of the controllers. The IOC is working fine even after the exit function so I had to press Ctrl-C at some point.

 

For your suggestion regarding different configuration: asyn 4.18 can't be built with base 3.15.6 because there is a line in the asyn Gpib module that sets an event record value (a char array) to an integer (which is what was in 3.14.12.3). And stream 2.5.1 with base 3.15.6 complains about two headers it can't find: wdlib.h and streamReferences. According to streamDevice/src/Makefile, StreamReferences should have been generated from CONFIG_STREAM but it's not.

 

I think for now I will stick with the old setup: base 3.14.12.3, asyn 4.18 and stream 2.5.1.

 

Since the same setup worked with the agilent controllers (serially interfaced and connected via terminal servers), A question came up to my mind, could the standard telnet port be related to this deadlock?

 

Best Regards,

Abdalla.

 

From: Mark Rivers [mailto:rivers@cars.uchicago.edu]
Sent: Wednesday, February 06, 2019 8:09 PM
To: Abdalla Ahmad <abdalla.ahmad@sesame.org.jo>; 'Dirk Zimoch' <dirk.zimoch@psi.ch>
Cc: 'tech-talk@aps.anl.gov' <tech-talk@aps.anl.gov>
Subject: RE: Weird stream device behavior when using the IOC shell's exit function

 

The first test I would like you to run is with the recent code, ie. base 3.15.6, asyn 4.33 and stream 2.8.8. Set asynTraceIOMask=2 and asynTraceMask=9 for the TCP port.  Then we will see all communication with the device.  When that is running type “exit”.  Send the complete output, for a few seconds before you type exit, and a few seconds after you type exit.

 

Mark

 

 

From: Mark Rivers
Sent: Wednesday, February 6, 2019 8:32 AM
To: 'Abdalla Ahmad' <abdalla.ahmad@sesame.org.jo>; Dirk Zimoch <dirk.zimoch@psi.ch>
Cc: tech-talk@aps.anl.gov
Subject: RE: Weird stream device behavior when using the IOC shell's exit function

 

Ø  I thought the while loop is causing the block so I removed the while loop and put the poll function just like what is done in version 4.18 but I got the same behavior.

Ø  So I think that poll here never returns.

Ø  As the documentation says, poll will block if a negative timeout is provided.

Ø  So I think somehow stream device is passing a negative timeout but I could not verify the timeout value received in the readIt function.

 

You could edit that code to print the value of readPollmsec just before the while() statement.  That will tell you if stream device is passing a negative timeout.  The purpose of the loop is to retry the poll in case it terminates early with errno=EINTR.  But it will only loop for readPollsec ms at longest.

 

I suggest you also try independently changing the versions of asyn and Stream to see which has changed to cause the problem.  I suggest using these 2 configurations:

 

-          Base 3.15.6, asyn 4.16 Stream 2.8.8

-          Base 3.15.6, asyn 4.33, Stream 2.5.1

 

I have a simple StreamDevice IOC that I will test today to see if I can reproduce the problem.

 

Mark

 

 

From: Abdalla Ahmad <abdalla.ahmad@sesame.org.jo>
Sent: Wednesday, February 6, 2019 6:45 AM
To: Mark Rivers <rivers@cars.uchicago.edu>; Dirk Zimoch <dirk.zimoch@psi.ch>
Cc: tech-talk@aps.anl.gov
Subject: RE: Weird stream device behavior when using the IOC shell's exit function

 

Hello Mark

 

Just would like to share some findings:

 

I cloned the latest stream device 2.8.8 and I still get the same behavior. So I investigated the backtrace a little bit specifically the thread you mentioned it is causing the deadlock.

 

In asyn 4.33 file asyn/drvAsynSerial/drvAsynIPPort.c function "readIt", line 725 is the poll function call causing the deadlock. I thought the while loop is causing the block so I removed the while loop and put the poll function just like what is done in version 4.18 but I got the same behavior. So I think that poll here never returns.

 

As the documentation says, poll will block if a negative timeout is provided. So I think somehow stream device is passing a negative timeout but I could not verify the timeout value received in the readIt function.

 

Best Regards,

Abdalla.

 

From: Abdalla Ahmad
Sent: Wednesday, February 06, 2019 9:12 AM
To: 'Mark Rivers' <rivers@cars.uchicago.edu>
Cc: tech-talk@aps.anl.gov
Subject: RE: Weird stream device behavior when using the IOC shell's exit function

 

Hello Mark

 

This is just to confirm that I re-built the old setup on CentOS 7 x64; base 3.14.12.3, asyn 4.18 and stream 2.5.1 and everything works fine. I don't even get the asynWrite error messages.

 

Best Regards,

Abdalla.

 

From: Mark Rivers [mailto:rivers@cars.uchicago.edu]
Sent: Tuesday, February 05, 2019 5:47 PM
To: Abdalla Ahmad <abdalla.ahmad@sesame.org.jo>
Cc: tech-talk@aps.anl.gov
Subject: RE: Weird stream device behavior when using the IOC shell's exit function

 

You can now use asynSetTraceIOMask and asynSetTraceMask to monitor the communication.  If you enable that before you type “exit” we can see what is happening.

 

I view the problem exiting the IOC as an annoyance but not something that has to be fixed immediately.  You can always just type CTRL-C.

 

Mark

 

 

From: Abdalla Ahmad <abdalla.ahmad@sesame.org.jo>
Sent: Tuesday, February 5, 2019 8:17 AM
To: Mark Rivers <rivers@cars.uchicago.edu>
Cc: tech-talk@aps.anl.gov
Subject: Re: Weird stream device behavior when using the IOC shell's exit function

 

Well I never thought of checking the client, I will test it and come back.

I forgot to mention that the device is being controlled through standard telnet port 23. Does it make a difference for stream device to work with a well known port number?

 

On Tue, Feb 5, 2019 at 4:14 PM +0200, "Mark Rivers" <rivers@cars.uchicago.edu> wrote:

Is your device working correctly, or is it timing out? I wonder if the exit problem is because Stream is polling constantly and never releasing the lock so the epicsExit thread can never run?
 
Mark
 
 
Sent from my iPhone
 
> On Feb 5, 2019, at 7:23 AM, Abdalla Ahmad  wrote:
> 
> Hello Mark
> 
> Including asyn.dbd file did the trick. Looking forward for your thoughts on the exit issue.
> 
> Thank you for your time.
> Abdalla.
> 
> -----Original Message-----
> From: Mark Rivers [mailto:rivers@cars.uchicago.edu] 
> Sent: Tuesday, February 05, 2019 3:19 PM
> To: Abdalla Ahmad 
> Cc: tech-talk@aps.anl.gov
> Subject: Re: Weird stream device behavior when using the IOC shell's exit function
> 
> OK, I understand the problem with the missing asyn commands.  You do have these commands in your help output:
> 
> 
> drvAsynIPPortConfigure          drvAsynIPServerPortConfigure
> drvAsynSerialPortConfigure
> 
> 
> That tells me that your application dbd file is including drvAsynIPPort.dbd and drvAsynSerialPort.dbd, but it is not including asyn.dbd.  It also explains why it used to work, and now it does not.  Previously drvAsynIPPort.dbd and drvAsynSerialPort.dbd themselves included asyn.dbd.  However, recent EPICS base releases no longer allow a dbd file to be loaded more than once, so asyn.dbd was removed from drvAsynIPPort.dbd and drvAsynSerialPort.dbd.  Now your application must explicitly include asyn.dbd.
> 
> 
> I think this is independent of the IOC exiting issue, but please include asyn.dbd and see if you still have that problem.
> 
> 
> Mark
> 
> 
> 
> ________________________________
> From: Abdalla Ahmad 
> Sent: Tuesday, February 5, 2019 6:34 AM
> To: Mark Rivers
> Cc: tech-talk@aps.anl.gov
> Subject: RE: Weird stream device behavior when using the IOC shell's exit function
> 
> Hi Mark
> 
> I attached the help output in help.txt. For the database nothing is I/O scanned, standard 1 second rate as in the attached database. I also checked the protocol file but nothing seems strange.
> 
> While writing the email I thought of increasing the scan rate to 5 seconds and it works. I still get the same asynError in write but the IOC eventually exits. Even if it exits gracefully now, it is still a problem because we need the scan rate to match the IMG ones. As I told you before it used to work on the old setup without any problems. Is there anything we can investigate?
> 
> Best Regards,
> Abdalla.
> 
> -----Original Message-----
> From: Mark Rivers [mailto:rivers@cars.uchicago.edu]
> Sent: Tuesday, February 05, 2019 2:20 PM
> To: Abdalla Ahmad 
> Cc: tech-talk@aps.anl.gov
> Subject: Re: Weird stream device behavior when using the IOC shell's exit function
> 
> Hi Abdalla,
> 
> 
> Your IOC is clearly built OK with asyn because you have threads that are in asyn functions.
> 
> 
> Thread 13 (Thread 0x7fffed943700 (LWP 29173)):
> #0  0x00007ffff6034f0d in poll () from /lib64/libc.so.6
> #1  0x00007ffff7926c14 in readIt (drvPvt=0x70eb30, pasynUser=0x79e4a8, data="" ">", maxchars=2048, nbytesTransfered=0x7fffed942ba0, gotEom=0x7fffed942b90)
>    at ../../asyn/drvAsynSerial/drvAsynIPPort.c:726
> #2  0x00007ffff7930886 in readIt (drvPvt=0x70fbb0, pasynUser=0x79e4a8, data="" ">", maxchars=, nbytesTransfered=0x7fffed942ba0, eomReason=0x7fffed942b90)
>    at ../../asyn/interfaces/asynOctetBase.c:233
> #3  0x00007ffff793a563 in readIt (ppvt=0x70fcb0, pasynUser=0x79e4a8, data="" ">", maxchars=63, nbytesTransfered=0x7fffed942ca0, eomReason=0x7fffed942c70)
>    at ../../asyn/miscellaneous/asynInterposeEos.c:231
> #4  0x00007ffff7bab5f5 in AsynDriverInterface::readHandler (this=this@entry=0x79e2e0) at ../AsynDriverInterface.cc:960
> #5  0x00007ffff7bacd08 in handleRequest (pasynUser=) at ../AsynDriverInterface.cc:1503
> #6  0x00007ffff791c9f3 in portThread (pport=0x70ece0) at ../../asyn/asynDriver/asynManager.c:902
> #7  0x00007ffff6b6f7fc in start_routine (arg=0x70f290) at ../../../src/libCom/osi/os/posix/osdThread.c:403
> #8  0x00007ffff5d2ce25 in start_thread () from /lib64/libpthread.so.0
> #9  0x00007ffff603fbad in clone () from /lib64/libc.so.6
> 
> 
> 
> Thread 12 (Thread 0x7fffeda44700 (LWP 29172)):
> #0  0x00007ffff5d30995 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
> #1  0x00007ffff6b71f3b in epicsEventWait (pevent=0x70d520) at ../../../src/libCom/osi/os/posix/osdEvent.c:103
> #2  0x00007ffff6b6b029 in epicsEventMustWait (id=) at ../../../src/libCom/osi/epicsEvent.cpp:125
> #3  0x00007ffff791c40c in portThread (pport=0x70d050) at ../../asyn/asynDriver/asynManager.c:788
> #4  0x00007ffff6b6f7fc in start_routine (arg=0x70d590) at ../../../src/libCom/osi/os/posix/osdThread.c:403
> #5  0x00007ffff5d2ce25 in start_thread () from /lib64/libpthread.so.0
> #6  0x00007ffff603fbad in clone () from /lib64/libc.so.6
> 
> I don't understand why the asyn iocsh commands would not be available.
> 
> 
> Please send the complete output of the iocsh "help" command.
> 
> 
> The hang at shutdown appears to be caused by this thread:
> 
> 
> Thread 1 (Thread 0x7ffff7fda740 (LWP 29161)):
> #0  0x00007ffff5d3351d in __lll_lock_wait () from /lib64/libpthread.so.0
> #1  0x00007ffff5d2ee36 in _L_lock_870 () from /lib64/libpthread.so.0
> #2  0x00007ffff5d2ed2f in pthread_mutex_lock () from /lib64/libpthread.so.0
> #3  0x00007ffff6b71a76 in mutexLock (id=0x70ef60) at ../../../src/libCom/osi/os/posix/osdMutex.c:46
> #4  epicsMutexOsdLock (pmutex=0x70ef60) at ../../../src/libCom/osi/os/posix/osdMutex.c:130
> #5  0x00007ffff7917e9b in lockPort (pasynUser=0x710668) at ../../asyn/asynDriver/asynManager.c:1741
> #6  0x00007ffff7925876 in cleanup (arg=0x70eb30) at ../../asyn/drvAsynSerial/drvAsynIPPort.c:246
> #7  0x00007ffff6b65ce3 in epicsExitCallAtExitsPvt (pep=) at ../../../src/libCom/misc/epicsExit.c:95
> #8  epicsExitCallAtExits () at ../../../src/libCom/misc/epicsExit.c:113
> #9  0x00007ffff6b66088 in epicsExit (status=0) at ../../../src/libCom/misc/epicsExit.c:181
> #10 0x000000000040544d in main (argc=, argv=) at ../iocMain.cpp:21
> 
> 
> So the epicsExit function is hung up in the drvAsynIPPort::cleanup function.  It has called lockPort, but cannot get that mutex.
> 
> 
> No other thread is waiting for a mutex, so it is not a traditional deadlock.  But it seems that some other thread does have that mutex and is blocking the epicsExit thread from continuing.
> 
> 
> It is probably this thread, which is in StreamDevice.
> 
> 
> Thread 13 (Thread 0x7fffed943700 (LWP 29173)):
> #0  0x00007ffff6034f0d in poll () from /lib64/libc.so.6
> #1  0x00007ffff7926c14 in readIt (drvPvt=0x70eb30, pasynUser=0x79e4a8, data="" ">", maxchars=2048, nbytesTransfered=0x7fffed942ba0, gotEom=0x7fffed942b90)
>    at ../../asyn/drvAsynSerial/drvAsynIPPort.c:726
> #2  0x00007ffff7930886 in readIt (drvPvt=0x70fbb0, pasynUser=0x79e4a8, data="" ">", maxchars=, nbytesTransfered=0x7fffed942ba0, eomReason=0x7fffed942b90)
>    at ../../asyn/interfaces/asynOctetBase.c:233
> #3  0x00007ffff793a563 in readIt (ppvt=0x70fcb0, pasynUser=0x79e4a8, data="" ">", maxchars=63, nbytesTransfered=0x7fffed942ca0, eomReason=0x7fffed942c70)
>    at ../../asyn/miscellaneous/asynInterposeEos.c:231
> #4  0x00007ffff7bab5f5 in AsynDriverInterface::readHandler (this=this@entry=0x79e2e0) at ../AsynDriverInterface.cc:960
> #5  0x00007ffff7bacd08 in handleRequest (pasynUser=) at ../AsynDriverInterface.cc:1503
> #6  0x00007ffff791c9f3 in portThread (pport=0x70ece0) at ../../asyn/asynDriver/asynManager.c:902
> #7  0x00007ffff6b6f7fc in start_routine (arg=0x70f290) at ../../../src/libCom/osi/os/posix/osdThread.c:403
> #8  0x00007ffff5d2ce25 in start_thread () from /lib64/libpthread.so.0
> #9  0x00007ffff603fbad in clone () from /lib64/libc.so.6
> 
> 
> Do you have StreamDevice records that are I/O Intr scanned?
> 
> 
> Mark
> 
> 
> 
> 
> ________________________________
> From: Abdalla Ahmad 
> Sent: Tuesday, February 5, 2019 5:53 AM
> To: Mark Rivers
> Cc: tech-talk@aps.anl.gov
> Subject: RE: Weird stream device behavior when using the IOC shell's exit function
> 
> 
> Hi Mark
> 
> 
> 
> No command available which starts with asyn. I cloned the latest asyn from github with the same behavior.
> 
> For the gdb part, attached is the stack trace from gdb for all pending threads.
> 
> 
> 
> Best Regards,
> 
> Abdalla.
> 
> 
> 
> From: Mark Rivers [mailto:rivers@cars.uchicago.edu]
> Sent: Monday, February 04, 2019 4:52 PM
> To: Abdalla Ahmad 
> Cc: tech-talk@aps.anl.gov
> Subject: RE: Weird stream device behavior when using the IOC shell's exit function
> 
> 
> 
> At the iocsh prompt when the IOC is still running type the command
> 
> 
> 
> help
> 
> 
> 
> It should show a complete list of commands that the iocsh understands.  See which ones start with "asyn".
> 
> 
> 
> Mark
> 
> 
> 
> 
> 
> From: Abdalla Ahmad <abdalla.ahmad@sesame.org.jo>
> Sent: Monday, February 4, 2019 8:44 AM
> To: Mark Rivers <rivers@cars.uchicago.edu>
> Cc: tech-talk@aps.anl.gov
> Subject: Re: Weird stream device behavior when using the IOC shell's exit function
> 
> 
> 
> Hello Mark
> 
> I will apply the gdb tip and get back to you. For the asyn commands, I don't see any asyn command when I type exit.
> 
> Get Outlook for Android
> 
> 
> 
> 
> 
> On Mon, Feb 4, 2019 at 4:33 PM +0200, "Mark Rivers" <rivers@cars.uchicago.edu> wrote:
> 
> Hi Abdalla,
> 
> 
> 
>> asynError in write. Asyn driver says: device:port disconnected.
> 
> 
> 
> During IOC shutdown asyn does close all TCP ports.  However, record processing should have already been shut down, so I don't understand why you are getting that message from Stream.
> 
> 
> 
> Another problem we are facing with this new setup is that I can't find some asyn IOC shell function like asynTraceMask for example. The IOC is configured properly in RELEASE and src/Makefile. Is there anything we miss in the new setup?
> 
> 
> 
>> But eventually the IOC exits. For the gamma controllers we get something really strange.
> 
>> There a point in the database where the IOC never exits, the exit command just freezes and Ctrl-C is the only way to shut down the IOC.
> 
> 
> 
> I don't think I have seen that with Stream on any version of Stream/asyn/base that I have used.  That includes base 3.14.12, 3.15.5, 7.0.2.
> 
> 
> 
> If you run the IOC with gdb then when you type exit and it hangs do the following:
> 
> 
> 
> - Type Ctrl-C
> 
> - Enter the gdb command
> 
> thread apply all bt
> 
> 
> 
> That will show you the current stack trace for all threads.  You can then see what is blocking the threads.
> 
> 
> 
>> Another problem we are facing with this new setup is that I can't find some asyn IOC shell function like asynTraceMask for example.
> 
>> The IOC is configured properly in RELEASE and src/Makefile. Is there anything we miss in the new setup?
> 
> 
> 
> The command is not "asynTraceMask" it is "asynSetTraceMask" or "asynSetTraceIOMask".
> 
> 
> 
> What asyn commands do you see if you type "help" at the iocsh prompt?
> 
> 
> 
> Mark
> 
> 
> 
> ________________________________________
> 
> From: tech-talk-bounces@aps.anl.gov  on behalf of Abdalla Ahmad via Tech-talk
> 
> Sent: Monday, February 4, 2019 1:41 AM
> 
> To: tech-talk@aps.anl.gov
> 
> Subject: Weird stream device behavior when using the IOC shell's exit function
> 
> 
> 
> Hi
> 
> 
> 
> We are using the following setup to test control of the agilent XGS gauge controllers and Gamma ion pump controllers:
> 
> 1.       EPICS Base 3.15.6
> 
> 2.       Asyn R4-33
> 
> 3.       Stream R2-7-7c
> 
> 
> 
> For agilent controllers we get the following error:
> 
> 
> 
> asynError in write. Asyn driver says: device:port disconnected.
> 
> 
> 
> But eventually the IOC exits. For the gamma controllers we get something really strange. There a point in the database where the IOC never exits, the exit command just freezes and Ctrl-C is the only way to shut down the IOC. For now I can see that this behavior occurs because more DB substitutions are configured which means more PVs and more controllers. But that was not the case when we had:
> 
> 1.       EPICS Base 3.14.12.3
> 
> 2.       Asyn R4-18
> 
> 3.       Stream R2-5-1
> 
> 
> 
> Where the IOC exits with no errors or freezing. Should we upgrade our support modules or change the EPICS base?
> 
> 
> 
> Another problem we are facing with this new setup is that I can't find some asyn IOC shell function like asynTraceMask for example. The IOC is configured properly in RELEASE and src/Makefile. Is there anything we miss in the new setup?
> 
> 
> 
> Best Regards,
> 
> 
> 
> Abdalla Ahmad
> 
> Control Engineer
> 
> SESAME
> 
> Allan, Jordan.
> 
> Tel: (+962-5) 3511348 , ext. 265
> 
> Fax: (+962-5) 3511423
> 
> Mob: (+962-7)88183296
> 
> http://www.sesame.org.jo/
> 
> 
</rivers@cars.uchicago.edu</rivers@cars.uchicago.edu</abdalla.ahmad@sesame.org.jo
epics> 2019/02/07 10:28:48.120 SR-IPC1:23 read 1
>
2019/02/07 10:28:48.220 SR-IPC1:23 read 13
OK 00 2721\r\r\n
2019/02/07 10:28:48.221 SR-IPC1:23 write 9
cmd 0D 1\r
2019/02/07 10:28:48.240 SR-IPC1:23 read 1
>
2019/02/07 10:28:48.340 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:48.341 SR-IPC1:23 write 9
cmd 0D 2\r
2019/02/07 10:28:48.360 SR-IPC1:23 read 1
>
2019/02/07 10:28:48.460 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:48.461 SR-IPC1:23 write 9
cmd 0D 3\r
2019/02/07 10:28:48.480 SR-IPC1:23 read 1
>
2019/02/07 10:28:48.587 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:48.588 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:28:48.607 SR-IPC1:23 read 1
>
2019/02/07 10:28:48.707 SR-IPC1:23 read 21
OK 00 3.4E-06 AMPS\r\r\n
2019/02/07 10:28:48.708 SR-IPC1:23 write 9
cmd 0C 1\r
2019/02/07 10:28:48.727 SR-IPC1:23 read 1
>
2019/02/07 10:28:48.830 SR-IPC1:23 read 13
OK 00 5008\r\r\n
2019/02/07 10:28:48.831 SR-IPC1:23 write 9
cmd 0A 3\r
2019/02/07 10:28:48.850 SR-IPC1:23 read 1
>
2019/02/07 10:28:48.950 SR-IPC1:23 read 21
OK 00 9.7E-07 AMPS\r\r\n
2019/02/07 10:28:48.951 SR-IPC1:23 write 9
cmd 0B 3\r
2019/02/07 10:28:48.970 SR-IPC1:23 read 1
>
2019/02/07 10:28:49.072 SR-IPC1:23 read 21
OK 00 4.5E-10 MBAR\r\r\n
2019/02/07 10:28:49.073 SR-IPC1:23 write 9
cmd 0C 3\r
2019/02/07 10:28:49.092 SR-IPC1:23 read 1
>
2019/02/07 10:28:49.192 SR-IPC1:23 read 13
OK 00 6982\r\r\n
2019/02/07 10:28:49.193 SR-IPC1:23 write 9
cmd 61 1\r
2019/02/07 10:28:49.212 SR-IPC1:23 read 1
>
2019/02/07 10:28:49.312 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:49.313 SR-IPC1:23 write 9
cmd 61 2\r
2019/02/07 10:28:49.332 SR-IPC1:23 read 1
>
2019/02/07 10:28:49.432 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:49.433 SR-IPC1:23 write 9
cmd 61 3\r
2019/02/07 10:28:49.452 SR-IPC1:23 read 1
>
2019/02/07 10:28:49.552 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:49.553 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:28:49.572 SR-IPC1:23 read 1
>
2019/02/07 10:28:49.676 SR-IPC1:23 read 21
OK 00 3.5E-06 AMPS\r\r\n
2019/02/07 10:28:49.677 SR-IPC1:23 write 9
cmd 0B 1\r
2019/02/07 10:28:49.696 SR-IPC1:23 read 1
>
2019/02/07 10:28:49.796 SR-IPC1:23 read 21
OK 00 2.3E-09 MBAR\r\r\n
2019/02/07 10:28:49.797 SR-IPC1:23 write 9
cmd 0C 1\r
2019/02/07 10:28:49.816 SR-IPC1:23 read 1
>
2019/02/07 10:28:49.923 SR-IPC1:23 read 13
OK 00 5000\r\r\n
2019/02/07 10:28:49.924 SR-IPC1:23 write 9
cmd 0A 2\r
2019/02/07 10:28:49.943 SR-IPC1:23 read 1
>
2019/02/07 10:28:50.043 SR-IPC1:23 read 21
OK 00 2.1E-10 AMPS\r\r\n
2019/02/07 10:28:50.044 SR-IPC1:23 write 9
cmd 0B 2\r
2019/02/07 10:28:50.063 SR-IPC1:23 read 1
>
2019/02/07 10:28:50.163 SR-IPC1:23 read 21
OK 00 1.3E-11 MBAR\r\r\n
2019/02/07 10:28:50.164 SR-IPC1:23 write 9
cmd 0C 2\r
2019/02/07 10:28:50.183 SR-IPC1:23 read 1
>
2019/02/07 10:28:50.287 SR-IPC1:23 read 13
OK 00 2999\r\r\n
2019/02/07 10:28:50.288 SR-IPC1:23 write 9
cmd 0D 1\r
2019/02/07 10:28:50.307 SR-IPC1:23 read 1
>
2019/02/07 10:28:50.407 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:50.409 SR-IPC1:23 write 9
cmd 0D 2\r
2019/02/07 10:28:50.427 SR-IPC1:23 read 1
>
2019/02/07 10:28:50.529 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:50.530 SR-IPC1:23 write 9
cmd 0D 3\r
2019/02/07 10:28:50.549 SR-IPC1:23 read 1
>
2019/02/07 10:28:50.649 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:50.650 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:28:50.669 SR-IPC1:23 read 1
>
2019/02/07 10:28:50.773 SR-IPC1:23 read 21
OK 00 3.3E-06 AMPS\r\r\n
2019/02/07 10:28:50.774 SR-IPC1:23 write 9
cmd 0B 1\r
2019/02/07 10:28:50.793 SR-IPC1:23 read 1
>
2019/02/07 10:28:50.893 SR-IPC1:23 read 21
OK 00 2.1E-09 MBAR\r\r\n
2019/02/07 10:28:50.894 SR-IPC1:23 write 9
cmd 0A 3\r
2019/02/07 10:28:50.913 SR-IPC1:23 read 1
>
2019/02/07 10:28:51.017 SR-IPC1:23 read 21
OK 00 9.6E-07 AMPS\r\r\n
2019/02/07 10:28:51.018 SR-IPC1:23 write 9
cmd 0B 3\r
2019/02/07 10:28:51.037 SR-IPC1:23 read 1
>
2019/02/07 10:28:51.137 SR-IPC1:23 read 21
OK 00 4.5E-10 MBAR\r\r\n
2019/02/07 10:28:51.139 SR-IPC1:23 write 9
cmd 0C 3\r
2019/02/07 10:28:51.157 SR-IPC1:23 read 1
>
2019/02/07 10:28:51.257 SR-IPC1:23 read 13
OK 00 6982\r\r\n
2019/02/07 10:28:51.258 SR-IPC1:23 write 9
cmd 61 1\r
2019/02/07 10:28:51.277 SR-IPC1:23 read 1
>
2019/02/07 10:28:51.377 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:51.379 SR-IPC1:23 write 9
cmd 61 2\r
2019/02/07 10:28:51.397 SR-IPC1:23 read 1
>
2019/02/07 10:28:51.497 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:51.498 SR-IPC1:23 write 9
cmd 61 3\r
2019/02/07 10:28:51.517 SR-IPC1:23 read 1
>
2019/02/07 10:28:51.617 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:51.619 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:28:51.637 SR-IPC1:23 read 1
>
2019/02/07 10:28:51.737 SR-IPC1:23 read 21
OK 00 3.4E-06 AMPS\r\r\n
2019/02/07 10:28:51.739 SR-IPC1:23 write 9
cmd 0C 1\r
2019/02/07 10:28:51.757 SR-IPC1:23 read 1
>
2019/02/07 10:28:51.857 SR-IPC1:23 read 13
OK 00 5000\r\r\n
2019/02/07 10:28:51.859 SR-IPC1:23 write 9
cmd 0A 2\r
2019/02/07 10:28:51.877 SR-IPC1:23 read 1
>
2019/02/07 10:28:51.977 SR-IPC1:23 read 21
OK 00 3.3E-05 AMPS\r\r\n
2019/02/07 10:28:51.978 SR-IPC1:23 write 9
cmd 0B 2\r
2019/02/07 10:28:51.997 SR-IPC1:23 read 1
>
2019/02/07 10:28:52.099 SR-IPC1:23 read 21
OK 00 2.7E-08 MBAR\r\r\n
2019/02/07 10:28:52.100 SR-IPC1:23 write 9
cmd 0C 2\r
2019/02/07 10:28:52.119 SR-IPC1:23 read 1
>
2019/02/07 10:28:52.224 SR-IPC1:23 read 13
OK 00 5250\r\r\n
2019/02/07 10:28:52.226 SR-IPC1:23 write 9
cmd 0D 1\r
2019/02/07 10:28:52.244 SR-IPC1:23 read 1
>
2019/02/07 10:28:52.344 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:52.346 SR-IPC1:23 write 9
cmd 0D 2\r
2019/02/07 10:28:52.364 SR-IPC1:23 read 1
>
2019/02/07 10:28:52.466 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:52.467 SR-IPC1:23 write 9
cmd 0D 3\r
2019/02/07 10:28:52.486 SR-IPC1:23 read 1
>
2019/02/07 10:28:52.586 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:52.587 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:28:52.606 SR-IPC1:23 read 1
>
2019/02/07 10:28:52.706 SR-IPC1:23 read 21
OK 00 3.3E-06 AMPS\r\r\n
2019/02/07 10:28:52.707 SR-IPC1:23 write 9
cmd 0B 1\r
2019/02/07 10:28:52.726 SR-IPC1:23 read 1
>
2019/02/07 10:28:52.833 SR-IPC1:23 read 21
OK 00 2.2E-09 MBAR\r\r\n
2019/02/07 10:28:52.834 SR-IPC1:23 write 9
cmd 0A 3\r
2019/02/07 10:28:52.852 SR-IPC1:23 read 1
>
2019/02/07 10:28:52.952 SR-IPC1:23 read 21
OK 00 9.6E-07 AMPS\r\r\n
2019/02/07 10:28:52.953 SR-IPC1:23 write 9
cmd 0B 3\r
2019/02/07 10:28:52.972 SR-IPC1:23 read 1
>
2019/02/07 10:28:53.072 SR-IPC1:23 read 21
OK 00 4.5E-10 MBAR\r\r\n
2019/02/07 10:28:53.073 SR-IPC1:23 write 9
cmd 0C 3\r
2019/02/07 10:28:53.092 SR-IPC1:23 read 1
>
2019/02/07 10:28:53.192 SR-IPC1:23 read 13
OK 00 6981\r\r\n
2019/02/07 10:28:53.193 SR-IPC1:23 write 9
cmd 61 1\r
2019/02/07 10:28:53.212 SR-IPC1:23 read 1
>
2019/02/07 10:28:53.312 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:53.313 SR-IPC1:23 write 9
cmd 61 2\r
2019/02/07 10:28:53.332 SR-IPC1:23 read 1
>
2019/02/07 10:28:53.432 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:53.433 SR-IPC1:23 write 9
cmd 61 3\r
2019/02/07 10:28:53.452 SR-IPC1:23 read 1
>
2019/02/07 10:28:53.552 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:53.553 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:28:53.572 SR-IPC1:23 read 1
>
2019/02/07 10:28:53.676 SR-IPC1:23 read 21
OK 00 3.4E-06 AMPS\r\r\n
2019/02/07 10:28:53.677 SR-IPC1:23 write 9
cmd 0C 1\r
2019/02/07 10:28:53.696 SR-IPC1:23 read 1
>
2019/02/07 10:28:53.796 SR-IPC1:23 read 13
OK 00 4993\r\r\n
2019/02/07 10:28:53.797 SR-IPC1:23 write 9
cmd 0A 2\r
2019/02/07 10:28:53.816 SR-IPC1:23 read 1
>
2019/02/07 10:28:53.919 SR-IPC1:23 read 21
OK 00 1.3E-07 AMPS\r\r\n
2019/02/07 10:28:53.920 SR-IPC1:23 write 9
cmd 0B 2\r
2019/02/07 10:28:53.939 SR-IPC1:23 read 1
>
2019/02/07 10:28:54.039 SR-IPC1:23 read 21
OK 00 1.3E-11 MBAR\r\r\n
2019/02/07 10:28:54.040 SR-IPC1:23 write 9
cmd 0C 2\r
2019/02/07 10:28:54.059 SR-IPC1:23 read 1
>
2019/02/07 10:28:54.162 SR-IPC1:23 read 13
OK 00 7115\r\r\n
2019/02/07 10:28:54.163 SR-IPC1:23 write 9
cmd 0D 1\r
2019/02/07 10:28:54.182 SR-IPC1:23 read 1
>
2019/02/07 10:28:54.282 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:54.283 SR-IPC1:23 write 9
cmd 0D 2\r
2019/02/07 10:28:54.302 SR-IPC1:23 read 1
>
2019/02/07 10:28:54.402 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:54.403 SR-IPC1:23 write 9
cmd 0D 3\r
2019/02/07 10:28:54.422 SR-IPC1:23 read 1
>
2019/02/07 10:28:54.522 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:54.523 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:28:54.542 SR-IPC1:23 read 1
>
2019/02/07 10:28:54.643 SR-IPC1:23 read 21
OK 00 3.6E-06 AMPS\r\r\n
2019/02/07 10:28:54.644 SR-IPC1:23 write 9
cmd 0B 1\r
2019/02/07 10:28:54.663 SR-IPC1:23 read 1
>
2019/02/07 10:28:54.763 SR-IPC1:23 read 21
OK 00 2.4E-09 MBAR\r\r\n
2019/02/07 10:28:54.764 SR-IPC1:23 write 9
cmd 0C 1\r
2019/02/07 10:28:54.783 SR-IPC1:23 read 1
>
2019/02/07 10:28:54.883 SR-IPC1:23 read 13
OK 00 5005\r\r\n
2019/02/07 10:28:54.884 SR-IPC1:23 write 9
cmd 0A 3\r
2019/02/07 10:28:54.903 SR-IPC1:23 read 1
>
2019/02/07 10:28:55.007 SR-IPC1:23 read 21
OK 00 9.6E-07 AMPS\r\r\n
2019/02/07 10:28:55.008 SR-IPC1:23 write 9
cmd 0B 3\r
2019/02/07 10:28:55.027 SR-IPC1:23 read 1
>
2019/02/07 10:28:55.127 SR-IPC1:23 read 21
OK 00 4.5E-10 MBAR\r\r\n
2019/02/07 10:28:55.128 SR-IPC1:23 write 9
cmd 0C 3\r
2019/02/07 10:28:55.147 SR-IPC1:23 read 1
>
2019/02/07 10:28:55.247 SR-IPC1:23 read 13
OK 00 6984\r\r\n
2019/02/07 10:28:55.248 SR-IPC1:23 write 9
cmd 61 1\r
2019/02/07 10:28:55.267 SR-IPC1:23 read 1
>
2019/02/07 10:28:55.367 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:55.368 SR-IPC1:23 write 9
cmd 61 2\r
2019/02/07 10:28:55.387 SR-IPC1:23 read 1
>
2019/02/07 10:28:55.487 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:55.488 SR-IPC1:23 write 9
cmd 61 3\r
2019/02/07 10:28:55.507 SR-IPC1:23 read 1
>
2019/02/07 10:28:55.615 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:55.616 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:28:55.642 SR-IPC1:23 read 1
>
2019/02/07 10:28:55.742 SR-IPC1:23 read 21
OK 00 3.4E-06 AMPS\r\r\n
2019/02/07 10:28:55.743 SR-IPC1:23 write 9
cmd 0B 1\r
2019/02/07 10:28:55.762 SR-IPC1:23 read 1
>
2019/02/07 10:28:55.864 SR-IPC1:23 read 21
OK 00 2.3E-09 MBAR\r\r\n
2019/02/07 10:28:55.865 SR-IPC1:23 write 9
cmd 0A 2\r
2019/02/07 10:28:55.883 SR-IPC1:23 read 1
>
2019/02/07 10:28:55.983 SR-IPC1:23 read 21
OK 00 1.3E-11 AMPS\r\r\n
2019/02/07 10:28:55.984 SR-IPC1:23 write 9
cmd 0B 2\r
2019/02/07 10:28:56.003 SR-IPC1:23 read 1
>
2019/02/07 10:28:56.103 SR-IPC1:23 read 21
OK 00 1.3E-11 MBAR\r\r\n
2019/02/07 10:28:56.104 SR-IPC1:23 write 9
cmd 0C 2\r
2019/02/07 10:28:56.123 SR-IPC1:23 read 1
>
2019/02/07 10:28:56.223 SR-IPC1:23 read 13
OK 00 6664\r\r\n
2019/02/07 10:28:56.224 SR-IPC1:23 write 9
cmd 0D 1\r
2019/02/07 10:28:56.243 SR-IPC1:23 read 1
>
2019/02/07 10:28:56.343 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:56.344 SR-IPC1:23 write 9
cmd 0D 2\r
2019/02/07 10:28:56.363 SR-IPC1:23 read 1
>
2019/02/07 10:28:56.463 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:56.464 SR-IPC1:23 write 9
cmd 0D 3\r
2019/02/07 10:28:56.483 SR-IPC1:23 read 1
>
2019/02/07 10:28:56.583 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:56.584 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:28:56.603 SR-IPC1:23 read 1
>
2019/02/07 10:28:56.709 SR-IPC1:23 read 21
OK 00 3.5E-06 AMPS\r\r\n
2019/02/07 10:28:56.710 SR-IPC1:23 write 9
cmd 0C 1\r
2019/02/07 10:28:56.729 SR-IPC1:23 read 1
>
2019/02/07 10:28:56.829 SR-IPC1:23 read 13
OK 00 4993\r\r\n
2019/02/07 10:28:56.830 SR-IPC1:23 write 9
cmd 0A 3\r
2019/02/07 10:28:56.849 SR-IPC1:23 read 1
>
2019/02/07 10:28:56.954 SR-IPC1:23 read 21
OK 00 9.6E-07 AMPS\r\r\n
2019/02/07 10:28:56.956 SR-IPC1:23 write 9
cmd 0B 3\r
2019/02/07 10:28:56.974 SR-IPC1:23 read 1
>
2019/02/07 10:28:57.074 SR-IPC1:23 read 21
OK 00 4.5E-10 MBAR\r\r\n
2019/02/07 10:28:57.076 SR-IPC1:23 write 9
cmd 0C 3\r
2019/02/07 10:28:57.094 SR-IPC1:23 read 1
>
2019/02/07 10:28:57.194 SR-IPC1:23 read 13
OK 00 6987\r\r\n
2019/02/07 10:28:57.195 SR-IPC1:23 write 9
cmd 61 1\r
2019/02/07 10:28:57.219 SR-IPC1:23 read 1
>
2019/02/07 10:28:57.319 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:57.320 SR-IPC1:23 write 9
cmd 61 2\r
2019/02/07 10:28:57.339 SR-IPC1:23 read 1
>
2019/02/07 10:28:57.439 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:57.440 SR-IPC1:23 write 9
cmd 61 3\r
2019/02/07 10:28:57.459 SR-IPC1:23 read 1
>
2019/02/07 10:28:57.559 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:57.560 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:28:57.579 SR-IPC1:23 read 1
>
2019/02/07 10:28:57.680 SR-IPC1:23 read 21
OK 00 3.4E-06 AMPS\r\r\n
2019/02/07 10:28:57.681 SR-IPC1:23 write 9
cmd 0B 1\r
2019/02/07 10:28:57.700 SR-IPC1:23 read 1
>
2019/02/07 10:28:57.805 SR-IPC1:23 read 21
OK 00 2.2E-09 MBAR\r\r\n
2019/02/07 10:28:57.806 SR-IPC1:23 write 9
cmd 0C 1\r
2019/02/07 10:28:57.824 SR-IPC1:23 read 1
>
2019/02/07 10:28:57.924 SR-IPC1:23 read 13
OK 00 4992\r\r\n
2019/02/07 10:28:57.926 SR-IPC1:23 write 9
cmd 0A 2\r
2019/02/07 10:28:57.944 SR-IPC1:23 read 1
>
2019/02/07 10:28:58.044 SR-IPC1:23 read 21
OK 00 7.8E-06 AMPS\r\r\n
2019/02/07 10:28:58.046 SR-IPC1:23 write 9
cmd 0B 2\r
2019/02/07 10:28:58.065 SR-IPC1:23 read 1
>
2019/02/07 10:28:58.166 SR-IPC1:23 read 21
OK 00 1.3E-11 MBAR\r\r\n
2019/02/07 10:28:58.167 SR-IPC1:23 write 9
cmd 0C 2\r
2019/02/07 10:28:58.186 SR-IPC1:23 read 1
>
2019/02/07 10:28:58.286 SR-IPC1:23 read 13
OK 00 6769\r\r\n
2019/02/07 10:28:58.287 SR-IPC1:23 write 9
cmd 0D 1\r
2019/02/07 10:28:58.306 SR-IPC1:23 read 1
>
2019/02/07 10:28:58.412 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:58.413 SR-IPC1:23 write 9
cmd 0D 2\r
2019/02/07 10:28:58.432 SR-IPC1:23 read 1
>
2019/02/07 10:28:58.532 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:58.533 SR-IPC1:23 write 9
cmd 0D 3\r
2019/02/07 10:28:58.552 SR-IPC1:23 read 1
>
2019/02/07 10:28:58.656 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:28:58.657 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:28:58.676 SR-IPC1:23 read 1
>
2019/02/07 10:28:58.776 SR-IPC1:23 read 21
OK 00 3.3E-06 AMPS\r\r\n
2019/02/07 10:28:58.777 SR-IPC1:23 write 9
cmd 0B 1\r
2019/02/07 10:28:58.796 SR-IPC1:23 read 1
>
2019/02/07 10:28:58.899 SR-IPC1:23 read 21
OK 00 2.3E-09 MBAR\r\r\n
2019/02/07 10:28:58.900 SR-IPC1:23 write 9
cmd 0A 3\r
2019/02/07 10:28:58.919 SR-IPC1:23 read 1
>
2019/02/07 10:28:59.019 SR-IPC1:23 read 21
OK 00 9.7E-07 AMPS\r\r\n
2019/02/07 10:28:59.020 SR-IPC1:23 write 9
cmd 0B 3\r
2019/02/07 10:28:59.039 SR-IPC1:23 read 1
>
2019/02/07 10:28:59.142 SR-IPC1:23 read 21
OK 00 4.6E-10 MBAR\r\r\n
2019/02/07 10:28:59.143 SR-IPC1:23 write 9
cmd 0C 3\r
2019/02/07 10:28:59.162 SR-IPC1:23 read 1
>
2019/02/07 10:28:59.262 SR-IPC1:23 read 13
OK 00 6990\r\r\n
2019/02/07 10:28:59.263 SR-IPC1:23 write 9
cmd 61 1\r
2019/02/07 10:28:59.281 SR-IPC1:23 read 1
>
2019/02/07 10:28:59.382 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:59.383 SR-IPC1:23 write 9
cmd 61 2\r
2019/02/07 10:28:59.401 SR-IPC1:23 read 1
>
2019/02/07 10:28:59.502 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:59.503 SR-IPC1:23 write 9
cmd 61 3\r
2019/02/07 10:28:59.521 SR-IPC1:23 read 1
>
2019/02/07 10:28:59.622 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:28:59.623 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:28:59.646 SR-IPC1:23 read 1
>
e2019/02/07 10:28:59.746 SR-IPC1:23 read 21
OK 00 3.4E-06 AMPS\r\r\n
2019/02/07 10:28:59.747 SR-IPC1:23 write 9
cmd 0C 1\r
2019/02/07 10:28:59.766 SR-IPC1:23 read 1
>
2019/02/07 10:28:59.866 SR-IPC1:23 read 13
OK 00 4997\r\r\n
2019/02/07 10:28:59.867 SR-IPC1:23 write 9
cmd 0A 2\r
2019/02/07 10:28:59.886 SR-IPC1:23 read 1
>
x2019/02/07 10:28:59.989 SR-IPC1:23 read 21
OK 00 7.3E-07 AMPS\r\r\n
2019/02/07 10:28:59.990 SR-IPC1:23 write 9
cmd 0B 2\r
2019/02/07 10:29:00.009 SR-IPC1:23 read 1
>
i2019/02/07 10:29:00.109 SR-IPC1:23 read 21
OK 00 1.3E-11 MBAR\r\r\n
2019/02/07 10:29:00.110 SR-IPC1:23 write 9
cmd 0C 2\r
2019/02/07 10:29:00.129 SR-IPC1:23 read 1
>
t2019/02/07 10:29:00.236 SR-IPC1:23 read 13
OK 00 7149\r\r\n
2019/02/07 10:29:00.237 SR-IPC1:23 write 9
cmd 0D 1\r

=== Exit has been executed here ===

2019/02/07 10:29:00.256 SR-IPC1:23 read 1
>
2019/02/07 10:29:00.356 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:29:00.357 SR-IPC1:23 write 9
cmd 0D 2\r
2019/02/07 10:29:00.376 SR-IPC1:23 read 1
>
2019/02/07 10:29:00.476 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:29:00.477 SR-IPC1:23 write 9
cmd 0D 3\r
2019/02/07 10:29:00.496 SR-IPC1:23 read 1
>
2019/02/07 10:29:00.596 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:29:00.597 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:29:00.616 SR-IPC1:23 read 1
>
2019/02/07 10:29:00.717 SR-IPC1:23 read 21
OK 00 3.1E-06 AMPS\r\r\n
2019/02/07 10:29:00.718 SR-IPC1:23 write 9
cmd 0B 1\r
2019/02/07 10:29:00.737 SR-IPC1:23 read 1
>
2019/02/07 10:29:00.837 SR-IPC1:23 read 21
OK 00 2.3E-09 MBAR\r\r\n
2019/02/07 10:29:00.838 SR-IPC1:23 write 9
cmd 0A 3\r
2019/02/07 10:29:00.857 SR-IPC1:23 read 1
>
2019/02/07 10:29:00.957 SR-IPC1:23 read 21
OK 00 9.6E-07 AMPS\r\r\n
2019/02/07 10:29:00.958 SR-IPC1:23 write 9
cmd 0B 3\r
2019/02/07 10:29:00.980 SR-IPC1:23 read 1
>
2019/02/07 10:29:01.080 SR-IPC1:23 read 21
OK 00 4.5E-10 MBAR\r\r\n
2019/02/07 10:29:01.081 SR-IPC1:23 write 9
cmd 0C 3\r
2019/02/07 10:29:01.100 SR-IPC1:23 read 1
>
2019/02/07 10:29:01.200 SR-IPC1:23 read 13
OK 00 6992\r\r\n
2019/02/07 10:29:01.201 SR-IPC1:23 write 9
cmd 61 1\r
2019/02/07 10:29:01.220 SR-IPC1:23 read 1
>
2019/02/07 10:29:01.323 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:29:01.324 SR-IPC1:23 write 9
cmd 61 2\r
2019/02/07 10:29:01.343 SR-IPC1:23 read 1
>
2019/02/07 10:29:01.443 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:29:01.444 SR-IPC1:23 write 9
cmd 61 3\r
2019/02/07 10:29:01.463 SR-IPC1:23 read 1
>
2019/02/07 10:29:01.563 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:29:01.564 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:29:01.588 SR-IPC1:23 read 1
>
2019/02/07 10:29:01.687 SR-IPC1:23 read 21
OK 00 3.5E-06 AMPS\r\r\n
2019/02/07 10:29:01.688 SR-IPC1:23 write 9
cmd 0C 1\r
2019/02/07 10:29:01.707 SR-IPC1:23 read 1
>
2019/02/07 10:29:01.807 SR-IPC1:23 read 13
OK 00 4993\r\r\n
2019/02/07 10:29:01.808 SR-IPC1:23 write 9
cmd 0A 2\r
2019/02/07 10:29:01.827 SR-IPC1:23 read 1
>
2019/02/07 10:29:01.927 SR-IPC1:23 read 21
OK 00 1.3E-11 AMPS\r\r\n
2019/02/07 10:29:01.928 SR-IPC1:23 write 9
cmd 0B 2\r
2019/02/07 10:29:01.947 SR-IPC1:23 read 1
>
2019/02/07 10:29:02.047 SR-IPC1:23 read 21
OK 00 1.3E-11 MBAR\r\r\n
2019/02/07 10:29:02.048 SR-IPC1:23 write 9
cmd 0C 2\r
2019/02/07 10:29:02.067 SR-IPC1:23 read 1
>
2019/02/07 10:29:02.167 SR-IPC1:23 read 13
OK 00 6701\r\r\n
2019/02/07 10:29:02.168 SR-IPC1:23 write 9
cmd 0D 1\r
2019/02/07 10:29:02.187 SR-IPC1:23 read 1
>
2019/02/07 10:29:02.287 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:29:02.288 SR-IPC1:23 write 9
cmd 0D 2\r
2019/02/07 10:29:02.307 SR-IPC1:23 read 1
>
2019/02/07 10:29:02.407 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:29:02.408 SR-IPC1:23 write 9
cmd 0D 3\r
2019/02/07 10:29:02.427 SR-IPC1:23 read 1
>
2019/02/07 10:29:02.527 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:29:02.528 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:29:02.547 SR-IPC1:23 read 1
>
2019/02/07 10:29:02.647 SR-IPC1:23 read 21
OK 00 3.5E-06 AMPS\r\r\n
2019/02/07 10:29:02.648 SR-IPC1:23 write 9
cmd 0B 1\r
2019/02/07 10:29:02.672 SR-IPC1:23 read 1
>
2019/02/07 10:29:02.772 SR-IPC1:23 read 21
OK 00 2.3E-09 MBAR\r\r\n
2019/02/07 10:29:02.773 SR-IPC1:23 write 9
cmd 0C 1\r
2019/02/07 10:29:02.791 SR-IPC1:23 read 1
>
2019/02/07 10:29:02.892 SR-IPC1:23 read 13
OK 00 5000\r\r\n
2019/02/07 10:29:02.893 SR-IPC1:23 write 9
cmd 0A 3\r
2019/02/07 10:29:02.911 SR-IPC1:23 read 1
>
2019/02/07 10:29:03.016 SR-IPC1:23 read 21
OK 00 1.3E-11 AMPS\r\r\n
2019/02/07 10:29:03.017 SR-IPC1:23 write 9
cmd 0B 3\r
2019/02/07 10:29:03.036 SR-IPC1:23 read 1
>
2019/02/07 10:29:03.136 SR-IPC1:23 read 21
OK 00 1.3E-11 MBAR\r\r\n
2019/02/07 10:29:03.137 SR-IPC1:23 write 9
cmd 0C 3\r
2019/02/07 10:29:03.156 SR-IPC1:23 read 1
>
2019/02/07 10:29:03.256 SR-IPC1:23 read 13
OK 00 4610\r\r\n
2019/02/07 10:29:03.257 SR-IPC1:23 write 9
cmd 61 1\r
2019/02/07 10:29:03.276 SR-IPC1:23 read 1
>
2019/02/07 10:29:03.376 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:29:03.377 SR-IPC1:23 write 9
cmd 61 2\r
2019/02/07 10:29:03.396 SR-IPC1:23 read 1
>
2019/02/07 10:29:03.496 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:29:03.497 SR-IPC1:23 write 9
cmd 61 3\r
2019/02/07 10:29:03.516 SR-IPC1:23 read 1
>
2019/02/07 10:29:03.616 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:29:03.617 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:29:03.636 SR-IPC1:23 read 1
>
2019/02/07 10:29:03.736 SR-IPC1:23 read 21
OK 00 3.2E-06 AMPS\r\r\n
2019/02/07 10:29:03.737 SR-IPC1:23 write 9
cmd 0B 1\r
2019/02/07 10:29:03.756 SR-IPC1:23 read 1
>
2019/02/07 10:29:03.860 SR-IPC1:23 read 21
OK 00 2.1E-09 MBAR\r\r\n
2019/02/07 10:29:03.861 SR-IPC1:23 write 9
cmd 0A 2\r
2019/02/07 10:29:03.879 SR-IPC1:23 read 1
>
2019/02/07 10:29:03.979 SR-IPC1:23 read 21
OK 00 1.3E-11 AMPS\r\r\n
2019/02/07 10:29:03.980 SR-IPC1:23 write 9
cmd 0B 2\r
2019/02/07 10:29:03.999 SR-IPC1:23 read 1
>
2019/02/07 10:29:04.100 SR-IPC1:23 read 21
OK 00 1.3E-11 MBAR\r\r\n
2019/02/07 10:29:04.101 SR-IPC1:23 write 9
cmd 0C 2\r
2019/02/07 10:29:04.120 SR-IPC1:23 read 1
>
2019/02/07 10:29:04.220 SR-IPC1:23 read 13
OK 00 6636\r\r\n
2019/02/07 10:29:04.221 SR-IPC1:23 write 9
cmd 0D 1\r
2019/02/07 10:29:04.240 SR-IPC1:23 read 1
>
2019/02/07 10:29:04.340 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:29:04.341 SR-IPC1:23 write 9
cmd 0D 2\r
2019/02/07 10:29:04.360 SR-IPC1:23 read 1
>
2019/02/07 10:29:04.464 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:29:04.465 SR-IPC1:23 write 9
cmd 0D 3\r
2019/02/07 10:29:04.484 SR-IPC1:23 read 1
>
2019/02/07 10:29:04.584 SR-IPC1:23 read 19
OK 00 RUNNING 00\r\r\n
2019/02/07 10:29:04.585 SR-IPC1:23 write 9
cmd 0A 1\r
2019/02/07 10:29:04.604 SR-IPC1:23 read 1
>
2019/02/07 10:29:04.705 SR-IPC1:23 read 21
OK 00 3.4E-06 AMPS\r\r\n
2019/02/07 10:29:04.706 SR-IPC1:23 write 9
cmd 0C 1\r
2019/02/07 10:29:04.724 SR-IPC1:23 read 1
>
2019/02/07 10:29:04.824 SR-IPC1:23 read 13
OK 00 4994\r\r\n
2019/02/07 10:29:04.825 SR-IPC1:23 write 9
cmd 0A 3\r
2019/02/07 10:29:04.844 SR-IPC1:23 read 1
>
2019/02/07 10:29:04.946 SR-IPC1:23 read 21
OK 00 2.6E-05 AMPS\r\r\n
2019/02/07 10:29:04.947 SR-IPC1:23 write 9
cmd 0B 3\r
2019/02/07 10:29:04.966 SR-IPC1:23 read 1
>
2019/02/07 10:29:05.066 SR-IPC1:23 read 21
OK 00 2.9E-08 MBAR\r\r\n
2019/02/07 10:29:05.067 SR-IPC1:23 write 9
cmd 0C 3\r
2019/02/07 10:29:05.086 SR-IPC1:23 read 1
>
2019/02/07 10:29:05.186 SR-IPC1:23 read 13
OK 00 3343\r\r\n
2019/02/07 10:29:05.187 SR-IPC1:23 write 9
cmd 61 1\r
2019/02/07 10:29:05.206 SR-IPC1:23 read 1
>
2019/02/07 10:29:05.306 SR-IPC1:23 read 12
OK 00 YES\r\r\n
2019/02/07 10:29:05.307 SR-IPC1:23 write 9
cmd 61 2\r
2019/02/07 10:29:05.326 SR-IPC1:23 read 1
>

Replies:
Re: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk
Re: Weird stream device behavior when using the IOC shell's exit function Dirk Zimoch via Tech-talk
References:
Weird stream device behavior when using the IOC shell's exit function Abdalla Ahmad via Tech-talk
Re: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk
Re: Weird stream device behavior when using the IOC shell's exit function Abdalla Ahmad via Tech-talk
RE: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk
RE: Weird stream device behavior when using the IOC shell's exit function Abdalla Ahmad via Tech-talk
Re: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk
RE: Weird stream device behavior when using the IOC shell's exit function Abdalla Ahmad via Tech-talk
Re: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk
RE: Weird stream device behavior when using the IOC shell's exit function Abdalla Ahmad via Tech-talk
Re: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk
Re: Weird stream device behavior when using the IOC shell's exit function Abdalla Ahmad via Tech-talk
RE: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk
RE: Weird stream device behavior when using the IOC shell's exit function Abdalla Ahmad via Tech-talk
RE: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk
RE: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk

Navigate by Date:
Prev: Re: Weird stream device behavior when using the IOC shell's exit function Dirk Zimoch via Tech-talk
Next: Point Grey GigE Blackfly conflict Nilson Pereira via Tech-talk
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  <20192020 
Navigate by Thread:
Prev: RE: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk
Next: Re: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk
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  <20192020 
ANJ, 07 Feb 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·