InSite Release 5.

01 Readme
Installation Issues Microsoft .NET Framework version 2.0 or higher MUST be installed for InSite to operate properly. If this is not installed correctly, InSite will display various exception handling errors and fail to run. InSite should attempt to see if it is installed during the installation process. If .NET Frameworks is installed, it should appear in the list of software shown in the Settings, Control Panel, Add or Remove Programs list (as Microsoft .NET Framework 2.0). The .NET Frameworks install is included on the CD as a separate install if you wish to run it separately (dotnetfx.exe). If a previous 5.xx version (field test) of InSite has been installed, the old release version must first be removed before installing the new version. This can be done automatically by using the InSite.exe that was used to install the software or manually by using the Control Panel to Add or Remove Programs. BOTH InSite release version 3 and InSite release version 5 can be installed but cannot be run at the same time. 5.01 Changes 1. The IND131/331 Save/Load operation was fixed so that it now works in all cases (version 5.00 had an issue where it would fail for unauthenticated users.) 5.00 Changes 2. The InSite Configuration Tool was redesigned as a modular application. Each product supported has its own separate install components, making updates and additions easier to manage. 3. Updates to the IND780 and IND560 products were made to bring each up to the latest released firmware version. 4. IND131/331 and IND560x products were added. 5. DSM (user) authentication was added to protect the tool from unauthorized use. 6. Save / Load operation was added and can be used even if InSite has not yet been authenticated. Product Configuration Notes It is important to remember the following special considerations: 1. InSite does not read ALL data from connected terminals as part of the connection operation. It reads information pertinent to the information currently being displayed. If all information is required (example, for a save/load file), a READ ALL operation must be performed. Even then some data is still protected from this operation - user and FTP passwords can never be read from the terminals. 2. If usernames and passwords are required as part of the backup file, these parameters may be edited offline and stored as part of the saved file. During a write operation, these edited parameters will be sent to the terminal. If these parameters need to be changed on a connected terminal, the user and FTP table pages can be used to modify the existing information. While InSite cannot read this data, it can overwrite it. ( InSite stores a copy of the default settings for the User & FTP tables as part of its saved files. When restoring a

saved file to the terminal, it will ask if the user wishes to overwrite the existing data with this information. If a special configuration of User & FTP tables is required, the saved file must be edited to include this information. ) 3. Tables and other similar configuration items (like discrete inputs or discrete outputs) do not write in the connected mode until the page view is switched to another configuration screen. This allows InSite to write all the changes to a particular table or shared data array at one time. For example, changes made to a discrete output table are not sent to the terminal until you switch to another page (like selecting the Terminal tab). Some pages with single parameters do not write until you switch to another page. 4. Log files are not saved as part of the configuration since they cannot be written back to the terminals. InSite allows them to be viewed when connected, but this data is not kept when the data is saved to the PC. 5. It is highly recommended that the terminal be power cycled after writing configuration data or loading an entire configuration. While InSite makes every attempt to issue the appropriate triggers to force the terminal to begin using new configuration data, there may be some cases where it is not applied immediately. Cycling power will insure that all configuration and operational data will be initialized and synchronized appropriately.

Product & Revision Specific Notes Notes There are no new reported product specific issues.

3.04 Notes [IND560 version 1.03] 1. InSite shows blank (reserved) records for empty connection slots in the communication configuration. 2. The % symbol is now recognized and double entry is not required. 3. Disabled second or third units are now correctly recognized by the terminal.

[IND560 version 1.02]

1. If the FTP Clear All operation is performed, it will remove all users (even the default). 2. If the Weight display size does not reset to the Big Weight display after changing the configuration of SmartTrac from InSite, this can be corrected from the IND560 terminal by re-establishing the configuration of SmartTrac (Terminal, Display, SmartTrac size = none ... if this is not present, first turn target mode to material transfer mode. After resetting the SmartTrac size, you can turn this mode back to none.) 3. When disabling the configuration of either a second or third unit, the terminal must be currently displaying the primary unit. If it is done in the incorrect unit, the terminal may display an incorrect symbol in the weight unit field (a range symbol may appear instead). This can be corrected from the IND560 terminal by re-establishing the primary unit (Enter

the same primary unit as configured in the Scale, Capacity & Increment parameter again from the terminal). 4. If a % symbol is used in a string in a template, the IND560 will not recognize this character unless it is entered twice. This is true for each required character, so if you wish to have two percent characters in a string you must enter %%%% as your string.