Instrument Log 

MAWS             C1                  CF Lamont, OK

Date

Technician

Comments

5/17/16

KT

Computer software patch updates were installed on the computer which caused the program needing to be restarted. At 1300 GMT the computer program was restarted. RTS at 1315 GMT.

7/13/15

Mentor

After 6 days, the MAWS program (which now includes a filter for wind spikes) is still functioning without problem.  All data spikes are being removed from the data stream. This issue can be considered fixed at this time.  (Regarding DQPR 4485)

7/7/15

Mentor

MAWS continues to show random spikes in wind speed data.  A new version of the data logger program was received from Vaisala.  Their best fix was to employ a data filter to mask out the large values which arise from a parsing issue.  They believe this is happening because there are 4 ports being called on via a Moxa.  They don't really know.  Mentor installed the program on a test system at ANL and tested it as best as possible (the issue can't be duplicated exactly at ANL). The tests seem to be successful.  Mentor uploaded the new program to the MAWS data logger at the SGP at 1508 GMT today. Will monitor the data to see if the wind spikes are removed.  The logger setup file is named SG062615.adc and replaces SG020915.adc.

4/8/15

CAM

As part of T/S wind speed spikes, instrument mentor requested the *control box and all its contents be swapped with the one from the ENA system.  Shut MAWS down at 1733 GMT and swapped control box with one designated for ENA.  Restored power and RTS at 1910 GMT.

                        *Old SN                   *New SN

Control Box:      K05502                   K05507

WD Tag #:        WD80618                WD80614

Datalogger::      J3975460                J3765073

Barometer:        K0440015               K0440020

Moxa:               TACIC1097680        TACIC1097666

4/6/15

CAM

Instrument mentor on site.  Continued T/S of wind speed spikes.  At 1445 GMT, bypassed the MOXA inside the MAWS enclosure by using a custom cable to connect the datalogger’s RS485 output directly to Port 2 of the external MOXA.  Changed MAWS settings on the virtual computer to read from Port 8, which corresponds to Port 2 of the MOXA.  Observed wind speed spikes on the MAWS console at 1640 GMT, thus eliminating the internal MOXA as the problem.  Bypassed the wind speed sensor’s surge protector at 1745 GMT.  Observed wind speed spikes at 1910 GMT, thus eliminating the surge protector as the problem.  Reloaded the program that Chris Keenan had supplied on 3/11 that included a checksum for the wind data.  RTS at 2015 GMT and will continue to monitor status.

3/17/15

CAM

Mentor requested the spare WMT sensor be hooked up in order to check the configuration settings.  Powered MAWS off at 1730 GMT.  Connected wind sensor SN K0630002 to RS485 port with vendor supplied service cable and to MAWS 15V power.  Mounted wind sensor on fence post near MAWS.   Restored MAWS power and RTS at 1742 GMT. 

3/12/15

Mentor

1 minute wind speeds were not being reported with last setup file that was loaded.  Mentor uploaded the last good setup file (SG020915), but wind spikes then returned.  Mentor continues to look into the problem.

3/12/15

CAM

There have been no wind speed spikes since the test setup file with checksum was loaded yesterday.  Mentor modified the original datalogger setup file to include this checksum and asked it be loaded to datalogger.  Powered MAWS off at 1759 GMT.  Removed all test communication cables that had been previously installed during testing.  Restored power at 1804 GMT.  Uploaded the original setup file (now with checksum) at 1808 GMT.  Restarted MAWS observation console and RTS at 1812 GMT.  1 minute wind speed averages would not display, so mentor set it for 2 minute averages for now.  Also removed test WMT700 from fence rail and put back in spares storage.

3/11/15

CAM

Instrument vendor supplied a new setup file that inserts a checksum at the end of the wind message in hopes of eliminating false wind speed spikes.  Closed MAWS observation console at 1348 GMT.  Uploaded new setup file US313v13.adc to datalogger.  Opened MAWS observation console and RTS at 1357 GMT.

3/6/15

Mentor

Mentor reloaded the original setup file to the datalogger at 2015 GMT and requested the raw SDI-12 signal be monitored and captured as it was on 2/26.  Connected the raw SDI-12 signal from datalogger MOD2/B5 terminal to MOXA RS232 port at 2050 GMT.  Set up a PuTTY connection on COM7 to monitor and capture the data to a file at 2118 GMT.  Except for this test cable being connected, MAWS is operating in its normal configuration.  Troubleshooting of wind speed spikes continues.

3/6/15

Mentor

