Summary of XPIA BAO Site Visit, 11 May 2015

1) WC61 was offline for the most number of days the previous week. It's stage head was rotating upon arrival, but stopped as soon as a Remote Desktop session was attempted. System was rebooted via the power switch. It was then reconnected to Cellular data network after a Verizon software coverage update. JKL confirmed login through TeamViewer.

2) WC68 was taking data and able to logged into via Remote Desktop Connection. Cellular data connection and related software programs were restarted and all worked fine on the device.

All data corresponding to NWTC 4.0 pad Fall 2014 was copied and removed from data hard drive, including empty of Windows Recycle Bin. However, RAW .dsp files were for this time period were not copied over (very large), but were moved to Windows Recycle Bin and not removed.

The above actions reduced disk usage to ~64%, which is much lower than the usage upon arrival.

3) WC16 v2 offshore system is so quiet, it is difficult to know if it is running when making a site visit! Neither Mozilla Firefox (windweb) nor a ping from a command window to the IP address could connect to the system.

Power was shut down momentarily to the system, and then a reboot occurred. Both the windweb software and the FileZilla data transfer worked beautifully. Although the analyst will have to look into the data files, a cursory look into the system showed little to no missing data, except for the brief time of power down today on 11 May.

4) ~3.05 GB of data from the AXYS Vindicator LiDAR system Compact Flash Card was copied today. PTQ updated the Google Drive folder to include the additional data.

--Electrical tape was put over a few outlet spots. Power cords sustained the Colorado rain & snow deluge of the power week.

--All 3 WC and the AXYS lenses were manually wiped off.

XPIA BAO WC61 & 68 Basic Maintenance and Troubleshooting

On 2015/04/03 between about 1500-1600 MDT, Paul Quelet serviced the WCv1 LiDARs running at the BAO during XPIA. Next day (2015/04/04), have checked both systems remotely. Seem to be taking more vertical data and have stronger cell signals.

WC61 (NCAR):

