DRB & DBD User manual Page 1 / 168
System DaveyTronic® SP/UG - DaveyTronic Swift® Language ENG Pack 64 Date 05/2022 Revision 1 Equipment User Interface Driver RTOS DRB2 DBD 02.02.04 02.02.00 02.00.16 03.00.16 1.60 Page 2 / 168 02.00.16 03.00.16 1.
Contents SYSTEM OVERVIEW ........................................................................................................ 7 DAVEYTRONIC® SP/UG SYSTEM .................................................................................................................. 7 SAFETY ........................................................................................................................................................... 8 Radio interference .....................................................
FIRING IN WIRELESS MODE ......................................................................................... 51 GENERAL INFORMATION................................................................................................................................. 51 Presentation of the DBD .......................................................................................................................... 54 Communication quality .......................................................................
WIRED MODE ............................................................................................................................................. 146 History file .............................................................................................................................................. 146 Datalogger files ..................................................................................................................................... 148 WIRELESS MODE ..........................
GLOSSARY OF TERMS DT – DaveyTronic® DTSP – DaveyTronic® Super Pit DTUG – DaveyTronic® Underground DRB2 – DaveyTronic® Remote Blaster 2 DBD – DaveyTronic® Blast Driver PU – Programming Unit DEDD – DaveyTronic® Electronic Delay Detonator RFID – Radio Frequency Identification UTM – Unversal Transverse Mercator GNSS – Glabal Navigation Satelite System Page 6 / 168
System overview DAVEYTRONIC® SP/UG system The Daveytronic® SP/UG system is a digital blasting system where one sets comprises of the following devices and accessories: DaveyTronic® SP system • • • • • • DaveyTronic® UG system with Swift One or more Programming Units (PU – SP/UG/Swift) One Daveytronic® Remote Blaster (DRB2 – SP/UG) One or more Daveytronic® Blast Drivers (DBD – SP/UG) Bus lines Wire connectors Daveytronic® electronic detonators Note: All information depicted in this manual applies to the
This mode of communication between the detonators and the equipment: • • • • • Allows programming of a delay for each detonator. Ensures testability at the shot and from the firing location. Controls the energy for each detonator up to firing time. Reports any anomaly to the operator. Prevents firing unless using the dedicated DRB2. This technology allows for optimal control of the firing sequence precision.
Lightning Even though the DEDDs has high resistance to initiation from extraneous currents, all types of explosives and detonators are susceptible to detonate when hit by lightning. Follow all applicable regional and mine specific laws and regulations regarding the approach and progress of electrical storms.
How to use the Firing caps While operating with DBD and DRB firing caps are available for use if required. NEVER touch the exposed wires of the firing line while connected to a DRB during firing The use of firing caps is shown in the following pictures: General precautions WARNING: ALWAYS use approved devices and hardware when using DEDDs. NEVER connect DEDDs to any energy supply other than the DRB2, DBD or PU: batteries and 110/220V circuits are strictly FORBIDDEN.
Implementation modes The DT SP/UG system comprises of 3 different devices: the PU, the DRB2 and the DBD. The combination of the 3 different devices allows the system to be used in various configurations suitable for various different operational needs. Demonstration / Training mode Demonstration mode is for use during training and is indicated in the system History files as such.
Once activated, when the DRB2 is switched ON, the following message is displayed and it is possible to disable the demonstration mode immediately by pressing the √ button. WIRED Mode Operating the DT SP/UG blasting system in WIRED mode requires the use of 1 up to 6 PUs, and a DRB2. The DEDDs are programmed using the PUs. The firing circuit is connected directly to the DRB2 firing terminals.
WIRELESS mode The DT SP/UG system can also be operated in WIRELESS mode. The WIRELESS configuration requires a DRB2, 1 DBD in Monoblast, up to 8 DBDs in Multibast, 3 DBD in Synchroblast and up to a maximum of 6 PUs per DBD. The DBDs are connected to the firing circuits and are placed close to the shot, in an area protected from fly rock. The DRB2 is used from the firing location in a safe area for the operator.
Monoblast / Multiblast / Synchroblast® The blast can be operated in three different ways, Monoblast Multiblast and Synchroblast®. Monoblast is used to operate a single DBD connected to a single or multiple shots in WIRELESS mode. Multiblast is used to operate multiple DBDs connected to multiple shots in WIRELESS mode. WARNING: The operation of the DRB2 and DBD must only be performed when safe and authorized to do so and when the mine has been evacuated.
Firing in WIRED mode Presentation of the Remote Blaster (DRB2) In WIRED mode, the DRB2 manages its network, carries out checks of the functionality of each detonator on the firing circuit and then transmits the secure commands to fire each detonator. The DRB2 can manage a maximum of 1500 Daveytronic detonators on its network (contact your local Enaex representative for more information). WARNING: The DRB2 provides the menu driven instructions and the energy necessary to fire the detonators.
A RS232 serial port J Screen 5”7 ¼ VGA S Dustproof plate B ON/OFF button K MODE button T Ethernet port C Antenna RP-TNC connector (only SP) L Arrow button down U Charger socket D CHARGE button M Arrow button up V Antenna E Arrow buttons N FIRE button W RFID card F ENTER button O Earthing connection X RFID reader G LIST button P Firing line connection terminals Y Label H Backlight button Q Speaker Z Charger I CANCEL button R USB port Page 16 / 168
Buttons The DRB2 operating controls include 14 buttons described below: DaveyTronic® SP DAVEYTRONIC ON/OFF button : - Switch ON (hold for 1 sec) - Switch OFF (hold for 1 sec) √ ENTER button: - Choose selected menu - Confirm X CANCEL button: - Exit to previous menu - Cancel previous selection LIST button: - List all programmed delays BACKLIGHT button: - Switch on the screen and buttons backlight MODE button: - Switch from configuration to operational mode and vice versa CHARGE button: - Must be held t
RFID Card The RFID card is the security tag of the system. Without an RFID card, the DRB2 cannot enter into operational mode and consequently cannot manage blasts. The DRB2 is able to manage 2 different RFID cards: • • First one for Testing (should always remain in the shot firer's possession) Second one for Firing (should always remain in the blast controller's possession) The RFID cards can only be associated to a DBR2 by means of the specific DRB2 Administrator menu.
A few seconds after the self-test is successfully completed, a short beep is generated. The following screen then appears displaying the MAIN menu NETWORK gives the users access to Read PUs, recover PU data with Copy PU to PU, performing a Wireless test and if activated Read exclusion zone and setting the Time windows GENERAL SETTINGS give the users access to the Language, Display, DRB2 Modem, Time Date, DBD modem and the About page.
NETWORK menu in SP On the MAIN menu, when the DRB2 is first switched on, the icon is displayed on the top right of the screen and means that no data has been transferred yet. Press √ to confirm the selection of NETWORK.
NETWORK menu in UG In UG the SWIFT BLAST SETTINGS are added to the NETWORK menu. • Swift blast settings allows to set the face offset and face offset delay settings. SWIFT BLAST SETTINGS menu in UG In UG the SWIFT BLAST SETTINGS which contains the FACE OFFSET and FACE OFFSET DELAY are added to the NETWORK menu. The face offset is a simple delay parameter that the user can add to avoid having too many dets firing at the same time when blasting several headings.
The following example displays the firing of 3 faces ranked in a define order with a face offset of 1 025 ms. By adding this delay, the total blast duration is 10 050 ms. Face offset This setting allows to turn ON or OFF the face offset using the / of the DRB2. Face offset delay This setting allows to set the face offset delay from 1 to 1500 ms. Use the / of the DRB2 to switch between numbers and use / on the left hand side of the device to change each number.
GENERAL SETTINGS menu On the MAIN menu, use / on the left hand side of the DRB2 to select GENERAL SETTINGS and press √ to confirm. Six menus are then available: Language, Display, Modem, Time – date, DBD modem and About. Language Select the appropriate language with / on the left hand side of the DRB2 and confirm with Use X to exit to the GENERAL SETTINGS without changing the language. Page 23 / 168 √ .
Display The display properties can be configured as indicated in the screen below. Increase/Decrease the backlight level by using the left / of the DRB2. Change the selection between LCD backlight and Keyboard backlight using the / of the DRB2. Select ON/OFF using the left / of the DRB2. Confirm new parameters with √ or use X to exit to the GENERAL SETTINGS without taking the modification into account.
Time – date As indicated in the screen below, the user can modify the time and date. The highlighted parameter can be changed using the left / of the DRB2. To change the selected parameter value, use the left / of the DRB2. Press √ or X to return to the MAIN operating screen WARNING: If the Time windows feature is activated, the date / time of the DRB2 can only be changed after tagging the “Time Window” RFID card.
About This screen display technical details of the DRB2 incl. battery capacity. HISTORY menu On the MAIN menu, use the left / of the DRB2 to select HISTORY FILE, press The screen below is then displayed giving users access to 3 menus: √ to confirm.
A USB key has to be connected to the DRB2’s USB port to proceed to download of the history or datalogger files.
History and Datalogger File Transfer". Note: Plug in the charger during the data transfer, as it will avoid a complete battery discharge.
Special procedure This additional setting allows to set a maximum amount of extra or missing detonators that can be fired with a Special Procedure. The default value is 0 for both errors.
PU to DRB2 data transfer The PU contains all the programming data (network name, associated DRB2 / DBD, detonator’s unique ID number, sequence number and delay) in its RFID tag. After programming and circuit testing with the PU is finished, and before starting the firing procedure, the stored data must be transferred from the PU to the DRB2. The blasting plan data transfer is done through RF communication between the RFID tags of the PU and the DRB2.
Press √ to continue and tag another PU or press X to exit and to return to the NETWORK menu. Note: Up to 6 PUs can be downloaded to the DRB2 per associated equipment, if the operator tags a 7th PU, the screen below is displayed. It will prompt the user to select a PU to be replaced to allow for the download of the current tagged PU. Select the desire PU with / and press √ to validate replacement or press X to cancel replacement.
Note: If the message "PU NOT COMPATIBLE" is displayed, it means that the tagged PU is not compatible with the SP/UG system software. Note: If message "No data to transfer!" is displayed, it means that the blast plan of the tagged PU is empty. Note: If message "TAG CORRUPTED OR NOT COMPATIBLE" is displayed, contact your Enaex representative. Firing window The firing assists with additional safety, where it is possible to only allow the firing procedure to be conducted during only predetermined time windows.
Note: All the equipment must be configured with this feature (DRB2 and DBDs).
Use the / buttons to select the field to modify and press The configuration is saved with √ . Use the X / to change the value of the field. button to abort the configuration change. The starting times is adjusted in increments of 15 minutes.. As charging and firing has been disabled, network testing is safe and the procedure can begin before the time window opens. But once testing is complete, charging (and then firing) is not allowed until the Time Window allows.
Testing the equipment network If the user wants to initiate the test procedure outside the time window and set Network testing anticipation, the following error is displayed Initiate a firing procedure out of the Firing windows If the shotfirer wants to initiate the firing procedure outside of the set time windows, the following error is displayed Page 35 / 168
Firing Procedure After all tests have been completed with the PU(s), the blast plan data has to be transferred from the PU(s) to the DRB2. Once the site is secured, the firing lines can be connected to the DRB2. The DRB2 executes the firing procedure and associated tests. The progress of the procedure and the results of the tests are displayed on the DRB2’s screen. Once authorisation has been given, the firing procedure can then be started.
Multiface selection in Swift Standard multiface selection After importing the content of a PU, press the button all the imported faces and their related information (PU serial number, face name, number of programmed detonators, and name of the applied template) are displayed. Per default, all the faces are selected. To unselect faces use the / of the DRB2. The indicator above the list of faces always displays the status of the selection and the authorized limits.
Multiface selection with a face offset To change the rank (firing order) or unselect faces use the or lower in the list. / of the DRB2, the faces will go higher The example below displays 6 ranked faces (Faces 1 to 6), an unselected face (Face 7) and an already fired face (Face 8). Press √ to validate the face selection and go back to the main READ PUs screen.
Starting a firing procedure Once the detonator information has been transferred from the PUs to the DRB2, and a network has been defined, press on the button to switch from configuration to operational mode. The DRB2 initially verifies that the shot does not contain duplicated detonators (1 detonator programmed on 2 different PUs). When using more than one PU to program a shot, programming the same detonator on different PUs is possible.
DRB2 : 0504 0003 = 0376 0001 100ms The onscreen message indicates that the same ID has been programmed by two different Pus (SN: 504 and 376). The rank indicates the detonator sequence number of the ID: - 3 in PU 0504 - 1 in PU 0376 The effective delay that will be assigned to this ID is 100ms which has been assigned with PU_376. For Swift, the text is formatted as the example below: DBD 0777 ID PU Faces Cat PU. Faces Cat 50A8D 3 0415 FACE 1.
Warning: The smallest delay of the blast must be below or equal to 10s. In case one delay is higher than 10s, the related message is displayed for 5s then the main screen is displayed. After pressing the √ button, the screen below is displayed while the DRB2 is processing the blast plan data. Depending on the size of the blast plan and thus the processing time, this screen may only be visible for a short time.
NOTE: Switching to the operational mode is only possible after tagging the DRB2 with the TESTING RFID tag. The TESTING RFID safety tag should always remain in the shot firer's possession. When the TESTING RFID tag has been used, the operational mode is available for 15 minutes. If no button is pressed within 15 minutes , it will be necessary to tag the TESTING RFID tag again to restart a procedure.
Any errors will be displayed on the DRB2 screen and a voice message will inform the user of the error. If an error occurs at this stage of the procedure, the fault must be rectified and the system will not allow the procedure to continue. The user can use the check again function to verify the faults reported.
Error messages during the line test If no error is detected, the procedure continues automatically to the Extra Det Check. Extra Det Check The Extra Det Check searches for detonators connected to the circuit, not corresponding to the data transferred from the PU(s). These extra detonators are not programmed but are connected to the line. Refer to the related chapter "Error messages during detection of extra dets".
An additional 1 minute is added to the timer and the timer will start counting down from a total of 13 minutes. Once the user presses the detonators will commence. button, the count down timer will stop and charging of the Once charging has been completed, the DRB2 will authorizes the firing of the detonators’ firing capacitors, the DRB2 screen will indicate “Firing authorized” along with a voice message “READY TO FIRE”.
If errors are detected: If the DRB2 encounters any error that would still allow the firing procedure to continue, the count down timer will start with every error. Once the user acknowledges the error and continues the procedure, the timer will pause up until the next error is encountered or until charging is authorized. The timer will be allocated an additional 1 minute above the remainder of the 12 minutes, when charging is authorized then pause again when the button is pressed and charging is started.
When firing is authorized, the firing additional time is added (and the additional time bar changes from black to blue) Firing additional time CHARGING To charge the detonators, the shot firer initially needs to enable the charge button by tagging the FIRING RFID card: once activated it is enabled for 10 seconds. NOTE: Charging and Firing is only possible after tagging the DRB2 with the FIRING RFID safety tag. The FIRING RFID safety tag should always remain in the blast controller's possession.
IMPORTANT: If the operator releases the button, the system will go into safety mode, the capacitors are discharged and the firing procedure has to be restarted from the Firing Line test phase on the DRB2. The only consequence of this action is the extra time taken to run the procedure again. Firing Firing must take place within the allowed time of the unique countdown timer and before the time expires, but after firing has been authorised on the DRB2.
Firing procedure flowchart Begin Duplicate check on single DBD Duplicates < 4? No Firing procedure aborted No Firing procedure aborted No Firing procedure aborted No Firing procedure aborted Yes DBD Autotest No error? Yes Checking blast mode Synchronised mode? Yes Master / Slave search No error? No Yes Duplicates check on complete network Duplicates < 4? Yes Summary blast No R key pressed? Yes 1 Page 49 / 168
1 Step where time windows countdown is paused Step where time windows countdown is decreased Line Test Test OK? No Interpretation of message and corrective action to be done by the user. See § « Error messages during the line test » No Interpretation of message and corrective action to be done by the user.
Firing in WIRELESS mode General information The DT SP/UG Digital Blasting System can be operated in WIRELESS mode in three different configurations: • • • Mono Multiblast Synchroblast In Mono 1 DBD is operated with 1 DRB2, with the use of either internal or external modems. The mono mode allows users to fire one or more than one blast from the same location with the DRB2 and in the same time window as long as the amount of detonators is less than 1500.
In Multiblast up to 8 DBDs can be operated using the same DRB2 with the use of either internal or external modems. The multiblast mode allows users to fire more than one blast from the same location with the DRB2 and in the same time window.
In SYNCHRONISED mode or synchroblast up to 3 DBDs can be controlled remotely with the DRB2 through the use of either internal or external modems. Synchronised mode allows users to divide a large shot into two or three sections and synchronise the firing of the two or three sections. The radio communication between DRB2 and DBDs is sequential: the DRB2 questions each DBD one after the other. The DRB2 is to be used at the firing location in a safe area for operators.
Presentation of the DBD The DBD is the part of the DT SP/UG, connected to the firing line when firing using WIRELESS mode. It will communicate with the detonators, perform tests, charge the detonators and send the command to fire. The DBD is remotely controlled by the DRB2. The DRB2 displays the DBD’s status at all times.
The DBD supply voltage is 10-12 V DC and the rated current is 4A max. WARNING: The self-test of the DBD checks the capabilities of the line driver and during this test current consumption can reach 300 mA, always check the battery capabilities of the DBD, as the self-test can switch OFF the equipment. Basic indicators DaveyTronic® No lit LED: the DBD is OFF. DaveyTronic® Green LED is flashing: the DBD is ON and operational.
Communication quality When firing in WIRELESS mode, once the user has switched to operational mode an RF communication is established between the DRB2 and the DBDs. The quality of the communication is continuously monitored and displayed on the DRB2’s screen. General recommendations Range reducing elements are commonly introduced into wireless communication systems in the form of walls, wind, vegetation, machinery, dust, buildings, etc. resulting in temporary (or continuous) signal interruptions.
It is recommended to have at least 2 bars out of 5 in order to proceed through the firing procedure. Note that empty bars indicate that a data frame has not been correctly received and may slow down the firing procedure due to the same data frame having to be sent twice. Poor communication WARNING: Only start the procedure if the Q indicators indicate good blasting conditions. In case of poor communication, move the DRB2 to an elevated location.
General Precautions IMPORTANT: To use the DT SP/UG blasting system in WIRELESS mode, it is necessary to attend specific training courses approved by Enaex and its subsidiaries, as well as holding all necessary regulatory certifications in force in the country where the system is being used. SAFETY: The inherent safety of the DT SP/UG is not affected when remotely controlled. The Firing line and detonators remain physically connected to and managed by a DBD.
The use of the system is only allowed under the following conditions: (1) the system must not produce interference and (2) the operator of the system should accept all received radio electric interference, even if this interference might compromise the functionality of the system This device must be professionally installed This portable equipment with its antenna complies with FCC’s radiation exposure limits set forth for an uncontrolled environment.
This device complies with Industry Canada’s licence-exempt RSSs. Operation is subject to the following two conditions: 1. This device may not cause interference, and 2. This device must accept any interference, including interference that may cause undesired operation of the device Le présent appareil est conforme aux CNR d’Industrie Canada applicables aux appareils radio exempts de licence. L’exploitation est autorisée aux deux conditions suivantes : 1. L’appareil ne doit pas produire de brouillage, et 2.
Preparing a blast in Wireless mode Note: It is assumed that "Firing in WIRED mode" has been read before reading this chapter Overview Chapters below describe how to setup the system to fire a blast in wireless mode. NOTE: A synchroblast can only be fired in WIRELESS mode.
Hereunder an overview of a Multiblast system (up to 8 DBD).
Data transfer from PU to DBD The PU has all the programming data (network name, detonator’s unique ID number, sequence number and delay) stored in its RFID tag. After programming and circuit testing with the PU is finished and before starting the firing procedure, the stored data has to be transferred through RF communication between the RFID tags of the PU to the DRB2 and then by RF communication from the DRB2 to the DBD.
- Repeater configuration A DBD can be used as a Repeater in order to improve wireless communications. DBDs connected to the firing line can be used close to the shot as usual and another DBD (not connected to the firing line) can be placed between DRB2 and the other DBD's on the shot to act as a repeater. The DRB2 and the DBD’s must be configured as follows: 1. 2. 3.
DBD modem configuration 1. Switch off the DBD 2. Install antennae on the DRB2 and DBDs (configuration will be done by means of wireless communication of the equipment; the equipment should be located in close proximity to each other.) 3. Power on the DRB2 4. On the DRB2, select the General Setting menu then DBD modem menu and press the √ button 5. Tag the DBD to be configured or enter its number with the arrow buttons and press the √ button 6.
7. Power on the DBD to be configured 8. The DBD configuration will be set automatically after communication between the DRB2 and DBD is established and should take no longer than a few seconds. 9.
DRB2 modem configuration 1. Power-on the DRB2 2. Select the General settings menu then DRB2 Modem menu and press the √ 3. Select a. Modem type => External or Internal b. Modem model (only available if external modem is selected) : 1. DIGI 2. RS485 3. RS232 c. Repeater mode => Enable or disable (only available if internal modem or DIGI external modem selected) 4.
Specific underground application For specific underground application, the DTUG system can be operated in wireless mode with specific communication modems. The DRB2 is to be used at the firing location on surface in a safe area for operators and the DBD is located close to the shot underground. Parameters of serial configuration can only be modified by means of the external modem configuration and is not possible to configure through the DRB2 menus.
Wireless test This menu enables the operator to test the wireless communication of the DT SP/UG system: - Equipment test: Enables a test and validates the RF chain between two units. Single range: Enables a test of the wireless communication of the system installed in the field (now available for SP and UG). Mine mapping: Enables users to define the best location of the equipment in the mine in order to have the best communication quality.
Equipment test The objective of this test is to check the chain of radio communication between a DRB2 and a DBD in an office (warehouse, laboratory, technical center …) environment. This test can be performed using internal modems, external modems, in repeater mode and in non-repeater mode. Note: The equipment under test should have the same modem configuration. The test time is approximately 3 minutes in non-repeater mode configuration and 4 minutes in repeater mode configuration.
Associate the DBD to the DRB2 The DBD to be tested must be associated with the DRB2 intended to be used. The operator needs to tag the DBD with the DRB2 or type its number by scrolling through the characters with / and moving the cursor with / .Then press √ to validate and continue. Press √ to start the test, X to exit or press the button to modify the tagged DBD.
Note: if DRB2 failed to establish wireless communication with the DBD, the following screen is displayed Test result Depending on the test results one of the two following screens is displayed: • Test failed • Test OK Both screens display the test result for each equipment used in the test: Page 72 / 168
• • • 𝑆̅ : Received Signal Strength Indication (Rssi) average S : deviation SMin/SMax : min and max value of the Rssi It also display 𝑄̅ : Quality average of the whole chain of communication Save test result At the end of the test the user has the option to export the test result to a USB key. This report logs the results of the test in a file named TE-DRBxxx_yyyymmdd.txt where xxx is the serial number of the DRB2 and yyyymmdd is the date of the test.
Single range The objective of this test is to check that the communication chain between the DRB2 and up to 4 DBDs is correct before tagging the PUs and start a firing procedure.
Associate the DBDs to the DRB2 The wireless communication can be test with 1 and up to 4 DBDs. The operator must either tag the DBDs with the DRB2 or type the DBDs number by scrolling through the characters with / and moving the cursor with / . Then press √ to validate association. Press √ to start the test, X to exit or press the button to modify the tagged DBDs.
Save test result At the end of the test the user has the option to export a report to a USB key. This report logs the results of the test in a file named SR-DRBxxx_yyyymmdd.txt where xxx is the serial number of the DRB2 and yyyymmdd is the date of the test. While in the test result screen on the DRB2, connect a USB key to the DRB2 and press the button so save the report.
Mine mapping The objectives of this functionality is to do a mapping of signal quality in the mine when the wireless DTSP system is introduced in order to determine suitable geographical positions for the DRB2 and the DBDs with good communication. Note: The equipment under test must have the same modem configuration. The test time for 1 DBD (not repeater) is approximately 1min30s, and for 4 DBD 6 minutes.
Page 78 / 168
I. Location x: The "x" is the location number, it defines the location of the unit and is reported in the summary table (refer to the "Summary" to access to the summary table) Press / to select the location and press √ to start the test from this location. II. Summary : Based on the test completed at different locations, the summary screen displays the summary test result in a table. This screen indicates the following information: o A summary of the test results previously done.
o DBD (per cell) : xx% is the average RSSI (Received Signal Strength Indicator) level and the color of the cell (refer to table below) depends on the average Q calculated during communication between the relevant DBD and DRB2. Q between DRB2 and related DBD is higher than 75% Q between DRB2 and related DBD is between 51% and 75% Q between DRB2 and related DBD is between 26% and 50% Q between DRB2 and related DBD is equal to or less than 25% This menu allows the report to be exported on to a USB key.
Firing procedure After all tests have been completed with the PU(s) and the site is secured the shot firer can connect the firing line to the DBD and retreat to a safe firing location. At the firing location the blast plan data can be transferred from the PU(s) to the DRB2, and the DRB2 switched into operational mode. The DBD then executes the firing procedure and associated tests. The progress of the procedure and the results of the tests are displayed on the screen of the DRB2.
Firing line terminals Synchro line terminals WARNING: Only connect a firing line to the firing line terminals of the DBD, encircled in red on the picture above. Never connect any other equipment to these terminals. WARNING: In Monoblast and Multiblast never connect anything to the Synchro line terminals of the DBD.
Monoblast Read PU On the MAIN menu, when the DRB2 is first switched on, the icon the screen which means that no data has been transferred yet. Use the / press √ . is displayed on the top right of arrow button on the left hand side of the DRB2 to select Network \ Read PUs and The DRB2 must read the PUs RFID tag in order to transfer the data. Switch off the PU, and tag the PU lining up the PU with the DRB2’s left bottom corner.
Tag another PU to add detonators in the blast plan. Press X to exit and return to MAIN menu. Press to proceed with blast procedure. Read Pus (Swift) Refer to the Read PU chapter. When the transfer of a Swift PU is completed a summary of the transferred data is displayed showing “DBD #XXXX” blast , number of faces, the total number of detonators and PU with its serial number.
The maximum number of faces is 8: If Swift detonators are already assigned to a DBD, impossible to tag another PU that contains non Swift detonators Impossible to have more than 1500 detonators per DBD: Page 85 / 168
Self-test and blast mode detection Once blast plan has been transferred from the PUs to the DRB2, press procedure. The DRB2 will conduct the following steps: - to start the blast Checking system compatibility Perform an equipment Self-test Perform a blast mode detection The status of the steps is displayed in the last line of the screen The system compatibility check verifies all components of the unit are compatible from an Hardware and Software point of view.
• • • Automatic blast mode: The DRB2 will check the DBD synchro line wiring and automatically detects the blast mode accordingly (in this mode the detection time can take between 10 to 45 seconds) Mono/Multiblast mode only: The Blast mode is forced for only Monoblast, Multiblast. There is no additional delay for mode detection as Synchroblast® is not possible. Synchroblast® mode only: The Blast mode is forced for only Synchroblast®.
Once the right mode has been detected successfully, the following screen is displayed: Or If an error occurs during the test, the relevant message is displayed in the status line on the screen of the relevant DBD. Once blast mode has been detected successfully, the operator is prompted to press the firing procedure.
Préliminary checks The screen below is displayed while the DRB2 transfers the blast plan data to the DBD. The time to process the blast plan, depends on the size of the blast plan and this screen may be visible for a very short time. When the download is successfully completed, the DRB2 analyses the blast plans NOTE: Switching to the operational mode is only possible after tagging the DRB2 with the TESTING RFID safety tag. The TESTING RFID safety tag should always remain in the shot firer's possession.
Press to list all detonators and delays When in the list of detonators and delays, press / to scroll through the detonators, to scroll through the PUs or X to return the summary display. OR Press to exit to the MAIN configuration menu. OR To start detonator test, swipe TESTING RFID card on the back of the DRB2 and press Page 90 / 168 √ .
Detonator test As soon as TESTING RFID card has been swiped on the back and (refer to the Préliminary checks chapter), the detonator tests start: √ button has been pressed Afterwards, the test procedure will proceed to the "extra det check" test and the "detonator self-test".
Dealing with errors during the firing phase chapter). If no error is detected during the tests and they have been completed, the system authorizes the charging of the detonators firing capacitors with an onscreen message “Charging authorized” and a voice message “READY TO CHARGE”. Charging of each network, must be started before the unique timer expires. Charge The operator has to enable the charge button by tagging the FIRING RFID card: charging is activated for 10 seconds.
Fire When charging is complete, a charge test is performed and firing is authorised. The illuminated and the vocal message “READY TO FIRE” is heard. Press button is to fire the blast. If the detonators are not fired by the time the unique countdown timer has expired, the DRB2 informs the user that the time has expired and the procedure has to be restarted, starting from the line test phase.
IMPORTANT: If the operator releases the charge button, the system will go into safety mode, the capacitors are discharged and the firing procedure has to be restarted from the detonators testing. The only consequence of this action is the extra time taken to run the procedure again. Multiblast Read PU Refer to the Read PU chapter. In Multiblast mode, the blasting system is able to control up to 8 DBD networks.
Press to proceed with blast procedure. Read PU (Swift) Refer to the Read PU and Read PU (Swift). The blasting system is able to control up to 8 DBD networks with Swift detonators. The maximum number of devices (DRB2/DBD) in the multiblast is 8.
Self-test and blast mode detection Refer to the Read Pus (Swift) Refer to the Read PU chapter. When the transfer of a Swift PU is completed a summary of the transferred data is displayed showing “DBD #XXXX” blast , number of faces, the total number of detonators and PU with its serial number.
The maximum number of faces is 8: If Swift detonators are already assigned to a DBD, impossible to tag another PU that contains non Swift detonators Impossible to have more than 1500 detonators per DBD: Page 97 / 168
Self-test and blast mode detection chapter. Example of Multiblast screen: Other configuration examples: Once blast mode has been detected successfully, the operator is prompted to press the firing procedure. Preliminary checks Refer to the Préliminary checks chapter.
Use / on the right hand side of the DRB2 to scroll through screens: the selected screen is surrounded in red. Detonator test Refer to the Detonator test chapter. The test procedure begins by testing the line. Operators should select a DBD network and press √ to start the test of the selected network.
The networks can be controlled independently from each other, although the firing line test can be started in parallel on all networks. Press / on the right hand side of the DRB2 to select another network (surrounded in blue) and press √ in order to start its line test. Charge Refer to the Charge chapter. Charging and firing is a sequential and continual process, this means that once a network has begun charging it must be fired or aborted before selecting the next network to charge and fire.
To charge the detonators of a DBD network, use the right / desired network (indicated by the green surrounded by red). of the DRB2 to highlight the Fire Refer to the Fire chapter. To fire, the operator must press the button while still holding down the In WIRELESS mode, the operator must hold the charge button. button down until the shot starts to fire. A line at the bottom of the screen shows the blast progress. (This can be very fast for maller shots).
After firing a shot the screen below is displayed. Operators are able to select the next screen and then fire the remaining networks by following the same charging and firing procedure.
Onetouch Multiblast In Onetouch Multiblast mode, up to 8 DBDs can be operated using the same with the use of either internal or external modems. Onetouch Multiblast mode allows users to run the different blast procedures in parallel until the system is “READY TO FIRE”. Once, the system is “READY TO FIRE”, all blast are triggered after pressing and holding the only once. button, then pressing the button By default, Onetouch Multiblast is not enabled.
DBD gap (for Onetouch Multiblast only) DBD gap is the delay between two successive blast when blast is operated in Onetouch Multiblast mode: BLAST 1 BLAST 2 DBD Gap Use the √ . / arrow key on the left hand side of the DRB2 to select Network \ DBD gap and press Use the / arrow key on the left hand side of the DRB2 to change the Gap value and press Gap value is between 1sec and 5 sec by step of 1sec. Read PU See Read PU Chatper.
Note: The message below is displayed if a tagged PU is associated with a 9th DBD in Onetouch Multiblast mode ERROR: No more location available Read PU (Swift) Refer to Multiblast Read PU and Read PU Chapters Self-test and blast mode detection See Read Pus (Swift) Refer to the Read PU chapter. When the transfer of a Swift PU is completed a summary of the transferred data is displayed showing “DBD #XXXX” blast , number of faces, the total number of detonators and PU with its serial number.
To select the faces to be fired, press LIST button (see “Multiface selection in Swift” chapter) The maximum number of Swift PU per DBD is 6: The maximum number of faces is 8: If Swift detonators are already assigned to a DBD, impossible to tag another PU that contains non Swift detonators Page 106 / 168
Impossible to have more than 1500 detonators per DBD: Self-test and blast mode detection chatper. In case of Onetouch Multiblast (“Automatic blast mode” or “Mono/MultiBlast forced” AND Onetouch Multiblast option enabled), the screen below is displayed according to the number of DBDs in the blast plan. The operator is prompted to press √ to continue the firing procedure.
Once blast mode has been detected successfully, the operator is prompted to press the firing procedure.
Note: The message below is displayed if the delay between two blasts > 10sec >10sec BLAST 1 BLAST 2 BLAST 3 BLINKING To fix the problem, decrease the DBD gap value or/and decrease the first delay of the corresponding blast plan (blast plan 3 – DBD 101 in above example). If √ is pressed, the corresponding blast is discarded for the rest of the blast procedure.
Note: Impossible to continue procedure as long as detonator tests are not finished for all DBD Detonator test See Detonator test chatper. The test procedure begin by testing the line. Operators should press in parallel.
Note: it is not possible to continue the procedure if all blasts do not reach “Charging authorized” step, unless one of the blast is greyed Example: DRB→DRB2 communication failure In this example it is possible to continue blast procedure with blasts 1 and 3 Charge See Charge chatper.
Then press and hold the key to charge the detonators. All blasts will be charged in parallel. Fire See Fire chapter. When charging is complete for all DBDs, a charge test is performed and firing is authorised. The button is illuminated and the vocal message “READY TO FIRE” is heard. Press at least 2 seconds to fire the blast.
Once the fire order has been sent and the firing is in progress, the firing button can be released. “Release the FIRE button” is displayed whether the button is released or not. After firing the blast, the green window below are displayed. Note: Once the button has been pressed, blasting sequence can be interrupted.
Synchroblast Read PU Refer to the Read PU chapter. The DT SP/UG system is capable of controlling up to a maximum of 3 DBDs in Synchroblast mode. Self-test and blast mode detection Refer to the Read Pus (Swift) Refer to the Read PU chapter. When the transfer of a Swift PU is completed a summary of the transferred data is displayed showing “DBD #XXXX” blast , number of faces, the total number of detonators and PU with its serial number.
The maximum number of faces is 8: If Swift detonators are already assigned to a DBD, impossible to tag another PU that contains non Swift detonators Impossible to have more than 1500 detonators per DBD: Page 115 / 168
Self-test and blast mode detection chapter. When performing a Synchroblast®, (“Automatic blast mode” or “Synchroblast mode only”) the master DBD is automatically selected according to the synchro-line wiring. (based on the wire length detection of the system) When the sync test is successfully completed the screen below is displayed.
Note: Impossible to continue procedure as long as detonator tests are not finished for all DBD Detonator test Refer to the Detonator test chapter. The test procedure begin by testing the line. Operators should press in parallel.
After detonator selftest has completed on all networks, all DBDs are Synchronized as described below. The multiple screens changes to a single screen and only the master DBD information is displayed. Only the master DBD is controlling all the detonators from this point forward. If no error is detected and the tests / synchronization is finished the procedure authorizes the operator to charge the detonators’ firing capacitors.
Charge Refer to the Charge chapter.
Fire Refer to the Fire chapter.
Safety lockout The safety lockout is a feature of DT SP/UG system that enhances the safety of the user of the DT equipment: The first safety feature is the enhanced security TAG • • • Testing TAG - required to proceed with Testing after summary blast Firing TAG - to proceed to Charge and Fire Safety Lockout TAG to o Adjust Firing Window setup o Change Date/time when Firing window is enabled o Bypass DRB2 position check errors when Exclusion zone has been enabled By default the DRB2 is set to have three se
Enhanced security tag setup For security purposes, the DT SP/UG system has the option to configure three different RFID tags in order to modify setup or unlock the testing or firing procedures. TESTING RFID tag The testing RFID tag is a mandatory requirement to enable the testing phase of the shots.
Safety Lockout RFID tag The SAFETY LOCKOUT RFID tag is mandatory: - - To setup the firing window option if it has been enabled on the DRB2 and enables the user to: • modify the time window setup • change date / time if time window is enabled. To bypass the exclusion zone feature if the GNSS position is not available during DRB2 position checks.
Exclusion zone The exclusion zone is a polygon of a maximum of 256 points corresponding to the exclusion zone set for the blast by the mine. The exclusion zone is defined by means of two files: - EXC_ZONE.csv : it contains exclusion zone coordinates (in UTM reference). UTM_DATA.txt: it contains all necessary information in order to interpret EXC_ZONE.csv and perform the convertion from WGS84 reference (longitude/latitude from GPS) into local UTM projection (Easting/Northing). EXC_ZONE.csv: 0;683349.
Read Eclusion zone The required exclusion zone files (EXC_ZONE.CSV and UTM_DATA.TXT) are transferred to the DRB2 by means of a USB key. Both files must be in the root folder of the USB key. The exclusion zone file is checked and verified before the files are transferred to the DRB2. If the file format or any of the data in the exclusion zone file is incorrect (EXC_ZONE.
If the file format or any of the data in the definition and format file is incorrect (UTM_DATA.TXT), the following message is displayed: Display Exclusion zone Exclusion zone Note : To get DRB2 position on the display, a valid GPS position is requested DRB2 position The exclusion zone can be integrated into different shots and/or pits and is compatible with Multiblast. All the blast locations must be inside a single polygon (refer to the following figure).
When imported to a DRB2 the exclusion zone will be automatically erased after 24hrs or immediatly after firing of all the blasts (In Multiblast the exclusion zone is available untill the last blast is fired) WARNING: If the exclusion zone feature is enabled, it is impossible to to complete the firing procedure without the correct EXC_ZONE.csv and UTM_DATA.txt files loaded into DRB2. Position of the DRB2 (and the shotfirer) An optional external GNSS accessory is available for the DTSP sytem.
Safety checks during the firing procedure The position of the DRB2 is checked: • • • When the MODE button is pressed. A screen is displayed to show the status of the safe position and the user must press the √ button to proceed.
Press √ Tag the TIME WINDOW RFID card • When the GNSS position is not available when the user is asked to press CHARGE button ( after ready to charge voice message): Page 129 / 168
Press √ Tag the TIME WINDOW RFID card Page 130 / 168
GNSS status The status of the GNSS accessory is verified during the safety checks. This status is displayed in the top right corner of the DRB2 screen near the battery level icon.
Examples Exclusion zone not defined or expired GNSS position not available DRB2 inside the exclusion zone or Page 132 / 168
Dealing with errors during the firing phase Dealing with errors during synchro-line test procedure Error Cause CORRECTIVE ACTIONS: Communication error with the related DBD Check the related DBD Short circuit on synchro line (Related DBD is blinking) Check the synchro line Interconnection between firing line and synchro-line (All DBDs are blinking) Check the firing line and synchro-line BLINKING Page 133 / 168
Error Cause CORRECTIVE ACTIONS: The self-test of the related blast driver failed (The related DBD is blinking) The system has detected an error during the self test when switched to operational mode. Contact your Enaex representative. BLINKING Error messages during the procedure MESSAGE INTERPRETATION: The related DBD fails CAUSES CORRECTIVE ACTIONS: The system has detected that the DBD stops Quarantine the DBD and contact your Enaex working during the firing procedure: hardware failure.
Error messages during the line test IMPORTANT: IT IS NOT POSSIBLE to continue with the procedure if a fault is detected during the line test phase. Open line MESSAGE INTERPRETATION: No detonators on the line. Voice message : ‘WARNING, FIRING LINE MALFUNCTION’ CAUSES CORRECTIVE ACTIONS: Firing line not connected to the firing line terminals • Check the connection. Bus line not connected to firing line • Check the connection. • Check the continuity of the line.
Error messages during detection of extra dets If the bus lines are correctly checked after the detonators have been connected, this type of error should not occur.
Det number ID Delay (ms) Remark #0001 45DFFC 10 #0002 567E01 40 #0003 8AA299 70 #0004 5DE871 13960 #0005 B14BC4 400 Extras det 1 05F23A 13979 13960 +19 Extras det 2 F42928 13998 13960 +2*19 Extras det 3 BD05FF 14000 13960 +3*19 >= 14000 Original blast plan Permanent incoherent Det answer MESSAGE INTERPRETATION: The system finds extra detonator but is unable to communicate with it.
Intermittent connection At the end of the of extra detonators detection test, the following will be displayed if there are intermittent detonators MESSAGE INTERPRETATION: The DRB2/DBD has detected a poor or intermittent connection for detonator 1 Voice message: ‘DETONATOR COMMUNICATION ERROR CAUSES CORRECTIVE ACTIONS: A cut line or a splice causes an intermittent connection ⚫ Turn off, disconnect the firing line and go to the blast area, identify and repair the wire (cut, splice, or poorly connected to
IMPORTANT: The firing procedure will automatically abort after 3 mins, if an option is not selected WARNING: To be able to continue with the procedure, it is necessary to scroll through the entire list.
Incoherent answer TYPE OF DEFECT INTERPRETATION: The detonator’s answer is corrupted and cannot be decoded. CAUSES CORRECTIVE ACTIONS: ⚫ Turn off, disconnect the firing line. Disconnect the detonator and check it with the PU: • If the PU reading is correct, check for leakage and/or check line to reduce lengths. • If the PU reading gives ‘NO DIALOGUE’ or INCOHERENT ANSWER’, treat the detonator as defective, in accordance with applicable rules.
Delay error TYPE OF DEFECT INTERPRETATION: The delay read in the detonator is different from the programmed delay. CAUSES CORRECTIVE ACTIONS: Detonator is out of order ⚫ Restart the procedure, if the same error happens, disconnect the detonator and treat the detonator as defective in accordance with applicable rules. WARNING: If the ‘DELAY ERROR’ message continues, the detonator will be initiated but with an incorrect firing time.
Special procedure The special procedure can be selected after the extra detonator test and detonator self-test when all error messages have been read. The ADMINISTRATOR menu section of the manual describes the limitations that can be applied to special procedures. Use / to select “ACCEPT AND GO ON” and confirm with Confirm with √ √ . to continue in special procedure. WARNING: It is the blaster’s responsibility to assess the errors and the consequences before selecting ‘SPECIAL PROCEDURE’ mode.
Error messages during charging and firing authorized window Line cut Monitoring: MESSAGE INTERPRETATION: A detonator has been detected missing. DT Evolution now displays the detonator number immediatly CAUSES CORRECTIVE ACTIONS: Bad or poor connection The detonator should be detected as "no dialogue" if the test procedure is run again.
WARNING: When "firing energy low" is detected, if no button is pressed before timeout. "TIME EXPIRED" is displayed and special procedure will be unavailable. Check that bus line lengths and leakage complies with Enaex recommendations (refer to the chapter "program dets") Firing button released MESSAGE INTERPRETATION: No voice message, long beep When the operator presses the charge button, the DRB2 detects that the firing button is already depressed. CAUSES CORRECTIVE ACTIONS: Keypad faulty.
Error message with a Swift detonator On SP/UG a detonator in error will be described with the PU number that programmed it, its sequence number and its delay.
History and Datalogger File Transfer The history file is a record of the events tracked by the equipment (DRB2 and DBD) from the start of the firing procedure up until the end of the firing procedure. This record allows users to keep track of previous blasts and to trace the sequence of events in case of irregularities. The record of the events can be obtained as a .TXT file on a USB key.
Insert a USB key. The USB port can be accessed by removing the dustproof plate on the right hand side of the DRB2 (simply pull on the 2 fast opening terminals). Press √ to start the transfer of the history file. The message “Transfer in progress.” is displayed and the progress is indicated by the increasing percentage. The USB key can be extracted once the message “Transfer OK 100%” is displayed.
The history of the procedures will be contained in the *.txt file on the USB key. The history file is named "HISTO_YYYXXXX.txt" where yyy is the type of equipment and XXXX is its serial number. Datalogger files In the MAIN menu, use / on the left hand side of the DRB2 to select HISTORY and press In screen below, select Download Datalogger Files and confirm with √ . Insert a USB key and press last firing procedures. √ √ . to start the transfer of the files.
Page 149 / 168
WIRELESS mode History file In wireless mode, it is important to download the history file of the DRB2 and the DBD as the events recorded and complementary. To download the history file of the DRB2, please refer to the the previous chapter. To download the history file of the DBD: 1. Connect the USB key to the corresponding port on the left side of the DBD (unscrew protecting cap first) and power on. 2. The 4 LEDs will start flashing back and forth. 3.
Additional procedures PU to PU transfer In the event of a PU failure (e.g. battery problems), the data contained in a PU can be recovered by the DRB2 and transferred to another PU. The function is accessible through the NETWORK menu. Note: It is assumed that "PU to DRB2 data transfer" has been read before reading this chapter In the MAIN menu of the DRB2, use / on the left hand side of the DRB2 to select NETWORK and press √ .
The transfer of the blast plan of the source PU to the DRB2 continues as long as the percentage increases and the message “Transfer in progress….” is displayed. The next screen below displays the message “Transfer OK” and prompts the users to tag the PU to which the data will be copied (target PU), with the DRB2.
The transfer of the blast plan from the DRB2 to the target PU continues as long the percentage value increases and the message “Transfer in progress…..” is displayed. When the message “Transfer OK” is displayed for the second transfer, the process is completed. The blast plan has been transferred from the source PU to a target PU.
Maintenance Battery management Only use the "spider" charger, or the car adapter provided to charge the batteries of the equipment. Recharge all equipment at least once a month. The user must not remove the batteries. Battery Type: Prismatic rechargeable Lithium-ion single cell Nominal voltage: 3.65 Volts Nominal capacity: 6.8 Ah Nominal energy: 24.8 Wh Charger: INPUT: OUTPUT: 100-240 VAC, 50/60 HZ, 2.0A 12 V, 6.
Do not store the battery fully charged at high temperature (over 25/30°C) this will reduce the battery life. - Ideal storage temperature is between 5 and 15°C (New batteries, or equipment stored) Unutilized equipment should not be stored fully charged for more than one month, but between 20 and 60% of charge. Avoid charging at high temperature (room temperature over 30/35°C) as this is shortening battery life, and may stop the charge cycle before fully charging, resulting in reduced capacity.
WARNING: Charging mode (plugged in to mains supply) is prohibited in outdoor use; charging mode (plugged in to mains supply) is for indoor use ONLY. If the equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired. The level of safety of this equipment is only guaranteed for usage that conforms to the intended use, as described in this manual.
Power consumption and battery autonomy The Remote Blaster (DRB2) Autonomy of the DRB2 is around 2 hours in WIRED mode (screen and keyboard backlight on) and 3 hours in WIRELESS mode (screen and keyboard backlight on). The DRB2 continuously displays a battery level indicator in the upper right-hand side of the screen.
➢ indicating a battery status of 25 to 49% charged ➢ indicating a battery status of 50 to 74% charged ➢ indicating a battery status of >75% charged When the DBD and the DRB2 are communicating during a blasting procedure, the battery level of the DBD is displayed on the screen next to the wireless indicators. When the battery of the DBD is worn the LED battery indicator level blinks and on the DRB2, the battery icon is crossed out.
Recharging the battery Charging duration from a flat battery is around 4 hours, and up to four units can be charged at the same time using the spider charger. Only use the "spider" charger, or the car adapter provided for recharging the batteries of the equipment. Recharge all equipment at least once a month. The Remote Blaster (DRB2) Batteries of the DRB2 are recharged by plugging one of the spider charger cables in to the charging point of the DRB2.
Battery calibration Battery calibration is a process than computes the real capacity of the equipement’s battery. During this process, the equipement drains its own battery. Once it is empty, it starts a charge cycles and measure the quantity of energy that is stored in the battery. At the end of the process, equipement computes the capacity of the battery in mAh.
The Remote Blaster (DRB2) Like the PU, when the number of charge is more than 30 charges, the DRB2 prompts the user to calibrate the battery The calibration process time is estimated and displayed because the complete process of discharging / charging can last a maximum 12h on a DRB with a brand fully charged new battery. As for the PU, if the X button is pressed or after 5 minutes, the DRB2 proceeds with standard charging.
The Blast Driver (DBD) Once a calibration is necessary, the DBD, as the DRB2, first completely discharges its battery and then charges it. As with the DRB2, it is possible to postpone the calibration if the user needs their units before the end of the estimated calibration time. Postponing is done by unplugging the power cord and plugging it again, During discharge, the 4 LEDs are blinking (Long ON, short OFF) The charge phase has the same behavior as standard charging.
Battery status indicator – Used battery After calibration, the battery is calibrated and the equipment displays a more accurate status of the battery. The indicator is now proportional to the real capacity of the battery (not to the theoretical value of a brand new battery).
During the firing procedure, the DBD battery level is displayed and if the battery is worn the indicator is . Cleaning For a longer use, keep the equipment as clean as possible. • Clean with a SOFT cloth and cleaning product • Do not use corrosive substances • Do not spill liquids on the equipment Annual inspection The devices of the blasting system must undergo annual maintenance by the manufacturer or an agency approved by the manufacturer.
repeated after a second attempt to re-start the equipment, return the affected equipment to the manufacturer or an agency approved by the manufacturer. Software revisions Enaex constantly develops new software to offer customers additional functions. Contact your Enaex representative for the latest software versions. Rating and characteristics of fuses Fuses used in the equipment are NANO Slo-Blo Fuse 452/454 Series and have interruptive ratings of 50 amperes at 125 VAC/VDC.
Example: shipment of 2 PUs and 2 DRB2s, is 4 pieces of equipment in total, 4 x 0.153 kg = 0.612 kg. The NET WEIGHT field to be filled in should be 0.612 kg. 4. Required document: the Shipper’s Declaration for Dangerous Goods Example: (https://www.iata.org/whatwedo/cargo/dgr/Documents/Shippers-DeclarationOpen-Format-Non-Fillable.pdf) Range of environmental conditions Refer to the related technical datasheet. Assembly, location and mounting The PU and DRB2 are handheld units.
Page 167 / 168
© Davey Bickford 2022 Information contained in this document is the sole property of Davey Bickford Enaex and cannot be reproduced without its written consent. Indications and recommendations described herein are based on current knowledge by the manufacturer. The manufacturer cannot foresee all possible applications for its products. Consequently, the products described in this manual are sold under the sole warranty that they conform with the specifications indicated in this manual.
