========================================================== GRAVIMETRIC GATEWAY RELEASE NOTES - MAGUIRE PRODUCTS, INC. ========================================================== What's in this document: Section 1 - What's New in Version 4.0.11 Section 2 - Getting Started Check List (Licensed Mode) Section 3 - How to use DEMO Mode (Previewing G2) Section 4 - Upgrading Your Version of G2 Section 5 - Version Release History Section 6 - Version Release History of Changes/Fixes ========================================= Section 1 - What's New in Version 4.0.11 ========================================= CURRENT OFFICIAL UPGRADE VERSION: 4.0.11 Released January 2, 2008 1. Changes to Yield Control including formula updates, LIW controller support updates and improvements to Yield Control Screen. 2. Bug fixes to G2 Demo Mode. 3. Misc other minor bug fixes. ======================================== Section 2 - Getting Started Check List ======================================== The Gravimetric Gateway Software has two main components. They are: The G2 Server - The G2 Server program should be running at all times. The G2 Server will monitor the Maguire Weigh Scale Blenders and collect totals at pre-determined intervals and tag changes. If the G2 Server is not running, totals are not collected from the blenders until the G2 Server is started again and is able to connect to the Blenders. All user functions are done from the G2 Client. The G2 Client connects to the G2 Server. More information on the G2 Server can be found in the Gravimetric Gateway Manual. The G2 Client - The G2 Client is the component of the G2 software that operators use to interact with the G2 software. The G2 Client is used to enter and download data, monitor information and generate reports. The G2 Client is not required to be running at all time in order to collect data from the Blenders. More information on the G2 Client can be found in the Gravimetric Gateway Manual. The following steps of this "Getting Started Check List" will briefly touch on the basics of quickly getting the G2 software running and communicating with your Maguire Weigh Scale Blenders. More information can be found in the Gravimetric Gateway Manual and should be reviewed for a further explaination of each step in the startup process as well as the monitoring and reporting process. Copies of the Gravimetric Gateway Manual can be downloaded from www.Maguire.com/g2 1. After installing the G2 Program, verify that the G2-SA is connected to a COM port on the computer. This COM port is the COM port you will use to connect to the Maguire Weigh Scale Blenders with. 2. Start the G2 Server from the Gravimetric Gateway Program Group in the Start Menu. Click Mode in the menu of the Server. Select Licensed then click Start G2 Server. While the Server is starting up, look for your 6 digit G2-SA serial number in the Server (Serial#:xxxxxx). If Serial number is displayed as Serial#:0, you are not communicating with the G2-SA and will not start in Licensed Mode. Verify that you are selecting the correct COM port and the G2-SA is powered on. 3. When the G2 Server has connected to your G2-SA and you can see the serial number if your G2-SA, you can start a G2 Client. The G2 Client will automatically connect to the G2 Server if they are running on the same PC. For networking G2, refer to the Gravimetric Gateway Manual. 4. Enter your Blender I.D. numbers into the Blender Edit Screen. If you do not know your blender I.D. numbers or have not assigned blender I.D. numbers to your blenders, refer to the Gravimetric Gateway Manual for information on how to enter or access the blender I.D. numbers. After entering an I.D. number, click Add/Update to add the I.D. number to the blender database. Select the I.D. from the Blender List to verify that the Blender is "On Line". If it is not On Line, verify your I.D. number and check the communication wiring. See the Gravimetric Gateway Manual for further troubleshooting. 5. Enter your materials into the material edit screen. All materials that will be downloaded to the blenders must be entered in G2's materials database. Recipes will be built from these materials. 6. Build your 4 or 12 software recipes in the Blender Recipe Edit screen. Recipes are built from the materials that you have previously entered. 7. Enter your Retrieval Times into the Retrieval Times screen. Retrieval Times are preset times that the G2 Server will log totals for reporting purposes. Typical retrieval times are hourly or at the end of each shift. 8. Download recipes to the blenders. In order for the G2 Server to be able to track material usage, the G2 Server must know the recipes that the blender is currently running. This is accomplished by downloading a recipe to a blender. In the G2 Client menu under download, select "Recipe to Blender". Select the Blender to receive download the from the dropdown menu. Enter an optional Operator # and Work Order #, then click Select Recipes. Your list of recipes will be displayed. Select the recipe you wish to download. Click "Send to Blender" to downlaod this recipe to the selected blender. After following these steps, the G2 Server is now collecting totals from the blender(s). You may now monitor the blender activity with several screens and generate material usage reports as usage totals become available. For further information on the G2 Server or G2 Server Client and the usage of the screens within the software, refer to the Gravimetric Gateway Manual. If you do not have a copy of the Gravimetric Gateway Manual or would like to download a more recent copy of the manual, please visit our web site at: www.Maguire.com/g2 ============================================================== Section 3 - How to use DEMO Mode (version 3.1 and later only) ============================================================== G2’s DEMO mode allows the user to preview actual operation of the G2 Server and the G2 Clients. G2 running in Demo Mode does not require actual blenders to communicate with. In DEMO Mode G2 communicates with simulated blenders to demonstrate the actual operation of G2. This allows a full simulation of an actual setup using multiple blenders in any mode or configuration. How to run in DEMO Mode To start using G2 in DEMO Mode, follow these steps: 1. Start up one or more G2 Simulated Blenders - Click the Simulated Blender icon in the Gravimetric Gateway program group of your start menu. For each simulated blender choose a new Id number. Click Start to power up the simulated Blender. Blenders 1 thru 10 are pre-configured blenders that are set to simulate specific models. They are as follows: WSB Id 1: 100 Series / 4 software / Chip Version B1025A WSB Id 2: 100 Series / 12 software / Chip Version B1025T WSB Id 3: 200 Series / 4 software / Chip Version B1025A WSB Id 4: 200 Series / 12 software / Chip Version B1025T WSB Id 5: 400 Series / 4 software / Chip Version B1025A WSB Id 6: 400 Series / 12 software / Chip Version B1025T WSB Id 7: 900 Series / 4 software / Chip Version B1025A WSB Id 8: 900 Series / 12 software / Chip Version B1025T WSB Id 9: 1800 Series / 4 software / Chip Version B1025A WSB Id 10: 1800 Series / 12 software / Chip Version B1025T 2. Start the G2 Server - Click the G2 Server icon in the Gravimetric Gateway program group of your start menu. Under Mode in the menu, select Demo, then Start G2 Server. (Server must be stopped to access the Mode menu.) The G2 Server is now running in Demo Mode and can only access Simulated Blenders. 3. Start the G2 Client - Click the G2 Client icon in the Gravimetric Gateway program group of your start menu. By default the Client will connect to the G2 Server running on the same computer. When running in Demo Mode, G2 will have pre-configured information in the databases. This information consists of Blenders 1 through 10, Materials, Recipes, Line, Line Recipe, Supplier and Retrieval Times. These database entries are there for your convenience. The user, if desired, can enter additional information. Blenders 1,2,3,4 are individual blenders while blenders 5, 6, and 7 are part of a 3-blender line. The G2 Client will function the same whether the G2 Server is live or DEMO. Follow "Section 2 - Getting Started Check List" in this document regarding adding materials, recipes and downloading recipes or refer to the Gravimetric Gateway Manual. ========================================== Section 4 - Upgrading Your Version of G2 ========================================== The Gravimetric Gateway® Server / Client Software may be updated to the latest version easily and free of charge. G2 Updates may be obtained online or requested on disk. A full installation over a previous installation will upgrade G2 to the latest version and will not alter the databases HOWEVER it is important to backup critical data not only before installing an upgrade but as a routine proceedure. In most cases use a full installation to upgrade the G2 Software. Smaller single-file upgrades may be available for your installation with a smaller download approx. 1.5 MB as opposed to the 12 MB download of a full install. The UPGRADE ONLY may be applied if your G2 Version matches the current release with the execption of the last digit. Examples: If you have version 4.0.1 and the upgrade is 4.0.3, you may use the single file UPGRADE ONLY option. If your version is 3.0.17 and the current release is 4.0.3, you must use the FULL VERSION install. Additional upgrade instructions regarding single-file upgrades can be found on the following page: http://www.maguire.com/page.php/downloads.html ===================================== Section 5 - Version Release History ===================================== CURRENT FULL VERSION: 4.0.11 released January 2, 2008 To determine if your G2 software may be updated to the current version through the Upgrade Only option, compare your version to the currently available version as specified above. If your first two numbers match the currently available version, you may use the Upgrade Only option and upgrade G2 without a full install. Currently only 3.0.x versions of G2 qualify for the Upgrade only option. If you do not have a 3.0 version of G2 then you must use the G2 Full Install to upgrade G2. Release History of version 4.0 ---------------------------------------------------------------------- CURRENT FULL OFFICIAL VERSION: 4.0.11 4.0.10 Nov 30, 2005 4.0.9 Oct 12, 2005 4.0.8 Jul 21, 2005 4.0.7 May 19, 2005 4.0.6 Apr 21, 2005 4.0.5 Mar 2, 2005 4.0.4 Feb 17, 2005 4.0.3 Feb 1, 2005 4.0.2 Jan 27, 2005 4.0.1 Jan 21, 2005 4.0.0 Jan 18, 2005 Release History of version 3.2 ---------------------------------------------------------------------- 3.2.11 Dec 23, 2004 3.2.10 Dec 17, 2004 3.2.9 Sept 22, 2004 3.2.8 May 12, 2004 3.2.6 Feb 5, 2004 3.2.5 Jan 23, 2004 3.2.4 Dec 15, 2003 3.2.3 Dec 2, 2003 3.2.2 Nov 12, 2003 3.2.1 Nov 12, 2003 - Released approx. 4 hours, updated to 3.2.2 Release History of version 3.1 ---------------------------------------------------------------------- 3.1.4 June 17, 2003 3.1.3 Apr 16, 2003 3.1.2 Mar 6, 2003 3.1.1 Feb 13, 2003 Release History of version 3.0 ---------------------------------------------------------------------- 3.0.17 Nov 14, 2002 3.0.16 Oct 31, 2002 3.0.15 Sept 27, 2002 3.0.14 Sept 12, 2002 3.0.13 August 1, 2002 3.0.12 August 1, 2002 3.0.11 June 26 2002 3.0.10 never released 3.0.9 never released 3.0.8 May 23, 2002 3.0.7 May 14, 2002 3.0.6 May 8, 2002 3.0.5 Apr 16, 2002 3.0.4 Apr 15, 2002 3.0.3 Mar 27, 2002 3.0.2 Mar 20, 2002 3.0.1 Mar 18, 2002 3.0.0 Mar 8, 2002 Release History of version 2.3 ---------------------------------------------------------------------- 2.3.1 Dec 5, 2001 2.3.0 Nov 8, 2001 Release History of version 2.2 ---------------------------------------------------------------------- 2.2.3 Oct 17, 2001 2.2.2 Sept 26, 2001 2.2.1 July 18, 2001 2.2.0 July 9, 2001 Release History of version 2.1 ---------------------------------------------------------------------- 2.1.0 May 7, 2001 2.1.1 June 6, 2001 Release History of version 2.0 ---------------------------------------------------------------------- 2.0.3 Apr 25, 2001 2.0.2 Mar 29, 2001 2.0.1 Mar 12, 2001 2.0.0 Feb 8, 2001 Release History of version 1.2 ---------------------------------------------------------------------- 1.2.12 Dec 27, 2000 1.2.11 Dec 11, 2000 1.2.10 Nov 21, 2000 1.2.9 Oct 26, 2000 1.2.8 Oct 17, 2000 1.2.7 Sept 13, 2000 1.2.6 Aug 18, 2000 1.2.5 Never Released 1.2.4 July 18, 2000 1.2.3 June 9, 2000 1.2.2 May 26, 2000 1.2.1 May 17, 2000 ===================================================== Section 6 - Version Release History of Changes/Fixes ===================================================== Numbered items indicate fixes or modifications to G2 for that version --------------------------------------------------------------------- 4.0.10 1. Changes to Yield Control including: Server side changes and Support for LIW (Loss In Weight) blenders. 2. Misc bugs 4.0.9 1. Changes to Yield Control including: Server side changes and Support for LIW (Loss In Weight) blenders. 2. Changes to Download To Blender screen to support comma "," fractional seperator. This problem was found in non-English versions of Windows. 3. Misc bugs 4. Changes to View Plant screen to toggled AIMS functionality off when AIMS turned off. 4.0.8 1. Fixed a potential bug that can result in the logging process ceasing to log if a blender goes offline. 2. Improved startup speed of a blenders when the G2 Server is started. 3. Added Gauge Control to the Yield Control screen. 4.0.7 1. Fixed a potential communication problem between the G2 Server and the G2 Client that could result in an increasing consumption of memory on the G2 Server computer until the system runs out of memory. This problem would have been more likely to occur if G2 is communicating with the blenders via Ethernet and there are a large number of blenders on the G2 system. This problem was corrected in 4.0.7. 2. Fixed cycle by cycle database purging problem where purging cycle by cycle logs from G2 databases would only purge from within the past 30 days. 3. Material Usage report bugs were fixed. 4.0.6 1. Improved the logic of determining if a pre-01612 blender encountered a turnover or if a clear of totals had occurred. G2 versions previous to 4.0.6, in some cases, could see a clear of totals in the blender as a turnover and therefore would log a false material usage number. That number was usually a very high usage. This condition was corrected in 4.0.6. 4.0.5 1. Added a material level adjustment field to the Materials Edit screen in the AIMS window. This utility allows users to adjust the material level without using AIMS in its full capacity. 2. Minor bug fixes. 4.0.4 1. Fix memory leaks introduced with the new MySQL ConnectorJ. 2. Made minor changes in Yield Screen including: - Sending voltages via voltage panel will download a zero TCV voltage even though there is not a voltage value in the voltage panel. - Fix update of specific gravity value in upper right box. 4.0.3 1. Corrected a database update error in the Line database. When a new installation of G2 4.0.1 or 4.0.2 detects an existing earlier version of the line database, the G2 Server updates the database to the current format. An error in the update resulted in the G2 Client not to display blenders within the line. This error was fixed in G2 4.0.3. 2. The Demo databases have been updated to G2 version 4.0. 4.0.2 1. Corrected a table creation error. With new installations G2 would create an older version of the Line table. This in turn would cause errors in the Line database. This also affects new G2 installations using MySQL as well. Customers who are upgrading from an existing installation may not experience any problems as G2 4.0.1 will upgrade the Line database correctly. This problem was fixed in G2 version 4.0.2. 4.0.1 1. Corrected a timing issue in report generating that could result in a blank report page being displayed when a report is generated. This was fixed in G2 version 4.0.1. 4.0.0 1. Specific Gravity value has been added to Materials database and can be entered into the Materials screen of the G2 Client. The Specific Gravity value can then be used in Yield Control screen to calculate thickness or gauge for the line. 2. DNS Control Priorities located in the Line Edit Screen (previously located in the Setup screen) have been changed to set the YieldD rules per line as opposed to setting the rules globally for all lines. 3. Removed DNS Control screen and the Control Line Screen. The Yield screen replaces all functionality of the older DNS and Line Control screens. 4. The G2 Server now used the Java Virtual Machine version 1.4, upgraded from 1.3. 5. Yield Screen now supports CTRLT and CTRLX (Yield X, Yield T, Yield D modes). 6. Improvements have been made to report generation in G2, which has improved the speed of generating a report in when using both G2 for databases as well as using MySQL for the databases. 7. MySQL database module officially released in G2 4.0.0. 8. Added Specific Gravity checkbox to Line screen to calculate or not calculate Specific Gravity on the Yield screen. 9. G2 Watchdog - Designed as a means of monitoring COM port activity, the G2 Watchdog will shutdown and restart the G2 Server if COM activity ceases for a period longer than the specified time period in the Watchdog_G2_Server startup shortcut. USING the G2 Watchdog: G2 4.0 beta requires a full install of G2 to update to 4.0. When 4.0 is installed, a shortcut called Watchdog_G2_server will be placed in the G2 program folder (by default c:\g2). To launch the G2 Server with the Watchdog monitoring program, use the Watchdog_G2_server shortcut. This shortcut will launch a monitoring program, which in turn will launch the G2 Server. When launched from this shortcut, the G2 Server will observe a COM port activity timer. If a preset amount of time elapses without any COM port activity, the G2 Server will exit. The G2 Watchdog, monitoring the G2 Server process, will detect that the G2 Server has exited and will re-start the G2 Server. The timeout value is set by default to 15 minutes. Typically 15 minutes is 5 minutes longer than the longest possible interval that COM activity may not occur under normal circumstances. The timeout value is set in the Watchdog_G2_server shortcut's target field as wd=900 appended to the end of the command line. The value is in seconds. This may be changed if necessary. 10. Improvements to the G2 code, and bug fixes. 3.2.11 1. When G2 would read the materials database an error may occur that would result if a message stating that the materials database was corrupted. This error message however was false and that materials database was not corrupted. This false error message was fixed in 3.2.11. 3.2.10 1. Downloading same recipe, w/at least one diff material, will throw a NullPointer exception. Found in version 3.2.9, fixed for 3.2.10. java.lang.NullPointerException at dac.data.WSBRecipeKey.setName(WSBRecipeKey.java:112) at dac.data.WSBRecipeKey.(WSBRecipeKey.java:26) at dac.Monitor.setRecipeTag(Monitor.java:1339) at dac.Monitor.setTag(Monitor.java:696) at dac.Monitor.databaseActionPerformed(Monitor.java:441) at dac.Monitor.dbAction(Monitor.java:296) at dac.servers.DataServer.run(DataServer.java:1192) at java.lang.Thread.run(Thread.java:534) 3.2.9 1. Critical update for G2 systems applying G2 Certificates. Users applying G2 certificates to increase the blender licensing or for adding G2 features will need to update to the G2 version 3.2.9 or later. G2 versions earlier than 3.2.8 have a flaw in reading the date format of the G2-SA security key when a certificate had been applied after September 15, 2004. This flaw in the date format was repaired in G2 version 3.2.9. All users applying G2 certificates must update to 3.2.9 for updates to work correctly in the G2 Server. If a 3.2.9 or later update is not applied prior to applying a G2 Certificate, the G2 Server will not detect and report the correct licensing information and instead will report licensing for a single blender and all features (AIMS, DNS, EXT) as off. G2 will then only be able to communicate with one blender until an update is applied. However once the update is applied, G2 will correctly detect and report the licensing information. 3.2.8 1. In some recipes G2 could incorrectly total the percentages in the download screen where the total of the regrinds was reported to be over 100 when it wasn't. The result would be G2 not allowing the download to occur. 3.2.6 1. Previous 3.2.x versions could occasionally lockup communications to the blenders although G2 would appear to be functioning correctly. Symptoms would be downloads remaining at the hourglass and and lack of data in reports due to G2 not retrieving usage totals from blenders. This has been corrected in 3.2.6. 2. Blenders with a chip version earlier than 60809A (08/09/1996) may have communication problems due to the lack of the feature to set the XP parameter. This command was introduced in chip 60809A (08/09/1996). G2 Attempted to set the XT parameter during a download to a pre-60809A blender and did not complete the communication successfully. This will was corrected in 3.2.6 with two changes. First G2 checks if the blender is pre-60809A. If it is pre-60809A, G2 does not set the XT parameter. Second, G2 verifies that the recipe settings do not require the adjustment of the XT parameter. If the recipe does require an XT adjustment, G2 will prompt the user to correct the recipe before allowing the download. 3.2.5 1. Previous 3.2.x versions could occasionally lockup communications to the blenders although G2 would appear to be functioning correctly. Symptoms would be downloads remaining at the hourglass and and lack of data in reports due to G2 not retrieving usage totals from blenders. This has been corrected in 3.2.5. Developers Note: Version 3.2.5 did not correct the "lockup" problem as stated above. Version 3.2.6 addressed and corrected the lockup problem. 2. Language files updated. Previous 3.2.x version had incomplete translations in languages other than English. 3.2.5 known issue to be corrected for next version: Blenders with a chip version earlier than 60809A (08/09/1996) may have communication problems due to the lack of the feature to set the XP parameter. This command was introduced in chip 60809A (08/09/1996). G2 Attempted to set the XT parameter during a download to a pre-60809A blender and does not complete the communication successfully. This will be corrected in 3.2.6. 3.2.4 1. Modifications to the Material Usage Report screen's Start/Stop time selection. G2 versions prior to 3.2.4 allowed the user to specify a start/stop time by increments of hours and minutes. G2's data could only limit reports by retrieval times that existed during the data collection event. Times that were specified by the user in many cases did not match actual retrieval times and reports presented data that appeared to be other than what was specified in the report screen. 3.2.3 1. XT parameter adjustment during recipe download fixed. Previously release versions 3.2.1 and 3.2.2 did not correctly adjust the XT parameter during recipe downloads with recipe settings requiring an XT parameter adjustment. This problem is corrected in version 3.2.3. 2. Improvements to the G2 code, and bug fixes. 3.2.2 1. Security has been applied to the G2 Server for startup, shutdown and closing the G2 Server. Important information on Security: - The enhancements to security has required an update of the security database. During an upgrade, users names and passwords entered into the security screen are converted over into the the new database when the G2 Server is started, however only the admin user's administrative privileges are retained granting all rights to the user admin. All other users will require their privileges to be specified by the user admin. Re-entering privileges is required due to the change from a 5 level security clearance system to unique user by user privilege system. - If Security was enabled in the previous installation of G2, an upgrade to 3.2.2 will require entering the username admin and your admin password. - Be aware that after an upgrade to 3.2.x or later from previous version of 3.1.x or earlier, you need to know your admin password if security was enabled in your previous installation of G2. If an upgrade was applied and the admin username's password is unknown, you will not be able to start the G2 Server. The work around for this situation is to delete the Security.data and Security.key from the c:\g2\g2data folder on the G2 Server PC. 2. Trend Screen re-design with more features including better Trend reporting, threshold alarms, Trending of multiple blenders, improved graph naviation and graph printouts. 3. MySQL - G2 version 3.2 now offers support for the use of MySQL as the primary location of the G2 databases. For customers who do not wish to use MySQL as the database engine, G2 continues to maintain its own set of databases. Important Notes on MySQL: - The MySQL installation is not included with the G2 software. - To download MySQL and for MySQL support, please visit: www.mysql.com - For MySQL setup instructions for use with G2, please read the latest copy of the G2 manual available at: www.maguire.com/g2 4. By default, when a blender is added to the Blender database, the recipe tag will be set to "Recipe". During a Download to Blender: In previous versions of G2, while downloading, G2 would cross check the recipe database to see if the recipe was from the recipe database. If not, G2 would not allow the download. In the case of customers who do not use recipe tags, a blank recipe was also not permitted. In 3.2 G2 permits this action now, in the case of the recipe tag pre-set to "Recipe". 5. Updates to the Security Screen allowing specific privileges to be granted to users, upgrading from a 5 level security system. 6. G2 screen layout changes using a different layout manager. 7. Improvements to the G2 code, and bug fixes. 3.2.1 Nov. 12, 2003 - Released approx. 4 hours, updated to 3.2.2 with modifications to security database conversion. Re-released as 3.2.2 on November 13, 2003 3.1.5 1. Multiple Network Interface Card Support Introduction of a feature to specify the I.P. address that the G2 Server will listen on for G2 Clients connections. This feature was introduced for customers who have two or more Network Interface Cards installed on the G2 Server PC. Specifying the I.P. address of the Network Interface Card that the G2 Server will listen for G2 Client connections on is done after the installation of the G2 Server as follows: After installing the G2 Software a modification to the G2 Server shortcut commandline must be made. The shortcut is located in two places, in the start menu and in the c:\g2 folder. To modify the shortcut commandline in the start menu, right-click the Start Button and choose Explore. In the right window, double-click Programs then Gravimetric Gateway. Right-click the G2 Server icon and choose properties. Using the arrow keys, go to the end of the "Target" field. Append to the end of the commandline: ip=x.x.x.x where x.x.x.x is the IP address of your NIC that G2 Client PC's can connect to the G2 Server. The end of the commandline should appear as follows: dac.G2Interface ip=x.x.x.x ^ Must be separated by a space, replace x.x.x.x with your IP. To modify the shortcut in the c:\g2 folder, browse My Computer to the c:\g2 folder. Right-click the G2 Server icon and choose properties. Using the arrow keys, go to the end of the "Target" field. Append to the end of the commandline: ip=x.x.x.x where x.x.x.x is the IP address of your NIC that G2 Client PC's can connect to the G2 Server. 2. G2 Servers Ping communications test utility fixed The prior version of G2, 3.1.4, the ping test did not function properly. Ping test fixed in 3.1.5 3.1.4 1. Satellite COM Server fix - The prior version of G2, 3.1.3 had a problem with the Satellite COM Server which prevented it from starting correctly. Fixed in 3.1.4 2. Improvements to the G2 Software and minor bug fixes 3.1.3 1. Baud Rate selection implemented. Toggles between 1200 and 2400. (Switching to 2400 requires changes to G2-SA and all blenders. See http://www.maguire.com/manuals/g2_baudrate.pdf for more info) 2. Bug in reporting fixed. If report was run using Report a Filter, then the same report is run without the filter, exception would occur. Fixed in 3.1.3. 3.1.2 1. In the Edit Recipe Screen if entering setting as XT setting starting with the decimal, decimal would not lock in place unless setting is entered with zero before decimal. Fixed in 3.1.2 2. When creating a 4 software recipe natural setting would prompt: "Recipe includes a setting of zero" Fixed in 3.1.2 3. Material changes in an existing recipe would not download new material name if "No Settings" was checked off. Fixed in 3.1.2 3.1.1 1. Simulated blenders weren't using the global GG_DATA environment var to open its configuration file and icons. So, starting the simulated blenders from the Start menu will fail to find the icons and fail to write the configuration files in the correct place. 2. Zero setting components were stopped from being downloaded to the blenders in 3.1. Customers requested the ability to create and download zero settings (in previous versions). Changed G2 to have this feature like previous versions. A component can have a zero setting as long as it doesn't violate one of the following rules: a. If all the nonzero components are regrinds, then the component totals must add up to 99/100. b. If there is a nonzero additive component, there must be a nonzero natural. 3. Certificate screen is disabled if G2-SA/Security Key is missing. 4. Improvements to the G2 Software and minor bug fixes 3.1.0 1. New Features - New Yield Control Monitoring/Control Screens - Material Usage Report Start/Stop Time Fields added - Events Log Reporting in the Activity Logger - Databases Recovery & Verification utility - Simulated Demo Blenders for G2 DEMO Server Mode - Communication Quality Ping Test for testing Serial lines - Improvements Client windows settings - XT settings support in recipe screen - Improvements to Trend Please refer to the latest copy of the Gravimetric manual for more information regarding these new features. 2. Improvements to the G2 Software and minor bug fixes 3.0.17 1. In certain situations clearing blender totals or component totals turning over could result in logging invalid material usage. Generally this could occur if the blender was either offline when the clear or turnover took place or if G2 was shutdown while a clear or turnover took place. G2 was modified to better detect if a clear or turnover occurred and to prevent invalid usage totals from being logged. 3.0.16 1. G2 incorrectly recognized even component turnovers for newer chips. 2. Added support for XT parameters for WSB chips that didn't support GET_ALL_PARAMETERS MLAN command. 3. Download to WSB screen was clearing the line recipe tag. 4. ServerLog, DebugLog, ErrorLog default archived file sizes increase. Previously archived at 40k (500 lines), reset to 800k (10,000 lines) 5. Download to WSB screen was incorrectly displaying XT value of 00100 causing the decimal to shift one position rather than two positions. 3.0.15 1. Report windows will display wrong page information if paging forward and backward too often. 2. G2 would fail to start if port 1099 was used by another program. 3. Removed "Batch Weight" field from Edit-Blenders screen. 3.0.14 1. Added the ability to change the server port on commandline. 2. G2 Server will probe for OFFLINE blenders for 1 hour after startup of the G2 Server. 3. No longer log GET_PARAMETERS failures. 3.0.13 1. Correction to operating system detection. COM port affected. 3.0.12 1. AIMSServer and ExtrCtrl could not be enabled from Setup screen. 3.0.11 1. Closing G2 before G2 fully starts will lock up G2 and stop it from closing properly. 2. Any logged record which fell between midnight and before End Of Day, and within a retreival which starts before midnight and end after midnight, will appear under the day after midnight. However this caused confusion, so these records will now be reported in the previous day. Reporting previously by DAY, RETREIVAL time caused this error. 3. G2 Server will detect if another process is using the COM port, and it will pop up a message indicating this. This is especially helpful if another G2 Server is already running. 4. Improved recipe download time. 5. Improved time for blenders to be monitored. 3.0.8 1. Activity Logger was logging type changes as setting changes and vice versa. 2. Downloading a recipe with changed components didn't change the component in blender database. 3.0.7 1. Server failed to log cycle by cycle data to databases and printed error information. 3.0.6 1. Server invoked downstream MLAN commands which logged errors in G2 Server. 3.0.5 1. Print features information to G2 server startup. 3.0.4 1. Print features information to G2 server startup. 3.0.3 1. Shutdown process too long. Improved shutdown response time. 2. Blenders went OFFLINE/ONLINE intermittently. 3.0.2 1. Blenders that dropped offline and remained offline for over an hour will be probed every 30 minutes. 2. When blenders drop offline, the Blender Screen parameter table for that blender remains visible. If blender drops offline, parameter table is removed. 3.0.1 1. Upgrade transitional issued corrected. 3.0.0 1. The following features added: a. Materials Reporting b. Recipe Reporting c. Cycle by Cycle Reporting d. Ethernet communication support e. AIMS Reporting f. Inventory Level Reporting g. Satellite ComServer h. Event Response Monitor 2. Includes minor bug fixes. 3. Improvements in performance with less processing. 2.3.1 1. COM port is opened in demo mode. 2. Foreign Language support for new features introduced in 2.3.0. 2.3.0 1. The following features added: a. AIMS History query and purge b. Activity filter and query c. Report filters d. Reports including percentage breakdown e. Retrieval times filter for reports f. Downstream and Yield control for beta sites 2. Inludes bug fixes for reported bugs Note* Upgrading to 2.3 requires a full upgrade. 2.2.3 1. Client did not connect to default server. 2. When trend is run for a long time, the server crashed. 3. Recipe screen permitted recipe numbers between 100-999 only. 4. ViewPlant screen table reported incorrect values. 5. Running a report a second time, may sometimes result in a blank report. 6. Pie chart displays wrong percentage number. 2.2.2 1. Running reports in succession may display previous reports. 2. Downloading a recipe with the same types and settings as the previous recipe will result with G2 switching the recipe back to the previous recipe. 3. Downloading a 4 component recipe to a 12 component blender will result with the 3rd component OFF. The blender will display that the 3rd component is an ADDITIVE. 4. ViewBlender will sometimes display incorrect information about selected blender. 2.2.1 1. Java failed to run with Pentium IV 2. After connecting to a new server, Download to WSB screen still displays the recipes from the previous server. 2.2.0 1. Added personal settings, auto recipe downloading, parameters viewing, and tag material consumption. 2.1.1 1. Control Line screen displays decimal in wrong place for some values. 2. View Download to WSB screen displayed wrong values for blender, showing values of one blender another. 3. Historical trending for a previous recipe will use current recipe. 4. ActivityLogger - weightUnit changes every hour; steady rate got logged when it shouldn't 5. Security - failure to delete users from the security screen 2.1.0 1. Requires full upgrade. New features added to this version. 2.0.3 1. ControlLine - If the total throughput is changed to an invalid number (ex. too large), the voltage and throughput values momentarily change to large amounts before recovering. 2.0.2 1. Blenders going offline for over a day, will log 2 erroneous totals after coming back online. The erroneous log totals include when the blender comes online, and the next log time. Logs after these will be correct again. 2.0.1 1. Reports didn't always print a row's reported fields. 2.0 1. Upgrading to 2.0 will require you to make a full install. New features have been added to this version. 1.2.12 1. If you have a older version, we recommended you upgrade to this version. 1.2.11 1. Client screen repaint problems fixed. 1.2.10 1. View Blender screen incorrectly displayed totals such as negative numbers. 1.2.9 1. Reports by retrieval time excluded retrieval times between midnight and end of day (EOD). 2. Reporting by retreival time followed by day has been disabled. 3. When starting up, g2 took a long time to find the blenders. 1.2.8 1. Fixed the OFFLINE/ONLINE problem. 1.2.7 1. Fixed: Reports by retrieval time could result in 0:00 - 0:00. 2. When a blender goes OFF_LINE for over a day and comes back ON_LINE, it logs incorrect totals. 3. Blenders go OFF_LINE when G2 experiences communication problems. 1.2.6 1. When a blender goes offline could cause bad totals. 2. Download Blender Screen - Download a different recipe to a blender without changing workorder and operator results in all three being changed.1.2.5 1. Changed About box to include # of blenders. 1.2.4 1. Clearing totals produces incorrect usage totals. 1.2.1 1. Closing Login window causes error to be printed. 2. G2 doesn't default to "lite" mode. Instead, it just timed out after about 30 minutes. 3. Clients weren't disconnected from server when server shut down. 4. Outer reports didn't reset inner reports to zero. 5. Purge and Archive functions end date used wrong month. 6. In Advanced Purge and Archive, the "Reload with Next Records" button wasn't disabled. 7. In the Advanced Purge and Archive's list, stop time was displayed, instead of start time. 8. When client connects to server, menu flickers. 9. In Advanced Purge and Achive, purging selected records before reloading caused the list to load from beginning of start date. 10. In Advanced Purge and Archive, when "Cancel" is chosen after prompt for purge before reloading, the Purge and Purge/Archive buttons aren't disabled. 11. In Purge and Achive and Advanced Purge and Archive screens, the begin and end dates are adjusted by the end of day set in Setup. 12. Server log window displays the latest log. 13. Clients were notified of silenced alarms. 14. Settings column in View Blender will no longer be displayed in a Pie Chart.