UTM-00339 | Rev 19
Page 237 of 253
DetNet South Africa Copyright © 2021
Troubleshooting / Remedial Action
This warning is triggered when the Commander detects that a
previously connected detonator is no longer present on the line.
When this error occurs, the user is encouraged to examine the
list to determine which detonator is missing. The user will then
need to return to the bench to identify and correct the fault.
Leakage is tested during various stages, including testing and
programming. Should a high leakage warning be triggered, the
user will need to find the source of the leakage – this is
performed most effectively by using a Tagger. The user is
encouraged to disconnect the string from the Commander and
divide the string into two equal halves and test each half with a
Tagger. The leakage should be present on only one half and
this process can be repeated until the source of the leakage is
discovered. Some of the reasons for leakage include damage
to the down-line wire of a detonator unit, moisture in the
connector of a detonator unit and damage to the surface
harness wire insulation.
It is recommended that the user resolve all leakage sources to
have a leakage of 0 mA, however, should it not be possible to
eradicate all leakage sources, the system may be able to cope
with leakage sources up to 1 mA per channel.
Each channel on the Commander needs to discover at least
one detonator that has been marked as the ‘last detonator’ on
the string. To ensure that there is connectivity to the last unit on
the harness, this ‘last detonator’ will be searched for just after
charging. The Commander will also check the voltage supplied
to the last detonator to ensure that sufficient energy has been
transferred to allow for successful blasting.
Should the Commander not find a detonator marked as the ‘last
detonator’ on a channel, the ‘Last detonator not set’ notification
will be displayed – note that the channel affected will also be
indicated.
To Next Page
Loading...