Instrument Log 

2-D Disdrometer                 C1                          CF Lamont, OK

Date

Technician

Comments

5/24/16

KT

There was an acquire_iut.exe window that was on the display which caused the program to lock up. At 1228 GMT closed the error window and the program began normal operations. RTS at 1243 GMT.

5/16/16

KT

There was an acquire_iut.exe window that was on the display which caused the program to lock up. At 1348 GMT closed the error window and the program began normal operations. RTS at 1403 GMT.

5/9/16

KT

There was no signal coming from Camera B. At 1450 GMT removed and replaced the bulb for Camera B. At 1500 GMT system was on line, Camera B signal was checked and observed good. RTS at 1506 GMT.

3/3/2016

MS

Both programs had stopped running around 0659 GMT.  At 1409 GMT, closed both programs and then launched the USB server and restarted the RUN_AQUIRE_EXE. /  DV2 program.  RTS at 1424.

2/24/2016

MS

Computer was not talking to Camera A or B during PM rounds, checked bulbs and noticed camera A bulb was burnt out.  Closed out both programs at 1406.  Did not get to instrument until 1548 GMT and then started servicing instrument. Took out burnt bulb and replaced with good bulb.  After replacing Camera A bulb, hooked up laptop computer to instrument and went through the proper steps to verify that  the signals were within proper range.  Signals are now in proper range,  RTS at 1618 GMT, 2/24/2016.

2/22/2016

MS

The DV2 program was displaying wrong date and time (2/20/2016. 1859 GMT).  The RUN_ACQUIRE_EXE. camera A and B were not talking to one another.  Closed out both instrument programs, did a PCAB rest and then reset dongle and started instrument programs back up.  RTS at 1413 GMT, 2/22/2016.

2/17/16

KT

The instrument was taken off the laptop and needed to be switched over to virtual machine and needed to have Windows 7 installed. At 1415 GMT the 2DVD laptop was disconnected and was set up on the virtual machine. Instrument mentor was able to login and install Windows 7. At 1600 GMT the instrument was online and began normal operations. RTS at 1615 GMT.

2/16/2016

MS

Both instrument programs were displaying the wrong dates and times.  The RUN_ACQUIRE_EXE. was showing a date 2/14/2016 and a time of 2119 GMT  2/14/2016.  The DV2 programs was showing a date 2/14/2016, and a time of 2059 GMT  2/14/2016,   Closed out both programs and restarted them at 1444 GMT, 2/16/2016 and RTS at 1459 GMT, 2/16/2016.

2/12/2016

MS

Both instrument programs were displaying the wrong date and time.  RUN_ACQUIRE_EXE. was displaying 2/11/2016, 2018 GMT.  The DV2 was displaying 2/11/2016, 1959 GMT.  Closed down both instrument programs and restarted them at 1634.  RTS at 1649 GMT, 2/12/2016.

2/11/2016

MS

Both instrument programs were displaying the wrong date and times.  The RUN_ACQUIRE_EXE. was displaying 2/10/2016,  20:15 GMT.   The DV2 was displaying 2/10/2016,  20:15 GMT.  Closed out both instrument programs and restarted them at 1413 GMT, 2/11/2016.  RTS at 1428 GMT, 2/11/2016.

2/8/2016

MS

The RUN_ACQUIRE_EXE. program was displaying wrong date and time.  It was showing 2/6/2016, 2125 GMT.  Also the DV2 program was displaying the wrong date and time, is was showing 2/6/2016, 2059 GMT.  Restarted both instrument programs at 1409 GMT, 2/8/2016.  RTS at 1424 GMT, 2/8/2016.

2/2/2016

MS

Both programs were on the wrong date and time.  The RUN_ACQUIRE_EXE. was on 2/2/2016, 01:37 GMT.  The DV2 was displaying 2/2/2016, 00:59 GMT.  Both programs should have been displaying 14:58:00 GMT, 2/2/2016.  Also a pop up window is coming up saying,  Internal Error.  Ignored the Internal Error and closed out both instrument programs at 1458 GMT, and then restarted them back up.  RTS 1513 GMT, 2/2/2016.

2/1/2016

MS

Instrument had wrong date and time displayed.  Time and date was 1/29/2016, 1821 GMT.  Restarted both the RUN_ACQUIRE_EXE. and the DV2 program at 1508 GMT 2/1/2016. RTS 1523 GMT, 2/1/2016.

1/29/2016

MS

Noticed that both programs had wrong date and time displayed,  instruments were displaying 1/28/2016, 1610 GMT.  Closed out both programs at 1420 GMT, 1/29/2016.  RTS at 1435 GMT.

1/28/2016

MS

Noticed that the DV2 program was displaying the wrong date and time.  It was displaying 1606 GMT 1/27/2016, which at the time was 1458 GMT, 1/28/2016.  Closed out DV2 program along with the RUN_AQUIRE_EXE program, restarted both programs at 1458 GMT, 1/28/2016.  RTS at 1513 GMT, 1/28/2016.

1/22/2016

MS

Signal was low in on Camera A.  Shutdown instrument at 2015 GMT, started instrument back up.  Stopped RUN_ACQUIRE.EXE and DV2 programs, reset cameras using PCAB_Reset.bat in CAM TOOLS folder. Opened TELA.BAT and TELB.BAT, entered proper command to view signals.  Adjusted Camera A bulb to its proper signal.  RTS 2059 GMT, 1/22/2016.

1/21/2016

MS

Could not Radmin into instrument during PM rounds.  Power cycled the instruments computer at 1523 GMT 1/21/2016,  RTS at 1538 GMT 1/21/2016.

1/11/2016

MS

The Date and Time were wrong on both programs, instrument was displaying Jan 10,2016   0739 GMT.  Closed out both programs and restarted them at 1409 GMT, 1/11/2016,  RTS at 1424 GMT 1/11/2016.

12/31/15

JEM

The central facility experienced an ice storm and the 2DVD had not resumed data collection.  Found the 2DVD laptop powered off.  Powered the laptop on at 1718 GMT and normal operation and data collection resumed at 1720 GMT.  RTS @1720 GMT.

12/15/15

MS

Computer needed to be restarted following scheduled software and security patch updates.  At 1404 GMT computers were updated and rebooted by the IT department, some data might be lost.

12/14/15

MS

