EPICS Home

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: Asyn 4-30 Problem on Arm processor
From: Mark Rivers <[email protected]>
To: Jörn Dreyer <[email protected]>
Cc: Epics <[email protected]>
Date: Fri, 17 Mar 2017 11:30:40 +0000 
Hi Jörn,

> I added a call to the base class connect function after I have connected to my device.
> The problem still persists as you can see from the output of the IOC below.
> Now the device is shown as connected.

I am not sure that I agree that the problem still persists.  Previously after iocInit you got:

2017/03/16 16:37:50.614 HAM1 asynManager::queueLockPort locking port
Segmentationfault


Now you get:

2017/03/17 07:39:13.071 HAM1 asynManager::queueLockPort locking port
2017/03/17 07:39:13.081 asynPortDriver::getBounds,low=0, high=65535
2017/03/17 07:39:13.084 asynInt32SyncIO getBounds: status=0 low 0 high 65535
2017/03/17 07:39:13.087 HAM1 queueUnlockPort
2017/03/17 07:39:13.094 HAM1 asynManager::queueLockPort locking port
2017/03/17 07:39:13.094 asynPortDriver::getBounds,low=0, high=65535
2017/03/17 07:39:13.095 asynInt32SyncIO getBounds: status=0 low 0 high 65535
2017/03/17 07:39:13.096 HAM1 queueUnlockPort
2017/03/17 07:39:13.108 HAM1 asynManager::queueLockPort locking port

I don't see a segmentation fault, and I do see successful calls to queueLockPort, queueUnlockPort, and getBounds.

Please add a call to asynReport 1 at the very end of your startup script, after iocInit.

I have a more basic question.  It appears you are writing an asyn driver based on asynPortDriver to talk to the Hamamatsu C11204-02. Would it be possible instead to use drvAsynSerialPort and StreamDevice? Then you only need to write a StreamDevice protocol file, not an asyn driver.

Mark


________________________________
From: Jörn Dreyer [[email protected]]
Sent: Friday, March 17, 2017 1:43 AM
To: Mark Rivers
Cc: Epics
Subject: Re: Asyn 4-30 Problem on Arm processor


Hi Mark,



I added a call to the base class connect function after I have connected to my device. The problem still persists as you can see from the output of the IOC below. Now the device is shown as connected.



Jörn



#!../../bin/linux-arm/crpc
< envPaths_raspi
epicsEnvSet("ARCH","linux-arm")
epicsEnvSet("IOC",raspi01)
epicsEnvSet("TOP","/home/fwkk_scs/Epics/app")
epicsEnvSet("SNCSEQ","/home/fwkk_scs/Epics/seq-2.2.2")
epicsEnvSet("EPICS_BASE","/home/fwkk_scs/Epics/base-3.14.12.5")
epicsEnvSet("ASYN","/home/fwkk_scs/Epics/modules/asyn4-26")
epicsEnvSet("STREAM_PROTOCOL_PATH","/home/fwkk_scs/Epics/app/protocols")
epicsEnvSet("MOTOR","/home/fwkk_scs/Epics/modules/motorR6-9")
epicsEnvSet("NETSNMP","/home/scs/Epics/modules/snmp")
epicsEnvSet("MIBDIRS","/usr/share/mibs/ietf:/home/fwkk_scs/Epics/app/protocols")
epicsEnvSet("WCR_PREF","guru WIENER-CRATE-MIB::")
cd /home/fwkk_scs/Epics/app
## Register all support components
dbLoadDatabase "dbd/crpc.dbd"
crpc_registerRecordDeviceDriver pdbbase
# Setup for HAMAMATSU power supply
HamamatsuC11204_02AsynPortDriverConfigure("HAM1","/dev/ttyUSB0",0)
asynSetTraceMask("HAM1",0,0x1f)
asynSetTraceIOMask("HAM1",0,0x1f)
dbLoadRecords "db/Hamamatsu_C11204.db"
dbLoadRecords ("db/iocAdminSoft.db", "IOC=raspi01")
dbLoadRecords ("db/iocAdminScanMon.db", "IOC=raspi01")
## Run this to trace the stages of iocInit
#traceIocInit
asynReport 1
HAM1 multiDevice:No canBlock:No autoConnect:Yes
   enabled:Yes connected:Yes numberConnects 1
   nDevices 0 nQueued 0 blocked:No
   asynManagerLock:No synchronousLock:No
   exceptionActive:No exceptionUsers 0 exceptionNotifys 0
   traceMask:0x1f traceIOMask:0x1f traceInfoMask:0x1
Port: HAM1
 Timestamp: <undefined>
 Input EOS[0]:
 Output EOS[0]:
