1. Partners in Batching Productivity with: Q.iMPACT WebEx Session #6: Q.iMPACT Support Tools Mark Whitt, Mettler-Toledo Q.i Product Support Engineer Scott Haimerl, Mettler-Toledo Q.i Product Manager September 24, 2008

2. Tool NameWhere can I find it? What does it do?How does it work?What tool(s) is it similar to? Why should I use it? DMT_Controller FTP SiteTransfer files to or from a Q.i or JagXtreme. See WEBEX #1 - Backup & Recovery Procedures FreeFTP, Internet Explorer Most reliable DMT file transfer method. Verification mode available. Can upload files from multiple units with a single click. Automatic Backup Feature available. FreeFTP http://www.brandy ware.com/freeftp.h tm Transfer files to or from a Q.i or JagX. Not supported by Mettler- Toledo. Contact Brandyware. DMT_Controller, Internet Explorer More reliable than Internet Explorer FTP. E-Flash FTP SiteUpdate the firmware on a Q.i or JagXtreme E-Flash Procedure Document NoneTo update firmware in your Q.i (or JagXtreme). MT_Port_Monitor FTP SiteRecords detailed troubleshooting information and Feed History Records. This WEBEX!HyperTerminal Q.i365 In case you need to send detailed information to Mettler- Toledo for analysis and troubleshooting.  Automatically compresses and archives data.  Automatically generated exception report to speed analysis.  Monitors for unexpected terminal resets  Monitors an entire cluster at once! MT_Datamonitor FTP SiteRecords changes to specified Shared Data variables to a log file. This WEBEX!NoneUnofficial tool to assist in troubleshooting:  Drain Time Problems  Unstable Scale  etc.. HyperTerminal Various Internet Download sites. No longer free from Hillgraeve! Records troubleshooting information and Feed History Records. How to setup HyperTerminal to capture data MT_Port_Monitor, Q.i365 Already installed on most systems (comes with many Windows Packages). Easy to use, but very limited functionality. Set_PC FTP SiteSets personality code on Controller card so specified version of Q.i firmware will run. Set_PC Tool InstructionsNoneRequired to run the Q.i firmware! Prevents accidental usage of incorrect firmware in Q.i unit. Personality code PRESET at the factory. Rarely needs modification. Problem Report FTP SiteAllows user to collect information about a problem in a structured way and send it to MT. Problem ReportNoneHelps MT support personnel understand the architecture of your system so they are better able to assist in solving problems. Better problem definition. Q.i365 FTP SiteRecords Feed History Information. Upcoming WEBEX on Q.i365! MT_Port_Monitor, HyperTerminal Stores feed information into a database. Provides SPC and trend analysis for preventative maintenance. Provides detailed troubleshooting information for each feed. Tool Cross-reference

3. Problem: How to collect troubleshooting data or archive feed history records on a Q.i? Traditional solution was to use HyperTerminal. But this posed problems of its own, such as: No predetermined structure as to where data should be stored. Data files could grow very large, making it difficult to transport them and analyze them. Setting up multiple HyperTerminal sessions to monitor a cluster was cumbersome, and keeping the data together was tedious. HyperTerminal had a tendency to disconnect, requiring someone to notice it and manually reconnect, resulting in lots of lost data. No way to toggle Q.i flags, which turn on extra troubleshooting output when needed. No way to separate out Feed History Records from Troubleshooting Data.

4. MT_Port_Monitor answers these problems. Data is always stored in the same directory, and in a consistent manner. Data is automatically compressed, and a new log file started at a user specified time every day. To save data from multiple Q.i’s the user merely needs to specify the IP addresses of the units to be monitored, from one application. If MT_Port_Monitor stops receiving data from any unit, that connection is automatically reset after a specified time (default of 10 minutes). Ability to directly edit the Q.i’s BX222 Shared Data variable to turn on troubleshooting information has been built in. Feed History records can be directed to a separate file for archiving.

5. Purpose: Record detailed information from a Terminal, or Cluster of Terminals, while running a process. Uses: 1.Validate a Process 2.Troubleshoot a Process 3.Troubleshoot a Terminal 4.Archive Data Produces a complete sequential record of terminal’s activity, including debugging information and Feed History Records.

6. Use this link: MT_Port_Monitor V1.0.3MT_Port_Monitor V1.0.3 Get it  Save and Extract it  OR

7. Install it  Run it  Install 7-zip for compression Or double click on the Desktop Icon From the Start Menu…

8. Turn on “Log Trace Data” for EACH Q.i as follows: 1 2 3 4

9. Hint: Synchronize the cluster Time and Date with the PC now!

10. Cluster Configuration Enter all of the Cluster IP Addresses. Don’t forget to click the “Add IP Address” Button!