Noticed that the RUN_AQUIRE.EXE & the  DV2 program displayed the wrong date & time.  Closed out both programs and restarted at 1407 GMT 11/14/15.  RTS 1422 GMT 11/14/15.

11/30/15

MS

Both of the instruments programs were displaying the wrong date and time, plus the programs had stopped running as of 0656 GMT, 11/28/2015.  Closed out both programs and restarted them at 1425 GMT 11/30/2015.  RTS at 1438 GMT 11/30/2015.

11/17/15

MS

A 7 hour power outage starting at 0700 GMT and power was returned at 1435 GMT, 11/17/2015. Instrument was down. During that time some data might be lost?  Started program back up and RTS at 1639 GMT, 11/17/2015.

10/22/15

MS

The Run_Aquire.EXE and DV2 were displaying wrong dates and times.  Camera B's bulb was burnt out.  Started replacing Camera B's bulb and restarted both programs at 1454 GMT, Got camera B's signal between 100-240 and restarted both programs at 1509 GMT.  RTS 1510 GMT.

10/19/15

MS

DV2 program was not updating, showing the wrong date.  Checked the 3sec directory and found that it had too many files.  Renamed the 3sec directory as 3sec_bkup_10.19.15 and created a new 3sec directory at 1339 GMT.  Restarted programs and RTS at 1339 GMT.

10/15/15

MS

Run Acquire program was not running at 1336 GMT.  Closed program at 1336 GMT and restarted the program, at 1351 GMT the system was online and operational.  RTS at 1351 GMT.

9/18/15

KT

The computer program was not running. At 1320 GMT closed the program window and restarted the program. At 1330 GMT the system was online and operational. RTS at 1335 GMT.

8/6/15

KT

The computer program appeared locked up. At 1533 GMT restarted the Run Acquire and Run 2 DVD programs. At 1537 GMT computer was online and operational. RTS at 1548 GMT.

7/27/15

MS

The RUN_ACQUIRE.EXE program was not running at 1309 GMT.  Restarted the RUN_ACQUIRE.EXE program at 1309 GMT.  RTS at 1324 GMT.

7/20/15

MS

The RUN_ACQUIRE.EXE program was not running and the date/time was off on the DV2 program, it was stuck on 7/17/2015.  Reset both programs and that did not work.  At 1553 GMT during inspection found that lamp B was burnt out and needed to be replaced.  Removed and replaced bulb, rebooted computer and system is online and operational.  RTS at 1608 GMT.

7/14/15

MS

The RUN_ACQUIRE.EXE program was not running and the DV2 time was of by one hour.  Closed out both programs and reset them at 1341 GMT.  RTS at 1359 GMT.

7/10/15

MS

DV2 program was not updating, showing a date of Thursday July 9 at 08:28:17.  Checked 3sec directory and found it had too many files.   Renamed 3sec directory as 3sec_bkup_7.10.15 and created a new 3sec directory.  Restarted programs and RTS at 1328 GMT.

7/9/2015

MS

The DV2 program time was off.  Reset both RUN_ACQUIRE.EXE  and the DV2 program at 1307 GMT.  RTS at 1322 GMT.

7/7/2015

MS

RUN_ACQUIRE.EXE program was not running correctly and the date/time was off on the DV2 program.  Reset both programs (RUN_ACQUIRE.EXE, DV2) at 1408 GMT.  RTS at 1523 GMT.

7/6/15

CAM

DV2 program window was not updating, showing a date of Friday, July 3.  Checked 3sec directory and found it contained over 19,000 files.  Renamed 3sec directory as 3sec_bkup_7.6.15 and created a new 3sec directory.  Restarted programs and RTS status O.K. at 1425 GMT.

6/30/2015

MS

The RUN_ACQUIRE.EXE program had stopped running.  Reset the RUN_ACQUIRE.EXE program at 1301 GMT.  RTS at 1316 GMT.

6/18/2015

MS

The DV2 program was not keeping the correct Date and time due to a full 3 second Data Directory.  Created a new 3 second Data Directory at 1301 GMT, Restarted both programs, the RUN_ACQUIRE.EXE and the DV2.   RTS at 1316 GMT.

6/17/2015

MS

The time is off on the DV2 program at 1258 GMT.  Reset the RUN_ACQUIRE.EXE program and DV2 program and RTS at 1313 GMT.

6/10/2015

MS

Due to a scheduled power outage the 2DVDisdro program was shut down at 1351 GMT.  Restarted 2DVDisdro program at 1543 GMT, RTS at 1558 GMT.

6/8/2015

MS

RUN_ACQUIRE.EXE program was not running. Restarted the RUN_ACQUIRE.EXE and the DV2 program as well at 1320 GMT.  RTS at 1335 GMT.

6/5/2015

MS

The RUN_ACQUIRE.EXE program was not running and the DV2 date, time was not correct.  Shutdown the DV2 program at 1334 GMT.  Restarted both the RUN_ACQUIRE_EXE and the DV2 programs.  RTS 1349 GMT.

6/4/2015

MS

Shutdown 2DVDisdro program at 1314 GMT due to a scheduled power outage.  Restarted 2DVDisdro program at 1843 GMT.  RTS 1858 GMT.

6/1/15

MS

System was locked up at 1331 GMT.  Did a hard reboot to the 2DVD at 1346 GMT.   RTS at 1346.

5/26/15

KT

The Run Acquire and Run 2DVD programs were not running. Restarted the two programs. System began normal operations. RTS at 1324 GMT.

5/22/15

MS

Programs for the RUN_ACQUIRE.EXE and the DV2 had stopped at 1334 GMT.  Reset both programs and RTS at 1449 GMT.

5/20/15

MS

The RUN_ACQUIRE.EXE program was not running at 1332 GMT.  Restarted the RUN_ACQUIRE.EXE program and RTS at 1347 GMT.

5/18/2015

MS

The program RUN_ACQUIRE.EXE and the DV2 were not running and out of date.  Restarted both programs and RTS at 1348 GMT.

5/12/15

MS

The program RUN_ACQUIRE.EXE was not running at 1313 GMT 5/12/2015.  Restarted both programs, RUN_ACQUIRE.EXE and the DV2 and RTS at 1528 GMT.

5/11/15

MS

The RUN_ACQUIRE.EXE and the DV2 program had stopped running at 1304 GMT.  Files were full in the DV2.  Reset the RUN_ACQUIRE.EXE,  reset the cameras and restarted the program.  Moved files from DV2 into a new file so the program could start collecting again.   RTS 1329 GMT 5/11/2015.

