i-konIII Blaster3000 MAN F1-18-03 D02-06en 20200113

i-kon™ Blaster 3000
DEVICE TO INITIATE ELECTRONIC DETONATORS IN SURFACE

AND UNDERGROUND MINING
MODES: SINGLE – REMOTE – SYNCHRONIZED
Instructions for Use - for Shotfirers
Article No: XBl3000

Firmware: F 1-18-03
D02-06en / 2020-01-13
© 2020 Orica
All rights reserved.
This documentation is copyrighted by Orica. The document contains
technical information that must not be copied, distributed, nor used without
authorization by Orica.
The manufacturer reserves the right to modify products without notice. All
information in this document is based on knowledge and data available at
the time of publication.
Orica cannot anticipate or control the conditions under which this
information and its products may be used. Therefore, Orica does not take
any responsibility for their suitability for use in any particular application
other than liabilities implied mandatorily by law. The user is expressly
responsible to verify the suitability of the information and the product for
use in any particular application.
Orica's general terms and conditions of contract are available upon
request.
Orica Sweden AB Technical Documentation:

Gyttorp Orica Europe Pty Ltd & Co KG
S-71382 Nora Mülheimer Straße 5
 +46 587 85000 53840 Troisdorf
www.orica.com  +49 2241 9952 0
info-gyse@orica.com www.orica.com
Contents
Contents
1. For your Safety 9

1.1. Purpose of this Manual ............................................................ 9
1.1.1. Evolution of i-kon™ 9
1.1.2. Additional Documentation 9
1.2. Target Group.......................................................................... 10
1.2.1. Qualification of Owners and Users 10
1.2.2. Duty to perform Maintenance and Service 10
1.2.3. Duty to report Faults and Damages 10
1.3. About this Manual .................................................................. 11
1.3.1. Structure and Meaning of Safety Messages 11
1.3.2. Safety Instructions 11
1.3.3. Notations used in the Manual 12
1.3.4. Step by Step Instructions 12
1.4. Intended Use.......................................................................... 13
1.5. Non-observance of Safety Regulations .................................. 13
1.6. Improper Use ......................................................................... 14
1.7. Product Safety ....................................................................... 15
1.7.1. Standards and Directives 15
1.7.2. Safety Concept 15
1.7.3. Keep-Alive Counter 16
1.8. Training .................................................................................. 16
1.9. Hazards and Risks when Using the Product........................... 17
1.9.1. Hazards when connecting a Defective Logger 17
1.9.2. Hazards when using a Defective Blaster 17
1.9.3. Hazards in a Remote-Controlled Blast 17
1.9.4. Re-Entering the Blasting Area 18
1.9.5. Risk of Misfires in the Muck Pile 18
1.9.6. Hazards caused by Unlogged Detonators 18
1.9.7. Hazards by a Strike of Lightning 19
1.10. Information in Case of Emergency ......................................... 19
2. About the Device: i-kon™ Blaster 3000 20
2.1. Components of the Blasting System....................................... 20
2.2. Functions of the Blasting Equipment ...................................... 21
2.3. Properties and System Limits ................................................. 22
2.3.1. System Limits 22
2.3.2. Firing Cable 22
2.3.3. Properties and Environmental Conditions 23
2.3.4. Product Identification 23
2.3.5. Electronic Detonators 24
2.4. Principle of Operation ............................................................. 25
2.4.1. Single Blaster 25
2.4.2. Synchronized Blasters 26
2.4.3. Remote-Controlled Blasters 27
2.4.4. Controlling Multiple Blasters 28
2.5. Underground Applications ...................................................... 29
2.5.1. Communication via Analog Phone 29
2.5.2. Leaky Feeder Network 30
a) Controller communicates via Leaky-Feeder Cable 30
b) Controller is connected via LAN to the Headend 31
i-kon™III / i-kon™ Blaster 3000 F 1-18-03 D02-06en 3

Contents
2.5.3. Configuration with LAN 32

2.5.4. Configuration with Wi-Fi 33
2.5.5. Configuration with multiple Blasters 34
2.6. Accessories............................................................................ 35
2.6.1. Product Overview 35
2.6.2. Output Terminals – Sync Terminals 35
2.6.3. Master Dongle and Remote Dongle 36
2.6.4. Antenna 37
2.6.5. Sync Cable 37
2.6.6. Pressure-Compensating Valve 37
2.7. Operating Keys and Connections ........................................... 38
2.7.1. Front Panel 38
2.7.2. Operating Keys 38
2.7.3. Audible Signals 39
2.7.4. Charging Unit 39
2.7.5. Charging Indicator Light 39
3. Operation and Settings 40
3.1. Operating the Device ............................................................. 40
3.1.1. Switching on and Self-Test 40
3.1.2. Switch on while in Standby Mode 41
3.1.3. The Start Menu 42
3.1.4. How to Switch off the Blaster 42
3.1.5. The Main Menu 43
3.1.6. How to return to the Start Menu 43
3.1.7. Functional Overview 44
3.1.8. Check the Charge Level of the Battery 44
3.1.9. Information about the Settings 45
3.1.10. Blaster Firmware Information 46
3.1.11. Assign a Name (Alias) to the Blaster 47
3.1.12. Using the virtual Keyboard 47
3.2. Configuring the Device ........................................................... 48
3.2.1. The Setup Menu 48
3.2.2. Setup Menu Overview 49
3.2.3. Factory Settings 49
3.3. Blaster Settings ...................................................................... 50
3.3.1. Vibration Monitoring 50
3.3.2. Adjust the Blaster ID 51
3.3.3. Blaster ID of <Sync Slave> Blasters 51
3.3.4. Adjust the Blaster Mode 52
3.3.5. Enter the Number of Allowed Errors 53
3.3.6. Allow Globals (Unlogged Detonators)? 54
3.4. Interface Settings ................................................................... 55
3.4.1. Serial Modem Settings 55
3.4.2. Configure the Radio Modem 56
3.4.3. Configure the RFI Modem 57
3.4.4. Configure the Analog Modem 58
3.4.5. Configure the LTE modem 59
3.4.6. Configure the LAN Interface 60
3.4.7. Configure the Wi-Fi Communication 61
3.4.8. Adjust the Termination Resistor on Synchronized Blasters 62
3.5. System Settings ..................................................................... 63
3.5.1. Factory Settings 63
3.5.2. Adjust Date and Time 64
3.5.3. Adjust the Operating Language 65
a) Choose the Operating Language 65
4 F 1-18-03 D02-06en i-kon™III / i-kon™ Blaster 3000

Contents
b) Install, Update or Remove an Operating Language 66

3.5.4. Adjust the Brightness of the Display 67
3.5.5. Choose the Color of the Display 67
3.5.6. Edit the Setup PIN 68
3.5.7. Update the Firmware 69
4. Blasting 70
4.1. Prepare for Blasting ............................................................... 70
4.2. Safety Precautions ................................................................. 71
4.2.1. Preventing Misfires 71
4.2.2. Unlogged Detonators – Risk of Misfires 72
4.2.3. Risk of Misfire because of a low Battery 72
4.2.4. Risk of Misfires when Blasting Multiple Blast Sites 73
4.2.5. Test the Logger Connections 74
4.2.6. Test Connections with Logger II 75
4.2.7. Prepare the Loggers 76
4.3. The Blasting Sequence .......................................................... 77
4.3.1. Evacuate the Blast Site 77
4.3.2. Blasting Sequence Overview 77
4.3.3. How to connect Loggers and Blasters 78
4.3.4. Using Harness Wire as Firing Cable 79
4.3.5. How to abort safely 80
4.3.6. Risk of Electrostatic Discharge 81
4.3.7. Begin the Blasting Sequence 81
4.4. Blasting with a Single Blaster ................................................. 82
4.4.1. Setup with a Single Blaster 82
4.4.2. Evacuate the Blasting Area 83
4.4.4. Stage 1: Start the Blasting Sequence 84
4.4.5. Stage 2: Programming Detonators 86
4.4.6. Overview – Check the Numbers 87
4.4.7. Stage 3: Initiate the Blast 88
4.4.8. Give the FIRE Command 89
5. Blaster Overview, Details and Errors 90
5.1. Blaster Overview in Stage 1 ................................................... 90
5.1.1. Blaster Details 91
5.1.2. Deselect a Logger 92
5.2. If an Error occurs.................................................................... 93
5.2.1. Warnings 93
5.2.2. Error – Abort 93
5.3. Blaster Overview after Programming in Stage 2 ..................... 94
5.4. Globals Detected.................................................................... 95
5.5. Overview with Detonator Errors.............................................. 97
5.5.1. Check and Confirm the Errors 98
5.5.2. Blaster Overview with confirmed Errors 100
5.6. Abort after the FIRE Command .............................................101
6. Procedure after the Blast 102
6.1. Uploading the Reports ..........................................................102
6.1.1. General Blast Report 102
6.1.2. Uploading the Logger Report 103
6.1.3. Combine the Reports of all Blasters 104
6.2. Shut down <Remote> Blasters ..............................................105

Contents
6.3. Re-Entering the Blasting Area ...............................................106

6.4. Misfires in the Muck Pile........................................................106
6.5. Inspection and Cleaning ........................................................107
6.6. Blast Report ..........................................................................108
6.6.1. Check the Blast Report 108
6.6.2. View the Vibration Report 109
6.6.3. Save a Report via USB 109
6.6.4. Contents of a Report 110
7. Blasting with synchronized Blasters 111
7.1. Prepare for a synchronized Blast ..........................................111
7.1.1. Test the Sync Cable 112
7.1.2. Check the Termination Resistor 112
7.1.3. How to connect synchronized Blasters 113
7.1.6. Prepare <Sync Slave> Blasters 116
7.2. Stage 1: Start the Blasting Sequence ....................................119
7.2.2. Activate the <Sync Master> 119
7.2.3. Activate <Sync Slave> Blasters 120
7.2.4. Initialization – Establish the Communication 121
7.2.5. Wrong Number of Synchronized Blasters 121
7.2.6. Check the «Blaster Overview» 122
7.3. Stage 2: Programming the Detonators ..................................123
7.4. Stage 3: Initiate the Blast ......................................................125
7.4.1. Blaster is Ready to Fire 125
8. Testing the Communication 127
8.1. Exit – Shut Down Blasters .....................................................128
8.2. Testing using Radio Modems ................................................129
8.2.1. Antenna Alignment and Position 129
8.2.2. Test Menu 130
8.2.3. Test the Modem – Interface Test 131
8.2.4. Determine the Roles: Transmitter – Receiver 131
8.2.5. Prepare the Receiver for Testing 132
8.2.6. Run the Test on the Transmitter 133
8.2.7. Transmitter: Check all Receivers 133
8.2.8. Transmitter: Test a specific Receiver 135
8.2.9. What does Connectivity indicate? 136
8.2.10. Increase the Radio Distance with a Repeater 137
8.2.11. Testing in a Setup with a <Repeater> 139
8.3. Testing in a Leaky Feeder Network .......................................141
8.3.1. Check the Signal Strength 141
8.3.5. Run the Test on the Transmitter 143
8.3.6. Transmitter: Check all Receivers 144
8.3.7. Transmitter: Test a specific Receiver 145
8.3.8. Monitoring the Noise 146
8.3.9. Traceroute 147
8.4. Testing in a LAN, Wi-Fi, or mobile Network ...........................148

Contents

8.4.2. Test the Interface 148
8.4.3. T1: Signal Test from <Controller> to <Remote> 149
8.4.4. T2: Signal Test <Remote> to <Controller> 150
8.5. Testing the Analog Phone Connection ..................................151
8.5.1. Test Menu 151
8.5.5. Test the Analog Connection 153
9. Blasting with Remote-Controlled Blasters 154
9.1. Prepare for Blasting ..............................................................154
9.1.1. Remote-Controlled Surface Blast 155
9.1.2. Remote-Controlled Underground Blast 156
9.1.4. Prepare <Sync Slave> Blasters 157
9.2. Prepare <Remote> Blasters ..................................................158
9.2.1. Activate <Sync Slave> Blasters 159
9.2.2. Access via Repeater? 160
9.2.4. Write the Remote Dongle 162
9.3. Stage 1: Start the Blasting Sequence ....................................163
9.3.2. Activate the Controller – Establish Communication 164
9.3.3. Choose the Blasting Mode 165
9.3.4. Read the Remote Dongles 166
9.3.5. Check <Sync Slave> Blasters 167
9.3.6. Verify the Numbers of Blasters, Loggers and Detonators 168
9.4. Stage 2: Programming the Detonators ..................................169
9.4.1. Retry Counter 170
9.4.4. Exclude Blasters in <Concurrent> Blasting Mode 172
9.5. Stage 3: Initiate the Blast ......................................................173
9.5.1. Blaster is Ready to Fire 173
9.5.3. Fire the next Blaster 175
9.6. Blasting – Analog Phone Communication .............................176
9.6.1. Stage 1: Start the Blasting Sequence 176
9.6.2. Activate the Controller – Establish Communication 177
9.6.3. Phone Number for Analog Modem Connection 178
9.6.4. Read the Remote Dongle 178
9.6.5. Verify the Numbers of Blasters, Loggers and Detonators 179
9.6.6. Stage 2: Programming Detonators 180
9.6.8. Stage 3: Initiate the Blast 182
10. Errors and Troubleshooting 184
10.1. Self-Test in the Blaster ..........................................................184
10.2. Generate a Backup of the Operating System ........................185
10.3. Errors and Warnings .............................................................186
10.4. Troubleshooting Summary ....................................................196

Contents
10.4.1. Issues while Blasting 196

10.4.2. Detonator Errors 197
10.4.3. Restart the Blasting Sequence 197
10.5. Guidelines on Handling Misfires ............................................198
11. Handling and Disposal 199
11.1. Storage .................................................................................199
11.2. Maintenance .........................................................................199
11.2.1. Cleaning and Checking for Damage 199
11.2.2. Charging the Device 200
11.2.3. Inspection Service 201
11.2.4. Updates and Upgrades 201
11.3. Transport Regulations ...........................................................202
11.4. Disposal ................................................................................202
12. Information 203
12.1. Expressions and Abbreviations .............................................203
12.2. Technical Data ......................................................................205
12.3. Units......................................................................................206
12.4. Orica Service Offices ............................................................206
12.5. Index .....................................................................................207

For your Safety
Purpose of this Manual 1
1. For your Safety

1.1. Purpose of this Manual
This manual describes the operation of the following product or device:
i-kon™ Blaster 3000
The i-kon™III i-kon™ Blaster 3000 is a blasting machine, used to initiate
i-kon™II and i-kon™III electronic detonators in a blast.
The use is restricted to users that have the necessary qualification.

⇒ See chapter Target Group, page 10.
IMPORTANT
READ THESE INSTRUCTIONS BEFORE USE.
KEEP FOR FURTHER REFERENCE.
Non-observance of these instructions, the training and the safety

precautions can result in death or severe injury.
1.1.1. Evolution of i-kon™

i-kon™ is the general trade name of Orica's premium electronic blasting
system.
 The i-kon™ system was first introduced in the year 2000.
 The next generation, the i-kon™II system, which has been available
since 2012, included a newly designed detonator with enhanced
reliability and safety features.
 The latest development, the i-kon™III system, released in early
2017, introduced an improved detonator with better corrosion and
shock resistance. The i-kon™III system is fully compatible with
i-kon™II detonators and equipment, and includes new equipment
with advanced capabilities.
1.1.2. Additional Documentation

This user manual is part of a documentation package for the i-kon™III
blasting system and relates to the documents:
 i-kon™III Technical Data Sheet
 i-kon™III Detonator Material Safety Data Sheet

For your Safety
1 Target Group
1.2. Target Group

1.2.1. Qualification of Owners and Users
Owner The owner is the natural or legal person with authoritative economic
control over the device.
The owner must ensure the following:
 The legal permission to use explosives and blasting equipment is
according to regional requirements.
 Only qualified and authorized personnel operate the device.
 All applicable work safety regulations are adhered to.
 Personal protection equipment is available to the personnel and is
used.
 The staff is instructed regularly about relevant work safety and
environmental protection.
 The staff receives special training in using Orica's electronic
detonators and firing equipment.
User The user is a blaster-in-charge or a shotfirer who has the license to use
explosives according to regional requirements. The user can also be an
assistant who is under the direct supervision of a shotfirer.
Users have the following qualifications:
 Technical training and experience in blasting procedures.
 Certificate of a successful training by Orica authorized trainers in the
use of the specific firing equipment.
 Familiarity with the relevant technical terms and regulations.
 Familiarity with the latest manuals and the safety instructions
contained therein.
 Ability to evaluate assigned tasks, identify potential hazards and take
appropriate safety precautions.
1.2.2. Duty to perform Maintenance and Service

 Operate the device only when it is in perfect working condition.
 Return the device to Orica for maintenance at time intervals
indicated on the inspection tag.
For instructions on maintenance, see chapter Maintenance, page 199.
1.2.3. Duty to report Faults and Damages

The user has the responsibility to check the all equipment for
noticeable damage or defects before use.
 Report any damages, or changes in operating behavior,
immediately to the Orica Service.

For your Safety
About this Manual 1
1.3. About this Manual

This document is written for the international market in U.S. spelling. We
apologize to all other English-speaking users.
1.3.1. Structure and Meaning of Safety Messages

Safety messages inform about potential hazards and give instructions to
avoid injuries.
Figure 1 Elements of a safety message
① Signal word (here DANGER) ④ Possible consequences

② Safety symbol ⑤ Instructions for avoiding the danger
③ Type and source of danger
Safety messages have three hazard levels depending on the degree of

danger:
Table 1 Signal words and colors
DANGER DANGER indicates an immediate danger that if not avoided, will
result in death or severe, permanent injury.
WARNING WARNING indicates a potentially hazardous situation that if not

avoided, could result in death or severe, permanent injury.
CAUTION CAUTION indicates a potentially hazardous situation that if not

avoided, could result in minor, nonpermanent injury.
Table 2 Safety symbols

Danger Electric Shock
Explosion Hazard Laser Beam
Electromagnetic disturbance
1.3.2. Safety Instructions

Safety instructions indicate safe work practices.
SAFETY INSTRUCTIONS
 Here you find for example reminders of safety procedures.
 Location of safety equipment.

For your Safety
1 About this Manual
1.3.3. Notations used in the Manual

NOTICE
A NOTICE indicates possible damage to property or data!
 Instructions to avoid the problem.
A mandatory notice contains information that must be observed.
Recommended procedures give instructions of best practice that

should be followed.
A general notice is a piece of information to improve understanding,

lists tips and tricks, or provides a quick start guide.
1.3.4. Step by Step Instructions

Procedural instructions describe steps that the user must execute
sequentially.
1. [Main Menu ► Setup]
That means: In the "Main Menu" choose "Setup".
Interim results and reactions of the system are written in italics.
2. Continue with second step.
An embedded safety message appears at the step where you must
follow it:
DANGER
 Do NOT do this or that.
3. Take the final step.

 The curved arrow marks the result.
Short Instructions can have a quick start guide:

 First step.
 Second step.
Alternative procedures or application rules are listed in a table.

Example:
[BACK] Quit the function.
[CONFIRM] Confirm the function.

For your Safety
Intended Use 1
1.4. Intended Use

The i-kon™ Blaster 3000 can be used in various blast configurations, with
different communication media in surface and underground mining
operations.
Prerequisites:
 All detonators are logged in i-kon Loggers.
The Blaster 3000 needs a Logger to communicate with detonators.
Configurations:
 Standalone Blaster
- The Blaster 3000 configured as <Single> Blaster controls directly
connected Loggers via firing cable.
 Synchronized Blasters
- A Blaster 3000 configured as <Sync Master> controls other
Blasters that are configured as <Sync Slaves>.
- <Sync Master> and <Sync Slave> Blasters are connected to the
same sync cable.
- Each Blaster is connected to Loggers with detonators.
 Remote-controlled Blasters
- A Blaster 3000 set up as <Controller> controls other <Remote>
Blasters via radio, LAN, WiFi, analog phone or Leaky Feeder
communication.
- <Remote> Blasters can have <Sync Slave> Blasters connected
via sync cable.
- Each Blaster is connected to Loggers with detonators.
 Repeater in surface applications
- A Blaster 3000 set up as <Repeater> increases the radio
distance to <Remote> Blasters.
- A <Repeater> is NOT connected to Loggers or detonators.
- A <Repeater> does not initiate a detonator.
1.5. Non-observance of Safety Regulations

Orica is not responsible for damage caused by non-observance of the
training instructions and the user manual, and improper use.
Non-observance can result in death or severe injuries.

To prevent hazards, follow safety regulations:
 Always comply with applicable federal, state and local regulations
relative to the proper usage of explosives.
 Always observe company safety regulations and accident prevention.
 Follow Orica safety instructions explained during training and in the
user manual.

For your Safety
1 Improper Use
1.6. Improper Use

This device complies with the generally accepted rules of technology and
standards and has a high standard of operational reliability. However, this
device may pose a hazard if used improperly or for purposes, it was not
designed for.
Improper use of blasting equipment will result in death or severe
injuries.
To prevent this hazard, follow these instructions:
 NEVER expose the blasting equipment to conditions that do not meet
the prescribed requirements.
 NEVER use blasting equipment with out-of-date firmware versions or
expired inspection tag.
 NEVER use defective blasting equipment, or blasting equipment with
loose or missing parts.
 NEVER use blasting equipment for applications that have not been
explicitly approved by Orica. For example, if detonators of various
brands and types are used together.
 NEVER modify or use modified blasting equipment that are not in
accordance with the original condition of the product.
 ALWAYS react appropriately to information, warnings and error
messages that are given by the product.
Wrong handling of detonators can result in death or severe

injuries.
To prevent hazards, follow these instructions:
 ALWAYS observe the Safety Data Sheet of the detonators.
 Avoid an initiation by friction, impact, shock, heat (FISH) or other
sources.
 ALWAYS keep explosives out of reach of unauthorized persons.
 NEVER open or disassemble detonators, or firing equipment.
 ALWAYS use personal protection equipment.
 When a thunderstorm approaches, initiate the blast immediately.
 Alternatively, evacuate, guard the site, and wait until the danger has
passed.
A detonator can initiate unintendedly when it is connected to

equipment that is NOT specifically approved.
To prevent this hazard, follow these instructions:
 Use i-kon™III equipment only with i-kon™II and i-kon™III detonators
according to the Technical Data Sheet (TDS).
 NEVER use i-kon™III equipment with detonators of other brands and
types.
 NEVER use i-kon™II and i-kon™III detonators together with other
electronic or electric detonator brands.
The manufacturer and supplier are not liable for damage that results
from improper use. The user alone assumes all associated risks.

For your Safety
Product Safety 1
1.7. Product Safety

1.7.1. Standards and Directives
The standards and directives used in the development, production and
configuration are listed in the Declaration of Conformity.
1.7.2. Safety Concept

The i-kon™III System is designed with very high safety measures:
 i-kon™II and i-kon™III detonators have protective structures in
their electronic circuit. Therefore, the detonators are highly resistant
to stray currents, over voltage, static electricity, and electromagnetic
radiation. The unique identity number on the detonator label allows
full traceability.
 i-kon™II and i-kon™III detonators are fully compatible.
 The first generation i-kon™ detonators are no longer supported,
and if they are connected to i-kon™ Loggers, they are not functional,
but connecting cannot cause any hazard.
 i-kon™ Loggers are "inherently safe". Even under fault conditions,
Loggers do not have enough current or voltage to initiate i-kon™II or
i-kon™III detonators.
 i-kon™ Blasters provide the firing code and sufficient energy to
initiate i-kon™II and i-kon™III detonators.
Only when the blasting area is evacuated, then Blasters may be

connected to the detonator network.
For blasting, the i-kon™II Blaster 3000 is installed in a safe location.

 When switched on, a Blaster continues only when it passes the self-
test.
 Remote-controlled blast:
- A remote-controlled Blaster generates a digital encrypted code
and writes it to the Remote Dongle.
- The controlling Blaster reads the Remote Dongle and establishes
a communication.
- The communication is protected against corruption and
manipulation.
 Synchronized Blasters are connected via the same sync cable.
 Initiation on the controlling Blaster:
- The shotfirer needs a special Master Dongle to charge and fire
the detonators.
- All Blasters provide the programming voltage to their detonators
and communicate with them.
- All Blasters check the system limits, display errors, and abort the
blasting sequence if necessary.
- When the programming is successful, the shotfirer can issue the
fire command.

For your Safety
1 Training
1.7.3. Keep-Alive Counter
A Blaster returns to standby mode if it loses the connection to the

controlling Blaster.
The controlling Blaster (<Controller> or <Sync Master>) sends signals to

all other Blasters that trigger their Keep-Alive Processor (KAP).
 The KAP is a timer that counts down 90 seconds.
 Every few seconds, the controlling Blaster sends the signal that
restarts the KAP timer in all Blasters.
 If a Blaster does not receive one of these signals during the
countdown, because the communication is disrupted, the KAP timer
expires. This Blaster switches off the output voltage and aborts the
blasting sequence.
1.8. Training
Electronic detonators differ dramatically from conventional electric or
non-electric detonators. Orica's i-kon™II and i-kon™III electronic
detonators and equipment must not be used without appropriate
training.
Lack of knowledge can result in death or severe injuries!

 Read and understand the Material Data Sheet and the Safety Data
Sheet of the device or system.
 Always use blasting equipment according to its Instructions for Use
and within its specified technical limits.
 Follow the recommended procedures specified during training.
Orica authorized training:

 Only persons who are trained successfully on the described system
or device have the qualifications to operate it under normal
conditions and emergency situations.
To arrange for training, please contact your regional Orica service office.
⇒ See chapter Orica Service Offices, page 206.

For your Safety
Hazards and Risks when Using the Product 1
1.9. Hazards and Risks when Using the Product

The purpose of devices for civil blasting is to initiate explosives. Therefore,
they constitute a potential hazard to people and property.
Hazards that cannot be eliminated by design features or protective
mechanisms are indicated in this document.
1.9.1. Hazards when connecting a Defective Logger

If you connect a defect detonator to a defect Logger, then the
detonator can initiate unintendedly.
To prevent this hazard, follow this chronological order:
 Switch on the Logger.
 After the Logger has passed its self-test, connect the detonator or the
detonator network to the Logger.
 Check that the cable is properly connected to the output terminals.
1.9.2. Hazards when using a Defective Blaster

A Blaster provides the energy to initiate those detonators that are directly
connected to it.
If you connect a defect Blaster to a Logger, then detonators could

initiate unintendedly.
To prevent hazards, follow this chronological order:
 Evacuate and guard the blasting area.
 Switch on the Blaster and wait until it passes its self-test.
 Then connect the Blaster to the detonator network.
 In general, send the blasting equipment for service regularly.
