Errors: mscorlib: Index was outside the bounds of the array.


Some conditions in the GridTrak software send it out of bounds. The only recovery is to close the program and run it again.
The cause is under investigation. One suspect cause is that the conditions may be related to operating the software in RDP sessions where the screen scaling changes between sessions. The issue has not been experienced when operating the software while logged into a physical workstation.
Typical Errors:
Red "X" is displayed in place of the graphic panels.
Err - 03/01/12 21:50:08.549[3], MainWF: Phasor_DrawGrid(1)
Index was outside the bounds of the array.
Err - 03/01/12 21:50:08.553[3], Main, Display Timer: Error: Phasor_Calc,Phasor_DrawGrid,PhaseChart_Calc,PhaseChart_DrawGrid,
Index was outside the bounds of the array.


ajstadlin wrote Mar 25, 2012 at 2:52 AM

I have not observed this error when operating in GPS Integrated mode. This is probably specific to host synchronized (non-GPS Time) mode of operation.

This is still an issue in Release 9.7

ajstadlin wrote Apr 17, 2013 at 9:46 PM

This is still an observed problem possibly related to the difference between the data time stamps and the current system time. The problem is less likely to happen when the host's time is synchronized with GPS or NIST standard time and the PMU's time is sychronized with the host. For example, if the PMU is operating in GPS synchronized mode and the host PC's clock time is significantly different from the GPS time, then there may be "X" charting problems. It is also possible that Serial Port buffering may cause delays between the data tiimestamps VS when the host processes the data from the PC's serial port buffer. The best mode of operation is to minimize the Serial Port buffer size or reduce the number of samples per second transmitted by the PMU to assure that the data does not accumulate in the serial port buffers.

This is not a problem with PMU Connection Tester or openPDC - both of which have much more sophisticated data I/O processing.