Parameter list 0
Number of parameters is: 19
Parameter 0 type=asynFloat64, name=SECOND_SIDE_HIGH_TEMP_CORR_FACTOR, value is undefined
Parameter 1 type=asynFloat64, name=SECOND_SIDE_LOW_TEMP_CORR_FACTOR, value is undefined
Parameter 2 type=asynFloat64, name=PRIMARY_SIDE_HIGH_TEMP_CORR_FACTOR, value is undefined
Parameter 3 type=asynFloat64, name=PRIMARY_SIDE_LOW_TEMP_CORR_FACTOR, value is undefined
Parameter 4 type=asynFloat64, name=REFERENCE_VOLTAGE, value is undefined
Parameter 5 type=asynFloat64, name=REFERENCE_TEMPERATURE, value is undefined
Parameter 6 type=asynInt32, name=STATUS_READ, value is undefined
Parameter 7 type=asynFloat64, name=VOLTAGE_READ, value is undefined
Parameter 8 type=asynFloat64, name=CURRENT_READ, value is undefined
Parameter 9 type=asynFloat64, name=TEMPERATURE_READ, value is undefined
Parameter 10 type=string, name=DEVICE_NAME_READ, value is undefined
Parameter 11 type=string, name=DEVICE_VERSION_READ, value is undefined
Parameter 12 type=string, name=DEVICE_BUILD_DATE_READ, value is undefined
Parameter 13 type=asynInt32, name=HV_OUTPUT_ON, value is undefined
Parameter 14 type=asynInt32, name=HV_OUTPUT_OFF, value is undefined
Parameter 15 type=asynInt32, name=RESET, value is undefined
Parameter 16 type=asynInt32, name=SET_TEMP_COMP_MODE, value is undefined
Parameter 17 type=asynInt32, name=MODE_WRITE, value is undefined
Parameter 18 type=asynInt32, name=MODE_READ, value is undefined
asynReport 1
HAM1 multiDevice:No canBlock:No autoConnect:Yes
   enabled:Yes connected:Yes numberConnects 1
   nDevices 0 nQueued 0 blocked:No
   asynManagerLock:No synchronousLock:No
   exceptionActive:No exceptionUsers 0 exceptionNotifys 0
   traceMask:0x1f traceIOMask:0x1f traceInfoMask:0x1
Port: HAM1
 Timestamp: <undefined>
 Input EOS[0]:
 Output EOS[0]:
Parameter list 0
Number of parameters is: 19
Parameter 0 type=asynFloat64, name=SECOND_SIDE_HIGH_TEMP_CORR_FACTOR, value is undefined
Parameter 1 type=asynFloat64, name=SECOND_SIDE_LOW_TEMP_CORR_FACTOR, value is undefined
Parameter 2 type=asynFloat64, name=PRIMARY_SIDE_HIGH_TEMP_CORR_FACTOR, value is undefined
Parameter 3 type=asynFloat64, name=PRIMARY_SIDE_LOW_TEMP_CORR_FACTOR, value is undefined
Parameter 4 type=asynFloat64, name=REFERENCE_VOLTAGE, value is undefined
Parameter 5 type=asynFloat64, name=REFERENCE_TEMPERATURE, value is undefined
Parameter 6 type=asynInt32, name=STATUS_READ, value is undefined
Parameter 7 type=asynFloat64, name=VOLTAGE_READ, value is undefined
Parameter 8 type=asynFloat64, name=CURRENT_READ, value is undefined
Parameter 9 type=asynFloat64, name=TEMPERATURE_READ, value is undefined
Parameter 10 type=string, name=DEVICE_NAME_READ, value is undefined
Parameter 11 type=string, name=DEVICE_VERSION_READ, value is undefined
Parameter 12 type=string, name=DEVICE_BUILD_DATE_READ, value is undefined
Parameter 13 type=asynInt32, name=HV_OUTPUT_ON, value is undefined
Parameter 14 type=asynInt32, name=HV_OUTPUT_OFF, value is undefined
Parameter 15 type=asynInt32, name=RESET, value is undefined
Parameter 16 type=asynInt32, name=SET_TEMP_COMP_MODE, value is undefined
Parameter 17 type=asynInt32, name=MODE_WRITE, value is undefined
Parameter 18 type=asynInt32, name=MODE_READ, value is undefined
cd /home/fwkk_scs/Epics/app/iocBoot/ioccrpc
iocInit
Starting iocInit
############################################################################
## EPICS R3.15.5
## EPICS Base built Mar  3 2017
############################################################################
2017/03/17 07:39:13.071 HAM1 asynManager::queueLockPort locking port
2017/03/17 07:39:13.081 asynPortDriver::getBounds,low=0, high=65535
2017/03/17 07:39:13.084 asynInt32SyncIO getBounds: status=0 low 0 high 65535
2017/03/17 07:39:13.087 HAM1 queueUnlockPort
2017/03/17 07:39:13.094 HAM1 asynManager::queueLockPort locking port
2017/03/17 07:39:13.094 asynPortDriver::getBounds,low=0, high=65535
2017/03/17 07:39:13.095 asynInt32SyncIO getBounds: status=0 low 0 high 65535
2017/03/17 07:39:13.096 HAM1 queueUnlockPort
2017/03/17 07:39:13.108 HAM1 asynManager::queueLockPort locking port
Replies:
Re: Asyn 4-30 Problem on Arm processor Jörn Dreyer
References:
Asyn 4-30 Problem on Arm processor Jörn Dreyer
Re: Asyn 4-30 Problem on Arm processor Jörn Dreyer
RE: Asyn 4-30 Problem on Arm processor Mark Rivers
Re: Asyn 4-30 Problem on Arm processor Jörn Dreyer
Navigate by Date:
Prev: Re: Asyn 4-30 Problem on Arm processor Jörn Dreyer
Next: Re: Asyn 4-30 Problem on Arm processor Jörn Dreyer
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: Asyn 4-30 Problem on Arm processor Jörn Dreyer
Next: Re: Asyn 4-30 Problem on Arm processor Jörn Dreyer
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