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 14:58:48 +0000 |
|
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
#!/usr/local/epics/synApps_6_0/support/motor-R6-10-1/motorExApp/WithAsyn/O.linux-x86_64/WithAsyn < asynMotor.E-712.cmd iocInit
Thank you!
Best regards,
Allan S. B. Bugyi Technology Development Analyst [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]>
Enviado: segunda-feira, 8 de abril de 2019 11:30:23 Para: Allan Serra Braga Bugyi Cc: [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] <[email protected]> on behalf of Allan Serra Braga Bugyi via Tech-talk <[email protected]> Sent: Monday, April 8, 2019 8:39 AM To: [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] (+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. |
csEnvSet("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")
asynSetTraceMask("tcpip_e712", -1, 0x9)
asynSetTraceIOMask("tcpip_e712", -1, 0x2)
< asynMotor.E-712.cmd
dbLoadTemplate("asynMotor.substitutions.E-712")
PI_GCS2_CreateController("PIasyn3", "tcpip_e712",3, 0,0, 10, 250)
2019/04/04 10:42:27.461 PIInterface::sendAndReceive() sending "*IDN?"
2019/04/04 10:42:27.461 10.0.9.74:50000 write 5
*IDN?
2019/04/04 10:42:27.461 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.466 10.0.9.74:50000 read 47
(c)2015 Physik Instrumente (PI) GmbH & Co. KG,
2019/04/04 10:42:27.466 10.0.9.74:50000 read 7
E-727,
2019/04/04 10:42:27.466 10.0.9.74:50000 read 12
0118027690,
2019/04/04 10:42:27.467 10.0.9.74:50000 read 12
14.04.01.02\n
2019/04/04 10:42:27.467 PIInterface::sendAndReceive() received "(c)2015 Physik Instrumente (PI) GmbH & Co. KG, E-727, 0118027690, 14.04.01.02"
2019/04/04 10:42:27.467 read from tcpip_e712: (c)2015 Physik Instrumente (PI) GmbH & Co. KG, E-727, 0118027690, 14.04.01.02
2019/04/04 10:42:27.467 PIInterface::sendAndReceive() sending "VEL?"
2019/04/04 10:42:27.467 10.0.9.74:50000 write 4
VEL?
2019/04/04 10:42:27.467 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.473 10.0.9.74:50000 read 1
1
2019/04/04 10:42:27.473 10.0.9.74:50000 read 1
=
2019/04/04 10:42:27.474 10.0.9.74:50000 read 17
7.500000000e+03 \n
2019/04/04 10:42:27.474 10.0.9.74:50000 read 20
2=7.500000000e+03 \n3
2019/04/04 10:42:27.476 10.0.9.74:50000 read 17
=2.000000000e+04\n
2019/04/04 10:42:27.476 PIInterface::sendAndReceive() received "1=7.500000000e+03
2=7.500000000e+03
3=2.000000000e+04"
2019/04/04 10:42:27.476 PIInterface::sendAndReceive() sending "SAI?"
2019/04/04 10:42:27.476 10.0.9.74:50000 write 4
SAI?
2019/04/04 10:42:27.476 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.481 10.0.9.74:50000 read 6
1 \n2 \n
2019/04/04 10:42:27.481 10.0.9.74:50000 read 2
3\n
2019/04/04 10:42:27.481 PIInterface::sendAndReceive() received "1
2
3"
PIasynAxis::PIasynAxis() 0: 1
2019/04/04 10:42:27.481 10.0.9.74:50000 write 7
SVO 1 1
2019/04/04 10:42:27.481 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.482 10.0.9.74:50000 write 4
ERR?
2019/04/04 10:42:27.482 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.488 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:27.488 10.0.9.74:50000 write 6
VEL? 1
2019/04/04 10:42:27.488 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.493 10.0.9.74:50000 read 2
1=
2019/04/04 10:42:27.493 10.0.9.74:50000 read 16
7.500000000e+03\n
2019/04/04 10:42:27.493 10.0.9.74:50000 write 6
POS? 1
2019/04/04 10:42:27.493 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.497 10.0.9.74:50000 read 1
1
2019/04/04 10:42:27.498 10.0.9.74:50000 read 17
=1.865460205e+01\n
2019/04/04 10:42:27.498 10.0.9.74:50000 write 6
TMN? 1
2019/04/04 10:42:27.498 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.502 10.0.9.74:50000 read 2
1=
2019/04/04 10:42:27.502 10.0.9.74:50000 read 16
0.000000000e+00\n
2019/04/04 10:42:27.503 10.0.9.74:50000 write 6
TMX? 1
2019/04/04 10:42:27.503 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.661 10.0.9.74:50000 read 1
1
2019/04/04 10:42:27.661 10.0.9.74:50000 read 17
=3.000000000e+02\n
PIasynAxis::PIasynAxis() 1: 2
2019/04/04 10:42:27.661 10.0.9.74:50000 write 7
SVO 2 1
2019/04/04 10:42:27.662 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.662 10.0.9.74:50000 write 4
ERR?
2019/04/04 10:42:27.662 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.666 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:27.666 10.0.9.74:50000 write 6
VEL? 2
2019/04/04 10:42:27.666 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.670 10.0.9.74:50000 read 1
2
2019/04/04 10:42:27.671 10.0.9.74:50000 read 17
=7.500000000e+03\n
2019/04/04 10:42:27.671 10.0.9.74:50000 write 6
POS? 2
2019/04/04 10:42:27.671 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.675 10.0.9.74:50000 read 2
2=
2019/04/04 10:42:27.675 10.0.9.74:50000 read 16
1.672723389e+01\n
2019/04/04 10:42:27.676 10.0.9.74:50000 write 6
TMN? 2
2019/04/04 10:42:27.676 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.680 10.0.9.74:50000 read 1
2
2019/04/04 10:42:27.680 10.0.9.74:50000 read 17
=0.000000000e+00\n
2019/04/04 10:42:27.681 10.0.9.74:50000 write 6
TMX? 2
2019/04/04 10:42:27.681 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.685 10.0.9.74:50000 read 2
2=
2019/04/04 10:42:27.685 10.0.9.74:50000 read 16
3.000000000e+02\n
PIasynAxis::PIasynAxis() 2: 3
2019/04/04 10:42:27.686 10.0.9.74:50000 write 7
SVO 3 1
2019/04/04 10:42:27.686 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.686 10.0.9.74:50000 write 4
ERR?
2019/04/04 10:42:27.686 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.692 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:27.692 10.0.9.74:50000 write 6
VEL? 3
2019/04/04 10:42:27.692 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.697 10.0.9.74:50000 read 2
3=
2019/04/04 10:42:27.697 10.0.9.74:50000 read 16
2.000000000e+04\n
2019/04/04 10:42:27.697 10.0.9.74:50000 write 6
POS? 3
2019/04/04 10:42:27.697 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.703 10.0.9.74:50000 read 1
3
2019/04/04 10:42:27.703 10.0.9.74:50000 read 17
=2.012329102e+01\n
2019/04/04 10:42:27.704 10.0.9.74:50000 write 6
TMN? 3
2019/04/04 10:42:27.704 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.861 10.0.9.74:50000 read 2
3=
2019/04/04 10:42:27.862 10.0.9.74:50000 read 16
0.000000000e+00\n
2019/04/04 10:42:27.862 10.0.9.74:50000 write 6
TMX? 3
2019/04/04 10:42:27.862 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.866 10.0.9.74:50000 read 1
3
2019/04/04 10:42:27.866 10.0.9.74:50000 read 1
=
2019/04/04 10:42:27.866 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")
2019/04/04 10:42:27.867 10.0.9.74:50000 write 1
\005
dbLoadRecords("/usr/local/epics/motor-2019-04-02/db/PI_Support.db","P=PIE712:,R=m3:,PORT=PIasyn3,ADDR=2,TIMEOUT=1")
dbLoadRecords("/usr/local/epics/motor-2019-04-02/db/PI_SupportCtrl.db","P=PIE712:,R=m1:,PORT=PIasyn3,ADDR=0,TIMEOUT=1")
#setIocLogDisable 0
#iocLogInit
iocInit
Starting iocInit
############################################################################
## EPICS R3.15.6
## EPICS Base built Mar 7 2019
############################################################################
2019/04/04 10:42:27.869 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:27.869 10.0.9.74:50000 write 6
POS? 1
2019/04/04 10:42:27.870 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.874 10.0.9.74:50000 read 1
1
2019/04/04 10:42:27.874 10.0.9.74:50000 read 1
=
2019/04/04 10:42:27.875 10.0.9.74:50000 read 16
1.865653992e+01\n
2019/04/04 10:42:27.875 10.0.9.74:50000 write 6
POS? 1
2019/04/04 10:42:27.875 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.879 10.0.9.74:50000 read 1
1
2019/04/04 10:42:27.879 10.0.9.74:50000 read 1
=
2019/04/04 10:42:27.880 10.0.9.74:50000 read 16
1.865611267e+01\n
2019/04/04 10:42:27.880 10.0.9.74:50000 write 1
\005
2019/04/04 10:42:27.883 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:27.883 10.0.9.74:50000 write 6
POS? 2
2019/04/04 10:42:27.883 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.888 10.0.9.74:50000 read 1
2
2019/04/04 10:42:27.888 10.0.9.74:50000 read 1
=
2019/04/04 10:42:27.889 10.0.9.74:50000 read 16
1.672848511e+01\n
2019/04/04 10:42:27.889 10.0.9.74:50000 write 6
POS? 2
2019/04/04 10:42:27.889 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.895 10.0.9.74:50000 read 1
2
2019/04/04 10:42:27.895 10.0.9.74:50000 read 1
=
2019/04/04 10:42:27.896 10.0.9.74:50000 read 16
1.673049927e+01\n
2019/04/04 10:42:27.896 10.0.9.74:50000 write 1
\005
2019/04/04 10:42:27.898 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:27.899 10.0.9.74:50000 write 6
POS? 3
2019/04/04 10:42:27.899 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.903 10.0.9.74:50000 read 1
3
2019/04/04 10:42:27.904 10.0.9.74:50000 read 1
=
2019/04/04 10:42:27.904 10.0.9.74:50000 read 16
2.012075806e+01\n
2019/04/04 10:42:27.904 10.0.9.74:50000 write 6
POS? 3
2019/04/04 10:42:27.904 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:27.908 10.0.9.74:50000 read 1
3
2019/04/04 10:42:27.909 10.0.9.74:50000 read 1
=
2019/04/04 10:42:27.909 10.0.9.74:50000 read 16
2.012399292e+01\n
2019/04/04 10:42:27.919 10.0.9.74:50000 write 1
\005
2019/04/04 10:42:28.067 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:28.067 10.0.9.74:50000 write 6
POS? 1
2019/04/04 10:42:28.067 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.072 10.0.9.74:50000 read 1
1
2019/04/04 10:42:28.072 10.0.9.74:50000 read 1
=
2019/04/04 10:42:28.072 10.0.9.74:50000 read 16
1.865763855e+01\n
2019/04/04 10:42:28.072 10.0.9.74:50000 write 6
POS? 1
2019/04/04 10:42:28.073 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.076 10.0.9.74:50000 read 1
1
2019/04/04 10:42:28.076 10.0.9.74:50000 read 1
=
2019/04/04 10:42:28.077 10.0.9.74:50000 read 16
1.865669250e+01\n
2019/04/04 10:42:28.077 10.0.9.74:50000 write 1
\005
2019/04/04 10:42:28.080 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:28.080 10.0.9.74:50000 write 6
POS? 2
2019/04/04 10:42:28.080 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.085 10.0.9.74:50000 read 1
2
2019/04/04 10:42:28.085 10.0.9.74:50000 read 1
=
2019/04/04 10:42:28.085 10.0.9.74:50000 read 16
1.672903442e+01\n
2019/04/04 10:42:28.086 10.0.9.74:50000 write 6
POS? 2
2019/04/04 10:42:28.086 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.092 10.0.9.74:50000 read 1
2
2019/04/04 10:42:28.093 10.0.9.74:50000 read 1
=
2019/04/04 10:42:28.093 10.0.9.74:50000 read 16
1.672955322e+01\n
2019/04/04 10:42:28.093 10.0.9.74:50000 write 1
\005
2019/04/04 10:42:28.096 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:28.096 10.0.9.74:50000 write 6
POS? 3
2019/04/04 10:42:28.096 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.102 10.0.9.74:50000 read 2
3=
2019/04/04 10:42:28.102 10.0.9.74:50000 read 16
2.012541199e+01\n
2019/04/04 10:42:28.103 10.0.9.74:50000 write 6
POS? 3
2019/04/04 10:42:28.103 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.107 10.0.9.74:50000 read 1
3
2019/04/04 10:42:28.107 10.0.9.74:50000 read 1
=
2019/04/04 10:42:28.107 10.0.9.74:50000 read 16
2.012310791e+01\n
2019/04/04 10:42:28.118 10.0.9.74:50000 write 1
\005
2019/04/04 10:42:28.269 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:28.270 10.0.9.74:50000 write 6
POS? 1
2019/04/04 10:42:28.270 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.274 10.0.9.74:50000 read 1
1
2019/04/04 10:42:28.275 10.0.9.74:50000 read 1
=
2019/04/04 10:42:28.275 10.0.9.74:50000 read 16
1.865681458e+01\n
2019/04/04 10:42:28.275 10.0.9.74:50000 write 6
POS? 1
2019/04/04 10:42:28.275 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.279 10.0.9.74:50000 read 2
1=
2019/04/04 10:42:28.280 10.0.9.74:50000 read 16
1.865689087e+01\n
2019/04/04 10:42:28.280 10.0.9.74:50000 write 1
\005
2019/04/04 10:42:28.282 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:28.283 10.0.9.74:50000 write 6
POS? 2
2019/04/04 10:42:28.283 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.287 10.0.9.74:50000 read 2
2=
2019/04/04 10:42:28.288 10.0.9.74:50000 read 16
1.672743225e+01\n
2019/04/04 10:42:28.288 10.0.9.74:50000 write 6
POS? 2
2019/04/04 10:42:28.288 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.292 10.0.9.74:50000 read 1
2
2019/04/04 10:42:28.292 10.0.9.74:50000 read 17
=1.672921753e+01\n
2019/04/04 10:42:28.293 10.0.9.74:50000 write 1
\005
2019/04/04 10:42:28.297 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:28.297 10.0.9.74:50000 write 6
POS? 3
2019/04/04 10:42:28.297 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.303 10.0.9.74:50000 read 1
3
2019/04/04 10:42:28.304 10.0.9.74:50000 read 17
=2.012115479e+01\n
2019/04/04 10:42:28.304 10.0.9.74:50000 write 6
POS? 3
2019/04/04 10:42:28.305 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.310 10.0.9.74:50000 read 2
3=
2019/04/04 10:42:28.310 10.0.9.74:50000 read 16
2.012239075e+01\n
2019/04/04 10:42:28.320 10.0.9.74:50000 write 1
\005
iocRun: All initialization complete
#setIocLogDisable 0
#iocLogInit
#iocLogShow 5000
2019/04/04 10:42:28.474 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:28.474 10.0.9.74:50000 write 6
POS? 1
2019/04/04 10:42:28.474 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.479 10.0.9.74:50000 read 2
1=
2019/04/04 10:42:28.479 10.0.9.74:50000 read 16
1.865728760e+01\n
2019/04/04 10:42:28.480 10.0.9.74:50000 write 6
POS? 1
2019/04/04 10:42:28.480 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.484 10.0.9.74:50000 read 1
1
2019/04/04 10:42:28.484 10.0.9.74:50000 read 17
=1.865586853e+01\n
2019/04/04 10:42:28.484 10.0.9.74:50000 write 1
\005
2019/04/04 10:42:28.487 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:28.487 10.0.9.74:50000 write 6
POS? 2
2019/04/04 10:42:28.487 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.492 10.0.9.74:50000 read 1
2
2019/04/04 10:42:28.492 10.0.9.74:50000 read 17
=1.672785950e+01\n
2019/04/04 10:42:28.492 10.0.9.74:50000 write 6
POS? 2
2019/04/04 10:42:28.492 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.496 10.0.9.74:50000 read 2
2=
2019/04/04 10:42:28.497 10.0.9.74:50000 read 16
1.672647095e+01\n
2019/04/04 10:42:28.497 10.0.9.74:50000 write 1
\005
2019/04/04 10:42:28.502 10.0.9.74:50000 read 2
0\n
2019/04/04 10:42:28.502 10.0.9.74:50000 write 6
POS? 3
2019/04/04 10:42:28.502 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.509 10.0.9.74:50000 read 2
3=
2019/04/04 10:42:28.509 10.0.9.74:50000 read 16
2.012255859e+01\n
2019/04/04 10:42:28.509 10.0.9.74:50000 write 6
POS? 3
2019/04/04 10:42:28.509 10.0.9.74:50000 write 1
\n
2019/04/04 10:42:28.513 10.0.9.74:50000 read 1
3
2019/04/04 10:42:28.514 10.0.9.74:50000 read 17
=2.012219238e+01\n
e
- 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
- Navigate by Date:
- Prev: Re: asynMotor device support and the motor specific driver (asynMotorContorller) Peterson, Kevin M. via Tech-talk
- Next: Re: firewalld configuration for EPICS? Benjamin Franksen 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) Peterson, Kevin M. 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 ·