Super-Site

From IARC 207 Wiki
Revision as of 10:31, 21 May 2019 by 172.18.0.1 (talk)
Jump to navigation Jump to search


Tower Remodel 2
Super Site Tower
Super Site LI-COR Parts Inventory
Super Site LI7200 Recalibration
LI-7200 Thermcouple Replacement

Visits

Current Programs

CSI Signature Values on 2014-08-11... checked from Dropbow/Logger_programs/super-site/:

==> SS_Diag_Diagnostic.dat <==
"TOA5","SS_Diag","CR1000","29724","CR1000.Std.20","CPU:ss_diag_2011-01-25.CR1","30274","Diagnostic"
    30274 ss_diag_2011-01-25.CR1
==> SS_Eco_1_AirTemps.dat <==
"TOA5","SS_Eco_1","CR1000","13604","CR1000.Std.22","CPU:ss_eco1_2012-07-10.CR1","10119","AirTemps"
    10119 ss_eco1_2012-07-10.CR1
==> SS_HeatFlux_1_Diagnostic.dat <==
"TOA5","SS_HeatFlux_1","CR1000","47954","CR1000.Std.24","CPU:ss_hf_2012-10-09.CR1","31220","Diagnostic"
    31220 ss_hf_2012-10-09.CR1
==> SS_Met_AirTemps.dat <==
"TOA5","SS_Met","CR1000","30801","CR1000.Std.20","CPU:ss_met_2013-03-06.CR1","47292","AirTemps"
    47292 ss_met_2013-03-06.CR1
==> SS_SnowTemp_Diagnostic.dat <==
"TOA5","SS_SnowTemp","CR1000","22972","CR1000.Std.16","CPU:ss_snow_pro_2011-10-10.CR1","19271","Diagnostic"
    19271 ss_snow_pro_2011-10-10.CR1
==> SS_Soil_Diagnostic.dat <==
"TOA5","SS_Soil","CR1000","29723","CR1000.Std.20","CPU:ss_soil_2010-11-03.CR1","11488","Diagnostic"
    11488 ss_soil_2010-11-03.CR1

PFA Cameras

user: pfa

This is the tower uplooking Serial to USB converter:

root@pfa-CF-AX3SEGJR:/home/PFA_/public_html/original/dc# udevadm info -a -n /dev/ttyUSB0 | grep '{serial}' | head -n1
   ATTRS{serial}=="0000:00:14.0"
Forest Floor: /dev/serial/by-path/pci-0000:00:14.0-usb-0:1:1.0-port0
Tower Top: /dev/serial/by-path/pci-0000:00:14.0-usb-0:2:1.0-port0

If you see a message like this in the logs:

Error 10003: eph_waitsig got -2

The camera is probably not turned on. To power on the tower top camera, press the button on the beige box for 2-3 seconds. To turn on the Forest Floor camera you will need to open the domed box and physically turn the power on.

Images recorded on the cron schedule show here:

Manually recorded measurements, such as when running the scrip from a terminal window, show up here:

/home/PFA_/public_html/original/dc


Computers currently at Shed (7/2017)

  • Eddy Flux Tower Top Toughbook CF-31
    • 64 bit Windows 7
    • hostname: tower
    • purpose: log & manage tower top LICOR 7200
  • Eddy Flux Forest Floor Toughbook CF-31
    • 64 bit Windows 7
    • hostname: ForestFloor
    • purpose: log & manage forest floor LICOR 7200
  • ss-main Toughbook cf-19
    • Debian
    • hostname: ss-main
    • purpose: logs super-site met etc. CR1000 systems
  • DTS Toughbook CF-19
    • Windows 7
    • hostname: dts-jics-PC
    • purpose: log & manage DTS system
  • MS700 Hyperspectral computer: Sony Vaio laptop
    • Japanese Windows 10
    • hostname: JAMSTECVAIO
    • purpose: LoggerNet for MS700 CR3000 logger
  • All Sky Cam Laptop
    • Ubuntu 16.04
    • hostname: pfa-CF-AX3SEGJR
    • purpose: downloads images from up & down looking cameras
  • Fiberswitch Small Dell Notepad
    • Windows 10
    • hostname: DELL-HK
    • purpose: manages HR400 system
  • JICS PC#1 Toshiba Laptop
    • Windows 7
    • hostname: JICS1-PC
    • purpose: Dropbox backup at the moment for Eddy Flux data

Other Computer Items

  • Hawking Technology Wireless Access Point
    • Signal ID: SS_Wifi
  • Ubiquiti M2 Bullet
    • Located at tower top w/ power of ethernet injector in shed, this is our access to the Poker Internet Infrastructure.
  • Net Gear 16 Port 10/100 Switch