5/1/2015

MS

The RUN_ACQUIRE.EXE and the DV2 program had stopped running.

Reset the RUN_ACQUIRE.EXE and the DV2 program.   RTS 1329 GMT.

4/27/15

MS

The RUN_ACQUIRE.EXE and the DV2 program had stopped running at 1330 GMT.  Restarted both programs at 1345 GMT.

4/23/2015

MS

The RUN_ACQUIRE.EXE and the DV2 programs were not running due to burned out Light Bulb B.  At 1258 GMT closed out and restarted both programs, it didn't take so at 1750 GMT changed out Light Bulb B.  Restarted both RUN_ACQUIRE.EXE, DV2 programs at 1809 GMT.  RTS 1809 GMT.

4/20/2015

MS

The RUN_ACQUIRE.EXE and the DV2 program was not running at 1415 GMT.  Closed programs and reset cameras and restarted the program at 1430 GMT.  RTS 1430 GMT.

4/17/2015

MS

The RUN_ACQUIRE.EXE program was not running at 1330 GMT.  Restarted both programs RUN_ACQUIRE.EXE and the DV2:OEU047 at 1345 GMT.  RTS at 1345 GMT.

4/21/15

CAM

The computer needs to be rebooted following scheduled software and security patch updates.  Stopped programs at 1833 GMT and rebooted computer. Restarted and RTS at 1835 GMT.

3/30/2015

MS

Programs for the RUN_ACQUIRE.EXE and the DV2: OEU047 were not responding at 1342 GMT.  Restarted both programs at 1342 GMT,  RTS at 1357 GMT.

3/27/15

PD

Last file shown on DV2 program was for 3/26/15 at 1948 GMT.  Run_Acquire program is open but has "Calibration mode is not set" repeating.  Closed programs, reset cameras and restarted program.  Normal operations resumed.  RTS at 1314 GMT.

3/23/15

MS

The Run_Acquire.Exe and the DV1: OEU047 was not running.  Stopped program at 1530 GMT and restarted at 1545 GMT.

3/9/15

PD

Acquire_iut.exe memory could not be read error message is shown.  Cleared error, reset cameras and restarted programs.  RTS at 1317 GMT.

2/19/15

KT

Computer IT department uploaded patches and updates to the instrument computer. The computer needed to be rebooted. At 1835 GMT the computer was rebooted. At 1840 GMT the computer came online and was operational. RTS at 1850 GMT.

1/28/15

KT

SDS reported no files. Could not log into instrument. At 1710 GMT found the computer off. At 1714 GMT power cycled the computer. The computer came online and began normal operations. RTS at 1725 GMT.

1/21/15

KT

Could not log into the computer using RADMIN. At 1410 GMT power cycled the computer. At 1416 GMT the computer came online and began normal operations. RTS at 1425 GMT.

1/16/15

KT

The computer was locked up. At 1620 GMT rebooted the computer. At 1625 GMT the computer came online and the programs began running. System is online and operational. RTS at 1635 GMT.

1/12/15

CAM

DV2 program window was not updating, showing a date of Friday, Jan 9.  Checked 3sec directory and found it contained over 84,000 files.  Renamed 3sec directory as 3sec_bkup_1.12.15 and created a new 3sec directory.  Restarted programs and RTS status O.K. at 1551 GMT.

12/18/14

KT

There was no communications with the instrument computer. At 1625 GMT the computer was found off. Powered the computer on. At 1630 GMT the computer came online and began normal operations. RTS at 1640 GMT.

12/2/14

KT

There was a calibration mode not set error. After rebooting the computer there was no change. During inspection found that lamp B bulb was burnt out and needed to be replaced. Removed and replaced bulb. Rebooted computer, system is online and operational. RTS at 1450 GMT.

12/1/14

KT

The computer was locked up with 182 errors. The UPS alarm was sounding. At 1600 GMT removed and replaced the UPS and cleared the error messages. System is online and operational. RTS at 1615 GMT.

11/25/14

MS

The program on the Run AQUIRE.EXE and the DV2 were not running correctly.  Power cycled the 2DVD and adjusted the signals for camera B.   RTS at 1511 GMT.

11/24/14

MS

The program on the Run AQUIRE.EXE and the DV2 were not running. Stopped and restarted both programs as well as tried to adjust the signal for camera B.  Still have a flat line for camera B.

11/20/14

PD

Run Acquire shows Calibration is not set.  Program stopped at 0859 GMT.  Closed programs, reset cameras, restarted programs.  RTS at 1424 GMT.

11/17/2014

MS

The RUN_ACQUIRE.EXE and the DV2 program was not running at 1419 GMT.  Closed out both programs and restarted them, RTS at 1434 GMT.

11/10/14

MS

Program was not running at 1414 GMT.  Closed out the Run Aquire EXE and the DV2 program and then restarted both programs on the 2DVD at 1429 GMT.

11/5/2014

MS

Noticed at 1552 GMT that the 2DVD had error windows up on screen.  Closed out error windows and then restarted program at 1607 GM

10/27/14

MS

Program for the Run Aqiure.EXE was not responding.  Stopped and restarted The Run Aqiure EXE and the DV2:OEUO47 program at 1250 GMT.

10/20/14

CAM

Instrument mentor (DQPR-4300) requested that the video signal levels be checked and to make sure they are between 100-200 counts.  Checked signal levels at 1735 GMT.  Camera B level was fully within the 100-200 range. Camera A level was above 200, approximately 220, at one end.  Adjusted camera A lamp holder for signal level between 100-200.  RTS at 1805 GMT.

10/14/14

CAM

No data had been collected from 2DVD since 0614 on 10/10.  Unable to access 2DVD computer remotely.   Local computer check found several acquire_iut.exe application error windows open stating that an instruction had referenced memory at an address that could not be read.  Cleared errors and closed programs at 1400 GMT.  Rebooted computer and RTS at 1405 GMT.

10/8/14

CAM

Data collection failed again this morning for 2DVD.  Checked status remotely and found DV2 program window was not updating.  Checked 3sec directory and found there were 99,891 files dating back to 10/4.  Renamed 3sec directory as 3sec_bkup_10.8.14 and created a new 3sec directory.  Restarted programs and RTS status O.K. at 1309 GMT.

