NT support tool (V053-E1-1) (986753), страница 58
Текст из файла (страница 58)
XXXwas an ExtendedScreen which is notsupported by thismodel, so it is converted to a standardscreen.––Correction related to history screensWhen a history screen is converted, an error message may be displayed due todifferences in the handling of the screen numbers of the frequency history screenand the occurrence history screen between conventional and new models. Difference:New models:Screen No. 9001 and No. 9002History screens (occurrence order, frequency order)cannot be edited.Conventional models:Screen No.
1997 and No. 1998History screens (occurrence order, frequency order)can be edited. Conversion result, error message and corrective actionStatus beforeConversionStatus afterConversionError MessageCorrective ActionWith a conventionalmodel, a historyscreen (occurrenceorder, frequency order) is edited.With a new model,the history screen isdeleted (displayingthe edited historyscreen is possibleby specifying it froma PT).The screen no. xxxwas a history occurrence (frequency)screen which is notsupported in thismodel. It is discarded.––477Data ConversionAppendix ACorrection related to the number of memory tablesSince the number of memory tables which can be used differs depending on thePT model, conversion is executed in the manner shown below. DifferenceNT11SNT20SNT600SNT30NT30CNT620SNT620CNT625CNT31NT31CNT631NT631CNumeral memorytable128128512512, or1000512, or1000512,1000, or2000Character stringmemory table(String table)128128256256, or1000256, or1000256,1000, or2000Bit memory table––––––256256256, or1000Extended I/O input table––––––64––––Extended I/Ooutput table––––––64––––F-key input notifytable4–––––––––– Conversion result, error message and corrective actionStatus beforeConversionA memory tablenumber which is outside the allowablerange of memorytables is used fordisplay or input.Status afterConversionThe memory tablenumber is reset to“0”.Error MessageCorrective Action[Object Name] refersto invalid numeraltable entry.
The referenced table entryis reset to entry “0”.Correct the memory tablenumber to the one whichis in the valid range. Ifthe memory table number is specified in a program, correct it also.(Refer to “Dialog BoxSettings in the PT Configuration “ in P52.)Correction related to contents of numeral memory tableWhen the data of a conventional model is converted to the data for a new model,the converted data requires your attention to the fact that the processing that occurs if incorrect data (existence of “A” to “F” other than “F” at the most significant bitposition) is written to an allocated word in the host differs between a conventionaland a new model. DifferenceNew models:The written data is invalid and the existing content is retained.Conventional models:The incorrect data is stored. Conversion result, error message and corrective action478Status beforeConversionStatus afterConversionError MessageCorrective Action––––––Note that the display differs between a conventional and a new model ifincorrect data is written.(Refer to 7-2.)Data ConversionAppendix ACorrection related to bit memory tableIf a bit memory table is converted from the conventional model to the new model,conversion will be executed in the manner shown below due to the difference of thebit memory table function.
DifferenceNew models:Alarm function and switch screen function cannot beset simultaneously.Conventional models:Alarm function and switch screen function can be setsimultaneously. Conversion result, error message and corrective actionStatus beforeConversionStatus afterConversionErrorMessageCorrective Action[Switch screen]: OFF[Screen No]: 0Function: None[Switch screen]: OFF[Screen No]: 0––Change function to [Alarm], ifyou want to display thealarm. (Refer to 7-4.)[Switch screen]: OFF[Screen No]: As desiredFunction: Alarm[Switch screen]: ON[Screen No]: As desired––Correction is not necessary.[Switch screen]: OFF[Screen No]: 0Function: Alarm[Switch screen]: ON[Screen No]: 9999––Correction is not necessary.[Switch screen]: ON[Screen No]: As desiredFunction: Alarm[Switch screen]: ON[Screen No]: As desired––Change the function to[Switch screen].
(Refer to7-4.)Correction related to extended I/O input/output tableWhen an extended I/O input/output table is converted, the data is converted in themanner shown below due to differences in the handling of an extended I/O input/output table between NT30/NT30C and other models. DifferenceNT30/NT30C:Extended I/O input/output table can be used.Other models:Extended I/O input/output table cannot be used. Conversion result, error message and corrective actionStatus beforeConversionStatus afterConversionWith an NT30/NT30C, an extendedI/O input/output tableis set.With a PT modelother than NT30/NT30C, the settingof an extended I/Oinput/output table isdiscarded.Error MessageCorrective Action––Correct the screen dataand a host program sothat unusable tables canbe replaced with inputs/outputs of a host, etc.(Refer to 7-5 and 7-6.)479Data ConversionAppendix ACorrection of image codesWhen 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 imagecodes between them.
DifferenceNew models:0001 to 0FFF (hexadecimal)Conventional models:FE20 to FEFF (hexadecimal) Conversion result, error message and corrective actionStatus beforeConversionStatus afterConversionError MessageConventional modelAssume the code is“X”.New modelThe code is “X –FE1F”.[E]Image Table entryhas been converted.[W]The code for screenelement [ObjectName] has beenconverted fromXXXX to YYY.New modelAssume the code is“Y”.Conventional modelThe code is “Y +FE1F” (if the converted code is outside the usablerange, the code isfixed as “FE20”.)[W]The code for screenelement [ObjectName] has beenconverted fromXXXX to YYY.Corrective ActionIf the code after conversion differs from theimage code to be used,change the code to thecorrect one. (Refer to8-1.)Correction of library codesWhen a library code is converted between a conventional and a new model, conversion is executed in the manner shown below due to differences in the librarycodes between them.
DifferenceNew models:1000 to 3FFF (hexadecimal)Conventional models:FA20 to FAFF, FB20 to FBFF, FC20 to FCFF, FD20 toFDFF (hexadecimal) Conversion result, error message and corrective actionStatus beforeConversion480Status afterConversionError MessageConventional modelAssume the code is“X”.New modelThe code is “X –EA20”.[E]Library Table Entryhas been converted.[W]The code for screenelement [ObjectName] has beenconverted fromXXXX to YYYY.New modelAssume the code is“Y”.Conventional modelThe code is “Y +EA20” (if the converted code is outside the usablerange, the code isfixed as “FA20”.)[W]The code for screenelement [ObjectName] has beenconverted fromXXXX to YYYY.Corrective ActionIf the code after conversion differs from the library code to be used,change the code to thecorrect one.
(Refer to8-2.)Data ConversionAppendix ACorrection related to image/library in (character) stringsWhen an image/library in a (character) string is converted between a conventionaland a new model, conversion is executed in the manner shown below due to differences in handling of the image/library between them. DifferenceNew models:Insertion of an image/library into a (character)string is impossible.Conventional models:Insertion of an image/library into a (character)string is possible.
Conversion result, error message and corrective actionStatus beforeConversionStatus afterConversionWith a conventionalmodel, the image/library is used in a(character) string.With a new model,the code is displayed like this:\<!xxxx>”.(The code after conversion conforms tothe image/librarycode conversionmethod.)Error MessageCorrective Action[E]Image Table entryhas been converted.[E]String Table: TableEntry XXXX has invalid componentcode. It has beenconverted fromXXXX to YYYY.Delete a code in the(character) string andmake corrections so thatthe (character) string andimage/library (fixed display or image lamp) areoverlapped for display orgrouped, allowing theimage/library to be displayed in the same wayas a (character) string.(Refer to 6-1-7.)(In case of lamp/touchswitch label, a fixed display–image goes behindthe label and the displaywill not be as desired.
Inthis case, use an imagelamp instead.)Correction of graphic display attributesWhen a graphic is converted between a conventional and a new model, conversion is executed as shown below due to differences in the display attributes. DifferenceNew models:The inverse attribute is not supported for some kinds ofgraphic.Conventional models:All graphics have inverse attributes. Conversion result, error message and corrective actionStatus beforeConversionStatus afterConversionWith a conventionalmodel, the “inverseattribute” is specifiedfor a graphic forwhich “inverse attribute” is not supportedby a new model.With a new model,the foreground colorand background color are automaticallyinterchanged.Error MessageCorrective Action[Object Name] –inverse attribute notsupported.
Foreground and background colours interchanged.Since the foreground color and background colorare automatically interchanged, no specialcorrection is required(display attribute is set todefault (standard)).481Data ConversionAppendix ACorrection of smoothing processing for marksIf a mark is converted between a conventional and a new model, conversion is executed in the manner shown below due to differences in the handling of marksmoothing processing between them.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