1.9.3. Hazards in a Remote-Controlled Blast

A remote-controlled blasting system consists of a controlling Blaster
(Controller) and at least one remote unit (Remote Blaster or Synchronized
Blaster). The Controller controls the blast from a place of safety; the other
Blasters are positioned near the blast site.
Remote-controlled or synchronized Blasters:
To prevent hazards and damage to the wiring, follow this chronological
order:
 Evacuate and guard the blast site.
 Switch on the Blaster and wait until it passes its self-test.
 Connect the Blaster to its detonator network.
Controller:
To prevent hazards, follow this chronological order:
 Evacuate and guard the blasting area.
 Switch on the Controller and wait until it passes its self-test.
 Then you can start the blasting sequence.

For your Safety
1 Hazards and Risks when Using the Product
1.9.4. Re-Entering the Blasting Area

People entering the blasting area too soon after a blast can be
severely injured.
Follow this sequence:
 Remove the dongles.
 Disconnect the firing cable.
 Wait at least 5 minutes.
 Follow local regulations for re-entering the blasting area.
1.9.5. Risk of Misfires in the Muck Pile

Misfires are explosive charges that failed to detonate after an attempt of
initiation.
Misfires can initiate and cause severe injuries or death.
To prevent misfires, follow these instructions:
 ALWAYS check the wires and connections.
 ALWAYS run the wires to minimize the chances of wire damage due
to vehicles, people and falls of ground.
 ALWAYS secure the firing cable.
 ALWAYS test all detonators.
 ALWAYS verify that you have registered all detonators.
 NEVER connect detonators that should NOT fire in the blast.
 ALWAYS verify the number of detonators.
 Verify that you know exactly which detonators have errors.
 NEVER fire if a lot of detonators have errors.
1.9.6. Hazards caused by Unlogged Detonators

Unlogged detonators (Globals) endanger the safety and success of
the blast by flyrock and vibration, or misfires in the muck pile.
To prevent misfires, follow these instructions:
 Log all connected detonators.
 Test the detonators in each Logger.
 Check the setting to fire or not fire unlogged detonators in each
Logger.
 Check the setting for unlogged detonators in the controlling Blaster.

For your Safety
Information in Case of Emergency 1
1.9.7. Hazards by a Strike of Lightning

Lightning can ignite explosive charges and result in death or severe
injuries.
 When a thunderstorm approaches, then fire the blast immediately.
 Optionally evacuate, guard the site, and wait until the danger has
passed.
1.10. Information in Case of Emergency
In case of an emergency, pull the dongle.
As long as you have not pressed the FIRE button, you can abort the
blasting sequence.
 Remove the dongle at the Blaster and all detonators immediately
return to a safe voltage level.
 It is also safe to disconnect the firing cable between the Blaster and
the Loggers, or to switch off the Blaster. The Loggers switch off after
a short timeout and the detonators discharge safely.
Orica provides an emergency response service:

 Australia: 1800 033 111
 New Zealand: 0800 734 607
 International: +61 3 9663 2130

About the Device: i-kon™ Blaster 3000
2 Components of the Blasting System
2. About the Device: i-kon™ Blaster 3000

2.1. Components of the Blasting System
The i-kon™III Electronic Blasting System (EBS) is a system to initiate
electronic detonators.
i-kon™ Hardware:
 i-kon™II and i-kon™III electronic detonators
 Logger (I), device for logging and testing 200 detonators that can be
initiated via Blaster 400 and Blaster 3000
 Logger II, device for logging and testing 500 detonators that can be
initiated via Blaster 3000
 Blaster 400, device to initiate 400 detonators
 Blaster 3000, device to initiate 3000 detonators
- 7 units Blaster 3000 can be combined to initiate up to 21000
detonators
Software:
 SHOTPlus™ Suite, blast design program
Figure 2 i-kon™ components
① Detonator ④ Blaster 400

② Logger II ⑤ Logger I
③ Blaster 3000
For underground applications, the Blaster 3000 can initiate eDev™II

detonators under the following conditions:
 Loggers are replaced by units of the eDev™II Blast Box 610C.
 Note the other properties of the eDev™II detonators.
⇒ Refer to the instructions for use of the eDev™II Blast Box 610C.

Functions of the Blasting Equipment 2
2.2. Functions of the Blasting Equipment

The i-kon™III system is suitable for complex blasts at large surface and
underground operations in challenging environments.
The i-kon™III system consists of programmable, electronic detonators

and controlling equipment.
 i-kon™II and i-kon™III detonators are fully programmable.
- A detonator has its own energy storage and a timing circuit.
Therefore, the detonator is independent after it receives the fire
signal.
- Each detonator has a unique identification number (Det-ID)
written to its chip during manufacture. This Det-ID is the basis for
communication between detonators and control equipment.
 A harness wire connects the detonators to a Logger.
 A Logger stores the delay time of the detonators and performs
testing functions.
- When a detonator is connected to the Logger, the Logger reads
and stores the unique detonator identification number (Det-ID).
- The user assigns the delay time.
- The Logger tests detonators and the detonator network.
- The Logger measures the leakage current. If the leakage current
is too high, the Logger announces an error.
- For safety reasons, the Logger cannot initiate a detonator.
 A firing cable connects the Loggers to the Blaster.
 A Blaster programs the detonators and initiates the blast.
- The Blaster uses the Logger to communicate with the detonators.
- The Blaster announces all system or detonator errors.
- The Blaster lists the number of Loggers and detonators.
- The Blaster provides the firing voltage, which passes through the
Loggers, to the detonators.
- After the blast, the Blaster generates a report with information
about the parameters, the Loggers, and errors.

2 Properties and System Limits
2.3. Properties and System Limits

2.3.1. System Limits
Resistance and leakage current can cause a voltage drop that exceeds
the system limits.
The following limits are valid under ideal conditions and no leakage:
Table 3 Blaster 3000 limits
Logger types  Logger I version 5.22e or later
 Logger II version 1-5-24 or later
 eDev™II Blast Box 610C 5.04a or later.
Loggers Up to 12 Loggers per Blaster
Detonators Up to 3000 detonators per Blaster
Max. delay time = 30000 ms
Harness wire per Resistance < 280 Ω
Logger ≈ 2000 m (=1.24 mi) standard harness wire
Blasters Up to 7 Blasters in one blast
= max. 21000 detonators
Output voltage 24 V
Voltage drop < 4 V on the firing line
Loggers must be supplied with 20 V.
Remote control  One Controller, 6 Remotes, 6 Repeaters
Radio distance under ideal conditions when
there are no obstacles within a radius of 8 m
(24ft.) around the line of sight between the
antennas.
 Distance < 2.5 km (1.6 miles)
Synchronized blast One Master, 6 synchronized Blasters
Sync cable < 70 Ω ≈ 500 m (=1600 ft) standard
harness wire
A warning appears if you operate different Logger types on one

Blaster.
Communication problems may occur. In the worst case, the Blaster
does not recognize all Loggers or aborts the blasting sequence.
 Verify the numbers of Loggers displayed in the overview.
2.3.2. Firing Cable

Maximum resistance of the firing line:
 70 Ω, when using delay times up to 30000 ms
(= 500 m harness wire)
 140 Ω, when using delay times up to 15000 ms

Properties and System Limits 2
2.3.3. Properties and Environmental Conditions

Properties:
 Dimensions: ~30 cm x 34 cm x 15 cm (~12” x 13” x 6”)
 Weight: ~4.8 kg, 11 lb.
 Sealing: Case is water and shock resistant.
(Ingress Protection rating: IP 54 open case, IP 65 closed case)
Table 4 Temperature range

Operating Transport / Storage Charging
-20 – +60°C -30 – +60°C 0 – 60°C
-4°F – 140°F -22°– 140°F 32°– 140°F
This device contains Lithium-Ion batteries; weight 506 g (1.12 lbs.).
⇒ For more information, see chapter Transport Regulations, page

202.
2.3.4. Product Identification

The identification plate of the product is at the back of the device or inside
the top cover.
Figure 3 Identification plate
① Product name ④ Country of origin, year of production

② Purpose ⑤ Certification
③ Serial number, hardware version

2 Properties and System Limits
2.3.5. Electronic Detonators

Use only i-kon™II and i-kon™III detonators.
To prevent misfires:
 NEVER use detonators of other brands and types with i-kon™
equipment.
 NEVER use i-kon detonators of previous generations.
Detonator properties:
 Programmable up to 30000 ms
 Precision as coefficient of variation: 0.005%
 Output strength:
- Equivalent to a reference detonator #3 according to the
European standard EN13763-15
- Equivalent to a No.8 blasting cap according to the definition of
"blasting agent", ATF Federal Explosives Law and Regulations,
§555.11 Meaning of terms
 Storage life is up to 2 years in an approved magazine.
Table 5 Temperature range

Operating Storage Transport
-20 – +70°C -20 – +50°C -40 – +65°C
-4°F – 158°F -4°– 120°F -40°– 150°F
⇒ For more information, refer to the detonator's technical data sheet.
For underground applications, the Blaster 3000 can initiate eDev™II

detonators under the following conditions:
 Loggers are replaced by units of the eDev™II Blast Box 610C.
 Note the other properties of the eDev™II detonators.
⇒ Refer to the instructions for use of the eDev™II Blast Box 610C.
System limits:
 Up to 12 units eDev™II Blast Box 610C with a total of 3000
detonators may be connected to one Blaster.
 Up to 800 detonators per Blast Box.
 NEVER operate units of eDev™ II Blast Box 610C and i-kon™
Loggers together on the same Blaster.
- These different units can create communication problems that
can interrupt the blasting sequence.
- In the worst case, a Logger or Blast Box cannot be detected.

Principle of Operation 2
2.4. Principle of Operation

2.4.1. Single Blaster
A single Blaster initiates the detonators of Loggers that are connected to
the Blaster's black output terminals.
Figure 4 Setup with a single Blaster
① Single Blaster in a place of safety ② Hazard area during the blast

during the blast
③ Firing cable connected after the Blaster passes
its self-test.
Connect only one Logger type to the Blaster.
① <Single> Blaster ② Loggers connected via firing cable

2 Principle of Operation
2.4.2. Synchronized Blasters

In a synchronized blast, the Blasters are connected to the same sync
cable. Connected Blasters fire at the same time.
 If one Blaster has a serious error, all Blasters abort the blasting
sequence.
 The controlling Blaster is called <Sync Master>.

- Loggers can be connected to the black output terminals.
 Dependent Blasters are called <Sync Slaves>.
- Loggers must be connected to the black output terminals.
 The <Sync Master> controls up to 6 <Sync Slave> Blasters that are
connected to the same sync cable via the yellow sync terminals.
Figure 6 Synchronized blast configuration
① <Sync Master> in a place of safety ④ Synchronization cable (sync cable) on

② <Sync Slave> 1 yellow output terminals
③ <Sync Slave> 2 – 6 ⑤ Firing cable to Loggers

Principle of Operation 2
2.4.3. Remote-Controlled Blasters

In a basic configuration for a remote-controlled blast, the <Controller>
Blaster controls up to 6 <Remote> Blasters.
 The <Remote> Blasters must have Loggers connected to their output
terminals.
 The <Controller> may have Loggers connected to its output
terminals.
Figure 7 Blast setup with RF modems
① <Controller> Blaster in a place of ② <Remote> Blaster (1 – 6)

safety ③ Firing cable to Loggers
Radio modems operate at a specific center frequency that is different for

each country. The country or region, and the center frequency are written
on the identification plate of the firing device.
Table 6 Examples of center frequencies
Country or region Center frequency
Australia 410.825 / 411.000 MHz
USA 469.000 MHz
European Union 869.0125 MHz / max. 500 mW
Each command is encrypted and includes a unique, random code.

 If another device operates at the same frequency, a blast cannot
be initiated accidentally.
 Devices operating at the same frequency can disturb each other,
so that the communication takes longer.

2 Principle of Operation
2.4.4. Controlling Multiple Blasters

The controlling Blaster <Controller> can control up to 6 other Blasters.
 Configuration of the other Blasters:
- <Remote> Blasters are controlled wirelessly.
- <Sync Slave> Blasters are connected to the <Controller> or a
<Remote> Blaster via sync cable.
FIRE characteristics:
 <Remote> Blasters fire depending on the blasting mode chosen in
the <Controller>: one after the other (automatically), nearly at the
same time (concurrent), or manually chosen.
 In a remote group, consisting of a <Remote> Blaster and connected
<Sync Slave> Blasters, the Blasters fire at the same time.
Figure 8 Controlling multiple Blasters (Example)
① <Controller> ④ <Sync Slave> to ③

② Remote group ⑤ Directly connected Loggers
③ <Remote> Blaster controlling a <Sync ⑥ <Sync Slave> to ①
Slave> Blaster ④

Underground Applications 2
2.5. Underground Applications

The Blaster 3000 can be used in underground operations, to initiate a blast
remotely from the central firing office of a mine.
Figure 9 Centralized firing configuration
① <Controller> connected to the modem ④ <Remote> Blaster near blast site

via radio or cable
② Modem, network, phone ⑤ Optional, <Sync Slave> Blaster
③ Communication method: LAN, Wi-Fi, Leaky feeder, analog phone
System configuration:
 The controlling Blaster <Controller> is installed at the central firing
office.
 Up to 6 <Remote> Blasters (with or without <Sync-Slave> Blasters)
are installed near the Loggers and their detonator networks.
 The following communication methods are available:
- Local Area Network (LAN)
- Wireless network (Wi-Fi, WLAN)
- Leaky Feeder network
- Analog phone
2.5.1. Communication via Analog Phone

When using an analog phone, the <Controller> can communicate with one
remote group consisting of a <Remote> Blaster and up to 5 connected
<Sync Slave> Blasters.
To fire more Blasters, you can prepare other remote groups, where the
<Remote> Blaster has a different phone number. You can fire the remote
groups one after the other.

2 Underground Applications
2.5.2. Leaky Feeder Network

When using a Leaky Feeder (LF) infrastructure, the Controller can
communicate via Leaky-Feeder cable, or can be connected directly to the
LF headend.
a) Controller communicates via Leaky-Feeder Cable

The following configuration is the most flexible, because it does NOT
require a direct access to the headend from the central firing office.
 The Orica HE router (headend router, sometimes called repeater) is
connected to or built into the headend.
 All Blasters have a LF modems installed and are exchangeable.
 All Blasters need a direct access to the Leaky-Feeder network.
Figure 10 Leaky Feeder 3-modem configuration
① <Controller> at central firing office ④ Orica LF router (repeater)

② RF antenna connected to headend ⑤ <Remote> Blaster in the mine
③ Leaky Feeder headend ⑥ <Remote> Blaster in the mine
The “3-modem configuration” requires three LF modems for the

communication between the <Controller> and one <Remote> Blaster:
 1 modem for: <Controller<, <Remote> Blaster and the headend.

b) Controller is connected via LAN to the Headend

The following application is generally used when no spare radio license is
available on the surface, but the central firing office has a LAN connection
to the communication room where the headend is installed.
 The HE modem (headend modem) is connected directly or built into

the headend.
 The <Controller> is connected via LAN to the HE modem.
 The <Controller> does not require a LF modem.
 The <Remote> Blasters are fitted with LF modems to communicate
with the LF system.
Figure 11 Leaky Feeder 2-modem configuration
① <Controller> at central firing office ④ <Remote> Blasters in the mine

② Leaky Feeder headend (HE) ⑤ <Remote> Blasters in the mine
③ Headend modem, HE modem
This “2-modem configuration” requires two LF modems for the

communication between the <Controller> and one <Remote> Blaster:
 1 modem for each: <Remote> Blaster and the headend.

2.5.3. Configuration with LAN

To use the local network (LAN) you need a LAN switch which is a
networking hardware device that allows a Blaster to connect to the local
network.
 The controlling Blaster, the <Controller>, is installed at the central
firing office and connected to the LAN.
 The LAN switch is installed in a communication room.
 <Remote> Blasters are connected to the network sockets.
Figure 12 Setup with a LAN access
① <Controller> ③ <Remote> Blaster, LAN setting

② LAN switch ④ <Remote> Blaster, LAN setting

2.5.4. Configuration with Wi-Fi

To use Wi-Fi, you need a wireless access point (WAP, or AP) which is a
networking hardware device that allows a Blaster3000 to connect to the
wireless network.
 The controlling Blaster is the <Controller> ①.
 The Controller is connected to the AP ③ via a LAN cable ② or
wirelessly.
 <Remote> Blasters ④ and ⑤ are connected via Wi-Fi.
Figure 13 Configuration with Wi-Fi
① <Controller> ④ <Remote> Blaster, Wi-Fi setting

② Optionally, LAN connection to AP ⑤ <Remote> Blaster, Wi-Fi setting
③ Wi-Fi access point (AP)
If the signal strength is not good enough, you can include a second access
point.
Figure 14 Configuration with a second access point
① <Controller>
② Wi-Fi access point (AP) ④ <Remote> Blaster, Wi-Fi setting
③ Wi-Fi access point (AP) ⑤ <Remote> Blaster, Wi-Fi setting

2.5.5. Configuration with multiple Blasters

The configuration below shows a complex system configuration:
 The controlling Blaster is the <Controller>.
 You can connect Loggers to the <Controller>.
 You can install up to 6 other units as <Remote>, or <Sync Slave>
Blasters.
 The <Controller> and each <Remote> Blaster can be connected via
LAN or Wi-Fi.
Figure 15 Complex setup
① <Controller> ⑤ Wi-Fi access point (AP)

② Wi-Fi access point (AP) ⑥ <Remote> Blaster, Wi-Fi
③ <Remote> Blaster, LAN ⑦ <Remote> Blaster, Wi-Fi
④ <Sync Slave> Blaster ⑧ <Sync Slave> Blaster
Example:
 The <Controller> ① can be connected to the access point ② of the
wireless network via LAN (dotted line) or Wi-Fi.
 The <Remote> Blaster ③ is connected via LAN.
 The <Sync Slave> Blaster ④ is connected via sync cable to the
<Remote> Blaster ③.
 The second access point ⑤ is situated for example somewhere in
the mine where it has a connection the first access point ②.
 The <Remote> Blasters ⑥ and ⑦ are connected via Wi-Fi.
 The <Sync Slave> Blaster ⑧ is connected via sync cable to the
<Remote> Blaster ⑦.

Accessories 2
2.6. Accessories
2.6.1. Product Overview
Figure 16 Blaster 3000 overview and connections
① Pressure purge ④ Radio antenna socket

② Connection for power supply unit ⑤ Firing line to connect Loggers
③ LAN connection ⑥ Sync terminals (yellow) for sync cable to
connect slave Blasters
2.6.2. Output Terminals – Sync Terminals

The Blaster 3000 has two sets of terminals:
 Connect synchronized Blasters via the yellow sync terminals that are
on the left side of the case.
 Connect the Loggers via the black output terminals that are at the
back of the case.
NOTICE
If you connect to the wrong terminals, Blasting is not possible!
 Connect Loggers via the black output terminals.
 Connect slave Blasters via the yellow sync terminals.

2 Accessories
2.6.3. Master Dongle and Remote Dongle

The Blaster 3000 has two “Dongles”:
 The red Master Dongle is necessary to start the blasting sequence
on the commanding Blaster.
 The blue Remote Dongle is programmable and holds the access
data of a Remote Blaster.
Figure 17 Dongles
① Red, Master Dongle ② Blue, Remote Dongle
Dongles must be permanentely in the safe possession of the shotfirer.

 Take all dongles with you when the blast is postponed or aborted.
 Keep spare dongles locked in a safe place.
Master Dongle
 The red marked Master Dongle is needed to control the blasting
sequence and to fire the blast.
 You need only one red Master Dongle in a blast.
Remote Dongle
The blue Remote Dongle is programmable and holds the access data of
a <Remote> Blaster.
 You need a Remote Dongle for each <Remote> Blaster in the blast.
 After the <Remote> Blaster is activated, it writes its access codes on
the blue Remote Dongle.
 You must physically carry the Remote Dongle to the <Controller> to
transfer the access codes.
 You cannot fire a blast with a blue Remote Dongle.
When you use multiple Remote Blasters in one blast, avoid mixing up
the Remote Dongles.
 Label each Remote Dongle with the Blaster ID.

Accessories 2
2.6.4. Antenna
When blasting remote, then connect the supplied portable antenna to the
antenna socket on the case.
NOTICE
The Blaster will not work with the wrong antenna!
 Only use the delivered antenna with the Blaster.
 Antenna must meet the allowed frequency range.
To install the antenna approximately 1 m (3 ft.) above the ground, use an

antenna extension cable and mount the magnetic base of the antenna
cable on a tripod.
Figure 18 Antenna cable and magnetic base
① Magnetic base and extension cable ② Tripod
2.6.5. Sync Cable

The sync cable is used to transfer data between <Sync Slave> Blasters
and their common, controlling Blaster.
Specifications:
 Copper wire, for example harness wire
 Diameter 0.6 mm ±0.013 mm
 Resistance ≃ 0.07 /m
2.6.6. Pressure-Compensating Valve

To protect the electronic components, the housing has a pressure-
compensating valve. The valve equalizes the air pressure from inside the
unit to the external pressure, but prevents dirt and water from entering.

2 Operating Keys and Connections
2.7. Operating Keys and Connections

2.7.1. Front Panel
Figure 19 Blaster3000 front
① Display ⑤ Battery symbol for charging

② Function keys ⑥ Power switch ( on / off)
③ Navigation keys ⑦ Dongle port
④ Numerical keys ⑧ USB port
2.7.2. Operating Keys

