385
Graphs
Section 7-10
7-10-3
Broken Line Graphs
[Function Outline]
Broken line graphs represent the contents of multiple consecutive numeral
memory tables as one broken line. They enable the values of consecutive numer-
al memory tables to be taken in at a glance.
It is possible to display more than one broken line graph in the same frame so that
they can be compared.
In this example, the values in 11 numeral memory
tables are displayed with the sign indicated.
100%
−
100%
0%
With broken line graphs, a 100% value, 0% value and
−
100% value can be set for
each broken line in order to calculate and display the numeral memory table values
in percentage terms. However, there are no percentage displays for individual nu-
meral memory tables.
[Restrictions]
S
One broken line graph frame can be registered for one screen. (Same for win-
dow screen.) For an overlapping screen comprising 8 child screens, up to 8 bro-
ken line graph frames can be displayed on one screen. Total maximum of 256
broken lines can be registered for one screen regardless of the number of
frames. (Same for window screen.)
There is no restriction on the number of broken line graph frames that can be
registered for one screen data file: any number can be registered as long as the
data file capacity is not exceeded. However, if a large number of elements are
registered, check that the restrictions on element display are complied with by
referring to “Display Restrictions” (page 644).
S
The contents of up to 320 consecutive numeral memory tables can be displayed
in one broken line.
S
Broken line graphs cannot be specified indirectly using a numeral memory table.
They must be specified by direct reference.
Summary of Contents for NT31 Series
Page 1: ...Cat No V043 E1 2 Programmable Terminal NT31 31C OPERATION MANUAL...
Page 2: ...iii NT31 31C Programmable Terminal Operation Manual Produced March 1999...
Page 41: ...30 Before Operating Section 1 5...
Page 75: ...64 Using a Memory Unit NT31 NT31C without V1 Section 3 6...
Page 160: ...149...
Page 174: ...163...
Page 193: ...182...
Page 211: ...200...
Page 235: ...224 c Return to the screen on which screens are specified...
Page 262: ...251...
Page 360: ...349 It is not possible to control a gloval window by touch switch operation...
Page 468: ...457 254 255 0 2 7 1 4 5 3 3 0 0 0 5 9 8 0 3...
Page 476: ...465 Special Functions Section 7 16...
Page 495: ...484 OFF...
Page 610: ...599 Commands Responses Section 9 3...
Page 630: ...619 Examples of Actual Applications of Memory Link Section 10 2...