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: sequencer + streamdevice |
From: | Andrew Johnson <[email protected]> |
To: | Christoph Burandt <[email protected]> |
Cc: | [email protected] |
Date: | Mon, 28 Oct 2013 14:20:37 -0500 |
Hi Christoph,Check that the DBD file for your combined IOC contains a registrar entry for your sequence program (in the makeBaseApp example that is this line:
registrar(sncExampleRegistrar)This is what causes the sequencer to be included in the IOC executable and the seq command to be registered when the startup script runs.
HTH, - Andrew On 10/28/2013 08:07 AM, Christoph Burandt wrote:
Hello, I'm having trouble setting up an IOC which provides both, the sequencer and the streamdevice support at the same time. Using "makeBaseApp -t ioc" allowed me to setup basic IOCs that support either the sequencer or the StreamDevice support. I therefore modified the files configure/RELEASE iocApp/src/Makefile accordingly. I checked that the resulting IOCs are ok by typing "help" in the IOC shell -> either the "seq" or the "drvAsynIPPortConfigure" will be part of the list of supported commands. I could also execute the state machine from "makeBaseApp -t example". If I try to write a Makefile which combines both features, "make" does not complain (as it seems to me). But "help" in the ioc shell tells me that "seq" is not a known command. Can anyone explain what goes wrong here? (The iocApp/src/Makefile of the "combined" IOC is attached) Greetings, Christoph
-- Advertising may be described as the science of arresting the human intelligence long enough to get money from it. -- Stephen Leacock