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 <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: asynMotor device support and the motor specific driver (asynMotorContorller) |
| From: | Allan Serra Braga Bugyi via Tech-talk <[email protected]> |
| To: | Mark Rivers <[email protected]> |
| Cc: | "[email protected]" <[email protected]> |
| Date: | Mon, 8 Apr 2019 18:31:31 +0000 |
|
asynReport
tcpip_e712 multiDevice:No canBlock:Yes autoConnect:Yes PIasyn3 multiDevice:Yes canBlock:Yes autoConnect:Yes Simulation motor driver PIasyn3, numAxes=3 axis 0 axis 1 axis 2 Port: PIasyn3
Please find it attached. Thanks, Allan De: Mark Rivers <[email protected]>
Enviado: segunda-feira, 8 de abril de 2019 15:07:15 Para: Allan Serra Braga Bugyi Cc: [email protected] Assunto: Re: asynMotor device support and the motor specific driver (asynMotorContorller) Turn the asynTrace on the IP port back to 9.
After the IOC boots type this command: asynReport I would have expected port PIasyn3 to exist. Mark Sent from my iPhone On Apr 8, 2019, at 1:00 PM, Allan Serra Braga Bugyi <[email protected]<mailto:[email protected]>> wrote: It says: asynManager:report port “PIasyn3” not found Please find attached the log. Allan <http://lnls.cnpem.br> ________________________________ De: Mark Rivers <[email protected]<mailto:[email protected]>> Enviado: segunda-feira, 8 de abril de 2019 14:10:13 Para: Allan Serra Braga Bugyi Cc: [email protected]<mailto:[email protected]> Assunto: RE: asynMotor device support and the motor specific driver (asynMotorContorller) Hi Allan, What does the following command show? asynReport 10 “PIasyn3” You can also add these commands to your asynMotor.E-712.cmd script after PI_GCS2_CreateController("PIasyn3", "tcpip_e712",3, 0,0, 10, 250) asynSetTraceIOMask("PIasyn3", -1, 0x2) asynSetTraceMask("PIasyn3", -1, 0xff) This will show lots more debugging info. Mark From: Allan Serra Braga Bugyi <[email protected]<mailto:[email protected]>> Sent: Monday, April 8, 2019 9:59 AM To: Mark Rivers <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: asynMotor device support and the motor specific driver (asynMotorContorller) Hi Mark, Yes, I already instantiated the driver and it's the one you thought. Below I'm showing you the files used to run the IOC. However, the stage is not responding when I do a caput to its VAL field of the motor record, in order to move. I believe that the device support is not able to load the PI commands, the reason for the stage not responding. Besides, I'm not sure if the PI's sources are a complete validated solution, since I didn't find the command set (used by start/build/end transaction) defined anywhere. What I did find were several methods inside the PIGCSController class which use the send/receive message function from asynOctetSyncIO interface in order to communicate with the stage. So I'm confused about using this driver: - Calling these methods separately using the asynPortDriver methodology of pasynUnser->reason and OUT and INP fields; - Or letting the device support to do all the job, in case of having the GCS command list loaded. Since the intention is to obviously use the motor record, I'm obliged to go with the second approach. Also, please find a log file attached. -- EPICS IOC's files * st.cmd #!/usr/local/epics/synApps_6_0/support/motor-R6-10-1/motorExApp/WithAsyn/O.linux-x86_64/WithAsyn < envPaths ## Register all support components dbLoadDatabase("${TOP}/dbd/WithAsyn.dbd") WithAsyn_registerRecordDeviceDriver(pdbbase) drvAsynIPPortConfigure("tcpip_e712","10.0.9.74:50000",0,0,0) asynOctetConnect("tcpip_e712", "tcpip_e712") asynOctetSetInputEos("tcpip_e712",0,"\n") < asynMotor.E-712.cmd iocInit * asynMotor.E-712.cmd dbLoadTemplate("asynMotor.substitutions.E-712") PI_GCS2_CreateController("PIasyn3", "tcpip_e712",3, 0,0, 10, 250) dbLoadRecords("${TOP}/db/PI_Support.db","P=PIE712:,R=m1:,PORT=PIasyn3,ADDR=0,TIMEOUT=1") dbLoadRecords("${TOP}/db/PI_Support.db","P=PIE712:,R=m2:,PORT=PIasyn3,ADDR=1,TIMEOUT=1") dbLoadRecords("${TOP}/db/PI_Support.db","P=PIE712:,R=m3:,PORT=PIasyn3,ADDR=2,TIMEOUT=1") dbLoadRecords("${TOP}/db/PI_SupportCtrl.db","P=PIE712:,R=m1:,PORT=PIasyn3,ADDR=0,TIMEOUT=1") * asynMotor.substitutions.E-712 file "$(MOTOR)/motorApp/Db/basic_asyn_motor.db" { pattern {P, N, M, DTYP, PORT, ADDR, DESC, EGU, DIR, VELO, VBAS, ACCL, BDST, BVEL, BACC, MRES, PREC, DHLM, DLLM, INIT, RTRY} {PIE712:, 1, "m$(N)", "asynMotor", "PIasyn3", 0, "PI-STAGE-725-X", um, Pos, 1, .1, .2, 0, 1, .2, 0.000001, 7, 0, 300, "", ""} {PIE712:, 2, "m$(N)", "asynMotor", "PIasyn3", 1, "PI-STAGE-725-Y", um, Pos, 1, .1, .2, 0, 1, .2, 0.000001, 7, 0, 300, "", ""} {PIE712:, 3, "m$(N)", "asynMotor", "PIasyn3", 2, "PI-STAGE-725-Z", um, Pos, 1, .1, .2, 0, 1, .2, 0.000001, 7, 0, 300, "", ""} } Thank you! Best regards, Allan S. B. Bugyi Technology Development Analyst [email protected]<mailto:[email protected]> (+55 19) 3512-3520 SOL/Beamline Software Group Brazilian Synchrotron Light Laboratory (LNLS) Center of Research in Energy and Materials (CNPEM) http://lnls.cnpem.br ________________________________ De: Mark Rivers <[email protected]<mailto:[email protected]>> Enviado: segunda-feira, 8 de abril de 2019 11:30:23 Para: Allan Serra Braga Bugyi Cc: [email protected]<mailto:[email protected]> Assunto: Re: asynMotor device support and the motor specific driver (asynMotorContorller) Hi Allan, I am not sure I fully understand your question. Have you tried to instantiate a controller and load a template file, and received errors, or are you not that far along? Unfortunately motor does not seem to contain an example for your controller, but it does contain examples for lots of other controllers that use devMotorAsyn.c and asynMotorController.cpp. Look in motor/iocBoot/iocWithAsyn/st.cmd.mcb4b for a simple example. It creates a controller object with MCB4BCreateController("MCB4B1", "serial1", 4, 100, 5000) In your case I believe this would be: PI_GCS2_CreateController(const char *portName, const char* asynPort, int numAxes, int priority, int stackSize, int movingPollingRate, int idlePollingRate) and then loads a template file with several motor records: dbLoadTemplate "motor.substitutions.mcb4b" You need to create a template file for your motors. The motor module is being split into separate repositories for each controller type. Each repository will contain an example IOC to help with these types of questions. These example IOCs will require help from the community, since at the APS we don't have all of the types of controllers that are supported, so we can't test examples. Mark ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Allan Serra Braga Bugyi via Tech-talk <[email protected]<mailto:[email protected]>> Sent: Monday, April 8, 2019 8:39 AM To: [email protected]<mailto:[email protected]> Subject: asynMotor device support and the motor specific driver (asynMotorContorller) Hello all, I need a clarification about the motor module. The asynMotor device support (defined in 'motorApp/MotorSrc/devMotorAsyn.c') tries to find an asynDrvUser interface in init_record function, so that it can find the driver commands with findDrvInfo function. I'm using the asynMotorController driver that implements the PI's command set GCS. How can I connect this driver with the motor record through asynMotor device support? Additional information: A class diagram of the PI sources (please ignore the error message; using motor 6-11 now) [cid:b8eb7e61-f6f9-41d6-8500-6813e6d2e809] Thank you! Allan S. B. Bugyi Technology Development Analyst [email protected]<mailto:[email protected]> (+55 19) 3512-3520 SOL/Beamline Software Group Brazilian Synchrotron Light Laboratory (LNLS) Center of Research in Energy and Materials (CNPEM) http://lnls.cnpem.br <http://lnls.cnpem.br> Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente. Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately. <pi563_iocLog_motor6-11_08-04.log> |
#!/usr/local/epics/motor-2019-04-02/motorExApp/WithAsyn/O.linux-x86_64/WithAsyn
epicsEnvSet("EPICS_IOC_LOG_INET", "127.0.0.1")
< envPaths
epicsEnvSet("ARCH","linux-x86_64")
epicsEnvSet("IOC","iocWithAsyn")
epicsEnvSet("TOP","/usr/local/epics/motor-2019-04-02")
epicsEnvSet("SUPPORT","/usr/local/epics/synApps_6_0/support")
epicsEnvSet("ASYN","/usr/local/epics/synApps/support_6_0/asyn-R4-33")
epicsEnvSet("SNCSEQ","/usr/local/epics/synApps/support_6_0/seq-2-2-5")
epicsEnvSet("BUSY","/usr/local/epics/synApps_6_0/support/busy-R1-7")
epicsEnvSet("EPICS_BASE","/usr/local/epics/base_3_15_6")
epicsEnvSet("IPAC","/usr/local/epics/synApps_6_0/support/ipac-2-15")
epicsEnvSet("MOTOR","/usr/local/epics/motor-2019-04-02")
## Register all support components
dbLoadDatabase("/usr/local/epics/motor-2019-04-02/dbd/WithAsyn.dbd")
WithAsyn_registerRecordDeviceDriver(pdbbase)
drvAsynIPPortConfigure("tcpip_e712","10.0.9.74:50000",0,0,0)
asynOctetConnect("tcpip_e712", "tcpip_e712")
asynOctetSetInputEos("tcpip_e712",0,"\n")
asynSetTraceIOMask("tcpip_e712", -1, 0x2)
asynSetTraceMask("tcpip_e712", -1, 0x9)
< asynMotor.E-712.cmd
dbLoadTemplate("asynMotor.substitutions.E-712")
PI_GCS2_CreateController("PIasyn3", "tcpip_e712",3, 0,0, 10, 250)
2019/04/08 15:25:41.302 PIInterface::sendAndReceive() sending "*IDN?"
2019/04/08 15:25:41.302 10.0.9.74:50000 write 5
*IDN?
2019/04/08 15:25:41.302 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.303 10.0.9.74:50000 read 47
(c)2015 Physik Instrumente (PI) GmbH & Co. KG,
2019/04/08 15:25:41.304 10.0.9.74:50000 read 7
E-727,
2019/04/08 15:25:41.304 10.0.9.74:50000 read 12
0118027690,
2019/04/08 15:25:41.304 10.0.9.74:50000 read 12
14.04.01.02\n
2019/04/08 15:25:41.304 PIInterface::sendAndReceive() received "(c)2015 Physik Instrumente (PI) GmbH & Co. KG, E-727, 0118027690, 14.04.01.02"
2019/04/08 15:25:41.304 read from tcpip_e712: (c)2015 Physik Instrumente (PI) GmbH & Co. KG, E-727, 0118027690, 14.04.01.02
2019/04/08 15:25:41.304 PIInterface::sendAndReceive() sending "VEL?"
2019/04/08 15:25:41.304 10.0.9.74:50000 write 4
VEL?
2019/04/08 15:25:41.304 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.305 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.305 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.306 10.0.9.74:50000 read 17
7.500000000e+03 \n
2019/04/08 15:25:41.306 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.306 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.306 10.0.9.74:50000 read 17
7.500000000e+03 \n
2019/04/08 15:25:41.306 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.307 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.307 10.0.9.74:50000 read 16
2.000000000e+04\n
2019/04/08 15:25:41.307 PIInterface::sendAndReceive() received "1=7.500000000e+03
2=7.500000000e+03
3=2.000000000e+04"
2019/04/08 15:25:41.307 PIInterface::sendAndReceive() sending "SAI?"
2019/04/08 15:25:41.307 10.0.9.74:50000 write 4
SAI?
2019/04/08 15:25:41.307 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.308 10.0.9.74:50000 read 3
1 \n
2019/04/08 15:25:41.308 10.0.9.74:50000 read 3
2 \n
2019/04/08 15:25:41.308 10.0.9.74:50000 read 2
3\n
2019/04/08 15:25:41.308 PIInterface::sendAndReceive() received "1
2
3"
PIasynAxis::PIasynAxis() 0: 1
2019/04/08 15:25:41.308 10.0.9.74:50000 write 7
SVO 1 1
2019/04/08 15:25:41.308 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.309 10.0.9.74:50000 write 4
ERR?
2019/04/08 15:25:41.309 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.310 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.310 10.0.9.74:50000 write 6
VEL? 1
2019/04/08 15:25:41.310 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.310 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.311 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.311 10.0.9.74:50000 read 16
7.500000000e+03\n
2019/04/08 15:25:41.311 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.311 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.312 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.312 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.312 10.0.9.74:50000 read 16
1.756140137e+01\n
2019/04/08 15:25:41.312 10.0.9.74:50000 write 6
TMN? 1
2019/04/08 15:25:41.313 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.313 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.314 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.314 10.0.9.74:50000 read 16
0.000000000e+00\n
2019/04/08 15:25:41.314 10.0.9.74:50000 write 6
TMX? 1
2019/04/08 15:25:41.314 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.315 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.315 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.315 10.0.9.74:50000 read 16
3.000000000e+02\n
PIasynAxis::PIasynAxis() 1: 2
2019/04/08 15:25:41.315 10.0.9.74:50000 write 7
SVO 2 1
2019/04/08 15:25:41.315 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.315 10.0.9.74:50000 write 4
ERR?
2019/04/08 15:25:41.315 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.316 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.317 10.0.9.74:50000 write 6
VEL? 2
2019/04/08 15:25:41.317 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.318 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.318 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.318 10.0.9.74:50000 read 16
7.500000000e+03\n
2019/04/08 15:25:41.318 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.318 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.319 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.319 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.319 10.0.9.74:50000 read 16
1.566122437e+01\n
2019/04/08 15:25:41.319 10.0.9.74:50000 write 6
TMN? 2
2019/04/08 15:25:41.319 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.320 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.321 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.321 10.0.9.74:50000 read 16
0.000000000e+00\n
2019/04/08 15:25:41.321 10.0.9.74:50000 write 6
TMX? 2
2019/04/08 15:25:41.321 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.322 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.322 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.322 10.0.9.74:50000 read 16
3.000000000e+02\n
PIasynAxis::PIasynAxis() 2: 3
2019/04/08 15:25:41.322 10.0.9.74:50000 write 7
SVO 3 1
2019/04/08 15:25:41.322 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.323 10.0.9.74:50000 write 4
ERR?
2019/04/08 15:25:41.323 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.323 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.323 10.0.9.74:50000 write 6
VEL? 3
2019/04/08 15:25:41.323 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.324 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.324 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.325 10.0.9.74:50000 read 16
2.000000000e+04\n
2019/04/08 15:25:41.325 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.325 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.326 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.326 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.326 10.0.9.74:50000 read 16
1.911419678e+01\n
2019/04/08 15:25:41.326 10.0.9.74:50000 write 6
TMN? 3
2019/04/08 15:25:41.326 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.327 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.327 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.327 10.0.9.74:50000 read 16
0.000000000e+00\n
2019/04/08 15:25:41.328 10.0.9.74:50000 write 6
TMX? 3
2019/04/08 15:25:41.328 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.328 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.329 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.329 10.0.9.74:50000 read 16
3.000000000e+02\n
dbLoadRecords("/usr/local/epics/motor-2019-04-02/db/PI_Support.db","P=PIE712:,R=m1:,PORT=PIasyn3,ADDR=0,TIMEOUT=1")
dbLoadRecords("/usr/local/epics/motor-2019-04-02/db/PI_Support.db","P=PIE712:,R=m2:,PORT=PIasyn3,ADDR=1,TIMEOUT=1")
dbLoadRecords("/usr/local/epics/motor-2019-04-02/db/PI_Support.db","P=PIE712:,R=m3:,PORT=PIasyn3,ADDR=2,TIMEOUT=1")
2019/04/08 15:25:41.329 10.0.9.74:50000 write 1
\005
dbLoadRecords("/usr/local/epics/motor-2019-04-02/db/PI_SupportCtrl.db","P=PIE712:,R=m1:,PORT=PIasyn3,ADDR=0,TIMEOUT=1")
#asynReport 10 â??PIasyn3â??
#setIocLogDisable 0
#iocLogInit
iocInit
Starting iocInit
############################################################################
## EPICS R3.15.6
## EPICS Base built Mar 7 2019
############################################################################
2019/04/08 15:25:41.330 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.330 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.330 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.331 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.331 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.331 10.0.9.74:50000 read 16
1.756149292e+01\n
2019/04/08 15:25:41.331 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.331 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.332 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.332 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.332 10.0.9.74:50000 read 16
1.756158447e+01\n
2019/04/08 15:25:41.333 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.333 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.333 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.333 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.334 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.334 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.335 10.0.9.74:50000 read 16
1.566059875e+01\n
2019/04/08 15:25:41.335 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.335 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.336 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.336 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.336 10.0.9.74:50000 read 16
1.566204834e+01\n
2019/04/08 15:25:41.336 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.337 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.337 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.337 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.338 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.338 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.338 10.0.9.74:50000 read 16
1.911480713e+01\n
2019/04/08 15:25:41.338 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.338 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.339 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.339 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.340 10.0.9.74:50000 read 16
1.911462402e+01\n
2019/04/08 15:25:41.350 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.350 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.351 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.351 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.351 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.352 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.352 10.0.9.74:50000 read 16
1.756166077e+01\n
2019/04/08 15:25:41.352 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.352 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.353 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.353 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.353 10.0.9.74:50000 read 16
1.756060791e+01\n
2019/04/08 15:25:41.353 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.354 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.354 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.354 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.355 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.355 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.355 10.0.9.74:50000 read 16
1.566235352e+01\n
2019/04/08 15:25:41.355 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.355 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.356 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.356 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.357 10.0.9.74:50000 read 16
1.566270447e+01\n
2019/04/08 15:25:41.357 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.357 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.357 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.357 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.358 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.359 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.359 10.0.9.74:50000 read 16
1.911204529e+01\n
2019/04/08 15:25:41.359 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.359 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.360 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.360 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.360 10.0.9.74:50000 read 16
1.911035156e+01\n
2019/04/08 15:25:41.370 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.371 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.371 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.371 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.372 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.372 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.373 10.0.9.74:50000 read 16
1.756079102e+01\n
2019/04/08 15:25:41.373 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.373 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.374 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.374 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.374 10.0.9.74:50000 read 16
1.756031799e+01\n
2019/04/08 15:25:41.374 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.375 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.375 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.375 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.376 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.376 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.376 10.0.9.74:50000 read 16
1.566058350e+01\n
2019/04/08 15:25:41.376 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.376 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.377 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.377 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.377 10.0.9.74:50000 read 16
1.566098022e+01\n
2019/04/08 15:25:41.378 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.378 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.378 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.378 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.379 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.379 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.380 10.0.9.74:50000 read 16
1.911195374e+01\n
2019/04/08 15:25:41.380 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.380 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.381 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.381 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.381 10.0.9.74:50000 read 16
1.911291504e+01\n
2019/04/08 15:25:41.391 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.392 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.392 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.392 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.393 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.393 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.393 10.0.9.74:50000 read 16
1.756126404e+01\n
2019/04/08 15:25:41.393 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.393 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.394 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.394 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.395 10.0.9.74:50000 read 16
1.756182861e+01\n
2019/04/08 15:25:41.395 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.395 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.395 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.395 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.396 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.396 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.397 10.0.9.74:50000 read 16
1.566233826e+01\n
2019/04/08 15:25:41.397 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.397 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.398 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.398 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.398 10.0.9.74:50000 read 16
1.566125488e+01\n
2019/04/08 15:25:41.398 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.399 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.399 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.399 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.400 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.400 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.400 10.0.9.74:50000 read 16
1.911251831e+01\n
2019/04/08 15:25:41.400 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.400 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.401 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.401 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.402 10.0.9.74:50000 read 16
1.911419678e+01\n
2019/04/08 15:25:41.412 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.412 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.412 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.413 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.413 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.414 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.414 10.0.9.74:50000 read 16
1.756045532e+01\n
2019/04/08 15:25:41.414 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.414 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.415 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.415 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.415 10.0.9.74:50000 read 16
1.756159973e+01\n
2019/04/08 15:25:41.415 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.416 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.416 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.416 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.417 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.417 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.417 10.0.9.74:50000 read 16
1.566339111e+01\n
2019/04/08 15:25:41.417 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.417 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.418 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.419 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.419 10.0.9.74:50000 read 16
1.566084290e+01\n
2019/04/08 15:25:41.419 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.419 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.419 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.420 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.420 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.421 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.421 10.0.9.74:50000 read 16
1.911186218e+01\n
2019/04/08 15:25:41.421 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.421 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.422 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.422 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.422 10.0.9.74:50000 read 16
1.911346436e+01\n
2019/04/08 15:25:41.432 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.433 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.433 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.433 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.434 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.434 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.435 10.0.9.74:50000 read 16
1.756024170e+01\n
2019/04/08 15:25:41.435 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.435 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.436 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.436 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.436 10.0.9.74:50000 read 16
1.756144714e+01\n
2019/04/08 15:25:41.436 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.437 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.437 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.437 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.438 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.438 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.438 10.0.9.74:50000 read 16
1.566369629e+01\n
2019/04/08 15:25:41.438 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.438 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.439 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.439 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.439 10.0.9.74:50000 read 16
1.566320801e+01\n
2019/04/08 15:25:41.440 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.440 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.440 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.440 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.441 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.441 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.442 10.0.9.74:50000 read 16
1.911250305e+01\n
2019/04/08 15:25:41.442 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.442 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.443 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.443 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.443 10.0.9.74:50000 read 16
1.911509705e+01\n
2019/04/08 15:25:41.453 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.454 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.454 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.454 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.455 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.455 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.455 10.0.9.74:50000 read 16
1.756118774e+01\n
2019/04/08 15:25:41.455 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.456 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.456 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.457 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.457 10.0.9.74:50000 read 16
1.756039429e+01\n
2019/04/08 15:25:41.457 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.458 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.458 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.458 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.458 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.459 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.459 10.0.9.74:50000 read 16
1.566386414e+01\n
2019/04/08 15:25:41.459 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.459 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.460 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.460 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.460 10.0.9.74:50000 read 16
1.566355896e+01\n
2019/04/08 15:25:41.460 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.461 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.461 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.461 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.462 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.462 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.462 10.0.9.74:50000 read 16
1.911529541e+01\n
2019/04/08 15:25:41.462 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.462 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.463 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.464 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.464 10.0.9.74:50000 read 16
1.911177063e+01\n
2019/04/08 15:25:41.474 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.475 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.475 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.475 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.476 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.476 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.476 10.0.9.74:50000 read 16
1.756425476e+01\n
2019/04/08 15:25:41.476 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.476 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.477 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.477 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.477 10.0.9.74:50000 read 16
1.756237793e+01\n
2019/04/08 15:25:41.478 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.478 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.478 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.478 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.479 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.479 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.480 10.0.9.74:50000 read 16
1.566349792e+01\n
2019/04/08 15:25:41.480 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.480 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.481 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.481 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.481 10.0.9.74:50000 read 16
1.566496277e+01\n
2019/04/08 15:25:41.481 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.482 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.482 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.482 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.483 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.483 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.484 10.0.9.74:50000 read 16
1.911131287e+01\n
2019/04/08 15:25:41.484 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.484 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.484 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.485 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.485 10.0.9.74:50000 read 16
1.911114502e+01\n
2019/04/08 15:25:41.495 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.496 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.496 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.496 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.497 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.497 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.497 10.0.9.74:50000 read 16
1.756314087e+01\n
2019/04/08 15:25:41.497 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.497 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.498 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.498 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.499 10.0.9.74:50000 read 16
1.756187439e+01\n
2019/04/08 15:25:41.499 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.499 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.499 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.500 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.500 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.501 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.501 10.0.9.74:50000 read 16
1.566375732e+01\n
2019/04/08 15:25:41.501 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.501 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.502 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.502 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.502 10.0.9.74:50000 read 16
1.566313171e+01\n
2019/04/08 15:25:41.502 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.503 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.503 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.503 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.504 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.504 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.504 10.0.9.74:50000 read 16
1.911196899e+01\n
2019/04/08 15:25:41.504 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.504 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.505 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.506 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.506 10.0.9.74:50000 read 16
1.911404419e+01\n
2019/04/08 15:25:41.516 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.517 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.517 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.517 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.518 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.518 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.518 10.0.9.74:50000 read 16
1.756358337e+01\n
2019/04/08 15:25:41.518 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.518 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.519 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.519 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.520 10.0.9.74:50000 read 16
1.756146240e+01\n
2019/04/08 15:25:41.520 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.520 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.520 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.520 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.521 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.521 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.522 10.0.9.74:50000 read 16
1.566131592e+01\n
2019/04/08 15:25:41.522 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.522 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.523 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.523 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.523 10.0.9.74:50000 read 16
1.566317749e+01\n
2019/04/08 15:25:41.523 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.524 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.524 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.524 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.525 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.525 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.525 10.0.9.74:50000 read 16
1.911441040e+01\n
2019/04/08 15:25:41.525 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.525 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.526 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.526 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.527 10.0.9.74:50000 read 16
1.911390686e+01\n
2019/04/08 15:25:41.537 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.537 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.537 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.538 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.538 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.539 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.539 10.0.9.74:50000 read 16
1.756361389e+01\n
2019/04/08 15:25:41.539 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.539 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.540 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.540 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.540 10.0.9.74:50000 read 16
1.756297302e+01\n
2019/04/08 15:25:41.540 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.541 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.541 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.541 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.542 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.542 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.542 10.0.9.74:50000 read 16
1.566213989e+01\n
2019/04/08 15:25:41.542 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.542 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.543 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.544 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.544 10.0.9.74:50000 read 16
1.566177368e+01\n
2019/04/08 15:25:41.544 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.545 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.545 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.545 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.545 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.546 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.546 10.0.9.74:50000 read 16
1.911167908e+01\n
2019/04/08 15:25:41.546 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.546 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.547 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.547 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.547 10.0.9.74:50000 read 16
1.911430359e+01\n
2019/04/08 15:25:41.798 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.799 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.799 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.799 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.800 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.800 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.800 10.0.9.74:50000 read 16
1.756182861e+01\n
2019/04/08 15:25:41.800 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:41.801 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.802 10.0.9.74:50000 read 1
1
2019/04/08 15:25:41.802 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.802 10.0.9.74:50000 read 16
1.756103516e+01\n
2019/04/08 15:25:41.802 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.803 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.804 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.804 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.805 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.805 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.805 10.0.9.74:50000 read 16
1.566130066e+01\n
2019/04/08 15:25:41.805 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:41.806 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.807 10.0.9.74:50000 read 1
2
2019/04/08 15:25:41.807 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.807 10.0.9.74:50000 read 16
1.566154480e+01\n
2019/04/08 15:25:41.807 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:41.808 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:41.808 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.808 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.809 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.809 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.810 10.0.9.74:50000 read 16
1.911123657e+01\n
2019/04/08 15:25:41.810 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:41.810 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:41.811 10.0.9.74:50000 read 1
3
2019/04/08 15:25:41.811 10.0.9.74:50000 read 1
=
2019/04/08 15:25:41.811 10.0.9.74:50000 read 16
1.911273193e+01\n
PI_SUP_TargetAO: 0.000000 for axis 0
PI_SUP_TargetAO: 0.000000 for axis 1
PI_SUP_TargetAO: 0.000000 for axis 2
iocRun: All initialization complete
asynReport
tcpip_e712 multiDevice:No canBlock:Yes autoConnect:Yes
PIasyn3 multiDevice:Yes canBlock:Yes autoConnect:Yes
Simulation motor driver PIasyn3, numAxes=3
axis 0
axis 1
axis 2
Port: PIasyn3
epics> 2019/04/08 15:25:42.062 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:42.063 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:42.063 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:42.063 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:42.064 10.0.9.74:50000 read 1
1
2019/04/08 15:25:42.064 10.0.9.74:50000 read 1
=
2019/04/08 15:25:42.065 10.0.9.74:50000 read 16
1.756170654e+01\n
2019/04/08 15:25:42.065 10.0.9.74:50000 write 6
POS? 1
2019/04/08 15:25:42.065 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:42.066 10.0.9.74:50000 read 1
1
2019/04/08 15:25:42.066 10.0.9.74:50000 read 1
=
2019/04/08 15:25:42.066 10.0.9.74:50000 read 16
1.756056213e+01\n
2019/04/08 15:25:42.067 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:42.067 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:42.068 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:42.068 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:42.069 10.0.9.74:50000 read 1
2
2019/04/08 15:25:42.069 10.0.9.74:50000 read 1
=
2019/04/08 15:25:42.069 10.0.9.74:50000 read 16
1.566204834e+01\n
2019/04/08 15:25:42.069 10.0.9.74:50000 write 6
POS? 2
2019/04/08 15:25:42.069 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:42.070 10.0.9.74:50000 read 1
2
2019/04/08 15:25:42.070 10.0.9.74:50000 read 1
=
2019/04/08 15:25:42.070 10.0.9.74:50000 read 16
1.566149902e+01\n
2019/04/08 15:25:42.071 10.0.9.74:50000 write 1
\005
2019/04/08 15:25:42.072 10.0.9.74:50000 read 2
0\n
2019/04/08 15:25:42.072 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:42.072 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:42.073 10.0.9.74:50000 read 1
3
2019/04/08 15:25:42.073 10.0.9.74:50000 read 1
=
2019/04/08 15:25:42.073 10.0.9.74:50000 read 16
1.911236572e+01\n
2019/04/08 15:25:42.074 10.0.9.74:50000 write 6
POS? 3
2019/04/08 15:25:42.074 10.0.9.74:50000 write 1
\n
2019/04/08 15:25:42.075 10.0.9.74:50000 read 1
3
2019/04/08 15:25:42.075 10.0.9.74:50000 read 1
=
2019/04/08 15:25:42.075 10.0.9.74:50000 read 16
1.911088562e+01\n
- Replies:
- RE: asynMotor device support and the motor specific driver (asynMotorContorller) Mark Rivers via Tech-talk
- References:
- asynMotor device support and the motor specific driver (asynMotorContorller) Allan Serra Braga Bugyi via Tech-talk
- Re: asynMotor device support and the motor specific driver (asynMotorContorller) Mark Rivers via Tech-talk
- Re: asynMotor device support and the motor specific driver (asynMotorContorller) Allan Serra Braga Bugyi via Tech-talk
- RE: asynMotor device support and the motor specific driver (asynMotorContorller) Mark Rivers via Tech-talk
- Re: asynMotor device support and the motor specific driver (asynMotorContorller) Allan Serra Braga Bugyi via Tech-talk
- Re: asynMotor device support and the motor specific driver (asynMotorContorller) Mark Rivers via Tech-talk
- Navigate by Date:
- Prev: Re: drvAsynIPPortConfigure and I/O Intr with asynRecord possible? Benjamin Franksen via Tech-talk
- Next: RE: asynMotor device support and the motor specific driver (asynMotorContorller) 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 <2019> 2020 2021 2022 2023 2024
- Navigate by Thread:
- Prev: Re: asynMotor device support and the motor specific driver (asynMotorContorller) Mark Rivers via Tech-talk
- Next: RE: asynMotor device support and the motor specific driver (asynMotorContorller) 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 <2019> 2020 2021 2022 2023 2024
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·