> The recored TEST:OUT0-O is connected to hardware all output records are not synchronous.
Are you sure they are not synchronous? What flags did you use in your asyn driver when calling pasynManager->registerPort? Are you using asynPortDriver base class?
> Hardware also having no delay.
What do you mean by that? How have you measured it?
> is dfanout record execute each link one by one or all simultaneously?
It processes one link at a time. How could it do them simultaneously?
Mark
The recored TEST:OUT0-O is connected to hardware all output records are not synchronous.
I am using asynDriver. and all these records have same asyn intereface as they are similar.
Hardware also having no delay.
is dfanout record execute each link one by one or all simultaneously?
From: Mark Rivers <[email protected]>
Sent: Fri, 14 Feb 2014 20:44:44
To: "'[email protected]'" <[email protected]>
Cc: techtalk <[email protected]>
Subject: Re: record processing time
Hi Vishnu,
Please tell us about your output records, TEST:OUT0-O, etc. Are they connected to hardware? If so, is the device support synchronous or asynchronous, and what driver are you using? If they are connected to hardware and the device support
is synchronous, then 50 microseconds may just be the time it takes the driver to do the I/O. If the records are not connected to hardware then how did you measure the 50 microseconds?
Mark
Hi,
In my application i am putting value on 4 output port lines simultaneously with dfanout record.
record (dfanout,"TEST:EVENT1-FOUT")
field(DESC, "stop all event simaltanously")
field(DOL, "TEST:WAIT-EVENT")
field(OMSL, "closed_loop")
field(OUTA, "TEST:OUT0-O PP")
field(OUTB, "TEST:OUT1-O PP")
field(OUTC, "TEST:OUT2-O PP")
field(OUTD, "TEST:OUT3-O PP")
"TEST:OUT0-O, TEST:OUT1-O, TEST:OUT2-O, and TEST:OUT3-O are 4 output record putting the values on output port lines.
The TEST:WAIT-EVENT is the taking value from User interface. 0 or 1.
I observed the delay between each output is approximately 50 micro second. so total delay from first to last PV is ~200 micro second.
The OS running the IOC is RHEL.
I would like to know this delay time is normal in EPICS or i can even get better with some mechanism.
From: Mark Rivers <[email protected]>
Sent: Wed, 12 Feb 2014 20:39:16
To: Vishnu Patel <[email protected]>, "techtalk " <[email protected]>
Subject: Re: record processing time
The processing time depends of course on the record type and the CPU you are using. But it is typically on the order of a few microseconds.
________________________________
From: [email protected] [[email protected]] on behalf of Vishnu Patel [[email protected]]
Sent: Wednesday, February 12, 2014 8:16 AM
To: techtalk
Subject: record processing time
Hi,
I would like to know about time required for record processing.
In my application
When PV1 becomes 1 (scan I/O Intr.), process waveform record with FLNK and then first element value of waveform record is placed in PVx and second element value of waveform record is put in PVy with subArray record.
I would like to know, what is the process time of EPICS record processing?
Thank you
Vishnu
[http://sigads.rediff.com/RealMedia/ads/adstream_nx.ads/www.rediffmail.com/signatureline.htm@Middle]<http://sigads.rediff.com/RealMedia/ads/click_nx.ads/www.rediffmail.com/signatureline.htm@Middle?>
Get your own FREE website, FREE domain & FREE mobile app with Company email.
Know More ><http://track.rediff.com/click?url="">>
Get your own
FREE website,
FREE domain &
FREE mobile app with Company email.
|
Know
More >
|
Get your own
FREE website,
FREE domain &
FREE mobile app with Company email.
|
Know
More >
|