******************************* GP-Pro EX V2.2 ******************************* July 2008 Digital Electronics Corp. Preface [Fixed defects] 1 Editor 2 Display Unit 3 Device/PLC 4 Project Converter 5 Movie Converter 6 Win GP 7 GP-Viewer EX Contents ================================================================================ [Fixed defects] 1 Editor (Editor) - When you logged in Windows 2000 and Windows XP with the "User" authority, Editor did not start normally. - The picture display size was changed to the specified default one. - Depending on the Meter Graph's size, the starting position of the scale and that of the needle did not match. - In the placement of Text Alarm, an unused window control address was displayed in the Text Alarm dialog when Cross Reference was checked. - When the user-created switch/lamp was rotated, the transparent processing disabled. - Upper and Lower Limit ranges could not be set normally for the data display. - Address information was not shown in the address view during simulation when window parts were set to "Address". - When a project file and a project-converted file that had been created using the old version were opened in GP-Pro EX, the needle of the meter graph was not displayed. - The call target screen did not appear in the window during preview. - In AGP-3200T or ST3000 Series: The display color was different between Preview and GP/Simulation. - Alarm Settings could not be imported in the CSV file format. - When you imported the CSV file of the alarm that was created using GP-Pro/PBIII for Windows, an error was displayed. - In Extended Script, an infinite loop was stopped during the processing. - Tab width in D-Script was changed after inserting line feeds. - In the D-Script Draw function settings dialog box: When "Line Type" was set to other than "Solid Line" and "Dotted Line", the selected line was not drawn appropriately. - D-Script Editor was slow to open when "Thai" was selected in "Standards and format" options on the "Regional and Language Options" tab of the "Regional Options" dialog box in Windows "Control Panel". - When "32 Bit" was specified for "Bit Length" in D-Script, writing "break" in the loop statement caused abnormal operation. - Selecting the "Sign +/-" check box for specific instructions in D-Script resulted in the error. - The drawing area of the call target screen became larger than that of the call source screen. - When "2" or higher was specified in "Line Thickness" for a rectangle and then the data was transferred to GP, the shadow was not displayed. - Parts that can be converted into a text table could not be done so if they were grouped. - After the Message Display position was fixed, the text display position could not be changed to the left alignment. - Certain addresses specified by selecting "Change Specifying Address Conversion" in the "Change Device/PLC" dialog box were not converted normally. - While the "Destination Folder" window was displayed in the CSV File screen, "CF Card" was displayed for File Location. - When "Import" was executed with Table1 to 16 checked in the Import Text Table dialog, it took very long for importing. - In the project file where the operation log settings specified in GP-Pro EX Ver.2.10, the ID of the part specified in Ver.2.01 or earlier was not output. - Changing to the previous/next screen caused the clear area setting of the keypad registration screen to be lost. - When "Copy From Another Project" was used for the project where D-Script was specified (including User Defined Functions), Editor was shut down. - In the workspace of the project where "AST-3501C" was selected for "Model", the color setting was not appropriate. - A user could not check the "ACK Bit Address" setting in the "Mode" tab of the Samples setting. - In the Filing feature: When "32 Bit" was specified for "Bit Length" in the Edit Filing Data screen, the setting area was not displayed normally. - GP-3302B had a feature that could not be set. - When the online editing was performed using the project created with the old version, the displays were different between a GP unit and a monitor. (I/O Driver) - When "Use HeartBeat" was selected for "Select Error Control Protocol", "0" could be set for "Producer heartbeat time". - When "0" was specified for Global SYNC period on the Slave side and the project was re-opened, the specified value was not "0". 2 Display Unit (Runtime) - When an undefined symbol variable was used in Alarm Settings, hang-up occurred. - When a Write error occurred to Device/PLC in WDT (Watchdog Timer) Settings, an error was not displayed for each specified time. - Using the Save Data feature to attempt to save alarm history data might cause the GP to freeze during the transition to the offline mode. - The same active alarm was issued two or more times. - When the [ENT] key was touched in no input status, Reverse Display was not performed. - Closing the window screen by the bit operation using the momentary switch caused the buzzer to keep sounding. - In the momentary switch with OFF Delay, a bit was turned off before the specified delay time. - When you turned ON/OFF the Base Screen (where Plate Color was specified) with the Clearing Action specified, the screen display was not turned OFF normally. - When an undefined symbol was specified for Setting Address in Alarm Settings, "0" was displayed for the address instead of "***". - When "Left Margin" was specified, the ones place digit for "Occurrences" in Alarm History was not displayed normally. - When "Float" was specified for Data Type, round-off was not performed normally. - When "Float" was specified for Data Type and round-off was performed, Alarms were not displayed normally. - When "Use Memory Card As Backup Area" was enabled but a memory card was not used, the Write error to Device/PLC occurred. - When the value exceeding the specified SRAM size was set in Sampling Group Settings, hang-up occurred. - Scrolling made the data redraw processing slow. At this time, communication also became slow temporarily. - "**:**" was displayed for the oldest time on the Time Display settings for a moment. - When "Float" was specified, an alarm was not operated normally. - In Historical Trend Graph and Data Block Display Graph: When a 2-dot auxiliary line was at the end of the display range, it was drawn out of the graph's display area for 1 dot. - The zoom display of Pen Recorder was not displayed normally. - The "Thin Out" display was different between the cases when Log Viewer was enabled and disabled. - Historical Trend Graph was not displayed on Window Screen normally. - Continuous typing of the historical data display switch in the historical trend graph caused the historical data display switch reverse display and the historical display status to be different. - When "32 bit Bin" was specified for Data Type: When the value that the most significant bit could be ON was entered, the graph was not displayed normally. - When the channel number exceeded "40", the dotted image was displayed which should have not. - Data Block Display Graph was not displayed on Window Screen. - Dots of Data Block Display Graph were not drawn on Window Screen. - When a Bar Graph was specified under the following conditions, "0" was displayed, although the maximum value should have been displayed: Data Length: 32 Bit, Input Range: No sign, Display Range: +/- - When Symbol was specified for Display Color in the Color settings, a pattern and a pattern color referenced the same address. - The plate color of the blank rows in the special data display (Data Transfer) became uneven. - When the screen including Filing Display or CSV Data Transfer Display was displayed using Call Screen, the display position was shifted from the correct position. - When Logic Monitor (or Ladder Monitor) was running with BCD specified for Screen Number, an inappropriate value was written in Change-To Screen. - When Touch Input was conducted in LT3000 Series and GP3000 Series (except for GP-3200 Series), a communication error with PLC occurred. WhenScreen Change was executed in this error status, the touch input after the Screen Change became disabled. - When Screen Change or Window Display was executed, a lamp display blinked for a moment. - When Screen Change was executed in GP-3300 seriesiBefore Rev.*-4j and LT3000 series, the contrast control value became the maximum one. - When CF Memory Loader was started, the message "Checking Hardware" was displayed twice. - A project where CANopen was specified in LT series could not be downloaded using Memory Loader. - Memory Loader was not started in the initial transfer mode. - When Comparison was executed under the status that models were different on the display unit and the backup data, the message saying that CF card and USB storage data had an error was displayed. - Hang-up occurred after the initial screen was displayed when the following steps were taken: (1) SRAM was used for both Operation Log and Alarm History. (2) Operation Log used up the SRAM free space. (3) Alarm History transferred the project that could not secure the SRAM to GP. - When the indirect address was specified in Data Display, the address to be output to the Operation Log was inappropriate. - Invalid symbol variables were output for Address. - Contrast could not be adjusted normally in AGP-3200A. - Transparency was disabled for image data in AGP-3200A. - When the chamfer rectangle size was 1 dot in AGP-3200T/A, it could not be displayed normally. - When an image data came rightward out of the display range for odd number dots in AGP-3200A, 1-dot vertical line was displayed. - Under the condition that Clearing Action was specified in Picture Display: When a part of the stroke font display came leftward out of the screen, drawing was not displayed normally. - When the chamfer rectangle came upward out of the display range for some dots for chamfering, drawing was not made normally. - When 3 or more coordinates points were on the same horizontal or vertical line in Polyline drawing: Drawing was made in the solid line even when any line type was specified. - When a Pie was placed beyond the upper limit of the screen, the line on the circle was drawn exceeding the start and end points. - When a black was specified for the pattern color of parts/fixed drawing in large-sized GP models, the vertical line was partly displayed. - Cyrillic could not be partly displayed in ST3000 series and GP3200 series. - No search item was found when using SET instruction and RST instruction. - When a printer type was "NEC PR201", stroke fonts could not be printed normally. - In JPEG Capture, the size of the file captured after start-up was different from that captured after a single JPEG display. - When Touch Panel Detection setting was OFF and the mode was restored from standby, untouched switches were operated. - Although the appropriate values were entered for number of address and parts in "Screen Information" of Editor, an error saying that the maximum limit was exceeded was displayed in transfer. - The input limit for the port number of Web Server was different from that for Editor. (It has been changed to "1 to 65535" to be the same as the one for Editor.) - The setting ranges for "Brightness", which were on the "Video Display" screen or the "Recording" screen, were different from those on Editor. - When Memory Loader was started without transferring the Japanese font in GP-3200 Series, no text was displayed. - When the mode in GP-3200 Series changed online from offline, the screen blinked. - When the mode went into the offline and returned to the online without saving the data, memory leak occurred. - Unnecessary code characters for display were displayed in the font check "PF NumericFull S". - When you were back to "Display Unit" from "Remote Viewer" using [Back] button, the top menu buttons were displayed inappropriately. - In the offline screen, initialization was conducted by selecting "Initialization Menu" and then "Initialize User Memory". When the progress status bar in the initializing dialog reached approximately 90%, the screen display became abnormal. - When Simulation was executed for a project (256-color mode) in GP-3200 Series and "Indirect" was specified for the color in Data Display, the color was in Monochrome 16 Levels. - When an undefined symbol variable was used in Historical Trend Graph, hang-up occurred. - When the RPA window display was turned ON immediately after it was OFF, the subsequent RPA connection became disable. - Placing a visible animation in a data display that had been set to an indirect address caused the plate color to appear in an incorrect color immediately after the screen change. - When two or more types of parts among Data Display, Sampling Display and CSV Display were combined and placed in the same screen, the later-placed display data was not displayed normally. - Editing the text in Text Display caused the display unit to freeze. - Changing screens during the data edit in Sampling Data Display caused the display unit to freeze. (I/O Driver) - When a communication cable was disconnected and then re-connected, all parameters were restored to all slaves. This specification was improved by adding a new setting "Restore behavior". 3 Device/PLC - GP could not be connected with MITSUBISHI's A2CCPU via CPU Direct Connection. - When "9600" was specified for the baud rate during the connection with MITSUBISHI's A series in the pass-through function, the time-outerror occurred. - Installation of virtual COM in the pass-through function might fail. - If Display Unit changes to off-line mode after pulling off the USB cable for pass-through, you might not be able to set it back to on-line mode even after connecting the cable again. - When pass-through function was enabled, DDE might not work with Pro-Server EX. - When you tried to add a new COM port, shutdown occurred. - "*" was not displayed when the device monitor read an out-of-range data. - In the connection with RS422, an error occurred on start-up or communication was disabled when Flow Control was not specified. - In the connection with ST Series, the communication error "Response timed out for device write command" was displayed on start-up. - When the not-officially supported PLC (TSX4740) is connected, the response error for the communication start request occurred, which enabled communication. - The address range check was performed inappropriately in Multi CPU and the address out-of-range error was displayed. - There was a case where a bit device failed to write properly. - When you renamed a variable name that had been registered in the Symbol Editor, it was displayed as "-undefine-". - When two or more tags were declared in Rockwell EtherNet/IP, an application error occurred. - Revised the list of device addresses in SDC45/46 series. - TimerFile's bit device values might not be displayed properly in the device monitor of Pro-Sever EX. - Communication error occasionally occurred when VIPA's MPI-supported PLC (not supported officially) was connected. - Communication error occasionally occurred when Wago (not supported officially) was connected. - When the write command was sent to GP in the extended binary mode of Memory Link SIO, the ACK response to the command was not made. - Window control bit of the Memory Link might not be turned OFF by Bit Reset switch in the window. - When using General Ethernet protocol, commands might fail to be sent. - Settings dialog of General Ethernet could not be displayed normally in 120dpi. - The window control bit was not turned to OFF with the bit reset switch in the window. - When you renamed a variable name that had been registered in the Symbol Variable Settings, it was displayed as "-undefine-". - The text with one-byte and two-byte characters mixed could not be written normally. - When you renamed a variable name that had been registered in the Symbol Variable Settings, it was displayed as "-undefine-". - The text with one-byte and two-byte characters mixed could not be written normally. - A communication error ("No response") occurred during the Ethernet communication using Revision A CPU. - The COM error occurred to the Ethernet unit. - The communication with PLC was slow compared with GP2000 series. - Ladder software (STEP7 V5.3 or later in Japanese mode) occasionally could not read "Field bus" data for PROFIBUS provided by Digital Electronics Corp. - Communication error occasionally occurred when WinLC (not supported officially) was connected. - The window control bit was not turned to OFF with the bit reset switch in the window. - When frequent writing (e.g. Large quantities of data were written to the internal device in the constantly-operating D-script) occurred to devices under the condition that the above-mentioned model/ communication driver was used with GP-3200/ST3000 Series, the system error was displayed on GP and the display unit could stop on rare occasions. - When KV-700/1000 series was selected, the address input ranges for Output Relay/Input Relay/Internal Relay were limited to 00000 to 09915. - When KV-700/1000 series was selected, the address input ranges for Output Relay/Input Relay/Internal Relay were limited to 00000 to 09915. 4 Project Converter - In GP-Pro/PBIII for Windows: When the screen where switches had been placed was converted and transferred to the main unit, some colors for them disappeared. - In GP-Pro/PBIII for Windows: When the screen where the R tag/J tag had been placed was converted, the parts disappeared. - In GP-Pro/PBIII for Windows: When the screen where more than the specified size of the image files had been compressed was converted and transferred to the main unit, it did not operate normally. - When the project file where null text had been imported was converted in GP-Pro/PBIII for Windows, shutdown occurred. - When "Align Center" was specified for the text on the parts label specified in GP-Pro/PBIII for Windows, the normal conversion could not made. - In converting the LT TypeA/TypeB/B+ project: Although the I/O variable types (Word/Bit) were different between the input and the output, the conversion was made to the same variable type for them. - In GP-Pro/PBIII for Windows: When a project including a blank text screen with a multi language was converted and then opened using Editor, GP-Pro EX shut down. - When "GP2501S" was specified for "Display" and a project was converted, an inappropriate color setting was enabled. 5 Movie Converter - When converting format from SDX to another, an exceptional error might occur depending on the settings. - A movie file which could be converted could not be recognized as a movie file under certain circumstances. - An existing file was deleted unexpectedly when you stopped converting after having started it under the overwrite setting. - If you entered an out-of-range value in the image settings under the default settings, the value might not be able to be modified and might remain abnormal. - If you changed the image type in the image settings under the default settings, the frame rate and the bit rate were set to be blank. - Start/End of conversion might not be recorded in the Log. 6 Win GP - Even when the active window was changed using keys such as [Alt]+Tab keys with the momentary switch held down in WinGP, the switch remained held down. - On WinGP (Simulation), the maximum value in the Input Range of Float Data Display with Input could not be entered normally. - When WinGP started on Windows Vista and shifted into the offline mode, "Windows Longhorn" was displayed for the OS version.