Page
29
of
32
8
Event Source Identification
8.1
PIPEMINDER-S Deployment
When using two or more PIPEMINDER-S devices to infer the source of an event it is important to ensure that
their clocks are closely synchronised. The first step in achieving this is to deploy them all on the same day
following the procedure in section 6.8. The devices should be deployed between 1km and 5km apart bridging
the suspected transient source.
If device contains NTP software please proceed to chapter 8.3. If device does not contain NTP software or
cellular signal is poor prohibiting the effectiveness of NTP please follow chapter 8.2 below.
8.2
PIPEMINDER-S Manual GPS Time Synchronisation
On retrieval, a second GPS time lock is required for each PIPEMINDER-S to retrospectively correct observed
events for clock drift. For this procedure the magnetic wand is required.
1.
Remove PIPEMINDER-S from its installed location without disconnecting the battery;
2.
Lay PIPEMINDER-S on the ground with a clear view of the sky;
3.
Activate magnetic switch 2 using the supplied (Figure 2: Device overview);
4.
Progress will be reported on the display; wait for a successful GPS fix;
5.
A drift file will be saved to PIPEMINDER-S
’s internal storage
. If PIPEMINDER-S is left on, it will be
automatically sent to the server at midnight. Alternatively, it can be transferred via USB and uploaded to
RADAR.
6.
Depending on the configuration, any transient events during the period will have either been stored locally
or uploaded to RADAR automatically.
There is no limit as to how many times this procedure, may be followed and the PIPEMINDER-S can be re-
deployed, without removing the battery, immediately following it. The time-fix of a transient event is
improved the more often a GPS synchronisation is carried out and this is reflected in the accuracy of identifying
the likely source, Syrinix recommend no longer than 21 days between GPS re-fixes.
