***************************  GP-Viewer EX V1.60.000  ***************************
                                                                        Oct 2009
                                                       Digital Electronics Corp.

Contents
================================================================================
   [Fixed defects]
     Problems resolved in V1.60.000:
          1. Some defects of GP-Pro EX V2.60.000's Runtime were fixed.
          2. Runtime of GP-Pro EX V2.60.000 is supported.
          3. When GP-Viewer EX connects or re-connects to Display Unit,
             GP-Viewer EX sometimes displays different Alarms from those displayed
             on Display Unit.
             In this case, select "Screen Update" from the menu of GP-Viewer EX.

     Problems resolved in V1.51.000:
          1. Some defects of GP-Pro EX V2.51.000's Runtime were fixed.

     Problems resolved in V1.50.000:
          1. Some defects of GP-Pro EX V2.50.000's Runtime were fixed.

     Problems resolved in V1.11.100:
          1. Some defects of GP-Pro EX V2.21.000's Runtime were fixed.

     Problems resolved in V1.11.000:
          1. Runtime of GP-Pro EX V2.21.000 is supported.

     Problems resolved in V1.10.100:
          1. If you have installed GP-Viewer EX V1.10 before uninstalling
             GP-Viewer EX V1.00, uninstall GP-Viewer EX V1.10 and then install
             it once again.
          2. In "Operation Lock":
             - When a low value is specified for "Timeout" in Operation Lock and
               a heavy load is constantly applied to the CPU, the continuous
               high-speed operation may cause an error in GP-Viewer EX, which
               does not allow you to operate the connected master and the slave.
               In this case, exit the GP-Viewer EX where the error has occurred
               for restoration.

     Problems resolved in V1.10.000:
          1. Forced screen change is not supported. 
             Even if forced screen change is enabled, changing screens by touch
             from the Viewer is available. 
          2. At high communication speeds, changing multiple bits ON and OFF may
             not be recognized by the Viewer.
             The Viewer also may not recognize screen changes at high
             communication speeds.
             As a result the Viewer may display different data from the server
             or reproduces a sound but it recovers on a screen change.
          3. When communication error occurred in a PLC, the Viewer stopped
             displaying the values of the other PLCs that were operating
             normally.
          4. In the "Update Data in Storage" dialog, specifying "All Folder" in
             "Image Data" does not enable the Viewer to load all the image files
             in Storage.
             For all the image files in Storage to be loaded, you should leave
             the "Folder (includes subfolders)" blank and press OK button.
          5. When "Update Data in Storage" is executed, the display of security
             level looks as if it has been changed (actually the security level
             isn't changed).
          6. The same message scrolls twice continuously by the banner alarm
             function.

     Problems resolved in V1.00.200:
          1. When a device/PLC was assigned to "System Area Start Address", it
             was unable to write to part of the PLC device.
          2. While the Viewer is acquiring the SRAM data, the display unit
             changes to off-line mode and recovers to on-line mode without
             modifying setting.
             After that, the Viewer can not acquire the SRAM data.

     Problems resolved in V1.00.100:
          1. In the Sampling Settings, Mode tab, if you use the Data Full Bit 
             Address or the Block Completed Bit Address, each bit turns on twice
             in a row as the condition is satisfied.
          2. Even if screen synchronization is set up, when you use Group with
             Auto OFF in the Bit Switch group function, upon exiting
             GP-Viewer EX the Auto Off operation is run.
          3. When the CPU utilization 100% status is sustained, the application

             may become the no-response condition or an application error may
             occur.
          4. When a data read/write is made at high speeds by the operations
             below, the CPU utilization goes up and the problem of the item 3
             occurs.
             - In Word Switch, select "Add Data", "Subtract Data" etc. and check
               "Continuous Add Feature".
               When you keep clicking the switch on the screen, the CPU
               utilization goes up.
             - With "Read Data From Each Alarm" enabled, change the triggered
               devices at the same time to read a large number of devices at a
               time.

================================================================================

Warning: No part of this document may be used or reproduced without permission.
******************************End of Release Note*******************************