Filter
Top Products
7... HYPERNET™ ICON BASED PROGRAMMING
USING THE OMP-MODL 7-5
Program Net Icon Selection Bar
Included in the Program Net Icon Bar is a collection of various icons
to be used in the development of Program Nets. Clicking on the
arrows at the left and right edge of the bar will scroll the bar left or
right displaying additional icons.
PROGRAM NET CONSTRUCTION
Program Nets are developed in HyperNet and saved as files with the filename
extension *.NET.
Program Nets must be developed to match the existing hardware installed in the
target OMP-MODL. For example a Program Net that uses a MLIM-2 Frequency
Input Channel will only work in a OMP-MODL that has a MLIM-2 installed.
Configuration details that must match include:
♦ Interface Modules - Program Nets must match the OMP-MODL
installed Interface Module types.
♦ Port - The Port (I/O Module location) used in the Program Net
and the Port used for an Interface Module in the OMP-MODL
must match.
♦ Channel Configurations - Interface Modules equipped with
hardware configuration switches must have their switches set to
match the Program Net on a channel by channel basis.
For Example: If an MLIM-1 is installed in Port 3 and has
the Channel B configured (via the Channel B hardware
configuration switch) for VDC-HI, then any Program Net
loaded into the OMP-MODL must have Channel 3B used
as a VDC-HI channel (or optionally, not used).
If a Program Net that does not match the target OMP-MODL hardware
configuration is uploaded to the OMP-MODL memory, a configuration
mismatch error will display and the upload will not occur. This checking of
compatibility is handled automatically within HyperWare during the upload
process and insures that hardware and software compatibility exists.
Figure 7... -9: Icon assortment (with scroll arrows at each end)