M4 New Builds Installation Notes

From PTAGISWiki

Beta Release 1.0.0.1 (10/25/07) Comments

--Alan 15:19, 29 October 2007 (PDT) Site monitoring should not be hindered (obviously). Was M4 suspended? I did have to click the windows logon "Employee" user icon to get to the desktop at 9:23

10/29/2007. Examination of the M4 logfile shows these three consecutive entries:

First:

Timestamp: 10/25/2007 4:09:25 PM
Message: The M4 Monitor Service denied a request by the system to suspend the computer.
Category: Default Category, Trace
Priority: -1
EventId: 200
Severity: Information
Title:
Machine: M4-GATEWAY-PROF
Application Domain: M4MonitorService.exe
Process Id: 2476
Process Name: C:\Program Files\PTAGIS\M4\M4MonitorService.exe
Win32 Thread Id: 1612
Thread Name: 
Extended Properties: 

Second:

Timestamp: 10/25/2007 4:09:25 PM
Message: The computer is about to enter a suspended state.
Category: Default Category, Trace
Priority: -1
EventId: 200
Severity: Information
Title:
Machine: M4-GATEWAY-PROF
Application Domain: M4MonitorService.exe
Process Id: 2476
Process Name: C:\Program Files\PTAGIS\M4\M4MonitorService.exe
Win32 Thread Id: 2628
Thread Name: 
Extended Properties: 

Third:

Timestamp: 10/29/2007 9:23:21 AM
Message: The system has resumed operation after being suspended.
Category: Default Category, Trace
Priority: -1
EventId: 200
Severity: Information
Title:
Machine: M4-GATEWAY-PROF
Application Domain: M4MonitorService.exe
Process Id: 2476
Process Name: C:\Program Files\PTAGIS\M4\M4MonitorService.exe
Win32 Thread Id: 540
Thread Name: 
Extended Properties: 

Troy 08:13, 25 October 2007 (PDT)My comments are below.

1. Used 'add/remove programs' to un-installed previous version of M4.
2. Downloaded M4Beta1001 from the ftp server and installed.
3. The following is a chain of events or actions performed.
   • Opened M4 application and started monitor.
   • Stale data was read
   • TT data from the 4 transceivers.
   • Stopped monitor, shut down app and rebooted.
   • Started app and monitor.
   • Started wheel with 2 tags on it running at 7 ft/sec.
     • Verified good data.
   • Stopped the monitor and re-started the monitor after 2 revolutions of the wheel.
     • No stale date.
   • Paused the monitor and re-started the monitor after 2 revolutions of the wheel.
     • Stale data. 4 records for 04, then 4 records for 03 and finally 4 records for 03 were written to the Operations page before data started entering in an orderly fashion.
     • No stale data for 01 was witnessed???
   • Stopped the monitor and re-started the monitor after 2 revolutions of the wheel.
     • No stale date.
4. Question#1 - What is the function of 'pause' and what should the user expect to happen when the monitor is paused.
5. Question#2 - The configuration doesn't appear to be lost when M4 is un-installed. Is this the way we want it to be?
   • Question#2.1 Should the configuration be the same for each build?
   • Question#2.2 Should we go through the process of building a new configuration when a new build is released to ensure that nothing changed in that area?

Beta Release (10/10/07) Comments

1. Installation went smoothly, initial start up had issues.
   • Found that .NET 3.0 is required. Once that was loaded M4 started OK.
   • Downloaded drivers for the device masters and configured a diversion unit in M4.
     • The following is a progression of what happened.
     • Data on 01 (COM36)
     • Tag data, status reports and odd ‘buffered tag’ which would show up everytime a tag came through 01.
     • Sparse data on 02. Occassional tag no status report.
     • No data on 03.
     • No data on 04.
     • M4 stopped and started, PC re-booted didn’t change results.
     • Changed port speed on DM’s
     • No data on 01
     • Tag data, and status reports on 02-04.
     • M4 stopped and started, PC re-booted didn’t change results.
   • Loaded Minimon on PC and found a problem on 02(no data) nor was is on the MM machine. Turned off/on 02 and started working on minimon and M4?
   • Started M4, received framing errors on 01-03 nothing for 04.
   • Stop monitoring, shut down M4. Shut off all transceivers.
   • Started M4 and started monitoring.
   • Turned on transceiver 01-data good on M4
   • Turned on transceiver 02-data good on M4
   • Turned on transceiver 03-data good on M4
   • Turned on transceiver 04-data good on M4
   • Turned off/on 02 while wheel was running. Data still good.
   • Stopped monitoring, started monitoring. Data still good.
   • Stopped monitoring, shutdown M4, restarted M4 and started monitoring. Data still good.
   • Shut down PC and restarted all. 40 + buffered tags were recorded for 02,03,04 but not 01.
   • Receiving exception errors occasionally. No data in the data tab only in the operations tab?
2. Problem discovered on 10/19/2007
   • Discovered a problem that may be related to device masters but affects M4 and Minimon.
     • Problem: The Device Masters are buffering data, when M4 or Minimon are shutdown and restarted the buffers immediately dump into the data file. This could be hazardous to equipment if this were to take place at a SbyC site, not to mention several tags would have erroneous time stamps.
     • I called comtrol tech support and they gave me case # 25313 and suggested I go to Device Manager, Multiport Adaptors, Port settings and click on the port I was using. (in this case COM36) and check the ‘wait for physical transmission’ check box which I did (I then did it for all ports). At first this seemed to fix the problem in Minimon but after further testing it was evident that it did not. I thought perhaps M4 was writing to the DM’s and possibly changing settings as I was in and out of M4 and Minimon without rebooting. This turned out to not be the case. Then I thought it might be something to do with the fact that I had the wheel constantly running and if the wheel was shut off for a period of time Minimon seemed to work most of the time but could never get M4 to. On my last test however I shut off the computer while the wheel was running and then shut off the wheel about a minute later. When I re-started the computer and Minimon a large number of buffered tags were dumped all at once. The only work around is to shut off the wheel prior to shutting down the computer.
       • Mack, at Comtrol said they have some tools that could help us trouble shoot the problem but most likely the when the program lets go of the port is isn’t clearing the buffers.
3. Troy 07:56, 24 October 2007 (PDT)Application Comments and Notes
   • The application looks very clean and easy to maneuver through. The initial site configuration was easy once the Device Master drivers were installed. There doesn’t appear to be a ‘hot key’ for inserting a marker. Having a ‘hot key’ to insert a marker would be helpful for troubleshooting. There isn’t much to test drive in this release as the Tag data and Alarm data are not making it from the Operations tab to the Data tab which would be helpful in troubleshooting future releases.
     

• Noted Observations With the Above Comments.
  • Keep in mind that BO4 running Device Masters has not exihibited the problems described.