Forest Floor Flux Bonus info

  • batch file to automove data to dropbox:
move c:\users\user\documents\* "C:\Users\user\Dropbox (JAMSTEC_PFRRdata)\pfrrflux\usprr_flux_original\archive_rawflux\floor\2018\"
  • scheduled task set up to run this daily.

Tower Flux Bonus info

  • Use this batch file to transfer flux data to dropbox:
move c:\users\user\documents\* "C:\Users\user\Dropbox (JAMSTEC_PFRRdata)\PFRRflux\USprr_Flux_Original\Archive_rawflux\Tower\2018\7200RS\"
  • Winscp script set up plus batch file running through task scheduler to transfer data from ss-met to dropbox:
"C:\Program Files (x86)\WinSCP\WinSCP.com" /script="c:\users\user\scripting\winscp_metdata.txt" 
  • contents of winscp_metdata.txt
open sftp://192.168.10.110
synchronize local "C:\Users\user\Dropbox (JAMSTEC_PFRRdata)\PFRRflux\USprr_Flux_Original\MeteorologicalData\Met" /var/opt/CampbellSci/LoggerNet/4.1/SS_Met
synchronize local "C:\Users\user\Dropbox (JAMSTEC_PFRRdata)\PFRRflux\USprr_Flux_Original\MeteorologicalData\Soil" /var/opt/CampbellSci/LoggerNet/4.1/SS_Soil
exit
  • Current raw archive:
C:\Users\user\Dropbox (JAMSTEC_PFRRdata)\PFRRflux\USprr_Flux_Original\Archive_rawflux\Tower\2018\7200RS
  • Both of these batch files run as separate scheduled tasks under Task scheduler.
    • Met data transfers at 9:10 AK STD
    • Flux data transfers at 1:08 AK STD

Older Content

Here's a page started by Bob. Not sure how often I'll be adding stuff but it's been on my to-do list. Thought I'd start with packages added to the toughbook.

COTS network system

It's not the cheapest way to go but I thought going for commercial hardware for the network components would be the way to go. We'll see once the site is operational for a winter or two. Presently, what I have going on is something like this:

This antenna picks up WiFi from a building at PFRR:
RadioLabs very directional antenna

This WiFi adapter has a linux compatible chipset and was easy to setup:
RadioLabs Magnum II USB Adapter
This powered USB extender (extend using ethernet cable from box to box) allows the usb wifi adapter to be up on the tower, minimizing the coax losses on the run to the antenna:
XTENDEX USB-C5-CE
I picked up some underground burial suitable Cat5E to go from the computer usb extender to the tower usb extender:
purchase link
So those items combine to get you to the computer.

I have two CSI white boxes. One to house the computer and one to house the tower USB & WiFi stuff. Each is lined with blueboard, sealed with duct seal, and has some extra desiccant to keep it dry, hopefully warm enough in the cold, time will tell on that though. I'll crunch the numbers at some point to see how much heat is being generated / how quickly it's dissipating. I don't expect to need to use the toughbook directly, should be available for sshing from UAF proper or via wired ethernet onsite but on the off chance I do need to connect locally, I have a VGA adapter connected to the computer and will leave a surplussed CRT monitor out at the site. Connection to the laptop will be via a bluetooth keyboard/touchpad combo:
purchase link

The computer is then connected to a network switch. This allows it to connect to the local NL100 and handle any local DHCP traffic. Probably a future upgrade will be a wireless bridge to allow other computers access to the internet / reduce the amount of brittle cabling laying about in the shed. See below for information and particulars of the software setup.

Toughbook Setup

Stock Debian with a few extra packages installed like Numpy, TeamViewer, LoggerNet for Linux

Currently use a Ubiqiti device to provide local network accesss. 192.168.10.x subnet I think.


PakBus etc.

Computer MD485:

RS485 & RS232 Active
RS485@ 38k
RS232@ 115.2k

Logger MD485s are setup:

RS485 & CSI/O active
CSI/O Mode -- Modem Enabled
Transparent communication mode
CSI/O @ 38k
RS485 @ 38k


Data loggers: add-device pakbus-port {PakBusPort} as-child {ComPort}; add-device CR1000 {SS_Met} as-child {PakBusPort}; (420) add-device CR1000 {SS_Soil} as-child {PakBusPort}; (421) add-device CR1000 {SS_Diag} as-child {PakBusPort}; (422) add-device CR1000 {SS_SnowTemp} as-child {PakBusPort}; (424) add-device CR1000 {SS_Eco_1} as-child {PakBusPort}; (423) add-device CR1000 {SS_HeatFlux_1} as-child {PakBusPort}; (425)

Field Visit Checklists