Maximize the Notepad window to read this file more easily. -------------------------- README: ioDisplay Software -------------------------- ioDisplay Professional (R7.0a) ioDisplay Basic (R6.2a) ------------------------------ December 8, 2005 ioDisplay software is now available in two versions: ioDisplay Basic and ioDisplay Professional. Information in this README file applies to both versions unless otherwise indicated with [BAS] or [PRO]. For information about the differences between Basic and Professional versions of ioProject software applications, see the ioProject Professional 7.0 Release Notes (Opto 22 form 1599). This document is included with all ioProject software and can also be downloaded from the Opto 22 website at www.opto22.com. [PRO] ioDisplay Professional adds several new features: * Support for Ethernet link redundancy using the dual Ethernet network interfaces on SNAP PAC controllers. You can designate primary and secondary control engines; if the primary is not available, ioDisplay Pro will switch to the secondary control engine. For maintenance or testing, you can also manually switch control engines. * Conversion of OptoDisplay projects to ioDisplay projects. * Connection to FactoryFloor controllers running OptoControl strategies. (SNAP-LCM4 with M4SENET-100 adapter card only.) * Ability to read and write I/O unit data through the control engine as well as directly from the I/O unit itself. This ability means you can set up segmented networks using a SNAP PAC controller, with one Ethernet interface used for the control network and one to communicate with hosts. (ioDisplay Basic, in contrast, must talk directly to I/O units.) * Primary and secondary scanners. As with control engines, if the primary is not available, ioDisplay Pro will switch to the secondary. You can also manually switch scanners. * Real-time overview of control engine and I/O unit status. * Access to Scratch Pad bits, integers, floats and strings; pointer variables; PIDs; event/reactions; and limited support for Integer 64 variables. * The ability to replace controllers, item names, table and bit indices for windows, alarm points, historic logs, sounds, triggers, and so on, for the entire project. [BAS] Enhancements ------------------ * ioDisplay Basic is very similar to the previous ioDisplay version 6.1, with the addition of support for new SNAP PAC controllers. Bug Fixes --------- The following issues have been resolved: * Digital input and output points are visible and can now be added to a Historic Data Log. * ioDisplay will not unexpectedly terminate for some Runtime windows containing Windows metafile graphics (.wmf or .emf). * Some bitmaps were focus-frame and beep enabled inadvertently; this problem has been fixed. * RAM used for a SuperTrend is now correctly shown in kilobytes (KB) rather than megabytes (MB). * Negative values in ioDisplay windows are correctly shown. (Previously, some had an extra comma.) * Lo alarms associated with a tag under Setup By Current Value are triggered correctly. * Historic logging works correctly. (The problem occurred when a new control engine was used and the log file name was created from a String Name.) * An erratic good/bad data state associated with a 64-bit integer tag or a 64-bit integer table element has been fixed. ============================================================= ioDisplay Software R6.1a May 31, 2005 Enhancements ------------ * Support for SNAP high-density digital input and output modules: * SNAP-IDC-32 * SNAP-ODC-32-SRC * SNAP-ODC-32-SNK Each of these modules provides 32 digital input (SNAP-IDC-32) or 32 digital output (SNAP-ODC-32-SRC and SNAP-ODC-32-SNK) points, for a total of up to 512 digital points on a 16-module mounting rack. Features differ from those in standard digital modules; for details, see Opto 22 form #1556, the SNAP High-Density Digital Module Data Sheet. * There is a new operator-driven “Read and Clear” dynamic attribute for reading a tag value and then clearing (reset) it. The following values can be read and cleared: * Counts (returns an integer value and then clears counts) * On time total * Off time total * Latch (ON) * Latch (OFF) * On pulse measure * Off pulse measure * Period * In the operator-driven “Send Value” dynamic attribute, values can now be formatted as hexadecimal numbers. * A SuperTrend object’s y-axis can now be scaled logarithmically. * An individual draw window in an ioDisplay project can now be exported, saved as a file, and then imported into another ioDisplay project. The exported window file contains all the objects and tags that were in the original window. Exporting and importing draw windows is a convenient way to reuse the same window in different ioDisplay projects. * Each drawing tool in the toolbox now has a shortcut key associated with it to make selecting and switching between tools easier and faster. To choose a tool, just press the corresponding key on the keyboard. Hold the cursor over a tool to find out which shortcut key is associated with it. * Added “Regenerate IO Scanner Tags” item to Tools menu. * Space and NULL characters are now removed from an Upload Recipe results file. * Vertical and horizontal spacing of objects has been improved. * The “Disk Full” error message is now more specific. This error is now also reported in the Event Log. Bug Fixes --------- * The following problems were addressed in this release of ioDisplay: * ioDisplay Configurator would crash if the user security group(s) and/or user(s) specified in the project were not present on the local domain. * Alarmpoints were not always correctly added to the Runtime scanner. * If an alarm sound was removed from an alarm and “Play until Acknowledged” was selected, the sound removed still played for that alarm. * The “Alarmpoint Controller Status” tag is now sent to the Runtime scanner. * For a PID loop, the IP address and port can now be configured correctly. * Incorrect PID Item Names were being generated occasionally * For a PID loop, the "Out Hi Clamp" and "Out Lo Clamp" values were being sent to "Input Under Range" and "Input Over Range". * The auto/manual flag for a PID loop was not toggleable or settable. * The "opening window" message is now only displayed if Runtime is the active application. * When logging value changes, the operator action log file would incorrectly indicate that the "previous value" was always zero. * In Configurator, the "Save Metafile As" command did not correctly save metafiles to disk. * String writes with space or NULL strings were not working. * SymbolFactory location is now predefined to reduce possible installation problems. * Autocorrect tags now checks for available display resources on the computer. * Historic log triggers were not added to the correct scanner group. * Historic logs did not peform an initial scan when a trigger event occurred. Subsequent scans functioned correctly. * Selecting and moving a large number of metafiles (usually 50 or more) on screen sometimes caused display problems. =============================================================================== ioDisplay Software R6.0a October 1, 2004 Enhancements ------------ * An expanded testing regimen has improved both the reliability and performance of the software over the previous version, ioDisplay 5.1. In particular, ioDisplay Runtime now opens and starts large ioDisplay projects much faster than before. * Recipes now support up to 2048 entries per table. * Numeric table objects now support up to 500 elements per table. * When configuring a SuperTrend, the estimated amount of memory the SuperTrend will use is now shown. * When using an ioDisplay project in Runtime, individual SuperTrend pens can now be either hidden or disabled. Bug Fixes - Configurator ------------------------ * Fixed a problem in the Configure Tag dialog box where, if the backspace key was pressed when the cursor was in the Element field, the Start Index and Number of Elements fields would become active. This would allow table ranges to be entered where they are not allowed. * Corrected an error that occurred where a duplicate control engine ID was sometimes used when a new control engine was added to an ioDisplay project. * Fixed a bug where trigger names sometimes did not appear in dialog boxes. * Fixed a problem in the Configure Dynamic Attributes dialog box where, when using the Tab key to move between the location fields, objects would move around on the screen. * Corrected a problem where AutoCorrect tags did not include cleared tags that were imported from a project created in ioDisplay 1.0. * Fixed a bug where column widths for numeric table controls were not saved correctly. Bug Fixes - Runtime ------------------- * Corrected the following problems in using recipes: - Float tables in a recipe download didn't work. - Recipe downloads and uploads would fail if ioDisplay wasn't monitoring any tags for the control engine specified in the recipe file. - When uploading and downloading recipes, a control engine string couldn't be used for the name of the destination file. - Notifications were not working after uploading or downloading a recipe. - Recipes weren't working if comment lines were embedded throughout the file. In the upload results file, any comment lines were written at the top of the file before the actual data instead of in their correct locations. - An uploaded file could not be subsequently downloaded if brackets [] were used around indices. - A blank line at the end of a file could cause Runtime to freeze. * Fixed the Silence/Unsilence alarm feature to operate correctly. * Corrected a problem where alarm sounds did not work correctly when combined with the Silence/Unsilence alarm feature. * Fixed the Offset feature to operate correctly. * Fixed the alarm point notifications to operate correctly. * Corrected a problem where historic logging did not work correctly when choosing the option From Strategy. * Fixed a bug where historic logs would sometimes display only commas for data, and display data at twice the refresh time or faster. * Fixed a problem when triggering an external application that used an appended string in the command line (for example, "C:/notepad.exe myfile.txt"). * Corrected a problem where a backup controller would sometimes not operate. * Corrected a problem where the Toggle Discrete dynamic attribute would not work correctly when the object also had other dynamic attributes configured. * Fixed a problem where notifications were not working correctly for the Application Manager and Historic Logs. * Fixed a bug where SuperTrend historic logs started with the date 1601. * Fixed a bug where XY plots did not correctly display graphed data. * Corrected a problem with color text in a graphic where, if the text was changed but the Color dynamic attribute for the text was not changed, the new text would display in default Configurator black. Known Issue -- Runtime ---------------------- Some customers set up ioDisplay Runtime to run automatically on a technician’s PC with no other applications available. In some cases, Windows operating services that must run on the PC before ioDisplay Runtime opens may take too long to launch. If this happens, a dialog box will appear stating that a necessary service is unavailable, and ioDisplay will not open. If this situation occurs, you need to add a delay to the ioDisplay launch. Here’s how: 1. Right-click on the ioDisplay Runtime icon in the Startup menu or folder, and choose Properties from the pop-up menu. 2. In the Properties dialog box, add a delay in seconds at the end of the Target field (outside the quotation mark), in the format . For example, to add a 20-second delay, you would type a space and then 20 as shown below: "C:\Program Files\. . .\ioDispR.exe" 20 3. Check how Runtime launches to make sure the delay is the right length, and adjust the delay value if necessary. =============================================================================== ioDisplay Software R5.1d June 23, 2004 ********** IMPORTANT ************ IMPORTANT *********** IMPORTANT *********** ioDisplay R5.1d is distributed as a software patch, not as a standalone installation program. To use this patch, ioDisplay 5.1b must already be installed on your computer. See the instructions below for more information. ********** IMPORTANT ************ IMPORTANT *********** IMPORTANT *********** Installing ioDisplay R5.1d if ioDisplay R5.1b Is Already Installed ------------------------------------------------------------------ Do the following: 1) Exit ioDisplay Configurator and ioDisplay Runtime applications if they are currently running. 2) Download the file ioDisplay_patch_R51d.zip from the Opto 22 Web site at the following link: http://www.opto22.com/support/softwareDrillDown/softwaredrilldown.aspx?Softwar eID=84 3) Uncompress the ZIP archive using WinZip or a similar program. The three .EXE files in this archive will replace three older files (R5.1b) with the same filenames. 4) Now find the ioDisplay directory on your computer. By default, ioDisplay is installed in the following location: c:\Program Files\Opto22\ioProject Software\ioDisplay 5) Drag or copy the three files you uncompressed into the ioDisplay directory. When a prompt asks if you want to replace existing files, click Yes. ioDisplay R5.1d installation is complete. Installing ioDisplay R5.1d if ioDisplay R5.1b Is Not Installed -------------------------------------------------------------- Do the following: 1) Exit ioDisplay Configurator and ioDisplay Runtime applications if they are currently running. 2) Install ioDisplay R5.1b on your computer. If necessary, download the installer from the Opto 22 Web site at the following location: http://www.opto22.com/support/softwareDrillDown/softwaredrilldown.aspx?Softwar eID=4 NOTE: You must purchase and register ioDisplay software if you have not already done so. Once registered, you can request a password from the Opto 22 Product Support group at support@opto22.com. 3) Download the file ioDisplay_patch_R51d.zip from the Opto 22 Web site at the following link: http://www.opto22.com/support/softwareDrillDown/softwaredrilldown.aspx?Softwar eID=84 4) Uncompress the ZIP archive using WinZip or a similar program. The three .EXE files in this archive will replace three older files (R5.1b) with the same filenames. 5) Now find the ioDisplay directory on your computer. By default, ioDisplay is installed in the following location: c:\Program Files\Opto22\ioProject Software\ioDisplay 6) Drag or copy the three files you uncompressed into the ioDisplay directory. When a prompt asks if you want to replace existing files, click Yes. ioDisplay R5.1d installation is complete. Bug Fixes -- Configurator ------------------------- * Corrected a "duplicate control engine ID" error that occurred when a control engine was added to an ioDisplay project. * Corrected a problem where tags that had been cleared weren't included when using AutoCorrect Tags on a project imported from ioDisplay R1.0. * Fixed a bug that caused trigger names to sometimes be displayed incorrectly in dialog boxes. * Corrected a problem in the Tag Configuration dialog box where pressing the Backspace key when the cursor was in an element field would make the Start Index and Number of Elements fields active. This allowed table ranges to be configured, even if the tag being configured was not a table. * Fixed a bug in the Configure Dynamic Attributes dialog box that occurred when using the Tab key to move between controls. Bug Fixes -- Runtime -------------------- * Multiple fixes to recipe handling: - Corrected a problem where recipe float tables were not downloaded correctly to the control engine running the ioControl strategy. - Fixed a bug where recipe downloads and uploads would fail if ioDisplay was not currently monitoring tags for the control engine specified in the recipe file. - Corrected a problem where uploading recipes with didn't work correctly if the option Filename from String Name was selected. - Fixed a problem where notifications didn't work after uploading or downloading a recipe. - Increased the number of table entries that can be used in a recipe to 2048 per table. - Corrected a problem where an uploaded recipe file could not be subsequently downloaded if brackets [ ] were used around table indices. - Fixed a problem where recipe files wouldn't work if comment lines were used throughout the file. * Corrected a problem where historic logging didn't work correctly if the option Filename from String Name was selected. * Fixed a problem where alarm point notifications did not work correctly with Application Manager and Historic Logs. * Corrected an error with toggling discrete tags that occurred when the tag was configured with another dynamic attribute. * Fixed a problem where the Offset feature didn't work on the Send Value dynamic attribute. * Corrected an error where a window state could not be configured by appending a string in a command line. * Fixed a bug where historic logs would sometimes display only commas for data, and sometimes display data at twice the refresh rate or faster. * Corrected a problem so historic SuperTrends no longer start with the "1601" date. * Corrected a problem where alarm sounds didn't work when used in conjunction with the Silence/Unsilence Alarm feature. ====================================================================== ioDisplay Software R5.1c April 27, 2004 ioDisplay software R5.1c was made available briefly as a beta version to a small number of testers, but this version was never formally released. ====================================================================== ioDisplay Software R5.1b February 27, 2004 Enhancements ------------ * In ioDisplay Runtime, multiple "not connected" and similar error messages appear when an ioDisplay project starts. You can now choose whether to have these initial messages displayed. To hide or show these error messages, in ioDisplay Configurator select Configure-->Scanner Location and then select or deselect the "Enable Bad Quality/Not Connected Errors" checkbox. * In the Scanner Location dialog box, the location "This computer" is now selected by default. Bug Fixes --------- * On digital points configured as counters, counters are now displayed correctly. * Correct Windows Help files for this version of ioDisplay are now installed. * Corrected error when a Historic Log is configured to get the filename from the controller. The Historic Log would not be created and a scan error (undefined) would be displayed. * Fixed problems in the View->Control Engines dialog box. Previously it still showed re-enable times. Also, if a control engine was not connected, it still said "Attached" even if no physical control engine existed. * If a control engine was not initially attachable, graphics for that control engine were not correctly displaying the "Detached on Error" color. * A trigger is no longer required to start or stop historic logs. Before, if a historic log was configured with no triggers, nothing would get logged. * Strings can now be written to string tables. * Recipes containing chart commands now work correctly. * Corrected problem when a window had the "Always in memory" box checked in Configurator, and then was closed in Runtime. Previously the data was still being scanned; now the group is disabled on the server so that no scanning takes place until the window is re-opened. * Fixed an error when trying to import an invalid metafile. * Graphic color changes for Last Known Value or Comm Error now occur as the graphic objects are being scanned instead of occurring all at once. * When multiple control engines must be monitored, selecting the Control Engine Status input dynamic attribute now shows the control engine that has the most critical status. A control engine's status, however, can only be monitored if the control engine is already referenced elsewhere in the ioDisplay project, and the referenced item is in an active ioDisplay window. ====================================================================== ioDisplay Software R1.0b February 1, 2002 Enhancements ------------ * The ioDsrX version of Runtime now has the View->Controllers menu option available. Bug fixes: ---------- * Selecting integer and float table ranges when configuring tags is only allowed if configuring an XY Plot or Historic Data Log points. * The option "Play sound continuously" now works correctly when using alarm points that are not inserted into an alarm graphic. * Deadbands for floats now work when configuring "Text In From Controller" Dynamic Attributes. * The "Switch Control Engines" menu option now appears correctly in Runtime. * Sending Discrete values to bits 0 through 31 of Integer64 types now works correctly in Runtime. * Metafiles are now properly pasted after being copied. * Repeatedly sending discrete values no longer locks the controller. ===================================================================== Initial Release ioDisplay Software R1.0a October 15, 2001 Known Issues ------------ * When running ioDisplay Configurator under the Windows 2000 operating system, the font used to format text in a text box may change as you edit or change the text box. This problem does not occur when the ioDisplay project is run in ioDisplay Runtime. ====================================================================== How to Get Help --------------- If you have any questions about this product, contact Opto 22 Product Support Monday through Friday, 7 a.m. to 5 p.m., Pacific Time. Email: support@opto22.com Phone: 800-TEK-OPTO (835-6786) 951-695-3080 Fax: 951-695-3017 Web: support.opto22.com Please provide the following information about your system to the Product Support engineer: - Version of this product - PC configuration (type of processor, speed, memory, operating system) - A complete description of your hardware system, including: - jumper configuration - accessories installed (such as daughter cards) - type of power supply - types of I/O units installed - third-party devices installed (e.g., barcode readers) - Control engine firmware version - Any specific error messages seen