The table lists the main functions of the operating keys. Special functions
are described in the appropriate chapters.
Table 7 Operating keys
Function key [F#1] – [F#3]:
 Function is indicated in the last line of the display
Navigation:
 [▲] = up
 [▼] = down
 [◄] = left
 [►] = right
Numerical keys [0] – [9]
[✔] for confirmation
Delete a character

Operating Keys and Connections 2
2.7.3. Audible Signals

Certain functions of the device can give audible signals and warning
beeps. These beeps consist of short and long sounds. In this manual, a
"short-short-short-long" beep looks like "∘ ∘ ∘ – ".
2.7.4. Charging Unit

The device is supplied with a charger.
Specification:
 Mains power source (90 – 230 V, 40 – 60 Hz)
2.7.5. Charging Indicator Light

The indicator light in the battery symbol on the front illuminates when the
Blaster is connected to the power supply.
Figure 20 Charging indicator
 The device can be stored while connected to the charging unit.

 You can operate the Blaster in a blast while the Blaster is connected
to the power supply.
Charge the batteries for at least 4 hours.

 If you switch on the device, the time for charging is longer.

Operation and Settings
3 Operating the Device
3. Operation and Settings

3.1. Operating the Device
WARNING
A detonator can initiate if device and detonator have major defects,
and all devices are connected to each other!
Death or severe injuries
 ALWAYS wait until the device passes its self-test.
 NEVER connect the device to the detonator network before the
device passed its self-test.
 NEVER use a device that fails its self-test.
3.1.1. Switching on and Self-Test

How to switch on
Prerequisites:
 NO firing line is connected to the output terminals.
 NO other Blaster is connected to the sync terminals.
 NO Dongle is connected.
 To switch on the device, turn the power switch to the right.

The Blaster runs a self-test.
 The start menu appears.
When the self-test is passed, the display shows the allowed detonators.
Figure 21 Allowed detonators
 After a few seconds, the start menu appears.
Use only i-kon™II and i-kon™III detonators.
⇒ For information on error messages, please refer to the chapter

Errors and Troubleshooting, page 184.

Operating the Device 3
3.1.2. Switch on while in Standby Mode

When a <Sync Slave> or <Remote> Blaster is prepared for blasting, it can
be in <sleep> or in <standby> mode.
 For a Blaster in standby mode, the display shows <Standby>.
 For a Blaster in sleep mode, the display is off.
If you are unsure, whether you have already prepared a Blaster for
blasting, then check the mode as follows.
 Switch on the Blaster.
 If the screen shows the start menu, the Blaster is not prepared.
If the Blaster was prepared for blasting, it goes into standby mode.
Figure 22 Status Standby
Bxx: Standby
<Bxx>, Blaster ID
 To abort the standby mode, press [ABORT].
Display shows the start menu.
 To use the current mode, do NOT touch any key.
 Blaster's mode is checked.

3.1.3. The Start Menu

When switched on, the display shows the start menu:
Figure 23 Start menu
① Blaster ID and battery ③ Functions

② Blaster mode ④ Instructions for blasting
 The Blaster's ID number is written in the battery symbol.

 The green part of the battery symbol indicates the charge level of the
battery.
 The first line shows the Blaster's mode and the current time.
 The middle of the screen shows instructions for the operator to start
the blasting sequence. The instructions depend on the chosen
Blaster mode.
 At the bottom of the screen functions allow to adjust and check the
settings, and [OK] to start the blasting sequence. To activate a
function, press the button below.
Table 8 Functions
[MENU] Enters the main menu to configure and test the Blaster, or
check the reports.
See chapter The Main Menu, page 43.
[INFO] Displays the Blaster's parameters.
See chapter Information about the Settings, page 45.
[OK] Starts the blasting sequence.
See chapter Blasting, page 70.
3.1.4. How to Switch off the Blaster
To switch off the device, turn the power key to the left.

3.1.5. The Main Menu

1. In the start menu. press [MENU]
Figure 24 Main menu
 The main menu provides functions to configure the settings, to check

the reports or to run tests on the remote configuration.
Table 9 Navigation
[▲] or [▼] Select an item in the menu.
[ENTER] Enter the selected function.
[BACK] Quit and return to the previous function.
“…” The item offers a submenu.
Table 10 Available functions

Testing Testing the communication between Blasters
Testing the Communication, page 127.
Reports Check the blast reports
Blast Report, page 108.
Setup Adjust the settings
Configuring the Device, page 48.
Alias Give the Blaster a specific name
Assign a Name (Alias) to the Blaster, page 47.
About Blaster Check information about the Blaster
Blaster Firmware Information, page 46.
3.1.6. How to return to the Start Menu
Use the function key [F#1] = [BACK], to return to the previous menu.

3.1.7. Functional Overview

The following diagram shows available menus and functions.
Figure 25 Menu structure
Start Menu Initialize the Blast

Connect Loggers
and <Sync Slave> Main Menu
press [OK]
Testing ... Testing
INFO Dependent on modem
Reports
MENU Controller to Remote
About Blaster
Remote to Controller
Alias
Interface test
Setup ...
Setup Menu
Blaster Interface ... System ...
Blaster ID Modem Date / Time

Blaster Mode Leaky Feeder Language ...
Max. error allowed Analog phone Display
Allow Globals LAN Setup PIN
Vibration monitor WLAN Factory Settings ...
Sync Line Update Firmware
3.1.8. Check the Charge Level of the Battery

The colored part of the battery symbol in the first line shows the battery
charge level.
Figure 26 Battery charge level
 If the color changes to yellow or red, you must charge the device.
 To see the percentage of the battery level, choose [INFO].
For blasting, a Blaster needs at least a battery charge level of 30%.
⇒ For more information, see chapter Charging the Device, page 200.

3.1.9. Information about the Settings

You can check the important parameter and settings of the Blaster.
► In the start menu, press [INFO].
Figure 27 Information
Table 11 Standard information

Parameter Description
Alias Name of the Blaster
Blaster Mode <Single>, <Controller>, <Remote>, <Sync Master>,
<Sync Slave>
Max. Errors Maximum errors allowed. If the Blaster detects more
errors, it aborts the blast.
Allow global detonators When Globals (unlogged detonators) are not allowed,
then the Blaster aborts if it finds Globals.
Note: The setting of the controlling Blaster
(<Controller>, <Sync Master>) is valid for all Blasters.
Termination Resistor Resistor at the end of the sync cable.
Battery Battery level
Firmware Version Version of the current firmware
The other data depends on the remote interface setting of the Blaster.
For the description of the parameter, see chapter Interface Settings,
page 55.

3.1.10. Blaster Firmware Information

You can check the Blaster's firmware data.
[MENU ► About Blaster]

Figure 28 Information
The display shows hardware, firmware information, and settings:

 Serial number
 GUI / Backend, Graphic User Interface
 Logger Interface, communication with the Loggers
 KAP: Keep alive processor
 Logger firmware requirements
 LAN, Wi-Fi addresses
This information is included in each blast report.
If the device responds in an unusual manner, then contact the Orica

Technical Service, explain the problem and report the firmware version.
Use the following keys for an easier navigation:

 [1], to the top  [3], page up
 [7], to the bottom  [9], page down

3.1.11. Assign a Name (Alias) to the Blaster

You can assign the Blaster an alias name that appears behind the
Blaster's number in the Blaster Overview.
Properties:
 An alias can have up to 5 letters.
 [MENU ► Alias]
A virtual keyboard appears on screen, and the current alias is
displayed in the top row.
 For information on how to enter a name, please refer to the section
Using the virtual Keyboard, page 47.
3.1.12. Using the virtual Keyboard

Some settings require letters or characters that are not on the Blaster’s
keyboard. Therefore, a virtual keyboard appears on screen, where the
current setting is displayed in the top row.
 When you enter a new digit, the old alias is deleted.
 When you delete the last digit, the rest of the alias remains.
Figure 29 Example: Blaster identification
Table 12 Rules for editing

[►], [◄], [▲], [▼] Select the digit that you want to enter.
[1] – [9], [0] Enter numbers directly.
[✔] Confirm the highlighted letter.
[] Delete the last digit.
[CANCEL] Quit without changing the alias.
[OK] Confirm the new name.

3 Configuring the Device
3.2. Configuring the Device

Settings are valid ONLY on the Blaster where you adjust the settings.
 Settings are NEVER transferred to other remote or sync Blasters.
3.2.1. The Setup Menu

 [MENU ► Setup]
The menu is protected by a password.
You need to enter the personal identification number (PIN).
At the time of delivery, the setup PIN is "1111".

To change the PIN, [Setup ► System ► Change Setup PIN].
Figure 30 Enter the personal identification (PIN)
 Enter the PIN (Personal Identification Number).

 Confirm the PIN with [[OK].
Figure 31 Setup menu
⇒ Functions are described in the next sections.

Configuring the Device 3
3.2.2. Setup Menu Overview

To find your way in the setup menu, the table lists all available functions.
Table 13 Setup menu
Function Description
Blaster ID [MENU ► Setup ► Blaster ► Blaster ID]
Each Blaster3000 in a blast must have a unique ID
number (1 – 7).
Blaster Mode [MENU ► Setup ► Blaster ► Blaster Mode]
Blaster's part in this blast, <Single>, <Controller>,
<Remote> Blaster, ...
Blaster name [MENU ► Alias]
Display, adapt it to light or dark [MENU ► Setup ► System ► Display]
surroundings  Brightness %
 Display color: default, black on white, white on
black
Factory settings [MENU ► Setup ► System ► Factory Setup]
Firmware upgrade [MENU ► Setup ► System ► Update Firmware]
Global detonators [MENU ► Setup ► Blaster ► Allow Global
Detonators]
LAN settings [MENU ► Setup ► Interface ► LAN]
 Blaster name, DHCP, IP Address, Subnet mask
Maximum of allowed errors [MENU ► Setup ► Blaster ► Max Errors]
When the Blaster detects more detonators with
errors, it aborts the blast.
Modem configuration [MENU ► Setup ► Interface ► Modem]
Operating language [MENU ► Setup ► System ► Language]
Setup PIN [MENU ► Setup ► System ► Setup PIN]
Termination resistor, [MENU ► Setup ► Interface ► Sync Line]
synchronized blast Activate a termination resistor when firing in sync
mode with more than 2 Blaster.
Time and Date setup [MENU ► Setup ► System ► Date / Time]
Adjust the current time and date.
Vibration monitoring [MENU ► Setup ► Blaster ► Vibration]
Wi-Fi (WLAN) settings [MENU ► Setup ► Interface ► WLAN]
 Detect WLANs, DHCP, IP Address, …
3.2.3. Factory Settings

Only authorized and trained personnel may use the “Factory Settings”,
which are described in the separate service manual.

3 Blaster Settings
3.3. Blaster Settings

Adjust the Blaster settings:
► [MENU ► Setup ► Blaster]
Figure 32 Blaster settings
3.3.1. Vibration Monitoring

To check if a <Remote> Blaster has fired, you can activate the monitoring
of the vibrations.
1. [MENU ► Setup ► Blaster ► Vibration monitoring]

2. Press [EDIT] to toggle between <On> and <Off>.
 Vibration monitoring is adjusted.
Situations when the vibration diagram is not available:

 Blast was aborted.
 Vibration monitoring is not activated.
 On a Blaster in <Single> mode.

Blaster Settings 3
3.3.2. Adjust the Blaster ID

Properties:
 Each Blaster must have a unique ID number.
 Repeaters have their own range of IDs.
1. [MENU ► Setup ► Blaster ► Blaster ID]

2. Press [EDIT].
3. Enter the new ID number in the range 1 – 7.
4. To quit and NOT change the ID, press [CANCEL].
5. To accept the value, press [OK].
 Blaster's ID number is adjusted.
If you blast multiple sites that are dependent on each other, and you
want to use the <Automatic> blasting mode, then verify:
 The Blaster that must fire first, needs a lower Blaster ID number.
 If a Blaster aborts, then you must abort dependent Blasters
manually.
3.3.3. Blaster ID of <Sync Slave> Blasters
Fast data connection:

When <Sync Slave> Blasters are connected to a <Remote> Blaster,
the ID of these <Sync Slave> Blasters should be greater than the ID of
their <Remote> Blaster.
If the Blaster IDs are chosen disadvantageous, the communication takes

longer.
Figure 33 Recommended Blaster ID settings
<Controller> ID = 1
<Remote> ID = 2
<Sync Slave> ID = 3
<Sync Slave> ID = 4
<Remote> ID = 6
<Sync Slave> ID = 7
Background:
 To start the blasting sequence, the <Controller> addresses the
Blasters in the order of their Blaster ID number.
 To address <Sync Slave> Blasters that are connected to a
<Remote> Blaster, the <Controller> must address the <Remote>
Blaster first as gateway.

3 Blaster Settings
3.3.4. Adjust the Blaster Mode

Before you start the blasting sequence, you must define which part the
Blaster has in this blast.
 [MENU ► Setup ► Blaster ► Blaster Mode]

Figure 34 Blaster mode
 Select the Blaster mode.

 Press [ENTER] to confirm the selected mode.
Table 14 Blaster modes
Blaster mode Description
Single, standalone Only 1 single Blaster is used in the blast in a standalone mode.
Only Loggers are connected via firing cable.
Controller A <Controller> controls a blast in a complex setup.
 Loggers can be connected via firing cable.
 <Remote> Blasters are connected via various methods*.
 <Sync Slave> Blasters can be connected via sync cable.
Controller (no Sync Setting accelerates the time to establish the communication
Slaves) with connected devices (Initialization), because <Sync Slaves>
are not present.
Remote A <Remote> Blaster is controlled by the <Controller>.
 <Sync Slave> Blasters are connected via sync cable.
Remote (no Sync Setting accelerates the time to establish the communication
Slaves) with connected devices (Initialization), because <Sync Slaves>
are not present.
Sync Master A <Sync Master> controls a synchronized blast.
 <Sync Slave> Blasters are connected via sync cable.
Sync Slave A <Sync Slave> is controlled by a controlling Blaster:
<Sync Master>, <Remote> Blaster, or <Controller>.
 Loggers are connected via firing cable.
 <Sync Slaves> are connected to the controlling Blaster via
sync cable.
 <Sync Slaves> and their controlling Blaster initiate their
detonators synchronously, that means, at the same time.
Repeater A repeater increases the radio distance between <Controller>
and <Remote> Blasters and bypasses obstacles when the
signal strength is not sufficient.
The Repeater is NOT connected to any Logger or Blaster.
The Repeater can only be used in surface radio
communication.
*Connection methods: Surface radio, LAN, Wi-Fi (wireless LAN), analog phone, Leaky
Feeder

Blaster Settings 3
3.3.5. Enter the Number of Allowed Errors

You can enter a maximum number of detonators that are allowed to have
an error. If there are more detonators with errors, the Blaster aborts the
blasting sequence automatically.
Risk of Misfires
You must expect misfires in the muck pile when you allow a high
number of errors when blasting.
 Use <None> or a low number of errors.
 <Unlimited> or high numbers are not recommended.
 [MENU ► Setup ► Blaster ► Max errors]

 Press [EDIT].
Figure 35 Maximum errors
The current setting is written in brackets:

Unlimited Even if all detonators have faults, the Blaster will NOT
abort.
WARNING
– Risk of misfires in the muck pile!
None If 1 detonator has a fault, the Blaster will abort.
Custom Only a certain number of errors is allowed, otherwise the
Blaster will abort. (max. 3000).

[►], [◄] Select an item.
When [Custom] is selected, you can enter a specific
number of detonators that may have an error.
[CANCEL] Quit without changing.
[OK] Confirm the new setting and quit.

3 Blaster Settings
3.3.6. Allow Globals (Unlogged Detonators)?

A "Global" is a detonator that is connected to the harness wire, but was
NOT recorded. No information about the detonator, as detonator ID and
delay time, is available.
Avoid Globals!
Because the position of the Globals is unknown, a delay time that fits to
the blast plan cannot be assigned. Therefore, Globals endanger the
success of the blast by flyrock, vibration or misfires in the muck pile.
You can decide to abort or continue the blasting sequence when Globals
(unlogged detonators) are detected on a Logger II.
Logger (I) and an eDev™II Blast Box610C cannot report Globals

to the Blaster during the blasting sequence.
 [MENU ► Setup ► Blaster ► Allow Global Detonators]

Figure 36 Settings
[EDIT] Toggles between <Yes> and <No>.

<No> Blaster aborts when Globals are found.
<Yes> WARNING
– Risk of flyrock, vibration and misfires
Blaster continues when Globals are found.
The setting in the Logger determines if Globals are fired or
not fired.
In a remote-controlled or synchronized blast, the setting of the

controlling Blaster concerning Globals is valid for all Blasters.
⇒ See also Unlogged Detonators – Risk of Misfires, page 72.

Interface Settings 3
3.4. Interface Settings

The interface settings allow to select the type of communication to other

Blasters.
► [MENU ► Setup ► Interface]
Figure 37 Interface
 The figure shows the parameters of the interface settings.
Modem settings are dependent on the installed modem type:

 Modems: Satel, RFI, serial modem, …
 Analog phone
3.4.1. Serial Modem Settings

When you use a serial connection to the modem, the parameters must be
adjusted in the modem itself.
⇒ Contact Orica Technical Service.

3 Interface Settings
3.4.2. Configure the Radio Modem

NOTICE
Value of power setting in the radio modem exceeds the allowed limit.
Damaged radio modem!
 Meet the allowed power setting.
 For example: Maximum power setting in Europe is 500 mW.
 Use only allowed frequencies.
For Satel modems, you can configure the frequency and the power.
► [MENU ► Setup ► Interface ► Modem]

Figure 38 Setup interface
<Enabled>
- <Yes>, interface is active.
- <No>, another interface is currently active.
<Frequency>, operation frequency
Two separate frequency parameters are available, if the frequencies
to receive and transmit are differently defined in the factory settings.
<TX Power>, transmission power, default value "1000 mW", values
depend on the license.
Enable the interface:

 Select <Enable> and press [EDIT].
A warning appears because another interface is still active.
 If you don’t want to enable this interface, press [CANCEL].
 To enable this interface, press [OK].
 Interface is enabled. The other interface is automatically switched off.

3.4.3. Configure the RFI Modem

Prerequisites:
 The Leaky Feeder modem is installed on the Blaster.

Figure 39 Setup LF modem
<Enabled>
<Network Address>, <0>
<Channel>,
- 2-modem configuration: <Controller> = <1>, <Remote> = <2>
- 3-modem configuration: <Controller> = <Remote> = <1>
<Transmit Power>, depends on the mine site
<RSSI Trip>, threshold to suppress bad signals (noise)
<No. of LF routers>,
- <0> in 2-modem configuration
- <1> in 3-modem configuration
Figure 40 Good and bad signals => RSSI Trip
① Good and strong signal ③ Weak signal, drowning in noise

② RSSI Trip, threshold

3.4.4. Configure the Analog Modem

Prerequisites:
 The analog interface is installed.

Figure 41 Analog settings
<Enabled>
<Ring count>, Number of rings until the modem picks up the line.
<Ring count>:
When the Blasters is connected to an analog telephone line that also
operates a normal telephone, then adjust the <Ring count> to a value
greater than 4. The Blaster will take the call at the 4th ring, and allow users
to accept the call before.
Firing Blasters in sequence:

You can prepare multiple <Remote> Blasters that use the same phone
line by setting different number of rings.
 Configure the first Blaster so that it activates after a certain number
of rings: <Ring count> = 4.
The Blaster will respond at the 4th ring, follow the Controller through
the blasting sequence and turns off.
 Configure the next Blaster so that it activates after the first Blaster.
<Ring count> = 6.
The second Blaster takes up the line because the first one is off.

3.4.5. Configure the LTE modem

Adjust the settings for the LTE modem with the data you'll receive from
your IT support.
 [MENU ► Setup ► Interface ► Modem]

Figure 42 Setup mobile phone
<Enabled>
<APN>, name of the gateway
<Access Number>, phone number
<Username>,
<Password>, password for the chosen network
<Network Type>, choose mobile network type
- <auto>:
- <2G>, <3G>, <4G>:
 Select the setting, press [EDIT].
 LTE modem is adjusted.
Enable the interface:

 Select <Enable> and press [EDIT].
A warning appears because another interface is still active.
 If you don’t want to enable this interface, press [CANCEL].
 To enable this interface, press [OK].
 Interface is enabled. The other interface is automatically switched off.
Some settings require special characters, please refer to the section


3.4.6. Configure the LAN Interface

To adjust the LAN interface, you need to enter the settings.
► [MENU ► Setup ► Interface ► LAN]
Figure 43 Setup LAN
<Enabled>
<IP Address>, internet protocol address of the Blaster
<Subnet Mask>, part of the IP address belonging to the network
<Gateway>, network address of the gateway
Edit the Subnet Mask:

The subnet mask can only have certain values.
 Select <Subnet Mask>.
 Press [EDIT].
 Use the keys [▲] or [▼] to select the correct value:
Figure 44 Subnet mask
 Press [OK] to confirm the shown value.

 Subnet mask is adjusted.

3.4.7. Configure the Wi-Fi Communication

To adjust the Wi-Fi (WLAN) interface, you need to enter the settings.
[MENU ► Setup ► Interface ► WLAN]
Figure 45 Setup Wi-FI (WLAN)
<Enabled>
<Detect WLANs>, searches for wireless networks
<SSID>, Name of the chosen network
<Password>, Password for the chosen network
<DHCP Client>
- <On>: The modem connects automatically to the chosen network
and the settings are displayed.
- <Off>: You need to enter the settings manually.
<IP Address>, Internet protocol address of the Blaster
<Subnet mask>, Part of the IP address belonging to the network
<Gateway>, network address of the gateway
Search for a wireless network:

 Select <Detect WLANs> and press [EDIT].
 Wait until the correct network is found.
The lock indicates a network that needs a password.
The bars behind the lock indicate the signal strength of the network.
[ENTER] Confirm the selected network.
[RESCAN] Repeat the search.
Some settings require special characters, please refer to the section


3.4.8. Adjust the Termination Resistor on Synchronized Blasters

When blasting in synchronized mode with more than two <Sync Slave>
Blasters, connect all Blasters in parallel via the sync terminals to the same
sync cable. There is no preferred position for the <Sync Master>.
To avoid signal reflections at cable connections, you must electrically
terminate both ends of the sync cable. Activate the termination resistor in
the first and last Blaster on the sync cable:
1. [MENU ► Setup ► Interface ► Sync Line ► Termination Resistor]
2. Choose <Off> or <On> with [EDIT].
 Termination resistor is adjusted.
⇒ For more information, see chapter How to connect synchronized

Blasters, page 113.
Figure 46 Synchronized blast - recommended setup
① - ④ Blasters connected via sync cable

Blasters at both ends of the sync cable, termination resistor ON
Blasters connected somewhere in the middle of the sync cable
The communication can be unreliable, when too much signals run over
the sync cable:
 Verify that a termination resistor is activated ONLY on two
Blasters.
 Verify that there are no open ends, which reflect the signal.

System Settings 3
3.5. System Settings

System settings include the following functions:

 Date and time
 Language of the user interface
 Color of the display
 Firmware updates on this Blaster
► [MENU ► Setup ► System]

Figure 47 Setup > System menu
3.5.1. Factory Settings

Only authorized and trained personnel may use the “Factory Settings”,
which are described in the separate service manual.

3 System Settings
3.5.2. Adjust Date and Time

You can adjust the date and time on this Blaster.
1. [MENU ► Setup ► System ► Date/Time]

2. Select the line with the date or the time.
3. Press [EDIT].
Figure 48 Date or time
The date has 3 values (year, month, day).

The time has 2 values (hour, minute).
You must edit each value separately.
The selected value is shown in brackets.

[►] , [◄] Select the value that you want to change.
[1] – [9], [0] Enter the new value.
[CANCEL] Quit without changing the value.
[OK] Confirm the new value.

System Settings 3
3.5.3. Adjust the Operating Language

You can choose the operating language or install a new language file.
► [MENU ► Setup ► System ► Language]

Figure 49 Setup language
a) Choose the Operating Language

► [MENU ► Setup ► System ► Language ► Select Language]
A list with the installed language files appears.
Figure 50 Choose operating language
English is the default language and is always present.

 To activate the selected language, press [ENTER].
 Language is chosen.

3 System Settings
b) Install, Update or Remove an Operating Language

You can install, update or remove an operating language.
Prerequisite to install or update:

 The language file is stored in the directory "\locale" of a USB device.
 USB key containing the language file is connected to the Blaster.
 [MENU ► Setup ► System ► Language ► Install Language]

Figure 51 Language installation
<Installed>, the language is installed.

<Update>, a language file is available on the USB key.
[UPDATE] The selected language can be updated.

Button appears when the language is installed and the
file is available on the USB key.
[INSTALL] The selected language can be installed.
Button appears when the language is not installed, but
a file is available on the USB key.
[UNINSTALL] The selected language can be deleted.
English is the default language and cannot be deleted.
Language files are stored in the folder "locale" and named as follows:
arbb_xx_YY.mo
xx_YY = language and country code

Example French: arbb_fr_FR.mo

System Settings 3
3.5.4. Adjust the Brightness of the Display

[MENU ► Setup ► System ► Display ► Brightness]
Figure 52 Display brightness
[►] , [◄] Select the percentage.

[CANCEL] Quit without changing the value.
[OK] Confirm the new value.
3.5.5. Choose the Color of the Display

[MENU ► Setup ► System ► Display ► Display Color]
Figure 53 Display settings
[►] , [◄] Select the Color profile:

[Colored], [Black on White], or [White on Black].
[CANCEL] Quit without changing.
[OK] Confirm the new color.

3 System Settings
3.5.6. Edit the Setup PIN

The setup PIN is a password necessary to enter the [Setup] menu.
Be sure to remember the new PIN. Otherwise, you cannot enter the
setup menu.
The default PIN is "1111".
1. [MENU ► Setup ► System ► Setup PIN]

2. Confirm the function with [ENTER].
New user PIN:
3. Enter a new PIN.

Allowed values are 0001 – 9999 (4 digits).
4. Complete the PIN with [OK].
Repeat new user PIN:
The new Setup PIN has to be confirmed.

5. Enter the new Setup PIN again.
6. Confirm with [OK].
If the two PINs differ, then the changes are discarded.
 New Setup PIN is set.

System Settings 3
3.5.7. Update the Firmware

NOTICE
An incomplete update can make the device unusable!
 ONLY update a device with fully charged batteries.
 NEVER abort the update process.
 NEVER remove the USB flash drive during updates.
Prerequisites:
 Blaster is fully charged or connected to the power supply.
 Update file is stored in the root directory of a USB storage device.
 The file is named "B3000__xx_yy_zz.mc3", where "xx_yy_zz" is the
firmware version.
1. [MENU ► Setup ► System ► Update Firmware]

2. Insert the USB storage device into the Blaster's USB port.
Display shows a list of firmware files found in the root directory of the
USB storage.
3. Choose the correct file from the list.
4. To quit, press [CLOSE].
5. To confirm the file, press [UPDATE].
Message appears that you need to confirm the update.
6. To NOT upgrade, press [CANCEL].
7. To upgrade, press [CONFIRM].
8. To start upgrading, press [OK].
Upgrade procedure starts. Messages show the progress.
9. Wait until the upgrade is finished and the Blaster shuts down.
10. Wait a few seconds and switch on the Blaster.
 Firmware is upgraded.
If an error occurs, the display shows: „Update failed! Retry“.

1. Switch the Blaster off and on again.
2. Retry to update.
3. If the update fails again, then contact the Orica Technical Service.
 Firmware is updated.
To prevent accidental updating, the buttons [CONFIRM] and [CANCEL]

change places when confirmation is necessary.
 Check which buttons allows confirming the displayed messages.

Blasting
4 Prepare for Blasting
4. Blasting
4.1. Prepare for Blasting
The diagram shows the preparation of Loggers and Blasters.
Figure 54 Blast preparation overview
Test detonators in the Loggers Preparation
No errors, no unlogged detonators

• Check Loggers IDs
• Check Loggers with a test Logger
• Charge the batteries
• Switch off Loggers
• Connect Loggers to firing cable
• Check Blaster IDs

• Charge the batteries
• Check Blaster positions
Start blasting
sequence
Evacuate the blast sites
2. Prepare Remote Blasters:

1. Prepare Sync Slaves:
• Connect Loggers
• Connect Loggers
Ready? • Connect Sync Slaves
• Press [OK] to initialize
• Press [OK] to initialize
• Sleep or stand by
• Write Remote Dongle
Evacuate the blasting areas
Controlling Blaster
(Single, Sync Master, Controller)
• Switch on, verify self-test
• Connect Loggers, Sync Slaves
Continue Step 1 of the blasting sequence

Press [OK] to INITIALIZE.
Background color:
blue: preparation yellow: user decisions white: system checks
orange: aborts light red: important decisions red: evacuate, detonate

Blasting
Safety Precautions 4
4.2. Safety Precautions

4.2.1. Preventing Misfires
WARNING
If detonators do NOT initiate, there are misfires in the muck pile, which
can detonate unexpectedly.
Death or severe injuries because of detonated misfires.
 Avoid detonators with errors.
 Avoid unrecorded detonators (Globals).
 Verify the numbers of detonators in all stages of the blasting
sequence.
Because various factors might cause misfires, it is impossible to offer

instructions to cover every situation.
The following list gives instructions to avoid the most common reasons for
misfires:
AVOID MISFIRES
An intermittent connection can result in misfires!
 NEVER use blasting equipment that has loose or missing terminals.
 ALWAYS run the wires to minimize the chances of wire damage due
to vehicles, people or landslide.
 ALWAYS verify that wires are securely connected to the output
terminals.
 ALWAYS verify that extended wires are properly joined and insulated.
 ALWAYS secure the firing cable.
Detonators that have errors can result in misfires!

If detonators have errors, then verify that they do not endanger the
success or the safety of the blast.
 ALWAYS treat unlogged detonators (Globals) as errors.
 ALWAYS treat detonators with errors as misfires!
 If there are many errors, then abort the blasting sequence.
 If you are not sure, then abort the blasting sequence.
Missing Loggers or detonators can result in misfires!

 ALWAYS verify that each Logger has a unique Logger ID on its
Blaster.
 ALWAYS verify the number of Loggers and detonators in all steps of
the blasting sequence.

Blasting
4 Safety Precautions
4.2.2. Unlogged Detonators – Risk of Misfires

WARNING
Depending on the setting in the Logger, unlogged detonators (Globals)
fire after the last detonator - or do NOT fire!
Death or severe injuries because of of flyrock, vibration, or
recovered misfires.
 ALWAYS verify that all detonators are logged in the Loggers.
 Check the setting for Globals in each Logger.
 NEVER connect detonators that should NOT fire in the blast.
If the controlling Blaster generally allows to fire with unlogged detonators

(Globals), then the setting in the Loggers concerning Globals (fire – or not
fire) is relevant.
Depending on the setting in the Logger, Globals fire – or do NOT fire!

 <Fire Globals> = <Yes>:
WARNING – RISK of flyrock and vibrations.
All unlogged detonators fire 10 ms after the last detonator.
 <Fire Globals> = <No>:
WARNING – RISK of misfires.
Unlogged detonators will NOT fire.
An eDev™II Blast Box 610C cannot detect Globals.

 The eDev™II Blast Box 610C always fires its Globals 10 ms after
the last detonator.
4.2.3. Risk of Misfire because of a low Battery

NOTICE
If the batteries of a Logger or Blaster are NOT sufficiently charged, the
Blaster will abort the blasting sequence!
 Operate the blasting equipment only with a fully charged battery.
 Use only the supplied charger.

Blasting
4.2.4. Risk of Misfires when Blasting Multiple Blast Sites

WARNING
Risk of Misfires – on dependent blast sites!
 Use the <manual> blast mode.
 Verify which Blaster has to fire first.
 NEVER use the <concurrent> blast mode.
When preparing 2 or more blast sites that are close to each other,
note the following to prevent misfires:
 If the blast sites depend on each other, check what happens if one
Blaster fails to initiate its detonators.
 Flyrock from one site can damage the wiring of the other site.
 An Electro-Magnetic Pulse (EMP) generated in the first blast can
interfere with the reception of the fire command of the second blast.
 Possible results: Blaster aborts or misfires in the muck pile.
Dependent blast Sometimes the success of a blast ② depends on the success of the blast
sites on another site ①. These blasts are dependent, because if blast ① does
not fire, the muck pile of blast ② will come to rest on top of the aborted
blast ③.
Figure 55 Example of dependent blast sites
① Blast on the lower site must initiate its detonators first

② Blast on the upper site must initiate only when blast ① has fired
③ Muck pile of blast ② on top of the aborted blast ①
NEVER use the <Concurrent> mode if the blast sites depend on each
other or are too close to each other.
Prevent misfires:
 Connect all detonator circuits to the same Blaster.
 Connect the Blasters to fire synchronously.
Synchronous Blasters abort if one Blaster has serious errors.
 Use the <manual> blasting mode.

Blasting
4.2.5. Test the Logger Connections
Tests are performed at a low, safe voltage level.
Use a spare Logger (Master Logger) at the position of the Blaster, to test
the communication to the other Loggers via firing cable.
Tasks of the tests:
 Displays the IDs of the Loggers that have responded after the query.
 Checks the firing cable for leakage and short circuit.
Figure 56 Test communication with a Master Logger
① Firing cable ④ Loggers to be tested

② Master Logger ⑤ Logger extension cable
③ Harness wire
Prepare all Loggers
+ Switch all Loggers that are to be tested into the test mode.
Functions on the Master Logger

Switch on Master Logger, to test the other Loggers.
+
Display Logger ID numbers:
 "?", intermittent connection
 Empty space, Logger ID not present or used twice
Test again
When you switch off the Master Logger, it sends a signal to the other
Loggers to switch off, too.

Blasting
4.2.6. Test Connections with Logger II
Tests are performed at a low, safe voltage level.
Use a spare Logger (Master Logger) at the position of the Blaster, to test
the communication to the other Loggers.
The Master Logger provides the following tests:
 Verifies that Logger IDs are not used twice.
 Checks the connection of the Loggers to the firing cable.
 Checks the communication on the firing cable.
 Checks the firing cable for leakage and short circuit.
 Tests the detonators.
 Searches for Globals.
Figure 57 Test the communication with a Master Logger
① Master Logger ④ Loggers to be tested

② Firing cable ⑤ Harness wire
③ Logger extension cable
System test:
 Connect the Loggers in parallel to the firing cable.
 Connect the firing cable to the output terminals of the Master
Logger.
 In the Master Logger, choose [Test ► System Test] to test all
Loggers.
 Choose [ALL DETS] to test all detonators.
 If errors occur, then solve the problems.

Blasting
4.2.7. Prepare the Loggers

We recommend to use the same Logger type and firmware on a
Blaster.
Using different Logger types or eDevTMII Blast Boxes 610C (has the
role of a Logger) on the same Blaster can lead to communication
problems and misfires!
Check the following preparations:

 Loggers on the same Blaster have a unique ID (1 – 12). 
 All detonators are connected to the harness wire. 
 All detonators are logged in the Loggers. 
 NO unlogged detonators (Globals) are present. 
 Handling of unlogged detonators is set in each Logger: 
- <FIRE Globals> = <Yes>, means fire unlogged dets
- <FIRE Globals> = <No>, means do not fire unlogged dets
 All detonators are tested successfully in the appropriate Loggers. 
 System setup is tested with a spare Master Logger. 
 All Loggers are switched off. 
 The batteries of the Loggers are fully charged. 
 Firing cable is secured and cannot contact high voltage lines. 
 All Loggers are connected to the firing cable. 
Do NOT (yet) connect the firing cable to the Blaster.

Blasting
The Blasting Sequence 4
4.3. The Blasting Sequence

4.3.1. Evacuate the Blast Site
Evacuate the charging site:
 Evacuating ensures that the wiring will not be damaged.
4.3.2. Blasting Sequence Overview

Prerequisites:
 All preparations are completed.
 Blast site is evacuated.
1. Switch on the Blaster.

2. Connect the Loggers and the <Sync Slave> Blasters to their

controlling Blasters.
3. Start the blasting sequence with [OK].
Blasting 4. Stage 1: Blaster and Logger communication (Initialization)
sequence: The controlling Blaster communicates with other Blasters (if there are
others) and with directly connected Loggers (if there are any).
- Insert the Remote Dongles when asked to do so.
- In the overview, check the number of Blasters and Loggers.
- When no errors occur, press [OK] to continue.
5. Stage 2: Programming detonators
- Insert the Master Dongle.
Blaster reads the Master Dongle and programs the detonators.
- When no errors occur or if the errors do not endanger the safety
and the success of the blast, then continue.
6. Stage 3: Ready to FIRE
- Check the ID of the Blasters that are going to fire.
- Check the numbers of Loggers and detonators.
7. When everything is correct, then confirm to fire the blast and press
both [FIRE] buttons simultaneously.
 Detonators fire according to their programmed delay time.

Blasting
4 The Blasting Sequence
4.3.3. How to connect Loggers and Blasters

WARNING
A detonator can initiate if Blaster, Logger, and detonator all have
serious defects and all devices are connected to each other!
 ALWAYS verify that unnecessary personnel has left the blast site.
 ALWAYS wait until the Blaster passes its self-test, before you
connect the Blaster to the detonator network.
Connect Loggers and Blasters:

 Switch on the Blaster and wait until it passes the self-test.
Display shows the start menu.
 Depending on the Blaster mode:
- Connect Loggers via firing cable to the black output terminals.
- Connect <Sync Slave> Blasters via sync cable to the yellow
output terminals.
Figure 59 Connect firing cable to black output terminals
Figure 60 Connect sync slaves via sync cable to yellow terminals

Sync Master Sync Slave
When the Blaster passes its self-test, then the output terminals are
powerless and short-circuited.

Blasting
4.3.4. Using Harness Wire as Firing Cable

RELIABLE CONNECTIONS
Unreliable connections lead to misfires!
 NEVER use blasting equipment that has loose or missing output
terminals.
 ALWAYS connect the wires securely to the output terminals.
 ALWAYS check that the clamps did not cut the wires.
You can use harness wire as firing cable to connect the Loggers to the
Blaster.
Pay attention when you connect harness wire to the output terminals:
 Check the electrical connection.
 WARNING – Risk of Misfire
Check that the output clamp does NOT cut the wire when
tightened.
The following figure shows two methods that are both valid, but need some
care.
Figure 61 Connect harness wire
① Wire loops around the output clamp:

- Loop the wire around the electrical part of the clamp.
- Twist the wire ending around the wire to tighten the loop.
② Wire runs through the hole of the output clamp:
- Run the wire through the hole.
Check that you do NOT CUT the wire when you tighten the clamp

Blasting
4 The Blasting Sequence
4.3.5. How to abort safely

If it is necessary to abort the blasting sequence, then pull the Master
Dongle. The Blaster sends the signal to discharge to all detonators.
TO ABORT BLASTING
 Pull the Master Dongle.
 Optional: Press the [ABORT] button.
 Wait at least 5 minutes before entering the blasting site.
1. To abort the blasting sequence, press [ABORT], or remove the

Master dongle.
Figure 62 Message after abort
[ABORT] pressed Dongle removed
2. If you accidently pressed [ABORT], you can still continue:

- To continue, press [NO].
- To abort, press [YES].
3. If you removed the dongle, you cannot continue; confirm with [OK].
The overview appears with the abort message.
Figure 63 Examples of overviews after abort
4. Depending on when you aborted, there might be details to check.

5. Press [OK] to quit.
 Blasting sequence is aborted.

Blasting
4.3.6. Risk of Electrostatic Discharge

WARNING
Electrostatic discharge and connection to high voltage lines!
Death or severe injuries by electrocution
 NO heart pacemaker wearers are allowed near the blast.
Electromagnetic interference can disrupt a cardiac rhythm device.
 NEVER position firing cables or harness wires near overhead high
voltage lines.
 ALWAYS secure the firing cable.
 ALWAYS follow local regulations.
 NEVER touch the connections of the firing cable during firing.
4.3.7. Begin the Blasting Sequence
When all preparations are completed, and the blasting area is

evacuated, then the shotfirer may start the blasting sequence.
Depending on the mode of the Blasters, continue in the following chapters:
Single:
⇒ Blasting with a Single Blaster, page 82.
Synchronized:
⇒ Blasting with synchronized Blasters, page 111.
Remote-controlled:
⇒ Blasting with Remote-Controlled Blasters, page 154.

Blasting
4 Blasting with a Single Blaster
4.4. Blasting with a Single Blaster

WARNING
Missing Loggers or detonators can result in misfires!
 ALWAYS verify that each Logger has a unique Logger ID on its
Blaster.
 ALWAYS verify the number of Loggers and detonators in all steps
of the blasting sequence.
4.4.1. Setup with a Single Blaster

Prerequisites:
 Blaster is configured as <Single Blaster>.
A single Blaster initiates the detonators that are connected to its
black output terminals.
[MENU ► Setup ► Blaster] <Blaster Mode> = <Single>
 Blast setup is prepared as shown in the figure below, but the firing
cable is not yet connected.
 Blaster is positioned in a safe location.
 Blasting area is evacuated.
 NO dongle is inserted into the Blaster's dongle port.
① Single Blaster in a place of safety ② Hazard area during the blast

during the blast
③ Firing cable connected after the Blaster passes
its self-test.

Blasting
Blasting with a Single Blaster 4
4.4.2. Evacuate the Blasting Area

DANGER
People in the blasting area!
 ALWAYS check that all people left the blasting area.
 Follow the site evacuation procedure.

Figure 65 Blasting sequence
Evacuate blasting area
• Switch on Blaster
• Connect Loggers via firing cable
Stage 1
Press [OK] to initialize Initialize
Establish communication
Blaster overview: no
User abort
Number Loggers + dets correct?
yes
Stage 2
no Programming dets
Insert Master dongle
yes
yes no
Confirm
Errors? User abort
errors?
no yes
yes
Stage 3
no FIRE
User abort Press [FIRE]
yes
no System check: yes Detonation

System abort Harness check
OK?
Reports
Background color:

Blasting
4.4.4. Stage 1: Start the Blasting Sequence
NO dongle is inserted into the Blaster's dongle port.

 Insert the dongle only when asked to do so.
 It takes up to 1 second for the Blaster to recognize the dongle.
Prerequisites:
 Switch on the Blaster or return to the start menu.
 Depending on the Blaster's mode, follow the instructions on the
screen.
1. Connect the firing cable from the Loggers to the Blaster.

2. To start the blasting sequence, press [OK].
The Blaster provides the communication voltage to the output
terminals and polls connected Loggers.
Communication runs at a low and safe voltage level.
If Loggers have errors, the Blaster aborts the blasting sequence

and shows an error message.
See section Errors and Warnings, page 186.
The «Blaster overview» lists all detected Blasters, their number of

Loggers and logged detonators.
In single Blaster mode, only a single Blaster appears in the list.

Blasting
Figure 67 Blaster overview
List of Blasters, Loggers and detonators:

– <B01> – <B07> ID of Blasters
– <Logger>, number of Loggers
– <Detonators>, number of logged detonators
[ABORT] If anything is wrong, then abort the blasting sequence.

[DETAIL] Check details (Loggers, detonators) of the selected
Blaster.
[OK] Continue only when all numbers are correct!
The button appears when there are no errors.
Verify the numbers:

1. Check the numbers of Blasters, Loggers and detonators.
WARNING – Risk of Misfires

Wrong numbers of Loggers or detonators lead to misfires!
 No error message appears for Loggers that are NOT in the list.
 Detonators of missing Loggers will NOT fire.
2. Press [DETAIL] and check the details of the selected Blaster.

See chapter Blaster Details, page 91.
3. If a number is wrong, then press [ABORT].
4. When all numbers are correct, then confirm with [OK].
 The numbers of Blasters, Loggers and detonators are correct.
Stage 1 is completed. Blaster is ready to program the detonators.

⇒ Continue in stage 2.

Blasting
4.4.5. Stage 2: Programming Detonators

Insert the Master Dongle
When the Blaster is ready to program the detonators, the message to
insert the Master Dongle appears.
Figure 68 Insert Master Dongle
Insert the red Master Dongle and to

start PROGRAMMING, press [OK]
1. Insert the Master Dongle.

When the Master Dongle is valid, the button [OK] appears.
2. If the dongle is not recognized, then pull it and insert it again.
3. To start programming the detonators, press [OK].
The Blaster charges, programs and calibrates the detonators.
Figure 69 Programming detonators
(100) number of detonators
<Status> shows the progress for each Blaster.

<Time to complete>, remaining time for programming
The programming time for 3000 detonators is approximately
2 minutes with a robust communication. (Not yet verified).
If the Blaster detects detonator errors, it tries to reprogram the detonators.
⇒ If the reprogramming is not successful, then an error appears, see
section Blaster Overview after Programming in Stage 2, page 94.
If the Blaster detects Globals, detonators that are not logged, it displays
an error or a warning, see chapter Globals Detected, page 95.

Blasting
4.4.6. Overview – Check the Numbers

When everything is correct or all errors are confirmed, the [OK] button
appears in the overview.
Figure 70 All errors are confirmed

– <Detonators>, number of detected detonators
– <Errors> x(y), x = number of errors, y = unconfirmed errors

Blaster.
Check the Numbers

When all detonator errors are confirmed, (0) zero between the brackets,
then the button [OK] appears.
 Check the numbers of Blasters, Loggers and detonators.

 When the numbers are wrong, then abort and search for the
missing components.
 When the numbers are correct, continue with [OK].
 Stage 2 is completed.
Detonators are now armed and ready to fire!

Blasting
4.4.7. Stage 3: Initiate the Blast

TO ABORT BLASTING
Prerequisites:
 No errors have occurred during the programming sequence.
 Or, the confirmed errors do not endanger the safety or success of the
blast.
The firing window timer is counting down.

If you do NOT give the FIRE command before the timer expires, the
Blaster aborts the blast.
Figure 71 Ready to fire
<Firing Window>, firing window timer (minutes: seconds)

– Green bar indicates the progress.
– Orange bar: 5 minutes are left
– Red bar: 1 minute is left
Yellow marked Blasters are going to fire
Blaster status:
 <Ready to Fire> – no detonator errors
 <Ready to Fire with Errors> – there are detonator errors
[FIRE] buttons flash accompanied by beeps. The beep switches off after
30 seconds and restarts for the last minute of the countdown.
 To check Loggers and detonators, select a Blaster and press
[OVERVIEW]. Continue in chapter Blaster Overview after
Programming in Stage 2, page 94.
 When everything is correct, then continue on the next page.

Blasting
4.4.8. Give the FIRE Command

When everything is correct or all errors are confirmed, then the Blaster is
ready to fire.
Figure 72 «FIRE» menu
1. Verify that the blasting area is evacuated.

2. Check the yellow marked Blasters that are going to fire.
3. To check Loggers and detonators, press [OVERVIEW].
If you fire with detonators that have errors or Globals,

expect misfires in the muck pile.
4. If you need to abort, then pull the Master Dongle.
The following step triggers the blast:

5. To fire the detonators, press both [FIRE] buttons at the same time.
The Blaster verifies that the first and the last detonator on each
harness circuit are still responding.
If an error occurs, the Blaster aborts the blast, see section Abort
after the FIRE Command, page 101.
 When no error occurs, the Blaster sends the fire command, and the
detonators initiate according to their delay time.
BANG
⇒ Continue in chapter Procedure after the Blast, page 102.

Blaster Overview, Details and Errors
5 Blaster Overview in Stage 1
5. Blaster Overview, Details and Errors

5.1. Blaster Overview in Stage 1
In stage 1, the «Blaster Overview» shows all Blasters and Loggers that
have responded to the controlling Blaster.
Figure 73 Example Blaster overview with 2 Blasters
All Loggers 1 Logger deactivated

– <Logger>, number of active Loggers
(2) total number of Loggers including deactivated Loggers

Blaster.

Blaster Overview in Stage 1 5
5.1.1. Blaster Details

In the Blaster overview, you can select a Blaster, and check its Loggers
and their status.
1. Select a Blaster number, and press [DETAIL].

The «Blaster Details» shows all Loggers that are identified by the
selected Blaster, and their numbers of detonators.
If an error occurs, a message appears behind the Logger ID.
Figure 74 Blaster details
<L01> – <L12>, ID of the Loggers

<--->, Logger not connected
2. If you need to exclude a Logger from the Blaster, continue in chapter
Deselect a Logger, page 92.
3. To return to the Blaster overview, press [BACK].
 Blaster details are checked.
In stage 1, the detonator status and leakage current are not available,
because there has not been a communication with the detonators.

5 Blaster Overview in Stage 1
5.1.2. Deselect a Logger

WARNING
Detonators of excluded Loggers will NOT fire.
Risk of Misfire
 Check if the blast design allows to exclude a Logger.
 Check the selected and deselected Logger IDs.
The shotfirer-in-charge can decide to exclude a Logger from the blast.

 For example, you can exclude a Logger with high leakage current
that had made the first attempt to fire unsuccessful.
 Detonators in a Logger that are installed in an independent blast site
(other stope) can be fired later in a different blast.
1. In the Blaster overview, choose [DETAIL].

The list shows the Loggers that are connected to the Blaster:
2. To exclude a Logger from the blast, select the Logger and press
[DEACTIVATE].
3. If the wrong Logger is deactivated, press [REACTIVATE].
4. When the list is correct, press [BACK].
A warning appears that you deactivated a Logger.
Figure 76 Warning
You are going to fire with 1

deactivated Logger.
[NO] Cancels the deactivation.

[YES] Confirms the deactivation.
Selected Loggers are deactivated.
 Display shows the Blaster overview again.
⇒ Please continue in the chapter Blaster Overview in Stage 1, page

90.

If an Error occurs 5
5.2. If an Error occurs

If an error occurs, the Blaster displays a warning or an error message.
5.2.1. Warnings
A WARNING has an orange border. A warning can point to a condition
that causes misfires!
Figure 77 Example for a warning
 Press [ABORT] and fix the problem before you continue.

 If you want to continue without solving the problem, and you are sure
to understand the consequences, you can continue with [OK].
5.2.2. Error – Abort

An ERROR has a red border; you cannot continue.
 Confirm the error with [OK].
Figure 78 Example for an error
Sometimes more information is available.

 Press [BACK] to return to the main menu.
 Fix the problem before you start the blasting sequence again.
 The Blaster aborts.
If the Blaster detects errors on Loggers or participating Blasters, it

aborts the blasting sequence and shows an error message.
Please refer to the chapter Errors and Warnings, page 186.

5 Blaster Overview after Programming in Stage 2
5.3. Blaster Overview after Programming in Stage 2

After programming the detonators in stage 2, the overview lists all
Blasters, their Loggers and detonators.
Figure 79 Blaster overview, example without errors
Logger “1(2)”: 1 Logger is currently active

– (2) total number of Loggers, including deactivated Loggers

Blaster.
 Press [DETAIL] to see more information.

Each Logger is listed with detonators, errors and leakage current.
There are no details available on Loggers without errors.
Figure 80 Details
 To return to the overview, press [BACK].
⇒ If Globals or errors are detected, then see the next sections.

Globals Detected 5
5.4. Globals Detected

In a remote-controlled or synchronized blast, the setting of the
controlling Blaster concerning Globals is valid for all Blasters.
After programming the detonators, the Blaster searches for Globals

(unlogged detonators). When Globals are found, a warning or an error
appears, depending on the setting in the controlling Blaster.
Error/Abort Globals are NOT allowed:

When Globals are not allowed in the controlling Blaster, different errors
are displayed depending on the Blaster mode.
Figure 81 Example of an error
Faulty Blaster present Error
 Confirm the errors.

 Press [DETAIL] to see information about the Loggers belonging to the
chosen Blaster.
Figure 82 Overview
The overview shows the error on the Blaster that found the Globals.
“(+2)”, the estimated number of Globals is shown in brackets.
“N/A”, no data on Globals if the firmware of the Logger does not
support the detection of Globals.
 Press [OK] to confirm the error and exit.
 The Blaster that has the Globals aborts. Blasters connected via sync
cable abort together.
In a remote-controlled Blast, you can continue in the blasting sequence

using the other Blasters.
 Continue only if the sites of remaining blasts are independent of
aborted blasts.

5 Globals Detected
Warning Globals are allowed:

When Globals are allowed on the controlling Blaster, a warning appears.
Figure 83 Warning
Globals found

 If you fire with Globals, you endanger the success of the blast
by flyrock, vibrations, or misfires in the muck pile.
 When you continue, the setting in the Loggers is executed:
- <Fire Globals>=<No>: Risk of misfires
- <Fire Globals>=<Yes>: Risk of vibrations
 Confirm the warning with [OK].
In the overview, Globals are shown in brackets behind the detonator
numbers.
Figure 84 Overview with Globals
Overview Blaster details
“(+2)”, two Globals detected

“N/A”, no data on Globals if the firmware of the Logger does not
support the detection of Globals.
[DETAIL], shows the information about Loggers belonging to the
chosen Blaster.
 If the number of Globals is high, then abort the blasting sequence.
Abort  To abort, press [ABORT]

 Blasting sequence is aborted. Search for the Globals and restart the
blasting sequence.
Continue  To continue, press [OK].

 You can continue in the blasting sequence.

Overview with Detonator Errors 5
5.5. Overview with Detonator Errors

WARNING
Detonators that have errors might not initiate.
 ALWAYS verify that detonators with errors do not endanger the
success or the safety of the blast.
 If there are many errors, then abort the blasting sequence.
 If you are not sure, then abort the blasting sequence.
 ALWAYS treat all detonators with errors as misfires!
If detonator errors occur during programming, the Blaster automatically

tries to re-program the faulty or not responding detonators.
 The Blaster tries two times to reprogram the detonators.
 Reprogramming increases the total programming time.
The following example shows an overview with detonator errors.
Figure 85 Errors on Blaster B02
Errors
[OK] not available
<Logger 1(2)>, one Logger is active, (2) total number of Loggers.

<Errors> 20(20), the Blaster announces 20 errors. The number in
brackets is the number of unconfirmed errors.
The button [OK] is not visible and you cannot continue because there
are unconfirmed errors.
 Press [DETAIL], check and confirm each detonator error.

5 Overview with Detonator Errors
5.5.1. Check and Confirm the Errors

Repeat the following procedure for all Blasters with errors:
1. Select the Blaster that has errors.
2. Press [DETAIL] to see information on Loggers.
The list includes the Loggers, their detonators, errors and leakage
current.
The number in brackets shows the unconfirmed errors.

3. Select a Logger that has errors.
4. Press [DETAIL] to see the detonator error list.
The list shows only the detonators with an error.
Figure 87 Logger details
<Position>, logging position of the detonator

<Detonator ID>, detonator ID
<Error>, error code
<Status>, status of the error <Unconfirmed>, <Confirmed>
5. Check all errors.
 Errors are checked.
If something is wrong or if it is NOT safe to continue, then abort:

 Press [BACK] and then press [ABORT].
 Blasting sequence is aborted.

Overview with Detonator Errors 5
Continue If the detonators that have errors do not endanger the success of the blast,
then you can continue:
WARNING – Risk of misfires

 Detonators with errors might not initiate.
1. Confirm each error with [CONFIRM].

Figure 88 Confirmed errors
The button [CONFIRM] is only visible on errors that are not yet
confirmed.
2. Press [BACK] to return to the previous overview.
Figure 89 Blaster details, errors are confirmed
<20(0)> All errors are confirmed, when the number in brackets is

zero.
3. Repeat the procedure for all Loggers with errors.
4. When all errors are confirmed, press [BACK] to return to the
overview.
 Detonator errors are confirmed.
⇒ For information on error messages, please refer to the chapter

Detonator Errors, page 197.

5 Overview with Detonator Errors
5.5.2. Blaster Overview with confirmed Errors

When the detonator errors are confirmed, press [BACK] to return to the
«Blaster Overview».
Figure 90 Blaster details, all errors confirmed


Blaster.
Check the Numbers


missing components.
Depending on the mode of the Blasters, continue in the following chapters:
Single:
⇒ Stage 3: Initiate the Blast, page 88.
Synchronized:
Remote-controlled:

Abort after the FIRE Command 5
5.6. Abort after the FIRE Command

After you press the FIRE command buttons, the Blasters perform various
tests.
If a critical error occurs, the controlling Blaster aborts the blasting
sequence, and shows a general error:
Figure 91 Error
Error
1. Confirm with [OK].

The overview appears with information on the error.
Figure 92 Example of an abort
<Det check failed>, in this example, the check has failed, where the
first and the last detonator are tested.
2. Press [DETAIL] to check the reason of the abort.
Figure 93 Example: No harness
⇒ For information on the various errors, see section Errors and

Warnings, page 186.

Procedure after the Blast
6 Uploading the Reports
6. Procedure after the Blast

6.1. Uploading the Reports
After the blast, the output voltage of the Blaster drops to the
communication voltage, and the Loggers remain switched on.
 Each Blaster uploads its general blast report from the Loggers
automatically. This report contains data on detonator errors.
 Each Blaster automatically uploads the data of good detonators.
If you don't need this data, you can stop the upload.
 If a controlling Blaster participates, it merges all reports of all Blasters
into a combined blast report.
If you don't need this data, you can stop the upload.
6.1.1. General Blast Report

Each Blaster automatically generates its own blast report.
Figure 94 Example of a blast report
Blaster ID Blaster Mode
B02 Single
Blaster ID: 2
...
Loggers: 12
Detonators: 2400
Detonator Errors: 2
...
Logger ID: 1
...
Detonators: 200 Errors: 2
DET DET-ID DELAY ERROR
1 EA5783E8 0 Faulty det
10 EA5783EA 15 No reply
Logger ID: 2
...
The blast report contains information on Loggers, errors on Loggers and

detonators with errors.
In a blast with more Blasters, the controlling Blaster (Controller, Sync
Master) stores additionally the information on participating Blasters and
errors on Blasters.
Figure 95 Example of a blast report in a controlling Blaster
Blasters: 5
Detonators: 3544
Detonator Errors: 7
Blast Setup
B01 Controller B02 Sync Slave
B01 Remote B02 Remote
B01 Remote
⇒ For a detailed description on blast reports, see chapter Contents of

a Report, page 110.
At this stage, the report does not contain data of good detonators.

Uploading the Reports 6
6.1.2. Uploading the Logger Report

After the general blast report is stored, each Blaster automatically loads
the reports of its Loggers. These Logger reports include data on each
detonator as position, detonator ID, delay time and status or error.
Figure 96 Uploading Logger reports (Example Sync Master)
Percentage on the right side shows the progress of uploading.

 Logger reports are stored in the corresponding Blasters.
All Blasters upload the Logger report in parallel. A Blaster needs about
1 minute to upload data of 200 detonators.
Figure 97 Example of a blast report that includes the Logger report

Blasters: 1
Detonators: 2400
Detonator Errors: 2
Blast Setup
...
Logger ID: 1
Serial No.: 1016
...
No. Detonator ID Delay Status No. Detonator ID Delay Status
1 EA5784C8 0 Faulty det 2 EA5784C7 150 Programmed
3 EA5784C6 300 Programmed 4 EA5784C5 450 Programmed
5 EA5784C0 1200 Programmed 6 EA5784BF 1350 No reply
Stop Uploading Logger Reports

If you don't need the Logger report in the controlling Blaster, you can stop
the process.
 To stop uploading Logger Reports, press [CANCEL] or switch off the
Blaster.
The controlling Blaster stops uploading reports.
All other Blasters continue uploading the Logger report.
 Blast report on the controlling Blaster does not include Logger
reports.
⇒ For information on how to transfer the Logger report from a Logger to

the PC, refer to the Logger's user manual.

6 Uploading the Reports
6.1.3. Combine the Reports of all Blasters

A controlling Blaster (Master Blaster, Controller) can collect the reports of
the other Blasters.
Prerequisites:
 Logger reports are uploaded to each Blaster.
Overall report Figure 98 Upload individual Blaster reports
Do you want to upload the individual

Blaster Reports to this Blaster?
[NO] An overall report will NOT be generated.

[YES] The overall report will be generated in the controlling Blaster.
Uploading the blast reports takes about 4 minutes for 2400 detonators
on one Blaster.
Vibration If the vibration monitoring is activated in the Blasters, the following

message appears.
Figure 99 Message for vibration reports
Do you want to upload vibration data

to this Blaster?
[NO] Vibration data of other Blasters will NOT be stored on the

[YES] Vibration data of other Blasters will be stored on the
Result The display lists all Blasters, their status, date and time.
Figure 100 Firing results
[VIBRATION] Display the vibration diagrams.

[OK] Continue, reports are generated.
⇒ For information on the reports and the vibration diagram, see chapter
Check the Blast Report, page 108.

Shut down <Remote> Blasters 6
6.2. Shut down <Remote> Blasters

You have the possibility to shut down <Remote> Blasters.
The display shows the «Firing Results».

 Confirm with [OK].
The shutdown procedure appears.
Figure 101 Shut down
[EXIT] Quit the procedure.

[SHUTDOWN] Switch off the selected Blaster.
[SHUTDOWN ALL] Switch off all Blasters.

6 Re-Entering the Blasting Area
6.3. Re-Entering the Blasting Area

DANGER
People enter the blasting area too soon!
 Wait at least 5 minutes.
 Follow local regulations for re-entering the blasting area.
Before entering the blasting area:

 Remove the Master Dongle and keep it safe.
 Keep Remote Dongles safe.
 Disconnect the firing cable from the Blaster.
 Wait at least 5 minutes for detonators to discharge safely.
When you pull the Master Dongle on the controlling Blaster <Controller>,
then all <Sync Slave> Blasters and <Remote> Blasters receive a signal to
abort. The output terminals on each Blaster connect and no voltage is
provided to the firing cable. Therefore, it is not necessary to disconnect
the firing cable.
Establish a best practice and work always in the same way:

 ALWAYS disconnect the firing cable before entering the blasting
area.
6.4. Misfires in the Muck Pile

WARNING
When recovering misfired or damaged detonators, they might initiate
instantly!
 Treat all misfires as damaged.
 Follow local regulations.
⇒ For information on misfires, see chapter Guidelines on Handling

Misfires, page 198.

Inspection and Cleaning 6
6.5. Inspection and Cleaning
Remove the dongles and keep them in a safe place.
Clean and check all devices for the next blast.

1. Follow local regulations for re-entry of the blasting area for after blast
inspections.
DANGER
 Wait at least 5 minutes before re-entering blasting area.
2. Switch off and disconnect all devices.

<Controller> and <Repeater> are always switched on - you have to
switch them off manually.
3. When blasting wireless:

- Dismount antenna.
- Store antenna below the top cover of the Blaster.
- Close the top cover.
4. Move the devices to a dry location.
5. Inspect the equipment for damage.
6. Clean the devices if necessary.
7. Print or export required reports.
8. Charge the devices for the next use.
9. Store the devices in a safe and dry location.
 Procedure after the blast is completed.
⇒ For information on cleaning, see chapter Maintenance, page 199.
 Check the date on the inspection tag.

 Send devices to Orica before the next service is due.
 Send defect devices immediately to Orica for servicing.

6 Blast Report
6.6. Blast Report

Blast reports include all information on participating Blasters, Loggers and
detonators.
6.6.1. Check the Blast Report

 [MENU ► Reports]
The list shows the reports with the date and time of the blast.
Figure 102 Reports
[SAVE] Saves the selected report on the USB device.

[VIEW] Opens the report.
The report is designed for print out and does not fit on the
screen.
 Use the navigation keys to move the viewable
section.
[VIBRATION] Shows the vibration diagram.
Up to 30 reports can be stored on the Blaster. When the next blast is

fired, the oldest report is overwritten with the new blast report.
Use the following keys for an easier navigation:

 [1], to the top  [3], page up
 [7], to the bottom  [9], page down


Blast Report 6
6.6.2. View the Vibration Report

You can view the vibration reports that the Blasters monitored during 30
seconds. Because the detection of vibrations in the Blaster is limited, the
vibration report can only serve as a verification of a successful firing and
the duration of the blast.
Prerequisites:
 Vibration monitoring must be activated in the Blaster settings.
1. [MENU ► Reports]
2. Select the report and press [VIBRATION].
Figure 103 Vibration overview
3. If the report includes results from other Blasters, you can use
[PREVIOUS] and [NEXT] to see all reports.
 Blast is verified.

6.6.3. Save a Report via USB

You can copy a report to a USB storage device.
1. [MENU ► Reports]
2. Insert the USB storage device.
When the USB device is detected, the [SAVE] button appears.
3. Select a report.
4. Press [SAVE].
 Report is copied to USB.
Reports are stored in the root directory of the USB storage as a text file
and in an xml-folder. When vibration monitoring is activated, an
additional graphic is added.

6 Blast Report
6.6.4. Contents of a Report

Figure 104 Blast report (example is shortened)
Blaster3000 Blast Report
① Blast Summary
Blasters: 4
Detonators: 2400
Detonator Errors: 2
② Blast Setup
Blaster ID Blaster Mode
③ B02 (ALIAS) Controller
B03 (ALIAS) Remote
B04 (ALIAS) Slave to B02
…
④ Blast Details
Blaster ID: 1
Serial No.:
...
Fire command sent at yymmdd 11:10:06
Status: OK
Loggers: 2
Detonators: 2400
Detonator Errors: 2
…
Logger ID: 1
Serial No.: 1016
Detonators: 200
Detonator Errors: 2
Globals: 3
...
⑤ No. Det-ID Delay Status No. Det-ID Delay Status
1 EA5783E8 0 Faulty det 2 EA5783E9 5 OK
3 EA5783EA 15 No reply 4 EA5783EB 25 OK
...
⑥ About Blaster 3000

Hardware Version: xx
Firmware Version: xx
Compile Date: date
...
Contents:
 ① Blast Summary: Total number of Blasters, detonators and
detonator errors
 ② Blast Setup: Blaster ID and Blaster mode
 ③ A controlling Blaster also lists lower-ranking Blasters
 ④ Blast Details: Blaster ID, serial number, firmware version
- <Fired at>, date and time when the FIRE command was issued
- <Aborted at>, if a blast was aborted
- Blaster status, number of Loggers and detonators, number of
detonator errors, battery level, current
- Logger IDs, number of detonators, number of errors on each
Logger
- Estimated number of Globals
 ⑤ List of all detonators with ID, delay time and status is only
included when the Logger report is uploaded from the Loggers.
 ⑥ <About Blaster 3000>: software and hardware identification
Unlogged detonators (Globals) can be detected with Logger II that has

a firmware 1.5.81 or later.

Blasting with synchronized Blasters
Prepare for a synchronized Blast 7
7. Blasting with synchronized Blasters

In a synchronized blast, the Blasters are connected to the same sync
cable. Connected Blasters fire at the same time.
 If one Blaster has a serious error, all Blasters abort the blasting
sequence.
 The controlling Blaster is called <Sync Master>.

- Loggers can be connected to the black output terminals.
 Dependent Blasters are called <Sync Slaves>.
- Loggers must be connected to the black output terminals.
 The <Sync Master> controls up to 6 <Sync Slave> Blasters that are
connected to the same sync cable via the yellow sync terminals.
7.1. Prepare for a synchronized Blast

 All Blasters have a unique ID number. 
 Blasters and Loggers are fully charged. 
 Blaster mode is adjusted: [Setup ► Blaster ► Blaster Mode]: 
- <Sync Master> for the controlling Blaster
- <Sync Slave> for Slave Blasters
 <Sync Slave> Blasters and the <Sync Master> are connected via 
the sync cable to the yellow sync terminals.
 When there is more than one slave Blaster, the termination resistor 
is switched on in the first and last Blaster on the sync cable.
- Function: [MENU ► Setup ► Interface ► Sync Line]
- <Termination resistor> = <on>
 All Blasters are positioned at a safe place. 
 The blast site is evacuated. 
 NO dongle is inserted in a Blasters' dongle port. 
You do NOT need a dongle to prepare a <Sync Slave> Blaster.
 All Loggers are connected to the firing cable. 
 The firing cable is NOT connected to a Blaster. 

7 Prepare for a synchronized Blast
7.1.1. Test the Sync Cable

A bad connection or bad cable can influence the reliability of the sync
cable.
If you are concerned, perform a resistance test:

1. Connect both wires of the sync cable on one end.
2. Measure the leakage current using a Logger on the other end.
3. When the Logger announces a short circuit the cable is usable.
The leakage current is greater than 15 mA.
The cable resistance is below 320 Ω.
4. Else check and repair the cable.
 Resistance is verified.
7.1.2. Check the Termination Resistor

WARNING
A Blaster might not fire if the termination resistor is switched on and the
Blaster is not at the end of the sync cable!
Risk of misfires
 Verify that the termination resistor is only switched on in the first and
the last Blaster on the sync cable.
If you connect more than 2 Blaster 3000 units via sync cable, then check
the setting of the termination resistor.
⇒ Continue in the next section.

7.1.3. How to connect synchronized Blasters

Recommended setup:
 The Blasters are connected via one sync cable.
 The sync cable has only two ends.
 Do not switch the polarity of the sync cable.
 Termination resistors are activated in both Blasters at the ends of
the sync cable.
 The <Sync Master> can be any of the Blasters.
Figure 105 Synchronized blast - recommended setup

Blasters at both ends of the sync cable, termination resistor is ON
Blasters connected in the middle of the sync cable, termination resistor OFF

In the following examples, the Blasters are connected by more than one
sync cable. Signals are reflected at open ends and at each connection of
the sync cable, causing interference.
Figure 106 NOT recommended setup

Blasters at 2 ends of the sync cable, termination resistor ON
Reflections: Bouncing signals on open ends and on connections
The communication can be unreliable, when too much signals run over
the sync cable:
 Verify that a termination resistor is activated ONLY on two
Blasters.
 Verify that there are no open ends, which reflect the signal.


The following diagram shows the preparation and blasting sequence in a
synchronized blast.
Figure 107 Blasting sequence
Clear blast sites All <Sync Slaves>:

• Switch on
• Check termination resistor
• Connect Loggers
• Press [OK] - Sleep or standby
Evacuate blasting area
<Sync Master>:
• Switch on
• Connect Loggers
• Connect <Sync Slaves>
Stage 1
• Press [OK] to initialize Initialize
• Enter number<Sync Slaves> Establish communication
• Wake up <Sync Slaves>
User abort
yes
Stage 2
Programming dets
no
Insert Master dongle
yes
yes
Programming errors? Confirm Errors? User abort
no
no yes
yes
Stage 3
no FIRE
User abort Press [FIRE]?
yes
no System check: yes Detonation

System abort • Sync Slaves OK?
• First + last det OK?
Reports
Background color:


7.1.6. Prepare <Sync Slave> Blasters

Prerequisites:
 Blaster mode is adjusted: 
- [MENU ► Setup ► Blaster ] <Blaster Mode> = <Sync Slave>
 No dongle is in the <Sync Slave> Blaster's dongle port. 
 Firing cable is NOT connected to the <Sync Slave> Blaster. 
 Termination resistor is adjusted: 
[MENU ► Setup ► Interface ► Sync Line ] <Termination resistor> =
- <ON>, on the first and last Blaster on the sync cable.
- <OFF>, on other Blasters on the sync cable.
The preparation occurs at a safe voltage level.
Prepare each <Sync Slave> Blaster:

1. Switch on the <Sync Slave> Blaster.
Blaster performs the self-test.
2. Check that <Sync Slave> is written in the first line (Blaster Mode).
Figure 108 Prepare for blasting
3. Connect the Loggers to this Blaster via firing cable.

4. Continue with [OK].
The Blaster communicates with its Loggers and shows the «Blaster
Overview».



Blaster.
Verify the numbers:




Set <Sync Slaves> to sleep or standby Mode

To save battery power, you can set <Sync Slave> Blasters into sleep
mode.
Figure 110 Choose the mode: sleep – stand by
Set this Sync Slave to sleep?
 Choose:
[NO] You fire the blast within the next 12 hours.
Blaster goes into standby mode.
[YES] You fire the blast later than 12 hours.
Blaster goes into sleep mode, and switches off to save
battery power.
This mode requires a special wakeup call by the controlling
Blaster and the <Sync Slave> needs some time to start.
 Close the lid of the Blaster’s case.

 <Sync Slave> Blaster is prepared for blasting.

Stage 1: Start the Blasting Sequence 7
7.2. Stage 1: Start the Blasting Sequence

DANGER
7.2.2. Activate the <Sync Master>

 Switch on the <Sync Master> Blaster.
Figure 111 Start initializing – Establish the communication
 Depending on the setup, connect Loggers and Blasters:

Loggers If there are Loggers to connect directly, then connect
the Loggers via the black output terminals.
Synchronized Connect all synchronized Blasters via the sync cable
Blasters to the yellow sync terminals.
If you connect the synchronized Blasters later, the
controlling Blaster will not recognize them!
 With [OK] you start the blasting sequence.

7 Stage 1: Start the Blasting Sequence
7.2.3. Activate <Sync Slave> Blasters

WARNING
You must wake up <Sync Slave> Blasters that are in sleep mode, or
they are not included in the blast!
 Wake up <Sync Slave> Blasters that are in sleep mode.
 If you are unsure in which mode the <Sync Slave> Blasters are,
choose [YES] for wake up.
The following number of <Sync Slave> Blasters and the wake-up

procedure concerns only those <Sync Slave> Blasters that are
connected to the <Sync Master>.
Enter the Number of Sync Slave Blasters

A message appears to enter the number of <Sync Slave> Blasters that
are connected to this Blaster.
Figure 112 Enter number of <Sync Slave> Blasters
Expected Sync Slaves:
1. Enter the number of <Sync Slave> Blasters.

Allowed range: 0 - 6
2. Optional, you can increase or decrease the number with [▲] or [▼].
3. Confirm the number of <Sync Slave> Blasters with [OK].
 Number of <Sync Slave> Blasters is entered.
Wake Up Synchronized Blasters?

If <Sync Slaves> are connected, choose the wake-up mode.
Figure 113 Wake up slaves?
Wake up Sync Slaves?
WARNING – Risk of misfire

If you do not wake up <Sync Slave> Blasters that are in sleep
mode, they are NOT included in the blast.
 Choose [YES], to wake up slave Blasters that are in <SLEEP> mode,

or if you don’t know in which mode the Blasters are.
Blasters in sleep mode need 60 seconds extra time to start up.
 Choose [NO] ONLY to activate slave Blasters that are in <STANDBY>
mode.
 If unsure, press [YES].
 Sync Slave Blasters are activated.

7.2.4. Initialization – Establish the Communication

 Press [OK] to continue.
[CONTINUE] activates when all Blasters are online.

 <Sync Master> has established the communication.
⇒ Continue in the next chapter.
During the initialization, the controlling Blaster communicates with the

slave Blasters and aligns the polarity.
 Do NOT remove the sync cable.
 Do NOT change the polarity of the sync cable.
7.2.5. Wrong Number of Synchronized Blasters

If the controlling Blaster detects more or less Sync Slave Blasters than
were expected, then a warning appears:
Figure 115 Warning
Found more Sync Slaves Found fewer Sync Slaves
 Press [OK] to confirm the message.

The blasting sequence continues.
 Check the number of synchronized Blasters.
 Abort if the number is wrong.

7.2.6. Check the «Blaster Overview»

The overview shows all detected Blasters, their Loggers and the number
of logged detonators.


Blaster.
Verify the numbers:




Stage 2: Programming the Detonators 7
7.3. Stage 2: Programming the Detonators

TO ABORT BLASTING
The controlling <Sync Master> is ready to program the detonators and the
message appears to insert the Master Dongle.


The <Sync Master> Blaster and the <Sync Slave> Blasters program
their detonators.
The screen shows the progress of each Blaster.
<Time to complete> shows the estimated programming time.

If an error occurs, the Blaster tries to re-program the faulty
detonators twice.
After programming, the Blaster overview appears.
Figure 119 Blaster overview with errors
4. If there are errors, you need to confirm the remaining errors of each
Blaster.

7 Stage 2: Programming the Detonators
You cannot continue with unconfirmed errors.

⇒ To confirm the errors, continue in chapter Check and Confirm the
Errors, page 98.
After confirmation, the Blaster overview shows no errors.


Check the Numbers


missing components.

Stage 3: Initiate the Blast 7
7.4. Stage 3: Initiate the Blast

TO ABORT BLASTING
7.4.1. Blaster is Ready to Fire

Prerequisites:
blast.


Blaster status:

7 Stage 3: Initiate the Blast

ready to fire.



BANG
⇒ Continue in chapter Procedure after the Blast, page 102.

Testing the Communication
8. Testing the Communication

TO PREVENT MISFIRES
Problems in communication can abort a remote-controlled Blaster.
 Test the communication some time before the blast.
 Separate the detonator networks of remote-controlled Blasters.
 If blasts of some Blasters are dependent on each other, then fire
them manually one after the other
After the Blasters are installed in their final blasting location, you should
test the communication.
We recommend testing the signal strength some time before the blast.
If necessary, you have enough time to search for a place where the
signal strength is better.
Configure the Mode of each Blaster:

 The controlling Blaster is configured as <Controller>:
[MENU ► Setup ► Blaster] <Blaster Mode>= <Controller>
 Remotely controlled Blasters are configured as <Remote> Blasters:
[MENU ► Setup ► Blaster] <Blaster Mode>= <Remote>
 Synchronized Blasters can be connected to the <Controller> and

the <Remote> Blaster, but are not relevant for the communication
test.
Because tests run on a low, safe voltage level, personnel can work on
the blast site.

8 Exit – Shut Down Blasters
8.1. Exit – Shut Down Blasters

The following chapters describe how to test the communication between
all Blasters, or with a specific Blaster.
You can cancel the test at any time.

 To end the test, press [EXIT] or [BACK].
Figure 123 Test is finished
[SHUTDOWN] Switch off the selected Blaster.

[SHUTDOWN ALL] Switch off all Blasters.
<Remote> Blasters that were prepared for blasting,
do not switch off, but return to the standby mode.

Testing using Radio Modems 8
8.2. Testing using Radio Modems

8.2.1. Antenna Alignment and Position
The usual "line of sight" is a straight line that has no obstacles. But with
radio waves, the "line of sight" is an ellipse-shaped area between the
antennas. If there are objects inside the area, the radio waves are reflected
and reach the receiver with a phase shift. These interferences reduce or
disturb the original signal.
As a rule of thumb, there should be no objects within 8 m (24 ft.)

around the direct path between the antennas and behind the
antennas.
Figure 124 Example for a recommended setup
B1 Blasting device on a higher B2 Blasting device, antenna mounted on a

position tripod
d Distance (~1 km) r Radius of the transmission zone
Figure 125 Antenna on the tripod
① Antenna mounted to the magnetic base of ② Tripod

the antenna extension cable
If you experience low connectivity then lift the antenna 1 – 1.5 m

(3 – 5 ft.) above the ground.

8 Testing using Radio Modems
8.2.2. Test Menu

IMPROVE THE RADIO COMMUNICATION
A bad connection can lead to an abort of the blast.
 Check the radio communication between the controller and the
remote-controlled Blasters.
 Optimize the position of the Blasters.
 Reduce the distance.
 Install the antenna higher above the ground.
 Use a repeater.
 Increase the radio transmission power if possible.
► [MENU ► Testing]
Figure 126 Test menu
Table 17 Functions
<Transmit test signals> Transmit the signals and check the communication.
 Choose to test all receivers, or just 1 receiver.
Prerequisite:
 All receivers are ready to receive signals.
<Receive test signals> Receiver is ready to receive signals.
<Interface test> Checks if the modem processes ist parameters
properly.

8.2.3. Test the Modem – Interface Test

If you changed the modem settings, you must run the following test on
each Blaster.
► [MENU ► Testing ► Interface test]

Display shows: <Applying modem settings. Please wait>.
The Blaster checks if the modem processes the parameters
correctly.
 Modem is tested successfully when the message appears <Modem
settings test successful>.
8.2.4. Determine the Roles: Transmitter – Receiver
When testing, we talk about a “Transmitter” that transmits signals, and

a “Receiver” that receives the signals and responds. The “Transmitter”
analyzes the signals.
 Each Blaster can take the role of the “Transmitter” or the
“Receiver”.
 The Roles do not dependent on the Blasters’ modes,
<Controller> or <Remote> Blaster.
 The operator must remember the roles of the individual Blasters.
When you want to perform the test from the location of the <Controller>,
then use the following functions:
- <Remote> is the receiver, and uses [Receive test signals].
- <Controller> is the transmitter, and uses [Transmit test signals].
When you want to perform the test from the location of the <Remote>
Blaster, use the following functions:
- <Controller> is the receiver, and uses [Receive test signals].
- <Remote> is the transmitter, and uses [Transmit test signals].
If a <Remote> Blaster is prepared for blasting, then it is in standby

mode and automatically the receiver.
 The <Controller> can perform the tests directly.

8.2.5. Prepare the Receiver for Testing

Choose the Blaster that takes the role of a receiver, and choose the
function:
 [MENU ► Testing ► Receive test signals]

When communicating via “radio”, you need to specify if this Blaster is
behind a <Repeater>.
Figure 127 Select the Repeater
 If this Blaster is NOT behind a <Repeater>, choose <No Repeater>.

 If this Blaster is behind a <Repeater>, then select the correct repeater
number.
 Receiver is ready for testing.

8.2.6. Run the Test on the Transmitter

The transmitter can check the communication to other Blasters.
Prerequisites:
 Roles of transmitter and receiver are decided.
 Receivers are in standby mode or prepared to receive test signals.
On the transmitter choose:

 [MENU ► Testing ► Transmit test signals]
 Choose a function:
[Test all Blasters] Test the communication with more than 1
Blaster.
[Test a single Blaster] Test the communication to a specific
Blaster.
⇒ Functions are described in the next sections.
8.2.7. Transmitter: Check all Receivers

The transmitter can check the communication with the receivers. The test
is usually performed by the Controller.
1. [MENU ► Testing ► Transmit test signals ► Test all Blasters]

Example: Transmitter = B01, Receivers = B02 and B05
Figure 129 List of Blasters
<Status> = <Test>, all Blasters are activated for the test.

2. Select each Blaster that is not present or that you don't want to check
and press [TOGGLE].
The status toggles between <Test> and <Do not test>.
3. Verify that all Blasters that you want to check have the status <Test>.

4. To start the test, press [TEST].

The transmitter communicates with all receivers and displays the
results.
Figure 130 RF Test
<Signal -64(-64)>, signal strength in [dBm]

– First value is measured in the receiver.
– Second value in brackets is measured in the transmitter.
– Analysis, <Good>, <Bad> or <Medium>
<Connectivity>, probability in percent of a successful radio
communication during the complete blasting sequence is displayed
after 30 measurements.
<Last reply>, time since the last reply
5. Watch the bar at the bottom of the screen.
6. If the bar is not green, then adjust the positions of the Blasters and
press [RESET] to test again.
 The communication is reliable when the bar at the bottom of the
screen is green.
To exit and shut down Blasters, see section Exit – Shut Down
Blasters, page 128.
RF connectivity:
99 - 100%: Communication will be successful
95 – 98%: Abort is possible
below 95%: Abort is most likely; blasting is not possible

8.2.8. Transmitter: Test a specific Receiver

Prerequisite:
 The receiver is ready to receive test signals.
On the transmitter choose the test function:
1. [MENU ► Testing ► Transmit test signals ► Test a Single Blaster]

Example: Transmitter B01, Receiver B05
2. Choose the Blaster in the list and press [TEST].
The transmitter communicates with the chosen Blaster, and displays
the communication probability after 30 data packets are transmitted
and received.
Figure 131 Test the communication with a specific Blaster
<RF Connectivity>, probability in percent of a successful

communication during the blasting sequence
<Sent Packets>, number of packets that the Controller sent
<Packets lost>, number of packets that the Controller sent but not
received
<Last packet>, time elapsed since the last packet was received
<Testing time>, time since the test has begun
<Bxx>, strength of the last signal measured in the Blaster
3. Watch the signal strength and the percentage of the <RF
Connectivity>.
4. If the bars are not green, then adjust the positions of the Blasters and
press [RESET] to test again.
 The communication with a specific Blaster is reliable when the
bars are green.
Blasters, page 128.
RF connectivity:
99 - 100%: Communication will be successful
95 – 98%: Abort is possible
below 95%: Abort is most likely; blasting is not possible

8.2.9. What does Connectivity indicate?

The connectivity is the probability of a successful communication during
the blasting sequence. The connectivity considers the number of lost
packets, possible retries, and the total number of signals that are needed
in the blasting sequence.
Figure 132 RF Connectivity (examples)

probably OK bad
The connectivity is displayed in percent and as a colored bar.

RF connectivity 99 - 100%: Green indicates that the communication will be successful
during the complete blasting sequence.
95 – 98%: Yellow indicates that the communication might fail in 2 to 5
blasts of 100 blasts.
below 95%: Red indicates that the communication will most likely fail, and
blasting will not be possible.
10 packets lost If 10 packets are lost successively, then the connectivity drops to
zero - and stays zero.
 Identify the source of the problem (For example radio interference,
mobile phone, Bluetooth devices, big rocks).
 Adjust the positions of the Blaster.
 Press [RESET] to delete the values and start a new test.
Bxx The lower bars on the screen show the signal strength of the transmitter
and the receiver.
Although the connectivity is high, interferences can disrupt the signal and
data packets can get lost.
 Find the source of the interference, for example search for obstacles
near the path of the radio beam.
⇒ See also Antenna Alignment and Position, page 129.
If the test results are bad, then install a <Repeater> between the
Blasters, and test the communication again.

8.2.10. Increase the Radio Distance with a Repeater

When the controlling Blaster has no line of sight to the <Remote> Blasters
or the signal strength is bad, then install a <Repeater>.
 A repeater is a standard Blaster 3000 that is set in the repeater
mode.
 The <Repeater> increases the radio distance to <Remote> Blasters
and bypasses obstacles.
Each <Repeater> must have a line of sight to the <Controller> and to

the <Remote> Blasters that will use this <Repeater>.
 A <Repeater> cannot communicate with another <Repeater>.
Figure 133 Example with 2 repeaters
① Controller is not in line of sight ④ <Remote> Blaster behind Rep.1

② Repeater 1 ⑤ Repeater 2
③ <Remote> Blaster behind Rep.1 ⑥ <Remote> Blaster behind Rep.2
Configure a <Repeater>:
[MENU ► Setup ► Blaster ► Blaster Mode ► Repeater]

Prepare the <Repeater> Blaster:

1. Switch on the <Repeater>.
Blaster performs a self-test.
2. If an error occurs, then abort and solve the problem.
Figure 134 Start the repeater
To start REPEATER, press [OK]
3. Press [OK].
You need to specify the number of this <Repeater>:
Figure 135 Choose repeater number
4. Select the number.

The number of the Repeater must be unique in this blast.
5. Press [OK].
 Repeater is activated and displays its number, for example
<Repeater 2 activated>.
A Blaster in <Repeater> mode is only a means of communication.

 A repeater is not displayed on any Blaster overview screen.
 When activated, a repeater displays <Repeater x activated>.
 After the blast, a repeater must be switched off manually.

8.2.11. Testing in a Setup with a <Repeater>

In a test with a Repeater, the transmitter has no information on the strength
of signals that the Repeater receives.
The red signals "B" and "C" are not displayed on the transmitter.
Figure 136 <Repeater> in a blast setup
① Transmitter ② <Repeater> ③ < Receiver

A Signal measured in the B-C Signals in the Repeater D Signal in the Receiver
Transmitter
To measure the signals that the Repeater receives, we recommend

testing the signal strength to and from the Repeater separately.
 Run 2 tests, where the <Repeater> takes the role of a transmitter
and of a receiver.
Test Signals between <Repeater> and Receiver

Figure 137 <Repeater> tests the receiver’s signals
① no role ② <Repeater> ③ Receiver
The Receiver ③ needs to be prepared:

1. [MENU ► Testing ► Receive test signals]
2. In the list of repeaters, select <No Repeater> and confirm.
 Receiver is ready to receive test signals.
The <Repeater> ② acts as transmitter:

1. [MENU ► Testing ► Transmit test signals]
2. Run [Test all Blasters].
3. Run [Test Single Blasters].
 <Repeater> provides information on the signal strength.

Test Signals between <Repeater> and Transmitter

Figure 138 Transmitter reads <Repeater> signals
① Transmitter ② <Repeater> ③ no role
The <Repeater> ② acts as Receiver:

1. [MENU ► Testing ► Receive test signals]
2. In the list of repeaters, select <No Repeater> and confirm.
 <Repeater> is ready to receive test signals.
Run the following tests on the Transmitter ①:

2. Run [Test all Blasters].
3. Run [Test a Single Blaster].
 Sender provides information on the signal strength.
When the signal strength is good, then you may continue with the blast
preparation.

Testing in a Leaky Feeder Network 8
8.3. Testing in a Leaky Feeder Network

8.3.1. Check the Signal Strength
Table 18 Functions
<Transmit test signals> Transmit the signals and check the communication.
 Choose to test all receivers or just 1 receiver.
Prerequisite:
 All receivers are ready to receive signals.
<Receive test signals> Receiver is ready to receive signals.
<Interface test> Checks if the modem processes ist parameters properly.
<Monitoring noise> Search for interfering signals that might disturb the
communication.
<Traceroute> Communicate with other Blasters to evaluate the signal
quality.

each Blaster.

correctly.

8 Testing in a Leaky Feeder Network

“Receiver”.


function:


8.3.5. Run the Test on the Transmitter

The transmitter can check the communication to other Blasters.
Prerequisites:
 Roles of transmitter and receiver are decided.
 Receivers are in standby mode or prepared to receive test signals.
On the transmitter choose:

 [MENU ► Testing ► Transmit test signals]
 Choose a function:
[Test all Blasters] Test the communication with more than 1
Blaster.
[Test a single Blaster] Test the communication to a specific
Blaster.
When using the 2-modem configuration, an additional function

appears to test the communication with the Controller from the position
of the <Remote> Blaster.
 Choose [Test Controller].

Figure 141 Test the Controller
 Enter the Blaster ID, or adjust it with [▲]/[▼].

 Testing has started.

8.3.6. Transmitter: Check all Receivers

The transmitter can check the communication with the receivers. The test
is usually performed by the Controller.
1. [MENU ► Testing ► Transmit test signals ► Test all Blasters]

Example: Transmitter = B01, Receivers = B02 and B05
Figure 142 List of Blasters
<Status> = <Test>, all Blasters are activated for the test.

2. Select each Blaster that is not present or that you don't want to check
and press [TOGGLE].
The status toggles between <Test> and <Do not test>.
3. Verify that all Blasters that you want to check have the status <Test>.
4. To start the test, press [TEST].
The transmitter communicates with all receivers and displays the
results.
Figure 143 Test result
<Signal>, signal strength in [dBm]

<Last reply>, time since the last reply
5. If the signals are too low, or the last reply takes too long, then check
the connections to the network.
6. To start a new test, press [RESET].
 Communication is reliable when the signal strength is high, and
the time since the last reply is short.
Blasters, page 128.

8.3.7. Transmitter: Test a specific Receiver

This test is usually performed on a Remote Blaster at its proposed location
for blasting to check its communication with the Controller.
Prerequisite:
 Receiver is prepared to receive test signals.
On the transmitter choose the test function.
1. [MENU ► Testing ► Send test signals ► Test a single Blaster]

Example: Transmitter B03, Receiver B01 (Controller)
Figure 144 Test the communication with a specific Blaster
2. Select the receiver and press [TEST].

The transmitter communicates with the chosen receiver and displays
the signal strength.
<Sent Packets>, number of packets that were sent
<Packets lost>, number of packets that were sent but not received
<Transmitter>, strength of the last signal
<Bxx>, strength of the last signal measured in the receiver
3. Watch the signal strength.
4. If the signal is very low (high negative value), then troubleshoot:
- Search for a better location of the Remote Blaster or its antenna.
- Check the Leaky Feeder environment.
5. To restart the test, press [RESET].
 The communication with a specific Blaster is reliable when the
signal strength is high and the time since the last reply is short.
Blasters, page 128.
Signal strength:
-44 dBm Strong signal
-70 dBm Minimum signal strength
-100 dBm Weak signal, probably drowning in noise

8.3.8. Monitoring the Noise

When the Blaster is positioned in its proposed location for blasting, you
can measure the strength of interfering signals.
In this test, the modem is passive and needs no other Blaster to

communicate with.
1. [MENU ► Testing ► Monitoring noise]

The modem listens for interfering signals on the dedicated channel.
Figure 145 Monitoring signal strength
<Average Noise>, signal strength of noise

<Average RSSI>, (Received Signal Strength Indicator)
2. To quit, press [BACK].
 Interfering signals are not a problem when their strength is low.
The average noise should be very low (high negative number).

The average RSSI should be at least 15 dBm stronger, so that you can
adjust the threshold (RSSI Trip) in the interface settings:
 RSSI Trip = -90 dBM or -100 dBM

8.3.9. Traceroute
You can check the signal strength of a message on its way from the
transmitter to the receiver.
 Test from the proposed location of the <Remote> Blaster to the
Controller to find the best position of the antenna of the Remote
Blaster.
 Test the communication from the Controller to the other Blasters
before firing to check if the communication is still good.
The receiving Blaster is in standby mode:

 [MENU ► Testing ► Receive test signals]
 Or prepared for blasting and the Dongle is written.
Run the test on the transmitter:

1. [MENU ► Testing ► Traceroute]
The example shows the Traceroute for the 3-modem configuration.
Figure 146 Traceroute (example Remote Blaster B03 to Controller)
2. Choose the Blaster whose communication route you want to test.

3. Press [ENTER].
The communication data is continuously displayed.
<1000>, Controller
<2000>, LF router (not in the 2-modem configuration)
<2101> – <21xx>, Remote Blaster (2100 + ID)
<yy dBm>, measured signal strength
<BH>, number of bad headings
<BP>, number of bad packages
<RT>, number of retries
4. To stop the test, press [STOP].
The summary is displayed:
<Tx>, <Rx>, number of packages transmitted and received
<Lost>, number and percentage of lost packages
<Min>, <Max>, minimum and maximum response time
<Avg>, average response time
5. If the signal strength is weak the search for another location of the
<Remote> Blaster or its antenna.
 The communication is reliable, when there are no lost packages.

8 Testing in a LAN, Wi-Fi, or mobile Network
8.4. Testing in a LAN, Wi-Fi, or mobile Network

Table 19 Functions
<T1: Signal test Controller to Remote> Controller transmits test signals and checks
the communication.
Prerequisite:
 <Remote> Blasters are prepared for
blasting, blue Dongle is available.
<T2: Signal test Remote to Controller> <Remote> Blaster transmits test signals to
the <Controller>.
 <Controller> must be in listening mode.
<T2: Controller in listening mode> Controller is ready to receive test signals.
<Interface test> Checks if the modem processes ist
parameters properly.
8.4.2. Test the Interface

If you changed the interface settings, you must test the connection on each
Blaster.

Display shows <Applying modem settings. Please wait.>
The test may take some time.
► If the test takes longer than usual, then check the connections.
 <Modem settings test successful> indicates a successful connection
to the network.

Testing in a LAN, Wi-Fi, or mobile Network 8
8.4.3. T1: Signal Test from <Controller> to <Remote>

The <Controller> can check the communication with all remote Blasters.
Prerequisites:
 The <Remote> Blasters are prepared for blasting.
 The remote dongles are written and available.
Run the following test on the <Controller>.

1. [MENU ► Testing ► T1: Signal test Controller to Remote]
The request to insert the dongles appears.
2. Insert the dongles of the <Remote> Blasters that you want to test.
3. Press [OK] to start the test.
The <Controller> communicates with the <Remote> Blasters and
displays the result.
The test may take some time.
Figure 148 Test all receivers
<Signal>, signal strength for Wi-Fi signals displayed in dBm and with
a block diagram.
<Last reply>, time since the last answer has been received.
“---“ (red rectangle), the fields are empty when there is no reply.
4. With [RESET] you can restart the test.
 Communication is reliable when the signal strength is high (in
Wi-Fi) and the time since the last reply is short.
Signal strength:
-45 dBm Strong signal
-120 dBm Weak signal, probably drowning in noise
Blasters, page 128.

8 Testing in a LAN, Wi-Fi, or mobile Network
8.4.4. T2: Signal Test <Remote> to <Controller>

On a <Remote> Blaster, you can test the communication with the
<Controller>.
Prerequisites:
 The <Controller> is in listening mode:
[MENU ► Testing ► T2: Controller in listening mode]
 The IP address of the <Controller> is displayed.
On the <Remote> Blaster start the following test.

1. [MENU ► Testing ► T2: Signal test Remote to Controller]
The message appears to enter the IP address of the <Controller>.
Figure 149 IP address
2. To enter the IP address, press [EDIT].

3. When the IP address is correct, press [CONFIRM].
4. Wait until the <Remote> Blaster has joined the network.
Figure 150 Signal strength
Wi-Fi (WLAN) LAN
<Signal>, signal strength is displayed in [dBM] and as a block

diagram for Wi-Fi communication.
<Last reply>, time since the last reply should be small.
When there is no reply, the time since the last reply is empty.
 Communication is reliable when the signal strength is high (Wi-
Fi) and the time since the last reply is short.

Testing the Analog Phone Connection 8
8.5. Testing the Analog Phone Connection

8.5.1. Test Menu
Table 20 Functions
<Transmit test signals> The transmitter establishes an analog phone
connection to the receiver.
 Works only when the receiver is ready to
receive test signals.
<Receive test signals> The receiver is ready to receive signals, to
take the call and respond.
<Interface test> Checks if the modem processes ist
parameters properly.

each Blaster.

correctly.

8 Testing the Analog Phone Connection

“Receiver”.


function:


Testing the Analog Phone Connection 8
8.5.5. Test the Analog Connection

Prerequisite:
 The receiver is ready to receive test signals.
On the transmitter choose the test mode.

Figure 152 Phone number of the receiver
2. Enter the phone number of the receiver.

3. When the phone number was entered before, press [ADDRESS] and
choose the number in the list.
4. Press [ENTER] to establish the connection.
Example: Transmitter = B01, Receiver = B06
Figure 153 Signal test
When the transmitter has found the receiver, it displays the analysis:
<Sent Packets>, number of packets that were sent
<Packets lost>, number of packets that were sent but not received
5. If the connection cannot be established, check the phone line and the
phone numbers.
6. With [RESET], you can start the test again.
 The communication is reliable when the time of the last packet
is short.

Blasting with Remote-Controlled Blasters
9. Blasting with Remote-Controlled Blasters
The following instructions describe the blasting procedures with all

options.
 Please skip the instructions on <Sync Slave> Blasters and
<Repeaters> if they are not relevant.
9.1. Prepare for Blasting

 Blasters and Loggers are fully charged. 
 The Loggers are installed and prepared for blasting. 
 All Blasters are positioned in a safe place. 
 Blaster modes are configured: [MENU ► Setup ► Blaster]: 
- Controller: <Blaster Mode> = <Controller>
- Remote Blaster: <Blaster Mode> = <Remote>
- Sync slave Blasters: <Blaster Mode> = <Sync Slave>
 All Blasters have a unique ID number. 
- No ID is used twice.
- Check that <Sync Slave> Blasters have a higher ID than their
<Remote> Blaster.
 The termination resistor is adjusted in all synchronized Blasters. 
 The method of communication is configured: 
- [MENU ► Setup ► Interface].
- Surface radio modems, or
- Underground LAN, Wi-Fi, analog phone, Leaky Feeder
 In surface applications, prepare the Repeater if necessary. 
- [MENU ► Setup ► Blaster] <Blaster Mode> = <Repeater>.
- In the start menu, start the Repeater mode.
- Choose a specific Repeater number.
 Communication is tested [MENU ► Testing]. 
 NO dongle is inserted in any Blaster's dongle port. 
 The blast site is evacuated. 
Prepare the units in the following order:

1. <Sync Slave> Blasters
2. <Remote> Blasters
 The system is ready to start the blasting sequence on the
<Controller>.
NO dongle is inserted into the Blaster's dongle port.

 Insert the dongle only when asked to do so.
 It takes up to 1 second for the Blaster to recognize the dongle.

Prepare for Blasting 9
9.1.1. Remote-Controlled Surface Blast

The diagram shows the preparation of all Blasters in a remote-controlled
blast performed on the surface.
Figure 154 Preparation of a remote-controlled blast
Position <Remote>
Blasters and <Controller>
Need
yes Activate <Repeater>
<Repeater> • Assign Repeater number
no
Test radio communication
Clear blast sites

Prepare <Sync Slaves>:
• Position <Sync Slave>
Sync yes • Switch on <Sync Slaves>
Slaves? • Connect sync cable
• Connect Loggers
• Sleep or standby
no
Prepare <Remote>: With Sync slaves

• Switch on <Remote>
• Connect Loggers
• Enter number <Sync Slaves>
• Wake up <Sync Slaves>?
Numbers of Loggers and no

User aborts
dets OK?
Acces via Repeater?

• Enter Repeater number
• Write remote dongle
Start blasting sequence on

<Controller>
Background color:

9.1.2. Remote-Controlled Underground Blast

The diagram shows the preparation of all Blasters in a remote-controlled
underground blast.
Figure 155 Preparation underground
Position <Remote>
Blasters and <Controller>
Test the signal strength
Clear blast sites

Prepare <Sync Slaves>:
• Position <Sync Slave>
Sync yes • Switch on <Sync Slaves>
Slaves? • Connect sync cable
• Connect Loggers
• Sleep or standby
no
Prepare <Remote>: With sync Slaves

• Switch on <Remote>
• Connect Loggers
• Enter number <Sync Slaves>
• Wake up <Sync Slaves>?
Numbers of Loggers and dets no

User aborts
OK?
yes
Write remote dongle (Not with analog phone)
Blasters in standby mode
Start blasting sequence on

<Controller>
Background color:

Prepare for Blasting 9

9.1.4. Prepare <Sync Slave> Blasters

WARNING
You must wake up <Sync Slave> Blasters that are in sleep mode, or
they are not included in the blast!
 Wake up <Sync Slave> Blasters that are in sleep mode.
 If you are unsure in which mode the <Sync Slave> Blasters are,
choose [YES] for wake up.
Initialize <Sync Slave> Blasters first:

 Check the Blaster ID. 
A <Sync Slave> Blaster has higher ID number than its <Remote>.
 Switch on and wait until the self-test is passed. 
 Check the termination resistor [MENU ► Setup ► Interface ► Sync 
Line].
 Connect the firing cable from the Loggers to the Blaster. 
 Start the initialization with [OK]. 
 Check the numbers of Loggers and detonators in the overview. 
 When you fire the blast later than 12 hours, choose the sleep mode, 
else choose standby mode.
WARNING – Risk of Misfire!
If a <Sync Blaster> is in the sleep mode, then choose the special
wake-up command for the controlling Blaster.
 Connect the sync cable. 
⇒ For more information, see chapter Prepare <Sync Slave> Blasters,

page 116.

9 Prepare <Remote> Blasters
9.2. Prepare <Remote> Blasters

You must prepare all <Remote> Blasters before you start the <Controller>.
Prerequisites:
 Communication between the <Remote> Blaster and the <Controller>
Blaster is tested and working sufficiently.
 <Sync Slave> Blasters are prepared and in standby or sleep mode.
Start the <Remote> Blaster

1. Switch on the <Remote> Blaster.
Blaster performs a self-test.
2. If an error occurs, then abort and solve the problem.
 Display shows instructions to connect Loggers and <Sync Slave>
Blasters.
Figure 156 Prepare for blasting
Depending on the blast configuration, connect Loggers and Blasters:

 Connect the Loggers via firing cable to the black output terminals.
 Connect <Sync Slave> Blasters via sync cable to the yellow output
terminals.
 Press [OK] to continue.

Prepare <Remote> Blasters 9
9.2.1. Activate <Sync Slave> Blasters

connected to the <Remote> Blaster.





mode.
⇒ Continue in the next section.

9.2.2. Access via Repeater?

When communicating via “radio”, you need to specify if this Blaster is
behind a <Repeater>.
Figure 159 Select the Repeater
 If this Blaster is NOT behind a <Repeater>, choose <No Repeater>.

 If this Blaster is behind a <Repeater>, then select the correct repeater
number.

Prepare <Remote> Blasters 9

WARNING
Detonators will NOT fire if they are connected to Loggers or Blasters
that are not recognized!
Risk of misfires in the muck pile!
 Verify the number of Blasters.
 Verify the number of Loggers and detonators.
In the example, the <Remote> Blaster B02 has a <Sync Slave>

Blaster B03.
Verify the numbers:




9.2.4. Write the Remote Dongle
When communicating via analog phone, continue in section Blasting

– Analog Phone Communication, page 176.
A message appears to insert the Remote Dongle.

Figure 161 Write communication data to the Remote Dongle
Ready to write Remote Dongle.

Insert remote Dongle.
1. Insert the blue Remote Dongle in the Blaster's dongle port.

The Blaster writes data and a unique password to the Remote
Dongle so that the <Controller> can communicate this Blaster.
2. Remove the Remote Dongle when asked to do so.
3. Clearly mark the Remote Dongle.
 Communication data is written to the Remote Dongle.
Preparation of the Remote Blaster is completed

 Wait until the Blaster have finished the preparation.
Figure 162 Preparation finished
Radio modems Analog modems
Bxx: Standby Please wait…

Waiting for connection
 Do NOT switch off the Blaster.

 Close the lid of the Blaster's case.
 Take the Remote Dongle to the controlling blaster.
 <Remote> Blaster is prepared.
Remote Dongles (blue dongles) are general and can be swapped

between <Remote> Blasters.
 When you prepare a <Remote> Blaster it writes a newly
generated password to the Remote Dongle.
 The controlling Blaster adds this password to all signals while
communicating with the <Remote> Blaster.

9.3. Stage 1: Start the Blasting Sequence

When communicating via analog phone, continue in section Blasting
– Analog Phone Communication, page 176.
Figure 163 Blasting sequence (Radio, LAN, Wi-Fi communication)
Evacuate the blasting area
Switch on Controller
Connect Loggers and Sync Slaves
Stage 1
Press [OK] to initialize
Initialization
Choose remote blasting mode.
Establish Ccmmunication
manual automatic concurrent
Insert all remote dongles
Enter Sync Slave number

Deactivate Logger?
User abort
yes Stage 2
no Programming
Insert master dongle
yes
yes no
no yes
yes
Blaster overview: no Concurrent mode:
Number Loggers + dets correct? Deactivate Blaster? no
yes
Stage 3
Manual mode:
FIRE
Select Blasters to fire?
no
yes
System check: Detonation
System no • Sync Slaves OK? yes
abort • Remote Blasters OK?
yes
yes
yes no Automatic Another Blaster?
Manuel mode?
mode?
no
Reports
Background color:


DANGER
9.3.2. Activate the Controller – Establish Communication

Establish the communication to all connected devices.
Prerequisites:
 All Blasters have a unique ID number.
 Remote communication is tested successfully.
 All <Sync Slave> Blasters are prepared and in sleep or standby
mode.
 All <Remote> Blasters are prepared and in standby mode.
1. Switch on the <Controller>.

2. Continue only when the Blaster passes the self-test.
 Depending on the setup, connect Loggers and Blasters:

Loggers If there are Loggers to connect directly, then connect
the Loggers via the black output terminals.
Synchronized Connect all synchronized Blasters via the sync cable
Blasters to the yellow sync terminals.
If you connect the synchronized Blasters later, the
controlling Blaster will not recognize them!
 With [OK] you start the blasting sequence.

9.3.3. Choose the Blasting Mode

WARNING
Misfires on blast sites whose success depends on each other!
 Choose the <Manual> blasting mode.
 NEVER use the <Concurrent> blasting mode.
When more than 1 <Remote> Blaster is present, you need to choose the
blasting mode:
Figure 165 Blasting modes
<Manual> You give the FIRE command manually for one Blaster
after the other.
<Automatic> Each Blaster initiates its detonators automatically
30 seconds after the previous Blaster.
<Concurrent> WARNING – Risk of misfires
 Use only for independent blast sites:
All Blasters initiate their detonators nearly at the same
time.
The firing timing depends on the exact time when the
Remote Blaster receives the fire command and the
quality of the communication with its Loggers.
 Select the blasting mode and continue with [OK].
Firing behavior:
 If one Blaster aborts because of an error, the other Blasters will
fire their detonators.
 If a Blaster aborts that is in a remote group, then the whole
remote group aborts.

9.3.4. Read the Remote Dongles

Read the blue Remote Dongles of all <Remote> Blasters into the
<Controller>.
Figure 166 Insert Remote Dongle
1. Insert a blue Remote Dongle.

Blaster reads the information on the dongle and updates the
information on the screen.
Figure 167 Read Remote Dongles
Line 1: Summary of Blasters, Loggers, and detonators

<Role>, Blaster configuration
<Conn.>, connection of a Blaster
<+Rx>, additional <Repeater>
2. Remove the Remote Dongle.
3. Repeat from step 1, until all Remote Dongles are read.
4. When all Remote Dongles are read, and all Blasters are in the list,
press [OK].

9.3.5. Check <Sync Slave> Blasters

connected to the <Controller>.





mode.

9.3.6. Verify the Numbers of Blasters, Loggers and Detonators

The controlling Blaster communicates with all other Blasters and updates
the overview.
When all Blasters respond, the button [OK] activates.

Blaster.
Verify the numbers:




9.4. Stage 2: Programming the Detonators

Prerequisites:
 You confirmed that the «Blaster Overview», the number of Blasters,
Loggers, and detonators are correct.
The controlling Blaster is ready to program the detonators and the



The controlling Blaster orders all other Blasters to program their
detonators, and programs its own detonators.
The screen shows the progress (charging, programming, calibration)
and leakage current for each Blaster.
<Time to complete>, approximate programming time

Each Blaster checks its Loggers, detonators and the leakage current.
If errors on detonators are detected, the Blaster tries to re-program
the detonators.
4. If an error occurs, you need to confirm the errors. Continue in the
chapter Check and Confirm the Errors, page 98.
5. If the radio communication is bad, see next page.
 When the programming is successful, the Blaster overview appears.

9.4.1. Retry Counter

If the communication is disturbed, the controlling Blaster tries up to 19
times to send a signal. The number of retries depends mainly on the
number of Blasters and the signal quality.
Figure 173 Retry counter
A remote-controlled Blaster aborts if it does not receive a valid signal

within 90 seconds (Keep-alive counter).

When using the radio communication, you can check the signal strength.
To check the radio communication, press [SIGNAL TEST].

Figure 174 Signal test
Signal:
 Green and yellow bars indicate a successful communication.
 If the bar turns red, communication is not possible.



Check the Numbers


missing components.
⇒ To continue with stage 3, please refer to chapter Stage 3: Initiate

the Blast, page 173.
⇒ If a Blaster has problems, you can deactivate it when using the

concurrent blasting mode. See chapter Exclude Blasters in
<Concurrent> Blasting Mode, page 172.

9.4.4. Exclude Blasters in <Concurrent> Blasting Mode

WARNING
Detonators of excluded Blasters will NOT fire.
Risk of misfires, or unstable rock and roof condition.
 Verify that the blast design allows to exclude these Blasters.
The shotfirer-in-charge can decide to remove a <Remote> Blaster from

the blast. When the de-selected Blaster has sync Slaves, the sync Slaves
are de-selected automatically.
Prerequisites:
 The function to de-select Blasters must be installed and activated in
the factory settings.
 The blasting mode <Concurrent> is chosen.
1. To remove a Blaster, select the Blaster and press [DESELECT].

Figure 176 Deselect a Blaster
Deselect a Blaster Select a Blaster
“---“, a Controller without Loggers cannot be de-selected.

2. To include the Blaster, press [SELECT].
WARNING – Risk of misfires

 Verify that you've excluded the correct Blaster.
3. Verify that you selected or deselected the correct Blasters.

4. To confirm your selection, press [OK].
A warning appears that you removed a Blaster.
Figure 177 Warning
1 Remote will be deactivated

Continue?
5. To confirm, press [YES].

6. To abort, press [NO].
 The selected <Remote> Blasters are removed.

9.5. Stage 3: Initiate the Blast

TO ABORT BLASTING
9.5.1. Blaster is Ready to Fire

Prerequisites:
blast.


concurrent blasting mode manual, or automatic blasting mode

Blaster status:

9 Stage 3: Initiate the Blast

The procedure depends on the chosen blasting mode.
 The yellow marked Blasters are going to fire.
 <Sync Slaves> fire with their appropriate <Remote> Blaster.
<Manual>  You can select a Blaster with [▲] or [▼].
 You initiate the selected Blaster with the [FIRE]
buttons.
<Automatic> The first Blaster to fire has lowest Blaster ID.
 You must initiate the first Blaster manually.
Other Blasters fire in sequence 30 seconds after the
previous Blaster, depending to their Blaster ID.
 You can fire each blast earlier with the [FIRE] buttons.
<Concurrent> All Blasters fire nearly at the same time.
Firing behavior:



BANG

9.5.3. Fire the next Blaster

When there are still Blasters to fire, their status indicates <Ready to fire>
or <Holding>.
Firing behavior:
<Fire command sent>, command to fire was sent to the Blaster

<Ready to fire>, Blaster fires its detonators in the next blast
– and countdown of 30 seconds for Blasters in automatic firing
mode
<Holding>, Blaster that fires later
If one Blaster aborts, then check that firing the next blast does not
endanger the later successes of the aborted blast and the next blasts.
Continue, depending on the blasting mode:

<Manual>  Select the next Blaster.
 To fire the blast, press [FIRE].
<Automatic>  Wait until the next Blaster fires.
 Optionally, to fire immediately, press [FIRE].
After a Blaster has fired, the blast status updates.

⇒ When all Blasters have fired, continue in the chapter Procedure
after the Blast, page 102.

9 Blasting – Analog Phone Communication
9.6. Blasting – Analog Phone Communication

9.6.1. Stage 1: Start the Blasting Sequence
When all preparations are completed, and the blasting area is

evacuated, then the shotfirer may start the blasting sequence.
Figure 180 Remote blasting sequence – Analog phone
Evacuate the blasting area
Switch on Controller
Stage 1
Press [OK] to initialize Initialize
Enter the phone number of Remote
Deactivate Logger?
yes User abort
Stage 2
Insert master dongle Programming
yes
yes no
no yes
no
yes
Stage 3
FIRE
no
yes
System check: Detonation
System no • Sync Slaves OK? yes
abort • Remote Blasters OK?
Reports
Background color:

Blasting – Analog Phone Communication 9
9.6.2. Activate the Controller – Establish Communication

DANGER
Establish the communication to all connected devices.

Prerequisites:
 All Blasters have a unique ID number.
 Remote communication is tested successfully.
 All <Sync Slave> Blasters are prepared and in sleep or standby
mode.
 All <Remote> Blasters are prepared and in standby mode.
1. Switch on the <Controller>.

2. Continue only when the Blaster passes the self-test.
When communicating via analog phone, the Controller usually has

no Loggers and no <Sync Slave> Blasters connected.
3. You do not need to connect a device.
4. Press [OK] to start the blasting sequence.
 Controller is ready.

9.6.3. Phone Number for Analog Modem Connection

When an analog modem is installed, the message appears to enter the
phone number of the connection to the <Remote> Blaster.
Figure 182 Analog phone number
1. Enter the analog phone number.

If the phone number was already used, it will be in the phone book.
2. Optionally, press [ADDRESS] and check the phone book for the
correct number.
3. Confirm the correct phone number with [ENTER].
 Analog phone number is chosen.
9.6.4. Read the Remote Dongle

Read the blue Remote Dongle of the <Remote> Blaster into the
<Controller>.
Figure 183 Insert Remote Dongle
1. Insert the blue Remote Dongle.

Blaster reads the information on the dongle and updates the
information on the screen.
2. Remove the Remote Dongle.
3. Press [OK] to continue.

9.6.5. Verify the Numbers of Blasters, Loggers and Detonators

WARNING
Detonators will NOT fire if they are connected to Loggers or Blasters
that are not recognized!
Risk of misfires in the muck pile!
 Verify the number of Blasters.
 Verify the number of Loggers and detonators.
The controlling Blaster communicates with all other Blasters and updates
the overview.
When all Blasters respond, the button [OK] activates.
Verify the numbers:




9.6.6. Stage 2: Programming Detonators

Prerequisites:
 You confirmed that the «Blaster Overview», the number of Blasters,
Loggers, and detonators are correct.
The controlling Blaster is ready to program the detonators and the



The controlling Blaster orders all other Blasters to program their
detonators, and programs its own detonators.
The screen shows the progress (charging, programming, calibration)
and leakage current for each Blaster.
(100) number of detonators
<Time to complete>, approximate programming time

Each Blaster checks its Loggers, detonators and the leakage current.
If errors on detonators are detected, the Blaster tries to re-program
the detonators.
4. If an error occurs, you need to confirm the errors. Continue in the
chapter Check and Confirm the Errors, page 98.
5. If the radio communication is bad, see next page.
 When the programming is successful, the Blaster overview appears.



Check the Numbers


missing components.

9.6.8. Stage 3: Initiate the Blast

TO ABORT BLASTING
Prerequisites:
blast.


Blaster status:
[OVERVIEW]. Continue in chapter Blaster Overview with confirmed
Errors, page 100.


ready to fire.



BANG
After a Blaster has fired, the blast status updates.

⇒ When all Blasters have fired, continue in the chapter Procedure
after the Blast, page 102.

Errors and Troubleshooting
10 Self-Test in the Blaster
10. Errors and Troubleshooting

10.1. Self-Test in the Blaster
When the Blaster is switched on, it performs a self-test:
Figure 190 Example: Self-test passed
ORICA
***FW Version : xxxx
***Serial Number :
***BATT: Voltage =
***BATT: Current =
***BATT: Level = 100%
***BATT: Temp. =
+++KAP-FW:
+++KAP: Internal Self-test ok
+++Overvoltage test ok
+++LI-FW:
Self-test passed
Line 1-6 Firmware version, serial number, battery data
Line 7-9 KAP version, overvoltage test
<LI-FW> Logger Interface firmware
Self-test failed:
If the self-test fails, an error message appears.
1. Check and retry.
2. If the self-test is passed, then check the settings.
Sometimes internal data are corrupted and standard parameters are
restored.
3. If the self-test fails again, then do NOT use this device.
DANGER
 NEVER use a defect device.
- Export the reports.
- Send the reports with a description of the problem to the Orica
Technical Service.
 Self-test is performed.

Generate a Backup of the Operating System 10
Table 21 Possible errors during self-test
Code Reason Code Reason
1 Self test initialization failed! 10 KAP internal self-test failed!
2 Main Switch is Off! 11 Battery check failed!
3 Overvoltage detected! 12 Low battery!
 Charge device, try again.
4 Overvoltage test failed! 13 Self-test timed out!
5 Unable to connect to the Logger 14 Failed to read RW-image!
interface!
6 Logger interface is not compatible! 15 Bridge error
7 Unable to switch off the Logger 16 Forced error
interface!
8 Keep alive process (KAP) not 17 Logger interface failed
available!
 Check and adjust date and time.
9 KAP not compatible! 18 Logger/Sync interface failed
10.2. Generate a Backup of the Operating System

You can generate a system image of the state of the Blaster 3000.
 The system image is a file that includes all settings and data that are
needed for an analysis.
If your device reacts strangely, then generate a system image:

1. Choose the menu: [MENU ► Reports]
2. Connect a USB storage device.
3. Wait until the USB device is recognized.
4. Press the following buttons at the same time: [✔] + [7] + [9].
 The display title has a green background, while the system image is
written to the USB device.
Send the system image file "rw_image.img.zip" and the folder

"B3000 x" (x = number) to Orica service and explain the problem.

10 Errors and Warnings
10.3. Errors and Warnings

The following table lists messages and errors that are possible on the
Blaster 3000 and the Loggers. If an incomprehensible message appears,
then report it to the Orica Technical Service.
Table 22 Possible warnings and error messages

Possible errors Source of problem No.
Abort Blaster aborts the blasting sequence. 1
 If reason unknown, report to Orica Services.
Approx. yy Globals Global detection does not give a definite value. 2
found, => See "Globals found"
Approx. more than yy
Globals found
ARM not confirmed Shortly before firing, the Logger does not confirm the "ARM" 3
command.
 Check the leakage current on the firing cable.
 Retry blasting.
If the error appears again, then report to Orica.
At least one Blaster … <At least one Blaster has fewer detonators than expected> 4-7
<At least one Blaster has fewer Loggers than expected>
<At least one Blaster has more detonators than expected>
<At least one Blaster has more Loggers than expected>
The information on the dongle is different from the data of
the Blaster.
 Check the number of Loggers and detonators.
 Check if it is save to continue in the blasting sequence.
 Abort if you are unsure.
Authentication failure Blaster: Check Wi-Fi configuration. 8
Blaster busy Blaster is busy with the previous command. Blaster will 9
probably abort the sequence.
 Repeat the blasting sequence.
 Check signal quality.
Blasting voltage error Error can appear when the detonators are charged for 10
blasting.
 Confirm the error and check the details.
 Or abort and try again.
 Could be a hardware error if no blasting voltage is
available, contact Orica technical service.
Blue Remote Dongle  Remove dongle. 11
contains an already  Edit the Blaster ID of the corresponding Remote Blaster.
existing Blaster ID  Initialize the Remote Blaster again.
Calibration failed Error can appear when the Blaster calibrates the detonators. 12
 Confirm the error and check the details.
Cannot change Logger You cannot change data of a fired blast in the Logger. 13
Parameters. Blast  Delete the Logger’s memory.
fired.
Cannot create file, Logger cannot create a file on external memory for export. 14
Cannot copy files  Check if you’ve remove the USB key too early.
 Let Windows® repair the file system of the USB flash
drive.
Cannot create folders! Logger cannot create a folder for export. 15
 Let Windows® repair the file system of the USB flash
drive.
 Check if you’ve remove the USB key too early.
Cannot load Det. Internal data is defective. 16
 Report to Orica.

Errors and Warnings 10

Cannot open file Logger cannot open a file. 17
 Import: Let Windows® repair the file system of the USB
flash drive.
 Else report to Orica.
Cannot read det. Logger cannot read detonator data from a file. 18
 See <Cannot open file>.
Cannot read header Logger cannot read the header of a file. 19
 See <Cannot open file>.
Cannot test det! Logger cannot test detonators. Internal communication error. 20
Cannot write blast info Logger cannot write blast information of a detonator list. 21
 Export: Let Windows® repair the file system of the USB
flash drive.
Cannot write CRC Logger cannot write the checksum to verify the data integrity 22
(CRC) of a file.
 See <Cannot write blast info>.
Cannot write det. Logger cannot write detonator data to a file. 23
Cannot write header Logger cannot write the header of a file. 24
Cannot write list Logger cannot write data to a file. 25
header  See <Cannot write blast info>.
Cannot write log Logger cannot write logging parameter. 26
params  See <Cannot write blast info>.
Charging failed Charging detonators failed: 165
 Check leakage on the harness.
 Check connections and damages of the harness wire.
CHECK not confirmed Shortly before firing, the Logger does not confirm the 28
"CHECK" command.
 Check connections to the Logger.
 Reduce electrical noise on the cable.
 Check battery level on the Logger.
 Retry blasting.
If the error appears again, then report to Orica.
Com. Warning, Indication for communication problems. Command cannot be 29
Comm warning decoded during logging or testing detonators.
 Check wiring.
Connection lost Connection to a Blaster is lost. 30
 Check connections, modems, settings, location.
Current too high Logger: Leakage current > 20 mA. 31
 Reduce leakage current.
 Check connections and connectors.
 Ensure proper wire insulation.
Blaster aborts the blasting sequence.
 Check leakage current on firing cable.


Data error Communication is corrupted! 32
 Check for electro-magnetic disturbances.
 Check intermittent connections or wires.
 Check leakage current.
Logger:
 Check if Loggers have the same ID number.
 Check the connection between Logger and Blaster.
Blaster:
 Check sync cable or radio communication.
 Check if Blasters have the same ID.
 Check connection to the Loggers.
 Check resistance of firing cable.
 Check crosstalk between cables of Loggers and Blasters.
Deactivate failed Blaster could not deactivate a Logger. 33
 Check Loggers.
Design logged Logger indicates that all detonators in the SHOTPlus design 34
are logged.
Det check failed Harness check shortly before firing did not detect the first or 35
the last detonator on the harness.
 Check where the first and the last detonators are
connected.
 Check if harness is broken.
 Check if a short circuit on the harness prevents the
communication.
Det not tested Detonator is logged without errors, but not tested in the 153
Logger. When the Logger is switched on, all detonators
receive the state <Det not tested>.
Det on firing cable NEVER connect a detonator directly to the firing cable. 164
Detonator will misfire.
 Connect the detonator to a Logger and log the detonator.
Det programmed Detonator status after the Blaster programmed the delay 155
time.
Det voltage Detonator NOT sufficiently charged during logging. 36
 Check resistance on the harness.
 Check leakage current on the harness.
Duplicate det ID Detonator ID is logged more than once. 37
 In SHOTPlus logging mode, check the SHOTPlus export
data.
 In non-SHOTPlus logging mode, contact Orica Technical
Service.
Exceeding Logger Check the system limits of the Logger II: 38
limits!  <Maximum dets in hole!>, max. 19 detonators per hole.
 <Maximum dets in pattern!>, max. 500 logged detonators.
In SHOTPlus, max. 700 detonators in the pattern.
 <Maximum dets logged!>, max. 500 detonators
Export failed Check the USB connection or connection to PC. 157
Failed to acquire DHCP Blaster cannot find DHCP data: 39
information  Check Wi-Fi settings.
Failed to check Detonator cannot be tested, communication errors. 40
Det!(Comms)  Check cables and connections.
Failed to create gadget Internal error. Logger cannot create the internal folder (RAM 41
disk) to show files.
Failed to detect the Check modem configuration in the Blaster. 42
modem type
Failed to enable Check modem configuration in the Blaster. 43
repeater mode


Failed to enter Check modem configuration in the Blaster. 44
command mode
Failed to enter data Check modem configuration in the Blaster. 45
mode
Failed to erase the Logger cannot delete the current detonator list. 46
memory  Report to Orica.
Failed to get a Blaster cannot read RFI modem settings. 47
parameter  Check modem configuration.
Failed to get the FW- Check modem configuration. 49
Version
Failed to get the Check the configuration of the logging mode. 158
maximum delay
Failed to get the WLAN Check Wi-Fi configuration. 51
FW version
Failed to initiate the Error can appear when you start the blasting sequence [OK] 52
blasting sequence! in the start menu), or when activating Blasters that are in
stand-by mode.
 Retry.
 If the error appears again, then report to Orica service.
