1 - Condmaster 2022 User Guide

ANALYSIS AND DIAGNOSTICS
2022
USER GUIDE
Additional information
72301 “Condmaster®Ruby, Installation and system administration” describes how to install the Condmaster Entity
Server (CES) Service, Condmaster software installation and setup, etc.
72302 “CES Admin Portal User Guide” describes license activation, management of databases, users, user groups,
system settings, etc.
72304 “Condmaster.NET User Guide” describes Condmaster.NET functionality.
Trademarks
Airius, CondID, Condmaster, DuoTech, EVAM, HD ENV, Intellinova, Leonova, Leonova Diamond, Leonova Emerald,
SPM and SPM HD are trademarks of SPM Instrument AB.
All other trademarks are the property of their respective owners.
Patents
www.spminstrument.com/patents
© Copyright SPM Instrument AB. ISO 9001 certified.
SPM Instrument AB I Box 504 I SE-645 25 Strängnäs I Sweden Technical data subject to change without notice.
Tel +46 152 22500 I info@spminstrument.se I www.spminstrument.com ISO 9001 certified. © SPM 2021-12. 72303 B Rev.1
2.15 The tree structure 35
Contents
2.16 Creating elements in the tree struc-
Contents 2 ture 36
1. Task definition 11 2.17 Machines, components and measuring

points 37
1.1 Machine faults, condensate pump 11
2.18 Color evaluation mode 38
1.2 Machine data, condensate pump 12
3. Machines and components 40
2. Graphical Overview 13
3.1 Creating machines and components 40
2.1 Navigating in the Graphical Overview 13
3.1.1 Creating a machine 40
2.2 Arranging the Graphical Overview 14
3.1.2 Creating a component 41
Example of arranging several levels in a
tree structure with pictures and Color 3.2 The component form 42
Zones 15 3.3 Extended component form 42
2.3 Importing pictures 16 3.4 Copy component 43
2.4 Picture properties 17 4. Measuring points 45
2.5 Adding Color Zones to pictures 19 4.1 Creating a measuring point 45
Adding Color Zones to SVG pictures 19
4.2 Measuring Point Data 46
Adding Color Zones to JPG or BMP pic- References 46
tures 20
History 46
Color Zone properties and settings 21
4.3 Copying a measuring point 47
2.6 Connecting folders and measuring
points to Color Zones 22 4.4 Editing a copy of a measuring point 48
See a list of connected nodes and dis- 4.5 Basic data and measuring techniques 49
connect a node from a Color Zone 23
4.6 Multiple shock pulse measurement tech-
Connecting several nodes to the same niques 50
Color Zone 24
4.7 Multiple measuring devices on one
Connecting measuring assignments from assignment 50
one measuring point to different Color
Zones 24 4.8 Change order of measuring assign-
ments 50
2.7 Adding Summary Boxes 26
4.9 Quick mode 51
2.8 Adding Symptoms 27
4.10 General RPM settings for the meas-
2.9 Arranging the nodes 28 uring point 52
2.10 A note on Edit mode and Run mode in 4.11 Settings for RPM measurement 53
Graphical Overview 29
4.12 RPM measurement using pseudo tach 56
2.11 Arranging information using rect-
angles and labels 30 4.13 Using RPM trigger to initiate meas-
urement 58
2.12 Displaying live update graphs in
Graphical Overview 31 4.14 Using Post trigger to initiate meas-
urement 59
2.13 Arranging folders on a picture 32
4.15 Cutting measurement times with
2.14 Options for display in the Graphical Conditions 60
Overview 33
4.16 Changing measuring devices for meas- 5.25 Frequency range for EVAM: motor,
uring assignments 61 pump 93
4.17 Deactivating measuring assignments 62 5.26 EVAM: FFT type and averaging for
Leonova and Intellinova 94
4.18 Measuring Point Overview 63
5.27 EVAM: Assignment for enveloping 95
5. Measuring techniques 64
5.28 EVAM: True Zoom settings 96
5.1 A note about transducer settings for
Leonova 64 5.29 EVAM: All condition parameters 97
5.2 Measurement with the DuoTech accel- 5.30 EVAM: Add fault symptoms and symp-
erometer 65 tom groups 98
5.3 The SPM HD measuring technique 66 5.31 EVAM: Disable excessive data 99
SPM HD vs. SPM dBm/dBc terminology 66 5.32 EVAM: Configure symptom, set alert
limit 100
5.4 SPM HD, input data 67
5.33 EVAM: Customizing the Leonova
5.5 Input data for SPM dBm/dBc 69 instrument display 101
5.6 Input data for SPM LR/HR and LR/HR 5.34 The HD ENV measuring technique 102
HD 70
Predefined filters 102
Redirection of OPC values to a LR/HR
measurement 72 Following the development of a damage
with three measuring assignments 102
5.7 SPM LR/HR, connection to Lubmaster 73
Measurement results 102
5.8 Using the bearing catalogue 74
More about HD ENV 102
5.9 Overview of measuring assignments 75
5.35 HD ENV, input data 103
5.10 Overview, edit machine fault symp-
toms 76 5.36 Cepstrum analysis 104
5.11 Overview, alert limits and alert delay 77 5.37 Input data for user defined meas-
urement 105
5.12 SPM Spectrum, input data 78
5.38 Input data for temperature meas-
5.13 SPM Spectrum, advanced settings 79 urement 106
5.14 Bearing symptom parameters 80 5.39 Checkpoint and comments download 107
5.15 Selection of rotating bearing part 81 5.40 Input data for lubrication round 108
5.16 SPM Spectrum, highlighted symptoms82 5.41 Orbit analysis 109
5.17 ISO 2372, input data 83 5.42 Orbit analysis, input data 110
5.18 ISO 10816, input data 84 5.43 Viewing Orbit measurement results 111
5.19 ISO 10816, spectrums 87 5.44 Viewing Shaft Centerline Plot 112
5.20 EVAM assignments, input data 88 5.45 Multi-channel simultaneous vibration
measurement 113
5.21 EVAM: Saving data in short and long
time memory 89 5.46 Setting up multi- channel vibration
measurements 114
5.22 EVAM: Frequency range settings 90
5.47 Bump Test 115
5.23 EVAM: Assignment for analysis 91
5.48 Frequency Response Function, FRF 116
5.24 Frequency range for EVAM: Shaft
symptoms 92
5.49 Run Up and Coast Down meas- 6.3 Copying in measuring round order 141
urements 118
6.4 Working with a split window 142
5.50 Working with the Run Up and Coast
Down results 119 6.5 Working within your own folders 143
5.51 Measuring techniques in the tree 7. Measuring rounds 144

structure 120
7.1 Creating a measuring round 144
5.52 Seamless measurement technique 121
Scheduling a measuring round based
The difference between seamless and on operating time 145
other measurement techniques 121
7.2 Entering measuring points into a
Configuring a Seamless measurement measuring round 146
assignment 122
7.3 Labels in measuring rounds 148
Activating a digital status output 123
7.4 Selecting measuring rounds for down-
Setting up a Condition 123 load 149
5.53 Time Signal Recording measurement 7.5 Downloading measuring round to

technique 124 instrument 150
5.54 Additional measuring technique set- 7.6 Settings for data transfer 151
tings, TSA Advanced 125
Simplify the workflow for down-
5.55 Setting up measuring assignments loading/uploading measuring rounds 151
for Airius vibration sensors 127
Faster measuring rounds in the
Changing name and default settings Leonova instruments 151
per sensor 127
Specific settings for Leonova Diamond
Setting up vibration measurements 128 and Leonova Emerald 151
Setting up temperature measurement 131 Downloading all measuring rounds

and measuring points from Cond-
Calculated RPM settings 132 master to the instrument 152
5.56 The Phase and Cross-channel phase 7.7 Connecting Leonova Diamond and
symptoms 133 Leonova Emerald to PC 153
Introduction to the Phase and Cross- 7.8 Connecting Leonova and Leonova
channel phase symptoms 133 Infinity to PC 154
Relative and absolute phase 133 7.9 Connecting A/T30 to PC 155
5.57 Settings for the Phase and Cross- 7.10 Uploading results to the PC, closing
channel phase symptoms 134 the measuring round 156
Phase symptom settings 134 7.11 Identification tag CondID in Cond-

master 157
Cross-channel phase symptom settings 134
8. Status display 158
5.58 Setting up phase alerts 136
8.1 Status display in the Graphical Over-
Alerts for the Phase symptom 136 view 158
Alerts for the Cross- channel Phase 8.2 Highlighted measuring points 160
symptom 138
8.3 Listing highlighted measuring points 161
6. Measuring point tree 139
8.3.1 Publishing highlighted measuring
6.1 Creating your own folder 139 points on the Internet 161
6.2 Copy alias via clipboard to folder 140 9. Evaluation Functions 162
9.1 Save form layout 162 9.16 Spectrum navigation and zooming 196
9.2 Evaluation functions from the Over- 9.17 Spectrum cursors 197
view 163
9.18 Harmonics and sidebands 198
9.3 Alert list 163
9.19 Highest peaks 199
Introduction 164
9.20 Marked peaks 200
Filters 165
9.21 Harmonic Highlight 201
Priority 165
9.22 Options and tools 202
Status 170
9.23 Y-scale Max 203
Type 170
9.24 Circular Plot 204
Period 171
9.25 Reference Spectrum 205
Source 171
9.26 DS/NDS Spectrum 206
Priority summary 172
9.27 Spectrum and symptoms 207
List of alerts 172
9.28 Symptom harmonics 208
Elements in the alert list 172
9.29 Editing symptoms 209
Alert actions 174
9.30 Spectrum enhancement 211
Alert details 175
9.31 Waterfall diagram 212
Docked windows 176
9.32 Order Tracking 213
9.4 Working with the alert list 177
9.33 Evaluating multi- channel meas-
Alert list workflow 177 urement results 215
Change status for one or several alerts 178 9.34 Pattern recognition in an SPM Spec-
trum 217
9.5 Alert label 180
9.35 Compare spectrum 219
9.6 Alert Limit Manager 181
Selecting measuring points for Com-
9.7 Flexible alert limits 182 pare Spectrum 220
9.8 Bands 183 Working with Compare Spectrum 221
9.8.1 Multiple bands 184 9.36 Colored Spectrum Overview 222
9.8.2 Octave bands 184 Where to find it 222
9.8.3 Implementing bands 185 9.36.1 Colored Spectrum Overview
functionality 223
9.9 Alert delay 189
9.36.2 How the colored spectrum over-
9.10 Measuring result register 190
view is created 225
9.11 Measuring results for vibration
9.37 Introduction to Condition View 226
assignments 191
9.38 Getting started with Condition View 227
9.12 Spectrum default layout 192
Saving selected measuring points as a
9.13 Customizing the layout of tool win-
sequence 228
dows in Spectrum 193
Viewing Trend Graphs 229
9.14 Customizing the toolbar in Spectrum 194
Assigning graphs from Graphic Evalu-229
9.15 Spectrum views 195
ation to Condition View 10.6 Creating and editing criteria 262
9.39 Elements of the Condition View win- 10.6.1 Distribution graph example 263
dow 230
10.6.2 Combined graph example 264
9.40 Condition View settings 231
10.7 Display of evaluated EVAM results 265
9.41 Default Condition View layout 232
10.8 Criteria with different selection con-
9.42 Adding attachments 233 ditions 266
Viewing All Attachments 235 10.9 The effect on COND numbers 267
9.43 Adding Deviations 236 10.10 Measuring result list in graphs 268
Viewing All Deviations 238 10.11 Display of COND no. and raw value 269
9.44 Editing the content and layout of 10.12 The Crest factor 269
Condition View 239
10.13 Kurtosis 270
Customization options in edit mode 240
10.14 Skewness 270
Horizontal or vertical layout 242
10.15 Unbalance 271
Object types 245
10.16 Misalignment 271
Saving your changes 246
10.17 Looseness 272
9.45 The Polar plot function 247
10.18 VEL, CREST and KURT 272
Working with phase symptoms in the
Polar plot function 248 10.19 Checking the spectrum 273
Customizing the Polar plot window set- 10.20 Spectrum with logarithmic Y-scale 274
tings 249
11. Comments 275
The polar plot 251
11.1 Working with comments 275
The Bode plot 252
11.2 New and Edit comments 276
The measurement results panel 253
11.3 Voice comments for the Leonova
9.46 Interpreting the phase symptom res- instruments 277
ults 254
11.4 Download comments to instrument 278
10. EVAM Evaluation 255
11.5 Set a comment in the Graphic Evalu-
10.1 The evaluation of EVAM readings 255 ation 279
10.2 COND numbers in graphics and spec- 11.6 Comment with additional text 280
trum 256
11.7 Comments in the Graphic Evaluation 281
10.3 Recording a batch of readings for the
12. Graphics Functions 282
Leonovas 257
12.1 Graphics functions in Condmaster
10.4 Recording a batch of readings for
Ruby 282
A/T30 258
12.2 Graphics default layout 283
10.5 The Condition Manager 259
12.3 Customizing the layout of tool win-
10.5.1 Alert options 259
dows 284
10.5.2 What is a criteria? 260
12.4 The display of diagrams 285
10.5.3 Criteria Guide vs. Condition Man-
12.5 Selection of items for graphics dis-
ager 261
play 286
12.6 Filtering parameters to be displayed 14.1 Standard work order for work mode
in diagrams 287 ‘Planning’ 316
12.7 Sequences of graphics data 288 14.2 Compiling a standard work order 317
12.8 Machine operating conditions tool 14.3 Compiling work orders 318
window 289
14.4 Editing work orders 319
12.9 Save case tool window 290
14.5 Executing work orders 320
12.10 Show and hide graphs 291
14.6 Preset speed in work orders 321
12.11 Y-scale settings 292
15. Intellinova Functions 322
12.12 Elements of a diagram 293
15.1 Intellinova Standard/Compact func-
12.13 Display of moving average 294 tionality 322
12.14 Combining diagrams 295 Where to find it 322
Saving combinations of diagrams as a Controlling the quality and amount of

sequence 297 measurement data 323
Change line size and color 297 15.2 Measurement conditions in

Intellinova Standard/Compact 324
12.15 Comment and measuring result
tables 299 15.3 Triggered measurements in
12.16 Editing and adding comments 300
15.4 Filtering of measurement results in
12.17 Printing diagrams 301 LinX and CES 328
12.18 Popup menus for alert, COND and 15.6 Alert setup when Intellinova fails to
Spectrum 302 deliver measuring results 329
12.19 Zoom Properties 303 Alerts in the Measuring Point Tree 330
12.20 Editing alert limits 304 Setting up Intellinova e-mail alerts 331
12.21 Drivers for screen and printer 305 15.5 Graphical filtering in Condmaster 332
12.22 Logotype on screen and printouts 306 Measuring and storing logic overview 332
12.23 Connecting drivers with screen and 15.7 Transferring data with OPC Data
printers 307 Access 334
13. Lubmaster 308 15.8 Setting up status outputs for
13.1 Lubmaster 308
15.9 Connecting alert limits to status out-
13.2 The evaluation graph 309
puts 337
13.3 Bearing condition development 310
15.10 Multiple SPM Spectrum assign-
13.4 Measuring point calibration 311 ments 338
13.5 Lubrication data for COMP no. cal- 15.11 Run up/Coast down measurement 339
culation 312
15.12 Monitoring unit workload 340
13.6 Calculation of alert limits 313
15.13 Machine operating conditions 341
13.7 The lifetime graph 314
15.14 Setting graphical filters for machine
13.8 Selecting the optimal lubricant 315 operating conditions 344
14. Work Orders 316 15.15 The ‘Ski slope’ phenomenon 346
15.16 Setting up the ‘Ski slope’ symptom 347

15.17 Filtering ‘Ski slope’ readings in 16.2 Measuring Point Imaging - Overview 388
Intellinova 349
16.3 Measuring Point Imaging using
15.18 Sensor connection check 351 mobile apps and cloud 389
15.19 Intellinova Parallel EN functionality 354 16.4 Measuring Point Imaging using apps
and manual transfer 390
Where to find it 354
16.5 Measuring Point Imaging using
Controlling the quality and amount of images in file folder 392
measurement data 355
16.6 Measuring Point Imaging - Viewing
Measuring assignments distributed on contents on cloud 393
DSPs 356
16.7 Work descriptions 394
Features characterizing Intellinova Par-
allel EN functionality 357 16.8 Standard symptoms for EVAM 395
15.20 Controlling the measurement logic 358 16.9 Symptom groups 396
15.21 Time-based measurement 358 16.10 Condition View Report 397
15.22 Group measurement 359 Introduction to Condition View Report 397
15.23 Linked measurement 361 Getting started 397
15.24 Idle time measurement 363 Opening a sequence or measuring

round in Condition View Report 398
15.25 Manual measurement 365
Creating your report in the Preview win-
15.26 Measurement conditions for dow 399
Intellinova Parallel EN 366
Structure of the report 400
15.27 Triggered measurements in
Intellinova Parallel EN 368 Cover Page section 401
15.28 Setting up status outputs for Creating page header and footer 402
Intellinova Parallel EN 370
Summary section 404
15.29 Global values for Intellinova Par-
allel EN 372 Detailed Page(s) section 405
Distribution of global CES values to Final Page section 407

LinX 373
16.11 Customized Reports 408
15.30 Live values in the Online System
Introduction to Customized Reports 408
Overview 374
Customized Reports navigation 408
15.31 CES Monitor in Condmaster 375
Edit Document navigation 409
15.32 CES Task log in Condmaster 378
Creating Customized Reports 410
15.33 Temperature measurement 380
Adding Field variable to Customized
15.34 Transferring data with OPC Unified
Reports 412
Architecture 382
Saving printouts of reports to Cus-
15.35 Signal Quality Test 383
tomized Reports Archive 413
Signal Quality Test settings 383
16.12 Report Manager 414
Viewing Signal Quality Test results 384
Understanding how reports are com-
16. Additional functions 387 posed 414
16.1 Rule Based Evaluation, RBE 387 Report Manager functions 415
Customizing the standard templates 416 The Variables tab 460
Designing your own reports 417 The Advanced tab 461
16.13 Exporting to Word file 418 The History tab 462
16.14 Exporting measuring results to Shared variables 463

Excel 418
Shared texts 464
16.15 Exporting spectrums and time sig-
nals 419 16.23 Condmaster.NET 465
16.16 Runtime count 420 16.24 Importing measurement results 466
16.17 Communication with SAP software 422 Setting up a Virtual Online Unit in Cond-
master Ruby 466
16.18 Safety copy 423
Set up measuring assignments defining
16.19 USB communication with Leonova the imported data 467
and Leonova Infinity 425
Scalar values 467
Troubleshooting Guide 428
Vibration values 470
16.20 Automatic removal of results 430
Import measurement results 473
Automatic removal of results – main
window 430 Data import via Condmaster.NET 473
Delete results immediately 430 Data import via CES API 475
Configure automatic removal for a 16.25 CES API 479

group of results 431
17. Plant Performer 480
Configure exceptions to automatic
17.1 Introduction to Plant Performer 480
removal of results 432
17.2 Prerequisites 481
Mark results that should be protected
from removal 433 17.3 Creating and using the machine type
register 482
Saved Cases 434
17.4 Working with economic KPIs 484
16.21 Machine Builder 435
17.4.1 Selecting economic KPIs 484
16.21.1 Adding a machine in Machine
Builder 435 17.4.2 Creating a register of corrective
maintenance actions with minimum sav-
16.21.2 Rearranging the measuring
ings 486
point numbers 438
17.4.3 Using corrective maintenance
16.22 Entity rules 440
comments for economic follow-up 488
Introduction 440
17.5 Working with technical KPIs 490
Where to find the function 440
17.5.1 Creating KPIs 490
Rule environment and rule types 441
17.5.2 Using corrective maintenance
How Entity rules are built 441 comments for follow- up of technical
KPIs 494
Adding an entity rule 442
17.6 Following up on prewarning and plan-
The General tab 443 ning times 496
The Conditions tab 444 17.7 Mean Time Between Failure, MTBF 498
The Actions tab 448 17.8 Viewing Plant Performer statistics 499
17.8.1 Plant Performer statistics with
filtered data 499
17.8.2 Plant Performer statistics access

via Condmaster.NET 500
17.8.3 Working with Plant Performer

data 501
18. Decision Support System 502
18.1 Introduction to Decision Support Sys-

tem 502
18.2 Getting started with Decision Sup-

port System 503
18.3 Machine Builder 504
18.4 Signal Quality Test 505
18.5 Machine baseline 506
18.5.1 Introduction 506
18.5.2 Establishing machine baselines 506
18.5.2.1 Prerequisites 506
18.5.2.2 Baseline Manager 506
18.5.2.3 Start a training period 508
18.5.2.4 Calculate baseline 510
18.5.2.5 Create baseline from his-

torical data 511
18.5.3 Baseline in other functions 512
18.5.3.1 Measuring Results 512
18.5.3.2 Graphic Evaluation 513
18.5.3.3 Colored Spectrum Overview 514
18.6 Health score 515
18.7 Alerts 516
18.7.1 Overview 516
18.8.2 Alerts 517
18.8 Entity rules 518
18.8.1 Introduction 518
18.8.2 Setting up alerts via Entity rules 518
18.8.3 Example of a rule generating

an alert 519
18.9 SPM Instrument AB Software License

Agreement 525
1. Task definition
1. Task definition
1.1 Machine faults, condensate pump
Measuring techniques on condensate pump
l (A) Motor ND: SPM

l (B) Motor DE: SPM
l (C) Pump DE: SPM, Vibration H, Vibration A, UD1, coupling
l (D) Pump ND: SPM, Vibration H, UD1, temp.
l (E) Other: SPM cavitation, UD1, temp., UD2, pipe, Check
The following pages show how to set up Condmaster Ruby for a measuring round, containing two con-
densate pumps and two heating water pumps, identical pairs, and their measuring points, using all
available measuring techniques.
Before you input data into Condmaster Ruby, you have to consider what kind of machine faults you
are looking for. For the first example, the main condensate pump in a heating plant, these are
assumed to be:
l Bearing damage, motor and pump bearings
l Pump vibration, general and at selected frequencies
l Misalignment between motor and pump
l Loose foundation bolts, other looseness
l Impeller damage
l Pump cavitation
l High temperature on the non-drive pump bearing
l Coupling wear
l Pipe wear, outflow side 1st bend
l Pump seals and general condition of the pump location.
This fault list is the basis for the selection of measuring techniques, see the picture. The fault list is
important, because unless you target specific faults, you do not know what to measure or cannot
make sense of the measuring results.
- 11 -
1. Task definition
1.2 Machine data, condensate pump
Machine data for input
l (A) Motor ND: ISO bearing no. (shaft diameter)

l (B) Motor DE: ISO bearing no. (shaft diameter)
l (C) Pump DE: ISO bearing no. (shaft diameter), (Machine class), Coupling wear, limit
l (D) Pump ND: ISO bearing no. (shaft diameter), Impeller blades, Temp. range
l (E) Other: Temp. range, Pipe wear, limit
l + General: RPM, Net frequency
For the machine itself, you need the component data: machine number and name, location (option),
and all other component data you want to register, see section "3.3 Extended component form" on
page 42. You may also want to store pictures of the station where the pumps are located and of each
pump type.
The machine data you need to set up the measuring points depend on the measuring techniques you
intend to use. In this example, they are:
l the RPM of the machine (for SPM, Vibration).
l the ISO standard number of all monitored bearings (for SPM HD, SPM LR/HR, SPM Spectrum
and Vibration). The ISO bearing number gives you access to the bearing catalogue data stored
in Condmaster Ruby, including the factors needed for a vibration spectrum analysis on bear-
ings. For SPM HD and SPM dBm/dBc, the shaft diameter is sufficient bearing data.
l the number of impeller blades on the pump (for Vibration, symptom 50).
l the range of temperature measured on the pump housing.
l limit values for the coupling and pipe wear to be measured.
For an extensive vibration analysis of the motor you would need to know the number of poles, rotor
bars, stator coils and, of course, the net frequency.
Measuring points are checked and marked beforehand. As measuring tools and inspection tools, use
either of the portable instruments, a stroboscope lamp to check the coupling, and an ultra sound
meter to measure the pipe wall.
- 12 -
2. Graphical Overview
2.1 Navigating in the Graphical Overview
Condmaster Ruby starts in the Graphical Overview (A). In the ribbon bar, the most commonly used
functions for each ribbon tab can be reached. The ribbon bar consists of the tabs Graphical Overview,
Maintenance, Online, Report Manager, Registers, System and Databases. When buttons are dimmed,
they are not accessible, else they take you to the function for the marked folder or marked item inside
a folder.
In the top right corner, the right panel menu (B) opens a menu complete with all available func-
tions. The menu folds out all functions connected to the active ribbon tab.
Below the ribbon bar, the main folder (C) for components and measuring points is located.
The Graphical Overview has a standard layout (D) which you can change by importing your own
images and arrange information so that you can get a quick and easily interpreted overview of the
state of your machines, see
l "2.2 Arranging the Graphical Overview" on the next page,
l "2.3 Importing pictures" on page 16,
l "2.4 Picture properties" on page 17,
l "2.5 Adding Color Zones to pictures" on page 19,
l and the rest of the sections belonging to Graphical Overview).
When navigating in the Graphical Overview or in the tree structure, press CTRL+Backspace to go
back one level in the structure.
- 13 -
2.2 Arranging the Graphical Overview
As an option, you can customize the Graphical Overview, using pictures or drawings of your plant and
its sections, right down to machine and measuring point level (see "2.2 Arranging the Graphical Over-
view" above). Using Color Zones in the picture and showing Summary Boxes provides a quick and
easy overview of the state of your machines.
In the example above, a picture of a plant has been imported (A), sections in the plant have
been marked with text labels and a Color Zone (B), and a Summary Box (C) is shown for each
folder.
For each folder and component in the tree structure, you can import several pictures, but on meas-
uring point level only one picture can be imported. Pictures need to be in BMP, JPG or SVG format.
When imported to Condmaster , the pictures are stored in the database and are therefore auto-
matically included in your backups.
For more information, see the example of arranging several levels in a tree structure below, and:
l "2.3 Importing pictures" on page 16
l "2.4 Picture properties" on page 17
l "2.5 Adding Color Zones to pictures" on page 19
l "2.6 Connecting folders and measuring points to Color Zones" on page 22
l "2.7 Adding Summary Boxes" on page 26
l "2.10 A note on Edit mode and Run mode in Graphical Overview" on page 29
l etc.
It is also possible to use the functionality available for the Graphical Overview in earlier Condmaster
versions, i.e. drag your folders (components, measuring points) to any part of the picture, and also
obtain a connecting line between a folder and a spot on the picture by dragging the status dot to this
spot, see "2.13 Arranging folders on a picture" on page 32.
- 14 -
Example of arranging several levels in a tree structure with pictures and Color Zones
This example contains several levels in a paper machine starting at the plant overview level. For each level, a picture has been
imported, Color Zones have been added at suitable locations in the picture and folders or measuring points have been con-
nected to these zones.
l A = Plant overview level with paper machine PM2 marked

l B = Component level with drying cylinder DC6 marked
l C = Application level with the gearbox belonging to drying cylinder DC6 and its motor marked
l D = Measuring point level with the gear on the output shaft marked
Double-clicking on PM2 (A) leads further down in the structure, here to the drying section containing
10 drying cylinders. All drying cylinders have a Color Zone with a folder connected to it, easily show-
ing the yellow warnings on DC 6 and DC 9.
Double-clicking on DC 6 (B) leads to the next level in which you can see a view of the drying cylinder,
its gearbox (C) and motor. The gearbox has a color zone with a folder connected to it, here showing a
yellow warning color.
Double-clicking on (C) leads to measuring point level where one measuring point with different meas-
uring assignments is used to monitor a bearing (Color Zone showing green) and the gear (Color Zone
showing yellow, D) belonging to the output shaft.
- 15 -
2.3 Importing pictures
Images must be in BMP, JPG or SVG format.
For each folder and component in the tree structure, several pictures can be imported. On measuring
point level, only one picture can be imported. Pictures must be in BMP, JPG or SVG format. When
imported to Condmaster Ruby , the pictures are stored in the database and are therefore auto-
matically included in your backups.
To import a picture:
1. Select Edit Mode (A).
2. Go to the desired location in the Graphical Overview by clicking on the folders until you reach
the level where you want to insert the picture.
3. Right-click in the empty area and select Add picture (B) in the popup menu.
4. In the Add picture window, choose a picture file and select Open (C).
5. Drag the picture to the desired place. To change the size of the picture, see "2.4 Picture prop-
erties" on the next page for instructions.
6. Cancel Edit Mode.
The next step would be to continue the editing by adding Color Zones on your picture (see " 2.5
Adding Color Zones to pictures" on page 19).
For more information, see the sections related to the Graphical Overview such as "2.4 Picture prop-
erties" on the next page, "2.5 Adding Color Zones to pictures" on page 19, "2.6 Connecting folders
and measuring points to Color Zones" on page 22, "2.7 Adding Summary Boxes" on page 26, etc.
- 16 -
2.4 Picture properties
In Edit Mode (A), right-click on the picture to open a popup menu with different options.
Select Set Picture Size (B) to set your preferred size on an imported picture. If the picture has been
created in a drawing tool, it might be important to set the original image size to avoid potential prob-
lems with distortions. The original size of the imageis specified in brackets.
If you have updated an image and want to reload it into the Graphical Overview, select Reload Pic-
ture from File (C). The image size (width x height) in the Graphical Overview does not change even
though the size of the picture file (in bytes) might have changed.
The alternative Copy Picture to Clipboard (D) can be useful for example when having similar
machines in a database. The function creates a copy of the picture, its size and all its Color Zones –
but not the nodes connected to the Color Zones. To paste the picture, right-click somewhere at the
white surface at the desired location and select Paste Picture from Clipboard.
Object Properties (E) opens a new window that handles filter effects, Color Zones and other set-
tings, see below.
- 17 -
Filter effects are found in the Filter menu (F) in the top right corner. In the Preview Color menu
(G), you can check how the red, yellow, green and grey status colors works with the picture. The pur-
pose of the filter and preview alternatives is to help setting a clear view of the status of your
machines.
The Automatic resize (H) alternative changes picture size in relation to Condmaster window size in
the Graphical Overview. This is especially useful when running Condmaster on multiple computers
with different screen sizes. Since nodes (e.g. measuring points or components) does not have the
same responsive functionality, it is not recommended to place nodes to the right or below the image
(they might end up outside the displayed area). For the same reason, it is not recommended to have
two pictures with Automatic resize in the same window. Automatic resize is not enabled by
default.
For pictures in JPG or BMP format, it is possible to click Rotate 90° (I) to rotate the picture to a
desired orientation.
The Convert SVG to JPG button (J) can help in the following situation: In a network with many cli-
ents connected to the same database, some computers might have problems showing SVG pictures
correctly in the Graphical Overview. In case this happens, go to the computer that shows the SVG pic-
ture correctly, then click Convert SVG to JPG to change its format. NOTE! Changing the format
from SVG to JPG "flattens" the picture which means that Color Zones can no longer be identified and
created automatically, see "2.5 Adding Color Zones to pictures" on the next page.
- 18 -
2.5 Adding Color Zones to pictures

In a picture, it is possible to add Color Zones and connect folders or measuring points to them. This
can be done in any level in the measuring point tree. Connecting measuring points or folders to Color
Zones in your picture(s) provides a quick and clear status of your machines: each Color Zone shows
the status with either red, yellow, green or grey color. By default, the colored zone will blink when
there is an alert on any of the measuring points belonging to the zone.
Adding Color Zones to SVG pictures
For pictures in SVG format, Color Zones are automatically detected. Picture elements that can be iden-
tified as Color Zones are circles, ellipses, rectangles, and polygons.
2. Drag a measuring point or folder to a Color Zone. The detected Color Zone appears in black
(B). There is automatically a connection between the measuring point or folder and the
added Color Zone. The added Color Zone appears in blue (C).
3. Repeat step 2 for all desired Color Zones.
4. Cancel Edit Mode. The Color Zones appear in red, yellow, green or grey color depending on
the evaluation status.
See below for more details about Color Zone properties and settings. For example, it is possible to
decide what will happen when you double-click a Color Zone in the Graphical Overview.
When disconnecting a measuring point or folder from a Color Zone in an SVG picture, the Color Zone
is automatically deleted. See " 2.6 Connecting folders and measuring points to Color Zones " on
page 22 for more information about connections (for example about connecting several nodes to the
same Color Zone, etc).
- 19 -
Adding Color Zones to JPG or BMP pictures
Unlike SVG pictures, Color Zones are not automatically detected for JPG and BMP pictures.
2. Right-click and select Object Properties (B).
3. In the Properties window, select ‘+’ (C).
4. Choose the desired shape (D) of the Color Zone. The shape appears in the top left corner (E).
5. Resize and drag the shape to a suitable location in the picture. If selecting polygon, drag to
draw the desired shape (F).
- 20 -
NOTE : Circular and rectangular shapes require less CPU power than polygons and update
faster when the Graphical Overview status is retrieved.
6. Repeat step 3-5 for all desired Color Zones.
NOTE: To add additional Color Zones in the same shape and size, mark the Color Zone, select
‘+’ and select Copy selected (G).
7. Cancel Edit Mode. The Color Zones appear in red, yellow, green or grey color depending on
the evaluation status.
Color Zone properties and settings
Each Color Zone gets its own numbered tab (A) in the Object Properties window. A Color Zone have
white color, and when activated it is marked with a blue frame (B).
Color Zone (C) uses default settings found under the '...' button: red, yellow and green are trans-
parent (50%) while grey is not (0%). Please note that settings changed under '...' affects all Color
Zones that have the Use Deafult box checked. If you wish, you can uncheck the Use Default box and
select different settings for transparency and frame properties - these changes only affect the current
Color Zone.
By default, Settings (D) has the Hide Node alternative checked, which means that the connected
folder or measuring point will be hidden in the Graphical Overview. Blink on Alert is also checked
and means that the colored zone will blink when there is an alert on any of the measuring points
belonging to the colored zone. If Blink on Alert is inactivated, Hide Node also needs to be inactivated.
On Double Click (E) determines what will happen when double-clicking a Color Zone in the Graph-
ical Overview. By default, this is set to Open Location (in the Graphical Overview) but can be set to
open other functions such as Condition View, Graphic Evaluation, Colored Spectrum, Spectrum.
- 21 -
For pictures in JPG or BMP format, the next step is to connect a folder or measuring point to the Color
Zone, see "2.6 Connecting folders and measuring points to Color Zones" below.
2.6 Connecting folders and measuring points to Color Zones
For pictures in JPG or BMP format, a Color Zone that is not yet connected to a folder or a measuring
point is white, while Color Zones with connections are colored (blue in Edit mode). To connect a folder
or a measuring point to a Color Zone:
2. Drag a measuring point or folder to a Color Zone (B). The detected Color Zone is highlighted
(B). When dropping a measuring point or folder to a Color Zone, it gets connected and the
Color Zone appears in blue (C).
3. Repeat step 2 for all desired Color Zones.
4. Cancel Edit Mode (D). In Run Mode, the Color Zones appear in red, yellow, green or grey
color depending on the evaluation status (E). For more information on Run Mode, see "2.10
A note on Edit mode and Run mode in Graphical Overview" on page 29.
- 22 -
By default, folders are hidden in Run Mode. This can be changed in the Settings found in the Object
Properties window: in Edit mode, right-click in the picture, select Object Properties, select the '...' but-
ton by Settings and clear Hide Node.
See a list of connected nodes and disconnect a node from a Color Zone
While in Edit Mode (A), mark a Color Zone (B) and right-click to open its popup menu. The option
Connected nodes (C) opens a separate window with a list of the connected nodes (D). To dis-
connect a node, clear it and select Save.
A quicker way to disconnect a node from a Color Zone would be to right-click on a Color Zone and
select Disconnect in the popup menu. This command disconnects the folder and all its subfolders (if
any).
- 23 -
Connecting several nodes to the same Color Zone
If you try to drop several nodes in the same Color Zone, you will get a warning that this shape already
has a connected node and alternatives on which action to make; move selected node(s) into the con-
nected folder (Note: If yes, a folder name is input and all nodes are moved to the new folder), or dis-
connect current (already connected) node and connect selected node instead.
If you wish to connect measuring assignments from one measuring point to different Color Zones that
is possible, see below.
Connecting measuring assignments from one measuring point to different Color Zones
It is possible to connect different measuring assignments from one measuring point to different Color
Zones. In this example, one measuring point with several assignments is used to monitor a gear
(Color Zone showing yellow, A) and a bearing (Color Zone showing green, B) belonging to the output
shaft. This was accomplished by creating new folders, copying assignments into them and then con-
nect the new folders to the Color Zones.
- 24 -
The original measuring point (C) consists of five measuring assignments monitoring the gear and
the bearing belonging to the output shaft. To be able to connect these assignments to different Color
Zones in the picture, they need to belong to separate folders.
In this case, a folder called Gearbox (D) with the folders Gear (E) and Bearing (F) was created. The
Gear folder (E) consists of the measuring assignments Vel TSA and HDENV3 TSA, while the Bearing
folder (F) consists of the measuring assignments Vel, HDENV3 and HDENV4 (the assignments were
copied into each folder).
After the structure for the folders and assignments was done in the measuring point tree, the Gear
and Bearing folder was connected to the Color Zones belonging to the gear and bearing in the picture
(A, B).
- 25 -
2.7 Adding Summary Boxes
In this example, Summary Boxes with both text and pie chart are shown for all (four) folders
Summary Boxes are a great way to get a quick status of the condition of your machines, either as
text, a pie chart or both.
To add a Summary Box, make sure that Edit Mode (A) is activated, then right-click a folder (com-
ponent or measuring point) and select Show Summary Box (B).
As default, the alternative Show text is activated. You can choose to show only text, only the pie
chart or both text and pie chart (right-click again). In this example, both text and pie charts are
shown.
The Summary Box (C) appears right beside the folder or measuring point, but you can drag and
drop it anywhere in the Graphical Overview.
When done editing, cancel Edit Mode (A).
- 26 -
2.8 Adding Symptoms
It is possible to add a shortcut to a symptom or a symptom group in the Graphical Overview and
connect it to a Color Zone in an image in the same manner as measuring points. The difference is
that you have to add the symptom or the symptom group in the Measuring point tree first.
• When standing in the Measuring point tree, right click and select Create > Shortcut to Symp-
tom (A).
• Select Measuring Point, Measuring assignment and Symptom/Symptom group, then click
Save (B).
• Connect the symptom to a Color Zone in the same manner as measuring points (see "2.6 Con-
necting folders and measuring points to Color Zones" on page 22).
When marking a symptom in the Measuring point tree, most shortcuts to other functions such as
the Measuring Point Register, Graphics, Spectrum, Measuring results, Comments, Alert
list, etc. works.
The color (green, yellow, red, grey) and alert is displayed on the basis of the symptom.
- 27 -
2.9 Arranging the nodes
If the nodes in the Graphical Overview have been moved around and you want to align (and sort)
them again, this is easily done.
l Activate Edit mode (A).
l Mark the nodes to be arranged (B).
l Click CTRL+O to align the nodes to a straight left margin according to the top left node (C).
l …or click CTRL+SHIFT+O to align the nodes to a straight left margin according to the top left
node and sort the order of the nodes (D).
- 28 -
2.10 A note on Edit mode and Run mode in Graphical Overview
Edit Mode.
When Edit Mode (A) is activated, the Color Zones turns into different colors; blue ones have a node
(folder or measuring point) connected to them (B, D), while white ones (C) does not have a node con-
nected. When selected, a Color Zone (B) has a dark blue frame and its connected node and Summary
Box (if shown) are marked.
Run Mode.
Run Mode means that Edit Mode is inactivated (A). When a Color Zone is selected, it is marked with
a dark blue frame (B) and its node (not visible if hidden) and Summary Box (if shown) are marked.
Color Zones that does not have a node connected are shown in white color (C). Right-clicking on a
Color Zone opens a popup menu (D). By default, double-clicking on a Color Zone opens up the node
(=Open location), see "2.5 Adding Color Zones to pictures" on page 19
- 29 -
2.11 Arranging information using rectangles and labels
In addition to pictures, it is also possible to add rectangles and labels to the Graphical Overview.
Adding rectangles and labels can be useful for organizational purposes.
Select Edit Mode (A). Right-click somewhere in the white surface (not in a picture) in the Graphical
Overview to find the alternatives Add Rectangle and Add Label (B) in the popup menu.
Rectangles and labels can be resized and placed at desired positions. To change its properties such as
colour, font, font style, etc., mark it, right-click and select Object Properties from the popup menu
(C).
When ready, cancel Edit Mode (A).
- 30 -
2.12 Displaying live update graphs in Graphical Overview
The following graphical items can be displayed with live updates in the Graphical Overview: Spectrums, Time signals, Trend
graphs, Circular plots, Latest reading as text.
Evaluation graphs and spectrum views can be added as objects to any place in the Graphical Over-
view, where they will be updated 'live' according to a user defined refresh interval.
To add a graph to the Graphical Overview, right click on a graph in the Graphic Evaluation window
and select Graphical Overview > Add Graph (A). Selecting Add Latest Result as Text displays
the latest result in the Graphical Overview as a text box (B).
To add a spectrum view to the Graphical Overview, right click on it in the Spectrum window and
select Graphical Overview > Add View. Spectrums can also be added from the Alert list in the
same manner. All added objects can be resized and placed at desired positions.
A double- click on an evaluation graph or spectrum view from the Graphical Overview opens the
graphic evaluation window or the spectrum window respectively. Unique to the spectrum objects is
that all settings such as zoom, active cursors, etc. are mirrored to the Graphical Overview.
The objects are updated at a predefined interval which can be changed: click the ‘i’ button in the rib-
bon bar, and select the General tab to input a desired refresh interval for graphs, spectrums, etc. in
seconds. Objects can be refreshed manually as well, by pressing F5 on the keyboard.
The opacity of the objects can also be changed on the General tab; 1 = no opacity, 0 = full opacity
(i.e. objects will not be seen at all), default value = 0.4.
- 31 -
2.13 Arranging folders on a picture
You can drag your folders (components, measuring points) to any part of the picture, and also obtain
a connecting line between a folder and a spot on the picture by dragging the status dot to this spot.
While in Edit mode, click on a folder (component or measuring point) (A), hold down the mouse but-
ton and drag.
Similarly, you can create a grey marker (C) by dragging the status dot (B) to any desired spot. A
line connects the grey marker and the box. To remove the marker, drag it inside the box.
The 'i' Properties button in the ribbon bar opens the Properties window and define options for meas-
uring point display, see "2.14 Options for display in the Graphical Overview" on the next page.
- 32 -
2.14 Options for display in the Graphical Overview

The 'i' Properties button (A) in the ribbon bar opens the Properties window and define options for
measuring point display, default picture directory and refresh intervals, etc.
In the Option tab (B), Number and Name are ticked by default. The Thick connections settings
allows you to select a thin or a thick line connecting the folder symbol with a dot placed somewhere in
the picture. The default setting for Color evaluation mode is Both, but can be changed to Basic
color evaluation or Health score. See "18.6 Health score" on page 515 for more information about the
color evaluation modes.
Under the General tab (C), you can determine how many clickable links to be displayed on the meas-
uring point tag. In addition to the status dot and the alert triangle (if any), a link to Graphics and Spec-
trum is shown by default, but you can also choose to show e.g. Color View, Comments, etc. In this
tab, it is also possible to select a default picture directory and different refresh intervals regarding
how often e.g. the alert list should be updated.
In the User Settings tab (D), you can select a Startup Folder (= the folder that opens when the
Graphical Overview is started), and set a number of your own shortcut keys (ALT GR + A to Z, or
CTRL+ALT + A to Z) to alternatives from the main menu or to a folder in the Graphical Overview.
Please note that the User Settings apply to the logged in user. Only the User Settings tab is available
for users with 'View only' access rights.
When navigating in the Graphical Overview or in the tree structure, press CTRL+Backspace to go
back one level in the structure.
- 33 -
There is also a tab called Runtime (E):
By default, Condmaster generates alerts and system faults for components not running, but these set-
tings can be changed as required.
- 34 -
2.15 The tree structure
The VIEW AS TREE button (A) toggles between Tree structure and Graphical Overview. The tree
structure in Condmaster is where you build the structure with the available elements, folders, com-
ponents and measuring points, that fits your purpose best. It gives an excellent overview over the
monitoring system.
The simplest structure is the main folder with the license name (B) which contains a measuring point
folder with individual measuring points.
The example here shows a structure for three windparks (yellow folders named WP..., C). The third
folder is open and reveals a number of yellow turbine folders. The Turbine 02 folder is open and
reveals three components (= machine units, blue motor symbol, D): main shaft, gearbox and gen-
erator. The measuring point on the main shaft (blue folder, E) reveals the two measuring techniques
used (individual symbols, F): SPM and vibration.
There are two advantages with such a structure:

l Each element in the structure has its status symbol (green, yellow or red dot showing con-
dition, alert triangle in case an alert limit has been exceeded, G). This dot reflects the status of
the lowest element in the structure. Here, all red dots with alert triangle are caused by an alert
on the main shaft bearing of turbine 02 in the third windpark.
l Folders can be copied with all subfolders, components and measuring points. In this case, a tur-
bine folder would be the ideal element to copy. By editing component and measuring point
names one can quickly create a ‘new’ turbine if it is constructed on the same lines.
Elements without evaluated measuring results have grey status dots (H).
- 35 -
2.16 Creating elements in the tree structure
Right-click anywhere in the tree structure and select Create (A) to create
l folders (B)
l components (C)
l measuring points (D)
l machines (E).
Once a component or measuring point is configured and saved, you can mark it and use Create >
Copy (SHIFT+F8) (F) to duplicate it, then Edit (G) to create a similar item.
Holding down CTRL while clicking on folders or components allows you to mark an entire group in any
order. To mark a group of items, you can also click on the first, then hold down the SHIFT key and
click on the last item in the group. You can freely drag items within the tree structure and also split
the screen and drag them from one part to the other. You can also use Cut and Paste to move items
to another position.
Please note that each item you create or paste is inserted above the marked position. Thus, if you
mark a folder, the components in the clipboard will be pasted in outside of and above this folder. To
get it inside, you must open the folder and mark the arrow beneath the last item or any of the items
inside.
All folders you create are originals. The originals of measuring points and components are placed
inside the main folder that has the license file name (H). The original measuring point and component
folders are sorted alphabetically by number. To delete measuring points and component, you must
delete them from these original folders, else you only remove copies. Copies are marked with a bent
arrow.
The folders inside the main folder are created automatically. There you will also find rounds and e-
mail alert assignments if you use these elements.
- 36 -
2.17 Machines, components and measuring points
To add machines, components and measuring points, select View as tree (A) in the ribbon bar.
Toggle between Graphical Overview and Measuring Point Tree using View as tree.
At the top, the Measuring point tree contains a folder with the license name of your Condmaster. This
folder cannot be deleted. Double-click to open it. The folder contains the machine register, com-
ponent register and the measuring point register, each in its permanent folder.
Beneath these folders, your own tree structure can be created. There are two alternatives:
l Alternative 1: Create machines, components and measuring points first, working in the
register folders. The machines, components and measuring points is then sorted alphabetically
by number. Create a structure of folders (this is an option) and drag aliases of the machines,
components and measuring points into the folders. The originals remain in the three register
folders. This is the sequence described in this user guide.
l Alternative 2: Create your own folders, and work inside your folders when creating machines,
components and measuring points. Inside your folders, they are aliases. The original will be
automatically put into the register folders.
See "3.1 Creating machines and components" on page 40 and "4.1 Creating a measuring point" on
page 45 for more information.
- 37 -
2.18 Color evaluation mode
In the Graphical Overview, the dots show the evaluation color and the alert icons show the alert pri-
ority color (for more information about alert priority, see "18.7 Alerts" on page 1.)
The color evaluation mode is set to Basic color evaluation by default, but can easily be toggled
between Basic color evaluation, Health score, and Both. This setting is valid per database (not per
user). The default setting can be changed under Properties in the ribbon bar.
Basic color evaluation shows machine condition in a green-yellow-red color scale, where
l green = everything is normal
l yellow = caution, there is something going on, but the situation is not yet critical
l red = warning, this measuring point needs immediate attention
Health score are calculated by applying mathematical algorithms to collected machine baseline data
(to set up a baseline, see " 18.5 Machine baseline" on page 506), and includes more colors for a more
detailed evaluation.
The colors in the health score correspond to a normalized floating-point value between 0-1, where 0.2
(green) corresponds to the normal state of the machine baseline:
If Basic color evaluation and Health score are used at the same time, the color that corresponds to the
most critical evaluation is displayed.
- 38 -
Health score is a feature in the Decision Support System. For more information, see "18.1 Intro-
duction to Decision Support System" on page 502.
- 39 -
3. Machines and components

3.1 Creating machines and components
In Condmaster Ruby, a machine consists of several components that together form a machine. For
example, a machine can consist of the components motor, gearbox and pump.
3.1.1 Creating a machine
NOTE: Machines can also be added from a library of standard components in Machine Builder. In
Machine Builder, users can add machines to the Graphical Overview/Tree structure. When a machine
is added via Machine Builder, appropriate measuring points, measurement assignments, and fault
symptoms are automatically generated for the machine. Color Zones are automatically added to the
measuring points of the added machine. For further information, see "16.21 Machine Builder" on
page 435.
To add machines that cannot be built in Machine Builder, follow these steps:
1. In the Measuring Point Tree, right-click the Machines folder (A), choose Create (B) and
select Machine (C).
2. Under General (D), enter Number, Name and Criticality for the machine.
3. In the right pane, select Insert (E).
4. Choose components and/or measuring points to include as parts of the machine from the list
and select OK (F).
5. Select Save (G).
As far as possible, work with complete machines. The operating condition of one component, e. g. a
motor, will affect the condition measurements on the whole machine.
NOTE: It is important what item in the tree is marked when right-clicking. If the component folder (or
the closed main folder) is marked, the component is created inside the component folder, as an ori-
ginal. If the space below is marked (as a rectangle with faint lines) or any of your own folders, an alias
is created in that location, plus an original in the component folder.
- 40 -
3.1.2 Creating a component
1. Right-click the components folder (A), choose Create (B) and select Component (C).
2. Enter Number and Name for the component and select Save. See "3.2 The component
form" on the next page for more information.
In Condmaster Ruby, a component is a part of a machine (a machine can consist of several com-
ponents, for example a condensate pump and a motor). As far as possible, work with complete
machines, because the operating condition of one component, e. g. the motor, will affect the con-
dition measurements on the whole machine.
NOTE: It is important what item in the tree is marked when right-clicking. If the component folder (or
the closed main folder) is marked, the component is created inside the component folder, as an ori-
ginal. If the space below is marked (as a rectangle with faint lines) or any of your own folders, an alias
is created in that location, plus an original in the component folder.
- 41 -
3.2 The component form
The required input data for a component are number and name. An item cannot be saved before the
required data are entered.
If the original component number is edited at a later point, Condmaster Ruby will ask if the meas-
urement point that belongs to the component should be automatically updated to reflect the change.
This is normally recommended.
To register additional component data, select Menu texts and modify the component form (see sec-
tion "3.3 Extended component form" below).
3.3 Extended component form
To create an extended component form:
- 42 -
1. In the Component window, select Menu texts (A).
2. Enter headers (B).
3. Select Save (C).
Up to 18 lines of component data can be entered. An additional line is activated when typing a header
on that line in the Menu texts window.
Entering the additional data when creating a new component is an option: you can save the com-
ponent after entering no more than number and name.
If the component form is modified at a later point, e. g. by erasing a header, you will not erase the
data on such a line. It will be invisible until you reactivate the line.
NOTE: The reports used to print component data on screen or paper are not linked to the menu text
form. They have to be edited to fit your own form, using the Report Manager for Components, found
in the Report Manager ribbon tab.
3.4 Copy component
To copy a component:
1. Select a component (A) and select Shift+F8.
NOTE: Alternatively, select the component symbol (E), choose a component to copy in the
list, and select OK.
2. Enter a new Number and Name (B) for the component.
- 43 -
3. If required, edit the component and measuring point data (C).
4. Select Save (D).
Quite often, you will have a number of identical machines, measured in the same way and with little
or no difference in the input data. Once the first of these machines is in the Condmaster database,
you can copy it and quickly create new components, changing only component number and name.
You should, however, verify the machines’ technical data, especially when you use SPM Spectrum or
EVAM for bearing condition analysis. For a spectrum analysis, the exact bearing geometry can be very
important.
In our example, we have a pump station with two pairs of identical pumps. For each twin, only com-
ponent number and name have to be edited on the component copy (and the serial numbers, if recor-
ded). A copy becomes a new component when the component number is changed. The measuring
point numbers are changed automatically, because the new component number becomes a part of all
measuring point numbers. In this example, the measuring point names have to be changed. This is
not necessary when you use ”neutral” names.
A component (measuring point) number is edited by placing the cursor in front of the part to be
changed and overwriting the following position(s): P-10|0 –> P-101 when you type 1 with the cursor
before the last 0. To change names, right hand click in the name field to get the edit functions, or just
mark the text and overwrite it.
- 44 -
4. Measuring points
4. Measuring points
4.1 Creating a measuring point
1. Mark a component or the Measuring points folder (A) and right-click.
2. Choose Create (B) and select Measuring point (C).
In Condmaster, the measuring point is a purely administrative item. Thus, a Condmaster measuring
point can represent several physical measuring points in approximately the same location on the
machine, where you collect different sets of data with different transducers connected to the portable
instruments, or even use other measuring instruments.
Measuring points can stand by themselves, unconnected to a component, but normally they are
attached to components. They are always automatically stored in the standard folder ”Measuring
points”, whose properties correspond to those of the component folder. In addition, they are listed
below the component icon when created as part of the component.
To add measuring points to a component, mark this component in the measuring point tree and right-
click. In the popup menu, choose Create and select Measuring point.
As a faster alternative, mark the component (alternatively the measuring point folder or the closed
main folder with the company name) and press Shift+F7.
- 45 -
4. Measuring points
4.2 Measuring Point Data
In the upper right corner of the Measuring Point Data form you will find tabs for Settings and for
further settings that are measuring device dependent (A). In the lower left corner of the form are two
tabs, References (B) and History (C):
References
References (B) is best described as a way to create templates for entire measuring points, or parts
thereof. Let’s say you have a large number of measuring points, using the same or very similar trans-
ducers, bearings, measuring techniques, settings etc. You can then create a “template point” with
your default settings and right click in the Measuring Point Data form to save it as a reference:
l Right click on the measuring point level to save the entire measuring point as a reference,
including frequency range, symptoms, resolution etc.
l Right click on the technique level to save all settings for the technique as a reference
l Right click on a measuring assignment to create a reference on assignment level. These ref-
erences will also show up in the vibration guide for the instrument(s) active on the assignment.
Now create your new measuring points and select your new reference from the Reference tab to
automatically configure them with the settings from the reference. Essentially, this could be com-
pared to copying a measuring point, but using the Reference option is quicker because you don’t
have to search the measuring point register for the measuring point to copy.
History
History (C) provides a log of all changes made to a measuring point or assignment. Once the change
has been saved, the previous settings can be viewed on the History tab. This makes it easy to e.g.
manually restore a previous setting on an individual measuring point, without having to load a backup
copy of the entire database.
- 46 -
4. Measuring points
4.3 Copying a measuring point
The fastest way to create a measuring point is to copy an existing one.
Mark a measuring point (A), then either

l right click on the point and select Create (B) >Copy (C), or
l press SHIFT + F8, or
l click the Create-Copy (measuring point) button (D) in the lower left corner of the screen
- 47 -
4. Measuring points
4.4 Editing a copy of a measuring point
Edit copy of measuring point:

l Edit Measuring point number (A), Name (B) if required
l Select measuring techniques (C) if required
To turn a copy into a new measuring point, the measuring point number has to be changed. The next
free number belonging to the component is automatically input. Of course you also edit other data as
required.
In this example, the name could be changed to 'Fan Motor DE' (drive end) instead of 'Fan Motor ND'
(non-drive end). More measuring techniques can be activated. Their respective settings are displayed
when you drag them into the upper field. You can input the data at once or after selecting all tech-
niques. Click on the technique to display its settings.
As a rule, use measuring points with the same or fewer measuring techniques when making copies.
When you deselect a measuring technique that has been configured before, you do not delete the
data on the technique forms, you only hide them. They turn up again when you activate the tech-
nique.
- 48 -
4. Measuring points
4.5 Basic data and measuring techniques
Measuring point:
l Input number (A) and Name (B). Location (C) and Work description (D) are options.
l Drag measuring techniques (E) to the upper window, or double click on them.
Compulsory input for Measuring points are number (A) and Name (B). When the measuring point is
created as part of a component, the measuring point number is automatically set to the next free
number under this component. In the Name field (B), you can right click to obtain a list of edit func-
tions for the text in this field.
The Location (C) information is an option, normally you use measuring point names which describe
the location, e.g. ”Motor ND” (non-drive side).
Work description (D) is an option – see section "16.7 Work descriptions" on page 394 in the Addi-
tional Functions chapter. A work description attached to a measuring point will turn up on measuring
rounds and/or work orders and can be printed when downloading to the instruments.
The available measuring techniques are shown in the bottom left hand field. Select one (or more) of
the measuring techniques by double clicking or by dragging it to the upper field. Depending on the
shock pulse technique activated in your instrument, select SPM HD, dBm/dBc, SPM Spectrum
LR/HR for shock pulse measurement. The measuring techniques Run up/Coast down, Bump test and
FRF are not on the list Available techniques - if you wish to use them, activate them in Leonova.
When you upload your measuring round to the pc, the Run up/Coast down, Bump test and FRF results
can be viewed under Comments for the measuring point in question.
When no default instrument has been set for the measuring technique under Measuring system
(see “ Configuring Condmaster Ruby ” in the Condmaster Installation and System Administration
manual, document no. 72301), a form for selecting the instrument is shown when setting up the
measuring point. To change instrument, right click on the technique. For each selected technique, a
data form is opened in the field to the right where you input the measuring parameters.
- 49 -
4. Measuring points
4.6 Multiple shock pulse measurement techniques
Shock pulse measurement with SPM HD, dBm/dBc, LR/HR and LR/HR HD may be combined on the
same measuring point. Take advantage of this opportunity e.g. for testing which of the two tech-
niques works best for a given application.
4.7 Multiple measuring devices on one assignment

Multiple measuring devices may be used under the same assignment (providing the devices are activ-
ated under System > Measuring System). For instance, you may already have an online system
measuring LR/HR and now you wish to complement the online measurements with SPM Spectrum
measurements using Leonova. Add and remove measuring devices by right clicking the assignment.
4.8 Change order of measuring assignments

Measuring assignments may be moved up and down in the list of assignments. When measuring
rounds are downloaded to a portable instrument, assignments are listed in the instrument in order of
their appearance in the measuring point register. If you wish to change this order, right click on an
assignment and select Move assignment upward or Move assignment downward.
- 50 -
4. Measuring points
4.9 Quick mode
Data aquisition and calculation times can be considerable for measurements on low RPM equipment.
Quick mode measurement is a way to speed up the measurement process e.g. for ISO 10816. By
basing computations on the FFT rather than on the time signal, settling times are shortened.
Using Quick mode, measurement is faster but time signal, crest, kurtosis, skew, peak and peak-to-
peak are not computed. Quick mode does not affect the accuracy of FFT, displacement, velocity and
acceleration measurement.
When Quick mode is activated (A), it applies only to that particular measuring assignment. The fol-
lowing settings cannot be combined with Quick mode:
l Time signal
l Crest
l Kurtosis
l Skew
l NL1-NL4
l Enveloping
- 51 -
4. Measuring points
4.10 General RPM settings for the measuring point
RPM settings are usually the same for all measuring assignments on a particular measuring point. To
facilitate the configuration of RPM settings, they are set only once per measuring point, rather than
on each individual assignment. When a measuring point is created, RPM automatically shows up as a
“measuring technique” in its own right (A).
By default, only the Variable speed checkbox and an RPM field (B) are displayed in the form. If the
Variable speed checkbox is ticked, Min RPM and Max RPM can be input (C). Furthermore, RPM
can be converted to a different, user defined unit, eg. m/min, ft/min, etc., by ticking the Convert
RPM to other unit checkbox (D). For information about RPM conversion, see "4.11 Settings for RPM
measurement" on the next page.
Min. speed may be set as required, but it is recommended that it be set to 25% of the maximum
rpm value. Entering data in fields (C) is mandatory.
When a measuring point is set up for variable speed, the settings and measured speed will be dis-
played in the resulting spectrum.
When using variable speed and the SPM dBm/dBc technique, the initial value dBi is not displayed on
the form.
When using variable speed in conjunction with LR/HR or LR/HR HD measurements, the Norm number
is blank. The alert limits for Lub, Cond, and Code are not affected, but if you should work with alert
limits on LR and/or HR, you must input one limit at max. speed and one limit at min. speed. If Norm is
set to 0 (zero), the evaluations Lub, Cond and Code are disabled.
Note: Variable speed is preferred when you want to perform a measurement containing Spectrum.
Even a small change of the RPM affects the position of the significant spectrum lines, so please meas-
ure the machine speed instead of using fixed speed data.
- 52 -
4. Measuring points
4.11 Settings for RPM measurement
With Leonova Diamond and Leonova Emerald, RPM can be measured via the instrument’s ‘RPM’ input.
In Condmaster, all settings for RPM measurement become available once you have added a meas-
uring technique and assigned an instrument to it.
To set up RPM measurement:
1. Mark the RPM measuring assignment (A).

Note: If a new measuring point is created within a component with already existing measuring
point(s), RPM settings of the first measuring point are automatically copied to the new meas-
uring point (but can be edited).
2. In the Settings tab (B), mark the Variable speed checkbox (C) (see previous page). The Cal-
culate RPM from the Leonova factor checkbox (D) is shown given that:
l variable speed is activated
l Leonova Diamond/Emerald is activated on any measuring assignment
l the Use factor checkbox is ticked in the Leonova tab (default when creating new meas-
uring points), see next page for more information
l the measuring point belongs to a component
3. Tick the Calculate RPM from the Leonova factor checkbox (D) to get the following func-
tionality:
l min/max RPM is calculated based on the factor given for Leonova Diamond/Emerald
l if a factor on a measuring point is changed, its Min/Max RPM is recalculated auto-
matically
l if Min/Max RPM (E) is changed on one measuring point, the Min/Max RPM is auto-
matically adjusted for all measuring points within the same component also having the
‘Calculate RPM from the Leonova factor’ option ticked. The measuring points affected
are shown in blue color in the tabs at the bottom of the Measuring Point Data window
- 53 -
4. Measuring points
(F) (these tabs are shown when several measuring points belonging to a component
have been marked in the measuring point tree). In the example, Min or Max RPM is
changed on the first measuring point (marked = dark blue) which affects measuring
points two and three (blue), but not four (white).
4. Tick the Convert RPM to other unit checkbox (G) if you want to convert RPM to a different,
user defined unit, e.g. m/min, ft/min.
Note: these settings will be identical for all measuring points within the same component hav-
ing ‘Calculate RPM from the Leonova factor’ ticked.
5. In the Leonova tab (H), select Portable transducer when using the TTP10 tachometer with
Leonova. For remote measuring points, select Remote and then select the appropriate trans-
ducer type (I). For the standard Leonova Diamond/Emerald, PNP, NPN and Key Phasor can be
used. For the IS version of Leonova Diamond/Emerald, select Namur. The internal transducer
voltage supply can be turned on or off by ticking or unticking the 12V Supply checkbox.
6. Tick the Use factor (J) checkbox (ticked by default and factor set to 1.0 for new measuring
points) to get the following functionality:
l possibility to input a factor (useful when monitoring gear ratio(s), e.g. gearbox and belt
drive monitoring). Click the ‘...’ button and enter a value manually, or compute a factor
by clicking the gearwheel button (K), the NEW button (L) and enter the number of teeth
for the two gears (for pulleys, integers of fractions may be input).
l activation of the Calculate RPM from the Leonova factor checkbox in the Settings
tab, given that variable speed is activated, Leonova Diamond/Emerald is activated in
any assignment, and that the measuring point belongs to a component. See previous
page for information.
7. You may also input and/or change the defaults according to the speed pulse setup and the RPM
variation expected during the measuring time (M).
- 54 -
4. Measuring points
RPM settings for Leonova Infinity differ from those regarding Leonova Diamond/Emerald
With Leonova Infinity, RPM can be measured via the instrument’s ‘RPM’ input. In Condmaster, all set-
tings for RPM measurement become available once you have added a measuring technique and
assigned an instrument to it.
To set up RPM measurement:
1. Mark the RPM measuring assignment (A).

Note: If a new measuring point is created within a component with already existing measuring
point(s), RPM settings of the first measuring point are automatically copied to the new meas-
uring point (but can be edited).
2. In the Settings tab (B), mark the Variable speed checkbox (C) (see "4.10 General RPM set-
tings for the measuring point" on page 52) and enter Min/Max RPM.
3. Tick the Convert RPM to other unit checkbox (D) if you want to convert RPM to a different,
user defined unit, e.g. m/min, ft/min (see "4.10 General RPM settings for the measuring point"
on page 52).
4. When monitoring gear ratio(s), e.g. gearbox and belt drive monitoring, go to the Leonova tab
(E) and tick the Use gearbox (F) checkbox. Enter Min/Max RPM for the input shaft in the
Tachometer RPM fields. The Min/Max RPM values entered by the variable speed checkbox in
the settings tab are shown in grey colour in Converted RPM fields.
Note: ‘Convert RPM to other unit’ and ‘Use gearbox’ cannot be activated simultaneously.
- 55 -
4. Measuring points
4.12 RPM measurement using pseudo tach
To use pseudo tach, Time Synchronous Averaging (A) must be selected.
For RPM measurement on intermediate shafts in gearboxes which are inaccessible for tachometers,
pseudo tach can be used. The pseudo tach is a software function that generates a “synthetic” pulse
train (turning speed signal) synchronous to the intermediate shaft, thus providing a way to apply syn-
chronous time averaging or order tracking on signals from a gearbox internal shaft.
Pseudo tach is available with Intellinova Standard (from CUPackage version 331), Intellinova Com-
pact (from CompactPackage version 108) and the Leonova Diamond/Emerald instruments, and can
be used for vibration measurements only.
Using pseudo tach requires Time Synchronous Averaging to be selected for the measuring assign-
ment (A). This setting will automatically activate pseudo tach in the measuring device. With a tacho-
meter providing one pulse per revolution on the input shaft, time synchronous averaging enhances
signal quality by amplifying repetitive signals while removing all vibrations not synchronous with
shaft speed. For the intermediate shaft this does not work, because every time the tacho pulse
passes, the shaft will be at a different position.
For pseudo tach to work, the number of teeth both on the drive gear and on the driven gear need to
be input in Condmaster.
- 56 -
4. Measuring points
In the Measuring Point Data window, mark the RPM measuring assignment and make sure the
Variable RPM checkbox is ticked on the Settings tab. On the measuring device tab (Online or
Leonova) (A), input the Number of pulses per revolution. To input an RPM factor, which can be
computed or entered manually, click the ‘...’ button (B).
l To compute the RPM factor, click the NEW button (C) in the RPM factor window and enter the
number of teeth for the two gears. For pulleys, integers or fractions may be input.
l To enter an RPM factor manually, click the gearwheel button (D) and enter a value.
Example: If the input shaft has 13 gear teeth and the output shaft has 22, then the frequency of the
tach signal is multiplied by 13/22 = 0,59090909. This means that when the input shaft has rotated 22
times and the tach has generated 22 pulses, the output shaft has rotated 13 times and the pseudo
tach has generated 13 pulses. Using time synchronous averaging or order tracking on the pseudo
tach, the signals which are synchronous to the intermediate shaft will be amplified.
In some cases, you may want to use pseudo tach without time synchronous averaging. This is accom-
plished by setting the number of averages for Time Synchronous Averaging to 1. This can be use-
ful e.g. in the following situations:
l when order tracking with multiple pulses per revolution is used and the distribution of pulses
over each revolution is uneven, thus causing a very varied RPM, activating pseudo tach will sta-
bilize the order tracking to one pulse per revolution.
l when using an encoder with many pulses per revolution, using pseudo tach improves order
tracking if the number of pulses exceeds the maximum number of orders tracked.
- 57 -
4. Measuring points
4.13 Using RPM trigger to initiate measurement
When measuring with Leonova on variable speed machines, an RPM trigger can be used to determ-
ine when to start a shock pulse or vibration measurement, ensuring that it is carried out at an appro-
priate speed. The RPM trigger can be used on applications where useful readings can be obtained only
within a limited RPM range, such as in cranes.
To implement an RPM trigger, open Measuring Point Data and mark a measuring assignment. Click
the Leonova Advanced tab (A).
Under Trigger selection, select RPM trigger (B), then select a Trigger type. ‘RPM run up’ means
Leonova will initiate the measurement, then wait for the machine to speed up to the level input under
Trigger level (C) before it starts recording the signals. With ‘RPM run down’, Leonova waits for RPM
to slow down to the Trigger level setting.
Under Delay time (D), you can specify a number of seconds (or tenths of a second) during which
Leonova will delay the start of measurement. This setting is optional.
- 58 -
4. Measuring points
4.14 Using Post trigger to initiate measurement
Post trigger can be used with the Leonova Diamond/Emerald instruments and the Intellinova Com-
pact/Parallel EN online systems, and works for SPM HD, LR/HR HD and all vibration measurement
techniques. The purpose of the post trigger is to avoid the recording of irrelevant signals that may ulti-
mately cause false alerts. It can be used where strong signals can be expected which are process
related and not attributed to machine damage. This is the case for example in rolling mills, where you
do not want to measure when the slab enters the work rolls (which causes a natural “peak” in the sig-
nal).
To implement a post trigger, open Measuring Point Data and mark an SPM HD or vibration meas-
uring assignment. Click the Leonova Advanced or Online Advanced tab (A).
Under Trigger selection, select Post trigger (B). Input a value (HDsv for SPM HD and usually
mm/s 2 for vibration measurements) under Trigger level (C). In the example to the left above,
Leonova Diamond and Leonova Emerald will initiate an SPM HD measurement and wait for the sig-
nal’s HDsv level to reach 25 before it starts a complete measurement including time signal and FFT.
Make sure you input a viable trigger level; if the level is never reached, the measurement must be
aborted manually.
Under Delay time (D), you can specify a number of seconds (or tenths of a second) during which the
instrument will delay the start of measurement. This setting is optional.
Post trigger settings for Intellinova Compact/Parallel EN are the same, with the addition of the Max
trigger window parameter (E). This setting determines how long the system will wait for the trigger
- 59 -
4. Measuring points
level to be met (i.e. for HDsv to reach 25, in this example) before moving on to the next meas-
urement channel.
4.15 Cutting measurement times with Conditions
In conjunction with SPM HD measurements with Leonova Diamond and Leonova Emerald, conditions
can be set up in Condmaster. They are a means to speed up the measurement process by ensuring
that certain measurements (which may be time-consuming) are carried out only when necessary.
To implement a measuring condition, open Measuring Point Data and mark the measuring point
name (A). Click the Leonova tab (B). Under Conditions, all SPM HD measuring assignments are lis-
ted. Mark one and click the EDIT button (C) to define a condition for it.
For SPM HD measurements, the condition is always an HDm limit (D). This condition means that a full
SPM HD measurement including FFT will only be completed if the initial HDm reading equals or
exceeds the limit value.
- 60 -
4. Measuring points
4.16 Changing measuring devices for measuring assignments
In this example, four measuring points will be affected by this instrument change. The dBm/dBc measuring technique is used
on all four of them. The Leonova instrument is used for measurement on three of the measuring points.
The purpose of this function is to provide a convenient way to quickly change (or add) measuring
devices for multiple measuring assignments at once, for example after upgrading to a newer instru-
ment. Please note that to use the function, you must have administrator privileges in Condmaster.
With multiple measuring points marked for display in the Measuring Point Data form, the function
can be accessed via the ‘...’ button in the lower right hand corner of the form (A).
In the Change instruments window, the measuring techniques involved are listed, along with the
number of measuring points using the respective measuring technique (B). The list also includes
information on which measuring devices are used and on how many of the selected measuring points.
To add a new instrument or monitoring system to a measuring point, mark a measuring technique in
the list and click ADD INSTRUMENT (C). Select the instrument or monitoring system you want to
add and click OK. You will see it added to the measuring technique row. At this point, all the devices
listed there may be used on the measuring points involved.
To replace a measuring device, mark a technique in the list and click the SWITCH INSTRUMENT but-
ton (D). Select the device to be replaced (E) and click OK. Now select the new instrument or mon-
itoring system (F) and click OK. The “old” device can now no longer be selected for measurements.
- 61 -
4. Measuring points
4.17 Deactivating measuring assignments
The Deactivate assignment option can be used to temporarily ‘suspend’ a measuring assignment.
For instance, to save some time you may prioritize monitoring horizontal vibration levels, and start
measuring the other directions only when the horizontal starts to increase. In such a case, you could
deactivate the vertical and axial direction measurements until they are called for. Or, you may want
to try different settings for a measuring assignment. Deactivating the ‘original’ assignment rather
than deleting it may save you some time and trouble.
To deactivate a measuring assignment, right click it in the Measuring Point Data window and select
Deactivate assignment (A). Deactivated measuring assignments are marked with a red ‘X’ (B) in
the Measuring Point Data window (B) and in the measuring point tree (C). Users of the Intellinova
online system will also see the ‘X’ in the Commander Unit Settings window.
Editing a deactivated measuring assignment is not recommended, as Condmaster does not check for
errors in the setup of deactivated assignments.
Deactivated measuring assignments are not shown in:
l Graphic Evaluation l Color Spectrum Overview

l Spectrum l Alert list
l Measuring results l Compare Spectrum
Furthermore, deactivated measuring assignments are not downloaded to the Leonova portable instru-
ments or transferred to the Intellinova online systems’ Commander Units.
NOTE: The following measuring assignments cannot be deactivated: co- measured SPM Spectrum
assignments, two and three-channel vibration assignments, assignments used to provide global val-
ues or measuring conditions.
- 62 -
4. Measuring points
4.18 Measuring Point Overview
Found under Registers > Measuring Point Overview in the right panel menu, the Measuring
Point Overview function creates a sortable, printable list of measuring assignment settings for selec-
ted measuring techniques. The list is very useful e.g. with large online systems, where it can be dif-
ficult and time consuming to get a collective overview of settings from the measuring point tree. The
Measuring Point Overview makes it easy to spot anomalies in measuring assignment settings.
The option buttons (A) enable the user to select a measuring technique to display in the list. The
options include all measuring techniques used in the current database, i.e. if there are no SPM HD
measuring assignments, this measuring technique will not appear among the option buttons.
The group of checkboxes (B, ‘Select column’) represent settings on measuring point level (not
measuring assignments). Ticking a checkbox means all measuring points containing such information
will be included in the list; if for instance ‘Location’ is ticked, only measuring points on which a loc-
ation has been specified in Measuring Point Data will be displayed.
The list can be sorted in ascending or descending order by clicking any of the column headers.
In the list, click a measuring point name to open Measuring Point Data and review (or change) its
measuring assignment settings.
Right clicking on the list opens a menu of options, including Print and Export to Excel (C).
- 63 -
5. Measuring techniques
5.1 A note about transducer settings for Leonova
Regardless of the measuring technique used, transducer settings are an integral part of measuring
assignment setup for portable data collectors (Leonova Diamond and Leonova Emerald). The options
are ‘Portable’ and ‘Remote’ (A), and it is important to understand the difference between the two:
l ‘Portable’ refers to portable transducers, typically attached to the measuring point using a
quick connector or magnet mount. The default transducer settings in the instrument will apply
upon measurement. The instrument will measure bias (for vibration transducers) and res-
istance (for shock pulse transducers) on the first measuring assignment only and the bias is
assumed to be the same for all subsequent measurements with the current transducer.
l ‘Remote’ usually refers to permanently installed transducers to which the data collector can be
connected directly or via a measurement terminal. When selecting ‘Remote’ transducer for a
measuring assignment, transducer type and sensitivity must be input in Condmaster and will
override instrument transducer settings. Bias (or resistance) is measured
- only on the first measuring assignment under a given measuring point, unless transducer set-
tings are changed, and
- when moving on to the next measuring point in the measuring round.
- 64 -
5.2 Measurement with the DuoTech accelerometer
Due to its capacity to support multiple measuring techniques, the DuoTech ® accelerometer requires
a few special pointers.
DuoTech is a multi- purpose, single transducer solution used for vibration or shock pulse meas-
urements, or both of them in combination. This flexibility makes it possible to select the optimal meas-
uring technique for a given type of problem or application.
DuoTech supports SPM HD, SPM LR/HR HD and all vibration measurement techniques with SPM online
and portable measuring devices.
For vibration measuring assignments with Leonova Diamond or Leonova Emerald, selecting ‘Portable’
under Transducer Mode (A) means that the default transducer settings in the instrument will apply
for the measurement. Selecting ‘Remote’ will override the instrument settings with the transducer
and sensitivity (B) input in the Measuring Point Data form in Condmaster.
Using the DuoTech accelerometer with magnet mount is not recommended, since the damping prop-
erties of the magnet will reduce the high frequency content captured by shock pulse transducers. If
possible, use a permanently installed DuoTech instead, or a DuoTech with quick connector.
- 65 -
5.3 The SPM HD measuring technique

SPM HD® is a further development of the original shock pulse method, True SPM ®. SPM HD is avail-
able for measurement with the Intellinova system and the portable Leonova Diamond and Leonova
Emerald instruments. SPM HD can be used on any application, but is particularly well suited for bear-
ing monitoring on low speed machinery.
Users accustomed to dBm/dBc measurement will find that SPM HD is as easy to use and does not
require much input data. An SPM HD measurement yields the following results:
l HDm, a scalar value expressed in decibels, representing the highest value measured during
the measuring cycle. HDm is the primary value to use to determine the severity of a bearing
damage.
l HDc, a scalar value expressed in decibels and a measure of lubrication condition.
l Time signal, measured simultaneously with HDm and HDc.
l Spectrum
HDm and HDc are both suitable as the basis for alert limit definition, regardless of machine type.
When measuring with SPM HD, the measuring cycle is based on number of revolutions rather than
time. This maximizes the chances of capturing relevant signals in the course of one measuring cycle.
By adjusting the sampling frequency to rpm, spectrums are clear and concise also when measuring
cycles are long.
SPM HD vs. SPM dBm/dBc terminology

Below is an account of the correlation of the basic terms used in the two shock pulse methods.
SPM HD SPM dBm/dBc Comments

The purpose is normalization and elimination of RPM dependency. HDi cov-
ers from -15 to 40 on the dBsv scale, while dBi covers from -9 to 40. Meas-
HDi dBi
urement on machinery running at extremely high speeds will require
manual RPM input.
HDc follows the same amplitude scale as dBc and is similar to dBc at basic-
HDc dBc
ally all speeds.
HDm follows the same amplitude scale as dBm and is similar to dBm at
HDm dBm
speeds above 100 RPM.
For information about input data, see "5.4 SPM HD, input data" on the next page.
- 66 -
5.4 SPM HD, input data
To measure with SPM HD, the measuring technique needs to be activated for your measuring device
under System > Measuring system found in the right panel menu. SPM HD measuring assign-
ments are created in the Measuring point data form the same way as any other assignment.
The only Measuring point data settings which are particular to SPM HD measurement are:
l HDi (A) is the normalization factor used to normalize the shock amplitude. The recommended
setting is “Calculated”, where Condmaster will automatically compute the value based on RPM
and shaft diameter.
l Measuring time: Depending on the rpm of your application, the Measuring time (B) setting
has a significant impact on the length of a measuring cycle. Empirical studies have shown that
in order to achieve reliable measurements of bearing condition, measurement should cover at
least 10 shaft revolutions and preferably 50 revolutions, which is the default setting. The time
required to complete a measuring cycle can be calculated as 50 X (60/RPM).
l Symptom enhancement factor: The Symptom enhancement factor (C) is used to improve
the signal-to-noise ratio. For applications with little electronic noise and few mechanical shock
phenomena, this factor can be kept low (1 to 5). Where noise and random shocks are fre-
quently occurring, it is recommended that the Symptom enhancement factor be set higher.
However, you should be aware that the higher this factor, the longer the measurement cycle.
Please note that for portable instruments, symptom enhancement is set to ‘Off’ by default.
The Y axis unit in spectrum and time signal differs depending on whether or not symptom enhance-
ment is used:
Y axis unit Symptom enhancement off Symptom enhancement on

In spectrum HDsv HDesv
In time signal HDsv HD2esv
- 67 -
l Time Synchronous Averaging (D) is used for detection of shocks which are synchronous to
rotating speed, such as gears, hydraulic piston pumps or gear pumps. This setting has an
impact on measurement times; the more averages, the longer it takes to collect enough data.
On a medium to high speed application, a minimum of 100 averages can be used for best res-
ults while on low speed machines, 20-50 averages may be more appropriate.
NOTE: Time Synchronous Averaging should not be used for detection of bearing faults.
In the upper right corner of the Measuring Point Data form you’ll find additional tabs (E) for meas-
uring device settings, in this example for Leonova Diamond.
- 68 -
5.5 Input data for SPM dBm/dBc
Input ISO bearing number (A) or shaft diameter. Alert limits (D) are usually set after measuring the bearing.
The basic data needed for bearing monitoring using the SPM dBm/dBc technique is the ISO standard
bearing number (A). The initial value dBi (B) of the bearing is automatically set after you enter
these data.
As an alternative to the ISO bearing number, you can input the shaft diameter. The manufacturer
name is an option. It is only needed in case you want to use SPM Spectrum or the EVAM technique for
bearing monitoring. The button ”...” (C) opens the bearing catalogue.
If dBi is known, it can also be entered manually.
SPM dBm/dBc measurements return evaluated results: values for bearing condition in dBn (dB nor-
malized with regard to bearing size and speed). They are displayed against the green-yellow-red con-
dition scale. The actual status of the measuring point will also be displayed as a colored dot in the
Graphical Overview.
To make use of the alert list, you must enter Alert limits (D). Once you have measuring results and
know the ”normal” values for a given bearing, you can edit the alert limits, e. g. set them to 5 dB
above normal.
Upper (E) means that an alert is given when the measured value is larger than the limit value.
Lower (F) means that you get an alert when the measured value drops below the limit.
Alert delay (G) is useful to obtain stable and well justified alerts. This function delays the alert by a
user specified number of readings and determines when alerts will be raised. All readings are still
saved to the Condmaster database; the “filtering” is done in the graphical display only.
- 69 -
5.6 Input data for SPM LR/HR and LR/HR HD
Input ISO bearing number (A) or TYPE no. (D) and mean diameter (E). Input NORM (F) and ACCUM (H). COMP (G) and
LR/HR alert limits (K) are set after measuring the bearing, or not used.
The basic data needed for bearing monitoring with the LR/HR technique is the ISO standard bearing
number (A). Type (D) and Mean diameter (E) are automatically set after you enter these data. If
you set Norm = 0 (F), you get no evaluation (unnormalized measurement: Lub, Cond and Code are
not displayed). As an alternative to the ISO bearing number, you can input the mean bearing dia-
meter (E) and the Type no (D) (see below).
The Accum (H) range is from 1 to 9. For low speed bearings (below 500 RPM), use the LR/HR method
and set Accum to 3 or higher. This returns an average of the set number of shock pulse readings.
SPM LR/HR and LR/HR HD measurements return two sets of results:

l the raw values LR (for strong pulses) and HR (for the shock carpet).
l the evaluation results LUB (lubrication number), COND (condition number), and CODE
(A = good, B = poor lubrication, C = beginning damage, D = damage).
A correct evaluation often demands that you set a Comp no. (compensation number, G). You cannot
do this before you have measuring results which you can check with LUBMASTER. To start with, you
can leave the Comp no. at “0” and input either ”BCD” as alert limits under Code, or “0” under LUB
and “32” under Cond. Once you have measuring results, you can fine tune your alert conditions by
introducing a Comp no. For this, use the button (G) to go to LUBMASTER, see under that header.
To make use of the alert list, you must enter Alert limits (I). Once you have measuring results and
know the ”normal” values for a given bearing, you can edit the alert limits. As an alternative, you may
disregard the evaluation code and trend the LR/HR values plus set alert limits for those (K), also selec-
ted with the help of LUBMASTER.
Alert delay (J) is useful to obtain stable and well justified alerts.
The field TLQ limit under Leonova (L) is normally set to “15”. For measuring points with remote
transducer, e.g. Ex transducers, a lower value can be set to force acceptance of a lower transducer
line quality number without causing a TLQ warning. For regular transducers however, alert limits
below 15 is not recommended.
- 70 -
1 Deep groove ball bearings, series 62, 63, 64
2 Angular contact bearings, all series
3 Deep groove ball series 60, 160, 618, double row and self-aligning ball bearings
4 Thrust ball bearings, all types
5 Cylindrical roller bearings, single row
6 Taper roller bearings, all radial types
7 Spherical roller bearings
Double row cylindrical roller bearings
8 Thrust roller bearings
For SPM purposes, bearing data are grouped into 8 different types, each with a TYPE number 1
through 8. The types are described in the table above.
Bearing manufacturers, though not all, follow ISO standards when numbering their bearings. The
number code contains the information on mean diameter and bearing type. Thus, when you use an
ISO bearing number as input in Condmaster, the program will give you Dm and TYPE no. As manual
input, you can use the last three digits of the ISO number, which will produce Dm but not the TYPE
no.
- 71 -
Redirection of OPC values to a LR/HR measurement
Note: The OPC redirection functionality applies to LR/HR only (not LR/HR HD).
To use data obtained via OPC for a LR/HR measurement, you set up two user defined measuring
assignments – one for LR and one for HR, both with OPC as instrument – in addition to the LR/HR
measuring assignment (A). In the OPC settings tab of a user defined measurement assignment, the
group Redirection of results (B) is used to redirect the user defined LR and HR result to the LR/HR
measuring assignment. Note that both LR and HR must have an OPC redirection for a result to be
saved.
When new OPC results arrive, the OPC LR and OPC HR results will be redirected to the LR/HR assign-
ment which is always measured in pairs. In order for this to work, a Max merge time (C) needs to
be set. Max merge time is used to adjust the time of the results with x seconds to tie the LR and HR
results to the exact same time. Otherwise, the LR and HR results will get different timestamps, caus-
ing Condmaster not being able to calculate LUB/COND/CODE. Max merge time should be set to the
same number of seconds for both LR and HR. You can check the time under measuring results to help
decide a max merge time.
If there is a result within the max merge time for HR, then the OPC LR value will be merged to this res-
ult. If a result for HR is missing, a new result with only LR will be created. To avoid any gaps in in the
measurements results, it is recommended to use the ‘Synchronous OPC Import’ setting when redir-
ection of result for LR/HR is used. This setting is found in the Online system overview > OPC import,
SETTINGS button. The reason for this recommendation is that for synchronous measurement, Cond-
master always receives a result from the OPC server. If the Condmaster measurement interval is
more frequent than the OPC server update interval, the OPC server returns the same result until a
newer result is available. In asynchronous measurement, only one result is obtained from the OPC
server when a new value exists, i.e. if the measurement interval in Condmaster is more frequent than
the OPC server update interval, you will not get a result and then there will be ‘gaps’ in the graph-
ics/measurement results. If asynchronous measurement is selected, please make sure that the OPC
server update interval is more frequent than the measurement interval in Condmaster to avoid gaps
in the measurement results.
To select which OPC value you want to use, click the … button by Item (D) and write a text in the fil-
ter dialog that appears. Only items containing the filtering text will be shown. If no filter is specified,
all values that the OPC server subscribes to will be displayed, and finding the value you are interested
in may be difficult.
- 72 -
5.7 SPM LR/HR, connection to Lubmaster
Lubmaster: From the measuring data point windows, click the LUBMASTER icon. Input the min (A)
and max (C) RPM to see the corresponding HR scales (B, D).
When Variable speed is marked, Condmaster needs two alert limits on LR/HR. Please note that alert
limits on LR and/or HR are an option. You do not have to use them, but if you do, you need two.
LUBMASTER helps you find them.
Given the ISO bearing number and the RPM, LUBMASTER will show the evaluation frame for the bear-
ing. The LR/HR values should be within the green zone of the frame while bearing condition is good.
Thus, the border between the green and the yellow zone is a suitable alert limit.
In the left image above, the minimum RPM has been input in field (A). The corresponding HR alert
limit is 29 (B). Changing the input to the maximum speed (C) pushes the HR limit to 47 (D). In both
cases, set the LR value to HR+5.
- 73 -
5.8 Using the bearing catalogue
The ISO bearing number is very useful, and you should work with it whenever possible. It links your
measuring point data to the Condmaster Ruby bearing catalogue which contains all data needed for
shock pulse and vibration evaluation and analysis of most bearings.
The bearing catalogue is located under Registers in the ribbon bar. To find a bearing, enter the num-
ber in field (A), then select bearing and manufacturer (B).
Click EDIT (C) to see the data. The four entries to the right (D) are the factors used by Condmaster to
configure the symptoms for bearing pattern recognition (spectrum analysis).TYPE no. (E) is specific
for SPM Instrument AB, only used for LR/HR and LR/HR HD measurements, and refers to eight bear-
ing types, see "5.6 Input data for SPM LR/HR and LR/HR HD" on page 70 for details and illustrations:
l 1 = Deep groove ball bearings, series 62, 63, 64
l 2 = Angular contact bearings, all series
l 3 = Deep groove ball series 60, 160, 618, double row and self-aligning ball bearings
l 4 = Thrust ball bearings, all types
l 5 = Cylindrical roller bearings, single row
l 6 = Taper roller bearings, all radial types
l 7 = Spherical roller bearings, Double row cylindrical roller bearings
l 8 = Thrust roller bearings
When bearing data is edited in the bearing catalogue, the change is reflected on all marked meas-
uring points using that particular bearing (F). Measuring points differing in any way from the bearing
data under Settings in the bearing data form are marked with a red asterisk in the ‘Affected meas-
uring points’ list (G). Marking the name of a measuring point with deviating bearing data will display
the differences in the bottom of the form (H).
- 74 -
5.9 Overview of measuring assignments
Mark the measuring point in the tree structure, right click with the mouse and select Edit to open the
Measuring Point Data form. When SPM HD, SPM Spectrum or a vibration measuring technique (A)
is marked in this form, an overview of all symptoms and condition parameters for this technique is dis-
played in the technique window in the right part of the form.
Click on one of the parameters/symptoms in the list to display the corresponding graph in the tech-
nique window. Use the UP and DOWN arrow buttons on your keyboard to move through the list.
The symptoms are enabled to the assignments by marking them in the Symptom list (B). A green
check mark in the box shows that the assignment is enabled and a red check mark shows that the
assignment is set up with alert limits (C). The assignments (D) are shown in the upper part of the
technique window. Here you can determine what symptoms to be displayed in the graphics for each
of the assignments.
After you have measured, the spectrum window (E) will show the latest measuring result when you
open this form. Right click in the graph for further display options (F). You can select logarithmic
scales and view matched or theoretical symptoms. Click the measurement unit on the horizontal
scale to switch between rpm, Hz and orders.
Selection of rotating bearing part
For vibration, SPM HD and SPM Spectrum assignments, the rotating part of the bearing can be selec-
ted (G), thereby excluding irrelevant symptoms. For instance, in an application where the load is on
the bearing inner ring, selecting Rotating inner race disables outer ring modulation (BPFOM).
- 75 -
5.10 Overview, edit machine fault symptoms
You can add machine fault symptoms from the fault symptoms register (A) to the measuring point,
rename and edit the fault symptoms by right clicking in the symptom field in the assignment over-
view.
Use NEW and ADD to get the list of available choices (for details, please see under "5.29 EVAM: All
condition parameters" on page 97). ADD appends the new item to your selection. Select a fault symp-
tom, name it and make the settings in the Standard Symptoms form (B).
INSERT places the new item above the marked line on the list. EDIT (C) opens a window where you
can configure a marked fault symptom.
Bearing symptoms
To recognize bearing patterns in a spectrum, use the symptom group Bearing. Condmaster contains
several bearing groups, which are identical except for the number of multiples which are highlighted.
- 76 -
5.11 Overview, alert limits and alert delay
You can add new, edit and delete alert limits for the symptoms. Mark the assignment and the symp-
tom to be changed and select the '...' button (A). In the Limit guide (B) you can set the Alert limit
type:
l Level alerts, i.e. a yellow or red alert is triggered whenever a measured parameter reaches a
certain, user defined threshold. This type of alert is static and therefore works well on applic-
ations running with fixed speed and stable loads.
l Moving average alerts; essentially the same as above but the value triggering the alert is a cal-
culated average of a user defined number of measuring results rather than one individual read-
ing. With moving average, alerts caused by sudden and random amplitude increases are
avoided. The system calculates a mean value of x number of readings and calculates a new
mean every time a new reading is registered. The higher the number of readings for mean cal-
culation, the flatter the resulting curve will be. Moving average alerts are preferably used on
applications subjected to randomly high readings from unexpected events.
l Condition alerts; static alert limits that will remain the same irrespective of machine running
condition. Alert limits based on RPM or machine operating conditions will vary depending on
established machine baseline settings. See also "10.5 The Condition Manager" on page 259.
Upper alert limit (C) means that an alert is generated when the measured value is larger than the
limit value. Lower alert limit means that an alert is generated when the measured value drops
below the limit.
Alert delay is useful to obtain stable and well justified alerts. Select the '...' button (D) to open the
alert delay settings where you select the technique and the number of delays (E). This function delays
the alert by a user specified number of readings and determines when alerts will be raised. All read-
ings are still saved to the Condmaster database; the “filtering” is done in the graphical display only.
See also the chapter "9. Evaluation Functions" on page 162.
- 77 -
5.12 SPM Spectrum, input data
The default range for SPM Spectrum is 0 to 1000 Hz, 1600 lines, full spectrum.
This gives a good overview with room for several multiples of the bearing symptoms. In a power spec-
trum, line amplitudes are squared, which puts an emphasis on large amplitude lines while suppress-
ing the smaller lines.
General
The frequency range, the number of spectrum lines, spectrum type and number of peaks to save can
all be edited (A). For number of peaks to save, any figure up to half the number of lines in the spec-
trum can be entered. You can select full spectrum or number of peaks to save in the memory, short or
long time memory. Under “Long time memory” (E) you can select measurement results from the
short time memory, with time interval or after a number of measurements, to be saved in the long
time memory as an addition. In the short time memory, the latest 100 readings are stored.
Settings
On the line Upper frequency, Hz (B), you can select a calculation function for this frequency, or
orders (C) if selected, by clicking on the “...” button (D). First select the default symptom you want to
use (selected under the tab “Leonova” or “Online”), and you will get the lowest available frequency
range or orders that accommodates all symptoms. Any measuring results below the lower frequency
will be displayed as grey lines in the resulting spectrum. Here you also select the type of spectrum
window, Rectangle, Hanning, Hamming or Flat-top, you want to use and number of lines in the spec-
trum.
- 78 -
5.13 SPM Spectrum, advanced settings
Advanced settings (A) in the lower part displays more options for setting SPM Spectrum para-
meters. In case an analysis is needed to distinguish between typical bearing patters and other spec-
trum lines, a linear spectrum with high resolution, e. g. 3200 lines over 500 Hz, should be used.
When Always measure is marked (in the Leonova tab), the Leonovas will automatically produce a
spectrum with every SPM measurement, else you can choose the spectrum function at will before
starting the SPM measurement with a Leonova instrument.
As FFT window, Hanning is the default setting. True zoom is normally not used in connection with
the SPM Spectrum.
In Condmaster, spectrum data are saved first in a short time memory, then transferred to a long time
memory, with a reduced amount of data if you so choose. This saves memory space. There is no point
in saving full spectrum data indefinitely – when you get high or suspicious measuring results, the
spectrum should be analyzed immediately. The size of the short time memory depends on the set-
tings made under System > Measuring system (see under "Configuring Condmaster Ruby" in the
Condmaster Installation and System Administration manual, document no. 72301).
For Leonova, the SPM Spectrum type can be set to Pattern recognition (SD), where each spec-
trum is scaled so that the total RMS value of all spectrum lines = 100 SD = the RMS value of the time
record. The alternative is Shock level (SL), the RMS value of the frequency component in decibel.
Alert levels are manually set for each symptom to show evaluated results in green-yellow-red.
For information about zooming, see section " 5.28 EVAM: True Zoom settings " on page 96 in this
chapter and "9.27 Spectrum and symptoms" on page 207).
- 79 -
5.14 Bearing symptom parameters
For bearing symptoms, the main parameter (Z) is imported from the bearing catalogue. It should
never be changed on this form. In case the catalogue data are incomplete or wrong, please edit the
catalogue.
Max. harmonics (A) determines how many repetitions of the pattern are highlighted. The settings
shown above (max. harmonics = 4) will highlight each pattern four times.
The symptoms BPFI (ball pass frequency, inner race) and BPFO (ball pass frequency, outer race) can
be rpm modulated and have sidebands, often 3 or more. These sidebands tend to overlap when sev-
eral harmonics are present, so only the 2 sidebands closest to the centre line are highlighted (B).
Please note that any changes made on this form, e. g. the entry under Max. harmonics or the RPM
tolerance, are valid for all bearing symptoms in the group.
- 80 -
5.15 Selection of rotating bearing part
For spectrum assignments, the rotating part of the bearing can be selected, thereby excluding irrel-
evant symptoms. For instance, in an application where the load is on the bearing inner ring, selecting
Rotating inner race disables outer ring modulation (BPFOM).
- 81 -
5.16 SPM Spectrum, highlighted symptoms
(A) BPFIM: Max. harmonics = 1, Sidebands = 2
(B) BPFI: Max. harmonics = 3, Sidebands = 0
(C) BPFIM: Max. harmonics = 3, Sidebands = 2
Example A shows how the symptom BPFIM (ball pass frequency modulation, inner race) is highlighted
by blue lines. The setting is Max. harmonics = 1 and Sidebands = 2. Note that this symptom will
only highlight the sidebands and not the centre frequency BPFI.
Example B shows the symptom BPFI (ball pass frequency, inner race). The setting is Max. har-
monics = 3, so the first, second and third harmonics are highlighted.
Example C shows again the symptom BPFI, but now with harmonics. By clicking on a line in the spec-
trum you mark it with a red square. See more about Spectrum functions under chapter "9. Evaluation
Functions" on page 162.
- 82 -
5.17 ISO 2372, input data
When the vibration assignment ISO 2372 icon (A) is marked in the Measuring Point Tree, the input
data form is displayed to the right. The Leonovas support all three available techniques: ISO 2372
(broadband RMS measurement, earlier called VIB in Condmaster), ISO 10816, and Vibration. ISO
10816 is a newer standard meant to replace ISO 2372. However, ISO 2372 is still widely and suc-
cessfully used. In Condmaster, T/A30 instruments can only be set up to use ISO 2372 for broadband
measurement and EVAM.
Please note: You do not normally mix the vibration techniques but use only one of them to monitor
machine condition. Vibration gives you the most options, whereas ISO 2372 is easiest to use.
Machine class
Selecting the ISO machine class (B) sets default values for yellow (maintain) and red alert (stop). You
can set a limit under Lower to get an alert in case vibration severity drops below this value.
Transducer settings
By default, the transducer setting (C) is Portable transducer. When you keep this setting, the vibra-
tion transducer data will be read from the data logger that is used for measurement. As an altern-
ative, you can select Installed transducer after clicking on the transducer icon. For Installed
transducer, the compulsory input is the transducer type (pull down and select) and the transducer
sensitivity. You can register your vibration transducer with its actual sensitivity, then you get this
data by default.
Alert limits
Upper (red) and Upper (yellow) (D) means that an alert is given when the measured value is lar-
ger than the limit value. Lower means that you get alert when the measured value drops below the
limit.
- 83 -
5.18 ISO 10816, input data
When the vibration technique ISO 10816 (A) is selected, the Vibration guide will open for setup of
input data. Vibration monitoring method ISO 10816 is available with Leonova instruments and Online
only.
For ISO 10816, the vibration guide quotes the ISO definitions of the Part (E) ( = part of the ISO
standard, so far published 1 - 6) and of the Group (F) (group of machines treated under that part).
Step through the guide with NEXT (D) and make you selections. The guide leads to the data input win-
dow. In Condmaster, T/A30 instruments can only be set up to use ISO 2372 for broadband meas-
urement and Vibration.
If you use ISO 10816 in your company, there should be a copy of the ISO standard available. Please
go through the definitions and study the illustrations, else it is not easy to classify your machines.
Most common industrial machinery, like electrical motors, pumps and fans, you will find in Part 3.
Part 6 is for reciprocating machines. There is the choice Measure. You are supposed to measure all
three vibration parameters, velocity, acceleration and displacement. The relatively highest meas-
uring result determines the machine’s ”vibration severity grade”. Assuming that present machine con-
dition is normal, the Leonovas will find the lowest ”Machine vibration classification number” where
this result falls into the A/B range. You should then go back to the data input form and change Meas-
ure to the appropriate classification number, else increasing vibration values will change the clas-
sification number instead of causing an alert.
- 84 -
In the final window of the vibration guide for ISO 10816, select the measuring direction and the fre-
quency range.
By default, the frequency is set to the ISO recommended values. Both upper and lower frequency can
be edited (A). Physically, the lower frequency is limited by the transducer you are using. Most vibra-
tion transducers are not linear below 3 Hz. This affects, above all, the displacement values (DISP).
For low speed applications which require true measurements of displacement you should work with a
displacement transducer and not rely on the converted displacement values obtained with an accel-
erometer.
The vibration limit values (B) are taken from the ISO standard and can not be edited. Values below
the B/C limit are in the green evaluation zone. The red evaluation zone starts with the value at C/D.
Your selection in the guide are displayed in the final window. Click Previous in case you want to
make changes, or finish with OK (C).
- 85 -
ISO 10816 produces a 1600 line velocity spectrum over the selected frequency range. Under Short
time memory (A), you can decide to save the full spectrum or up to 800 peaks. In the short time
memory, the latest 100 readings are stored. Under Long time memory, you can have a different
setting. Normally, you reduce the data, like here to 50 peaks. For more information about saving
data, please see section "5.21 EVAM: Saving data in short and long time memory" on page 89 in this
chapter.
The Time signal unit (B) depends on the transducer (ACC for an accelerometer).
Speed data are not required. When the measuring point includes speed data set under other tech-
niques, they are displayed in the data window.
Please note: Condmaster treats the ISO 10816 technique like a reduced version of the EVAM tech-
nique. In the technique window, you can right hand click on ISO 10816 and convert to EVAM.
In the upper right corner of the form you’ll find tabs for Settings and for further settings that are
measuring device dependent (C).
- 86 -
5.19 ISO 10816, spectrums
In an ISO 10816 spectrum, symptoms cannot be shown, but using a marker and the function CPM/
orders, an indication of machine condition can be obtained:
l Use CPM/orders and the marker to detect imbalance at 1 x rpm (A) or alignment at 2- 3 x rpm
l Asynchronous frequencies with harmonies may indicate bearing damage (B)
l On gearboxes, sidebands at the rpm frequency with harmonies may indicate gear tooth dam-
age
When an ISO measurement spectrum indicates problems, it is recommended that the measurement
be followed up with FFT vibration analysis.
- 87 -
5.20 EVAM assignments, input data
By default a Vibration assignment (A) is named "1000 Hz, 1600 Lines" (B). The assignment name
turns up in the measuring technique window and on graphs and result lists, so make sure to change it
to your preferences. If the assignment name tells what and how you measure, you do not have to
check the input data form to understand the results.
The Vibration assignment in the example above returns twelve condition parameters and a linear (C)
spectrum of 1600 lines over the range 2 - 1000 Hz (D), of which a full spectrum is saved in the short
time memory and 800 peaks in the long time memory (E). All parameters can be edited. Upper fre-
quency can be calculated by first selecting and activating a symptom , then click “...” (F) and select
Calculate suitable frequency range (G).
Measuring time and resolution depend on the set parameters. With the above settings, the assign-
ment takes 1.6 seconds to measure and calculate and has a resolution of 0.625 Hz (H).
There is no general recommendation on how to configure a Vibration assignment. Everything

depends on the machine faults you are trying to detect. You also have to distinguish between ”mon-
itoring” and ”analysing” condition. Known machine faults can be easily detected by monitoring a small
fraction of all the data you can collect using vibration, so for routine measurement you would disable
most of the parameters. This greatly reduces the amount of graphs and spectra which would oth-
erwise make your database unmanageable. If an unknown vibration problem requires a detailed ana-
lysis, you can always activate more parameters and add more assignments.
- 88 -
5.21 EVAM: Saving data in short and long time memory
l Short time memory (A): more data are usually saved here than in long time memory
l Long time memory: the amount of data saved in long time memory should be drastically
reduced. Also make settings for additional save as required (B).
The purpose of the two different memories is to save disk space. A full spectrum can take as much
space as several thousand measurements without spectrum. Normally, it is desirable to reduce the
amount of data transferred from short to long time memory.
In short time memory, the latest 100 results are saved. When the number of measurements exceed
100, less than the full time signal data of each measurement can be stored in order to save memory
space. On a falling scale, the alternatives require memory space as follows:
l Time signal (saves the full time signal)
l Full spectrum (returns the number of lines entered under “Lines in spectrum” and contains
2,56 times less data than the time signal)
l Peaks (saves spectrum lines that have a line with a lower amplitude on either side. Thus, a
maximum of half the total number of lines in a spectrum can be peaks, so you can set ”Peaks”
to max. half the value entered under ”Lines in spectrum”). A/T30 can only save peaks (up to
200).
l Condition parameters (disables the spectrum completely and returns up to twelve condition
parameters. Please read ”EVAM: all condition parameters” for more information.)
Please note that you cannot store more data in long time memory than was originally saved in short
time memory. If for instance only peaks are saved in short time memory, you cannot save the full
time signal or full spectrum in long time memory.
Note that the condition parameters are calculated in the instruments on the basis of the measured
time record. Thus, they are influenced by the frequency range but not by the spectrum type. Nat-
urally, a lower frequency range contains less vibration energy than a larger frequency range meas-
ured under the same conditions, so RMS values measured over 10 - 500 Hz are lower than those
measured over 10 - 1000 Hz.
An additional function in long term memory is the option to save regularly at an interval of your
choice for hours, days or measurements (B).
- 89 -
5.22 EVAM: Frequency range settings
The frequency range settings affect the condition parameters (slightly) and the spectrum (very
much). For condition parameters, one normally uses the range 10 - 1000 Hz. This makes the con-
dition parameter VEL comparable with the RMS value returned by ISO 2372, and the parameters VEL,
ACC and DISP comparable with the values returned by ISO 10816. A/T30 instruments are limited to 3
to 200, 500, 1000, 2000 or 5000 Hz.
The “...” button (A) selects the calculation function for Upper frequency, Hz (B). Select the symp-
toms you want to use, and get the lowest available frequency range that accommodates all symp-
toms.
The Lower frequency, Hz can be edited by selecting a value from a dropdown menu (C) or a field in
which a value can be entered manually (E). Physically, the frequency range is limited by the trans-
ducer you are using. Accurate measurements in the high frequency range (above 1000 Hz) require a
firm transducer attachment (screw mounted against a flat milled surface). Most vibration transducers
are not linear below 3 Hz. This affects, above all, the displacement values (DISP). For speed applic-
ations which require true measurements of displacement you should work with a displacement trans-
ducer and not rely on the converted displacement values obtained with an accelerometer.
The frequency range for the spectrum should be large enough to contain the selected fault symptoms
(see ahead). The spectrum resolution is determined by the range divided by the number of lines in
the spectrum. The selected resolution is displayed at the bottom of the screen (D).
- 90 -
5.23 EVAM: Assignment for analysis
Spectrum settings:
l Select the spectrum data to save in short and long time memory (A).
l Select the frequency range (B).
l Select the number of spectrum lines (C).
l Select spectrum type (D).
Depending on your measuring equipment and the modules purchased, the spectrum settings avail-
able in Condmaster will vary.
For information on the options for short and long time memory (A), see "5.21 EVAM: Saving data in
short and long time memory" on page 89 in this chapter.
When lines from different symptoms are close together, you want a high resolution to distinguish
between them. For this, you select a large number of lines over a narrow frequency range. In this
example, measuring 3200 lines over 500 Hz gives a resolution of 0.156 Hz. The resolution and the
acquisition time (E) are displayed after you have made your selections.
- 91 -
5.24 Frequency range for EVAM: Shaft symptoms
A = Standard symptom no.
B = Shaft symtoms, 1X = RPM/60, 2968 RPM = 49.467 Hz
C = Shaft symtoms, 1X = 49.467 Hz, Range = 200 Hz
D = Shaft symtoms, 1X = 49.467 Hz, Range = 500 Hz
Before you create an EVAM assignment, you have to consider which frequency range to use in order
to catch the fault symptoms you are interested in. The patterns you get from the symptom registers
do not change, but their position in the spectrum depends on the rpm of the machine. The greater the
machine speed, the larger the frequency range needed.
Above, you see the shaft symptoms, used for most types of rotating machines. The fundamental fre-
quency is at 1X, here 2968 rpm or 49.467 Hz, i. e. very close to 50 Hz. Symptom 12, Looseness,
requires the largest range, 10X or just under 500 Hz. This would suggest a measuring range of 500
Hz to accommodate the symptoms.
The resolution over 500 Hz is max. 0.0781 Hz a 6400 line spectrum. For shaft symptoms, one would
normally use 800 lines (resolution 0.625 Hz) and save 400 peaks, making the min. distance between
peaks 1.25 Hz. The exceptions are electric motors, which require a high resolution to distinguish
between the net frequency (here 50 Hz) and 1X (here 49.467 Hz). A suitable upper frequency can eas-
ily be calculated by pressing the “...” button in the setup window.
When you work with spectra, you normally measure in one direction only, because the spectrum
gives you the information on unbalance, misalignment and looseness you would try to induce from
the relative differences between the RMS measurements taken in three directions. For EVAM points,
choose the direction returning the highest value, or the most convenient direction if values are
roughly the same.
- 92 -
5.25 Frequency range for EVAM: motor, pump
A = Motor symptoms, 200 Hz range, 1X = 49.467 Hz
B = Rotor bar symptom 36, 5000 Hz range for 1X = 49.467 Hz
C = Impeller symptom 50, 1000 Hz range for 1X = 49.467 Hz
Of the electric motor symptoms in Condmaster Ruby, all but one are in the 200 Hz range for 1X ≈ 50
Hz. The rotor bar symptom 36 requires a measuring range of at least 2000 Hz.
Symptom 30 shows the effect of magnetostriction (normal in a motor and thus always present). This
line at 100 Hz is here extremely close to the typical misalignment line at 2X (98.933) or the line
caused by an uneven stationary air gap between rotor and stator.
Symptoms 32 and 34 require a very high resolution, because they work with the slip frequency of the
motor, here only 0.533 Hz. For symptoms 30, 32 and 34 you need a zoom spectrum with the centre
frequency at 100 Hz.
You also use the shaft symptoms on the motor. A simple test for electric faults in a motor can be
made by turning off the power and measuring while the machine is running down. Your measuring res-
ults should drop considerably if they were affected by excessive magnetostriction or other electrical
causes.
Shaft symptoms can be used as they are, but the motor symptoms 32, 34, 36 and the impeller symp-
tom 50 must be configured.
- 93 -
Please note: The example above is given for a net frequency of 50 Hz. If your net frequency is 60 Hz,
the relationship between 1X and the motor frequencies are similar, but instead of 50 Hz and its mul-
tiples you get 60 Hz with its multiples. The motor symptoms are available for both 50 and 60 Hz net
frequency.
5.26 EVAM: FFT type and averaging for Leonova and Intellinova
FFT type: Select from the menu (A). Default: Linear.
Average type: Select from the menu (B). Default: FFT Linear, 4 readings. Input the number of con-
secutive measurements (C).
The default setting for the FFT type is a linear spectrum, showing the RMS values of the spectrum line
amplitudes (e. g. the RMS value of vibration velocity if velocity is the spectrum unit).
An amplitude spectrum will show peak values instead, and a power spectrum the squared RMS val-
ues. Power spectral density is the squared RMS value over a 1 Hz band.
The default setting for Averaging type is “FFT Linear”. “FFT Peak Hold” returns the summary of the
calculated spectrum, displaying all peaks occurring during measurement. Selecting “Yes” under Aver-
aging overlap means that the number of measurements set under Averages will be overlapped in
the resulting spectrum graph. Overlapping reduces data aquisition time.
Machine vibration is not a smooth, continuous signal, so each time record measured will differ some-
what from the next. To stabilize the measuring results one can use various forms of averaging. This
requires more than one consecutive measurement. The number of measurements is input under
Averages (C). Please note that the default setting (invisible unless you open Advanced settings)
for SPM Spectrum is FFT linear averaging with four measurements.
Time synchronous averaging means that all included measurements are started with the shaft in the
same position. This requires a trigger pulse from an inductive probe or the SPM tachometer probe con-
nected to the RPM input. For more options related to TSA, see "5.54 Additional measuring technique
settings, TSA Advanced" on page 125.
”FFT linear” returns the RMS value of the spectrum lines, while ”FFT peak hold” returns the highest
value of each spectrum line obtained from the stated number of measurements. Thus, the com-
bination of the FFT type ”Amplitude”, 4 measurements and ”Peak hold” will return the maximum peak
values of all spectrum lines obtained during four consecutive measurements.
For information about zooming, please see section "5.28 EVAM: True Zoom settings" on page 96 in
this chapter.
- 94 -
5.27 EVAM: Assignment for enveloping
Enveloping =finding machine resonances through broadband measurement. A = Filter frequency, B

= Resonances.
Enveloping is mainly used for bearing damage analysis. If you already measure bearing condition
with one of the SPM techniques, you have a better option for this purpose, the SPM Spectrum, which
normally gives you a much clearer signal from the bearing.
Enveloping is a technique which demodulates the amplitude of a high frequency signal and presents a
spectrum of the modulating frequencies.
To find the right filter frequency (C), you should first take a broad band measurement over e. g. 5 000
Hz and look for the machine resonances. In the example above, there is a cluster of lines around 1
400 Hz and almost no signal above 2 000 Hz. The correct frequency of the high pass filter (which
excludes all lower frequencies from the measurement) is here 1 000 Hz.
A rule of thumb for filter frequency selection is

l 6.25 x BPFI x RPM for machine speeds below 600 RPM
l 5.25 x BPFI x RPM (but not less than 1 000 Hz) for machine speeds 600 to 3 000 RPM.
- 95 -
5.28 EVAM: True Zoom settings
l Input the frequency that you wish to study in detail under Zoom center (A).
l Input the resolution required to find the fault under Lines in spectrum (C).
l What range above and below the zoom center is needed? Calculate as Upper frequency /
Zoom factor. N.B. Lines in spectrum * Zoom factor must not exceed 25600 (see below).
To facilitate identification of certain symptoms, e.g. electrical faults in electrical motors, True Zoom
can be used. The purpose of True Zoom is to achieve the highest possible resolution around a certain
frequency. The result of a measurement with True Zoom is a spectrum which retains the number of
spectrum lines but across a new and limited frequency range.
The typical frequency area to zoom is the double net frequency, 100 Hz or 120 Hz (A). A high res-
olution in this frequency range is necessary to distinguish between electrical and mechanical faults.
Zooming in on 100 (or 120) Hz requires an upper frequency of min. 200 Hz (B).
By selecting an upper frequency twice the desired zoom frequency, an in-depth analysis can be done.
In the example (above), the frequency range is set to 0-200 Hz (B). The maximum number of spec-
trum lines in Leonova is 12800 (C). These settings give a resolution of 0.015625 Hz (200/12800),
equivalent to 0.94 rpm (D). This resolution can be doubled using True Zoom with the following set-
tings:
l Under Zoom center (A), input “100” Hz (corresponds to the range to zoom)
l Under Zoom factor (E), input “2”. The upper frequency is now divided by the zoom factor
(200/2), resulting in a resolution of 0.0078 Hz (0.46 rpm).
The number of Lines in spectrum (C) is the deciding factor for what zoom factor can be set. If the
zoom factor is too large in relation to the number of lines, the memory space allocated for meas-
urement results will be exceeded. Lines in spectrum * Zoom factor must not exceed 25600.
The upper frequency (B) divided by the zoom factor (E) sets the size of the “zoom range” (F), which is
equally distributed around the selected zoom center. Please note that the zoom range must be within
the selected frequency range.
- 96 -
5.29 EVAM: All condition parameters
With the Leonova instruments you can measure twelve condition parameters:
l DISP = vibration displacement, RMS
l VEL = vibration velocity, RMS
l ACC = acceleration, RMS
l CREST = difference between RMS value and peak value
l KURT = kurtosis, showing the presence of transients caused by shocks
l SKEW = skewness, showing the direction of transients.
l NL1 to NL4 = noise level in the four quarters of the selected range
l the peak value of the time signal unit
l the peak to peak value of the time signal unit
A/T30 instruments do not handle the noise level (NL) or peak value parameters.
All these parameters can be useful analysing tools, but for routine condition monitoring you should
make a selection. Vibration velocity VEL is most useful commonly measured in on industrial machines
in the normal speed range. Displacement DISP is used for low speed applications (and should be
measured with a true displacement transducer). Acceleration ACC is used for high speed applications.
Marking Vibration (A) will open the technique window. The assignments are shown in the upper part
of the window (B). Here you can determine what symptoms to be displayed in the graphics for each of
the assignments. The symptoms are enabled to the assignments by marking them in the Symptom
list (C). A green check mark in the box shows that the assignment is enabled and a red check mark
shows that the assignment is set up with alert limits (D).
After you have measured, the spectrum window (E) will show the latest measuring result when you
open this form.
- 97 -
5.30 EVAM: Add fault symptoms and symptom groups
l Mark a position in the parameter window (A).

l Right click and select Insert or Add (B).
l Select condition parameter, symptom or symptom group (C).
l Possibility to change symptom name (D), but see below.
The purpose of machine fault symptoms is to help you with pattern recognition in the spectrum. A
fault symptom highlights the spectrum lines affected by a certain type of machine fault. For vibration,
it also adds the amplitudes of the lines involved and displays the result as the symptom value.
The simplest and most important is “10 Unbalance” which finds the line at 1X (shaft rotation in Hz).
All symptoms in the group ”Shaft” are combinations of 1X and its multiples (also called ”orders”). The
group needs no configuration because its common variable is the measured rpm of the shaft.
To add a symptom (symptom group, deleted condition parameter ), position the cursor in the para-
meter window (A), then right click and select either Insert or Add (B). Select an item from the list
(C). Insert inputs this item above the cursor position. Add places it at the bottom of the parameter
window.
The new list contains all available condition parameters and the contents of the symptom and symp-
tom group registers. Select by double clicking (or mark and click OK). Repeat the sequence Inser-
t/Add – OK for each item you want to add to the assignment.
Menus for renaming and configuring symptoms and symptom groups are opened automatically.
Renaming is an option. It is recommended that you retain the standard names (or edit the names in
the registers if you prefer you own naming system), because using the same symptom under lots of
different names will lead to confusion.
- 98 -
Most symptoms can be used without changing the configuration, some require additional data. Please
note: Do not clutter up your measuring points with too many symptoms. Getting the data is easy,
using them takes time.
5.31 EVAM: Disable excessive data
l A = Condition, 2 condition values

l B = 500 Hz, 3 symptom values
l C = Envelop, 6 symptom values
The purpose of the three assignments shown above is as follows:
Overall Condition: Return the RMS value of vibration velocity (VEL) and acceleration (ACC) values,
measured over the 1000 Hz range. With this value you can trend the general vibration condition of
the machine and get an alert when vibration is increasing.
Assignment 500 Hz 3200 lines: Returns a high resolution spectrum over the range were all the
interesting symptoms are located. The condition parameters are disabled, because they are covered
by the Condition assignment. The symptom group Bearing is also disabled, being covered by the
Envelope assignment. With this assignment, you can trend the symptom values for unbalance, mis-
alignment, looseness and the impeller condition.
Assignment Envelop 500 Hz: In case you do not use SPM HD, this is your assignment for monitoring
the bearing.
By systematically deleting and disabling parameters, the amount of data per measurement has been
reduced, none of them doubled.
- 99 -
5.32 EVAM: Configure symptom, set alert limit
Edit symptom: Input / change parameter value as needed (A). Click OK.
Set alert limit: Input upper alert limit (B). When desirable, input lower alert limit (C). Click SAVE.
When you right-click on a symptom on the assignment form and select Edit, a list of the named symp-
tom parameters is displayed. Please make this a rule: when you add new symptoms to your Standard
symptom register, name all parameters which do not have a ”standard” symptom parameter value.
This makes them visible on this form and saves you the trouble of going to the register to check.
The symptom 50 Vane and impeller is one of those you must adapt to your machine. The missing
parameter is Z = number of vanes, here the number of impeller blades in your pump. This data
must be accurate, else the symptom is worthless.
Alert limits on symptom parameter values
In case you have symptoms with stable matches and strong amplitude values, you can set both up-
per and lower alert limits on these. Please check the amplitude values on scale before you decide to
set alert limits. The spectra are auto-scaled, so a long line does not, in itself, mean that it has a sig-
nificant amplitude value!
- 100 -
5.33 EVAM: Customizing the Leonova instrument display
In Condmaster, users of the Leonova Diamond and Leonova Emerald portable instruments can make
settings to control the default contents of the instrument display.
In the Measuring Point Data form, mark a vibration measuring technique and click the Leonova
tab (A). Make your preferred settings under:
l Instrument display (B),
l Default graph (C), and
l Default symptom in spectrum (D).
- 101 -
5.34 The HD ENV measuring technique

HD ENV ® is an enveloping technique used for early detection of impact related events such as gear
and bearing damage. Capable of detecting at a very early stage such machine problems which are
generally difficult to find in good time with non-enveloping techniques, the method utilizes cleverly
engineered algorithms for digital signal processing to obtain optimal data for trending purposes. HD
ENV is available for measurement with the Intellinova system and the portable Leonova Diamond and
Leonova Emerald instruments. HD ENV can be used on applications in a very broad RPM range.
Users accustomed to envelope measurement will find that HD ENV is as easy to use.
Predefined filters
A number of predefined filters are available to detect damages or anomalies in different stages of
development; two of which are specifically designed for gear and bearing monitoring and the others
for special applications. To suppress vibrations in different frequency ranges, different high pass (HP)
and band pass (BP) filters are available. The BP filters are named filter 1-4. Filter 1 and 2 are normally
used for special applications and filter 3 and 4 for gear and bearing damage.
l Filter 1 = 5 – 100 Hz
l Filter 2 = 50 – 1000 Hz
l Filter 3 = 500 – 10 000 Hz
l Filter 4 = 5000 – 40 000 Hz
Following the development of a damage with three measuring assignments

To follow an impact related damage throughout its development in all stages – from initial crack to
loose parts and spalling – it is recommended to set up three vibration measuring assignments:
l one HD ENV assignment with filter 4 for detection of early faults
l one HD ENV assignment with filter 3 for detection of more developed faults
l one velocity vibration assignment for detection of far advanced faults
Measurement results
An HD ENV measurement yields the following results:
l HD Real Peak, a scalar value expressed in decibels, representing the highest value measured
during the measuring cycle. HD Real Peak is the primary value to use to determine the severity
of a bearing damage.
l Time signal, measured simultaneously with HD Real Peak.
l Spectrum
More about HD ENV

HD Real Peak is suitable as the basis for alert limit definition, regardless of machine type.
When measuring with HD ENV, the measuring cycle is based on number of revolutions rather than
time. This maximizes the chances of capturing relevant signals in the course of one measuring cycle.
By adjusting the sampling frequency to rpm, spectrums are clear and concise also when measuring
cycles are long.
The number of spectrum lines affects the resolution and the measuring time. Doubling the number of
lines also doubles the measuring time. In cases where different fault symptoms, such as bearing fre-
quencies and multiples of 1X, are close together, a high resolution spectrum is preferred.
- 102 -
5.35 HD ENV, input data
To measure with HD ENV, the measuring technique needs to be activated for your measuring device
under System > Measuring system. HD ENV measuring assignments are created in the Meas-
uring Point Data form the same way as any other assignment.
The Measuring Point Data settings important to consider for HD ENV measurement are:
l Symptom enhancement factor: The Symptom enhancement factor (A) is used to improve
the signal-to-noise ratio. For applications with little electronic noise and few mechanical shock
phenomena, this factor can be kept low (1 to 5). Where noise and random shocks are fre-
quently occurring, it is recommended that the Symptom enhancement factor be set higher.
However, you should be aware that the higher this factor, the longer the measurement cycle.
The acquisition and calculation time is automatically updated when the parameters that affect
the time changes (B).
Please note that for portable instruments, symptom enhancement is set to ‘Off’ by default.
The Y axis unit in spectrum and time signal differs depending on whether or not symptom
enhancement is used:
Y axis unit Symptom enhancement off Symptom enhancement on

In spectrum HDeu HDeuE
In time signal HDeu HD2euE
l Envelope frequency: A number of predefined filters (C) are available to detect damages or
anomalies in different stages of development; two of which are specifically designed for gear
and bearing monitoring (Filter 3 and 4) and the others for special applications (Filter 1, 2, and
the high pass filters; for more information, see previous page).
l Time synchronous averaging (TSA) (D) is a technique that uses multiple measurements
providing a time signal where only repetitive signals synchronous with the RPM remains.
Please note that TSA is recommended for detection of gear faults only, not bearing faults (E).
TSA requires a trigger pulse from an inductive probe or the SPM tachometer probe connected
to the RPM input. See also "5.54 Additional measuring technique settings, TSA Advanced" on
page 125.
- 103 -
In the upper right corner of the Measuring Point Data form you’ll find additional tabs for settings of
the measuring device.
5.36 Cepstrum analysis
Measuring assignment setup for cepstrum analysis
Cepstrum analysis, also called quefrency analysis (or cepstral analysis), is especially useful for detec-
tion and analysis of bearing vibrations and gear faults in gearboxes. Its strength is finding periodic
components and repeated patterns in a time signal, which can be difficult to find in other types of
spectra.
Cepstrum is the forward Fourier transform of a logarithmic spectrum (‘a spectrum of a spectrum’).
Thus, while a frequency spectrum or FFT reveals the periodicity of a signal in the time domain, the
cepstrum reveals the periodicity of a spectrum. In the cepstrum, overlapping sets of sidebands or har-
monics will be separated, much like the spectrum separates repetitive time patterns in the wave-
form. The result of cepstrum analysis resembles a time signal, with the number of valid samples
equal to the number of lines in the corresponding spectrum. The X and Y axes units are called Que-
frency (time in seconds) and Gamnitude (dimensionless), respectively.
Cepstrum is not recommended in ‘noisy’ environments, where the signal may be subjected to dis-
turbance.
For the setup of cepstrum analysis, the following restrictions apply:

l Short time memory and Long time memory must both be set to ‘Full spectrum’ (A)
l The same settings must be selected for Time signal unit and Spectrum unit (B)
l Enveloping cannot be used (C)
l Quick Mode cannot be used (D)
l Averaging type must be set to ‘FFT linear’ (E)
l Overlapping cannot be used (F)
l True zoom cannot be used (G)
l Condition parameters and fault symptoms cannot be used
- 104 -
5.37 Input data for user defined measurement
Input data for user defined measurement:

l Select User defined (A). Input measured quantity (B), measuring unit (C).
l Input display format (D), display range (E), scale division (F). Set alert limits (G).
The form User defined has two variations. You make the selection on the technique form, either
Temperature or User defined (A).
When selecting User defined, you get the form shown above. Select incoming signal, Manual, mA or
Volt. Input the measured quantity (B, here “Coupling wear”, which becomes the name of the tech-
nique, and the measuring unit (C, ”mm”). You also input a display format (D) for your measuring unit,
using the ”#” character. ”#.#” means a one digit number with one decimal.
Set the graphics range (E) to cover the min. - max. variation you want to measure. Note that read-
ings outside of this range will be stored but require a scale adjustment under Graphics to become vis-
ible. Set a suitable scale division (F) for the graphics display.
You can set two lower and two upper alert limits (G). The presence of one upper alert limit is indicated
by a red band, the presence of two upper alert limits by a yellow and a red band above the green field.
Setting lower limits produces bands below the green.
- 105 -
5.38 Input data for temperature measurement
Input data for temperature measurement:

l Select Temperature (A).
l Input display range (B), scale division (C). Set alert limits (D).
l For Leonova Diamond and Leonova Emerald, define the emission factor (E).
For temperature, the measured quantity (Temperature) and the measuring unit (°C or °F, depend-
ing on your configuration under System > Settings) are preset. The display format is ”###.#”.
Set the graphics range to cover the min. - max. variation of the temperature you want to measure
(B). Note that readings outside of this range will be stored but require a scale adjustment under
Graphics to become visible. Set a suitable scale division (C) for the graphics display.
You can set two lower and two upper alert limits (D). The presence of one upper alert limit is indicated
by a red band, the presence of two upper alert limits by a yellow and a red band above the green field.
Setting lower limits produces bands below the green.
With Leonova Diamond and Leonova Emerald, temperature can be measured with an IR probe. To
obtain reliable and accurate readings in infrared temperature measurement, the emission factor of
the object measured on needs to be input in Condmaster. On the Leonova tab, select the appropriate
emission factor from the list (E). The default setting is ‘Aluminum, oxidized (Factor 0.4)’. Further
emission factors can be entered with the NEW button. Options on the list can be edited and deleted.
- 106 -
5.39 Checkpoint and comments download
Checkpoint:
l Input text (A).
l Select commets (B).
The input data for checkpoints is a line of text, describing what to check. You can download check-
points to the portable instrument and thus get a reminder to do the check. The maximum text length
is 35 characters.
It is possible to add one checkpoint per measuring point, except for the Leonova Diamond and Emer-
ald instruments for which an unlimited number of checkpoints can be added per measuring point.
While you do not record any data under Checkpoint, you can attach a comment. This enables you to
report on e. g. ”General machine condition”: you check for damage, leakage, cleanliness, safety haz-
ards, etc., and can set comments like ”Minor faults, fixed (no spare fuses)”, or ”Major damage (leak-
ing pipe)”, with an alert attached to the latter comment.
The comments window (B) opens the list of standard comments. A/T30 instruments take up to 16
comments. The Leonovas take an unlimited number of comments, so for them you can use the altern-
ative All. With Own selection you load only the comments you mark on the list.
- 107 -
5.40 Input data for lubrication round
l Select Lubrication data (A).

l Input "Grease" or "Oil", brand name or type (B).
l For grease, input quantity in grams (C).
l Add data for SPM LR/HR measurements (D).
The input of lubrication data is an option. To verify a shock pulse reading indicating bearing damage,
you should make a lubrication test, so it is useful to know what kind and how much lubricant to use.
You also have the option to make lubrication rounds (using the working mode Planning). With this
type of round, you print a work order with all lubrication points and lubricant data.
Under Measuring Point Data, select Lubrication data (A). Input ”Grease” or ”Oil”, brand name or
type (B) and, for grease, the recommended grease quantity in grams (C).
For SPM LR/HR measuring points, you can add the lubrication data on the lower part of the form (D).
This data is used by the LUBMASTER program (under Maintenance tab in the ribbon bar).
LUBMASTER helps you to set COMP nos. as well as alert limits for HR, LR, COND, and LUB, or you can
use it to find a better lubricant for your bearing. If you enter the necessary lubrication, load and tem-
perature data here, they will be available to LUBMASTER, else you can enter them when using that
program. For details, see under the heading "13. Lubmaster" on page 308.
Load in Newton is the actual load on the bearing. As an alternative, you can input the load ratio
(actual load P divided by the bearing’s dynamic load rating C, expressed in percent). You find ”dy-
namic C” in the bearing catalogue.
Under EP quality, input either the FZG no. 7 (no EP additives in the lubricant) or 12 (lubricant con-
tains EP additives).
- 108 -
5.41 Orbit analysis
Orbit analysis is a vibration measurement function. An orbit represents the path of a shaft centerline
during rotation. The two- dimensional orbit graph is used to analyze shaft centerline movement,
which may indicate rubs, unbalance, misalignment or oil whip, in machines equipped with journal
bearings.
The data required for the orbit analysis are collected by means of 1) a two channel simultaneous vibra-
tion measurement, where two displacement transducers are placed 90 degrees from each other, and
2) a trigger signal from a tachometer probe. The amplitudes of channels X and Y are plotted, resulting
in a graph of the shaft centerline movement. The displacement transducers can be substituted for
accelerometers and the orbit parameters set up accordingly, in which case the measurement result is
an orbit graph of machine movement.
Orbit measurement with displacement transducers requires the orbit interface 15315 to be used with
Leonova Infinity (Leonova Diamond does not require an interface). It also requires setting up two
transducers particular to orbit in the transducer register. For measurement with accelerometer or
velocity transducers, use the two- channel measuring cable CAB51 (Leonova Infinity) or CAB89
(Leonova Diamond). For Intellinova Parallel EN, the displacement signal interface INO33 is required
for orbit measurement.
Go to System > Transducers and create two displacement type orbit transducers for the X and Y
axes, respectively. For an 8 mm diameter proximity probe, the Sensitivity (B) is normally 7,87
V/mm (7,87 mV/μm). For other probes, please turn to the TD sheet for information about their sens-
itivity. Enter Max. frequency (C) as appropriate.
When using Leonova Infinity, mark the check box Transducer supply (A). This will bring up addi-
tional parameter settings. Enter Min. bias range (V) = 0 and Max. bias range (V) = 24. Set Set-
tling time to 2 seconds and click OK. If using Intellinova Standard, the check box (A) should normally
be unmarked as the signals normally are received from buffered outputs. Please note that for
Leonova Diamond, the Transducer supply checkbox shall not be marked.
In the measuring point tree, right hand click on the measuring point where orbit is to be measured
and choose Edit. Select Orbit under Available techniques and drag it to the upper window. To the
right in the Measuring point data form, the parameters that need to be set for orbit measurement
are now displayed. Please note that only one orbit assignment per measuring point can be set up.
- 109 -
5.42 Orbit analysis, input data
Normally, Transducer = “Remote” is recommended. This means that measurement is carried out
on the buffered outputs of the machine protection system, thus preventing any interference with
machine operation. With a portable transducer, the transducer settings in Leonova are used instead.
In the Transducer: Name dropdown lists (A and B), select the “orbit transducer” previously created
in the transducer register. The transducer Sensitivity is input in V/mm (mV/μm). With Transducer
set to “Portable”, this setting is not displayed.
For best results, it is strongly recommended that a measured rpm value be used in connection with
orbit measurement. If rpm measurement cannot be done, enter “No” in the Measure RPM sim-
ultaneously field. This will bring up a new field named RPM, where you should input the shaft rpm
value manually.
Max RPM can be set to either 24 000 (= 256 samples per revolution) or 48 000 (= 128 samples per
revolution). Select sampling rate depending on the application measured; e.g. for a 21 000 RPM tur-
bine, choose 24 000 (48 000 will also work, but will have lower sampling rate). For an application
rotating > 24 000 up to 48 000 RPM, choose 48 000 (24 000 will not work).
For Filter type, the default setting is Bandpass, showing frequencies at rpm ±10%. With the filter
type set to Lowpass, all frequencies above the selected multiple of shaft speed (Orders, 1-5) are
filtered out. The Orders setting is used to calculate the center frequency for bandpass mode and the
upper frequency for lowpass mode, respectively.
In the Number of revolutions field, input the number of shaft revolutions to acquire and display in
the orbit graph. Number of orbit results to save sets the number of orbit results saved in the data-
base and is a means to limit database size. “Unlimited” means all orbit results will be saved and
never overwritten.
For an evaluated measurement on the green - yellow - red scale, input Alert limits for the X and Y
axes according to supplier recommendations.
- 110 -
5.43 Viewing Orbit measurement results
Orbit measurement results can be accessed from the measuring point tree as well as from the Graph-
ical Overview, using either the Graphics or Measuring results button in the ribbon bar.
Right clicking on a result in the Graphic evaluation window allows you to see either the orbit graph or
the measuring results (A). The value showed in the Graphic evaluation is the longest vector, i.e. the
largest distance measured from the orbit centre.
Right clicking on a result in the Measuring results window brings up a menu of options (B), allowing
you to further evaluate and/or comment on the measurement.
The orbit graph (C) shows an overlay of the graphs for each measured revolution plus their average.
Each individual revolution can be selected, as well as the average of all revolutions (displayed by
default). The current graph is marked in blue. A blue arrow shows the angle and X/Y values at that
angle. The arrow can be moved in the orbit graph using the mouse.
Right clicking in the graph displays a menu of further options.
- 111 -
5.44 Viewing Shaft Centerline Plot
Shaft centerline plot is a function available with the portable instrument Leonova Diamond. Especially
useful for assessment of lubrication during start-up of a machine with journal bearings, the plot dis-
plays changes in radial rotor position over a range of speed.
Settings for Shaft centerline plots are made in Leonova Diamond. The results are uploaded to Cond-
master with the measuring round and can be viewed via the Comments function.
To see a Shaft centerline plot, select the measuring point in the Measuring point tree, then click on
the Comments button in the tool bar. In the Comments window, right-click on the Shaft centerline
comment and select ‘Open attachment’ from the popup menu (A). The Shaft Centerline window is
opened, displaying one or more graphs of the measurements (B).
Click the ORIENTATION button (C) to input transducer positions, and the BEARING CLEARANCE
button (D) to input bearing clearance. Specify shaft centerline starting point reference via the BOT-
TOM/CENTER/TOP button (E) :
l Bottom: Use the bottom starting point reference for a horizontal machine train.
l Center: Use the center starting point reference for a vertical machine train.
l Top: Use the top starting point reference for overhung rotors, such as fans and compressors.
Click the PREVIOUS / NEXT buttons (F) to see:

l the assignment settings made in Leonova Diamond, or
l any notes that may have been input in Leonova Diamond.
The Shaft centerline plots are available wherever Comments are accessible in Condmaster; i.e. in
graphs etc.
- 112 -
5.45 Multi-channel simultaneous vibration measurement
Three channel vibration spectrum
Two and three channel simultaneous vibration monitoring requires the ‘EVAM’ measuring technique
to be activated in Condmaster Ruby. It can be used with Intellinova Parallel EN, Airius wireless vibra-
tion sensors, and the portable instrument Leonova Diamond.
With multi-channel simultaneous vibration measurement, machine movement can be studied in two
or three dimensions by observing the difference between the phase angles measured on the chan-
nels.
Measurement requires setting up two (or three) vibration assignments with identical parameters in
Condmaster Ruby. Condmaster Ruby displays the RMS values for DISP, VEL and ACC for the respect-
ive channels. Three graphs are available for each measurement: spectrum, phase spectrum, and time
signal.
To connect the transducers to the Leonova Diamond transducer input, the measuring cables CAB89
and CAB88 are used for two and three-channel measurements, respectively.
Two cursors show the difference in phase angle at the actual frequency. A phase is a time delay ex-
pressed in degrees of rotation. Leonova Diamond calculates the time delay between the passage of
the tachometer pulse and the peak of the frequency component of interest from the vibration trans-
ducer at the speed of rotation. The value presented is a relative angle, not an absolute, because there
is no compensation for phase lag in the transducer or the electronic circuits.
- 113 -
5.46 Setting up multi-channel vibration measurements
l In the Measuring Point Data form, select '2 or 3 channel vib' under Techniques (A).
l Create two (or three) measuring assignments (B).
l Set up data for all channels (C).
l Select EVAM measurement parameters (D).
To measure vibration concurrently on multiple channels, you must first add the technique ‘2 or 3 chan-
nel vib’ to the measuring point. Depending on your choice in the Vibration Guide then opened, two
(or three) measuring assignments for EVAM are created for the measuring point. They should all be
given descriptive names and the necessary settings made for each of the channels. Please note that
the measuring assignments involved must have the same frequency range, transducer type and num-
ber of lines in spectrum.
Several two or three channel vibration measurements may be set up per measuring point, providing
the possibility to use more measuring techniques, in two or three directions, such as velocity, accel-
eration and enveloping, for instance.
The measurement procedure is the same as for the corresponding measurement with a single trans-
ducer.
The cable CAB91 is used to connect the triaxial transducer 90546. Note that this transducer has:
l channel 1 = Z
l channel 2 = X
l channel 3 = Y
- 114 -
5.47 Bump Test
The Bump Test is a function available with the portable instruments Leonova Infinity and Leonova Dia-
mond.
A bump test is an impact test carried out on a machine that is not running in order to determine its
natural (resonant) frequency. The test reveals whether resonance is the cause of high noise or vibra-
tion levels.
The natural frequency of the machine is the frequency where it starts to vibrate as a result of an
impact. When this frequency coincides with that of the machine at running speed, or any other signal
generated by the machine, the signals will be amplified, causing a higher than normal vibration level
which may ultimately cause machine damage or failure. If the natural frequency is at or close to the
normal running speed, steps should be taken to change this frequency.
The Bump Test parameters are set up in the instrument and after the measuring round (or file) is
uploaded, the settings and measuring results can be viewed in Condmaster.
To see a Bump test result, mark the measuring point in the Measuring point tree, then click on the
Comments button in the tool bar. In the Comments window then displayed, double click on the com-
ment (A). Select ‘Edit comment’ (B) to see comment data and edit them if required, or select ‘Open
attachment’ (B) to see the bump test diagram.
In the Bump Test window, click the Settings button (C) to see transducer data and settings, and
the Graph (D) button to return to the diagrams.
The natural frequency is the highest line in the spectrum. With a right hand click on the spectrum, it
can be stored as reference spectrum for any measuring assignment, copied to clipboard, or saved as
file in .uff or .txt format.
The diagrams are also available via the Edit function when viewing comments in graphs etc.
- 115 -
5.48 Frequency Response Function, FRF
FRF results can be viewed via Comments (A). In the FRF window, users can toggle between assignments settings, a summary
of the measurements, time signals and spectrums for each hammer hit, and notes.
Frequency Response Function (FRF) is a function available with the portable instrument Leonova Dia-
mond. It is used to measure the vibration response (natural frequencies) of a machine structure, sim-
ilar to the Bump test (see previous page). FRF however is more sophisticated, measuring the
response resulting from a known applied input by using an impact hammer and a vibration transducer
connected to Leonova Diamond’s vibration input using a split cable (please see the ‘Leonova Diamond
User Guide’, document no. 71950 for more information).
The FRF measuring assignment is set up in Leonova Diamond and after the measuring round is
uploaded, the settings and measuring results can be viewed in Condmaster.
To see an FRF result, select the measuring point in the Measuring point tree, then click on the Com-
ments button in the ribbon bar. In the Comments window, right-click on the FRF comment and select
‘Open attachment’ from the popup menu (A). The FRF window is opened, displaying a summary of the
FRF measurements (B) with coherence, accelerance and phase information.
Click the PREVIOUS/NEXT buttons to see:

l time signals and spectrums from each individual hammer hit (C); toggle between hits by click-
ing on the numbered tabs in the upper right corner of the window (D),
l the FRF assignment settings made in Leonova Diamond, or
l any notes that may have been input in Leonova Diamond.
Clicking on the ‘Spectrum’ button (E) in the upper right corner of each individual graph opens a lar-
ger version with zoom options etc. Clicking on the ’...’ button (F) in the middle individual graph opens
a menu with scale unit options (see below).
The FRF diagrams are available wherever Comments are accessible in Condmaster; i.e. in graphs etc.
- 116 -
Default scale unit for ’FRF’ is Accelerance. Click on the ’...’ button to find the following scale units to
be viewed:
l Accelerance [(m/s2)/N] (LOG)
l Mobility [(mm/s)/N] (LOG)
l Compliance [μm/N] (LOG)
l Effective mass [kg] (LOG)
l Impedance [N/(mm/s)] (LOG)
l Stiffness [N/μm] (LOG)
The frequency response is calculated by dividing the output response from the transducer, in V/g
(m/s2), by the input excitation from the hammer in V/N (force). Therefore, the most common scale
unit is Accelerance [(m/s2)/N] (LOG). If the signal is converted from ACC (acceleration) to VEL (velo-
city), the unit will be expressed in Mobility [(mm/s)/N] (LOG), and if the signal is double integrated
from ACC (acceleration) to DISP (displacement), the unit will be expressed in Compliance [μm/N]
(LOG).
The most common transducer type used in this context is an accelerometer, and the most common
scale unit type is Accelerance. Note that the different possible formulations above can all be con-
sidered frequency response functions since each of these formulations can be numerically integ-
rated/differentiated into equivalent displacement/velocity/acceleration over force relationship.
Accelerance, Mobility and Compliance in the frequency plane is equal to reaction to input, i.e. how the
machine or machine part reacts to the input/force.
Effective mass is the inverse of Accelerance, Impedance is the inverse of Mobility, and Stiffness is the
inverse of Compliance.
Effective mass, Impedance and Stiffness in the frequency plane is equal to resistance to movement,
i.e. how the machine or machine part reacts to the movement after the input.
- 117 -
5.49 Run Up and Coast Down measurements
Set up a Run up/Coast down comment in Standard comments:

l Create a new standard comment and name it e.g. "Run up/Coast down".
l Click the '...' button under Run up/Coast down (A) to assign a default comment to it.
Like the Bump test and FRF, run up and coast down measurements are methods for resonance test-
ing, available with Leonova Infinity and Leonova Diamond.
During run up and coast down, machines go into resonance once a certain speed is reached. This
speed is known as the critical speed. The critical speed depends on a number of variables, such as
shaft diameter and length and how the shaft is supported. Operation at or near critical speed should
be avoided because vibration will increase and may build to unsafe levels. Operational speed should
be +- 30% from the critical speed in order to avoid influence of resonance. Please note that
machinery may have multiple resonance frequencies.
Normally, rotating machinery operate above their critical speed. Therefore, the rotor must pass
through its critical speed(s) during run up and coast down. Time spent within the critical speed ranges
should be kept to a minimum. If the run up or coast down process is too slow, the machine may be
subject to excessive vibration. The critical speed range(s) should be passed as quickly as all concerns
allow.
Passing through critical speed is usually safe, provided there are no excessive exciting forces such as
unbalance or misalignment, and damping is sufficient. However, some damages may cause the crit-
ical speed to shift closer to the normal operating speed of the machine. This is a condition to be watch-
ful of, as normal running speed must be sufficiently far from the critical speed. If the critical and
running speeds should be close with no present damage, stiffening the structure e.g. may solve the
problem.
To start using Run up/Coast Down, a Run up/Coast Down comment must first be defined under
Registers/Standard Comments. Once the comment is created, its code and color can be edited.
Add the comment to the desired measuring point, create a measuring round and download it to
Leonova. The parameters for Run up/Coast Down are set in the instrument, then uploaded to Cond-
master where the measurement results can be found under Comments for the measuring point in
question by right-clicking and selecting ‘Open attachment’ from the popup menu. They are also avail-
able via the Edit button.
- 118 -
5.50 Working with the Run Up and Coast Down results
To see a run up/coast down result, mark the measuring point in the Measuring point tree, then
click on the button Comments in the tool bar. In the Comments window then displayed, double click
on the comment to see its data and edit them if required. To see the run up/coast down diagram, click
on the button Run up/Coast down in the Comments window tool bar. The diagrams are also avail-
able via the Edit function when viewing comments in graphs etc.
Three types of diagrams can be viewed:

l Waterfall diagram, displaying the current diagram in blue. Mark a measuring result, then the
arrow keys on your keyboard can be used to step between diagrams. With a right hand click on
the waterfall diagram, it can be stored as reference spectrum for any measuring assignment.
l Nyquist diagram, showing the phase angle and amplitude in a single diagram, with the cur-
rent diagram in green. A phase is a time delay expressed in degrees of rotation. The Leonova
calculates the time delay between the passage of the tachometer pulse and the peak of the fre-
quency component of interest from the vibration transducer at the speed of rotation. The value
presented is a relative angle, not an absolute, because there is no compensation for phase lag
in the transducer or the electronic circuits. In the Nyquist diagram, RPM is displayed in the list
of measurements only.
l Bode diagram showing two separate diagrams with vibration amplitude (DISP, VEL or ACC)
and phase angle on the Y axis, respectively, and RPM om the X axis. All measurements are dis-
played in time sequence. The current measurement is shown in green.
In all diagrams, a green dot shows the position of the measurement marked on the list.
- 119 -
5.51 Measuring techniques in the tree structure
To see all measuring point data for a component, go to the tree structure. Double click on all meas-
uring point folders belonging to the component. Each measuring technique is shown as a symbol. If it
is marked with a “+”, you can click it open to see measuring assignment details.
From there, you can go directly to any technique form. Mark the measuring point folder and press
ENTER (opens the main data form of the measuring point), or mark the measuring technique and
press ENTER (opens the marked measuring technique).
- 120 -
5.52 Seamless measurement technique

Supported in the online system Intellinova Parallel EN, a Seamless measurement assignment infin-
itely monitors the vibration signal, saving a time record to the Condmaster database only when a
user-defined trigger level is reached.
When to use it
Seamless measurement is suitable for uninterrupted monitoring of critical equipment where

machine failures are relatively few and far between, but where a potential damage or breakdown may
develop very quickly and may potentially have serious or catastrophic consequences.
If the operating condition is usually stable for long periods of time, measurement at short intervals
may not be warranted since it creates large amounts of measurement data. If at the same time it is
critical that the system reacts immediately to any changes in vibration levels, then seamless meas-
urement is ideal; the method captures and quickly responds to extremely short events happening
rarely and/or unexpectedly, but does not store large amounts of measurement data to the database
(more information below).
The difference between seamless and other measurement techniques

For most other measurement techniques, vibration or shock pulse levels are measured in intervals
according to measurement assignment settings and - regardless of the measured value - the meas-
urement data is saved to database after extensive processing (FFT etc.).
A Seamless measurement assignment, on the other hand, is infinite. Capable of sampling a vibration
signal at a very high sampling rate, it will save an unprocessed portion of the time signal to database
only when the user-defined trigger level is reached. The sampling rate and length of the time record
saved is dependent on the measurement assignment settings for Fmax (Upper frequency) and the
number of lines of resolution (Lines in spectrum).
- 121 -
Configuring a Seamless measurement assignment
Setting up a measurement assignment for seamless measurement is straightforward. There are, how-
ever, some restrictions:
l A maximum of four measurement assignments per DSP may be set up for seamless meas-
urement.
l A maximum of 60 measurement results per hour (A) can be transferred from the DSP to the
Condmaster Entity Server (CES).
The Trigger level (B) is entered in g for acceleration, mm/s for velocity, or in µm for displacement.
NOTE: We recommend that you do not change the default setting 'OFF' for Long time memory, oth-
erwise it may result in large amounts of data. We also recommend that you be careful when con-
figuring alert limits; if you set them too low, this too can quickly generate very large amounts of data.
- 122 -
Activating a digital status output
When the trigger level is reached, Intellinova Parallel EN can respond immediately and activate a
digital status output, e.g. triggering a remote alert.
Digital outputs are set up on the Online tab in the Measuring Point Data window. Click the ellipsis
(…) button under Status output (A), then click the NEW button (B) to configure the status output
(C).
For more information about the parameters in the Status Output Configuration window, see sec-
tion "15.28 Setting up status outputs for Intellinova Parallel EN" on page 370.
Setting up a Condition
Conditions are set up on the Online Advanced tab in the Measuring Point Data window. For the
Seamless measuring technique, the setting for Conditions, checked during measurement works
in the same way as for other measuring techniques, with the difference that checks are made when
the measurement is completed. The measurement is saved if the conditions are met.
If conditions are used together with digital status outputs: conditions must be fulfilled in order for the
digital status output to be activated. When the measurement is completed, a check if the conditions
are met is made (if so, the measurement is saved).
Click the elipsis (...) button under Conditions, checked during measurement (D) and see section
"15.26 Measurement conditions for Intellinova Parallel EN" on page 366 for more information about
the set up.
- 123 -
5.53 Time Signal Recording measurement technique
Supported in the online system Intellinova Parallel EN, Time Signal Recording is a function for tak-
ing longer recordings of time signals. It can be used to capture and analyze rare fault occurrences, for
example. If there is a need to analyze a particular section of the time signal, it can be exported to
third- party analysis software (see section " 16.15 Exporting spectrums and time signals " on
page 419). On a computer with sound card you can also listen to the time signal, played back as a
wav file.
A time signal recording is performed during a predetermined time period (A) and is typically set up as
a time- based measurement (B), but can also be set up as a " 15.22 Group measurement " on
page 359or "15.23 Linked measurement" on page 361. Alternatively, a trigger can be set up to start
the measurement on the Online Advanced tab (C).
The following time signal units are available: Disp, Vel, Acc and envelope.
- 124 -
NOTE: To preserve database resources, Long time memory (D) is set to OFF by default. If you
change this setting so that time signals are saved to the long time memory, you are strongly recom-
mended to activate the Automatic removal of results function, otherwise the database size can
grow very fast, see "16.20 Automatic removal of results" on page 430.
5.54 Additional measuring technique settings, TSA Advanced
TSA Advanced is an addition to TSA (Time Synchronous Averaging) and useful when measuring on
applications with varying loads (e.g. gearboxes). The purpose of the function is to obtain good TSA
measurement during representative conditions, i.e. to avoid measuring when the gearbox is idle or
has very low load, as well as avoiding extreme shocks that may adversely affect the measurement
result.
TSA Advanced can only be activated when TSA has been chosen as averaging technique. At present,
the TSA Advanced functionality works in Intellinova Parallel EN with the HD ENV, SPM HD, LR/HR HD
and Vibration measuring techniques.
A TSA measurement consists of a number of individual measurements. With TSA Advanced enabled,
the following applies to each individual measurement:
l Threshold = threshold value (unit depends on measuring technique), the value must be
above the set level during measurement (set to avoid measurement during idling or at very
low load).
l Upper limit = peak value (unit depends on measuring technique), the value must be below a
set level during measurement (to avoid measuring extreme shocks).
l Number of sections = default 4, number of sections in an individual measurement, each of
which must meet the threshold and upper limit for the measurement to be included in the TSA
calculation. If this is not the case, the individual measurement is discarded (i.e., if the load
goes down and falls below the threshold during an individual measurement, the individual
measurement will be discarded) and new attempts might be made (see Number of retries).
- 125 -
l Number of retries = default 10, number of retries to be made until an individual meas-
urement meet Threshold and Upper limit (and Number of sections) conditions. If these con-
ditions are not met and the number of retries is exceeded, the entire TSA measurement is
discarded (not just the individual measurement).
Threshold and Upper limit are parameters that must be met during an individual measurement,
while Number of sections and Number of retries are parameters that determine how often the
Threshold and Upper limit criteria should be tested.
NOTE: Combining long measurement times and a large Number of retries poses a potential risk for
very long "waiting times" (days in worst case) when the TSA measurement occupies one of the pro-
cesses in the instrument.
- 126 -
5.55 Setting up measuring assignments for Airius vibration sensors

NOTE : It is assumed that 1) Airius vibration sensors have been added to Condmaster via the
SPM Connect app, see Airius QuickStart, document no. 72241 for details (or added via Condmaster,
see Condmaster Installation and System Administration manual, document no. 72301 ), and
2) communication between the sensor, CES and Condmaster have been set up via the SPM Connect
app, see Airius QuickStart, document no. 72241 (this is required for measurements to work).
The following measuring techniques can be used with Airius vibration sensors:
l Vibration
l 2 or 3 channel vibration
l ISO 10816
l Temperature - set up as a condition parameter, see below
Airius vibration sensors are three-axial and can thus perform measurements in three directions. The
direction of the screws on the sensor corresponds to the z- axis (see markings for z, x, y on the
sensor). Wireless vibration sensors are added as online units in Condmaster, and therefore the instru-
ment Online must be selected when setting up measurement assignments.
Changing name and default settings per sensor

Name and default values for Measuring interval etc. can be changed per sensor under Online Sys-
tem Overview > Registered units > Edit.
The default Measuring interval is set to 12 hours (= 2 measurements/day) but can be changed as
required. (NOTE: a tight measurement interval affects battery life considerably.)
The Operational time is set to 24 hours a day all days but can be changed as required.
- 127 -
The default value for the Measuring range expressed in ‘g’ can be changed. The smaller the range
the better the measurement resolution, but also the higher the risk of the vibration signal being out of
range.
Setting up vibration measurements

NOTE: It is assumed that components and measuring points have been added as necessary, see "3.1
Creating machines and components" on page 40 and "4.1 Creating a measuring point" on page 45.
1. Add a vibration measurement technique (Vibration, 2 or 3 channel vibration, or ISO 10816)

and add measuring assignments as required (A). For more information, see the section for
the vibration technique you selected:
l "5.20 EVAM assignments, input data" on page 88
l "5.46 Setting up multi-channel vibration measurements" on page 114
l "5.18 ISO 10816, input data" on page 84
2. For each measuring assignment, go to the Online tab (B) and select the correct sensor and
direction (z, x or y) under Address (C). (Default values for Measuring interval etc. can be
changed per sensor under Online System Overview > Registered units > Edit, see
above.)
Example: the component Exhaust fan have two wireless sensors (two measuring points named
Motor and Fan bearing) both measuring Velocity (RMS values) in three directions (Vertical,
Axial, Horizontal), two times a day.
After selecting sensor and direction in the Online tab, the current settings that can be done
under the Settings tab are displayed. The settings look roughly the same as for other instru-
ments, but with some limitations on the selection of different parameters, see below.
- 128 -
3. Go to the Settings tab (D), Name the assignment and perform other settings as required.
For information on the parameters and its options for each vibration measuring technique,
see
l "5.20 EVAM assignments, input data" on page 88 and forward
l "5.46 Setting up multi-channel vibration measurements" on page 114
l "5.18 ISO 10816, input data" on page 84
NOTE: for the Airius sensors, Time signal unit is always stored as acceleration (Acc) and the
Lower frequency parameter only affects spectrum (it does not affect the time signal which
therefore also contains frequencies below this limit). Regarding Envelope frequency, Filter 3
is available.
- 129 -
4. Go to RPM (E), select (or unselect for fixed speed) variable speed, and enter required
RPM values.
5. For variable RPM, select an assignment, go to RPM 1 (F) under Online, and choose ‘Cal-
culated RPM’ to calculate the RPM from spectrum or choose a global value source to fetch the
RPM as a global value. For details and settings regarding calculated RPM, see "Calculated
RPM settings" on page 132 at the end of this section. For information on how to set up RPM
as a global value, see "15.29 Global values for Intellinova Parallel EN" on page 372.
6. Go to the Online Advanced (G) tab for advanced settings.
l Conditions (H) are checked immediately after the measurement, see "15.26 Meas-
urement conditions for Intellinova Parallel EN" on page 366 for information on how to
set up a condition.
l Filtering of results (I) can for example be used to limit the amount of values stored
to the database, see "15.4 Filtering of measurement results in LinX and CES" on
- 130 -
7. When all settings for each measuring assignment have been made, select Save in the lower
left corner of the Measuring Point Data window.
Setting up temperature measurement
The Airius vibration sensors can perform temperature measurement. Temperature measurement
with set alert limits can for example be used as a further indication of condition. Temperature meas-
urement is set up as a condition parameter roughly in the same way as for Intellinova Parallel EN, see
section "15.33 Temperature measurement" on page 380
- 131 -
Calculated RPM settings
When setting up vibration measurements for Airius sensors, it is possible to select Calculated RPM
in the Measuring Point Data window. By default, the setting for the calculated RPM is 1 pulse per
revolution, and the chosen axis for the RPM value is the same as the measuring assignment.
To edit the settings for how the RPM is calculated:
1. Go to Online > Online System Overview and select Online Unit Configuration (A) from
the 'more options' button for an Airius sensor.
2. Select the RPM tab (B) and select EDIT (C).
3. Name (D) is set to Calculated RPM by default but can be changed as required.
4. Number of pulses per revolution (E) is set to 1 as default. The function looks for the
highest peak value within the min and max RPM range specified in the Measuring Point Data
window. For example, if the min and max RPM is 600- 6000, the function will look for the
highest peak value in the 10-100 Hz range in the spectrum. Suppose the number of pulses per
revolution is changed to, for example, 4. In that case, the function looks for the highest peak
value in an area higher up in the spectrum (4x10-4x100 Hz) and then divides the value by 4 so
that it falls within the specified min and max rpm interval.
If the peak value is equal to or higher than Min signal level (H), the value is used to calculate
the RPM. If the peak value is lower than Min signal level, the measurement will be discarded
due to the RPM value being out of range.
5. Channel (F) is set to Channel 1 and cannot be changed.
6. Axis for RPM value (G) is set to Same as assignment by default but can be changed to any of
the drop-down list alternatives as required. A general recommendation is to select the axis
where the RPM signal is most evident.
7. Min signal level (H) is blank by default, meaning that a predefined routine is used which,
based on a number of parameters, looks for one clear peak within the specified min-max RPM
interval. Min signal level is mainly used to indicate that the machine is running (not standing
still).
- 132 -
5.56 The Phase and Cross-channel phase symptoms

Introduction to the Phase and Cross-channel phase symptoms
The Phase and Cross-channel phase symptoms in Condmaster can be used to trend the devel-
opment of phase differences over time, and raise alerts for changes that may indicate machine prob-
lems. The Phase symptom takes into account either the phase angle alone, or a combination of
amplitude and phase, while Cross-channel phase only looks at phase angle. For more information
on setting up alerts, see "Alerts for the Phase symptom" on page 136 and "Alerts for the Cross-chan-
nel Phase symptom" on page 138.
The Phase symptom can be examined in various graphs using the Polar plot function (for more
information, see "9.45 The Polar plot function" on page 247). The Cross-channel phase symptom
can be viewed in trend graphs in the Graphic Evaluation window, or in the alert list (for more inform-
ation, see " 12.1 Graphics functions in Condmaster Ruby " on page 282 and " 9.3 Alert list " on
page 163, respectively).
The absolute amplitude value and the development over time for the amplitude and phase com-
bination can both be used to assess machine health. When trending amplitude and phase, a change in
these values may signal that something has happened, that can ultimately lead to damage or break-
down.
Relative and absolute phase

Phase analysis can be useful to detect changes in vibratory motions that might otherwise go
unnoticed. For instance, it can facilitate the detection of imbalance, shaft crack, structural resonance,
and more.
Phase is the relative time difference between two signals, measured in units of angle rather than in
units of time. In vibration analysis, phase is measured using absolute or relative techniques:
l The Phase symptom is based on single-channel measurements with a fixed, once-per-shaft-
revolution reference signal from a tachometer. This technique is known as absolute phase. The
Phase symptom can be set up for any integer multiple of rotational speed (up to the meas-
uring assignment’s Upper frequency (Fmax) setting). Absolute phase is expressed as a lag-
ging angle with values between 0° and 360°.
l The Cross-channel phase symptom, on the other hand, is based on simultaneous meas-
urement on two channels – one of which represents the reference – at the same frequency.
This is relative phase, which is expressed as phase lead/lag in values between -180° and
+180°. Cross-channel phase can be calculated for any integer or decimal number up to the
Fmax setting.
Absolute phase thus compares a vibration signal to a once-per-turn reference pulse, while relative
phase looks at the timing between two vibration signals with the same frequency. A phase change
means that the timing between the tachometer pulse and the maximum positive value of the filtered
vibration has changed.
NOTE: If displacement sensors are used, be aware that erroneous data may result, because there is
no runout compensation in the calculation of the phase symptoms.
- 133 -
5.57 Settings for the Phase and Cross-channel phase symptoms

Phase and Cross-channel phase are configured as symptoms in Condmaster (for more information
on how to add symptoms to measuring assignments, see section "5.30 EVAM: Add fault symptoms
and symptom groups" on page 98).
The Phase symptom can be activated for measuring assignments with the following measuring tech-
niques:
l Vibration (including standard enveloping)
l HD ENV
l SPM HD
l LR/HR HD
NOTE : Time synchronous averaging (TSA) must be used for accurate results. Furthermore, it is
strongly recommended that symptom enhancement is not used.
The Cross-channel phase symptom is calculated from the time signals of two-channel vibration
measurements. The time signal must be saved in short and long- time memory. Using time syn-
chronous averaging (TSA) is recommended, and for variable speed machines, order tracking is a fur-
ther recommendation.
Phase symptom settings

When adding or inserting the Phase symptom, input a number of orders (A; integers only, not
exceeding the Fmax setting):
When changing the Orders parameter, the phase symptom name is automatically updated to reflect
the change; e.g., entering 2 orders will automatically result in the symptom being named “Phase 2X”.
As described above, the Phase symptom uses absolute phase, comparing the vibration signal to a
periodic reference pulse. In a polar plot, one cycle of that reference pulse represents a complete
circle, i.e., a 360° phase angle. Thus, the phase lag is a value between 0° and 360°.
Cross-channel phase symptom settings

When adding or inserting the Cross-channel phase symptom, enter a number under Orders (A;
integer or decimal number, not exceeding the Fmax setting):
- 134 -
When changing the Orders parameter, the symptom name is automatically updated to reflect the
change; e.g., entering 3,5 orders will automatically result in a symptom named “Cross-channel phase
3,5X”.
If there is more than one two-channel vibration measurement assignment on the measuring point,
select which Channel 1 should be the reference channel by ticking/unticking the appropriate check-
box (B):
For the Cross-channel phase symptom, the result of the comparison between the two vibration sig-
nals is a either a phase lag or a phase lead with a value between -180° and +180°.
To set up alert limits, see "5.58 Setting up phase alerts" on the next page.
- 135 -
5.58 Setting up phase alerts

The Phase and Cross- channel phase symptoms can be used to generate alerts for changes in
phase angle, or a combination of phase angle and synchronous amplitude (1X, 2X, etc.).
As with all alert leves, phase alerts should be based on baseline measurements that determine the
normal behavior of the machine or component. For general information about setting up alerts, see
"5.11 Overview, alert limits and alert delay" on page 77.
Alerts for the Phase symptom

For the Phase symptom, two options (A) are available for setting alert levels:
The Level alert limit type is based on degrees of absolute phase only, displaying results in a trend
graph with a 0-360° Y-axis (B):
- 136 -
NOTE: The Y-axis of the phase diagram is somewhat special because it is folded (C). For example, if
the phase value is increasing towards 360°, it will not go beyond that value but start over at 0°. The
same is true for a decreasing phase value passing 0°; in this case, the value will shift to 360°. The
phase Y-axis is also special because there is no correlation between a high value and severity.
The Polar plot displays the development of phase and amplitude in a graph using polar coordinates
(D):
Based on where in the polar plot the readings are usually located, user-defined, yellow and red alert
circles are set, the radius of which define what degree of vectorial change (i.e., the magnitude of the
movement in the polar plot) is within acceptable levels. Whether it is the amplitude or the phase – or
a combination of the two – that changes into a value outside the acceptance region, an alert will be
raised.
To set up an area alert for the polar plot in the Limit Guide window:
1. Input the Phase and Level values (E). Together, these values define the center of the yellow
and red circles in the polar plot.
2. Under Radius (F), input a radius that will determine the threshold perimeter of the red alert
circle; any value outside of the circle will trigger an alert.
3. Under Yellow limit (G), input a percentage of the alert circle radius. This percentage number
defines the radius of the yellow alert circle; any values outside of this circle will raise an alert.
- 137 -
Alerts for the Cross-channel Phase symptom

Alerts for Cross-channel phase are level alerts, based on changes in phase angle and shown in a
trend graph with a +/-180° Y scale (A):
NOTE: The Y-axis of the phase diagram is somewhat special because it is folded (B). For example, if
the phase value is increasing towards +180°, it will not go beyond that value but start over at -180°.
The same is true for a decreasing phase value passing -180°; in this case, the value will shift to
+180°. A high phase value does not necessarily imply a more severe condition than a low value.
- 138 -
6. Measuring point tree
6.1 Creating your own folder
l Click on the arrow beneath the Measuring Point folder (A) and press SHIFT+F5 (or click on the
yellow folder icon, C)
l Name the folder and click OK (B)
After copying and editing the first component three times, the component folder contains four
machines. All their measuring points are in the measuring point folder. Both folders are sorted alpha-
betically by number.
You do not have to change this simple tree structure. However, building your own tree structure
beneath these permanent folders has many advantages and does not take much time. The idea is to
sort your machines by either location and/or production process, to give you a easy to grasp overview
over the monitored parts of the plant, and a fast means to create measuring rounds.
Your first own folder is placed beneath the standard structure. Click on the arrow (A) to mark it, then
press F5 for ”new folder” (or click on the yellow folder icon, bottom left). Input the folder name and
click OK (B).
Your other alternatives are to mark the folder position as above and either
l right click and select Create > Folder, or
l click on the yellow Create (folder) icon (C) in the lower left hand corner of the screen.
- 139 -
6.2 Copy alias via clipboard to folder
l Mark the component (A), right click and select Copy (B).
l Mark the arrow beneath the folder (C), right click and select Paste.
To put machines into your folder, you copy a component to the clipboard, then paste it into the pre-
viously created folder.
The original component remains inside the standard component folder. Your own folder contains an
alias, recognizable by an arrow on the icon (E) (the original component icon does not have an arrow,
D). When you edit the alias, the original is also edited automatically. Deleting the alias will not affect
the original.
- 140 -
6.3 Copying in measuring round order
l Hold down CTRL, mark components in desired sequence, press CTRL+C.

l Mark the arrow beneath the destination folder (A), press CTRL+V.
Holding down CTRL while clicking on the components allows you to mark a whole group in any order.
If you mark them in measuring round order (the sequence in which they are to be measured), you
can later place your own component folder into a measuring round, without making any changes.
To mark a group of items, you can also click on the first, then hold down the SHIFT key and click on
the last item in the group.
- 141 -
6.4 Working with a split window
l While in 'View as tree' mode, right click and select Split window (A).
The standard component folder will soon contain many items. Instead of scrolling up and down
between this folder and your tree structure, you can split the window and scroll each part to the
desired position.
Please note that each item you create or paste is inserted above the marked position. Thus, if you
mark a folder, the components in the clipboard will be pasted in outside of and above this folder. To
get it inside, you must open the folder and mark the arrow beneath the last item or any of the items
inside.
You cannot drag items within the tree structure unless you split the window. To move them to
another position, use Cut to clipboard (CTRL+X), then paste them into the desired place (CTRL+V).
- 142 -
6.5 Working within your own folders
l Folder can be inside other folders.

l Components/measuring points can be created inside your own folders.
Instead of creating components in the standard component folder, you can make your own tree struc-
ture first and create them inside your own folders. This will place aliases in your folders and auto-
matically put the originals in the standard component folder.
Folders can be put inside other folder, extending the structure sideways (A).
It is also possible to use measuring point folders instead of components. This saves you the trouble to
create components. The disadvantage of this procedure is that you do not have a machine unit with
which you can connect work descriptions or comments concerning the whole machine.
- 143 -
7. Measuring rounds
7. Measuring rounds
7.1 Creating a measuring round
For data loggers you need to create measuring rounds (or standard work orders) for download to the
instrument. To create a measuring round, right click in the Measuring point tree and select Create >
Round (A). Measuring rounds are numbered from 1 to 9999 (B). They are also named (C), e. g. with
the name of the folder where you store the measuring points.
Normal interval (D) is the time between measurements. Click the '...' button to open the calendar
and set a desired interval, for example every 30 days, the first Monday of every month, etc. Present
interval is automatically set to Same as Normal interval. Edit this value when you want to make a
temporary change in the measuring interval. For example, to measure once a week (to check on the
deterioration rate of a bad bearing), you would set Present interval to every week instead.
Next date (E) is the day you plan to take the reading. Condmaster sets a new next date when you
upload your readings to the PC, by adding the Present interval to the uploading date. To keep your
time plan in order, always measure and upload as planned. The Next dates button displays a list that
contains the next 20 dates the round should be performed according to Present interval and Next
date.
Type of speed (F) can be either ”Measured” (done with a tachometer probe in conjunction with the
condition measurements) or ”Constant/preset”. Constant speed is the speed value stored in Meas-
uring point data. Preset speed is input while downloading the round.
Work description is an option: you can input the code of a previously created work description and
connect it to the round.
Under Data Transfer - Users (G), users with access to the current database can be connected to
the measuring round, which will enable them to select only their own rounds for download to the
instrument. At this point, the measuring round is empty; see "7.2 Entering measuring points into a
measuring round" on page 146 for instructions how to add measuring points to rounds.
- 144 -
7. Measuring rounds
Scheduling a measuring round based on operating time
The purpose of this function is to schedule measuring rounds based on operating time (number of
operating hours) obtained via OPC or any other user defined measurement. The measuring round is
controlled via the operating time of one object ( Measuring assignment , A) that represents all
objects in the round (if this object is running, all other objects in the round are also running). Active
limit (B) is the limit that the measured value must be higher or equal to for the machine to be con-
sidered running (measured value >= limit value).
You set an Operating time interval (C) in number of operating hours (for example 800 h) and a
time interval (Normal interval) (for example “every 30 day (s)”) when setting up the measuring
round. This is like when service will occur for a car: based either on passing 30,000 kilometers or 365
days, whichever alternative happens first. When you set the operating hours, a countdown will start.
You can view the operating time left in the Data Transfer window (D). When the operating hour
countdown reaches 0, or when the time interval is passed, it is time to perform the measuring round.
The measuring round is then placed on top of the measuring round list. Operating hours will stay 0
until the round is performed and uploaded to the PC.
The measuring round will automatically receive an estimated date for execution based on either the
last 60 days or since the last closing of the round, whichever includes the greatest amount of days.
The date used for scheduling will be the one closest in time, either the next date based on the time
interval or the estimated date.
- 145 -
7. Measuring rounds
7.2 Entering measuring points into a measuring round
l Click the NEW button (A) on the Round data input form, mark Measuring point in the next
window (B) and click OK.
l In the Search (Measuring point) form (C), mark one or more measuring points to include in
the measuring round and click OK.
l Click SAVE (D).
On the measuring round input form, clicking the NEW button (A) > Measuring point (B) > OK
opens the measuring point tree (C). Any item in the tree can be selected to be included in the meas-
uring round. If all measuring points intended for the measuring round are in one folder in the meas-
uring point tree, and in the right order, you simply mark the folder and click the OK button to transfer
the whole lot to the measuring round. Multiple measuring points may also be selected by holding
down the CTRL key and clicking each of the measuring points in turn.
Clicking NEW (A) again allows you to add more measuring points at the end of the measuring round.
You can also mark a measuring point in the measuring round and click the INSERT button to add fur-
ther measuring points above the one marked.
To delete a measuring point from a measuring round, mark it and click the DELETE button. Two or
more consecutive measuring points may be marked by holding down the SHIFT key and clicking on
each row in turn. When you mark a measuring point and click EDIT, you replace it with your selection
from the tree. To finish, click SAVE (D).
- 146 -
7. Measuring rounds
In the Measuring Point Data form under the Settings tab, the field Included in round (E) shows
which measuring round(s) a particular measuring point is included in.
If the measuring point is not included in a round, this field is not displayed.
- 147 -
7. Measuring rounds
7.3 Labels in measuring rounds
To add a label in a measuring round:

l In the Round form, mark a measuring point and click INSERT (A).
l In the Insert form (B), select ‘Round label’ and click OK.
l Enter a round label name and description (C) and click OK.
l Back in the Round form, click SAVE.
The measuring points contained in a measuring round can be organized under labels to create a
logical structure and improve measuring route efficiency - much like you would sort various files into
separate file folders to create a logical structure.
In the Round input form, mark the first measuring point you want included under the new measuring
round label. The new label will be placed immediately above that measuring point; in the example
above all measuring points initially belong to the ‘C - Basement’ measuring round label.
Click the INSERT button (A). Select ‘Round label’ (B) and click OK . Input name and description
(optional) for the measuring round label (C) and click OK . The measuring points in the above
example are now separated under two different measuring round labels (D). You can move meas-
uring points as well as labels in the list using the MOVE UP and MOVE DOWN buttons. When you are
done, click SAVE to close the Round form.
Using the NEW button instead of INSERT will append a new measuring round label at the end of the
list of measuring points. If that is not where you want the label, move it with the MOVE UP button.
- 148 -
7. Measuring rounds
7.4 Selecting measuring rounds for download
To download a measuring round to a data logger, click Data transfer in the Maintenance tab (A).
The Data Transfer window opens; this is where you select what measuring round(s) to download to
your instrument.
On the All rounds tab (B), all measuring rounds in the database are listed.
If specific users were connected to a measuring round when it was created (via the Data Transfer -
Users option; see section "7.1 Creating a measuring round" on page 144), the Data transfer win-
dow instead opens with the My rounds tab (B) displayed. On this tab, all measuring rounds con-
nected to specific users are listed.
In a database with many measuring rounds, the connection of users to rounds works as a “filter”,
such that when downloading rounds, the user can choose to see only their own subset of measuring
rounds on the My rounds tab.
Connecting users to more measuring rounds can be done from the My rounds tab by clicking the MY
ROUNDS button (C) and selecting measuring rounds from the My rounds window (D).
Under SETTINGS (E), it is possible to tick ‘Component name on separate line’ checkbox which splits
the number and name of components on two separate lines for Leonova Diamond and Leonova Emer-
ald displays, thus ensuring that the entire number/name appears on the screen.
Over time, your database may contain a large number of measuring rounds. To help locate particular
round(s), Search text (F) is a free text field that searches all measuring round names for the user-
specified text and marks all matches in orange. On both tabs, the list of measuring rounds can be sor-
ted on any column by clicking the column headers.
- 149 -
7. Measuring rounds
7.5 Downloading measuring round to instrument
l Click Data transfer (A) in the Maintenance tab in the ribbon bar.
l Mark a measuring round and click Transfer to instrument (B).
To download a measuring round to a data logger, click Data transfer in the Maintenance tab (A) in
the ribbon bar. From either the My rounds or All rounds tab in the Data transfer window, select
which measuring round to transfer, then click Transfer to instrument (B) to download all meas-
uring points.
Downloading all measuring points is the normal routine, but it is also possible to make a selection.
Click the '...' button beside Transfer to instrument to open a popup menu with alternatives (C).
The alternatives are; all, only those on the alert list (visible if the round contains measuring points on
the alert list), and only those not measured (visible if the round contains measuring points not meas-
ured).
The second alternative, measuring points on the alert list, is used when you want to do an additional
check on the measuring points with high readings. The third alternative, measuring points not meas-
ured, means not measured in the instrument. This option can be used for example if only half of the
measuring points in the round were measured and then uploaded to the PC, and this time you want to
download and measure the rest of the round.
If more than one instrument type is used, select one to download the round to in the Select instru-
ment window (D). If more than one individual Leonova Diamond or Leonova Emerald instrument is
available, select one and click OK to start the transfer of measuring points.
With Print (E) you can print out the measuring points in the measuring round and work descriptions
via the Report Manager (see "16.12 Report Manager" on page 414).
NOTE: If a measuring round includes a deactivated measuring assignment (see section "4.17 Deactiv-
ating measuring assignments" on page 62), that assignment will not be downloaded to your instru-
ment.
Settings (F) contains alternatives for simplifying the workflow for downloading/uploading measuring
rounds with fewer clicks and more, see "7.6 Settings for data transfer" on the next page.
- 150 -
7. Measuring rounds
7.6 Settings for data transfer
Settings (A) for data transfer contains alternatives for simplifying the workflow for down-
loading/uploading measuring rounds with fewer clicks, etc. see below.
Simplify the workflow for downloading/uploading measuring rounds

Under General, the setting Show 'Communication completed' dialog (B) is activated by default
and means that a window with the text 'Download completed' or 'Upload completed' is shown when
the data transfer is ready, and you have to click to close it. To simplify the workflow for down-
loading/uploading measuring rounds with fewer clicks, untick the checkbox Show 'Communication
completed' dialog (B) and click OK to save the setting.
Faster measuring rounds in the Leonova instruments

By default, the Download Symptom to the instrument (C) alternative under Leonova is activ-
ated. Untick this checkbox to disable symptom calculations in the instrument. When the results are
uploaded from the Leonova instrument, the symptoms are calculated by Condmaster, and alerts are
registered for these symptoms. This function applies to Leonova Diamond, Leonova Emerald and
Leonova Infinity instruments.
Specific settings for Leonova Diamond and Leonova Emerald

For Leonova Diamond and Leonova Emerald instruments, the checkbox Show components in
measuring round (D) is activated by default which means that components will be downloaded to
the instrument. The component name can be shown in a separate row from the measuring number by
ticking the Component name on separate line checkbox, and it is also possible to set the Opacity
of the text as desired.
- 151 -
7. Measuring rounds
By default, the Show 'Delete round' dialog after upload checkbox (E) is deactivated. If this is
activated, Condmaster will ask if the uploaded measuring round should be deleted from the instru-
ment.
Downloading all measuring rounds and measuring points from Condmaster to the instrument
The alternative Download all round data (F) is activated by default. This means that when a meas-
uring round is downloaded to the instrument, all measuring rounds and their measuring points for the
current database is downloaded to the SD card in the instrument, but without measuring results. The
data is not visible in the instrument, but can be accessed via the functions mentioned below.
NOTE: Data from one database only is stored in the instrument. If several measuring rounds from dif-
ferent databases are downloaded, it is measuring rounds and measuring points from the most
recently downloaded database that is stored in the instrument.
The Download all round data function is the basis for the follwing functionality in the instrument:
l Keeping track of CondID tags belonging to other measuring rounds in the same database
l Creating temporary measuring rounds in the instrument
l Adding temporary measuring points to the measuring round in the instrument
See the Leonova Diamond User guide and Leonova Emerald User guide for more information.
- 152 -
7. Measuring rounds
7.7 Connecting Leonova Diamond and Leonova Emerald to PC
l Connect the instrument to port, start ‘Communication’ (A)

l On the PC, select instrument type (B) and click OK.
l If applicable, select an individual instrument (C) and click OK.
To transfer, connect the instrument(s) to a computer USB port. Select Communication on the instru-
ment’s FILE menu (A). The instrument screen reads ‘Transfer mode activated’.
On the PC, go to Maintenance > Data transfer and click TRANSFER TO INSTRUMENT (or
TRANSFER TO PC). Select measuring points to transfer, then select instrument type (B) and click
OK. If more than one instrument is connected to the PC, select one (C) and click OK. Communication
with the selected instrument now starts.
The transferred measuring round appears as a file on the instrument’s FILE menu. Measuring points
and techniques come up on the instrument screen in measuring round order.
An error message is displayed if anything is wrong with the data transfer.
- 153 -
7. Measuring rounds
7.8 Connecting Leonova and Leonova Infinity to PC
l Connect to port, start ”Communication” (A)

l Click OK (B)
To transfer, connect Leonova to the COM or USB port registered under System > Measuring sys-
tem (check Properties for the instrument). Select Communication (A) on the Leonova FILE menu.
The instrument screen reads ”Ready for transfer”. Click OK on the PC screen (B).
The round appears as a file on the Leonova FILE menu. Measuring points and techniques come up on
the instrument screen in round order.
You get an error message if anything is wrong with the data transfer. Normal reasons for com-
munication errors are:
l The downloaded round does not contain a Leonova measuring point.
l The communication port set on Leonova is not the same as the port set in Condmaster.
l Leonova is connected to the wrong communication port.
A note on USB communication: the correct USB driver is required, and any USB active sync software
must be deactivated in order for the USB communication to work. Also, Condmaster 64-bit version
only supports serial communication (RS232) for Leonova and Leonova Infinity. For more information,
see "16.19 USB communication with Leonova and Leonova Infinity" on page 425.
- 154 -
7. Measuring rounds
7.9 Connecting A/T30 to PC
l Connect to COM port, start and switch to "Communication" (A).

l Click OK (B).
To transfer, connect the data logger to the COM port registered under System > Measuring
system. For computers with USB ports only, a USB to RS232 converter is needed.
Select Communication (A) on the instrument screen and press the ENT key. The instrument screen
reads ”Ready for transfer.” Click OK on the PC screen (B). An error message is displayed if anything is
wrong. After successful data transfer, the last line on the instrument screen reads ”Finished”.
Measuring points and techniques come up on the instrument screen in round order. Normally, you
complete the measuring round before uploading results. You can upload a partly finished round and
download the remaining measuring points later, using the alternative ”Measuring points without res-
ults”.
- 155 -
7. Measuring rounds
7.10 Uploading results to the PC, closing the measuring round
l Connect instrument to the PC port, switch to Communication.

l Click Transfer to PC (C).
After downloading a measuring round, the transfer form shows the downloading date (A) and the sig-
nature used to open Condmaster when the measuring round was downloaded (B). Thus you can keep
track of the measuring rounds which are currently being measured and of the personnel working on
them.
To upload results you use the same procedure as for downloading, but a different button: Transfer
to PC (C). When the uploaded measuring round is complete (all points measured) it is automatically
closed. This removes the transfer data and sets a new due date under Next date (D). For an unfin-
ished measuring round you get a reminder that measurements are missing. You can close the meas-
uring round anyway and finish it and transfer the rest later.
The button Select round from Leonova (E) allows you to transfer any Leonova file to the PC,
provided it only contains measuring points that are set up in your Condmaster.
- 156 -
7. Measuring rounds
7.11 Identification tag CondID in Condmaster
When the instruments are loaded with measuring points from Condmaster, the program will auto-
matically send all necessary codes. For an open system without password there is no setup for tags.
For a system with the extra password protection, you have to input the passwords. Everything else is
an automatic part of the downloading procedure. A identification tag is ready for reading/writing
when the box Use this measuring technique (A) is marked.
You can use all available measuring techniques together with the tags, checkpoints included. They
are initiated through a first WRITE command. The measuring points must then be uploaded to Cond-
master.
In the measuring point tree, ”tagged” measuring points are marked by the tag icon. If it shows a red
dot (B), the tag memory could not accommodate all data. In such a case, data will be left out. This
starts with shortening the measuring point name. Next, the checkpoint text is shortened/left out,
then others, working rear to front. The ID tag menu will show the used number of bytes (one byte =
one character).
In case of memory trouble, edit the measuring point. You may be able to cut down on redundant
information:
l Use short measuring point names and short texts for ”checkpoints”.
l Define Measured quantity for User defined with as few characters as possible. Keep the res-
ult display format ”##.#” to the minimum.
l Distribute the measuring techniques to two measuring points if necessary.
Note: For Leonova Diamond and Emerald MMI 6.04 or higher, the CondID functionality is different.
Only CondID identification number is stored.
- 157 -
8. Status display
8. Status display
8.1 Status display in the Graphical Overview
Once there are measuring results stored in Condmaster, the Graphical Overview provides a display
of current status based on the latest measuring results. For details, you click on the folders or Color
Zones you want to look at and work your way downwards to the measuring point level.
In the lower image (A), the Graphical Overview has been arranged by the user with pictures, own
shaped Color Zones with folders and measuring points connected to them, and Summary Boxes in
order to provide a quick status display of the plant and its machinery, see "2.2 Arranging the Graph-
ical Overview" on page 14.
In the upper image (B), View as tree mode has been selected showing folders and its sub folders
down to measuring point level.
Green - Yellow - Red (and grey)
The latest measuring results show the condition of the worst measuring point inside a folder through
a colored dot:
l green: all evaluation results inside the ”good condition” limits, or only raw values inside the
folder (no evaluation)
l yellow: at least one evaluation result inside the ”caution” limits
l red: at least one evaluation result inside the ”bad condition” limits
l grey: no measuring results or alert levels inside the folder.
- 158 -
8. Status display
A triangle after the status dot shows that at least one measuring point inside the folder is presently on
the alert list. The triangle can turn up in connection with a grey or a green dot when the measuring
point has been forced on the alert list with a comment. Clearing the alert list removes the triangle.
Status display on measuring point level
When you click your way down to the measuring point level, different windows will be displayed
depending on how/if your Graphical Overview has been arranged.
When arranging your Graphical Overview with images and Color Zones , it is possible to decide
whether the measuring point should open at its location (default), or open in Condition View, Graphic
Evaluation , Colored Spectrum or Spectrum . Please see " 2.5 Adding Color Zones to pictures " on
If you have not arranged your Graphical Overview in that way, you will see all active measuring tech-
niques and the status based on the latest measuring results:
Measuring techniques listed with status dot (and alert indication), and measuring results listed with time and date
Vibration measuring results are only displayed if they are evaluated by means of a so-called criterion,
else you see the message ”Either criterion, symptoms, or result missing” under the assignment
name.
If there is no result, the dot is greyed out. Missing symptoms means that all condition and symptom
parameters were deactivated in the measuring point register. In this case, the criterion is missing,
because it has not yet been defined. One reading is not enough for making a criterion, you need a
whole batch of readings (see under " 10.3 Recording a batch of readings for the Leonovas " on
page 257).
- 159 -
8. Status display
8.2 Highlighted measuring points
l Mark the measruing point and press CTRL+H

l Select your settings in the Highlight measuring point window (A)
l Click ADD NEW COMMENT to add a comment (optional) (B)
Measuring points of particular interest can be highlighted in the Measuring point tree and displayed
in a separate window, making it easy to keep an extra watchful eye on them.
In the Measuring point tree (or in the Graphical Overview), mark the measuring point and press
CTRL+H on your keyboard. In the Highlight measuring point form (A), marking the Bold style
checkbox makes the measuring point name stand out in bold text, and marking Show latest com-
ment in graphical overview makes it possible to see measuring point comments. Publish makes
it possible to view highlighted measuring points on the Internet via a mobile device without access to
Condmaster, please see " Publishing trend graphs and alerts on the Internet " in the Condmaster
Installation and System Administration manual, document no. 72301.
The ADD NEW COMMENT button enables you to enter a new comment (B) (optional), and also to
select a default standard comment (C) (mandatory).
Using CTRL+H (and in some cases via popup menus), you can highlight measuring points also from
the following Condmaster functions: Colored Spectrum Overview, Spectrum , Compare Spectrum,
Trend Graphics, Alert List.
In the Measuring point tree, highlighted measuring points appear in bold text and if a comment has
been entered, it can be viewed by clicking on a small, colored square at the end of the line (D).
When you no longer need a particular measuring point highlighted, press CTRL + H again and untick
the checkbox(es) in the Highlight measuring point form (A).
See "8.3 Listing highlighted measuring points" on the next page for information on how to view high-
lighted measuring points.
- 160 -
8. Status display
8.3 Listing highlighted measuring points
Highlighted measuring points can be shown in a separate window for easy overview.
Click the right panel menu button and select Graphical Overview > Miscellaneous > Show high-
lighted measuring points window (A) to display the highlighted measuring points window (B).
In the Highlighted measuring points list, the ‘Signature’ column shows who highlighted the measuring
point.
From this window, you can go to Graphic Evaluation, Alert list, Colored Spectrum Overview etc. just
by clicking on their respective icons (C).
To close the Highlighted measuring points window, go to the right panel menu button and select
Graphical Overview > Miscellaneous > Show highlighted measuring points window option
again (A).
8.3.1 Publishing highlighted measuring points on the Internet

The trend graphs of highlighted measuring points can be published on the Internet and viewed via
most mobile devices with Internet connection (such as smartphone, tablet and computer), without
access to Condmaster. This enables you to easily monitor critical machines or machines with deteri-
orating condition when you are on call or on the go.
The setup for publishing is described in the Condmaster Installation and System Administration
manual, document no. 72301.
- 161 -
9. Evaluation Functions
9.1 Save form layout
In Condmaster, there are several parts that have support for modifying and saving the layout, per-
haps most notably in Spectrum and Graphic Evaluation. In Spectrum for example, there are sev-
eral ways in which the layout can be modified (e.g. customizing the toolbar, tool windows positions,
etc.)
For the parts of Condmaster in which the layout can be modified, the layout is saved by selecting
Save form layout in the System window popup menu (A) accessed either by clicking the small red-
yellow-green icon at the top left in the title bar, or by right clicking anywhere at the title bar in the cur-
rent window supporting this functionality. Next time the window is opened, the saved layout is
restored.
To reset to default layout, select Reset form layout from this menu (A). Please note that the win-
dow has to be reopened for the reset to take effect.
It is also possible to copy a layout from another user or another computer by selecting Copy layout
from in this menu (A). This opens a separate window (B) containing the saved layouts for all users
and computers for the current database. In the example above, the user System has been logged on
and saved the layout on two different computers. If you save your layout on one computer and then
log on to other computers, a saved layout does not automatically follow because screen resolutions,
number of screens, etc. might differ between computers and the layout might not fit. Select the lay-
out to copy and click OK. This is now your new layout.
If the layout has been changed, a confirmation dialogue (C) is shown when closing a window with the
save form layout functionality. Select if you want to save the current layout or not, or select to always
save or never save. An Always or a Never save option can later be modified under System > Set-
tings > User Settings.
- 162 -
9.2 Evaluation functions from the Overview
From the Graphical Overview you can go to all other functions you might need for a more detailed
evaluation of machine condition.
The most common evaluation functions are available directly from the Graphical Overview ribbon
bar (A), while the right panel menu > Graphical Overview contains a complete list of options (B).
All evaluation functions may not be accessible; e.g. Lubmaster is only active when you have marked
an item containing a LR/HR measuring point (or the LR/HR measuring technique itself).
To mention a few evaluation functions; the Alert list option opens the alert list for the item currently
marked in the Graphical Overview.
The Condition View option provides one window with multiple graph types which e.g. can provide
some guidance regarding further analysis.
The Spectrum option leads to the Spectrum view in which the spectrum and time signal are dis-
played by default. With the Compare spectrum option you can display the spectra from several
assignments, which can belong to different measuring points or components.
9.3 Alert list

This section contains information about the alert list and its constituent parts. For information about
how to work with alerts, see "9.4 Working with the alert list" on page 177.
- 163 -
Introduction
Alert list in the ribbon bar opens the alert list for the item currently marked in the Graphical Over-
view.
The alert list is an essential part of Condmaster and fundamental to your evaluation work. The alert
list collects different type of alerts from all sources, such as machines, measuring points, and units,
which are included in the chosen database. An example is limit alerts whose alert limits are set for
each measuring assignment. If you don't set alert limits, the measuring assignment will not appear
on the alert list, even when the result indicates that the machine condition is bad.
The alert list window consists of four fundamental sections:

l A = Filters. Different ways of filtering the alert list, for example, by Priority, Status, Type,
Period, or Source.
l B = Based on the currently selected filters, Priority summary shows the number of alerts
with different priority levels.
l C = List of alerts. Here is where you manage the Priority, Status, etc. for the alerts.
l D = Docked windows. Easily accessible analysis of alerts by opening, for example, the trend
graph window next to the alert list.
See below for more information about each section.
- 164 -
Filters
By default, the alert list shows alerts with All priorities, Active alerts (= alerts with status New or
Open), All types of alerts for Any time period and from All sources. You can filter the list of alerts
according to these parameters as required. See below for more information about each parameter.
Priority
By default, the alert list show alerts with all priorities. Priority shows the severity of the alert. There
are six priorities, shown as intuitive colors, ranging from Info (blue = no immediate action required)
to Critical (dark red = requires immediate action). Thus, Info is the least severe level and Critical the
most severe level.
The idea with priority is to help you categorize the alerts, for example, which alerts require immediate
action. Priority is, however, not an evaluation of the machine condition. The evalution of machine con-
dition is presented in basic color evaluation in green-yellow-red or as health scores in blue-green-yel-
low-orange-red-dark red in the Graphical Overview. Health scores can be presented given that you
have a baseline activated for your measuring assignment, see "18. Decision Support System" on
See below for information about how priority works for the different alert types.
- 165 -
Priority: Limit alerts
For alerts of type Limit (see below for more information about alert types), red and/or yellow alert
limits must have been set on the measuring assignment. If you don't set alert limits, the measuring
assignment will not appear on the alert list, even when the result indicates that the machine condition
is bad.
When a measurement result exceeds a yellow or red alert limit, this is reflected in the alert list as mod-
erate or high priority, respectively.
If the measuring assignment’s measuring point belongs to a machine, it is possible to set a machine
criticality rating to reflect its importance.
The machine criticality rating affects the different type of alerts in different ways, see below.
For Limit alerts, machine criticality is reflected in the priority as follows:

l Machine criticality A (Mission Critical)
l Yellow alert limit = Medium priority
l Red alert limit = Critical priority
l Machine criticality B (Critical)

l Yellow alert limit = Moderate priority
l Red alert limit = High priority
- 166 -
l Machine criticality C (Less Critical)

l Yellow alert limit = Low priority
l Red alert limit = Medium priority
l Machine criticality D (Not Critical)

l Yellow alert limit = Info priority
l Red alert limit = Moderate priority
If machine criticality is not set, the default behaviour for limit alerts is equal to machine criticality B.
Priority: Online unit and CES/LinX alerts
For alerts of type Online unit and CES/LinX, the priority is set to medium:
If the machine has a machine criticality rating, the following applies:

l Machine criticality A (Mission Critical)
l Online unit and CES/LinX alerts = High priority
l Machine criticality B (Critical)

l Online unit and CES/LinX alerts = Medium priority
l Machine criticality C (Less Critical)

l Online unit and CES/LinX alerts = Moderate priority
l Machine criticality D (Not Critical)

l Online unit and CES/LinX alerts = Low priority
If machine criticality is not set, the default behaviour for Online unit and CES/LinX alerts is equal to
machine criticality B.
- 167 -
Priority: Comment alerts
For alerts of type Comment, there is no connection to machine criticality, but you can decide priority
when creating or editing comments in the Standard Comments register.
To set alert priority on a comment:
1. In the ribbon bar, go to Registers > Standard Comments (A).
2. Select NEW or mark an existing comment and select EDIT (B).
3. In the Standard Comment window, select Alert priority from the list (C).
4. Select SAVE (D).
In this example, the standard comment “FA01 Temperature high” was selected to have the alert pri-
ority “High”, which is reflected in the alert list:
- 168 -
Setting your own priority for generated alerts
If required, you can open an alert in the alert list and set your own priority.
To change the priority for an alert:
1. Select the arrow (A) to open the alert details.
2. Change the priority by moving the arrow in the color bar (B) (or use the arrow under the
color bar to open a list and make your selection).
In Condmaster Ruby, you can also right-click an alert to open a menu and select priority from there
(selecting the ellipsis button also opens this menu).
- 169 -
Status
Alerts can have different statuses:
l New – unhandled alert (blinks in the Graphical Overview)
l Open – acknowledged alert

l Snoozed – paused and hidden alert (for a period of time)
l Closed – handled alert
l (Deleted – deleted alert, not possible to access)
By default, the alert list shows alerts with the status New and Open (= Active alerts). Alerts with
status Snoozed and Closed are categorized as Inactive alerts.
Note: Deleted alerts are not possible to access.
When an alert is generated, it always gets the status New. When you are working with the alerts, you
can change their status as required. For a suggested workflow regarding the statuses when working
with alerts, see "9.4 Working with the alert list" on page 177.
Type
By default, all types of alerts are shown in the alert list. However, you can select to show, for
example, only limit alerts. These are the different types:
l Limit = alert generated according to the alert limits that have been set on a measuring assign-
ment
l Online unit = alert generated by an online unit, for example, “No result from online unit”
l CES/LinX = alert generated by CES or LinX, for example, “Failed to connect to OPC server”
l Comment = alert generated by a comment a user has made on a measuring point
- 170 -
Period
By default, the alert list shows alerts from Any time period, but it is possible to filter out alerts
according to different alternatives such as the last day, last seven days, etc., or a custom selection.
To change the period, click the arrow to the right and make your selection.
Source
Source can be used to filter out alerts in different ways, for example, by selecting a measuring
assignment, measuring point, component, machine, or online unit (A). Depending on your
database, this list can be very long.
It is also possible to write in the text field and search for a specific source. As you write, the sys-
tem will suggest potential sources that you can select (B).
- 171 -
Priority summary
Based on the currently selected filters, Priority summary shows the number of alerts with different
priority levels.
CLEAR FILTERS (A) is used to reset to the default filter values (= all priorities, all active alerts, all
types).
The arrow (B) is used to collapse the Filter and Priority summary sections, which mean that the alert
list gets more space.
List of alerts
Elements in the alert list
The list of alerts is where you work with the alerts. The list shows individual alerts in rows. The
columns show:
A. Priority, ranging from Info to Critical showing the severity of the alert.
B. Date/time for when the alert was generated.
C. Status (New, Open, Snoozed, Closed). By default, the alert list shows alerts with status New
and Open (active alerts). Note: Deleted alerts are not accessible.
D. Source, for example measuring assignment, online unit, etc., and its current evaluation (Basic
color evaluation) if applicable.
E. Description of the alert, for example which value generated the alert, or “No result from
online unit”, etc.
- 172 -
F. Actions: menu with different actions to perform on the alert (corresponds to a right-click on
an alert).
G. Details: shows details for the alert, for example, an event log.
H. Comment: with a digit representing the number of comments on a measuring point.
I. Deduplication: informs how many times (x1, x2, etc.) the alert is deduplicated. Dedu-
plication prevents the occurrence of copies of the same alert, which keeps the alert list short
and easy to work with.
J. Ellipsis icon: visible when at least one alert is marked and used for changing the priority on
one or several alerts.
In addition to the Filter section above the alert list, it is also possible to filter, sort and group alerts by
using the functionality in the list.
l Filtering: Select the filter icon (A) at the top of the list to show the filtering options for each
column. For example, writing the text “Vel” in the Description field filter out all alerts with the
text Vel in its description (B).
l Sorting: Select a column name to sort alerts by that parameter. Any sorting is indicated by an
up/down arrow, see the arrow by Source (C) for an example.
l Grouping: Select the grouping icon for a column to group alerts according to that para-
meter. The image shows an example of grouping by Priority (A) and Status (B). Select the
arrow to the left to expand/collapse each group. To remove a grouping, close a grouping icon
visible in the grouping field (C).
- 173 -
Alert actions
Clicking the ellipsis icon for an alert opens a menu with actions that can be performed, such as chan-
ging status and priority, providing a shortcut to the Measuring Point Data window to edit the alert
limit as well as shortcuts to other functions, possibility to go to or add comments, etc.
Right-clicking an alert also opens this menu.
- 174 -
Alert details
For each alert, you can select the arrow at the end of the row to open a window showing its Details
(A), Related comments (if any) (B), and Event log (C).
From here, you can change priority and status, filter and sort comments (if any), and check as well as
entering new posts in the event log.
For information about how to work with alerts, see "9.4 Working with the alert list" on page 177.
- 175 -
Docked windows
Docked windows provide easily accessible analysis of alerts. It is possible to open functions such as
Graphic Evaluation, Spectrum, Colored Spectrum, etc., directly from the alert list as docked win-
dows. The windows are docked, meaning that they get “attached to” the alert list window.
When selecting an icon from Docked windows, for example the Graphic Evaluation icon (A), it
gets 'activated' and opens next to the alert list. If you close the alert list, both windows will be closed.
When opening the alert list again, the system remembers the activated icon and will open the Graphic
Evaluation window.
When marking an alert in the list (B), it is also shown in the docked Graphic Evaluation window (C).
This facilitates, for example, the initial analysis when deciding whether the alert needs further invest-
igation or if it can be closed or deleted.
Depending on the size of your computer screen/screens, the docked windows will be distributed
around the alert list as far as they can fit (windows that don't fit will be placed over another window).
You can resize the windows as required.
Other functions in the alert list window
Under the ellipsis button (A), there is a possibility to print the alert list.
Alert export (B) to SAP and AMOS can be set up under System > Settings > Alert export, see
Condmaster Installation and System Administration manual, document no. 72301 . However, we
recommend using our REST API for a modern, flexible and secure solution if you want to export alerts
to other systems, see "16.25 CES API" on page 479, or check with your sales representative for more
information.
- 176 -
9.4 Working with the alert list

This section contains information about how to work with alerts. For more information about the alert
list and its constituent parts, see "9.3 Alert list" on page 163.
Alert list workflow

The workflow described below is a suggestion. Depending on factors such as the amount of alerts, the
type of alerts currently in the alert list, way of working in the maintenance team and/or analysis team
(if any), etc., you might find other approaches more suitable.
1. Filter out, sort, or group according to Priority , and check Critical and High priority first.
(optional)
Note: If the list is very short, you might not need this step. Also, depending on the current
alerts in the list, other priorities might be of greater interest. This is up to you.
2. Filter out, for example, New and Limit alerts. (optional)
Note: If the list is very short, you might not need this step. Also, depending on the current
alerts in the list, you might want to check, for example, "No result from online unit" alerts first.
This is up to you.
3. Examine each alert by using, for example, the docked Graphic Evaluation window and
change the status for the alert according to the suggested workflow with status below.
- 177 -
l For alerts with status New (blink in the Graphical Overview), check and decide:
l if the alert is clearly a false alert = delete the alert.
l if the alert should be further analyzed = set the alert status to Open (do not blink in the
Graphical Overview). This means that the alert has been acknowledged and is under
investigation.
l When an open alert has been further analyzed and taken care of = set its status to Closed.
l You can also snooze an alert, which means that it is paused and hidden for a period of time.
This can be useful if, for example, you know that the bearing causing the alert will be replaced
in a couple of weeks.
l Note: Deleted alerts are not possible to access.
The alert list has many functions and offers a flexible way of working with alerts. If the steps
described above do not suit you, try other ways until you find one that works well for you.
For more information, see for example, "Priority" on page 165, "Type" on page 170, "List of alerts" on
page 172, "Docked windows" on page 176.
Change status for one or several alerts
- 178 -
There are several ways of changing the status for an alert. One way is to use the ellipsis icon at the
bottom right of the alert list. When you mark one or several alerts, the ellipsis icon becomes visible
and shows the number of marked alerts (A).
Hover/select the ellipsis icon and select appropriate alternative for the marked alerts. For example,
selecting Acknowledge (B) sets the status to Open for the marked alerts.
You can also change the status for an individual alert via its details page, or by right-clicking an alert
and select from a menu.
- 179 -
9.5 Alert label
Alert labels can be used to categorize the alerts in a customized way. For production personnel or sim-
ilar, alert labels may serve as a supplementary guide on what to do when an alert is raised. Alert
labels are displayed in the alert list.
To create alert labels:
1. Go to System > Settings > Alert labels tab.
2. Select Add, enter a Name and click OK.
3. Tick the Require alert label on new alert limits check box to force the selection of an alert
label before a new alert limit can be saved (optional).
- 180 -
9.6 Alert Limit Manager
l A = Edit button, shortcut to measuring point register to edit alert limits

l B = Open graph in lower part of Alert Limit Manager
l C = Alert limit marked for review
l D = Open in separate window
The Alert Limit Manager in Condmaster presents an overview of existing alert limits. This is a con-
venient tool to verify that alert limits are in fact set up for your measuring points and that they are
viable and reasonable.
Mark a folder or measuring point in the Graphical Overview, then go to the right panel menu >
Graphical Overview > Miscellaneous and select Alert Limit Manager.
l To view a graph of any of the measuring points in the Alert Limit Manager window, mark one
and click the Graphics button (B) in the toolbar. The graph is then displayed at the bottom of
the Alert Limit Manager window. To open a graph or spectrum in a separate window, click the
Graphics or Spectrum icon (D) on the row of an individual measuring point.
l The Edit button (A) in the Alert Limit Manager toolbar is a shortcut to the measuring point
register where alert limits may be edited if required. Double clicking on a row in the list of
measuring points also takes you to the measuring point register.
l Click any column head to sort the list by that column.
- 181 -
9.7 Flexible alert limits
l A = When ticked, color limits are default SPM. Alert levels are user defined (preferred setup).
l B = When ticked, alert levels are user defined, and color limits will automatically be the same.
l C = When none of the two check boxes are ticked, alerts and color limits can be user defined
and will not have to match (as opposed to B)).
Via the Alert limits function in the measuring point register, it is possible to set yellow and red limits
for all parameters. For example, you may set individual yellow and red limits for dBm, dBc, LR and
HR, respectively.
Normally, you’ll want to retain the default SPM color limits while entering your own alert limits (A).
However, you may also enter alternative color limits (C), or have them be the same as your alert lim-
its (B). For instance, for a machine that you know is in good condition even though readings are “in
the yellow”, indicating a possible problem, customizing your alert and color limits is a convenient way
to avoid unnecessary alerts.
Only one of the two check boxes under Alert limits may be ticked at any given time. When color and
alert limits are connected (B), dBm (or LR) is the controlling value of the scale. NOTE: this does not
apply when measuring LR/HR on a variable speed application, when green - yellow - red cannot be
obtained. Alert limits are then rpm dependent.
When none of the two check boxes are ticked, you can edit the Color limits (C). Any limits you input
are immediately reflected in the graph. It is possible to select Alert label (D) for the upper and lower
alert limits. It is also possible to apply the upper/lower limits to other measuring points: tick the Con-
nect settings box (E), then click ADD to select which measuring points to apply the startup value(s)
to.
- 182 -
9.8 Bands
In spectrum analysis, it can be difficult to distinguish the spectrum lines of a particular symptom from
those of another; the energy content will sometimes “spill over” into neighboring frequencies. Bands
are an efficient way to “isolate” the symptom frequencies from each other. To accomplish this, the
RMS value of all the amplitudes within a user defined frequency range are added. The result is a bar
graph of the energy contained in the different frequency bands. Bands can be used when you want to
study a broader frequency range, e.g. covering an entire production cycle.
Careful tuning of the frequency range for individual bands (Band settings) will “separate” the symp-
toms, resulting in improved alert reliability. Random high readings caused by resonance or sources of
disturbance are filtered out, minimizing the number of false alerts. Finding the optimum band settings
is largely a trial-and-error process, and may also vary depending on the selected spectral window
type (Hanning etc.).
For variable RPM applications, there is no need to measure rpm if the variation is known and you set
the Band settings parameter to cover that range. Ticking the By orders checkbox makes the band
entirely rpm dependent; it will “slide along” with rpm as it changes within its upper and lower vari-
ation limits.
Bands produce bar graphs, as opposed to spectrum analysis which shows single frequency lines.
- 183 -
9.8.1 Multiple bands
The Multiple bands function illustrates multiples of rpm; the more serious the problem, the more
multiples are shown. Multiple bands will further clarify the symptoms and can be used for trending
purposes. Grey bars represent the RMS value of that particular band, while black bars represent the
combined RMS values of all bands in the spectrum.
9.8.2 Octave bands
Spectrum analysis with FFT is appropriate for resolving higher-frequency harmonics and sidebands.
However, sometimes FFT analysis provides more detail than you need; the detection of certain
machine faults does not require such high resolution. When this is the case, octave analysis may be a
better option. Typically, octave analysis is used for gearboxes and high rpm applications.
In octave band analysis, frequencies are segmented into proportionate widths (octave bands). An
octave band is the interval between any two frequencies having a ratio of 2 to 1. This means each
band occupies a bandwidth that is twice as wide as the previous band and half as wide as the next. In
spectral analysis, all frequency bands occupy equal bandwidth.
Constant percentage bandwidth
The type of octave band used in Condmaster is called constant percentage band. A constant per-
centage bandwidth filter is a bandpass filter where the width of each frequency band is a constant per-
- 184 -
centage of its center frequency. Each octave band has a bandwidth equal to about 70% of its center
frequency. This means the bands become wider in proportion to their center frequencies:
9.8.3 Implementing bands
The various forms of bands are implemented from the Measuring point data form.
Mark a measuring assignment, then right click in the symptom overview and select Add or Insert.
From the list of symptoms, select a band alert type (Band, Multiple bands or Octave band).
- 185 -
Band
In the Band window, input Band settings wide enough to cover the peaks of the spectrum.
For alert limits, you may input your own levels or have Condmaster calculate them for you. By
default, the CALCULATE button (available for Bands and Multiple bands) will look at the latest read-
ing and add 20% to calculate where on the condition scale yellow condition will apply. For red con-
dition, 40% is added to the latest reading. You can change these percentages, and if you do, they will
remain in the system as the new defaults. Alert limits are mm/second.
- 186 -
A = Double click to view all bands
B = Double click to view one band at a time
When looking at a spectrum, double click on the measuring assignment in the Spectrum window to
display the bands. To view only one band at a time, double click on a frequency range.
- 187 -
Multiple bands
In the Multiple Bands window, click NEW to input multiple Band settings wide enough to cover
the peaks of the spectrum. Use the CALCULATE button for alert limits, or input your own.
Octave bands
Depending on what resolution you want in the spectrum, select an appropriate fraction of an octave in
the Octave bands window. In many cases, one-third octave bands are sufficiently narrow.
- 188 -
9.9 Alert delay
Alert delay is useful to obtain stable and well justified alerts. This function delays the alert by a user
specified number of readings and determines when alerts will be raised. All readings from the meas-
uring unit are still saved to the Condmaster database; the “filtering” is done in the graphical display
only.
The function is accessed via the Alert Delay “...” button under Alert limits in the Measuring point
data form. The Number of alert delays setting means this number of consecutive readings must
be on or above the alert limit before an alert is actually raised. When applicable, tick the Include
COND checkbox. This means alerts will be raised on raw values as well as condition parameters.
When an alert delay is set, readings exceeding the alert limit are counted and evaluated against the fil-
ter setting. If for instance the delay filter is set to 4, above-alert-limit readings are not displayed and
no alert will be generated until four consecutive readings exceed the alert limit. Reading no. 4 will
then be displayed in the Graphic Evaluation and will also cause an alert.
Example
Alert delay: 4, Alert limit: 36
Date Reading Displayed in graph? Alert?

2019-10-06 34 Yes --
2019-10-05 40 Yes No
2019-10-04 36 Yes Yes
2019-10-03 39 No No
2019-10-02 38 No No
2019-10-01 37 No No
2019-09-30 33 Yes --
2019-09-29 29 Yes --
2019-09-28 32 Yes --
To confirm that readings are indeed “consistently” and not randomly high, a series of high readings is
thus required. In the example above, four consecutive readings above the alert limit is considered reli-
able enough to merit an alert. You may need to experiment a bit with the delay setting to find out
what number is required to exclude any false alerts for a certain measuring point.
- 189 -
9.10 Measuring result register
All measuring results are stored in the measuring result register. This register can be found e.g.
under the Maintenance ribbon tab. The measuring point is selected via the tree structure after click-
ing on the ”...” button (A). You can limit the list of measuring results by setting a From date, a To
date, or both (B). When you skip from e. g. Graphics, you go straight to the marked measuring point
or technique.
Depending on the active measuring techniques, the form shows tabs for Results (C) and other tabs
for different assignments (D). Click on a tab to open the result list. Results for specific parameters
connected to certain measuring techniques are listed under the assignments. The header for altern-
ative measurements (E) is the measuring unit set under the measuring point data.
When you access it, the measuring result list is sorted by date, with the latest result at the top. You
can change the sorting by clicking on any of the headers. This will put the highest measuring result
for this measuring technique at the top of the list and sort the list by value, with secondary sorting by
date. The colored dot (F) shows the status at the time of measurement. A red triangle (G) shows that
the point is on the alert list. A red value (H) means that an alert limit has been exceeded.
Values on the Results form can be manually input (press INSERT on the keyboard) and edited (mark
and press ENTER). All values can be deleted (mark and press DELETE). Evaluated results cannot be
edited and are input exclusively via data logger or online measuring unit. You can, however, input a
new vibration reading from the assignment form.
- 190 -
9.11 Measuring results for vibration assignments
To see the measuring results in a vibration assignment, click the different assignment tab(s) (A). The
results are displayed in groups: condition parameter values, symptom parameter values, and speed.
Use the drop down button (B) to change the display.
Vibration measuring results cannot be manually input. However, they can be deleted. Pressing DE-
LETE on the keyboard removes the marked results.
The only editable value for vibration measuring results is rpm. Mark a result row in the list and click
the Edit measuring result button (C, upper left corner). Input a new rpm value and click OK to
return to the Measuring results window.
Right-click in the list to obtain a menu with alternatives (D), for example, open other functions.
- 191 -
9.12 Spectrum default layout
The function Spectrum shows a spectrum and a time signal (A) based on one measuring result. Meas-
uring point number, name, assignment, date, and time are displayed above the spectrum and the
time signal respectively.
The default layout consists of one large area in which different spectrum views can be shown (A), two
toolbars in the top (B), and tool windows with spectrum data to the right (C).
Spectrum is set to Basic layout mode by default. In the Basic layout mode, toolbar buttons (B) and
tool windows (C) needed for the most common functions are displayed. The tool windows shown by
default are the Conditions window and the Symptoms window.
There are several layout options available. Click the ‘...’ button besides Basic (D) and select between
Basic, Advanced and Custom layout mode.
l In the Advanced layout mode, more toolbar buttons (B) and one additional tool window (C)
called Highest peaks are shown.
l In the Custom layout mode, it is possible to select exactly what to show and where to show it,
see the following pages for more information.
From this menu (D), it is also possible to select which tool windows to be displayed, and if the panel
with tool windows should be displayed or not (activate/deactivate Show Right Panel).
- 192 -
9.13 Customizing the layout of tool windows in Spectrum
l CTRL+mouse click and drag tool windows at desired drop sites

l Save changes by clicking Save form layout in Spectrum top menu
Tool windows are the Conditions, Symptoms, Symptom edit, Highest Peaks and Image win-
dows which in the default layout resides to the right. To drag and drop the tool windows at different
drop sites, hold down the CTRL key, click the blue ‘drag icon’ (A), then drag and drop the tool window
at the desired drop site (B). The large middle area is reserved for the different spectrum views.
Resize windows by hovering the mouse pointer at the border of a window, and when the mouse
pointer changes to a left-right arrow, click and drag to a desired size.
To save the layout, click the small red-yellow-green icon in the upper left corner of the Spectrum win-
dow title bar (or by right clicking anywhere at the Spectrum window title bar) and select Save form
layout from the popup menu (C).
To revert the save form settings, select Reset form layout from this menu (C). Please note that the
window has to be reopened for the reset to take effect.
- 193 -
9.14 Customizing the toolbar in Spectrum
Customizing the toolbar (A) is done by using the toolbar customizer (B) found in the Spectrum view
popup menu under Options > Toolbar > Customize Toolbar.
In the toolbar customizer (B), it is possible to add Separators, New Lines, and any of the com-
mands available in the Spectrum view window. Click ADD or INSERT (C) to find the alternatives:
l --Separator-- adds space between buttons in the toolbar
l <<New Line>> adds a new row in the toolbar
The commands are available in a list under All Commands, or by category under By Category. Com-
mands with ‘>>’ signs after them signifies ‘sub menu’, meaning that the new button in the toolbar
will have a small arrow from which the belonging options may be accessed.
Mark and click a command, e.g. Zoom Back All (D) found under Zoom, and it will be added into the
toolbar customizer list (E). Then click APPLY (F) to make the new button show up in the toolbar (G).
In this example, a New Line has been added above Zoom Back All in the toolbar customizer, meaning
that the new Zoom Back All button shows up in a new row in the toolbar.
To change the name of a command, mark it in the toolbar customizer (B) and click RENAME (H). In
the window that opens, type the new name and click OK, then click APPLY (F) to apply the change in
the toolbar. To change order of objects, mark an object in the toolbar customizer (B) and use the
MOVE UP or MOVE DOWN buttons (I) to move it to the desired location. To delete an object, mark it
and click DELETE (J). Remember to click APPLY to apply the changes in the toolbar.
To save the changes for the toolbar layout, select Save form layout from the Spectrum window title
bar menu (see "9.13 Customizing the layout of tool windows in Spectrum" on the previous page).
- 194 -
9.15 Spectrum views
Available views are:

l Spectrum (shown by default)
l Time signal (shown by default if a saved time signal result is available)
l Circular Plot
l Phase
l Reference Spectrum
l DS/NDS
If there is no button available in the toolbar for a certain spectrum view, right hand click to open the
popup menu, go to Layout and find the spectrum view options (A). When activating (or deactivating)
a spectrum view, it is added to (or removed from) the large middle area in the Spectrum window.
The Full Screen option in this menu (A) is also accessible through an icon shaped as a screen in the
top right of each spectrum view (B). Clicking a full screen icon (B) will display its window in full
screen. To get back to the normal view, click the screen icon again, or press the ESC key.
The Auto Layout option in this menu (A) is activated by default. Auto layout shows different spec-
trum views automatically depending on different conditions: Circular Plot view is shown automatically
if Time Synchronous Averaging (TSA) has been activated for a measuring assignment, Time Signal
view is not shown if a time signal result has not been saved, Reference Spectrum and DS/NDS spec-
trum view are shown if these views has been activated for display. Taken together, this has the effect
that the layout might change when browsing through measuring data. If the layout should stay the
same when browsing through measuring data, deactivate Auto Layout. Remember to save the deac-
tivation of Auto layout by selecting Save form layout from the Spectrum window title bar popup
menu.
- 195 -
9.16 Spectrum navigation and zooming
l Browse between current data by using arrows, '...' button or keyboard

l Click and drag horizontally or vertically to zoom
The current data displayed in Spectrum is shown at the top of the Conditions tool window (A). To
change current measuring point, measuring technique or measuring result, it is possible to use the
small left/right arrows (B), or clicking the ‘...’ button (B) which will open a separate window (C)
(example from the Assignment level) in which the desired data can be selected.
It is also possible to use the keyboard to change the displayed data:

l CTRL+LEFT/RIGHT arrows to go to the next or previous measuring result
l CTRL+UP/DOWN arrows to browse between measuring assignments and measuring points
If the layout should stay the same when browsing through measuring data, deactivate the option
Auto Layout under Layout in the Spectrum view popup menu (see "9.15 Spectrum views" on the
previous page).
The unit in the spectrum is automatically set to Hz, CPM or Orders (order 1 = 1X, the frequency cor-
responding to the rpm of the shaft) depending on the measuring point data settings. Clicking on the
spectrum unit (D) toggles between frequency and orders.
It is possible to select frequency units and in which order to toggle them under System > Settings,
in the Settings tab, in the box for Spectrum.
Click and drag horizontally (y-axis) or vertically (x-axis) to zoom in. Combine the two by using the
SHIFT key and drag the mouse at the same time. This way, you can easily zoom in on any area.
Click the Zoom back button (E) or use CTRL+Z on the keyboard to zoom out. To zoom back all,
right click and select Zoom back all (F) from the pop-up menu or use SHIFT+CTRL+Z on the key-
board.
If you have zoomed in on a result, you can scroll the axis by clicking and dragging it.
- 196 -
9.17 Spectrum cursors
Cursors is one of the most important tools when working with spectrum data. When opening a spec-
trum, one cursor (A) is activated by default. This is because the option Set cursor A to RPM when
open is activated by default (see Spectrum view popup menu under Cursors). To add a cursor, click
a cursor button in the toolbar (B), or use the Spectrum popup menu under Cursors, or hold in the
SHIFT key and simultaneously long click (click and hold down) the mouse in the spectrum.
In the time signal, a cursor is divided into two parts (e.g. A1 and A2) (C) where the delta (difference)
between the two parts is reflected in the spectrum.
To move a cursor in the Spectrum, simply click and drag it (or click LEFT/RIGHT arrow keys), and the
cursor will move one line at the time. Hold down SHIFT while dragging the cursor (or SHIFT+LEFT/
RIGHT) for finer increment (the cursor is moved 1/10 of a line). When moving a cursor, the infobar
(D) is updated directly. In the time signal, it is possible to move both parts of a cursor (e.g. A1 and
A2) at the same time by clicking and dragging the small dot in the middle (E). Clicking and dragging
the left dot moves A1, while the right dot moves A2 (ALT + LEFT/RIGHT arrows also moves A2).
To fine tune a cursor, double click it and change the values in the edit window that opens.
- 197 -
9.18 Harmonics and sidebands
Harmonics are shown in the spectrum when clicking the Harmonics button in the toolbar (A) or
CTRL+O on the keyboard. Harmonics marks all multiples of a marked frequency position with orange
triangles. In the Spectrum popup menu under Options, you can activate Harmonic Numbers. The
numbers show the fundamental frequency (Cursor A) and its harmonics (B). To move a harmonic,
simply click and drag it (or click LEFT/RIGHT arrow keys), and the harmonic will move one line at the
time. Hold down SHIFT while dragging the harmonic (or SHIFT+LEFT/RIGHT) for finer increment (the
harmonic is moved 1/10 of a line).
Sidebands can be shown in the spectrum by clicking the Sidebands button in the advanced layout
toolbar (C) or CTRL+B on the keyboard. To move sidebands, click and drag it or click
ALT+LEFT/RIGHT arrow keys. The centre position is the position of the marked frequency. Sidebands
are marked at 1X distance on either side of the marked frequency. This function is used to check on
rpm modulation of a frequency, common in connection with inner race damage and gear damage.
The number of showing sideband can be adjusted in the Spectrum popup menu under Sidebands.
The number of the sideband shows best when zooming in on the spectrum (D).
For the time signal, use the Periods button in the toolbar (E) to show/hide Periods. The same moving
functionality as for Harmonics in the spectrum applies for Periods in the time signal.
- 198 -
9.19 Highest peaks
The Highest peaks tool window (A) is shown by default in the Advanced mode layout, or when
Show Peaks have been activated (see "9.12 Spectrum default layout" on page 192). The Highest
peaks tool window contains a list with the five highest peaks in descending order. Hover the mouse
over a highest peak value in the list to see the fundamental frequency and the harmonics in yellow
color in the spectrum (B) (make sure that Highlight Harmonics is activated, see Spectrum view
popup menu under Options > Harmonic Highlight). Harmonic hits will be shown with harmonic
highlight (see " 9.21 Harmonic Highlight " on page 201 for more information). A double click on a
highest peak value in the list will set the current active cursor on the fundamental frequency.
The highest peaks values can be shown in two different ways; graphical or calculated. Graphical
value means that the peak is always drawn at the middle of a spectrum line, while calculated values
are drawn more close to the true value for the peak (see "9.20 Marked peaks" on the next page for a
zoomed in example). By default, graphical values for highest peaks are shown. Click the ‘...’ button in
the tool window (C) to activate the calculated values. From this menu, it is also possible to change the
number of highest peaks values to be shown in the list.
- 199 -
9.20 Marked peaks
Mark a peak in the spectrum by clicking on a spectrum line. The mark consists of the spectrum line
values and a small dark box (A). Remove the marked peak label by clicking on the marker or the line
again.
Pressing SHIFT while clicking a line will mark the calculated peak, which has a yellow frame around
the small dark box (B).
It is also possible to mark a peak using a cursor; place the cursor on the spectrum line and click
SPACE on the keyboard (SHIFT+SPACE will produce the calculated peak).
- 200 -
9.21 Harmonic Highlight
Harmonic hits in Symptoms indicated with + signs (A), Harmonic match (B)
The function Harmonic highlight makes it easy to see harmonic hits in the spectrum. When hov-
ering the mouse over the grey marked values in the toolbox windows, the hits are highlighted with yel-
low lines in the spectrum. This is because Highlight Harmonics is activated by default (see
Spectrum view popup window under Options > Harmonic Highlight).
Harmonic hits in the Symptom tool window are indicated with + signs for hits on two or more har-
monies, while numbers indicate hits on specific harmonies. In the example above (A) there are hits
on two or more harmonies for the BPFO symptom indicated with a + sign. In the second example
above (B), when hovering over the second highest peak 649.20 Hz, there is a harmonic match at
1298.40 Hz.
Ten harmonics are shown by default in the spectrum. The number of harmonics to show can be
changed from the Spectrum view popup menu under Options > Harmonic Highlight.
- 201 -
9.22 Options and tools
In the Options menu (A), settings for how to show the Spectrum views are available. To find
Options, right click to open the Spectrum view popup menu or click SHIFT+CTRL+O on the key-
board.
Some of the options are:

l Info = shows information (cursor values etc) in the top right corner of the spectrum view
l Grid = shows a background grid in the spectrum (select Dark grid for darker grid color)
l Lines = draws lines between the spectrum bars
l Bars as Watermarks = shows spectrum bars as watermarks (only applicable when showing
data as lines)
l Log X or Log Y = shows the spectrum data in logarithmic scale
l Spectrum Unit = applies for vibration measurement assignments and shows the unit set up
the measuring point data by default, but can be changed to Disp, Vel or Acc
l FFT Type = select between Linear, Amplitude, Power or Power spectral density
l Window Type = select between Rectangle, Hanning, Hamning, Blackman, Kaiser Bessel, etc.
l Waterfall = activates Waterfall (a recommendation is to have Grid activated)
In the lower part of the Spectrum view popup menu (B), there are some practical tools available, such
as: Print, Copy to Clipboard, Save to File, Play As Wavefile (listen to the time signal), Highlight Meas-
uring Point, Force measurement, Set RPM1 from Active Cursor, and shortcuts to Measuring Point Data
and Colored Spectrum Overview.
A useful tool for those using keyboard shortcuts is SHIFT+CTRL+ALT+S = lists all keyboard
shortcuts available in the Spectrum view window.
- 202 -
9.23 Y-scale Max
The Set Y-scale Max alternative is found in the Spectrum view popup menu (A). Clicking Set Y-scale
max opens a new window in which it is possible to change the Y-scale start up values for the current
Spectrum and Time signal. You may enter your own values, or select Auto Calculated (which cor-
responds to the default value) (B). The same applies for the Time Signal (C). Click OK to save.
It is also possible to apply the start up values to other measuring points: tick the Connect settings
box (D), then click ADD (E) to select which measuring points to apply the startup value(s) to. The
From Selected alternative lists matching measuring technique and measuring data point settings
from the current selection seen in the Conditions tool window, while the From All alternative lists all
measuring points in the database with matching measuring technique and measuring point data set-
tings. A click on either of these alternatives opens up a new window in which measuring points can be
selected by using Mark/Unmark, then OK (F). The selected measuring points are now listed under
the Connect settings box (G). Click OK to save the settings.
Reset the settings by selecting Auto Calculated, and click OK.
- 203 -
9.24 Circular Plot
The Circular Plot view (A) is basically another way of looking at the time signal. It is well suited for
visual representation of gear condition, typically used with Time Synchronous Averaging (TSA) in con-
junction with gearbox analysis, condition monitoring of rollers or other machine faults which are syn-
chronous with rotational speed.
The Circular Plot view is activated by default in Spectrum when TSA is activated for the measuring
assignment (given that Auto Layout has not been deactivated, see " 9.15 Spectrum views " on
page 195) or otherwise shown/hidden via the Circular Plot button in the toolbar (B).
By default, the Circular Plot shows the first revolution, but as soon as there is a cursor activated, e.g.
A, the delta between A1 and A2 is shown. Click and hold down LEFT/RIGHT arrows to make the cir-
cular plot rotate. Decide which data to show by moving the A2 cursor as desired. The example above
shows almost one revolution for the 23 teeth for this application (C). Y-scale zooming also affects the
circular plot.
Options available for Circular Plot are found in the Spectrum view popup menu under Options > Cir-
cular Plot (D). The set number of sectors, background image and invert signal options are saved for
the measuring technique (and for the current measuring point).
- 204 -
9.25 Reference Spectrum
Set a spectrum as reference:

l Right click in the spectrum
l Select Reference Spectrum > Set as Reference Spectrum (A)
Any spectrum stored in the database can be set as a reference spectrum for any assignment.
However, an assignment can only have one reference spectrum at any given time.
To set a reference spectrum for the current assignment, right click on the spectrum and select Refer-
ence Spectrum > Set as Reference Spectrum from the drop down menu (A). The reference spec-
trum is automatically placed under the assignment spectrum, drawn with green color and marked
Reference Spectrum (B).
Another way to set a reference spectrum is to right click on the spectrum and select Reference Spec-
trum > Copy to define the spectrum as reference for the current measuring assignment. Then bring
up the assignment spectrum which is to refer to the copy, right click on the spectrum and select
Reference Spectrum > Paste.
Use the Reference Spectrum button (C) available in the Advanced mode layout to show/hide the ref-
erence spectrum. From now on, every time this assignment is opened, the reference spectrum will
show automatically (given that Auto Layout has not been deactivated, see "9.15 Spectrum views" on
page 195 ). To remove a reference spectrum, right click it and select Reference Spectrum >
Delete.
The Y-scale are the same for both spectrums by default. This can be changed by right clicking on a
spectrum and from the popup menu select Options > Individual Y-scaling.
- 205 -
9.26 DS/NDS Spectrum
DS/NDS spectrum is much like a “live” reference spectrum because it shows the measuring result nearest in time instead of a
static value.
A reference spectrum (see "9.25 Reference Spectrum" on the previous page) is a static view of a res-
ult at a given time, while DS/NDS spectrum is much like a “live” reference spectrum because it
shows the measuring result nearest in time compared to the spectrum currently looked at. A DS/NDS
spectrum is used when comparing measuring results with each other, normally Drive Side and Non-
Drive Side (DS/NDS).
To set a DS/NDS spectrum, right click on the spectrum and select DS/NDS Spectrum > Copy from
the drop down menu (A) to define the spectrum as reference for the current measuring assignment.
Then bring up the assignment spectrum which is to refer to the copy, right click on the spectrum and
select DS/NDS Spectrum > Paste. What also happens when doing Paste for DS/NDS spectrum, is
that a cross reference is set: if spectrum 1 is copied and then pasted as DS/NDS reference to spec-
trum 2, then when entering spectrum 1 again, it has automatically gotten spectrum 2 set as its
DS/NDS reference spectrum.
The ND/NDS spectrum is automatically placed under the assignment spectrum, drawn with purple
color and marked DS/NDS Spectrum (B). Use the DS/NDS button (C) available in the Advanced mode
layout to show/hide the DS/NDS spectrum. From now on, every time this assignment is opened, the
DS/NDS spectrum will show automatically (given that Auto Layout has not been deactivated, see
" 9.15 Spectrum views " on page 195 ). To remove a DS/NDS spectrum, right click it and select
DS/NDS Spectrum > Delete. The Open DS/NDS alternative in the DS/NDS Spectrum menu (A)
opens up the DS/NDS spectrum in a separate window.
The Y-scale are the same for both spectrums by default. This can be changed by right clicking on a
spectrum and from the popup menu select Options > Individual Y-scaling.
- 206 -
9.27 Spectrum and symptoms
Symptoms:
l Click on a symptom (A) to mark lines(s) in the spectrum
l Right click on a symptom to change its line color
The Symptoms tool window (A) shows the symptoms attached to the current data. A click on a symp-
tom marks it (A) and theoretical lines in the spectrum are marked with dashed blue lines (B), within
the tolerances set for the symptom. It is possible to show both matched and theoretical lines at the
same time by using the corresponding buttons (C) available in the toolbar for Advanced mode layout.
Theoretical lines are shown by default, but this can be changed in the Spectrum view popup menu
under Options > Symptom default lines.
By right clicking on a symptom, a menu opens in which it is possible to change color for matched and
theoretical lines (D). Click Custom Color, then select color in the following window that opens and
click OK . It is also possible to show or hide symptom names in the spectrum by activ-
ating/deactivating Show Symptom Name in this menu (D).
A click on a symptom group folder shows all its belonging symptoms in the spectrum. For more
information about symptoms, see ahead.
- 207 -
9.28 Symptom harmonics
Symptom harmonics: Hover over a gray marked value to see harmonics in the spectrum.
When hovering the gray marked values in the Symptom window (A), harmonic hits are indicated
with + signs for hits on two or more harmonies, while numbers indicate hits on specific harmonies
(A).
The number of harmonic hits on the symptom are drawn in full yellow color while other harmonics are
drawn with 50% opacity in the spectrum (B). For the modulation symptoms (e.g. BPFIM), the side-
bands are also drawn. Modulation symptoms don’t have a center frequency, but a calculated center
frequency is drawn with 50% opacity in the spectrum as a reference to a center position.
To edit a symptom, double click it to open a symptom editor (C), see "9.29 Editing symptoms" on the
next page for more information.
- 208 -
9.29 Editing symptoms
To edit a symptom, double click it to open the symptom editor (A). When editing a symptom para-
meter value and then moving on to the next parameter value, the spectrum is updated with the new
information. To save the changes, click SAVE (B). This opens up a separate window (C) in which it is
possible to select which parameters to save and if the changes should be saved to other measuring
points and/or to the bearing catalogue.
The edited parameters are listed in the Current Measuring Point box (D). Untick any parameters
that should not be saved. When for example a BPFO symptom has been edited for a specific bearing,
the system checks the database and if this bearing is found on other measuring points are these listed
in the lower Other Measuring Points box (F). In the upper Other Measuring Points box (E), the
edited parameters for the symptom are listed. This provides the opportunity to tick which symptom
parameters should be saved for all or selected other measuring points. Tick the Bearing Catalogue
box (G) if the changes should be saved to the bearing catalogue (the Bearing Catalogue box is only
visible when editing bearing symptoms). Click SAVE (H) to save selected changes.
See below for more information about editing symptoms.
- 209 -
When standing in the symptom editor, clicking the CUSTOM button (A) opens a window (B) from
which it is possible to load a symptom from the symptom register. This is useful when investigating
whether the symptom in the spectrum could be for example ‘unbalance’. Select an ‘unbalance’ symp-
tom from the list (B) and click OK.
The ‘unbalance’ symptom is now shown in the spectrum and in the editor (C). Once a symptom from
the register has been loaded into the editor, it “stays” there (until the Spectrum window is closed).
Therefore, a click on the CUSTOM button from now on always shows the already loaded symptom.
Toggle between the loaded ‘unbalance’ and current symptoms by marking them in the tool window,
then click CUSTOM again to check the ‘unbalance’. Changing parameter values for a loaded symptom
in the editor does not overwrite the symptom register values.
To load another symptom from the symptom register, click LOAD (D).
- 210 -
9.30 Spectrum enhancement
If there are known disturbances, for example from surrounding equipment, the Spectrum enhance-
ment function lets you filter out the corresponding spectrum lines in order to obtain a clearer view of
the relevant signals in the spectrum (D). Depending on the settings you make, this function may also
be used to do the opposite; i.e. highlight interesting spectrum areas (E).
The function is accessed by right clicking in the Spectrum, Compare Spectrum or the Colored
Spectrum Overview and selecting Spectrum enhancement. By default, the function is always
enabled.
To implement the function, select Spectrum enhancement > Open from the popup menu, then
click the NEW button. Under Range (A), ticking the Single line checkbox lets the user input a center
frequency around which a selected number of lines will be hidden (or highlighted). When left
unticked, a frequency range can be input to single out multiple lines.
Ticking By Orders changes the unit of the spectrum frequency axis to orders.
The Visualization settings (B) is where you either hide or highlight certain spectrum lines. To
remove lines, tick the Remove lines checkbox; to highlight, leave the checkbox unticked. Use the
Line color and Background color ‘...’ buttons to further distinguish your selection.
Under Description (C), a describing text can be input and set to be displayed in the spectrum.
In symptom calculation, hidden lines are not included. Condition parameters, e.g. VEL RMS, will not
be affected.
When the function is used in the Colored Spectrum Overview, hidden lines will be dark blue.
- 211 -
9.31 Waterfall diagram
You'll find the Waterfall diagram under Options in the popup menu available in Spectrum, see "9.22
Options and tools" on page 202.
A waterfall diagram is a three dimensional display of 2 - 25 vibration spectra. The different readings
are displayed along the Z coordinate, with the latest nearest the viewer.
You can zoom in on part of the diagram by dragging the cursor across it.
- 212 -
9.32 Order Tracking

Order Tracking is used with Intellinova, Leonova Infinity, Leonova Diamond and Leonova Emerald for
analysis on variable speed applications. It is an ideal technique for analysing vibration problems that
are related to the rotational speed of various machine components. Order Tracking can also be
applied to HD ENV, SPM HD and SPM Spectrum measurements.
The method uses multiples of running speed (orders), rather than absolute frequency (Hz) to deter-
mine the upper frequency range. A tachometer pulse from the machine is required to determine the
sampling frequency. To use order tracking, the Variable speed checkbox must be ticked (found
under the RPM technique in Measuring Point Data).
The purpose of order tracking is to retain the line resolution (number of lines per order) even when
rotational speed varies during measurements. The reference axis of the resulting spectrum is scaled
in orders, i.e. multiples of the rotational frequency. When expressed in orders, two or more spectra
from the same machine can be more easily compared because the rotational speed (1x) and its mul-
tiples (harmonics) will always appear in the same spectrum position (orders), even when rotational
speed varies.
The results can also be displayed in a Waterfall diagram:
- 213 -
The primary advantage of order tracking is that the selected order range will always cover the symp-
toms of interest, regardless of running speed.
- 214 -
9.33 Evaluating multi-channel measurement results
Two-channel measurement result
In the spectrum and the time signal, the channels for multi-channel measurement results are presen-
ted separately. The example above shows results from a two- channel vibration assignment (see
below for an example of results from a three-channel vibration assignment).
Marking a channel either in the Spectrum (A) or in the Conditions tool window (B) shows its spec-
trum data in the tool windows (C). Cursor information (D) is shown for the currently marked channel,
and the value expressed in degrees is the phase. For further information on how to work with the
spectrum, please see previous sections, in which layout, navigation, harmonics, symptoms, and a lot
more is explained.
A two-channel phase spectrum can also be viewed. Right click on the spectrum and select Layout >
Phase. The phase spectrum displays the phase of one channel minus the phase of the other, see next
page for an example. At values beyond ± 180°, 180° is added/subtracted. The scale shows -180° to
+ 180°. To show the individual phases, right click on the spectrum and select Options > Multiple
Channels Phase View > Individual.
- 215 -
Three-channel measurement result
The example above shows results from a three-channel vibration assignment. See above for inform-
ation about how data is displayed. A three-channel phase spectrum can also be viewed. Right click on
the spectrum and select Layout > Phase (A).
Three-channel phase spectrum
The phase spectrum displays the phase of one channel minus the phase of another, and since there
are three channels, several graphs are shown here (B). At values beyond ± 180°, 180° is added/sub-
tracted. The scale shows -180° to + 180°.
The phase difference(s) is shown by default in the phase spectrum. To show the individual phases,
right click on the spectrum and select Options > Multiple Channels Phase View > Individual.
- 216 -
9.34 Pattern recognition in an SPM Spectrum
A = Outer race pattern: Non-rotating. Symptom BPFO. No sidebands but strong multiples indicating heavy damage.
B = Inner race pattern: Rotating. Symptoms BPFI (center frequency) and BPFIM (sidebands), SPM Spectrum.
C = Same pattern from same measuring point in an enveloped vibration spectrum.
Figures A and B show very clear patterns from damaged bearings. In both cases, the shock values are
in the red condition zone.
Typical for a non-rotating, damaged outer race (A) is a strong line at BPFO (ball pass frequency, outer
race). There are no side bands because the race is stationary relative the bearing’s load zone. Usu-
ally, this line has a number of multiples. Marking the line in the spectrum produces the red dot and
writes its position and amplitude above the line. With Show harmonics you produce a grid of red lines
marking all multiples.
Typical for a rotating, damaged inner race (B) is a strong line at BPFI (ball pass frequency, inner race)
with a group of side bands. The spacing between these lines is 1X (the rotational speed of the shaft in
Hz). The side bands indicate that the signal amplitude at BPFI is increasing and decreasing over time,
due to the damaged spot moving in and out of the load zone at every shaft revolution.
Figure C is the result of a traditional enveloped vibration measurement made immediately after meas-
uring the SPM Spectrum (B). The shock pulse spectrum yields clearer data, because it is based on the
time record from a calibrated resonating body (the shock pulse transducer).
- 217 -
D = Impeller pattern: Vane pass frequency (VPF), symptom 50. Signal measured on a cavitating pump.
E = Impller pattern: Same as (D), with a logarithmic Y-scale clearly showing the multiples of VPF.
F = No discernible pattern: Matches found for all symptoms but no clear pattern. This spectrum does not allow any con-
clusions.
Negative evidence is also valuable. The SPM Spectrum in figures (D) and (E) is from a pump with a
cavitation problem. The high shock values (yellow zone) are not from the bearing. The dominant fre-
quency line matches the pass frequency of the impeller blades. The function Logarithmic Y-scale
reveals the pattern of VPF multiples.
Inconclusive evidence is not helpful but must be expected, especially when measuring on good bear-
ings. The SPM Spectrum in figure (F) contains no discernible pattern.
For Leonova, the SPM Spectrum type can be set to Pattern recognition (SD), where each spec-
trum is scaled so that the total RMS value of all spectrum lines = 100 SD = the RMS value of the time
record. The alternative is Symptom value (SL), the RMS value of the frequency component in
decibel. Alert levels are manually set for each symptom to show evaluated results in green - yellow -
red.
- 218 -
9.35 Compare spectrum
With the Compare spectrum function, you can view more than one frequency range and/or res-
olution at a time. This means that you can implement a variable frequency range from one measuring
assignment to another and also between measuring points.
Other features of the Compare spectrum function are:

l the possibility to display a list of symptoms, where one or several symptoms can be high-
lighted for easy evaluation. Each symptom can be assigned an individual color and its name dis-
played in the spectrum.
l The Y scale can be manually set or optimized per individual spectrum.
l Reference spectrums can be set and be displayed or hidden as required.
l The possibility to change the display order of spectrums or delete any spectrums in between,
enables comparison between spectrums from the same measuring point at different points of
time.
l When calling the single spectrum function, zoom and symptom settings are retained.
When you plan to start working with Compare spectrum, it is advisable that you begin by deciding
what symptoms should be shown in the spectra, and in what colors. These settings will apply to all
spectrums throughout Condmaster. Select all measuring points by marking the Measuring points
folder in the Graphical Overview, then click the right panel menu and select Compare spectrum
(under Graphical Overview). In the right part of the Compare spectrum window, select each symp-
tom that you want shown in the spectra, then click the “...” button to make settings for color and
whether or not symptom names should be shown in the spectra.
- 219 -
Selecting measuring points for Compare Spectrum
To view the Compare spectrum function, first select the measuring point (s) (or folders) in the
Graphical Overview (A). To select multiple measuring points, hold down the CTRL button on your key-
board and left click on each measuring point of interest, then click Compare Spectrum in the right
panel menu (B). Measuring points can also be selected by dragging across them with the left mouse
button held down.
If a selected measuring point has more than one assignment, all of them will be included in Compare
spectrum.
- 220 -
Working with Compare Spectrum
In the Compare spectrum window, the Individual Y-scaling button (A) turns optimization of the
individual spectrum scaling on or off.
Click the Show reference spectrum button (B) to show/hide any reference spectra available.
Mark an individual spectrum and use the arrow buttons (C) to move it up or down in the list of spec-
tra.
The Maximize/minimize spectrums button (D) displays or hides the symptom list to the right (E).
Select symptoms to show in the spectra from this list by double clicking on the symptom(s), or by
marking them and clicking on the Select symptom button. The lines then shown (standard color =
red) are the actual matches for the symptom in question. To instead see where the peaks should the-
oretically appear e.g. for a damaged inner ring, tick the box Theoretical symptoms (H) (standard col-
or= blue).
Marking the box Multi select symptom (H) makes it possible to select numerous symptoms.
Use the “...” buttons (I) to change the symptom line standard colors and to display or hide symptom
names in the spectra.
Double clicking on a spectrum unit (F) displays or hides all spectra with this unit.
In the individual spectrum, you can move between measurements by clicking on the left/right arrows
(G). A right click in the spectrum brings up a popup menu where e.g. the spectrum can be set as ref-
erence spectrum. Right clicking while moving the mouse brings up a movable cursor. Zooming in the
frequency ranges is possible using the left mouse button and dragging in the spectrum. Use the Back
button in the tool bar to zoom back.
- 221 -
9.36 Colored Spectrum Overview

The Colored Spectrum Overview is a three-dimensional view of all spectrums under a particular
measuring assignment. Its purpose is to simplify the process of identifying in spectrums the patterns
and trends which indicate damages. In the Colored Spectrum Overview, signals which are always
present in the machine are clearly distinguished from signals caused by developing damages. The
Colored Spectrum Overview provides a very good overall picture of machine condition development.
Patterns and trends are easily detected in the overview, particularly in “noisy” spectrums. There is no
need to predefine what symptoms should be highlighted; the overview displays all symptoms by
default. Spectrums can be viewed in orders, Hz or CPM.
Where to find it
The Colored Spectrum Overview is always accessible from the right panel menu under Graphical Over-
view, and can also be found be found in the following places:
l Graphical Overview (Colored Spectrum button in the ribbon bar)
l Measuring results
l Graphic evaluation
l Spectrum
l Compare spectrum
- 222 -
9.36.1 Colored Spectrum Overview functionality
The Colored Spectrum Overview window is packed with information. Here’s a brief description of
the main elements (please see screenshot):
l Tool bar (A): The tool bar contains the following functions:
1. Go to previous/next measuring assignment.
2. Select measuring assignment from a list (applicable only when a measuring point is
marked in the Measuring Point Tree, rather than an individual measuring assignment).
3. Zoom back.
4. Show/hide focus rectangle. Activate the focus rectangle (4, 11) to zoom in on a par-
ticular area in the color spectrum. A magnification of the focused area is shown in the
zoom window, to the right of the color spectrum (D). The size of the focus rectangle can
be changed by pointing at the “extra” handle in the lower right corner of the rectangle
and dragging to the desired rectangle size. Harmonics are always shown. Sidebands can
be activated by the user.
5. Zoom in/out in the color scale to emphasize colors in the spectrum.
6. Spectrum information field: when you hover the mouse over the color spectrum, or
when the focus rectangle is activated, details about the spectrum currently pointed at
(or in focus) is displayed here.
7. Show/hide RPM/symptom list, Zoom window and individual spectrum.
8. Show/hide zoom window.
9. Show/hide individual spectrum.
10. Show/hide measuring point image (photo of measuring point location).
- 223 -
l Color spectrum (B) : Occupying the major part of the Colored Spectrum Overview win-
dow, this is the collection of spectrums under the measuring assignment. Comments are
shown below the graph as small, colored squares which can be clicked on the display or edit
the comment. Click on ‘X Orders’, ‘X Hz’ or ‘X CPM’ on the Y axis (12) to toggle between them.
Right click in the color spectrum for a popup menu with further options.
l RPM/symptom list (C): This is a list of the symptoms etc. set up on the measuring point.
Mark one to display RPM and symptom values (F) for the current measuring result. Matching
symptoms for the current position in the color spectrum are indicated with red arrows in the
list and in the color spectrum, or blue arrows for theoretical matches.
l Zoom window (D): Shows a magnification of the spectrum currently pointed at (or in focus)
in the color spectrum. The bluish grey arrows on each side indicate the highest value and its
sidebands (if any).
l Line graph (E): The trend curve of the order currently pointed at (or in focus) is displayed
immediately below the color spectrum. The current center position in the color spectrum is
indicated with two bluish grey arrows.
l Symptom graph (F): The trend curve of the RPM or symptom currently marked in the
RPM/symptom list is displayed in the lowermost part of the Colored Spectrum Overview win-
dow.
l Individual spectrum (G): In the lower right corner of the Colored Spectrum Overview win-
dow, the spectrum corresponding to the measuring result currently in focus is displayed. Under
the ‘...’ button, the display of theoretical lines can be turned on or off.
- 224 -
9.36.2 How the colored spectrum overview is created

1) On all spectrums under the selected measuring assignment, amplitude is translated into a relative
color scale:
2) The spectrums are “piled up” into a stack, then the whole lot is turned upwards and displayed from
above:
3) The result can be thought of as a topographic map, only here the tightest contour (or altitude) lines
correspond to the color red:
- 225 -
9.37 Introduction to Condition View
The Condition View function is a powerful tool for presentation and further analysis of measuring
results.
Multiple graph types (e.g. spectrums, time signals, condition trends and more) and measurement
assignments from one or more measuring points can be combined in a single window. For instance,
you might want to see and compare measuring results from both the drive and non-drive ends of a
roll, or time signals from multiple axes, in order to get a complete view of machine condition.
Printout via Condition View Report or Customized Reports
The information in Condition View also provides the basis for the Condition View Report and Cus-
tomized Reports features, where you can create reports and save them in Microsoft Word format
for printout.
The reports can be used to show current machine condition, recent condition development, or main-
tenance actions, e.g. to clarify or justify planned maintenance activities to maintenance teams or
management. For further information, see "16.10 Condition View Report" on page 397 and "16.11
Customized Reports" on page 408.
- 226 -
9.38 Getting started with Condition View
Start by selecting one or more measuring points in the Graphical Overview (to select multiple meas-
uring points, press the SHIFT or the CTRL key and mark the ones you want to include in Condition
View) (A).
NOTE: When selecting more than one measuring point in the Measuring Point Tree, Condition
View will display them in the order you selected them (to the left of the measuring point number,
you’ll see your selection being numbered in sequential order (A)).
When you’ve made your selection, click the Condition View icon (B) in the ribbon bar (or press the
F12 key).
- 227 -
Saving selected measuring points as a sequence

To save yourself some time and effort in the future, your selections of measurement assignments can
be saved as sequences that can be loaded into Condition View with a just a couple of clicks.
In the Condition View window, click the ellipsis (‘…’) button in the toolbar (A), select Sequence ->
Edit (B) -> click the SAVE SEQUENCE AS button (C) and give the sequence a descriptive name (D).
Next time you wish to open Condition View with a particular sequence of measurement assign-
ments, just right-click on the Condition View button in the ribbon bar and select the sequence from
the popup list (E):
- 228 -
Viewing Trend Graphs
The Trend Graphics tab (A) shows trend graphs for the current measurement task. To change the
number of visible graphs, right-click and choose Number of graphs per page (B). Click Edit Mode
(C) to add or insert trend graphs to the view.
Assigning graphs from Graphic Evaluation to Condition View
The advantages of assigning the graphs from Graphic Evaluation to Condition View are the possibility
to filter and change graphs for more than one measurement assignment at a time. To assign graphs
to Condition View:
- 229 -
1. Select a measuring point, component or folder in the Graphical Overview.
2. Click the Graphics icon (A) found under the Graphical Overview tab in the ribbon bar.
3. In the Graphical Evaluation window, modify the graphs as desired.
4. Click the ellipsis ('...') button (B).
5. Click Assign graphs to Condition View (C). A confirmation window is shown. Click OK.
6. Go back to Condition View. The graphs are now available under the Trend Graphics tab.
9.39 Elements of the Condition View window
Here is an account of the user interface and functionality of the Condition View window:
l Use the arrow up/down buttons (A) to toggle between measurement assignments and meas-
uring points. You can also use the CTRL and arrow up/down keys on your keyboard to do the
same thing.
l Under the ellipsis (‘…’) button (B), a menu of shortcuts is found.
l You can switch between the Trend Graphics tab (D), which shows trend graphs for the cur-
rent measurement task, and the Condition View tab.
l When enabling status in the settings menu, your defined status (F) appears. Add the statuses
you want, "Acceptable" or "Unsatisfactory" for example. For these statuses, a common text as
"Lubrication needed" or "High temperature" can be defined. The No Reading icon (G) is
shown if results are missing within the user-defined time frame.
l Ticking the Detailed printout checkbox (C) makes the Condition View graphs and the con-
tents of the right panel (alert list, attachments, deviations, comments and image) available for
printout via the Condition View Report function, where it appears under Detailed Page(s).
For more information, see the "16.10 Condition View Report" on page 397.
- 230 -
l Using the Attachments button (H), the entire panel to the right of the Condition View win-
dow – displaying alert list, attachments, deviations, comments and images – can be shown or
hidden.
l The Edit Mode button (I) opens a new window where the default Condition View and Trend
Graphics layouts can be customized (for more information, see the "9.44 Editing the content
and layout of Condition View" on page 239 section).
l Double-click on any graph (spectrum, time signal etc.) to open it in a separate window. Right-
click to open a context-sensitive menu (E).
l In the panel on the right, double-click on any section to open the content in a separate window.
Right-click to add, edit or delete (J).
NOTE: The possibility to add attachments in Condition View is particularly useful; for more
information, see section "9.42 Adding attachments" on page 233.
l The various ZOOM buttons (L) are used to zoom back out to view the full graph after you have
zoomed in. For example, all time signals displayed in the Condition View window will be
zoomed back out with a single click.
NOTE: if, after having zoomed in, you toggle to another measurement assignment and then
toggle back again, the graphs in the first measurement assignment will automatically be
zoomed back out. This behavior can be changed under Settings -> General -> Clear zoom
on startup.
l Click the Alert list, Attachments, Deviations, Comments or Image buttons (K) to hide or
show the corresponding information in the panel.
9.40 Condition View settings
- 231 -
Under the ellipsis (‘…’) button in the toolbar (A), the Settings (B) option offers a range of settings to
customize the appearance, content and behavior of Condition View in various ways (C).
To simplify the work with settings when you for example have a new database, you can import and
export (D) your Condition View settings (the settings are saved in the file format .cvSettings).
9.41 Default Condition View layout
Depending on what measuring assignments are under each of the selected measuring points, the
default layout of the Condition View window will vary.
In the graphics part of the Condition View window (A), the various graphs are displayed in separate
squares, acting like ‘containers’. By default, the graphs are displayed in a row-based layout. In the
panel to the right of these graphs (B), the alert list, attachments, comments and images (if any) are
displayed.
To suit different needs, the default layout can be customized by the user and saved, either for all eli-
gible measurement assignments, or only for a selection of them (see section "9.44 Editing the con-
tent and layout of Condition View" on page 239).
Graphs, comments/explanations and pictures can be added in the form of attachments, in which case
they will be part of the Condition View Report (see section " 16.10 Condition View Report " on
page 397). After the attachments have served their purpose as part of a printed report, they should
be deleted.
TIP! When working with your content in the Condition View window, press CTRL + P on your key-
board, then click the UPDATE button in the Preview window that opens to see (and print) a pre-
view of how the graphs and information will look when included in a report.
- 232 -
9.42 Adding attachments
Attachments are very useful to comment, clarify or supplement the information in the Condition
View graphs. Accepting free text, graphs and images, the attachments option is very flexible. Condi-
tion View accepts multiple attachments.
The possibility to add an attachment is available in all graphics functions in Condmaster:
- Condition View - Trend Graphics

- Spectrum - Colored Spectrum
- Time Signal - Lubmaster
- Phase - Orbit
- Circular Plot
Just right-click in a spectrum, time signal or other graph and select Add to Attachments from the
popup menu to include it in Condition View. From there, you can double-click on the attachment to
open it and add more content, such as free text and/or pictures.
When including attachments in Condition View Report (for more information, see section "16.10
Condition View Report" on page 397), it might look something like this example page, containing
three attachments:
- 233 -
Condition View Report sample page containing three attachments.
- 234 -
Viewing All Attachments
Condition View shows only the registered attachments for the selected measurement assignment. To
view all attachments:
1. Right-click in the Attachments section and click All Attachments (A).
2. If you also want to show archived attachments, tick the checkbox Show Archived Attach-
ments (B).
3. To archive an attachment, right-click and select Edit (C). Tick the Archived checkbox (D).
- 235 -
9.43 Adding Deviations
1. In the Condition View window, click the ellipsis ('...') button (A).
2. Click Settings (B).
3. Click Deviations (C).
4. Tick the checkbox 'Use Deviations'.
5. Click Selectable Standard Comments.
6. For creating a new list of standard comments, click New.
7. Select the standard comments desired by ticking the checkboxes. Click OK.
8. Click Save.
9. Select which information should be included in the deviation. Click OK. A Deviation section
appears in the panel to the right.
- 236 -
10. In the Deviation section, right-click and select Add Deviation (D). Alternatively, right-click
a spectrum, time signal or other graph and select Add to Deviations (E).
11. Click Add Note (F). A header is then added.
12. Enter your notes where the cursor is placed.
13. Fill in the information required in the General (G) and Additional (H) fields. Click Save. The
deviations are listed in the Deviation section.
- 237 -
Viewing All Deviations
Condition View shows only the registered deviations for the selected measurement assignment. To
view all deviations:
1. Right-click in the Deviation section and click All Deviations (A).
2. If you also want to show closed deviations, tick the checkbox Show Closed Deviations (B).
3. To close a deviation, right-click and select Edit (C). Tick the Closed checkbox (D).
- 238 -
9.44 Editing the content and layout of Condition View
Example: Spectrum and time signal from both ends of a shaft
Let’s say you want to compare the spectrums from both ends of a shaft. In Condition View, you can
position the two spectrums – from two separate measuring assignments on two separate measuring
points - next to each other in the same window; complete with zooming, cursor and fault symptom
capabilities. By combining multiple graphs in this manner, you’ll be able to get a comprehensive view
of the operating condition of an entire machine, and analyze the readings from all its measuring
points in relation to each other.
To accomplish this, however, you’ll need to edit the default content of the Condition View tab,
because the default view only shows graphs from a single measuring point and a single measuring
assignment. See below for more information.
- 239 -
Click the Edit Mode (padlock) button farthest to the right in the toolbar to open the edit window.
You’ll see a dimmed version of the default content and layout in the left part of the window (A) – with
the top left graph marked – while the panel to the right (B) now contains editing tools, and properties
(C).
Customization options in edit mode

The panel shows a list of items representing the current layout of the graphics section. In order to cre-
ate the layout you want, it is important that you understand this list representation:
- 240 -
When using the ADD or INSERT buttons in the panel, the following options are available:
l Square: the “box” that contains the individual graphs;

l New line (square): row break
l Object: any of the graphs available on the individual measurement assignments
l New line (object): row break within a square
l Title: adds a repositionable title bar to an object.
- 241 -
Horizontal or vertical layout

Items (squares and objects) can be added or inserted in the horizontal or vertical direction:
l ADD or INSERT -> New line (Square) performs a horizontal row break. NOTE: depending
on what item is marked, inserting/adding a new line might not necessarily show any changes
in the graphics section, until you add or insert a square and/or an object.
l ADD or INSERT -> New line (Object) performs a horizontal row break within the marked
square. Again, you may have to add or insert a square or object before the change is visible in
the graphics section of the window.
l ADD -> Square (i.e. without first adding or inserting a new row break) puts a new, empty
square at the very end of the current layout/list, regardless of which item was originally
marked in the list:
- 242 -
l INSERT -> Square (i.e. without first adding or inserting a new row break) puts a new, empty
square (B) immediately before the marked list item (A):
l ADD or INSERT -> Object (i.e. without first adding or inserting a new row break) splits the
marked square vertically and inserts the selected object (graph) within that square.
All items (squares, objects/graphs, lines and titles) can be moved to a different position using drag-
and-drop or by clicking the arrow up/arrow down buttons at the top of the panel. You can also use the
SHIFT + CTRL + Up/Down keys on your keyboard to move items.
- 243 -
Sorting the graphical content in rows vs. columns
Under the ellipsis ‘…’ button, the default row-based layout of the graph section of the Condition
View window can be changed into a column-based layout (A):
The difference between row-based and column-based layout:
- 244 -
Object types
When adding or inserting a new object, first select a measurement assignment and then a graphical
object from a list of object types ((A); the list options may vary depending on measurement assign-
ment settings).
Depending on measurement assignment settings, there may be further options when selecting object
types ‘Graphics’ (B) and ‘Spectrum’ (C).
- 245 -
Saving your changes
When you exit edit mode by clicking the Edit mode (padlock) button (or by hitting the ESC key), any
changes you have made to the selected measurement assignments will be automatically saved, so
they will look the same the next time you open them in Condition View.
Under the ellipsis ‘…’ button (A), further options are available:
l Apply to (B): although they may not necessarily be included in your current Condition View
selection, the current content and layout can be applied to other measurement assignments of
the same kind (same measuring technique) or only to a user-defined selection of meas-
urement assignments using Apply to.
In the Apply to window on the Accepted (C) tab, you will see all other measuring points hav-
ing measurement assignments with the same measuring technique as the one you are cur-
rently viewing in Condition View . In this list, mark the measuring points which should
henceforth have this content and layout when you open them in Condition View.
Mark or unmark your selection by double-clicking on them or by using the MARK/UNMARK

button (D). You can also select multiple rows in sequence by marking one, and then using the
space bar to mark/unmark several subsequent rows in the list.
If it’s a long list of measuring points, you can use the PAGE UP and PAGE DOWN keys on your
keyboard to go to the top or the end of the list.
On the Rejected (E) tab, you’ll find the measuring points whose measurement assignments
have different settings in some way that disqualifies them from applying the current Condi-
tion View content to them.
l Restore to default (F): restores the current Condition View content and layout to the
default for the selected measurement assignment.
l Undo changes (G): with a single click, this will undo all your changes that have not yet been
saved. If you wish to remove only a specific item, mark it and use the DELETE button. NOTE:
the Undo operation will also apply if you have changed the layout from row-based to column-
based layout.
- 246 -
9.45 The Polar plot function

For the Phase symptom, the Polar plot function provides a way to visualize amplitude and absolute
phase angle in a single graph, making it possible to monitor the trends of the two together. Along with
the polar plot, the function also displays a Bode plot.
Accessed from the ribbon bar, the Polar plot function can be selected when a measuring assignment
that includes a saved time signal is marked in the Measuring Point Tree (or in the Graphical Over-
view):
The function can also be accessed under Graphical Overview in the right panel menu.
The Polar plot function offers the possibility to trend the development of phase differences over
time. It can reveal deviations that cause phase changes, but which are not necessarily reflected in a
clear increase in vibration amplitude. Vectors of 1X, 2X, etc., can be examined in the polar plot.
- 247 -
Working with phase symptoms in the Polar plot function

Selecting the Polar plot function in the ribbon bar opens the Polar plot window, the main parts of
which are:
l a polar plot (A)

l a Bode plot showing amplitude (B) and phase (C) trends,
l a measurement results panel, showing two different tabs: All results and Selected results
(D).
In the lower right part of the window (E) are Date/time and RPM filters, along with further condition
parameters (orders of rotational speed), as well as the phase and ACC/VEL/DISP symptoms set up on
the measuring point, with checkboxes for turning their display in the graphs on or off.
When opening the Polar plot window, the following defaults apply:
- Parameters: 1X, 2X, 3X, 4X, and 8X.
- Symptoms: if one or more phase symptoms are set up on the measuring assignment, their respect-
ive checkboxes will be marked. If no phase symptom exists, the ‘1X’ parameter will be marked for dis-
play in the graphs.
- Symptoms: DISP, VEL or ACC (depending on the spectrum unit setting) will be marked for display.
Any changes to these default settings will be saved and will thus continue to apply between instances
of running Condmaster (for more information on editing default settings, see "Customizing the Polar
plot window settings" on the next page.
- 248 -
Customizing the Polar plot window settings

Under ‘…’ > Settings in the toolbar (A), the default settings can be edited:
In the Settings > General section (B), settings to control the look and behavior of constituent parts
of the Polar plot window are found.
The Settings > Parameters section (C) offers the possibility to change, add, and activate or deac-
tivate parameters, and change their respective default colors. Parameters must only be integer mul-
tiples of the rotational speed.
- 249 -
In the Settings > Symptoms section (D), the default color of a maximum of ten symptoms can be
changed.
NOTE: The default Parameter colors can be temporarily changed by clicking on a color box and
selecting Assign temporary color (E):
- 250 -
The polar plot

The polar plot (also known as a Nyquist diagram) is found in the top left of the window. The display of
phase and amplitude data in polar coordinates visualizes phase changes in the range of zero to 360
degrees. Phase angle and vibration amplitude graphed together in a polar plot are displayed as vector
quantities. Each measuring result thus constitutes a vector, i.e., a line with an amplitude and a dir-
ection. In the polar plot, the “tips” of the vectors are plotted at a distance from the center that rep-
resents their amplitude, and at angles showing absolute phase.
The circular area alert (acceptance region) in the polar plot represents an area where all vibration vec-
tors falling within the region are considered normal, while those found outside the region are con-
sidered deviations and will generate an alert.
The polar plot displays 1X vibration (typically caused by imbalance) and integer multiples (2X, 3X,
etc.). It shows the same data as the two graphs to the right, known together as a Bode plot, which dis-
play amplitude in the top diagram, and phase in the bottom one. In some cases, the Bode plot can be
easier to follow, since the polar plot displays neither time nor rotational speed. For more information
about these graphs, see "The Bode plot" on the next page.
Bode and Nyquist diagrams are often used to determine critical speeds in turbomachines when data is
collected during run-up and coast down, and to keep track of vibrations during startup.
The polar plot can also be included in the Condition View function.
The functionality of the polar plot includes:

l zooming in by dragging the mouse from left to right, and zooming back out by clicking on
’Zoom back’.
l marking/unmarking an individual measurement result by clicking it; detailed information is
shown in the yellow panel in the top right corner of the Polar plot window.
l marking/unmarking multiple measurement results at once by holding the CTRL key while
zooming.
l opening the graphs panel in a separate window by clicking on the ’Full view’ icon in the upper
right corner of the panel, and returning to the Polar plot window by clicking the icon again.
l hovering over a measurement result to highlight the corresponding measurement in the Bode
plot (amplitude and phase graphs).
For information about how to interpret the results, see "9.46 Interpreting the phase symptom results"
on page 254
- 251 -
The Bode plot

The Bode plot shows the amplitude gain (A) and phase response (B) for the active symptoms. The
same information is presented in the polar plot to the left, which graphs amplitude versus phase in
polar coordinates rather than along XY axes.
In the amplitude graph, the total level can also be displayed by marking the Vel, RMS checkbox
under Symptoms (C). The overall vibration level gives an estimate of the amplitude of individual fre-
quency components in relation to the total amplitude level.
The functionality of the Bode plot includes:

l toggling between RPM and time on the X-axis by clicking on its unit, immediately below the
graph.
l zooming in along the X and Y-axes by dragging the mouse, and zooming back out by clicking
on ’Zoom back’. When zooming in, the polar plot is also updated automatically to display the
same subset of measurement results as the Bode plot.
l marking/unmarking an individual measurement result by clicking it; detailed information is
shown in the yellow panel in the top right corner of the Polar plot window.
l marking/unmarking multiple measurement results at once by holding the CTRL key while
zooming.
l opening the graphs panel in a separate window by clicking on the ’Full view’ icon in the upper
right corner of the amplitude or phase graph, and returning to the Polar plot window by clicking
the icon again.
l hovering over a measurement result to highlight the corresponding measurement in the polar
plot.
If the diagrams show deviating values, it may be interesting to find out if they are a natural con-
sequence of varying operating conditions (e.g. speed), rather than an indication of deteriorating
mechanical condition. Deviating values can be marked and thus highlighted in all the graphs, as well
as on the Selected results tab, where it is easy to see when the readings were taken and compare
these times to the operating conditions at the current time. Showing rpm on the X-axis in the Bode
plot is another intuitive way to show if the values were measured at different operating speeds.
- 252 -
For information about how to interpret the results, see "9.46 Interpreting the phase symptom results"
on the next page
The measurement results panel

The measurement results panel in the bottom left part of the Polar plot window displays a table of
readings included in the polar and Bode graphs. The All results tab (A) always shows the entire set
of measurement results (regardless of any filter settings), while the Selected results tab (B) shows
a subset of results based on user selections.
In the measurement results table, the following applies:

l marking a measurement result on either tab in the table (A, B) will highlight the result in the
graphs, and detailed information will be shown in the yellow panel in the upper right corner of
the window.
l user selections made under Parameters (C) and Symptoms (D) determine which columns
are shown in the table.
l when clicking on a measurement result in any of the graphs, the Selected results (B) tab is
always displayed, and the selected result is highlighted in amber color.
l when toggling between table rows, the corresponding measurement result is highlighted in the
graphs.
l the measurement results on the Selected results tab (B) are sorted 1) according to the order
of the symptoms activated under Symptoms (D), and 2) by the time of the measurement
(i.e., according to the X-axis in the Bode plot).
- 253 -
9.46 Interpreting the phase symptom results

When using the polar plot to diagnose machine faults, the same rules of thumb apply as when inter-
preting a frequency spectrum, except that only integer multiples of the rotational speed can be seen
in the polar plot. To get the whole picture, it is therefore recommended to examine both spectrum
and polar plot.
If the amplitude is low, near the noise level of a frequency component, the phase value may vary sig-
nificantly because the low amplitude level is caused, or influenced, by non-periodic forces.
If the rotational speed changes, amplitude and phase will also change. This difference in operating
conditions may cause readings outside the alert circle (acceptance region), in turn generating an alert
that in fact has natural causes. The radius or position of the alert circle itself will not change with chan-
ging speed; if it goes outside the rpm range set up on the measuring point, no alert will be raised.
If a resonance frequency is passed during run-up/coast down, it will show up as a circular movement
in the polar plot; as a peak in the amplitude graph in the Bode plot; and as a 180° change in the
phase graph (in theory – providing that enough data is collected, and assuming that the value is not
affected by other resonances). This may explain any large movements that may occur in the polar
plot during variations in rotational speed. Near a resonance frequency, even small rpm variations can
lead to significant changes in phase and amplitude.
If the amplitude unit on the measuring assignment is changed from displacement to velocity, there
will be a 90° phase difference, and a further 90° if it is changed from velocity to acceleration. Thus,
between displacement and acceleration, the difference is 180°.
In the phase graph in the Bode plot, possible values are 0- 360°. If the value is at 359° and it
increases by 2°, the value will end up at 1°, i.e., at the bottom of the Y-axis. Thus, despite only a
slight change in phase, it will look like a significant movement in the graph (whereas in the polar dia-
gram, where 0 and 360° degrees correspond to the same position, a 2° change will appear less dra-
matic). In the polar plot, phase change can be more intuitive and easier to understand, since they are
displayed as a change in vector angle.
- 254 -
10. EVAM Evaluation
10. EVAM Evaluation

10.1 The evaluation of EVAM readings
Criterion calculation:
l A criterion is based on a defined set of measurements (A)
l The green - yellow - red condition zones depend on mean value and standard deviation (B)
Looking at spectra and studying the trends of condition parameters may, on occasion, be useful, but
it does not provide you with the fast condition analysis needed for efficient condition monitoring. Both
the SPM method and vibration severity measurements (VIB) work with general evaluation standards
which apply to all bearings of a type (SPM evaluation) or all machines of a class (ISO standard).
These only need fine tuning for exceptional applications.
EVAM readings need an individual evaluation, based on the vibration readings (A) from a specific
machine or even a specific measuring point. Only experience can show whether the same evaluation
standard can be applied to several similar machines.
The evaluation of EVAM parameters is based on statistics: the mean value and standard deviation (B)
obtained from a number of representative vibration readings. The readings should cover the whole
range of normal operating conditions (speed, load, temperature, etc.) that affect the machine’s vibra-
tion behaviour, because you will get a ”bad condition” indication whenever a reading falls outside of
the normal range, and this can either be due to abnormal machine vibration (which you try to detect)
or too narrow a base.
A specific set of evaluation data is called a criterion. The calculations are automatically made by Cond-
master; all you have to do is select the vibration readings to be included. To quickly acquire a set of
readings for evaluation, the Recording function in Condmaster can be used (see the following pages
for more information).
- 255 -
10. EVAM Evaluation
10.2 COND numbers in graphics and spectrum
COND numbers in graphic evaluation and spectrum:

l COND no. graph for every condition and symptom parameter (A)
l Click on measurement to see evaluated parameters (B)
l COND nos. and value for COND = 0 in the spectrum (C)
The result of the application of a criterion is a non-dimensional COND no. (condition number) for each
active condition parameter and symptom. In Graphic evaluation, you can switch from a raw value dia-
gram to a COND no. diagram (A), or activate both. You can click on any measuring result in an EVAM
diagram and see all parameter values plus their COND nos. marked in green - yellow - red (B).
In the spectrum, you now see the parameter value plus the corresponding COND no. You also get the
mean value of the measurements belonging to the criterion, under COND = 0 (C).
- 256 -
10. EVAM Evaluation
10.3 Recording a batch of readings for the Leonovas
Recording set:
l Open a measuring point, press MENU and select Recording.
l Set number of measurements (A), measuring interval (B).
l Click New (C), select technique (D). Start recording by pressing MEASURE.
A recording set for the Leonova instruments consists of at least one measuring point and different
measuring techniques.
A typical application for vibration measurement are run-up and run-down controls on machines that
change their vibration behaviour during the starting and stopping period. Use spectrum settings with
short acquisition times and measure ”as fast as possible”.
To make an adequate criterion for the evaluation of measuring results, you have to obtain vibration
readings covering the whole range of normal operating conditions of a specific machine. This may
take considerable time. A practical way to start is the function ”Recording” in the Leonova instru-
ments, which allows you to quickly collect a set of data for a preliminary criterion. Please note that
this is a shortcut, not likely to provide a very accurate base for correct machine condition evaluation,
but it gives you a starting position and you can – and should – make a more appropriate criterion
once you have sufficient data.
Download a single measuring point or round to Leonova and open it. Select Recording from MENU.
You can record a stated number of measurements at stated intervals, or measure for a stated number
of minutes. The field (F) toggles between ‘measurements’ and ‘minutes’.
Input the number of measurements (A) and the time interval (B). ”0” in the time field means ”as fast
as possible”. Use the key NEW (C) and select measuring technique (D) - selected technique will show
on the list under Measuring sequence (E). Connect the transducer and use MEASURE to start.
- 257 -
10. EVAM Evaluation
10.4 Recording a batch of readings for A/T30
Recording set:
l Click NEW (A), input Name and select Instrument (B)
l Click NEW (C) and, after data definition, SAVE (F). Transfer (H).
For A/T30, ”Recording” is similar to making a round and using Data transfer. Open ”Recording” and
click NEW (A). This brings you to the editing form where you input a name for the set and select the
instrument (B). Click NEW (C) on this form to define measuring points and measurements. Each
measuring point will be listed on the edit form (D). At the bottom of the form the required memory for
the measurement is displayed (E). You will get a warning in case the instrument capacity is exceeded.
Save the set (F).
Set name and instrument are listed on the recording form (G). Download/upload as with a measuring
round (H).
- 258 -
10. EVAM Evaluation
10.5 The Condition Manager

What used to be called the Criteria Guide in earlier Condmaster versions had a complete makeover in
Condmaster Nova 2010 in order to allow greater flexibility in alert configuration. The Condition Man-
ager is a general improvement applicable to EVAM, SPM Spectrum SL and SPM HD readings obtained
with any SPM measuring device (flexible condition evaluation is not applicable to ISO2372/10816
measurement, where alert limits are defined by the ISO standards).
Furthermore, users of the Intellinova online system can use machine operating conditions such as
power, flow or pressure as criteria to determine equipment running condition (for further information
on the use of machine operating conditions in Intellinova, please see "15.13 Machine operating con-
ditions" on page 341).
10.5.1 Alert options

Over the years, Condmaster alert options have evolved and by the Condmaster Nova 2008 version,
they included:
l Level alerts, i.e. a yellow or red alert is triggered whenever a measured parameter reaches a
certain, user defined threshold. This type of alert is static and therefore works well on applic-
ations running with fixed speed and stable loads.
l Moving average alerts; essentially the same as above but the value triggering the alert is a cal-
culated average of a user defined number of measuring results rather than one individual read-
ing. With moving average, alerts caused by sudden and random amplitude increases are
avoided. The system calculates a mean value of x number of readings and calculates a new
mean every time a new reading is registered. The higher the number of readings for mean cal-
culation, the flatter the resulting curve will be. Moving average alerts are preferably used on
applications subjected to randomly high readings from unexpected events.
l Bands (single, multiple and octave): In a spectrum, the use of bands is an efficient way of isol-
ating symptom frequencies from each other. The RMS value of all the amplitudes within a user
defined frequency range are then added to each other, resulting in a bar graph of the energy
contained in the different frequency bands.
l Criteria Guide, used to create alert limits based on a statistical computation of multiple meas-
uring results from machinery in good running condition.
All of these alert options are available also in Condmaster Ruby, but as mentioned above, the new
Condition Manager replaces the former Criteria Guide.
The Condition Manager enables users to experiment freely in order to find the optimal alert setup for
any given application. This “learning phase” can continue until the criteria is saved. When it is saved,
the criteria is activated and Condmaster starts to evaluate measuring results according to the criteria
setup. If at some later time it turns out the alert settings yield unsatisfactory results, you can always
go back and edit the criteria.
- 259 -
10. EVAM Evaluation
10.5.2 What is a criteria?
A criteria is based on a specific, user selected set of measurement data. In order to obtain “rep-
resentative” baseline readings on which to base condition statistics, this selection should be com-
posed of readings from machinery in good running condition. The calculation of condition statistics is
automatically made by Condmaster , all you have to do is select a suitable set of readings to be
included.
Condmaster calculates the mean value and standard deviation obtained from the selected set of read-
ings. The readings should cover the whole range of normal operating conditions (speed, load, tem-
perature, etc.) that affect the machine’s vibration behaviour, because you will get a ”bad condition”
indication whenever a reading falls outside of the normal range, and this can either be due to abnor-
mal machine vibration or too narrow a base.
Criterias are used to define alert limits based on running and/or operating condition. This is also
known as flexible condition evaluation, meaning that current operating conditions determine whether
or not a measurement value merits an yellow alert (yellow condition) or red alert (red condition). A
high vibration reading taken under certain operating conditions may not necessarily mean the same
as an identical result when operating conditions are different. Because it allows the setup of variable
evaluation schemes, flexible condition evaluation is useful for applications such as wind turbines or
extruders, which run under variable operating conditions.
The result of criteria calculation is a non-dimensional COND no. (condition number) for each con-
dition parameter (VEL, ACC, DISP, Crest etc.) and symptom (unbalance, BPFO, gear mesh etc.).
COND no. = 0 (zero) represents the mean value of the readings selected. Criterias are handled indi-
vidually for each symptom and therefore can provide more precise alert limits for every symptom.
Selection of measuring results to include in the calculation of criteria is done using click-and-drag dir-
ectly in various graphs.
- 260 -
10. EVAM Evaluation
10.5.3 Criteria Guide vs. Condition Manager

The difference between the Criteria Guide in Condmaster Nova 2008 (and older versions) and the
Condition Manager is significant.
In previous Condmaster versions, criteria calculation was made on the measuring point level, mean-
ing all measuring results from the selected time period(s) were included in the computation. The user
had no means of selecting a representative “subset” of readings on individual assignments, condition
parameters or symptoms for inclusion in criteria calculation. The result was a “stairlike” evaluation of
measuring results, where the same value might result in different condition evaluation depending on
load, for example:
Example: A particular measuring result, measured under “moderate” conditions, might evaluate to yellow condition. Depend-
ing on the influence of load, the same value measured under “heavy” conditions might evaluate to green.
In comparison, the Condition Manager gives the user full flexibility in terms of what to include in cri-
teria calculation. Individual measuring results, condition parameters and/or symptoms can be easily
selected from graphs and the result is an immediate graphical presentation. The Condition Manager
yields a smoother “evaluation curve”:
- 261 -
10. EVAM Evaluation
10.6 Creating and editing criteria

The Condition Manager is accessed via Maintenance > Condition Manager in the Maintance rib-
bon tab or from the right panel menu, or via the Alert limit guide in the Measuring Point data
form. The main Condition Manager window lists all existing criteria:
1. Click the NEW button (A), or mark an existing criteria and click EDIT (B).
2. The Condition Manager displays the Measuring Point tree. Select a measuring assignment on
which to base the criteria. Note that only one measuring assignment can be selected here; how-
ever, in the final step of the guide, more measuring results from the same and other meas-
uring assignments can be added for the sake of improving statistics.
3. Select a Criteria type. Criteria may be one of two types:
l Static criteria means that alert limits will remain the same regardless of operating con-
dition. For static criteria, the result of the statistical computation is a normal distribution
graph (also known as a bell curve; turn the page for an example), which is a bar graph
summarizing groups of measuring results representing the amount of variation in the
readings. It visually represents the amount of variation in your selection of measuring
results and allows you to see how many readings fall within a certain range. It will help
you determine whether a particular reading fits into the bigger picture.
l Criteria type RPM (or a process parameter in Intellinova) means alert limits will vary
with operating condition, i.e. the present value of its controlling parameter (power,
speed, flow, pressure etc.). Selecting a process parameter results in a combined graph,
with symptom units on the Y axis and RPM or process parameters on the X axis.
4. Now select what alert limits are to be included in the criteria.
5. Select an alert limit type:
l COND means the result is a COND value where 0 represents the average of all meas-
uring results included in the criteria. Alert limits will be fixed to +21 for yellow upper
alerts and +35 for red upper alerts. The lower limits will be fixed to -21 for yellow alerts
and -35 for red alerts.
l Symptom value represents the actual value of the alert limit, e.g. 1.22 mm/sec for
upper alert.
6. In the final step of the Criteria Manager, all measuring results belonging to the measuring
assignment are shown. This is where you should be careful to make a representative selection
of results to base your criteria on. Use click-and-drag in any of the graphs to select measuring
results, then click the MARK button in the upper left corner of the form.
7. To calculate the criteria, click the CALCULATE button.
Please see below for a description of the functionality in the graphs.
- 262 -
10. EVAM Evaluation
10.6.1 Distribution graph example

Below is an example of the final step of the Condition Manager. In the previous steps of the guide, the
following settings were made:
l Criteria type = Static

l Alert limits = Red upper alert, Yellow upper alert
l Alert limit type = Symptom value
As a result of selecting the Static criteria type, the graph is a distribution graph. In this example, a
number of measuring results have been selected by the user through a click-and-drag operation in
the lower graph. The selected measuring results are represented by the blue, rectangular area (A).
These results will be included in the statistical criteria computation, but the computation itself is yet
to be done.
1. In the lower graph, multiple “areas” of measuring results can be selected using click- and-
drag. For each selection of results, click the MARK button in the upper left corner of the win-
dow (B). The selection of readings then turns blue in both graphs.
2. To delete unwanted measuring results from the computation, click and drag, then click the
UNMARK button (C).
3. When you’re done selecting measuring results, click the CALCULATE button in the upper left
corner of the upper graph (D). Following this action, a green-yellow-red evaluation scale is
automatically displayed in both graphs (E, see inset), showing what readings are considered to
fall under “good operating condition”.
- 263 -
10. EVAM Evaluation
10.6.2 Combined graph example

Here is another example, this time with the following settings:
l Criteria type = RPM (process parameter)

l Alert limits = Red upper alert, Yellow upper alert
l Alert limit type = COND
Condition guide functions
Once the criteria calculation has been done, there are a number of practical functions to help you
work with the criteria:
l Zooming: Click-and-drag to mark an area in the graph(s), then click the ZOOM / ZOOM
BACK buttons (A).
l Adding more measuring results: click the ‘...’ button (B) to add measuring results from other
measuring assignments.
l Viewing single symptoms or condition parameters: Tick the checkboxes for symptoms or con-
dition parameters (C) to view them individually.
l Calculate criteria for individual symptoms or condition parameters: Tick the checkboxes for
symptoms or condition parameters (C), then click CALCULATE (D). Use Calculate all symp-
toms on the ‘...’ popup menu (E) to include all of them.
l Viewing comments: Click the small squares at the bottom of the graphs (F) to display com-
ments made on the measuring point (if any).
l Moving alert limits manually: position the cursor on any of the green, yellow or red squares
(G). The cursor turns into a two-way arrow and the alert limit can be moved up or down.
- 264 -
10. EVAM Evaluation
10.7 Display of evaluated EVAM results
l Latest results shown in Graphical Overview on measuring point level (A)

l Any result (C) in Graphic Evaluation (B) when clicking on a dot
The COND nos. for EVAM parameters are displayed with colour coding in several places:
l for the latest measuring result in the Graphical Overview at the assignment level. Click all the
way down to see each active condition and symptom parameter as a staple against a green -
yellow - red background.
l for the selected range of measuring results in the Graphic evaluation, with green - yellow - red
scales. You also get the colour code on the dots on your folders.
l for the measuring result you click on in the Graphic evaluation, as a list of parameter values
plus COND nos. highlighted in green, yellow, or red.
This gives you a very fast and efficient tool for evaluating machine vibration. However, you must
learn how to read the COND number displays correctly and judge them against the data set on which
you have based your criterion. The following pages give you examples.
- 265 -
10. EVAM Evaluation
10.8 Criteria with different selection conditions
Same data, different selection:

l High value (A) excluded: lower mean value (B), narrow spread (C)
l High value (A) included: higher mean value (D), large spread (E)
One set of data, recorded ”as fast as possible”, form the base of two different criteria, here called Y
and Z. Criterion Y excludes the first high VEL value (A). The remaining values are all close to 0.4
mm/s. The mean value corresponding to ”COND no. = 0” is 0.39 mm/s (B). The spread of the
included values (C) is very narrow, which makes the standard deviation small.
The selection for criterion Z includes all measuring results, even the high value (A). The resulting
mean value (D) is 1.13 mm/s. The spread of the included values (E) is much wider, which makes the
standard deviation large.
The figures are taken from Graphic Evaluation. The spread indication (green) and the red lines mark-
ing the mean values have been added.
- 266 -
10. EVAM Evaluation
10.9 The effect on COND numbers
Evaluation Y and Z: A narrow data spread produces high changes in COND nos. for moderate deviations from the mean value.
The effect of different criteria on individual COND numbers can be dramatic. The diagrams above are
all based on the same facts. The lowest diagram shows straight measuring results for the condition
parameter VEL, in mm/s RMS.
Diagram Y is produced with the criterion Y that does not include the first high value and thus has a nar-
row spread. Consequently, the COND no. for this first value goes right over the top (COND = 60 is the
largest possible value, meaning ”out of range”). Judged with criterion Z, the same value is still in the
yellow zone.
Another interesting part of these diagrams are the differences in evaluation at points A, B, and C.
There is a noticeable increase in the raw value at (A), which is almost invisible at (B) and exaggerated
at (C). In fact, VEL at this point has increased from 0.27 (previous reading) to 1.34 mm/s RMS or 5
times. It is four times higher than the mean value for COND = 0, using criterion Z. This is quite a big
change, especially considering that the first value in the batch, 10.47 mm/s, is almost certainly a
measuring fault.
Another important fact is that, although there are differences when examined point by point, the gen-
eral shape of the diagrams and thus the trends are clearly the same: vibration severity is low and
stable. The conclusion from this is:
l you have to think and check before making a criterion
l you must not overreact to individual high COND nos. but check the trend and the raw values.
- 267 -
10. EVAM Evaluation
10.10 Measuring result list in graphs
Evaluation, criterion Z: Click on a point to see parameter values.
The fastest way of checking a ”suspect” measurement is to click on the point in a graph. This opens a
list of all parameter values and the corresponding COND nos. It does not matter which parameter dia-
gram you use, the list is always complete.
As said before, the VEL graph is most relevant for judging machine condition, so it should be the first
choice.
- 268 -
10. EVAM Evaluation
10.11 Display of COND no. and raw value
In the Graphic Evaluation, you can easily copy a diagram by holding down the CTRL key while you
click on the title (A). Then drag the title to the space beneath the original diagram, thus doubling it on
the screen. SHIFT+F4 alternates between a COND no. diagram and a raw value diagram. The first has
COND at the top left (B) and colored scales. The second has the measuring unit, if any, at the top (C)
and gray scales. Thus you can place raw values beneath each COND diagram. You can do that once
for a batch of diagrams and save these settings as a sequence for later recall.
This and the following example have all been produced in that manner. The following additions have
been made in the figures:
l The mean value used by the criterion (displayed in the function Spectrum) has been written
at the top left (D) and drawn across the measurements (E). The first value, not included in Cri-
terion Y, is shown in a different color. All examples use the criterion Y unless they compare the
results from Y and Z.
10.12 The Crest factor
When you make a criterion, the mean value and the standard deviation for each active condition para-
meter is calculated separately. Excluding a high VEL reading excludes the whole measurement, but
that is not likely to exclude a measurement with an exceptional CREST factor. For this, you have to
set a condition on CREST.
- 269 -
10. EVAM Evaluation
The CREST factor is the ratio between the RMS value and the peak value in a vibration velocity meas-
urement. The diagrams show, for example at (B) and (C), that a value below the mean value has the
same effect on the COND no. as a value above the mean. Thus, you have to compare COND no. and
raw value graphs (or go to the measuring result list) to see whether a change in COND no. is due to
an increase or a decrease of the raw value.
The CREST factor of a pure sine wave is 1.414, and normal values vary between 1.4 and 3. Transients
due to shocks can cause peaks far above the RMS value: they have high amplitudes but contain little
energy because they are of very short duration.
10.13 Kurtosis
CREST, KURT, and SKEW are non-dimensional. They are calculated directly from the time record dur-
ing vibration measurement. They all indicate the presence of transients in the vibration signal: tran-
sients which are due to shocks. In these examples, the measuring results are ”artificial”, produced by
knocking on the machine from different sides with a metallic object to produce shocks.
KURT describes how the vibration signal is grouped around its mean value. A pure sine wave has
KURT = -1.5. The more transients in the signal and the higher their amplitude, the higher the kurtosis
value.
10.14 Skewness
- 270 -
10. EVAM Evaluation
SKEW describes the symmetry of the signal grouping around its mean value. If symmetry is perfect,
SKEW = 0. The value goes from plus to minus depending in the direction of the transients in relation
to the measuring direction of the transducer.
Positive transients cause a positive value, negative transients cause a negative value. Here the values
change dramatically because the machine was hit from opposite sides with a metallic object during
measurement.
10.15 Unbalance
When you use symptoms in an assignment, their parameter values are evaluated by the criterion in
the same way as condition parameter values. The raw value is the RMS velocity value in mm/s from
all matching lines in the spectrum combined. The symptom ”Unbalance” has only one line, so here
you see a graph of that line’s amplitude. The raw symptom parameter value is 0 when that line is not
present in the spectrum. For symptoms with several lines and harmonics, the values can change a lot
with the number of matches found, especially when the overall vibration is low.
Note that the mean value here is very low. The only significant change in the COND no. (when we
ignore the first reading) is actually due to a drop of the parameter value.
10.16 Misalignment
- 271 -
10. EVAM Evaluation
Misalignment values have a large spread. The mean value is extremely low, which can explain the
variations: in a two line symptom, finding one or two matching lines can make a large difference.
The only significant increase in COND no. is due to an increase in the raw value.
10.17 Looseness
Again, we see a large spread and a very low mean value. The symptom consists of eight lines. The
two tops in the COND no. diagram have opposite causes: the first marks a decrease, the second an
increase in the measured value.
10.18 VEL, CREST and KURT
- 272 -
10. EVAM Evaluation
The diagrams above compare the curves for VEL (COND no. plus raw values), CREST and KURT. In
both cases where VEL went up, the shock indicators went down. Thus, there was a true increase in
vibration severity at (A), reflecting the greater vibration energy and not due to transient shocks.
10.19 Checking the spectrum
A right click on the measuring result in Graphic Evaluation opens a menu from where you can jump
directly to Spectrum.
This is the spectrum for the measurement discussed on the previous pages, scaled 0 to 20 mm/s. You
see almost nothing because the measured vibration is very low.
Scale downwards or click anywhere in the spectrum window and mark Logarithmic Y-scale to get a
better view.
- 273 -
10. EVAM Evaluation
10.20 Spectrum with logarithmic Y-scale
The magnified spectrum shows no line above≈1 mm/s and confirms the conclusion drawn from the
overall low RMS values: there is nothing alarming about the vibration measurement.
Note that peak values have little influence on the spectrum when they are due to transients.
- 274 -
11. Comments
11. Comments
11.1 Working with comments
Condmaster contains a register of Standard Comments. These are templates for comments which you
can attach to a component or a measuring point and a time, to mark and explain e.g. an important
measuring result or some other event you want to remember. These comments turn up as coloured
squares beneath the diagrams in Graphic Evaluation. The report Comments, Statistics found under
Graphical Overview >Comments > Printout prints all comments in your database together with
their frequency of occurrence. You can use this report as statistics for bearing failures and other
machine faults.
A standard comment has a code and name (A). These become part of the comment when you use it,
together with measuring point/component number, date and time, and an explanatory text
(optional).
The buttons NEW (B), EDIT (C), and COPY (D, duplicate marked standard comment, edit and save
under new code/name) all lead to the edit form, see "11.2 New and Edit comments" on the next page.
DELETE (E) removes the marked standard comment unless it is still used somewhere (old comments
can be removed when making a safety copy).
For the A30/T30 and the Leonova instruments, the user can select what comments should be down-
loaded to the instrument and the order in which to show them (F). (For the A30/T30, there is a max-
imum limit of 16 standard comments to be selected for downloading.) Every time you download a
round, these standard comments automatically go with it.
The “...” buttons (G) are used for assigning default text to the standard Bump test, Run up/Coast
down, FRF, Shaft Center Line, and Highlight measuring point comments.
- 275 -
11. Comments
11.2 New and Edit comments
Create/edit standard comment:

l Input/edit code and name (A).
l If required, select Alert priority (B) to generate an alert via the comment with the selected
priority.
l Select color for graphics (C).
A standard comment is input or changed on the edit form. Input the code (max. four characters) and
the name (A). Click on a color (C) to select the color of the comment square in Graphic Evaluation.
The selected field is marked FG (foreground). BG (background) is always on black and has no prac-
tical effect. Black becomes the foreground colour when you click on it.
A comment attached to a measuring point or component forces the item(s) onto the alert list when
aAlert priority (B) is selected for the standard comment.
- 276 -
11. Comments
11.3 Voice comments for the Leonova instruments
With the Leonova Diamond and Leonova Emerald instruments, comments to measurements can be
voice recorded (in .WAV format).
When a measuring point has a voice comment, you can listen to it in Condmaster. Go to Comments
(Graphical Overview > Comments) and click the Sound comment button (A).
From the Graphics window, voice comments are accessed via right click > Comments.
- 277 -
11. Comments
11.4 Download comments to instrument
Select standard comment for downloading:

l Click on Comments to T/A30 or Leonova (A).
l Click on a comment to select it (B).
l Use MOVE UP/MOVE DOWN to set the order (C).
l Finish with SAVE.
For the Leonova instruments, you can select which comments should be downloaded to the instru-
ment and in which order to show them. Go to Registers > Standard comments and click Com-
ments to Leonova instruments (A), click on a comment to select it (B). Use MOVE UP/MOVE
DOWN buttons to set the order in which to show the comments (C). Finish with SAVE.
For the T30 and A30 data loggers, the following instructions apply:
Up to 16 standard comments can be selected for downloading to the data logger. Downloading is auto-
matic every time you download a measuring round.
After taking a reading (any measuring technique) you have the option to set a comment. It will be
uploaded to the comment register and appear in the Graphic evaluation. You can then add your own
text to it.
It is recommended to select standard comments which contain information that is relevant for the
condition of the machines and their environment but not apparent from the measuring results, for
example the comments listed above (D).
- 278 -
11. Comments
11.5 Set a comment in the Graphic Evaluation
l Right click on the small white area just below a diagram (A).
l Click Add comment (B), select standard comment (C, D), add text and attachments (E, F)
(optional).
In Graphic Evaluation, right hand click in the small white area directly below a diagram to add a
comment (A). First zoom in on the spot to get date and time right. Select Add new comment (B).
This opens the comment data window. Click the ‘...’ button by Standard comment (C) to open the
standard comment register, mark a comment and click OK to select (D). Adding additional text (E)
and Attachments (F) is optional. Finish by clicking SAVE.
- 279 -
11. Comments
11.6 Comment with additional text
Comment data:
l Select measuring point or component number (A).
l Click “...” (B) and select standard comment.
l Add text (C) to the selected comment (optional).
l Click NEW under Attachments to attach a file (D, optional).
An uploaded comment has the date and time when you set it in the instrument, and is always
attached to a specific measuring point. When adding a comment in Graphic Evaluation, it can be
connected to either a measuring point or to the whole component; select with the dropdown button
(A) by Measuring point/Component in the comment data form. A component comment is shown
under each measuring technique diagram of all measuring points belonging to the component.
In the field for Standard comment (B), you can select a standard comment from the standard com-
ments register (see "11.5 Set a comment in the Graphic Evaluation" on the previous page).
In the text field (C), you can enter a large amount of free text (optional).
Under Attachments, files (D) can be added to the comment (optional). A file is saved to the data-
base and can thus be viewed by all users with access to it. (The previous functionality with hyper-
linked documents is also supported, see 'Hyperlinks set up' in section 'Optional configuration settings'
in the Condmaster Installation and System Administration manual, document no. 72301).
- 280 -
11. Comments
11.7 Comments in the Graphic Evaluation
Display comment:
l Click on square to display comment (A)
l Right click to edit (B)
l Popup menu: Selecting Show > Comments places comments under the diagram (C)
Clicking on a comment square in the Graphic evaluation opens a hint with code, standard comment
name and comment text (A). Right click on a comment square to edit the comment (B). Right click
anywhere in the graph, select Show > Comments from the popup menu and the comments are
placed beneath the diagram (C). It stays visible and is printed together with the diagram.
To delete a comment, right click anywhere on a graph to open the popup menu. Select Comments,
mark the comment to remove, then click the recycle bin (D).
- 281 -
12. Graphics Functions

12.1 Graphics functions in Condmaster Ruby
Graphic Evaluation window
The function Graphic Evaluation features e.g. the following:

l Close interaction between measuring point tree structure and the display of diagrams.
l Using the right hand mouse button and keyboard commands to open sub functions and short-
cuts to registers, Lubmaster, spectrum display, etc.
l More options for mixing diagrams, tables with measuring result and comments plus texts in
printed reports. Standard texts and logotypes can be stored.
l Storage of display sequences including texts and tables, as well as of individual screen layouts.
l The display of trend curves consisting of a running average of a user defined number of meas-
uring results.
l The option of customizing the graphics display and printout by editing the drivers for screen
and printer.
- 282 -
12.2 Graphics default layout
Graphic Evaluation default layout
Open the Graphic Evaluation function either by clicking on the Graphics button from the ribbon
bar, or by selecting Graphical Overview > Graphics (or Maintenance > Graphic Evaluation) in the
right panel menu, or use the Graphics button from other places in Condmaster.
In the Graphic Evaluation default layout, tool windows are shown to the right (A), the diagram(s) for
a marked item are shown in the graphics field (B), and there is a toolbar at the top (C).
All tool windows are shown by default; Measuring Point Tree, Filters, Sequence, Machine Oper-
ating Conditions. Click the ‘...’ button in the top right corner above the tool windows (D) to open a
menu in which it is possible to select which tool windows to be displayed, and if the panel with tool
windows should be displayed or not (activate/deactivate Show Right Panel).
In the toolbar at the top (C), the button with number 3 is marked by default (E), meaning that three
diagrams are displayed in the graphics field. Click buttons 1-5, or select a number from the drop
down menu to display a different number of diagrams in the graphics field.
Clicking the ‘...’ button in the toolbar (F) opens a menu in which more alternatives are available for
the graphics field. See ahead for more information about tools and options for the graphics display.
- 283 -
12.3 Customizing the layout of tool windows
Customized layout of tool windows in Graphic Evaluation window:

l CTRL+mouse click and drag tool windows at desired drop sites (A, B)
l Save changes by clicking ‘Save form layout’ in the top menu (C)
Tool windows are the Measuring Point Tree, Filters, Sequence, and Machine Operating Condi-
tions windows which in the default layout resides to the right. To drag and drop the tool windows at
different drop sites, hold down the CTRL key, click the blue ‘drag icon’ (A), then drag and drop the
tool window at a desired drop site (B). The large middle area is reserved for the different diagrams.
Resize windows by hovering the mouse pointer at the border of a window, and when the mouse
pointer changes to a left-right arrow, click and drag to a desired size.
To save the layout, click the small red-yellow-green icon in the upper left corner of the Graphic eval-
uation window title bar (or right click anywhere at the Graphic evaluation window title bar) and select
Save form layout from the popup menu (C).
To revert the save form settings, select Reset form layout from this menu (C). Please note that the
window has to be reopened for the reset to take effect.
- 284 -
12.4 The display of diagrams
Change display of diagrams:

l Drag left to right on the time scale to zoom (B), zoom back with (C).
l Select number of diagrams to display (E).
A diagram title (A) consists of measuring point number and name plus measuring technique. The time
scale (B) is shown below the diagrams. The time intervals change with the length of the period
shown. The horizontal date and time shows the time at the cursor position. To zoom in on a period,
click on the time scale and drag from left to right. Use the back button (C) to zoom back. You can
grab the time scale bar (D) and move the scale (and the diagrams with it) forward or backward in
time.
The buttons 1-5 (E) in the toolbar at the top are used to select the default number of diagrams to dis-
play in the graphics field. Click buttons 1-5, or select a number from the drop down menu to display a
different number of diagrams in the graphics field. Use the scroll bar (F) to move up and down among
the diagrams, or the keyboard keys PAGE UP, PAGE DOWN, HOME, and END to browse through the
diagrams on the screen.
To move a diagram to a different position, grab the diagram title (G) and drag it to the lower border of
another diagram. Drop it beneath this diagram when the cursor changes to an arrow. If you hold
down CTRL when marking the title, you move a copy of the diagram. The original remains in place.
Clicking the ‘...’ button in the toolbar (H) opens a menu with different alternatives. As default, Grid is
set to ON, and it is also possible to activate Measuring protocol which produces an even spacing
between measuring results, independent of the time interval. Activating Spectrum or Image will dis-
play a small version of the belonging spectrum or image (if any) to the right of the diagram(s) in the
graphics field.
- 285 -
12.5 Selection of items for graphics display
Select data to display by using the Graphics button from various places in Condmaster to open
marked item(s) in the Graphic Evaluation window
When opening the Graphic Evaluation function without making a selection of what to open, ALL
measuring points in the database are loaded into the Graphic Evaluation window. Depending on the
amount of measuring points in combination with computer capacity, this could be a heavy operation
for the system. It might be more common to use the Graphics button from other places in Cond-
master to open marked items in the Graphic Evaluation function. The selected item(s) will open in the
graphics field and are also added to the Measuring Point Tree tool window.
To select items from the tree structure:
Right click between the graphs and select Insert from tree (A). This opens a new window in which it is
possible to select what to display (B). Selecting a folder will include all its sub folders. Press CTRL to
select several items on the same level from the same location (e. g. components from the same
folder) in any order (SHIFT for consecutive order), and click OK. The selected item(s) will open in the
graphics field and are also added to the Measuring Point Tree tool window.
Clear graphics field for a new selection:
Mark a graph in the graphics field and press the DELETE key. You can also right click on a graph and
select Delete from the popup menu. When you load a sequence (see ahead), the graphics field is
updated automatically.
See other sections for more information about filter functionality, sequences, etc.
- 286 -
12.6 Filtering parameters to be displayed in diagrams
Activate/deactivate parameters to display in the diagrams using the Filter functionality
In addition to selecting which measuring points and components to display (see "12.5 Selection of
items for graphics display" on the previous page), the Filter tool window (A) makes it possible to fil-
ter out which graphs to display. The categories in the Filter tool window are Alert, Alert limit, Evalu-
ation, Units, Techniques, and Condition Parameters and Symptoms, making it possible to
filter out graphs according to measuring technique(s), symptom(s), measuring points with or without
alerts, and much more. Each category has a number of parameters. As default, all parameters in each
category is ticked and therefore displayed in the graphics field. The numbers to the right of each para-
meter shows how many graphs that are displayed in the current selection. The blue numbers to the
right of the text Filter shows how many graphs are currently displayed of the total number of graphs
available.
For example, to filter out assignments with the HD ENV technique, first untick the box next to Tech-
niques to deactivate all techniques, then tick the boxes with an HD ENV icon (B). When activating or
deactivating a parameter or category in the Filter tool window, the Graphics field and the Measuring
Point Tree window are updated with the new selection automatically.
NOTE: In the filter functionality, there is an “AND” operator between each category, meaning that
each category needs at least one parameter to be ticked, otherwise the graphics field will be empty.
For the parameter RPM in the category Techniques, it is possible to make a selection of an RPM
interval to display. Click the ‘...’ button by the RPM parameter (C), enter a range and click OK (D).
Using an exclamation mark (“!”) before the interval (for example “!12-500”) excludes the entered
interval. To show the whole RPM interval again, delete the numbers in this window (D) and click OK.
- 287 -
12.7 Sequences of graphics data
Save and load sequences of graphics data
Opening a sequence from the Graphical Overview
In the Sequence tool window to the right (A), you are able to save and load sequences of graphs. A
sequence contains (1) the selection of items for graphics display (2) any filters applied to that data.
To save a new sequence, click the ‘+’ button (B), input a name and click OK in the window that
appears (C). The sequence is saved in its present (edited) state. Saved sequences are listed in the
Sequence tool window.
To load a saved sequence, double click its name in the Sequence tool window. A blue marker to the
right of the sequence means that it is loaded. The ‘...’ button to the left of each sequence (D) opens a
menu in which it is possible to load, save, rename or delete it.
To open a sequence from the Graphical Overview, click the Sequence icon in the ribbon bar (E), then
select a saved sequence to load from the window that opens.
- 288 -
12.8 Machine operating conditions tool window
In the Machine operating conditions tool window to the right (A), you are able to view graphs related
to machine operating conditions such as power, pressure, flow, etc. for vibration measurement
assignments measured with Intellinova.
Machine operating conditions are created by the user under Register > Machine Operating Condi-
tions, then associated with a measured value (either as a global value or as a user defined measuring
assignment). See section "15.13 Machine operating conditions" on page 341 for information about
how a machine operating condition is set up.
Clicking the “...” button next to a condition opens the window (B) in which graphical filters can be set
if Predefined intervals have been set up in the Machine operating conditions register (see "15.14
Setting graphical filters for machine operating conditions" on page 344). Select an interval from the
dropdown list and click close. Readings falling into the selected interval (C) will be displayed in the
graphics; all others will be left out. (‘None’ means no filter - all data is shown.)
- 289 -
12.9 Save case tool window
In the Saved Cases tool window to the right, you can load a saved case, i.e. a certain event in a
single graph, for example a bearing fault, a bearing replacement, imbalance, etc.
For more information, see "Saved Cases" on page 434.
- 290 -
12.10 Show and hide graphs
The number of graphs shown in the graphics field can increase quickly, and all of them might not be
relevant for display depending on situation (e.g. certain types of bearing symptoms, etc). The
Show/ Hide graphs functionality makes it possible to exclude (and include) graphs for display.
Graphs are hidden individually, but filters can easily be used to hide groups of graphs (see below).
The fastest way to hide a single graph is to right click it and select Hide graph (A) in the popup
menu. Another way is to use Show/Hide Graphs (B) in the toolbar ‘...’ button menu. If this altern-
ative is activated, an icon appears in the top of each graph (C), and if clicked, a question ‘Hide graph?’
is shown (D). It is also possible to mark several graphs (SHIFT+Mouse) and show/hide them at the
same by clicking SPACE on the keyboard. A very useful feature for hiding a whole group of graphs is
to first use the filter functionality to filter out all e.g. BPFO symptoms, and then hide all these by mark-
ing all (CTRL+A) and then click SPACE.
When opening Graphic evaluation, graphs that have been hidden are not shown. Clicking the button
SHOW HIDDEN GRAPHS (E) shows hidden graphs in grey colour (F).
If an alert occurs on a hidden graph, it will always be shown (in grey) in the graphics field.
- 291 -
12.11 Y-scale settings
The Y-scale start up settings alternative is found either under Properties in the Graphics popup
menu (A), or whenever changing the Y-scale in a graph via clicking the SAVE button (A). In the new
window that opens (B), it is possible to change the Y-scale start up values for the current graph. You
may enter your own Y-scale settings, or select Calculated Y-scale (which corresponds to the
default value) (C). Click OK to save.
It is also possible to apply the start up values to other graphs: tick the Connect settings box (D),
then click ADD (E) to select which graphs to apply the startup value (s) to. The From Selected
alternative lists matching graphs from the current data selection, while the From all alternative
lists all matching graphs in the database. A click on either of these alternatives opens up a new win-
dow in which graphs can be selected by using Mark/Unmark, then OK (F). The selected graphs will
be listed under the Connect settings box, click OK to save the settings.
Reset the settings by selecting Calculated Y-scale, and click OK.
- 292 -
12.12 Elements of a diagram
l Scales (A), alert limits (B, C), measurements (D).

l Hints: results (E, click on point), comment (F, click on square).
The diagram has a scale on the left hand side (A), and in some cases also on the right hand side. For
evaluated measuring results, the scales are colored green - yellow - red. For raw values, they are
gray. When you grab either scale anywhere below the dividing line at the top, the cursor turns into a
vertical double arrow and you can move the scale up or down (affects the active diagram plus its cop-
ies, if any).
Upper alert limits (B) are shown as solid, lower alert limits (C) as broken lines. In case of shock pulse
readings with variable speed, the alert limits for speed dependent values follow the machine speed,
else the lines are straight.
Measuring results, here LR (blue) and HR (red), are represented as dots (D), connected by thin grey
lines.
When you click on a measuring result dot, you get a box (E) showing measuring time and results.
Comments are shown as colored squares at the bottom of the diagram. Clicking on a square opens
the comment box (F).
Moving the mouse while holding down the right hand button produces cross hairs (G).
- 293 -
12.13 Display of moving average
l Right click in a diagram for popup menu (B).

l Select Show > Curve and/or Moving average (D).
The top of the scale (A) can be grabbed. The cursor turns into a horizontal double arrow and you can
expend or reduce the diagrams sideways within the diagram field (affects the whole display and is
saved).
Right clicking (without moving the mouse) anywhere in a diagram opens a popup menu (B), allowing
you to print the active diagram or copy it to the clipboard. Its lower part (C) contains shortcuts to func-
tions such as Measuring point data, Comments, Measuring results (all points), Compare spec-
trum, Waterfall diagram and Colored Spectrum Overview, each for the active diagram.
Select Show to obtain a menu (D) that allows you to manipulate the active diagram.
The upper diagram (E) shows the measuring results as CURVE ( Curve is marked on this menu,
everything else is off). When you unmark Curve as well, you get no diagram. The middle diagram (F)
is a copy of the one above. Curve is off and Moving average, 5 results is on.
The lower diagram (G) is obtained by activating both Curve and Moving average, 5 results. You
can produce the same effect with only Curve on by pressing F5 (for 5 results average) or F6 (for 10
results average). This toggles the average display on and off, for all marked diagrams. Settings made
under Show can be saved with a sequence.
- 294 -
12.14 Combining diagrams
In Graphic Evaluation, you can combine up to 10 diagrams. The possibility to combine diagrams is
useful to compare trends and relationships between various parameters. You can, for example, com-
pare
l different measurement assignments for the same measuring point, e.g., trends for velocity,
HD ENV, temperature, and process parameters (such as pressure, flow, production rate, etc.)
from an OPC source
l similar measurement assignments for different measuring points, e.g., three different velocity
trends.
To place a diagram inside another diagram:
Grab a diagram title (A) and drag it to the right-hand scale of the other diagram (B). Drop it
when the cursor turns into an arrow. (If you hold down CTRL while grabbing the diagram, you move a
copy.)
- 295 -
When two diagrams have been combined, the appearance changes. One line is marked with bigger
result squares (C) while the other line is shown in a different color, and both the left-hand and
right-hand Y-scale represents the marked line (D).
When a third line is added to the diagram, the result looks like this:
Click one of the result dots to change marked line. Note that both the left-hand and right-hand Y-
scale also changes when another line is marked.
To detach or delete one of the lines, right-click the right-hand Y-scale and select Detach or Delete
selected line. Detach selected line means that the diagram is placed directly below the combined
diagram. Delete selected line means that the diagram is deleted from the combined diagram and
deleted from the Graphic Evaluation window, but it will appear again after restarting Graphic Evalu-
ation.
To change the scale, right click and select Properties. See "12.11 Y-scale settings" on page 292 for
details.
- 296 -
Note! For HDm/HDc, LR/HR HD and LUB/COND for LR/HR HD, the left-hand Y-scale represents
one of the lines (for example HDm) (E), and the right-hand Y-scale represents the other line (HDc)
(F).
The title of one of the lines is also written against the right-hand scale. To extract one of these lines,
grab its title and drag it to any space above, below, or between the other diagrams. Drop it when the
cursor turns into an arrow.
Saving combinations of diagrams as a sequence

It is possible to save your combinations of diagrams as a sequence, see "12.7 Sequences of graphics
data" on page 288 for details.
Change line size and color

It is possible to change the default size for selected and other lines, as well as the default colors for
the lines. When combining lines in a diagram, the color of the line is decided depending on the order
in which it is added; the first line is always blue, the second is grey, etc.
To change size and/or color:
1. Click Settings (A) under the ‘…’ button menu in the toolbar.
2. In the Properties window and the Drivers tab, select COPY (B) to open the driver data.
- 297 -
3. At the top of the Driver Data form, Name (C) the new driver. Modifications are saved under a
new driver name.
4. Modify the properties for Multi graphs (D) as requested.
5. Select SAVE (E).
6. Go to the Devices tab (F), select the new driver as default for Screen (G) and click OK (H) in
order to apply the changes.
To learn more, see "12.21 Drivers for screen and printer" on page 305.
- 298 -
12.15 Comment and measuring result tables
l Activate Comments and Results (A) under the Show menu.

l Extended/shorten tables by grabbing their lower borders (B).
In the Show menu, you can activate Comments and/or Results (A).
Both comments and measuring results are listed for the displayed time span, starting with the latest
reading/comment shown on the left hand side of the diagram.
The lists can be extended/shortened by grabbing its lower border (B) and pulling down-
wards/upwards when the cursor turns into a double vertical arrow.
When only Curve is marked, the Comments table can be toggled on/off with SHIFT+F2, the Results
table with SHIFT+F3. This is valid for all marked diagrams.
- 299 -
12.16 Editing and adding comments
Edit/add comments:
l Right click on the comment line below the diagram (A).
l Click Add new comment, select a standard comment (B), add text.
l Right click on an existing comment to edit it (C).
A right click on the space where the colored squares representing comments are placed (A) allows a
shortcut to the comment register where you can add a new comment (B).
A right hand click on a colored square provides the opportunity to edit the active comment (D).
- 300 -
12.17 Printing diagrams
Print diagram:
l Print marked diagram from popup menu (A).
l Print any diagram using the Print option from the ‘...’ button menu in the toolbar (B).
There are two ways of doing a printout. In the popup menu, you can select Print to print the active
diagram (A).
To print one or more diagrams, select Print in the ‘...’ button menu in the toolbar (B).
The Print command allows you to select a connected printer and also shows the active printer driver
(C). Clicking on a line opens a selection. You can print all diagrams, selected diagrams, or the active
diagram (D).
The choice X-scale with each diagram Yes/No (E) has the following effect: Yes means that the
time scale is printed below each individual diagram. No means that the time scale is printed once at
the bottom of each page.
- 301 -
12.18 Popup menus for alert, COND and Spectrum
l SHIFT+F4 toggles between raw value and COND no. (C, D).
l Right-click for Show and shortcuts.
Graphs for measuring techniques on the alert list have an alert icon next to the title (A). A click on the
icon opens the alert list. Right-clicking the icon opens the function Delete alert (B).
For measuring points with COND number calculation (see " 10.5 The Condition Manager " on
page 259), the Show menu allows you to display a parameter as its COND no. diagram (C) with
colored scales, or as a diagram of the raw values (D). The third diagram in this example is a copy of
the second. For the third diagram, COND on the Show menu is marked (E), for the second it is not
marked. If COND is not marked, you can toggle it on/off with SHIFT + F4, for all marked diagrams.
For most measuring techniques, there are shortcuts to Compare spectrum, Waterfall diagram
and other functions (F).
A right-click on a measuring result allows a shortcut straight to Spectrum (G) which opens in a new
window. There is a tight connection between graphs and spectrum, a click on a dot in a graph imme-
diately update the spectrum.
Please note: When opening Graphic Evaluation, Condmaster reads the measuring results and cal-
culates the parameters, which can take a noticeable time. An immobile alert icon shows that the pro-
cessor is still busy with calculations, which causes small delays in screen updates. A moving alert icon
shows that the calculations are finished.
- 302 -
12.19 Zoom Properties
Zoom properties:
l Right click on the time scale to select (A).
l Use Properties (B) to edit.
Right clicking on the time scale produces a list of available zoom scales (A). These can also be activ-
ated by pressing CTRL+1 to max. CTRL+9. You can have more than 9 zoom scales, but the additional
scales can only be selected by marking them on the drop-down list.
To edit zoom scales, select Properties (B). This opens the Zoom properties window (C). To edit,
click ”...” (D) for an item on the list. With the button NEW (E) you can add items.
A zoom scale is defined by a name and a time interval in days (F). Any of the zoom scales can be used
as the default setting for the standard zoom when you open diagrams.
From current time and backwards means that the time scale starts with the present date and
time, else it starts with the date and time of the most recent measuring result.
To provide a fast graphics display, Condmaster starts showing diagrams after approx. two seconds.
The program then gets the remaining measuring results, if any, and adds more diagrams until all
selected diagrams are available. This can affect the zoom range in case results read later in the pro-
cess span over a longer time. When Automatic zoom range extension is on, the zoom range is
automatically adjusted to accommodate all measuring results, i. e. you can click on the back button
to extend the range presently shown.
- 303 -
12.20 Editing alert limits
In Graphic Evaluation you can edit set alert limits:
1. Click and drag the grey circle in a graph up or down (A). When the mouse button is released,
the Alert limit guide will open.
2. Confirm the new value (B) in the Alert limit guide. For more information about alert limits,
see "9.7 Flexible alert limits" on page 182.
NOTE : This function is available for most alert limits, but not for variable alert limits, COND,
dBm/dBc, LR/HR, RPM, and TLT (the grey circles are not present in these graphs).
- 304 -
12.21 Drivers for screen and printer
l Click Settings (A) under the ‘...’ button menu in the toolbar to open the driver menu (B).
l Click COPY (C) to edit the driver data (D).
The option Settings (A) found when pressing the '...' button above the graphics field opens a Prop-
erties window with three functions:
l Modification of the drivers for screen and printers
l Selection of the drivers for screen and printers
l Creation of a new running average curve.
The function selection is made by clicking on one of the tabs (E).
Marking a driver (B) and clicking the button COPY (C) opens the driver data (D). Modifications are
saved under a new driver name. The new driver can the be linked with the screen or a printer, see
ahead.
- 305 -
12.22 Logotype on screen and printouts
New driver:
l Mark a standard driver and click COPY (A). Name (B) and edit the driver data.
l Select Devices (F) to save and activate.
One example of modified drivers is the display and printout of a company logotype together with dia-
grams. For this, you must first make a copy of the standard driver. Mark e. g. 1 Standard screen and
click the COPY button (A).
In the driver data menu, input the name of the new driver (B), e. g. 4. Logo screen. When the logo-
type is in the Condmaster directory (in .BMP format), input the file name (C), else input path and file
name.
Next, define the width and height (D) of the logotype as shown on the screen, keeping the pro-
portions of the picture. You can use 1 decimal.
Top diagram margin (E) must be set to a value greater than the height of the logotype, else the top
diagram will cover part of the logotype.
The modified driver is saved and selected as the screen driver under Devices (F), see "12.23 Con-
necting drivers with screen and printers" on the next page. To get the logotype on the printouts, you
have to repeat this procedure for one or more of the printer drivers.
Driver copies can be opened for editing by double clicking on their names.
- 306 -
12.23 Connecting drivers with screen and printers
Select driver:
l Click on ”...” for the active driver (A) on the Properties menu.
l Select a driver from the list (B), click OK.
The program contains three standard drivers, for the screen, a black and white printer, and a color
printer. In addition, you can save your own modified versions (see previous page).
The Properties menu lists the display and printers connected to your PC or work station and their act-
ive drivers. To select a different driver, click on ”...” (A), mark it on the list (B) and click OK.
- 307 -
13. Lubmaster
13. Lubmaster
13.1 Lubmaster
l Evaluation graph (A) for bearing condition.

l Life time graph (B) for optimizing the lubricant.
LUBMASTER is based on three sources:
1. SPM’s algorithms for bearing condition evaluation, using the LR/HR method.
2. The formulas recommended by ISO 281 for rating life calculation.
3. The formulas used by lubricant and bearing manufacturers to calculate life adjustment factors
which quantify the effect of lubricant type, viscosity, load, and temperature on bearing life.
LUBMASTER works with the Condmaster Ruby bearing catalogue data (bearing type, size, and load
rating) for bearings with standardized dimensions according to ISO 15, ISO 355, and ISO 104. Spe-
cifically, LUBMASTER can be used for:
1. Training - the graphic display of the SPM evaluation graph clearly shows the relationship of
shock values and condition codes.
2. Calibrating SPM measuring points - by comparing calculated LR/HR values with the measured
results, one can determine a calibration constant (COMP no.) for each individual bearing applic-
ation.
3. Assessing alert limits - the display shows the dynamic range of LR/HR readings, LUB and COND
numbers.
4. Optimizing lubrication conditions - by changing lubrication data (e.g. lubricant type, viscosity),
one can simulate the effect such changes would have on bearing life expectancy.
For this, you have two LUBMASTER functions, the evaluation graph (A) and the life time graph (B).
- 308 -
13. Lubmaster
13.2 The evaluation graph
l Bearing data and graphical display of evalution results.
The evaluation graph shows the green-yellow-red condition zones and the bearing symbol (A). The
shape of the graph and its position relative the HR scale (B) varies with bearing type, size, and rpm.
In a correct shock pulse reading, the LR value is always higher than the HR value. The difference
between LR and HR is called delta, shown on the vertical scale (C). The COND no. scale (D) is con-
stant, 20 to 65.
The bearing symbol can be moved with the cursor. The LR/HR values (E) corresponding to its position
will be shown, as well as the resulting condition codes (F). The coloured fields of the graph and the
corresponding CODE nos. represent:
l CODE = A Good condition (green)
l CODE = B Dry running (yellow, low delta)
l CODE = C Caution - beginning damage (yellow, high delta)
l CODE = D Bearing damage
With CODE A and B, the condition data field contains a LUB no. describing lubrication condition. With
CODE B, C, and D you get a COND no. indicating the degree of surface stress and damage. These
CODES are valid provided the signal comes from the bearing and not from a disturbance source in the
machine.
When the bearing symbol is moved below the evaluation graph (HR larger than LR), you get error
code E2 = “Disturbance”. This means that such a reading cannot originate from a rolling element bear-
ing.
When the bearing symbol is moved to the left of the evaluation graph, you get the error code E3 =
“Signal too low”.
- 309 -
13. Lubmaster
13.3 Bearing condition development
l Bearing condition development from good to bad.
Bad bearing condition can be caused by poor lubrication. When the bearing is running dry, the overall
shock pulse value increases while the delta value (the difference between LR and HR) stays low (A).
The LUB no. indicates the thickness of the oil film in the rolling interface. LUB no. = 0 means dry run-
ning condition. The interpretation of LUB nos. between 1 and 4 depends on the bearing type. For ball
bearings, 1 to 2 means “boundary lubrication” and higher values “full lubrication”. For roller bearings,
1 to 4 means “boundary lubrication” and values above 4 “full lubrication”. Dry running eventually
leads to surface damage, so the CODE changes from A to B to D.
Surface damage normally causes a high delta value (B), and the CODE changes from A to C to D. The
COND no. (condition number) indicates the degree of surface stress and damage in the rolling inter-
face and should be interpreted as follows:
l COND no. below 30 = minor damage
l COND no. 30 to 40 = increasing damage
l COND no. above 40 = severe damage
- 310 -
13. Lubmaster
13.4 Measuring point calibration
COMP no. calculation:

l Click CALCULATE COMP (A).
l The COMP no. (B) is displayed.
l Click SAVE COMP (C).
To get an accurate evaluation of LR/HR readings, it is often necessary to calibrate the measuring
point. Get a shock pulse reading from the measuring point. Make sure that it is accurate and that
there is no disturbance. Save the reading in Condmaster Ruby and open LUBMASTER. When skip-
ping from the Graphical Overview, you automatically get the data for the marked measuring point,
including the latest measuring result. A good bearing should be in the centre of the green field, or
slightly right of the centre.
Go to the Lifetime graph and input the lubrication data. This is not absolutely necessary but
improves accuracy, see next page. Click UPDATE GRAPH and CALCULATE COMP (A). This displays
the COMP no. (B) and moves the bearing symbol unless COMP = 0. Accept positive COMP nos. by
clicking SAVE COMP (C). The COMP no. is now part of the basic bearing data and will be added to
each reading before it is evaluated.
Setting a COMP no. does not affect the measured LR/HR values or the dynamic range of the shock
pulse measurement. If bearing condition deteriorates, you get the same increase in the LR/HR values
with or without COMP no. The COMP no. simply helps you to avoid misleading error and condition
codes and makes it easier to follow bearing condition development.
Warning: Avoid using negative COMP nos. unless you know exactly what you are doing! For bearings
with high but stable readings, it is better to increase alert levels than using negative COMP nos.
- 311 -
13. Lubmaster
13.5 Lubrication data for COMP no. calculation
l Select lubricant, viscosity (A). Set FZG to 12 (HP additives) or to 7 (none).

l Enter load ratio (10%), bearing housing temperature (B).
l Click UPDATE GRAPH (C).
As a rule, you should calibrate after entering the lubrication data. You can do that when you create
the measuring point. You can use an approximate value for bearing load (≈10%), but the lubricant
data (1) and the bearing temperature (2), measured on the bearing housing under normal operating
conditions, should be accurate.
However, it is possible to obtain a COMP no. without entering lubrication data. LUBMASTER will then
give you a COMP no. based on the calculated HR value corresponding to Kappa = 1 (full lubrication).
The COMP no. thus received is “reasonably accurate” in the low speed range but tends to be too high
for bearings in the higher speed range, where you can expect Kappa values considerably greater than
1.
As a guide: Bearings in the low speed ranges, up to 500 rpm, tend to have Kappa values near or
below 1, even when they are properly lubricated. The speed is too low to build up an oil film which can
separate rolling elements and raceway. In the medium speed range, 500 to 3000 rpm, you can
expect Kappa values above 1 with the right lubricant viscosity. In the high speed range, above 3000
rpm, oil film thickness can drop again because the lubricant cannot flow back as fast as it is pressed
aside by the rolling elements, and also because higher temperature reduces oil viscosity.
- 312 -
13. Lubmaster
13.6 Calculation of alert limits
l From the position where COMP = 0, go right (up) and note the difference in LR/HR. Normal LR
range good to bad = 8-9 dB.
In the measuring point register, you can program alert limits for COND, LUB, LR and HR. With
LUBMASTER, you can easily find suitable limit values. Again, the results will be more accurate if you
input lubrication data (bearing load is not important in this context).
To find suitable alert limits for HR and LR, move the bearing symbol into a position where
CALCULATE COMP returns COMP no. = 0. Set LR = HR+4. The bearing symbol is now in the exact
“Good condition” position according to SPM evaluation rules. If you move the bearing symbol straight
up until it touches the red condition zone, the displayed LR value is a suitable LR alert limit.
Normally you receive COND no. 29 when passing the limit from CODE A to CODE C. This is a suitable
alert value for a yellow COND no. alert, giving a first warning of developing bearing damage. You can
use the LR value received on entering the red zone as a second damage alert.
Go back to the initial position, then straight to the right. The LUB no. will decrease as you come closer
to the yellow condition zone. Pick a suitable value for ”poor lubrication” alert, e.g. half the value of the
original LUB no.
You can use the HR value shown when CODE B comes up as limit for a ”dry running” alert.
- 313 -
13. Lubmaster
13.7 The lifetime graph
l Input lubricant data (A, B), load ratio in % (C), bearing housing temperature (D).
l Click UPDATE GRAPH (E).
The lifetime graph shows the relationship between the Kappa value (horizontal scale) and the bearing
life adjustment factor a23 (vertical scale). The Kappa value is a way of expressing relative oil film
thickness in the rolling interface. Calculations of the rated bearing life L10a, as given in the bearing
catalogues, presupposes “full oil film lubrication”, i.e. a Kappa value of at least 1, corresponding to a
life adjustment factor a23 of 1.
The life adjustment factor a23 is a function of Kappa and also of other lubricant qualities, such as the
additives used to prevent bearing damage. The range where additives affect the bearing life is
marked by a darker shade on the graph.
On the basis of the data input for lubricant, bearing load, and bearing temperature, LUBMASTER cal-
culates
l friction loss in Watt (Loss W)
l oil film viscosity at operating temperature (v = Greek ny)
l minimum viscosity for L10 life (v1)
l Kappa (v/v1)
l life adjustment factor (a23, depending on Kappa)
l approximate bearing life in hours (L10a h, depending on a23, load and FZG number).
The input of the lubrication data also affects the Evaluation graph. Without these data, LUBMASTER
assumes Kappa=1 when calculating a COMP no. With the lubrication data, the program uses the
actual Kappa value. Thus, you use the life time graph both for accurate calibration of the measuring
point and for finding the optimal lubricant for a given bearing.
- 314 -
13. Lubmaster
13.8 Selecting the optimal lubricant
Optimizing lubricant:
l Input bearing and lubrication data. Change oil type, viscosity (A).
l Watch the life time graph (B), L10ah (C).
l Example: ISO 6310, rpm = 1480, temp. = 80 °C, load = 7.4%.
The lifetime graph can be used to simulate different lubrication conditions for a given bearing, with
the intention to find the lubricant which gives the best or at least a satisfactory lifetime for the bear-
ing. For this, you input different oil types, viscosities, and additives, and note their effect on the
Kappa value, the life adjustment factor a23, and the bearing life L10ah. In the example above (bear-
ing ISO 6310, rpm = 1480, bearing housing temperature = 80 °C, load = 7.4%), a simple change of
oil viscosity from 32 cSt to 68 cSt resulted in more than double the life expectancy.
For a proper lifetime calculation, you have input an ISO bearing number under Evaluation graph. If
not, LUBMASTER uses default values for the dynamic bearing load C, which can have a large effect on
the calculation of the bearing life. Data on bearing load, lubricant, and bearing temperature should be
as accurate as possible. Temperature is measured on the bearing housing, at normal operating tem-
perature. The program accepts values from 0 to +200 °C (+32 to 392 °F).
Lubricant type you can select from a menu: mineral oil, synthetic oil and poly-glycol. For greases,
choose the type of oil contained within the grease. If your lubricant catalogue does not mention the
lubricant type, you have a mineral oil. Synthetic oil includes all synthetic types except polyglycol. For
synthetic oil and polyglycol you must input the viscosity at 100 °C.
When any of the lubrication parameters is changed, the evaluation graph is updated, reflecting the
effect the change will have on the COMP no. and the LUB no. If the evaluation graph was obtained
without lubrication data, LUBMASTER will automatically update it and set a COMP no. which shows
the difference in HR at Kappa = 1 and at the newly calculated Kappa value.
- 315 -
14. Work Orders
14. Work Orders

14.1 Standard work order for work mode ‘Planning’
l Input code and name (A), execution interval (B), next date (C).
l Select type (D). Click NEW (E) to select rounds / points.
The work’ mode Planning is an alternative to Data transfer when working with handheld data log-
gers. The working mode is selected under System > Settings. When using Planning, it allows you to
create three types of Standard work orders:
1. Measuring: for condition monitoring with a data logger. This type of work order resembles a
measuring round. However, it can contain several rounds and/or individual measuring points.
2. Lubrication: For a lubrication work order, you can print out check lists containing the lubricant
data in the measuring point register.
3. Maintenance: any maintenance connected with the components and measuring points in the
database. Printout of check lists and work descriptions.
Open Registers > Standard work orders . Input a code, max. 4 characters, and a name (A).
Under Normal interval, input the execution interval in days (B). Present interval is automatically
set to the same number of days. You can edit the Present interval in case you want to make a tem-
porary change in your measuring routines. Next date (C) is the execution date. This is automatically
updated when you close the work order after execution, by adding Present interval to the closing
date. As an alternative, you can mark Set next date on compilation. This sets Next date by
adding Present interval to the day you select the work order for execution. Select the work order
type from the menu (D). As an option, you can connect a work description with the Standard work
order.
Click NEW (E) to add rounds and/or measuring points to the Standard work order.
- 316 -
14. Work Orders
14.2 Compiling a standard work order
l NEW (A) adds to the list of rounds/ measuring points.

l INSERT (B) adds above the marked item, EDIT (C) replaces the marked item.
l Click SAVE (D) to finish and add to the register (E).
The content of the Standard work order is a list of rounds and/or measuring points. When you click
NEW (A), you can select either. Round takes you to the measuring round register, Measuring
point to the tree structure were you make your selection.
With the NEW button you add an item at the bottom of the list. INSERT (B) adds an item above the
marked item. EDIT (C) replaces the marked item with a new choice. When finished, click SAVE (D).
Your finished standard work orders are listed by code (E). With Planning under Maintenance in the
right panel menu you can select Standard work orders for execution. When selected, they become
Work orders, i. e. copies which can be edited without affecting the Standard work order.
- 317 -
14. Work Orders
14.3 Compiling work orders
l NEW adds to the list of work orders. Click EDIT to make changes in the marked work order, or
EXECUTE to download and/or print checklists.
The Planning function, found under the Maintenance ribbon tab, starts with a window for compiling
and editing work orders. Selected work orders are listed by execution date (A). Compilation date (B)
is the date the work order was set up from here. The next column shows the signature (C) used to
start Condmaster Ruby when the work order was compiled. Work order type (D)(1 = measuring, 2 =
lubrication, 3 = maintenance) and name (E) are also listed.
When the underlying Standard work order is OK, click the button EXECUTE to download or print
checklists.
With NEW, you get the Standard work order list and can select from it.
In case you want to modify the work order (without altering the Standard work order), click EDIT and
add/delete rounds or measuring points.
- 318 -
14. Work Orders
14.4 Editing work orders
When editing a work order, you can use the SHOW ROUND button (A) to get a list of the measuring
points within the round (B) and edit these. All other edit functions are the same as for making Stand-
ard work orders.
- 319 -
14. Work Orders
14.5 Executing work orders
l Connect instrument and select Load instrument (A).

l If used, print work descriptions, check lists (B).
The button EXECUTE on the main Planning menu opens a number of choices. Load instrument trans-
fers the work order to the data logger (A). You can print out a list with all measuring points in the
order (B).
Downloading and uploading work orders is the same procedure as for a measuring round with Data
transfer, see "7.5 Downloading measuring round to instrument" on page 150 etc. in section Meas-
uring Rounds.
- 320 -
14. Work Orders
14.6 Preset speed in work orders
l Input speed (A) while downloading or use Input preset speed (B) and Save without load-
ing instrument (C).
Within the same round used in a work order, the measuring points can either have ”Measured speed”
or ”Constant/preset speed”. In case of preset speed, the second speed measuring unit (e.g. meter/
min. or %) is entered. It must be the same for all measuring points in the round. The difference
between max. speed and min. speed must also be the same, e.g. min. speed = 25% for all measuring
points.
The work order can contain up to 10 rounds with different speed settings. For individual measuring
points in the work order (but not inside a round), you cannot preset speed.
Under Input preset speed , you can enter preset speeds before downloading, then use Save
without downloading to save the work order. Normally, you enter preset speeds during the down-
loading procedure.
- 321 -
15. Intellinova Functions

15.1 Intellinova Standard/Compact functionality
Below is an account of the most important functions particular to the Intellinova Standard/Compact
online system.
Where to find it
The Measuring Point Tree has a default element: the Online folder (A), automatically created by
Condmaster for Intellinova users. Under this folder, the registered Intellinova Commander Units are
listed. Under each Commander Unit in the Online folder, measuring points may be created and con-
figured for up to 32 channels (Intellinova Standard).
Note: Maximum number of measuring assignments for Intellinova Standard is 127, and for
Intellinova Compact 96.
The Online System Overview option on the Online ribbon tab (B) displays an overview of all Com-
mander Units in the system. This is also where you create global values and measuring conditions:
Commander Units are registered and monitoring units input under either System > Measuring sys-
tem > NEW or Online System Overview > Registered units > NEW.
More information on the registration of Commander Units in Condmaster is found in the Condmaster
Installation and System Administration manual, document no. 72301.
- 322 -
Controlling the quality and amount of measurement data

When running the Intellinova Standard/Compact online system, Condmaster offers several ways to
control data quality as well as the amount of measurement data saved to database. There are three
different levels on which to control what is measured, saved to the Condmaster database and dis-
played on screen:
1. Commander Unit level: This is where measurement conditions and triggered measurements
are handled. They are used to ensure that readings are taken only when required and at
exactly the right time. If conditions and/or triggers are not fulfilled, no measurement will take
place.
2. LinX level: LinX handles filtering of the measurement results received from the Commander
Unit. The purpose is to dispense with insignificant information. Readings filtered out at this
level are not saved to the database.
3. Condmaster level: Graphical filters are handled by Condmaster and are applied only to read-
ings stored in the database. Graphical filtering only affects what is displayed on screen and
when alerts are raised, i.e. all readings remain in the database, whether displayed or not.
Implementing stringent settings for measurement conditions and/or triggers and filtering options
may cause no measuring results at all being saved to database. If this is the case, Condmaster can be
set up to notify you by means of a system alert. If such an alert is raised, you should examine your
conditions, triggers and filter settings as a first measure. This can be done using the Measuring and
storing logic overview.
Conditions, triggers, filtering options and Measuring and storing logic are all accessed via the
Measuring point data form, or via the Graphic Evaluation.
- 323 -
15.2 Measurement conditions in Intellinova Standard/Compact

From the Online Advanced tab on the Measuring Point Data form, conditions for measurement
may be set up. Conditional measurements are useful for applications where measurement needs to
be guided by strict rules in order to obtain consistent and reliable readings, but where the time of
measurement is not critical.
A maximum of four conditions may be set up for one measuring assignment. Intellinova will check the
status of each of the conditions in turn and measure only if all are met, otherwise move on to the next
measurement task. Conditions may be based on a value measured on another measuring point, on
rpm, digital input or local or global values. Global values, typically rpm, are accessible throughout the
system.
When setting up conditions, you should be aware that when the condition is being evaluated, the
latest available reading is used, i.e. new measurements are not necessarily carried out for each con-
dition evaluation. For instance, if you base a condition for measuring point A on the dBc value of meas-
uring point B and this is measured once every 60 minutes, then the condition may use a reading that
is up to one hour old. The exception is when using rpm or digital input as conditions; these are con-
tinuously measured by the Commander Unit and will therefore always be new and “just-measured”.
Example: Vibration measurement on crane
Condition Implication Action

1) Rpm in range 15 to 60 Crane is in operation If yes, check next condition. If No, abort.
2) Hook load over 10 tons Load variation is acceptable If yes, check next condition. If No, abort.
3) Digital input equals 1 Crane is lifting If yes, measure. If No, abort.
- 324 -
Conditions are set up on the Online System Overview > Measuring condition tab, which you
access either from the Online ribbon tab or from the Measuring Point Data form, using the “...”
button on the Online Advanced tab. The process is as follows:
1. From the Measuring Point Data form, create a condition by clicking a '...' button (A).
2. This will take you to the Measuring condition tab in the Online System Overview form,
click NEW (opens the Measuring Condition window) to create a new condition and name it (B).
3. Select Global value or the Commander Unit under which the measuring point implementing
the condition is registered (C).
4. Select a global value or something measured by the previously selected Commander Unit (D).
5. Select a condition (Over, Under, In range, Out of range etc.) to be evaluated (E).
6. Input one (or two) condition value(s) (F).
7. Save the condition, return to Measuring point data and select it from the dropdown list
under Conditions.
- 325 -
15.3 Triggered measurements in Intellinova Standard/Compact

Like conditional measurements, triggered measurements are a way to guarantee that measurement
is carried out in a controlled manner. The difference is that triggers are used for time critical meas-
urements.
By definition, triggers are event-driven and will execute in response to a change of some sort (e.g.
digital input changing from 0 to 1 or RPM falling below a certain level). This means they are appro-
priate for use when it is imperative that measurement be done only when a certain situation occurs.
Let’s say you set a trigger that a certain DI should go from 0 to 1. If, and only if, this happens within
the specified time frame (Max trigger window), that is the event that triggers the measurement.
Triggers may be based on digital input, OPC or rpm originating from the Commander Unit to which
the measuring point implementing the trigger is connected.
It is possible to implement conditions only, triggers only or a combination of both. In the latter case,
conditions take priority and so will be evaluated before the trigger.
Example:
On an automotive lifting device, measurement should be carried out only when the device is lifting. A
trigger is therefore set up for a certain rpm, say 300. The system will then halt and wait, for a user
defined period of time (Max trigger window), for rpm to pass this limit. If this happens within the
trigger time frame, it will wait for another user defined period of time ( Delay time ) for rpm to
become sufficiently stable, and only then will it start measuring.
See below for information on how to set up triggers.
- 326 -
Triggers are set up on the Online Advanced tab in the Measuring Point Data form, or via the
Online ribbon tab > Online System Overview. The process is as follows:
1. From the Measuring Point Data form, select a trigger type (e.g. Standard trigger) and cre-
ate a trigger by clicking the '...' button (A).
click NEW (opens the Measuring Condition window) to create a new trigger and name it (B).
3. Select the Commander Unit to which the measuring point implementing the trigger belongs
(C).
4. Select value measured on that Commander Unit (D).
5. Select a condition to be evaluated among those having a dark blue icon, and input a value (e.g.
15 rpm) (E).
6. Tick the Use trigger checkbox, input Max trigger (i.e. time to wait for trigger condition to be
met) and Delay time before measurement (time to wait before starting measurement)(F).
under Conditions (G).
8. In the Measuring point data form, input a Retry trigger time (H) (i.e. time to wait before
checking the trigger condition again if it wasn’t passed the first time), which should be equal to
or shorter than the Measuring interval set up under the Online tab. This is to prevent a situ-
ation where the trigger condition is never met.
For information on how to set up a Post trigger (supported by Intellinova Compact and Intellinova
Parallel EN), please refer to "4.14 Using Post trigger to initiate measurement" on page 59.
- 327 -
15.4 Filtering of measurement results in LinX and CES

Filtering of results can be used to discard unwanted readings, e.g. those taken while a machine is not
running, or to limit the amount of readings saved to database when measurement frequency is high
and readings don’t change much over time. Filter settings will not impact the setup of individual meas-
urements, which will always take place at the user defined intervals (providing they meet any con-
ditions and/or triggers set up). Filtering only affects what is saved to database. However, readings
that have been filtered out can still be used as measurement conditions.
When filter settings are implemented, the system evaluates each new reading against the latest read-
ing saved to database according to your filter settings:
The settings in this example means the following:

l A = The initial reading saved to database must be equal to or higher than 0.55 (Accepted
value level).
l B = If Forced storing is activated as in the example above, every tenth measurement result
will always be saved, even if the Accepted value level is not met.
l C = If Extended filter is used as in the example above, the prerequisite for saving a meas-
uring result is that the Accepted value level has to be met and that the measuring value
must deviate by at least 3 (min variation for storing) from the latest one saved; all other ones
are discarded. This step is repeated for every new reading.
Use the Min variation for storing parameter to avoid saving readings that don’t differ significantly
from the latest one stored. This way, you don’t save an unnecessary amount of data, but still capture
enough results to see an evolving trend.
- 328 -
15.6 Alert setup when Intellinova fails to deliver measuring results

When no new Intellinova measuring results are saved to the Condmaster database, you’ll want to
know so you can start troubleshooting. You should therefore take advantage of the Condmaster alert
options for Intellinova to raise an alert if this situation occurs. Options include indication on the alert
list and, if desired, also alert e-mail to a given recipient.
For alert on the alert list, follow these steps:
1. In the right panel menu, go to System> Measuring System.

2. Click the PROPERTIES button (A) and then click Online (B):
3. In the Settings window, mark a registered online unit and click EDIT.
4. To get a “no measuring results alert” on the alert list, select an appropriate time frame from
the Timeout alert on no result dropdown list under LinX (or CES) settings (C):
In the example above, Condmaster will wait for one hour before raising an alert that it is not
receiving new measuring results. The default setting for this function is 1 day. If set to None,
no alerts will be indicated on the alert list.
5. Click SAVE.
The alert list will look something like this to indicate that no measuring results are delivered from one
or more online unit(s):
- 329 -
In the alert list, there is one alert per online unit and measuring assignment.
Alerts in the Measuring Point Tree

In the Measuring Point Tree, the Online folder is marked with an alert icon if one (or more) online
units have alert one or more alerts (A). The individual measuring points whose measuring channels
are affected by a online unit alert mode are also marked with an alert icon (B):
You can also set up to receive alert via e-mail. This can be very useful if operators can’t always keep
an eye on the Condmaster alert list, for instance if the Condmaster computer is in a remote location.
For instructions, see below.
- 330 -
Setting up Intellinova e-mail alerts

This function sends e-mail to a given recipient to notify them that Condmaster, for some reason, is
not receiving measuring results from one or more online units in the Intellinova system. The e-mail
alert is sent according to a user defined timeout alert setting for each registered online unit.
NOTE: In order to implement e-mail alerts, you need to complete the procedure in the preceding sec-
tion, Alert setup when Intellinova fails to deliver measuring results first.
This is the setup process:
1. Go to System > Settings, then click the Alert e-mail tab (A):
2. The recommended setting is Send mail using CES because CES is most likely always up and
running. If CES is to be used for sending emails, the SMTP (or corresponding) settings are man-
aged in theCES Admin Portal. Then go to step 6 below. If Use custom SMTP server is selec-
ted, Condmaster Ruby will be used for sending the alert email, meaning that Condmaster Ruby
must be running. Follow the steps below.
3. Input the company mail server name (C).
4. The default setting for Sender (E-mail address) (D) and the default setting for SMTP Port
25 (G) may be edited if required. Tick the checkbox Use SSL as required (H).
5. If settings made in your mail server require it, input your user name (E) and a password (F).
6. Mark the box ‘Send e-mail when no measuring results from Intellinova’ (H) and input a
valid e-mail address. If Condmaster does not receive new measuring results from an online
unit, an e-mail alert will be sent to this address when the set timeout limit for the particular
online unit has passed.
The e-mails will contain the same text as in the one displayed in the ‘Description’ column in the alert
list (see screen shot example above).
- 331 -
15.5 Graphical filtering in Condmaster

Graphical filtering is done using the Alert delay function, accessed from the Measuring Point Data
form. Alert delay filters out randomly high readings from display and determines when alerts will be
raised. Readings filtered out this way remain in the database; they just aren’t shown in the Graphic
Evaluation, and no alerts are generated for filtered-out readings.
Graphical filtering is not exclusive to Intellinova; it is a function open to all Condmaster users.
Measuring and storing logic overview

Measuring and storing logic provides an overview of all conditions, triggers and filters set for the
selected measuring assignment. Make use of this function to verify that you have not implemented fil-
ter settings, conditions or triggers that will cause all readings to be discarded.
The Measuring and storing logic overview is accessed from the bottom right corner of the Online
Advanced tab on the Measuring point data form.
Under Location, select a Commander Unit, monitoring unit and channel to view. Under Measuring
task, select a measuring assignment. The present settings are displayed to the right:
A = Reading passed the trigger. B = Reading did not pass condition.
To have a look at the latest readings, click the GET LATEST VALUES button. The latest values that
were evaluated against your filter(s), condition(S) and trigger(s), are displayed and you’ll be able to
determine whether the filter settings etc. are reasonable. Values not accepted for storing appear in
red, and if they continue to do so when you get the latest values again, then your filter settings need
to be reviewed.
You can also access the Measuring and storing logic overview from the Graphic Evaluation:
- 332 -
Right click on a title of a graph with Measuring and Storing logic applied and find View Measuring and Storing logic in the
popup menu.
For a key to the measuring and storing logic overview:
Key to Filter overview graphs.
A = Over 100
B = RPM run up trigger level
C = RPM run down trigger level
D = Under 100
E = Out of range, over 200 or under 100
F = Digital input goes high
G = In range, between 100–200
H = Equals 100
I = Digital input goes low
- 333 -
15.7 Transferring data with OPC Data Access
LinX supports OPC import/export via the OPC DA standard protocol.
Read more about the required configurations and settings for OPC import/export using LinX in the
Condmaster Installation and System Administration manual, document no. 72301.
- 334 -
15.8 Setting up status outputs for Intellinova Standard/Compact

When Condmaster alerts cannot be monitored in realtime by an operator who can take immediate
action, status outputs can be used to trigger various kinds of external events (such as a relay setting
off sirens, rotating or flashing warning lights etc., or sending a signal to a digital input in a PLC sys-
tem). The status outputs can be set up to indicate alert status with or without delay time.
Status outputs are used in conjunction with Condmaster alert limits, i.e. when a measuring result
causes an alert, the status output is activated (goes from 'High' to 'Low' or reverse), in turn setting off
the external device connected to it. However, if graphical filtering is set up in Condmaster (see "15.5
Graphical filtering in Condmaster" on page 332 and "9.9 Alert delay" on page 189), the system will
await further readings in order to determine whether an alert should be raised and the status output
set.
To implement an alert/status output scheme, start by setting up the status output (see below), then
connect it to the appropriate alert limit.
1. Go to Online > Online System Overview in the Online ribbon tab.

2. In the Online System Overview window, select the Overview tab.
3. Click the ‘...’ button next to the Commander Unit on which you want to set up the status output
and select Online unit configuration from the popup menu:
4. In the Commander unit configuration window, select the Status outputs tab.
5. In the Commander Unit Configuration form, click the NEW button to open settings for the
status output in the Status Output Configuration form:
- 335 -
6. Name the status output and select a monitoring unit channel for it.
7. As long as the Commander Unit is online (and there are no graphical filters set up in Cond-
master), LinX will immediately trigger the status output connected to a given alert limit if it
receives a reading high enough to raise that particular alert. If the Commander Unit loses its
network connection, the Activation delay parameter (A) replaces the function of the graph-
ical filtering. To implement an alert delay, enter an appropriate time (in seconds) under Activ-
ation delay.
For Commander Units running as standalone units, Activation delay should always be used.
8. Following an alert set off by a status output, you may or may not want to manually restore the
status output to its default state. If you prefer the system to automatically deactivate the alert,
check the Automatic deactivation checkbox (B) and input the amount of time (in seconds)
to wait before deactivation. The alternative Time based means that the status output will
always be deactivated after x number of seconds. The alternative Next result below alert limit
means that when the next measuring result that is not generating an alert comes in, the status
output will be deactivated after x number of seconds.
9. Under Normal state (C), select the status output’s default state (Low or High) from the
drop-down list.
10. Click OK to save your settings.
- 336 -
15.9 Connecting alert limits to status outputs

In order for the system to know when to activate a status output, it is usually connected to one or
more alert limits set up on a measuring point. A Condmaster alert prompts the online unit to trigger
the status output, with or without delay, depending on settings.
Follow these steps to connect an alert limit to a status output:
1. Select a measuring point and open Measuring Point Data.

2. Mark a measuring technique (A).
3. Click the ‘...’ button under Alert limits and select ‘Edit alert limit’ (or ‘New alert limit’)
from the popup menu (B):
4. In the Limit Guide window, select a status output from the Status output dropdown list (C)
(right).
- 337 -
15.10 Multiple SPM Spectrum assignments

For Intellinova, multiple SPM Spectrum assignments may be set up for the same measuring point. For
best spectrum results, it is recommended that you select one SPM Spectrum assignment to be meas-
ured in immediate connection with your dBm/dBc or LR/HR measurement. This is the Co-measured
assignment parameter under the Online tab in the Measuring Point Data form.
- 338 -
15.11 Run up/Coast down measurement

Run up/coast down measurement with Intellinova can be performed from Condmaster. This function
is found under the Online ribbon tab > Online System Overview:
On the Run up/Coast down tab, all previous run up/coast down measurement results (if any) are
displayed, and new measurements can be initiated via the NEW button.
Under Location, select:
1. a measuring point under which to store the run up/coast down measurement result
2. a channel to use on the Commander Unit to which the measuring point belongs
3. an RPM value
Please note that only RPM channels local to the selected Commander Unit can be used. Input your pre-
ferred settings and click START. This run up/coast down measurement will now overrun whatever
task LinX is working on. When measurement is completed, LinX will return to the Commander Unit
task file and resume work where it was interrupted.
To abort a run up/coast down measurement, mark it on the list of measurements on the Run
up/Coast down tab and press <DELETE> on your keyboard.
- 339 -
15.12 Monitoring unit workload

In the Online System Overview found in the Online ribbon tab, an estimate of the workload of
each Commander Unit can be viewed. Click the WORK LOAD button on the Overview tab to view
the workload of each individual monitoring module and channel. It tells you how busy the Com-
mander Unit hardware resources are.
Work load is a helpful feature e.g. if you need to figure out why measuring results aren’t coming in
at the intervals set up in Condmaster. Possible reasons might be:
l hardware malfunctions
l measurement conditions or triggers too restrictively set
l nothing gets past your filter settings
l unduly high Commander Unit workload
Work Load is an estimate of the maximum theoretical workload. A high workload percentage implies
that the Commander Unit hardware is very busy and may be unable to carry out measurement assign-
ments according to the set up measurement intervals. However, the actual workload may be con-
siderably less. Measurement conditions and triggers need to always be evaluated at the specified
intervals, which takes some amount of effort on behalf of the hardware (theoretical workload), but if
the conditions and/or triggers aren’t met no measurement will take place, thus lowering the actual
workload.
Ideally, measuring assignments should be evenly distributed among the available channels. SPM
Spectrum measurements in particular require multiple hardware resources.
NOTE: Deactivated measuring assignments are not included in the estimation of theoretical work load
(see chapter Measuring points, section "4.17 Deactivating measuring assignments" on page 62).
- 340 -
15.13 Machine operating conditions

For online units managed by LinX (Intellinova Standard, Intellinova Compact) and CES (Intellinova
Parallel EN, Airius, Virtual Online Unit), it is possible to measure machine operating conditions such as
power, speed, pressure, flow etc. in connection with vibration measurement. Based on these read-
ings, alert limits can be set in the Condition Manager. Machine operating conditions can be measured
in several different ways depending on the measuring system used; for example through an
Intellinova Standard analog monitoring unit, connected to a temperature or pressure gauge, for
example, or via the RPM input. They can also be imported from Global values.
Throughout Condmaster, a light blue “dot” icon symbolizes machine operating conditions (see screen-
shots below).
To start using machine operating conditions, follow these steps:
1. Define the new operating condition under Registers > Machine Operating Conditions >
NEW button (A):
2. Name the operating condition and input a unit of measurement and a format (B).
3. Predefined intervals (filter for graphics) (C) is an optional setting. Any intervals input
here can be used in graphics to filter out results you don’t want to see at a given time. Click the
NEW button (D) to enter intervals for graphical filtering:
- 341 -
4. Each machine operating condition needs to be “associated” with a measured value. Your next
move is therefore to set up how this particular value is measured. The alternatives are:
l as a global value (under Online > Online System Overview > Global values tab)
and/or
l as a User defined measuring assignment on a measuring point (apply only to
Intellinova Standard/Compact).
5. Next, you’ll need to make the actual “association” between the named operating condition and
the measured value. Select the measuring point where the machine operating condition is to
be used and open the Measuring point data form.
For Intellinova Standard/Compact:
6. On each measuring assignment, two machine operating conditions may be used. Under
Machine operating condition, click the '...' button and select Edit (E).
7. In the Advanced window that opens, select an operating condition (F).
8. Select the origin of the measured value, i.e. a global value or a user defined measurement (G).
9. Max fluctuation (H) represents the maximum fluctuation of the measured value allowed dur-
ing the measurement time. If it varies more than the percent input here, the measurement is
considered failed.
10. Max number of retries (I) is the number of times the Commander Unit will try to measure
before measurement is considered failed.
11. When all settings have been made, select Save in the lower left corner of the Measuring
Point Data window.
- 342 -
For Intellinova Parallel EN:
6. On each measuring assignment, two Hardware controlled (managed by the unit's

DSP hardware) and five Software controlled (managed by the unit's software
application) machine operating conditions may be used. If the machine operating condition
require a setting for max fluctuation (see below), set it up under Hardware controlled, oth-
erwise set it up under Software controlled for optimal performance. Under Machine oper-
ating condition, click the '...' button (in the appropriate place) and select Edit (E).
7. In the Advanced window that opens, select an operating condition (F).
8. Select the origin of the measured value, i.e. a global value (G).
9. Max fluctuation (H) (for Hardware controlled only) represents the maximum fluctuation of
the measured value allowed during the measurement time. If it varies more than the percent
input here, the measurement is considered failed.
10. Max number of retries (I) (for Hardware controlled only) is the number of times the system
unit will try to measure before measurement is considered failed.
Point Data window.
- 343 -
For Airius and Virtual Online Unit:
6. On each measuring assignment, five machine operating conditions managed by CES may be
used. Under Machine operating condition, click the '...' button and select Edit (E).
7. In the Advanced window, select an operating condition (F).
8. Select the origin of the measured value, i.e. a global value (G).
Point Data window.
15.14 Setting graphical filters for machine operating conditions

If Predefined intervals have been set up in the Machine operating conditions register, you can use
them to filter out what you want to see in the Condmaster graphics. The filters will apply to Graphical
evaluation, Spectrum and Compare spectrum. However, from each of these Condmaster functions,
other filter settings can be made.
1. In the right panel menu, go to Graphical Overview > Miscellaneous and select Set filter
for machine operating conditions.
2. In the dropdown list of the operating condition you wish to filter on (A), select an interval. Note
that only one interval can be selected per operating condition. Readings falling into the selec-
ted interval will be displayed in graphics; all others will be left out.
- 344 -
3. Under the ‘...’ button, other predefined intervals can be selected. A new and temporary inter-
val, not defined in the Machine operating conditions register, can also be input here.
The blue Machine operating conditions icon is available in Graphic Evaluation, Spectrum and
Compare spectrum, so filter settings can be changed from there.
- 345 -
15.15 The ‘Ski slope’ phenomenon
A typical ski slope; high amplitude values in the low frequency range.
The ski slope phenomenon involves high amplitude readings in the low frequency region (A), typically
in a steeply declining curve. It can show up in the spectrum domain for vibration as well as shock
pulse measurement.
Ski slope readings may occur for reasons not related to developing machine damages, such as:
l inadequate transducer settling times (common when measuring with portable instrument on
permanently installed transducers)
l in online measurement, ski slopes are frequently caused by variations of Bias voltage (due to
bad cables and/or connectors, oxidation, bad isolation, moisture, aged electronics etc.)
l transducer exposed to high mechanical shocks or excessive temperature changes (e.g from
blowing steam, high-pressure water etc.)
The ‘Ski slope’ symptom in Condmaster can be used to discard these unwanted readings from the
Intellinova online system.
For information on ‘Ski slope’ symptom settings, see "15.16 Setting up the ‘Ski slope’ symptom" on
the next page.
- 346 -
15.16 Setting up the ‘Ski slope’ symptom
The ’Ski slope’ symptom can be used for all types of measuring assignments involving frequency
domain analysis.
The symptom compares the signal level of a low- frequency range with a higher frequency range
(where the frequencies of interest are found), both defined by the user:
Low frequency band value /(divided with) High frequency band value = Ski slope symptom value
If the low frequency range is too dominant, the reading is most likely a faulty ‘ski slope’ reading and
of no use.
To implement the ‘Ski slope’ symptom, follow these steps:
1. In the Measuring Point Data window, mark a measuring technique.

2. In the symptoms section of the window, right click and select New > Add or Insert (A).
- 347 -
3. Keep the default symptom name or enter a name of your own choice.
4. Select a measuring assignment on which to apply the symptom (B).
5. Enter From and To values for the low frequency band (C), in Hz or orders as preferred.
6. Enter From and To values for the higher frequency band (D).
7. Enter a minimum band level (E).
NOTE: The purpose of the Min band level parameter is to prevent readings that are not “true”
ski slopes from being rejected by mistake. If the low frequency band value is lower than the
Min band level, then the ‘Ski slope’ symptom value will always be set to 0 (zero), meaning
the reading will not be discarded.
Using the calculation formula on the previous page, the example in the screen shot above
means:
The low frequency range is 0 - 0,5 Orders = Band value 204.91 mm/s
The higher frequency range is 0,55 - 100 Orders = Band value 28,06 mm/s
The ‘Ski slope’ symptom value is 204,91 / 28,06 = 7,30
8. Click OK to save the settings.
For filtering of measuring results from Intellinova, LinX uses the ‘Ski slope’ symptom value to deter-
mine what readings to discard. To accomplish this, further settings need to be made, see "15.17 Fil-
tering ‘Ski slope’ readings in Intellinova" on the next page.
- 348 -
15.17 Filtering ‘Ski slope’ readings in Intellinova
The purpose of the ‘Ski slope’ symptom is to distinguish a ski slope reading from a good reading and
prevent the faulty readings from being saved to database.
NOTE: Low amplitude readings in the low frequency region may look like ski slopes at a quick glance.
Study the potential ski slope carefully before implementing the ‘Ski slope’ symptom to filter out
measuring results from Intellinova.
In order to use the ‘Ski slope’ symptom in the Intellinova system, the symptom must first be added
to the measuring assignment in Measuring Point Data and two frequency bands defined (see sec-
tion "15.16 Setting up the ‘Ski slope’ symptom" on page 347). Once this is done, follow these steps:
1. In the Measuring Point Data window, mark the measuring assignment and click the
Online Advanced tab.
2. In the Value dropdown list under Filtering of results, select the ski slope symptom (A).
3. Under Accepted value level (B), input a ‘Ski slope’ symptom value above which to filter
out measuring results. The Min variation for storing parameter found under Extended fil-
ter (C) is not used.
4. Click SAVE to save your settings.
See below for an example of measuring results before and after ‘Ski slope’ filtering.
- 349 -
A = Original measurement results; no ‘Ski slope’ symptom filtering.
B = Ski slope’ symptom filtering applied with accepted ‘Ski slope’ symptom value level <= 1.
C = Original measurement results after symptom filtering is applied.
- 350 -
15.18 Sensor connection check

The Sensor Connection Check function is used to verify that an installation of an Intellinova online
system is properly implemented and that the measurement assignments in Condmaster measure on
the correct channel.
The function is also used to check the ‘Transducer Line Quality’ (TLQ), i.e. checking the voltage from
the online unit through the cable to the transducer.
The function performs a measurement on a transducer connected to a channel in Intellinova. During

the check, you have to tap on the transducer. If the transducer is connected to the correct channel,
you should see the peaks from the tapping in the resulting time signal. If you don’t see the peaks
from the tapping or if the time signal consists of noise, there is something wrong in the installation set
up, see below.
The Sensor Connection Check can be carried out directly from the Online ribbon tab, or from the
Online System Overview:
From the Online ribbon tab: First mark a measuring point, then click the Sensor Connection Check
icon.
From the Online System Overview: Click the ‘…’ button by a unit and select Sensor Connection Check.
The Sensor Connection Check function opens up in a separate window.
- 351 -
The sensor connection check is to be carried out on one channel at a time. Please note that during a
check for e.g. channel 1, all other channels are disabled, meaning that no measurement data is col-
lected during this time.
Measuring Time (A) is set to 4 seconds by default. This can be changed as required, but note that
the measuring time affects the line resolution for the measurement (which in turn affects the meas-
uring time).
Click START (B) to start the Sensor Connection Check – and remember to tap on the transducer dur-
ing the measurement.
The result is presented as a time signal and a TLQ value (bias, TLT or kOhm depending on transducer
type) for the transducer (C).
Time signal results:
If the peaks from tapping on the transducer are visible in the time signal, the check indicates that the
setup is OK. But if the time signal consists of noise, there is something wrong with the set up in your
installation. Make sure that the correct transducer is connected to the correct channel in your
Intellinova system and try again. If you are sure that the transducer is connected to the correct chan-
nel and the test fails, the cause might be a cable or transducer failure.
TLQ results:
For a vibration transducer, a typical OK bias value is around 12 V, while 0 V indicates a short circuit
and 24 V indicates cable failure. Different kinds of transducers have different units for this value:
l Vibration transducers: bias value
l Shock pulse transducers (except 44 000 transducers): TLT value
l Shock pulse 44 000 transducers: kOhm value
Click SAVE (D) to save the date and time of the latest performed sensor connection check. This
information is saved as a comment connected to the measuring point.
Click CREATE REPORT (E) to create a report which shows date, time etc. for the latest performed
sensor connection check (sorted by channel). It is possible to print and save the report. The report
template is based on Fast report and can be edited if you require (see section "16.12 Report Manager"
on page 414).
See below for an example of a Sensor Connection Check report.
- 352 -
Example of a Sensor Connection Check report.
- 353 -
15.19 Intellinova Parallel EN functionality

Below is an account of the most important functions particular to the online system Intellinova Par-
allel EN.
Where to find it
The Measuring Point Tree has a default element: the Online folder (A), automatically created by
Condmaster for Intellinova users. Under this folder, the Intellinova system units, registered/created
under the Online System Overview, are listed.
The Online System Overview option under the Online tab in the ribbon bar (B) displays an over-
view of all units in the system. This is also where you create global values and measuring conditions.
System units can be registered/created either in Condmaster under the Online System Overview
> Registered units (C) > NEW or in CES Admin Portal under Unit Management > CREATE UNIT
(D).
More information about registrating/creating units in Condmaster is found in the Condmaster Install-
ation and System Administration manual, document no. 72301.. You can also register/create units in
CES Admin Portal, see the integrated help or the CES Admin Portal User Guide, document no. 72302
- 354 -
Controlling the quality and amount of measurement data

When running the online system Intellinova Parallel EN, Condmaster offers several ways to control
data quality as well as the amount of measurement data saved to database. There are three different
levels on which to control what is measured, saved to the Condmaster database and displayed on
screen:
1. System unit level: This is where measurement conditions and triggered measurements are
handled. They are used to ensure that readings are taken only when required and at exactly
the right time. If conditions and/or triggers are not fulfilled, no measurement will take place.
2. CES level: CES handles filtering of the measurement results received from the system unit.
The purpose is to dispense with insignificant information. Readings filtered out at this level are
not saved to the database.
3. Condmaster level: Graphical filters are handled by Condmaster and are applied only to read-
ings stored in the database. Graphical filtering only affects what is displayed on screen and
when alerts are raised, i.e. all readings remain in the database, whether displayed or not.
Implementing stringent settings for measurement conditions and/or triggers and filtering options
may cause no measuring results at all being saved to database. If this is the case, Condmaster can be
set up to notify you by means of a system alert. If such an alert is raised, you should examine your
conditions, triggers and filter settings as a first measure. This can be done using the Measuring and
storing logic overview.
Conditions, triggers, filtering options and Measuring and storing logic are all accessed via the
Measuring point data form, or via the Graphic Evaluation.
See below for more information about features characterizing Intellinova Parallel EN.
- 355 -
Measuring assignments distributed on DSPs

The Intellinova Parallel EN unit INCEN16 has 16 channels for vibration and/or shock pulse meas-
urement. These 16 channels are distributed on 4 Digital Signal Processors (DSP). Each DSP controls 4
channels, which means that the DSP can handle 4 simultaneous measurements. The Intellinova Par-
allel EN unit INCEN8 has 8 channels connected in parallel to 2 DSPs. The dual processor capacity
enables the possibility to set up two and three channel measurements on any two channels, inde-
pendent of the physical connection, for instance, phase measurement between any channel pair. The
Intellinova Parallel EN unit INCEN4 has 4 channels and 1 DSP that can handle 4 simultaneous meas-
urements.
At this time, for HD measuring techniques such as SPM HD and HD ENV, the maximum number of sim-
ultaneous measuring assignments for each DSP is 3.
- 356 -
The Resource handling functionality on the Online tab in the Measuring Point Data window is avail-
able for INCEN8 only. Our recommendation is to use the default setting Automatic, meaning that the
allocation of resources to perform measuring assignments is scheduled using a default schema, suit-
able for most applications.
Under special circumstances, such as to make sure a specific measuring assignment is always guar-
anteed resources, you can select which DSP will perform the measurement. NOTE: It is not recom-
mended to configure the measuring assignments on an individual INCEN8 unit with a combination of
Automatic and DSP1/DSP2. Use either Automatic on all measuring assignments, or DSP1/DSP2
(combined as preferred) on all measuring assignments handled by the unit.
Features characterizing Intellinova Parallel EN functionality

l Each DSP handles maximum 4 measuring assignments (max. 3 for HD Technology) at this time
l Group measurements
l Linked measurements
l Idle time measurements
l Time Signal Recording
l The measuring state is saved and restored on a new assignment definition (e.g. if a measuring
assignment is changed in Condmaster, the Intellinova Parallel EN unit does not restart the
measuring (as Intellinova Standard/Compact does) - it continues from where it was)
l Live monitoring
l in Condmaster via Live values and CES Monitor
l in Condmaster.NET, with pie charts, diagrams and a complete overview from system
level down to measuring assignment level
l Advanced logging
l in Condmaster via CES Task Log
l in Condmaster.NET via Logs
l Unlimited number of measuring assignments
l For Conditions and Triggers, it handles analog input in addition to digital input, OPC and RPM
l For Conditions, in addition to conditions checked before measurement, it also handles con-
ditions during measurement
l Forced measurement interrupts any ongoing readings on the current DSP, and then the
forced measurement is performed individually
l Unlimited simultaneously measurement of analog values
l Support for SDXC (up to 2 TB SD cards) for offline storing
- 357 -
15.20 Controlling the measurement logic
Measurement logic in Intellinova Parallel EN is about controlling when measurement assignments

shall be conducted. Most common is time- based measurement, where individual measurement
assignments are set up to be measured every X second(s), minute(s) or hour(s). With this type of
measurement logic, the system itself optimizes its resources.
However, some applications or circumstances may call for different logic, in practice overriding the
system’s automated priorities.
More information about the different measurement types:
"15.21 Time-based measurement" below
"15.22 Group measurement" on the next page
"15.23 Linked measurement" on page 361
"15.24 Idle time measurement" on page 363
15.21 Time-based measurement

As previously mentioned, time-based measurement (available for all Intellinova online systems) is by
far the most common set up. This means that whenever the system has available resources, it will
conduct the measurements in order of priority, with the most delayed measurement assignment first
(if any).
For time-based measurement, a measurement interval is the only input data required.
- 358 -
15.22 Group measurement

Available for Intellinova Parallel EN only, this option is used to group multiple measurement assign-
ments to be started simultaneously. For example, you might group ACC, VEL and DISP meas-
urements, or biaxial or triaxial measurements, to ensure that they are all conducted under similar
operating conditions. To start a group measurement, a trigger (and/or measurement condition) is
often set up on one of the measurement assignments in the group. Implementing group meas-
urement means overriding normal system priorities.
NOTE: If phase readings are required for biaxial or triaxial measurements, use the 2 or 3 channel
vib measurement technique.
Setting up group measurement
The necessary input data is basically what measurement assignments should be included in the
group, when the measurement should start, and how often it should be conducted.
Prerequisites
The following prerequisites apply to group measurement:

l A maximum of sixteen measurement assignments can be included in one group (not counting
analog measurements).
l Only one of the measurement assignments in a group can be combined with a trigger and/or
measurement condition.
l Group measurements may include measurement assignments from multiple channels.
l A maximum of four measurement assignments from any individual DSP/group of channels (1-
4, 5-8, 9-12 and 13-16, respectively) can be included in a group. That is to say, a group could
consist of, for example, two measurements on channel 1 and two on channel 2 (which are on
the same DSP or channel group). Further measurement assignments in the same group must
thus be conducted in a different channel group, for example channel 5.
- 359 -
1. In the Measuring Point Data window, mark a measurement assignment to include in a group
measurement (A).
2. On the Online tab, select Group measurement from the dropdown list under Type of meas-
urement (B).
3. Click the ellipsis (‘…’) button under Group to create a new group (C).
4. Click the NEW button in the Group Measurement Register window (D) (or EDIT to change
the setup of an existing group measurement).
5. Name the group (E) and enter a Measurement interval. Click SAVE.
6. Click CLOSE to leave the Group Measurement Register window. You have now created the
group - now you’ll need to tell the system which measurement assignments should be included
in it.
7. For each measurement assignment (under the current measuring point, or a different one) to
be included in the group measurement, mark the assignment in the Measuring Point Data
window (A), select Group measurement (B), then select the group you just created from the
Group dropdown list (C).
8. To set up a trigger or condition for the group measurement on the Online Advanced tab, see
sections "15.27 Triggered measurements in Intellinova Parallel EN" on page 368 and "15.26
Measurement conditions for Intellinova Parallel EN" on page 366, respectively.
Remember: under the ‘…’ button (C), you can always open the Group Measurement Register win-
dow to see the configuration of all your group measurements.
- 360 -
15.23 Linked measurement

Linked measurement (available with Intellinova Parallel EN only) can be used to ensure that cer-
tain types of measurements are conducted under certain operating conditions or within a certain time
frame, for instance on applications with limited measurement windows. With linked measurement,
the system is forced to conduct a user-defined sequence of measurement assignments, thus over-
riding normal system priorities. In other words, if there is a sequence of linked measurements, the
system will bypass the measurement assignment that is next in turn (i.e. the one most delayed) in
order to first complete the entire sequence.
For measurement assignments that are part of a sequence, it is the completion of the previous meas-
urement in the sequence that determines when the next measurement will start (except for the first
assignment in the sequence, which may be time-based and have conditions and/or triggers).
Within the sequence, each individual measurement assignment is performed in accordance with its
conditions and/or trigger settings etc.
Setting up linked measurement
To set up a linked measurement sequence, all you need to do is mark a measurement assignment
and select which other measurement should be conducted immediately before it.
Let's say there is a measuring point with the following measurement assignments:
l VEL (to determine when replacement can’t wait),

l HDENV Filter 3 (to identify later stage bearing damage and start to plan for replacement), and
l HDENV Filter 4 (to detect early stage bearing damage)
Let’s also say that you always want them measured in that order, with no other measurement assign-
ments occurring between these three. Then you would select Linked measurement and simply tell
the system to measure HDENV3 after VEL, and HDENV4 after HDENV3 (see example below).
Prerequisites
The following prerequisites apply to linked measurement:

l A linked measurement sequence can only include measurement assignments from the same
measuring point.
l The first measurement assignment in the linked sequence cannot be of measurement type
“Linked measurement”.
- 361 -
1. In the Measuring Point Data window, mark a measurement assignment to include in a

sequence of linked measurement assignments (A).
2. On the Online tab, select Linked measurement from the dropdown list under Type of
measurement (B).
3. In the dropdown list under Measure after, all other measurement assignments under the
measuring point are listed (C). From this list, select which measurement shall precede the one
you have currently marked.
4. Repeat steps 1-3 for every measurement assignment you want to include in the sequence.
5. Click the ellipsis ‘…’ button (D) to view the Linked measurement sequence configuration
(E). The circled numbers to the left of the measurement assignments indicate the order in
which they will be conducted.
- 362 -
15.24 Idle time measurement

Idle time measurement is available for Intellinova Parallel EN and provides a means to detect
quickly developing events in machines and save only necessary data.
Idle time measurements are conducted in the background whenever the Intellinova Parallel EN unit is
not busy with regular measurements. Any number of measurement assignments can be configured
for idle time measurement; however, the measurement time between them will increase in pro-
portion to the number of such measurement assignments.
Whenever a regular measurement is in line to be handled, idle time measurement assignments are
aborted. Idle time measurement results are not saved until the measuring interval is fulfilled, or
unless the reading exceeds an alert limit.
Idle time measurement is not available for Time Signal Recording or Seamless measurement
assignments.
Setting up idle time measurement
Follow the steps below to set up idle time measurement.
1. In the Measuring Point Data window, mark a measurement assignment for idle time meas-
urement (A).
2. On the Online tab, select Idle time measurement from the dropdown list under Type of
measurement (B).
3. Input a measurement interval (C).
- 363 -
4. Click the ellipsis ‘…’ button (D) to edit the default settings for storing interval and number of
readings preceding an alert that should be saved to database (E).
In the example above, the measurement assignment will be measured in the background as often as
possible (i.e. whenever the system has available resources), but regardless of how often this occurs,
a measurement result will always be saved every 12 hours (Measuring interval, (C)). Should an
alert limit be exceeded during background measurement, the reading will be saved to database along
with the five preceding measurement results (Number of results to store, (E)). If subsequent read-
ings are still above the alert limit, a new measurement result will be saved every fifteen minutes
(Extended storing interval, (E)).
NOTE! A word of caution: be careful when configuring alert limits for measurement assignments set
up for idle time measurement; if you set them too low, it can quickly generate very large amounts of
data.
- 364 -
15.25 Manual measurement

Manual measurement is available for Intellinova Parallel EN and provides a possibility to perform a
manual measurement via:
l a forced measurement - performed manually by the user in Condmaster Ruby (can be per-
formed from several places) or in the Live view under Online in Condmaster.NET
l an API call
Manual measurement can also be used to let a measuring assignment stay active (and stay visible in
the Graphical Overview) but never be measured. (If a measuring assignment is set to inactive, it is
not visible in the Graphical Overview or other places.)
Setting up manual measurement
Follow the steps below to set up manual measurement.
1. In the Measuring Point Data window, mark a measurement assignment for manual meas-
urement (A).
2. On the Online tab, select Manual measurement from the dropdown list under Type of
measurement (B).
3. Perform a forced measurement (can be performed from various places in Condmaster Ruby).
For example, go to '...' by Address (C), mark the measuring assignment in the Online Address
window (D) and click MEASURE.
In Condmaster.NET, go to Online > Live view tab and select unit. Select measuring assign-
ment and then click Force measurement in the Functions window (see 'Live view – online
units' in the Online section in Condmaster.NET User Guide, document no. 72304).
- 365 -
15.26 Measurement conditions for Intellinova Parallel EN
From the Online Advanced tab on the Measuring Point Data form, conditions for measurement
may be set up. Intellinova Parallel EN continuously checks the conditions in the background and
starts measurement immediately when the condition(s) is/are met.
Four conditions being continuously monitored, and two conditions checked during measurement may
be set up for one measuring assignment. Intellinova Parallel EN will continuously check the status of
each of the conditions and measure only if all are met. If the checkbox Save only one result during ful-
filled Condition is ticked, only the first measuring value will be saved when the condition(s) is/are
met. In order for another measurement to be saved, the condition(s) must first get invalid and then
valid again. If the checkbox is not ticked, all values will be save as long as the measuring interval and
the condition value(s) is/are met. Conditions may be based on a value measured on another meas-
uring point, on rpm, analog or digital input, or local or global values. Global values are accessible
throughout the system.
Conditions are set up on the Online System Overview > Measuring condition tab, which you
access either from the Online ribbon tab or from the Measuring Point Data form, using the “...”
button on the Online Advanced tab. The process is as follows:
1. From the Measuring Point Data form, create a condition by clicking a '...' button (A).
click NEW (opens the Measuring Condition window) to create a new condition and name it (B).
- 366 -
3. Select Global value or the Commander Unit under which the measuring point implementing
the condition is registered (C).
4. Select a global value or something measured by the previously selected Commander Unit (D).
5. Select a condition (Over, Under, In range, Out of range etc.) to be evaluated (E).
6. Input one (or two) condition value(s) (F).
under Conditions.
When setting up conditions, you should be aware that when the condition is being evaluated, the
latest available reading is used, i.e. new measurements are not necessarily carried out for each con-
dition evaluation. For instance, if you base a condition for measuring point A on the HDc value of
measuring point B and this is measured once every 60 minutes, then the condition may use a reading
that is up to one hour old. The exception is when using rpm or digital input as conditions; these are
continuously measured by the system unit and will therefore always be new and “just-measured”.
Example: Vibration measurement on crane
Condition Implication Action

1) Rpm in range 15 to 60 Crane is in operation If yes, check next condition. If No, abort.
2) Hook load over 10 tons Load variation is acceptable If yes, check next condition. If No, abort.
3) Digital input equals 1 Crane is lifting If yes, measure. If No, abort.
- 367 -
15.27 Triggered measurements in Intellinova Parallel EN

Like conditional measurements, triggered measurements are a way to guarantee that measurement
is carried out in a controlled manner. The difference is that triggers are used for time critical meas-
urements.
By definition, triggers are event-driven and will execute in response to a change of some sort (e.g.
digital input changing from 0 to 1 or RPM falling below a certain level). This means they are appro-
priate for use when it is imperative that measurement be done only when a certain situation occurs.
Let’s say you set a trigger that a certain DI should go from 0 to 1. If, and only if, this happens within
the specified time frame (Max trigger window), that is the event that triggers the measurement.
Triggers may be based on digital input, analog input (analog input not supported by Intellinova Stand-
ard/Compact) OPC or rpm originating from the Commander Unit to which the measuring point imple-
menting the trigger is connected.
It is possible to implement conditions only, triggers only or a combination of both. In the latter case,
conditions take priority and so will be evaluated before the trigger.
Example:
On an automotive lifting device, measurement should be carried out only when the device is lifting. A
trigger is therefore set up for a certain rpm, say 300. The system will then halt and wait, for a user
defined period of time (Max trigger window), for rpm to pass this limit. If this happens within the
trigger time frame, it will wait for another user defined period of time ( Delay time ) for rpm to
become sufficiently stable, and only then will it start measuring.
See below for information on how to set up triggers.
- 368 -
Triggers are set up on the Online Advanced tab in the Measuring Point Data form. The process is
as follows:
1. From the Measuring Point Data form, select a trigger (A). Please note that the following pro-
cedure will describe how to set up an RPM trigger from this menu (only supported by
Intellinova Parallel EN at this time).
The procedure for creating and setting up a Standard trigger is described in section "15.3
Triggered measurements in Intellinova Standard/Compact" on page 326 and Post trigger is
described in section "4.14 Using Post trigger to initiate measurement" on page 59.
2. Select Trigger type (RPM run up or RPM run down) (B).

3. Input Trigger level, i.e. the value that the RPM should pass on its way up or down, e.g. 1200
RPM (C).
4. Under Delay time (D, optional setting), you can specify a number of seconds (or tenth of a
second) during which Intellinova Parallel EN will delay the start of the measurement.
5. The value for Max trigger window will determine how long the system will wait for the trig-
ger level to be met (i.e. for RPM to reach 1200 in this example).
Please note that RPM trigger communicates directly with an RPM input on the Intellinova Parallel EN
unit, and therefore works differently (reponds more quickly and is checked more often) than the kind
of RPM trigger that is possible to set up using a Standard trigger. The RPM trigger allocks one DSP
resource and uses the RPM information set up under the Online tab, e.g. it uses the RPM raw signal x
the factor which is a calculated value (while Standard trigger uses the RPM raw signal).
Using an RPM trigger would be useful when measuring e.g. a crane that is active for one minute. Let's
say that the measuring interval is set to measure every 60 minutes. As soon as the crane motor rpm
increases and passes the trigger level (e.g. 1200 rpm) within the Max trigger window (600 seconds =
10 minutes in this example), measurement will take place.
- 369 -
15.28 Setting up status outputs for Intellinova Parallel EN

When Condmaster alerts cannot be monitored in realtime by an operator who can take immediate
action, status outputs can be used to trigger various kinds of external events (such as a relay setting
off sirens, rotating or flashing warning lights etc., or sending a signal to a digital input in a PLC sys-
tem). The status outputs can be set up to indicate alert status with or without delay time.
Status outputs are used in conjunction with Condmaster alert limits, i.e. when a measuring result
causes an alert, the status output is activated (goes from 'High' to 'Low' or reverse), in turn setting off
the external device connected to it. However, if graphical filtering is set up in Condmaster (see "15.5
Graphical filtering in Condmaster" on page 332 and "9.9 Alert delay" on page 189), the system will
await further readings in order to determine whether an alert should be raised and the status output
set.
To implement an alert/status output scheme, start by setting up the status output (see below), then
connect it to the appropriate alert limit.
1. Go to Online > Online System Overview in the Online ribbon tab.

2. In the Online System Overview window, select the Overview tab.
3. Click the ‘...’ button next to the Commander Unit on which you want to set up the status output
and select Online unit configuration from the popup menu:
4. In the Commander unit configuration window, select the Status outputs tab.
5. In the Commander Unit Configuration form, click the NEW button to open settings for the
status output in the Status Output Configuration form:
- 370 -
6. Name the status output and select a monitoring unit channel for it.
7. Following an alert set off by a status output, you may or may not want to manually restore the
status output to its default state. If you prefer the system to automatically deactivate the alert,
check the Automatic deactivation checkbox (A), input the amount of time (in seconds) to
wait before deactivation and select one of the following alternatives:
Next result below alert limit = when the next measuring result that is not generating an alert
comes in, the status output will be deactivated after x number of seconds.
Time based = the status output will always be deactivated after x number of seconds.
Time based, start over on alert = the status output will be deactivated after x number of
seconds if no new measuring result generating an alert comes in before the deactivation. If a
new alert is generated, the countdown is restarted.
8. Under Normal state (C), select the status output’s default state (Low or High) from the
drop-down list.
- 371 -
15.29 Global values for Intellinova Parallel EN
Global values, typically RPM, are accessible throughout the system. Global values are used when e.g.
RPM is measured in one location and should be sent to (or be used by) several system units.
Creating global values:
1. Go to Online ribbon tab > Online System Overview > Global values tab (A).
2. Click NEW (B).
3. Provide a descriptive Name (C).
4. Intellinova System (D) is set to CES by default. CES can handle an indefinite number of
global values, while LinX can handle up to 32 global values. This means that when using CES,
the global values does not need to be assigned a number between 1 and 32, as in the case
when using LinX.
5. Indefinite validity (E) is ticked by default, but you can select a time defining how long this
global value should be valid.
6. Mark the checkbox Distribute value to LinX (F) if the global CES value should be distributed
to LinX. Read more in the section "Distribution of global CES values to LinX" on the next page.
7. Mark the checkbox Import via OPC (G) if the value is to be imported via OPC UA. (This
requires that appropriate OPC UA settings have been made, see section ‘Transferring data with
OPC Unified Architecture’ in the Condmaster Installation and System Administration manual,
document no. 72301 manual.)
8. Regarding Source (H), you can select RPM, Digital input, Analog input, API (analog input and
API not supported by Intellinova Standard/Compact), or another measuring point.
9. When ready, click OK (I).
When you have created a global value, this is selectable in the Measuring Point Data form when set-
ting up measuring assignments.
- 372 -
Distribution of global CES values to LinX

It is possible to distribute a global CES value to LinX, which in turn sends the value to Intellinova
Standard/Compact units. Global values handled by CES are scalar values that originate from CES API,
Entity rules, OPC UA, etc.
If a global CES value should be distributed to LinX, open and edit an existing global value or create a
new global value according to the instructions above. Make sure that Intellinova system is set to
CES. Mark the checkbox Distribute value to LinX and select a number for the global value (Global
number ). LinX can handle up to 32 values. It is important that you select a number that is not
already assigned.
Limitations regarding the distribution of global CES values to LinX:

l A value’s validity time is not supported in LinX and Intellinova Standard/Compact units.
l Max 32 values are supported by LinX.
l The Individual value per commander unit functionality (under Settings > LinX - Global val-
ues > EDIT for an online unit handled by LinX) is not supported.
- 373 -
15.30 Live values in the Online System Overview
The Online System Overview consists of several tabs with different kinds of information. Live val-
ues, i.e. current status and/or measuring value in real time, are shown in a column to the right (A)
under the following tabs: Global values, Measuring Conditions, RPM and Digital inputs, Status
outputs.
Please note that the Live values functionality is handled via Condmaster Entity Server (CES). LinX
does not support Live values (B). OPC is supported by LinX but currently not supported by CES, which
means that no values are shown for OPC.
If there is no answer from CES, the text “Waiting…” (C) is shown.
For LinX, the tab LinX Diagnostics (D)(previously called 'Diagnostics', is only shown if there are any
LinX instances registered) does not provide live values but provides information about the latest val-
ues for different parameters, e.g. RPM, Conditions, etc.
- 374 -
15.31 CES Monitor in Condmaster
The purpose of the CES Monitor is to provide a simple overview over what is going on in the online
system and to facilitate troubleshooting. Open the CES Monitor via the CES MONITOR button (A) in
the Online System Overview (available in the Online ribbon tab).
All measuring assignments are listed for each unit; date and time for the latest storage, information
on measuring interval and when next measurement will take place (B). The status bars in the 'Next
measurement' column indicates the progress on the currently performed measurement in percent
(C).
A red circle with a white X inside it (D) is shown if an error has occurred during the latest meas-
urement. Click on the icon to open the error message.
A yellow triangle with an exclamation mark inside it is shown if Condition(s) and/or Trigger (E) have
not been met. When this is shown for a group measurement, this icon is shown for all its assign-
ments. Click on the icon to open an error message with information about which assignment failed.
If a measuring assignment is expanded, all parameters that are included in the measurement will be
displayed along with its status and/or value. The values represent the latest measurement for the
assignment:
- 375 -
If the checkbox Channel view is ticked (A), the sorting is changed according to channels.
Depending on which kind of object is marked in the upper window (B), different information is shown
in the lower window (C):
If the CES folder is marked, information on how much data has been stored (D).
If a system unit folder is marked, information on work load is shown per DSP (E).
If a DSP is expanded, detailed information on current activity is shown (F).
- 376 -
If a measuring assignment is marked, information on number of measurements is displayed (G). If

this measurement assignment is part of a group or a linked measurement, you can right click in the
grid and select either View belonging group measurements or View belonging linked measurements
(H) to open that view (right click and unmark View belonging group/linked measurements to close the
view).
If a measuring assignment that is included in a group measurement is marked, then all measurement
tasks included in the group are displayed (I).
If a measuring assignment that is included in a linked measurement is marked, then all measurement
tasks included in the group are displayed (J).
Clicking the TASK LOG button (K) in the upper right corner opens the task log for the current meas-
uring assignment or unit (see "15.32 CES Task log in Condmaster" on the next page).
When clicking FORCED MEASUREMENT (L), a forced measurement for the current measuring
assignment is performed. Please note that the forced measurement does not interrupt all the other
readings. Also note that it is only possible to performed a forced measurement on measuring assign-
ment level.
Right click on a measuring assignment to find shortcuts to Spectrum, Graphics or Measuring res-
ults.
- 377 -
15.32 CES Task log in Condmaster
The CES Task log window is opened by clicking the TASK LOG button (A) in the CES Monitor win-
dow (which is accessed via the Online System Overview found in the Online ribbon bar). When
the Task log window is opened, 1 MB of data is retrieved with log information from current time and
backwards.
In the upper window (B), you select the CES server, Database, Intellinova Parallel EN unit, or Meas-
uring assignment that you want to see the log for.
In the lower window (C), the current log information is shown. Different rows are colored differently
depending on their categorization; Fatal errors and Errors are color coded red while Warnings are yel-
low, System information is gray and consists of information about what the system is doing (e.g. Pre-
paring..., Sending Measure request to DSP, etc), and Extended information is colored purple and can
provide useful information about for example Global values (e.g. Global value 1 changed from 12.12
to 12.85, Global value 2 has not changed, etc.). By default, the log filter is set to Extended inform-
ation but this can be changed under Settings (F), see below.
Right click on a measuring assignment to find shortcuts to Spectrum, Graphics or Measuring res-
ults.
The FORCED MEASUREMENT button (D) is only enabled when a measuring assignment is marked.
When clicked, a forced measurement for the current measuring assignment is performed. Please note
that the forced measurement does not interrupt all the other readings.
Clicking the Log elipsis ‘…’ button (E) opens a popup menu with several options:
- 378 -
l Automatic update – this option is ticked by default and means that new log information is
retrieved automatically. If this option is unticked, a new option Retrieve log is shown. Select
this option to retrieve further log information.
l Retrieve earlier log – this option is only visible when the top row in the log window is
marked. A click on this option retrieves all earlier log information from the first post’s time
stamp. When this information has been retrieved, the log functionality goes back to retrieving
the latest log information.
l Clear log – clears the window (deletes the information).
l Save to text file – all information in the log window is saved into a text file (defined by the
user).
l Settings (F) – opens a separate Log settings window with options:
Filter (G) contains a dropdown list with a set of options on what to show in the log information win-
dow. Please note that these options only affects what is shown in the window – it does not affect the
actual logging in the unit. To be able to affect the log level in the unit, use Condmaster.NET (see the
integrated help or the Condmaster.NET User Guide, document no. 72304).
Log size (H) refers to how many lines/rows displayed in the log window. When maximum number of
lines/rows are reached, the oldest is deleted.
Click SAVE (I) to save your settings.
- 379 -
15.33 Temperature measurement

Vibration transducers with integrated temperature measurement, i.e. transducers of type
SLD144B-M8/UNF-T, is supported in the online system Intellinova Parallel EN. The transducer gen-
erates a signal which is extracted and converted into a temperature reading in Condmaster. Tem-
perature measurements with set alert limits can for example be used as a further indication of
condition.
When setting up the measuring assignment in the Measuring Point Data window, select Vibration
as measuring technique with Online as measuring instrument (A). On the Online tab (B), make sure
to select an Intellinova Parallel EN unit, and a channel using the transducer SLD144 with Tem-
perature (C):
- 380 -
In the Measuring Point Data window with the Vibration measuring technique marked to the left
(D), temperature is set up as a condition parameter. Right click on the white surface to the right, click
ADD (or INSERT) (E) and select Temperature (F) from the list:
Click the … button under Alert limits (G) to set an alert limit for the temperature.
See below for an example of a trend graph showing temperature readings:
- 381 -
In the transducer register (found under System > Transducers), it is possible to set a time interval
for how often temperature readings should be done:
Please note that this setting affects all measuring assignments using the SLD144 transducer with tem-
perature.
15.34 Transferring data with OPC Unified Architecture
Condmaster Entity Server (CES) supports OPC import/export via the OPC UA standard protocol.
Read more about the required configurations and settings for OPC import/export via OPC UA in the
Condmaster Installation and System Administration manual, document no. 72301.
- 382 -
15.35 Signal Quality Test

Available for the Intellinova Parallel EN system, the Signal Quality Test runs in the background, con-
tinuously checking for ski slopes and bias problems. It can also help to identify problems with faulty
or incorrectly connected transducers. The purpose of the function is to determine if the signal is of
good quality or if there are deviations that should be investigated further.
The test comprises the following measurements, the results of which are converted to a scale of 0-1:
l One HD ENV, Filter 3 measurement to determine the signal-to-noise ratio, where a factor
below 0.1 means there is too much noise, and the reading is rejected.
l One ski slope measurement; if the ratio is higher than 10, the signal is deemed as a ski slope,
and the reading rejected.
l Bias stability measurement; if the standard deviation during the measurement time is greater
than 0.5 volts, the value is considered unstable, and the reading is rejected.
l Signal quality index; a weighted summary of the three parameters mentioned above.
If one or more of these measurements is rejected, the total result of the test is negative.
Signal Quality Test settings

Here is how to find the Signal Quality test settings:
1. On the Online tab, select Online System Overview in the ribbon bar.
2. On the Overview tab in the Online System Overview window, mark a unit and click the
Registered units button (A):
3. On the Online units tab in the Settings window, mark an existing unit and click the Edit but-
ton (or click New to add a new unit) (B).
- 383 -
4. In the Online System window, the Signal Quality Test can be enabled and set to run x num-
ber of times per minute, hour, or day (C).
5. Make the appropriate settings and click Save (D).
Viewing Signal Quality Test results

For units with the signal quality test enabled, the results of the test are accessed from the Online
System Overview window using the ‘…’ button:
- 384 -
The Signal Quality window displays the respective measurement results (ski slope, signal-to-noise
ratio, bias stability, and signal quality index) in separate graphs per channel. The signal quality index
is a weighted summary of the three parameters.
In general, low numbers for all signal quality parameters is an indication of good signal quality, but it
depends on where the transducer is located and if there is a lot of naturally occurring vibration or not
(in some situations, there might be a lot of naturally occurring vibrations that might affect some num-
bers).
- 385 -
Right-click a channel or select the more options button (A) for a menu with alternatives:
l Show connections: shows all measuring assignments connected to the channel in a tree
view.
l View as list: can be toggled on or off.
l Hide item: hides the selected item.
l Settings: opens Signal Quality Index settings (B).
The default Signal Quality Index settings (B) are weighted numbers for calculating the signal qual-
ity index. The ski-slope factor has the highest weight number because a ski-slope is generally con-
sidered more severe than vibration bias and signal noise.
By default, all online units are shown in the list at the top of the window (Show all online units (C)),
but it is possible to select a single measuring unit from the list.
Selecting the Word icon (D) at the top opens a window where you can save the result list in Word
format and thus be able to print it.
- 386 -
16. Additional functions

16.1 Rule Based Evaluation, RBE
The purpose of the optional module RBE is to give guidance on what to do when certain conditions are
met.
To define an RBE alert, go to the right panel menu, select Maintenance > Rule Based Evaluation.
Click NEW to create a new RBE alert (or EDIT to make changes in an existing setup).
In the Rule Based Evaluation data form, click “...” (A) under Standard comment to select a com-
ment that will be set when the RBE rule is fulfilled.
Under Triggered measuring points, click NEW (B) and make your selection from the list of meas-
uring points. For each trigged measuring point, click NEW (C) under Variables to name a variable
(use descriptive names), e.g. Pump_Housing, and select a measuring technique. Depending on the
choice of technique, the variables are automatically assigned certain properties which can be eval-
uated by rules.
Rules are set up in the lower part of the form, where a list of operators and variables is displayed to
the right (D). At the bottom of this list are the variables, with their respective properties following the
variable name, e.g. Pump_Housing.LimitUpper_dBm. Double click in the list to select the variables
involved and the appropriate operator(s), which are then displayed under Rules to the left (E). To
remove a variable or an operator from the Rules list, mark it with the mouse, then press Delete on
your keyboard.
The example rule in the figure above, “DriveSide_SPM.dBc > 22 AND Pump_Housing_SPM.dBc > 35”,
means an alert will be triggered when the dBc value on the drive side exceeds 22 and the dBc value
on the pump housing exceeds 35. Use the Comment tab (F) to indicate what actions should be taken
when this particular alert is triggered, e.g. “Open inlet valve”. Photographs etc. may be attached for
illustrative purposes.
- 387 -
16.2 Measuring Point Imaging - Overview
1. Download app to mobile phone.

2. Use the app to download measuring round to phone:
a) manual transfer via USB cable to computer, or
b) via cloud
3. Take photographs with mobile phone and connect them to measuring points
4. Upload photographs to Condmaster (via USB or cloud)
The Measuring Point Image Handler enables users to connect images or photographs to meas-
uring points. Once connected, the images can be displayed in various parts of Condmaster, such as
the Alert list, Graphic Evaluation, Spectrum and Colored Spectrum Overview. They are also
shown in the Leonova portable instrument, making it easier for users to ensure that measurement is
carried out on the right equipment.
There are two ways to provide Condmaster with images:

l Photographs, taken with any camera, can be saved to a file folder and then uploaded to Cond-
master. If there are many images of the same type (gearboxes, motors etc.), it can be difficult
to tell which image corresponds to which measuring point when connecting them in Cond-
master.
l Photographs can be taken with Android or iPhone cellular devices, using apps from SPM, and
then uploaded to Condmaster in either of two ways:
a) manual transfer by connecting your mobile phone to the Condmaster pc
b) through an SPM cloud storage service (online file storage)
For maximum efficiency, we recommend that you use one of the apps for measuring point imaging.
With the apps, measuring rounds are downloaded to the mobile phone and the photographs taken are
automatically tagged with a user-selected measuring point number. This is done right on site, so you
can be sure the correct image is connected to every measuring point.
The SPM apps are downloadable from the Google Play and iPhone AppStore web sites.
- 388 -
16.3 Measuring Point Imaging using mobile apps and cloud
l In the Measuring Point Image Handler window, measuring points are listed (G) according
to the selection made under the ‘...’ button (H). A camera symbol indicates that an image is
connected to the measuring point.
Start by downloading and installing the appropriate app for your mobile phone, then go to Cond-
master and open the Measuring Point Image Handler in the right panel menu under Graphical
Overview > Miscellaneous (A).
In the Measuring Point Image Handler window, use the Tools button in the upper right corner
(B) to make default size and resolution settings for the images. These settings can be edited for indi-
vidual images at any time (see section "16.5 Measuring Point Imaging using images in file folder" on
page 392).
Click the MOBILE IMAGE SYNCHRONIZATION button (C). The Measuring Point Image window
is displayed. Copy and paste (or write down) the Synchronization code (D) in this form; you will
need it later on.
Under Select action in the same form, select Upload rounds to cloud (E) and click NEXT. Then,
select the measuring round(s) to download to your mobile phone and click the NEXT button. Click
UPLOAD to start transferring the measuring round(s) to the cloud.
On your mobile phone, start the SPM app. When you use the app for the first time, go to the app Set-
tings and input the synchronization code. Exit Settings and select Upload/Download > Download
rounds from cloud.
When the download is finished, open a measuring round in the app, select a measuring point (this
automatically activates the camera) and take a photograph of the corresponding equipment. Repeat
- 389 -
this process for every measuring point in the measuring round. To view an image, click the measuring
point again. When you are done, click Back and select Upload/Download > Move images to
cloud. This action moves the images to the cloud and deletes them from your phone.
Back in Condmaster, select Download images from cloud (F), then click NEXT and DOWNLOAD.
The images are now connected to their measuring points. For information on how to change the size,
resolution and orientation of images, please see end of section "16.5 Measuring Point Imaging using
images in file folder" on page 392 in this manual.
16.4 Measuring Point Imaging using apps and manual transfer
l In the Measuring Point Image Handler window, measuring points are listed (F) according to the
selection made under the ‘...’ button (G). A camera symbol indicates that an image is con-
nected to the measuring point.
Start by downloading and installing the appropriate app for your mobile phone, then connect the
phone to the Condmaster computer. In Condmaster, open the Measuring Point Image Handler in
the right panel menu under Graphical Overview > Miscellaneous (A).
In the Measuring Point Image Handler window, use the Tools button in the upper right corner
(B) to make default size and resolution settings for the images. These settings can be edited for indi-
vidual images at any time (see below).
Click the MOBILE IMAGE SYNCHRONIZATION button (C). The Measuring Point Image window
is displayed. Under Select action, select Move rounds manually to mobile device (D) and click
NEXT. Then, select the measuring round(s) to download to your mobile phone and click NEXT. Now
select your type of mobile phone and click NEXT again. Follow the instructions in the top of the form.
- 390 -
NOTE: for Android, a folder named ‘SPM’ must be present at root level of the phone’s SD card; if it is
not there, you need to create one. Click CLOSE. The measuring rounds are now available in your
mobile phone.
Disconnect the phone and start the SPM app. Open a measuring round, select a measuring point (this
automatically activates the camera) and take a photograph of the corresponding equipment. Repeat
this process for every measuring point in the measuring round. To view an image, click the measuring
point again.
When you are done photographing, connect the phone to the computer. In Condmaster, select Move
images manually from mobile device (E). Click NEXT and select your mobile phone type and
click NEXT again. Follow the instructions in the top of the form, then click MANUAL DOWNLOAD.
When download is complete, disconnect the phone.
The images are now connected to their measuring points. For information on how to change the size,
resolution and orientation of images, please see end of section "16.5 Measuring Point Imaging using
images in file folder" on the next page.
- 391 -
16.5 Measuring Point Imaging using images in file folder
If you do not use the mobile app to photograph machine equipment, but have images stored in a file
folder, open the Measuring Point Image Handler in the right panel menu under Graphical Over-
view > Miscellaneous (A).
In the Measuring Point Image Handler window, click the ‘...’ button (B) to make a selection of
measuring points to connect images to; all measuring points, the measuring points marked in the
Graphical Overview (or Measuring Point Tree) when opening the function, or one of the meas-
uring rounds displayed in the Filter selection window. Click OK to save your selection.
Back in the Measuring Point Image Handler window, use the Tools button in the upper right
corner (C) to make default size and resolution settings for the images. These settings can be edited
for individual images at any time (see below).
Still in the Measuring Point Image Handler window, mark a measuring point in the list and click
the ‘Edit’ link (D). Browse to the image file folder location, select an image to connect to the marked
measuring point and click OPEN. The Measuring Point Image window is displayed. In the lower
part of this window are ‘+’ and ‘-’ buttons (E) to adjust the default size and quality (resolution) of the
image. To select a different image, click the LOAD IMAGE button (F). To delete the image, click the
CLEAR IMAGE button (G).
Click SAVE to return to the list of measuring points and repeat the process; mark measuring point >
‘Edit’ > browse and select image > adjust size and resolution (if necessary) > SAVE.
- 392 -
When a measuring point has a saved image connection, the image is displayed in the right part of the
Measuring Point Image Handler window. Using the ‘Rotate left’ and ‘Rotate right’ links below
the images (H), they can be rotated for best display.
16.6 Measuring Point Imaging - Viewing contents on cloud
Via the Measuring Point Image Handler, you are able see what measuring rounds are uploaded to
the online file storage (cloud). Measuring rounds can also be removed from the cloud.
To view the current content on the cloud, open the Measuring Point Image Handler in the right
panel menu under Graphical Overview > Miscellaneous (A).
In the Measuring Point Image Handler window, click the MOBILE IMAGE SYNCHRONIZATION
button. The Measuring Point Image window is displayed. Under Select action , select Show
cloud information (B) and click NEXT. A new window is opened, listing the measuring rounds cur-
rently available on the cloud (C).
To remove a measuring round from the cloud, mark it and click the DELETE ROUND ON CLOUD but-
ton (D). After deletion, click REFRESH (E) to verify that the measuring round was removed (and to
see if others have been added).
- 393 -
16.7 Work descriptions
• Input Code (A) and Name (B).
• Write text (C) and save.
Work descriptions, found in the right panel menu under Registers > Work descriptions, can be
attached to measuring points, components, rounds, and work orders. They consist of a Code (A),
max. 4 characters, a Name (B), and free text (C).
Work descriptions are free standing objects, stored in the work description register. They can be
attached to more than one item. When attached to a round or work order, you can print them when
downloading to the instrument.
- 394 -
16.8 Standard symptoms for EVAM
This register contains the standard symptoms used for spectrum analysis of EVAM measuring results
(A). You can create your own symptoms by clicking NEW (B), save them under a name and input the
parameter names (C) and parameter values (D). For details, see the separate instruction ”Stand-
ard symptoms in Condmaster”, number 71584.
- 395 -
16.9 Symptom groups
A symptom group consists of two or more standard symptoms and can even contain other symptom
groups. By saving the typical symptoms of a machine part, e. g. a shaft with its bearings, as a group,
you can quickly attach all those symptoms to an EVAM assignment.
Bearing symptoms are always a group, because the rotational speed of the shaft has to be multiplied
with different factors to define the frequencies of inner ring, outer ring, and cage. The whole group is
configured together when you input the shaft rpm and the ISO bearing number under one of its symp-
toms.
Click NEW (A) to create a symptom group, select standard symptoms from the list and save under a
name.
- 396 -
16.10 Condition View Report

Introduction to Condition View Report
The main purpose of the Condition View Report function is to provide the possibility to create and
print reports based on the information in Condition View.
Condition View Report thus allows you to design and print a report containing all the graphs,
attachments, comments etc. laid out in the Condition View function and save it in Microsoft Word
format (where it can be further edited, if necessary). In addition, cover and end pages and sup-
plementary text can be added to the report.
Getting started
Condition View Report is found under the Report Manager tab in the ribbon bar. Mark the meas-
uring point(s) you want to include in the report (A) and click the Condition View Report button (B):
- 397 -
Opening a sequence or measuring round in Condition View Report
If you have saved sequences of measuring points in Condition View (see section "9.38 Getting star-
ted with Condition View" on page 227 -> ‘Saving selected measuring points as a sequence’), you can
open them straight from the ribbon bar by right-clicking on the Condition View Report button (A)
and selecting a sequence from the popup list (B). The sequence opens in the Condition View
Report window (C).
From the Condition View Report window (C), you can change to a different sequence by clicking
the LOAD SEQUENCE button (D).
NOTE : You can also load measuring rounds into Condition View Report by clicking the LOAD
ROUND button (E).
- 398 -
Creating your report in the Preview window

Once you have opened the measuring points (or sequence) that should be included in your report, it’s
time to get to work on creating it. In the Condition View Report window, click the PRINT
PREVIEW button (A):
By clicking the CONDITION VIEW button in this window you can quickly go straight to Condition
View, should you discover while working with the report that something needs to be added, removed
or otherwise changed.
NOTE: The DELETE button in this window only deletes the marked measurement assignment(s)
from Condition View Report, not from any sequence they may be part of.
- 399 -
Structure of the report

The reports generated through Condition View Report are made up of four main ‘sections’ (A, B, C,
D), parts of which you can edit to suit your needs. The editable parts can either be considered as per-
manent elements of every report – parts containing ‘standard’ text that you usually do not change -
or you can edit the content from time to time if necessary.
Using checkboxes, the various sections can be included or excluded, in whole or in part, to create a
report tailored to the target audience and purpose.
In addition to the information, data and graphics provided in the main sections, you can also create a
custom header and footer (E) (see section ‘Creating header and footer’).
By clicking the UPDATE button (F), you generate the initial report. Whenever you’ve made a change
to the report, click this button again to update it and see the result of your changes.
The content you created for the editable parts of the report is retained when you exit the function and
thus will be there next time you open Condition View Report. Note that everything you do in Condi-
tion View Report applies only to the current database.
- 400 -
Cover Page section

As the name implies, this section is the front - or title - page of the report. This page may include text
as well as image(s).
To create a cover page, click the EDIT button (A) under Cover Page in the Preview window. This
opens a simplified editor (B), where you can enter and format text, and insert images:
Enter your content and click SAVE to save your work and close the editor. In the example above, we
entered a title, a subtitle, and a date, and aligned it all in the center of the page. To spice things up,
we also inserted an image.
Back in the Preview window, click the UPDATE button (C) in the lower left corner to see a preview
version of your cover page.
To include or exclude the cover page, remember to tick or untick its checkbox (A) in the Preview win-
dow.
NOTE: The header and footer of a report are not created in the same editor as the cover page, but
under the ellipsis (‘…’) button in the bottom of the Preview window (D) (see section ‘Creating header
and footer’).
- 401 -
Creating page header and footer
Appearing on every page of the report, headers (A) and footers (B) can be used to display additional
and descriptive information, such as page numbers, document name, the date the report was cre-
ated, a logotype, a draft or revision number, etc.
To create a header and footer for the report, click the ellipsis (‘…’) button in the bottom of the Pre-
view window and select Edit Header/Footer (C). This opens a separate editor, see below.
- 402 -
The editor for the header and footer looks a little different than that for the cover page, but essentially
offers the same possibilities as Microsoft Word.
To enter information in the header or footer, double-click in their respective area of the document in
the editor and use the tools in the toolbar. For instance, to insert page number, page count and logo-
type (picture), click the Insert menu (D).
- 403 -
Summary section
In the Summary section (A), you have the opportunity to elaborate on the content of the report in
free text. The constituent parts of this section are:
l Initial Part 1 takes free text input as well as pictures. For example, you could use this part for
an initial summary of the report. Click the ellipsis (‘…’) to create content for this part.
l The Measuring Point Summary Graph shows the percentage distribution between green,
yellow, red, and grey condition status for the included measuring points. It also indicates the
number of alerts.
l Initial Part 2 also takes free text input and pictures; click the ellipsis (‘…’) to enter content for
this part.
l Measuring Points lists the measuring point number, name and condition status of the meas-
uring points included in the report.
l Measuring Assignments lists all measurement assignments under each of the measuring
points included.
l Alerts shows alerts connected to the respective measuring points (if any).
l The Final part appears after the list of measuring points and alerts, and takes free text input
as well as pictures. You might use it to go into details, or – despite its name - you could even
use it to enter an introduction to the Detailed Page(s) section that follows. Click the ellipsis
(‘…’) to create content for this part.
Back in the Preview window, click the UPDATE button (C) in the lower left corner to see a preview
version of your report. In the report, the different parts discussed above will appear in the order they
are listed under Summary in the Preview window - but remember that you can include or exclude
information as you see fit, using the checkboxes (should you wish to rearrange the order in which the
information is presented, first save the report as a Word file, then edit in MS Word).
- 404 -
Detailed Page(s) section
The Detailed Page(s) section retrieves its content from the information you worked on in Condi-
tion View (see the "9.37 Introduction to Condition View" on page 226 section).
Assuming you’ve ticked the Detailed Printout checkbox - either in the Condition View toolbar or in
the Condition View Report window (A) - this part of the report can contain all the graphs (i.e. spec-
trums, time signals, condition trends etc.), as well as the alerts, attachments, comments, and images
(B) from Condition View, all of which can be included or excluded using the checkboxes.
- 405 -
NOTE : The Condition View Graph can be rotated to suit printing in landscape or portrait ori-
entation:
Don’t forget to click the UPDATE button to view your changes after you’ve included or excluded
information.
- 406 -
Final Page section
The Final Page takes free text input and images; perhaps a standard text that is always the same in
all your reports, or a situation-based conclusion or discussion about further actions. Click the EDIT
button to create content for the final page, then click UPDATE to see the result.
- 407 -
16.11 Customized Reports

Introduction to Customized Reports
Customized Reports makes it possible to design reports according to personal preferences by creating
and customizing scripts that generate the desired output to the reports. To use Customized Reports,
basic programming skills are required.
Instead of creating time-consuming individual reports, for instance by copying and pasting inform-
ation from Condmaster into a Word document, a universal report can be built using Customized
Reports by adding variables linked to components, measuring points and fields in the report. The
variables are linked to functions or procedures that are called when previewing/printing to add reques-
ted information (such as trends or spectrums) about the variables in the report.
The functionality can be used advantageously when condition monitoring is applied to several similar
plants or machines, where the significant difference is the components and measuring points set up in
Condmaster. If Customized Reports has been used to create a report for a plant or machine, and an
additional report should be created for a similar plant or machine, you only need to make a copy of
the report and link the variables to the other plant's/machine's components and measurement points
in Condmaster. You do not need to go into each individual report to edit settings, and thus you win
time, even though Customized Reports requires a large portion of time to create the first report.
Customized Reports navigation
A. Customized Reports icon.

B. Customized Reports window.
C. List of existing reports.
D. Preview = preview, print or save selected report.
E. ... = go to Customized Reports Archive.
F. New = create a new report.
G. Copy = make a copy of selected report.
H. Edit = edit selected report.
I. Delete = delete selected report.
J. Export to file = export selected report to file.
K. Import from file = import a file from file.
L. Report window.
M. List of created variables (components, measuring points and fields).
- 408 -
N. Add = add variable linked to component, measuring point or field at the bottom of the list.
O. Insert = insert component, measuring point or field variable above the selected variable.
P. Edit = edit selected variable.
Q. Delete = delete selected variable.
R. Arrows = move selected variable up or down the list.
S. Edit Document = open the Edit Document window.
Edit Document navigation
A. Edit Document window.

B. Insert Function = insert a function into the document where the cursor is placed.
C. Global Procedures = instead of creating several individual functions to display, for example,
an alert list for multiple measuring points, you can create a global procedure to achieve that.
D. Function Name = appear in the report where the cursor was placed when the script was inser-
ted.
E. Function Script = the actual code of the script.
F. Print Report = generate a preview that you can print.
G. Insert Script = select script from a list to standalone functions/procedures or func-
tions/procedures for components, measuring points and fields.
H. Script Help = get a description of that the selected script does.
- 409 -
Creating Customized Reports
1. Click the Customized Reports icon (A) found under the Report Manager tab in the ribbon
bar.
2. Click New (B) in the Customized Reports window. For editing an existing report, select
report and click Edit.
3. Name the report under Report Name (C).
4. Add (D) Components, Measuring Points and Fields to the report. Variables are automatically
linked to the items added. See section ‘Adding Field variable to Customized Reports’ for fur-
ther information.
5. Click Edit Document (E).
6. For creating a function, place the cursor where in the report the function should be inserted.
Click Insert Function (F).
7. Name the function in the Function Name (G) box.
8. Place the cursor in the Function Script box (H). Click Insert Script (I) and select func-
tions/procedures for a component, measuring point or field, or standalone func-
tions/procedures.
9. Select script and/or object from the list. Click OK. The script is now inserted to the Function
Script box. Adjust the script as desired. Check that there is no warning text marked with red
- 410 -
in the bottom of the window. For help understanding the meaning of the script, place the
cursor on the script and click Script Help.
10. For creating a global procedure, click Global Procedures (J). Click Insert Default Pro-
cedures and edit the code as desired. Click OK. The Global Procedures are now available
when clicking Insert Script in a function.
11. For settings to enable various output from Condition View to Customized Reports, see sec-
tion 9.37 and above.
12. Mark a script and click Print Report (K).
13. Select Execute all scripts and click OK.
14. Double click and edit the fields in the Print Report window, and click OK in the Edit window.
15. Click OK in the Print Report window. A print preview will appear.
16. Print report, Save As Word File, Save to Archive (see section ‘Saving printouts of
reports to Customized Reports Archive’ for further information) or Close window, as desired.
- 411 -
Adding Field variable to Customized Reports
1. Click Add Field in the Report window.
2. Fill in Caption and Variable Name. The variable name must start with a letter and contain
only A-Z, 0-9 and underscore.
3. Select Combobox or Edit field. A combobox with a list of alternatives to choose between
when producing the report can be created. An Edit field enables programming using different
value types. See below.
4. If Edit field is selected, select Value Type. Choose String for text programming, Integer for
integer programming, Float for use of decimal values, Date for date and Document for insert-
ing text and pictures from a text editor.
5. Enter selectable values in the Values box.
6. Select if the field variable is required for the report.
7. Click OK.
- 412 -
Saving printouts of reports to Customized Reports Archive
1. When you have created a report, click Save to Archive in the Preview window.
2. Input Name and click OK.
3. In the Customized Reports window, click the '...' button and select Customized Reports
Archive to access the archive.
4. Preview, Rename, Delete report or Close window as desired. Via the Preview button you
can print or save the report as a word file.
The difference between Customized Reports and Customized Reports Archive
Reports accessible from the Customized Reports window can be regarded as "templates" in which
you can edit variables, scrips, etc. while reports accessible from the Customized Reports Archive
is to be regarded as printouts of a Customized Report (scripts etc. are not editable).
- 413 -
16.12 Report Manager

Condmaster Ruby comes with a function called the Report Manager. This function provides a num-
ber of standard reports of database items such as components, measuring points, measuring rounds,
alert list etc.
The Report Manager is accessed via the Report Manager tab in the Condmaster ribbon bar:
The reports can be previewed on screen, printed, saved as PDF, exported and imported. Most reports
also offer sort order and other options.
Understanding how reports are composed

Each report is composed of a template and a collection of database items:
It is important to understand the difference between a template and a report, and the relationship
between the two.
The standard SPM templates contain a page header, printed only on the first page of every report,
and a footer, which is copied onto every report page. That’s all.
- 414 -
The “bulk” of a report on the other hand is a set of data, collected from the Condmaster database and
laid out according to the individual report design. Depending on the type of report and the amount of
data in your database, this bulk of information can range from a few rows to many pages.
Every time a particular report is generated, the template is merged with the current bulk of data. This
means there must be a “connection” between the default template and every individual report. For all
standard reports, this connection has been set up by SPM. However, if you want to make changes to a
standard SPM template or report, you need to make a new connection yourself (see section "Cus-
tomizing the standard templates").
Report Manager functions

Each menu option displays the Report Manager window (see screen shot below), where a tree struc-
ture in turn presents the reports available to you. Two file folders are always present in the tree:
l My reports (A): Under this folder, you’ll find any reports you have created yourself.
l Standard reports (B): Reports developed by SPM are found under this folder. They come
with the system and cannot be edited, deleted or renamed.
PRINT (C): Send report straight to printer without preview (not applicable to templates)
PREVIEW (D): Preview report on screen before printing (not applicable to templates)
NEW (E): Create a new report from scratch in the report generator tool. The new report will be saved
under My reports for the database item selected (Components, Measuring rounds etc.)
- 415 -
COPY (F): Open a copy of the current report in the report generator tool, where you can edit the copy
and save it under a new name under My reports
EDIT (G): Open the current report in the report generator tool so you can edit and save it under the
same name (this option is available only for My reports)
DELETE (H): Delete the current report (this option is available only for My reports)
EXPORT TO FILE (I): Export the current report (in FastReport file format)
IMPORT FROM FILE (J): Import a report (in FastReport file format) and save it under My reports
Functions under the ‘...’ button:
Print to PDF file (K): Create a copy of the current report in pdf format (not applicable to templates)
Rename (L): Rename the current report (applicable to My reports only)
Set as default template (M): Select this template to be the default template for all reports (applic-
able to templates under My reports only)
Customizing the standard templates

The standard templates delivered with Condmaster contain the SPM logotype and a report name
assigned by SPM. If you prefer your own logotype or any other change to a report header or footer,
follow these steps:
1. In the right panel menu, select Report Manager > Templates.

2. Mark a standard template and click COPY. The report generator tool, FastReport, opens inside
Condmaster. For more information about FastReport, please see section ‘Designing your own
reports’.
3. Make your changes in FastReport.
4. Click the SAVE button in the FastReport tool bar. You are prompted to enter a name for the
new template. When you have done so, close FastReport. The new template is now found
under Templates > My Reports.
5. Mark the new template, click the ‘...’ button and select Set as default template.
At this point, your changes do not affect any of the reports, i.e. when you print or preview
them, they will still have the standard SPM header and footer. To have your template changes
reflect on the reports, you need to make a copy of a given report, then make a new connection
between that report and your new template. Follow these steps:
6. In the Report Manager menu, select a database item for printout (Components, Measuring
points, Comments, etc.).
7. Select an individual report in the Report Manager window. For a standard report, click COPY.
For a report in the My reports folder, click EDIT. FastReport opens within Condmaster and dis-
plays the design of the report.
8. In the FastReport menu bar, select Report > Options:
- 416 -
9. The Report settings window is displayed. Click on the Inheritance tab:
10. Among the option buttons, select Inherit from base report, then mark the template you cre-
ated earlier. Click OK.
11. When FastReport displays the following warning message, select Delete duplicates and click
OK:
12. Save the report. If it is a copy of a standard report (see under 7) above), you are prompted to
give it a new name.
13. Close FastReport.
14. Preview the report to verify that your new template is in fact applied to this report.
Repeat steps 6-13 above for every report where you want your new template applied.
Designing your own reports

The Report Manager uses a report generator tool named FastReport. This is an add-on component
which opens inside Condmaster, making it look like an integral part of the Condmaster program.
FastReport has the capability to generate reports containing graphs, spectrums and time signals as
well as orbit graphs.
FastReport is a complex product requiring a certain level of programming skills and understanding.
Along with the Condmaster installation comes a separate user manual for the FastReport software.
Please take advantage of that and other FastReport support options if you need to design customized
reports.
- 417 -
16.13 Exporting to Word file
Clicking the "..." button in the Graphic Evaluation window (found under Graphical Overview ribbon
bar 'Graphics' or via the right panel menu) sends the whole or parts of the graphics selection in JPG
format to a Microsoft Word file. On the menu that opens (see screen shot), you can make a selection
and edit diagram size.
16.14 Exporting measuring results to Excel
In the Graphical Overview, you can mark any folder or group of folders and go to the right panel
menu where you select (Graphical Overview >) Miscellaneous > Export to Excel file to export
the measuring point name and number and a selection of measuring results to an Excel document
where you can set up your own graphics for the results.
- 418 -
16.15 Exporting spectrums and time signals
Spectrums and time signals may be exported as .txt (plain text) or .uff (Universal File Format) files,
facilitating the transfer of data for further analysis in ME’scope, MatLab or LabVIEW, etc.
In a spectrum or time signal, right click and select Save to file (A). In the Save as window, browse
to the location where you want to save the file.
By default, the file will “inherit” the measuring point name with the addition of date and time inform-
ation, followed by “- Spectrum” or “- Time signal” and the selected file format (.txt or .uff) (2).
Time signals can also be exported as .wav (audio file format), select ‘Save as type: Wave file (.wav)’
in the Save as window.
- 419 -
16.16 Runtime count
This is an optional function that counts the number of hours a component has been running, and
reminds the user when a periodic machine maintenance service is due. Typical services are inspec-
tion, lubrication, oil change or part replacements which are due after a stated number of operating
hours.
The function is used in connection with continuous monitoring (CMS System). On machines with vari-
able speed, the rpm is used to indicate whether the machine is running or not. Components with fixed
rpm must have at least one measuring point with the technique ‘User defined measurement’. As an
example, it can measure the temperature of a bearing. When a stated minimum value is exceeded at
the time of measurement, the machine is ‘running’, else it is not. The measuring intervals must be
short enough to get a realistic estimate of the machine’s operating hours.
A short description of the maintenance service is saved as a 'Standard comment'. One or more of
these comments are connected with the service assignment, e. g.:
A Inspection (every 40 hours)
B Lubrication (every 80 hours)
C Spindle bearing adjustment (every 120 hours).
By making one service assignment which includes these three jobs, the user starts three clocks which
respectively give alert every 40, 80, and 120 hours. 'Adjustment' includes 'Inspection' and 'Lubric-
ation', so all three clocks are zeroed when 'Adjustment' is reported back as done. 'Lubrication'
includes 'Inspection', so two clocks are zeroed while the countdown for 'Adjustment' continues.
- 420 -
To achieve this,
1. Input all three services on the same runtime form in the runtime register under a common
name, e. g. ‘Lathe maintenance’.
2. Input the three comments in the Standard Comment Register.
3. Attach all three comments to all three sub assignments.
4. Designate the appropriate comment as ‘service comment’.
5. Set two alert times, e.g. yellow alert 8 hours, red alert 4 hours before the service is due.
6. Attach this ‘Standard service assignment’ to the component.
It will appear on the runtime form under the right panel menu > Maintenance > Runtime, where it
shows the hour count. The service report is made either
l via the button on the runtime form which sets the service comment against the component
(visible in the ‘Graphics’ display and on the comment list) and nulls the clock.
l by setting the service comment with the Set comment function.
Service alerts connected with the runtime function do not appear on the alert list. To check what has
to be done, open the run time function and check the remaining hours to service. The message will
change to alert colour at the stated number of hours before the service is due.
- 421 -
16.17 Communication with SAP software
SPMs software Condmaster Ruby for machine condition monitoring provides a direct link to SAP soft-
ware. Pressing the SAP button (A) on the Condmaster alert list sends the marked alert as a message
to the SAP software. Returned is a Work order number that locks the alert, until a second message
from SAP deletes the alert and sets a comment on the Condmaster measuring point, stating what has
been done.
In addition, the Condmaster measuring point setup now contains an optional field for SAP equipment
numbers.
The operation requires no extra data input and one simple operator decision: Does the Condmaster
alert merit an SAP work order? The SAP operator responds by sending a Standard Comment to a text
file.
Standard Comments are a user defined register of short messages in Condmaster, e. g. ‘Bearing
replaced’. The SAP operator can add free text. On receiving the comment, Condmaster deletes the
alert. The comment is added to the list of comments under the measuring point and is visible in the
measuring result diagram.
l When Condmaster is set up, the SAP operator is registered in the window shown above. For
SAP protocol, see Condmaster Installation and System Administration manual, document no.
72301.
- 422 -
16.18 Safety copy
1. Go to System > (Database maintenance >) Safety copy.

2. Select path to the destination folder and change filename as needed (A)
3. Select backup type (B), normally Full (Basic data and measuring results). Depending on
backup type, different options (C) are displayed.
4. If you want, click the link under Backup interval (days) (D) to set an interval for an auto-
matic reminder
5. Click START (E)
Normally you select a Full (Basic data and measuring results) backup type, which means that
everything will be copied. Other backup type options are:
l Basic data = includes Condmaster settings, measuring point setup, rounds, etc.
l Measuring results = includes all measuring results in the database. The option ‘Include res-
ults from long term memory’ means that all measuring results from the short term memory
and the long term memory will be copied.
l Measuring results: Interval = includes measuring results within a user selected date and
time interval.
l Measuring results: Incremental = includes measuring results added since the last incre-
mental backup.
To highlight an important difference between the interval and the incremental backup type: If
you use the interval backup type to include measuring results from the past 24 hours, meas-
uring results with date and time within the last 24 hours will be included. The incremental
backup type includes all measuring results added (regardless of date and time) since the last
incremental backup. Example: A unit goes offline for three days, then starts running again and
sends 10 measuring results for day 1, 10 results for day 2, and 10 results for day 3. An interval
backup type that runs once per day includes the past 24 hours and therefore includes the 10
measuring results for day 3 (the 20 results from day 1 and 2 are missing). An incremental
backup type that runs once per day includes all 30 measuring results because these have been
added since the latest incremental backup was made.
The ‘Next incremental from date’ setting is something that you do not normally use when per-
forming a regular incremental backup, but offers the following options:
Reset = resets the date and includes all measuring results from when the database was
- 423 -
created. Set to latest Full backup = sets the date to latest full backup and includes measuring
results added since the last full backup was made.
Set to custom date = sets the date to a user selected one and includes results measured after
this date. This option can be used when you want to start using the incremental backup type
from today’s date or when you want to override the latest incremental backup date for some
reason.
l Measuring results: Differential = includes results added since the last full backup was
made.
This image shows the difference between incremental and differential backup type.
l Bearing catalogue = includes the Condmaster bearing catalogue

l Reports = includes all reports made using the Fast Report tool
Under Backup interval, click the link to set a time interval for making safety copies. You will get a
reminder to make one when you start Condmaster.
The safety copy function takes a snapshot of the database at the exact time you click START – given
that your database account has permission to create databases. If problems occur, we strongly
recommend to cancel the backup and make necessary changes. Normally there are no problems with
database privileges, but if problems occur, the SQL Server database account needs to be adjusted.
Check with your system administrator to get permission to create databases.
If you click YES in this window instead of taking the necessary actions needed, the safety copy func-
tionality from previous Condmaster versions is used when creating the backup. However, this func-
tionality does not take a snapshot of the database. Instead, it reads directly from the database which
can be changed during the backup and thereby risking full data consistency and integrity. Please note
that this option is not recommended.
It is possible to set up automatic backups via a scheduled task in Windows, see section ‘ Backup
routines’ in the Condmaster Installation and System Administration manual, document no. 72301 for
details.
- 424 -
16.19 USB communication with Leonova and Leonova Infinity

The 64-bit version of Condmaster Ruby supports only serial communication (RS232) with
Leonova and Leonova Infinity. Use the Condmaster 32- bit version for USB com-
munication.
Depending on your hardware and software setup, additional actions might be needed. Please be
reminded that the correct USB driver is required, and that any USB active sync software must be deac-
tivated in order for the USB communication to work. Some computers might have USB ports which
are incompatible with the instrument, and therefore we recommend trying an external USB 2.0 com-
patible hub if the problem remains despite having installed the right driver etc. (see below).
Depending on your Condmaster version (as well as hardware and software setup), this is an outline of
options and the necessary actions:
Instructions in the right box may be required also for older Condmaster versions and/or when
installing Condmaster on a different computer.
Windows 7/8.x/10 64-bit system; install/check USB driver and disable active sync soft-
ware system
In Windows 7/8.x/10 64-bit system, Windows Mobile Device Center (WMDC) must be installed.
Also, a deactivation of USB active sync software needs to be done.
With the instrument connected to the PC and set to communication mode:
1. Make sure that Windows Mobile Device Center (WMDC) is installed (check in the Control
panel).
In Windows 8.x/10 64- bit system , Windows Mobile Device Center (WMDC) is installed
automatically when the instrument is connected to the computer the first time, provided the
computer has internet access.
- 425 -
In Windows 7 64-bit system, Windows Mobile Device Center (WMDC) is not installed by
default when the instrument is connected to the computer. Instead, an error that Windows
could not install drivers for unknown devices might show. Please follow steps a) and b) below
before continuing the rest of the procedure:
a) Type “windows update” into the ‘Search program and files’ field in the start menu to
check for updates.
b) Windows will suggest a required update for Microsoft USB Sync (Windows Mobile
Device Center). Download and install the update.
2. Under Control panel > Device manager, verify that the instrument shows up as Microsoft
USB Sync under Mobile devices.
3. In WMDC, go to Connection settings and uncheck ‘Allow USB connections’. (The rest of the
settings are not important for the communication to work.)
4. Make sure that any other USB active sync software is deactivated/turned off.
Windows 7/8.x/10 32-bit system; install/check USB driver and disable active sync soft-
ware
In Windows 7/8.x/10 32-bit system, an error that Windows could not install drivers for unknown
devices might show when you connect the instrument to the computer. Installation of the required
driver needs to be done manually.
1. From spminstrument.com > Downloads > SPM Software, download the following files to your
computer:
- 426 -
2. Connect the instrument to the computer and set the instrument in communication mode. Win-
dows default USB driver will be installed first time the instrument is plugged in.
3. Go to Control Panel > Device Manager and locate Microsoft USB sync under Mobile devices.
4. Right click on Microsoft USB sync and select ‘Update Driver Software’.
5. Click ’Browse my computer for driver software’ (locate and install driver software manu-
ally).
6. Click ‘Let me pick from a list of device drivers on my computer’.
7. Click the button ‘HAVE DISK…’, then BROWSE and select the wceusbsh file (wceusbsh.inf)
from where you downloaded onto your computer. Click OPEN, then OK.
8. Now you should be able to see Anchor USB EZ-Link Cable in the list of compatible hardware.
Mark it and click NEXT.
9. The ‘Update Driver Warning’ dialogue box is displayed. Click YES.

Note: If you get a warning stating that a certificate is missing, click ‘Install anyway’.
10. Verify in the Device manager (Control panel > Device manager) that the instrument shows up
as Anchor USB EZ-Link Cable under Mobile devices.
- 427 -
11. If your computer has Windows Mobile Device Center (WMDC) installed, go to its Connection set-
tings and uncheck ‘Allow USB connections’. Also make sure that any other USB active sync
software is deactivated/turned off.
Troubleshooting Guide
When all actions above have been taken and communication still is not working, try the following:
1. Make sure to use the latest MMI version (4.26 or later for Infinity, 3.08 for Leonova).
2. Make sure that the cable between the instrument and the computer is properly connected and
working correctly.
3. Set USB communication in the instrument to USB - Standard, since not all computers are cap-
able of using High speed USB communication.
4. Always try different USB Ports (some may differ from others because some motherboards have
different chipsets from one side to another). Also try USB Ports on peripheral devices such as
laptop docking stations, monitors, keyboards, adapters, etc.
5. Some computers might have USB ports that are incompatible with the instrument. We recom-
mend using an external USB 2.0 compatible hub.
6. Make sure that the antivirus software and/or firewall settings is not stopping or blocking the
process wmdc.exe or wmdcbase.exe (Windows Mobile Device Center). The easiest way to
check if WMDC conflicts with your firewall is by turning off the firewall completely (do this on a
trusted network) and plugging in the instrument. If it does connect when you have turned off
the firewall, you have a firewall conflict.
7. Make sure to use the latest revision of your Condmaster version.
8. Make sure that your version of Condmaster supports the operating system on your computer,
see table below.
Nova Nova Nova Ruby Ruby Ruby Ruby Ruby

Operating system 2006 2008 2010 2012 2014 2016 2018 2019
XP X X X X X - - -
Vista 32-bit X X X X X - -
Vista 64-bit - - - - - -
Windows 7/8.x/10
X X X X X X
32-bit
Windows 7/8.x/10
X X X* X* X* X*
64-bit
*) Condmaster 64-bit version does not support USB communication with Leonova and Leonova
Infinity
9. Ensure that your computer has all Windows Updates http://update.microsoft.com/

10. If you have Windows 7/8.x/10 64-bit operating system and problems installing Microsoft USB
sync (Windows Mobile Device Center, WMDC), try updating the driver manually by running the
64-bit version from http://support.microsoft.com/kb/931937.
11. The driver for Microsoft USB sync might be outdated or installed incorrectly. In the Device
Man- ager window (Control panel > Device Manager), check in the Mobile devices node for
‘Microsoft USB sync’. Right-click on ‘Microsoft USB sync’ and select ‘Uninstall’. In the ‘Confirm
Device Un- install’ window, check the alternative ‘Delete the driver software for this device.’
and click OK. Next time you plug in the USB connector; Microsoft USB sync will be reinstalled.
- 428 -
12. Ensure that .NET Framework 3.5 is installed and enabled on the PC (Control panel > Program
and features > Windows features).
13. Remove all the files in the /Windows/Temp/ and C:/Users/AppData/Local/Temp directories.
This will empty Windows cache memory.
14. There might be a problem with conflicting applications such as:
l Parental control utilities blocking specific kinds of network traffic
l Network Traffic Optimizers reducing bandwidth usage by introducing compression
15. An alternative is to use serial communication (RS232) via cable CAB47 together with an USB-
RS232 converter (art. no. 93423). Note that this step requires changing instrument and Cond-
master settings to instrument communication via COM port (instead of USB).
- 429 -
16.20 Automatic removal of results

Depending on the settings regarding how often an online unit is to measure and how much results are
to be saved, the measurements can potentially quickly lead to large databases that take a lot of disk
space, which in turn can slow down Condmaster. To save disk space, you can set up an automatic
removal of results when a certain amount of time has passed. It is possible to choose whether the
time signal should be deleted on the results saved, and it is also possible to mark results that should
not be covered by the removal. If you don’t want to schedule automatic removal of results, you can
delete results immediately, learn more below.
The Automatic removal of results function is found under System > Database Maintenance.
NOTE: The function only removes results for measuring assignments connected to online instru-
ments.
Automatic removal of results – main window

The overall steps needed to activate the automatic removal of results function are listed below. For
more information about the individual steps, see the sub-headings further below.
l Configure automatic removal for the groups of results via the EDIT button (A).
l Add any exceptions via the EXCEPTIONS button (B).
l Tick the Automatic removal of results checkbox to activate the function (C).
l Click SAVE to save the configuration (D).
In this example settings have been made for Spectrum results and Scalar results.
Each time measuring results are moved from the short time memory to the long time memory,
removal of results is performed according to the configuration made. Automatic removal of results is
performed when the short time memory has reached 150 results.
Delete results immediately

If you want to remove measurement results immediately according to the current configuration, click
the DELETE NOW button (E) and click OK in the window that appears.
- 430 -
Configure automatic removal for a group of results

Mark a group of results, for example Spectrum results and click the EDIT button in the Automatic
removal of the results window to configure the removal.
Tick the checkbox Enable filtering (A) to enable filtering of results. The checkboxes Filter 1 (B),
and Filter 2 (C) gets ticked by default and are set with default values for elapsed time (weeks) and a
number of results to keep. Make your settings as required and click OK. The settings are explained
below.
According to the settings in this example for Spectrum results, the following removal occur:
Short time memory
Results from the short time memory are never removed.
Long time memory

l The first 12 weeks in the long time memory are left intact.
l Filter 1 (13-52 weeks) (B): For results that are older than 12 weeks, 14 results per week are
kept. This means that one measurement result is being saved every 12 hours; the rest are
deleted (except protected results).
If the alternative Remove time signal checkbox is ticked, the time signal will be removed on
the remaining results (protected results are left intact).
l Filter 2 (53-156 weeks)(C): After an additional 40 weeks have passed, i.e. for results that are
older than 52 weeks (12+40 weeks), one result is saved every week; the rest are deleted
(except protected results).
l End of life (>156 weeks)(D): All results that are older than 156 weeks (52+104 weeks) are
removed. If the Remove protected results checkbox is ticked, those results will also be
removed.
NOTE:
- 431 -
l To run the Automatic removal of results function itself does not affect the performance of
Condmaster significantly.
l Since the time signal is large, you can save a lot of disk space by only removing the time signal
and setting the Number of results to keep to All. A time signal takes 2.56 times as much
disk space as a full spectrum.
l If the Remove time signal checkbox is ticked, a full spectrum is always saved.
Configure exceptions to automatic removal of results

Click the EXCEPTIONS button in the Automatic removal of the results window to configure
exceptions to automatic removal of results. All measuring assignments configured for online instru-
ments are listed.
Mark the measurement assignments that should NOT be included in the removal of measurement res-
ults and click OK.
NOTE: Marked results are categorized as exceptions and will therefore always be left intact (even if
End of life and Remove protected results is activated for groups of results).
- 432 -
Mark results that should be protected from removal
From Measuring results, Graphics, Spectrum, and Condition View windows, you can protect res-
ults from removal. Mark a result, right-click and select Protect results from removal (A). When
protected, the result is marked with a shield symbol.
After a result has been marked as protected, it is not possible to delete it without first inactivating the
protection (mark the result, right-click and select Protect results from removal). NOTE: Protected
results can be removed automatically if End of life is activated and the Remove protected results
checkbox is ticked.
To activate/inactivate protection of several results at a time, select them and click CTRL + P.
- 433 -
Saved Cases
In Graphics in the Saved Cases tool window to the right, you can load a saved case, i.e. a certain
event in a single graph, for example a bearing fault, a bearing replacement, imbalance, etc.
To save a new case:
1. Zoom in the area of a graph that applies to the case, then right-click and select Save case (A).
2. In the Save case window that opens, Name the case (B) (and check that the From and To date
and time is correct). Enter a description of the case as necessary. The Protect results from
removal alternative (C) is marked by default, which means that the results will be protected
from removal.
3. Click SAVE (D).
Double click a saved case in the Saved Cases tool window to open the measuring point and show the
case. The time period of the saved case is displayed with a yellow background color (E).
- 434 -
16.21 Machine Builder

Note: The Machine Builder function has primarily been designed for the instruments Intellinova Par-
allel EN , Leonova Diamond, and Leonova Emerald. Although Intellinova Standard and Intellinova
Compact belong to the "Online" instruments, the functionality has not been designed for these instru-
ments, and therefore we can not guarantee that it will work for them.
In Condmaster Ruby, a machine consists of several components that together form a machine. For
example, a machine can consist of the components motor, gearbox and pump.
From a component library in Machine Builder , users can add machines to the Graphical
Overview /Tree structure. When a machine is added in Machine Builder , appropriate measuring
points, measurement assignments, and fault symptoms are automatically generated for the machine.
Color Zones are automatically added to the measuring points of the added machine.
To add a machine to the Graphical Overview /Tree structure, follow the instructions in " 16.21.1
Adding a machine in Machine Builder" below.
16.21.1 Adding a machine in Machine Builder
1. In the ribbon bar, go to Graphical Overview > Machine Builder (A).
2. In the Machine Builder window, choose an option in the list and select OK (B).
3. In the Machine Builder window, select Add (C).
4. In the Add component window, choose a component and select OK (D). The component is
then added to the Machine Builder overview.
5. In the Machine Builder window, select Add (C).
6. In the Add component window, choose another component and select OK (D).
- 435 -
7. In the Machine Builder overview, select and hold a component (E) and drag the component
to another component and connect the couplings of the components. The components form a
machine that can be expanded with additional components.
NOTE: A green field appears on the couplings of the components when selecting and holding
a component. These green fields should be linked together.
8. To add additional components to the machine, repeat steps 5-7.
9. To change the order of the measuring points numbers, see Rearranging the measuring point
numbers.
10. In the right pane, select ‘…’ by a component and choose Calculated RPM, Measured RPM
or Fixed RPM (F) for components of the machine.
- 436 -
11. In the right pane, select ‘…’ by a measuring point and choose a transducer (G) for the meas-
uring points.
NOTE: To select a transducer type to be used for all measuring points, select the transducer
by Default vibration transducer (H), choose a transducer in the list and select OK.
12. Select Continue (I).
13. In the Edit window, enter Number, Name, and Machine criticality for the machine and
select OK (J).
14. In the Measuring points window, choose a component from the list and select Edit (K). Enter
the desired Number and Name for the component and select Save.
15. In the Measuring points window, select '...' (L) by a measuring point. Enter the desired Num-
ber and Name for the measuring point and select OK.
16. Select Save machine (M).
- 437 -
The machine is displayed with grey Color Zones in the Graphical Overview/Tree structure. Elements
without evaluated measurement results have grey Color Zones, which mean that there are either no
measurement results or no alert limits set. For information on how to set up alert limits, see "5.11
Overview, alert limits and alert delay" on page 77.
Previously added machines can be reused. To reuse previously added machines, go to Machine
Builder > Add> Previously created machines.
There is also possible to reuse saved templates from Machine Builder. To save a template, select '...'
in the Machine Builder window and select Save as template. To reuse previously saved templates,
go to Machine Builder > Add> Templates.
16.21.2 Rearranging the measuring point numbers
- 438 -
When a machine is added in Machine Builder, measuring points numbers (A) are added automatically.
In Machine Builder, the measuring point numbers appear as red dots on the machine. To rearrange
the order of the measuring point numbers, follow these steps:
1. In the Machine Builder window, select Rearrange (B).
2. Choose a component in the list and select Move up (C) or Move down (D).
NOTE: The measuring point numbers are automatically adjusted when moving the com-
ponents up or down. The lowest numbering is always at the top of the list and the highest
numbering is always at the bottom.
3. Select Close.
4. To rearrange the measuring point number on a component, right-click a measuring point and
choose a measuring point number in the list (E).
- 439 -
16.22 Entity rules

Introduction
The highly flexible and powerful Entity rules function can be used as a hub for expanding and cus-
tomizing Condmaster with customer-unique, event-driven functions, as well as creating custom integ-
rations with other IIoT systems.
The function makes it possible to monitor a variety of events and automatically invoke actions – in
Condmaster or elsewhere – based on these events.
Through a straightforward interface, users create “IF/THEN” logic flows, thus configuring custom
rules governing what happens when defined condition(s) occur.
Rule statements can be time-based and/or event-based, and actions may include, for example
l triggering a defined type of measurement
l triggering a system alert
l sending an email
l sending an API call
l creating a work order
l closing a relay
l or a variety of other things.
Below are a few examples of entity rules of varying complexity:
l When a measuring result (for example VEL RMS) exceeds 2.3, then send an email.
l When the RPM for machine A exceeds the RPM of machine B, then send an email.
l When a speed measurement from any of the centrifugal pumps exceeds 3500 or drops to 135
RPM, then send an email.
l A global value from measuring device x should always (no condition) be sent to another sys-
tem.
Please note that the flexibility of the Entity rules functionality allows you to create much more com-
plex rules than the examples above.
The Entity rules functionality applies to online units handled by Condmaster Entity Server (CES)
(i.e. Intellinova Parallel EN, Airius sensors).
Where to find the function
- 440 -
Entity rules resides in Condmaster.NET and can be accessed from there, or from Condmaster Ruby
via the Entity rules icon under the Online ribbon tab.
Rule environment and rule types

When working with Entity rules, understanding the concepts of Rule environment and Rule type is
important.
Rule environment defines where the rule will be processed:

l Server rules are processed by Condmaster Entity Server (CES), while
l Edge rules are processed by the measuring device rather than by the server.
Using Edge rules enables faster rule evaluation and decision-making because it takes place right at
the node, without first sending all data to the server for processing; this also saves server resources
shared by many devices. However, compared to Server rules, there are limitations as to what kinds of
actions can be triggered as a result of rule evaluation.
Edge rules can be applied to devices suitable for the types of resources required by the device. (Airius
sensors' specialty is to send measurement data, not to process data or save measurement results,
etc. and is therefore not possible to use with Edge rules.)
Rule type defines what type of event should trigger the rule, which in turn determines what kind of
data are available when configuring it. The available options are all data-driven events, happening
either in the condition monitoring systems handled in Condmaster, or in other systems with which
Condmaster can communicate.
Rule Rule
Event triggering the rule
environment types
Server rule API CES server receives an API call to run this specific rule
Global value
Parameter set up as a global value in Condmaster changes
change
An event set up to happen with a certain interval occurs
Interval
(for example, every 30 minutes)
Measurement CES saves new result from measuring assignment, com-
result ponent, machine, measuring device, or measuring point
Scheduled A scheduled event occurs
Signal Quality test A signal quality test has been run on the measuring device
Edge rule* - -
*Edge rules will be released in an upcoming revision.
The CES server, or an edge node, automatically “listens” for events matching the rule type from the
various devices and when they occur, initiates rule processing.
How Entity rules are built

Entity rules are built using different elements such as conditions, actions, and, where relevant, vari-
ables. Together, these elements provide extensive flexibility to create rules for customized, auto-
mated behaviors and integration.
The respective elements are found on separate tabs in the Entity rule window. On an overall level,
these tabs work as explained in the table below.
- 441 -
Tab does what?

General Conditions Actions Variables
Predefined system vari-
Define when to execute Define how to determine
Define what action(s) to ables or user defined
the rule “When event if rule condition(s) are
trigger after rule exe- variables to be used in a
xxx happens on entity met (using relational
cution flexible way when build-
yyy…” and logical operators)
ing rules
Rule type: what event
(s) trigger(s) rule exe-
cution? “xxx”
When TRUE: trigger xxx Can be applied in Condi-
Rule applies to: physical Evaluate if condition(s) tions
entity (measuring point, = TRUE condition(s) = When FALSE: create xxx
component, machine, FALSE Can be applied in
ALWAYS: send xxx Actions
measuring device) or
measuring assignment)
“yyy”
The Advanced tab contains advanced settings for the rule. At this time of writing, the settings regard
how often the rule going to be executed (see further below).
Adding an entity rule

Note: When adding entity rules, options available in dropdown lists will vary depending on choices
made in previous steps. In the text that follows, the following entity rule will be created: 'When a VEL
RMS value for measuring point x or x exceeds 2.3, an email should be sent.'
1. To create a new entity rule, click the ‘+’ sign in the bottom right part of the screen (A):
2. Name the rule (B).

3. Select the appropriate Rule environment (C); Server rule or Edge rule, see above. For our
example, we select Server rule.
4. Select the appropriate Rule type (D); i.e., what type of event that the CES server or edge
- 442 -
node should listen for. For our example, we select Measurement result.
5. Click CREATE (E). The rule now exists but has no conditions or actions tied to it.
To limit the number of events to listen for, the Rule applies to function is used, see below. NOTE:
While rules can be created and configured without selecting anything under Rule applies to, it is not
recommended due to, among other things, the potential load on the CES server.
The General tab

When you have created a new entity rule and selected its rule environment and type, the General
tab (A) is shown in the Edit rule window:
1. Click the ‘+’ sign under Rule applies to and select an alternative in the dropdown list (B). In
our example, we select Measuring points.
2. Under Relational mode (C), select an appropriate relation. Is one of means that entities selec-
ted in the next step are included, while Is not one of means the opposite.
3. In the dropdown list (D), select entities that should be included in the Is one of (or excluded,
Is not one of). In this example, the rule is applied to measuring points, and thus all measuring
points in the current database are displayed in the list. To include multiple measuring points in
the rule, click the down arrow after each selected measuring point to select from the dropdown
list again.
4. Click SAVE to save your selection of entities (in this example, measuring points), which is then
displayed under Rule applies to:
- 443 -
5. Click the Save icon in the upper right part of the screen (E) to save the selection under the cur-
rent rule.
At this stage, this rule would read something like:
"When the CES server saves a measuring result on measuring point I-000.00 OR measuring point I-
000.02, then <something not yet specified>…"
The Conditions tab

On the Conditions tab (A), conditions are added that are used to determine if rule condition(s) are
met using relational and logical operators:
1. To add conditions, click the ‘+’ sign under Edit conditions and select an alternative in the
dropdown list (B). For our example, Measurement value is selected.
2. Depending on the alternative selected in step 1, different additional settings are displayed in
the Add window in the right part of the screen (C). Using Measurement value in this example,
all standard symptoms and condition parameters in Condmaster are listed. Since we want to
apply the rule to a velocity RMS value, we select VEL from the list.
- 444 -
3. Under Relational mode (D), select an appropriate relation. For our example, we select
Greater than.
4. Select Static value or Functional value (E).
- A Static value would be applicable to our example, that the measurement result (Velocity)
should be greater than 2.3. This value is entered manually in the Value field.
- A Functional value can be useful when setting up rules such as ‘When the RPM for machine
A exceeds the RPM of machine B, …’ which is a value that will vary. For Functional value, you
select a value from the same list of alternatives as in step 1.
5. Click SAVE (F).

6. Add more conditions as necessary, depending on how you want to build your rule. In our
example, one condition is enough.
7. Click the Save icon in the upper right part of the screen (G) to save the selection under the
current rule.
See below for more information on the settings possible under Show advanced.
- 445 -
Advanced (optional)
Under Show advanced, it is possible to select a post-operation to be performed on this particular

value, such as rounding the value to one decimal place.
1. Click the ‘+’ sign belonging to Post operations and select an alternative from the menu (H).
In this case Utils > Round to is selected to be able to round the measurement value to one
decimal place (I).
After saving (J), add or delete post operations as required. It is possible to decide which order they
should be executed by using the arrows.
- 446 -
Web request
Many of the condition functions such as Date and Time is more or less self-explanatory. However, the
web request functionality may need to be explained in more detail.
The Web request function is used to retrieve a scalar value from another system via a web request.
For example, it can be used to retrieve data from another API (for example, to retrieve the outdoor
temperature from YR (a weather forecast service) via an API for a specific position that is saved for
each measurement).
1. Enter the URL (A) that the web request function should call.
2. Response type (B) is set to JSON as default, meaning that a JSON object is expected in
return. The Text alternative means that the answer is expected to be a value that can be con-
verted to a numeric value. The Status code alternative means that the HTTP status code is
fetched as an answer (usually 200 for GET, for example).
3. Value JSON Path (C) is used to retrieve the value from the object. See JSON Path in the API
documentation in the CES Admin Portal.
4. Authentication (D) is set to None by default but can be changed if account information (user-
name/password) is needed when calling the server.
5. Enter the HTTP Headers (E) (optional) to be included in the request.
6. Select TEST (F) to perform the request and check what value is returned.
- 447 -
The Actions tab

On the Actions tab (A), you decide what is going to happen in relation to the condition, for example,
invoke something in a different system or notify a person or system of something:
1. To add an action, select the ‘+’ sign in the top right part of the screen and select an alternative
in the dropdown list (B).
l Alert – add, delete or update an alert on the alert list
l Devices – action related to a device, for example set a status output for Intellinova Parallel EN
l Email – send an email to a recipient
l Execute rule – execute another rule
l Global value – send a global value
l Shared variable – set a shared variable
l Webhook – send a value to another system
Each of these actions are described in detail below. To learn about the email example in our rule, see
the Email action below.
- 448 -
Alert
Alerts are added to the Alert list in Condmaster, see "18.7 Alerts" on page 516 to learn more.
1. Execute on is set to Fulfilled (C) by default but can be changed in the dropdown list as
required.
When the rule is executed, the conditions are either TRUE or FALSE. If the conditions are TRUE,
the Fulfilled actions will be executed. If the conditions are FALSE, the Not fulfilled action(s)
will be executed. For the alternative Always, the action is always executed regardless of
whether the conditions are true or false. Error can occur when, for example, Mathematical
expression has been selected and this expression cannot be executed for some reason (for
example, division by zero, reference to a variable that no longer exists, etc.).
2. Enter a Description (D) of the action.
3. Enter the Alert text (E) that should be shown in the Alert list.
If you want to include a measurement value in the alert list, you need to add a variable under
the Variables tab, see below.
4. Deduplication informs how many times (x1, x2, etc.) the alert is deduplicated. Deduplication
prevents the occurrence of copies of the same alert, which keeps the alert list short and easy to
work with. Insert a Deduplication identifier (F) to get an updated number in the altert list
each time the alert is generated. For example, you could insert "Alert_measuringpointID" for a
measuring point alert (but change the text "measuringpointID" to a unique measuring point
identification number).
5. By default, Priority (G) is set to Informational but can be changed as required from the drop-
down list.
6. By default, Status (H) is set to New but can be changed as required from the dropdown list.
7. In the field Tags (I), it is possible to enter one or several tags so that the user can more easily
- 449 -
categorize the alert (the tags are accessible via the CES API).
8. Select SAVE (J).
Alert - Delete alert
required.
3. The Deduplication identifier (E) entered for the alert that should be deleted must be written
exactly in the same way in this field (otherwise, it will not be deleted).
4. Select SAVE (F).
Alert - DSS: Update alerts
required.
- 450 -

3. Min priority (E) is set to Medium as default and works as follows; when the rule is executed
(for measurement results), it checks the alert level and if there is there an alert.
YES and medium or higher: the deduplication number is increased in the alert list.
YES and lower than medium: the deduplication number is deleted from the alert list.
NO: creates an alert if it is medium of higher and is shown in the alert list.
4. Update level (F) is set to Assignment by default. If there is any symptom that has medium
or higher, one alert is created. When no symptom has medium or higher, any alerts are
removed. The purpose is to reduce the number of alerts. The option Symptom means that
alerts can be created on symptom level, i.e. one alert for each symptom (one alert for BPFO,
one alert for BPFI, etc.).
5. Select SAVE (G).
Devices - Force measurement
The action type Force measurement is used when the rule, after execution, should start a meas-
urement on a measuring assignment. It only works for Intellinova Parallel EN units.
required.
When the rule is executed, the conditions are either TRUE or FALSE. If the conditions are TRUE,
the Fulfilled actions will be executed. If the conditions are FALSE, the Not fulfilled action(s)
will be executed. For the alternative Always, the action is always executed regardless of
whether the conditions are true or false. Error can occur when, for example, Mathematical
expression has been selected and this expression cannot be executed for some reason (for
example, division by zero, reference to a variable that no longer exists, etc.).

3. Enter Technique (Tech) ID (E) for the measuring assignment that should be measured. The
TechID is found in Condmaster Ruby, at the bottom of the Measuring Point Data window for
the measuring assignment.
4. Click SAVE (F).
5. Click the Save icon (G) in the upper right part of the screen to save the selection under the
current rule.
- 451 -
Devices - Intellinova Parallel EN: Status output
This action type is used to set a status output (digital output) on an Intellinova Parallel EN unit. If the
function used returns 0, the status output is inactivated - for all other values the status output is activ-
ated.
required.
3. Select an Intellinova Parallel EN measuring device (E). Leave this field blank to use the
device used to acquire the measurement result (this applies when the rule type measurement
result has been selected when the rule was created).
4. Select Interface number from the dropdown list (F).
5. Status output value is set to Activate output (G) as default, but can be set to Deactivate
output or Custom. When Custom is selected, more options are available, see example
below.
6. Select Save (H).
For example, to toggle the status output between active and inactive, the Binary NOT function can be
used. Binary NOT returns the value 1 if the function it evaluates return 0; otherwise, it returns 0.
When using Binary NOT, the same measuring device must be selected, see screenshot and more
information below.
- 452 -
To toggle the status output, select Custom as Status output value (G). As value, select Devices >
Intellinova Parallel EN (H) and point out the status output you want to fetch the current status
from (I and J), use the same settings as entered in (E, measuring device) and (F, Interface number).
This will set the status output to the same state as it already has. To invert the value, select Show
advanced (K), select the '+' sign and then Utils > Binary NOT as Post-operation (L).
- 453 -
Devices - Moxa ioLogik E1200 Series
This action type has support for setting values on MOXA ioLogik E1200 Series modules. These mod-
ules have different configurations with respect to analog inputs, analog outputs, digital inputs, digital
outputs, relay channels, RTD (Resistance Temperature Device) channels, and thermocouple chan-
nels. With this functionality, it is possible to, for example, set an analog output via Entity rules and
then use Modbus TCP (or MOXA AOPC, MXIO) protocol to read this value.
Note: It is assumed that the MOXA ioLogik E12XX module used has been set up and configured
according to its user manual.
required.
3. Enter the IP or Hostname for the MOXA device (E).
4. Select Interface from the dropdown list (F). Depending on the MOXA unit type, the options in
the list can differ.
5. Select Slot (G) and Index (I/O Number)(H).
6. Select Value parameter (I) from the dropdown list. Options in the list depends on the selec-
ted Interface in step 4.
The FETCH CURRENT VALUE button can be used to test to read the value from the MOXA
device.
7. Select Value (J) from the dropdown list to set to the MOXA device.
8. Select Save (K).
- 454 -
Email
required.
3. Enter Recipient (E) email address.
4. Enter an email Subject (F).
5. In the field Body (G), enter the text that you want to send in the email.
Note: If you want to include, for example, a measurement value, you need to create a variable
under the Variables tab, see below. When the variable has been created, it can be inserted
using the Function symbol (∑) (H). This opens a list of objects that is possible to insert. It is
also possible to use Rule properties to include, for example, a measuring point name and
measuring point number. Available rule properties will vary depending on the rule type chosen
when you created the rule.
6. Use the SEND TEST EMAIL button (I) to check if the email reaches the recipient. If an error
occurs, check the email settings in CES Admin Portal or Condmaster Ruby, depending on your
set up. Please note that the variables (or rule properties, etc.) will not show any values in the
test email because the rule has not been executed.
7. Click SAVE (J).
- 455 -
Execute rule
The action type Execute rule is used to execute another rule. It is only applicable to the API rule
type.
required.
3. Select an Entity rule (E) to be executed when the rule you are currently editing, is executed.
4. Click SAVE (J).
- 456 -
Global value
The Global value action is used to set a global value, which in turn often is used to signal something
to a measurement system (or dashboard, etc.). It can, for example, be used to control various
Intellinova Parallel EN measurement units or to trigger measurements in a unit (a condition para-
meter that is set to "listen for" a global value change).
It is recommended to only use global values of type 'API' (but there is nothing technical that prevents
other types of global values from being used).
The global value must have been registered in Condmaster Ruby in advance, see "15.29 Global val-
ues for Intellinova Parallel EN" on page 372 for information on how to set up global values.
required.
3. Select a Global value (= a global value that has been set up in Condmaster Ruby in advance)
by selecting one from the list) (E).
4. The CURRENT VALUE button (F) gets the current global value and can be used as a test.
5. Valid seconds (G) is set to 0 (= ‘infinite’) by default but can be changed by entering another
value.
6. Select Value (H). Please note that the following steps might differ depending on which type of
value selected. For this example (not related to the rule about the VEL RMS value being greater
than 2.3), we select Static value.
7. Input a Value (I) for the static value.
8. Click SAVE (J).
In the example, the global value is set to be updated with the static value 100.
- 457 -
Shared variable
The Shared variable action type is used to set a value for a shared variable when the rule is
executed.
required.
3. Select a Shared variable (E) from the dropdown list. See the Shared variables section to
learn how shared variables are created.
4. The Update type (F) is set to Fixed value by default but can be changed as required.
The Incremented option means that the Shared variable value can be set to be increased by,
for example a static value. The corresponding applies to the Decremented option, which
means that the shared variable value can be set to be decreased by a value.
5. Select Value (G) for example a Static value, and enter a Value (H).
6. Select Save (I).
In this example, the shared variable varShared2 is set to 123 when the rule is executed and fulfilled.
- 458 -
Webhooks
A Webhook (also called a web callback or HTTP push API) is a way to provide other applications with
real-time information. When selecting Webhook as action, this means for example that the value can
be sent to another system.
1. To add a Webhook action, see steps 1 to 2 above for (C) and (D).
2. Enter the URL(E) to the system that should present the value.
3. Enter the appropriate behavior for the webhook. It can be an API command, or you can add a
variable (F). To fetch data from CES, select a HTTP/HTTPS GET request.
4. Click to add Headers (G).
5. Click to enter the data under PostData (H) that should be posted in the other system.
Note: If you want to include, for example, a measurement value, you need to create a variable
under the Variables tab, see below. When the variable has been created, it can be inserted
using the Function symbol (∑). This opens a list of objects that is possible to insert, variables
and, for example Shared texts (if there are any created).
6. Click SAVE (I).
- 459 -
The Variables tab

On the Variables tab (A), variables are added. They are mainly used to send information in for
example emails (but they can also be used in conditions):
1. To add a Variable, click the ‘+’ sign in the upper right part of the screen and select an altern-
ative in the dropdown list (B). In our example, we use Round to to be able to round the meas-
urement result to one decimal place, and then present the value in an email.
Note: Depending on the alternative selected, the following steps will vary depending on its func-
tionality.
2. Name the variable (C).

3. Enter the number of Digits (decimals) to round to.
4. Select a value for which the Round to function should be used. In our example, we select
Measurement value (because we want to apply the variable to our VEL RMS value).
5. Select type of measurement value from the list. In our example, we select VEL (velocity).
6. Click SAVE.
7. Click the Save icon in the upper right part of the screen (H) to save the variable.
To insert a variable in, for example, the body of an Email action: go to the Actions tab, create or edit
an Email action, click the Function symbol in the body field and select a variable from the list:
- 460 -
The list of objects possible to insert are variables, shared variables, shared texts, and rule properties.
Rule properties are used to include, for example, a measuring point name and measuring point
number. Available rule properties will vary depending on the rule type chosen when you created the
rule.
The Advanced tab

The Advanced tab (A) contains advanced settings.
In the General tab, the Rule applies to setting regards for WHAT is the rule going to be executed.
In the Advanced tab, the Rule frequency type setting regards WHEN (or how often) is the rule
going to be executed.
1. To change the Rule frequency type, select an alternative from the dropdown list (B).
As default, Rule frequency type is set to Every time, meaning that the rule is executed
every time. In our example, every time a measurement result is saved to the database. If you
do not want the rule to execute every time, you can for example select Only first time (per-
haps you want to send an email only the first time the value pass 2.3, not every time). For the
alternative Met number of times in interval, you can for example set '10 times and 25
seconds' which means that the condition must be met 10 times during a period of 25 seconds
- 461 -
in order for the action to be executed. For the alternative Persists, you can set that the con-
dition must be met during 25 seconds in order for the action to be executed (this can be useful
if you want to avoid single and short (in duration) random values).
2. Remember to click the Save icon in the upper right part of the screen (C) to save the changes
for the current rule.
The History tab

The History tab (A) contains a history of the executions performed for the rule.
Select a row (B) to get more information about the rule execution.
- 462 -
Shared variables
A variable can be created and used individually per rule (under Rules and the variables tab), but a
Shared variable is created 'outside' a rule and can therefore be reused amongst rules.
1. To create a Shared variable, click the ‘+’ sign in the bottom right part of the screen (A).
2. Name (B) the shared variable.
3. Enter a value (C).
4. When ready, select SAVE (D).
Shared variable is also available as a Function and as an Action type (see The Action tab section
above).
- 463 -
Shared texts
Shared texts are, like Shared variables, possible to reuse amongst rules. A Shared variable is numer-
ical, and a Shared text is text.
1. To create a Shared text, click the ‘+’ sign in the bottom right part of the screen (A).
2. Name (B) the shared text.
3. Enter a text (C).
4. When ready, select SAVE (D).
In this example, the shared text MyServer with the value http://myserver.com was created. If
the server name is used as a property in actions (in, for example, Webhooks) for several rules and
needs to be updated, you only need to change it here, under Shared texts.
- 464 -
16.23 Condmaster.NET
The Condmaster.NET web application and downloadable app for iOS and Android can now be used
to access Condmaster Ruby data via web browsers on all types of devices.
It presents an intuitive and easily accessible overview of color evaluation and alerts and offers basic
analysis functionality. Application-specific, customized dashboards to visualize and monitor process
data can be created on request. Furthermore, the Plant Performer function and live display of online
measuring units are now part of Condmaster.NET.
To learn more, see the built-in context sensitive help in Condmaster.NET accessible from the question
mark symbol in the upper right corner of the screen, or see Condmaster.NET User Guide, document
no. 72304.
You can access Condmaster.NET via the built-in web browser in Condmaster Ruby or open Cond-
master.NET in an external web browser using the following address:
http://{CESSERVERNAME}:PortNo. (e.g.: http://127.0.0.1:7890)
- 465 -
16.24 Importing measurement results

Via the CES API, import of measuring results from other systems or units can be done. Initially, the
vibration and user-defined measurement techniques are supported. While measurement assignment
setting restrictions apply, vibration data from almost any source can be imported into Condmaster.
Once in Condmaster, the system handles this data in the same way as data from SPM measurement
systems. That means, among other things, that the imported data can be analyzed using Cond-
master's all advanced features, Colored Spectrum Overview, etc. To enable the import of measuring
results from other systems or units via the API, a Virtual Online Unit needs to be set up*.
The overall steps for importing measuring results into Condmaster:
1. Set up a Virtual Online Unit in Condmaster Ruby (or under the Online module in Cond-
master.NET)*.
2. Set up measuring assignments defining the imported data in Condmaster Ruby:
l use the measuring technique User defined for import of scalar values
l use the measuring technique Vibration for import of vibration values
3. Import measurement results.
Setting up a Virtual Online Unit in Condmaster Ruby

A recommendation for intuitive visual display is to create a Virtual Online Unit that corresponds to a
physical device. (It is possible to create all measurement assignments on only one unit, but it is not
recommended.)
*Note: A Virtual Online Unit is recommended but not required for the import of scalar values.
1. In Condmaster, go to Online > Online System Overview (A) (in the ribbon bar or via the
right panel menu).
2. Click the REGISTERED UNITS button (B) and then click NEW (C).
- 466 -
3. Select Virtual Online Unit (D) and click NEXT (E).
For the Virtual Online Unit, there are a number of vibration inputs, analog inputs, and RPM inputs that
are more of a ‘summary importance’, they do not really have to match reality.
4. Name (F) the unit and click CES UNIT CONFIGURATION (G).

5. Enter a Serial number (H). The serial number should consist of 7 characters (A-Z and
numeric characters 0-9 can be used).
6. Enter the URL or IP address (I) that this unit will use to access and communicate with CES.
7. Click SAVE CONFIGURATION TO CES (J) to send this information to CES (required in order
to synchronize the information between Condmaster and CES).
8. Click CLOSE (K) to close the CES Unit Configuration window, and then click SAVE (L) to save
and exit the Online System unit settings.
Set up measuring assignments defining the imported data

NOTE: It is assumed that components and measuring points have been added as necessary, see "3.1
Creating machines and components" on page 40 and "4.1 Creating a measuring point" on page 45.
Scalar values
For import of scalar values, use the measuring technique User defined.
- 467 -
1. In the Measuring Point Data window, select the measuring technique User defined (A) and
click ADD (B).
2. Select Online (C) as instrument for User defined and click OK (D).
3. Go to the Online tab (E), click the '…' button by Address (F), expand a Virtual Online Unit,
expand Analog input, select a channel (G) (it does not matter which channel number) and
click OK (H).
- 468 -
4. Go to the Settings tab (I), select type of Incoming signal (J) (which type is not important,
but needed to be able to save the measuring assignment) and enter a Lowest value and a
Highest value (K).
5. Enter a Unit (L) (needed to be able to save the measuring assignment).
6. Go to the Online Advanced tab (M) for advanced settings.

l Conditions (N) are checked during the import, see "15.26 Measurement conditions for
Intellinova Parallel EN" on page 366 for information on how to set up a condition. Please
note that for Virtual Online Unit, conditions apply to global values only.
l Filtering of results (O) can for example be used to limit the amount of values stored
- 469 -
7. When all settings have been made, select SAVE in the lower left corner of the Measuring
Point Data window.
Vibration values
For import of vibration values, use the measuring technique Vibration.
1. In the Measuring Point Data window, select the measuring technique Vibration (A) and
click ADD (B).
2. Select Online (C) as instrument for Vibration and click OK (D).
3. Go to the Online tab (E) , click the '…' button by Address (F), expand a Virtual Online Unit,
expand VIB, select a channel (G) (it does not matter which channel number) and click OK
- 470 -
(H).
4. Go to the Settings tab (I) and select Time signal unit (J)(Disp, Vel, Acc). It must match the
imported time signal.
5. For Spectrum unit (K), select which unit (Disp, Vel, Acc) to display in the spectrum. (Spec-
trum is by default set to be calculated during import, and the import calculates the FFT accord-
ing to the set unit). However, it is possible to choose to import an already calculated FFT. In
this case, the Spectrum unit must match the imported FFT, and the number of lines (Lines in
spectrum) must match.
6. Order Tracking (L) is not supported and must be set to No.
7. For Upper frequency (M), the frequency unit must be in Hz (Orders is not supported).
Otherwise, the data do not have to match the measurement assignment settings when it comes to
sampling frequencies and sampling rates; our advanced algorithms automatically decimate and trans-
form the imported data into the correct format.
- 471 -
8. Under the Online tab (N) and Machine operating conditions, it is possible to link imported
vibration data to defined process parameters, see "15.13 Machine operating conditions" on
9. Go to the Online Advanced (O) tab for advanced settings.

l Conditions (P) are checked during the import, see "15.26 Measurement conditions for
Intellinova Parallel EN" on page 366 for information on how to set up a condition. Please
note that for Virtual Online Unit, conditions apply to global values only.
l Filtering of results (Q) can for example be used to limit the amount of values stored
10. When all settings have been made, select SAVE in the lower left corner of the Measuring
Point Data window.
- 472 -
Import measurement results

Measurement result data is imported via the CES API. The first section below describes data import of
scalar values via Condmaster.NET, and the second section provides details on how to use the API to
import scalar values and vibration values.
Data import via Condmaster.NET

To import scalar values , there is an import function available in Condmaster.NET . This feature
allows you to import scalar values from Excel files.
1. Go to the Online tab and select the Condmaster.NET icon (A) (or go to http://{CES_
SERVER:Port.no}).
2. In Condmaster.NET, go to Settings (B) and select Data import (C).
- 473 -
3. At the Data import page, select Upload file (D) and select an excel file to be imported.
4. Under Select assignments (E), select the measuring assignment(s) to import the values to.
(One measuring point have support for two User defined measurement assignments; User
defined 1 and User defined 2.)
5. Under Select data columns, select which data columns to import from the file.
By default, every data column has the value Ignore. One of the columns must be set to
Date/Time (F) and one (or two if you import to two User defined measuring assignments) of
the columns must contain values to be imported. In the example, one User defined measuring
assignment (Pressure) is imported (G). Columns that should not be imported must have the
value Ignore.
6. Select Import data (H). A ‘Data import done´ message should be shown if the import suc-
ceeded.
The imported data can be analyzed using Condmaster's all advanced features, Colored Spectrum
Overview, etc.
To view the imported data, you can, for example, mark the measuring point in Graphical Overview
and select Measuring results to view the imported measuring results:
- 474 -
Data import via CES API

Measurement results are imported via the following endpoint:
http://server:7890/api/v1/databases/{database_name}/import/measurements
The same endpoint is used for all (two) types of measurement results. Which type of measurement
result is imported depends on how the JSON document is formatted. The two types of measurement
results supported are Scalar and Vibration. If the JSON document has "Type": "scalar" means that
it is a scalar value, etc.
The two objects (measurement result types) are documented in Swagger (see http://server-
:7890/apidoc/):
• TcesImportMeasurement_Scalar
• TcesImportMeasurement_Vibration
- 475 -
Scalar
TechID = the measurement assignment to import to. Ends with _9 or _10.
Measurements = one or more scalar values to import. DateTime = timestamp in ISO 8601 format
(the same format that all timestamps in the API use).
UID = Optional. Unique identifier for a measurement result. This is returned in the response from the
server, along with the obtained id for the measurement result.
Alt1 = Scalar value with _9
Alt2 = Scalar value with _10 (not included in the example above)
- 476 -
Vibration
- 477 -
Vibration is a more complex object than the Scalar one. For information on each parameter, see doc-
umentation in Swagger at http://server:7890/apidoc/ for TcesImportMeasurement_Vibration.
Response
A response is received from the server (example of a response obtained from a scalar value):
"UID": "{845DC164-B6F4-45D7-880E-786B1CF044B4}",
Same as stated at the call. If not specified, a new one is created.
"IntNo": 26431,
Measurement result number in Condmaster.
"Result": 1
Whether the measurement was read or not (1 = true, check in Swagger).
Log: Log from the processing of the call.
Now the measurement result is available in Condmaster and can be handled like other measurement
results.
- 478 -
16.25 CES API
The Condmaster Entity Server API, or CES API for short, is our REST API.
It can be seen as an interface providing a well-established and easy-to-implement way to share data
between systems. Using the CES API, other devices or process control systems can retrieve Cond-
master data for further processing or analysis. It is also possible to import data into Condmaster, see
"16.24 Importing measurement results" on page 466.
Many tools have built-in support for REST APIs and JSON-data. For example, Excel, Power BI, or
Node-RED can be used to fetch data directly from the API.
For more information on how to work with the CES API, please refer to:
l The API chapter introducing the CES API and containing information about basic data types,
command examples, how to work with the API, etc. found in the CES Admin Portal User Guide,
document no. 72302 available on your installation media or at
http(s)://[address to the CES server and port number]/help/admin/en/?#G-API/API.htm
l Open API 3.0 documentation:

http(s)://[address to the CES server and port number]/api/v1/openapi.json
l Swagger – built-in documentation reader and API tester:

http(s)://[address to the CES server and port number]/apidoc/
- 479 -
17. Plant Performer
17. Plant Performer

17.1 Introduction to Plant Performer
Plant Performer is a statistical module in Condmaster, the purpose of which is to compile and visu-
alize statistics relating to the economic impact of your condition-based maintenance program for dis-
play, evaluation, and printing in Condmaster.NET . The module provides the opportunity to enter
information necessary to follow up on the cost savings resulting from planned maintenance activities.
The module also provides the opportunity to monitor technical KPIs, such as vibration levels, unbal-
ance and alignment statistics, lubrication condition, or MTBF; follow up on prewarning times and plan-
ning times; and monitor various long-term trends from a condition-based maintenance perspective.
The economic KPIs used in Condmaster/Plant Performer are widely accepted, standard financial meas-
ures in the OEE/TEEP area, while the technical KPIs can be user-defined to best suit your own busi-
ness.
Plant Performer is a useful tool to demonstrate the benefits of condition monitoring and communicate
its technical and economic impact to all levels of the organization. Justifying investments in condition
monitoring equipment is easier when it can be shown that condition-based maintenance is not merely
about avoiding breakdowns, but also long-term work to keep machines productive for years after
depreciation.
The function is Industry 4.0 compatible in that it can export data/statistics to other systems by means
of an application programming interface (API). There is also the capacity to import and export stat-
istics from an unlimited number of Condmaster databases – such as from other divisions, plants, or
an entire group – for easy comparison of data.
See below for more information about "17.2 Prerequisites" on the next page and important steps to
follow when working with Plant Performer.
- 480 -
17. Plant Performer
17.2 Prerequisites
To provide meaningful information, maintenance performance data should be relevant, accurate and
consistent. The Plant Performer economic and technical KPI statistics shown in Condmaster.NET are
based on information specified in Condmaster. To ensure accurate and complete data for the stat-
istical calculations in Plant Performer, it is important to follow the steps below.
l Set up a machine type register (see section "17.3 Creating and using the machine type
register" on the next page), and
l Ensure that each measuring point is configured with one or more machine types (see section
"17.3 Creating and using the machine type register" on the next page)
l Decide which economy-related key performance indicators (KPIs) to monitor (e.g. Loss of Con-
tribution, Waste production, etc. (see section Selecting economic KPIs in "17.4 Working with
economic KPIs" on page 484)
l Create a register of typical maintenance and repair jobs, and enter the agreed-upon minimum
savings that occur when they are carried out during planned stops (as opposed to the cost of
unplanned maintenance; see section Entering minimum savings for maintenance actions in
"17.4 Working with economic KPIs" on page 484)
l Whenever corrective maintenance has been carried out (whether planned, unplanned or due to
machine breakdown), ensure that a corrective maintenance comment is entered on the meas-
uring point, specifying under each of the economic KPIs the minimum savings made due to the
individual planned maintenance action (see section "17.5 Working with technical KPIs" on
page 490).
Following these steps and maintaining a routine regarding the use of corrective maintenance com-
ments will help ensure that you get the most out of the Plant Performer function.
Once the Plant Performer function has been set up and the basic data entered in Condmaster, the stat-
istical data can be viewed in the Plant Performer module in Condmaster.NET, see "17.8 Viewing Plant
Performer statistics" on page 499. Viewing and working with Plant Performer data in CES does not
require expert Condmaster knowledge.
- 481 -
17. Plant Performer
17.3 Creating and using the machine type register

The purpose of the machine type register is to enable the compilation and filtering of Plant Per-
former statistics based on machine type. The register should therefore be set up to contain the types
of machinery that you wish to monitor (e.g. in terms of database statistics such as the number of
measuring points on fans, the number of electrical motors in green condition, or economy statistics
such as the total savings from condition-based maintenance work on all gearboxes).
Giving some thought to the structure and content of your machine type register is a worthwhile effort.
A well-thought-out machine type register – and consistent use of machine types at measuring point
level – creates optimal filtering capabilities in Plant Performer (see below).
To create the machine type register, follow these steps:
1. In the right panel menu, select Registers > Machine type register.
2. Click the NEW button to input new machine types:
NOTE: Be sure to use the exact same terminology, spelling, and upper/lower case for your machine
types across all your databases, or the comparison of Plant Performer data between databases will be
unreliable.
When using the filtering function in Plant Performer, multiple filters can be combined for a customized
selection of data. A few examples using the machine type register in the example screenshot above:
- Filter out all <500 kW ABB motors with planetary gearbox and criticality rating A
- Filter out all centrifugal fans with criticality rating B
- Filter out all centrifugal and screw pumps
- 482 -
17. Plant Performer
3. Ensure that all your measuring points are configured with one or more machine types (A)
from the machine type register (B):
TIP : To input machine type (s) on multiple existing measuring points (‘Multi- change’), open the
Meas-uring Point Tree and press the CTRL button on your keyboard while left clicking on each
measuring point of interest; then right click and select Edit. The Measuring Point Data window
opens, with all the selected measuring points displayed on individual tabs in the lower right corner
and with arrow buttons for toggling between them.
- 483 -
17. Plant Performer
17.4 Working with economic KPIs

The economical statistics in Plant Performer show estimated savings gained by doing corrective main-
tenance during scheduled stops. Through such planned activities, costs for corrective actions can be
minimized, avoiding breakdown of machinery and optimizing productivity. Some actions will also
improve the running condition of the machinery, which means longer lifetime.
17.4.1 Selecting economic KPIs

To enable economic follow-up, the first step is to determine which economic KPIs associated with
planned maintenance should be monitored for your plant. Ideally, these should be agreed upon by
the Maintenance Manager and the Head of Production. At a later stage, a register of corrective main-
tenance actions will be set up, along with the minimum savings that result when these activities are
carried out during planned stops (see section 17.4.2 'Creating a register of corrective maintenance
actions with minimum savings'). The economic KPIs selected in this section will be calculated for each
of the maintenance measures.
1. Under the right panel menu, go to System > Settings and select the Plant Performer tab
(A) (or navigate via System > Settings in the ribbon bar):
2. Select the KPIs that you want to monitor by ticking/unticking the checkboxes (B) under Key
Performance Indicators. These KPIs are fixed and therefore cannot be removed, only deac-
tivated. Two additional fields are available which can be user defined (C), should you require
follow-up on further metrics. Some definitions:
- Direct maintenance costs: Savings on costs associated directly to the maintenance activities,
including internal expenses required to carry out maintenance functions, such as labor, tools,
spare parts, training, etc., and any other expenses that are directly related to maintenance.
Repair work done in a planned manner drastically reduces the total time for the replacement
(labor costs are lowered because of less overtime etc., and spare parts, special tools, lifting
gear, working platforms etc. can be ordered well in advance at mini-mum costs).
- Production time: Estimated time saved by doing corrective actions in a planned manner. Jobs
done during planned production stops benefits availability.
- 484 -
17. Plant Performer
- Waste production/Reworking costs are indirect maintenance costs, generated e.g. due to lack
of maintenance or inadequate/unsuccessful maintenance. When breakdowns or unplanned
events occur, product quality will often be negatively affected. The stopping and starting of pro-
duction processes normally implicates quality losses. Avoiding such stops is money saved.
- Loss of contribution: Estimated savings in increased production through avoiding or short-

ening a stop. Loss of contribution (loss of revenue) is calculated as contribution per hour (sales
price of the product – production cost). Total savings in LOC is the contribution per hour * the
saved time.
- Costs for Secondary Damage: When a component can be replaced prior to breakdown, sec-
ondary damage on other components such as shaft, bearing housing, gears, impellers etc. can
be avoided.
3. For each of the performance indicators to be used, click the corresponding row in the Unit
column (D) and enter an appropriate unit of measurement (usually in time, energy, or mon-
etary units).
NOTE: Be sure to input the exact same names for extra fields, including spelling and upper/lower
case, and the exact same units for the performance indicators across all your databases, or the com-
parison of economic data between databases will be of no use.
4. Click OK to save the settings and close the Settings form.
In Plant Performer, costs incurred as a result of unplanned maintenance actions are shown as debit
entries (i.e. negative amounts), while savings thanks to planned maintenance are positive.
- 485 -
17. Plant Performer
17.4.2 Creating a register of corrective maintenance actions with minimum savings

In this step, the standard minimum savings for typical maintenance activities are entered.
Since the exact savings for a given maintenance measure are difficult to estimate, it is recommended
that the numbers entered in the Corrective Maintenance Predefined Register (see below) are
kept on an agreed-upon minimum level. For instance, if everyone agrees that bearing replacement
may save up to $52,000, but generally at least $35,000, then the lower amount should be input in
Condmaster.
1. In the right panel menu, select Registers > Corrective maintenance predefined register.
The Corrective Maintenance Predefined Register window opens, displaying a table with
the economic KPIs selected in section 17.4.1 ('Selecting economic KPIs') as column heads.
NOTE: To ensure that any existing data are not altered or deleted by mistake – potentially
causing erroneous Plant Performer statistics – the window opens in View mode (A) by default.
To make changes, click the EDIT button (B).
2. Click NEW (C) to add typical corrective maintenance activities (e.g. bearing replacement, lub-
rication, alignment, lubricant renewal, balancing, cleaning, pump replacement, etc.):
- 486 -
17. Plant Performer
3. Complete each new entry by specifying the minimum savings occurring in conjunction with this
type of planned maintenance action in the respective KPI column:
NOTE: The amounts entered here will be used as the standard minimum savings. In conjunc-tion
with entering corrective maintenance comments (see section 17.4.3 ' Entering maintenance com-
ments for economic follow-up'), these amounts can be changed if the actual savings deviate sig-
nificantly from the default values.
4. Click SAVE.
- 487 -
17. Plant Performer
17.4.3 Using corrective maintenance comments for economic follow-up

When corrective maintenance has been carried out on a machine (whether planned, unplanned, or
due to machine breakdown), make sure to add a comment to the measuring point, stating whether
the activity was planned or not, and what was carried out. If necessary, the standard minimum sav-
ings that were entered in the Corrective Maintenance Predefined Register (see section 17.4.2
'Creating a register of corrective maintenance actions with minimum savings') can be changed here
to better reflect the actual amounts saved in each individual situation.
1. In the Graphic Evaluation window, right-click in the narrow white area just below the appro-
priate measuring result/point in time in a graph (you may have to zoom in to find the right
spot) and select Add new comment.
2. In the New Comment window, select an appropriate comment and click OK.
3. Under Corrective maintenance in the Comment Data window, select Yes (A).
4. Under Type of activity (B), select the appropriate option:
The ’Planned’ option results in positive amounts in Plant Performer, while ’Unplanned’ and ‘Break-
down’ will be shown as negative values.
5. Under Predefined values, the maintenance activities input in the Corrective Maintenance
Pre-defined Register (see section 17.4.2 'Creating a register of corrective main-
tenance actions with minimum savings') are listed (C). Select the appropriate option from
the list.
- 488 -
17. Plant Performer
6. Next, review the standard minimum savings (D). If the amounts deviate significantly from the
standard numbers, they can be edited.
7. Click SAVE to save the corrective maintenance comment and close the window.
- 489 -
17. Plant Performer
17.5 Working with technical KPIs

Technical KPIs should be quantifiable measures that facilitate defining and measuring progress to-
wards the goals of your maintenance organization. Calculated at regular time intervals, they can be
used for follow- up on various levels; e.g., for a machine type, a department, or an entire plant.
Examples include:
l Overall vibration level
l Number of fans in green condition
l Mean Time Between Failure
l Lubrication condition
l Comparison of long-term machine condition trends between production units
l Percent distribution of green-yellow-red condition for A-rated electric motors
l Comparison of overall readings between various gearbox suppliers
17.5.1 Creating KPIs

Technical KPIs are created in the form of “fictional” measuring points, the configuration of which is
applied to user-selected, actual folder(s) with measuring points (or entire databases). KPI measuring
points are user-defined, and in the same way as for other measuring points, Condmaster's graphics
functions are used to display the results of the KPI calculations. To create a technical KPI measuring
point:
1. Create a new measuring point.

2. From the Techniques list, add the KPI “technique”.
3. Under Quantity (A), change the default value (which is ‘KPI’) to something that clearly defines
what you are monitoring; in this example, we are creating a KPI to monitor overall vibration
levels (Velocity RMS). Enter the appropriate unit and display format (B).
- 490 -
17. Plant Performer
4. On the KPI tab (C), click the ADD button (D) in the Folders group to select a subset of folders
– or an entire database – from the measuring point tree in the Select folder window (E).
5. Still on the KPI tab (C), click the ADD button (F) in the Machine types group to select in the
Machine types window (G) what machine types should be included in trend computations for
this KPI. For example, you might want to be able to follow up on the overall vibration trend for
all gearboxes in the press section of a paper machine.
- 491 -
17. Plant Performer
6. Under Symptom values and condition parameters (H), the symptom values and condition
parameters available within your selection of folders and machine types are listed. Within par-
entheses after each option is the number of measuring points configured with that symptom
value or condition parameter. Select the appropriate one(s) for this KPI.
NOTE: If the dropdown list is not showing the expected content, the combination of Folders
and Machine types may be too narrow. Try a different selection.
- 492 -
17. Plant Performer
7. Under Value (I), select which value shall be used for calculation:
- ‘Average’: calculates the average value of each individual measuring point, sums them up
and shows the average.
- ‘Lowest’: takes the lowest value from each individual measuring point in the calcula-tion of
the KPI.
- ‘Highest: takes the highest value from each individual measuring point in the calcula-tion of
the KPI.
- ‘Latest: takes the latest value from each individual measuring point in the calculation of the
KPI.
8. Under Interval (J), select whether the KPI shall be calculated on a daily, weekly or month-ly
basis.
9. Tick the Re-build history results checkbox (K) to include historical values (i.e., the KPI cal-
culation will include all database values for your selection of folders). When left un-checked,
the calculation will include only values from the current day onwards.
- 493 -
17. Plant Performer
10. Finally, mark the measuring point number (H). Under Name (I), enter a descriptive name, e.g.
one that further explains the KPI.
11. Click SAVE to save your settings and close the window.
17.5.2 Using corrective maintenance comments for follow-up of technical KPIs

Technical KPI measuring points are like any other measuring point in that results (KPI calculations)
are displayed in the Graphics function in Condmaster. The trend graphs are updated in accordance
with the calculation interval set up on the KPI measuring point. Statistics based on these KPI cal-
culations are also available in the Plant Performer module in Condmaster.NET.
- 494 -
17. Plant Performer
For example: let’s say that you created a KPI measuring point to keep track of the overall alignment
situation for your pumps. Much like you would set a corrective maintenance comment on the measur-
ing point when alignment was carried out on a particular pump, you could do the similar in the graph
showing your overall alignment KPI, explaining that a drop in the trend levels was the effect of a
recent alignment campaign on pumps:
- 495 -
17. Plant Performer
17.6 Following up on prewarning and planning times

The Standard Comments register contains three predefined comments (A) which can be added to
graphs to obtain statistics on prewarning and planning times, respectively:
l WOP: Work Order Prewarning (default color red); add this comment to a graph when meas-
urements start to indicate problems (i.e., yellow/alert condition).
l WOI: Work Order Issued (default color yellow); add this comment in conjunction with issuing
a work order to rectify the problem.
l WOC: Work Order Closed (default color green); add this comment when the job is finished and
the work order has been closed.
The name and color of the WOP, WOI, and WOC comments (A) can be edited by marking the com-
ment in the Standard Comments window and clicking the EDIT button (B). The code (C), however,
cannot be changed by the user.
- 496 -
17. Plant Performer
In the Plant Performer statistics, prewarning time (D) is the time elapsed from when the machine
fault or problem was detected until the time when the work order is closed. The time between issuing
the work order and its completion is the planning time (E; see below).
- 497 -
17. Plant Performer
17.7 Mean Time Between Failure, MTBF

Mean Time Between Failure (MTBF) is the average time between repairable asset failures; i.e.,
conditions which place the asset out of service. Indicating the expected failure rate of equipment, this
measure is a good way to quantify asset reliability and availability. MTBF provides key insights into a
component’s expected performance and lifespan and can be used to determine the frequency of
inspection and planned maintenance activities.
MTBF only measures the time – typically in hours – that the asset is, in fact, up and running; it does
not include time spent waiting for repair; performing the repair; waiting to be put back into operation
after repair or preventive maintenance; or any other events keeping it out of operation after the fail-
ure itself.
In Plant Performer, MTBF statistics can be provided at machine type level. Follow these steps to set it
up in Condmaster:
1. In the right panel menu, select Registers > Standard comments (or navigate via Registers
> Standard comments in the ribbon bar).
2. In the Standard comments window, mark a comment and click EDIT (A).
3. Tick the MTBF checkbox (B).
4. Click SAVE to close the window.
- 498 -
17. Plant Performer
17.8 Viewing Plant Performer statistics

Plant Performer resides in Condmaster.NET and can be accessed from there, or from Condmaster
Ruby, learn more below.
17.8.1 Plant Performer statistics with filtered data

Go to Maintenance > Plant Performer in the ribbon bar:
This opens the Plant Performer module on database level, meaning that various performance data for
the current Condmaster database is presented.
Marking one or more nodes in the Graphical Overview or in the measuring point tree – such as folders
or components – before selecting Plant Performer as above, will cause that selection to automatically
be applied as a “predefined” filter when the module opens, and you will thus see statistics only for the
marked node(s). More filtering options (machines, machine types, measuring techniques, and cor-
rective maintenance comments) are available, enabling the selection to be narrowed down further.
With no nodes selected in Condmaster, the Plant Performer module will open displaying statistics for
the entire database.
- 499 -
17. Plant Performer
17.8.2 Plant Performer statistics access via Condmaster.NET

Go to Online > Condmaster.NET in the ribbon bar:
This opens Condmaster.NET via the built-in web browser in Condmaster Ruby. The Plant Performer
module is found in the main menu (see further below).
Another option is to open Condmaster.NET in an external web browser using the following address:
http://{CESSERVERNAME}:PortNo. (e.g.: http://127.0.0.1:7890)
Log in with your user credentials and open the Plant Performer module.
- 500 -
17. Plant Performer
To see the Plant Performer module, it must be enabled on your user account. To display Plant Per-
former data, the module must also be activated for one or more databases. If this is not the case, con-
tact to the system administrator.
17.8.3 Working with Plant Performer data

In the Plant Performer module, statistics can be viewed on various levels:
l The Plant Performer Overview level presents a compilation of data from all databases with
Plant Performer enabled.
l The Database level presents data for an individual database. Filtering options provide the
opportunity to narrow the data down to individual nodes, machine types, measuring tech-
niques, and/or corrective maintenance comments.
l At database level, Plant Performer offers the opportunity to drill down for a higher level of
detail for long-term trends, economy, machine condition, and database statistics/content.
For more information on how to work with Plant Performer data , please see the Plant Performer
chapter in the Condmaster.NET User Guide, document no. 72304.
- 501 -
18. Decision Support System

18.1 Introduction to Decision Support System
The Decision Support System (DSS) provides the user with predictions about machine damage, gen-
eral machine health.
DSS is highly automated and learns from past operations. It uses collected data to continuously
provide better predictions. With artificial intelligence, statistical analysis and other algorithms, the
DSS helps the user to make good and accurate decisions.
The DSS is not a function that can be toggled on or off, but a way of working with your condition mon-
itoring program by using the included features mentioned below.
In Condmaster Ruby, these standalone features form the DSS:

l Machine Builder – a tool for creating machines with its components, measuring points, meas-
uring assignments, and symptoms based on expertise of experienced condition monitoring
practitioners, see "18.3 Machine Builder" on page 504.
l Signal Quality Test – a way to determine whether the measurement signal is of good quality
or if there are deviations (for example ski slopes, bias problems) that merit further invest-
igation, see "18.4 Signal Quality Test" on page 505.
l Machine baseline – determines normal machine behavior and can be used to automatically
calculate deviations and potentially raise alerts for machine fault symptoms and condition para-
meters via Entity rules, see " 18.5 Machine baseline" on page 506.
l Health score – are calculated by applying mathematical algorithms to the collected baseline
data and is presented in blue-green-yellow-orange-red-dark red colors for a detailed eval-
uation, see "18.6 Health score" on page 515.
l Alerts – offers a flexible workflow and efficient management of maintenance tasks when equip-
ment condition and criticality rating calls for action, such as setting priority levels and status
indications on individual alerts, see "18.7 Alerts" on page 516.
l Entity rules (optional) – can be used to automatically invoke actions based on certain events,
for example, triggering a defined measurement type, sending an email, sending an API call,
creating an alert, etc., see "18.8 Entity rules" on page 518.
- 502 -
18.2 Getting started with Decision Support System
1. Create a machine with measuring points, measuring assignments and symptoms in Machine
Builder. See "18.3 Machine Builder" on the next page for further information.
2. Set up a Machine baseline by collecting measurement data during a training period when the
machine is in good mechanical condition and runs under normal operating conditions. It is
also possible to use historical data to establish a baseline. See " 18.5 Machine baseline" on
page 506 for further information.
3. Get AI-calculated machine health score automatically, and alerts via Entity rules to facilitate
the work with your condition monitoring program. Condmaster Ruby applies mathematical
algorithms to baseline data to continuously calculate machine health scores. See "18.6
Health score" on page 515 and "18.7 Alerts" on page 516 for further information.
- 503 -
18.3 Machine Builder
Machine Builder contains the knowledge base derived from the expertise of experienced condition
monitoring practitioners. It provides a graphical drag- and- drop interface to create complete
machines from components, and automatically obtain all measurement assignment settings.
When a machine is created via Machine Builder, appropriate measuring points, measurement assign-
ments, and fault symptoms are automatically generated for the machine. In addition, Color Zones,
which easily show the status of the measuring points, are automatically added to the measuring
points of the created machine.
To add a machine to the Graphical Overview /Tree structure, follow the instructions in " 16.21.1
Adding a machine in Machine Builder" on page 435.
NOTE: It is strongly recommended to create a machine via Machine Builder that relies on expert
knowledge. However, it is also possible to create a machine, its components, and measuring points
with measuring assignments and symptoms manually; see "2.16 Creating elements in the tree struc-
ture" on page 36, "3.1 Creating machines and components" on page 40, and "4.1 Creating a meas-
uring point" on page 45.
- 504 -
18.4 Signal Quality Test
Signal Quality Test is a background process that continuously checks for ski slopes and bias prob-
lems. The function can also identify issues with faulty or incorrectly connected transducers. The main
purpose is to determine whether the signal is of good quality or if there are deviations that merit fur-
ther investigation.
The function is available for Intellinova Parallel EN; see "15.35 Signal Quality Test" on page 383 for
more information about how to activate the function, etc.
- 505 -
18.5 Machine baseline

18.5.1 Introduction
With machine baseline performance data, normal machine behavior can be determined. Baseline per-
formance data are collected through regular measuring assignments as appropriate for the machine,
taken over a training period when the machine is in good mechanical condition, and run under normal
operating conditions.
Mathematical algorithms are applied to baseline data to continuously calculate machine health score
indicated in blue-green-yellow-orange-red-dark red colors for a detailed evaluation.
The machine baseline data can also be used to automatically calculate deviations and potentially raise
alerts for the machine fault symptoms and condition parameters via the Entity rules functionality.
The steps for creating a baseline are as follows:
1. Configure appropriate measuring assignments for relevant measuring points. This can be
done via Machine Builder (see "16.21 Machine Builder" on page 435) or manually (see "2.16
Creating elements in the tree structure" on page 36, "3.1 Creating machines and com-
ponents" on page 40, and "4.1 Creating a measuring point" on page 45.)
2. Collect measurement data during a training period to establish a baseline. It is also possible
to use historical data, see "18.5.2 Establishing machine baselines" below.
18.5.2 Establishing machine baselines

18.5.2.1 Prerequisites
Baseline performance calculations require that measurement assignments are set up in Orders or Hz.
For variable RPM, order tracking is recommended to get reliable data.
The following parameters must not be changed:
l Spectrum unit
l Order tracking
l Frequency range (both min and max)
l Number of lines in the spectrum
l Envelope settings
A baseline is created during a training period, either by collecting measurement data or using his-
torical data. Baselines and training periods are handled via Baseline Manager.
18.5.2.2 Baseline Manager
Baseline Manager is accessed from the Maintenance tab in the ribbon bar and is where training
periods and baselines are handled.
- 506 -
The Baseline Manager window (A) shows measuring assignments with Online selected as meas-
uring instrument, and their status such as Training started, Baseline calculated, and Paused.
The data can be Grouped by (B):

l Measuring point (default if no components exist)
l Component (default if no machines exist)
l Machine (default if machines exist)
l Measuring unit
It is possible to filter out relevant measuring assignments, such as when the baseline is missing or
where baseline has been calculated etc., by using the alternatives available under the Filter func-
tionality (C).
- 507 -
Under the ellipsis button (D), the default settings for defining the training period (days or number
of results) and calculating baselines are managed.
18.5.2.3 Start a training period

Ensure that the training period lasts under appropriate conditions, meaning when the machine is in
good mechanical condition and runs under normal operating conditions.
1. Open Baseline Manager from the Maintenance tab in the ribbon bar (A).
- 508 -
2. Select the ellipsis button for an object (B) (machine, component, measuring point, meas-
uring assignment, or measuring unit) and then select Start training period (C). If you want
to start a training period for all measuring assignments on a measuring point , select the ellip-
sis button for the measuring point, then start the training period.
By default, the training period lasts 30 days, but can be changed to a custom number of days
or number of results. The alternative Manual stop means that you must add the results your-
self on which the baseline is based. These results can be added to the baseline from Graphic
Evaluation , Colored Spectrum , and Measuring Results ; see " 18.5.3 Baseline in other
functions" on page 512 for more information.
3. Select an appropriate alternative and click START (D).
Note: When the training period has started, it is possible to pause and resume it. This can be
relevant to use, for example, if a planned stop has been scheduled.
4. For the alternatives After number of days and After number of results , the training
period stops automatically, and the baseline is calculated and activated. In the Baseline Man-
ager window, the status text Baseline calculated is shown. The green arrow indicates that the
baseline is activated. (A grey arrow indicates that the baseline is inactivated).
5. After the training period is finished, you can select Calculate baseline (E) for a measuring
assignment to check and change the settings for how the baseline should be calculated if
needed. From the Calculate baseline window that opens, you also select to add historical
data to the baseline from various functions, or inactivate the baseline if necessary; see below
for more information.
- 509 -
18.5.2.4 Calculate baseline
The baseline is calculated based on a number of results, distributed over a number of groups
(grouped by RPM by default) where a minimum number of results is required per group (A).
Group by (B) is automatically set to RPM1 and shows the min and max RPM for the measuring point.
If required, this setting can be changed to No grouping or Machine operating conditions (only
displayed if Machine operating conditions have been set up). For Machine operating conditions, the
lowest and highest results are shown for all measuring results.
Permitted area for baseline calculation (C):

l Number of groups 2-1000
l Required number of results per group 3-10 000
The number of results per group must be reached to get a health score evaluation. A group with blue
color has reached a minimum number of results, while a group with a grey color has too few results,
and no evaluation will be made for that RPM interval.
How does a good baseline look like? It depends on the machine. You need to decide if the number of
groups and/or results is ok depending on the machine’s normal behavior.
Active (D) is checked by default and means that the baseline is active for the selected measuring
assignment. To inactivate the baseline, untick the checkbox and select SAVE.
Edit range (E) is used to change From and To values in the y-scale of the graph.
- 510 -
The warning message at the top right of the screen is displayed if there are measurement results that
are linked to the baseline that do not match its measurement settings or do not have a full spectrum.
The message is only information and does not prevent the possibility to activate the baseline. Use the
ellipsis button (F) to open the Measuring Results window and manage these results (see "18.5.3
Baseline in other functions" on the next page for more information).
The settings on the measurement results that must be the same for the measuring assignment’s
baseline calculations are as follows:
l Spectrum unit
l Order tracking
l Frequency range (both min and max)
l Number of lines in the spectrum
l Envelope settings
6. Work with the different settings until you are satisfied, then select SAVE (G).
Using statistical analysis and other methods, Condmaster Ruby now performs algorithmic baseline cal-
culations, computing an average of the selected measurement results that serves as a "benchmark"
for what will be considered within the limits of normal machine behavior.
Future measurements will be compared with the baseline, and the system will provide detailed health
score evaluation information in the Graphical Overview, see "18.6 Health score" on page 515.
18.5.2.5 Create baseline from historical data

It is possible to create a baseline from previously collected data by selecting a subset of rep-
resentative measurements via Measuring Results, Graphic Evaluation, and Colored Spectrum;
see "18.5.3 Baseline in other functions" on the next page for details.
- 511 -
18.5.3 Baseline in other functions

18.5.3.1 Measuring Results
The 'B' icon in the first column in the measurement results window shows that the measurement res-
ult is linked to the baseline and part of a baseline calculation.
The 'B with a red x' icon shows that the measurement result is linked to a baseline but that its meas-
urement settings do not match the baseline’s measurement settings or that the full spectrum is not
stored on the measurement result. Therefore, these measuring results will be excluded from the
baseline calculation. If this icon is displayed on any measuring result, a warning message will appear
in the row below the list of results.
In order to add results to (or delete results from) a baseline, the measuring assignment must have a
baseline where the status is Training started or Baseline calculated, see below for the required steps.
To link one or more results to the baseline:
1. Go to Maintenance > Baseline Manager.
2. Make sure that the measuring assignment of interest has a baseline where the status is Train-
ing started or Baseline calculated.
3. Select the ellipsis button and then select Measuring Results.
4. Mark one or more measuring results to be included in the baseline data (A).
5. Click the 'B' button in the Measuring results window toolbar and select Add to Baseline (B)
from the menu. If the baseline is activated, it is recalculated.
The alternative Delete from Baseline deletes marked results from the baseline.
- 512 -
18.5.3.2 Graphic Evaluation
In order to add results to (or detele results from) a baseline, the measuring assignment must have a
baseline where the status is Training started or Baseline calculated, see below for the required steps:
3. Select the ellipsis button and then select Graphic Evaluation.
4. In the graph, zoom in on the period to be included in the baseline data (A).
5. Right-click and select Add to Baseline (B).
The baseline is automatically calculated, and the selection is marked with blue color in the
graph. To hide the blue color in the graph, right-click and inactivate Show information texts
(C).
- 513 -
18.5.3.3 Colored Spectrum Overview
In order to add results to (or delete results from) a baseline, the measuring assignment must have a
baseline where the status is Training started or Baseline calculated, see below for the required steps:
3. Select the ellipsis button and then select Colored Spectrum.
4. In the spectrum, zoom in on the period to be included in the baseline data (A).
5. Right-click and select Add to Baseline (B). The baseline is automatically recalculated.
Subtract Baseline (C) in the Colored Spectrum window toolbar can be toggled on and off. On means
that the baseline is subtracted from each spectrum. As a result, data that differs from the baseline is
emphasized. Data that is the same as the baseline is toned down. Measuring results for groups in the
baseline that are not active or fall outside the min/max in the Calculate baseline window (see
"18.5.2.4 Calculate baseline" on page 510) are shown in dark blue.
- 514 -
18.6 Health score

When a Machine baseline is set, the health score calculations are presented by the machine, com-
ponents and measuring points in the Graphical Overview . To set a baseline, see " 18.5 Machine
baseline" on page 506.
The Health score feature includes more colors than the basic color evaluation (green-yellow-red) for a
more detailed evaluation. The colors in the Health score correspond to a normalized floating-point
value between 0-1, where 0.2 (green) corresponds to the normal state of the machine baseline:
A machine with blue health score is considered to be in better condition than the machine baseline,
which could mean that the machine baseline was not set up correctly.
If health score and basic color evaluation are used at the same time, the color that corresponds to the
most critical evaluation is displayed.
In the Graphical Overview, the color evaluation mode is set to Basic color evaluation by default,
but you can easily toggle between Basic color evaluation, Health score, and Both. This setting is
valid per database (not per user).
The dots show the evaluation color and the alert icons show the alert priority color (for more inform-
ation about alert priority, see "18.7 Alerts" on the next page.)
- 515 -
18.7 Alerts
18.7.1 Overview
To view the alert list, go to Graphical Overview > Alert list (A):
A. Alert list: opens the alert list in Condmaster Ruby.

B. Filters: filter out the alerts according to different parameters, for example, priority.
C. Based on the currently selected filters, Priority summary shows the number of alerts with dif-
ferent priority levels.
D. Priority: the colored icons with text informs about the alert priority.
E. Date/time: date and time for when the alert was generated.
F. Status: current status of the alert.
G. Source: source that triggered the alert, for example, a measuring assignment or a measuring
unit. Its current evaluation (basic color evaluation) is shown if applicable.
H. Description: text describing the alert.
I. Actions: menu with different actions to perform on the alert (corresponds to a right-click on
an alert).
J. Details: shows details for the alert, for example, an event log.
K. Comment: with a digit representing the number of comments on a measuring point.
L. Deduplication: informs how many times (x1, x2, etc.) the alert is deduplicated. Dedu-
plication prevents the occurrence of copies of the same alert, which keeps the alert list short
and easy to work with.
M. Docked windows: possibility to open, for example, Graphic Evaluation next to the alert list
window.
N. Ellipsis icon: visible when at least one alert is marked and used for changing the priority on
one or several alerts.
Alerts are assigned six different priority levels for better and easier prioritization:
- 516 -
l Informational – blue.
l Low – green.
l Moderate – yellow.
l Medium – orange.
l High – red.
l Critical – dark red.
Alerts also have statuses that are used to enable workflow-based handling:
l New – unhandled alert.
l Open – acknowledged alert.
l Snoozed – paused and hidden alert for a period of time.
l Closed – handled alert.
l Deleted – deleted alert (not possible to access).
To change the status of an alert, mark it and hover over the ellipsis icon at the bottom right of the
window and choose a status in the list. An alert does not have to follow the workflow. For example, an
alert can be changed from Closed to New.
To pause and hide an alert from the alert list without deleting it, select the Snooze status. In the
snooze window, define how long the alert should be snoozed and select Yes, snooze the alert.
18.8.2 Alerts
The alert list is an essential part of Condmaster and fundamental to your evaluation work. The alert
list collects different types of alerts from all sources, such as machines, measuring points, and units,
which are included in the chosen database. If alert limits are set up on measuring assignments, alerts
will be generated when a measuring result exceeds the defined limits. Also, alerts such as ‘No result
from online unit’ and comment alerts made by a user can appear on the alert list.
The alert list offers a flexible workflow and efficient management of maintenance tasks when equip-
ment condition and criticality rating calls for action, such as setting priority levels and status indic-
ations on individual alerts.
For more information about the constituent parts of the alert list and how to work with alerts, see "9.3
Alert list" on page 163 and "9.4 Working with the alert list" on page 177.
Alerts based on health score
Alerts based on health score calculations can be set up via the Entity rules functionality. This way,
you get great flexibility regarding what you want to see in the alert list. For an example of how to set
up an alert via Entity rules, see "18.8 Entity rules" on the next page.
- 517 -
18.8 Entity rules

18.8.1 Introduction
Entity rules is not a necessary part of the Decision Support System. It is a stand-alone functionality
that can be used as a hub for expanding and customizing Condmaster with event-driven functions, as
well as creating custom integrations with other IIoT systems.
The feature makes it possible to monitor a variety of events and automatically invoke actions based
on these events. Other rule actions may include:
l triggering a defined type of measurement
l sending an email
l sending an API call
l create an alert
l creating a work order
l closing a relay
l or a variety of other things.
You can use Entity rules to set up certain actions when a certain combination/combinations of con-
ditions occur, for example “if the velocity is higher than 2.8 mm/s and if the RPM is higher than 1200,
then send an email”.
Read more about all the possibilities in the section "16.22 Entity rules" on page 440.
18.8.2 Setting up alerts via Entity rules

This section describes an example of how to set up Alerts via Entity rules. For full documentation on
the Entity rules functionality, see section "16.22 Entity rules" on page 440.
Example: If the health score value for a measuring assignment on measuring point "I-000.00 Motor"
exceeds 0.8, then create an alert with priority high.
Overall steps:
l Create a server rule based on a measuring result to be applied on the measuring point.
l Set up the condition: if the health score value is higher than 0.8
l Action: set up what will happen when the condition is fulfilled, i.e. create an alert with priority
high
Note: The Entity rules functionality applies to online units handled by Condmaster Entity Server
(CES) (i.e. Intellinova Parallel EN, Airius sensors).
- 518 -
18.8.3 Example of a rule generating an alert
1. Go to Entity rules. The function resides in Condmaster.NET and can be accessed from there, or
from Condmaster Ruby via the Entity rules icon under the Online ribbon tab.
2. To create a new entity rule, select the ‘+’ sign in the bottom right part of the screen (A):
3. Name the rule (B).
- 519 -
4. For Rule environment, select Server rule (C).
5. As Rule type, select Measurement result(D).
6. Select CREATE (E). The rule now exists but has no conditions or actions tied to it.
When you have created a new entity rule and selected its rule environment and type, the General
tab (A) is shown in the Edit rule window:
7. Select the ‘+’ sign under Rule applies to and select Measuring points (B).
8. Under Relational mode (C), select Is one of.
9. In the dropdown list (D), select the measuring point that should be included in the Is one of.
10. Select SAVE(E). The rule now applies to the I-000.00 Motor measuring point.
- 520 -
11. Select Save in the upper right part of the screen (E) to save the selection under the current
rule.
On the Conditions tab (A), conditions for the rule are added.
12. To add conditions, select the ‘+’ sign under Edit conditions and select Measurement value
(B).
13. Select Health score value (0-1) (C) from the list.
Health score value (0-1): the health score in a scale from 0 to 1 (floating point number). For
example, a value higher than 0.8 (red) can motivate to create an alert. For more information
about the values, see "18.6 Health score" on page 515.
Health score value slow (0-1): the health score in a scale from 0 to 1 where slow means that
the value is changing more slowly; instead of using the latest measuring result, an average
of serveral latest results are used.
Heath score color evaluation: the health score value (0-1) in a scale from 0 to 6 (the health
score decimal value transposed to an integer value), where 0 = grey, 1 = blue, 2 = green, 3
= yellow, 4 = orange, 5 = red, 6 = dark red.
Health score color evaluation slow: the health score value slow in a scale from 0 to 6 (the
health score slow decimal value transposed to an integer value).
- 521 -
14. Under Relational mode, select Greater than (D).
15. Select Static value, and enter 0.8 in the Value field (E).
16. Select SAVE (F).
17. Select Save in the upper right part of the screen (G) to save the rule.
See " 16.22 Entity rules " on page 440 for information about the settings possible under Show
advanced.
On the Actions tab (A), you decide what is going to happen in relation to the condition, for example,
generate an alert.
18. To add an action, select the ‘+’ sign in the top right part of the screen and then select Alert
(B).
- 522 -
Alerts are added to the Alert list in Condmaster, see "18.7 Alerts" on page 516 to learn more.
19. Execute on is set to Fulfilled by default (C) .

When the rule is executed, the conditions are either TRUE or FALSE. If the conditions are
TRUE, the Fulfilled actions will be executed.
21. Enter the Alert text (E) that should be shown in the Alert list.
If you want to include a measurement value in the alert list, you need to add a variable under
the Variables tab. See "16.22 Entity rules" on page 440 for information about how to create
a variable.
22. Deduplication informs how many times (x1, x2, etc.) the alert is deduplicated. Deduplication
prevents the occurrence of copies of the same alert, which keeps the alert list short and easy
to work with. Insert a Deduplication identifier (F) to get an updated number in the altert
list each time the alert is generated. For example, you could insert "Alert_measuringpointID"
for a measuring point alert (but change the text "measuringpointID" to a unique measuring
point identification number).
23. Change the Priority (G) to High (or appropriate).
24. By default, Status (H) is set to New.
25. In the field Tags (I), it is possible to enter one or several tags so that the user can more eas-
ily categorize the alert (the tags are accessible via the CES API).
- 523 -
26. Select SAVE (J).
27. Select Save in the upper right part of the screen to save the rule.
The rule is ready and when the health score value passes 0.8 for any of the measuring assingments
on the measuring point H-000.00 Motor, an alert with priority high will be generated in the alert list.
- 524 -
18.9 SPM Instrument AB Software License Agreement

This is a legal agreement between you, the end user, and SPM Instrument AB. This License Agree-
ment applies to the copy of the software program(s) and all software material included in the delivery
that you, the end user, are now taking into use.
By opening the media package or installing or using the software, you are agreeing to be bound by
these terms and conditions. If you do not agree to them, promptly return the unopened media pack-
age and accompanying material for a full refund.
Grant of license
SPM Instrument AB grants you the right to have one installation of the software on a single computer
standing alone or acting as a network server. You may use upgrade software only to replace or
enhance your earlier-licensed version of the software. If use of the software is authorized under an
Additional License, SPM Instrument AB grants you the right to make one additional authorized use of
the earlier-licensed software. To assist you in using the software, you may either make a copy of the
software solely for archival purposes, or transfer the software to a single hard disk provided that you
keep the original solely for archival purposes. You must include all copyright notices on the archival
copy. If the software is pre-installed on the hard disk of a computer, any accompanying media con-
stitute the archival copy. You may not use, copy, modify, or transfer your right to use the software or
accompanying material, or any copy of either, except as expressly provided in this License Agree-
ment. All rights not expressly granted are reserved by SPM Instrument AB or its suppliers.
Termination of license
You may terminate this License at any time by destroying the software, archival copy and accom-
panying material.SPM Instrument AB may terminate this License Agreement if you fail to comply with
its terms and conditions; upon such termination you shall destroy the software, archival copy and
accompanying material.
Other restrictions
You may not rent or lease the software, but you may transfer all your rights on a permanent basis,
provided you transfer all copies of the software, including your most recent upgrade and all prior ver-
sions, and accompanying material, and the recipient agrees to the terms of this License Agreement.
Export is subject to the requirements and restrictions of applicable laws and requirements, including
but not limited to the Export Administration Regulations of the United States of America. You may not
reverse engineer, decompile or disassemble the software, except to the extent such acts may not be
prohibited by law in the country of use. You may configure the software for your own use, but not oth-
erwise modify it or merge it into another program unless in support of your authorized use.
Copyright
© SPM Instrument AB 1999. All rights reserved. No part of this manual may be reproduced, trans-
ferred, or copied, in any form or by any means, without written permission bySPM Instrument AB.
Reservations
This manual describes the product at the time stated above. The contents of this manual may be
altered without notice and may not be regarded as a commitment from SPM Instrument AB .
SPM Instrument AB takes no responsibility for possible errors or discrepancies in this manual.
Trademark
Condmaster and Condmaster®Ruby are registered trademarks of SPM Instrument AB. Other com-
pany and product names which may occur in this manual are trademarks or registered trademarks of
the respective owners.
Limited Warranty
SPM Instrument AB warrants that the software will perform under normal use substantially in accord-
ance with the accompanying material for a period of three (3) months from the date of receipt.
- 525 -
SPM Instrument AB warrants the media on which the software is furnished to be free from defects in
materials and workmanship under normal use for a period of three (3) months from the date of
receipt. This Limited Warranty is void if failure of the software has resulted from accident or misuse.
No other warranties. SPM Instrument AB disclaims all other warranties, either expressed or

implied, including but not limited to implied warranties of merchantability and fitness for a particular
purpose, with respect to the software. There is no warranty by SPM Instrument AB or any other party
or person that the functions contained in the software will meet your requirements or that the oper-
ation of the software will be uninterrupted or error-free. You assume all responsibility for the selec-
tion of the software to achieve your intended results, and for the installation, use and results obtained
from it.
No liability for consequential damages. To the maximum extent permitted by applicable law,
SPM Instrument AB and its suppliers and any other party or person shall not be liable for any dam-
ages whatsoever (including, without limitation, damages or losses of business profits, lost savings,
business interruption, loss of business information or data, or other pecuniary loss) arising out of the
use of or liability to use this software, even if SPM Instrument AB or its suppliers or the other party or
person has been advised of the possibility of such damages.
SPM Instrument AB
Box 504, SE-645 25 STRÄNGNÄS
Sweden
- 526 -

1 - Condmaster 2022 User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1 - Condmaster 2022 User Guide

Uploaded by

Copyright:

Available Formats

ANALYSIS AND DIAGNOSTICS

© Copyright SPM Instrument AB. ISO 9001 certified.

1. Task definition 11 2.17 Machines, components and measuring

5.51 Measuring techniques in the tree 7. Measuring rounds 144

5.53 Time Signal Recording measurement 7.5 Downloading measuring round to

Setting up temperature measurement 131 Downloading all measuring rounds

Relative and absolute phase 133 7.9 Connecting A/T30 to PC 155

Phase symptom settings 134 7.11 Identification tag CondID in Cond-

12.14 Combining diagrams 295 Where to find it 322

Saving combinations of diagrams as a Controlling the quality and amount of

Change line size and color 297 15.2 Measurement conditions in

15.16 Setting up the ‘Ski slope’ symptom 347

15.21 Time-based measurement 358 16.10 Condition View Report 397

15.22 Group measurement 359 Introduction to Condition View Report 397

15.23 Linked measurement 361 Getting started 397

15.24 Idle time measurement 363 Opening a sequence or measuring

Distribution of global CES values to Final Page section 407

Designing your own reports 417 The Advanced tab 461

16.13 Exporting to Word file 418 The History tab 462

16.14 Exporting measuring results to Shared variables 463

16.16 Runtime count 420 16.24 Importing measurement results 466

Configure automatic removal for a 16.25 CES API 479

17.8.2 Plant Performer statistics access

17.8.3 Working with Plant Performer

18. Decision Support System 502

18.1 Introduction to Decision Support Sys-

18.2 Getting started with Decision Sup-

18.3 Machine Builder 504

18.4 Signal Quality Test 505

18.5 Machine baseline 506

18.5.1 Introduction 506

18.5.2 Establishing machine baselines 506

18.5.2.1 Prerequisites 506

18.5.2.2 Baseline Manager 506

18.5.2.3 Start a training period 508

18.5.2.4 Calculate baseline 510

18.5.2.5 Create baseline from his-

18.5.3 Baseline in other functions 512

18.5.3.1 Measuring Results 512

18.5.3.2 Graphic Evaluation 513

18.5.3.3 Colored Spectrum Overview 514

18.6 Health score 515

18.7 Alerts 516

18.7.1 Overview 516

18.8.2 Alerts 517

18.8 Entity rules 518

18.8.1 Introduction 518

18.8.2 Setting up alerts via Entity rules 518

18.8.3 Example of a rule generating

18.9 SPM Instrument AB Software License

Measuring techniques on condensate pump

l (A) Motor ND: SPM

1.2 Machine data, condensate pump

Machine data for input

l (A) Motor ND: ISO bearing no. (shaft diameter)

2.1 Navigating in the Graphical Overview

2.2 Arranging the Graphical Overview

l A = Plant overview level with paper machine PM2 marked

2.3 Importing pictures

Images must be in BMP, JPG or SVG format.

1. Select Edit Mode (A).

6. Cancel Edit Mode.

2.4 Picture properties