User's Manual

Table Of Contents

Draft

R00.f RT 1000 v1.0 Deployment Guide 27

Troubleshooting

LED Chart

7.3 LED Chart

Insert the chart showing possible LED situations and what they mean.

Throughout the project, there will likely be intermittent problems with the ground

electronics. Failures can result from poor initial deployment, general wear and tear,

lighting strikes or other acts of god, livestock and wildlife, or vandalizing (or

curious) humans. When these problems must be solved physically, the Observer

will use troubleshooters. Battery replacements fall into this category as well, if only

an anomalous few need to be replaced within the spread.

The troubleshooters, as noted in the User Story section, will have quick

transportation (usually a mule or ATV), a collection of spares and tools, and a

reasonable level of technical skill and training. The Observer will provide him with

a printed list or file that can be loaded to a GPS. It will include:

• Location (X/Y and line/station)

• Faulty piece of equipment (geophone string, LTU/BSU, WRU)

• Nature of problem (GPS failed, dead battery)

• Prioritization

As each issue is addressed, the troubleshooter will communicate the action to the

Observer. At any point after this communication, the Observer will want to issue a

command to the WRU in question, such as battery or geophone test. This can be

issued immediately, tests that involve the analog circuit will result in zero-ed data

from that WRU for as long as the test takes. It can also be sent to a queue, where

the command is sent automatically when there is a pause in production. This is a

part of the event management tool. This queue also handles duty cycle issues-

where a WRU power state requires commands to wait for a particular interval.

When a WRU has failed, the rib will automatically skip-heal. This means that

adjacent WRUs will communicate around the dead WRU, so that recording can

continue uninterrupted. If a troubleshooter replaces or repairs the WRU, re-

creation of the rib can only happen when production is paused. This can be done

on command, or can be queued as with other testing commands.

In addition to troubleshooting reports, the Observer will be able to generate a

battery report. This will contain all health information about any battery that has

sent data to the CSS. Indexed by line/station or serial number, it will report the

number of charge cycles, current charge state, and any other available statistics.

Troubleshooting

• All troubleshooting functions will be performed in the active and not the

acquiring state

• The units must be commanded to stop sending seismic data; however the cycle-

mode will remain active to facilitate the troubleshooting process.