Failed to initiate the Error can appear when you test the connection to other 53
test! Blasters.
 Switch off and retry.
 If the error appears again, then report to Orica service.
Failed to join the Check Wi-Fi configuration. 54
wireless network
Failed to load the dets! Logger cannot load the detonator list during delete or replace 55
function.
Failed to load the Check the configuration of the logging mode. 159
logging mode
Failed to load the Check the configuration of the logging mode. 160
logging parameters
Failed to modify the Logger cannot edit the detonator list during retrace. 56
detlist!  Report to Orica.
Failed to open modem Blaster cannot read modem data. 57
interface  Check modem parameter.
 Check if the modem is activated.
 Check connection to modem.
Failed to open serial Check the serial settings of the modem. 154
interface
Failed to open the Wi-Fi module error: 58
WLAN TTY  Check Wi-Fi configuration.
Failed to publish Internal error. Logger cannot create the internal folder (RAM 59
gadget disk) to present the files on PC.
Failed to read CRC. Logger cannot read the checksum to verify the data integrity 60
(CRC) of a file.
 Import: Let Windows® repair the file system of the USB
flash drive.
Failed to read Blaster or Logger cannot read the backup data. 61
Rwimage  Firmware could be defect.
Failed to reset the Logger cannot edit the detonator list during retrace. 62
pattern.  Report to Orica.