10/7/14

CAM

Data collection failed for 2DVD this morning.  Message displayed stating acquire_iut.exe had encountered a problem and needed to close.  Run_aquire.exe showed it had skipped several duplicate data files.  Closed programs and restarted.  RTS at 1301 GMT.

9/25/14

CAM

Data collection failed for 2DVD this morning.  Remote status check found an application error message displayed for acquire_iut.exe.  The error indicated an instruction had referenced memory at 0x0000028c that could not be read.  Unable to clear the error remotely.  Accessed computer locally and cleared the error.  Restarted programs but DV2 program would not update.  Checked for data files and found there were over 11,000 files in the 3sec directory.  Renamed the current 3sec directory as 3sec_bkup_9.25.14 and created a new 3sec directory.  Restarted programs and both began updating as they should and creating new data files.  RTS at 1235 GMT.

9/24/14

CAM

RUN_ACQUIRE showing calibration mode is not set.  Checked video signal levels and both were fine.  Restarted programs but RUN_ACQUIRE would not update.  Rebooted computer and RTS status O.K. at 1300 GMT.

9/18/14

CAM

2D Video Disdrometer computer was updated with the latest patches and needed to be rebooted.  Stopped program at 1601 GMT and rebooted computer.  Restarted and RTS at 1604 GMT.

9/15/14

CAM

No data had been collected from 2DVD since 0614 GMT on 9/10.  Remotely checked video signals and found signal B was flat-lined.  Checked bulb B and found it was loose in its socket and not lit.  Reinserted bulb fully in socket and it then lit.  Adjusted bulb for best video signal.  Restarted programs and RTS at 1310 GMT.

9/8/14

CAM

No data had been collected from 2DVD since 0614 GMT on 9/7.  Remote check found RUN_ACQUIRE showing calibration mode is not set.  Checked video signal levels and both were fine.  Restarted programs and RTS status O.K. at 1218 GMT.

8/13/14

MG

Instrument was not updating and time and date were stuck on 21:35 08-12-14.  Rebooted computer and will monitor for the time being.

8/4/14

CAM

No data had been collected from 2DVD since 7/25.  Logged in remotely and found Run_Acquire showing an error: Unable to process input data transfer file.  DV2 program was not updating and showed: Looking for OEU data: c:/2dvddata/3sec/0*.*"  Checked for data files and found there were 251,328 files in the the 3sec directory.  Renamed the current 3sec directory as 3sec_bkup_8.4.14 and created a new 3sec directory.  Restarted programs and both began updating as they should and creating new data files.  RTS at 1447 GMT.

7/28/14

CAM

No data had been collected from 2DVD since 7/25.  Remote check found RUN_ACQUIRE showing calibration mode is not set.  Attempted to check video signals but unable to communicate with cameras.  Power cycled both cameras and communications restored.  Video signals checked out ok. Restarted programs and RTS status O.K. at 1214 GMT.

6/17/14

CAM

 

Dialog box displayed stating acquire_iut.exe had encountered a problem and needed to close.  Closed programs and rebooted computer at 2210 GMT.  RTS status O.K. at 2215 GMT.

6/17/14

CAM

Run_acquire shows 2 errors:  Unable to Process Input Data Transfer File 1403007102.b.cam and Empty Frame With Negative Time Jump – Drop.  Restarted programs at 1220 GMT.  Remote check at 1300 GMT found dialog box open stating Acquire_iut Encountered a Problem and Needs to Close.  Closed programs and restarted at 1303 GMT.

6/16/14

CAM

There were 6 error messages displayed stating acquire_iut.exe had encountered a problem and needed to close, even though run_acquire and DV2 appeared to be running and current.  Closed programs and rebooted computer at 1203 GMT.  RTS status O.K. at 1206 GMT.

6/12/14

CAM

Message displayed stating acquire_iut.exe had encountered a problem and needed to close, even though run_acquire appeared to be running and current.  Closed programs and restarted at 1213 GMT.  RTS status O.K. at 1215 GMT.

6/10/14

KT

The 2DVD program needed to be restarted.  At 2025 GMT restarted the 2DVD program. Program still did not start up. After further inspection Camera B bulb was out and needed to be changed. Removed and replaced Camera B bulb. RTS at 2045 GMT.

6/9/14

CAM

No data had been collected from 2DVD since 0614 GMT on 6/7.  Remotely checked video signals and found signal A was flat-lined.  Checked bulb A and found it was loose in its socket and not lit.  Reinserted bulb fully in socket and it then lit.  Adjusted bulb for best video signal.  Restarted programs and RTS at 1307 GMT.

5/27/14

CAM

No data had been collected from 2DVD since 0614 on 5/25.  Logged in remotely and found several acquire_iut.exe application error windows open stating that an instruction had referenced memory at an address that could not be read.  Cleared errors and closed programs at 1250 GMT.  Restarted programs and RTS at 1252 GMT.

5/19/14

MG

Run acquire program was flashing with Error message.  Rebooted computer at 1446 GMT. Everything looks good at 1500

5/15/14

CAM

No data had been collected from 2DVD since 5/13.  Logged in remotely and found 2DVD program showing there were only 4 files found, 5 needed.  Run_Aquire program was not updating.  Checked camera A and B video signals and both were within range.  Restarted both programs with no change in status.  Rebooted computer and this time programs started as they should.  RTS at 1226 GMT.

5/12/14

JEM

The 2DVD froze up at 1033 GMT on 5/11/14.  Rebooted the 2DVD computer @1423 GMT.  Status observed normal @1428 GMT.  RTS @1430 GMT.

5/6/14

KT

The Camera programs were not running. At 1330 GMT reset both Camera A and Camera B. Then started programs. RTS at 1345 GMT.

4/15/14

CAM

Message displayed stating acquire_iut.exe had encountered a problem and needed to close.  Run_aquire.exe shows it was unable to process several different input data transfer files.  Closed programs and restarted.  RTS status O.K. at 1214 GMT.

4/3/14

PAD

Run_Acquire shows; Calibration mode is not set.  Reset cameras and restarted programs.  RTS at 1302 GMT.

3/31/14

PAD

Run_Acquire shows; Calibration mode is not set.  Reset cameras and restarted programs.  RTS at 1222 GMT.

3/21/2014

PAD

