Forcing initialization, Forcing initialization -132, 4 forcing initialization – Delta RMC101 User Manual
Page 182
RMC100 and RMCWin User Manual
3-132
1. On the main window's Tools menu, click Options.
2. Click the Preferences tab.
3. Select the preferences you want to use.
4. Click OK.
The Preferences tab includes the following options:
• Do not show confirmation warnings check box
Select this check box to suppress confirmation-warning messages. This includes all warnings
when closing a window to save the contents to either the RMC or the disk. Select this check box
only if you know the program very well and understand when your work is saved.
• Look-only check box
In Look-only mode, the user cannot make changes to the module. This prevents the user from
changing any parameters or issuing any commands. It is still possible to view all data. Notice that
this setting is saved so it will be remembered the next time RMCWin is started.
• Limit Instances to One per Board File check box
Clear this option if you want to open multiple RMCWin copies at once but do not care which board
file is used. For example, if you wish to share between two event step tables, you can clear this
option, start a second RMCWin, open an Event Step table editor under each, and copy and paste
between them.
Set this option in all other situations. The primary reason for this is that it prevents accidentally
starting multiple RMCWin copies, for example, by clicking the RMCWin icon too many times.
A more important reason to set this option is that several PC-based human-machine-interface
(HMI) software packages allow starting RMCWin from a button, but if the focus is switched back to
the full-screen HMI there is no way to retrieve the copy of RMCWin hidden behind the HMI.
Clicking the button with this option cleared starts a new copy of RMCWin, but if the serial port is
being used, then the new copy would be useless since the first, hidden copy would retain control of
the serial port. With this option set, clicking on the button on the HMI will trigger the original
RMCWin instance to be brought to the foreground instead of starting a second instance.
Some systems require access to two or more RMCs and provide a separate button for each on the
HMI. Each button starts RMCWin with a different board file and a different communication path.
Therefore, with this option set, it is possible to have each of these various board files and
communication paths open under different copies of RMCWin, but you are still protected from
starting multiple copies with the same board file and communication path.
• Ignore Configuration Conflicts check box
When this box is checked, RMCWin’s configuration-conflict detection feature is disabled. For
details on this feature, see Configuration Conflict Detection.
3.11.4 Forcing Initialization
It is possible to have RMCwin automatically send the parameters it has stored in a file to the