Skip to content

TARSAN 2021 AMIGOS Field Plan

Jump to bottom
Bruce Wallin edited this page Aug 18, 2021 · 4 revisions

2021 TARSAN AMIGOS Field Tasks

AMIGOS3A - Cavity Camp

Download seabird and aquadopp data

Upon reaching the towers one of the first tasks will be downloading the data from the ocean sensors for the periods when data could not be retrieved by the tower.

Gaps:

AMIGOS3A (Cavity):

  • 2020/05/28 - 2020/09/07
  • 2021/03/27 - present

AMIGOS3C (Channel):

  • 2020/08/07 - 2020/09/07
  • 2021/03/31 - present

The download rate over IMM is 9600 baud which effectively means on the order of ~5 samples per second.

Seabird sampling rate: every 10 minutes

Aquadopp sampling rate: every hour

Seabird data

  1. Open the orange imm box via 2 latches

  2. Realease both ends of steel cable by loosening the large screws on terminal blocks

  3. Feed the steel cable ends into the manual IMM box (orange box similar to that on tower, but with IMM mounted inside)

  4. Plug a computer usb to serial cable into your computer and the serial port inside the manual IMM box

  5. Attach a 9v battery to the power leads in the manual IMM box

  6. Test for communication with the IMM. From the utils/ocean-sensors directory,

    (laptop) python mooring.py --imm-check

If all goes well this will display the IMM configuration, status, and perform a discovery routine on the line. If there is no response, check all connections, and disconnect battery for 30 seconds before retrying.

  1. Test for communication with the first seabird (device-id 05):

    (laptop) python mooring.py seabird --device-id 05 --status

If communication is established, this will report the status of the seabird. Note the value within the Samples element

<Samples>N</Samples>

N will be the sample number of the most recent sample. You will need this value in the next step.

  1. Translate the daterange you wish to download into a sample range

    (laptop) python daterange_to_sample_numbers.py --last-sample N --start YYYYMMDD --end YYYYMMDD

  2. Download the sample range

    (laptop) python mooring.py seabird --device-id 05 --start N_start --end N_end

  3. Data should be downloaded in 100 sample chunks to seabird_data directory. If the previous step fails at any point, recheck connections, disconnect the 9v battery for 30 seconds and restart. It should continue from where it left off.

  4. Repeat with device-ids 06 and 07

Aquadopp data

  1. Open the orange imm box via 2 latches

  2. Realease both ends of steel cable by loosening the large screws on terminal blocks

  3. Feed the steel cable ends into the manual IMM box (orange box similar to that on tower, but with IMM mounted inside)

  4. Plug a computer usb to serial cable into your computer and the serial port inside the manual IMM box

  5. Attach a 9v battery to the power leads in the manual IMM box

  6. Test for communication with the IMM

    (laptop) python check_imm.py

If all goes well this will display the IMM configuration, status, and perform a discovery routine on the line. If there is no response, check all connections, and disconnect battery for 30 seconds before retrying.

  1. Test for communication with the first seabird (device-id 20):

    (laptop) python mooring.py aquadopp --device-id 20 --status

If communication is established, this will report the status of the seabird. Note the value within the Samples element

<Samples>N</Samples>

N will be the sample number of the most recent sample. You will need this value in the next step.

  1. Translate the daterange you wish to download into a sample range

    (laptop) python daterange_to_sample_numbers.py --last-sample N --start YYYYMMDD --end YYYYMMDD

  2. Download the sample range

    (laptop) python aquadopp.py download --device-id 20 --start N_start --end N_end

  3. Data should be downloaded in 100 sample chunks to aquadopp_data directory. If the previous step fails at any point, recheck connections, disconnect the 9v battery for 30 seconds and restart. It should continue from where it left off.

  4. Repeat with device-ids 22 and 24

Access tower upper components

Likely need to Lower the tower to access the upper components (if necessary).

Recover SD card and swap in "testing" SD card

  1. Disconnect the power cable to the white box
  2. Enable the debugger serial port by putting in place the JB5 jumper on the Triton main board
  3. Remove the SD card from the Triton board by pressing it in gently until it clicks and pops out
  4. Install the "TESTING" SD card in its place
  5. Reconnect the power cable to the white box

With the "TESTING" card in place, the tower will boot up in an idle state with the ethernet hub powered. This allows you to connect an ethernet cable to the 'comp' port and your laptop to connect via ssh

(laptop) make ssh-con

Troubleshoot/replace IMM

  1. Test the IMM Login in to the AMIGOS (e.g. via ethernet and SSH) and run

    (amigos) honcho imm --repl