Failed to restart Logger cannot get data from the detonator interface. 63
logging!  Report to Orica.
Failed to retrieve Blaster cannot read the dongle data. 64
dongle state  Remove the dongle.
 Try again.
 If the dongle fails again, then use a spare dongle.
Failed to save the Device cannot save the modem configuration. 66
configuration!  Check modem configuration.
Failed to save the det! Logger cannot save the detonator list. 67
Failed to save the Check modem configuration. 68
modem settings
Failed to save the new Logger cannot change the logging mode. 65
logging mode!  Report to Orica.
Failed to send data  Check Wi-Fi configuration. 70
 Check SSID.
Failed to set a Wi-Fi module error: 71
parameter  Check Wi-Fi configuration.
Failed to set error Check modem configuration. 72
correction
Failed to set the Center Check modem configuration. 73
Frequency
Failed to set the Check modem configuration. 74
Channel Spacing
Channel to zero
Failed to set the Check Wi-Fi configuration. 76
passphrase
primary addresses
Failed to set the RX- Check modem configuration. 78
Adressing active
Failed to set the RX- Check modem configuration. 79
Frequency
Failed to set the RX-  Check modem configuration. 80
Threshold  Wrong value selected?
Failed to set the  Check modem configuration. 81
secondary addresses  Check connection to modem.
Failed to set the SSID Check Wi-Fi configuration. 82
Failed to set the TX- Check modem configuration. 83
Adressing active
Failed to set the TX- Check modem configuration. 84
Frequency
Failed to set the TX-  Check modem configuration. 85
Power  Wrong value selected?
Failed to skip the hole. Logger cannot find the position of the next hole. 86
Failed to start logging! Logger aborts when charging the harness wire for logging. 87
 Short circuit on the harness wire.
