723U0201 THOR Operator Manual Rev 08
723U0201 THOR Operator Manual Rev 08
Customer Support
Instantel is represented by a network of qualified dealers throughout the United States, Canada, and
internationally. For further information, including product literature and the dealer nearest you, contact
Instantel.
Legal
© 2019 Xmark Corporation. All rights reserved.
The Instantel logo, THOR, Auto Call Home, Blastware, Blastmate, Histogram Combo, InstaLink, Minimate, Minimate Blaster,
Minimate Plus, Minimate Pro4, and Minimate Pro6 are trademarks of Stanley Black & Decker, Inc., or its affiliates. Instantel and
Micromate are registered trademarks of Stanley Black & Decker, Inc., or its affiliates.
Adobe, Acrobat, and Reader are registered trademarks of Adobe Systems Incorporated.
Citrix is a trademark of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States
Patent and Trademark Office and in other countries.
CONVENTION INDICATES
The names of user interface elements, such as buttons, fields, and
Bold type
checkboxes, are indicated in bold type.
NOTE In this manual, the term "Minimate Pro" refers to both the Minimate Pro4 (4 Channel) and the
Minimate Pro6 (6 Channel) devices.
NOTE In this manual, the term “Unit(s)” refers to the “Monitoring Unit(s)” noun.
Collapse
panel
Navigation arrows
sections.
Shortcuts
Functions can be accessed using, buttons, icons, drop-down menus, collapsible panels, right clicks,
keyboard, or navigation arrows. This manual’s procedures do not show all the alternatives, rather for
clarity only one straightforward path is used.
E.g. There are occasions where the same function is available via a different path.
The functions Add Project, Edit Project and Delete Project have three ways to access their functionality.
An icon exists in the Menu Bar, in the Project Details Panel and also by right-clicking on a project.
Advanced License
Enabled Features
Report Analysis
This feature allows you to perform analysis operations on waveforms in event reports.
THOR organizes data into Projects and Events. Projects automatically group related events for easy
navigation and analysis. For more information, see section 4.1 Understanding Projects on page 74 and
section 5.1 Understanding Events and the Event Table on page 86.
The unit tab displays the dashboard which provides important information about the units such as:
Connection status, monitoring mode, connection details, battery health, available memory, scheduler status,
current unit setup, number of events residing on the unit, name of the assigned operator, unit date and time, last
calibration date, calibration company, firmware version, and Auto Call Home state.
The dashboard provides tools to add, edit, delete, and manage units. The dashboard can also help
configure units connected to THOR either through a local computer or through remote communications.
Some common tasks accessible via the dashboard:
Change the monitoring state, define a schedule, update date and time, reload the unit’s setup file, add and
remove operators, change the owner, delete events and logs, perform a sensor check, manage Auto Call Home,
update the firmware, restart the unit.
For more information, see section 3.3
Unit Dashboard View on page 36.
A selected unit
The Auto Call Home (ACH) tab defines the ACH communication parameters, and customizable settings
for reports, filters and email.
NOTE The Auto Call Home function uses a Windows Service and does not require THOR to run to be active.
See section 6 Auto Call Home Setup and Management on page 135. Understanding Auto Call Home (ACH)
NOTE Whereas Blastware Mail was a separate application, THOR integrates email functionality. From
within the THOR user interface, you can set up a Secure Sockets Layer (SSL) or Transport Layer
Security (TLS) secure connection with your Simple Mail Transfer Protocol (SMTP) server, as well
as email a PDF of event data to stakeholders.
General preferences define which format THOR uses to display date/time, measurement units, and
compliance standards. Setting these preferences only changes how data is viewed in THOR. The settings
of the units are unaffected.
These are the default settings for all Projects & Events. If you change preferences for an individual
Project/Event, they will override the general preferences for that Project/Event.
1.5 NOTIFICATIONS
Notifications are short messages that bring attention to new information. They appear in a designated
sidebar and are accessible regardless of the active tab. You can configure which notifications to display by
selecting their respective checkboxes in the Preferences General section. See section 7.1 on page 156.
Notifications Bell
alert icon
Notifications can also appear as Popups to direct the user’s attention to the new information. Popups
will only appear when THOR is not the active screen, (E.g.
A user is writing an email while a notification occurs).
Popups disappear after a few seconds, either click on the
link in the Popup or expand the notifications sidebar to
view the notification. The sidebar shows a Bell icon to
indicate that there are notifications for reviewing.
NOTE You can Filter and Sort notifications in the same way as with Events, see section 5.7.5 Filter Events on
page 102 and section 5.7.6 Sort Events on page 106.
Warning
Info
Error
NOTE For unit upgrades, please contact your local Instantel dealer.
NOTE * See the release notes for a full description of Series III support. Date/time can only be updated when
the unit stops recording and enters the idle state.
NOTE Only one instance of THOR can run on a computer at a time. THOR does not support multi-user
environments, such as Citrix solutions.
You also require:
An Internet connection (installations, patches, upgrades, email notifications, sending events to Vision).
A USB port to physically connect THOR to a Micromate, Minimate Plus or Blastmate III.
An Ethernet, USB, or RS232 serial port, to physically connect THOR to a Minimate Pro.
O PTIONAL
PDF viewer—to view reports
Printer—to print reports
Optical drive (DVD or CD)—to install THOR using a CD Remote Computer
Monitoring
A cellular modem connection may be used to connect a Cellular Network
unit to a cellular network. Cellular Cellular
NOTE The Auto Call Home feature and connecting to a unit (to configure the unit from THOR) using remote
communications requires a cellular modem. Instantel recommends using the Sierra Wireless™
AirLink™ GX-400, LS-300 series or Raven RV-50 modems.
NOTE Once installed THOR can run without an internet connection although some features will not be
available. (E.g. THOR cannot communicate with units on the network or check for software updates.)
THOR connects occasionally (7 days) to the license server to verify Advanced licenses. Advanced
licenses that have expired will revert to the functionality of Standard licenses until they are renewed.
1 Download the THOR installer from https://www.instantel.com/resources under the Software section.
2 Run the THORWebInstaller.exe. If a Security Warning dialog opens, click Run
1.2
To change the
install folder,
click Browse
149
1. Click Check
for Updates
2. Right-click the
blue icon, then
choose an option
3 (Optional) If the Check for Updates button changes to Install update now, you can:
Read the release notes for the new version (right-click the blue icon and select View changes).
Install the update (right-click the blue icon and select Install update now).
NOTE You can run THOR without an Internet connection, however certain features will not be available.
(E.g. Communicating with units on the network or software updates.)
NOTE If you have set up a THOR desktop icon, you can start THOR by double-clicking the icon.
2.3 LICENSING
2.3.1 LICENSE INFORMATION
Information about your license appears in the License Information window. From this window, you can enter a
new License Key, refresh your license to view information about Enabled Features (license dependent).
Advanced
features appear
depending on
the active
license
3 To refresh your license, click on the Refresh License button, (or change the License Key).
Expired licenses will open a warning message. You will be able to continue using THOR’s standard
features however all Advanced functions will be disabled until the license has been renewed.
This is a legal agreement between you (either an individual or an entity) and Instantel, Stanley Black &
Decker, Inc. By clicking the I accept the agreement button or taking any step to install or use the software
product, you are agreeing to be bound by the terms of this agreement. If you do not agree with the terms
of this agreement, click the I do not accept the agreement button.
The software which accompanies this license agreement (the “Software”) is warranted against defects in
materials and workmanship and shall perform substantially in accordance with the accompanying written
materials for a period of one year. Should a product fail within this period it shall be repaired or replaced
free of charge. Instantel does not warrant that the operation of the Software will be uninterrupted or error-
free. Instantel does not represent that any product will prevent bodily injury or damage to property. This
warranty is void if the product has been dismantled, altered or abused in any way. EXCEPT FOR THE
WARRANTIES SPECIFIED IN THIS AGREEMENT, THERE ARE NO WARRANTIES OR CONDITIONS,
EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OR CONDITIONS OF
FITNESS FOR PURPOSE, MERCHANTABILITY OR FUNCTION OF THE SOFTWARE FOR A
PARTICULAR PURPOSE AND THOSE ARISING BY STATUTE OR OTHERWISE IN LAW OR FROM A
COURSE OF DEALING OR USAGE IN TRADE. USE OF THE SOFTWARE IS ENTIRELY AT YOUR SOLE
RISK.
INSTANTEL WILL NOT BE LIABLE FOR: (A) HARM TO OR LOSS OF YOUR RECORDS OR DATA; (B)
ANY CLAIMS AGAINST YOU BY THIRD PARTIES; OR (C) ANY DIRECT, INDIRECT, SPECIAL,
INCIDENTAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES, INCLUDING BUT NOT LIMITED TO
LOST PROFITS, LOST BUSINESS REVENUE, OR FAILURE TO REALIZE ON SAVINGS, EVEN IF
INSTANTEL HAS BEEN ADVISED OF THE POSSIBILITY OF THESE DAMAGES. THIS LIMITATION
APPLIES TO ALL CLAIMS BY YOU IRRESPECTIVE OF THE CAUSE OF ACTION UNDERLYING THE
CLAIM BUT NOT LIMITED TO BREACH OF CONTRACT INCLUDING FUNDAMENTAL BREACH, TORT
INCLUDING NEGLIGENCE AND MISREPRESENTATION; AND BREACH OF STATUTORY DUTY. IN NO
EVENT SHALL THE LIABILITY OF INSTANTEL EXCEED THE COST OF THE SOFTWARE.
This agreement allows you to use the Software on one computer and make one copy of the software solely
for backup purposes. You must reproduce on any such copy all copyright notices and any other proprietary
legends on the original copy of the Software. You may not decompile, reverse engineer, disassemble, or
otherwise reduce the Software to a human conceivable form.
This agreement gives you limited rights to use the Software. You do not become the owner of, and Instantel
retains title to, the Software, and all copies thereof. All rights not specifically granted in this agreement are
specifically reserved by Instantel.
Instantel may terminate your license if you breach any term of this agreement and do not remedy the breach
within 10 days written notice of the breach. Upon termination, you will immediately delete the Software from
the computer in which it is installed and return all copies of the Software to Instantel.
This agreement constitutes the entire agreement of the parties with respect to the subject matter and
supersedes all prior agreements, understandings, negotiations and discussions, whether oral or written,
between the parties. This agreement will be governed by the laws of the Province of Ontario excluding
the law of conflicts and excluding the United Nations Convention of Contracts for the Sale of Goods. You
agree to attorn to the exclusive jurisdiction of the courts of the Province of Ontario which will have
exclusive jurisdiction over matters in respect of this agreement.
Directly
Use a serial, USB or Ethernet cable to create a direct physical connection between the computer
and the unit.
(For cable/unit compatibility see section 3.1.1 Direct Link to a local Computer on page 27.)
Remotely
Use a cellular modem to create a remote connection between the computer and a remote unit.
THOR can control most settings (see note) on the unit. Event data can be downloaded to THOR.
NOTE: Some settings can only be accessed on the physical unit: Ex. The Auxiliary “modem power”
port must be configured on the Micromate unit. ACH baud rate, ACH session time out. For more
information see the unit’s respective Operator’s manual.
Minimate Pro
Connect the Minimate using the default Ethernet cable provided or with an optional serial cable.
(a USB to serial adaptor can be ordered separately from an Instantel dealer.)
WARNING
1 Connect the auxiliary connector to the auxiliary port located Forcing these
on the side of the unit. quarter-turn
connectors
2 Attach the other end according to the available connections on the computer: may damage
a. Serial cables connect to a serial port on the computer them.
b. USB to serial adaptors connect to the USB port on the computer
c. Ethernet cables connect to an Ethernet port on the computer
Micromate
Connect the Micromate using the default “PC to USB” cable.
1 Connect the square end of the USB cable to the Micromate’s PC port.
2 Connect the rectangular end of the USB cable to the computer’s USB port.
NOTE The unit and the PC will beep, indicating that Windows has detected the Micromate.
NOTE The Micromate must be connected and powered on to access Micromate settings or upload data
to the computer.
Setting up modem communications requires three steps. Once completed the unit should be connected
to the computer and ready to upload event files from the units to the computer.
Only use
1 Configure serial communications on the monitoring unit Instantel cables.
a. see the user manual for the specific unit.
2 Configure the remote cellular modem
a. Configure the modem before taking it into the field to connect with the remote unit. If the
modem is used in parallel with third-party software, make sure it is configured to be
compatible with THOR. Then try a test call.
NOTE Configuring the modem depends on the manufacturer and model. Refer to the instructions provided with
the modem. For the latest information on modem deployment, consult Instantel’s online support site.
Modem relay
setting power
ON is not
accessible via
THOR.
LABEL CONNECTIONS
The unit (Minimate Pro or Micromate) connects to a modem through a serial connection.
The modem uses the TCP/IP protocol to connect to a network.
The network uses the TCP/IP protocol to connect to a computer running THOR.
1 Touch the Auto Call Home short cut icon on the Micromate touch screen.
2 Enable Auto Call Home. Set the Session Time Out to 10 minutes, Modem to Generic and Modem
Baud rate to 115200.
For modem
connected Unit
NOTE Session Time Out is used to exit Auto Call Home and return to monitor mode. Use this feature to set
the maximum amount of time the Micromate will NOT be in monitor mode.
Instantel recommends using the tested and fully compatible Sabrent CB-FTDI USB to Serial Cable to
connect the Micromate to the modem.
The Micromate units are tested and fully compatible with Sierra RV-50, LS-300, and GX-400 modems.
Example of the GX-400 modem, using the AirLink Ace Manager software to configure the modem.
When setting the TCP idle time-out value, use the following values based on your expected usage.
• If you remotely configure the Compliance Setup or Schedule of the unit, we recommend
using 10 minutes to allow for the TCP idle time that occurs between the time the
Compliance Setup window is opened in THOR and the time the new configuration is sent to
the unit.
• If you do not remotely configure the Compliance Setup and Schedule of the unit, we
recommend using 65 seconds to allow for TCP idle time that occurs when an Auto Call
Home session executes a Delete All on the unit.
Example parameters
for the GX-400
modem, using Sierra’s
AirLink Ace Manager
software to configure
the modem.
NOTE As the
modems are third
party components
their firmware may
occasionally change
along with their user
interface. See the
latest white paper or
FAQ for compatible
modems and their
setup configuration.
Manually THOR will automatically add a unit if the unit initiates an Auto Call
Using Auto Discovery Home session, and a filter exists recognizing the unit’s serial number.
Blastmate and Minimate Plus units may connect in this way to THOR.
See section 6.2.2.2 Filters & Actions on page 142
*If the WAN blocks broadcasts to the LAN where THOR resides, Auto-Discovery will not be available.
NOTE Any event data that the unit collected will remain in THOR even if the unit is deleted from THOR.
2. Click the
Add button
or right-click to
add/edit a unit
3. Fill in fields
FIELD FUNCTION
Name A unique name for the unit.
Unit Description
A description or note that is useful for identifying the unit.
(Optional)
The exact serial number of the unit. Without the correct serial number, THOR
Serial Number
cannot communicate with the unit.
The model of the unit. Without the correct model type, THOR will not
Unit Type
communicate with the unit.
Serial
In the Port field, Enter the COM port. Minimate Pro and Minimate Plus units
must also have their communication speed defined.
Baud Rate:
Minimate Pro: choose between 9600, 38400, 115200.
Minimate Plus: must be set to 38400.
Communication TCP
When using a modem, in the IP Address field, type the public, static TCP/IP
address configured on the modem. THOR supports IPv4 and IPv6 address
formats. In the Port field, type the TCP/IP port configured on the modem.
For Minimate Pro units connected to a network, in the IP Address field, type
the TCP/IP address configured on the Minimate Pro.
In the Port field, type 9034.
Domain Name
The domain name of the unit. (E.g. Instantel.com)
Disabled
Do not use this function
Use Preferences Settings
Check monitoring
unit automatically Apply the same settings as those defined in Preferences
1. Click the
2. Click the Unit Preferences tab
Connection button
4. Click Apply
3. Select a unit
from the list
3c. right-click to
add a New Unit
DASHBOARD
WARNING THOR will only function properly with compatible units. To upgrade a unit please contact
Instantel at [email protected].
This can be useful for example to update the firmware, refresh, or disconnect multiple units in one shot.
This dashboard appears when you select multiple units from the list of available units.
Multiple units
selected from
the list
If a unit’s last known connection status was disconnected, a manual refresh will try to re-establish a
connection and then retrieve the unit’s status.
3. Click Refresh
2. Select a
unit in the list
ICON
STATE MEANING
The monitoring unit: SERIES MINIMATE MICROMATE
III PRO
Connected and Associated with the current project
monitoring Communicating with THOR
Connection monitoring Last known state was connected and
automatically as defined in monitored
preferences refresh rate. The connection is automatically monitored
Last known state Associated with the current project
connected and Not communicating with THOR
monitored Last known state was connected and
Not monitoring monitored
automatically The connection is not currently monitored
Connected Associated with the current project
Connection monitoring Communicating with THOR
automatically as defined in Last known state was connected
preferences refresh rate. The connection is automatically monitored
Last known state Associated with the current project
connected Not communicating with THOR
Not monitored Last known state was connected
automatically The connection is not currently monitored
Disconnected Associated with the current project
Connection monitoring Not communicating with THOR
automatically as defined in Last known state was disconnected
preferences refresh rate. The connection is automatically monitored
Last known state Associated with the current project
disconnected Not communicating with THOR
not monitored Last known state was disconnected
automatically The connection is not currently monitored
You can choose to check the connection and status of all units automatically or select individual units to
check automatically.
WARNING Refreshing unit status automatically
can use a significant amount of data, as the
units are in constant communication with THOR.
2. Define refresh
intervals
3. Click Apply
NOTE The Auto Discover Connected Units function will monitor the computer’s ports and detect any units
that get connected to the computer. This is only to establish a connection. The following two settings
determine the Dashboard display’s refresh rate of the unit status. This means, for a refresh rate of 1
hour, if the unit’s status changes within the hour, THOR will only reflect this change after one hour, or
if the user chooses to refresh manually.
NOTE Unit level settings always override the general preferences settings in section 3.4.2.1.
1. Click the Unit tab
3. Click Edit
2. Select a
unit in the list
5. Select Use
Specific Settings
4 Select Use Specific Settings and define the refresh intervals for the two fields.
The disconnect feature will not stop a unit that is actively calling home. In this
case you will see that not all units are disconnected, and you must try again.
4. Click Delete
3. Click disconnect
2. Click a
monitoring
unit in the list
DASHBOARD
Idle, the unit A Schedule is The unit is The unit is The unit is The unit is
is not running, but monitoring in monitoring in monitoring in monitoring in
currently the unit is Waveform Waveform Histogram Histogram
monitoring. not currently mode. Manual mode. Combo
monitoring. mode. mode.
NOTE The icon updates based on the refresh interval defined in THOR.
See section 3.4.2 Check Unit Connection and Status Automatically on page 40.
NOTE Minimate Plus and Blastmate III only display the active state of monitoring, other monitoring modes
are not shown in the icon for these units.
1 Click the Monitoring Mode icon (if it is in idle mode, it will ask to start. If it is monitoring, it will
ask to stop)
2 In the confirmation dialog box, click OK.
The icon will change to reflect the new Monitoring Mode of the unit.
When the unit is no longer monitoring, the icon will return to Idle.
3. Click a
connected unit
in the list
5 Enable the checkboxes of the channels to include and click the Check button. (A sensor
diagnostic begins and shows the results in the window.
3. Click a unit
in the list
3. Click a
connected unit
in the list
4. Click the
Current Operator
button
5 To delete an operator, click the X icon next to an Operators cannot be deleted when
operator’s name in the Available Operators list. in use on actively connected units.
5b. To add an operator: Type a name for the operator and
click the Add button.
6 Click the right blue arrow to assign an operator to a unit.
6b. Click the left blue arrow to remove an operator from a unit.
7 Double click a name to assign an operator as the “Active Operator” and click Apply and Done.
8 The Dashboard reflects the new active operator. If the active operator is removed, the
Operator field will record “Operator”
(blank for Minimate units).
8. The new
active operator
3. Click a
connected unit
in the list
5. Type
Owner text
4. Click Firmware
Version
5 Click the Update button and then click Done to return to the Unit Dashboard.
Multiple Units
1. Select
Dashboard
multiple units
2. Click
Firmware
update icon
2 Click on the Firmware update icon. THOR will provide a status summary of the available updates for
units, including their current firmware version and any updated firmware version that is available.
3 Click Update, then click Done to return to the Multi-Units Dashboard.
3. Click Update
and then Done
Available
updates
Start monitoring
Stop monitoring
Self-check
Auto Call Home
Online units can be programmed to act at any time. Schedules can be saved and transferred to units of
the same type.
E.g. The schedule from one Micromate can be sent to five Micromate units provided their Setup files are
the same. Micromate schedules are not compatible with Minimate schedules and vice-versa.
Units with daily schedules will look at previous activities on that day. Units with weekly schedules will
look at the activities scheduled earlier in the week to determine their monitoring state.
If an activity on the schedule is Self-Check or Auto Call Home, the unit will search for previous activities
to find a “Start Monitoring” action. If found it will start to monitor using the compliance setup and the
unit’s Auto Call Home configuration. If “Start Monitoring” action is not found in the schedule, then the
unit will enter into a Scheduler Running state until it reaches the next defined action in the schedule.
When a unit is monitoring due to a schedule and it reaches a Start Monitoring event, the unit will stop
the current monitoring session, run any Auto Call Home actions, load the compliance setup and continue
monitoring.
NOTE If the Call Home After Event Recorded checkbox is disabled, a unit running a schedule will not call
home after an event occurs. The unit will only call home if there is an Auto Call Home entry in the
schedule.
Disabled: a unit running a schedule will stop monitoring during an Auto Call Home session that was
triggered by an event. (This does not apply to Auto Call Home sessions triggered from a schedule. Only Auto
Call Home sessions triggered because Auto Call Home is enabled on the unit and an event occurred.)
Enabled: if an event occurs, the unit will continue to monitor during the Auto Call Home session. The
monitor log will not be copied, events will not be deleted, and time will not synchronize at the end of
the Auto Call Home session.
When performing a scheduled Auto Call Home session, (not an Auto Call Home session due to an event
occurring) monitoring will stop and complete any in-progress events. This allows all events for that time
period to be transferred during the Auto Call Home session, and for events to be deleted from the unit,
Auto Call Home on unit: Records events + transfer data, no stopping to monitor.
Scheduled Auto Call Home session: Stop monitoring + transfer data (or delete events, or synchronize)
E.g. Monitoring in Histogram Combo mode, transfer data every six hours, daily, delete events, copy the
log and synchronize time once a day. Do the following:
Self-check is a diagnostic tool that performs a variety of tests on the unit. For information collected by a
self-check, see the operator manual included with the monitoring unit.
NOTE Before creating a schedule, set the workday range (Start time / End Time), this is purely to help in
planning visualization, actions outside of these times can still work.
E.g. The workday starts at 8:00 AM and ends at 5:00 PM. The time grid will display 8:00 AM to 5:00 PM.
If an action is set up for 7:00 AM, that action is still scheduled and will process.
3c. Delete an
2. Click Manage Schedules existing Schedule
4 Define the Schedule’s Name, Description, and the Unit Type. (Micromate or Minimate Pro).
5 Define the range for the calendar display (Start Time and End Time).
6 Select Day to setup actions on a daily routine (E.g. Start at 10:00 and Stop at 14:00).
Select Week to set up actions on a weekly routine (E.g. Self-Check or Auto Call Home every
Monday at 8:00 and Friday at 17:00).
7 To create an action, double-click in a time slot.
8 Select the appropriate Action and the Unit Setup. (A Unit Setup must exist, either create one
first or download one from a unit.
9 (Optional) To repeat the schedule, enable the Repeat Daily / Repeat Weekly checkbox.
10 Repeat steps 7-8 until all actions are added.
NOTE Right-clicking an interval can facilitate edit, delete, copy and paste actions.
5. Define the
Calendar range
7. Double click a
6. Define Day &/or timeslot to create
Week actions an action
NOTE Saving a schedule will only store it on the computer, it must still be sent to the unit and enabled for
the schedule to take effect.
3. Select a unit
Schedules can only be loaded and sent to units that are communicating with THOR. The units must be of
the same type. (Micromate schedules cannot be sent to a Minimate Pro, and Minimate Pro schedules
cannot be sent to a Micromate.)
NOTE A schedule’s setup file must coincide with the hardware used. This means if the Setup file specifies a
microphone, but no microphone is connected to the unit, an error will be generated.
NOTE After sending a schedule, you must enable the schedule for it to run.
NOTE Loading a schedule to THOR does not remove it from the unit.
NOTE If a Start Monitoring event on the schedule refers to a compliance setup that is not available, a
warning icon is displayed in the Start Monitoring block on the schedule.
Enabled Disabled
NOTE Clicking the icon in the Scheduler section will not enable or disable the scheduler.
You must click the word Enabled / Disabled:
NOTE Clicking the icon in the Scheduler section will not enable the scheduler. You must click the word
Disabled and see it toggle to Enabled.
4 Click the Monitoring Mode button.
If the last item on the schedule was Start Monitoring, the Monitoring Mode icon will display
the current monitoring mode:
(Waveform, Waveform Manual, Histogram, or Histogram Combo).
Otherwise, the Monitoring Mode icon will display Scheduler Running.
4. Click Monitoring
Mode
3. Click Disabled
Unit Setup files can be created, edited and used as templates for other units. Saving unit settings for
later use facilitates switching between configurations. Once created in THOR they simply need to be
loaded into the unit.
E.g. A Minimate Pro operating on a pile driving project (using Histogram mode) is moved to a blasting
project. In this case, the unit set up with waveform parameters would be loaded into the unit to adapt
its monitoring for blasting.
Setup files can be sent to any unit of the same type (Minimate Pro or Micromate). The same unit setups
can be used on multiple units.
E.g. Applying a single unit setup to three Micromate’s used to monitor the same series of blasts at a quarry.
NOTE For one unit’s setup file to work without errors in another unit, they must have the same active
channels and sensors. This means a Unit Setup with an attached microphone will cause an error with a
unit with no microphone or with a different microphone.
Unit setup files are managed remotely through THOR resulting in no interruption of onsite event monitoring.
The same settings are accessible through the Micromate or Minimate Pro interface (see their respective
user manual).
NOTE Some settings are dependent on the chosen Recording Mode: Waveform, Waveform Manual,
Histogram, or Histogram Combo. Ex: Waveform does not set an interval. Histogram does not set the
record time or record stop mode.
The setup file is composed of 5 parts, shown here for a quick overview. These parts can collapse for ease
of use. The available fields vary depending on the selected options. (Micromate settings are different from
Minimate Pro settings)
All components are described in detail in the following tables.
Condensed View
Micromate
units
Minimate Pro
units
(offers some extended
functionality)
Setup type You must have an extended license to use the advanced features.
Advanced It offers more possibilities to define the active sensors per channel.
(Only available for Minimate units.)
Record 1 - 90
When an event is triggered the unit will record for this defined length of time
Time seconds
Auto Stop 1-10 When in Record Stop Mode – Auto Record: Recording stops a specified period
after seconds after the event activity falls below the trigger level.
DIN 1-80 Hz
Geophone Complies with the DIN 45669-1 Class I standard.
Sensor
ISEE Linear Records air overpressure.
Microphone Frequency range: 2 – 250 Hz, Amplitude 2 – 500 Pa, (88 – 148 dB)
Sensor Records noise. Frequency range: 10 Hz – 20 kHz, Amplitude 30 – 140 dB
Both Weighting A or C
Micromate Sound Level
Response Slow/Fast
& Minimate Microphone
LN1 Statistical noise level as a percentage
LN2 Statistical noise level as a percentage
Use the selected sensor as a trigger source. (once triggered,
all channels will begin to record data) When enabled it will
Enable Trigger Checkbox
send a warning signal to the Auxiliary port (if the trigger level
is surpassed)
A defined threshold before monitoring can begin. This should
be set high enough to prevent monitoring noise and low
Trigger Level mm/s
enough to catch all events. (Histogram Combo mode triggers
will initiate waveform recording)
Alarms create a visual, audio or other notification based on the
trigger level set for warnings/alarms. Remote alarm controllers
Enable Alarm Checkbox
can set the alarm levels as part of the compliance setup. When
enabled it will send an alarm signal to the Auxiliary port.
Alarm Level mm/s A defined threshold before an alarm is sent.
Right-click
options
When you add/edit a unit setup file, don’t forget to send the file
to the unit! It will automatically become the active setup file.
see Transferring Setup Files on page 71.
NOTE Unit setup files can only be used on units of the same type, with the same environments.
(Micromate setup file for Micromate’s, Minimate Pro setup file for Minimate Pro’s.)
3. Select a 6. Select a
Unit or Unit or
5. Select a setup multiple multiple
file from the list units units
NOTE Once a setup file is loaded into THOR, it will appear in the Setup files list, ready to edit. If the setup file
has a name conflict, you must decide to overwrite the existing file or rename it.
Projects link event data from different units. Once linked, all events downloaded from the units will
appear in the specific project folder.
Project folders are accessible from the Projects & Events tab under the Manage Events icon or
Manage Projects icon. New projects require a unique name. Each project folder can contain numerous
monitoring units. Units can be assigned dynamically to existing projects.
(For more information, see section 3 Managing Monitoring Units on page 25.)
Units not assigned to any active projects are automatically assigned to the default catch-all project. (The
default project cannot be deleted.)
Projects are a new
concept introduced in
THOR version 1.0.
Projects are particularly useful when events:
Example of how two projects can organize data from three Micromate units:
Panel 1: A user monitors “Quarry A” with two units and “Building Site B” with one unit.
Panel 2: In THOR, the user creates one project for “Quarry A” and one project for “Building Site B”.
Panel 3: Then the user adds the two units installed at the quarry to the “Quarry A Project” and one unit
at the building site to the “Building Site B Project”.
Panel 4: The units collect event data.
Panel 5: When the units upload their event data, the data will automatically appear in the
corresponding project.
Panel 6: Event data becomes accessible within each project.
NOTE Event data remains with the project even after a unit is re-assigned to a new project.
See section 4.4.1 Assign a Unit to a Project on page 80.
NOTE Archived projects cannot be edited apart from their project description.
see section 4.5 Archive and Delete Projects on page 82.
1 Click the Projects & Events tab
2 Click the Manage Projects button (or right-click on a project in the Manage Events section)
3 Select a project from the list
4 Click the Edit Project button
5 Configure the Project level settings (these override the Global Preferences)
6 Click OK (in the confirmation dialog box click OK a second time)
1. Click the Projects & Events tab
2. Click Manage Projects
3. Select a project
from the list
5. Configure the
Project level settings
6. Click OK
2. Right-click on
a project and
click Edit Project
3. Choose between
Use Application Preferences Credentials
and Use Project Specific Credentials
4. Choose between
Use Application Preference Language
and Use Project Specific Language
NOTE Units previously assigned to a project, are disassociated and reassigned through this procedure to the
newly chosen project.
3. Select a project
from the list
To remove a unit from a project, follow the same procedure as when adding a unit, this time instead of
selecting, deselect the units (they will turn grey).
Deleted projects are permanently removed from THOR, while archived You cannot archive or
delete the default project
projects can be reactivated. Archived projects will maintain their settings
and event information.
ARCHIVE DELETE
If the project may become active again If the project will never be re-activated in the
sometime in the future. future.
If you never need to view the collected event
To view the event data sometime in the future.
data again.
When a project is archived, a grey icon is displayed for any units that were assigned to it and had events
downloaded to the project. Units assigned to archived or deleted projects are automatically reassigned
to the default project.
NOTE Any unit that has been assigned to the default project will NOT be reassigned automatically to a
project if that project was archived and reactivated.
3. Select one or
multiple projects
from the list
THOR can:
1. View events
2. Copy events to your computer
You can also create reports on events. For more
3. Delete events
information see section 5.8 Monitoring Logs
4. Group and filter events
5. Print and export events
6. Export events list
When event data is loaded into THOR, if the unit is not assigned to a project, the data will appear in the default
project. (To set up a project that includes related events (E.g. on a single job, or at one location.) see chapter 4
Project Setup and Management on page 73.
USE… TO …
Access external event file data offline. For event data that
has already been transferred to a computer or USB device.
Import Event Files to THOR
See section 5.3 on page 88.
(Note: You cannot import event data while the unit is monitoring.)
THOR can display event data from a physically connected or remotely connected unit. To view events of
a unit that is not connected, you must create a local copy (at some point when the unit is connected,
using the Copy Events from a Unit function) of the events on a local computer.
NOTE Events can only be imported into an active project (not archived projects).
NOTE Files and folders other than events are not imported.
The Import Event Files’ icons show the status of the files. Hover the cursor over the icons for status details.
ICON MEANING
File was imported successfully
File not imported
Invalid event file
6. Choose the
Project where
the Event files
will be imported
into
5 Repeat Steps 3-4 until all the files to import appear in the list.
6 Choose the Project where the Event Files will be imported into.
7 Click Import and then Done.
Unit: The event file is stored on the unit and is being viewed temporarily in THOR.
Local: A copy of the event file has been downloaded to the local computer and can be viewed
permanently in THOR.
3. Click a
project 5. Right-click an event to copy
Tip: To select multiple events, hold down CTRL on the keyboard and select the events.
4. Right-click a
monitoring unit
5. Click Print
3. Click a
project arrow
4. Click an Event
NOTE Multiple events will be printed as individual reports. To customize event reports or add a custom logo
before printing see section 5.9.3.1 Printing an Image on Reports on page 124.
Example of a printed
event in the form of a
report. This is fully
customizable, see
section 5.9 Reports
on page 113.
FEATURE DESCRIPTION
Show only certain columns and hide others. Restore hidden columns at any time.
Viewing
For more information see section 5.7.1 Preferences for Viewing Events on page 96.
Sort columns to make events appear in a different order. Use column sorting to
show data with ascending or descending values, (alphabetical order or reverse
Sorting
alphabetical order).
For more information see section 5.7.6 Sort Events on page 106.
Find and work with a subset of data. Filtering data will only display rows that meet
Filtering certain conditions. Rows that don't meet these conditions are hidden.
For more information see section 5.7.5 Filter Events on page 102.
Only the event data that was registered by the unit while it belonged to the project will be displayed.
Events whose location is Local are displayed.
Events whose location is Unit are not displayed.
(In some cases, event data exists from the same unit while it was assigned to another project. Those events will not
appear in the currently selected project).
When viewing a UNIT
Automatic Event View is enabled: All events are displayed regardless if their location is Local or Unit.
Automatic Event View is disabled: Only events whose location is Local are displayed.
Viewing the data will not automatically upload it to the computer. For this you must either:
3. Click on a project
These events
are stored on
the unit
NOTE If an event resides on the computer and has not yet been deleted from the monitoring unit, the event
will appear twice in the events list, once as Unit, and once as Local.
Tip 2: Drag a
column to the
left or right
NOTE When columns are rearranged, their relative positions are stored at the project level. This
means that all units within the project will display the same column arrangement.
Every project contains its own column arrangement independent of the other projects.
4 Expand the areas of interest by clicking on the drop-down arrow. You can also select
everything by checking the Select All Columns field or deselect everything by checking the
Deselect All Columns field.
5 Check the columns to appear in the Event Table. If there are fields that do not fit into the
window view, use the scrolling bar on the right side or click on the Show More button.
NOTE At least one field must be selected. In the case when Deselect All Columns is selected, the Apply
button will remain grey until a field is selected.
E.g. Events grouped by the Operator column for values containing "Ebba" are grouped together.
Ex: Grouped data by the Operator column: all data recorded by Ebba appears together. If the Storage
column is added, the data recorded by Ebba will appear together and within the Ebba group. Events
from Storage and the Events from Unit appear separately.
To remove column groupings, hover the mouse over the column header in the Grouped by area and
click the X button that appears.
You can also sort any column that is grouped to display the rows by ascending or descending values.
Click the arrow in the header button to change the sort order.
Click the arrow to change
the sort order.
Simple Filters
E.g. The Operator field is used to filter
with possible choices (H, LOG, W) if LOG is
selected, then only the events with LOG
files will be displayed.
Complex Filters
UM6008
UM1009
MP12528
MP99900
OPERATOR RETURNS
Data that matches the alphanumeric value.
Is equal to Example: filtering Serial No. with Is equal to UM6008
returns: UM6008
Data that does not match the alphanumeric value.
Example: filtering Serial No. with Is not equal to UM6008 returns all entries with
Is not equal to
a value other than UM6008 in the Serial No. field.
returns: UM1009, MP12528, and MP99900
Data that begins with the alphanumeric value.
Example: filtering Serial No. with Starts with UM will return all entries with a
Starts with
value that begins with UM in the Serial No. field.
returns: UM6008 and UM1009.
Data that ends with the alphanumeric value.
Ends with Example: filtering Serial No. with Ends with 8
returns MP12528 and UM6008.
Data that contains the alphanumeric value in any position.
Contains Example: filtering Serial No. with Contains 00
returns: UM6008, UM1009, and MP99900
Data that does not contain the alphanumeric value.
Does not Example: filtering Serial No. with Does not contain 125
contain UM6008, UM1009, and MP99900 are returned.
MP12528 is not returned because 125 is found in MP12528.
Data with a value that is part of the typed alphanumeric value.
Is contained in Example: filtering Serial No. with Is contained in 9MP125289
returns: MP12528 (because MP12528 can be found within 9MP125289)
Data with a value that is not part of the typed alphanumeric value.
Is not Example: filtering Serial No. with Is not contained in 9MP125289
contained in returns: UM 6008, UM1009, and MP99900
(because they are not found within 9MP125289)
OPERATOR RETURNS
Fields that contain no data.
Example: filtering Serial No. with Is empty
Is empty returns: no data (because events always include the serial number of the unit
that recorded them. Alternatively, filtering Trigger with Is empty
returns: all events that were recorded without using a trigger.
Fields that contain any data.
Example: filtering Serial No. with Is not empty
Is not empty
returns: all data (because events always include the serial number of the unit
that recorded them)
Data that has a lesser value than the typed alphanumeric value.
Is less than Example: filtering Serial No. with Is less than UM6008
returns: UM1009, MP12528, and MP99900. (M appears before U in alphabetical order)
Data that is less than or equal in value to the typed alphanumeric value.
Example: filtering Serial No. with Is less than or equal to UM1009,
Is less than
returns: UM1009, MP12528, and MP99900
or equal to
(M appears before U in alphabetical order, UM6008 is not returned because it
has a higher value than UM1009)
Data that has a greater value than the typed alphanumeric value.
Example: filtering Serial No. with Is greater than MP12528,
Is greater than
returns: UM1009, UM6008, and MP99900
(U appears after M in alphabetical order)
Data that is greater than or equal in value to the typed alphanumeric value.
Is greater than Example: filtering Serial No. with Is greater than or equal to MP99900,
or equal to returns: MP99900, UM1009, and UM6008
(U appears after M in alphabetical order)
Fields with data entries of "null".
Example: filtering Serial No. with Is null,
Is null returns: no data (Events always include the Serial No. of the unit that recorded them)
Alternatively, filtering Operator with Is null,
returns: all events recorded with no active operator.
Fields with data that does not equal "null".
Example: filtering Serial No. with Is not null
returns: all events (Events always include the serial number of the unit that
Is not null recorded them.
Alternatively, filtering Operator with Is empty
returns: all events recorded when there was no active operator
Filters can be combined. This means that multiple columns can be filtered at the same time.
Example: To find all the Histograms collected by Ron, filter the Type column for Histograms and the
Operator column for Ron.
Tip 1. To add complex filtering options, use the section “Show rows with value that” In this section, you
can use logical operators for comparisons (see the table below describing all options).
Tip 2. To remove a filter, select the filter then click the Clear Filter button.
Tip 3. To use a case sensitive filter, click the Match Case button. (not available for Time/Date functions).
Three sorting states are indicated by the small blue arrow in the column header.
No arrow: The column is not sorted. By default, events are displayed by the
Date/Time column, chronologically from oldest to most recent, with the event
that occurred first appearing first in the list of events.
Arrow pointing up ( ) The column is sorted with the highest number first,
descending to the lowest number. If the column contains text, the text displays
in alphabetical order (A-Z), following the numeric values.
Arrow pointing down ( ) If the column contains text, the text displays in
reverse alphabetical order (Z-A), followed by numeric values. The lowest number
displays immediately following the text, ascending to the highest number.
Example: A column containing the values: CCC, ZZZ, 999, AAA, BBB, 123,
would appear according to their sorting state as follows:
Events sort one column at a time, they will reorder when the header of another column is clicked.
In the Date/Time column, no arrow or the up arrow will show events chronologically with the event that
occurred first appearing first in the list. The down arrow will show events in reverse chronological order.
A chosen sorting will remain on the same computer until changed even after logging out. Logging back
into the same computer with the same user name will keep the same sorting.
3 Select the data fields to include in the exported file by clicking on the column selector icon.
2. Click on a project or
any unit in the project
4 Expand the areas of interest by clicking on the drop-down arrow. You can also export everything
by checking the Select All Columns field.
Export everything
5 Check the columns that will appear in the export file and click on the Apply button. If there are fields that
do not fit into the window view, use the scrolling bar on the side or click on the Show More button.
9. Click Export
Event List icon
6. Drag and drop columns
to reposition them
8 Select the Events to export by clicking on each row using the CTRL/Shift key.
9 Click on the Export Event List icon and select Export Selected Events (or Export All Events).
10 Choose the file format, either CSV or Excel, add an optional comment and click Export.
Monitoring Logs should not be confused with Auto Call Home (ACH) Logs.
• ACH Logs keep track of communications between units and THOR.
• Monitoring Logs keep track of actions that units experience to detect and store vibrations.
For more information about ACH Logs see section 6.4 on page 151.
4. Double-click
a LOG file
3. Expand the project
and select a unit
3. Expand
4b. Right-click and select
the project
Create a Local Copy of
and select
All Event(s) and Log(s)
a unit
To export a file into different file formats (PDF, CSV, XML, ASCII) double-click the LOG file and in the
Tools section, click one of the export options.
Export options
5.9 REPORTS
5.9.1 VIEW
Reports are a convenient way to present event data in a customized format that can highlight important
information with a quick visual representation.
They can have their own company logo, unique title, as well as customized language, graphing scale, and
units. All customizable components are accessible through the configuration side panel. This panel is
accessed by double-clicking on any event that appears in the project Events page.
1 Click the Projects & Events tab.
2 Click the Manage Events button.
3 Click the arrow next to a project (or click a unit in the project to see only that unit’s event.
4a. To view a single report, double-click an event.
4b. To view reports for multiple events, use the Shift or CTRL keys to select up to 100 reports
then right-click and select View Events.
5 Click through multiple reports using the arrow keys. (They will appear in chronological order.)
1. Click Projects & Events
NOTE: When
working with
2. Click Manage Events
multiple reports, the
configuration
settings will apply to
all event reports.
4b. Select multiple events Making changes to
and click View Events an individual report
3. Click a project will only apply to the
arrow or Unit current report.
5. Click through
multiple reports
NOTE:
Advanced event
reports contain
extra channel
information.
All channel graphs will record a marker when using the Crosshair
Tool. Zoom functions will apply to all graphs. Clearing crosshair
markers will remove crosshairs from all graphs.
Synchronize Graphs On
Crosshairs and
zoom are
synchronized
Remove Crosshair All markers on the channel will be erased. If channels are
markers synchronized this will remove all markers on every graph.
To zoom on a waveform graph, first, activate the zoom function by clicking the icon .
Click Zoom On
Then either:
Hold down the left mouse button and select an area of the graph.
Drag the white markers on the grey slider to zoom in on the axis.
Drag the grey slider (left and right) to view the parts of the waveform that are offscreen.
When finished zooming, click the Zoom Off button to zoom out.
1 While viewing a report, turn on the Crosshairs by clicking the icon. It will change to the
Crosshair On icon .
Click to turn
Crosshairs On
2 Double-click anywhere on a graph. (A crosshair is added, with the velocity and exact time. )
Double-click
Click to turn the
on the graph Crosshairs Off
To turn the cross-hair tool off, click the Turn Cross-Hair Off icon.
5.9.2 CONFIGURE
To access the configuration side panel:
3. Click a Project or
Unit within a
4. Double click an
Project
event
Event Report
2 Report Title
Quarry Blasting Site3 September
7 Graphs
Refer to the 8 Show Compliance Graph
following
9 Show Channels
table for
descriptions 10 Scale Each Channel to Its Own Peak
of each 11 Combine Geophone Channels
setting
12 Show Sensor Check
13 Compliance Graph with
14 Show Ponderated Peaks Zero Crossing Freq…
15 Display Geophone Peaks in dB
16 Geophone reference level
17 Sound Monitoring Graph
18 Equivalence level (Leq)
19 LN1 Exceedance level (Default is L10)
20 LN2 Exceedance Level (Default is L90)
FUNCTION DESCRIPTION
Report Configuration for Every project has its own event report configuration. These default parameters are
1
Default Project used when reports are generated automatically (E.g. Using Auto Call Home)
7 Graphs The available options for the graphical display of the report.
Scale Each Channel to Its Adjusts the graph’s scale to enhance the visual representation of the channel’s
10
Own Peak waveform.
If a sensor check was included after the event monitoring, the report
will indicate the status of the sensor check, either passed or failed.
12 Show Sensor Check
This helps to indicate of the sensors were functioning properly
(validating or invalidating the integrity of the results)
FUNCTION DESCRIPTION
See 8
13 Compliance Graph with: Fast Fourier Transform (FFT) – (only for Waveform events) or
Zero-Crossing Frequency – (only for Histogram events)
Ponderation is a weighting of waveform frequencies specifically used for
the French National Compliance standard. Changing the geophone
14 Show Ponderated Peaks reference level will refresh the report viewer and recalculate peaks in
decibels based on the formula: PeakIndB = Math.Abs (20 x Math.Log10(PPV)
+ Reference Level)
this value must be in dB, to calculate the proper value you must first convert
16 Geophone reference level the Reference PPV value, using the following formula:
Reference dB = 20 x LOG (1/Reference PPV)
17 Sound Monitoring Graph Options available when using a Sound Level Microphone
18 Equivalence level (Leq) The true equivalent sound level measured over the time of the recording
LN1 Exceedance level The percent of the recording that was at, or above, the default L10 level.
19
(Default is L10) Example: If L10 = 51.2 dB then 10% of the time recording was above 51.2 dB
LN2 Exceedance Level The percent of the recording that was at, or above, the default L90 level.
20
(Default is L90) Example: If L90 = 42 dB then 90% of the time recording was above 42 dB
FFT reports are for Waveform ground and linear channels only. You cannot perform an FFT on Histogram or sound
events. An FFT report will appear at the bottom of the event report and will be printed on a separate page.
The options for configuring FFT reports are:
Show /Hide the FFT report
Naming the FFT report
Adjusting the FFT frequency range
The slider at 2 Hz. The slider at 315 Hz. Drag the left slider to Drag the right slider to
change the lower limit. change the upper limit.
Double-click
the event or
click View
3. Click a project
arrow or Unit 5. Double-click an Event
5. Change the
Configuration options
NOTE Only one configuration is saved at a time. Any saved configuration re-writes the current configuration.
PDF
XML
Text/ASCII
CSV (Comma Separated Value)
Exporting multiple reports is only available into a single PDF file. They will appear sorted chronologically
from the date and time that the events took place.
1. Click an
export icon
PDF CSV
XML Save
ASCII Save as
The accepted image formats are .bmp, .jpg, .gif, and .png.
1 To save a Report, click either: (You must be in the report viewer, see section 5.9.1 on page 113)
Save or Save as (Saves a report that has already been saved, with a new name)
1. Click Save
or Save as
2. Enter Name
and Description
3 To View the report, along with other reports of that event, click the expand (+) symbol and click the
View icon
4 To Print the report, click on the Print icon
5 To Delete the report, click on the Delete icon (This does not delete the raw data of the event)
NOTE To delete a post-event note, follow the procedure to add a post-event note, and remove the text.
1 Click the Projects & Events tab.
2 Click the Manage Events button.
3 Click a project’s arrow.
4 Click an event. (To select multiple events, use CTRL and click additional events).
5 Click the Post Event Notes button.
3. Click a
project arrow 4. Click an Event
THOR calculates the scaled distance based on the distance from the event source divided by the square
root of the weight of the explosives detonated, (as well as factoring in any delays).
THOR’s Scaled Distance files display the estimates graphically to better visualize their effect. The scaled
distance graph can reflect the Square Root, Cube Root, or Air Blast. You can also customize the
percentage of the regression plotline.
The actual value of the scaled distance depends on the units of measure used in the equation,
SD = D/Wr
where the distance D, and weight of charge W, may be expressed in either Metric or Imperial units and r
is either 1/2 or 1/3 depending on whether the square or cube root is used. (Air pressure always uses
cube root scaling.)
There is a correlation between scaled distance and particle velocity. If enough PPV (or pressure) - SD
sample pairs are available, statistical analysis can be used to derive an expression to show this
dependence. It is of the form:
P = H(SD)-ß
Where:
P = PPV is peak particle velocity (or air pressure)
H = Velocity (or air pressure) axis intercept (P when SD = 1)
SD = Scaled Distance
ß = The slope of the curve, (the negative decay exponent)
This is an equation for a curve of the form y = axb. (In the case of air pressure in dB, the equation is of
the form P = a+b logSD where P is pressure.) If the logarithm is taken of both sides, we have
log y = log a + b log x. This gives a linear xy relationship when plotted using log-log scales. Since the
curve is reduced to a straight line, we can perform a linear regression analysis to find its equation. Linear
regression is a statistical tool for determining a line of fit through a distribution of points on a graph.
Linear regression is used to find the equation of a straight line of the form
y = a + bx
a=y-b*x
In the equations above, n is the number of points (or Event PPV, SD pairs) xi and yi are the ith variable in
the set i = 1 to n, and x and y are means of each of the variables in the given set.
A confidence line is based on the "rule of thumb" as a special case of Chebyshev’s Rule. It states that in a
normally distributed large population approximately 68% of the members lie within one standard
deviation of the mean, whereas 95% of the members lie within two standard deviations.
Dowding, Charles H. Blast Vibration Monitoring and Control. Englewood Cliffs, NJ: Prentice-
Hall Inc., 1985.
Federal Register, Vol.48, No. 46, Tuesday, March 8, 1983. Rules and Regulation. Washington,
D.C.: U.S. Government Printing Office.
Newbold, Paul. Statistics for Business and Economics. Englewood Cliffs, NJ: Prentice-Hall Inc.,
1984.
Rosenthal, Michael F. and Gregory L. Morlock. Blasting Guidance Manual. Office of Mining
Reclamation and Enforcement (OSMRE), March 1987.
4. Type a Name
and Description
5. Click Add
button
7. Click Import Events
6. Edit specific
values
6 Type a Name and Description
7 Click the Add button. The event will appear in the list.
8 To edit specific values, click on a column and manually change the value.
9 To Import existing events, click the Import Events button.
12 In the Plot Type field, select a calculation type for the regression line.
(Square Root, Cube Root, Air Blast)
13 In the Plot field, enter a percentage value for the regression line.
NOTE Available file types for exporting will depend on your THOR license.
1 Click the Projects & Events tab.
2. Click Scaled
Distance button 4. Click a Scaled
Distance Report
icon
3. Select a Scaled
Distance file
5. Click Convert
5 Use the Browse button to modify the saving folder location, then click Convert.
3. Select a Scaled
Distance file
4. Scroll down to
the Scaled Distance
Calculator
Calculate the Charge Weight, enter values in the PPV and Distance boxes.
Calculate the Scaled Distance, enter a value in the PPV box.
Calculate the Peak Particle Velocity, enter a value in the Scaled Distance box.
Calculate the distance, enter values in the PPV and Charge Weight boxes.
7. The generated
table according
to entered values
6 To display a Scaled Distance Table, enter values for the Distance, Increment, PPV, and
Table Size, then click Calculate.
7 A table is generated displaying the calculated Charge Weight relative to Distance with
increments as defined by the Increment field.
or at specified times. A unit using ACH can initiate a session to transfer data and execute other actions.
Event data
Monitoring The computer Step 3: uploads to
Step 1: Step 2:
unit calls the identifies Computer computer and
Event Call
destination monitoring executes performs any
Occurs Esablished
computer unit actions other defined
actions
Step 1. The unit’s configuration defines how communications are established when calling a computer.
Step 2. Once ACH is initiated by the unit, the computer identifies the unit using its protocol filters.
Step 3. Once identified, actions are taken during the Auto Call Home session.
Possible Actions:
Copy events (that haven't previously been copied)
For information on ACH and Vision,
Copy monitor logs see section 7.4.5 Send Data to
Delete event data from the unit after upload Vision using ACH on page 166.
Send event data to Vision
Synchronize the date and time
NOTE Though THOR was designed for Minimate Pro and Micromate units, ACH can download event data
from Blastmate and Minimate Plus units. See section 1.1.2 Transitioning from Blastware on page 2.
Minimate Pro units connect to computers directly using serial, serial to USB, and Ethernet cables.
For more information, see section 3.1 Connecting Units to THOR on page 26.
Serial
Serial to USB
Ethernet
Micromate units connect to computers directly using USB to PC and USB to serial cables.
For more information, see section 3.1.1 Direct Link to a local Computer on page 27.
USB to PC
USB to Serial
NOTE For information on modem connection types, see section 3.1.2 Remote Link using a Modem on page 29.
The graphic below illustrates a Minimate Pro or Micromate connected to a modem using a serial
connection. The modem can:
LABEL CONNECTIONS
The network connects to a computer running THOR using the TCP/IP protocol.
The unit
The computer running THOR
THOR can configure ACH on both the computer and the unit with one exception; the Session Time Out.
This must be configured directly on the unit. (See the unit’s User Manual for information on how to set
up its Session Time Out.)
Units store their unique configuration locally and are independent of THOR. THOR has one single
configuration stored on the host computer. You must set up each configuration independently, then
THOR and the unit will use both configurations to determine how to communicate and which actions to
perform during the Auto Call Home session.
Minimate Pro units connecting to THOR over their Ethernet port must configure their TCP/IP to match
the TCP/IP address of the computer running THOR.
3 The Monitoring Mode must be “Idle”. If not, click the button and wait until the unit is ready to
perform configuration functions displaying “Idle”.
4 Click the Auto Call Home Setup button.
5 Activate the Enable Auto Call Home check box and apply the desired settings.
5. Activate the
AHC begins after each recorded event. Enable Auto Call
Home check box
Sets the delay (minutes), before a unit will
call home after a recorded event.
The time it takes for the modem to startup is dependent on the model. ACH will
only attempt a connection after the warm up time (in seconds) has elapsed.
6.2.2.1 GENERAL
Set the TCP Listener Port.
The TCP Listener is the computer’s port that communicates with the unit’s modem (or in the case of the
Minimate Pro with the Ethernet port). When THOR attempts an Auto Call Home, it will poll the TCP port
for network interfaces.
2. Type the
number of the
All Minimate Plus units with an The unit will synchronize its date and time with the
BC Set Date/Time
internal geophone computer.
All Minimate Plus units without
BE
an internal geophone The unit’s schedule is downloaded to the computer.
Send Schedule If you need to send a schedule to Vision for the
All Blastmate III and
B* to Vision automatic Watchdog feature, then this must be
Minimate Plus units
enabled.
MP* All Minimate Pro units
Send Events to Events are copied to Instantel’s cloud-based
UM* All Micromate units
Vision software “Vision”.
The simplest filter is a serial number. Filtering for a serial number will return one single result.
Example: To create a filter for a Micromate unit with the serial number UM2222,
Type UM2222 in the filter field.
Filters can use the wildcard character *. This can be used to represent one or more unknown characters.
Example: Micromate serial numbers begin with UM. Minimate Pro serial numbers begin with MP.
To filter Micromate units type MP* in the filter field.
To filter Minimate Pro units type UM* in the filter field.
THOR uses best match logic when multiple filters are used.
Example: If the following filters were defined: UM12*, UM123*, and UM1234, to find a unit with serial
number UM1234. The UM1234 filter will be used.
3 In the Filter / Description fields, type a name and description of the filter.
3. Type a name
and description
4. Select the
filter’s Actions
WARNING If you enable “Delete Events and Logs from Unit” but disable “Copy Events”.
The events and logs will be deleted without being uploaded.
6.2.2.3 REPORTS
Auto Call Home (ACH) can generate Event Reports and Monitor Log Reports.
Before generating these reports, the Frequency Range and Compliance Graph
must be defined. To generate ACH reports:
Auto Call Home has limited compatibility with Blastmate and Minimate Plus units. The configuration
must be setup within the unit (no configuration within THOR). All generated reports will use the
default preferences as defined in THOR.
Report Folder
When Auto Call Home generates reports from a unit’s event data, they are
generated in four formats:
PDF
XML
Some formats may not be available,
ASCII depending on your THOR license.
CSV
These files are saved to the project’s data folder. The default catch-all folder can be found at
C:\THORDATA\Default Project. It contains all file types and the raw source data from the units that
established an Auto Call Home connection.
4. Click
Edit icon
3. Select the Project
2. Enable Event
Summaries
3 (Optional) The Custom Subject line allows you to personalize the email. (E.g. Quarry Blast site 3)
4 Select the Administrator Email Group, this is the group that receives all messages.
5 (Optional) The other Email groups only receive event files based on their defined preferences.
Event Type: Only sends emails conforming to this recorded event (when empty, all events are sent)
Minimum PPV: Only sends emails of events exceeding this threshold (when empty, all events are sent)
6 (Optional) The Email Monitor Log to Email Group When a Log is Downloaded Using Auto Call Home
check box sends log data in the email. (See note for step 2)
7 (Optional) Send Detailed Report PDF Attached to Email attaches a PDF report to the email.
8 (Optional) Send Auto Call Home errors to the selected email group sends error notifications for
incomplete Auto Call Home sessions to the selected dropdown group.
3. Email
subject line
4. Select who
receives all
emails
5. Add existing
Email Groups
6. Send Log
data with email
7. Send PDF
with email
8. Select who
receives error
notifications
3. Select a Project
When Auto Call Home starts, it will notify the user in THOR regardless of the active tab.
Auto Call Home sessions generate Auto Call Home logs that record session connections, successes/failures,
and transferred data. To view the Auto Call Home logs:
1. Click Auto
Call Home
SETTING RESULT
Start Auto Call Home THOR processes Auto Call Home sessions
Stop Auto Call Home THOR does not process Auto Call Home sessions
NOTE Auto Call Home is installed as a Windows service and runs in the background of the computer.
1 Click the Auto Call Home tab.
2. Click Start to
Activate ACH
Click Stop to
Deactivate ACH
2 In the General area, click the Start or Stop button. The Service will activate/deactivate and
show the status in the lower right corner of the THOR window.
Auto Call Home (ACH) logs record every step of an ACH session:
ACH logs are XML/TXT files, they can be viewed with plain text viewers such as Notepad, and most HTML
editors, THOR also provides an in-app viewer.
To access the Auto Call Home Logs, click on the Auto Call Home tab.
THOR displays the latest logs on the right side of the ACH page. ACH logs update automatically indicated by
a spinning wheel under the status header.
1 Click the drop-down menu in any of the fields to view the available options. Click the calendar icon in
the Custom date/time fields.
1. Drop-down menus
2. Click Apply
5. Sort the results by
clicking on the header
3. List of
log files
By default, events are sorted by the Last Call Home column, in chronological order from most recent to
oldest, with the log that occurred first appearing last in the list.
Arrow pointing down ( ) If the column contains text, the text displays in
reverse alphabetical order (Z-A), followed by numeric values. The lowest
number displays immediately following the text, ascending to the highest
number.
Example: If the Project column contains the values: Quarry West End, Pile Driving East End, and
Downtown Construction, the values would appear as follows:
Logs sort one column at a time, they will reorder when the header of another column is clicked.
In the Last Call Home column, no arrow or the up arrow will show logs chronologically with the log that
occurred first appearing first in the list. The down arrow will show logs in reverse chronological order.
A chosen sorting will remain on the same computer until changed even after logging out. Logging back
into the same computer with the same user name will keep the same sorting.
1. Click the
Preferences tab
NOTE If the General section is not expanded, click the Expand arrow.
2. Define refresh
intervals
3. Click Apply
NOTE The Auto Discover Connected Units function will monitor the computer’s ports and detect any units
that get connected to the computer. This is only to establish a connection. The following two settings
determine the Dashboard display’s refresh rate of the unit status. This means, for a refresh rate of 1
hour, if the unit’s status changes within the hour, THOR will only reflect this change after one hour, or
if the user chooses to refresh manually.
3. Click Apply
4. Send a Test
Email
2 Click the Email Server section
dropdown or icon, and fill in
all the fields.
LABEL DESCRIPTION
SMTP Host Simple Mail Transfer Protocol Host.
SMTP Port Simple Mail Transfer Protocol Port. By default, SMTP uses email port 587.
Send Email From The email address you want to send an email from.
Send Email Name The email name that will appear in the email notification.
SMTP Security Choose between StartTLS/SSL and None. If you select None, the user name and
password are optional, if you use them, they are transferred in clear text, with
no encryption. The default SMTP port for None is port 25.
User name Type the user name for your email account.
Password Type the password for your email account.
All Email Groups Are CC’ed: Everyone in the Email Group receives and sees who received the email.
Bcc’ed: Everyone in the Email Group receives but does not see who received the email.
Send Test Email To Tests the SMTP configuration by sending an email with the entered values.
NOTE If you don’t know your SMTP information, contact your IT department. Some SMTP services do not
allow modifications to the Send Email From and Send Email Name options.
1. Click the
Preferences tab
6. Remove
a recipient
8. Delete an 7. Delete a
Email Group Recipient
5. Add a
recipient 3. Create a
recipient
Section to define Email Groups Section to define Recipients and their emails addresses
3 Create Recipients by entering a Recipient Name and Email Address and clicking on Add. The
new name will appear in the recipients' list. (Repeat this for as many recipients as needed.)
4 Create Email Groups by entering a Group Name and clicking on Add. (Repeat this for as many
groups as needed.)
5 To Add a Recipient to an Email Group, first select the Email Group then select the Recipient and
click the left arrow.
6 To Remove a Recipient from an Email Group, Select the Email Group, then select the Recipient
in the Group and click the right arrow. (This does not delete the Recipient but disassociates it
with that group.)
7 To Delete a Recipient, click the Delete icon next to the Recipient’s name. (You can only delete a
Recipient if they are not associated with a group)
8 To Delete an Email Group, click the Delete icon next to the Email Group’s name.
T-Mobile [email protected]
Virgin Mobile [email protected]
AT&T [email protected]
Sprint [email protected]
Verizon [email protected]
Tracfone [email protected]
Ting [email protected]
Boost Mobile [email protected]
U.S. Cellular [email protected]
Metro PCS [email protected]
NOTE For more information on trial versions or for purchasing a Vision license please contact
[email protected].
1. Enter your
Username and
Password
2. On the Dashboard
Click on Edit Company
3. Click Next to
access Page 2
5. Click Save
Once you have created a Web Service User Name and the Web Service Password on the Vision web
interface, they can be entered in THOR. Once THOR has established a connection it can upload data to
your Vision account.
3 Click Test Connection to verify the web service link and click Apply to register the changes.
1. Click the
Preferences tab
2. Fill in the
appropriate fields
3. Select a Project
2. Select a filter
3. Click the
Edit button
8.1 INTRODUCTION
This chapter describes the optional Advanced module which offers additional features and capabilities
to the THOR program. Features include Advanced Unit Setup Files that can be configured to use sample
rates ranging from 512 sps to 65,536 sps, and the ability to configure virtually any type of sensor that
can connect to the Minimate Pro monitors. The advanced module is enhanced with Software Tools that
allow you to perform waveform analysis regardless of the data source (Series III, Minimate Plus,
Minimate Pro, Micromate). You can perform FFT calculations and determine the frequency of a
waveform at any point with the easy to use Windows® interface.
The Advanced module is designed to easily integrate with the Compliance module. It adds features to
the Compliance module without changing the look and operation of the THOR software, allowing you to
easily begin using the software. It builds on the Compliance module.
This section of the manual explains the new Advanced module features without repeating the
Compliance module information. All operations that are performed using the Compliance module
remain available from the THOR menus.
Advanced License
(with extended features)
Enabled Features
Report Analysis
This feature allows you to perform analysis operations on waveforms
in event reports.
Advanced Unit Setup
This feature allows you to configure Series IV units in Advanced Setup mode.
It also adds the supports of advanced events in THOR.
Advanced Waveform
(AW) Event
Using THOR, you can work with advanced events in the same way as you do with regular events. You
can:
When event monitoring data is loaded into THOR, it is added to a project. Using projects to organize
events is optional, in the absence of any projects, all events are stored in the default project.
The purpose of creating projects is to group related events, such as on a single job, or location.
1.
2.
Name, Description and Unit type
Recording Mode
Expanded View (also on next page)
3. Unit Setup
4. Active Sensors
5. User Notes
Condensed
View
Setup type
You must have an extended license to use the advanced features.
Advanced It offers possibilities to define the active sensors per channel.
(Only available for Minimate Pro units.)
Auto Stop When in Record Stop Mode – Auto Record: Recording stops a specified
1-9 seconds
After period after the event activity falls below the trigger level.
A defined threshold before monitoring can begin. This should be set high
Enable
Checkbox enough to prevent monitoring noise and low enough to catch all events.
Trigger
(Histogram Combo mode triggers will initiate waveform recording)
Use the selected sensor as a trigger source. (Once triggered, all channels
Enable Alarm Checkbox will begin to record data.) When enabled it will send a warning signal to
the Auxiliary port (if the trigger level is surpassed).
Right-click
options
When you add/edit a unit setup file, don’t forget to send the file
to the unit! It will automatically become the active setup file.
see Transferring Setup Files on page 179.
3. Select a 6. Select a
Unit or Unit or
5. Select a setup
multiple multiple
file from the list
units units
NOTE Once a setup file is loaded into THOR, it will appear in the Setup files list, ready to edit. If the setup file
has a name conflict, you must decide to overwrite the existing file or rename it.
3. Expand a project
and select a unit 4. Click an event
CHAPTER 8. ADVANCED THOR FEATURES
The following table outlines the lists of operations THOR can perform on Event data.
OPERATION DESCRIPTION
Scale This operation changes the measurement units and offset value for a waveform. Use this operation to
scale a waveform up or down, depending on the scale factor you select.
Shift This command shifts the currently selected waveform forward or backward on the time axis. The
waveform's absolute time does not change. This changes the waveforms trigger offset.
Signature Hole Signature Hole Analysis Operation is used to create and analyze theoretical blast vibration data based
on your input range of blast timing parameters and a Signature Hole Waveform.
Smooth The Smooth operation is used to average consecutive data points of a waveform.
Sound Calculations Use this operation to recalculate channel data using sound specific criterion.
Subtract Use this operation to subtract two waveforms.
Third Octave The Third Octave is a frequency band tool that has a width that is only 1/3 of the width of an octave,
Band displayed in Hz.
Timeline Overlay Use this operation to show the blast timing on a waveform. This operation applies the timeline file you
select to the channel.
Truncate This command truncates a waveform by removing unwanted sections.
Vector Sum The Vector Sum operation performs a point by point vector addition of selected waveforms. Vector
sums can be calculated for two or three waveforms.
To Add waveforms, select an event from the Event Table and click the Analyze Event icon. In the Preset
Configuration click on the Edit Preset icon or add a new preset. Click the Add New dropdown menu and
select the Add operation. The following dialog box appears.
Select the two waveforms to add together in the first two drop-down menus (Channel 1 and Channel 2).
The waveforms can come from channel data (E.g. Tran, Vert, Long) or from other previous operations.
Click OK.
Channel 2: Vert
waveform
Add operation
performed on
Channel 1 and
Channel 2
To Create a Waveform, select an event from the Event Table and click the Analyze Event icon. In the
Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu. Select the
Create Waveform operation. The following dialog box appears.
Choose a Name to assign to the newly created waveform (E.g. New Waveform).
Enable the Show Graph checkmark to display the result in the form of a graph on the right side of the window.
Click OK.
New waveform
from three
amplitude and
frequency values
To differentiate a waveform, select an event from the Event Table and click the Analyze Event icon. In
the Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu. Select
the Differentiate operation. The following dialog box appears.
Enable the Show Graph checkmark to display the result in the form of a graph on the right side of the window.
Click OK.
Channel Vert
waveform
Vert waveform
Differentiated
To perform an FFT, select an event from the Event Table and click the Analyze Event icon. In the Preset
Configuration, click on the Edit Preset icon and click on the Add New dropdown menu. Select the Fast
Fourier Transform operation. The following dialog box appears.
To perform a Filter operation, select an event from the Event Table and click the Analyze Event icon. In the
Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu. Select the
Filter operation. The following dialog box or one of its variations depending on the filter type appears.
Choose the Channel waveform from the drop-down list to filter for the new waveform.
Filter Weights from File: Performs filtering of frequency weighting from a file containing a weights table
(.fwt file). Select a file from the list, you can also edit the values by clicking on the edit icon, or create
your own by selecting “Create Timeline File”
Weight Table
Enable the Show Graph checkmark to display the result in the form of a graph on the right side of the window.
Click OK.
Click Analyze to create the new waveform.
The following illustration shows an example of the High and Low Cutoff frequencies, with a -40 dB per
decade roll-off.
See section 8.9 Human Exposure Reports on page 217 for a detailed description of this operation.
To perform an integration operation, select an event from the Event Table and click the Analyze Event icon.
In the Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu. Select
the Integrate operation. The following dialog box appears.
Choose the waveform Channel to integrate from the first drop-down menu.
Choose a Name for the new waveform.
Enable the Show Graph checkmark to display the result in the form of a graph on the right side of the window.
Click OK.
Click Analyze to create the new waveform.
Channel Vert
waveform
Integrate operation
performed on
Channel Vert
Input the delay range. This range can be from Delay Min of 1 msec to a Delay Max of 500 msec. The
delay range that was previously calculated is shown to the right of each entry. If you input a new delay
range that is within the previously calculated range, the Interval Analysis will not need to be
recalculated.
Example of the
output from an
Interval Analysis
Choose the waveform Channel to use in the analysis in the first drop-down menu.
Choose a Timeline File from the dropdown menu, if there doesn’t exist one then you can create a new
one by clicking on “Create Timeline File”. The timelines represent the number of shots and delays.
Enter the Number of Rows, Inter Row Delay, Holes per Row, Inter Hole Delay, Decks per Hole, and Inter
Deck Delay values then click on the
Append button. The Timeline Table
will populate. You can select any value
in the Table to edit or delete the
value.
Linear
Superposition
Some recorded waveforms may contain a DC offset. Visually, a waveform containing an offset appears to be
shifted a constant value above or below the X-axis. The system does not automatically remove all offsets as a
user may purposely wish to include them. THOR removes an offset by subtracting the average.
NOTE You can manually adjust the offset using the scale command.
To perform a Remove Offset operation, select an event from the Event Table and click the Analyze Event
icon. In the Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu.
Select the Remove Offset operation. The following dialog box appears.
Select the waveform Channel on which to perform the Remove Offset operation in the first drop-down menu.
Choose a Name for the new waveform.
Enable the Show Graph checkmark to display the result in the form of a graph on the right side of the window.
Click Analyze to create the new waveform.
Offset of 1 in/s
Offset
Removed
To perform a Scale operation, select an event from the Event Table and click the Analyze Event icon. In the
Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu. Select the
Scale operation. The following dialog box appears.
The Result units text box names units
only, it does not check to ensure the
actual waveform result units match the
units named in this box.
To Convert from
acceleration in mm/s2 to
g you would scale the
waveform by 0.0001019
as 9810 mm/s2 = 1g.
To perform a Shift operation, select an event from the Event Table and click the Analyze Event icon. In the
Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu. Select the Shift
operation. The following dialog box appears.
Select the waveform Channel on which to perform the Shift operation in the first drop-down menu.
Enter a Shift Interval in seconds to be applied to the waveform. To shift the waveform to the left, enter
a minus sign (-) in front of the second's input.
Choose a Name for the new waveform.
Enable the Show Graph checkmark to display the result in the form of a graph on the right side of the window.
Click Analyze to create the new waveform.
NOTE You can only shift waveforms within the Events recorded time frame. You cannot shift the Event
outside this time frame.
Shifted 2 seconds
to the left
This tool first creates all the blast Timeline file combinations, based on your input parameters for the
range of different time delays to simulate. Then for each channel in the signature hole waveform, it
shifts the waveform in time according to these timeline files and adds them together to produce a
simulated waveform. These simulated waveforms are conveniently listed in a Signature Hole Analysis
Table with the delays used to create them, the resulting Peak Particle Velocities (PPV), Peak Vector
Sum (PVS), Dominant FFT frequency and the Upper to Lower frequency ratio for each channel. This
table along with all the timeline files and simulations can be exported to a CSV, XML, ASCII, or PDF file.
WARNING This is a simulation tool to help you optimize and improve blast performance, it does
not replace standard blasting practices and experience.
Timeline Files:
A timeline file contains all the time delays, relative to time zero (the actual initiation time) for the entire blast.
These delays are derived from the Inter-Deck delays, Inter-Hole delays and Inter-Row delays. (Shown in
the diagram below representing a Production Shot.) These are the typical delays used in the design of a
blast. They will be used during the signature hole analysis process.
Frequency Ratio:
This is a ratio of the content of the lower frequency range to the content of the upper-frequency range.
The Signature Hole Waveform must be representative of the actual production blast. The hole(s) must be:
Basic assumptions to use the Signature Hole Analysis operation are: that the geology across the
Signature Hole and the Production Blast will remain constant, that each hole will produce identical
vibration results, and that the monitoring unit’s geophone was consistently positioned and correctly
installed.
To perform a Signature Hole Analysis operation, select an event from the Event Table and click the Analyze
Event icon. In the Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown
menu. Select the Signature Hole operation. The following dialog box appears.
NOTE Removing any frequency from the signature hole waveform will also remove them from the
simulation results. It is always a good idea to look at the results before filtering to fully understand the
potential impact of filtering.
Inter-Deck Delay
Enter the Start, End, and Increment values in msec for the
number of Decks per Hole. ie 2 decks and a range from 10 to 20
msec. The increment number allows you to reduce the number of
simulations and quickly narrow in on the desired delays.
Inter-Hole Delay
Enter the Start, End, and Increment values in msec for the number of
Holes per row. ie 10 holes per row and a range from 10 to 30 msec.
Again, the increment number allows you to reduce the number of
simulations and quickly narrow in on the desired delays.
Number of Rows
Enter the proposed number of Rows in your production blast.
Inter-Row Delay
Enter the Start, End, and Increment values in msec for the Number
of Rows. ie 5 rows of holes and a range from 120 to 150 msec. Again,
the increment number allows you to reduce the number of
simulations and quickly narrow in on the desired delays.
3. Fill in the Frequency Ratios section. This indicates the concentration of the Upper and Lower ranges
(in Hz). To remove any unwanted frequencies in your signature hole waveform it is recommended to
first perform a Band Pass Filter operation.
To perform a Smooth operation, select an event from the Event Table and click the Analyze Event icon. In
the Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu. Select the
Smooth operation. The following dialog box appears.
Select the waveform Channel on which to perform the Smooth operation in the first drop-down menu.
Channel Long
Channel Long
after Smooth
operation
To perform a Sound Calculation operation, select an event from the Event Table and click the Analyze Event
icon. In the Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu.
Select the Sound Calculation operation. The following dialog box appears.
To perform a Subtract operation, select an event from the Event Table and click the Analyze Event icon. In
the Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu. Select the
Subtract operation. The following dialog box appears.
Select Channel 1 and Channel 2 waveforms to subtract in the first two drop-down menus.
Channel 1: Tran
Channel 2: Vert
Subtract Operation:
Channel 1 – Channel 2
To perform a Third Octave Band operation, select an event from the Event Table and click the Analyze Event
icon. In the Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu.
Select the Third Octave Band operation. The following dialog box appears.
Select the Channel waveform to view using the Third Octave operation from the drop-down menu.
Microphone
waveform
Third Octave
operation
performed on
the
Microphone
waveform
To perform a Timeline Overlay operation, select an event from the Event Table and click the Analyze Event
icon. In the Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu.
Select the Timeline Overlay operation. The following dialog box appears.
Timeline
overlay on the
Tran waveform
To perform a Truncate operation, select an event from the Event Table and click the Analyze Event icon. In
the Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu. Select the
Truncate operation. The following dialog box appears.
Select the Channel on which to perform the Truncate operation from the drop-down menu.
To perform a Vector Sum operation, select an event from the Event Table and click the Analyze Event icon.
In the Preset Configuration, click on the Edit Preset icon and click on the Add New dropdown menu. Select
the Vector Sum operation. The following dialog box appears.
Channel 3
Vector Sum
A six-channel Minimate Pro could use two geophones to monitor an event. In this configuration, one
geophone would be placed at the exterior of the building (this would be the Ground Channel). The other
geophone would be placed inside the building (this becomes the Structure Channel) Both geophones
record the triaxial response during an event. The transfer function will then compare one axis on one
geophone to the same axis on the second geophone. The resulting graph is the frequency response of
the building or otherwise known as the Transfer Function.
For more information, refer to the following publications for a complete explanation of natural
frequencies and related calculations.
Dowding, C.H., 1985, ―Blast Vibration Monitoring and Control,‖ chapters 5 and 7, Prentice-Hall, Inc.,
Englewood Cliffs, N.J.
Siskind, D.E., Stagg, M.S., Kopp, J.W., and Dowding, C.H., 1980, ―Structure Response and Damage
Produced by Ground Vibrations from Surface Blasting,‖ U.S. Bureau of Mines, Report of Investigations
8506.
3. Click Transfer
1. Click Projects & Events
Function
2. Click Manage Events
The result is displayed in a graphical form. Scroll the window to view all calculations.
3 To export a PDF report of the Transfer Function, click the PDF icon. Below is an example report PDF
Choose at least one waveform event from the event management window and click on the Frequency
Filter button. You can also import more events from within the report view.
8. Click Save
9. Click Execute
11. Choose from the
dropdown list to
display results in
Velocity, Acceleration
or Displacement
10. The filtered
results appear
3. Expand a project
and select a unit
3 Expand a project and select a unit to view events and logs associated with the unit.
4 Click a Waveform or Advanced Waveform event.
5 Click the Analyze Event button.
7. Enter a Preset
Name and Description
Click the Add New button to add new operations to your Configuration Preset.
8 Select the operations to include in the configuration Preset.
Configure the operation parameters.
11. Click OK
3. Expand a project
and select a unit
7. Click Analyze
3. Click an area
to annotate
Text (Place simple text on the graph, then double-click to edit, this allows you to select
font, text size and color.)
Line (Add a line between two points on the graph, double-clicking the line gives the
option to delete the line. Click an end section to adjust the line.)
Arrow (Point out a section on the graph, click the point of the arrow to delete, click the
end section to adjust the arrow.)
Time Delay (Measures the time between two points on the graph, click the end section
to adjust the line.)
Delete All (Removes all annotations.)
3. Click Save
Before you can view the human exposure report, first do the following to set up a frequency weight file.
6 Select a Frequency Weighting File from the dropdown menu or create a new one.
8. Click Save
7 To customize your frequency file, add a Name then add frequencies and assign a weighting to them.
8 Click the Save button
9 Click the Execute button.
10 The VDV and RMS results appear.
9. Click Execute