If/when you see a prompt '>' type 'GetSD' and hit enter. You should see status information of the IMM module. If there is an error or nothing happens for more than 15 seconds, there is an issue with the IMM and/or its connection to the Triton.

  1. See walkthrough in )
  2. Repeat the test in 1.

Troubleshoot/replace CRX

  1. Testing the CRX Login in to the AMIGOS (e.g. via ethernet and SSH) and run

    (amigos) honcho crx --run

If working, the log will show communication/data retrieved from the cr1000x and a timestamped data sample will be appended to '/media/mmcblk0p1/data/crx/CRX.log'.

The CR1000X is located inside the battery box, so troubleshooting it may need to wait until it is accessible. Besides visually checking connections and module, you can check that it is recieving power on its power terminals. Power can be manually switched on with the command

(amigos) honcho gpio --crx-on

Troubleshoot/replace snow height

The snow height sensor logs data through the CR1000X so testing is similar. The last field in the CRX sample is the height measurement in meters.

  1. Testing the CRX Login in to the AMIGOS (e.g. via ethernet and SSH) and run

    (amigos) honcho crx --run

If working, the log will show communication/data retrieved from the cr1000x and a timestamped data sample will be appended to '/media/mmcblk0p1/data/crx/CRX.log'.

Install deployment SD card

Once troubleshooting steps are complete, the last step is to install the new deployment SD card. When installed, and the tower is powered, it should then run in normal autonomous mode.

  1. Shutdown the tower

    (amigos) honcho system --shutdown

  2. Disconnect the power cable to the white box

  3. Remove the "TESTING" SD card from the Triton board by pressing it in gently until it clicks and pops out

  4. Install the "deployment" SD card in its place

  5. Reconnect the power cable to the white box

Note: this will make the 'comp' ethernet connection generally unusable as much of the time the network hub is powered off to conserve batteries. Further interaction will require accessing the serial debugger connection on the Triton board (or waiting for the times when the station powers on the hub when performing a task requiring it).

Final check of system

At this point, when powered on, the system should be running in normal operation mode. This can be verified by e.g.

  1. Running ps, looking for a line in the output with supervise.sh
  2. Checking the various log files in /media/mmcblk0p1/logs, particularly supervise.log and schedule.log (the latter may take several minutes to show up)
  3. Looking for data collected in /media/mmcblk0p1/data according to the schedule in /media/mmcblk0p1/honcho/config.py
  4. Looking for subroutine successes/failures in the files /media/mmcblk0p1/archive/honcho.tasks*.log.

When satisfied, it is a good idea to take a snapshot of the system for later reference. This can be done with

make backup

which will copy the SD card contents to a local directory under backup/<datetime>

Remove the JB5 jumper

A final thing to do before raising the tower is removing the JB5 jumper. This disables the serial debugger on the Triton, and saves a small amount of power.

  1. Shutdown the tower

    (amigos) honcho system --shutdown

  2. Disconnect the power cable to the white box

  3. Remove the JB5 jumper

  4. Reconnect the power cable to the white box

After removing the serial port console will not function.

Raise tower

Before raising the tower, an 'access' ethernet cable can remain attached to the 'comp' port to verify operation. This connection will not generally be active, however, only during the time the tower turns on the hub for a task.

AMIGOS3C - Channel Camp

Download seabird and aquadopp data

Seabird data

Same instructions as AMIGOS3A, except device ids 08, 09, and 80

Aquadopp data

Same instructions as AMIGOS3A, except device ids 21, 23, and 25

Access tower upper components

Same instructions as AMIGOS3A

Recover SD card and swap in "testing" SD card

Same instructions as AMIGOS3A

Troubleshoot/replace IMM

Same instructions as AMIGOS3A

Troubleshoot/replace router

See walkthrough in )

To test further you can try and upload a file

(amigos) touch /media/mmcblk0p1/upload/test_file
(amigos) honcho upload --run

Which will take a few minutes to run and should indicate success/failure in the end. More insight may be gained by viewing the router logs. To view them, connect via ssh and run

(amigos) honcho gpio --rtr-on --ird-on

This will turn on the router and iridium modem. Next navigate in your browser to 192.168.0.1, login with the 'admin' credentials.

Troubleshoot/replace snow height

Same instructions as AMIGOS3A

Troubleshoot/replace SOL

Inspect the solar sensor connections and replace module if necessary.

  1. Testing the solar sensors Login in to the AMIGOS (e.g. via ethernet and SSH) and run

    (amigos) honcho sol --run

If working, the log will show communication/data retrieved from the light sensors and a timestamped data sample will be appended to '/media/mmcblk0p1/data/sol/SOL.log'.

Install deployment SD card

Same instructions as AMIGOS3A

Remove the JB5 jumper

Same instructions as AMIGOS3A

Raise tower

Same instructions as AMIGOS3A

Clone this wiki locally