Appendix A
Data Conversion
472
Conversion result, error message and corrective action
Status before
Conversion
Status after
Conversion
Error Message
Corrective Action
With an NT30/
NT30C, an ex-
tended I/O input/
output table is set.
With a PT model
other than NT30/
NT30C, the setting
of an extended I/O
input/output table is
discarded.
––
Correct the screen data
and a host program so
that unusable table
entries can be replaced
with inputs/outputs of a
host, etc. (Refer to 7-5
Extended I/O Input
Table and 7-6 Extended
I/O Output Table.)
Correction of image codes
When an image code is converted between a conventional and a new model,
conversion is executed in the manner shown below due to differences in the
image codes between them.
Difference
New models:
0001 to 0FFF (hexadecimal)
Conventional models:
FE20 to FEFF (hexadecimal)
Conversion result, error message and corrective action
Status before
Conversion
Status after
Conversion
Error Message
Corrective Action
Conventional model
Assume the code is
X.
New model
The code is X –
FE1F.
[E]
Image Table entry
has been con-
verted.
[W]
The code for screen
element [Object
Name] has been
converted from
XXXX to YYY.
If the code after conver-
sion differs from the
image code to be used,
change the code to the
correct one. (Refer to
8-1 Image Editor.)
New model
Assume the code is
Y.
Conventional model
The code is Y +
FE1F (if the con-
verted code is out-
side the usable
range, the code is
fixed as FE20.)
[W]
The code for screen
element [Object
Name] has been
converted from
XXXX to YYY.
Correction of library codes
When a library code is converted between a conventional and a new model, con-
version is executed in the manner shown below due to differences in the library
codes between them.
Difference
New models:
1000 to 3FFF (hexadecimal)
Conventional models:
FA20 to FAFF, FB20 to FBFF, FC20 to FCFF, FD20 to
FDFF (hexadecimal)
Conversion result, error message and corrective action