Failed to store the Logger cannot write the exception information to the 88
exception. detonator list.


Failed to test the det! Logger cannot test the detonator. 89
 Unresponsive detonator interface.
Failed to test the new Logger cannot test the detonator. 90
det!  Unresponsive detonator interface.
Failed to write blue Blaster cannot write to the dongle. 91
Remote Dongle  Remove Dongle, try again.
 If the Dongle fails again, mark it as defect and don't use it.
Faulty Blasters present A Blaster has a self-test error. 92
 Check Blasters.
Faulty detonator Error in the detonator's self-test. The detonator is 93
Faulty det. malfunctioning, detonator is going to misfire:
 Replace detonator.
Firing unconfirmed Remote Blaster did not confirm firing. 99
 Check Blaster to Blaster communication.
 Check Logger connections.
 Retry.
Found fewer Sync Blaster cannot detect all <Sync Slave> Blasters. 94
Slaves  Check connection to <Sync Slave> Blasters.
 Count <Sync Slave> Blasters.
 Try again.
Found more Sync Blaster detected more <Sync Slave> Blasters than expected. 95
Slaves  Count <Sync Slave> Blasters
 Try again.
Fuse error Detonator is defect. Detonator is going to misfire: 96
Fusehead error  Replace detonator.
Globals found Detonator that has responded but is not logged. 97
 Run tests in the Logger.
 Log all unlogged detonators.
