Table of Contents
Advertisement
S5-95F
Steps 1 through 7 present the minimal requirements for setting the parameters
are additional rules that make it easier for you to assign parameters.
For example:
•
You have the ability to add comments.
•
You can expand the mnemonics used as parameter names by using plain text.
Comments can be added anywhere a filler is allowed
The comment symbol must be placed at the beginning and at the end of your comment
between two comment symbols may not contain an additional #.
Example: #Comment#
At least one filler must follow the # sign.
In order to make it easier to read parameter names, you can add as many characters as you wish if
you add an underscore (_) after the abbreviated parameter name.
Example:
SF becomes SF_SENDMAILBOX .
At the end of the input, you must add at least one filler.
There is a rule of thumb that will help you check DB1. You should include at least one filler in the
following instances.
•
After the start ID
•
Before and after the block ID, parameter name, argument, and semicolon
9.3.4
How to Recognize and Correct Parameter Errors
Should an error occur while assigning parameters and the programmable controller does not go to
the "RUN" mode, you have two possibilities for recognizing errors.
•
By using the COM 95F software (see COM 95F manual)
•
By direct interpretation of the entry in the system event DB (see section 15.3.9).
EWA 4NEB 812 6210-02
.
Blocks and Their Functions
.
The comment symbol is the pound (#) sign.
.
Beyond that, there
.
The text
9-29
Advertisement
Table of Contents
