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  <20152016  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  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: calling the output of one record into another record
From: Eric Norum <[email protected]>
To: Ana Malagon <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Thu, 15 Jan 2015 12:16:50 -0800
Have you added asyn.dbd  to your application?  The listing below shows a bunch of missing commands.


On Jan 15, 2015, at 11:50 AM, Ana Malagon <[email protected]> wrote:

Hi Mark,

Thanks -  I've moved over to StreamDevice and now have a very simpleminded question. I've created a test application following the instructions here; make runs successfully in my top directory. When I run st.cmd, however, I get a 'no reply from device with 1000 ms'. I believe I'm using up to date versions of asyn (4.22), stream (2.6), and base (3.14). I'm sure I'm missing something obvious - is there some other setup step that I should have done? Below is the output from st.cmd -

Thanks,

Ana

admx@admxcontrol:~/admxepics/devices/fieldfoxstream/iocBoot/iocFIELDFOXSTREAMtest$ ./st.cmd

#!../../bin/linux-x86_64/FIELDFOXSTREAMtest

## You may have to change FIELDFOXSTREAMtest to something else

## everywhere it appears in this file

< envPaths

epicsEnvSet("ARCH","linux-x86_64")

epicsEnvSet("IOC","iocFIELDFOXSTREAMtest")

epicsEnvSet("TOP","/home/admx/admxepics/devices/fieldfoxstream")

epicsEnvSet("ASYN","/home/admx/epics/asyn4-22")

epicsEnvSet("STREAM","/home/admx/epics/StreamDevice-2-6")

epicsEnvSet("EPICS_BASE","/home/admx/epics/base-3.14.12.4")

epicsEnvSet "STREAM_PROTOCOL_PATH" "/home/admx/admxepics/devices/fieldfoxstream/db"

epicsEnvSet "P" "fieldfoxstream"

epicsEnvSet "R" "Test"

cd /home/admx/admxepics/devices/fieldfoxstream

## Register all support components

dbLoadDatabase "dbd/FIELDFOXSTREAMtest.dbd"

FIELDFOXSTREAMtest_registerRecordDeviceDriver pdbbase

drvAsynIPPortConfigure("L0", "10.95.101.76:5025", 0, 0, 0)

asynOctetSetInputEos("L0", 0, "\n")

st.cmd line 18: Command asynOctetSetInputEos not found. <<<<<<<<<<<<<<<<!!!!!!!!!!!

asynOctetSetOutputEos("L0", 0, "\n")

st.cmd line 19: Command asynOctetSetOutputEos not found. <<<<<<<<<<<<<<<<!!!!!!!!!!!

asynSetTraceIOMask("L0", -1, 0x2)

st.cmd line 20: Command asynSetTraceIOMask not found. <<<<<<<<<<<<<<<<!!!!!!!!!!!

asynSetTraceMask("L0", -1, 0x9)

st.cmd line 21: Command asynSetTraceMask not found. <<<<<<<<<<<<<<<<!!!!!!!!!!!

## Load record instances

dbLoadRecords("db/devFIELDFOXSTREAM.db","P=fieldfoxstream, R=Test, PORT=L0, A=0")

cd /home/admx/admxepics/devices/fieldfoxstream/iocBoot/iocFIELDFOXSTREAMtest

iocInit

Starting iocInit

############################################################################

## EPICS R3.14.12.4 $Date: Mon 2013-12-16 15:51:45 -0600$

## EPICS Base built May 20 2014

############################################################################

cas warning: Configured TCP port was unavailable.

cas warning: Using dynamically assigned TCP port 43138,

cas warning: but now two or more servers share the same UDP port.

cas warning: Depending on your IP kernel this server may not be

cas warning: reachable with UDP unicast (a host's IP in EPICS_CA_ADDR_LIST)

iocRun: All initialization complete

## Start any sequence programs

#seq sncxxx,"user=admxHost"

epics> 2015/01/15 11:20:44.557860 L0 fieldfoxstreamTestIDN: No reply from device within 1000 ms

2015/01/15 11:20:45.559805 L0 fieldfoxstreamTestIDNwf: No reply from device within 1000 ms


-- 
Eric Norum
[email protected]





Replies:
RE: calling the output of one record into another record Mark Rivers
References:
calling the output of one record into another record Ana Malagon
RE: calling the output of one record into another record Mark Rivers
Re: calling the output of one record into another record Ana Malagon

Navigate by Date:
Prev: Re: calling the output of one record into another record Ana Malagon
Next: RE: calling the output of one record into another record Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: calling the output of one record into another record Ana Malagon
Next: RE: calling the output of one record into another record Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024