Depending on the setting in the Logger, Globals fire on the
global delay time (10 ms after the last detonator).
 Check the setting for Globals in each Logger.
 <Fire Globals>, risk of vibration.
 <Not fire Globals>, risk of misfires in the muck pile!
Group abort Message on Blasters without errors in a Remote group, 163
when another Blaster aborted.
Hardware error x Hardware error detected: 98
(Blaster 3000) Error 1: Error in Logger interface
 Check Logger.
Error 2: Failed to set bridge voltage to 0 V.
 Run Blaster's self-test.
Error 3: Failed to set bridge voltage to 6 V.
 Run Blaster's self-test.
Error 4: Blasting voltage is active when it should not be.
Error 6: KAP communication error:
Harness error The first or the last detonator, or both, are not connected to 161
the harness.
Check the harness and the connections to the harness.
Incompatible Blaster Incompatible firmware versions. 100
 Check all Blasters' firmware.
Incompatible Det ID Detonator has an ID that is not compatible with the system: 101
 Replace detonator.


Incompatible remote Check modem configuration. 102
Blaster interface
Invalid Logger Invalid response from the polled Logger. 103
Wrong Logger type, firmware, or serial number.
 Check that each Logger ID has a unique ID number.
 A loose connection can simulate an invalid response.
Invalid Remote Blaster Check modem configuration. 104
Frequency
Leakage current Blaster: Leakage current > 80 mA while programming 105
Logger: Leakage current > 15 mA while logging
Logger Error x  1: Internal Logger error. 106
 2: Logger responds after programming, but programmed
flag of the Logger is not set.
 3: Unlogged detonators detected, but unlogged detonator
count is 0.
 4: Logger reports that test passed, but errors detected.
Report to Orica.
Logger hardware error, Hardware error in Logger during self-test. 107
Logger HW  Run Logger's self-test.
Logger ID Blaster detects an invalid response from the polled Logger. 108
 Check if Logger ID is used more than once. Assign a
unique ID number to each Logger.
 A loose connection can simulate an invalid response.
Logger initialization Blaster cannot initialize a Logger. 109
failed  Abort.
 Check the connections to the Loggers.
 Check the Loggers.
Logger reset Logger in reset condition. 110
 Check Logger battery.
 Check connections and firing cable.
 Check if there is a short circuit on the harness.
 Retry.
 If nothing helps, then report to Orica service.
Logger version Logger firmware version not compatible with the Blaster's: 111
Logger ver.  Check firmware versions.
 Update Logger or Blaster.
Logger voltage Voltage provided to the Logger is < 20 V and insufficient for 112
blasting:
 Check resistance of wire between Blaster and Logger.
 Check length and diameter of firing cable.
Low battery Logger or Blaster reports a low battery charging level. 113
 Charge device.
 On a Logger, copy the Logger memory into a spare,
charged Logger.
Low voltage, Detonator NOT sufficiently charged to fire at the assigned 27
Cap voltage low delay time. This detonator will NOT fire!
 Check resistance on the harness.
 Check leakage current on the harness.
 Reassign delay time.
 Connect firing cable closer to detonators with long delay
times.
 If nothing helps, then treat this detonator as misfire.
Master dongle inserted Blaster cannot start the blasting sequence when a Master 114
Dongle is inserted.
 Remove Master Dongle.
 Insert Master Dongle when asked to do so.


Master dongle User pulled the Master Dongle. 115
removed
Max. det count You cannot attach more detonators than allowed. 116
exceeded  Logger (I), max. 200 detonators
 Logger (I) in SHOTPlus: No. of dets + exceptions <= 210
 Logger II, max. 500 detonators
Mixed Logger versions Blaster detects Loggers with different firmware versions. 117
 Check firmware on Loggers.
 Update Loggers.
No dets No detonator responds, or no detonator is connected. 120
 Check the connections.
 Check Logger and log detonators.
No firing cable Blaster cannot detect any Logger. 121
Only <Controller> and <Sync Master> are allowed to operate
without any Loggers.
No good det No detonator without errors on a Logger. 122
 Check if harness is broken.
 Check the connections.
No harness First and last detonator on the harness of a specific Logger 123
did not respond.
 Check connection of harness to the Logger.
 Verify that the correct harness is connected to the Logger.
No Link No LAN connection found. 124
 Check network configuration.
No Logger Blaster could not detect a Logger: 125
 Allowed on <Controller>, <Sync Master>, and <Remote>
with synchronized Blasters.
On other Blasters:
 Check Logger type and version.
 Check connections to Loggers.
No radio link <Controller> could not detect any <Remote> Blaster. 126
 Check radio communication.
 Check <Blaster mode>.
No Repeater Blaster cannot find the repeater. 127
No reply (from Remote) <Remote> Blaster does not respond: 128c
 Check the signal strength.
 Is the <Remote> behind a <Repeater>?
 Is the <Repeater> number used by another <Repeater>?
 Is the <Repeater> in repeater mode?
 Check communication with the <Remote> Blaster.
No reply (from Sync <Sync Slave> Blaster does not respond: 128d
Slave)  Check the communication from the appropriate
<Remote> Blaster to the <Controller>.
 Check the sync cable between <Sync Slave> and
<Remote> Blaster.
No reply (from Logger) Blaster cannot detect or understand a Logger's reply 128a
 Check the Loggers.
 Check the Logger IDs.
 Check connection to Blaster.
 Check leakage current on firing cable.
Blasting sequence - detonator reply not detected or
understood:
 Check if it is safe to fire without this detonator.


No reply (from det) Logger cannot detect or understand a detonator's reply: 128b
 Check if the detonator is connected to the harness.
 Check if the harness is broken.
 Check the contact between harness and connector
terminals.
 Check the communication conditions because of leakage
current, resistance, capacitance, EMI.
 If nothing helps, then treat this detonator as misfire.
 Replace detonator if possible.
No Sync Slaves Controlling Blaster could not detect a <Sync Slave> Blaster. 129
 Check sync cable to <Sync Slave>.
 If there are no <Sync Slave> Blasters in the setup, then
choose a Blaster mode without synchronized Blasters.
Not logged Detonator is not logged, only used in SHOTPlus logging 156
mode.
Not programmed The status of the detonator is not correct. 130
 Logger: check cables, connections, output terminals.
 Blaster: This detonator is going to misfire. Abort and retry.
Not ready Uninitialized Logger detected after Logger initialization. 131
 Check the Logger.
 Run Logger's self-test.
Programming failed Blaster cannot program the detonators. 132
 Check connections.
 Retry.
RE error Read error during logging. Possible causes: 133
 Multiple detonators are connected to the harness at the
same time.
 Crosstalk between detonators in adjacent holes.
Solutions:
 Confirm each detonator on the Logger before proceeding
to the next.
 Check legwires for damages and connection from Logger
to harness.
 Check for splice in harness.
 Change polarity of the detonator connection to the
harness.
 Try again to log.
