Thanks for sharing your thought. Actually you triggered me to ask
another question: One of the major achievements in 3.14 is the
introduction of the OSI which supports iocCore on platforms besides
vxWorks. What kind of "breakthrough" is in 3.15, the post pi era of
EPICS? Are there any fundamental changes/improvements on the iocCore
and Channel access?
It is very interesting to see similar statements in the release notes
of 3.14.0alpha1 and 3.15.0.x: "Please don't use it for existing
operational systems", "EPICS Base 3.15.0.x releases are not intended
for use in production systems.". It is surprising that it takes about
one decade to release each major version (<pi, 3.14, >pi).
Currently, I'm not very interested in EPICSv4 since the V3 is good
enough for all kinds of controls. For me, V3 is complicated enough if
I want to dig into the cores. After I read some online documents about
V4, the V4 seems more complicated. Can anyone share your experience of
understanding and using V4? I will give a try on V4 when I have enough
On Fri, Oct 26, 2012 at 3:24 AM, Ralph Lange <Ralph.Lange@gmx.de> wrote:
> On 25.10.2012 20:04, Jack Smith wrote:
>> Wow, what diverse views! Thank all for sharing your thoughts.
>> Ernest is right. The original term "IOC" covers every case. The term
>> "softIOC" seems to make simple thing complicated.
> Here's one more:
> The term "soft IOC" originated with the introduction of the OSI library
> layer in EPICS Base 3.14.
> Before that, an IOC would always run on a dedicated, hard real-time
> system. After that, you could run multiple IOCs as processes on a
> full-size OS, only allowing for soft real-time in most cases.
> So for me, the difference is the not the hardware connection, but the
> platform an IOC runs on.
> If it runs on a machine that is able to run multiple IOCs, I would call
> it a soft IOC. There are grey-zone cases, I know.
> I often use the IOC console as a hint. If the last inch is through a
> serial line, it probably is a hard IOC. If it is solely through a file
> descriptor, it probably is a soft IOC.
> But that's just my universe....
- Re: 3.14 v.s. 3.15 vs. v4 Andrew Johnson
- Navigate by Date:
Re: waveform record: how its VAL get data? any potential memory leak? ... Jack Smith
Re: waveform record: how its VAL get data? any potential memory leak? ... Andrew Johnson
- Navigate by Thread:
Re: User Created File Types: FILE TYPE += ABC [EPICS R3-14-12] Bruce Hill
Re: 3.14 v.s. 3.15 vs. v4 Andrew Johnson