Run_Acquire program shows: Calibration mode is not set.  Reset cameras and restarted programs.  RTS at 1352 GMT.

3/13/14

PAD

Run Acquire program shows "Calibration mode is not set".  Reset cameras and restarted Run Acquire and 2DVD programs.  RTS at 1346 GMT.

3/11/14

KT

The signal for camera A needed to be adjusted. At 1300 GMT adjusted the signal for camera A. At 1307 GMT reset both camera A and B. RTS at 1315 GMT.

12/26/2013

MS

Noticed at 1345 GMT that the program was not running on the 2DVDisdro. Power cycled cameras on the 2DVDisdro at 1406 GMT. Program is now up and running

12/3/13

CAM

Message displayed stating acquire_iut.exe had encountered a problem and needed to close, even though run_acquire appeared to be running and current.  Closed programs and restarted at 1630 GMT.  RTS status O.K. at 1632 GMT.

11/4/13

MS

Light bulb for camera B was burned out. At 1910 GMT removed and replaced light bulb, rebooted computer. RTS at 1925 GMT.

10/2/13

CAM

No data files had been collected since 0616 GMT on 9/30.  Check of instrument found Run_acquire showing “Calibration Mode is Not Set”.  Checked camera signal levels and found signal B was flat lined, indicating the bulb was out.  Opened instrument and found bulb B was out, but only because it was loose in the socket.  Secured bulb in the socket and adjusted for best signal level.  Restarted programs and RTS at 1315 GMT.

9/27/13

ML

The computer monitor had multiple error messages displayed in the screen.    Power cycled the 2DVDisdro computer @1530 GMT.  The computer then appeared to be running properly and scrolling data.  RTS 1535 GMT.

9/5/13

CAM

No data had been collected since 0614 GMT on 9/3.  Logged in remotely and found message stating acquire_iut.exe had encountered a problem and needed to close, even though run_acquire appeared to be running and current.  Closed program and restarted at 1310 GMT.  Run_acquire restarted ok, but DV2 program showed "Looking for OEU data: c:\2dvddata\3 sec\0*.*".  Checked 3sec directory and found it contained 66,164 files.  Renamed the current directory to 3sec_bkup6 so all of the original files are still present and created a new 3sec directory. Restarted both programs and RTS status O.K. at 1321 GMT.

8/29/13

CAM

Remote status check found error message displayed: Acquire_iut.exe has encountered a problem and needs to close.  Closed error and attempted to restart programs, but Run_acquire showed “Calibration Mode is Not Set”.  Checked camera signal levels and found A signal was exceeding the maximum limit on the right side.  Adjust bulb A to bring signal level within min and max limits.  Restarted programs and RTS at 2030 GMT.

8/29/13

CAM

No data files had been collected since 0614 GMT on 8/27.  Check of instrument found Run_acquire showing “Calibration Mode is Not Set”.  Checked camera signal levels and found both had good shapes and min/max values, but signal B had random narrow spikes that dipped below the min value.  Opened lid and found mud daubers had built nests inside the enclosure and there were several small pieces of hardened mud within the slit openings.  Cleaned slits and removed mud dauber nests.  Used canned air to clean mirrors and camera lenses.  Rechecked camera signal levels and they were normal.  Restarted programs and RTS at 1256 GMT.

7/1/13

CAM

No data had been collected since 0614 GMT on 6/27.  Logged in to computer remotely and found 2 Windows errors stating that drive A could not reconnect to \\192.168.1.11\data and drive B could not reconnect to \\192.168.1.12\data.  T/S found the 48VDC power supply had no output and so the instrument was without power.  Power cycled power supply and the output returned and instrument powered on at 1400 GMT.  Checked video signals and confirmed they were within the acceptable ranges.  Rebooted laptop and restarted programs.  RTS status O.K. at 1407 GMT. 

6/18/13

CAM

DQPR 3771 indicates data is still not being received from 2DVD, even since the lamp was changed on 6/13.  Checked video signals and found A signal was exceeding the maximum limit on the right side.  Adjusted lamp holder to bring signal within limits.  Restarted programs and RTS at 1242 GMT.

6/13/13

CAM

No data files had been collected since 0600 GMT on 6/11.  Check of instrument found Run_acquire showing “Calibration Mode is Not Set”.  Checked camera signal levels and A signal was flat lined, indicating the bulb was out.  Replaced A bulb and adjusted for best signal.  Restarted programs and RTS at 1252 GMT.

5/28/13

CAM

Error message displayed: Acquire_iut.exe has encountered a problem and needs to close.  Errors also shown in Run_Acquire window: Unable to process input data transfer file 1369743366.  Closed programs at 1218 GMT and restarted. RTS status O.K. at 1219 GMT.

5/20/13

CAM

Check of instrument found Run_acquire showing “Calibration Mode is Not Set”.  Checked video camera signal levels and A signal was exceeding the maximum limit.  Adjusted lamp holder to bring signal down within the acceptable range.  Restarted programs and RTS at 2230 GMT.

5/20/13

CAM

No data had been collected from 2DVD since 0620 GMT on 5/18.  Run_Acquire indicated cal mode not set.  Checked camera signal levels and B signal was flat lined, indicating the bulb was out.  Replaced B bulb and adjusted for best signal.  Restarted programs and RTS at 1300 GMT.

5/13/13

CAM

Error message displayed: Acquire_iut.exe has encountered a problem and needs to close.  Errors also shown in Run_Acquire window: Unable to process input data transfer file 1368468003.b.cam.  Closed programs at 1838 GMT and restarted. RTS status O.K. at 1839 GMT.

3/28/13

PAD

Last file in Run_Acquire was on 3/27/13 at 2240 GMT.  No error messages are shown.  Closed programs and reset cameras.  Restarted Run_Acquire and DV2 programs.  Programs started correctly.   RTS at 1231 GMT.

1/29/13

PAD

Run_Acquire program shows "Calibration mode is not set".  Last DV2 file was at 1236 GMT.  It is raining at this time.  Exited programs and reset cameras.  Restarted programs and Run_Acquire program indicated it was detecting rain then locked up after 15 seconds.  Stopped/restarted programs.  Programs started correctly.  RTS at 1413 GMT.

1/24/13

PAD

Last file shown on DV2 program was on 1/23/13 at 2059 GMT.  Calibration Mode is not set is shown repeatedly on Run_Acquire program.  Reset cameras and restarted programs.  RTS at 1454 GMT. 