Vendor supplied a modified setup file that will generate an SDI-12 log file.  The log will include both raw data from the sensor as well as the parsed results.  Mentor uploaded the setup file to datalogger at 1758 GMT and turned on the trace log at 1803 GMT.  New program would not do 1 minute wind speed average so it was set for 2 minute average.  A wind spike was observed on the console a few minutes later and mentor sent the corresponding files to vendor for analysis.

3/5/15

CAM

Continued troubleshooting of spikes in wind speed data.  Mentor requested the datalogger be replaced with the one from AMF2 MAWS.  Powered MAWS off at 1539 GMT and R/R *datalogger.  Also reconnected the original WMT sensor to datalogger.   Restored power at 1548 GMT.  Datalogger clock was about 8 hours ahead.  Set datalogger clock to correct time at 1652 GMT.  Noticed a W/S spike occurred at approximate 1744 GMT and again at 2100 GMT.  Vendor will supply a modified program to monitor both the raw and parsed output from the SDI-12.  Troubleshooting continues.

*Old – J3765196  *New – J3975460

2/26/15

CAM

Continued troubleshooting of spikes in wind speed data.  The test sensor that was connected to the datalogger yesterday is also producing spikes on the observation console, but still no spikes are found in the raw data from RS485 port.  Vendor requested that a new connection be made to allow parallel monitoring of the raw SDI-12 signal.  Powered MAWS off at 1910 GMT.  Picked the raw SDI-12 signal from datalogger MOD2/B5 terminal and connected to MOXA RS232 port.  Restored MAWS power at 1915 GMT.  Set up a PuTTY connection on COM7 to monitor and capture the raw SDI-12 signal to a file. 

2/25/15

CAM

No spikes have been observed in the raw data files from the wind sensor that is currently under test and streaming data via RS485 serial port.  Instrument mentor and vendor requested that the test sensor now be connected directly to the datalogger.  Powered MAWS off at 2230 GMT.  Disconnected the MAWS tower-based wind sensor from the datalogger and connected the test sensor in its place.  Restored power and RTS at 2235 GMT.  Wind data from MAWS will be invalid from this point until tower-based sensor is reconnected.

2/23/15

CAM

Instrument mentor and vendor requested that the wind sensor that was removed on 11/13 be connected to the RS485 port of the Moxa 5250 for testing.  Powered MAWS off at 2100 GMT.  Connected wind sensor SN K0630002 to RS485 port with vendor supplied service cable and to MAWS 15V power.  Mounted wind sensor on fence post near MAWS.   Restored MAWS power at 2115 GMT.  Connected directly to the sensor with Putty and configured settings as requested by vendor in order to log error information.  Starting streaming and saving data to a test file at  2140 GMT.  Will send file to vendor daily for analysis.

1/16/15

KT

The instrument was not reporting WS, WD, Temp, Hum and Press. While working with instrument mentor, logged into the computer and tried to disconnect and reconnect to the instrument. We were able to disconnect but not reconnect. Instrument mentor requested that I power cycle the instrument. Power cycled instrument at 2140 GMT. At 2145 GMT instrument came online and started reporting values. Instrument is operational at this time. RTS at 2150 GMT.

11/14/14

Mentor

Mentor reports spikes are still showing up in the wind data.  T/S continues.

11/13/14 –

11/14/14

CAM

Instrument mentor sent a new program via email and requested it be uploaded to the datalogger.  New program hopes to correct problem of missing data points for temperature, humidity and pressure.  Uploaded new program at 2151 GMT on 11/13.  SYSINFO indicated that a consistency check had failed and program was now running with errors.  The MAWS display in the BBSS room also stopped updating.  Mentor emailed two more programs, including a copy of the original, but errors still occurred when uploading.  After discussing the problem with the vendor, it was determined that the problem was due to the programs being sent via email.  Mentor used Radmin to transfer the new program to the MAWS computer and it was then copied to a laptop and uploaded to datalogger at 1829 GMT on 11/14.  This time the upload was successful and MAWS returned operational.

11/13/14

KT/MS

Instrument mentor requested the sonic wind sensor be replaced due to spikes in the data.  Lowered tower at 1810 GMT and R/R *wind sensor.  Raised tower and RTS at 1900 GMT.  The bird cage was also removed and left off at mentor’s request.

*Old – K0630002  *New – K0630006

11/6/14

JM/CM/MG

Lowered MAWS tower at 1830 GMT and installed wind sensor bird cage.  Cage is supposed to stop random wind spikes (40m/s) that have been occurring in the data.  Raised tower and RTS at 1840 GMT.

6/23/14

Mentor

Instrument mentors on site all week for *MAWS installation.  

*New – K05502  (WD80618)