EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  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  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: maybe off topic, maybe not :-)
From: "Liyu, Andrei" <[email protected]>
To: [email protected]
Date: Tue, 05 Jul 2005 12:31:08 -0400
Hi, All

	I read new branch of epics tech-talk about core-talk. There are
a lot of messages to do something in newest V4 version. There are
suggestions/examples how it should be done. It is fine and nice ...
	But I couldn't find the MAIN start points. 
- Why must it be changed? For example, if I am not mistaken main point
of 3.13 -> 3.14 is multiOS/multiplatforms. What problems have been met?
- What is final goal? Better couldn't be goal! Changes of types, db
access and so on couldn't be goal too. It will be nice to read short
document and understand whole picture.

	From another point of view I started to work with Epics couple
years ago. I couldn't understand how Epics work a lot of time. My
opinion - idea of record programming is a little strange. For example,
couple moments:
- It is not full language. I suppose sequence(r) came due that problem.
Am I correct? Another way to solve the problem is C programming on
device level. Ok, we came to C 
- It is enough slow (for example, I changed BLM software (SNS). I
continue to use EPICS for BLM but I added my own small SCADA in the same
IOC (Motorola VME based). After that BLM has 5-10 times better
performance. Actually, records language is like interpretator language.

	So I would like to open another topic. Let's temporary forget
about Epics and discuss SCADA overview. Let's start. 

	There are two SCADA's layers 
- first layer is SCADA objects that talk each other through network. It
is like picture on p. 23 in Epics Application Developer's guide. But it
is much complicated.
- second layer is SCADA's objects itself.

	Accelerator control system must have next SCADA objects
- servers (IOCs in Epics) for accelerator systems, detectors
- "Tools" servers
	- timing server
	- DB server
	- MPS (machine protection) server
	- Alarm server
	- Error server
	- maybe PPS (personal protection) server
	- archive (history, data logger) server
- clients

	Any server type has different behavior type, relationships ... 

	I stop and I hope temporary. Please, any comments? I would like
to have technical discussion. If Epics community doesn't like to
continue this I will not continue too.

Have a good day, Andrei Liyu.


Navigate by Date:
Prev: RE: odd libca message printed Jeff Hill
Next: RE: Asyn driver for FLUKE 8508A Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: EPICS 3.14.7 static client build Jeff Hill
Next: dynamic libraries location Christophe Moins
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·