1/22/13

PAD/KT

At 1701 GMT, observed Run_Acquire program not running.  Last file on DV2 was on 1/21/13 at 0622 GMT.  Program failed to restart.  Signal graphs show side A reading flatlined.  Inspection of instrument found side A bulb had burnt out.  At 1941 GMT, shut down instrument and R/R side A bulb.  Cleaned mirrors and Fresnal lenses and adjusted both side A and B lamps.  Started programs.  RTS at 2016 GMT.

1/15/13

CAM

Error message displayed: Acquire_iut.exe has encountered a problem and needs to close.  Errors also shown in Run_Acquire window: Unable to process input data file.  Closed programs at 1340 GMT.  Rebooted computer and RTS status O.K. at 1343 GMT.

1/14/13

KT

Camera A signal was low and needed to be adjusted. At 1950 GMT made adjustments to bulb A and then rebooted both cameras after completion. RTS at 2015 GMT.

1/11/13

KT

The computer was running but the values for the mirrors were incorrect. At 1510 GMT rebooted computer. When the computer came online the mirror values were correct. System performing normal operations.

12/11/12

CAM

No files had been collected from 2DVD since 0614 on 12/9.  Remote status check found an error message window open that displayed: an error occurred while reconnecting B to \\192.168.1.12\data.  Closed error message and programs and rebooted computer.  Programs started normally.  RTS at 1320 GMT.

12/10/12

KT

The 2DVDisdrometer program was not running. At 1513 GMT rebooted computer. RTS at 1528 GMT.

11/28/12

CAM

2DVD was not generating data. No files collected since 11/26.  DV2 program heading displayed: Looking For OEM.  Message in program body: only 4 files found, but need 5.  There was a Windows error window open that displayed: an error occurred while reconnecting B to \\192.168.1.12\data. Closed programs and checked video signals.  Both were fine.  Attempted to start DV2 and Run_Acquire with no change in status.  Rebooted computer and programs started normally.  RTS at 1328 GMT.

10/29/12

KT

The 2DVDisdrometer program was not running.  At 1555 GMT changed the bulb out on Camera "B", adjusted bulb as needed to place signal between upper and lower threshold of signal graph. RTS at 1610 GMT.

10/16/12

CAM

Error message displayed: Acquire_iut.exe has encountered a problem and needs to close.  Errors also shown in Run_Acquire window: Unable to process input data file.  Closed programs at 1240 GMT.  Checked video signals of both cameras and they were ok.  Reset cameras and restarted software.  RTS at 1243 GMT.

10/15/12

CAM

2DVD is not generating data.  No files collected since 10/8.  RUN_ACQUIRE program shows calibration mode not set.  Checked video signal and found right side was below low limit.  Adjusted bulb and side mirror to get signal between limits.  Signal graph does not have the normal shape, but is within limits.  Restarted software and RTS at 1550 GMT.

8/27/12

PAD

Last file shown on Run_Acquire program was at 0918 GMT on 8/26/12.  Checked signal graphs for 8/26/12.  Signals were within limits.  Reset cameras and restarted programs.  RTS at 1245 GMT.

8/22/12

PAD

Last measurement taken was on 8/20/12 at 1930 GMT.  Cal mode is not set is shown in Run_Acquire program.  Checked signal graphs for both cameras and they are within limits.  Reset cameras and restarted programs.  RTS at 1407 GMT.

8/20/12

PAD

Run_Acquire program shows cal mode is not set.  Last measurement was taken at 0710 GMT.  Troubleshooting found lamp A bulb burnt out.  R/R bulb at 1335 GMT.  Adjusted lamp A bulb after install to get signal between low and high limits. Instrument was restarted at 1400 GMT.   At 1722 GMT, found program had stopped.  Right side of signal graph for lamp A was exceeding max limit.  Adjusted lamp A bulb.  Program started correctly.  RTS at 1747 GMT.

7/11/12

CAM/KT

Mentor requested a plane distance measurement be done.  Connected laptop directly to instrument at 1750 GMT and dropped 10mm spheres until at least 5 were detected in the 3 required corners.  Ran the do_plane batch file and obtained three new distance values and saved them to acquire.par.  Dropped at least 30 each of 2, 4 and 6mm spheres and saved results for mentor to review.  Reset cameras and restarted software.  RTS at 1912 GMT.

Old values:   HBL = 5.8525  HBR = 5.3694  HFR = 5.1603

New values: HBL = 5.7716  HBR = 5.1888  HFR = 4.7743

6/21/12

PAD

Remotely accessed computer at 1255 GMT.  Several Acquire_iut.exe messages were shown, maybe 100 of them.  Cleared messages and observed last DV2 file was at 0958 GMT.  No frames for either camera.  Run_Acquire status shows : error, unable to process input data file transfer file 1340283276.  a. cam. Retrieved frame is invalid.  Reset cameras and restarted programs.  Programs started correctly and are showing values indicating it is measuring current precipitation.  RTS at 1310 GMT.

6/15/12

PAD

Remotely accessed computer and found no frames or Bytes shown for camera A.  Last DV2 file was at 0558 GMT.  Reset cameras and started Run-Acquire and DV2 programs.  RTS at 1253 GMT.

6/4/12

PAD

Last SDS collection was at 1828 GMT.  Lamp B bulb was replaced earlier today.  At 2116 GMT, remotely accessed computer and Run_Acquire program showed "calibration mode is not set".  Connected with cameras and found right side of camera A signal graph was above limit of 240.  Connected laptop directly to instrument and adjusted side A bulb.  Returned laptop to shelter and restarted program.  RTS at 2156 GMT.

6/4/12

KT

DMF collections stopped on instrument on 6/4/12 at 0500. During inspection Lamp B bulb was found burnt out. Removed and replaced bulb. Status OK.

5/30/12

CAM

DSView page showed last successful collection was at 0614 on 5/28.  Remotely accessed computer and observed the following error:  DWWIN.EXE - Application Error.  The application failed to initialize properly (0XC0000142).  Click  OK to Terminate Application.  Unable to clear error by clicking on OK.  Restarted computer at 1314 GMT.  Run_Acquire and DV2 programs started normally.  RTS at 1317 GMT.

4/30/12