• 2149 45-55 seconds (approximately), wiped lens manually. Should be NaNs in data files.
• Lens wipe seems to have helped LiDAR remotely sense more vertical levels? (So far this seems to be the case...
• Still running very strong.
• Usually transferring data (although not always full file size).
• Strong Verizon dongle signal (usually ~3 bars).
• System requested Verizon software update upon login 2015/04/04. After saying "Yes", was not able to update, and said update will come back in two days. Should happen ~0830 MDT 2015/04/06?
• Sun cover on.

WC68 (CU):

• 2213-2215 installed WC49 cover on top of WC68. Put Verizon dongle upward to extend length and wiped lens off manually.
• Lens wipe seems to have helped LiDAR remotely sense more vertical levels? (So far this seems to be the case...
• Running well.
• Manually downloaded data from 2015/03/20 to 2015/04/03 through remote desktop connection.
• Has had trouble transferring data remotely or allowing TeamViewer login.
• 2015/04/04 0000 UTC FTP data transfer seemed much improved with dongle position change.

Yes, I am aware that this is the non-matching sun cover number on the WC. However, it was quite a feat of strength to get the cover out of the Leosphere box and transport it to the site alone.

Summary of XPIA AXYS Vindicator LiDAR Deployment & WC Operations, 30 March 2015

AXYS Vindicator LiDAR Deployment

• Yanis Gryshan led the way to install two AXYS Vindicator LiDARs just to the east of the LiDAR supersite at the BAO, across the dirt driving path from the two WC v1s from CU, the Halo scanning LiDAR, and the NRG/Leosphere v2 profiling LiDAR.
• The Vindicator lidars stand on Lundquist group WindCube flat platforms.
• Each system has a serial number, noted as "13" and "15", these being AXYS generation 3 systems.
• Single power cord run across the road with orange plastic fencing noting the placement. Power cable connections secured with electrical tape.
• 10-minute averaged data can be accessed in real time through AXYS user login website, which Yanis and colleagues will disburse.
• Data is distributed through cell network in real time. Also system has satellite connections available if cell network goes down.
• (Much can be done by AXYS remotely once systems are running.)
• Systems have installed GPS and compass for position can orientation that can be viewed on website also.
• (Technically, both Vindicators are facing directly south, but these adjustments can be made in post processing, and may show systems aligned property due to correction in the software according to Yanis Gryshan.)
• 1-second data is available on compact flash card inside electrical box. Access to the CF card should be via coordination with AXYS and Julie Lundquist.
• Data heights are 49, 60, 80, 100, 120, and 149.7m (where the start and ending heights are near the BAO tower sonic heights, but are dependent on the Vindicator system setup).
• On-site system login is very similar to a WindCube LiDAR where the system IP Address must be specified and a Laptop can be used for a remote connection with an ethernet (CAT 5) cable. Would need to obtain IP addresses for each Vindicator LiDAR from Yanis or AXYS.
• LiDAR pair is to be deployed ~2 months.
• Washer fluid and compressed air tank should last ~6 weeks without changing needs. These components wash off the optical apertures if they are obstructed or dirty.

AXYS Vindicator Next Steps

• Arrival of UMBC motion table on truck will be coordinated with BAO staff Dan Wolfe, safety officer Otto, Julie Lundquist, and Andy Clifton. UMBC should be bringing compressed air tanks so that Julie can return compressed air rental tanks to Broomfield ASAP. Note that two compressed air tanks should last the two lidars three months.
• AXYS LiDAR closer to the road ("15") will be deployed to the UMBC motion table for testing.
• To deploy, the LiDAR does not need to be powered down, but could be via the red turn switch on the west side.
• There is ~4.5m cable that can be extended out to keep the RS power cables connected between the systems.
• Care must be taken in taking the Vindicator onto the motion table as cords / tubes must be threaded out from the central stand to not be obstructed keeping the systems connected.

AXYS Vindicator Storage Boxes

• The AXYS Vindicator storage boxes are put back together and stored under the BAO middle shipping container next to the tower.
• The boxes are covered with tarps to keep dry from weather.
• The top and front panels are held in place only with two screws.
• Robertson drives (square heads) are required to seal / unseal these boxes.
• All remaining Robertson head screws are in sealed ziploc bags inside the AXYS boxes.
• Note: The Robertson (square head) bit still needs to be returned to the BAO since it goes with the AXYS tool set. (Might want to hold onto it until packing up the Vindicator LiDARs for opening the boxes.)

General Field Work Notes:

• Halo scanning LiDAR at the BAO LiDAR supersite was observed to be moving and scanning upon further examination. Julie Lundquist observed very little change in aperture orientation. Later, Paul Quelet confirmed the change of scanning head position. Hopefully, this system is working well.
• Created on breeze in /data/fielddata/XPIA/ the following folders: MGAUS_photos and BAO_LiDAR_supersite_photos, and AXYS_Vindicator_deploy_photos. These are the start of some folders where photos can be transferred, shared, and used.

CU / NCAR WindCube LiDAR Notes:

• Morning of 30 March 2015, Julie Lundquist manually wiped off the apertures of the WC LiDAR systems. Should see momentary loss of data on the date 30 March in MDT morning.
• As of 30 March, WC68 is about 58% full on the local instrument D: drive data storage. This is cautioned with yellow in the WindSoft software. (WC61 is only ~40ish % full, so going strong).
• WC61 continues its great performance. Did not make any changes to the system. Cover is on and Verizon cell dongle hangs vertically from entrance door, but still under sun shield cover. Usually has about 3 bars of Verizon 3G cell service.
• WC68 has been inconsistent in cell data connection for remote login or data transfer (TeamViewer or FTP). Usually only has 1 bar of Verizon 3G cell service.
• Testing of WC68 Verizon dongle on 30 March revealed stretching out the dongle to top of WC68 produced greater cell signal strength. When put away without sun shield, dongle was stretched more horizontally, so (update) 1-2 bars of Verizon 3G cell service is now occurring.
• WC68 continues to not transfer the full files in FTP. (Update: 31 March 2015.) WC61 did not transfer full files via FTP either.
• Could consider installing WC68 sun shield and hanging Verizon dongle vertically for better remote connectivity. 
• On site, Paul Quelet was able to remote desktop with ethernet cable to WC68. Transferred all current Alarm, .rtd, and .sta files. Copied them over to breeze.
• Changed WC_FTP.txt (script) on WC61 and WC68 to dates of 2015_03_3* so that only March 30 & 31 files are transferred.
• Must change WC61 and WC68 WC_FTP.txt scripts to 2015_04* at the beginning of April to transfer all April files.
• WC16 (new v2 system) needs more careful steps to remote desktop into to obtain 1-second data files. Also, requires FileZilla according to Welly Cobden from NRG to complete this data transfer. The manual must be read carefully here and executed on site.
• WC49 is unplugged completely. Still would need an external keyboard, monitor, and mouse ("old school" style) to troubleshoot problems with on board computer. (Not quite a priority at this point.)

6/8/2012 Notes

I made a trip out to the CU Windcube while at NWTC Site 4.4 on 6/8/2012.  I was out there primarily to check on the system after a sever thunderstorm rolled through the NWTC 2 days prior, and to download the WC hard drive.

I first checked the WC at approximately 10:05 MDT and the laser head was rotating.  I initially tried to connect the CU Windcube laptop to the WC with an Ethernet line.  At first the connection was successful, but only for a moment.  It appeared that the WC computer was having some trouble as the head stopped rotating and the connection could not be reestablished with the laptop.  The WC computer self recovered after several minutes and subsequent connection to the laptop was reestablished.  Everything appeared to be operating normally from the WC self restart till the data transfer was complete.



General notes:
To connect the laptop, I set the laptop IPv4 address to 10.170.152.77, the Subnet mask to 255.255.255.128, and the Gateway to 10.170.152.1.  The WC IP address was 10.170.152.78.

 The water bucket was completely full.  I tested the wiper system and neither the water pump, nor the wiper blade activated when the system triggered each.

The WC computer listed the time as 12:34 AM when the local time was 12:34 MDT.

The directional offset in the system was +5 deg. and the "compass heading corr" was reading +8 deg.

For the sake of time some of the .dsp files (D:/DATA-EOLID/RAW) were not transferred.


Data repository:
I uploaded all of the data to breeze.colorado.edu.  (/data/fielddata/NWTC/Windcube/WC68/...)