CU Windcube
ID: 123 561 016
Password: windcube7CU
NCAR Windcube
ID: 597 162 296
Password: windcube7NCAR
Tuesday, November 20, 2012
Friday, October 26, 2012
WLS7-68 update
The Verizon software did not want to automatically connect itself, this has likely been an issue for the last week. I will need to keep an eye on that to see if the updated windsoft version could be interfering with the functionality of the Verizon software and associated scripts.
After the recent snow, the laser window was unobstructed even with the sun shield still installed. I cleared off the sun shield, and in that process knocked some snow over the window. The wiper tried to activate (I could hear either the wiper motor or the pump motor try to do its thing), but no wiping or squirting actually occurred. The curse of Colorado continues to plague the WLS7-68 wiper motors. I then manually cleaned the laser window. Before the next snow we should consider taking the sun shield off for the winter.
Turbine Outflow Dissipation Study data can be found in the following breeze directory:
/data/fielddata/TODS/WC68
After the recent snow, the laser window was unobstructed even with the sun shield still installed. I cleared off the sun shield, and in that process knocked some snow over the window. The wiper tried to activate (I could hear either the wiper motor or the pump motor try to do its thing), but no wiping or squirting actually occurred. The curse of Colorado continues to plague the WLS7-68 wiper motors. I then manually cleaned the laser window. Before the next snow we should consider taking the sun shield off for the winter.
Turbine Outflow Dissipation Study data can be found in the following breeze directory:
/data/fielddata/TODS/WC68
100S
After this week's snow I checked on the 100S today. It was unresponsive through team viewer before heading to the NWTC. When I arrived about about 12:30 MDT it appeared that the system was staring to the NE , but further north than the M5 tower. After I wiped snow off the top of the box and scanner head, the head began rotating counter clock-wise and appeared to be taking a PPI scan at a low elevation angle (less than 10 deg. above the horizon). Considering snow was built up on the scanner head, I assume that the head had been stuck in that position for a considerable amount of time. The last data file before restarting was created on October 24 at 18:11:56 UTC (shortly after noon local time), but the file is over 2800 times larger than a typical PPI scan. A typical PPI scan lasts for about 1 minute.
I connected to the LIDAR through the laptop. Upon connecting, a windows dialogue box was warning that the Windsoft software had crashed. I closed that box and restarted the windsoft software. The system re-initialized and began taking PPI sector scans between the M5 tower and Alstom turbine.
Otherwise the water bucket was unfrozen and had plenty of water after topping it off some in the last two weeks.
The 100S data can be found on the breeze server under the following path:
/data/fielddata/TODS/100S/Data
I connected to the LIDAR through the laptop. Upon connecting, a windows dialogue box was warning that the Windsoft software had crashed. I closed that box and restarted the windsoft software. The system re-initialized and began taking PPI sector scans between the M5 tower and Alstom turbine.
Otherwise the water bucket was unfrozen and had plenty of water after topping it off some in the last two weeks.
The 100S data can be found on the breeze server under the following path:
/data/fielddata/TODS/100S/Data
Thursday, September 13, 2012
Time Change
At approximately 1451 MDT today I switched the CU Windcube time from 251 MDT to 1451 MDT.
The LIDAR was operational upon arriving. The only issue was with the Verizon modem. It appears that the modem tried to update locations or software and when this occurs it is not able re-initialize a connection when the VZW task runs.
The LIDAR was operational upon arriving. The only issue was with the Verizon modem. It appears that the modem tried to update locations or software and when this occurs it is not able re-initialize a connection when the VZW task runs.
Friday, August 3, 2012
Windcube move to 4.0 pad
Matt, Brian, Clara and Mike moved the CU WC from the 4.4 pad to the 4.0 pad in preparation for upcoming GE turbine wake measurements.
The last data file from the 4.4 site is WLS7-68_2012_07_31__21_00_34.sta.
The first data file from 4.0 is WLS7-68_2012_08_02__22_09_03.sta which was started at ~10:10 AM MDT on August 3, 2012. THERE IS A DIFFERENCE IN WC TIME AND LOCAL TIME!
While aligning the WC to magnetic north, a -3deg. offset was applied in the system software. The GPS coordinates are 39deg. 54.716min. N 105deg. 13.352min. W. Work was wrapped up at ~11:03 MDT
The last data file from the 4.4 site is WLS7-68_2012_07_31__21_00_34.sta.
The first data file from 4.0 is WLS7-68_2012_08_02__22_09_03.sta which was started at ~10:10 AM MDT on August 3, 2012. THERE IS A DIFFERENCE IN WC TIME AND LOCAL TIME!
While aligning the WC to magnetic north, a -3deg. offset was applied in the system software. The GPS coordinates are 39deg. 54.716min. N 105deg. 13.352min. W. Work was wrapped up at ~11:03 MDT
Wednesday, June 13, 2012
6/13/2012 Update
The Summer School for Remote Sensing in Wind Energy paid a visit to the windcube between ~9:30 and 11:00 MDT today.
Everything was working well with the windcube. I finished downloading the remainder of the .dsp files, so everything should be in order for connecting the windcube to Siemens network.
The computer time on the system should be adjusted at a convenient break in data collection; it appears to be 12 hours ahead of MDT time.
Everything was working well with the windcube. I finished downloading the remainder of the .dsp files, so everything should be in order for connecting the windcube to Siemens network.
The computer time on the system should be adjusted at a convenient break in data collection; it appears to be 12 hours ahead of MDT time.
Monday, June 11, 2012
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/...)
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/...)
Thursday, May 10, 2012
Archival scripts
The Windcube is frequently deployed at the NWTC. When it is integrated into a company's network at the NWTC (we will not identify the company in this forum), they prefer to have scripts archive the data for inclusion into their database. When the Windcube is not deployed in their network, the scripts are disabled so that the data can be ftp'ed back to breeze.colorado.edu via the Verizon modem.
From Mike Rhodes:
The company's scripts are still on the windcube; I just
deactivated them. To reactivate them you need to log-in to the
windcube computer. Once you've logged-in go to the Start
Menu>All Programs> Accessories> System Tools>
Scheduled Tasks. This should bring up a window with several
scripts. The scripts include things like, 'Archive_Windcube',
'cleanup_windcube', 'Pack_Windcube', 'WC2MySQL*'. As I recall the
scripts ran once each day from a file folder called 'Processing'.
Generally right clicking on each task and then selecting Properties allows for changes in the scheduling routine. If you have trouble getting the scripts to run, there is plenty of information online about how to use the task scheduler, just make sure to look up info. on the appropriate windows version (XP for the windcube).
Generally right clicking on each task and then selecting Properties allows for changes in the scheduling routine. If you have trouble getting the scripts to run, there is plenty of information online about how to use the task scheduler, just make sure to look up info. on the appropriate windows version (XP for the windcube).
Initial post (test)
This blog will serve as an informal log of activities related to the CU Windcube in its various deployments. We may also include photos of the Windcube here for use in presentations or printed matter. Data files should not be shared here but rather in the archive set up on breeze.colorado.edu.
Subscribe to:
Posts (Atom)