PAD

 Run_Acquire shows zero frames for camera A.  Last file shown in DV2 program was at 0359 GMT.  Stopped programs and reset cameras.  Restarted Run_Acquire and DV2 programs.  Programs started correctly.  RTS at 1351 GMT.

4/16/12

PAD

Remotely accessed computer at 1334 GMT and error message was shown on login page:  The instruction at "Ox692f91ff" referenced memory at "OxOaOc3068", memory could not be read.  Cleared error message and logged on computer.  DV2 last file was on 4/14/12 at 0510 GMT.  There were about 150 Acquire_iut.exe_Application errors.  Cleared errors, shut down DV2 and Run_Acquire programs.  Reset cameras and restarted programs.  Programs started correctly.  RTS at 1349 GMT.

4/3/12

PAD

Last SDS collection was at 0500 GMT.  Unable to remotely access computer.  Laptop was removed from shelter to connect directly with instrument on 4/2/12 and was power supply was not reconnected after returning to shelter.  Plugged power supply into laptop.

4/2/12

PAD

Run_Acquire and DV2 programs have stopped three times since 3/21/12.  Each time, last time stamp on DV2 file ended at 59 minutes after the hour.  Consulted with mentor who found the signals from both A and B lamps are coming very close if not exceeding high limit of 240.  Lamp A signal is indicating hourly movement shown on VIEW_VID.EXE mostly on right side of graph and maybe reaching upper limit.  Lamp B signal is steadier but small spike in middle of graph maybe reaching upper limit.  Mentor recommends adjusting lamps to move signal further away from upper limit.  Stopped programs at 2007 GMT and adjusted both A and B bulbs.  Restarted programs.  RTS at 2032 GMT.

4/2/12

PAD

Last file shown on DV2 program is for 3/30/12 at 1659 GMT.  Stopped DV2 and Run_Acquire programs.  Reset cameras and restarted programs.  RTS at 1253 GMT.

3/29/12

PAD

Last file shown on DV2 was on 3/28/12 at 1959 GMT.  Run_Acquire and DV2 programs are not updating.  Closed programs, reset cameras and restarted programs.  RTS at 1305 GMT.

3/27/12

PAD

Last file shown on DV2 was on 3/26/12 at 1959 GMT.  Run_Acquire and DV2 programs are not updating.  Closed programs, reset cameras and restarted programs.  RTS at 1404 GMT.

3/26/12

PAD

Last SDS collection was on 3/25/12 at 0500 GMT.  Last file shown on DV2 program was on 3/21/12 at 1859 GMT.  Run_Acquire program shows "calibration mode is not set". Found lamp A bulb had burnt out.  R/R bulb and adjusted signal after restarting instrument.  RTS at 1626 GMT.

2/2/12

PAD

Run acquire does not show any data.  DV2 show 2/1/12 at 2338 GMT as the last data.  Closed programs and reset cameras.  Started Run acquire and DV2 programs.  Both programs are now running normally.  RTS at 1329 GMT.

1/18/12

PAD/KT

Last SDS collection was on 1/16/12 at 0500 GMT.  Bulb B is burnt out and needs to be replaced.  Shut down instrument and R/R bulb.  Powered up system and connected laptop directly to instrument.  Brought up signal graph and adjusted bulb as needed.  RTS at 1925 GMT.

12/21/11

PAD

Run_Acquire program has sporadically been resetting every 1.5 minutes.  Mentor suspects Camera A signal being low may be responsible for erratic behavior.  Mentor requests Camera A bulb or illumination mirror adjusted to try to get signal higher above lower threshold.  Previous attempts at adjusting bulb did not improve signal graph.  Cleaned all mirrors, camera, and bulb, and adjusted illumination mirror and bulb as needed to improve signal graph.  Although signal graph is not as smooth as Camera B, it is well within the lower and upper threshold limits.  Started programs.  RTS at 1933 GMT.

12/20/11

PAD

Error shown on login page:  Acquire_iut.exe- Application error.  "The memory could not be read".  DV2 last shows data for 12/19/11 at 1932 GMT.  Cleared error message and logged on computer.  About 50 Run_Acquire Microsoft errors are shown.  Cleared errors and reset cameras.  Programs restarted correctly.  RTS at 1332 GMT.

12/15/11

PAD

Remotely accessed computer and error message was shown on login page:  Acquire_iut.exe-Application error.  The instrument at "Ox6a2f91fd" reference memory @ "Ox28000124".  The memory could not be read.  Click OK to terminate the program.  After clearing error and logging on, Run_Acquire has sync id=102 but no frames or data from cameras A or B.  Reset cameras and now both show 66 bytes of data.  RTS at 1333 GMT.

12/14/11

PAD

Remotely accessed computer and camera A was showing 22.21 KBytes.  Camera B was showing 66 Bytes.  Stopped programs and reset cameras.  After programs were restarted, both cameras are showing 66 Bytes.  RTS at 1346 GMT.

11/29/11

CAM/PAD

Mentor requested a plane distance measurement be done.  Connected laptop directly to instrument at 2215 GMT and dropped 10mm spheres until at least 5 were detected in the 3 required corners.  Ran the do_plane batch file and obtained three new distance values and saved them to acquire.par.  Dropped at least 30 each of 2, 4 and 6mm spheres and saved results for mentor to review.  Reset cameras and restarted software.  RTS at 2315 GMT.

Old values:   HBL = 6.3514  HBR = 5.8793  HFR = 5.8159

New values: HBL = 5.8525  HBR = 5.3694  HFR = 5.1603

11/21/11

PAD/CAM

Mentor requested plane test performed.  At 1820 GMT, connected laptop directly to instrument to conduct test.  Program recognized a few dropped spheres then would not detect them.  Run_acquire program was freezing, then restarting on its own.  Moved computer back into building and reconnected with original comms.  Camera A would then show 22 KB of data and camera B 66 bytes.  Shut down/ restarted system but Run_Acquire would show nothing or "Calibration mode is not set".  Tried to connect with camera to check signal graph but it did not show anything.  Contacted mentor.  Troubleshooting at this time.  RTS at 2100 GMT.

10/31/11

PAD

Camera A shows 22.21 KBytes of data while camera B shows 66 Bytes.  No precipitation at this time.  Opened enclosure and found nothing that would cause false readings.  Stopped Run_Acquire and DV2 programs and reset cameras.  Started programs with no change in readings.  Powercycled instrument and restarted programs.  Camera A now shows 66 Bytes.  RTS at 1637 GMT.

