Experimental Physics and Industrial Control System
|
Note that ControlLogix communications (multicast with tcp messaging)
includes a fairly severe penalty for using the
tag names. There are a limited number of cip resources (255 is common).
Each module consumes several and each IOC access
by tag name consumes one. As a result, we always use arrays and end up
in the same old boat of having to do lots of name
mapping to array position. In principle the tag names are very nice; in
practice they are not too useful.
John Sinclair
David Dudley wrote:
For NSLS-2, all configuration and logic is planned to be incorporated
into the IRMIS system, as a single database layout.
In addition, I should have initially mentioned that one of the primary
reasons for the A-B choice is that it uses a communications format
named ‘CIP’, and its internal memory configuration is entirely driven
by TAGNames.
In tne ControlLogix platform, you do not do programming or
configuration by having to remember or know things like “...
‘B-703:R-E5<OTB>T-1’ is wired to terminal IW102... (That’s Building
703, Room E5, Optical Testing Lab, Temperature 1)” .
- Replies:
- Re: Remote I/O David Dudley
- References:
- Re: Remote I/O David Dudley
- Navigate by Date:
- Prev:
RE: New home for asyn Mark Rivers
- Next:
mbboDirect problem Dirk Zimoch
- 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:
Re: Remote I/O David Dudley
- Next:
Re: Remote I/O David Dudley
- 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
|
ANJ, 31 Jan 2014 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|