Difference between revisions of "Super-Site"
imported>Bob |
|||
| Line 96: | Line 96: | ||
Data loggers: | 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==== | ====Field Visit Checklists==== | ||
Revision as of 09:56, 20 July 2016
Contents
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
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.
Sensors
To Do
- Figure out problems with Soil Moisture probes
- Figure out problem with soil heat flux plate
- Emailed this site to CSI 11/30/2010.
Local Network
Subnet is 192.168.10.x
Computer: Select DHCP or for static these are currently in use:
- 192.168.10.230
- 192.168.10.230
- 192.168.10.230
Subnet: 255.255.255.0
Default Gateway: 192.168.10.20
DNS: Your own preferred, or 192.168.10.20
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)