Remote Blaster has  Remove dongle. 134
incompatible error  Edit the settings in the corresponding Remote Blaster.
correction settings  Initialize the Remote Blaster again.
Remote Blaster is in Check network settings. 135
different network
Remote connection  Adjust the positions of the Blasters. 136
check failed  Check the modem settings.
 Perform a radio test.
 Try again.
Reprogramming failed Programming the detonators again is not possible. 137
 Check the wiring.
Selftest error code x Self-test failed: 138
 Refer to chapter "Self-Test".
Short circuit Logger reports a short circuit on the harness wire. 140
 Check and repair harness and legwires.
 Check and repair connectors.
Blaster: Programming error due to a leakage
current > 100 mA at firing voltage.
 Check connections.


Short circuit on firing Leakage current on firing cable is too high. 141
cable  Check and repair firing cable.
 Check and repair connection to Loggers.
Short circuit, high Blasting voltage is not active when it should. 142
voltage not active Report to Orica.
System had to be reset Device parameter had to be reset to factory settings. 143
because of memory  Check the settings.
corruption
Test mode Logger is in "Test mode"; Logger is not switched off: 144
 Switch off the Logger.
 Start blasting sequence again.
Too many dets More than the allowed number of detonators are attached to 145
a blasting device.
 Blaster 3000, max. 3000 detonators
 Blaster 400, max. 400 detonators
Too many errors Too many detonators with errors. 146
 Check how many errors are allowed on the Blaster.
 Check the connections and the wiring.
Unable to read blue Blaster cannot read the Remote Dongle. 147
Remote Dongle  Remove dongle.
 Try again.
 If the dongle fails again, then abort and mark the dongle
as defect.
 Initialize the corresponding Remote Blaster again with a
spare dongle.
Undefined error Logger cannot decode a status. 148
 Inform Orica service.
Unexpected Blaster Sequence error occured. 149
state  Retry blasting sequence.
Unexpected error Contact Orica Technical Service. 150
Unknown number of Global detection does not give a definite value. 119
Globals found => See "Globals found"
Update failed Logger update failed. The Logger will stay on. 139
 Press the reset button.
 Restart the Logger and try updating again.
 If the update fails again, contact Orica Technical Service.
Upload incomplete Blaster report could not be transferred completely to the 151
WLAN FW upgrade Check Wi-Fi configuration. 152
required
Numbers on the right side refer to the original list in English.

(obsolete messages removed: 48, 50, 69, 118, 162)

10 Troubleshooting Summary
10.4. Troubleshooting Summary

The following guide gives information when you have problems with an
i-kon™ device.
10.4.1. Issues while Blasting
When you need to abort:

 Remove the Master Dongle.
 Disconnect the firing cable.
 <Remote> and <Sync Slave> Blasters return to standby mode,
safe mode with no power to the firing cable.
 Allow 3 minutes power down time before reprogramming.
 Allow 5 minutes before re-entering the blast site.
Table 23 Possible issues

§ Problem Correction
1. No response from Logger after initialization by Blaster
a) Poor connection or break in firing cable.  Abort and disconnect firing cable.
 Repair connections to Loggers.
b) Incompatible or same Logger IDs Check Logger IDs and edit.
c) Loggers cannot be initialized if in test  Switch off the Loggers.
mode.
2. Remote: Poor signal strength
Various  Check antenna, clean connections.
 Check for interference caused by other
transmitters nearby.
 Ensure line of sight.
 Check no obstacles within 8 m around
the direct path between antennas.
 Check that distance is not too great.
 Check arrangement of Blaster units.
 Raise the Blaster higher off the ground.
 Use a Repeater.
3. Errors while programming detonators
a) Voltage  Abort and disconnect firing cable.
b) Leakage  Verify that limits of harness wire and
firing cables are complied with.
c) Short Circuit
 Find and fix reason for leakage current.
4. Detonator errors
If there are too many detonator errors,  Check detonator details.
they all might misfire.  Abort and disconnect firing cable.
 Troubleshoot at the blast site.
5. <No harness> error – Blaster aborts
a) Check of first and last detonator on  Abort and disconnect firing cable.
harness failed.  Check first and last detonator on each
b) Break in harness or harness extension Logger.
 Check all wires for breaks.

Troubleshooting Summary 10
10.4.2. Detonator Errors

If detonator errors occur during programming, the Blaster automatically
addresses the faulty or not responding detonators and tries to re-program
them.
Table 24 Possible detonator errors
Error Reason Corrective measures
Low voltage, Voltage drop on the harness wire is  Abort the blast.
Cap voltage low too high. The detonator capacitor is  Check the leakage current.
not charged enough to fire.  Check delay time of the detonator.
 Detonator will probably not fire.  Check where the detonator is located and
where the connection to the Logger is.
Data Error Communication is interrupted.  Abort the blast.
 Detonator will probably not fire.  Retry programming.
Faulty det Detonator is malfunctioning.  Detonator will not fire.
Fusehead error  Replace detonator.
No reply Detonator does not reply. Detonator will probably not fire.
 Broken legwire  Review the detonator position on plan.
 Poor connection  Abort blast and fix.
 Broken Harness wire
Not programmed, Detonator has not received all  Abort the blast.
Programming failed programming information.  Review the detonator position on plan.
 Retry programming.
Check if it is safe to fire the detonators with errors, or abort and replace
the faulty detonators.
10.4.3. Restart the Blasting Sequence
To re-start the blasting sequence:

 Re-connect firing cables.
 If <Remote> and <Sync Slave> Blasters are not in standby mode,
you need to prepare them again.
 Start the blasting sequence on the Controller.

10 Guidelines on Handling Misfires
10.5. Guidelines on Handling Misfires

DANGER
A misfired or damaged detonator might initiate unexpectedly!
 ALWAYS assume that a misfired detonator and that is still in the
ground is damaged.
 NEVER use a metal detector to locate a misfired detonator.
 NEVER remove a booster from a damaged detonator.
 NEVER subject a detonator to sharp mechanical shock or impact.
 NEVER crush or bend a detonator.
 ALWAYS keep cell phones and radios at least 5 m (17 ft) away.
 ALWAYS wear eye and ear protection.
 ALWAYS wear leather gloves.
 ALWAYS dispose of a detonator whose shell is deformed, broken,
pierced, shrink-wrapped or significantly corroded.
 ALWAYS point the detonator away from people.
 ALWAYS hold the detonator by the wires or the crimped end of the
shell.
 ALWAYS twist the detonator's bare wire endings together.
 Contact the Orica Technical Service for further instructions.
Treat a misfired detonator with appropriate caution.

 Ask the Orica Technical Service for recommendations on product
destruction, or advice that is specific to the situation.
 Verify that no other person is present when you are handling a
misfired detonator.
 Take measures to reduce the risk of an electrostatic discharge
before you touch the legwires of a detonator.
Handling visually undamaged misfires:

Even if the misfired detonator shows no visible signs on the shell, the
internal safety structures can be damaged.
 If safety structures inside the electronic detonator are damaged,
detonators are more vulnerable to static electricity and electro-
magnetic effects (radio signals).
 If explosives are dislodged, the sensitivity to mechanical shock,
impact, and electrostatic discharge (ESD) is increased. In the worst
case, an electric discharge between the operator and the legwires of
a detonator could initiate the damaged detonator.
 If explosives are exposed, they can initiate by a spark or friction.
If you think the case is important and should be investigated, then

contact the Orica Technical Service before you send the misfired
detonators to Orica.

Handling and Disposal
Storage 11
11. Handling and Disposal

11.1. Storage
The blasting equipment is splash water protected, but not waterproof.
Store the blasting equipment in a dry environment and at moderate

temperatures.
11.2. Maintenance
WARNING
Unauthorized modifications lead to equipment malfunction, to misfires,
or to unintended detonation!
 NEVER deactivate safety functions or remove safety precautions.
 NEVER use defective equipment.
 NEVER unscrew the casing of Orica devices.
 NEVER retrofit, extend or modify Orica devices.
The device requires only basic maintenance as routine inspections and

cleaning.
11.2.1. Cleaning and Checking for Damage
WARNING
If the blasting equipment is damaged, detonators can misfire!
Death or severe injuries because of misfires in the muck pile
 Verify that all devices are free of damage.
 Verify that no parts are loose or missing.
 Verify that output terminals are fixed.
Clean the blasting equipment after each blast.

 Brush off the dirt.
 Clean with a damp, soft cloth.
 Do not spill liquids on the device.
 Do not put fully into water.
Make a visual control after each blast:

 Check that the blasting equipment is free of damage.
 Verify that no parts are loose or missing.
Send defective devices to Orica for maintenance.

11 Maintenance
11.2.2. Charging the Device

NOTICE
If the batteries of a Logger or Blaster are NOT sufficiently charged, the
Blaster will abort the blasting sequence!
 Operate the blasting equipment only with a fully charged battery.
 Use only the supplied charger.
This electronic device contains lithium-ion batteries.
Guidelines to extend the battery life

 Charging:
- Charging is faster when the device is switched off.
- Fully charge the battery after each use.
- Device can be stored, connected to the charger.
- Battery should stay cool (< 40°C, 104 °F).
- Don’t charge below 0°C (32°F).
 Discharge:
- Avoid deep discharges (< 20% state of charge).
- For blasting you need at least 30 % state of charge.
- If storage temperature exceeds 25 °C over 6 months, then
recharge the battery periodically.
 Usage:
- Avoid heat > 60°C (> 151°F).
- Avoid direct sunlight.
- Use heat-insulating packaging when using the device at very low
temperatures.

Maintenance 11
11.2.3. Inspection Service

WARNING
If the blasting equipment is faulty, detonators can misfire or fire out of
sequence!
Death or severe injuries because of misfires in the muck pile
 NEVER use blasting equipment with out-of-date firmware or expired
inspection tag.
 NEVER taper with the inspection tag.
 Have the blasting equipment serviced regularly.
To ensure that the blasting equipment operates properly, we recommend

inspection every 3 years by an Orica Service or an Orica authorized
service provider.
If local regulations specify a shorter interval, then have the blasting
equipment checked earlier.
Figure 191 Inspection tag
① Tester's signature
② Month and year of the next inspection
11.2.4. Updates and Upgrades

Arrange with Orica service personnel to check if it is possible to update
the firmware during the inspection.

11 Transport Regulations
11.3. Transport Regulations

The Lithium-ion batteries used in Orica’s EBS devices have less than
100 Wh and are tested to UN 38.3.
 When the consignment contains only 1 or 2 devices, no labelling
and no dangerous goods paperwork is required (UN3481); this
also applies to air freight.
If you need to ship more than 2 devices, then find a carrier who is trained
and able to carry class 9 dangerous goods.
11.4. Disposal
This electronic device contains lithium-ion batteries.
Dispose of or recycle all devices and their batteries according to the

legal requirements.

Information
Expressions and Abbreviations 12
12. Information
12.1. Expressions and Abbreviations
Table 25 Glossary
Expression Description No
abort Deliberate termination of the blasting sequence (charging or firing). 1
arm, arming Energizing the capacitor of an electronic detonator to the firing voltage. 2
blast pattern Diagram of the drilled holes as laid out for blasting. 3
blast plan List of all technical details including drilling and loading. 4
charging site Area where boreholes are located and explosive materials are handled 5
blast site during loading of the shot. The area includes at least 15 meters (50 ft) in
all directions.
The area can be larger in local regulations.
blasting area Area that can be affected by flyrock, dust, or fumes from an explosion 6
that can cause personal injuries, damages to property.
blasting Steps that lead to the "FIRE" command: 7
sequence,  initialize – charge and program – fire
firing
sequence
borehole Hole drilled in material to place explosives. 8
burning Location where misfires can be destroyed. 9
ground
connector Enables an electrical connection between the harness wire and the 10
legwires of a detonator.
deck Layer of detonators within a borehole, separated by stemming. 11
delay time, Lapse of time between the application of a firing signal and the 12
delay detonation of a delay detonator.
detonator Short for "electronic detonator": 13
det, dets Electronic device containing micro-chip and detonating charge, used to
initiate an explosive.
detonator ID Detonator's unique identification number stored in the chip and printed 14
on the label.
detonator Electric circuit containing electronic detonators and associated wiring. 15
network,
firing circuit
EMI Electromagnetic Interference 16
harness Double wired cable, or bus line where detonators are connected on in 17
parallel.
IP code International Protection Marking,or Ingress Protection Rating, classifies 18
the protection a housing against the intrusion of solid objects and water.
Examples:
 IP 54: "5" = dust protected, "4" = splash-proof
 IP 67: "6" = dust tight, "7" = protected against temporary flooding
leakage Undesirable flow of current from the detonator network into the ground. 19
current
legwires Pair of insulated wires attached to a detonator on one side and to a 20
connector on the other side.
loading Process of placing an explosive charge into a borehole. 21
LTE Modem type to communicate via mobile phone network 38
misfire Explosive charge or detonator that fails to detonate after an attempt of 22
initiation.
muck pile Pile of broken burden resulting from a blast. 23
out of Detonator initiated at a wrong delay time, after the shotfirer gave the 24
sequence FIRE command.
firing
pattern Drawing or list with the positions of boreholes; same as blast pattern. 25

Information
12 Expressions and Abbreviations
Expression Description No
primer Unit, package, or cartridge of explosives used to initiate other 26
explosives or blasting agents, and which contains detonator and
booster.
shotfirer Holder of a licence to use explosives to break or dislodge rock and soil, 27
or to demolish structures.
shotfirer-in- Qualified person who is in charge of and responsible for the design, 28
charge, loading and firing of a blast.
blaster-in-
charge
sleep mode In the passive mode (sleep mode), the device consumes very little 29
passive mode battery power. The device has to be activated by a special command.
sleep time Time between explosives being loaded into a borehole and their 30
initiation.
standby In standby mode, the device is ready to receive signals. 31
mode,
standby time
stemming Inert material filled between the explosive charge and the collar of the 32
borehole to confine the explosion gases.
stray current, Flow of electricity through equipment, buildings or the ground. Reason 33
stray voltage might be imbalances in electrical supply systems or because of wiring
damage.
Stray current results from an electrical potential between objects that
should not have a voltage difference.
sympathetic Detonation of explosive material as the result of receiving an impulse 34
detonation from another detonation through air, earth or water.
uncommande Detonator initiated before the shotfirer gave the FIRE command. 35
d firing
unintended Detonator initiated unintendedly because of friction, heat, impact, shock, 36
initiation electrostatic discharge or other sources. Or the detonator was NOT
specified for the firing device.
WLAN / Wi-Fi Both expressions are used for the wireless area network 37
Table 26 Terms used with the i-kon™ Blaster3000

Expression Description
Blaster Firing device used to initiate electronic detonators

C A CH F Fire commands:
"C A": Check – Arm
"CH": Check Harness
"F": Fire
Firing cable Wire connecting firing device and Loggers
Leaky Feeder Radio communication system for underground mines using coaxial
cables, which emit and receive radio waves through gaps in the outer
conductor.
Logger Logging and testing device for electronic detonators
Master dongle The red marked dongle is needed to control the blasting sequence and to
fire the blast.
Remote dongle A blue marked data key (dongle) records the access details of a
<Remote> Blaster.
 You cannot fire a blast with a remote dongle.
Remote group A remote group constist of a <Remote> Blaster and connected <Sync
Slave> Blasters.
Globals, unlogged Detonators that are connected to the harness, but are not recorded in a
detonators Logger. Unlogged detonators usually fire 10 ms after the last detonator.

Information
Technical Data 12
12.2. Technical Data

Table 27 Blaster 3000 technical data
Maximum detonators 3000
Maximum Loggers 12
Weight 4.8 kg / 10.5 lb
Dimensions ~ 30 cm x 34 cm x 15 cm
Display Colored
Keypad Numbers, navigation, 3 function keys
Sealing Closed: IP65
Open: IP54
Interfaces  Serial
 LAN (Ethernet, chipset Davicom DM9000)
 Wi-Fi (internal antenna 3dB gain, UDP
protocol), microchip RN171
 VLAN (Virtuel LAN), port 12205
Modem types  Satel radio
 VHF
 Leaky Feeder RFI
 Analog phone
Battery Lithium-Ion, weight 506 g (1.12 lbs.)

Information
12 Units
12.3. Units
Table 28 Units
Unit Description
mA milli Ampères
µA micro Ampères
V Volts
ms milli seconds
mW milli Watts
Ω Ohms, unit of electric resistance
12.4. Orica Service Offices

To find your local Orica Service office, ask your Orica representative, or
visit the site http://www.orica.com.
Table 29 Orica Service Offices (Examples)
Region Address Contact
Europe Orica Europe Pty Ltd & Co KG Tel. +49 2241 9952 0
Middle East Mülheimer Straße 5 Fax +49 2241 9952 3235
Africa 53840 Troisdorf
Germany
North Orica USA Inc. Phone +1 303 268 5000
America 33101 East Quincy Avenue Fax +1 303 268 5250
Watkins
Colorado 80137
Asia Orica Limited Phone 1300 555 175 (Australia)
Pacific 1 Nicholson Street Phone +61 3 9665 7111
East Melburn (International)
Victoria 3002 Fax +61 3 9665 7937
Australia e-mail: companyinfo@orica.com
Latin Orica Mining Services Tel. +56 2 2715 3800
America Costanera Sur 2730 Fax +56 2 2715 3927
Las Condes, Santiago
Chile
Device to i nitiate el ectronic D etonators in s urfac e and underground mini ng

Modes: Si ngle – R emote – Sync hronized
Article N o:
Firmware:
Instr ucti ons for Us e - for Shotfirers
Contents
Index

Information
Index 12
12.5. Index
Detonators
A Allowed ...................................... 40
More, fewer .............................. 186
Abort Disposal........................................ 202
Globals found ............................ 95 Detonator ................................. 198
Abort blasting ................................. 80 Dongle ............................................ 36
About the Blaster............................ 46
Adapter
Power plug ................................. 39 E
Alias ............................................... 47 Enable Satel modem ...................... 56
Analog modem ............................... 58 Error
Analog phone ................................. 29 List ........................................... 186
Antenna.......................................... 37 Programming ..................... 97, 197
Antenna alignment ....................... 129 Programming report ................... 94
Automatic mode ........................... 165 Self-test .................................... 184
Errors
B Limit ........................................... 53
Backup ......................................... 185

Batteries Li-Ion ............................. 202 F
Battery............................................ 44 Factory settings ........................ 49, 63
Charge ....................................... 39 Fewer
Disposal ........................... 200, 202 Dets/Loggers ............................ 186
Level ............................ 44, 45, 184 FIRE ....................... 89, 126, 174, 183
Blast report................................... 108 Firing cable ..................................... 79
Blast sites Firmware .................................. 45, 46
Dependent ................................. 73 Update ....................................... 69
Blaster Version in report ....................... 110
Name ......................................... 47 Front panel ..................................... 38
Blaster details ................................ 91 Function keys ................................. 38
Blaster ID ....................................... 51
Sync Slave ................................. 51
Blaster info ..................................... 45 G
Blaster mode .................................. 52 Globals
Blaster overview ............................. 90 In Logger .................................... 72
Blasting in Overview ................................ 95
Analog phone .......................... 176 Info ............................................. 54
Sequence .................................. 77 Report ...................................... 110
System....................................... 20 Setting ........................................ 54
Blasting mode .............................. 165
I
C
ID Blaster........................................ 51
Central firing unit ............................ 29 Identification plate .......................... 23
Charger .......................................... 39 Improper use .................................. 14
Charging ........................................ 39 Info Blaster ..................................... 45
Cleaning ....................................... 199 Information ..................................... 46
Communication Inspection ..................................... 201
Test.......................................... 127 Install
Concurrent mode ......................... 165 Language ................................... 66
Connectivity ................................. 136 Intended use................................... 13
Interface
D Setup.......................................... 55
Date ............................................... 64
Deactivate K
Logger ....................................... 92 Keep-alive counter (KAP) ......... 16, 46
Dependent blast sites..................... 73 Keyboard ........................................ 47
Deselect Blaster ........................... 172 Keys for operation .......................... 38
Det not logged .............................. 194
Detonator
Misfire ...................................... 198
Properties .................................. 24

Information
12 Index
L Log in ......................................... 48
Pressure compensation .................. 37
LAN Problems ...................................... 196
Settings...................................... 60 Programming error report ............... 97
Test.......................................... 148 Programming report........................ 94
Language ....................................... 65 Properties ....................................... 23
Leakage current ................... 169, 180
Leaky Feeder
2 modems .................................. 31
R
3 modems .................................. 30 RE error ........................................ 194
Modem ....................................... 57 Re-enter blast area ....................... 106
Traceroute ............................... 147 Remote blasting ................... 164, 177
Limit Remote Dongle .............................. 36
Errors ......................................... 53 Remote group ................................. 28
Limits.............................................. 22 Remove Blaster ............................ 172
Logger Repeater....................................... 137
Exclude ...................................... 92 Repeater mode ............................... 52
Report ........................................ 91 Report................................... 108, 110
Requirements ............................ 46 Save ......................................... 109
Loggers Retry counter ................................ 170
Count numbers .......................... 82 RSSI Trip ...................................... 146
More, fewer .............................. 186
Low voltage .................................. 192
S
M Safety concept ................................ 15
Safety key....................................... 36
Maintenance ................................ 199 Safety message .............................. 11
Manual mode ............................... 165 Safety regulations ........................... 13
Master Dongle ................................ 36 Self-test .......................................... 40
Menu Error ......................................... 184
Blaster settings .......................... 50 Failed ....................................... 184
Interface..................................... 55 Serial modem ................................. 55
System....................................... 63 Serial number ......................... 46, 110
Menu structure ............................... 44 Service offices .............................. 206
Misfire .......................................... 198 Setup
Mixed Logger type.......................... 76 LF Modem .................................. 57
Modem Password ............................. 48, 68
Analog ....................................... 58 Satel Modem .............................. 56
Leaky Feeder ............................. 57 SHOTPlus ...................................... 20
LTE ............................................ 59 Shut down
Setup Satel ................................ 56 Remote Blaster ................ 105, 128
Test.......................... 131, 141, 151 Signal strength ............................. 146
More Sleep mode .................................. 118
Dets/Loggers ........................... 186 Standby
Check ......................................... 41
N Sync ......................................... 118
Storage ......................................... 199
N/A ................................................. 95 Switch off ........................................ 42
Noise ............................................ 146 Switch on ........................................ 40
Not programmed .......................... 194 Sync
Cable........................................ 113
O Cable test ................................. 112
Interface ..................................... 62
Operating language........................ 65 Output terminal .......................... 35
Output terminal .............................. 35 Sync Slaves
Overview Less/more ................................ 121
Stage 1 ...................................... 90 System image ............................... 185
Stage 2 ...................................... 94 System test............................... 74, 75
With errors ................................. 97
Owner ............................................ 10
T
P Target group ................................... 10
Terminals........................................ 35
Password Termination resistor ........ 62, 112, 114
Edit ............................................ 68 Test

Information
Index 12
Communication ........................ 127 User ................................................ 10

LAN or Wi-Fi ............................ 148
LF communication ................... 145 V
Loggers................................ 74, 75
Modem ..................... 131, 141, 151 Version ........................................... 45
Time ......................................... 44, 64 Vibration ................................. 50, 109
Traceroute.................................... 147 Voltage low ................................... 192
Training .......................................... 16
Transport...................................... 202
Troubleshooting ........................... 196
W
Sync......................................... 112 Wi-Fi
Settings ...................................... 61
U Test .......................................... 148
WLAN ................................. See Wi-Fi
Update ........................................... 69
Language................................... 66

i-konIII Blaster3000 MAN F1-18-03 D02-06en 20200113

Uploaded by

Copyright:

Available Formats

You might also like

i-konIII Blaster3000 MAN F1-18-03 D02-06en 20200113

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

i-konIII Blaster3000 MAN F1-18-03 D02-06en 20200113

Uploaded by

Copyright:

Available Formats

i-kon™ Blaster 3000

DEVICE TO INITIATE ELECTRONIC DETONATORS IN SURFACE

Instructions for Use - for Shotfirers

Article No: XBl3000

Orica Sweden AB Technical Documentation:

1. For your Safety 9

i-kon™III / i-kon™ Blaster 3000 F 1-18-03 D02-06en 3

2.5.3. Configuration with LAN 32

4 F 1-18-03 D02-06en i-kon™III / i-kon™ Blaster 3000

b) Install, Update or Remove an Operating Language 66

i-kon™III / i-kon™ Blaster 3000 F 1-18-03 D02-06en 5

6.3. Re-Entering the Blasting Area ...............................................106

6 F 1-18-03 D02-06en i-kon™III / i-kon™ Blaster 3000

8.4.1. Check the Signal Strength 148

i-kon™III / i-kon™ Blaster 3000 F 1-18-03 D02-06en 7

10.4.1. Issues while Blasting 196

8 F 1-18-03 D02-06en i-kon™III / i-kon™ Blaster 3000

1. For your Safety

The use is restricted to users that have the necessary qualification.

Non-observance of these instructions, the training and the safety

1.1.1. Evolution of i-kon™

1.1.2. Additional Documentation

i-kon™III / i-kon™ Blaster 3000 F 1-18-03 D02-06en 9

1.2. Target Group

1.2.2. Duty to perform Maintenance and Service

For instructions on maintenance, see chapter Maintenance, page 199.

1.2.3. Duty to report Faults and Damages

10 F 1-18-03 D02-06en i-kon™III / i-kon™ Blaster 3000

1.3. About this Manual

1.3.1. Structure and Meaning of Safety Messages

① Signal word (here DANGER) ④ Possible consequences

Safety messages have three hazard levels depending on the degree of

WARNING WARNING indicates a potentially hazardous situation that if not

CAUTION CAUTION indicates a potentially hazardous situation that if not

Table 2 Safety symbols

Explosion Hazard Laser Beam

1.3.2. Safety Instructions

i-kon™III / i-kon™ Blaster 3000 F 1-18-03 D02-06en 11

1.3.3. Notations used in the Manual

A mandatory notice contains information that must be observed.

Recommended procedures give instructions of best practice that

A general notice is a piece of information to improve understanding,

1.3.4. Step by Step Instructions

3. Take the final step.

Short Instructions can have a quick start guide:

Alternative procedures or application rules are listed in a table.

12 F 1-18-03 D02-06en i-kon™III / i-kon™ Blaster 3000

1.4. Intended Use

1.5. Non-observance of Safety Regulations

Non-observance can result in death or severe injuries.

i-kon™III / i-kon™ Blaster 3000 F 1-18-03 D02-06en 13

1.6. Improper Use

Wrong handling of detonators can result in death or severe

A detonator can initiate unintendedly when it is connected to

14 F 1-18-03 D02-06en i-kon™III / i-kon™ Blaster 3000

1.7. Product Safety

1.7.2. Safety Concept

Only when the blasting area is evacuated, then Blasters may be