The epicsTimer quantum is that of the vxWorks system clock and is almost certainly too large for this to be accomplished.
If you have a hardware timer available you could use it to generate interrupts and perform the timing that way.
If you need really precise timing you might have to move all this out to custom hardware.
On Jun 3, 2010, at 1:15 PM, Szalata, Zenon M. wrote:
> I have a VME system, which is external trigger driven. I wrote a device driver for one of the modules in the VME crate. The device driver is so far OSI. I am using EPICS R3.14.11 and vxWorks 6.6.
>
> In my device driver, I need to execute a command a few hundred of micro seconds after the trigger. The device driver responds to the trigger, by queuing a call back routine. I would like to setup in the trigger handling call back routine another call back routine to be called a few hundred microseconds later. I don't want to call vxWorks routines directly. Looking through "EPICS: Input/Output Controller Application Developer's Guide", it seems to me that epicsTimer is a good candidate. Unfortunately, as it is for me, this guide is very good once I know what I am doing. Since I have not used epicsTimer before, the description in the guide is not explicit enough to be useful.
>
> I would greatly appreciate if someone sent me an example of how to accomplish my goal in a device driver written in C.
>
> Thank you,
> Zen
>
--
Eric Norum
[email protected]
- Replies:
- Re: epicsTimer Ron Sluiter
- References:
- epicsTimer Szalata, Zenon M.
- Navigate by Date:
- Prev:
epicsTimer Szalata, Zenon M.
- Next:
Re: epicsTimer Ron Sluiter
- 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:
epicsTimer Szalata, Zenon M.
- Next:
Re: epicsTimer Ron Sluiter
- 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
|