|
Unique architecture
provides speed, ease of use, and room for growth. The
cornerstone of the Vsystem architecture is Vaccess, a user-extendable, real-time
database and library of access routines. Vaccess is similar in structure to an
electronic crate--like a VME crate--into which you can plug a variety of
modules. While individual modules interact with Vaccess, they are independent of
each other. Vaccess holds and transmits data and functions as an event-driven
bus, providing notification of change upon request.
Vaccess maintains a responsive, secure, memory-resident
data description of your facility. From ASCII text files, Vsystem generates a
real-time database customized for your facility. You can divide the database
into many databases distributed among the computers of the system. Security can
be controlled per database or per channel. In a distributed, networked
environment, although a database resides on only one computer, all other
computers in the network have access to that single copy. Optionally, events
generated from that database update remote applications with significant changes,
ensuring efficient use of computing resources.
And you can construct systems from small, easily
defined, tested modules. In essence, Vsystem breaks complexity down into
manageable pieces.
Benefits of this unique architecture:
-
Speed, manageability, security, and scalability
-
High performance and memory resident
-
Channel types: binary, integer (8-, 16-, and 32-bit;
signed/unsigned), single-precision floating-point, double-precision
floating-point, string (232 characters), and time (resolution 1
ns)
-
All channels can be time stamped
-
Numeric channels can be arrays up to 232
bytes
-
Array channels can be circular buffers; each value
can optionally be time stamped
-
Each database can have up to
65,535 channels
-
Up to 65,535 databases in a system,
with any number on each computer
-
Alarming with delayed alarms and
with reference alarms
-
Full API
-
Event-driven change notification on all fields
-
Dynamic memory management
-
User-written conversion routines with parameters
-
Conversion routines can do gets
and puts
-
Multiple conversion routines per
channel
-
User-written I/O routines
-
Most fields are dynamically changeable
-
Channels can be added dynamically to a running
system
-
All releases intercommunicate -
no need
to upgrade your old system when a new system is added
-
256 alarm priorities
-
Database, channel, and field security
-
Database checkpoint manager to
ensure that disk copy is current in case of failure
-
Area and subarea fields
supported for larger applications
Updated
Mar 31, 2006 |