11. Auto Archive Set the Time Click the “Set” button Check the “Enable Auto Archive” checkbox. Enable Output Files Don’t check “Memory Leak” checkbox. Check “Command / Feed Status” checkbox to generate a “Command_Feed_StatusCheck.txt” file. Check “Process History Records” to generate a file that contains only Feed History Records.

12. Once the options are set, click the “Connect” button to start monitoring.

13. To view live data from a different unit, change the IP address selected.

14. Note Directories

15. If any unit being monitored should cycle power or reset, an alert banner is displayed. The event is also recorded in MT_Port_Monitor’s log file. This button clears the alert

16. Click here to force an archive immediately. Archive in Progress. Files Generated. Note Directory!

17. There is a data file for each IP address. Each data file contains the following: All commands sent to the Q.i All Q.i responses Feed History Records Trouble-shooting information

18. File NameStatus Type Tick Counter Status Note filenames Something interesting here! Note: Any other “.txt” files in the date directory will be compressed and stored here. Good place for project notes!

19. There is a History file for each IP address. Each record contains over 80 pieces of information about each feed. How do we make sense of this???

20. Excel Spreadsheet Tool:HistoryDataTempl.xls 1 2 3 4 5 6 7

21. This sorts by Material Path

22. MT_Port_Monitor can NOT run on the same PC at the same time that other monitoring programs are running, such as MT_Datamonitor and Q.i365 due to resource conflicts. Sometimes we only need the “Command_Feed_StatusCheck.txt” file to diagnose a problem. The ErrHist.Log file on each Matroller contains the same information as the “Command_Feed_StatusCheck.txt” file.

23. Detailed help function available! Tool Tips on all objects!

24. Problem: How to access and collect Shared Data variable data directly from a Q.i (or JagXtreme) so that the information can be used to troubleshoot a process or Terminal problem? ANSWER: MT_Datamonitor! Monitor Scale or Flowmeter variables and flags Monitor multiple terminals at the same time. Logging Interlock allows stored data to be narrowed to the area of interest. Information stored in a file on the PC for later analysis, or so it can be sent to Mettler-Toledo support personnel. NOTE: MT_Datamonitor is an UNOFFICIAL tool that has been found to be very useful. But documentation and help are limited. It is usually used under the direction of an MT Engineer.

25. Purpose: Record changes to Shared Data variables on a Terminal or a Cluster of Terminals. Uses: 1.Validate a Process 2.Troubleshoot a Process 3.Troubleshoot a Terminal Produces a sequential record of changes to the specified Shared Data variables.

26. Use the same procedure as for MT_Port_Monitor: Download from the FTP site: MT_DataMonitorMT_DataMonitor Extract into a temporary directory Run the Setup.exe – No 7-zip to install this time! Run it  Or double click on the Desktop Icon From the Start Menu…

27. Enter IP Addresses to be monitored (just like MT_Port_Monitor). Type in new IP Address Click “Add IP Address” Select Variable from List Select Update Mode Click “Add Variable” to add it to the list. Default Log File Name

28. How do I figure out what Shared Data Variables to look at? Use ShareData.doc !ShareData.doc

29. Select the file to use for logging by clicking “Browse” Accept the new Default name, or type in your own. The new file name is shown here.

30. Define the Multiple Define the base units: 0.1 Seconds Seconds Minutes Hours Days Defines how often a record will be written to the log file, NOT how often the variable will be checked. Controls the size of the Log File. Polling Rate defines how often all of the variables in the list should be read from EACH of the Q.i’s being monitored. Controls the amount of Network Traffic generated.

31. Click here to start logging Click here to stop logging How many updates were written to the log file Log File data Note the following info: Time Stamp IP Address Shared Data Name Shared Data Value Clears Update Count – restart at zero.

32. A way to restrict data based on value Checking this enables the Logging Interlock Enter the value above which data should be recorded. Current Value of First Item in the list. Red indication shows that values are NOT being recorded.

33. Number of records written to log file. Current Value of First Item in the list. Green indication shows that values ARE being recorded.

34. MT_Datamonitor can NOT run on the same PC at the same time that other monitoring programs are running, such as MT_Port_Monitor and Q.i365 due to resource conflicts. Questions?

35. 1.Backup recovery procedures March Mark Whitt and Scott Haimerl 2.New features in A.0 firmware (plus earlier versions and options) April Mark Whitt and Scott Haimerl 3.Optimizing material paths and channels May Bradley Timm and Scott Haimerl 4.Getting help, where, who, when? June Scott Haimerl 5.Guidelines for insuring a successful installation August Bradley Timm and Scott Haimerl 6.Support tools and how to use them September Mark Whitt and Scott Haimerl 7.Mettler-Toledo Q.i 365 product (license required) October Bradley Timm and Scott Haimerl

36. Thank you for your participation! See you next month for WebEx #7: Mettler-Toledo Q.i 365