Corrections to Windcube updates

Thanks, Paul, for the summary in your post of 3/14/15. Some corrections are necessary.... the lidar supersite at the middle south guy wire consists of :
- 2 CU v1 Windcubes (WC49, WC 68)
- 1 NCAR v1 Windcube (WC61)
- 1 HALO photonics scanning lidar (not an AXYS system)
- 1 Leosphere v2 Windcube offshore 8.66 system (with motion compensation). Logging into that system is beautifully simple. Use the "laptop" ethernet port and then use a browser to go to "http://windcube/windweb". Please do not change any settings when accessing this system (currently it is set to collect data at 40, 50, 60, 80, 100, 120, 140, 150, 160, 180, 200, and 220m - nice to have 12 levels!). Here's an image of the windweb from the 8.66 manual:

The two AXYS systems (one for the ground, one for the motion table) are currently in boxes just east of the trailer in which the windcube storage boxes are stored near the base of the main tower. Current plan is for Yanis from AXYS to arrive on 30 March to install.

Julie's version of the status:
WC49:

• Operating but not likely collecting usable data. Most recent access (25 Feb) showed all NaN. Not ftp-ing data anymore since modem disconnected.
• Cannot log into this system with ethernet cable in person, perhaps because of a bad port.
• Previous alarm files noted laser errors ("Alarm: EDFA").
• To Do: Welly Cobden suggests take keyboard, mouse, and external monitor into field with side panel open to troubleshoot computer ports at some point. Julie attempted this on 13 March but brought USB keyboard, mouse, monitor cables. Need to bring old-school keyboard, mouse, and monitor cables. Not a priority since WC61 and WC68 functioning reasonably well.

WC61:

• Has been continuously taking data.
• Have intermittent difficulties logging in via TeamViewer (JKL: these challenges continue depending on modem connection, but seldom persist longer than an hour.)
• Welly suggested that noise was related to fan and overheating. Will not address until system goes to NRG in April

WC68: 

• More difficult to log into with Team Viewer probably due to modem issues. Data are being ftped to breeze (/data/ftp/incoming/instrument_data) every few days (scheduled daily but ftps fail if modem not connecting at just the right time). When logging in with Team Viewer, JKL sometimes gets a blank white screen but file transfer can still occur (hence my diagnosis of modem bandwidth issue)
• WC68 was "stopping" itself due to Drive issues (see /data/ftp/incoming/instrument_data/WC68_ALM files) that seem to have stopped since Welly's adjustment of drive accuracy tolerance (from 1 to 3) on 12 Mar. These drive errors are due to the motor aging (which is interesting as this motor has been replaced a few times).

The HALO scanning schedule involves periodic stares at the 50m tower sonic. Please try not to obstruct its view when visiting the WCs. Its schedule is:

1. 8-beam VAD once every 12 minutes (each scan takes ~40 sec), 
2. 50 m sonic stare for ~10 minutes once per hour,
3. Target sector scan (Erie HS Stadium light posts) once per day, 
4. Vertical staring the rest of the time.