9/27/11

PAD

UVSR building is needing outer skin replaced.  Facilities have to remove all power and communications boxes from outside of shelter to complete work.  They requested all instruments that power or comms run through UVSR shelter shut down.  At 1830 GMT, shut down Summinet and 2DVDisdrometer computers.  Removed all power and comm cables going to those instruments.  Network hub located in UVSR building was also shut down.  This affects the WRG and Disdrometer instruments.  RTS at 1930 GMT.

9/12/11

PAD

DV2 program shows last file created on 9/11/1 at 1024 GMT.  Reset cameras and restarted Run_Acquire and DV2 programs.  Programs started correctly.  RTS at 1320 GMT.

8/22/11

PAD

Last file on DV2 program was on 8/21/11 at 1259 GMT.  Troubleshooting found Camera B light source bulb is burnt out.  R/R bulb, adjusted signal and restarted Run_Acquire and DV2 programs.  RTS at 1616 GMT.

8/16/11

SD

DV2 program has a time stamp for 8/13/11 at 2306:48.

Also the DV2 Program shows "Looking for OEU data: c:|2dvddata|3 sec|0*.*"   Renamed the current directories to C:\2dvddata\temp_bkup and C:\2dvddata\3sec_bkup so all of the original files are still present. Created NEW C:\2dvddata\temp and C:\2dvddata\3sec directories. Performed a PCAB_Reset and restarted the Acquire and DV2 programs and all looks well at 1800 GMT.

8/12/11

PAD

Run_Aquire program stopped on 8/11/11 at 2110 GMT.  TS found lamp A had failed.  Earlier rain prevented bulb to be changed at time found.  At 2045 GMT, R/R bulb A.  Adjusted signal and started programs.  RTS at 2100 GMT.

08/08/11

SPD

Aquire program was not synced.Log message was "Calabration mode not set". Visual inspection revealed one of the lights was out.  Via software, reset the system and then opened live video mode. That cleared the errors and the light in the unit came back on.

8/1/11

PAD

DV2 program shows data was last processed on 7/31/11 at 1549 GMT.  Troubleshooting found camera A signal was dropping below the threshold of 80 towards the left side of the display.  Cleaned all mirrors and Fresnel lenses for cameras A and B.  Camera A signal is now above minimum threshold and Run Acquire and DV2 programs started correctly.  RTS at 1649 GMT.

7/25/11

PAD

Run Acquire shows Cam A has 107 frames and is showing 22.21 KB of data.  Camera B has 1 frame and 66 Bytes of data.  Nothing found at instrument to produce false readings for Cam A.  #3 port on the ethernet switch is on solid.  Reset cameras and started Run Acquire and DV2 programs.  Run Acquire now shows 66 Bytes for both cameras.  RTS at 1600 GMT.

7/18/11

PAD

Observed camera A and B time stamps are  sporadically and do not match.  Camera A shows 1310999574 and B shows 131977842.  Instrument status on Run-Acquire shows:  Calibration mode is not set.  DV2 program shows last data set collected was in the 0800 GMT hour.  Stopped/restarted Run-Acquire and DV2 programs.  Programs started correctly.  RTS at 1730 GMT.

6/16/11

PAD

At 1325 GMT, observed no sync id for Run_Acquire program.  DV2 shows 0755 GMT as last data collected.  Thunderstorms had moved through CF area during the night.  Stopped/restarted Run_Acquire and DV2 programs but sync id was not established.  Reset cameras using software and started programs again.  Sync id is now established and both programs are running correctly.  RTS at 1340 GMT.

6/14/11

PAD

Unable to RA computer.  Rebooted computer and restarted programs.  Now able to RA computer.  RTS at 1445 GMT.

6/13/11

PAD

At 1615 GMT, found instrument did not have power.  DV2 program shows 6/12/2011 at 0535 GMT.  Power indicator light was on instrument power supply.  Power cycled instrument power supply.  Restarted DV2 and Run_Acquire programs.  RTS at 1630 GMT.

5/2/11

PAD

At 1450 GMT, logged onto computer as Distro and observed Run Acquire and DV2 programs were not running.  Both programs started upon login.  No other issues observed.  RTS at 1505 GMT.

4/18/11

PAD

Unable to RA computer.  At 1345 GMT, error message is shown on computer:  Acquire_iut.exe-Application error.  Printed screen image but was unable to open Word Document to save.  Cleared error message and a cmd-exe-Application error was shown.  Cleared second error and approximately 50 Microsoft acquire.iut.exe messages.  Run Acquire and DV2 programs started after messages were cleared. Saved screenshot in error folder on desktop.  RTS at 1400 GMT.

4/15/11

JEM

The program has stopped running and the last time on the program window is Friday, April 15th 08:17:21.  Powered off the computer and then turned the instrument power cycled the instrument @1510 GMT.  After a couple of minutes powered on the computer.  After the computer completed booting up, the instrument software was observed running as expected.  RTS @1520 GMT.

4/12/11

PAD

Program is not running, error shown:  Acquire_iut.exe Application error.  The instruction at "0x6z2f91ff" referenced memory at "0x0993e5fz".  The memory could not be read.  Click OK to terminate program.  Took a screenshot of error message and saved in error folder on desktop.  Cleared error message and rebooted computer.  Program started correctly.  RTS at 1852 GMT.

3/25/11

MK

The frames and file sizes were not changing every 3 seconds.  Closed software and restarted, no change. Power cycled instrument power supply and rebooted software, system returned to normal.

3/24/11

PAD

Run Acquire and DV2 programs stopped at 1007 GMT.  No syncId is shown.  At 1423 GMT, opened instrument enclosure and verified all link lights were lit on Ethernet hub.  Powercycled instrument and rebooted computer.  Programs started up correctly.  RTS at 1438 GMT.

3/14/11

PAD

Remotely accessed computer at 1302 GMT.  No synch ID shown on Run_Acquire program.  Program shows 3/13/11 at 2113 GMT.  Suspect that is when data acquisition stopped.  Stopped/restarted Run_Acquire and DV2 programs.  Error was shown:  An error occurred while reconnecting B: to \\092.168.1.2\ data/  Network path was not found.  This connection has not been restored.  At 1734 GMT, powercycled instrument and rebooted computer.  Programs started correctly.  RTS at 1749 GMT.