Super-Site

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 desicant 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 disapating. I don't expect to need to use the toughbook directly, should be availablle 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. LoggerNet for linux is also running on it (at present anyway). See below for more information and particulars of the software setup.

Toughbook Setup

Toughbook is a CF-19 (small one with the touchscreen)

1. Install Ubuntu 10.10
2. Install Xinput Calibrator as per suggestions here
3. Install Numpy
4. Install Git
5. Install DHCP server for local network access on eth0 (wlan0, intel chipset installed on toughbook wasn't designed to serve as a wireless access point)
6. Install DNS Masq for supplying dns to local network (eth0 only) dnsmasq website
7. Manually configure IPTables for internet connection sharing
8. Install Loggernet for Linux
   1. Handy: this page on rpm to dem
   2. Handy: Ken's Notes
   3. Handy: Redhat vs. Debian naming convention
   4. Gist is to change the daemon command in csilgrnet, csildmp, csildep to something like this: start-stop-daemon --start --user loggernet --exec /opt/CampbellSci/LoggerNet/csilgrnet -- --run-as-daemon=true
9. clone git repositories for datapro tools

cd ~/.ssh
ssh-keygen -t rsa -C "bob"
cat ~/.ssh/id_rsa.pub
[paste key on github]
cd ~/working_files/bin/py_datapro/
git clone git@github.com:frankohanlon/DataPro.git

1. sftp datapro configs
2. Buy a bluetooth keyboard/mouse
3. set up sshd
4. set up keys w/ toughbook & iarc.server
5. LoggerNet isn't initially running at start. For ubuntu:

cd /etc/init.d
sudo update-rc.d myscript defaults 98 02

1. add sites to loggernet

1. Yet to be done:
   1. Dig out an old CRT monitor
   2. make insulated enclosure for laptop
   3. search/replace to get datapro scripts running on the new computer
   4. set up scp & data processing on the cron

Things running locally on the cron: IP address posted to peeps.working_files/ss_status/

Sensors

To Do

1. Figure out problems with Soil Moisture probes
2. Figure out problem with soil heat flux plate
3. Emailed this site to CSI 11/30/2010.

Local Network

I'd draw pictures if I knew how. Anyway:

• Small Toughbook gets internet over wlan1 from the Poker Flats facility over DHCP
• Out of eth0, the wired ethernet port, it acts as a DHCP server on the 192.168.1.1 address range.
• The site NL100 is set to 192.168.1.2
• The camera is set to _____
• There is a network switch so that other devices can also connect such as the eddy flux down the road.

PakBus etc.

NL100 settings:

NL100/105:
TLink config: [disabled]
RS485 config: [PakBus]
 RS485 bps: [38k]
 RS485 beacon interval (sec): [60]
 RS485 verify interval (sec): [0]
 RS485 neighbor list: [0]
CS I/O config: [disabled]
RS232 config: [disabled]
EtherNet 10BASE-T: [enabled]
 10BASE-T port IP address: [192.168.1.2]
 10BASE-T port network mask: [255.255.255.0]
 IP address of the default gateway: [192.168.1.1]
PakBus Address of the NL100/105: [678]
 Clock source address: [0]
 Central Routers: [0]
PakBus/TCP server config: [enabled]
 PakBus/TCP server port number: [7808]
PakBus/TCP client config: [disabled]
Modbus/TCP gateway config: [disabled]
Telnet IP port number: [23]
DevConfig security code: [0]
NL100/105 (ver, show, edit, defaults, reset, help, bye): ver
                ROM version: 2.10
                OS version: 9
 EtherNet physical address: 00d02c001395
Number of objects on heap: 431 (pkt pool: 1)

MD485s are setup:

RS485 & CSI/O active
RS485 @ 38k
CSI/O @ 38k
Transparent communication mode

Data loggers:

Super-Site Met (16 meter tower & radiation) -- PakBus ID 420
Super-Site Soil (Soil Pit, Heat Flux, Snow, Surface Temps) -- PakBus ID 421
Super-Site Power (Current Monitor & diagnostics) -- PakBus ID 422