FM Professional Help

www.mixtelematics.com
Table of Contents
Part I Fleet Manager Documentation 1

Part II Fleet Manager Dealer Utility 2

1 FM Dealer Utility
...................................................................................................................................
User Manual 5

Part III Fleet Manager Professional 17

1 Installing Fleet
...................................................................................................................................
Manager Professional 9 20
2 Registering ...................................................................................................................................
Fleet Manager Professional 30
3 FM Upgrade+
...................................................................................................................................
(Registering Your Software) 31
4 Configuring ...................................................................................................................................
FM Professional for Network Operation 36
5 Fleet Manager
...................................................................................................................................
Views 43
6 Getting Started
...................................................................................................................................
With Fleet Manager Professional 45
7 Glossary ................................................................................................................................... 49
8 Trip Explanation
................................................................................................................................... 55
9 Working with
...................................................................................................................................
Fleet Manager Professional 56
Language Settings
.......................................................................................................................................................... 56
Measurement..........................................................................................................................................................
Settings 57
Daylight Savings
..........................................................................................................................................................
Settings 58
Security Settings
.......................................................................................................................................................... 65
Wizards .......................................................................................................................................................... 68
About Wizards
......................................................................................................................................................... 68
Fleet Manager
.........................................................................................................................................................
Wizards 69
Extensions .......................................................................................................................................................... 71
10 Windows and
...................................................................................................................................
Menus 72
Windows .......................................................................................................................................................... 72
Main Program.........................................................................................................................................................
Window 72
Activity Timeline
.........................................................................................................................................................
Window 77
Report Window
......................................................................................................................................................... 79
Graph Window......................................................................................................................................................... 80
Menus .......................................................................................................................................................... 81
File ......................................................................................................................................................... 81
Print List ......................................................................................................................................... 81
Exiting Fleet Manager .........................................................................................................................................
Professional 8 82
Edit ......................................................................................................................................................... 83
Event Definitions......................................................................................................................................... 83
Trip Categories ......................................................................................................................................... 87
Code Plug......................................................................................................................................................... 88
Plug Information......................................................................................................................................... 88
Tools ......................................................................................................................................................... 89
Fuel Information......................................................................................................................................... 89
Options ......................................................................................................................................... 90
Service History ......................................................................................................................................... 93
Extension Manager ......................................................................................................................................... 95

www.mixtelematics.com
2
 11 Organisation...................................................................................................................................
Properties 97
Driver Scoring ..........................................................................................................................................................
Parameters 99
Audit Policy .......................................................................................................................................................... 101
12 Site Properties
................................................................................................................................... 102
13 Vehicles ................................................................................................................................... 104
Unit Types .......................................................................................................................................................... 104
Unit Properties
.......................................................................................................................................................... 106
Vehicle Properties
.......................................................................................................................................................... 112
Servicing and..........................................................................................................................................................
Licensing 115
Engine Hours .......................................................................................................................................................... 118
Arming Delay ..........................................................................................................................................................
and Standing Delay 121
Interval (Tacho)
..........................................................................................................................................................
Data 122
Device Properties
.......................................................................................................................................................... 124
14 Drivers ................................................................................................................................... 127
Driver Properties
.......................................................................................................................................................... 127
Driver/Vehicle
..........................................................................................................................................................
Access Control 130
Driver Licensing
.......................................................................................................................................................... 132
How to use the
..........................................................................................................................................................
Extended Driver Identification functionality 133
Fleet Manager
..........................................................................................................................................................
DTCO Functionality 137
15 Passengers................................................................................................................................... 138
How To Configure
..........................................................................................................................................................
and Manage Passenger Code-Plugs 138
Passenger Properties
.......................................................................................................................................................... 140
16 Configuration
...................................................................................................................................
Groups 141
Driver Configuration
..........................................................................................................................................................
Group Properties 141
Vehicle Configuration
..........................................................................................................................................................
Group Properties 143
17 Reporting Groups
................................................................................................................................... 146
Driver Reporting
..........................................................................................................................................................
Group Properties 146
Vehicle Reporting
..........................................................................................................................................................
Group Properties 147
18 Configuring
...................................................................................................................................
the On-Board Computer 148
Event Configuration
..........................................................................................................................................................
Overview 148
About Devices,
..........................................................................................................................................................
Parameters and Events 152
Defining Custom
..........................................................................................................................................................
Events 173
Device Properties
.......................................................................................................................................................... 183
Parameter Properties
.......................................................................................................................................................... 186
Event Properties
.......................................................................................................................................................... 188
Default Vehicle
..........................................................................................................................................................
Configurations 191
19 Reports ................................................................................................................................... 197
Criteria Wizard
.......................................................................................................................................................... 197
Reporting Batches
.......................................................................................................................................................... 198
Activity Timeline
.......................................................................................................................................................... 202
Tachograph ..........................................................................................................................................................
Data 204
Driver and Vehicle
..........................................................................................................................................................
Lists 205
Trip Reports.......................................................................................................................................................... 206
Driver Scoring
..........................................................................................................................................................
Report 208
Fuel Consumption
..........................................................................................................................................................
Report 209
Performance..........................................................................................................................................................
Summary Report 210
Driving Errors
..........................................................................................................................................................
Report 211
Event Report.......................................................................................................................................................... 212
FM Terminal..........................................................................................................................................................
Report 213

www.mixtelematics.com
3
 Fleet Log Book
..........................................................................................................................................................
Report 214
20 Fleet Manager
...................................................................................................................................
Professional 9 Administrator 215
21 Software Support
................................................................................................................................... 222

Part IV Fleet Manager Extensions 224

1 Fleet Manager
...................................................................................................................................
Active Tracking and Messaging Extension 228
2 Fleet Manager
...................................................................................................................................
Advanced Driver Scoring Extension 253
3 Fleet Manager
...................................................................................................................................
Australian Driving Hours Exception Extension 268
4 Fleet Manager
...................................................................................................................................
Comms Scheduler Extension 276
5 Fleet Manager
...................................................................................................................................
Costing Extension 285
6 Fleet Manager
...................................................................................................................................
Event Consumption Reports Extension 293
7 Fleet Manager
...................................................................................................................................
Event Summary Reports Extension 303
8 Fleet Manager
...................................................................................................................................
Exploration and Production Safety Extension 309
9 Fleet Manager
...................................................................................................................................
Export Extension 333
10 Fleet Manager
...................................................................................................................................
Location Reports Extension 345
11 Fleet Manager
...................................................................................................................................
Passenger Extension 361
12 Fleet Manager
...................................................................................................................................
Snow Plough Extension 371
13 Fleet Manager
...................................................................................................................................
Materials Handling Extension 382
14 Fleet Manager
...................................................................................................................................
Map & Guide Extension 395
15 FM Map Set...................................................................................................................................
Extension 401
FM Map Set ..........................................................................................................................................................
Installation Guide 404
FM Map Set ..........................................................................................................................................................
User Manual 408
16 Fleet Manager
...................................................................................................................................
GPS Log Viewer Extension 418
Fleet Manager
..........................................................................................................................................................
GPS Log Viewer for MapPoint Extension 436
Mapping with
..........................................................................................................................................................
Google Earth 444
17 Fleet Manager
...................................................................................................................................
System Tools 1 Extension 447
18 Fleet Manager
...................................................................................................................................
Taxlog Extension 466
19 Fleet Manager
...................................................................................................................................
TCO Driver Data Extension 473
20 Fleet Manager
...................................................................................................................................
Timeline Reports Extension 494
21 Fleet Manager
...................................................................................................................................
Trailer Management Extension 499
22 Fleet Manager
...................................................................................................................................
Vehicle Maintenance Extension 506

Part V Fleet Manager Communications Suite 513

1 Setting Up and Configuring the Transparent GSM and GPS
Features ................................................................................................................................... 515
2 Fleet Manager
...................................................................................................................................
SMS Processor 518
Setting Up And
..........................................................................................................................................................
Configuring A GSM Modem for SMS 522
3 Fleet Manager
...................................................................................................................................
GSM Downloader 544
Setting Up And
..........................................................................................................................................................
Configuring A GSM Modem 548
4 Fleet Manager
...................................................................................................................................
DECT Downloader 570
Setting Up And
..........................................................................................................................................................
Configuring FM DECT Modems 574

www.mixtelematics.com
4
 5 Fleet Manager
...................................................................................................................................
GPRS Service 580
GPRS Product..........................................................................................................................................................
Fact Sheet 593
GPRS Questions
..........................................................................................................................................................
and Answers 597
Testing a GPRS
..........................................................................................................................................................
SIM card 601
6 Fleet Manager
...................................................................................................................................
AutoPoll Client 622
FM Downloader
..........................................................................................................................................................
Service 630
7 Setting Up ...................................................................................................................................
And Configuring A GSM Modem for GPRS 632
8 Fleet Manager
...................................................................................................................................
SMTP Mail Service 655
9 FM Sat Comms
................................................................................................................................... 658
FM Sat Comms
..........................................................................................................................................................
Installation Guide 663
FM Sat Comms
..........................................................................................................................................................
User Guide 677
10 IP Router ................................................................................................................................... 681
11 Handset & ...................................................................................................................................
E-Mail Notifications In The Fleet Manager System 686

Part VI Fleet Manager Packages 689

1 Fleet Manager
...................................................................................................................................
Track & Trace 689
Fleet Manager
..........................................................................................................................................................
Track & Trace Installation Guide 692
Fleet Manager
..........................................................................................................................................................
Track & Trace User Guide 699
Fleet Manager
..........................................................................................................................................................
Track & Trace User Guide - Maps, Vehicles and Messages 709
Fleet Manager
..........................................................................................................................................................
Track & Trace User Guide - Reports and Management 721
2 FM Tracer ................................................................................................................................... 737
FM Tracer Installation
..........................................................................................................................................................
Guide 741

Part VII Fleet Manager Hardware Products and

Accessories 744
1 FM Messenger
................................................................................................................................... 749
2 FM Navigator
................................................................................................................................... 752
3 FM Wireless
...................................................................................................................................
Kit 755
FM Wireless..........................................................................................................................................................
Kit Installation Guide 757
FM Wireless..........................................................................................................................................................
Kit Getting Started Guide 759
4 FM DECT ................................................................................................................................... 775
5 FM Impact ...................................................................................................................................
Sensor 787
FM Impact Sensor
..........................................................................................................................................................
Installation Manual 789
FM Impact Sensor
..........................................................................................................................................................
User Manual 793
6 FM Keypad................................................................................................................................... 799
FM Keypad Installation
..........................................................................................................................................................
Manual 801
FM Keypad User
..........................................................................................................................................................
Manual 804
7 How to use...................................................................................................................................
Temperature Recorders with FM200 Plus 810
8 FM TCO Interface
...................................................................................................................................
Installation Manual 815
9 FM KTCO1318
...................................................................................................................................
Interface Installation Manual 817
10 FM Terminal
................................................................................................................................... 819
FM Terminal..........................................................................................................................................................
User Manual 822
FM Terminal..........................................................................................................................................................
Installation Manual 827
11 FM Trailer ID
................................................................................................................................... 836

www.mixtelematics.com
5
 FM Trailer ID..........................................................................................................................................................
Installation Manual 838
FM Trailer ID..........................................................................................................................................................
User Manual 840
12 FM Wireless
...................................................................................................................................
Trailer ID 842
FM Wireless..........................................................................................................................................................
Trailer ID Setup 845
13 USB Download
...................................................................................................................................
Module 846
14 FM100 ................................................................................................................................... 850
FM100 Product
..........................................................................................................................................................
Manual 852
FM100 User ..........................................................................................................................................................
Manual 867
FM100 Beep..........................................................................................................................................................
and Flash Codes 868
15 FM200 ................................................................................................................................... 872
FM200 ComLink-GSM
.......................................................................................................................................................... 872
FM200 ComLink-GSM
.........................................................................................................................................................
Installation 875
FM200 Communicator
.......................................................................................................................................................... 878
FM200 Communicator
.........................................................................................................................................................
Installation Checklist 882
FM200 Communicator
.........................................................................................................................................................
Installation Manual 883
FM200 GPS ..........................................................................................................................................................
Interface Installation Manual 887
FM200 Locator
.......................................................................................................................................................... 889
FM200 Locator
.........................................................................................................................................................
Installation Manual 892
FM200 Plus .......................................................................................................................................................... 895
FM200 Plus
.........................................................................................................................................................
User Manual 898
FM200 Plus
.........................................................................................................................................................
Questions and Answers 902
FM200 Plus
.........................................................................................................................................................
Quick Start Guide 904
FM200 Plus
.........................................................................................................................................................
Installation Manual 914
FM200 Plus
.........................................................................................................................................................
Installation Checklist 932
FM200 Plus
.........................................................................................................................................................
Beep and Flash Codes 933
FM200 Plus
.........................................................................................................................................................
HV Installation and User Manual 941
FM200 Plus
.........................................................................................................................................................
Serial Cable User Manual 964
FM200 Plus
.........................................................................................................................................................
Waterproof Serial Cable Installation and User Manual 966
FM200 Plus
.........................................................................................................................................................
Waterproofing Kit 969
FM200 Plus
.........................................................................................................................................................
Wiring Harness User Manual 975
How to connect
.........................................................................................................................................................
FM Dayton to FM200 Plus 977
FM200 CAN .......................................................................................................................................................... 979
16 FM300 ................................................................................................................................... 981
FM300 ComLink-GSM
.......................................................................................................................................................... 981
FM300 Communicator
.......................................................................................................................................................... 984
FM300 Communicator
.........................................................................................................................................................
Installation Manual 988
FM300.........................................................................................................................................................
User Manual 1007
FM300 CAN..........................................................................................................................................................
Overview 1016
FM300.........................................................................................................................................................
CAN Installation Manual 1022
FM300.........................................................................................................................................................
CAN User Manual 1024
FM300 Twin..........................................................................................................................................................
Serial Harness 1027
17 FM 3310i Overview
................................................................................................................................... 1030
FM 3310i User
..........................................................................................................................................................
Manual 1034
FM 3310i Setup
..........................................................................................................................................................
on FM-Web 1037

Part VIII Interaction With Other Devices 1044

1 Introduction
...................................................................................................................................
to CAN 1044
2 Garmin Integration
................................................................................................................................... 1056

www.mixtelematics.com
6
 Part IX Fleet Manager SDKs 1066
1 Fleet Manager
...................................................................................................................................
Extention SDK 8 1072
Client Extension
..........................................................................................................................................................
Manager Interface 1074
Server Extension
..........................................................................................................................................................
Manager Component 1076
XML Web Service
.......................................................................................................................................................... 1077
CI Language..........................................................................................................................................................
Tools 1078

Part X Marketing and Support 1080

1 Product Support
................................................................................................................................... 1081
2 Fleet Management
...................................................................................................................................
Systems Offline Knowledge Base 1083
All Articles .......................................................................................................................................................... 1084
CI Data .......................................................................................................................................................... 1101
CITAS 2010.......................................................................................................................................................... 1102
EV100 .......................................................................................................................................................... 1103
Fleet Manager..........................................................................................................................................................
98 1104
Fleet Manager..........................................................................................................................................................
2000 1110
Fleet Manager..........................................................................................................................................................
2001 1116
Fleet Manager..........................................................................................................................................................
2002 Professional 1118
FM100 .......................................................................................................................................................... 1120
FM200 .......................................................................................................................................................... 1123
3 Offline Knowledge
...................................................................................................................................
Base Articles 1129
Knowledge..........................................................................................................................................................
Base Article 1 1129
Knowledge..........................................................................................................................................................
Base Article 2 1131
Knowledge..........................................................................................................................................................
Base Article 3 1133
Knowledge..........................................................................................................................................................
Base Article 4 1134
Knowledge..........................................................................................................................................................
Base Article 5 1135
Knowledge..........................................................................................................................................................
Base Article 6 1136
Knowledge..........................................................................................................................................................
Base Article 7 1138
Knowledge..........................................................................................................................................................
Base Article 8 1140
Knowledge..........................................................................................................................................................
Base Article 9 1143
Knowledge..........................................................................................................................................................
Base Article 10 1146
Knowledge..........................................................................................................................................................
Base Article 11 1149
Knowledge..........................................................................................................................................................
Base Article 12 1150
Knowledge..........................................................................................................................................................
Base Article 13 1151
Knowledge..........................................................................................................................................................
Base Article 14 1152
Knowledge..........................................................................................................................................................
Base Article 15 1153
Knowledge..........................................................................................................................................................
Base Article 16 1154
Knowledge..........................................................................................................................................................
Base Article 17 1155
Knowledge..........................................................................................................................................................
Base Article 18 1156
Knowledge..........................................................................................................................................................
Base Article 19 1157
Knowledge..........................................................................................................................................................
Base Article 20 1158
Knowledge..........................................................................................................................................................
Base Article 21 1159
Knowledge..........................................................................................................................................................
Base Article 22 1160
Knowledge..........................................................................................................................................................
Base Article 23 1161
Knowledge..........................................................................................................................................................
Base Article 24 1162
Knowledge..........................................................................................................................................................
Base Article 25 1163
Knowledge..........................................................................................................................................................
Base Article 26 1164
Knowledge..........................................................................................................................................................
Base Article 27 1165
Knowledge..........................................................................................................................................................
Base Article 28 1166

www.mixtelematics.com
7
 Knowledge..........................................................................................................................................................
Base Article 29 1167
Knowledge..........................................................................................................................................................
Base Article 30 1168
Knowledge..........................................................................................................................................................
Base Article 31 1169
Knowledge..........................................................................................................................................................
Base Article 32 1171
Knowledge..........................................................................................................................................................
Base Article 33 1172
Knowledge..........................................................................................................................................................
Base Article 34 1173
Knowledge..........................................................................................................................................................
Base Article 35 1174
Knowledge..........................................................................................................................................................
Base Article 36 1175
Knowledge..........................................................................................................................................................
Base Article 37 1176
Knowledge..........................................................................................................................................................
Base Article 38 1181
Knowledge..........................................................................................................................................................
Base Article 39 1183
Knowledge..........................................................................................................................................................
Base Article 40 1185
Knowledge..........................................................................................................................................................
Base Article 41 1187
Knowledge..........................................................................................................................................................
Base Article 42 1189
Knowledge..........................................................................................................................................................
Base Article 43 1190
Knowledge..........................................................................................................................................................
Base Article 44 1191
Knowledge..........................................................................................................................................................
Base Article 45 1192
Knowledge..........................................................................................................................................................
Base Article 46 1195
Knowledge..........................................................................................................................................................
Base Article 47 1198
Knowledge..........................................................................................................................................................
Base Article 48 1199
Knowledge..........................................................................................................................................................
Base Article 49 1200
Knowledge..........................................................................................................................................................
Base Article 50 1201
Knowledge..........................................................................................................................................................
Base Article 51 1202
Knowledge..........................................................................................................................................................
Base Article 52 1203
Knowledge..........................................................................................................................................................
Base Article 53 1204
Knowledge..........................................................................................................................................................
Base Article 54 1205
Knowledge..........................................................................................................................................................
Base Article 55 1206
Knowledge..........................................................................................................................................................
Base Article 56 1207
Knowledge..........................................................................................................................................................
Base Article 57 1208
Knowledge..........................................................................................................................................................
Base Article 58 1209
Knowledge..........................................................................................................................................................
Base Article 59 1210
Knowledge..........................................................................................................................................................
Base Article 60 1211
Knowledge..........................................................................................................................................................
Base Article 61 1212
Knowledge..........................................................................................................................................................
Base Article 62 1214
Knowledge..........................................................................................................................................................
Base Article 64 1215
Knowledge..........................................................................................................................................................
Base Article 65 1216
Knowledge..........................................................................................................................................................
Base Article 66 1219
Knowledge..........................................................................................................................................................
Base Article 67 1220
Knowledge..........................................................................................................................................................
Base Article 68 1221
Knowledge..........................................................................................................................................................
Base Article 69 1222
Knowledge..........................................................................................................................................................
Base Article 70 1223
Knowledge..........................................................................................................................................................
Base Article 71 1224
Knowledge..........................................................................................................................................................
Base Article 72 1225
Knowledge..........................................................................................................................................................
Base Article 73 1226
Knowledge..........................................................................................................................................................
Base Article 74 1228
Knowledge..........................................................................................................................................................
Base Article 75 1230
Knowledge..........................................................................................................................................................
Base Article 76 1232
Knowledge..........................................................................................................................................................
Base Article 77 1233
Knowledge..........................................................................................................................................................
Base Article 78 1234
Knowledge..........................................................................................................................................................
Base Article 79 1235
Knowledge..........................................................................................................................................................
Base Article 80 1236
Knowledge..........................................................................................................................................................
Base Article 81 1238

www.mixtelematics.com
8
 Knowledge..........................................................................................................................................................
Base Article 82 1240
Knowledge..........................................................................................................................................................
Base Article 83 1241
Knowledge..........................................................................................................................................................
Base Article 84 1243
Knowledge..........................................................................................................................................................
Base Article 85 1245
Knowledge..........................................................................................................................................................
Base Article 86 1246
Knowledge..........................................................................................................................................................
Base Article 87 1247
Knowledge..........................................................................................................................................................
Base Article 88 1249
Knowledge..........................................................................................................................................................
Base Article 89 1251
Knowledge..........................................................................................................................................................
Base Article 90 1252
Knowledge..........................................................................................................................................................
Base Article 91 1254
Knowledge..........................................................................................................................................................
Base Article 92 1256
Knowledge..........................................................................................................................................................
Base Article 93 1257
Knowledge..........................................................................................................................................................
Base Article 94 1258
Knowledge..........................................................................................................................................................
Base Article 95 1259
Knowledge..........................................................................................................................................................
Base Article 96 1260
Knowledge..........................................................................................................................................................
Base Article 97 1261
Knowledge..........................................................................................................................................................
Base Article 98 1262
Knowledge..........................................................................................................................................................
Base Article 99 1263
Knowledge..........................................................................................................................................................
Base Article 100 1265
Knowledge..........................................................................................................................................................
Base Article 101 1267
Knowledge..........................................................................................................................................................
Base Article 102 1268
Knowledge..........................................................................................................................................................
Base Article 103 1270
Knowledge..........................................................................................................................................................
Base Article 104 1271
Knowledge..........................................................................................................................................................
Base Article 105 1272
Knowledge..........................................................................................................................................................
Base Article 106 1274
Knowledge..........................................................................................................................................................
Base Article 107 1275
Knowledge..........................................................................................................................................................
Base Article 108 1277
Knowledge..........................................................................................................................................................
Base Article 109 1278
Knowledge..........................................................................................................................................................
Base Article 110 1280
Knowledge..........................................................................................................................................................
Base Article 111 1282
Knowledge..........................................................................................................................................................
Base Article 112 1284
Knowledge..........................................................................................................................................................
Base Article 113 1285
Knowledge..........................................................................................................................................................
Base Article 114 1287
Knowledge..........................................................................................................................................................
Base Article 115 1289
Knowledge..........................................................................................................................................................
Base Article 116 1290
Knowledge..........................................................................................................................................................
Base Article 117 1291
Knowledge..........................................................................................................................................................
Base Article 118 1292
Knowledge..........................................................................................................................................................
Base Article 119 1294
Knowledge..........................................................................................................................................................
Base Article 120 1296
Knowledge..........................................................................................................................................................
Base Article 121 1297
Knowledge..........................................................................................................................................................
Base Article 122 1299
Knowledge..........................................................................................................................................................
Base Article 123 1300
Knowledge..........................................................................................................................................................
Base Article 124 1301
Knowledge..........................................................................................................................................................
Base Article 125 1302
Knowledge..........................................................................................................................................................
Base Article 126 1304
Knowledge..........................................................................................................................................................
Base Article 127 1306
Knowledge..........................................................................................................................................................
Base Article 128 1307
Knowledge..........................................................................................................................................................
Base Article 129 1308
Knowledge..........................................................................................................................................................
Base Article 130 1310
Knowledge..........................................................................................................................................................
Base Article 131 1312
Knowledge..........................................................................................................................................................
Base Article 132 1313
Knowledge..........................................................................................................................................................
Base Article 133 1314

www.mixtelematics.com
9
 Knowledge..........................................................................................................................................................
Base Article 134 1315
Knowledge..........................................................................................................................................................
Base Article 135 1316
Knowledge..........................................................................................................................................................
Base Article 136 1317
Knowledge..........................................................................................................................................................
Base Article 137 1319
Knowledge..........................................................................................................................................................
Base Article 138 1321
Knowledge..........................................................................................................................................................
Base Article 139 1323
Knowledge..........................................................................................................................................................
Base Article 140 1325
Knowledge..........................................................................................................................................................
Base Article 141 1326
Knowledge..........................................................................................................................................................
Base Article 142 1328
Knowledge..........................................................................................................................................................
Base Article 143 1330
Knowledge..........................................................................................................................................................
Base Article 144 1331
Knowledge..........................................................................................................................................................
Base Article 145 1332
Knowledge..........................................................................................................................................................
Base Article 146 1333
Knowledge..........................................................................................................................................................
Base Article 147 1335
Knowledge..........................................................................................................................................................
Base Article 148 1336
Knowledge..........................................................................................................................................................
Base Article 149 1337
Knowledge..........................................................................................................................................................
Base Article 150 1339
Knowledge..........................................................................................................................................................
Base Article 152 1340
Knowledge..........................................................................................................................................................
Base Article 153 1342
Knowledge..........................................................................................................................................................
Base Article 154 1343
Knowledge..........................................................................................................................................................
Base Article 155 1344
Knowledge..........................................................................................................................................................
Base Article 156 1345
Knowledge..........................................................................................................................................................
Base Article 157 1347
Knowledge..........................................................................................................................................................
Base Article 158 1349
Knowledge..........................................................................................................................................................
Base Article 159 1350
Knowledge..........................................................................................................................................................
Base Article 160 1352
Knowledge..........................................................................................................................................................
Base Article 161 1354
Knowledge..........................................................................................................................................................
Base Article 162 1356
Knowledge..........................................................................................................................................................
Base Article 163 1358
Knowledge..........................................................................................................................................................
Base Article 164 1359
Knowledge..........................................................................................................................................................
Base Article 165 1360
Knowledge..........................................................................................................................................................
Base Article 166 1362
Knowledge..........................................................................................................................................................
Base Article 167 1364
Knowledge..........................................................................................................................................................
Base Article 168 1365
Knowledge..........................................................................................................................................................
Base Article 169 1367
Knowledge..........................................................................................................................................................
Base Article 170 1368
Knowledge..........................................................................................................................................................
Base Article 172 1370
Knowledge..........................................................................................................................................................
Base Article 173 1371
Knowledge..........................................................................................................................................................
Base Article 174 1372
Knowledge..........................................................................................................................................................
Base Article 175 1373
Knowledge..........................................................................................................................................................
Base Article 176 1374
Knowledge..........................................................................................................................................................
Base Article 177 1375
Knowledge..........................................................................................................................................................
Base Article 178 1376
Knowledge..........................................................................................................................................................
Base Article 179 1378
Knowledge..........................................................................................................................................................
Base Article 180 1379
Knowledge..........................................................................................................................................................
Base Article 181 1381
Knowledge..........................................................................................................................................................
Base Article 182 1382
Knowledge..........................................................................................................................................................
Base Article 183 1384
Knowledge..........................................................................................................................................................
Base Article 184 1385
Knowledge..........................................................................................................................................................
Base Article 185 1386
Knowledge..........................................................................................................................................................
Base Article 186 1387
Knowledge..........................................................................................................................................................
Base Article 187 1389

www.mixtelematics.com
10
 Knowledge..........................................................................................................................................................
Base Article 188 1392
Knowledge..........................................................................................................................................................
Base Article 189 1393
Knowledge..........................................................................................................................................................
Base Article 190 1394
Knowledge..........................................................................................................................................................
Base Article 191 1395
Knowledge..........................................................................................................................................................
Base Article 192 1396
Knowledge..........................................................................................................................................................
Base Article 193 1398
Knowledge..........................................................................................................................................................
Base Article 194 1400
Knowledge..........................................................................................................................................................
Base Article 195 1401
Knowledge..........................................................................................................................................................
Base Article 196 1402
Knowledge..........................................................................................................................................................
Base Article 197 1404
Knowledge..........................................................................................................................................................
Base Article 198 1406
Knowledge..........................................................................................................................................................
Base Article 199 1408
Knowledge..........................................................................................................................................................
Base Article 200 1410
Knowledge..........................................................................................................................................................
Base Article 203 1411
Knowledge..........................................................................................................................................................
Base Article 204 1412
Knowledge..........................................................................................................................................................
Base Article 205 1414
Knowledge..........................................................................................................................................................
Base Article 206 1416
Knowledge..........................................................................................................................................................
Base Article 207 1418
Knowledge..........................................................................................................................................................
Base Article 208 1419
Knowledge..........................................................................................................................................................
Base Article 209 1420
Knowledge..........................................................................................................................................................
Base Article 210 1421
Knowledge..........................................................................................................................................................
Base Article 211 1422
Knowledge..........................................................................................................................................................
Base Article 212 1424
Knowledge..........................................................................................................................................................
Base Article 213 1425
Knowledge..........................................................................................................................................................
Base Article 214 1427
Knowledge..........................................................................................................................................................
Base Article 215 1428
Knowledge..........................................................................................................................................................
Base Article 216 1429
Knowledge..........................................................................................................................................................
Base Article 217 1432
Knowledge..........................................................................................................................................................
Base Article 218 1433
Knowledge..........................................................................................................................................................
Base Article 219 1435
Knowledge..........................................................................................................................................................
Base Article 220 1436
Knowledge..........................................................................................................................................................
Base Article 221 1437
Knowledge..........................................................................................................................................................
Base Article 222 1438
Knowledge..........................................................................................................................................................
Base Article 223 1439
Knowledge..........................................................................................................................................................
Base Article 224 1440
Knowledge..........................................................................................................................................................
Base Article 225 1442
Knowledge..........................................................................................................................................................
Base Article 226 1444
Knowledge..........................................................................................................................................................
Base Article 227 1445
Knowledge..........................................................................................................................................................
Base Article 228 1446
Knowledge..........................................................................................................................................................
Base Article 229 1447
Knowledge..........................................................................................................................................................
Base Article 230 1448
Knowledge..........................................................................................................................................................
Base Article 231 1449
Knowledge..........................................................................................................................................................
Base Article 232 1450
Knowledge..........................................................................................................................................................
Base Article 233 1451
Knowledge..........................................................................................................................................................
Base Article 234 1452
Knowledge..........................................................................................................................................................
Base Article 235 1454
Knowledge..........................................................................................................................................................
Base Article 236 1455
Knowledge..........................................................................................................................................................
Base Article 237 1457
Knowledge..........................................................................................................................................................
Base Article 238 1458
Knowledge..........................................................................................................................................................
Base Article 239 1459
Knowledge..........................................................................................................................................................
Base Article 240 1461
Knowledge..........................................................................................................................................................
Base Article 241 1463

www.mixtelematics.com
11
 Knowledge..........................................................................................................................................................
Base Article 242 1465
Knowledge..........................................................................................................................................................
Base Article 243 1467
Knowledge..........................................................................................................................................................
Base Article 244 1468
Knowledge..........................................................................................................................................................
Base Article 245 1470
Knowledge..........................................................................................................................................................
Base Article 246 1472
Knowledge..........................................................................................................................................................
Base Article 247 1474
Knowledge..........................................................................................................................................................
Base Article 248 1475
Knowledge..........................................................................................................................................................
Base Article 249 1476
Knowledge..........................................................................................................................................................
Base Article 250 1478
Knowledge..........................................................................................................................................................
Base Article 251 1479
Knowledge..........................................................................................................................................................
Base Article 252 1480
Knowledge..........................................................................................................................................................
Base Article 253 1481
Knowledge..........................................................................................................................................................
Base Article 254 1482
Knowledge..........................................................................................................................................................
Base Article 255 1484
Knowledge..........................................................................................................................................................
Base Article 256 1486
Knowledge..........................................................................................................................................................
Base Article 257 1487
Knowledge..........................................................................................................................................................
Base Article 258 1488
Knowledge..........................................................................................................................................................
Base Article 259 1489
Knowledge..........................................................................................................................................................
Base Article 260 1490
Knowledge..........................................................................................................................................................
Base Article 261 1491
Knowledge..........................................................................................................................................................
Base Article 262 1493
Knowledge..........................................................................................................................................................
Base Article 263 1494
Knowledge..........................................................................................................................................................
Base Article 264 1496
Knowledge..........................................................................................................................................................
Base Article 265 1498
Knowledge..........................................................................................................................................................
Base Article 266 1500
Knowledge..........................................................................................................................................................
Base Article 267 1501
Knowledge..........................................................................................................................................................
Base Article 268 1502
Knowledge..........................................................................................................................................................
Base Article 269 1503
Knowledge..........................................................................................................................................................
Base Article 270 1504
Knowledge..........................................................................................................................................................
Base Article 271 1506
Knowledge..........................................................................................................................................................
Base Article 272 1507
Knowledge..........................................................................................................................................................
Base Article 273 1508
Knowledge..........................................................................................................................................................
Base Article 274 1509
Knowledge..........................................................................................................................................................
Base Article 275 1511
Knowledge..........................................................................................................................................................
Base Article 276 1512
Knowledge..........................................................................................................................................................
Base Article 277 1513
Knowledge..........................................................................................................................................................
Base Article 278 1515
Knowledge..........................................................................................................................................................
Base Article 279 1516
Knowledge..........................................................................................................................................................
Base Article 280 1518
Knowledge..........................................................................................................................................................
Base Article 281 1520
Knowledge..........................................................................................................................................................
Base Article 282 1521
Knowledge..........................................................................................................................................................
Base Article 283 1523
Knowledge..........................................................................................................................................................
Base Article 284 1525
Knowledge..........................................................................................................................................................
Base Article 285 1527
Knowledge..........................................................................................................................................................
Base Article 286 1528
Knowledge..........................................................................................................................................................
Base Article 287 1529
Knowledge..........................................................................................................................................................
Base Article 288 1530
Knowledge..........................................................................................................................................................
Base Article 289 1531
Knowledge..........................................................................................................................................................
Base Article 290 1533
Knowledge..........................................................................................................................................................
Base Article 291 1535
Knowledge..........................................................................................................................................................
Base Article 292 1536
Knowledge..........................................................................................................................................................
Base Article 293 1537

www.mixtelematics.com
12
 Knowledge..........................................................................................................................................................
Base Article 294 1538
Knowledge..........................................................................................................................................................
Base Article 295 1540
Knowledge..........................................................................................................................................................
Base Article 296 1542
Knowledge..........................................................................................................................................................
Base Article 297 1543
Knowledge..........................................................................................................................................................
Base Article 298 1545
Knowledge..........................................................................................................................................................
Base Article 299 1547
Knowledge..........................................................................................................................................................
Base Article 300 1549
Knowledge..........................................................................................................................................................
Base Article 301 1551
Knowledge..........................................................................................................................................................
Base Article 302 1552
Knowledge..........................................................................................................................................................
Base Article 303 1553
Knowledge..........................................................................................................................................................
Base Article 304 1555
Knowledge..........................................................................................................................................................
Base Article 305 1556
Knowledge..........................................................................................................................................................
Base Article 306 1558
Knowledge..........................................................................................................................................................
Base Article 307 1560
Knowledge..........................................................................................................................................................
Base Article 308 1563
Knowledge..........................................................................................................................................................
Base Article 309 1565
Knowledge..........................................................................................................................................................
Base Article 310 1568
Knowledge..........................................................................................................................................................
Base Article 312 1569
Knowledge..........................................................................................................................................................
Base Article 313 1570
Knowledge..........................................................................................................................................................
Base Article 314 1572
Knowledge..........................................................................................................................................................
Base Article 315 1573
Knowledge..........................................................................................................................................................
Base Article 316 1575
Knowledge..........................................................................................................................................................
Base Article 317 1576
Knowledge..........................................................................................................................................................
Base Article 318 1577
Knowledge..........................................................................................................................................................
Base Article 319 1578
Knowledge..........................................................................................................................................................
Base Article 320 1579
Knowledge..........................................................................................................................................................
Base Article 321 1581
Knowledge..........................................................................................................................................................
Base Article 322 1583
Knowledge..........................................................................................................................................................
Base Article 323 1585
Knowledge..........................................................................................................................................................
Base Article 324 1587
Knowledge..........................................................................................................................................................
Base Article 325 1588
Knowledge..........................................................................................................................................................
Base Article 326 1590
Knowledge..........................................................................................................................................................
Base Article 327 1591
Knowledge..........................................................................................................................................................
Base Article 328 1593
Knowledge..........................................................................................................................................................
Base Article 329 1594
Knowledge..........................................................................................................................................................
Base Article 330 1596
Knowledge..........................................................................................................................................................
Base Article 331 1597
Knowledge..........................................................................................................................................................
Base Article 332 1598
Knowledge..........................................................................................................................................................
Base Article 333 1599
Knowledge..........................................................................................................................................................
Base Article 334 1601
Knowledge..........................................................................................................................................................
Base Article 335 1603
Knowledge..........................................................................................................................................................
Base Article 336 1605
Knowledge..........................................................................................................................................................
Base Article 337 1607
Knowledge..........................................................................................................................................................
Base Article 339 1609
Knowledge..........................................................................................................................................................
Base Article 340 1610
Knowledge..........................................................................................................................................................
Base Article 341 1611
Knowledge..........................................................................................................................................................
Base Article 342 1612
Knowledge..........................................................................................................................................................
Base Article 343 1613
Knowledge..........................................................................................................................................................
Base Article 344 1615
Knowledge..........................................................................................................................................................
Base Article 345 1617
Knowledge..........................................................................................................................................................
Base Article 347 1619
Knowledge..........................................................................................................................................................
Base Article 348 1621

www.mixtelematics.com
13
 Knowledge..........................................................................................................................................................
Base Article 349 1623
Knowledge..........................................................................................................................................................
Base Article 350 1624
Knowledge..........................................................................................................................................................
Base Article 351 1626
Knowledge..........................................................................................................................................................
Base Article 352 1628
Knowledge..........................................................................................................................................................
Base Article 353 1630
Knowledge..........................................................................................................................................................
Base Article 355 1634
Knowledge..........................................................................................................................................................
Base Article 356 1637
Knowledge..........................................................................................................................................................
Base Article 357 1639
Knowledge..........................................................................................................................................................
Base Article 358 1641
Knowledge..........................................................................................................................................................
Base Article 359 1643
Knowledge..........................................................................................................................................................
Base Article 360 1644
Knowledge..........................................................................................................................................................
Base Article 361 1646
Knowledge..........................................................................................................................................................
Base Article 362 1647
Knowledge..........................................................................................................................................................
Base Article 365 1649
Knowledge..........................................................................................................................................................
Base Article 366 1651
Knowledge..........................................................................................................................................................
Base Article 367 1652
Knowledge..........................................................................................................................................................
Base Article 368 1654
Knowledge..........................................................................................................................................................
Base Article 369 1655
Knowledge..........................................................................................................................................................
Base Article 370 1657
Knowledge..........................................................................................................................................................
Base Article 371 1658
Knowledge..........................................................................................................................................................
Base Article 372 1660
Knowledge..........................................................................................................................................................
Base Article 373 1661
Knowledge..........................................................................................................................................................
Base Article 374 1662
Knowledge..........................................................................................................................................................
Base Article 375 1664
Knowledge..........................................................................................................................................................
Base Article 376 1666
Knowledge..........................................................................................................................................................
Base Article 377 1668
Knowledge..........................................................................................................................................................
Base Article 378 1671
Knowledge..........................................................................................................................................................
Base Article 379 1673
Knowledge..........................................................................................................................................................
Base Article 380 1675
Knowledge..........................................................................................................................................................
Base Article 381 1676
Knowledge..........................................................................................................................................................
Base Article 383 1677
Knowledge..........................................................................................................................................................
Base Article 384 1678
Knowledge..........................................................................................................................................................
Base Article 385 1680
Knowledge..........................................................................................................................................................
Base Article 386 1681
Knowledge..........................................................................................................................................................
Base Article 387 1682
Knowledge..........................................................................................................................................................
Base Article 388 1684
Knowledge..........................................................................................................................................................
Base Article 389 1686
Knowledge..........................................................................................................................................................
Base Article 390 1688
Knowledge..........................................................................................................................................................
Base Article 391 1689
Knowledge..........................................................................................................................................................
Base Article 392 1691
Knowledge..........................................................................................................................................................
Base Article 393 1693
Knowledge..........................................................................................................................................................
Base Article 394 1695
Knowledge..........................................................................................................................................................
Base Article 395 1696
Knowledge..........................................................................................................................................................
Base Article 396 1697
Knowledge..........................................................................................................................................................
Base Article 397 1699
Knowledge..........................................................................................................................................................
Base Article 398 1701
Knowledge..........................................................................................................................................................
Base Article 399 1702
Knowledge..........................................................................................................................................................
Base Article 400 1703
Knowledge..........................................................................................................................................................
Base Article 401 1704
Knowledge..........................................................................................................................................................
Base Article 402 1706
Knowledge..........................................................................................................................................................
Base Article 403 1708
Knowledge..........................................................................................................................................................
Base Article 404 1709

www.mixtelematics.com
14
 Knowledge..........................................................................................................................................................
Base Article 405 1710
Knowledge..........................................................................................................................................................
Base Article 406 1711
Knowledge..........................................................................................................................................................
Base Article 407 1713
Knowledge..........................................................................................................................................................
Base Article 408 1715
Knowledge..........................................................................................................................................................
Base Article 409 1717
Knowledge..........................................................................................................................................................
Base Article 410 1718
Knowledge..........................................................................................................................................................
Base Article 411 1719
Knowledge..........................................................................................................................................................
Base Article 412 1721
Knowledge..........................................................................................................................................................
Base Article 413 1723
Knowledge..........................................................................................................................................................
Base Article 414 1724
Knowledge..........................................................................................................................................................
Base Article 415 1725
Knowledge..........................................................................................................................................................
Base Article 416 1727
Knowledge..........................................................................................................................................................
Base Article 417 1728

www.mixtelematics.com
15
 1

1 Fleet Manager Documentation

© 2008 MiX Telematics | Updated 2008/06/11

Overview
The Fleet Manager product range offers powerful and flexible solutions designed to satisfy the diverse requirements of fleet
managers and other mobile asset managers the world over.

The Fleet Manager system combines world class hardware and software components into fully integrated solutions designed to
monitor, record, analyse and improve driver and vehicle performance. Information from the system can be used to improve
productivity, increase efficiency, promote good driving techniques, improve safety and reduce fleet operating costs.

Fleet Manager Professional

Fleet Manager Professional (FM Professional) is an enterprise solution, designed to leverage the power and flexibility of the full
range of Fleet Manager on-board computers, accessories and peripherals. FM Professional is a client-server application which
can run on a stand-alone computer or scale to run with components distributed across a local area network (LAN), wide-area
network (WAN) or even the Internet.

FM Professional includes functionality for monitoring and managing driver and vehicle performance, controlling communications
costs, reporting on fleet operating costs, active (real-time) and passive (after-the-fact) tracking of vehicles and drivers, location
management, communications and messaging, route planning and variance reporting, trailer management, vehicle maintenance
reporting, service reminders and much more.

FM Professional includes the powerful Fleet Manager Communications Suite and a comprehensive collection of Extensions (add-
on's) designed to meet the unique requirements of diverse vertical markets such as exploration and safety, materials handling
and others.

FM-Web
The FM-Web service supplies the information you need using the web and e-mail. If you have access to the Internet you can
access your fleet information anytime, anywhere, thus significantly lowering your total cost of ownership. Behind the scenes, the
bureau service takes care of data transfer, administration and management of your vehicle data, while an extensive security
model ensures the right people see the right information.

FM-Web is however not covered in this documentation.

1
www.mixtelematics.com

1
 2

2 Fleet Manager Dealer Utility

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The Fleet Manager system offers a unique, low cost method of transferring data to and from Fleet Manager on-board computers
by using code-plugs. Green vehicle code-plugs can be used for downloading trip, event and interval (tacho) data as well as for
uploading device drivers (firmware) and event configurations to vehicles. Code-plugs can also be used for setting the date and
time on the on-board computer, for driver identification, for diagnostics and a number of other purposes.

The FM Dealer Utility is used to initialise and manage code-plugs. This section provides an overview of the different code-plugs
and their uses.

The FM Dealer Utility is also used as the primary means for distributing device driver (firmware) updates for FM200 series on-
board computers.

This document describes the following code-plugs:

· Vehicle code-plug

· Driver code-plug

· Passenger code-plug

· Co-driver code-plug

· Device Driver code-plug

· System Override code-plug

· Calibration code-plug

· Diagnostic code-plug

· Engine-hours code-plug

· Multi-plug

Vehicle code-plug

The green vehicle code-plug is used to transfer information between the office software and the on-board computer. Three
different capacities are available namely 32kb, 96kb and 256kb.

A green code-plug is used to download trip, event and interval (tacho) data from a Fleet Manager on-board computer as well as
to upload configuration parameters defined using the Fleet Manager application software.

A 256kb green code-plug can be used to upload new device drivers (firmware) into an FM200 series on-board computer (see the
Device Driver code-plug section below).

2
www.mixtelematics.com

2
 3

Driver code-plug

The blue driver code-plug is a 128 byte code-plug used specifically by drivers. The driver code-plug carries a driver ID number as
well as a vehicle access list (a list controlling the driver's access to the vehicles in the fleet).

The blue code-plug can also be used to set the date and time in the on-board computer.

Passenger code-plug

The black passenger code-plug is a 128 byte code-plug used to identify a passenger boarding or exiting a vehicle equipped with
an FM200 series on-board computer. When a passenger boards a vehicle, he/she inserts their code-plug into the code-plug
socked and then removes it. The date and time of the identification and the odometer reading of the vehicle are recorded together
with the passenger's ID number in the on-board computer's memory.

Co-Driver code-plug

The Co-Driver plug is a 128 byte code-plug used in conjunction with the FM TCO Interface, which enables FM200 series on-
board computers to utilize tachograph information for fleet management purposes. The Co-Driver plug is used to identify co-
drivers and their activities.

Device Driver code-plug

FM200 series on-board computers are fully re-programmable. The programs for the on-board computers take the form of device
driver files that are uploaded to on-board computer. A 256kb green code-plug can be used for this purpose.

System Override code-plug

A System Override code-plug can be used by the driver to override one or more of the following functions in an emergency:

· The immobiliser relay of the on-board computer

· The buzzer

3
www.mixtelematics.com

3
 4

· The external relay drives of the on-board computer

Any 128 byte code-plug (blue, black, orange or violet) can be initialised as a system override code-plug using the FM Dealer
Utility.

Calibration code-plug

The violet calibration code-plug is a 128 byte code-plug used during the installation of the on-board computer. There are two
types of calibration plugs - RPM and Speed. The FM Dealer Utility can be used to configure the calibration code-plug.

GPS Speed Auto-calibration

FM200 Plus series units with GPS receivers connected will auto-calibrate the speed input using information from the GPS
receiver. See the FM Dealer Utility User Manual for more information.

Diagnostic code-plug

A diagnostic code-plug is used check whether devices connected to the on-board computer are functioning correctly. The
following devices can be checked using a diagnostic code-plug:

· GPS receiver

· DECT / GSM modem

· FM Trailer ID

Any 128 byte code-plug (blue, black, orange or violet) can be initialised as a diagnostic code-plug using the FM Dealer Utility.

Engine hours code-plug

An engine hours code-plug is used to set the hour meter reading on FM200 series on-board computers which have been
configured to record engine hours.

Any 128 byte code-plug (blue, black, orange or violet) can be initialised as an engine hours code-plug using the FM Dealer Utility.

Multi-plug

A multi-plug is a green vehicle code-plug that has been initialised in such a manner that it can be used to download from any
vehicle. The Multi-plug can be inserted into any vehicle and it will download the data from the vehicle. Once the data is
downloaded onto the code-plug, the code-plug can be inserted into the Downloader Pod, to download the data into the Fleet
Manager software. The Fleet Manager software then clears the multi-plug so that it can be used to download data from any
vehicle again. Any green code-plug can be initialised as a multi-plug using the FM Dealer Utility.

4
www.mixtelematics.com

4
 5

2.1 FM Dealer Utility User Manual

© 2008 MiX Telematics | Updated 2008/07/03

Overview
The FM Dealer Utility is used to initialise and manage code-plugs. It is also used as the primary means for distributing device
driver (firmware) updates for FM200 series on-board computers.

It can be installed either as a stand-alone program or as an Extension to the Fleet Manager Professional software. The latest
version of the FM Dealer Utility can be downloaded on the Fleet Manager web site at http://www.fm-web.co.za

Important notice: If you have any of the following on-board computers (FM200 Plus, FM200 Locator, FM200 Communicator, FM
Messenger, FM Navigator), please refer to the various FM200 Plus sections of the documentation.

· Installing FM Dealer Utility

· Password Protection

· Function Descriptions

File

· Closing the Application

Settings

· Language Settings

· Managing Password Protection

· Port Settings

Code Plug

· Dump Plug

· Restore Plug

· Format Plug

· Initialise Plug

· Load Device Drivers

· Load Config (Configuration)

· Calibrate Plug

· Clear Unit

· Set Date/Time

· Set Odometer

· Plug Info

Installing FM Dealer Utility

5
www.mixtelematics.com

5
 6

Stand-Alone Application

The installation set of the Stand-Alone version can be found on the Fleet Manager CD. The installation set will create a shortcut
to the FM Dealer under START -> Programs -> Fleet Manager Office -> Fleet Manager Dealer Utility.

Extension

The extension can be installed by selecting the appropriate tick box as part of the Fleet Manager Office install set.

After installation the extension will load as part of your Fleet Manager software and can be run from the Fleet Manager’s TOOLS -
> DEALER UTILITY menu.

Password Protection
The FM Dealer utility can be password protected for access-control purposes. This should be done as soon as possible after
installation, if security is required.

Function Descriptions

File

Closing the Application

Close the Fleet Manager Dealer Utility program.

Settings
Language Settings

Selects the FM Dealer operating language.

Managing Password Protection

Allows you to enter a new password or change an existing password. When doing the latter, you will need to specify your current
password for the operation to complete. Specifying and confirming a new blank password will remove password protection.

6
www.mixtelematics.com

6
 7

Port Settings

Select the communication port onto which your code-plug reader is installed. This option is not available on the FM Dealer
Extension since it uses the Fleet Manager port setting.

Code Plug
Dump Plug

Copy (dump) the contents of a Code Plug to a Binary file.

Enter a file name and click Save to dump the contents of the Code Plug to the file.

The file can be restored (loaded back) to a similar plug by using the Restore Plug command

Restore Plug
Restore a Binary file (created by the Dump Plug command) to a code plug. Please note that the plug used must be of the same
size as plug dump file. Restoring a 256kB file to a 128 byte plug, for example, may corrupt the plug.

7
www.mixtelematics.com

7
 8

Format Plug

Vehicle Plug Format a FM100, FM200, FM200 Plus or “Multi Plug” data plug to its factory settings. The plug
may be initialised to a vehicle ID after this operation (except if it’s a Multi Plug), which will
assume the vehicle ID once a download starts.

Driver Plug Format a driver ID plug to its factory settings. The plug may be initialised to a driver ID after this
operation.

Co-Driver Plug Format a co-driver ID plug to its factory settings. The plug may be initialised to a co-driver ID
after this operation.

Passenger Plug Format a passenger plug to its factory settings. The plug may be initialised to a passenger ID
after this operation.

Device Drivers Create a FM200 or FM200 Plus Device Driver Plug. A Device Driver Plug is used to load device
drivers onto multiple vehicles. Loading the device drivers is discussed later in this document.

System Override Create a System Override plug. This plug may be used to override engine protection.

Calibration Plug Format a plug to an RPM- or Speed-calibration plug and initialises it to its default values.

Diagnostic Plug Format a plug to a GPS, GSM/DECT or TrailerID diagnostic plug. With ignition switched on,
inserting these plugs will indicate GPS, GSM/DECT or TrailerID activity.

Engine-hours Plug Format a plug to an Engine-hours plug. The plug may be initialised with a specific value of
engine hours.

Initialise Plug
Set Vehicle ID

Initialise an FM100, FM200 of FM200 Plus vehicle plug to a specific vehicle ID. You may also elect to update the FM200 Plus (or
any on-board computer within the FM200 range) vehicle unit to this new ID.

8
www.mixtelematics.com

8
 9

Important Notice: Do not answer yes to this question unless you specifically want to change the vehicle ID!

Set Driver ID

Initialise a driver plug to a specific driver ID.

Set Co-Driver ID

Initialise a co-driver plug to a specific co-driver ID.

Set Passenger ID

Initialise a passenger plug to a specific passenger ID.

System Override

Initialise a system override plug to a specific vehicle ID.

Set Engine-hours

Initialise an Engine-hours plug to a specific value

Load Device Drivers

This function allows you to load new device drivers (DDRs/DDXs) to the range of FM200 on-board-computers. It also allows you
to load new device driver modules (DDMs) to the FM Terminal (if you have one connected).

FM200 Device Drivers

9
www.mixtelematics.com

9
 10

Use this set to update the device drivers on your FM200. This set of Device Drivers support the following:

GSM FM Terminal

DECT FM Info

FM TCO/ KTCO Interface

FM200 Plus Device Drivers

Use this set to update the device drivers on your FM200 Plus. These Device Drivers will support the following:

GSM/GPRS FM Terminal

DECT FM Info

FM TCO/ KTCO Interface FM Trailer ID

FM Impact Sensor FM Keypad

FM Terminal: Modules

Use this set to update the device driver modules on your FM Terminal.

10
www.mixtelematics.com

10
 11

Load Config (Configuration)

Basic Config

Load a basic configuration onto the vehicle unit. This allows the FM200 or FM200 Plus on-board computer to start logging data
without first having to install the Fleet Manager software.

Calibrate Plug
Please note that for any calibration plug to work, the vehicle ignition must be switched on!

Manual

Allows manual RPM or Speed calibration to be done on the vehicle. Use a previously formatted RPM-calibration or Speed-
calibration plug.

11
www.mixtelematics.com

11
 12

Automatic

Allows automatic RPM or Speed calibration to be done on the vehicle. Use a previously formatted RPM-calibration or Speed-
calibration plug.

Transfer

Allows RPM or Speed calibration values to be transferred from one vehicle to another. Use a RPM transfer plug to acquire RPM
calibration values, and use a Speed transfer plug to acquire Speed calibration values. Inserting this plug into a vehicle deciphers
the relevant calibration value of that vehicle. Inserting the plug into new vehicle (or vehicles) calibrates it to the same setting.

GPS Speed Auto-calibration

FM200 Plus series units with GPS receivers connected will auto-calibrate the speed input using information from the GPS
receiver. Auto-calibration will only take place when a unit has a GPS receiver physically connected and correctly configured,
provided the unit has not yet been calibrated with a calibration code-plug.

If you wish to auto-calibrate a unit that has already been calibrated using a calibration code-plug, you may reset the calibration to
factory defaults by using a Speed (Auto GPS) calibration code-plug. Insert this plug into the FM until three short beeps are heard
and follow the steps below:

12
www.mixtelematics.com

12
 13

1. Ensure that a good quality speed signal from the vehicle is connected to the unit's speed input line.

2. The GPS receiver must have GPS lock and the signal quality must be as strong as possible (it would be beneficial to mount
the GPS antenna on the roof of the vehicle for best possible GPS reception).

3. The vehicle must be driven at 60km/h or faster (80km/h is preferable).

4. Speed must be kept as constant as possible for at least 3 seconds.

5. The unit will beep 3 times when it has established a calibration value.

Note: depending on the GPS signal quality, using GPS speed auto-calibration may be less accurate than calibrating the unit over
a fixed distance.

Diagnostic

Allows a diagnostic calibration plug to be created. Use a previously formatted RPM-calibration or Speed-calibration plug. With
ignition switched on, inserting these plugs will indicate RPM or Speed activity.

Speed and Sensitivity Calibration

The sensitivity of the Speed and RPM input lines can be adjusted using a Sensitivity Calibration Plug.

1. Select Code Plug->Format Plug->Calibration Plug->Speed & RPM Sensitivity.

2. Select which to change: either Speed or RPM, or both. The unselected value will remain unchanged.

3. Select the sensitivity level:

· Less Sensitive for large thresholds, requiring large amplitude signals to be detected, and

· More Sensitive for small thresholds, requiring small amplitude signals to be detected.

The sensitivity setting cannot be read back from the OBC unit, only set using the Sensitivity Calibration Plug.

The default is set to Average Sensitivity, which should be compatible with a wide variety of signal sources. Setting the sensitivity
too high can cause erroneous reading of noisy signals embedded in the required signal. Setting the sensitivity too low may cause
the required signal to be read intermittently, or not at all. The recommended setting is on average. Adjust if the obtained readings
during a calibration and/or verification trip appear random (noisy).

13
www.mixtelematics.com

13
 14

Clear Unit
Clear FM200 / FM200 Plus Memory

Enter the vehicle ID and click OK. Insert the plug into the vehicle to clear the FM200 or FM200 Plus memory.

Clear FM100 Memory

Use this option to clear the FM100 memory.

Clear Device Drivers (FM200/ FM200 Plus)

Use this option to clear only the Device Drivers from the FM200 / FM200 Plus.

Set Date/Time
Set the time on the plug, for upload to the vehicle unit. Remember to insert the plug into the vehicle immediately, or allow for a
few minutes delay by increasing the clock artificially.

14
www.mixtelematics.com

14
 15

The setting of the Date/ Time is done using a Driver code-plug.

Set Odometer
Set the vehicle odometer using a vehicle code-plug. Insert the plug into the vehicle to complete the operation.

Plug Info
Plug Info

Displays general plug information on the main form.

Device Driver Info

Displays Device Driver information for a FM200 / FM200 Plus code plug or a Device Driver plug.

15
www.mixtelematics.com

15
 16

16
www.mixtelematics.com

16
 17

3 Fleet Manager Professional

© 2008 MiX Telematics | Updated 2008/05/07

Overview
Fleet Manager Professional (FM Professional) is an enterprise solution, designed to leverage the power and flexibility of the full
range of Fleet Manager on-board computers, accessories and peripherals. FM Professional is a client-server application which
can run on a stand-alone computer or scale to run with components distributed across a local area network (LAN), wide-area
network (WAN) or even the Internet.

FM Professional includes functionality for monitoring and managing driver and vehicle performance, controlling communications
costs, reporting on fleet operating costs, active (real-time) and passive (after-the-fact) tracking of vehicles and drivers, location
management, communications and messaging, route planning and variance reporting, trailer management, vehicle maintenance
reporting, service reminders and much more.

FM Professional includes the powerful Fleet Manager Communications Suite and a comprehensive collection of Extensions (add-
on's) designed to meet the unique requirements of diverse vertical markets such as exploration and safety, materials handling
and others.

Features

FM Professional has a familiar Microsoft Outlook-like look and feel, making it easy to use.
Familiar Look and Feel
The Windows-type tree view and shortcut bar provides quick access to commonly used
features.

The shortcut bar contains links to the most frequently used functions and reports. Shortcuts
Shortcut Bar
to your favourite reports and graphs can be added to the shortcut bar.

FM Professional makes it easy to manage vehicle, driver and passenger details including
Vehicle, Driver and Passenger
service and license reminders.
Details

Configure your Fleet Manager on-board computers, accessories and peripherals easily using
Manage and Configure
the powerful yet easy to use Device and Event Wizards. Wizards simplify complex tasks by
Equipment
breaking them down into a series of easy to understand steps. Decide which events should
be monitored and recorded by your on-board computers. Set threshold values such as speed
and RPM limits etc.

Define your own powerful events to detect conditions important to you for example entry into
Customised Events *
a no-go zone.

Over 20 standard reports and graphs are available to help fleet owners understand more
Management Reporting
about performance and utilization of their vehicles and drivers.

Track your vehicles on a digital map. Various tracking methods are available to suit your
Vehicle Tracking *
business requirements.

FM Professional provides a variety of options for the transfer of data between the vehicle and
Multiple Communications Options
the office. Data transfer can be done manually using code-plugs or automatically using DECT
*
(short range) or the GSM network (long range)

Keep in contact with your drivers using cost-effective technologies such as GSM SMS or
Messaging and Jobs *
GPRS. FM Professional gives you full control over communications costs, allowing you to
decide which information is important enough to be sent in real-time and which information
can be downloaded later using cheaper communications methods.
Send your drivers job instructions and monitor job progress. Seamless integration with a
range of navigation systems ensures drivers can concentrate on their driving without worrying
about how to get there.

A variety of Extensions (add-on's) to FM Professional are available providing additional

Various Extensions Available
functionality.

17
www.mixtelematics.com

17
 18

FM Professional supports accessories and peripherals such as GPS receivers, GSM

Support for Accessories
modems, FM DECT, FM Terminal, FM Info, FM Trailer ID, FM Keypad, FM Impact Sensor
and others.

FM Professional is a client-server application which can run on a stand-alone computer or

Scalable architecture
scale to run with components distributed across a local area network (LAN), wide-area
network (WAN) or even the Internet.

FM Professional can run on a stand-alone computer using the free SQL Server Database
Microsoft SQL Server Database Engine included with the software or it can be integrate into the company's existing SQL
Technology Server infrastructure.

FM Professional supports over 11 different languages, daylight savings, different units of

Internationalised measure and different currencies.

* not applicable to FM100 on-board computers

Reports and Graphs

Various reporting levels are available, including individual driver or vehicle reports, reports based on user-defined groups,
reports by site and summary reports. Selection criteria can be saved and re-used to simplify the generation of frequently used
reports and graphs. Shortcuts to your favourite reports and graphs can be added to the shortcut bar. Your company's logo can
be used in reports in place of the standard logo.

Activity Timeline One of the most powerful features of FM Professional is the Activity Timeline which provides
an interactive graphical overview of vehicle and driver activities during a 24 hour period. Trips
and events are displayed graphically on the timeline. Clicking on an item in the timeline or
selecting a time period by dragging your mouse displays the details of what took place.

Trip Report Available with varying levels of detail, the trip report shows trip start, depart, arrival and end
times, driving time, idling time, parking time, maximum speed, average speed, distance
driven, odometer reading and more.

Event Report Displays the number of occurrences, duration and value of all or selected events (including
your own custom events) for the specified time period.

Driving Errors Report Provides an overview of driver performance. Shows a summary of driving errors.

Driver Scoring Report The Driver Scoring Report is an objective matrix calculating driver scores using a set of user-
defined parameters. An Advanced Driver Scoring Extension is also available.

Accident Analysis The Interval (Tacho) Data Graph displays the second-by-second values of speed, RPM and
other inputs such as headlight status, brake pedal status etc. This detailed information is
useful for performing accident analysis.

Fuel Consumption The Fuel Consumption reports show fuel consumption and highlight variances against targets.
Reports can be based on captured fuel transactions, actual fuel usage measured by the on-
board computers or a comparison of the two.

Performance Summary The Performance Summary Report is a utilisation report displaying the percentage driving
time, idling time, standing time, distance driven and more, allowing you to monitor vehicle and
driver utilisation.

Graphs A number of powerful graphs are available.

18
www.mixtelematics.com

18
 19

Additional Reports and Graphs A variety of Extensions exist which provide additional reports and graphs.

Mapping and Tracking

Various map viewers are available to display the geographical position of the vehicles. The Fleet Manager GPS Log Viewer for
MapPoint covers Europe and North America. Other Fleet Manager GPS Log Viewers and FM Map Sets exist to cover regions
such as South Africa, Africa, Australia, Taiwan, Chile etc.

Active Tracking
FM Professional supports tracking of vehicles in real-time, known as Active Tracking. You can start or stop tracking a vehicle by
sending an instruction from the office. The on-board computer can also be configured to initiate tracking automatically when user-
defined events or conditions are detected.

Passive Tracking
FM Professional supports tracking of vehicles after-the-fact, known as Passive Tracking. Once trip data has been downloaded
and stored in the Fleet Manager Database, you can view the routes your vehicles took on an interactive map or by using the
extensive suite of Location Reports. This enables you to monitor the routes drivers take and highlight vehicles entering and/or
exiting pre-defined locations. You can also configure the on-board computers to record the GPS position when specific events
occur and view where the vehicle was when events occurred.

19
www.mixtelematics.com

19
 20

3.1 Installing Fleet Manager Professional 9

© 2008 MiX Telematics | Updated 2008/06/25

Minimum Requirements
Below are the minimum requirements for installing Fleet Manager Professional 9.

Operating System Windows 2000, Windows XP Professional

Processor Pentium IV 1.6 GHz or higher

Disk Space 1 GB free disk space

RAM 512 MB

Database Server MS SQL Server 7 SP4

CD-ROM Drive

Overview
Installation of the Fleet Manager Professional 9 software is accomplished by running a single setup program from the Fleet
Manager Professional 9 CD-ROM. The installation process consists of several steps and takes approximately 30 to 60 minutes to
complete.

The setup program has been designed to restart after the machine reboots. If your computer requires that you log in before using
it, you must log in before the setup program will restart. In the event that the setup program does not restart automatically, you
can run it again manually. It will then continue at the correct point in the setup process.

Upgrading From a Previous Release

If you have a version of the Fleet Manager software installed on your computer that is older than version 8, please uninstall this
before proceeding with the Fleet Manager Professional 9 installation. Different versions of the Fleet Manager Professional
software are not designed to run side-by-side on the same computer. You must also ensure that all old versions of Fleet Manager
Extensions are uninstalled.

If you are upgrading from a beta release of Fleet Manager Professional, you must uninstall the beta release and all related
software, such as the Fleet Manager Professional Communications Suite, before starting the installation.

If you are upgrading from a previous (non-beta) release of Fleet Manager Professional, you should also uninstall the previous
version before starting the installation. Create a backup of the Fleet Manager database using the Backup function of the Fleet
Manager Administrator Utility before starting the installation.

The Installation Process

Step 1. Starting the installation

Run the program by inserting the Fleet Manager Professional 9 CD. A start up screen will appear. Select your preferred language
and select "Install Software".

Click on "Install Fleet Manager Professional 9" and the Installation Program will automatically be launched.

If you want to run it manually, you can access the Installation Program from the following directory on the CD: D:\Fleet Manager
Professional\FleetManagerProfessional.exe. This assumes that your CD drive is your D drive. If not, replace the D in the
command with the correct drive letter.

20
www.mixtelematics.com

20
 21

Step 2: The Setup Wizard

Once the setup program has started, it will prompt you to select a language for the installation process. Select a language from
the drop-down box and click the OK button.

Next, the setup wizard will display a series of dialogs. Navigate through these dialogs by clicking the Next> and <Back buttons.

The first step of the setup wizard is a welcome dialog. Please take note of the instruction to ensure that no other programs are
running on your personal computer before clicking the Next> button to continue.

The second step of the setup wizard displays the end user license agreement for the Fleet Manager software. Please make sure
you read this agreement. Clicking the Yes button of this step indicates your acceptance of the terms and conditions of the
agreement.

21
www.mixtelematics.com

21
 22

The Third step of the setup wizard is to choose a Typical or a Custom installation. If you do not want to install any additional
extensions, select Typical. If you want to install additional extensions, select Custom.

The fourth step of the setup wizard allows you to select the folder into which the Fleet Manager software is to be installed. You
may click the Browse button to select a different folder for Fleet Manager if required.

22
www.mixtelematics.com

22
 23

The setup wizard allows you to specify a name for the Fleet Manager program folder.

If you have selected the Custom installation, you will now be able to select which Extensions to install.

Note: Do not choose to install all Extensions unless you are certain that you require all of them. Should you choose to install all
Extensions, the Fleet Manager Client application will not be able to load all of them simultaneously. You will need to unload some
extensions in order to be able to load others. A message will be displayed when you run the Fleet Manager Client application with
instructions on how to do this.

23
www.mixtelematics.com

23
 24

The setup wizard will ask you whether you would like to install Microsoft SQL Express.

If you choose not to install the SQL Express on your computer and connect to a Fleet Manager database on another computer
elsewhere on the network, you will need to install the Microsoft SQL Client Connectivity Tools. These components are required to
run the Fleet Manager Professional software and are included in the SQL Express installation. If you do not have an existing SQL
installation on your computer, it is recommended that you install the SQL Express.

If you already have Microsoft SQL Server 7 or higher installed on your computer, the "DO NOT install SQL" option will be selected
by default.

Note: If you already have Microsoft SQL Server 7 or higher installed, you must ensure that you have the latest service pack
installed. FM Professional 9 requires SQL Server 7 SP4 or later or SQL Server 2000 SP3 or later. The install set cannot verify
that you have a suitable service pack installed and the software will fail to run correctly if you do not have the appropriate service
pack installed.

If you are modifying an existing installation of Fleet Manager Professional where you chose to install SQL, selecting the "DO NOT
install SQL " option will uninstall SQL from your computer.

The setup wizard will ask you to select the port to which the FM Download Module is connected. Options are:

· There is no FM Download Module connected to this computer

· LPT1

· LPT2

· USB

24
www.mixtelematics.com

24
 25

The fifth step of the setup wizard allows you to specify whether you would like driver reports to be enabled or not. In some
regions, it is unlawful to generate reports that provide a direct comparison of drivers.

Fleet Manager Professional 9 will now be installed to your computer.

25
www.mixtelematics.com

25
 26

Restarting your System

The setup program has been designed to restart automatically after you computer restarts. If your computer requires that you log
in before using it, you must log in before the setup program will restart. In the event that the setup program does not restart
automatically, you can run it again manually. It will then continue at the correct point in the setup process.

Creating or Upgrading the Database

After the restart, the setup program will launch the database creation program, which will prompt you for information required to
create the Fleet Manager database, or update it if you are upgrading from a previous release.

Select a language and click OK. The language you select here will be used by the database creation program to name objects in
the Fleet Manager database.

Creating a new Fleet Manager database on the local computer:

If you elected to install the SQL Express on your computer in the Fleet Manager Professional setup, and would like the Fleet
Manager database to be created on the local computer, click OK.

26
www.mixtelematics.com

26
 27

Upgrading an existing database on the local computer:

If you wish to upgrade an existing Fleet Manager database located on this computer, enter the appropriate credentials and select
the database to be upgraded, then click OK.

The following databases can be upgraded:

· Fleet Manager Professional 9.00

· Fleet Manager Professional 8.37

· Fleet Manager Professional 8.35

· Fleet Manager Professional 8.32

· Fleet Manager Professional 8.31

· Fleet Manager Professional 8.21

· Fleet Manager Professional 8.12

· Fleet Manager Professional 8.11

and all Tripmaster versions:

· Tripmaster Professional 9.00

· Tripmaster Professional 8.37

· Tripmaster Professional 8.35

· Tripmaster Professional 8.32

If you need to upgrade a database from an older software version, please contact your dealer.

Creating a new Fleet Manager Professional 9 database on a SQL Server located elsewhere on the network:

If you would like to create a new Fleet Manager Professional 9 database on a SQL Server located elsewhere on the network,
enter the Server’s name and appropriate login credentials as well as a name for the new database, then click OK.

Upgrading an existing Fleet Manager database on a SQL Server located elsewhere on the network:

If you would like to upgrade an existing Fleet Manager database on a SQL Server located elsewhere on the network, enter the
Server’s name and appropriate login credentials, then select the database to be upgraded before clicking OK.

The following databases can be upgraded:

· Fleet Manager Professional 9.00

· Fleet Manager Professional 8.37

· Fleet Manager Professional 8.35

· Fleet Manager Professional 8.32

27
www.mixtelematics.com

27
 28

· Fleet Manager Professional 8.31

· Fleet Manager Professional 8.21

· Fleet Manager Professional 8.12

· Fleet Manager Professional 8.11

and all Tripmaster versions:

· Tripmaster Professional 9.00

· Tripmaster Professional 8.37

· Tripmaster Professional 8.35

· Tripmaster Professional 8.32

Note: You cannot restore a database from a backup on a CD or across a network. You need to copy the backup to a local drive
first.

If you chose to create a new Fleet Manager database, the database creation program will require confirmation. Click Yes.

At this point you can choose whether to create a new empty database, or create a new database from a backup of an FM2001
SR2 (or later) database.

If you are creating a new database, the database creation program will prompt you for a physical disk file name for the new
database. The physical file name will default to match the logical database name. You need not change this under normal
circumstances.

If you have selected to upgrade from a backup of a Fleet Manager database you will be prompted to select the database backup
file. This can be entered manually if you know the path, or it can be selected by clicking on the Browse button.

The programme will now create a new database or upgrade an existing database as required.

Once the database has been created or upgraded successfully, a message box will be displayed. Click OK. You may now run the
Fleet Manager Professional 9 application.

Troubleshooting
There may be known issues that have been encountered when installing the Fleet Manager Professional 9 software under certain
specific conditions. These issues, solutions and/or workarounds will be described in knowledge base articles, which are located
on the Fleet Manager web site at http://www.mixtelematics.com

Knowledge Base
To access the knowledge base, click on ‘Search the Knowledge Base’ at the top of the page. The knowledge base search page
will be displayed in your browser. Enter “Fleet Manager Professional 9 install” in the keywords field (without the quotes), and click
the search button.

Please note: The knowledge base search facility does not work correctly with Microsoft Internet Explorer version 3.x.

If you are not able to locate an article describing the problem you are experiencing, please contact the distributor. However, in
urgent cases where a timely solution cannot be reached it is possible to log a request directly with the development teams via this
web site.

Log a Service Request

28
www.mixtelematics.com

28
 29

To log a support request, click on the “Support” link in the menu bar home page. Enter your details and the details of the problem
you are experiencing before clicking the Submit button. Please enter the exact description of any error messages that are
displayed. The more information you are able to provide, the easier it will be for our developers to locate and correct the problem.

Alternatively, please contact your local dealer for support.

29
www.mixtelematics.com

29
 30

3.2 Registering Fleet Manager Professional

© 2008 MiX Telematics | Updated 2008/05/07

The Fleet Manager Professional software must be registered under the FM Upgrade+ Programme before it can be run. Please
contact your Fleet Manager dealer for more information regarding the FM Upgrade+ Programme and to purchase FM Upgrade+
packages.

If you have already obtained FM Upgrade+ Packages, you can visit the Fleet Manager Upgrade+ website to complete your
registration and obtain a registration code for your software.

30
www.mixtelematics.com

30
 31

3.3 FM Upgrade+ (Registering Your Software)

© 2008 MiX Telematics | Updated 2008/06/25

Overview
Each customer must purchase FM Upgrade+ packages to register the FM Professional software for their fleet. The FM Upgrade+
packages enable the customer to obtain the registration code needed to activate the software. Registered customers are entitled
to new version/s of the Fleet Manager Professional software and firmware released during the 365 day period following the date
of registration free of charge (excluding consultancy, installation and setup costs which may be incurred).

After the one year FM Upgrade+ coverage period has elapsed, the software will remind the customer to renew their FM Upgrade+
cover every time it is run. Renewal is optional, but the customer will be reminded by the software to renew irrespective of whether
or not they elect to do so.

As an incentive to renew, customers are offered a substantial discount (30% less than the price of new packages), provided they
renew within 60 days of expiry. Customers should be encouraged to renew, as doing so ensures that they are running the latest
version of the Fleet Manager Professional software, simplifying the support process and guaranteeing them access to the latest
features and benefits.

If a customer elects not to renew their FM Upgrade+ cover, their software will continue to operate, but they will not be entitled to
receive new versions of the software or firmware from that point onwards. Should the customer require the latest version of the
Fleet Manager Professional software or firmware at a later stage, they will need to purchase new FM Upgrade+ packages again
at the full price.

How to Register
Each FM Upgrade+ package contains a code used to register 10, 25, or 50 vehicles. The registration process accepts multiple
package numbers and issues a single registration code for the fleet. For example, if a customer requires a registration code for
35 vehicles, he must purchase a 25-vehicle package and an additional 10-vehicle package. If a customer will register 20 vehicles,
he should purchase two 10-vehicle packages. If a customer will register one vehicle, he must purchase the minimum 10-vehicle
package.

After obtaining the FM Upgrade+ package numbers, log onto the FM Upgrade+ web site at http://www.upgrade-plus.com . You
may also call the technical support department in your region to assist you with this process.

Click on the link "Activate Upgrade+ Package".

31
www.mixtelematics.com

31
 32

Select whether you have activated a previous FM Upgrade+ package before.

· If you have not registered a package before, enter the new package number in the text boxes provided, and press "Submit".

· If you have registered FM Upgrade+ packages before, enter an existing FM Upgrade+ package number, press "Submit" and
follow the instructions from there.

If this is your first registration, scroll down the and enter information into the appropriate boxes. Also, make sure the date format is
correct (dd/mm/yyyy).

When finished, click on "Registered Packages", where your registration code will appear. You will also be able to change your
software version on this page.

Run the Fleet Manager software.

The following screen will appear:

Click Yes if you have a registration code.

Enter the company name and registration code exactly as displayed on the FM Upgrade+ web site. Both the company name and
registration code fields are case-sensitive.

Note: One of the most frequent causes of failure when registering the software is typographical error. Do not misspell the

32
www.mixtelematics.com

32
 33

company name when entering the registration information in the previous step. If the company name is misspelled, enter it
exactly as it was recorded in the FM Upgrade+ database.

After the registration information has been entered correctly, click the Register button and the Fleet Manager Main window will be
loaded.

How to Renew an Upgrade+ Package

When you originally purchased your FM Upgrade+ license packages, you purchased packages for a given number of vehicles.
These provided you with upgrade cover for a period of one year from the date that they were registered. You may purchase
additional packages and add them to your registration at a later date. There are two types of packages that can be added to your
registration, each providing different benefits.

· Full packages

These are the same packages that you originally purchased on joining the FM Upgrade+ programme. When you add these
packages to your existing registration, the effect is to increase the number of vehicles you are permitted to operate within the
Fleet Manager software and to extend the period that your registration is valid for. If you do not have sufficient licences for the
number of vehicles, the software will warn you periodically. You should note that adding a full package to an existing registration
will not extend the registration period for a full year. The reason for this is that the new licence period from the package being
added is applied to both existing and new vehicles. The package provides one year of cover for the number of vehicles on it's
face, but because this year is used to extend the registration for existing vehicles as well, the registration period will be extended
by a shorter time.

Your new expiry date will be calculated using the following formula;

· Renewal packages

These are packages that allow you to extend the period that your registration is valid for. When you apply one of these packages
a new expiry date is calculated from the current expiry date, the number of vehicles you have registered and the number of
vehicles that the renewal package applies to. Typically you would add renewal packages matching the number of vehicles you
have registered, which would extend your registration period by one year. However if you add renewal packages for more or
fewer vehicles than you have registered your registration will be extended for a longer or shorter period.

Your new expiry date will be calculated using the following formula;

33
www.mixtelematics.com

33
 34

You are permitted to apply renewal packages to your registration at any time before the current expiry date. Additionally you are
granted a 60 day grace period after the expiry date during which you may apply renewal packages to your registration. You will
not be permitted to apply any full or renewal packages to your registration if the 60 day grace period has passed and you will be
required to purchase full packages and use them to begin a new registration, which may use the same company name as your
current registration.

Note: It must be noted that in cases where you have a very large number of vehicles registered, and you add full or renewal
packages for a very small number of vehicles, the expiry date may not change. This occurs because the pro-rata increase gained
by the new licences is less than one day and the expiry date is therefore not changed. It is therefore important that you purchase
and register sufficient packages at a time so that their total addition would have an effect on the expiry date, while adding them
individually might not have any effect at all.

Examples of renewals

Below are several examples of different scenarios that you might encounter when extending your registration period or increasing
the number of vehicles that you have registered.

1. You currently have 10 vehicles registered, your registration expires on 15 December 2002, you wish to extend your registration
and you have purchased a 10 vehicle renewal package which you wish to apply on 5 December 2002. Your registration is still
valid, so you may do this. Your new expiry date will be calculated as;

2. You currently have 25 vehicles registered, your registration expires on 15 December 2002, you wish to extend your registration
and you have purchased two 10 vehicle renewal packages which you wish to apply on 5 January 2003. Your registration has
expired, but you are still within the grace period, so you may do this. Your new expiry date will be calculated as;

3. You currently have 25 vehicles registered, your registration expires on 15 December 2002, you wish to extend your registration
and you have purchased a 50 vehicle renewal package which you wish to apply on 5 December 2002. Your registration is still
valid, so you may do this. Your new expiry date will be calculated as;

4. You currently have 10 vehicles registered, your registration expired on 30 September 2002, you wish to extend your
registration and you have purchased a 10 vehicle renewal package which you wish to apply on 5 December 2002. Your
registration has expired and the grace period has passed, so you may not do this. You should contact the dealer from whom
you purchased the renewal package and find out if they will allow you to return it. You need to purchase a new 10-vehicle full
package and use it to begin a new registration. You may use the same company details as on your expired registration.

5. You currently have 25 vehicles registered, your registration expires on 15 December 2002, you wish to add another 25 vehicles
and extend your registration. You have purchased a 25 vehicle full package and a 50 vehicle renewal package and wish to
apply them on 5 December 2002. Your registration is still valid, so you may do this. Your vehicle licences will be increased to
50 and your new expiry date will be calculated as;

6. You currently have 5000 vehicles registered, your registration expires on 15 December 2002 and you wish to extend your
registration. You have purchased a 10-vehicle renewal package and wish to apply it on 5 December 2002. Your registration is

34
www.mixtelematics.com

34
 35

still valid so you may do this, but you would be ill-advised to do so. The addition of such a small number of licences to a
registration with such a large number of vehicles will have no effect on the expiry date. Even if you add more licences later, you
will not benefit from the addition of this 10-vehicle renewal package.

35
www.mixtelematics.com

35
 36

3.4 Configuring FM Professional for Network Operation

© 2008 MiX Telematics | Updated 2008/06/11

Overview
The Fleet Manager Professional utilises an advanced three-tier client-server model and is designed to scale from running on a
single stand-alone computer to running on multiple computers on a local area network (LAN) or wide area network (WAN).

This document describes the procedure required to configure the Fleet Manager Professional for network operation. It is intended
for network administrators and assumes that the reader has an in-depth understanding of the networking of Microsoft operating
systems. Administrative access to the network is required in order to make the configuration changes documented below.

Components
The Fleet Manager Professional system consists of a number of components, which perform discrete functions and interact with
one another. The table below lists these components and provides a brief description of their functions:

Component Filename Functions

Client FMCli8.EXE Provides the Fleet Manager Professional user interface including all windows, dialogs,
menus, toolbars etc.

Database Server FMSvr8.DLL Retrieves data from the database and passes it to the Client.

Database The Microsoft SQL Server or Microsoft Database Engine (MSDE) used to store the
data.

In a stand-alone configuration, these components all run on a single computer. The installation set installs Fleet Manager
Professional to run in stand-alone mode.

Network Configuration
When the Fleet Manager Professional software is configured to access one database in a networked environment, each client
computer has its own FMSvr8.DLL component connecting to the single database on another computer.

Note: A second method, multiple DCOM connections to an FMSvr.DLL on a server, is no longer supported.

Please note that network operation using Windows Terminal Server, Citrix Winframe and similar systems is not supported.

36
www.mixtelematics.com

36
 37

Configuring multiple connections to the database

Requirements

To configure the Fleet Manager Professional for client-server, you will need Microsoft SQL Server 2000 or Microsoft SQL Server
2005 with the latest service packs installed. Please see the Installation required for the Microsoft SQL Server installation.

NOTE:

· Fleet Manager Professional uses the Microsoft SQL Server database engine to store the fleet data. If you do not have a copy
of Microsoft SQL Server, the installation for Fleet Manager Professional will ask to install Microsoft SQL Express.

· Client - a Pentium III 800 MHz or higher personal computer running Windows 2000 or Windows XP Professional with at least
256 MB of RAM and at least 1 GB of available disk space.

Configuration

In order to configure each Fleet Manager Professional installation to use the correct database, the SQL Server Client Access
tools and SQL-DMO must be installed on the client computer. Please refer to the Microsoft SQL Server documentation for more
information on installation.

37
www.mixtelematics.com

37
 38

1) Microsoft SQL Server can use several

different protocols to communicate with the
database. It is advisable to configure both
the server and the client machines to use
the TCP/IP protocol, as the default Named
Pipes may not work in all cases.

The Client Network Utility can be used to

change this. The program shortcut is
available from the Microsoft SQL Server
program menu.

2) Please ensure that your SQL Server

administrator has set up the required Logins
so that users for the Fleet Manager system
can connect to the server.

Please refer to the Microsoft SQL Server

documentation for more information about
Security.

3) Install the Client Components onto each

client computer. The component that needs
to be installed depends on the version of
SQL Server installed.

38
www.mixtelematics.com

38
 39

a) For SQL Server 2000 the minimum

requirement is to select the Client Tools
Only option on the Installation Definition
step.

a.1) Next ensure that Client Connectivity is

selected, and at least Enterprise Manager or
Query Analyser are selected in the
Management Tools component.

39
www.mixtelematics.com

39
 40

b) When installing SQL Server 2005 the

minimum requirements are the connectivity
and legacy components. To install these
click the Advanced button on the
Components to Install step.

b.1) In the Feature Selection, expand the Client

Components, then ensure the Connectivity
Components and Legacy Components are
selected to install to local hard drive.

40
www.mixtelematics.com

40
 41

4) Install the Fleet Manager Professional

software onto the client machines. A copy
may be installed on the server if so desired,
but it is not necessary. The install set
prompts to install SQL Express if a SQL
database engine is not found on the
computer. If you have the SQL Client
Components installed, you should select to
not install SQL.

5) At the end of the installation the database

program runs automatically, and a dialog
screen with language options will be
displayed. Clicking OK will open the
connection dialog.

41
www.mixtelematics.com

41
 42

6) Enter the Computer name where the SQL

database is, the login information and the
name of the database.

NOTE: To change the database connection

at a later time, run the Fleet Manager
Administrator (found in Control Panel).

Double click on the Connection Icon to open

the Database connection properties.

NOTE: If a password is specified, this will be

stored in an encrypted format to prevent the
password from being viewed.

The first client computer will create the

database. The second and subsequent
computers should wait until the database
has been created before setting up the
connection.

42
www.mixtelematics.com

42
 43

3.5 Fleet Manager Views

© 2008 MiX Telematics | Updated 2008/06/11

Customised Views
Fleet Manager Professional introduces a new mechanism for simplifying the user experience, utilizing customized views. These
allow Fleet Manager Professional to be tailored to specific application scenarios. The views provide market-specific terminology
and graphics for use. The view reorganises the menu structures and hides unwanted detail. Associated Extensions are loaded
automatically and it is possible to automatically execute menu functions on start-up.

Installing a default view

Four views are installed and the installation can be customised to force a specific view.

Fleet Manager View

This is the classic default view without any tailoring.

Fleet Manager Reporting View

This view focuses exclusively on reporting and exporting.

Track & Trace View

This view focused predominantly on the Active Tracking and Messaging Extension. The Active Tracking window layout is
automatically opened on start-up. The moving status of the vehicles is indicated on the map.

Materials Handling View

The captions and order of menus are altered to better suit the materials handling environment. For example, in this view vehicles
are known as equipment and drivers as operators.

43
www.mixtelematics.com

43
 44

The Materials Handling and Advanced Driver Scoring extensions are always loaded at start-up.

Changing between views

The File menu allows you to switch between views. Access to this function can be restricted by the security system, thereby
locking users down to a single view.

Changing the view requires a restart in order to load appropriate resources required by the selected view.

44
www.mixtelematics.com

44
 45

3.6 Getting Started With Fleet Manager Professional

© 2008 MiX Telematics | Updated 2008/06/11

Requirements
This section will provide the information you will need to get started with Fleet Manager Professional 9. You must install the Fleet
Manager Professional software before commencing with the steps in this document. By following these you will be able to view
information recorded by one of your on-board computers in approximately 20 to 25 minutes.

Documentation
You will notice that the first item in the Fleet Manager Start Menu folder is called Documentation. It opens the Documentation
Help file, allowing you to view all documentation and search it for keywords.

Getting Started
Step 1. Running the program

The Fleet Manager Professional 9 installation program creates a number of shortcuts in your Start Menu, in the Start Menu folder
you specified during the installation process (by default this is Fleet Manager). You can locate these shortcuts by clicking on the
Start button in the bottom left-hand corner of your desktop, clicking on the Programs folder in the Start Menu and then clicking on
the Fleet Manager folder.

Click on the Fleet Manager Professional shortcut to launch the Fleet Manager Professional 9 program.

The Fleet Manager Professional 9 splash screen will be displayed while the program is loading.

Step 2. Registration

As the Fleet Manager Professional application loads, a message may be displayed saying that the software is not registered. The
Fleet Manager Professional application must be registered on the FM Upgrade+ Programme before using it for the first time. If
you require any assistance with registering, contact the dealer who supplied the software.

Step 3. Customising the program

Change Default Organisation Name

Replace the default organisation name (My Organisation) with your organisation’s name. To do this, right click on My
Organisation in the top left-hand corner of the tree-view. Click on the Properties menu item. The Organisation property page will
be displayed. Enter your organisation’s name in the appropriate field and click OK.

Repeat the above steps to rename the default Vehicle and Driver Configuration Groups, Vehicle and Driver Reporting Groups
and Site appropriately.

Download Module Port

During the installation, the port to which the download module is connected was selected. Follow this procedure to change the
selected port.

· Click on the Tools menu at the top of the Fleet Manager Professional main window and click on the Options menu item. The
Options dialog will be displayed.

45
www.mixtelematics.com

45
 46

· Click on the Code Plug tab. Ensure that the download module is plugged into the first or second printer port on your computer
(LPT1 or LPT2 respectively). Select the appropriate port by clicking on its radio button.

Measurements

Click on the Measurement tab. Choose the appropriate measurement units (Metric, Imperial or U.S.).

Daylight Savings

Click on the Daylight Savings tab. If you have daylight savings in your country, click the Enable Daylight Savings check box and
enter the start, end and adjustment times.

Click OK to save your preferences.

Step 4. Downloading First Trips

Download Code Plug

Insert the green code-plug from one of your on-board computer equipped vehicles into the download module.

Click on the Code Plug menu at the top of the Fleet Manager Professional main window and click on the Download All Trips
menu item.

You should see the LED on the download module flash as it reads information from the code-plug. The Download Data wizard will
be displayed indicating download progress.

Add Vehicle

A notification will pop up, stating that the Vehicle ID on the plug is not configured in the database and the vehicle should be
added to the database.

The Vehicle Properties dialog will be displayed. Enter the vehicle registration number and description. Do not alter the contents of
the ID number field. Click OK. Additional tabs will be added to the Vehicle Properties dialog. Click OK a second time to save the
vehicle record in the database with default configuration settings. You can customise the vehicle’s configuration settings at a later
stage.

After clicking OK you will be returned to the Match Vehicle ID dialog. Click OK and ensure that the new vehicle you have just
added is selected by clicking on its description. Click OK to continue the downloading process.

The pre-processing phase of the download will begin and progress will be displayed.

Once the pre-processing phase of the download is completed, the processing phase will begin. Once again, progress will be
displayed.

After a while, the Match Driver ID dialog will be displayed. Make a note of the date and time of the trip described in the label at the
top of the dialog. Click the Add Driver button.

46
www.mixtelematics.com

46
 47

Add Driver

The Driver Properties dialog will be displayed. Enter the employee number and name of the driver who drove the vehicle on the
date and time displayed on the Match Driver ID dialog. Do not alter the contents of the ID number field. Click OK.

After clicking OK you will be returned to the Match Driver ID dialog. Click OK and ensure that the new driver you have just added
is selected by clicking on their description. Click OK to continue the pre-processing phase.

The Match Driver ID dialog will be displayed more than once if more than one blue plug was used. Repeat the above steps as
necessary.

When downloading is finished, summary information will be displayed. Ensure that the Open Activity Timeline check box is
checked and click OK.

Step 5. Analyse the trips and events

The Activity Timeline form will be displayed, showing a twenty-four hour graphical view of trips and events.

Press the F1 key to open the Fleet Manager Professional 9 context sensitive help for an explanation of how to use the Activity
Timeline’s powerful features to analyse the data.

Troubleshooting

47
www.mixtelematics.com

47
 48

Website

There may be known issues that have been encountered when downloading information from the green code-plug. These issues,
solutions and/or workarounds are described in knowledge base articles, which can be located on the MiX Telematics web site at
http://www.mixtelematics.com.

Knowledge Base

To access the knowledge base, click on ‘Search the Knowledge Base’ in the Support section of the website. The knowledge base
search page will be displayed in your browser. Enter “Fleet Manager Professional 9” in the keywords field (without the quotes),
select “all” in the “Show me” combo-box and click the search button.

Please note: The knowledge base search facility does not work correctly with Microsoft Internet Explorer version 3.x.

Distributors

If you are not able to locate an article describing the problem you are experiencing, please contact the distributor. However, in
urgent cases where a timely solution cannot be reached it is possible to log a request directly with the development teams via this
web site.

Log a Service Request

To log a support request, click on the “Support” link in the menu bar at the top of the home page. Enter your details and the
details of the problem you are experiencing before clicking the Submit button. Please enter the exact description of any error
messages that are displayed. The more information you are able to provide, the easier it will be for our developers to locate and
correct the problem.

48
www.mixtelematics.com

48
 49

3.7 Glossary
© 2008 MiX Telematics | Updated 2008/05/07

Below you will find a list of commonly used words within the Fleet Industry and in the Fleet Manager software.

|A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z|

Activity Timeline

The Activity Timeline displays trip and event information for a driver or vehicle graphically in the form of a timeline. The timeline
can display up to 24 hours (a full day) of information and can be zoomed in to display various time periods down to 1 hour.

Active Event

An Active Event is an event (see Events) configured to send a message to the office when it is detected. The Fleet Manager can
decide which events are important enough to justify the sending of real-time messages.

Active Tracking

Active Tracking occurs when you track your vehicles in real-time on your desktop PC using Fleet Manager Professional software
or on the internet using FM-Web. You can start or stop tracking a vehicle by sending an instruction from the office, or the vehicle
can initiate tracking automatically as soon as an event (see Events) is detected. You can also be alerted in real-time when a
driving violation occurs.

Analogue or Digital Inputs

FM200 series on-board computers have analogue or digital inputs, which can be used to monitor any device on a vehicle that
generates a change in voltage e.g. headlights, refrigerator units, emergency lights, doors, PTO, Trailer coupling etc.

Arming Delay

Arming Delay is the length of time that the vehicle must be inactive before a trip ends and the unit re-arms.

Auxiliary Frequency Input

FM200 series on-board computers have auxiliary frequency inputs, which can be configured to monitor any device that generates
a change in frequency, such as temperature sensor, liquid flow measurement or pulse counter (e.g. electronic fuel consumption
measurement (EDM)).

Communication Cost Control (CCC)

The Communication Cost Control feature provides the Fleet Manager with the ability to keep communication costs to a minimum.
Communication Cost Control allows the Fleet Manager to choose which events are urgent enough to justify the cost of sending
real-time notifications to the office.

Combo Box

A combo box is a text box with a button to the right. Clicking the button pulls down a list of possible values that may be selected.

Comparison

Comparison operators are used to describe relationships between values. The Fleet Manager software uses the following
operators.

Operator Description

· = Equals. True when the values on either side are equal.

49
www.mixtelematics.com

49
 50

· <= Less than or equal to. True when the value on the left is either less than or equal to the value on the right.

· < Less than. True when the value on the left is less than the value on the right.

· >= Greater than or equal to. True when the value on the left is either greater than or equal to the value on the right.

· > Greater than. True when the value on the left is greater than the value on the right.

See About Devices, Parameters and Events.

Configuration Group

Configuration groups are used to define default vehicle or driver properties that are used when adding new vehicles or drivers to
the system.

For example if you always wish to configure light delivery vehicles a certain way, you can create a configuration group and assign
it to new light delivery vehicles rather than manually configuring each new vehicle.

Decimal Hours

Decimal hours reflect periods of time as decimal fractions of hours rather than as hours, minutes and seconds. For example 1
hour 30 minutes is 1.5 decimal hours.

Device Driver

FM200 and above series on-board computers are fully programmable. The programs for the vehicle unit take the form of device
driver files that are uploaded to the vehicle unit by means of the green vehicle code-plug or other communications methods..

Distance Unit

Distance units refer to miles if you are using the Imperial or US measurement units, or kilometres if you are using metric
measurement units.

Download

A download is the process of retrieving information from the on-board computer using the green vehicle code-plug or other
communication methods and storing the information in the database.

Download Module

The download module is a peripheral that plugs into your computer's parallel (printer) port. It has a socket into which code plugs
are inserted and allows information to be read from or written to the code plug.

Driver

Any person who has been granted access to drive one of your vehicles.

Driver ID

The driver is identified by the act of inserting the driver code-plug into the code-plug socket in the vehicle.

Driving Violations

All Fleet Manager on-board computers record the standard driving violations - over-speeding, over-revving, green band driving,
harsh braking and excessive idling. FM200 and above series on-board computers can also be configured to record additional
violations such as harsh acceleration as well as user-defined events such as headlights on, cargo door opening in no-go zone
etc.

Engine Hours

50
www.mixtelematics.com

50
 51

Engine hours is the elapsed time in decimal hours that a vehicle's ignition was on and/or that the vehicle was generating a signal
on the RPM line.

Events

Events define what is to be monitored by the unit. Events can be standard driving violations (e.g. Over-speeding), standard
events (e.g. Battery Disconnection) or user-defined events.

See About Devices, Parameters and Events

Extension

An extension is a program, shipped with the Fleet Manager software or provided by a third-party. It plugs into the Fleet Manager
software and appears to the user to be a part of the Fleet Manager software.

See Extensions.

Fleet Manager Administrator

The Fleet Manager Administrator allows you to administer and maintain your database on your Fleet Manager SQL Server
Database. Functionality such as backup, restore and import is available from the FM Administrator. It also allows you to specify
the location of your Fleet Manager databases, select the Company Logo to appear on all your reports and select the number of
days after which the back up reminder appears.

FM100

Fleet Manager 100 / FM100 on-board computer.

FM200

Fleet Manager 200 on-board computer. The FM200 has been discontinued, but the FM200 Plus has all the functionality (and
much more) than the original FM200.

FM300 and variations

Fleet Manager 300 series on-board computer.

FM400 and variations

Fleet Manager 400 series on-board computer.

Frequency Inputs

Please see Auxiliary Frequency Input

Global Positioning System (GPS)

The Global Positioning System (GPS) is a satellite-based navigation system which uses up to 24 satellites within the network to
pin-point the exact location of a object, anywhere in the world, any time of the day.

GPRS

General Packet Radio Service (GPRS) is a new non-voice value-added service that allows information to be sent and received
across a mobile telephone network. It enables networks to offer 'always-on', higher capacity, Internet-based content and packet-
based data services. Within the mobile phone context, it enables services such as colour Internet browsing, e-mail on the move,
powerful visual communications, multimedia messages and location-based services. GPRS is an extension of the Global System
for Mobile Communications (GSM). Most GSM service providers support GPRS as the upgrade path to third generation (3G)
mobile communication systems.

Global System for Mobile Communications (GSM)

51
www.mixtelematics.com

51
 52

Global System for Mobile Communications (GSM) is a digital protocol that is the most widely deployed wireless standard in the
world. GSM allows vehicle data to be extracted remotely from the vehicle, anywhere within the GSM Network range. The GSM
Data Calls are scheduled and initiated by the Fleet Manager software and can be used to:

· Download data from the on-board computer

· Upload new device drivers and configuration to the vehicles

The GSM circuit-switched data (CSD), Short Message Service (SMS) and General Packet Radio Service (GPRS) technologies
can be used for communicating with FM200 and above series on-board computers.

Interval Data

See Tacho Data.

Multi-plug

A multi-plug is a vehicle plug that has been initialised in such a manner that it can be used to download from any vehicle.

Object

An object is any tangible entity or item within the system. Organisations, sites, vehicles, drivers, passengers, configuration groups
and reporting groups are all objects.

On-board Computer

A computer installed into a vehicle, used for monitoring and recording the activities of the vehicle.

Organisation

An enterprise operating out of one or more sites and controlling one or more drivers and vehicles.

Passive Tracking

Passive Tracking lets you view the route of your vehicles on an interactive map after the data has been downloaded and stored in
the Fleet Manager database. This helps you to monitor the routes drivers take, and highlight when vehicles enter and/or exit pre-
defined locations. You can also set up that the GPS position of events should be recorded when they occur, as this allows you to
view where the vehicle was when certain events occur.

Passenger

A person who is to be identified to the unit when entering or exiting a vehicle. Only supported for the FM200, FM200e and above
units.

Plug Ratio

The ratio between the number of trips and the amount of tachometer information that can be downloaded into the green vehicle
plug.

Property

A property is an item of information attached to an object that describes the object or it's behaviour.

Property Page or Property Dialog

A form used to view or modify an object's properties. Property pages usually, but not always, group information on separate
pages known as tabs. Index tabs appear at the top of the property page and you can switch to the relevant page by clicking on
these.

52
www.mixtelematics.com

52
 53

Quick Download

A Quick Download is the download of vehicle data that has not been downloaded yet. This can be done either with or without
tacho (interval) data.

Radio Button

Radio buttons are small round controls used together in groups. Only one radio button in the group may be selected at a time.
The group as a whole has a value based on the selected radio button.

Range of FM200 on-board computers

This includes the FM200 Plus, FM200 Locator, FM200 Communicator, Messenger and Navigator.

Relay Drive

FM200 and above series units are equipped with one or more relay drives that can be used to switch an external device on via an
external relay when an event occurs.

Reporting Group

Reporting groups are simply logical groupings to aid you in selecting groups of vehicles or drivers for reporting purposes.

For instance, if you have ten salespeople from four different sites that you would like to reflect on a single report, you could create
a reporting group rather than selecting them individually.

Serial Interfaces

The FM200 and above series on-board computers have serial interfaces that can be used to connect accessories to the on-board
computer e.g. FM Terminal.

Sender

A sender is a device in the vehicle that is connected to one of the on-board computer's input lines. It passes information back to
the unit.

Site

A physical location at which drivers are based and from which vehicles are operated.

SMS

The GSM short message service.

Standing Delay

Standing delay indicates the length of time that the vehicle must be stationary while in a trip before a sub trip is ended and a new
sub trip started.

Sub trip

A sub trip is the portion of a trip between the vehicle's departure and the end of the standing delay after it comes to a halt. If the
trip is ended before the standing delay time is up, the sub trip ends immediately.

Tacho Data

Tacho data (originally recorded by a traditional tachograph) is second-by-second data which normally includes speed and RPM in
a graphical format on a paper disk. FM200 and above series on-board computers record this information electronically.

53
www.mixtelematics.com

53
 54

Trip Category

Trip categories are optional informational items that you can assign to downloaded trips, to describe what category the trip falls
into.

Trip End

A trip ends when the vehicle's ignition is turned off.

User-Defined Events

A Fleet Manager is able to set up his own customised events such as driver door opening, no-go zone entered, hazard lights
activated,refrigerator temperature exceeded, etc. More complex events can be set up as well, such as driver door opening after
hours, headlights off while driving at night etc. Also see Events.

* Excluding FM100. The FM100 cannot record or monitor any user-defined events

Vehicle

For the purpose of the Fleet Manager system, a vehicle is defined as any vehicle such as a car or truck into which an on-board
computer has been installed.

Vehicle Unit

See On-board Computer.

54
www.mixtelematics.com

54
 55

3.8 Trip Explanation

© 2008 MiX Telematics | Updated 2008/05/07

55
www.mixtelematics.com

55
 56

3.9 Working with Fleet Manager Professional

3.9.1 Language Settings

© 2008 MiX Telematics | Updated 2008/05/07

Fleet Manager Professional software is Internationalised, offering more than 11 different language options. In addition, Fleet
Manager Professional also supports daylight savings and different measurement settings allowing you to use the software
anywhere in the world.

Selecting your preferred language

Step 1: Select the Options dialog from the Tools menu

Step 2: Click on the Language Tab. All the installed languages are listed.

Step 3: Select your preferred Language. The language will only be changed once OK or Apply has been clicked.

56
www.mixtelematics.com

56
 57
3.9.2 Measurement Settings

© 2008 MiX Telematics | Updated 2008/05/07

Fleet Manager Professional software supports three different measurement units:

· Metric Units (kilometres / litres)

· Imperial Units (miles / gallons)

· U.S. Units (miles / gallons)

Selecting your preferred measurement units

Step 1: Select the Options dialog from the Tools menu

Step 2: Click on the Measurements Tab.

Step 3: Select your preferred Measurement Units.

· Measurement units -The measurement units used in reports

· Consumption - When running fuel consumption reports, the consumption is indicated in this measurement setting. When
metric units are used, there are a choice of using Kilometres per litre (km/l) or Litres per hundred kilometres (l/100km)

· Fuel Odometer Reading - When capturing fuel, the odometer is entered using this measurement setting.

· Fuel Volume - When capturing fuel, the volume of fuel is entered using this measurement setting.

57
www.mixtelematics.com

57
 58
3.9.3 Daylight Savings Settings

© 2008 MiX Telematics | Updated 2008/05/07

Overview
Daylight Savings Time (DST) adjustments are only utilized by the Fleet Manager application software. No adjustments take place
in the Fleet Manager on-board computer (OBC).

If a trip recorded by an on-board computer started outside of the DST period, the trip times are not adjusted by the Fleet Manager
software, irrespective of whether or not the trip ended inside the DST period.

If however a trip recorded by an on-board computer started inside the DST period, the trip times are adjusted by the Fleet
Manager software as the data is downloaded, irrespective of whether or not the trip ended inside the DST period.

Interval (tacho) data is stored in a highly compressed binary format in the Fleet Manager database and is thus not adjusted until it
is extracted at the time of generating an interval data graph. See the section entitled “The effects of DST on interval data” below
for an explanation.

Terminology
DST - Daylight Savings

OBC - on-board computer

How Daylight Savings affect Fleet Manager Data

The situation that may arise at the end of the DST period

Figure 1 shows a timeline of trips with their corresponding DST adjustments for both the Northern Hemisphere and the Southern
Hemisphere. The following explanation will reference the Northern Hemisphere, but the situations described apply to the
Southern Hemisphere as well.

The times of trip A, trip B, trip E and trip F are not adjusted, because they started outside of the DST period. Although trip B
crosses into the DST period, it’s times will not be adjusted because it started outside of the DST period.

The times of trip C and trip D are adjusted, because they started inside the DST period. Although trip D ends after the end of the
DST period, it’s times are still adjusted because the it started inside the DST period.

These adjustments result in trip D overlapping trip E.

The following example clarifies this situation further:

If the end of the DST period occurs on 1 October at 02:00 with the DST time shift is 1 hour, if a trip begins at 01:30 and the driver
drives for 1 hour, the trip will be recorded with start and end times of 01:30 - 02:30. By the time the driver stops driving, clocks
have been set back by an hour, which means that it is once again 01:30. If the driver begins another trip and drives for a further
hour, the trip will again be recorded with start and end times of 01:30 - 2:30. This means that the same driver and vehicle will
appear to have driven two trips during the same time period.

When this occurs in the Fleet Manager system, the trips will be shown as overlapping trips on the Activity Timeline.

58
www.mixtelematics.com

58
 59

Figure 1 – Daylight Savings in the Northern Hemisphere (top) and Southern Hemisphere (bottom).

Overlapping trips on the Activity Timeline

Figure 2 shows the trips D and E overlapping. The events recorded by trip D are shown as a black bar, and the events recorded
by trip E are shown as a white bar:

59
www.mixtelematics.com

59
 60

Figure 2 - Overlapping trips D and E

Figure 3 shows trips D and E combined. A display of these trips on the activity timeline will show both trips. They will overlap, but
the user will not be able to see the overlap.

Figure 3 - Overlapping trips D and E combined

When the system processes events for report generation, it takes all the events between the trip start and trip end. Consequently
an event display of Trip E will include the events of trip E and trip D. Conversely an event display of Trip D will include the events
of trip D and trip E.

The effects of DST on interval data

An illustration of interval data storage and retrieval is shown below in figure 4:

60
www.mixtelematics.com

60
 61

Figure 4 - Interval storage and retrieval

After the data is recorded, and during the download of data into the client, the trip data is shifted forward by DST (which is set in
the client). When the user requests a interval graph, the system takes the start of the activity timeline selection into account, and
references back to the interval data using DST.

Complete illustration of interval data retrieval

The following explanation assumes that the Activity Timeline selection corresponds with that of the trip start and end times.

Figure 5 - Trip before DST period

There is no time shift for the trip data, and thus interval data is referenced by the start of the activity timeline selection.

Figure 6 - Trip before DST period crosses into the DST period

61
www.mixtelematics.com

61
 62

Despite the fact that the trip crosses into DST, there is no time shift for the trip data, and thus interval data is referenced by the
start of the activity timeline selection.

Figure 7 - Trip inside DST period

Because the trip started in DST, there is a time shift for the trip data, and thus interval data is referenced by the start of the
activity timeline selection less the DST value.

Figure 8 - Trip inside DST period – shifted trip is still inside DST period

Because the trip started in DST, there is a time shift for the trip data, and thus interval data is referenced by the start of the
activity timeline selection less the DST value.

Figure 9 - Trip inside DST period – shifted trip is outside DST period

Because the trip started in DST, there is a time shift for the trip data. The shifted trip data falls outside of DST and thus interval
data is referenced by the start of the activity timeline selection. Unfortunately the interval data is in another location, and as a
result no interval data will be displayed.

62
www.mixtelematics.com

62
 63

Figure 10 - Trip inside DST period crosses to normal time – shifted trip is outside DST period

Despite the fact that the trip crosses into normal time, the trip started in DST and there is a time shift for the trip data. The shifted
trip data falls outside of DST and thus interval data is referenced by the start of the activity timeline selection. Unfortunately the
interval is in another location, and as a result no interval data will be displayed.

Figure 11 - Trip outside DST period

There is no time shift for the trip data, and thus interval data is referenced by the start of the activity timeline selection.

Figure 12- DST time changed after data is downloaded

The trip was downloaded in DST, and thus the trip data is shifted. If the daylight savings amount has been changed, say from a
two-hour shift to a one-hour shift, the interval data will not be referenced correctly, and a Interval data plot will include partial
interval data.

63
www.mixtelematics.com

63
 64

Figure 13 - DST settings disabled after data downloaded in DST period

If the trip data is downloaded in DST, and daylight savings is then turned off, the system will reference the interval data by the
start of the activity timeline selection, and not the trip start less the DST value. As a result the interval data will not be displayed.

Figure 14 - DST settings enabled after data downloaded in normal time

If the trip data is downloaded in normal time, daylight savings is then turned on, and the trip date happens to fall within DST, the
system will reference the interval data by the start of the activity timeline selection less the DST value, and not the trip start. As a
result the interval data will not be displayed.

64
www.mixtelematics.com

64
 65
3.9.4 Security Settings

© 2008 MiX Telematics | Updated 2008/06/25

Overview
Fleet Manager now implements role-based function access control. No security is enforced when a new database is first created.
If you wish to apply security in your organisation, the administrator should set the password of the FMAdmin user by selecting the
"Change Password" function from the File menu (this can also be done from the Fleet Manager Security Extension).

Default Account Users

There are three default user accounts in the Fleet Manager database. These are FMAdmin, FMUser and FMCommsUser, and
these may not be deleted. If there are no other user accounts in the database and the passwords have been left empty, the Fleet
Manager Professional Client application will automatically log in with the FMAdmin account. If there is a single password set for
any user account, or if there is any user account that has been created by Fleet Manager users (excluding the three default user
accounts), the user will be prompted to log in on starting the Fleet Manager Professional Client application.

65
www.mixtelematics.com

65
 66

If an access password exists when a database is upgraded from a previous version of Fleet Manager, this password is
automatically assigned to the new FMUser user account. If an update password exists when a database is upgraded from a
previous version of Fleet Manager, this password is automatically assigned to the new FMAdmin user account. If no update
password exists, the FMAdmin user account is assigned the access password.

Roles
The following predefined roles exist and once again the administrator may add or edit roles and function level permissions at will.

Note: A user account will have the combined security permissions of all the roles of which it is a member. In the case of
differences between security permissions on two roles of which a user account is a member, 'Access' takes precedence.

Example: if a user is a member of Role A and Role B, and Role A has access to Event Configuration and Role B does not, the
user account will have access to Event Configuration.

Note that the traditional “update password” control is now achieved by selecting the "Event Configuration" sub-functions as listed
below.

Finally, it goes without saying that whoever has administrative access should apply caution when modifying the role level access.

66
www.mixtelematics.com

66
 67

TIP: Passwords are case-sensitive, meaning that entering ABC123 is not the same as entering abc123. This is one of the
most common reasons that users are unable to login, so if you are having trouble accessing the client check that your
Caps-Lock is set to the same setting it was when you first entered the password.

67
www.mixtelematics.com

67
 68
3.9.5 Wizards

3.9.5.1 About Wizards

© 2008 MiX Telematics | Updated 2008/04/14

Wizards are intelligent assistants that help you to complete complex tasks. Instead of a complicated dialog with many options,
you are shown a simple form that breaks the option down into a number of steps. The wizard monitors what you have entered
and adjusts the following steps so that selection lists are only pre-filled with relevant selections and you are shown options based
on what you have previously entered.

Each step tells you exactly what you need to do and guides you through providing the required information in an intuitive manner.

Each wizard has five buttons used to move through the wizard as you enter information.

· Next
Takes you to the next step in a wizard. This button may be disabled if you are on the last step of the wizard or if you have not
completed all the options for the current step.

· Back
Takes you to the previous step in a wizard. This button may be disabled if you are on the first step of the wizard or if you have
not completed all the options for the current step

· Finish
Closes the wizard and completes the task. This button is only available if you have completed all the required steps. If you click
the Finish button before you have reached the last step of the wizard, default values will be used for the remaining steps

· Cancel
Closes the wizard without completing the task or saving any of the information you have entered.

· Help
Displays the help page.

The current step and total number of steps are displayed on the title bar of the wizard. Do not be concerned if the total number of
steps changes as you move through the wizard. This is a normal consequence of the wizard adjusting to the information you have
entered.

Which Wizards are available in this software?

68
www.mixtelematics.com

68
 69
3.9.5.2 Fleet Manager Wizards

© 2008 MiX Telematics | Updated 2008/04/14

The Fleet Manager software provides wizards to simplify the following functions:

Clear Data
This wizard is used to selectively remove downloaded trip information from the database, and allows you to select which vehicles
and periods you wish to delete information for. It is accessed by clicking the Clear Data button on the Advanced tab of the
Organisation Properties.

NOTE: The information for a trip is shared between the vehicle and the driver that undertook the trip. This means that removing
the vehicle's trip information will also remove the driver's trip information.

Initialise Plug
The following wizards assist you with these tasks:

Vehicle Plug

Allows you to update the green vehicle plug for the following reasons:

· Change the vehicle for which the plug is to be used.

· Update the unit's event configuration.

· Update the unit's odometer reading.

· Update the attached FM Terminal's menu and critical warning delays.

· Select a specified date range for which to download trip and tachometer information from the unit when the plug is next
inserted into the unit.

· Change the plug storage ratio

Driver Plug

Allows you to change the driver assigned to the specific plug.

Passenger Plug

Allows you to change the passenger assigned to the specific plug.

Format

Clears a plug and resets it to factory defaults.

Device Drivers

Loads the device drivers from your personal computer to the plug for uploading to the vehicle unit.

System Override plug

Allows you to change the vehicle assigned to the specific plug

Report and Graph Criteria

When you request a report or graph a wizard guides you through the entry and selection of the criteria. The last step of the wizard

69
www.mixtelematics.com

69
 70

allows the selections to be saved so that they may be opened at a later time. Saved criteria files can also be used in the Report
Batches.

Set Date and Time

When you need to set the time in the vehicle unit, use the Set Date/Time wizard on the Code Plug menu. Select the date and
time you wish the unit to be set to. These are stored in the driver's plug and the date and time are set the next time the driver
identifies himself. It is therefore important that the driver insert the plug at the exact time that you set in the wizard.

Set Odometer

When you need to change the vehicle unit's odometer reading this wizard will assist you.

Trip Download

When you request a trip download a wizard helps you enter any information required and keeps you up to date on the download
progress.

The trip download wizard checks to see that a green vehicle plug is inserted in the download module, if not you are prompted to
insert one. The wizard then reads the trips from the plug. If the vehicle is not known to the system, the Match Vehicle ID dialog is
opened allowing you to select the vehicle that the trips should be assigned to. If an unknown driver is encountered while
downloading the trips, the wizard opens the Match Driver ID dialog allowing you to specify which driver to use. This dialog also
allows you to specify whether this driver should be assigned when an unknown driver is encountered later in the download, or
not.

Once the trips have been downloaded they are processed and stored in the database. When processing is complete you are
shown the statistics of the trips processed and stored. You also have the option to open the activity timeline to view the newly
downloaded trips.

If the vehicle is due or overdue for a service you are shown a reminder, which has an option to specify if the service has already
taken place.

Add Device
This wizard assists you in adding devices when defining the event configuration for your on-board computers.

70
www.mixtelematics.com

70
 71
3.9.6 Extensions

© 2008 MiX Telematics | Updated 2008/05/07

An Extension is an add-on program, shipped with the Fleet Manager software or provided by a third-party. It plugs into the Fleet
Manager software and appears to the user to be a part of the Fleet Manager software.

The list of installed extensions can be accessed by clicking on Extension Manager in the Tools menu.

71
www.mixtelematics.com

71
 72

3.10 Windows and Menus

3.10.1 Windows

3.10.1.1 Main Program Window

© 2008 MiX Telematics | Updated 2008/06/12

You will spend most of your time in the software working with the main program window, which has the following components:

Menu Bar
The menu bar provides access to all the functions of the software.

Tool Bars
The tool bars provide access to the most commonly used features of the software, with buttons for the following functions on the
standard toolbar. If any extensions are installed, the extension toolbar may be visible and will have buttons allowing quick access
to the features of the extensions. Thus not all of these buttons may be visible.

Delete - deletes the selected item.

Properties - opens the selected item's property page.

Event Definitions - opens the Event Definitions property page.

Trip Categories - opens the Trip Categories dialog.

Add Site - opens the Site Properties property page for a new site.

Add Vehicle - opens the Vehicle Properties property page for a new vehicle.

Add Driver - opens the Driver Properties property page for a new driver.

Add Passenger - opens the Passenger property page for a new passenger.

Add Vehicle Configuration Group - opens the Vehicle Configuration Group property page for a new vehicle
configuration group.

Add Vehicle Reporting Group - opens the Vehicle Reporting Group property page for a new vehicle reporting group.

Add Driver Configuration Group - opens the Driver Configuration Group property page for a new driver configuration
group.

Add Driver Reporting Group - opens the Driver Reporting Group property page for a new driver reporting group.

72
www.mixtelematics.com

72
 73

Options - opens the Options dialog.

Extension Manager - opens the Extension Manager dialog.

Plug Information - opens the Plug Information dialog.

Quick Download - opens the Download wizard.

Activity Timeline - opens the Activity Timeline.

View - changes the manner that items are displayed in the list view.

Quick Download - opens the Download wizard.

Active Tracking and Messaging – displays the Active Vehicles window.

Manage Jobs – opens the Manage Jobs window

New Job Message – opens the Add a Job window

Send Free-text Message – sends a free-text message

SMS Message to Mobile – sends an SMS message to a mobile phone

Plot GPS Logs – opens the Plot GPS Logs wizard to report by Site, Reporting Groups or Vehicles

Show Map – loads the Map Viewer

Currencies – opens Currencies window with list of available currencies

Locations – opens a list of loaded locations

Routes – opens the Routes dialog box

Contacts – opens a list of loaded contacts

Find – opens a search box to search for ID or part of a name/description

Vehicle Route Planner – opens the Route Planner window to plot a route per vehicle

73
www.mixtelematics.com

73
 74

Data Export Wizard – opens a wizard to guide you through the process of exporting data to a file on your computer

Plot GPS Log with Map Point – uses Map Point to plot the GPS log

FM Comms Scheduler – allows you to schedule regular communications with the FM unit

Maintain Trailers – opens a list of trailers with options to add detail

Fuel Consumption Settings – opens a list of snow ploughs and allows addition of average fuel consumption data

Blade Width Settings – opens a list of snow ploughs and allows you to set their blade width value

Shortcut Bar
A shortcut bar similar to the one in Microsoft Outlook appears by default at the left side of the main program window. It allows the
creation of shortcuts to items in the tree and list view windows. These shortcuts are reflected as icons with a caption, in the same
manner as shortcuts are shown on your Windows desktop. To use a shortcut click on it using your left mouse button.

These shortcuts are organised by grouping them, and the shortcut bar always contains a system group with shortcuts to the
standard system objects. Groups are represented by bars at the top or bottom of the shortcut bar and to switch to a group you
click on its bar.

To create a shortcut to an item in the folder list or list view, right-click the item and select the Add To List Bar option. This option
has a sub-menu listing the groups that the shortcut can be created in. If you choose New Group you will be prompted for the
name of the new group.

In addition to the system shortcuts and those you create, it is possible that other shortcuts may be created by extensions.

The shortcut bar may be hidden or redisplayed using an option on the View menu.

74
www.mixtelematics.com

74
 75

Folder List
The folder list is a tree view window similar to the one in Windows Explorer that appears at the left side of the main program
window. This window presents a hierarchical view of your organisation allowing you to navigate quickly to any of your
configuration groups, reporting groups, passengers, sites, vehicles or drivers. The picture below shows an example of what your
organisation's hierarchy might look like.

The folder list can be hidden by clicking on the in the bar above the folder list. When the folder list is hidden and you move
your mouse over the object title above the list view window, it will become a raised button that you can click to redisplay the folder
list. The folder list can also be hidden and redisplayed with an option on the View menu.

75
www.mixtelematics.com

75
 76

List View Window

A list view window similar to the one in Windows Explorer appears at the right side of the main program window. This window
contains icons representing the items contained within the item selected in the tree view to the left. Double clicking on an item will
display any items belonging to the item or its property page if it has no sub-items.

76
www.mixtelematics.com

76
 77
3.10.1.2 Activity Timeline Window

© 2008 MiX Telematics | Updated 2008/04/14

The Activity Timeline displays trip and event information for a driver or vehicle graphically in the form of a timeline. The timeline
can display up to 24 hours (a full day) of information and can be zoomed in to display various time periods down to 1 hour.

Note: The Fleet Manager Timeline Reports Extension can be used to generate a report containing an Activity Timeline for
multiple vehicles over multiple days.

Tool bar

Print the Activity Timeline

Open the Trip Information dialog

View the Tachograph Data. The selected time period should be less than 9 hours

Select the events to be graphically displayed on the timeline

Change the time period visible on screen

Specify whether drivers or vehicles are being viewed

Select the vehicle or driver to view

View Previous Day

The Current selected date

View Next Day

Select the time of day from which to start the timeline

Using the Activity Timeline

The window has two main areas. The upper window shows trips and events graphically on the timeline while the lower window
shows textual information describing those trips and events.

Tip: Maximise the timeline window for best viewing results.

· Use the arrow buttons on either side of the date control to move forwards or backwards one day at a time.

· Click on a parking or driving time block to select it and display more details.

· Once you have selected a driving or parking time the arrow keys will move forwards and backwards through periods of the
same type as the selection.

77
www.mixtelematics.com

77
 78

· If there are several small trips close together, click to one side of them and drag past them before releasing the mouse button.
This will select the entire period and show you the details of all the trips.

· Click outside the timeline or press escape to deselect the selected area.

· Selecting the Trip Information command will open a dialog showing details of the selected trip. You can also assign a trip
category and enter trip notes on this dialog.

Interval (Tacho) Data

Interval (Tacho) Data is available when the "Interval (tacho) data available" row in the graphical window, is highlighted in green
(see below).

The second-to-second data can be viewed by selecting the icon from the Tool bar. See Tachodata Graph for more
information

78
www.mixtelematics.com

78
 79
3.10.1.3 Report Window

© 2008 MiX Telematics | Updated 2008/04/14

When you generate a report or open a saved report, the Report Window is displayed. This window consists of

· A Menu Bar

· A Toolbar

· A Report View

The menu and toolbar provide commands allowing you to save the report, open a previously saved report, print the report and
control the zoom factor of the report viewer.

If the report being viewed is newly generated, you will be prompted to save it when you close the window or request to open
another saved report.

It is possible to have more than one report window open at a time.

79
www.mixtelematics.com

79
 80
3.10.1.4 Graph Window

© 2008 MiX Telematics | Updated 2008/04/14

When you generate a graph or open a saved graph, the Graph Window is displayed. This window consists of

· A Menu Bar

· A Toolbar

· A Graph View

The menu and toolbar provide commands allowing you to save the graph, open a previously saved graph, print the graph and
control the appearance of the graph.

If the graph being viewed is newly generated or has been modified since saving, you will be prompted to save it when you close
the window or request to open another saved graph.

It is possible to have more than one graph window open at a time.

80
www.mixtelematics.com

80
 81
3.10.2 Menus

3.10.2.1 File

3.10.2.1.1 Print List

© 2008 MiX Telematics | Updated 2008/05/07

"Print List" is situated in the File menu at the top of the Main Client window, and prints the list of organisations/sites/drivers/
vehicles/ reporting groups/configuration groups as viewed by the user in the List View Window. The List is printed to the Default
Printer.

81
www.mixtelematics.com

81
 82
3.10.2.1.2 Exiting Fleet Manager Professional 8

© 2008 MiX Telematics | Updated 2008/06/12

Fleet Manager Professional 9 can be exited by clicking on the Exit menu item, using the File Menu at the top of the main window.

A dialog box will appear asking if you are sure you would like to exit. Click "Yes" if you would like to exit the application.

If your database has not been backed up within a certain number of days, a warning message will appear, reminding you to back
up the database. The number of days after which the warning starts to appear can be changed using the Fleet Manager
Administrator.

82
www.mixtelematics.com

82
 83
3.10.2.2 Edit

3.10.2.2.1 Event Definitions

© 2008 MiX Telematics | Updated 2008/06/12

Overview
One of the most powerful features of the Fleet Manager system is the ability to monitor, detect and record events that occur within
your vehicles. You can configure the on-board computers in your fleet to detect and report on events that are of interest to you.
This process, known as defining the event configuration of the on-board computer, is done by defining Devices, Parameters and
Events and by setting parameters specific to different types of unit (on-board computer).

The Event Definitions dialog is accessed from the Edit menu in the Main window.

Devices

Devices are physical objects connected to the input lines of the on-board computers. Many standard devices, for example a
Speed Sender, are supported by the software and you can easily define other devices such as a Headlights Switch.

Events can be defined to take information from these external devices into account. For example, an event to detect Over
Speeding would take the value of Road Speed from the Speed Sender device into account.

Unit Types

83
www.mixtelematics.com

83
 84

The Unit Type list displays the type of on-board computers supported by the FM Professional software. See Unit Types.

From this list, you can specify which devices will be connected by default to each type of unit, as well as the default device
properties for each connected device.

If a device is connected to a particular type of unit at this level, all vehicles added to the database will have this device connected
by default unless it has been specifically removed for a Vehicle Configuration Group or Vehicle. User-defined devices may be
added or removed from the system. Devices may not be removed if they are configured to be connected to a unit. Editing a
device invokes the Device Property page, which allows configuration of the device.

Parameters

84
www.mixtelematics.com

84
 85

Parameters are used to represent the values returned by connected devices. Examples of standard parameters are Road Speed
(from the Speed Sender device) and Latitude (from the GPS Receiver device).

The list shows the name of each parameter that may be edited in the system. Editing a parameter invokes the Parameter
Property page which allows the name and profile ranges to be changed if necessary. Parameters are added when creating a
device, and removed when the last device referencing the parameter is removed.

Events

85
www.mixtelematics.com

85
 86

Events define what should be monitored and/or recorded by the unit as well as what other actions the unit should take when an
event is detected, for example sending a message back to the office, switching a device on or off etc. Examples of standard
events are Over Speeding, Harsh Braking and Excessive Idle.

The list shows the name of each Event that may be edited in the system, and whether it should be monitored. User-defined
events may be added or removed from the system. Removing an event will cause all occurrences recorded for the event to be
removed too. Editing an event invokes the Event Property page which allows the name, condition, recording options and actions
to be changed.

Note: For a more in-depth description of event configuration, please see About Devices, Parameters and Events and Defining
Custom Events.

86
www.mixtelematics.com

86
 87
3.10.2.2.2 Trip Categories

© 2008 MiX Telematics | Updated 2008/06/24

The "Trip Categories" dialog is accessed from the Edit menu, and allows you to define the list of trip categories you will use to
describe your trips.

The dialog consists of a list of categories with buttons to Add, Edit or Delete categories.

When you click "Add", a new category is entered into the list. It is initially given a system-assigned name and displayed with the
text highlighted and surrounded by a box. You can type in the name you wish to use and press "Enter" to rename the new
category.

Clicking "Edit" will cause the selected category to be displayed with its text highlighted and surrounded by a box. Type in the new
name you wish to use and press enter.

Clicking "Delete" will delete the selected category. Any trips that were assigned to the category will remain in the database
without an assigned category.

Through the use of a toggle switch, drivers can indicate whether a vehicle is being used for private use. When Private Mode is
selected using the switch, a beep sequence will sound to indicate this selection. In addition, if the switch is set to private mode,
once the trip has begun the beep sequence will also sound.

87
www.mixtelematics.com

87
 88
3.10.2.3 Code Plug

3.10.2.3.1 Plug Information

© 2008 MiX Telematics | Updated 2008/06/12

When you select the "Plug Information" option on the Code Plug menu, the Plug Information dialog opens. This dialog displays
the following information:

Plug Type

Indicates the type of plug that is in the download pod.

Plug System Number

The ID Number of the related driver, vehicle or passenger assigned to the plug.

Plug Description

The driver's name, the vehicle's registration and description, or the passenger's name matching the ID Number in the database.

Plug Storage Ratio

Shown only for the range of FM200 on-board computers and FM200e vehicle plugs, this displays the Events to Tachometer Data
ratio that was defined when the plug was initialised.

Device Driver Information

Shown only for the range of FM200 on-board computers and FM200e vehicle plugs and Device Driver plugs, and displays
information about the Device Drivers loaded in the unit.

88
www.mixtelematics.com

88
 89
3.10.2.4 Tools

3.10.2.4.1 Fuel Information

© 2008 MiX Telematics | Updated 2008/06/12

The "Captured Fuel" dialog is accessed via the Fuel Data option on a vehicle's context menu by right-clicking on a vehicle, and
allows you to maintain records of fuel put into the vehicle.

Managing Fuel Data

A list of records is shown along with Add, Edit and Delete buttons. Select a record by clicking on the date in the list to edit or
delete it.

Clicking the Add or Edit button displays the Fuel Usage dialog, where you can enter the date, odometer reading, fuel quantity and
cost.

NOTE: This information is not removed by the Clear Data function. If Fuel Usage records are to be deleted, they must be deleted
from this page.

Measurements
The measurement settings can be changed to display metric, Imperial or U.S. measurements. For more information please view
Measurement Settings help page.

89
www.mixtelematics.com

89
 90
3.10.2.4.2 Options

© 2008 MiX Telematics | Updated 2008/06/12

The "Options" dialog is accessed from the Tools menu and has seven tabs:

Reporting
Allows you to define where your report and graph files are stored. Type the path to the directory into the relevant field or click
"Browse" and use the Browse For Folder dialog to indicate the directory to use.

The "Batch reporting log file" option allows you to define the name and location of the log file use for Scheduled Reporting.
Please note that this log file is not created or updated when running report batches via the Reporting Batches dialog.

There is also an option specify if a reminder to print Vehicle or Driver lists is required, if changes are made to the Vehicle or
Driver's properties.

Code Plug
Allows you to define options used for controlling how code plugs are read and updated.

Download module

Allows you to set the parallel port that your download module is connected to.

Plug Update Confirmation

Allows you to specify how the plug is to be updated when you make a change that needs to be transferred to the vehicle.

· Always update the plug

Requires that the correct plug always be inserted into the download module before any action that may cause a plug update is

90
www.mixtelematics.com

90
 91

done.

· Confirm before update

Prompts you to insert the correct plug when a plug update is required.

· Do not update
Will not update the plug when a change is made. You will have to remember to use the Code Plug Initialise functions to update
the plug later.

The checkbox "Download Tacho (Interval) Data when requesting a quick download" allows you to download tacho (Interval) Data
when requesting a Quick Download.

Language
Allows you to specify the language and measurement units to use for the software.

Configured Language

A list of installed languages. The language currently in use is highlighted. You can select another language by clicking on it,
however the change will only take effect when you click the Apply or OK button.

Measurement

The measurement tab has four options that control the systems use of measurement related units, formats and formulas.

Measurement units

Allows you to specify the measurement units you wish to use. The choices are Metric, Imperial and U.S.

Consumption

Allows you to specify the format in which you wish to see fuel consumption figures reflected. There are two possible values;

· Distance units per measurement unit

Depending on the measurement units chosen this is either km/l (kilometres per litre) or mpg (miles per gallon).

· Measurement units per 100 distance units

This format is only allowed when measurement units are set to Metric when it has the meaning l/100km (litres per 100
kilometres).

Fuel Odo reading

Options are:

· Use measurement settings

Selecting this option will cause the odometer reading to be reflected in the measurement units currently selected for the system
on the fuel capture dialog.

· Metric, Imperial or U.S.

Selecting one of these options will cause the odometer reading to be reflected in the chosen measurement units during fuel
capture, irrespective of the measurement units currently selected for the system.

Fuel Volume

Options are:

· Use measurement settings

Selecting this option will cause the fuel volume to be reflected in the measurement units currently selected for the system on
the fuel capture dialog.

91
www.mixtelematics.com

91
 92

· Metric, Imperial or U.S.

Selecting one of these options will cause the fuel volume to be reflected in the chosen measurement units during fuel capture,
irrespective of the measurement units currently selected for the system.

Daylight Savings
Allows you to configure the daylight savings settings to use on your system. You can specify whether to use daylight savings or
not. If you choose to use it, specify the dates and times that daylight savings starts and ends and the number of hours to adjust
by. See the Daylight Savings help file for more information on daylight savings and how it affects the Fleet Manager System.

Dealer Details
Allows you to capture the name and telephone number of the Dealer who supplied the Fleet Manager system.

Extensions
Allows you to access the options dialogs of loaded extensions, where available. A list of extensions that provide option dialogs is
displayed. To open an option dialog, double-click on the extension name, or single click the name and then click the Show
Options button.

92
www.mixtelematics.com

92
 93
3.10.2.4.3 Service History

© 2008 MiX Telematics | Updated 2008/06/12

The "Service History" dialog is accessed via the Service History option on a vehicle's context menu by right-clicking on the
vehicle. This allows you to maintain records of the vehicle's maintenance services.

Managing Service History

A list of records is shown along with Add, Edit and Delete buttons. Select a record by clicking on the date in the list to edit or
delete it.

93
www.mixtelematics.com

93
 94

Clicking the Add or Edit button displays the Service History data entry dialog, where you can enter the following information about
the service. Required fields are highlighted.

· Date

· Odometer reading

· Service cost

· Reference or Job Card number

· Service notes

Below the list of records are fields displaying the date or odometer reading at which the next service is due. These fields are not
updated automatically when you add, edit or remove records. To update these fields you must click the Recalculate button. In
addition the recalculated information is not automatically saved into the database nor updated on the main client window. You
must click the Apply or OK button to save the recalculated next service information.

NOTE: This information is not removed by the Clear Data function. If Fuel Usage records are to be deleted, they must be deleted
from this page.

Measurements
The measurement settings can be changed to display metric, Imperial or U.S. measurements. For more information please view
Measurement Settings help page.

94
www.mixtelematics.com

94
 95
3.10.2.4.4 Extension Manager

© 2008 MiX Telematics | Updated 2008/06/12

The Extension Manager allows you to control the loading and unloading of Extensions.

Loading/Unloading an Extension
In order for the functions of the extension to be used, the extension must be loaded. This can be achieved in two ways.

· Selecting an unloaded extension from the list and clicking the Load button will load the extension. This is indicated by
"(Loaded)" being displayed after the extension's name. Likewise, selecting a loaded extension and clicking the Unload button
will unload the extension.

· Checking the checkbox next to the extension's name will not load the extension immediately but will cause it to be loaded
automatically when the program next starts. Similarly, unchecking the checkbox next to an extension's name will not unload it
immediately but it will no longer be loaded when the program starts.

Note: If you select to load all installed extensions, they may not all load due to limitations on the maximum number of icons
allowed on the menu.

Priority

It is possible to control the order in which the extension will load by using the and buttons to move the extensions up or
down in the list. Extensions marked to be loaded when the program starts are loaded in the order in which they appear in the list.

Registering an Extension
While many extensions are provided free of charge there are others which must be registered to unlock all their features or to use

95
www.mixtelematics.com

95
 96

them at all. To register an extension you have purchased, you must enter a registration code purchased from the Fleet Manager
Upgrade+ website. To do this you click on the Register button which displays the Extension Registration dialog. This dialog has a
single field into which you enter the registration code you have been given before clicking the Register button. If you do not yet
have a registration code for the extension you can click the FM Upgrade+.com button (shown below) to visit the website and
obtain a registration code.

96
www.mixtelematics.com

96
 97

3.11 Organisation Properties

© 2008 MiX Telematics | Updated 2008/06/12

Right-click an organisation to display its properties.

The property page for the organisation consists of three tabs:

General
Holds general information about the organisation and contains these properties:

Name

The name of your organisation.

97
www.mixtelematics.com

97
 98

Administrative Notes

A free-format field that can be used to hold any notes you wish to keep about the organisation.

Vehicle Access

Set if default configuration groups allow new drivers to access all vehicles

Late Download Warning

A Late Download notification appears next to the Last Trip column of a Vehicle on the Vehicle List, if the vehicle has not
downloaded any trips for the number of days specified here. This setting affects all vehicles in the organisation.

Company ID

Your Fleet Manager Company ID.

Driver Scoring
Allows you to define parameters by which drivers are scored.

This feature allows you to compare drivers accurately using a standard set of measurables that are independent of the type of
vehicle or its uses and limitations. Drivers are measured according to the degree they have complied with the standards of good
driving set for the vehicles they drive. The standard set of measurables comprises of the following six violations:

· Over speeding

· Over revving

· Harsh braking

· Harsh acceleration

· Out of green band driving

· Excessive idle

The Driver Scoring topic explains this configuration in detail.

Advanced
Allows for advanced configuration and contains these buttons:

Clear Data

Used to selectively clear trip information downloaded from the vehicles.

Event Definitions

Opens the Parameter and Event definition dialog

System Audit Policy

Opens the Audit Policy dialog.

98
www.mixtelematics.com

98
 99
3.11.1 Driver Scoring Parameters

© 2008 MiX Telematics | Updated 2008/04/14

The Driver Scoring Tab in Organisation Properties dialog allows you to define the parameters by which drivers are scored.

There are three factors used in the calculation of a driver's score - Weight, Duration and Severity..

Weight Factor

The weight of the violation indicates the importance of the violation in the calculation of the overall score. A weight factor has a
value of 0 to 99 with a higher value assigning greater weight to the violation. If one violation has a weight of 20 and another has a
weight of 10, the first has twice the importance of the second.

TIP: If you set a weight factor to zero, that violation is excluded from the overall (Average) score calculation for a driver.

Duration Factor

Duration factor is the percentages ranging from 0% to 100% indicating the effect that duration has on the scoring of each of the
five violations. You set the duration factor to the percentage, in excess of which the score for the violation must be zero.

For example, you may wish the score for the over speeding violation to be zero when the over speeding time was more than 75%
of the total sub trip time. In this case you would set the over speeding duration factor to 75. If the sub trip time is 40 minutes and
the driver over speeds for 30 minutes or more, the score will be zero. If the driver over speeds for a shorter period the software
calculates the score based on a percentage of the duration factor. So if the driver over speeds for 15 minutes on a 40 minute sub
trip and the duration factor is 75, the driver over sped for 50% of the duration factor period of 30 minutes (75% of 40) and so the
score for this violation is 50.

99
www.mixtelematics.com

99
 100

TIP: If you set a duration factor to zero, the duration of the violation is excluded from the scoring calculation. This means
the violation will only be scored on Severity, if applicable.

Severity Factor

Severity factor is the percentage ranging from 101% to 250% or 0% indicating the effect that the severity of the violation has on
the scoring calculation. You set the severity factor to the percentage of the violation trigger value at which the score must be zero.

For example, you may wish to assign a score of zero when the violation exceeds 150% of the trigger value for over speeding. In
this case you would set the over speeding severity factor to 150. If the trigger value for a vehicle's over speeding is set to 80 km/h
(50 mph) then the severity score will be zero if the vehicle exceeded 120 km/h (75 mph).

TIP: If you set a severity factor to zero, the severity of the violation is excluded from the scoring calculation. This means
the violation will only be scored on the Duration, if applicable.

Calculating the Score

Each violation is processed for each sub trip in the selection period. Duration and severity are scored individually and then
averaged. So if the duration score for over speeding is 50 and the severity score for over speeding is 30, the score for the over
speeding violation will be 40. If the factor for either duration or severity is set to zero the score for the violation is merely the score
of the non-zero factor.

Each event's score is then averaged for all sub trips, taking the duration of each sub trip into account. This means that a short
sub trip will not affect the score as much as a longer sub trip.

Once the scores have been calculated for each violation the final score is calculated by averaging the violation scores, taking the
weight factor into account. This is done by multiplying each violation score by it's weight and then averaging the weighted scores,
before dividing the weighted average score by the sum of the weight factors to give the final score.

Notes:

· Small variations in scoring may be noticed if scores are compared to scores calculated by earlier versions of the Fleet manager
software. This is a result of the fact that scores are now calculated per sub trip, instead of per trip.

· The Advanced Driver Scoring Report Extension enables you to define other methods of calculating driver scores.

100
www.mixtelematics.com

100
 101
3.11.2 Audit Policy

© 2008 MiX Telematics | Updated 2008/04/14

The Audit Policy dialog allows you to control the level of auditing or recording of plug-related changes in the system. It presents a
checkbox used to indicate whether auditing is to be enabled or not. If auditing is enabled, seven further check boxes are enabled
allowing you to control exactly which events are to be audited.

The Audit Policy dialog can be viewed by clicking on "Audit Policy" on the Advanced Tab in the Organisation Properties dialog.

You can control auditing for the following events:

· Setting of date and time on a driver plug

· Setting of the odometer reading on a vehicle plug

· Initialising a vehicle plug

· Initialising a driver plug

· Initialising a passenger plug

· Formatting a plug

· Initialising a system override plug

A button is provided for viewing the log of audit information that has been recorded.

101
www.mixtelematics.com

101
 102

3.12 Site Properties

© 2008 MiX Telematics | Updated 2008/06/12

The Site Properties page can be accessed by selecting a site, and selecting Properties from the File Menu, or by right-clicking in
the List View Window.

The property page for the site consists of only one tab:

General
Holds general information about the site and contains three properties:

Name

102
www.mixtelematics.com

102
 103

The name of the site.

ID Ranges

This allows a range of IDs to be used when automatically assigning a new ID, if a Driver or Vehicle is added to the system. Driver
IDs and Vehicle IDs can be assigned different ranges if required. If this is not enabled, the system will allocate the first available
ID (starting from 2).

Administrative Notes

A free-format field that can be used to hold any notes you wish to keep about the site.

103
www.mixtelematics.com

103
 104

3.13 Vehicles
3.13.1 Unit Types

© 2008 MiX Telematics | Updated 2008/06/18

FM9.0 FM9.1

FM100 FM 1000 (FM100)

FM200 **

FM200 Plus FM 2000 (FM200 Plus)

FM200 CAN FM 2001

FM200 Locator (FM200 Plus,GPS) FM 2100 (FM200 Locator)

FM200 Communicator(FM200 Plus,GPS,GSM) FM 2300 (FM200 Communicator)

VDO Messenger (FM200 Plus,GPS,GSM,FM Terminal) ***

VDO Navigator (FM200 Plus,GSM,VDO Dayton) ***

FM200 Plus HV FM 2000HV (FM200 Plus HV)

FM200 Locator HV (FM200 Plus HV,GPS) FM 2100HV (FM200 Locator HV)

FM200 Communicator HV (FM200 Plus HV,GPS,GSM) FM 2300HV (FM200 Communicator HV)

VDO Messenger HV (FM200 Plus HV,GPS,GSM,FM Term) ***

VDO Navigator HV (FM200 Plus HV,GSM,VDO Dayton) ***

FM300 ComLink-GSM (GSM) FM 3200/3210 (FM300 ComLink-GSM)

FM300 CAN ComLink-GSM (GSM) FM 3201/3211 (FM300 CAN ComLink)

FM 3316 FM 3306/3316

FM300 CAN Communicator (GPS,GSM) FM 3301/3311 (FM300 CAN Communicator)

FM300 Communicator (GPS,GSM) FM 3300/3310 (FM300 Communicator)

FM 3305/3315 (J1708) ****

NOTES:

** unit no longer in new databases. Will still be present if database is upgraded from old version.

*** support as distinct unit type removed. Any vehicles that were using these unit types will be converted to FM200 Communicator
or FM200 Communicator HV

104
www.mixtelematics.com

104
 105

**** Tripmaster unit types converted to equivalent FM unit type except the 3315.

105
www.mixtelematics.com

105
 106
3.13.2 Unit Properties

© 2008 MiX Telematics | Updated 2008/06/25

"Unit Properties" allows you to specify unit properties. These can be accessed by double-clicking from the Device tab on Vehicle
Properties.

Device
The unit type installed can be changed. Please note that if the incorrect unit type is selected, the system will not function
correctly. If a new vehicle on-board computer is installed, the user should still perform a Swap Unit before the Unit Type is
changed.

Calibration

106
www.mixtelematics.com

106
 107

Arming Delay

For more information see Arming/Standing Delay

Standing Delay

For more information see Arming/Standing Delay

Trip Start

This function only applies to the FM200 and FM200 Plus unit, and allows the user to specify when turning the ignition on will start
a trip. By default, turning the ignition on will only start a trip if a driver has been identified. Note that the unit will always start a trip
if speed or engine RPM are detected.

Record Engine Hours

For more information see Engine Hours

Disable late download Warning

When this option is checked, no indication of overdue download will be displayed on the list in the main program window. This
option will always be reset and become unchecked after the vehicle has been successfully downloaded.

Power Management

A checkbox enables deep sleep mode for FM200 Plus and FM300 type models. This should only be enabled when the RS232

107
www.mixtelematics.com

107
 108

Comms option is selected.

Swap Unit

Clicking on this button informs the software that the unit in the vehicle has been replaced or the memory of the unit was cleared.
This function is required for correct processing of downloaded data after the unit has been swapped. Please note that using this
function when the unit has not been swapped could cause duplicate event data to be saved for a vehicle.

Driver Access
For more information see Driver/Vehicle Access

Buzzer

108
www.mixtelematics.com

108
 109

Disarm Buzzer Action when the ignition is on

Indicates what warning the vehicle unit must give if a trip is started without the driver being identified. Options are:

· Don't Sound Buzzer

No alarm will be sounded.

· Sound alarm until the driver is identified

The alarm will sound once a second until the driver is identified or the trip ends.

· Sound alarm for 10 seconds only

The alarm will sound once a second for 10 seconds.

Buzzer Volume

The loudness of the Buzzer can be set on all on-board computers that are FM200 Plus (FM200 Plus) or higher.

Hours of Service (USA only)

Enable or disable the Hours of Service function using the checkbox to set allowable driver hours and ensure drivers are not on
the road for more than the permitted time.

109
www.mixtelematics.com

109
 110

Power
Power management options include monitoring of battery voltage and the enabling of automatic unit shutdown should the vehicle
be standing for a certain time period.

110
www.mixtelematics.com

110
 111

111
www.mixtelematics.com

111
 112
3.13.3 Vehicle Properties

© 2008 MiX Telematics | Updated 2008/04/14

The property page for a vehicle consists of up to nine tabs, depending on the capabilities of the vehicle's unit, and a common
display field showing details of the last download, service reminders and the last calibration.

General
Holds general information about the vehicle and contains six properties:

ID Number

The number used to uniquely identify the vehicle to the system. This number is stored in the unit. When creating a vehicle you
choose this number, which may be in the range -32,768 to 32,767 (excluding -1, 0 and 1 which are reserved for system use). If
you specify a value of 0 the system will allocate the next available number for the Home Site.

NOTE: Once the vehicle has been created this number may no longer be changed.

Unit Type

Indicates the type of unit installed in the vehicle. The current version of the software supports FM100, FM200 Plus, FM200
Locator, FM200 Communicator, Messenger and Navigator. See Unit Types for more information on the different supported unit
types.

In order to change the unit type after first creating the vehicle, you must select the Device tab, then select the current Unit Type
and click Edit.

Registration Number

The vehicle's registration number.

112
www.mixtelematics.com

112
 113

Description

The vehicle's description.

Home Site

The site that the vehicle operates from.

Configuration Group

The vehicle configuration group that the vehicle derives its default settings from.

Target Fuel Consumption

Indicates the ideal fuel consumption figure for the vehicle.

Default Driver

Indicates a driver that should be used when downloading trips where no driver identification was performed.

Additional information such as last download and next service information is shown in a read-only area at the bottom of the
dialog.

Servicing
See Servicing and Licensing of Vehicles for more information

Engine Hours

See Engine Hours for more information

Licensing
See Servicing and Licensing of Vehicles for more information

Reporting Groups
Allows you to specify which reporting groups the vehicle is a member of. Click the checkbox on each record to toggle its value.
The vehicle belongs to groups with checked boxes. See Vehicle and Driver Reporting Groups for more information.

Devices
This tab presents a list of the input lines exposed by the unit, and displays which device is connected. Editing an input line allows
the connection or removal of a device. Once connected, the device may then be calibrated, and profiling ranges set for analogue
or frequency devices.

An additional two options control when interval data is to be recorded for those devices that have been selected to record it. One
option controls whether interval data is to be recorded during trips, while the other controls whether interval data is to be recorded
outside of trips.

This tab also allows the Unit Properties to be accessed, by double-clicking on the Unit (e.g. FM200 Plus). Unit Properties
contains unit details such as Unit Type, Driver Access, Configuration details and Buzzer Settings.

Events
Allows the event configuration for the vehicle to be viewed and modified. Only events that can be recorded by the unit and
attached devices are listed. See Event Properties for a full description, but remember the Event description may not be changed
at the vehicle level.

113
www.mixtelematics.com

113
 114

Add Vehicle
When you choose the Add Vehicle command from the menu or toolbar, the vehicle properties are displayed but only the General
tab is available. Once you have completed the properties on this tab and clicked OK, the other tabs will become available.

Copy Vehicle
When you choose the Copy Vehicle command from the menu, a dialog is displayed asking for the properties of a vehicle that can
not be duplicated between vehicles (the Registration number and Description). When the OK is clicked, the vehicle properties will
open with the new vehicles information.

114
www.mixtelematics.com

114
 115
3.13.4 Servicing and Licensing

© 2008 MiX Telematics | Updated 2008/04/14

The Fleet Manager can be used to remind you of upcoming services and licensing renewals in the Servicing and Licensing tabs
in the Vehicle Properties.

Services Reminders can be set to Remind on Distance, Duration or Engine Hours. Service Reminders on Distance and Duration
can be viewed in this document. For more information regarding Service Reminders on Engine Hours, please see Engine Hours.

Licensing Reminders can be set for vehicle licenses, road worthy licenses and driver licenses. For more information on managing
driver licenses, please see Driver Licensing.

Servicing
Vehicle Servicing Reminders can be set in the Servicing tab in Vehicle Properties. It holds information used to provide you with
service reminders for your vehicle. There are two groups of four properties each, namely "Remind on distance" and "Remind on
duration".

Each has a checkbox indicating whether that method of reminders is enabled for the vehicle. The properties are:

Remind on distance

Previous service performed at

Indicates the number of distance units at which the last service was performed.

· Next service due at

Indicates the odometer reading at which the next service is due.

· Service interval

115
www.mixtelematics.com

115
 116

Indicates the frequency of servicing the vehicle in the distance units you are using.

· Reminder period
Indicates the number of distance units before a service is due that you will be reminded at.

Remind on duration

· Previous service performed on

Indicates the date on which the last service occurred.

· Next service due on

Indicates the date on which the next service is due.

· Service interval
Indicates the frequency of servicing the vehicle in months.

· Reminder period
Indicates the number of weeks before a service is due that you will be reminded at.

Licensing

This tab contains two groups of fields.

License reminders

This group of fields controls the generation of license reminders and is enabled when the License Reminders checkbox is
selected.

· Last renewal date

The date on which the license was last renewed.

116
www.mixtelematics.com

116
 117

· Expiry date
The date on which the current license expires.

· License duration
The period, in months, for which a license is valid after issue.

· Reminder period
The period, in weeks, that you should be reminded before the license is due to expire.

Road worthiness reminders

This group of fields controls the generation of road worthiness certificate reminders and is enabled when the Road worthiness
Reminders checkbox is selected.

· Last renewal date

The date on which the road worthiness certificate was last renewed.

· Expiry date
The date on which the current road worthiness certificate expires.

· Road worthiness duration

The period, in months, for which a road worthiness certificate is valid after issue.

· Reminder period
The period, in weeks, that you should be reminded before the road worthiness certificate is due to expire.

117
www.mixtelematics.com

117
 118
3.13.5 Engine Hours

© 2008 MiX Telematics | Updated 2008/05/07

The FM200 Plus (FM200 Plus) can be configured to record Engine Hours if required.

· Configuring Engine Hour Recording

· Service Reminders on Engine Hours

Configuring Engine Hour Recording

Engine Hours can be set in the Calibration tab in the Device dialog, accessible by double-clicking on the on-board computer (e.g.
FM200 Plus) icon on the Device tab in the Vehicle Properties dialog.

Engine hours can be recorded either:

· When Ignition is on or engine revs are detected

· When both ignition is on and engine revs are detected

If you enable the Recording of Engine Hours, you need to upload the event configuration to the on-board computer and set the
on-board computer's engine hours reading.

118
www.mixtelematics.com

118
 119

Service Reminders on Engine Hours

Service Reminders on Engine Hours can be set in the Engine Hours tab in Vehicle Properties dialog.

This tab contains two sections:

Service reminder

Indicates whether engine hours are to be used for generating service reminders. This option is only available if the monitoring of
engine hours has been turned on. If service reminders are turned on the following four fields become available.

· Last service
The engine hour reading at which the last service was performed.

· Next service
The engine hour reading at which the next service is due.

· Service interval
The interval, in engine hours, at which services are to be performed.

· Reminder period
The period, in engine hours, that you should be reminded before a service is due

119
www.mixtelematics.com

119
 120

· Target Fuel consumption

Indicates the targeted fuel consumption per hour.

120
www.mixtelematics.com

120
 121
3.13.6 Arming Delay and Standing Delay

© 2008 MiX Telematics | Updated 2008/05/07

A Vehicle's Arming and Standing Delay can be set in the Calibration tab of the on-board computer Device settings available from
the Device tab on the Vehicle Properties dialog.

Arming Delay

Arming Delay is the length of time that the vehicle must be inactive before a trip ends and the unit re-arms.

Standing Delay

Standing delay indicates the length of time that the vehicle must be stationary while in a trip before a sub trip is ended and a new
sub trip started.

121
www.mixtelematics.com

121
 122
3.13.7 Interval (Tacho) Data

© 2008 MiX Telematics | Updated 2008/05/07

Configuring The On-Board Computer To Record Tacho Data

Tacho data (originally recorded by a traditional tachograph) is second-by-second data which normally includes speed and RPM in
a graphical format on a paper disk. FM200 series on-board computers record this information electronically.

A vehicle can record tacho data during and/or between trips. This setting can be changed on the Calibration tab of the on-board
computer (e.g. FM200 Plus) Device settings, available on the Device tab in the Vehicle Properties dialog.

Viewing Tacho Data

Tacho data can be viewed as a graph. For more information see Interval (Tacho) Graph.

122
www.mixtelematics.com

122
 123

123
www.mixtelematics.com

123
 124
3.13.8 Device Properties

© 2008 MiX Telematics | Updated 2008/05/07

Devices are the physical items that can be connected to the on-board computer. The device list can be accessed by selecting
Event Definitions from the Edit menu option.

Double-click on a device in the list to access the Device Properties dialog:

124
www.mixtelematics.com

124
 125

Device Properties
There are usually two or more tabs containing the properties specific to the device, the first tab always contains one or more of
the following details:

ID Number

Holds the internal id number of the device. This may not be updated.

Description

Holds the description of the Device.

Value Parameter

Holds the name of the parameter which is used to test the value returned from the device. This may not be updated.

Calibration
For certain devices, a Calibration tab will be available. Calibration is dependent on the type of device whose properties are being
viewed. Below are some examples:

Boolean Switches

For switches, the threshold voltage and whether the switch is "on" or "true" when the voltage is high or when low.

125
www.mixtelematics.com

125
 126

Analog Sender

Two known sets of values may be entered, from which other values will be calculated using a linear algorithm. The maximum and
minimum possible values are displayed.

Pulse Counter

A known value for a certain number of pulses is entered. The system uses a linear calculation to determine other values.

Frequency Sender

Two known sets of values may be entered, from which other values will be calculated using a linear algorithm. The maximum and
minimum possible values are displayed.

FM Terminal

This holds the path containing the FM Terminal script files, the script to be used and the Primary and Secondary languages.

KTCO 1318 Tachograph

There is no direct calibration of the KTCO, except to specify whether the tachograph supplies engine RPM or not.

GPS

If the GPS power supply is controlled by the FM200 output relay, the time delay can be set here. The other settings specify
whether to record a trail of where the vehicle was driven. The distance factor allows the trail not to be recorded for the first part of
a sub trip, allowing for yard positioning.

GSM modem

The unit phone number, power turn off delay and the default PIN code may be set.

NOTE: In order to change the PIN code on the SIM card, the SIM card must be extracted from the GSM device and the PIN
changed on a normal hand held device.

NOTE: For a more in depth description of Event Configuration, please see Event Configuration Overview as well as About
Devices, Parameters and Events

126
www.mixtelematics.com

126
 127

3.14 Drivers
3.14.1 Driver Properties

© 2008 MiX Telematics | Updated 2008/06/12

The Driver Properties dialog can be accessed, by right-clicking on a driver in the List View Window and selecting properties. The
property page for a driver consists of four tabs:

· General

· Vehicle Access

· Licensing and

· Reporting Groups

· (USA ONLY - Hours of Service)

General
Holds general information about the driver and contains five properties:

ID Number

The number used to uniquely identify the driver to the system. When creating a driver you choose this number which may be in
the range -32,768 to 32,767. If you specify a value of 0 the system will allocate the next available number. Once the driver has
been created this number may no longer be changed.

Employee Number

127
www.mixtelematics.com

127
 128

The driver's employee number.

Extended ID

The driver's unique extended ID, a hexadecimal number (allowed digits are 0-9 and A-F) of up to 24 digits, is used to identify the
driver to certain third-party devices, for example the smart card reader.

Name

The driver's name.

Home Site

The site at which the driver is based.

Configuration Group

The driver configuration group that default settings are derived from.

Vehicle Access

See Driver/Vehicle Access Control for more information

Licensing

See Driver Licensing for more information

Reporting Groups

Allows you to specify which reporting groups the driver is a member of.

Click the checkbox on each record to toggle its value. The driver belongs to groups with checked boxes.

Hours of Service (USA only)

Allows you to set allowable driver hours to ensure drivers are not on the road for more than the allowed time.

128
www.mixtelematics.com

128
 129

129
www.mixtelematics.com

129
 130
3.14.2 Driver/Vehicle Access Control

© 2008 MiX Telematics | Updated 2008/05/07

There are two methods of managing Driver/Vehicle Access. The first method is storing the driver/vehicle access table on the blue
driver code-plug and the second method is storing the driver/vehicle access table in the on-board computer.

Note: The second method is only available for FM200 Plus series on-board computers.

By default, the driver/vehicle access table is stored on the blue driver code-plug. When this method is used, you may specify a
list of up to 50 vehicles that the driver may access (white list) or up to 50 vehicles that the driver may not access (black list).

If the driver/vehicle access table is stored in the on-board computer, a white list or black list of up to 500 drivers may be defined.

Access Control With Blue Driver Code-Plug

The Vehicle Access Tab on the Driver Properties dialog can be used to indicate which vehicles a driver should be allowed to use.

Remember: You must initialise the blue driver code-plug using the Code Plug menu in the Main Window after changing the list.

Vehicles Allowed

Indicates how many of the organisation's vehicles the driver may drive.

Vehicles Disallowed

Indicates how many of the organisation's vehicles the driver may not drive.

Access Control By On-Board Computer

130
www.mixtelematics.com

130
 131

To indicate which drivers are allowed to use a vehicle, double-click on the unit type line in the device list on the Device tab in the
Vehicle Properties dialog, then click on the Driver Access tab.

Note: This method is only available for FM200 Plus series on-board computers.

Remember: You must upload the event configuration to the on-board computer after changing the list.

131
www.mixtelematics.com

131
 132
3.14.3 Driver Licensing

© 2008 MiX Telematics | Updated 2008/05/07

Driver Licensing can be accessed from the Licensing tab on the Driver Properties dialog.

The group of fields on this tab controls the generation of license reminders and is enabled when the Licensing checkbox is
checked.

Last renewal date

The date on which the license was last renewed.

Expiry date

The date on which the current license expires.

License duration

The period, in months, for which a license is valid after issue.

Reminder period

The period, in weeks, that you should be reminded before the license is due to expire

132
www.mixtelematics.com

132
 133
3.14.4 How to use the Extended Driver Identification functionality

© 2008 MiX Telematics | Updated 2008/05/07

The extended driver identification function supports third-party smart card identification cards to be used as a means of identifying
the driver. This functionality is available via the new digital tachograph (DTCO) and Kienzle Cardreader devices. It is therefore
possible to use multiple means of identification within a fleet.

All of the blue driver plug functionality is supported and therefore the extended driver identification can be used to control vehicle
access or just to report on driver performance data. In addition if an unmatched driver identification code is recorded, the Fleet
Manager database will automatically add a new driver record to log against all the recorded trip and event data.

The extended identification supports up to 128 bits entered as 32 hexadecimal or 16 ASCII characters on the Driver Properties
dialog.

Driver Configuration

The input format is defined on the Driver Configuration Group. When a driver is moved from one configuration group to another
the input format will change according to the select group. The default selection is that no extended driver identification cards are
used and therefore the input fields are not made available.

133
www.mixtelematics.com

133
 134

The ASCII input format is shown here:

With the Extended Driver ID reader device properties Identification tab shown below, one can now choose to allow unknown
driver identification cards to disarm the vehicle unit.

NOTE: The database will not allow duplication of Extended Driver ID values.

134
www.mixtelematics.com

134
 135

A similar Identification tab is available on the TCO Speed and ELVIST TCO Speed devices.

A new system level ‘Unmatched Extended DriverIDs’ driver is added with a Driver ID of 1. This will log the extended ID from the
card while using Driver ID 1 as the internal FM Driver ID for recording events, trip data, displaying on the terminal and sending
active events. The unknown ID is matched to the known driver records in the database to reflect the actual driver for trips and
events. If a match is not found a new Driver record will automatically be added to the selected Site and Configuration group with
the hexadecimal extended ID stored in the driver name, similar to the way that AutoPoll drivers are created. The user can then
update the driver record with the actual driver name.

135
www.mixtelematics.com

135
 136

The Extended Driver ID field is supported in the Extension SDK.

136
www.mixtelematics.com

136
 137
3.14.5 Fleet Manager DTCO Functionality

© 2008 MiX Telematics | Updated 2008/05/07

DTCO Functionality
Support was added to the Fleet Manager 8.32 release to allow Driver Identification to be done using the Driver Card, instead of
the blue or orange plugs. This, however, required the FMTCO interface and did not allow for time synchronization with the DTCO
internal clock. With Fleet Manager 8.35 the FM OBC can now record the data from the DTCO via the S3 serial port.

Electrical connection:

The info interface (D8) from the DTCO must be connected to pin 2 (TX) of a female DB9 connector that is connected to the S3
DB9 male connector on the FM OBC serial harness.

Database configuration:

The vehicle configuration is done as follows:

1. Connect ELVIST Speed to F1 and check the “Use DTCO Driver Identification” option.

2. Connect ELVIST RPM to F2.

3. Connect Serial TCO to S3.

The FM unit functions in the same manner as the previous versions of TCO, with the following differences:

1. As there is no chart door, Fleet Manager will consider ‘TCO Door Open’ to be true when there is no Driver card inserted. The
system will consider the door open until the card has been accepted by the TCO.

2. As the DTCO does not transmit all data packets while the ignition is off, the usual 5 minute delay for communication timeout
has been extended to 24 hours. This needs to be enabled by ensuring the option ‘Use DTCO Driver Identification’ is checked
on the F1 Speed from ELVIST configuration tab.

3. The FM OBC connects to DTCO directly (without TCO interface) on the serial port. This allows the timestamp and odometer to
be synchronized at the end of each trip. When the DTCO and GPS is connected, the FM OBC will not synchronize time with
GPS. The odometer is synchronized at the end of the trip when the vehicle is armed. The time is synchronized one minute
later.

IMPORTANT: For the time to be set to the correct time zone, it must initially be set via the blue driver code plug or remotely via
GPRS. The time synchronization allows for a difference of up to 2.5 minutes, leading or lagging. The time difference would
typically never be more than 5 seconds.

Synchronization of Timestamp with DTCO

The FM OBC connects to DTCO directly (without TCO interface) on the serial port. This allows the timestamp to be synchronized
on a regular basis (each trip) between the devices where DTCO is the master.

137
www.mixtelematics.com

137
 138

3.15 Passengers
3.15.1 How To Configure and Manage Passenger Code-Plugs

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The Fleet Manager software includes support for the black passenger code-plug. This code-plug is used to identify passengers
(non-drivers) getting into and out of a vehicle. The software also includes a report listing the various times that a passenger
identified himself/herself in the vehicle.

The Passenger Code-Plug

The passenger plug is a black coloured code-plug that is used to identify a passenger boarding a vehicle or exiting a vehicle.
When a passenger boards a vehicle, he/she inserts their plug into the pod in the vehicle and then removes it. The time of the
identification and the odometer reading are recorded with this passenger's identification. When the passenger alights from the
vehicle at a later stage, he/she inserts and removes their passenger plug again. The time of the identification and the odometer
reading are again recorded. The period between these two identifications is then interpreted as the period that the passenger was
on board the vehicle.

Managing Passengers

Adding New Passengers

After acquiring a black passenger code-plug from your Dealer, you should add records for your passengers and then initialise the
code-plugs.

New Passengers can be added by using the Add Passenger Icon on the Tool Bar: or by Right Clicking in the Passenger List
window.

Enter the passenger’s name and some descriptive notes if required, then click OK (see below).

138
www.mixtelematics.com

138
 139

Initialise Passenger Plug

Once you have created the passenger record, you need to initialise a Passenger code-plug to identify him/her. To do this, click
the Code Plug menu, followed by the Initialise Plug submenu, and then click the Passenger Plug submenu. Follow the
instructions in the Initialise Plug Wizard.

Testing the Passenger Code-Plug

In order to test that your passenger code-plug is set up correctly, you need to do a short trip. Identify yourself as the driver using
your blue driver code-plug, start a trip, and then insert the newly created black passenger code-plug. Complete the trip and
download the trip data into the Fleet Manager Client application.

In order to see that a passenger was identified by the unit, generate a “Passenger Identification Report” by clicking the Reports
menu, followed by the Vehicle Reports submenu, and then click the Passenger Identification submenu.

Follow the instructions in the Selection Criteria Wizard, being careful to select the correct vehicle and date/time range.

Fleet Manager Passenger Extension

The Fleet Manager Passenger Extension was designed and developed to extend the functionality of the passenger plug and
provides additional reporting on Passengers.

139
www.mixtelematics.com

139
 140
3.15.2 Passenger Properties

© 2008 MiX Telematics | Updated 2008/04/14

The property page for the passenger consists of only one tab:

General

Holds information about the passenger and contains two properties:

· ID Number
This property displays the ID number of the passenger and can not be modified.

· Name
The name of the passenger.

· Administrative Notes
A free-format field that can be used to hold any notes you wish to keep about the passenger.

For more information on Passengers, please see How To Configure and Mange Passenger Code-Plugs

140
www.mixtelematics.com

140
 141

3.16 Configuration Groups

3.16.1 Driver Configuration Group Properties

© 2008 MiX Telematics | Updated 2008/04/14

Driver Configuration Groups are templates designed to simplify the maintenance of Driver objects in the Fleet Manager system. A
Driver object may only belong to a single Driver Configuration Group. When a Driver object is added, property values from the
specified Driver Configuration Group are used as defaults for the new Driver.

The property page for a driver configuration group consists of three tabs:

General

Holds general information about the group and contains two properties:

· Name
The name of the group.

· Administrative Notes
A free-format field that can be used to hold any notes you wish to keep about the group.

Vehicle Access

This tab contains a single checkbox that indicates whether drivers in new groups should be able to access all vehicles or not.

Licensing

This tab contains details that will be used to generate reminders about the expiry of drivers licenses.

· License duration

141
www.mixtelematics.com

141
 142

The number of months for which a vehicle license remains valid.

· Reminder period
The number of weeks before the license expires at which you should be reminded of the upcoming expiry.

142
www.mixtelematics.com

142
 143
3.16.2 Vehicle Configuration Group Properties

© 2008 MiX Telematics | Updated 2008/06/12

Vehicle Configuration Groups are templates designed to simplify the maintenance of vehicles in the Fleet Manager system. A
vehicle may only belong to a single Vehicle Configuration Group. When a vehicle is added, property values from the specified
Vehicle Configuration Group are used as defaults for the new vehicle.

The property page for a vehicle configuration group consists of eight tabs:

General
Holds general information about the group and contains three properties:

· Name
The name of the group.

· Administrative Notes
A free-format field that can be used to hold any notes you wish to keep about the group.

· Target fuel consumption

A field used to enter the ideal fuel consumption for vehicles belonging to the group.

Servicing
Holds default information used when creating a new vehicle in the group. The tab contains four properties arranged into two
groups:

Remind on distance

Indicates the frequency of servicing the vehicle based on the distance units you are using.

143
www.mixtelematics.com

143
 144

· Service interval
Indicates the frequency in distance units at which servicing is required.

· Reminder period
Indicates the number of distance units before a service is due that you will be reminded at.

Remind on duration

Indicates the frequency of servicing the vehicle based on duration.

· Service interval
Indicates the frequency in months at which servicing is required.

· Reminder period
Indicates the number of weeks before a service is due that you will be reminded at.

You can define both distance and time-based reminders as both are evaluated when data is downloaded.

Engine Hours
Holds default information used when creating a new vehicle in the group. The tab contains three properties arranged into two
groups:

Monitor engine hours

Indicates whether or not engine hours should be monitored.

Service reminder

Indicates the frequency of servicing the vehicle based on engine hours.

· Service interval
Indicates the frequency in engine hours at which servicing is required.

· Reminder period
Indicates the number of engine hours before a service is due that you will be reminded at.

Licensing
Holds default information used when creating a new vehicle in the group. The tab contains four properties arranged into two
groups:

Licensing

· License duration
The number of months for which a vehicle license remains valid.

· Reminder period
The number of weeks before the license expires at which you should be reminded of the upcoming expiry.

Road worthiness details

· Road worthiness duration

The number of months for which a vehicle is certified road worthy.

· Reminder period
The number of weeks before the road worthiness certificate expires at which you should be reminded of the upcoming expiry.

144
www.mixtelematics.com

144
 145

Unit Types
Allows you to specify default properties for each unit type in the group.

Parameters
Presents a list of parameters that may be profiled by vehicles in the group. Editing a parameter allows the Profile ranges for
vehicles in the group to be changed.

Events
Allows the event configuration for the group to be viewed or modified. See Event Properties for a full description, but remember
the Event description may not be changed at the configuration group level.

145
www.mixtelematics.com

145
 146

3.17 Reporting Groups

3.17.1 Driver Reporting Group Properties

© 2008 MiX Telematics | Updated 2008/04/14

The Fleet Manager system allows groups of drivers to be defined for reporting purposes. A driver may belong to none, one or
many Driver Reporting Groups.

The property page for a driver reporting group consists of two tabs:

General
Holds general information about the group and contains two properties:

· Name
The name of the group.

· Administrative Notes
A free-format field that can be used to hold any notes you wish to keep about the group.

Membership

Allows you to specify which drivers are members of this group.

Click the checkbox on each record to toggle its value. The marked drivers are members of the group.

The list is hierarchical with vehicles being grouped according to their site. The checkbox on a site record can be used to select or
deselect all the vehicles in the site.

146
www.mixtelematics.com

146
 147
3.17.2 Vehicle Reporting Group Properties

© 2008 MiX Telematics | Updated 2008/04/14

The Fleet Manager system allows groups of vehicles to be defined for reporting purposes. A vehicle may belong to none, one or
many Vehicle Reporting Groups.

The property page for a Vehicle Reporting Group consists of two tabs:

General

Holds general information about the group and contains two properties:

· Name
The name of the group.

· Administrative Notes
A free-format field that can be used to hold any notes you wish to keep about the group.

Membership

Allows you to specify which vehicles are members of this group.

Click the checkbox on each record to toggle its value. The marked vehicles are members of the group.

The list is hierarchical with vehicles being grouped according to their site. The checkbox on a site record can be used to select or
unselect all the vehicles in the site.

147
www.mixtelematics.com

147
 148

3.18 Configuring the On-Board Computer

3.18.1 Event Configuration Overview

© 2008 MiX Telematics | Updated 2008/05/07

Overview
One of the most powerful features of the Fleet Manager system is the ability to monitor, detect and record events that occur within
your vehicles. You can configure the on-board computers in your fleet to detect and report on events that are of interest to you.
This process, known as defining the event configuration of the on-board computer, is done by defining Devices, Parameters and
Events and by setting parameters specific to different types of unit (on-board computer).

The Event Definitions dialog is accessed from the Edit menu in the Main window.

Devices

Devices are physical objects connected to the input lines of the on-board computers. Many standard devices, for example a
Speed Sender, are supported by the software and you can easily define other devices such as a Headlights Switch.

Events can be defined to take information from these external devices into account. For example, an event to detect Over
Speeding would take the value of Road Speed from the Speed Sender device into account.

Unit Types

148
www.mixtelematics.com

148
 149

The Unit Type list displays the type of on-board computers supported by the FM Professional software. See Unit Types.

From this list, you can specify which devices will be connected by default to each type of unit, as well as the default device
properties for each connected device.

If a device is connected to a particular type of unit at this level, all vehicles added to the database will have this device connected
by default unless it has been specifically removed for a Vehicle Configuration Group or Vehicle. User defined Devices may be
added or removed from the system. Devices may not be removed if they are configured to be connected to a unit. Editing a
device invokes the Device Property page, which allows configuration of the device.

Parameters

149
www.mixtelematics.com

149
 150

Parameters are used to represent the values returned by connected devices. Examples of standard parameters are Road Speed
(from the Speed Sender device) and Latitude (from the GPS Receiver device).

The list shows the name of each parameter that may be edited in the system. Editing a parameter invokes the Parameter
Property page, which allows the name and profile ranges to be changed if necessary. Parameters are added when creating a
device and removed when the last device referencing the parameter is removed.

Events

150
www.mixtelematics.com

150
 151

Events define what should be monitored and/or recorded by the unit as well as what other actions the unit should take when an
event is detected, for example sending a message back to the office, switching on or off a device etc. Examples of standard
events are Over Speeding, Harsh Braking and Excessive Idle.

The list shows the name of each Event that may be edited in the system and whether it should be monitored. User-defined events
may be added or removed from the system. Removing an event will cause all occurrences recorded for the event to be removed
too. Editing an event invokes the Event Property page which allows the name, condition, recording options and actions to be
changed.

Note: For a more in depth description of event configuration, please see About Devices, Parameters and Events and Defining
Custom Events.

151
www.mixtelematics.com

151
 152
3.18.2 About Devices, Parameters and Events

© 2008 MiX Telematics | Updated 2008/06/25

Overview
Fleet Manager Professional software allows you to define sophisticated events to be monitored by your vehicles. This is one of
the most powerful features of the Fleet Manager system. Please see the Event Configuration Overview before reading this
document.

This document covers the following topics:

· Definitions

· Structure of Model

· Defining Devices

· Connecting Devices

· Defining Unit Types

· Defining Parameters

· Defining Events

· Event Condition Editor

· Configuration Report

Definitions
The following section describes the terminology used in the Fleet Manager system.

Devices

A Device is a physical device connected to one of the input lines of the on-board computer. By definition a device can be either a
simple device that is used to monitor one state, i.e. a door switch or a speed sender, or a complex device that can monitor more
than one state or accept input, i.e. the FM Terminal or a tachograph.

There are two types of devices; Default devices, which are present in a new database, and User devices that may be added to
the system. Only simple devices may be added as User devices.

Each device may only be connected to a certain type of input line on the vehicle unit. A Wizard exists to simplify the process of
defining a new device. See the "Defining Devices" section below for more information.

Parameters

A parameter is the calculated value from a Device. All Event definitions are based on a combination of one or more Parameters.
There are three types of parameters in the Fleet Manger system.

System Parameters

System parameters are parameters that are available as standard features of the on-board computer. Examples of these are the
Current Date and the Day of Week parameters. These parameters cannot be removed from the system.

Default Parameters

152
www.mixtelematics.com

152
 153

Default parameters are parameters that are automatically created in the Fleet manager system when the Fleet Manager software
is installed. These parameters are dependent on a system Device being connected to one of the input lines. Examples of these
are the Road Speed and the Engine RPM parameters.

User Parameters

User parameters are parameters that are created by the user and are specific to the user’s needs. Examples of these parameters
include Fridge Temperature Sender and Door Switch. User parameters are created when a User Device is created.

Operators

Operators are used in the definition of an Event, to relate a Parameter to a Trigger or threshold value. Valid operators are Greater
Than (>), Less Than (<), Greater Than Or Equal To (>=), Less Than Or Equal To (<=), and Equal To (=).

Trigger Value

A trigger value is a threshold value, or a Boolean state (true/false) that determines when a condition is true.

Condition

A condition is the combination of a parameter, an operator and a trigger value. A combination of one or more conditions is used
to define when an event is recognised by the unit. For example, the default Over Speeding event occurs when the Road Speed
parameter is greater than 120 km/h (75 mph).

You could enhance the Over Speeding event to take a Siren On parameter into account. This would be useful in emergency
vehicles. In this case, you would define the Over Speeding event to occur when Road Speed is greater than 120 km/h (75 mph)
AND Siren On is False. In other words, over speeding would not be recorded in an emergency situation, if the siren were on.

Event Definitions
Events are monitored and recorded by the Fleet Manager on-board computer. An event occurs when the combination of its
conditions are true.

All Events can have various attributes assigned to them. This includes a recording delay, the level of detail to be recorded,
whether or not to sound the unit’s buzzer and whether or not to send a message to the office.

There are three types of events supported by the Fleet Manager system:

System Events

The vehicle unit uses these events internally. These events cannot be configured by the user and are therefore hidden from the
event configuration dialogs and reporting functions.

Default Events

These events are automatically created in the Fleet Manager system when the Fleet Manager software is installed. These events
cannot be removed from the system, however most can be disabled (not monitored) for a vehicle. Examples of these include the
Over Revving and Harsh Braking events.

User Events

The user defines these events, which gather information specific to the organisation’s needs. These events normally monitor the
user parameters defined for the organisation.

Calibration

Calibration values ensure that Fleet Manager monitors input lines correctly. The Fleet Manager unit monitors an electrical signal
from the sensor or switch in the vehicle. Calibration allows the Fleet Manager system to convert these electrical signals into

153
www.mixtelematics.com

153
 154

meaningful values for reporting. Reverse calibration is done when the event configuration is loaded into the unit, i.e. the trigger
values entered by the user are converted into the expected electrical values. The Fleet Manager unit can monitor both Frequency
signals and Voltage signals.

Structure of Event model

The Event Configuration is structured in three levels, namely the Organisation, Vehicle Configuration Group and Vehicle levels.

Changes made at the Organisation level can be cascaded down to the Configuration Group and the Vehicle levels. The same
applies to Configuration Groups; changes at this level can be cascaded down to all vehicles belonging to the group.

The Organisation level configuration is available from the Event Definitions menu on the Edit menu on the Main form. The Vehicle
Configuration Group and Vehicle level’s Event configuration are exposed as part of the Property dialog for the item.

Defining Devices
This section describes the functionality used to create and maintain Devices in the Fleet Manager system.

Accessing devices

The Organisation and Configuration Group levels both have a list of devices that may be edited. The Vehicle level shows a list of
Input lines and the devices attached to each input. This difference allows defaults to be set for all devices at the Organisation or
Configuration Group levels. At the vehicle level only one device can be connected to each input line.

Creation, naming and deletion of devices are only available from the Organisation level.

Creating a new device

To create a new device, click on the Add button. The Add Device Wizard is started.

The first step of the wizard allows the ID number and a description to be entered for the new device.

The ID and description must be unique for the database. If the ID number is left at 0, the system will assign the next available
device ID.

154
www.mixtelematics.com

154
 155

The second step of the wizard gives a choice between creating a new device and copying the details from an existing device.

If the device is copied, the wizard will display a list of existing devices that may be copied. After selecting the device to copy from,
the confirmation step is displayed.

The third step of the wizard specifies the type of device to be attached, from which the system will determine the type of input line
the device may be connected to.

There are eight types of devices that can be created:

· Switch max 38V

These devices are used to monitor the state (on/off, open/closed) of a switch such as a door switch up to a max. of 38V

· Switch max 117V

These devices are used to monitor the state (on/off, open/closed) of a switch such as a door switch up to a max. of 117V

155
www.mixtelematics.com

155
 156

· Analogue sender max 38V

These devices are used to monitor a range of voltages, up to a maximum of 38V. Example: temperature senders.

· Analogue sender max 5V

These devices are used to monitor a range of voltages, up to a maximum of 5V.

· Analogue sender max 84V

These devices are used to monitor a range of voltages, up to a maximum of 84V.

· Analogue sender max 117V

These devices are used to monitor a range of voltages, up to a maximum of 117V.

· Pulse Counter
These devices are used to count the number of pulses generated by a special purpose sender. Example: fuel flow meter.

· Frequency sender
These devices can be used to monitor a range of frequencies. Example: secondary RPM senders.

The fourth step of the wizard offers the option to link the device to an existing parameter, or to create a new one.

If the Existing Parameter is selected, the wizard will display a list of parameters for devices of the same type as the new device.
After selecting the parameter, the confirmation step is displayed.

By electing to use an existing parameter, two or more devices can be used to monitor a single parameter. An example of this is if
two types of temperature senders are used in a fleet. A device is created for each type of sender, allowing for separate default
calibration settings.

It is important to note that if two devices are linked to the same parameter, only one of the devices may be connected to a vehicle
at a time.

156
www.mixtelematics.com

156
 157

The fifth step of the wizard allows details for a new parameter to be entered.

If a specific ID number is to be assigned, the number should be a negative number, between -9999 and -1. Leaving the ID
number at 0 will cause the system to allocate the next available negative ID number. The description of the parameter is required
to be entered, and units can be specified if desired. The parameters of a digital switch have no unit.

The final step of the wizard displays the details entered for the device. Please note that the device type and the linked
parameter cannot be changed once the wizard is finished.

When the Finish button is clicked, the device and parameter is saved into the Fleet Manager database and is available for use in
the system.

157
www.mixtelematics.com

157
 158

Modifying Devices

Clicking the Edit button will open the properties for a device. At the Organisation and Vehicle Configuration Group levels, the
properties will have two tabs, a Device and a Calibration tab. The Device tab shows the device name (which may be changed
only at the Organisation level), the input line the device is to be connected to by default, and whether the device should be
monitored for interval data.

The Vehicle level displays a list of devices that may be connected to the selected input line. If a Frequency or Analogue device is
attached, a Profile tab will be displayed. This is described in the Parameter section below.

The Calibration tab is specific to the type of device, and is described below.

NOTE: It is possible to calibrate a device at the Organisation and Vehicle Configuration Group levels without specifying the
device as being connected. This allows a default calibration to be set, and when connected to a vehicle, the device will be
calibrated.

System Devices
The complex System devices each have their own configuration or usage guides. Please refer to these documents for the
description of the calibration settings.

Digital Switches

These devices may only be connected to the analogue input lines. The linked parameter is considered true if the voltage on the
line is higher and the Greater than (>=) is used, or if the voltage on the line is lower than the configured value and the Less than
(<) used. The Greater than (>=) is used when the parameter is true when there is a higher current (i.e. a light switch), while

the Less than (<) used when the parameter is true when there is lower current (i.e. a Door switch).

158
www.mixtelematics.com

158
 159

Analogue senders

These devices have a varying voltage that can be calibrated to reflect a value.

The Fleet Manager system assumes that these devices will have a uniform linear set of values. Two values with known voltages
have to be entered. Other possible values are calculated by the system from these entries using a linear algorithm. The high
resolution analogue send registers an input voltage range of 0 to 5 Volts, and can measure voltages with higher accuracy than
that of the standard analogue sender which is able to measure voltages from 0 to 38 Volts.

Pulse Counter

Pulse counters calculate a value based on the number of pulses received. As the system assumes 0 pulses to be a 0 value, only

159
www.mixtelematics.com

159
 160

one value for a known number of pulses has to be entered. Other values are calculated using a linear algorithm.

Frequency sender

These devices supply a value based on the frequency received on the input line. The Fleet Manager system requires two values
at known frequencies to be entered, and will calculate values for other frequencies using a linear algorithm.

Resolution of Frequency

The frequency and pulse devices also need to specify the resolution of the frequency input. The drop down selection shows the
available options and the range of frequencies the device can monitor. This selection affects both the event monitoring and the
Tachometer data.

Enabling and Disabling Transmitters

To comply with the safety regulations in specific industry sectors, drivers are able to inhibit all communication transmissions from
an in-vehicle "safe mode" switch.

To set up: In the Devices tab of a device connected to an I line, select "Transmission shut off switch".

160
www.mixtelematics.com

160
 161

When the switch is set, positive drive will be shut off, removing power to all devices connected to positive drive. The shut off is
not instantaneous, but first ensures that it is safe to shut down the GSM modem (all SIM and flash writers are complete) before
removing power. This will also affect the terminal on all OBC devices and GPS/GSM on FM300s.

Connecting Devices
Devices may be connected in one of two ways. The first is to create default Input Line connections for the Organisation or Vehicle
Configuration by specifying the input line the device is to be connected to. By default the Road Speed parameter is connected to
the F1 input line.

The second method of connecting a device is by specifying what device is connected to a specific input line on a vehicle’s
property page. This will override any configuration specified for the vehicle’s Configuration group or the Organisation defaults.

The vehicle will inherit the calibration from the Vehicle Configuration Group. This will be used unless the device’s calibration is
specifically changed at the vehicle level.

Defining Unit Types

Accessing Unit Types

This allows you to define Default Configurations for Unit Types.. This can be accessed from the Events Definitions function,
available from the Event Definitions menu item on the Edit menu, or the Event Definitions button on the Advanced Tab of the
Organisation Properties dialog.

Modifying a Unit Type

Unit Types cannot be added or deleted, but can be modified.

The default settings for the Unit Type can be defined, including the following:

· Which Devices use which input lines

· Calibration

· Recording of Engine Hours

161
www.mixtelematics.com

161
 162

· Driver Access

· Buzzer

Defining Parameters
This section describes the functionality used to maintain Parameters in the Fleet Manager system.

Accessing parameters

Parameters are defined once for the whole Organisation. The list of parameters is available on the Parameter Configuration tab
of the Event Definitions function. This can be accessed from the Event Definitions menu item on the Edit menu, or the Event
Definitions button on the Advanced Tab of the Organisation Properties dialog.

Creating a new parameter

Refer to the "Creating a new device" section above.

Modifying a Parameter

162
www.mixtelematics.com

162
 163

Once a parameter has been created, it can be modified. To do this, select the description in the list and click on the Edit button.

The description of the parameter may be changed, but the parameter type may not be changed after the parameter has been
created. The Units for the parameter may be changed if the parameter is not a Boolean parameter.

Deleting a Parameter

A parameter cannot be deleted. User parameters are removed from the system when the last device linked to the parameter is
deleted.

Defining Events
This section describes the functionality used to create and maintain Event Definitions in the Fleet Manager system.

Accessing Events

The Organisation’s list of Event Definitions is available on the Event Configuration tab of the Event Definitions function. This can
be accessed from the Event Definitions menu item on the Edit menu, or the Event Definitions button on the Advanced Tab of the
Organisation Properties.

At the Organisation level, Events can be created, modified and user events can be deleted.

163
www.mixtelematics.com

163
 164

Each Vehicle Configuration Group has an Event Definition tab. This does not allow new events to be created at this level, but
allows modification of the event definitions for a group of vehicles.

This is a powerful facility and can save time when customising the event definitions of a large group of vehicles that should all
have the same event configurations.

Depending on the unit type, an Event Definition tab may also be available in the Vehicle Properties. Again, event definitions can
only be modified at this level.

Only events that can be monitored by a vehicle will be shown in the Vehicle event list. Whether an event can be monitored or not
depends on the Device Configuration settings of the vehicle. For example, a vehicle will not monitor the Over Revving event if the
Engine RPM device is not connected.

164
www.mixtelematics.com

164
 165

Creating an Event

To create an event, go to the Event Configuration tab of the Event Definitions. Click on the Add button. The Event Definition form
will open, starting with an Add Event Wizard.

Step 1: Add Event Wizard

The First Step of the Add Event Wizard allows you to enter the ID Number of the Event and a description.

Step 2: Add Event Wizard

If the event should return a value either when recorded or via the active message, please specify which parameter to return a
value from.

If no value is to be recorded, select "Do not associate value with event" at the top of the list.

165
www.mixtelematics.com

165
 166

Step 3: Add Event Wizard

Select the value of the parameter that should be recorded. The following values can be chosen:

· Minimum

· Maximum

· Average

Step 4: Add Event Wizard

The last step of the Add Event Wizard provides a summary of what was selected during the wizard.

Click Finish when you are done.

166
www.mixtelematics.com

166
 167

First, specify the description for the new event. This description is used to identify the event for reporting purposes. This
description must be unique across all events in the Fleet Manager system.

The In Use option specifies whether the event will be loaded to the vehicle unit.

Next specify the conditions under which the event is considered true. Please see the Event Condition Editor section below for
more information on how to create conditions. There must be at least one condition defined before the event may be added.

Click on the Record tab. There are a number of settings on this tab. The recording delay is the time that the event must be true
before the unit will record the occurrence of the event. If this is disabled then the event will not be recorded by the unit, but can
still be used to sound the buzzer or enable the relay.

The Event Type frame allows you to select the required event type to determine the level of detail to be recorded by the unit.

The Recording Options change according to the type of event selected, and allow extra information to be recorded.

167
www.mixtelematics.com

167
 168

The Store Value frame allows you to specify a value to be stored when the event is true. If this option is checked, a drop down list
of parameters becomes available from which the required parameter can be selected. The type of value can also be selected.
The unit can store the Maximum, Average or Minimum value of the required parameter during the time the event is true. This
option may only be specified when adding an event to the system.

The final option allows a message to be entered. This will be displayed after downloading data from the vehicle

There are three event types:

· Notification
Each start of the Event will be recorded. The end of the event is not recorded; hence the unit will record no duration.

· Detailed
Each start and end of the Event will be recorded. This means that duration can be shown for each individual occurrence of the
event.

· Summarised
The number of occurrences and the total duration (the total amount of time that the event was true) will be recorded with each
sub trip.

Depending on the type of event specified, the Start and End Odometer and the Start and End Position (if a GPS device is
attached) can be recorded when the event occurs. Detail Events can also be configured to record the quantity measured by a
pulse counter. This is only possible if the vehicle has a Pulse counter device connected.

The first option on this tab specifies whether to sound the unit’s buzzer. If this is selected, a delay can be specified. Please note
that this delay is independent of the Record delay, enabling the unit to sound the buzzer before actually recording the event.

The next two options are used to instruct the unit to enable the external relays when the event occurs.

If either the buzzer or relay is enabled, the System Override may be specified. This will prevent the buzzer from sounding and the
relays from being enabled if a System Override plug is inserted before starting a trip. This override only works if a driver was
identified, the system disarmed, and the plug inserted before the ignition is turned on. The override is only active until the unit re-
arms.

An option for Progressive Activation is offered, which switches on a device gradually over 4 cycles. This means that the output

168
www.mixtelematics.com

168
 169

(e.g. buzzer) will switch on (e.g. beep) 11 times per cycle group (for 4 groups = 44 beeps). After each group (or 11 cycles) the
length of the beep will increase. Thus the first cycle of 11beeps will be short, growing longer per group until 180seconds passes
where after the buzzer will sound continuously, thus reached the on state.

This is typically used for the Progressive Shutdown of a vehicle fuel line driven from Relay Drive 1. It can be used with the Buzzer
and Relay Drive 1 for FM300, and for FM200 Plus it can be used on Relay drive 2 too.

This dialog is always visible at organisation level. It enables the unit to send an SMS message after an event has occurred. There
is also the option to send the vehicle coordinates with the event notification. This enables the user to see on a map exactly where
the event occurred. The Enable Active Tracking option allows the vehicle to be tracked for a specified amount of time after the
event has occurred.

169
www.mixtelematics.com

169
 170

Maintaining an Event
To maintain an event, go to the list of events at Organisation, Vehicle Configuration Group or Vehicle level. Click on the Edit
button to open the Event Definition dialog. All of the options described under “Creating An Event” can be changed except the
option to store a value.

PLEASE NOTE: You must remember to initialise the green code-plug for the vehicle or group of vehicles after adding, editing or
deleting events. The Fleet Manager software only reminds you to do this when modifying events at Organisation and Vehicle
Configuration Group levels. Changes will only take effect when the new configuration is uploaded into the unit the next time the
green plug is inserted into the vehicle’s code-plug socket.

Deleting an Event
To delete an event, select the event in the Organisation Event list and click the Delete button. Only User Events may be deleted
from the system. The system will confirm that the event is to be removed as this action will also remove all information for the
event that was recorded by vehicles.

Event Condition Editor

The event condition editor allows the user of the Fleet Manager system to view and modify the conditions that make up an event.
Any number of conditions may be entered for an event.

Required and Optional conditions

Default and User parameters can either be required or optional.

Required

170
www.mixtelematics.com

170
 171

If a parameter is required, it must be connected to an input line in the Input Configuration tab of the Vehicle Properties. If it is not
connected to an input line, events utilising this parameter in their conditions will not be listed in the Event Definition tab of the
Vehicle Properties. Conditions with required parameters are indicated by means of an icon with a blue line at the top.

Optional

If a parameter is optional, it does not need to be connected to an input line in the Input Configuration tab of the Vehicle
Properties. Events utilising these parameters in their conditions will be listed in the event definition of the Vehicle Properties, but
the condition containing the optional parameter will not be evaluated by the unit.

An example illustrating this is the Idle event. In the definition of the Idle event, the Road Speed parameter is required and the
Engine RPM parameter is optional. For a vehicle that has both parameters connected, both the speed and RPM conditions will be
evaluated. For a vehicle that does not have the Engine RPM parameter connected, the event will still be monitored, but only Road
Speed condition will be used to determine when the event occurs.

Basic Editing

Each condition is listed on a separate line in the editor. Each line is made up of the parameter’s icon (which specifies whether the
parameter is required or optional), the description of the parameter, the operator for the condition, the trigger value for the
condition, and the units of measure of the trigger value.

The components of the condition that are blue in colour may be edited. In order to change one of these components, move the
mouse cursor over the desired component. The mouse cursor will change to an I-bar when it is over an editable entry. Click on
the editable entry to begin editing it.

When clicking on an editable entry, a drop down list or an entry field will appear. To change the value, select the desired value, or
enter the value in the field.

Editing of a condition is only possible if one condition is selected. It is possible to select more than one condition by holding down
the Shift key and clicking on the required conditions. If more than one condition is selected, editing will not be permitted.

Order of evaluation

When evaluating the definition of an event, each condition is treated individually. When there are two or more conditions, each
condition is joined to the next using an AND operator or an OR operator. The AND requires that both the conditions be true, the
OR only requires one of the conditions to be true.

If the definition contains both AND and OR, the unit will evaluate the conditions joined by AND first, then the conditions joined by
OR. This order of evaluation can be changed using brackets (parentheses) to group conditions. Conditions inside brackets are
evaluated before other conditions. The event editor will allow brackets to be nested four levels deep.

Inserting a Condition

To insert a condition into the event definition click on the Insert button. A condition will be inserted above the currently
selected condition. If this button is disabled, a condition may not be inserted before the selected condition. This can occur if more
that one condition is selected, or the current condition is part of a default event’s definition.

Removing a condition

To remove one or more conditions, select the conditions and click the remove button. Conditions defined as part of a default
event cannot be deleted. If more than one condition is selected, and a bracket is part of this selection, the corresponding bracket
must also be selected before the remove button will be enabled.

If an opening bracket is the only selected line, removing this will cause the both the opening and closing bracket to be removed.
The conditions that were contained within the brackets will be retained.

Moving a condition

171
www.mixtelematics.com

171
 172

It is possible to move one or more conditions relative to the other conditions. When one condition is selected, click on
the Move Up button. This will swap the selected condition with the condition above. If more than one condition is selected, the
condition above the selection is moved below the selection. The reverse happens if the Move Down button is clicked.

It is possible to move one or more conditions into or out of brackets. If the selection does contain brackets, this will cause the
bracket nesting level to be increased or decreased. If the nesting level would exceed four levels, the move would be disallowed i.
e. the button would be disabled.

It is not possible to move a single bracket over another bracket. The move button will be disabled to prevent this.

Bracketing conditions

Bracketing conditions changes the order of evaluation of the event’s conditions. To bracket conditions, select two or more
conditions and click on the Bracket button. The selection conditions will be indented and brackets placed around them.

Configuration Report

The Vehicle Configuration Report, available from the Vehicle Report sub menu allows the configuration for one or more vehicles
to be printed. The report shows the devices connected to the vehicle, the calibration, as well as the definition for each event that
will be monitored by the unit.

172
www.mixtelematics.com

172
 173
3.18.3 Defining Custom Events

© 2008 MiX Telematics | Updated 2008/06/12

Overview
The Fleet Manager Professional software allows you to define sophisticated events to be monitored by your vehicles. This is one
of the most powerful features of the Fleet Manager system. Please see Event Configuration Overview before reading this
document.

How to define an event

The following steps define the procedure to be followed to create a “Driver Door Open” event. This event will detect and record
times when the driver door is open.

Step 1. Creating a New Device and Parameter

The first step in creating this new event is to create a “Driver Door Switch” device and the corresponding Driver Door Open
parameter, which will be used in the definition of the new “Driver Door Open” event. To access the Event Definitions, click the
“Edit” menu, and then click “Event Definitions”.

Click the “Devices” tab. A list of devices defined in the system will be displayed. User-defined parameters will only be monitored
by a unit if the corresponding device is marked as attached to the unit.

173
www.mixtelematics.com

173
 174

Step 1

Click "Add" to begin creating the new Device and Parameter.

The “Add Device Wizard” will be displayed. The first step requires a description of the device. Enter “Driver Door Switch” and click
Next.

Step 2

Step 2 gives you the option to copy the type and linked parameter from an existing device. As we are creating our first device,
select Create a New device and click Next.

174
www.mixtelematics.com

174
 175

Step 3

Step 3 is where the type of the new device is selected. For a door switch, make sure the Switch max 38V is selected and click
Next.

Step 4

Step 4 allows the creation of a new parameter, or linking the new device to an existing parameter already created for another
device.

As there are no existing parameters, only the “Create a new parameter” option is available and selected.

175
www.mixtelematics.com

175
 176

Step 5

Step 5 allows the details of the new parameter to be entered. Type the description of the parameter “Driver Door Open” and click
Next.

Because the device is a Boolean device that can only be on or off, we cannot specify units.

Step 6

The last step confirms the details of the new device and parameter. The Type of device and the link between the device and
parameter cannot be changed after this wizard is finished.

Once you have checked that the details are correct, click Finish.

176
www.mixtelematics.com

176
 177

Once the device is added, the device properties are displayed.

The second tab allows the voltage to be entered above or below which the parameter is to be considered True. Normally door
switches are True when there is no current (i.e. the switch is open) so select the <= option.

Click OK to save the changes.

Step 2. Defining your Event

The second step is to create the event. Select the Event tab, which shows a list of available events.

Click "Add" to create a new event.

Step 1 of Event Wizard

Enter “Driver door open” in the description field.

Step 2 of Event Wizard

Select "Do not associate value with Event"

177
www.mixtelematics.com

177
 178

Click Next.

If you are happy with the final values, click Finish.

Click the Insert icon ( ) to allocate the first condition to the event. The first parameter listed alphabetically will be displayed.
Clicking on the text will change the text into a drop down combo box control, from which you can select the Driver Door Open
parameter. The trigger value will default to True.

Next, click on the Record Tab. This shows the options that specify what is to be recorded when the event’s condition becomes
true.

The first option is a delay before the event. If you wish to only record this event if the driver’s door is open for more than 45
seconds, set the time in the delay time field. It is possible to turn off recording an event, in which case only the Actions will be
performed.

178
www.mixtelematics.com

178
 179

The Event type determines what is recorded. Detailed events are used when you need to know when each occurrence of the
event starts and ends. Detailed events also allow the Odometer reading, Position (Only available if a GPS device is attached to
the unit) and pulse count (Only available if a Pulse counter e.g. EDM is attached to the unit) to be recorded at the start and end of
the event.

If required a message can be entered that is displayed at the end of the Trip Download Wizard if an occurrence of the event was
found in the data.

The Actions tab allows you to configure the unit’s buzzer and Relays.

179
www.mixtelematics.com

179
 180

These are the settings for SMS message notification. You can configure SMS message priorities, and enable active tracking.
These settings will not be available at vehicle level or vehicle configuration level if the vehicle does not have a GPS and GSM
connected with SMS messaging enabled.

Once you have set up the event, click OK to save it. It will then appear in the list of events. Click Close to close the Event
Definition dialog.

Step 3. Uploading the new configuration to a unit

If the Driver Door Switch device was attached at the Organisation level, the individual vehicle properties do not have to be
updated.

Step 1

Start the Update Vehicle Plug wizard from the Initialise Plug sub-menu on the Code Plug Menu. The first step is to ensure the
vehicle’s green plug is inserted into the download module, then click Next.

180
www.mixtelematics.com

180
 181

Step 2

The second step is to select the vehicle. The wizard checks the plug and selects the vehicle in the list. This is to ensure the
correct plug is in the download module. If the correct vehicle is selected, click Next.

Step 3

Step 3 shows the options of what can be uploaded to the vehicle. Make sure the Update Unit Event configuration is selected.

Optionally, the Odometer can be updated. The Plug storage ratio determines how much Tachograph data vs. event data is stored
in the plug.

NOTE: The unit has fixed areas for storing data that cannot be changed.

Click next to go to the final step.

Step 4

Click Next.

181
www.mixtelematics.com

181
 182

Step 5

The last step confirms the actions that will be performed on the plug. Click finish to update the plug. A message is displayed until
the plug has been updated. You can then take the plug and insert it into the unit’s socket to complete the upload.

Congratulations! You have defined a simple event, enabled it for monitoring by a vehicle unit, and uploaded the new event
configuration into the vehicle unit.

182
www.mixtelematics.com

182
 183
3.18.4 Device Properties

© 2008 MiX Telematics | Updated 2008/04/14

Devices are the physical items that can be connected to the on-board computer. The device list can be accessed by selecting
Event Definitions from the Edit menu option.

Double-click on a device in the list to access the Device Properties dialog:

183
www.mixtelematics.com

183
 184

Device Properties
There are usually two or more tabs containing the properties specific to the device. The first tab always contains one or more of
the following details:

· ID Number
Holds the internal ID number of the device. This may not be updated.

· Description
Holds the description of the Device.

· Value Parameter
Holds the name of the parameter which is used to test the value returned from the device. This may not be updated.

Calibration
For certain devices, a Calibration tab will be available. Calibration is dependent on the type of device whose properties are being
viewed. Below are some examples:

· Boolean Switches
For switches, the threshold voltage and whether the switch is "on" or "true" when the voltage is high or when low.

· Analog Sender
Two known sets of values may be entered, from which other values will be calculated using a linear algorithm. The maximum
and minimum possible values are displayed.

184
www.mixtelematics.com

184
 185

· Pulse Counter
A known value for a certain number of pulses is entered. The system uses a linear calculation to determine other values.

· Frequency Sender
Two known sets of values may be entered, from which other values will be calculated using a linear algorithm. The maximum
and minimum possible values are displayed.

· FM Terminal
This holds the path containing the FM Terminal script files, the script to be used and the Primary and Secondary languages.

· KTCO 1318 Tachograph

There is no direct calibration of the KTCO, except to specify whether the tachograph supplies engine RPM or not.

· GPS
If the GPS power supply is controlled by the FM200 output relay, the time delay can be set here. The other settings specify
whether to record a trail of where the vehicle was driven. The distance factor allows the trail not to be recorded for the first part
of a sub trip, allowing for yard positioning.

· GSM modem
The unit phone number, power turn off delay and the default PIN code may be set.

NOTE: In order to change the PIN code on the SIM card, the SIM card must be extracted from the GSM device and the PIN
changed on a normal hand held device.

NOTE: For a more in depth description of Event Configuration, please see Event Configuration Overview as well as About
Devices, Parameters and Events

185
www.mixtelematics.com

185
 186
3.18.5 Parameter Properties

© 2008 MiX Telematics | Updated 2008/06/12

Parameters expose values recorded by devices and are used to define events.

· ID
Holds the internal ID number of the parameter, which cannot be changed.

· Description
Holds the description of the parameter.

· Type
Defines the type of parameter, which cannot be changed. Parameter types are Value Range, Digital Switch, Date and Time or
Pulse counter. The type can only be set while using the Add Device wizard.

· Units
Defines the description of the units measured by frequency and analogue parameters. Not used for other types of parameters.

If the parameter is a Pulse Counter there is an option to specify that the value of the parameter is Fuel Quantity, which can be
used in the Measured Fuel Reports and Graphs.

The system parameters (created by the system at installation time) cannot be deleted, although their descriptions can be
changed. However, if you change their descriptions you may render the system outputs such as reports and graphs meaningless.

For analogue and frequency parameters, a second tab will become available on which the profile ranges of values may be

186
www.mixtelematics.com

186
 187

entered.

Note: For a more in depth description of Event Configuration, please see Event Configuration Overview

187
www.mixtelematics.com

187
 188
3.18.6 Event Properties

© 2008 MiX Telematics | Updated 2008/06/12

The Event Properties dialog is used to define events.

Parameters
Defines the event and contains the following properties:

· ID Number
The non-updatable ID number of the event.

· Description
The displayed name of the event.

· In Use
Specifies whether the event is to be used by the vehicle. This allows events to be defined but not uploaded into a vehicle.

· Event conditions
A list of conditions that specify when the event becomes true. The Conditions are made up from the parameters defined in the
system.

188
www.mixtelematics.com

188
 189

Record
Specifies what must be recorded when the event occurs and contains six properties:

· Record delay
Indicates a delay time that the event must be true before the unit records it. If this is turned off, the event will not be recorded,
but the unit will only sound the buzzer or enable the relay.

· Event Type
Indicates the type of event and can have one of the following values:

a) Notification
Will merely record the time the event occurred.

b) Detailed
Will record the start and end time for each occurrence of the event.

· Summarises
Will record the number of times the event became true, and the total time the event was true for each sub trip.

· Recording options
The available recording options depend on the type of event. When available, the options include whether to store the
Odometer Reading at the start or end of recording the event, the Position (if a GPS is connected) at the start or end of
recording the event, and, if the unit has a parameter of type Pulse Counter attached, to store the pulses recorded while the
event was true.

· Display the following message when the Event is downloaded

This allows you to display the typed message when the event occurs during a plug download. This is only applicable to plug
downloads.

Actions
Defines what action must be taken when the event occurs and contains five properties:

· Sound the buzzer after

Indicates whether an alarm must warn the driver and if so after how long.

· Enable the relay after

Indicates whether the relay must be switched and if so after how long. This will not be available if a GPS or other device is
using the relay for power control.

· Allow Override
Only available if either Buzzer or Relay delays are enabled. If marked the alarm and relay will not activate during a trip if a
System Override plug was inserted between identifying the driver and starting the trip.

· FM Terminal warning message

This allows a critical warning to be enabled that will be displayed for certain events on the FM Terminal after the configured
delay.

Active
Defines additional, communication actions that must be taken when the event occurs and contains two properties:

· Queue SMS Message

Indicates whether the vehicle is to send an SMS message notifying that the event has occurred. You are able to specify the
delay (time that the event must be true) before a message is sent, the priority for the message and whether the message
should include GPS position information. Note that this delay is independent of the recording delay and the delay period begins
immediately the event becomes true. There are two possible priority settings. Urgent will cause an SMS message to be sent
immediately (after the delay) while Normal will cause the event message to be queued to be sent in an SMS message when

189
www.mixtelematics.com

189
 190

the message is full or before that if another event with urgent priority occurs.

· Enable Active Tracking

Indicates whether that the vehicle should be actively tracked (position information sent at regular intervals) when the event
occurs. If this option is turned on, the time for which active tracking should be turned on can be chosen as well as the interval
at which the active tracking messages are to be sent.

The default events that are loaded when the system is installed cannot be deleted, although their descriptions can be changed.
However, if you change their descriptions you may render the system outputs such as reports and graphs meaningless.

Notes:

· At least one of the delays (Recording, Buzzer or Relay) must be enabled for the event to be saved.

· For a more in depth description of Event Configuration, please see Event Configuration Overview

190
www.mixtelematics.com

190
 191
3.18.7 Default Vehicle Configurations

© 2008 MiX Telematics | Updated 2008/05/07

If a new unit has been added to a new database, the following default vehicle configuration settings are used.

Unit Settings

Arming Delay 00:05:00

Standing Delay 00:02:00

FM200 only

Disarm Buzzer Action Sound for 10 seconds

Input Parameters

FM100 F1 - Road Speed - Units = Km/h

F2 - Engine RPM - Units = RPM

FM200 Plus F1 - Road Speed - Units = Km/h

F2 - Engine RPM - Units = RPM

*No Connections* to F, I or S inputs

FM200 Locator F1 - Road Speed - Units = Km/h

F2 - Engine RPM - Units = RPM

F3 - GPS Receiver

FM200 Communicator F1 - Road Speed - Units = Km/h

F2 - Engine RPM - Units = RPM

F3 - GPS Receiver

S2 - GSM Modem

Messenger F1 - Road Speed - Units = Km/h

F2 - Engine RPM - Units = RPM

F3 - GPS Receiver

S1 - FM Terminal

S2 - GSM Modem

191
www.mixtelematics.com

191
 192

Navigator F1 - Road Speed - Units = Km/h

F2 - Engine RPM - Units = RPM

S2 - GSM Modem

S3 - GPS Receiver

Battery Disconnection Event (FM200 only)

Record After: 00:00:00

Event Type: Notification only

Alarm After: 00:00:00

Relay After: No Relay

Recording Options: System Override Plug does NOT disable Alarm and Relay

Start Odometer of occurrence is NOT recorded

End Odometer of occurrence is NOT recorded

Pulse count from F3 parameter (fuel, etc.) is NOT recorded

Record Latest value of Battery Disconnect Date/Time

Download Message Battery was disconnected from unit

Trigger When: Battery Disconnect duration > 120 sec

Harsh Acceleration Event (FM200 Only)

Record After: 00:00:00

Event Type: Summarise only

Alarm After: No Alarm

Relay After: No Relay

Recording Options: System Override Plug does NOT disable Alarm and Relay

192
www.mixtelematics.com

192
 193

Start Odometer of occurrence is NOT recorded

End Odometer of occurrence is NOT recorded

Pulse count from F3 parameter (fuel, etc.) is NOT recorded

Record Maximum value of Acceleration

Download Message

Trigger When: Acceleration > 8 Km/h/s

Harsh Braking Event

Record After: 00:00:00

Event Type: Summarise only

Alarm After: No Alarm

Relay After: No Relay

Recording Options: System Override Plug does NOT disable Alarm and Relay

Start Odometer of occurrence is NOT recorded

End Odometer of occurrence is NOT recorded

Pulse count from F3 parameter (fuel, etc.) is NOT recorded

Record Maximum value of Deceleration

Download Message

Trigger When: Deceleration> 15 Km/h/s

Idle Event

Record After: 00:00:00

Event Type: Summarise only

Alarm After: No Alarm

193
www.mixtelematics.com

193
 194

Relay After: No Relay

Recording Options: System Override Plug does NOT disable Alarm and Relay

Start Odometer of occurrence is NOT recorded

End Odometer of occurrence is NOT recorded

Pulse count from F3 parameter (fuel, etc.) is NOT recorded

Record

Download Message

Trigger When: Ignition On True AND

Road Speed < 5 Km/h AND

Engine RPM > 0 RPM AND

Engine RPM < 1500 RPM

Excessive Idle Event

Record After: 00:03:00

Event Type: Summarise only

Alarm After: No Alarm

Relay After: No Relay

Recording Options: System Override Plug does NOT disable Alarm and Relay

Start Odometer of occurrence is NOT recorded

End Odometer of occurrence is NOT recorded

Pulse count from F3 parameter (fuel, etc.) is NOT recorded

Record

Download Message

Trigger When: FM200

Ignition On True AND

Road Speed < 5 Km/h AND

194
www.mixtelematics.com

194
 195

Engine RPM > 0 RPM AND

Engine RPM < 1500 RPM

FM100

Road Speed < 5 Km/h AND

Engine RPM > 200 RPM

Out of Green Band Driving Event

Record After: 00:00:00

Event Type: Summarise only

Alarm After: No Alarm

Relay After: No Relay

Recording Options: System Override Plug does NOT disable Alarm and Relay

Start Odometer of occurrence is NOT recorded

End Odometer of occurrence is NOT recorded

Pulse count from F3 parameter (fuel, etc.) is NOT recorded

Record

Download Message

Trigger When: ( Engine RPM < 2000 RPM OR Engine RPM > 4500 RPM ) AND

Road Speed > 25 Km/h

Over Revving Event

Record After: 00:00:00

Event Type: Summarise only

Alarm After: No Alarm

Relay After: No Relay

195
www.mixtelematics.com

195
 196

Recording Options: System Override Plug does NOT disable Alarm and Relay

Start Odometer of occurrence is NOT recorded

End Odometer of occurrence is NOT recorded

Pulse count from F3 parameter (fuel, etc.) is NOT recorded

Record Maximum value of Engine RPM

Download Message

Trigger When: Engine RPM > 4500

Over Speeding Event

Record After: 00:00:00

Event Type: Summarise only

Alarm After: No Alarm

Relay After: No Relay

Recording Options: System Override Plug does NOT disable Alarm and Relay

Start Odometer of occurrence is NOT recorded

End Odometer of occurrence is NOT recorded

Pulse count from F3 parameter (fuel, etc.) is NOT recorded

Record Maximum value of Road Speed

Download Message

Trigger When: Road Speed > 120 Km/h

196
www.mixtelematics.com

196
 197

3.19 Reports
3.19.1 Criteria Wizard

© 2008 MiX Telematics | Updated 2008/06/12

When you request a report or graph a Wizard guides you through the entry and selection of your criteria. The Criteria Wizard
allows you to refine the report to suit your needs. The Criteria Wizard could allow you to select the following:

· Site, Reporting Groups or Individual Drivers/Vehicles

· The detail level of the report e.g. Detailed, Daily, etc.

· Time period of the report

· More Options depending on the type of report

The last step of the wizard allows you to save your selection criteria in a criteria (.CRI) file so that you can easily generate a
report using the same criteria at a later stage.

Saved criteria files can also be used in the Report Batches and to create shortcuts on the Shortcut Bar.

197
www.mixtelematics.com

197
 198
3.19.2 Reporting Batches

© 2008 MiX Telematics | Updated 2008/06/12

Reporting batches allow a group of saved criteria files to be submitted to the Report generation routine. The reports and graphs
will be generated and saved into a specified folder.

The Report Batches dialog displays a list of batches that have been created. Buttons on the right of the list allow new batches to
be created, and existing batches to be edited or deleted. The Run button will submit the highlighted batch to the report generation
routine.

The batch maintenance form allows you to specify the criteria files that should be used by the batch, and the folders where the
generated files should be saved.

Scheduled Reporting
In some cases you might wish to generate reports automatically, under the control of a scheduling tool. This can be achieved by
executing the Fleet Manager Client (FMCli8.exe) and passing the fully qualified name of a reporting batch file (.RBF) to it as a
command line parameter. For example;
"C:\Program Files\Fleet Manager Professional\FMCli8.exe" C:\Data\sample.rbf
When you do this the Fleet Manager Client executes in a hidden mode. Status information relating to the execution of the
reporting batch is written to the Batch reporting log file specified on the Reporting tab of the Options dialog.

How to create a scheduled report using Windows XP

Step 1: Create a Report Batch

Create a new report batch using the Reporting Batches function available from the Reports menu.

When you have completed setting up the Reporting Batch, close Fleet Manager Professional.

198
www.mixtelematics.com

198
 199

Step 2: Add a new Scheduled Task

The list of Scheduled Tasks can be viewed by selecting Scheduled Tasks in the Control Panel.

Click Add Schedule.

Follow the wizard and add FMCli8.exe as the selected Program. It is normally situated in C:\Program Files\Fleet Manager
Professional unless another directory was chosen during the initial installation.

Select the name of the Scheduled Task, and how frequently the task should be performed.

Depending on the frequency required, please select the additional information needed, such as time of day, day/days/months the
task should run.

199
www.mixtelematics.com

199
 200

Enter your Windows User Name and password. Type in the password again to confirm it.

Note: You must enter your password or the scheduled task will not run.

On the last page of the Wizard, select the checkbox "Open Advanced properties for this task when I click Finish"

Click Finish

Step 3: Select Advanced Properties of the Scheduled Task

In the Run text field, enter the following:

"C:\Program Files\Fleet Manager Professional\FMCli8.exe" C:\Data\sample.rbf
Where "C:\Program Files\Fleet Manager Professional\FMCli8.exe" is the location of the FMCli8.exe file and C:\Data\sample.rbf
the name of the Report Batch file you want to run.

200
www.mixtelematics.com

200
 201

When you are finished, click OK.

The Scheduled Task will now appear in the Scheduled Tasks list. If you would like to run the Task immediately, you can right-click
on the FM Professional Task icon, and select "Run".

201
www.mixtelematics.com

201
 202
3.19.3 Activity Timeline

© 2008 MiX Telematics | Updated 2008/06/24

The Activity Timeline displays trip and event information for a driver or vehicle graphically in the form of a timeline. The timeline
can display up to 24 hours (a full day) of information and can be zoomed in to display various time periods down to 1 hour.

Note: The Fleet Manager Timeline Reports Extension can be used to generate a report containing an Activity Timeline for
multiple vehicles over multiple days.

Tool bar

Print the Activity Timeline

Open the Trip Information dialog

View the Tachograph Data. The selected time period should be less than 9 hours.

Select the events that must be graphically displayed on the timeline

Change the time period visible on screen.

Specify whether drivers or vehicles are being viewed. If a trailer is present, the Trailer ID and
description will be available to report on.

Select the vehicle or driver to view.

View Previous Day

The Current selected date

View Next Day

Select the time of day from which to start the timeline.

Using the Activity Timeline

The window has two main areas. The upper one shows trips and events graphically on the timeline while the lower one shows
textual information describing those trips and events.

Tip: Maximise the timeline window for best viewing results.

· Use the arrow buttons on either side of the date control to move forwards or backwards one day at a time.

· Click on a parking or driving time block to select it and display more details.

· Once you have selected a driving or parking time the arrow keys will move forwards and backwards through periods of the
same type as the selection.

202
www.mixtelematics.com

202
 203

· If there are several small trips close together click to one side of them and drag past them before releasing the mouse button.
This will select the entire period and show you the details of all the trips.

· Click outside the timeline or press escape to deselect the selected area.

· Selecting the Trip Information command will open a dialog showing details of the selected trip. You can also assign a trip
category and enter trip notes on this dialog.

Interval (Tacho) Data

Interval (Tacho) Data is available when the "Interval (tacho) data available" row in the graphical window, is highlighted in green
(see below).

The second-to-second data can be viewed by selecting the icon from the Tool bar. See Tachodata Graph for more
information

203
www.mixtelematics.com

203
 204
3.19.4 Tachograph Data

© 2008 MiX Telematics | Updated 2008/06/24

The Interval (Tacho) Graph is a specialised form of the graph window used to display the interval (tacho) data recorded by an on-
board computer. Selecting a period of up to 9 hours on the Activity Timeline and clicking the Interval (Tacho) Graph tool button
opens this form.

Although you may have requested recording of tacho data for several parameters, only two can be displayed at a time due to the
limitations of a two-dimensional graphing system. Each line is plotted using it's own scale on either the left or right vertical axis.
Controls are provided on the toolbar for selecting the data that is to be plotted against each axis.

Tool bar

Open a saved graph

Save the graph

Print the graph

Copy the graph

View Graph Designer. The Graph Designer allows you to change Graph related details
such as edit title etc.

View Graph Wizard. Allows the Chart Type to be changed to Area, Bar, Line, Step, Pie and
more.

Selects the Input to appear on the Left Axis.

Note: F1 supports a Hi-Resolution Speed Sender device for slow moving vehicles,
indicating speed measured in metres per minute .

Selects the input to appear on the Right Axis

204
www.mixtelematics.com

204
 205
3.19.5 Driver and Vehicle Lists

© 2008 MiX Telematics | Updated 2008/05/07

Driver List
This report lists all drivers matching the selection criteria. Drivers are grouped by site and the following columns are displayed.

· Site

· Name

· Employee number

· Configuration group

· Driver ID

· Reporting Group

Vehicle List
This report lists all vehicles matching the selection criteria. At least the following information is shown for each vehicle.

· Site

· Description

· Unit type

· Configuration group

· Vehicle ID

The following optional information may also be shown.

· Last trip - date and odometer

Reflects the date of the last trip and the odometer reading at the end of that trip.

· Service - next, interval and reminder

Reflects the servicing information that has been defined for the vehicle.

· Arming - delay and buzzer

Reflects the delay before the unit rearms after a trip and the buzzer action that will take place if a trip is started without driver
identification.

· Target fuel consumption

Reflects the target fuel consumption that has been defined for the vehicle.

· Reporting groups
Reflects the reporting groups that the vehicle belongs to.

205
www.mixtelematics.com

205
 206
3.19.6 Trip Reports

© 2008 MiX Telematics | Updated 2008/06/24

Trip Report - detail (applies to vehicle and driver reports)

This report reflects details of individual trips. Optionally, details of sub-trips can be shown. If sub-trips are shown then selected
event details may also be shown. Each of these is shown on a separate line.

The following columns are shown:

· Start
This column applies only to a trip record and indicates the time at which the trip started.

· Depart
For sub-trip records this column indicates the departure time for the sub-trip. For trip records this column indicates the
departure time of the first sub-trip in the trip.

· Driving
This column indicates the portion of the trip or sub-trip during which the vehicle was considered to be driving.

· Idle
This column indicates the portion of the trip or sub-trip during which the vehicle was considered to be idling.

· Duration
This column indicates the duration of the trip or sub-trip. For trips this is the period from start to end and for sub-trips it is the
time from depart to halt.

· Halt
For sub-trip records this column indicates the time at which the vehicle halted at the end of the sub-trip. For trip records this
column indicates the halt time of the last sub-trip in the trip.

· Standing
This column indicates the portion of the trip that the vehicle was considered to be standing. For sub-trip records this is the time
between the halt time and the trip end time or the depart time of the next sub-trip in the trip.

· End
This column applies only to trip records and indicates the time at which the trip ended.

· Parking
This column applies only to trip records and indicates the time between the end of the trip and the start of the following trip.

· Max speed
This column indicates the maximum speed attained during the trip or sub-trip. If the High-Resolution Speed Sender is used for
slow-moving vehicles, this may be given in metres per minute.

· Avg speed
This column indicates the average speed for the trip or sub-trip. If the High-Resolution Speed Sender is used for slow-moving
vehicles, this may be given in metres per minute.

· Distance
This column indicates the distance that the vehicle travelled during the trip or sub-trip. Due to the fact that the vehicle unit
measures to the closest 100 metres, this may be zero if the vehicle moved less than 100 metres. In this case the average
speed cannot be calculated and is shown as zero. For slow-moving vehicles using the High-Resolution Speed Sender,
distance may be measured in metres.

Trip records are identified by the presence of a value underneath the start column. Sub-trip records are identified by the absence
of a start value but the presence of a depart value. Event records are shown as strings of concatenated information relating to the
event. The left-hand side of these strings aligns with the left of values in the depart column.

206
www.mixtelematics.com

206
 207

Events are shown in chronological order with events occurring within a sub-trip appearing below that sub-trip.

Trip Report - daily (applies to vehicle and driver reports)

This report shows one line per day for each vehicle or driver that matches the selection criteria. Most of the columns are the
same as those on the detail trip report with the following exceptions.

· Date and day

These columns start each line and show the date and day that the line applies to.

· Odometer (end)
This column reflects the odometer reading at the end of the day.

· Trips/Events
This column reflects the number of trips and events that occurred during the day, separated by a slash character.

Trip Report - monthly (applies to vehicle and driver reports)

This report shows one line per month for each vehicle or driver that matches the selection criteria. Most of the columns are the
same as those on the detail trip report with the following exceptions.

· Month
This column shows the month and year that the line applies to.

· Odometer (begin)
This column reflects the odometer reading at the beginning of the month that the line applies to.

Trip Report - summary (applies to vehicle and driver reports)

This report shows one line for each vehicle or driver that matches the selection criteria. Most of the columns are the same as
those on the other trip reports with the following exceptions.

· Driver/vehicle
This column shows the name of the driver or the description of the vehicle that the line applies to.

· Recorded period
This column shows the start and end dates within the period for which the relevant driver or vehicle had trips.

207
www.mixtelematics.com

207
 208
3.19.7 Driver Scoring Report

© 2008 MiX Telematics | Updated 2008/05/07

This report shows a single line for each driver matching the selection criteria, grouped by site. The following columns are shown.

· Driver

· Duration

· Distance

· Over speeding score

· Over revving score

· Harsh braking score

· Excessive idling score

· Green band score

· Harsh Acceleration

· Average score

The scores are calculated according to the rules defined on the Driver Scoring tab of the Organisation Properties dialog. Each
score reflects how well the driver scored as a percentage, with 100% being a perfect score.

Note: The Advanced Driver Scoring Report Extension enables you to define other methods of calculating driver scores.

208
www.mixtelematics.com

208
 209
3.19.8 Fuel Consumption Report

© 2008 MiX Telematics | Updated 2008/05/07

This report indicates fuel consumption figures that have been captured for vehicles matching the selection criteria. The following
columns are shown.

· Vehicle

· Date

· Odometer
The odometer reading that was captured.

· Consumption
The fuel consumption calculated from the captured details. The distance is calculated from the odometer readings of this and
the previous record and the consumption is calculated using this distance and the captured fuel quantity.

· Target
The target fuel consumption defined for the vehicle.

· % of target
The calculated consumption reflected as a percentage of the target consumption. Note that this percentage requires a certain
amount of interpretation. If consumption is shown as km/l or mpg then a percentage below 100 indicates that the vehicles
consumption is worse than the target. On the other hand, if the consumption is shown as l/100km then a percentage below 100
indicates that the vehicles consumption is better than the target.

Note: A number of Extensions are available with additional fuel related reports for example the Event Consumption Reports
Extension.

209
www.mixtelematics.com

209
 210
3.19.9 Performance Summary Report

© 2008 MiX Telematics | Updated 2008/05/07

This report prints a single line for each driver or vehicle matching the selection criteria. The following columns are displayed.

Driver
· Driving time
Shows the time spent driving in hours and minutes. The driving time is also shown as a percentage of trip duration.

· Idling time
Shows the time spent idling in hours and minutes. The idling time is also shown as a percentage of the trip duration.

· Standing time
Shows the time the vehicle spent standing* in hours and minutes. The standing time is also shown as a percentage of the trip
duration.

· Distance
Shows the distance travelled.

· Days with trips

Shows the number of days in the reporting period on which there are trips.

NOTE: Although idling time is shown as a percentage of trip duration, it cannot be reconciled with driving and standing times. Due
to the way that these times are recorded, the idling time overlaps both driving and standing times. However it is correct to say
that driving time + standing time = trip duration.

* Standing time is the time between the halt of a sub-trip and the departure of the next sub-trip.

210
www.mixtelematics.com

210
 211
3.19.10 Driving Errors Report

© 2008 MiX Telematics | Updated 2008/05/07

These reports reflect different summarisations of information on driving errors. Besides columns indicating the driver and period
to which the line applies, three columns appear for each of the following five key violations.

· Over speeding

· Over revving

· Harsh braking

· Harsh Acceleration

· Excessive idle

Each of these has the following columns.

· Count
Indicates how many times the violation occurred.

· Max
Indicates the maximum value recorded for the violation.

· Duration
Indicates the time period for which the violation was committed.

In addition there is a column showing the percentage of time during which the vehicle was being driven outside of the green
band.

211
www.mixtelematics.com

211
 212
3.19.11 Event Report

© 2008 MiX Telematics | Updated 2008/06/11

This report reflects events that occurred for drivers or vehicles matching the selection criteria. Events shown are restricted to
those that were selected from the reporting criteria wizard. Columns shown are.

· Event

· Event type
Indicates whether the event is a detail, summary or notification event.

· Begin

· End

· Duration

· Occurs
Indicates how many times a summary event occurred.

· Value
Indicates the value recorded for the event.

· Start odo

· End odo

· Distance

Note: A number of Extensions are available with additional event related reports for example the Event Summary Reports
Extension and the Event Consumption Reports Extension.

212
www.mixtelematics.com

212
 213
3.19.12 FM Terminal Report

© 2008 MiX Telematics | Updated 2008/05/07

The FM Terminal Report shows each menu event recorded by the FM Terminal, and each Vehicle depart and halt. The report is
sorted into Date and Time sequence.

The Criteria Wizard for the report can be used to select the required vehicles and a specific date period for the report.

213
www.mixtelematics.com

213
 214
3.19.13 Fleet Log Book Report

© 2008 MiX Telematics | Updated 2008/05/07

The Fleet Log Book Report summarises the data entered into the FM Terminal and recorded by the on-board computer, such as
Customer codes, Driving and Resting Reasons with the sub trips.

214
www.mixtelematics.com

214
 215

3.20 Fleet Manager Professional 9 Administrator

© 2008 MiX Telematics | Updated 2008/06/12

Overview
The Fleet Manager Professional Administrator Utility allows you to administer and maintain your Fleet Manager SQL Server
database. Functions exist to backup and restore the database, to import data from a legacy database and more.

This document covers the following topics:

· Running Fleet Manager Administrator

· Overview of FM Administrator Interface

· Data Access Mode

· Database Actions

· Server Options

· Backup Reminder

· Report Logo

Running Fleet Manager Administrator

The FM Administrator takes the form of a Windows Control Panel applet. To start it open the Control Panel by selecting it from
the Settings sub-menu of your Start menu.

Once the Control Panel is open, double-click on the FM Administrator icon to start the FM Administrator.

215
www.mixtelematics.com

215
 216

Overview of FM Administrator Interface

The FM Administrator consists of the following sections:

· Data Access Mode:

Select if the Connection should be to a Remote or a Local Database.

· Language Selector:
Use the language selector to change the language used by FM Administrator.

· Database Actions:
Double-click on the icons to activate the various database functions.

· Modify Button:
Click on the Modify button to change the selected server option.

216
www.mixtelematics.com

216
 217

· Server Options:
Double-click on an option you wish to change.

· Close Button:
Click on the Close button to close the FM Administrator.

Data Access Mode

You can configure the Fleet Manager software to connect to a SQL Server database located on the local network (Local Mode) or
to connect to a Fleet Manager Database located on a remote FM-Web server (Remote Mode).

Local Mode

When Local Mode is selected, double-click on the Connection icon on the Database Actions panel to open the Database
Connection Dialog. The Database Connection Dialog is also accessible by double clicking on SQL Server Computer or Database
Name properties within the Server Options (or by clicking Modify).

This dialog allows you to configure the connection to the database by specifying a server name, log on credentials and a
database name. Selecting Use Windows NT authentication allows you to be verified with the credentials you use to log in to your
Windows NT domain. If you select Use SQL Server authentication you must enter a valid user name and password for the SQL
Server you are connecting to.

Clicking OK will initiate an attempt to connect to the server and database you specified. If the database does not exist, the system
will ask if you wish to create it, and to specify the configuration language and disk file location for the database.

Remote Mode

When Remote Mode is selected, the Remote Connection dialog is displayed allowing you to enter the URL of the FM-Web
service, your user name and password.

This information can be obtained from the FM-Web service provider.

217
www.mixtelematics.com

217
 218

Downloaders
If the computer is being used as an FM-Web communications server, the downloader application (SMS Processor, GSM
Downloader, DECT Downloader or Wireless Internet Service (GPRS & WLAN)) must be configured to login to the FM-Web
service. Double-click on the Downloaders icon in Database Actions Panel to open the Downloaders Dialog.

Enter a default User Name and Password for the downloader applications on the computer.

This information can be obtained from the FM-Web service provider.

Database Actions
Backup Database

Double-click on the Backup icon in Database Actions Panel to open the Backup Database Dialog.

Name of Backup File

The upper field is used to specify a name for the backup file and will be pre-filled with a default file name derived from the current
date and time when the dialog opens. If you do not wish to use this default name you may type in a new name or click the Browse
button to open a standard file save dialog that will allow you to select the folder you wish to use and enter the file name to use.

In the case where the SQL Server is located on another computer, the path for the filename must be relative to the computer
running the SQL Server, not the computer where the FM Administrator is executed.

218
www.mixtelematics.com

218
 219

Backup Description

The lower field is used to enter a description for the backup. This field will also be pre-filled with a default value, which you may
change if you wish.

When you are satisfied with the values of these fields, click the OK button to start the backup.

Restoring a Database

Double-click on the Backup icon in Database Actions Panel to open the Restore Database Dialog.

The dialog has a single entry field that is used to enter the name of the backup file to be restored. As with the backup function,
the file name must be relative to the computer where the SQL Server is running.

Once you have selected a backup file it's description will be displayed in the read-only field at the bottom of the dialog. When you
are sure that the correct file is selected, click the OK button to start the restore.

Compacting a Database

Double-click on the Compact icon in Database Actions Panel to start Compacting the Database. It will immediately start a
compaction task to reduce the size of the database. Although no progress dialog is displayed, the mouse pointer changes to an
hourglass while the compact is in progress.

Deleting a Database

Double-click on the Delete icon in the Database Actions Panel.

A confirmation dialog will appear, asking you if you are sure that you would like to delete the database. Click yes, if you would like
to delete the database.

219
www.mixtelematics.com

219
 220

Importing a Database

Double-click on the Import icon in Database Actions Panel. Executing the Import action will open a standard file open dialog that
will allow you to navigate to and select the database you wish to import Drivers, Vehicles and Passengers from. The system will
allow data to be imported from Fleet Manager Lite databases.

NOTE: This function will not import a vehicle twice from the same database.

Loading Event Configuration

Double-click on the Load Event Configuration icon in Database Actions Panel. This function allows new Devices, Parameters and
Events to be loaded. These will normally be events specific to a third-party solution developed for the Fleet Manager system.

Server Options
SQL Server Computer

Indicates the network name of the computer from which the SQL Server database is accessed. The Modify button will perform the
Connection Database action.

Database Name

Indicates the name of the database that the FM Server will access. The Modify button will perform the Connection Database
action.

Backup Reminder

Indicates the number of days that must pass after a backup before reminders appear to perform a backup are displayed when
closing Fleet Manager Professional 9. You can change this value by double clicking on Backup Reminder within the Server
Options.

220
www.mixtelematics.com

220
 221

System Database File

Indicates the location of the Microsoft Access system database used during the import of databases.

Report Logo
Indicates the filename of the image file containing the logo to be used on reports. The default value is 0, which indicates that the
default image that is built into the report engine should be used. If you wish to use a custom logo, please take note of the
following guidelines.

When a custom image file is used for a report logo, the image is re-sized to fit on the report. The default logo has a size of
154×64 pixels and custom logos are resized to this according to these rules.

· Images smaller than the standard size are not re-sized.

· Images larger than the standard size are re-sized and their aspect ratio is preserved. This means that the height and width of
the image are shrunk so that it's largest dimension just fits within the standard size. So an image of 567×173 pixels would be
shrunk to 20×64 pixels and an image of 173×567 pixels would be shrunk to 154×47 pixels. You should therefore try to use a
logo that is as close as possible to the size of the default logo.

· Graphics files supported include:

bitmap (.bmp) files, icon (.ico) files, cursor (.cur) files, run-length encoded (.rle) files, metafile (.wmf) files, enhanced metafiles (.
emf), GIF (.gif) files, and JPEG (.jpg) files.

Message Folder
Indicates the folder where Event Notification e-mail messages generated by the SMS Processor and Wireless Internet Service
(GPRS & WLAN) should be stored. See Handset & E-Mail Notifications in the Fleet Manager System as well as SMTP Mail
Service for more information.

Notification Sender Address

Specifies the sender e-mail address to be used when Event Notification e-mail messages are generated.

221
www.mixtelematics.com

221
 222

3.21 Software Support

© 2008 MiX Telematics | Updated 2008/06/12

Overview
If you require software support, it can be obtained in the following ways:

· Support Channel
Contact your nearest Fleet Manager dealer for more information

· Online Knowledge Base

The Online Knowledge Base can be accessed via the MiX Telematics site (http://www.mixtelematics.com)

· Log a Service Request

In cases of extreme urgency a request for support may be logged directly with the development teams. This is done by
connecting to the support page of the Fleet Manager website and selecting the Log a Service Request link.

· World Wide Web

Search the MiX Telematics site (http://www.mixtelematics.com) for more information.

Also see Product Support.

General
When reporting problems experienced with our software, we need the following information:

1. Hardware specifications (CPU, RAM and open hard disk space), operating system and version (include service packs where
applicable).

2. The software and version of the software (version numbers are available on the Help-About menu).

3. Setup of software - stand-alone/client-server (and how it has been set up).

4. WHEN the error/problem occurred and FREQUENCY of occurrence (what you were trying to do when this happened, or what
changed on the computer that it doesn't work anymore).

5. If there are ANY error descriptions, always include the FULL error message (the best would be to send a screenshot of the
error(s)).

Installation
1. Before starting to install or upgrade, RESTART YOUR PC (this goes for core software as well as Extensions).

2. If installation fails the first time, try installing again.

3. If this fails, try installing from a different source (when installing from a CD, try another CD/CD-ROM - when installing from a
downloaded file, download the file again, and try installing again).

Data Downloading
When experiencing download problems:

Via Plug

1. Does this happen with only one plug? Have you tried another? Or a different download module?

2. Is the behaviour the same downloading into another/new database?

222
www.mixtelematics.com

222
 223

3. Generate a plug dump (using FMDealer), and send it to the responsible support person/dealer.

Via GSM/GPRS

1. Check the DlSchLog.txt file for a description of the problem, and check modem setup and drivers.

2. Is this error repeatable with a manual plug download?

3. Send the DlSchLog.txt file to the responsible dealer/support person.

Reporting
If there is a problem specific to a certain report, please include the following in an e-mail message to the responsible dealer/
support person:

· Saved criteria file (.cri file)

· Saved report (.pdf file)

Extensions
GPS Log Viewer or FM Map Set Extension South Africa

If you have trouble registering your GPS log viewer or FM Map Set, ensure that you have the correct unlocking code for the
version of GPS Log viewer or Map Set installed:

· The first GPS Log Viewer installs component FMGPS.dll (look for this component in your Fleet Manager install directory).

· FMPlus GPS Log Viewer installs component FMGPSCIS.dll (look for this component in your Fleet Manager install directory).

· They use different unlocking codes - check this if found that GPS unlocking code is not valid, or contact the responsible dealer/
support person.

223
www.mixtelematics.com

223
 224

4 Fleet Manager Extensions

© 2008 MiX Telematics | Updated 2008/05/07

Fleet Manager Extensions are software plug-in's that are designed to extend the functionality available from the Fleet Manager
Professional software. The extensions consist of additional reports and other functionality to support a variety of additional
business needs or country-specific requirements. The extensions are grouped into five categories listed below:

· Driver Performance

· Vehicle Performance

· Communication

· Mapping and Location Management

· Miscellaneous and Vertical Markets

Driver Performance
Fleet Manager Advanced Driver Scoring Extension

The Fleet Manager Advanced Driver Scoring Extension is an enhanced version of the Driver Scoring Report available in the Fleet
Manager Professional software. It allows driver score calculations to be based on the occurrence of user-defined events. Two
reports are provided; a simple report and an advanced report. The simple report allows scores to be calculated using a points
addition or deduction algorithm, and the advanced report uses scoring graphs which calculate scores using the duration and
severity of the event occurrences.

Fleet Manager Taxlog Extension

The Fleet Manager Taxlog Extension produces trip reports summarizing business, private and other vehicle usage, ideal for
claiming tax rebates on business mileage.

Product Specific: Requires the FM Keypad

Fleet Manager Australian Driving Hours Exception Extension

The Fleet Manager Australian Driving Hours Exception Extension is a specialised extension designed to report on driver
compliance with the Australian Road Traffic Legislation of 1999. This extension requires a registration code. Please contact
Siemens Australia for more information regarding the purchase of this extension.

Country Specific: Designed to comply with Australian legislation.

Fleet Manager TCO Driver Data Extension

The Fleet Manager TCO Driver Data Extension is designed for markets where the tachograph is legislated. The reports provide a
summary of TCO driving, resting, active work and passive work information and allows you to export data in a standard or user-
defined format.

Product Specific: Requires the FM TCO Interface

Fleet Manager Exploration and Production Safety Extension

The Fleet Manager Exploration and Production Safety Extension extends the Fleet Manager Software by including driver
certification, licensing and profile functionality to record, manage and report on a driver’s certification and safety profile. It also
includes additional driver scoring reporting enhancements and new reports.

Specific to the Exploration and Production market.

224
www.mixtelematics.com

224
 225

Vehicle Performance
Fleet Manager Timeline Extension

The Fleet Manager Timeline Extension provides two additional reports to the Fleet Manager Professional Client, combining
graphical and factual information.

Fleet Manager Event Consumption Reports Extension

The Fleet Manager Event-Consumption Report Extension reports on fuel consumption during event occurrences.

Product Specific: Requires a fuel measuring device such as the EDM.

Fleet Manager Costing Extension

The Fleet Manager Costing Extension provides functionality to capture and report on fleet operating costs. It is multi-currency
capable, and takes into account manually entered transactions as well as fuel costs, oil costs and other transactions captured
using the FM Terminal.

Pre-requisite: Requires the Fleet Manager System Tools 1 Extension.

Communications
Fleet Manager Comms Scheduler Extension

The Fleet Manager Comms Scheduler Extension enables you to create and maintain schedule entries that define when and how
often data is to be transferred to and from vehicles equipped with remote data transfer devices such as GSM modems.

Product Specific: Requires a remote communications device such as a GSM modem.

Fleet Manager Active Tracking and Messaging Extension

The Fleet Manager system includes a set of powerful features known as Active Events, Active Tracking and Messaging. These
features make use of the various communication technologies like GSM Short Message Service (SMS), GSM circuit-switched
data (CSD), GPRS, etc. to deliver real-time fleet management information to the fleet manager’s desktop and to send and receive
free-text and job messages. The Fleet Manager Active Tracking and Messaging Extension provides functionality to manage
communicate with vehicles and track them in real-time.

Mapping and Location Management

Fleet Manager Location Reports Extension

The Fleet Manager Location Reports Extension reports on how much time is spent by your vehicles and drivers at different
locations. You can filter reports based on different types of locations (e.g. customers, no-go zones, base, etc.) to get a better
understanding of your where your vehicles and drivers spend their time.

Pre-requisite: Requires a GPS receiver and the Fleet Manager System Tools 1 Extension.

Fleet Manager GPS Log Viewer for MapPoint Extension

The Fleet Manager GPS Log Viewer for MapPoint Extension integrates with Microsoft MapPoint 2002 or later to display digital
maps for active tracking, passive tracking and other functions that require mapping.

Pre-requisite: Microsoft MapPoint 2002 or later.

Fleet Manager GPS Log Viewer Extension

The Fleet Manager GPS Log Viewer Extension is used to display digital maps for active tracking, passive tracking and other
functions that require mapping. Versions are available for:

225
www.mixtelematics.com

225
 226

· Africa

· Australia

· Chile

· South Africa

· Taiwan

Please note: The GPS Log Viewer Extensions are not included on the Fleet Manager Office CD and must be purchased
separately. For more information, please visit the Fleet Manager website http://www.fm-web.co.za.

Miscellaneous and Vertical Markets

FM Dealer Utility

The Fleet Manager Dealer Utility provides functionality required by the dealer/installer of Fleet Manager on-board computers,
including functionality for initialising code-plugs and uploading device drivers (firmware) to FM200 and above series on-board
computers and the FM Terminal.

Fleet Manager System Tools 1 Extension

The Fleet Manager System Tools 1 Extension provides functionality to maintain currency, location and contact information
required by other extensions.

Fleet Manager Vehicle Maintenance Extension

The Fleet Manager Vehicle Maintenance Extension includes additional reports to report on vehicle service history, road
worthiness and licensing information.

Fleet Manager Event Summary Reports Extension

The Fleet Manager Event Summary Reports Extension provides a suite of reports that can be used to analyse event information
recorded by the Fleet Manager on-board computers. This report is especially useful for reporting on user-defined events.

Fleet Manager Export Extension

The Fleet Manager Export Extension allows you to export data from the Fleet Manager database in user-defined formats, suitable
for importing into other applications.

Fleet Manager Trailer Management Extension

The Fleet Manager Trailer Management Extension provides functionality to maintain trailer records, including servicing
information. Two reports are available to report on trailer utilization.

Product Specific: Requires the FM Trailer ID

Fleet Manager Passenger Extension

The Fleet Manager Passenger Extension reports on passenger information gathered by the FM200 and above series on-board
computers when black passenger code-plugs are used.

Product Specific: Requires the use of passenger code-plugs

Fleet Manager Exploration and Production Safety Extension

Most Exploration and Production companies have stringent global QHSE driving policies and standards. As such, many
companies require that their vehicles be fitted with approved vehicle monitors, and drivers are required to have appropriate

226
www.mixtelematics.com

226
 227

certification before being allowed to drive a vehicle.

The Fleet Manager Exploration and Production Safety Extension extends the Fleet Manager Software by including driver
certification, licensing and profile functionality to record, manage and report on drivers' certification and safety profiles.

Specific to the Exploration and Production market.

Fleet Manager Snow Plough Extension

The Fleet Manager Snow Plough Extension is a specialised extension which allows you to manage snow ploughing activities
more efficiently and effectively. The extension can report on the distance that a snow plough travelled, the time spent within a
user-defined location and the area ploughed. The Snow Plough Extension will allow you to generate two specialised location
utilisation reports.

Product Specific: Requires a GPS receiver

Fleet Manager Materials Handling Extension

The Fleet Manager Materials Handling Extension is used in conjunction with the FM Impact Sensor to generate reports reflecting
the daily use of equipment, and includes Utilisation, Event, Collision and Timeline Reports and Graphs, as well as a tool to plan
shifts for operators and equipment and report on the utilisation per shift.

Product Specific: Requires FM Impact Sensor.

227
www.mixtelematics.com

227
 228

4.1 Fleet Manager Active Tracking and Messaging Extension

© 2008 MiX Telematics | Updated 2008/07/04

Overview of document
This document describes how to use the features of the Fleet Manager Active Tracking and Messaging Extension, and covers the
following topics:

· Introduction to Active Tracking and Messaging Extension

· Installing and Loading the Extension

· Functions

Menus and Dialogs

· Options Dialog

· Manage Job Window

· Add new Job Window

· Edit Job Menu

· Send Free Text Message

· SMS to Mobile

· Active Tracking and Messaging

· Active Vehicles Window

· Polling for new Messages

· Message List Features

Introduction to Active Tracking and Messaging Extension

The Fleet Manager Professional release includes a set of powerful features known as Active Events, Active Tracking and
Messaging. These features make use of the various communication technologies like GSM Short Message Service (SMS), GSM
Data Call, GPRS, etc. to deliver real-time fleet management information to the fleet manager's desktop and to send and receive
free-text and job messages. The Fleet Manager Active Tracking and Messaging Extension is designed to display and manage
this real-time information by enabling you to:

· Define your own preferences for receiving and displaying incoming messages.

· Manage message data in the Fleet Manager database.

· Select which vehicles you would like to monitor.

· Put vehicles into tracking mode for a specified time period.

· Track vehicle movement on a map in real-time, using any of the new GPS Log Viewer or FM Map Set Extensions.

· Request the current status and position of a vehicle.

· View a list of incoming messages for selected vehicles.

228
www.mixtelematics.com

228
 229

· Receive pop-up notifications of selected incoming messages.

· Create new job messages with multiple location addresses.

· Manage and send job messages or job lists.

· Track job status in real-time.

· Send free-text messages with predefined driver response options.

· Send SMS messages to predefined GSM mobile phones.

· And much more .

Installing and Loading the Extension

To install the extension, run the Fleet Manager Professional installation program and select the Active Tracking & Messaging item
under the Fleet Manager Extensions section (Custom setup). It is advisable not to have the Fleet Manager Client application open
whilst installing.

Once installed, the extension will be loaded automatically. To change this, open the Extension Manager from the Tools menu,
and uncheck the Active Tracking and Messaging item:

The Extension Functions

The Fleet Manager Active Tracking and Messaging Extension has 4 main functions:

1. Job Message Management

2. Free-Text Message Definition

3. Active Tracking

4. Active Event and Message Display

229
www.mixtelematics.com

229
 230

Overview

Job Message Management is handled by the Manage Jobs dialog. Free-Text Messages are defined and sent from the Send
Free-Text Message dialog. All incoming and outgoing Active Messages are displayed in the Active Messages window. The Active
Vehicles dialog lists actively tracked and managed vehicles. The extension's Options dialog defines preferences for creating,
managing and viewing messages. These windows and their functions are described in more detail later in this document.

In addition, the Extension integrates with Active Tracking-capable GPS Log Viewer or FM Map Set Extensions to display vehicle
information in one or more map windows. Please consult theFleet Manager GPS Log Viewer for MapPoint Extension and Fleet
Manager GPS Log Viewer Extension documentation for more information.

The Extension windows can be arranged on screen in any layout which is appealing to the operator. For active tracking the
recommended layout is to have the Active Vehicles List on the left hand side of the screen, the Active Message List at the bottom
of the screen and the map viewer window/s occupying the remaining screen space.

Menu and Toolbar

Menu
Active Tracking and Messaging
The main functions of the Fleet Manager Active Tracking and Messaging
Extension can be accessed from Menu > Tools. The tracking of and messaging to/from vehicles.

More information on active tracking and

messaging

Manage Jobs

All job message functions of the Active Tracking

and Messaging extension can be accessed from
the Manage Jobs window. These include
viewing, adding, editing and deleting job
messages, importing and exporting job lists, as

230
www.mixtelematics.com

230
 231

well as managing job message status and

ordering and sending job lists.

More information on managing jobs

New Job Message

New jobs can be created using the Add New

Job window.

More information on adding a New Job

Send Free-Text Message

Use the Send Free-Text Message window to

send a free-text message to a vehicle.

More information on sending a Free-Text

Message

SMS Message to Mobile

This function is used to send free-text messages

to a contact's mobile phone number via SMS.
Contacts are defined using the System Tools 1
extension (see Fleet Manager System Tools 1
user documentation for details). The dialog list
all contacts with a valid mobile phone number in
the Recipients combo box. Predefined
messages can be selected, or a new message
can be entered into the Subject and Body fields.

More information on SMS Message to Mobile

Tool bar
Active Tracking and Messaging
The main functions can also be accessed from the Tool bar in the Fleet
Manager Professional Client Software. These icons are added during the
installation of the extension and does not have to added at a later stage. Manage Job Messages

Add a Job Message

Send a free text Message

SMS Message to Mobile

Dialogs
The Options Dialog

The Options dialog allows you to manage the way in which messages are sent, received and displayed, to select which GPS Log
Viewer or FM Map Set to use for tracking and to manage message data in your Fleet Manager database.

231
www.mixtelematics.com

231
 232

It can be accessed by:

· Selecting the 'Active Tracking and Messaging' item on the Extensions tab of the Fleet Manager Client application's Options
dialog

232
www.mixtelematics.com

232
 233

· Or, by clicking the Options menu item under the Tools menu of the Active Vehicles window

· Or, by clicking the Options tool button on the Active Vehicles window.

· Or, by clicking the Options button on the Active Messages window.

The Options dialog includes the following options:

Filters

These options determine which new messages to display in the Active Messages window. You can choose to either see all
messages to and from the vehicles listed in the Active Vehicles list, or to filter and display only messages relevant to your
immediate requirements.

Display

Use the New Messages option to specify how often to check for new Active messages. Because of the nature of SMS messages,
it is not necessary to set this value too low - doing so might slow the extension down and reduce usability. Checking for new
messages every 60 seconds is usually adequate.

You can specify whether or not to display pop-up message dialogs (called Notification Dialogs) when new messages arrive, for all
messages or only for urgent messages. If you select to see notification dialogs for all or urgent messages, you can choose to
exclude tracking messages. Tracking messages will still be received and displayed in the Messages list and on open map
viewers, but no notification dialogs will be displayed for them.

You can elect to play a warning sound when active event notification pop-ups are displayed. Note that the PC must be set up to
play audible sounds. The specified FMWarning.wav file can be changed to suit the user's requirements. Some .WAV files are
installed by the extension and these or any other .WAV file can be used to replace the FMWarning.wav file in the installed
directory.

Active Vehicle Options define how vehicle status properties are displayed in the Active Vehicles dialog. See Active Vehicle
Properties.

Tracking
The Vehicle Tracking option allows you to specify the default parameters to use when initiating Active Tracking. These default
settings can be overridden when using the Initiate Tracking function (described in more detail later in this document).

Use the Active Map Display option to specify which GPS Log Viewer Extension to use for displaying tracking points and
messages on a map.

If no Log Viewers are available in the combo box, install the latest active tracking-enabled Log Viewer extension. You can also
specify whether or not to use the Log Viewers' advanced options to filter out inaccurate GPS points, as well as define how these
Log Viewer windows behave when used with the Active Vehicles window.

233
www.mixtelematics.com

233
 234

· Free-Text

Standard Message Responses are defined in the Options dialog and will appear on the Standard Responses tab of the Send
Free-Text Message dialog. These are attached to the message before sending it to the vehicle. When replying to a Free-Text
message, the driver can select one of the Standard Responses, or choose to type his own response.

Notification Options define whether or not the vehicle should generate a notification message to notify the office when the state of
a Free-Text message changes. Notification Options selected in the Options dialog will be checked by default on the Options tab
of the Send Free-Text Message dialog. The selection can be changed before the message is sent.

· Predefined

Predefined Messages specified in the Options dialog are templates that appear in the Select Predefined Message drop down box
on the Send Free-Text Message and Add New Job dialogs.

When a Predefined Message is selected from the list, the free-text or job message description and detail fields are filled with the
corresponding Predefined Message text, and the corresponding Default Standard Responses are selected (Free-Text only).

· Jobs

Job Options define the default options that apply when a new job is created using the Add New Job dialog. Except for the Unique
Job Number option, these can be changed on the Add New Job dialog prior to sending the job.

Job Notification Options are similar to those of Free-Text messages described above. Notification Options selected in the Options
dialog will be checked by default on the Options tab of the Add New Job dialog. The selection can be changed before the job is
sent.

· Advanced

Active Event and Tracking Message Maintenance options are used to manage the message data contained in the Fleet Manager
database. Select one of the three options, based on the number of vehicles in your system, the number of messages generated

234
www.mixtelematics.com

234
 235

by the vehicles and your unique data storage requirements.

The Active Tracking and Messaging Extension provides a function to increment a unit's daily SMS limit, and to change the status
of a job on the FM system. These functions are described in more detail later in this document. You can password protect these
functions by setting any non-blank password in the Security section of the Options dialog. If you do not wish to password protect
these functions, enter a blank password. To enter a blank password, make sure that the New Password and Confirm Password
fields are empty.

Warning: Do not forget your password.

Note: Filter, Display, Tracking and Password Security options are specific to the local computer only and will not affect other
computers running the Extension.

Manage Jobs Window

All job message functions of the Active Tracking and Messaging extension can be accessed from the Manage Jobs window.
These include viewing, adding, editing and deleting job messages, importing and exporting job lists, as well as managing job
message status and ordering and sending job lists.

The Manage Jobs window can be accessed by:

· Selecting the Manage Jobs item under the Tools menu of the Main Window

· Or by clicking the Manage Jobs tool button on the Extension toolbar of the Fleet Manager Client application's Main Window

· Or from the right click menu of a vehicle configured to receive and display messages

· Or from the right-click or Vehicles menu for a selected vehicle in the Active Vehicles list.

235
www.mixtelematics.com

235
 236

The Manage Jobs window includes the following functions:

· Display Job Messages

The Manage Jobs window lists job messages based on the filter setting defined in the Message Display Filters section. When the
window is accessed from the right-click menu of a vehicle in the Main window or Active Vehicles list, the list is filtered to display
jobs assigned to the selected vehicle or vehicles only.

· Add and Edit

The Manage Jobs window allows adding and editing of new job messages through the Add New Job dialog, described in more
detail later in this document. To access the Add New Job dialog from the Manage Jobs window, click the Add button or right-click
in the list and select Add from the context menu.

· Delete

To delete a job, click the Delete button or right-click on the job and select Delete from the context menu. More than one job can
be deleted at a time by selecting multiple jobs in the list. The job is not physically deleted from the system. Instead the status of
the job will be changed to deleted and it will still appear in the Manage Jobs and Active Messages lists. If the job has been sent
previously, a notification message will be generated and automatically sent to inform the vehicle that the job was deleted.

· Send

To send a job, click the Send button or right-click on the job and select Send from the context menu. When sending multiple jobs,
you have the option of defining a job order list in the Order Jobs dialog. Note that only jobs with a 'New' status can be ordered or
sent.

· Re-Send

Jobs are re-sent by copying the details from an existing job and using these to create a new job message. To access the Re-
Send Job dialog from the Manage Jobs window, click the Re-Send button or right-click on a job in the list and select Re-Send
from the context menu.

· Status

To change the status of a job, click the Status button or right-click on the job and select Status from the context menu. The status
can be changed for more than one job at a time by selecting multiple jobs in the list.

· Import and Export Job Lists

To import a list of new job messages contained in a special format text file (Comma Separated Values - .CSV), click the Import
button and load the file. To export a list of all jobs displayed in the Manage Jobs window, click the Export button. Use an exported
job list file as a template for importing new job messages.

NOTE: When importing job lists, the AddressList column must contain valid Location ID values. These can be obtained by
exporting a Location list (please refer to the System Tools 1 user documentation for more detail on exporting Location lists).

236
www.mixtelematics.com

236
 237

· Refresh

To refresh the job message list and retrieve the latest status information for all displayed jobs, click the Refresh button.

· Message Display Filters

To filter the job messages displayed in the Manage Jobs list, select the filter criteria from the fields provided, and then click the
Filter button. To turn off filtering, press the Filter button again.

Add New Job Window

New jobs can be created using the Add New Job window.

The Add New/Edit Job Window can be accessed:

· From the right click menu of a vehicle configured to receive and display messages

· From the right-click or Vehicles menu for a selected vehicle in the Active Vehicles list.

Options

The Add New Job window includes the following fields:

237
www.mixtelematics.com

237
 238

· Job Details

Select the vehicle to which the job is assigned in the vehicle drop down list. Note that only vehicles fitted with a display device like
the Dayton PC 5XXX Pro navigation system or FM Terminal can be selected. For more information on enabling vehicles for
remote messaging and message display, please refer to the Fleet Manager Professional user documentation.

Select a predefined message from the Predefined Message drop down box, or type a new job description and message detail into
the fields provided. If the 'Job numbers must be unique' option is checked (Job Options on the Jobs tab of the Options dialog), a
unique job number or description must be entered into the Unique Job Number / Description field.

The maximum characters allowed for Job Description and Detail depend on the display device connected to the selected vehicle,
as well as whether or not an address abbreviation will be added to the Job Description text:

Maximum number of characters

Display Device Job Description Job Description (With Address Job Detail
Summary)

Dayton PC 5XXX Pro 38 19 1000

FM Terminal 20 Option Not Available 120

· Addresses

Assign up to 9 addresses to a job by adding them from the Select Location or Select Route window. Please refer to the Fleet
Manager System Tools 1 Extension user documentation for more detail on Locations and Routes. Sequence the addresses using
the Move Up and Move Down buttons.

Text entered into the Find box is used to filter the Locations or Routes lists by Description or Zip/Postal code. If only one Location
or Route matches the filter text, it is added automatically. If more than one matching Location or Route is found, the filtered list is
displayed. If no Location or Route match the filter text, the Add New Location / Route dialog is opened automatically, allowing the
user to add the required item.

NOTE: The same rule applies when adding addresses to a job, whether they are added from the Locations list or built from
selected Routes. There can be a maximum of 9 unique location addresses per job.

If you do not wish to assign an Address to a Job, the 'Job must have at least one destination address' option must be un-
checked.

To add a short description of the first or last address to the Job Description text, select 'Append an address summary to the Job
description' option. This will add abbreviated city and street data for the selected address to the last part of the job description
(see table above).

· Options

Select automatic notification and job validity period from the Options tab. To send the message immediately, select the 'This is an
urgent job' option. Select the preferred transport mechanism from the drop down box provided, or leave the option on <Default .>
to use the default transport for the selected vehicle/s (see the Default Message Transport setting on the Transports tab of the
vehicle's GSM device properties dialog).

· Status

When adding a new job, no status history is available. When editing a job message, a complete status history is displayed. To
change the status of a job message in the Fleet Manager database, click the Change Job Status button. The new status,
displayed on the Job Detail and Status tabs, will only be saved when the edited job message is saved by clicking the Save
button.

To send the new job immediately, click the Send button. To save the job without sending it, click the Save button.

238
www.mixtelematics.com

238
 239

Edit Job Window

Existing jobs can be edited using the Edit Job window. Job details can only be changed for job messages that have not been sent
to a vehicle previously (i.e. job messages with a 'New' status). For all other job messages, the fields in the Edit Jobs window will
be disabled. For jobs that do not have a 'New' status, only the Change Job Status function is enabled. Note that the vehicle will
not be notified of a status change to a job that has previously been sent to it.

Send Free-Text Message Window

Use the Send Free-Text Message window to send a free-text message to a vehicle.

The window Send a Free-Text Message can be accessed by:

· Selecting the Send Free-Text Message item under the Tools menu of the Main Window

· Clicking the Send Free-Text Message tool button on the Extension toolbar of the Fleet Manager Client application's Main
Window

· From the right click menu of a vehicle configured to receive and display messages

· Or from the right-click or Vehicles menu for a selected vehicle in the Active Vehicles list.

Options

The Send Free-Text Message window includes the following fields:

· Message Details

Select the vehicle to which the message should be sent from the vehicle drop down list. Note that only vehicles enabled for SMS
messaging and fitted with a Dayton PC 5XXX Pro navigation system or FM Terminal, can be selected.

· Standard Responses

239
www.mixtelematics.com

239
 240

Select up to 5 Standard Responses from the list. The driver will be able to select one of these when replying to the message, or
he can type a new response.

· Options

Select an automatic notification and message expiry date from the Options tab. To send the message immediately, select the
'This is an urgent message' option. Select the preferred transport mechanism from the drop down box provided, or leave the
option on <Default .> to use the default transport for the selected vehicle/s (see the Default Message Transport setting on the
Transports tab of the vehicle's GSM device properties dialog).

To send the new free-text message, click the Send button.

SMS Message to Mobile

This function is used to send free-text messages to a contact's mobile phone number via SMS. Contacts are defined using the
System Tools 1 extension (see Fleet Manager System Tools 1user documentation for details). The dialog lists all contacts with a
valid mobile phone number in the Recipients combo box. Predefined messages can be selected, or a new message can be
entered into the Subject and Body fields.

The SMS Message to Mobile window can be accessed by:

· Selecting the SMS Message to Mobile item under the Tools menu of the Main Window

· by clicking the SMS Message to Mobile tool button on the Extension toolbar of the Fleet Manager Client application's Main
Window

To send the new free-text message, click the Send button.

Active Tracking and Messaging

The Active Vehicles Window

The Active Vehicles window is the core, controlling window of the Active Tracking and Active Message Display functionality and
must be loaded before the Active Message List window can be displayed. All of the Extension's functionality, as well as some of

240
www.mixtelematics.com

240
 241

the System Tools extension functions, are accessible from this window.

The Active Vehicles window can be accessed by:

· Selecting the 'Active Tracking and Messaging' item under the Tools menu of the Main Window

· clicking the 'Active Tracking and Messaging' tool button on the Extension toolbar of the Fleet Manager Client application's Main
Window

The Active Vehicles window includes the following functions:

· Display Active Messages

The Active Message List window is displayed automatically the first time the Active Vehicles window is opened. After closing the
Active Message List window, you can re-open it by selecting the Show Message List menu item under the Tools menu of the
Active Vehicles window.

· Active Vehicle Properties

The Active Vehicles window includes a detail section where vehicle mode, connection and position information are displayed.

The mode section indicates the vehicle's active tracking and messaging capabilities. These are dependant on the vehicle's device
configuration. The top status block indicates the accuracy of the most recent GPS position - green indicating an accurate reading,
and red indicating that the current position may not be accurate. The lower status block indicates the GPRS connection status -
green indicating that a GPRS status was received less than x minutes ago and red indicating a possible delay in GPRS
communications. The value of x is configurable in the Options dialog.

The Nearest Active Location box shows the distance and heading from the nearest location listed in the Active Locations list. If a
Log Viewer is selected in the Options dialog, and the vehicle is near a valid street address, the Nearest Address box will indicate
that address.

In the vehicle list, the Last GPS Point column indicates the date of the most recent GPS point received from the vehicle. The At
Location column shows Active Location names when a vehicle enters any of the locations listed on the Active Locations tab.

Multi-Select Functions
The Active Vehicles window allows most functions to be performed on multiple vehicles. By holding down the Shift key, multiple
vehicles can be selected in the list. This is useful for sending the same free-text message to more than one vehicle
(broadcasting), or to enable tracking for multiple vehicles.

241
www.mixtelematics.com

241
 242

NOTE: If at least one of the multi-selected vehicles is enabled for a specific function, the menu and tool button items for that
function are enabled in the Active Vehicle dialog. The action is only performed on these enabled vehicles and not on all selected
vehicles. A confirmation dialog will indicate which vehicles apply to the selected action:

· Add Vehicle

To add a vehicle to the Active Vehicles list, select the Add Vehicle menu item from the Vehicles menu, or right-click in the list of
vehicles and select Add Vehicle from the menu, or click the Add Vehicle tool button on the Active Vehicles toolbar:

The Select Vehicle dialog only lists vehicles properly configured for active tracking and/or messaging:

242
www.mixtelematics.com

242
 243

· Remove Vehicle

When a vehicle is removed from the Active Vehicles list, any messages sent to or received from that vehicle will also be removed
form the Active Messages list.

To remove a vehicle from the Active Vehicles list, select the Remove Vehicle menu item from the Vehicles menu, right-click in the
list of vehicles and select Remove Vehicle from the menu, or click the Remove Vehicle tool button on the Active Vehicles toolbar:

· Request Current Position

Use this function to send an urgent message to the vehicle's FM200 unit, requesting the vehicle's current status and position.
The vehicle will reply by sending a high priority tracking message, which will be displayed in the Active Messages window.

You can access this function by selecting the Request Current Position menu item from the Vehicles menu, by right-clicking on a
vehicle in the list and selecting the Request Current Position menu, or by clicking the Request Current Position tool button on the

Active Vehicles toolbar:

The Send Options dialog will be displayed. Select the preferred transport mechanism for sending the position request from the
drop down box provided, or leave the option on <Default > to use the default transport for the selected vehicle/s (see the Default
Command Transport setting on the Transports tab of the vehicle's GSM device properties dialog).

243
www.mixtelematics.com

243
 244

· Initiate Tracking

Use this function to send a high priority message to the vehicle's FM200 unit, instructing it to enter tracking mode with the
specified parameters. The vehicle will send back tracking messages for the specified duration at the specified time interval.

To put a vehicle into tracking mode, either select the Initiate Tracking menu item from the Vehicles menu, right-click on the
vehicle in the list and select Initiate Tracking from the menu, or click the Initiate Tracking tool button on the Active Vehicles

toolbar:

The Initiate Tracking dialog will be displayed with default frequency and duration as specified in the Options dialog. You can
override these default values as required. Select the preferred transport mechanism for sending the tracking request from the
drop down box provided, or leave the option on <Default .> to use the default transport for the selected vehicle/s (see the Default
Command Transport setting on the Transports tab of the vehicle's GSM device properties dialog).

After sending the Initiate Tracking request, if the vehicle is not already assigned to an open map viewer, you can choose to add it
to a new or existing viewer (provided you have a viewer capable of Active Tracking installed and selected in the Options dialog).

If you wish to add the vehicle to a map viewer window, click Yes.

244
www.mixtelematics.com

244
 245

You can choose to add the vehicle to a new map viewer window or to an existing viewer window if there is one open. This
enables you to view multiple vehicles on the same map, or split them across different maps if necessary. It is also possible to
view the same vehicle/s on multiple maps. For example, you may wish to have two map viewer windows open, both displaying the
same vehicles, but at different zoom levels.

You can also specify how many points to plot on the map viewer window/s. The <n> most recent GPS data records for the vehicle
will be retrieved from the Fleet Manager database and plotted on the map/s (where <n> is the specified number of points).

Note: The latest GPS points are retrieved from the database and can include both Active Message points and GPS log points
(downloaded from the vehicle).

These vehicle points will be updated on the map/s automatically, whenever the Active Messages window is refreshed and new
GPS locations were received from the displayed vehicles. Vehicles that are being tracked are indicated by " Tracking..." in
the Mode column of the Active Vehicle list.

· Stop Tracking

Use this function to send an urgent message to the vehicle's FM200 unit, instructing it to stop sending tracking messages. You
can do this by selecting the Stop Tracking menu item from the Vehicles menu or by right-clicking on a vehicle in the list and
selecting the Stop Tracking item the menu.

Select the preferred transport mechanism for sending the Stop Tracking request from the drop down box provided, or leave the
option on <Default .> to use the default transport for the selected vehicle/s (see the Default Command Transport setting on the
Transports tab of the vehicle's GSM device properties dialog).

Note that the "Tracking." text in the Mode column will only be removed once a Final Tracking Message is received from the
vehicle.

· Centre On Map

This function adds the selected vehicle to a map viewer window (if it has not already been assigned to an open map viewer
window), plots the last specified number of GPS points on the map and centres the map on the most recent point available for the
vehicle.

The map will be automatically updated whenever new tracking messages are received for the vehicle and the Active Messages

245
www.mixtelematics.com

245
 246

window is refreshed.

To use this function, select the Centre On Map menu item from the Vehicles menu, right-click on a vehicle in the list and select

Centre On Map from the menu, or click the Centre On Map tool button on the Active Vehicles toolbar:

· Plot Trail on Map

This function is identical to the Centre on Map function, but does not pan the map viewer.

To use this function, either select the Plot Trail on Map menu item from the Vehicles menu or right-click on a vehicle and select
Plot Trail on Map from the menu.

· Messages

For Messenger or Navigator vehicles equipped with a display device like a Dayton PC XXXX Pro navigation system or an FM
Terminal, Job or Free-Text Messages can be sent directly from the Active Vehicles dialog. Simply select the Manage Jobs, New
Job Message or Send Free Text Message sub-menu items from the Messages item under the Vehicles or right-click menu. This
will open the Manage Jobs, Add New Job or New Free-Text Message windows respectively, with the corresponding vehicle(s)
pre-selected.

· Show Last Trip

This function plots the vehicle's last trip, including any GPS points received after the last trip's download, on a new (passive) Log
Viewer map.

· Distance to Locations

This function opens a list showing all distances and headings from the locations listed in the Active Locations list to the selected
vehicle.

· Change Tracking Icon

For some GPS Log Viewers and FM Map Sets, the icon used to display vehicles on the map can be specified per vehicle. To
change the icon colour for a vehicle, either select the Change Tracking Icon menu item from the Vehicles menu or right-click on a
vehicle and select Change Tracking Icon from the menu. This opens the Icon Colour dialog.

· Increase Daily SMS Limit

FM200 and above units have the ability to limit the number of SMS messages sent by the unit per day. This is a powerful feature
designed to assist with the management of communications costs. This limit is specified in the SMS tab of the GSM Modem
device for the vehicle.

When a vehicle has reached its maximum daily SMS limit, it will not send any more tracking or event messages. Messages
generated by the unit after the limit is reached are buffered in the unit's memory and sent the following day.

246
www.mixtelematics.com

246
 247

You can increase the daily SMS limit for a vehicle should the need arise. To do so, either select the Increase Daily SMS Limit
menu item from the Vehicles menu or right-click on a vehicle and select Increase Daily SMS Limit from the menu. If the function
is password protected, you will be prompted to enter the Daily SMS Limit password prior to proceeding. After successfully
entering the password, you can specify how many additional SMS messages should be sent by the unit today. Select the
preferred transport mechanism for sending the Limit Increase request from the drop down box provided, or leave the option as
<Default.> to use the default transport for the selected vehicle/s (see the Default Command Transport setting on the Transports
tab of the vehicle's GSM device properties dialog).

An urgent message is sent to the vehicle's unit, instructing it to increase its SMS limit for the current day.

Note: Increasing the vehicle's daily SMS limit applies only to the current day. The unit will revert to the daily SMS limit that was
programmed into it the following day. If you wish to permanently increase the vehicle's daily SMS limit, you must change the
setting in the Vehicle Properties dialog and re-upload the event configuration to the unit.

· Clear Message Buffer

This function sends an urgent message to the vehicle's unit, instructing it to delete all unsent SMS messages buffered in the
unit's memory.

This function should only be used to prevent unwanted pending messages from being sent by the vehicle. For example, if you
upload an event configuration to the unit which causes the unit to generate excessive SMS messages, the unit will send
messages until its daily SMS limit is reached, thereafter it will begin buffering them in its memory to be sent the following day. If
you realize that too many messages are being generated, you can correct the problem in the unit's event configuration, re-upload
the configuration and use this function to instruct the unit to delete the unwanted buffered messages. Note that vehicle events
from these SMS messages may have been generated. These will not be deleted, and will still be downloaded in the normal
manner.

To access the function, either select the Clear Message Buffer menu item from the Vehicles menu or right-click on a vehicle and
select Clear Message Buffer from the menu. Select the preferred transport mechanism for sending the Clear Message Buffer
request from the drop down box provided, or leave the option as <Default.> to use the default transport for the selected vehicle/s
(see the Default Command Transport setting on the Transports tab of the vehicle's GSM device properties dialog).

· Request C-IQ Navi ID & Send C-IQ Access Key

For vehicles configured with a VDO Dayton device (with CIQ activated on the Navigation tab of the vehicle's Dayton device
properties tab), the CIQ functions are enabled in the Active Vehicles list. This allows you to send a request for a CIQ Navi ID to
the vehicle:

247
www.mixtelematics.com

247
 248

The vehicle will reply by sending back the Navi ID in a free-text message. This Navi ID is required for obtaining a valid CIQ
Access Key. This can then be sent to the vehicle to unlock the Dayton device:

· Active Locations

Locations added to the list on the Active Locations tab are used to monitor active vehicle positions in relation to user-defined

248
www.mixtelematics.com

248
 249

locations in the FM system. With the corresponding options selected on the Display tab of the Options dialog, the user can
receive Notifications whenever an (active) vehicle enters any of the Active Locations. Nearest (active) vehicle information is also
displayed in the Current Status section at the bottom of the Active Locations list. A list of distances and directions from the
nearest active vehicles can be accessed via the Locations menu or by right-clicking on a location in the list. From the same menu
or right-click, it is possible to centre Active Map displays on the selected Location.

· Tile Windows

Use this function to resize the Active Vehicles and Active Messages dialogs to their default startup positions and display all open
map viewers. Select the Tile Windows menu item from the Tools menu.

· Save Window Layout

To save the current window layout of the Active Vehicles and Active Messages dialogs, select the Save Window Layout menu
item from the Tools menu.

· Options

To open the Options dialog and define preferences for sending, receiving and displaying incoming messages, either select the

Options menu item from the Tools menu, or click the Options tool button on the Active Vehicles toolbar:

· Show Message List

If the Active Message List window is not visible, you can display it by selecting the Show Message List menu item from the Tools
menu.

Note: If the Active Message List window is not loaded, open map viewers will not be updated with the latest vehicle positions
when new tracking messages are received.

· Show All Map Viewers

To make all open map viewers visible (restore minimized viewer windows), either select the Show All Map Viewers menu item

from the Tools menu, or click the Show All Map Viewers tool button on the Active Vehicles toolbar:

The Active Message List

This window is opened automatically when the Active Vehicles list is opened. It polls the Fleet Manager database for new
messages and lists messages for the vehicles listed in the Active Vehicles list window. It also displays pop-up message dialogs
to notify the user when new messages are received. Message information is retrieved and displayed based on the settings
specified in the Options dialog.

If necessary, the Active Message list window can be opened by selecting the Show Message List menu item from the Tools menu
of the Active Vehicles window.

249
www.mixtelematics.com

249
 250

Polling for New Messages

The Active Message List window polls the database for the complete list of active tracking, active event, job and free-text
messages the first time it is opened. All messages (or only filtered messages, depending on the options selected on the Filter tab
of the Options dialog) for the Active vehicles, are added to the list. The Messages dialog then checks for new incoming and
outgoing messages whenever the Refresh button is clicked or automatically at regular intervals (as specified in the New
Messages section on the Display tab of the Options dialog).

Message Display

Messages are added and displayed differently, depending on the type of message and the information associated with the
message.

· Message Priority

Urgent and Very Urgent Messages

These are added with an and icon respectively in the Priority column

Normal Priority Messages

If you have selected to show "All" messages in the Message Display section of the Options dialog, these are added without
any icon in the Priority column.

· GPS Data Messages

Messages containing vehicle position data can be plotted on a map and are added to the list with an icon in the GPS column.

· Message Type

Tracking and Status Messages

These are generally referred to as tracking messages and may or may not contain position data. They are added with an
icon in the Type column

Event Messages

These are generated by the unit in response to an event occurring within the vehicle. Event messages are configured in the
Active tab of the Vehicle's Event Properties dialog. If a parameter value is recorded with the event (configured when the
event was first created in the Fleet Manager software), it will be displayed in the Event Value column with units (if any) in the
Units column. These active event messages are added to the list with an icon in the Type column.

Job Messages

These display job description and most recent status information. They are added with an icon in the Type column.

Free-Text Messages

These display incoming (vehicle to office) and outgoing (office to vehicle) messages, as well as the most recent status
information. They are added with an icon in the Type column.

Vehicle Command Messages

These display outgoing messages that act as commands to a vehicle's unit. They are added with an icon in the Type
column.

· Other Information

250
www.mixtelematics.com

250
 251

Date/Time

This is the date and time the message was generated by the vehicle's unit (incoming messages) or the date and time of the
last status change in the database (outgoing job and free-text messages).

Vehicle Description

Driver Description

Event / Message Description

This is a short description of the type of tracking or event message or contains the job or free-text message header.

Value / Response

This contains the event value, any response to a job or free-text message or the last status of job, free-text or command
message.

Units

The units associated with an event value are contained in this column.

Odometer

This reflects the unit's odometer reading at the time that the message was generated.

Status

The most recent message status is displayed in this column.

Message List Features

The Messages list contains features that make viewing and managing active messages easier. These include:

· Notification Pop-up Dialogs

Depending on the settings specified in the Message Display section of the Options dialog, pop-up notification dialogs may be
display whenever new messages are added to the list. If multiple new messages are added to the list simultaneously, a warning
message will indicate the number of pop-up notification dialogs to be displayed. You choose not to view the unread messages
and if you do so, they will be marked as read and will not be displayed automatically again on the same PC for the same user.

· Message Detail Dialog

By right-clicking on a message and selecting Show Message Detail from the menu, the Notification Dialog for any message can
be displayed. This dialog allows you to view, print or copy to the clipboard all the information contained within the message. A
status history list is displayed for job and free-text messages. Note that the first date in the status history list is the date the status
was generated by the caller and is dependant on the Server, Processor or Vehicle Unit date and time settings. The date in

251
www.mixtelematics.com

251
 252

brackets is the server date when the status was changed in the database.

· Plot Message on Map

Any message that contains vehicle position information can be plotted on a map. Simply right-click on the message and select
Plot Position on New Map from the menu. This will open a new map viewer window, plot the point on the map, zoom to street
level and centre the map on the point.

· Sorting Columns

The Message list is sorted by the Date/Time column in descending order by default. This ensures that the most recent message
is always at the top of the list. To sort the list on any other column, simply click the column heading.

· Auto Scroll

To make finding new incoming messages easier, you can elect to have the Message List window automatically scroll to the last
new message added to the list. To do this, check the "Automatically scroll to latest incoming message" checkbox.

· Options

The Options dialog can also be accessed from the Active Messages window by clicking the Options button. This provides a quick
way to filter the messages displayed, by changing options on the Filter tab of the Options dialog.

· Last Refresh Date/Time

Whenever Message Polling takes place, the date and time is updated in the Message list window's title bar. This makes it easy to
determine when the latest messages were last retrieved from the Fleet Manager database.

252
www.mixtelematics.com

252
 253

4.2 Fleet Manager Advanced Driver Scoring Extension

© 2008 MiX Telematics | Updated 2008/07/04

Introduction
The Advanced Driver Scoring Extension provides two reports for driver scoring: a simple report and an advanced report. The
simple report allows a score to be calculated on a point addition or deduction basis, while the advanced report uses scoring
graphs to calculate a score using the duration and severity of the events when they occur. The FM Advanced Driver Scoring
Extension is an extended version of the current Driver Scoring Reports, in that it also allows scoring on all user events.

Installation
Fleet Manager Professional 9

The Advanced Driver Scoring Extension can be installed by running the Install set for Fleet Manager Professional 9, or with the
Add/Remove dialog in the Control Panel.

If you have the Fleet Manager Office CD at hand, please add insert the CD. If you do not have the Fleet Manager Office CD at
hand, you can install the Extension by opening Control Panel, select Add or Remove Programs, then select Fleet Manager
Professional and click on Change/Remove.

· Select Modify, which allows you to extend the current application by adding new features to install.

· Select Advanced Driver Scoring, which is located underneath Extensions > Driver Performance. Click Next.

· The next step is to select if you would like to install MSDE or configure the database manually. Click Next.

· Select the Communications Port to which the Download Pod is connected (if one is connected). Click Next.

· Select if Driver Reporting should be available or not. Click next and wait for the Extension to install.

253
www.mixtelematics.com

253
 254

Fleet Manager 2002 Professional

The Advanced Driver Scoring Extension can be installed by running FmAdsEx.exe, and following the directions.

Setting up Extension Options

Set the default options for the extension by selecting Tools\Options from the client menu, then selecting the “Extensions” tab, and
double-clicking on the “FM Advanced Driver Scoring” entry. This loads a form that has three tabs, namely: “Simple”, “Advanced”
and “Options”.

Simple Report Tab

Introduction

The simple report allows the user to draw reports based the addition or subtraction of points for each occurrence of an event. The
number of points to be added or deducted can be defined for each event to be scored.

Note : The resultant score is heavily influenced by the frequency of event occurrences.

Scoring Description

All drivers start with a specified number of points. For example drivers may begin with 0 points and have points be added for each
event occurrence. Limits may also be imposed on the driver’s total score, preventing the total score from falling below a specified
value, or exceeding a specified value. The output of the report can be in points, but if both upper and lower limits are specified,
the user may choose to have the results displayed as percentages, where the lower limit yields an average of 0%, and the upper
limit yields an average of 100%.

Components
Components Description

254
www.mixtelematics.com

254
 255

· Event Selection Button

New events can be selected or changed by clicking on the event selection button. If you wish to clear an event entry, press this
button to load the event selection form. There is a “Clear Event” button on this form to have the entry cleared.

· Event Entry

After an event has been selected, the event description and points criteria are displayed on the form.

If you types “-” in the points text box, the number will remain unaffected, but the description text box will change to “will be
removed” and the text will become red. This means that each time this event occurs for a driver, that amount of points will be
deducted from the drivers total.

If you types “+” in the points text box, the number will remain unaffected, but the description text box will change to “will be added”
and the text will become green. This means that each time this event occurs for a driver, that amount of points will be added from
the drivers total.

Note : See Also, “Selecting Events (Simple Report)”, for a detailed explanation of event selection.

· Settings Frame

255
www.mixtelematics.com

255
 256

The “Start From” text-box allows you to enter the number of points that the driver starts with. Selecting “No Limits”, means that no
limits are imposed on the number of points calculated.

Selecting “Limited” imposes an upper and/or lower limit on the number of points calculated. In the above example, the driver
starts with 5000 points, but can never acquire more than 8000 points.

256
www.mixtelematics.com

256
 257

In this example, both the upper limit and lower limit have been specified, and the option to display the results as percentages has
been enabled. In this case, if the driver acquires 8000 points or more, the report will show 100%, and if the driver acquires -2000
points or less, the report will show 0%.

Note: The “Start from” value must fall within the bounds of the upper and lower limits, and the upper limit (if selected) must by
greater than the lower limit (if selected), else an error message will be displayed.

· OK Button; Cancel Button; Load Button; Save Button; Reset Button; Description Button

See “Buttons Description”.

Selecting events (Simple Report)

If no event is selected, the event entry is greyed out. The input text boxes are also hidden. An event can be selected by pressing
the button next to any checkbox. This brings up an event selection form with a list of events. If the event entry was empty, there
will be only two buttons (OK and Cancel). If the event entry was populated, then there will be three buttons (OK, Cancel and Clear
Event).

The button functions are described below:

· OK Button
When this button is pressed, the event will be selected.

· Cancel Button
Pressing this button simply cancels the form, and ignores any selections made.

· Clear Event Button

Pressing this button clears the event entry.

After a new event has been selected, the event name and points criteria are displayed. Each event has a corresponding
checkbox. The events with check boxes selected will be the ones reported on, while those with unchecked boxes will not be
reported on.

Deleting events (Simple Report and Advanced Report)

If you wish to clear an event entry, first select the event by pressing the “Event Selection Button”. This loads a form that lists the
events. In the bottom right corner of the form there is a “Clear Event” button to clear a selected event.

Advanced Report Tab

Scoring Description

The advanced report allows you to create reports using linear equations and weight factors. Each event has a score generated
for it, based on two linear equations. The dominance of the one equation over the other can also be specified. In turn, the event’s
contribution to the total score can be weighted. This scoring system penalises drivers when events occur. The magnitude of the
penalty incurred is dependant on the severity and duration of the events. The event sub trip scores are weighted either by sub trip
duration, by sub trip distance, or by both equally. If in the case of sub trip the distances are 0km, then 100m will be used in the
score calculation to allow the event sub trip score to have some influence on the final event score. (This happens for trips that are
less than 100m, or for trips that are recorded if the driver turns the ignition on and off again). There are three main aspects in the
scoring of an event, namely: the contribution of the chosen event score to the total score, the duration factor applied in generating
the event score, and the severity factor applied in generating the event score if applicable:

Contribution

If an event has a contribution of 20%, then it means that the score generated for that event will influence the final score by 20%

Duration

The duration column allows the user to specify a percentage as a threshold for the duration score (marked with an x). If the x is

257
www.mixtelematics.com

257
 258

close to 100%, the scoring is more lenient, as opposed to giving x a very small value, which makes the scoring stricter. The “x”
point also can be said to define the point at which all points for that event’s duration or severity are lost, or the point beyond which
all toleration is lost:

Severity

The severity column also has a value that sets a threshold (see x below). The horizontal axis is from 0% to 200%.

· The domain 0% to 100% is for events which store minimum values. For example: Road Speed < 30. If an event occurs, and
the minimum value during that sub-trip is 20, then the severity is 66%.

· The domain 100% to 200% is for events that store maximum values.For example: Road Speed > 30. If an event occurs, and
the maximum value during that sub-trip is 40, then the severity is 133%.

If the x is close to 200%, the scoring is more lenient, as opposed to having x very small value which makes the scoring stricter:

Note: Observe how the graph is mirrored about the y-axis.

· Pyramid

The pyramid is a 3D representation of the severity and duration graphs (see below):

This representation is graphically displayed by the application:

258
www.mixtelematics.com

258
 259

As can be seen from the image above, the graphs are combined. If the pyramid is stretched toward the edges (toward 0% and
200% for severity, and toward 100% for duration), the pyramid will contain more green, indicating that the scoring is more lenient.
The concept of the pyramid having red and green shading is that it will give an intuitive ‘feel’ for the leniency or strictness of the
scoring system. Also, although the threshold values can be entered in the text boxes, they can also be set by clicking near the
axes on the graph.

Components
Components Description

Event Selection Button

259
www.mixtelematics.com

259
 260

New events can be selected or changed by clicking on the event selection button. If you wishes to clear an event entry, use this
button to load the event selection form.

Event Entry

After an event has been selected, the event description and the contribution, duration and severity criteria are displayed on the
form.

If the event is a duration event: Two text boxes will be displayed: “Contribution” and “Duration”. For duration events, the slider bar
is disabled and fixed at 100% duration.

Note: For an explanation on the slider bar, see “Duration/Severity Slider Bar”.

If the event is a severity event, three text boxes will be displayed; “Contribution” and “Duration” and “Severity. If a new event is
added, and the event condition is such that the event value is greater than or equal to (“>” or “>=”) a value, then the severity will
default to 150%. If a new event is added, and the event condition is such that the event value is less than or equal to (“<” or “<=”)
a value, then the severity will default to 50%.

There are three text boxes, namely contribution, duration and severity:

· Contribution text box

By default, the contribution is set such that each event has an equal weighting in the scoring calculation. When a new event is
added, its contribution will be set to 0. The user must then enter the contribution that the event is to make toward the total score
for the driver. If there is more than one event entry, and the user types in a contribution percentage, the following will apply:

- If the sum of the contribution percentages of the other events plus the percentage just typed in is less than 100%: Then the
other text boxes will remain unaffected.

- If the sum of the contribution percentages of the other events plus the percentage just typed in is greater than 100%: Then the
other text boxes will be scaled proportionally such that the sum across all the event contribution text boxes is 100%.

· Duration text box

The duration text box allows the user to enter a duration threshold between 0 and 100%.

· Severity text box

If the event is a severity event, then this text box will be visible. If the sign of the event condition is “>” or “>=”, then the user can
enter thresholds between 100% and 200%. If the sign of the event condition is “<” or “<=”, then the user can enter thresholds
between 0% and 100%.

Note: - See the “Selecting events (Advanced Report)” section for a description of the event scoring types.

Pyramid Graph

The pyramid graph gives a graphical representation of the thresholds for an event.

Typing in text in the duration or severity text boxes changes the pyramid accordingly. Clicking on the pyramid and dragging the
points along the axis will alter the pyramid, and also change the text boxes pertaining to the relevant axes after the mouse button
has been released.

Duration/Severity Slider Bar

For a new event that has just been added:

· If the event is a duration only event, the slider bar will be disabled and set to 100% duration.

· If the event is a severity event (duration and severity), the slider bar will be enabled and set to 50%/50% by default.

260
www.mixtelematics.com

260
 261

Slider bar behaviour

· If the pyramid has a high duration value (100%) and a low severity value (99%, 101% on the severity axis), and the slider is
biased toward duration, the pyramid will become predominantly green.

· If the pyramid has a high duration value (100%) and a low severity value (99%, 101% on the severity axis), and the slider is
biased toward severity, the pyramid will become predominantly red.

· If the pyramid has a low duration value (0%) and a high severity value (0%, 200% on the severity axis), and the slider is biased
toward severity, the pyramid will become predominantly green.

· If the pyramid has a low duration value (0%) and a high severity value (0%, 200% on the severity axis), and the slider is biased
toward duration, the pyramid will become predominantly red.

Weighting Options Frame

The original driver scoring offers the “By trip time only” weighting option, but the FM Advanced driver Scoring Extension allows
you to select any one of the following weighting options:

· By trip time only

To generate the event score for an event, each event score for each sub trip is weighted by the duration of the sub trip.

· By trip distance only

To generate the event score for an event, each event score for each sub trip is weighted by the duration of the sub trip relative
to the other sub trips occurring in the specified grading date range.

· By trip time and trip distance

To generate the event score for an event, each event score for each sub trip is weighted equally by the duration of the sub trip,
and the distance of the sub trip relative to the other sub trips occurring in the specified grading date range.

Note: It is highly recommended that the third option is considered, as it allows the most honest scoring relationship between
event scores. The first two options are for more time/distance-intensive scoring.

OK Button; Cancel Button; Load Button; Save Button; Reset Button; Description Button

See “Buttons Description”.

Selecting events (Advanced Report)

If no event is selected, the event entry is greyed out. The input text boxes are also hidden. An event can be selected by pressing
the button next to any checkbox. This brings up an event selection form with a list of events. If the event entry was empty, then
there will be only two buttons (OK and Cancel). If the event entry was populated, then there will be three buttons (OK and Cancel
and Clear Event).

The form displays a list of events in three columns. The event is categorized as a duration-only event (referred to as a duration
event), or and event that allows both duration and severity components (referred to as a severity event).

A severity event is defined as an event that has only one mandatory event condition (optional event conditions are ignored),
which must be “>=”, “>”, “<” or “<=”. The last two columns display bullets that indicate whether or not the event is a duration or a
severity event.

After a new event has been selected, the event name, contribution, duration and severity criteria are displayed. Each event has a
corresponding checkbox. The events with selected checkboxes will be reported on, while those that are unchecked will not be
reported on.

Options Tab
The options tab allows the user to set extra filtering and sorting options for the report.

261
www.mixtelematics.com

261
 262

Components
Components Description

Filter Frame

The filter frame allows the user to display all drivers, the n best drivers, or the n worst drivers (where n denotes the maximum
number of records to be shown in the report).

Sorting Frame

The sorting frame allows you to view the reported data ordered by driver name, ordered by driver score (descending) or by driver
score (ascending):

· If “View all drivers” is clicked, the sorting frame is enabled. You can select any of the three available sorting options.

· If “View the best drivers” is clicked, the sorting frame is greyed out, and is fixed at displaying the data from maximum score to
minimum score.

· If “View the worst drivers” is clicked, the sorting frame is greyed out, and is fixed at displaying the data from minimum score to
maximum score.

Buttons Description
The following section explains the functions of the buttons on the options form:

262
www.mixtelematics.com

262
 263

OK Button

The application first performs a series of checks on the user data, and accepts the data if it is entered correctly. The application
will not accept the data if:

· No events have been selected.

· Limiting has been selected, the upper and lower limits are checked, and the lower limit is greater than the upper limit. (Simple
report only)

· Limiting has been selected, the upper limit is checked, and the “Start from” field is higher than the upper limit. (Simple report
only)

· Limiting has been selected, the lower limit is checked, and the “Start from” field is lower than the lower limit. (Simple report
only)

· The sum of the contributions across the events are less than 100% (Advanced report only)

Cancel Button

If this button is pressed, the application will ignore the data that has been entered.

Load Button

Pressing this button loads a saved report from a file.

Save Button

Pressing this button allows you to save the data to a file.

Reset Button

Pressing this button resets both the simple and advanced panes. The simple and advanced settings are cleared, and return to
their default values.

Description Button

Clicking this button brings up the description form:

Both the simple and advanced reports can have their own description. If the button is pressed while the simple pane is displayed,
then the simple description will be displayed and can be modified. If the button is pressed while the advanced pane is displayed,
then the advanced description will be displayed and can be modified.

Running the report

The simple report is found under: Reporting\Driver Reports\Driver Scoring\Advanced Driver Scoring (Simple Report)

The advanced report is found under: Reporting\Driver Reports\Driver Scoring\Advanced Driver Scoring (Advanced Report)

263
www.mixtelematics.com

263
 264

Criteria wizard
The Advanced Driver Scoring Extension requires you to select the drivers that are to be reported on and the date-time range.
These are entered using the criteria wizard:

Step 1 Drivers

The first frame of the wizard is driver selection. Make a selection based on Site, Reporting Group or Driver.

Step 2 Time Range

The second frame allows you to enter the time range for the report. The time range is set from the previous month to the current
day as default. Other options such as week-to-date and month-to-date may also be selected from the combo box.

264
www.mixtelematics.com

264
 265

Step 3 Save Criteria

The third frame allows you to set the extension specific criteria for the report, and save the criteria into a criteria file. This allows
the user to apply the same criteria to the report if the report is drawn on a regular basis.

Processing of Data (Advanced report)

The advanced report has two main steps in the calculation of the scores, namely the acquisition of data and the application of the
scoring threshold values to the data. The report implements an optimization feature; if an advanced report has just been run, and
another report is run with the exact same date/time and driver selection criteria, while no data is downloaded in the report period
in the interim, then the first step is left out, and the application moves immediately to the application of the scoring threshold
values.

Report Output
Simple Report

265
www.mixtelematics.com

265
 266

The event score column values are the total amount of points added/deducted for that event for that driver across the reporting
period. The report displays the averages for the report in the bottom row.

Advanced Report

The event score column values are the scores for that event for that driver across the reporting period. The report also displays
the averages for the report in the bottom row.

266
www.mixtelematics.com

266
 267

267
www.mixtelematics.com

267
 268

4.3 Fleet Manager Australian Driving Hours Exception Extension

© 2008 MiX Telematics | Updated 2008/07/04

Introduction
In order to adhere to Australian driving hours legislation, this extension produces an exception report based on the Australian
Road Traffic Legislation of 1999, which will assist management in taking corrective disciplinary action where exceptions occur.

This document describes the steps to follow when installing and using the Fleet Manager Australian Driving Hours Exception
Extension.

Installing and Loading the Extension

The Extension can be installed by running the Fleet Manager Professional 9 install set, and selecting to install the Australian
Driving Hours Exception Extension.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the Australian Driving Hours item in the list of available
extensions.

The extension must be registered before it can be loaded. Please contact Siemens FM Australia for more information regarding
registering your extension.

The Menu Items

The menu items for this extension are divided into two parts.

· Under the “Reporting” menu item, shown below in Figure 1, you have the option to generate a driver report.

· Under the “Tools” menu item (Figure 2), you have the option to configure the Tables and the Criteria for the extension. These
options will be explained in more detail later in this document.

268
www.mixtelematics.com

268
 269

Figure 1

Figure 2 Tools Menu Item

Legislation Table Form

The driving hours regulations set forth by the Australian government are presented in a table format and include groups of driving
criteria for that table. The extension allows you to create regulation tables like Bus Drivers, Truck Drivers etc. and save these to
the database.

When the extension is first installed, a default table structure is created and contains the legislation for Solo and Two-Up Truck
Drivers, Solo Bus Drivers and Two-Up Bus Drivers applicable to the Australian Road Traffic Legislation of 1999. Each table
structure contains criteria that define the driving time and resting time as set forth in the legislation.

The Add and Edit buttons open a maintenance form (shown below) where table structures can be created or modified. The Delete
button deletes the selected record from the Table Maintenance Form.

269
www.mixtelematics.com

269
 270

You can assign criteria to the table by using the buttons labelled Move Up and Move Down to move criteria items between the
upper list of available criteria items and the lower list of selected criteria items.

Legislation Criteria Form

The driving hours regulations set forth by the Australian government are presented in a table format and include groups of driving
criteria for that table. The extension allows you to enter a number of criteria which can be added to the legislation table explained
above.

When the extension is first installed, a default criteria structure is created that contains the legislation criteria for Solo and Two-Up
Truck Drivers, Solo Bus Drivers and Two-Up Bus Drivers. These criteria items are linked to the applicable tables and items may
be Added, Edited or Deleted at your discretion.

The following form is used to manage the criteria:

270
www.mixtelematics.com

270
 271

The Add and Edit buttons open a maintenance form (shown below) on which the criteria structure is defined. The Delete button
deletes the selected record from the Table Maintenance Form.

271
www.mixtelematics.com

271
 272

The maintenance form allows you to select from four different predefined criteria structures. Each structure contains different
wording used to define a criteria that best fits the requirement. Note that 5 hours and 30 minutes should be entered as 5.5 hours.

Generate Reports - The Standard Criteria Wizard

The Menu Items

The menu structure for the reports is shown earlier in this document. Upon selection of the Fleet Manager Australian Driving
Hours Exception Reports menu item, the criteria wizard will be launched.

The Criteria Wizard

The standard criteria wizard in the Fleet Manager Client Software includes an option to select from the list of Sites, Reporting
Groups or Drivers, exactly which drivers to report on, a date selection to specify the period range, and a “More Options” form that
will be used to define which legislation table to report on.

Step 1 of the Wizard allows you to specify which drivers should be included in the report.

272
www.mixtelematics.com

272
 273

Step 2 of the Wizard allows you to select a date and time range for the data to be included on the report.

Step 3 of the Wizard firstly allows the selection of more options, and secondly, the option of saving the selected criteria. The
More Options form is explained in more detail below.

273
www.mixtelematics.com

273
 274

The More Options Dialog

The More Options dialog can be accessed by pressing the button on the criteria wizard (when the reports are generated) or by
selecting the Tools menu option (top level menu structure found in the Fleet Manager Client software), then selecting Options
menu item that, in return, presents an Extension Tab and a list of extensions installed on the user machine.

Settings changed on the More Options dialog accessed from the Tools menu will affect all reports, whilst settings changed on the
More Options dialog accessed from the criteria wizard will only affect the report currently being produced.

The reports can be generated for a specific table and you can specify which table will be used by simply clicking on the table as
shown above.

Driver Reports

274
www.mixtelematics.com

274
 275

Below is an example of the exception report that is created when you complete the steps in the criteria wizard.

The report includes the description of the vehicle that was being driven when the exception occurred.

The “date start” and “date end” columns are the start and end times of the trips that are in violation. For example, should a trip
start at 08:00 in the morning and end at 13:00, but the exception started in the middle of the trip at 11:30, then the date start on
the report will be 11:30 and the date end 13:00.

Should the next resting period be insufficient (as described in the legislation criteria), the start and end time of these trip(s) will
appear in the next lines in the report until the driver takes a valid break that causes the violation to end.

The process will repeat itself for new violations that occur, with each defined in its own grouping structure as shown on the report.

The “significance” field is a cumulative value that increases with each consecutive violation and resets itself when a new violation
occurs

The following has to be considered in order to achieve accurate results:

· The driver is not allowed to be the default driver for two or more vehicles. If two drivers start driving different vehicles but
neither identifies them by using the driver code plug, the system assigns each trip to the default driver. This creates the
perception that one driver is driving two or more vehicles on the same time.

· Once the data is stored in the database, this action could result in faulty data which will increase the probability of an invalid
exception occurring.

· Should daylight savings adjustments be a factor, the selected period should not include a daylight savings period and should
rather be broken up into two separate reports, each starting prior to or ending after the adjustment for daylight saving time.

275
www.mixtelematics.com

275
 276

4.4 Fleet Manager Comms Scheduler Extension

© 2008 MiX Telematics | Updated 2008/07/04

Introduction
The Fleet Manager Comms Scheduler Extension enables you to create and maintain schedule entries that define when and how
often data is to be transferred to and from individual remote data transfer capable device (e.g. GSM, GPRS) equipped vehicles,
groups of vehicles and/or vehicles in a site.

Installing and Loading the Extension

The Fleet Manager Comms Scheduler Extension can be installed by running the Fleet Manager Professional 9 install set. The
Fleet Manager Comms Scheduler Extension is also automatically installed with the Fleet Manager Communications Suite.

Menus

The Fleet Manager Comms Scheduler Extension can be accessed by:

Clicking on the Scheduler menu item on the Tools menu,

Or clicking on the Scheduler tool button

Fleet Manager Comms Scheduler

The Scheduler window will be displayed.

276
www.mixtelematics.com

276
 277

Maintaining Schedule Entries

Adding a New Schedule Entry

To create a new schedule entry, click on the New menu item beneath the Schedule menu. The New Schedule Entry dialogue will
be displayed.

Enter a description for the schedule entry then complete the remaining details in the dialogue.

277
www.mixtelematics.com

277
 278

General

If you are defining a schedule for an individual vehicle, the combo box will only list vehicles that have a remote data transfer
capable device attached.

When defining a schedule for a site or reporting group however, only sites or reporting groups that have at least one vehicle with
a remote data transfer capable device connected will be listed.

When the transport is set as default while creating or modifying schedules that apply to a site or reporting group, some of the
functions that are specified in the schedule may not be supported by the vehicle's default remote data transport. If this is the
case, the function(s) will be ignored for that vehicle.

If a specific transport is selected and the schedule applies to a site or reporting group, only the vehicles in that site or reporting
group which support the specified transport will be scheduled.

Actions

Ensure that the computer(s) running the relevant Downloader application have the correct date and time set when utilising the
“Synchronise Date/Time” function.

Upload

The Upload options can only be chosen in conjunction with a quick or full download. This is a safety feature designed to ensure
that the latest trip and event information is always downloaded from the FM unit prior to uploading a new configuration or
firmware.

Schedule

When one or more of the Upload options are selected, “Once” becomes the only frequency available on the Schedule tab. This is
a safety feature designed to prevent accidental automatic uploading of a new configuration or new firmware device drivers. It is
crucial that you test a new configuration and/or new device drivers with a simulator or a vehicle close at hand before uploading

278
www.mixtelematics.com

278
 279

them to a vehicle that is less accessible. It is possible to upload a configuration or firmware that will prevent you from connecting
to the vehicle using remote data transfer in future, so a great deal of caution should be exercised when using these functions.

Click the OK button to display the schedule entry in the list. You can see the date and time that the schedule entry will be
processed in the Next Due column.

Editing a Schedule Entry

To edit a schedule entry, double-click on the required entry in the list box. Once you have made your changes click OK to save
them. A message box may be displayed asking you to confirm that you wish to re-schedule the entry. This only occurs if the entry
was originally scheduled to run only once. As soon as one of these entries is opened for editing, the date and time are set to the
current time, which means that merely clicking OK without changing anything else will re-schedule the entry. In some cases this
may not be desirable as the entry may have an action such as setting the odometer reading which should definitely not be done
again now. Therefore the warning is displayed to remind you that such unwanted actions may occur if you have not checked for
and disabled them.

You can define as many schedules as you require.

Activity Log
An activity log is maintained for each schedule entry. These logs are useful for monitoring the status of the entries. To view the
log for an individual entry, click on the required entry in the list and then click on the Log menu item beneath the View menu.

The log viewer window has a search facility enabling you to analyse the logs by searching for key words.

An auto-refresh option is also available from the View menu. Enabling this will refresh the log viewer window automatically every
20 seconds.

Viewing and retrieving a vehicle’s status

To view a vehicle’s status, right click on the vehicle in the list view in the Fleet Manager Client application and select the “Data
Transfer Functions” menu item, then select the “View Vehicle Status” submenu.

If the status information has never been retrieved for the vehicle, a message box will be displayed asking whether you would like
to schedule a status request. Click Yes.

279
www.mixtelematics.com

279
 280

The Vehicle Status dialogue will be displayed.

You will notice that the word “Scheduled …” appears in red text at the top of the dialogue. This indicates that the status request
has been scheduled for processing by the relevant Downloader application.

If you open the Fleet Manager Comms Scheduler Extension window (see “Maintaining schedule entries” above), you will see that
a new once-off schedule has been created automatically. The description of this new schedule is “Retrieve Current Status” and
the execution (next due) date of the schedule is set to today’s date at 00:00. This ensures that the relevant Downloader
application will execute the status request schedule as soon as possible.

As with any other schedule, you can monitor the progress of the status request schedule by viewing its activity logs. You can
access the activity log for the status request schedule by clicking on the View Log button in the Vehicle Status dialog.

The Vehicle Status dialogue refreshes automatically every 10 seconds whilst it is open, so if you leave it open, once the status
request schedule has been executed by the relevant Downloader application, the dialogue will be refreshed to display the
vehicle’s current status information.

280
www.mixtelematics.com

280
 281

Plot Position on Map

If the vehicle’s FM unit has a GPS connected to it, you can plot the vehicle’s current position on a map by clicking the “Plot
Position On Map” button.

Note: You must have an FM Professional version of the Fleet Manager GPS Log Viewer Extension, FM Map Set or Fleet
Manager GPS Log Viewer for MapPoint Extension installed to use this function. If you have an older version, the requests to plot
the position on the map will timeout and a message box will be displayed.

281
www.mixtelematics.com

281
 282

Vehicle Status
The Vehicle Status dialogue has a “Keep window on top” check box, which is checked by default. This is a useful feature when
viewing the vehicle’s status information in conjunction with its current position.

The Vehicle Status dialogue is non-modal, which means you may open many instances of it. This enables you to compare the
status information of more than one vehicle.

When the Vehicle Status dialogue is opened, the last status information that was retrieved is displayed. You can retrieve the
current status for one or more vehicles at any time by clicking on the “Retrieve Current Status” button on the appropriate Vehicle
Status dialogue.

Note: When you open the Vehicle Status dialogue, check to see whether another user has scheduled a status request for the
vehicle by looking for the word “Scheduled …” in red text at the top of the status dialogue. If another user has already scheduled
a status request for the vehicle, clicking the “Request Current Status” button will have no effect.

In addition to retrieving the current status of a single vehicle by clicking on the “Retrieve Current Status” button on the Vehicle
Status dialogue, you can also define one or more schedule entries to retrieve the vehicle status for a group of vehicles or all of
the vehicles in a site. To do this, create new schedule entries using the Fleet Manager Comms Scheduler Extension window (see
Maintaining schedule entries above). Such schedule entries may be configured to be processed by the relevant Downloader
application as soon as possible, or at some time in the future, once, or repeatedly. Any schedule which has the “Retrieve current
status” check box checked will update the vehicle status record in the database so that the new status information will appear in
the Vehicle Status dialogues.

282
www.mixtelematics.com

282
 283

Scheduling An Immediate Download

To schedule an immediate download from a vehicle, right click on the vehicle in the list view in the Fleet Manager Client
application and select the “Data Transfer Functions” menu item, then select the “Perform Full Download Now” or “Perform Quick
Download Now” submenu.

If you open the Fleet Manager Comms Scheduler Extension window (see “Maintaining schedule entries” above), you will see that
a new once-off schedule has been created automatically. The description of this new schedule is “Download Vehicle Now” and
the execution (next due) date of the schedule is set to today’s date at 00:00. This ensures that the relevant Downloader
application will execute the status request schedule as soon as possible.

Summary of functions
The Fleet Manager Comms Scheduler Extension n has the following functions:

Scheduler Window Menu Shortcut Key Function

Schedule

New INS Displays the New Schedule Entry dialogue, allowing you to
define a new schedule entry

Edit ENTER Displays the Edit Schedule Entry dialogue, allowing you to
modify the selected schedule entry

Delete DEL Deletes the selected schedule entry

Clear Log Clears the activity log for the selected schedule entry

Exit ALT-F4 Closes the Fleet Manager Comms Scheduler Extension window

View

Log Opens the Download Log window, allowing you to view the
activity log for the selected schedule entry

Refresh F5 Refreshes the Fleet Manager Comms Scheduler Extension

window

Tools

Clear All Logs Clears the activity logs of all schedule entries

Help

About Displays the About box containing information such as the

version number of the Fleet Manager Comms Scheduler
Extension.

FM Client Menu Shortcut Key Function

Vehicle Right-Click, Data Transfer Functions

283
www.mixtelematics.com

283
 284

View Vehicle Status S Displays the vehicle status dialogue

Perform Full Schedules a full download of trip and event data as well as
F
Download Now interval (tacho) data for the vehicle

Perform Quick Schedules a quick download of trip and event data as well as
Q
Download Now interval data for the vehicle

284
www.mixtelematics.com

284
 285

4.5 Fleet Manager Costing Extension

© 2008 MiX Telematics | Updated 2008/07/04

Introduction
The Fleet Manager Vehicle Costing Extension provides functionality to capture and report on your fleet operating costs.

Fuel cost transactions entered via the FM Terminal and/or the FM Client application, as well as service costs, are automatically
taken into account. Other fleet operating costs can be easily entered and maintained using the Vehicle Costing Extension’s
intuitive user interface. Cost transactions can be categorised as required with user-defined cost categories. Recurring costs can
be defined. The system includes multi-currency capabilities. A suite of reports is provided ranging from a detailed transaction-by-
transaction report to a summary per vehicle for a specified time period. Driving distance measured by the on-board computer is
used in conjunction with the cost transactions to calculate a cost per distance (CPD) for each vehicle. The actual CPD for each
vehicle is compared to a target CPD and variances are shown.

This document describes how to use the Fleet Manager Vehicle Costing Extension.

Installing and Loading the Extension

To install the extension, run the Fleet Manager Professional installation program and select the Vehicle Costing item under the
Fleet Manager Extensions section (Custom setup). It is advisable not to have the Fleet Manager Client application open whilst
installing.

Once installed, the extension will be loaded automatically. To change this, open the Extension Manager from the Tools menu,
and uncheck the Vehicle Costing item.

285
www.mixtelematics.com

285
 286

Menu and Tool bars

Menu

The Cost Category Maintenance Dialog and the Capture

Vehicle costs Dialog can be accessed through the Edit Menu
of the main window.
Vehicle Costs

Vehicle Cost data should be captured against individual vehicles

on a monthly basis.

More information on Vehicle Costs

Cost Categories

Cost categories are used to differentiate vehicle costs into Fixed

and Variable costs and to indicate which cost items are recurring
on a monthly basis.

More information on Cost Categories

Tool bars Cost Categories

When the Vehicle Costing Extension is loaded, it adds two
icons to the toll bar.
Vehicle Costs

286
www.mixtelematics.com

286
 287

Cost Categories
Cost categories are used to differentiate vehicle costs into Fixed and Variable costs and to indicate which cost items are recurring
on a monthly basis.

Accessing Cost Categories

The Cost Category Maintenance dialog is accessed through the Edit menu of the main window

· by clicking the Cost Category Maintenance tool-button:

· or selecting any of the above options opens the Cost Category Maintenance dialog:

This can be used to Add, Edit or Delete cost categories. When deleting a cost category, note that all costs related to that
category will also be removed from all vehicle cost data. When clicking Add or Edit, the Add/Edit Category dialog opens:

Note that a cost item belonging to a monthly recurring category, will be repeated automatically on the last day of every
subsequent month (following the date when the cost was first added for the vehicle), unless a final payment month is set for the
particular cost item.

287
www.mixtelematics.com

287
 288

The Default Memo entered here will appear in the Memo field for new costs entered against this category.

When clicking the Protect button on the Cost Category Maintenance dialog, the Change Password dialog appears. This allows
password protection to be set on all Vehicle Costing functions and prevents unauthorised users from viewing sensitive cost
information. To disable password protection, simply save a blank password using the same dialog.

Vehicle Costs
Vehicle Cost data should be captured against individual vehicles on a monthly basis.

Accessing Vehicle Costs

· The Vehicle Costs dialog is accessed by right clicking a vehicle and selecting Capture Vehicle Costs

· By clicking the Capture Vehicle Costs tool-button

Selecting any of the above options opens the Vehicle Costs dialog

288
www.mixtelematics.com

288
 289

This can be used to Add, Edit or Delete costs for individual vehicles. The target Cost Per Distance (CPD), used as a comparative
value for actual CPD in Vehicle Cost reports, can also be entered here. When clicking Add or Edit, the Add/Edit Cost dialog for
the selected vehicle opens:

This allows costs to be added for the selected vehicle. When selecting a cost category, the default memo (if any) for the selected
category will appear in the Memo field. This can be changed for the current cost item. The last payment month can be set for
recurring type costs.

When capturing Cost Values, select the appropriate Currency (base currency selected by default) and then enter any two of the
three values (Value, Conversion Factor and Base Value). The third value will be calculated automatically. When capturing costs
in the base currency, only enter the Value (Conversion Factor = 1 selected automatically).

289
www.mixtelematics.com

289
 290

Note: Also remember to enter the Odometer value applicable when the cost was incurred. Do not enter an odometer value for
fixed or recurring costs.

Invoking the Reports

A menu for the extension is added to the Vehicle Reports menu of the main window:

Select either the Summary- or Detail Report, depending on level of detail required from the report.

Report Criteria
The Vehicle Cost per Distance (CPD) reports uses the standard report criteria wizard from the Fleet Manager Professional
interface.

Step 1: The first step allows the selection of vehicles based on Site, Reporting Group or individuals.

Step 2: The second step allows the period to be specified:

290
www.mixtelematics.com

290
 291

Step 3: The third and last step of the wizard allows for criteria to be saved to a criteria file. A report can then be opened later
using the Open Criteria File menu option.

Note: A report cannot be generated for cost data where the base currency changes. If you do get an error message that indicates
a change in base currency, check the vehicle cost items as well as the fuel and service costs for the vehicles you want to report
on, and make sure that all costs use the same base currency. For this reason, it is not advisable to regularly change the base
currency using the Fleet Manager System Tools 1 Extension.

Sample Report

291
www.mixtelematics.com

291
 292

Exporting a Report
Each report provides the functionality to export its data into 5 of the main formats. Namely Comma Separated Values (.CSV) ,
Microsoft Word (.DOC) , Microsoft Excel (.XLS) , Rich Text Format (.RTF) and Plain Text (.TXT).

To access the Export functionality, select Export from your File menu on your Generated Report.

292
www.mixtelematics.com

292
 293

4.6 Fleet Manager Event Consumption Reports Extension

© 2008 MiX Telematics | Updated 2008/07/04

Introduction
The Fleet Manager Event-Consumption Report extension allows the customer to print reports that display fuel consumption
figures based on event selection criteria, using either Metric, Imperial or U.S. measurement units.

The Event-Consumption report displays the following for one or more vehicles:

· The total fuel consumption.

· The fuel consumption for a first event.

· The fuel consumption for a second event.

Any of the three columns within the report may have a fuel consumption display based either on distance or duration.

· Metric: l/km; km/l; l/100km; l/min; l/hr

· Imperial and U.S: gal/mi; mi/gal; gal/100mi; gal/min; gal/hr

Installing and Loading the Extension

To install the Extension, run the Fleet Manager Professional 9 installation program. It is advisable not to have the Fleet Manager
Client application open while installing.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the Event Consumption Reports item.

Menus and Toolbars

Menu

293
www.mixtelematics.com

293
 294

The Event-Consumption Report is run from the “Reporting” menu, found under Reporting > Vehicle Reports > Event
Consumption Report.

Setting up the Events

The Event-Consumption report extension requires events that are configured as fuel events. These events must have the
following characteristics:

· The event type is detailed.

· It records the start odometer value.

· It records the end odometer value.

· It records pulse counts.

· It records the event data after a delay of 2 seconds.

The figure shown below has the fields highlighted:

294
www.mixtelematics.com

294
 295

Example of an event configuration for a blower

This section shows how to create events that record fuel information for a blower mechanism. Two events are set up: the first, “
Blower On” records fuel while the blower device is turned on, and the second, “Blower Off” records fuels while the device is
turned off.

First, create a device called "Blower". It is to be configured as a Boolean switch which is connected to the blower mechanism. For
this device, you must create a parameter called "Blower On"

Then you must create the following two events:

“Blower On” Event:

(Ignition On = True) and
(Road Speed < 5 Km/h) and
(Engine RPM > 0 RPM) and
(Engine RPM < 900 RPM) and
(BlowerOn = True)

(The “Blower On” event is raised when the vehicle is idling and the blower is on.)

“Blower Off” Event:

(Ignition On = True) and
(Road Speed >= 5 Km/h) and
(BlowerOn = False)

(The “Blower Off” event is raised when the vehicle is moving and the blower is off.)

Both events are to be configured as Detailed Events. This is done by editing the property page for each event, and clicking the
record tab, then setting the events as "Detailed".

In the "Recording Options" frame, "Start Odometer", "End Odometer" and "Record Pulse Counts" must also be checked. The
events must be set to record after 2 seconds.

You must also have a Fuel Device connected to the unit - an EDM for instance. The fuel device will have a corresponding
Parameter. The parameter must be set as a Fuel Parameter (This is done by checking the checkbox on the parameter property

295
www.mixtelematics.com

295
 296

page).

Setting the Extension Options

The extension options are selected from the Tools\Options menu. The following form will be displayed:

The options are accessed by selecting “FM Event-Consumption Report” from the list, and the “Show Options” button.

The form below shows the default settings for the Event-Consumption report. The report has three columns, “Total Fuel” and two
event columns. The default settings for these columns are shown here:

Each column can have fuel consumption figures displayed either in distance or duration format. The format is selected from the
drop down list box:

296
www.mixtelematics.com

296
 297

The distance format allows fuel consumption figures to be displayed as:

· litres per kilometre

· kilometres per litre or

· litres per 100 kilometres

The duration format allows fuel consumption figures to be displayed as:

· litres per minute or

· litres per hour

The extension also caters for Imperial and U.S. measurement units. The units can be changed by selecting Tools > Options from
the main menu, and then selecting the measurement pane. The unit settings are contained within the “Measurement units” frame:

If Imperial or U.S. measurement options are selected and the options form is loaded again, the form will display the fuel
consumption options in that format:

297
www.mixtelematics.com

297
 298

The two right-hand event columns have an event assigned to each. To assign a different event to a column, click on the
corresponding event selection button. When the button is clicked, an event selection form is displayed:

The form has a checkbox that controls which events to display. If the checkbox is selected, then only the database events that
have specifically been configured as fuel events, will be displayed. If the checkbox is de-selected, then all events will be
displayed:

The option, which displays all events, allows you to select an event, which may have been a fuel event in the past, but has
subsequently been changed. If no fuel events exist in the system, all events will be displayed, and the checkbox will be greyed:

298
www.mixtelematics.com

298
 299

Reports
The report may be viewed in four different formats:

· Per Trip

· Daily

· Monthly

· Summary

Criteria Wizard
The Event-Consumption report requires the user to select the vehicles that are to be displayed and a date-time range. These are
entered using the criteria wizard.

Step 1 Vehicles

The first frame of the wizard is vehicle selection. Make a selection based on Site, Reporting Group or Vehicle.

299
www.mixtelematics.com

299
 300

Step 2 Time Range

The second frame allows you to enter the time range for the selected vehicles, and the report type. The time range is set from the
previous month to the current day. Other options such as week-to-date and month-to-date may also be selected from the combo
box.

Step 3 Event Selection

The third frame is event selection. If no events have been set by default, then events may be selected here

Step 4 Save Criteria

The fourth frame allows you to set the extension-specific options for the report, and save the criteria into a criteria file. This allows
you to apply the same criteria to the report if the report is drawn on a regular basis.

300
www.mixtelematics.com

300
 301

More Options

If no default settings have been saved for any of the two columns, the event columns will indicate that there are no events
assigned, by displaying “Not Selected” in red:

You will not be allowed to press OK until two events have been selected.

There is also a “Toggle Events” button. When this is clicked, the event assignments of the two columns will swap.

After “OK” is pressed, the report is generated by pressing the “finish” button.

Report Layout
The figure below shows the report layout for a vehicle, and displays fuel data for a vehicle that has a “Blower On” event:

301
www.mixtelematics.com

301
 302

302
www.mixtelematics.com

302
 303

4.7 Fleet Manager Event Summary Reports Extension

© 2008 MiX Telematics | Updated 2008/07/04

Introduction
The Fleet Manager Event Summary Reports Extension provides a suite of reports that can be used to analyse event information
recorded by Fleet Manager on-board computers.

Reports range from a detailed report listing each occurrence of the specified event and totals per vehicle or driver, to a summary
report that produces a single line of totals per vehicle or driver for the specified event. All reports show the total number of
occurrences, total duration, minimum value, maximum value, sum of values and average value recorded for the specified event
during the specified time period.

This document describes how to install and use the Fleet Manager Event Summary Reports Extension.

Installing and Loading the Extension

To install the Extension, run the Fleet Manager Professional 9 installation program. It is advisable not to have the Fleet Manager
Client application open while installing.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the Event Summary Reports item.

Menus and Tool bars

The menu items for the Fleet Manager Event Summary Reports Extension are added to both the Vehicle and Driver Reports
menu item found under the Reporting Menu of the Fleet Manager Client application’s Main window.

On selection of the Fleet Manager Event Summary Reports, the user will be presented with the standard criteria wizard that
guides you through the steps to generate a report.

The vehicle reports option is illustrated graphically below.

303
www.mixtelematics.com

303
 304

Criteria Wizard
The criteria wizard creates the Event Summary Reports and consists of three steps.

Clicking on the appropriate menu item to open the Event Summary Reports wizard:

Step 1 of the Criteria Wizard allows you to specify which vehicles (or drivers) should be included in the report.

Step 2 of the Criteria Wizard allows you to specify the date criteria and how much detail you would like to include in your event
summary report.

304
www.mixtelematics.com

304
 305

Step 3 of the Criteria Wizard allows you to access the "More Options" form. When selecting More Options the dialog described in
the next section is displayed.

More Options
The More Options form allows the user to set default options that will affect the generation of reports by manipulating the data to
conform to the options set. When the More Options button is pressed, the Options form is populated and will allow you to specify
which event to report on. This data is stored on a temporary basis and will reset to the default values once the report is
generated.

Should you, however, want to change the default settings, the More Options form can be accessed via the Options Toolbar or
Options Menu in the Fleet Manager Client Application. Once the form is saved, the chosen settings will become the default
settings for every report created until these settings are changed again.

The More Options form is shown below.

305
www.mixtelematics.com

305
 306

Creating Reports
You can generate Event Summary Reports for both vehicles and drivers. Once the criteria wizard is open, specify (step two of the
wizard) the detail level to report on. Below is an extraction from a report generated for a vehicle using the detail level option. The
detail level prints every event (as per the more options selection) for each selected vehicle and can result in large report if large
amounts of data exits.

306
www.mixtelematics.com

306
 307

The second example is extracted from a summary report that was generated by setting the detail level to summary level in the
criteria wizard (step two of the wizard). Data is summarized when the report is generated and drastically reduces the amount of
data included in the report.

307
www.mixtelematics.com

307
 308

Note that you can also select Monthly and Daily detail levels of which an illustration is not included in this manual.

308
www.mixtelematics.com

308
 309

4.8 Fleet Manager Exploration and Production Safety Extension

© 2008 MiX Telematics | Updated 2008/07/04

Introduction
Most Exploration and Production companies have stringent global QHSE driving policies and standards. As such, many
companies require that their vehicles be fitted with approved vehicle monitors, and that drivers have valid and appropriate
certification before being allowed to drive a vehicle. In addition to enforcing the policy and standards, companies are also
proactive in continually seeking measures and innovations that can prevent accidents and improve the safety of their staff.

The Fleet Manager Exploration and Production Safety Extension expands the Fleet Manager Software by including driver
certification, licensing and profile functionality to record, manage and report on a driver’s certification and safety profile. It
includes additional driver scoring reporting enhancements and new reports.

This document describes the steps to follow when installing and using the Fleet Manager Exploration and Production Safety
Extension.

Installing and Loading the Extension

To install the Extension, run the Fleet Manager Professional 9 installation program. It is advisable not to have the Fleet Manager
Client application open while installing.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the Exploration and Production Safety Extension item.

Menu and Tool bars

Menu

The menu items for this extension are divided into two parts.

Under the “Tools” menu item (Fig 1), the user will have the option to manage the driver certification and profile as well as to
maintain the certification, license and profile categories.

309
www.mixtelematics.com

309
 310

Under the “Reporting” menu item the user will have the option to generate driver reports as well as driver graphs under the
“Driver Reports” (Fig 2) and “Driver Graphs” (Fig 3) menu options respectively.

Fig 1

Fig 2

Fig 3

Maintain Certification Categories

In order to assign a certification to a driver, it is first necessary to define and maintain all available certifications. To manage
certifications, click on the “Exploration and Production Safety” menu item and select “Maintain Certification Categories” (under the

310
www.mixtelematics.com

310
 311

“Tools” menu in the Fleet Manager Client application).

The following page will be displayed:

This shows all available certifications saved in the database. The box shows the name of the certification as it will appear on
system reports and in a driver’s certification record. It also shows the period for which a certification is valid for the particular site,
and if it is mandatory or not.

The following functions are available to users: Add, Edit, Delete and Close.

Adding a Certification

Clicking Add will give the user a window to add a certification:

The user needs to capture the following information:

· Certification Name – the description of the certification .e.g. Commentary Drive

· Validity Period – this is the usual validity period for the certification. Options include 5 years, 4 years, 3 years, 2 years, 18
months, 12 months, 9 months, 6 months, 3 months, 1 month, etc. The validity period will apply to this certification only, and
only within the current database. It is used to calculate when a driver’s certification will next expire.

· Mandatory – this declares if this certification is mandatory or not. This option can be checked or unchecked. If it is checked,
the certification is mandatory. A mandatory certification is absolutely required for driving an OFS vehicle. If a mandatory
certification held by a driver expires, the driver is not permitted to drive until the certification has been renewed.

NOTE: The system does not prevent the driver from driving - this option is for reporting purposes only.

311
www.mixtelematics.com

311
 312

Editing a Certification

To change a certification’s details select a certification and click Edit. This will bring up the same screen that is used to add a
certification, but the fields will be populated with the data already stored for that certification in the database.

Deleting a Certification

To delete a certification from the available select a certification and click Delete. Should a certification be connected to a driver,
the certification cannot be deleted from the database. You must delete the certification from each driver using that particular
certification before deleting the record from the list of certifications.

Maintain License Categories

Simply defined, a driver license is used to indicate whether a driver has acquired the appropriate license(s).

To manage licences, click on the “Exploration and Production Safety” menu item and select “Maintain License Categories” (under
the “Tools” menu in the Fleet Manager Client application).

The following page will be displayed:

312
www.mixtelematics.com

312
 313

Adding a License

Clicking Add will display a screen to add a license category:

Editing a License

To change a license description select a license and click Edit. This will bring up the same screen that is used to add a license,
but the fields will be populated with the data already stored for that license in the database. For example:

Deleting a license

To delete a safety license from the driver’s record select a license and click Delete. Should a license be connected to a driver, the
license cannot be deleted from the database. You must delete the license from each driver using that particular license before
deleting the record from the list of licenses.

313
www.mixtelematics.com

313
 314

Maintain Profile Categories

Simply defined, driver safety profiles are used to indicate a driver’s risk potential. This information can be used in conjunction with
driver scoring data to review the relationship between the driver’s actual score and his assessed safety/risk profile.

To manage certifications, click on the “Exploration and Production Safety” menu item and select “Maintain Profile
Categories” (under the “Tools” menu in the Fleet Manager Client application).

The following page will be displayed:

The following functionality is available: Add, Edit, Delete and Close

Adding a Driver Safety Profile

Clicking Add will display a screen to add a driver safety profile category:

Editing Driver Safety Profile

To change a driver safety profile’s description select a driver safety profile and click Edit. This will bring up the same screen that
is used to add a driver safety profile, but the fields will be populated with the data already stored for that safety profile in the
database. For example:

Deleting a safety profile

314
www.mixtelematics.com

314
 315

To delete a safety profile from the driver’s record select a safety profile and click Delete. Should a profile be connected to a
driver, the profile cannot be deleted from the database. You must delete the profile from each driver using that particular profile
before deleting the record from the list of profiles.

Managing a Driver’s Certification Record

Each driver’s certification needs to be recorded in the system, so that adequate reporting and warnings can be available to give
the driver and his manager forewarning of any imminent expiries.

To manage a driver’s certification record, right click on a driver and select “Manage Driver Certification” (Fig 3). This function can
also be accessed from the Tools option on the main menu as shown in Fig 1 from above.

Fig 4

The certification record (managed and added by the functionality explained earlier in this document) must be connected to a
driver. Selecting the “Manage Driver Certification” from the “Tools” menu option instead of right clicking on a driver and selecting
the option from there (Fig 4) displays a list of drivers to select from before the main form is shown.

The Manage Driver Certification form is show below:

315
www.mixtelematics.com

315
 316

The certification record as contained in the driver’s QHSE passport is shown.

Each individual certification is validated to check whether it is valid, expired or will soon expire. Should it be Valid the certification
will be presented with a green tick, shown above. An orange tick is shown if it expires soon and a red cross if the certification
expired. The overall certification status is dependant on all of the certifications that the driver has and is determined by the
following rules :

· The Current Certification Status is VALID if all ‘mandatory’ certifications have not yet expired (i.e. expiry date later than today’s
date) or if all of the mandatory certifications were conducted by a qualified trainer. Should the overall certification status be
VALID, the status will be shown in black.

· The Current Certification Status is EXPIRED as soon as any one of the mandatory certifications expires. This can happen if the
expiry date of any of the mandatory certifications is earlier than today’s date, or if any of the mandatory certifications were
conducted by an unqualified trainer. Should the overall certification status be EXPIRED, the status will be shown in red.

· A driver has NO CERTIFICATION if no certification is linked to the driver and is shown in red.

It is thus possible for a driver to have the current certification status as VALID but have a certification that is expired when, for
example, the expiry date is exceeded but the certification is not mandatory.

The following options are available:

· Add/edit/remove certification

316
www.mixtelematics.com

316
 317

· Add/edit/remove drivers licenses

· Close

· Add a Certification to a Driver’s Record

Adding a Driver’s Certification

Clicking Add will display a screen to add a certification for a driver:

The user will have to capture the following information:

· Certification
Select a certification from the list of available certifications. (This list only contains certifications that are not already allocated to
this driver)

· Date obtained
This is the date on which the certification was obtained. Clicking on the drop down box will display a calendar tool to select the
date on which certification was achieved, with the current date as the default

· Instructor
This is the person who conducted the certification. Indicate if the instructor was qualified to do the test. If the instructor is not
qualified, the certification is not valid. This is useful to the manager so that when he captures the certification for a driver, it
serves as a double check to ensure the certification is valid in the first place.

Editing a driver’s Certification

To change a driver’s certification details select a certification and click Edit. This will bring up the same screen that is used to add
a certification, but the fields will be populated with the data already stored for that certification in the database. For example:

317
www.mixtelematics.com

317
 318

Removing a driver’s Certification

To remove a certification from the available list select a certification and click Delete. This will bring up a warning screen to allow
confirmation that the certification should be removed from the driver’s record:

Removing a certification might change the driver’s status to expired or current, depending on the certification that is removed and
the ones that remain. The certification will only be deleted from the driver and will not affect the list of available certifications
added on the other forms explained earlier in this document.

Adding/Editing a driver’s Country Driving Licenses

Clicking Add will display a screen to add a license for a driver:

318
www.mixtelematics.com

318
 319

Capture the following information:

· Country
Select a country from the list of available countries and licenses for these countries. (This list only contains countries that are
not already allocated to this driver)

· License Code
This value is the license code and will be populated when the country is selected.

· Date Obtained
This is the date the license was obtained.

· Date Expires
This is the date the license will expire.

Editing a driving license

To change a driver’s license details select a license and click Edit. This will bring up the same screen that is used to add a
license, but the fields will be populated with the data already stored for that license in the database. For example:

Removing a driving license

To remove a license from the available list select a license and click Delete. This will bring up a warning screen to allow

319
www.mixtelematics.com

319
 320

confirmation that the license should be removed from the driver’s record:

Managing a Driver’s Safety Profile

A driver’s personal safety profile needs to be maintained to ensure effective use of this information. A driver’s safety profile is
included on reports such as the Driver Scoring & Safety Report, as well as in the driver’s certification record. The information can
be used to ascertain the correlation between a drivers’s score and his safety profile and will provide useful information to
management regarding the specific driver’s behaviour and training requirements.

To manage a driver’s safety profile, right click on a driver and select Manage Safety Profile. This function can also be accessed
from the Tools option on the main menu.

The driver safety profile score is calculated by averaging all the scores captured for each profile category of the specified driver

The following options are available:

· Add/edit/remove drivers safety profile

· Close

320
www.mixtelematics.com

320
 321

Adding a driver safety profile

Clicking Add will display a screen to add a category for a driver:

Capture the following information:

· Select a Safety Profile category from the list of available categories. (This list excludes safety profiles categories that are
already allocated to this driver)

· Score – this is the score for the category and can be between 0 and 100

Editing a driver safety profile

To change a driver safety profile allocated to a driver select a driver safety profile and click Edit. This will display the same screen
that is used to add a driver safety profile, but the fields will be populated with the data already stored for that profile in the
database. For example:

Removing a driver safety profile

To remove a safety profile from the driver’s record select a safety profile and click Remove. This will bring up a warning screen
and allow confirmation before removing the safety profile from the driver’s record:

321
www.mixtelematics.com

321
 322

Note: Removing a safety profile from the driver’s record might affect the driver’s safety profile score.

More Options
The More Options form can be accessed by pressing the button on the criteria wizard (when the reports are generated) or by
selecting the Tools menu option (top level menu structure found in the Fleet Manager Client software) then selecting Options
menu item that, in return, presents an Extension Tab and a list of installed extensions.

Settings changed on the More Options dialog accessed from the Tools menu will affect all reports, whilst settings changed on the
More Options accessed from the criteria wizard will only affect the report currently being produced.

The “More Options” are divided into three tabs illustrated below.

Detail Report Tab

The Detail Report More Options tab allows you to specify which driver certifications must be included when reports are generated
and which driver certifications must not be included in the report.

Validity Report Tab

322
www.mixtelematics.com

322
 323

The Validity Report More Options tab is very similar to the Detail Report More Options tab and allows you to specify which driver
certifications must be included when reports are generated and which driver certifications must not be included in the report,
focusing more on validity of certifications than detailed data.

RAG Report Tab

323
www.mixtelematics.com

323
 324

The Rag Report More Options, also known as “Red Amber Green” Report More Options tab allow you to specify the boundary
score that differentiates a driver into a Red, Amber and Green colour spectrum when reports or graphs are generated.

The Criteria Wizard

The Criteria Wizard is the tool the Fleet Manager Client Application uses to help you generate Reports and Graphs. Should the
report or graph that you selected to generate require additional settings, a “More Options” button will presented (last step of the
wizard) which will open the applicable report or graph related form. The More Options are explained earlier in this document.

Clicking on the appropriate menu item opens the Criteria Wizard:

Step 1 of the Wizard allows you to specify which drivers should be included in the report.

324
www.mixtelematics.com

324
 325

Step 2 of the Wizard allows you to select a date and time range for the data to be included on the report.

Step 3 of the Wizard firstly allows the selection of more options, and secondly, the option of saving the selected criteria. When
selecting More Options the dialog described in the next section is displayed

325
www.mixtelematics.com

325
 326

Creating Reports
The Menu Items

Exploration and Production Safety Driver Reports can be printed from the “Reporting” menu item in the Fleet Manager Client
Application’s Driver Reports menu item. The reports that can be generated include Detail Certification Report, Validity
Certification Report, Driver Scoring and Safety Profile Report as well as RAG reports that include RAG Daily, RAG Monthly and
RAG Summary Driver Scoring Reports.

Detail Certification Report

This report can be produced for one or many drivers, using the standard reporting wizard. For each driver in the selection, the
report will contain each driver’s certification details. This is the same report that could be produced from the Managing
Certification Record page for an individual driver.

Drivers whose certification is already expired should be highlighted in red. Drivers whose certification is due to expire in 2 months
should be highlighted in amber.

326
www.mixtelematics.com

326
 327

Validity Certification Report

This report can be produced for one or many drivers, using the standard reporting wizard. For each driver in the selection, the
report will contain a top level summary of each driver’s certification details. This will immediately highlight to management which
drivers have expired certifications and which have valid certifications.

327
www.mixtelematics.com

327
 328

Driver Scoring and Safety Profile Report

The Driver Scoring and Driver Safety Profile Report is a modification of the existing FM2001 Driver Score report. It has been
modified to include the driver’s RAG score and Driver Safety Profile in the same report. This report includes all selected drivers in
the selected period and should use the standard reporting wizard.

RAG Daily, Monthly, Summary and Progressive YTD Driver Scoring Reports

The RAG Reports group drivers into groups of Red, Amber and Green distinguished from each other by a score worked out
applying the following formula to the data captured by the Fleet Manager Hardware device installed in the vehicle:

· Speed Score = ((Speeding Time / 10) / Trip Distance) * 100

· Acceleration Score = (Number Acceleration Occurs / Trip Distance) * 100

328
www.mixtelematics.com

328
 329

· Deceleration Score = (Number Brake Occurs / Trip Distance) * 100

· Total Score = Speed Score + Acceleration Score + Deceleration Score

Once the RAG score is calculated, drivers are classified into one of three groups which can be configured in the “More Options”.

For illustrative purposes the following values where configured in the “More Options”:

· Red drivers have a RAG score of > 5. These drivers require improvement.

· Amber drivers have a RAG score of 2-5. These drivers have room for improvement.

· Green drivers have a RAG score of < 2. These drivers are excellent.

The RAG Daily Reports calculate the score for each driver on a daily basis whilst the Monthly and Summary RAG reports
summarize the Scoring data appropriately. The Progressive Year to Date report gives the user an easy way of quickly identifying
which drivers are consistently in the red band by displaying the data in a tabular format by month. This report also includes a
summarised graph at the bottom.

The RAG Daily, Monthly, Summary and Progressive YTD Driver Scoring Reports are graphically presented below:

329
www.mixtelematics.com

329
 330

330
www.mixtelematics.com

330
 331

Creating Graphs
RAG Daily, Monthly and Summary Driver Scoring Graphs

RAG Graphs are created in addition to the RAG Reports and present the Report data in a graphical structure as illustrated by the
RAG Monthly Driver Scoring Report below:

331
www.mixtelematics.com

331
 332

332
www.mixtelematics.com

332
 333

4.9 Fleet Manager Export Extension

© 2008 MiX Telematics | Updated 2008/06/11

Introduction
Currently the Fleet Manager Client program’s data reporting functionality is restricted to the reports created by various extensions
which are defined and runs within the scope of the system.

These reports are the only way to represent data that is stored within the Fleet Manager database and often restrict reporting on
the data required for the user's own analysis.

It is therefore desirable to represent data in raw textual format by allowing the user to export only the data required utilising the
export extension’s exporting tool.

This document describes the easy steps to follow when installing and using the Fleet Manager Export Extension.

Installing and Loading the Extension

The Extension can be installed by running the Fleet Manager Professional 9 install set, and selecting to install the Export
Extension.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the Export Extension item in the list of available extensions.

Menus and Tool bars

Menu

The menu items for this extension can be accessed by clicking on the “Tools” menu option then “Data Export Extension”. The sub
menu items include the “Data Export Wizard”, “Immediate Export Log File” and “Data Export Log File” presented graphically
below.

333
www.mixtelematics.com

333
 334

The Data Export Wizard

Introduction to the Export Wizard

The Export Extensions Wizard functionality is limited to the number of “Export Template” files that are installed on the user’s
machine (file with an ‘sef’ extension). By default, three “Export Template” files (DDR – Driver Distance Report, TDR – Trailer
Distance Report and VDR – Vehicle Distance Report) are included in the installation of the Export Extension.

In addition to the default installed “Export Template” files, mentioned above, MiX Telematics can, upon request, create new
“Export Template” files. These files are also called “Master Files” and the format cannot be changed once installed.

The “Export Templates“ are accessed by running the Export Wizard in the Fleet Manager Client application once installed. The
following options (explained in more detail later in this document) should be noted:

· You can only create a copy of the Master File to change general settings like the headers, footers, fields included in the export
and position of fields by defining the first field, second field etc. Once the Master file is copied, a new name is given to the file
by the user. Should the Wizard be run the next time, the newly copied file will also appear in the lists of available exports and
can now be edited, deleted or copied.

· You can use the Master File exactly as it is and export the data immediately without changing anything

Navigate through all the steps in the Wizard, which may vary depending on the specifics of the “Export Template” file selected.
When the finish button is pressed in the Wizard a new file with the same name as the master file but with a different extension
(“seb”) is created. This file is called an “Export Bag” and contains the date range, Vehicle IDs, Driver IDs and more that is unique
to the specific export requirements. When the export is performed, the “Export Bag” is used and not the “Export Template”.

In Summary:

· An “Export Template” is required to initiate the correct steps in the Export Wizard.

· The template is issued on demand and installed into the appropriate directory.

· Without the “Export Template” the Export Wizard is useless and will not work.

· “Export Templates” are called “Master Files” and can only be copied or used as is - that is until a copy of it is created by the
Wizard.

· When a “Master Template” is copied a “User Template” is created which can be copied, edited, deleted or used.

· Once the Finish button is pressed after navigation all the way through the steps presented in the export wizard, a new file

334
www.mixtelematics.com

334
 335

called an “Export Bag” is created. The “Export Bag” is used to perform the actual export and contains information like date
ranges, Vehicle Id’s etc.

The Export Wizard

Step 1

Two new buttons have been added to the export Wizard screen; NEW FILE and OPEN FILE.

NEW FILE : This is for export of file template setup.

OPEN FILE : Allows you to open/select a template file from a list of installed templates. Once you have selected the template that
best fits your export needs and pressed next, you will have the option to copy, edit or use the template.

Step 2

The path and file specified in the space provided is the name of the text file that will contain the data as a result of the export. You
can specify whether the text file should be zipped (compressed).

Other options include override the file if it exists, or create the path if you typed it in instead of using the “…” button.

335
www.mixtelematics.com

335
 336

Step 3

Steps 4 and 5

Please make sure you read the introduction to the criteria wizard found earlier in the document before continuing. The files
presented below in Fig1 are the “Master Files” only. You will see in the next step (Fig 2) that the “edit” option is disabled because
“Master Files” cannot be deleted or edited.

Let’s assume that the wizard for the “DDR” (“Export Template” – Master File) was completed but you created a copy of it called
DD2. Fig 3 now includes the DD2 file that can be edited and deleted. It is still an “Export Template” but does not carry the
“Master” status anymore.

336
www.mixtelematics.com

336
 337

Fig 1

Fig 2

337
www.mixtelematics.com

337
 338

Fig 3

Fig 4

Step 6

338
www.mixtelematics.com

338
 339

Let’s assume that you created a copy of the Master “Export Template” (DDR) and named it DD2. You can now set the Template
description as well as the Field and Line Delimiter. The Field delimiter is the delimiter between fields. Four fields might be
exported: Field A, Field B, Field C and Field D. The comma (,) is the field delimiter and the Line delimiter is the delimiter that will
separate the next row of data from the first. Say 2 records are exported with a comma field delimiter:
Field A, Field B, Field C, Field D
Record 1, Record 1, Record 1, Record 1 {vbcrlf}
Record 2, Record 2, Record 2, Record 2 {vbcrlf}
The “{vbcrlf}” is the only line delimiter that causes the next record to start on a new row. Be careful not to make the line delimiter
state “;”. The following result will be obtained:
Field A, Field B, Field C, Field D ; Field A, Field B, Field C, Field D ;
Record 1, Record 1, Record 1, Record 1 ; Record 2, Record 2, Record 2, Record 2 ;
Step 7

The next step allows you to specify exactly which fields will be included and which fields will be excluded from the export. The

339
www.mixtelematics.com

339
 340

position can be changed by the up and down arrows and each field can be edited to define the correct format. The following form
opens once the field is edited:

The User Format is the format that the field must be exported in. If a double value of say 234.234 is exported and the format is
0.00 the value will appear as 234.23 in the new file.

Conversion Objects and Conversion Types

Conversion Object and Conversion Type are only enabled in conditions specified by the Template. Should these settings be
available – as above - the following applies:

· The Conversion Objects includes “Speed”, “Volume”, “Measurement” and “Seconds To Time”. If the field is a field that can be
converted, the options will be available to the user.

· The Conversion Types includes “Default”, “Metric”, “U.S” ,”Imperial” and “hh:mm:ss” which applies the correct conversion factor
to the data.

· For all Conversion Objects, except for the “Seconds To Time”, the Default option will convert the value to the default value that
the client is currently set to. (If the client's measurement setting is in Metric then the applicable values will be converted to a
metric value)

· In some instances the time is stored as a number field (seconds) in the database. In order the view the time as “hh:mm:ss”, the
time is converted by Setting the value in the “User Format” field equal to “hh:mm:ss”. The “Conversion Object” must be set to
“Seconds To Time” and the Conversion Type to “hh:mm:ss”.

Step 8

The Criteria Wizard is necessary only if the “Export Template” specifies that the criteria wizard is required. In some instances the
Criteria Wizard will be omitted.

340
www.mixtelematics.com

340
 341

Step 9

By default the header populated is the list of fields selected in the previous steps. Once changed to your requirements, it will stay
the same until the “Refresh” button is pressed. Note that the Line Delimiter and Field Delimiter are also included in the header
file. The “Refresh” button will always default to the selected Line and Field Delimiters.

Step 10

The second last step of the Wizard will always create the “Export Bag” file (with extension “seb”). Please read the introduction to
the export wizard if you had not already done so.

The “Export Bag” is used from here onwards and will always be used for exports. The “Export Template” used up till now can be
used again to create a new export, provided your file selection changes or criteria wizard selection changes etc. If your criteria
remains unchanged, the “Export Bag” can be used for quick daily exports or to schedule an export, but this is discussed in more
detail later in the document.

341
www.mixtelematics.com

341
 342

Step 11

The final step of the Export Wizard gives you a preview of what to expect when the gross data is exported. Presented above are
the first 5 records of the actual export. Should you decide to change settings, the Back button can be used to go back and do
this.

The “Perform Export Now” instructs the wizard to use the “Export Bag” created in the previous step and to perform the export.
Should you decide not to perform the export, the check box can be unchecked and the Finish button pressed. Before continuing
to the next menu items, the following should be considered in the Export Wizard:

• Using step 4 of the Export Wizard to select the “Export Template” instead of copying or editing it reduces the number of steps
although the base concept stays unchanged.

The Immediate Export Log File

The Immediate Export Log File is a log file that presents a list of previously created “Export Bag” files. An “Export Bag” file is
created with a .seb extension at completion of the Export Wizard.

342
www.mixtelematics.com

342
 343

Using Step 5 above, a copy of the Master “Export Template” file was created, called “DDR.sef”. We named it “DD2” and carried
on from there. When the “Export Bag” was written, a file with the name of “DD2.seb” was created.

Below is the log file with that particular file populated in it:

From here there are options to delete the file or to start the Export by selecting the appropriate item and pressing the correct
button below.

The Data Export Log File

Once an export is completed the history is written to a log file. Should the file be a text file, it can be opened by clicking on the
appropriate file and selecting the open button.

343
www.mixtelematics.com

343
 344

The Data Export Scheduler

The Data Export Scheduler is a stand-alone application called “ExportExtensionRun.exe” The file requires one parameter and can
be run from the command line (by selecting the “Start” button in Windows then “Run”). In the Command Line the following must
be entered, assuming we are going to run the DD2.seb file created earlier in the document.

The following text should be entered exactly as presented:

Database without login:

"<Fleet Manager Path>\ExportBags\ExportExtensionRun.exe" user1,DD2
where user1 is the user name, and DD2 is the SEB file (Export Bag) without extensions.

Database with login:

"<Fleet Manager Path>\ExportBags\ExportExtensionRun.exe" user2,pass,DD2
where user2 is the user name, pass is the password, and DD2 is the SEB file (Export Bag) without extensions.

Note: The “ “ must be added exactly as presented above. DD2 is the name of the “Export Bag” file and should be replaced with
the name of your created “Export Bag” files. Once the export starts, there will be no visible indication of the process running. You
can monitor the Data Export Log File in the Fleet Manager Client Software to determine whether and when the file was exported /
created.

It is possible to use Windows Task Scheduler to schedule the task to run on your defined settings by using the same
configuration shown above.

344
www.mixtelematics.com

344
 345

4.10 Fleet Manager Location Reports Extension

© 2008 MiX Telematics | Updated 2008/06/25

Introduction
The Fleet Manager Location Reports Extension enhances the Fleet Manager Software by including new vehicle and driver reports
as well as route planning functionality that allows you to plot routes before departure.

This extension offers essential reporting functionality to the user by including a number of new location-related reports in a
detailed or summary approach. Also included in its functionality is a Route Planning device which will prove to be indispensable
for route planning, accurate reporting and fleet management decisions.

You can use this extension to produce Job Messaging Reports that reflect messaging data when messages are sent to and from
vehicles using the Fleet Manager Active Tracking and Messaging Extension.

User-defined locations, used in the reports, are created and maintained by using the Fleet Manager System Tools 1 Extension.
More information regarding the creation and maintenance of locations and related functionality can be found in the Fleet Manager
Systems Tools documentation included in this release.

This document describes the steps to follow when installing and using the Fleet Manager Location Reports Extension reporting
and route planning functionality.

Installing and Loading the Extension

To install the Extension, run the Fleet Manager Professional 9 installation program, and select Fleet Manager Location Reports
from the Extension list. It is advisable not to have the Fleet Manager Client application open while installing.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the Location Reports item in the list of available extensions.

Menu Items
The menu item for the Location reports is added to both the Vehicle Reports (Fig1) and the Driver Reports menu item found

345
www.mixtelematics.com

345
 346

under the Reporting Menu of the Fleet Manager Client application’s Main window.

On selection of the Location Reports, you can create Detailed-, Overview-, and Summary Location Reports, or create a Route
Plan or Route Variance Report. The Route Plan report is not available for drivers and is therefore omitted from the Driver Reports
menu. Other Location Reports that can also be selected from include Driving Reports and Locations Not Visited, which reports on
locations that were driven through and locations not visited respectively..

Locate the Job Detail Report (for messaging reporting) on the same menu as the location reports. (Fig 2)

Fig 1

Fig 2

346
www.mixtelematics.com

346
 347

The Criteria Wizard

The steps to create a Location Report based on drivers or vehicles are the same. For this example a Location Report based on a
vehicle is created.

Clicking on the appropriate menu item opens the Vehicle Location Report wizard:

Step 1

Specify which vehicles should be included on the report.

347
www.mixtelematics.com

347
 348

Step 2

Select a date and time range for the data to be included on the report.

Step 3

Allows the selection of more options and the option of saving the selected criteria. When selecting More Options the dialog
described in the next section is displayed.

348
www.mixtelematics.com

348
 349

More Options
The More Options form (Fig 1a, b, c, d) allows you to set default options that will affect the generation of reports by manipulating
the data to conform to the options set. When the More Options button is pressed, the Options Form is populated and will allow
the user access to only the options that are applicable for the specific report selected. This data is stored on a temporary basis
and will reset to the default values once the report is generated.

Should you, however, want to change the default settings, the More Options form can be accessed via the Options Toolbar or
Options Menu item as displayed in Fig 2. Once the form is saved, the chosen settings will become the default settings for every
report created until these settings are changed again.

The More Options form has 4 tabs of which a graphical illustration of each is shown below.

The first option on this tab reduces the number of locations that will be displayed on the reports by filtering the “Arrived At”
location on the report to only show the selected locations in the list view control. Locations found under “Departed From” on the
reports will not be filtered and you would typically see all the locations the vehicle departed from, even if the location is a
coordinate value.

The second option, should it be selected, allows you to specify a time criteria spent at a location (“Time At Location”).

The third option should be used with care as it can slow down the generation of reports. Should this option be selected, the
system will try to locate an address for each record retrieved by using the appropriate log viewer selected from the combo box.

If you decide to use the South African Log Viewer, the “None” option must be selected. Any Log Viewers besides the South
African Log Viewer will be presented as options in the combo box. More information regarding the log viewers can be found in the
Fleet Manager GPS documentation.

349
www.mixtelematics.com

349
 350

Tab 1 (Fig 1a)

The fourth option substitutes all the locations that do not have valid addresses with their coordinate values. Should the coordinate
be missing, “unidentified location” will be printed on the report. If you choose to use both the GIS lookup function and to show
coordinates, coordinates will only be show if a valid address is not found for that location after the GIS lookup was done.

The fifth and final option allows you to specify the time range that history data can be looked up and is applicable to Locations
Not Visited. The time range is used to specify how far back a search must be performed into the history of trip data to find the last
visit (trip) to a specific location.

Planner Tab

The Planner Tab is used to set options for the Route Planner form. When you plan a route for a vehicle by selecting locations that
must be visited, the system will automatically work out the straight-line distance between the “from” location and the ”to” location
selected in the list. Roads that the vehicle travels on are always longer than the straight distance and there is thus an option to
add a % to the straight distance. The Route Planner functionality is explained in more detail later in this document.

Another option available is to specify an average speed at which the vehicle will travel from one location to the other. The system
will calculate the estimated arrival time of arrival (at a planned location). The system will use the average speed and distance to
calculate the trip time for a vehicle and display it. You can either change or accept the value on the Route Planning form.

350
www.mixtelematics.com

350
 351

Tab 2 (Fig 1b)

Variances Tab

The Variances Tab is used to set parameters for the Route Variation Report and will be available for that report only. The Route
Variance Report is produced after a trip was done and matches the actual stop at a location compared to the planned stop
primed before a trip is started.

The first option, to match planned stops with actual stops where the actual arrival time is within a given time from the planned
stop, is used to define a period of time that the system will use to determine whether a stop is a planned or unplanned stop. For
example, a vehicle delivering packages in the local area only will miss the stop if the arrival time is 1 hour later than planned. A
vehicle delivering packages from one city to another and travelling far distances will miss the stop if the arrival time is 8 hours
later than the planned arrival time.

Adjusting this time upwards or downwards will match different actual and planned locations with each other. This report is
explained later in the document.

You can choose to highlight Late and Early arrivals, Excess and Short Distance travelled as well as Longer and Shorter stops for
each actual stop matched with a planned stop. Adjusting the percentages, for example, for the Late and Early arrivals can change
a matched stop (planned with actual) from being a late arrival stop to being on time.

351
www.mixtelematics.com

351
 352

Tab 3 (Fig 1c)

Job Messaging Tab

The Job Messaging tab is used to specify whether the Job Location field will be included in the Job Detail Report or not.

Bear in mind that, when the Job Location is included, the report will print duplicate jobs with the exception to the job location
value, for each location when more than one location exists for a job.

352
www.mixtelematics.com

352
 353

Tab 4 (Fig 1d)

Once the Finish button is clicked, the report will be generated and shown on the screen. The reports can then be printed or
exported into Excel (xls), MS Word (doc), Portable Document Format (pdf), Text (txt) and other formats.

Fig 2

353
www.mixtelematics.com

353
 354

Sample Reports
Print various reports such as to those illustrated below.

Detailed Reports

There are three detailed reports on offer, each sorted differently, available for both vehicles and drivers. They are Detailed Visits
by Vehicle (shown above), which is sorted by vehicle (or driver for the driver reports), Detailed Visits by Location, which is sorted
by location, and Detailed Visits by Time At Location, which is sorted by the time a vehicle (or driver for the driver reports) spent at
a location.

Please note that the data displayed is subject to the criteria set under the More Options form explained earlier in this document.
Should the options on the More Options form’s first tab be set to only show certain locations, the Arrived At Location will only
display locations that meet that criteria, whilst the Departed from location will show all locations departed from.

You can select is to only display locations where the Time At Location is, for example, at least 30 minutes. This will reduce the
data in the reports and you will notice that the Time At Location column (right most column of this particular report) will not show
any values less than 30 minutes.

When you specify to use the GIS option, also found on the first tab of the More Options form, address lookups will be done for all
locations that are not user-defined. Should a valid address not be found, the report will display an “unidentified location” for those
particular locations. Note that this setting makes the report generation process very slow.

You can choose to display coordinates should the option be selected on the same tab mentioned above, and thus replace the
“unidentified locations” with a valid coordinate value. Should no coordinate be found, a “No coordinate available” text will be
displayed for those particular locations.

354
www.mixtelematics.com

354
 355

Summary Report

The summary report displays a condensed representation of the information in the detailed reports. Remember that the options
set under the More Options form will affect the summary report in the same way as it affects the detailed reports, and data will not
be included in the summary if the criteria in the More Options are not met.

It is recommended that, when creating a summary report for comparative usage to the detailed reports, the options on the More
Options form must remain unchanged between producing reports. This will reduce confusion when totals are compared etc.

Overview Report

The Overview report is a summarised representation of the summary report and, once again, when creating an overview report
for comparative usage to the summary report or detailed reports, the options on the More Options form must remain unchanged
between producing reports. This will reduce confusion when totals are compared etc.

355
www.mixtelematics.com

355
 356

Route Reports

There are two Route Reports. The Route Plan Report creates a checklist that the driver of a vehicle can use to manually enter
whether a stop was missed, unplanned, late, etc. This serves as a manual entry system that can later be compared to the second
report, the Route Variance Report (shown below).

The Route Variance Report uses and matches the data entered via the Route Planner form (explained later in this document)
before a trip is started and actual data after a trip is finished. Data is matched according to the More Options form's Route
Variance Tab. Should a stop be a Missed Stop or an Unplanned Stop then no variances will be reflected. Should the actual stop
fall within the planned stop variances of Late and Early Arrivals, Excess and Shortage Distance Travelled and Longer or Shorter

356
www.mixtelematics.com

356
 357

Stops will be highlighted. This is subject to the settings in the More Options form.

Job Detail Report

The Job Detail report is used to report on the job messages sent to a vehicle and can be generated by including or excluding the
Job Location, depending on the options set in the More Options form.

Route Planner
The Menu Items

The Route Planner Form can be opened from a vehicle’s context menu, the Tools menu item and the Toolbar shown above.

357
www.mixtelematics.com

357
 358

The Route Planner Form

358
www.mixtelematics.com

358
 359

Route Planning

Route Planning is done on a vehicle basis only and care should be taken to select the appropriate vehicle from the list of
vehicles. The vehicle is selected automatically when you right click on a vehicle and select the Route Planning option.

Plan routes for different intervals. Daily, Weekly and Monthly intervals are available from the list.

Once a location is added from the list of user-defined locations, the location will be placed in the “Planned Stops” list view. During
to the addition process, there is an option to specify the time at location, distance to travel and arrival time. The system calculates
this in advance using the two options, set under the More Options form, Route Planner Tab.

You can change the values and accept them. Once the stops are entered, you must save the data to the database by pressing
the Save button on the form. Also available are the Recalculate and Edit buttons. The Recalculate button will allow you to
recalculate the arrival times as well as the distance for all the trips. Indicate the starting point of recalculation by selecting a stop
in the Planned Stops list view. Recalculation is done from the selected point, downwards.

The Edit button allows you to edit a Planned Stop, as no editing functionality is available on the list view.

Stops can also be imported from and exported to a text file.

Load Routes

Routes can be loaded into the Route Planning form by clicking on the “Load Route” button. Once the button is clicked, a new
form will open which allows you to select the route (by clicking on the route and pressing the “Select Button”). Before the route

359
www.mixtelematics.com

359
 360

data is added, specify the first arrival date/time.

Routes can be managed by installing and loading the Fleet Manager System Tools extension into the Fleet Manager Client
Application. Please refer to the documentation for complete instructions regarding Routes.

360
www.mixtelematics.com

360
 361

4.11 Fleet Manager Passenger Extension

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The Fleet Manager Passenger Extension allows the user to print reports on passengers based on the trips that they have made in
vehicles listed in the database. Passengers are identified using the black Passenger Plugs.

This document provides an overview of the Passenger Extension and include the following topics:

· The Passenger Plug

· Installing and Loading the Extension

· Menus and Tool bars

· Manage Passenger Details

· Report Overview

· Generating a Report

· Missing Passenger Identification Dialog

The Passenger Plug

The passenger plug is a black coloured plug that is used to identify a passenger boarding or exiting a vehicle. When a passenger
boards a vehicle, he/she inserts their plug into the pod in the vehicle and then removes it. The time of the identification and the
odometer reading are recorded with this passenger's identification. When the passenger alights from the vehicle at a later stage,
he/she inserts and removes their passenger plug again. The time of the identification and the odometer reading are again
recorded. The period between these two identifications is then interpreted as the period that the passenger was on board the
vehicle.

It is important that the passenger is identified when he/she boards the vehicle and when he/she alights from the vehicle. Failure
to do this may lead to problems when generating passenger reports. To see how these problems are dealt with, refer to the ‘
Missing Passenger Identification Dialog.’

Installing and Loading the Extension

To install the Extension, run the Fleet Manager Professional 9 installation program. It is advisable not to have the Fleet Manager
Client application open while installing.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the Passenger Reports item.

361
www.mixtelematics.com

361
 362

Menu and Tool bars

The Passenger Reports can be accessed from the Reporting Menu in the main window.

Managing Passenger Details

A list of Passengers can be viewed and managed by clicking on Passengers in the Folder List.

For more information please view "How to set up and Manage Passenger Plugs" in the Fleet Manager Professional 9
documentation

Report Overview
There are 3 types of reports in this extension

362
www.mixtelematics.com

362
 363

Detailed

This report shows the following information for each of the specified passengers on separate pages:

· Driver of the trip

· Vehicle travelled in

· Date of trip

· Start time of trip

· End time of trip

· Total trip time for that passenger

· Total trip distance for that passenger

Summary

This report shows a summary of the specified passenger’s trips. The information displayed in this report consists of:

· Driver of the trip

· Vehicle travelled in

· Number of identifications

· Total trip time

· Total trip distance

Detailed per driver

This report shows a summary of the specified passenger’s trips for each driver in the database. The information displayed in this
report consists of:

· Driver of the trip

· Vehicle travelled in

· Start time of the passenger’s trip

· End time of the passenger’s trip

· Total trip time

· Total trip distance

This report also includes sub totals per driver.

Generating a report
Detailed Passenger Report

To generate a detailed passenger reports, follow these steps:

Step 1

363
www.mixtelematics.com

363
 364

Click on the ‘Detailed’ menu command in the ‘Reports -> Passenger Reports’ sub menu.

Step 2

The reporting criteria wizard is displayed. The first step in this wizard for this report is to specify which passengers to report on.
Select the passengers that you want to report on and click the ‘Next’ button.

Step 3

The next step is to select the time period for which the report is to show information for. Make this selection and click ‘Next’ or
‘Finish.’

Step 4

If you wish to save the criteria that you specified for this report up to this point, click the save button. To proceed to the report,
click ‘Finish.’

364
www.mixtelematics.com

364
 365

Step 5

Wait for the report to be displayed. If a missing passenger identification is reported, refer to the documentation on the Missing
Passenger Identification dialog.

Step 6

A report similar to the example shown below will be displayed.

Summary Passenger Report

The procedure for generating a passenger summary report is similar to the detailed passenger report. To generate a passenger
summary report, follow these steps:

Step 1

Click on the ‘Summary’ menu command in the ‘Reports -> Passenger Reports’ sub menu (see right).

365
www.mixtelematics.com

365
 366

Step 2

The reporting criteria wizard is displayed on the screen. The first step in this wizard for this report is to specify which passengers
to report on. Select the passengers that you want to report on and click the ‘Next’ button.

Step 3

The next step is to select the time period for which the report is to show information for. Make this selection and click ‘Next’ or
‘Finish.’

Step 4

If you wish to save the criteria that you specified for this report up to this point, click the save button. To proceed to the report,
click ‘Finish.’

Step 5

366
www.mixtelematics.com

366
 367

Wait for the report to be displayed. If a missing passenger identification is reported, refer to the documentation on the Missing
Passenger Identification dialog.

Step 6

A report similar to the example shown below will be displayed.

Detailed per Driver

To generate a passenger detailed per driver report, follow these steps:

Step 1

Click on the ‘Detailed Per Driver’ menu command in the ‘Reports -> Passenger Reports’ sub menu (see below).

Step 2

The reporting criteria wizard is displayed on the screen. The first step in the wizard for this report is to specify which drivers to
report on. Select the drivers that you want to report on and click the ‘Next’ button.

Step 3

367
www.mixtelematics.com

367
 368

The next step is to select the time period for which the report is to show information. Make this selection and click ‘Next’ or
‘Finish.’

Step 4

If you wish to save the criteria that you specified for this report up to this point, click the save button. To proceed to the report,
click ‘Finish.’

Step 5

Wait for the report to be displayed. If a missing passenger identification is reported, refer to the documentation on the Missing
Passenger Identification dialog.

Step 6

A report similar to the example shown below will be displayed.

368
www.mixtelematics.com

368
 369

Missing Passenger Identification Dialog

The ‘Missing Passenger Identification Dialog’ appears when an uneven number of identifications are found for a passenger on a
vehicle’s trip while generating a passenger report. The dialog offers 4 options, each of which provide different courses of action to
take. See the example below:

· Assume the missing identification is at the start of the passenger’s first trip during this trip.
Selecting this option will cause the application to add a passenger identification with a ‘Date Identified’ value and a ‘Odometer
Reading’ value which are the same as those at the start of the vehicle’s trip.

· Assume the missing identification is at the end of the passenger’s last trip during this trip.
Selecting this option will cause the application to add a passenger identification with a ‘Date Identified’ value and a ‘Odometer
Reading’ value which are the same as those at the end of the vehicle’s trip.

· Ignore this passenger on this trip.

Selecting this option will cause the application to ignore all of this passenger’s identifications on this trip.

· Insert an identification for this passenger on this trip.

When this option is selected, you need to specify the ‘Date Identified’ and the ‘Odometer Reading’ of the identification.
Depending on these values, the identification will be inserted into the correct position in the list of identifications for this
passenger on this vehicle’s trip.

369
www.mixtelematics.com

369
 370

At the bottom of the dialog, there is a check box labelled ‘Save this change.’ If this is checked, the option that has been selected
will be saved permanently.

To apply the change that has been made and continue generating the report, click on the ‘OK’ button.

370
www.mixtelematics.com

370
 371

4.12 Fleet Manager Snow Plough Extension

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
In order to manage snow ploughing activities more efficiently and effectively, the pre-installed Fleet Manager hardware (on the
snow plough) can monitor the distance that a snow plough travelled and the time spent within a user-defined location, among
other things. The Snow Plough Extension will allow you to generate two location utilisation reports that will report on these
variables monitored by the Fleet Manager hardware. The core values of the reports include the time spent in a location, the
amount of fuel used, the distance travelled and the area that where ploughed.

This document describes the steps to follow when installing and using the Fleet Manager Snow Plough Extension.

Installing and Loading the Extension

To install the Extension, run the Fleet Manager Professional 9 installation program. It is advisable not to have the Fleet Manager
Client application open while installing.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the Snow Plough (Loaded) item.

Menus and Dialogs

Menu

The menu items for this extension are divided into two parts.

Under the “Reporting” menu item (Fig 1), the user will have the option to generate detailed and summary location utilisation
reports. The menu structure are presented graphically below.

Under the “Tools” menu item (Fig 2), the user will have the option to use capture the blade width settings as well as the average
fuel consumption for a snow plough.

371
www.mixtelematics.com

371
 372

Fig 1

Fig 2

The Blade Width Settings Form

The Blade Width form is used to set the blade width for each snow plough. The “Set Value” button is used to set the value
entered in the text box for the snow plough(s) selected in the tree view (by using the checkbox next to it).

372
www.mixtelematics.com

372
 373

Should you want to reset the blade width value, a zero should be entered in the text box which will result in “*no blade width
defined” displayed in bold and attached to the snow plough description. Immediately after the value is set, the text box clears
itself.

The Average Fuel Consumption Settings Form

The Fuel Capture form is used to set the average fuel consumption for each snow plough. The “Set Value” button is used to set
the value entered in the text box for the snow plough(s) selected in the tree view (by using the checkbox next to it).

373
www.mixtelematics.com

373
 374

Should you want to reset the blade width value, a zero should be entered in the text box which will result in “*no blade width
defined” displayed in bold and attached to the snow plough description. Immediately after the value is set, the text box clears
itself.

Creating Reports
The Menu Items

The menu structure for the reports is illustrated earlier in this document under Fig 1. Upon selection of the Fleet Manager Snow
Plough Reports, you will have an option to create a Detailed and Summary Location Utilisation Report.

The Criteria Wizard

The standard criteria wizard, unique to the Fleet Manger Client Software, will include the option to select from the list of Sites,
Reporting Groups or Vehicles, exactly which snow ploughs to report on, a date selection to specify the period range, and a “More
Options” form that is used to define which events to report on. Read more about the more options in the “More Options” section
below.

Step 1 of the Wizard allows you to specify which equipment (or operators for the operator reports) should be included in the
report.

374
www.mixtelematics.com

374
 375

Step 2 of the Wizard allows you to select a date and time range for the data to be included in the report.

Step 3 of the Wizard allows the selection of more options and the option of saving the selected criteria. The More Options form is
explained in more detail below.

375
www.mixtelematics.com

375
 376

More Options
The More Options form can be accessed by pressing the button on the criteria wizard (when the reports are generated) or by
selecting the Tools menu option (top level menu structure found in the Fleet Manager Client software), then selecting Options
menu item to display an Extension Tab and a list of extensions installed on the user machine.

The More Options values set under the Tools menu item are saved as defaults for all the reports, whilst the More Options values
set under the criteria wizard are altered to set the options for that particular report only. The More Options choices found under
the Tools menu are presented below and include two tabs; Event Settings and General Settings.

The Event Settings Tab

It is up to you to create user-defined events which will be populated in the tree view shown above. The events that are applicable
to snow plough locations must be set up in the Fleet Manager Client software for the organisation.

A typical event that will allow accurate reports and conform to the requirements must be a detailed event set up to additionally
capture both the start and end odometer readings when the event occurs.

The event can be set up in such a way that, when the snow plough is in a <user defined> location with the RPM reading more
than <min> RPM and when the snow plough blade is <down or up>, it will occur and cause the hardware device installed on the
snow plough to capture the required data.

Refer to the Fleet Manager Client documentation how to set up a user defined event if this is unclear to you.

In our example, we created a user-defined (detailed) event that captures the start and end odometer reading for vehicle when it is
in a <user defined> location (in our case a town called Paarl) with the RPM reading > 1000 RPM in order to simulate the snow
plough activities entering, working in and exiting a <user defined> location.

376
www.mixtelematics.com

376
 377

The General Settings Tab

The General Settings will allow you to manage graphs to include or exclude in the reports, or specify the units which the area and
distance are defaulted to.

377
www.mixtelematics.com

377
 378

Detailed Location Utilisation Reports

The Detailed Location Utilisation Report will show detailed information for the selected location, for every trip a vehicle made in
the location. The Detailed Location Utilisation Reports will be categorised by the location, date and the name of the snow plough.
The following fields are included in the report.

· Vehicle
The Vehicle’s Name.

· Start
This will be either the time the vehicle entered the location, or the time when the vehicle was switched on in the location.

· Total Time
This will be the total time the vehicle travelled within the location – the end of each event occurrence minus the start of each
event occurrence.

· Distance Travelled
Total Distance travelled within the location for the trip.

· Stop
This will either be the time the vehicle left the location or the time when the vehicle was switched off in the location.

· Average Fuel Consumption for Vehicle ((litres or gallons) / Engine Hours)

The entered value of Fuel Consumption for the Snow Plough.

378
www.mixtelematics.com

378
 379

· Fuel Consumption for the Trip

The total Fuel consumed within the Location (in Litres/ Gallons).

· Width of Snow Plough Blade

The entered width of the Snow Plough Blade.

· Area Ploughed for the Trip

This is the distance travelled within the location multiplied by the width of the blade.

A graphical presentation of the report can be found below :

379
www.mixtelematics.com

379
 380

Summary Location Utilisation Reports

The Summary Location Utilisation Report will display summarised information for the selected location, for every vehicle which
travelled in the location. The Summary Location Utilisation Reports will be categorised by location, date and name of the snow
plough. The following fields are included in the report.

· Vehicle
Name of the vehicle.

· Total Time
This will be the total time the vehicle travelled within the location – the end of each event occurrence minus the start of each
event occurrence.

· Distance Travelled
Total Distance travelled within the location for the vehicle.

· Total Fuel Consumed for Vehicle

Total fuel consumed for the vehicle within the location (in litres or gallons).

· Total Area Ploughed for the vehicle

This is the distance travelled by the vehicle within the location multiplied by the width of the blade.

A graphical presentation of the report can be found below:

380
www.mixtelematics.com

380
 381

381
www.mixtelematics.com

381
 382

4.13 Fleet Manager Materials Handling Extension

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
Materials handling equipment as well as the materials transported by the equipment are exposed to various forms of
maltreatment. Currently the Fleet Manager unit is used by various materials handling vendors to monitor the use of the materials
handling equipment in order to reduce costs incurred by maltreatment.

In order to extend the use of the Fleet Manager unit, the current hardware range now includes a device called the Impact Sensor.
The Impact Sensor is used to monitor the G Force value of any impacts that the equipment incurs during an average day's use.

The Fleet Manager Materials Handling Extension is required to generate reports reflecting the daily use of equipment and
includes Utilisation, Event, Collision and Timeline Reports and Graphs.

This document describes the steps to follow when installing and using the Fleet Manager Materials Handling Extension.

Installing and Loading the Extension

The Extension can be installed by running the Fleet Manager Professional 9 install set, and selecting to install the Materials
Handling Extension.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the Materials Handling item in the list of available
extensions.

Menus and Dialogs

Menu

Under the "Reporting" menu item (Fig 1), the user will have the option to generate operator and equipment reports as well as
operator and equipment graphs. This example shows the Equipment Reports menu structure, but you can also follow the same
structure for the Operator Reports and both the Operator and Equipment Graphs.

382
www.mixtelematics.com

382
 383

Fig 1

Creating Reports
The Menu Items

The menu structure for reports is illustrated earlier in this document under Fig 1. Upon selection of the Fleet Manager Materials
Handling Reports, you will have an option to create Utilisation-, Events-, Collision- and Timeline reports for both operators and
equipment.

The Criteria Wizard

The steps to create a Materials Handling Report based on operators or equipment is the same. For this sample a Materials
Handling Report based on an operator is created.

Clicking on the appropriate menu item opens the Detailed Event Reports by Operator wizard for illustration purposes only:

Step 1 of the Wizard allows you to specify which operator (or equipment for the equipment reports) should be included in the
report.

Step 2 of the Wizard allows you to select a date and time range for the data to be included in the report.

Step 3 of the Wizard allows the selection of more options, or the option of saving the selected criteria. The More Options form is
explained in more detail below.

383
www.mixtelematics.com

383
 384

More Options
The More Options form is accessed by pressing the button on the criteria wizard (when the reports are generated) or by selecting
the Tools menu option (top level menu structure found in the Fleet Manager Client software) then selecting Options menu item
that displays an Extension Tab and a list of extensions installed on the user machine.

The More Options values set under the Tools menu item are saved as defaults for all the reports, whilst the More Options values
under the criteria wizard are altered to set the options for that particular report only.

The More Options found under the Tools menu are presented below and include three tabs; Event Settings, General Settings and
Graph Settings.

The Events tree view is a list of Default and User Events that are included in the reports. The "Change System Severity Report
Parameters" opens the following form:

384
www.mixtelematics.com

384
 385

You can specify 4 range settings applicable to the System Events. Each event is broken up into three ranges; Minimum, Medium
and Severe, which can be set by dragging the little black thumb in the bar from left to right or vice versa until a satisfactory value
is set.

These settings are used in the reports to categorise events into a minimum, medium and severe range as well as a colour
indicator used to set the colours of bars in the graphs.

In the main More Options form, you can select the General Tab which determines whether a report will include graphs or not.

385
www.mixtelematics.com

385
 386

You may also elect to hide the odometer column from appearing in the impact detection report. This may be helpful in cases
where odometers are not used, for example with fork lifts.

The Graph Settings tab allows you to specify the number of records that should be printed on each page populated with graph
data.

386
www.mixtelematics.com

386
 387

Operator Reports
Detailed Event Reports by Operator

The Detail Event Reports by Operator displays the events for the equipment in the organisation, sorted by operator and date of
the sub trip.

Should the event be a detailed system event the description field categorises the event as a minimum, medium or severe event
as per the settings in "More Options".

387
www.mixtelematics.com

387
 388

Detailed Event Reports by Event

The Detail Event Reports by Event displays the events for the equipment in the organisation, sorted by events and date of the
sub trip.

Should the event be a detailed system event the description field categorises the event as a minimum, medium or severe event
as per the settings in "More Options".

Detailed Collision Reports by Operator

The Detailed Collision Reports by Operator displays the collision (detected by the impact sensor) events for the equipment in the
organisation, sorted by operator and date of the event.

The description field categorises the collision event as a minimum, medium or severe event as per the settings in "More Options".

Also included in the report are two graphs that illustrate the totals for the report graphically (illustrated below). Once again the
graphs can be switched off in "More Options". The first graph illustrates the Maximum values of collisions and the second the
number of collisions for the operator.

388
www.mixtelematics.com

388
 389

Summary Collision Reports by Operator

The Summary Collision Reports by Operator displays the summary representation of the detailed report's collision (detected by
the impact sensor) events for the equipment in the organisation, sorted by operator and date of the event. The report is not
presented graphically in this document.

Detailed Utilisation Reports by Operator

The Detailed Utilisation Reports by Operator displays the utilisation for the equipment in the organisation, sorted by operator and
date of the sub trip. The report analyses the sub trips and breaks them down into a percentage driving, standing and idling time
for each sub trip.

A graph, included in the report, can be "switched off" by un-checking the "Include Graphs" option in "More Options". The pie chart
is generated for each operator and illustrates the total standing, idling and driving time as a percentage of the total sub trips.

389
www.mixtelematics.com

389
 390

Summary Utilisation Reports by Operator

The Summary Utilisation Reports by Operator displays the summary representation of the detailed report's utilisation data for the
equipment in the organisation, sorted by operator and the of the event. The report is not presented graphically in this document.

Equipment Reports
Detailed Event Reports by Equipment

The Detail Event Reports by Equipment displays the events for the equipment in the organisation, sorted by equipment and date
of the sub trip.

Should the event be a detail system event the description field categorises the event as a minimum, medium or severe event as
per the settings in "More Options".

390
www.mixtelematics.com

390
 391

Detailed Event Reports by Event

The Detail Event Reports by Event displays the events for the equipment in the organisation, sorted by events and date of the
sub trip.

Should the event be a detail system event the description field categorises the event as a minimum, medium or severe event as
per the settings in "More Options".

Detailed Collision Reports by Equipment

The Detailed Collision Reports by Equipment displays the collision (detected by the impact sensor) events for the equipment in
the organisation, sorted by equipment and date of the event.

The description field categorises the collision event as a minimum, medium or severe event as per the settings in "More Options".

Also included in the report are two graphs that illustrate the totals for the report graphically. Once again the graphs can be
switched off via "More Options". The first graph illustrates the Maximum values of collisions and the second the number of
collisions for the equipment.

Summary Collision Reports by Equipment

The Summary Collision Reports by Equipment displays the summary representation of the detailed report's collision events
(detected by the impact sensor) for the equipment in the organisation, sorted by equipment and date of the event.

391
www.mixtelematics.com

391
 392

Detailed Utilisation Reports by Equipment

The Detailed Utilisation Reports by Equipment displays utilisation of the equipment in the organisation, sorted by equipment and
date of a sub trip. The report analyses the sub trips and breaks them down into a percentage driving, standing and idling time for
each sub trip.

A graph, included in the report, can be "switched off" by un-checking the "Include Graphs" option in "More Options". The pie chart
is generated for the equipment and illustrates the total standing, idling and driving time as a percentage of the total sub trips.

Summary Utilisation Reports by Equipment

The Summary Utilisation Reports by Equipment displays the summary representation of the detailed report's utilisation data for

392
www.mixtelematics.com

392
 393

the equipment in the organisation, sorted by equipment and date of the event. The report is not presented graphically in this
document.

Operator Graphs
Collision Graphs By Operator

The Collision Graphs by Operator displays collision events (detected by the impact sensor) for the equipment in the organisation.

The description field categorises the collision event as a minimum, medium or severe event as per the settings in "More Options".

The graph's left axis shows the Maximum value of collisions for the operator and is grouped into Minimum, Medium and Severe
with the bars changing colour appropriately as set in the "More Options" dialog. The graph's right axis shows the number of
collisions (or impacts) that the operator induced.

You will notice that 4 (four) records are returned per page. This setting is explained earlier under the "More Options" form, Graph
Settings tab.

Utilisation Graphs By Operator

The Utilisation Graphs by Operator displays the utilisation for the equipment in the organisation, sorted by operator for all sub
trips for a date range. The graph analyses the sub trips and breaks them down into a percentage driving-, standing- and idling
time of the total sub trip time.

Equipment Graphs
Collision Graphs By Equipment

The Collision Graphs by Equipment displays collision events (detected by the impact sensor) for the equipment in the
organisation.

393
www.mixtelematics.com

393
 394

The description field categorises the collision event as a minimum, medium or severe event as per the settings in "More Options".

The graph's left axis shows the Maximum value of collisions for the equipment and is grouped into Minimum, Medium and Severe
with the bars changing colour appropriately as set in the "More Options" dialog.

The graph is not presented graphically in this document.

Utilisation Graphs By Operator

The Utilisation Graphs by Equipment displays the utilisation for the equipment in the organisation, sorted by equipment for all sub
trips for a date range. The graph analyses the sub trips and breaks them down into a percentage driving, standing and idling time
of the total sub trip time.

394
www.mixtelematics.com

394
 395

4.14 Fleet Manager Map & Guide Extension

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The Fleet Manager Map and Guide extension utilises Map and Guide’s map server functionality to create maps that can be used
to plot FM vehicle points and manage FM locations.

This document describes the procedure required to configure the Fleet Manager Map and Guide extension to utilise and setup
licensing and functionality provided by the Map and Guide map server. It is intended for Fleet Manager Administrators and
assumes that the reader has an in-depth understanding of installing and configuring Fleet Manager Extensions in the Fleet
Manager Professional range of software.

Components
The Fleet Manager Map and Guide extension consists of a number of components which perform discrete functions and interact
with one another. The table below lists these components and provides a brief description of their functions:

Component Function

FM Fleet Manager Map and Guide Host to open and close Map and Guide maps from the Fleet Manager Client
Extension applications and functionality to configure Map and Guide map server.

Map and Guide Map Server Map and Guide Map Server to generate maps used by the extension and can be found
on the installation CD.

License File Holds licensing information for the Map and Guide Map Server and is generated once
the Map and Guide Map Server components are installed.

Map Files Map files that should be installed on the machine and are not provided on the CD.

The Installation and Configuration Process

The following process must be followed to install, run and configure the Fleet Manager Map and Guide Extension.

Step 1:

Create a backup of your current Fleet Manager Professional database before attempting to install the Fleet Manager Map and
Guide Extension. The FM Fleet Manager Map and Guide Extension will upgrade the database upon installation, thus it is
imperative that you have a backup copy of the database should the installation or the upgrade procedures fail and corrupt your
database.

Step 2:

Install the Map and Guide Map Server found on the Fleet Manager Professional CD. This will install the Map and Guide Maps and
components required to generate maps for the extension.

The server, MapServer.exe, can be found on the Fleet Manager Professional CD by browsing to the MapServerIK directory.

395
www.mixtelematics.com

395
 396

Step 3:

Install the Fleet Manager Map and Guide Extension using the auto run feature found on the Fleet Manager Professional CD.

396
www.mixtelematics.com

396
 397

Step 4:

The extension setup will take you through the setup operation. Make sure that the extension is installed under the Fleet Manger
Professional path only e.g. C:\Program Files\Fleet Manager Professional

Step 5:

Run the Fleet Manager Professional software. A message should appear that indicates the database must be upgraded before
the extension can run. Select yes only if you made a backup copy of the database explained in Step 1 above.

The database will be upgraded. Do not shut down the PC during the operation. It could take several minutes.

Step 6:

Once the database is upgraded a message will appear to inform you that the process completed successfully.

397
www.mixtelematics.com

397
 398

Step 7:

The extension will attempt to start, but the configuration is not loaded at this point. Accept the message that informs you of this.
The Fleet Manager Client should continue loading and open normally.

Step 8:

Navigate to the Tools, Options menu item in the client, then to the Extensions tab once the Options form opens. Select the Fleet
Manager Map and Guide Extension. A form should open that contains the settings to configure the Map and Guide Map Server
and License options.

398
www.mixtelematics.com

398
 399

Step 9:

The first path to enter on the (blank) options form is the path to the maps installed on the machine. Navigate to a path that
contains maps e.g. “C:\Program Files\mg10\d7.map”

Once you have browsed to the Map file of your choice, the options form should look similar to this:

399
www.mixtelematics.com

399
 400

Step 10:

The second path to enter on the options form is the path to the Map and Guide Map Server License file on the machine where the
extension is installed. Navigate to a path that contains the “mapserv.lic” file e.g. “C:\Program Files\Common Files\MapServ
\mapserv.lic”

Once you have browsed to the license file, it should look similar to this:

Enter your licence information as indicated above. You can reduce or increase the number of licenses by toggling them. Please
note that, once saved, the next time the file is opened it will contain the information that you saved and not the information in the
screen shot above.

Step 11:

Close the form and restart the Fleet Manager Client application for the extension to load the configuration settings. When the
extension starts, it should load the extension without any message boxes. You will see the toolbars for the extension and be able
to use it.

400
www.mixtelematics.com

400
 401

4.15 FM Map Set Extension

© 2008 MiX Telematics | Updated 2008/05/07

Fleet Manager Map Set is a set of maps used in conjunction with Fleet Manager Track & Trace and Fleet Manager Professional.

The map set is integrated into FM Track & Trace, but is offered as an extension to FM Professional. It offers users the flexibility to
load specific map layers, the option to view labels, location names and other meta-data, and view a variety of map displays.

The FM Map Set facilitates and enables all the mapping, tracking and location management functionality of FM Professional.

Features
Active and Passive Tracking

Track your fleet in real time or replay historic trips on the map. The FM Map Set allows you to zoom in or out, pan around the
map, display or hide locations, and display more detailed position information. Start or stop tracking of a vehicle by sending an
instruction from the office. The on-board computer may also be configured to initiate tracking automatically when user-defined
events or conditions are detected.

401
www.mixtelematics.com

401
 402

Find Vehicle

Display the selected vehicle on the map.

Manage Locations

Add and define any desired location, such as customer, supplier or no-go zone.

Route Planning

402
www.mixtelematics.com

402
 403

Use the maps to plan routes by entering stops, start times and duration of each stop. This can serve as a daily job activity sheet
for your drivers.

System Requirements

· Operating System: Windows 2000, Windows XP Professional with CD-ROM drive

· Processor: Pentium IV 1.6 GHz or higher

· Disk Space: 1GB free disk space

· RAM: 1GB

403
www.mixtelematics.com

403
 404
4.15.1 FM Map Set Installation Guide

© 2008 MiX Telematics | Updated 2008/05/07

FM Map Set is installed automatically with FM Track & Trace. Use the following steps to install the Map Set when using FM
Professional 8.34 and newer:

Step 1:

Ensure that your computer meets the operating system requirements for FM Map Set. Insert the FM Map Set CD into the CD-
ROM. Run the Setup.exe file.

Step 2:

To continue the installation, click "Next".

404
www.mixtelematics.com

404
 405

Step 3:

Read the Licence Agreement and click "Yes" to continue.

Step 4:

Choose a destination location for the Map Set install. One will be chosen by default - to change this click "Browse" and find the
location you wish to use. Click "Next".

405
www.mixtelematics.com

405
 406

Step 5:

Enter your company name and registration code, click "Next".

Step 6:

The Map Set will now install on your computer.

406
www.mixtelematics.com

406
 407

Step 7:

Once the process is complete, click "Finish" to exit the installer.

407
www.mixtelematics.com

407
 408
4.15.2 FM Map Set User Manual

© 2008 MiX Telematics | Updated 2008/05/07

Installing and Loading the Extension

The FM Map Set Extension is installed by running the “Setup.exe” executable on your FM Map Set CD.

Once installed, the Extension is loaded using the Extension Manager in the Fleet Manager Client application. It can be configured
to load automatically at start-up by checking the box next to the Map Viewer item in the list of available Extensions. The extension
must be registered before it can be loaded.

Map Set Display Options

The Extension adds an item to the list of loaded extensions on the Extensions tab of the Options dialog.

Double clicking the item, or selecting it and clicking the Show Options button, displays the Extension’s Display Options dialog.
This dialog is also accessible from the Extension’s Criteria Wizard. This will be described in more detail later in this document.

Option Dialog

The Options dialog allows you to specify which points to display on the map, and how the Viewer should display them. Different
icons can be selected to represent different User and Default events, as well as Start, End and Route Log points. You can also
choose to show connecting lines between Log points, and change the line colour. This makes it easier to distinguish between
overlapping trips.

408
www.mixtelematics.com

408
 409

Note: The options you specify in this dialog are used as the default display options in the Extension’s Criteria Wizard, but can be
overridden in the Criteria Wizard at the time of generating a map.

Events Tree

Double click an item in the Events tree, or select it and click the Change Icon button. This displays the Select An Icon dialog that
allows you to pick an icon from the default font set.

409
www.mixtelematics.com

409
 410

Customise font, colour and style

You can select from any font on your system and change icon size, colour and style to obtain an icon that best suits the particular
point.

Advanced Options

410
www.mixtelematics.com

410
 411

By clicking the Advanced button on the Map Set Viewer Display Options window, you can define advanced filters to be applied to
the Map Sets when plotting them on the map. These filters generally determine the accuracy of the points displayed.

HDOP

HDOP is a measure of positional accuracy of GPS points. A lower HDOP indicates a higher accuracy.

Number of Satellites

The number of satellites detected by the GPS unit when the point was recorded influence accuracy. A minimum of 4 satellites is
required for a three-dimensional fix. More satellites usually constitute higher positional accuracy.

Age of Reading

When the GPS unit is unable to obtain an accurate fix, it saves the previous accurate position, as well as the time since the last
accurate position (age of reading). By setting the maximum age of reading to zero, you exclude any points that are inaccurate
according to the GPS’s factory set criteria.

Layer Offset

The Layer Offset values allow you to position inaccurate layers with a constant position offset error, in order to have them match
up trip log points. For the supplied map layers, leave these settings at the default values.

Export Logpoints to Google Earth KML file

Your logpoints will be exported in Google Earth .kml file format and viewable from the Google Earth programme, provided a
network link in Google Earth is set up.

Main Map Viewer Window

The Map Viewer has the following components:

411
www.mixtelematics.com

411
 412

Menu Bar

The menu bar provides access to all the main software functions.

Context Menu

While the mouse pointer is hovered over Locations, click the right mouse button. The context menu provides access to some of
the functions of the software.

Tool Bars

The tool bars provide access to the most commonly used features of the software.

Layer Legend

A legend tool on the left of the main window provides a list of all loaded map layers. You can move layers up or down in the layer
hierarchy by dragging and dropping layer items in the Legend. Note that the legend is locked by default to prevent accidental re-
order or removing of layers. To unlock the legend, uncheck the Lock Map Legend item under the Layers menu. It is also possible
to resize the Legend by dragging its right-hand border, and to show or hide the Legend by selecting the Legend item under the
View menu.

Scale Bar and Status Bar

At the bottom of the Viewer window, the Scale Bar and Status Bar respectively indicate the scale of the current map display and
information on the cursor location on the map.

412
www.mixtelematics.com

412
 413

Viewer Window
The map is displayed inside the Viewer window. The map can be panned by holding down the right mouse button while dragging
the map display. You can zoom in by dragging a rectangle (with the left mouse button pressed) inside the Viewer window.
Zooming out is accomplished by holding down the Shift key while clicking the left mouse button. You can also zoom to a specific
point by right clicking on the point and selecting Zoom to Point from the context menu. The same menu allows you to view detail
for a point by selecting Show Detail.

Viewer Functions

The Viewer provides various functions to help analyse Map Set points and manage Locations. Some of these functions are
described below.

Locations

Circular, rectangular and polygonal Locations in the Fleet Manager system can be maintained from the Fleet Manager System
Tools 1 extension, or added directly from the Viewer.

Add a Location

To add a location, select an appropriate location shape item from the Location menu:

or click the corresponding tool bar item and follow the instructions:

Once the location is drawn, fill in the Location name, type, address and other details on the Add New Location dialog:

413
www.mixtelematics.com

413
 414

Remove a Location

To remove a Location, click the Delete Location menu or tool bar button. To pan the map to a specific Location, select it from the
Go To Location drop-down box.

Show Detail

To view detail for a specific Location, hover the mouse over the point. The mouse pointer will change to display an information
icon. Click the right mouse button and select Show Detail from the context menu.

Street Sections

New street sections can be added for areas without detailed street level maps. To add a street section, click the Add New Street
Section item under the Edit menu, or click the tool button.

414
www.mixtelematics.com

414
 415

Map Point Detail

To view detail for a specific Map Set point, hover the mouse over the point. The mouse pointer will change to display an
information icon. Click the right mouse button and select Show Detail from the context menu.

To view a complete list of GPS Points for a specific vehicle, right-click the vehicle and select List All Logs from the context menu.

To pan the map to a specific log point, select it in the list and click the Zoom To button. To pan the map to the last log point for a
specific vehicle, select the vehicle from the Go To Vehicle drop-down box.

Address Search

You can search the local address database for street names. This enables you to quickly locate the position of a street on the
map. To open the Find Street Address dialog, either select the Find Address menu item under the Edit menu or click the Find
Address tool button. Type the name of the street you want to search for into the text box, then click the Find button. This executes
the search and displays all relevant streets in the list box.

Now simply select the required street in the list box and click the Locate on Map button. The map display will zoom to the location
of the street, and will place a Cross icon onto the map.

Map Layers and Files

One of the powerful features of the Viewer is the ability to move, load and unload layers to suit your particular requirements.
When the Viewer starts up for the first time, a default set of layers are loaded automatically. You can then load new layers or
remove loaded layers to suit your area and map view preference.

Loading Layers

To load new layers into the Viewer, either select the Add Layer menu item under the Layers menu or click the Add Layer tool
button.

This will display the standard File Open dialog. Select the file (map layer) type from the drop-down box and find the particular file
on the drive. Then click the Open button to add the new layer to the Viewer.

Supported map file types - File Type Comments

ESRI Shape (*.shp)

415
www.mixtelematics.com

415
 416

One of the industry standards for geographic data, these consist of a set of three files - shape file (.shp), index file (.shx) and
dbase file (.dbf) and could also include a projection file (.prj). To display properly in the Viewer, make sure that your Shape files
are in WGS84 geographic coordinates (decimal degrees).

CAD (*.dwg, *.dxf)

Digital eXchange Format and AutoCAD Drawing Database, these are industry standards for CAD files and allow any CAD file
saved in geographic units to be loaded into the Viewer

VPF (*.pft, *.lat, *.aft, *.tft)

Vector Product Format, this is the U.S. Department of Defence military standard for large geographic databases.

Standard Images (raster files)

The following raster files are supported and will display inside the Viewer, provided it has georeferencing information in its header
or there is a corresponding world file. *.bmp, *.dib, *.tif, *.tff, *.tiff, *.jpeg, *.jpg, *.bil, *.bip, *.bsq, *.gis, *.lan, *.rlc, *.sid, *.sun, *.rs,
*.ras, *.svf, *.img, *.ovr, *.l, *.ntf

Note: Image layers are added to the bottom of the layers hierarchy. Other map layers might hide the newly added image layer.
To make it visible, move it up in the hierarchy using the Legend Tool.

When adding CAD layers, the Viewer will prompt you to select which part of the CAD file to load. The viewer can only load one
feature type at a time. Select the feature type and press the Add Layers button.

Removing Layers

To remove a layer from the Viewer, first select the layer in the Legend and then either select the Remove Active Layer menu item
under the Layers menu or click the Remove Layer tool button.

To remove all loaded layers, select the Remove All Layer menu item under the Layers menu. Note that the Remove Layer
function is locked by default to prevent accidental removing of layers. To unlock the function, uncheck the Lock Map Legend item
under the Layers menu, and then select the layer to be removed.

Saving Layer Layout

To save your current layer setup, either select the Save Layout menu item under the File menu or click the Save tool button.

When the Viewer is loaded, the last saved layer layout is used to determine which layers to load and in what order.

Supplied Map Layers

The Fleet Manager Map Dataset will be installed with your extension. Look for the data under the "Maps" folder where your
extension was installed. When the extension starts for the first time, it will attempt to load some default layers from this folder.
You can also move the map files to a different folder or drive. The extension will prompt you to point to the new location at
startup.

FM Regional Map Viewer

Custom Layers Setup

ESRI Shape file layers supplied by third-party vendors can be opened by the Viewer, as discussed in the Map Layers and Files
section. These will be loaded with random, unformatted colours and without labels unless the Log Viewer is set up to recognize
these files:

416
www.mixtelematics.com

416
 417

If you are using the regional version of the Map Viewer (no Fleet Manager maps installed), use the Setup feature to edit your
custom layers for the correct colour and label display:

1. Open the extension's Display Options and click on the Setup button.

This opens the Format Setup File dialog:

This dialog is used to edit the setup file (DO NOT EDIT LayerFormat_Setup.lvs manually) and gives information on what changes
are required to the layer's .DBF files. This dialog can also be used to geo-reference image files (an alternative to the procedure
described in Georeferencing Image Files section.

2. Simply load a shape or raster (image) layer using the Open or Image buttons respectively. Then select the appropriate layer
type from section 2 of the dialog or, in the case of raster images, follow the on-screen prompts.

3. For the selected shape file layer, read the text in section 3 of the dialog carefully. Copy this text to a single text document for
later reference.

4. When all layer types are configured properly, click the OK button. This saves the new LayerFormat_Setup.lvs file.

5. Close the Setup dialog and make the required changes to the layer .DBF files as described in your text document.

6. Load the layers into the Map Viewer and confirm that the formatting (feature colours and labels) is correct.

Manual Setup

If you do not see a Setup button on the Options dialog, you can still configure your custom layers to be formatted like one of the
standard FM layers supplied with your extension.

1. Decide which FM layer TYPE best suits your custom layer's type. The Shape file can be a point, area or line type layer. If your
custom layer contains street data for example, it will match the FM _roads layers best.

2. Run "Regedit" from Start -> Run and locate the HKEY_LOCAL_MACHINE\SOFTWARE\Data Pro Development (Pty) Ltd\Fleet
Manager\Extensions\FMGPSCIS8\Settings folder. Add your custom layer's name to the appropriate string value. For example,
add your road layer's name to the "ArterialsLayers" or "RoadsLayers" (depending on what zoom level you want to view it). Note
the position of commas and spaces in this string.

3. Now all that's left to do is change your custom layer's .dbf file to match the structure of the corresponding FM layers. Locate
one of the .lvf files installed by the Log Viewer's install set (this should be in the same where the extension was installed). Open
one of these files with a text editor like Notepad. This file contains the information needed to format your layer to match a specific
Viewer and Layer type. You have to change your layer to this format. For the _roads layer example:

A. Locate ## StreetLabel ##. Note "SA_Field=Name". This means your roads layer's .dbf file must contain a column named
"Name" that contains the road descriptions/names. Use Excel to edit your Roads.dbf accordingly (be careful not to resize the
column widths - Excel seems to throw away parts of strings when doing this...)

B. Locate ## SA_MinorOuter ##. Note the "Field=CLASS". Again your roads.dbf should contain a roads class column that
contains the road types as specified ("FREEWAY", "NATIONAL", etc.) if the DBF does not contain road classes, rename another
text column to "CLASS". All roads will then be formatted as per the "DefaultSymbol_Color" value.

417
www.mixtelematics.com

417
 418

4.16 Fleet Manager GPS Log Viewer Extension

© 2008 MiX Telematics | Updated 2008/07/04

Introduction
The purpose of this document is to describe how to analyse GPS data and manage Locations using the Fleet Manager Client
application software and the “Fleet Manager GPS Log Viewer” Extension. For detailed information on all Log Viewer features,
please consult the Log Viewer Help (from the Help, Contents menu of the Log Viewer Main Window or open the FMGPSHelp.
chm file located in the folder where the Log Viewer extensions was installed).

The document covers the following GPS Log Viewer Extensions:

· Regional Map Viewer

Note: Mapsets are separate applications and are not included on the Fleet Manager Office CD. For more information,
please visit the Fleet Manager website www.mixtelematics.com.

For information on the use of the GPS Log Viewer extensions for active tracking, refer to the “Fleet Manager Active Events and
Tracking Extension” document.

For more information on managing and viewing Locations (Customer and No-Go Zones for example) without using the Fleet
Manager GPS Log Viewer Extension, see the “Fleet Manager System Tools 1 Extension” document.

Installing and Loading the Extension

The “GPS Log Viewer” Extension is installed by running the “Setup.exe” executable on your GPS Log Viewer CD.

Once installed, the Extension is loaded using the Extension Manager in the Fleet Manager Client application. It can be configured
to load automatically at start-up by checking the box next to the “GPS Log Viewer” item in the list of available Extensions. The
extension must be registered before it can be loaded. Please refer to the FM GPS Log Viewer Overview & Licensing section at
the end of this document.

GPS Log Display Options

The Extension adds an item to the list of loaded extensions on the Extensions tab of the Options dialog.

418
www.mixtelematics.com

418
 419

Double clicking the item, or selecting it and clicking the Show Options button, displays the Extension’s Display Options dialog.
This dialog is also accessible from the Extension’s Criteria Wizard. This will be described in more detail later in this document.

Options Dialog
The Options dialog allows you to specify which points to display on the map, and how the Viewer should display them. Different
icons can be selected to represent different User and Default events, as well as Start, End and Route Log points. You can also
choose to show connecting lines between Log points, and change the line colour. This makes it easier to distinguish between
overlapping trips.

Note: The options you specify in this dialog are used as the default display options in the Extension’s Criteria Wizard, but can be
overridden in the Criteria Wizard at the time of generating a map.

419
www.mixtelematics.com

419
 420

Events Tree
Double click an item in the Events tree, or select it and click the Change Icon button. This displays the Select An Icon dialog that
allows you to pick an icon from the default font set.

420
www.mixtelematics.com

420
 421

Customise font, colour and style

You can select from any font on your system and change icon size, colour and style to obtain an icon that best suits the particular
point.

Advanced Options

421
www.mixtelematics.com

421
 422

By clicking the Advanced button on the GPS Log Viewer Display Options window, you can define advanced filters to be applied to
the GPS logs when plotting them on the map. These filters generally determine the accuracy of the points displayed.

· HDOP

HDOP is a measure of positional accuracy of GPS points. A lower HDOP indicates a higher accuracy.

· Number of Satellites

The number of satellites detected by the GPS unit when the point was recorded influences accuracy. A minimum of 4 satellites is
required for a three-dimensional fix. More satellites usually constitute higher positional accuracy.

· Age of Reading

When the GPS unit is unable to obtain an accurate fix, it saves the previous accurate position, as well as the time since last
accurate position (age of reading). By setting the maximum age of reading to zero, you exclude any points that are inaccurate
according to the GPS’s factory set criteria.

· Layer Offset

The Layer Offset values allows you to position inaccurate layers with a constant position offset error, in order to have them match
up trip log points. For the supplied map layers, leave these settings at the default values.

Displaying GPS Logs (Passive Tracking)

The Criteria Wizard

The Extension makes use of the familiar Criteria Wizard, allowing you to select the information you would like displayed on the
map. The Criteria Wizard filters the GPS data in the FM database based on your selection and displays the resultant points on
the map in the Viewer.

Plotting GPS Logs from the Activity Timeline

The Extension adds items to the menu bar and tool bar of the Activity Timeline. When any of these items are selected, the GPS
logs for the selected trip(s) are plotted. Events displayed on the Timeline are automatically selected for display on the map.

422
www.mixtelematics.com

422
 423

Accessing the Extension's Criteria Wizard

The Extension adds items to the menu bar, tool bar and right-click menu of the main program. When any of these items are
selected, the Extension’s Criteria Wizard is launched:

· Select Reporting – Driver/Vehicle Reports – Plot GPS Logs from the main menu:

· Or select a Driver, Vehicle or Reporting Group in the Tree View or List View window of the main program window and then click
the Extension Icon in the tool bar:

Selecting GPS data to display in the Viewer

Depending on your selection and method used above, the Extension’s Criteria Wizard is displayed, with certain pre-selected
settings. The last pane of the Criteria Wizard has a More Options button that displays the Extension’s Display Options dialog. The
settings you specified in the Options dialog will be used as default settings. You can change these default settings at this point to
suit your requirements. The Advanced Options form is also available at this stage, allowing you to control the filtering of GPS
data.

Step 1: Select the Vehicle, Driver, Site or Reporting Group

423
www.mixtelematics.com

423
 424

Step 2: Select the time period

Step 3: Select Default and User Events

424
www.mixtelematics.com

424
 425

Step 4: Save selection to Criteria file and/or set Display Options

All of the parameters specified in the Criteria Wizard can be saved in Criteria Files by clicking the Save button, allowing you to
easily reproduce maps with your specific preferences.

After clicking the Finish button in Step 4 of the Criteria Wizard, the GPS data is filtered based on the selected criteria, and the
required GPS Logs are exported to the Viewer. The Viewer will automatically load and display the data on a street level map. If
the Viewer is already open, a new instance of the Viewer will be loaded when you click Finish.

Showing the Map without plotting GPS logs

To use the Viewer functions, for example while managing locations, it is not always necessary to plot GPS logs. To load the
Viewer without going through the Criteria Wizard, select the “Show Map” item under the View menu of the main program window:

425
www.mixtelematics.com

425
 426

or select the corresponding tool button:

Main Program Window

426
www.mixtelematics.com

426
 427

You will spend most of your time in the GPS Log Viewer working with the main program window, which has the following
components:

· Menu Bar

The menu bar provides access to all the functions of the software.

· Context Menu

While the mouse pointer is hovered over Log Points or Locations, click the right mouse button.

The context menu provides access to some of the Log Point functions of the software.

· Tool Bars

The tool bars provide access to the most commonly used features of the software.

· Layer Legend

427
www.mixtelematics.com

427
 428

A legend tool on the left of the main window provides a list of all loaded map layers. You can move layers up or down in the layer
hierarchy by dragging and dropping layer items in the Legend. Note that the legend is locked by default to prevent accidental re-
ordering or removing of layers. To unlock the legend, uncheck the Lock Map Legend item under the Layers menu.

It is also possible to resize the Legend by dragging its right-hand border, and to show or hide the Legend by selecting the Legend
item under the View menu.

· Scale Bar and Status Bar

At the bottom of the Viewer window, the Scale Bar and Status Bar respectively indicate the scale of the current map display and
information on the curser location on the map.

Viewer Window
The map is displayed inside the Viewer window. The map can be panned by holding down the right mouse button while dragging
the map display. You can zoom in by dragging a rectangle (with the left mouse button pressed) inside the Viewer window.
Zooming out is accomplished by holding down the Shift key while clicking the left mouse button. You can also zoom to a specific
point by right clicking on the point and selecting Zoom to Point from the drop down menu. The same drop down menu allows you
to view detail for a point by clicking selecting Point Detail

428
www.mixtelematics.com

428
 429

Viewer Functions

The Viewer provides various functions to help analyse GPS log points and manage Locations. Some of these functions are
described below.

Locations

Circular, rectangular and polygonal Locations in the Fleet Manager system can be maintained from the Fleet Manager System
Tools 1 extension, or added directly from the Viewer.

Add a Location

To add a location, select the appropriate location shape item from the Location menu:

or click the corresponding tool bar item and follow the instructions:

Once the location is drawn, fill in the Location name, type, address and other details on the Add New Location dialog:

429
www.mixtelematics.com

429
 430

Remove a Location

To remove a Location, click the Delete Location menu or tool bar button. To pan the map to a specific Location, select it from the
Go To Location drop down box.

Show Detail

To view detail for a specific Location, hover the mouse over the point. The mouse pointer will change to display an information
icon. Click the right mouse button and select Show Detail from the context menu:

Street Sections

New street sections can be added for areas without detailed street level maps. To add a street section, click the Add New Street
Section item under the Edit menu, or click the tool button:

Log Point Detail

To view detail for a specific GPS log point, hover the mouse over the point. The mouse pointer will change to display an
information icon. Click the right mouse button and select Show Detail from the context menu:

430
www.mixtelematics.com

430
 431

To view a complete list of Log Points for a specific vehicle, select List All Logs from the context menu

To pan the map to a specific log point, select it in the list and click the Zoom To button. To pan the map to the last log point for a
specific vehicle, select the vehicle from the Go To Vehicle drop down box.

Address Search

You can search the local address database for street names. This enables you to quickly locate the position of a street on the
map. To open the Find Street Address dialog, either select the Find Address menu item under the Edit menu or click the Find
Address tool button. Type the name of the street you want to search for into the text box, then click the Find button. This executes
the search and displays all relevant streets in the list box.

431
www.mixtelematics.com

431
 432

Now simply select the required street in the list box and click the Locate on Map button. The map display will zoom to the location
of the street, and will place a Cross icon onto the map.

Map Layers and Files

One of the powerful features of the Viewer is the ability to move, load and unload layers to suit your particular requirements.
When the Viewer starts up for the first time, a default set of layers are loaded automatically. You can then load new layers or
remove loaded layers to suit your area and map view preference.

Loading Layers

To load new layers into the Viewer, either select the Add Layer menu item under the Layers menu or click the Add Layer tool
button.

This will display the standard File Open dialog. Select the file (map layer) type from the drop down box and find the particular file
on the drive. Then click the Open button to add the new layer to the Viewer.

Supported map file types

File Type Comments

ESRI Shape (*.shp) One of the industry standards for geographic data, these consist of a set of three files - shape file (.
shp), index file (.shx) and dbase file (.dbf) and could also include a projection file (.prj). To display
properly in the Viewer, make sure that your Shape files are in WGS84 geographic coordinates
(decimal degrees).

CAD (*.dwg, *.dxf) Digital eXchange Format and AutoCAD Drawing Database, these are industry standards for CAD
files and allow any CAD file saved in geographic units to be loaded into the Viewer

VPF (*.pft, *.lat, *.aft, *. Vector Product Format, this is the U.S. Department of Defence military standard for large geographic
tft) databases.

Standard Images (raster The following raster files are supported and will display inside the Viewer, provided it has
files) georeferencing information in its header or there is a corresponding world file. *.bmp, *.dib, *.tif, *.tff,
*.tiff, *.jpeg, *.jpg, *.bil, *.bip, *.bsq, *.gis, *.lan, *.rlc, *.sid, *.sun, *.rs, *.ras, *.svf, *.img, *.ovr, *.l, *.ntf

432
www.mixtelematics.com

432
 433

Note: Image layers are added to the bottom of the layers hierarchy. Other map layers might hide the newly added image layer.
To make it visible, move it up in the hierarchy using the Legend Tool.

When adding CAD layers, the Viewer will prompt you to select which part of the CAD file to load. The viewer can only load one
feature type at a time. Select the feature type and press the Add Layers button.

Removing Layers

To remove a layer from the Viewer, first select the layer in the Legend and then either select the Remove Active Layer menu item
under the Layers menu or click the Remove Layer tool button. To remove all loaded layers, select the Remove All Layer menu
item under the Layers menu. Note that the Remove Layer function is locked by default to prevent accidental removing of layers.
To unlock the function, uncheck the Lock Map Legend item under the Layers menu, and then select the layer to be removed.

Saving Layer Layout

To save your current layer setup, either select the Save Layout menu item under the File menu or click the Save tool button.
When the Viewer is loaded, the last saved layer layout is used to determine which layers to load and in what order.

Supplied Map Layers

The Fleet Manager Map Dataset will be installed with your extension. Look for the data under the "Maps" folder where your
extension was installed. When the extension starts for the first time, it will attempt to load some default layers from this folder.
You can also move the map files to a different folder or drive. The extension will prompt you to point to the new location at
startup.

Please refer to the Log Viewer Help, Advanced Topics, FMData Map Layers for more detail on the map layers supplied with your
extension.

FM Regional Map Viewer

Custom Layers Setup

ESRI Shape file layers supplied by third-party vendors can be opened by the Viewer, as discussed in the Map Layers and Files
section. These will be loaded with random, unformatted colours and without labels unless the Log Viewer is set up to recognize
these files:

433
www.mixtelematics.com

433
 434

If you are using the regional version of the Map Viewer (no Fleet Manager maps installed), use the Setup feature to edit your
custom layers for the correct colour and label display:

1. Open the extension's Display Options and click on the Setup button.

This opens the Format Setup File dialog:

This dialog is used to edit the setup file (DO NOT EDIT LayerFormat_Setup.lvs manually) and gives information on what changes
are required to the layer's .DBF files. This dialog can also be used to georeference image files (an alternative to the procedure
described in Georeferencing Image Files section.

2. Simply load a shape or raster (image) layer using the Open or Image buttons respectively. Then select the appropriate layer
type from section 2 of the dialog or, in the case of raster images, follow the on-screen prompts.

3. For the selected shape file layer, read the text in section 3 of the dialog carefully. Copy this text to a single text document for
later reference.

4. When all layer types are configured properly, click the OK button. This saves the new LayerFormat_Setup.lvs file.

5. Close the Setup dialog and make the required changes to the layer .DBF files as described in your text document.

6. Load the layers into the Map Viewer and confirm that the formatting (feature colours and labels) is correct.

434
www.mixtelematics.com

434
 435

If you do not see a Setup button on the Options dialog, you can still configure your custom layers to be formatted like one of the
standard FM layers supplied with your extension.

1. Decide which FM layer TYPE best suits your custom layer's type. The Shape file can be a point, area or line type layer. If your
custom layer contains street data for example, it will match the FM _roads layers best.

2. Run "Regedit" from Start -> Run and locate the HKEY_LOCAL_MACHINE\SOFTWARE\Data Pro Development (Pty) Ltd\Fleet
Manager\Extensions\FMGPSCIS8\Settings folder. Add your custom layer's name to the appropriate string value. For example,
add your road layer's name to the "ArterialsLayers" or "RoadsLayers" (depending on what zoom level you want to view it). Note
the position of commas and spaces in this string.

3. Now all that's left to do is change your custom layer's .dbf file to match the structure of the corresponding FM layers. Locate
one of the .lvf files installed by the Log Viewer's install set (this should be in the same where the extension was installed). Open
one of these files with a text editor like Notepad. This file contains the information needed to format your layer to match a specific
Viewer and Layer type. You have to change your layer to this format. For the _roads layer example:

A. Locate ## StreetLabel ##. Note "SA_Field=Name". This means your roads layer's .dbf file must contain a column named
"Name" that contains the road descriptions/names. Use Excel to edit your Roads.dbf accordingly (be careful not to resize the
column widths - Excel seems to throw away parts of strings when doing this...)

B. Locate ## SA_MinorOuter ##. Note the "Field=CLASS". Again your roads.dbf should contain a roads class column that
contains the road types as specified ("FREEWAY", "NATIONAL", etc.) if the DBF does not contain road classes, rename another
text column to "CLASS". All roads will then be formatted as per the "DefaultSymbol_Color" value.

FM GPS Log Viewer Overview & Licensing

What is FM GPS Log Viewer?

As the name implies, it is an FM Software extension that enables a user to plot (on a map of country or region) the positions as
logged by vehicles fitted with an FM 200 and above, plus a GPS. As an FM Extension to the software, you must have a licensed
installation of the software before you can load this extension.

What does the price include?

Included is the FM GPS Log Viewer Extension software, all the vector maps for use with the product and 1 year FM Upgrade+
(upgrade protection for this extension).

Multi User Sites

This product is licensed per seat (computer user) and not per vehicle. There are single packs and 5-user packs to cover the
licensing of the computers the product is loaded onto. For example if you have a client that wants to load the Log Viewer onto 4
computers it would be most economical to purchase a 5 pack. If you want to load it onto 10 computers purchase 2 x 5 packs, and
so on.

Pricing

Please contact your FM Dealer for the latest pricing and FM Upgrade+ registration of the GPS Log Viewer Extension for your
country or region.

435
www.mixtelematics.com

435
 436
4.16.1 Fleet Manager GPS Log Viewer for MapPoint Extension

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The purpose of this document is to describe how to analyse GPS data using the Fleet Manager Professional application software
and the “GPS Log Viewer for MapPoint” Extension. Please consult the “Fleet Manager GPS Functionality” document for general
information on GPS hardware, device driver and data recording configuration. For detail on the use of Viewer extensions in active
tracking and location management, refer to the “Fleet Manager Active Events and Tracking Extension” and “Fleet Manager
System Tools 1 Extension” documents respectively.

Note: You will require Microsoft’s MapPoint 2002 or MapPoint 2004 (either North America or Europe versions), installed and
registered on your computer in order for the GPS Log Viewer for MapPoint Extension to function properly.

Installing and Loading the Extension

To install the extension, run the Fleet Manager Professional installation program and select the Europe or North America version
applicable to your MapPoint version under the Fleet Manager Extensions section (Custom setup). It is advisable not to have the
Fleet Manager Client application open whilst installing.

Once installed, the Extension is loaded using the Extension Manager in the Fleet Manager Professional application. It can be
configured to load automatically at start-up by checking the box next to the “GPS Log Viewer for MapPoint” item in the list of
available Extensions.

Specifying MapPoint Display Options

The Extension adds an item to the list of loaded extensions on the Extensions tab of the Options dialog.

436
www.mixtelematics.com

436
 437

Double clicking the item, or selecting it and clicking the Show Options button, displays the Extension’s Display Options dialog.
This dialog is also accessible from the Extension’s Criteria Wizard. This will be described in more detail later in this document.

The Options dialog allows you to specify which points to display on the map, and how MapPoint should display them.

· Different icons can be selected to represent different User and Default events. (Double click an item in the Events tree, or
select it and click the Change Icon button.)

· The “Show information popups” check boxes allow you to automatically display point information when MapPoint displays the
GPS log. This is especially useful for quickly finding a sub trip start or endpoint.

· The “Use the same icon for all points” checkbox allows you to quickly display a GPS log using the same icon for all points. The
process of loading and displaying logs in MapPoint is substantially faster using this option.

· Use the Location Display Options to define how Locations and Location labels are displayed.

437
www.mixtelematics.com

437
 438

Note: The options you specify in this dialog are used as the default display options in the Extension’s Criteria Wizard, but can be
overridden in the Criteria Wizard at the time of generating a map.

438
www.mixtelematics.com

438
 439

By clicking the Advanced button, you can define advanced filters to be applied to the GPS logs when plotting them on the map.
These filters generally determine the accuracy of the points displayed.

· HDOP

HDOP is a measure of positional accuracy of GPS points. A lower HDOP indicates a higher accuracy. The number of satellites
detected by the GPS unit when the point was recorded influences accuracy. A minimum of 4 satellites is required for a three-
dimensional fix. More satellites usually constitute higher positional accuracy.

· Age of Reading

When the GPS unit is unable to obtain an accurate fix, it saves the previous accurate position, as well as the time since the last
accurate position (age of reading). By setting the maximum age of reading to zero, you exclude any points that are inaccurate
according to the GPS’s factory set criteria.

439
www.mixtelematics.com

439
 440

Displaying GPS Logs in MapPoint

The Extension makes use of the familiar Criteria Wizard, allowing you to select the information you would like displayed on the
map. The Criteria Wizard filters the GPS data in the Fleet Manager database based on your selection and displays the resultant
points on the map in MapPoint.

Accessing the Extension’s Criteria Wizard

The Extension adds items to the menu bar, tool bar and right-click menu of the main program window as well as the menu bar
and tool bar of the Activity Timeline. By selecting any of these items, the Extension’s Criteria Wizard is launched.

Select Reporting – Driver/Vehicle Reports – Plot GPS Logs with MapPoint from the main menu:

Or select a Driver, Vehicle or Reporting Group in the Tree View or List View window of the main program window and then click

the Extension Icon in the tool bar:

Alternatively, select a sub trip or time range on the Activity Timeline and then select View – Plot GPS Logs with MapPoint from
the Timeline’s menu bar or click the Extension Icon in the Timeline’s tool bar:

Selecting GPS data to display in MapPoint

Depending on your selection and method used above, the Extension’s Criteria Wizard is displayed, with certain pre-selected
settings. From the Activity Timeline for example, the Criteria Wizard is automatically populated with the selected vehicle and date/
time range. Events displayed on the Timeline are automatically selected to display on the map. These settings can be overridden.
The last pane of the Criteria Wizard has a More Options button that displays the Extension’s Display Options dialog. The settings
you specified in the Options dialog will be used as default settings. You can change these default settings at this point to suit your
requirements. The Advanced Options form is also available at this stage, allowing you to control the filtering of GPS data.

Step 1: Select the Vehicle, Driver, Site or Reporting Group

440
www.mixtelematics.com

440
 441

Step 2: Select the time period

Step 3: Select Default and User Events

441
www.mixtelematics.com

441
 442

Step 4: Save selection to Criteria file and/or set Display Options

All of the parameters specified in the Criteria Wizard can be saved in Criteria Files by clicking the Save button, allowing you to
easily reproduce maps with your specific preferences. The last pane of the Criteria Wizard has a More Options button that
displays the Extension’s Display Options dialog. The settings you specified in the Options dialog (as described in Specifying
MapPoint Display Options above) will be used as the default settings. You can change these default settings at this point to suit
your requirements. The Advanced Options is also available at this stage, allowing you to control the filtering of GPS data.

442
www.mixtelematics.com

442
 443

After clicking the Finish button in Step 4 of the Criteria Wizard, the GPS data is filtered based on the selected criteria, and the
required GPS Logs are exported to MapPoint. MapPoint will automatically load and display the data on a street level map. Any
Locations defined using the Fleet Manager System Tools 1 Extension will also be drawn on the map. Note that moving the
Location shapes or their labels will not change the corresponding Location in the FM system. Editing Locations must be done
from the Fleet Manager System Tools 1 Extension.

Note: The accuracy of displayed logs on the map is dependant on the positional accuracy of the GPS data, as well as the
positional accuracy of the actual map. If the points on the map are not displayed on the road as expected, try adjusting the filters
using the Advanced Options dialog, i.e. lower the HDOP value, increase the number of satellites value and/or lower the age of
reading. Under most circumstances, the default settings should be adequate. MapPoint maps are fairly accurate, especially in
major metropolitan areas. There are however many inaccurate sections on the maps, for example curved on- and off-ramps,
smaller towns etc.

Inside Microsoft MapPoint

Microsoft’s MapPoint GIS software includes functionality for importing customer data, defining points of interest, displaying route
points, planning and optimising routes, printing driving directions and much more. Please refer to your MapPoint documentation
for more information on these functions.

443
www.mixtelematics.com

443
 444
4.16.2 Mapping with Google Earth

© 2008 MiX Telematics | Updated 2008/05/07

Summary
Users can now track their FM vehicles on Google Earth® maps.

The user can configure their Fleet Manager GPS Log Viewer or FM Map Set extension to write any GPS Logs currently plotted
( both passive and active logs) to a Google Earth® data file. The running Google Earth® application linked to this file, will update
at set intervals, showing the user the latest GPS logs as icons on the Google Earth® map:

Set Up
1. Install the latest Fleet Manager GPS Log Viewer or FM Map Set extension off the FM8 CD.

2. In the Viewer’s Options, click the Advanced Options button and turn on the "Export Logpoints to GE ..." option.

444
www.mixtelematics.com

444
 445

3. In the FM Main Window, open Active Tracking and plot one or more vehicles on the map (or plot a passive GPS log from the
Activity Timeline). This will create the .KML file in the folder specified in the Advanced Options.

4. Open Google Earth®, and create a new Network Link by right-clicking My Places in the places tree.

5. Point it to the "FMGELogs.kml" file in the FM directory and set a Time-based Refresh interval.

445
www.mixtelematics.com

445
 446

6. This will only have to be done once. Whenever the user has Google Earth® running they will be able to see the last set of
active/passive GPS logs plotted on their Google Earth® Map.

7. Click on the blue Logpoint links in the places tree to view detail. Double-click the link to fly towards a Logpoint. Double-click the
icon to get the information popup.

446
www.mixtelematics.com

446
 447

4.17 Fleet Manager System Tools 1 Extension

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The Fleet Manager System Tools 1 Extension is designed to provide system functionality that may not be required by all users of
the Fleet Manager software. The version of the System Tools Extension shipped with the latest Fleet Manager Professional
provides a facility to maintain currency, location, route and contact information.

Location information is required for location-based events for vehicles fitted with GPS devices and when using the Fleet Manager
Location Reports Extension or the Fleet Manager Active Tracking and Messaging Extension.

Locations can be defined graphically (visually) on the map using the Fleet Manager GPS Log Viewer or FM Map Set Extension.

Route information is used in the Fleet Manager Active Tracking and Messaging Extension when assigning a list of location
addresses to jobs, and in the Fleet Manager Location Reports Extension to plan trips by assigning a list of locations (route) these
to a vehicle.

Contact information is required for keeping track of customer contact numbers and when sending text messages to contacts via
the Fleet Manager Active Tracking and Messaging Extension.

Currency information is only required if you wish to enter fuel or vehicle service transactions with multiple currencies, and/or when
using the Fleet Manager Vehicle Costing Extension.

FM Object Finder is used to search for objects (sites, vehicles, driver, etc.) in the FM database.

This document describes how to install and use the Fleet Manager System Tools 1 Extension.

Installing and Loading the Extension

To install the extension, run the Fleet Manager Professional installation program and select System Tools 1 under the Fleet
Manager Extensions section. It is advisable not to have the Fleet Manager Client application open whilst installing.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the System Tools 1 item.

447
www.mixtelematics.com

447
 448

Menus and Dialogs

Edit Menu
The Extension adds menu items to the Edit menu of the Fleet Manager Client Currency
application’s Main window:
Currency data is used in when capturing fuel and
vehicle service history transactions, as well as by
the Fleet Manager Vehicle Costing Extension.

For more information on Currency Maintenance

Locations

Location data is used in the Fleet Manager Active

Tracking and Messaging Extension when
assigning location addresses to jobs, and by the
Fleet Manager Location Reports Extension to
relate trip data to locations.

For more information on Locations

Contacts

Contact information is required for keeping track

of customer contact numbers and when sending
text messages to contacts via the Fleet Manager
Active Tracking and Messaging Extension.

For more information on Contacts

Routes

448
www.mixtelematics.com

448
 449

A route is a set of locations. Route data is used in

the Fleet Manager Active Tracking and Messaging
Extension when assigning a list of location
addresses (route) to jobs, and in the Fleet
Manager Location Reports Extension to plan trips
by assigning a list of locations (route) these to a
vehicle.

For more information on Routes

Find

Previously loaded as a separate extension, this

function is used to search for objects (sites,
vehicles, driver, etc.) in the FM database.

For more information on FM Object Finder

Tool bar
Currency
The extension also adds tool-buttons to the Extension Toolbar of the Fleet
Manager Client application’s Main window:
Locations

Routes

Contacts

Find

Locations

Location data is used in the Fleet Manager Active Tracking and Messaging Extension when assigning location addresses to jobs,
and by the Fleet Manager Location Reports Extension to relate trip data to locations. Locations are displayed on the maps of the
GPS Log Viewer or FM Map Set extension, and can also be used in location based events. The System Tools 1 Extension
provides a facility to maintain location records.

How to access Locations Dialog

· The Extension adds menu items to the Edit menu of the Fleet Manager Client application’s Main window

· The extension also adds tool-buttons to the Extension Toolbar of the Fleet Manager Client application’s Main window

Click on the Locations menu or tool button to open the Locations dialog:

449
www.mixtelematics.com

449
 450

This dialog can be used to Add, Edit, Delete, Import and Export Location information, as well as to maintain Location Type
Information.

Click on the Type button to open the Type Editor dialog.

Up to four location types can be defined. Each location type has a unique colour, used to display locations of that type on the
map. Double click on a location type to change its description.

Click the Add or Edit button on the Locations dialog to display the Add/Edit Location dialog:

General tab

Enter the following mandatory details for the location:

450
www.mixtelematics.com

450
 451

· Description – a unique name for the location

· Type – select the appropriate type for the location.

· Location Shape – the geographical co-ordinates of a location that define a circle, rectangle or polygon shape. These can be
entered manually, or defined visually using the GPS Log Viewer or FM Map Set Extension (this option will only be available if
you have the GPS Log Viewer or FM Map Set Extension installed and loaded).

To define a location shape visually using the GPS Log Viewer or FM Map Set, check the “Use a Log Viewer to define the location
on a map” checkbox and click the Edit button. The GPS Log Viewer / FM Map Set map window will be displayed

GPS Log Viewer for MapPoint

Resize and/or move the existing shape, or click the New button to draw a new shape. Click OK to save.

451
www.mixtelematics.com

451
 452

Other GPS Log Viewers and Map Sets

Click any of the location shape buttons, draw a new shape on the map and then click the Save button.

452
www.mixtelematics.com

452
 453

Manually

To define a location shape manually, uncheck the “Use a Log Viewer to define the location on a map” checkbox and click the Edit
button. The Define Location dialog for the selected shape will be displayed:

· Circle Shape

Define the circle’s centre point coordinates, as well as the circle’s radius in meters.

453
www.mixtelematics.com

453
 454

· Rectangle Shape

Define the upper left and lower right point’s coordinates.

454
www.mixtelematics.com

454
 455

· Polygon Shape

Define the polygon shape by adding coordinates to the list. The coordinates can be ordered using the Up and Down arrows.

455
www.mixtelematics.com

455
 456

· Address tab

Enter the relevant address details for the location, or click the Find button (Fleet Manager GPS Log Viewer for MapPoint installed)
and use the viewer’s Find dialog:

456
www.mixtelematics.com

456
 457

457
www.mixtelematics.com

457
 458

· Other tab

Enter the contact and other details for the location in the relevant fields:

458
www.mixtelematics.com

458
 459

Importing Locations

As an alternative to manually entering the above data, you can import a list of Locations contained in a text file (Comma
Separated Values or CSV). The file must have the columns described below. Use the export function to create a template file:

Note that Location.csv file can be edited using Microsoft Excel (use the Import Data function with comma delimiter) or any text
editor application. Remember to save the file back into .CSV format.

The Location.csv file has the following columns:

· LocationID
Any numeric number (used to reference import errors)

· LocationName
A unique description for the location (mandatory)

· Details
Address and Other details associated with the location

459
www.mixtelematics.com

459
 460

These must be in the following format:

"Street=16 Some Street ;City=Some City ;Province=Some Region ;Zip=1234 ;Country=South Africa ;EMail=MyMail@Home.
com ;HomePhone=(021) 12345 ;WorkPhone=(021) 883 2288 ;WorkFax=(021) 883 2288 ;Comments=Some comments about
this location ;MobilePhone=082 12345 ;"

· LocationType
Type of Location (mandatory)

This must be a number from 1 to 4:

Blue = 1 (Customers)
Red = 2 (No-go zones)
Yellow = 3 (Sites)
Green = 4 (Other locations)

· ShapeType
Type of Location shape (mandatory)
Circle = 0
Polygon = 1 (NOTE: These require an XML file containing polygon points)
Rectangle = 2

· PointLongitude
The longitude value (use | for decimal separator) of the centre point (mandatory for circle (ShapeType = 0))

· PointLatitude
The latitude value (use | for decimal separator) of the centre point (mandatory for circle (ShapeType = 0))

· PointRadius
The radius value (use | for decimal separator) of the circle in meters (mandatory for circle (ShapeType = 0))

· UpperLeftLongitude
The longitude value (use | for decimal separator) of the Upper Left point (mandatory for both circle and rectangle)

· UpperLeftLatitude
The latitude value (use | for decimal separator) of the Upper Left point (mandatory for both circle and rectangle)

· LowerRightLongitude
The longitude value (use | for decimal separator) of the Lower Right point (mandatory for both circle and rectangle)

· LowerRightLatitude
The latitude value (use | for decimal separator) of the Lower Right point (mandatory for both circle and rectangle)

Exporting Locations

You can export a list of Locations to a text file (Comma Separated Values or CSV). If the list includes polygon type locations, an
XML file containing polygon point coordinates is also created. These files can either be used as a template for importing
locations, or to extract the Fleet Manager Locations data for use in other applications or another FM database.

Routes
A route is a set of locations. Route data is used in the Fleet Manager Active Tracking and Messaging Extension when assigning a
list of location addresses (route) to jobs, and in the Fleet Manager Location Reports Extension to plan trips by assigning a list of
locations (route) these to a vehicle. The System Tools 1 Extension provides a facility to maintain route records.

How to access Routes Dialog

· The Extension adds menu items to the Edit menu of the Fleet Manager Client application’s Main window

· The extension also adds tool-buttons to the Extension Toolbar of the Fleet Manager Client application’s Main window:

460
www.mixtelematics.com

460
 461

Click on the Routes menu or tool button to open the Routes dialog:

This dialog can be used to Add, Edit, Delete, Import and Export Route information.

Click the Add or Edit button to display the Add/Edit Route dialog.

Enter a valid Route Description. Consider using descriptive names that indicate the direction (start and end destination) of the
route. This will be useful when choosing the correct route from a route list for Jobs and Route Planning.

Locations can be added to the Route Points list using the Add button. Clicking the Add button opens the Locations list. Select one
or more Locations from the list and click the Select button. Text entered into the Find box on the Routes dialog is used to filter the
list of available Locations for either Location description or zip/postal code properties. If only one Location matches the Find text,
the Location is added automatically. If no match is found, the Add Location dialog is opened automatically.

Route points can be re-ordered using the Up and Down arrows, and can be deleted from the list by clicking the Delete button.

Contacts
Contact information is required for keeping track of customer contact numbers and when sending text messages to contacts via
the Fleet Manager Active Tracking and Messaging Extension. The System Tools 1 Extension provides a facility to maintain
contact records.

461
www.mixtelematics.com

461
 462

How to access Contact Dialog

· The Extension adds menu items to the Edit menu of the Fleet Manager Client application’s Main window

· The extension also adds tool-buttons to the Extension Toolbar of the Fleet Manager Client application’s Main window:

Click on the Contacts menu or tool button to open the Contacts dialog:

This dialog can be used to Add, Edit or Delete Contact information. Click the Add or Edit button in the Contacts dialog to display
the Add/Edit Contact dialog:

To clear a contact telephone number, click the Clear Number button

To change a contact phone number, click the ellipsis button

This will open the Contact Number dialog:

462
www.mixtelematics.com

462
 463

Use this dialog to select a country code and enter a valid telephone number.

NOTE: For sending text messages to contacts via the Fleet Manager Active Tracking and Messaging Extension, a valid mobile
phone number is required.

Currency Maintenance
Currency data is used in when capturing fuel and vehicle service history transactions, as well as by the Fleet Manager Vehicle
Costing Extension. The System Tools 1 Extension provides a facility to maintain currency records.

How to access Currency Dialog

· The Extension adds menu items to the Edit menu of the Fleet Manager Client application’s Main window:

· The extension also adds tool-buttons to the Extension Toolbar of the Fleet Manager Client application’s Main window:

Click on the Currencies menu or tool button to open the Currency Maintenance dialog:

This dialog can be used to Add, Edit or Delete currencies. Do not delete a currency if it has been used previously in vehicle fuel
or service history transactions.

When the Add or Edit button is clicked, the Add/Edit Currency dialog is opened.

Mark a currency as the base currency for the system by checking the “This is the base currency” checkbox.

Take care when editing or adding FM Terminal Properties for currencies. A corresponding custom FM Terminal script must be
uploaded to all FM Terminals in the fleet for any change made to these properties to take effect.

463
www.mixtelematics.com

463
 464

FM Object Finder
Previously loaded as a separate extension, this function is used to search for objects (sites, vehicles, driver, etc.) in the FM
database.

How to access FM Object Finder

· The Extension adds menu items to the Edit menu of the Fleet Manager Client application’s Main window

· The extension also adds tool-buttons to the Extension Toolbar of the Fleet Manager Client application’s Main window

Click on the Find menu or tool button to open the Find dialog.

Enter the ID or part of the object name/description and click the Find button.

464
www.mixtelematics.com

464
 465

465
www.mixtelematics.com

465
 466

4.18 Fleet Manager Taxlog Extension

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The Fleet Manager Taxlog Report extension allows the customer to print reports that display trip reports on a per-sub trip basis.
The report also displays a driving reason (entered in from the FM Keypad unit) for each sub trip. The Taxlog report also allows for
various grouping configurations and allows for location data to be displayed in the report. Trip notes can also be entered after-
the-fact by using the activity timeline, and displayed in the Taxlog report.

The Taxlog report displays the following for one or more vehicles:

· The sub trip distance

· The ‘From’ and ‘To’ locations (if the vehicle has GSM installed and locations have been specified)

· Trip notes (if they’ve been entered in from the activity timeline)

· The driving reason

Installing and Loading the Extension

The Extension can be installed by running the Fleet Manager Professional 9 install set, and selecting to install the Taxlog
Extension.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the Taxlog Extension item in the list of available extensions.

Taxlog Report - Options

The 'Options' form can be accessed with the menu option underneath TOOLS.

466
www.mixtelematics.com

466
 467

The ‘Options’ form is used to specify the report output:

The report may be viewed in a variety of formats:

· Display/Hide location names in report

If this is set, the start and end location names of the trip are displayed. These locations are predefined in the Fleet Manager
Professional software.

467
www.mixtelematics.com

467
 468

· Include/Exclude trip notes with driving reason

If this is set, the trip notes can be displayed. Trip notes are entered into the Fleet Manager Professional from the activity timeline.

· Include/Exclude Any of the four driving reasons

Any of the four driving reasons can be excluded from the report

· Group data by Driving Reason OR Group data by Vehicle/Driver

Driving reasons can be grouped either by Driving Reason, or by Vehicle (if a Vehicle Taxlog Report)

Driving reasons can be grouped either by Driving Reason, or by Driver (if a Driver Taxlog Report)

Menu and Dialogs

The Taxlog Report is run from the “Reporting” menu. The Driver Taxlog Report is found under Reporting\Driver Reports\Driver
Taxlog Report:

The Taxlog Report is run from the “Reporting” menu. The Vehicle Taxlog Report is found under Reporting\Vehicle Reports

468
www.mixtelematics.com

468
 469

\Vehicle Taxlog Report:

The Taxlog report requires the user to select the vehicles that are to be displayed, and a date-time range. These are entered
using the criteria wizard.

1) Vehicles

The first frame of the wizard is vehicle selection. Make a selection based on Site, Reporting Group or Vehicle.

2) Time Range

The second frame allows you to enter the time range for the selected vehicles, and the report type. The time range is set from the
previous month to the current day. Other options such as week-to-date and month-to-date may also be selected from the combo

469
www.mixtelematics.com

469
 470

box.

3) Event Selection

The third frame allows you to set the extension-specific options for the report, and save the criteria into a criteria file. This allows
you to apply the same criteria to the report if the report is drawn on a regular basis.

Report Examples
The following report printouts show the various configurations that the report extension can output:

Example 1

470
www.mixtelematics.com

470
 471

Example 2

Example 3

471
www.mixtelematics.com

471
 472

Example 4

472
www.mixtelematics.com

472
 473

4.19 Fleet Manager TCO Driver Data Extension

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
This extension is used to export and report on data that can be used to analyse tachograph (TCO) information, as recorded by an
FM200 or above on-board computer connected to a tachograph device.

Reports range from a detailed report that lists the time spent in each driving mode (driving, resting, active work and passive work)
for the specified drivers and time period, to a summary report that provides totals for the specified drivers and time period.

The extension allows the user to export TCO data in specific formats. New export format specifications can be defined by copying
and editing existing formats.

Installing and Loading the Extension

To install the extension, run the Fleet Manager Professional installation program and select TCO Driver Data Extension under the
Fleet Manager Extensions section. It is advisable not to have the Fleet Manager Client application open whilst installing.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the TCO Driver Data item in the list of available extensions.

Invoking the TCO Driver Data extension

A menu for the extension is added to the Driver Reports menu of the main window:

473
www.mixtelematics.com

473
 474

The right-click menu of drivers or driver reporting groups also provides access to the extension:

In this case the selected driver or group will be highlighted by default when opening the criteria wizard as detailed next.

TCO Data Criteria Wizard

The extension uses the standard criteria wizard from the Fleet Manager Professional interface.

Step 1: Select Drivers, Reporting groups or Sites

Select the drivers required for the report or export by selecting one or more Sites, Reporting Groups or individual drivers. Only the
highlighted driver or reporting group will be selected when the wizard is accessed using the right-click menu.

474
www.mixtelematics.com

474
 475

Step 2: Time Period and Type Report

Specify the period and type of report (Detail, Daily, Monthly or Summary). Only the Detail option applies when exporting TCO data
based on the export formats.

Step 3: More Options

Click on the <More Options> button to define additional criteria options.

475
www.mixtelematics.com

475
 476

Choose whether you would like to produce a report and/or export the data using one of the predefined export formats.

If you chose to export data, you will have several more options to define the export format and destination file as well as choose
what activity codes to export.

476
www.mixtelematics.com

476
 477

Click the <Select File> button, select the folder you wish to export to, enter your filename and select the export format you wish to
use. Click <Save>. This will not yet run/start the export, but only saves your filename and export type at this time.

Choose the options to automatically compress (zip) the output, overwrite the file if it exists, and create the output path if it does
not exist. These options are recommended for automatic schedule exports to run successfully.

Select the activities that you want to include in the export. Specify the minimum activity duration you want to be recognised as an
activity. This option will collate all activities with durations less than the specified minimum into the preceding activity. If you do
not wish to collate short activities then change the minimum duration to 0 (ZERO).

NOTE: Two new activities added to the latest version of the software now include "4 hours driving exceeded" as well as "9 hours
driving exceeded".

Once you have reviewed all your criteria, you can choose to save your criteria, allowing the same report or export to be generated
at a later stage. Click Finish to initiate the report or export.

477
www.mixtelematics.com

477
 478

Reports will be generated before the export starts. Progress will be shown during the generation of the report and the export of
the TCO data.

Successful exports are logged to the export log file FMExport.log in your <Fleet Manager>\ExportFormats sub folder. The log file
can also be viewed from the extension properties as detailed later on.

By clicking the Open Criteria File sub-menu from the Reports menu, you can select and open a criteria file.

478
www.mixtelematics.com

478
 479

You can now also associate Criteria Files with the FMRunExport.exe application. This application allows you to run exports ad-
hoc without the need to run the full FM client application and TCO extension. You may also create shortcuts to FMRunExport and
add the full path of the criteria file to it's command line. You can then run this shortcut from a command scheduler as illustrated
above. Please note that the criteria file itself defines the name of the export format file (SEF file) to use and the name of the
output file. It also defines options for overwriting the output file and compressing it into a zip file.

Sample Report

If you chose the option to produce a report, the extension will process the data and allow you to preview the report before printing
or exporting it.

479
www.mixtelematics.com

479
 480

The reporting engine provides the option to export reports into any of five common formats, namely Comma Separated Values (.
CSV), Microsoft Word (.DOC) , Microsoft Excel (.XLS) , Rich Text Format (.RTF) and Plain Text (.TXT).

To access this report export functionality, select the Export sub-menu from the File menu in the Report Preview window.

Note that exporting report data differs from exporting data using a predefined format as detailed below.

Managing Export Formats

The TCO Driver Data Extension adds functionality that allows the user to maintain various export formats. This requires in-depth
understanding of the desired output format required by the third-party software. This functionality is only intended for advanced
users.

480
www.mixtelematics.com

480
 481

Export formats are managed by accessing this extension’s options via the Options dialog in the Fleet Manager Client application.

General
In the general tab you may configure the default options applicable when exporting data, or edit and define new export formats to
be used. When you click the <Change> button the dialog described above with the Criteria Wizard <More Options> button in
Step 3 is shown.

The original format specification as provided by the vendor may not be edited or deleted. Additional formats can be defined based
on any of the original formats by selecting a base format and copying it. Existing custom formats can be edited, copied or deleted.

The formats are stored as interchangeable ASCII text files in the “ExportFormats” folder beneath the folder where you installed
the Fleet Manager Client application (typically “C:\Program Files\Fleet Manager Professional”).

Export Log
The second tab of the Export Formats dialog displays a log of the most recent export runs.

481
www.mixtelematics.com

481
 482

This log is automatically truncated when it exceeds 64 Kbytes and a backup is created. The log is a simple CSV text file named
TCOExport.log, located in the “ExportFormats” sub folder.

Defining Export Formats

The Export Format Editor provides various tabs for specifying the export format.

General

Use the General tab to specify the 3-character name used as the output file’s extension and the export format’s description.

The field and line delimiters are also specified on this tab. Special mnemonics are used for hidden characters such as {tab} and
{crlf}.

Fields

482
www.mixtelematics.com

482
 483

The Fields tab allows you to select the fields to export. Each export format’s field list may be different from the other. There are
several general field types and the field formats are user-definable. The fields are currently based on the fields defined in the
ElvistDriverData view in the FM database.

The export field order can be changed by moving the highlighted fields up or down.

NOTE: Select multiple fields by holding the CTRL key and clicking on the fields you require, then move the selected fields up or
down in the export order by clicking the Up or Down button.

Several static text fields can also be defined in this tab. For example, you may wish to define a field containing constant
characters to be exported.

In addition, built-in calculated fields can be defined, such as a check sum.

The field format can be selected from a list of defined formats per field type, or it may be user-defined. The field format characters
used here may be affected by the local or regional settings of the operating system and special care should be taken when they
are defined. Field formats are documented in Appendix B below.

Tip: Always check the effect of any format or field order changes by clicking on the Preview tab.

Criteria

The Criteria tab allows you to define the activity code criteria. You may edit the exportable code associated with each of the
activities described in the second column. Select the default activities that will be included in the export file.

483
www.mixtelematics.com

483
 484

Specify the minimum duration that will be counted as activity. Any activity less than the specified period will be collated into the
preceding activity. If you wish to disable filtering based on minimum duration, set this value to 0 (ZERO).

Headers & Footers

Some export formats may require headers and footers to be defined. You may use predefined mnemonics to insert system values
such as date, time etc into the Export records. Mnemonics are evaluated and inserted at export time. Mnemonics are
documented in Appendix A below.

NOTE: An empty line will attach the specified line delimiter to the end of the header and footer. If you don't wish to include a
header or footer at all you must specify so by entering the mnemonic “{none}”.

Preview

The Preview tab is used to visually verify the export format definition. Only the top 5 data records are returned for previewing.

484
www.mixtelematics.com

484
 485

The format is saved at any time when the OK or Apply buttons are clicked.

Appendix A - Mnemonics
Predefined mnemonics can be referenced between curly brackets when specifying the delimiters, field formats, headers or
footers of the export format. The default export processor identifies the following mnemonics:

Mnemonic Description

{none} Empty and will not force a line delimiter – used for voiding headers and footers

{tab} Tab character

{crlf} Carriage return and line feed

{date} Current date in regional format

{time} Current time in regional format

{counter} Sequential line counter starting at 1

{checksum} Hexadecimal checksum of all preceding line characters – for advanced use only

{name} Name of the line processor used

Appendix B - Formats
The format text is used to indicate the exact way that the data should be written to the export file. The format text must always be
tested using the Preview tab and even then, specific conditions in the source data may cause the format feature to produce
unintended results.

Fixed Width Formatting Symbols

There are two ways of specifying fixed width formats. When you simply require numeric data to be preceded (padded) with zeros
up to a specific length, you may use the standard specifications as detailed below. The safer mechanism is to prefix the format

485
www.mixtelematics.com

485
 486

string with an "@" character followed by ‘L’ or ‘R’ to indicate the ‘Left’ or ‘Right’ text justification, then followed by the padding
character, and finally specifying the exact length in digits of the field. The length cannot exceed 8000 characters and only the first
four characters after the padding character will be used.

If the data is larger than that allowed by the maximum width, the output text will be padded with # characters up to the exact width
specified. Take special care with literal text. It is safer to escape ambiguous literals with a backslash (\). Also remember that
mnemonics are only allowed in Static field formats. Mnemonics used in non static fields will not be expanded and will cause
undesired results.

Format Description

@R 20 Right aligned fixed width of 20 characters padded with spaces to the left

@L?100 Left aligned fixed width of 100 characters padded with question marks to the right.

@RX9999 Right aligned fixed width maximum of 8000 characters padded with X to the left

Special Formatting Symbols

If you are formatting a non-localized numeric string, you should use a user-defined numeric format to ensure that you get the look
you want.

If your regional calendar setting is Gregorian and the format specifies date formatting, the supplied expression must be
Gregorian. If the calendar setting is Hijri, the supplied expression must be Hijri.

If the calendar is Gregorian, the meaning of format expression symbols is unchanged. If the calendar is Hijri, all date format
symbols (for example, dddd, mmmm, yyyy) have the same meaning but apply to the Hijri calendar. Format symbols remain in
English; symbols that result in text display (for example, AM and PM) display the string (English or Arabic) associated with that
symbol. The range of certain symbols changes when the calendar is Hijri.

Character Description

None Display the number with no formatting.

No formatting

: Time separator.

In some locales, other characters may be used to represent the time separator. The time separator
divides hours, minutes, and seconds when time values are formatted. The actual character used as
the time separator in formatted output is determined by your system settings.

/ Date separator.

In some locales, other characters may be used to represent the date separator. The date separator
divides the day, month, and year when date values are formatted. The actual character used as the
date separator in formatted output is determined by your system settings.

C Display the date as ddddd and display the time as t t t t t, in that order. Display only date information
if there is no fractional part to the date serial number; or display only time information if there is no
integer portion.

D Display the day as a number without a leading zero (1 - 31).

486
www.mixtelematics.com

486
 487

Dd Display the day as a number with a leading zero (01 - 31).

Ddd Display the day as an abbreviation (Sun - Sat).

dddd Display the day as a full name (Sunday - Saturday).

ddddd Display the date as a complete date (including day, month, and year), formatted according to your
system's short date format setting. The default short date format is m/d/yy.

dddddd Display a date serial number as a complete date (including day, month, and year) formatted
according to the long date setting recognized by your system. The default long date format is mmmm
dd, yyyy.

w Display the day of the week as a number (1 for Sunday through 7 for Saturday).

ww Display the week of the year as a number (1 - 53).

m Display the month as a number without a leading zero (1 - 12). If m immediately follows h or hh, the
minute rather than the month is displayed.

mm Display the month as a number with a leading zero (01 - 12). If m immediately follows h or hh, the
minute rather than the month is displayed.

mmm Display the month as an abbreviation (Jan - Dec).

mmmm Display the month as a full month name (January - December).

q Display the quarter of the year as a number (1 - 4).

y Display the day of the year as a number (1 - 366).

yy Display the year as a 2-digit number (00 - 99).

yyyy Display the year as a 4-digit number (100 - 9666).

h Display the hour as a number without leading zeros (0 - 23).

hh Display the hour as a number with leading zeros (00 - 23).

n Display the minute as a number without leading zeros (0 - 59).

nn Display the minute as a number with leading zeros (00 - 59).

s Display the second as a number without leading zeros (0 - 59).

ss Display the second as a number with leading zeros (00 - 59).

ttttt Display the time as a complete time (including hour, minute, and second), formatted using the time
separator, defined by the time format recognized by your system. A leading zero is displayed if the
leading zero option is selected and the time is before 10:00 A.M. or P.M. The default time format is h:
mm:ss.

487
www.mixtelematics.com

487
 488

AM/PM Use the 12-hour clock and display an uppercase AM with any hour before noon; display an
uppercase PM with any hour between noon and 11:59 P.M.

am/pm Use the 12-hour clock and display a lowercase AM with any hour before noon; display a lowercase
PM with any hour between noon and 11:59 P.M.

A/P Use the 12-hour clock and display an uppercase A with any hour before noon; display an uppercase
P with any hour between noon and 11:59 P.M.

a/p Use the 12-hour clock and display a lowercase A with any hour before noon; display a lowercase P
with any hour between noon and 11:59 P.M.

AMPM Use the 12-hour clock and display the AM string literal as defined by your system with any hour
before noon; display the PM string literal as defined by your system with any hour between noon and
11:59 P.M. AMPM can be either uppercase or lowercase, but the case of the string displayed
matches the string as defined by your system settings. The default format is AM/PM.

0 Display a digit or a zero.

Digit placeholder · If the expression has a digit in the position where the 0 appears in the format string, display it;
otherwise, display a zero in that position.

· If the number has fewer digits than there are zeros (on either side of the decimal) in the format
expression, display leading or trailing zeros.

· If the number has more digits to the right of the decimal separator than there are zeros to the right
of the decimal separator in the format expression, round the number to as many decimal places
as there are zeros.

· If the number has more digits to the left of the decimal separator than there are zeros to the left of
the decimal separator in the format expression, display the extra digits without modification.

# Display a digit or nothing.

Digit placeholder If the expression has a digit in the position where the # appears in the format string, display it;
otherwise, display nothing in that position.

This symbol works like the 0 digit placeholder, except that leading and trailing zeros aren't displayed
if the number has the same or fewer digits than there are # characters on either side of the decimal
separator in the format expression.

. In some locales, a comma is used as the decimal separator. The decimal placeholder determines
how many digits are displayed to the left and right of the decimal separator. If the format expression
Decimal placeholder contains only number signs to the left of this symbol, numbers smaller than 1 begin with a decimal
separator. If you always want a leading zero displayed with fractional numbers, use 0 as the first digit
placeholder to the left of the decimal separator instead. The actual character used as a decimal
placeholder in the formatted output depends on the Number Format recognized by your system.

%
The expression is multiplied by 100. The percent character (%) is inserted in the position where it
appears in the format string.
Percent placeholder

488
www.mixtelematics.com

488
 489

, In some locales, a period is used as a thousand separator. The thousand separator separates
thousands from hundreds within a number that has four or more places to the left of the decimal
Thousand separator separator.

Standard use of the thousand separator is specified if the format contains a thousand separator
surrounded by digit placeholders (0 or #).

Two adjacent thousand separators or a thousand separator immediately to the left of the decimal
separator (whether or not a decimal is specified) means "scale the number by dividing it by 1000,
rounding as needed."

You can scale large numbers using this technique. For example, you can use the format string
"##0,," to represent 100 million as 100. Numbers smaller than 1 million are displayed as 0. Two
adjacent thousand separators in any position other than immediately to the left of the decimal
separator are treated simply as specifying the use of a thousand separator.

The actual character used as the thousand separator in the formatted output depends on the
Number Format recognized by your system.

: In some locales, other characters may be used to represent the time separator. The time separator
separates hours, minutes, and seconds when time values are formatted. The actual character used
Time separator as the time separator in formatted output is determined by your system settings.

/ In some locales, other characters may be used to represent the date separator. The date separator
separates the day, month, and year when date values are formatted. The actual character used as
Date separator the date separator in formatted output is determined by your system settings.

E- E+ e- e+ If the format expression contains at least one digit placeholder (0 or #) to the right of E-, E+, e-, or e
+, the number is displayed in scientific format and E or e is inserted between the number and its
Scientific format exponent.

The number of digit placeholders to the right determines the number of digits in the exponent. Use E-
or e- to place a minus sign next to negative exponents. Use E+ or e+ to place a minus sign next to
negative exponents and a plus sign next to positive exponents.

- + $ ( ) space
To display a character other than one of those listed, precede it with a backslash (\) or enclose it in
double quotation marks (" ").
Display a literal character

\ Many characters in the format expression have a special meaning and can't be displayed as literal
characters unless they are preceded by a backslash. The backslash itself isn't displayed.
Display the next character
in the format string Using a backslash is the same as enclosing the next character in double quotation marks. To display
a backslash, use two backslashes (\\). Examples of characters that can't be displayed as literal
characters are the date- and time-formatting characters (a, c, d, h, m, n, p, q, s, t, w, y, and /:), the
numeric-formatting characters (#, 0, %, E, e, comma, and period), and the string-formatting
characters (@, &, <, >, and !).

"ABC"
To include a string in format from within code, you must use Chr(34) to enclose the text (34 is the
Display the string inside
character code for a double quotation mark).
the double quotation
marks

@ Display a character or a space. If the string has a character in the position where the @ appears in
the format string, display it; otherwise, display a space in that position. Placeholders are filled from
Character placeholder right to left unless there is an ! character in the format string. See below.

489
www.mixtelematics.com

489
 490

& Display a character or nothing. If the string has a character in the position where the & appears,
display it; otherwise, display nothing. Placeholders are filled from right to left unless there is an !
Character placeholder character in the format string. See below.

<
Display all characters in lowercase format.
Force lowercase

>
Display all characters in uppercase format.
Force uppercase

!
The default is to fill from right to left.
Force left to right fill of
placeholders

Named Formats

Instead of using symbols, you may specify standard formats by name. The following table lists the format names you can use.

Named Format Description

General Number Shows numbers as entered.

Currency Shows negative numbers inside parentheses.

Fixed Shows at least one digit.

Standard Uses a thousands separator.

Percent Multiplies the value by 100 with a percent sign at the end.

Scientific Uses standard scientific notation.

General Date Shows date and time if the expression contains both. If the expression is only a date or a time, the
missing information is not displayed.

Long Date Uses the Long Date format specified in the Regional Settings dialog box of the Microsoft Windows
Control Panel.

Medium Date Uses the dd-mmm-yy format (for example, 03-Apr-93).

Short Date Uses the Short Date format specified in the Regional Settings dialog box of the Windows Control
Panel.

Long Time Shows the hour, minute, second, and "AM" or "PM" using the h:mm:ss format.

Medium Time Shows the hour, minute, and "AM" or "PM" using the "hh:mm AM/PM" format.

Short Time Shows the hour and minute using the hh:mm format.

490
www.mixtelematics.com

490
 491

Yes/No Any nonzero numeric value (usually - 1) is Yes. Zero is No.

True/False Any nonzero numeric value (usually - 1) is True. Zero is False.

On/Off Any nonzero numeric value (usually - 1) is On. Zero is Off.

Multiple Formats

A user-defined format expression can have from one to four sections separated by semicolons.

If the format argument contains one of the named formats, only one section is allowed. Fixed length formats are not recognised
as part of a multiple format expression.

If you use The result is

One section The format expression applies to all values.

Two sections The first section applies to positive values and zeros, the second to negative values.

Three sections The first section applies to positive values, the second to negative values, and the third to zeros.

Four sections The first section applies to positive values, the second to negative values, the third to zeros, and the
fourth to Null values.

The following example has two sections: the first defines the format for positive values and zeros; the second defines the format
for negative values.
$#,##0;($#,##0)
If you include semicolons with nothing between them, the missing section is printed using the format of the positive value. For
example, the following format displays positive and negative values using the format in the first section and displays "Zero" if the
value is zero.
$#,##0;;\Z\e\r\o
Examples

The following conversions assume that the country in the Windows Control Panel is set to "English (United States)."

Data Format Result

8315.4 00000.00 08315.40

8315.4 #####.## 8315.4

8315.4 ##,##0.00 8,315.40

315.4 $##0.00 $315.40

7 0.00% 700.00%

"This Is A Test" < this is a test

491
www.mixtelematics.com

491
 492

"This Is A Test" > THIS IS A TEST

1/27/1993 m/d/yy 1/27/93

1/27/1993 dddd, mmmm dd, yyyy Wednesday, January 27, 1993

1/27/1993 d-mmm 27-Jan

1/27/1993 mmmm-yy January-93

1/27/1993 hh:mm AM/PM 07:18 AM

1/27/1993 h:mm:ss a/p 7:18:00 a

1/27/1993 "d-mmmm h:mm 27-January 7:18

1/27/1993 d-mmmm-yy 27-January-93

1/27/1993 d mmmm 27 January

1/27/1993 mmmm yy January 93

1/27/1993 hh:mm AM/PM 08:50 PM

1/27/1993 h:mm:ss a/p 8:50:35 p

1/27/1993 h:mm 20:50

1/27/1993 h:mm:ss 20:50:35

1/27/1993 m/d/yy h:mm 1/27/93 20:50

Multiple Section Examples

Format (format) Positive 5 Negative 5 Decimal .5 Null

Zero-length String 5 -5 0.5

0 5 -5 1

0.00 5.00 -5.00 0.50

#,##0 5 -5 1

#,##0.00;;;Nil 5.00 -5.00 0.50 Nil

$#,##0;($#,##0) $5 ($5) $1

$#,##0.00;($#,##0.00) $5.00 ($5.00) $0.50

492
www.mixtelematics.com

492
 493

0% 500% -500% 50%

0.00% 500.00% -500.00% 50.00%

0.00E+00 5.00E+00 -5.00E+00 5.00E-01

0.00E-00 5.00E00 -5.00E00 5.00E-01

493
www.mixtelematics.com

493
 494

4.20 Fleet Manager Timeline Reports Extension

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The Fleet Manager Timeline Reports Extension provides two additional useful reports:

Daily Timeline Report

This report combines a graphical view of a 24-hour driving period with a trip-by-trip account of distance driven, fuel consumption,
over speeding, over revving, harsh braking, harsh acceleration, percentage of time in green band and idling information for the
specified vehicle and day.

Summary Report

This report provides a single line summary per vehicle of distance driven, fuel consumption, over speeding, over revving, harsh
braking, harsh acceleration, percentage of time in green band and idling information for the specified vehicles and time period.

This document describes how to use the Fleet Manager Timeline Reports Extension.

Installing and Loading the Extension

To install the Extension, run the Fleet Manager Professional 9 installation program. It is advisable not to have the Fleet Manager
Client application open while installing.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the Time Line Reports item.

Menus and Toolbars

Menu

The menus for the extension are added to the Vehicle Reports menu.

494
www.mixtelematics.com

494
 495

The reports are also available from the popup menu when a Site, Vehicle Reporting Group or individual Vehicle is right-clicked:

The Daily Timeline Report is also available when viewing the Activity Timeline in Vehicle mode.

Criteria Wizard

The criteria wizard forms the basis to create the Event Summary Reports and consists of only three steps. Both the Daily
Timeline and the Summary reports use the standard report criteria wizard from the Fleet Manager interface.

Clicking on the appropriate menu item opens the TimeLine Reports wizard:

Step 1 of the Criteria Wizard allows the selection of vehicles based on Site, Reporting Group or individual vehicles.

495
www.mixtelematics.com

495
 496

Step 2 of the Criteria Wizard allows you to specify the date criteria and how much detail you would like to include in your report.

The Daily Timeline Report will default to “Last 7 Days”, unless invoked from the Activity Timeline, in which case it will be the
specific day the Activity Timeline starts on. The Summary report will default to “Last 30 Days”.

Step 3 of the Criteria Wizard allows the criteria to be saved. This will allow the report to be opened using the Open Criteria File
menu option.

Daily Timeline Report

496
www.mixtelematics.com

496
 497

The Daily Timeline Report prints out the daily totals, a timeline showing the trips and sub-trips for the day, and details about each
sub-trip. Each day will start on a new page.

Daily Timeline Report Group tree Navigation functionality allows you easy navigation within the Daily Timeline Report using the
icon on the toolbar.

When visible, a list of the vehicles and the days for which there is information is displayed. Selecting a day will reposition the
report preview on the page to the selected day.

Summary Timeline Report

The summary report prints one row per vehicle, showing the totals for the requested period.

The Summary report may be exported to one of five formats. Selecting the Export menu option or clicking the envelope on the
toolbar will request a name for the file the data is to be exported to. The ‘Save as Type’ option can be used to select how the data
is exported.

497
www.mixtelematics.com

497
 498

498
www.mixtelematics.com

498
 499

4.21 Fleet Manager Trailer Management Extension

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The Fleet Manager Trailer ID Extension provides functionality to allow fleet managers to maintain and report on trailer-related
information for their fleets.

Functionality is included to Add, Delete, Copy and Edit trailer records.

A suite of five reports are Included:

· Detail Trailer Report (by Vehicle)

· Detail Trailer Report (by Trailer)

· Summary Trailer Report (by Vehicle)

· Summary Trailer Report (by Trailer)

· Trailer Service Reminder Report

The standard Fleet Manager Criteria Wizard is used to allow simple selection of criteria for the various reports.

This document describes how to install and use the Fleet Manager Trailer Management Extension.

Installing and Loading the Extension

To install the Extension, run the Fleet Manager Professional 9 installation program and choose custom installation, selecting
Trailer Management from the Extensions. It is advisable not to have the Fleet Manager Client application open while installing.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the Trailer Management item.

499
www.mixtelematics.com

499
 500

Menus and Tool bars

Trailer List

The Trailer List for maintaining Trailer Information can be accessed from either the Tools Menu or the Extension toolbar in the
Fleet Manager Client application’s Main window.

or

Trailer Reports

The reports are accessed from the Trailer Reports menu item beneath the Reporting menu of the Fleet Manager Client
application:

Maintaining Trailer Information

The Trailer List is used to view and maintain trailers details.

500
www.mixtelematics.com

500
 501

You can add, edit or delete trailer records by right-clicking on a trailer entry in the list or by clicking on the appropriate item
beneath the Trailers menu.

Trailer Properties

The Trailer Properties dialog is used to add a new trailer record, or to view or edit the details of an existing trailer record.

General Tab

This tab contains general information such as the Description and Registration of the Trailer.

The option to Change the Trailer ID also appears, but this option should be used with caution. For more information see Change
Odometer / Trailer ID section.

Servicing Tab

501
www.mixtelematics.com

501
 502

Servicing Reminders can be specified by distance and/or duration:

A Reminder appears in the text label at the bottom of the dialog if the trailer is within the service reminder period.

A warning appears in the same place if the trailer is overdue for a service.

Odometer Tab

The Odometer tab in the Trailer Properties dialog allows you to specify the trailer’s current odometer reading and the effective
date of that particular odometer reading:

Change Odometer / Trailer ID

The Change Odometer Function can be used be used in conjunction with the Change Trailer ID Function, accessible by clicking
the Change button on the General Tab. This Function should only be used if a new physical FM Trailer ID unit is installed into the
trailer. Under normal circumstances, you should not delete any of the ID numbers associated with a physical trailer as doing so
may prevent historical data from being reflected correctly on the reports.

502
www.mixtelematics.com

502
 503

Criteria Wizard

The reports invoke the standard Criteria Wizard from the Fleet Manager Client application. Follow the steps in the Criteria Wizard
to select the vehicle/s and range of information you would like to see on the reports.

More Options

The last step of the Criteria Wizard has a More Options button. Click on this button to select the trailers to be included in the
Report. By Default all the Trailers are included in the report.

The “Save” button allows you to save your report parameters in a Criteria file.

Sample Reports
Detailed Trailer Reports

The Detailed Trailer Report displays the detailed information on the vehicle the trailer was connected to, the date and time the
trailer was connected and disconnected, and the distance travelled. The report can be run per vehicle or per trailer. See Figure 1
for an example of the Detailed Trailer Report by Trailer.

503
www.mixtelematics.com

503
 504

Figure 1

Summary Trailer Reports

The Summary Trailer Report displays the summary information on the Trailers connected to which Vehicles, total distance
connected and the total time it was connected. The report can run per vehicle or per trailer. See Figure 2 for an example of the
Summary Trailer Report by Vehicle.

Figure 2

Trailer Service Reminder Report

The Trailer Service Reminder Report displays a list of the Trailer's Service Information . The report shows the odometer reading
of each selected Trailer, the date/odometer reading of the previous service and the date and odometer of the next service. See
Figure 3 for example of Trailer Service Reminder report.

504
www.mixtelematics.com

504
 505

Figure 3

Exporting a Report

Each report provides the functionality to export its data into 5 of the main formats. Namely Comma Separated Values (.CSV) ,
Microsoft Word (.DOC) , Microsoft Excel (.XLS) , Rich Text Format (.RTF) and Plain Text (.TXT).

To access the Export functionality, select Export from your File menu on your Generated Report.

505
www.mixtelematics.com

505
 506

4.22 Fleet Manager Vehicle Maintenance Extension

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
Almost every company that uses the Fleet Manager Client application requires that their vehicles are serviced on a regular basis.
Another requirement is that vehicles be properly licensed and are road worthy.

The Fleet Manager Vehicle Maintenance Extension extends the Fleet Manager Software by including new reports used to list the
service history of the fleet, road worthiness and licensing information.

This document describes the steps to follow when installing and using the Fleet Manager Vehicle Maintenance Reports
Extension.

Installing and Loading the Extension

To install the Extension, run the Fleet Manager Professional 9 installation program. It is advisable not to have the Fleet Manager
Client application open while installing.

Once installed, the extension will be loaded automatically the next time the Fleet Manager Client application is run. To change
this, open the Extension Manager from the Tools menu, and uncheck the Vehicle Maintenance Extension item in the list of
available extensions.

Menu and tool bars

Menu

The menu items for the Fleet Manager Vehicle Maintenance Extension Reports are added to the Vehicle Reports menu item
found under the Reporting Menu of the Fleet Manager Client application’s Main window.

On selection of the Vehicle Maintenance Extension Reports, you can choose to create Service, License or Road worthy Reports.
The Service Reports will include the following sub-sections: Service on Record, No Service on Record and Service Due or
Overdue.

Service Due or Overdue can be broken down into the following: By Odo, By Date and By Engine Hours. This is illustrated below.

506
www.mixtelematics.com

506
 507

Criteria Wizard

The criteria wizard is used to create the Vehicle Maintenance Reports and consists of only two steps.

Clicking on the appropriate menu item opens the Vehicle Maintenance Reports wizard:

Step 1 of the Criteria Wizard allows you to specify which vehicles should be included on the report.

Step 2 of the Criteria Wizard allows you to select more options or save the selected criteria. When selecting More Options the
dialog described in the next section is displayed.

More Options

The More Options form (Fig 1a) allows the user to set default options that will affect the generation of reports by manipulating the
data to conform to the set options. When the More Options button is pressed, the Options Form is populated and will allow the
user access to only the options that are applicable for the specific report selected. This data is stored on a temporary basis and
will reset to the default values once the report is generated.

"More Options" will only be available for the Service Reports’ Service on Record menu option. It will not be available for any of the
other reports selected.

Should you, however, want to change the default settings, the More Options form can be accessed via the Options Toolbar or
Options Menu (Fig 1b). Once the form is saved, the chosen settings will become the default settings for every report created until
these settings are changed again.

The More Options form is shown below.

507
www.mixtelematics.com

507
 508

Fig 1 a

The More Options form allows the user to specify a filter criterion, specific to the Service Reports.

Analysing the form presented above, the first option allows you to filter service vehicle information to display vehicles that have
been serviced and have an odometer reading between the parameters as indicated above. The “from” parameter can never be
more than the “to” parameter and validation is done in that regard. Should the options be unselected, the report will show all
vehicles.

The second option allows you to filter service vehicle information to display vehicles that have been serviced and have an engine
hours reading between the parameters as indicated above. The “from” parameter can never be more than the “to” parameter and
validation is done in that regard. Should the options be unselected, the report will show all vehicles.

Hitting the Escape key will close the form and the Enter key saves the selected settings.

508
www.mixtelematics.com

508
 509

Fig 1 b

Creating Reports
Service Reports – Service on Record

The “Service on Record” form reports on all vehicles that have a service history in the system. The service history is printed on a
per-vehicle basis and includes information such as service reference, costs of service and service notes.

The last trip odometer reading, last downloaded date and engine hours readings are populated for each vehicle. These values
will only be included in the report if they are valid and are used in the system.

The data displayed in the Service Reports (Service On Record) is subjected to the criteria set under the more options form
explained above.

Service Reports – No Service on Record

The “No Service on Record” reports include vehicles that have no service history on record and an example is shown below.

509
www.mixtelematics.com

509
 510

Service Reports – Service Due or Overdue – By Odometer

The “Service Due or Overdue” reports include vehicles that are due or overdue for a service. Vehicles that are overdue for a
service are marked with an overdue icon similar to the icon found in the Fleet Manager Client application for overdue or due
vehicles. The same applies to vehicles that are due for a service.

A Vehicle is overdue for a service if the next service due odometer reading is less than the last downloaded odometer reading. A
Vehicle is due for a service if the next service due odometer reading is more than the last downloaded odometer reading but falls
within the reminder period set in the Fleet Manager Client application.

Vehicles that do not have a distance reminder set will not be included in the reports. The reminders are set in the Fleet Manager
Client’s vehicle property settings, servicing tab illustrated below. (Fig 2)

The same applies to the other reports. A sample report is illustrated in Fig 3 below

510
www.mixtelematics.com

510
 511

Fig 2

511
www.mixtelematics.com

511
 512

Fig 3

Two other reports that fall within the same category is the “Service Due or Overdue – By Date” and “Service Due or Overdue – By
Engine Hours” reports.

The license reports include two reports. These reports are “No License on Record” and “License Due or Overdue” and can be
found under the menu items illustrated earlier in this document.

Unlicensed vehicles (no license on record) are vehicles that have not got a reminder set for then. The reminder settings are found
on the vehicle properties page’s license tab.

A Vehicle is overdue for a license if the expiry date is earlier than the current date. A Vehicle is due for a service if the expiry date
is in the future but falls within the reminder period set in the Fleet Manager Client application.

Vehicles that have not got a license reminder set will not be included in any of the reports. The reminders are set in the Fleet
Manager Client’s vehicle property settings, servicing tab illustrated above. (Fig 2)

The Road Worthy reports work on the same basis as the license reports.

512
www.mixtelematics.com

512
 513

5 Fleet Manager Communications Suite

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The Fleet Manager Communications Suite is a collection of applications used to manage remote communications with Fleet
Manager on-board computers equipped with remote communications modules. The suite includes the following applications:

· Fleet Manager SMS Processor

· Fleet Manager GSM Downloader

· Fleet Manager DECT Downloader

· Fleet Manager Wireless Internet Service (GPRS & WLAN)

· Fleet Manager AutoPoll Client

· Fleet Manager SMTP Mail Service

· Fleet Manager Comms Scheduler Extension

Fleet Manager SMS Processor

The Fleet Manager SMS Processor is used to send and receive GSM short message service (SMS) messages to and from
FM200 and above series on-board computers equipped with GSM modems. Messages are sent and managed using the Fleet
Manager Active Tracking and Messaging Extension.

Fleet Manager GSM Downloader

The Fleet Manager GSM Downloader utilises a telephony device such as a modem to transfer information to and from FM200
and above series on-board computers equipped with GSM modems using GSM circuit-switched data (CSD) calls. Data transfer
schedules are defined and managed using the Fleet Manager Comms Scheduler Extension. Information downloaded from the on-
board computers is written into files which are transferred into the Fleet Manager database by the Fleet Manager AutoPoll Client.

Fleet Manager DECT Downloader

The Fleet Manager DECT Downloader transfers information to and from FM200 and above series on-board computers equipped
with FM DECT modules using digitally enhanced cordless telephony (DECT) technology. Information downloaded from the on-
board computers is written into files which are transferred into the Fleet Manager database by the Fleet Manager AutoPoll Client.

Fleet Manager Wireless Internet Service (GPRS & WLAN)

The Fleet Manager Wireless Internet Service (GPRS & WLAN) is used to send and receive messages and transfer data to and
from FM200 Plus and above series on-board computers equipped with GSM modems using the general packet radio service
(GPRS). Messages are sent and managed using the Fleet Manager Active Tracking and Messaging Extension. Data transfer
schedules are defined and managed using the Fleet ManagerComms Scheduler Extension. Information downloaded from the on-
board computers is written into files which are transferred into the Fleet Manager database by the Fleet Manager AutoPoll Client.

Fleet Manager AutoPoll Client

The Fleet Manager AutoPoll Client is a utility that continuously “polls” a download module connected to your computer and
automatically downloads trip, event and/or interval (tacho) data from green vehicle code-plugs that are inserted into the download
module’s code-plug socket.

The AutoPoll Client is also used to transfer information downloaded via code-plugs, the GSM Downloader, DECT Downloader or
Wireless Internet Service (GPRS & WLAN) into the Fleet Manager database.

513
www.mixtelematics.com

513
 514

Fleet Manager SMTP Mail Service

The Fleet Manager SMTP Mail Service sends e-mail messages generated by the SMS Processor and Wireless Internet Service
(GPRS & WLAN) using an SMTP mail server. Refer to Handset and E-Mail Notifications for more information.

Fleet Manager WLAN Service

The Fleet Manager Communications Suite makes provision for the new FM Wireless Kit that connects to Wireless LAN (WLAN)
networks. The FM Wireless Kit is compatible with most wireless access points e.g. products from Netgear. The WLAN
functionality of the Fleet Manager Communications Suite allows the user to have the full functionality provided over the GPRS
network to clients that want to make use of short range RF technologies like Wireless LAN.

514
www.mixtelematics.com

514
 515

5.1 Setting Up and Configuring the Transparent GSM and GPS Features
© 2008 MiX Telematics | Updated 2008/05/07

Overview
Third party devices can gain access to GSM modems or GPS receivers connected to the FM200 and above OBC families.

Transparent GSM Modem

This feature gives any third-party device full access to the GSM modem connected to any FM OBC, such as the FM200
Communicator: To make use of this feature the FM unit must be loaded with the correct firmware and configuration to allow third-
party devices access to the S3 auxiliary serial port.

Before connecting the third-party device to S3:

· Check that the vehicle configuration has ‘GSM modem’ connected to S2 and ‘Other serial device’ connected to S3. The GSM
antenna is to be mounted further than 20cm away from the human body under normal operating conditions.

· Upload device drivers. The simplest way to do this is to schedule an upload or, if you are using a code plug, use the new
device driver upload function in FM Professional. When using FM Dealer ensure that you use the second device driver set for
modems and SDK.

· Upload vehicle configuration. Again, the simplest is to schedule an upload.

· Connect the third-party device e.g. laptop, PDA etc. to S3.

With the third-party device connected to S3:

· Use any application that expects a standard Hayes-compatible modem connected to it's serial port with 19200-8-N-1. Please
ensure that you test this with a stand-alone modem first.

· The third-party device sends ‘AT <CR>’ and waits for a response.

· If the FM unit is not able to relinquish the modem, it will reply with ‘ERROR’ and the third-party device should retry after a
reasonable period, such as every minute.

· If the FM unit is able to relinquish the modem, it will respond with ‘OK’.

· The third-party device now has full control over the modem via the modem's own AT command interface.

· While the third-party device is using the modem, the FM unit will not try to use it.

· If the FM unit detects that the third-party device has closed the port or has not used the port for more than 2 minutes, it will
once again take over the use of the modem.

· The third-party device is responsible for relinquishing the modem and closing the port when it is not needed.

· There is a new parameter available called "GSM modem in use by SDK". This parameter can be used to define one or more
events in the FM unit to monitor and record third-party device modem usage.

· If the GSM modem’s power is managed by the FM OBC it will not shut down power while the modem is in use by the third-party
device.

· Through the modem's AT command interface, the third-party device can use SMS, CSD and/or GPRS, provided the modem
supports them.

· The third-party device must establish its own GPRS session to get onto the Internet.

515
www.mixtelematics.com

515
 516

Transparent GPS Receiver

This feature gives any third-party device read-only access to the GPS receiver connected to any FM OBC, such as the FM200
Locator. To make use of this feature the FM unit must be loaded with the correct firmware and configuration to allow third-party
devices access to the S3 auxiliary serial port.

Before connecting the third-party device to S3:

· Check that the vehicle configuration has ‘GPS receiver’ connected to F3 and GPS NMEA output’ connected to S3.

· Upload device drivers. The simplest way to do this is to schedule an upload or, if you are using a code plug, use the new
device driver upload function in FM Professional. When using FM Dealer ensure that you use the second device driver set for
modems and SDK.

· Upload vehicle configuration. Again, the simplest is to schedule an upload.

· Connect the third-party device e.g. laptop, PDA etc. to S3.

With the third-party device connected to S3:

· The FM unit will continuously stream the NMEA sentences from the GPS out on S3 for the third-party device to read with 4800-
8-N-1.

Additional Information

· When setting up dialup connection on 3rd party device, ensure redial attempts are set to high (20 should be more than
sufficient).

· When setting up dialup connection on 3rd party device, ensure time between redial attempts is very little (i.e. 3 or 5 seconds)

· The modem may take up to 1 minute to switch to "transparent modem mode" (i.e. retry to connect frequently & often)

· It is recommended that a simple null modem cable be used (as per the diagram below) between the OBC and 3rd party
device.

· It is recommended that the application use hardware flow control. If hardware flow control is not available (such as with some
Pocket PCs), the recommended cable to use is the loopback null modem cable. (Hardware flow control is needed, as the FM
unit has an internal buffer with limited space. It will process data as fast as possible, however the OBC needs to attend to other
tasks, therefore cannot sustain a throughput of 19200 bits/second).

Simple null modem cable

This is the recommended cable to use.

Full null modem cable

A simple null modem cable should be sufficient, but this cable (full null modem cable), can also be purchased as-is and used.

516
www.mixtelematics.com

516
 517

Loopback null modem cable

This cable should be used if connecting a device without hardware flow control, such as certain Pocket PCs.

517
www.mixtelematics.com

517
 518

5.2 Fleet Manager SMS Processor

© 2008 MiX Telematics | Updated 2008/06/10

Introduction
The SMS processor application facilitates messaging via short message service (SMS) between Fleet Manager on-board
computers that have GSM Modems connected and the Fleet Manager Database.

Note: This document should be read in conjunction with the following documents:

· Setting Up And Configuring A GSM Modem

How Does It Work?

The SMS Processor is typically installed into the "C:\Program Files\Fleet Manager Communications Suite\Fleet Manager SMS
Processor" folder. The installation process creates two folders beneath this, named Inbox and Outbox. These are used as
temporary folders through which the incoming and outgoing messages are processed.

When started, the SMS Processor loads the SMS Communication Processor (SMSComm.dll), which performs the actual
communication with the GSM network. The diagram below describes the flow of messages between the database and the GSM
network.

The SMS Processor monitors an SMS Queue in the Fleet Manager database via the FM Server. When a new entry is detected,
the SMS Processor translates it into a file in the common XML format and places the file in the Outbox folder. The SMS
Communication Processor is in turn monitoring the Outbox folder for new XML files. When one is detected, it is converted into the
transmission format and transmitted to the vehicle via the GSM network.

Incoming messages are treated in a similar fashion. When the SMS Communications Processor receives a message from a
vehicle via the GSM network, the message is translated into the common XML format and placed in the Inbox folder. The SMS
Processor is monitoring the Inbox folder for new files and, when one is detected, it is read and written into the Fleet Manager
database via the FM Server.

XML (eXtensible Markup Language) files are simply text files with a standard structure. They are used as a transfer mechanism
between the SMS Processor and the SMS Communications Processor for several reasons. Firstly, because they are plain text

518
www.mixtelematics.com

518
 519

files they can be read by people as easily as by programs, which makes for easier diagnosis of any problems that may occur in
the flow of processing. Secondly they can be validated in an efficient manner by comparing their structure to the structure defined
in a DTD (Data Type Definition) file. These factors combine to make for an open, yet structured, data transfer mechanism.

How Do I Use It?

Launch the SMS Processor using the shortcut created by the install set. Unless otherwise specified during installation, this
shortcut is created in the Fleet Manager Office folder beneath the Programs folder on the Start menu.

The install set also creates an additional shortcut in the Startup folder so that the SMS Processor is launched automatically when
your computer is restarted.

When you launch the SMS Processor from the menu it may attempt to start processing immediately, if it has been configured to
do so. If this is the case but all configuration data is not correct, the processor will fail to start and a message will be displayed. If
however the configuration data is correct the processor will start and will indicate that it is running by displaying the icon in the
system tray. When the processor is not running the icon is displayed in the system tray.

All configuration of the SMS Processor is done from a single dialog that can be accessed by double-clicking the system tray icon,
or by right-clicking the system tray icon and selecting Configure from the menu. Once you have entered the configuration
information you can simply click the Start button to initiate processing of incoming and outgoing SMS messages.

The configuration dialog is as follows.

There are a number of controls on the dialog;

Language selector

519
www.mixtelematics.com

519
 520

Appears at the top of the dialog and is used to select the language in which the SMS Processor is to operate.

Autostart setting

Appears just below the language selector and is used to indicate whether processing is to commence as soon as the program is
started.

Modem settings

Appears as a tabbed group in the centre of the dialog. Two modems are supported and the tabs are used to select the modem
whose settings you wish to view or change. The settings themselves consist of;

· Comm Port – the communications (serial) port that the modem is connected to.

NOTE: Although the program interface only allows the section of COM ports 1 through 4, it is possible to make use of other
COM ports. To do so it will be necessary to edit the registry. The port information is held in the following registry value;
HKEY_LOCAL_MACHINE
SOFTWARE
Data Pro Development (Pty) Ltd
Fleet Manager
SMS Processor
Modem001 (or Modem002)
Port
The value of the Port entry is a string of the form COMn where n is the port number; the value would be COM1 if the modem
is connected to the first serial port. In order to change the port, the value of this entry can be changed. For example, to use
the 27th serial port you would change this entry to COM27. You should terminate the SMS Processor before making this
change and start it again afterwards. The modem settings tab in the SMS Processor will correctly display the new port that
you have specified.

· Message Centre Number – the telephone number of the GSM SMS message centre to be used for sending and receiving
messages.

· PIN Number – the PIN code required to access the SIM card in the GSM modem. Note that this is a protected field and can
never be viewed in plain text.

· BAUD rate – the speed at which communications between the port and the modem will take place. This field has a default
value of 19200.

· Modem number – the telephone number of the modem connected to the SMS processor.

Area Code Restriction

When this is check and area codes have been specified, SMS messages will only be sent to telephone numbers with the
specified area codes.

Messages Folder

This is the location of the e-mail message folder where notification e-mail messages will be generated. Refer to the Handset and
E-Mail Notifications documentation for more information.

Inbox

A display-only field indicating the Inbox folder path.

Outbox

A display-only field indicating Outbox folder path.

520
www.mixtelematics.com

520
 521

Status indicator

Appears at the top right of the dialog and consists of the word Running and the system icon with a green light, indicating that the
processor is running, or the word Stopped and the system icon with a red light, indicating that the processor is not running.

Start/Stop button

Used to stop or start the processor. The text displayed on the button and the action it will take depend on whether the processor
is running or stopped.

View Log button

Opens the Log Ticker window pictured below.

The Log Ticker window can be used to monitor the processing that is taking place. It will display a number of messages,
indicating the processing actions that are occurring. The default display is up to 20 messages, but this can be configured
between 20 and 255 by changing the value in the text box at the bottom of the window.

It must be noted that the Log Ticker does not display all the messages that are being logged by the SMS Processor. If you wish to
view the full log file, click on the Full Log button. This will open the log file FMSMSLog.txt using the default text editor. If the Log
Ticker window is open when you exit the SMS Processor, it will be reopened when next the SMS Processor is executed. The
Close button will close the Log Ticker window.

Close button

Closes the configuration dialog without exiting the SMS Processor, in effect minimizing it to the system tray.

Exit button

Exits the SMS Processor. A confirmation dialog is displayed that requires you to confirm your intention to exit before the program
is actually exited.

521
www.mixtelematics.com

521
 522
5.2.1 Setting Up And Configuring A GSM Modem for SMS

© 2008 MiX Telematics | Updated 2008/06/25

Overview
The purpose of this document is to provide additional information for using GSM modem devices with FM200 and above series
on-board computers.

The following topics are covered:

· Hardware

· Device Drivers

· GSM modems supported by FM200 series on-board computers

· Installing a modem with the Fleet Manager on-board computer

· Using HyperTerminal to test a modem

· Configuring the modem to echo all typed characters

· Changing the modem baud rate

· Setting up the modem

· Reading and writing SMS messages

· Call management

· Testing GPRS

· Overview of GSM software

· Configuring a GSM Modem with Fleet Manager Professional 9

Note: The information in this document may not be pertain to all modem devices.

Hardware
A standard off-the-shelf GSM module can be connected to an FM200 and above series unit via the RS232 port. Please see GSM
modems supported by FM200 series and above on-board computers section for more information and a list of recommended
GSM devices and requirements.

Device Drivers
When a GSM module is connected to the FM unit for the first time, a set of firmware device drivers must be transferred to the unit
using a standard 256kb device driver code-plug. These device drivers enable the unit to communicate with the GSM module.

The latest version of the FM Dealer Utility should be used to initialise a device driver code-plug with the required device drivers.

GSM modems supported by FM200 and above series on-board computers

Minimum modem specifications

For your modem to be used with the current release of FM200, FM200Plus and above firmware and office software it needs to be
configurable to the following minimum specifications.

522
www.mixtelematics.com

522
 523

RS232 (DTE-DCE) communications

· RS232 voltage levels

· 19200 baud (FM200/Plus configures this)

· 8 data bits (Pre-Configured)

· 1 stop bit (Pre-Configured)

· RTS-CTS flow control (FM200 configures this)

· Controlled lines (RX, TX, RTS, CTS, GND)

· DTR and DSR are looped back in the FM communications harness

Over the air data transfer

· Non-Transparent data transfer (From the PC side software only)

· Fixed baud rate (V.32) (From the PC side software only)

Power requirements

The installer should make sure that the installation meets the power requirements of the modem device installed.

AT commend set

The modem should support the standard Hayes AT command format and conform to the GSM extensions thereof. SMS
messaging should also be supported in both text and PDU modes.

Note: The Siemens M1 terminal does not support SMS messaging in text mode and is thus not suitable for use with the FM200
for SMS functionality.

FM200 Plus Compatible Modems

The following is a list of modems compatible with the FM200 Plus series of on-board computers as well as the communications
methods they support:

Siemens

· M20 Terminal: (SMS and CSD)

· TC35 Terminal: (SMS and CSD)

· MC35 Terminal: (SMS, CSD and GPRS)

· MC35i Terminal: (SMS, CSD and GPRS)

Wavecom

· WM0D2 Terminal: (SMS and CSD)

· C2D Terminal: (SMS, CSD and GPRS)

· Fastrack M1206: (SMS, CSD and GPRS)

Nokia

523
www.mixtelematics.com

523
 524

· 6090: (SMS and CSD)

· 810: (SMS and CSD)

Falcom

· A2D-1: (SMS and CSD)

Note: This list only contains the modems that were tested to work with the FM200 Plus unit. The FM units use a basic AT
command set and should be compatible with a wide range of available modems.

Installing a modem with the Fleet Manager on-board computer

Make sure the modem you are installing has got the latest firmware installed onto it. If the modem comes with an ignition input, it
is highly recommended that this be connected to the ignition circuit for improved reliability.

GSM Modem Installation Accessories

FM unit serial cable

· FM TTL converter: The original TTL converter (FM: X39-723-002-055) can be used to connect a modem to the FM unit, it is not
recommended though as it only provides 1 serial port.

· FM Splitter cable: The FM Splitter cable (FM: X39-723-002-075) can also be used to connect a modem to the FM unit.

· FM200Plus serial cable: This cable can be used with the FM200Plus unit and is much more useful than the splitter cable. This
cable provides connection for the FMTerminal as well as two other serial ports.

GSM modem

Any of the supported modems with the FM unit.

Modem antenna

The selection of the antenna depends on the modem type and mounting requirements. The GSM antenna is to be mounted
further than 20cm away from the human body under normal operating conditions.

SIM card

The SIM card should be obtained from your preferred network operator. The SIM card should be enabled to receive incoming
data calls and to send and receive SMS messages if SMS functionality is required.

GSM diagnostic plug

The GSM diagnostic plug is an essential tool for the installation of GSM modems. A diagnostic plug can be formatted using the
FM Dealer Utility. See the FM Dealer Utility documentation for more information.

Fleet Manager software

The Fleet Manager software is needed to configure the FM unit to communicate with the modem.

Modem connector cable

Some modems, such as the WAVECOM WMOD2 modem, need a converter cable to convert from the DB15 connector on the
modem to the DB9 connector on the FM Splitter. This can be obtained from your modem supplier.

RS232 extender cable

If the modem cannot be mounted close enough to the FM unit for the converter harness to reach it, then a RS232 extender cable

524
www.mixtelematics.com

524
 525

(straight through) can be used between the modem and the FM unit. However, this is not recommended.

Relay for modem power control

The external-drive lines from the FM unit can be wired to control power to the modem. This saves the vehicle’s battery and allows
the modem to be “hard reset” by the FM unit in case of a modem lock-up.

Note: Before you start with the installation make sure you have got all the required components specific to your installation.

Modem Connections
Most modems require three (types of) connections:

· Antenna

· Power

· Serial cable

Antenna

The antenna is the simplest connection as it has no active connection to the FM unit. Refer to your modem documentation to find
the details of the antenna that must be used. Note: not all modem manufacturers supply an antenna as part of the modem. The
GSM antenna is to be mounted further than 20cm away from the human body under normal operating conditions.

Power

It may be important to control the modem's power consumption to prevent it from draining the vehicle's battery. The Fleet
Manager Client software provides functionality to configure this. You can set the on-board computer to switch the modem off x
hours after the vehicle is parked, or if the vehicle battery voltage drops below a certain level.

The physical outputs available for controlling the power to the modem vary depending on the type of FM unit being used. There
are two types of power control outputs provided by the FM units; “External Relay Drive” outputs and the "Positive Drive" output.
The External Relay Drive outputs can be used to drive an external relay with a maximum current loading of 250mA. The Positive
Drive supplies battery voltage and can be used to supply power to external devices with a maximum current loading of 1 Amp.

Refer to the table below for a list of power outputs available for modems when connected to different unit types..

The table below indicates which physical outputs can be used to supply power to the external or internal GSM modem of each
unit type.

Unit Type External Relay Drive 1 External Relay Drive 2 Positive Drive

FM200 Yes No - FM200 only has 1 External No - FM200 does not have
Relay Drive a Positive Drive

FM200 Plus Yes Yes Yes

FM200 Communicator No -internal modem is connected No - internal modem is connected Yes

to Positive Drive to Positive Drive

Note: Use a fuse in the supply of power to the modem. Refer to the modem specification for details of the fuse size.

Positive Drive power connection:

The Positive Drive power and ground lines are only available when the FM200Plus Serial Cable is connected. The brown wire is
ground (permanent) while the red wire is the switched battery voltage line.

525
www.mixtelematics.com

525
 526

External Relay Drive power connection:

The External Relay Drive lines require an external relay for controlling the power supply to the modem. See the connection
diagram below for a typical connection.

Note: The relay assigned pin numbers may differ depending on the relay type and manufacturer.

Serial cable

The type of cable supported depends on the type of FM unit used. The table below list the combinations of cables that may be
used. On the FM200 Plus Serial Cable, the longer of the two DB9 connector cables is S2 (if not labelled).

Unit Type FM TTL To RS232 Converter FM Splitter Cable FM 200 Plus Serial Cable

FM200 Yes Yes No

FM200 Plus (FM200 Plus) Yes Yes Yes

FM200 Communicator No No Yes

General installation procedure

1. Using the FM Dealer Utility, load the latest released Device Drivers into unit. For best results it is recommended that you use a
Device Driver code-plug.

2. Use the Fleet Manager Client application to correctly specify the vehicle configuration. Using a green vehicle code-plug, load
the configuration into the unit. It is important that this configuration contains the correct PIN code needed to enable the SIM
card. You must also ensure that the configuration contains the correct home-base number (the number of the modem in the
office that receives SMS messages) as well as the correct SMSC (short message service centre) number if SMS functionality is
required. You must ensure that all GPRS settings are specified correctly if GPRS functionality is required.

3. Connect the modem to the FM unit (refer to accessories for connecting cables).

4. Use an RS232 extender cable if required (not recommended).

5. The FM unit will try to initialise the modem to operate at 19200 baud. The Firmware on the FM unit will be able to find the
modem baud rate in the range from 2400 baud up to and including 38400 baud. If the modem is configured to a baud rate
outside of this range the FM unit will not be able to re-configure the modem to 19200 baud (you will need to reconfigure it
manually). See Changing the modem baud rate for more information.

526
www.mixtelematics.com

526
 527

6. Create a GSM/DECT diagnostic plug using the FM Dealer utility.

7. For audible and visual feedback of the GSM functionality, insert a GSM diagnostic plug in the FM code-plug socket.

8. When the diagnostic plug is inserted you will hear a short double-beep, signalling that the FM unit is configured for GSM
functionality. Any other beeps signal an incorrect configuration of the unit.

9. The code-plug socket LED should flash approximately every 30 seconds, indicating that the FM unit is able to communicate
with the modem. This may take longer than 30 seconds the first time the modem is being initialised (in the order of 120
seconds).

10.Once the modem is logged onto the GSM network, the FM unit will issue a single beep in sync with the LED flashes (GPRS-
capable modems will issue a double beep).

11.Check the status LED on the modem itself (most modems have one). Refer to the modem’s documentation for more
information on the meaning of its state.

12.Only proceed with the installation and testing once the diagnostic plug indicates that the FM unit is communicating with the
modem and the modem is registered on the network.

13.Dial the vehicle from another data modem to check that the modem answers the incoming data call. The FM unit will not
automatically answer voice calls (the FM Keypad is required for managing these).

14.Send a position request to the vehicle to test SMS messaging to and from the vehicle. The on-board computer will reply to a
position request, even if no GPS is physically connected to the unit.

For more on the GSM diagnostic beep codes refer to Beep and Flash Codes.

Warning: SIEMENS TC35 / MC35 Terminal (only applies when used with an FM200)

"Power Down" mode: The TC35 and MC35 modem has a sleep mode function. When the modem goes into power down mode, it
can only be awakened by either changing the state of the DTR (pin4) line on the modem, or by changing the ignition input line
state from low to high for longer than 200ms. The FM200 unit has no control over the DTR line, thus it is not able to change the
modem’s state. For this reason, it is recommended that you connect the modem’s ignition input to the vehicle's ignition line. The
modem goes into this state when it is outside of GSM coverage for a long time or when the "modem off" at-command is issued.
For this reason, the power down command is not used in the FM200 firmware.

Warning: SIEMENS TC35/MC35 Terminal (applies when used with any FM unit)

It is not recommended that you manage theses modems' power consumption with serial commands. If you do, you must ensure
that the ignition input of the modems is properly connected. Once the Sleep AT command is sent to the modem, only a change in
the modem's ignition input from off to on will wake the modem.

Warning: SIEMENS M1 Terminal

The M1 modem does not support SMS messaging in text mode and is thus not suitable for SMS functionality.

Using HyperTerminal to test a modem

This section explains how to use a terminal program like HyperTerminal to communicate with a serial device such as a modem.
There are a number of terminal applications like HyperTerminal and the user is not restricted to this one only.

What you will need

· RS232 Cable to connect the modem to your PC’s serial port.

· Power supply for the modem (refer to modem documentation)

· Serial port terminal application, e.g. HyperTerminal

527
www.mixtelematics.com

527
 528

Start HyperTerminal

HyperTerminal can be installed from the Microsoft Windows installation disk if not already installed on you PC. Refer to the MS
Windows documentation for more info on the application.

Step 1

Open the HyperTerminal and the “Connection Description” dialog box.

Step 2

Enter a name that for the HyperTerminal session (if you wish to save it for later use), for example “Siemens TC35 on COM1”.
Click OK to open the “Connect To” dialog.

Step 3

Using the “connect using” drop-down-list, select the serial port that the modem is connected to. A serial port can only be used by
one device at a time, so make sure that no other device is using the selected serial port. Click OK to open the serial port physical
settings.

528
www.mixtelematics.com

528
 529

Step 4

Select the baud rate (bits per second) that the modem is currently configured for (refer to the modem’s technical manual). Select
“None” for the Flow control option. Clicking OK would open HyperTerminal connected to the COM1 device.

Step 5

529
www.mixtelematics.com

529
 530

You can now save the settings to be loaded at a later stage. Ensure that Caps-Lock is on when you are communicating with the
modem. It is not necessary, but some modems needs the AT commands in capital letters to synchronize with the PC baud rate.

Step 6

To check that the modem is communicating, type “AT” and press the Enter/Return (¿) key. The modem should respond with the
string: “OK”. If nothing appears while typing the command you can either turn on local-echoing in HyperTerminal or you can
configure the modem to echo all characters that it received. The latter is preferred.

For all sections related to sending commands to the modem the following conventions will be followed.

Command ATE1 Turn echoing on

Response OK The modem accepted the command

The first column describes direction of the string. "Command" is the string entered on HyperTerminal while "Response" is the
string/s returned from the modem as a response to the command sent. When you want to send a command to the modem, type
in the command string followed by the Enter/Return (¿) key. Usually AT commands are entered as capital letters.

Note: If you see “xxxx” as part of a command, read the comments field to see whether you have to enter xxxx or need to replace
that part of the command with your own string!!!!

If the modem is not responding to your commands:

· Check the spelling of your commands (zero and o can easily be confused!)

· Check the baud rate setting on HyperTerminal

Configure modem to echo all typed characters

If you want to see what you are typing you can use the following sequence of command to turn on the echoing function of the
modem.

Command ATE1 Turn echoing on

530
www.mixtelematics.com

530
 531

Response OK The modem accepted the command

Changing the modem baud rate

The first step is to ensure that the modem to responds to commands entered. To check the modem, use the normal AT query.
Remember to give the modem a chance to register to the network, as it might only respond once the network log-on was
completed successfully. Also check the LED status on the modem itself (refer to modem user manual).

Test the modem response

Command AT Check is the modem is ready

Response OK Modem interpreted AT command correctly

Change the baud rate in HyperTerminal until you receive a valid response for the test modem command. At this point
communication with the modem has been established.

The next step is to check the modem baud rate setting.

Checking the active baud rate setting

Command AT+IPR? Query the modem baud rate setting

Response +IPR: 0 The modem is configured in auto baud detection mode. In this mode you can
communicate to the modem at any baud rate as long as you use capital
letters as the AT commands.

+IPR: xxxx “xxxx” represents the baud rate of the modem as an integer string value.

Setting the new baud rate

Command AT+IPR=19200 Set the modem baud rate to 19200 baud. You can replace the “19200” with
“9600” if the modem needs to be configured to run at 9600 baud.

Response OK Setting accepted.

If the specified baud rate is different to your HyperTerminal setting, then the modem will no longer respond to AT command.
Change the HyperTerminal baud rate to the value the modem was set to. Use the test command to verify that the modem is
responding. At this point you can now save the value as the default baud rate, which will be used when the power is disconnected
and re-connected.

Save all the current settings as the power-on defaults

Command AT&W Save all settings

Response OK Command accepted

Setting up the modem

531
www.mixtelematics.com

531
 532

Before you use the GSM, check the following.

Enable extended error reporting

Command AT+CMEE=1 Enable extended error reporting on AT commands

Response OK The modem excepted the commandErrors will now be reported in the form
“+CEER: Error XX” where XX is the extended error code.

Check if a PIN code is required

Command AT+CPIN? Check Pin code status

Response +CPIN: READY No PIN code is required

+CPIN: SIM PIN You need to enter the PIN for the SIM card

+CPIN: SIM PUK The SIM is locked and requires a PUK code. Use your mobile phone to enter
the PUK code (much safer).

Enter the PIN code if required

Command AT+CPIN=”xxxx” Enter Pin code to the SIM, the string xxxx must be replaced with your SIM's
PIN code. This command may take a few seconds before it responds, as it
might only respond after it has registered with the network. Remember that
you can only enter the PIN code incorrectly 3 times before the PUK code is
required!!!

Response OK PIN accepted

Check the signal quality/level

Command AT+CSQ Check the signal strength.

Response +CSQ: 16,0 The first value (before the comma) is an indication of how good the reception
is. 99 means that the modem cannot determine the signal strength, otherwise
the value would be in the rang from 0 to 31, where 31 means perfect and 1 is
very poor.

Check the network registration status of the SIM card

Command AT+CREG? Check the modem registration status.

Response +CREG: 0,1 The second value (after the first comma) is the status of network registration.
Valid values:

· 0: not registered, ME is currently not searching for new operator.

· 1: registered, home network

532
www.mixtelematics.com

532
 533

· 2: not registered, but ME is currently searching for a new operator

· 3: registration denied

· 4: unknown

· 5: registered, roaming

When the PIN status is OK and the modem is registered then the modem is ready to accept GSM related commands.

Reading and writing SMS messages

Before you can send SMS messages from the modem, the SMS service centre address needs to be specified. Ask your network
provider if you do not know what it is. The number should normally be entered in international format, i.e. starting with a “+”.

Enter SMS service centre address

Command AT+CSCA=”+27832000001” Set your network service centre address

Response OK Service centre address accepted

Check the service centre address

Command AT+CSCA? Query the active service centre address

Response +CSCA: "+27831000002",145 Service centre address is the value before the first comma.

Store the service centre address permanently

Command AT+CPAS Store SIM related settings

Response OK Settings was saved

We are only going to send and read SMS messages in text format, so we need to configure the modem to do so.

Select text modem SMS message format

Command AT+CMGF=1 Enable text mode SMS messaging

Response OK Command accepted

Check the message storage

Command AT+CPMS? Check the available and used message storage

Response +CPMS: “SM” means the message is stored on the SIM

“SM”,0,15,”SM”,0,15,”SM”,0,15

533
www.mixtelematics.com

533
 534

“MT” means the message is stored on the modem

At this point the modem is configured to read and write SMS messages in text mode.

List all messaged stirred on the modem

Command AT+CMGL=”ALL” List all stored SMS messages

Response +CMGL: 1,”REC UNREAD”,”081234569”, This is Settings were saved

the message text+CMGL: 2,”REC
UNREAD”,”081234569”, This is the message
text… Etc.

Read a specific message

Command AT+CMGR=x Read a message stored on the specified storage

location “x”.

Response +CMGR: "REC Display the selected messaged detail

READ","+27836414132", ,"03/12/17,11:42:37
+08"

Delete a message

Command AT+CMGD=x Delete the message stored on the specified storage location “x”.

Response OK Message was deleted

Sending an SMS message is a bit more involved and takes 3 steps to execute. First the command is entered, then you need to
wait for the prompt to enter the message body and finally use the "Send" key-stroke to transmit the message. To terminate the
message body without sending it, use the Escape key (Esc).

Sending an SMS message

Command AT+CMGS=”PhoneNumber” Start to send an SMS message

Response > Prompt to receive the message body

Command type your message mode text now Enter the message body now

Command Ctrl-z Type the Ctrl-Z key stroke to send the message. (Hold down the
control (Ctrl) key and press z)

Response +CMGS: y The message was sent

Example:
AT+CMGS="0825626159"
> Hello®

534
www.mixtelematics.com

534
 535
+CMGS: 77
Note: DO NOT press the Enter key after entering the message text. Use only Ctrl-z to indicate the end of the message text.

Call management
This section covers making voice and data calls as well as answering incoming calls

Enable extended call information

Command AT+CRC=1 Enable extended call information

Response OK Command accepted

Enable caller line identity

Command AT+CLIP=1 Switch on caller line identification (CLI), not supported on all
modems. For the modem to report to CLI the other party must
have “send own number” enabled and the SIM in the modem has
to be enabled to receive CLI. Ask your service provider for more
info.

Response OK Command accepted

When an incoming call is received the modem sends unsolicited strings to HyperTerminal.
+CRING: ASYNC (indicates the type of incoming call; a data call in this case)
+CLIP: “0839876543”,xx (indicates the calling party’s number)
Placing a voice call

Command ATDxxxxxxxx; Dials a GSM phone number. The semi-colon “;” at the end signals
a voice call.

Response OK The called party answered the call

Placing a data call

Command ATDxxxxxxxx Dials a GSM phone number

Response OK The called party answered the call

CONNECT The modem connection was successful

NO CARRIER The call was terminated/not available

BUSY The called party is busy with another call

When a modem is in a data call then it does not accept any AT commands. To make it accept AT commands there is a particular
character sequence that needs to be sent to the modem:
<do not type anything for 1 second>

535
www.mixtelematics.com

535
 536
+++
<do not type anything for 1 second>
The modem will now respond with "OK" to signal that it is in command mode.

Terminating a call (hang-up)

Command ATH Terminate any calls

Response OK Command accepted

Testing GPRS
This section of the document will explain how to determine whether or not your modem is GPRS capable. The simplest test is to
query the GPRS PDP context activation status. For an explanation of how to do a more comprehensive GPRS test, please see
Testing GPRS SIM Cards.

Get the GPRS PDP context activation status

Command AT+CGACT? GPRS PDP context activation status

Response ERROR Command not known, this modem cannot be used for GPRS with
the FM unit

+CGACT: 1,0 The modem understood the command, and has an inactive PDP
context.

Define a PDP context

Command AT+CGDCONT=1,"IP","internet" Define a PDP context, where “internet” is the APN string

Response OK Context defined

Create a new GPRS session

Command ATD*99***1# Create a new GPRS session using context #1

Response CONNECT Connected to the GPRS network

~ }#À!}!}!} }6}!}$}%Ü}"}&} } } } }'}"} PPP configuration strings

(}"}#}$À#&´~

Overview of GSM Software

SMS Processor

The Fleet Manager SMS Processor is used to send and receive GSM short message service (SMS) messages to and from
FM200 and above series on-board computers equipped with GSM modems. Messages are sent and managed using the Fleet
Manager Active Tracking and Messaging Extension.

GSM Downloader

536
www.mixtelematics.com

536
 537

The Fleet Manager GSM Downloader utilises a telephony device such as a modem to transfer information to and from FM200
and above series on-board computers equipped with GSM modems using GSM circuit-switched data (CSD) calls. Data transfer
schedules are defined and managed using the Fleet Manager Comms Scheduler Extension. Information downloaded from the on-
board computers is written to files which are transferred into the Fleet Manager database by the Fleet Manager AutoPoll Client.

Wireless Internet Service (GPRS & WLAN)

The Fleet Manager Wireless Internet Service (GPRS & WLAN) is used to send and receive messages and transfer data to and
from FM200 Plus and above series on-board computers equipped with GSM modems using the general packet radio service
(GPRS). Messages are sent and managed using the Fleet Manager Active Tracking and Messaging Extension. Data transfer
schedules are defined and managed using the Fleet Manager Comms Scheduler Extension. Information downloaded from the on-
board computers is written to files which are transferred into the Fleet Manager database by the Fleet Manager AutoPoll Client.

Configuring a GSM modem with Fleet Manager Professional 9

The Fleet Manager Client application allows you to specify how the FM unit interacts with the GSM module.

Step 1

The Device tab of the Vehicle Properties dialogue is used to specify that a GSM module is connected to a serial port of the FM
unit.

Double clicking on the relevant serial port entry in the list box displays the Device Connection dialogue.

Step 2

Select GSM Modem in the devices tab. Click on the Modem tab.

Step 3

Enter the PIN code and Modem initialization string.

Important: You must remove the SIM card from the GSM module and make use of a mobile phone to update the PIN code for
the SIM card if necessary. For security reasons, changing the PIN code in the Vehicle Properties dialogue does not update the
PIN code in the device. If the PIN code entered into the Vehicle Properties dialogue does not match the PIN code in the GSM
module, the GSM module will not be able to logon to the GSM network.

537
www.mixtelematics.com

537
 538

If you have an FM Keypad and wish to use it to make voice calls, enable voice communications and select the voice channel to
be used with your hands-free kit.

Step 4

Click on the CSD Tab.

Set the data number of the GSM modem that is connected to the FM unit. All telephone numbers must be entered in canonical
format by specifying a country, city or area code and local number. This is so that the GSM Downloader can translate them into
valid dialling strings using the Windows dialling rules. This is described in more detail below.

Step 5

538
www.mixtelematics.com

538
 539

Click on the SMS tab

This tab is used to configure the SMS settings for this unit. To enable SMS communications, tick the relevant check box on this
tab and complete the details.

The SMS limit from the unit to the office determines how many SMSs the unit will be allowed to send per day. The SMS limit from
the office to the unit determines how many SMS messages will be allowed to be sent to the unit from the office.

Step 6

Click on the GPRS tab.

This tab is used to configure the GPRS settings for this unit. To enable GPRS communications, tick the relevant check box on
this tab and complete the details.

The APN, User name and Password must be obtained from your network service provider.

The Server IP Address and Server IP Port must be set to those of the computer hosting the Fleet Manager Wireless Internet
Service (GPRS & WLAN).

Also see GPRS Questions and Answers for more information on these settings.

539
www.mixtelematics.com

539
 540

Step 7

Click the Advanced button.

If your cellular network charges for every GPRS Connection made, you may limit the number of connections per day. Otherwise,
you should leave this unchecked.

Specify the frequency at which that Automatic Vehicle Location (AVL) packets should be sent by the unit. AVL packets serve two
purposes. Firstly, they keep the GPRS connection alive to prevent the unit's IP address from changing. On most GPRS networks,
dormant connections will be terminated after 5 to 10 minutes. Secondly, they include GPS position information useful for Active
Tracking.

Note: Setting the AVL period for out-of-trip to less than 30 seconds will cause power management to be bypassed. The GSM unit
will remain switched on permanently.

540
www.mixtelematics.com

540
 541

Step 8

Click on the Packet Comms tab.

The Packet Comms tab is used to specify whether packet based communications (such as GPRS) should be used for active
events and messaging.

You may also configure the unit to send end-of-trip (EOT) download of active events. This will cause the office software to
automatically perform a quick download at the end of each trip.

Step 9

541
www.mixtelematics.com

541
 542

Click on the Database tab.

The database tab is used to filter the storage of AVL packets in the database. As described above, AVL packets serve two
purposes. If you require AVL packets to be sent to keep the GPRS connection alive, you may not wish to store all AVL packets in
the database. In the same way, if your FM unit does not have a GPS receiver connected, you may not wish to store AVL packets
in the database.

Step 10

Click on the Transports tab.

This tab is used to configure the default transports for data transfer, commands and messages for this vehicle. These values can
be over-ridden when defining a schedule with the Comms Scheduler Extension and when sending command messages, free-text
messages or jobs using the Active Tracking and Messaging Extension.

Select the appropriate default transport values and click the Power tab.

542
www.mixtelematics.com

542
 543

Step 11

Select the appropriate power management options for the modem. See Installing a modem with the Fleet Manager on-board
computer for more information.

543
www.mixtelematics.com

543
 544

5.3 Fleet Manager GSM Downloader

© 2008 MiX Telematics | Updated 2008/06/11

Overview
This document includes the following topics:

· Fleet Manager GSM Downloader Overview

· What's new in Version 8.10

· GSM Modem Installation

· Starting GSM Downloader

· Database Connection

· Using the GSM Downloader

Fleet Manager GSM Downloader Overview

The Fleet Manager GSM Downloader utilises a telephony device such as a modem to transfer information to and from FM200
and above series on-board computers equipped with GSM modems using GSM circuit-switched data (CSD) calls. Data transfer
schedules are defined and managed using the Fleet Manager Comms Scheduler Extension. Information downloaded from the on-
board computers is written to files which are transferred into the Fleet Manager database by the Fleet Manager AutoPoll Client.

The GSM Downloader is designed to make use of any modem device that complies with the Windows Telephony Application
Program Interface (TAPI) version 1.4 or later. Before launching the GSM Downloader for the first time, ensure that you have at
least one TAPI modem device connected to your computer and ensure that the appropriate driver software is installed and
configured correctly.

Note: This document should be read in conjunction with the following documents:

· Setting up and Configuring GSM Modems

· Fleet Manager Comms Scheduler Extension

· Fleet Manager SMS Processor

· Fleet Manager Wireless Internet Service (GPRS & WLAN)

· Fleet Manager Active Tracking and Messaging Extension

New in Version 8.10 - released with Fleet Manager Professional 8 (March 2004)
Version 8.10 of the GSM Software Suite includes the following new feature:

· Area Code Restriction – This provides the ability to limit which telephone numbers will be dialled from a GSM downloader.

GSM Modem Installation

Modems are installed using the Modems applet in the Control Panel. Consult your Windows and modem documentation for more
information.

Starting GSM Downloader

Launch the GSM Downloader using the shortcut created by the install set. Unless otherwise specified during installation, this

544
www.mixtelematics.com

544
 545

shortcut is created in the Fleet Manager Office folder beneath the Programs folder on the Start menu.

Another shortcut to the GSM Downloader is placed in the Startup folder so that the GSM Downloader runs automatically when
your computer is restarted. Consult your Windows documentation for more information.

Database Connection

The GSM Downloader can be configured to use a database on the LAN or at a remote location. This database connection is
configured using the Fleet Manager Administratorwhich can be launched from the shortcut in the Windows Control Panel. If the
database connection is configured to use an FM-Web database on the LAN or to connect to an FM-Web remote URL, the
downloader login credentials must be supplied. Refer to the Fleet Manager Administrator documentation for more information on
how to set these credentials.

Using the GSM Downloader

When the GSM Downloader is running, the following icon is displayed in the task bar: Double-click on this icon or right click
on it and click on Configure to display the GSM Downloader configuration dialogue.

Language Settings
Use the language drop down list to select the language.

Changing Device Settings

Drop down the Device combo box and select the modem to be used by the GSM downloader. The Settings button in the Device
frame can be used to specify specific modem properties:

545
www.mixtelematics.com

545
 546

You can specify a network initialisation string and/or modem initialisation string if necessary. Some modems require special
initialisation strings to function correctly. Consult your modem’s documentation for more information.

If you are using a GSM modem, you can enter a PIN code for the modem in this dialog.

Important: You must ensure that your modem’s properties and dialling properties are set correctly to enable the GSM
Downloader to function correctly. These properties are set using the Modems applet in Control Panel. The modem’s dialling
properties are used to convert the telephone numbers from the canonical format into the appropriate dialling string. It is crucial
that the current location and other dialling rules be specified to ensure this conversion is done correctly.

The modem’s telephone number must be entered in the Modem Number field.

Start

Ensure that your modem is correctly connected and switched on before clicking the Start button to commence processing of the
schedule entries.

After clicking the Start button, “Starting …” will be displayed in the Device Status area. After approximately 10 seconds,
“Processing queue …” will be displayed.

View Log

The View Log button can be used to view a log file containing a detailed record of the GSM Downloader’s actions. This log file
includes all of the detail contained in the activity logs for individual schedule entries, as well as additional information such as
modem errors.

Schedule

The Schedule button can be used to display the Fleet Manager Comms Scheduler Extension window to maintain the schedule
entries. See the Fleet Manager Scheduler Extension documentation for more information.

You can check when the next schedule is due by clicking on the Schedule button to display the Fleet Manager Comms Scheduler
Extension window and examining the Next Due column.

Note: The Next Due column provides an indication of the approximate date and time that a schedule entry will be processed.
Schedule entries are processed synchronously (one at a time), so the actual time that a schedule entry is processed may differ
significantly from it’s Next Due time.

When the next schedule entry falls due, “Dialling <number> …” will be displayed, where <number> is the dialling string that
resulted from applying the dialling rules to the canonical telephone number.

546
www.mixtelematics.com

546
 547

Important: Check that the <number> displayed is the correct dialling string.

During a Download

Whilst a call is in progress, the Hangup button will be enabled. You can use this button to terminate the current call at any time.

The vehicle description will be displayed in the Vehicle field of the Download Status area. The modem will begin dialling the
required number.

If a call is successfully established, “Verifying vehicle ID …” will be displayed in the Device Status area.

If the vehicle ID of the FM unit is verified successfully, the download will be initiated and progress will be displayed in the
Download Status area.

If an error of any kind occurs, an error message will be displayed, the details of the error will be logged in the activity log of the
schedule entry and a retry will be scheduled, provided the maximum number of retries has not been exceeded.

Multiple Downloaders

It is possible to configure more than one GSM Downloader on the network to process the queue of schedules. To facilitate this,
when a schedule entry falls due and is processed by the GSM Downloader, it is “locked” so that other GSM Downloaders will not
retrieve it from the queue. When certain error conditions occur, for example if the GSM Downloader computer is switched off
during processing, the schedule entry will remain “locked” for approximately 2 hours. Should this occur, the schedule entry will
appear to be due (its next due date will be in the past), but the GSM Downloader will not process it. If you do not wish to wait for 2
hours for the schedule entry to be unlocked, you should delete and re-create the schedule entry.

After Download

If the scheduled data transfer is completed successfully, the GSM Downloader will terminate the data call and resume processing
of the queue approximately 20 seconds after the modem device is idle.

Remember: Downloaded trip and event data is written to a file from where it is read and transferred into the Fleet Manager
database by the Fleet Manager AutoPoll Client. Ensure that the AutoPoll Client is running to automate this process. For more
information on the AutoPoll Client please refer to the Fleet Manager AutoPoll Client documentation.

547
www.mixtelematics.com

547
 548
5.3.1 Setting Up And Configuring A GSM Modem

© 2008 MiX Telematics | Updated 2008/06/11

Overview
The purpose of this document is to provide additional information concerning the use of GSM modem devices with FM200 series
on-board computers.

The following topics are covered:

· Hardware

· Device Drivers

· GSM modems supported by FM200 series on-board computers

· Installing a modem with the Fleet Manager on-board computer

· Using HyperTerminal to test a modem

· Configuring the modem to echo all typed characters

· Changing the modem baud rate

· Setting up the modem

· Reading and writing SMS messages

· Call management

· Testing GPRS

· Overview of GSM software

· Configuring a GSM Modem with Fleet Manager Professional 9

Note: The information in this document may not be pertain to all modem devices.

Hardware
A standard off-the-shelf GSM module can be connected to an FM200 series unit via the RS232 port. Please see GSM modems
supported by FM200 series on-board computers section for more information and a list of recommended GSM devices and
requirements. The GSM antenna is to be mounted further than 20cm away from the human body under normal operating
conditions.

Device Drivers
When a GSM module is connected to the FM200 unit for the first time, a set of firmware device drivers must be transferred to the
FM200 unit using a standard 256kb device driver code-plug. These device drivers enable the FM200 unit to communicate with
the GSM module.

The latest version of the FM Dealer Utility should be used to initialise a device driver code-plug with the required device drivers.

GSM modems supported by FM200 series on-board computers

Minimum modem specifications

548
www.mixtelematics.com

548
 549

For your modem to be used with the current release of FM200, FM200Plus firmware and office software it needs to be
configurable to the following minimum specifications.

· RS232 (DTE-DCE) communications

RS232 voltage levels

19200 baud (FM200/Plus configures this)

8 data bits (Pre-Configured)

1 stop bit (Pre-Configured)

RTS-CTS flow control (FM200 configures this)

Controlled lines (RX, TX, RTS, CTS, GND)

DTR and DSR are looped back in the FM communications harness

· Over the air data transfer

Non-Transparent data transfer (From the PC side software only)

Fixed baud rate (V.32) (From the PC side software only)

· Power requirements

The installer should make sure that the installation meets the power requirements of the modem device installed.

· AT commend set

The modem should support the standard Hayes AT command format and conform to the GSM extensions thereof. SMS
messaging should also be supported in both text and PDU modes.

Note: The Siemens M1 terminal does not support SMS messaging in text mode and is thus not suitable for use with the FM200
for SMS functionality.

FM200 Plus (FM200 Plus) Compatible Modems

The following is a list of modems compatible with the FM200 Plus series of on-board computers as well as the communications
methods they support:

Siemens

· M20 Terminal: (SMS and CSD)

· TC35 Terminal: (SMS and CSD)

· MC35 Terminal: (SMS, CSD and GPRS)

· MC35i Terminal: (SMS, CSD and GPRS)

Wavecom

· WM0D2 Terminal: (SMS and CSD)

· C2D Terminal: (SMS, CSD and GPRS)

· Fastrack M1206: (SMS, CSD and GPRS)

549
www.mixtelematics.com

549
 550

Nokia

· 6090: (SMS and CSD)

· 810: (SMS and CSD)

Falcom

· A2D-1: (SMS and CSD)

Note: This list only contains the modems that were tested to work with the FM200 Plus unit. The FM units only use a basic AT
command set and should be compatible with a wide range of available modems.

Installing a modem with the Fleet Manager on-board computer

Make sure the modem you are installing has got the latest firmware installed onto it. If the modem comes with an ignition input, it
is highly recommended that this be connected to the ignition circuit for improved reliability.

GSM Modem Installation Accessories

· FM unit serial cable

FM TTL converter: The original TTL converter (FM: X39-723-002-055) can be used to connect a modem to the FM unit, it is not
recommended though as it only provides 1 serial port.

FM Splitter cable: The FM Splitter cable (FM: X39-723-002-075) can also be used to connect a modem to the FM unit.

FM200Plus serial cable: This cable can be used with the FM200Plus unit and is much more useful than the splitter cable. This
cable provides connection for the FMTerminal as well as two other serial ports.

· GSM modem

Any of the supported modems with the FM unit.

· Modem antenna

The selection of the antenna depends on the modem type and mounting requirements. The GSM antenna is to be mounted
further than 20cm away from the human body under normal operating conditions.

· SIM card

The SIM card should be obtained from your preferred network operator. The SIM card should be enabled to receive incoming
data calls and to send and receive SMS messages if SMS functionality is required.

· GSM diagnostic plug

The GSM diagnostic plug is an essential tool for the installation of GSM modems. A diagnostic plug can be formatted using the
FM Dealer Utility. See the FM Dealer Utility documentation for more information.

· Fleet Manager software

The Fleet Manager software is needed to configure the FM unit to communicate with the modem.

· Modem connector cable

Some modems like the WAVECOM WMOD2 modem needs a converter cable to convert from the DB15 connector on the modem
to the DB9 connector on the FM Splitter. This can be obtained from your modem supplier.

· RS232 extender cable

550
www.mixtelematics.com

550
 551

If the modem cannot be mounted close enough to the FM unit for the converter harness to reach then a RS232 extender cable
(straight through) can be used between the modem and the FM unit. Not recommended though.

· Relay for modem power control

The external-drive lines from the FM unit can be wired to control the power to the modem. This saves the vehicle’s battery and
allows the modem to be “hard reset” by the FM unit in case of a modem lock-up.

Note: Before you start with the installation make sure you have got all the required components specific to your installation.

Modem Connections
Most modems require three (types of) connections:

· Antenna

· Power

· Serial cable

Antenna

The antenna is the simplest as it has got no active connection to the FM unit. Refer to your modem documentation to find the
details of the antenna that must be used. Note: not all modem manufacturers supply an antenna as part of the modem.

Power

It may be important to control the modem's power consumption to prevent it from draining the vehicle's battery. The Fleet
Manager Client software provides functionality to configure the on-board computer to control power supplied to the modem. You
can configure the on-board computer to switch the modem off x hours after the vehicle is parked or if when the vehicle battery
voltage drops below a certain level.

The physical outputs available for controlling the power to the modem varies depending on the type of FM unit being used. There
are two types of power control outputs provided by the FM units namely “External Relay Drive” outputs and the "Positive Drive"
output. The External Relay Drive outputs can be used to drive an external relay with a maximum current loading of 250mA. The
Positive Drive supplies battery voltage and can be used to supply power to external devices with a maximum current loading of 1
Amp.

Refer to the table below for a list of power outputs available for modems when connected to different unit types..

The table below indicates which physical outputs can be used to supply power to the external or internal GSM modem of each
unit type.

Unit Type External Relay Drive 1 External Relay Drive 2 Positive Drive

FM200 Yes No - FM200 only has 1 External No - FM200 does not have
Relay Drive a Positive Drive

FM200 Plus Yes Yes Yes

FM200 Communicator No -internal modem is connected No - internal modem is connected Yes

to Positive Drive to Positive Drive

Note: Use a fuse in the supply of power to the modem. Refer to the modem specification for details of the fuse size.

Positive Drive power connection: The Positive Drive power and ground lines are only available when the FM200Plus Serial Cable
is connected. The brown wire is ground (permanent) while the red wire is the switched battery voltage line.

551
www.mixtelematics.com

551
 552

External Relay Drive power connection: The External Relay Drive lines require an external relay for controlling the power supply
to the modem. See the connection diagram below for a typical connection.

Note: The relay assigned pin numbers may differ depending on the relay type and manufacturer.

Serial cable

The type of cable supported depends on the type of FM unit used. The table below list the combinations of cables that may be
used. On the FM200 Plus Serial Cable, the longer of the two DB9 connector cables is S2 (if not labelled).

Unit Type FM TTL To RS232 Converter FM Splitter Cable FM 200 Plus Serial Cable

FM200 Yes Yes No

FM200 Plus (FM200 Plus) Yes Yes Yes

FM200 Communicator No No Yes

General installation procedure

1. From the FM Dealer Utility, Load the latest released Device Drivers into unit. For best results it is recommended to use a
Device Driver code-plug.

2. Use the Fleet Manager Client application to correctly specify the vehicle configuration. Using a green vehicle code-plug, load
the configuration into the unit. It is important that this configuration contains the correct PIN code needed to enable the SIM
card. You must also ensure that the configuration contains the correct home-base number (the number of the modem in the
office that receives SMS messages) as well as the correct SMSC (short message service centre) number if SMS functionality is
required. You must ensure that all GPRS settings are specified correctly if GPRS functionality is required.

3. Connect the modem to the FM unit (refer to accessories for connecting cables).

4. Use an RS232 extender cable if required (not recommended).

5. The FM unit will try to initialise the modem to operate at 19200 baud. The Firmware on the FM unit will be able to find the
modem baud rate in the range from 2400 baud up to and including 38400 baud. If the modem is configured to an baud rate
outside of this range the FM unit will not be able to re-configure the modem to 19200 baud (reconfigure it then manually). See
Changing the modem baud rate for more information.

6. Create a GSM/DECT diagnostic plug using the FM Dealer utility.

552
www.mixtelematics.com

552
 553

7. For an audible and visual feedback of the GSM functionality, insert a GSM diagnostic plug in the FM code-plug socket.

8. When the diagnostic plug is inserted you will hear a short double-beep, signalling that the FM unit is configured for GSM
functionality. Any other beeps signal an incorrect configuration of the unit.

9. The code-plug socket LED should flash approximately every 30 seconds indicating that the FM unit is able to communicate
with the modem. This may take longer than 30 seconds the first time the modem is being initialised (in the order of 120
seconds).

10.Once the modem is logged onto the GSM network, the FM unit will issue a single beep in sync with the LED flashes (GPRS
capable modems will issue a double beep).

11.Also check the status LED on the modem itself (most modems have one). Refer to the modem’s documentation for more
information on the meaning of its state.

12.Only proceed with the installation and testing once the diagnostic plug indicates that the FM is communication with the modem
and the modem is registered on the network.

13.Dial the vehicle from another data modem to check that the modem answers the incoming data call. The FM unit will not
automatically answer voice-calls (the FM Keypad is required for managing voice-calls).

14.Send a position request to the vehicle to test SMS messaging to and from the vehicle. The on-board computer will reply to a
position request, even if no GPS is physically connected to the unit.

For more on the GSM diagnostic beep codes refer to Beep and Flash Codes.

Warning: SIEMENS TC35 / MC35 Terminal (only applies when used with an FM200)

"Power Down" mode: The TC35 and MC35 modem has a sleep mode function. When the modem goes into power down mode, it
can only be awakened by either changing the state of the DTR (pin4) line on the modem, or by changing the Ignition input line
state from low to high for longer than 200ms. The FM200 unit has no control over the DTR line, thus it is not able to change the
modem’s state. For this reason, it is recommended that you connect the modem’s ignition input to the vehicles ignition line. The
modem goes into this state when it is outside of GSM coverage for a long time or when the "modem off" at-command is issued.
For this reason, the power down command is not used in the FM200 firmware.

Warning: SIEMENS TC35/MC35 Terminal (applies when used with any FM unit)

It is not recommended to use the option to manage theses modems' power consumption with serial commands. If you do, you
must ensure that the ignition input of the modems is properly connected. Once the Sleep AT command is sent to the modem,
only a change in the modem's ignition input from off to on will wake the modem.

Warning: SIEMENS M1 Terminal

The M1 modem does not support SMS messaging in text mode and is thus not suitable for SMS functionality.

Using HyperTerminal to test a modem

This section explains how to use a terminal program like HyperTerminal to communicate with a serial device like a modem. There
a quite a few terminal applications like HyperTerminal and the user is not restricted to this one only.

What you will need

· RS232 Cable to connect the modem to your PC’s serial port.

· Power supply for the modem (refer to modem documentation)

· Serial port terminal application, e.g. HyperTerminal

Start HyperTerminal

553
www.mixtelematics.com

553
 554

HyperTerminal can be installed from the Microsoft Windows installation disk is not already installed on you PC. Refer to the MS
Windows documentation for more info on the application.

Step 1

This will open the HyperTerminal and the “Connection Description” dialog box.

Step 2

Enter a name that for the HyperTerminal session (if you wish to save it for later use). E.g. “Siemens TC35 on COM1”. Click OK to
open the “Connect To” dialog.

Step 3

Using the “connect using” drop-down-list, select the serial port that the modem is connected to. A serial port can only be used by
one device at a time, so make sure that no other device is using the selected serial port. Click OK to open the serial port physical
settings.

554
www.mixtelematics.com

554
 555

Step 4

Select the baud rate (bits per second) that the modem is currently configured for (refer to the modem’s technical manual). Select
“None” for the Flow control option. Clicking OK would open HyperTerminal connected to the COM1 device.

Step 5

555
www.mixtelematics.com

555
 556

You can now save the settings to be loaded at a later stage. Ensure that Caps-Lock is on when you are communicating with the
modem. It is not necessary, but some modems needs the AT commands in capital letters to synchronize with the PC baud rate.

Step 6

To check it the modem is communicating type the following string: “AT” and press the Enter/Return (¿) key. The modem should
respond with the string: “OK”. If nothing appears while typing the command you can either turn on local-echoing in HyperTerminal
or you can configure the modem to echo all characters that it received. The later is preferred.

For all sections related to sending commands to the modem the following conventions will be followed.

Command ATE1 Turn echoing on

Response OK The modem excepted the command

The first coulomb describes direction of the string. Command is the string entered on HyperTerminal while Response it the string/
s returned from the modem as a response of the command sent to it. When you want to send a command to the modem you type
in the command string followed by the Enter/Return (¿) key. Usually AT commands are entered as capital letters.

Note: If you see “xxxx” as part of a command, read the comments field to see whether you have to enter xxxx or need to replace
that part of the command with your own string!!!!

If the modem is not responding to your commands:

· Check the spelling of your commands (zero and o can easily be confused!)

· Check the baud rate setting on HyperTerminal

Configure modem to echo all typed characters

If you want to see what you are typing you can use the following sequence of command to turn on the echoing function of the
modem.

Command ATE1 Turn echoing on

556
www.mixtelematics.com

556
 557

Response OK The modem excepted the command

Changing the modem baud rate

The first step is to get the modem to respond to commands entered. To check the modem, use the normal AT query. Remember
to give the modem chance to register to the network, as it might only respond once the network log-on was completed
successfully. Also check the LED status on the modem itself (refer to modem user manual).

Test the modem response

Command AT Check is the modem is ready

Response OK Modem interpreted AT command correctly

Change the baud rate in HyperTerminal until you receive a valid response for the test modem command. At this point we have
established communication with the modem. The next step is to check the modem baud rate setting.

Checking the active baud rate setting

Command AT+IPR? Query the modem baud rate setting

Response +IPR: 0 The modem is configured in auto baud detection mode. In this modem you
can communicate to the modem at any baud rate as long as you use capital
letters as the AT commands.

+IPR: xxxx “xxxx” represents the baud rate of the modem as an integer string value.

Set the new baud rate

Command AT+IPR=19200 Setting the modem baud rate to 19200 baud. You can replace the “19200”
with “9600” is the modem needs to be configured to run at 9600 baud.

Response OK Setting accepted.

If the specified baud rate is different to your HyperTerminal setting, then the modem would not respond any longer to AT
command. Change the HyperTerminal baud rate to the value the modem was set to. Use the test command to verify the modem
is responding. At this point you can now save the value as the default baud rate (will be used when the power is disconnected
and re-connected).

Save all the current settings as the power-on defaults

Command AT&W Save all settings

Response OK Command accepted

Setting up the modem

Before you can use the GSM for anything there is a few things to check.

557
www.mixtelematics.com

557
 558

Enable extended error reporting

Command AT+CMEE=1 Enable extended error reporting on AT commands

Response OK The modem excepted the commandErrors will now be reported in the form
“+CEER: Error XX” where XX is the extended error code.

Check if a PIN code is required

Command AT+CPIN? Check Pin code status

Response +CPIN: READY No PIN code is required

+CPIN: SIM PIN You need to enter the PIN for the SIM card

+CPIN: SIM PUK The SIM is locked and requires a PUK code. Use your mobile phone to enter
the PUK code (much safer).

Enter the PIN code if required

Command AT+CPIN=”xxxx” Enter Pin code to the SIM, the string xxxx must be replaced with your SIM's
PIN code. This command may take a few seconds before it responds, as it
might only respond after it registered to the network. Remember that you can
only enter the PIN code 3 times incorrectly after which the PUK code would be
required!!!

Response OK PIN excepted

Check the signal quality/level

Command AT+CSQ Check the signal strength.

Response +CSQ: 16,0 The first value (before the comma) is an indication of how good the reception
is. 99 means that the modem cannot determine the signal strength otherwise
the value would be in the rang from 0 to 31, where 31 means perfect and 1 is
very poor.

Check the network registration status of the SIM card

Command AT+CREG? Check the modem registration status.

Response +CREG: 0,1 The second value (after the first comma) is the status of network registration.
Valid values:0: not registered, ME is currently not searching for new operator1:
registered, home network2: not registered, but ME is currently searching for a
new operator3: registration denied4: unknown5: registered, roaming

When the PIN status is OK and the modem is registered then the modem is ready to accept GSM related commands.

Reading and writing SMS messages

558
www.mixtelematics.com

558
 559

Before you can send SMS messages from the modem the SMS service centre address needs to be specified. Ask your network
provider if you do not know what it is. The number normally should be entered in international format, i.e. starting with a “+”.

Enter SMS service centre address

Command AT+CSCA=”+27832000001” Set your network service centre address

Response OK Service centre address accepted

Check the service centre address

Command AT+CSCA? Query the active service centre address

Response +CSCA: "+27831000002",145 Service centre address is the value before the first comma.

Store the service centre address permanently

Command AT+CPAS Store SIM related settings

Response OK Settings was saved

We are only going to send and read SMS messages in text format, so we need to configure the modem to do so.

Select text modem SMS message format

Command AT+CMGF=1 Enable text mode SMS messaging

Response OK Command accepted

Check the message storage

Command AT+CPMS? Check the available and used message storage

Response +CPMS: “SM” means the message is stored on the SIM

“SM”,0,15,”SM”,0,15,”SM”,0,15
“MT” means the message is stored on the modem

Now we can start with the fun. At this point the modem is configured to read and write SMS messages in text mode.

List all messaged stirred on the modem

Command AT+CMGL=”ALL” List all stored SMS messages

Response +CMGL: 1,”REC UNREAD”,”081234569”, This is Settings was saved

the message text+CMGL: 2,”REC
UNREAD”,”081234569”, This is the message
text… Etc.

559
www.mixtelematics.com

559
 560

Read a specific message

Command AT+CMGR=x Read a message stored on the specified storage

location “x”.

Response +CMGR: "REC Display the selected messaged detail

READ","+27836414132", ,"03/12/17,11:42:37
+08"

Delete a message

Command AT+CMGD=x Deletes the message stored on the specified storage location “x”.

Response OK Message was deleted

Sending an SMS message is a bit more involved and takes 3 steps to execute. First the command is entered, then you need to
wait for the prompt to enter the message body and finally the send key-stroke to transmit the message. To terminate the
message body without sending it, use the Escape key (Esc).

Sending an SMS message

Command AT+CMGS=”PhoneNumber” Start to send an SMS message

Response > Prompt to receive the message body

Command type your message mode text now Enter the message body now

Command Ctrl-z Type the Ctrl-Z key stroke to send the message. (Hold down the
control (Ctrl) key and press z)

Response +CMGS: y The message was sent

Example:
AT+CMGS="0825626159"
> Hello®
+CMGS: 77
Note: DO NOT press the Enter key after entering the message text. Use only Ctrl-z to indicate the end of the message text.

Call management
This section covers placing voice and data calls as well as answering incoming calls

Enable extended call information

Command AT+CRC=1 Enable extended call information

Response OK Command accepted

560
www.mixtelematics.com

560
 561

Enable caller line identity

Command AT+CLIP=1 Switch on caller line identity, not supported on all modems. For
the modem to report the CLI the other party must have “send own
number” enabled and the SIM in the modem has to be enabled to
receive CLI. Ask your service provider for more info.

Response OK Command accepted

When an incoming call is received the modem sends unsolicited strings to HyperTerminal.

+CRING: ASYNC (Signals the type of incoming call, data call in this case)

+CLIP: “0839876543”,xx (signals the calling party’s number)

Placing a voice call

Command ATDxxxxxxxx; Dials a GSM phone number, the semi-colon “;” at the back signals
a voice call.

Response OK The called party answer the call

Placing a data call

Command ATDxxxxxxxx Dials a GSM phone number

Response OK The called party answered the call

CONNECT The modem connection was successful

NO CARRIER The call was terminated/not available

BUSY The called party is in another call

When a modem is in a data call then it does not accept any AT commands. To make it accept AT commands there is a special
character sequence that needs to be sent to the modem:
<do not type anything for 1 second>
+++
<do not type anything for 1 second>
the modem will now respond with an OK to signal that it is in command mode

Terminating a call (hang-up)

Command ATH Terminate any calls

Response OK Command accepted

Testing GPRS

561
www.mixtelematics.com

561
 562

This section of the document will explain how to determine whether or not your modem is GPRS capable. The simplest test is to
query the GPRS PDP context activation status. For an explanation of how to do a more comprehensive GPRS test, please see
Testing GPRS SIM Cards.

Get the GPRS PDP context activation status

Command AT+CGACT? GPRS PDP context activation status

Response ERROR Command not known, this modem cannot be used for GPRS with
the FM unit

+CGACT: 1,0 The modem understood the command, and has got an inactive PDP
context.

Define a PDP context

Command AT+CGDCONT=1,"IP","internet" Define a PDP context, where “internet” is the APN string

Response OK Context defined

Create a new GPRS session

Command ATD*99***1# Create a new GPRS session using context #1

Response CONNECT Connected to the GPRS network

~ }#À!}!}!} }6}!}$}%Ü}"}&} } } } }'}"} PPP configuration strings

(}"}#}$À#&´~

Overview of GSM Software

SMS Processor

The Fleet Manager SMS Processor is used to send and receive GSM short message service (SMS) messages to and from
FM200 series on-board computers equipped with GSM modems. Messages are sent and managed using the Fleet Manager
Active Tracking and Messaging Extension.

GSM Downloader

The Fleet Manager GSM Downloader utilises a telephony device such as a modem to transfer information to and from FM200
series on-board computers equipped with GSM modems using GSM circuit-switched data (CSD) calls. Data transfer schedules
are defined and managed using the Fleet Manager Comms Scheduler Extension. Information downloaded from the on-board
computers is written into files which are transferred into the Fleet Manager database by the Fleet Manager AutoPoll Client.

Wireless Internet Service (GPRS & WLAN)

The Fleet Manager Wireless Internet Service (GPRS & WLAN) is used to send and receive messages and transfer data to and
from FM200 Plus series on-board computers equipped with GSM modems using the general packet radio service (GPRS).
Messages are sent and managed using the Fleet Manager Active Tracking and Messaging Extension. Data transfer schedules
are defined and managed using the Fleet Manager Comms Scheduler Extension. Information downloaded from the on-board
computers is written into files which are transferred into the Fleet Manager database by the Fleet Manager AutoPoll Client.

Configuring a GSM modem

562
www.mixtelematics.com

562
 563

The Fleet Manager Client application allows you to specify how the FM200 unit interacts with the GSM module.

Step 1

The Device tab of the Vehicle Properties dialogue is used to specify that a GSM module is connected to a serial port of the FM
unit.

Double clicking on the relevant serial port entry in the list box displays the Device Connection dialogue.

Step 2

Select GSM Modem in the devices tab. Click on the Modem tab.

Step 3

Enter the PIN code and Modem initialization string.

Important: You must remove the SIM card from the GSM module and make use of a mobile phone to update the PIN code for the
SIM card if necessary. For security reasons, changing the PIN code in the Vehicle Properties dialogue does not update the PIN
code in the device. If the PIN code entered into the Vehicle Properties dialogue does not match the PIN code in the GSM module,
the GSM module will not be able to log onto the GSM network.

If you have an FM Keypad and wish to use it to make voice calls, enable voice communications and select the voice channel to
be used with your hands free kit.

563
www.mixtelematics.com

563
 564

Step 4

Click on the CSD Tab.

Set the data number of the GSM modem that is connected to the FM unit. All telephone numbers must be entered in canonical
format by specifying a country, city or area code and local number. This is so that the GSM Downloader can translate them into
valid dialling strings using the Windows dialling rules. This is described in more detail below.

Step 5

Click on the SMS tab

564
www.mixtelematics.com

564
 565

This tab is used to configure the SMS settings for this unit. To enable SMS communications, enable the relevant check box on
this tab and complete the settings on this tab. The SMS limit from the unit to the office determines how many SMSes the unit will
be allowed to send per day. The SMS limit from the office to the unit determines how many SMS messages will be allowed to be
sent to the unit from the office.

Step 6

Click on the GPRS tab.

This tab is used to configure the GPRS settings for this unit. To enable GPRS communications, enable the relevant check box on
this tab and complete the settings on this tab.

The APN, User name and Password must be obtained from your network service provider.

The Server IP Address and Server IP Port must be set to those of the computer hosting the Fleet Manager Wireless Internet
Service (GPRS & WLAN).

Also see GPRS Questions and Answers for more information on these settings.

565
www.mixtelematics.com

565
 566

Step 7

Click the Advanced button.

If your cellular network charges for every GPRS Connection made, you may limit the number of connections per day. Otherwise,
you should leave this unchecked.

Specify the frequency that Automatic Vehicle Location (AVL) packets should be sent by the unit. AVL packets serve two
purposes. Firstly, they keep the GPRS connection alive and prevent the unit's IP address from changing. On most GPRS
networks, dormant connections will be terminated after 5 to 10 minutes. Secondly, they include GPS position information useful
for Active Tracking.

Note: setting the AVL period for out-of-trip to less than 30 seconds, will cause power management to be bypassed. The GSM unit
will remain switched on permanently.

566
www.mixtelematics.com

566
 567

Step 8

Click on the Packet Comms tab.

The Packet Comms tab is used to specify whether packet based communications (such as GPRS) should be used for active
events and messaging.

You may also configure the unit to send end-of-trip (EOT) download active events. This will cause the office software to
automatically perform a quick download at the end of each trip.

Step 9

567
www.mixtelematics.com

567
 568

Click on the Database tab.

The database tab is used to filter the storage of AVL packets in the database. As described above, AVL packets server two
purposes. If you require AVL packets to be sent to keep the GPRS connection alive, you may not wish to store all AVL packets in
the database. In the same way, if your FM unit does not have a GPS receiver connected, you may not wish to store AVL packets
in the database.

Step 10

Click on the Transports tab.

This tab is used to configure the default transports for data transfer, commands and messages for this vehicle. These default
transport values can be over-ridden when defining a schedule with the Comms Scheduler Extension and when sending command
messages, free-text messages or jobs using the Active Tracking and Messaging Extension.

Selected the appropriate default transport values and click the Power tab.

568
www.mixtelematics.com

568
 569

Step 11

Select the appropriate power management options for the modem. See Installing a modem with the Fleet Manager on-board
computer for more information.

569
www.mixtelematics.com

569
 570

5.4 Fleet Manager DECT Downloader

© 2008 MiX Telematics | Updated 2008/05/07

Overview
This document includes the following topics:

· Fleet Manager DECT Downloader Overview

· Fleet Manager DECT Downloader Functionality

· Starting and Configuring the Software

· How it Works

· Analysing Downloaded Data

Fleet Manager DECT Downloader Overview

The Fleet Manager DECT Downloader is a software component used to automatically transfer data to and from DECT-equipped
FM200 and above series units whenever they are within range of the DECT base station.

The DECT Downloader checks continuously to see if a DECT-equipped FM unit is in range of the DECT base station. When a
vehicle is detected, the company ID (transferred automatically when the configuration is uploaded into the Fleet Manager on-
board computer) is verified against that stored in the Fleet Manager database, and if it is valid, the required data is transferred to
and from the FM unit over the airwaves.

Fleet Manager DECT Downloader Functionality

The DECT Downloader can be used to perform the following operations:

· Perform a quick or full download of trip and event data

· Perform a quick or full download of interval (tacho) data

· Synchronise the Fleet Manager on-board computer’s date and time with the personal computer

· Upload a new event configuration

· Upload new device drivers

Downloaded data is written to files from where it is read and transferred into the Fleet Manager database by the Fleet Manager
AutoPoll Client. For more information on the AutoPoll Client please refer to the Fleet Manager AutoPoll Client documentation.

Starting and Configuring the Software

Launch the Fleet Manager DECT Downloader using the shortcut created by the install set. Unless otherwise specified during
installation, this shortcut is created in the Fleet Manager Office folder beneath the Programs folder on the Start menu.

The install set also creates an additional shortcut in the Startup folder so that the DECT Downloader runs automatically when
your computer is restarted.

The DECT Downloader can be configured to use a database on the LAN or at a remote location. This database connection is
configured using the Fleet Manager Administrator which can be launched from the shortcut in the Windows Control Panel. If the
database connection is configured to use an FM-Web database on the LAN or to connect to an FM-Web remote URL, the
downloader login credentials must be supplied. Refer to the Fleet Manager Administrator documentation for more information on
how to set these credentials.

570
www.mixtelematics.com

570
 571

When the DECT Downloader is running, the following icon is displayed in the task bar:

Double-click on this icon or right click on it and click on the Configure menu option to display the DECT Downloader configuration
dialog.

Settings

· Select whether you would like the DECT Downloader to perform quick or full downloads of trip end event data, as well as
whether or not to download interval (tacho) data.

· Drop down the Serial Port combo box and select the serial port that the DECT base station module is connected to.

· Click the Upload Settings button to display the Upload Settings dialog:

571
www.mixtelematics.com

571
 572

Indicate whether to synchronise date and time, upload event configuration and/or upload device drivers by clicking in the
appropriate column adjacent to the required vehicle description. The actions specified in this dialog will be taken the next time the
specified vehicle/s make a connection to the base station.

Note: These actions occur only once and are reset once they have been executed successfully.

View Log

The View Log button can be used to view a log file containing a detailed record of the DECT Downloader’s actions. This log file
includes information such as communications errors. It is important that you check the log file from time to time to ensure that all
vehicles are being downloaded successfully.

Ensure that your DECT base station module is correctly connected and switched on before clicking the Start button.

How it works
When a DECT equipped vehicle is within range of the base station module, the in-vehicle DECT module initiates a connection to
the base station and the red connection indicator on the DECT Downloader configuration dialog turns green. If data has not
already been transferred to or from the unit, the vehicle description will be displayed in the Vehicle field of the Download Status
area and progress will be displayed as data is transferred. If an error of any kind occurs, an error message will be displayed,
while the details of the error will be logged in the log file.

After data has been successfully transferred, the in-vehicle DECT module disconnects from the base station. It then immediately
tries to initiate another connection to the base station module. The DECT Downloader software recognises that the unit has
already been downloaded and instructs it to hibernate (sleep) for 60 minutes so that other in-vehicle modules can be given the
opportunity to connect. During this 1-hour hibernation period, the in-vehicle module will not attempt to establish a connection with
the base station.

After the 1-hour hibernation period has elapsed, the in-vehicle module will once again establish a connection to the base station.
At this point, the DECT Downloader will check to see when data was last transferred to or from the unit. If this occurred within the
“Minimum interval (hours) between downloads” (by default 12 hours, but you can change this), it will once again instruct the unit
to hibernate for 60 minutes, giving other modules a chance to download. This cycle is repeated until the “Minimum interval
(hours) between downloads” has elapsed, after which data will once again be transferred to or from the unit.

572
www.mixtelematics.com

572
 573

Remember: Downloaded data is written into files from where it is read and transferred into the Fleet Manager database by the
Fleet Manager AutoPoll Client. Ensure that the AutoPoll Client is running to automate this process. For more information on the
AutoPoll Client please refer to the Fleet Manager AutoPoll Client document.

Analysing Downloaded Data

Once data has been downloaded via the Fleet Manager DECT Downloader, it is no different from data downloaded via code-
plugs and normal methods of analysing or reporting on the data can be used.

573
www.mixtelematics.com

573
 574
5.4.1 Setting Up And Configuring FM DECT Modems

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The purpose of this document is to describe how to connect the FM DECT communications module (FM DECT X10-723-002-010)
to the Fleet Manager on-board computer and how to configure the unit to facilitate automated remote transfer of data.

Hardware
An FM DECT module can be connected to an FM200 unit via the RS232 port.

An FM DECT Base Station can be connected to the personal computer via the serial port (COM1 or COM2) to facilitate
automated downloading of information from DECT-equipped FM units.

· FM DECT vehicle kit X10-723-002-010

· FM DECT Base Station X10-723-002-011

Please see “Appendix A – FM200 DECT Interface” for more information.

Hardware Configuration
No configuration of the FM DECT hardware is required. The solution is designed to be plug & play. All necessary settings are
transferred with the vehicle configuration. The base station is configured automatically by the Fleet Manager Professional (or
higher) office software.

Device Drivers
A set of firmware device drivers must be transferred to the FM unit using a standard 256kb data plug. These device drivers
enable the unit to communicate with the DECT module.

The FM Dealer Utility software should be used to initialise a data plug with the required device drivers. Please consult the FM
Dealer documentation for more information.

Fleet Manager DECT Downloader

The Fleet Manager DECT Downloader is a software component used to automatically transfer data to and from your DECT
equipped FM200 units whenever they are within range of the DECT base station.

If you do not already have the DECT Downloader installed, please install it.

Important: The DECT Downloader requires Fleet Manager Professional 9 or higher.

Configuring DECT-equipped FM units

The Fleet Manager software allows you to specify that a DECT module is connected to the FM unit.

Step 1: Set up the Device in Vehicle Properties

The Device tab of the Vehicle Properties dialog is used to specify that a DECT module is connected to a serial input of the FM
unit.

574
www.mixtelematics.com

574
 575

Double clicking on the relevant serial entry in the list box displays the Device Connection dialog.

Select the DECT device in the list.

Step 2: Select Transfer Transport Setting

Click on the Transports tab and select the default transports for this vehicle’s FM unit. If the vehicle only has a DECT device for
communications, only DECT will appear in the default data transfer transport setting and the default command transport setting
will not be applicable. If this unit has a messaging device such as an FM Terminal connected, the configuration upload transport
will appear in the messages setting. Otherwise this setting is not applicable.

575
www.mixtelematics.com

575
 576

Step 3: Select Power Management Settings

Click on the Power tab and specify the appropriate power management settings for the DECT unit.

Click OK to close the Device Connection dialog.

576
www.mixtelematics.com

576
 577

Click OK to close the Vehicle Properties dialog.

Step 4: Upload Vehicle Configuration

The software will prompt you to upload a new configuration into the FM unit:

If you have the green code-plug for the vehicle, insert the plug into the download module and click the Yes button. The updated
vehicle configuration will be transferred onto the green plug.

If you do not have the vehicle’s green plug, click the No button, but then remember to use the Initialise Plug Wizard accessible
from the Code Plug menu to update the vehicle’s green plug at a later stage.

Remember: You must upload the new configuration into the FM unit by inserting the green code-plug into the code plug socket in
the vehicle. If you do not do this, the DECT module will not function.

Appendix A – DECT modules & FM200 components

Description

The latest set of device drivers must be loaded onto the FM unit to enable the connection of a DECT module. The DECT module
is connected to the FM unit through the FM Splitter, thus the Terminal and the DECT module can be used at the same time on
the unit.

Recommended DECT module

The following DECT module has been verified to work with FM200 and above.

· FM DECT kit (X10-723-002-010)

DECT Module Characteristics

The FM DECT module has the following characteristics:

· Radio Coverage indoor up to 50m, outdoor up to 300m

· Interface with RS232 Voltage levels on a DB9 Female connector.

· Baud rate = 19200, No Parity, 8bits, 1 stop bit, RTS-CTS flow control

· Connection Pins – (RS232), {RX: PIN2, TX: PIN3, RTS: PIN7, CTS: PIN8, GND: PIN5}

· Accepts 8V to 25V power

· Connection Pins – (POWER), {GND: PIN1, 8 & 9 ; 8..25V DC: PIN 6 & 7}

· Extended AT command set (DECT specific)

· Transparent asynchronous data communication

· Conforms to Siemens DECT Engine MD32 interface specifications

577
www.mixtelematics.com

577
 578

DECT Initialisation

It is not necessary to initialise the FM DECT module manually. It is important to note that the in-vehicle DECT modules connected
to the FM units and the base station DECT module connected to the personal computer must be running the identical version of
firmware, otherwise they will fail to communicate (default setting).

DECT Required components

The following is needed to DECT enable an Fleet Manager on-board computer:

· FM DECT module with antenna (X10-723-002-010)

· 12V or 24V power connection (Automotive and PC supply; PC supply shown)

· FM Splitter

The following is needed to configure a FM DECT base station connected to a personal computer. (Figure 3)

· FM DECT Base Station (X10-723-002-011)

· 12V power connection (PC supply)

· Standard serial cable (not included in the FM DECT Base Station kit)

Figure 1 – In-vehicle installation components

Figure 2 – FM DECT Base Station

578
www.mixtelematics.com

578
 579

Figure 3 – FM DECT Base station components

External power control

Provision has been made to switch the power to the modem off to protect the vehicle battery from running down.

Use an external relay or the positive drive output of the on-board computer to control the power to the modem so that it will be
switched off one hour after the ignition has been switched off.

Set the configuration in the vehicle property dialog.

579
www.mixtelematics.com

579
 580

5.5 Fleet Manager GPRS Service

© 2008 MiX Telematics | Updated 2008/06/12

Overview
The Fleet Manager Wireless Internet Service (GPRS & WLAN) facilitates data transfer and messaging between Fleet Manager
on-board computers equipped with GPRS-capable GSM Modems and the Fleet Manager Database.

Note: This document should be read in conjunction with the following documents:

· GPRS Questions and Answers

· Setting Up And Configuring A GSM Modem

· Testing GPRS SIM Cards

How Does It Work?

What is GPRS?

Please refer to GPRS: Questions and Answers for more information on GPRS and its use in the Fleet Manager system.

Pre-requisites
The Wireless Internet Service (GPRS & WLAN) must always be installed on a PC that has a permanent Internet connection.

The Wireless Internet Service (GPRS & WLAN) supports two modes of operation; stand-alone mode and gateway mode.

· In stand-alone mode, the computer communicates directly with the Fleet Manager units over the Internet.

· In gateway mode, the computer communicates with the units through the Fleet Manager GPRS Gateway hosted on the
Internet. The primary advantage of using the Fleet Manager GPRS Gateway is that your Wireless Internet Service (GPRS &
WLAN) computer does not require a fixed public IP address, which may be difficult or costly to obtain.

Stand-alone mode:

When running the Wireless Internet Service (GPRS & WLAN) in stand-alone mode, you require the following:

Fixed public IP address

The Wireless Internet Service (GPRS & WLAN) computer requires a fixed public IP address. Please speak to your Internet
Service Provider (ISP) to obtain this.

Once the Wireless Internet Service (GPRS & WLAN) has been installed and configured, its IP address is set in the event
configuration of the FM units by editing their GSM Device Properties and uploading the new event configurations.

580
www.mixtelematics.com

580
 581

Note: A fixed public IP address is the same type of address required to host a permanent Internet web site. It must be a fixed IP
address and not a dynamically allocated IP address. It must be a public Internet IP address (i.e. permanently available on the
public Internet) and not an IP address on a private network.

A port open for UDP

The Wireless Internet Service (GPRS & WLAN) utilizes the User Datagram Protocol (UDP) to communicate with the Fleet
Manager units. In addition to the fixed public IP address described above, the Wireless Internet Service (GPRS & WLAN) must
be able to accept inbound and outbound UDP connections on a specified port. By default the Wireless Internet Service (GPRS &
WLAN) will use port 2000, but you can configure it to use any port. Please speak to your Internet Service Provider to obtain a
suitable port number for use with the Wireless Internet Service (GPRS & WLAN) and to ensure that their firewall is open for in-
and outbound UDP connections on that port.

Gateway mode:

When running the Wireless Internet Service (GPRS & WLAN) in gateway mode, you require the following:

Valid current FM Upgrade+ registration

You must have a current, valid FM Upgrade+ registration code to make use of the Fleet Manager GPRS Gateway. See FM
Upgrade+ (Registering Your Software) for more information on the FM Upgrade+ programme.

Fleet Manager GPRS Gateway settings

Speak to your Fleet Manager dealer to obtain the settings required to access the Fleet Manager GPRS Gateway and consult the
section below which describes how to configure the Wireless Internet Service (GPRS & WLAN) to use the gateway.

581
www.mixtelematics.com

581
 582

The following paragraphs will specify the usage of the Proxy type field of the Gateway settings.

Gateway Access to the internet via "No Proxy (UDP)"

This option allows you to connect to the Fleet Manager GPRS Gateway using a UDP connection.

A port open for UDP

In this mode the Wireless Internet Service (GPRS & WLAN) utilizes the User Datagram Protocol (UDP) to communicate with the
Fleet Manager GPRS Gateway. The Wireless Internet Service (GPRS & WLAN) must be able to accept inbound and outbound
UDP connections on a specified port. By default the Wireless Internet Service (GPRS & WLAN) will use port 2000, but you can
configure it to use any port. Please speak to your Internet Service Provider to obtain a suitable port number for use with the
Wireless Internet Service (GPRS & WLAN) and to ensure that their firewall is open for in- and outbound UDP connections on that
port.

Gateway Access to the internet via "No Proxy (TCP)"

This option allows you to connect to the Fleet Manager GPRS Gateway using a TCP connection.

TCP access to the internet

In this mode the Wireless Internet Service (GPRS & WLAN) uses the TCP to communicate with the Fleet Manager GPRS
Gateway. The Wireless Internet Service (GPRS & WLAN) must be able to make outbound TCP connections to the specified port
of the Fleet Manager GPRS Gateway.

Gateway Access to the internet via "Socks4", "Socks4A", "Socks5" or "HTTP 1.1"

This option allows you to connect to the Fleet Manager GPRS Gateway via a proxy server using a TCP connection. This option
will also enable users inside a firewall to access the Fleet Manager GPRS Gateway.

Access to proxy server

In this mode the Wireless Internet Service (GPRS & WLAN) uses the TCP to make a connection to the specified proxy server.
The proxy server will then allow the Wireless Internet Service (GPRS & WLAN) to make a connection through the firewall to the
Fleet Manager GPRS Gateway.

How does the Wireless Internet Service (GPRS & WLAN) work?
The Wireless Internet Service (GPRS & WLAN) uses the GPRS network to send messages and jobs created using the Active
Tracking and Messaging Extension, to receive active events and messages from vehicles, and to processes schedule entries
defined using the Comms Scheduler Extension.

When a vehicle initiates a GPRS connection to the office (refer to GPRS: Questions and Answers for more information on how to
do this), the vehicle ID is verified. If it is valid, queued messages are sent and pending schedules are executed. Downloaded trip
and event data is written to files from where it is read and transferred into the Fleet Manager database by the Fleet Manager
AutoPoll Client.

The FM Service Manager

The Wireless Internet Service (GPRS & WLAN) is not an executable program, and can therefore not be run from the Windows
“Start” menu. It is a Service, and should be started from the FM Service Manager, which can be found under Control Panel.

When the FM Service Manager is launched, a system tray icon will be displayed.

Right click on this icon in the system tray and click Open to access the Service Manager window.

582
www.mixtelematics.com

582
 583

You will see the Wireless Internet Service (GPRS & WLAN) listed, provided you chose to install it when you installed the Fleet
Manager Communications Suite. From here you can Start, Stop and Re-Start the service by using the relevant icons or menu
items. You can also configure the Wireless Internet Service (GPRS & WLAN) by double-clicking it in the list view.

Port Number is the IP port number that the Wireless Internet Service (GPRS & WLAN) will use to "listen" for incoming UDP
connections from the FM units. If you are using a fixed public IP address, this will be the port supplied by your ISP. In this case,
your FM units must be configured to connect to the fixed public IP address of the Wireless Internet Service (GPRS & WLAN) and
to use the same port number that the service is configured to use

583
www.mixtelematics.com

583
 584

Maximum Concurrent Downloads specifies how many communications schedules can be processed in parallel. This setting
should not typically be changed.

Create Detailed Log turns on detailed logging used for troubleshooting and advanced diagnostics. Detailed log files will be
produced in the Detailed Log folder specified in the Paths frame.

Configuration Upload and Download directories is used for storing temporary data.

A Notification Rules File can be specified enabling sending of handset and e-mail notifications. See Handset & E-Mail
Notifications In The Fleet Manager System.

Connect to Fleet Manager GPRS Gateway is used to configure the Wireless Internet Service (GPRS & WLAN) to use the Fleet
Manager GPRS Gateway, and should be used if you do not have a fixed public IP address to host your Wireless Internet Service
(GPRS & WLAN). Speak to your Fleet Manager dealer for more information on the Fleet Manager GPRS Gateway.

The Gateway IP Address and Gateway Port are used to specify the Fleet Manager GPRS Gateway’s fixed public IP address and
port numbers. The default values may be used.

Please note: When running in gateway mode, remember to configure all vehicles to connect to the gateway IP address and port
number. It is critical that the FM Wireless Internet Service (GPRS & WLAN) is set up to point to the gateway before any vehicle
configurations are changed. Vehicles should not be configured to access the gateway before the Wireless Internet Service
(GPRS & WLAN) does so, as this could lead to data loss or corruption.

584
www.mixtelematics.com

584
 585

The Gateway Server Keep Alive value specifies how often your Wireless Internet Service (GPRS & WLAN) will contact the Fleet
Manager GPRS Gateway, and should not typically be changed, as your dynamic IP address may expire if the delay is made too
long.

FM Upgrade+ Package Number is used to enter the number from one of your registered FM Upgrade+ packages. You must have
a valid FM Upgrade+ registration code to make use of the Fleet Manager GPRS Gateway. See FM Upgrade+ (Registering Your
Software) for more information on the FM Upgrade+ programme.

The Proxy Type field should specify the means of connecting to the internet. The default method is "No Proxy (UDP)". Depending
on this selection some of the other fields might be required.

The Proxy IP Address and Proxy Port Number fields specify the Proxy server to be used for Internet access.

The Proxy User Name and Proxy Password fields should only be filled if your proxy server requires these.

Fields are applicable to types of proxy servers

No Proxy (UDP/
Socks4 Socks4A Socks5 HTTP 1.1
TCP)

Proxy IP Address N/A Required Required Required Required

Proxy Port
N/A Required Required Required Required
Number

Proxy User Name N/A N/A N/A Optional Optional

Proxy Password N/A N/A N/A Optional Optional

Note: After you have changed settings, the Wireless Internet Service (GPRS & WLAN) must be restarted before the new settings
will take effect.

Fleet Manager GPRS Gateway – Trouble shooting

When running in gateway mode after starting or restarting the Wireless Internet Service (GPRS & WLAN), it is recommended that
you look at the Windows Event Log to determine if the operation was successful. The Event Viewer can be opened from the
Control Panel, Administrative tools.

585
www.mixtelematics.com

585
 586

Click on the Application node, and inspect the most recent Wireless Internet Service (GPRS & WLAN) logs by double-clicking on
an Event with Source = “GPRSService”.

You should see an Event stating “Service Started”.

586
www.mixtelematics.com

586
 587

If you are using the Fleet Manager GPRS Gateway, you should check the Event Viewer to determine whether a successful
connection was made to the gateway. A message will be added to the Event Log approximately 30 seconds after starting the
service.

The following events may be added to the Event Log:

587
www.mixtelematics.com

587
 588

This indicates that a successful connection was made to the gateway service.

588
www.mixtelematics.com

588
 589

The FM Upgrade+ package number you supplied is not valid. Please ensure that the number you supplied is for a normal FM
Upgrade+ package and not for an Extension.

589
www.mixtelematics.com

589
 590

The FM Upgrade+ cover for the package number you supplied has expired. Please contact your Fleet Manager dealer to
purchase renewal packages to update your FM Upgrade+ cover.

590
www.mixtelematics.com

590
 591

Your Company ID is not unique. This is a potential problem when using the Fleet Manager GPRS Gateway as your Company ID
is used by the gateway service to route data from your vehicles to your computer. Using the same Company ID as another
company could result in data loss or corruption. It is therefore necessary for you to change your Company ID using the
Organisation Properties dialog in the Fleet Manager Professional software. Please note that should you do this, you must upload
the event configuration to all vehicles in your fleet.

591
www.mixtelematics.com

591
 592

The Wireless Internet Service (GPRS & WLAN) is not able to communicate with the Fleet Manager GPRS Gateway. Check that
your Internet connection is activated. Check that you entered the gateway IP address and port number correctly. Also contact
your Internet service provider and ask them to check that the firewall is opened for UDP packets on the specified port.

SQL Login – Trouble shooting

It is recommended that your Fleet Manager System database be set up using the SQL login “sa”, with administrative password.

If this is not the case (and you are using NT authentication) you may need to assign a User Login & Password to the Fleet
Manager Wireless Internet Service (GPRS & WLAN). This can be done from the Windows Service Manager under Control Panel.

592
www.mixtelematics.com

592
 593
5.5.1 GPRS Product Fact Sheet

© 2008 MiX Telematics | Updated 2008/05/07

Overview
General Packet Radio Service (GPRS) is a new non-voice value-added service that allows information to be sent and received
across a mobile telephone network. It enables networks to offer 'always-on', higher capacity, Internet-based content and packet-
based data services. Within the mobile phone context, it enables services such as colour Internet browsing, e-mail on the move,
powerful visual communications, multimedia messages and location-based services. GPRS is an extension of the Global System
for Mobile Communications (GSM), which is a digital protocol that is the most widely deployed wireless standard in the world.
Most GSM service providers support GPRS as the upgrade path to third generation (3G) mobile communication systems.

GPRS is NOT related to GPS (the Global Positioning System), a similar acronym that is often used in the context of Fleet
Management.

Key Features of GPRS

Speed Theoretical maximum speeds of up to 171.2 kilobits per second (kbps) can be achieved over GPRS. This is
about three times as fast as data transmission speeds possible over today’s fixed telecommunications networks
and ten times as fast as current circuit-switched data services on GSM networks. This theoretical maximum will
most likely never be supported by network operators as this would require all eight available time-slots to be
utilised. The same time slots are shared with voice data which is the network’s primary source of revenue.

By allowing information to be transmitted more quickly, immediately and efficiently across the mobile network,
GPRS may well be a relatively less costly mobile data service compared to SMS and Circuit Switched Data
(CSD).

Immediacy No dial-up modem connection is necessary; therefore information can be sent or received immediately when
the need arises.

How GPRS Works

The two most common methods for using data transfer are circuit-switching and packet-switching. With circuit-switching
transmission, a dedicated circuit is established across a range of links and then the entire channel is allocated to a single user for
the duration of the connection.

GPRS uses a packet-switching technique to transfer data and signalling in a cost-efficient manner over GSM radio networks and
also optimizes the use of radio and network resources.

With packet-switching transmission, the data is first separated into smaller parts, called packets, which are sent to the user in
sequence. At the receiving end, the packets are assembled into the original data again. The network resources are only utilised
when the user has something to send. When there is no data to be sent, the resources are free to be used by other users.

593
www.mixtelematics.com

593
 594

Limitations of GPRS

There are a number of limitations to GPRS:

· The mobile device must be configured with the Access Point Name (APN) details and can only connect to a single APN.

· On most networks, the up-link (transmission of data from vehicle to office in fleet management terms) is limited to 1 time-slot
which equates to a throughput of 9600 bps. This is the same throughput available via CSD. For the downlink (transmission of
data from office to vehicle in fleet management terms), up to four time-slots are available which equates to a throughput of 39
Kbps. These limitations were chosen by the network operators because the majority of GPRS users are consumers requiring
Internet access from mobile devices, i.e. there is bigger demand for downlink bandwidth. Unfortunately, for fleet management
solutions most of the data will be transferred from the mobile to the office utilising the slower uplink bandwidth.

· A permanent connection to a network provider offering GPRS is required. It is hoped that this connection will be available via
the Internet on most networks.

· The connection between mobile device and office is not point to point (modem to modem) as it is with CSD.

GPRS and Fleet Manager Professional

With GPRS communication a vehicle connects to a fixed public IP address via the GPRS network. Due to the fact that fixed
public IP addresses are generally very difficult and costly to obtain, the GPRS Service supports two modes of operation; stand-
alone mode and gateway mode. Stand-alone mode is aimed at customers who have access to a fixed public IP address, while
gateway mode is aimed at customers who do not have access to or do not want to secure a fixed public IP address themselves.

Please note that all bureau customers have access to the bureau server’s fixed public IP address.

Stand-alone mode:

In this mode the fixed public IP address is on a server connected to the public internet. A GPRS downloader application on the
server enables the server to communicate with the vehicles in the field. Information is downloaded from the vehicle’s on-board
computer and stored in a central database. You can access the vehicle information through the standalone FM Pro software or
through the Bureau.

This model using the standalone FM Pro software is illustrated as follows:

This model using the Bureau is illustrated as follows:

594
www.mixtelematics.com

594
 595

Gateway mode:

In this mode the fixed public IP address is on a gateway called the GPRS Gateway that is hosted on the internet. The vehicle
connects to the GPRS network, which in turns connects to the server at the base station via the GPRS Gateway. A GPRS
downloader application on the server enables the server to communicate with the vehicles in the field. Information is downloaded
from the vehicle’s on-board computer and stored in a central database. You can access the vehicle information through the FM
Pro standalone software.

The gateway model is illustrated as follows:

Fleet Manager GPRS Features

Communication Options FM Fleet Manager offers a range of communication options to

suit your requirements, including code-plugs, DECT, GSM
CSD, GSM SMS and GPRS.

Scheduled trip, event and interval (tacho) data downloads Data can be downloaded from the vehicle at scheduled
intervals with GPRS.

Active Tracking The location of your vehicles can tracked in real-time using
GPRS, without the communication costs of frequent SMS
messages to and from the vehicles.

Real-time Vehicle Status Information The status of the vehicle, such as the current odometer
reading, speed, RPM or status of the analogue inputs can be
retrieved in real-time via GPRS.

Messaging and Active Events Jobs, free text messages and active events can be sent via
GPRS, which is cheaper, faster and more reliable than SMS
messages.

Trickle trip and event data downloads Trip and event data can be transferred into the database as it is
recorded, enabling recent trips and events to be viewed in real-

595
www.mixtelematics.com

595
 596

time.

Advantages of GPRS over CSD

GPRS is not the direct replacement of CSD. GPRS is an extension to current GSM communications technology. Due to the
limitations of GPRS described above, it is more suitable for messaging and tracking than for downloading.

Advantages of GPRS over CSD include the following:

· GPRS is ‘always online’ enabling the software to request GPS positions in real-time, without the additional communication
costs and delays experienced with CSD.

· GPRS can manage the positions and status of thousands of vehicles concurrently, without any interference.

· GPRS can support simultaneous downloads from multiple vehicles.

· GPRS can be used to improve communications while keeping the costs down.

596
www.mixtelematics.com

596
 597
5.5.2 GPRS Questions and Answers

© 2008 MiX Telematics | Updated 2008/05/07

Overview
This document provides answers to frequently asked questions about GPRS and its use with the Fleet Manager system.

Questions And Answers

1. What is GPRS?

GPRS (General Packet Radio Service) can be thought of as “wireless Internet”, or “Internet over GSM”. Rather than making a call
and sending a stream of data, with GPRS data is carried from the source (i.e. the GSM modem in the vehicle) to the destination
(i.e. computer in the office) via IP packets.

2. Why would anyone use GPRS?

The decision to use GPRS for data transfer depends on a number of factors: the network provider - especially their quality of
service and support, coverage, pricing structure, service reliability and availability. In many cases it is more economical to use
GPRS instead of other GSM services such as circuit-switched data calls (CSD) or the short message service (SMS) for tracking
and messaging applications.

3. How does GPRS billing work?

This varies from one network to another, but with GPRS you typically only pay for the data that is sent and received, not for the
duration of the connection. Your local network operator will be able to provide you with more information.

4. Is GPRS cheaper and better than other GSM services?

This depends entirely on your network operator and other variables such as the size of your fleet, the nature of your operations
and how you use the FM system. In some cases, it is better to use other GSM services and in other cases it is better to use
GPRS.

5. What Fleet Manager hardware will support GPRS?

The following versions of Fleet Manager hardware support GPRS:

· FM200 Plus with an external GPRS-capable modem (e.g. Siemens MC35)

· FM200 Communicator (includes an integrated GPRS-capable modem)

6. What do I need for GPRS?

Inside the vehicle:

· FM200 Communicator or FM200 Plus with an external GPRS-capable modem (e.g. Siemens MC35).

· The modem needs to be equipped with a GPRS-enabled SIM card.

· The on-board computers must be configured with information specific to the GPRS network:

- Access Point Name (APN) to gain access to the public internet via the GPRS network.

- User name to gain access to the GPRS network.

- Password to gain access to the GPRS network.

· In addition, the on-board computers must be configured with the fixed public IP address and port number of the server in the

597
www.mixtelematics.com

597
 598

office that is running the Fleet Manager Wireless Internet Service (GPRS & WLAN) or the fixed public IP address and port
number of the Fleet Manager GPRS Gateway (see office requirements below). The Fleet Manager Wireless Internet Service
(GPRS & WLAN) forms part of the FM Communications Suite in the FM Professional 8 software release. The FM Professional
8 software can be used to configure the on-bard computers with settings such as the APN, IP address and port number.

In the office:

· FM Professional 8 to configure your units for GPRS communications.

· A computer running the Fleet Manager Wireless Internet Service (GPRS & WLAN).

· A permanent Internet connection, connecting the Fleet Manager Wireless Internet Service (GPRS & WLAN) computer to the
Internet.

· Either a fixed public IP address for the Fleet Manager Wireless Internet Service (GPRS & WLAN) computer (contact your
Internet Service Provider to obtain this) or access to the Fleet Manager GPRS Gateway (contact your Fleet Manager dealer for
more information on the Fleet Manager GPRS Gateway).

· The firewall must be open for UDP connections on a specified (configurable) port. By default port 2000 is used. Contact your
Internet Service Provider to ensure that the firewall is opened as required.

7. What features are supported by GPRS?

All Fleet Manager functions available using other GSM services are available using GPRS including:

· Active Tracking & Events

· Messaging (including jobs and free-text messages)

· Downloading all types of data (trip and event data, interval (tacho) data, etc.)

· Uploading of vehicle configuration and device drivers (firmware), setting the unit's date and time, etc.

8. What is the key difference between GPRS and other GSM services in the FM environment?

With GSM circuit-switched data (CSD), the office computer makes a call to the vehicle to initiate download or upload of data. The
call ends when the transaction is complete. With GSM Short Message Service (SMS), either the office or the vehicle can send a
message.

With GPRS, the vehicle must always initiate a connection to the office before any communications transactions can take place. It
is not possible for the office computer to initiate a communications transaction unless the vehicle has connected to the office
computer first. This is because the GPRS network allocates a dynamic (changing) IP address to the vehicle whenever a GPRS
connection is established. Thus the IP address of the vehicle unit changes continually and the vehicle unit must notify the office
computer of its new IP address before communications can take place.

9. What happens when the FM unit loses its GPRS connection?

If the FM unit looses its GPRS connection, it will attempt to re-establish the connection under any one of the following
circumstances:

· When it receives an SMS message from the office computer requesting a GPRS connection.

· When an event occurs which has been configured to send a message to the office (such as when an Active Event occurs).

· If the unit has been configured to send Automatic Vehicle Location (AVL) packets at a pre-defined interval, it will attempt a
GPRS connection when it is time to send the AVL.

10. How can the office contact the vehicle unit if it can’t initiate a connection?

598
www.mixtelematics.com

598
 599

As mentioned above, the office cannot initiate a connection with the vehicle over GPRS, and instead, relies on the vehicle
initiating a connection to the office. There are a number of possible ways of getting the FM unit to initiate a GPRS connection.
These are described in the answer to Question 9 above.

If you need to download data from a vehicle, you must schedule the download using the FM Comms Scheduler, but the download
will only start when the vehicle connects to the office. Each time the vehicle initiates a connection with the office, the Wireless
Internet Service (GPRS & WLAN) checks whether there are any outstanding communications schedules and executes them.

11. If the vehicle is not connected to the office via GPRS, and considering that the office cannot connect to
the vehicle directly, then what do I do if I need it to connect urgently (e.g. to perform a download)?

There are a number of possible ways of getting the FM unit to initiate a GPRS connection. These are described in the answer to
Question 9 above.

12. If I currently use other GSM services, can I switch over to GPRS?

Yes, you can, provided that a GPRS capable modem and SIM card is installed in the vehicle and you have subscribed to the
Wireless Internet Service (GPRS & WLAN).

13. I have a few vehicles that can only communicate with other GSM services and not GPRS. Can I use other
GSM services for these vehicles and GPRS for the others?

Yes, you can. The communication settings are configured per vehicle. The SMS Processor, GSM Downloader and Wireless
Internet Service (GPRS & WLAN) can be used in parallel to communicate with vehicles using these services.

14. How do I send messages to the vehicle? Will the messages arrive at the vehicle immediately, or only
when the vehicle connects to the GPRS network? Is it the same with Active Tracking?

You use the Active Tracking and Messaging Extension to send messages and jobs to the vehicle via GPRS, in the same manner
as with SMS. Messages are held by the Wireless Internet Service (GPRS & WLAN) until the vehicle initiates a connection to the
office, upon which they will be delivered to the FM unit and appear on the FM Terminal or VDO Dayton display. The same applies
to command messages such as those used to initiate Active Tracking.

15. How often should my FM unit be configured to initiate a GPRS connection?

If permanent connectivity between the Wireless Internet Service (GPRS & WLAN) on the office computer and the vehicle unit is
required, the vehicles units should be configured to send an Automatic Vehicle Location (AVL) packet every 30 to 600 seconds.
This setting varies from one network to another and you should contact your network service provider to find out how often the
GPRS connection is likely to be terminated by the network.

599
www.mixtelematics.com

599
 600

600
www.mixtelematics.com

600
 601
5.5.3 Testing a GPRS SIM card

© 2008 MiX Telematics | Updated 2008/06/12

Overview
The purpose of this document is to explain how to test a GPRS enabled SIM card and settings to ensure that it can gain access
to the public Internet using a PC running Windows XP and a GPRS-capable GSM modem.

These steps should be followed to ensure that the SIM card and settings will function correctly when the SIM card is used in a
GPRS-enabled GSM modem connected to a Fleet Manager on-board computer.

Note: This document should be read in conjunction with the following documents:

· GPRS Questions and Answers

· Setting Up And Configuring A GSM Modem

Getting Started
Some modems, like the Nokia D211, are shipped with application software to automate and simplify this process (refer to the
modem documentation for more information).

Note: If the SIM card requires a PIN number, ensure that the PIN number is entered before you being. For information on how to
enter the PIN number using Hyper Terminal, see Setting Up And Configuring A GSM Modem.

Creating a GPRS connection on Windows XP requires two steps. The first step is to create a modem device and the second is to
create a PPP dial-up connection.

Note: You may need to log into the computer with a user account that has local machine administrative rights in order to
configure the modem device and dialup connection.

Creating a modem device

Step 1

Go to the Control panel

601
www.mixtelematics.com

601
 602

Step 2

Open the Phone And Modem Options dialog as shown below.

Step 3

Add a modem. Some modems can be automatically detected by MS Windows, if not, tick the “Don’t detect modem” tick box.

602
www.mixtelematics.com

602
 603

Step 4

Select a 19200 modem. Note: Your modem should be configured to run at 19200 baud for the XP operating system. For
information on how to check and set the modem baud rate see Setting Up And Configuring A GSM Modem.

Step 5

Select the Serial port to be assigned to the new modem that will be created.

603
www.mixtelematics.com

603
 604

Step 6

At this point a new modem is added to the system.

Step 7

To check if your modem is configured correctly, open the properties dialog of the modem and click on the Diagnostics Tab as
shown. Click the Query Modem button to interrogate the modem.

604
www.mixtelematics.com

604
 605

Step 8

The modem requires extra configuration to initiate a GPRS connection.

Open the modem properties dialog. Click on the Advanced Tab and enter the GPRS Access Point Name (APN) configuration
string as follows:
AT+CGDCONT=1,”IP”,”internet”
“internet” is the APN itself and varies from one network to another. You must obtain the correct APN for public internet access
from your network service provider.

605
www.mixtelematics.com

605
 606

Step 9

Now set up a PPP dial-up connection. To do so, open Control Panel and open the Network Connections dialog.

Step 10

In the Network Connections dialog, choose the Add New Connection option. This will then open the New Connection Wizard.

606
www.mixtelematics.com

606
 607

Step 11

Select the Connect to the Internet option.

Step 12

Select the Set up my connection manually option.

607
www.mixtelematics.com

607
 608

Step 13

Select the Connect using a dial-up modem option.

Step 14

Enter a name for the dial-up connection, for example "MTN GPRS"

608
www.mixtelematics.com

608
 609

Step 15

The universal phone number to dial when making a GPRS connection is “*99***1#”.

Step 16

Make the connection available to all users.

609
www.mixtelematics.com

609
 610

Step 17

Clear all check boxes and fields in the Internet Account Information dialog.

Step 18

The PPP connection you have created will be shown in the Network Connections Dialog.

Test the connection by skipping to step 30. On some networks, it may be necessary to alter the PPP configuration settings to
obtain a successful GPRS connection. Alternative settings are listed in steps 19 to 29.

610
www.mixtelematics.com

610
 611

Step 19

On some networks, it may be necessary to alter the PPP configuration settings to obtain a successful GPRS connection. To do
so, open the Properties dialog of the PPP connection by right-clicking on it and clicking Properties.

Step 20

611
www.mixtelematics.com

611
 612

Click the Configure button beneath the modem description and ensure that the modem is set to use hardware flow control.

Step 21

On the Options tab, uncheck the Prompt for phone number checkbox.

612
www.mixtelematics.com

612
 613

Step 22

The X.25 options are not often used and all X.25 fields should be cleared.

613
www.mixtelematics.com

613
 614

Step 23

On the Security tab, choose the Advanced (custom settings) option and click the Settings button.

614
www.mixtelematics.com

614
 615

Step 24

Only enable the PAP and CHAP protocols. Ensure that the rest are disabled.

615
www.mixtelematics.com

615
 616

Step 25

On the Network tab, ensure that PPP and TCP/IP are selected.

616
www.mixtelematics.com

616
 617

Step 26

Access the PPP settings by clicking the Settings button. Ensure that all check boxes are unchecked.

Step 27

Edit the TCP/IP settings and ensure that the Obtain an IP address automatically and Obtain DNS server address automatically
options are selected.

617
www.mixtelematics.com

617
 618

Step 28

Check the Advanced tab as well.

618
www.mixtelematics.com

618
 619

Step 29

After clicking OK, the PPP-connection you have edited will be shown in the Network Connections Dialog.

Step 30

Double-click on the PPP-connection to connect.

Enter the user name and password required to gain access to the GPRS network. You must obtain the correct user name and

619
www.mixtelematics.com

619
 620

password for the APN you are using from your network service provider.

Step 31

Click OK to initiate the connection..

Step 32

The dial-up connection system tray icon will appear once the GPRS network connection has been established. To view the
connection details, double-click the icon.

620
www.mixtelematics.com

620
 621

Step 33

Test that you have public Internet access by opening your web browser and connecting to a public web site on the Internet.

Note: If your computer is also connected to the Internet via the local area network (LAN), you should disconnect your LAN cable
before testing the GPRS connection to ensure that your web browser only has one path to the Internet.

621
www.mixtelematics.com

621
 622

5.6 Fleet Manager AutoPoll Client

© 2008 MiX Telematics | Updated 2008/06/26

NOTE: The AutoPoll Client is no longer used for standalone systems, and has been replaced by a new downloader service that
runs as a Windows Service, accessible from the FM Services control panel applet.

Overview
The document covers the following topics:

· Overview of the Fleet Manager AutoPoll Client

· Using the AutoPoll Client

· How it Works

· How to implement Remote Downloading

· How to schedule a Data Transfer

· How to enable AutoPoll Backups

Overview of the Fleet Manager AutoPoll Client

The Fleet Manager AutoPoll Client is an application that performs one or both of the following functions:

1. It continuously “polls” a download module connected to your computer and automatically downloads trip, event and/or interval
(tacho) data from green vehicle code-plugs that are inserted into the Download Module’s code-plug socket. Data downloaded
from the code-plugs is stored in a number of files located in a special folder structure named AutoPoll, beneath the folder
where the AutoPoll client was installed (typically C:\Program Files\Fleet Manager Communications Suite\Fleet Manager
AutoPoll Client\AutoPoll).

2. At a specified time interval, the data files created in point 1 are processed by the AutoPoll Client and the information contained
in these files is transferred into the Fleet Manager database which may be on the LAN or at a remote location.

The result is identical to executing either the “Quick Download” or “Full Download” functions from within the Fleet Manager Client
application (depending on the options you specify).

Information downloaded from Fleet Manager on-board computers using the Wireless Internet Service (GPRS & WLAN), GSM
Downloader or DECT Downloader is stored by these applications in identical folder structures to that created by the AutoPoll
Client when code-plugs are downloaded. The AutoPoll Client can be configured to transfer data downloaded by these other
applications into the Fleet Manager database. Please see the documentation for these other applications for more information.

The AutoPoll Client can be installed and configured to perform only the first function (polling of a download module) on a
computer that is disconnected from the Fleet Manager database server. This scenario can be particularly useful for manually
harvesting information at a remote site. As the information gathered by the AutoPoll Client consists of a folder structure
containing files, the data can easily be manually copied, e-mailed, transferred over a low-speed connection etc, from a remote
site to the central database for processing. See the section entitled “How to Implement Remote Downloading” below for more
information.

The AutoPoll Client can be executed with a special command line argument (/NOW) which causes it to perform the second
function (transfer data into the database) once only and then exit. This enables you to schedule the transfer of data into the
database during off-peak times using any scheduling software such as the Windows Task Scheduler. See the section entitled
“How to Implement Scheduled Data Transfer” below for more information.

Using the AutoPoll Client

Starting the software

622
www.mixtelematics.com

622
 623

Launch the AutoPoll Client using the shortcut created by the install set. Unless otherwise specified during installation, this
shortcut is created in the Fleet Manager Office folder beneath the Programs folder on the Start menu.

The install set also creates an additional shortcut in the Startup folder so that the AutoPoll Client runs automatically when your
computer is restarted.

Configuring the software

The AutoPoll Client can be configured to use a database on the LAN or at a remote location. This database connection is
configured using the Fleet Manager Administrator which can be launched from the shortcut in the Windows Control Panel. If the
database connection is configured to use an FM-Web database on the LAN or to connect to an FM-Web remote URL, the
downloader login credentials must be supplied. Refer to the Fleet Manager Administrator documentation for more information on
how to set these credentials.

When the AutoPoll Client is running, the following icon is displayed in the task bar:

Double-click on this icon or right click it and click the Configure menu item to display the AutoPoll Client configuration dialog:

The Fleet Manager AutoPoll Client configuration dialog allows you to:

· Change the language of the AutoPoll Client.

· Change the parallel port number (LPT1 or LPT2) that your download module has been connected to.

Note: This may only be changed when the download module is not being polled. If the port options are disabled, click the “Stop”
button first.

· Configure the AutoPoll Client to do full downloads from code-plugs by checking the “Download all trips” checkbox.

623
www.mixtelematics.com

623
 624

Note: This option can also only be changed when polling is stopped.

· Specify the default site and vehicle configuration group or driver configuration group to use when data for an unknown vehicle
or driver is downloaded by clicking the “Defaults” button.

· Start or Stop polling of the download module by clicking on the “Start” or “Stop” button.

Note: This button applies only to the polling of the download module. The transfer of data to the server cannot be stopped.

· Specify the interval in minutes, at which data should be processed and stored in the Fleet Manager Server Database.

· Process and store all downloaded data immediately by clicking the “Transfer Now” button.

· View the log file by clicking the “View Log” button. An entry is written to the log file each time the AutoPoll Client loads, exits, or
processes data to the server. You should check the log file from time to time to ensure that all units are being downloaded and
processed successfully.

· Configure multiple folders that the AutoPoll Client should read when processing data to the server by clicking the “Advanced”
button. This option is required when installing the “Data Extraction Only” and “Full Product” versions on different computers
within your network. (See the section entitled “How to Implement Remote Downloading” below). This option is also required
when configuring the AutoPoll Client to process data files downloaded by the GSM or DECT Downloader applications.

How it works

When the transfer interval has expired or you click the “Transfer Now” button, the system begins processing all data files
contained within the specified directories.

· If the application is running in local mode, the data within the data files is stored in the Fleet Manager Server Database and
transfer progress is displayed in the “Transfer Status” frame.

· If the application is running in remote mode, the data files are sent to the FM-Web server as specified in Advanced settings. An
AutoPoll Client application that is running on the FM-Web server’s LAN will then process the files into the relevant databases.

In local mode, when data is transferred for a vehicle that does not exist in the Fleet Manager database, the AutoPoll Client will
automatically create a vehicle record with a description of “AutoPoll Vehicle <idnumber>”, and a registration number of
“FMAPC<idnumber>”. Similarly, new driver records will be created automatically, with a default name of “AutoPoll Driver
<idnumber>”.

These vehicles and drivers will be linked to the specified default site and configuration group.

The default names and descriptions assigned to these records can be modified later using the Fleet Manager Client application.

How to Implement Remote Downloading

Automatic Remote Downloading

If the Fleet Manager Database Connection settings have been configured to use a remote connection to an FM-Web server, the
AutoPoll Client will transfer data files to the web server at the specified interval.

Manual Remote Downloading

The Fleet Manager AutoPoll Client performs two functions:

1. It continuously “polls” a download module connected to your computer and automatically downloads trip, event and/or interval
(tacho) data from green Vehicle code-plugs that are inserted into the Download Module’s code-plug socket.

2. Occasionally, at a user-defined time interval, the data files created in point 1 are processed by the AutoPoll Client and the
information contained in these files is transferred into the Fleet Manager database.

624
www.mixtelematics.com

624
 625

When you install the Fleet Manager AutoPoll Client, there are two installation options available, namely “Data Extraction Only”
and “Full Product”.

The “Full Product” option installs the components required for both phase 1 and 2 described above, while the “Data Extraction
Only” option installs only the components required for phase 1.

Remote workstations which are disconnected from the Fleet Manager database or separated from the Fleet Manager database
by a low speed WAN connection can be used as polling stations by selecting the “Data Extraction Only” install option.

Data gathered by a remote polling station can be processed automatically by an AutoPoll Client connected to the Fleet Manager
database over a WAN connection, simply by using the using the “Advanced” button in the AutoPoll Client’s configuration dialog
and adding the appropriate network share/s to the list of folders to be processed.

Files on remote computers may be manually or automatically copied over to the server computer (via e-mail etc.), but care should
be taken to retain the file/folder structures beneath the AutoPoll Folder.

How to Implement Scheduled Data Transfer

The AutoPoll Client can be executed with a special command line argument (/NOW) causing it to perform an immediate transfer
of data files into the database once only, and then exit. This feature enables you to schedule the transfer of data into the
database during off-peak times using any standard scheduling software such as the Windows Task Scheduler.

Different versions of Windows implement the Task Scheduler in different ways. Consult the Windows documentation for your
particular version of Windows for more information. To schedule the AutoPoll Client to transfer data into the database at a
specified time using the Windows XP Professional Task Scheduler, do the following:

1. Ensure that the Windows task scheduler is installed. Consult the Windows documentation for more information.

2. Launch the Task Scheduler from the Start menu. This can be found beneath the Start menu under All Programs, Accessories,
System Tools. The Scheduled Tasks window will be displayed.

3. Click on Add Scheduled Task. The Scheduled Task Wizard will be displayed.

625
www.mixtelematics.com

625
 626

4. Click Next.

5. Click Browse and locate the AutoPoll Client (FMAPCPro.EXE) in the folder you selected when you installed the AutoPoll
software (typically C:\Program Files\Fleet Manager Communications Suite\Fleet Manager AutoPoll Client).

6. Select when you would like the AutoPoll Client to run and complete the remaining steps of the wizard. Ensure that you select
the checkbox to display advance properties in the final step of the wizard.

626
www.mixtelematics.com

626
 627

7. At the end of the field labelled Run, add a space, followed by the /NOW command line argument as follows:

8. Click OK. The AutoPoll Client will now run automatically at the specified time, process the data files into the database and exit.

When the AutoPoll Client executes, it will create an entry in the log file (APCLog.txt) indicating that an immediate transfer has
been performed:
01/05/2002 10:19:03 - Fleet Manager AutoPoll Client is starting
01/05/2002 10:19:04 - Beginning immediate transfer
01/05/2002 10:19:04 - Processing Folder "AutoPoll"
01/05/2002 10:19:04 - Processing Folder "C:\Program Files\Fleet Manager GSM Downloader\AutoPoll"

627
www.mixtelematics.com

627
 628
01/05/2002 10:19:04 - Processing Folder "C:\Program Files\Fleet Manager DECT Downloader\AutoPoll"
01/05/2002 10:19:04 - Fleet Manager AutoPoll Client is shutting down

How to Enable AutoPoll Backups

It is possible to configure the AutoPoll Client to create backup copies of the files contained within the AutoPoll folder structure
after they have been transferred into the database. To do so, you should add a string value to your system registry as follows:

1. Click Start " Run and type regedit to access your registry:

2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Data Pro Development (Pty) Ltd\Fleet Manager\AutoPoll Client.

3. Add BackupFiles as a new String Value to the right hand side (right click to add new String Value) and set the value to be True.

628
www.mixtelematics.com

628
 629

Your Autopoll folders contents will now be backed up every time the AutoPoll Client downloads or transfers data to the database.

629
www.mixtelematics.com

629
 630
5.6.1 FM Downloader Service

The Autopoll Client (APC) is not used for standalone systems any more and has been replaced by a new downloader processor
that runs as a Windows Service. It is ‘accessible’ from the FM Services control panel applet.

There are two services: Fleet Manager Download Preprocess and Fleet Manager Download Process. Each service can only run
once per PC, but you can install on multiple machines. Is now advisable to have the Fleet Manager Download Preprocess
running on each machine that is downloading from vehicles, but only have one Fleet Manager Download Process running in
standalone installations. (FYI: The old system had one APC reading data from shares on each downloader machine.)

EXAMPLE:

· Four servers: 1x Database 1x GPRS, 1x GSMPro, 1x other

· Old FMAPCPro: would be installed on ‘other’ pointing to Database, reading DAT files from GPRS and GSMPro servers.

· NEW: FM Preprocess services running on GPRS and GSMPro. FM Process service running on ‘other’. All three servers
pointing to SQL on Database.

In the Bureau environment multiple FM Process services will automatically load-balance between organisations.

Since the new download service is not remote mode enabled it should only be run on hosted servers. Therefore the ‘old’

630
www.mixtelematics.com

630
 631

FMAPCPro is still supported for downloaders running in REMOTE mode. Standalone installations should not install the
FMAPCPro full installation.

It is possible to control thread count for Preprocess and Process, but this should not be adjusted from 1 unless running into
throughput issues. Increasing these too high will slow the system down.

631
www.mixtelematics.com

631
 632

5.7 Setting Up And Configuring A GSM Modem for GPRS

© 2008 MiX Telematics | Updated 2008/07/03

Overview
The purpose of this document is to provide additional information concerning the use of GSM modem devices with FM200 series
on-board computers.

The following topics are covered:

· Hardware

· Device Drivers

· GSM modems supported by FM200 series on-board computers

· Installing a modem with the Fleet Manager on-board computer

· Using HyperTerminal to test a modem

· Configuring the modem to echo all typed characters

· Changing the modem baud rate

· Setting up the modem

· Reading and writing SMS messages

· Call management

· Testing GPRS

· Overview of GSM software

· Configuring a GSM Modem with Fleet Manager Professional 9

Note: The information in this document may not be pertain to all modem devices.

Hardware
A standard off-the-shelf GSM module can be connected to an FM200 series unit via the RS232 port. Please see GSM modems
supported by FM200 series on-board computers section for more information and a list of recommended GSM devices and
requirements.

Device Drivers
When a GSM module is connected to the FM200 unit for the first time, a set of firmware device drivers must be transferred to the
unit using a standard 256kb device driver code-plug. These device drivers enable the unit to communicate with the GSM module.

The latest version of the FM Dealer Utility should be used to initialise a device driver code-plug with the required device drivers.

GSM modems supported by FM200 series on-board computers

Minimum modem specifications

For your modem to be used with the current release of FM200, FM200Plus firmware and office software it needs to be
configurable to the following minimum specifications.

632
www.mixtelematics.com

632
 633

RS232 (DTE-DCE) communications

· RS232 voltage levels

· 19200 baud (FM200/Plus configures this)

· 8 data bits (Pre-Configured)

· 1 stop bit (Pre-Configured)

· RTS-CTS flow control (FM200 configures this)

· Controlled lines (RX, TX, RTS, CTS, GND)

· DTR and DSR are looped back in the FM communications harness

Over the air data transfer

· Non-Transparent data transfer (From the PC side software only)

· Fixed baud rate (V.32) (From the PC side software only)

Power requirements

The installer should make sure that the installation meets the power requirements of the modem device installed.

AT commend set

The modem should support the standard Hayes AT command format and conform to the GSM extensions thereof. SMS
messaging should also be supported in both text and PDU modes.

Note: The Siemens M1 terminal does not support SMS messaging in text mode and is thus not suitable for use with the FM200
for SMS functionality.

FM200 Plus (FM200 Plus) Compatible Modems

The following is a list of modems compatible with the FM200 Plus series of on-board computers as well as the communications
methods they support:

Siemens

· M20 Terminal: (SMS and CSD)

· TC35 Terminal: (SMS and CSD)

· MC35 Terminal: (SMS, CSD and GPRS)

· MC35i Terminal: (SMS, CSD and GPRS)

Wavecom

· WM0D2 Terminal: (SMS and CSD)

· C2D Terminal: (SMS, CSD and GPRS)

· Fastrack M1206: (SMS, CSD and GPRS)

Nokia

633
www.mixtelematics.com

633
 634

· 6090: (SMS and CSD)

· 810: (SMS and CSD)

Falcom

· A2D-1: (SMS and CSD)

Note: This list only contains the modems that were tested to work with the FM200 Plus unit. The FM units use only a basic AT
command set and should be compatible with a wide range of available modems.

Installing a modem with the Fleet Manager on-board computer

Make sure the modem you are installing has the latest firmware installed. If the modem comes with an ignition input, it is highly
recommended that this be connected to the ignition circuit for improved reliability.

GSM Modem Installation Accessories

FM unit serial cable

· FM TTL converter:
The original TTL converter (FM: X39-723-002-055) can be used to connect a modem to the FM unit, but it is not recommended
as it only provides 1 serial port.

· FM Splitter cable:
The FM Splitter cable (FM: X39-723-002-075) can also be used to connect a modem to the FM unit.

· FM200Plus serial cable:

This cable can be used with the FM200Plus unit and is much more useful than the splitter cable. This cable provides
connection for the FM Terminal as well as two other serial ports.

GSM modem

Any of the FM unit supported modems.

Modem antenna

The selection of the antenna depends on the modem type and mounting requirements. The GSM antenna is to be mounted
further than 20cm away from the human body under normal operating conditions.

SIM card

The SIM card should be obtained from your preferred network operator and be enabled to receive incoming data calls, and to
send and receive SMS messages if SMS functionality is required.

GSM diagnostic plug

The GSM diagnostic plug is an essential tool for the installation of GSM modems. A diagnostic plug can be formatted using the
FM Dealer Utility. See the FM Dealer Utility documentation for more information.

Fleet Manager software

The Fleet Manager software is needed to configure the FM unit to communicate with the modem.

Modem connector cable

Some modems such as the WAVECOM WMOD2 modem need a converter cable to convert from the DB15 connector on the
modem to the DB9 connector on the FM Splitter. This can be obtained from your modem supplier.

634
www.mixtelematics.com

634
 635

RS232 extender cable

If the modem cannot be mounted close enough to the FM unit for the converter harness to reach it, then a RS232 extender cable
(straight through) can be used between the modem and the FM unit. This is not recommended though.

Relay for modem power control

The external-drive lines from the FM unit can be wired to control the power to the modem. This saves the vehicle’s battery and
allows the modem to be “hard reset” by the FM unit in case of a modem lock-up.

Note: Before you start with the installation make sure you have all the required components specific to your installation.

Modem Connections
Most modems require three (types of) connections:

· Antenna

· Power

· Serial cable

Antenna

The antenna is the simplest to connect as it has got no active connection to the FM unit. Refer to your modem documentation to
find the details of the antenna that must be used. Note: not all modem manufacturers supply an antenna as part of the modem.

Power

It may be important to control the modem's power consumption to prevent it from draining the vehicle's battery. The Fleet
Manager Client software provides functionality to configure the on-board computer to control power supplied to the modem. You
can configure the on-board computer to switch the modem off x hours after the vehicle is parked or if the vehicle battery voltage
drops below a certain level.

The physical outputs available for controlling the power to the modem vary depending on the type of FM unit being used. There
are two types of power control outputs provided by FM units; “External Relay Drive” and "Positive Drive". The External Relay
Drive outputs can be used to drive an external relay with a maximum current loading of 250mA. The Positive Drive supplies
battery voltage and can be used to supply power to external devices with a maximum current loading of 1 Amp.

The table below indicates which physical outputs can be used to supply power to the external or internal GSM modem of each
unit type.

Unit Type External Relay Drive 1 External Relay Drive 2 Positive Drive

FM200 Yes No - FM200 only has 1 External No - FM200 does not have
Relay Drive a Positive Drive

FM200 Plus Yes Yes Yes

FM200 Communicator No -internal modem is connected No - internal modem is connected Yes

to Positive Drive to Positive Drive

Note: Use a fuse in the supply of power to the modem. Refer to the modem specification for details of the fuse size.

Positive Drive power connection:

The Positive Drive power and ground lines are only available when the FM200Plus Serial Cable is connected. The brown wire is

635
www.mixtelematics.com

635
 636

ground (permanent) while the red wire is the switched battery voltage line.

External Relay Drive power connection:

The External Relay Drive lines require an external relay for controlling the power supply to the modem. See the connection
diagram below for a typical connection.

Note: The relay-assigned pin numbers may differ depending on the relay type and manufacturer.

Serial cable

The type of cable supported depends on the type of FM unit used. The table below list the combinations of cables that may be
used. On the FM200 Plus Serial Cable, the longer of the two DB9 connector cables is S2 (if not labelled).

Unit Type FM TTL To RS232 Converter FM Splitter Cable FM 200 Plus Serial Cable

FM200 Yes Yes No

FM200 Plus (FM200 Plus) Yes Yes Yes

FM200 Communicator No No Yes

General installation procedure

1. From the FM Dealer Utility, Load the latest released Device Drivers into unit. For best results it is recommended you use a
Device Driver code-plug.

2. Use the Fleet Manager Client application to correctly specify the vehicle configuration. Using a green vehicle code-plug, load
the configuration into the unit. It is important that this configuration contains the correct PIN code needed to enable the SIM
card. You must also ensure that the configuration contains the correct home-base number (the number of the modem in the
office that receives SMS messages) as well as the correct SMSC (short message service centre) number if SMS functionality is
required. You must ensure that all GPRS settings are specified correctly if GPRS functionality is required.

3. Connect the modem to the FM unit (refer to accessories for connecting cables).

4. Use an RS232 extender cable if required (not recommended).

5. The FM unit will try to initialise the modem to operate at 19200 baud. The Firmware on the FM unit will be able to find the
modem baud rate in the range from 2400 baud up to and including 38400 baud. If the modem is configured to an baud rate

636
www.mixtelematics.com

636
 637

outside of this range the FM unit will not be able to re-configure the modem to 19200 baud (reconfigure it then manually). See
Changing the modem baud rate for more information.

6. Create a GSM/DECT diagnostic plug using the FM Dealer utility.

7. For an audible and visual feedback of the GSM functionality, insert a GSM diagnostic plug in the FM code-plug socket.

8. When the diagnostic plug is inserted you will hear a short double-beep, signalling that the FM unit is configured for GSM
functionality. Any other beeps signal an incorrect configuration of the unit.

9. The code-plug socket LED should flash approximately every 30 seconds indicating that the FM unit is able to communicate
with the modem. This may take longer than 30 seconds the first time the modem is being initialised (in the order of 120
seconds).

10.Once the modem is logged onto the GSM network, the FM unit will issue a single beep in sync with the LED flashes (GPRS-
capable modems will issue a double beep).

11.Also check the status LED on the modem itself (most modems have one). Refer to the modem’s documentation for more
information on the meaning of its state.

12.Only proceed with the installation and testing once the diagnostic plug indicates that the FM is communication with the modem
and the modem is registered on the network.

13.Dial the vehicle from another data modem to check that the modem answers the incoming data call. The FM unit will not
automatically answer voice calls (the FM Keypad is required for managing voice calls).

14.Send a position request to the vehicle to test SMS messaging to and from the vehicle. The on-board computer will reply to a
position request, even if no GPS is physically connected to the unit.

For more on the GSM diagnostic beep codes refer to Beep and Flash Codes.

Warning: SIEMENS TC35 / MC35 Terminal (only applies when used with an FM200)

"Power Down" mode: The TC35 and MC35 modem has a sleep mode function. When the modem goes into power down mode, it
can only be awakened by either changing the state of the DTR (pin4) line on the modem, or by changing the ignition input line
state from low to high for longer than 200ms. The FM200 unit has no control over the DTR line, thus it is not able to change the
modem’s state. For this reason, it is recommended that you connect the modem’s ignition input to the vehicles ignition line.

The modem goes into this state when it is outside of GSM coverage for a long time or when the "modem off" AT command is
issued. For this reason, the power down command is not used in the FM200 firmware.

Warning: SIEMENS TC35/MC35 Terminal (applies when used with any FM unit)

It is not recommended to use the option to manage these modems' power consumption with serial commands. If you do, you
must ensure that the ignition input of the modems is properly connected. Once the Sleep AT command is sent to the modem,
only a change in the modem's ignition input from off to on will wake the modem.

Warning: SIEMENS M1 Terminal

The M1 modem does not support SMS messaging in text mode and is thus not suitable for SMS functionality.

Using HyperTerminal to test a modem

This section explains how to use a terminal program such as HyperTerminal to communicate with a serial device (modem). There
are a variety of terminal applications similar to HyperTerminal and you are not restricted to this one only.

What you will need

· RS232 Cable to connect the modem to your PC’s serial port.

637
www.mixtelematics.com

637
 638

· Power supply for the modem (refer to modem documentation)

· Serial port terminal application, e.g. HyperTerminal

Start HyperTerminal

HyperTerminal can be installed from the Microsoft Windows installation disk if not already installed on your PC. Refer to the MS
Windows documentation for more info on the application.

Step 1

Open HyperTerminal and the “Connection Description” dialog box.

Step 2

Enter a name for the HyperTerminal session (if you wish to save it for later use), e.g. “Siemens TC35 on COM1”. Click OK to
open the “Connect To” dialog.

Step 3

638
www.mixtelematics.com

638
 639

Using the “connect using” drop-down-list, select the serial port that the modem is connected to. A serial port can only be used by
one device at a time, so make sure that no other device is using the selected serial port. Click OK to open the serial port physical
settings.

Step 4

Select the baud rate (bits per second) that the modem is currently configured for (refer to the modem’s technical manual). Select
“None” for the Flow control option. Clicking OK would open HyperTerminal connected to the COM1 device.

639
www.mixtelematics.com

639
 640

Step 5

You can now save the settings to be loaded at a later stage. Ensure that Caps-Lock is on when you are communicating with the
modem. It is not necessary, but some modems needs the AT commands in capital letters to synchronize with the PC baud rate.

Step 6

To check if the modem is communicating type the following string: “AT” and press the Enter/Return (¿) key. The modem should

640
www.mixtelematics.com

640
 641

respond with the string: “OK”. If nothing appears while typing the command you can either turn on local echoing in HyperTerminal
or you can configure the modem to echo all characters that it received. The latter is preferred.

For all sections related to sending commands to the modem the following conventions will be followed.

Command ATE1 Turn echoing on

Response OK The modem accepted the command

The first column describes the direction of the string. Command is the string entered on HyperTerminal while Response it the
string/s returned from the modem as a response of the command sent to it. To send a command to the modem, type in the
command string followed by the Enter/Return (¿) key. Usually AT commands are entered as capital letters.

Note: If you see “xxxx” as part of a command, read the comments field to see whether you have to enter xxxx or need to replace
that part of the command with your own string.

If the modem is not responding to your commands:

· Check the spelling of your commands (zero and o can easily be confused!)

· Check the baud rate setting on HyperTerminal

Configure modem to echo all typed characters

If you want to see what you are typing you can use the following sequence of commands to turn on the echoing function of the
modem.

Command ATE1 Turn echoing on

Response OK The modem accepted the command

Changing the modem baud rate

The first step is to get the modem to respond to commands entered. To check the modem, use the normal AT query. Remember
to give the modem a chance to register to the network, as it might only respond once the network logon was completed
successfully. Also check the LED status on the modem itself (refer to modem user manual).

Test the modem response

Command AT Check that the modem is ready

Response OK Modem interpreted AT command correctly

Change the baud rate in HyperTerminal until you receive a valid response for the test modem command. At this point we have
established communication with the modem. The next step is to check the modem baud rate setting.

Checking the active baud rate setting

Command AT+IPR? Query the modem baud rate setting

Response +IPR: 0 The modem is configured in auto baud detection mode. In this modem you

641
www.mixtelematics.com

641
 642

can communicate to the modem at any baud rate as long as you use capital
letters as the AT commands.

+IPR: xxxx “xxxx” represents the baud rate of the modem as an integer string value.

Set the new baud rate

Command AT+IPR=19200 Setting the modem baud rate to 19200 baud. You can replace the “19200”
with “9600” if the modem needs to be configured to run at 9600 baud.

Response OK Setting accepted.

If the specified baud rate is different to your HyperTerminal setting, then the modem would no longer respond to the AT
command. Change the HyperTerminal baud rate to the value the modem was set to. Use the test command to verify that the
modem is responding. At this point you can now save the value as the default baud rate (will be used when the power is
disconnected and re-connected).

Save all the current settings as the power-on defaults

Command AT&W Save all settings

Response OK Command accepted

Setting up the modem

Before you can use the GSM, check the following:

Enable extended error reporting

Command AT+CMEE=1 Enable extended error reporting on AT commands

Response OK The modem accepted the command. Errors will now be reported in the form
“+CEER: Error XX” where XX is the extended error code.

Check if a PIN code is required

Command AT+CPIN? Check Pin code status

Response +CPIN: READY No PIN code is required

+CPIN: SIM PIN You need to enter the PIN for the SIM card

+CPIN: SIM PUK The SIM is locked and requires a PUK code. Use your mobile phone to enter
the PUK code (much safer).

Enter the PIN code if required

642
www.mixtelematics.com

642
 643

Command AT+CPIN=”xxxx” Enter SIM Pin code - the string xxxx must be replaced with your SIM's PIN
code. This command may take a few seconds before it responds, as it might
only respond after it registered to the network. Remember that you can only
enter the PIN code 3 times incorrectly after which the PUK code would be
required!!!

Response OK PIN accepted

Check the signal quality/level

Command AT+CSQ Check the signal strength.

Response +CSQ: 16,0 The first value (before the comma) is an indication of how good the reception
is. 99 means that the modem cannot determine the signal strength. The value
should be in the range from 0 to 31, where 31 means perfect and 1 is very
poor.

Check the network registration status of the SIM card

Command AT+CREG? Check the modem registration status.

Response +CREG: 0,1 The second value (after the first comma) is the status of network registration.
Valid values:

· 0: not registered, ME is currently not searching for new operator

· 1: registered, home network

· 2: not registered, but ME is currently searching for a new operator

· 3: registration denied

· 4: unknown

· 5: registered, roaming

When the PIN status is OK and the modem is registered then the modem is ready to accept GSM-related commands.

Reading and writing SMS messages

Before you can send SMS messages from the modem, the SMS service centre address needs to be specified. Ask your network
provider if you do not know what it is. The number normally should be entered in international format, i.e. starting with a “+”.

Enter SMS service centre address

Command AT+CSCA=”+27832000001” Set your network service centre address

Response OK Service centre address accepted

Check the service centre address

643
www.mixtelematics.com

643
 644

Command AT+CSCA? Query the active service centre address

Response +CSCA: "+27831000002",145 Service centre address is the value before the first comma.

Store the service centre address permanently

Command AT+CPAS Store SIM related settings

Response OK Settings were saved

We are only going to send and read SMS messages in text format, so we need to configure the modem to do so.

Select text modem SMS message format

Command AT+CMGF=1 Enable text mode SMS messaging

Response OK Command accepted

Check the message storage

Command AT+CPMS? Check the available and used message storage

Response +CPMS: “SM” means the message is stored on the SIM

“SM”,0,15,”SM”,0,15,”SM”,0,15
“MT” means the message is stored on the modem

At this point the modem is configured to read and write SMS messages in text mode.

List all messaged stored on the modem

Command AT+CMGL=”ALL” List all stored SMS messages

Response +CMGL: 1,”REC UNREAD”,”081234569”, This is Settings were saved

the message text+CMGL: 2,”REC
UNREAD”,”081234569”, This is the message
text… Etc.

Read a specific message

Command AT+CMGR=x Read a message stored on the specified storage

location “x”.

Response +CMGR: "REC Display the selected message's detail

READ","+27836414132", ,"03/12/17,11:42:37
+08"

Delete a message

644
www.mixtelematics.com

644
 645

Command AT+CMGD=x Deletes the message stored on the specified storage location “x”.

Response OK Message was deleted

Sending an SMS message is a bit more involved and takes 3 steps to execute. First the command is entered, then you need to
wait for the prompt to enter the message body, and finally use the send key-stroke to transmit the message. To terminate the
message body without sending it, use the Escape key (Esc).

Sending an SMS message

Command AT+CMGS=”PhoneNumber” Start to send an SMS message

Response > Prompt to receive the message body

Command type your message mode text now Enter the message body now

Command Ctrl-z Type the Ctrl-Z key stroke to send the message. (Hold down the
control (Ctrl) key and press z)

Response +CMGS: y The message was sent

Example:
AT+CMGS="0825626159"
> Hello®
+CMGS: 77
Note: DO NOT press the Enter key after entering the message text. Use only Ctrl-z to indicate the end of the message text.

Call management
This section covers placing voice and data calls as well as answering incoming calls

Enable extended call information

Command AT+CRC=1 Enable extended call information

Response OK Command accepted

Enable caller line identity

Command AT+CLIP=1 Switch on caller line identity (CLI), not supported on all modems.
For the modem to report the CLI the other party must have “send
own number” enabled and the SIM in the modem has to be
enabled to receive CLI. Ask your service provider for more info.

Response OK Command accepted

When an incoming call is received the modem sends unsolicited strings to HyperTerminal.

+CRING: ASYNC (Signals the type of incoming call, data call in this case)

645
www.mixtelematics.com

645
 646

+CLIP: “0839876543”,xx (signals the calling party’s number)

Placing a voice call

Command ATDxxxxxxxx; Dials a GSM phone number. The semi-colon “;” at the back signals
a voice call.

Response OK The called party answers the call

Placing a data call

Command ATDxxxxxxxx Dials a GSM phone number

Response OK The called party answered the call

CONNECT The modem connection was successful

NO CARRIER The call was terminated/not available

BUSY The called party is on another call

When a modem is in a data call it does not accept any AT commands. To make it accept AT commands there is a special
character sequence that needs to be sent to the modem:
<do not type anything for 1 second>
+++
<do not type anything for 1 second>
The modem will now respond with an OK to signal that it is in command mode.

Terminating a call (hang-up)

Command ATH Terminate any calls

Response OK Command accepted

Testing GPRS
This section of the document will explain how to determine whether or not your modem is GPRS capable. The simplest test is to
query the GPRS PDP context activation status. For an explanation of how to do a more comprehensive GPRS test, please see
Testing GPRS SIM Cards.

Get the GPRS PDP context activation status

Command AT+CGACT? GPRS PDP context activation status

Response ERROR Command not known, this modem cannot be used for GPRS with
the FM unit

+CGACT: 1,0 The modem understood the command, and has got an inactive PDP

646
www.mixtelematics.com

646
 647

context.

Define a PDP context

Command AT+CGDCONT=1,"IP","internet" Define a PDP context, where “internet” is the APN string

Response OK Context defined

Create a new GPRS session

Command ATD*99***1# Create a new GPRS session using context #1

Response CONNECT Connected to the GPRS network

~ }#À!}!}!} }6}!}$}%Ü}"}&} } } } }'}"} PPP configuration strings

(}"}#}$À#&´~

Overview of GSM Software

SMS Processor

The Fleet Manager SMS Processor is used to send and receive GSM short message service (SMS) messages to and from
FM200 series on-board computers equipped with GSM modems. Messages are sent and managed using the Fleet Manager
Active Tracking and Messaging Extension.

GSM Downloader

The Fleet Manager GSM Downloader utilises a telephony device such as a modem to transfer information to and from FM200
series on-board computers equipped with GSM modems using GSM circuit-switched data (CSD) calls. Data transfer schedules
are defined and managed using the Fleet Manager Comms Scheduler Extension. Information downloaded from the on-board
computers is written into files which are transferred into the Fleet Manager database by the Fleet Manager AutoPoll Client.

Wireless Internet Service (GPRS & WLAN)

The Fleet Manager Wireless Internet Service (GPRS & WLAN) is used to send and receive messages and transfer data to and
from FM200 Plus series on-board computers equipped with GSM modems using the general packet radio service (GPRS).
Messages are sent and managed using the Fleet Manager Active Tracking and Messaging Extension. Data transfer schedules
are defined and managed using the Fleet Manager Comms Scheduler Extension. Information downloaded from the on-board
computers is written into files which are transferred into the Fleet Manager database by the Fleet Manager AutoPoll Client.

Configuring a GSM modem with Fleet Manager Professional 9

The Fleet Manager Client application allows you to specify how the FM200 unit interacts with the GSM module.

Step 1

The Device tab of the Vehicle Properties dialogue is used to specify that a GSM module is connected to a serial port of the FM
unit.

Double clicking on the relevant serial port entry in the list box displays the Device Connection dialogue.

647
www.mixtelematics.com

647
 648

Step 2

Select GSM Modem in the devices tab. Click on the Modem tab.

Step 3

Enter the PIN code and Modem initialization string.

Important: You must remove the SIM card from the GSM module and make use of a mobile phone to update the PIN code for
the SIM card if necessary. For security reasons, changing the PIN code in the Vehicle Properties dialogue does not update the
PIN code in the device. If the PIN code entered into the Vehicle Properties dialogue does not match the PIN code in the GSM
module, the GSM module will not be able to log onto the GSM network.

If you have an FM Keypad and wish to use it to make voice calls, enable voice communications and select the voice channel to
be used with your hands free kit.

648
www.mixtelematics.com

648
 649

Step 4

Click on the CSD Tab.

Set the data number of the GSM modem that is connected to the FM unit. All telephone numbers must be entered in canonical
format by specifying a country, city or area code and local number. This is so that the GSM Downloader can translate them into
valid dialling strings using the Windows dialling rules. This is described in more detail below.

Step 5

Click on the SMS tab

649
www.mixtelematics.com

649
 650

This tab is used to configure the SMS settings for this unit. To enable SMS communications, enable the relevant check box on
this tab and complete the settings on this tab. The SMS limit from the unit to the office determines how many SMSes the unit will
be allowed to send per day. The SMS limit from the office to the unit determines how many SMS messages will be allowed to be
sent to the unit from the office.

Step 6

Click on the GPRS tab.

This tab is used to configure the GPRS settings for this unit. To enable GPRS communications, enable the relevant check box on
this tab and complete the settings on this tab.

The APN, User name and Password must be obtained from your network service provider.

The Server IP Address and Server IP Port must be set to those of the computer hosting the Fleet Manager Wireless Internet
Service (GPRS & WLAN).

Also see GPRS Questions and Answers for more information on these settings.

650
www.mixtelematics.com

650
 651

Step 7

Click the Advanced button.

If your cellular network charges for every GPRS Connection made, you may limit the number of connections per day. Otherwise,
you should leave this unchecked.

Specify the frequency that Automatic Vehicle Location (AVL) packets should be sent by the unit. AVL packets serve two
purposes. Firstly, they keep the GPRS connection alive and prevent the unit's IP address from changing. On most GPRS
networks, dormant connections will be terminated after 5 to 10 minutes. Secondly, they include GPS position information useful
for Active Tracking.

Note: setting the AVL period for out-of-trip to less than 30 seconds will cause power management to be bypassed. The GSM unit
will remain switched on permanently.

651
www.mixtelematics.com

651
 652

Step 8

Click on the Packet Comms tab.

The Packet Comms tab is used to specify whether packet-based communications (such as GPRS) should be used for active
events and messaging.

You may also configure the unit to send end-of-trip (EOT) download of active events. This will cause the office software to
automatically perform a quick download at the end of each trip.

Step 9

652
www.mixtelematics.com

652
 653

Click on the Database tab.

The database tab is used to filter the storage of AVL packets in the database. As described above, AVL packets serve two
purposes. If you require AVL packets to be sent to keep the GPRS connection alive, you may not wish to store all AVL packets in
the database. In the same way, if your FM unit does not have a GPS receiver connected, you may not wish to store AVL packets
in the database.

Step 10

Click on the Transports tab.

This tab is used to configure the default transports for data transfer, commands and messages for this vehicle. These default
transport values can be over-ridden when defining a schedule with the Comms Scheduler Extension and when sending command
messages, free-text messages or jobs using the Active Tracking and Messaging Extension.

Select the appropriate default transport values and click the Power tab.

653
www.mixtelematics.com

653
 654

Step 11

Select the appropriate power management options for the modem. See Installing a modem with the Fleet Manager on-board
computer for more information.

654
www.mixtelematics.com

654
 655

5.8 Fleet Manager SMTP Mail Service

© 2008 MiX Telematics | Updated 2008/06/12

Introduction
The Fleet Manager SMTP Mail Service sends e-mail messages generated by the SMS Processor and Wireless Internet Service
(GPRS & WLAN) using an external SMTP mail server. Refer to the Handset and E-Mail Notifications documentation for more
information.

How Does It Work?

The Fleet Manager SMTP Mail Service is a Windows NT Service that polls one or more message folders periodically, reads the e-
mail message files, makes an SMTP connection to an SMTP mail server, sends the mail messages and then deletes the
message files.

FM Service Manager

The Fleet Manager SMTP Mail Service is not an executable program, and can therefore not be run from the Windows “Start”
menu. It is a Service, and should be run (Started) from the FM Service Manager, which can be found under Control Panel.

How Do I Use It?

Launch the FM Service Manager from the Control Panel, by double clicking on it. A system tray icon will be displayed.

Right click on this and select “Open”.

You will see the Fleet Manager SMTP Mail Service listed provided you elected to install it when you installed the Fleet Manager
Communications Suite. From here you can Start, Stop and Re-Start the service using the relevant icons or menu items. You can
also set options by double clicking on the Fleet Manager SMTP Mail Service.

655
www.mixtelematics.com

655
 656

Before changing any settings, it is recommended to Stop the service, and Start it again after the changes have been applied.

· SMTP Host is the name or IP address of the SMTP server to be used to send e-mail messages.

· Message Format specifies the format to be used when generating e-mail messages.

· Processing Frequency specifies how often (in seconds) the SMTP Mail Service should check the message folder for new
messages to send.

656
www.mixtelematics.com

656
 657

· Message Folders defines the path/s where message files are located.

Note: The SMS Processor and Wireless Internet Service (GPRS & WLAN) generate e-mail messages into the folder specified
when they were installed (by default C:\Messages). The messages folder can also be specified using the Fleet Manager
Administrator Utility. If any of these applications are located on a different computer to where the Fleet Manager SMTP Mail
Service is running, it will be necessary to share the messages folders on the other computers and then add the shared folders to
the Fleet Manager SMTP Mail Service's Message Folders list. You must also ensure that the Fleet Manager SMTP Mail Service is
configured to use a user account with full control over the shared folders on the other computers.

657
www.mixtelematics.com

657
 658

5.9 FM Sat Comms

© 2008 MiX Telematics | Updated 2008/06/11

The MiX Telematics Satellite Communication Solution has been developed for use in areas where no currently supported
communication infrastructure (GSM, WiFi or DECT) is available. The solution uses the Satamatics transceiver in combination with
the FM OBC. Satamatics uses the Inmarsat D+ system which consists of 4 geostationary satellites offering global coverage.

The solution consists of the following components:

· The Satamatics SAT201 transceiver

· FM300 OBC

· FM software

· Airtime

658
www.mixtelematics.com

658
 659

Satamatics and Inmarsat Systems

The Satamatics system is a satellite data communication system based on Inmarsat D+ and uses the Satamatics SAT201
satellite modem. The SAT201 consists of an Inmarsat D+ transceiver, used for transmission of data via the Inmarsat system, and
an onboard GPS receiver used for positioning.

Satamatics SAT201 satellite modem

The Inmarsat system consists of 4 Geo-stationary satellites giving global coverage, excluding the Polar regions. The coverage is
split up into ocean regions - Pacific Ocean, Atlantic Ocean East and West, and Indian Ocean.

Inmarsat coverage

SAT201 and Inmarsat D+ Operation

659
www.mixtelematics.com

659
 660

The SAT201 unit determines its position at initial power up using its onboard GPS, and then tries to listen to the satellite with the
best elevation from it.

There are 3 channels that the modem uses for communications - bulletin board channel, traffic channel and return channel.
Message capabilities allow for data to be sent in bursts of 84 bits from the satellite modem and 1000 bits to the modem.

The Inmarsat satellite continuously transmits a bulletin board with a frame length of 4 minutes. The bulletin board contains info on
Date and UTC time of day, Traffic Channel Assignment, Service ID, Satellite Beam ID, Pager Subset Number (PSN) and Ocean
Region. Once the unit has received this info, it can then tune to the traffic channel.

The traffic channel is used by the Inmarsat D+ system to send messages to modems and the return channel is used by the
modems to send messages.

The traffic channel is a burst transmission with a frame length of up to 2 minutes. It is a burst transmission in the sense that if the
frame is not completely used, transmission is stopped until the start of the next frame. If the load is extremely heavy, transmission
can be continuous.

The frame header at the beginning of the traffic channel burst holds information on Return channel assignments.

Following the frame header is the frame ID and then a message preview block.

The message preview block contains the partial address of units that have messages for them. If the unit determines there is a
message for it from the preview block it will continue to decode the rest of the traffic channel to receive its message.

If the unit does not have a receive message pending or it has finished decoding its message and has a message to transmit, it
will then tune to the return channel that was broadcast in the traffic channel header and randomly select a transmission slot
inside the return channel frame to transmit its message.

The frame length for the return channel is also 2 minutes.

The data payload on the Inmarsat D+ system is 84 bits (10.5 bytes) from unit and 1000 bits (125 bytes) to unit.

The unit will remain on the traffic channel frequency as long as it detects traffic channel frames.

If it misses 2 traffic channel frames and then misses 2 bulletin board frames it assumes it has lost the satellite transmission. It will
then check its GPS position and tune to the second preferred satellite and listen for the bulletin board.

Definitions
AVL

An AVL is a packet containing GPS info that is used to keep the GPRS session alive. The AVLs received are not recorded in the
database unless it is setup for the GSM device. The AVLs can still be plotted on a map but there is no historical data unless they
are stored in the database.

660
www.mixtelematics.com

660
 661

Tracking Points

Tracking points are GPS positions that can be seen as messages in the Active messages window. These messages are
automatically stored in the database. They are primarily used for active tracking, but are used for Satamatics because the
Satamatics device does not send AVLs.

Passive Trail

Passive trail records vehicle positions in trip for the settings below. The tab has a full description of its operation. This is used with
tacho data in the activity timeline.

661
www.mixtelematics.com

661
 662

Active Trail

Active trail is only applicable to units with GPRS. It buffers positions with the settings below and sends the buffer when
scheduled. The tab carries a detailed description of the operation.

662
www.mixtelematics.com

662
 663
5.9.1 FM Sat Comms Installation Guide

© 2008 MiX Telematics | Updated 2008/05/07

Step 1: Satamatics Unit Installation

Please refer to the Satamatics Installation Guide supplied with the unit.

Step 2: Connect the Satellite Unit to the FM Unit

Use the Db9 Female connector as follows:

663
www.mixtelematics.com

663
 664

Step 3: Add the Unit as a Device

The unit is set up by installing it as a device on S3 for a vehicle.

Double-click the vehicle to be configured in the Main Window of FM Pro to open the Vehicle Properties window. Click on the
“Devices” tab to add the unit.

Step 4: Set up the Satellite Service

· Ensure that the Fleet Manager Communications Suite is installed with the Fleet Manager Wireless Internet option selected.

664
www.mixtelematics.com

664
 665

· Run setup.exe in the Satamatics folder to install the service.

· During the installation process a user account and password are required to install the service as a user account service on
your local PC. This requires that you have administrative rights on the PC. Provide a user account and password with the
domain path (eg. CIDEV\CuanV).

· To provide access between the PC and the service, an exception needs to be added to the PC firewall. This is particularly
relevant to FM Pro running as a stand-alone application. Go to Control Panel and open Windows Firewall. Add an exception for
TCP port 5101 and name it Satamatics 5101.

Note: If the firewall service is not running on your PC then ignore this and continue to the next step.

665
www.mixtelematics.com

665
 666

· Add an exception for TCP port 8101 and name it Satamatics 8101.

· Go to Control Panel and click on FM Service Manager.

666
www.mixtelematics.com

666
 667

· The Fleet Manager Services Manager will be displayed.

· Click on the second icon from the right next to the refresh icon.

· This will display the Fleet Manager Satamatics Service setup.

667
www.mixtelematics.com

667
 668

· The username and password required here is the one that will be used by the service to log onto the database – the same as
your FM Pro login and password.

· Ignore the proxy settings – they are only needed if the service is installed as a local system account.

· Click Update to save the settings.

· A warning window will appear telling you that the service needs restarting.

· Click on OK.

· Click on the Start service Icon to start the service.

· The service will attempt to start.

668
www.mixtelematics.com

668
 669

· There are 2 additional Tabs – Error Log and Message Log.

· Error Log tab views the ErrorLog.txt file found in the application directory for viewing any errors that may have occurred.

· Message Log tab views the message transactions between the service and the gateway. Note: when this window is closed the
messages that were in the window are lost.

669
www.mixtelematics.com

669
 670

· If all is working you should see xml transaction text every 60 seconds. This poll time is configurable in the config file.

Set up the modem

Editing the device properties and selecting the Modem tab will allow for the setup of the Satamatics modem properties.

670
www.mixtelematics.com

670
 671

· The “Daily Message Limit” box sets the number of messages the vehicle can send per day. This is reset at midnight. If this
count is exceeded, the vehicle unit will not transmit any more messages until the midnight reset.

· The “Enable failover support for other transport” checkbox allows commands to be sent to the vehicle if the default transport
type (e.g. GPRS) fails to send the command within the time specified in the Queue time threshold box.

· The “Device ID” is the modem’s unique address. It is found printed on a label underneath the modem. It is usually a 5
character alpha-numeric address. It is very important that this address is correctly inserted, as communication with the modem
is initiated with this address code.

· The in trip and out of trip positions checks set up the in trip and out of trip position frequency. Note that the minimum frequency
is 2 minutes.

· The passive trail tab and power tab setup are the same for other devices.

Step 4: Set up Messages and Events

Critical Active Events

The Active events setup tab has a critical event radio button. Events that are selected as critical will be sent using Satamatics if
there is no coverage in another transport (cheaper) type.

671
www.mixtelematics.com

671
 672

If the “Send current position in message” check box has been selected, once a positive acknowledgement of the critical event has
been received, a second message with GPS information will be sent if Satamatics has been used to send the critical event.

An example of a custom Critical Active Event is depicted below:

Analog Voltage was used to activate the Critical Active Event.

672
www.mixtelematics.com

672
 673

Critical Event Priority has been added to the “Active” tab.

673
www.mixtelematics.com

673
 674

The rest of the settings on the tabs will behave as before, the only addition being the Critical Message Priority. Critical Active
Events are sent as soon as possible. Critical Events will test for WiFi or GPRS communications to relay the Event. If the
communication methods are not available the unit will queue the message to be sent via Sat Comms. Messages of “Normal” and
“Urgent” priority will NOT be sent over Sat Comms, but will be queued to be sent when other transport methods (GPRS or WiFi)
regain active status.

Increasing the Daily Message Limit for the Satellite device

Use the Active Tracking Extension and add the desired Sat Comms enabled vehicle. Right click on the vehicle and select
“Increase Daily Satamatics Message Limit”. The following screen will appear:

The “Send update command via” option box will contain the available transport types on the selected vehicle. The Non Sat
Comms devices will always be the default device to use. You are able to increase the message limit for any of the listed
transports from this screen.

Step 5: Tracking via the Satellite Device

674
www.mixtelematics.com

674
 675

Use the Active Tracking Extension and add the desired Sat Comms enabled vehicle.

The first of the two time boxes represents the frequency that a message will be requested from the vehicle. The second time box
specifies the duration that the frequency should be executed for. The minimum for both of these time boxes is 5 minutes. This is
directly related to the pickup window that the satellite provides. The “Send tracking request via” option box will contain the
available transport types on the selected vehicle. The Non Sat Comms devices will always be the default device to use.

Step 6: Testing the Satellite Communications

The following tests should aid as guidelines:

Communication Critical Active Event

Methods

No Comms When all Communications are down (excluding Unit Sleeping) and a Critical Active Event is
triggered, Positive Drive is woken up and message is sent via Sat Comms

GPRS Comms When GPRS Comms (FM Comms) is available and a Critical Active Event is triggered, the GPRS
communication should be used and NOT Sat Comms

GPRS Comms (No When GPRS Comms is not available or there is no coverage, and a Critical Active Event is
Coverage) + Sat Comms triggered, then the Event should be sent over Sat Comms

Satamatics Diagnostics
Using a Satamatics diagnostics plug:

· Sat modem enabled = 4x beeps

· Sat modem disabled = 2x long beeps

· Start diagnostics = 1x beep

· Transmit an Event = 2x beeps

· Receive an ACK = 3x beeps

· Add to command queue = 1x long beep

· Transmit current position = 3x long beeps

· Increase daily limit = 5x long beeps

· Receiving RMC strings = 1x LED flash (code plug LED)

675
www.mixtelematics.com

675
 676

LED indicators on the Satamatics modem

676
www.mixtelematics.com

676
 677
5.9.2 FM Sat Comms User Guide

© 2008 MiX Telematics | Updated 2008/05/07

FM Professional
FM Sat Comms provides an additional communication method to GSM/GPRS. Access to the functionality can be found under
“Active Tracking and Messaging” in FM Professional.

The functions applicable to FM Sat Comms are:

· Request Current Position

· Initiate Tracking

· Stop Tracking

· Increase Daily Satamatics Message Limit

All GPS positions received from the vehicle via Satamatics are tracking points and can be viewed in the Active Messages
window. Active events are always displayed in the Active Messages window.

677
www.mixtelematics.com

677
 678

FM Web
In FM Web, the FM Sat Comms functionality is found under "Mapping", "Live Tracking".

678
www.mixtelematics.com

678
 679

Right-click a selected vehicle and choose to start or stop tracking with Satamatics using the context menu. Included in the right-
click menu is the option to increase the daily SAT limit.

679
www.mixtelematics.com

679
 680

680
www.mixtelematics.com

680
 681

5.10 IP Router
© 2008 MiX Telematics | Updated 2008/06/12

Background
The IP Router provides a communication gateway between OBCs and a GPRS service in the following scenarios:

· WLAN-equipped OBC that is behind a network firewall and needs to connect to the GPRS Service on the FM Bureau.

· WLAN-equipped OBC that is behind a network firewall and needs to connect to its own GPRS Service hosted on a public IP.

681
www.mixtelematics.com

681
 682

· WLAN-equipped OBC that is behind a network firewall and needs to connect to its own GPRS Service using the FM GPRS
Gateway.

Installation
The IP Router install-set is part of the FM Fleet Manager Communications Suite. Run the install-set and choose to install IP
Router. The default folder where the IP Router is installed may be changed if required. No other configuration is required during

682
www.mixtelematics.com

682
 683

installation.

Configuration
Configuration is done using the FM Service Manager in the Windows Control Panel. Once configured, the IP Router Service must
be restarted for changes to take effect. This may be done using the FM Service Manager.

Select IP Router Service and double click it to get to the configuration dialog.

OBC Communication

The IP Router Configuration Dialog is shown below. The incoming port and debug settings can be configured using the ‘Settings’
tab. The incoming port number is the port that the IP Router will use to receive data from the OBCs. This corresponds to the unit’s
Server IP Address as configured with the Fleet Manager Office software.

GPRS Service and FM Gateway Configuration

683
www.mixtelematics.com

683
 684

The connection details of the GPRS Service/s that the IP Router must connect to are configured in the ‘Server Options’ tab.

Click on the ‘Add Server’ button to add a GPRS Service connection. Complete the form by supplying the IP Address and port of
the GPRS Service.

The FM GPRS Gateway IP Address and port must be used if the GPRS Service can only be reached via the FM GPRS Gateway.
In this case the ‘via FM Gateway’ check box must be checked and the company ID (in hexadecimal) must also be provided.

684
www.mixtelematics.com

684
 685

Communication Settings

The proxy type and details of the connection to the GPRS Service are configured on the ‘Server Options’ tab under Proxy. The
first two types of communication (UDP and TCP) do not make use of a proxy. Select one of these types if a proxy is not needed.

Otherwise, select the appropriate proxy type and its IP Address as well as username and password.

685
www.mixtelematics.com

685
 686

5.11 Handset & E-Mail Notifications In The Fleet Manager System

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The SMS Processor and Wireless Internet Service (GPRS & WLAN) are capable of sending SMS notification messages to GSM
handsets and/or e-mail messages to e-mail addresses when active event messages are received from vehicles. SMS notification
messages are sent by the SMS Processor and e-mail messages are sent by the SMTP Mail Service.

Enabling this facility has not been made available through the program interface but is done by creating a special rule file named
notify.csv.

The SMS Processor requires this notify.csv file to be located in the same directory as the SMS Processor executable (typically C:
\Program Files\Fleet Manager Communications Suite\SMS Processor"). The Wireless Internet Service (GPRS & WLAN) can be
configured to use a notify.csv file located in any folder, making it possible for all three components to share a common
notifications rule file.

Rule File Format

The rule file is a comma-separated value (CSV) file with one header line and one line for each rule. A CSV file is a plain text file
with each record having a number of fields, separated by commas, and can therefore be created in any text editor. Microsoft
Excel is also able to open and save comma-separated value files, so you could use Excel if you prefer. However you should still
open the file you create in a text editor and verify that its format matches the one described below.

The header line has one of two fixed formats, one used for single organizations and another for use in bureau type installations
where the SMS Processor is handling messages for multiple organizations. If you have a single organization then the header line
must match the following line.
Events,Vehicles,Drivers,Telephone Numbers,Email Addresses,Message Template
If however you have an FM-Web installation with multiple organisations, the header line must match the line below.
Organisations,Events,Vehicles,Drivers,Telephone Numbers,Email Addresses,Message Template
We suggest that you copy one of these lines from this document and paste it into your text editor to ensure accuracy.

Each of the event lines must contain six or seven fields, depending on the format of the header line, namely Organisations,
Events, Vehicles, Drivers, Telephone Numbers, Email Addresses and Message Template.

Organisations

The Organisations field contains a list of organisation identifiers to which the rule is to apply. The identifiers in the list must be
separated by semi-colon (;) characters. If a single asterisk (*) character is provided instead of a list of identifiers, the rule will
apply to any organisation. The identifier for the organisations in FM-Web can be determined by the FM-Web administrator. To
retrieve this information the following query should be executed against the FM-Web database using the SQL Server query
analyzer.
select sOrganisationName as Organisation,
liOrgID as ID,
case bActive when 1 then 'YES' else 'NO' end as Active
from Organisation
where liOrgID <> -1
Please note that events with the same name may have different identifiers in different organisation's databases. If this is the case
you will not be able to enter multiple organisation identifiers on each line of the notification file.

Events

The Events field contains a list of event identifiers to which the rule is to apply. The identifiers in the list must be separated by
semi-colon (;) characters. If a single asterisk (*) character is provided instead of a list of identifiers, the rule will apply to any
event. The identifier for an event can be determined by examining the event details in the FM Client.

686
www.mixtelematics.com

686
 687

Vehicles

The Vehicles field contains a list of vehicle identifiers to which the rule is to apply. The identifiers in the list must be separated by
semi-colon (;) characters. If a single asterisk (*) character is provided instead of a list of identifiers, the rule will apply to any
vehicle.

Drivers

The Drivers field contains a list of driver identifiers to which the rule is to apply. The identifiers in the list must be separated by
semi-colon (;) characters. If a single asterisk (*) character is provided instead of a list of identifiers, the rule will apply to any
driver.

Telephone Numbers

The Telephone Numbers field contains a list of the GSM telephone numbers to which notifications of the event must be sent. The
numbers must be entered in full, with a leading + symbol and country code. Other than the leading + symbol, only numeric digits
are permitted. The numbers in the list must be separated by semi-colon (;) characters.

Email Addresses

The Email Addresses field contains a list of e-mail addresses to which notifications of the event must be sent. The e-mail
addresses must be separated by semi-colon (;) characters.

Message Template

The Message Template is the text you wish to be sent to the handset and may contain any of the replacement tokens listed
below. These tokens are replaced with the appropriate values before the message is sent to the handset.

· #vehicle_id – use this to include the vehicle’s identification number.

· #vehicle_desc – use to include the vehicle’s description, including the registration number.

· #timestamp – use this to include the date and time at which the event occurred.

· #driver_id – use this to include the driver’s identification number. If no driver has been identified the vehicle’s default driver will
be assumed to be driving.

· #driver_name – use this to include the driver’s name.

· #event_id – use this to include the event’s identification number.

· #event_desc – use this to include a description of the event.

· #event_value – use this to include the event’s recorded value. As this is the raw, un-calibrated value directly from the vehicle it
may only be useful to include this for certain specific events.

· #longitude – use this to include the longitudinal element of the vehicle’s position when the event occurred.

· #latitude – use this to include the latitudinal element of the vehicle’s position when the event occurred.

Comments
You are able to insert comments into the notification file by beginning a line with the semi-colon (;) character. The rules processor
will ignore any line that begins with this character.

Rule Processing

When the SMS Processor or Wireless Internet Service (GPRS & WLAN) is started the rule file is read and the rules are loaded
into a table. When an incoming active event message is received, the rule table is scanned for rules with a matching event

687
www.mixtelematics.com

687
 688

identifier, vehicle identifier and driver identifier. All three of these must match (list must be * or contain the identifier) for a rule to
be matched.

If any rules were matched, a notification message using the message template from the rule is sent to each telephone number in
the Telephone Numbers field and each e-mail address in the Email Addresses field of each matched rule. Care must be taken
not to create a situation where multiple rules match, including the same telephone number or e-mail address, as this will cause
multiple messages to be sent.

Example

As an example we will assume that we have the following rule file.

; this is a sample notification file
Events,Vehicles,Drivers,Telephone Numbers,Email Addresses,Message Template
; the following rule will send messages to two telephone numbers and
; an e-mail address when active event messages indicating
; overspeeding is received
1,*,*,+27831234567;+27829876543,xyz@abc.com,#event_desc at #timestamp in #vehicle_desc with #driver_nam
When an overspeeding event (event ID 1) occurs, an SMS message will be sent to the numbers +27831234567 and
+27829876543 and an e-mail will be sent to xyz@abc.com. The text of the message will be something like “Over speeding at
29/08/2002 16:33:42 in Mercedes Actros 37 (XYZ12345) with John Smith driving”. As the Vehicles and Drivers fields are both set
to * (any), this rule will apply to all vehicle and driver combinations.

Rule Changes

When any changes are made to the rule file it is necessary to stop and restart the SMS Processor and Wireless Internet Service
(GPRS & WLAN) before the changes will take effect.

Disabling Rule Processing

If you no longer wish notifications to be sent, merely delete or rename the rule file. Once again you must stop and restart the SMS
Processor and Wireless Internet Service (GPRS & WLAN) for this change to take effect.

688
www.mixtelematics.com

688
 689

6 Fleet Manager Packages

6.1 Fleet Manager Track & Trace
© 2008 MiX Telematics | Updated 2008/06/11

Fleet Manager Track & Trace is a subset of the Fleet Manager Professional enterprise fleet management solution.

It replaces the current FM Remote Client and provides a simple yet comprehensive solution that encompasses the most
frequently used FM Professional functions. Similar to the FM Remote Client, FM Track & Trace is an FM-Web Service-specific
application aimed at large FM-Web Service customers who do extensive fleet management of big fleets. The maps used in the
application are installed locally to optimise the performance of mapping functionalities, whereas the database is hosted on the
Bureau and accessed remotely by FM Track & Trace.

FM Track & Trace includes functionality for real-time and historical tracking of vehicles and drivers, location management,
messaging, route planning, job management and more.

Features
Active and Passive Tracking

Request the vehicle position in real-time or view the route taken after the trip has been downloaded. Active Trail allows hourly
updating of the Fleet Manager software with GPS vehicle positions.

Manage Locations

Add any desired location such as customer, supplier or no-go zone.

Route Planning

Plan routes by entering stops, start times and duration of each stop. This can serve as daily job activity sheets for your drivers.

Messaging and Jobs

689
www.mixtelematics.com

689
 690

Send your drivers job instructions and monitor job progress. Seamless integration with the VDO Dayton range of navigation
systems ensures drivers can concentrate on their driving without worrying about how to get there. Alternately send messages to
the FM Terminal and receive responses from drivers.

Mapping and Tracking

The FM Map Set, integrated with FM Track & Trace, enables various mapping display options and functionality including the
ability to manage locations and track vehicles.

Active and Passive Tracking

Track your fleet in real time or replay historic trips on a digital map. FM Track & Trace allows you to zoom in or out, pan around
the map, display / hide locations, and display more detailed position information. Start or stop tracking a vehicle by sending an
instruction from the office. The on-board computer can also be configured to initiate tracking automatically when user-defined
events or conditions are detected.

Location Management

690
www.mixtelematics.com

690
 691

Define and add new locations or edit and delete existing locations

System Requirements

· Operating System: Windows 2000, Windows XP Professional

· Processor: Pentium IV 1.6 GHz or higher

· Disk Space: 1 GB free disk space

· RAM: 512 MB

· CD-ROM Drive

691
www.mixtelematics.com

691
 692
6.1.1 Fleet Manager Track & Trace Installation Guide

© 2008 MiX Telematics | Updated 2008/06/11

Ensure you have Administrator rights for the workstation you wish to install the software on.

Uninstall old FM installations

Uninstall any existing FM Pro installations by:

· Using the “Add or Remove Programs” functionality in the Control Panel.

· Ensuring the C:\Program Files\Fleet Manager Professional directory is deleted.

Uninstall any existing GPS Log Viewers installations by:

· Using the “Add or Remove Programs” functionality in the Control Panel.

· Ensuring the C:\Program Files\Fleet Manager GPS Log Viewer directories are deleted.

Uninstall any existing Remote Client installations using the “Add or Remove Programs” functionality in the Control Panel.

Install FM Track & Trace

Insert the FM Track & Trace disk into your CD-ROM drive. Click on “Install Fleet Manager Track & Trace” to install the software.

Click "Next"

692
www.mixtelematics.com

692
 693

Read the License Agreement, click "Yes" to accept the terms and continue the installation:

693
www.mixtelematics.com

693
 694

Click "Next" to install Track & Trace in the default location, or "Browse" to select a different folder:

Click "Next" to confirm programme location:

694
www.mixtelematics.com

694
 695

The remote server URL will be automatically entered in the URL field. Click "Next".

695
www.mixtelematics.com

695
 696

Installation on your computer will commence. This may take a few minutes.

Please note that the FM Track & Trace install shield calls the Regional Map Set install shield that installs the maps. The
registration code for the Regional Map Set can be obtained by contacting support@mixtelematics.com. Once installation is
complete, click "Finish" to end.

696
www.mixtelematics.com

696
 697

To register your product click on "Register Software" on the installation screen. This will take you to the Upgrade+ website:

697
www.mixtelematics.com

697
 698

698
www.mixtelematics.com

698
 699
6.1.2 Fleet Manager Track & Trace User Guide

© 2008 MiX Telematics | Updated 2008/06/11

Before you start, please ensure you have correctly installed and registered FM Track & Trace.

Open FM Track & Trace by clicking on the icon on your desktop or in your Start menu and login using your FM Bureau or FM
Web user name and password.

Select your organization.

699
www.mixtelematics.com

699
 700

Four default view screens will be displayed:

· FM Fleet Manager Track & Trace

· Active Vehicles

· Active Messages

· Map Viewer – select a map viewer window

Although only these default screens are shown, full FM Web functionality is available using the toolbars and menus.

You may see a pop-up indicating that a new event message has been received.

700
www.mixtelematics.com

700
 701

To view, click “Yes”. There are options provided to copy or print the message. Click “OK” to go to the next message. To mark as
read without viewing, click “No”

NOTE: If you change the view before exiting the program, your new selection will open as default when the program is restarted.

Main Screen Navigation

The main screen provides complete access to FM Track & Trace functionality, including reporting, saving and viewing information
on your fleet.

701
www.mixtelematics.com

701
 702

NOTE: Access to these functions is role-based. You may not be able to access all of them.

The tool bars provide access to the most commonly used features of the software, with buttons for the following functions on the
standard toolbar:

Delete - deletes the selected item.

Properties - opens the selected item's property page.

Event Definitions - opens the Event Definitions property page.

Trip Categories - opens the Trip Categories dialog.

Add Site - opens the Site Properties property page for a new site.

Add Vehicle - opens the Vehicle Properties property page for a new vehicle.

Add Driver - opens the Driver Properties property page for a new driver.

Add Passenger - opens the Passenger property page for a new passenger.

Add Vehicle Configuration Group - opens the Vehicle Configuration Group property page for a new vehicle configuration
group.

Add Vehicle Reporting Group - opens the Vehicle Reporting Group property page for a new vehicle reporting group.

Add Driver Configuration Group - opens the Driver Configuration Group property page for a new driver configuration group.

Add Driver Reporting Group - opens the Driver Reporting Group property page for a new driver reporting group.

Options - opens the Options dialog.

Extension Manager - opens the Extension Manager dialog.

Plug Information - opens the Plug Information dialog.

Quick Download - opens the Download wizard.

Activity Timeline - opens the Activity Timeline.

702
www.mixtelematics.com

702
 703

View - changes the manner that items are displayed in the list view.

Active Tracking and Messaging – displays the Active Vehicles window.

Manage Jobs – opens the Manage Jobs window

New Job Message – opens the Add a Job window

Send Free-text Message – sends a free-text message

SMS Message to Mobile – sends an SMS message to a mobile phone

Plot GPS Logs – opens the Plot GPS Logs wizard to report by Site, Reporting Groups or Vehicles

Show Map – loads the Map Viewer

Currencies – opens Currencies window with list of available currencies

Locations – opens a list of loaded locations

Routes – opens the Routes dialog box

Contacts – opens a list of loaded contacts

Find – opens a search box to search for ID or part of a name/description

Vehicle Route Planner – opens the Route Planner window to plot a route per vehicle

Shortcut Bar

703
www.mixtelematics.com

703
 704

A shortcut bar at the left side of the main program window allows the creation of shortcuts to items in the tree and list view
windows. These shortcuts are reflected as icons with a caption, in the same manner as shortcuts that are shown on your
Windows desktop. To use a shortcut, click on it using your left mouse button.

The shortcuts are arranged in system groups with shortcuts to the standard system objects. Groups are represented by bars at
the top or bottom of the shortcut bar and to switch to a group when you click on its bar.

The shortcut bar can be hidden or redisplayed using "View".

To create a shortcut to an item in the folder list or list view, right-click the item and select the Add To List Bar option. This option
has a sub-menu listing the groups that the shortcut can be created in. If you choose New Group you will be prompted for the
name of the new group.

Folder List
The folder list is a tree view window similar to the one in Windows Explorer that appears at the left side of the main program
window. This window presents a hierarchical view of your organisation allowing you to navigate quickly to any of your
configuration groups, reporting groups, passengers, sites, vehicles or drivers.

The folder list can be hidden by clicking on the in the bar above the folder list. When the folder list is hidden and you move
your mouse over the object title above the list view window, it will become a raised button that you can click to redisplay the folder
list. The folder list can also be hidden and redisplayed with an option on the View menu.

704
www.mixtelematics.com

704
 705

List View Window

A list view window to the right side of the main program window contains icons representing the items contained within the folder
selected to the left.

Double clicking on an item will display any items belonging to the item, or its property page if it has no sub-items. By right clicking
on the header bar, a column chooser will display which allows you to select or deselect columns of your choice for viewing.

705
www.mixtelematics.com

705
 706

Accessing Reports
Reports on your fleet can be accessed quickly and easily using the main window and shortcut bars.

Main window Reporting

706
www.mixtelematics.com

706
 707

System Shortcuts
To the left of the main screen is a menu bar with shortcuts to data, grouped by function.

Clicking on one of the icons in the column on the left of the main window will select a folder in the Folder List and show its
contents in the list window.

Sites

707
www.mixtelematics.com

707
 708

List your sites list in the folder list. Click on the "+" or "-" to expand or collapse the list. Click on an item in the folder list to view its
contents in the list window.

Vehicles

List your vehicles folder in the folder list. Click on the "+" or "-" to expand or collapse the list. Click on an item in the folder list to
view its contents in the list window.

Drivers

List your drivers folder in the folder list. Click on the "+" or "-" to expand or collapse the list. Click on an item in the folder list to
view its contents in the list window.

Passengers

List your passengers folder in the folder list. Click on the "+" or "-" to expand or collapse the list. Click on an item in the folder list
to view its contents in the list window.

Vehicle Configuration Groups

List your vehicle configuration groups folders in the folder list. Click on the "+" or "-" to expand or collapse the list. Click on an
item in the folder list to view its contents in the list window.

Vehicle Reporting Groups

List your vehicle reporting groups folders in the folder list. Click on the "+" or "-" to expand or collapse the list. Click on an item in
the folder list to view its contents in the list window.

Driver Configuration Groups

List your driver configuration groups folders in the folder list. Click on the "+" or "-" to expand or collapse the list. Click on an item
in the folder list to view its contents in the list window.

Driver Reporting Groups

List your driver reporting groups in the folder list. Click on the "+" or "-" to expand or collapse the list. Click on an item in the folder
list to view its contents in the list window.

708
www.mixtelematics.com

708
 709
6.1.3 Fleet Manager Track & Trace User Guide - Maps, Vehicles and Messages

© 2008 MiX Telematics | Updated 2008/05/07

Map Viewer Window

The default Map Viewer window shows vehicles selected in the Active Vehicles window. By default this opens in maximum zoom-
out view.

The Map Viewer window is automatically sized to dock with the Active Vehicles and Active Messages windows, but you can
maximize the map viewer to full screen. Minimizing will re-dock it with the other two windows.

Use your mouse to move up, down or side-to-side by clicking on a corner or side of the map.

Map Navigation
As you move your mouse over the map, the latitude and longitude will be displayed in the lower left-hand corner of the screen.

709
www.mixtelematics.com

709
 710

· Use the values at the bottom of the map to view approximate distances.

· Click and drag a rectangle on the map viewer to zoom into a location.

· Click to the left, right, top or bottom of the screen to move the view in those directions

· Click to zoom out to the fullest extent, click to zoom in, click to zoom out, and click to zoom to street
level.

· Use the drop-down menu just above the map to zoom to a defined location.

To the left of the Map Viewer screen is a map legend, a guide to visual elements on the map. Loading additional layers will add
items to the legend. You will be prompted to save any changes when exiting the program.

710
www.mixtelematics.com

710
 711

Vehicles you selected when the program opened are shown on the map. Placing your mouse over a vehicle location will produce
an "i" icon – double-click it for details of the vehicle in a pop-up window.

You may set the vehicle information you would like to show using the menu bar, using “View” and “Vehicle Options”. A red arrow
indicates the direction the vehicle is travelling.

Menu and Toolbar

Use the expanding text menus and short-cut icons to access map and location options:

711
www.mixtelematics.com

711
 712

Manage map viewer output:

· Save the current map layout

· Print the current map layout

· Export the map layout to your computer as a Bitmap file

· Exit the map viewer

Manage how the map viewer displays:

· Zoom out to the fullest extent , in , out or to street level

· If you have changed the view (zoomed in or out, jumped to a location etc), navigate through the views using "Previous View"

and "Next View"

· Save the current view - assign a name to the view. The name will appear in the upper drop-down menu and you can
jump to it by clicking the name later.

712
www.mixtelematics.com

712
 713

· Remove the current view - remove a saved view from the list.

· Select or de-select Street Rendering, Street Names or Place Names to choose whether they are displayed in the map viewer.

· Select or de-select Vehicle Options to display on the map.

· Use Label Options to choose which information to display for a vehicle on the map.

· Select or de-select Show Trip Replay Control to view this on the map.

Manage locations:

· Add a location by shape

· Delete a selected location

· Select or de-select Show Locations and Location Names to choose whether they are displayed in the map viewer.

Edit and measure:

· Find an address - type in the street name and suburb in the pop-up window

· Add a new street section by clicking on the start and end of the section, as per instructions in the pop-up window.

· Measure distance between two points by clicking two points as per the instructions in the pop-up window.

713
www.mixtelematics.com

713
 714

Manage map layers and format:

· Add a map layer from a file.

· If you have a number of layers added, you can remove an active layer , or remove all layers.

· Manage map regions - select which map regions to show.

· Change map look - choose a format from file.

· Select or de-select "Show Map Legend" and "Lock Map Legend" to choose whether they are displayed in the map viewer.

· Open the map viewer help.

Active Vehicles Window

Use the Active Vehicles window to view the current activity of your vehicles, their movement history and tracking status. By
default, all vehicles you selected when the program started will be shown in this window.

714
www.mixtelematics.com

714
 715

The Active Vehicles list shows:

· List of vehicles

· Vehicle colour on the map

· Current status - moving or stopped

· Last GPS point

· Whether the vehicle is at a specified location or not. If it is at a location, the location name is shown.

Click on a vehicle in the list to view further status and information. Double-click a vehicle to centre it on the Map screen at right,
then use the Map controls to zoom from maximum expanded view to street level.

Navigation

The menu bar contains text and icon shortcuts to functions within the Active Vehicles window.

715
www.mixtelematics.com

715
 716

Use the drop-down text menus and icons to view Vehicles, Locations and Tools options:

Manage vehicle display:

· Add a vehicle to the Active Vehicles by selecting it from the pop-up window. You can select a single vehicle or many
vehicles. Deselect a vehicle in the pop-up window to remove it from the Active Vehicles list.

· Remove a selected vehicle from the Active Vehicles list .

· Request the current position of a selected vehicle.

· Initiate tracking of a selected vehicle. Use the pop-up window to set parameters.

· Stop tracking a selected vehicle.

· Centre a selected vehicle on the map view.

· Plot a selected vehicle's trail on the map. Choose a map viewer and number of points to plot from the pop-up window.

716
www.mixtelematics.com

716
 717

· Show Last Trip on New Map - opens a new map viewer window with the last trip for the selected vehicle displayed.

· Change Tracking Icon - choose an icon colour from the pop-up window to change the vehicle's icon colour on the map.

· Increase Daily SMS Limit - use the pop-up window to change the selected vehicle's SMS limit.

· Messages - this option may not be available, along with Dayton-only functions, Manage Jobs ], New Job Message

and Send Free Text Message . Access to these functions depends on role.

· Set Immobiliser/Relay Drive - Please note the warning message associated with this function!

· Clear Message Buffer clears unsent messages to the selected vehicle. Confirm the command using the pop-up window.

· Request GPRS connection - confirm a request for a high-priority message to be sent using the pop-up window. Note that this
will only apply to GPRS-capable vehicles.

Manage locations relative to Active Vehicles:

· Add Location opens the locations list window, from where you can manage your locations.

Manage your view with Tools:

· Tile windows - arranges open windows to fit within your screen so you can view them all at the same time.

· Save Window Layout - saves the layout you have chosen for your windows, and will load this the next time you start the
programme.

· Options opens a pop-up window with tabs to select Filters, Display, Tracking, Free-Text, Predefined, Jobs and Advanced
settings. These options are shared by the Active Message Window.

717
www.mixtelematics.com

717
 718

· Show All Map Viewers - displays all open map viewers.

· Exit - closes the Active Vehicles window.

Other functions available from the menu bar are:

· Opens a Locations manager window

· Opens a Routes manager window for selected vehicle

· Opens a Contacts manager window and lists current contacts

· Opens a Manage jobs window

· Add a job

· Send a free-text message

· Send an SMS to a mobile – opens a Send SMS window

Active Messages Window

A list of the most recent Active Messages is displayed.

718
www.mixtelematics.com

718
 719

Double-clicking any event in the list will open a window giving details.

Place your mouse over the icons in the message list to check priority , GPS status or type .

The Options button in the lower right-hand corner of the Active Vehicles screen opens an Active Tracking and Messaging Options
window. These settings are shared by the Active Vehicles window.

719
www.mixtelematics.com

719
 720

720
www.mixtelematics.com

720
 721
6.1.4 Fleet Manager Track & Trace User Guide - Reports and Management

© 2008 MiX Telematics | Updated 2008/05/07

Vehicle Performance
Activity Timeline

Vehicle activity over time is shown in linear graph format.

The Activity Timeline screen will show periods of activity in linear graph format for the vehicle you have selected, over the time
period you have chosen.

Map-based timeline can be shown using the Plot GPS Log or using the Plot GPS Log Criteria Wizard

721
www.mixtelematics.com

721
 722

Driver Performance
A. Activity Timeline

Driver activity over time is shown in linear graph format.

722
www.mixtelematics.com

722
 723

The Activity Timeline screen will show periods of activity in linear graph format for the driver you have selected, over the time

period you have chosen. Map-based timeline can be accessed using the Plot GPS Log .

723
www.mixtelematics.com

723
 724

B. Scoring Graph

Driver scoring over time is shown in graph format. Use the screens to select information to show.

724
www.mixtelematics.com

724
 725

Change how the information is displayed using the Designer or Wizard.

725
www.mixtelematics.com

725
 726

726
www.mixtelematics.com

726
 727

Communication, Messaging and Jobs

A. Communications

727
www.mixtelematics.com

727
 728

Access all your active messages for selected vehicles in the Active Messages window, and view their current location on the Map
Viewer.

B. Messaging and Jobs

NOTE: Access to this feature is role-dependant and requires an FM terminal in the vehicle.

Send a job or pre-defined message to a driver using pre-set messages via the Add New Job window.

728
www.mixtelematics.com

728
 729

C. Manage Jobs

Access and manage messages to drivers and vehicles using the Manage Jobs window options.

729
www.mixtelematics.com

729
 730

D. Send Free-text Message

Send a free-text message to a vehicle using the Send Free-text Message window.

730
www.mixtelematics.com

730
 731

Location Manager
Use the Location Manager to view and manage locations.

A. Using the Map

Show Map opens a Map Viewer window. Note that selected vehicles are not shown on this map. This map view is specific to
locations.

731
www.mixtelematics.com

731
 732

B. Navigation

· Please your mouse over a point on the map to view its latitude and longitude at the bottom of the map viewer screen.

· Use the values at the bottom of the map to view approximate distances.

· Click and drag a rectangle on the map viewer to zoom into a location.

· Click to the left, right, top or bottom of the screen to move the view in those directions

· Click to zoom out to the fullest extent, click to zoom in, click to zoom out, and click to zoom to street
level.

· Use the drop-down menu just above the map to zoom to a defined location.

732
www.mixtelematics.com

732
 733

C. Menu and Toolbar

Use the expanding text menus and short-cut icons to access map and location options:

Manage map viewer output:

· Save the current map layout

· Print the current map layout

· Export the map layout to your computer as a Bitmap file

· Exit the map viewer

733
www.mixtelematics.com

733
 734

Manage how the map viewer displays:

· Zoom out to the fullest extent , in , out or to street level

· If you have changed the view (zoomed in or out, jumped to a location etc), navigate through the views using "Previous View"

and "Next View"

· Save the current view - assign a name to the view. The name will appear in the upper drop-down menu and you can

jump to it by clicking the name later.

· Remove the current view - remove a saved view from the list.

· Select or de-select Street Rendering, Street Names or Place Names to choose whether they are displayed in the map viewer.

· "Vehicle Options" is not available on the Locations Map Viewer.

Manage locations:

· Add a location by shape

· Delete a selected location

734
www.mixtelematics.com

734
 735

· Select or de-select Show Locations and Location Names to choose whether they are displayed in the map viewer.

Edit and measure:

· Find an address - type in the street name and suburb in the pop-up window

· Add a new street section by clicking on the start and end of the section, as per instructions in the pop-up window.

· Measure distance between two points by clicking two points as per the instructions in the pop-up window.

Manage map layers and format:

· Add a map layer from a file.

· If you have a number of layers added, you can remove an active layer , or remove all layers.

· Manage map regions - select which map regions to show.

· Change map look - choose a format from file.

· Select or de-select "Show Map Legend" and "Lock Map Legend" to choose whether they are displayed in the map viewer.

Open the map viewer help.

Manage Locations

735
www.mixtelematics.com

735
 736

Access and manage your locations using the Locations window.

736
www.mixtelematics.com

736
 737

6.2 FM Tracer
© 2008 MiX Telematics | Updated 2008/06/20

Available in Europe only

The FM Tracer solution is powered by the FM 3310i on-board computer which includes an internal GPS receiver and GSM
modem. The GPS receiver allows for the recording of highly accurate position information. The GSM modem enables the
transmission of data, making real-time vehicle tracking and immediate event notifications possible.

The optional Garmin FM Interface allows for the connection of a Garmin Portable Navigation Device to FM Protector to which jobs
can be dispatched, which can route the driver to the exact job location, as well as facilitating the sending and receiving of text
messages.

Two-way voice communication is possible when using the optional FM Voice Kit in combination with the internal GSM modem.

Features

ACTIVE TRACKING

Tracking and Route Replay Track the vehicle position in real-time, or view and replay historic routes taken on a digital map.

GPS Data Recording A variety of information is recorded with every GPS position such as vehicle and driver ID
(optional), date and time, latitude and longitude, altitude, heading, speed and the number of visible
satellites.

Manage Locations Add, delete or edit user-defined locations such as customer, supplier, no-go zone etc. The entry
and exit from locations are recorded along with the date and time of the occurrence and the
duration spent at each location.

Active Events Active events are based on active locations, GPS speed and 2 user inputs. Immediate event
notifications can be sent via SMS whenever a critical event is recorded. Such events could be
when entering or exiting a Zone, Panic / Assist button pressed (optional), Battery disconnect, etc.

Backup Battery As an additional layer of security the FM 3310i is equipped with a Backup Battery, making tracking
possible even if the vehicle’s main battery has been disconnected. The Backup Battery starts to
operate as soon as the supply to the main vehicle battery is cut.

COMMUNICATIONS

Downloading from / The GSM modem is used to download data from and upload data to the FM 3310i via GPRS, SMS
Uploading to vehicle or CSD Data call. This allows for real-time tracking and immediate SMS event notifications.

It is possible to upgrade firmware or update the configuration remotely over-the-air using the GSM
modem, thus reducing the need to remove the vehicle from duty when performing maintenance.

737
www.mixtelematics.com

737
 738

Satellite Communication Satellite communication allows limited data download from and upload to the FM 3310i when
using the optional FM Sat Comms transceiver. This provides real-time tracking and event
monitoring when out of GSM coverage. FM Sat Comms provides global coverage except at the
extreme poles of the earth.

Voice Calls Two-way voice communication is possible when using the optional FM Voice Kit, which allows for
hands-free operation.

VEHICLE

Trip Data Recording The following data is recorded: date and time, distance travelled, journey duration, vehicle speed,
journey departure and arrival time, location entered / exited, driver name (optional), driver ID
(optional) and vehicle ID.

Driving Violations Over speeding events are triggered when exceeding a preset speed limit.

Input Events Two user-configurable digital inputs are available which can be employed to trigger custom events
such as cargo door open and panic / alert button pressed.

Servicing and Licensing Set reminders for your vehicle’s next service or for your vehicle/driver license expiry.

General information

Ignition input Used to monitor the ignition switch status.

Positive drive output Used to power external devices. Battery voltage -2V DC. It can supply current up to 1A.

Buzzer output Audio signaling device.

Audio interface This interface allows the user to make voice calls using an optional FM Voice Kit.

FM 3310i Includes: · GSM/GPRS Antenna

· GPS Antenna

· Main harness with integrated buzzer (2x frequency input, 2x digital input)

· Backup Battery

· FM on-board computer user manual

· FM300 code-plug harness and socket

· Optional: Blue driver’s plug (Driver ID)

· Optional: FM Voice Kit

· Optional: Garmin FM Interface (Jobs & Messaging)

· Optional: FM Sat Comms

Technical description

738
www.mixtelematics.com

738
 739

Voltage range 9V DC – 33V DC

Input Protection Automotive 24V load dump (160V, 2 Ohm, 400mS); short duration low-energy & high-energy
transients).

Clock Real-time with independent battery back-up.

Inputs & Events Highly configurable inputs and events.

Firmware Re-programmable firmware and configuration over wireless media (or optional wired interface).

2 Digital inputs 2 X digital inputs (I1 & I2) can be configured by the user to monitor any device that generates a
(configurable) change in voltage in the range of 0 – 38 volts.

2 RS232 Serial Ports 2 X RS232 serial ports operating at 57600 Baud rate (higher rates possible with hardware flow
control) for connecting supported serial devices using an optional serial harness.

Buzzer and LED The FM 3310i has a buzzer to warn the driver and provide feedback of the vehicle’s status.

l²C Bus Intended for use with optional code-plugs used to identify drivers, calibrate, diagnose faults,
upload firmware and new configurations, and to download unit specific configuration information.
This bus can also be used to drive the optional FM Keypad, which allows the driver to make voice
calls when used together with the optional FM Voice Kit.

Backup Battery The backup battery is powered by a rechargeable Li-Ion Battery Pack. When fully charged, the
backup time is typically 4 hours if the GSM is active in low power mode and the GPS is disabled.

Voltage range 9V DC – 33V DC

Input Protection Automotive 24V load dump (160V, 2 Ohm, 400mS); short duration low-energy & high-energy
transients).

Clock Real-time with independent battery back-up.

Technical specifications

ENVIRONMENT

Temperature (Storage) -20°C to +70°C

(Operating) -20°C to +55°C

(Charging) 0°C to +45°C

Limited GSM functionality extends to -25°C and +70°C

Circuit Protection Conformal coating over the PCB and all components (excluding connectors).

SUPPLY

Current
(Operating) <42mA at 28V (typical)*

739
www.mixtelematics.com

739
 740

(Sleep) <20mA at 28V (typical)*

(Operating) <70mA at 12V (typical)*

(Sleep) <30mA at 12V (typical)*

(Powered down) <2mA at 12V (typical)*

(Powered down) <3mA at 28V (typical)*

* The signal strength on the GSM affects the current consumption. The firmware running on the
FM 3310i micro processor affects the current consumption of the unit.

740
www.mixtelematics.com

740
 741
6.2.1 FM Tracer Installation Guide

© 2008 MiX Telematics | Updated 2008/05/07

This user manual is applicable to the 3310i On-board Computer. Available in Europe only

The 3310i On-board Computer should be installed by a suitably qualified person. Please consult the installation manual of the
applicable on-board computer in the Fleet Manager Software CD for installation details.

The 3310i On-board Computer must be powered from a battery source. The signal wires should not exceed 30 metres.

Operation
The 3310i On-board Computer is restricted to be used with FM-Web only.

The functioning of the 3310i On-board Computer is determined largely by the configuration specified within the Fleet Manager
Software.

Please note that sections referring to Driver Identification and “Driver Code Plug” are applicable if the optional Driver ID is used.

Armed / Disarmed Status

Armed status is indicated by one short flash of the red lamp every two seconds. In some installations, the vehicle cannot be
started while in the armed mode, and must be disarmed as described below. The red lamp remains off while the 3310i On-board
Computer is disarmed.

Driver Identification and Disarming of the 3310i On-board Computer

If driver identification is required before the trip can begin, the driver must insert the blue driver key into the Code Plug Socket. If
the driver is authorised to drive the vehicle, the 3310i On-board Computer will beep twice briefly and the LED in the reader unit
will be switched off. The unit is now disarmed and will allow the vehicle to be started.

Troubleshooting

Symptom Probable Cause Action

LED does not Flash. · No Voltage. · Check the voltage supply to the 3310i On-board
Computer

The 3310i On-Board · The Driver Code Plug is not assigned to · Use the correct Driver Code Plug or ensure Driver
Computer cannot be the vehicle. Code Plug is assigned to the vehicle.
enabled.

The Buzzer sounds when · The driver registration was not done or · Register with the Driver Code Plug.
turning on the ignition.
· The Driver Code Plug is not released / · Ensure Driver Code Plug is released for the
configured for the vehicle. vehicle and register with it.

Beep and Flash Codes

The 3310i On-board Computer status is indicated by audible and visual signals. The following table shows the codes used to
indicate the various states.

Symbols used:

Audible buzzer

741
www.mixtelematics.com

741
 742

Red lamp on Code Plug socket

__ Signal sequence.

Condition Beep and Flash Code Durations

At Installation

No beeps
Only operating system loaded
1s on. 1/8s off
_________ _________ _________ _________

No beeps
Operating system and device
drivers loaded
1/2s on. 1/2s off
_____ _____ _____ _____ _____

No beeps
Normal ‘Armed Mode’
1/16s on. 2s off
_ _ _

Before Trip

No beeps
Normal ‘Armed Mode’
1/16s on. 2s off
_ _ _

___ ___ ___ ___ 1/4s on 3/4s off

Driver identification requested
Lamp off

_ _ 2 x 1/8s beeps
Driver authorized to drive
vehicle
Lamp off

_____ 1 x 1/2 s beep

Driver not authorized to drive
vehicle
1/16s on. 2s off
_ _ _

_ _ _ 3 x 1/8s beep
OBC memory 80% - 95% full
Lamp off

3 x 1/2s beeps
OBC memory 95% - 100% full _____ _____ _____
Lamp off

742
www.mixtelematics.com

742
 743

During Calibration

__________ __________ 1s on. 1s off.

Speed or RPM Calibration
Code Plug inserted
Flashes
__ __ __ __ __ __ __ __ __ __ __

_ _ _ 3 x 1/8s beeps
Setting date and time (Driver
Code Plug)
Unchanged
……………….. unchanged ………………..

During A Trip

No beeps
Start of trip
Flashing stops

No beeps
While driving
Lamp off

______________________________________ Continuous beep

Event alarm
Lamp off

_
Start of sub-trip 1 x 1/8s beep

_ 1 x 1/8s beep
End of trip
1/16s on. 2s off
_ _ _

743
www.mixtelematics.com

743
 744

7 Fleet Manager Hardware Products and Accessories

© 2008 MiX Telematics | Updated 2008/06/18

Packages
FM100

The FM100 is the entry-level product for the Fleet Manager range. It offers an ideal solution for driver and vehicle management
for a small fleet. The FM100 records the most important events – over-speeding, over-revving, green band driving, harsh braking
and excessive idling. The data can be transferred from the vehicle to the software using the green vehicle plug with minimum
effort.

> FM100 Overview

FM200 Plus

The FM200 Plus is the ideal solution for Driver and Vehicle Management. In addition to recording the standard events, you can
also define and monitor additional customised events, such as the emergency lights, refrigeration units and trailer coupling. The
FM200 Plus is more advanced than the FM100 and offers standard recording of data, second-to-second (Tacho) data (used for
accident analysis) as well as additional custom events (e.g. headlights, driver door open).

>FM200 Plus Overview

FM200 Locator

The Fleet Manager 200 Locator (FM200 Locator) is an on-board computer based on the stable and reliable platform of the FM200
Plus. The FM200 Locator offers the extensive driver and vehicle management the FM200 Plus offers, and an internal GPS
receiver, where GPS information (such as the GPS location, GPS heading and GPS speed) can also be recorded.

> FM200 Locator Overview

FM200 Communicator

The Fleet Manager 200 Communicator (FM200 Communicator) is an on-board computer based on the stable and reliable
platform of the FM200 Plus. The FM200 Communicator offers the same extensive driver and vehicle management, but has an
additional internal GPS receiver and GSM modem. The GPS receiver allows the recording of GPS Position information, which
allows you to know exactly where you driver has been. With the GSM modem, you can actively track your vehicles, and request
their position at any time.

> FM200 Communicator Overview

FM200 ComLink-GSM

The FM200 ComLink-GSM is based on the FM200 Plus, all the FM200 Plus functionality is available on the FM200 ComLink-
GSM with the exception of the external use of the S2 serial interface. The FM200 ComLink-GSM is fitted with an onboard GSM
module.

>FM200 ComLInk-GSM

FM200 CAN

The FM200 CAN is based on the FM200Plus, all the FM200Plus functionality is available on the FM200 CAN. The FM200 CAN is
fitted with an on-board CAN module which allows it to communicate on two discrete CAN buses.

>FM200 CAN

FM300 ComLink-GSM

The FM300 ComLink-GSM, the latest on-board computer on the market, provides a comprehensive fleet management solution.

744
www.mixtelematics.com

744
 745

The unit combines extensive driver and vehicle management with advanced communication functionality.

An internal GSM/GPRS modem that allows remote communication between the vehicle and your office, enables you to receive
real-time notifications of events, to perform remote downloads of driver and vehicle data, and to perform configuration uploads all
without physical access to the vehicles.

The modularity of the FM300 ComLink-GSM allows you to connect additional accessories and information systems such as an
optional headset and external keypad. The headset receives incoming calls ensuring the driver remains focused on the road,
contributing to enhanced communication and safety. Other accessories such as additional sensors, including accident recorder,
tachographs and sensors for load or fuel measuring improves the maintenance and efficiency of your fleet dramatically.

>FM300 ComLink-GSM

FM300 Communicator

The Fleet Manager 300 Communicator (FM300 Communicator) is an on-board computer based on the stable and reliable FM200
Plus platform. The FM300 Communicator offers the same extensive driver and vehicle management as FM200 Plus and has an
additional internal GPS receiver and GSM/GPRS modem.

The GPS receiver allows the recording of GPS position information, enabling you to determine the movement history of the
vehicles. The GPS receiver in conjunction with the GSM/GPRS modem allows active tracking of vehicles enabling you to request
their position at any time. In addition the GSM/GPRS modem enables you to receive real-time notifications of user specified
events such as the time arrived at a specified location.

Remote data upload and download to and from your FM300 Communicator with the GSM/GPRS Modem, ensures that data
transfer does not interfere with the daily activities of the fleet. An optional headset that receives incoming calls ensures the driver
remains focused on the road, contributing to enhanced communication and safety.

Security concerns are addressed with the provision of an optional battery backup that allows uninterrupted communication with
the Fleet Manager Software even if the unit’s power is cut.

>FM300 Communicator

FM300 CAN

The FM300 Communicator (CAN) is the ideal on-board computer for the management of vehicle and driver performance, driver
safety and vehicle utilization. The on-board computer enables the fleet manager to remotely monitor the performance of a
vehicle. Data is recorded on a second-by second basis with driver violations and detailed trip information being made available to
the fleet manager in real-time.

The FM300 Communicator (CAN) on-board computer integrates directly with the vehicle’s CANbus electrical interface which
today is readily available in most modern vehicles.

The CANbus interface has several benefits over the traditional way of capturing vehicle data. Vehicle speed, engine speed
(RPM), power takeoff (PTO) and fuel usage as supported by the FM300 Communicator (CAN) on-board computer is read directly
from the CANbus using the FMS standard. This not only allows for the processing of more accurate data, but makes installation
of the unit much easier.

>FM300 CAN

FM300 Twin Serial Harness

The FM300 Twin Serial Harness enables the connection of two supported serial devices simultaneously to the FM300 On-Board-
Computer in place of the FM terminal by exposing serial ports S1 and S3 for use.

>FM300 Twin Serial Harness

FM 3310i

The FM 3310i on-board computer includes an internal GPS receiver and GSM modem. The GPS receiver allows for the recording
of highly accurate position information. The GSM modem enables the transmission of data, making real-time vehicle tracking and

745
www.mixtelematics.com

745
 746

immediate event notifications possible.

Support for satellite communications is available with an optional FM Sat Comms transceiver that enables real-time tracking and
event monitoring for a vehicle that is out of GSM coverage.

Two-way voice communication is possible when using the optional FM Voice Kit in combination with the internal GSM modem.

>FM 3310i

FM Messenger

The FM Messenger is a developed package with the focus on communication. The FM Messenger provides the Fleet Manager
with the following functionality:

· Driver and Vehicle Management

· Location Management

· Active Tracking & Immediate Alerts (Active Events)

· Two-way Messaging with an in-vehicle terminal

> FM Messenger Overview

FM Navigator

The FM Navigator is a perfect solution for communication and navigation within fleets. The FM Navigator provides the Fleet
Manager with the following functionality:

· Driver and Vehicle Management

· Location Management

· Active Tracking & Immediate Alerts (Active Events)

· Two-way Messaging with an in-vehicle terminal

· Navigation

>FM Navigator Overview

Accessories
FM Terminal

The Fleet Manager Terminal is a versatile add-on to the FM range of FM200 on-board computers. The FM Terminal supports text
messaging (job and free-text), capturing of operating data (e.g. driving reasons, reasons for stopping, fuel quantity and costs,
customer details etc.)

> More on FM Terminal

FM Keypad

The Fleet Manager Keypad (FM Keypad) is a smart data input and display unit. The drivers can use the FM Keypad to select
driving reasons for their trips. The FM Keypad also has Voice Functionality.

> More on FM Keypad

746
www.mixtelematics.com

746
 747

FM Trailer ID

The Fleet Manager Trailer ID (FM Trailer ID) is designed and developed to monitor your assets and cargo. The FM Trailer ID can
be fitted to any trailer, which can be coupled to a vehicle equipped with any of the FM200 range of on-board computers.

> More on FM Trailer ID

FM Impact Sensor

The Fleet Manager Impact Sensor accurately detects and record any impacts to the vehicle or equipment. The severity of the
impact is transmitted and recorded on the on-board computer. Depending on your requirements, the on-board computer can
either log the impact or send an immediate notification, informing you of the impact.

> More on FM Impact Sensor

VDO Dayton

The FM Messenger uses VDO Dayton PC 5XXX Pro as in the in-vehicle navigation system. This allows support for 2 way
messaging between the office and drivers. Drivers can read and accept job messages sent to them and be guided to their
destinations. The office can also at any stage see the status of a job.

FM TCO Interface

This device is used to download information from the FTCO, MTCO and TVI2400 tachographs onto the FM200 on-board
computer. The data available ranges from vehicle speed, engine speed and distance travelled to driving and stop times for each
individual driver.

> FM TCO Interface Installation Manual

FM KTCO Interface

The FM KTCO1318 optical interface is designed to pass Driving Modes as well as vehicle and engine speed (if available on the
specific tachograph), to a standard FM200 Plus unit.·

> FM KTCO1318 Installation Manual

FM GPS Interface

The Global Positioning System (GPS) is a satellite-based navigation system which uses up to 24 satellites within the network to
pin-point the exact location of a object, anywhere in the world, any time of the day.

> FM GPS Interface Installation Manual

FM DECT

The DECT solution is used for the remote download of Fleet Manager data from the FM200 Plus or FM200 Locator (FM200 Plus
+ GPS) on-board computers. The system consists of the DECT Base Station that is installed in the vehicle yard, and DECT
vehicle units that are installed in every vehicle. The download occurs automatically when the vehicle is in open range of 300
meters from a DECT Base Station, with no additional costs involved.

> FM DECT Installation Manual

FM200 Plus Wiring Harness

The FM200 Plus Wiring Harness is used to connect the FM200 Plus to the different outputs, such as the speed and RPM, of the
vehicle.

> FM200 Plus Wiring Harness User Manual

FM200 Plus Serial Cable

747
www.mixtelematics.com

747
 748

The FM200 Plus Serial cable facilitates the connecting of two standard RS232 Data Communication Equipment (DCE) devices
and a Fleet Manager Terminal to the FM200 Plus on-board-computer.

> FM200 Plus Serial Cable User Manual

FM Wireless Kit

The FM Wireless Kit allows data to be downloaded from, or uploaded to the FM On-board Computer. Clients now have the option
to make use of cheaper communication alternatives such as short range RF technologies like Wireless LAN. This feature of the
FM Communications Suite provides functionality equivalent to communications over GPRS.

The FM Wireless Kit firmware supports WPA PSK (WiFi Protected Access Pre-shared Key) and WPA Cisco LEAP (WiFi
Protected Access Lightweight Extensible Authentication Protocol) authentication in addition to the original WiFi security standard,
WEP (Wired Equivalent Privacy). WPA provides significantly more sophisticated data encryption and more enhanced user
authentication than WEP.

>FM Wireless Kit

748
www.mixtelematics.com

748
 749

7.1 FM Messenger
© 2008 MiX Telematics | Updated 2008/05/07

Overview

The FM Messenger is a product package focused on communication. FM Messenger provides the Fleet Manager with the
following functionality:

· Driver and Vehicle Management

· Location Management

· Active Tracking & Immediate Alerts (Active Events)

· Two-way Messaging with an in-vehicle terminal

Features

Messaging

Two-way Messaging FM Messenger has the functionality to manage and send jobs, standard and free-text
messages, do job management and reporting.

Fuel Capturing Capture fuel costs, dates of refueling and quantity to manage your fleet’s fuel intake, calculate
fuel consumption and report on the captured data.

Customer Information The FM Terminal can be used to enter customer details (e.g. Names, Codes, Costs and
Locations)

Communication

Active Events Receive messages (e.g. SMS) when selected standard or user-defined events take place, such
as headlights not on at night

749
www.mixtelematics.com

749
 750

Downloading/uploading to/ The GSM/GPRS Modem can be used to download and upload data from and to the FM
from vehicle Messenger . This can be done remotely with out the need for the vehicle to be in the yard. The
GSM/GPRS Modem also enables the FM Messenger to be actively tracked by the Fleet
Manager Software

Vehicle and Driver Management

Trip Data Recording For every journey the vehicle takes, the following information is recorded:

Date and Time, Distance or Hours, Speed or Hours, Engine Speed (RPM),Trip started / ended
time, Trip depart / arrive time, Driver Name & ID, Vehicle ID

Driving Violations The following standard violations are recorded:

Over Speeding, Over Revving, Green Band Driving (low and high), Harsh Braking, Harsh
Acceleration, Excessive Idling and Overtime Driving

Customised Events You can also define customised events, such as driver door opening, no-go zone entered,
hazard lights activated, refrigerator temperature exceeded

Second-to-Second (Tacho) FM Messenger records the status of all inputs (e.g. speed, RPM, brake lights) every second,
Data which provides valuable in-depth information for accident analysis.

Servicing and Licensing Reminders can be set when your vehicle’s next service is due or when your vehicle / driver
licence expires.

Driver Identification & A driver tag can be used to identify the driver, and a default driver can be assigned to a vehicle.
Immobilisation FM Messenger can also be installed with an immobiliser function – the car will only start if an
authorised driver inserts his driver tag.

Warning Buzzer A warning buzzer can be set to sound when driving violations or events take place.

Communication
The in-vehicle terminal (Fleet Manager Terminal) is a versatile extra to the on-board computer. The FM Terminal supports text
messaging (job and free-text) and capturing of operating data (e.g. driving reasons, reasons for stopping, fuel quantity and costs,
customer details etc.). The Graphical Liquid Crystal display can also display standard event violations such as over-speeding,
over-revving, harsh braking, harsh acceleration and excessive idle.

The FM Terminal menu is easy to use and can be customised to suit your needs. External devices (such as an IBM AT-
compatible keyboard or barcode scanner) can be added to allow the driver to quickly enter important customer information,
saving valuable working time.

The FM Terminal also has the capability to enter fuel quantities and costs when filling up. The software has various built-in fuel
reports – manually entered fuel data, captured fuel data (with external Fuel Measure equipment) and a comparison between the
entered and measured fuel data.

Data Communication

FM Messenger uses the Global System for Mobile Communications (GSM/GPRS) Network for communicating with the on-board
computer. The GSM/GPRS Modem allows the remote uploading / downloading of data, anywhere within GSM/GPRS Network
Coverage.

The communication between the vehicle and the office can be scheduled by the Fleet Manager software and used to:

750
www.mixtelematics.com

750
 751

· Download Data from the on-board computer

· Upload new device drivers and configuration to the vehicles

· Alert the office of Active Events

Fleet Manager has a unique feature - Communication Cost Control. Communication Cost Control is implemented at application
level and allows the Fleet Manager to choose which messages are urgent, and should return a response to the Fleet Manager.
The Communication Cost Control feature provides the Fleet Manager with control to keep communication costs to a minimum.

Immediate Alerts (Active Events)

FM Messenger can keep the Fleet Manager up to date with his fleet, by sending him a text message as soon as an important
event occurs - such as the door opening in a No-Go Zone. The Fleet Manager can choose which occurrences he would like to
know of and when - immediately, once the vehicle downloaded or never. The Fleet Manager is in total control of the information
he needs to successfully control and manage his fleet.

Technical Information

8 configurable analogue The FM Messenger analogue or digital inputs can be configured to monitor any device that
or digital inputs generates a change in voltage, e.g. seat belts, headlights, refrigeration units, emergency lights,
doors, PTO, UDS, trailer coupling etc.

4 auxiliary frequency input The FM Messenger auxiliary frequency input can be configured to monitor any device that generates
a change in frequency, e.g. temperature sensor, liquid flow measurement. Alternatively, this input
can be used as a pulse counter, e.g. electronic fuel consumption measurement (EDM). This input
can also be used to read low baud rate digital data (e.g. GPS).

2 Auxiliary relay drive This can be used to switch a relay with a current consumption of up to 150 mA.

1 Serial interface (1x This can be connected to any RS232 serial device using the FM Serial cable. The TTL serial
RS232) interface connects to the FM Terminal. A second RS232 Port (S2) is connected to the internal GSM/
GPRS Modem

Software
Fleet Manager Professional 9 provides the serious fleet operator with extensive fleet management tools to manage and report on
his fleet. The software enables you to manage vehicle, driver and passenger information, define and manage events to be
monitored, analyse fleet data and do extensive management reporting. In addition to the core software, Fleet Manager
Professional 9 also offers a set of extensions that allow additional monitoring and reporting on the fleet.

Our Internet Bureau Service, FM-Web, also supports the FM Messenger.

751
www.mixtelematics.com

751
 752

7.2 FM Navigator
© 2008 MiX Telematics | Updated 2008/05/07

Overview

FM Navigator is the perfect solution for communication and navigation within a fleet. FM Navigator is a product package which
provides the Fleet Manager with the following functionality:

· Driver and Vehicle Management

· Location Management

· Active Tracking & Immediate Alerts (Active Events)

· Two-way Messaging with an in-vehicle terminal

· Navigation

Features

Navigation

Navigation With the advanced FM Navigation system, you can send job messages to your drivers, and then
navigate them to their destination. This increases driver productivity, reduces communication
costs and improves customer service.

Two way Messaging The FM Navigation system enables the driver to receive and reply to text messages. This
improves communication between the office and drivers, while keeping the communication
costs down.

Location Management

Request the position of a vehicle in real-time or review the route taken after the trip has been
Active/ Passive Tracking or
downloaded. Active Trail allows the Fleet Manager software to be updated with vehicle positions
Active Trail
every hour.

Manage Locations Locations can be added showing customer, supplier, no-go zones or any desired locations.

Routes can be planned by entering stops, the planned time of start and the planned duration of
Route Planning
each stop. This can serve as daily job activity sheets for your drivers.

752
www.mixtelematics.com

752
 753

Receive data messages (e.g. SMS) when selected standard or user-defined events take place,
Active Events
such as a cargo door opening in a no-go zone, or driver arrived at customer location.

Communication

Downloading/uploading to/ The GSM/GPRS Modem can be used to download and upload data from and to the FM
from vehicle Navigator. This can be done remotely without the need for the vehicle to be in the yard. The
GSM/GPRS Modem also enables the FM Navigator to be actively tracked by the Fleet Manager
Software

Vehicle and Driver Management

Trip Data Recording For every journey the vehicle takes, the following information is recorded:

Date and Time, Distance or Hours, Speed or Hours, Engine Speed (RPM), Trip started / ended
time, Trip depart / arrive time, Driver Name & ID, Vehicle ID

Driving Violations The following standard violations are recorded:

Over Speeding, Over Revving, Green Band Driving (low and high), Harsh Braking, Harsh
Acceleration, Excessive Idling and Overtime Driving

Customised Events You can also define customised events, such as driver door opening, no-go zone entered,
hazard lights activated, refrigerator temperature exceeded

Second-to-Second (Tacho) FM Navigator records the status of all inputs (e.g. speed, RPM, brake lights) every second,
Data which provides valuable in-depth information for accident analysis.

Servicing and Licensing Reminders can be set when your vehicle’s next service is due or when your vehicle / driver
licence expires.

Driver Identification & A driver tag can be used to identify the driver, and a default driver can be assigned to a vehicle.
Immobilisation FM Navigator can also be installed with an immobiliser function – the car will only start if an
authorised driver inserts his driver tag.

Warning Buzzer A warning buzzer can be set to sound when driving violations or events take place.

Navigation
FM Navigator can dramatically improve your driver’s productivity and reduce your fleet operating costs with the VDO Dayton
Navigation system. Free-text and job messages can be read, entered and sent using the in-vehicle navigation system.

The VDO Dayton Navigation can automatically navigate the driver directly to job destination addresses, improving productivity
and reducing costs. This also ensures that the possibility of the driver getting lost is reduced dramatically.

753
www.mixtelematics.com

753
 754

Data Communication
FM Navigator uses the Global System for Mobile Communications (GSM/GPRS) Network for communicating with the on-board
computer. The GSM/GPRS Modem allows the remote uploading / downloading of data, anywhere within GSM/GPRS Network
Coverage.

The communication between the vehicle and the office can be scheduled by the Fleet Manager software and used to:

· Download Data from the on-board computer

· Upload new device drivers and configuration to the vehicles

· Alert the office of Active Events

Fleet Manager has a unique feature - Communication Cost Control. Communication Cost Control is implemented at application
level and allows the Fleet Manager to choose which messages are urgent, and should return a response to the Fleet Manager.
The Communication Cost Control feature provides the Fleet Manager with control to keep communication costs to a minimum.

Immediate Alerts (Active Messages)

FM Navigator can keep the Fleet Manager up to date with his fleet, by sending him a text message as soon as an important event
occurs - such as the door opening in a No-Go Zone. The Fleet Manager can choose which occurrences he would like to know of
and when - immediately, once the vehicle downloaded or never. The Fleet Manager is in total control of the information he needs
to successfully control and manage his fleet.

Technical Information

8 configurable analogue FM Navigator analogue or digital inputs can be configured to configured to monitor any device that
or digital inputs generated a change in voltage, e.g. seat belts, headlights, refrigeration units, emergency lights,
doors, PTO, UDS, trailer coupling etc.

4 auxiliary frequency input The FM Navigator auxiliary frequency input can be configured to monitor any device that generates a
change in frequency e.g. temperature sensor, liquid flow measurement or as a pulse counter e.g.
electronic fuel consumption measurement (EDM)

2 Auxiliary relay drive This can be used to switch a relay with a current consumption of up to 150 mA.

2 Serial interface (1x This can be connected to any TTL or RS232 serial device using the FM Serial cable (e.g. FM
RS232 and 1x TTL) Terminal). The second RS232 serial interface (S3) is used to connect the VDO Dayton to the on-
board computer.

Software
Fleet Manager Professional 9 provides the serious fleet operator with extensive fleet management tools to manage and report on
his fleet. The software enables you to manage vehicle, driver and passenger information, define and manage events to be
monitored, analyse fleet data and do extensive management reporting. In addition to the core software, Fleet Manager
Professional 9 also offers a set of extensions that allow additional monitoring and reporting on the fleet.

Our Internet Bureau Service, FM-Web, also supports the FM Navigator.

754
www.mixtelematics.com

754
 755

7.3 FM Wireless Kit

© 2008 MiX Telematics | Updated 2008/05/07

Overview

The FM Wireless Kit allows data to be downloaded from, or uploaded

to the FM On-board Computer. Clients now have the option to make use of cheaper communication alternatives such as short
range RF technologies like Wireless LAN. This feature of the FM Communications Suite provides functionality equivalent to
communications over GPRS.

The FM Wireless Kit firmware supports WPA PSK (WiFi Protected Access Pre-shared Key) and WPA Cisco LEAP (WiFi
Protected Access Lightweight Extensible Authentication Protocol) authentication in addition to the original WiFi security standard,
WEP (Wired Equivalent Privacy). WPA provides significantly more sophisticated data encryption and more enhanced user
authentication than WEP.

Features

Automated remote downloads Perform automated remote downloads of trip, event, tacho and other
data whenever the vehicle is in contact with the Wireless LAN. This is
intended for vehicles that regularly return to home base.

No GSM communication costs Data is transmitted to and from the FM On-board Computer via a
Wireless LAN, thus no GSM communication costs are incurred.

Remotely upgrade firmware There is no need to have physical access to the vehicle in order to
upgrade firmware or load new configurations. This is done Over The Air
(OTA) via the Wireless LAN.

Technical Information

Compatible on-board computer FM200 Plus and FM300 series

Wireless standard IEEE802.11b/g

Encryption • 64-bit and 128-bit data encryption using WEP (Wireless Encryption
Protocol) or

• WPA-PSK (WiFi Protected Access Pre-shared Key) encryption or

• WPA Cisco LEAP (WiFi Protected Access Lightweight Extensible

Authentication Protocol) encryption

755
www.mixtelematics.com

755
 756

Transmission range 200m under optimal conditions

We declare on our own responsibility that the product is in compliance

with following norm(s) or documents:

DIN EN 55022 (09/2003)

DIN EN 61000-6-2 (08/2002)

This product conforms to the requirements of Directive 72/245/EEC,

amended by 2004/104/EC (14 October 2004)

Components
The FM Wireless Kit comprises of the following components:

· FM Wireless Kit Modem

· FM Wireless Kit Serial Harness

· FM Wireless Kit Antenna

756
www.mixtelematics.com

756
 757
7.3.1 FM Wireless Kit Installation Guide

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The FM Wireless Kit allows data to be downloaded from, or uploaded to the On-board Computer (FM200 Plus or FM300 series),
using the IEEE802.11b/g standard. The FM Wireless Kit connects to the S2 or S3 serial line on the FM200 Plus, or S3 serial line
on the FM300. The FM Wireless Kit is powered from the Positive Drive line.

Please Note: Security in the FM Wireless Kit is supplemented with 256-bit data encryption using WEP (Wireless Encryption
Protocol).

Declarations

We declare on our own responsibility that the product is in compliance with following norm(s) or
documents:

DIN EN 55022 (09/2003)

DIN EN 61000-6-2 (08/2002)

This product conforms to the requirements of Directive 72/245/EEC, amended by 2004/104/EC (14
October 2004)

FM Wireless Kit (X10-723-002-045) has the following components:

· FM Wireless Kit Modem

· FM Wireless Kit Serial Harness (X39-723-002-110)

· FM Wireless Kit Antenna

Hardware Installation
The FM Wireless Kit Modem has an external connector for the serial link and power supply. The FM Wireless Kit Serial Harness
connects to the external connector. A 2.4GHz antenna can be connected to the male Reverse Polarity SMA (RPSMA) connector.

Perform the following steps to install the FM Wireless Kit:

· Plug the black 6-way connector of the FM Wireless Kit Serial Harness into the FM Wireless Kit Modem, and the DB9 connector
into the S3 (or S2 on FM200 Plus) serial line.

· Connect the Red wire to the Positive Drive line (Red wire for the FM200 Plus or Red/Blue wire for the FM300).

· Connect the Brown wire to the Ground line (Brown Wire).

· Connect the female RPSMA plug of the antenna to the male RPSMA socket, via the extension cable provided.

· Place the antenna in a location that has a clear view to the Access Point antenna. Ensure the antenna is mounted as far from
grounded metal parts, as possible (to minimize interference with RF signals). Ensure that the orientation, in which the antenna
is placed, aligns with the Access Point antenna orientation, for maximum coupling.

(See KBA for further information on Setting Up Wireless Communications)

Ensure the latest Device Driver Set (modems and Wireless LAN) is loaded, as well as an updated Config.

757
www.mixtelematics.com

757
 758

The link status is indicated by the Status LEDs:

· A blinking RED LED indicates that the FM Wireless Kit is powered and scanning for a valid Access Point.

· A solid RED LED indicates that the FM Wireless Kit is associated with an Access Point.

· A solid GREEN LED indicates that the FM Wireless Kit is configured.

758
www.mixtelematics.com

758
 759
7.3.2 FM Wireless Kit Getting Started Guide

FM WIRELESS KIT
The FM Wireless Kit allows data to be downloaded from or uploaded to the On-board Computer (FM200 Plus or FM300 series),
using the IEEE802.11b/g standard.

The FM Wireless Kit connects to the S2 or S3 serial line on the FM200 Plus, or S3 serial line on the FM300. The FM Wireless Kit
is powered from the Positive Drive line.

This document describes the setup of WiFi communications between an FM200 Plus or FM300 and the Database Server.

The FM200 Plus or FM300 can use IEEE802.11b/g Wireless Communications (aka WiFi), instead of GPRS or DECT to download
the data.

Setting up the Access point

You should be able to use any Access Point hardware and antenna. For example, we use an “outdoor packaged” AP/Bridge with
PoE and an 8dBi Omni-directional antenna for our office site.

Position the Access Point hardware as close to the antenna as possible

The antenna should be mounted in an open area for optimal coupling with the vehicle units. It is possible to mount the antenna
inside the office close to the server, but then the RF signals have to travel a long way past many obstacles to reach the vehicles.
The ideal is that the access point at the site is placed inside the Parking Garage, close to all the vehicles. Signal loss may occur
and depends on the distance and type of link between the antenna and the Access Point. It is best to have the Access Point
located next to the antenna, with both of these far from the server and close to the roaming units.

Set up the Access Point with a preferred SSID (Service Set Identifier)

Access Points can share the same SSID. This enables you to build a mesh of Access Points on your site which will improve the
likelihood of successful connection from the roaming devices. Multiple Access Points with a common SSID result in the wireless
connection determining the optimum (nearest and strongest) connection point.

Set up the Access Point with your Authentication method

The Wireless Kit supports 64-bit or 128-bit WEP encryption, WPA PSK (WiFi Protected Access Pre-shared Key) and WPA Cisco
LEAP (WiFi Protected Access Lightweight Extensible Authentication Protocol) authentication. WPA provides significantly more
sophisticated data encryption and more enhanced user authentication than WEP. The latest FM Wireless Kit v2 and FM Pro
v8.37 or higher are required to utilize the WPA security modes.

Ensure that the Access Point is connected on the same sub-net mask (network settings) as the GPRS Service (Wireless Internet
Service) server, or make sure the traffic entering via the Access Point can be routed to the computer running the GPRS Service
(Wireless Internet Service) server. (Consult with your network administrator regarding this set-up.)

Setting up the FM Hardware

The FM Wireless Kit Modem has an external connector for the serial link and power supply. The FM Wireless Kit Serial Harness
connects to the external connector. A 2.4GHz antenna can be connected to the male Reverse Polarity SMA (RPSMA) connector.

Install the FM Wireless Kit

Plug the black 6-way connector of the FM Wireless Kit Serial Harness into the FM Wireless Kit Modem, and the DB9 connector
into the S3 (or S2 on FM200 Plus) serial line.

· Connect the Red wire to the Positive Drive line (Red wire for the FM200 Plus or Red/Blue wire for the FM300)

· Connect the Brown wire to the Ground line (Brown Wire).

759
www.mixtelematics.com

759
 760

· Connect the female RPSMA plug of the antenna to the male RPSMA socket, via the extension cable provided.

Antenna Placement

Place the antenna in a location that has a clear view to the Access Point antenna. Ensure the antenna is mounted as far from
grounded metal parts as possible to minimize interference with RF signals. Ensure that the antenna orientation aligns with the
Access Point antenna orientation for maximum coupling.

Place your antenna initially in an area where there is a direct-view coupling possible between the FM Wireless Kit antenna and
the Access Point antenna to ensure the best chance of establishing a link. You may move the antenna to more covert locations
once you are able to establish a connection. The location of the antenna will be determined by using an iterative approach:

· Start with a location that provides the best chance of establishing the connection. Once you have success you can try
alternative / preferred locations.

· Try the location where you prefer the antenna to be located (e.g. inside the dashboard). If you cannot establish a link from this
location, try other locations.

The rules of RF communication dictates that the signal must have an unobstructed path between the two antennas. Metal
obstructions severely attenuates the signal, and thus reduces range of connection. These obstructions include vehicle bodies, air
conditioning ducts, building structures (concrete re-enforcing), etc.

For best performance, the antenna should be mounted outside the vehicle to ensure maximum exposure to the medium in which
the RF signals travel.

Connect the FM Wireless Kit

Connect the FM Wireless Kit to one of the available serial ports (S2 or S3 for FM200 Plus; S3 for FM300); Connect the power
lines to the Positive Drive and Ground connections. Both a GSM and the FM Wireless Kit can be connected (each to a different
Serial Interface Line), and the FM OBC will determine via which channel to communicate data.

Setting up the FM Software

Open the FM software.

Add the Wireless Kit device to the serial port on which the physical connection was made (S2 or S3 for FM200 Plus; S3 for
FM300).

760
www.mixtelematics.com

760
 761

761
www.mixtelematics.com

761
 762

On the Device Properties->Connection Tab, select "Use a specific network name (Service Set Identifier)" and type in the name of
your Access Point(s).

Note that all your Access Points can share the same name, e.g. FMWLAN. Avoid using names such as "any" or "internet", unless
you want the units to connect to these type of resources. Do make sure you type in the name exactly as you have defined it in the
Access Point - See Access Point Step 3 above.

Type in the IP address of your database server. This is the IP address of the computer which will accept the data you send via
the Access Point. It is the address of the computer running the GPRS Service component, which collects the data and delivers it
to the application that posts the data to the database.

Select the enabled ports on each device. The default values are usually acceptable. Check with the administrator of the GPRS
Service computer for the proper server IP port.

762
www.mixtelematics.com

762
 763

On the Device Properties, Network Tab you can specify how IP addresses are assigned. You can use specific settings or use the
DHCP facility of your network to automatically assign IP addresses for the FM OBC. Confirm these settings with your network
administrator.

763
www.mixtelematics.com

763
 764

On the Device Properties, Encryption Tab you can select the Authentication methods. You can select the specific Mode, as
defined in the Access Point, but Automatic should work. The FM Wireless Kit supports 64-bit and 128-bit WEP key encryption.
You must specify the key values.

The WEP key is the 5 or 13 ASCII digit password for WEP security.

764
www.mixtelematics.com

764
 765

765
www.mixtelematics.com

765
 766

Device Properties->Packet Comms and Device Properties->Database specify the type of traffic (AVL), the amount of traffic and
what you do with the data traffic. These are required to keep the link alive, or the IP address would be re-assigned to another
network node. Also specify if data should be transferred at the start or end of trips, or not at all (in which case it can be extracted
at a fixed scheduled time or manually). Refer to the FM Professional documentation for more detail.

766
www.mixtelematics.com

766
 767

767
www.mixtelematics.com

767
 768

On the Device Properties->Transports Tab, select Wireless Internet (GPRS, WiFi) as the default Remote Data Transfer
Transport. The FM Unit determines which link (GPRS or WLAN) to use, preferring WLAN and using GPRS as backup option. You
can specify “WiFi Only” if you prefer.

768
www.mixtelematics.com

768
 769

On the Device Properties->Power Tab, check the settings for power management and Battery voltage. If the device detects
battery input voltage below the threshold, it can disable the device if powered via Positive Drive. Also note that other devices may
be powered from Positive drive, and these too could disable Positive Drive and the Wireless Kit with it. Also double-check the
Automatic Shutdown feature. If enabled, the Wireless Kit may be powered down after an amount of time.

769
www.mixtelematics.com

769
 770

Once this has been done, click OK, Apply and your FM Wireless Kit is now added.

770
www.mixtelematics.com

770
 771

Upload the new vehicle configuration via plug to the vehicle.

Device Drivers
Open the Dealer Utility.

If you have created your FM Wireless Kit on S2 load the following device drivers:

771
www.mixtelematics.com

771
 772

If you have created your FM Wireless Kit on S3, use the following Device Drivers:

Upload the new Device drivers to the vehicle by plug.

Troubleshooting
Once you have installed all equipment, check the following on the WiFi kit and software:

772
www.mixtelematics.com

772
 773

Check the LED status on the Wireless Kit (if it is accessible):

· The Red LED blinks if it is scanning for an Access Point, and stays lit if it is connected to (associated with) an Access Point.

· The green LED is lit when an IP address is assigned to the Wireless Kit.

Check the log files on the GPRS Service (Wireless Internet Service) computer:

The log for each unit will indicate when a connection was made. You can verify the assigned IP address and unit information.

If the above conditions do not appear, here is a list of troubleshooting options that you can use:

· The Wireless Kit antenna is located in a spot where there is no signal, e.g. inside the vehicle cabin or boot.

· The Wireless Kit is not powered up, either due to hardware failure (loose connection to Positive Drive), or because the software
is powering it down (Power Management options for the devices).

· The Wireless Kit has a communication failure, either due to hardware failure (the serial cable is detached) or the Wireless Kit is
assigned to the wrong port. This could also be due to a failure of the antenna connection.

· The Wireless Kit cannot log on to the Access Point. This could be due to authentication failure (wrong method and/or
password), wrong/mismatched SSID, or wrong parameters on the Access Point settings.

· The Server IP and/or port settings are wrong. Check the settings as defined in the FM Professional device configuration dialog.
Check the settings with the LAN administrator.

· The server is not connected to the network. Check with the LAN administrator.

· The GPRS Service (Wireless Internet Service) is not running. Check that the service is installed (part of the communications
Package) and enabled. Refer to the GPRS Service (Wireless Internet Service) documentation for details on setting up and
operating the GPRS Service (Wireless Internet Service) component.

· The Wireless Kit is out of range of the Access Point. Under ideal conditions, a link can be established at distances up to 500m.
This requires a clear line-of-sight path. Any obstructions severely shorten this distance. A safer margin would be 200m. If
Wireless Kit unit does not establish reliable connections, it is advisable to install more Access Points, evenly spaced on the
site. The Wireless Kit firmware will connect to the Access Point with the best signal strength. This enables a connection to
complete data transfer, i.e. maintain the connection, even if the Wireless Kit unit is mobile between Access Points.

When selecting the serial port (S2 or S3) to connect the WiFi kit on, you will need to load the specific device driver for this port
configuration. These are two of the selectable device drivers from the Dealer Utility:

· “Device Drivers for modems and Wireless LAN” – These will be used for the WiFi on S3

· “Device Drivers for Wireless LAN and SDK” – These will be used for the WiFi on S2

How to enable WiFi diagnostics information on the FM Terminal (FM 8.37 and older)

1. Download the WiFi Diagnostic script & ddm from www.mixtelematics.com (KBA#376)

2. Set up your FM Hardware with a FM Terminal & WiFi kit .

3. Paste the CidevBig.fmt file into your FMTerminal folder (under C:\Program Files\Common Files\Fleet Manager\).

4. In the FM Software, under Devices, go to -> Terminal -> Script --Select the ‘CidevBig.fmt’ script from the dropdown list.

5. Load the config onto the unit by means of a vehicle plug.

6. In the dealer utility:

773
www.mixtelematics.com

773
 774

· Format a Device Driver plug

· Go to 'Load Device Drivers' -> 'Browse' to the location where your SCRIPT.DDM file is saved, and Load it onto the plug

7. Load the drivers onto the unit by inserting the driver plug into the vehicle plug socket.

8. The last step is to create a WiFi diagnostics plug with the dealer utility and to insert it into the vehicle plug socket.

9. On the Terminal, under menu option 6 ("Diagnostics"), the following fields will be displayed:
Diag Plug Type
Signal Strength (Measured in dBm. The higher the number, the stronger the signal.)
Port Status -Current MAC Port Connection Status, where...
1 = disabled
2 = searching for initial connection
3 = Connected to IBSS
4 = Connected to ESS
5 = out of range (in ESS)
8 = started host AP
Link Status -Wireless Local Network Status, where...
0 = Association not yet completed
1 = Connected
2 = Disconnected
3 = AP change
4 = AP out of range
5 = AP in range
6 = Association failed)
DHCP Status
0 = DHCP is disabled
1 = DHCP is in the process of leasing an address
2 = DHCP has leased an address

774
www.mixtelematics.com

774
 775

7.4 FM DECT
© 2008 MiX Telematics | Updated 2008/05/07

Overview
This document incorporates the following three Installation Manuals:

· DECT Vehicle Unit

· DECT Base Station

· DECT Base Station Alternative

DECT Vehicle Unit Installation

Product Code

X10-732-002-010

Description

The DECT solution is used for the remote download of Fleet Manager data from the FM200 Plus or FM200 Locator (FM200 Plus
+ GPS) on-board computers. The system consists of the DECT Base Station that is installed in the vehicle yard, and DECT
vehicle units that are installed in every vehicle. The download occurs automatically when the vehicle is in open range of 300
meters from a DECT Base Station, with no additional costs involved.

The DECT Vehicle Unit System consists of a DECT vehicle transceiver unit, a DECT antenna and a TTL to RS232 converter. The
vehicle transceiver unit is connected to the FM200 / FM200 Plus unit with the TTL to RS232 converter.

Contents of DECT Vehicle Kit

DECT Vehicle Transceiver Unit (With fused cable)

DECT Antenna

TTL to RS232 converter (Connects DECT vehicle unit to FM200/

FM200 Plus)

775
www.mixtelematics.com

775
 776

Additional Requirements

If a standard DECT installation is performed, no other items are required other than the DECT Base Station (installed within the
vehicle yard) and the FM200 or FM200 Plus units (installed in vehicle).

If a connection to an FM Terminal is needed, either an FM Splitter harness (FM200/FM200 Plus) or the FM200 Plus harness
(FM200 Plus) is used to connect the FM Terminal to the DECT vehicle unit and on-board computer.

Installation
Standard Installation

Step 1

Connect the TTL converter harness between the DECT vehicle unit and the FM200 or FM200 Plus..

Step 2

Connect the DECT antenna to the DECT vehicle unit.

Step 3

Connect the power control to the DECT modem.

Step 4

Test the vehicle Unit Installation:

1. Format a DECT diagnostic plug using the FM Dealer utility. (e.g. a Driver Plug)

2. Insert the Diagnostic plug in the socket.

3. When the plug is inserted in the unit it will beep once and the LED (red light) will stop flashing.

4. When a DECT server is in range, a single continuous beep will sound (about a 60 second cycle, sometimes a bit longer).

5. When a download is initiated from the DECT server computer, the unit will give 3 beeps.

A diagnostic plug will take the unit out of sleep mode and will power the relay if relay power is used. It is not necessary to turn the
vehicle ignition on and start a trip (this is required on older FM200 firmware versions. If all else fail, start a trip).

Standard Installation Connection Diagram

776
www.mixtelematics.com

776
 777

Enhanced Installations: Power Control

To prevent the DECT unit from draining the vehicle battery, the power to the DECT transceiver can be controlled. In the standard
installation the DECT transceiver is directly connected to the vehicle battery. This can be changed to be switched by a relay
circuit controlled by the FM200 or FM200 Plus unit. On the FM200 Plus unit the relay is not required if the “positive drive” power
line is used.

Uncontrolled Circuit

Relay Control Circuit

777
www.mixtelematics.com

777
 778

Positive Drive Control Circuit

Enhanced Installations: FM Terminal

To add an FM Terminal to the DECT vehicle unit, an FM Splitter cable is required for operation with a FM200 or FM200 Plus unit.
The FM200 Plus harness can also be used with a FM200 Plus unit.

FM200 / FM 200 Plus Installation with FM Splitter

Step 1

Connect the FM200 / FM200 Plus to the DECT Vehicle Unit with the FM Splitter.

Step 2

Connect the DECT Antenna to the DECT Vehicle Unit.

778
www.mixtelematics.com

778
 779

Step 3

Connect the FM Terminal to the DECT Vehicle Unit.

Step 4

Connect the Power to the DECT Vehicle Unit .

FM200 Plus Installation with FM200 Plus harness

Step 1

Connect the FM200 Plus to the DECT Vehicle Unit with the FM200 Plus harness.

Step 2

Connect the DECT Antenna to the DECT Vehicle Unit.

Step 3

Connect the FM Terminal to the FM 200 Plus with the FM200 Plus harness.

Step 4

Connect the Power to the DECT Vehicle Unit .

FM Terminal Connection Diagram

FM 200 / FM200 Plus Connection Diagram with FM Splitter

779
www.mixtelematics.com

779
 780

DECT Base Station Installation Manual

Product Code

X10-732-002-011

Description

The DECT solution is used for the remote download of Fleet Manager data from the FM200 or FM200 Plus on-board computers.
The system consists of the DECT Base Station that is installed in the vehicle yard, and DECT vehicle units that are installed in
every vehicle. The download occurs automatically when the vehicle is in open range of 300 meters from a DECT Base Station,
with no additional costs involved.

The DECT Base Station System consists of four parts – The Remote Base Station unit, RS485 to RS232 converter, DECT power
supply, and the DECT server computer. The remote box is water-proof and is designed to be mounted in the vehicle yard where it
can cover a larger range. Typical line of sight range of the DECT short-range data extraction units is 300m. Any obstacles in the
line of sight will reduce the reliable RF connection range of the DECT.

780
www.mixtelematics.com

780
 781

Contents of DECT Kit

Waterproof DECT Base Station

Universal Power supply
Remote/Yard Box

RS232 to RS485 Connector DB9 Female Connector

Additional Requirements

In addition to the above contents, you will also need a cable connecting the DECT server computer and the DECT Remote Base
Station unit. It can either be a shielded 3 pair cable or a 4 pair shielded cable. The length of the cable depends on the individual
installation. The length of the cable connecting the remote box to the PC can exceed the length of normal RS232 cables (5
metres) as it is running on a RS485 protocol (up to 1000 meters). Care has to be taken when the cable length nears the
maximum length of RS422 cable networks as there are factors that will influence the installation. The communication speed
between the DECT server computer and DECT Remote Base Station unit is 19200bps.

When installing the DECT Base Station, the following skills are required:

· Soldering of the DB9 Connector

· Mounting of the Remote Box

· Installation and cabling of the DECT system

Standard Installation
Step 1 Remove the lid from the DECT Base Station Remote Box

To open the housing, remove the 4 screws in the four corners on the front of the DECT Base Station unit.

Step 2 Remove the DECT Controller Board

The main DECT Controller Board is mounted with four plastic screws. Remove the main Controller Board from the DECT Base
Station unit. Take care, as the Controller Board is fixed with two connectors.

781
www.mixtelematics.com

781
 782

Step 3 Connect the Cable

Mount the cable using the PG-connector and fix the cable using the appropriate cable holder. Fix the cables using the connector
block based on the wiring diagram below.

Step 4 Solder the wires to the DB9 connector

Solder the wires securely inside the DB9 connector (See connection diagram below). Cover the DB9 connector with the provided
housing. Connect the DB9 connector to the RS485 to RS232 converter.

782
www.mixtelematics.com

782
 783

Connector wires in DB9 Female diagram (Office Side)

9 +12V

8 +12V

7 GND

6 GND

5 GND

4 TX (Y)

3 TX (Z)

2 RX (B)

1 RX (A)

Step 5 Replace the DECT controller board and close housing

Once the cable has been connected, the main DECT Base Station Controller Board must be mounted again. Ensure that the
Controller Board fits into the connectors. Now fix the main PCB with the plastic screws and mount the housing.

Step 6 Mount the DECT Base Station Remote Box

The best results for coverage of the DECT Base Station can be achieved if no walls etc. are located between the DECT-equipped
vehicles and DECT Base Station. In certain applications it could be necessary to improve the directional coverage of the DECT
Base station. To achieve this, the FM DECT Base Station must be mounted on a metal sheet as shown in the drawing. The size
of the metal sheet should be approx. 200 x 300mm.

Step 7 Connect the Remote Box to the Computer

Use the Connector Diagram to connect the DECT Base Station unit to the Computer.

Step 8 Switch on the computer

Boot up the computer and run Microsoft Windows.

783
www.mixtelematics.com

783
 784

Step 9 Install the DECT Software

Install the DECT software from the Fleet Manager CD provided, and enter the Upgrade+ registration code. Ensure that Fleet
Manager Software is installed on the computer.

Step 10 Test the DECT Base Station unit with the DECT software

Each vehicle should have the DECT vehicle unit installed for the DECT unit to be tested. Please see the “DECT Vehicle Unit
Installation Guide” for further details.

Connection Diagram

Warnings

Please take note of the following warnings before you install DECT devices.

· DECT devices could have an impact on medical devices.

· The FM DECT Base Station could cause a buzzing sound in hearing aids.

· The FM DECT Base Station must not be operated in areas of danger of explosion.

DECT Base Station Alternative Installation Manual

784
www.mixtelematics.com

784
 785

Product Code

X10-732-002-010

Description

The DECT solution is used for the remote download of Fleet Manager data from the FM200 Plus or FM200 Locator on-board
computers. The system consists of the DECT Base Station that is installed in the vehicle yard, and DECT vehicle units that are
installed in every vehicle. The download occurs automatically when the vehicle is in open range of 300 meters from a DECT Base
Station, with no additional costs involved.

The DECT Vehicle Unit System consists of a DECT vehicle transceiver unit, a DECT antenna and a TTL to RS232 converter. The
vehicle transceiver unit is connected to the FM200 / FM 200 Plus unit with the TTL to RS232 converter.

Contents

DECT Vehicle Kit

Additional Requirements

For the installation of the DECT Base Station Alternative solution, a DB9F to DB9M Modem Extender Cable and 1A 12V Power
Supply are required. Both these items can be acquired from a local computer hardware shop.

Installation
Step 1

Connect the DECT antenna to the DECT Vehicle Unit.

Step 2

Connect the A1 12V Power Supply to the DECT Vehicle Unit.

Step 3

Connect the DB9M connector of the Modem Extender Cable to the DB9F connector of the DECT Vehicle Unit.

Step 4

Connect the other end of the Modem Extender Cable to the serial port of the computer. Ensure that the length of the cable does
not exceed 5 meters.

Step 5

Install the DECT software from the Fleet Manager CD provided. Ensure that Fleet Manager Software is already installed on the
computer.

Step 6

Test the DECT Base Station Alternative unit with the DECT software. Each vehicle should have the DECT vehicle unit installed
for the DECT unit to be tested. Please see the “DECT Vehicle Unit Installation Guide” for further details.

Connection Diagram

785
www.mixtelematics.com

785
 786

Restrictions

Since the original purpose of the DECT vehicle unit is to not to be used as a base station, there are certain limitations. Firstly the
unit is not waterproof and cannot be mounted outdoors. Secondly, due to the RS232 limitation on the cable, the distance between
the computer and the Base Station Alternative unit cannot exceed 5 meters. Thirdly, if the antenna is mounted indoors, the DECT
range is reduced (normally 300 meters).

786
www.mixtelematics.com

786
 787

7.5 FM Impact Sensor

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The FM Impact Sensor is designed and developed to accurately detect and record any impacts to equipment. The severity of the
impact is transmitted to the FM200 Plus on-board computer. Depending on requirements, the on-board computer can either log
the impact, or a notification can be sent to the Fleet Manager, informing him of the accident.

Features

Robust and Water Resistant The FM Impact Sensor is for indoor and outdoor use.

Impact Recording Monitors impacts from all lateral directions simultaneously.

Versatile Uses The FM Impact Sensor can be used to monitor different parts of a vehicle e.g. fork of a
forklift or the axis to monitor harsh loading.

Vertical or Horizontal Mounting The unit can be mounted in either vertical or horizontal positions, to monitor different types
of impact.

Notifications Notifications can be set up to send a text-message the office when an impact with a high
value occurs *requires GSM/GPRS.

Technical Information

Supply Voltage 9V - 100V DC Storage Temperature -40ºC - +80ºC

Current Supply Less than 15mA Operating Temperature -40ºC - +80ºC

Maximum Impact Typically 15 Gs Size 65 mm x 42 mm

Data Capture
The FM Impact Sensor outputs an analogue signal which is derived from acceleration.

The following data is recorded with every impact:

· The date and time of the impact

· Vehicle on which the impact occurred

· The driver of the vehicle

· The G-force value of the impact

· The direction of the impact (e.g. front, right, left-rear)

787
www.mixtelematics.com

787
 788

Mounting
The FM Impact Sensor is an external device and is connected to the FM200 Plus via a cable. This makes it suitable and practical
to mount in sensitive areas that are not practical for the FM200 Plus on-board computer. The FM Impact Sensor can be mounted
either in a vertical or horizontal orientation, to record different types of impacts.

Software
The Materials Handling Extension is used in conjunction with the Fleet Manager Professional 9 software to allow the Fleet
Manager to generate reports reflecting the daily use of equipment / vehicles. The Materials Handling Extension includes the
Utilisation, Event, Collision and Timeline Report and Graphs.

Please see the Fleet Manager Materials Handling Extension documentation for more information.

Product Code
The FM Impact Sensor product code is X10-723-002-017.

788
www.mixtelematics.com

788
 789
7.5.1 FM Impact Sensor Installation Manual

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The FM Impact Sensor uses an accelerometer to accurately detect impacts from any lateral direction, and transmit the severity in
an analogue format to the FM200 Plus on-board computer. These values will be detected by two FM200 Plus analogue inputs,
and depending on the requirements, the FM200 Plus system can act appropriately on these events (e.g. log the value and send a
SMS).

In addition to monitoring collisions to the vehicle, the system can be attached to many mechanical vehicle accessories and used
to detect misuse and accidental damage other than that directly to the vehicle (e.g. the arm of a crane mounted on some
vehicles; the fork attached to a forklift or reach-truck; harsh loading of trucks etc). The FM Impact Sensor can also be mounted on
its side, and can be used to monitor driving surfaces, and thereby be configured to place further restrictions on the driver during
poor road conditions. Many other applications are possible.

Declarations
Type Approval

This product conforms to the requirements of Directive 71/245/EEC, as last amended by Directive 95/54/
EC.

023376

Installation

FM Impact Sensor Components

1. Red Wire with terminal - 8V - 100V positive supply for FM Impact Sensor - can be connected to FM200 Plus Positive Drive
supply line (pin 15 of comms connector).

2. Green, Black, Cable Screen drain wire with heat-shrink and terminal - can be connected to FM200 Plus Positive Drive Ground
line (pin 4 of comms connector).

3. Yellow - FM Impact Sensor Y axis output voltage can be connected to any FM200 Plus analogue line.

789
www.mixtelematics.com

789
 790

4. White - FM Impact Sensor X axis output voltage can be connected to any FM200 Plus analogue line.

5. Blue - FM impact sensor signal true line can be connected to any FM200 Plus analogue line. Fitting this line is highly
recommended to eliminate potentially false readings caused by supply voltage dips/switching, electromagnetic interference,
etc.

6. FM200 Plus - can be mounted in any suitable location.

7. FM Impact Sensor - should be mounted on a flat steady horizontal surface, using supplied bolts, or other suitable secure
means, away from high voltage sources, sources of mechanical damage, etc. The cable should face away from the direction of
travel.

8. 3m insulated, screened FM impact sensor cable - this should be routed along a safe path away from high voltage ignition lines,
sources of mechanical damage, etc. Cable should be safely secured.

Important

i All analogue lines used by the impact sensor should be Soldered and insulated as close to FM200 Plus as practically
possible (cut analogue wire down to approximately 3cm). Front and left impacts will generate positive going voltages of the
respective lines.

ii The impact sensor should be securely mounted using bolts in order to measure accurately.

iii The impact sensor should be powered up from the FM200 Plus Positive Drive line.

iv The Ferrite Choke (9) needs to be on the cable as close to the FM200 Plus as possible to help prevent invalid signals
being measured.

v If the FM200 Plus is not grounded to the vehicle chassis, then electrically insulate the Impact Sensor from the vehicle
chassis when mounting it.

Installation should be performed by a qualified FM200 Plus installer with soldering or crimping skills. Wires that are joined should
be insulated and protected using heat shrink, tape, or other acceptable means. The components section above specifies specific
details for each component.

Software Setup

· Device drivers should be loaded from the FM Dealer Ver 2.10.0.0 or later (using a 256K device driver plug, a vehicle plug set
up for that vehicle, GSM or RF device driver upload facility).

· The front-end used to support the FM Impact Sensor should be installed from the FM2002 Professional SR1 CD or later. The
appropriate axis for each input used should be selected as a device for each input line.

· The input calibration for each input should be preconfigured to 2.51V=0G, 2.66V=1G.

· The "signal true" line should be calibrated as 2.51V=0V; 3.51V=1V. Its noise threshold should be set to 0.1V.

· As is normally done, appropriate events should be created according to the G-Force being exceeded. Data logging and active
events can be performed according to these results.

· Event configuration should be transferred to the vehicle (using a vehicle plug, GSM or RF configuration upload facility).

Testing the Installation

Once the wires have been connected and before the sensor has been securely mounted, the installer should set up impact
events on the front-end software, load the configuration to the FM200 Plus, and test the impact functionality by lightly tapping the
sensor on each side with a soft object. The system should correctly register the impacts. A left impact and a forward impact will

790
www.mixtelematics.com

790
 791

produce positive G-Force readings on the respective input lines.

Completing the Installation

The FM Impact Sensor should be secured to a stable horizontal surface, typically using the bolts and washers supplied with the
product. The unit should be mounted so that the cable is at 180º to the direction of travel. The unit should be mounted with care
and severe mechanical shock (e.g. hitting on or near the device with a hammer) should be avoided, as this may damage the unit.

Specifications
* For proper operation and to avoid damage, do not expose the device to conditions in excess to the following:

*Maximum mechanical shock: 200 Gs

*Supply Voltage: 9 - 100V

*Temperature range: -40º - 80º

*Maximum G-Force system can measure: 8 Gs to 15 Gs; (this figure may vary for different sensors)

Current draw of the Impact Sensor on vehicle <15mA

Safe detection resolution 1G

(FM200 Plus (FM200 Plus) restriction)

Sensitivity (X and Y axis) 0.15V = 1G

Annexure A
Summary of using the Amp Connector and Terminals - FM200 Plus Comms Connector:

The Amp Terminal is an ideal place to obtain a safe power supply for the FM Impact sensor. A brief summary of the use of this
terminal follows. Note that if the comms connector is already being used, existing wires using the specified terminal numbers
should be tapped into. Note also that the connector pin numbers are marked at the rear of the connector.

A. Red Positive impact sensor power line (to be inserted into Pin 15 of 16-way Amp Connector) - insert by sliding the terminal into
the back of the connector with the lock mechanism B lifted;

B. Connector Terminal Lock Mechanism - this must be lifted as shown by black arrows in order to insert or remove power

791
www.mixtelematics.com

791
 792

terminals;

C.Pin 15 - for inserting Red power wire into (Positive drive from FM200 Plus - used to power up FM Impact Sensor);

D.Green/Black/Drain (heat-shrinked) ground wires for FM Impact Sensor (to be inserted into pin 4 of 16-way Amp Connector) -
see A for insertion instructions;

E. To remove an incorrectly inserted terminal, one needs to insert an appropriate thin sharp metal rod at the point indicated and
lift the small plastic catch located inside the hole, while pulling the terminal out from the other side;

F. Pin 4 for inserting Green/Black/Drain (heat-shrinked) ground lines into (FM200 Plus ground wire) - insert by sliding the terminal
into the back of the connector with the lock mechanism B lifted.

Summary of the Analogue Line Wire Colours - FM200 Plus Main Harness:

Pin 5 Purple / White Analogue line 1

Pin 6 Red / White Analogue line 2

Pin 3 Green / White Analogue line 3

Pin 4 Yellow / White Analogue line 4

Pin 17 Black / White Analogue line 5

Pin 16 Blue / White Analogue line 6

Pin 15 Brown / White Analogue line 7

Pin 14 White Analogue line 8 / F4 (can be used if supported by current version of front-end software)

792
www.mixtelematics.com

792
 793
7.5.2 FM Impact Sensor User Manual

© 2008 MiX Telematics | Updated 2008/05/07

Installation
For more information on the installation and specifications of the FM Impact Sensor, please see the FM Impact Sensor
Installation Manual

Software Setup

Once the front-end software has been installed, and a vehicle containing an FM Impact Sensor has been added, the inputs used
by the FM Impact Sensor should be connected in a similar way to what is seen below, but using the analogue inputs that
correspond to those installed in the vehicle. Remember that Interval data for peak impact readings is available for inputs 1 to 4,
so if one of these lines was used for either the X or the Y axis impacts, or both, then per-second peak values will be available for
viewing driving trends. This can also help when setting the impact thresholds for a particular environment.

Calibration (for both the X axis and Y axis) is set so that 2.51V is equivalent to 0G, 3.51V is equivalent to 6.6667G, and 1.51V is
equivalent to 6.6667G. Profile storage will not normally be used, but could sometimes be useful for recording driving styles (e.g.
harsh cornering/acceleration/braking).

793
www.mixtelematics.com

793
 794

The integrity line calibration is set at a 1 to 1 relationship with volts, with an input level of 2.51V equivalent to an integrity level of
zero. Deviations from this in either the positive or the negative direction will cause the integrity line to trigger and to reject
potentially incorrect values caused by supply voltage dips and electrical interference. The sensitivity setting will dictate how much
of this noise will be rejected. One should choose this setting according to the level of impacts one is interested in. If one is
reacting on a high G-force impact, a "Less sensitive" setting should be chosen, meaning that the integrity line will reject less
noise.

If one finds that impacts that cannot be explained are being recorded, you should increase the sensitivity of this line (use a more
sensitive setting to reject these values, assuming they were caused by noise).

Not connecting the integrity line at all is possible, but is not recommended. Be aware that in doing this, information recorded
could at times be false. You can manually reject these incorrect values by looking at the context in which they were generated (e.
g. the voltage dip experienced when the vehicle was started).

794
www.mixtelematics.com

794
 795

Events for impacts on both the X and Y axis should be enabled. These monitor the resultant peak acceleration calculated by
combining the X and Y impact maximums over the last second into a single vector value and then reacting on this. The two
events are separated to allow recording of the separate peak components. This allows the resultant direction of the impacts to be
best resolved.

The minimum value of an impact can be set up by editing the event. One should set the event to a value that suits the
environment in which the equipment is operating. Lower values will record more events during harsh cornering, braking,
accelerating, or driving over bad surfaces. Higher values will record less. Be aware that an impact that reduces speed by 3 Km
per hour over a period of 100 milliseconds will cause an impact of at least 1G. The shock of hitting a rigid object may at times
cause higher impacts, even though the resultant speed is not reduced by such an extent. The shock of an object colliding with the
vehicle or by a door being slammed may cause a low G force impact to be recorded if the impact threshold is set to a low value.
Use your discretion in choosing appropriate values. The default value will suite many commonly found environments.

795
www.mixtelematics.com

795
 796

Data Storage
Data will be stored by the FM200 Plus Unit and transferred to the database during normal download activity or by Active Events, if
these were set up.

When an impact is recorded and transferred to the database, the results can be viewed in the Activity Timeline in a standard
manner.

796
www.mixtelematics.com

796
 797

If inputs 1 to 4 were used for the X and Y resultant forces, you can view the second by second values of g-force in the Interval
graph.

797
www.mixtelematics.com

797
 798

Software Reports
The Materials Handling Extension is used in conjunction with the Fleet Manager Professional 9 software to allow the Fleet
Manager to generate reports reflecting the daily use of equipment / vehicles. The Materials Handling Extension includes
Utilisation, Event, Collision and Timeline Report and Graphs

Please see the Fleet Manager Materials Handling Extension documentation for more information.

Impact Sensor Data Integrity and Precautions

Much work has been done to optimise the data integrity of the FM Impact Sensor and the data recorded by the FM200 Plus Unit.
To further improve the integrity of the data, there is an obligation on the installer to mount the unit properly, route the cable
correctly (and safely), and to set up the events correctly with carefully considered values.

It is important that the installer and the user take basic precautions with the unit. It is primarily intended for use in materials
handling and industrial environments, and is not intended as a device to be relied on to prevent injury or death cased by impacts.
It will not provide data at an extremely high resolution for detailed analysis of accidents, as is the case with FM UDS. It is to be
used as an instrument that, when installed and set up correctly, will help notify authorities of an impact.

The FM Impact Sensor is an external device (connected to the FM200 Plus on-board computer via a cable). It is external to the
FM200 Plus Unit to make it suitable and practical for mounting in sensitive areas that are not practical for the FM200 Plus
mounting. This feature means that should the cable connecting the Impact Sensor to the FM200 Plus on-board computer break
due to an impact (assuming the integrity line connected correctly), the FM200 Plus Unit will not record the impact (the broken
integrity line will cause the data to be rejected. - the unit will not be able to establish whether the signal was caused by a collision
or by a cut cable, and will therefore not report a potentially invalid impact). By default, the FM200 Plus Unit will not record an
event if the Impact Sensor cable was physically cut (assuming the integrity line is present). The FM Impact Sensor will not
function correctly if the vehicle battery voltage is too low (resulting in it being powered from less than the specified volts). For
detection of these types of conditions (cable cut etc.), one needs to create separate events to monitor the voltages of the lines in
question with respect to the vehicle's status.

The FM200 Plus Unit will not record an impact if during the impact, the power to the system is lost (e.g. the force of the impact
dislodges or damages the vehicle battery).

The direction of an impact will sometimes not be resolved accurately if multiple collisions occur during the second preceding the
logging of the impact (i.e. hitting two or more objects in short succession - this can sometimes be caused by the vehicle
rebounding off one object and hitting another). Impacts that are vertically (or nearly vertically) orientated to the vehicle may
sometimes not be resolved accurately in terms of direction of impact (this can be caused by the wheel of the vehicle hitting an
obstacle). Resonance within the vehicle caused by an impact can in some cases cause the direction of the impact not to be
resolved accurately. Vertically orientated impacts will not be recorded with an accurate value, as the device was designed to
measure horizontally orientated impacts.

The impact sensor outputs an analogue signal which is derived from acceleration. As with all analogue signals, the value
received by the FM200 Plus Unit has a small noise error component caused by environmental influences and by small resolution
errors caused by the A to D converter resolving the values. This noise can be picked up and logged by the FM200 Plus Unit. It is
important to be aware that by setting up the FM200 Plus Unit to record impact of very small values, false impacts of low G-Force
values may be recorded during normal vehicle activity. Typical noise values can be seen in interval data recorded while the
vehicle is stationary (see "B" below). Mechanical shocks caused by general vehicle activity (e.g. a door slamming) can be a
source of small G-force values (see "A" below). This shock may also vary depending on source and orientation of the mechanical
activity. This activity can cause a resonant shock within the vehicle and the resultant shock at the actual point of the impact
sensor can be inflated (this resonant shock may vary by mounting the impact sensor in different places).

798
www.mixtelematics.com

798
 799

7.6 FM Keypad
© 2008 MiX Telematics | Updated 2008/06/12

Overview
The Fleet Manager (FM) Keypad is a data input and display unit, designed to work in conjunction with the FM200 Plus on-board
computer. Using the FM Keypad, drivers can select Driving Reasons for tax purposes and use the selection of pre-defined phone
numbers for making phone calls from the vehicle. The driving reasons are logged by the on-board computer, along with all other
trip information, and downloaded to the front-end software for reporting. The unit will also display the GSM connection visually.

Features

Configurable With Fleet Manager Professional 9 software, tax logging and voice functionality can be enabled
or disabled. The software is also used to program the pre-defined telephone numbers into the
keypad.

Quality product Solid construction E1 and CE approved, attractive design and an easy installation concept
make the FM Keypad suitable for any vehicle and any type of fleet.

Network Status Display The GSM connection is indicated with the network status LED.

Recording of Driving Reasons The trip’s driving reasons are logged by the FM200 Plus, along with all other trip information,
and downloaded to the front-end software for reporting.

Phone functionality When combined with a GSM modem, phone and voice calls can be made to 4 pre-defined
numbers. The vehicle can also receive voice calls.

Automated Backlight The FM Keypad keys are backlit, and will stay on for the duration of the trip. At the end of the
trip, the backlight will remain on for an additional 5 minutes. At the start of a new trip, or if the
user presses any keys, the backlight will turn back on again.

Flexible The FM Keypad’s design is very flexible and new functionality will be implemented in future
products.

Technical Information

Operating Temperature -40ºC … +85ºC

Storage Temperature -40ºC … +85ºC

Current 6ma

Backlight LED

Data Capture
Drivers can capture data via the FM Keypad’s built-in keypad with two different key presses. Quick button presses are used for
driving reason selection, and delayed button presses are used for making voice calls.

Driving Reasons

799
www.mixtelematics.com

799
 800

At the start of a trip or a sub-trip, the driver is prompted to enter one of the following driving reasons: Business, Commute, Private
or Other. All details entered into the FM Keypad are stored with the trip information on the FM200 Plus unit. The data is then
downloaded to the front-end software for analysing and reporting.

Voice
(Available if a GSM modem is connected to your vehicle. It is also required that a hands free kit is installed.)

The driver can phone any one of 4 predefined phone numbers and make a voice call. The vehicle can also receive voice calls.
The Fleet Manager Professional 9 allows the user to enter up to four voice phone numbers which the driver may phone from the
vehicle. It is not necessary for the user to enter all four numbers.

Software
Fleet Manager Professional 9 provides the serious fleet operator with extensive fleet management tools to manage and report on
his fleet. The software enables you to manage vehicle, driver and passenger information, define and manage events to be
monitored, analyse fleet data and do extensive management reporting. In addition to the core software, Fleet Manager
Professional 9 also offers a set of extensions that allow additional monitoring and reporting on the fleet.

800
www.mixtelematics.com

800
 801
7.6.1 FM Keypad Installation Manual

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The FM Keypad displays Taxlog driving reasons and GSM connection status visually, and provides for the selection of Driving
Reasons for Tax logging purposes, and the selection of Phone Numbers for making voice phone calls from the vehicle. The
driving reasons are logged by the FM200, along with all other trip information, and downloaded to the front-end software for
reporting.

Declaration
Type Approval

This product conforms to the requirements of Directive 71/245/EEC, as last amended by Directive 95/54/EC.

022944

FM Keypad Components
Faceplate Layout

Each function button has a corresponding function LED which turns on when a driving reason is selected. The driving reasons
are: Business, Commute, Private and Other. The function buttons are also used to select any one of four phone numbers with
which the FM200 will make a call. The network status LED shines green if the vehicle has GSM reception, and red if it does not.

Hardware Installation
The FM Keypad harness has two connectors. One of the connectors is attached to the code plug connector, and the other
connector is connected to the code plug socket: The connection of the code-plug socket with the harness is broken (shown by
dotted ellipse). The code-plug socket is connected to the male FM Keypad connector. The female FM Keypad connector is then
connected to the male harness connector.

The FM Keypad should be securely mounted using the mounting plate, ensuring that it does not obstruct or impede any vehicle
functions such as steering, braking, accelerating, changing gears, engaging indicators and/or windscreen wipers etc. It should be
in clear view of the driver, but not obstructing any vehicle information such as speedometer, rev-counter, warning lights etc.

801
www.mixtelematics.com

801
 802

NB: The FM Keypad must be mounted out of direct sunlight.

Using the FM Keypad

Button Press Overview

The FM Keypad has two types of button presses, namely quick and delayed. Quick button presses are used for driving reason
selection, and delayed button presses are used for making voice calls.

Quick button press

The driver holds down the button until a quick beep is issued by the on-board computer, and then releases immediately.

Delayed button press

The driver holds down the button until a quick beep is issued by the on-board computer, keeps holding it until a quick double
beep is issued by the on-board computer, and then releases the button.

Taxlog Functionality
Setting or Changing a Driving Reason

The driving reason is changed by making two quick button presses on the same button within three seconds.

Driver Prompting

Two options are available and can be set from the front-end, namely previous driving reason or specific driving reason.

· Previous driving reason sets the driving reason to that selected in the previous sub-trip.

· Specific driving reason sets the driving reason to that specified by the front-end software.

When driver prompting occurs, The relevant function LED flashes for 8 seconds, and the buzzer will beep. Prompting can be
disabled by the user by selecting a driving mode before the sub-trip has started.

Saving the Driving Reason

The driving reason is stored at the end of each sub-trip – this means that during a sub-trip, the driver can still change the driving
reason. The driving reason is only saved at the end of a sub-trip if the vehicle has moved 100 metres.

NOTE: The driving reason will not be saved if the FM Keypad is not plugged in.

802
www.mixtelematics.com

802
 803

Driving Reasons Only Mode:

If the voice functionality has been disabled, the Network LED will be turned off and the OBC will issue an error beep if the driver
tries to make voice calls.

Voice Functionality
Making phone calls

A phone call is initiated by holding B1,B2,B3 or B4 down for two seconds. After two seconds the OBC acknowledges the delayed
press, and issues a quick double beep as confirmation. If the button pressed has been configured for a phone number, the phone
call will be made, or else a long error beep will ensue. When the phone call is made, the network LED will flash between off and
green. The pressed function LED will flash at a quicker rate between off and red.

Receiving phone calls

When a phone call is received, the FM Keypad alerts the user by flashing the network LED between red and green. After the
phone call has been answered or rejected, the function LED’s will return to the last selected driving reason.

Answering the call

An incoming call can be answered by pressing any of the function buttons.

Rejecting the call

An incoming call can be rejected by pressing the hang up button

Interaction between Voice and Taxlog

When a call is made, the function LED corresponding to the button will flash. If a driving reason is selected after the LED has
started flashing, the driving reason will be selected and displayed (corresponding to the button press), and the LED will stop
flashing and remain solid.

Backlighting

The FM Keypad keys are backlit, and will stay on for the duration of the trip. When a vehicle ends a trip, the backlighting will stay
on for five more minutes and will then be switched off. If the user presses any key, or the vehicle starts another trip, the
backlighting will be turned back on again.

Note: Tests have shown that although the Keypad lights may flash intermittently if exposed to emissions at certain frequency
bandwidths above 20Mhz, the lights will return to normal after the radiation has been removed. Recording of driving reasons is
not affected at all.

Software Configuration
Please read the FM Keypad User Manual for more details on Software Configuration.

803
www.mixtelematics.com

803
 804
7.6.2 FM Keypad User Manual

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The FM Keypad displays Taxlog driving reasons and GSM connection status visually, and provides for the selection of Driving
Reasons for Tax logging purposes, and the selection of Phone Numbers for making voice phone calls from the vehicle. The
driving reasons are logged by the FM200 along with all other trip information, and downloaded to the front-end software for
reporting.

The FM Keypad plugs directly into the FM200 Code Plug socket and requires no additional hardware configuration. Software
configuration is required and is explained in greater detail later in this document.

Taxlog
The FM Keypad records driving reasons. The driver can select any one of 4 driving reasons per sub-trip. Each sub-trip has one
driving reason ascribed to it.

Voice
The driver can phone any one of 4 predefined phone numbers and make a voice call. The vehicle can also receive voice calls.

This document includes the following sections:

· FM Keypad Components

· Using the FM Keypad

· Installation (Please view the Fleet Manager Keypad Installation Manual)

Fleet Manager Professional Software

· Device Drivers

· FM Keypad Configuration

· Reports

FM Keypad Components
Faceplate Layout

804
www.mixtelematics.com

804
 805

Each function button has a corresponding function LED which turns on when a driving reason is selected. The driving reasons
are: Business, Commute, Private and Other. The function buttons are also used to select any one of four phone numbers with
which the FM200 will make a call. The network status LED shines green if the vehicle has GSM reception, and red if it does not.

Using the FM Keypad

Button Press Overview

The FM Keypad has two types of button presses, namely quick and delayed.

Quick button presses are used for driving reason selection, and delayed button presses are used for making voice calls.

Quick button press

The driver holds down the button until a quick beep is issued by the on-board computer, and then releases immediately

Delayed button press

The driver holds down the button until a quick beep is issued by the on-board computer, keeps holding it until a quick double
beep is issued by the on-board computer, and then releases the button.

Taxlog Functionality
Setting or Changing a Driving Reason

The driving reason is changed by making two quick button presses on the same button within three seconds.

Driver Prompting

Two options are available and can be set from the front-end, namely previous driving reason or specific driving reason.

· Previous driving reason sets the driving reason to that selected in the previous sub-trip.

· Specific driving reason sets the driving reason to that specified by the front-end software.

When driver prompting occurs, the relevant function LED flashes for 8 seconds, and the buzzer will beep. Prompting can be
disabled by selecting a driving mode before the sub-trip has started.

Saving the Driving Reason

805
www.mixtelematics.com

805
 806

The driving reason is stored at the end of each sub-trip – this means that during a sub-trip the driver can still change the driving
reason. The driving reason is only saved at the end of a sub-trip if the vehicle has moved 100 metres.

NOTE: The driving reason will not be saved if the FM Keypad is not plugged in.

Driving Reasons Only Mode:

If the voice functionality has been disabled, the Network LED will be turned off and the OBC will issue an error beep if the driver
tries to make voice calls.

Voice Functionality
Making phone calls

A phone call is initiated by holding B1,B2,B3 or B4 down for two seconds. After two seconds the OBC acknowledges the delayed
press, and issues a quick double beep as confirmation. If the button pressed has been configured for a phone number, the phone
call will be made, or else a long error beep will ensue. When the phone call is made, the network LED will flash between off and
green. The pressed function LED will flash at a quicker rate between off and red.

Receiving phone calls

When a phone call is received, the FM Keypad alerts the user by flashing the network LED between red and green. After the
phone call has been answered or rejected, the function LED’s will return to the last selected driving reason.

Answering the call

An incoming call can be answered by pressing any of the function buttons.

Rejecting the call

An incoming call can be rejected by pressing the hang up button

Interaction between Voice and Taxlog

When a call is made, the function LED corresponding to the button will flash. If a driving reason is selected after the LED has
started flashing, the driving reason will be selected and displayed (corresponding to the button press), and the LED will stop
flashing and remain solid.

Backlighting

The FM Keypad keys are backlit, and will stay on for the duration of the trip. When a vehicle ends a trip, the backlighting will stay
on for five more minutes and will then be switched off. If the user presses any key or the vehicle starts another trip, the
backlighting will be turned back on again.

Note: Tests have shown that although the Keypad lights may flash intermittently if exposed to emissions at certain frequency
bandwidths above 20Mhz, the lights will return to normal after the radiation has been removed. Recording driving reasons is not
affected at all.

Installation
Please see the Fleet Manager Keypad Installation Manual for more information.

Device Drivers
It will be necessary to update your vehicle unit’s device drivers.

A special driver has been written for the FM Keypad, and is available from the Fleet Manager Office CD (Fleet Manager 2002
Professional SR1and higher).

806
www.mixtelematics.com

806
 807

FM Keypad Software Configuration

Front-end Software

The FM Keypad device is connected to the code plug (CP) line. This is done from the device selection pane in the vehicle
properties:

There are two settings panes for the FM Keypad, namely Driving Reason and Voice:

Driving Reasons

Driving reason functionality can be disabled by unchecking the “Enable recording of driving reasons” checkbox.

The driver is prompted at the beginning of a sub-trip if a driving reason has not been entered. Prompting happens both visually
and audibly. The audible prompting can be disabled by unchecking the “Enable audible prompting” checkbox.

When the driver is prompted for a driving reason at the start of a sub-trip, the Keypad can either default to the previously entered
driving reason, or a specific driving reason as shown in the pane.

807
www.mixtelematics.com

807
 808

Voice

Voice functionality can be disabled by unchecking the “Enable Dialing” checkbox.

This pane allows the user to enter up to four voice phone numbers which the driver may phone from the vehicle. It is not
necessary for the user to enter all four numbers.

Audio channel selection can also be made, though most modems will use channel 1 only.

NOTE: This pane will be disabled if the vehicle does not have GSM connected

Reports

808
www.mixtelematics.com

808
 809

Fleet Manager Professional 9 provides the serious fleet operator with extensive fleet management tools to manage and report on
his fleet. The software enables you to manage vehicle, driver and passenger information, define and manage events to be
monitored, analyse fleet data and do extensive management reporting. In addition to the core software, Fleet Manager
Professional 9 also offers a set of extensions that allow additional monitoring and reporting on the fleet.

The Taxlog Extension contains FM Keypad specific reports. For more information on the Taxlog Extension, please read the Fleet
Manager Taxlog Extension document.

809
www.mixtelematics.com

809
 810

7.7 How to use Temperature Recorders with FM200 Plus

© 2008 MiX Telematics | Updated 2008/05/07

Supported devices
This document describes the functionality of interface between the FM200 Plus and any of the following types of Temperature
Recorders: Euroscan, Transcan-XL, Transcan-T2

Minimum requirements
This functionality is available for the FM200 Plus family on-board computers, with the device drivers and configuration provided
by FM Professional 8.21 or later.

You would also need the FM200 Plus serial cable accessory for connecting your recorder to the DB9 connector marked S3 (the
shorter of the two).

Event Configuration
The temperature recorders send various temperature and digital inputs to the OBC. These are interpreted by the FM200 Plus as
parameters that can be used in user event definitions.

810
www.mixtelematics.com

810
 811

Parameters
The following parameters are available:

Device connected

To see if the logger device is connected to the FM unit, the serial interface reports whether it can successfully communicate with
the device. If communications with the logger failed more than 3 successive times, the device connected bit will be cleared. As
soon as a device is connected its state will be set to true.

Temperatures

This will allow a valid temperature range of -50.00 ... 50.00°C. To keep in line with what the logger is reporting, any unconnected
or unsupported temperature inputs will be reported as 0°C. 5 Temperature inputs are supported, (4 + 1 ambient).

Digital

Digital inputs will be handled as bit fields. “0” implies inactive, while “1” implies active. To keep in line with what the logger is
reporting, any unconnected or unsupported digital inputs will be reported as inactive. 4 Digital inputs are supported.

Tick

Tick parameters are used with conditions for triggering the recording of temperature values at specific intervals on-the-hour every
hour, or down to every 5 minutes. This parameter is true for 1 second only, so it is advised to only record Notification events
when testing for this parameter to be true.

Event definition

By default none of the parameters are recorded. Therefore User events must be created that record the parameters based on
user-defined conditions.

811
www.mixtelematics.com

811
 812

This example shows the steps to add a very basic event to Record Temperature 1 every 15 minutes.

Note that Event Type should be set to Notification.

This example shows the steps to add a more complex event to Record Ambient Temperature Profile.

Thus under normal conditions where the ambient temperature is below 22°C it records the actual temperature on-the-hour every
hour, else if the temperature rises above this value it will record every 5 minutes.

812
www.mixtelematics.com

812
 813

Another example is "Record the average temperature every 5 minutes". This can be done by creating an event to monitor the
Average value of temperature while the Tick – 05 min is False, and record as Detail. This will save the average temperature over
the preceding 5 minutes every fifth minute.

Reports
Since the recording of temperature is done using user-defined events, use the standard event reports as illustrated below.

813
www.mixtelematics.com

813
 814

814
www.mixtelematics.com

814
 815

7.8 FM TCO Interface Installation Manual

© 2008 MiX Telematics | Updated 2008/05/07

Product Description
The Fleet Manager TCO interface is designed to connect to the range of FM200 on-board-computers. It enables the FM200 to
utilize tachograph information for fleet management purposes. Information provided by the tachograph, and logged by the
FM200, includes vehicle & engine speed, driver 1 & 2 driving modes (Active work, Passive work and Rest), vehicle moving/
stopped, engine on/off and chart error.

Tachographs
The FM TCO interface supports the following tachographs:

· F-TCO (TCO1319)

· M-TCO (TCO1324)

· Veeder-Root (2400)

To connect a FM200 to a K-TCO (1318), please refer to “FM KTCO1318 Interface Installation Manual".

Diagram
The wiring diagram for the FM TCO interface is shown in Figure 1.

Figure 1

815
www.mixtelematics.com

815
 816

Installation
Connecting FM200 to F-TCO (1319), M-TCO (1324) or Veeder Root 2400:

Interfacing between a FM200 and any one of the TCOs must be done via the TCO interface as shown in figure 2. The Table
below indicates which pin on the TCO to connect to. Note: The first time the FM200 detects TCO communication, the FM200 LED
will quickly flash five times.

Figure 2

Connection Table

Tachograph TCO pin

F-TCO (1319) B5

M-TCO (1324) D8

Veeder Root 2400 D8

816
www.mixtelematics.com

816
 817

7.9 FM KTCO1318 Interface Installation Manual

© 2008 MiX Telematics | Updated 2008/05/07

Product Description
The FM KTCO1318 optical interface is designed to pass Driving Modes as well as vehicle and engine speed (if available on the
specific tachograph), to a standard FM200 Plus unit.·

· The interface connects the FM200 Plus and the standard EC KTCO1318, using the optical output of the KTCO.

· The status of the Driving Modes Switches (Active Work, Passive Work and Rest) is supplied to the FM200 Plus.

· Two additional status events are sent to the FM200 Plus. These are TCO ERROR (No Chart or Door Open) and VEHICLE
DRIVING.

· The optical interface connects to the FM200 Plus much in the same way as a regular speed sender unit. This is a 3-wire
interface, made up of Ground, Speed input and Speed sender voltage.

· The FM KTCO1318 optical interface supports both speed-only as well as speed-and-rpm tachographs.

Installation
Connection to KTCO1318

· Using a 3mm diameter twist drill, carefully drill through the membrane covering the optical output. Please refer to the necessary
FM Service Information documentation.

· Fit the optical interface to Tachograph.

Connection to the FM200 Plus

· The optical interface is connected to the FM200 Plus much like a speed sensor would be. See the Wiring diagram below,
remembering to pay special attention to colour of each wire.

· Note: The first time the FM200 Plus detects TCO communication, the FM200 Plus LED will quickly flash five times.

FM200 Plus Device Driver Installation

· Please refer to the documentation on the installation CD or see our website for latest details.

Wiring Diagram

817
www.mixtelematics.com

817
 818

818
www.mixtelematics.com

818
 819

7.10 FM Terminal
© 2008 MiX Telematics | Updated 2008/05/07

Overview
The FM Terminal is a versatile keypad and display unit. It is designed to work in conjunction with existing and future FM Fleet
management and MiX Telematics products. The FM Terminal is both configurable and re programmable. This means that the
actual menus and events that provide its functionality can be customised to suit the application. Using the FM Terminal, a driver
can capture operating data (for example: reasons for journeys, re-fuelling data, laid-up periods, customer details, product orders,
etc.) in the FM200 on-board computer. The display unit will also show standard event violations as detected by the FM 200 unit.
Two management reports are available to present this data in a useful format. The FM Terminal is shipped with the basic Fleet
logbook functionality as well as capabilities for Job and Free-Text Messaging.

Features

Configurable & re programmable The actual menus and events of the FM Terminal can be configured and reprogrammed
by a suitably qualified developer to suit the business need.

Menu driven system The standard FM Terminal menu is clearly laid out, making it easy and simple to use.
One of two languages, including international settings, can be selected from the menu.

Quality product Solid construction, attractive design and a flexible installation concept make the FM
Terminal suitable for any vehicle and any type of fleet.

On screen display Trip information and violation warnings are displayed on the screen.

Keyboard data input The FM Terminal has a built-in keypad for simple data capture.

Support for external devices External keyboards or bar-code readers can be connected to the Terminal

Internationalised The FM Terminal supports a number of different languages, daylight saving, different
units of measure and different currencies.

Automatic display dimming The FM Terminal display backlighting will dim automatically if there is no keypad activity
for 60 seconds. The contrast is automatically adjusted with temperature variation.

Automated Fleet Log Book The FM Terminal can automate functions such as Driving Reasons and Resting
Reasons.

Job and Free-Text Messages If the FM Terminal is connected to a GSM modem, it can be used to send and receive job
and text messages from the vehicle.

Technical Information

Operating 0 ... 60 ‘C Display resolution 128 x 64 pixels

temperature

Operating voltage 9 … 36 V Backlight LED

Memory 1MB Display type Graphical Liquid Crystal

819
www.mixtelematics.com

819
 820

Data Capture
Drivers can capture data via the FM Terminal’s built-in keypad or via an external keyboard or bar-code scanner that can be
connected to the FM Terminal

The driver can enter trip and freight details, including:

· Reason for trip (e.g. business or private or maintenance),

· Reasons for stopping (e.g. refueling or maintenance or traffic jam)

· Customer details (e.g. Names, Codes, Costs and Locations)

· Fuel quantity and cost, etc.

· Free text and responses to job messages

· All details entered into the Terminal are stored in the FM 200 unit and are displayed in the Fleet Manager software reports.

Jobs and Free Text Messaging

When combined with a GSM Modem, then job and free-text messages can be sent and received from the FM Terminal.

Job Messages

When a new job is received by the FM Terminal, a pop-up message will be displayed saying that a new job has arrived and focus
will be moved to the Job List menu. The Job List Menu shows the current list of jobs assigned to the vehicle. The new job
message can be accepted, rejected or postponed, after which the FM Terminal will send a reply will convey the status of the
message.

Text Messages

As with Job Messages, a notification will be displayed when a new Text Message arrives, and focus will be moved to the Inbox.
The new text message can be read, replied to, or deleted.

Job and Text Status

Different icons indicate a unique message and/or job state:

· Read message / job.

· Unread message / job.

820
www.mixtelematics.com

820
 821

· Urgent message / job.

· Accepted job

· Postponed job.

Automated Fleet Log Book

The Fleet Log Book on the FM Terminal has a manual and automated option. If the Fleet Log Book is automated, it provides the
following automatic functions:

· Once a trip has started the “Driving Reasons” menu will automatically be activated. When a vehicle has travelled 1km the
“Driving reason” is sent to the FM200 on-board-computer to be stored.

· When ignition is switched off the “Resting Reasons” menu is automatically activated. When a trip ends the “Resting reason” is
sent to the FM200 on-board-computer to be stored.

External Devices

Keyboard The FM Terminal has an external keyboard port to which most IBM AT compatible “QWERTY” keyboards
can be connected, using a converter cable.

Barcode scanner Keyboard compatible barcode scanners can also be used provided they do not exceed the FM Terminal
electrical rating.

Warning messages will display on the FM Terminal screen if it detects an incompatible keyboard or scanner.

Software
The Fleet Manager Professional 9 software application includes two reports that present data captured on the terminal and stored
in the FM 200 on-board computer.

The FM Terminal Log Book Report is a log of all entries and events recorded by the FM Terminal, including entries captured by
the driver. This report summarises the Customer codes, Driving and Resting Reasons with the sub trips recorded by the FM 200
unit. The FM Terminal Event Report shows each menu event recorded by the FM Terminal, and each vehicle departs and halts.
Both reports can be exported into a .csv format for processing by an external application. The Active Tracking and Messaging
extension is used to message jobs and free-text messages between office and vehicle.

821
www.mixtelematics.com

821
 822
7.10.1 FM Terminal User Manual

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The FM Terminal is a versatile keypad and display unit. It is designed to work in conjunction with existing and future FM Fleet
management and Telematics products. The FM Terminal is both configurable and re programmable. This means that the actual
menus and events that provide its functionality can be customised to suit the application. The FM Terminal is shipped with the
basic Fleet logbook functionality as well as Job and Free-Text Messaging. It is this basic functionality and menu structure which is
described in this Manual.

Warning: Although the FM Terminal is firmware upgrade able, some older units (with OS versions older than 1.7) may become
unusable after an upgrade. If this happens, please exchange your unit for a new one.

Using the FM Terminal

The following topics will be discussed in the User Manual:

· Menus

· Switching the FM Terminal on and off

· Automatic Fleet Log Book

· Job List

· Text Messages

· Job and Text Messages States

· Clearing Job and Text Messages

· Daylight Savings

· Languages

· Display Control

· Critical Events

822
www.mixtelematics.com

822
 823

· External Keyboard/Barcode Reader

· Mounting

· Cleaning FM Terminal

Menus
Menu Navigation

Menus can be navigated by either:

· Pressing the menu item number.

· Using the up and down arrow keys to highlight the desired menu option and then pressing the “RET” key.

Main Menu

1. Job List

2. Text Messages

3. Fleet Log Book

4. Trip Display

5. Options

By pressing the “ESC” key, the parent menu is activated.

Data Entry

Text and numbers can be entered into the field space provided. The left arrow key is used to “backspace”. By holding the left
arrow key down, the entire field can be cleared. The contents of the field together with its appropriate identifier is sent to the
FM200 on-board-computer when the “RET” key is pressed. Pressing the “ESC” key cancels the data entry operation.

Each keypad key on the FM Terminal has a number of characters allocated to it. By pressing the same key more than once, the
other characters can be accessed. If a number field such as “Customer code” is selected, the keypad keys will always start their
key cycle with the associated key digit. If a alphanumeric field such as “Description” is chosen the keypad key cycle will begin
with the first associated key character.

Switching the FM Terminal on and off

The FM Terminal will switch on automatically when the following events occur:

· Any key is pressed.

· A driver is identified by means of a driver key.

823
www.mixtelematics.com

823
 824

· Vehicle ignition is switched on.

· If the FM200 is in Drive mode (rpm and/or speed is present).

The FM Terminal will switch off automatically on completion of a trip once the FM200 on-board-computer enters its armed state
(the FM200 indicator LED starts to flash) and ignition is off. This will happen only if there has been no keyboard activity for the
last 60 seconds, in which case the FM Terminal will delay switching off until the user has completed his operation.

Automatic Fleet Log Book

The automatic fleet logbook provides the following automatic functions:

· On power on, the FM Terminal will activate the “Value 2” menu with the menu item “Customer code” selected.

· Once a trip has started the “Driving Reasons” menu will automatically be activated. When a vehicle has travelled 1km the
“Driving reason” is sent to the FM200 on-board-computer to be stored.

· When ignition is switched off the “Resting Reasons” menu is automatically activated. When a trip ends the “Resting reason” is
sent to the FM200 on-board-computer to be stored.

Note: If the user is busy typing on the keypad or if an event message has been displayed, the FM Terminal will not immediately
automatically activate the Driving or Resting reason Menu. The FM Terminal will wait until there has been a 30-second period of
no keypad or event activity before activating the appropriate automatic menu. The automatic functions can be disabled in the
Fleet Manager Windows application.

Job List
The Job List shows the current list of jobs assigned to the vehicle. When a new job is received by the FM Terminal, a pop-up
message will be displayed saying that a new job has arrived and focus will be moved to the Job List menu.

Text Messages
If the FM200 is set up to use a GSM modem, then Text Messages can be sent and received from the FM Terminal. FM Terminal
can only accommodate/send 40 characters but can receive 120 characters.

As with Jobs, a notification will be displayed when a new Text Message arrives, and focus will be moved to the Inbox.

Note: The FM Terminal can only send 40 characters but it can receive 120 characters.

For more information on sending and receiving text messages using Fleet Manager Client software, please view the Active
Tracking and Messaging Extension documentation.

Job & Message States

These icons each indicate a unique message and/or job state:

· Read message / job.

· Unread message / job.

· Urgent message / job.

· Accepted job.

· Postponed job.

Clearing Text Messages and Jobs

824
www.mixtelematics.com

824
 825

Warning: This function should be used with the utmost caution. All Text Messages & Jobs will be deleted from the FM Terminal.

To clear all Text Messages and Jobs from the FM Terminal, disconnect the FM Terminal from the FM200 by unplugging the FM
Terminal cable. Then, holding down the ‘5’ key on the keypad, reconnect the FM Terminal.

Daylight Saving
The FM Terminal is capable of displaying the current date and time received from the FM200. This is displayed in the Trip display
menu. The FM200 date and time is not automatically corrected for daylight saving. The Daylight saving menu option allows the
operator to advance the time in hourly increments. This is to accommodate the change in time during summer months in areas
where daylight saving is practised. This feature will allow for a variance of up to 3 hours between the seasons.

Languages
The FM Terminal is shipped with two default languages, namely English and German. Other languages can be loaded via the
Fleet Manager Windows program.

Display Control
On newer versions of the FM Terminal, the display contrast is adjusted automatically, and can no longer be adjusted from the
keypad.

On older versions, both the screen brightness and contrast can be manually adjusted. There are three default display settings
which can be activated by pressing the zero "0" when in the Display Control screen. This is useful when the display contrast is
very dark or very light. This feature allows the operator to easily find a setting which is readable.

Automatic Display Dimming

The FM Terminal display backlighting will dim automatically if there is no keypad activity for 60 seconds. Any subsequent
automatic or manual menu action will cause the display to return to its previous setting.

Critical Events
Critical events can be selected from the Fleet Manager Windows program that will cause an event warning to be displayed on the
FM Terminal for the duration of the event. While the event remains true, the user can clear the message by pressing any key.

External Keyboard / Barcode Reader Socket

CAUTION: Do not plug in an external keyboard or barcode scanner while the FM Terminal screen is on (Display must be off).
This may cause damage to the QWERTY keyboard or barcode scanner.

For more information on how to connect a barcode reader/ keyboard to the FM Terminal, please consult the FM Terminal
Installation Manual.

The FM Terminal has an external keyboard port to which most IBM AT compatible “QWERTY” keyboards can be connected.
Keyboard compatible barcode scanners can also be used, provided they do not exceed the FM Terminal electrical rating. The FM
Terminal will sense the presence of electrically incompatible external keyboards or barcode readers and report these by means of
a warning message to the screen. Please ask your local distributor for information concerning compatible devices and conversion
cables.

Mounting Bracket
The FM Terminal can be mounted in most vehicles with the mounting bracket provided. Please ask your local distributor about
other mounting options.

Cleaning the FM Terminal

To prevent damage to the FM Terminal housing, use only a mild detergent and water on a damp cloth to wipe the FM Terminal

825
www.mixtelematics.com

825
 826

clean.

826
www.mixtelematics.com

826
 827
7.10.2 FM Terminal Installation Manual

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The FM Terminal is a versatile keypad and display unit. It is designed to work in conjunction with existing and future FM Fleet
management and MiX Telematics products. The FM Terminal is both configurable and re programmable. This means that the
actual menus and events that provide its functionality can be customised to suit the application.

· Installation

· Standard Installation

· Enhanced Installation: FM Terminal with GSM

· Enhanced Installation: FM Terminal with FM DECT

· Connecting External Devices

· Job and Free Text Messaging

· Declarations

· Software

· Configuring the FM Terminal

· FM Terminal Reports

Installation
Standard Installation

The standard installation requires the following:

FM Terminal Cable (sold

FM Terminal
together with FM Terminal)

Steps of standard installation

1. Connect the FM Terminal to the FM200 Plus using the FM Terminal cable

827
www.mixtelematics.com

827
 828

2. Set up the Device information in Fleet Manager Professional 9. The FM Terminal should be connected to S1.

3. Configure FM Terminal Critical Warning Messages

4. Update the FM Terminal unit

For Step 2,3 and 4 see Fleet Manager Terminal User Manual for more information.

Enhanced Installations: FM Terminal with GSM Modem

The enhanced installation with FM Terminal and External GSM requires the following:

FM200 Plus
Serial Cable
FM
Terminal
(X39.723-002-
082)

External
GSM

FM200 Plus

1. Connect the FM Terminal to the FM200 Plus using the FM200 Plus Serial Cable.

2. Connect the GSM Modem to the FM200 Plus using S2 on the FM200 Plus Serial Cable (S2 is the longest cable of the 2 DB9
connectors). The GSM antenna is to be mounted further than 20cm away from the human body under normal operating
conditions.

3. Set up the Device information in the Fleet Manager Professional software. The FM Terminal should be connected to S1, and
the GSM Modem to S2.

4. Configure FM Terminal Critical Warning Messages

5. Update the FM Terminal unit

FM200 Communicator

828
www.mixtelematics.com

828
 829

The FM200 Communicator has an internal GSM Modem connected to S2. Please follow the Standard Installation procedure when
installing the FM Terminal to a FM200 Communicator.

Enhanced Installations: FM Terminal with FM DECT

For more information on installing the FM Terminal with FM DECT, please read the FM DECT Installation Manual.

Connecting External Devices

Keyboard / Barcode Reader Overview

The FM Terminal supports the connection of either an AT compatible keyboard or barcode reader to the KBD port. These devices
can be used to enter information instead of using the FM Terminal keypad.

Compatible Devices

The keyboard or barcode reader must be compatible with the AT Keyboard standard and must not exceed the limitations of the
KBD port, as detailed below.

FM Terminal KBD Port Specifications

KBD supply voltage = 5V (±5%) under load. Open circuit voltage = 5V (+10%).

KBD maximum current sourced = 150mA.

Note: If the attached keyboard draws more than the maximum current, of 150mA, the FM Terminal will disable the KBD power
supply and display the message "Incompatible Device On KBD Port. Please Remove".

Caution

Do not connect an external device to the FM Terminal KBD port while the unit is powered-up. Always make sure that the unit is
'Shut Down' before inserting the connector. This can be done by selecting 'Shut Down' from the main menu. The FM Terminal is
'Shut Down' when the screen is blank.

Interconnection

An interface cable, which connects the keyboard or barcode reader to the FM Terminal is available from your local distributor.
Details of the cable are shown below.

Signal Name Mini-DIN(PS2) Modular Plug

Data 1 2

Not connected 2 ---

Ground 3 3&4

+5V 4 6

Clock 5 1

Not connected 6 ---

Not connected --- 5

829
www.mixtelematics.com

829
 830

Shield --- ---

Job and Free Text Messaging

Job and Free Text Messaging is available with on-board computers with GSM capability. The FM Terminal itself is shipped with
the basic Fleet Logbook functionality, as well as Job and Free-Text Messaging. The Active Tracking and Messaging Extension is
used in conjunction with Fleet Manager Professional 9 software to send/receive/manage job and free-text messages. For more
information, please refer to the Active Tracking and Messaging Extension documentation.

Customised Menu
The FM Terminal menus are re programmable and can be changed. For more information, please download the FM Terminal
Scripting document from the Fleet Manager website http://www.fm-web.co.za

Declarations
Type Approval

This product conforms to the requirements of Directive 71/245/EEC, as last amended by Directive 95/54/
EC.

021545

Software
The Fleet Manager Professional 9 software application includes two reports that present data captured on the terminal and
stored in the FM 200 on-board computer.

The FM Terminal Log Book Report is a log of all entries and events recorded by the FM Terminal, including entries captured by
the driver. This report summarises the Customer codes, Driving and Resting Reasons with the sub trips recorded by the FM 200
unit. The FM Terminal Event Report shows each menu event recorded by the FM Terminal, and each vehicle departs and halts.
Both reports can be exported into a .csv format for processing by an external application. The Active Tracking and Messaging
extension is used to manage jobs and free-text messages between office and vehicle.

830
www.mixtelematics.com

830
 831

Configuring the FM Terminal

The configuration of the FM Terminal can be done at three levels in the Fleet Manager Client application, namely the
Organisation level, Vehicle Configuration Group level, and Vehicle level.

The configuration of the FM Terminal has been changed in the Fleet Manager 2002 Professional SR1 and higher from previous
versions of Fleet Manager Software. The user now specifies a script to be used and can then select two languages to be sent to
the FM Terminal.

Configuring the FM Terminal functionality

The Devices tab on the Event Definitions dialog is used to specify the default configuration settings for devices in the Fleet
Manager system.

A similar tab can be found in both the Vehicle Configuration Group Property and Vehicle Property dialogs, to define the default
configuration settings for devices for a group of vehicles or an individual vehicle respectively.

In any of these dialogs, double-clicking the FM Terminal device opens the Device Properties dialog for the FM Terminal device.

The Calibration tab of the Device Properties dialog for the FM Terminal device has four entry fields.

· The first field allows you to enter the name of the folder containing the FM Terminal script files. This field is only enabled at the
Organisation level. Under normal circumstances, you should not need to change the contents of this field as the FM Terminal
script files are automatically installed into a folder named FM Terminal beneath the Fleet Manager program folder.

· The next is a combo box which is filled with the scripts present in the path.

· The other two fields allow you to select the primary and secondary languages to be uploaded to the FM Terminal.

831
www.mixtelematics.com

831
 832

Four scripts are installed for the following:

· FM_Metric_ALB.fmt (default)

· FM_Metric_MLB.fmt

· FM_Imp_ALB.fmt

· FM_Imp_MLB.fmt

The Metric scripts show distance and speed in Kilometres, the Imp scripts show distance and speed in miles.

The ALB scripts are Automated Fleet Logbook scripts. These scripts will automatically prompt the driver to enter driving and
resting reasons at the start and end of each trip.

The MLB scripts are Manual Fleet Logbook scripts. These scripts have the same menus as the ALB scripts, but do not
automatically prompt the driver for input.

Configuring FM Terminal Critical Event Warning Messages

Use the Actions tab on the Event Properties dialog to specify whether or not to display a warning message. You can also specify
whether to display the message immediately or only after the event has been true for a specified time period.

It is possible to configure certain FM200 events to cause a warning message to be displayed on the FM Terminal.

This option is available on the following events:

· Over speeding

· Over revving

· Harsh braking

· Idle - excessive

832
www.mixtelematics.com

832
 833

· Harsh acceleration

· FM200e - High engine temperature

· FM200e - Low coolant

· FM200e - Low oil pressure (linear of RPM)

Updating the FM Terminal Units

There are two methods to transfer the FM Terminal menus and Critical Event configuration settings to the FM Terminal unit in the
vehicle.

Firstly, after editing the FM Terminal device or one of the critical events in the Vehicle Properties for the vehicle, the Fleet
Manager Client application, will prompt you to update the vehicle’s green code-plug.

If you change the Organisation or Configuration Group level properties, the Fleet Manager Client application will remind you that
you should manually update the green code-plugs of affected vehicles. To do this, use the Initialise Vehicle Plug Wizard function
available from the Code-Plug menu.

Insert the affected vehicle’s green code-plug into Download Module and follow the instructions in the Wizard. Make sure that you
check the Build FM Terminal menus option.

833
www.mixtelematics.com

833
 834

Positive Drive
With Fleet Manager 2002 Professional SR1 and higher, the FM200 Plus / FM Messenger unit can turn off the Positive Drive
which the FM Terminal gets power from. It is important to ensure that the terminal is connected correctly to the FM200 unit before
inserting the code-plug into the vehicle’s socket. If the FM Terminal does not wake up when a button is pressed, insert a Driver
plug into the vehicle socket to ensure the Positive Drive is on.

Beep and Flash Codes

The FM Terminal will sound three short beeps to acknowledge the successful transfer of the new menus configuration settings.

A single long beep signifies that the FM Terminal did not accept the new menu definitions. If this happens, please ensure that the
FM Terminal scripts are correctly installed on your computer. Due to changes in the way that the FM Terminal operates, it is
important to ensure that the FM Dealer utility is used to upload the latest Device Drivers to both the on-board computer and the
FM Terminal device.

Please note that it is not possible to update the FM Terminal menus via GSM or DECT. It is however possible to update the
Critical Event configuration settings via these methods.

FM Terminal Reporting
There are two reports in the Fleet Manager Client application that can be used to view the information collected by the FM
Terminal units.

FM Terminal Event Report

The first report shows each menu event recorded by the FM Terminal, and each Vehicle depart and halt. The report is sorted into
Date and Time sequence. The Criteria Wizard for the report can be used to select the required vehicles and a specific date
period for the report.

834
www.mixtelematics.com

834
 835

Fleet Log Book

The second report is the Fleet Log Book report. This report summarises the Customer codes, Driving and Resting Reasons with
the sub trips recorded by the vehicle’s on-board computer. The Criteria Wizard also allows the selection of required vehicles and
a date period.

It is also possible for third-party software developers to access the FM Terminal information using the Fleet Manager Extension
interface.

835
www.mixtelematics.com

835
 836

7.11 FM Trailer ID
© 2008 MiX Telematics | Updated 2008/05/07

Overview
The Fleet Manager Trailer ID (FM Trailer ID) is designed and developed to monitor your assets and cargo. The FM Trailer ID can
be fitted to any trailer, which can be coupled to a vehicle equipped with a Fleet Manager (FM) 200 on-board computer.

The FM Trailer ID monitors when and where trailers are connected, disconnected and the distance the trailer travelled. Service
Reminders can be generated to remind the Fleet Manager of upcoming Trailer Services.

Features

Easy Installation The FM Trailer ID is very easy to install. It has only two wires, one which connects to the on-board
computer, and one which is the ground wire

Robust design The FM Trailer ID is designed to be used in rough conditions. It is both durable and waterproof.

Daisy-Chaining The FM Trailer ID enables more than one trailer to be connected to a truck – up to four trailers can
be connected to one vehicle with an on-board computer installed.

Low Cost This is a very economical way to monitor your trailers in addition to your vehicles

Technical Information

Operating temperature -40ºC to +85ºC

Storage temperature -40ºC to +85ºC

Current consumption The FM Trailer ID supply current is typically 3mA.

Voltage 9 – 30 V

Data Recording

The FM Trailer ID derives its power from the vehicle battery line, which is collected through the on-board computer (OBC). The
FM Trailer ID records the following details when a trailer is connected or disconnected from a vehicle:

· Date and Time

· The vehicle to which the trailer is/was connected

· Odometer Reading

· Vehicle Position

When the trailer is connected, it continuously sends a unique signal to the on-board computer, to ensure that the trailer is still
connected. Once the trailer is disconnected, the data is stored in the database and the Fleet Manager can see when the trailers
were connected or disconnected.

836
www.mixtelematics.com

836
 837

Software
The Fleet Manager Trailer ID Extension is used in conjunction with the Fleet Manager Professional 9 software and provides
functionality to allow fleet managers to maintain and report on trailer-related information for their fleets. Functionality is included
to maintain trailer records, including service information.

A suite of five reports is included: Detail Trailer Report (by Vehicle), Detail Trailer Report (by Trailer), Summary Trailer Report (by
Vehicle), Summary Trailer Report (by Trailer) and Trailer Service Reminder Report.

Please see the Fleet Manager Trailer Management Extension documentation for more information.

837
www.mixtelematics.com

837
 838
7.11.1 FM Trailer ID Installation Manual

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The Trailer-ID unit (X10-723-002-014) has two wires protruding from it: GROUND & SIGNAL. The GROUND (brown) wire needs
to be connected to earth while the SIGNAL (blue) wire needs to be connected to an Analog Line (I1 or I2 or I3 or I4) on the
FM200. Since the Trailer-ID is on the trailer, the connection has to be made via the Tractor-Trailer connector - usually a J560, 7-
wire connector. The Trailer-ID will therefore be connected to the FM200 via the J560’s Auxiliary wire (Blue wire). Not all trucks will
have the blue auxiliary wire available. In this case, it is up to the installer to choose an unused wire. If no unused wire is available,
Trailer-ID cannot be installed.

Minimum Requirements
The Trailer-ID units can only be installed on trailers that have at least one unused wire (usually the blue Auxiliary wire) available
on their Tractor-Trailer connectors.

Installation
Installation should occur in three steps:

Install Hardware.

1. Decide which analog line to use (I1, I2, I3 or I4) for Trailer Identification. This line is selected in the Front-End software in step
3.

2. Install the 470E pull-up resistor from the analog line to VBATTERY.

3. Connect the analog line to the unused (Auxiliary*) wire of the Tractor-Trailer connector, on the Tractor side.

4. Connect the corresponding wire (Auxiliary*), on the Trailer side, to the blue SIGNAL wire of the Trailer-ID.

5. Ensure all GROUND wires are properly connected, as shown in Figure 1.

Upload new Device Drivers to FM200.

1. Using the FM-Dealer utility, upload the new device drivers to the vehicle.

Update the vehicle Devices & Events.

1. From the Fleet Manager Professional software, update the vehicle’s Devices and Events and upload the new configuration to
the vehicle. I.e. choose the analog line that is used for Trailer Identification, and ensure that “Detail” events are being logged.

Connection Diagram

838
www.mixtelematics.com

838
 839

Declarations
Type Approval

This product conforms to the requirements of Directive 71/245/EEC, as last amended by Directive 95/54/EC.

022124

839
www.mixtelematics.com

839
 840
7.11.2 FM Trailer ID User Manual

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The FM Trailer ID allows trailers to be managed as part of the fleet. The Trailer’s unique ID is logged by the FM200, along with all
other trip information, and downloaded to the front-end software for reporting.

For instructions on the hardware installation of a FM Trailer ID, please refer to “FM Trailer ID Installation Manual”. Software
configuration is also required and is explained in this document.

Unique Trailer ID
Each Trailer ID is programmed with a unique ID, which is printed on the front of the unit. In the figure shown, the unique Trailer ID
is “83”. This allows the front-end software to track the trailer.

It is important to record this ID when installing the unit into a physical trailer, as this information is required by the Fleet Manager
Trailer ID Extension.

FM Trailer ID Software Configuration

Front-end

The FM Trailer ID devices can be connected to any of the digital lines, i.e. I1 to I8. Trailer IDs can be daisy-chained, so that up to
four can be connected to a single digital line. Only one digital line can be used at any given time.

840
www.mixtelematics.com

840
 841

Fleet Manager Software

Please see “Fleet Manager Trailer Management Extension” document for information on using the Trailer Management Extension
and Reporting functions.

841
www.mixtelematics.com

841
 842

7.12 FM Wireless Trailer ID

© 2008 MiX Telematics | Updated 2008/06/25

Overview
The FM Wireless Trailer ID solution allows users of MiX Telematics FM and Datatrak products to identify trailers connected to
tractor units via a wireless link. The system comprises a trailer mounted Tag and a tractor mounted Tag Reader which connects
to either an FM300 or MK6 Datatrak Locator via a serial connection. The trailer Tag can be used as a standalone device or it can
be coupled to door switches and temperature sensors to provide additional information. The Reader can be configured to receive
Tags over a medium range (~250m) or a short range (~4m).

General information
The Tag comprises an FM low power transmitter module operating in the 433MHz band and a PIC microcontroller. The power for
both of these devices is sourced from a single 3.6V lithium cell where the PIC micro is permanently powered but the FM
transmitter is only switched on during transmit.

The Tag Reader is connected to the vehicle or tractor unit on to which trailers with active tags are connected. The Reader can be
powered either directly from the vehicle supply with an ignition input to set the reader into standby power mode or from an
external device i.e. the FM300.

For applications where a much shorter range can be used for reading the Tag ID, the RSSI signal can be used to control the
receiver sensitivity. By selecting a high level of RSSI, the Tag will have to be much closer for it to be read and decoded. This
reduction in range will prevent the reader picking up other tags.

Once powered, the reader will start to pick up transmissions from trailer tags in range. The decision for the tag to be attached
(assumed to be connected to the trailer) is only started when a “moving” signal is sent from the FM300 or MK6. Once the
“moving” signal is received a maximum of 2 tags will be selected as attached. These tags must be received on 7 consecutive
updates and if more than 2 tags are detected, the count is reset.

The movement indicator is an event set up on the FM 300 or MK6. The event requires the following:

· Speed >7kmph (GPS derived)

· Ignition on

· In Trip

Product Range
The Tag and Tag Reader product range has several variants as listed below:

Tag

· A7185/1 – Tag Transmitter with 4 x Digital Inputs

· A7185/2 – Tag Transmitter in Sealed Enclosure

Tag Reader

· A7183/1 – Tag Reader and Transmitter (Loading Bay configuration)

· A7183/2 – Tag Reader with 20dB Attenuator

· A7183/3 – Tag Reader Analogue Comms (no Attenuator)

Note: The A7183/2 product variant has the short range option as it has an internal 20dB attenuator at the RF input to the receiver
module.

842
www.mixtelematics.com

842
 843

Features

GENERAL FEATURES

Trailer Tag · Low power – long operating life from internal battery

· Range – 20cm to ~250m

· Digital inputs – up to 4 available, dependant on product option. Detect multiple switch

open/closed states via a voltage free switch.

· Analogue input for temperature probes

Tag Reader · FM Transceiver capability

· AM Receiver capability

· Low power standby operation

· Range – 20cm to ~250m, dependant on product option

· Serial communications

· SPI communications via the FM300 bus

· 1 RS232 Serial Interface which can be connected to any RS232 serial device using the
FM300 Serial Harness

Technical description: Trailer Tag

Physical Size PCB - 85 x 65 x 18mm

Weight 35g

Battery · 3V AA Lithium Cell – 1.1AHr (Tadiran)

· Minimum operating voltage: 2.2V

· Standby current 5µA

· Tx current: 5mA for 25ms every 20 seconds

· Operating Temperature: 25% at +80°C, 10% at -20°C and 65% varied

· Battery life estimated at over 5 years

Frequency 433.92MHz

Modulation FM (30kHz deviation)

RF Power +5dBm

843
www.mixtelematics.com

843
 844

Antenna Internal

Temperature Range -20°C to +80°C

I/O Connections Spring load terminals

Technical description: Tag Reader

Physical Size 115 x 75 x 30mm

Weight 55g

Supply 8V DC to 32V DC

Frequency 433.92MHz

Modulation FM (30kHz deviation)

Rx Sensitivity -103dBm

Antenna Internal

Temperature Range -20°C to +80°C

Serial I/F RS232 levels (Rx, Tx, CTS, RTS)

844
www.mixtelematics.com

844
 845
7.12.1 FM Wireless Trailer ID Setup

Wireless Readers can only connect to a maximum of 2 trailer tags

Set-up in FM Professional
There are 2 modes of operation – long range and short range.

Short Range Mode

For use in the range of ½ - 3m

Must use short range reader

1. In FM Pro, select the device on S3.

2. In the calibration tab select the RSSI check box

3. If you choose RSSI a slider appears

4. The higher the RSSI level, the closer the tag must be to the reader to connect.

5. RSSI values are an index and proportional to the signal strength the reader should connect to it is not an indication of distance.

Preconditions for the Short Range Mode

Single ID transmission = connected

Long range Mode

For use up to 250m

Must use long range reader

1. Ensure RSSI box is unchecked

2. Pre-conditions for a connection event for long range mode:

3. Tag transmits its ID 6 consecutive times to the reader

4. Speed must be >7km/h

5. The Tag transmits every 4 minutes

845
www.mixtelematics.com

845
 846

7.13 USB Download Module

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The USB Download Module allows data to be downloaded from or uploaded to the code plug, using the Fleet Manager
Professional Software. The USB Download Module connects to any USB port on a PC. This guide explains how to install and
configure the USB Download Module to work with an FM Installation.

USB Download Module Components

USB Download Module

USB Download Module Harness

The download module has a code plug socket with an LED. The code plug socket accepts code plugs, and the LED is used to
indicate that the USB Download Module is writing to or reading from the code plug.

Installing the USB Download Module

Install the FM Professional 8.2 Software.

Perform the following steps to install the USB Download Module Hardware:

• Plug the Mini-B connector of the harness into the USB Download Module.

846
www.mixtelematics.com

846
 847

• Plug the “A” connector into an available USB port.

After the USB Download Module has been plugged in, the following message pops up:

Select “No, not this time”, and click Next.

Ensure that “Install the software automatically (Recommended)” is selected, and click Next.

The above form is displayed, while the software is installing software for the device.

847
www.mixtelematics.com

847
 848

Click Continue Anyway.

Click Finish.

Configuring the Software for the USB Download Module

848
www.mixtelematics.com

848
 849

Configuring the Fleet Manager Client

Edit the Options of the Fleet Manager Client, by selecting Options from the Tools menu, and selecting the Code Plug tab. The
following form will be displayed:

Select “USB” and click OK.

Configuring the FM Dealer Utility

Load the Fleet Manager FM Dealer utility.

From the Settings\Port menu, select USB.

Prerequisites for the USB Download Module

A USB 1.1 or USB 2.0 card is required to run the USB Download Module.

849
www.mixtelematics.com

849
 850

7.14 FM100
© 2008 MiX Telematics | Updated 2008/05/07

Overview
The FM100 is the entry-level product for the Fleet Manager range. It offers an ideal solution for driver and vehicle management
for a small fleet.

The FM100 records the most important events – over-speeding, over-revving, green band driving, harsh braking and excessive
idling. The data can be transferred from the vehicle to the software using the green vehicle plug with minimum effort.

Features

Trip Data Recording Standard recorded data includes:

• Date and time

• Distance

• Speed

• Engine Speed (RPM)

• Trip start/depart/end time

• Driver name and ID

• Vehicle ID

Driving Violations The following five standard violations are recorded:*

• Over Speeding, Over Revving, Green Band Driving (low and high), Harsh Braking and
Excessive Idling

* It is not possible to define custom events on the FM100.

Driver Warning A buzzer can be set to sound when an event occurs.

Driver Identification A driver tag (code-plug) is used to identify a driver. Starter circuit interruption is available.

Servicing and Licensing Reminders can be set when your vehicle’s next service is due or when your vehicle / driver
licence expire.

On-board Memory (32 KB) Up to 700+ trips, including event and violation data (caters for in excess of 30 days of driving @
20 trips per day)

850
www.mixtelematics.com

850
 851

Technical Information

Operating voltage 9... 16 V Protection class IP 54

Interrupter relay max. 25A Clock Component Real Time Clock

Memory 32 KB EEPROM Indicator Integrated buzzer

Interface I2C for the connection of the code-plug reader

Event Parameters

Over speeding • Speed > (x) where (x) is user defined

Excess idling • Idling time longer than (time), where (time) is user defined

Over revving • RPM > (x) where (x) is user defined

Harsh braking • Deceleration < (x) where (x) is user-defined

Green band • RPM < (x) or RPM > (y) where (x) and (y) are user defined

Trip start • (Ignition “on” and driver identified) or speed detected or RPM detected

Trip end • Rev = 0 and speed = 0 and no speed for longer than (time) where (time) is user defined between 3
seconds and 10 minutes

Data Downloading
Code Plug

The code-plug mechanism is the only means of extracting data from a FM100 unit. A 32Kb plug is inserted into the vehicle’s
code-plug socket, and then inserted into a download module connected to a computer.

Software
The FM100 can use one of two software packages:

• The Fleet Manager Lite software package is a simple application for the analysis and management of data recorded by the
FM100.

• The Fleet Manager Professional 9 client-server software application is designed to work in conjunction with the entire range of
Fleet Manager Products, including the FM200 range of on-board computers and FM accessories. This sophisticated software
package enables users to manage vehicle, driver and passenger information, manage and analyse event data and as well as do
extensive management reporting.

851
www.mixtelematics.com

851
 852
7.14.1 FM100 Product Manual

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The FM100 covers the following topics:

· Safety Regulations

· Installation

· Configuration

· Function test

· Starting

· Maintenance

· Troubleshooting

· Operating manual of the FM100

Safety Regulations
Notes before the Installation

Requirements

NOTE:

· Unqualified intervention into the vehicle may adversely affect the operating reliability of the vehicle and therefore can endanger
other road users. Please pay attention to the articles of the StVZO (Road Traffic Licence Regulations)!

· For the installation, basic knowledge of car electric and mechanics are necessary. The Fleet Manager 100 may only be
installed by trained car mechanics who should have a working knowledge of the operation of computers. We strongly
recommend a training course at FM for the installation, configuration and operation of the Fleet Manager 100.

· Before the installation make yourself familiar with the vehicle specifications concerning the specific vehicle type and possible
special characteristics! Make sure you are familiar with the vehicle layout in regards to fuel/hydraulics/compressed air- and
other electrical wiring!

· Pay attention to possible wiring changes in the vehicle before you begin installation!

· No smoking, open fire or lighters/matches!

Securing the Workplace

· Take the ignition key out of the ignition. Ensure that there is no possibility of an unintentional engine start during installation.

· Record all data from volatile memories, as the loss of data is possible. When disconnecting the negative pole of the battery all
volatile memories loose their values. Therefore please record all corresponding data for reprogramming before disconnecting.

· Short circuits inside the vehicle electrical system can cause fire in the wiring, explosion of the battery and damage to other
electrical systems. Disconnect the negative pole of the vehicle battery before starting to work! If the vehicle has additional
batteries it may be necessary to disconnect the negative poles of these also

852
www.mixtelematics.com

852
 853

Notes during the Installation

When fitting or removing seats, covers, etc., please ensure that no cables are damaged or that cable connections are detached.
Only install non-defective parts into your vehicle.

Installation Position

· During installation, ensure that the components of the product do not influence or hamper the functions of the vehicle and are
not damaged. At the installation location note that you have the necessary room behind the drilled hole or the installation
opening for the installation. Please pay attention to the course of cables.

· Do not choose the installation location in the mechanical or electric airbag area.

· Do not drill into supporting or stabilising braces or beams.

Procedure

For small installation openings use a drill and for bigger openings use a cone milling cutter, a compass saw or file. Trim the
edges. Pay careful attention to the safety regulations of the tool manufacturers. Oils and fuels must be collected in appropriate
size and suitable containers and then disposed of in accordance to the law.

Wiring

Pay attention to the cable cross-section. If the cross section is reduced the current density increases. This can cause a heating
up of the corresponding cable section. If you lay the electrical connection cables please use the existing cable channels.

· Do not lay the cables parallel to ignition cables or to cables which run a high amount of current. Fix the cables with cable ties or
insulation tape.

· Do not run the cables over moving parts. Do not fix cables on the steering column.

· Please ensure that the cables are not exposed to pulling, pressure or shearing.

· If the cables are pulled through drilled holes protect them with rubber grommets or similar.

· For stripping of cables only use a cable stripper. Adjust the stripper so that it can not damage or separate the strands.

· Solder new cable connections smoothly or use a crimping tool. Crimp connections only with a crimping tool.

· Pay attention to the safety directions of the tool manufacturers.

· Isolate free strands so that no short circuits can occur.

· Avoid creating short circuits through faulty connections or crimped cables.

· Short circuits inside the vehicle electrical system can cause fire in the wiring, explosion of the battery or damage to other
electrical systems. Therefore all connections of the current circuit must be soldered or provided with weldable joints and
suitably insulated. Other connections such as. the tap of the speed or revolution signal or the connection of the brake light or
the clutch switch can be made with the usual crimped connections.

· Faulty connections can lead to short circuits. Only connect the cable according to the electrical connecting plan.

· For measuring current and voltage inside the vehicle only use a multi-meter or diode testing lamps. The use of ordinary testing
lamps can cause damage to control devices or to other electronic systems.

Note After Installation

· Connect the earth cable with the negative pole of the battery

853
www.mixtelematics.com

853
 854

· Reprogram the values of the volatile memories

· Check all (!) vehicle functions.

· Introduce the customer to the functions of the Fleet Manager 100 and hand over the operation manual

Note While Operating

If you do not use the product as directed it can cause personal injury, material damage and damage to the environment.
Therefore only use the product as directed!

Declarations
Confirmation of conformity

The product was developed, produced and tested according to the regulations 71/245/EWG which were
updated with 95/54/EG and the recognised state-of-the-art.

021230

Usage as directed

The product is only for use in land based vehicles (except motor bikes).

Year 2000 compliance

The Fleet Manager 100 system is year 2000 compliant when used with Fleet Manager 100 software version 1.20 (incl. SR4) or
later. Year 2000 compliance is also provided when using Fleet Manager 98 software version 2.20 (incl. SR1) or later.

Product overview
E-Box X39-723-002-001

Speed signal/revolution signal

· Rectangular signal min. 3 V PP

· Offset (Rectangle) max. 4 V

· Tracer relation 20% - 80%

· Sine signal min. 12.5 V PP

· Frequency 1 – 5000 Hz

854
www.mixtelematics.com

854
 855

· Overvoltage protection +/– 600 V peak, +/– 50 Volt DC

No. of revolution signal (frequency)

· Rectangular signal min. 3 V PP

· Offset (Rectangle) max. 0.5 V

· Tracer relation 20% - 80%

· Sine signal min. 4 V PP

· Frequency 1 – 5000 Hz

· Overvoltage protection +/– 600 V peak, +/– 100 Volt DC

· Protection class IP54

Rated voltage 12 Volt

Working voltage 9 ... 16 V

Working voltage max. 18 Volt for 1 hr., 24 Volt for 5 min.

Storage temperature -20 °C ... +70 °C

Working temperature -40 °C ... + 85 °C

Humidity (max.) 95%

Clock component Real Time Clock (RTC)

Backup Lithium Battery

Memory 32kb EEPROM (9600bps)

709 trips, equivalent to 1 month with 30 trips per day

Interrupter relay max. 25A

Indicator Buzzer

Interface I2C for the key reader

E-Box X39-723-002-053

855
www.mixtelematics.com

855
 856

Speed signal/revolution signal

· Rectangular signal / sine signal

· Offset Voltage pp pp > 0.5V

· Tracer relation 1% - 99%

· Frequency max 5000 Hz

· Overvoltage protection +/– 600 V peak, +/– 50 Volt DC

no. of revolution signal (frequency)

· Rectangular signal / sine signal

· Offset (Rectangle) -50 ... + 50 Volt

· Offset Voltage pp pp > 0.5V

· Tracer relation 1% - 99%

· Frequency max 5000 Hz

· Overvoltage protection +/– 600 V peak, +/– 100 Volt DC

· Protection class IP54

Rated voltage 12 /24 Volt

Working voltage 9 ... 36 V

Working voltage max. 40 Volt for 1 hr., 50 Volt for 5 min.

Storage temperature -20 °C ... +70 °C

Working temperature -40 °C ... + 85 °C

Humidity (max.) 95%

Clock component Real Time Clock (RTC)

Backup Lithium Battery

856
www.mixtelematics.com

856
 857

Memory 32kb EEPROM (9600bps)

709 trips, equivalent to 1 month with 30 trips per day

Interrupter relay max. 25A

Indicator Buzzer

Interface I2C for the key reader

Key reader X39-723-002-005

Connection Compact plug

Fixing Pin up socket for wedging

Connecting cable X39-723-002-002

857
www.mixtelematics.com

857
 858

Plug Connections Compact plug for FM 100 Electronic

Compact plug for key reader

Indicator Integrated Buzzer (12 Volt)

Connection for Voltage Supply

Speed Signal

Number of Revolution signal

Driver key (blue) X39-723-002-006

Case Plastic

Memory 8kb EEPROM (9600bps)

Driver ID, Using Permission, Date and Time

Calibration set X39-723-002-028

SPDCAL

For programming of the two calibration keys you will need the FM Dealer Utility.

Car key (green)

858
www.mixtelematics.com

858
 859

Case Plastic

Memory Memory 32kb EEPROM (9600bps)

709 trips, equivalent to 1 month with 30 trips per day

RPMCAL

Order numbers

X10-723-002-003 Fleet Manager 100

(incl. X39-723-002-053, .../002, .../003, .../004, .../005, .../006, .../007)

X39-723-002-053 Electronic FM 100

X39-723-002-002 Cable FM 100

X39-723-002-003 Metal housing FM 100

X39-723-002-004 One way screws FM 100 (4x)

X39-723-002-005 Key reader FM 100

X39-723-002-006 Driver key FM 100 (blue)

X39-723-002-007 Car key FM 100 (green)

X39-723-002-008 Software Fleet Manager 100

X39-723-002-009 PC Read in device FM 100

X39-723-002-010 Installation Guide Software German/English

X39-723-002-027 Voltage converter 24/12 Volt (for FM 100 X10-723-002-001)

X39-723-002-028 Calibration set

System Requirements
The Fleet Manager 100 is designed for vehicles with 12/24 V onboard voltage (FM 100 X39-723-002-001 only in conjunction with
a 24/12 V voltage transformer). For the calibration and functional test after the installation of the Fleet Manager 100, the
workshop must have the Fleet Manager Lite or Fleet Manager Professional software program. The FM Dealer Utility should also
be available.

859
www.mixtelematics.com

859
 860

System Description
The Fleet Manager 100 is an on-board computer for use in land based vehicles (except motor bikes), for recording vehicle
information such as speed, engine revolutions, parking-, stop- and driving times. To obtain the registration of the driver, the Fleet
Manager 100 is equipped with a relay which can be used for the interruption of the ignition circuit. The registration of the driver is
carried out with a driver specific key. For the transmission of the vehicle information from the vehicle to the car pool centre there
is a special key available. Read in data may be analysed and processed with the Fleet Manager Lite Software as well as with the
Fleet Manager Professional software. The Microsoft Access Database guarantees flexibility, which simplifies the processing and
export of the information.

Versions
FM 100 Kit X10-723-002-001 from 11/97 to 1st quarter of 1999 contains: FM 100 E-Box X39-723-002-001

FM 100 Kit X10-723-002-003 from 1st quarter of 1999 contains: FM 100 E-Box X39-723-002-053

The version introduced in the 1st quarter of 1999 differs from the first FM 100 version; its operating voltage is extended to 12/24 V
and it offers improved signal processing. In addition, there is no need for a signal converter for processing PWM signals.

Installation
Technical requirements

The workshop installing the Fleet Manager 100 needs:

· the usual technical equipment for cars, tools and aid

· a PC with Windows 3.x, Windows 95/98, 2000, NT4 or XP.

· The Fleet Manager 100 calibration set

· The FM Dealer Utility software

· Fleet Manager Lite or Fleet Manager Professional software

Personal Requirements

The technician who does the installation of the Fleet Manager 100

· must be a trained automotive technician,

· shall know how to use a PC,

· should have had training at FM about the installation, the

· configuration and the operation of the Fleet Manager 100.

Note

We assume in the following guide that the technician has occupation-specific comprehensive knowledge and has complete
command of the actions which correspond to the occupation. We would like to emphasise that unqualified intervention into the
vehicle can influence the operating reliability of the vehicle negatively and therefore can endanger other road users. Please pay
attention to the articles of the StVZO (Road Traffic Regulations).

Please pay attention to the safety information in the FM100 Product Manual.

Tools

860
www.mixtelematics.com

860
 861

For the installation of the Fleet Manager 100 you need the usual tool set of an automotive technician. In addition car specific tools
for removing the casing or consoles may be needed.

Installation E-Box
Installation position

The E-Box must be installed inside the passenger compartment or the driver cabin, so that it is protected against damage.

Note: Please pay attention to the safety regulations regarding the Installation position.

It must not be installed near to the ventilation or heating opening because it could cause damage due to overheating. The
installation position of the E-Box must be protected against pressure, impact and excessive vibration.

After careful selection of the installation position you can install the E-Box.

Mark the holes you want to drill on the installation area and drill the holes. Lay out the connection cables from the installation
position of the E-Box to the corresponding connections inside the vehicle. Information on this can be found in the wiring plan.

After the installation and the functional test of the Fleet Manager 100 put the E-Box into the protection housing and lock it with the
provided one-way screws. Mount the housing with the attached screws onto the installation area.

Installation of FM100 key reader

Installation position

The key reader must be installed inside the closed passenger area or the driver cabin, so that it is protected against damaging.

Note! Please pay attention to the safety regulations regarding the Installation position.

It must not be installed near to or in the ventilation or heating opening because it could cause damage due to overheating.

The installation position of the key reader must be protected against pressure, impact and excessive vibration. After careful
selection of the installation position you can install the key reader.

Mark the selected area on the installation area and drill the hole. Remove the mounting clip of the key reader. Remove the
protection film on the gummed surface of the protection ring and stick it against the back of the base. Put the base through the
hole and press on the mounting clip.

Wiring
Connect the cables according to the wiring diagram.

861
www.mixtelematics.com

861
 862

Interruption

The Fleet Manager 100 has an internal relay. This is intended for the interruption of the starter circuit.

Connection

Attach the two cables onto the corresponding connections of the Fleet Manager 100. Separate the cable from the ignition lock to
the starter (clip 50) and solder the ends from the Fleet Manager 100 cables with the ends of the cables from the starter. The order
in which the connection is done does not matter, because the relay is a normally open relay which is closed with the driver’s
registration.

NOTE: The internal relay is only there for the interruption of the starter circuit (clip 50). Do not use it for the interruption of the
voltage supply of the fuel pump or the ignition (clip +15)!

862
www.mixtelematics.com

862
 863

Configuration
Driver- and Data key

Configuration

For the calibration of the Fleet Manager 100 you need the calibration set, which contains the two calibration keys "SPD

CAL" and "RPM CAL". In addition, you will need the FM Dealer Utility.

Before you can carry out the calibration of the Fleet Manager 100 to the number of revolutions per distance and the engine
number of revolutions, the driver and the data key need to be configured and the first initialising of the Fleet Manager 100 must
be carried out. Proceed as follows:

Note: The following procedure only refers to the use of Fleet Manager 100 software.

Step 1

Take the blue and the green key out of the Fleet Manager 100 package.

Step 2

Start the Fleet Manager 100 Software on your Computer.

Step 3

Open the data transfer menu item and click on "initialise key". Choose the first item "Initialising of the green car key" and click on
"Enter". If the vehicle which is to be initialised is not on the list choose "add". Insert the registration number and a short
description of the vehicle (e.g. estate car green) into the input box and click "Enter".

Step 4

Insert the mileage in the corresponding field. This value will be transmitted to the Fleet Manager 100 during the next data
transmission.

For the configuration of the blue key proceed as follows:

Step 5

Open the data transfer menu item and click on "initialise key". Choose the second item "initialise the blue key" and click on
"Enter". If the driver who is to be initialised is not on the list choose "add". Insert the name of the driver into the input box and click
on "OK". The blue key is now allocated to the chosen driver.

First Initialising

Put the green vehicle key into the key reader. The Fleet Manager 100 transmits the data which is on the key and saves among
other things the car registration. The system is now ready for operation.

Note Before you can record vehicle information , you must calibrate the system to the movement impulse number and the engine
revolution frequency as described below:

Distance

Calibration

Disarm the system with the blue key and drive to the beginning of a 20 meter length. Put the violet key with the label "SPD CAL"
into the key reader and drive exactly 20 meters. Remove the violet key from the key reader at the end of the measured length.
The Fleet Manager 100 is now calibrated to the vehicle movement impulse number.

Note The pre-programmed value (20m) of the violet key "SPD CAL" can be changed to any value with the "FM Dealer Utility".

863
www.mixtelematics.com

863
 864

Number of revolutions

Calibration

Disarm the system with the blue driver key. Put the violet key with the label "RPM CAL" into the key reader and start the engine.
Increase the number of engine revolutions to 2000 rev./min and keep this value constant and pull the violet key out of the key
reader. The Fleet Manager 100 is now calibrated to the number of revolutions of the vehicle.

Note The pre-programmed value (2000 rev./min) of the violet key "RPM CAL" can be changed to any value with the "FM Dealer
Utility".

FM Dealer Utility - Software Program

The FM Dealer Utility can be found on the Fleet Manager Professional CD-ROM or can be ordered directly from FM. Notes on
operation can be found in the corresponding help file.

Function test
Read out data - Test drive

Put the blue key into the key reader and wait for the beep. Pull the key out again and start the engine. Leave the engine for at
least two minutes in neutral gear to get a stop time registration. Carry out a test drive.

Read out

After the test drive turn off the ignition and put the green car key into the key reader. Two beeps are heard which indicates data
transmission. At the same time the LED on the key reader starts to flash. Now you can pull out the vehicle key and transfer the
data via the read in station and the computer to the Fleet Manager 100.

Note Information on the procedure on this can be found in the manual and the help function of the Fleet Manager Lite
programme.

Starting
Setting of date and time

To make sure that only current values regarding date and time exist in Fleet Manager Lite, these values should be re-set after the
first initialising.

Note Please pay attention to the time difference between the time of the initialising of the key in the computer and the data
transmission in the vehicle. The transmission must take place at the time that is programmed on the key!

Software

Open the menu item "Data transmission" in the Fleet Manager Lite Software. Click on the entry "Setting date/time" and insert the
date and time at which you are going to put the key into the key reader. Put the blue key into the read in device at the computer
and click "OK". The values will be written onto the driver key.

Vehicle

Put the blue key in the key reader exactly at the time that you have set with the software. Three short beeps indicate that the
values have been read into Fleet Manager Lite. The values are now programmed.

Note Daylight saving must be activated.

Setting of Vehicle Root Data

Fleet Manager Lite allows the setting of vehicle specific values e.g. threshold values for speed, number of revolutions, stop times,
parking times and so on. These values are defined in the Fleet Manager Software and are transmitted to the vehicle with the

864
www.mixtelematics.com

864
 865

green vehicle key.

Software

The procedure for this can be found in the operating manual and the help function of the Fleet Manager Lite Software. Once the
vehicle root data is set, they must be transmitted to the green vehicle key.

Vehicle

Put the green vehicle key into the key reader. The data on the key will automatically be read into the Fleet Manager Lite. Make a
test drive and read the data for control reasons into the Fleet Manager Lite Software.

Maintenance
The Fleet Manager 100 is maintenance-free. Please take care that the connections inside the key reader stay free of dirt.

Troubleshooting

Problem Possible Cause Solution

LED does not flash No voltage Check the voltage supply of the Fleet
Manager 100.

The Fleet Manager 100 can not be The blue driver key is not enabled for the Use the correct driver key or get the driver
released vehicle key enabled for the vehicle

The recorded vehicle data is incorrect The Fleet Manager 100 has not been Calibrate the Fleet Manager as described
calibrated correctly again

Time/Date of the trips are incorrect The clock in the Fleet Manager 100 is set Set the date and time by means of the
incorrectly blue driver key.

The buzzer warns when turning on the The driver registration was not done Register with your blue driver key
ignition
or there is no user permission for this Get your blue driver key enabled for the
vehicle vehicle

Operating manual of the FM100

Driver registration and release of the on-board computer

For the driver registration put the blue driver key, which carries your personal ID, into the key reader inside the vehicle. The on-
board computer gives two beeps and the LED inside the key reader stops flashing. Your driver ID has been transmitted and you
can start the engine. If the LED inside the key reader still flashes, the registration has failed or you do not have user permission
for the vehicle. If you have user permission, repeat the procedure.

Data transmission

For the transmission of the data put the green vehicle key into the key reader of the vehicle. A short beep indicates the start of
the data transmission. The LED inside the key reader starts flashing fast, while the data gets transmitted. After the transmission a
short beep sounds and the LED flashes at one second intervals. Only the data will be read that was added since the last reading,
that is why the time between the two beeps can be very short. Should a failure occur during transmission (e.g. key full) you will be
informed by a long beep. Please note the information in the section "10.5 Acoustic signals".

Setting of the vehicle root data

865
www.mixtelematics.com

865
 866

For the setting of the vehicle root data you use the green vehicle key. This key will be initialised by the software with the vehicle
threshold values. These values will be transmitted to the on-board computer the next time you put the key in. From this moment
on the on-board computer works with the new settings. Details on the various threshold values can be found in the manual
Installation and configuration of the software or directly in the help function of the software.

Setting of date and time

For the setting of date and time you must initialise the blue driver key as described in the manual installation and configuration of
the software.

Note: Daylight saving must be activated.

Put the key into the key reader of the vehicle exactly at the time and date set on the PC. Date and time will be re-set
automatically, the time settings on the key will be deleted afterwards.

Acoustic signals

The FM 100 on-board computer has a diagnostic function which gives information about memory capacity, communication with
data keys and operating conditions over acoustic signals.

866
www.mixtelematics.com

866
 867
7.14.2 FM100 User Manual

© 2008 MiX Telematics | Updated 2008/05/07

Operation in the Vehicle

Driver log-on and enabling of the on-board computer

To log on as a driver, insert your blue driver key into the reader unit in the vehicle. The on-board computer will beep twice briefly
and the LED in the reader unit will go out. Your driver I.D. has then been loaded, and you can start the vehicle. If the LED
continues to flash, log-on has failed or you have no access entitlement for the vehicle. The entitlement can be stipulated with the
Fleet Manager software.

Data transmission

For data transfer, insert the green vehicle key into the reader unit in the vehicle. The on-board computer beeps briefly and starts
transferring the data. During transfer, the LED in the reader unit flashes rapidly. When data transfer is complete, a brief acoustic
signal sounds and the LED starts flashing in a one second rhythm again. Only the data which has been added since the last time
the key was read is transferred, and the time between the two acoustic signals can therefore be very short. Should an error occur
during data transfer (e.g. key is full), it is identified by an acoustic code. Please consult the notes in the following chapter.

Setting of the vehicle setup data

Use the green vehicle key to set the vehicle setup data. It is to be initialised with the vehicle limit data by means of the software.
When the key is next inserted in the vehicle, the data is transferred to the on-board computer. From that moment onwards, the
on-board computer functions with the latest settings.

Details of the various limits can be found in the installation and operating manual for the software or direct in the software help
function.

Setting of date and time

In order to set the date and time in the on-board computer, initialise the blue driver key on the PC as described in the installation
and operating manual for the software. Insert the key into the reader unit in the vehicle on the exact date and at the exact time
that you set on the PC. The date and time are then automatically reset, and the time settings on the key are deleted.

Troubleshooting

Problem Possible Cause Solution

LED does not flash No voltage Check the voltage supply of the Fleet
Manager 100.

The Fleet Manager 100 can not be The blue driver key is not enabled for the Use the correct driver key or get the driver
released vehicle key enabled for the vehicle

The recorded vehicle data is incorrect The Fleet Manager 100 has not been Calibrate the Fleet Manager as described
calibrated correctly again

Time/Date of the trips are incorrect The clock in the Fleet Manager 100 is set Set the date and time by means of the
incorrectly blue driver key.

The buzzer warns when turning on the The driver registration was not done Register with your blue driver key
ignition
or there is no user permission for this Get your blue driver key enabled for the
vehicle vehicle

867
www.mixtelematics.com

867
 868
7.14.3 FM100 Beep and Flash Codes

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The FM100 communicates with acoustic and visual signals. Below is a list of all the FM100 Beep and Flash Codes.

FM100 Audible buzzer

Red Lamp on Code-plug socket

Signal sequence

CONDITION BEEP AND FLASH CODE DURATIONS COMMENTS

Before a Trip

Normal ‘Armed No beeps This is the normal ‘Armed’

Mode’ mode. It indicates that the
1/8s on. 1s FM 100 is operational and
off is not in trip mode or busy
with any other operation.

Driver 1/4s on. 3/4s If driver identification is

identification off required, the beeps will be
requested repeated 10 times, or until
Lamp off an authorised driver is
identified. This depends
on the selection made in
the FM Professional
Vehicle Properties
options.

Driver 2 x 1/8s When an authorised

authorised to beeps driver’s identification plug
drive vehicle is inserted, two short
Lamp off beeps will be heard. The
driver will now be
permitted to start the
vehicle. The lamp will
remain off, indicating that
the FM 100 is now in the
‘Disarmed’ mode.

Driver not 1 x 1/2 s When an unauthorised

authorised to beep driver’s plug is inserted,
drive vehicle one long beep will be
1/8s on. 1s heard. The FM 100 will
off remain in ‘Armed Mode’
as indicated by the lamp
flash rate. The driver will
be unable to start the
vehicle.

868
www.mixtelematics.com

868
 869

FM 100 memory 3 x 1/8s 3 Short beeps. The FM

80% - 95% full. beep 100 memory is 80% - 95%
full and must be
Lamp off downloaded, with a green
code plug. If driver
identification was
required, this warning will
occur one second after
successful identification.
Otherwise, it will be heard
when the trip begins.

FM 100 memory 3 x 1/2s 3 Long beeps. The FM

95% - 100% beeps 100 memory is 95% -
full. 100% full and must be
Lamp off downloaded, with a green
code plug. If driver
identification was
required, this warning will
occur one second after
successful identification.
Otherwise, it will be heard
when the trip begins.

During Calibration

Speed or RPM 1s on. 1s While the violet calibration

calibration plug off. plug is inserted, long
inserted (Violet beeps will be heard. The
Plug) Flashes lamp flash rate is
dependant on the
frequency of the
calibration pulses (one
change per 25 pulses).
This is an indication that
the pulses are being
detected by the FM 100.

Setting date 3 x 1/8s Three short beeps will be

and time (Blue beeps heard if the date and time
Plug) was set successfully. The
Unchanged flash sequence will remain
------ unchanged ------- unchanged and depends
on the status of the FM
100 when the blue plug is
inserted.

During a Trip

Event alarm Continuous While any event alarm

beep threshold is being
exceeded, the buzzer will
Lamp off sound continuously and
the lamp will remain off.

During Data Transfer

869
www.mixtelematics.com

869
 870

Incorrect 1 x 1/2s If the incorrect green plug

vehicle plug beep is inserted, the buzzer will
inserted. give one long beep and
1/8s on. 1s the flash sequence will
off remain unchanged.

Correct vehicle 1 x 1/8s One short beep marks the

plug inserted – ------- data transfer ----- beep start of the data transfer.
Successful During the transfer, the
download of trip Lamp flickers lamp flickers. One short
data. beep indicates the end of
downloading trip data.
When the transfer is
complete, the lamp will
resume the normal
‘Armed Mode’ flash rate.

Correct vehicle 2 x 1/8s One short beep marks the

plug inserted – ------- data transfer ----- beep start of the data transfer.
Successful During the transfer, the
transfer of Lamp flickers lamp flickers. Two short
configuration. beeps indicate the end of
uploading configurations.
When the transfer is
complete, the lamp will
resume the normal
‘Armed Mode’ flash rate.

Correct vehicle 1 x 1/2s One short beep marks the

plug inserted – ----- data transfer ---- beep start of the data transfer.
Unsuccessful During the transfer, the
data transfer. Lamp flickers lamp will flicker. If the
transfer was unsuccessful
or incomplete, one long
warning beep will be
heard.

Green plug 1 x 5s beep A 5 second audible

memory full. warning will be heard
FM100 has not 1/8s on. 1s when the green plug’s
completed off memory is full, and the FM
transfer of trip 100 still has trip data to
data. transfer. The lamp flickers
while data is being
transferred and resumes
the normal ‘Armed Mode’
flash rate when the plug is
full.

Speed Calibration Diagnostic Plug Inserted

Speed pulses 1s on. 1s off. Long beeps are generated

connected to while the plug is inserted
FM100 Speed Lamp flashes The lamp flash rate is
input proportional to the
frequency of the signal on
the FM100 Speed input.

870
www.mixtelematics.com

870
 871

RPM Calibration Diagnostic Plug Inserted

RPM pulses 1s on. 1s off. Long beeps are generated

connected to while the plug is inserted.
FM100 RPM Lamp flashes The lamp flash rate is
input proportional to the
frequency of the signal on
the FM100 RPM input.

871
www.mixtelematics.com

871
 872

7.15 FM200
7.15.1 FM200 ComLink-GSM

© 2008 MiX Telematics | Updated 2008/06/24

Overview
The Fleet Manager 200 ComLink-GSM (FM200 ComLink-GSM) is based on the reliable platform of the FM200 Plus, offering
extensive driver and vehicle management, with an on-board GSM modem.

The GSM Modem allows you to improve the communication flow between the vehicle and office, by offering:

· remote downloading of vehicle and driver data

· remote configuration uploads

· real-time notifications and events

· optional headset for the driver

The FM200 ComLink-GSM combined with the FM Terminal, can improve communication and productivity further by allowing text
and job messages to be sent to and from the vehicle.

Data can be uploaded and downloaded remotely to and from your FM200 ComLink-GSM with the on-board GSM Modem,
ensuring that the downloading of data does not interfere with the daily activities of the drivers. Communication and safety is also
enhanced – with an optional headset, the FM200 ComLink-GSM can accept incoming calls, ensuring the driver’s focus stays on
the road.

Features

Active Events

Active Events Receive data messages (e.g. SMS) when selected standard or user-defined events take place,
such as over-speeding or when the hazard-lights has been on for longer than 4 minutes, and
the vehicle is not moving.

Communication

Downloading/uploading to/ The GSM Modem can be used to download and upload data from and to the FM200 ComLink-
from vehicle GSM. This can be done remotely without the need for the vehicle to be in the yard. The GSM/
GPRS Modem also enables the FM200 ComLink-GSM on-board computer to be actively tracked
by the Fleet Manager Software

Voice Calls The FM200 ComLink-GSM on-board computer allows incoming voice calls where a headset is
connected to the on-board computer (OBC).

Vehicle and Driver Management

Trip Data Recording For every journey the vehicle takes, the following information is recorded:

Date and Time, Distance or Hours, Speed or Hours, Engine Speed (RPM),Trip started / ended
time, Trip depart / arrive time, Driver Name & ID, Vehicle ID

872
www.mixtelematics.com

872
 873

Driving Violations The following standard violations are recorded:

Over Speeding, Over Revving, Green Band Driving (low and high), Harsh Braking, Harsh
Acceleration, Excessive Idling and Overtime Driving

Customised Events You can also define customised events, such as driver door opening, hazard lights activated,
refrigerator temperature exceeded

Second-to-Second (Tacho) The FM200 ComLink-GSM records the status of all inputs (e.g. speed, RPM, brake lights) every
Data second, which provides valuable in-depth information for accident analysis.

Servicing and Licensing Reminders can be set when your vehicle’s next service is due or when your vehicle / driver
licence expire.

Driver Identification & A driver tag can be used to identify the driver, and a default driver can be assigned to a vehicle.
Immobilisation The FM200 ComLink-GSM can also be installed with an immobiliser function – the car will only
start if an authorised driver inserts his driver tag.

Warning Buzzer A warning buzzer can be set to sound when driving violations or events take place.

Active Events

With Active Events, you can receive a text message when the refrigerator temperature exceeded the acceptable limit or when the
driver is over-speeding. The Active Events can per set up per individual vehicle, per site or per organisation.

With Active Events, you can deliver real-time fleet management information to the fleet manager's desktop or cell phone such as
when the refrigerator temperature exceeded the acceptable limit or when the driver is over-speeding. You can choose which
messages you would like to receive, and from which vehicles.

Communication

The FM200 ComLink-GSM allows incoming voice calls where a headset is connected to the on-board computer (OBC). This
allows the drivers to safely communicate over a head-set, allowing them to focus on the road.

Remote Downloads
The FM200 ComLink-GSM enables you the download the vehicle and driver data remotely, without the need for the vehicle to be
in the yard.

Remote downloading and uploading of configurations ensures that the downloading of data does not interfere with the daily
activities of the drivers.

873
www.mixtelematics.com

873
 874

Technical Information

8 configurable analogue The FM200 ComLink-GSM analogue or digital inputs can be configured to monitor any device that
or digital inputs generates a change in voltage, e.g. seat belts, headlights, refrigeration units, emergency lights,
doors, PTO, UDS, trailer coupling etc.

4 auxiliary frequency input The FM200 ComLink-GSM auxiliary frequency input can be configured to monitor any device that
generates a change in frequency e.g. temperature sensor, liquid flow measurement or as a pulse
counter e.g. electronic fuel consumption measurement (EDM)

2 Auxiliary relay drive This can be used to switch a relay with a current consumption of up to 150 mA.

2 Serial interface (1x This can be connected to any TTL or RS232 serial device using the FM Serial cable (e.g. FM
RS232 and 1x TTL) Terminal).

A second RS232 Port (S2) is connected to the internal GSM/GPRS Modem

Software
Fleet Manager Professional 9 provides the serious fleet operator with extensive fleet management tools to manage and report on
his fleet. The software enables you to manage vehicle, driver and passenger information, define and manage events to be
monitored, analyse fleet data and do extensive management reporting. In addition to the core software, Fleet Manager
Professional 9 also offers a set of extensions that allow additional monitoring and reporting on the fleet.

The FM200 ComLink-GSM is also supported by our Internet solution, FM-Web.

874
www.mixtelematics.com

874
 875
7.15.1.1 FM200 ComLink-GSM Installation

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The FM200 ComLink-GSM is based on the FM200 Plus, all the FM200 Plus functionality is available on the FM200 ComLink-
GSM with the exception of the external use of the S2 serial interface. The FM200 ComLink-GSM is fitted with an onboard GSM
module.

Installation
Notes on Installation

1. The FM200 ComLink-GSM is already loaded with compatible device drivers and a basic vehicle configuration.

2. The unit needs to be calibrated for RPM and Speed, while the vehicle ID and odometer need to be configured.

3. It is important to select the correct mounting location for the FM ComLink-GSM. Do not mount it close to air ducts that can
channel cold or hot air directly onto the unit. The GSM antenna is to be mounted further than 20cm away from the human body
under normal operating conditions.

4. Do not twist the FM200 ComLink-GSM unit if mounted on an uneven surface.

5. Do not connect the S2 serial port to any external devices, these lines are in use by the internal GSM module.

6. GSM is powered via Positive Drive and GSM must be configured on S2.

7. Ensure that the GSM antenna connector nut is properly secure onto the GSM connector.

8. Do not bundle the GSM antenna with any wiring harnesses as this could cause interference.

9. Loop the antenna cables onto the main harness cable close to the unit and secure with suitable cable-tie.

10.Ensure that the GSM cable is tension free where the cable connectors plug into the unit.

Handsfree Kit

· Only use Siemens FM HFD-01-01-103

Software Setup

1. The FM200 ComLink-GSM is compatible with the Fleet Manager Dealer Utility version 2.10.1.0 or higher.

2. Ensure that the latest devices drivers are uploaded to the unit.

875
www.mixtelematics.com

875
 876

3. Select the GSM modem on the S2 serial port.

4. Select to power the GSM modem from the Positive drive line.

Testing the Installation

1. After the GSM configuration and new vehicle configuration has been set, upload to the unit the GSM can be tested with a GSM
diagnostic code plug to check for network connection.

2. Once the calibration has been done a test drive must be performed with a reasonable duration, speed and distance. If possible
check whether violations such as over speeding and excessive idling are recorded.

3. Download vehicle and check Tacho data to verify that all devices and events are recording correctly at all data ranges.

4. Perform download via GSM to verify that vehicle is downloading and GSM modem and SIM is functioning correctly.

FM200 Communicator Installation Checklist

1. Unit has been mounted properly.

a) Not close to air ducts, moving parts or areas with excessive heat or moisture.

b) Unit not twisted if mounted on an uneven surface.

c) The S2 serial port is not connected to any external components.

d) The GSM antenna is secure and not bundled with any wiring harnesses.

e) Cables are tension free where the cable connectors plug into the unit.

f) The GSM antenna is mounted further than 20cm away from the human body under normal operating
conditions.

2. Unit has been connected to proper power, ignition and earth and wiring has been cut to the correct lengths.

3. All connections are secure, soldered and insulated.

4. Wiring harness has been insulated with insulation tape or sleeving and all wiring has been secured with clamps
or cable ties away from any sharp metal or moving objects

876
www.mixtelematics.com

876
 877

5. Upload ID to unit.

6. Upload Configuration to the vehicle insuring that the GSM is configured for S2.

7. Set date and time.

8. GPS unit has been given approximately (15 minutes) after initial power up to download complete almanac (Did
not interrupt power during this time) and operation was verified with GPS diagnostic plug.

9. Calibrate speed and RPM inputs.

10. Perform a test drive with a reasonable duration, speed and distance. (If possible check whether violations such
as excessive idling are recorded)

11. Download vehicle and check Tacho data to verify that all devices and events are recording correctly at all data
ranges.

12. Set odometer reading.

13. Perform download via GSM to verify that vehicle is downloading and GSM modem and SIM is functioning
correctly.

Declarations

This product conforms to the requirements of Directive 71/245/EEC, as last amended by Directive 95/54/
EC.

024001

It is possible for the GSM reception to be affected when certain frequencies are radiated close to the unit.

877
www.mixtelematics.com

877
 878
7.15.2 FM200 Communicator

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The Fleet Manager 200 Communicator (FM200 Communicator) is an on-board computer based on the stable and reliable
platform of the FM200 Plus. The FM200 Communicator offers the same extensive driver and vehicle management, but has an
additional internal GPS receiver and GSM modem.

The GPS receiver allows the recording of GPS Position information, which allows you to know exactly where you driver has been.
With the GSM modem, you can actively track your vehicles and request their position at any time.

Data can be uploaded and downloaded remotely to and from an FM200 Communicator with the GSM Modem, ensuring that the
downloading of data does not interfere with the daily activities of your drivers. Communication and safety is also enhanced – with
an optional headset, the FM200 Communicator can accept incoming calls, ensuring the driver’s focus stays on the road.

If you are concerned about security, the FM200 Communicator can be provided with battery backup, allowing the unit to keep on
communicating with the Fleet Manager Software even though the unit’s power has been cut.

Features

Location Management

Active/ Passive Tracking or You can request the position of his vehicle in real-time, or you can review the route taken after
Active Trail the trip has been downloaded. Active Trail allows the Fleet Manager software to be updated with
vehicle positions (GPS) every hour. For more information please visit What's new in Fleet
Manager Professional 9.

GPS Data Recording Various information is recorded with every GPS point, such as Vehicle and Driver ID, Date and
time, Latitude and Longitude, Altitude, Heading, Velocity, Number of Satellite etc

Manage Locations Locations can be added showing customer, supplier, no go zones or any desired locations.

Route Planning Routes can be planned by entering stops, the planned time of start and the planned duration of
each stop. This can serve as daily job activity sheets for your drivers.

878
www.mixtelematics.com

878
 879

Active Events Receive data messages (e.g. SMS) when selected standard or user-defined events take place.
E.g. A cargo door opening in a no-go zone, driver arrived at customer location.

Communication

Downloading/uploading to/ The GSM/GPRS Modem can be used to download and upload data from and to the FM200
from vehicle Communicator. This can be done remotely with out the need for the vehicle to be in the yard.
The GSM/GPRS Modem also enables the FM200 Communicator to be actively tracked by the
Fleet Manager Software

Voice Calls The FM200 Communicator allows incoming voice calls where a headset is connected to the on-
board computer (OBC).

Vehicle and Driver Management

Trip Data Recording For every journey the vehicle takes, the following information is recorded:

Date and Time, Distance or Hours, Speed or Hours, Engine Speed (RPM),Trip started / ended
time, Trip depart / arrive time, Driver Name & ID, Vehicle ID

Driving Violations The following standard violations are recorded:

Over Speeding, Over Revving, Green Band Driving (low and high), Harsh Braking, Harsh
Acceleration, Excessive Idling and Overtime Driving

Customised Events You can also define customised events, such as driver door opening, No-go zone entered,
hazard lights activated, refrigerator temperature exceeded

Second-to-Second (Tacho) The FM200 Communicator records the status of all inputs (e.g. speed, RPM, brake lights) every
Data second, which provides valuable in-depth information for accident analysis.

Servicing and Licensing Reminders can be set when your vehicle’s next service is due or when your vehicle / driver
licence expires.

Driver Identification & A driver tag can be used to identify the driver, and a default driver can be assigned to a vehicle.
Immobilisation The FM200 Communicator can also be installed with an immobiliser function – the car will only
start if an authorised driver inserts his driver tag.

Warning Buzzer A warning buzzer can be set to sound when driving violations or events take place.

Active Tracking

The internal GPS receiver and GSM/GPRS modem allow the FM200 Communicator to be actively tracked – the Fleet Manager is
able to see exactly where his vehicles are in real-time. Fleet Manager uses either the GSM Short Message Service (SMS) or the
GPRS connection to deliver the real-time information to you. For more information on GPRS, please refer to "GPRS Questions
and Answers".

With Active Tracking, you can track where you vehicles are at the moment, locate a vehicle closest to a customer location or view
the trail as the vehicle moves. Even if you do not request the position of a vehicle, the vehicle’s location positions are stored in
the on-board computer and can be used for historical (passive) tracking.

879
www.mixtelematics.com

879
 880

Communication

The FM200 Communicator allows incoming voice calls where a headset is connected to the on-board computer (OBC). This
allows the drivers to safely communicate hands-free, allowing them to focus on the road. The FM200 Communicator is
compatible with the Falcon A2-FSE02 Hands-Free Unit.

Battery Backup (Optional)

Optional Battery Backup is available if you would like more security. The Battery Backup starts to operate as soon as the supply
to the vehicle battery is cut. The battery backup is supplied by a Hi Temp NiMH Battery Pack. The backup time is a minimum of 4
hours, when the GSM is active in low power mode and the GPS is disabled.

Technical Information

8 configurable analogue The FM200 Communicator analogue or digital inputs can be configured to monitor any device that
or digital inputs generates a change in voltage, e.g. seat belts, headlights, refrigeration units, emergency lights,
doors, PTO, UDS, trailer coupling etc.

3 auxiliary frequency input The FM200 Communicator auxiliary frequency input can be configured to monitor any device that
generates a change in frequency e.g. temperature sensor, liquid flow measurement or as a pulse
counter e.g. electronic fuel consumption measurement (EDM)

A fourth auxiliary input (F3) is connected to the internal GPS receiver.

2 Auxiliary relay drive This can be used to switch a relay with a current consumption of up to 150 mA.

2 Serial interface (1x This can be connected to any TTL or RS232 serial device using the FM Serial cable (e.g. FM
RS232 and 1x TTL) Terminal). A second RS232 Port (S2) is connected to the internal GSM/GPRS Modem

Software

880
www.mixtelematics.com

880
 881

Fleet Manager Professional 9 provides the serious fleet operator with extensive fleet management tools to manage and report on
his fleet. The software enables you to manage vehicle, driver and passenger information, define and manage events to be
monitored, analyse fleet data and do extensive management reporting. In addition to the core software, Fleet Manager
Professional 9 also offers a set of extensions that allow additional monitoring and reporting on the fleet.

Our Internet Bureau Service, FM-Web, also supports the FM200 Communicator.

881
www.mixtelematics.com

881
 882
7.15.2.1 FM200 Communicator Installation Checklist

© 2008 MiX Telematics | Updated 2008/05/07

1. Unit has been mounted properly.

a) Not close to air ducts, moving parts or areas with excessive heat or moisture.

b) Unit not twisted if mounted on an uneven surface.

c) The GPS antenna is mounted where least metal obstruction will occur.

d) The F3 line and S2 serial port is not connected to any external components.

e) The GPS and GSM antenna is secure and not bundled with any wiring harnesses.

f) Cables are tension free where the cable connectors plug into the unit.

2. Unit has been connected to proper power, ignition and earth and wiring has been cut to the correct lengths.

3. All connections are secure, soldered and insulated.

4. Wiring harness has been insulated with insulation tape or sleeving and all wiring has been secured with clamps
or cable ties away from any sharp metal or moving objects

5. Upload ID to unit.

6. Upload Configuration to the vehicle insuring that the GSM is configured for S2 and the GPS for F3.

7. Set date and time.

8. GPS unit has been given approximately (15 minutes) after initial power up to download complete almanac (Did
not interrupt power during this time) and operation was verified with GPS diagnostic plug.

9. Calibrate speed and RPM inputs.

10. Perform a test drive with a reasonable duration, speed and distance. If possible check whether violations such
as excessive idling are recorded.

11. Download vehicle and check Tacho data to verify that all devices and events are recording correctly at all data
ranges.

12. Set odometer reading.

13. Perform download via GSM to verify that vehicle is downloading and GSM modem and SIM is functioning
correctly.

882
www.mixtelematics.com

882
 883
7.15.2.2 FM200 Communicator Installation Manual

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The FM200 Communicator is based on the FM200 Plus, all the FM200 Plus functionality is available on the FM200
Communicator with the exception of the external use of the F3 line and the S2 serial interface. The FM200 Communicator is fitted
with an onboard GSM and GPS module.

Installation
Notes on Installation

1. The FM200 Communicator is already loaded with compatible device drivers and a basic vehicle configuration.

2. The unit needs to be calibrated for RPM and Speed, while the vehicle ID and odometer need to be configured.

3. It is important to select the correct mounting location for the FM Communicator. Do not mount close to air ducts that can
channel cold or hot air directly onto the unit.

4. Do not twist the FM200 Communicator unit if mounted on an uneven surface.

5. Mount the GPS antenna where the least metal obstruction will occur. For best results place the antenna on a metal surface

6. Do not connect the F3 line or S2 serial port to any external devices. These lines are in use by the internal GSM and GPS
module.

7. GSM and GPS are powered via Positive Drive and GSM must be configured on S2.

8. Insure that the GPS antenna is correctly inserted all the way into the MCX panel mount connector socket.

9. Do not force the GPS antenna connector into the socket.

10.Ensure that the GSM antenna connector nut is properly secure onto the GSM connector.

11.Do not bundle the GSM antenna with any wiring harnesses as this could cause interference. The GSM antenna is to be
mounted further than 20cm away from the human body under normal operating conditions.

12.Loop the antenna cables onto the main harness cable close to the unit and secure with a suitable cable-tie.

13.Ensure that the GSM and GPS cables are tension free where the cable connectors plug into the unit.

Hands Free Kit

883
www.mixtelematics.com

883
 884

Only use the Siemens FM HFD-01-01-103:

· Pin1 - 9-32V

· Pin2 - Open

· Pin3 - Open

· Pin4 - GND

· Pin5 - SPK+

· Pin6 - SPK-

· Pin7 - MIC+

Software Setup

The FM200 Communicator is compatible with the Fleet Manager Dealer Utility version 2.10.1.0 or higher.

1. Select the GPS on F3 line in the software

2. Select to power the GPS from the Positive drive option

3. Select the GSM modem on the S2 serial port

4. Select to power the GSM modem from the Positive drive line

Testing the Installation

1. The first time the receiver is powered-up, it is searching for satellites from a cold start (no almanac). While the receiver will
begin to compute position solutions within the first two minutes, the receiver must continuously track satellites for
approximately 15 minutes to download a complete almanac. This initialization process should not be interrupted.

2. Insert a GPS diagnostic plug into the code plug socket.

3. A single beep is given when GPS information is received by the FM200 Communicator but no satellite fix is achieved. Please
wait a few minutes to give the GPS time to recover from the cold start and change from last position.

4. A double beep means that the GPS receiver achieved a satellite fix and all is in order.

5. If no double beep is being received from the FM200 Communicator then move the GPS antenna until a double beep is
achieved.

6. If a specific location in the vehicle is giving bad reception to the GPS antenna please relocate the antenna to a more suitable
position.

7. After the GSM configuration and new vehicle configuration upload to the unit the GSM can be tested with a GSM diagnostic
code plug to test for network connection.

8. Once the calibration has been done a test drive must be performed with a reasonable duration, speed and distance (If possible
check whether violations such as over speeding and excessive idling are recorded).

9. Download vehicle and check Tacho data to verify that all devices and events are recording correctly at all data ranges.

10.Perform download via GSM to verify that vehicle is downloading and GSM modem and SIM is functioning correctly.

884
www.mixtelematics.com

884
 885

FM200 Communicator Installation Checklist

1. Unit has been mounted properly.

a) Not close to air ducts, moving parts or areas with excessive heat or moisture.

b) Unit not twisted if mounted on an uneven surface.

c) The GPS antenna is mounted where least metal obstruction will occur.

d) The F3 line and S2 serial port is not connected to any external components.

e) The GPS and GSM antenna is secure and not bundled with any wiring harnesses.

f) Cables are tension free where the cable connectors plug into the unit.

g) The GSM antenna is mounted further than 20cm away from the human body under normal operating
conditions.

2. Unit has been connected to proper power, ignition and earth and wiring has been cut to the correct lengths.

3. All connections are secure, soldered and insulated.

4. Wiring harness has been insulated with insulation tape or sleeving and all wiring has been secured with clamps
or cable ties away from any sharp metal or moving objects

5. Upload ID to unit.

6. Upload Configuration to the vehicle insuring that the GSM is configured for S2 and the GPS for F3.

7. Set date and time.

8. GPS unit has been given approximately (15 minutes) after initial power up to download complete almanac (Did
not interrupt power during this time) and operation was verified with GPS diagnostic plug.

9. Calibrate speed and RPM inputs.

10. Perform a test drive with a reasonable duration, speed and distance. If possible check whether violations such
as excessive idling are recorded.

11. Download vehicle and check Tacho data to verify that all devices and events are recording correctly at all data
ranges.

12. Set odometer reading.

13. Perform download via GSM to verify that vehicle is downloading and GSM modem and SIM is functioning
correctly.

Declarations

885
www.mixtelematics.com

885
 886

This product conforms to the requirements of Directive 71/245/EEC, as last amended by Directive 95/54/
EC.

024000

It is possible for the GPS reception to be affected when certain frequencies are radiated close to the unit.

886
www.mixtelematics.com

886
 887
7.15.3 FM200 GPS Interface Installation Manual

© 2008 MiX Telematics | Updated 2008/05/07

Product Description
The GPS interface (X39-723-002-069) harness consists of two connector cables:

· A FM200 connector cable, and

· A GPS connector cable

The FM200 connector cable is wired to the FM200 as shown below. It enables the FM200 to be easily connected to a GPS
module that has a female DB9 connector as standard. For GPS modules that do not have appropriate connectors, you will need
the GPS connector cable.

Minimum GPS Requirements

Any GPS module chosen to work with the FM200 should conform to the following specification level to assure proper functioning.
A GPS module should:

· Output NMEA 0183 serial data @ 4800 baud, one stop bit

· Output a 10V voltage swing, for example: –5 to +5 Volts (V.24/RS232).

· Accept unregulated power (typically 12V or 24V)

Recommended GPS Modules

The following GPS modules have been verified to work with the FM200.

· GARMIN GPS 35/36 TracPak

· TRIMBLE Lassen SK-8

· GARMIN GPS III

· WISI AG10b

GARMIN GPS 35/36 pin-outs

GND Black + unscreened wires

Power Red wire

Signal White wire

Installation & Power Saving

To ensure that the GPS does not drain the vehicle battery, the GPS must be powered off the vehicle ignition, or alternatively from
the vehicle battery, but through a relay. The relay is then controlled by the FM200’s External Drive (brown & red wire). The
connections for this are:

Relay Connection Connects to

887
www.mixtelematics.com

887
 888

Pin 30 GPS-module’s power input.

Pin 85 FM200’s external drive output (brown & red wire).

Pin 86 Battery Voltage (typically 12V).

Pin 87 Battery Voltage (typically 12V).

Power-saving settings can be adjusted from the front-end software.

Note: The first time the FM200 detects GPS communication, the FM200 LED will quickly flash five times.

Diagnostics Plug

To verify that the GPS installation is successful and the system working correctly, use the FM Dealer Utility to prepare a GPS-
Diagnostic plug. Switch on ignition and insert the plug into the FM200. Multiple flashes from the FM200 will indicate successful
communication with the GPS. A beep every few seconds indicates successful messages (GGA, RMC etc). Double beeps indicate
successful satellite tracking.

Diagram

Please Note: You must use the FM200 connector cable, as GPS will not work without it.

888
www.mixtelematics.com

888
 889
7.15.4 FM200 Locator

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The Fleet Manager 200 Locator (FM200 Locator) is an on-board computer based on the stable and reliable platform of the FM200
Plus.

The FM200 Locator offers the extensive driver and vehicle management the FM200 Plus offers, and an internal GPS receiver,
where GPS information (such as the GPS location, GPS heading and GPS speed) can also be recorded.

Features

Location Management

GPS Data Recording Various information is recorded with every GPS point, such as Vehicle and Driver ID, Date and
time, Latitude and Longitude, Altitude, Heading, Velocity, Number of Satellite etc

Manage Locations Locations can be added showing customer, supplier, no go zones or any desired locations.

Route Planning Routes can be planned by entering stops, the planned time of start and the planned duration of
each stop. This can serve as daily job activity sheets for your drivers.

Reports and Graphs Various reports and graphs can display information such as locations visited, time of arrival /
delivery and no-go zones entered

Vehicle Management

Trip Data Recording For every journey the vehicle takes, the following information is recorded:

Date and Time, Distance or Hours, Speed or Hours, Engine Speed (RPM),Trip started / ended
time, Trip depart / arrive time, Driver Name & ID, Vehicle ID

Driving Violations The following standard violations are recorded:

Over Speeding, Over Revving, Green Band Driving (low and high), Harsh Braking, Harsh
Acceleration, Excessive Idling and Overtime Driving

889
www.mixtelematics.com

889
 890

Customised Events You can also define customised events, such as driver door opening, No-go zone entered,
hazard lights activated, refrigerator temperature exceeded

Second-to-Second (Tacho) The FM200 Locator records the status of all inputs (e.g. speed, RPM, brake lights) every
Data second, which provides valuable in-depth information for accident analysis.

Servicing and Licensing Reminders can be set when your vehicle’s next service is due or when your vehicle / driver
licence expire.

Driver Management

Immobiliser The FM200 Locator can be installed with an immobiliser function – the car will only start if a
driver, authorised to drive that vehicle, inserts his driver plug.

Driver Identification A driver tag can be used to identify the driver, and a default driver can be assigned to a vehicle.
This allows you to monitor who’s driving your vehicles and how.

Warning Buzzer A warning buzzer can be set to sound when driving violations or events take place.

Passive (Historical) Tracking

The FM200 Locator records GPS information, which can be reviewed after the trip has been downloaded. This can give the you
understanding of the movements of your vehicles / drivers, where they go, when and at what times they arrive and depart, length
of visits, which locations are visited most often or not enough.

The FM200 Locator can be programmed to record GPS information in intervals (e.g. every 5 minutes) or when the direction of the
vehicle changes more than a certain amount of degrees (e.g. 35°). Both values can be defined in the FM Software.

Location Management

890
www.mixtelematics.com

890
 891

The Fleet Manager Location Reports lets you determine how much time is spent by your vehicles at different locations, enabling
you to get a better understanding of what your vehicles and drivers do. Location reports include Driver, Vehicle and location trip
reports, a route plan report and variance reporting.

The route planner for planning the stops each driver should make, by entering stops, planned time of start, and planned duration
of each stop. This can serve as daily activity sheets for your drivers. With the return of the trip, you can check the planned stops
versus the actual stops, allowing you to see the route deviation.

Technical Information

8 configurable analogue The FM200 Locator analogue or digital inputs can be configured to monitor any device that
or digital inputs generates a change in voltage, e.g. seat belts, headlights, refrigeration units, emergency lights,
doors, PTO, UDS, trailer coupling etc.

3 auxiliary frequency input The FM200 Locator auxiliary frequency input can be configured to monitor any device that generates
a change in frequency e.g. temperature sensor, liquid flow measurement or as a pulse counter e.g.
electronic fuel consumption measurement (EDM)

A fourth auxiliary input (F3) is connected to the internal GPS receiver.

2 Auxiliary relay drive This can be used to switch a relay with a current consumption of up to 150 mA.

3 Serial interface (2x This can be connected to any TTL or RS232 serial device using the FM Serial cable (e.g. FM
RS232 and 1x TTL) Terminal).

Software
Fleet Manager Professional 9 provides the serious fleet operator with extensive fleet management tools to manage and report on
his fleet. The software enables you to manage vehicle, driver and passenger information, define and manage events to be
monitored, analyse fleet data and do extensive management reporting. In addition to the core software, Fleet Manager
Professional 9 also offers a set of extensions that allow additional monitoring and reporting on the fleet.

Our Internet Bureau Service, FM-Web, also supports the FM200 Locator.

891
www.mixtelematics.com

891
 892
7.15.4.1 FM200 Locator Installation Manual

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The FM200 Locator is based on the FM200 Plus and is fitted with an internal GPS receiver. All FM200 Plus functionally is
available on the FM200 Locator with the exception of the external use of the F3 line.

Installation
FM200 Locator

1. Installation details for the FM200 Locator are the same as for the FM200 Plus. These are detailed in the document “FM200
Plus Installation Manual”.

2. The FM200 Locator contains device drivers and a basic configuration to enable the internal GPS.

3. Refer to “FM200 Plus Installation Manual” for details on calibrating RPM and Speed and for setting Vehicle ID, Odometer and
Time.

4. The FM200 Locator F3 line is used internally by the GPS module and is not available for connecting an external device.

5. Refer to “FM200 Plus Installation Manual” for details on positioning and mounting the FM200 Locator.

6. When mounting the FM200 Locator on an uneven surface, ensure that the housing is not distorted

GPS Antenna

1. The GPS antenna must be mounted with a clear, unobstructed view of the sky.

2. For best results, place the antenna on a horizontal metal surface.

3. Where a metal surface is not available, mount the GPS antenna on the supplied metal plate, to improve reception.

4. When the antenna is mounted on a metal surface, it is best to isolate the antenna from the metal to avoid galvanic corrosion
between the metal surface and the antenna.

5. Connect the GPS antenna to the FM200 Locator by carefully inserting the connector into the round socket on the front panel of
the FM200 Locator.

6. Ensure that the GPS antenna connector is inserted all the way into the socket.

7. Do not force the antenna connector into the socket.

8. To prevent the disconnection of the GPS antenna, secure the antenna cable to the FM200 Locator main harness with a cable-
tie or insulation tape. Make sure that there is sufficient slack in the cable to prevent straining the connector when the main
harness is moved.

892
www.mixtelematics.com

892
 893

Configuring Vehicle Properties

1. The FM200 Locator is configured in the same way as the FM200 Plus.

2. Vehicle Properties of the FM200 Locator unit are specified in the Fleet Manager application software. This includes the
selection of devices connected to each input, and the events associated with data measured on those inputs.

3. More details can be found in the Fleet Manager application software documentation, or online help.

4. Using the Fleet Manager application software, configure the vehicle properties to show a GPS device connected on the F3 line.

5. The device’s power management option must be set to “Device will be powered by unit’s positive drive”.

Testing the Installation

1. The GPS receiver requires about 15 minutes to initialise before it can determine position. This initialisation process should not
be interrupted by disconnecting power or obstructing the antenna.

2. Format a GPS Diagnostic Plug, using the FM Dealer Utility.

3. Insert the GPS Diagnostic Plug into the code plug socket.

4. A single beep every 1 to 2 seconds indicates GPS information is being received by the FM200 Locator but the position could
not be determined. The position can be determined only after the GPS receiver has completed initialising.

5. A double beep every 3 seconds indicates the FM200 Locator is receiving GPS position data from the GPS receiver.

6. If the single beep sequence continues, after allowing time for initialisation to complete, the GPS antenna should be moved to a
better position. The beep sequence will change to a double beep when the antenna position is suitable.

Declarations

This product conforms to the requirements of Directive 71/245/EEC, as last amended by Directive 95/54/EC.

023570

893
www.mixtelematics.com

893
 894

Excessive electromagnetic interference applied at certain frequencies can affect GPS reception.

894
www.mixtelematics.com

894
 895
7.15.5 FM200 Plus

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The FM200 Plus is the ideal solution for Driver and Vehicle Management. In addition to recording the standard events, you can
also define and monitor additional customised events, such as the emergency lights, refrigeration units and trailer coupling.

The FM200 Plus is more advanced than the FM100 and offers standard recording of data, second-to-second (Tacho) data (used
for accident analysis) as well as additional custom events (e.g. headlights, driver door open).

Features

Trip Data Recording For every journey the vehicle takes, the following information is recorded:

Date and Time, Distance or Hours, Speed or Hours, Engine Speed (RPM),Trip started / ended
time, Trip depart / arrive time, Driver Name & ID, Vehicle ID

Driving Violations The following standard violations are recorded:

Over Speeding, Over Revving, Green Band Driving (low and high), Harsh Braking, Harsh
Acceleration, Excessive Idling and Overtime Driving

Customised Events You can also define customised events, such as driver door opening, No-go zone entered,
hazard lights activated, refrigerator temperature exceeded

Second-to-Second (Tacho) The FM200 Plus records the status of all inputs (e.g. speed, RPM, brake lights) every second,
Data which provides valuable in-depth information for accident analysis.

Servicing and Licensing Reminders can be set when your vehicle’s next service is due or when your vehicle / driver
licence expire.

Warning Buzzer A warning buzzer can be set to sound when driving violations or events take place.

Vehicle Immobilisation / Driver A driver tag can be used to identify the driver, and a default driver can be assigned to a vehicle.
Identification The FM200 Plus can also be installed with an immobiliser function – the car will only start if an
authorised driver inserts his driver tag.

On-board Memory (1 MB) - Up to 900+ trips (trip and event data) can be recorded – which caters for up to 30 days of
driving @ 30 trips per day

- 384 KB for trip and event data, 128 KB reserved for second-by-second (Tacho) data, and the
remaining are used by the operating system and device drivers

895
www.mixtelematics.com

895
 896

Technical Information

Operating voltage 9... 36 V Protection class IP 54

Auxiliary relay
Current consumption 25 mA max 150 mA (both)
drivers

Interrupter relay max. 25A Clock Component Real Time Clock

Memory 1 MB FLASH Indicator Integrated buzzer

Interface I2C for the connection of the

vehicle interface

8 configurable analogue The FM200 Plus analogue or digital inputs can be configured to monitor any device that generates a
or digital inputs change in voltage, e.g. seat belts, head lights, refrigeration units, emergency lights, brakes, doors,
PTO, UDS, trailer coupling, etc.

4 auxiliary frequency input The FM200 Plus auxiliary frequency input can be configured to monitor any device that generates a
change in frequency, e.g. temperature sensor, liquid flow measurement. Alternatively, this input can
be used as a pulse counter, e.g. electronic fuel consumption measurement (EDM). This input can
also be used to read low baud rate digital data (e.g. GPS)

2 Auxiliary relay drive This can be used to switch a relay with a current consumption of up to 150 mA.

3 Serial interface (2x This can be connected to any TTL or RS232 serial device using the FM Serial cable (e.g. FM
RS232 and 1x TTL) Terminal).

Data Downloading
Three alternatives are available for extracting data from an FM200 Plus unit:

1. Remote downloads (GSM/GPRS )

GSM can be used to automatically download data from your GSM equipped on-board computers at predefined time intervals.
The software can also be used to upload configuration and device drivers to off-site vehicles and to obtain a vehicle's current
status. GPRS allows you to have a dedicated connection between the vehicle and the office which can be used to actively track
your vehicles, download trip data and upload vehicle configuration. For more information please view the GPRS Questions and
Answers document.

2. DECT (yard)
Provided a DECT module has been connected and configured and a base station has been installed, DECT can be used over
a short distance of approximately 300 metres. This negates the need for the physical access to the vehicle required by the
code-plug downloading method and is intended for vehicles that return regularly to home base. These downloads are
scheduled and initiated by the DECT Downloader Software.

3. Code-plug (manual)
Choice of 96k or 256 k green plug. The code plug mechanism is the original means of extracting data from a vehicle. A plug is
inserted into the vehicle’s code-plug socket, and then inserted into a download module connected to a PC. The plug can store
900+ trips, including event and violation data (caters for up to 30 days of driving @ 30 trips per day).

Driver Management

896
www.mixtelematics.com

896
 897

Using the blue driver code-plug, you can define and control access to your vehicles. The optional starter-circuit interruption
(immobiliser) means that if a driver attempts to start a vehicle without authorization, the vehicle will not disarm, thereby improving
security, preventing unauthorized trips and saving you money at the same time.

Driver identification also means that you will always know who drove your vehicles and when. All vehicle trips will be associated
with a driver, and this will encourage your drivers to be more responsible and careful about their driving and use of company
vehicles.

The FM200 Plus improves your driver's driving style and reduces the potential for road accidents. When a user-defined event
violation occurs in a vehicle (e.g. over-speeding, harsh braking) the in-vehicle buzzer can sound to notify the driver instantly. The
drivers can then take immediate corrective action and avoid potentially fatal consequences.

Vehicle Management
You can reduce fleet operating costs by monitoring and managing critical vehicle event and fuel data. The FM200 Plus detects
and records standard and user-defined events, including over-speeding, over-revving, harsh braking, harsh acceleration and out
of green band driving. Reducing these events can significantly reduce the variable fleet operating costs associated with
unnecessary tyre, brake and engine wear, excessive fuel costs and high accident rates.

Accident Analysis

The FM200 Plus records second-to-second (Tacho) data which can be used for accident analysis. Interval (Tacho) Data is
second-to-second data which includes date, time, speed, RPM as well as the current status of the digital/analogue inputs. A
traditional tachometer records speed and RPM in graphical format on a paper disc, whereas the on-board computer records this
information electronically. This information can help you analyse accidents to give you an idea of what happened during the last
few seconds before the accident.

Accessories
The FM200 Plus is modular in design and can interface with a wide range of accessory products including fuel meters,
tachographs, hand held computers, and other products in the Fleet Manager range (e.g. FM Info, FM Terminal, FM Trailer Id,
etc.). The FM200 Plus supports the use of the black passenger code plug for identifying passengers.

Software
Fleet Manager Professional 9 provides the serious fleet operator with extensive fleet management tools to manage and report on
his fleet. The software enables you to manage vehicle, driver and passenger information, define and manage events to be
monitored, analyse fleet data and do extensive management reporting. In addition to the core software, Fleet Manager
Professional 9 also offers a set of extensions that allow additional monitoring and reporting on the fleet.

897
www.mixtelematics.com

897
 898
7.15.5.1 FM200 Plus User Manual

© 2008 MiX Telematics | Updated 2008/05/07

Installation
The Fleet Manager 200 Plus (FM200 Plus) On-Board-Computer should be installed by a suitably qualified person. Please consult
Fleet Manager 200 Plus Installation Manual on the Fleet Manager Software CD for installation details.

The FM200 Plus must be powered from a battery source. The signal wires should not exceed 30 meters.

Operation
The functioning of FM200 Plus is determined largely by the configuration specified within the Fleet Manager Software.

Armed / Disarmed Status

Armed status is indicated by one short flash of the red lamp, every two seconds. In some installations, the vehicle cannot be
started while in the armed mode, and must be disarmed as described below. The red lamp remains off while the FM200 Plus is
disarmed.

Driver Identification And Disarming Of The FM200 Plus

If driver identification is required before the trip can begin, the driver must insert the blue driver key into the Code Plug Socket. If
the driver is authorised to drive the vehicle, the FM200 Plus will beep twice briefly and the LED in the reader unit will be switched
off. The unit is now disarmed and will allow the vehicle to be started.

Data Transfer

Data stored in the FM200 Plus can be transferred by inserting the green vehicle plug into the Code Plug Socket. The FM200 Plus
beeps briefly before copying the stored data onto the Code Plug. During the transfer, the red lamp flickers rapidly. One short
beep indicates the completion of a successful transfer. The red lamp then resumes the normal armed mode flash rate of one
short flash every two seconds. An unsuccessful data transfer, is indicated by a long beep.

Trouble shooting

LED does not Flash No Voltage Check the voltage supply to FM200 Plus

The Fleet Manager 200 Plus can The blue driver key is not assigned to the Use the correct blue driver key or get the
not be enabled. vehicle. driver key assigned to the vehicle.

The Buzzer sounds when The driver registration was not done Register with your blue driver key.
turning on the ignition. or

The blue driver key is not released / Get your blue driver key released for the
configured for the vehicle. vehicle and register with it.

Beep and Flash Codes

The Fleet Manager (FM) 200 Plus was previously known as the FM200 Plus. The FM200 Plus status is indicated by audible and
visual signals. The following table shows the codes used to indicate the various states.

FM200 Plus Audible buzzer

Red Lamp on Code-plug socket

898
www.mixtelematics.com

898
 899

Signal sequence

CONDITION BEEP AND FLASH CODE DURATIONS

At Installation

No Beeps
Only Operating system
loaded
1s on. 1/8s off

No Beeps
Operating system and
device drivers loaded
1/2s on. 1/2s off

No Beeps
Normal ‘Armed Mode’
1/16 on. 2s off

Before a Trip

No beeps
Normal ‘Armed Mode’
1/16s on. 2s off

7 short beeps
Notification - 'Private Mode'
enabled
Lamp off

1/4s on. 3/4s off

Driver identification
requested
Lamp off

2 x 1/8s beeps
Driver authorised to drive
vehicle
Lamp off

1 x 1/2s beep
Driver not authorised to
drive vehicle
1/16s on. 2s off

3 x 1/8s beeps
FM200 Plus memory 80% -
95% full.
Lamp off

899
www.mixtelematics.com

899
 900

3 x 1/2s beeps
FM200 Plus memory 95% -
100% full.
Lamp off

During Calibration

1s on. 1s off.
Speed or RPM calibration
plug inserted (Violet Plug)
Flashes

3 x 1/8s beeps
Setting date and time (Blue
Plug)
Unchanged
------ unchanged -------

During a Trip

No beeps
Start of Trip
Flashing Stops

No Beeps
While Driving
Lamp off

Continuous beep
Event alarm
Lamp off

1 x 1/8s beep
Start of sub trip
Lamp off

1 x 1/8s beep
End of trip
1/16s on. 2s off

During Data Transfer

1 x 1/2s beep
Incorrect vehicle plug
inserted.
1/16s on.2s off.

900
www.mixtelematics.com

900
 901

Correct vehicle plug ------- data transfer ----- 1 x 1/8s beep

inserted – Successful
download of trip data. Lamp flickers

Correct vehicle plug ------- data transfer ----- 2 x 1/8s beeps

inserted – Successful
transfer of configuration. Lamp flickers

Correct vehicle plug ----- data transfer ---- 1 x 1/2s beep

inserted – Unsuccessful
data transfer. Lamp flickers

Green plug memory full.

1 x 5s beep
FM200 Plus has not
completed transfer of trip
1/16s on. 2s off.
data.

901
www.mixtelematics.com

901
 902
7.15.5.2 FM200 Plus Questions and Answers

© 2008 MiX Telematics | Updated 2008/05/07

The Fleet Manager (FM) 200 Plus was previously known as the FM200 Plus.

What is the Fleet Manager (FM) 200 Plus?

The FM200 Plus on-board computer is the successor to the powerful FM200 unit. Built on the same reliable platform, the FM200
Plus unit provides all of the functionality of the FM 200 unit, is fully backward compatible, and caters for expansion to enable new,
more powerful applications in the future.

The FM200 Plus unit replaces the FM200 unit. It will not be sold in addition to the FM200 unit. The production of the FM 200 unit
will stop when the FM200 Plus is released.

What software will support the FM200 Plus ?

The following previous versions of Fleet Manager software are capable of supporting the FM200 Plus unit:

· Fleet Manager 2000 Second Edition (version 5.00.0003)

· Fleet Manager 2001 SR2 (version 6.20.0023)

· Fleet Manager 2002 Professional (version 7.00.000)

In order for the software mentioned above to support the FM200 Plus unit, you will have to install the updates contained on the
FM200 Plus Update CD (excluding Fleet Manager Professional SR1).

In these versions of the Fleet Manager software, the unit type will still be treated as an FM200 unit, although you will be able
upload new FM200 Plus device drivers using the updated FM Dealer utility. The event configuration should initially be uploaded
to the unit using a green code-plug formatted with the new FM Dealer utility. Once the unit has been configured for the first
time, you can use the updated versions of the GSM or DECT software suites to upload and download data as required.

· Fleet Manager 2002 Professional SR1

Fleet Manager 2002 Professional SR1 supports all the new features of the FM200 Plus unit, but displays it as a FM200 Plus.

If you have any other release of Fleet Manager software not listed above, you must upgrade to the next supported version of
software.

The Fleet Manager Professional 9 release supports the FM200 Plus as a new unit type, and also provides full support for all the
new features of the FM200 Plus.

What new features does the FM200 Plus support?

Initially, when you install and use the updated software components (contained on the FM200 Plus Update CD) together with
older versions of the software, the functionality of the FM200 Plus unit will be identical to that of an FM 200 unit.

With Fleet Manager 2002 Professional SR1 or higher, you will be able to take advantage of the new features of the FM200 Plus
unit by uploading new firmware (device drivers) to the units. With these device drivers you will be able to use more of the FM200
Plus’s new hardware features, including the extra inputs, outputs and serial ports.

If I want to replace an FM200 unit in a vehicle with an FM200 Plus unit, what installation
procedure must I follow?
If you have an existing customer that wants to upgrade their unit to an FM200 Plus, the process is quite easy. Simply disconnect
the FM200 unit from its harness, and connect the FM200 Plus unit to the old FM200 harness. Then set-up and configure the
FM200 Plus unit in the same way that you set up the FM200 unit. You must remember to run the Swap Unit function in the Fleet
Manager software. Note: While it is possible to connect an FM200 Plus onto an FM200 harness, you cannot connect an FM200

902
www.mixtelematics.com

902
 903

unit onto an FM200 Plus harness.

Can an FM200 Plus harness be used with an FM200 and vice versa?
The FM200 Plus can be used with an FM200 harness, but the FM200 cannot be used with an FM200 Plus harness.

Do I still need to use the FM Splitter when connecting an FM200 Plus to a serial device?
Yes, but in future you will have the option of using the new FM200 Plus serial cable for connecting serial devices to the FM200
Plus.

Do I still need to use the FM200 GPS Interface cable when connecting an FM200 Plus to a
GPS receiver?
No. Although you may still use the GPS Interface cable, you do not have to. With the FM200 Plus, you can connect a GPS
module directly to the unit using the purple wire. You need to set the GPS jumper on the FM200 Plus board, as follows:

Can the FM200 do anything that the FM200 Plus can’t do?
No. The FM200 Plus can do everything that the FM200 does, and more.

Where can I get more technical information on the FM200 Plus?

The FM200 Plus User Manual provides detailed technical information.

903
www.mixtelematics.com

903
 904
7.15.5.3 FM200 Plus Quick Start Guide

© 2008 MiX Telematics | Updated 2008/05/07

Overview
Explains step-by-step, how to setup and install a fleet of vehicles with FM200 Plus units.

· Steps marked OFF-SITE should be undertaken prior to installing the units into the customer’s vehicles and can be undertaken
away from the customer’s premises.

· Steps marked ON-SITE should be undertaken at the customer’s premises.

Check list

Check Requirements off-site

1. Build Bench Tester off-site

2. Install Software off-site

3. Prepare DDX (Device Driver) Plug off-site

4. Prepare Installer Plug off-site

5. Prepare Vehicle Plugs off-site

6. Connect Unit off-site

7. Configure Unit off-site

8. Test Unit off-site

9. Prepare Driver Plugs off-site

904
www.mixtelematics.com

904
 905

10. Backup Database off-site

11. Install Software on-site

12. Install Unit on-site

13. Final Test on-site

Requirements Checklist

Check Requirements off-site

1. Build Bench Tester off-site

2. Install Software off-site

3. Prepare DDX (Device Driver) Plug off-site

4. Prepare Installer Plug off-site

5. Prepare Vehicle Plugs off-site

6. Connect Unit off-site

7. Configure Unit off-site

905
www.mixtelematics.com

905
 906

8. Test Unit off-site

9. Prepare Driver Plugs off-site

10. Backup Database off-site

11. Install Software on-site

12. Install Unit on-site

13. Final Test on-site

To build a bench tester

· FM200 Plus Wiring Harness (X39.723-002-081)

· FM200 Plus Code Plug Harness (X39.723-002-005)

· 12V DC transformer or battery

· Approx 0.5m red, 0.5m black and 0.5m brown electrical wire

906
www.mixtelematics.com

906
 907

· Switch

· Side cutters

· Soldering iron & solder

· Electrical tape

To install units in vehicles

· Other tools may be required to install the units into the customer’s vehicles

· Vehicle specific tools and/or sensors may be required

· Read Document FM200 Plus Installation Manual

FM200 Plus Kit/s (X10.723-002-015) - 1 per vehicle

· Unit

· Wiring Harness

· Code-Plug Harness

· FM200 Plus User Manual

Code Plugs

· 256 KB Green code-plug (X39.723-002-033) for device drivers

· 96KB Green code-plug/s (X39.723-002-057) - 1 per vehicle

· Blue Driver ID code-plug - 1 per driver & 1 for installer

· FM calibration Set (X39.723-002-028)

Office equipment

· Suitable Personal Computer (see requirements on back of FM Office CD)

· FM Download Module (X39.723-002-009)

· FM Office CD (X39.723-002-079)

· FM Upgrade-Plus Package/s to cover number of vehicles

Vehicle information (for each vehicle)

· Unique description

· Registration number

· Odometer reading

Driver information (for each driver)

· Name

907
www.mixtelematics.com

907
 908

· Employee number

· List of vehicles he/she is allowed to drive

1. Build Bench Tester

· NB! Read FM200 Plus Installation Manual

· DO NOT Connect FM200 Plus unit to wiring harness at this stage

· Connect the code plug harness to the FM200 Plus wiring harness

· Connect the 12V DC transformer/battery positive to red (BATT+) wire in FM200 Plus wiring harness

· Connect the transformer/battery positive to black (IGN) wire through switch

· Connect the transformer/battery negative to brown (GND) wire

2. Install Software

NB! Read Fleet Manager Installation Manual

· Install Fleet Manager Professional 9 by inserting the Fleet Manager Office CD and select "Install Fleet Manager Professional 9"

· Run Fleet Manager Professional 9

· Register software using FM Upgrade-Plus package/s and web site (www.upgrade-plus.com)

· Install FM Dealer Utility by inserting the Fleet Manager Office CD and select "Install Dealer Utility"

· Connect the download module to the personal computer

3. Prepare Device Driver code-plug

· NB! Read FM Dealer Utility User Manual

· Run FM Dealer Utility

· Insert the 256kb green code plug into download module

· Click the Code Plug menu, then click Format Plug, then Device Drivers, then FM200 Plus

908
www.mixtelematics.com

908
 909

· Wait for the code plug to be formatted

· Click the Code Plug menu, then click Load Device Drivers, then FM200 Plus Device Drivers

· Click Load

· Wait for device drivers to be loaded onto plug

· Label the plug clearly as a device driver plug

4. Prepare Installer Plug

Run FM Professional Software

· Insert a blue driver ID code plug into the download module

· Click the Code Plug menu, then click Initialise Plug, then Driver Plug

· Click next, then select Installer from the list

· Click next, then click Finish

· Label the plug clearly as an Installer plug

5. Prepare Vehicle Specific Code Plug/s

Create a vehicle record in the database

· Click the Add Vehicle tool button on the main toolbar

· Enter the vehicle description and registration number

· Click OK, then click OK again

· When prompted to update the vehicle code plug, click No

Initialise the vehicle specific code plug

· Insert a 96kb green code plug into the download module

· Click the Code Plug menu, then click Initialise Plug, then Vehicle Plug

· Click next, then select the vehicle from the list

· Click next, then ensure that Update Event Configuration and Update Odometer are checked.

· Enter the vehicle’s odometer reading in the space provided

· Click next, then click Finish

· Label the plug clearly with the vehicle’s unique description or registration number

909
www.mixtelematics.com

909
 910

6. Connect Unit

· Label the FM200 Plus unit clearly with the vehicle’s unique description and registration number

· Connect the unit to the bench tester

· Observe the unit LED behaviour and consult the FM200 Plus User Manual

· The LED should indicate that only the operating system is loaded

7. Configure Unit

Upload device drivers

· Insert the 256kb green device driver code plug configured in Step 3 into the unit’s code plug socket

· Wait for the device drivers to be loaded

· Listen carefully for any long (1 sec) beep indicating that an error has occurred

· If an error occurs, remove the code plug and re-insert it and try again

· The unit will reset and beep twice once the device drivers have been loaded successfully

· The unit LED should now indicate that device drivers are loaded

Upload configuration

· Insert the 96kb green vehicle specific code plug configured in Step 3 into the unit’s code plug socket

· Wait for the configuration to be loaded

· Listen carefully for any long (1 sec) beep indicating that an error has occurred

· If an error occurs, re-initialise the code plug by following the instructions in step 5 and try again

· The unit will beep twice once the configuration has been loaded successfully

· The unit LED should now indicate that the configuration has been loaded

Set date/time

· Insert the Installer code plug configured in Step 4 into the download module

· Click the Code Plug menu, then click Set Date/Time

· Enter the current date/time then click Finish (note, the software defaults to 10 min in the future, ensure you overwrite this)

· Insert the code plug into the unit’s code plug socket

· The unit will beep three times indicating that the date/time has been set

910
www.mixtelematics.com

910
 911

8. Test Unit

Do a bench test trip

· Switch on the ignition switch on the bench tester

· Wait approximately 60 seconds, then switch off the ignition switch

Download data

· Insert the 96kb green vehicle specific code plug configured in Step 3 into the unit’s code plug socket

· Wait for the trip data to be downloaded onto the code plug

· Insert the code plug into the download module

· Click on the Code Plug menu, then click Download All Trips

· Once the data has been downloaded and processed, ensure that the View Activity Timeline checkbox is checked, then click
Finish

· Once the Activity Timeline window has been opened, click the Go button on the toolbar

· Check that the test trip is displayed in the timeline

Repeat Step 5 through Step 8 for each vehicle

9. Prepare Driver Plugs

Create a driver record in the database

· Click the Add Driver tool button on the main toolbar

· Enter the driver name and employee number

· Click OK, then click on the Vehicle Access tab

· Check the vehicles that the driver is allowed to drive, then click OK

· When the software prompts to update the vehicle code plug, click No

Initialise the Driver specific code plug

· Insert a blue code plug into the download module

· Click on the Code Plug menu, then click Initialise Plug, then Driver Plug

· Click next, then select the driver from the list

· Click next, then click Finish

· Label the plug clearly with the driver’s name

Repeat Step 9 for each driver

911
www.mixtelematics.com

911
 912

10. Backup Database

· NB! Read Fleet Manager Professional 9 Administrator

· Run the FM Admin Utility

· Double-click the Backup icon

· Click Browse and select a suitable path and filename for the backup file

· Click OK and wait for the backup to complete

· Copy the backup file onto suitable removable media e.g. CD-R to take to the customer’s site

11. Install Software (on-site)

Copy the database backup file created in Step 10 into a folder on the hard disk of the customer’s computer

· Install Fleet Manager Professional 9 onto customer’s computer

· When prompted to create a database, choose to create a new database from a backup

· Select the backup file located on the hard disk. DO NOT attempt to restore the database from the removable media, this may
fail

· Install FM Dealer Utility onto the customer’s computer if required

· Run the FM Dealer Utility

· Click on the Settings menu, then click Password

· Leave the Current Password field blank

· Enter a suitable password in the fields provided and click OK

· Connect download module to personal computer

12. Install Unit (on-site)

NB! Read FM200 Plus Installation Manual

· Install the FM200 Plus unit into the vehicle

· Calibrate the unit’s speed and RPM inputs using the calibration code plugs

· When calibrating the unit, use the Installer code plug configured in Step 4 to identify yourself

· The speed input should be calibrated over a distance of at least 1km when manually calibrated

13. Final Test (on-site)

912
www.mixtelematics.com

912
 913

Do a test trip

· After calibrating the unit, wait for the unit to re-arm before test driving

· Do a test trip of more than 1 km

Download data

· Insert the 96kb green vehicle specific code plug configured in step 3 into the unit’s code plug socket

· Wait for the trip data to be downloaded onto the code plug

· Go to the personal computer and insert the code plug into the download module

· Click on the Code Plug menu, then click Download All Trips

· Once the data has been downloaded and processed, ensure that the View Activity Timeline checkbox is checked, then click
Finish

· Once the Activity Timeline window has been opened, click the Go button on the toolbar

· Check that the test trip is displayed in the timeline

Repeat Step 12 through Step 13 for each vehicle

913
www.mixtelematics.com

913
 914
7.15.5.4 FM200 Plus Installation Manual

© 2008 MiX Telematics | Updated 2008/06/11

Overview
This document covers the following topics:

· Introduction

· Safety Procedures

· Before Installation

· During Installation

· After Installation

· During Operation

· Installation

· Installation Requirements

· Summary of Installation Steps

· FM200 Plus Harness Installation

· Starter Interruption

· Code-plug Socket Installation

· Positioning the FM200 Plus Unit

· Signal Inputs

· Frequency Jumper Input Selection

· Serial Communication

· Loading Device Drivers

· Setting the real time clock

· Speed and RPM calibration

· Testing Installation

· Troubleshooting

· Maintenance

· FM200 Plus Specifications

· Declarations

· Restrictions

914
www.mixtelematics.com

914
 915

· FM Part Numbers

Introduction
System Overview

The Fleet Manager 200 Plus (FM200 Plus) is an on-board-computer for use in vehicles and working machines. The system is
designed to record a wide range of vehicle and trip information, including vehicle speed, engine speed, engine temperature, fuel
consumption, and trip start and end times. The FM200 Plus interfaces directly with a large selection of transducers that enable
the recording of data, such as vehicle position, fuel consumption, and vehicle loading.

The FM200 Plus unit is used in conjunction with the Fleet Manager application software. This software facilitates the
management of vehicle, driver and passenger information, definition and management of events to be monitored by vehicle units,
recording of servicing details, analysis of fleet data and extensive management reporting.

The primary method of communicating with the FM200 Plus unit is via the green Vehicle Plug. The plug is used to extract data
from the FM200 Plus unit and transfer it to a Personal Computer, where it can be processed and analysed by the Fleet Manager
application software. Various modems can be connected to the FM200 Plus to facilitate wireless communication with the vehicle
unit.

Vehicle drivers are identified by means of a driver-specific blue plug; identification can be enforced by interrupting the vehicle’s
starter circuit.

Analogue/Digital Inputs

The FM200 Plus is equipped with eight analogue/digital inputs (I1-I8), which can be used to monitor either digital or analogue
signals. The eighth Analogue/Digital input (I8) is shared with the fourth frequency input (F4). Input signal voltage range and
resolution are selectable from the Fleet Manager software. For digital type input signals, switching thresholds can be defined in
the software, which, when crossed, trigger an event that records the specified data. Please refer to "Specifications" for more
information.

Frequency Inputs

The FM200 Plus has four frequency inputs, which can be used to record frequency type signals. The fourth frequency input (F4)
is shared with the eighth Analogue/Digital input (I8). Provision is made for a wide range of signal types. Please refer to the
“Frequency Input Jumper Selection” section of this document for more details.

System Requirements

The FM200 Plus is designed for use in vehicles, special vehicles and working machines with a 12 or 24 volt DC battery system.
The Fleet Manager application software is required to complete the installation process.

Safety
Before installation

Installer Requirements:

· Installation should only be undertaken by a vehicle technician with comprehensive occupation-specific knowledge and who has
complete command of the actions required by the occupation.

· Installation by an unqualified technician may adversely affect the operating reliability of the vehicle and could endanger other
road users.

· A basic knowledge of vehicle electrical and mechanical systems is required to successfully install the Fleet Manager 200 Plus
system.

· The system should only be installed by a suitably qualified vehicle technician with a basic knowledge of the operation of
computers.

915
www.mixtelematics.com

915
 916

· Installation technicians should attend an FM training course to acquire the skills needed for installation, configuration and
operation of the Fleet Manager system.

· Installers should consult the vehicle manufacturer’s documentation for the specific vehicle make and model prior to
undertaking an installation.

· Installers should pay particular attention to the location of fuel systems, hydraulic systems, compressed air systems and other
electrical and mechanical systems that may have a bearing on the installation.

· Installers should pay attention to any changes to the vehicle’s systems or settings, which should be noted prior to the
installation.

· Installers should refrain from smoking and the use of naked flames, which could cause a fire in or near the vehicle.

Tools:

· Standard technical equipment and appropriate tools for use with vehicles are required to install the Fleet Manager 200 Plus
system.

· Vehicle-specific tools may be required for the removal of consoles and covers.

Secure the workplace:

· Remove the ignition key from the vehicle’s ignition lock.

· Ensure that the vehicle’s engine cannot be unintentionally started during the installation.

· Record all data stored in the volatile memory of the vehicle’s systems to ensure that such data can be restored.

· When the negative terminal of the battery is disconnected, all volatile memory will be lost. Please ensure that such information
is recorded prior to disconnection so that systems can be reconfigured correctly.

· Short-circuiting the vehicle’s electrical system may result in fire, explosion of the battery and/or damage to other electrical
systems.

· The negative terminal of the vehicle’s battery should be disconnected before commencing installation. If the vehicle has
additional batteries, it may be necessary to disconnect the negative terminals of these batteries too.

During installation

· Should it be necessary to remove seats, covers or other components, care should be taken to avoid accidental damage and/or
disconnection of cables.

· All components should be checked for damage prior to being installed into the vehicle.

· For small installation openings, a drill should be used.

· For larger openings, a conical milling cutter, compass saw or file should be used.

· All rough edges should be trimmed.

· Careful attention must be paid to the manufacturer’s safety regulations for all tools used.

· Oils and fuels must be collected in appropriate containers and disposed of in accordance with the law.

Positioning of product components:

· Installers should ensure that the components of the product do not influence or hamper the functioning of the vehicle’s
systems.

916
www.mixtelematics.com

916
 917

· Care should be taken to ensure that the product’s components are not damaged during installation.

· Ensure that sufficient space is available for all components of the product prior to commencing the installation.

· Please pay attention to the routing of cables and wiring.

· Do not install the product in or near the location of mechanical or electrical airbags.

· Do not drill into supporting or stabilising braces or beams.

Installation of Wiring:

· Note the product’s wire gauge.

· If the wire gauge is reduced, current density increases which may cause the wiring to overheat.

· Cables should be routed in existing channels and should not be routed parallel to ignition cables or other cables subject to high
current.

· Cables should be fixed with cable-ties or adhesive tape.

· Do not route cables over moving parts.

· Do not fix cables on the steering column.

· Ensure that the cables are not exposed to pulling, pressure or shearing deformation.

· If the cables are routed through drilled holes, rubber grommets or similar protection should be used.

· Suitable cable-strippers should be used to strip insulating material from cables and cable-strippers should be adjusted to avoid
damaging or separating the wire strands.

· Cables should only be connected using solder or suitable crimping lugs.

· A proper crimping tool should be used on all crimping lugs.

· Careful attention must be paid to the manufacturer’s safety regulations for all tools used.

· Insulate all exposed wires to prevent short-circuits.

· Connections to vehicle power supply must be installed with a fuse or current limiting device.

· Be aware that short-circuiting may be caused by faulty connections and crushed or damaged cables.

· Short-circuiting the vehicle’s electrical system may result in fire, explosion of the battery and/or damage to other electrical
systems. To prevent this, all connections carrying current must be soldered and insulated correctly. Other connections such as
the speed signal, RPM signal, brake light or clutch switch can be made with crimping lugs.

· Incorrect connections can lead to short circuits. Connections should only be made in accordance with the vehicle’s wiring
diagram.

· Current and voltage should be measured with a multi-meter or diode test lamp.

· The use of inadequate test equipment may result in the damage to control devices or other electrical systems.

After Installation

· Reconnect the vehicle’s ground cable to the negative terminal of the battery.

917
www.mixtelematics.com

917
 918

· Re-configure the values in the volatile memory of all systems.

· Check all vehicle functions.

· Explain the functions of the FM200 Plus system to the customer and give the customer the User Manual.

During Operation

· The product must be used in accordance with operating instructions.

· Failure to use the product as directed might result in personal injury, material damage and/or damage to the environment.

Installation
Installation Requirements

Please note the requirements specified in the “Safety” section of this document.

Summary of Installation Steps

View print version

Step Action Software Tools Related Documents

1 Install harness None -

2 Install code plug socket None -

3 Connect power and signal inputs None -

4 Format Vehicle Plug FM Dealer Utility FM Dealer Utility User Manual

5 Initialise Vehicle Plug FM Dealer Utility FM Dealer Utility User Manual

Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

6 Load device drivers FM Dealer Utility FM Dealer Utility User Manual

FM200 Plus Beep and Flash Codes

7 Set Vehicle ID on unit FM Dealer Utility FM Dealer Utility User Manual

Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

8 Create new vehicle and define Fleet Manager Application Software Fleet Manager Application Software Help &
properties Docs

9 Load vehicle configuration Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

10 Initialise Driver ID plug FM Dealer Utility FM Dealer Utility User Manual

918
www.mixtelematics.com

918
 919

Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

11 Set FM200 Plus date and time FM Dealer Utility FM Dealer Utility User Manual

Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

12 Calibrate Speed and RPM inputs FM Dealer Utility FM Dealer Utility User Manual

13 Test Installation Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

Note: Steps 4, 5 & 6 can be performed in one operation using the FM Dealer Utility.

FM200 Plus Harness Installation

Please read the “Safety” section, of this document, before installing the vehicle harness.

Connect the FM200 Plus harness wires according to the following table:

· Connect to vehicle battery

J1-12 Red BATT+ Battery Power
· Must be protected with a 7.5 amp fuse

· Connect directly to vehicle ground

J1-13 Brown GND Ground
· Do not tap into an existing ground wire carrying high
current

· Connect to vehicle ignition switch

J1-1 Black IGN Ignition
· Must be protected with a 7.5 amp fuse

· Vehicle speed signal connected here

J1-19 Blue/White F1 Frequency Input 1 · Refer to “Frequency Input Jumper Selection” if signal is
not detected by FM200 Plus..

· Connect TCO to only F1 input

· Engine speed signal (RPM) connected here

J1-20 Green F2 Frequency Input 2
· Refer to “Frequency Input Jumper Selection” if signal is
not detected by FM200 Plus

· Connect GPS to only F3 input

· Move F3 jumper to GPS position, if GPS is connected

J1-21 Violet F3 Frequency Input 3 without using “FM200-GPS Interface Cable”

· Refer to “Frequency Input Jumper Selection” if signal is

not detected by FM200 Plus

919
www.mixtelematics.com

919
 920

J1-5 White/Violet I1 Digital/Analog Input 1 · Maximum signal voltage = 35V

J1-6 White/Red I2 Digital/Analog Input 2 · Do not connect signals from inductive sources such as
relay coils
White/ · Refer to “Frequency Input Jumper Selection” if signal is
J1-3 I3 Digital/Analog Input 3
Green not detected by FM200 Plus

White/
J1-4 I4 Digital/Analog Input 4
Yellow

J1-17 White/Black I5 Digital/Analog Input 5

J1-16 White/Blue I6 Digital/Analog Input 6

White/
J1-15 I7 Digital/Analog Input 7
Brown

Digital/Analog Input 8
J1-14 White I8/F4
Frequency Input 4

· Supplies power to a speed sensor

· Output voltage typically 11V

J1-18 Black White VSPD Speed Sender Power
· Load current must not exceed 35mA

· Output controlled by FM200 Plus and selected in

Vehicle Properties

· Connect the ground side of an external relay coil here

J1-22 Brown/Red EXT DRIVE 1 Relay Drive 1 · Relay operation is controlled by the FM200 Plus and is
specified in Vehicle Properties

· Coil current must not exceed 150mA

· Connect the ground side of an external relay coil here

J1-11 Brown/Black EXT DRIVE 2 Relay Drive 2 · Relay operation is controlled by the FM200 Plus and is
specified in Vehicle Properties

· Coil current must not exceed 150mA

· Connects to ignition switch side of starter circuit, if

starter interruption is required
J3 Black IMM1A Starter interruption
· Do not interrupt high current side of starter circuit

J4 Black IMM1B Starter interruption · Connect to ignition switch side of starter circuit, if starter
interruption is required

920
www.mixtelematics.com

920
 921

J1-2 Black GND Code Plug Ground · Connected directly to code plug socket connector.

J1-8 Green CPDATA Code Plug Data · No additional connection required

J1-9 Red CPPOWER Code Plug Power

J1-10 White LEDOUT Code Plug Socket LED

· Connected internally
J1-7 Brown BUZ Buzzer Power
· No additional connection required

Starter Interruption
The FM200 Plus has an internal relay intended exclusively for the interruption of the vehicle’s starter circuit.

Connect the two starter interruption wires to the corresponding terminals on the back of the vehicle unit. Cut the wire from the
ignition lock to the starter relay and solder the starter interruption wires from the FM200 Plus unit onto the ends of the wires from
the starter circuit. These wires can be connected either way.

Note: The internal relay is intended only for interruption of the low current starter circuit. This relay should not be used to interrupt
the fuel pump or any other component of the vehicle’s electrical system. For high current starter applications, an additional relay
will be required.

Code Plug Socket Installation

Note: Please follow the instructions regarding the positioning of product components as contained in the “Safety” section of this
document.

• The Code Plug Socket must be installed inside the passenger compartment or the driver cabin to protect it from possible
damage by water or other environmental factors.

• The Code Plug Socket should not be installed in or near the ventilation or heating systems, which may cause it to overheat.

• The Code Plug Socket should be installed in a position where it will not be subjected to pressure, impact or excessive vibration.

• Select the installation position carefully before proceeding with the installation.

• Mark and drill or cut the required hole.

• Remove the mounting clip from the socket.

• Remove the protective film from the adhesive surface of the foam ring and press it firmly against the back of the interface.

• Insert the socket into the mounting hole and slide the mounting clip into position.

921
www.mixtelematics.com

921
 922

Hole size = 13/16” - 20 mm

Positioning the FM200 Plus Unit

Note: Please follow the instructions regarding the positioning of product components as contained in the “Safety” section of this
document.

· The FM200 Plus must be installed inside the passenger compartment or the driver cabin to protect it from possible damage by
water or other environmental factors.

· The FM200 Plus should not be installed in or near the ventilation or heating systems, which may cause it to overheat.

· The FM200 Plus should be installed in a position where it will not be subjected to pressure, impact or excessive vibration.

· Select the installation position carefully before proceeding with the installation.

· Mark and drill the required holes.

· Route cables from the unit to the appropriate senders within the vehicle. Additional information can be found in the “Harness
Installation” section of this document.

· After connecting the system components and performing a system test, mount the vehicle unit securely, making use of the
optional metal armoured housing if required. The armoured housing is available as a spare part and is used to protect against
tampering.

Signal Inputs
Analogue/Digital Inputs

The FM200 Plus is equipped with eight analogue/digital inputs (I1-I8), which can be used to monitor either digital or analogue
signals. The eighth Analogue/Digital input (I8) is shared with the fourth frequency input (F4). Input signal voltage range and
resolution is selectable from the Fleet Manager software. For digital type input signals, switching thresholds can be defined, in the
software, which, when crossed, trigger an event that records the specified data. Please refer to the “Specifications” and “Harness
Installation” sections of this document for more details.

Frequency Inputs

The FM200 Plus has four frequency inputs that can be used to record frequency type signals. The fourth frequency input (F4) is
shared with the eighth Analogue/Digital input (I8). Provision is made for a wide range of signal types. Please refer to the “
Frequency Input Jumper Selection”, “Harness Installation” and “Specifications” sections of this document for more details.

Frequency Input Jumper Selection

The FM200 Plus can accept a large variety of input signal types. To accommodate the many possibilities, each frequency input
(F1/SPD, F2/RPM, F3 and F4) is provided with a jumper for selecting the appropriate signal range. These jumpers are located

922
www.mixtelematics.com

922
 923

inside the FM200 Plus as shown below.

For most installations, the default settings will be correct. If the FM200 Plus does not correctly detect the input signal, the
following table should be consulted to establish the applicable setting. If the signal type is unknown, try the options in the order
shown below, starting from the top. The table shows the jumper position for each signal type. Each jumper position can be
applied to each of the four frequency inputs. The last row in the table shows the F3 jumper position when a GPS is connected. A
summary of this table is provided inside the lid of each FM200 Plus.

Jumper Signal Symbol Input Details When to Select

Positio Range
n

1 • AC coupled • Factory default setting

• Signal peak-to-peak voltage greater • Required when a FM TCO Interface is

than 0.5 volts connected to F1/Speed input

• Lower input impedance • Equivalent to FM200

• High sensitivity • Not recommended for noisy signals

2 • AC coupled • Large Noisy signals – improved noise

immunity
• Signal peak-to-peak voltage greater
than 4 volts • Signals with high source impedance

• Higher input impedance

• Signal max offset voltage -32V to

+32V

3 • DC coupled • Noisy TTL signals – improved noise

immunity
• Signal switches between 0 and > 5
volts • Larger TTL signals

• Higher input impedance

4 • DC coupled • Small TTL signals

• Signal switches between 0 and < 5 • Signal may be degraded due to low input
volts impedance.

• Lowest input impedance

• High sensitivity

923
www.mixtelematics.com

923
 924

GPS • DC coupled • Move F3 jumper to GPS position when a

GPS is connected to F3 without a FM200-
• Reduced input impedance GPS Interface Cable

• Suitable only for TTL/CMOS type • Leave F3 Jumper in default position when
signals GPS is connected to F3 via a FM200-GPS
Interface Cable

Power Outputs
External Relay Drives

• The FM200 Plus has two external relay drive outputs (Relay Drive 1 & 2), which are suitable for controlling external relays.

• These outputs are controlled by the FM200 Plus and are configured in Vehicle Properties of the Fleet Manager application
software.

• The Relay Drive Outputs connect to the ground side of an external relay.

• The maximum current of the external relay is limited to 150mA.

• Please refer to the “Specifications” and “Harness Installation” sections of this document for more details.

Speed Sender Power (VSPD)

• A nominal 11 Volt DC supply is provided specifically for powering a speed sensor requiring external power.

• VSPD output is internally current limited. Refer to the “FM200 Plus Specifications” section of this document.

• This output is controlled by the FM200 Plus and is configured in Vehicle Properties of the Fleet Manager application software.

Positive Drive

• The Positive Drive output supplies power to FM200 Plus accessories.

• This output is controlled by the FM200 Plus and is configured in Vehicle Properties of the Fleet Manager application software.

• Access to this output is via the FM200 Plus Serial Cable.

• Refer to the “FM200 Plus Specifications” section of this document.

Serial Communication

• The FM200 Plus is equipped with one TTL (S1) and two RS232 (S2 & S3) serial ports.

• The FM200 Plus Serial Cable is required to connect to these ports.

• Please refer to the “Specifications” section of this document and the FM200 Plus Serial Cable documentation for more details.

Loading Device Drivers

• The FM200 Plus is supplied with only the Operating System loaded.

• Before the unit can be configured, the latest version of FM200 Plus Device Drivers must be loaded.

924
www.mixtelematics.com

924
 925

• The latest Device Drivers are contained in the latest version of the FM Dealer Utility, which can be downloaded from http://www.
mixtelematics.com

• Load Device Drivers onto either a 256k Vehicle Plug or 256k Device Driver Plug, using the FM Dealer Utility. Refer to “FM
Dealer Utility User Manual”

• Insert the plug containing the Device Drivers into the vehicle’s code plug socket.

• The device drivers will be loaded onto the FM200 Plus.

• Refer to “FM200 Plus Beep and Flash Codes” for an explanation of the audible and visible signals generated by the FM200
Plus.

Note: Make sure the data transfer is complete before removing the plug from the socket. Successful transfer is indicated by two
short beeps. If a different beep sequence is heard, data transfer was unsuccessful and must be repeated. To do this, the vehicle
plug must be re-initialised and the device drivers reloaded onto the plug.

Configuring Vehicle Properties

• The configuration of the FM200 Plus unit is specified in the Fleet Manager application software. It includes the selection of
devices connected to each input and the events associated with data measured on specific inputs.

• More details can be found in the Fleet Manager application software documentation, or via online help.

• Once the vehicle configuration has been defined, it is loaded onto the Vehicle Plug and transferred to the vehicle by inserting
the plug into the vehicle’s code plug socket.

• Please refer to “FM200 Plus Beep and Flash Codes” for an explanation of the audible and visible signals generated by the
FM200 Plus.

• The latest documentation, firmware and application information can be obtained from http://www.mixtelematics.com

Setting the Real Time Clock

The Real Time Clock in the FM200 Plus must be set to the local time. This is done using the blue Driver Plug and either the FM
Dealer Utility or Fleet Manager application software. The correct date and time is then loaded into the FM200 Plus by inserting
the Driver Plug into the vehicle’s code plug socket.

Speed and RPM Calibration

Vehicle speed and RPM signals are calibrated using the violet calibration plugs labelled “SPD CAL" and “RPM CAL",
respectively. The calibrations can be performed using either the default settings on the calibration plug, or by selecting specific
values using the FM Dealer Utility. Before calibrating, the blue driver plug should be initialised.

Engine Speed (RPM) Calibration

Default Settings

The “RPM CAL” plug is pre-programmed for use at 1000 RPM.

• Disarm the system using the blue driver plug.

• Insert the “RPM CAL” violet plug into the code plug sockets

• Start the engine

• Increase engine speed to 1000 RPM and keep it constant for a few seconds.

• Remove the violet plug from the socket.

925
www.mixtelematics.com

925
 926

• The FM200 Plus will be calibrated to the engine speed of the vehicle.

Custom Settings

The “RPM CAL” plug can be programmed with custom calibration values.

• Disarm the system using the blue driver plug.

• Measure the exact frequency of the RPM signal using the appropriate measurement tools.

• Set the “RPM CAL” plug to the measured frequency using the “FM Dealer Utility” software.

• Disarm the system using the blue driver plug.

• Turn the ignition on.

• Insert the calibration plug into the code plug socket.

• The unit will beep three times indicating that it has been calibrated successfully.

Vehicle Speed Calibration

Default Settings

The "SPD CAL" plug is pre-programmed for use over 10 meters. This value can be changed using the FM Dealer Utility software.
During calibration the LED will flash as speed pulses are received, and the unit will beep in periods of one second. When the plug
is removed, the unit will beep three times.

• Disarm the system using the blue plug

• Drive to the beginning of a measured 10 meter distance.

• Insert the violet plug labelled "SPD CAL" into the code plug socket

• Drive the measured 10 meters.

• Remove the violet plug from the vehicle interface.

• The FM200 Plus unit is now calibrated with the correct distance to pulse ratio.

Custom Settings

· Disarm the system using the blue plug.

· Drive to the beginning of a demarcated 10 meter distance.

· Measure the exact distance to pulse ratio using the appropriate measurement tools.

· Set the speed calibration plug “SPD CAL” to the correct distance to pulse ratio using the FM Dealer Utility software.

· Disarm the system using the blue driver plug and turn the ignition on.

· Insert the calibration plug into the code plug socket.

· The unit will beep three times indicating that it has been calibrated successfully.

Testing Installation
Test Drive

926
www.mixtelematics.com

926
 927

• Disarm the system by inserting the blue plug into the Code Plug socket.

• Wait for the audible signal.

• Remove the plug.

• Start the engine.

• Carry out a test drive.

Extract and Transfer Data

• After the test drive, turn off the ignition.

• Wait for the system to arm, indicated by LED on the code plug socket flashing.

• Insert the green vehicle plug into the code plug socket.

• A beep indicates the start of data transmission.

• The LED on the code plug socket flickers during data transfer.

• A second beep indicates data transmission is complete.

• Remove the green vehicle plug.

• Insert the vehicle plug into the download module.

• Transfer the data to the PC using the Fleet Manager application software.

• Consult the Fleet Manager application software documentation for further details.

Troubleshooting
• A large assortment of application information in the form of Knowledge Base Articles (KBA’s) can be accessed from the Support
section of: http://www.mixtelematics.com

• Other application documents can be found on the Fleet Manager CD, or downloaded from http://www.mixtelematics.com

• The audible and visual signals generated by the FM200 Plus are described in the document: “FM200 Plus Beep and Flash
Codes”

LED does not Flash No Battery voltage applied to FM200 Plus • Check the voltage supply to FM200 Plus

• Check fuse

FM200 Plus remains armed and The blue driver key is not enabled for the • Use the correct blue driver key or get the
vehicle cannot start vehicle. driver key assigned to the vehicle.

• Enable the Driver Plug for the vehicle

Recorded vehicle data is The FM200 Plus has not been calibrated • Calibrate the FM200 Plus inputs
incorrect correctly

Data or Time of Trips are The clock in the FM200 Plus is not set • Set the date and time using the FM Dealer
incorrect and blue Driver Plug

927
www.mixtelematics.com

927
 928

Buzzer sounds when turning on Driver has not been identified or the driver is • Enable Blue Driver plug for the vehicle
the ignition not authorised to drive this vehicle

Maintenance
The FM200 Plus unit is maintenance-free.

Please ensure that the Code Plug socket is kept clean and free of dust and dirt.

FM200 Plus Specifications

Parameter Specification

Rated battery voltage 12 / 24 Volt dc nominal vehicle voltage battery

Minimum operating battery voltage 9 Volts dc

Maximum operating battery voltage 32 Volts dc

Typical stand-by current consumption 30mA

Storage temperature range - 20 ºC (- 4 ºF) to + 70 ºC (+ 158 ºF)

Working temperature range - 40 ºC (- 40 ºF) to + 80 ºC (+ 176 ºF)

Maximum non-condensing humidity 95%

Serial Port type - S1 TTL compatible master/slave bus

Serial Port type - S2 & S3 RS-232 Port (TX, RX, CTS & RTS)

Non-volatile backup memory 8kB FRAM

Real-Time-Clock backup power Lithium Battery

Non-volatile memory 1MB Flash

Interrupter relay – max continuous contact current 30A

Interrupter relay - max switching contact current 60A (for 3 max seconds)

Relay Drive 1 & 2 – max sink current Internally limited to 150mA

Audible indicator Integrated buzzer

Code Plug interface I2C bus

Speed sensor power supply nominal voltage 11Vdc

Speed sensor power supply max current Internally limited to 35mA

928
www.mixtelematics.com

928
 929

Positive Drive - nominal output voltage Battery+ voltage less 1V

Positive Drive - typical continuous supply current 1 amp dc

Maximum number of frequency inputs 4

F4 input Shared with I8 input

Frequency input waveform: F1(Speed), F2(RPM), Square / Sine wave

F3 & F4

Frequency signal offset voltage range - 32 Volts to + 32 Volts

Frequency signal peak-to-peak voltage minimum 0,5Vp-p

Frequency signal duty cycle range 1% - 99%

Frequency input impedance Dependant on jumper position (See Jumper Selection Table)

Maximum signal frequency: F1 & F2 5000 Hz

Maximum signal frequency: F3 & F4 10 000 Hz

Frequency Input Protection: F1 & F3 & F4 ± 45V spike (<50ms), ± 45V dc

Frequency Input Protection: F2(RPM) ± 400V spike (<50ms), ± 50V dc

Frequency Input Protection: GPS ± 45V spike (<50ms), ± 23V dc

Maximum number of Digital / Analogue inputs 8

Digital / Analogue Input 8 (I8) Shared with F4 input

Trigger voltage 0 – 38,33 Volt (programmable from application software)

Resolution (0 to +38V signal range) 150 mV

Hi-Resolution (0 to +5V signal range only) 20 mV

Input impedance 115K Ohms

Input Protection Immunity – DC input ports: 2kV fast transients;

27 Volt DC above battery voltage; -27 Volts below ground voltage

Enclosure Protection Classification IP 54

Note: All specifications are typical and are subject to change without prior notice.

Declarations

929
www.mixtelematics.com

929
 930

Type-Approval

This product conforms to the requirements of Directive 71/245/EEC, as last amended by Directive 95/54/EC.

Type-approval number: e1*72/245*95/54*2551*00

022551

Declaration of Conformity

We declare on our own responsibility that the product is in compliance with following norm(s) or documents:

· DIN EN 55022 (11/2001)

· DIN EN 61000-6-2 (03/2000)

Restrictions
• The FM200 Plus is for use only in earthbound vehicles and working machines.

• The FM200 Plus must be powered from a battery source.

• The FM200 Plus signal wires should not exceed 30 meters.

FM Part Numbers

Part Number Description

X10.723-002-015 FM200 Plus Kit

X39.723-002-080 FM200 Plus Vehicle Unit

X39.723-002-081 FM200 Plus Wiring Harness

X39.723-002-082 FM200 Plus Serial Cable

X39.723-002-033 Code Plug 256k (same as FM200)

X39.723-002-057 Code Plug 96k (same as FM200)

X39.723-002-006 Driver ID Plug (same as FM200 and FM100)

X39-723-002-054 Passenger Plug

X39.723-002-005 Code Plug Harness

X39.723-002-031 Metal housing FM200/FM200 Plus

X39.723-002-079 Fleet Manager Application Software

930
www.mixtelematics.com

930
 931

X39.723-002-009 Download Module

X39-723-002-069 FM200 - GPS Interface

X39.723-002-028 Calibration Set (Violet Code Plug set)

931
www.mixtelematics.com

931
 932
7.15.5.5 FM200 Plus Installation Checklist

© 2008 MiX Telematics | Updated 2008/05/07

1. Install harness

2. Install code plug socket

3. Connect power and signal inputs

4. Format Vehicle Plug

5. Initialise Vehicle Plug

6. Load device drivers

7. Set Vehicle ID on unit

8. Create new vehicle and define properties

9. Load vehicle configuration

10. Initialise Driver ID plug

11. Set FM200 Plus date and time

12. Calibrate Speed and RPM inputs

13. Test Installation

932
www.mixtelematics.com

932
 933
7.15.5.6 FM200 Plus Beep and Flash Codes

© 2008 MiX Telematics | Updated 2008/05/07

The FM200 Plus status is indicated by audible and visual signals. The following table shows the codes used to indicate the
various states.

This document is also applicable to the FM200 Locator, FM200 Communicator, FM Messenger and the FM Navigator.

Explanation of Symbols

FM200 Plus Audible buzzer

Visual signal - Red Lamp (LED) on Code-plug socket

Signal sequence

CONDITION BEEP AND FLASH CODE DURATIONS

FM200 Plus Installation

The FM200 Plus is shipped with

No Beeps
only the operating system
Only Operating
installed. The dealer must still
system loaded 1s on. 1/8s
install device drivers and the
off
configuration.

No Beeps The operating system and device

Operating system
drivers have been installed. The
and device drivers
1/2s on. 1/2s dealer must still install the
loaded
off configuration.

No Beeps This is the normal 'Armed' mode. It

indicates that the FM200 is
Normal ‘Armed Mode’
1/16 on. 2s operational and is not in trip mode
off or busy with any other operation.

No beeps 8 rapid flashed occur when the

FM200 Plus detect FM200 detects a GPS or TCO
GPS or TCO device 8 x 1/8 device, either at power-up, or after
flashes a period of inactivity.

Before a Trip

No beeps This is the normal 'Armed' mode. It

indicates that the FM200 is
Normal ‘Armed Mode’
1/16s on. 2s operational and is not in trip mode
off or busy with any other operation.

Private mode switch is in the on

Notification - Private 7 short
position. Location will not be
Mode enabled beeps
recorded for the trip that is about

933
www.mixtelematics.com

933

Driver identification
requested
Driver authorised to
drive vehicle
Driver not authorised
to drive vehicle
Passenger Plug
(black) inserted
FM200 Plus memory
80% - 95% full.
FM200 Plus memory
95% - 100% full.
During Calibration
Speed or RPM
calibration plug
934
www.mixtelematics.com
934
934
Lamp off to start.
If driver identification is required,
the beeps will be repeated 10
1/4s on. 3/4s
times, or until an authorised driver
off
is identified. This depends on the
selection made in the Fleet
Lamp off
Manager software Vehicle
Properties.
When an authorised driver's
identification plug is inserted, two
2 x 1/8s
short beeps will be heard. This
beeps
driver will now be permitted to start
the vehicle. The lamp will remain
Lamp off
off, indicating the FM200 Plus is
now in 'Disarmed' mode.
When an unauthorised driver's
1 x 1/2s plug is inserted, one long beep will
beep be heard. The FM200 Plus will
remain in 'Armed' mode as
1/16s on. 2s indicated by the lamp flash rate.
off The driver will be unable to start
the vehicle.
One short beep occurs when the
1 x 1/8s
FM200 Plus has successfully read
beeps
the Passenger plug. The flash
sequence depends on the status
Lamp
of the FM200 Plus when the plug
flashes
is inserted.
3 Short beeps. The FM200 Plus
memory is 80% - 90% full and
3 x 1/8s must be downloaded, with a green
beeps code-plug. If driver identification
was required, this warning will
Lamp off occur one second after successful
identification. Otherwise, it will be
heard when the trip begins.
3 long beeps. The FM200 Plus
memory is 95% - 100% full and
must be downloaded using a
3 x 1/2s
green code plug. If driver
beeps
identification was required, this
warning will occur one second
Lamp off
after successful identification.
Otherwise, it will be heard when
the trip begins.
When the violet calibration plug is
1s on. 1s off.
inserted, long beeps will be heard.
 935

The lamp flash rate is dependent

on the frequency of the calibration
pulses (one change per 25
inserted (Violet Plug) Flashes
pulses). this is an indication that
the pulses are being detected by
the FM200 Plus.

Three short beeps will be heard if

3 x 1/8s
the date and time was set
beeps
Setting date and time successfully. The flash sequence
(Blue Plug) depends on the status of the
Lamp
FM200 Plus when the plug is
flashes
inserted.

One short beep occurs when the

2 x 1/8s
-------------------------------------- FM200 Plus detects the plug. Two
Set Odometer value beeps
short beeps occur when the
(Green Plug)
Odometer value has been set. The
Flickers
lamp flickers during the operation.

4 x 1/8s Four short beeps occur when the

beeps Engine Hours value was set
Set Engine Hours successfully. The flash sequence
Lamp depends on the status of the
flashes FM200 when the plug is inserted.

During a Trip

When a trip begins, the FM200

No beeps
Plus mode changes from armed to
Start of Trip disarmed mode and the lamp
Flashing
stops flashing. There is no audible
Stops
indication that the trip has begun.

During a trip, while no alarm

No Beeps
thresholds are being exceeded,
While Driving
the lamp remains off and the
Lamp off
buzzer is silent.

Continuous While any alarm thresholds are

beep being executed, the buzzer will
Event alarm
sound continuously and the lamp
Lamp off will remain off.

1 x 1/8s
The start of a sub-trip is indicated
beep
Start of sub trip by one short beep. There is no
visual indication.
Lamp off

At the end of the trip, after the

1 x 1/8s
arming delay, the buzzer gives
beep
one short beep. The FM200 mode
End of trip
changes to 'Armed'. the lamp will
1/16s on. 2s
resume the normal 'Armed Mode'
off
flash rate.

935
www.mixtelematics.com

935

During Data Transfer
Incorrect vehicle plug
inserted.
Correct vehicle plug
inserted – Successful
download of trip data.
Correct vehicle plug
inserted – Successful
transfer of
configuration.
Correct vehicle plug
inserted –
Unsuccessful data
transfer.
GSM Diagnostic Plug Inserted (GSM Diagnostics operate on a 30 second cycle.)
Modem registered on
GSM network
Connection
Established
SMS Received
SMS Sent
936
www.mixtelematics.com
------- data transfer -----
------- data transfer -----
----- data transfer ----
936
936
1 x 1/2s
If the incorrect green plug is
beep
inserted, the buzzer will give one
long beep and the flash sequence
1/16s on.2s
will remain unchanged.
off.
One short beep marks the start of
the data transfer. During the
1 x 1/8s transfer, the lamp flickers. One
beep short beep indicates the end of
downloading trip data. When the
Lamp flickers transfer is complete, the lamp will
resume the normal ‘Armed Mode’
flash rate.
One short beep marks the start of
the data transfer. During the
2 x 1/8s transfer, the lamp flickers. Two
beeps short beeps indicate the end of
uploading configurations, DDRs or
Lamp flickers DDMs. When the transfer is
complete, the lamp will resume the
normal ‘Armed Mode’ flash rate.
One short beep marks the start of
1 x 1/2s the data transfer. During the
beep transfer, the lamp will flicker. If the
transfer was unsuccessful or
Lamp flickers incomplete, one long warning
beep will be heard.
1 x 1/16s One short beep indicates the
beep modem is logged onto a GSM
network. The lamp flashes when
Lamp valid responses are received from
flashes the GSM modem.
Three short beeps indicate an
3 x 1/16s
incoming data call was answered
beep
and a point-to-point connection
was established. The lamp flashes
Lamp
when valid responses are received
flashes
from the GSM modem.
2 x 3/16s Two medium beeps indicate an
beep incoming SMS was processed.
The lamp flashes when valid
Lamp responses are received from the
flashes GSM modem.
3 x 3/16s Three medium beeps indicate an
beep outgoing SMS has been saved to
 937

the SIM and is ready to be sent.

Lamp The lamp flashes when valid
flashes responses are received from the
GSM modem.

1 x 5/8s One long beep occurs if the

beep modem responds with an error.
General Error The lamp flashes when valid
Lamp responses are received from the
flashes GSM modem.

2 x 5/8s Two long beeps occur if the

beep supplied PIN code was rejected.
Pin Error The lamp flashes when valid
Lamp responses are received from the
flashes GSM modem.

5 Short beeps indicates that the

out-bound messages buffer has
5 x 1/16s
exceeded 10 unsent messages
beeps
Message buffer full (Active Events & Text messages).
At this point the oldest messages
Lamp off
in the buffer will be removed to
keep place for new information.

GPRS Diagnostics (Use GSM diagnostic plug)

When there are no

All beep and flash codes for normal GSM operation communications on the GPRS link,
General
applies. the GSM modem will check for
incoming SMS messages.

Two short beeps indicate that the

1 x 1/16s
modem is logged onto a GSM
beep
Modem registered on network and is GPRS capable (not
GSM network logged on). The lamp flashes
Lamp
when valid responses are received
flashes
from the GSM modem.

Three short beeps indicate that the

3 x 1/16s modem has changed from GSM
beep modem to GPRS mode. This also
Connection
means that a GPRS connection to
Established
Lamp the GSM network is established.
flashes The lamp flashes with results from
the modem.

no beeps Any incoming packets from the

GPRS Wireless Internet Service (GPRS
communication Lamp & WLAN) (office) will be indicated
flashes by a lamp flash.

DECT Diagnostic Plug Inserted (DECT Diagnostics operate on a 10 second cycle)

937
www.mixtelematics.com

937
 938

1 x 1/16s One short beep occurs when the

beep FM200 detects a DECT base
Modem Registered station. The lamp flashes when
Lamp valid responses are received from
flashes the DECT modem.

Three short beeps indicate a point-

3 x 1/16s to-point connection to a DECT
beep server was established. The lamp
Connection
flashes when valid responses are
Established
Lamp received from the DECT modem.
flashes

GPS Diagnostic Plug Inserted

1 x 1/2s
One half-second beep occurs
beep
Data received from each time an error is detected.
GPS with errors The lamp flashes when data is
Lamp
received from the GPS.
flashes

1 x 1/16s One short beep occurs when GPS

GPS data received - beep data is received with position
position not undetermined. The lamp flashes
determined Lamp when data is received from the
flashes GPS.

2 x 1/16s
beep Two short beeps occur when GPS
data is received with position
GPS data received -
Lamp determined. The lamp flashes
position determined
flashes when data is received from the
GPS.

Trailer ID Diagnostic Plug Inserted (A combination of these beep sequences will occur, depending on which trailers are
connected, while the diagnostic plug is inserted.)

1 beep /
One beep per second indicates
second
trailer 1 is connected. The lamp
First trailer detected
flashes when valid responses are
Lamp
received from the Trailer ID unit.
flashes

2 beeps /
Two beeps per second indicate
second
Second trailer trailer 2 is connected. The lamp
detected flashes when valid responses are
Lamp
received from the Trailer ID unit.
flashes

3 beeps / Three beeps per second indicate

second trailer 3 is connected. The lamp
Third trailer detected
flashes when valid responses are
Lamp received from the Trailer ID unit.

938
www.mixtelematics.com

938
 939

flashes

4 beeps /
Four beeps per second indicate
second
Fourth trailer trailer 4 is connected. The lamp
detected flashes when valid responses are
Lamp
received from the Trailer ID unit.
flashes

Speed Calibration Diagnostic Plug Inserted

Long beeps are generated while

1s on. 1s off.
Speed pulses the plug is inserted The lamp flash
connected to FM200 rate is proportional to the
Lamp
Speed input frequency of the signal on the
flashes
FM200 Speed input.

Two short beeps occur each

2 x 1/8s second when a TCO signal is
TCO connected to
beeps / s detected on the FM200 Speed
FM200 Speed input
input. The lamp flashes when valid
Lamp responses are received from a
flashes TCO unit connected to the FM200
Speed input.

RPM Calibration Diagnostic Plug Inserted

Long beeps are generated while

1s on. 1s off. the plug is inserted
RPM pulses
connected to FM200
Lamp The lamp flash rate is proportional
RPM input
flashes to the frequency of the signal on
the FM200 RPM input.

WLAN Diagnostics

Link with access point

is OK, but no active 1 x 1/16s beep
comms channel

Port connection to
access point is OK,
2 x 1/16s beeps
but no comms
channel

Connected to access
point and attempting
3 x 1/16s beeps
to send data to the
service

An error string /
condition was 1s on
received

Module in power-save 2 x 3/16s beeps

939
www.mixtelematics.com

939
 940

mode (positive drive

is off)

Module configuration
is out of date, busy 5 x 3/16s beeps
reconfiguring

940
www.mixtelematics.com

940
 941
7.15.5.7 FM200 Plus HV Installation and User Manual

© 2008 MiX Telematics | Updated 2008/06/11

Overview
This document covers the following topics:

· Introduction

· Safety Procedures

· Before Installation

· During Installation

· After Installation

· During Operation

· Installation

· Installation Requirements

· Summary of Installation Steps

· Operation

· Beep and Flash Codes

· FM200 Plus HV Harness Installation

· Starter Interruption

· Code-plug Socket Installation

· Positioning the FM200 Plus HV Unit

· Signal Inputs

· Frequency Jumper Input Selection

· Power Outlets

· Serial Communication

· Loading Device Drivers

· Setting the real time clock

· Speed and RPM calibration

· Testing Installation

· Troubleshooting

· Maintenance

941
www.mixtelematics.com

941
 942

· FM200 Plus HV Specifications

· Declarations

· FM Part Numbers

Introduction
System Overview

The FM Fleet Manager 200 Plus HV (FM200 Plus HV) is a high voltage on-board-computer for use in vehicles and working
machines. It is specifically intended for vehicles with battery power exceeding 24V, and is specified to work up to an input voltage
of 110V. The system is fully compatible with the FM200 Plus, and is specifically suited for operation in the new 42V vehicles
without an external regulator. The system is designed to record a wide range of vehicle and trip related information, including
vehicle speed, engine speed, engine temperature, fuel consumption, trip start and end times. The FM200 Plus HV interfaces
directly to a large selection of transducers which enable the recording of data, such as vehicle position, fuel consumption, and
vehicle loading.

The FM200 Plus HV is used in conjunction with the FM Fleet Manager application software. This software facilitates the
management of vehicle, driver and passenger information, definition and management of events to be monitored by vehicle units,
recording of servicing details, analysis of fleet data and extensive management reporting.

The primary method of communicating with the FM200 Plus HV is via the green Vehicle Plug. The plug is used to extract data
from the FM200 Plus HV and transfer it to a Personal Computer, where it can be processed and analysed by the FM Fleet
Manager application software. Various modems can be connected to the FM200 Plus HV to facilitate wireless communication
with the vehicle unit.

Vehicle drivers are identified by means of a driver specific blue plug. Identification can be enforced by interrupting the vehicle’s
starter circuit.

Note: This document will use the word “vehicle”, referring to vehicles and all other types of electrical equipment where the
system may be installed. It also will in places use the words “FM200” or “FM200 Plus” – as abbreviations for FM200 Plus HV.

Analogue/Digital Inputs

The FM200 Plus HV is equipped with eight analogue/digital inputs (I1-I8), which can be used to monitor either digital or analogue
signals of up to 117V DC, using four . The eighth Analogue/Digital input (I8) is shared with the fourth frequency input (F4). Input
signal voltage range and resolution is selectable from the Fleet Manager software. For digital type input signals, switching
thresholds can be defined in the software, which, when crossed, trigger an event that records the specified data. Other actions
(including the switching of relays and warnings) can also be defined. Please refer to the “Specifications” section of this document
for more details.

Frequency Inputs

The FM200 Plus HV has four frequency inputs, which can be used to record frequency type signals. The fourth frequency input
(F4) is shared with the eighth Analogue/Digital input (I8). Provision is made for a wide range of signal types. Please refer to the “
Frequency Input Jumper Selection” section of this document for more details.

System Requirements

The FM200 Plus HV is designed for use in vehicles, special vehicles and working machines with a 24 to 110 volt DC power
supply. The FM Fleet Manager application software is required to complete the installation process.

Safety
Before installation

Installer Requirements:

942
www.mixtelematics.com

942
 943

· Installation should only be undertaken by a vehicle technician with comprehensive occupation specific knowledge and who has
complete command of the actions required by the occupation.

· Installation by an unqualified technician may adversely affect the operating reliability of the vehicle and could endanger other
road users.

· A basic knowledge of vehicle electrical and mechanical systems is required to successfully install the FM Fleet Manager
200Plus system.

· The system should only be installed by a suitably qualified vehicle technician with a basic knowledge of the operation of
computers. Installation technicians should attend an FM training course to acquire the skills needed for installation,
configuration and operation of the FM Fleet Manager system.

· Installers should consult the vehicle manufacturer’s documentation for the specific vehicle make and model prior to
undertaking an installation.

· Installers should pay particular attention to the location of fuel systems, hydraulic systems, compressed air systems and other
electrical and mechanical systems, which may have a bearing on the installation.

· Installers should pay attention to any changes to the vehicle’s systems or settings, which should be noted prior to the
installation.

· Installers should refrain from smoking and the use of naked flames, which could cause a fire in or near the vehicle.

Tools:

· Standard technical equipment and appropriate tools for use with vehicles are required to install the FM Fleet Manager 200 Plus
system.

· Vehicle-specific tools may be required for the removal of consoles and covers.

Secure the workplace:

· Remove the ignition key from the vehicle’s ignition lock.

· Ensure that the vehicle’s engine cannot be unintentionally started during the installation.

· Record all data stored in the volatile memory of the vehicle’s systems to ensure that such data can be restored.

· When the negative terminal of the battery is disconnected, all volatile memory will be lost. Please ensure that such information
is recorded prior to disconnection so that systems can be reconfigured correctly.

· Short-circuiting the vehicle’s electrical system may result in fire, explosion of the battery and/or damage to other electrical
systems.

· Electrical shock from high voltage batteries must be avoided, as this may lead to death or injury.

· The negative terminal of the vehicle’s battery should be disconnected before commencing installation. If the vehicle has
additional batteries, it may be necessary to disconnect the negative terminals of these batteries too.

During installation

· Should it be necessary to remove seats, covers or other components, care should be taken to avoid accidental damage and/or
disconnection of cables.

· All components should be checked for damage prior to being installed into the vehicle.

· For small installation openings, a drill should be used.

943
www.mixtelematics.com

943
 944

· For larger openings, a conical milling cutter, compass saw or file should be used.

· All rough edges should be trimmed.

· Careful attention must be paid to the manufacturer’s safety regulations for all tools used.

· Oils and fuels must be collected in appropriate containers and disposed of in accordance with the law.

Positioning of product components:

· Installers should ensure that the components of the product do not influence or hamper the functioning of the vehicle’s
systems.

· Care should be taken to ensure that the product’s components are not damaged during installation.

· Ensure that sufficient space is available for all components of the product prior to commencing the installation.

· Please pay attention to the routing of cables and wiring.

· Do not install the product in or near the location of mechanical or electrical airbags.

· Do not drill into supporting or stabilising braces or beams.

Installation of Wiring:

· Note the product’s wire gauge.

· If the wire gauge is reduced, current density increases which may cause the wiring to overheat.

· Cables should be routed in existing channels and should not be routed parallel to ignition cables or other cables subject to high
current.

· Cables should be fixed with cable-ties or adhesive tape.

· Do not route cables over moving parts.

· Do not fix cables on the steering column.

· Ensure that the cables are not exposed to pulling, pressure or shearing deformation.

· If the cables are routed through drilled holes, rubber grommets or similar protection should be used.

· Suitable cable-strippers should be used to strip insulating material from cables and cable-strippers should be adjusted to avoid
damaging or separating the wire strands.

· Cables should only be connected using solder or suitable crimping lugs.

· A proper crimping tool should be used on all crimping lugs.

· Careful attention must be paid to the manufacturer’s safety regulations for all tools used.

· Insulate all exposed wires to prevent short-circuits.

· Connections to vehicle power supply must be installed with a fuse or current limiting device.

· Be aware that short-circuiting may be caused by faulty connections and crushed or damaged cables.

· Short-circuiting the vehicle’s electrical system may result in fire, explosion of the battery and/or damage to other electrical

944
www.mixtelematics.com

944
 945

systems. To prevent this, all connections carrying current must be soldered and insulated correctly. Other connections such as
the speed signal, RPM signal, brake light or clutch switch can be made with crimping lugs.

· Incorrect connections can lead to short circuits. Connections should only be made in accordance with the vehicle’s wiring
diagram.

· Current and voltage should be measured with a multi-meter or diode test lamp.

· The use of inadequate test equipment may result in the damage to control devices or other electrical systems.

Recommendation: 3M™ manufactures a range of water-resistant crimps that can help to speed up an installation and make the
installation more reliable. These crimps are part of the 3M™ Scotchlok™ range of products. The part number for the suitable
crimps is UB2A and the part number for the crimping tool is E-9Y, E-9E, or E-9BM. Contact your local 3M™ agent to order these
parts and for detailed information on their use. These crimps are self stripping, and the wire must be left unstripped when using
them (pre-stripped wires can simply have their ends cut cleanly using side-cutters).

Note:

1) All joined wires should be connected using a suitable crimp or joined using a soldered connection.

2) Not using the crimping tool recommended for a particular crimp with will almost certainly severely impair the installation quality
and reliability.

3) Soldered connections need to be kept dry to prevent corrosion. Adhesive lined heat shrink (provided) may assist in
accomplishing this.

After Installation

· Reconnect the vehicle’s ground cable to the negative terminal of the battery.

· Re-configure the values in the volatile memory of all systems.

· Check all vehicle functions.

· Explain the functions of the FM200 Plus HV system to the customer and give the customer the User Manual.

During Operation

· The product must be used in accordance with operating instructions.

· Failure to use the product as directed might result in personal injury, material damage and/or damage to the environment.

Installation
Installation Requirements

Please note the requirements specified in the “Safety” section of this document.

Summary of Installation Steps

Step Action Software Tools Related Documents

1 Install harness None -

2 Install code plug socket None -

945
www.mixtelematics.com

945
 946

3 Connect power and signal inputs None -

4 Format Vehicle Plug FM Dealer Utility FM Dealer Utility User Manual

5 Initialise Vehicle Plug FM Dealer Utility FM Dealer Utility User Manual

Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

6 Load device drivers FM Dealer Utility FM Dealer Utility User Manual

FM200 Plus Beep and Flash Codes

7 Set Vehicle ID on unit FM Dealer Utility FM Dealer Utility User Manual

Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

8 Create new vehicle and define Fleet Manager Application Software Fleet Manager Application Software Help &
properties Docs

9 Load vehicle configuration Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

10 Initialise Driver ID plug (only FM Dealer Utility FM Dealer Utility User Manual
necessary if driver identification is
selected) Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

11 Set FM200 Plus HV date and FM Dealer Utility FM Dealer Utility User Manual
time (for local time)
Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

12 Calibrate Speed and RPM inputs FM Dealer Utility FM Dealer Utility User Manual

13 Test Installation Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

Note: Steps 4, 5 & 6 can be performed in one operation, using the FM Dealer Utility.

Operation
The functioning of FM200 Plus HV is determined largely by the configuration specified within the Fleet Manager Software.

Armed / Disarmed Status

Armed status is indicated by one short flash of the red lamp every two seconds. In some installations, the vehicle cannot be
started while in the armed mode and must be disarmed as described below. The red LED remains off while the FM200 Plus is
disarmed.

Driver Identification and Disarming of the FM200 Plus HV

If driver identification is required before the trip can begin, the driver must insert the blue driver key into the Code Plug Socket. If
the driver is authorised to drive the vehicle, the FM200 Plus HV will beep twice briefly and the LED in the reader unit will be

946
www.mixtelematics.com

946
 947

switched off. The unit is now disarmed and will allow the vehicle to be started.

Data Transfer

Data stored in the FM200 Plus HV can be transferred by inserting the green vehicle plug into the Code Plug Socket. The FM200
Plus HV beeps briefly before copying the stored data onto the Code Plug. During the transfer, the red lamp flickers rapidly. One
short beep indicates the completion of a successful transfer. The red lamp then resumes the normal armed mode flash rate of
one short flash every two seconds. An unsuccessful data transfer is indicated by a long beep. A change to the system
configuration will result in two short beeps at the end of the data transfer session.

Trouble Shooting

LED does not Flash No Voltage • Check the voltage supply to FM200 Plus HV

The Fleet Manager 200 Plus HV The blue driver key is not assigned to the • Use the correct blue driver key or get the
can not be enabled vehicle. driver key assigned to the vehicle.

The Buzzer sounds when The driver registration was not done or • Register with your blue driver key.
turning on the ignition
The blue driver key is not released / • Get your blue driver key released for the
configured for the vehicle. vehicle and register with it.

Beep and Flash Codes

The FM200 Plus HV status is indicated by audible and visual signals. The following summarized table shows the codes used to
indicate the various states.

CONDITION BEEP AND FLASH CODE DURATIONS

At Installation

No Beeps
Only Operating system loaded
1s on. 1/8s off

No Beeps
Operating system and device
drivers loaded
1/2s on. 1/2s off

No Beeps
Normal ‘Armed Mode’
1/16 on. 2s off

Before a Trip

No beeps
Normal ‘Armed Mode’
1/16s on. 2s off

947
www.mixtelematics.com

947
 948

1/4s on. 3/4s off

Driver identification requested
Lamp off

2 x 1/8s beeps
Driver authorised to drive vehicle
Lamp off

1 x 1/2s beep
Driver not authorised to drive
vehicle
1/16s on. 2s off

3 x 1/8s beeps
FM200 Plus HV memory 80% -
95% full.
Lamp off

3 x 1/2s beeps
FM200 Plus HV memory 95% -
100% full.
Lamp off

During Calibration

1s on. 1s off.
Speed or RPM calibration plug
inserted (Violet Plug)
Flashes

3 x 1/8s beeps
Setting date and time (Blue Plug)
Unchanged
------ unchanged -------

During a Trip

No beeps
Start of Trip
Flashing Stops

No Beeps
While Driving
Lamp off

Continuous beep
Event alarm
Lamp off

948
www.mixtelematics.com

948
 949

1 x 1/8s beep
Start of sub trip
Lamp off

1 x 1/8s beep
End of trip
1/16s on. 2s off

During Data Transfer

1 x 1/2s beep
Incorrect vehicle plug inserted.
1/16s on.2s off.

------- data transfer -----

1 x 1/8s beep
Correct vehicle plug inserted –
Successful download of trip data.
Lamp flickers

Correct vehicle plug inserted – ------- data transfer ----- 2 x 1/8s beeps
Successful transfer of
configuration. Lamp flickers

----- data transfer ---- 1 x 1/2s beep

Correct vehicle plug inserted –
Unsuccessful data transfer.
Lamp flickers

Green plug memory full. FM200 1 x 5s beep

Plus has not completed transfer
of trip data. 1/16s on. 2s off.

See detailed table in the “FM200 Plus Beep and Flash Codes” manual for all beep and flash codes.

FM200 Plus Harness Installation

Please read the “Safety” section of this document before installing the vehicle harness.

Connect the FM200 Plus HV harness wires according to the following table:

· Connect to vehicle battery +24V to +110V.

J1-12 Red BATT+ Battery Power

949
www.mixtelematics.com

949
 950

· Must be protected with the provided 3 amp high voltage

slow blow fuse, or a similar one already present in the
vehicle's wiring.

· Connect directly to vehicle ground.

J1-13 Brown GND Ground
· Do not tap into an existing ground wire carrying high
current.

· Connect to vehicle ignition switch.

J1-1 Black IGN Ignition
· Must be protected with a 7.5 amp fuse

· Vehicle speed signal connected here

J1-19 Blue/White F1 Frequency Input 1 · Refer to “Frequency Input Jumper Selection” if signal is
not detected by FM200 Plus HV.

· Connect TCO to only F1 input.

· Engine speed signal (RPM) connected here

J1-20 Green F2 Frequency Input 2
· Refer to “Frequency Input Jumper Selection” if signal is
not detected by FM200 Plus HV

· Connect GPS to only F3 input.

· Move F3 jumper to GPS position if GPS is connected

J1-21 Violet F3 Frequency Input 3 without using “FM200-GPS Interface Cable”.

· Refer to “Frequency Input Jumper Selection” if signal is

not detected by FM200 Plus HV

J1-5 White/Violet I1 Digital/Analog Input 1 · Maximum signal voltage = 117V.

J1-6 White/Red I2 Digital/Analog Input 2 · Do not connect signals from unsuppressed inductive
sources such relay coils (where severe voltage spikes
can be generated).
White/
J1-3 I3 Digital/Analog Input 3
Green
· For F4, refer to “Frequency Input Jumper Selection” if
the signal is not detected by FM200 Plus HV.
White/
J1-4 I4 Digital/Analog Input 4
Yellow

J1-17 White/Black I5 Digital/Analog Input 5

J1-16 White/Blue I6 Digital/Analog Input 6

White/
J1-15 I7 Digital/Analog Input 7
Brown

Digital/Analog Input 8
J1-14 White I8/F4
Frequency Input 4

950
www.mixtelematics.com

950
 951

· Supplies power to a speed sensor

· Output voltage typically 11V

J1-18 Black White VSPD Speed Sender Power
· Load current must not exceed 35mA

· Output controlled by FM200 Plus HV and selected in

Vehicle Properties.

· Connect the ground side of an external relay coil here.

J1-22 Brown/Red EXT DRIVE 1 Relay Drive 1 · Relay operation is controlled by the FM200 Plus and is
specified in Vehicle Properties.

· Coil current must not exceed 150mA

· Connect the ground side of an external relay coil here.

J1-11 Brown/Black EXT DRIVE 2 Relay Drive 2 · Relay operation is controlled by the FM200 Plus and is
specified in Vehicle Properties.

· Coil current must not exceed 150mA

· Connects to ignition switch side of starter circuit, if starter

interruption is required.

· Do not interrupt high current side of starter circuit.

J3 Black IMM1A Starter interruption
· Do not interrupt starter circuit while current is flowing
(especially at higher voltages than 24V) – the relay
contacts may undergo excessive wear, damage or arcing
and fire may result.

J4 Black IMM1B Starter interruption · Connect to ignition switch side of starter circuit, if starter
interruption is required.

J1-2 Black GND Code Plug Ground · Connected directly to code plug socket connector.

J1-8 Green CPDATA Code Plug Data · No additional connection required.

J1-9 Red CPPOWER Code Plug Power

J1-10 White LEDOUT Code Plug Socket LED

· Connected internally
J1-7 Brown BUZ Buzzer Power
· No additional connection required

· Wire is only provided with FM200 Plus Water Proofing

J2-15 Orange Positive Drive Power external devices Kit

· A maximum current of 500mA may be supplied to

Brown/ external devices
J2-4 GND GND external devices
Yellow

951
www.mixtelematics.com

951
 952

Starter Interruption
The FM200 Plus HV has an internal relay intended exclusively for the interruption of the vehicle’s starter circuit.

Connect the two starter interruption wires to the corresponding terminals on the back of the vehicle unit. Cut the wire from the
ignition lock to the starter relay and solder the starter interruption wires from the FM200 Plus HV unit onto the ends of the wires
from the starter circuit. These wires can be connected either way.

Note: The internal relay is intended only for interruption of the low current starter circuit. This relay should not be used to interrupt
the fuel pump or any other component of the vehicle’s electrical system. For high current starter applications, an additional relay
will be required.

This relay should not interrupt current of higher values than those shown in the following table directly. Relay arcing, damage and/
or fire can result from interrupting (switching off) high current loads at high voltages. This is not normally a concern because the
relay is usually in the switched state when current is removed. If required, an additional adequately rated and externally mounted
relay (which switches the high current load) should be switched by the starter interruption relay.

Voltage Maximum Relay Interrupting Current (Current Flowing when Relay Switches)

24V 60A

36V 2A

48V 1A

72V 0.6A

96V 0.45A

110V 0.4A

Code Plug Socket Installation

Note: Please follow the instructions regarding the positioning of product components as contained in the “Safety” section of this
document.

• The Code Plug Socket must be installed inside the passenger compartment or the driver cabin, to protect it from possible
damage by water or other environmental factors.

• The Code Plug Socket should not be installed in or near the ventilation or heating systems, which may cause it to overheat.

• The Code Plug Socket should be installed in a position where it will not be subjected to pressure, impact or excessive vibration.

• Select the installation position carefully before proceeding with the installation.

• Mark and drill or cut the required hole.

• Remove the mounting clip from the socket.

• Remove the protection film from the adhesive surface of the foam ring and press it firmly against the back of the interface.

• Insert the socket into the mounting hole and slide the mounting clip into position.

952
www.mixtelematics.com

952
 953

Hole size = 13/16” - 20 mm

Positioning the FM200 Plus HV Unit

Note: Please follow the instructions regarding the positioning of product components as contained in the “Safety” section of this
document.

· The FM200 Plus HV must be installed inside the passenger compartment, the driver cabin, or other protected location, to
protect it from possible damage by water, solvents, fuel or other environmental factors.

· The FM200 Plus HV should not be installed in or near the ventilation system, heating system, or hot surfaces which may cause
it to overheat or be damaged by condensed water vapour.

· The FM200 Plus HV should be installed in a position where it will not be subjected to pressure, impact or excessive vibration.
Uneven surfaces where the box can be deformed or damaged should be avoided.

· Select the installation position carefully before proceeding with the installation.

· Mark and drill the required holes.

· Route cables from the unit to the appropriate senders within the vehicle. Additional information can be found in the “Harness
Installation” section of this document.

· After connecting the system components and performing a system test, mount the vehicle unit securely, making use of the
optional metal armoured housing, if required. The armoured housing is available as a spare part and is used to protect against
tampering.

Signal Inputs
Analogue/Digital Inputs

The FM200 Plus HV is equipped with eight analogue/digital inputs (I1-I8), which can be used to monitor either digital or analogue
signals. The eighth Analogue/Digital input (I8) is shared with the fourth frequency input (F4). Input signal voltage range and
resolution is selectable from the Fleet Manager software. For digital type input signals, switching thresholds can be defined in the
software, which, when crossed, trigger an event that records the specified data. Please refer to the “Specifications” and “Harness
Installation” sections of this document for more details.

Frequency Inputs

The FM200 Plus HV has four frequency inputs, which can be used to record frequency type signals. The fourth frequency input
(F4) is shared with the eighth Analogue/Digital input (I8). Provision is made for a wide range of signal types. Please refer to the “
Frequency Input Jumper Selection”, “Harness Installation” and “Specifications” sections of this document for more details.

Frequency Input Jumper Selection

The FM200 Plus HV can accept a large variety of input signal types. To accommodate the many possibilities, each frequency
input (F1/SPD, F2/RPM, F3 and F4) is provided with a jumper for selecting the appropriate signal range. These jumpers are
located inside the FM200 Plus HV as shown below.

953
www.mixtelematics.com

953
 954

For most installations the default settings will be correct. If the FM200 Plus HV does not correctly detect the input signal, the
following table should be consulted to establish the applicable setting. If the signal type is unknown, try the options in the order
shown below, starting from the top. The table shows the jumper position for each signal type. Each jumper position can be
applied to each of the four frequency inputs. The last row (position 4) in the table shows the F3 jumper position that should be
used when an external GPS signal is connected (no special /intelligent GPS cable is then required). A summary of this table is
also provided inside the lid of each FM200 Plus HV.

Jumper Signal Symbol Input Details When to Select

Positio Range
n

1 Small Sine Wave · Factory default setting

· AC coupled · Required when a FM TCO Interface is

connected to F1/Speed input
· Signal peak-to-peak voltage greater
than 0.5 volts · Equivalent to FM200

· Lower input impedance · Not recommended for noisy signals

· High sensitivity · This work for high frequencies

2 Big Sine Wave · Large Noisy signals – improved noise

immunity
· Default Setting
· Signals with high source impedance
· AC coupled
· This works for lower frequencies
· Signal peak-to-peak voltage greater
than 4 volts

· Higher input impedance = 94K?

· Signal max offset voltage -110V to

+110V

3 Big Square Wave · Noisy TTL signals – improved noise

immunity
· DC coupled
· Larger TTL signals
· Signal switches between 0 and > 5
volts · This works for lower frequencies

· Higher input impedance = 94K?

954
www.mixtelematics.com

954
 955

· Signal max offset voltage -110V to

+110V

4 Small Square Wave · Small TTL signals

· DC coupled · Signal may be degraded due to low input

impedance.
· Signal switches between 0 and < 5
volts · This works for high frequencies and GPS
signals on F3
· Lowest input impedance = 8.8K?

· High sensitivity

Power Outputs
External Relay Drives

· The FM200 Plus HV has two external relay drive outputs (Relay Drive 1 & 2), which are suitable for controlling external relays.

· These outputs are controlled by the FM200 Plus HV and are configured in Vehicle Properties of the Fleet Manager application
software.

· The Relay Drive Outputs connect to the ground side of an external relay.

· The maximum current of the external relay is limited to 150mA.

· Please refer to the “Specifications” and “Harness Installation” sections of this document for more details.

Speed Sender Power (VSPD)

· A nominal 11 Volt DC supply is provided specifically for powering a speed sensor requiring external power.

· VSPD output is internally current limited. Refer to the “FM200 Plus HV Specifications” section of this document.

· This output is controlled by the FM200 Plus HV and is configured in Vehicle Properties of the Fleet Manager application
software.

Positive Drive

· The Positive Drive output supplies power to FM200 Plus HV accessories.

· This output is controlled by the FM200 Plus HV and is configured in Vehicle Properties of the Fleet Manager application
software.

· Access to this output is via the FM FM200 Plus Serial Cable.

· Refer to the “FM200 Plus HV Specifications” section of this document.

· Do NOT connect an external voltage to the positive drive line. This may cause damage to the product.

Serial Communication

955
www.mixtelematics.com

955
 956

· The FM200 Plus HV is equipped with one TTL (S1) and two RS232 (S2 & S3) serial ports.

· The FM200 Plus Serial Cable is required to connect to these ports.

· Please refer to the “Specifications” section of this document and the FM200 Plus Serial Cable documentation for more details.

Loading Device Drivers

· The FM200 Plus HV is supplied with the Operating System, the latest market-accepted set of device drivers (at time of
manufacture), and a basic configuration (set for minimum default logging) loaded.

· Before the unit can be configured, ensure that the latest version of FM200 Plus Device Drivers required for the task is loaded.

· The latest Device Drivers are contained in the latest version of the FM Dealer Utility, which can be downloaded from http://
www.mixtelematics.com

· Load Device Drivers onto either a 256k Vehicle Plug or 256k Device Driver Plug, using the FM Dealer Utility. Refer to the
document “FM Dealer Utility User Manual”

· Insert the plug containing the Device Drivers into the vehicle’s code plug socket.

· The device drivers will be loaded onto the FM200 Plus HV.

· Refer to the document “FM200 Plus Beep and Flash Codes” for an explanation of the audible and visible signals generated by
the FM200 Plus HV.

Note: Make sure the data transfer is complete before removing the plug from the socket. Successful transfer is indicated by two
short beeps. If a different beep sequence is heard, data transfer was unsuccessful and must be repeated. To do this, the vehicle
plug must be re-initialised and the device drivers reloaded onto the plug.

Configuring Vehicle Properties

· The configuration of the FM200 Plus HV unit is specified in the Fleet Manager application software. It includes the selection of
devices connected to each input, and the events associated with data measured on specific inputs.

· More details can be found in the Fleet Manager application software documentation, or online help.

· Once the vehicle configuration has been defined, it is loaded onto the Vehicle Plug and transferred to the vehicle by inserting
the plug into the vehicle’s code plug socket.

· Please refer to the document “FM200 Plus Beep and Flash Codes” for an explanation of the audible and visible signals
generated by the FM200 Plus HV

· The latest documentation, firmware and application information can be obtained from http://www.mixtelematics.com

Setting the Real Time Clock

The Real Time Clock in the FM200 Plus HV must be set to the local time. This is done using the blue Driver Plug and either the
FM Dealer Utility of Fleet Manager application software. The correct date and time is then loaded into the FM200 Plus HV by
inserting the Driver Plug into the vehicle’s code plug socket.

Speed and RPM Calibration

Vehicle speed and RPM signals are calibrated using the violet calibration plugs labelled “SPD CAL" and “RPM CAL",
respectively. The calibrations can be performed using either the default settings on the calibration plug, or by selecting specific
values using the FM Dealer Utility. Before calibrating, the blue driver plug should be initialised and inserted in the vehicle socket,
and the ignition should be switched on.

956
www.mixtelematics.com

956
 957

Engine Speed (RPM) Calibration

Default Settings

The “RPM CAL” plug is pre-programmed for use at 1000 RPM.

· Disarm the system using the blue driver plug.

· Insert the “RPM CAL” violet plug into the code plug sockets (the LED should flash once for every 50 pulses received, and the
buzzer should sound in a one second on, one second off cycle).

· Start the engine.

· Increase engine speed to 1000 RPM and keep it constant for a few seconds.

· Remove the violet plug from the socket.

· The unit will beep three times, indicating that it has been calibrated successfully.

· The FM200 Plus HV will be calibrated to the engine speed of the vehicle.

Custom Settings

The “RPM CAL” plug can be programmed with custom calibration values.

· Disarm the system using the blue driver plug.

· Measure the exact frequency of the RPM signal using the appropriate measurement tools.

· Set the “RPM CAL” plug to the measured frequency using the “FM Dealer Utility” software.

· Disarm the system using the blue driver plug.

· Turn the ignition on.

· Insert the calibration plug into the code plug socket.

· The unit will beep three times indicating that it has been calibrated successfully.

Vehicle Speed Calibration

Default Settings

The "SPD CAL" plug is pre-programmed for use over 10 meters. This value can be changed using the FM Dealer Utility software.
During calibration, the LED will flash as speed pulses are received, and the unit will beep in periods of one second. When the
plug is removed the unit will beep three times.

· Disarm the system using the blue plug.

· Drive to the beginning of a measured 10 meter distance.

· Insert the violet plug labelled "SPD CAL" into the code plug socket (the LED should flash once for every 50 pulses received,
and the buzzer should sound in a one second on, one second off cycle).

· Drive the measured 10 meters.

· Remove the violet plug from the vehicle interface.

957
www.mixtelematics.com

957
 958

· The FM200 Plus HV unit is now calibrated with the correct distance to pulse ratio.

Custom Settings

The “SPD CAL” plug can be programmed with custom calibration values.

· Measure the exact distance to pulse ratio using the appropriate measurement tools.

· Set the speed calibration plug “SPD CAL” to the correct distance to pulse ratio using the FM Dealer Utility software.

· Disarm the system using the blue driver plug and turn the ignition on.

· Insert the calibration plug into the code plug socket.

· The unit will beep three times indicating that it has been calibrated successfully.

Testing Installation
Test Drive

· Disarm the system by inserting the blue plug into the Code Plug socket.

· Wait for the audible signal.

· Remove the plug.

· Start the engine.

· Carry out a test drive.

Extract and Transfer Data

· After the test drive, turn off the ignition.

· Wait for the system to arm, indicated by the LED on the code plug socket flashing.

· Insert the green vehicle plug into the code plug socket.

· A beep indicates the start of data transmission.

· The LED on the code plug socket flickers during data transfer.

· A one second beep indicates data transmission is complete.

· Remove the green vehicle plug.

· Insert the vehicle plug into the download module.

· Transfer the data to the PC using the Fleet Manager application software.

· Consult the Fleet Manager application software documentation for further details.

Troubleshooting
· A large assortment of application information in the form of Knowledge Base Articles (KBA’s) can be accessed from the
Support section of: http://www.mixtelematics.com

958
www.mixtelematics.com

958
 959

· Other application documents can be found on the Fleet Manager CD, or downloaded from http://www.mixtelematics.com

· The audible and visual signals generated by the FM200 Plus HV are described in the document: “FM200 Plus Beep and Flash
Codes”

LED does not Flash No Battery voltage applied to FM200 Plus HV · Check the voltage supply to FM200 Plus
HV

· Check fuse

FM200 Plus HV remains armed The blue driver plug is not enabled for the · Use the correct driver plug
and vehicle cannot be started. vehicle
· Enable the Driver Plug for the vehicle

Recorded vehicle data is The FM200 Plus has not be calibrated · Calibrate the FM200 Plus HV inputs
incorrect correctly

Date or Time of Trips are The clock in the Fleet Manager 200 Plus is not · Insert blue driver plug for identification
incorrect set.

Buzzer sounds when turning on Driver has not been identified or · Enable Blue driver plug for the vehicle
the ignition
Driver is not authorised to drive this vehicle · Configure vehicle not to beep when driver is
not identified.

Maintenance
The FM200 Plus HV unit is maintenance-free.

Please ensure that the Code Plug socket is kept clean and free of dust and dirt (if damaged this socket can be replaced).

FM200 Plus HV Specifications

Parameter Specification

Minimum operating battery voltage 17 Volts DC (Typical)

Maximum operating battery voltage 120 Volts DC (Positive drive will be internally switched off at typically 115V)

Typical stand-by current consumption 30mA

Storage temperature range - 20 ºC (- 4 ºF) to + 70 ºC (+ 158 ºF)

Working temperature range - 40 ºC (- 40 ºF) to + 80 ºC (+ 176 ºF)

Maximum non-condensing humidity 95% Relative

Serial Port type - S1 TTL compatible master/slave bus

Serial Port type - S2 & S3 RS-232 Port (TX, RX, CTS & RTS)

959
www.mixtelematics.com

959
 960

Non-volatile backup memory 8kB FRAM

Real-Time-Clock backup power Lithium Battery

Non-volatile memory 1MB Flash

Interrupter relay – max continuous contact current 30A

Interrupter relay - max switching contact current 60A (for 3 max seconds)

Interrupter relay – Max Relay Interrupting Current 24V – 60A; 36V – 2A; 48V – 1A; 72V – 0.6A; 96V – 0.45A; 110V – 0.4A
(Current flowing immediately before or after the
relay switches)

Relay Drive 1 & 2 – max sink current Internally limited to 150mA (Typical)

Audible indicator External Integrated buzzer

Code Plug interface I2C bus

Speed sensor power supply nominal voltage 11V DC (Typical)

Speed sensor power supply max current Internally limited to 35mA (Typical)

Positive Drive - nominal output voltage Typical: 12V DC (no Load) 11VDC (maximum load)

Positive Drive - typical continuous supply current Total: 1 amp DC

External devices: 500mA

Maximum number of frequency inputs 4

F4 input Shared with I8 input

Frequency input waveform: F1(Speed), F2(RPM), Square / Sine wave

F3 & F4

Frequency signal offset voltage range - 15 Volts to + 15 Volts from DC

Frequency signal peak-to-peak voltage minimum See table below

Frequency signal duty cycle range 1% - 99% (non 50% duty cycle waveforms will be further limited in
maximum frequency)

Frequency input impedance Dependant on jumper position (See Jumper Selection Table)

Maximum signal frequency: F1 - F4 See table below

Frequency Input Protection: F1- F4 +/- 500V spike, +/- 110V DC

Maximum number of Analogue inputs (can be used 8

960
www.mixtelematics.com

960
 961

as digital inputs with settable thresholds)

Digital / Analogue Input 8 (I8) Shared with F4 input

Trigger voltage 0 – 117 Volt (programmable from application software, using four different
voltage ranges)

Resolution (0 to +117V signal range) 460 mV

Resolution (0 to +84V signal range) 330 mV

Resolution (0 to +38V signal range) 150 mV

Hi-Resolution (0 to +5V signal range only) 20 mV

Input impedance =104.3 K?

Input Protection Immunity –2kV fast transients (DIN EN61000-4-4)

400V voltage transients (<1 Second, not more than 1 pulse every 10
seconds)

220 Volt DC/RMS

Enclosure Protection Classification IP 54

Typical maximum frequencies supported for different jumper settings:

P-P Voltage \ Jumper Small Sine Wave Big Sine Wave Small Square Wave Big Square Wave

2V AC Sine Wave 6700Hz 760Hz - -

5V AC Sine Wave 17000Hz 1800Hz - -

10V AC Sine Wave 34000Hz 3700Hz 3100Hz 500Hz

2V DC Square Wave 10000Hz 1100Hz - -

5V DC Square Wave 24000Hz 2600Hz 11000Hz 2000Hz

12V DC Square Wave 60000Hz 6000Hz 5000Hz 800Hz

Typical absolute minimum signal levels for different jumper settings:

Noise Type\Jumper Small Sine Wave Big Sine Wave Small Square Wave Big Square Wave

AC (Sine Wave) – 0.5V 1V 5V 5.5V

Minimum signal level

961
www.mixtelematics.com

961
 962

DC (Square Wave) – 0.35V 0.7V 2.7V 3.5V

Minimum signal level

Typical current consumption at different operating voltages:

Operating Voltage\Current Consumption Out of Trip Mode (Typical) Trip Mode (Typical)

24V 27mA 41mA

48V 17mA 30mA

72V 16mA 25mA

96V 16mA 23mA

110V 16mA 23mA

Note: All specifications are typical and are subject to change without prior notice.

Declarations
Type-Approval

This product conforms to the requirements of Directive 71/245/EEC, as last amended by Directive
95/54/EC.

Type-approval number: e1*72/245*95/54*2551*00

023854

Declaration of Conformity

We declare on our own responsibility that the product is in compliance with following norm(s) or documents:

DIN EN 55022 (11/2001)

DIN EN 61000-6-2 (03/2000)

FM Part Numbers

Part Number Description

X10.723-002-021 FM200 Plus HV Kit

X39-723-002-090 FM200 Plus HV Vehicle Unit

X39.723-002-081 FM200 Plus Wiring Harness

X39.723-002-082 FM200 Plus Serial Cable

X39.723-002-033 Code Plug 256k (same as FM200)

962
www.mixtelematics.com

962
 963

X39.723-002-057 Code Plug 96k (same as FM200)

X39.723-002-007 Code Plug 32K (Same as FM100 - Jobs & Fast downloads of recent data)

X39.723-002-006 Driver ID Plug (same as FM200 and FM100)

X39-723-002-054 Passenger Plug

X39.723-002-005 Code Plug Harness

X39.723-002-031 Metal housing FM200 Plus (for protection against tampering)

X39.723-002-079 Fleet Manager Application Software

X39.723-002-009 Download Module

X39-723-002-069 FM200 - GPS Interface

X39.723-002-028 Calibration Set (Violet Code Plug set)

X10.723-002-022 FM200 Plus Waterproofing Kit

X39.723-002-091 FM200 Plus Waterproof Serial Cable

X39.723-002-092 FM200 Plus Waterproof Antenna

X10.723-002-017 FM Impact sensor (For monitoring and detecting impacts)

X10.723-002-009 FM Info (Fleet logbook, visual indication of vehicle exceptions)

X10.723-002-005 FM Terminal (Keyboard/screen for jobs/messaging, Fleet logbook, etc)

X10.723-002-016 FM Keypad (for making phone calls and Fleet logbook)

X10.723-002-014 FM Trailer ID (For logging and identifying trailer connection)

X39.723-002-077 FM TCO (for connecting to a non-optical tacho graph interface)

963
www.mixtelematics.com

963
 964
7.15.5.8 FM200 Plus Serial Cable User Manual

© 2008 MiX Telematics | Updated 2008/06/25

Product Description
The FM200 Plus Serial cable facilitates the connecting of two standard RS232 Data Communication Equipment (DCE) devices
and a Fleet Manager Terminal to the FM200 Plus on-board-computer.

Packet Contents

The FM200 Plus Serial Cable is supplied with the following components:

· FM200 Plus Serial Cable

· FM200 Plus Serial Cable User Manual

· Screwlock Assemblies

Installation
To install the FM200 Plus Serial Cable:

· Connect the grey 16-way connector to the FM200 Plus.

· Connect the first DCE device to the 9-pin-plug marked S2 after removing the dust cover, and secure with the supplied
screwlock assembly.

· Connect the second DCE device to the 9-pin-plug marked S3 after removing the dust cover, and secure with the supplied
screwlock assembly.

· If an FM Terminal is fitted, plug the RJ45 connector into the FM Terminal PWR socket.

· Power and GND wires are provided for easy installation of external GPS and GSM devices. The RED wire is the FM200 Plus
Positive Drive supply line and is under the control of the FM200 Plus . 1 Ampere DC is available on average on this line. The
available current will be reduced if a daughter board is fitted. The Brown wire is GND.

· The Green and Yellow wires are reserved for future use

964
www.mixtelematics.com

964
 965

FM200 Plus Serial Cable Connector Configuration

The FM200 Plus Serial Cable provides a standard 9 pin RS232 interface with the following configuration:

9 Pin Male Name Function FM Splitter Application

1 NC No Connection Not used

2 RD Receive Data Receive serial data from DCE device

3 TD Transmit Data Send serial data to DCE device

4 DTR Data Terminal Ready Looped back to DSR

5 SG Signal Ground Signal Ground

6 DSR Data Set Ready Looped back to DTR

7 RTS Request to Send Output from FM200

8 CTS Clear to Send Input from DCE device

9 NC No Connection Not Used

965
www.mixtelematics.com

965
 966
7.15.5.9 FM200 Plus Waterproof Serial Cable Installation and User Manual

© 2008 MiX Telematics | Updated 2008/05/07

Product Description
The FM200 Plus Waterproof Serial cable facilitates the connecting of two standard RS232 Data Communication Equipment
(DCE) devices and a Fleet Manager Terminal to the Fleet Manager Range of on-board-computers.

Package Contents

The FM200 Plus Waterproof Serial Cable is supplied with the following components:

· FM200 Plus Waterproof Serial Cable.

· Silicone seal.

· FM200 Plus Waterproof Serial Cable User Manual.

· Screw-lock Assemblies.

· DB9 dust covers x 2.

Installation
To install the FM200 Plus Waterproof Serial Cable:

· Open the FM200 Plus Waterproofing Housing by undoing the screws at the bottom of the housing.

· Remove the middle seal in line with the 16 way Amp connector by undoing the 2 screws and removing it.

· Remove the grey 16-way Amp connector from the Fleet Manager product (if this connector has wires leading out of the main
waterproof connector that cannot be freed, then secure the unused connector, or cut and insulate the unused wires).

· Align the silicone seal carefully on the harness and ensure correct seating.

· Insert the grey 16-way connector at the end of your FM200 Plus Waterproof Serial cable through the middle hole (now
exposed) in the housing.

· Ensure that the connector has been securely plugged in and that the clip has located properly (an audible click can normally be
heard).

· Make sure the seal seals the harness and is aligned with the housing.

· Fasten the two screws securing the harness connector plug onto the housing. Do not over tighten the screws as the seal does
not use pressure to seal.

· Close the FM200 Plus Waterproofing Housing by tightening the screws underneath the housing.

· Mount the housing using all three bolts. Do not over tighten the bolts, as the housing can crack when using excessive force.

· Cable tie the serial harness to the main harness where it exits the housing to prevent excessive movement and cable fatigue
where the cable enters the housing.

· Connect the first DCE device to the 9-pin-plug marked S2 after removing the dust cover, and secure it with the supplied screw-
lock assembly.

· Connect the second DCE device to the 9-pin-plug marked S3 after removing the dust cover, and secure it with the supplied

966
www.mixtelematics.com

966
 967

screw-lock assembly.

· If an FM Terminal is fitted, plug the RJ45 connector into the FM Terminal PWR socket.

· Power and GND wires are provided for easy installation of external GPS, GSM and other approved devices. The RED wire is
the FM200 Plus HV Positive Drive supply line and is under the control of the FM200 Plus HV. 500 mA DC is usually on this
line. This available current could sometimes be reduced when certain daughter boards are fitted.

· The Brown wire is GND and the Red wire is Positive Drive out

· The Green and Yellow wires are reserved for future use.

FM200 Plus HV Serial Cable Connector Configuration

The FM200 Plus HV Serial Cable provides a standard 9 pin RS232 interface with the following configuration:

9 Pin Male Name Function FM Splitter Application

1 NC No Connection Not used

2 RD Receive Data Receive serial data from DCE device

3 TD Transmit Data Send serial data to DCE device

4 DTR Data Terminal Ready Looped back to DSR

5 SG Signal Ground Signal ground

6 DSR Data Set Ready Looped back to DTR

7 RTS Request to Send Flow-Control output from FM200

8 CTS Clear To Send Flow-Control input from DCE device

9 NC No Connection Not used

967
www.mixtelematics.com

967
 968

Waterproofing

The FM200 Plus HV Serial Cable is waterproof at the waterproof seal of the FM200 Plus water proofing housing to level IP66.
The ends of the cable S1, S2 and S3 as well as the four wire ends are not waterproof and care should be taken to keep them dry
or sealed.

Do not cut the cable short and leave the ends exposed for water to penetrate the centre of these cables. Water can seep down
the centre of the cable into the housing. Always ensure that the ends of the cable face down to help prevent water entering the
cable.

The two DB9 connectors S2 and S3 and the FM Terminal RJ45 connectors are not corrosion resistant. It is possible for them to
corrode if left exposed to high levels of moisture and condensation.

Some chemicals can affect the outer insulation of the cable, causing it to crack, which could let water penetrate the centre of the
cable and seep into the housing. Please install the cable in such a way that it is not exposed to unknown chemicals that could
affect the outer cable insulation.

968
www.mixtelematics.com

968
 969
7.15.5.10 FM200 Plus Waterproofing Kit

© 2008 MiX Telematics | Updated 2008/05/07

Product Description
The FM200 Plus Waterproofing Kit facilitates the waterproofing of all FM200 Plus products. All Fleet Manager products that have
the same form factor as the FM200 Plus will fit into this housing.

Package Contents

The FM200 Plus Waterproofing Kit is supplied with the following components:

· FM200 Plus waterproof housing lid.

· FM200 Plus waterproof housing base.

· FM200 Plus waterproof housing silicone main seal.

· FM200 Plus waterproof harness.

· FM200 Plus waterproof harness silicone seal.

· 2 x auxiliary harness silicone seals

· 2 x auxiliary harness plastic covers

· 3 x silicone feet

· 6 x harness plastic screws

· FM200 Plus Waterproofing Kit User Manual.

· 3 X M5 30mm machine screws

· 3 X M5 10mm flat washers

· 3 X M5 25mm flat washers

· 3 X M5 nylock nuts

· 6 X 16mm plastic screws

· 10 X 3m™ Scotchlok™ gel-filled wire crimps

· 1 x adhesive lined heat shrink (200mm)

· 1 x adhesive lined heat shrink (120mm)

· 1 x black spiral binding (2 metre)

· 1 x wired fuse holder

· 2 X 3A high voltage slow-blow fuse

· PCB mounting screw

Installation

969
www.mixtelematics.com

969
 970

To install the FM200 Plus Waterproofing Kit:

· Plan your installation. The equipment is sensitive to moisture, fluids, static electricity and metal surfaces. Please handle the
bare PCB’s with care.

· Find a suitable mounting place for the housing. Do not mount the unit near excessive heat sources or where unknown
chemicals may attack the plastic or seals.

· Open the FM200 Plus housing and remove the unit. Do not place the PCB on any metal surface or conductive surface.

· Keep the unit and waterproof housing clean and dry.

· Place the PCB into base of the waterproof housing by locating the back of the PCB onto the PCB supports, then push the PCB
clip forward and push the PCB downwards.

· Ensure that the PCB clip locks on top of the PCB.

· Use the PCB 2.5mm mounting screw provided to secure the PCB through 4mm hole in the right-hand front corner of the PCB.

· Locate the main harness seal and place it onto the main harness (note the orientation).

· Connect the main harness to the unit by plugging in the harness connector into the PCB. Make sure the silicone seal is aligned
and seated.

· Secure the harness seal using 2 of the harness screws.

· If you have auxiliary harnesses, follow the instructions supplied with these harnesses carefully to install them properly.

· Find the two auxiliary harness connector plugs and auxiliary silicone seals.

· If GSM or other modules are used, insert all SIM cards, battery packs etc. carefully by following the instructions provided with
these components.

· Align the seals and harness connector plugs and secure them using the harness screws.

· Align and seat the main housing seal onto the base and fit the housing lid.

· Secure the housing lid using all of the housing screws provided.

· Mount the unit, ensuring that the auxiliary harness holes are sealed and the screws are secure (preferably mount the housing
vertically, with the harnesses exiting the housing downwards).

· Cable tie the harnesses together where they exit the housing to prevent excessive movement and stress on the harness seals.

· Mount the housing using the supplied machine screws, washers, and nylock nuts (3 x M5 machine screws, 3 x 10mm M5 flat
washers, 3 x 25mm flat M5 washers, 3 x nylock nuts) through the 3 mounting holes provided. The large washers are provided
to give extra support when mounting the product on a thin or weak surface.

· Route all cables carefully to prevent chafing or damage. Use the spiral binding for neatness and to keep the cables together.

Water-Resistance

Please note that the ends of the cables S1, S2 and S3 as well as all the wire ends are not waterproof and care should be taken to
keep them dry or sealed. This is to minimize the chance of water seeping between the wire conductor strands and into the
product housing over an extended period of time. The Hot Melt adhesive lined heat shrink tubing is provided to help seal the ends
of unused wires, as well as to seal wires that have been joined. This should be used to seal wires that are too thick to accept the
waterproof Scotchlok™ crimps provided. It also helps prevent corrosion of solder that has been used to join wires. A hot air heat
gun (or similar heat source) is best suited to shrinking this heat shrink. The installer should ensure the heat shrink is shrunk
tightly over the conductor, and that the hot melt has insulated the connection.

970
www.mixtelematics.com

970
 971

If installed, the two DB9 connectors S2 and S3 and the FM Terminal connector (S1) are not corrosion resistant and it is possible
for them to corrode if left exposed to moisture or condensation. Steps should be taken to keep these dry at all times.

Some chemicals may affect the outer insulation of the cables, causing them to crack. This can allow water to penetrate the
conductor strands and to seep into the housing over an extended period of time. Install the cable in such a way that it is not
exposed to chemicals that could affect the insulation.

For antennae that are not corrosion resistant, steps should be taken to insulate and protect these from high levels of moisture.

Waterproofed antennae and serial cable assemblies are available separately, so customised waterproofing of is not required or
recommended. It is not recommended that installers create their own sealed assembly because the use of hot melt adhesive heat
shrink or silicon sealant to seal the product in an uncontrolled environment has not been approved. Doing so may compromise
the water resistance of the product.

Please note:

1. The supplied gel-filled Scotchlok™ crimps will speed up installation and will provide a reliable watertight seal of joined wires.
Ensure that the correct 3M™ tool (part numbers: E-9Y, E-9E, or E-9BM available from your local 3M™ agent) is used when
securing these crimps – other tools that have not been designed for these crimps will result in an unreliable connection. More
crimps can be purchased from 3M™ using the “UB2A” part number.

2. Do not cut the cables or wires short or leave the ends exposed for water to penetrate the centre of these cables, as water can
seep down the centre of the cable into the housing. Always ensure that the ends of the cable face downwards to prevent water
entering them, and seal them using appropriate methods (such as with adhesive lined heat shrink).

Waterproof Crimps

Ensure the correct 3M™ tool (part numbers: E-9Y, E-9E, or E-9BM available from your local 3M™ agent) is used when securing
these crimps. Other tools that have not been designed for these crimps may result in an unreliable connection. The reason for
this is that when closed, the width of the crimping tool jaws must be accurately limited to 5mm, and at this point, they must be
perfectly parallel (see picture below).

Please note: The maximum specifications for the wire Insulation is 0.082" (2,08 mm). AWG range is 19 to 26 (0,4mm to 0,9mm)
solid wire.

Crimping Procedure: (see the 3M™ website or documentation for more details)

1. Cut the FM200 Plus input wire to the required length. Remove all loose wire strands from the end of the wire (the wire should
end with insulated copper).

2. Insert the FM200 Plus input wire into the hole in the crimp (see picture).

3. Clip the crimp over the wire to be intercepted (see picture).

4. Use the correct crimping tool to close the crimp tightly over the two wires to be joined, creating a watertight connection.

Housing Assembly

The housing is designed for easy retro fitting by a qualified installer.

Procedure:

1. Ensure that the housing is open, the harness connector plug is free, and the PCB is loose. Avoid touching the components on
the PCB, as damage may result (it is best to hold the PCB by its edges). Also avoid dropping the PCB, and take extreme care
of it, as failing to do so may result in damage.

2. Clip the PCB into the housing base (ensure back of PCB is under locating bars).

3. Secure the PCB with screw provided (number 15 on assembly diagram).

4. Insert the main harness through the large hole provided. The small FM200 Plus connector should be inserted first, then the

971
www.mixtelematics.com

971
 972

large AMP connector should be inserted, then the two relay connectors should be inserted, and finally the “connector plug”.
The “connector plug” should already be fitted with the seal provided. Silicon based lubricant should be used to lubricate the
seal while inserting it.

5. As the connector plug slides into the hole and seals, the two FM200 Plus connectors should be plugged in.

6. Secure the connector plug with the screws provided (same screws as number 16 shown on assembly diagram). Do not over
tighten the screws, as stripping of the thread or other damage may result.

7. Secure other harnesses in a similar manner using the smaller plug holes (if no other harnesses are provided, use blocked off
connector plugs with the seals provided).

8. Use silicon lubricant to lubricate the main seal (number 5 on assembly diagram), for easy and successful assembly.

9. Holding the top housing portion / lid (number 4 on assembly diagram) facing down, position the seal carefully on the sealing
area – note the up-side of the seal has a curved edge on the connector side (wrong orientation won’t compromise the
waterproof nature of the product). The seal should fit positively in the lid.

10.Lower the housing base carefully (bottom facing up) over the top housing until the housing is closed. Use the 6 screws
provided (number 16 shown on assembly diagram) to close the housing carefully. Do not over tighten the screws, as stripping
of the thread or other damage may result.

11. The housing feet (number 6 shown on assembly diagram) can be inserted into the recesses provided, to reduce vibration
when the housing is mounted on a flat surface.

12.The housing can be mounted and secured on a flat surface using the three screws, washers, and nuts provided.

972
www.mixtelematics.com

972
 973

973
www.mixtelematics.com

973
 974

Specifications

Temperature: -40°C to +85°C (housing resistant to plastic melting and deformation up to 115°C).

Water resistance: IP66*

Weight: 300g (approximate housing only)

Dimensions: 176.6mm X 208.4mm X 55.1mm (W X L X H)

Wall Thickness: 4mm (Typical)

* The product has been designed to withstand being washed with high pressure water jets. It will also typically survive
submersion in water, but this cannot be guaranteed. Practical measures have been taken to ensure the product meets the
waterproof specification, and measures have also been taken to assist the installer with installing the product in a way that will
best maintain this specification. The installer must therefore take responsibility for following the guidelines provided and for taking
additional steps seen fit to ensure that the IP66 specification is maintained.

974
www.mixtelematics.com

974
 975
7.15.5.11 FM200 Plus Wiring Harness User Manual

© 2008 MiX Telematics | Updated 2008/05/07

Pin Colour Name Function Application Information

J1-12 Red BATT+ Battery Power · Connect to vehicle battery.

· Must be protected with a 7.5 amp fuse.

J1-13 Brown GND Ground · Connect directly to vehicle ground.

· Do not tap into an existing ground wire carrying high current.

J1-1 Black IGN Ignition · Connect to vehicle ignition switch.

· Must be protected with a 7.5 amp fuse

J1-19 Blue/White F1 Frequency Input 1 · Vehicle speed signal connected here

· Refer to “Frequency Input Jumper Selection” if signal is not detected

by FM200 Plus

· Connect TCO to only F1 input.

J1-20 Green F2 Frequency Input 2 · Engine speed signal (RPM) connected here

· Refer to “Frequency Input Jumper Selection” if signal is not detected

by FM200 Plus

J1-21 Violet F3 Frequency Input 3 · Connect GPS to only F3 input.

· Move F3 jumper to GPS position, if GPS is connected without using

“FM200-GPS Interface Cable”.

· Refer to “Frequency Input Jumper Selection” if signal is not detected

by FM200 Plus

J1-5 White/ I1 Digital/Analog Input 1 · Maximum signal voltage = 35V.

Violet
· Do not connect signals from inductive sources like relay coils.
J1-6 White/Red I2 Digital/Analog Input 2
· Refer to “Frequency Input Jumper Selection” if signal is not detected
by FM200 Plus
J1-3 White/ I3 Digital/Analog Input 3
Green

J1-4 White/ I4 Digital/Analog Input 4

Yellow

J1-17 White/Black I5 Digital/Analog Input 5

J1-16 White/Blue I6 Digital/Analog Input 6

975
www.mixtelematics.com

975
 976

J1-15 White/ I7 Digital/Analog Input 7

Brown

J1-14 White I8/F4 Digital/Analog Input 8

Frequency Input 4

J1-18 Black White VSPD Speed Sender Power · Supplies power to a speed sensor

· Output voltage typically 11V

· Load current must not exceed 35mA

· Output controlled by FM200 Plus and selected in Vehicle Properties.

J1-22 Brown/Red EXT Relay Drive 1 · Connect the ground side of an external relay coil here.
DRIVE 1
· Relay operation is controlled by the FM200 Plus and is specified in
Vehicle Properties.

· Coil current must not exceed 150mA

J1-11 Brown/ EXT Relay Drive 2 · Connect the ground side of an external relay coil here.
Black DRIVE 2
· Relay operation is controlled by the FM200 Plus and is specified in
Vehicle Properties.

· Coil current must not exceed 150mA

J3 Black IMM1A Starter interruption · Connect to ignition switch side of starter circuit, if starter interruption
is required.

· Do not interrupt high current side of starter circuit.

J4 Black IMM1B Starter interruption · Connect to ignition switch side of starter circuit, if starter interruption
is required.

J1-2 Black GND Code Plug Ground · Connected directly to code plug socket connector.

J1-8 Green CPDATA Code Plug Data · No additional connection required.

J1-9 Red CPPOWE Code Plug Power

R

J1-10 White LEDOUT Code Plug Socket

LED

J1-7 Brown BUZ Buzzer Power · Connected internally

· No additional connection required

976
www.mixtelematics.com

976
 977
7.15.5.12 How to connect FM Dayton to FM200 Plus

© 2008 MiX Telematics | Updated 2008/05/07

Overview
VDO Dayton has a range of powerful state-of-the-art navigation computers utilizing GPS satellite information to guide a vehicle
from its current location to a destination address specified by the driver. The PC 5XXX pro range has a serial interface (RS-232)
allowing it to communicate with an external device.

FM Fleet Manager has a range of powerful state-of-the-art fleet management onboard computers that monitor and log a variety of
sensor and instrument data such as speed, door switches and GPS location. These also function as an extensible
communications and computing resource. A serial interface allows communication with external devices.

FM has integrated these two powerful devices to enable remote navigation and messaging functionality, allowing the FM Fleet
Manager Professional software to manage the sending of text messages and jobs with addresses to the vehicle, then displaying
these interactively on the VDO Dayton unit.

Installation Requirements
The following VDO Dayton navigation computers are supported: PC 5100 pro, PC 5510 pro and PC 5400 pro.

The following FM Fleet Manager on-board computers are supported: FM200 Plus, FM200 Communicator, FM300 ComLink-GSM
and FM300 Communicator.

The following interface cable is required for VDO Dayton: CA 5100COM

The following interface cable is required for FM Fleet Manager: FM200 Plus Serial Harness or FM300 Serial Harness

In some cases you may need a RS232C serial extender cable. These are available in various lengths for most retail outlets that
sell computer accessories.

The VDO Dayton Pro series comes pre-installed with the required Communications Interface (CCI) software. However it is
recommended that you check that you have the latest version installed.

The Fleet Manager Dealer software available on the FM website has the latest required Fleet Manager firmware.

Installation Instructions
Locate the serial connection (C3) at the rear topmost right hand corner of the VDO Dayton navigation computer .

977
www.mixtelematics.com

977
 978

Connect the FM200 Plus Serial harness to the S3 port (shortest cable).

With the FM300 Serial harness, S3 is the only port available to connect to.

Making up a direct interface cable to reduce costs

In many cases when a longer cable is required it is difficult to channel the serial connectors in the vehicle. Manufacturing the
cable only requires three wires to be connected between the VDO Dayton blue Audi type plug supplied with the VDO Dayton and
a standard 9-pin female D-type connector (readily available). The table below shows the wiring configuration for a serial cable.

PC 5XXX PRO (C3 Blue connector FM OBC 9-pin female D-type connector
(S3)

GND Pin 15 Pin 5

Rx Pin 17 Pin 3

Tx Pin 19 Pin 2

978
www.mixtelematics.com

978
 979
7.15.6 FM200 CAN

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The FM200 CAN is based on the FM200Plus, all the FM200Plus functionality is available on the FM200 CAN. The FM200 CAN is
fitted with an on-board CAN module which allows it to communicate on two discrete CAN buses.

Installation
Notes on Installation

1. The FM200 CAN is already loaded with compatible device drivers.

2. The unit still needs to be configured for the vehicle in which it will be installed and the vehicle ID and odometer need to be
configured.

3. It is important to select the correct mounting location for the FM200 CAN. Do not mount close to air ducts that can channel
cold or hot air directly onto the unit.

4. Do not twist the FM200 CAN unit if mounted on an uneven surface.

Connection

1. The FM200 CAN has two CAN buses with which it may communicate.

2. The primary CAN bus comprises pins 11 and 16 on the Serial Harness. It is designated by a yellow wire and a green wire. If
they are not already twisted, they should be twisted together.

3. The secondary CAN bus has its own connector and associated harness, located on the front faceplate of the FM200 CAN
directly above the relay contacts.

4. Colour coding of the buses is shown in the table below:

CAN Interface CAN-HIGH CAN-LOW

Primary CAN Interface Yellow Green

Secondary CAN Interface Yellow Blue

979
www.mixtelematics.com

979
 980

CAN daughterboard Jumper settings (J11)

Jumper Position Jumper Function

1 K-Line (Connect jumper to enable K-Line communications, which override CAN channel 1). Note: When this
jumper is connected, please remove the other four jumpers (Jumper 2 - Jumper 5).

2 Terminate CAN Channel 1 - Connect jumper to switch in 120 Ohm Terminating Resistor for channel 1.

3 Terminate CAN Channel 2 - Connect jumper to switch in 120 Ohm Terminating Resistor for channel 2.

4 CAN Channel 1 Silent Mode - Remove jumper to ensure no transmission of CAN messages on channel 1.

5 CAN Channel 2 Silent Mode - Remove jumper to ensure no transmission of CAN messages on channel 2.

Beep and Flash Codes

Upon insertion of a CAN Diagnostic Plug, the FM200 CAN will beep and flash the LED on the code plug socket in accordance
with the table below to provide diagnostic information:

CONDITION BEEP AND FLASH CODE DURATIONS

CAN Daughter Board No Beeps

detected by FM200Plus
1 second on, 1 second off

CAN Communications 1 double beep per second

detected by FM200Plus
1 second on, 1 second off

A CAN Diagnostic Plug may be created from a standard 128 byte code plug using the FM Dealer Utility, version 8.3.1.0 or later.

980
www.mixtelematics.com

980
 981

7.16 FM300
7.16.1 FM300 ComLink-GSM

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The FM300 ComLink-GSM, the latest on-board computer on the market, provides a comprehensive fleet management solution.
The unit combines extensive driver and vehicle management with advanced communication functionality.

An internal GSM/GPRS modem that allows remote communication between the vehicle and your office enables you to receive
real-time notifications of events, to perform remote downloads of driver and vehicle data, and to perform configuration uploads -
all without physical access to the vehicles.

The modularity of the FM300 ComLink-GSM allows you to connect additional accessories and information systems such as an
optional headset and external keypad. The headset receives incoming calls, ensuring the driver remains focused on the road,
contributing to enhanced communication and safety. Other accessories such as additional sensors, including accident recorder,
tachographs and sensors for load or fuel measuring improve the maintenance and efficiency of your fleet dramatically.

Features

Communication

Downloading to / uploading from Use the GSM/GPRS Modem to download data to and upload data from the FM300
vehicle ComLink-GSM.

Voice Calls Incoming voice calls are possible with an optional headset, keypad and cable.

Vehicle and Driver Management

Trip Data Recording The following data is recorded: date and time, distance travelled, journey duration, vehicle
speed, engine speed (RPM), journey departure and arrival time, driver name, driver ID,
vehicle ID.

Driving Violations The following standard violations are recorded: over speeding, over revving, green band
driving, harsh braking, harsh acceleration, excessive idling and overtime driving.

Customised Events Define customised events, such as driver door opening, hazard lights activated and

981
www.mixtelematics.com

981
 982

refrigerator temperature exceeded.

Second-to-Second (Tacho) Data The status of inputs such as speed and RPM is recorded every second. This provides
valuable in-depth information for accident analysis.

Servicing and Licensing Set reminders for your vehicle’s next service or for your vehicle/driver license expiry.

Driver Identification & Use a driver tag to identify the driver. A default driver can be assigned to a vehicle. An
Immobilisation immobiliser function ensures the car only starts if an authorised driver inserts his driver tag.

Warning Buzzer Set a warning buzzer to sound when driving violations or events take place.

Technical Information

8 configurable analogue or digital Configured to monitor any device that generates a change in voltage, e.g. seat belts,
inputs headlights, refrigeration units, emergency lights, doors, PTO, UDS, trailer coupling etc.

4 auxiliary frequency input Configured to monitor any device that generates a change in frequency e.g. temperature
sensor, liquid flow measurement or as a pulse counter e.g. electronic fuel consumption
measurement (EDM).

1 Auxiliary relay drive Used to switch a relay with a current consumption of up to 150 mA.

2 Serial interface (1x RS232 and

Connected to any TTL or RS232 serial device using the FM Serial cable (e.g. FM Terminal).
1x TTL)

Ignition input Used to monitor the ignition switch status.

Positive drive output Used to power external devices. It can supply current up to 500mA.

Buzzer output Signaling device

Audio interface This interface allows the user to make voice calls using a headset, keypad and cable.

The FM300 ComLink-GSM Kit Includes

· Electronic Module with integrated GSM/GPRS module.

· GSM/GPRS Antennae.

· Main harness with integrated buzzer (2x frequency input, 3x digital/analogue input).

· FM300 code plug-harness including vehicle interface.

· Blue driver’s key (driver log-on).

· FM on-board computer user manual.

· Optional harnesses: I/O harness (2x frequency input, 4x digital/analogue input), serial harness, voice harness.

Software

982
www.mixtelematics.com

982
 983

Fleet Manager Professional 9 provides the serious fleet operator with extensive fleet management tools to manage and report on
his fleet. The software enables you to manage vehicle, driver and passenger information, define and manage events to be
monitored, analyse fleet data and do extensive management reporting. In addition to the core software, Fleet Manager
Professional 9 also offers a set of extensions that allow additional monitoring and reporting on the fleet.

Our Internet Bureau Service, FM-Web, also supports the FM300 ComLink-GSM.

983
www.mixtelematics.com

983
 984
7.16.2 FM300 Communicator

© 2008 MiX Telematics | Updated 2008/05/07

Overview

The Fleet Manager 300 Communicator (FM300 Communicator) is an on-board computer based on the stable and reliable FM200
Plus platform. The FM300 Communicator offers the same extensive driver and vehicle management as FM200 Plus and has an
additional internal GPS receiver and GSM/GPRS modem.

The GPS receiver allows the recording of GPS position information, enabling you to determine the movement history of the
vehicles. The GPS receiver in conjunction with the GSM/GPRS modem allows active tracking of vehicles, allowing you to request
their position at any time. In addition the GSM/GPRS modem provides real-time notifications of user specified events such as the
time arrived at a specified location.

Remote data upload and download to and from your FM300 Communicator with the GSM/GPRS Modem ensures that data
transfer does not interfere with the daily activities of the fleet. An optional headset that receives incoming calls ensures the driver
remains focused on the road, contributing to enhanced communication and safety.

Security concerns are addressed with the provision of an optional battery backup that allows uninterrupted communication with
the Fleet Manager Software even if the unit’s power is cut.

Features

Location Management

Active/ Passive Tracking or Active Trail Request the vehicle position in real-time or view the route
taken after the trip has been downloaded. Active Trail allows
hourly updating of the Fleet Manager software with GPS
vehicle positions.

GPS Data Recording A variety of information is recorded with every GPS point, e.g.
vehicle and driver ID, date and time, latitude and longitude,
altitude, heading, velocity, number of satellite etc.

Manage Locations Add any desired location such as customer, supplier or no-go
zones.

Route Planning Plan routes by entering stops, start times and duration of each
stop. This can serve as daily job activity sheets for your drivers.

984
www.mixtelematics.com

984
 985

Active Events Receive data messages such as SMS when selected standard
or user-defined events occur, e.g. a cargo door opening in a
no-go zone, driver arrived at customer location.

Communication

Use the GSM/GPRS Modem to download data to and upload

data from the FM300 Communicator. The modem also enables
Downloading to / uploading from vehicle
active tracking of the FM300 Communicator by the Fleet
Manager Software.

Voice Calls Incoming voice calls are possible with an optional headset.

Vehicle and Driver management

The following data is recorded: date and time, distance

travelled, journey duration, vehicle speed, engine speed
Trip Data Recording
(RPM), journey departure and arrival time, driver name, driver
ID, vehicle ID.

The following standard violations are recorded: over speeding,

Driving Violations over revving, green band driving, harsh braking, harsh
acceleration, excessive idling and overtime driving.

Define customised events, such as driver door opening, no-go

Customised Events zone entered, hazard lights activated and refrigerator
temperature exceeded.

The status of inputs such as speed and RPM is recorded every

Second-to-Second (Tacho) Data second. This provides valuable in-depth information for
accident analysis.

Set reminders for your vehicle’s next service or for your vehicle/
Servicing and Licensing
driver license expiry.

Use a driver tag to identify the driver. A default driver can be

Driver Identification & Immobilisation assigned to a vehicle. An immobiliser function ensures the car
only starts if an authorised driver inserts his driver tag.

Set a warning buzzer to sound when driving violations or

Warning Buzzer
events take place.

Active Tracking

985
www.mixtelematics.com

985
 986

The internal GPS receiver and GSM/GPRS modem allow active tracking of the FM300 Communicator. You are able to locate and
track your vehicles precisely in real-time. The Fleet Manager software uses either the GSM Short Message Service (SMS) or the
GPRS connection to deliver the real-time information to you.

With active tracking, you can track the current position of your vehicles, locate a vehicle closest to a customer location, or view
the trail as the vehicle moves. In addition, all vehicle location positions are stored in the on-board computer and can be used for
historical or passive tracking.

Communication

The FM300 Communicator allows incoming voice calls where a headset, keypad and cable is connected to the on-board
computer (OBC). This allows the drivers to safely communicate over a head-set, allowing them to focus on the road. The FM300
Communicator is compatible with the Falcom A2-FSE02 Hands Free Unit.

Battery Backup (Optional)

Optional Battery Backup is available if you would like more security. The Battery Backup starts to operate as soon as the supply
to the battery is cut. The battery backup is supplied by a Hi Temp NiMH Battery Pack. The backup time is a minimum of 4 hours
when the GSM/GPRS is active in low power mode and the GPS is disabled.

Activation Management

The unit can be configured to switch itself off. In the switched-off state the unit will only power-up when the ignition line is
switched on. Thereafter it will abide by the conditions defined by the unit configuration.

Technical Information

8 configurable analogue or digital inputs Configured to monitor any device that generates a change in
voltage, e.g. seat belts, headlights, refrigeration units,
emergency lights, doors, PTO, UDS, trailer coupling etc.

986
www.mixtelematics.com

986
 987

3 auxiliary frequency inputs Configured to monitor any device that generates a change in
frequency e.g. temperature sensor, liquid flow measurement or
as a pulse counter e.g. electronic fuel consumption
measurement (EDM). A fourth auxiliary input is connected to
the internal GPS receiver.

1 Auxiliary relay drive Used to switch a relay with a current consumption of up to 150
mA.

2 Serial interface (1x RS232 and 1x TTL) Connected to any TTL or RS232 serial device using the FM
Serial cable (e.g. FM Terminal).

Ignition input Used to monitor the ignition switch status.

Positive drive output Used to power external devices. It can supply current up to
500mA.

Buzzer output Signaling device.

Audio interface This interface allows the user to make voice calls using a
headset, keypad and cable.

The FM300 Communicator Includes

· Electronic Module with integrated GSM/GPRS module.

· GSM/GPRS Antennae.

· GPS Antennae.

· Main harness with integrated buzzer (2x frequency input, 3x digital/analogue input).

· FM300 code plug-harness including vehicle interface.

· Blue driver’s key (driver log-on).

· FM on-board computer user manual.

· Optional harnesses: I/O harness (2x frequency input, 4x digital/analogue input), serial harness, voice harness

Software
Fleet Manager Professional 9 provides the serious fleet operator with extensive fleet management tools to manage and report on
his fleet. The software enables you to manage vehicle, driver and passenger information, define and manage events to be
monitored, analyse fleet data and do extensive management reporting . In addition to the core software, Fleet Manager
Professional 9 also offers a set of extensions that allow additional monitoring and reporting on the fleet.

Our Internet Bureau Service, FM-Web, also supports the FM300 Communicator.

987
www.mixtelematics.com

987
 988
7.16.2.1 FM300 Communicator Installation Manual

© 2008 MiX Telematics | Updated 2008/06/25

Introduction
System Overview

The FM Fleet Manager 300 product range is on-board-computers for use in vehicles and working machines. It is specifically
intended for equipment in the automotive market 12V to 24V. The FM300 is compatible to the FM200 Plus. It is designed to
record a wide range of vehicle and trip related information, including: vehicle speed, engine speed, engine temperature, fuel
consumption, trip start and end times. The FM300 Communicator-Battery has an internal GSM and GPS with Li-ION battery
backup which makes it ideally suited for modern Fleet management where company assets need to be tracked and managed.

The FM300 is used in conjunction with the FM Fleet Manager application software. This software facilitates the management of
vehicle, driver and passenger information, definition and management of events to be monitored by vehicle units, recording of
servicing details, analysis of fleet data and extensive management reporting.

The primary method of communicating with the FM300 will be via GSM/GPRS, it is also possible via the green Vehicle Plug. The
plug is used to extract data from the FM300 and transfer it to a Personal Computer, where it can be processed and analysed by
the FM Fleet Manager application software.

Vehicle drivers are identified by means of a driver specific blue plug; identification can be enforced by interrupting the vehicle’s
starter circuit.

Note: This document will use the word “vehicle”, referring to vehicles and all other types of electrical equipment where the system
may be installed.

Analogue/Digital Inputs

The FM300 is equipped with eight analogue/digital inputs (I1-I8), which can be used to monitor either digital or analogue signals.
The eighth Analogue/Digital input (I8) is shared with the fourth frequency input (F4). Input signal voltage range and resolution is
selectable from the Fleet Manager software. For digital type input signals, switching thresholds can be defined in the software,
which, when crossed, trigger an event that records the specified data. Other actions (including the switching of relays and
warnings) can also be defined.

Frequency Inputs

The FM300 has four frequency inputs, which can be used to record frequency type signals. The fourth frequency input (F4) is
shared with the eighth Analogue/Digital input (I8). Provision is made for a wide range of signal types on F1 and F2. F3 and F4 will
only read TTL signals or signals that changes from 0V to +5V e.g. -5V ~+24V. F3 is connected to the internal GPS, and is not
made available on the harness for the FM300 Communicator.

System Requirements
The FM300 is designed for use in 12V vehicles. Special vehicles and working machines with a 24 to 110 volt DC battery system
will require a voltage converter to facilitate the required 12V~24V. The FM Fleet Manager application software is required to
complete the installation process.

Safety
Before installation

Installer Requirements

· Installation should only be undertaken by a vehicle technician with comprehensive occupation specific knowledge and who has
complete command of the actions required by the occupation.

· Installation by an unqualified technician may adversely affect the operating reliability of the vehicle and could endanger other

988
www.mixtelematics.com

988
 989

road users.

· A basic knowledge of vehicle electrical and mechanical systems is required to successfully install the FM Fleet Manager
system.

· The system should only be installed by a suitably qualified vehicle technician with a basic knowledge of the operation of
computers.

· Installation technicians should attend an FM training course to acquire the skills needed for installation, configuration and
operation of the FM Fleet Manager system.

· Installers should consult the vehicle manufacturer’s documentation for the specific vehicle make and model prior to
undertaking an installation.

· Installers should pay particular attention to the location of fuel systems, hydraulic systems, compressed air systems and other
electrical and mechanical systems, which may have a bearing on the installation.

· Installers should pay attention to any changes to the vehicle’s systems or settings, which should be noted prior to the
installation.

· Installers should refrain from smoking and the use of naked flames, which could cause a fire in or near the vehicle.

Tools

· Standard technical equipment and appropriate tools for use with vehicles are required to install the FM Fleet Manager 300.

· Vehicle specific tools may be required for the removal of consoles and covers.

Secure the workplace

· Remove the ignition key from the vehicle’s ignition lock.

· Ensure that the vehicle’s engine cannot be unintentionally started during the installation.

· Record all data stored in the volatile memory of the vehicle’s systems to ensure that such data can be restored.

· When the negative terminal of the battery is disconnected, all volatile memory will be lost. Please ensure that such information
is recorded prior to disconnection so that systems can be reconfigured correctly.

· Short-circuiting the vehicle’s electrical system may result in fire, explosion of the battery and/or damage to other electrical
systems.

· Electrical shock from high voltage batteries must be avoided, as this may lead to death or injury.

· The negative terminal of the vehicle’s battery should be disconnected before commencing installation. If the vehicle has
additional batteries, it may be necessary to disconnect the negative terminals of these batteries too.

During installation

· Should it be necessary to remove seats, covers or other components, care should be taken to avoid accidental damage and/or
disconnection of cables.

· All components should be checked for damage prior to being installed into the vehicle.

· For small installation openings, a drill should be used.

· For larger openings, a conical milling cutter, compass saw or file should be used.

· All rough edges should be trimmed.

989
www.mixtelematics.com

989
 990

· Careful attention must be paid to the manufacturer’s safety regulations for all tools used.

· Oils and fuels must be collected in appropriate containers and disposed of in accordance with the law.

Positioning of product components

· Installers should ensure that the components of the product do not influence or hamper the functioning of the vehicle’s
systems.

· Care should be taken to ensure that the product’s components are not damaged during installation.

· Ensure that sufficient space is available for all components of the product prior to commencing the installation.

· Ensure that the unit and harness are secured to prevent the harness vibrating differently to the unit at the harness connectors.

· Please note that the voltage of the external relay is rated to the vehicle voltage specification. Do not run a 12V relay at 24V.

· Please pay attention to the routing course of cables and wiring.

· Do not install the product in or near the location of mechanical or electrical airbags.

· Do not drill into supporting or stabilising braces or beams.

Installation of Wiring

· Note the product’s wire gauge cross-sectional area.

· If the wire gauge cross-section is reduced, current density increases which may cause the wiring to overheat.

· Cables should be routed in existing channels and should not be routed parallel to ignition cables or other cables subject to high
current.

· Cables should be fixed with cable-ties or adhesive tape.

· Do not route cables over moving parts.

· Do not fix cables on the steering column.

· Ensure that the cables are not exposed to pulling, pressure or shearing deformation.

· If the cables are routed through drilled holes, rubber grommets or similar protection should be used.

· Suitable cable-strippers should be used to strip insulating material from cables and cable-strippers should be adjusted to avoid
damaging or separating the wire strands.

· Cables should only be connected using solder or suitable crimping lugs.

· A proper crimping tool should be used on all crimping lugs.

· Careful attention must be paid to the manufacturer’s safety regulations for all tools used.

· Insulate all exposed wires to prevent short-circuits (use good quality adhesive tape or the provided heat shrink ).

· Connections to vehicle power supply must be installed with a fuse.

· Be aware that short-circuiting may be caused by faulty connections and crushed or damaged cables.

· Short-circuiting the vehicle’s electrical system may result in fire, explosion of the battery and/or damage to other electrical

990
www.mixtelematics.com

990
 991

systems. To prevent this, all connections carrying current must be soldered and insulated correctly. Other connections such as
the speed signal, RPM signal, brake light or clutch switch can be made with crimping lugs.

· Incorrect connections can lead to short circuits. Connections should only be made in accordance with the vehicle’s wiring
diagram.

· Current and voltage should be measured with a multi-meter or diode test lamp.

· The use of inadequate test equipment may result in the damage to control devices or other electrical systems.

· Route the harness in such a way to prevent water condensation formed on the cable to run into the unit. This can be achieved
by having the harness at a lower point just before it connects to the unit.

· Do not Mount the GSM antenna against a metal surface as this affects GSM reception and transmission.

After Installation

· Reconnect the vehicle’s ground cable to the negative terminal of the battery.

· Re-configure the values in the volatile memory of all systems.

· Check all vehicle functions.

· Explain the functions of the FM300 system to the customer and give the customer the User Manual.

· If a FM300 Communicator-Battery was installed, the Li-ION battery should be inspected annually.

During Operation

· The unit switches on only with IGN.

· The product must be used in accordance with operating instructions.

· Failure to use the product as directed might result in personal injury, material damage and/or damage to the environment.

Installation
Installation Requirements

Please note the requirements specified in the “Safety” section of this document.

Summary of Installation Steps

Step Action Software Tools Other Related Documents

1 Install harness None

2 Install code plug socket None

3 Install GSM antennae None

4 Install GPS antennae None

5 Connect power and signal inputs None

991
www.mixtelematics.com

991
 992

6 Format Vehicle Plug FM Dealer Utility “How To Use The FM Dealer Utility”

7 Initialise Vehicle FM Dealer Utility “How To Use The FM Dealer Utility”

Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

8 Load device drivers (only FM Dealer Utility “How To Use The FM Dealer Utility”
necessary if newer drivers are
available) “Fleet Manager On-Board-Computer User
Manual”

9 Set Vehicle ID on unit (When FM Dealer Utility “How To Use The FM Dealer Utility”
initialised plug)
Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

10 Create new vehicle and define Fleet Manager Application Software Fleet Manager application software
properties documentation or online help

11 Load vehicle configuration Fleet Manager Application Software Fleet Manager application software
documentation or online help

12 Initialise Driver ID plug (only FM Dealer Utility “How To Use The FM Dealer Utility”
necessary if driver identification is
selected) Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

13 Set FM300 date and time (for FM Dealer Utility “How To Use The FM Dealer Utility”
local time)
Fleet Manager Application Software Fleet Manager Application Software Help &
Docs

14 Calibrate Speed and RPM inputs FM Dealer Utility “How To Use The FM Dealer Utility”

15 Test Installation Fleet Manager Application Software Fleet Manager application software
documentation or online help

16 Test GSM using GSM diagnostic Fleet Manager Application Software Fleet Manager application software
plug documentation or online help

17 Test GPS using GPS diagnostic Fleet Manager Application Software Fleet Manager application software
plug documentation or online help

Note: Steps 4, 5 & 6 can be performed in one operation using the FM Dealer Utility.

Beep and Flash Codes

The FM300 status is indicated by audible and visual signals.

See detailed table in the “Fleet Manager On-Board-Computer User Manual” manual for all beep and flash codes.

FM300 Harness Installation

Please read the “Safety” section, of this document before installing the vehicle harness.

992
www.mixtelematics.com

992
 993

Connect the FM300 main harness wires according to the following table:

Pin Colour Name Function Application Information

8 Red BATT+ Battery Power · Connect to vehicle battery +12V to +24V.

· Must be protected with the provided 5 amp slow blow

fuse, or a similar one already present in the vehicles
wiring.

1 Brown GND Ground · Connect directly to vehicle ground.

· Do not tap into an existing ground wire carrying high

current.

13 Black IGN Ignition · Connect to vehicle ignition switch.

· Must be protected with a 7.5 amp fuse

12 Blue/White F1 Frequency Input 1 · Vehicle speed signal connected here.

· Connect TCO to only F1 input.

4 Green F2 Frequency Input 2 · Engine speed signal (RPM) connected here

11 White/Violet I1 Digital/Analog Input 1 · Maximum signal voltage = 38V.

10 White/Red I2 Digital/Analog Input 2 · Do not connect signals from unsuppressed inductive

sources such relay coils (where severe voltage spikes
can be generated).
9 White/Green I3 Digital/Analog Input 3

2 Red/Blue Pos DRV Power to external · Supplies power to a speed sensor

devices
· Output voltage typically BAT -2V

· Load current must not exceed 1A

· Output controlled by FM300 and selected in Vehicle

Properties of the FM Professional software.

5 Brown/Red EXT DRIVE 1 Relay Drive 1 · Connect the ground side of an external relay coil here.

· Relay operation is controlled by the FM300 and is

specified in Vehicle Properties of the FM Professional
software.

· Coil current must not exceed 150mA

6 Brown/Blue Relay Starter interruption · Connect to external relay , provide negative current sink
200mA, if starter interruption is required.

· Do not interrupt starter circuit while current is flowing

(especially at higher voltages than 24V) – the relay
contacts may undergo excessive wear, damage or

993
www.mixtelematics.com

993
 994

arcing and fire may result.

3 Yellow/Green BUZ Buzzer Power · Connected internally

· No additional connection required

7 Green CAN Bus CAN-Low Reserved for future use

14 Yellow CAN Bus CAN-Hi Reserved for future use

Relay 87 BLACK 2mm² RELAY RELAY Switch BLACK 2mm² Relay contact 87 wire

Relay 30 BLACK 2mm² RELAY RELAY Switch BLACK 2mm² Relay contact 30 wire

Connect the FM300 auxiliary harness wires according to the following table:

Pin Colour Name Function Application Information

1 Brown GND Ground · Connect directly to vehicle ground.

· Do not tap into an existing ground wire carrying high current.

8 Violet F3 Frequency Input 3 · Connect external GPS to only input only. (This applies to the
FM300 ComLink-GSM only.

7 White/Yellow I4 Digital/Analog Input · Maximum signal voltage = 38V.

4
· Do not connect signals from unsuppressed inductive sources
6 White/Black I5 Digital/Analog Input such relay coils (where severe voltage spikes can be
5 generated).

5 White/Blue I6 Digital/Analog Input

6

4 White/Brown I7 Digital/Analog Input

7

3 White/ I8/F4 Digital/Analog Input

8

Frequency Input 4

2 Red/Blue Positive Power external · A maximum current of 1A may be supplied to external devices
Drive devices

Connect the FM300 code plug harness wires according to the following table:

Pin Colour Name Function Application Information

1 Black GND Code Plug Ground · Connected directly to code plug socket connector.

994
www.mixtelematics.com

994
 995

4 Green CPDATA Code Plug Data · No additional connection required.

3 Red CPPOWER Code Plug Power

2 White LEDOUT Code Plug Socket

LED

Connect the FM300 serial harness wires according to the following table:

Pin Colour Name Function Application Information

2 DB9 cable CTS2-IN Handshaking S3

3 DB9 cable RX2-IN Data received S3

4 RJ45 cable RX-IN Data received S1

5 RJ45 cable RTS-OUT Handshaking S1

1 Red/Blue POS DRV Power BAT - 2V 1A

7 DB9 cable RTS2-OUT Handshaking S3

8 DB9 cable TX2-OUT Data transmitted S3

9 RJ45 cable CTS-IN Handshaking S1

10 RJ45 cable TX-OUT Data transmitted S1

6 Brown GND OV 1A

Connect the FM300 audio cable harness wires according to the following table

Pin Colour Name Function Application Information

6 Black SPK+ Speaker positive Voice on Hands Free Kit

drive

5 Black SPK- Speaker negative Voice on Hands Free Kit

drive

4 Black GND OV 1A

3 Black MIC- Microphone Voice on Hands Free Kit

negative

2 Black MIC+ Microphone Voice on Hands Free Kit

positive

995
www.mixtelematics.com

995
 996

1 Black Pos DRV Power BAT – 2V 1A

Starter Interruption

The FM300 requires an external relay for the interruption of the vehicle’s starter circuit. The relay required should be adequately
rated for the purpose intended. Please note that a 30A or 40A relay should be selected. A standard 5 PIN automotive relay
manufactured by a reputable supplier would be adequate. The correct relay operating voltage is required for the relay not to be
damaged. 24V relays will not function correctly in 12V applications and 12V relays will be damaged when used at 24V.

To connect the relay it only needs to be plugged into the relay socket on the main FM300 harness. The two 2mm² black wires
represent the two sides of the relay contacts that are controlled via the driver ID Plug. Cut the wires as short as possible where
higher current will be interrupted via the relay.

In addition, use a cable tie to secure the relay through the mounting ear (5mm hole) to the main harness or where possible. If the
relay is secured to the vehicle an M5 lock-nut and bolt is to be used. Ensure that the relay wires have enough play on them not to
strain the relay terminal crimps connecting the relay to the wires.

Do not use a relay with built in diode as this is not required by the FM300 unit.

Code Plug Socket Installation

Note: Please follow the instructions regarding the positioning of product components as contained in the “Safety” section of this
document.

· The Code Plug Socket must be installed inside the passenger compartment or the driver cabin, to protect it from possible
damage by water or other environmental factors.

· The Code Plug Socket should not be installed in or near the ventilation or heating systems, which may cause it to overheat.

· The Code Plug Socket should be installed in a position where it will not be subjected to pressure, impact or excessive vibration.

· Select the installation position carefully before proceeding with the installation.

· Mark and drill or cut the required hole.

· Remove the mounting clip from the socket.

· Remove the protection film from the adhesive surface of the foam ring and press it firmly against the back of the interface.

· Insert the socket into the mounting hole and slide the mounting clip into position.

996
www.mixtelematics.com

996
 997

Hole size = 13/16” - 20 mm

Positioning the FM300 Unit

Note: Please follow the instructions regarding the positioning of product components as contained in the “Safety” section of this
document.

· The FM300 must be installed inside the passenger compartment or the driver cabin to protect it from possible damage by
water, solvents, fuel or other environmental factors.

· The FM300 should not be installed in or near the ventilation, heating system, or hot surfaces which may cause it to overheat or
be damaged by condensed water vapour.

· The FM300 should be installed in a position where it will not be subjected to pressure, impact or excessive vibration. Uneven
surfaces where the box can be deformed or damaged should be avoided.

· Select the installation position carefully before proceeding with the installation.

· Mark and drill the required holes.

· Route cables from the unit to the appropriate senders within the vehicle. Additional information can be found in the “Harness
Installation” section of this document.

· After connecting the system components and performing a system test, mount the vehicle unit securely, making use of the
optional metal armoured housing, if required. The armoured housing is available as a spare part and is used to protect against
tampering.

Signal Inputs
Analogue/Digital Inputs

The FM300 is equipped with eight analogue/digital inputs (I1-I8), which can be used to monitor either digital or analogue signals.
The eighth Analogue/Digital input (I8) is shared with the fourth frequency input (F4). Input signal voltage range and resolution is
selectable from the Fleet Manager software. For digital type input signals, switching thresholds can be defined, in the software,
which, when crossed, trigger an event that records the specified data. Please refer to the “Specifications” and “Harness
Installation” sections of this document for more details.

Frequency Inputs

The FM300 has four frequency inputs which can be used to record frequency type signals. The fourth frequency input (F4) is
shared with the eighth Analogue/Digital input (I8). F3 is connected to the internal GPS, and is not made available on the harness
for the FM300.

Power Outputs
External Relay Drives

· The FM300 has one external relay drive output (Relay Drive 1 ), suitable for controlling an external relay.

997
www.mixtelematics.com

997
 998

· This output is controlled by the FM300 and configured in Vehicle Properties of the Fleet Manager application software.

· The Relay Drive Outputs connect to the ground side of an external relay.

· The maximum current of the external relay is limited to 200mA.

· Please refer to the “Specifications” and “Harness Installation” sections of this document for more details.

Positive Drive

· The Positive Drive output supplies power to FM300 accessories.

· This output is controlled by the FM300 and is configured in Vehicle Properties of the Fleet Manager application software.

· Access to this output is via any FM300 harness or cable.

· Refer to the “FM300 Specifications” section of this document.

· Do NOT connect an external voltage to the positive drive line. This may cause damage to the product.

Serial Communication

· The FM300 is equipped with one TTL (S1) and one RS232 (S3) external serial port.

· The FM300 Serial Cable is required to connect to these ports.

· Please refer to the “Specifications” section of this document and the FM300 Serial Cable documentation for more details.

· S2 is internally connected to the internal GSM engine.

Loading Device Drivers

· The FM300 is supplied with the Operating System, the latest market accepted set of device drivers (at time of manufacture),
and a basic configuration (set for minimum default logging) loaded.

· Before the unit can be configured, ensure that the latest version of FM300 Device Drivers required for the task is loaded.

· The latest Device Drivers are contained in the latest version of the FM Dealer Utility, which can be downloaded from http://
www.mixtelematics.com.

· Load Device Drivers onto either a 256k Vehicle Plug or 256k Device Driver Plug, using the FM Dealer Utility. Refer to the
document “How To Use The FM Dealer Utility”.

· Insert the plug containing the Device Drivers into the vehicle’s code plug socket.

· The device drivers will be loaded onto the FM300 .

· Refer to the document “Fleet Manager On-Board-Computer User Manual” for an explanation of the audible and visible signals
generated by the FM300 .

Note: Make sure the data transfer is complete before removing the plug from the socket. Successful transfer is indicated by two
short beeps. If a different beep sequence is heard, data transfer was unsuccessful and must be repeated. To do this, the vehicle
plug must be re-initialised and the device drivers reloaded onto the plug.

Configuring Vehicle Properties

· The configuration of the FM300 unit is specified in the Fleet Manager application software. It includes the selection of devices
connected to each input, and the events associated with data measured on specific inputs.

998
www.mixtelematics.com

998
 999

· More details can be found in the Fleet Manager application software documentation, or online help.

· Once the vehicle configuration has been defined, it is loaded onto the Vehicle Plug and transferred to the vehicle by inserting
the plug into the vehicle’s code plug socket.

· Please refer to the document “Fleet Manager On-Board-Computer User Manual” for an explanation of the audible and visible
signals generated by the FM300 .

· The latest documentation, firmware and application information can be obtained from http://www.mixtelematics.com.

Setting the Real Time Clock

The Real Time Clock in the FM300 must be set to the local time. This is done using the blue Driver Plug and either the FM Dealer
Utility of Fleet Manager application software. The correct date and time is then loaded into the FM300 by inserting the Driver Plug
into the vehicle’s code plug socket.

Speed and RPM Calibration

Vehicle speed and RPM signals are calibrated using the violet calibration plugs labelled “SPD CAL" and “RPM CAL" respectively.
The calibrations can be performed using either the default settings on the calibration plug, or by selecting specific values using
the FM Dealer Utility. Before calibrating, the blue driver plug should be initialised, inserted in the vehicle socket, and the ignition
should be switched on.

Engine Speed (RPM) Calibration

Default Settings

The “RPM CAL” plug is pre-programmed for use at 1000 RPM.

· Disarm the system using the blue driver plug.

· Insert the “RPM CAL” violet plug into the code plug sockets (the LED should flash once for every 50 pulses received, and the
buzzer should sound in a one second on, one second off cycle).

· Start the engine.

· Increase engine speed to 1000 RPM and keep it constant for a few seconds.

· Remove the violet plug from the socket.

· The unit will beep three times indicating that it has been calibrated successfully.

· The FM300 will be calibrated to the engine speed of the vehicle.

Custom Settings

The “RPM CAL” plug can be programmed with custom calibration values.

· Disarm the system using the blue driver plug.

· Measure the exact frequency of the RPM signal using the appropriate measurement tools.

· Set the “RPM CAL” plug to the measured frequency using the “FM Dealer Utility” software.

· Disarm the system using the blue driver plug

· Turn the ignition on.

999
www.mixtelematics.com

999
 1000

· Insert the calibration plug into the code plug socket.

· The unit will beep three times indicating that it has been calibrated successfully.

Vehicle Speed Calibration

Default Settings

The "SPD CAL" plug is pre-programmed for use over 10 meters. This value can be changed using the FM Dealer Utility software.
During calibration, the LED will flash as speed pulses are received, and the unit will beep in periods of one second. When the
plug is removed the unit will beep three times.

· Disarm the system using the blue plug

· Drive to the beginning of a measured 10 meter distance.

· Insert the violet plug labelled "SPD CAL" into the code plug socket (the LED should flash once for every 50 pulses received,
and the buzzer should sound in a one second on, one second off cycle).

· Drive the measured 10 meters.

· Remove the violet plug from the vehicle interface.

· The FM300 unit is now calibrated with the correct distance to pulse ratio.

Custom Settings

The “SPD CAL” plug can be programmed with custom calibration values.

· Measure the exact distance to pulse ratio using the appropriate measurement tools.

· Set the speed calibration plug “SPD CAL” to the correct distance to pulse ratio using the FM Dealer Utility software.

· Disarm the system using the blue driver plug and turn the ignition on.

· Insert the calibration plug into the code plug socket.

· The unit will beep three times indicating that it has been calibrated successfully.

Testing Installation
Test Drive

· Disarm the system by inserting the blue plug into the Code Plug socket.

· Wait for the audible signal.

· Remove the plug.

· Start the engine.

· Carry out a test drive.

Extract and Transfer Data

· After the test drive, turn off the ignition.

· Wait for the system to arm, indicated by the LED on the code plug socket flashing.

1000
www.mixtelematics.com

1000
 1001

· Insert the green vehicle plug into the code plug socket.

· A beep indicates the start of data transmission.

· The LED on the code plug socket flickers during data transfer.

· A second beep indicates data transmission is complete.

· Remove the green vehicle plug.

· Insert the vehicle plug into the download module.

· Transfer the data to the PC using the Fleet Manager application software.

· Consult the Fleet Manager application software documentation for further details.

Voice\ Handsfree connection

Only use Siemens FM / Telicom HFD-01-01-103 with FM300 voice cable.

GPS antenna connection

· Mount the GPS antenna where the least metal obstruction will occur. For best results place the antenna on a metal surface

· Do not connect the F3 line to external device unless you are using a FM300 ComLink-GSM.

GSM Antenna connection

· Do not mount the GSM antenna against a metal surface this effects GSM communication. The GSM antenna is to be
mounted further than 20cm away from the human body under normal operating conditions.

· Some vehicles require the GSM antenna to be mounted outside the vehicle cabin. Please verify before installing the GSM
antenna.

Troubleshooting
· A large assortment of application information, in the form of Knowledge Base Articles (KBAs) can be accessed from the
Support section of: http://www.mixtelematics.com.

· Other application documents can be found on the Fleet Manager CD, or downloaded from http://www.mixtelematics.com.

· The audible and visual signals generated by the FM300 are described in the document: “Fleet Manager On-Board-Computer
User Manual” .

Symptom Probable Cause Action

LED does not flash No battery voltage applied to · Check the voltage supply to the FM300 .
FM300 .
· Check fuse

FM300 remains armed and The blue driver plug is not enabled · Use the correct driver plug
vehicle cannot be started for the vehicle
· Enable the Driver Plug for the vehicle

Recorded vehicle data is The FM300 has not been · Calibrate the FM300 inputs

1001
www.mixtelematics.com

1001
 1002

incorrect calibrated correctly

Time or Date of trips are The clock in the FM300 is not set. · Set the date and time by using FM Dealer and blue
incorrect Driver Plug

Buzzer sounds when turning
on the ignition
Driver has not been identified
Driver is not authorised to drive
this vehicle
· Insert blue driver plug for identification
· Enable Blue driver plug for the vehicle
· Configure vehicle not to beep when driver is not
identified.

Maintenance
The FM300 unit is maintenance-free.

Please ensure that the Code Plug socket is kept clean and free of dust and dirt (if damaged this socket can be replaced).

FM300 Specifications

Parameter Specification

Rated battery voltage 12 / 24 Volt DC nominal vehicle voltage battery

Minimum operating battery voltage 9 Volts DC

Maximum operating battery voltage 33 Volts DC (Positive drive will be internally switched off at
typically 30V)

Typical stand-by current consumption 20mA

Storage temperature range FM300 Communicator and FM300 ComLink-GSM

Maximum = +70ºC Limited GSM functionality

Minimum = -20ºC

FM300 Communicator Battery

Maximum = +55ºC*

Minimum = -20ºC *

* Note : Battery charging/discharging temperature limits

product operating temperature.

Battery charging:

Maximum = +45ºC

Minimum = 0ºC

Battery discharging:

1002
www.mixtelematics.com

1002
 1003

Maximum = +50ºC

Minimum = -20ºC

Working temperature range FM300 Communicator and FM300 ComLink-GSM

Maximum = +70ºC

Minimum = -20ºC

FM300 Communicator Battery

Maximum = +55ºC

Minimum = -20ºC

Maximum relative non-condensing humidity 95% Relative

Serial Port type - S1 TTL compatible master/slave bus

Serial Port type - S2 & S3 RS-232 Port (TX, RX, CTS & RTS)

Non-volatile backup memory 8kB FRAM

Real-Time-Clock backup power 3V Lithium Battery

Non-volatile memory 1MB Flash

Interrupter relay drive – max continuous contact current 250mA

Relay Drive 1 – max sink current Internally limited to 200mA

Audible indicator Integrated buzzer

Code Plug interface I2C bus

Positive Drive - nominal output voltage Typical: Battery voltage -2V DC

Positive Drive - typical continuous supply current Total: External devices:1A

Maximum number of frequency inputs 3

F4 input Shared with I8 input

Frequency input waveform: F1(Speed), F2(RPM) Square / Sine wave

Frequency signal offset voltage range - 15 Volts to + 15 Volts from DC

Frequency signal peak-to-peak voltage minimum See table below

Frequency signal duty cycle range 10% - 90% (non 50% duty cycle waveforms will be limited in

1003
www.mixtelematics.com

1003
 1004

maximum frequency)

Maximum signal frequency: F1 – F2 See table below

Frequency Input Protection: F1 – F2 +/- 500V spike, +/- 110V DC

Frequency input waveform F3 TTL Signals only, External GPS input

Frequency input waveform F4 TTL Signals only, Low Frequency only

Maximum number of Analogue inputs (can be used as digital 8

inputs with settable thresholds)

Analogue Input 8 (I8) Shared with F4 input

Trigger voltage 0 – 38 Volt (programmable from application software, using

four different voltage ranges)

Resolution (0 to +38V signal range) 150 mV

Hi-Resolution (0 to +5V signal range only) 20 mV

Input impedance analogue line =100 K?

F1 & F2

Signal Frequency

2V AC Signal 300Hz

5V AC Signal 5000Hz

10V AC Signal 5000Hz

Declarations
Type-Approval

This product conforms to the requirements of Directive72/245/EEC, as last amended by Directive 95/54/EC.

Type-approval number: e1*72/245*95/54*4436*00

1004
www.mixtelematics.com

1004
 1005

Declaration of Conformity

We declare on our own responsibility that the product is in compliance with following norm(s) or documents:

· DIN EN 55022 (09/2003)

· DIN EN 61000-6-2 (08/2002)

FM Part Numbers

Part Number Description

X10-723-002-031 FM300 ComLink-GSM Kit

X10-723-002-032 FM300 Communicator Kit

X10-723-002-033 FM300 Communicator Battery Kit

X39-723-002-094 FM300 ComLink-GSM Vehicle Unit

X39-723-002-097 FM300 Communicator Vehicle Unit

X39-723-002-102 FM300 Communicator Battery Vehicle Unit

X39-723-002-106 FM300 MAIN Harness

X39-723-002-101 FM300 Code Plug Harness

X39-723-002-098 FM300 I/O Harness

X39-723-002-100 FM300 Voice Cable

X39-723-002-099 FM300 Serial Cable

X39-723-002-033 Code Plug 256k (same as FM200)

X39-723-002-057 Code Plug 96k (same as FM200)

X39-723-002-007 Code Plug 32K (For jobs/messaging & Fast downloads of recent data)

X39-723-002-006 Driver ID Plug (same as FM200 and FM100)

X39-723-002-054 Passenger Plug

X39-723-002-005 Code Plug Socket Harness

X39-723-002-031 Metal housing FM200 Plus (for protection against tampering)

X39-723-002-079 Fleet Manager Application Software

X39-723-002-009 Download Module

1005
www.mixtelematics.com

1005
 1006

X39-723-002-028 Calibration Set (Violet Code Plug set)

X10-723-002-017 FM Impact sensor (For monitoring and detecting impacts)

X10-723-002-009 FM Info (Fleet logbook, Visual indication of vehicle exceptions)

X10-723-002-005 FM Terminal (Keyboard/screen for jobs/messaging, Fleet logbook, etc)

X10-723-002-016 FM Keypad (for making phone calls and Fleet logbook)

X10-723-002-014 FM Trailer ID (For logging and identifying trailer connection)

X39-723-002-095 FM TCO (for connecting to a non-optical tacho graph interface)

1006
www.mixtelematics.com

1006
 1007
7.16.2.2 FM300 User Manual

© 2008 MiX Telematics | Updated 2008/05/07

Installation
This user manual is applicable to FM200 series and FM300 series on-board-computers.

The Fleet Manager On-Board-Computer should be installed by a suitably qualified person. Please consult the installation manual
of the applicable on-board computer in the Fleet Manager Software CD for installation details.

The Fleet Manager On-Board-Computer must be powered from a battery source. The signal wires should not exceed 30 meters.

Operation
The functioning of the Fleet Manager On-Board-Computer is determined largely by the configuration specified within the Fleet
Manager Software.

Armed / Disarmed Status

Armed status is indicated by one short flash of the red lamp every two seconds. In some installations, the vehicle cannot be
started while in the armed mode and must be disarmed as described below. The red lamp remains off while the Fleet Manager
On-Board-Computer is disarmed.

Driver Identification And Disarming Of the Fleet Manager On-Board-Computer.

If driver identification is required before the trip can begin, the driver must insert the blue driver key into the Code Plug Socket. If
the driver is authorised to drive the vehicle, the Fleet Manager On-Board-Computer will beep twice briefly and the LED in the
reader unit will be switched off. The unit is now disarmed and will allow the vehicle to be started.

Data Transfer

Data stored in the Fleet Manager On-Board-Computer can be transferred by inserting the green vehicle plug into the Code Plug
Socket. The Fleet Manager On-Board-Computer beeps briefly before copying the stored data onto the Code Plug. During the
transfer the red lamp flickers rapidly. One short beep indicates the completion of a successful transfer. The red lamp then
resumes the normal armed mode flash rate of one short flash every two seconds. An unsuccessful data transfer is indicated by a
long beep.

Troubleshooting

LED does not Flash No Voltage Check the voltage supply to the Fleet Manager
On-Board-Computer

The Fleet Manager On-Board- The blue driver key is not assigned to Use the correct blue driver key or get the driver
Computer can not be enabled the vehicle key assigned to the vehicle.

The Buzzer sounds when turning on The driver registration was not done Register with your blue driver key.
the ignition.
The blue driver key is not released / Get your blue driver key released for the vehicle
configured for the vehicle. and register with it.

Beep and Flash Codes

The Fleet Manager On-Board-Computer (OBC) status is indicated by audible and visual signals. The following table shows the
codes used to indicate the various states.

1007
www.mixtelematics.com

1007
 1008

Audible buzzer Red Lamp on Code-plug socket Signal sequence

CONDITION BEEP AND FLASH CODE DURATIONS

At Installation

The FM300 Communicator is

shipped with only the
No Beeps
Only Operating operating system installed.
system loaded The dealer must still install
1s on. 1/8s off
device drivers and the
configuration.

The operating system and

Operating system No Beeps
device drivers have been
and device drivers
installed. The dealer must still
loaded 1/2s on. 1/2s off
install the configuration..

This is the normal 'Armed'

mode. It indicates that the
No Beeps
Normal ‘Armed FM300 Communicator is
Mode’ operational and is not in trip
1/16 on. 2s off
mode or busy with any other
operation.

8 rapid flashes occur when

FM300
No beeps the FM300 Communicator
Communicator
detects a GPS or TCO device,
detect GPS or
8 x 1/8 flashes either at power-up or after a
TCO device
period of inactivity.

Before a Trip

This is the normal 'Armed'

mode. It indicates that the
No beeps
Normal ‘Armed FM300 Communicator is
Mode’ operational and is not in trip
1/16s on. 2s off
mode or busy with any other
operation.

Private mode switch is in the

Notification - 7 short beeps
on position. Location will not
Private Mode
be recorded for the trip that is
enabled Lamp off
about to start.

If driver identification is
required, the beeps will be
Driver 1/4s on. 3/4s off repeated 10 times or until an
identification authorised driver is identified.
requested Lamp off This depends on the selection
made in the Fleet Manager
software Vehicle Properties.

Driver authorised When an authorised driver's

2 x 1/8s beeps
to drive vehicle identification plug is inserted,

1008
www.mixtelematics.com

1008
 1009

two short beeps will be heard.

This driver will now be
permitted to start the vehicle.
Lamp off The lamp will remain off,
indicating the FM300
Communicator is now in
'Disarmed' mode.

When an unauthorised
driver's plug is inserted, one
long beep will be heard. The
Driver not 1 x 1/2s beep
FM300 Communicator will
authorised to
remain in 'Armed' mode as
drive vehicle 1/16s on. 2s off
indicated by the lamp flash
rate. The driver will be unable
to start the vehicle.

One short beep occurs when

the FM300 Communicator has
successfully read the
1 x 1/8s beeps
Passenger Plug Passenger plug. The flash
(black) inserted sequence depends on the
Lamp flashes
status of the FM300
Communicator when the plug
is inserted.

3 Short beeps. The FM300

Communicator memory is
80% - 90% full and must be
downloaded with a green
3 x 1/8s beeps
OBC memory code-plug. If driver
80% - 95% full. identification was required,
Lamp off
this warning will occur one
second after successful
identification. Otherwise, it will
be heard when the trip begins.

3 long beeps. The FM300

Communicator memory is
95% - 100% full and must be
downloaded using a green
3 x 1/2s beeps code plug. If driver
OBC memory
identification was required,
95% - 100% full.
Lamp off this warning will occur one
second after successful
identification. Otherwise, it will
be heard when the trip
begins.

During Calibration

When the violet calibration

plug is inserted, long beeps
Speed or RPM
1s on. 1s off. will be heard. The lamp flash
calibration plug
rate is dependent on the
inserted (Violet
Flashes frequency of the calibration
Plug)
pulses (one change per 25
pulses). This is an indication

1009
www.mixtelematics.com

1009
 1010

that the pulses are being

detected by the FM300
Communicator.

Three short beeps will be

heard if the date and time was
3 x 1/8s beeps set successfully. The flash
Setting date and
sequence depends on the
time (Blue Plug)
Unchanged status of the FM300
------ unchanged ------- Communicator when the plug
is inserted.

One short beep occurs when

the FM300 Communicator
Set Odometer -------------------------------------- 2 x 1/8s beeps detects the plug. Two short
value (Green beeps occur when the
Plug) Flickers Odometer value has been set.
The lamp flickers during the
operation.

Four short beeps occur when

the Engine Hours value was
4 x 1/8s beeps set successfully. The flash
Set Engine Hours sequence depends on the
Lamp flashes status of the FM300
Communicator when the plug
is inserted.

During a Trip

When a trip begins, the

FM300 Communicator mode
No beeps changes from armed to
Start of Trip disarmed mode and the lamp
Flashing Stops stops flashing. There is no
audible indication that the trip
has begun.

During a trip, while no alarm

No Beeps
thresholds are being
While Driving
exceeded, the lamp remains
Lamp off
off and the buzzer is silent.

While any alarm thresholds

Continuous beep
are being executed the buzzer
Event alarm
will sound continuously and
Lamp off
the lamp will remain off.

1 x 1/8s beep The start of a sub-trip is

Start of sub trip indicated by one short beep.
Lamp off There is no visual indication.

1 x 1/8s beep At the end of the trip, after the

End of trip arming delay the buzzer gives
1/16s on. 2s off one short beep. The FM300

1010
www.mixtelematics.com

1010
 1011

Communicator mode changes

to 'Armed'. The lamp will
resume the normal 'Armed
Mode' flash rate.

During Data Transfer

If the incorrect green plug is

1 x 1/2s beep inserted the buzzer will give
Incorrect vehicle
one long beep and the flash
plug inserted.
1/16s on.2s off. sequence will remain
unchanged.

One short beep marks the

start of the data transfer.
Correct vehicle During the transfer the lamp
------- data transfer -----
plug inserted – 1 x 1/8s beep flickers. One short beep
Successful indicates the end of
download of trip Lamp flickers downloading trip data. When
data. the transfer is complete the
lamp will resume the normal
‘Armed Mode’ flash rate.

One short beep marks the

start of the data transfer.
During the transfer the lamp
Correct vehicle
------- data transfer ----- flickers. Two short beeps
plug inserted – 2 x 1/8s beeps
indicate the end of uploading
Successful
configurations, DDRs or
transfer of Lamp flickers
DDMs. When the transfer is
configuration.
complete the lamp will resume
the normal ‘Armed Mode’ flash
rate.

One short beep marks the

start of the data transfer.
Correct vehicle ----- data transfer ----
1 x 1/2s beep During the transfer the lamp
plug inserted –
will flicker. If the transfer was
Unsuccessful
Lamp flickers unsuccessful or incomplete
data transfer.
one long warning beep will be
heard.

Green plug
memory full. OBC
1 x 5s beep
has not
completed
1/16s on. 2s off.
transfer of trip
data.

GSM Diagnostic Plug Inserted (GSM Diagnostics operate on a 30 second cycle)

One short beep indicates the

modem is logged onto a GSM
1 x 1/16s beep
Modem registered network. The lamp flashes
on GSM network when valid responses are
Lamp flashes
received from the GSM
modem.

1011
www.mixtelematics.com

1011
 1012

Three short beeps indicate an

incoming data call was
3 x 1/16s beep answered and a point-to-point
Connection
connection was established.
Established
Lamp flashes The lamp flashes when valid
responses are received from
the GSM modem.

Two medium beeps indicate

an incoming SMS was
2 x 3/16s beep
processed. The lamp flashes
SMS Received
when valid responses are
Lamp flashes
received from the GSM
modem.

Three medium beeps indicate

that an outgoing SMS has
3 x 3/16s beep been saved to the SIM and is
SMS Sent ready to be sent. The lamp
Lamp flashes flashes when valid responses
are received from the GSM
modem.

One long beep occurs if the

1 x 5/8s beep modem responds with an
General Error error. The lamp flashes when
Lamp flashes valid responses are received
from the GSM modem.

Two long beeps occur if the

supplied PIN code was
2 x 5/8s beep
rejected. The lamp flashes
Pin Error
when valid responses are
Lamp flashes
received from the GSM
modem.

5 Short beeps indicate that

the out-bound messages
buffer has exceeded 10
5 x 1/16s beeps unsent messages (Active
Message buffer
Events & Text messages). At
full
Lamp off this point the oldest messages
in the buffer will be removed
to make place for new
information.

GPRS Diagnostics (use GSM diagnostic plug)

When there are no

communications on the GPRS
All beep and flash codes for normal GSM operation
General link, the GSM modem will
applies.
check for incoming SMS
messages.

1 x 1/16s beep Two short beeps indicate that

Modem registered
the modem is logged onto a
on GSM network
Lamp flashes GSM network and is GPRS

1012
www.mixtelematics.com

1012
 1013

capable (not logged on). The

lamp flashes when valid
responses are received from
the GSM modem.

Three short beeps indicate

that the modem has changed
from GSM modem to GPRS
3 x 1/16s beep
Connection mode. This also means that a
Established GPRS connection to the GSM
Lamp flashes
network is established. The
lamp flashes with results from
the modem.

Any incoming packets from

No beeps
GPRS the Wireless Internet Service
communication (GPRS & WLAN) (office) will
Lamp flashes
be indicated by a lamp flash.

GPS Diagnostic Plug Inserted

One half-second beep occurs

Data received 1 x 1/2s beep
each time an error is detected.
from GPS with
The lamp flashes when data is
errors Lamp flashes
received from the GPS.

One short beep occurs when

GPS data 1 x 1/16s beep GPS data is received with
received - position position undetermined. The
not determined Lamp flashes lamp flashes when data is
received from the GPS.

2 x 1/16s beep Two short beeps occur when

GPS data GPS data is received with
received - position Lamp flashes position determined. The lamp
determined flashes when data is received
from the GPS.

Trailer ID Diagnostic Plug Inserted (A combination of these beep sequences will occur, depending on which trailers are
connected, while the diagnostic plug is inserted)

One beep per second

indicates trailer 1 is
1 beep / second
First trailer connected. The lamp flashes
detected when valid responses are
Lamp flashes
received from the Trailer ID
unit.

Two beeps per second

2 beeps / second indicate trailer 2 is connected.
Second trailer
The lamp flashes when valid
detected
Lamp flashes responses are received from
the Trailer ID unit.

Third trailer 3 beeps / second Three beeps per second

1013
www.mixtelematics.com

1013
 1014

indicate trailer 3 is connected.

The lamp flashes when valid
detected Lamp flashes
responses are received from
the Trailer ID unit.

Four beeps per second

4 beeps / second indicate trailer 4 is connected.
Fourth trailer
The lamp flashes when valid
detected
Lamp flashes responses are received from
the Trailer ID unit.

Speed Calibration Diagnostic Plug Inserted

Long beeps are generated

Speed pulses
1s on. 1s off. while the plug is inserted The
connected to
lamp flash rate is proportional
FM300 Speed
Lamp flashes to the frequency of the signal
input
on the FM300 Speed input.

Two short beeps occur each

TCO connected to second when a TCO signal is
FM300 Speed 2 x 1/8s beeps / s detected on the FM300 Speed
input input. The lamp flashes when
Lamp flashes valid responses are received
from a TCO unit connected to
the FM300 Speed input.

RPM Calibration Diagnostic Plug Inserted

Long beeps are generated

while the plug is inserted. The
RPM pulses 1s on. 1s off.
lamp flash rate is proportional
connected to
to the frequency of the signal
FM300 RPM input Lamp flashes
on the FM300 Communicator
RPM input.

WLAN Diagnostics

Link with access

point is OK, but
1 x 1/16s beep
no active comms
channel

Port connection to
access point is
2 x 1/16s beeps
OK, but no
comms channel

Connected to
access point and
attempting to 3 x 1/16s beeps
send data to the
service

An error string /
1s on
condition was

1014
www.mixtelematics.com

1014
 1015

received

Module in power-
save mode
2 x 3/16s beeps
(positive drive is
off)

Module
configuration is
5 x 3/16s beeps
out of date, busy
reconfiguring

1015
www.mixtelematics.com

1015
 1016
7.16.3 FM300 CAN Overview

© 2008 MiX Telematics | Updated 2008/05/07

Overview
The FM300 Communicator (CAN) is the ideal on-board computer for the management of vehicle and driver performance, driver
safety and vehicle utilization. The on-board computer enables the fleet manager to remotely monitor the performance of a
vehicle. Data is recorded on a second-by second basis with driver violations and detailed trip information being made available to
the fleet manager in real-time.

The FM300 Communicator (CAN) on-board computer integrates directly with the vehicle’s CANbus electrical interface which
today is readily available in most modern vehicles.

The CANbus interface has several benefits over the traditional way of capturing vehicle data. Vehicle speed, engine speed
(RPM), power takeoff (PTO) and fuel usage as supported by the FM300 Communicator (CAN) on-board computer is read directly
from the CANbus using the FMS standard. This not only allows for the processing of more accurate data, but makes installation
of the unit much easier.

Standard Features

CAN Support

CAN Interface Standard The FM300 Communicator (CAN) supports CAN interfaces that comply with the FMS
standard.

Vehicle Data Support The FM300 Communicator (CAN) is capable of reading accurate Vehicle speed, Engine
speed (RPM), Power Takeoff (PTO) and Fuel Usage from the CANbus.

Data Resolution Vehicle Speed: Logged at a resolution of 1 km/h

RPM: Logged at a resolution of 100 RPM

PTO: Can be either On or Off

Fuel Usage: Logged at a resolution of 0.5 litres

Vehicle and Driver Management

Vehicle Access Control A driver tag (code-plug) is used to identify and verify a driver. An optional starter interrupt
can be used to immobilise the vehicle until such time as the driver presents an authorised
driver tag.

Trip Data Recording Standard recorded data includes: date and time, distance or hours, speed or hours, RPM,
power takeoff, fuel usage, trip start/depart/arrive/end time, driver name and ID, vehicle ID.

Second-to-Second (Tacho) Data The status of all inputs such as speed, RPM, power takeoff etc. is recorded every second.
This provides valuable in-depth information for accident analysis.

Violation & Event Monitoring Standard event violations include: over speed, over revving (RPM), green band driving (low
and high), hard braking, rapid acceleration, excessive idling, overtime driving, power takeoff
(true or false).

Customisable Events Optional hardware is available to allow you to define additional custom events such as panic
button pressed, door open, no-go zone entered, sudden impact, warning lights activated,

1016
www.mixtelematics.com

1016
 1017

refrigerator temperature exceeded, etc.

Active Events Receive data messages such as SMS when selected standard or user-defined events
occur, e.g. a cargo door opening in a no-go zone, driver arrived at customer location.

Driver Warning A buzzer can be set to sound when an event occurs.

Servicing and Licensing Set reminders for your vehicle’s next service or for your vehicle/driver license expiry.

Location Management

Manage Locations Add any desired location such as customer, supplier or no-go zones.

Route Planning Plan routes by entering stops, start times and duration of each stop. This can serve as daily
job activity sheets for your drivers.

Active/ Passive Tracking or Active Request the vehicle position in real-time or view the route taken after the trip has been
Trail downloaded. Active Trail allows hourly updating of the Fleet Manager software with GPS
vehicle positions.

GPS Data Recording A variety of positional information is recorded with every GPS point, such as vehicle and
driver ID, date and time, latitude and longitude, altitude, heading, speed, number of satellite
etc.

Communication

Downloading to / uploading from The GSM/GPRS Module is used to download data to and upload data from the FM300
vehicle Communicator. This allows for active real-time tracking.

Voice Calls Incoming voice calls are possible with an optional headset.

General Information

Ignition input Used to monitor the ignition switch status.

Positive drive output Used to power external devices. It can supply current up to 500mA.

Buzzer output Signaling device

Audio interface This interface allows the user to make voice calls using a headset, keypad and cable.

FM300 Communicator Includes · GSM/GPRS Antennae.

· GPS Antennae.

· Main harness includes CAN lines with integrated buzzer (2x frequency input, 3x digital /
analogue input).

· FM300 code-plug harness including vehicle interface.

· Blue driver’s plug (driver log-on).

1017
www.mixtelematics.com

1017
 1018

· FM on-board computer user manual.

· Optional harnesses: serial harness, voice harness, I/O harness (2x frequency input, 4x
digital / analogue input)

Technical Description

Voltage range 9VDC – 33 VDC

Input Protection Automotive 24V load dump (160V, 2 Ohm, 400mS); short duration low-energy & high-
energy transients).

Clock Real time with independent battery back-up

Inputs, events & outputs Highly configurable inputs, events and output control.

Firmware Re-programmable firmware and configuration over wired and wireless media.

FMS CAN interface The FM300 Communicator supports the FMS CAN standard.

8 analogue inputs 8 analogue lines measuring voltages in the range of 0 – 38 volts in steps of approximately
0.15 volts. These inputs can be programmed to measure voltages between 0 and 5 volts in
increments of approximately 0.02 volts.

Frequency measurement A selected analogue input can measure frequencies of up to 150Hz or low board rate
encoded RS232 inputs (up to 75 baud).

Frequency inputs 4 high frequency inputs, one dedicated to measuring engine RPM and another to
measuring Vehicle Road Speed. The 3rd and 4th inputs were originally dedicated to
measuring user-defined inputs, especially those from fuel measuring devices i.e. EDMs.
The 3rd frequency input can be used to input NMEA strings from the GPS receiver. These
inputs work to approximately 5KHz (RPM & Speed) and 12KHz (F3 & F4).

Relays The FM300 Communicator features 2 150mA open collector output drivers for driving a
relay. One relay can be used to switch off peripheral devices such as GPS.

Buzzer and LED The FM300 Communicator has a buzzer and LED to warn the driver and to provide
feedback on the vehicle’s status.

l²C Bus Intended for use with code-plugs used to identify drivers, calibrate, diagnose faults, upload
firmware and new configurations, and to download logged data and unit specific
configuration information. This bus can also be used to drive a simple icon based Fleet
Log-Book (FM Info and FM Keypad) which displays driving reasons, violations and faults
and can allow the driver to make voice calls.

TTL level serial port Intended to be used by devices designed to work on a bus. The bus was specified to be a
Multi-Master type to enable other intelligent devices to optionally work as master, relieving
the FM300 Communicator of processing.

Memory Memory is limited to 1 megabyte of flash and 20Kb’s of RAM. 196Kb’s of flash memory is
dedicated to storing firmware, 128KB for tacho data, 312 KB for event data and the
remaining 384KB for buffering data and non-volatile temporary memory space. A FRAM is
also present as a non-volatile replacement for RAM.

1018
www.mixtelematics.com

1018
 1019

Technical Specifications

Environment

Temperature (Storage) -20° to +70°C (Operating) - Non battery backup

10° to +70°
Non battery backup

Circuit protection Conformal coating over the PCB and all components (excluding connectors).

Supply

Current (Operating) <42mA at 28V (typical)*

(Sleep) <20mA at 28V (typical)*

(Operating) <70mA at 12V (typical)*

(Sleep) <30mA at 12V (typical)*

(Powered down) <2mA at 12V (typical)*

(Powered down) <3mA at 28V (typical)*

* The signal strength on the GSM affects the current consumption. The firmware running
on the FM300 Communicator micro processor affects the current consumption of the unit.

Relay Circuit

Current Specifications 200mA (typical).

Maximum continuous voltage on pin 33V

Protection Voltages of 36V and higher will be clamped by tranzorb.

RS232 Ports

Maximum Speed 57600 Baud (higher rates possible with hardware flow control)

Protection (transient) 15Kv as per human body model

Protection (DC) 0V to +12V

I²C Bus

Normal operating speed ~38Kbits per second

Maximum supply current (CLK) <20mA

Protection (transient) 15Kv as per human body model

Protection (DC) 0V to +12V

1019
www.mixtelematics.com

1019
 1020

CANbus

Normal operating speed ~250Kbits per second

Maximum operating speed ~1Mbits per second

Protection (DC) -27v to +40v

Real Time Clock

Time Loss <10 Minutes per year (Typical)/ <5 seconds when a GPS is used (auto synchronization)

Temperature change affects the accuracy of the RTC crystal. The crystal is most accurate
at +25°C.

Battery backup life >5 Years (typical at -30° to +70°C)

GPS

Channels 16

Update rate 1Hz

Accuracy position 2.5m CEP

Accuracy DGPS/SBAS 2.0m CEP

Start-up time <2minutes

GPS operating temperature -40°C to 85°C

GSM

GPRS Multi-slot class 10

Triple band EGSM900/DSC1800/PSC1900

For voice, data, text messages (SMS) and Fax.

Transmit power Class 4 (2W) for EGSM900

Class 1 (1W) for DSC1800/PCS1900

Operating temperature -20°C to 55°C

-25°C to 70°C (limited functionality)

SIM Card 3V

Auxiliary Inputs and Outputs

1020
www.mixtelematics.com

1020
 1021

8 configurable analogue or digital The FM300 Communicator analogue or digital inputs can be configured to monitor any
inputs device that generates a change in voltage, e.g. seat belts, headlights, refrigeration units,
emergency lights, doors, PTO, UDS, trailer coupling etc.

4 auxiliary frequency input The FM300 Communicator auxiliary frequency input can be configured to monitor any
device that generates a change in frequency e.g. temperature sensor, liquid flow
measurement or as a pulse counter e.g. electronic fuel consumption measurement
(EDM) A fourth auxiliary input (F3) is connected to the internal GPS receiver.

2 Auxiliary relay drive This can be used to switch a relay with a current consumption of up to 150 mA.

3 Serial interface (2x RS232 and 1x This can be connected to any TTL or RS232 serial device using the FM Serial cable (e.g.
TTL) FM Terminal). A second RS232 Port (S2) is connected to the internal GSM/GPRS Module

1021
www.mixtelematics.com

1021
 1022
7.16.3.1 FM300 CAN Installation Manual

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
This document is applicable to the FM300 Series of On-board Computers (OBCs) that feature on-board CAN functionality, i.e. the
FM300 ComLink-GSM (CAN), FM300 Communicator (CAN) and FM300 Communicator Battery (CAN). Henceforth these products
will be referred to collectively as FM300 CAN.

The FM300 CAN is based on the FM300 Series and is fitted with an on-board CAN module which allows the OBC to
communicate on a CAN bus supporting the FMS CAN protocol.

Installation
Notes on Installation

1. The FM300 CAN is already loaded with compatible device drivers.

2. The unit still needs to be configured for the vehicle in which it will be installed and the vehicle ID and odometer need to be
configured.

3. It is important to select the correct mounting location for the FM300 CAN. Do not mount it close to air ducts that can channel
cold or hot air directly onto the unit.

4. Do not twist the FM300 CAN unit if mounted on an uneven surface.

Connection

1. The CAN bus comprises pins 7 and 14 on the Main Harness. It is designated by a yellow wire and a green wire. If they are not
already twisted, they should be twisted together.

2. Colour coding of the bus is shown in the table below:

Pin Wire Colour Function

7 Green CAN-Low

14 Yellow CAN-Hi

Connection CAN Jumper Settings

Jumper Function

J17 Terminate CAN Channel - Connect jumper to switch in 120 Ohm Terminating Resistor

J18 CAN Channel Silent Mode - Remove jumper to ensure no transmission of CAN messages

Refer to Figure 1 for the locations of J17 and J18 on the FM300 CAN circuit board.

1022
www.mixtelematics.com

1022
 1023

Figure 1 FM300 CAN Circuit Board showing Jumper Positions

Beep and Flash Codes

Upon the insertion of a CAN Diagnostic Plug the FM300 CAN will beep and flash the LED on the code plug socket in accordance
with the table below to provide diagnostic information:

Condition Beep and Flash Code Duration

CAN Functionality Detected by OBC No Beeps

1 second on, 1 second off

CAN Communications Detected by OBC 1 double beep per second

1 second on, 1 second off

A CAN Diagnostic Plug may be created from a standard 128 byte code plug using the FM Dealer Utility, version 8.3.1.0 or later.

1023
www.mixtelematics.com

1023
 1024
7.16.3.2 FM300 CAN User Manual

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
Controller Area Network (CAN): FMS CAN

Fleet Manager supports the FMS CAN bus standard implemented by Daimler-Chrysler, MAN, Scania, DAF, IVECO, Volvo and
Renault Trucks (see www.fms-standard.com ).

CAN is supported on selected devices for both the FM200 and FM300 product ranges.

Four parameters can be monitored:

· vehicle speed

· engine speed

· power takeoff (PTO)

· fuel usage

Vehicle speed is logged at a resolution of 1 km/h, engine speed at a resolution of 100 RPM and fuel usage at a resolution of 0.5
liters. PTO can be either on or off (true or false).

FM Professional
When selecting the CAN device on C1, CAN Speed and CAN RPM are automatically assigned to F1 and F2 respectively. It is not
necessary to connect any other fuel monitoring device (like EDM) to the frequency or analog inputs, since this will already be
monitored of the CAN bus.

1024
www.mixtelematics.com

1024
 1025

PTO and fuel usage are also monitored by default, but may be disabled if desired.

1025
www.mixtelematics.com

1025
 1026

1026
www.mixtelematics.com

1026
 1027
7.16.4 FM300 Twin Serial Harness

© 2008 MiX Telematics | Updated 2008/05/07

PRODUCT DESCRIPTION
The FM300 Twin Serial Harness enables the connection of two supported serial (RS232) devices simultaneously to the FM300
On-Board-Computer by exposing serial ports S1 and S3 for RS232 serial device use.

The FM300 Twin Serial Harness does not replace the existing FM300 Serial Harness as the FM 300 Serial Harness supports the
FM Terminal and another serial device, whereas the new FM300 Twin Serial Harness does not support the FM Terminal.

PACKET CONTENTS
The FM300 Twin Serial Harness is supplied with the following components:

· FM300 Twin Serial Harness

· Hexagonal nuts

INSTALLATION
To install the FM300 Twin Serial Harness:

· Connect the 10-way connector to the FM300 OBC

· Connect supported serial devices to ports S1 and S3

· Ensure that the DB9 connector marked S1 and S3 is connected to the correct device as specified in the unit configuration

· Connect the two exposed wires (positive drive and ground) to the power input of the serial devices if required.

PIN COLOUR NAME FUNCTION APPLICATION INFORMATION

2 DB9 cable CTS2-IN Handshaking S3

3 DB9 cable RX2-IN Data received S3

4 DB9 cable(S1) RX-IN Data received S1

5 DB9 cable(S1) RTS-OUT Handshaking S1

1027
www.mixtelematics.com

1027
 1028

1 Red/Blue POS DRV Power BAT - 2V 1A

7 DB9 cable RTS2-OUT Handshaking S3

Data
8 DB9 cable TX2-OUT S3
transmitted

9 DB9 cable(S1) CTS-IN Handshaking S1

10 DB9 cable(S1) TX-OUT Data transmitted S1

6 Brown GND OV 1A

SUPPORTED DEVICES
The FM300 Twin Serial Harness currently supports the following serial devices:

· Garmin PND

· VDO Dayton

· Card reader (FM Comms SDK)

· Other serial device (FM Comms SDK)

· Siemens DTCO (Serial Scriptable Comms)

· Kimax I&II (Serial Scriptable Comms)

· Euro/Transcan (Serial Scriptable Comms)

· Other Serial Scriptable Comms devices

S1 S2 S3 DDR Set FM300

FM Comms SDK GSM Garmin 08.01.01.10

Other Serial Device SMS Location (GPS) and later

Card Reader* CSD Jobs & Messaging

GPRS

FM Comms SDK GSM Dayton 08.01.01.1

Other Serial Device SMS Location(GPS) and later

Card Reader* CSD Jobs & Messaging

GPRS

FM Comms SDK GSM Serial Scriptable Comms (SSC) 08.01.01.2

Other Serial Device** SMS Siemens DTCO and later

1028
www.mixtelematics.com

1028
 1029

CSD Kimax I&II

GPRS Euro/Transcan

Other SSC devices

* When configuring the Card Reader device to connect to S1 in the FM Professional software, first connect the VDO Dayton or
Garmin PND device on S3. Only once connected to S3, is the Card Reader available for connection to S1 in the software.

** FM Professional will not permit any logical connections on S1, however you are able to connect any device using the FM
Comms SDK to S1, such as a PDA.

1029
www.mixtelematics.com

1029
 1030

7.17 FM 3310i Overview

© 2008 MiX Telematics | Updated 2008/05/07

OVERVIEW

The FM 3310i on-board computer includes an internal GPS receiver and GSM modem. The GPS receiver allows for the recording
of highly accurate position information. The GSM modem enables the transmission of data, making real-time vehicle tracking and
immediate event notifications possible.

Support for satellite communications is available with an optional FM Sat Comms transceiver that enables real-time tracking and
event monitoring for a vehicle that is out of GSM coverage.

Two-way voice communication is possible when using the optional FM Voice Kit in combination with the internal GSM modem.

FEATURES

ACTIVE TRACKING

Tracking and Route Replay Track the vehicle position in real-time, or view and replay historic routes
taken on a digital map.

GPS Data Recording Various information is recorded with every GPS position such as vehicle
and driver ID (optional), date and time, latitude and longitude, altitude,
heading, speed and the number of visible satellites.

Manage Locations Add, delete or edit unlimited user-defined locations such as customer,
supplier, no-go zone etc. Entry and exit from locations is recorded along
with the date and time of the occurrence and the duration spent at each
location.

Active Events Active events are based on 2 user inputs and active locations (on-board
zones). Immediate event notifications can be sent via SMS whenever a
critical event is recorded. Such events could be when entering or exiting
a zone, panic / assist button pressed (optional), battery disconnect, etc.

Backup Battery As an additional layer of security the FM Tracer is equipped with a

Backup Battery, making tracking possible even if the vehicle’s main
battery has been disconnected. The Backup Battery starts to operate as
soon as the supply to the main vehicle battery is cut.

COMMUNICATIONS

1030
www.mixtelematics.com

1030
 1031

The GSM modem is used to download data from and upload data to the
FM Tracer. This allows for real-time active tracking and immediate SMS
event notifications.
Downloading from / Uploading to vehicle
It is possible to upgrade firmware or update the configuration remotely
over-the-air using the GSM modem, thus reducing the need to remove
the vehicle from duty when performing maintenance.

Satellite communication allows limited data download from and upload to

the FM unit when using the optional FM Sat Comms transceiver. This
Satellite Communication provides real-time tracking and event monitoring when out of GSM
coverage. FM Sat Comms provides global coverage except at the
extreme poles of the earth.

Two-way voice communication is possible when using the optional FM

Voice Calls
Voice Kit, which allows for hands-free operation.

VEHICLE AND DRIVER MANAGEMENT

The following data is recorded: date and time, distance travelled, journey
duration, vehicle speed, journey departure and arrival time, location
Trip Data Recording
entered / exited, driver name (optional), driver ID (optional) and vehicle
ID.

The following standard violations are recorded: over speeding, over

Driving Violations revving (optional), harsh braking, harsh acceleration and excessive idling
(optional).

Two user-configurable digital inputs are available which can be employed

Input Events to trigger custom events such as cargo door open / close, lights on / off
etc.

Set reminders for your vehicle’s next service or for your vehicle/driver
Servicing and Licensing
license expiry.

GENERAL INFORMATION

Ignition input Used to monitor the ignition switch status.

Positive drive output Used to power external devices and can supply current up to 500mA.

Buzzer output Audio signaling device.

This interface allows the user to make voice calls using an optional Voice
Audio interface
Kit.

· GSM/GPRS Antenna.

· GPS Antenna.
FM 3310i Includes:
· Main harness with integrated buzzer (2x frequency input, 2x digital
input).

1031
www.mixtelematics.com

1031
 1032

· Backup Battery.

· FM on-board computer user manual.

· Optional: FM300 series code-plug harness including vehicle interface.

· Optional: Blue driver’s plug (driver log-on).

· Optional: FM Twin Serial Harness.

· Optional: FM Voice Kit.

· Optional: FM Sat Comms.

TECHNICAL DESCRIPTION

Voltage range 9V DC – 33V DC

Automotive 24V load dump (160V, 2 Ohm, 400mS); short duration

Input Protection
low-energy & high-energy transients).

Clock Real-time with independent battery back-up.

Inputs & Events Highly configurable inputs and events.

Re-programmable firmware and configuration over wireless media (or

Firmware
optional wired interface).

2 X digital inputs (I1 & I2) can be configured by the user to monitor any
2 Digital inputs (configurable)
device that generates a change in voltage in the range of 0 – 38 volts.

2 X high frequency inputs (F1 & F2) working to approximately 5KHz, one
2 Frequency inputs dedicated to measuring engine RPM (optional) and another to measuring
Vehicle Road Speed (optional, alternatively GPS speed is utilized (F3)).

2 X RS232 serial ports operating at 57600 Baud rate (higher rates

possible with hardware flow control) for connecting the following optional
2 RS232 Serial Ports
serial devices; S1: Other Serial Device or Card reader and S3: Dayton or
FM Sat Comms. S2 is dedicated to the internal GSM modem.

The FM 3310i has a buzzer and optional LED to warn the driver and
Buzzer and LED
provide feedback of the vehicle’s status.

Intended for use with optional code-plugs used to identify drivers,

calibrate, diagnose faults, upload firmware and new configurations, and
l²C Bus to download logged data and unit specific configuration information. This
bus can also be used to drive the optional FM Keypad, which allows the
driver to make voice calls when used together with the optional Voice Kit.

The backup battery is powered by a Hi Temp NiMH Battery Pack. The

Backup Battery minimum backup time is 4 hours, if the GSM/GPRS is active in low power
mode and the GPS is disabled.

1032
www.mixtelematics.com

1032
 1033

TECHNICAL SPECIFICATIONS

ENVIRONMENT

(Storage) -20°C to +70°C

(Operating) -20°C to +55°C

Temperature
(Charging) 0°C to +45°C

Limited GSM functionality extends to -25°C and +70°C

Conformal coating over the PCB and all components (excluding

Circuit protection
connectors).

SUPPLY

(Operating) <42mA at 28V (typical)*

(Sleep) <20mA at 28V (typical)*

(Operating) <70mA at 12V (typical)*

(Sleep) <30mA at 12V (typical)*

Current
(Powered down) <2mA at 12V (typical)*

(Powered down) <3mA at 28V (typical)*

* The signal strength on the GSM affects the current consumption. The
firmware running on the FM unit micro processor affects the current
consumption of the unit.

1033
www.mixtelematics.com

1033
 1034
7.17.1 FM 3310i User Manual

© 2008 MiX Telematics | Updated 2008/05/07

Installation
The FM 3310i On-board Computer should be installed by a suitably qualified person.

The FM 3310i On-board Computer must be powered from a battery source. The signal wires should not exceed 30 metres.

Operation
The FM 3310i On-board Computer is restricted to be used with FM-Web only.

The functioning of the FM 3310i On-board Computer is determined largely by the configuration specified within the FM Software.

Please note that sections referring to LED (or “red lamp”) flashing, Driver Identification and “Driver Code Plug” are applicable if
the optional Driver ID is used.

Armed / Disarmed Status

Armed status is indicated by one short flash of the red lamp, every two seconds. In some installations, the vehicle cannot be
started while in the armed mode, and must be disarmed as described below. The red lamp remains off while the FM 3310i
On-board Computer is disarmed.

Driver Identification and Disarming of the 3310i On-board Computer

If driver identification is required before the trip can begin, the driver must insert the blue driver key into the Code Plug Socket. If
the driver is authorised to drive the vehicle, the FM 3310i On-board Computer will beep twice briefly and the LED in the reader
unit will be switched off. The unit is now disarmed and will allow the vehicle to be started.

Troubleshooting

Symptom Probable Cause Action

LED does not Flash. No Voltage. Check the voltage supply to the FM 3310i
On-board Computer

The FM 3310i On-board Computer The Driver Code Plug is not assigned to Use the correct Driver Code Plug or ensure
cannot be enabled. the vehicle. Driver Code Plug is assigned to the vehicle.

The Buzzer sounds when turning on The driver registration was not done or Register with the Driver Code Plug.
the ignition.
The Driver Code Plug is not released / Ensure Driver Code Plug is released for the
configured for the vehicle. vehicle and register with it.

Beep and Flash Codes

The FM 3310i On-board Computer status is indicated by audible and visual signals. The following table shows the codes used to
indicate the various states. Symbols used:

Audible buzzer Red Lamp on Code-plug socket Signal sequence

1034
www.mixtelematics.com

1034
 1035

CONDITION BEEP AND FLASH CODE DURATIONS

At Installation

No Beeps
Only Operating system loaded
1s on. 1/8s off

No Beeps
Operating system and device
drivers loaded
1/2s on. 1/2s off

No Beeps
Normal ‘Armed Mode’
1/16 on. 2s off

Before a Trip

No beeps
Normal ‘Armed Mode’
1/16s on. 2s off

7 short beeps
Notification - Private Mode
enabled
Lamp off

1/4s on. 3/4s off

Driver identification requested
Lamp off

2 x 1/8s beeps
Driver authorised to drive
vehicle
Lamp off

1 x 1/2s beep
Driver not authorised to drive
vehicle
1/16s on. 2s off

3 x 1/8s beeps
OBC memory 80% - 95% full.
Lamp off

1035
www.mixtelematics.com

1035
 1036

3 x 1/2s beeps
OBC memory 95% - 100%
full.
Lamp off

During Calibration

1s on. 1s off.
Speed or RPM calibration plug
inserted (Violet Plug)
Flashes

3 x 1/8s beeps
Setting date and time (Blue
Plug)
Lamp flashes

During a Trip

No beeps
Start of Trip
Flashing Stops

No Beeps
While Driving
Lamp off

Continuous beep
Event alarm
Lamp off

1 x 1/8s beep
Start of sub trip
Lamp off

1 x 1/8s beep
End of trip
1/16s on. 2s off

1036
www.mixtelematics.com

1036
 1037
7.17.2 FM 3310i Setup on FM-Web

© 2008 MiX Telematics | Updated 2008/05/07

OVERVIEW
FM 3310i functionality is linked to the FM-Web database only, and unit setup is slightly different from the normal setup of other
units on FM-Web.

This document describes the process that should be followed when configuring and setting up an FM 3310i unit for the first time
on FM-Web.

Note: This setup guide is aimed at Dealers, not end users. If you are running the FM software in standalone mode, you will NOT
have the FM 3310i unit available in your devices list. As per the above, this is ONLY available on FM-Web (i.e. connecting to
FM-Web database in remote mode).

Setting up the FM 3310i Unit

Dat
aba
se

A database needs to be set up on FM-Web in order for the FM3310i units to be configured.

1. Request your Key Account Manager (KAM) or Customer Relationship Manager (CRM) to create a new database,
specifying that it should be FM Tracer (FM 3310i) enabled.

2. If a database is already available on FM-Web, ask your Key Account Manager to ensure it is Tracer enabled.

3. After receiving the database and login details open the FM Professional software and connect to the database in remote
mode. To do this, open the FM Admin utility, ensure you have selected remote mode, and enter valid connection details
(the URL for FM-Web, your username and password):

1037
www.mixtelematics.com

1037
 1038

Veh
icle
setu
p

1. Open the FM Professional Software and enter your FM-Web username and password when prompted. If you have
access to more than one database, select the appropriate database, and continue to open the FM Professional
Software.

2. Add a new vehicle (Tools menu ? Add Vehicle), or open an existing vehicle’s properties if you are going to replace an
existing unit with the FM3310i unit.

3. Select FM Tracer as the Unit Type and click OK.

1038
www.mixtelematics.com

1038
 1039

4. Ensure that the correct APN and GPRS settings are selected. Your KAM/CRM will provide you with the appropriate
GPRS IP and Port settings. The APN is available from the SIM provider. Set up the rest of the configuration, or use the
default selection.

5. Once you are happy with the configuration set up, Apply or OK the configuration.

Note: Do NOT attempt to upload the configuration to a green vehicle key at this stage.

Tra
nsfe
rrin
g
con
figu
rati
on
to
the
FM 1. Login to the FM-Web site
331
0i
unit

1039
www.mixtelematics.com

1039
 1040

2. From the menu, select Sys Admin ? Manage Plugs

3. Select the “Vehicle”, “% Event data” and “Plug Size” from the drop down list, then click Get Plug Data.

1040
www.mixtelematics.com

1040
 1041

4. At the bottom of the screen you will see the following text:

5. Click on the link to download the plug dump.

6. Save the plug dump to the location where you have the FM Dealer utility installed (this could also be installed as an
extension with FM Professional).

7. Extract the file to a specific location (it will have a .BIN extension after being extracted).

8. Insert a 256KB green vehicle key into the Download Module.

9. Open the Fleet Manager Dealer Utility (this can be done from within the Fleet Manager software (Tools ? Dealer
Utility), or if installed as standalone, from Start ? All Programs ? Fleet Manager Office ? Fleet Manager Dealer utility.

10.From the Code Plug menu, select Restore Plug.

1041
www.mixtelematics.com

1041
 1042

11.Browse to where the extracted file is located, select the filename and click Open to restore the plug dump to the green
vehicle plug.

After the file has been restored to the plug (the LED on the Download module will stop flickering, or when using USB
Download module will return to its previous state of flashing occasionally), insert the plug into the vehicle socket
connected to the unit whose configuration you are uploading.

NOTE: The configuration should be transferred in the same way as other units. Before inserting the configurations plug,
ensure the unit is OUT of trip mode and switched on. If it is a new unit that has never been used, turn ignition on to “wake
up” the unit, turn ignition off again, and wait for the LED to indicate out of trip mode. Ensure the LED on the vehicle socket
is flashing as per the Beep and Flash code documentation (No Beeps, LED 1/16s on. 2s off).

Test Once the configuration has been transferred, ensure the unit is working correctly and connecting to the FM-Web
ing database. This can be done in a number of ways, but the easiest is to view the vehicle status in the database. (From the
the Active Tracking and Messaging section, you should be able to see when the vehicle last connected).
FM
331 If the unit is working correctly, any further configuration changes required may be made via the FM-Web database by
0i using FM Professional in remote mode, and uploaded to the unit using GPRS.
unit
If the unit is not working, check the configuration settings and ensure all information has been entered correctly. If there is
no connection to the database, use diagnostics plugs to check GPS/GSM/GPRS connectivity from the hardware side.
Alternatively contact Support for assistance in troubleshooting.

1042
www.mixtelematics.com

1042
 1043

Inst Once a successful unit-to-database connection is established, the unit can be installed in the vehicle. See the FM 3310i
allin Installation Guide for information on installing the FM3310i unit.
g
the After vehicle installation is complete, a test trip should be done and checked on FM-Web to ensure proper connection and
unit reporting. Once again, the easiest/quickest way to do this would be to check active tracking. If problems are experienced,
into check the installation, or contact Support for assistance in troubleshooting.
the
vehi
cle

Cus After installation, it is the dealer’s responsibility to obtain sign-off from the customer and pass this information through to
tom their CRM/KAM.
er
sign
-off

1043
www.mixtelematics.com

1043
 1044

8 Interaction With Other Devices

8.1 Introduction to CAN
© 2008 MiX Telematics | Updated 2008/06/20

Moving towards the exciting world of CAN-based installations opens up almost endless possibilities for Fleet Managers. Now
there is much more information available from just this simple two-wire connection to the vehicle. CAN is, however, complex and
has some limitations. It is therefore important to have a general understanding of how this technology works.

WHAT IS CAN?
Controller Area Network (CAN or CAN-bus) is actually just another computer network protocol and bus standard designed to
allow micro-controllers and devices to communicate with each other without the need for a host computer. It was introduced by
the Robert Bosch Company in the mid-1980’s.

HOW CAN WORKS

Just as your office PC is connected to other PCs, servers, and printers via a Local Area Network or LAN, so sensors, actuators
and controllers are connected to one another inside your vehicle via a Controller Area Network or CAN, or on some vehicles, by a
J1708 network.

Why do we need networks anyway? Imagine all your office PCs being connected to one another, as well as to printers and
servers, through discrete wires. You would have a spider web of wire, as shown in Figure 1.

The same would happen in a vehicle. It is estimated that connecting every sensor, actuator and controller using discrete wires in
a modern vehicle would require in excess of 100kg of wire! This would add unnecessary weight and great cost to the vehicle.

1044
www.mixtelematics.com

1044
 1045

Networks solve this problem by allowing communication between many nodes over fewer wires. Figure 2 depicts a “star” network
such as your office LAN, while Figure 3 depicts a linear “bus” network, such as CAN.

But communication between many nodes over fewer wires implies that nodes must take turns speaking, as shown in Figure 4.

1045
www.mixtelematics.com

1045
 1046

For CAN, each data frame (“word”) has an identifier field as well as data fields, as shown in Figure 5. The identifier indicates
what signals (speed RPM etc.) can be expected inside the data fields.

Once the FM is connected to the CAN bus, it will listen to the “words” or “conversations” on the bus; the “conversations” between
the other nodes. From this it can determine and log useful information such as fuel consumption. However, the “language”
spoken by the nodes on the bus may be foreign to the FM.

In FM Professional 9.0, the FM 3316 can be configured to understand J1939. J1939 is actually the “language” being spoken on
most CAN busses in heavy vehicles today. We can liken this “language” to “English”. But, not all vehicles speak ”English”. And
so we are teaching the FM 3316 to understand other “languages” by creating scripts for it. For example, to understand the native
DaimlerChrysler protocol. We will call this “German”!

Another way to think about it is by analogy to trains. All trains run on tracks (“CAN busses”) and all the trains carry passengers
(“signals”). But, on different routes (J1939, DC) the passengers like to sit in different carriages. We are trying to find the
passengers (vehicle speed, engine speed, fuel consumption etc.)

Similarly, if CAN was a railway track, J1708 could be likened to a tar road with J1587 the transporter carrying the passengers
(“signals”).

CAN – TECHNICALLY SPEAKING

Controller Area Network (CAN) is a two-wire communications network between 2 or more Electronic Control Units (ECU). This
two-wire network is commonly referred to as a bus – more specifically the CAN-bus. The typical computer network uses a
hub-and-spoke topology, whereas CAN uses a multi-drop bus where only one ECU can transmit data onto the bus while all the
other ECUs are listening to the data.

Similar to the Internet, communication over CAN is packet-based. The packets destination addresses. Each sending CAN
controller checks the bus firstly to see if anything is being sent, and secondly for arbitration. A controller will wait for the end of a
packet if one is currently in transit. It starts by sending the packet header. CAN controllers must watch the bus to see that each

1046
www.mixtelematics.com

1046
 1047

bit it sends matches the bus state. If there is a difference, then a higher-priority CAN controller is attempting to send at the same
time. In this case, all lower-priority CAN controllers must stop using the bus and wait to send their packet. Only one controller will
eventually have control of the bus after the header is sent.

A remote transmission request mechanism permits a device to signal another node to provide the requested data based on the
packet's address. This is typically used to request Diagnostic Trouble Codes (DTC).

CAN initially was defined with an 11-bit address. Sometime later a 29-bit address was defined, allowing a single address space to
handle a large number of nodes and multiple interlinked CAN networks. Of course, this makes the packet longer. That and the
proliferation of small CAN networks is why the 11-bit addressing is still more commonly used.

Each address has an associated mask that is used on each destination address in an incoming packet and compared with a
receive address to determine whether the controller will capture the data. This also allows data to be broadcast to more than one
controller where each of these controllers is set up to look for the appropriate masked address. Since only part of the address is
used for routing, the remaining address bits can be used for data.

CAN controllers typically implement multiple mail boxes. An address and a mask are associated with a mailbox so incoming
messages with matching addresses can be stored there. Hence CAN nodes are not restricted to a single address. In fact, the
data in CAN packets is actually what is identified by the address, and this field is typically called the object identifier.

CAN is a high-integrity serial data communications bus for real-time control applications and performs at data rates of up to 1
mega bits per second with excellent error detection and confinement capabilities. It is therefore not only used in automotive
vehicles, but also used in many other industrial automation and control applications.

The CAN protocol is based on the familiar OSI session layers and is documented in ISO 11898 (for applications up to 1 mega bits
per second) and ISO 11519 (for applications up to 125 K bits per second). Automotive CAN is typically implemented using
higher-level protocols such as SAE J1939.

The table below shows a general comparison between CAN and Ethernet.

CAN Ethernet

Speed 125 Kbits/s to 1 Mbits/s 10 Mbits/s to 10 Gbits/s

Cable Distance 100 meters 150 meters

Data size (min) 0 bytes (address only) 64 bytes

Data size (max) 8 bytes (64 bits) 1518 bytes

2032 for 11-bit address

Max devices 281 474 billion
536 million for 29-bit

The J1939 protocol comes from the international Society of Automotive Engineers (SAE) and works on the physical layer with
CAN-high speed according to ISO11898. The application focus is on the power trains and chassis of commercial vehicles. The
protocol is used in heavy vehicles for on-street and off-road operations. Related to J1939 are the ISOBUS according to ISO11783
for agricultural machines, NMEA2000 for maritime use, and the ISO 11992 truck & trailer interface. Similarly, the FMS standard is
based on J1939 communication.

SAE J1939 was required to provide some backward-compatible functionality to older RS485-based communication protocols
(J1708/J1587).

SAE J1708 specifies on the physical layer of the communication link. It uses RS485 as an electrical layer operating at 9600 baud.
(Note: Unlike RS232/485 there are no message collisions under CAN).

1047
www.mixtelematics.com

1047
 1048

J1939 is a multi-master system with decentralized network management without channel-based communication. It supports up to
254 logical nodes and 30 physical ECUs per segment. The information is described as parameters (signals) and combined on 4
data pages in parameter groups (PGs). Each parameter group can be identified via a unique number, the parameter group
number (PGN). Irrespective of this, each signal is assigned a unique SPN (suspect parameter number).

The majority of the communication usually occurs cyclically and can be received by all ECUs without explicit request of data
(broadcast). In addition, the parameter groups are optimized to a length of 8 data bytes. This enables very efficient use of the
CAN protocol. Particular information such as configuration data or diagnostic data can be exchanged exclusively between two
ECUs (peer-to-peer). The specification of the communication, broadcast or peer-to-peer, is a property of the parameter group
used. Thus, in addition to the definition of which parameters are transmitted, the transmission type also depends on the
parameter group.

The standard defines an index called PGN (Parameter Group Number), which is embedded in the message's 29-bit identifier. A
PGN identifies a message's function and associated data. J1939 attempts to define standard PGNs to encompass a wide range
of automotive purposes. For example, there exist predefined PGNs for information such as engine RPM. A range of PGNs
(00FF0016 through 00FFFF16, inclusive) is reserved for proprietary use.

SAE J1939 has been adopted widely by diesel engine manufacturers. One driving force behind this is the increasing adoption of
the engine Electronic Control Unit (ECU), which provides one method of controlling exhaust gas emissions within US and
European standards. Consequently, SAE J1939 can now be found in a range of diesel-powered applications: vehicles (on- and
off-road), marine propulsion, power generation and industrial pumping.

The diagram below shows how various ECUs are networked over a CAN-bus. Many vehicle manufacturers would require third
party devices such as the Fleet Manager to be connected via a gateway such as the FMS Gateway in order to protect they “hot
bus” from third party devices that may corrupt the information bus. The Fleet Manager however has hardware configurable
jumpers that prohibit it from writing to the bus and also for including a bus terminator that may be required in some
circumstances.

1048
www.mixtelematics.com

1048
 1049

WHAT INFORMATION IS AVAILABLE VIA CAN IN FM PROFESSIONAL v9?

SAE J1939 (CAN) signals supported

· Vehicle speed

· Engine speed

· Fuel consumption

· Fuel tank level

· Power take off (PTO)

· Coolant level

· Coolant temperature

· Retarder engaged

· Coolant temperature high *

· Oil pressure high *

· Oil level low *

· Clutch overload *

· Axel weight

1049
www.mixtelematics.com

1049
 1050

· Brakes applied

· Clutch disengaged

· Total engine hours

· Vehicle odometer

· Distance to next service

· TCO drive recognize

· TCO over speed

· TCO direction indicator

* Scania proprietary

SAE J1587 (J1708) signals supported

· Vehicle speed

· Engine speed

· Fuel consumption

· Brakes applied

· Clutch engaged

· Accelerator pedal position

· Vehicle odometer

· Cruise Control Status **

· Engine Oil Temperature **

· Intake Manifold Temperature **

· Power Takeoff Status **

· Throttle Position **

** Included for upcoming release (not yet available in FM9.0)

WHAT DO I NEED TO ACCESS THE FM9 CAN INFORMATION?

The abovementioned information can only be logged using the new FM 3316 or FM 3306 unit, running the latest FM Professional
v9 device drivers and an FM Professional 9 configuration on a vehicle that supports the J1939 (for CAN) or J1587 (for J1708)
vehicle busses.

What if I can’t see this information?

We currently only support the protocols J1939 and J1587. Please check with the vehicle manufacturer for further information on
protocols available. In future phases we will expand the number of protocols we support.

1050
www.mixtelematics.com

1050
 1051

DEVICE DRIVERS
Two distinct sets of device drivers are required by the FM3316/FM3306 to function correctly, a core set and an auxiliary
“CAN/J1708” set. The auxiliary device drivers are often referred to as device driver modules or DDMs.

It is recommended that you load all device driver sets using FM Professional, as this software will automatically select the
appropriate core set of drivers to be loaded to the vehicle.

Loading device driver sets using the FM Dealer is a manual process. Note that all sets will work with the FM 3316/3306 by
default, except when using an FM3316/3306 with a modem and a VDO Dayton. In this case, please load the specific device
driver set called “Device Drivers for modem and VDO Dayton for FM3316”. All other sets support the FM3316 functionality by
default.

1051
www.mixtelematics.com

1051
 1052

For the auxiliary CAN device driver module, please load the “3316 CAN / J1708: Module” to the FM unit.

Note: It is possible to load this driver together with the core set in one step using one device driver plug.

CONFIGURATION
Using the FM Professional software, create a new FM 3316 unit:

1052
www.mixtelematics.com

1052
 1053

From the C1 device, select the appropriate “script” to load via the config. “Scripts” are used to define which information the FM
attempts to decode.

1053
www.mixtelematics.com

1053
 1054

· The default script for CAN (J1939) is “CAN: J1939 FEF2”. This script will try to decode all the listed signals off the CAN bus. If
this configuration does not succeed in recording fuel consumption information after a test trip, please try one of the “CAN:
J1939 FEE9” scripts, and repeat the test trip.

· The “CAN: J1939 FEE9” scripts are identical to “CAN: J1939 FEF2”, but use a different fuel input.

· The script for J1708 (J1587) is “J1708: J1587”.

CONNECTION
· For CAN (J1939) installations, the FM 3316 must be connected to a J1939 CAN bus using the yellow / green twisted wires on
the main connector

· For a J1708 (J1587) installation, the FM 3316 must be connected to the J1708 bus using the separately supplied yellow / blue
twisted wires.

Please refer to the FM300 CAN Installation Procedure for more details.

JUMPER SETTINGS
For jumper settings, please refer to the FM300 CAN Installation Procedure.

We recommend that you close both jumpers for the first test on the vehicle. This is the most likely configuration that will work,
and is the default production configuration. After a successful test, try to remove first one of the jumpers, then the other, and
finally both. If the FM continues to record data, leave the jumpers off (open). This is the safest configuration and should not

1054
www.mixtelematics.com

1054
 1055

interfere with the vehicle’s electronics.

1055
www.mixtelematics.com

1055
 1056

8.2 Garmin Integration

© 2008 MiX Telematics | Updated 2008/06/24

Introduction
The FM3316, FM3316i and FM200 Plus hardware platform integrates with Garmin’s Portable Navigation Devices (PND) via the
Garmin Fleet Management Interface (FMI) which enables you to send jobs and messages between drivers and the office.

Benefits
· Easy to use
Touch screen functionality, in car navigation, turn-by-turn voice directions

· Reduce communication costs

Send and receive text messages between office and vehicle

· Better manage jobs

Send new jobs to driver with destination address embedded

· Reduce the number of miles driven and fuel costs

On accepting a new job, the Garmin PND will route the driver directly to the destination with detailed street maps and
turn-by-turn voice directions

· Increase pickup / drop off rates

Estimated Time of Arrival is displayed to the driver and relayed back to the office

PND Compatibility
Garmin maintains a list of PND's which are enabled with the Fleet Management Interface and can interface with the FM product
range.

The following link lists the Garmin FMI enabled PND's:

http://www8.garmin.com/solutions/pnd/supportedproducts.jsp

As Garmin are constantly refreshing their product range with new models in different regions, this list can include models which
are already or are soon to be discontinued. It is therefore essential to check with your local Garmin dealer as to the status of a
particular model in your region.

The available Job and Messaging functionality can vary between Garmin PND models and to assist with the selection of a
suitable Garmin PND, we test the listed models and verify the functionality supported. The results of these tests are published in
KBA #409 where you can compare the various Garmin FMI enabled models. This KBA will be updated as new models are
verified, so please check regularly.

Setup and Installation

Load the OBC with the corresponding device driver set (set ver YY.MM.DD.8). Set up the vehicle’s configuration which maps the
Garmin device to S3 using FM Professional.

Set up on FM Professional

Right-click the vehicle using the Garmin PND and select “Properties”. Select S3 from the Device list and click “Edit”:

1056
www.mixtelematics.com

1056
 1057

Choose the Garmin PND from the list and click “OK”.

1057
www.mixtelematics.com

1057
 1058

The Garmin PND will show as connected to S3. Click “Apply” to save the changes to the vehicle’s profile.

1058
www.mixtelematics.com

1058
 1059

12V Connection

The wiring diagram below illustrates how to connect the FM OBC to the Garmin PND in a 12V vehicle:

1059
www.mixtelematics.com

1059
 1060

24V Connection

The Garmin FM Interface Cable is rated to 12V only, and thus installation into a 24V vehicle requires an additional 24V > 12V
reducer to make it compatible with a 24V vehicle.

The Mix Telematics 24V-12V Adapter (440FT0323) can safely be used to enable installation into a 24V vehicle. The wiring
diagram below illustrates how to connect the FM OBC to the Garmin PND using the 24V-12V Adapter:

1060
www.mixtelematics.com

1060
 1061

Supported Garmin Devices

For the latest supported Garmin devices, please see: http://www8.garmin.com/solutions/pnd/supportedproducts.jsp

The Fleet Management interface cables can be ordered directly from MiX Telematics, and include the necessary connectors for
connecting to the FM OBC.

· Where the Garmin website states “Fleet Management functionality requires accessory: 010-10813-00”, please order MiX
Telematics accessory part number 440FT0326.

· Where the Garmin website states “Fleet Management functionality requires accessory: 010-10865-00”, please order MiX
Telematics accessory part number 440FT0327.

Operation
Note: All screenshots are from a Nuvi 660 and may vary depending on model.

Establishing a connection

The icon in the top right corner of the screenshot indicates no serial communication has been established. This could be caused
by incorrect setup, incorrect device drivers set or configuration loaded to the OBC and/or faulty serial cables/module.

1061
www.mixtelematics.com

1061
 1062

Once communications is established the icon disappears as shown below.

Send and Receive Messages

The Dispatch menu contains the FMI functionality, namely Stops/Jobs and Messaging. The screenshot below shows the Dispatch
menu contents.

Note: A new Garmin device (out of the box) will not display the Dispatch menu until it establishes communications with the OBC.

Send message from Office

Using FM Web or FM Pro, send a text message to the Garmin via the connected OBC.

1062
www.mixtelematics.com

1062
 1063

The Garmin displays:

Send a Message to the Office

In the “Create Message” menu type your message and then send it.

1063
www.mixtelematics.com

1063
 1064

Send a Job Message from the Office to the Garmin Unit.

1064
www.mixtelematics.com

1064
 1065

The Garmin displays:

1065
www.mixtelematics.com

1065
 1066

9 Fleet Manager SDKs

© 2008 MiX Telematics | Updated 2008/06/11

Overview
The Fleet Manager product range offers a powerful and flexible platform upon which hardware and software systems integrators
can develop sophisticated, customer specific solutions. A range of development tools, documentation, tutorials and sample
source code is available in the form of Software Development Kits (SDKs). The following diagram shows the components of the
Fleet Manager system, highlighting the interfaces addressed by the SDKs:

1066
www.mixtelematics.com

1066
 1067

The Fleet Manager Communications SDK (FM Comms SDK) can be used by engineers to enable other hardware devices to
communicate with the FM200 Plus unit using RS-232 serial communications. The SDK includes portable C source code that can
be used to implement the FM200 Plus communications protocol on programmable serial devices, as well as a callable interface
that can be used to develop back office applications to communicate with the FM200 Plus unit once a communications link has
been established.

The Fleet Manager Extension SDK (FM Extension SDK) can be used by software developers to develop Extensions (add-ons)
to the Fleet Manager application software, to implement customer specific reporting, import data from and export data to third
party software systems such as CRM or ER solutions etc. The SDK includes Windows COM based interfaces facilitating the
development of both client and server-side applications to integrate with the Fleet Manager system. An XML Web Service is also
provided enabling non-Windows based applications to exchange data with the Fleet Manager system using industry standard
SOAP/XML protocols. Tools are included to allow developers to incorporate multi-language support into the Extensions.

1067
www.mixtelematics.com

1067
 1068

What SDK do I need?

The table below lists some examples of development projects that have been / could be undertaken using the Fleet Manager
SDKs. Many of the existing Fleet Manager products were developed using the SDKs and these are listed where applicable.

1068
www.mixtelematics.com

1068
 1069

More on the Comms SDK

The hardware communications interface with the FM200 Plus unit is done via the S1 (with TTL-RS232 converter), SB (with FM
Splitter) or S2 RS-232 serial port of the FM200 Plus unit. An HDLC protocol is used, typically at a baud rate of 19200 bps, 8 data
bits, no parity, 1 stop bit and hardware flow-control.

The application layer commands are abstracted into callable C functions. These functions allow individual parameters, data
structures and data blocks to be read from and written to the unit. Functions are available to:

§ Get and set unit date/ time, driver ID, odometer reading, engine hours etc.

§ Get general information such as vehicle ID, driver ID, current speed, RPM, odometer reading, GPS data, etc.

§ Retrieve event and interval (tacho) data blocks from the unit.

§ Update event configuration and firmware device drivers in the unit

§ Check critical event conditions such as over speeding, over revving, etc.

§ Store user data and values such as driving and stopping reasons, document codes, costs, etc. in the unit’s memory.

More on the Extension SDK

The FM Extension SDK provides three possibilities for integrating with the Fleet Manager system:

Client Extension Manager Interface

The FM Client executable exposes a COM interface known as the Extension Manager interface. Client-side Extensions are
add-ons to the Fleet Manager application software. Extensions are COM DLLs which interface with the FM Client executable by
implementing a public FM Extension COM interface. Extensions are registered with the Extension Manager object, which loads
them at start-up, passing them a handle to itself. Extensions have access to the many methods and properties of the Extension
Manager enabling them to:

· Add menu items.

· Add toolbar buttons.

· Add UI elements such as forms, dialogs etc.

· Add per object property pages (to extend the properties of standard Fleet Manager Objects such as drivers, vehicles, sites etc).

· Invoke the standard Report Criteria Wizard and Progress dialogs.

· Add a More Options dialog to the final step of the Criteria Wizard.

· Read, add, modify or delete Fleet Manager static object data such as vehicles, trailers, drivers, passengers, locations, sites,
reporting group etc.

1069
www.mixtelematics.com

1069
 1070

· Gain access to other Fleet Manager data such as trip and event data, GPS data etc.

· Import data into and export data out of the Fleet Manager database.

· Store proprietary data in the Fleet Manager database.

· Leverage off the Fleet Manager 3-tier client/server architecture to support multi-user environments.

· Leverage off the Fleet Manager Upgrade+ program to manage licensing.

Client-side Extensions run in-process of the FM Client executable and as such, require the FM Client executable to be running.

Server Extension Manager Component

The FM Server Extension Manager component is a COM DLL that exposes numerous methods and properties enabling
applications to:

· Read, add, modify or delete Fleet Manager static object data such as vehicles, trailers, drivers, passengers, locations, sites,
reporting group etc.

· Gain access to other Fleet Manager data such as trip and event data, jobs, messages, GPS data etc.

· Import data into and export data out of the Fleet Manager database.

· Store proprietary data in the Fleet Manager database.

· Send free-text messages to vehicles.

· Send jobs to vehicles and query the status of jobs in real-time

· Request the current position and status of vehicles in real-time.

The FM Server Extension Manager component runs in-process of the application that instantiates it, thus applications that use
this component do no require the FM Client executable.

XML Web Service

The FM XML Web Service is an industry standard XML web service which runs on a Microsoft Internet Information Service (IIS)
web server within the Microsoft .NET framework. The service exposes numerous methods and properties that can be accessed
by posting XML requests in SOAP envelopes to the web server using the HTTP or HTTPS protocols. The FM XML Web Service
enables applications to:

· Read, add, modify or delete Fleet Manager static object data such as vehicles, trailers, drivers, passengers, locations, sites,
reporting group etc.

· Gain access to other Fleet Manager data such as trip and event data, jobs, messages, GPS data etc.

· Import data into and export data out of the Fleet Manager database.

· Store proprietary data in the Fleet Manager database.

· Send free-text messages to vehicles.

· Send jobs to vehicles and query the status of jobs in real-time.

· Request the current position and status of vehicles in real-time.

Although the service runs on Windows under IIS and .NET, it can be accessed from any platform supporting the HTTP or HTTPS
protocol.

1070
www.mixtelematics.com

1070
 1071

What skills do I need?

The FM COMMS SDK is designed to be used by engineers with embedded software development experience. Most of the
sample source code provided with this SDK is written in C.

The FM Extension SDK is designed to be used by software developers with COM development experience and/or SOAP/XML
experience. An assortment of sample source code is provided. Both client-side and server-side Extensions can be developed with
any COM enabled software development tool. The XML Web Service can be accessed using any tool on any platform capable of
posting SOAP envelopes containing XML objects using HTTP protocol.

Where can I get the SDKs?

The SDKs are available for download free of charge from the MiX Telematics Fleet Management Services web site
http://www.mixtelematics.com.

· To download the FM COMMS SDK, click on the Products link at the top of the home page, and then click on the “FM Comms
SDK” link in the products menu on the left hand side of the page.

· To download the FM Extension SDK, click on the Products link at the top of the home page, and then click on the “FM
Extension SDK” link in the products menu on the left hand side of the page. Alternatively, click on the “Fleet Manager Software
Developers Kit” link on the Downloads page.

1071
www.mixtelematics.com

1071
 1072

9.1 Fleet Manager Extention SDK 8

© 2008 MiX Telematics | Updated 2008/06/11

Overview

The Fleet Manager product range offers a powerful and flexible platform upon which hardware and software systems integrators
can develop sophisticated, customer specific solutions. A range of development tools, documentation, tutorials and sample
source code is available in the form of Software Development Kits (SDKs). This documentation describes the Fleet Manager
Extension SDK (FM Extension SDK). For more information on Fleet Manager SDKs, please consult the MiX Telematics web site
at http://www.mixtelematics.com.

What is the FM Extension SDK?

The FM Extension SDK can be used by software developers to develop Extensions (add-ons) to the Fleet Manager Professional
application, to implement customer specific reporting, import data from and export data to third party software systems such as
CRM or ERP solutions and much more.

This SDK includes Windows COM based interfaces facilitating the development of both client and server-side applications to
integrate with the Fleet Manager system. An XML Web Service is also provided enabling non-Windows based applications to
exchange data with the Fleet Manager system using industry standard SOAP/XML protocols. Tools are included to allow
developers to incorporate multi-language support into their Extensions.

License
You may use and re-distribute the tools and components in this SDK royalty-free exclusively for the development and runtime
execution of Extensions to the Fleet Manager Professional application and only in accordance with the terms and conditions of
the Fleet Manager Professional end user license agreement (EULA) and the FM Upgrade-Plus Programme.

Use of any part of this SDK for any other purpose whatsoever requires written permission from MiX Telematics (Pty) Ltd.

SDK Scope
Prior to studying the other documentation in the FM Extension SDK, you should familiarise yourself with the topic describing
delimited lists and the routines used to create and manage them. These lists are used by many of the objects, methods and
properties in the SDK.

The FM Extension SDK provides various possibilities for integrating with the Fleet Manager system. To determine which option or
combination is best suited to your requirements, please read the topics listed below.

· Client Extension Manager Interface

· Server Extension Manager Component

· XML Web Service

The FM Extension SDK also includes the MiX Telematics Language Tools, enabling developers to incorporate multi-language
support into the Extensions they develop.

Skills Required

1072
www.mixtelematics.com

1072
 1073

The FM Extension SDK is designed to be used by software developers with COM development experience and/or SOAP/XML
experience. An assortment of sample source code is provided. Both client-side and server-side Extensions can be developed with
any COM enabled software development tool. The XML Web Service can be accessed using any tool on any platform capable of
posting SOAP envelopes containing XML objects using HTTP protocol.

Support
MiX Telematics is committed to supporting developers writing Extensions to the Fleet Manager system. Should you require
support, please log a service request on our web site by clicking on the following link: Log a service request. Please ensure that
you include as much detail as possible when logging a request.

1073
www.mixtelematics.com

1073
 1074
9.1.1 Client Extension Manager Interface

© 2008 MiX Telematics | Updated 2008/06/25

Introduction
The Fleet Manager Professional Client executable (FMCli<n>.exe) exposes an Extension Manager COM interface. Client-side
Extensions are add-ons to the Fleet Manager Professional Client application in the form of COM DLLs which interface with the
Fleet Manager Professional Client executable by implementing a public Extension4 COM interface. Client-side Extensions are
registered with the Extension Manager object, which loads them at start-up, passing them a handle to itself. Client-side
Extensions run in-process of the Fleet Manager Professional Client executable and as such, require the Fleet Manager
Professional Client executable to be running.

Note: The Client Extension Manager interface was specifically designed to enable developers to extend the user interface of the
Fleet Manager Professional Client application and to provide the high-speed data retrieval methods required to generate reports
etc. The Client Extension Manager cannot be used to create objects within the Fleet Manager database. To do so, client-side
extensions should make use of the Server Extension Manager component.

Capabilities
Client-side Extensions have access to the many methods and properties of the Extension Manager interface enabling them to:

§ Add menu items.

§ Add toolbar buttons.

§ Add UI elements such as forms, dialogs etc.

§ Add per object property pages (to extend the properties of standard Fleet Manager Objects such as drivers, vehicles, sites etc).

§ Invoke the standard Report Criteria Wizard and Progress dialogs.

§ Add a More Options dialog to the final step of the Criteria Wizard.

§ Read Fleet Manager static object data such as vehicles, trailers, drivers, passengers, locations, sites, reporting groups etc.

§ Gain access to other Fleet Manager data such as trip and event data, GPS data etc.

§ Store proprietary data in the Fleet Manager database.

§ Leverage off the Fleet Manager system three-tier client-server architecture to support multi-user environments.

1074
www.mixtelematics.com

1074
 1075

§ Leverage off the Fleet Manager Upgrade+ program to manage licensing.

§ And much more! Study the methods and properties of the ExtensionManager interface for more information and examples of
what is possible.

Every client-side Extension must implement the Extension4 interface described in the Fleet Manager Extension type library
(FMExtension.tlb). This allows the Extension Manager to load extensions that will only be developed in the future. It is important
that

you implement all the properties and methods of the interface, even if you only implement some as stubs with no functionality.
Failure to do so could result in errors when the Extension Manager attempts to call the missing property or method.

How do I use it?

To learn how to develop client-side Extensions, complete the client-side Extension Tutorials included in this SDK.

Recordset Enumerator
When the FM Extension SDK is installed, it installs a client-side Extension called the Recordset Enumerator. This tool is used to
display and print the structure of the ADOR recordsets returned by the data retrieval methods in the Extension Manager.

The Recordset Enumerator Extension will be loaded when you start the Fleet Manager Professional Client application and can be
accessed from the Tools menu. The Recordset Enumerator provides a single dialog enabling you to specify your requirements,
and view the definition of the resultant recordset.

There are three options for you to choose from; Retrieval Method, Object Type and Data Type. Depending on the value you
choose for Retrieval Method, either Object Type or Data Type is available. There are numerous possible values corresponding to
the data retrieval methods exposed by the Extension Manager.

Once you have selected the desired options, click the Retrieve Recordset button and the Extension will then retrieve the
recordset, enumerate it and display the column names and data types. Please refer to the ADO documentation for a description
of the various data types. The Print button can be used to print the results In some cases where there is no data available the
Extension cannot enumerate the recordset and the following message is displayed.
No data in result set
Unable to enumerate columns

1075
www.mixtelematics.com

1075
 1076
9.1.2 Server Extension Manager Component

© 2008 MiX Telematics | Updated 2008/06/25

Introduction
The Fleet Manager Server Extension Manager component (FMSExtMan8.DLL) is a COM DLL that exposes a hierarchy of
collections and objects within the Fleet Manager system. The component runs in-process of the server-side Extension that
instantiates it, thus applications that use this component do not require the Fleet Manager Professional Client executable to be
running.

Note: The Server Extension Manager component was specifically designed to enable developers to develop back office
applications that integrate with the Fleet Manager system. If you wish to develop an application to extend the user interface of the
Fleet Manager Professional Client application, you should use the Client Extension Manager interface.

Capabilities
Applications can be developed to use the FM Server Extension Manager component to:

· Read, add, modify or delete Fleet Manager static object data such as vehicles, trailers, drivers, passengers, locations, sites,
reporting groups etc.

· Gain access to other Fleet Manager data such as trip and event data, jobs, messages, GPS data etc.

· Import data into and export data out of the Fleet Manager database.

· Store proprietary data in the Fleet Manager database.

· Send free-text messages to vehicles.

· Send jobs to vehicles and query the status of jobs in real-time.

· Request the current position and status of vehicles in real-time.

· And much more! Study the Server Extension Manager's object hierarchy for more information and examples of what is
possible.

How do I use it?

To learn how to develop server-side Extensions, study the sample applications included in this SDK. These can be found in the
\Sample Source Code\Server-side Extensions\VB6 folder beneath the folder where you installed this SDK.

1076
www.mixtelematics.com

1076
 1077
9.1.3 XML Web Service

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
The Fleet Manager XML Web Service is an industry standard XML web service which runs on a Microsoft Internet Information
Service (IIS) web server within the Microsoft .NET framework. The XML Web Service exposes numerous web methods and
properties that can be accessed by posting XML requests in SOAP envelopes to the web server using the HTTP or HTTPS
protocols. Most of the capabilities of the Server Extension Manager component are available through the web service.

Capabilities
Applications can be developed to use the FM XML Web Service to:

· Read, add, modify or delete Fleet Manager static object data such as vehicles, trailers, drivers, passengers, locations, sites,
reporting groups etc.

· Gain access to other Fleet Manager data such as trip and event data, jobs, messages, GPS data etc.

· Import data into and export data out of the Fleet Manager database.

· Store proprietary data in the Fleet Manager database.

· Send free-text messages to vehicles.

· Send jobs to vehicles and query the status of jobs in real-time.

· Request the current position and status of vehicles in real-time.

· And much more! Study the methods and properties of the web service classes for more information and examples of what is
possible.

Although the service runs on Windows under IIS and .NET, it can be accessed from any platform supporting the HTTP or HTTPS
protocol.

How do I use it?

To learn how to develop web Extensions, study the sample applications included in this SDK. These can be found in the \Sample
Source Code\Web Extensions\C# folder beneath the folder where you installed this SDK.

1077
www.mixtelematics.com

1077
 1078
9.1.4 CI Language Tools

© 2008 MiX Telematics | Updated 2008/05/07

Introduction
CI Language Tools is a collection of tools used for providing multilingual support in your applications. It comprises a Language
Editor utility for creating and maintaining language sets, a Language Translator utility for translating language files and a
Language Manager COM component used by your application to retrieve strings from the language files. The following diagram
illustrates the use of these tools in the three distinct development, translation and runtime environments.

The development environment centres on the use of the Language Editor utility to create the language set. The translation
environment encompasses the use of the Language Translator utility to translate the strings within the individual language files.
The run-time environment is where the application program makes use of the Language Manager COM Component to control the
language under which the application is running and to retrieve language strings from the appropriate language file.

What is a language set?

A language set is a collection of files comprising the following:

§ Language Set file – the language set (.LS2) file is the file that ties the rest of the language set together. It is an XML file
containing all the details about the language set. It is also the primary document that the Language Editor edits. The individual
language files within the set are not visible from the Language Editor, allowing the developer to add languages and strings to
the set without needing to consider its underlying structure.

Note: Caution should be exercised if the language set XML file is edited with a tool other than the Language Editor. The
Language Editor provides a Create Schema function accessible from the File menu which can be used to generate the XML
schema (.XSD) file defining the language set file structure.

§ Language file – a language set contains one binary language (.LNG) file for each language in the set. When a set is being

1078
www.mixtelematics.com

1078
 1079

edited the developer adds, modifies and deletes strings in the primary language. The Language Editor provides a function to
Generate Language Files accessible from the File menu. Once language files have been translated using the Language
Translator, they can be imported back into the language set using the Language Editor's Import Language File function
accessible on the File menu.

§ Visual Basic Constant Module file – when the Language Editor saves the language set, a Visual Basic Constant Module (.BAS)
file is generated if the developer specifies a filename for it. This is a Visual Basic source module containing a list of public
constants used by your Visual Basic application program to refer to strings when retrieving them via the Language Manager
COM component.

§ C/C++ Constant Header file – when the Language Editor saves the language set, a C/C++ include (.H) file is generated if the
developer specifies a filename for it. This is a C/C++ source file containing a list of compiler definitions (# defines) used by your
C or C++ application program to refer to strings when retrieving them via the Language Manager COM component.

How do I use these tools?

To learn how to create and maintain language sets using the Language Editor and Language Translator utilities, complete the
Language Tools Tutorials included in this SDK. To learn how to develop an application to make use of a language set, study
Tutorial 3 in the client-side Extension section of this SDK.

1079
www.mixtelematics.com

1079
 1080

10 Marketing and Support

© 2008 MiX Telematics | Updated 2008/05/08

Overview
Welcome to the Fleet Manager Marketing and Product Support Index. This index contains links to the a number of useful
reference materials and other documentation. It is recommended that you read the documents in the order in which they appear
in this index.

Presentations
The following presentations on the Fleet Manager Product range are available on the Fleet Manager Office CD-ROM in D:
\Documents\English\Presentations where D:\ represents the CD-ROM Drive.

Fleet Manager - Solutions and FM Professional functionality

A PowerPoint Presentation describing the range of solutions FM Professional functionality and FM Extensions can offer you
including Driver Performance, Driver safety & behaviour modification, Vehicle Performance, Location Management, Tracking,
Messaging & Navigation and Accident Analysis.

Fleet Manager - Solutions.ppt

Fleet Manager - Modular Platform

Fleet Manager solutions benefit from a modular system architecture, making it easy to modify or expand an installation in line with
specific customer requirements.

Fleet Manager - Modular Platform.ppt

Fleet Manager - Packages

A PowerPoint Presentation describing the various product packages and software solutions Fleet Manager sell and support.

Fleet Manager - Packages.ppt

Product Support
For more information, please see Product Support

Offline Knowledge Base

The Offline Knowledge Base is a snapshot of the Online Knowledge Base available on http://www.fm-web.co.za. The Knowledge
Base contains various articles detailing problems found with Fleet Manager products and their solutions or work-arounds. For
more information, please see Offline Knowledge Base.

1080
www.mixtelematics.com

1080
 1081

10.1 Product Support

© 2008 MiX Telematics | Updated 2008/06/11

How to obtain Support

Support Channel

To provide the best possible level of support to users of the Fleet Manager system a clearly defined support channel has been
put into place. This not only allows the user to obtain answers to support issues as quickly as possible but also allows the
development teams to concentrate on enhancing the products rather than continually answering requests for support. To this end
the various levels in the channel have been given training allowing them to provide support to those further down the chain.

When any issues arise with the Fleet Manager software or units that require support the user will approach the distributor who will
attempt to resolve the issue. Should the distributor be unable to resolve the issue, the distributor will escalate the issue by
communicating with the regional distributor. Should the regional distributor be unable to resolve the issue, the regional distributor
will escalate the issue by communicating with the international distributor. Finally, in cases where the international distributor is
unable to resolve the issue, the international distributor will escalate the issue and communicate with the development teams.

There should be no need for direct communication between parties more than one level apart in the channel. However, in urgent
cases where a timely solution can not be reached it is possible for any level to log a request directly with the development teams
via the Development web site.

On-line Knowledge Base

As problems are investigated and solutions found, knowledge base articles are created detailing the problems and giving
solutions or work-arounds. The knowledge base can be accessed by connecting to the MiX Telematics web site at http://www.
mixtelematics.com. Once you are connected, select the Support link at the top of the screen to display the support page. The
Knowledge Base can then be accessed from the Search the Knowledge Base link.

Logging a Request via the Internet

1081
www.mixtelematics.com

1081
 1082

In cases of extreme urgency a request for support may be logged directly with the development teams. This is done by
connecting to the support page of the Development web site and selecting the Log a Service Request link.

A data entry screen will be displayed into which details of the request must be entered.

You should complete this form with as many details as you can. It is particularly important that you give a full description of the
problem that prompted the request. The more information you can provide on the problem, the better the chances are of a quick
solution being provided.

Once your request has been received you will receive feedback on what actions will be taken to resolve the problem.

1082
www.mixtelematics.com

1082
 1083

10.2 Fleet Management Systems Offline Knowledge Base

Fleet Management Systems

Offline Knowledge Base (generated 27 March 2008)

CI Data

CITAS 2010

EV100

Fleet Manager 98

Fleet Manager 2000

Fleet Manager 2001

Fleet Manager 2002 Professional

FM100

FM200

All Articles, includes articles for non-fleet products

NOTE: The offline knowledge base is a snapshot of the online knowledge base and it is possible that hyperlinks within articles
may become invalid over time. Should you encounter any invalid links, the valid link can always be found in the corresponding
article in the online knowledge base.

Online Knowledge Base

The Online Knowledge Base is updated regularly. If you have Internet access, please visit the support section of our website at
http://www.mixtelematics.com to view new and updated articles.

1083
www.mixtelematics.com

1083
 1084
10.2.1 All Articles

Title KB No.

Software unable to read data from the download module 1

Shurlok EV100 Year 2000 compliance (Y2k) 2

When trying to print a report, error 50524 is displayed 3

When trying to print a report, error 50500 is displayed 4

Error 3050 occurs when running the software 5

When downloading data or clicking on the International tab of the Options dialog, error 13: Type Mismatch is
6
displayed

How do I access the information in the system using Access 97? 7

CITAS 2010 Year 2000 compliance (Y2k) 8

CI Data Year 2000 compliance (Y2k) 9

FM Kienzle Fleet Manager 100 Year 2000 compliance (Y2k) 10

CTL3D32.DLL incorrect version on Windows 95 with Novell Netware Client Shell installed 11

The default backup reminder period of one day cannot be changed 12

.ECU file cannot be restored 13

Trips with a very short distance show a very high average speed 14

Reports display incorrect ODO reading 15

'Time in Green Band' column should be labeled 'Time out of Green Band' 16

Error when initialising a driver plug 17

Windows dealer utility reports incorrect date and time on driver plug. 18

Total sum for vehicles in detailed daily trip report is incorrect 19

Incorrect serial number printed on registration card 20

Overflow Error on download if the driver ID is a negative number 21

Changing trip details in the driver activity timeline causes an error 22

Boolean (digital) events with False parameter settings do not work 23

1084
www.mixtelematics.com

1084
 1085

Title KB No.

How do I rotate a 3D graph in the Fleet Manager software? 24

Manual Installation of FM '98 software 25

Error creating database during installation 26

Error updating the FM '98 Database 27

Negative slope input configuration 28

FM100 reports do not fit on US Letter paper 29

What's new in CI Data version 1.50 (SR1) 30

What's new in CITAS 2010 version 2.00 31

What's new in Shurlok EV100 version 1.6 (SR2) 32

What's new in Fleet Manager 100 version 1.20 (SR4) 33

16 bit Fleet Software fails to run under Windows 95, 98, or NT 34

16 bit Software - Error executing graph 35

When I try to generate a report, Error 13 with no description is displayed 36

How to configure the Fleet Manager application for client-server 37

'Invalid Procedures for Processing Event Type' During FM200 Download 38

Fleet Manager Terminology (FM200(e) Unit) 39

Fleet Manager Software procedure to follow when an FM200(e) unit is swapped 40

Fleet Manager Software procedures for when a FM200(e) Unit is cleared 41

Guidelines for Report Logo Images 42

Report generation finishes but the report is not displayed. 43

CITAS 2010 - Divide by zero generating Driver Score Report 44

FM Kienzle Fleet Manager Software Year 2000 Compliance (Y2K) 45

What's New in FM Kienzle Fleet Manager 98 version 3.00 (SR1) 46

FM98 - Error 3001 when program starts 47

1085
www.mixtelematics.com

1085
 1086

Title KB No.

unInstaller Fails to Initialise on Windows NT 48

'Invalid SelectionIDs' when Opening Criteria File. 49

16 bit Fleet Products on a Network 50

Exported spreadsheet shows dates in place of times. 51

Tacho data graph shows incorrect Road Speed values 52

Fleet Manager 98 Timeline Displays Incorrectly (FM100) 53

Fleet Manager 98 Daily Trip Report has no Standing Time (FM100) 54

Error During FM98 SR1 Install: 'Microsoft Data Access Components 2.0 is required.' 55

Error 2004 occurs when generating a report 56

Error -214721887 (3022) when downloading 57

Tacho data graph shows zero values for the auxilliary frequency input (F3) 58

Fleet Manager Installation Resets DCOM Configuration Settings 59

How do I specify the order for .cri files in a Report Batch? 60

FM Kienzle Fleet Manager Software with Microsoft Office 2000 61

Driver Reports Not Available 62

Cannot Save or Print Reports 64

Data Pro Service Online & Centre-Point Year 2000 Compliance (Y2K) 65

Events Utilising the System Override Plug Do Not Work 66

How To Create a Plug Dump 67

Over Speeding is shown as km/h on Event Export, but units are displayed as mph 68

Incorrect column types in Excel exports 69

Overflow Error When Adding or Viewing KB Article 70

OLEMSG32.DLL Fails to Register during Service Online & Centre-Point Installation 71

Error 105 When the software Loads 72

1086
www.mixtelematics.com

1086
 1087

Title KB No.

New Events Not Visible on Timeline 73

Out Of Memory Errors in FM98 and FM2000 74

KB Article Won't Print from Netscape Navigator 75

New Events Not Being Recorded For Vehicle 76

Error 3167 while Downloading 77

Error -2147217887 Executing the Swap Unit Function 78

Fleet Manager 98/2000 software reports different driving times than FM100 software does. 79

The FM Kienzle Fleet Manager database is not a valid database file. 80

Multiple Drivers Driving one Vehicle 81

After SR1 Install, FM98 stops working 82

Fatal Error when Installing 16 bit Fleet Products under Windows 98 83

Repeating Message Box occurs on Profile Edit 84

Error 3026 on Compact 85

Error 52 or 53 when trying to save a Criteria file 86

Data for Events defined on one PC not being stored on another 87

Tacho Data Recorded While Vehicle is Stationery 88

The 'Elapsed Time' reported for an Event Occurrance is Incorrect 89

Cancelling Reports 'Hangs' the system 90

Managing Large Databases with FM98 and FM2000 91

Max RPM Shows Higher than RPM on Tacho Graph 92

Max RPM Shows Lower than RPM on Tacho Graph 93

FM100 Idle Configuration Incorrect 94

'Invalid Use of Null' Trying to add/modify a Service Request 95

Installation Fails on Windows 98 Second Edition (Win98 SE) 96

1087
www.mixtelematics.com

1087
 1088

Title KB No.

Error on Clear Data and Delete (The data you tried to update is in use...) 97

Error 324 on Download 98

Rules for Creating and Upgrading Fleet Manager Databases 99

Errors when attempting to backup database 100

Activity Timeline Statistics Don't Display Correctly 101

Not a valid snapshot file 102

Parking time calculation on detailed trip reports 103

FM200(e) Events appear permanently 'on' in Activity Timeline 104

Idle Occurring Outside of a Trip 105

Error 429 On Download when using Win98 SE 106

No Idling or Ignition events recorded 107

Incorrect Data from Fuel Recorder (EDM) 108

Error 50104 trying to access the download module 109

New Status not visible from SR page 110

'Closed' Service Requests no longer visible 111

Overflow Error on Create/Update database 112

What's New in FM Kienzle Fleet Manager 98 SR1a 113

Events Based on Trip Distance Don't Work 114

All 2010 Interval Data Gets Rejected On Download 115

EDM Data on Tacho Graph shows zero values 116

Activity Timeline Displays incorrect l/100km 117

How do I access the information in the system using Access 2000? 118

Divide By Zero error occurs on Activity Timeline 119

Error 2201 occurs when generating a report 120

1088
www.mixtelematics.com

1088
 1089

Title KB No.

Error 50104 occurs, and my software is installed into a disk drive other than C: 121

Error 53 After Modifying Reader Options 122

Fleet Manager on a Novell Netware server 123

Modifying Input or Service Information at Config Group doesn't update Vehicle 124

General Protection fault (Access Violation) Generating a Report 125

Error -113 During Installation of FM98 Software 126

Spaces in SOL/CP Message Headers 127

Adding or Editing an SR 'Hangs' the Server 128

'Store Average Value' for Events Does Not Work 129

Mail no longer works after IE4 Install 130

HTTP Error 403 or 405 accessing SOL/CP 131

FMTerminal Date Displays Incorrectly 132

Centre-Point Fails to Unlock 133

CPMail MAPI_E_TIMEOUT & MAPI_E_NOT_FOUND errors 134

Vehicle trip report figures do not balance when there are days with no trips 135

Incorrect readings from EDM 136

Discrepancies between Odometer Reading and Distance on Performance Summary Report 137

Error 429 During Installation or Trying to Open the Software 138

Error -113 During Installation of Fleet Manager on Eastern OS 139

Date Capturing and the CITAS 2010 Hand-Held 140

Having Centre-Point 'Strip Out' Original Message Texts 141

APCLog.txt File Grows Very Large 142

How to Clear the Memory from an FM100 Unit 143

Noisy FMTerminal Units 144

1089
www.mixtelematics.com

1089
 1090

Title KB No.

FMTerminal Display Unreadable 145

'Invalid DDR Path Specified' even if it exists 146

No DDR's found, even if they exist 147

'Allowed to Login' Query does not show Organisation Contacts 148

Report/Graph Criteria: From Date Greater Than To Date 149

'Type Mismatch' Error clicking on the International Tab 150

Contact No Longer Has a Username or Password Defined 152

Trip Report or Driving Errors Report Prints Blank or Generates an Error Message 153

I can't find the FM Upgrade+ Registration Card on the FM2000 CD 154

CPMail Memory Usage Increases 155

Error 50504 when trying to generate a report 156

Administrator Program can't lock Database 157

Daylight Savings Not Updating 158

Can't Upgrade Database After SR1a Install 159

What's New in CI Data version 2.0? 160

What's New in Shurlok EV100 version 2.0? 161

Can't Upgrade Database After FM2000 Install 162

What's new in CITAS 2010 version 2.20? 163

'Unknown' Error Reported in Fuel Consumption Graph 164

'No Code Plug Found' (Code Plug is in Pod) running under NT or 2000 165

CPMail 'Queued message could not be sent because no addresses were supplied.' 166

Error -132 during SR1a Install 167

'Method '~'...' when clicking OK/Apply on the Vehicle dialog 168

'Distance' and 'Duration' columns missing 169

1090
www.mixtelematics.com

1090
 1091

Title KB No.

What's New in FM Kienzle Fleet Manager 98, SR1b 170

Initialise Plug, no Vehicles of Type Causes Problems 172

'System Override' Option Enabled for FM100 Event 173

'Unknown Drivers' prints zeroes on Driver Score Report 174

FMServer.exe Access Violation on Driver Scoring Report 175

Modify Fuel Entry results in two entries 176

Cancel Vehicle Form still updates plug, or asks to update plug 177

How To Implement Remote Downloading 178

FMTerminal Event Report always displays 'Unknown Driver' 179

Port settings reset when upgrading with FM2000 180

Can’t log in to Centre-Point 181

Error -113 During Installation of Fleet Manager Software 182

Centre-Point Mail Server does not send mail 183

Error 3075 Generating Event Report 184

Fuel Entries 'Missing' After Upgrade to CI Data v2.0 185

Error 94 while downloading a vehicle plug 186

What's New in FM Kienzle Fleet Manager 2000 187

Scale Incorrect on Fuel Consumption Graph 188

Trips or Events 'On' for Extended Periods of Time 189

Run-time error '3265' when trying to use FM Object Finder Extension 190

Driver Trip report for ONE Driver displays ALL Drivers 191

Error running reports from SR1b 192

What's new in Fleet Manager 100 version 2.00 193

Beep and Flash Codes Made EASY 194

1091
www.mixtelematics.com

1091
 1092

Title KB No.

Fleet Manager 2000 hangs while loading 195

No reports under FM98SR1b 196

How to change graph defaults 197

Error 13 when trying to generate Event Report/Activity Timeline 198

Error when attempting to create a new language set 199

FM Kienzle SI No. 381008 - Using the Fleet Manager Software FM100 with Windows 2000 200

FM Kienzle SI No. 381005 - Fleet Manager 100 -- Operation with an external speed signal sender 203

Importing FM100 Version 2 database into FM98/FM2000 fails 204

FM98 SR1b Reports hangs 205

Relay Enabled parameter incorrectly set 206

Runtime error '40052' when accessing vehicle servicing 207

Unable To Upload Customised FM Terminal Menu Script 208

PC won't shutdown while FMAPC is running 209

FM Kienzle SI No. 382012 - Using the FM200 with the Mercedes Benz PSM-Module (parameterizable special
210
module)

F3 parameter does not accept 'Units' description when added 211

Fleet Manager on Windows ME 212

Error 3075 when generating ANY Report 213

Latest Device Drivers for FM200 and FMTerminal 214

How To Add More Digital Inputs To The FM200 215

Is the FM200 / FM300 Unit Intrinsically Safe? 216

Connecting A Keyboard or Barcode Scanner To The FM Terminal 217

FM2000SE extensions not to be installed with previous versions of FM 218

When to use the Event Configuration File (.ecf) 219

Abnormally high duration values on Daily Driver Trip report 220

1092
www.mixtelematics.com

1092
 1093

Title KB No.

FMDealer displays no text 221

Error when printing report in FM100 version 2 222

Error selecting 'Is Not' in Contact Organisation combo on adhoc query. 223

FMClient hangs after installing FMAPC 224

Centre-Point Database Grows Abnormally Large (Centre-Point causes Infinite E-Mail loop) 225

Paper Size Error when printing report 226

Reload DDRs after upgrading to FM2000SE 227

Exported Vehicle Configuration Report vs Snapshot version of the report 228

Setting arming delay in Vehicle Configuration Group to less than 1 minute 229

Pulse counter not accepted by software 230

Geo-fencing not recording 231

KTCO modes not recorded correctly 232

Contact can still change SR Status on an empty 'New Status' Combo 233

Error when exporting large report 234

Copy Vehicle Feature duplicates the unit phone number 235

Data discrepancies in reports - FM2001 236

No data recorded with EDM on I1-I4 237

What's new in Fleet Manager 100 version 2.50 238

Data discrepancies in reports - FM2000 239

Error 91 when uploading configuration to vehicle plug 240

MSDE Installation 241

Running FM2001 with Microsoft SQL Server 2000 242

Error 3021 when no devices connected to F2 243

Error when uploading FM100 configuration 244

1093
www.mixtelematics.com

1093
 1094

Title KB No.

PreProcessFM200Data error while downloading in FM2001SR2 245

Incorrect start time on Event Report 246

EDM Data not Recorded when Connected to Analogue Lines. 247

Calculation of Fuel Consumption in the FM software 248

Unable to restore backed up database 249

ASP Script Errors in FMOnline 250

Guide to Time synchronisation setup for GSM 251

Reports take very long to generate 252

42V Trucks and FM200 voltage 253

Plug Downloads - ASP Errors 254

Why do I need to execute the Swap unit functionality 255

Time-synchronisation issues 256

Configuring Engine hours 257

Problem with negative ID's 258

Tachometer / Speedometer / Rev Counter values not displayed correctly. 259

CallDMI error occurs in GSM Download 260

Long calls to GSM modem connected to FM200 261

Activity Timeline and Trip Report trip data and event data inconsistency 262

Changing sim card causes ID verification to fail first time around, Using no PIN 263

How to recover a TrailerID's lost ID 264

Invalid property error while adding event 265

When changing from FMOnline mode the FM Client needs to be restarted 266

GPS Log Viewer buttons and menus are disabled 267

Timeline Reports prints incorrectly 268

1094
www.mixtelematics.com

1094
 1095

Title KB No.

TCO diagnostics 269

Things to take into account when connecting speed line 270

How to enable Autopoll backups 271

Detailed Trip report hangs for large scope of data 272

How to import Location data 273

FM2002 initialised driver plug does not disarm FM unit 274

Trailer ID extension strings displays in English if Spanish is selected as preferred language 275

Mutliplug aborts in FM2002 Client 276

FM200 loses its Calibration, Odometer, or Vehicle ID 277

Recommended GPS installation 278

Not able to connect more than one FM200e device at a time 279

Nokia 6090 issues 280

Error when connecting to SQL Server 281

Error upgrading FM2001 (SR1/SR2) database to FM2002 282

Pre Paid functionality in Fleet Manager 283

After uninstalling and reinstalling MSDE, I cannot open my existing database or create a new one 284

Activity timeline details displayed incorrectly 285

No checkboxes on RTF report 286

Missing Dutch Language Files 287

Using COM ports higher than COM1 to COM4 with the SMS Processor 288

Setting engine hours via GSM 289

Power management with the FM200PLUS unit and its positive drive 290

FM-Terminal Custom Script Update 291

Reload DDMs after upgrading to FM2002 SR1 292

1095
www.mixtelematics.com

1095
 1096

Title KB No.

Error connecting to a DB without permission 293

FM200 Plus Device Driver Upgrade 294

Data download stops at processing phase 295

TCO 1319 & ELVIST 296

FM200 Plus configuration uploaded to FM200 unit via GSM 297

Importing suburb location data using the GPS Log Viewer 298

Downloaded data not showing in database 299

Maximum SMS sent when active tracking enabled event becomes true 300

Ensuring successful remote vehicle configuration upload 301

FM Lite and USB Printer 302

Updated DCOM Client/Server installation procedure 303

Connecting devices to the FM200 Plus Serial cable 304

Additional Location Reports functionality 305

Driver Scoring Reports displays incorrect data 306

Fleet Manager 2002 SR1 January 2003 release patches and updates 307

Pulse count incorrect on F4 308

Fleet Manager 2002 SR1 Patch 8 309

SMS Processor terminates abnormally 310

F4/I8 input on the FM200 Plus unit 312

HOW TO correct a date jump on an FM unit 313

Tips when using the Nokia D211 314

FM200 Plus calibration & GPS 315

GSM Downloader on faster computers 316

Interval data on the FM200 and FM200 Plus 317

1096
www.mixtelematics.com

1096
 1097

Title KB No.

Client appears to hang when saving tacho graph 318

FM Dealer Utility versions 319

FM and Siemens MC35i modem 320

FM unit current consumption 321

FM GPRS Gateway 322

Optimising location events 323

One FM Upgrade+ NFR package per GPRS Gateway registration 324

Configuring FM GPRS to use the GPRS Gateway 325

FM Client aborts after unloading extension 326

Fleet Manager Trailer ID Odometer 327

The Significance of the Company ID in the FM system 328

FM 200 Communicator and GSM data download 329

Controlling device power by Relay 330

Loading FM Terminal scripts on Fleet Manager 8 331

FM Professional 8 and MSDE 332

Installing the Fleet Manager Professional 8 Update 333

Using GPS Velocity as speed 334

What's New in FM Dealer Utility (version number 2.11.2.0) 335

Force Fleet Manager database upgrade in network environment 336

Upgrading Fleet Manager Professional 8 database to FM8 Update 337

Event Mismatch Error Message 339

Event consumption report - treeview explained 340

Event Consumption Report extension - closing report 341

Typical Crystal reporting issues 342

1097
www.mixtelematics.com

1097
 1098

Title KB No.

Reports hanging 343

How to connect and setup a Pocket PC 344

Setting up GPS velocity as speed on GARMIN GPS 345

Forcing device driver upload via GPRS/GSM 347

DiagGPRSRouter.log - column heading definition 348

FMLite Report issue 349

GPRS Service memory management 350

Enhancing FM Autopoll Client performance 351

How to set up an FM300 unit in the Fleet Manager software prior to FM8.3 352

Setting up WiFi 353

FleetManager Professional 8.31 update 1 355

Modified GPRS Service for FM300 units 356

GPRS package number 357

Timeout on device driver upload via GPRS 358

No speed recorded when 'only consider gps as speed when ignition is turned on' option is selected 359

Specific Absorption Rate of Fleet Manager Products 361

Digital Hands Free Kit 362

Changing From GSM or GPRS Modem Function Beneath Roaming 365

FM 100 device configuration does not reflect buzzer settings 366

FM Locator GPS issue 367

GSM downloader is causing a GPF if modems other than MC35 are used 368

Regional settings on Google Earth 369

Error when generating a locations report using reverse geo lookup 370

DECT downloader issues 371

1098
www.mixtelematics.com

1098
 1099

Title KB No.

Issues while upgrading a FM2002 database 372

FM300 GSM modem does not wake up 373

FM300 Communicator stops running after attempting remote device drivers uploads 374

General networking principles for Fleet Manager installations 375

How to enable WiFi Diagnostic information on the FM Terminal 376

Upgrade Plus Registration information and FAQ 377

Allowing a user with standard user permissions to use Fleet Manager 8 software 378

HOW TO connect both PDA and DTCO to the FM300 Communicator at the same time 379

Free-Text messaging from Dayton to mobile phone 380

No communication between OBC and PC5200PRO 381

VDO Dayton Active Job Message corruption & guidance issues 383

Active tracking - sort on 'Last GPS Point' 384

New Mapset for FM8.3 385

Wifi on S2 or S3 - Device drivers 386

Spurious speed pulses when using Hunter CAN Bus 387

EnP Extension RAG YTD 388

Back-up battery Information 389

Vehicles not appearing on 'Live Tracking' window in FM-Web 390

Replacement of Hands Free Kit with the FM Voice Kit 391

FM Lite with USB Download Module 392

Analogue Inputs On FM200 Plus/FM300 393

How to set up FM Tracer unit with FM-Web 394

FM-Web - Google Earth Maps 395

FM Professional 8.35 Location Reports 396

1099
www.mixtelematics.com

1099
 1100

Title KB No.

GPS Velocity as Speed 397

Cannot download BIN file from FM-Web 398

Specific Absorbtion Rate (SAR) of FM Product 399

MapViewer in FM8.35 blocked after updating an older database 400

Windows Vista compatibility with Fleet Manager Professional 401

Modem Initialisation Strings 402

Comms Suite Fails In FM9.0 403

FM9 vehicle configuration upload fails 404

GPRS mail notifications on FM9.0 405

FM9.0 Update 406

TM9.0 Update 407

FM9.0 GSM Downloader error 408

FM Garmin Compatibility 409

FM Professional 9 Compatibility with XP SP3 410

Configuration Error when uploading to CAN unit in FM9.0 411

WLAN modules not transmitting any trip data 412

How to install SQL with FM9.0 onwards 413

How to reformat csv files from FMWeb for calculation 414

Error 429 - FM 9.0 in Remote mode 415

Uploading Extended Config using FM9.0 416

FM9. Extended Config Uploads Via Comms scheduler 417

1100
www.mixtelematics.com

1100
 1101
10.2.2 CI Data

Title KB No.

Software unable to read data from the download module 1

When trying to print a report, error 50524 is displayed 3

When trying to print a report, error 50500 is displayed 4

Error 3050 occurs when running the software 5

How do I access the information in the system using Access 97? 7

CI Data Year 2000 compliance (Y2k) 9

What's new in CI Data version 1.50 (SR1) 30

16 bit Fleet Software fails to run under Windows 95, 98, or NT 34

16 bit Software - Error executing graph 35

16 bit Fleet Products on a Network 50

Fatal Error when Installing 16 bit Fleet Products under Windows 98 83

How do I access the information in the system using Access 2000? 118

Report/Graph Criteria: From Date Greater Than To Date 149

'Type Mismatch' Error clicking on the International Tab 150

Trip Report or Driving Errors Report Prints Blank or Generates an Error Message 153

What's New in CI Data version 2.0? 160

'No Code Plug Found' (Code Plug is in Pod) running under NT or 2000 165

'Distance' and 'Duration' columns missing 169

Fuel Entries 'Missing' After Upgrade to CI Data v2.0 185

Driver Trip report for ONE Driver displays ALL Drivers 191

1101
www.mixtelematics.com

1101
 1102
10.2.3 CITAS 2010

Title KB No.

When trying to print a report, error 50524 is displayed 3

When trying to print a report, error 50500 is displayed 4

Error 3050 occurs when running the software 5

How do I access the information in the system using Access 97? 7

CITAS 2010 Year 2000 compliance (Y2k) 8

What's new in CITAS 2010 version 2.00 31

16 bit Fleet Software fails to run under Windows 95, 98, or NT 34

16 bit Software - Error executing graph 35

CITAS 2010 - Divide by zero generating Driver Score Report 44

16 bit Fleet Products on a Network 50

Fatal Error when Installing 16 bit Fleet Products under Windows 98 83

All 2010 Interval Data Gets Rejected On Download 115

How do I access the information in the system using Access 2000? 118

Error 53 After Modifying Reader Options 122

Error 429 During Installation or Trying to Open the Software 138

Date Capturing and the CITAS 2010 Hand-Held 140

Report/Graph Criteria: From Date Greater Than To Date 149

What's new in CITAS 2010 version 2.20? 163

What's New in FM Kienzle Fleet Manager 2000 187

1102
www.mixtelematics.com

1102
 1103
10.2.4 EV100

Title KB No.

Software unable to read data from the download module 1

Shurlok EV100 Year 2000 compliance (Y2k) 2

When trying to print a report, error 50524 is displayed 3

When trying to print a report, error 50500 is displayed 4

Error 3050 occurs when running the software 5

How do I access the information in the system using Access 97? 7

What's new in Shurlok EV100 version 1.6 (SR2) 32

16 bit Fleet Software fails to run under Windows 95, 98, or NT 34

16 bit Software - Error executing graph 35

16 bit Fleet Products on a Network 50

Fatal Error when Installing 16 bit Fleet Products under Windows 98 83

How do I access the information in the system using Access 2000? 118

Report/Graph Criteria: From Date Greater Than To Date 149

'Type Mismatch' Error clicking on the International Tab 150

Trip Report or Driving Errors Report Prints Blank or Generates an Error Message 153

What's New in Shurlok EV100 version 2.0? 161

'No Code Plug Found' (Code Plug is in Pod) running under NT or 2000 165

'Distance' and 'Duration' columns missing 169

Driver Trip report for ONE Driver displays ALL Drivers 191

What's new in Fleet Manager 100 version 2.50 238

1103
www.mixtelematics.com

1103
 1104
10.2.5 Fleet Manager 98

Title KB No.

Software unable to read data from the download module 1

How do I access the information in the system using Access 97? 7

CTL3D32.DLL incorrect version on Windows 95 with Novell Netware Client Shell installed 11

The default backup reminder period of one day cannot be changed 12

.ECU file cannot be restored 13

Trips with a very short distance show a very high average speed 14

Reports display incorrect ODO reading 15

'Time in Green Band' column should be labeled 'Time out of Green Band' 16

Error when initialising a driver plug 17

Windows dealer utility reports incorrect date and time on driver plug. 18

Total sum for vehicles in detailed daily trip report is incorrect 19

Incorrect serial number printed on registration card 20

Overflow Error on download if the driver ID is a negative number 21

Changing trip details in the driver activity timeline causes an error 22

Boolean (digital) events with False parameter settings do not work 23

How do I rotate a 3D graph in the Fleet Manager software? 24

Manual Installation of FM '98 software 25

Error creating database during installation 26

Error updating the FM '98 Database 27

Negative slope input configuration 28

When I try to generate a report, Error 13 with no description is displayed 36

How to configure the Fleet Manager application for client-server 37

'Invalid Procedures for Processing Event Type' During FM200 Download 38

1104
www.mixtelematics.com

1104
 1105

Fleet Manager Terminology (FM200(e) Unit) 39

Fleet Manager Software procedure to follow when an FM200(e) unit is swapped 40

Fleet Manager Software procedures for when a FM200(e) Unit is cleared 41

Guidelines for Report Logo Images 42

Report generation finishes but the report is not displayed. 43

FM Kienzle Fleet Manager Software Year 2000 Compliance (Y2K) 45

What's New in FM Kienzle Fleet Manager 98 version 3.00 (SR1) 46

FM98 - Error 3001 when program starts 47

unInstaller Fails to Initialise on Windows NT 48

'Invalid SelectionIDs' when Opening Criteria File. 49

Exported spreadsheet shows dates in place of times. 51

Tacho data graph shows incorrect Road Speed values 52

Fleet Manager 98 Timeline Displays Incorrectly (FM100) 53

Fleet Manager 98 Daily Trip Report has no Standing Time (FM100) 54

Error During FM98 SR1 Install: 'Microsoft Data Access Components 2.0 is required.' 55

Error 2004 occurs when generating a report 56

Error -214721887 (3022) when downloading 57

Tacho data graph shows zero values for the auxilliary frequency input (F3) 58

Fleet Manager Installation Resets DCOM Configuration Settings 59

How do I specify the order for .cri files in a Report Batch? 60

FM Kienzle Fleet Manager Software with Microsoft Office 2000 61

Driver Reports Not Available 62

Cannot Save or Print Reports 64

Events Utilising the System Override Plug Do Not Work 66

Over Speeding is shown as km/h on Event Export, but units are displayed as mph 68

1105
www.mixtelematics.com

1105
 1106

Incorrect column types in Excel exports 69

Error 105 When the software Loads 72

New Events Not Visible on Timeline 73

Out Of Memory Errors in FM98 and FM2000 74

New Events Not Being Recorded For Vehicle 76

Error 3167 while Downloading 77

Error -2147217887 Executing the Swap Unit Function 78

Fleet Manager 98/2000 software reports different driving times than FM100 software does. 79

The FM Kienzle Fleet Manager database is not a valid database file. 80

Multiple Drivers Driving one Vehicle 81

After SR1 Install, FM98 stops working 82

Repeating Message Box occurs on Profile Edit 84

Error 3026 on Compact 85

Error 52 or 53 when trying to save a Criteria file 86

Data for Events defined on one PC not being stored on another 87

Tacho Data Recorded While Vehicle is Stationery 88

The 'Elapsed Time' reported for an Event Occurrance is Incorrect 89

Cancelling Reports 'Hangs' the system 90

Managing Large Databases with FM98 and FM2000 91

Max RPM Shows Higher than RPM on Tacho Graph 92

Max RPM Shows Lower than RPM on Tacho Graph 93

FM100 Idle Configuration Incorrect 94

Installation Fails on Windows 98 Second Edition (Win98 SE) 96

Error on Clear Data and Delete (The data you tried to update is in use...) 97

Error 324 on Download 98

1106
www.mixtelematics.com

1106
 1107

Rules for Creating and Upgrading Fleet Manager Databases 99

Errors when attempting to backup database 100

Activity Timeline Statistics Don't Display Correctly 101

Not a valid snapshot file 102

Parking time calculation on detailed trip reports 103

FM200(e) Events appear permanently 'on' in Activity Timeline 104

Idle Occurring Outside of a Trip 105

Error 429 On Download when using Win98 SE 106

Incorrect Data from Fuel Recorder (EDM) 108

Error 50104 trying to access the download module 109

Overflow Error on Create/Update database 112

What's New in FM Kienzle Fleet Manager 98 SR1a 113

Events Based on Trip Distance Don't Work 114

EDM Data on Tacho Graph shows zero values 116

Activity Timeline Displays incorrect l/100km 117

How do I access the information in the system using Access 2000? 118

Divide By Zero error occurs on Activity Timeline 119

Error 2201 occurs when generating a report 120

Error 50104 occurs, and my software is installed into a disk drive other than C: 121

Fleet Manager on a Novell Netware server 123

Modifying Input or Service Information at Config Group doesn't update Vehicle 124

General Protection fault (Access Violation) Generating a Report 125

Error -113 During Installation of FM98 Software 126

'Store Average Value' for Events Does Not Work 129

Vehicle trip report figures do not balance when there are days with no trips 135

1107
www.mixtelematics.com

1107
 1108

Incorrect readings from EDM 136

Discrepancies between Odometer Reading and Distance on Performance Summary Report 137

Error 429 During Installation or Trying to Open the Software 138

Error -113 During Installation of Fleet Manager on Eastern OS 139

APCLog.txt File Grows Very Large 142

'Invalid DDR Path Specified' even if it exists 146

No DDR's found, even if they exist 147

Report/Graph Criteria: From Date Greater Than To Date 149

Administrator Program can't lock Database 157

Daylight Savings Not Updating 158

Can't Upgrade Database After SR1a Install 159

Can't Upgrade Database After FM2000 Install 162

'Unknown' Error Reported in Fuel Consumption Graph 164

Error -132 during SR1a Install 167

'Method '~'...' when clicking OK/Apply on the Vehicle dialog 168

What's New in FM Kienzle Fleet Manager 98, SR1b 170

Initialise Plug, no Vehicles of Type Causes Problems 172

'System Override' Option Enabled for FM100 Event 173

'Unknown Drivers' prints zeroes on Driver Score Report 174

FMServer.exe Access Violation on Driver Scoring Report 175

Modify Fuel Entry results in two entries 176

Cancel Vehicle Form still updates plug, or asks to update plug 177

How To Implement Remote Downloading 178

Error -113 During Installation of Fleet Manager Software 182

Error 3075 Generating Event Report 184

1108
www.mixtelematics.com

1108
 1109

Scale Incorrect on Fuel Consumption Graph 188

Trips or Events 'On' for Extended Periods of Time 189

Error running reports from SR1b 192

No reports under FM98SR1b 196

Importing FM100 Version 2 database into FM98/FM2000 fails 204

FM98 SR1b Reports hangs 205

1109
www.mixtelematics.com

1109
 1110
10.2.6 Fleet Manager 2000

Title KB No.

Software unable to read data from the download module 1

How do I access the information in the system using Access 97? 7

CTL3D32.DLL incorrect version on Windows 95 with Novell Netware Client Shell installed 11

How do I rotate a 3D graph in the Fleet Manager software? 24

Error creating database during installation 26

How to configure the Fleet Manager application for client-server 37

Fleet Manager Terminology (FM200(e) Unit) 39

Fleet Manager Software procedure to follow when an FM200(e) unit is swapped 40

Fleet Manager Software procedures for when a FM200(e) Unit is cleared 41

Guidelines for Report Logo Images 42

Report generation finishes but the report is not displayed. 43

FM Kienzle Fleet Manager Software Year 2000 Compliance (Y2K) 45

Exported spreadsheet shows dates in place of times. 51

Error 2004 occurs when generating a report 56

Tacho data graph shows zero values for the auxilliary frequency input (F3) 58

Fleet Manager Installation Resets DCOM Configuration Settings 59

How do I specify the order for .cri files in a Report Batch? 60

FM Kienzle Fleet Manager Software with Microsoft Office 2000 61

Driver Reports Not Available 62

Incorrect column types in Excel exports 69

Error 105 When the software Loads 72

New Events Not Visible on Timeline 73

Out Of Memory Errors in FM98 and FM2000 74

1110
www.mixtelematics.com

1110
 1111

Fleet Manager 98/2000 software reports different driving times than FM100 software does. 79

The FM Kienzle Fleet Manager database is not a valid database file. 80

Multiple Drivers Driving one Vehicle 81

Repeating Message Box occurs on Profile Edit 84

Error 3026 on Compact 85

Data for Events defined on one PC not being stored on another 87

Tacho Data Recorded While Vehicle is Stationery 88

The 'Elapsed Time' reported for an Event Occurrance is Incorrect 89

Cancelling Reports 'Hangs' the system 90

Managing Large Databases with FM98 and FM2000 91

Max RPM Shows Higher than RPM on Tacho Graph 92

Max RPM Shows Lower than RPM on Tacho Graph 93

Installation Fails on Windows 98 Second Edition (Win98 SE) 96

Error 324 on Download 98

Rules for Creating and Upgrading Fleet Manager Databases 99

Errors when attempting to backup database 100

Activity Timeline Statistics Don't Display Correctly 101

Not a valid snapshot file 102

Parking time calculation on detailed trip reports 103

FM200(e) Events appear permanently 'on' in Activity Timeline 104

Idle Occurring Outside of a Trip 105

Error 429 On Download when using Win98 SE 106

Incorrect Data from Fuel Recorder (EDM) 108

Error 50104 trying to access the download module 109

Events Based on Trip Distance Don't Work 114

1111
www.mixtelematics.com

1111
 1112

EDM Data on Tacho Graph shows zero values 116

Activity Timeline Displays incorrect l/100km 117

How do I access the information in the system using Access 2000? 118

Divide By Zero error occurs on Activity Timeline 119

Error 2201 occurs when generating a report 120

Error 50104 occurs, and my software is installed into a disk drive other than C: 121

Fleet Manager on a Novell Netware server 123

Modifying Input or Service Information at Config Group doesn't update Vehicle 124

General Protection fault (Access Violation) Generating a Report 125

Error -113 During Installation of FM98 Software 126

'Store Average Value' for Events Does Not Work 129

FMTerminal Date Displays Incorrectly 132

Vehicle trip report figures do not balance when there are days with no trips 135

Incorrect readings from EDM 136

Discrepancies between Odometer Reading and Distance on Performance Summary Report 137

Error 429 During Installation or Trying to Open the Software 138

Error -113 During Installation of Fleet Manager on Eastern OS 139

APCLog.txt File Grows Very Large 142

Noisy FMTerminal Units 144

'Invalid DDR Path Specified' even if it exists 146

No DDR's found, even if they exist 147

Report/Graph Criteria: From Date Greater Than To Date 149

I can't find the FM Upgrade+ Registration Card on the FM2000 CD 154

Administrator Program can't lock Database 157

Daylight Savings Not Updating 158

1112
www.mixtelematics.com

1112
 1113

Can't Upgrade Database After FM2000 Install 162

What's new in CITAS 2010 version 2.20? 163

'Unknown' Error Reported in Fuel Consumption Graph 164

Error -132 during SR1a Install 167

'Method '~'...' when clicking OK/Apply on the Vehicle dialog 168

Initialise Plug, no Vehicles of Type Causes Problems 172

'System Override' Option Enabled for FM100 Event 173

'Unknown Drivers' prints zeroes on Driver Score Report 174

FMServer.exe Access Violation on Driver Scoring Report 175

Modify Fuel Entry results in two entries 176

Cancel Vehicle Form still updates plug, or asks to update plug 177

How To Implement Remote Downloading 178

FMTerminal Event Report always displays 'Unknown Driver' 179

Port settings reset when upgrading with FM2000 180

Error -113 During Installation of Fleet Manager Software 182

Error 3075 Generating Event Report 184

Error 94 while downloading a vehicle plug 186

What's New in FM Kienzle Fleet Manager 2000 187

Scale Incorrect on Fuel Consumption Graph 188

Trips or Events 'On' for Extended Periods of Time 189

Run-time error '3265' when trying to use FM Object Finder Extension 190

Beep and Flash Codes Made EASY 194

Fleet Manager 2000 hangs while loading 195

How to change graph defaults 197

Error 13 when trying to generate Event Report/Activity Timeline 198

1113
www.mixtelematics.com

1113
 1114

Error when attempting to create a new language set 199

Importing FM100 Version 2 database into FM98/FM2000 fails 204

Relay Enabled parameter incorrectly set 206

Unable To Upload Customised FM Terminal Menu Script 208

PC won't shutdown while FMAPC is running 209

FM Kienzle SI No. 382012 - Using the FM200 with the Mercedes Benz PSM-Module (parameterizable special 210
module)

F3 parameter does not accept 'Units' description when added 211

Fleet Manager on Windows ME 212

Error 3075 when generating ANY Report 213

Latest Device Drivers for FM200 and FMTerminal 214

How To Add More Digital Inputs To The FM200 215

FM2000SE extensions not to be installed with previous versions of FM 218

When to use the Event Configuration File (.ecf) 219

Abnormally high duration values on Daily Driver Trip report 220

FMDealer displays no text 221

FMClient hangs after installing FMAPC 224

Reload DDRs after upgrading to FM2000SE 227

Exported Vehicle Configuration Report vs Snapshot version of the report 228

Setting arming delay in Vehicle Configuration Group to less than 1 minute 229

Pulse counter not accepted by software 230

Error when exporting large report 234

Data discrepancies in reports - FM2001 236

Data discrepancies in reports - FM2000 239

Error when uploading FM100 configuration 244

Why do I need to execute the Swap unit functionality 255

1114
www.mixtelematics.com

1114
 1115

Activity Timeline and Trip Report trip data and event data inconsistency 262

Pre Paid functionality in Fleet Manager 283

1115
www.mixtelematics.com

1115
 1116
10.2.7 Fleet Manager 2001

Title KB No.
Software unable to read data from the download module 1
.ECU file cannot be restored 13
Trips with a very short distance show a very high average speed 14
Reports display incorrect ODO reading 15
'Time in Green Band' column should be labeled 'Time out of Green Band' 16
Error when initialising a driver plug 17
Total sum for vehicles in detailed daily trip report is incorrect 19
Incorrect serial number printed on registration card 20
Overflow Error on download if the driver ID is a negative number 21
Changing trip details in the driver activity timeline causes an error 22
Error updating the FM '98 Database 27
Fleet Manager Software procedures for when a FM200(e) Unit is cleared 41
Guidelines for Report Logo Images 42
FM Kienzle Fleet Manager Software with Microsoft Office 2000 61
Latest Device Drivers for FM200 and FMTerminal 214
How To Add More Digital Inputs To The FM200 215
FM2000SE extensions not to be installed with previous versions of FM 218
FMClient hangs after installing FMAPC 224
Exported Vehicle Configuration Report vs Snapshot version of the report 228
Pulse counter not accepted by software 230
Geo-fencing not recording 231
KTCO modes not recorded correctly 232
Error when exporting large report 234
Copy Vehicle Feature duplicates the unit phone number 235
Data discrepancies in reports - FM2001 236
No data recorded with EDM on I1-I4 237
Data discrepancies in reports - FM2000 239
Error 91 when uploading configuration to vehicle plug 240
MSDE Installation 241
Running FM2001 with Microsoft SQL Server 2000 242
Error when uploading FM100 configuration 244
PreProcessFM200Data error while downloading in FM2001SR2 245
Incorrect start time on Event Report 246
Unable to restore backed up database 249
ASP Script Errors in FMOnline 250
Guide to Time synchronisation setup for GSM 251
Reports take very long to generate 252
Why do I need to execute the Swap unit functionality 255
Time-synchronisation issues 256
CallDMI error occurs in GSM Download 260
Activity Timeline and Trip Report trip data and event data inconsistency 262
Changing sim card causes ID verification to fail first time around, Using no PIN 263

1116
www.mixtelematics.com

1116
 1117

FM2002 initialised driver plug does not disarm FM unit 274

Error upgrading FM2001 (SR1/SR2) database to FM2002 282
Pre Paid functionality in Fleet Manager 283
After uninstalling and reinstalling MSDE, I cannot open my existing database or create a new one 284
Error connecting to a DB without permission 293
Reports hanging 343

1117
www.mixtelematics.com

1117
 1118
10.2.8 Fleet Manager 2002 Professional

Title KB No.

FM Kienzle Fleet Manager Software with Microsoft Office 2000 61

How To Create a Plug Dump 67

Incorrect start time on Event Report 246

Why do I need to execute the Swap unit functionality 255

Time-synchronisation issues 256

Configuring Engine hours 257

Problem with negative ID's 258

CallDMI error occurs in GSM Download 260

Long calls to GSM modem connected to FM200 261

Activity Timeline and Trip Report trip data and event data inconsistency 262

Changing sim card causes ID verification to fail first time around, Using no PIN 263

When changing from FMOnline mode the FM Client needs to be restarted 266

GPS Log Viewer buttons and menus are disabled 267

Detailed Trip report hangs for large scope of data 272

How to import Location data 273

FM2002 initialised driver plug does not disarm FM unit 274

Mutliplug aborts in FM2002 Client 276

Not able to connect more than one FM200e device at a time 279

Error upgrading FM2001 (SR1/SR2) database to FM2002 282

Pre Paid functionality in Fleet Manager 283

After uninstalling and reinstalling MSDE, I cannot open my existing database or create a new one 284

Activity timeline details displayed incorrectly 285

Missing Dutch Language Files 287

1118
www.mixtelematics.com

1118
 1119

Using COM ports higher than COM1 to COM4 with the SMS Processor 288

Setting engine hours via GSM 289

FM-Terminal Custom Script Update 291

Reload DDMs after upgrading to FM2002 SR1 292

FM200 Plus Device Driver Upgrade 294

FM200 Plus configuration uploaded to FM200 unit via GSM 297

Driver Scoring Reports displays incorrect data 306

Fleet Manager 2002 SR1 January 2003 release patches and updates 307

Fleet Manager 2002 SR1 Patch 8 309

Client appears to hang when saving tacho graph 318

FM and Siemens MC35i modem 320

Optimising location events 323

Reports hanging 343

How to set up an FM300 unit in the Fleet Manager software prior to FM8.3 352

Issues while upgrading a FM2002 database 372

1119
www.mixtelematics.com

1119
 1120
10.2.9 FM100

Title KB No.

Software unable to read data from the download module 1

When trying to print a report, error 50524 is displayed 3

When trying to print a report, error 50500 is displayed 4

Error 3050 occurs when running the software 5

When downloading data or clicking on the International tab of the Options dialog, error 13: Type Mismatch is 6
displayed

How do I access the information in the system using Access 97? 7

FM Kienzle Fleet Manager 100 Year 2000 compliance (Y2k) 10

FM100 reports do not fit on US Letter paper 29

What's new in Fleet Manager 100 version 1.20 (SR4) 33

16 bit Fleet Software fails to run under Windows 95, 98, or NT 34

16 bit Software - Error executing graph 35

FM Kienzle Fleet Manager Software Year 2000 Compliance (Y2K) 45

What's New in FM Kienzle Fleet Manager 98 version 3.00 (SR1) 46

16 bit Fleet Products on a Network 50

Fleet Manager 98 Timeline Displays Incorrectly (FM100) 53

Fleet Manager 98 Daily Trip Report has no Standing Time (FM100) 54

New Events Not Visible on Timeline 73

Fleet Manager 98/2000 software reports different driving times than FM100 software does. 79

Multiple Drivers Driving one Vehicle 81

Fatal Error when Installing 16 bit Fleet Products under Windows 98 83

FM100 Idle Configuration Incorrect 94

Error 429 On Download when using Win98 SE 106

No Idling or Ignition events recorded 107

1120
www.mixtelematics.com

1120
 1121

What's New in FM Kienzle Fleet Manager 98 SR1a 113

How do I access the information in the system using Access 2000? 118

Incorrect readings from EDM 136

Discrepancies between Odometer Reading and Distance on Performance Summary Report 137

APCLog.txt File Grows Very Large 142

How to Clear the Memory from an FM100 Unit 143

Report/Graph Criteria: From Date Greater Than To Date 149

'Type Mismatch' Error clicking on the International Tab 150

Trip Report or Driving Errors Report Prints Blank or Generates an Error Message 153

Error 50504 when trying to generate a report 156

What's New in FM Kienzle Fleet Manager 98, SR1b 170

Initialise Plug, no Vehicles of Type Causes Problems 172

'System Override' Option Enabled for FM100 Event 173

What's New in FM Kienzle Fleet Manager 2000 187

What's new in Fleet Manager 100 version 2.00 193

Beep and Flash Codes Made EASY 194

FM Kienzle SI No. 381008 - Using the Fleet Manager Software FM100 with Windows 2000 200

FM Kienzle SI No. 381005 - Fleet Manager 100 -- Operation with an external speed signal sender 203

Importing FM100 Version 2 database into FM98/FM2000 fails 204

Runtime error '40052' when accessing vehicle servicing 207

FM Kienzle SI No. 382012 - Using the FM200 with the Mercedes Benz PSM-Module (parameterizable special 210
module)

Error when printing report in FM100 version 2 222

Paper Size Error when printing report 226

What's new in Fleet Manager 100 version 2.50 238

Error when uploading FM100 configuration 244

1121
www.mixtelematics.com

1121
 1122

Tachometer / Speedometer / Rev Counter values not displayed correctly. 259

FM2002 initialised driver plug does not disarm FM unit 274

FMLite Report issue 349

FM 100 device configuration does not reflect buzzer settings 366

1122
www.mixtelematics.com

1122
 1123
10.2.10 FM200

Title KB No.

Software unable to read data from the download module 1

How do I access the information in the system using Access 97? 7

Boolean (digital) events with False parameter settings do not work 23

'Invalid Procedures for Processing Event Type' During FM200 Download 38

Fleet Manager Terminology (FM200(e) Unit) 39

Fleet Manager Software procedure to follow when an FM200(e) unit is swapped 40

Fleet Manager Software procedures for when a FM200(e) Unit is cleared 41

FM Kienzle Fleet Manager Software Year 2000 Compliance (Y2K) 45

What's New in FM Kienzle Fleet Manager 98 version 3.00 (SR1) 46

Tacho data graph shows incorrect Road Speed values 52

Error -214721887 (3022) when downloading 57

Tacho data graph shows zero values for the auxilliary frequency input (F3) 58

Events Utilising the System Override Plug Do Not Work 66

New Events Not Visible on Timeline 73

New Events Not Being Recorded For Vehicle 76

Error 3167 while Downloading 77

Error -2147217887 Executing the Swap Unit Function 78

The FM Kienzle Fleet Manager database is not a valid database file. 80

Multiple Drivers Driving one Vehicle 81

Data for Events defined on one PC not being stored on another 87

Tacho Data Recorded While Vehicle is Stationery 88

The 'Elapsed Time' reported for an Event Occurrance is Incorrect 89

Max RPM Shows Higher than RPM on Tacho Graph 92

1123
www.mixtelematics.com

1123
 1124

Max RPM Shows Lower than RPM on Tacho Graph 93

Error 324 on Download 98

FM200(e) Events appear permanently 'on' in Activity Timeline 104

Idle Occurring Outside of a Trip 105

Error 429 On Download when using Win98 SE 106

No Idling or Ignition events recorded 107

Incorrect Data from Fuel Recorder (EDM) 108

What's New in FM Kienzle Fleet Manager 98 SR1a 113

Events Based on Trip Distance Don't Work 114

EDM Data on Tacho Graph shows zero values 116

How do I access the information in the system using Access 2000? 118

Divide By Zero error occurs on Activity Timeline 119

'Store Average Value' for Events Does Not Work 129

Incorrect readings from EDM 136

Discrepancies between Odometer Reading and Distance on Performance Summary Report 137

Error 429 During Installation or Trying to Open the Software 138

APCLog.txt File Grows Very Large 142

How to Clear the Memory from an FM100 Unit 143

'Invalid DDR Path Specified' even if it exists 146

No DDR's found, even if they exist 147

Report/Graph Criteria: From Date Greater Than To Date 149

Initialise Plug, no Vehicles of Type Causes Problems 172

Cancel Vehicle Form still updates plug, or asks to update plug 177

FMTerminal Event Report always displays 'Unknown Driver' 179

Error 94 while downloading a vehicle plug 186

1124
www.mixtelematics.com

1124
 1125

What's New in FM Kienzle Fleet Manager 2000 187

Trips or Events 'On' for Extended Periods of Time 189

Beep and Flash Codes Made EASY 194

No reports under FM98SR1b 196

How to change graph defaults 197

Error 13 when trying to generate Event Report/Activity Timeline 198

Importing FM100 Version 2 database into FM98/FM2000 fails 204

FM98 SR1b Reports hangs 205

Relay Enabled parameter incorrectly set 206

PC won't shutdown while FMAPC is running 209

FM Kienzle SI No. 382012 - Using the FM200 with the Mercedes Benz PSM-Module (parameterizable special 210
module)

F3 parameter does not accept 'Units' description when added 211

Fleet Manager on Windows ME 212

Error 3075 when generating ANY Report 213

Latest Device Drivers for FM200 and FMTerminal 214

How To Add More Digital Inputs To The FM200 215

Is the FM200 / FM300 Unit Intrinsically Safe? 216

FM2000SE extensions not to be installed with previous versions of FM 218

When to use the Event Configuration File (.ecf) 219

Abnormally high duration values on Daily Driver Trip report 220

FMDealer displays no text 221

FMClient hangs after installing FMAPC 224

Reload DDRs after upgrading to FM2000SE 227

Exported Vehicle Configuration Report vs Snapshot version of the report 228

Setting arming delay in Vehicle Configuration Group to less than 1 minute 229

1125
www.mixtelematics.com

1125
 1126

Pulse counter not accepted by software 230

Geo-fencing not recording 231

KTCO modes not recorded correctly 232

Error when exporting large report 234

Copy Vehicle Feature duplicates the unit phone number 235

Data discrepancies in reports - FM2001 236

No data recorded with EDM on I1-I4 237

Data discrepancies in reports - FM2000 239

Error 91 when uploading configuration to vehicle plug 240

PreProcessFM200Data error while downloading in FM2001SR2 245

Incorrect start time on Event Report 246

EDM Data not Recorded when Connected to Analogue Lines. 247

Calculation of Fuel Consumption in the FM software 248

Unable to restore backed up database 249

Guide to Time synchronisation setup for GSM 251

42V Trucks and FM200 voltage 253

Why do I need to execute the Swap unit functionality 255

Tachometer / Speedometer / Rev Counter values not displayed correctly. 259

Long calls to GSM modem connected to FM200 261

Changing sim card causes ID verification to fail first time around, Using no PIN 263

How to recover a TrailerID's lost ID 264

TCO diagnostics 269

Things to take into account when connecting speed line 270

FM2002 initialised driver plug does not disarm FM unit 274

FM200 loses its Calibration, Odometer, or Vehicle ID 277

1126
www.mixtelematics.com

1126
 1127

Recommended GPS installation 278

Nokia 6090 issues 280

Pre Paid functionality in Fleet Manager 283

Power management with the FM200PLUS unit and its positive drive 290

Reload DDMs after upgrading to FM2002 SR1 292

FM200 Plus Device Driver Upgrade 294

Data download stops at processing phase 295

TCO 1319 & ELVIST 296

FM200 Plus configuration uploaded to FM200 unit via GSM 297

Downloaded data not showing in database 299

Connecting devices to the FM200 Plus Serial cable 304

Pulse count incorrect on F4 308

Fleet Manager 2002 SR1 Patch 8 309

F4/I8 input on the FM200 Plus unit 312

HOW TO correct a date jump on an FM unit 313

FM200 Plus calibration & GPS 315

Interval data on the FM200 and FM200 Plus 317

FM and Siemens MC35i modem 320

FM unit current consumption 321

Fleet Manager Trailer ID Odometer 327

FM 200 Communicator and GSM data download 329

Controlling device power by Relay 330

Using GPS Velocity as speed 334

What's New in FM Dealer Utility (version number 2.11.2.0) 335

How to connect and setup a Pocket PC 344

1127
www.mixtelematics.com

1127
 1128

Setting up GPS velocity as speed on GARMIN GPS 345

Forcing device driver upload via GPRS/GSM 347

How to set up an FM300 unit in the Fleet Manager software prior to FM8.3 352

Setting up WiFi 353

FleetManager Professional 8.31 update 1 355

Specific Absorption Rate of Fleet Manager Products 361

Digital Hands Free Kit 362

FM Locator GPS issue 367

How to enable WiFi Diagnostic information on the FM Terminal 376

Spurious speed pulses when using Hunter CAN Bus 387

Back-up battery Information 389

1128
www.mixtelematics.com

1128
 1129

10.3 Offline Knowledge Base Articles

10.3.1 Knowledge Base Article 1

Article Number 1

Title Software unable to read data from the download module

Created 11/19/1998 4:37:02 PM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 1/29/2003 9:38:53 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Shurlok EV100, all versions

· CI Data, all versions

· FM Kienzle Fleet Manager 100, all versions

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

· Fleet Manager 2001, all versions

· Fleet Manager 2002, all versions

----- SUMMARY -----

Some customers have experienced difficulty downloading data via the download module with the
above products. This article describes a number of common causes of and solutions to such
problems.

----- CAUSE -----

The following are common causes of problems accessing the download module:

1. Download module unplugged.

2. Code-plug not inserted correctly or not making contact with connecters in the download module
socket.

3. Software set to use incorrect parallel port.

4. Software running on Microsoft Windows NT and you are using a version of the FM98 software
prior to Service Release 1, or a version of the FM100 software prior to Service Release 4, or any
of the other above products.

5. Parallel port configured as an ECP, EPP or bi-directional port.

1129
www.mixtelematics.com

1129
 1130

Note: This does not apply if you are using SR1 or greater of the Fleet Manager 98 software, or SR4
or greater of the Fleet Manager 100 software, and the software is configured to run on Microsoft
Windows NT or Microsoft Windows 98.

6. Parallel port faulty.

7. The cable connecting your download module to your PC is damaged, or the download module
itself is damaged.

8. You have created a shortcut to the software product in question, but have neglected to modify the
"Start In" directory of the shortcut.

----- SOLUTION -----

If you believe that your experience is due to one of the above reasons, then please follow the
corresponding step, below, to attempt to rectify the problem.

1. Ensure that the download module is correctly connected to a parallel port on the personal
computer.

2. Inspect the connectors in the download module socket as these may be bent. Ensure that the
code-plug is inserted firmly into the download module.

3. Ensure that the software is configured to use the appropriate parallel port. The software uses
LPT1 by default.

4. The current version of download module software (Except for when using FM98 Service Release
1 or higher, or FM100 Service Release 4 or higher) does not function on Microsoft Windows NT.

5. Check the BIOS settings of your personal computer to ensure that the parallel port is configured
as a uni-directional printer port. The current version of download module software does not
support ECP, EPP or bi-directional parallel ports.

If your personal computer is incapable of being configured to use a uni-directional parallel port
(such as SPP), then you should consider upgrading to Microsoft Windows NT 4.0 or Microsoft
Windows 98, or contact your computer supplier, to obtain a computer that does support this
standard.

Note: This does not apply if you are using SR1 or greater of the Fleet Manager 98 software, or SR4
or greater of the Fleet Manager 100 software, and the software is configured to run on Microsoft
Windows NT.

6. Test that the parallel port functions correctly with other devices such as a printer.

7. Contact your distributor, in order to aquire a new download module.

8. Ensure that, if you have manually created a shortcut to the software product, that you modify that
shortcut's "Start In" location to be the correct path to the software.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM200 FM98 FM2000 EV100 CIDATA FM2001

1130
www.mixtelematics.com

1130
 1131
10.3.2 Knowledge Base Article 2

Article Number 2

Title Shurlok EV100 Year 2000 compliance (Y2k)

Created 11/19/1998 1:59:01 PM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:45:14 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Shurlok EV100

----- SUMMARY -----

The Shurlok EV100 system (including hardware and software) has been tested, and found to
function correctly under the conditions listed below, when EV100 application software version
1.6 (Service Release 2) or higher is used. The latest version of EV100 software can be
downloaded from the EV100 FTP Download site.

---- UNIT ----

The EV100 unit records dates in a proprietary compressed format. To conserve storage space
within the unit, the century is not recorded with dates. The unit firmware is designed to
accommodate the millennium rollover and applies the following rules to deal with dates well into
the twenty-first century. Dates with a year of 70 or greater are considered to be from the
twentieth century i.e. dates ranging from 01/01/70 to 31/12/99 inclusive are considered to be
01/01/1970 to 31/12/1999 inclusive. Dates with a year of 69 or less are considered to be from
the twenty first century i.e. dates ranging from 01/01/00 to 31/12/69 inclusive are considered to
be 01/01/2000 to 31/12/2069 inclusive.

---- SOFTWARE ----

The EV100 application software applies the rules documented above to convert dates received
from the EV100 units as well as dates with two digit years entered via the software interface. All
dates are converted into fully qualified dates before being stored in the EV100 database.

The following areas of the EV100 application software are affected by dates and have been
tested to ensure they function correctly:

· The Daylight Savings fields on the International tab of the Options dialog.

· The Set Date/Time function accessed from the Code Plug menu.

· The report and graph selection criteria dialogs.

· The Fuel Usage maintenance window.

· The Registration Wizard.

---- TESTS CONDUCTED ----

1131
www.mixtelematics.com

1131
 1132

Several tests have been conducted to ensure that the entire system will function correctly into
the twenty-first century. An EV100 unit was connected to a trip simulator. The unit’s real-time
clock was set forward as required for each test and several simulated trips were done. All data
was downloaded into the EV100 software and the database and system outputs were checked
for validity. A year 2000 compliant personal computer was used to conduct all tests and the
personal computer’s real-time clock was set forward as required for each test.

A test results pack can be downloaded from ftp://ftp.centre-point.com/KBase/

EV100_Y2k_Test_Results.zip. This 55kb .ZIP file contains the EV100 test database (EV100.
MDB) and a collection of comma separated value (.CSV) files.

Dates with a two-digit year

All functions within the application software were tested to ensure that two-digit years are
converted and stored in the database correctly. Dates outside of the valid system date range
documented above (01/01/1970 to 31/12/2069 inclusive) are rejected by the software and may
not be entered.

The 31st of December 1999 (31/12/1999)

All functions within the system were tested to ensure that the rollover to the 1st January 2000 is
handled correctly.

The 29th of February 2000 (29/02/2000)

Many people are not aware that the year 2000 is a leap year. This is the case and all system
functions were tested to ensure that this date is considered valid and is handled correctly.

The 30th of April 2000 (30/04/2000)

This will be the first month of the year 2000 ending on a weekend. All system functions were
tested to ensure that this is handled correctly.

The 10th of October 2000 (10/10/2000)

On systems where dates are entered in the format “MMDDYY”, this would be the first 6-digit date
that could cause a problem (101000). All system functions were tested to ensure that this date is
handled correctly.

The 31st of December 2000 (31/12/2000)

This will be the last day of the year 2000. All system functions were tested to ensure that the
rollover to 1st January 2001 is handled correctly.

The 29th of February 2001 (29/02/2001)

Many people are under the impression that the year 2001 is a leap year. This is not the case and
all system functions were tested to ensure that this date is not considered valid.

The 31st of December 2001 (31/12/2001)

This will be the last day of the year 2001, the end of the second year after the turn of the
century. All system functions were tested to ensure that the rollover to 1st January 2002 is
handled correctly.

------------------------------------------------------------------------------

KEYWORDS: EV100

1132
www.mixtelematics.com

1132
 1133
10.3.3 Knowledge Base Article 3

Article Number 3

Title When trying to print a report, error 50524 is displayed

Created 10/26/1998 10:51:16 AM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 8/2/1999 12:13:56 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· Shurlok EV100, all versions

· CI Data, all versions

· FM Kienzle Fleet Manager 100, all versions

· CITAS 2010, all versions

----- SUMMARY -----

Some customers have experienced this problem when generating a report with one of the above
products.

----- MORE INFORMATION -----

The above products make use of the Crystal Reports print engine to generate and preview reports.

----- CAUSE -----

The Crystal Reports print engine makes use of a DLL file called CRPE.DLL. This DLL may be
overwritten with an older, incompatible version when other software packages which make use of the
Crystal Reports engine are installed.

----- SOLUTION -----

Re-install our product. If this does not solve the problem, try copying the CRPE.DLL file from our
installation set over the incompatible one on your personal computer's hard disk.

Some third-party applications have been known to alter the DOS path causing the system to make
use of an incompatible version of the CRPE.DLL located in another directory. You should search
your hard disk to determine whether more than one copy of this file exists.

------------------------------------------------------------------------------

KEYWORDS: FM100 EV100 CIDATA CITAS 2010

1133
www.mixtelematics.com

1133
 1134
10.3.4 Knowledge Base Article 4

Article Number 4

Title When trying to print a report, error 50500 is displayed

Created 10/26/1998 10:51:43 AM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 8/2/1999 12:14:02 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· Shurlok EV100, all versions

· CI Data, all versions

· FM Kienzle Fleet Manager 100, all versions

· CITAS 2010, all versions

----- SUMMARY -----

Some customers have experienced this problem when generating a report with one of the above
products.

----- MORE INFORMATION -----

The above products make use of the Crystal Reports print engine to generate and preview
reports.

----- CAUSE -----

The Crystal Reports print engine uses report immage (.RPT) files to format report output. Error
50500 indicates that the .RPT file required for the generation of the report you are requesting is
invalid or corrupted.

----- SOLUTION -----

Try copying the *.RPT files from our installation set over the corrupted ones on your personal
computer's hard disk. If this does not solve the problem, re-install our product.

------------------------------------------------------------------------------

KEYWORDS: FM100 EV100 CIDATA CITAS 2010

1134
www.mixtelematics.com

1134
 1135
10.3.5 Knowledge Base Article 5

Article Number 5

Title Error 3050 occurs when running the software

Created 10/26/1998 10:52:06 AM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 8/2/1999 12:14:08 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· Shurlok EV100, all versions

· CI Data, all versions

· FM Kienzle Fleet Manager 100, all versions

· CITAS 2010, all versions

----- SUMMARY -----

Some customers have experienced this problem when running one of the above applications. This
error is common when the software is being run on Microsoft Windows 3.1.

----- CAUSE -----

Error 3050 occurs when the software is unable to lock the database. This usually occurs when the
DOS sharing utility (SHARE.EXE) is not loaded or is loaded with incorrect parameters.

----- SOLUTION -----

If you are using a version of Windows that is prior to Windows 3.11, then check your CONFIG.SYS
file to ensure that the DOS sharing utility is being loaded and that "L" (locks) parameter is being
used as follows:

DEVICE=C:\DOS\SHARE.EXE /F:2048 /L:100

------------------------------------------------------------------------------

KEYWORDS: FM100 EV100 CIDATA CITAS 2010

1135
www.mixtelematics.com

1135
 1136
10.3.6 Knowledge Base Article 6

Article Number 6

When downloading data or clicking on the International tab of the Options dialog,
Title
error 13: Type Mismatch is displayed

Created 10/26/1998 10:53:21 AM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:43:41 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO -----

· FM Kienzle Fleet Manager 100, all versions

----- SUMMARY -----

"Unexpected Error 13: Type Mismatch" occurs when downloading trip data from a vehicle plug
and/or when selecting the International tab on the Options dialog.

----- MORE INFORMATION -----

This problem occurs when the following conditions are true:

1. Daylight Saving has been enabled using the International tab on the Options dialog of the Fleet
Manager 100 software.

AND

2. An invalid system date or system time format has been specified using the Regional Settings
applet (Microsoft Windows 95, 98, or NT) or International applet (Microsoft Windows 3.1, 3.11, or
3.11 for Workgroups) in Control Panel. An example of an invalid system date format is dd.mm.yy.
(which contains a trailing period). The equivalent valid date format would be dd.mm.yy (without
the trailing period).

AND/OR

3. The system date and system time format use the same separator character. The separator
character for date and time must be different so that Windows is able to differentiate dates and
times.

----- CAUSE -----

This error occurs when invalid date and/or time formats have been configured in Control Panel.

----- SOLUTION -----

On the PC where the problem is occurring:

1. Make sure that the system date and time formats are valid using the Regional Settings applet
(Windows 95) or International applet (Windows 3.x) in Control Panel.

1136
www.mixtelematics.com

1136
 1137

2. Make sure that the system date and time formats DO NOT use the same separator character.

3. Run the FM100 application.

4. Backup the FM100 database file using the Backup option on the File menu.

5. Close the FM100 application.

6. Upgrade to the latest version of the Fleet Manager Lite software (you can download this from
the www.omnibridge.com website.

7. Run the FM100 application.

8. Reconfigure the daylight saving settings using the International tab on the Options dialog of the
Fleet Manager 100 application.

------------------------------------------------------------------------------

KEYWORDS: FM100

1137
www.mixtelematics.com

1137
 1138
10.3.7 Knowledge Base Article 7

Article Number 7

Title How do I access the information in the system using Access 97?

Created 11/19/1998 4:38:36 PM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 11:57:25 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

· Shurlok EV100, all versions

· CI Data, all versions

· FM Kienzle Fleet Manager 100, all versions

· CITAS 2010, all versions

----- SUMMARY -----

Many customers would like to develop their own applications which utilise the information stored in
the above products' databases.

----- MORE INFORMATION -----

All of the above products use a Microsoft Jet database to store information. You can use any
application capable of accessing Jet databases to retrieve information from the databases. In order
to ensure the integrity of the information, these databases are read-only. Updating records is not
permitted.

The FM Kienzle Fleet Manager application utilises a Jet 3.5 database (.MDB file) named FMServer.
MDB. You can open this databases directly using any Jet 3.5 compatible application such as
Microsoft Access 97.

The Shurlok EV100, CI Data, FM Kienzle Fleet Manager 100 and CITAS 2010 applications are 16-
bit applications and utilise a 16-bit Jet 2.5 database (.MDB files) named EV100.MDB, CIDATA.
MDB, FM100.MDB and CITAS.MDB respectively. You can open these databases directly using any
Jet 2.5 compatible application such as Microsoft Access 2.0.

These 16-bit databases cannot be opened directly using Microsoft Access 97 because they must
be first be upgraded. Once upgraded, they are no longer accessible to 16-bit applications.

----- SOLUTION -----

You can utilise the data in the 16-bit Jet 2.5 databases without upgrading them by creating a new
empty Jet 3.5 database using Access 97 and linking the Jet 2.5 database tables into it.

1138
www.mixtelematics.com

1138
 1139

Access 97 help contains instructions on how to link tables. This is a very simple procedure which
consists of the following basic steps:

1. Click on the "File" menu then select "Get External Data" then select "Link Tables".

2. The standard "File Open" dialog is displayed. Browse for the Jet 2.5 database file.

3. A list of tables is displayed. Select the tables you wish to link (or click "Select All").

4. Click the OK button.

5. The tables are linked into the empty Jet 3.5 database. Linked tables have an arrow icon
differentiating them from other tables in the database.

You can open any of the linked tables and create queries, reports etc. using them.

Linked tables are read-only (just like the original tables in the underlying 16-bit database) and
cannot be updated.

Linked tables are "links" to the original tables so that changes in the original tables are reflected
real-time in the linked tables.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM200 FM98 FM2000 EV100 CIDATA CITAS 2010

1139
www.mixtelematics.com

1139
 1140
10.3.8 Knowledge Base Article 8

Article Number 8

Title CITAS 2010 Year 2000 compliance (Y2k)

Created 11/19/1998 2:08:06 PM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:41:34 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· CITAS 2010

----- SUMMARY -----

The CITAS 2010 system (including hardware and software) has been tested, and found to function
correctly under the conditions listed below, when CITAS 2010 application software version 2.00 or
higher is used.

It should also be noted that, since the CITAS 2010 Unit is a re-programmable unit, the latest .bin
files from the CITAS 2010 2.00 installation set (or higher) should be uploaded into all the CITAS
2010 vehicles in your organisation.

The latest version of CITAS 2010 software can be downloaded from the CITAS2010 FTP Download
site.

----- UNIT -----

The CITAS 2010 unit records dates in a proprietary compressed format. To conserve storage space
within the unit, the century is not recorded with dates. The unit firmware is designed to
accommodate the millennium rollover and applies the following rules to deal with dates well into the
twenty-first century. Dates with a year of 28 or greater are considered to be from the twentieth
century i.e. dates ranging from 01/01/28 to 31/12/99 inclusive are considered to be 01/01/1928 to
31/12/1999 inclusive. Dates with a year of 27 or less are considered to be from the twenty first
century i.e. dates ranging from 01/01/00 to 31/12/27 inclusive are considered to be 01/01/2000 to
31/12/2027 inclusive.

----- SOFTWARE -----

The CITAS 2010 application software applies the rules documented above to convert dates received
from the CITAS 2010 units as well as dates with two digit years entered via the software interface.
All dates are converted into fully qualified dates before being stored in the CITAS 2010 database.

The following areas of the CITAS application software are affected by dates and have been tested to
ensure they function correctly:

· The report and graph selection criteria dialogs.

· The Set Date/Time function accessed from the Code Plug menu.

· The “Date Installed” field, available from the Vehicles form.

1140
www.mixtelematics.com

1140
 1141

· The export criteria dialogs.

----- TESTS CONDUCTED -----

Several tests have been conducted to ensure that the entire system will function correctly into the
twenty-first century. A CITAS 2010 unit was connected to a trip simulator. The unit’s real-time clock
was set forward as required for each test and several simulated trips were done. All data was
downloaded into the CITAS 2010 software and the database and system outputs were checked for
validity. A year 2000 compliant personal computer was used to conduct all tests and the personal
computer’s real-time clock was set forward as required for each test.

A test results pack can be downloaded from ftp://ftp.centre-point.com/KBase/

CITAS_2010_Y2k_Test_Results.zip. This 351kb .ZIP file contains the CITAS 2010 test database
(CITAS.MDB) and a collection of comma separated values (.CSV) and graph bitmap (.BMP) files
exported from the CITAS 2010 software.

Dates with a two-digit year

All functions within the application software were tested to ensure that two-digit years are converted
and stored in the database correctly. Dates outside of the valid system date range documented
above (01/01/1970 to 31/12/2069 inclusive) are rejected by the software and may not be entered.

The 31st of December 1998 (31/12/1998)

The system was fully tested to ensure that the rollover from this year into next year is handled
correctly.

The 28th of February 1999 (28/02/1999)

A leap year in the twentieth century was tested, to ensure that the system functions correctly.

The 31st of August 1999 (31/08/1999)

The rollover from 31/8/99 to 1/9/99 was tested, to ensure that this date causes no problems.

The 31st of December 1999 (31/12/1999)

All functions within the system were tested to ensure that the rollover to the 1st January 2000 is
handled correctly.

The 29th of February 2000 (29/02/2000)

Many people are not aware that the year 2000 is a leap year. This is the case and all system
functions were tested to ensure that this date is considered valid and is handled correctly.

The 30th of April 2000 (30/04/2000)

This will be the first month of the year 2000 ending on a weekend. All system functions were tested
to ensure that this is handled correctly.

The 10th of October 2000 (10/10/2000)

On systems where dates are entered in the format “MMDDYY”, this would be the first 6-digit date
that could cause a problem (101000). All system functions were tested to ensure that this date is
handled correctly.

The 31st of December 2000 (31/12/2000)

This will be the last day of the year 2000. All system functions were tested to ensure that the rollover

1141
www.mixtelematics.com

1141
 1142

to 1st January 2001 is handled correctly.

The 29th of February 2001 (29/02/2001)

Many people are under the impression that the year 2001 is a leap year. This is not the case and all
system functions were tested to ensure that this date is not considered valid.

The 31st of December 2001 (31/12/2001)

This will be the last day of the year 2001, the end of the second year after the turn of the century. All
system functions were tested to ensure that the rollover to 1st January 2002 is handled correctly.

The 29th of February 2004 (29/02/2004)

The system was tested to ensure that it correctly interprets the year 2004 as a leap year.

------------------------------------------------------------------------------

KEYWORDS: CITAS 2010

1142
www.mixtelematics.com

1142
 1143
10.3.9 Knowledge Base Article 9

Article Number 9

Title CI Data Year 2000 compliance (Y2k)

Created 11/23/1998 11:17:53 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:40:39 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· CI Data

----- SUMMARY -----

The CI Data system (including hardware and software) has been tested, and found to function
correctly under the conditions listed below, when CI Data application software 1.50 (Service Release
1)or higher is used. The latest version of CI Data software can be downloaded from the CI Data FTP
Download site.

----- UNIT -----

The CI Data unit records dates in a proprietary compressed format. To conserve storage space
within the unit, the century is not recorded with dates. The unit firmware is designed to
accommodate the millennium rollover and applies the following rules to deal with dates well into the
twenty-first century. Dates with a year of 70 or greater are considered to be from the twentieth
century i.e. dates ranging from 01/01/70 to 31/12/99 inclusive are considered to be 01/01/1970 to
31/12/1999 inclusive. Dates with a year of 69 or less are considered to be from the twenty first
century i.e. dates ranging from 01/01/00 to 31/12/69 inclusive are considered to be 01/01/2000 to
31/12/2069 inclusive.

---- SOFTWARE -----

The CI Data application software applies the rules documented above to convert dates received
from the CI Data units as well as dates with two digit years entered via the software interface. All
dates are converted into fully qualified dates before being stored in the CI Data database.

The following areas of the CI Data application software are affected by dates and have been tested
to ensure they function correctly:

· The Daylight Savings fields on the International tab of the Options dialog.

· The Set Date/Time function accessed from the Code Plug menu.

· The report and graph selection criteria dialogs.

· The Fuel Usage maintenance window.

· The Registration Wizard.

· The export criteria dialog.

1143
www.mixtelematics.com

1143
 1144

----- TESTS CONDUCTED -----

Several tests have been conducted to ensure that the entire system will function correctly into the
twenty-first century. A CI Data unit was connected to a trip simulator. The unit’s real-time clock was
set forward as required for each test and several simulated trips were done. All data was
downloaded into the CI Data software and the database and system outputs were checked for
validity. A year 2000 compliant personal computer was used to conduct all tests and the personal
computer’s real-time clock was set forward as required for each test.

A test results pack can be downloaded from ftp://ftp.centre-point.com/KBase/

CI_Data_Y2k_Test_Results.zip. This 61kb .ZIP file contains the CI Data test database (CIDATA.
MDB) and a collection of comma separated values (.CSV) files exported from the CI Data software.

Dates with a two-digit year

All functions within the application software were tested to ensure that two-digit years are converted
and stored in the database correctly. Dates outside of the valid system date range documented
above (01/01/1970 to 31/12/2069 inclusive) are rejected by the software and may not be entered.

The 31st of December 1998 (31/12/1998)

The system was fully tested to ensure that the rollover from this year into next year is handled
correctly.

The 28th of February 1999 (28/02/1999)

The last non-leap year in the twentieth century was tested, to ensure that the system functions
correctly.

The 31st of August 1999 (31/08/1999)

The rollover from 31/8/99 to 1/9/99 was tested, to ensure that this date causes no problems.

The 31st of December 1999 (31/12/1999)

All functions within the system were tested to ensure that the rollover to the 1st January 2000 is
handled correctly.

The 29th of February 2000 (29/02/2000)

Many people are not aware that the year 2000 is a leap year. This is the case and all system
functions were tested to ensure that this date is considered valid and is handled correctly.

The 30th of April 2000 (30/04/2000)

This will be the first month of the year 2000 ending on a weekend. All system functions were tested
to ensure that this is handled correctly.

The 10th of October 2000 (10/10/2000)

On systems where dates are entered in the format “MMDDYY”, this would be the first 6-digit date
that could cause a problem (101000). All system functions were tested to ensure that this date is
handled correctly.

The 31st of December 2000 (31/12/2000)

This will be the last day of the year 2000. All system functions were tested to ensure that the rollover
to 1st January 2001 is handled correctly.

1144
www.mixtelematics.com

1144
 1145

The 29th of February 2001 (29/02/2001)

Many people are under the impression that the year 2001 is a leap year. This is not the case and all
system functions were tested to ensure that this date is not considered valid.

The 31st of December 2001 (31/12/2001)

This will be the last day of the year 2001, the end of the second year after the turn of the century. All
system functions were tested to ensure that the rollover to 1st January 2002 is handled correctly.

The 29th of February 2004 (29/02/2004)

The system was tested to ensure that it correctly interprets the year 2004 as a leap year.

------------------------------------------------------------------------------

KEYWORDS: CIDATA

1145
www.mixtelematics.com

1145
 1146
10.3.10 Knowledge Base Article 10

Article Number 10

Title FM Kienzle Fleet Manager 100 Year 2000 compliance (Y2k)

Created 11/23/1998 11:19:05 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:38:49 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 100

----- SUMMARY -----

The FM100 system (including hardware and software) has been tested, and found to function
correctly under the conditions listed below, when FM100 application software version 1.20
(Service Release 4) or higher is used. The latest version of FM100 software can be downloaded
from the CI Development web site at http://www.mixtelematics.com

----- UNIT -----

The FM100 unit records dates in a proprietary compressed format. To conserve storage space
within the unit, the century is not recorded with dates. The unit firmware is designed to
accommodate the millennium rollover and applies the following rules to deal with dates well into
the twenty-first century. Dates with a year of 70 or greater are considered to be from the twentieth
century i.e. dates ranging from 01/01/70 to 31/12/99 inclusive are considered to be 01/01/1970 to
31/12/1999 inclusive. Dates with a year of 69 or less are considered to be from the twenty first
century i.e. dates ranging from 01/01/00 to 31/12/69 inclusive are considered to be 01/01/2000 to
31/12/2069 inclusive.

----- SOFTWARE -----

The FM100 application software applies the rules documented above to convert dates received
from the FM100 units as well as dates with two digit years entered via the software interface. All
dates are converted into fully qualified dates before being stored in the FM100 database.

The following areas of the FM100 application software are affected by dates and have been tested
to ensure they function correctly:

· The Daylight Savings fields on the International tab of the Options dialog.

· The Set Date/Time function accessed from the Code Plug menu.

· The report and graph selection criteria dialogs.

· The Fuel Usage maintenance window.

· The Registration Wizard.

· The export criteria dialogs.

1146
www.mixtelematics.com

1146
 1147

----- TESTS CONDUCTED -----

Several tests have been conducted to ensure that the entire system will function correctly into the
twenty-first century. An FM100 unit was connected to a trip simulator. The unit’s real-time clock
was set forward as required for each test and several simulated trips were done. All data was
downloaded into the FM100 software and the database and system outputs were checked for
validity. A year 2000 compliant personal computer was used to conduct all tests and the personal
computer’s real-time clock was set forward as required for each test.

A test results pack can be downloaded from ftp://ftp.centre-point.com/KBase/

FM100_Y2k_Test_Results.zip. This 75kb .ZIP file contains the FM100 test database (FM100.
MDB) and a collection of comma separated values (.CSV) files exported from the FM100 software.

Dates with a two-digit year

All functions within the application software were tested to ensure that two-digit years are
converted and stored in the database correctly. Dates outside of the valid system date range
documented above (01/01/1970 to 31/12/2069 inclusive) are rejected by the software and may not
be entered.

The 31st of December 1999 (31/12/1999)

All functions within the system were tested to ensure that the rollover to the 1st January 2000 is
handled correctly.

The 29th of February 2000 (29/02/2000)

Many people are not aware that the year 2000 is a leap year. This is the case and all system
functions were tested to ensure that this date is considered valid and is handled correctly.

The 30th of April 2000 (30/04/2000)

This will be the first month of the year 2000 ending on a weekend. All system functions were
tested to ensure that this is handled correctly.

The 10th of October 2000 (10/10/2000)

On systems where dates are entered in the format “MMDDYY”, this would be the first 6-digit date
that could cause a problem (101000). All system functions were tested to ensure that this date is
handled correctly.

The 31st of December 2000 (31/12/2000)

This will be the last day of the year 2000. All system functions were tested to ensure that the
rollover to 1st January 2001 is handled correctly.

The 29th of February 2001 (29/02/2001)

Many people are under the impression that the year 2001 is a leap year. This is not the case and
all system functions were tested to ensure that this date is not considered valid.

The 31st of December 2001 (31/12/2001)

This will be the last day of the year 2001, the end of the second year after the turn of the century.
All system functions were tested to ensure that the rollover to 1st January 2002 is handled
correctly.

------------------------------------------------------------------------------

1147
www.mixtelematics.com

1147
 1148

KEYWORDS: FM100

1148
www.mixtelematics.com

1148
 1149
10.3.11 Knowledge Base Article 11

Article Number 11

CTL3D32.DLL incorrect version on Windows 95 with Novell Netware Client Shell

Title
installed

Created 11/19/1998 4:39:14 PM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 12:27:46 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

After installing the FM Kienzle Fleet Manager software on a Windows 95 personal computer with
the Novell Netware Client Shell installed, the following error message may be displayed each time
Windows starts up:

"This application uses CTL3D32.DLL which is not the correct version. This version of CTL3D32.
DLL is designed only for Windows NT systems."

----- CAUSE -----

The Fleet Manager software installs a version of the CTL3D32.DLL file which is incompatible with
the Novell Netware Client Shell.

----- SOLUTION -----

1. Rename the copy of CTL3D32.DLL installed by the Fleet Manager installation set.

2. Re-install the Novell Netware Client Shell.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1149
www.mixtelematics.com

1149
 1150
10.3.12 Knowledge Base Article 12

Article Number 12

Title The default backup reminder period of one day cannot be changed

Created 11/23/1998 11:20:59 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:49:30 PM

Last Modified By Tony Gois (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

The default backup reminder period of one day cannot be changed in the Options pane of the Fleet
Manager 98 Administrator utility.

----- CAUSE -----

This is caused by an error in the Administrator utility.

----- SOLUTION -----

Download the Fleet Manager 98 Update from ftp://ftp.centre-point.com/KBase/FM98_SR0.zip. This

is a 1683kb file.

For more information on the Fleet Manager 98 update, please search for "FM98" and "Update".

----- STATUS -----

This problem has been solved with Service Release 1 of the Fleet Manager 98 Software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1150
www.mixtelematics.com

1150
 1151
10.3.13 Knowledge Base Article 13

Article Number 13

Title .ECU file cannot be restored

Created 11/23/1998 11:21:55 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:37:33 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

The .ECU files that are created by the backup facility of the Fleet Manager 98 Administrator utility
cannot be restored using the FMEventRestore.EXE unsupported utility.

----- CAUSE -----

This is caused by errors in the FMEventRestore and Administrator utilities.

----- SOLUTION -----

Upgrade your system to the latest version of the Fleet Manager software (FM Fleet Manager
FM2001 SR2 or later).

For more information on the Fleet Manager 98 update, please search for "FM98" and "Update".

----- STATUS -----

This problem has been solved with Service Release 1 of the Fleet Manager 98 Software. It should
also be noted that, in FM98-SR1, the .ECU file is obsolete, and has been replaced with the .ECF
file.

------------------------------------------------------------------------------

KEYWORDS: FM98

1151
www.mixtelematics.com

1151
 1152
10.3.14 Knowledge Base Article 14

Article Number 14

Title Trips with a very short distance show a very high average speed

Created 11/23/1998 11:23:04 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:37:18 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

On the detailed trip reports, trips with a very short distance sometimes show a very high average
speed.

----- CAUSE -----

This is caused by an error in the report engine.

----- SOLUTION -----

Upgrade your system to the latest version of the Fleet Manager software (FM Fleet Manager FM2001
SR2 or later).

For more information on the Fleet Manager 98 update, please search for "FM98" and "Update".

----- STATUS -----

This problem has been solved with Service Release 1 of the Fleet Manager 98 Software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1152
www.mixtelematics.com

1152
 1153
10.3.15 Knowledge Base Article 15

Article Number 15

Title Reports display incorrect ODO reading

Created 11/23/1998 11:23:58 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:37:06 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

The vehicle performance summary reports display the largest odometer reading for the vehicle
instead of the latest odometer reading. These two readings may not be the same if the "Set
Odometer" function of the Fleet Manager 98 software has been used to change the odometer
reading stored in the vehicle's unit.

----- CAUSE -----

This is caused by errors in the report engine.

----- SOLUTION -----

Upgrade your system to the latest version of the Fleet Manager software (FM Fleet Manager
FM2001 SR2 or later).

For more information on the Fleet Manager 98 update, please search for "FM98" and "Update".

----- STATUS -----

This problem has been solved with Service Release 1 of the Fleet Manager 98 Software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1153
www.mixtelematics.com

1153
 1154
10.3.16 Knowledge Base Article 16

Article Number 16

Title 'Time in Green Band' column should be labeled 'Time out of Green Band'

Created 11/23/1998 11:25:08 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:36:54 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

The "Time in Green Band" column on the driving errors reports should be labelled "Out of Green
Band".

----- SOLUTION -----

Upgrade your system to the latest version of the Fleet Manager software (FM Fleet Manager
FM2001 SR2 or later).

For more information on the Fleet Manager 98 update, please search for "FM98" and "Update".

----- STATUS -----

This problem has been solved with Service Release 1 of the Fleet Manager 98 Software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1154
www.mixtelematics.com

1154
 1155
10.3.17 Knowledge Base Article 17

Article Number 17

Title Error when initialising a driver plug

Created 11/23/1998 11:32:27 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:36:26 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

If a driver is granted access to more than 30 vehicles, an error occurs when initialising the driver
plug.

----- CAUSE -----

This is caused by errors in the vehicle/driver access validation in the software.

----- SOLUTION -----

Upgrade your system to the latest version of the Fleet Manager software (FM Fleet Manager
FM2001 SR2 or later).

For more information on the Fleet Manager 98 update, please search for "FM98" and "Update".

----- STATUS -----

This problem has been solved with Service Release 1 of the Fleet Manager 98 Software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1155
www.mixtelematics.com

1155
 1156
10.3.18 Knowledge Base Article 18

Article Number 18

Title Windows dealer utility reports incorrect date and time on driver plug.

Created 11/23/1998 11:37:24 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 9/21/1999 1:49:29 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

When a blue driver plug is initialised to set the date and time using the windows dealer utility, the
plug (and unit) is initialised correctly but when the dealer utility reads the date back off the plug, it is
displayed incorrectly.

----- CAUSE -----

This is caused by errors in the windows dealer utility.

----- STATUS -----

This problem has been solved with the FMDealer version that comes on the FM Kienzle Fleet
Manager 98 Service Release 1 (Version 3.00) Compact Disc.

------------------------------------------------------------------------------

KEYWORDS: FM98

1156
www.mixtelematics.com

1156
 1157
10.3.19 Knowledge Base Article 19

Article Number 19

Title Total sum for vehicles in detailed daily trip report is incorrect

Created 11/23/1998 11:39:34 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:36:05 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

Total sum for vehicles in the detailed trip for vehicles shows the driver and not the vehicles.

----- CAUSE -----

This is caused by errors in the report engine.

----- SOLUTION -----

Upgrade your system to the latest version of the Fleet Manager software (FM Fleet Manager
FM2001 SR2 or later).

For more information on the Fleet Manager 98 update, please search for "FM98" and "Update".

----- STATUS -----

This problem has been solved with Service Release 1 of the Fleet Manager 98 Software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1157
www.mixtelematics.com

1157
 1158
10.3.20 Knowledge Base Article 20

Article Number 20

Title Incorrect serial number printed on registration card

Created 11/23/1998 11:41:52 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:35:51 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

Sometimes the printed registration form shows a serial number 5 characters in length. The
registration window in the software displays a 6 characters serial number. The 6 character serial
number displayed by the software is the correct serial number.

----- CAUSE -----

This is caused by errors in the report engine.

----- SOLUTION -----

Upgrade your system to the latest version of the Fleet Manager software (FM Fleet Manager
FM2001 SR2 or later).

For more information on the Fleet Manager 98 update, please search for "FM98" and "Update".

----- STATUS -----

This problem has been solved with Service Release 1 of the Fleet Manager 98 Software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1158
www.mixtelematics.com

1158
 1159
10.3.21 Knowledge Base Article 21

Article Number 21

Title Overflow Error on download if the driver ID is a negative number

Created 11/23/1998 11:46:00 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:35:38 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

An overflow error occurs on download if a driver with a negative ID Number has driven the vehicle
in question.

----- CAUSE -----

This is caused by errors in the client software validation for driver ID's.

----- SOLUTION -----

Upgrade your system to the latest version of the Fleet Manager software (FM Fleet Manager
FM2001 SR2 or later).

For more information on the Fleet Manager 98 update, please search for "FM98" and "Update".

----- STATUS -----

This problem has been solved with Service Release 1 of the Fleet Manager 98 Software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1159
www.mixtelematics.com

1159
 1160
10.3.22 Knowledge Base Article 22

Article Number 22

Title Changing trip details in the driver activity timeline causes an error

Created 11/23/1998 11:48:29 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:35:25 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

When saving changed trip details (Altering the Trip Category, or adding/modifying Trip Notes) from
the driver timeline, an unexpected error occurs.

----- CAUSE -----

This is caused by errors in the activity timeline.

----- SOLUTION -----

Upgrade your system to the latest version of the Fleet Manager software (FM Fleet Manager
FM2001 SR2 or later).

For more information on the Fleet Manager 98 update, please search for "FM98" and "Update".

----- STATUS -----

This problem has been solved with Service Release 1 of the Fleet Manager 98 Software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1160
www.mixtelematics.com

1160
 1161
10.3.23 Knowledge Base Article 23

Article Number 23

Title Boolean (digital) events with False parameter settings do not work

Created 11/23/1998 11:56:01 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:35:01 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

Setting up an event which occurs when a boolean (digital) parameter value is False does not work.
An event set up in this way will always occur when the specified parameter is True, regardless of
the way it is set up in the software.

----- CAUSE -----

This is caused by an error in the Fleet Manager 98 software.

----- SOLUTION -----

Upgrade your system to the latest available version of the Fleet Manager software (FM Fleet
Manager 2001 SR2 or later).

----- STATUS -----

This problem has been solved with Service Release 1 of the Fleet Manager 98 software and later.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM98

1161
www.mixtelematics.com

1161
 1162
10.3.24 Knowledge Base Article 24

Article Number 24

Title How do I rotate a 3D graph in the Fleet Manager software?

Created 11/25/1998 3:18:20 PM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 11:22:09 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

· FM Kienzle Fleet Manager 2001, all versions

----- SOLUTION -----

In order to rotate a three dimensional (3D) graph in the Fleet Manager software, move your mouse
pointer over the graph you would like to rotate. Press and hold down the control (CTRL) key on the
keyboard. The mouse pointer will change to circular arrows indicating that the graph can be rotated.
Move the mouse to rotate the graph. Release the control key once you have rotated the graph to the
desired orientation.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1162
www.mixtelematics.com

1162
 1163
10.3.25 Knowledge Base Article 25

Article Number 25

Title Manual Installation of FM '98 software

Created 12/1/1998 8:40:07 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 11:11:23 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, all versions

----- SUMMARY -----

Installing from an FM '98 CD fails with a message that a file on the CD could not be opened.

----- CAUSE -----

This problem is caused by a fault on the CD

----- SOLUTION -----

You can install the FM98 software manually by following the steps as outlined. (Assuming that D:\ is
your CD drive)

For an English installation:

1. Install the Microsoft SnapShot Viewer from D:\Snapshot Viewer\English\snpvw80.exe

2. Install the Microsoft Access Runtime from D:\Access Runtime\English\Setup.exe

3. If not running on Windows NT, install DCom for windows D:\DCOM\Windows 98\DCom98.exe

4. Restart your computer.

5. Install MDAC 2.0 (Microsoft Data Access Components) from D:\MDAC\mdac_typ.exe

6. Restart your computer.

7. Run the FM98 Lite Install set from D:\Lite Install Set\FM98.exe

Note: For other language installations, replace the word "English" in the above steps your language
in English (For example, "German").

------------------------------------------------------------------------------

KEYWORDS: FM98

1163
www.mixtelematics.com

1163
 1164
10.3.26 Knowledge Base Article 26

Article Number 26

Title Error creating database during installation

Created 12/7/1998 9:32:47 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 12:29:27 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

The default configuration file could not be found.

The default filename is English.ecu or German.ecu (version 2.10), or English.ecf or German.ecf

(version 3.00 (SR1) or later)

----- MORE INFORMATION -----

There are two possible causes for this problem.

1. The .ecu/.ecf file might be missing or corrupted

2. You might be installing the FM Kienzle Fleet Manager in the root directory of a hard drive. e.g.
C:\

----- SOLUTION -----

1. Check that the .ecu (version 2.10) or .ecf (version 3.00 (SR1) or later) file exists in the specified
install directory.

2. Install the software in a sub directory of the hard drive e.g. C:\Program Files\Fleet Manager

----- STATUS -----

The problem with installing the software to the root directory has been fixed with Service Release 1
of the FM Kienzle Fleet Maneger 98 software

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FMCreateDB

1164
www.mixtelematics.com

1164
 1165
10.3.27 Knowledge Base Article 27

Article Number 27

Title Error updating the FM '98 Database

Created 12/7/1998 9:50:26 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:33:49 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

Error occured in Database update: (52) Bad file name or number

----- MORE INFORMATION -----

This error occurs when updating the FM Kienzle Fleet Manager in the root directory of a hard drive.
e.g. C:\

The error can be duplicated by running the "FMCreateDB.Exe" application, located on the Fleet
Manager 98 CD, or running the Fleet Manager 98 Install set from "D:\Setup.exe", where "D:\" is the
letter of your CD-ROM drive, from the FM98 CD-ROM.

----- SOLUTION -----

Upgrade your system to the latest version of the Fleet Manager software (FM Fleet Manager
FM2001 SR2 or later).

Or use the following workaround:

Copy the Fleet Manager 98 database (usually "FMServer.mdb") into a sub directory of the hard
drive, e.g. C:\Program Files\Fleet Manager. Then use the "FM98 Administrator" program in the
Control Panel to set your database path to the new path for the Server Database. Attempt the
upgrade again.

----- STATUS -----

This has been fixed - Upgrade your system to the latest version of the Fleet Manager software (FM
Fleet Manager FM2001 SR2 or later).

------------------------------------------------------------------------------

KEYWORDS: FM98 FMCreateDB FMAdmin

1165
www.mixtelematics.com

1165
 1166
10.3.28 Knowledge Base Article 28

Article Number 28

Title Negative slope input configuration

Created 1/7/1999 11:13:00 AM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 12:30:00 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

When defining a input configuration with a negative slope, i.e. where the value increases as the voltage
decreases, the event definition does not work correctly.

----- MORE INFORMATION -----

If you define an event to occur when the temp > 90 degrees, the opposite effect takes place (event
ocurs when the temp < 90).

----- CAUSE -----

This problem is caused by a bug in the Fleet Manager 98 software

----- SOLUTION -----

You should use the opposite logic to determine then the event using the input line is true.

E.g. defining a High temperature event to occur when the parameter, Temperature < 90 and not > 90

----- STATUS -----

This has been fixed in Service Release 1 of Fleet Manager 98

------------------------------------------------------------------------------

KEYWORDS: FM98

1166
www.mixtelematics.com

1166
 1167
10.3.29 Knowledge Base Article 29

Article Number 29

Title FM100 reports do not fit on US Letter paper

Created 1/11/1999 10:10:01 AM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:32:00 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 100, version 1.10 (SR3) and previous.

----- SUMMARY -----

Reports generated by the FM100 application are designed to fit on A4 paper and do not fit on US Letter
paper.

----- STATUS-----

FM100 Service Release 4 includes an option, allowing you to specify which style of paper to print reports
on (A4 or US Letter). Download and install FM100 Service Release 4 or higher from the http://www.
mixtelematics.com website.

------------------------------------------------------------------------------

KEYWORDS: FM100

1167
www.mixtelematics.com

1167
 1168
10.3.30 Knowledge Base Article 30

Article Number 30

Title What's new in CI Data version 1.50 (SR1)

Created 1/11/1999 10:36:17 AM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:30:44 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· CI Data, version 1.50 (SR1)

----- SUMMARY -----

The following is a list of what's new in CI Data version 1.50 (SR1).

The latest version of CI Data software can be downloaded from the CI Data FTP Download site

· A new facility has been added allowing you to export trip data from your CI Data database, and save it
as a text file.

· A feature has been added to the system allowing you to backup your database to another location, to
be restored in the case of a crisis.

· You may now request information about a specific plug, by selecting “Plug Information” from the
“Code Plug” menu. This allows you to determine which vehicle or driver a plug is initialised for.

· The start-up wizard, that gets loaded when the software is run for the first time, is no longer
mandatory, and may be exited.

· You may now choose whether you want information to be displayed using the metric (Kilometres, and
Litres), U.S. (Miles, and U.S. Gallons), or Imperial (Miles, and Imperial Gallons) measurement
systems.

· Errors in the interpretation of two digit years have been corrected, ensuring millennium compliance.
Two digit years from 00 to 69 inclusive are interpreted as being from 2000 to 2069 inclusive. Two digit
years from 70 to 99 inclusive are interpreted as being from 1970 to 1999 inclusive. For more
information on millenium compliance, search for "CIDATA" and "Y2K".

------------------------------------------------------------------------------

KEYWORDS: CIDATA

1168
www.mixtelematics.com

1168
 1169
10.3.31 Knowledge Base Article 31

Article Number 31

Title What's new in CITAS 2010 version 2.00

Created 1/11/1999 10:45:28 AM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:29:39 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO -----

· CITAS 2010, version 2.00

----- SUMMARY -----

The following is a list of what's new in CITAS 2010 version 2.00.

The latest version of CITAS 2010 software can be downloaded from the CITAS 2010 FTP Download
site

New and Enhanced Features:

· Autopolling. The software can now automatically start the download of trips from the Office Interface.
The frequency of these download can be set in the options.

· Year 2000 compliance. The complete system has been extensively tested to ensure all dates are
interpreted correctly. Two digit years from 00 to 27 inclusive are interpreted as being from 2000 to
2027 inclusive. Two digit years from 28 to 99 inclusive are interpreted as being from 1928 to 1999
inclusive. For more information on Y2K Compliance in the CITAS 2010 Software, search for "CITAS"
and "Y2K".

· The vehicle and driver maintenance forms have been enhanced to allow the capture of a vehicle or
driver ID when adding a record.

· The vehicle and driver list reports have been enhanced to include the vehicle ID (fleet number) or
driver ID.

· The software check which rejected trips with a driver ID greater than 200 has been removed.

· The vehicle/driver access maintenance form has been enhanced to ensure that no more than 200
drivers may be granted access to a vehicle (to adhere to the 2010 unit’s limitations).

· The DATAMAN utility has been enhanced to provide backup and restore facilities. The CITAS 2010
application has been enhanced to include a backup reminder facility.

· The repair facility in the DATAMAN utility has been enhanced to rectify additional database corruption
related errors.

· New Bin files for the unit. This new bin file must be uploaded to all the vehicles in order to ensure
correct date handling.

1169
www.mixtelematics.com

1169
 1170

· The options facility has been enhanced to allow a sort order for vehicles and drivers to be specified.
This sort order applies to all vehicle or driver lists and reports.

· Report and Graph date criteria have been extended. The Start and End of range can now be selected
for both date and time. The existing Time Period is still retained for the trip reports.

· The Event criteria for the Event Report and Violation summary now retains the event selection
between reports.

· The Interval Report and Graph can now spread over two days. The total reported period may not be
more than 24 hours. This is to allow Accident Analysis over midnight.

Updates to known issues in Version 1.54 (SR2)

· The error that prevented a user from changing his/her password has been corrected.

· The user maintenance form has been enhanced to prevent the last “system” level user from being
changed to “user” level. The last “system” level user may no longer be deleted.

· The Utilisation column on the summary Trip report has been corrected.

· The errors on the driver scoring report have been corrected.

· Certain forms were displaying incorrect details when opened. This has been corrected.

· Trips with an unknown driver ID are no longer rejected when downloading. Instead, the unknown
driver ID is substituted with ID 1 (unknown driver).

· Trips with an unknown vehicle ID are no longer rejected when downloading. Instead, a vehicle record
with the unknown vehicle ID is created automatically.

· When events were disabled in the software, the unit configuration was not changed. This meant that
the buzzer still sounded for certain disabled events, confusing the driver. This has been corrected.

· The “indexing” error, which occurred under certain conditions when extracting a trip report has been
corrected.

------------------------------------------------------------------------------

KEYWORDS: CITAS 2010

1170
www.mixtelematics.com

1170
 1171
10.3.32 Knowledge Base Article 32

Article Number 32

Title What's new in Shurlok EV100 version 1.6 (SR2)

Created 1/11/1999 10:52:45 AM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:28:32 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· Shurlok EV100, version 1.6 (SR2)

----- SUMMARY -----

The following is a list of what's new in Shurlok EV100 version 1.6 (SR2).

The latest version of EV100 software can be downloaded from the EV100 FTP Download site

· A facility has been added allowing you to export trip data from your EV100 database, and save it as a
csv file.

· A feature has been added to the system, allowing you to backup your database to another location, to
be restored in the case of a crisis.

· You may now request information about a specific plug, by selecting “Plug Information” from the
“Code Plug” menu. This allows you to determine which vehicle or driver a plug is initialised for.

· The start-up wizard, that gets loaded when the software is run for the first time, is no longer
mandatory, and may be exited.

· You may now choose whether you want information to be displayed using the metric (Kilometres, and
Litres), U.S. (Miles, and U.S. Gallons), or Imperial (Miles, and Imperial Gallons) measurement
systems.

· Errors in the interpretation of two digit years have been corrected, ensuring millennium compliance.
Two digit years from 00 to 69 inclusive are interpreted as being from 2000 to 2069 inclusive. Two digit
years from 70 to 99 inclusive are interpreted as being from 1970 to 1999 inclusive. For more
information on millenium compliance, search for "EV100" and "Y2K".

------------------------------------------------------------------------------

KEYWORDS: EV100

1171
www.mixtelematics.com

1171
 1172
10.3.33 Knowledge Base Article 33

Article Number 33

Title What's new in Fleet Manager 100 version 1.20 (SR4)

Created 1/11/1999 10:56:38 AM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:27:06 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 100, version 1.20 (SR4)

----- SUMMARY -----

The following is a list of what's new in Fleet Manager version 1.20 (SR4).

The latest version of Fleet Manager 100 software can be downloaded from the CI Development web site
at http://www.mixtelematics.com

· The reports have been enhanced to allow printing on U.S. Letter style paper.

· The start-up wizard, that gets loaded when the software is run for the first time, is no longer
mandatory, and may be exitted.

· Errors in the interpretation of two digit years have been corrected, ensuring millennium compliance.
Two digit years from 00 to 69 inclusive are interpreted as being from 2000 to 2069 inclusive. Two digit
years from 70 to 99 inclusive are interpreted as being from 1970 to 1999 inclusive. For more
information on millenium compliance, search for "FM100" and "Y2K".

------------------------------------------------------------------------------

KEYWORDS: FM100

1172
www.mixtelematics.com

1172
 1173
10.3.34 Knowledge Base Article 34

Article Number 34

Title 16 bit Fleet Software fails to run under Windows 95, 98, or NT

Created 1/11/1999 12:15:25 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 8/2/1999 12:17:35 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 100, all versions

· CI Data, all versions

· Shurlok EV100, all versions

· CITAS 2010, all versions

----- SUMMARY -----

When attempting to execute one of the above products with the default language in the Regional
Settings set to anything other than English, either nothing happens; or the appropriate product's
splash screen is displayed, and then dissappears.

----- CAUSE -----

This problem is caused by an incompatibility between the 16 bit engine, on which the software is
based, and some of the Windows locale settings.

----- SOLUTION -----

Please ensure that your default language is set to one of the "English" languages at all times.

------------------------------------------------------------------------------

KEYWORDS: FM100 EV100 CIDATA CITAS 2010

1173
www.mixtelematics.com

1173
 1174
10.3.35 Knowledge Base Article 35

Article Number 35

Title 16 bit Software - Error executing graph

Created 1/11/1999 12:22:28 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 8/2/1999 12:17:41 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 100, all versions

· CI Data, all versions

· Shurlok EV100, all versions

· CITAS 2010, all versions

----- SUMMARY -----

When attempting to execute a graph, using one of the above products running under Windows 95, 98, or
NT; and with the default language set to something other than English, the following error message is
generated:

"Error in graph criteria - -21474836401: OLE Automation error."

----- CAUSE -----

This problem is caused by an incompatibility between the 16 bit engine, on which the software is based,
and some of the Windows locale settings.

----- SOLUTION -----

Please ensure that your default language is set to one of the "English" languages at all times.

------------------------------------------------------------------------------

KEYWORDS: FM100 EV100 CIDATA CITAS 2010

1174
www.mixtelematics.com

1174
 1175
10.3.36 Knowledge Base Article 36

Article Number 36

Title When I try to generate a report, Error 13 with no description is displayed

Created 1/12/1999 5:50:05 PM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 12:30:37 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

When generating reports on certain PCs, Error 13 is displayed. No description is provided with this error
code.

----- CAUSE -----

This error is caused by an incompatibility in the Fleet Manager 98 reporting engine. It occurs when one of
the following conditions is true:

1. Either the English version of Fleet Manager 98 was installed and the Windows locale is set to any
language other than one of the English language options.

2. Or the German version of Fleet Manager 98 was installed and the Windows locale is set to any
language other than one of the German language options.

----- WORK AROUND -----

If you installed the English version of the Fleet Manager 98 application, please ensure that your Windows
locale is set to one of the English language options at all times (irrespective of the operating system
language).

If you installed the German version of the Fleet Manager 98 application, please ensure that your
Windows locale is set to one of the German language options at all times (irrespective of the operating
system language).

----- STATUS -----

This problem has been corrected in Service Release 1 of the Fleet Manager 98 software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1175
www.mixtelematics.com

1175
 1176
10.3.37 Knowledge Base Article 37

Article Number 37

Title How to configure the Fleet Manager application for client-server

Created 1/22/1999 5:54:52 PM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 12/17/1999 7:19:42 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- OVERVIEW -----

The Fleet Manager application utilises an advanced three-tier client-server model and is designed to scale
from running on a single stand-alone computer to running on multiple computers on a local area network
(LAN) or wide area network (WAN).

The purpose of this document is to describe the procedure required to configure the Fleet Manager
application to operate on a network. This document is intended for network administrators and assumes
that the reader has an in-depth understanding of Microsoft Windows 95, Windows 98 and Windows NT
networking. Administrative access to the network may be required in order to make the configuration
changes documented below.

----- COMPONENTS -----

The Fleet Manager application utilises a technology called Distributed Component Object Model (DCOM).
This model provides a great deal of flexibility and caters for a wide variety of client-server configurations.
This document describes a typical client-server configuration and does not cover all possible
configurations.

The Fleet Manager system consists of four major components, which perform discrete functions and
interact with one another. The table below lists these components and provides a brief description of their
functions:

Component Filename Functions

Client FMClient.EXE Provides the Fleet Manager user interface including all
windows, dialogs, menus, toolbars etc.

Database Server FMServer.EXE Retrieves data from the database and passes it to the
Client.

Receives data from the Client and updates the database.

1176
www.mixtelematics.com

1176
 1177

Reports Server FMReports.EXE Receives report requests from the Client.

Manages the report queue.

Controls the Report Engine.

Informs the Client about report generation progress.

Transfers completed report files to the Client.

Report Engine FMReports.MDE Generates report files.

In a stand-alone configuration, these components all run on a single computer. The Fleet Manager
installation set installs the Fleet Manager system to run in stand-alone mode.

A typical client-server configuration includes one or more Client computers running the Client component
and a Server computer running the Database Server, Reports Server and Report Engine components.

----- REQUIREMENTS -----

To configure the Fleet Manager application for client-server, the following is required:

1. Client - a Pentium 100 Mhz or higher personal computer running Windows 95, Windows 98 or Windows
NT 4.0 with at least 32 MB of RAM and at least 80 MB of available disk space.

2. Server - a Pentium 200 Mhz or higher personal computer running Windows 95, Windows 98 or
Windows NT 4.0 with at least 32 MB of RAM and at least 80 MB of available disk space. Note: The
amount of RAM required on the server is dependent on the number of applications running on the
server as well as the number of Client connections.

3. Network - any network infrastructure supported by the version of Windows on the Clients and Server.

4. TCP/IP - the TCP/IP protocol must be installed and configured on each Client computer as well as the
Server computer.

5. Administrative access - you must have administrative access to the network as well as to each Client
computer and the Server computer in order to make the configuration changes documented below.

6. User-level access control - DCOM makes use of the user-level access control security model. Windows
95 and Windows 98 computers must be configured for user-level access control and NOT for share-
level access control. Please consult the appropriate Windows documentation for more information on
configuring user-level access.

----- CONFIGURATION PROCEDURE -----

Before you begin, ensure that the network is fully functional by logging into each Client computer with
administrative access. Check that each Client computer is capable of connecting to a file-share on the
Server computer.

----- CONFIGURING THE SERVER -----

The following steps should be performed on the Server computer:

1. Log into the Server with administrative access.

2. Install the Fleet Manager application by following the instructions provided in the software package.

1177
www.mixtelematics.com

1177
 1178

3. Run the Fleet Manager application and confirm that it is functioning correctly in stand-alone mode.

4. Close the Fleet Manager application.

5. If the Server is running Windows NT, use the "User Manager" utility to create a user account for the
Fleet Manager application. You must grant this user account the necessary permissions to access the
Fleet Manager directories and files. You must also log into the Server using this user account’s
credentials and install a printer driver. You may install any printer driver. This is required for the Report
Engine to be able to generate reports.

6. If the Server is running Windows 95 or Windows 98, Install the appropriate DCOM configuration utility
by running DCM95CFG.EXE or DCM98CFG.EXE respectively. If the Server is running Windows NT 4.0,
the DCOM configuration utility will already be installed.

7. Run the DCOM configuration utility by clicking on the "Start" button, selecting "Run", and entering
"DCOMCNFG" and clicking the "OK" button.

8. Click on the "Default Properties" tab. Ensure that the "Enable Distributed COM on this computer"
checkbox is checked. Set the default authentication level to "(None)". Set the default impersonation
level to "Impersonate".

If the computer is running Windows 95 or Windows 98, click the "Edit Default" button and set access the
permissions to grant access to "The World".

If the computer is running Windows NT, click the appropriate "Edit Default" button and set the access
permissions to grant access to "Everyone". Click the appropriate "Edit Default" button and set the launch
permissions to allow launching by "Everyone". Click the appropriate "Edit Default" button and set the
configuration permissions to allow "Everyone" read permissions.

9. Click on the "Applications" tab. Scroll down to the "FMReports.Report" entry in the applications list.

10.Double-click on the "FMReports.Report" entry in the applications list to open the application properties
dialog. Click on the "Location" tab. Ensure that the "Run application on this computer" checkbox IS
checked. Ensure that the "Run application on the computer where the data is located" and "Run
application on the following computer" checkbox are NOT checked.

11.Click on the "Security tab".

If the computer is running Windows 95 or Windows 98, ensure that the "Use default access permissions"
option is selected.

If the computer is running Windows NT, ensure that the "Use default access permissions", "Use default
launch permissions" and "Use default configuration permissions" options are selected.

12.If the Server is running Windows NT, click on the "Identity" tab. Ensure that the "This user" option is
selected and enter the credentials for the user account created in step 6 above.

13.Click the "OK" button to close the application properties dialog.

14.Repeat steps 11 through 14 for the "FMServer.Organisation" application.

15.Finally, locate the application entitled "Microsoft Access Database". Configure this application in
exactly the same way as you configured the "FMReports.Report" and "FMServer.Server" applications.

16.Click the "OK" button to close the DCOM configuration utility. Restart the computer if prompted to do
so.

17.If the Server is running Windows 95 or Windows 98, copy the launch utility (FMLaunch.EXE) to a
suitable location on the Server and create a shortcut in the Startup group to run it every time the Server
is logged in. Also create a shortcut in the Startup group to run RPCSS.EXE (installed by the DCOM

1178
www.mixtelematics.com

1178
 1179

configuration utility install set and located in the Windows\System directory).

On Windows 95 and Windows 98, the Server computer must be left logged in with both of these utilities
running in order for Clients to establish connections to the Server. If either utility is not running, Clients will
display an error message when attempting to connect to the Server. These utilities are not required on
Windows NT and the Server computer may be left logged off.

----- CONFIGURING THE CLIENTS -----

The following steps should be performed on each Client computer:

1. Log into the Client with administrative access.

2. Install the Fleet Manager application by following the instructions provided in the software package.

3. Run the Fleet Manager application and confirm that it is functioning correctly in stand-alone mode.

4. Close the Fleet Manager plication.

5. If the Client is running Windows 95 or Windows 98, Install the appropriate DCOM configuration utility by
running DCM95CFG.EXE or DCM98CFG.EXE respectively. If the Client is running Windows NT 4.0, the
DCOM configuration utility will already be installed.

6. Run the DCOM configuration utility by clicking on the "Start" button, selecting "Run", and entering
"DCOMCNFG" and clicking the "OK" button.

7. Click on the "Default Properties" tab. Ensure that the "Enable Distributed COM on this computer"
checkbox is checked. Set the default authentication level to "(None)". Set the default impersonation
level to "Impersonate".

8. Click on the "Default Security" tab. Ensure that the "Enable remote connection" check-box is checked.

If the computer is running Windows 95 or Windows 98, click the "Edit Default" button and set access the
permissions to grant access to "The World".

If the computer is running Windows NT, click the appropriate "Edit Default" button and set the access
permissions to grant access to "Everyone". Click the appropriate "Edit Default" button and set the launch
permissions to allow launching by "Everyone". Click the appropriate "Edit Default" button and set the
configuration permissions to allow "Everyone" read permissions.

9. Click on the "Applications" tab. Scroll down to the "FMReports.Report" entry in the applications list.

10.Double-click on the "FMReports.Report" entry in the applications list to open the application properties
dialog. Click on the "Location" tab. Ensure that the "Run application on the computer where the data is
located" and "Run application on this computer" checkboxes are NOT checked. Ensure that the "Run
application on the following computer" checkbox IS checked. Enter the name of the Server computer in
the textbox.

11.Click on the "Security tab".

If the computer is running Windows 95 or Windows 98, ensure that the "Use default access permissions"
option is selected.

If the computer is running Windows NT, ensure that the "Use default access permissions", "Use default
launch permissions" and "Use default configuration permissions" options are selected.

12.If the Client is running Windows NT, click on the "Identity" tab. Ensure that the "This user" option is
selected and enter the credentials for the user account created in step 6 above.

1179
www.mixtelematics.com

1179
 1180

13.Click the "OK" button to close the application properties dialog.

14.Repeat steps 10 through 12 for the "FMServer.Organisation" and "Microsoft Access Database"
applications.

15.Click the "OK" button to close the DCOM configuration utility. Restart the computer if prompted to do
so.

16.Run the Fleet Manager application and test that it is functioning correctly.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1180
www.mixtelematics.com

1180
 1181
10.3.38 Knowledge Base Article 38

Article Number 38

Title 'Invalid Procedures for Processing Event Type' During FM200 Download

Created 2/3/1999 12:34:41 PM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 4/12/2000 5:02:19 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 2.10

----- SUMMARY -----

An unexpected error occurs when downloading

----- MORE INFORMATION -----

The following error information is displayed:

54321 (0x0000D431): Invalid procedure for processing event type.

Seq=115549 Event=32000 occurred in downloading FM200Data.ProcessEvent (line 34500). The error

has been logged.

The values for "Seq" and "Event" may vary, depending on the data stored in the vehicle unit.

----- CAUSE -----

This problem occurs due to corruption inside the vehicle unit. It takes place when a new configuration is
loaded into the vehicle during a trip.

----- SOLUTION -----

The solution to this is two-fold:

1. Create a clear data plug, using the FMDealer software - and clear all data from the FM200 unit in
question.

2. Use the "Swap Unit" function in the software (Please search for "Swap Unit" (ALL Keywords) in the
Knowledge Base for guidelines, and more information on this function), on the vehicle that is causing the
error.

A new configuration will then have to be uploaded into the vehicle.

----- STATUS -----

This problem has been fixed with the device driver files (.DDR) included with Service Release 1 (SR1) of
the Fleet Manager '98 software.

1181
www.mixtelematics.com

1181
 1182

------------------------------------------------------------------------------

KEYWORDS: FM200 FM98

1182
www.mixtelematics.com

1182
 1183
10.3.39 Knowledge Base Article 39

Article Number 39

Title Fleet Manager Terminology (FM200(e) Unit)

Created 2/9/1999 8:24:26 PM

Created By Henry Potgieter (MiX Telematics - Stellenbosch)

Last Modified 3/26/2002 11:56:08 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

· FM Fleet Manager 2001, all versions

----- SOLUTION -----

Definition of Trip terms:

TRIP

A Trip is defined as the period during which the vehicle is in use. The FM considers the vehicle to be in
use or active when the Ignition is on or when engine revs or road speed are detected. A trip ends if the
vehicle is not in use for the Arming Delay time defined for the vehicle (default is 5 minutes).

START

The Start of a trip is defined as the time when the vehicle becomes active.

END

The End of a trip is defined as the time when the vehicle becomes in-active (i.e. the Ignition is OFF, and
the engine is stopped), and does not become active again for the Arming Delay period.

DURATION

The Duration of a trip is defined as the difference between the start and end times of the trip.

PARKING

Parking is the time when the vehicle is not active, i.e. when the vehicle is not in a Trip.

SUB TRIP

A Sub Trip is defined as each period during a trip the vehicle was moving. A Sub Trip will end at the end
of the Trip or if the vehicle is stationary for longer than the Standing Delay defined for the vehicle
(default is 2 minutes).

1183
www.mixtelematics.com

1183
 1184

DEPART

Depart is the start of a subtrip, and is defined as the time when the vehicle starts to move.

HALT

Halt is the end of a sub trip, and is defined as the time when the vehicle becomes stationary, and does
not move for a pre-determined time (the Arming Delay or Standing Delay).

DRIVING TIME

Driving Time is defined as the difference between the Depart and Halt times of a sub trip. The Driving
Time for a Trip is the sum of the Driving Times for each sub trip in the trip.

STANDING TIME

Standing Time is defined as the time within a trip that is outside of driving time, i.e. the time between
Trip Start and first Depart, the time between each Halt and Depart, and the time between the last Halt
and Trip End.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM98 FM2000

1184
www.mixtelematics.com

1184
 1185
10.3.40 Knowledge Base Article 40

Article Number 40

Title Fleet Manager Software procedure to follow when an FM200(e) unit is swapped

Created 3/11/1999 5:13:44 PM

Created By Jeremy Hartley (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 11:25:55 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

· FM Kienzle Fleet Manager 2001, all versions

----- SUMMARY -----

This article describes the procedure to follow in the Fleet Manager Software after exchanging an FM200
or FM200e vehicle unit. Failure to follow these steps could result in incorrect information being stored for
the vehicle in the Fleet Manager database.

----- MORE INFORMATION -----

For installation instructions, please see the Fleet Manager Hardware Manual.

----- CAUSE -----

In cases where an FM200 or FM200e unit has to be replaced, the Fleet Manager software needs to
reset data stored internally to ensure further data processing for the unit is handled correctly. Failure to
follow these steps could result in incorrect data being stored for the vehicle.

----- SOLUTION -----

The following describes the steps should be taken:

1) Replace the physical unit in the vehicle. Please consult the Fleet Manager Hardware manual for more
information.

2) In the Fleet Manager software, double click on the appropriate vehicle icon in the tree/list view. The
Vehicle Properties dialog will be displayed. Click the Swap Unit button. Please read the warning
message dialog before continuing.

3) Check the Input and Event configurations for the vehicle (these can also be found in the Vehicle
Properties dialog).

4) In the FMDealer software, format all green plugs to be used for the unit.

5) In the Fleet Manager software, initialise a formatted green plug for the unit. The confirmation step of
the Wizard should indicate that the Vehicle ID will be updated and the Event Configuration will be

1185
www.mixtelematics.com

1185
 1186

uploaded.

6) Insert this plug into the vehicle unit. The vehicle ID will be set and the required configuration to be
monitored will be uploaded.

7) Perform a test trip in the vehicle and download to confirm the unit is functioning correctly.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM98 FM2000

1186
www.mixtelematics.com

1186
 1187
10.3.41 Knowledge Base Article 41

Article Number 41

Title Fleet Manager Software procedures for when a FM200(e) Unit is cleared

Created 3/11/1999 5:14:36 PM

Created By Jeremy Hartley (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 11:12:18 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

· FM Kienzle Fleet Manager 2001, all versions

----- SUMMARY -----

This article describes the steps needed to be done in the Fleet Manager Software after clearing the
memory of a FM200 or FM200e vehicle unit. Failure to follow these steps could result in incorrect
information being stored for the vehicle in the Fleet Manager database.

----- CAUSE -----

In cases where a FM200 or FM200e unit's memory has to be cleared, the Fleet Manager software
needs to reset data stored internally to ensure further data processing for the unit is handled correctly.
Failure to follow these steps could result in incorrect data being stored for the vehicle.

----- SOLUTION -----

The following describes the steps should be taken:

1) Initialise a Clear Data plug in the FMDealer software. Insert this plug into the vehicle until a beep is
heard. The LED should now be flashing long on with a short off.

2) In the Fleet Manager software, in the Vehicle Properties for the vehicle, click in the Swap Unit
function. Please read the warning message before confirming the swap unit function.

3) In the Fleet Manager software, confirm the Input and Event configurations for the vehicle (Vehicle
Properties).

4) In the FMDealer software, format all green plugs to be used for the unit.

5) In the Fleet Manager software, initialise a formatted green plug for the unit. The confirmation step of
the Wizard should indicate that the Vehicle ID will be updated. The Event Configuration has to be
uploaded.

6) Insert this plug into the vehicle unit. The required configuration to be monitored will be uploaded.

------------------------------------------------------------------------------

1187
www.mixtelematics.com

1187
 1188

KEYWORDS: FM200 FM200e FM98 FM2000 FM2001 FMDealer

1188
www.mixtelematics.com

1188
 1189
10.3.42 Knowledge Base Article 42

Article Number 42

Title Guidelines for Report Logo Images

Created 3/17/1999 3:20:55 PM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 10/3/2001 3:44:29 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98 SR1, and later

· FM Kienzle Fleet Manager 2000, all versions

· FM Kienzle Fleet Manager 2001, all versions

----- SUMMARY -----

Images used as report logos will give the best results if the are approximately the right size.

----- MORE INFORMATION -----

When a custom image file is used for a report logo, the image is re-sized to fit on the report. The
default logo has a size of 154×64 pixels and custom logos are resized to this according to the following
rules.

· Images smaller than the standard size are not re-sized.

· Images larger than the standard size are re-sized and their aspect ratio is preserved. This means
that the height and width of the image are shrunk so that it's largest dimension just fits within the
standard size. So an image of 567×173 pixels would be shrunk to 20×64 pixels and an image of
173×567 pixels would be shrunk to 154×47 pixels.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FM2001

1189
www.mixtelematics.com

1189
 1190
10.3.43 Knowledge Base Article 43

Article Number 43

Title Report generation finishes but the report is not displayed.

Created 3/17/1999 4:33:01 PM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:25:22 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· Fleet Manager 98 SR1 and later

----- SUMMARY -----

When a report is generated, the report generation window closes but the report snapshot is not
displayed.

----- CAUSE -----

This problem occurs when the image file selected as the report logo is too large.

----- SOLUTION -----

Use a smaller image as the report logo. The Guidelines for Report Logo Images article provides
more information about custom report logos.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1190
www.mixtelematics.com

1190
 1191
10.3.44 Knowledge Base Article 44

Article Number 44

Title CITAS 2010 - Divide by zero generating Driver Score Report

Created 3/23/1999 10:08:14 AM

Created By Jeremy Hartley (MiX Telematics - Stellenbosch)

Last Modified 8/2/1999 12:18:43 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· CITAS 2010 versions 1.54, 2.00

----- SUMMARY -----

When generating a Driver Score report, a Divide by Zero error occurs.

----- CAUSE -----

This occurs when one or more event trigger values are set to 0 for the scored events. The standard
event configuration has the following constraints used in the calculation of Driver Scoring:

· GB RPM Low Revs/min

· Harsh Brake Km/h/s

· Max Road Speed

· Max Engine RPM

When modifing the Event configuration, if any of these constraints are set to 0, the Driver Scoring
calculation will fail.

----- WORK AROUND -----

Ensure that all the scored constraints have a non-zero trigger value. This should be checked at the
Fleet Default level and for all individual vehicles where the defaults have been overridden.

----- STATUS -----

This has been corrected in version 2.00 of the CITAS 2010 Software.

------------------------------------------------------------------------------

KEYWORDS: CITAS 2010

1191
www.mixtelematics.com

1191
 1192
10.3.45 Knowledge Base Article 45

Article Number 45

Title FM Kienzle Fleet Manager Software Year 2000 Compliance (Y2K)

Created 3/25/1999 9:06:28 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:24:37 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

The FM Kienzle Fleet Manager system (including hardware and software) has been tested, and found to
function correctly under the conditions listed below, when FM98 application software version 3.00
(Service Release 1) or higher is used. It should also be noted that, since the FM200 and FM200e Units
are re-programmable units, the device driver files (.DDR) from the FM98 SR1 Compact Disc, or higher,
should be uploaded into all FM200 or FM200e vehicles in your organisation.

---- FM100 UNIT ----

The FM100 unit records dates in a proprietary compressed format. To conserve storage space within the
unit, the century is not recorded with dates. The unit firmware is designed to accommodate the
millennium rollover and applies the following rules to deal with dates well into the twenty-first century.
Dates with a year of 70 or greater are considered to be from the twentieth century i.e. dates ranging from
01/01/70 to 31/12/99 inclusive are considered to be 01/01/1970 to 31/12/1999 inclusive. Dates with a
year of 69 or less are considered to be from the twenty first century i.e. dates ranging from 01/01/00 to
31/12/69 inclusive are considered to be 01/01/2000 to 31/12/2069 inclusive.

---- FM200 AND FM200e UNITS ----

The FM200 and FM200e both record dates in a proprietary compressed format. To conserve storage
space within the unit, the century is not recorded with dates. The unit firmware is designed to
accommodate the millennium rollover and applies the following rules to deal with dates well into the
twenty-first century. Dates with a year of 38 or greater are considered to be from the twentieth century i.
e. dates ranging from 01/01/38 to 31/12/99 inclusive are considered to be 01/01/1938 to 31/12/1999
inclusive. Dates with a year of 37 or less are considered to be from the twenty first century i.e. dates
ranging from 01/01/00 to 31/12/37 inclusive are considered to be 01/01/2000 to 31/12/2037 inclusive.

---- SOFTWARE ----

The Fleet Manager application software applies the rules documented above to convert dates received
from the FM100, FM200 and FM200e units as well as dates with two digit years entered via the software
interface. All dates are converted into fully qualified dates before being stored in the Fleet Manager
database.

The following areas of the Fleet Manager application software are affected by dates and have been

1192
www.mixtelematics.com

1192
 1193

tested to ensure they function correctly:

· The Daylight Savings fields on the Language tab of the Options dialog.

· The Set Date/Time function accessed from the Code Plug menu.

· The report and graph selection criteria wizards.

· The Fuel Usage maintenance window.

· The Registration Wizard.

· Date/Time Specific Events.

---- TESTS CONDUCTED ----

Several tests have been conducted to ensure that the entire system will function correctly into the
twenty-first century. An FM100 unit was connected to a trip simulator. The unit’s real-time clock was set
forward as required for each test and several simulated trips were done. All data was downloaded into
the Fleet Manager software and the database and system outputs were checked for validity. A year 2000
compliant personal computer was used to conduct all tests and the personal computer’s real-time clock
was set forward as required for each test.

The same test was conducted with both an FM200 and FM200e unit, connected to a trip simulator. In
addition, the unit's Battery Disconnect event was specifically tested over a selection of roll-over periods.

A test results pack can be downloaded from ftp://ftp.centre-point.com/KBase/FM98_Y2k_Test_Results.

zip. This 360kb .ZIP file contains a collection of report snapshot files (.snp), and the criteria files (.cri)
files used to generate those reports.

Dates with a two-digit year

All functions within the application software were tested to ensure that two-digit years are converted and
stored in the database correctly. Dates outside of the valid system date range documented above
(01/01/1970 to 31/12/2069 inclusive) are rejected by the software and may not be entered.

The 1st of September 1999 (01/09/1999)

1/9/99 was identified as a date which may have caused errors. The system was tested to ensure that it
functions correctly on this date.

The 9th of September 1999 (09/09/1999)

The day, 9/9/99 was identified as a date which may have caused errors under certain circumstances.
The system was tested to ensure that it functions correctly on this date.

The 31st of December 1999 (31/12/1999)

All functions within the system were tested to ensure that the rollover to the 1st January 2000 is handled
correctly.

The 29th of February 2000 (29/02/2000)

Many people are not aware that the year 2000 is a leap year. This is the case and all system functions
were tested to ensure that this date is considered valid and is handled correctly.

The 30th of April 2000 (30/04/2000)

This will be the first month of the year 2000 ending on a weekend. All system functions were tested to

1193
www.mixtelematics.com

1193
 1194

ensure that this is handled correctly.

The 10th of October 2000 (10/10/2000)

On systems where dates are entered in the format “MMDDYY”, this would be the first 6-digit date that
could cause a problem (101000). All system functions were tested to ensure that this date is handled
correctly.

The 31st of December 2000 (31/12/2000)

This will be the last day of the year 2000. All system functions were tested to ensure that the rollover to
1st January 2001 is handled correctly.

The 29th of February 2001 (29/02/2001)

Many people are under the impression that the year 2001 is a leap year. This is not the case and all
system functions were tested to ensure that this date is not considered valid.

The 31st of December 2001 (31/12/2001)

This will be the last day of the year 2001, the end of the second year after the turn of the century. All
system functions were tested to ensure that the rollover to 1st January 2002 is handled correctly.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM200 FM200e FM98 FM2000

1194
www.mixtelematics.com

1194
 1195
10.3.46 Knowledge Base Article 46

Article Number 46

Title What's New in FM Kienzle Fleet Manager 98 version 3.00 (SR1)

Created 3/26/1999 9:09:03 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:23:29 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

The following is a list of what's new in FM Kienzle Fleet Manager 98, version 3.00 (SR1).

· Full support for the download module on Windows NT computers has been added. The install set
automatically installs and configures the required device drivers on Windows NT computers to
enable uploading and downloading of information to and from code-plugs.

· The install set allows you to disable driver reporting. This is a legal requirement in certain regions.

· A new Parameter Wizard simplifies the process of adding parameters by explaining the different
types of parameters and providing examples.

· Support for pulse generating devices such as fuel flow meters has been added. Parameters may be
defined to record fuel consumption per sub-trip.

· New FM200 system parameters have been made available, allowing a host of new event
possibilities.

For example:

The “Current Time” parameter could be used to create “Overtime Driving” events.

The “Ignition On” parameter could be used to create an event which takes the status of the vehicle’s
ignition into account.

· A new system event has been added to record times when battery power is removed from the unit.

· Support for the new FM200e (FM200 with Engine Management Interface) has been added.

The FM200e is a hardware interface module, which connects to the FM200 and provides a number of
engine management facilities.

· The Report/Graph Criteria Wizard has been enhanced to allow user friendly date ranges to be
selected. For example “Today”, “Yesterday”, “Week to date” etc.

A specific date range may also be specified and this has been enhanced to include the time as well as

1195
www.mixtelematics.com

1195
 1196

the date.

· The Trip Filter pane of the Report/Graph Criteria Wizard has been enhanced to include a time
window. This allows you to report on trips, which occurred within a specified time range.

· The last pane of the Report/Graph Criteria Wizard allows you to save your specifications. These can
be opened at a later stage to generate the same report or graph by simply clicking the Finish button.

User friendly date ranges are dynamically adjusted when a criteria file is opened. For example, if you
specify a date range of “This week” for your report or graph, the start and end dates of the current week
will be calculated automatically every time the criteria file is opened.

· You can define reporting batches containing any number of criteria files.

Simply click the “Run” button before going home in the evening and the entire batch of report and
graph files will be generated automatically and saved into pre-defined directories for you to review at
your leisure.

This is very useful for batches of reports and graphs required on a regular basis. For example, you
could save a number of criteria files with a date range of “Last Week”. Running the batch on a Monday
would generate reports and graphs for the previous week.

· You can enable profiling of certain parameters and specify any number of profile ranges. This
causes the unit to record the amount of time spent within each range.

The percentage of time spent in each range during a specified period can be graphed. This can provide
an excellent view of driver and or vehicle performance.

· The Activity Timeline has been enhanced to allow you to specify which events to display.

For vehicles with a fuel measurement device connected, fuel consumption information is displayed in
the detail text.

· You can supply a graphic file containing your company’s logo to be printed on all reports.

Use the Fleet Manager ‘98 Administrator utility to specify the location of the graphic file.

· Additional fuel consumption reports and graphs have been provided to accommodate FM200 units
with fuel flow meters connected.

Detailed and summary reports can be generated showing fuel consumption derived from fill-up
information captured via the Vehicles form (“Entered”), fuel usage measured by the unit (“Measured”)
as well as a comparison of the two.

· The Vehicle Configuration Group and Vehicles forms have been enhanced to allow the capture of a
target fuel consumption. This target as well as the percentage difference between actual
consumption and target consumption is displayed on the fuel consumption reports and graphs.

· All reports have been enhanced to print the selection criteria specified in the Report Criteria Wizard
on the last page.

Other Enhancements

· Activity Timeline performance has been enhanced.

· Reporting performance has been enhanced.

· The FM200 configuration has been enhanced so that if a driver plug is inserted during a trip (but

1196
www.mixtelematics.com

1196
 1197

whilst the vehicle is stationary), the trip is automatically ended and a new trip started for the new
driver

· The Plug Information dialog has been enhanced to display device driver information contained in a
device driver plug.

To download this document in Microsoft Word 97 format, with screen-shots, go to ftp://ftp.centre-point.

com/KBase/What's New in SR1.zip. This is a 453kb zip file.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM200 FM98

1197
www.mixtelematics.com

1197
 1198
10.3.47 Knowledge Base Article 47

Article Number 47

Title FM98 - Error 3001 when program starts

Created 3/29/1999 8:56:36 AM

Created By Jeremy Hartley (MiX Telematics - Stellenbosch)

Last Modified 8/2/1999 12:19:25 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, versions 2.10 and 2.11

----- SUMMARY -----

When the program starts, an error is reported as follows:

3001 (0x00000BB9): The application is using arguments that are of the wrong type, are out
of acceptable range, or are in conflict with one another. occurred in Groups.GetList (Line
2660).

The program then terminates.

----- CAUSE -----

This is caused by the installation of a later version of the database access software, called "Microsoft
Data Access Components" [MDAC]. This could be installed indirectly by other products (Full installation
of Microsoft Internet Explorer 5 [IE5] has this).

----- STATUS -----

This has been fixed in the SR1 release (version 3.00)

------------------------------------------------------------------------------

KEYWORDS: FM98

1198
www.mixtelematics.com

1198
 1199
10.3.48 Knowledge Base Article 48

Article Number 48

Title unInstaller Fails to Initialise on Windows NT

Created 3/29/1999 12:32:12 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 8/24/1999 1:38:40 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00

----- SUMMARY -----

When installing the Fleet Manager 98 software on a Microsoft Windows NT computer, and another
copy of the FM98 software has already been installed on the same computer, the unInstaller setup
may fail to initialise; and you will be unable to uninstall the FM98 software.

----- CAUSE -----

This problem occurs because there is another copy of the Fleet Manager 98 on the same computer.
Under some circumstances, the installation set may be unable to overwrite the "Uninst.isu" installation
log file.

----- SOLUTION -----

The workaround for this problem is to first uninstall the previous copy of the FM98 software (Ensure
that you have a recent backup of your Fleet Manager 98 Database before attempting this), and then
install the newer version.

You may also manually delete the "Uninst.isu" file, located in the directory where the Fleet Manager 98
is installed, from within Windows NT Explorer, before installing a later version of the Fleet Manager 98
software.

----- STATUS -----

This problem is being investigated.

------------------------------------------------------------------------------

KEYWORDS: FM98

1199
www.mixtelematics.com

1199
 1200
10.3.49 Knowledge Base Article 49

Article Number 49

Title 'Invalid SelectionIDs' when Opening Criteria File.

Created 3/29/1999 12:38:53 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:22:46 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00

----- SUMMARY -----

When attempting to open a criteria file, the following error is displayed: "An unexpected error occured in
the report server. An invalid SelectionIDs parameter was passed to the GenerateReport routine in
FMReports.MDB".

----- MORE INFORMATION -----

This error occurs when opening a criteria file, when none of the selected items (Sites, Drivers or
Vehicles, or Reporting Groups, as applicable) exist in the FM98 database anymore, and clicking
"Finish".

----- CAUSE -----

This is caused by the fact that none of the items (Sites, Drivers or Vehicles, or Reporting Groups, as
applicable) exist in the FM98 database, anymore.

----- SOLUTION -----

Upgrade your system to the latest version of the Fleet Manager software available (FM Fleet Manager
2001 SR2 or later).

----- STATUS -----

This problem has been solved with version 3.00.0008 and later versions of the Fleet Manager Client.

------------------------------------------------------------------------------

KEYWORDS: FM98

1200
www.mixtelematics.com

1200
 1201
10.3.50 Knowledge Base Article 50

Article Number 50

Title 16 bit Fleet Products on a Network

Created 3/29/1999 1:02:17 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 8/2/1999 12:19:44 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Shurlok EV100, all versions

· CI Data, all versions

· CITAS 2010, all versions

· FM Kienzle Fleet Manager 100, all versions

----- QUESTION -----

Can the above products be run over a network?

----- ANSWER -----

Running these products over a network is not supported in any way. It is technically possible to point
these products to a database on a network file share, but this practise could result in data loss, and is
not supported.

------------------------------------------------------------------------------

KEYWORDS: FM100 EV100 CIDATA CITAS 2010

1201
www.mixtelematics.com

1201
 1202
10.3.51 Knowledge Base Article 51

Article Number 51

Title Exported spreadsheet shows dates in place of times.

Created 4/6/1999 12:29:49 PM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 12:50:02 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When viewing an exported spreadsheet in Excel, the columns that should contain times contain dates
instead.

----- CAUSE -----

The Fleet Manager software exports both the date and time for these columns. However, Microsoft
Excel's default cell formatting causes only the date to be displayed.

----- SOLUTION -----

Change the cell formatting for these columns to show the date and time, or just the time as you
require.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1202
www.mixtelematics.com

1202
 1203
10.3.52 Knowledge Base Article 52

Article Number 52

Title Tacho data graph shows incorrect Road Speed values

Created 4/12/1999 4:08:01 PM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:21:15 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

The Tacho Data Graph shows incorrect Road Speed values when the system is set to use the
Imperial or US measurement systems.

----- MORE INFORMATION -----

When the system is set to use the Imperial or US measurement systems and a Tacho Data Graph is
generated, Road Speed is shown in Kilometers Per Hour (kph) instead of Miles Per Hour (mph).

----- CAUSE -----

This is caused by an error in the Fleet Manager 98 Client application.

----- SOLUTION -----

Upgrade your system to the latest available version of the Fleet Manager software (FM Fleet
Manager 2001 SR2 or later).

----- STATUS -----

This problem has been solved with version 3.00.0008 and later of the Fleet Manager Client.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM98

1203
www.mixtelematics.com

1203
 1204
10.3.53 Knowledge Base Article 53

Article Number 53

Title Fleet Manager 98 Timeline Displays Incorrectly (FM100)

Created 4/16/1999 4:02:36 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:20:00 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

When viewing an Activity Timeline for an FM100 Vehicle, sometimes the sub-trips are not displayed
correctly.

----- MORE INFORMATION -----

When viewing FM100 trips that have no depart time, the light blue sub-trip line from the previous trip
appears to continue from the previous trip, through the trip(s) that have no depart time, before ending.

For more information on this topic, see Knowledge Base Article 54.

----- CAUSE -----

This is caused by an error in the downloading of FM100 Trip Data into the Fleet Manager 98 Software.

----- SOLUTION -----

Upgrade to the latest available version of the Fleet Manager software (FM Fleet Manager 2001 SR2 or
later).

To fix any corrupt data already saved into the database, use the Clear Data function to remove the
corrupt data from the database and do a full download from the vehicle's plug.

----- STATUS -----

This problem has been solved with version 3.00.0008 and later versions of the Fleet Manager Client.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM98

1204
www.mixtelematics.com

1204
 1205
10.3.54 Knowledge Base Article 54

Article Number 54

Title Fleet Manager 98 Daily Trip Report has no Standing Time (FM100)

Created 4/16/1999 4:25:42 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:18:24 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

When doing a Daily Trip Report for an FM100 vehicle, the Standing Time column on the report
appears blank.

----- MORE INFORMATION -----

When an FM100 Trip has no Depart Time, this trip will appear on the Daily Trip Report with the
Standing Time column blank.

For more information on this topic, see Knowledge Base Article 53.

----- CAUSE -----

This is caused by an error in the downloading of FM100 Trip Data into the Fleet Manager 98 Software.

----- SOLUTION -----

Upgrade to the latest available version of the Fleet Manager software (FM Fleet Manager 2001 SR2
or later).

To fix any corrupt data already saved into the database, use the Clear Data function to remove the
corrupt data from the database and do a full download from the vehicle's plug.

----- STATUS -----

This problem has been solved with version 3.00.0008 and later of the Fleet Manager Client.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM98

1205
www.mixtelematics.com

1205
 1206
10.3.55 Knowledge Base Article 55

Article Number 55

Title Error During FM98 SR1 Install: 'Microsoft Data Access Components 2.0 is required.'

Created 4/19/1999 11:23:11 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:16:35 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

After installing the release version (version 2.10) of the FM Kienzle Fleet Manager 98 software from
the CD, and then attempting to install Service Release 1 (version 3.00), the above message is
generated.

----- MORE INFORMATION -----

The full version of the FM Kienzle Fleet Manager 98 installation program installs a component, called
"Microsoft Data Access Components 2.0" [MDAC]. When attempting to upgrade this to Service
Release 1, the software says that this component has not been installed.

----- CAUSE -----

This is caused by a later version of the above component being installed on the computer (Microsoft
Internet Explorer 5 [IE5], for example, installs version 2.1 of this component). The Fleet Manager 98
installation program specifically checks for "Microsoft Data Access Components" version 2.0.

----- SOLUTION -----

Upgrade to the latest version of the Fleet Manager software available (FM Fleet Manager 2001 SR2 or
later).

----- STATUS -----

This problem has been solved with version 3.00.0008 of the Fleet Manager Client. This fix has also
been included in all later versions of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1206
www.mixtelematics.com

1206
 1207
10.3.56 Knowledge Base Article 56

Article Number 56

Title Error 2004 occurs when generating a report

Created 4/20/1999 12:39:27 PM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 11:32:19 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When generating a very large report, an unexpected error 2004 (Out of Memory) occurs. No
description is provided for this error.

----- CAUSE -----

The system does not have enough memory available to generate the requested report.

----- SOLUTION -----

Try closing other applications to free up additional resources and/or try refining your selection criteria
to generate a smaller report.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

RELATED KBA'S: 74

1207
www.mixtelematics.com

1207
 1208
10.3.57 Knowledge Base Article 57

Article Number 57

Title Error -214721887 (3022) when downloading

Created 4/20/1999 5:30:19 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:14:26 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

When attempting to download from a green vehicle plug, error -214721887 is displayed.

----- MORE INFORMATION -----

Sometimes, when downloading from a green vehicle plug into the Fleet Manager software, the
following error is displayed:

-214721887 (0x80040E21): "The changes you requested to the table were not successful because
they would create duplicate values in the index, primary key, or relationship. Change the data in the
field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate
entries and try again."

This is also known as error 3022.

----- CAUSE -----

This is caused by a misinterpretation of data recieved from the plug during a download.

----- SOLUTION -----

Download the 32Kb ClearFM200RawEvents.exe and execute this file. PLEASE NOTE: This program
should only be used to fix this problem.

Upgrade your current system to the latest Fleet Manager available (FM Fleet Manager 2001 SR2 or
later).

Re-download the plugs for all vehicles, using the "Download All" option in the software.

----- STATUS -----

The cause of this problem has been solved with FM Kienzle Fleet Manager 98, SR1a and all later
versions of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM200 FM200e

1208
www.mixtelematics.com

1208
 1209
10.3.58 Knowledge Base Article 58

Article Number 58

Title Tacho data graph shows zero values for the auxilliary frequency input (F3)

Created 4/22/1999 1:03:57 PM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 12:53:37 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

The Tacho Data Graph displays zero values for the auxilliary frequency input (F3), even though the
F3 input is functioning correctly.

----- MORE INFORMATION -----

The FM200 and FM200e units have an auxilliary frequency input known as the F3 input. This input
can be connected to any source which generates electrical pulses and can be configured to measure
the frequency of pulses generated in Hz.

Version 3.00 (SR1) of the Fleet Manager software provides an enhancement which allows the F3
input to be configured to count the number of pulses generated during a sub-trip and associate the
pulses with a value. For example, the F3 input can be connected to a fuel flow meter. By counting the
number of pulses generated during a sub-trip, the quantity of fuel used during the sub-trip can be
derived.

----- CAUSE -----

Current versions of the Fleet Manager software configure the FM200 and FM200e unit to monitor the
F3 input with a resolution of 50 Hz (50 pulses per second). Some devices which generate electrical
pulses such as fuel flow meters generate far less that 50 pulses per second. Thus when a tacho data
graph is generated, the quantity of pulses generated during each 1 second interval if less than 50 is
displayed as 0.

----- STATUS -----

The Fleet Manager 2000 software will include an enhancement permitting the FM200 unit to be
configured to monitor the F3 input with a higher resolution.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM98 FM2000

1209
www.mixtelematics.com

1209
 1210
10.3.59 Knowledge Base Article 59

Article Number 59

Title Fleet Manager Installation Resets DCOM Configuration Settings

Created 4/26/1999 3:21:22 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 12:54:28 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1) or higher.

----- SUMMARY -----

When upgrading to a new version of the Fleet Manager software, DCOM Configuration settings
revert back to defaults.

----- MORE INFORMATION -----

The upgrade to a new version of the Fleet Manager software causes any DCOM Configuration
settings (Access Permissions, Server Names, etc.) that were specified for the previous version to
be deleted.

----- CAUSE -----

This is caused by the way in which the installation set "cleans up" un-needed data in the user's
system registry, caused by a previous installation of the Fleet Manager Software.

----- SOLUTION -----

Before running Fleet Manager install set over a previous version of the software, write down all your
DCOM Configuration settings relating to this product.

After the upgrade, ensure that these settings are as they were before the upgrade.

----- STATUS -----

This behaviour is a function of the Installation Set of version 3.00 and above, and is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1210
www.mixtelematics.com

1210
 1211
10.3.60 Knowledge Base Article 60

Article Number 60

Title How do I specify the order for .cri files in a Report Batch?

Created 4/26/1999 3:39:13 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 12:56:27 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1) and higher.

----- SUMMARY -----

When creating Report Batches, how do I specify which order the specified criteria files are generated
in?

----- SOLUTION -----

Criteria files are generated sequentially, in the order in which they were added to the batch. It is
important, then, when adding criteria files to a Report Batch, to add them in the order in which you
want them to be generated.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1211
www.mixtelematics.com

1211
 1212
10.3.61 Knowledge Base Article 61

Article Number 61

Title FM Kienzle Fleet Manager Software with Microsoft Office 2000

Created 5/10/1999 12:05:13 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 5/23/2003 11:43:44 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00.0008 (FMClient.exe version) or later

· FM Kienzle Fleet Manager 2000, all versions

· FM Fleet Manager 2001, all versions

· FM Fleet Manager 2002, all versions

Please note: This article applies only to the above versions of the Fleet Manager software product.
Versions prior to the above will fail when running in conjunction with Microsoft Office 2000.

----- SUMMARY -----

The above version of the Fleet Manager software has been extensively tested, when used in
conjunction with the Microsoft Office 2000 software package (http://www.microsoft.com/office), and
the findings listed below were reported.

----- MORE INFORMATION -----

1. If the FM Kienzle Fleet Manager Software is installed, and Microsoft Office 2000 has already
been installed on the target system, then both software packages will work without problems.

2. If, however, the Microsoft Office 2000 software is installed after the Fleet Manager software, the
following problems may be experienced:

When running the FMCreateDB.Exe utility (Please see the file "FMCreateDB Readme.txt" file,
included on the Fleet Manager CD), an "ActiveX Component can't create object" error (Error 429)
may occur.

When attempting to generate reports from within the Fleet Manager software, a General Protection
fault (Access Violation) error may occur in the FMReports server. (Or reports may seem to hang).

----- CAUSE -----

The problems reported in point (2) above result from a newer version of the Microsoft Data Access
Components, used by the Fleet Manager software, being installed by the Microsoft Office 2000
software.

----- SOLUTION -----

1212
www.mixtelematics.com

1212
 1213

If you are experiencing one or both of the problems described in point (2) above, then please re-
install the Microsoft Access Runtime setup from the Fleet Manager CD-ROM. You will find this on
the software CD, in a Access Runtime folder. (On the FMOffice or later CD this folder can be found
under the Setup Files section under the Fleet Manager software install section).

If this does not solve your problem, then it is likely that you installed Office 2000 after the Fleet
Manager software, and allowed the setup to "Remove previously installed Office components". If
this is the case, then you will need to completely remove Office 2000 from your computer, and re-
install the Fleet Manager software. Once the reports are seen to be working, you may re-install
Office 2000, and both software products will continue to work successfully.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FM2001 FM2002 Reports Hang

1213
www.mixtelematics.com

1213
 1214
10.3.62 Knowledge Base Article 62

Article Number 62

Title Driver Reports Not Available

Created 5/19/1999 11:27:53 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 12:58:02 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

If the software is installed, and "Driver Reporting Functions" are enabled, everything will appear to be
functioning correctly. However, when another user logs into the computer, using his/her own profile,
these reports will be disabled.

----- MORE INFORMATION -----

The FM Kienzle Fleet Manager 98 Client software is "profile specific". This means that specific
options selected for one user will not be selected for another.

----- CAUSE -----

The client software reads & writes settings from the "HKEY_CURRENT_USER" key in the Windows
System Registry. This key only ever applies to the user currently logged in to the computer.

----- SOLUTION -----

Each user should install the FM Kienzle Fleet Manager 98, while logged in using their profile. Note:
Absolute care should be taken in this case to ensure that exactly the same options for the installation
are selected by all users.

----- STATUS -----

This problem will be solved in the FM Kienzle Fleet Manager 2000 software product.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1214
www.mixtelematics.com

1214
 1215
10.3.63 Knowledge Base Article 64

Article Number 64

Title Cannot Save or Print Reports

Created 5/20/1999 10:10:16 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 8/2/1999 12:22:33 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

1. Clicking the "Save" button when previewing a report does nothing, and/or

2. Clicking the "Print" button when previewing a report displays a message box, with a yellow exclamation
mark within a triangle, but no text.

----- MORE INFORMATION -----

Some people have reported the above problem after upgrading their Fleet Manager 98 Software from
version 2.10 to SR1.

----- CAUSE -----

This problem is caused by an incompatibility with the Microsoft Common Dialog Controls file,
COMDLG32.DLL, which cause the Save and Print dialogs of the above form to fail to display.

----- WORKAROUND -----

Generate a report, so that this problem occurs. Then, exit the Fleet Manager software, and restart it. You
will now be able to Print and Save report files again, for the rest of the duration of the current session.
When next the computer is restarted, however, this problem will re-occur.

----- STATUS -----

This problem is under investigation.

------------------------------------------------------------------------------

KEYWORDS: FM98

1215
www.mixtelematics.com

1215
 1216
10.3.64 Knowledge Base Article 65

Article Number 65

Title Data Pro Service Online & Centre-Point Year 2000 Compliance (Y2K)

Created 5/21/1999 3:33:24 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/21/2002 11:14:13 AM

Last Modified By Wesley De La Harpe (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Data Pro Service Online

· Data Pro Centre-Point

----- SUMMARY -----

The Data Pro Service Online and Data Pro Centre-Point systems have been tested, and found to
function correctly under the conditions listed below, when the most current release (This is when the
version of the SOLUI.DLL component is at 2.05 or higher. If you are running Data Pro Centre-Point,
then this is when the version of the CPUI.DLL component is at 3.00 or higher) of the Service Online
or Centre-Point Server software is used. Please contact support@mixtelematics.com to get the latest
version of Centre-Point. More information about the Centre-Point product can be found on the CI
Development web site at http://www.mixtelematics.com

Please note that the Y2K Compliance status of any client machines cannot be guaranteed by Data
Pro Development (Pty) Ltd. Since client computers can use any Java and Frames capable Internet
browser, this browser needs also to be fully Year 2000 Compliant. It is also imported to ensure that
the computers themselves are all fully Y2K compliant.

----- SERVER SOFTWARE -----

The following areas of the Service Online and Centre-Point Server applications are affected by dates
and have been tested to ensure they function and/or display correctly:

· All “Last Modified On” and “Created On” dates of Organisations, Contacts, Service Requests, and
Knowledge Base articles.

· The “Birthday” field on the Contact Maintenance form.

· The “Anniversary” field on the Contact Maintenance form.

· Service Request logged dates.

· Calculation of Due Dates of Service Requests, as well as the Auto Escalation thereof.

· Dates of Last Actioned Comments.

· Calculation of Average Days of Service Requests in the system, as well as Average Days since
last actioned.

1216
www.mixtelematics.com

1216
 1217

· The various Query facilities, when querying on Birthday, Anniversary, Logged Date, Due Date,
Last Actioned Date, etc.

· System administrative functions: the definitions of non-working days, Auto Escalation Parameters,
etc.

----- TESTS CONDUCTED -----

Several tests have been conducted to ensure that the entire system will function correctly into the
twenty-first century. The system date of a server computer running Data Pro Service Online or
Centre-Point at the above versions, as well as the dates of two client computers running web
browsers, were set forward in order to run these tests.

Dates with a two-digit year

All functions within the software were tested to ensure that two-digit years are converted and stored
in the database correctly.

The 31st of December 1998 (31/12/1998)

The system was fully tested to ensure that the rollover from this year into next year is handled
correctly.

The 28th of February 1999 (28/02/1999)

The last non-leap year in the twentieth century was tested, to ensure that the system functions
correctly.

The 31st of August 1999 (31/08/1999)

The rollover from 31/8/99 to 1/9/99 was tested, to ensure that this date causes no problems.

The 31st of December 1999 (31/12/1999)

All functions within the system were tested to ensure that the rollover to the 1st January 2000 is
handled correctly.

The 29th of February 2000 (29/02/2000)

Many people are not aware that the year 2000 is a leap year. This is the case and all system
functions were tested to ensure that this date is considered valid and is handled correctly.

The 30th of April 2000 (30/04/2000)

This will be the first month of the year 2000 ending on a weekend. All system functions were tested
to ensure that this is handled correctly.

The 31st of December 2000 (31/12/2000)

This will be the last day of the year 2000. All system functions were tested to ensure that the rollover
to 1st January 2001 is handled correctly.

The 29th of February 2001 (29/02/2001)

Many people are under the impression that the year 2001 is a leap year. This is not the case and all
system functions were tested to ensure that this date is not considered valid.

The 31st of December 2001 (31/12/2001)

1217
www.mixtelematics.com

1217
 1218

This will be the last day of the year 2001, the end of the second year after the turn of the century. All
system functions were tested to ensure that the rollover to 1st January 2002 is handled correctly.

The 29th of February 2004 (29/02/2004)

The system was tested to ensure that it correctly interprets the year 2004 as a leap year.

------------------------------------------------------------------------------

KEYWORDS: SERVICE ONLINE CENTRE-POINT

1218
www.mixtelematics.com

1218
 1219
10.3.65 Knowledge Base Article 66

Article Number 66

Title Events Utilising the System Override Plug Do Not Work

Created 5/26/1999 6:03:15 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:09:14 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

If an event allows the system override plug to disable the buzzer and relay for that particular event, the
event will not work correctly.

----- MORE INFORMATION -----

When creating an event, you have the option of sounding the buzzer and/or enabling the relay after a
specified time. If either of these options are selected, you also have the option of specifying that, when
this event occurs, the System Override plug for the vehicle can be used to disable the buzzer and/or the
relay.

If an event is created in this manner, both the buzzer and/or the relay will fail to fire when the event
occurs.

----- CAUSE -----

This is caused by an error in the database creation/upgrade program, that is installed with SR1 of the
FM Kienzle Fleet Manager 98 software.

----- SOLUTION -----

Upgrade to the latest available version of the Fleet Manager software (FM Fleet Manager 2001 SR2 or
later).

----- STATUS -----

This problem has been solved with the SR1a update to FM Kienzle Fleet Manager 98, as well as all
later versions of the software.

--------------------------------------------------------------------------

KEYWORDS: FM98 FM200 FM200e

1219
www.mixtelematics.com

1219
 1220
10.3.66 Knowledge Base Article 67

Article Number 67

Title How To Create a Plug Dump

Created 5/31/1999 1:12:41 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 12/7/2005 9:28:49 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· All units , All software

----- SUMMARY -----

In many cases, when a problem is reported to Control Instruments MiX Telematics, relating to the
Fleet Manager software, MiX Telematics is unable to investigate without a Plug Dump of the vehicle
that may be causing the error.

----- MORE INFORMATION -----

A Plug Dump is a physical dump of all the memory on a code plug, in the form of a *.bin or *.ini file,
depending on the method that you use to create the dump - see below. This file can be used to
recreate the plug, as though the physical code plug was sent to us.

The latest FMDealer utility can be used to generate these plug dumps (as well as restore them.)

----- SOLUTION -----

The easiest way to generate a plug dump is to use the latest FMDealer utility.

1. Insert plug to be dumped into the download module connected to the computer where the plug
dump will be created.

2. Run the FMDealer utility.

3. From the menu items, select CODE PLUG -> DUMP PLUG

4. Enter a filename and save.

5. The saved file is a .bin file to be used for this plug.

You can download the latest FMDealer utility from www.FMfm.com website.

------------------------------------------------------------------------------

KEYWORDS: Plug Dump FMDealer FM2002 FM8

1220
www.mixtelematics.com

1220
 1221
10.3.67 Knowledge Base Article 68

Article Number 68

Title Over Speeding is shown as km/h on Event Export, but units are displayed as mph

Created 6/8/1999 8:24:06 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 8/2/1999 12:22:53 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager, version 3.00 (SR1) and below.

----- SUMMARY -----

On an exported Event report, the values for the Over Speeding event are being displayed in km/h, even
though the units are still displayed as mph.

----- CAUSE -----

This is caused by errors in the Fleet Manager Reporting database.

----- STATUS -----

This problem has been solved in the next release of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1221
www.mixtelematics.com

1221
 1222
10.3.68 Knowledge Base Article 69

Article Number 69

Title Incorrect column types in Excel exports

Created 6/9/1999 10:39:17 AM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 1:47:10 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When reports are exported to Excel files, some columns have the wrong data type.

----- MORE INFORMATION -----

When reports are exported to Excel file, some columns that contain numeric data are not formatted as
numbers. This means that calculations, such as totalling can not be done on these columns without
first using the "Text to Column..." function to make the column numeric.

----- CAUSE -----

The exporting of Excel data is done via a standard Microsoft Access function and it is unclear at this
time why the columns are given the wrong formatting.

----- SOLUTION -----

To work-around this problem the following can be done.

Instead of exporting to an Excel file, export a comma-separated value file using the default .csv
extension and specifying that the file be opened after exporting. As the .csv files are associated to
Excel by default, the file will open in Excel and the columns mentioned above will already be numeric.
The file can then be saved as an Excel file after adding column totals or making other modifications.

----- STATUS -----

This problem is under investigation.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1222
www.mixtelematics.com

1222
 1223
10.3.69 Knowledge Base Article 70

Article Number 70

Title Overflow Error When Adding or Viewing KB Article

Created 6/10/1999 8:26:45 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 1/11/2000 9:54:55 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Data Pro Service Online, version 2.05 and below.

----- SUMMARY -----

Sometimes, after adding a Knowledge Base article, or clicking to view a Knowledge Base article,
from within SOL, an "Overflow Error" is displayed.

----- MORE INFORMATION -----

The error message displayed is as follows:

An unexpected error occurred:

6: Overflow occurred in Routines.CleanupValue (Line 3495).

This problem occurs when the text in the Knowledge Base article you are trying to display consists
of more than 32767 characters (32Kb).

----- CAUSE -----

Data Pro Service Online, version 2.05 and below, only supports Knowledge Base articles with a
maximum length of 32Kb. If the article your are trying to add or view is longer than that, the above
error will occur.

----- SOLUTION -----

Rewrite the Knowledge Base article, so that the text consists of less than 32Kb.

----- STATUS -----

All releases of the Data Pro Centre-Point software, the successor to Service Online, will allow
Knowledge Base articles of up to 64 kilobytes in size. Any article larger than this will be truncated to
64kb.

------------------------------------------------------------------------------

KEYWORDS: SERVICE ONLINE CENTRE-POINT

1223
www.mixtelematics.com

1223
 1224
10.3.70 Knowledge Base Article 71

Article Number 71

Title OLEMSG32.DLL Fails to Register during Service Online & Centre-Point Installation

Created 6/10/1999 12:18:31 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 1/25/2000 5:11:06 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Data Pro Service Online, all versions

· Data Pro Centre-Point, all versions

----- SUMMARY -----

Sometimes, when installing the Data Pro Service Online or Centre-Point software onto the server
computer, a message box is displayed, saying that the OLEMSG32.DLL file failed to register.

----- CAUSE -----

This error is caused by the fact that Microsoft Windows Messaging has not yet been installed onto
the server computer. Some of Service Online and Centre-Point's mailer component files are
dependant on Windows Messaging being installed onto the computer.

----- SOLUTION -----

Install Windows Messaging, and then re-run the Service Online installation set.

If you are running Microsoft Windows NT or Microsoft Windows 95, then this component may be
found in the Add/Remove Programs applet, under the Windows Setup tab. If you are running
Microsoft Windows 98, then this component needs to be installed manually, from the Windows 98
CD-ROM at (Assuming that D:\ is the letter of your CD-ROM drive): D:\WIN98_SE\SETUP\TOOLS
\OLDWIN95\MESSAGE\INTL\WMS.EXE.

------------------------------------------------------------------------------

KEYWORDS: SERVICE ONLINE CENTRE-POINT

1224
www.mixtelematics.com

1224
 1225
10.3.71 Knowledge Base Article 72

Article Number 72

Title Error 105 When the software Loads

Created 6/10/1999 12:18:56 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 4/12/2000 4:05:54 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

On some computers, when loading the Fleet Manager software, error 105 is displayed.

----- CAUSE -----

This is caused by a version of Microsoft Windows 95 on the computer that has been upgraded from
Windows 3.x. During this upgrade process, the user is asked if he/she wants to enable "Long
Filename Support". If you answered "No" to this question, you will get this error. This is because the
Fleet Manager software uses Long Filenames for many of its dependant files.

----- SOLUTION -----

Install a fresh copy of the operating system onto the computer, this time enabling "Long Filename"
support. Then, re-install the Fleet Manager software.

----- STATUS -----

This behaviour is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1225
www.mixtelematics.com

1225
 1226
10.3.72 Knowledge Base Article 73

Article Number 73

Title New Events Not Visible on Timeline

Created 6/11/1999 9:59:58 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 2:00:52 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1) and later.

----- SUMMARY -----

When a new event is added to a vehicle, this new event does not automatically show up on the
Activity Timeline.

----- MORE INFORMATION -----

In previous versions of the Fleet Manager 98, whenever a new event was added to a vehicle, and
you subsequently requested an Activity Timline for that vehicle, the new event was displayed in the
graphical list of events. This is no longer the case (although all the events that occured for the
period still display as they should in the Detail Text portion of the Timeline).

----- CAUSE -----

Service Release 1 of the Fleet Manager 98 introduced a new feature of the Activity Timeline,
allowing you to select which events you would like to display for a vehicle. This feature can be
accessed from within the Timeline, by clicking the blue Exclamation Mark (!) icon on the toolbar.

For more information about this, and other new features in Service Release 1 of the Fleet Manager
98 software, please see KB#46: What's New in FM Kienzle Fleet Manager 98 version 3.00 (SR1).

----- SOLUTION -----

To display a new event for a vehicle on the Timeline, click this blue Exclamation Mark icon; or click
the View menu, and then select Events. Then, select all the events that you would like to display,
and click OK.

Please note that when the timeline is closed, these settings are saved, so that these same events
will be displayed the next time you open a vehicle of that type. Also note, then, that these settings
are saved per unit type (FM100, FM200, FM200e, FM2010) - so that each FM100 vehicle's timeline
will display the events that were displayed for the last FM100 vehicle's timeline, and so forth.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

1226
www.mixtelematics.com

1226
 1227

KEYWORDS: FM98 FM2000

1227
www.mixtelematics.com

1227
 1228
10.3.73 Knowledge Base Article 74

Article Number 74

Title Out Of Memory Errors in FM98 and FM2000

Created 6/17/1999 10:20:10 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 11:31:40 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1) and later

----- SUMMARY -----

Occasionally, when working within the Fleet Manager software, an Out of Memory error (Error 2004)
occurs.

----- MORE INFORMATION -----

The above error occurs most often while downloading data from a vehicle's green plug, into the Fleet
Manager 98 software. However, this error does occasionally appear when doing various tasks in the
software.

Cancelling and re-starting numerous downloads can aggrevate the problem.

----- CAUSE -----

The Microsoft database engine, used to access the Fleet Manager database file, allocates large
amounts of temporary disk space in order to complete various tasks.

If you are using 256k data plugs, the amount of disk space allocated during downloads, etc. is
particularly large. This space is freed again as soon as the relevant operation is completed.

If the your computer has multiple drives (e.g. C: and D:), there must be enough disk space on both
the drive where the database is located, and enough space on the drive containing the Windows
Temp path.

For example if the Fleet Manager software is installed on the D: drive, which may have several
gigabytes of free disk space, the system will still fail if the C: drive has limited disk space.

----- SOLUTION -----

Please try to free as much disk space as possible on all drives on your computer, and try the
operation again.

----- STATUS -----

Data Pro Development is investigating this problem, and hopes to prevent it from occurring in future
versions of the software.

1228
www.mixtelematics.com

1228
 1229

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

RELATED KBA'S: 56

1229
www.mixtelematics.com

1229
 1230
10.3.74 Knowledge Base Article 75

Article Number 75

Title KB Article Won't Print from Netscape Navigator

Created 6/17/1999 10:58:48 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 1:59:15 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Data Pro Service Online, SOLUI.DLL version 2.05.0001 and below

----- SUMMARY -----

When trying to print a Knowledge Base article from within Netscape Navigator, a "Data Missing"
message appears on the printout.

----- MORE INFORMATION -----

The printed message is as follows:

Data Missing

This document resulted from a POST operation and has expired from the cache. If you wish you can
repost the form data to recreate the document by pressing the reload button

Clicking the reload button from within Netscape Navigator has no effect.

----- CAUSE -----

This is caused by fact that the Netscape browser attempts to reload the page from the user's cache for
printing. Since all Knowledge Base articles have a special html directive, which makes them expire
from the cache immediately, Netscape has to download this page again from the web.

However, it is unable to do this because it no longer knows which KB number to open the page at.

----- SOLUTION -----

A reasonable workaround is to copy the text of the KB article into a Word Processor, and print it from
there. If this proves unacceptable, then you should use Microsoft Internet Explorer 4 or 5 to print
Knowledge Base articles from Service Online.

----- STATUS -----

This problem has been fixed in Data Pro Centre-Point, version 3.00 Please ask your administrator to
log a support request from the CI Development web site (http://www.mixtelematics.com), in order to
obtain the latest version of this product.

------------------------------------------------------------------------------

1230
www.mixtelematics.com

1230
 1231

KEYWORDS: SERVICE ONLINE CENTRE-POINT

1231
www.mixtelematics.com

1231
 1232
10.3.75 Knowledge Base Article 76

Article Number 76

Title New Events Not Being Recorded For Vehicle

Created 6/17/1999 11:42:26 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 1:50:27 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

When a new event is created or modified for a vehicle, occurrances of that event is not being
recorded by the vehicle.

----- MORE INFORMATION -----

If a new event, created or modified using Service Release 1 of the Fleet Manager 98 software, is
loaded into a vehicle that does not have the latest Device Drivers loaded, that event will not be
immediately recorded by that vehicle.

----- CAUSE -----

This is caused by the fact that an event was created using SR1 of the Fleet Manager 98 software,
but the device drivers in the vehicle are those included with a previous release of the software.

----- SOLUTION -----

The latest SR1 Device Driver (DDR) files must be uploaded into all vehicles. To verify that this is
done, insert the green vehicle plug for each vehicle into the download module, and click "Plug
Information". Scroll down the "Device Driver Information" box until you see a DDR named "FM
Kienzle FM200 Event Controller". Verify that the version number of this DDR is "12.1.8" or higher. If
this is not the case, then new Device Drivers need to be uploaded into that vehicle.

Once this has been done, re-upload the event configuration for all vehicles whose Device Driver
Information has changed. All events should now be recorded successfully.

----- STATUS -----

This functionallity is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM200 FM200e

1232
www.mixtelematics.com

1232
 1233
10.3.76 Knowledge Base Article 77

Article Number 77

Title Error 3167 while Downloading

Created 6/21/1999 12:02:00 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 1:57:35 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

During the "Processing" stage of an FM200 or FM200e download, error 3167 is displayed.

----- MORE INFORMATION -----

Before the error is displayed, but during the "Processing" phase of the download, it may be noticed
that, while no new trips are stored, some new events may be stored.

The error message displayed is as follows:

3167 (0x00000C5F): Record is deleted. occured in ProcessFM200Data.LoadFM200Events (Line

9800) The error has been logged.

----- CAUSE -----

If the "Swap Unit" function in the Fleet Manager 98 software is executed often, and you begin to get
error -2147217887 (See KB#78: Error -2147217887 Executing the Swap Unit Function) while
executing this function, then the above error will begin to occur. If so, then it means that some
internal errors have occured, which will prevent the correct processing of data from the green
vehicle plug, during a download.

----- SOLUTION -----

Upgrade to the latest version of the Fleet Manager software (FM Fleet Manager 2001 SR2 or later).

----- STATUS -----

This problem has been solved in the FM98 SR1a update and following releases.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM200 FM200e

1233
www.mixtelematics.com

1233
 1234
10.3.77 Knowledge Base Article 78

Article Number 78

Title Error -2147217887 Executing the Swap Unit Function

Created 6/21/1999 12:06:08 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:49:21 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

When executing the swap unit function for a specific vehicle, the above error is displayed. The
swap unit function may continue to function normally for other vehicles.

----- MORE INFORMATION -----

The error message displayed is as follows:

-214721887 (0x80040E21): "The changes you requested to the table were not successful because
they would create duplicate values in the index, primary key, or relationship. Change the data in the
field or fields that contain duplicate data, remove the index, or redefine the index to permit
duplicate entries and try again. occured in Vehicles.ResequenceData (Line 33280). The error has
been logged."

----- CAUSE -----

This is caused by an error in the Fleet Manager 98 server component.

----- SOLUTION -----

Upgrade to the latest available version of the Fleet Manager software (FM Fleet Manager 2001
SR2 or later).

----- STATUS -----

This problem has been solved with the FM98 SR1a Update release as well as subsequent versions
of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e

1234
www.mixtelematics.com

1234
 1235
10.3.78 Knowledge Base Article 79

Article Number 79

Fleet Manager 98/2000 software reports different driving times than FM100 software
Title
does.

Created 6/25/1999 8:40:34 AM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 11:06:59 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

Detailed trip reports generated by the Fleet Manager 98 or Fleet Manager 2000 software show
different driving times than a report for the same vehicle generated by the Fleet Manager 100
software.

----- CAUSE -----

This is not an error but comes about from the introduction of the concept of standing time in the
Fleet Manager 98 software.

In FM100 reports, the trip duration is the sum of driving time and idling time. However the concept
of standing time changes this so that in Fleet Manager 98/2000 reports, the trip duration is the sum
of driving time and standing time.

In FM98, the idling time can not be directly related to any other value as it partially overlaps both
the driving and standing times. Because of this, the Driving Time on the FM98 Trip Report may
include time spent Idling, while this is not the case in the FM100 Trip Report.

----- STATUS -----

There are no plans to change this as it has come about due to a change in the business rules of
the system.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM98 FM2000

1235
www.mixtelematics.com

1235
 1236
10.3.79 Knowledge Base Article 80

Article Number 80

Title The FM Kienzle Fleet Manager database is not a valid database file.

Created 6/25/1999 12:59:28 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:46:52 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When opening the FM Kienzle Fleet Manager software, the Splash screen is displayed, followed by
this message:

The FM Kienzle Fleet Manager database is not a valid database file. Please check the configuration
of the server computer.

----- CAUSE -----

This problem has the following possible causes:

1. Database read-only. The database file on the server (For example, FMServer.mdb) is marked as
Read-Only.

2. Database not found. The database file on the server (For example, FMServer.mdb) does not exist
in the location pointed to by the Fleet Manager Administration program.

3. System database not found. The system database file on the server (For example, Secure.mdw)
does not exist in the location pointed to by the Fleet Manager Administration program.

4. Database corrupt. The database file on the server (For example, FMServer.mdb) is corrupt.

----- SOLUTION -----

1. Using Microsoft Windows Explorer, locate the database file on the server. Click this file with your
right mouse button, and select Properties from the pull-down menu that appears. Ensure that the
Read Only attribute is not set.

2. Open the Windows Control Panel, and double-click the FM98 Administrator (or FM200
Administrator) icon. Lock the database, and double click Server Options. Double click Server
Database File, and select an existing Fleet Manager database.

3. Use the Fleet Manager Administrator, as above, to specify the location of the System Database
File.

1236
www.mixtelematics.com

1236
 1237

4. Using the Fleet Manager Administrator, you can attempt to Repair the database. If this proves
unsuccessful, you should restore the database from a recent backup. Failing that, please contact
CI Development support (By logging a Support Request from the MiX Telematics Web Site) for
assistance.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FMADMIN

1237
www.mixtelematics.com

1237
 1238
10.3.80 Knowledge Base Article 81

Article Number 81

Title Multiple Drivers Driving one Vehicle

Created 6/30/1999 8:53:18 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 1:00:34 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 100, all versions

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

· FM Kienzle Fleet Manager 2001, all versions

----- SUMMARY -----

Under certain circumstances, it is possible for the Fleet Manager software to indicate that the same
driver was driving two or more vehicles at the same point in time. This would typically be displayed on
the driver trip reports and/or driver Activity Timeline.

----- MORE INFORMATION -----

Although it is not physically possible for a driver to drive more than one vehicle at any point in time,
there are certain conditions which cause the Fleet Manager system to display information indicating
that this occurred. The following section describes two possible causes of this.

----- CAUSE -----

1. You may have initialised more than one blue Driver Code Plug for the same driver, in the Fleet
Manager Software.

2. It is possible that a driver, upon finishing his shift, will exit his vehicle without turning the ignition off,
and then get into another vehicle and identify himself as the driver. Meanwhile, another driver will
get into the previous vehicle (while it is still in Trip Mode) without identifying himself as a new driver.
This would cause the system to indicate that the same driver was driving both vehicles
simultaneously.

----- SOLUTION -----

1. While it is possible to initialise two driver plugs with the same driver ID, this should not be done. For
best results, each driver should have only ONE driver plug, and each driver plug should have a
unique ID number.

2. It is considered good practice for a driver to properly shut down the vehicle before exiting, and for
each driver to properly identify himself, whenever he drives each vehicle, using his unique blue
driver plug.

1238
www.mixtelematics.com

1238
 1239

----- STATUS -----

This behaviour is by design.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM200 FM98 FM2000

1239
www.mixtelematics.com

1239
 1240
10.3.81 Knowledge Base Article 82

Article Number 82

Title After SR1 Install, FM98 stops working

Created 6/30/1999 1:43:04 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 11:21:16 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (Service Release 1)

----- SUMMARY -----

After installing Service Release 1 of the FM Kienzle Fleet Manager 98, the program no longer
functions. The upgrading of the database at the end of the installation also fails.

----- MORE INFORMATION -----

If you have installed the production release of Service Release 1, after having installed one or more
pre-release (Beta) versions of SR1, without first un-installing, the above error will occur.

----- CAUSE -----

The latest SR1 database upgrade utility cannot upgrade databases created by certain Beta versions
of FM98 SR1. Because the database upgrade fails, the system will fail to function correctly.

----- SOLUTION -----

First un-install the pre-release version of Fleet Manager 98 from your computer. Next, make sure that
the FMServer.mdb database file is deleted. Finally, install the latest version of the Fleet Manager
software, reconfigure your organisation settings, and re-download from all vehicles.

----- STATUS -----

This behaviour is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FMCREATEDB

1240
www.mixtelematics.com

1240
 1241
10.3.82 Knowledge Base Article 83

Article Number 83

Title Fatal Error when Installing 16 bit Fleet Products under Windows 98

Created 7/9/1999 10:25:45 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 4/12/2000 4:55:33 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· CITAS 2010, all versions

· CI Data, all versions

· Shurlok EV100, all versions

· FM Kienzle Fleet Manager 100, all versions

----- SUMMARY -----

When attempting to install one of the above products under Windows 98, a "Fatal Error" occurs in
the Installation set.

----- MORE INFORMATION -----

At the end of the setup initialisation, a fatal error occurs in ISINST30 or _Ins0433._mp.

----- CAUSE -----

The above problem only occurs under the Microsoft Windows 98 Operating System, and happens
due to incompatibilities with certain drivers installed on the computer. In particular, it will occur if
you have the Microsoft IntelliPoint 2.2 software loaded.

----- SOLUTION -----

To solve this problem, please make sure that the offending software is not running during the
installation process. The easiest way to do this is to boot the computer in Safe Mode by following
these steps:

1. If the computer is currently switched on, Shut it down, by clicking the Start menu, selecting "Shut
Down", and clicking "Yes".

2. Switch the computer on, and wait until you see a message saying "Starting Windows 98". Press
the F8 key on your keyboard. A menu will appear.

3. Select the "Safe Mode" option, and press Enter.

4. Your computer will boot up in Safe Mode. You should now install the 16-bit software. When this
is complete, you should re-boot your computer again.

1241
www.mixtelematics.com

1241
 1242

----- STATUS -----

This problem is due to an error in the InstallShield installation software, used to create the setup
programs. It is beyond the control of Data Pro Development.

------------------------------------------------------------------------------

KEYWORDS: CITAS 2010 CIDATA EV100 FM100

1242
www.mixtelematics.com

1242
 1243
10.3.83 Knowledge Base Article 84

Article Number 84

Title Repeating Message Box occurs on Profile Edit

Created 7/19/1999 12:50:29 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:45:25 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

· FM Kienzle Fleet Manager 98, SR1a Update

----- SUMMARY -----

Entering an invalid range in the Profile configuration dialog boxes, and clicking Add causes the
system to Beep repeatedly for several seconds. After the beeping has subsided, a message box will
appear several times.

----- MORE INFORMATION -----

If you edit a profile range for a parameter at one of the three levels (Parameter Properties, Group
Parameter Properties, or Input Line Properties), and enter an invalid value, the above situation will
occur. For example, editing or adding a value between 120 and 140, and making it 160.

The message displayed in the message box is as follows:

This value would cause overlapping ranges. Please restrict this value to between [x] and [y].

(Replace [x] and [y] with the upper and lower values of the profile range that you are trying to insert
into.

----- CAUSE -----

This is caused by an error in the Fleet Manager Client software.

----- WORKAROUND -----

Always press the ENTER key on your keyboard after editing a profile value, before clicking Add to
add a new value.

----- SOLUTION -----

Upgrade to the latest available version of the Fleet Manager software (FM Fleet Manager 2001 SR2
or later).

----- STATUS -----

This problem has been solved in the FM98 SR1b update, as well as the FM Kienzle Fleet Manager

1243
www.mixtelematics.com

1243
 1244

2000 software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 MSGBOX

1244
www.mixtelematics.com

1244
 1245
10.3.84 Knowledge Base Article 85

Article Number 85

Title Error 3026 on Compact

Created 7/19/1999 2:40:55 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 1:54:55 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When trying to compact the Fleet Manager Database, error 3026 is displayed.

----- MORE INFORMATION -----

If you double click the "Compact" option in the FM Kienzle Fleet Manager Administrator program, error
3026 is displayed after a while.

----- CAUSE -----

Error 3026 means that there is not enough free disk space to perform the compact. You must have at
least double the amount of free disk space as the current size of the Fleet Manager Database
(FMServer.MDB) in order to perform a compact.

----- SOLUTION -----

Free up more disk space by uninstalling un-used programs, and deleting uneccessary files.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FMADMIN FM2000

1245
www.mixtelematics.com

1245
 1246
10.3.85 Knowledge Base Article 86

Article Number 86

Title Error 52 or 53 when trying to save a Criteria file

Created 7/20/1999 1:21:17 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:12:23 PM

Last Modified By Tony Gois (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

When trying to save a criteria file for any report or graph, either error 52 ("Bad file name or number")
or error 53 ("File not found") is displayed.

----- MORE INFORMATION -----

The above errors are displayed when the FM Kienzle Fleet Manager Client is in the French
(Français) language.

When running under Microsoft Windows NT, the error message displayed is as follows:

(52) Bad file name or number occurred in frmCriteria.cmdSave_Click

and when running under Microsoft Windows 95 or Microsoft Windows 98, the error message
displayed is as follows:

(53) File not found occurred in frmCriteria.cmdSave_Click

----- CAUSE -----

This is caused by an error in the French (Français) Client language file.

----- SOLUTION -----

Download the (60 Kb) ftp://ftp.centre-point.com/KBase/FraCriFix.Exe file. Execute this file, and
extract it's contents into your Fleet Manager directory (Typically C:\Program Files\Fleet Manager).
(Be sure to exit the FMKienzle Fleet Manager 98 software before doing this.)

----- STATUS -----

This problem will be fixed in the next release of the Fleet Manager 98 software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1246
www.mixtelematics.com

1246
 1247
10.3.86 Knowledge Base Article 87

Article Number 87

Title Data for Events defined on one PC not being stored on another

Created 7/28/1999 12:57:44 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 1:58:08 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

If you define a custom event in the Fleet Manager software, data for that event will only be
downloaded correctly into the database in which it was defined.

If custom event data is downloaded into another (different) database or computer, the data will not
be stored correctly and may result in meaningless data being stored.

----- MORE INFORMATION -----

The Fleet Manager software allows you to define any number of custom events, to be monitored by
your FM200 or FM200e units. If you make use of this feature, it is important that you always
download data into the same Fleet Manager database in which such custom events were defined.

----- CAUSE -----

The Fleet Manager software identifies each event in the database using a unique identifier (ID
number). This ID number is assigned when the event is created, and is not related in any way to the
description or definition of the event.

It is highly unlikely that any given custom event will have the same ID number as the "same" event
created in another database. It is also possible that totally unrelated events in two databases will
have the same ID numbers.

When downloading data, the Fleet Manager software ignores unrecognised event IDs. This behavior
can cause confusion and lead to the incorrect perception that data has been lost.

If unrelated custom events in both databases have the same ID numbers, event data will be
recorded against the incorrect event definition.

For example:

I create an event called "Door open" in my Fleet Manager database and configure one of my FM200
units to monitor this event. At the time that the event is created, the Fleet Manager software
allocates an ID number to the event.

1247
www.mixtelematics.com

1247
 1248

I create an identical event in a different Fleet Manager database. The Fleet Manager software
allocates a different ID number to this event.

When I download from my FM200 green plug (initialised using the first database) into the second
database, the "Door open" events have an unrecognised ID number and are ignored.

----- SOLUTION -----

Ensure that you always download a vehicle's data into the same Fleet Manager database used to
initialise the green vehicle plug.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1248
www.mixtelematics.com

1248
 1249
10.3.87 Knowledge Base Article 88

Article Number 88

Title Tacho Data Recorded While Vehicle is Stationery

Created 7/28/1999 1:42:18 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 1:59:32 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1) and below.

----- SUMMARY -----

Under certain circumstances, the tacho data you require may not be available.

----- CAUSE -----

The Fleet Manager 200 unit has the abilty to record a large volume of tacho data (the values of
the units inputs on a second-by-second basis). The unit has sufficient capacity to retain several
months of tacho data under normal circumstances.

The Fleet Manager 200 unit records tacho data whilst the vehicle is stationery, as well as whilst
it is engaged in a trip. This is by design. If the one or more of the unit's inputs are connected to
a constantly changing voltage source (for example a "normally high" voltage source), the unit
will continuously record tacho data, even though the vehicle is not in use.

This could result in the unit eventually overwriting tacho data eventhough the vehicle is not in
use.

----- SOLUTION -----

Tacho Data should be downloaded as soon as possible, after it has been established that such
data is required.

In addition, caution should be excercised when defining the Tacho Configuration of units to
avoid meaningless data being recorded unecessarily.

Where possible, input lines should be connected to "normally zero" voltage sources, as
"normally high" voltage sources continuosly fluctuate as current is drawn by devices connected
to the vehicle's electrical system.

----- STATUS -----

The FM Kienzle Fleet Manager 2000 software will include a feature, allowing you to specify
whether or not you would like the unit to record Tacho Data for various Inputs while the vehicle
is not engaged in a trip.

------------------------------------------------------------------------------

1249
www.mixtelematics.com

1249
 1250

KEYWORDS: FM98 FM200 FM200e FM2000

1250
www.mixtelematics.com

1250
 1251
10.3.88 Knowledge Base Article 89

Article Number 89

Title The 'Elapsed Time' reported for an Event Occurrance is Incorrect

Created 7/28/1999 1:55:36 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 2:05:08 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

Sometimes, on the Event Report and the Timeline, the total elapsed time for an event will appear to
be incorrect.

----- CAUSE -----

Since the Fleet Manager 200 unit can only begin recording events after they have been true for at
least 1 second, it is possible that each event recorded will actually appear to have occurred for a
second LESS than it actually did.

While this is usually unnoticable, it can have a substantial affect on the total columns for the various
reports.

----- SOLUTION -----

Bear in mind at all times that any given event will take at least 1 second to become True.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FM200 FM200e

1251
www.mixtelematics.com

1251
 1252
10.3.89 Knowledge Base Article 90

Article Number 90

Title Cancelling Reports 'Hangs' the system

Created 7/29/1999 8:38:42 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 2:06:20 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When generating a large Report, and clicking "Cancel" before the "Generating" stage, the
computer will appear to "hang".

----- MORE INFORMATION -----

When you request a report, there are four steps displayed on the Status dialog before the report
is finished generating. (There may be more or less, depending on the type of report) These are,
typically:

· Requesting Report

· Report Queued

· Extracting Data

· Generating

If you cancel a report before the final step, it may take a long time to cancel, depending on the
size of the report, possibly creating the impression that the software has stopped responding.

----- CAUSE -----

When a report is generated, the Fleet Manager Reports Server (FMReports.Exe) instructs the
Microsoft Access Runtime (A technology on which the databases in the software are based) to
execute various "queries" - instructions for Access to read the contents of the database, and
return specific information.

While Access is running these queries, it is unable to respond to requests from the Fleet
Manager Client, such as the request to "Cancel" a report. The Cancel request will then be set
aside, for Access to respond, when it is done executing the query.

This may take several minutes, depending on the size of the report to be generated.

1252
www.mixtelematics.com

1252
 1253

----- SOLUTION -----

When you cancel the generation of a report, wait for the report to cancel successfully before
requesting the generation of another report. This may take several minutes.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1253
www.mixtelematics.com

1253
 1254
10.3.90 Knowledge Base Article 91

Article Number 91

Title Managing Large Databases with FM98 and FM2000

Created 8/11/1999 9:40:42 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 5/25/2000 10:10:14 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

Some customers have encountered problems such as insufficient disk space or lack of
memory, when the Fleet Manager server database file (FMServer.MDB) becomes very large.

----- SOLUTION -----

When you experience problems as a result of your Fleet Manager server database file
becoming very large, you should consider using the "Clear Data" facility located on the
"Advanced" tab of the "Organisation Properties" dialog to remove unneeded data from the
database. After utilising this function, the "Compact Database" facility in the Fleet Manager
Administrator utility should be used to reduce the physical file size of the database file and free
up disk space.

Note: The "Clear Data" facility permanently removes data from the database. If you need to
retain historical data, the following steps should be taken:

1. At the end of each month (or other reasonable period), use the Fleet Manager Administrator
utility to backup the current Fleet Manager database.

2. Rename the backup copy of the database to the name of the corresponding period (e.g.
January-1999.mdb, February-1999.mdb, etc.)

3. Use the "Clear Data" facility to remove all data on or before the end of the period.
Remember to use the "Compact Database" facility to free up disk space.

Following the above three steps on a regular basis, you will always have a current, up-to-date
database, and historical data stored in seperate databases. Whenever necessary, you can use
the Fleet Manager Administrator utility to point to one of databases containing historical data.
After viewing your historical data, be sure to point the Server Database Path back to the
current database.

NOTE: When viewing historical databases, care should be taken to ensure that you do not
download into the wrong database. All downloading should only be done into the current
(working) database.

1254
www.mixtelematics.com

1254
 1255

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FMADMIN

1255
www.mixtelematics.com

1255
 1256
10.3.91 Knowledge Base Article 92

Article Number 92

Title Max RPM Shows Higher than RPM on Tacho Graph

Created 8/11/1999 10:15:31 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 2:07:49 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When viewing a Report or the Activity Timeline, the "Maximum RPM" value shows up as a
different value to the maximum RPM value for the same period on the Tacho Graph.

----- MORE INFORMATION -----

The above concern is most common with the Engine RPM Input, but could also occur with the
Maximum Speed etc.

If you open the Activity Timeline, and click on the Trip, then scroll down the end of the text details
area, you will see an entry for "Maximum Engine RPM". If you select the trip in question, and
generate a tacho graph, the value for the highest point on the graph can be lower than the value
reported on the Activity Timeline.

----- CAUSE -----

The Fleet Manager 200 and FM200e units are able to record tacho data many times during a one
second interval. If, at the end of any given one second cycle, there is more than one recording of
any given input, the unit stores the average of all data recorded in that second. This average, at
the highest point of the Tacho Graph, may consequently be much lower than the "Maximum RPM"
reported by the software.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FM200 FM200e

1256
www.mixtelematics.com

1256
 1257
10.3.92 Knowledge Base Article 93

Article Number 93

Title Max RPM Shows Lower than RPM on Tacho Graph

Created 8/11/1999 10:22:05 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 2:09:21 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When viewing a Report or the Activity Timeline, the "Maximum RPM" value shows up as a different
value to the maximum RPM value for the same period on the Tacho Graph.

----- MORE INFORMATION -----

The above concern is most common with the Engine RPM Input, but could also occur with the
Maximum Speed, etc.

If you open the Activity Timeline, and click on the Trip, then scroll down the end of the text details
area, you will see an entry for "Maximum Engine RPM". If you select the trip in question, and
generate a tacho graph, the value for the highest point on the graph can be higher than the value
reported on the Activity Timeline.

----- CAUSE -----

The Fleet Manager 200 and FM200e units are only capable of recording events that have been true
for more than 1 second. However, when it records Tacho Data, it can record data many times during
any given second.

The "Maximum RPM" displayed is actually a specialised event which the FM200 and FM200e units
are set up to record automatically. This event is based on the highest RPM achieved by the vehicle.
However, because the unit can only record events after they have been true for 1 second, it is
possible that the "Maximum RPM" recorded will appear to be less than the value on the highest
point of the Tacho Graph (which is recorded continuously).

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FM200 FM200e

1257
www.mixtelematics.com

1257
 1258
10.3.93 Knowledge Base Article 94

Article Number 94

Title FM100 Idle Configuration Incorrect

Created 8/12/1999 3:07:24 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:42:26 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

After updating an FM100 plug's configuration from within the Fleet Manager 98 software, the
Excessive Idle and Idle events will occur in the vehicle regardless of the value of the Road
Speed parameter.

----- MORE INFORMATION -----

When the above problem occurs, you will see that the "Idle" time on the Fleet Manager Trip
Report will be unusually close to the "Duration" reported.

----- CAUSE -----

This problem is caused by incorrect interpretations of FM100 event configurations from with the
Fleet Manager 98 software.

----- WORKAROUND -----

The FMLite software can be used to update the configuration of your FM100 vehicles.
Download the latest version of the FM Fleet Manager Lite software from http://www.
mixtelematics.com.

----- SOLUTION -----

Upgrade to the latest available version of the Fleet Manager software (FM Fleet Manager 2001
SR2 or later).

----- STATUS -----

This problem has been solved with the SR1a Update for Fleet Manager 98 as well as later
versions of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM100

1258
www.mixtelematics.com

1258
 1259
10.3.94 Knowledge Base Article 95

Article Number 95

Title 'Invalid Use of Null' Trying to add/modify a Service Request

Created 8/16/1999 1:17:45 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:39:53 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Data Pro Service Online, version 2.05 (SOLUI.DLL version 2.05.0000) or below.

----- SUMMARY -----

When attempting to add or edit a Service Request, an unexpected "Invalid Use of Null" (Error 94)
may occur.

----- MORE INFORMATION -----

The error message displayed is as follows:

An unexpected error occurred:

94: Invalid use of Null occurred in Section.BuildComboBox (Line 2795).

----- CAUSE -----

This error can occur when trying to add or modify a Service Request record when your administrator
has edited the priviledges in such a way that the "All Contacts" Contacts group in Service Online
does not have permission to log requests with any Service Request Status.

----- SOLUTION -----

Ask your administrator to ensure that the "All Contacts" group has permission to log Service
Requests with at least one status. (Usually "New Request", the default.)

----- STATUS -----

This problem has been solved in version 3.00 of the Data Pro Centre-Point software. Please ask
your administrator to log a Service Request from the CI Development web page at http://www.
mixtelematics.com, in order to obtain the latest version of this product.

------------------------------------------------------------------------------

KEYWORDS: SERVICE ONLINE CENTRE-POINT

1259
www.mixtelematics.com

1259
 1260
10.3.95 Knowledge Base Article 96

Article Number 96

Title Installation Fails on Windows 98 Second Edition (Win98 SE)

Created 8/17/1999 2:33:54 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/30/2000 10:48:18 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

----- SUMMARY -----

The installation of the Fleet Manager 98 fails while trying to install DCOM98 onto a computer
running Microsoft Windows 98, Second Edition.

----- MORE INFORMATION -----

The setup program launches the DCOM98 setup program, which displays a message, stating that
"A newer version of DCOM98 is already installed. Please uninstall the current installation of DCOM."
After recieving this message, the setup launches the MDAC setup, which restarts the computer, and
then starts the FM98 setup again from the beginning. Trying to run the Lite version of the Fleet
Manager 98 installation program says that DCOM98 is required.

For more information about the cause of this problem, please consult the Microsoft KB Article at
http://support.microsoft.com/support/kb/articles/q236/3/54.asp.

----- CAUSE -----

The installation set for Fleet Manager 98 checks for a specific version of DCOM98 on the target
machine, and Windows 98 Second Edition has an older version number than the one that it is
looking for. This causes the Fleet Manager 98 setup to assume that it needs to install DCOM, which
fails to install, because the version installed by Win98 SE is actually a newer version.

----- SOLUTION -----

The above Microsoft Knowledge Base Article describes a new version of DCOM98, version 1.3.
Read the above article, and then download and install this new version. You should now be able to
install the Fleet Manager 98 software.

----- STATUS -----

This problem has been solved in the first release of the Fleet Manager 2000 software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1260
www.mixtelematics.com

1260
 1261
10.3.96 Knowledge Base Article 97

Article Number 97

Title Error on Clear Data and Delete (The data you tried to update is in use...)

Created 9/1/1999 8:34:24 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:33:36 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1) and below.

----- SUMMARY -----

When trying to clear large amounts of data out of the Fleet Manager 98 database, the above error
may occur. The clear data function may appear to be working correctly, but after some time, it may
fail with this error.

The above error also manifests itself if you attempt to delete a Site or Configuration Group, which
contains many vehicles, with large volumes of data.

----- MORE INFORMATION -----

The error message displayed is as follows:

"The data you tried to update is in use by another process, and cannot be updated now"

----- CAUSE -----

This is caused by errors in the software when dealing with extremely large volumes of data.

----- SOLUTION -----

A workaround to this problem would be to only clear data for a few vehicles, for a short period at a
time. This way, it is possible to eventually have all the required data cleared out of the database.

Alternatively, delete the vehicles from the Site or Configuration Group one at a time.

This problem has been solved in later versions of the Fleet Manager software. Please upgrade to
the latest available version (FM Fleet Manager 2001 SR2 or later).

----- STATUS -----

This problem has been solved with the SR1a Update for Fleet Manager 98 and has been included
in the latest available Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM98

1261
www.mixtelematics.com

1261
 1262
10.3.97 Knowledge Base Article 98

Article Number 98

Title Error 324 on Download

Created 9/1/1999 9:05:55 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:32:21 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1) and below.

----- SUMMARY -----

When doing a full or quick download from an FM200 plug, error 324 may be displayed, during or at
the end of the "PreProcess" phase of the download.

----- MORE INFORMATION -----

The error message is as follows:

"324 (0x00000CAE) Operation not supported in transactions. occured in FM200Data.PreProcess

(Line 4840)."

----- CAUSE -----

This is due to errors in the Fleet Manager Download component (FMDownload) when trying to deal
with certain types of data returned by the FM200 Data Plug.

----- SOLUTION -----

This problem has been solved with the SR1a Update for Fleet Manager 98, and has been included
in later version of the software.

Please upgrade to the latest available version of the Fleet Manager software (FM Fleet Manager
2001 SR2 or later).

----- STATUS -----

This problem has been solved in the FM Kienzle Fleet Manager 2000 software release.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FM200 FM200e

1262
www.mixtelematics.com

1262
 1263
10.3.98 Knowledge Base Article 99

Article Number 99

Title Rules for Creating and Upgrading Fleet Manager Databases

Created 9/1/1999 9:55:34 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 11:49:02 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.10 (SR1a) and above (FMServer.exe version).

----- SUMMARY -----

When creating or updating a Fleet Manager database, there are many rules relating to the amount
of free space that is required. This affects both the hard drive on which the database is/will be
located, as well as the hard drive on which the temporary Windows files are stored. (The "TEMP"
and "TMP" environment variables.)

----- The "TEMP" and "TMP" variables -----

These Windows system variables instruct Windows where it should place its temporary files, for
use during various tasks. An explanation of how to set these variables follows:

For Microsoft Windows 95 or 98

Edit the Autoexec.bat file, located in the root directory of your main boot partition. Set the "TEMP"
and "TMP" variables to the directory of your choice, and reboot the computer.

For example, to set the Windows temporary path to D:\Temp, add the following lines to the
Autoexec.bat file:

SET TEMP=D:\Temp

SET TMP=D:\Temp

For Microsoft Windows NT

Open the System properties dialog. This is achieved by clicking Start|Settings|Control Panel, and
then double-clicking the System icon.

Then, click the Environment tab, and set the "TEMP" and "TMP" variables for the local user to the
path of your choice (For example, D:\Temp). Note: Under Microsoft Windows NT, this value is
specific to the CURRENT USER, and you should therefore repeat this process for each user who
will be using the Fleet Manager software.

----- MORE INFORMATION -----

The rules governing the free space requirements were previously implied rules, and problems
would arise if these weren't followed. Begining with SR1a, the database creation/upgrade program

1263
www.mixtelematics.com

1263
 1264

validates this information for you. The rules are as follows:

· If you are creating a new database, which will reside on the same disk drive or partition as the
temporary location, a minimum of 10 MB of free disk space is required on the target drive, in
order to complete the creation.

· If you are creating a new database, which will reside on a different drive to that of the temporary
location, you need a minimum of 6 MB of free space on the drive where the database will be
created, and a minimum of 3 MB of free space on the temporary drive.

· If you are upgrading an existing database, which resides on the same drive as the temporary
location, you need a minimum of three (3) times the size of the database, in free space, on the
target drive.

For example, if your Fleet Manager database is 50 MB in size, and is located in "C:\Program Files
\Fleet Manager", and your temporary location is "C:\Windows\Temp", then you need at least 150
MB of free disk space in order to complete the upgrade.

· If you are upgrading an existing database, which is located on a different drive to that of your
temporary location, then you need at least double the size of the database in free space on the
target drive. In addition, you also need at least 1 and a half times the size of the database in free
space on the temporary drive.

For example, if your Fleet Manager database is 50 MB in size, and is located in "D:\Fleet Manager",
and your temporary location is "C:\Windows\Temp", then you need at least 75 MB of free disk
space on the C:\ drive. In addition, you also need at least 100 MB of free disk space on the D:\
drive.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FMCREATEDB

1264
www.mixtelematics.com

1264
 1265
10.3.99 Knowledge Base Article 100

Article Number 100

Title Errors when attempting to backup database

Created 9/3/1999 1:36:24 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/30/2000 10:52:43 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

Under some circumstances, when trying to backup your Fleet Manager Database using the Fleet
Manager Administrator program, various errors may be displayed. These errors are displayed after
you click OK on the dialog that asks you for backup locations.

----- MORE INFORMATION -----

Some errors that may occur are as follows:

52: Bad file name or number

Other miscellaneous errors relating to insufficient disk space, not being able to find paths, etc.

----- CAUSE -----

This is typically caused by attempting to backup your database to a floppy disk, where the disk is
write-protected, there is insufficient disk space on the disk, there is no disk in the drive, or the disk
is corrupt.

However, it could also occur when trying to back up to a hard disk, when there is a problem with
the disk, or (more commonly) not enough disk space on the hard drive.

----- SOLUTION -----

If you are trying to backup to a floppy disk, check the following:

· Is the disk correctly inserted in the drive, and the door closed?

· Is the disk write-protected?

· Is there enough free disk space on the disk, and/or is the database itself to large to fit on a
floppy disk?

· Can you format the disk?

If trying to backup to a hard drive, make sure that there is enough disk space for the database,
and that the hard drive itself is not corrupt. If the problem persists, consult your hardware support

1265
www.mixtelematics.com

1265
 1266

personnel.

----- STATUS -----

The Fleet Manager 2000 software release will include "friendly messages", telling you that the disk
is write protected, there is not enough free space, etc.

------------------------------------------------------------------------------

KEYWORDS: FM98 FMADMIN FM2000

1266
www.mixtelematics.com

1266
 1267
10.3.100 Knowledge Base Article 101

Article Number 101

Title Activity Timeline Statistics Don't Display Correctly

Created 9/3/1999 5:28:02 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 1:07:54 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1) and below

----- SUMMARY -----

Occasionally, it may be observed that the statistics block of Activity Timeline (for Maximum Speed,
Average Speed and Distance) will not display correctly.

----- MORE INFORMATION -----

The above statistics may appear "chopped off", or may not display at all.

----- CAUSE -----

This is caused by the Windows font size setting set to "Large Fonts". Because the Timeline uses the
Windows default font, it does not cater for this font being larger than normal.

----- SOLUTION -----

In the "Display Properties" of the computer (Right click the Desktop, and click "Properties"), select
Settings. In the "Font Size" combo box, select "Small Fonts". This will solve the problem.

----- STATUS -----

This has been solved in the FM Kienzle Fleet Manager 2000 software release.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1267
www.mixtelematics.com

1267
 1268
10.3.101 Knowledge Base Article 102

Article Number 102

Title Not a valid snapshot file

Created 9/6/1999 12:22:09 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 11:51:52 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When attempting to open a report, an error is displayed saying that the report file you are trying to
open is not a valid snapshot file.

In this case, an error message, stating:

[Path\Filename.snp] is not a valid snapshot file

appears on the screen.

----- MORE INFORMATION -----

If you are opening a saved report, or you are running in Client/Server mode, and a report has just
finished generating, and is waiting to be displayed, the above error may occur. It may occur if you
have no printers installed on the computer from which you are trying to open the report. To verify this,
try to open the file from within Windows Explorer, using the Microsoft Snapshot Viewer. You should
recieve a message, stating that no printers have been installed.

----- CAUSE -----

This is due to the fact that the Microsoft Snapshot Viewer requires that a printer be installed, in order
for it to calculate the format in which to display the snapshot. When the Fleet Manager Software
attempts to open this report, the snapshot viewer control incorrectly reports an unexpected error,
which the software reports as an invalid snapshot file.

----- SOLUTION -----

Install a printer in your computer, so that you will be able to view reports.

----- STATUS -----

This is a function of the Microsoft Snapshot Viewer control, used to display reports inside the Fleet
Manager software. As such, it is beyond our control.

------------------------------------------------------------------------------

1268
www.mixtelematics.com

1268
 1269

KEYWORDS: FM98 FM2000

1269
www.mixtelematics.com

1269
 1270
10.3.102 Knowledge Base Article 103

Article Number 103

Title Parking time calculation on detailed trip reports

Created 9/13/1999 5:05:30 PM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:16:57 PM

Last Modified By Tony Gois (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

This article explains how parking times on detailed trip reports are derived.

----- MORE INFORMATION -----

Two distinct sets of parking times are reflected on detailed trip reports.

1. Detail Lines

Parking times on detail lines are reflected as the time elapsed between the start of the trip and
the end of the previous trip.

2. Summary Lines

Parking times on daily summary lines are derived by a fairly complex algorithm but it can
generally be said that parking time is 24 hours less the sum of driving and standing times.

The exception to this rule occurs when trips start before midnight and end after midnight. Driving
and standing times are credited to the day in which the trip started and therefore such a day
would have a sum of driving, standing and parking time that exceeds 24 hours. Likewise a day
that includes part of a previous day's trip would have a sum of driving, standing and parking time
that is less than 24 hours.

Where there are a number of these days with non-standard times, it is possible to total the
driving, standing and parking times for these days and arrive at a multiple of 24 hours that equals
the non-standard days. The snapshot file at ftp://ftp.centre-point.com/KBase/kb103a.snp
demonstrates this, with 15 May having a daily total of 24:40:18 and 16 May having 23:19:42
giving a total of 48:00:00.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 Driver Report Parking Time

1270
www.mixtelematics.com

1270
 1271
10.3.103 Knowledge Base Article 104

Article Number 104

Title FM200(e) Events appear permanently 'on' in Activity Timeline

Created 9/20/1999 12:49:31 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 1:11:56 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When viewing a detailed (Record each start and end) FM200 or FM200e event in the Activity
Timeline, the coloured bar representing the event may appear continously, even on days where no
trips where recorded.

----- MORE INFORMATION -----

An event displayed in such a way may stop occuring briefly, for a day. If so, then you will observe a
jagged edge for that event in the middle of the day, followed by a new start and end ocurrance. Other
legitimate occurances of that event may be displayed correctly for the remainder of the day in
question, before the event "begins" again on the following day.

----- CAUSE -----

This is caused by the fact that the start time for a given event may be downloaded into the software,
but no end is downloaded. This typically occurs when, for example, you download from the unit while
the driver door is open.

Furthermore, the end time for that event may in fact never be downloaded, but other occurances of
the event are downloaded in the mean time.

----- SOLUTION -----

Determine when it is that the event first started, and clear all data for that vehicle, for that day, out of
your Fleet Manager database. The Activity Timeline will now display that event correctly.

----- STATUS -----

It is certainly possible for this to happen within the Fleet Manager 200 hardware unit, and the manner
in which it is displayed on the Activity Timeline is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FM200 FM200e Events

1271
www.mixtelematics.com

1271
 1272
10.3.104 Knowledge Base Article 105

Article Number 105

Title Idle Occurring Outside of a Trip

Created 9/23/1999 12:31:02 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 2:19:28 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

It may sometimes be observed, on the Activity Timeline and Reports, that the "Idle" events occur for a
vehicle, even when the vehicle is outside of "Trip Mode".

----- MORE INFORMATION -----

This behaviour will typically be observed under the following conditions.

1. The "Engine RPM" parameter has been disconnected from the F2 Input, in the vehicle's "Input
Configuration".

2. The driver chooses not to identify him/herself when entering the vehicle, and instead just allows
"Unknown Driver" to be passed as the driver.

----- CAUSE -----

The reason for this is the definition of the Idle event, and the conditions required to record a Trip
Start.

The "Idle" event is defined as follows, at the vehicle level (When Engine RPM is not connected):

Ignition On = True AND

Road Speed < 5 km/h

Trip Start is usually defined as follows:

Road Speed >= 5 km/h OR

(Ignition On = True AND

Driver Identified)

However, if the Driver does not get identified properly, the second condition evaluates to False. The
definition of Trip Start thus becomes:

1272
www.mixtelematics.com

1272
 1273

Road Speed >= 5 km/h

Therefore the trip only starts when the vehicle is actually moving, and in this way Idle may appear to
occur outside of the trip. This is because the fact that the Ignition is on no longer implies in any way
that the vehicle is in a trip.

----- STATUS -----

This behaviour is by design.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000 FM98

1273
www.mixtelematics.com

1273
 1274
10.3.105 Knowledge Base Article 106

Article Number 106

Title Error 429 On Download when using Win98 SE

Created 9/28/1999 9:50:25 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/23/1999 9:01:24 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1)

----- SUMMARY -----

After having installed the Fleet Manager 98 software onto a computer running Microsoft Windows
98 Second Edition (SE), the above problem may be experienced.

----- MORE INFORMATION -----

When attempting to download from an FM100 vehicle plug, the following error may occur:

429 (0x000301AD): ActiveX component can't create object occurred in FM100Data.Preprocess

(Line 8580)

The error also occurrs when downloading from an FM200 vehicle plug, but is worded slightly
differently. The error message, therefore, may also be:

429 (0x000301AD): ActiveX component can't create object occurred in FM200Data.Preprocess

(Line 4840)

----- CAUSE -----

This is caused by an incorrect version of Microsoft DCOM98 being installed on the user's
computer. The version of this software that is included on the Fleet Manager 98 SR1 CD is
incompatible with Windows 98, Second Edition.

----- SOLUTION -----

Download and install the latest version of DCOM98 from the Microsoft web site at http://www.
microsoft.com/com/dcom/dcom98/download.asp. Please ensure that you read the licensing
agreement carefully before downloading this software.

----- STATUS -----

This problem will be solved with the FM Kienzle Fleet Manager 2000 release.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1274
www.mixtelematics.com

1274
 1275
10.3.106 Knowledge Base Article 107

Article Number 107

Title No Idling or Ignition events recorded

Created 9/29/1999 11:17:44 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 9/29/1999 12:51:58 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 100

· FM Kienzle Fleet Manager 200

· FM Kienzle Fleet Manager 200e (FM200 with EMI)

----- SUMMARY -----

Excessive voltage spikes may damage the ignition input circuit which causes ignition related
events not to be recorded.

----- MORE INFORMATION -----

The FM200 ignition and battery circuitry is protected against voltage spikes of up to 300V (volts)
and down to -400V. It has been observed that on a certain make of heavy duty truck tractor, where
these limits were exceeded, that a resistor has been damaged. This causes the vehicle unit not to
sense the "Ignition On" event. This means that the Idle event, and any other Ignition related events,
are not recorded. This problem has only been observed on FM200 installations but since the
circuits are common to the FM100, it is not excluded that they may display similar symptoms. To
date only heavy duty truck tractors have been seen to cause this problem (specifically, older
Mercedes Benz Powerliners).

----- CAUSE -----

Vehicles which have extremely noisy ignition circuits, especially those with unprotected inductive
loads, can generate high energy voltage spikes. These spikes have been seen to damage a
resistor on the ignition input circuitry on the FM200 (This has been observed to date on older
Mercedes PowerLiner 1735 truck tractors - see note under Status).

----- SOLUTION -----

Protect the FM200 Ignition input by fitting a Metal Oxide Varistor (Siemans S10K30) between
Ignition and ground on the FM200 harness.

----- STATUS -----

An investigation into the failures on the Mercedes Powerliner trucks was undertaken and it was
found that high voltage spikes were generated on some trucks when ignition was turned off. The
source of these spikes has not yet been identified and they may well be generated by third-party
electrical equipment. As a precaution, the above MOV (Siemans S10K30) should be fitted when

1275
www.mixtelematics.com

1275
 1276

installing any of the FM series of vehicle units into heavy duty trucks.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM200 FM200e

1276
www.mixtelematics.com

1276
 1277
10.3.107 Knowledge Base Article 108

Article Number 108

Title Incorrect Data from Fuel Recorder (EDM)

Created 9/30/1999 4:03:24 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 2:20:12 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1) or higher

----- SUMMARY -----

Having just installed an EDM unit into a vehicle, in conjunction with an FM200 or FM200e, you may
observe that the data does not appear to be realistic.

After double-checking the calibration of the unit, measurement format (U.S., Imperial, or Metric), and
consumption type (km/l - Kilometers per Litre, l/100km - Litres per 100 Kilometers, or mpg - Miles per
Gallon), the unit still does not appear to be recording accurate fuel consumption data.

----- CAUSE -----

This typically occurs when the user merely does 2 or 3 very short trips (2 kilometers or less), in order
to "test" that the EDM is functioning correctly. Realistic fuel consumption information may only begin
to be displayed after long trips are done.

----- SOLUTION -----

Allow the vehicle at least one week of normal operation, before expecting to see realistic EDM data
on the Fleet Manager reports and graphs.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM98 FM2000

1277
www.mixtelematics.com

1277
 1278
10.3.108 Knowledge Base Article 109

Article Number 109

Title Error 50104 trying to access the download module

Created 9/30/1999 4:51:45 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 12/3/1999 9:57:56 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When attempting to access any download module related function from within the Fleet Manager
software, error 50104 (Plug Communications Error) may be displayed.

----- MORE INFORMATION -----

The error message displayed is as follows:

50104 (C3B8): A Download Module communication error occurred. Please make sure the Download
Module is configured correctly. occurred in PlugReader.GetPlugInfo (Line 19280).

The "occured in" and "Line" sections above are for the "Plug Information" dialog, and may vary
depending on which Download Module related function that you are trying to perform.

This error may typically occur if you have manually created a custom shortcut, which points to the
"FMClient.exe" (or "FMClient2.exe") file.

The behavior that could produce the error includes: Downloading, Initialising a Plug, Plug Information,
etc, for any supported plug types. If installed, the Fleet Manager Dealer Utility (FMDealer) will read
from the plug correctly.

When this error occurs, search your hard drive for the following files: TODLM.INI and TOWDB.INI. If
this Knowledge Base Article applies to you, then you should observe that the TODLM.INI file exists in a
directory other than your default Fleet Manager directory, while TOWDB.INI does not exist at all.

----- CAUSE -----

The error in this case is caused when you launch a custom shortcut to the "FMClient.exe" (or
"FMClient2.exe") file, who's "Start In" property is a directory that is different from the Fleet Manager
directory. Alternatively, it could occur if you simply run this file from the Windows Start menu. For
example, click Start|Run, and type C:\Program Files\Fleet Manager\FMClient.exe.

The Fleet Manager 98 software attempts to launch a seperate program, called DMI2.EXE. It expects to
find this program in your current default directory. If this file is not found, the software will not be able to
launch it, and will assume that a Plug Comms error has occurred.

1278
www.mixtelematics.com

1278
 1279

----- SOLUTION -----

Always ensure that you launch the main executable (FMClient.exe or FMClient2.exe) from the directory
in which it resides. Any shortcuts you create to this file should have their "Start In" properties modified
to point to the Fleet Manager directory.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1279
www.mixtelematics.com

1279
 1280
10.3.109 Knowledge Base Article 110

Article Number 110

Title New Status not visible from SR page

Created 10/6/1999 9:35:27 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 1/25/2000 5:14:30 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Data Pro Service Online, all versions

· Data Pro Centre-Point, all versions

----- SUMMARY -----

After defining a new SOL/CP Status from the System Administration section, it is not visible while
logging/modifying a Service Request.

(This article assumes that you are familiar with the System Administration functions of Service Online
and Centre-Point, and that you have Administrative rights, to carry them out. If not, then please
contact your Service Online or Centre-Point Administrator.)

----- MORE INFORMATION -----

You have created a new Service Request status, by navigating to System Administration, Service
Request Parameters, Statuses, Maintain. After clicking Add Record, you attempt to add a new service
request (Service Requests, Maintain), and observe that you are not able to assign it to your newly
created Status.

----- CAUSE -----

After adding a new status, you still need to define which groups of contacts (Contact Groups) have
permission to change Service Requests to that Status. Typically, after creating a new status, no-one
is allowed to use it, yet. You need to ensure that at least one Contact Group has permissions on that
status.

----- SOLUTION -----

Navigate to System Administration, Groups, Contact Groups, Maintain. Select the group that you
would like to have permission to use the new status. Now, select your new status in the list of
checkboxes, and click Modify Record. Repeat this for all groups that you would like to grant
permissions on the new Status.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

1280
www.mixtelematics.com

1280
 1281

KEYWORDS: SERVICE ONLINE CENTRE-POINT

1281
www.mixtelematics.com

1281
 1282
10.3.110 Knowledge Base Article 111

Article Number 111

Title 'Closed' Service Requests no longer visible

Created 10/6/1999 10:12:11 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 1/25/2000 5:00:16 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Data Pro Service Online, all versions

· Data Pro Centre-Point, all versions

----- SUMMARY -----

After the Status of a Service Request has been changed to "Closed", that SR is no longer visible in
any of the pre-defined Service Request lists.

----- MORE INFORMATION -----

You have changed a Service Request to "Closed", by clicking on the "Change this service request's
status" link, selecting "Closed", and clicking Change Status.

After changing the status, the following lists, which previously included the particular Service Request,
no longer include the Request:

· Contact Management

o Organisations

§ Maintain

o Contacts

§ Maintain

· Service Requests

o Lists

§ Open Requests Assigned To Me

§ Open Requests Logged By Me

§ Open Requests Where I Am The Contact

o Open Request Statistics

1282
www.mixtelematics.com

1282
 1283

§ By User

§ By Group

§ By Status

§ By Type And Category

§ By Priority

(Note: Depending on your access restrictions and security level in the system, some or none of the
above lists may be visible)

----- CAUSE -----

The above lists all list Service Requests whose Status is not "Closed". This is because of tha fact that
the "Closed" Status is a special type of Status, that is used to indicate that a given Request has been
resolved to completion.

However, this does not mean that Closed Service Requests are no longer in the system. They are still
within the relevant system's Database, and visible through the Service Request Query.

----- SOLUTION -----

To see Service Requests that have been closed, navigate to Service Requests, Query (Or Service
Requests, Adhoc Query, for Data Pro Centre-Point). Fill in one or more of the Search Criteria fields
and click Submit. All Requests matching these criteria will be displayed.

(This solution assumes that you have permission to perform a Service Request Query. If you do not,
please contact your System Administrator)

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: SERVICE ONLINE CENTRE-POINT

1283
www.mixtelematics.com

1283
 1284
10.3.111 Knowledge Base Article 112

Article Number 112

Title Overflow Error on Create/Update database

Created 10/7/1999 11:02:56 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:29:02 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.10 (SR1a) - FMServer.exe version

----- SUMMARY -----

When attempting to install the Fleet Manager 98 SR1a Update patch, the above error may occur. It may
also occur if you attempt to manually execute the FMCreateDB.Exe file, located in your Fleet Manager
directory.

----- MORE INFORMATION -----

The error messages that may be displayed are as follows:

Error occurred in database update: (6) Overflow

Or,

Error occurred in database creation: (6) Overflow

----- CAUSE -----

This problem occurs if you have more than 2 gigabytes of free disk space on the target computer at the
time of install. It may also occur when upgrading, if the size of your Fleet Manager database exceeds
this same 2 gigabyte limit.

----- SOLUTION -----

Please upgrade to the latest available version of the Fleet Manager software (FM Fleet Manager 2001
SR2 or later).

----- STATUS -----

This problem has since been solved.

------------------------------------------------------------------------------

KEYWORDS: FM98 FMCREATEDB

1284
www.mixtelematics.com

1284
 1285
10.3.112 Knowledge Base Article 113

Article Number 113

Title What's New in FM Kienzle Fleet Manager 98 SR1a

Created 10/12/1999 9:35:56 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:27:24 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, SR1a Update

----- SUMMARY -----

The following is a list of what's new in the SR1a Update of FM Kienzle Fleet Manager 98.

This update can be downloaded from the Data Pro Development web site at http://www.
mixtelematics.com

· When attempting to clear large amounts of vehicle data from the Fleet Manager database, an
error message would be displayed some time into the clear process, stating: “The data you tried to
update is in use by another process, and cannot be updated now.” The only way to get around this
was to clear small amounts of data for one or two vehicles at a time, and eventually all the
required data would be removed. This was due to the incredibly large volume of data in the
database, and has been corrected in SR1a. For more information about this problem, please see
Knowledge Base Article 97.

· The above problem would also occur when trying to delete a Site or Configuration Group
containing large volumes of vehicles.

· When attempting to download data from an FM200 data plug, the following error message may
have been displayed: “324 (0x00000CAE) Operation not supported in transactions. Occurred in
FM200Data.PreProcess (Line 4840)”. This was due to an error in the download component, which
prevented it from correctly interpreting some event data. A solution to this problem has been
developed, and is included in the SR1a release. For more information, see Knowledge Base
Article 98.

· If an FM100 plug was initialised from within the Fleet Manager 98 software, its configuration would
be corrupted, so that the Idle and Idle – Excessive events would occur in the vehicle, regardless of
the value of Road Speed. The only way to work around this problem was to initialise all FM100
plugs from the FM Kienzle Fleet Manager FM100 software. Please see Knowledge Base Article 94
about this problem, which has been solved in SR1a.

· Occasionally, there was a discrepancy between the Driver Scoring Report, and the Driver Driving
Errors Report. This would cause a driver to score less than 100% for Over Revving (and other
events), however the Driver Driving Errors report reported that there was no occurrence of that
event for the same period, for that driver. This problem has been solved in SR1a.

· There were discrepancies between the detail and summary Trip Reports, when a particular vehicle
or driver had to be calculated over more than one page. These have been corrected In SR1a.

1285
www.mixtelematics.com

1285
 1286

· The Entered Fuel Consumption Report will no longer generate an unexpected error if there are
fuel entries where no fuel was entered. (Litres/Gallons column is zero)

· The database creation/upgrade program (FMCreateDB.Exe) has been enhanced, to check at

various intervals during the upgrade for data corruption of various types, and attempt to correct/
recover from that corruption wherever possible. There are also numerous rules that are now
enforced, regarding the amount of free disk space required to create or upgrade databases under
certain circumstances. For a description of these rules, please see Knowledge Base Article 99.

To download this document in Microsoft Word 97 format, go to ftp://ftp.centre-point.com/KBase/

NewInSR1a.doc. This is a 39kb document file.

To view the FM SI document regarding FM98 SR1a, refer to FM SI No 382007 - Fleet Manager 98
SR1a.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM200 FM98

1286
www.mixtelematics.com

1286
 1287
10.3.113 Knowledge Base Article 114

Article Number 114

Title Events Based on Trip Distance Don't Work

Created 10/18/1999 2:46:22 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 2:21:19 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1) and above

----- SUMMARY -----

Creating an event based on the "Trip Distance" parameter does not work correctly. Events created
in this way may continue to occur even when the vehicle is stationary.

----- MORE INFORMATION -----

You create a new event, and set it to occur when:

Trip Distance > 1.5 Km

After uploading the new event into a vehicle, and doing a trip of 2.0 Km in length, you may notice
that the event occurs at 1.5 Km, and stays "On", even after the ingition is turned off.

----- CAUSE -----

This is caused by the fact that the value of the Trip Distance parameter is only internally "Reset"
after the unit re-arms. Even after turning the ignition of the vehicle off after a 2 Km trip, the value of
Trip Distance will continue to be 2 Km until such time as the vehicle arms. This can be up to 10
minutes.

----- SOLUTION -----

Add a second parameter into your event definition, so that it only fires when the vehicle is actually
active. The Vehicle Active parameter internally becomes False after the ignition is turned off, when
there is no speed or Engine RPM.

Thus, the definition of your event should be:

Trip Distance > 1.5 AND

Vehicle Active = True

This will cause the event to stop occurring as soon as your ignition is turned off.

----- STATUS -----

This is one of the design philosophies of the FM200 unit, and cannot be changed.

1287
www.mixtelematics.com

1287
 1288

------------------------------------------------------------------------------

KEYWORDS: FM98 FM200 FM2000

1288
www.mixtelematics.com

1288
 1289
10.3.114 Knowledge Base Article 115

Article Number 115

Title All 2010 Interval Data Gets Rejected On Download

Created 10/20/1999 11:14:28 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 10/20/1999 11:14:28 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· CITAS 2010, all versions

----- SUMMARY -----

When downloading interval data from the Blue Tag, it may be observed that all interval data will be
rejected by the system.

----- MORE INFORMATION -----

This may happen even though there are actually trips stored for the vehicle in the database.
However, should this begin to occur, you will notice that the driver who drove the trips in question is
not captured into the system.

----- CAUSE -----

When downloading trips from the Office Reader, the CITAS 2010 software will automatically create a
vehicle, if one is not found. It will not create drivers as necessary, though, and will match these
drivers to "No Tag Inserted".

However, when downloading Interval data, the driver cannot be matched in this way, and the interval
will be rejected if no driver is found.

----- SOLUTION -----

In order to extract Interval data into the CITAS 2010 software, ensure that all drivers are correctly
captured into the database.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: CITAS 2010

1289
www.mixtelematics.com

1289
 1290
10.3.115 Knowledge Base Article 116

Article Number 116

Title EDM Data on Tacho Graph shows zero values

Created 10/26/1999 5:28:08 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 3/22/2000 12:27:40 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1) and above

----- SUMMARY -----

After connecting an EDM unit (or other fuel flow meter) to your FM200 vehicle unit, all EDM
related data is displayed correctly.

However, when attempting to view Tacho Data for the F3 Input, of a vehicle which has a fuel flow
meter attached, you notice that the value displayed on the graph is shown as zero.

----- CAUSE -----

The smallest value that can be displayed on the Tacho Data Graph is zero, and the points on the
graph are shown at one second intervals.

Because the volume of fuel that is typically used in one second is very small, the graph is unable
to display the value, and merely displays zero (0).

----- STATUS -----

This is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FM200 FM200e

1290
www.mixtelematics.com

1290
 1291
10.3.116 Knowledge Base Article 117

Article Number 117

Title Activity Timeline Displays incorrect l/100km

Created 11/4/1999 1:17:29 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 1:26:01 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, SR1a and below

----- SUMMARY -----

When viewing fuel consumption figured on the Activity Timeline, with your Consumption Units set to
Litres per Hundred Kilometers (l/100km). The figures are displayed correctly.

----- MORE INFORMATION -----

With vehicles that include a fuel counter (for example, EDM), the software allows you to view fuel
consumption information on a per Sub-Trip and Trip basis. If displayed in l/100km format, this
information will be incorrect.

Note that this error does not affect any of the other Reports or Graphs, but only the Activity
Timeline.

----- CAUSE -----

The above versions of the software use an incorrect formula to calculate fuel consumption in this
system. Where the formula should be:

(Litres / Kilometers) * 100

it is being incorrectly calculated as:

Litres / (Kilometers * 100)

----- SOLUTION -----

To workaround this problem, you may view this information in the "Kilometers per Litre" (Km/l) or
"Miles per Gallon" (mpg) measurement units. Alternatively, you should use the other Reports and
Graphs to view this information.

----- STATUS -----

This has been solved in the Fleet Manager 2000 release.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1291
www.mixtelematics.com

1291
 1292
10.3.117 Knowledge Base Article 118

Article Number 118

Title How do I access the information in the system using Access 2000?

Created 11/11/1999 12:19:31 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/11/1999 1:21:40 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

· Shurlok EV100, all versions

· CI Data, all versions

· FM Kienzle Fleet Manager 100, all versions

· CITAS 2010, all versions

----- SUMMARY -----

Many customers would like to develop their own applications which utilise the information stored in
the above products' databases.

----- MORE INFORMATION -----

All of the above products use a Microsoft Jet database to store information. You can use any
application capable of accessing Jet databases to retrieve information from the databases. In order
to ensure the integrity of the information, these databases are read-only. Updating records is not
permitted.

The FM Kienzle Fleet Manager application utilises a Jet 3.5 database (.MDB file) named FMServer.
MDB. You can open this databases directly using any Jet 3.5 compatible application such as
Microsoft Access 97.

The Shurlok EV100, CI Data, FM Kienzle Fleet Manager 100 and CITAS 2010 applications are 16-bit
applications and utilise a 16-bit Jet 2.5 database (.MDB files) named EV100.MDB, CIDATA.MDB,
FM100.MDB and CITAS.MDB respectively. You can open these databases directly using any Jet 2.5
compatible application such as Microsoft Access 2.0.

The above products' databases cannot be opened directly using Microsoft Access 2000 because
they must be first be upgraded. Once upgraded, they are no longer accessible to their applications.

----- SOLUTION -----

You can utilise the data in these databases without upgrading them by creating a new empty
database using Access 2000 and linking the product databases' tables into it.

1292
www.mixtelematics.com

1292
 1293

Access 2000 help contains instructions on how to link tables. This is a very simple procedure which
consists of the following basic steps:

1. Click on the "File" menu then select "Get External Data" then select "Link Tables".

2. The standard "File Open" dialog is displayed. Browse for the database file.

3. A list of tables is displayed. Select the tables you wish to link (or click "Select All").

4. Click the OK button.

5. The tables are linked into the empty database. Linked tables have an arrow icon differentiating
them from other tables in the database.

You can open any of the linked tables and create queries, reports etc. using them.

Linked tables are read-only (just like the original tables in the underlying database) and cannot be
updated.

Linked tables are "links" to the original tables so that changes in the original tables are reflected real-
time in the linked tables.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM200 FM98 FM2000 EV100 CIDATA CITAS 2010

1293
www.mixtelematics.com

1293
 1294
10.3.118 Knowledge Base Article 119

Article Number 119

Title Divide By Zero error occurs on Activity Timeline

Created 11/12/1999 11:16:04 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 4/10/2002 10:58:08 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, SR1/SR1a

----- SUMMARY -----

When clicking on a blue trip bar in the Activity Timeline, the following error is displayed:

11 (0x0000000B): Division by zero. occurred in frmActivity.WriteSelect (Line 56760)

----- MORE INFORMATION -----

This error occurs when viewing trip data for a vehicle that has a fuel counter connected (For
example, an EDM unit), and your fuel consumption measurement units are set to Litres per hundred
kilometers (l/100km). It occurs because a very small quantity of fuel usage was recorded for the
particular trip in question, but the distance of the trip was not great enough to record, and so zero (0)
was stored for that trip's distance.

----- CAUSE -----

The software calculates l/100km as follows:

(Litres/Kilometers) * 100

Thus, in a hypothetical example, where 0.001 Litres where used for a trip, which didn't record a
distance (Kilometers = 0), this evaluates to:

(0.001/0) * 100

0.001/0 is illegal, for the reason described above. (Division by zero)

----- SOLUTION -----

In order to prevent this error from occuring, you may set your measurement units to show Kilometers
per litre (km/l). Alternatively, you may make use of the Fuel Consumption reports and graphs, which
do not suffer from this problem.

----- STATUS -----

This problem has been solved in the FM Kienzle Fleet Manager 2000 software.

------------------------------------------------------------------------------

1294
www.mixtelematics.com

1294
 1295

KEYWORDS: FM98 FM2000 FM200 FM200e

1295
www.mixtelematics.com

1295
 1296
10.3.119 Knowledge Base Article 120

Article Number 120

Title Error 2201 occurs when generating a report

Created 11/16/1999 11:16:49 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 3/6/2000 1:18:09 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When generating any report, an unexpected error 2201 (No Default Printer) occurs. No
description is provided for this error.

----- CAUSE -----

This error typically occurs during the generation of a report, when there is no default printer
installed. It happens when there is in fact one or more printers installed on your computer, but
none of them have been set to be the Default Printer

----- SOLUTION -----

In order to generate reports from the Fleet Manager software, you must have a default printer
set up on your computer. To set a printer to be the default printer, follow these steps:

Click Start, Settings, Printers. Click one of the printers with your right mouse button, and click
Set as default. Make sure that this option is checked (ticked).

----- STATUS -----

This problem is under investigation

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1296
www.mixtelematics.com

1296
 1297
10.3.120 Knowledge Base Article 121

Article Number 121

Title Error 50104 occurs, and my software is installed into a disk drive other than C:

Created 12/3/1999 10:00:37 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:25:20 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

----- SUMMARY -----

When attempting to access any download module related function from within the Fleet Manager
software, error 50104 (Plug Communications Error) may be displayed.

----- MORE INFORMATION -----

The error message displayed is as follows:

50104 (C3B8): A Download Module communication error occurred. Please make sure the Download
Module is configured correctly. occurred in PlugReader.GetPlugInfo (Line 19280).

The "occured in" and "Line" sections above are for the "Plug Information" dialog, and may vary
depending on which Download Module related function that you are trying to perform.

This error may typically occur if you installed the software onto a disk drive other than the default C:
option offered by the installation program (For example, D:\Fleet Manager). If this is not the case,
then please see also Knowledge Base Article 109: Error 50104 trying to access the download
module.

The behavior that could produce the error includes: Downloading, Initialising a Plug, Plug
Information, etc, for any supported plug types. If installed, the Fleet Manager Dealer Utility
(FMDealer) will read from the plug correctly.

When this error occurs, search your hard drive for the following files: TODLM.INI and TOWDB.INI. If
this Knowledge Base Article applies to you, then you should observe that the TODLM.INI file exists in
a directory other than your default Fleet Manager directory, while TOWDB.INI does not exist at all.

----- CAUSE -----

The error in this case is caused by a fault in the installation program. When the shortcut to Fleet
Manager 98 is created, no Start In directory is assigned.

The Fleet Manager 98 software attempts to launch a seperate program, called DMI2.EXE. It expects
to find this program in your current default directory. If this file is not found, the software will not be
able to launch it, and will assume that a Plug Comms error has occurred.

----- WORKAROUND -----

1297
www.mixtelematics.com

1297
 1298

You should edit this shortcut to contain the valid Start In path. To do this, click the Start menu with
your right mouse button, and click Explore. Locate the shortcut to the Fleet Manager 98 software,
right-click it, and click Properties. Modify the Start In location to point to the valid path (For example,
D:\Fleet Manager), and click OK.

----- STATUS -----

This problem has been solved in the Fleet Manager 2000 software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1298
www.mixtelematics.com

1298
 1299
10.3.121 Knowledge Base Article 122

Article Number 122

Title Error 53 After Modifying Reader Options

Created 12/13/1999 9:29:25 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 1/7/2000 9:52:39 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· CITAS 2010, all versions

----- SUMMARY -----

After modifying any of the "Reader Options" from the CITAS 2010 software, error 53 (File not found)
may be displayed.

----- MORE INFORMATION -----

The error message displayed is as follows:

Error in Save Communication Options - 53: File not found

Steps to reproduce behaviour:

1. From the CITAS 2010 main program window, click the Setup menu, and then click Options.

2. Click the Reader Options button.

3. Modify any of the options on the screen, and click OK.

----- CAUSE -----

This error may occur if either the Diagnostic Binary File (In version 2.00, this file is called "D2008.
BIN") and/or the CITAS 2010 Unit Binary File (This file is called "C3003.BIN" in version 2.00 of the
software) are not found, at the time of clicking the OK on the CITAS Office Interface Options dialog.

----- SOLUTION -----

By default, these files are located in a directory called C:\CITAS\BIN on your computer. Please verify
the existence of these files - if they do not exist, then you will need to re-install the software.

----- STATUS -----

This problem will be solved in the next release of the CITAS 2010 software. (Version 2.10)

------------------------------------------------------------------------------

KEYWORDS: CITAS 2010

1299
www.mixtelematics.com

1299
 1300
10.3.122 Knowledge Base Article 123

Article Number 123

Title Fleet Manager on a Novell Netware server

Created 12/14/1999 10:05:17 AM

Created By Wayne Davies (MiX Telematics - Stellenbosch)

Last Modified 12/14/1999 10:15:43 AM

Last Modified By Wayne Davies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98 - all versions

· FM Kienzle Fleet Manager 2000 - all versions

----- SUMMARY -----

The Fleet Manager application cannot be configured to operate in client-server mode, as described in
the document entitled "Network Configuration Guide" (included on the Fleet Manager CD) on a Novell
Netware server.

----- MORE INFORMATION -----

The Fleet Manager application utilises a technology called Distributed Component Object Model
(DCOM) when operating in client-server mode on a network. This technology allows the components of
the system to run on separate personal computers on the network, resulting in a distributed processing
solution. Minimal data is exchanged between components over the network.

To the best of our knowledge, DCOM cannot run on a Novell server and thus the Fleet Manager
application cannot be configured to run in client-server mode on a Novell Netware server.

It is possible to install the Fleet Manager application and database files onto a Novell Netware file share
on a Novell Netware server, however care should be excercised when doing so as numerous problems
may be encountered. Below is a list of problems which we have encountered to date:

1. The Fleet Manager applications may require the number of locks on the file server to be increased.

2. The Fleet Manager application is not designed to run from a file share and file/record locking
problems may be experienced.

3. If the Fleet Manager database file (FMServer.MDB) is located on a file share, large volumes of data
will be transfered over the network and the risk of database corruption increases dramatically. Any
network interruptions are likely to result in the database becomming corrupted.

----- CONCLUSION -----

We do not advise that the Fleet Manager application be run from a file share.

------------------------------------------------------------------------------

KEYWORDS: FM98, FM2000

1300
www.mixtelematics.com

1300
 1301
10.3.123 Knowledge Base Article 124

Article Number 124

Title Modifying Input or Service Information at Config Group doesn't update Vehicle

Created 12/17/1999 12:53:26 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 12/17/1999 1:33:01 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

It is possible to modify the default values for Input Configuration and Service Information (As well as
Event Configuration) for your vehicles, from within the Vehicle Configuration Group. Properties
modified in this way do not automatically update the vehicles that may already exist in that group.

----- MORE INFORMATION -----

To reproduce this behaviour, right-click a vehicle configuration group which contains vehicles, and
click Properties. Modify some of the properties on the Input Configuration or Service Information tabs
(For example, the Arming Delay property). Click OK, and notice that these changes have not affected
your existing vehicles. However, had you made changes to the Event Configuration while in the
Group, the Event changes would have taken effect.

----- CAUSE -----

As the Fleet Manager documentation and help files explain, the Vehicle Configuration Group
properties merely define default values for new vehicles that are added to the system. Modifying
them at a later date does not affect already existing vehicles.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1301
www.mixtelematics.com

1301
 1302
10.3.124 Knowledge Base Article 125

Article Number 125

Title General Protection fault (Access Violation) Generating a Report

Created 1/7/2000 9:34:21 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:24:30 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When attempting to generate any report from within the Fleet Manager software, a General
Protection Fault (GPF) may occur in the Reports server (FMReports.exe for FM98, or FMReports2.
exe for FM2000)

----- MORE INFORMATION -----

If you have Microsoft Office 2000 installed, the above error may occur. The details of the Access
Violation are as follows:

FMREPORTS caused an exception 10H in module MSVBVM60.DLL at 0177:660121d7.

The above description will be displayed if you have Fleet Manager 98 installed. If you have FM2000,
the details are as follows:

FMREPORTS2 caused an exception 10H in module MSVBVM60.DLL at 0177:660121d7.

----- CAUSE -----

This is one of the problems that may occur if Microsoft Office 2000 (specifically, Microsoft Access
2000 or Microsoft Excel 2000) is installed onto your computer after installing the Fleet Manager
software.

This is due to the fact that Office 2000 removes many entries in the user's system registry, that are
required by the Microsoft Access Runtime to function correctly. The Microsoft Access Runtime is
installed by the FM Kienzle Fleet Manager installation set, and is required to generate all reports.

For more information about Microsoft Office 2000 and the Fleet Manager system, please see KBA61:
FM Kienzle Fleet Manager Software with Microsoft Office 2000.

----- SOLUTION -----

Re-install the Microsoft Access Runtime from the Fleet Manager CD-ROM. This will restore all the
registry entries required to generate reports. After verifying that the reports are working correctly,
execute Microsoft Access 2000 or Microsoft Excel 2000. The Office 2000 setup dialog will appear, to

1302
www.mixtelematics.com

1302
 1303

re-install all the necessary Office 2000 registry entries. Once this has been done, both software
products should continue to function correctly.

If this does not solve the problem, then it is likely that you installed Office 2000 after the Fleet
Manager software, and allowed it to "Remove previously installed Office components". If this is the
case, you will need to completely uninstall Office 2000, and re-install the Fleet Manager software.
Once the reports are working, you may re-install Office 2000, and both products will continue to work
successfully.

----- STATUS -----

This is a known issue with Microsoft Office 2000, and is beyond the control of Data Pro Development
(Pty) Ltd.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 Reports Office 2000

1303
www.mixtelematics.com

1303
 1304
10.3.125 Knowledge Base Article 126

Article Number 126

Title Error -113 During Installation of FM98 Software

Created 1/7/2000 9:47:29 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 5/17/2000 10:33:18 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, Service Release 1 (SR1)

----- SUMMARY -----

When attempting to install the Fleet Manager 98 software from the Fleet Manager 98 CD-ROM, error
-113 may occur in the installation set. The error will occur in the final stages of the setup program,
when the files are being copied to your hard disk.

----- MORE INFORMATION -----

The details of the error are as follows:

ComponentMoveData had the following error:

Media Name: data

Component: Program Files

File Group: Program Files

File: Español.ecf (Espanol.ecf)

Error Number: -113

After this has been displayed, a message box will be displayed, reading:

An error ocurred during the move data process: -113

Component: Program Files

File Group: Program Files

File name: D:\Español.ecf

(Replace "D:\" above with the letter of your CD-ROM drive.) Following this, another message box is
displayed, which reads:

An error has occurred that prevents setup from continuing. Setup will end now.

The installation then terminates.

1304
www.mixtelematics.com

1304
 1305

----- CAUSE -----

Some CD-ROM drives tend to have difficulty when copying files off CD's, if the file name has a
special character in it. The special "ñ" character (An "n" with an accent marker) in Español.ecf may
therefore cause this problem on some systems.

----- SOLUTION -----

From within Windows Explorer, copy the entire FM98 CD-ROM image (Including all subdirectories)
into a temporary directory on your hard drive. Then, execute the setup program from this location.

----- STATUS -----

This problem has been solved in the Fleet Manager 2000 release.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1305
www.mixtelematics.com

1305
 1306
10.3.126 Knowledge Base Article 127

Article Number 127

Title Spaces in SOL/CP Message Headers

Created 1/10/2000 1:24:25 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 1/10/2000 1:24:25 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Data Pro Service Online, all versions

· Data Pro Centre-Point, all versions

----- SUMMARY -----

When the above products send out e-mail, and the subject of the e-mail message that they send out
is longer than 66 (sixty-six) characters, a space will be inserted at the 66th position.

----- MORE INFORMATION -----

An example of the above is a message with the following subject:

Service request SR#3932 re-assigned to Jeremy Hartley (Data Pro D evelopment (Pty) Ltd)

The subject line should in fact read:

Service request SR#3932 re-assigned to Jeremy Hartley (Data Pro Development (Pty) Ltd)

However, a space is inserted at the 66th position (...D_evelopment...). This does not only occur with
service request assignments, but with notification of any action, when the subject line would be more
than 66 characters in length.

----- CAUSE -----

This is an issue with the Microsoft Exchange e-mail server, where the server will insert a space at
position 66, of the subject of any e-mail message.

----- STATUS -----

This is unfortunately an issue with the Microsoft Exchange e-mail system, and is beyond the control
of Data Pro Development (Pty) Ltd.

------------------------------------------------------------------------------

KEYWORDS: SERVICE ONLINE CENTRE-POINT

1306
www.mixtelematics.com

1306
 1307
10.3.127 Knowledge Base Article 128

Article Number 128

Title Adding or Editing an SR 'Hangs' the Server

Created 1/10/2000 1:32:29 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 1/25/2000 5:03:09 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Data Pro Service Online, all versions

· Data Pro Centre-Point, version 3.00

----- SUMMARY -----

If you click on Service Requests|Maintain in the tree view on the left, from either of the above
products, the server stops responding, and appears to "hang". The problem also occurs when
clicking on a Service Request number, to view its details.

----- MORE INFORMATION -----

When this problem occurs, you may notice that a particular process, the Inetinfo process on the
server, goes to 100% CPU Usage. You are unable to terminate this process. The only solution is to
re-start the server computer.

----- CAUSE -----

This is caused by the fact that there are no working days defined in the system. The system uses
the defined list of working days to calculate the due date of a Service Request. An absence of
working days means that the system enters an endless loop, attempting to find the next working
day, to calculate the due date.

----- SOLUTION -----

Ensure that you have at least one working day defined. To define a working day, log into your
Service Online or Centre-Point system (You may need to re-start your server computer in order to
do this) as a user with System Administrator privileges.

In the tree view on the left, click System Administration|Auto Escalation Parameters. Ensure that
the Enabled property of at least one day is checked, and enter a From and To time for that day.

----- STATUS -----

This problem has been solved in Centre-Point 3.01.

------------------------------------------------------------------------------

KEYWORDS: SERVICE ONLINE CENTRE-POINT

1307
www.mixtelematics.com

1307
 1308
10.3.128 Knowledge Base Article 129

Article Number 129

Title 'Store Average Value' for Events Does Not Work

Created 1/11/2000 2:49:04 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:22:13 PM

Last Modified By Tony Gois (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

Creating a new event, and electing to store the Average value of a parameter does not work
correctly. An incorrect value will be returned.

----- MORE INFORMATION -----

When you create a custom event from within the Fleet Manager software, you have the option to
have this event record (store) a value - Maximum, Minimum or Average. If you decide to do this, you
also need to select a parameter, who's value to record.

When data for such an event, that has been defined to record the Average value of a parameter, is
downloaded from your FM200 or FM200e vehicle, the value that is recorded will be incorrect.

----- CAUSE -----

This is caused by errors in one of the Device Driver files (DDR). This error causes average values to
be calculated incorrectly by the unit.

----- SOLUTION -----

Download the 52k patch from ftp://ftp.centre-point.com/KBase/stravg.zip, and extract its contents into
your Fleet Manager Device Drivers (Typically "C:\Program Files\Fleet Manager\Drivers") directory.
Then, re-upload Device Drivers to all the vehicles that you would like to utilise the "Store Average"
functionality in.

To verify that you have the correct device driver files loaded, insert a vehicle plug, and click the "Plug
Information" toolbutton. Scroll down the list of device drivers that have been loaded, until you find one
that reads:

(C)C.I.1998:FM Kienzle FM200 Event Controller (12.0.28 16K)

If the version number of the above DDR is less than "12.0.28", then you will need to re-upload device
drivers to that vehicle.

----- STATUS -----

1308
www.mixtelematics.com

1308
 1309

This problem has been solved. The fixed device driver file has been included in the next release of
the Fleet Manager 2000 software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FM200 FM200e

1309
www.mixtelematics.com

1309
 1310
10.3.129 Knowledge Base Article 130

Article Number 130

Title Mail no longer works after IE4 Install

Created 1/17/2000 11:52:45 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 1/17/2000 1:16:31 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Data Pro Service Online, all versions

· Data Pro Centre-Point, all versions

----- SUMMARY -----

After installing Internet Explorer 4 on the server, and electing to install Outlook Express 4, the above
products no longer send out e-mail.

----- MORE INFORMATION -----

For more information about this problem, please see Q129119 - PRB: MAPI/CDO Applications Fail
After Outlook Express 4 Install, on the Microsoft web site.

----- CAUSE -----

This is caused by the fact that Outlook Express 4 replaces a DLL required by SOL/CP, with another
version, that does not support all the functionality that the other one did. (The version installed by
Windows Messaging)

----- SOLUTION -----

Ensure that Outlook Express is not set to be the "Default MAPI Client" on the server. This will restore
the old version of the component DLL.

To ensure that Outlook Express is not your "Default MAPI Client", follow these steps:

1. On the server computer, in Outlook Express 4, from the Tools menu, choose Options.

2. Click the General tab, and clear the "Make Outlook Express my default Simple MAPI client" check
box.

3. Click OK, and then click OK again.

4. Restart the server

----- STATUS -----

This is has been set up by Microsoft to do so and the above manual workaround is the only way one
can disable the Outlook Express from taking over the MAPI interface.

1310
www.mixtelematics.com

1310
 1311

------------------------------------------------------------------------------

KEYWORDS: SERVICE ONLINE CENTRE-POINT

1311
www.mixtelematics.com

1311
 1312
10.3.130 Knowledge Base Article 131

Article Number 131

Title HTTP Error 403 or 405 accessing SOL/CP

Created 1/20/2000 11:29:37 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 4/13/2000 11:58:55 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Data Pro Service Online, all versions

· Data Pro Centre-Point, all versions

----- SUMMARY -----

After installing Service Online or Centre-Point, and pointing your browser to the installed URL
(Typically http://localhost/centre-point), either HTTP error 405 or error 403 is displayed on the
browser.

----- MORE INFORMATION -----

This is a "Permission Denied" error, who's description varies from browser to browser.

----- CAUSE -----

When you create the Service Online or Centre-Point virtual directory in Internet Information Server,
the "Default Page" property contains only "Default.htm". (Unless the user has customised the IIS
default properties to include other pages) Service Online and Centre-Point do not contain a "Default.
htm" page, but rather a "Default.asp" page. Since the user does not have permissions to browse the
file structure of http://localhost/centre-point, and no "Default.htm" exists, the "Permission Denied"
error is displayed.

----- SOLUTION -----

Edit the properties of the Service Online or Centre-Point virtual directory. Click the "Documents" tab,
and check "Enable Default Document" (If this has not already been done). Click the "Add" button, and
enter "Default.asp".

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: SERVICE ONLINE CENTRE-POINT

1312
www.mixtelematics.com

1312
 1313
10.3.131 Knowledge Base Article 132

Article Number 132

Title FMTerminal Date Displays Incorrectly

Created 1/24/2000 9:43:39 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:22:58 PM

Last Modified By Tony Gois (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, all versions

· FM Kienzle Fleet Manager Terminal

----- SUMMARY -----

The date readout on the trip display of your FMTerminal unit may display one day after the actual
date.

----- MORE INFORMATION -----

For example, if the date is the 1st of March 2000 (01/03/00), the date displayed on your FMTerminal
unit will be the 2nd of March 2000 (02/03/00). This merely affects the display of the date: the data
downloaded into the FM2000 software will show the correct date.

----- CAUSE -----

This is caused by a known date problem with all FMTerminal units with serial numbers before 1432. It
is a leap year problem, and comes about from the fact that these units fail to recognise the year 2000
as a leap year. (I.e. the FMTerminal believes that the month of February 2000 has only 28 days;
where there are actually 29 days in this month.)

----- SOLUTION -----

Please download a new device driver file from ftp://ftp.centre-point.com/KBase/d15datefix.exe.

Execute this 38Kb self extracting archive, and extract the file called D15.DDM into your C:\Program
Files\Fleet Manager\FMTerminal directory. Then, re-initalise the plugs for all vehicle that exhibit this
problem. (Be sure to select "Build FMTerminal Menu" in the Initialise Plug wizard)

Once this has been done, and the FMTerminal units are seen to be displaying dates correctly, delete
the C:\Program Files\Fleet Manager\FMTerminal\D15.DDM.

----- STATUS -----

This is a known problem, and only occurs in a very small number of FMTerminal units, with serial
numbers 1000 to 1432.

------------------------------------------------------------------------------

KEYWORDS: FM2000 FMT

1313
www.mixtelematics.com

1313
 1314
10.3.132 Knowledge Base Article 133

Article Number 133

Title Centre-Point Fails to Unlock

Created 1/24/2000 4:38:07 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 1/24/2000 4:38:07 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Data Pro Centre-Point, all versions

----- SUMMARY -----

After installing a fresh copy of Centre-Point, and obtaining an unlocking code from Data Pro
Development (Pty) Ltd, the software fails to unlock.

----- MORE INFORMATION -----

While the software was being installed, numerous DLL files (most notably vb5db.dll and msvbvm60.dll
) are reported as being "Read Only" by the installset. This occurs most often if the user has Microsoft
Office 97 (Specifically, Microsoft Access 97) installed on the server computer, and/or any software
that was written in Microsoft Visual Basic 5 or 6.

If you then search for these files, you will see that, while they are no longer "Read Only", the "Last
Modified Date" has not been updated, showing that these files were not correctly overwritten.

----- CAUSE -----

This is caused by an error in the installation set, which causes "Read Only" files not to be overwritten,
even if "Yes" is clicked for each of these files.

----- SOLUTION -----

After ascertaining that the DLL files in question are no longer "Read Only", and that no other
applications are running, re-install Centre-Point. Enter your unlocking code once again.

----- STATUS -----

This problem is under investigation.

------------------------------------------------------------------------------

KEYWORDS: CENTRE-POINT

1314
www.mixtelematics.com

1314
 1315
10.3.133 Knowledge Base Article 134

Article Number 134

Title CPMail MAPI_E_TIMEOUT & MAPI_E_NOT_FOUND errors

Created 1/27/2000 1:25:00 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 5/23/2000 1:02:48 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Data Pro Centre-Point, all versions

----- SUMMARY -----

The CPMail service or application sometimes logs MAPI_E_TIMEOUT or MAPI_E_NOT_FOUND

errors in the application log. At other times, no errors will be displayed, but CPMail does not respond to
e-mails sent to it's mailbox account.

----- MORE INFORMATION -----

This problem will occur if you have installed a Service Pack onto your Windows NT Server/Workstation
(On which Centre-Point resides), followed by Windows Messaging/Centre-Point, but did not re-apply
the Service Pack.

----- CAUSE -----

This is caused by the fact that the Windows Messaging component on the Windows NT CD contains
older versions of files than those in the Service Pack. Thus, some files will be the most current
versions, and others will be outdated. This will cause the Centre-Point e-mail component to fail.

----- SOLUTION -----

After installing Windows Messaging, re-apply the Service Pack. This will update all the files that the
Windows Messaging component installed with the most current versions.

------------------------------------------------------------------------------

KEYWORDS: CENTRE-POINT SERVICE ONLINE

1315
www.mixtelematics.com

1315
 1316
10.3.134 Knowledge Base Article 135

Article Number 135

Title Vehicle trip report figures do not balance when there are days with no trips

Created 1/28/2000 9:59:00 AM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:28:26 PM

Last Modified By Tony Gois (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

Totals and summary figures on vehicle trip reports do not always balance.

The number of hours achieved by adding driving, standing and parking times should equal 24 ×
number of days in reporting period. If however, there are days in the reporting period on which there
were no trips this is not so as the parking time will be incorrect.

----- CAUSE -----

The data extraction for vehicle trip reports fails to take into account any days on which there were no
trips. This has the effect of reducing the parking time figure for the period by 24 hours for each day with
no trips.

----- SOLUTION -----

1. Please download the FMReports.zip file,

2. Restart you computer to ensure that none of the FM components are running.

3. Extract this file, and copy it to your Fleet Manager install directory

----- STATUS -----

This has been solved in the FMReports.mde file available, as well as in the FM Kienzle Fleet Manager
2001 software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 Report Parking

1316
www.mixtelematics.com

1316
 1317
10.3.135 Knowledge Base Article 136

Article
136
Number

Title Incorrect readings from EDM

Created 2/11/2000 3:24:36 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 9/7/2006 9:51:02 AM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, Service Release 1 (SR1) and above

· FM Kienzle Fleet Manager 2000, all versions

· FM Kienzle Fleet Manager 200 (Unit)

· FM Kienzle Fleet Manager 200e (Unit)

----- SUMMARY -----

After connecting an EDM 1404 unit (Electronic Diesel Consumption Measuring System) to your FM200 or
FM200e unit, incorrect data is returned to the Fleet Manager software. This continues to occur, even after
a reasonable period of approximately 1 week.

----- MORE INFORMATION -----

When connecting an EDM1404 unit to your FM200 or FM200e On Board Computer, there are two
methods that you may follow:

1. WITH DISPLAY

You may connect the FM Unit to a complete EDM 1404 system. This includes the EDM 1404 Compact
Display Unit (CDU), as well as the 1404 flowmeter. There is an output for an OBC as well as other
auxiliary units on the back of the CDU - which will be a yellow plug that comes with the display. The
FM200 and FM200e OBC's are fully compatible with this signal.

2. WITHOUT DISPLAY

The second method is to connect the FM200 or FM200e to the fuel flow meter only. In this case, you will
need to supply the flowmeter with the correct operating voltage of 6 to 16 Volt DC (Direct Current). The
output from the flowmeter should be calibrated from the software at 322 pulses per litre. This second
method requires special installation measures as described below.

Please see also KBA108: Incorrect Data from Fuel Recorder (EDM).

To view the FM SI document regarding the incorrect representation of EDM-data in the FM98/FM2000
software, refer to FM SI No 382011.

1317
www.mixtelematics.com

1317
 1318

----- CAUSE -----

Built into the output signal from the flowmeter is a control pulse. The control pulse is about a 0.7 Volts
which is large enough for the FM200 unit to be able to count. This results in incorrect data being passed
back to the Fleet Manager software, and displayed on the reports and Activity Timeline. If you are
connecting the fm200 directly to the EDM (not via the EDM display) as described in method 2 above,
measures must be taken to eliminate the control pulse.

----- SOLUTION -----

The best solution is to fit two 5.1V zener diodes. inline with the signal (Blue wire) from the EDM. The
zener diodes are fitted back to back (the stripes facing different directions). It does not matter in what
directions the zener diode is facing as long as they face in different directions. This will eliminate all
interference.

An alternate solution, which should work in most installations, is to use a 10K pull-up resistor between the
positive power supply (Black wire) and the output signal (Blue wire) of the fuel flowmeter will be sufficient
to eliminate the ripple.

Note: You should place the Zener diodes or resistor as close to the FM200(e) as possible, to make the
system less susceptible to noise.

Remember that if you are driving the FM200 input directly from an EDM display, the fm200 will measure
the flow accurately and the above solutions are not required!

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM200 FM200e FM98 FM2000

1318
www.mixtelematics.com

1318
 1319
10.3.136 Knowledge Base Article 137

Article Number 137

Discrepancies between Odometer Reading and Distance on Performance Summary

Title
Report

Created 2/11/2000 3:58:16 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 2/11/2000 5:28:25 PM

Last Modified By Wayne Davies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When viewing a Driver or Vehicle Performance Summary Report, you will see that there is a "Start
Odo" column, an "End Odo" column, and a "Distance" column. The "Distance" column on any given
line may not correspond to the value of the "End Odo" minus the "Start Odo".

----- CAUSE -----

There are two possible causes of this problem:

1. Since the "Start Odo" reflects the unit's odometer reading at the start of the first trip in the summary
period, and the "End Odo" reflects the unit's odometer reading at the end of the last trip in the
summary period, it is possible that the unit's odometer reading was reset sometime within this
period. This would have been done via either the Inialise Plug Wizard, or the Set Odometer option
on the Code Plug menu.

2. The "Distance" column on this report is derived from the sum of the distances of each individual trip
within the summary period. However, the FM200 unit stores distance to a resolution of 100m. Thus,
the sum of each individual trip distance may differ by a margin of approximately 1% from the actual
figure. When viewing a report over a large summary period, these 1% discrepancies may produce
a relatively large discrepancy in the final figure.

----- SOLUTION -----

Neither of the above causes are the result of errors in the Fleet Manager products. The solution,
therefore, is to make sure that it is known when the unit's odometer reading was reset and to
understand that if the unit's odometer reading was not reset during the sumary period, a discrepency
can still occur due to the fact that the unit records trip distance rounded to the nearest 100m.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

1319
www.mixtelematics.com

1319
 1320

KEYWORDS: FM100 FM200 FM200e FM98 FM2000

1320
www.mixtelematics.com

1320
 1321
10.3.137 Knowledge Base Article 138

Article
138
Number

Title Error 429 During Installation or Trying to Open the Software

Created 2/15/2000 12:11:54 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 12/8/2000 11:58:30 AM

Last Modified By Mischa Gottwals (Siemens FM Trading GmbH - Germany)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

· Fleet Manager AutoPoll Client ("Full Product" only), all versions

· Data Pro Language Translator, all versions

· CITAS 2010 to Fleet Manager 98, all versions

· FM Object Finder Extension for FM2000, all versions

· FM200 Tacho Dump Utility Extension for FM2000, all versions

· Data Pro Service Online, all versions

· Centre-Point Service Tracker, all versions

----- SUMMARY -----

When installing any of the above products, while another of the above products is running, you will get an
error 429 (ActiveX Component Can't Create Object) error, either during the installation, or when trying to
access the software.

----- MORE INFORMATION -----

For the Fleet Manager 98 software, the error will occur the first time the user attempts to run the Fleet
Manager Client application; for the Centre-Point and Service Online applications, the error will occur the first
time a user attempts to connect to the appropriate web site.

For the Fleet Manager 2000 software, the error will occur during database creation/upgrade (FMCreateDB2.
Exe), immediately after the final restart. For all other applications, the error will occur the first time the user
starts the system.

----- CAUSE -----

The above Data Pro Development software products all make use of generic components (DLL and OCX
files). If, during the installation, one of these files is in use (As is the case when another of the above

1321
www.mixtelematics.com

1321
 1322

products is running at the time), the installation set marks it to be overwritten the next time the computer is
restarted. Many of these components use long file names, and since the Microsoft Windows technology for
overwriting such files does not permit the use of such file names, these will be re-named to 8.3 (MS-DOS)
format file names.

----- SOLUTION -----

Search your computer for any of the 8.3 file names in the following table, and manually re-name any that you
find to their 32-bit counterpart. Please remember that you cannot have any of the above products open
during this time.

8.3 File 32-Bit File

DPERRO~?.DLL DPErrorHandler.Dll

DPLANG~?.DLL DPLanguage.Dll (If using FM98 or Service Online)

DPLANG~?.DLL DPLanguage2.Dll (If using FM2000, FMAPC or Centre-Point)

DPMSGH~?.DLL DPMsgHook.Dll

DPPOPU~?.OCX DPPopupMenu2.Ocx

DPSUBT~?.DLL DPSubTimer2.Dll

In order to prevent this error from occuring in future, it is advisable to ensure that all applications and non-
critical services are stopped, prior to running an installation program.

----- STATUS -----

This is unfortunately a problem in the method in which Microsoft Windows handles locked files.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 SERVICE ONLINE CENTRE-POINT FMAPC FMFIND FMTACHODUMP

DPLANGTR

1322
www.mixtelematics.com

1322
 1323
10.3.138 Knowledge Base Article 139

Article Number 139

Title Error -113 During Installation of Fleet Manager on Eastern OS

Created 2/15/2000 1:43:44 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 5/17/2000 10:28:03 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When attempting to install the Fleet Manager 98 software onto an Eastern version of Windows (For
example, a Korean version of Microsoft Windows 98), error -113 may occur in the installation set. The
error will occur in the final stages of the setup program, when the files are being copied to your hard
disk.

----- MORE INFORMATION -----

The details of the error are as follows:

ComponentMoveData had the following error:

Media Name: data

Component: Program Files

File Group: Program Files

File: Español.ecf (Espanol.ecf)

Error Number: -113

After this has been displayed, a message box will be displayed, reading:

An error ocurred during the move data process: -113

Component: Program Files

File Group: Program Files

File name: D:\Español.ecf

(Replace "D:\" above with the letter of your CD-ROM drive.) Following this, another message box is
displayed, which reads:

1323
www.mixtelematics.com

1323
 1324

An error has occurred that prevents setup from continuing. Setup will end now.

The installation then terminates.

----- CAUSE -----

The Eastern Operating Systems use a specialised, "double byte" character set that is incompatible
with our, Western character set. The special "ñ" character (An "n" with an accent marker) in Español.
ecf, for example, is thus interpreted by the Operating System as the first part of a double byte
character. These double byte characters cannot be displayed using the Western Character set - and
no files containing these double byte characters exist on the Fleet Manager 98 CD.

----- SOLUTION -----

Unfortunately, this is a problem with the Eastern versions of the Microsoft Windows Operating System,
and there is no known workaround or solution at this time.

----- STATUS -----

This problem is under investigation.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1324
www.mixtelematics.com

1324
 1325
10.3.139 Knowledge Base Article 140

Article Number 140

Title Date Capturing and the CITAS 2010 Hand-Held

Created 2/15/2000 4:47:11 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 2/15/2000 4:47:11 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· CITAS 2010, version 2.00 and higher

----- SUMMARY -----

This article describes the process of entering dates into the CITAS 2010 hand-held diagnostic unit,
in order for the correct year (For example, 2000) to be downloaded into the software and displayed
on the "Trip Display". Note that you must be using version 2.00 of the software, and all units have to
be re-programmed with the binary data files (BIN) that are supplied with this version.

----- MORE INFORMATION -----

Dates are entered into the 2010 hand-held in the format YYMMDD (two digit year, two digit month,
two digit day). The exception to this rule is when the current year is 2000 or beyond.

When entering dates, where the year is greater than "99", numbers from 100 upwards should be
used. For example, entering "990112" would assume the 12th of January, 1999. However, entering
1000215 would assume the 15th of February, 2000. Likewise, entering "1011210" would assume the
10th of December, 2001.

------------------------------------------------------------------------------

KEYWORDS: CITAS 2010

1325
www.mixtelematics.com

1325
 1326
10.3.140 Knowledge Base Article 141

Article Number 141

Title Having Centre-Point 'Strip Out' Original Message Texts

Created 2/24/2000 8:48:31 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 2/24/2000 9:10:40 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Centre-Point Service Tracker, all versions

----- SUMMARY -----

When a user replies to a system generated e-mail, that user's comments are automatically added to
the relevant service request. Whenever possible, the "Original Message" portion is removed from the
message before it is added as comments.

----- MORE INFORMATION -----

After a default installation, Centre-Point is already configured to strip out the "Original Message" texts
added by the English and German versions of Microsoft Outlook.

This article explains how to go about customising this functionality, by "teaching" Centre-Point about
other products' "Original Message" formats.

----- SOLUTION -----

The setting that controls this is stored in the Windows System Registry. On the server on which
Centre-Point is installed, open a Registry Editing Utility (Such as regedit.exe). Browse to the following
Key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CPMail\Parameters
\OriginalMessageText

By default, this value contains the following string:

-Original Message-|-Ursprungliche Nachricht-

This is a list of strings that various mailers use to denote the original message. When processing
comments, the Centre-Point Mail Server (CPMail) ignores any text that comes below one of these
strings, as well as these strings themselves.

You should modify this list to include other strings as applicable. For example, if your mailer puts the
original message under "- Original Message -", then you would need to modify the value as follows:

-Original Message-|-Ursprungliche Nachricht-|- Original Message -

----- STATUS -----

1326
www.mixtelematics.com

1326
 1327

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: CENTRE-POINT

1327
www.mixtelematics.com

1327
 1328
10.3.141 Knowledge Base Article 142

Article Number 142

Title APCLog.txt File Grows Very Large

Created 2/24/2000 12:46:25 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 2/24/2000 12:46:25 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager AutoPoll Client, all versions

----- SUMMARY -----

The Fleet Manager AutoPoll Client creates a log file (APCLog.txt) of all its activities while running. If left
unchecked, this file can tend to grow very large, rather quickly.

----- MORE INFORMATION -----

The log file continues to grow whenever the AutoPoll Client is transferring, and so the speed of growth is
greatly increased if you use the "Transfer Continuously" option from the configuration window.

----- CAUSE -----

Each time the software transfers data, it logs at least three entries per folder that it processes:

Processing Folder "AutoPoll" (Checking for errors in download)

Processing Folder "AutoPoll" (Checking for FM100 Data)

Processing Folder "AutoPoll" (Checking FM200/FM200e Data)

In addition to this, a line is written to the log whenever the software actually transfers data from a .dat
or .ini file, or finds an error in the download of a .dat or a .ini file.

With "Transfer Continuously" checked, this process happens each second, and so the log file may be
megabytes in size after only a short time.

----- SOLUTION -----

When you click "View Log" from within the AutoPoll Client, the APCLog.txt file opens in a standard text
editor. You may clear this log file out, close and save it, without having to exit the AutoPoll Client.

----- STATUS -----

A new feature is planned for the next release of the AutoPoll Client, which will allow the user to control
the growth of this log file.

------------------------------------------------------------------------------

1328
www.mixtelematics.com

1328
 1329

KEYWORDS: FM2000 FM98 FMAPC

1329
www.mixtelematics.com

1329
 1330
10.3.142 Knowledge Base Article 143

Article Number 143

Title How to Clear the Memory from an FM100 Unit

Created 2/24/2000 2:42:45 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 1:49:40 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 100 (Unit)

----- SUMMARY -----

Many customers need a method of clearing the memory of their FM100 units. The Fleet Manager Dealer
Utility (FMDealer) provides an easy method of clearing an FM100 memory.

----- SOLUTION -----

To clear the FM100 unit's memory:

1. Run FMDealer

2. Insert the green vehicle plug that you would like to use to clear the unit into the download module

3. From the codeplug menu select Clear Memory plug -> FM100

4. Before inserting this plug into your FM100 unit, please ensure that it has been unplugged.

5. Insert the plug, and re-connect the FM100 to the harness. After a few seconds, you will hear a beep
from the unit, indicating that it has been cleared.

6. Unlike the FM200, this plug remains a clear plug until such time as it is formatted and re-initialised.
This can only be done through the Fleet Manager Dealer Utility.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM SI FMDealer Clear Memory

1330
www.mixtelematics.com

1330
 1331
10.3.143 Knowledge Base Article 144

Article Number 144

Title Noisy FMTerminal Units

Created 2/25/2000 8:56:17 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:30:02 PM

Last Modified By Tony Gois (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager Terminal

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

Some FMTerminals are noisy under certain backlight settings.

----- MORE INFORMATION -----

A high pitched tone can be heard on some FMTerminals while the backlighting is on. The level of the
tone is dependant on the backlight setting and the vehicle battery voltage.

----- CAUSE -----

This is caused by errors in the backlighting control of the FMTerminal.

----- SOLUTION -----

A new device driver, which improves the backlighting control, is available for downloading from ftp://
ftp.centre-point.com/KBase/d0noisefix.exe. Download and execute this file (32 k), and extract it's
contents into your C:\Program Files\Fleet Manager\FMTerminal directory. Then, re-initialise the plugs
for all vehicles that exhibit this problem. (Be sure to select "Build FMTerminal Menu" in the Initialise
Plug wizard).

Once this has been done, and the FMTerminal units are functioning correctly, delete the C:\Program
Files\Fleet Manager\FMTerminal\D0.DDM.

----- STATUS -----

This problem has been solved in the latest firmware. It will affect all FMTerminal units with serial
numbers up to and including 1520.

------------------------------------------------------------------------------

KEYWORDS: FMT noise FM2000

1331
www.mixtelematics.com

1331
 1332
10.3.144 Knowledge Base Article 145

Article Number 145

Title FMTerminal Display Unreadable

Created 2/25/2000 10:29:35 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 5/9/2000 10:30:48 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager Terminal

----- SUMMARY -----

The FMTerminal display contrast can become too dark or too light under temperature extremes.

----- MORE INFORMATION -----

The FMTerminal Liquid Crystal Display (LCD) contrast is sensitive to temperature extremes. A high
temperature, or prolonged exposure to direct sunlight, can cause the contrast level to increase,
resulting in the screen becoming dark and unreadable.

----- CAUSE -----

This is caused by the sensitivity of the LCD display to extremely high temperatures.

----- SOLUTION -----

Pressing the zero “0” key in any FMTerminal menu will activate the Display Control screen. While in
the Display Control screen, three default display settings can be sequentially activated by repeatedly
pressing the zero "0". This is useful when the display contrast is very dark or very light and allows the
operator to easily find a setting which is readable.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FMT

1332
www.mixtelematics.com

1332
 1333
10.3.145 Knowledge Base Article 146

Article Number 146

Title 'Invalid DDR Path Specified' even if it exists

Created 2/25/2000 11:52:37 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 4/17/2000 2:08:50 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

If you alter the "FM200 Device Driver Location" from the "Options" dialog, and Apply, you will receive a
message, stating that the path could not be found.

----- MORE INFORMATION -----

The error message that is displayed for FM2000 is as follows:

The path specified for the FM200 device drivers does not exist. Please specify an existing folder.

For FM98:

The location for FM200 Device Driver Location does not exist. Do you wish to create this folder?

Conversely, if you specify a folder that does not exist, the Options dialog will return no errors.

----- CAUSE -----

There is a logic error inherant in the above software products, which causes the validation of the path
to fail if it does exist; the same error causes this validation to succeed if the path does not exist.

----- SOLUTION -----

The solution to this problem involves changing an entry in the Windows system registry. Please ensure
that you have taken all necessary precautions before following these steps, as incorrect modification of
the registry can render your computer unbootable.

1. Open a registry editing tool (Such as regedit.exe)

2. a) If you are using FM2000, browse to the following location: HKEY_LOCAL_MACHINE

\SOFTWARE\Data Pro Development (Pty) Ltd\Fleet Manager Client\Options.

b) If you are using FM98, browse to the following location: HKEY_CURRENT_USER\SOFTWARE

\Data Pro Development (Pty) Ltd\Fleet Manager Client\Options.

3. Locate the value under this key, called DDRPath, and modify its contents to point to the correct
path.

1333
www.mixtelematics.com

1333
 1334

Note: If you are using FM98, then the above change needs to be made for each Windows user using
the system.

----- STATUS -----

This problem was not discovered in time to be corrected on the first release of the FM2000 CD-ROM. It
will be solved in the next version.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1334
www.mixtelematics.com

1334
 1335
10.3.146 Knowledge Base Article 147

Article Number 147

Title No DDR's found, even if they exist

Created 2/25/2000 1:44:36 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:30:46 PM

Last Modified By Tony Gois (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When attempting to upload device drivers to an FM200/FM200e plug, the system reports that no
device drivers could be found. You can confirm that the path to the device drivers does exist, and
contains a list of .DDR files.

----- MORE INFORMATION -----

This problem occurs in Step 2 of the "Upload Device Drivers" wizard, immediately after you click
"Next". It only occurs on computers running Microsoft Windows 95, and the exact error message is
as follows:

No Device Driver files were found in the specified directory. Please specify another directory.

----- CAUSE -----

This is caused by an oversight in the application, which passes "\\" (A double backslash) in the path,
when searching for .DDR files. Windows 98, Windows NT, and Windows 2000 are able to correctly
convert this to a single backslash internally, but Windows 95 is not.

----- SOLUTION -----

Download the latest version of the FMDealer software from the http://www.mixtelematics.com
website.

To view the FM SI document regarding this issue, refer to FM SI No 382010.

----- STATUS -----

This problem was unfortunately not identified in time for the intial release of the FM2000 CD-ROM. It
will be solved in the next version.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1335
www.mixtelematics.com

1335
 1336
10.3.147 Knowledge Base Article 148

Article Number 148

Title 'Allowed to Login' Query does not show Organisation Contacts

Created 2/29/2000 5:30:37 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 12:31:21 PM

Last Modified By Tony Gois (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Centre-Point Service Tracker, version 3.01 and below

----- SUMMARY -----

When viewing contacts who are allowed to login, the system only shows Service Organisation
Contacts or System Administrators. Organisation Contacts who have been allowed to login are not
displayed.

----- MORE INFORMATION -----

To duplicate this behaviour, click the following links in the tree view on the right: Contact
Management, Contacts, Lists, Contacts Allowed to Login. If you have allowed any contacts with a
contact type of "Organisation Contact" to login, they will not be displayed in the list.

----- CAUSE -----

This is caused by an error in an internal query of the Centre-Point database.

----- SOLUTION -----

Download the latest DBUpdate utility (196k) from ftp://ftp.centre-point.com/KBase/dbupdate.exe.

Stop the Centre-Point Mail Server (CPMail), and Centre-Point Auto Escalation Server (CPAE), as
well as the web site on which Centre-Point resides. Copy the DBUpdate.exe into the Centre-Point
directory (Typically C:\Program Files\Centre-Point) on the server, and execute it.

Start the services and the web site again.

----- STATUS -----

This problem will be solved in the next release of the Centre-Point system.

------------------------------------------------------------------------------

KEYWORDS: CENTRE-POINT

1336
www.mixtelematics.com

1336
 1337
10.3.148 Knowledge Base Article 149

Article Number 149

Title Report/Graph Criteria: From Date Greater Than To Date

Created 3/7/2000 3:38:32 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 3/7/2000 3:41:37 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· CI Data, all versions

· Shurlok EV100, all versions

· CITAS 2010, all versions

· FM Kienzle Fleet Manager 100, all versions

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

The above products all allow you to specify an "Start Date" greater than the "End Date", when
specifying criteria for reports and graphs. In this case, the software will internally "swap" the "Start"
and "End" dates before actually generating the report or graph. You will thus still get the information
that you expect.

----- MORE INFORMATION -----

To simulate this behaviour from within the 16-bit products (i.e. CI Data, EV100, CITAS 2010, or
FM100), click the "Reports" menu, and ask for a report or graph. (From the CITAS 2010, you need to
click the "Graphs" menu to generate a graph) Enter (for example) "07/03/2000" in the first date field,
and (for example) "01/01/2000" in the second. If there is any data for the report or graph, between
01/01/2000 and 07/03/2000, the data will still be displayed correctly. (Even though the first date is
greater than the end date)

To simulate this behaviour from within the FM98 or FM2000 products, click "Reporting", and ask to
generate a Vehicle or Driver Graph or Report. In the step which says "Include Information for the
period:", enter (for example) "07/03/2000" in the first date field, and (for example) "01/01/2000" in the
second. If there is any data for the report or graph, between 01/01/2000 and 07/03/2000, the data
will still be displayed correctly (Even though the first date is greater than the end date).

This same behaviour is true for times. If the first date/time combination is "07/03/2000 13:00:00", and
the second is "07/03/2000 06:00:00", then any data between 06:00 and 13:00 on the 07/03/2000 will
be returned by the report or graph.

----- STATUS -----

1337
www.mixtelematics.com

1337
 1338

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM200 FM2000 FM98 EV100 CIDATA CITAS 2010

1338
www.mixtelematics.com

1338
 1339
10.3.149 Knowledge Base Article 150

Article Number 150

Title 'Type Mismatch' Error clicking on the International Tab

Created 3/7/2000 5:54:16 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 3/8/2000 8:39:02 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Shurlok EV100, version 1.55 (SR1) and above

· CI Data, all versions

· FM Kienzle Fleet Manager 100, all versions

----- SUMMARY -----

If you click Setup, Options, and then click the "International" tab, error 13 (Type mismatch) is
displayed.

----- MORE INFORMATION -----

The exact wording of the error message is as follows:

An unexpected error has occurred in move to new tab -

13: Type mismatch

The error will occur if you install the software, while your Microsoft Windows Regional Settings is
set to one of the "German" locales. If you then switch your regional settings to one of the "English"
locales, this error will occur when you click on the "International" tab.

----- CAUSE -----

This is caused by errors in the above software products.

----- WORKAROUND -----

Either always install the software in one of the "English" locales, or always use the software in the
same locale as you installed it.

----- STATUS -----

This problem is being investigated.

------------------------------------------------------------------------------

KEYWORDS: EV100 CIDATA FM100

1339
www.mixtelematics.com

1339
 1340
10.3.150 Knowledge Base Article 152

Article Number 152

Title Contact No Longer Has a Username or Password Defined

Created 3/8/2000 3:02:54 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 3/8/2000 3:02:54 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Centre-Point Service Tracker, all versions

· Data Pro Service Online, all versions

----- SUMMARY -----

When a contact tries to log in to the system, he gets an error message, stating that his login name
could not be found. Nobody else in the system has removed this contact's login name.

----- MORE INFORMATION -----

The error message that is displayed when the contact tries to log in is as follows:

Invalid login name supplied.

You can confirm that the contact's login name was spelt correctly, and the contact was previously
allowed to login.

It occurs when the contact in question is a Service Organisation Contact or System Administrator. If
you log in as a different contact, and view the contact's details, you will note that the details were last
modified by another contact, with Organisation Contact security level.

----- CAUSE -----

Centre-Point allows Organisation Contacts to modify other contacts from his own organisation. He
may monitor telephone numbers, addresses, etc, but he may not monitor the Allowed To Login flag, or
the Login Name and Password fields for contacts that are of a higher security level than himself. (i.e.
He may not allow or disallow a Service Organisation Contact or System Administrator to log in, or
modify such a contact's user name or password)

Because of this, the Allowed to Login and User Name fields are seen as read only. Additionally, the
Password field is not displayed, when editing contacts of a higher security level than himself. However,
the problem occurs when the contact clicks Modify Record: the contact record is re-written to the
database, without the Allowed To Login, User Name, or Password fields. They are effectively
removed.

----- SOLUTION -----

Keep your Admin user's password in a safe place, and do not allow any other contacts to belong to the
same organisation as this user. This will ensure that at least one System Administrator is allowed to

1340
www.mixtelematics.com

1340
 1341

log in at all times.

----- STATUS -----

This problem is under investigation.

------------------------------------------------------------------------------

KEYWORDS: SERVICE ONLINE CENTRE-POINT

1341
www.mixtelematics.com

1341
 1342
10.3.151 Knowledge Base Article 153

Article Number 153

Title Trip Report or Driving Errors Report Prints Blank or Generates an Error Message

Created 3/14/2000 4:06:19 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 3/15/2000 11:58:06 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 100, all versions

· Shurlok EV100, all versions

· CI Data, all versions

----- SUMMARY -----

If you do a Daily Trip report, in the FM100 software, the report displays blank. If you then select
individual vehicles (Or a vehicle other than the one that is causing the problem), the report may
appear correct.

----- MORE INFORMATION -----

This problem also occurs in the FM100 Detail Trip report and Driving Errors report, as well as the
EV100 and CI Data Trip reports. However, in these cases, an actual error message is displayed:

An unexpected error has occurred in extract for Driver Error -

3315: Field 'DrvError.dtTripStart' can't be a zero-length string.

----- CAUSE -----

This is caused by the fact that one of the vehicles in your selection criteria, for the specified period,
has a trip which starts at exactly midnight (00:00:00 or 12:00:00 AM) on a particular day. This is
used internally by the software as a "control value", which instructs the report to stop processing at
this point.

----- SOLUTION -----

This problem is under investigation.

----- STATUS -----

This problem is under investigation.

------------------------------------------------------------------------------

KEYWORDS: FM100 EV100 CIDATA

1342
www.mixtelematics.com

1342
 1343
10.3.152 Knowledge Base Article 154

Article Number 154

Title I can't find the FM Upgrade+ Registration Card on the FM2000 CD

Created 3/17/2000 10:55:26 AM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 11:26:44 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000

· FM Upgrade+

----- SUMMARY -----

The document containing the FM Upgrade+ Registration Card can not be found on the FM2000 CD.

----- CAUSE -----

There is no copy of this document on the FM2000 CD.

----- SOLUTION -----

You should have received printed English and German versions of the registration card in both your
software box and your FM Upgrade+ package.

If you no longer have these registration cards you can download the English version in Adobe
Acrobat format here.

------------------------------------------------------------------------------

KEYWORDS:

FM2000 UPGRADE+

1343
www.mixtelematics.com

1343
 1344
10.3.153 Knowledge Base Article 155

Article Number 155

Title CPMail Memory Usage Increases

Created 3/17/2000 5:00:28 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 3/17/2000 5:16:02 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Centre-Point Service Tracker, all versions

----- SUMMARY -----

When the Centre-Point system has been running for a long time, and the Centre-Point Mail Server
(CPMail) has been sending out mail as it should, you may notice that the memory usage of the Mail
component increases.

----- MORE INFORMATION -----

If you are running Windows NT or Windows 2000, you can open the Task Manager, by clicking . If
you observe the "Memory Usage" of the "CPMail.exe" process, you will notice that it slowly
increases over time.

----- CAUSE -----

The CPMail component uses a Microsoft technology, called "Active Messaging v1.1". This
technology has a known "Memory Leaks", which will cause the CPMail component to slowly
consume more and more memory. For information about this problem, please see the Microsoft
Knowledge Base Article at http://support.microsoft.com/support/kb/articles/Q171/4/27.ASP?
LNG=ENG&SA=ALLKB&FR=0.

----- SOLUTION -----

The only solution at this time is to periodically stop and start the CPMail application (Win9x), or the
Centre-Point Server service (WinNT)

----- STATUS -----

This problem is under investigation. We have determined that this "Memory Leak" has been solved
in the next release of Active Messaging, called "CDO" (Collabarative Data Objects). However, CDO
is not Royalty Free Re-distributable.

------------------------------------------------------------------------------

KEYWORDS: CENTRE-POINT

1344
www.mixtelematics.com

1344
 1345
10.3.154 Knowledge Base Article 156

Article Number 156

Title Error 50504 when trying to generate a report

Created 3/23/2000 11:16:22 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 11:11:26 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 100, version 1.20 (SR4)

----- SUMMARY -----

When trying to generate a report, error 50504 may be displayed. It will occur after just installing the
full version of FM100 v1.20, and selecting "Letter (8 1/2 x 11 in)" when asked: "Please specify the
type of paper to be used for reports:", in the last step of the installation wizard.

----- MORE INFORMATION -----

The exact wording of the error message is:

An unexpected error has occurred in Process report -

50504: Invalid Report file name, C:\FM100\LTRRPT\TripData.rpt

You may replace the TripData.rpt file name above with any other .rpt file name in the system. The
file described above applies only to the Vehicle or Driver Trip Report.

It will only occur if there is data for the report that you are trying to generate, during the "Opening..."
phase of the report generation.

In addition, if you make any change on the Options window, and click Save, you will receive the
following message:

The Report File Path does not exist. Please enter the path to the directory containing the FM100
report templates.

If you look in your FM100 directory (Typically C:\FM100), you will notice that a required subdirectory,
"LTRRPT" has not been created. This is the directory containing the U.S. Letter report templates.
(Required to generate reports in the U.S. Letter format)

----- CAUSE -----

This is caused by the fact that the full install of version 1.20 of the FM100 software does not
correctly create the "LTRRPT" folder, nor does it copy the U.S. Letter report templates.

----- SOLUTION -----

Install the latest "Update Only" version of the FM100 software. The latest version at the time of this

1345
www.mixtelematics.com

1345
 1346

article is SR4, but you can always download the latest version from the Fleet Manager Lite
download page.

----- STATUS -----

This problem has been solved in the version 2 of the FM100 software.

------------------------------------------------------------------------------

KEYWORDS: FM100

1346
www.mixtelematics.com

1346
 1347
10.3.155 Knowledge Base Article 157

Article Number 157

Title Administrator Program can't lock Database

Created 3/24/2000 10:34:45 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 3/24/2000 10:54:53 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1) and above

· FM Kienzle Fleet Manager 200, version 4.00.0002 (FMAdmin2.exe version)

----- SUMMARY -----

When trying to lock the Fleet Manager database using the Admin program, you keep getting a
message, saying that the database could not be locked. You can confirm that there is nothing
accessing the database.

----- MORE INFORMATION -----

The error message that is displayed is as follows:

For FM2000:

The FM2000 Administrator could not lock the database. Please make sure that all FM2000 Clients are
closed

For FM98:

The FM 98 Administrator could not lock the database. Please makre sure that all FM 98 Clients are
closed.

You are offered a choice to "Retry" or "Cancel", but no matter how many times you Retry, the message
keeps getting displayed.

If you click "Cancel", and then double click "Server Options", you will notice that the database (As
displayed under Server Database File) does not exist. Furthermore, the path that the database is
located in does not exist.

----- CAUSE -----

This is caused by errors in the Fleet Manager Administrator program, that causes it to fail to lock a
database who's physical disk path does not exist.

----- SOLUTION -----

Re-create the path specified in the Server Database File property. Copy the Fleet Manager database
into this location and re-name it accordingly. You will now be able to lock the database, and change it to

1347
www.mixtelematics.com

1347
 1348

point to the new location. You may then re-delete the path.

----- STATUS -----

This problem will be solved in the next update to the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FMADMIN FMADMIN2

1348
www.mixtelematics.com

1348
 1349
10.3.156 Knowledge Base Article 158

Article Number 158

Title Daylight Savings Not Updating

Created 3/24/2000 11:52:25 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 1:57:06 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, version 4.00.0013 (FMClient2.exe version)

----- SUMMARY -----

If you change any of the information on the Daylight Savings tab of the Options dialog, without
modifying the Enabled property, the change will not take effect.

----- MORE INFORMATION -----

The Options that exhibit this problem are:

1. Daylight savings starts on (Date and Time)

2. and ends on (Date and Time)

3. Adjust by (Hours)

----- CAUSE -----

This is caused by errors in the Fleet Manager Client application, when saving Daylight Savings
information to the server.

----- SOLUTION -----

When making any change to the Daylight Savings properties, simply disable and re-enable Daylight
Savings. (i.e. Uncheck and check the "Enable Daylight Savings" checkbox) This will tell the software to
update these details.

----- STATUS -----

This problem was solved in FM Kienzle Fleet Manager 2000 Second Edition.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1349
www.mixtelematics.com

1349
 1350
10.3.157 Knowledge Base Article 159

Article Number 159

Title Can't Upgrade Database After SR1a Install

Created 4/3/2000 11:37:07 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 11:07:57 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, FMServer version 3.10 (SR1a)

----- SUMMARY -----

During the installation of SR1a, when trying to upgrade the database, you receive an error message,
stating that the database is too old to be upgraded. If you try and run FMCreateDB.Exe manually, you
will receive the same error message.

----- MORE INFORMATION -----

The exact wording of the error message is as follows:

The database C:\Program Files\Fleet Manager\FMServer.mdb is too old to be upgraded. Please create
a new database.

Replace C:\Program Files\Fleet Manager\FMServer.mdb, above, with the full path to your Fleet
Manager database. The error will occur during the Checking Database Integrity phase of the upgrade.
When you click OK for that error message, you will receive another, which says:

WARNING: You will not be able to run the FM Kienzle Fleet Manager 98 until the database has been
successfully updated.

The error will occur if you attempt to install the FM98 SR1a Update over a release version (Version
2.10) of the software.

----- CAUSE -----

A database from version 2.10 (First Release) of the FM98 software cannot be upgraded. This is due to
the fact that SR1a is a "Server Only" upgrade, which is intended to be applied only to existing FM98
SR1 (Version 3.00) installations.

----- SOLUTION -----

Upgrade to the latest version of the Fleet Manager software available. (This is FM Fleet Manager 2001
or later).

----- STATUS -----

This functionality is by design.

1350
www.mixtelematics.com

1350
 1351

------------------------------------------------------------------------------

KEYWORDS: FM98 FMCREATEDB

1351
www.mixtelematics.com

1351
 1352
10.3.158 Knowledge Base Article 160

Article Number 160

Title What's New in CI Data version 2.0?

Created 4/3/2000 11:48:24 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 11:05:53 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· CI Data Millennium, version 2.0

----- SUMMARY -----

The following is a list of what's new in CI Data Millennium (version 2.0).

The latest version of CI Data Millennium software can be downloaded from the CI Data FTP
download site

· Multi Plug support. This functionality requires version 1.5 of the CI Data hardware unit. The multi
data plug ("Multi Plug") cannot disarm a vehicle and is by default unassigned. As soon as this plug
is inserted into a vehicle (which has a version 1.5 CI Data unit installed), the plug will be assigned
to that vehicle. There is an option to have the Download automatically reset these plugs after a
download.

· Enhanced Service Reminders. Service reminders have been expanded to enable Duration based
reminders for vehicles that have low mileage. For example, a vehicle that does not travel the
10000Km (±6000miles) service interval in a year, should be serviced after 12 months. You may set
this as an option for the vehicle.

· Fuel Usage. You may now enter fuel usage data, where the quantity/volume is in a different
measurement unit to the odometer reading (e.g. Miles and Litres).

· Consumption Types. You may now select the Fuel Consumption Type, for reporting purposes. (i.e.
litres/100Km or Km/litre)

· Reporting Groups. This allows a report to be printed for a specific group of vehicles or drivers,
instead of All or only one at a time. The reports and graphs that are able to take advantage of this
functionality are: Trip Report, Operating Statistics Report, Driver Score Report, Fuel Consumption
Report, Violation Summary Graph, Driver Score Graph and Fuel Consumption Graph.

· Start Each Vehicle or Driver on a new page. This option has been added to the criteria for most
reports. This will optionally cause the report not to print data for more than one vehicle or driver on
the same page. The reports and graphs that are able to take advantage of this functionality are:
Trip Report, Operating Statistics Report, and Fuel Consumption Report.

· Detailed reporting. CI Data Millennium allows full "detail" mode for the Trip Report. This allows
each individual trip to be displayed on a separate line.

· Detailed Export. The Export function now exports each individual trip.

1352
www.mixtelematics.com

1352
 1353

· Activity Timeline. An Activity Timeline graph has been added. This graphically shows trips for a
selected day, and allows you to click on a trip to see detailed information about that trip.

· Windows NT/2000 support. With the installation of the CI Data Millennium Windows NT and
Windows 2000 Download Drivers (709 kb), CI Data Millennium is now fully compatible with
Microsoft Windows NT 4.0 and Microsoft Windows 2000.Delete Data Correction. There was an
error, whereby if you deleted data for a vehicle in the future, the Last Trip Information for the
vehicle did not get updated. This has been corrected.

------------------------------------------------------------------------------

KEYWORDS: CIDATA

1353
www.mixtelematics.com

1353
 1354
10.3.159 Knowledge Base Article 161

Article Number 161

Title What's New in Shurlok EV100 version 2.0?

Created 4/3/2000 3:42:15 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 11:04:13 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· Shurlok EV100, version 2.0

----- SUMMARY -----

The following is a list of what's new in Shurlok EV100 version 2.0.

The latest version of Shurlok EV100 software can be downloaded from the EV100 FTP download site

· Multi Plug support. This functionality requires version 1.5 of the EV100 hardware unit. The multi data
plug ("Multi Plug") cannot disarm a vehicle and is by default unassigned. As soon as this plug is
inserted into a vehicle (which has a version 1.5 EV100 unit installed), the plug will be assigned to
that vehicle. There is an option to have the Download automatically reset these plugs after a
download.

· Enhanced Service Reminders. Service reminders have been expanded to enable Duration based
reminders for vehicles that have low mileage. For example, a vehicle that does not travel the
10000Km (±6000miles) service interval in a year, should be serviced after 12 months. You may set
this as an option for the vehicle.

· Fuel Usage. You may now enter fuel usage data, where the quantity/volume is in a different
measurement unit to the odometer reading (e.g. Miles and Litres).

· Consumption Types. You may now select the Fuel Consumption Type, for reporting purposes. (i.e.
litres/100Km or Km/litre)

· Reporting Groups. This allows a report to be printed for a specific group of vehicles or drivers,
instead of All or only one at a time. The reports and graphs that are able to take advantage of this
functionality are: Trip Report, Operating Statistics Report, Driver Score Report, Fuel Consumption
Report, Violation Summary Graph, Driver Score Graph and Fuel Consumption Graph.

· Start Each Vehicle or Driver on a new page. This option has been added to the criteria for most
reports. This will optionally cause the report not to print data for more than one vehicle or driver on
the same page. The reports and graphs that are able to take advantage of this functionality are: Trip
Report, Operating Statistics Report, and Fuel Consumption Report.

· Windows NT/2000 support. With the installation of the Shurlok EV100 Windows NT and Windows
2000 Download Drivers (687 kb), Shurlok EV100 is now fully compatible with Microsoft Windows NT
4.0 and Microsoft Windows 2000.

· Delete Data Correction. There was an error, whereby if you deleted data for a vehicle in the future,

1354
www.mixtelematics.com

1354
 1355

the Last Trip Information for the vehicle did not get updated. This has been corrected.

------------------------------------------------------------------------------

KEYWORDS: EV100

1355
www.mixtelematics.com

1355
 1356
10.3.160 Knowledge Base Article 162

Article Number 162

Title Can't Upgrade Database After FM2000 Install

Created 4/3/2000 5:40:07 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 1:58:43 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, version 4.00.0006 (FMCreateDB2.Exe version)

----- SUMMARY -----

During the installation of FM2000, when trying to upgrade the database, you receive an error
message, stating that the database is too old to be upgraded. If you try and run FMCreateDB2.Exe
manually, you will receive the same error message.

----- MORE INFORMATION -----

The exact wording of the error message is as follows:

The database C:\Program Files\Fleet Manager\FMServer.mdb is too old to be upgraded. Please create
a new database.

Replace C:\Program Files\Fleet Manager\FMServer.mdb, above, with the full path to your Fleet
Manager database. The error will occur during the Checking Database Integrity phase of the upgrade.
When you click OK for that error message, you will receive another, which says:

WARNING: You will not be able to run the FM Kienzle Fleet Manager 2000 until the database has
been successfully updated.

The error will occur if you attempt to install FM2000 over a release version (Version 2.10) of the FM98
software.

----- CAUSE -----

This is caused by errors in the above release of FMCreateDB2.Exe. These errors make the
FMCreateDB2 program incapable of upgrading databases from version 2.10 (First Release) of the
Fleet Manager 98 software.

----- SOLUTION -----

Install FM98 SR1, and upgrade the database to that version. Then install FM2000.

----- STATUS -----

If you are using old software, please use the workaround supplied. The latest software can upgrade
any database from FM98SR1b onwards.

1356
www.mixtelematics.com

1356
 1357

------------------------------------------------------------------------------

KEYWORDS: FM2000 FMCREATEDB FMCREATEDB2

1357
www.mixtelematics.com

1357
 1358
10.3.161 Knowledge Base Article 163

Article Number 163

Title What's new in CITAS 2010 version 2.20?

Created 4/4/2000 12:46:19 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 11:01:14 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· CITAS 2010, version 2.20

----- SUMMARY -----

The following is a list of what's new in CITAS 2010 version 2.00.

The latest version of CITAS 2010 software can be downloaded from the CITAS2010 FTP download
site.

There were 2 known problems with dates in version 2.00 and version 2.10. These problems
occurred only on Microsoft Windows 95 and Microsoft Windows 3.x, and affected the following
functions in the software:

1. Database Upgrade Functionality. If a database was upgraded to version 2.0 or version 2.1 after
the 31st of December 1999, then all dates already stored in the database for the in the 20th
century would be incorrectly converted to the 21st century. For example, any data in the year
1998 would be converted to the year 2098, etc. Had these databases been upgraded before the
turn of the century, then this problem would never have occurred.

2. The report criteria window. If the previous time the user requested a report, he selected a “From”
or “To” date in the 20th century, then the next time it was opened, it would convert to the 21st.
This is due to the fact that the software saves the report criteria for later use. The second (and
subsequent) time it is opened, the software reads these criteria back, and corrupts the year.

Both of the above problems have been corrected in version 2.20 of the CITAS 2010 software. It is
important to note that the FM Kienzle Fleet Manager 2000 CD-ROM ships with version 2.10 of the
software. (In the \Other\CITAS 2010 directory, on the CD-ROM.) This version should not be
installed.

------------------------------------------------------------------------------

KEYWORDS: CITAS 2010 FM2000

1358
www.mixtelematics.com

1358
 1359
10.3.162 Knowledge Base Article 164

Article Number 164

Title 'Unknown' Error Reported in Fuel Consumption Graph

Created 4/5/2000 10:37:06 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 10:59:23 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, version 3.00 (SR1) and above.

----- SUMMARY -----

When trying to do a Vehicle Fuel Consumption Graph (Entered) in Comparative mode, you may
receive error -214721900 while extracting.

----- MORE INFORMATION -----

The exact wording of the error message is as follows:

The following unexpected error/s occurred:

-214721900 (0x80040e14): Unknown occurred in Vehicles.GetFuelConsumption (Line 9220). The

error has been logged.

The error will occur during the Extracting fuel consumption information phase of the report.

----- CAUSE -----

This error occurs if one of the vehicles in the selection criteria has a fuel usage entry, within the
specified date/time range, where the Fuel Quantity field is zero (0) litres or gallons.

This value causes an error in the software, when it tries to calculate fuel consumption.

----- SOLUTION -----

Upgrade to the latest version of the Fleet Manager software (FM Fleet Manager 2001 or later).

----- STATUS -----

This problem has been solved in the FM98 SR1b update, as well as the FM Kienzle Fleet Manager
2000 software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1359
www.mixtelematics.com

1359
 1360
10.3.163 Knowledge Base Article 165

Article Number 165

Title 'No Code Plug Found' (Code Plug is in Pod) running under NT or 2000

Created 4/5/2000 1:33:06 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 10:57:03 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Shurlok EV100, version 1.92 (SR2) or below

· CI Data, version 1.50 (SR1) or below

----- SUMMARY -----

When running the above products under Microsoft Windows NT 4.0, or Microsoft Windows 2000, the
plug functions do not work. When trying to do a Plug Information, the software takes an unusual
amount of time, and then reports "No Code Plug Found". You have verified that there is a plug inserted
into the download module, and that the software is configured to use the correct port (LPT1 or LPT2).

----- MORE INFORMATION -----

You have installed one of the above product versions onto Microsoft Windows NT or Microsoft
Windows 2000, or have recently upgraded to Windows NT or Windows 2000, having one of the above
product versions installed. You downloaded and installed the appropriate product's Windows NT and
Windows 2000 Download Drivers from the Data Pro Development or CIFMS websites, but the problem
still occurs.

----- CAUSE -----

The Windows NT and Windows 2000 Download Drivers available for the above products will only work
with version 2.0 of the relevant product.

----- SOLUTION -----

Download and install version 2.0 of the appropriate product from the

1. CI Data FTP download site.

2. EV100 FTP download site,

and then re-install the NT/2000 download drivers.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

1360
www.mixtelematics.com

1360
 1361

KEYWORDS: EV100 CIDATA

1361
www.mixtelematics.com

1361
 1362
10.3.164 Knowledge Base Article 166

Article Number 166

Title CPMail 'Queued message could not be sent because no addresses were supplied.'

Created 4/7/2000 9:26:34 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 4/13/2000 11:49:59 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Centre-Point Service Tracker, all versions

----- SUMMARY -----

Whenever a request is logged or actioned, you may see the above message in your Windows NT
Application Log, on the Centre-Point server. You will only see this message if Centre-Point itself is
installed onto a Microsoft Windows NT (Server or Workstation) or Microsoft Windows 2000
computer.

----- MORE INFORMATION -----

The details of the message are as follows:

Date="Date"

Time="Time"

User="Either "N/A", or the user name of the user currently logged in to the server"

Computer="Centre-Point Server computer name"

Event ID=3

Source=CPMail

Type=Error

Category=None

The description for Event ID ( 3 ) in Source ( CPMail ) could not be found. It contains the following
insertion string(s): Queued message could not be sent because no addresses were supplied.

Queued="Date/Time the service request e-mail was queued"

Subject="The Subject line of the e-mail"

BodyText="The Body of the e-mail"

This message will be logged when a service request is actioned, and none of the "When Actioned,
E-Mail" checkboxes are checked (And no additional e-mail addresses are supplied). It will appear

1362
www.mixtelematics.com

1362
 1363

once for each action, that would result in an e-mail, where the relevant request has not been set
up to e-mail anybody.

----- CAUSE -----

This is due to the fact that the Windows Messaging Components report this error whenever one
tries to send an e-mail message with no addresses in the "To:", "Cc:", or "Bcc:" fields. The Centre-
Point Mail Server passes this error through to the event log.

----- SOLUTION -----

Either add some E-Mail options to the relevant service request, or stop the Centre-Point Mail
Server (CPMail) altogether, to avoid seeing this message. It is also acceptable, when actioning or
logging a service request, to add your own e-mail address in the "Other" field.

----- STATUS -----

This problem will be solved with the next release of Centre-Point Service Tracker.

------------------------------------------------------------------------------

KEYWORDS: CENTRE-POINT

1363
www.mixtelematics.com

1363
 1364
10.3.165 Knowledge Base Article 167

Article Number 167

Title Error -132 during SR1a Install

Created 4/11/2000 12:28:01 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 4/11/2000 12:29:01 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, SR1a (FMServer version 3.10)

----- SUMMARY -----

During the installation of FM98 Service Release 1a (SR1a), when the copy is at 96%, error -132 is
displayed.

----- MORE INFORMATION -----

The exact wording of the error message is as follows:

An error occurred during the move data process: -132

Component:

File Group:

File:

When you click OK, the installation terminates.

----- CAUSE -----

This error occurs when the installation set attempts to overwrite a file that is in use (Locked). This
typically occurs when upgrading a Windows 95 or Windows 98 Fleet Manager Server, when a shortcut
to FMLaunch.exe has been placed in your Startup group. However, it can also occur if the Fleet
Manager software is running at the time of the upgrade, or you have recently requested a report.

----- SOLUTION -----

Remove any shortcut to FMLaunch.exe that you may have in your Startup group, and restart your
computer. Verify that none of the Fleet Manager components are running, and then re-install SR1a.

----- STATUS -----

This problem has been solved in the FM Kienzle Fleet Manager 2000 release.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1364
www.mixtelematics.com

1364
 1365
10.3.166 Knowledge Base Article 168

Article Number 168

Title 'Method '~'...' when clicking OK/Apply on the Vehicle dialog

Created 4/12/2000 3:59:13 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 10:54:56 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, Service Release 1 (SR1)

· FM Kienzle Fleet Manager 98, SR1a Update

· FM Kienzle Fleet Manager 2000, version 4.00.0016 (FMClient2.exe version) and below

----- SUMMARY -----

If you click the OK or Apply button on the Vehicle Properties dialog, after adding fuel records, error -
2147217887 may occur.

----- MORE INFORMATION -----

The exact wording of the error message is as follows:

The following unexpected error/s occurred:

-2147217887 (0x80040E21): Method '~' of object '~' failed occurred in frmVehicle.ApplyForm (line
38240).

The above line number applies only to SR1a of the FM Kienzle Fleet Manager 98 software. For
FM2000, the line number is 49120.

----- CAUSE -----

The error will occur if you add a fuel record to the vehicle, click the Apply button, add some more
records, and click the OK or Apply button again. It is due to errors in the code of the FM Kienzle Fleet
Manager Client, which caused the system to believe that it was adding a given record twice.

----- SOLUTION -----

Always use the OK button after adding fuel entries. This ensures that the vehicle dialog is always
closed and re-opened between adding entries.

Upgrade to the latest version of the Fleet Manager software available (FM Fleet Manager 2001 or
greater).

----- STATUS -----

This problem has been solved in the FM Kienzle Fleet Manager 98, SR1b release, and was included

1365
www.mixtelematics.com

1365
 1366

in the following release of the FM Kienzle Fleet Manager 2000 software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1366
www.mixtelematics.com

1366
 1367
10.3.167 Knowledge Base Article 169

Article Number 169

Title 'Distance' and 'Duration' columns missing

Created 4/18/2000 6:16:16 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 10:52:34 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· CI Data Millenium, version 2.00

· Shurlok EV100, version 2.00

----- SUMMARY -----

After upgrading to one of the above software products, you will notice that the above two columns no
longer appear on the trip report.

----- MORE INFORMATION -----

The problem will occur when doing a vehicle or driver trip report, in Summary, Daily, or Detail modes.
In the previous versions of the products, the "Distance" and "Duration" columns appeared on the report
- now they do not.

----- CAUSE -----

There was an error in the first release of the version 2.00 installation sets of the above products. These
have been corrected.

----- SOLUTION -----

Simply re-download the software from

1. the CI Data FTP download site.

2. the EV100 FTP download site.

----- STATUS -----

This problem has been corrected.

------------------------------------------------------------------------------

KEYWORDS: EV100 CIDATA

1367
www.mixtelematics.com

1367
 1368
10.3.168 Knowledge Base Article 170

Article Number 170

Title What's New in FM Kienzle Fleet Manager 98, SR1b

Created 4/20/2000 4:02:03 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 10:32:36 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO -----

· FM Kienzle Fleet Manager 98, SR1b Update

----- SUMMARY -----

The following is a list of what's new in the SR1b Update of FM Kienzle Fleet Manager 98.

This update can be found on the FM Kienzle Fleet Manager 2000 CD, under the "Other" section:

· If you try and initialise a vehicle plug, and there are no vehicles of that particular type in the
system, you may run into problems in the Initialise Plug Wizard. For more information about this
problem, please see Knowledge Base Article 172.

· If you enabled the alarm for an FM100 event, you were allowed to use the System Override Plug.
For more information, see Knowledge Base Article 173.

· The Driver Scoring Report would always print a row of zeroes for Unknown Drivers, even though
there were trips for that driver, for that period. Please see Knowledge Base Article 174 about this
problem.

· Occasionally, when doing a Driver Scoring Report, an Access Violation error would occur in
FMServer.exe. Knowledge Base Article 175 explains this problem in more detail.

· A "Method ~ of Object ~" error would sometiems occur on adding fuel entries. For more
information about this problem, please see Knowledge Base Article 168.

· If you added a fuel entry, clicked Apply, and immediately modified that entry, an additional entry
would be created. See Knowledge Base Article 176.

· When adding profile ranges, you would get a series of "beeps", followed by a repeating message
box, if you added an invalid entry, and clicked the add button again. This problem is described in
Knowledge Base Article 84.

· Opening a criteria file, where all of the objects previously selected had since been deleted, would
cause problems. These problems have been solved in SR1b

· When you executed a Vehicle Fuel Consumption Graph, Comparative, you would sometimes get
error -214721900. This error, and it's description and cause, are detailled in Knowledge Base
Article 164.

1368
www.mixtelematics.com

1368
 1369

------------------------------------------------------------------------------

KEYWORDS: FM98

1369
www.mixtelematics.com

1369
 1370
10.3.169 Knowledge Base Article 172

Article Number 172

Title Initialise Plug, no Vehicles of Type Causes Problems

Created 4/20/2000 4:17:44 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 10:27:56 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, Service Release 1 (SR1)

· FM Kienzle Fleet Manager 98, SR1a Update

----- SUMMARY -----

A problem occurs if you try and intialise a plug plug, and there are no vehicles of the plug's unit
type, in the Fleet Manager database.

----- MORE INFORMATION -----

If, for example, you try and initialise an FM100 plug, using the Initialise Plug wizard in the software,
you will get to step 2 of the wizard. At this point, you will see a disabled list box, with an item "No
Vehicles in System" as the first item. The Next button of the wizard, at this point, is enabled. If you
click it, you will be asked if you wish to change the vehicle id on the plug to be for "No Vehicles In
System"

----- CAUSE -----

This is caused by an error in the FM Kienzle leet Manager Client application. (FMClient.exe)

----- SOLUTION -----

Upgrade to the latest version of the FM Fleet Manager software available, or to the FM Kienzle Fleet
Manager 98 SR1b Update to be found on the FM Fleet Manager 2000 CD under the "Other"
section.

This will solve the problem.

----- STATUS -----

This problem has been solved in the FM98 SR1b update, as well as the FM Kienzle Fleet Manager
2000 software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FM200

1370
www.mixtelematics.com

1370
 1371
10.3.170 Knowledge Base Article 173

Article Number 173

Title 'System Override' Option Enabled for FM100 Event

Created 4/20/2000 4:23:56 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 10:27:42 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, Service Release 1 (SR1)

· FM Kienzle Fleet Manager 98, SR1a Update

----- SUMMARY -----

In the Event Properties of an FM100 vehicle, the checkbox to enable the System Override plug is
enabled if you check the Alarm checkbox.

----- MORE INFORMATION -----

If you click on the Actions tab for an event at the vehicle level, and the vehicle is an FM100 vehicle,
you have the option of enabling the alarm. If you check this option, which reads Sound the Buzzer
After, another checkbox, System Override plug disables Alarm and Relay, becomes enabled. This
should not be the case, since the FM100 unit does not support the use of the System Override plug.

----- CAUSE -----

This is caused by errors in the FM Kienzle Fleet Manager Client program. (FMClient.exe)

----- SOLUTION -----

Upgrade to the latest version of the FM Fleet Manager software available, or to the FM Kienzle Fleet
Manager 98 SR1b Update to be found on the FM Fleet Manager 2000 CD under the "Other" section.

This will solve the problem.

----- STATUS -----

This problem has been solved in the FM98 SR1b update, as well as the FM Kienzle Fleet Manager
2000 software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1371
www.mixtelematics.com

1371
 1372
10.3.171 Knowledge Base Article 174

Article Number 174

Title 'Unknown Drivers' prints zeroes on Driver Score Report

Created 4/20/2000 4:36:00 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 10:27:26 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, Service Release 1 (SR1)

· FM Kienzle Fleet Manager 98, SR1a Update

----- SUMMARY -----

If you print a Driver Scoring report, and select to show the Unknown Drivers (Or Unknown Driver)
Driver, you will see a duration of zero (As well as a distance and scores of zero) for that driver. This
occurs even if there are trips for that driver in the database. (i.e. trips were recorded, within the
reporting period, where no driver was identified.)

----- MORE INFORMATION -----

To duplicate this problem, click Reporting, Driver Reports, Trip Report. Include Information for
selected Drivers, pick Unknown Drivers (Or Unknown Driver, and select a date range. Based on the
results of the report, confirm that there are trips for that driver. Now, do a Driver Scoring report, for the
same criteria, and note the Distance, Duration, and scores columns. These columns will all contain
zero.

----- CAUSE -----

This is caused by errors in the FM Kienzle Fleet Manager Database Server component. (FMServer.
exe)

----- SOLUTION -----

Upgrade to the latest version of the FM Fleet Manager software available, or to the FM Kienzle Fleet
Manager 98 SR1b Update to be found on the FM Fleet Manager 2000 CD under the "Other" section.

This will solve the problem.

----- STATUS -----

This problem has been solved in the FM98 SR1b update, as well as the FM Kienzle Fleet Manager
2000 software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1372
www.mixtelematics.com

1372
 1373
10.3.172 Knowledge Base Article 175

Article Number 175

Title FMServer.exe Access Violation on Driver Scoring Report

Created 4/20/2000 4:44:10 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 10:27:11 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, Service Release 1 (SR1)

· FM Kienzle Fleet Manager 98, SR1a Update

----- SUMMARY -----

When doing a Driver Scoring report, you may notice that a General Protection Fault (GPF) error
may occur in the database server. (FMServer.exe)

----- MORE INFORMATION -----

The error occurs when calculating scores for a particular driver. Other drivers will calculate
successfully, and a report which excludes that driver, or a report for a different period, may not
exhibit the error.

----- CAUSE -----

This is caused by corruption in the database. It occurs when there is a trip, by the particular driver
that caused the error, that ends before it starts. You will not be able to see that trip through the
client software (FMClient.exe).

----- SOLUTION -----

A workaround is to indentify all the vehicles that the offending driver drove during the reporting
period, and clear all data for those vehicles. You will then be able to generate the report with no
errors.

Upgrade to the latest version of the FM Fleet Manager software available, or to the FM Kienzle
Fleet Manager 98 SR1b Update to be found on the FM Fleet Manager 2000 CD under the "Other"
section.

This will solve the problem.

----- STATUS -----

The problem has been fixed in the FM Kienzle Fleet Manager 2000 software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1373
www.mixtelematics.com

1373
 1374
10.3.173 Knowledge Base Article 176

Article Number 176

Title Modify Fuel Entry results in two entries

Created 4/20/2000 4:51:25 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 10:26:12 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, Service Release 1 (SR1)

· FM Kienzle Fleet Manager 98, SR1a Update

· FM Kienzle Fleet Manager 2000, version 4.00.0016 (FMClient2.exe) or below

----- SUMMARY -----

When you modify a fuel entry for a vehicle, and click OK or Apply, the next time you enter that
particular vehicle's properties, there will be one extra entry in the list.

----- MORE INFORMATION -----

The error occurs if you add a new entry, click Apply, and immediately click Edit to edit the entry just
created.

----- CAUSE -----

This is caused by errors in the FM Kienzle Fleet Manager Client program. (FMClient.exe for FM98, or
FMClient2.exe for FM2000)

----- SOLUTION -----

Upgrade to the latest version of the FM Fleet Manager software available, or to the FM Kienzle Fleet
Manager 98 SR1b Update to be found on the FM Fleet Manager 2000 CD under the "Other" section.

This will solve the problem.

----- STATUS -----

This problem has been solved in the FM98 SR1b update, and has been included in the release of the
FM Kienzle Fleet Manager 2000 software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1374
www.mixtelematics.com

1374
 1375
10.3.174 Knowledge Base Article 177

Article Number 177

Title Cancel Vehicle Form still updates plug, or asks to update plug

Created 4/20/2000 4:56:56 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 10:25:09 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, Service Release 1 (SR1)

· FM Kienzle Fleet Manager 98, SR1a Update

----- SUMMARY -----

If you cancel the vehicle properties dialog, you may observe one of two behaviours:

1. If you have your Plug Update Confirmation set to Confirm before updating the plug (The default),
you will be prompted to update the vehicle's plug, even though you cancelled the dialog.

2. If this option is set to Always update the plug, the vehicle's plug will always be updated, even
though to cancelled the dialog.

The above behaviours apply only to FM200 or FM200e vehicles' property dialogs.

----- MORE INFORMATION -----

The problem will occur if modify anything on the Tacho Configuration tab of the vehicle properties
dialog, and then click Cancel.

----- CAUSE -----

This problem is caused by errors in the FM Kienzle Fleet Manager Client program. (FMClient.exe)

----- SOLUTION -----

Upgrade to the latest version of the FM Fleet Manager software available, or to the FM Kienzle Fleet
Manager 98 SR1b Update to be found on the FM Fleet Manager 2000 CD under the "Other" section.

This will solve the problem.

----- STATUS -----

This problem has been solved in the FM98 SR1b update, as well as the FM Kienzle Fleet Manager
2000 software.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1375
www.mixtelematics.com

1375
 1376
10.3.175 Knowledge Base Article 178

Article Number 178

Title How To Implement Remote Downloading

Created 4/26/2000 5:34:53 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 5/17/2000 11:07:04 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, Service Release 1a (SR1a) or greater

· FM Kienzle Fleet Manager 2000, all versions

----- DETAILS -----

This article describes the use of the Data Extraction Only installation option of the Fleet Manager
Autopoll Client.

This Data Extraction Only option is designed to be installed on computers that do not have any of the
Fleet Manager components installed (but do have download modules attached).

It's purpose is to enable downloading of data from code plugs at a remote point and to store their data
as disk files.

The Fleet Manager Autopoll is performed in two phases:

1. Polling data from a plug (in the download module) and channelling it into files.

2. Processing these files containing the data, and transferring this information to the Fleet Manager
Server Component (FMServer).

When you install FM Autopoll, there are two installation options:

Data Extraction Only, or

Full Product.

The Full Product includes both phase 1 and 2 mentioned above, while Data Extraction Only consists
of the first phase.

Remote workstations can be used as data polling stations, provided that:

1. The server has the Full Product installed (default with FM2000 installation)

2. The workstations are running Data Extraction Only with *NO* Fleet Manager software installed.

The Autopoll Client on the server can be configured to process from a network (see the advanced
option in Autopoll Client). Files on remote computers may be copied over to the server computer (via
e-mail etc), but care should be taken to maintain the file/folder structures underneath the Autopoll

1376
www.mixtelematics.com

1376
 1377

Folder.

----- HOW TO INSTALL -----

The following describes how to install the Data Extraction Only option of the Fleet Manager Autopoll
Client:

1. Run \Other\Fleet Manager Autopoll Client\setup.exe from the FM2000 CD.

2. When you get to the Setup Type step of the installation, you are given two options: Data Extract
Only and Full Product. Choose Data Extraction Only and continue the installation.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000 FMAPC

1377
www.mixtelematics.com

1377
 1378
10.3.176 Knowledge Base Article 179

Article Number 179

Title FMTerminal Event Report always displays 'Unknown Driver'

Created 5/9/2000 2:41:01 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 5/17/2000 11:10:37 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager Terminal

----- SUMMARY -----

The FMTerminal Event Report always displays "Unknown Driver" for resting reasons (i.e. business/
private/maintenance halt, refuelling or traffic jam).

----- CAUSE -----

The FMTerminal Event Report is designed to show the data exactly as it is recorded by the FM200.

The resting reason of the FMTerminal is saved after the trip ends. The trip end causes the current driver
to be "logged off", i.e. reset to "Unknown Driver". This is why the resting reason is shown as "Unknown
Driver".

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000 FMT

1378
www.mixtelematics.com

1378
 1379
10.3.177 Knowledge Base Article 180

Article Number 180

Title Port settings reset when upgrading with FM2000

Created 5/15/2000 3:14:01 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 5/17/2000 11:14:23 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When upgrading an existing installation of the Fleet Manager 98 software to Fleet Manager 2000,
the port setting for the Download Module resets.

----- MORE INFORMATION -----

In the case where the Download Module of the existing Fleet Manager installation is connected to
LPT2, it has been found that after running the upgrade to FM2000, this port is reset to LPT1.

----- CAUSE -----

This occurs because the upgrade installation set for Fleet Manager 2000 uninstalls the "current"
version of the software before it does the upgrading and installation of the new version. During the
uninstall, some of the settings (e.g. the LPT port settings for the Download Module) are reset.

----- SOLUTION -----

The default setting for this port is LPT1, and if any other parallel port is used for the download
module, it should be selected manually after installing/upgrading.

To change you port settings for the Download Module:

1. Run the Fleet Manager Client program

2. Go to Tools Menu, choose Options

3. Go to the Code Plug tab

4. Under Download Module Port, select either LPT1 or LPT2

5. Apply/OK

6. Your Download Module’s port is now set.

----- STATUS -----

This problem is under investigation.

1379
www.mixtelematics.com

1379
 1380

------------------------------------------------------------------------------

KEYWORDS: FM2000

1380
www.mixtelematics.com

1380
 1381
10.3.178 Knowledge Base Article 181

Article Number 181

Title Can’t log in to Centre-Point

Created 5/16/2000 11:11:24 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 5/17/2000 11:16:40 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Data Pro Centre-Point, all versions

----- SUMMARY -----

When trying to log into Centre-Point, no error message is displayed, and the login screen returns
blank.

----- MORE INFORMATION -----

When typing in a name and password on the Centre-Point login screen, and then clicking the "Login"
command button or pressing ENTER, there is no Login as expected. Instead, the login screen returns
with the Username and Password fields blank.

----- CAUSE -----

This is caused by the client having disabled "Cookies" in their web browser. Centre-Point uses Cookies
to identify the logged on user, so when Cookies are disabled at the client, this problem will appear.
(For example, this problem occurs when using Microsoft Internet Explorer 4 or higher, and the Centre-
Point web site is in a zone whose security is set to "High".)

----- SOLUTION -----

The solution is to enable cookies in your browser.

----- STATUS -----

The functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: CENTRE-POINT

1381
www.mixtelematics.com

1381
 1382
10.3.179 Knowledge Base Article 182

Article Number 182

Title Error -113 During Installation of Fleet Manager Software

Created 5/17/2000 10:22:20 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 10:21:57 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When attempting to install the Fleet Manager software from the Fleet Manager CD-ROM, error -113
may occur in the installation set. The error will occur in the final stages of the setup program, when
the files are being copied to your hard disk.

----- MORE INFORMATION -----

The details of the error are as follows:

ComponentMoveData had the following error:

Media Name: data

Component: [Component]

File Group: [File Group]

File: [File]

Error Number: -113

After this has been displayed, a message box will be displayed, reading:

An error ocurred during the move data process: -113

Component: [Component]

File Group: [File Group]

File name: D:\[File]

(Replace "D:\" above with the letter of your CD-ROM drive.) Following this, another message box is
displayed, which reads:

An error has occurred that prevents setup from continuing. Setup will end now.

1382
www.mixtelematics.com

1382
 1383

The installation then terminates.

Note: If [File] above is "Español.ecf", then please see KBA126: Error -113 During Installation of
FM98 Software. If you are trying to install the software onto an Eastern version of Microsoft
Windows (For example, Korean), then please see KBA139: Error -113 During Installation of FM98
Software on Eastern OS.

----- CAUSE -----

This is an error that is returned by the InstallShield package, used to create the installation sets for
the above products. It means that there was an error copying a certain file from the CD. This could
be because the CD itself is corrupt, or your CD-ROM drive is having difficulty reading the CD.

----- SOLUTION -----

Firstly, if possible, try to copy the entire CD image onto your hard disk, and run the setup program
from there. If this does not work or is not possible, then try running the setup from a different CD-
ROM drive. If neither of the above options work or are possible, please contact your distributor to
obtain another CD.

----- STATUS -----

This problem is beyond our control.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1383
www.mixtelematics.com

1383
 1384
10.3.180 Knowledge Base Article 183

Article Number 183

Title Centre-Point Mail Server does not send mail

Created 5/17/2000 10:54:43 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 5/17/2000 10:56:24 AM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Centre-Point Service Tracker

----- SUMMARY -----

When actioning Service Requests, or Service Requests are auto-escalated, no e-mail is sent out. No
messages are logged in the Application Event log, and you have made certain that the program is
configured to send out e-mail, and that the relevant Service Request has e-mail addresses in the
"When Actioned, E-Mail" section.

----- MORE INFORMATION -----

You will also notice that, when you start the e-mail client on the server machine, before starting the
Mail Server application or service, then the program successfully sends out e-mail. If the application or
service is started first, then no e-mail is sent. This happens regardless of whether the mail client is
subsequently started or not.

----- CAUSE -----

This problem is caused by two versions of a particular file, called mapisp32.exe residing on the server
computer. One of these files will be of a newer version than the other. (Right click, click "Properties",
and then click "Version").

----- SOLUTION -----

Find the newer version of the file (If you are using Microsoft Windows NT 4.0 with Service Pack 5, for
example, then this should be version 5.5.1960.3). Copy this version over all other versions that are
installed on the server. Then, restart the server computer. If the Centre-Point Mail Server (CPMail)
application or service is not started after the re-start, start it manually.

----- STATUS -----

This problem is under investigation.

------------------------------------------------------------------------------

KEYWORDS: CENTRE-POINT

1384
www.mixtelematics.com

1384
 1385
10.3.181 Knowledge Base Article 184

Article Number 184

Title Error 3075 Generating Event Report

Created 5/18/2000 5:40:15 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/30/2000 2:26:05 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When executing an event report, you may receive an error 3075 while the report is generating.

----- MORE INFORMATION -----

You will get this error on both the driver and vehicle event reports. It occurs during the "Extracting
Data" phase of the report generation. The exact wording of the error message is as follows:

The following error/s occurred while communicating with the server:

3075

If you get this error, pay particular attention to the list of events that were selected for the report. You
will notice that one or more of these has an inverted comma (") character in the description.

----- CAUSE -----

This is caused by errors in the system, that causes the report to fail when event descriptions contain
this inverted comma character.

----- SOLUTION -----

Edit the description of the event so that it does not contain an inverted comma, and generate the
report again.

----- STATUS -----

This problem has been solved in FM Kienzle Fleet Manager 2000 Second Edition (version 5.00.0003).

------------------------------------------------------------------------------

KEYWORDS: FM2000 FM98

1385
www.mixtelematics.com

1385
 1386
10.3.182 Knowledge Base Article 185

Article Number 185

Title Fuel Entries 'Missing' After Upgrade to CI Data v2.0

Created 5/23/2000 3:53:26 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 5/23/2000 3:53:26 PM

Last Modified By Graham Downs (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· CI Data Millenium, version 2.0 or greater

----- SUMMARY -----

After upgrading your CI Data database to CI Data Millennium (version 2.0 or greater), you observe that
data entered into "Fuel Usage" are missing.

----- MORE INFORMATION -----

These entries do not disappear altogether. Rather, the "Odometer Reading" and "Fuel Quantity" fields
are all set to zero (0). If you close and re-open CI Data Millennium, the values are as they were before
the upgrade.

----- CAUSE -----

This is a problem with the CI Data software, the cause of which is as yet unknown.

----- SOLUTION -----

Close and re-open the CI Data Millennium software. You will see that the Fuel Entry values return to
normal.

----- STATUS -----

This problem is under investigation.

------------------------------------------------------------------------------

KEYWORDS: CIDATA

1386
www.mixtelematics.com

1386
 1387
10.3.183 Knowledge Base Article 186

Article Number 186

Title Error 94 while downloading a vehicle plug

Created 5/24/2000 11:35:50 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/19/2004 4:59:41 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 2000, version 4.00.0004 (FMServer2.exe version)

----- SUMMARY -----

An unexpected error 94 occurs while downloading a vehicle plug from within the Fleet Manager 2000.

----- MORE INFORMATION -----

The full description of the error reads as follows:

The following unexpected error/s occurred.

94 (0x0000005E): Invalid use of Null occurred in ProcessFM200Data.ProcessFMTerminalData (Line

57320), The error has been logged.

----- CAUSE -----

This error occurs when the driver captured fuel data into the Fleet Manager Terminal, but did not
enter a "cost" value.

This data is "recorded" by the Fleet Manager Terminal as having a "Null" value entered for fuel cost.
This "Null" value is passed to the Fleet Manager Software, which in turn attempts to use it in
mathematical calculations.

The above error is displayed, because the software cannot use a "Null" value in a mathematical
expression/calculation.

----- SOLUTION -----

1. Download the 616KB patch from ftp://ftp.cidev.com/KBase/FM2000Fix1.Zip

2. Extract this file into your Fleet Manager install directory (typically C:\Program Files\Fleet Manager).

(The software now takes the "Null" value, and assumes it to be zero ("0"), which is correct, as the
data - in this case the amount of fuel entered - was "nothing". It is now able to perform mathematical
calculations with this value, as it is a mathematical value).

----- STATUS -----

This problem has been fixed in the next release of Fleet Manager 2000 (FM Kienzle Fleet Manager

1387
www.mixtelematics.com

1387
 1388

2000 Second Edition - version 5.00.0003).

------------------------------------------------------------------------------

KEYWORDS: FM2000 FMTerminal FMT FM200 FM200e

1388
www.mixtelematics.com

1388
 1389
10.3.184 Knowledge Base Article 187

Article Number 187

Title What's New in FM Kienzle Fleet Manager 2000

Created 5/24/2000 2:24:26 PM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 11/22/2004 10:55:38 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

The following is a list of what's new in FM Kienzle Fleet Manager 2000 (version 4.00)

Please contact your nearest Fleet Manager Distributor for more information about purchasing this
software.

· FMTerminal Support

Full support for the FM Kienzle FMTerminal has been added, allowing drivers to capture fuel entry,
driving and resting reasons, customer codes, etc. Two new reports have been added to assist in the
interpretation of this information: The Fleet Log Book Report, and the FMTerminal Event Report.

· F3 Frequency

When a parameter is connected to the F3 input of a vehicle, the software allows you to specify the
resolution, in Hz, of the sender being monitored.

· Event level Fuel Recording

The event definitions have been enhanced, so that if a vehicle has a fuel sender (for example, an
EDM) connected, the amount of fuel used during the occurrence of events can be recorded.

· Enhanced Event Definitions

The definitions of events have been greatly enhanced, allowing the definition of events with any
number of conditions.

· Passenger List

The software supports the use of the FM Kienzle Black Passenger Plug, to identify passengers
entering and exiting the vehicle. A powerful passenger identification report has been added,
showing the dates/times of passenger identification in specified vehicles.

· Auto Polling Software

The Fleet Manager Autopoll Client supports unattended data downloading. Whilst the Autopoll client
is running, data is downloaded automatically whenever a green vehicle plug is inserted into the

1389
www.mixtelematics.com

1389
 1390

download module. This data is processed and stored in the Fleet Manager database automatically
at specified time intervals.

· New Duration column on Trip Reports

The Driver and Vehicle Trip Reports have been enhanced. The “Duration” column on these reports
is the actual time spent by the Driver/Vehicle in a Trip. There is an additional value, called
“Summary Duration (first start to last end)”. This value is the total time between the start of the first
trip in the specified time period, to the end of the last trip.

· Fleet Manager 2010 unit type

The system now supports automatic importing of data from your Fleet Manager 2010 units. This
allows you to run a mixed fleet of FM2010, FM100 and FM200 units and to take advantage of the
Fleet Manager’s powerful reporting and graphing features.

· Copy Vehicle As...

With a vehicle selected, you may now click on the “Tools” menu, and click “Copy Vehicle As…”
After providing some information about the new vehicle (New Vehicle ID – leave 0 to have the
software assign one, Registration Number, and Description), an exact copy of the selected vehicle
will be created. This includes the unit type of the original vehicle, Service Information, Event and
Input Configuration, etc.

· Vehicle and Driver ID Ranges

Two new fields have been added to the Site Properties dialog. If enabled (Enabling/disabling is
done separately), the will restrict all newly created vehicles and drivers, where the ID number is left
to automatically assign, to the specified range. If the user tries to add a driver or vehicle, with an
automatically assigned ID, and all the ID numbers in the specified range have been assigned, the
user will be told that he cannot add a vehicle or driver at that time.

· Backup Facility of Fleet Manager Administrator

The backup facility of the Fleet Manager Administrator has been enhanced to cater for backing up
of the database to removable disks, so that appropriate messages will be displayed if the disk is not
available, or if there is insufficient disk space on the disk to perform the backup.

· New language translation tools

The software makes use of a new language management component that greatly simplifies the
process of translating language strings. A translator utility has been developed enabling distributors
to translate the software and test their translations without waiting for resource files to be compiled.

(These tools are intended for FM Kienzle Fleet Manager distributors only)

· Tacho Configuration

Two more options are provided on the Tacho Configuration tab of the Vehicle Properties form,
allowing you to specify whether or not you would like the vehicle unit to record Tacho data both
inside and outside of trips.

· Calibration Details

The Input Configuration Properties dialog now shows details of the vehicle’s calibration, when
viewing the Road Speed or Engine RPM lines.

· Vehicle Configuration Report

1390
www.mixtelematics.com

1390
 1391

A new report has been added, allowing you to print out the configuration (Event and Input) of
specified vehicles. In addition, the last calibration details of the vehicle will also be printed on this
report.

· Last Configuration Uploaded

Once a new configuration has been uploaded to a vehicle, and a download has been completed,
you will see the “Last Configuration Uploaded” date on the Vehicle Properties form.

· Extension Manager

A new concept has been added, called “Extensions”. With this powerful new feature, 3rd party
software developers have at their disposal the facility to create custom “Extensions”, which build
into the Fleet Manager Client’s menu structure, to facilitate custom reports, and a variety of other
functions.

Two sample extensions, the FM Object Finder Utility, and the FM200 Tacho Dump Utility, have
been included on the Fleet Manager 2000 CD-ROM.

· Activity Timeline Refresh

The Activity Timeline no longer "Loads" all the necessary data as soon as it is opened. Instead, the
Fleet Manager 2000 software allows you the facility of selected the Vehicle or Driver to view, the
specific Events to view, as well as the date and time from which to start, before requiring to you
click a "Go" button to retrieve data.

· Update Password

A new password facility has been implemented, allowing the dealer to restrict access to various
aspects of the system, including deleting data, modifying vehicle configurations, etc.

To download this document in Microsoft Word 2000 format, with screen-shots, go to ftp://ftp.cidev.
com/kbase/What's New in Fleet Manager 2000.doc. This is a 140kb document file. Please note that
this document refers to other documents for more information on many of the features described
above. These other documents are included on the Fleet Manager 2000 CD-ROM.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000

1391
www.mixtelematics.com

1391
 1392
10.3.185 Knowledge Base Article 188

Article Number 188

Title Scale Incorrect on Fuel Consumption Graph

Created 5/25/2000 11:54:47 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 9:31:16 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

----- SUMMARY -----

When viewing a Vehicle Fuel Consumption Graph (Entered), the scale of the "Fuel Consumption"
axis ranges from zero (0) to ten (10) in increments of five (5). This causes confusion and makes
the graph difficult to read, if the vehicle's fuel consumption ever exceeds 10km/l or 10l/100km.

----- CAUSE -----

This is caused by the fact that an incorrect version of the graph template file, responsible for this
graph, was shipped on the Fleet Manager 98 CD-ROM.

----- SOLUTION -----

Download the 18k template update from ftp://ftp.cidev.com/kbase/DetailedFuelConsumption.vtc,

and copy it into your Fleet Manager directory. (Typically C:\Program Files\Fleet Manager) This will
modify the scale of the graph to be in a more readable scale.

----- STATUS -----

This problem has been solved in the FM Kienzle Fleet Manager 2000 release.

------------------------------------------------------------------------------

KEYWORDS: FM98 FM2000

1392
www.mixtelematics.com

1392
 1393
10.3.186 Knowledge Base Article 189

Article Number 189

Title Trips or Events 'On' for Extended Periods of Time

Created 5/26/2000 9:12:52 AM

Created By Graham Downs (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 2:10:45 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When viewing a trip or event on the activity timeline, from within the Fleet Manager software, the trip or
event may appear active for an abnormal period of time. In some cases, the trip or event is seen to go
on for many hours, where it would seem impossible for the trip or event to occur.

----- MORE INFORMATION -----

If the Battery Disconnect event has been enabled for your vehicle, you will see that this event is also
true for the duration of the offended trip or event.

----- CAUSE -----

This is caused by the fact that the unit's power was disconnected while an event was ocurring, or the
vehicle was active. The unit has thus recorded the start of the event or trip, but is not able to record the
end of that event or trip until the battery is re-connected. The Activity Timeline only shows a graphical
representation of event/trip start to event/trip end. Since the event/trip end in the case of the power
being disconnected is only recorded some time later, that is what the Timeline displays.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM98 FM2000 Events

1393
www.mixtelematics.com

1393
 1394
10.3.187 Knowledge Base Article 190

Article Number 190

Title Run-time error '3265' when trying to use FM Object Finder Extension

Created 5/26/2000 1:32:44 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/30/2000 2:23:25 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, all versions

· FM Kienzle Fleet Manager Object Finder Extension version 1.00.0004

----- SUMMARY -----

After installing the Fleet Manager 2000 software, as well as the Fleet Manager Object Finder
Extension, and trying to use this Extension to search for a number, the above error may occur.

----- MORE INFORMATION -----

The error message reads as follows:

Run-time error '3265':

ADO could not find the object in the collection corresponding to the name or ordinal reference
requested by the application.

----- CAUSE -----

This is caused by an incorrect version of MDAC being installed on the user's computer. The version of
this software that is included on the Fleet Manager 2000 CD is incompatible with this version of the
Fleet Manager Object Finder Extension version 1.00.0004.

----- SOLUTION -----

Download and install the version 2.5 of MDAC (Microsoft Data Access Components MDAC 2.5 RTM)
from the Microsoft Universal Data Access Download Page at http://www.microsoft.com/data/
download_250rtm.htm. Please ensure that you read the licensing agreement carefully before
downloading this software.

----- STATUS -----

This problem has been solved in FM Kienzle Fleet Manager 2000 Second Edition (Version 5.00.003).

------------------------------------------------------------------------------

KEYWORDS: FM2000 FMFind

1394
www.mixtelematics.com

1394
 1395
10.3.188 Knowledge Base Article 191

Article Number 191

Title Driver Trip report for ONE Driver displays ALL Drivers

Created 6/2/2000 5:08:16 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 9:28:26 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Shurlok EV100, Version 2.00

· CI Data Millennium, Version 2.00

----- SUMMARY -----

When trying to do a Driver Trip report, for one specific driver, a detailed Trip Report for All drivers
are displayed.

----- MORE INFORMATION -----

When doing a trip report, by driver, you are given the option to choose one driver ONLY. After
submitting this as criteria, the report displays the following:

"All drivers from..." (displays on the top left-hand corner of the report) together with a detailed trip
report for ALL the drivers in the database, instead of a detailed trip report for one specified driver.

----- SOLUTION -----

Download EV100 version 2.01 or CI Data Millennium version 2.01.

----- STATUS -----

This has been fixed and the latest versions are available on the website.

------------------------------------------------------------------------------

KEYWORDS: EV100 CIDATA

1395
www.mixtelematics.com

1395
 1396
10.3.189 Knowledge Base Article 192

Article Number 192

Title Error running reports from SR1b

Created 6/5/2000 4:41:38 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/5/2000 4:42:30 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, SR1b

----- SUMMARY -----

When trying to run any report after upgrading the Fleet Manager 98 software to Fleet Manager SR1b,
an error message is displayed.

----- MORE INFORMATION -----

The error message reads as follows:

The FM Kienzle Fleet Manager reports database is not a valid database file. Please check the
configuration of the server computer.

----- CAUSE -----

The Read only attribute of FMReports.mde has been set.

----- SOLUTION -----

The solution to this problem is to uncheck the Read Only attribute of the FMReports.mde file.

To uncheck the Read only attribute:

1. Quit the Fleet Manager software

2. Browse to your Fleet Manager install directory (typically C:/Program Files/Fleet Manager)

3. Right Click FMReports.mde

4. Go to properties

5. Uncheck the Read Only attribute to the bottom of the property dialogue box

6. Apply/OK

----- STATUS -----

This has been corrected in a newer version of the Fleet Manager 98SR1b install set.

1396
www.mixtelematics.com

1396
 1397

------------------------------------------------------------------------------

KEYWORDS: FM98

1397
www.mixtelematics.com

1397
 1398
10.3.190 Knowledge Base Article 193

Article Number 193

Title What's new in Fleet Manager 100 version 2.00

Created 6/6/2000 6:52:37 PM

Created By Jeremy Hartley (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 9:21:53 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 100, version 2.0

----- SUMMARY -----

The following is a list of what's new in FM Kienzle Fleet Manager 100 version 2.0.

The latest version of FM Kienzle Fleet Manager 100 software can be downloaded from the http://www.
mixtelematics.com website.

· Enhanced Service Reminders. Service reminders have been expanded to enable Duration based
reminders for vehicles that have low mileage. For example, a vehicle that does not travel the
10000Km (±6000miles) service interval in a year, it should still be serviced after 12 months. You may
set this as an option for each vehicle.

· Trip Report. Due to user-feedback, the format of the Trip Report has been changed. The ordering of
the columns has changed to reflect the Parking Time as the first column. This now reflects the time
the vehicle was stopped between the end of the previous trip to the start of the current trip (the old
format displayed the time between the end of the current trip and the start of the next trip).

· Fuel Usage. You may now enter fuel usage data, where the quantity/volume is in a different
measurement unit to the odometer reading (e.g. Miles and Litres).

· Consumption Types. You may now select the Fuel Consumption Type, for reporting purposes. (i.e.
litres/100Km or Km/litre)

· Reporting Groups. This allows a report to be printed for a specific group of vehicles or drivers,
instead of All or only one at a time. The reports and graphs that are able to take advantage of this
functionality are: Trip Report, Driving Errors Report, Driver Score Report, Fuel Consumption Report,
Violation Summary Graph, Driver Score Graph and Fuel Consumption Graph.

· Start Each Vehicle or Driver on a new page. This option has been added to the criteria for most
reports. This will optionally cause the report not to print data for more than one vehicle or driver on
the same page. The reports and graphs that are able to take advantage of this functionality are: Trip
Report, Driving Errors Report, and Fuel Consumption Report.

· Windows NT/2000 support. With the installation of the Fleet Manager 100 Windows NT and
Windows 2000 Download Drivers (1.30 Mb), FM100 is now fully compatible with Microsoft Windows
NT 4.0 and Microsoft Windows 2000.

· Delete Data Correction. There was an error, whereby if you deleted data for a vehicle in the future,

1398
www.mixtelematics.com

1398
 1399

the Last Trip Information for the vehicle did not get updated. This has been corrected.

------------------------------------------------------------------------------

KEYWORDS: FM100

1399
www.mixtelematics.com

1399
 1400
10.3.191 Knowledge Base Article 194

Article Number 194

Title Beep and Flash Codes Made EASY

Created 6/8/2000 11:58:06 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 9:16:23 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 100

· FM Kienzle Fleet Manager 200

----- SUMMARY -----

The Fleet Manager 100 and Fleet Manager 200 make use of simple beep and LED flash codes to
provide useful feedback and diagnostic information during installation, maintenance and normal
operation.

The following documents and Quick reference cards will greatly assist the installer and customer to
easily recognize and understand these codes.

Beep and Flash Codes.pdf

FM100 Beep and Flash Codes - Quick Ref Card.pdf

FM200 Beep and Flash Codes - Quick Ref Card.pdf

------------------------------------------------------------------------------

KEYWORDS: FM100 FM200 FM200e FM2000

1400
www.mixtelematics.com

1400
 1401
10.3.192 Knowledge Base Article 195

Article Number 195

Title Fleet Manager 2000 hangs while loading

Created 6/8/2000 12:11:55 PM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 11/30/2000 11:50:39 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

FM2000 hangs after the splash screen has been displayed.

----- CAUSE -----

For technical reasons it was necessary to change the Extension Manager type library exposed by the
FM2000 client after the inital release of FM2000. This means that any extensions that were compiled
against the new version of the type library will cause any version of FM2000 with the old type library to
hang and vice versa.

----- SOLUTION -----

The problem can be circumvented by preventing incompatible extensions from being loaded. To do
this you will have to edit the registry database as described below.

Please note that making incorrect registry changes can have a severe effect on the opertaion of your
computer and we CAN NOT be held responsible for any problems that may arise from such changes.

To correct the problem, run RegEdit.exe and navigate to the HKEY_LOCAL_MACHINE\SOFTWARE

\Data Pro Development (Pty) Ltd\Fleet Manager Client\Extensions key. This key has a subkey for each
extension installed on the computer. Each of these subkeys has a value called LoadOnStart. Edit this
value and change it to False for those extensions that you do not wish to be loaded when the FM2000
client starts.

----- ADDITIONAL INFORMATION -----

If you attempt to load an incompatible extension from within the FM2000 Extension Manager, the
program will crash. Besides this, setting an incompatible extension to load on startup via the Extension
Manager will once again cause the program to hang while loading.

----- STATUS -----

The FM2000 client from the SR1 release onwards will contain the new type library.

------------------------------------------------------------------------------

KEYWORDS: FM2000 extension manager sdk hang startup

1401
www.mixtelematics.com

1401
 1402
10.3.193 Knowledge Base Article 196

Article Number 196

Title No reports under FM98SR1b

Created 6/21/2000 9:41:00 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/18/2002 9:05:17 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, SR1b

----- SUMMARY -----

After upgrading to FM98 SR1b, there are problems creating reports/running criteria and batch files.

----- MORE INFORMATION -----

After installing FM98 SR1b, several error messages are displayed as soon as any of the following is
attempted: run reports, criteria files or batch files.

The error descriptions are as follows:

The following unexpected error/s occurred:

462 (0x000001CE): The remote server machine does not exist or is unavailable occurred in frmMain.
mnuReport_Click (Line 19220).

The following unexpected error/s occurred:

-2147217865 (0x080040E37): The Microsoft Jet database engine cannot find the input table or query
'Dummy'. Make sure it exists and that its name is spelled correctly. occurred in Report.
OpenReportDatabase (Line 4360). The error has been logged.

Fmserver

This program has performed an illegal operation and will be shut down. If the problem persists,
contact the program vendor.

----- SOLUTION -----

Upgrade to the latest version of the Fleet Manager software available, or to the later version of
FM98SR1b that is available on the Fleet Manager 2000 CD.

----- STATUS -----

These problems have been solved in the later version of SR1b available.

------------------------------------------------------------------------------

1402
www.mixtelematics.com

1402
 1403

KEYWORDS: FM200 FM200e SR1b

1403
www.mixtelematics.com

1403
 1404
10.3.194 Knowledge Base Article 197

Article Number 197

Title How to change graph defaults

Created 6/23/2000 5:41:34 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/23/2000 5:41:34 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

There have been several requests regarding the changing of the default Graph format to a user
specified format (using the chart type, style and layout available).

----- MORE INFORMATION -----

Several FM users have a certain preference for a different looking graph than the two-dimensional bar
graph template that is used by default.

It is possible to change the format of your graph, but this needs to be done for every single graph you
generate. The only time the format of a graph is saved, is when you save the graph itself together with
the data.

----- CAUSE -----

For every graph there is a .vtc file that is used as the template, and this template has been set to a
standard two-dimensional bar graph.

----- SOLUTION -----

TO CHANGE THE STANDARD GRAPH TEMPLATE:

You need to open the template of the specific graph you would like to format, make your changes here
(to the template), and save it.

The template files are the following:

ComparativeFuelConsumption.vtc represents the following fuel consumption graphs found under

[Menu: Reporting: Driver Graphs/Vehicle Graphs: Fuel Consumption: Measured by OBC: Comparitive]

DetailedFuelConsumption.vtc represents the following fuel consumptions graphs found under [Menu:
Reporting: Driver Graphs/Vehicle Graphs: Fuel Consumption: Measured by OBC: Detailed]

DriverScoring.vtc represents the Driver scoring graph found under [Menu: Reporting: Driver Graphs:
Driving Errors]

1404
www.mixtelematics.com

1404
 1405

DrivingErrors.vtc represents the Driving Error graphs found under [Menu: Reporting: Driver Graphs/
Vehicle Graphs: Driving Errors]

Profile.vtc represents the Vehicle Profile graph found under [Menu: Reporting: Vehicle Graphs: Profile]

To open the template files and change them:

1. Run Fleet Manager

2. On the Reporting Menu - Open Saved Graph

3. Choose any of the above-mentioned files (which should all be located in your Fleet Manager install
directory)

4. Change the format to whatever you want it to be

5. Save this file back to its original location (Fleet Manager install directory)

Every time you run the above formatted graph, it should display as you specified in step 4.

TO RESTORE THE STANDARD GRAPH TEMPLATE:

Copy the template files (.vtc files) from the Fleet Manager CD back to your Fleet Manager install
directory (typically C:\Program Files\Fleet Manager).

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000

1405
www.mixtelematics.com

1405
 1406
10.3.195 Knowledge Base Article 198

Article Number 198

Title Error 13 when trying to generate Event Report/Activity Timeline

Created 6/30/2000 9:15:45 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 2:14:48 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When trying to generate an Event Report or Activity Timeline, an unexpected Error 13 is displayed,
and the report/timeline will not generate. This error is not operating system specific.

----- MORE INFORMATION -----

Several error messages can be displayed when the above problem occurs. The detailed error
description may include any of the following:

The following unexpected error/s occurred:

13 (0x0000000D): Type mismatch occurred in frmActivity.ShowForm (line 1300). The error has been
logged.

The following unxepected error/s occurred:

13 (0x0000000D): Type mismatch occurred in frmCriteria.GetParameterBag (Line 1820). The error

has been logged.

The following unxepected error/s occurred:

13 (0x0000000D): Type mismatch occurred in frmCriteria.SetupPane (Line 1820).

----- CAUSE -----

The cause of this is that the short date style in your regional settings has no date separator or it has
an invalid date separator. In other words the format is similar to the following: ddmmyyyy (where dd
= day, mm = month and yyyy = year). The short date style must have a valid separator, you can use
any of the following: /, - or " " (space). As long as there is a valid separator specified in the Short
date style field itself, the above-mentioned error(s) won't occur.

----- SOLUTION -----

The solution to this is that you should change the short date style on date settings of your machine
to contain a valid short date separator. To do this, do the following:

1406
www.mixtelematics.com

1406
 1407

1. Click the Start button in the bottom left-hand corner of your screen.

2. Click Settings

3. Click Control Panel

4. Select Regional Settings

5. Go to the Date tab

6. Change the Short date style to dd/mm/yyyy or something similar with /, - or " " (space) as a
separator between the day (dd), month (mm) and year (yyyy).

7. Change the Short date separator to be /, - or " " (space), depending on what you specified in (6)
to be the Short date style separator.

----- STATUS -----

This problem is beyond our control.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000 Error 13

1407
www.mixtelematics.com

1407
 1408
10.3.196 Knowledge Base Article 199

Article Number 199

Title Error when attempting to create a new language set

Created 6/30/2000 12:12:22 PM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 6/30/2000 12:12:59 PM

Last Modified By Steve Crane (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Data Pro Language Editor

· Data Pro Language Manager SDK

· Data Pro Extension Manager SDK

----- SUMMARY -----

When selecting File|New in the Language Editor an error occurs.

----- MORE INFORMATION -----

When selecting File|New in the Language Editor the error message "Failed to open key '-
2147483647',Section: 'Software\Data Pro Development\Language Editor' for delete access" is
displayed.

----- CAUSE -----

Early versions of the install set did not install certain registry keys. When creating a new file the
program attempts to open one of these missing keys for delete access, thereby triggering the error.

----- SOLUTION -----

This can be rectified by creating the missing registry keys as follows.

1. Copy the following text and paste it into a new text file in Notepad.

---- copy from here ----

REGEDIT4

[HKEY_CURRENT_USER\Software\Data Pro Development\Language Editor]

"MaxCount"=dword:00000004

"Count"=dword:00000000

"DefaultLanguage"="English"

"BasicLangConst"="LangConst.bas"

1408
www.mixtelematics.com

1408
 1409

------- to here --------

2. Save the file as DPLangEd.reg then execute it.

You should now be able to use the File|New function without further problems.

----- STATUS -----

This has been corrected in later versions of the install set.

------------------------------------------------------------------------------

KEYWORDS: FM2000 SDK extension language editor manager error new

1409
www.mixtelematics.com

1409
 1410
10.3.197 Knowledge Base Article 200

Article Number 200

FM Kienzle SI No. 381008 - Using the Fleet Manager Software FM100 with Windows
Title
2000

Created 7/6/2000 10:38:59 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 3/10/2004 4:12:16 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· FM Kienzle Fleet Manager 100

----- SUMMARY -----

An update of the existing FM 100 installation is necessary to enable the Fleet Manager 100 Program
running on Windows 2000 to communicate with the download pod. You may request this free of
charge from FM Kienzle, or download it from the http://www.mixtelematics.com website. It replaces
the previous update FM100NT4.exe, and is also used to update the FM100 Software running on
Windows NT4.0.

Please note:

Administrator rights are necessary to execute this on Windows NT 4.0 or Windows 2000.

The FM100 Software does not obtain network capability through the installation of the Windows NT
4.0/2000 Update described in this service information! It may still only be executed on a single
computer.

Installation of the Fleet Manager 100 Windows NT4.0/2000 Update:

1. Make a backup of the FM100 database (FM100.mdb)

2. Run the file FM100_NT.exe and follow the instructions in the setup program. For all program files to
be registered by the operating system the user log-on after the computer has been rebooted has to
take place with administrator rights.

3. Run FM100 and check the communication with the download pod.

----- MORE INFORMATION -----

To download this document in .pdf format click FM SI No 381008.

------------------------------------------------------------------------------

KEYWORDS: FM SI FM100

1410
www.mixtelematics.com

1410
 1411
10.3.198 Knowledge Base Article 203

Article Number 203

FM Kienzle SI No. 381005 - Fleet Manager 100 -- Operation with an external speed
Title
signal sender

Created 7/6/2000 12:14:33 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 5:10:24 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 100

----- SUMMARY -----

The Fleet Manager 100 can be used with an external speed signal sender.

----- MORE INFORMATION -----

For more information, please refer to the following FM SI document: FM SI No 381005.

------------------------------------------------------------------------------

KEYWORDS: FM SI FM100

1411
www.mixtelematics.com

1411
 1412
10.3.199 Knowledge Base Article 204

Article Number 204

Title Importing FM100 Version 2 database into FM98/FM2000 fails

Created 7/6/2000 4:08:38 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/30/2000 2:15:14 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 100, Version 2

· FM Kienzle Fleet Manager 98, All versions

· FM Kienzle Fleet Manager 2000, Client Version 4.00.0013

----- SUMMARY -----

Importing a FM Kienzle Fleet Manager 100 database (FM100.mdb) into FM Kienzle Fleet Manager
software fails. This is accompanied by a message stating that the FM100 database is of the wrong
version, and that it should be upgraded to version SR3 (FM100 version 1.1) or SR4 (FM100
version 1.2).

----- MORE INFORMATION -----

The message received reads as follows:

The C:\FM100\FM100.mdb database is from an unknown version of FM100. Please upgrade this
database to FM100 SR3 or SR4 before attempting to import this database into the FM2000
system.

The FM100 Service Release is available on the FM2000 CD or from the Download section of the
Fleet Manager Web Site (http://www.datapro.co.za/development).

----- CAUSE -----

When the Fleet Manager software imports a FM100 database, it looks for a FM100 version 1.1 or
version 1.2 database. It sees a FM100 version 2 database and does not recognise it as a valid
FM100 database.

----- SOLUTION -----

We are investigating a solution, in the meantime the following is proposed as workaround:

Import from a backup of the database (FM100.mdb), version 1.1 (SR3) or version 1.2 (SR4).

----- STATUS -----

This has been corrected in FM Kienzle Fleet Manager 2000 Second Edition (Version 5.00.0003).

1412
www.mixtelematics.com

1412
 1413

------------------------------------------------------------------------------

KEYWORDS: FM100 FM200 FM200e FM2000

1413
www.mixtelematics.com

1413
 1414
10.3.200 Knowledge Base Article 205

Article Number 205

Title FM98 SR1b Reports hangs

Created 7/27/2000 4:07:51 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 7/27/2000 4:13:24 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, SR1b

----- SUMMARY -----

Generating report hangs after upgrading to FM Kienzle Fleet Manager 98 version SR1b.

----- MORE INFORMATION -----

Reports generate without any problem in FM98 SR1 or FM98 SR1a, but after upgrading to SR1b,
NO report generates. The report starts generating, but hangs during the initial stages of generating
the report.

----- CAUSE -----

When upgrading to FM98 SR1b, the FMReports.mde file are overwritten with a "new" FMReports.
mde. If MSAccess is running while upgrading, the "old" FMReports is not overwritten. Instead the
existing FMReports.mde is renamed to FMRe~1.mde. In the Fleet Manager install directory (typically
C:\Program Files\Fleet Manager) there will be more than one FMReports.mde. Some of there
FMReports.mde's will be renamed to be FMRe~x.mde where "x" represents any number, begin from
1.

----- SOLUTION -----

A solution to the above problem would be to do the following:

1. On the Start menu (on your computer - left bottom corner) go to Control Panel - FM98
Administrator

2. Lock the database by clicking the green cylindrical icon of the FMAdmin program

3. Double click Server Options

4. Select the Reports Database File, and click the Modify command button.

5. Select the appropriate Reports Database File (usually it would be FMReports.mde and click
Open).

6. Unlock the database and quit FMAdmin

7. Run the Fleet Manager software, and try to generate a new report.

1414
www.mixtelematics.com

1414
 1415

If this doesn't succeed, repeat steps 1 to 7, and instead of choosing FMReports.mde in step 5,
choose one of the FMRe~x.mde files until you are able to generate reports.

If the file your Reports Database File points to is NOT FMReports.mde, but one of the FMRe~x.mde
files, do the following:

1. Delete FMReports.mde

2. Rename the correct FMRe~x.mde file to FMReports.mde

3. Delete all other FMRe~x.mde files.

4. Repeat steps 1-7 above, to set the Reports Database File again, as you have now renamed it,
and FMAdmin will not recognise the renamed file.

You should be able to generate reports now.

----- STATUS -----

This problem occurs when upgrading while certain files/programs are still open/running. It is good
practice to exit everything, and reboot your pc before installing/upgrading any software. This is not a
Fleet Manager software error/problem.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM98 SR1B

1415
www.mixtelematics.com

1415
 1416
10.3.201 Knowledge Base Article 206

Article Number 206

Title Relay Enabled parameter incorrectly set

Created 7/28/2000 4:26:46 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/30/2000 2:05:29 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, version 4.00.0013

----- SUMMARY -----

When the Relay Enabled parameter is set to TRUE in the Event Configuration, it records when
the Relay is disabled (instead of enabled), and vica versa.

----- MORE INFORMATION -----

The FM200e Event FM200e - System Bypassed Idle uses the Relay Enabled parameter. The
default settings for this event look as follows:

Relay Enabled = TRUE AND

Engine RPM > 0

This event only records when Relay Enabled = FALSE (this is visible on the Activity Timeline/
Trip/Event reports).

----- SOLUTION -----

This will be solved in the next release of the Fleet Manager 2000 software, but the following can
serve as a workaround for the moment:

1. Create a new User Event (Call it anything, but for clarity something to do with System
Bypassed Idle)

2. Insert the following settings/parameters:

Relay Engaged FALSE AND

Engine RPM > 0

3. Disable the "incorrect" System Bypassed Idle Event and enable this newly created System
Bypassed Idle user event.

4. Ensure that the Record and Action tabs are set up exactly as that of the original System
Bypassed Idle Event.

----- STATUS -----

1416
www.mixtelematics.com

1416
 1417

This has been corrected and included in the next version of the Fleet Manager 2000 software
(FM Kienzle Fleet Manager 2000 Second Edition -version 5.00.0003).

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000

1417
www.mixtelematics.com

1417
 1418
10.3.202 Knowledge Base Article 207

Article Number 207

Title Runtime error '40052' when accessing vehicle servicing

Created 8/7/2000 12:13:08 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 5:09:34 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 100, Version 2.00.0197

----- SUMMARY -----

When accessing the servicing of any vehicle in a FM Kienzle Fleet Manager 100 database with the
language set to Français, a runtime error '40052' occurs.

----- MORE INFORMATION -----

The error reads as follows:

Runtime error '40052'

Unable to retrieve localised string (8958).

It has been verified that this error only occurs when the Configured Language (on the International
tab of the FM100) has been set to French.

----- CAUSE -----

This error is caused by an incorrect translation in the French language file.

----- SOLUTION -----

Upgrade to the latest available version of the Fleet Manager 100 software.

----- STATUS -----

This has been fixed in the next version of the FM100 software.

------------------------------------------------------------------------------

KEYWORDS: FM100

1418
www.mixtelematics.com

1418
 1419
10.3.203 Knowledge Base Article 208

Article Number 208

Title Unable To Upload Customised FM Terminal Menu Script

Created 8/15/2000 12:41:13 PM

Created By Colan Tredrea (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 5:01:58 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, version 4.00.0013

· makescr.exe, prior to version 1.2

----- SUMMARY -----

Unable to upload customised FM Terminal Menu Script

----- MORE INFORMATION -----

The customised FM Terminal menu script compiles correctly, but when uploading, the FM Terminal
sounds a 5 second beep and does not load the new menu script. This may occur when certain
customised scripts are uploaded. It does not apply to standard FM Terminal menu scripts.

----- SOLUTION -----

Click here to download an updated FM Terminal menu script compiler. Place this file in 'c:\program
files\fleet manager\fm terminal' directory. This updated version will be included in the next release of
FM2000 (FM2000 SE).

----- STATUS -----

Corrected in FM Terminal script compiler (makescr.exe) ver1.2.

This updated version will be included in the next release of FM2000 (FM2000 SE).

------------------------------------------------------------------------------

KEYWORDS: FMT Terminal

1419
www.mixtelematics.com

1419
 1420
10.3.204 Knowledge Base Article 209

Article Number 209

Title PC won't shutdown while FMAPC is running

Created 9/6/2000 10:13:34 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 9/6/2000 10:16:13 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

· Fleet Manager Autopoll Client, version 5.00.0003

----- SUMMARY -----

It is not possible to shutdown/restart your computer while the Fleet Manager Autopoll Client is
running.

----- MORE INFORMATION -----

After installing version 5.00.0003 of the Fleet Manager Autopoll Client, it is no longer possible to
shut down your computer while the Fleet Manager Autopoll Client is running (the FMACP icon is still
displayed in the task tray).

When attempting a restart/shutdown while Autopoll is running, no error messages are given, and the
computer’s screen view returns to the desktop, without shutting down/restarting.

----- SOLUTION -----

The solution is to shut the Fleet Manager Autopoll Client down manually, and then restart the
computer:

1. Right click the green FMAPC/download icon in the task tray.

2. Select "Exit" on the popup menu

3. Restart/shutdown your computer.

----- STATUS -----

This is by design, as it ensures that the Autopoll will not be interrupted while transferring data.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000 FMAPC

1420
www.mixtelematics.com

1420
 1421
10.3.205 Knowledge Base Article 210

Article Number 210

FM Kienzle SI No. 382012 - Using the FM200 with the Mercedes Benz PSM-Module
Title
(parameterizable special module)

Created 9/8/2000 4:19:54 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 5:00:55 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 100

· FM Kienzle Fleet Manager 200

----- SUMMARY -----

When using the FM200 with the MB PSM Module (MB ACTROS, MB ATEGO, ...) please note that
this module has to be activated and parameterized by a Mercedes Benz workshop before the FM200
can be supplied with a speed or revolution count signal.

A number of settings can be made when parameterizing the revolution count signal. For perfect
processing of the revolution count signal the PSM-Module should be set to 8 pulses/revolution.

Please note:

The speed or revolution count signals may not be read directly on the FTCO as this could lead to
disturbances in the vehicle diagnosis system.

The parameterizable special module is only installed in certain specially equipped vehicles. As a
result MB vehicles may have to be retrofitted with the PSM.

----- MORE INFORMATION -----

To download this document in .pdf format click FM SI No 382012.

------------------------------------------------------------------------------

KEYWORDS: FM SI FM100 FM200 FM200e FM2000

1421
www.mixtelematics.com

1421
 1422
10.3.206 Knowledge Base Article 211

Article Number 211

Title F3 parameter does not accept 'Units' description when added

Created 10/16/2000 1:06:30 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 10/16/2000 1:06:30 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, Second Edition (Version 5.00.003)

----- SUMMARY -----

When adding a pulse counter parameter, unchecking "This is a fuel parameter", and entering a
description for "Units", the value for "Units" is not saved with the rest of the new parameter's
settings.

----- MORE INFORMATION -----

Adding the parameter as follows, results in the above situation:

1. Add parameter

2. Select "Pulse counter"

3. Uncheck "This is a fuel parameter"

4. Enter description for Parameter

5. Enter description for Units

6. Save the parameter

When opening the parameter again, you will find that the value entered for "Units" wasn't saved
with the rest of the parameter settings.

----- SOLUTION -----

The workaround given to the above situation would be to Edit the already created parameter, and
enter the value/description for "Units" now.

1. Select the parameter

2. Click the "Edit" command button

3. Enter a description for "Units"

4. Save & close

1422
www.mixtelematics.com

1422
 1423

The value/descriptions for "Units" will now be saved together with the rest of the parameter's
settings.

----- STATUS -----

This functionality is by design, and will not be changed for the current version of the Fleet
Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000

1423
www.mixtelematics.com

1423
 1424
10.3.207 Knowledge Base Article 212

Article Number 212

Title Fleet Manager on Windows ME

Created 10/27/2000 12:13:16 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/30/2000 12:01:57 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, version 4.00.0013

----- SUMMARY -----

The above products will not be supported on Windows ME, as they were released prior to the
release of Windows ME.

The error described in the following section of this Knowledge base article, is only one of many
that might occur on Windows ME.

When running Fleet Manager 2000 (version 4.00.0013) on Windows Millennium, an unexpected
error 429 occurs when trying to download data from a vehicle plug into the database.

----- MORE INFORMATION -----

The error message reads as follows:

'Unexpected Error' 429 (0x000001AD): ActiveX Component can't create object in FM200Data.
PreProcess (Line 6960).

----- SOLUTION -----

This version of the Fleet Manager software was released before Windows ME. You won't be able
to download data into the database.

The only solution is to either upgrade to Fleet Manager 2000, second edition, or run the Fleet
Manager 2000 (version 4.00.0013) software on a different Windows operating system.

----- STATUS -----

The functionality is by design, and will not be changed.

The FM Kienzle Fleet Manager 2000 Second Edition runs on Windows ME.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000

1424
www.mixtelematics.com

1424
 1425
10.3.208 Knowledge Base Article 213

Article Number 213

Title Error 3075 when generating ANY Report

Created 10/27/2000 12:50:28 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:59:45 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, version 4.00.0013

----- SUMMARY -----

When executing any report, you may receive an error 3075 while the report is generating.

----- MORE INFORMATION -----

The error occurs during the "Extracting Data" phase of the report generation. The exact wording of
the error message is as follows:

The following error/s occurred while communicating with the server:

3075

If this error is specific to Event reports, please see KBA 184 (Error 3075 Generating Event Report
for a more descriptive solution to this specific problem.

If you have access to Centre-Point, go to KBA 184 (Error 3075 Generating Event Report),
otherwise go to the http://www.mixtelematics.com website, and search the Knowledge base for
Error 3075 or 184.

----- CAUSE -----

This is caused by an error in the reporting engine.

----- SOLUTION -----

1. Please download the FMReports.zip file,

2. Restart you computer to ensure that none of the FM components are running.

3. Extract this file, and copy it to your Fleet Manager install directory

----- STATUS -----

This has been solved in the FMReports.mde file available, as well as in the FM Kienzle Fleet
Manager 2001 software.

1425
www.mixtelematics.com

1425
 1426

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000

1426
www.mixtelematics.com

1426
 1427
10.3.209 Knowledge Base Article 214

Article Number 214

Title Latest Device Drivers for FM200 and FMTerminal

Created 11/17/2000 1:56:18 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:49:17 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· The FM Kienzle FM200 on-board computer and FMTerminal.

----- SUMMARY -----

Ongoing development on the FM200 and FMTerminal results in new versions of device drivers (DDR/
DDM) being released from time to time.

----- MORE INFORMATION -----

Adding new peripherals to the FM200 (GSM modem, FM-Info, FM-Splitter) may require you to update
your vehicle unit's device drivers.

After upgrading to a later version of the Fleet Manager software, it is often necessary to update the
device drivers in the vehicle units, in order to support new functionality.

----- SOLUTION -----

Download the latest version of FMDealer:

1. FMDealer Standalone

2. FMDealer Extension

Use the FMDealer program to upload the latest device drivers for the appropriate devices connected
to your FM200.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000 FM2001 DDR DDM FMT

1427
www.mixtelematics.com

1427
 1428
10.3.210 Knowledge Base Article 215

Article Number 215

Title How To Add More Digital Inputs To The FM200

Created 11/20/2000 9:21:09 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 7/19/2007 11:16:08 AM

Last Modified By Michael Chamberlain (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 200

----- SUMMARY -----

Increase the number of FM200 digital inputs from 4 to 8.

----- MORE INFORMATION -----

The FM200 has 4 analogue inputs available for measuring analogue or digital signals. If additional
digital inputs are required, these 4 inputs can each be split into 2 digital inputs, resulting in a total
of 8 digital inputs.

For more details, please download the document:How To Multiplex An FM200 Analogue Input.pdf

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000 FM2001

1428
www.mixtelematics.com

1428
 1429
10.3.211 Knowledge Base Article 216

Article Number 216

Title Is the FM200 / FM300 Unit Intrinsically Safe?

Created 11/20/2000 4:13:03 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 3/9/2006 11:25:34 AM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

· FM Kienzle Fleet Manager 2001, all versions

· FM Fleet Manager 2002, all versions

· FM Fleet Manager Office

· FM Fleet Manager 200 unit

· Fleet Manager Professional 8

· FM200 Plus series units

· FM300 series units

· Related hardware components connected to FM units mentioned above

----- SUMMARY -----

In general, the cabinet (driver) area of a vehicle is classified as a non-hazardous area, i.e. has a
small probability of a flammable mixture being present. Non-intrinsically safe equipment installations,
such as radios and phone chargers, are allowed in these areas. It is recommended that, in situations
where intrinsic safety is required, the FM200 or FM300 unit be installed in such a non-hazardous
zone.

----- MORE INFORMATION -----

However, the final authority on what is and is not a safe equipment installation rests with the "Safety
Enforcement Authority" for that area. This authority may be a representative of the insurance
underwriters, a local government inspector or a member of the corporate safety organization. The
FM200 or FM300 unit has not been classified as intrinsically safe for a particular Class, Zone,
Division, and Group of hazard as classified by the North American Electrical Codes, IEC, European,
or other agencies.

Here follows a brief overview of intrinsic safety and hazardous areas as defined by the various
international authorities.

1429
www.mixtelematics.com

1429
 1430

What is Intrinsically Safe?

Intrinsically safe means "Inherently Safe." Intrinsically safe equipment is defined as: "equipment
wiring which is incapable of releasing sufficient thermal or electrical energy under normal or abnormal
conditions. To cause ignition of a specific hazardous atmosphere mixture in it's most easily ignited
concentration." (ISA-RP12.6)

In order to have a fire or explosion, fuel, oxygen and a source of ignition must be present. An
intrinsically safe system assumes the fuel and oxygen is present in the atmosphere, but the system is
designed so the electrical energy or thermal energy of a particular instrument loop can never be great
enough to cause ignition.

What Constitutes a Hazardous Area?

An area classified as "hazardous" is an area in which the atmosphere contains, or may contain,
flammable or explosive gases, dusts, or fibres. In this type of area, fire or explosion could occur when
all three basic conditions are fulfilled:

1. Flammable gas, vapour, dust or fibres must be present.

2. The combustible material must be mixed with air in the proportions required to produce a
flammable mixture.

3. A source of ignition must act to ignite the mixture. The source under consideration is any portion of
the instrumentation system that could release sufficient energy to cause ignition. A spark or hot
surface may release the incendiary energy.

In the United States, the National Electrical Code, Article 500 for both Zones and Divisions, Canada,
Canadian Electrical Code, Section 18 for Zones, defines a hazardous area by applying a three-part
classification. In Europe the classification is in type of industry and degree of hazard. See the
following tables, for relationship of North America, European definitions and comparisons.

Applying safety barriers requires some knowledge of intrinsic safety principles and terminology.

To view a table of the two main systems in international use, view Safety Barriers Table.

And a Non-hazardous (Safe) Area?

An area classified as non-hazardous has a small probability of a flammable mixture being present. It
is also called a "safe area" and includes most control rooms.

Who Deals with Instrument System Certification?

The Safety Enforcement Authority's job is made easier if the proposed equipment is certified for use
in the hazardous area by a private or government-testing agency. The testing agency subjects the
equipment to rigorous electrical tests varying in difficulty depending on the Class, Zone, Division, and
Group of hazard for which the equipment is being certified.

Over the years several testing agencies have earned the confidence of safety enforcement
authorities in their respective countries. A partial listing, by country, of several major-testing agencies
includes the following:

USA CSA/NRTL, Factory Mutual System (FM), or UL

Canada Canadian Standards Association (CSA) or UL

Europe British Approvals Service for Electrical Equipment in Flammable Atmospheres (BASEEFA),
or SIRA, or Laboratoire Central Des Industries Electriques (LCIE)

1430
www.mixtelematics.com

1430
 1431

Japan Safety Standard (RIIS)

Australia Standards Association of Australia (SAA)

International Electrotechnical Commission IEC International Standards for other countries.

Safety enforcement authorities within that country generally accept certification by one of these
agencies. Safety enforcement authorities in other countries may also accept this certification as valid
for their own applications.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM300

1431
www.mixtelematics.com

1431
 1432
10.3.212 Knowledge Base Article 217

Article Number 217

Title Connecting A Keyboard or Barcode Scanner To The FM Terminal

Created 11/22/2000 5:24:53 PM

Created By Colan Tredrea (MiX Telematics - Stellenbosch)

Last Modified 11/24/2006 12:25:35 PM

Last Modified By Bülent Bas (Siemens FM Automotive - Switzerland)

Details ----- APPLIES TO ----

· FM Terminal

----- SUMMARY -----

Which keyboards and barcode readers can be connected to the FM Terminal?

How is the keyboard or barcode reader connected to the FM Terminal?

----- SOLUTION -----

Click here to download the document Connecting A Barcode Reader To The FM Terminal.pdf which
provides details on connecting a keyboard or barcode reader to the FM Terminal.

------------------------------------------------------------------------------

KEYWORDS: FMT Terminal

1432
www.mixtelematics.com

1432
 1433
10.3.213 Knowledge Base Article 218

Article Number 218

Title FM2000SE extensions not to be installed with previous versions of FM

Created 11/24/2000 10:12:14 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/24/2000 10:17:27 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, all versions

· FM Kienzle Fleet Manager 2001

----- SUMMARY -----

The extensions included on the Fleet Manager 2000 Second Edition (version 5) CD, should not be
installed with previous versions (i.e. Fleet Manager 2000 version 4.00.0013) of the Fleet Manager
software.

----- MORE INFORMATION -----

When installing one of the Fleet Manager 2000 SE extensions with a previous version of the Fleet
Manager software some errors might occur. These errors include the following:

1. The client will not start

2. The Fleet Manager system hangs.

----- CAUSE -----

Installation of extensions with incorrect version of Fleet Manager software.

----- SOLUTION -----

To solve the above mentioned problem:

1. Restart your computer

2. Install FM2000 Second Edition or higher

3. Reinstall all extensions.

----- STATUS -----

Any extensions included on the Fleet Manager 2000 Second Edition CD can only be installed with
FM2000 SE and later versions.

This is by design, and will not be changed.

1433
www.mixtelematics.com

1433
 1434

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000 FM2001 Extensions

1434
www.mixtelematics.com

1434
 1435
10.3.214 Knowledge Base Article 219

Article Number 219

Title When to use the Event Configuration File (.ecf)

Created 11/28/2000 10:14:28 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/28/2000 11:30:31 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

This Knowledge base article describes the procedure of when and how to restore an event
configuration file (.ecf).

----- MORE INFORMATION -----

The event configuration file (.ECF) is only used when creating a new database. The Fleet Manager
system ships standard with an ECF file per language. If you have a valid backup of the Fleet
Manager database, the event configuration file is not required to restore an event configuration.

An event configuration file of a user's events is creating during a backup in case the backup of the
actual database is lost/corrupt etc.

In this case, the following is recommended:

1. The user may then copy his ECF file over the standard ECF (i.e. for English, the user would
rename English.ECF, then rename .ecf as English.ECF)

2. Create a new database (by executing FMCreateDB.exe wich uses the language specified by
FMAdmin). This database will contain the same event configuration as the previous (now corrupted)
database.

----- STATUS -----

This functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000

1435
www.mixtelematics.com

1435
 1436
10.3.215 Knowledge Base Article 220

Article Number 220

Title Abnormally high duration values on Daily Driver Trip report

Created 12/1/2000 5:18:57 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:40:56 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When generating a daily driver trip report, the values displayed as duration is abnormally high.

----- MORE INFORMATION -----

This only occurs on the driver trip report (values far more than 24 hours per day). The values
displayed on the Vehicle Trip report are realistic.

----- CAUSE -----

This is caused by an error in the reporting engine.

----- SOLUTION -----

1. Please download the FMReports.zip file,

2. Restart you computer to ensure that none of the FM components are running.

3. Extract this file, and copy it to your Fleet Manager install directory

----- STATUS -----

This has been solved in the FMReports.mde file available, as well as in the FM Kienzle Fleet
Manager 2001 software.

------------------------------------------------------------------------------

KEYWORDS:FM200 FM200e FM2000 FMReports

1436
www.mixtelematics.com

1436
 1437
10.3.216 Knowledge Base Article 221

Article Number 221

Title FMDealer displays no text

Created 12/7/2000 11:34:11 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:39:45 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, Second Edition

· FMDealer, Version 2.3.1.0

----- SUMMARY -----

When opening the FMDealer program (version 2.3.1.0), after installing either the extension or Stand-
alone, no text are displayed on the FMDealer program itself.

----- MORE INFORMATION -----

This usually occurs when installing either the Stand-alone, or the Extension in German. When
selecting English as language, this doesn't occur. When German is selected as language (after
installation), the FMDealer will automatically revert to English when started up again.

----- CAUSE -----

This is a problem in the language files for this version of the FMDealer.

----- SOLUTION -----

Please download and install either or both of the following install sets for FMDealer:

1. FM Dealer -stand alone.

2. FM Dealer -extension.

----- STATUS -----

This problem has been fixed in the latest version of FMDealer as specified in the solution of this KBA.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000 FMD FMDealer Dealer

1437
www.mixtelematics.com

1437
 1438
10.3.217 Knowledge Base Article 222

Article Number 222

Title Error when printing report in FM100 version 2

Created 12/13/2000 5:25:19 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:38:35 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 100, version 2

----- SUMMARY -----

When trying to print any report after installing FM100 version 2 (using Letter size paper), the message
"Add A4 Paper" is displayed, and the printed reports' margins are set incorrectly.

----- MORE INFORMATION -----

When installing FM100, you get an option to choose between "A4 (210 x 297 mm)" and "Letter (8 1/2 x
11 in)". When selecting Letter size paper, the above-mentioned problem occurs.

----- CAUSE -----

The FM100 version 2 install set does not install the report templates for Letter paper.

----- SOLUTION -----

1. Download the LetterReports.exe file

2. Extract this file to your FM100\LTRRPT directory (typically C:\FM100\LTRRPT).

3. Try generating reports now!

----- STATUS -----

This has been fixed in the file available, and will be fixed in the next version of FM100.

------------------------------------------------------------------------------

KEYWORDS: FM100

1438
www.mixtelematics.com

1438
 1439
10.3.218 Knowledge Base Article 223

Article Number 223

Title Error selecting 'Is Not' in Contact Organisation combo on adhoc query.

Created 1/10/2001 2:42:04 PM

Created By Wesley De La Harpe (MiX Telematics - Stellenbosch)

Last Modified 5/28/2001 9:19:04 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Centre-Point Service Tracker

----- SUMMARY -----

Returns an error '3464: Data type mismatch in criteria expression. occurred in SRQuery.BuildForm
(Line 5700).'

----- CAUSE -----

If a user selects 'Is Not' in the Contact Organisation section of the Adhoc Query.

----- SOLUTION -----

The latest version of the CPUI.DLL needs to be installed.

----- STATUS -----

The Problem has been fixed

------------------------------------------------------------------------------

KEYWORDS:3464 Data type mismatch SRQuery.BuildForm 5700 CENTRE-POINT

1439
www.mixtelematics.com

1439
 1440
10.3.219 Knowledge Base Article 224

Article Number 224

Title FMClient hangs after installing FMAPC

Created 1/16/2001 4:52:11 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:37:29 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

· FM Kienzle Fleet Manager 2001, all versions

· FM Kienzle Fleet Manager Autopoll Client, version 6.0.0.7

----- SUMMARY -----

After installing the Fleet Manager Autopoll client, version 6.0.0.7 on Windows 2000, the Fleet Manager
Client hangs.

----- MORE INFORMATION -----

When executing the Fleet Manager software after installing the Fleet Manager Autopoll client on
Windows 2000, all code plug functions are disabled and/or the Fleet Manager Client hangs when
trying to download/access any code plug functions via either the Autopoll or Fleet Manager software.

----- CAUSE -----

This is caused by an incorrect version of the DMI2.exe and DMIAP.exe (download module interface
files) being installed by the Autopoll install set. The version being installed is for Windows 9x instead
of WindowsNT/2000.

----- SOLUTION -----

As a current workaround to this problem:

1. Exit the Autopoll, and ensure that it is removed from the startup menu.

2. Ensure that NO Fleet Manager software is running

3. Restart your computer, and then do either of the following:

A. COPY THE CORRECT FILES FROM THE FLEET MANAGER CD IN USE

1. Go to the Windows NT Specific Files directory on your Fleet Manager CD (this can be any Fleet
Manager CD, preferrably FM2000SE or later)

1440
www.mixtelematics.com

1440
 1441

2. Copy the two files dmi2.exe and DmiAp.exe

or

B. DOWNLOAD THE FOLLOWING FILE (CONTAINING THE DMI2.EXE version 0.1.6.1 AND DMIAP.
EXE version 0.0.1.12)

1. DMI.zip

2. Unzip the contents of this file (dmi2.exe and DmiAp.exe) to your Fleet Manager install directory

----- STATUS -----

This will be fixed in the next version of the Fleet Manager Autopoll Client, whereafter this KBA will be
updated.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000 FMAPC AUTOPOLL FM2001

1441
www.mixtelematics.com

1441
 1442
10.3.220 Knowledge Base Article 225

Article Number 225

Centre-Point Database Grows Abnormally Large (Centre-Point causes Infinite E-Mail

Title
loop)

Created 1/18/2001 4:11:59 PM

Created By Graham Downs (GDC)

Last Modified 6/14/2002 4:36:12 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Centre-Point Service Tracker, all versions

----- SUMMARY -----

The Centre-Point System continually sends out e-mails to itself. As a result, the database grows
abnormally large.

----- MORE INFORMATION -----

For a given service request, the Last Action list grows very large, and keeps growing. The items in
this list do not appear to make logical sense - as if comments are simply being e-mailed and replied
to constantly. This also causes a severe bottleneck in your company's internal e-mail system, and
while this is happening, the Centre-Point system will be abnormally slow.

----- CAUSE -----

This problem can occur in one or both of the following cases:

1. The "System Administrator" contact in your Centre-Point system has been given an e-mail
address. This e-mail address will be the same as that of the Centre-Point mailbox in your e-mail
system.

2. For a given service request(s), an e-mail address is entered in the "Other" field. This e-mail
address will be the same as that of the Centre-Point mailbox in your e-mail system.

When a request is logged or actioned, Centre-Point is designed to send out an e-mail message to
all the contacts that are checked for that service request (SR) record. In addition, it was also e-mail
any additional addresses specified in the "Other" field for the request.

In addition, it is designed to reply to any e-mail sent to its address. (i.e. the address of the Centre-
Point mailbox within your e-mail system.

If, when a request is added or actioned, one of the contacts selected to be e-mailed has an e-mail
address which is the same as the Centre-Point mailbox in your e-mail system, or this address is
explicitly defined in the "Other" field of that request, the system e-mails itself. It then replies to that
e-mail, e-mailing itself again. This results in an endless loop, with the system e-mailing itself ad
infinatum.

----- SOLUTION -----

1442
www.mixtelematics.com

1442
 1443

To solve this problem, follow these steps:

1. Stop the "Centre-Point Mail Server" service.

2. Open the Centre-Point user's mailbox using an e-mail client (e.g. Microsoft Outlook), and remove
all messages in the "Inbox" and "Sent Items" folder for this user.

3. Log into Centre-Point system with "System Administrator" priveledges. Identify the service
request(s) that exhibit the problem, and delete them. (Note: All information relating to the deleted
service requests will be lost!)

4. Go through your Centre-Point Contacts list, and ensure that no contact in your database has an
e-mail address which is the same as that of the Centre-Point mailbox in your e-mail system.

Once this has been completed, you will notice that because of all this activity, your Centre-Point
database (Typically C:\Program Files\Centre-Point\Data\CP.mdb) has grown very large. If you
would now like to attempt to reduce it's size, then please click here to download a file called
CompactCPDB.zip (7 kb). Extract and run this file on your Centre-Point server computer, and follow
the on-screen prompts. Note: This application does not guarantee to substantially reduce the size
of your Centre-Point database, depending on how much data is in your database. It will, however,
help to clean up wasted disk space resulting from the above problem.

----- STATUS -----

This problem is by design. We do not reccommend referring to the e-mail address of the Centre-
Point mailbox within your e-mail system anywhere in your Centre-Point system.

------------------------------------------------------------------------------

KEYWORDS: CENTRE-POINT

1443
www.mixtelematics.com

1443
 1444
10.3.221 Knowledge Base Article 226

Article Number 226

Title Paper Size Error when printing report

Created 1/23/2001 1:57:19 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:33:12 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 100, version 2

----- SUMMARY -----

When attempting to print ANY report, the printer generates an error instructing you to add A4 paper,
even though it is suppose to print on Letter Size Paper (8 1/2 x 11).

----- MORE INFORMATION -----

This occurs even though FM100 was installed with Letter size paper (8 1/2 x 11) selected during the
install process.

----- CAUSE -----

FM100 version 2 does not install the report templates for Letter paper.

----- SOLUTION -----

Download this file: LetterReports.exe

and extract its contents to the LTRRPT folder. (Typically C:\FM100\LTRRPT)

----- STATUS -----

This has been fixed, and will be included in the next version of FM100.

------------------------------------------------------------------------------

KEYWORDS: FM100

1444
www.mixtelematics.com

1444
 1445
10.3.222 Knowledge Base Article 227

Article Number 227

Title Reload DDRs after upgrading to FM2000SE

Created 1/25/2001 10:11:03 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 1/25/2001 10:11:03 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, Second Edition

----- SUMMARY -----

After upgrading from a previous version of the Fleet Manager software, to Fleet Manager 2000 SE, it is
necessary to reload the device drivers of the FM200 unit.

----- MORE INFORMATION -----

The reloading of the latest device drivers is necessary, as certain enhancements were made in the
device drivers of FM2000SE. Trying to upload a new event configuration onto the vehicle unit, before
updating the device drivers, will fail, as the new configuration is dependent on certain enhancements
made in some of the later device drivers.

----- SOLUTION -----

Please upload the latest device drivers (or device drivers for FM2000SE specifically) to each unit
before trying to update the event configuration. You can do this by creating a Device Driver plug from
the code plug menu from within the Fleet Manager 2000SE software.

----- STATUS -----

The functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: DDR FM200 FM200e FM2000

1445
www.mixtelematics.com

1445
 1446
10.3.223 Knowledge Base Article 228

Article Number 228

Title Exported Vehicle Configuration Report vs Snapshot version of the report

Created 1/25/2001 11:08:51 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 1/25/2001 11:09:43 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When comparing the Vehicle Configuration report with the exported version of this report (for the
same vehicle), the information on the exported file is not complete.

----- MORE INFORMATION -----

The exported file contains only the Event configuration for the vehicle, and not all the other information
displayed in the Snapshot created report.

----- CAUSE -----

There are two sub-reports, both displayed on the Snapshot file, but both of them cannot be exported
into one file.

----- SOLUTION -----

The workaround for this is not to export a Vehicle Configuration report.

After upgrading to FM2001, any saved Criteria file for the Vehicle Configuration Report should be
recreated. Opening a FM2000 criteria file which specified that an export is to be done will still create
the old format of export.

----- STATUS -----

The export option for Vehicle Configuration Report has been disabled in FM2001

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000 FM2001 Report

1446
www.mixtelematics.com

1446
 1447
10.3.224 Knowledge Base Article 229

Article Number 229

Title Setting arming delay in Vehicle Configuration Group to less than 1 minute

Created 1/25/2001 11:41:59 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 1/25/2001 11:45:24 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000 Second Edition

----- SUMMARY -----

Difficulties in changing the default arming delay time to less that 1 minute.

----- MORE INFORMATION -----

When attempting to change the default arming delay in the Vehicle Configuration Group, it seems
that it is impossible to change this delay to anything less than 1 minute. When attempting to enter
30 seconds as the default arming delay, the arming delay jumps back to 10 minutes (or whatever
the previous default was set to be).

In other words, (the arming delay "mask" looks as follows: 00:10:00) when trying to change the 10 to
00 to remove "minutes" to enter 30 for the seconds, the arming delay changes to 00:10:00 again.

----- SOLUTION -----

The current workaround (to change the default arming delay to 30 seconds) is the following:

1. Change the minutes to anything between 0 and 10 (excluding these two number). (i.e. the arming
delay is now set to 00:02:00)

2. Enter 30 (or the amount of seconds you want the arming delay to be) for the seconds.(i.e. the
arming delay is now set to 00:02:30)

3. Now remove the minutes (replace it by 00). (i.e. the arming delay is now set to 00:00:30)

The arming delay will now be accepted. Update this to the vehicle unit.

----- STATUS -----

This is under investigation.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000

1447
www.mixtelematics.com

1447
 1448
10.3.225 Knowledge Base Article 230

Article Number 230

Title Pulse counter not accepted by software

Created 2/19/2001 12:41:47 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 2/19/2001 12:41:47 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, all versions

----- SUMMARY -----

When adding a new input parameter for F3 (pulse counter), but not as fuel consumption, fuel
consumption is displayed, and the units for the parameter discarded.

----- MORE INFORMATION -----

This is visible on the Activity timeline - where "Fuel Used" is given as an abnormal high value, and
Fuel Consumption is 0.00 Km/l. What should have been displayed is the value and units for the F3
parameter, as specified on the input and event configuration for the specific vehicle.

----- SOLUTION -----

Upgrade to the FM Kienzle Fleet Manager 2001 software.

----- STATUS -----

This has been fixed in the next release of the FM Kienzle Fleet Manager 2001 software.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2000 FM2001

1448
www.mixtelematics.com

1448
 1449
10.3.226 Knowledge Base Article 231

Article Number 231

Title Geo-fencing not recording

Created 3/2/2001 9:28:34 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:31:56 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2001, version 6.01.0000

----- SUMMARY -----

Geo-fencing is not recorded by the FM200 unit.

----- MORE INFORMATION -----

Geo-fencing is set up to record in a certain area - defining values for latitude and longitude as
described in the "How to do Geo-fencing with the FM200" document to be found on the FM2001 CD.
This event does not record, even though the event configuration has been uploaded to the unit.

----- CAUSE -----

This is caused by an error in the configuration dll file.

----- SOLUTION -----

Download the following file: FMCfg3.dll.

1. Ensure that none of the Fleet Manager components are running.

2. Copy this file to your Windows\System or WINNT\System32 folder. (Search for the location of the
current FMCfg3.dll, which must be replaced by the new one)

----- STATUS -----

The problem has been solved in the fix provided, and will be included in the next release of the Fleet
Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2001 GPS

1449
www.mixtelematics.com

1449
 1450
10.3.227 Knowledge Base Article 232

Article Number 232

Title KTCO modes not recorded correctly

Created 3/7/2001 2:01:28 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:30:52 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2001, version 6.01.0000

----- SUMMARY -----

The driver modes are not recorded correctly.

----- SOLUTION -----

Download the following file: KTCOFix.ecz.

and update the Event Configuration as follows:

1. Save the file to your Fleet Manager 2001 install directory (typically C:\Program Files\Fleet Manager
2001).

2. Ensure that none of the Fleet Manager components are running.

3. Run the FMAdministrator program from the Control Pannel

4. Select Load Event Configuration

5. Browse to where you saved the KTCOFix.ecz file, and select it.

6. Remember to update your vehicles with the new event configuration.

----- STATUS -----

This has been fixed, and will be included in the next release of the FM Kienzle Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2001 KTCO TCO

1450
www.mixtelematics.com

1450
 1451
10.3.228 Knowledge Base Article 233

Article Number 233

Title Contact can still change SR Status on an empty 'New Status' Combo

Created 4/10/2001 12:53:16 AM

Created By Graham Downs (GDC)

Last Modified 4/10/2001 12:53:16 AM

Last Modified By Graham Downs (GDC)

Details ----- APPLIES TO ----

· Data Pro Centre-Point, all versions

----- SUMMARY -----

If you want to change the status of a Service Request, and click "Submit" after selecting nothing on
the "New Status" combo box, the status of the request is changed to the first non-Closed Status in
the system.

----- MORE INFORMATION -----

When viewing the details of a Service Request, you may elect to change the status of that request.
If you do this, you are presented with a list of statuses. However, if none of the Contact Groups
that you belong to have permission to change a service request to any status, the "New Status"
combo box is empty. If, under these circumstances, you click the "Submit" button, the Service
Request's status is set to the first non-Closed Status in the system

----- CAUSE -----

This problem is caused by errors in the Centre-Point system.

----- SOLUTION -----

To workaround this problem, ensure that all contact groups in the system have permission to
change Service Requests to at least one status in the system.

----- STATUS -----

This is a known problem, and a fix is under investigation by Data Pro Development (Pty) Ltd.

------------------------------------------------------------------------------

KEYWORDS: CENTRE-POINT

1451
www.mixtelematics.com

1451
 1452
10.3.229 Knowledge Base Article 234

Article Number 234

Title Error when exporting large report

Created 5/10/2001 11:18:38 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 5/10/2001 1:07:11 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, all versions

· FM Kienzle Fleet Manager 2001, all versions

----- SUMMARY -----

An error message is received when trying to export a large report. This problem usually occurs when
trying to Export large Event Reports.

----- MORE INFORMATION -----

The error message received reads as follows:

The following error/s occurred whilst communicating with the server:

91

or

The following error/s occurred whilst communicating with the server:

3078

----- CAUSE -----

The number of records specified is too large for the Access database to handle. See SOLUTION for a
workaround.

----- SOLUTION -----

The best workaround is to export smaller amounts of data (by specifying shorter date ranges/less
detail etc).

For more information on the error received, you can read Microsoft Knowledge base article Q173006.

----- STATUS -----

This problem is beyond our control. Please use the suggested workaround as solution.

------------------------------------------------------------------------------

1452
www.mixtelematics.com

1452
 1453

KEYWORDS: FM200 FM200e FM2000 FM2001 Reports

1453
www.mixtelematics.com

1453
 1454
10.3.230 Knowledge Base Article 235

Article Number 235

Title Copy Vehicle Feature duplicates the unit phone number

Created 5/16/2001 9:54:46 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 5/16/2001 10:05:36 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2001, all versions

----- SUMMARY -----

The Copy Vehicle feature duplicates the unit phone number for the newly created vehicle.

----- MORE INFORMATION -----

This can lead to problems when attempting to download via GSM, as one of the vehicles does not
have the correct unit phone number.

----- SOLUTION -----

The current workaround is to either clear the number or replace the duplicated phone number from
the newly created vehicle with its own number.

To do this:

1. Go to the vehicle properties of the new vehicle (created by the Vehicle Copy feature)

2. On the Device tab, select the GSM device and edit it.

3. On the calibration tab of this device, edit the Unit Phone Number, and replace it with the new
vehicle's number or clear it by clicking the Clear command button.

----- STATUS -----

We are considering clearing the Unit Phone Number as default when copying a vehicle. This will be
included in a future version of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM2001 GSM

1454
www.mixtelematics.com

1454
 1455
10.3.231 Knowledge Base Article 236

Article Number 236

Title Data discrepancies in reports - FM2001

Created 5/23/2001 9:17:30 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:29:08 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2001

· FM Kienzle Fleet Manager 2001, SR1

----- SUMMARY -----

Data discrepancy problems has been reported for some of the reports in the FM Kienzle Fleet Manager
2001 and FM Kienzle Fleet Manager 2001 SR1 software. These problems mostly include incorrect
values displayed for Distance or Odometer values on the reports.

----- MORE INFORMATION -----

Specific problems reported include the following:

1. The Distance and Odometer values displayed on the Detailed Driver Trip and Monthly Driver Trip
Reports are incorrect. (In both cases the correct value is the value displayed on the report divided by 10,
i.e. Odo is displayed as 1234.0km, and should be 123.4km)

2. Data for the last day inclusive on the Driver Scoring Report is not displayed, in other words, when
requesting a Driver Scoring Report for one day, you get a message stating that there are no data in the
database for the selected period, even if there are data for the specified date.

3. When the Measurement Settings for the Fleet Manager software is set to Imperial, the distance on
the Driver Scoring Report is reported in kilometers instead of Miles.

4. There are duplicate trips with different odometer readings listed in the Vehicle Driving Errors Report (i.
e. more than one trip with the same Start and End times, but different Odometer readings.

5. When generating a FM Terminal Event Report for a specific vehicle for Last Year as time period, the
report is generated for All vehicles from the beginning of last year to date.

6. When the Measurement Settings for the Fleet Manager software is set to Imperial, the average and
maximum values for speed on the Measured Fuel Consumption Vehicle report (detail) is unusually
large.

7. When entering fuel data for a vehicle, and entering the same mileage twice (i.e. there is no distance
to calculate consumption), a fuel consumption figure is calculated on the Fuel Consumption Report
(Manually Entered) where in fact the consumption should be zero.

8. The value for harsh braking on the Detailed Vehicle Trip Report is not being converted from kmph/s

1455
www.mixtelematics.com

1455
 1456

(kilometres per hour per second) to mph/s (miles per hour per second) when the measurement settings
is changed from Metric to Imperial. In other words, where this value should have been 9.9mph/s, it is
reflected as 16mph/s, which is the correct kilometre value.

9. Instead of displaying event duration for events in a subtrip on the Vehicle Event Report, the duration
displayed is that of the sub-trip itself.

10. When requesting a Vehicle Fuel Consumption Report for any vehicle for a specific period (This
year), the report header reads Measured Fuel Consumption Driver Monthly Summary instead of Fuel
Consumption Vehicle Monthly Summary.

11. When doing a Detailed Vehicle Trip report (and measurement settings are set to U.S.), including
subtrip & event info for Events recording start/end odo readings, the value under the Odometer field
differs from that shown as the end/start odo recorded with the event.

12. Vehicle Configuration report: When measurement settings are set to US, mph calibration has 12
decimal places.

----- CAUSE -----

Incorrect calculations in the FMRpt.mde file installed with FM2001/FM2001SR1.

----- SOLUTION -----

Download version 6.40 of the FMRpt.mde file.

1. Unzip this file

2. Ensure that none of the Fleet Manager components or MSAccess is running (if you do not know how
to do this, restart your PC before copying the file to the correct location).

3. Copy the FMRpt.mde file to the Fleet Manager 2001 install directory (typically C:\Program Files\Fleet
Manager 2001).

4. Run the Fleet Manager software, and generate your reports.

----- STATUS -----

This has been fixed in the FMRpt.mde file supplied, and will be included the Fleet Manager 2001 SR2
software.

For more information on related problems in the FM Kienzle Fleet Manager 2000 software, go to the
http://www.mixtelematics.com website, and search for Reports on the Knowledge base (Support -
Search the knowledge base), or if you have login access in Centre-Point, view KBA#239 (Data
discrepancies in reports - FM2000).

------------------------------------------------------------------------------

KEYWORDS: FM200 FM2001 FM2001SR1 Reports FMRpt.mde

1456
www.mixtelematics.com

1456
 1457
10.3.232 Knowledge Base Article 237

Article Number 237

Title No data recorded with EDM on I1-I4

Created 5/29/2001 10:15:10 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:27:34 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager SR1, version 6.03.0000

----- SUMMARY -----

When connecting the EDM to any of the status input lines (I1-I4), no fuel is recorded.

----- MORE INFORMATION -----

The following problems are experienced with EDM connected to any of the status input lines (I1 - I4):

1. An error in measured fuel consumption stored procedure was causing a difference when comparing
the report and the graph.

2. No tachodata was recorded for speed, RPM and EDM when a FM Kienzle EDM 1404 is connected to
one of the status inputs (I1 – I4).

To download the FM Kienzle Service Information document describing this problem in conjunction with
setting up a GSM modem on F3, click: FM SI No 382019.

----- SOLUTION -----

1. Download and install the FM2001SR1 patch.

2. Download version 2.5.5.0 of the FM Dealer Utility, and upload the latest device drivers to the affected
vehicles' units.

----- STATUS -----

This has been fixed and will be included in the next release of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2001 EDM

1457
www.mixtelematics.com

1457
 1458
10.3.233 Knowledge Base Article 238

Article Number 238

Title What's new in Fleet Manager 100 version 2.50

Created 6/5/2001 4:13:26 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/5/2001 4:23:59 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 100, version 2.50

----- SUMMARY -----

Following is a list of what’s new in FM Kienzle Fleet Manager 100 version 2.50:

· Configuration: The vehicle configuration has been converted to be the same as that of FM100
version 1.20. This involves the recording of RPM-related events when the RPM line is not connected
to the FM100 unit.

· Tax Reports have been added to the Reporting menu.

· Driver Reporting Groups have been improved to enable groups for the Tax Reports.

· Driver Score Report/Graph can be sorted on Average Score.

· Support for EV100 plugs to be downloaded has been added. Please note that configuration of
Driver/Vehicle plugs for EV100 must be done using EV100 version 2.01 software.

· Single install set for all Operating Systems – It is no longer necessary to install an extra driver when
installing on Windows NT4.0 or Windows 2000.

· Previous problems experienced with the restoring of databases have been fixed.

------------------------------------------------------------------------------

KEYWORDS: FM100 EV100

1458
www.mixtelematics.com

1458
 1459
10.3.234 Knowledge Base Article 239

Article Number 239

Title Data discrepancies in reports - FM2000

Created 6/19/2001 3:17:54 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:26:18 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000, Second Edition

----- SUMMARY -----

Data discrepancy problems has been reported for some of the reports in the FM Kienzle Fleet
Manager 2000 Second Edition.

----- MORE INFORMATION -----

Specific problems reported include the following:

1. There are duplicate trips with different odometer readings listed in the Vehicle Driving Errors Report
(i.e. more than one trip with the same Start and End times, but different Odometer readings.

2. When entering fuel data for a vehicle, and entering the same mileage twice (i.e. there is no distance
to calculate consumption), a fuel consumption figure is calculated on the Fuel Consumption Report
(Manually Entered) where in fact the consumption should be zero.

3. The value for harsh braking on the Detailed Vehicle Trip Report is not being converted from kmph/s
(kilometres per hour per second) to mph/s (miles per hour per second) when the measurement
settings is changed from Metric to Imperial. In other words, where this value should have been 9.9mph/
s, it is reflected as 16mph/s, which is the correct kilometre value.

4. Instead of displaying event duration for events in a subtrip on the Vehicle Event Report, the duration
displayed is that of the sub-trip itself.

----- CAUSE -----

Incorrect calculations in the FMReports.mde file installed with FM2000SE.

----- SOLUTION -----

Download version 5.08 of the FMReports.mde file.

1. Unzip this file

2. Ensure that none of the Fleet Manager components or MSAccess is running (if you do not know how
to do this, restart your pc before copying the file to the correct location).

3. Copy the FMReports.mde file to the Fleet Manager 2000 install directory (typically C:\Program Files

1459
www.mixtelematics.com

1459
 1460

\Fleet Manager).

4. Run the Fleet Manager software, and generate your reports.

----- STATUS -----

This has been fixed in the FMReports.mde file supplied, and will be included the Fleet Manager 2001
SR2 software.

For more information on related problems in the FM Kienzle Fleet Manager 2001 software, go to the
http://www.mixtelematics.com website, and search for Reports on the Knowledge base (Support -
Search the knowledge base), or if you have login access in Centre-Point, view KBA#236 (Data
discrepancies in reports - FM2001).

------------------------------------------------------------------------------

KEYWORDS: FM200 FM2000 FM2000SE SE FM2001SR1 Reports FMReports.mde

1460
www.mixtelematics.com

1460
 1461
10.3.235 Knowledge Base Article 240

Article Number 240

Title Error 91 when uploading configuration to vehicle plug

Created 6/27/2001 11:31:52 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 9/7/2001 2:20:29 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2001, SR1 with patch

----- SUMMARY -----

An unexpected error 91 occurs when trying to upload the vehicle configuration from the software to a
vehicle plug, after installing the patch for the Fleet Manager 2001 SR1 software.

----- MORE INFORMATION -----

The error description reads as follows:

The following unexpected error/s occurred:

91 (0x0000005B): Object variable or With block variable not set occurred in EventMaint.
UploadFM200Events (Line 3120). The error has been logged.

----- CAUSE -----

This error occurs when the GSM device is connected to S1, and no telephone number has been
entered on the Calibration tab.

----- SOLUTION -----

The current workaround is to enter a phone number in the calibration tab of the GSM device
connected, to do this:

1. On the Vehicle Properties dialog

2. Go the Device tab

3. Select/Edit the GSM device

4. On the Calibration tab, enter (edit) the phone number

5. Apply the changes and upload the config now.

If you still receive the error after updating the GSM device, change some of the values on the
calibration tab of the vehicles GPS device, submit these changes, edit the calibration tab again to
contain the original values (or the values you want it to be), submit that and try uploading the
configuration to the plug again.

1461
www.mixtelematics.com

1461
 1462

To edit the GPS device calibration tab:

1. On the Vehicle Properties dialog

2. Go the Device tab

3. Select/Edit the GPS device

4. On the Calibration tab, edit some of the values

5. Apply the changes

6. On the Calibration tab, change the values back to what it was or what you actually want it to be

7. Apply these changes and upload the config now.

----- STATUS -----

This will be fixed in FM Kienzle Fleet Manager 2001 SR2.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200e FM2001 GSM

1462
www.mixtelematics.com

1462
 1463
10.3.236 Knowledge Base Article 241

Article Number 241

Title MSDE Installation

Created 6/27/2001 2:55:42 PM

Created By Trevor Richardson (MiX Telematics - Stellenbosch)

Last Modified 9/9/2003 2:46:42 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 2001, all versions

· FM Fleet Manager 2002, all versions

----- SUMMARY -----

This document describes the manual installation of MSDE. It also describes the process of installing
the MSDE when not installing it to the default partition/harddrive (C:\).

The installation of MSDE may take relatively long, depending on the specification of the pc being
installed on. When you cancel/end the installation before it has completed, you might have a problem
either uninstalling and/or reinstalling the MSDE.

----- MORE INFORMATION -----

The basic manual installation of MSDE:

1. Copy the contents (two files) of the MSDE directory on the FM2001 CD to a certain location on your
hard disk (say C:\temp\msde\*.*).

2. Go to the Dos commandline (Start -> Run -> command).

3. Browse to the directory where you have copied the contents of the MSDE directory. (cd c:\temp
\msde)

4. Now execute the following command line:

MSDEX86.exe -a -s -f1 "[path]unattend.iss"

where [path] represents the path where you copied the files to, in other words "C:\temp\msde\".

5. It might seem that your pc is hanging, but MSDE is actually installing. This process might take up to
half an hour - depending on system specifications.

If you do not want to install the MSDE on C:\MSSQL7 (currently the default path for installing MSDE),
it is necessary to edit the unattend.iss file and then continue with a manual installation as described
above.

To install into a different path than C:\MSSQL7, do the following:

1463
www.mixtelematics.com

1463
 1464

1. After completing step 1 of the Manual installation, edit the unattend.iss file - replace all "C:
\MSSQL7"-strings, with the drive letter or path you wish to install i.e. make it "D:\MSSQL7" etc.

2. Save this changed file

3. Continue with the manual installation as described from step 2 above.

------------------------------------------------------------------------------

KEYWORDS: FM2001 MSDE Installation

1464
www.mixtelematics.com

1464
 1465
10.3.237 Knowledge Base Article 242

Article Number 242

Title Running FM2001 with Microsoft SQL Server 2000

Created 7/13/2001 2:36:45 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/2/2001 11:06:53 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 2001, SR1 or later

----- SUMMARY -----

This document describes the installation and management of the FM Kienzle Fleet Manager 2001
software on a computer where Microsoft SQL Server 2000 is installed.

----- MORE INFORMATION -----

NOTE: for the purposes of this article, the Microsoft Data Engine (MSDE) installed by the Fleet
Manager installation set, is considered the same as Microsoft SQL Server 7

Database Connection

The following has been tested and found to be working fine:

1. Both the FM Client and Server has Microsoft SQL Server 7 installed.

2. Both the FM Client and Server has Microsoft SQL Server 2000 installed.

3. Microsoft SQL Server 7 is installed on the FM Server computer, and Microsoft SQL Server 2000 is
installed on the FM Client computer.

The only case where problems have been experienced is where the FM Server computer has
Microsoft SQL Server 2000 installed, and the computer where the FM Client components are installed
only has Microsoft SQL Server 7 installed.

Database Backups

The following has been tested and found to be working fine:

1. Backup taken from a Microsoft SQL Server 7 database can be restored into a Microsoft SQL Server
7 database or Microsoft SQL Server 2000 database.

2. Backup taken from a Microsoft SQL Server 2000 database can only be restored into a Microsoft
SQL Server 2000 database.

NOTE: A backup taken from a Microsoft SQL Server 2000 database cannot be restored into a
Microsoft SQL Server 7 database. The following error is raised from FMAdmin:

1465
www.mixtelematics.com

1465
 1466

The file structure of the backup database (FleetManager) is different to that of the target database.
This process cannot restore from this backup device.

----- SOLUTION -----

To solve the problem mentioned above, you will have to install at least the Microsoft SQL Server 2000
Client Tools on the FM Client computer.

For more information on Microsoft SQL Server licencing and installation, please consult the Microsoft
production information.

----- STATUS -----

The Fleet Manager system will be designed to operate on Microsoft SQL Server 7 or 2000. The Fleet
Manager system will continue to install MSDE when required, but the installation of the full product
Microsoft SQL Server is outside the scope of the Fleet Manager support.

------------------------------------------------------------------------------

KEYWORDS: FM2001 MSDE Client SQL Server Network

1466
www.mixtelematics.com

1466
 1467
10.3.238 Knowledge Base Article 243

Article Number 243

Title Error 3021 when no devices connected to F2

Created 9/10/2001 11:10:03 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 9/10/2001 11:11:17 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2001 SR2

----- SUMMARY -----

An unexptedted error 3021 occurs when no devices connected to F2.

----- MORE INFORMATION -----

When the device on the F2 frequence line (RPM or TCO RPM) is disconnected at vehicle level, the
following error message is displayed:

The following unexpected error/s occurred:

3021 (0x00000BCD): Either BOF or EOF is True, or the current record has been deleted. Requested
operation requires a current record. occurred in frmDevices.SaveProfileTab (Line 33310).

----- SOLUTION -----

After the error has occurred, click the OK command button to get rid of the error and continue editing
the devices list. This will not cause a problem in uploading the configuration or downloading data at a
later stage.

----- STATUS -----

This is a known problem, and will be fixed in the next release of the FM Kienzle Fleet Manager
software.

1467
www.mixtelematics.com

1467
 1468
10.3.239 Knowledge Base Article 244

Article Number 244

Title Error when uploading FM100 configuration

Created 9/11/2001 1:36:42 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 9/11/2001 2:14:48 PM

Last Modified By Jeremy Hartley (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2000 SE

· FM Kienzle Fleet Manager 2001 release, SR1, SR2

----- SUMMARY -----

When trying to upload a FM100 configuration to a FM100 vehicle plug, an error occurs. The error
message received is different from FM2000SE to FM2001.

----- MORE INFORMATION -----

The error message received for FM2000SE reads as follows:

The following unexpected error/s occurred:

30999 (0x00007917): Currupt Triggers!!! occurred in VehicleConfig.UploadFM100Data (Line 2460). The

error has been logged

The error message received for FM2001 (all versions mentioned above) reads as follows:

The following unexpected error/s occurred:

91 (0x0000005B): Object variable or With block variable not set occurred in EventMaint.UploadEvents
(Line 1300). The error has been logged.

----- CAUSE -----

The reason for the error(s) occurring is that some of the FM100 events are disconnected at vehicle group
level, and these cascades down to vehicle level, which is an invalid condition at vehicle level.

----- SOLUTION -----

The current workaround is to ensure that all of the following events are connected at either grouplevel as
well as vehicle level, or just to reconnect them at vehicle level:

1. Harsh braking

2. Idle - Excessive

3. Out of Green Band driving

1468
www.mixtelematics.com

1468
 1469

4. Over revving

To reconnect these values in FM2000SE:

A. On vehicle configuration group level:

* Go to the Vehicle Configuration Group's properties dialog

* Go to the Event Configuration tab

* Ensure that all four events mentioned previously in this KBA are checked

* Click Apply to submit these changes and check that the information is saved

B. On vehicle level

* Go to the Vehicle's properties dialog

* Go to the Event Configuration tab

* Ensure that all four events mentioned previously in this KBA are checked

* Click Apply to submit these changes and check that the information is saved

To reconnect these values in FM2001:

A. On vehicle configuration group level:

* Go to the Vehicle Configuration Group's properties dialog

* Go to the Events tab

* Ensure that all four events mentioned previously in this KBA are checked

* Click Apply to submit these changes and check that the information is saved

B. On vehicle level:

* Go to the Vehicle's properties dialog

* Go to the Events tab

* Ensure that all four events mentioned previously in this KBA are checked

* Click Apply to submit these changes and check that the information is saved

----- STATUS -----

This problem will be fixed in a future release of the Fleet Manager software. In the meantime, please use
the workaround suggested.

------------------------------------------------------------------------------

KEYWORDS: FM100 FM2000 FM2000SE FM2001 SR1 SR2

1469
www.mixtelematics.com

1469
 1470
10.3.240 Knowledge Base Article 245

Article Number 245

Title PreProcessFM200Data error while downloading in FM2001SR2

Created 10/2/2001 10:08:47 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/14/2002 4:18:37 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2001, SR2

· FMDealer, Version 2.7.0.0

----- SUMMARY -----

There is a problem in the D12 (FM200 Event Controller) device driver released with FM 2001 SR2. In
some cases, this device driver may result in invalid information being recorded by the FM200 unit.
Testing has revealed that this problem is likely to affect less than 2% of FM200 installations.

----- MORE INFORMATION -----

The error in the D12 device driver causes the FM200 unit to record duplicate block sequence numbers
which result in one of the following errors whilst downloading data into the database:

-2147217900 (80040E14): Violation of PRIMARY KEY constraint 'FM200RawEventsEx_PK'. Cannot

insert duplicate key in object 'FM200RawEventsEx'. occurred in PreProcessFM200Data.
ReceiveFM200Events (Line 6320).

Or

-2147217900 (80040E14): Event Mismatch - Start Seq 0, end Seq 272527000: Database (Event/
Action/Type) = -32460/5/130, New = 32050/1/131 occurred in PreProcessFM200Data.
ReceiveFM200Events (Line 6320).

The errors occur irrespective of the download method being used (code-plug, GSM or DECT).

PLEASE NOTE:

The above errors can occur when using older device drivers, but in such cases, are as a result of a
procedural error. Please go to the http://www.mixtelematics.com website and search the Knowledge
base for KBA 41 for more information.

If you are already experiencing one of the above errors, you must follow the steps documented in KBA
41 as well as upload the new device drivers to correct the problem.

----- CAUSE -----

The error in the D12 device driver causes the FM200 unit to record duplicate block sequence
numbers.

1470
www.mixtelematics.com

1470
 1471

----- SOLUTION -----

As a precaution, an updated FM Dealer installation set (version 2.7.1.0), incorporating an updated

D12 device driver (version 12.0.35), is being released. Please install this updated version of the FM
Dealer install set and use it to upload the latest device drivers to your FM200 units.

You can download and install either or both of the following latest install sets for FMDealer:

1. FM Dealer -stand alone.

2. FM Dealer -extension.

----- STATUS -----

The fix is already available with the latest FMDealer install set and will also be included in the next
release of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM2001 SR2 Plug Download

1471
www.mixtelematics.com

1471
 1472
10.3.241 Knowledge Base Article 246

Article Number 246

Title Incorrect start time on Event Report

Created 10/3/2001 9:19:05 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 10/4/2001 4:29:11 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Kienzle Fleet Manager 2001, all versions

----- SUMMARY -----

When doing a Vehicle Event Report or Driver Event Report, the start time, given at the summary of
the day's trip, is incorrect.

----- MORE INFORMATION -----

On the Vehicle/Driver Event Report, there is a section at the end of each day displaying a summary of
the day's events (first start, last end, total duration etc). On this section of the report - the start time
isn't always correct - sometimes it's the start time of an event that occurred later in the day, instead of
the start time for the first event in the day.

----- CAUSE -----

This is caused by an error in the FMRpt.mde file (version 6.43 and earlier) when the regional settings
are set to use a 12-hour clock. When you are using the 24-hour clock, this problem will not occur.

----- SOLUTION -----

The workaround for this problem is to set your Regional Time settings to use the 24-hour clock instead
of the 12-hour clock.

To do this:

1. Go to Start -> Settings -> Control Panel -> Regional Options/Regional Settings

2. Go to the Time tab

3. You will see that the Time format is as follows (or similar to): hh:mm:ss

4. Change the Time Format to contain "HH" instead of "hh" - in other words, your time format should
be set to: HH:mm:ss

----- STATUS -----

Please use the workaround supplied, as this has been fixed in version 6.44 and later of the FMRpt.
mde file, which will be included in the next release of the Fleet Manager software (FM2002).

1472
www.mixtelematics.com

1472
 1473

------------------------------------------------------------------------------

KEYWORDS: FM200 FM2001 Event Report

1473
www.mixtelematics.com

1473
 1474
10.3.242 Knowledge Base Article 247

Article Number 247

Title EDM Data not Recorded when Connected to Analogue Lines.

Created 11/5/2001 5:18:40 PM

Created By Bryan Jarmain (MiX Telematics - Stellenbosch)

Last Modified 11/5/2001 5:18:40 PM

Last Modified By Bryan Jarmain (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200

----- SUMMARY -----

EDM data is not recorded by the FM200 when connected to an analogue line.

----- MORE INFORMATION -----

Zero litres of Fuel get recorded when an EDM is connected to an analogue line on the FM200. Normally
an EDM is connected to F3, but has to be connected to an analogue line when a GPS is also being
used (a GPS can only be connected to F3).

----- CAUSE -----

The EDM has a very week (high) pullup impedance, which is "swamped" by the impedance of the
analogue input.

----- SOLUTION -----

The latest device driver set will ensure the impedance of I1 and I2 are sufficiently week so as not to
swamp the EDM signal. Alternatively, an additional external 10K resister between the EDM output and
its power supply will ensure the signal is not lost. This resister is especially suitable if the EDM is
connected to I3 or I4.

----- STATUS -----

This is fixed with latest device drivers and with the recomended resister fitted in the harness.

------------------------------------------------------------------------------

KEYWORDS: FM200

1474
www.mixtelematics.com

1474
 1475
10.3.243 Knowledge Base Article 248

Article Number 248

Title Calculation of Fuel Consumption in the FM software

Created 11/6/2001 11:30:06 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/6/2001 12:05:41 PM

Last Modified By Trevor Richardson (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2001, all versions

----- SUMMARY -----

The FM200 unit stores the number of pulses received from the EDM.

This article discusses the way fuel consumption is calculated in the FM software, using these pulses.

----- MORE INFORMATION -----

The FM200 stores the number of pulses received from the EDM at the start and end of a sub trip.

During the Processing of the download the pulse count per sub trip is then converted to Litres using the
calibration from the device configuration.

Detailed events can also have the number of pulses stored, which are also converted in the download
but not included in the trip data.

The FM200 does not store Fuel consumption, this is calculated at reporting time depending on the
client's measurement settings. The Sub trip consumption uses the sub trip distance value, events use
the difference in the Odometer readings.

All distances recorded by the FM200 are rounded down to 100m intervals. This does affect fuel
consumption calculations for short trips.

Fuel usage for periods between subtrips can be recorded by detailed events. If the recording is Detail,
the number of pulses, and hence litres, can be recorded. If the Vehicle does not move, i.e. Start Odo =
End Odo or distance = 0, consumption cannot be calculated.

----- STATUS -----

This functionality is by design

------------------------------------------------------------------------------

KEYWORDS: FM FM200 FUEL EDM

1475
www.mixtelematics.com

1475
 1476
10.3.244 Knowledge Base Article 249

Article Number 249

Title Unable to restore backed up database

Created 12/7/2001 4:08:45 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 12/7/2001 4:39:32 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2001, SR2

----- SUMMARY -----

An error occurs when trying to restore a backup of a database onto a (local) Server, and the restore
process is aborted.

----- MORE INFORMATION -----

The error message received reads as follows:

An unexpected error occurred:

Error -2147218350 - [Microsoft][ODBC SQL Server Driver][SQL Server]The backup set holds a backup
of a database other than the existing '[database name]' database.

[Microsoft][ODBC SQL Server Driver][SQL Server]Backup or restore operation terminating abnormally,

occurred in FMBackup.RestoreDB (Line 5760).

----- SOLUTION -----

As a workaround do the following create a new database on your local machine by referencing the
machine name as server instead of using (local), and restore the backup to this newly created
database:

To create the new database:

1. Open FMAdmin, and double click Connection

2. Enter your computer name as Server instead of using the default (local) as Server

3. Enter a new database name, to ensure that a new, empty database is created with a different name
to the one that you are restoring.

4. Click OK and continue creating your new database.

5. After the database has created successfully, you should be able to restore the backup to this
database without a problem.

----- STATUS -----

1476
www.mixtelematics.com

1476
 1477

This is under investigation.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM2001 Backup Restore SR2

1477
www.mixtelematics.com

1477
 1478
10.3.245 Knowledge Base Article 250

Article Number 250

Title ASP Script Errors in FMOnline

Created 12/12/2001 12:04:45 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 3/8/2002 9:33:38 AM

Last Modified By Adam Nachman (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Online

----- SUMMARY -----

It has been found that FMOnline experiences some ASP Script Errors in the Browser window on most
pages.

When trying to view the last downloaded vehicle's information or Activity Timeline, an unexpected error
occurs:

An unexpected error occurred:

94: Invalid use of Null

----- CAUSE -----

The table structures are correct for an FM2001SR2 database, but some of the stored procedures do not
appear to be correct.

----- SOLUTION -----

Upgrade the FM2001 database using the latest FMDB.zql file (this fix will be included in the next release
of the Fleet Manager software).

----- STATUS -----

This has been fixed, and the fix will be included in the next release of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FMOnline

1478
www.mixtelematics.com

1478
 1479
10.3.246 Knowledge Base Article 251

Article Number 251

Title Guide to Time synchronisation setup for GSM

Created 12/18/2001 12:48:06 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 1/7/2002 10:13:05 AM

Last Modified By Bryan Jarmain (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2001, SR2 and later

----- SUMMARY -----

Time jumping (time/date stored on FM200 unit unexpectedly becomes incorrect) on FM200 units with
GSM or DECT units installed.

----- MORE INFORMATION -----

The following guideline will reduce the risk of the time jumping on FM200 units with GSM installed:

1) Only allow GSM to synchronise time on vehicles without GPS. Units with GPS installed will keep
time synchronised more accurately than the GSM will be able to. Allowing the GSM to synchronise
time when a GPS is installed may result in occasional time jumps (which may later be fully/partially
corrected by the GPS).

2) Only specify the GSM to synchronise time once a month. The drift on an FM200 unit should not be
more than 30 seconds during this period.

3) Take all possible measures to ensure the time/date on the PC communicating with the GSM is
accurate.

4) Future refinements to the GSM front-end software will improve and automate the time
synchronisation process, reducing the risk of time jumps.

------------------------------------------------------------------------------

KEYWORDS: FM200 GSM GPS FM2001 time jumps synchronisation

1479
www.mixtelematics.com

1479
 1480
10.3.247 Knowledge Base Article 252

Article Number 252

Title Reports take very long to generate

Created 1/30/2002 3:51:31 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 1/31/2002 12:20:55 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2001 SR2

----- SUMMARY -----

In some cases (after upgrading from Fleet Manager 2001 SR1 to Fleet Manager 2001 SR2)it has been
reported that reports take up to 30 minutes to generate, regardless of the criteria selected. The rest of
the system functions without a problem.

----- CAUSE -----

This usually occurs after upgrading to Fleet Manager 2001 SR2 (from Fleet Manager 2001 SR1) where
MSOffice has been installed on the computer where this is occurring.

----- SOLUTION -----

A confirmed solution to this problem, is to rename the MSACCESS.exe file in the Office folder and then
reinstall the Access Runtime Module.

If you are using WindowsXP, an additional solution to the above, could be the following:

Right-click the applications' properties and choose the "compatibility" option, you can specify Windows
95, 98, NT 4 (Svc pack 5), or Win 2000.

Your reports should generate properly now.

----- STATUS -----

This is by design, not specific to the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM2001 SR2 Reports MSAccess

1480
www.mixtelematics.com

1480
 1481
10.3.248 Knowledge Base Article 253

Article Number 253

Title 42V Trucks and FM200 voltage

Created 2/22/2002 1:42:53 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 2/22/2002 2:35:37 PM

Last Modified By Bryan Jarmain (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 200

----- SUMMARY -----

Reports have been received concerning the connection of FM200 units to 42V trucks, as the 42 volt
supply from the trucks could be too excessive for the FM200 units.

----- MORE INFORMATION -----

These 42 volt vehicles have an OEM onboard voltage regulator (a 42 volt to 12 volt converter) which
can power up several products, so an aftermarket power supply shouldn't have to be installed.

Connecting directly to ignition (if the ignition input is 42 volts, and a 12 volt ignition input cannot be
found) will damage the FM200 if applied for too long, as this line is also used as a second voltage
supply to the FM200 (done to prevent a breakdown if in the event of the battery wire being
disconnected).

----- SOLUTION -----

An easy solution for the Ignition line is to use an inline resister of value 18K Ohms (to protect the
system against the 42V ignition voltages).

15K Ohm resisters should be used inline for analogue lines that can be connected to 42V. This will
allow accurate readings of up to 55V - instead of 38V (as is standard).

It should be noted that this (inline 15K ohm resister connection) should be done on all analogue lines
that are connected to possible 42V sources - even if accurate voltage readings are not required on
those lines; otherwise these excessive voltages will cause other analogue lines to be measured
inaccurately.

------------------------------------------------------------------------------

KEYWORDS: FM200 Voltage 42V Volts

1481
www.mixtelematics.com

1481
 1482
10.3.249 Knowledge Base Article 254

Article Number 254

Title Plug Downloads - ASP Errors

Created 3/8/2002 9:41:14 AM

Created By Adam Nachman (MiX Telematics - Stellenbosch)

Last Modified 11/14/2005 6:11:11 PM

Last Modified By Bülent Bas (Siemens FM Automotive - Switzerland)

Details
----- APPLIES TO ----

· Fleet Manager Online

----- SUMMARY -----

Script Errors on Vehicle and Driver plug downloads

----- MORE INFORMATION -----

When trying to download the vehicle configuration from the FM Online Web-based Administration
Function > Vehicle Configuration Plug, the following is experienced:

Error Type:

FMUpload3(0x8004C354): Automation error occurred in FM200Config.CreateVehiclePlug (Line 4500).

The error has been logged.

/fmonline/ConfigurationPlug.asp, line 39

When trying to download the vehicle configuration from the FM Online Web-based Administration
Function > Driver Disarm Plug, the following is experienced:

Error Type:

FMUpload3(0x8004C354): Automation error occurred in FM200Config.CreateDriverPlug (Line 8280).

The error has been logged.

/fmonline/DriverPlug.asp, line 39

----- CAUSE -----

The application cannot write the temporary files required to the hard drive in the security context in
which it is running.

----- SOLUTION -----

The NT account used by IIS (Internet Information Server), whether it is an anonymous account or
individual accounts (NT Integrated security) needs to have write access to the directory where the
FMUpld3.dll resides. This is usually the Fleet Manager 2001 directory, but in some instances could be
the Fleet manager Online directory.

1482
www.mixtelematics.com

1482
 1483

----- STATUS -----

This has been identified, and will be included in the documentation for Fleet Manager Online.

------------------------------------------------------------------------------

KEYWORDS: FMOnline

1483
www.mixtelematics.com

1483
 1484
10.3.250 Knowledge Base Article 255

Article Number 255

Title Why do I need to execute the Swap unit functionality

Created 3/11/2002 3:29:00 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 3/12/2002 7:17:04 PM

Last Modified By Bryan Jarmain (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 200

· FM Kienzle Fleet Manager 98, all versions

· FM Kienzle Fleet Manager 2000, all versions

· FM Fleet Manager 2001, all versions

· FM Fleet Manager 2002, all versions

----- SUMMARY -----

After clearing a FM200 unit's memory, it is necessary to execute the SWAP unit function in the related
software.

----- MORE INFORMATION -----

The FM200 stores events data with an event block sequence number. Event blocks are downloaded
into the database and these sequence numbers are used to key the data (time that the blocks were
generated cannot be used for this purpose as it is not guaranteed to be unique).

If you replace an FM200 (in a vehicle) with another one with the same vehicle ID, it is possible that its
block sequence numbers duplicate the previous units numbers. If this occurs, the downloader will raise
the 'corrupt Raw events' error, and leave the data download incomplete.

Data will then not be downloadable until the user has run the "Swap Unit Function" on the database.
This function closes all incomplete events and moves the data to unique events block sequence
numbers, allowing downloads to commence.

When wanting to clear the FM200 memory, one also needs to prevent incomplete events stored on the
database from causing errors. To do this, the swap unit function should also be run. This will close and
fix any incomplete events, preventing unnecessary download errors.

To execute the swap unit functionality, on the specific vehicle's properties, go to the Unit tab, and click
the Swap Unit command button.

To get more information on clearing the unit, please refer to KBA#41 (Fleet Manager Software
procedures for when a FM200(e) Unit is cleared).

------------------------------------------------------------------------------

1484
www.mixtelematics.com

1484
 1485

KEYWORDS: FM200 FM200e FM2000 FM2001 FM2002 Clear Memory Unit Swap

1485
www.mixtelematics.com

1485
 1486
10.3.251 Knowledge Base Article 256

Article Number 256

Title Time-synchronisation issues

Created 4/26/2002 12:59:58 PM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 4/26/2002 12:59:58 PM

Last Modified By Steve Crane (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2001, Fleet Manager 2002 and Fleet Manager Online

----- SUMMARY -----

In some instances time-sensitive functions may fail to work properly.

----- CAUSE -----

This is caused by differences in the times of computer clocks when running with components
distributed, including SQL Server, spread across different computers.

----- SOLUTION -----

This problem can be eliminated by implementing an automated time-synchronisation strategy so that

all computers running Fleet Manager server components and all computers using SQL Server or
MSDE to manage the Fleet Manager (and Fleet Manager Online) databases. This can be done using
the Windows NET TIME command, executing on a schedule. There are also numerous third-party time
synchronisation applications available that can perform this function.

----- STATUS -----

There are no plans to correct this in current versions of the products mentioned above, or in those
versions currently undergoing beta testing. Consideration will be given to implementing changes in
future versions to alleviate the problem.

------------------------------------------------------------------------------

KEYWORDS: FM2001 FM2002 FM Online FMOnline

1486
www.mixtelematics.com

1486
 1487
10.3.252 Knowledge Base Article 257

Article Number 257

Title Configuring Engine hours

Created 4/26/2002 4:17:32 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 5/2/2002 9:06:36 AM

Last Modified By Jeremy Hartley (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Fleet Manager 2002 Professional

----- SUMMARY -----

Incorrect (abnormally high or low) engine hour values are downloaded when Engine hours configured
on a vehicle, but not set in the unit.

----- MORE INFORMATION -----

After a vehicle has been configured to record engine hours, it is necessary to set the engine hours
using an Engine hours plug. If the engine hours is not set specifically, these incorrect engine hour
values will be displayed, as the value has not been specifically set in the unit. The FM Dealer can be
used to format an Engine hours plug.

----- STATUS -----

A message box will appear when checking the Engine hours check box on a vehicle's properties - this
checkbox serves as a reminder to set the engine hours of the vehicle, as is described above, and in
more detail in the documentation.

------------------------------------------------------------------------------

KEYWORDS: FM2002 Engine Hours

1487
www.mixtelematics.com

1487
 1488
10.3.253 Knowledge Base Article 258

Article Number 258

Title Problem with negative ID's

Created 6/3/2002 3:21:13 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/3/2002 4:39:48 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002

----- SUMMARY -----

Negative ID numbers cause problems in remote download/upload applications.

----- MORE INFORMATION -----

It is possible to use negative vehicle and/or driver ID's for Drivers and Vehicles in the Fleet Manager
2002 software. However these might cause problems when using the GSM Downloaded, SMS
Processor or DECT functionality.

----- SOLUTION -----

The current workaround is not to use negative vehicle or driver ID numbers.

----- STATUS -----

This is by design.

------------------------------------------------------------------------------

KEYWORDS: FM2002 GSM Downloader SMS Processor DECT

1488
www.mixtelematics.com

1488
 1489
10.3.254 Knowledge Base Article 259

Article Number 259

Title Tachometer / Speedometer / Rev Counter values not displayed correctly.

Created 6/6/2002 3:59:04 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/6/2002 5:00:39 PM

Last Modified By Bryan Jarmain (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 FM100

----- SUMMARY -----

Symptoms are:

The Speedometer / Rev Counter / automatic transmission systems / tacho-graphs on vehicle do not
work properly after the FM100/FM200 is installed. The FM unit still records data correctly.

----- MORE INFORMATION -----

Some speed and/or rev signals (less likely for rev signals) in some vehicles are very weak, and the
loading effects of the FM unit can sometimes cause this signal strength to be reduced to such an
extent that other equipment (using these signals) do not operate properly.

----- SOLUTION -----

The solution is to decrease the loading effect the FM200 has on the lines being affected.

When the speed signal is being effected, connect a 100 kilo ohm resister (this value almost always
solves the problem) in series (in line) with the speed signal line, as close to the FM unit as practical.
This resister will decrease the loading effect that the FM unit has on the signal.

The same applies to the RPM signal, if that is being affected (RPM).

If problems are still encountered (e.g. the FM unit cannot detect the signal), the value of the resister
can be decreased to make the FM unit more sensitive to the signal (decreasing will also load the line
more - decreasing the effect the 100K resister would have had on other devices). If the other
equipment still does not work properly, the resister value can be increased to load the line less.
(increasing will also make the FM unit less sensitive).

----- STATUS -----

The load that the FM unit places on the lines was chosen by design, and was kept relatively low (10
kilo ohms) to keep the signal noise level on the line low and to help improve the sensitivity of the FM
unit to the wide variety of signal types.

------------------------------------------------------------------------------

KEYWORDS: FM200, Tacho graph, Speed Signal, RPM Signal, revs, speed, drop off, gears

1489
www.mixtelematics.com

1489
 1490
10.3.255 Knowledge Base Article 260

Article Number 260

Title CallDMI error occurs in GSM Download

Created 6/6/2002 4:11:55 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/6/2002 4:45:38 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· GSMDl.exe version 6.05.0140

----- SUMMARY -----

In some cases a GSM download will fail with a CallDMI error for no specific reason.

----- MORE INFORMATION -----

The error message received usually reads as follows:

An unexpected error has occurred in CallDMI - 53 (35): File not found (Line 13095)

----- CAUSE -----

The install set for the GSM Downloader creates shortcuts incorrectly. The "Start In" parameter is
omitted, which causes the program directory to be wherever the the current directory was at the time
the program started.

----- SOLUTION -----

Correct the faulty shortcuts manually. To do this, go to Start->Programs->Startup-> [Right Click] GSM
Downloader link, and correct the Start in field to point to the same directory the GSMDl.exe file resides
in(typically "C:\Program Files\Fleet Manager 2001\").

----- STATUS -----

This has been corrected in the next version of the GSM Downloader to be released together with
FM2002.

------------------------------------------------------------------------------

KEYWORDS: GSM Downloader FM2001 SR2 CallDMI

1490
www.mixtelematics.com

1490
 1491
10.3.256 Knowledge Base Article 261

Article Number 261

Title Long calls to GSM modem connected to FM200

Created 6/6/2002 4:39:49 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/7/2002 9:37:42 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2001 SR2

· GSMDl.exe version 6.05.0140

----- SUMMARY -----

In some cases it has been found that unusually long calls are made to the FM200.

----- MORE INFORMATION -----

When a GSM modem connected to a FM200 unit has been set up to auto answer, the FM200 unit
does not detect this, and there could be long periods where the modem auto-answered a call and the
FM200 unit have not detected it, therefore no data are transferred to or from the modem.

The FM200 checks whether the modem is registered on the GSM network. If a DATA call is active
from the FM200 unit’s side, (and the unit does not detect this - auto answer is enabled), the FM200
will try to request the network registration status. This will fail, because the modem does not respond
to Commands in DATA call mode. Therefore the FM200 will reset the modem and terminate the call.

However, if an incoming voice call was received and automatically answered by the modem, the
modem stays in command mode. In this state the FM unit cannot detect the active call and the call
could stay open from the vehicle's side forever (remember this was an incoming call to the vehicle).

Another cause for long data calls could be that for some reason the Schedular application on the
computer was unable to close the call. An extended safety measure would be to set the modem to
automatically disconnect the call after a certain time when there was no communication on the line
(See the next section for more information on this).

----- SOLUTION -----

The current workaround for this includes to set the modem connected to your FM200 unit not to auto
answer, and to change the settings for the modem connected to your computer.

A. Modem connected to FM200

It is extremely important that the modem attached to the FM200 should not be configured to
automatically answer incoming calls. Refer to the modems operator manual in how to check and
disable this.

B. Modem connected to computer

1491
www.mixtelematics.com

1491
 1492

1. In Control Panel->Modem properties/Phone and Modem Options,

2. Go to the properties of a modem (such as Sportster Flash V.90 Voice PnP or other correctly
installed with it's specific driver - not the standard modem installed by Windows)

3. Go to this modem's Advanced properties, check the Disconnect a call if idle for more than [ ] mins,
and set the value for it.

----- STATUS -----

This is currently by design, but have been fixed in the release of the FM2002 set of device drivers.

------------------------------------------------------------------------------

KEYWORDS: GSM Downloader Modem FM200 Auto answer

1492
www.mixtelematics.com

1492
 1493
10.3.257 Knowledge Base Article 262

Article Number 262

Title Activity Timeline and Trip Report trip data and event data inconsistency

Created 6/11/2002 11:26:21 AM

Created By Adam Nachman (MiX Telematics - Stellenbosch)

Last Modified 6/12/2002 10:14:50 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager, All versions

----- SUMMARY -----

Events show for a driver when there is no trip.

Trip shows for a driver but there are no events.

----- MORE INFORMATION -----

When a the driver for a selected trip is changed via the 'Trip Information' option in the 'View' menu of
the Activity Timeline and the Activity Timeline is refreshed for the origional driver for that trip, no data
is displayed in the trip bar for the Activity Timeline, while the events are still reported.

The converse applies when the same Activity Timeline report is generated for the new driver - there is
Trip Data in the trip bar, but no events are reported.

This behaviour is also reflected in the Trip Reports.

----- CAUSE -----

This is caused by changing the driver for a trip from the Vehicle Activity Timeline. Although the trip is
now modified to reflect the driver change, the event data is not.

----- STATUS -----

Unfortunately there is currently no solution to this, but it will be reviewed and fixed in a future release
of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM2000 FM2001 FM2002 Driver Trip Report

1493
www.mixtelematics.com

1493
 1494
10.3.258 Knowledge Base Article 263

Article Number 263

Title Changing sim card causes ID verification to fail first time around, Using no PIN

Created 6/11/2002 1:16:25 PM

Created By Wesley De La Harpe (MiX Telematics - Stellenbosch)

Last Modified 8/2/2002 11:36:04 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· GSM Downloader FM_Comms

· FM200

· Fleet Manager 2001 SR2

· Fleet Manager 2002

----- SUMMARY -----

The FM200 checks the network registration status of the SIM card on the network. If the modem is reset
while the FM200 thiks it is still allive then the FM200 would not detect the incorrect modem configuration
(factory defaults).

----- MORE INFORMATION -----

When the SIM card is changed in the vehicle unit, the first time the vehicle is dialed, the vehicle ID
verification process fails (times out). The second and subsequent times the vehicle is dialed it works
fine.

----- CAUSE -----

Any incomming call would be detected and the FM200 will answer it. Due to the fact that the modem
was not properly reset, the now active data channel was set up incorrectly. From the PC side,
FM_Comms would time out while requesting the general info from the vehicle. (i.e. the first time the call
will fail) Due to the prolonged open data channel, the FM200 would detect that the active call was
dropped, this would then result in the FM200, resetting the modem state machine and thus re-initialising
it.

----- SOLUTION -----

A fix for replacing the SIM on the fly, would be:

1. to reset the FM200 after the new sim was inserted.

2. Enable the SIM pin code.

----- STATUS -----

As the swapping of sim cards is not a regular occurence, and due to the fact that it does not occur on

1494
www.mixtelematics.com

1494
 1495

the next retry, no plans have been made as yet for a permanent fix.

------------------------------------------------------------------------------

KEYWORDS: GSM Downloader FM_Comms FM200 FM2001 SR2 FM2002 FM200

1495
www.mixtelematics.com

1495
 1496
10.3.259 Knowledge Base Article 264

Article Number 264

Title How to recover a TrailerID's lost ID

Created 6/13/2002 9:10:17 AM

Created By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Last Modified 1/12/2007 10:54:45 AM

Last Modified By Warren Tieling (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· TrailerID System

----- SUMMARY -----

TrailerID unit has lost it's sticker.

----- MORE INFORMATION -----

Because a TrailerID unit is usually mounted in a harsh enviornment (outside of a trailer), it's sticker
may become unreadable or even peal off. To recover it's ID, follow this procedure.

----- SOLUTION -----

Whilst a more permanent solution is being investigated, please follow this work-around:

Assumed: (1) You have a working FM200 installed in a Horse(truck). (2) You have the TrailerID
installed in a Trailer.

(a) First Connect the trailer to the horse.

(b) Disconnect the trailer from the horse and leave it disconnected for three minutes.

(c) Now, do a data download from the vehicle and open the activity timeline.

(d) You should see a message saying that a trailer (A,B,C or D) ended with some maximum value.
(Typically "16777xxxx")

(e) Open your Windows Calculator and type in this decimal number.

(f) Click on the "+/-" function to make the number negative. (i.e. "-16777xxxx")

(g) Convert it to Hexadecimal.

(h) It should now look something like: "F6xxxxxx" where the TrailerID = xxxxxx. For example:
"F6000159" means the TrailerID = "000159".

(i) Try to record this number somwhere safe.

----- STATUS -----

1496
www.mixtelematics.com

1496
 1497

More premanent solution on wish list.

------------------------------------------------------------------------------

KEYWORDS: FM200 TrailerID Trailer Sticker

1497
www.mixtelematics.com

1497
 1498
10.3.260 Knowledge Base Article 265

Article Number 265

Title Invalid property error while adding event

Created 7/8/2002 3:56:53 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 3/13/2003 12:01:49 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2001

· Fleet Manager 2002

· Microsoft SQL Server 2000

----- SUMMARY -----

An error occurs when trying to add an event in the Fleet Manager software if you have Microsoft SQL
Server 2000 installed.

----- MORE INFORMATION -----

The error reads as follows:

Invalid property value occurred in frmEventDefinition.LoadProperties (Line 4490)

(The line number may differ depending on the version of software installed).

This error is specific to computers where Microsoft SQL Server 2000 has been installed.

----- CAUSE -----

This is caused by a SQL 2000 function not performing as expected, but has been corrected in SP1 (or
later) of Microsoft SQL Server 2000.

To determine the version of the SQL Server 2000 Service Pack you have install, refer to the following
Microsoft Knowledge base article:

321185 - HOW TO: Identify Your SQL Server Service Pack Version and Edition

----- SOLUTION -----

To solve this problem, get the Microsoft SQL Server 2000 Service Pack 1 or later from either your local
Microsoft SQL Server dealer or the www.microsoft.com website, and update your system.

----- STATUS -----

This problem is beyond our control, and is fixed with the Microsoft SQL Server 2000 Service Pack 1 or
later update.

1498
www.mixtelematics.com

1498
 1499

------------------------------------------------------------------------------

KEYWORDS: SQL 2000 Fleet Manager

1499
www.mixtelematics.com

1499
 1500
10.3.261 Knowledge Base Article 266

Article Number 266

Title When changing from FMOnline mode the FM Client needs to be restarted

Created 7/11/2002 9:16:11 AM

Created By Adam Nachman (MiX Telematics - Stellenbosch)

Last Modified 7/11/2002 9:17:10 AM

Last Modified By Adam Nachman (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Kienzle Fleet Manager 2001, all versions

· FM Kienzle Fleet Manager 2002 ver 7.0.0

----- SUMMARY -----

The Fleet Manager Client returns an error when selecting an organisation in FM Online mode.

----- MORE INFORMATION -----

If the user (or Administrator) changes the database from an FMOnline database to a FM2002 database
using the FMAdmin.exe after opening the Fleet Manager Client, clicking on File > Select Organisation
results in the following unexpected error being displayed:

91 (0x00000058): Object variable or With block variable not set occurred in frmFMOnlineDGB.ShowForm
(line340)

----- CAUSE -----

The Fleet Manager Client has been set into an Online state. This provides slightly different functionality
in some menus. Changing the database connection makes these functions invalid, resulting in the error.

----- SOLUTION -----

1. Close and restart the Fleet Manager Client to allow it to detect the database environment on startup.

2. Ensure that the database environment is not modified while the client is connected in Online Mode.

----- STATUS -----

This is being investigated for correction in a future release of Fleet Manager

------------------------------------------------------------------------------

KEYWORDS: FM2002 FMCLIENT FMONLINE

1500
www.mixtelematics.com

1500
 1501
10.3.262 Knowledge Base Article 267

Article Number 267

Title GPS Log Viewer buttons and menus are disabled

Created 7/11/2002 9:27:46 AM

Created By Adam Nachman (MiX Telematics - Stellenbosch)

Last Modified 7/11/2002 9:30:20 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002

· GPS Log Viewer 7.0 and later

----- SUMMARY -----

Pressing escape disables menus and buttons for the GPS Log Viewer (all regions).

----- MORE INFORMATION -----

Pressing escape actually prevents the GPS Log Viewer from loading the rest of the map layers. This is
a design feature to allow users to cancel their latest command, thus preventing slow refresh with many
layers loaded.

----- CAUSE -----

This behaviour only occurs if the user presses escape while the map layers are loading. This is not
duplicated anywhere else.

----- SOLUTION -----

Simply right-click on the map window and drag the map little, or shift and click to zoom out. This will
reload the map and enable to menus.

----- STATUS -----

This is being investigated for correction in a later release of the GPS Log Viewers

------------------------------------------------------------------------------

KEYWORDS: FM2002 GPSLOGVIEWER GPSVIEWER

1501
www.mixtelematics.com

1501
 1502
10.3.263 Knowledge Base Article 268

Article Number 268

Title Timeline Reports prints incorrectly

Created 7/16/2002 10:05:04 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 7/16/2002 10:15:08 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Fleet Manager 2001

· FM Fleet Manager 2002

· Timeline Reports extension (FMTimelineEX.dll version 2.0.0.35)

· Crystal Reports 8.0

----- SUMMARY -----

When viewing a Timeline report generated by the Timeline Reports extension, the report seems to be
fine, but when printing it, it could happen that the wrong graph is matched to the wrong data.

----- MORE INFORMATION -----

This happens intermittently, and the displayed graph is usually the graph viewed in the preview before
printing - it seems that the same graph is used on each page of the report, regardless of the printed
data matched to a different graph in the preview.

----- CAUSE -----

The cause of this have been found to be a confirmed problem in the Crystal Reports 8.0 used for the
Timeline Reports Extension.

----- SOLUTION -----

There is a workaround to this problem however:

To print the Activity Timeline report - generate it, and before browsing/previewing different pages -
print the report (by clicking the printer icon, or using the File-Print menu command).

----- STATUS -----

This problem is beyond our control, but will be investigated in future as improved versions of Crystal
Reports are made available.

------------------------------------------------------------------------------

KEYWORDS: Timeline Report Extension Crystal

1502
www.mixtelematics.com

1502
 1503
10.3.264 Knowledge Base Article 269

Article Number 269

Title TCO diagnostics

Created 7/16/2002 11:48:51 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 7/16/2002 11:55:27 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 unit

· FM Dealer

----- SUMMARY -----

This article describes how you can ensure that the FM200 is reading the TCO unit correctly.

----- MORE INFORMATION -----

To ensure that the FM200 is correctly reading the TCO unit, you must prepare a Speed Diagnostic
plug (by using the FMDealer) and insert it into the FM200. You should see the LED flashing rapidly
and hear the FM200 give short beeps every half-second (i.e. two beeps per second). This means that
the communication between the TCO and the FM200 is working.

Please Note: Before you insert the Speed Diagnostic plug, make sure that:

1) The vehicle ignition is turned on.

2) The switch for Driver 1 is in Active Work Mode (on the TCO).

To make a Speed Diagnostic plug with the FMDealer do the following:

1) Use a 128 byte plug (for example, a blue driver plug).

2) In the FMDealer, click on Code Plug->Format Plug->Calibration Plug->Speed, and click OK.

3) Now click on Code Plug->Calibrate Plug->Diagnostic.

Your plug is now ready to use on the FM200.

------------------------------------------------------------------------------

KEYWORDS: FM Dealer TCO

1503
www.mixtelematics.com

1503
 1504
10.3.265 Knowledge Base Article 270

Article Number 270

Title Things to take into account when connecting speed line

Created 7/25/2002 3:50:21 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 7/26/2002 9:20:53 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 unit

----- SUMMARY -----

It has been reported that in some cases a speed value is recorded as soon as a vehicle is started,
even though the vehicle is not moving. This may well result in some events (such as Harsh
Acceleration, Harsh Braking and Out of Green Band Driving) being recorded incorrectly.

----- CAUSE -----

If your vehicle is exhibiting this problem, it is probably caused by noise on the speed line. There are a
number of possibilities why there could be noise on the line:

• battery line voltage fluctuating

• poor ground wiring in the vehicle

• Signal converters (SDLs) can also sometimes be responsible for such noise (is has been found that
when using a SDL (Serial Data Link) to provide the speed and or RPM, there could be a problem with
the validity of the recorded speed data)

----- SOLUTION -----

Most of this noise can be eliminated by using a 100K ohm resister in series with this line (a 10 K okm,
3K ohm or 2 K ohm resister will usually be too small), connecting it as close as practically possible to
the FM200. If this doesn’t work, you should use an oscilloscope to measure the speed line while
idling and note the signal voltage ripple (peek to peek voltage). To keep compatible with the widest
possible range of signal types, the FM200 will record ripple voltages of 0.5V and higher. If you have
an excessive ripple voltage, you should find a better place to pick up the signal from, or eliminate
other problems such as a faulty SDL, poor grounds etc. until the noise is sufficiently eliminated.

More info when using SDL

Regarding problems experienced with the SDL measuring speed signals, the ONLY solution is to pick
up the speed signal directly off the speedometer sender.

Using a Serial Data Link will work OK on some model trucks, poorly in others, and not at all on some.
Even when it seems like the speed signal is working OK, you will run into problems with Harsh
Acceleration and Harsh Braking reports. Other times, you will only get a speed signal when the
vehicle is doing 10km/h or more. This is a limitation of the information being outputted from the trucks

1504
www.mixtelematics.com

1504
 1505

data bus. It is not a limitation of the SDL. The problem is that each manufacturer interprets the J1708
Data Standard differently, and then implements it in their software differently as well.

Whenever an SDL is installed, the speed signal is (should) ALWAYS (be) sourced separately.

The only solution is to pick up a true hard wired speed signal from either the speed sender, back of
the speedo, ECU or another suitable place. If you are unsure, ask the manufacturer. This is the
ONLY way to guarantee that you will have a reliable speed signal and that all reports your customer
needs will be accurate and true with every installation.

The speed signal on the J1708 data bus is mathematically calculated by the vehicles ECU. The
vehicles computer uses several parameters such as tyre diameter, diff ratio etc to work out the
speed.

Due to legal implications with the reporting of true vehicle speed in many markets, other products that
have built in SDL's also have separate speed signal inputs so that a true speed signal can be
connected to the Fleet Management Computer, and a custom calibration can be performed.

(It is important to consider the legal implications in your market, especially on fuel tankers if you are
picking up a computer generated speed signal rather than a true speed signal).

(We want to thank George Stavrinou from SiemensFM Australia for information supplied on the SDL
regarding this issue).

------------------------------------------------------------------------------

KEYWORDS: FM200 SDL Speed Noise

1505
www.mixtelematics.com

1505
 1506
10.3.266 Knowledge Base Article 271

Article Number 271

Title How to enable Autopoll backups

Created 8/6/2002 11:02:58 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 9/18/2002 1:00:02 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Autopoll Client

----- SUMMARY -----

This article describes how to make Autopoll backups.

The Autopoll Backup functions as follows: when the file is Transferred to the database, a copy of the *.
INI, *.DAT and *.TDT files are made using the AUTOPOLL BACKUPS folder as the root. If multiple
paths are autopolled (i.e. for GSM, DECT, other PCs etc), all the files will be copied into one root on the
PC where FMAPC is running (i.e. combine all DATs into one folder structure).

----- MORE INFORMATION -----

To enable Autopoll backups, simply add the following key to the Windows Registry by downloading the
following file (ActivateAPCBackup.reg), save and execute it (when prompted to add this to your
Registry, click yes/ok).

This will add the appropriate key to your registry, and enable your Autopoll backups.

This registry entry is checked only when the FMAPC starts (NOT the Start/Stop button on the form). In
order to get the backups started, the program must be Exited and then re-started.

------------------------------------------------------------------------------

KEYWORDS: Autopoll Backup

1506
www.mixtelematics.com

1506
 1507
10.3.267 Knowledge Base Article 272

Article Number 272

Title Detailed Trip report hangs for large scope of data

Created 8/21/2002 2:39:05 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/7/2002 9:00:21 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Fleet Manager 2002, version 7.00.0000

----- SUMMARY -----

When trying to generate a Detailed Vehicle Trip report for a large scope of data, the report seems to
hang.

----- MORE INFORMATION -----

When generating the report for smaller amounts of data, it doesn't seem to have a problem.
Generating any other form of the report (Daily, Monthly or Summary) works fine.

The report doesn't give an error, not even if you have the ShowAccess key set, it just seems to hang
when the report criteria includes either a large number of Vehicles, or large time period.

----- CAUSE -----

This caused by a change made to the FMRpt.mde file.

----- SOLUTION -----

Download the latest version of the FMRpt.mde file, and restore it to your computer as follows:

1. Download and save, then extract the FMRpt.zip file to a location on your hard driver other than the
Fleet Manager install directory.

2. Restart your computer to ensure that none of the Fleet Manager or reporting components are
running.

3. Copy this file to your Fleet Manager install directory (typically C:\Program Files\Fleet Manager 2002
).Your reports should generate fine by now.

----- STATUS -----

This has been fixed in the latest version of the FMRpt.mde file available, and will be included in the
Fleet Manager 2002 Service Release 1.

------------------------------------------------------------------------------

KEYWORDS: Report FM2002 Trip

1507
www.mixtelematics.com

1507
 1508
10.3.268 Knowledge Base Article 273

Article Number 273

Title How to import Location data

Created 8/22/2002 9:43:48 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/22/2002 9:50:16 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002

· Fleet Manager System Tools 1 Extension

----- SUMMARY -----

Importing Location data can be done with the Fleet Manager System Tools 1 Extension.

----- MORE INFORMATION -----

An updated version of the FM System Tools 1 Extension document can be downloaded from here or
the www.cidev.com website.

This updated document includes a section, describing the procedure to import location data.

------------------------------------------------------------------------------

KEYWORDS: FM2002 Location Report System Tools

1508
www.mixtelematics.com

1508
 1509
10.3.269 Knowledge Base Article 274

Article Number 274

Title FM2002 initialised driver plug does not disarm FM unit

Created 8/26/2002 4:58:36 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/27/2002 9:44:19 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM100 units

· FM200 units

· Fleet Manager 2001, all versions

· Fleet Manager 2002, version 7.00.0000

----- SUMMARY -----

When a driver plug has been initialised in the above-mentioned software versions, the driver plug will
not always disarm a certain vehicle, even though the vehicle is part of the collection of Allowed vehicles
for that specific driver.

----- MORE INFORMATION -----

When the driver plug is inserted into the vehicle socket, the unit beeps twice, but does not disarm (and
the LED continues flashing).

----- CAUSE -----

This is caused by an driver initialisation problem in the software.

----- SOLUTION -----

This will be fixed in the next release of the Fleet Manager software, but in the meantime you can use the
following workaround:

1. Insert the driver plug into the Download Module attached to the computer

2. In your FleetManager software, select the driver you would like to allow access a certain vehicle, and
open the Driver properties (by double clicking on the driver name, or right click, and select properties).

3. On the Driver Properties, go to the Vehicle Access tab

4. Ensure that the correct vehicle(s) are in the selection of Allowed vehicles. Now also CHECK the Allow
driver access to new vehicles that are added to the system checkbox.

5. When prompted to update the driver plug with this information, click Yes.

1509
www.mixtelematics.com

1509
 1510

This updated driver plug should now disarm the FM100 unit in question.

For the above workaround, including screenshots as a guideline, please download the following
document: DriverAccess.doc.

----- STATUS -----

This problem will be solved in the next version of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM2001 FM2002 FM100 FM200 Driver Access

1510
www.mixtelematics.com

1510
 1511
10.3.270 Knowledge Base Article 275

Article Number 275

Trailer ID extension strings displays in English if Spanish is selected as preferred

Title
language

Created 8/28/2002 2:55:44 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/28/2002 3:27:33 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002, version 7.00.0000

· FM Trailer ID Extension (TrailerIDExt.dll version 7.00.0000)

----- SUMMARY -----

When selecting Spanish as language for the Fleet Manager software, the Trailer ID extension's strings
are still displayed in English.

----- MORE INFORMATION -----

When selecting Spanish as the language in the Fleet Manager Options' Language tab, the Trailer ID
extension's strings are still displayed in English, and not in Spanish as it should be. When selecting the
Espanol (Chile), the Trailer ID displays the correct Spanish language strings.

----- CAUSE -----

The Spanish language file (FMTRLRIDEspanol.lng) for the Trailer ID is corrupt, and causes the Trailer
ID extension to use the English language file.

----- SOLUTION -----

This has been corrected in a new Spanish language file for the Trailer ID extension.

Click here to download the corrected file. Replace your currently corrupted FMTRLRIDEspanol.lng with
this file.

To do this, close your Fleet Manager software, and copy this file to the location on your computer
where the previous FMTRLRIDEspanol.lng was located (this should be your Fleet Manager install
directory, typically C:\Program Files\Fleet Manager 2002\).

----- STATUS -----

The fix is available from this KBA, and will be included in the next release of the Fleet Manager
software.

------------------------------------------------------------------------------

KEYWORDS: FM Trailer ID Extension Language strings Spanish

1511
www.mixtelematics.com

1511
 1512
10.3.271 Knowledge Base Article 276

Article Number 276

Title Mutliplug aborts in FM2002 Client

Created 10/2/2002 3:24:47 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 10/2/2002 5:11:20 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002, version 7.00.0000

----- SUMMARY -----

When trying to do a manual download (quick or full in the Fleet Manager 2002 Client) from a valid
Multiplug with or without data on it, no data is downloaded, and the download aborts.

----- MORE INFORMATION -----

When attempting the download manually, the data processing seems to start, but this changes to a
"Download aborted" message being displayed in the download data dialog box.

No data has been downloaded, nor has the multiplug been reset to ID 0.

----- CAUSE -----

This is due to an issue in the Fleet Manager Client. Please note that it only affects the FM Client,
and not the Fleet Manager Autopoll Client.

----- SOLUTION -----

The current workaround is to use the Autopoll functionality to download the data from the Multiplug
into the database. (You can either set Autopoll Client to do a quick or full download).

----- STATUS -----

This will be fixed in the Fleet Manager 2002 Service Release 1 version of this software. Use the
workaround described above as a solution for the current version (FM2002 release version) of the
software.

------------------------------------------------------------------------------

KEYWORDS: Multiplug FM2002 Download Aborted

1512
www.mixtelematics.com

1512
 1513
10.3.272 Knowledge Base Article 277

Article Number 277

Title FM200 loses its Calibration, Odometer, or Vehicle ID

Created 10/2/2002 3:34:13 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 4/29/2003 12:43:00 PM

Last Modified By Bryan Jarmain (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Fleet Manager 200

· FM Dealer Version 2.8.4.0 (Shipped with the Fleet Manager Office July 2002 release)

· Device Driver 2.0.19 (“(C)C.I.2002:FM200 S1&Splitter Data RX/TX (2.0.19)”)

----- SUMMARY -----

A small number of FM200 units will seem to lose some setting (calibration, vehicle ID, and odometer)
when running the device driver set shipped with the Fleet Manager Office July 2002 release. This
occurs when nothing is connected to the serial port of the FM200 and when a multi-plug is being
used. There is also a small chance that the symptoms will occur when a standard vehicle plug is
being used.

----- MORE INFORMATION -----

If the problem occurs, one or more of the following symptoms may be noted:

When data is downloaded via a plug (especially a Multi-Plug) the data downloaded will not appear in
the database or the data will not indicate speed and RPM, and the Odometer will not indicate
distance.

A vehicle plug will cause the unit either to emit a long beep when inserted, or to emit a quick beep,
flash quickly for a short period of time, and then resume its normal slow flashing (flash once every 2
seconds). Reloading the vehicle ID will usually temporarily fix the problem, and data downloaded may
appear to be correct for a period of time until the problem occurs again.

Resetting the unit, or reloading device drivers will accentuate the symptoms of the problem if the unit
has already been affected, and cause the unit also to appear to loose its calibration and odometer.

The chances of this occurring are considerably reduced (virtually to null) when an RS232 device is
plugged into the serial port (e.g. an FM Splitter, TTL Converter, an FM Terminal).

----- CAUSE -----

A bug in the FM200 firmware that manages the serial port causes memory corruption of the stored
values for the above mentioned settings on a small percentage of FM200 units.

----- SOLUTION -----

1513
www.mixtelematics.com

1513
 1514

The solution is to update the FM200 units with the latest available device drivers, to do this:

1. Download the latest FM Dealer from the http://www.mixtelematics.com website and install it.

2. Reload the device drivers to all affected vehicles using vehicle plugs or a Device Driver Plug
(especially vehicles exhibiting the symptoms).

3. Reset the Vehicle ID to its correct value and recalibrate the vehicle Speed and RPM using the
values extracted from the Front-End software (select the Properties for the vehicle by double-clicking
it (the vehicle), select the Device Tab, select the RPM signal or Speed Sender Device, and select the
Calibration tab).

----- STATUS -----

The problem has been solved in Versions 2.9.20.0 or later of the FM Dealer Software (Device Driver
2.0.20 - “(C)C.I.2002:FM200 S1&Splitter Data RX/TX (2.0.20)”).

------------------------------------------------------------------------------

FM200 FM200e

1514
www.mixtelematics.com

1514
 1515
10.3.273 Knowledge Base Article 278

Article Number 278

Title Recommended GPS installation

Created 10/3/2002 3:13:37 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 10/3/2002 4:10:54 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 unit

· GPS Module

----- SUMMARY -----

This Knowledge Base Article summarises the best way to install a GPS module, in order for it to
function most effectively when used in combination with the FM200 unit.

----- MORE INFORMATION -----

The recommended way of installing a GPS module with the FM200 unit, is to connect it via the
ignition or through a relay. It is not advisable to connect the GPS module directly to the battery: if
the COMMS of the GPS module should malfunction, it could cause the FM200 to hang (if the GPS
Module is connected directly to the battery). The risk of this happening, is largely reduced, if the
GPS module has been installed as recommended below.

Please download and view the following document: FM200 - GPS Interface.doc

This document describes the recommended way of connecting a GPS module to the FM200 unit to
ensure optimum performance.

------------------------------------------------------------------------------

KEYWORDS: FM200 GPS Unit Hangs

1515
www.mixtelematics.com

1515
 1516
10.3.274 Knowledge Base Article 279

Article Number 279

Title Not able to connect more than one FM200e device at a time

Created 10/4/2002 9:47:00 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 10/4/2002 11:08:02 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002, release version 7.00.0000

· FM EMI (FM Engine Management Interface)

----- SUMMARY -----

It is not possible to connect more than one FM200e device at any level (organisation, configuration
group, or vehicle level) at one time.

----- MORE INFORMATION -----

The first FM200e device connects to the appropriate line without a problem, but as soon as an
attempt it made to connect a second FM200e device, the FM200e device initially connected gets
disconnected, and only the "second" FM200e device appears to be connected.

----- CAUSE -----

This is caused by a problem in the way the FM200e devices are set up in the database.

----- SOLUTION -----

Download and install the following patch as described below:

1. Check that the database does in fact exhibit the problem (using FMClient)

2. Download FM2002-Patch1.zip.

3. Ensure that all clients (including Autopoll, GSM, DECT, etc) are shutdown.

4. Extract the 3 files in the FM2002-Patch1.zip into the Fleet Manager 2002 folder.

5. Execute the FM2002-Patch1.BAT file (this should execute rather quickly).

6. Open your Fleet Manager Client and check the device configuration.

NOTE: The fix applies the patch to the currently configured database only. (In other words, if you
change to another database, you will have to execute the batch file (FM2002-Patch1.BAT) again).

WARNING: This patch applies to FM2002 version 7.00.0000 ONLY, and should not be installed with
ANY other version of the Fleet Manager software.

1516
www.mixtelematics.com

1516
 1517

----- STATUS -----

This has been fixed with the patch supplied with this KBA, and will be included in the Fleet Manager
2002 Service Release one version of the software.

------------------------------------------------------------------------------

KEYWORDS: FM200e FM2002 Device

1517
www.mixtelematics.com

1517
 1518
10.3.275 Knowledge Base Article 280

Article Number 280

Title Nokia 6090 issues

Created 10/14/2002 8:55:47 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 10/14/2002 12:03:53 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 unit

· Nokia 6090

----- SUMMARY -----

This article describes some known issues when using a Nokia 6090 phone as GSM download
connection to the FM200 unit.

----- MORE INFORMATION -----

There are mainly two issues to take note of:

1. When receiving a new SMS

If a new SMS message arrives on the Nokia 6090 while other SMS messages are being read by the
FM200 unit, it (the SMS) might not be processed by the FM200 unit.

2. When answering a data call

When the Nokia 6090 receives a data (or any other) call, it rings.

a) If the user manually answers this call on the Nokia 6090 BEFORE the FM200 gets the chance to do
so, the Nokia 6090 malfunctions. To reset the Nokia 6090, and consequently return it to a normal
functioning state, it needs to be powered down.

b) If the user manually tries to answer (i.e. press the Answer/End button) the call AFTER the FM200
unit has answered it, the data call is terminated.

The function of the Answer/End button is depends on the state of the Nokia 6090 (i.e. it has a different
function when it is in a call to when it is out of a call).

To avoid the above from happening, DO NOT answer data calls. Data calls are distinguishable from
voice calls by the ring tone (Please consult your Nokia 6090 documentation for more information on
this).

3. Nokia 6090 Power Down function

The Nokia 6090 has a power down function. This can be set to power down the Nokia 6090 after a trip
(i.e. ignition has been disabled/switched off). In other words, if this has been set to 1 hour, the phone

1518
www.mixtelematics.com

1518
 1519

will turn off after 1 hour. This could conflict with the related setting in the FM200 configuration (and
switch off the Nokia 6090 before all GSM functions have been executed.

To avoid this from happening, set this Power down value to a number larger than what has been
specified in the Fleet Manager software or disable it.

4. Flow Control and AT Command Mode

Occasionally when the Nokia 6090 is in Command Mode (i.e. Nokia 6090 mode when executing AT
commands: reading SMS, checking signal quality, network registration) the Nokia 6090 could (for
various reasons) ignore Flow Control (controls the tempo of the data flow, and is needed for normal
functioning of the FM200 and FM Splitter). The command mode can malfunction, and will therefore not
respond to any requests from the FM200 unit.

To exit this mode, and return to the normal functioning, reset the Nokia 6090 by powering it down.

Important things to remember

* The FM200 reads and deletes all SMS messages, therefore the user will not receive normal
messages.

* In most cases a manual reset (manually powering down the Nokia 6090 & switching it on again), or
using the FM200 Relay to periodically shut down the Nokia 6090, fixes the problems mentioned above.
This cannot be done by the FM200 unit, as the Nokia 6090 does not support the Software Power Off
and Power On commands as does the Wavecom and Siemens modems.

* Installation suggestion:

Connect the Nokia 6090 Ignition Line through the FM200 External Drive Relay to VBat and set the
auto-off timeout of the phone to 45 seconds (the minimum). This will allow the Nokia 6090 Power
Down function to operate similar to other phones – i.e. instead of having the Power Off function set to
a maximum to avoid the phone from switching off (as suggested in 3), the time is set to a minimum
and connected through the External drive. If the power off time on Fleet Manager Client (in the GSM
Device calibration tab) is set to 4 hours, the Nokia 6090 will switch off after 4 hours, and the Nokia
6090 timer (set to 45 seconds) will count down, and power down the Nokia 6090.

----- STATUS -----

A number of these irregularities are due to Nokia 6090 design features. We are investigating possible
automated workaround(s) and/or solution(s) for the issues mentioned, but in the meantime, keep the
above-mentioned workarounds and tips in mind.

------------------------------------------------------------------------------

KEYWORDS: FM200 Nokia 6090

1519
www.mixtelematics.com

1519
 1520
10.3.276 Knowledge Base Article 281

Article Number 281

Title Error when connecting to SQL Server

Created 10/17/2002 10:26:18 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 10/17/2002 10:54:48 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· SQL Server 7.0 Service Pack 2 and later

----- SUMMARY -----

Microsoft reported error(s) occurring when using SQL Server 7. These errors occur for distributed
transactions (i.e. multiple db servers). This could have an effect on the Fleet Manager or Fleet
Manager Online software, as the minimum requirements include the SQL Server 7.0 Service Pack 3
database engine.

----- MORE INFORMATION -----

More information regarding this problem, can be found in the following Microsoft Knowledge Base
Article: Microsoft KBA Q266337.

----- STATUS -----

This is a Microsoft SQL Server issue, and beyond the scope of our control.

------------------------------------------------------------------------------

KEYWORDS: SQL Server FMOnline FM

1520
www.mixtelematics.com

1520
 1521
10.3.277 Knowledge Base Article 282

Article Number 282

Title Error upgrading FM2001 (SR1/SR2) database to FM2002

Created 10/17/2002 10:54:20 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 10/17/2002 11:07:25 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2001, all versions

· Fleet Manager 2002, version 7.00.0000

----- SUMMARY -----

When trying to upgrade your Fleet Manager 2001 software to Fleet Manager 2002, an error occurs
during the database upgrade part.

----- MORE INFORMATION -----

The error message displayed reads as follows:

An unexpected error occurred:

Error -2147467259 - Change to 'EventDescription' failed as a required event was disabled. occurred
in FMEventLoad.LoadEventDescription(Line 29340).

----- CAUSE -----

For some reason the Idle and Overspeeding events are not selected as they should be - this is
compulsory for the system to function normally.

----- SOLUTION -----

To work around this problem, and ensure a successful database upgrade, please do the following:

1) Open the FM2001 database in FM2001 (which ever version being upgraded from)

2) Edit Events, mark the Overspeeding and Idle as In Use (ticked in list)

3) Close the FMClient

4) Upgrade to FM2002.

The FM2001 database should upgrade to FM2002 now without a problem.

----- STATUS -----

This will be fixed in the next release of the Fleet Manager software. In the meantime, use the

1521
www.mixtelematics.com

1521
 1522

workaround provided.

------------------------------------------------------------------------------

KEYWORDS: Upgrade FM2001 FM2002

1522
www.mixtelematics.com

1522
 1523
10.3.278 Knowledge Base Article 283

Article Number 283

Title Pre Paid functionality in Fleet Manager

Created 11/5/2002 2:49:29 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/6/2002 11:30:58 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Fleet Manager 2000, all versions

· FM Fleet Manager 2001, all versions

· FM Fleet Manager 2002, all versions

----- SUMMARY -----

This article describes the purpose and use of the Prepaid functionality in the FM Fleet Manager
software.

----- MORE INFORMATION -----

The Fleet Manager software makes provision for Pre Paid functionality using two events, namely:

(1) Pre Paid - Disabled after period and (2) Pre Paid - Usage remaining.

(1) The Pre Paid - Disabled after period event consists of the following condition:

Usage Counter > [x] Hours

This Usage Counter counts the hours that the engine was on (i.e. ignition detected), and if it reaches
the [x] number of hours specified, by default switches on the relay. It is the responsibility of the
installer to connect the relay so that the desired action will be taken when the usage counter reaches
its limit (x).

The Pre Paid - Usage remaining event consists of the following conditions:

In Trip [is] TRUE AND

Usage Remaining [is] TRUE

This event will return the number of hours left at the end of each subtrip (this can be seen in the
activity timeline and the event report).

Note: The Usage Counter is reset to 0 (zero) everytime a new Vehicle Configuration is uploaded to
the vehicle unit.

------------------------------------------------------------------------------

1523
www.mixtelematics.com

1523
 1524

KEYWORDS: FM200 FM2000 FM2001 FM2002 Fleet Manager Software Event Prepaid

1524
www.mixtelematics.com

1524
 1525
10.3.279 Knowledge Base Article 284

Article Number 284

After uninstalling and reinstalling MSDE, I cannot open my existing database or

Title
create a new one

Created 11/6/2002 2:41:34 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/6/2002 3:20:09 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Fleet Manager 2001, all versions

· FM Fleet Manager 2002, all versions

· Microsoft SQL Server

----- SUMMARY -----

After uninstalling MSDE, and then reinstalling it, you may not have access to your "existing" SQL
Server databases or be able to create a "new" database with the same name as one created with the
previous SQL Server/MSDE installation.

The reason for this being that during the uninstallation, a file is removed, that keeps track of all
"currently" available databases. When MSDE is reinstalled, a new file is installed, and therefore do
not have the record of the previously created (FM) databases, even though they can be physically
located on the disk.

----- SOLUTION -----

To overcome this issue, you can either delete the physical files and create a new database from a
backup of your Fleet Manager database, or you will have to reattach the database to SQL Server.

To reattach the database, please follow the instructions below:

If you have query analyser installed (a part of MS SQL Server Client Tools), you can use method A
described below, otherwise you will have to use method B:

METHOD A - Reattaching database using Query Analyser

In query analyser, type the following command:

exec sp_attach_db N'FleetManager', N'C:\MSSQL7\data\FleetManager.mdf',

N'C:\MSSQL7\data\FleetManager.ldf'

In the above command we used the default database FleetManager - if this has been changed on
your installation, please use the appropriate database name instead of FleetManager, as well as the
correct path for the physical database.

1525
www.mixtelematics.com

1525
 1526

Above FleetManager is the logical database name - the name of the database you see in FMAdmin
FleetManager.mdf is the physical data filename FleetManager.ldf is the physical log filename.

If you do not know how to use query analyser, please get someone with some SQLServer knowledge
to help you. You will need the Client Tools from MSSQLServer7 or MSSQL2000 to be able to run
query analyser, and execute the command.

METHOD B - Dos command prompt

1. Start->Programs->Accessories->Command Prompt

2. If you used the default installation settings for MSDE, at the C:\ prompt, type the following:

C:\MSSQL7\BINN\osql -U sa -P

[and press ENTER]

3. now type the following:

exec sp_attach_db N'FleetManager', N'C:\MSSQL7\data\FleetManager.mdf',

N'C:\MSSQL7\data\FleetManager.ldf'

[and press ENTER]

4. and then type

GO

Repeat the above procedure for each database where necessary.

[and press ENTER]

5. Then type Exit and press enter, and Exit the dos command window

You should now be able to select this database in the FMAdmin connection dialog.

----- STATUS -----

This problem is beyond our control. Care should be taken to backup frequently, especially before
uninstalling or changing (upgrading) any of the Fleet Manager components or software.

------------------------------------------------------------------------------

KEYWORDS: FM2001 FM2002 Database Creation MSDE SQL install

1526
www.mixtelematics.com

1526
 1527
10.3.280 Knowledge Base Article 285

Article Number 285

Title Activity timeline details displayed incorrectly

Created 12/6/2002 12:15:00 PM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 12/6/2002 12:15:00 PM

Last Modified By Steve Crane (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2001

· Fleet Manager 2002

----- SUMMARY -----

Timeline details may not be correctly displayed when the timeline period starts at a time other than
midnight.

----- MORE INFORMATION -----

When the time line period starts at a time other than midnight, certain details may not be correctly
displayed when areas of parking time are selected. Specifically the end of parking event may not be
reflected. If it is the parking time shown may be incorrect.

----- CAUSE -----

The exact cause is not known at this time.

----- SOLUTION -----

The problem does not occur when the timeline period starts at midnight (00:00:00) so you should
display timelines that begin at midnight to be sure that the details displayed are correct.

----- STATUS -----

The problem is being investigated and will be corrected in a future release of Fleet Manager.

------------------------------------------------------------------------------

KEYWORDS: FM2002 timeline parking

1527
www.mixtelematics.com

1527
 1528
10.3.281 Knowledge Base Article 286

Article Number 286

Title No checkboxes on RTF report

Created 12/16/2002 1:04:45 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 12/16/2002 1:05:37 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2001, all versions

· Fleet Manager 2002, all versions

----- SUMMARY -----

No checkboxes are included on the RTF reports.

----- MORE INFORMATION -----

When generating a report in Rich Text Format (RTF or .rtf), checkboxes (such as the checkboxes for
interval/tacho data on the Vehicle Configuration report), is not included on report.

----- CAUSE -----

When exporting Access reports to RTF, graphical elements are not included. (This is by design).

----- STATUS -----

In a case where checkboxes are used on report (such as the Vehicle configuration report), it is
advisable to generate the report in Snapshot format (.snp).

------------------------------------------------------------------------------

KEYWORDS: Report Export RTF

1528
www.mixtelematics.com

1528
 1529
10.3.282 Knowledge Base Article 287

Article Number 287

Title Missing Dutch Language Files

Created 12/17/2002 3:51:24 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 12/20/2002 9:25:32 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Terminal

· Fleet Manager 2002

----- SUMMARY -----

There are no Dutch Language files available for the FMTerminal in the Fleet Manager 2002 software.

----- MORE INFORMATION -----

The Dutch Language files was not included in the original Fleet Manager 2002 release. It is therefore
not possible to upload Dutch scripts for the FMTerminal.

----- CAUSE -----

Dutch Language files was not included in the Fleet Manager 2002 software set.

----- SOLUTION -----

Download the following patch and install it as follows:

1. Download and save this patch: FM2002-Patch for FMT Dutch.zip.

2. Extract this file into your "Fleet Manager\FMTerminal" install directory (typically "C:\Program Files
\Fleet Manager 2002\FMTerminal").

3. Retest uploading Dutch script to the FMTerminal (this should work after extracting the 5 files
included in the patch to the FMTerminal directory).

----- STATUS -----

This is fixed in the patch supplied, and will be included in Fleet Manager 2002 SR1.

------------------------------------------------------------------------------

KEYWORDS: FMT FMTerminal Terminal Script FM2002 Dutch

1529
www.mixtelematics.com

1529
 1530
10.3.283 Knowledge Base Article 288

Article Number 288

Title Using COM ports higher than COM1 to COM4 with the SMS Processor

Created 1/6/2003 1:19:17 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 1/6/2003 1:21:19 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002 all versions

· Fleet Manager SMS Processor

----- SUMMARY -----

This article describes the way to select a COM port other than COM1 to COM4 with the SMS
processor, as this it is possible to do so, but currently not very obvious HOW.

----- MORE INFORMATION -----

In the SMS Processor it is possible to select either COM1, COM2, COM3 or COM4 as the port to be
used for the modem used in conjunction with the Fleet Manager SMS Processor.

To select any other COM port, simply make a change to the Registry of the computer as described
below:

1. Enter the system registry by clicking Start->Run and type "regedit".

2. to to the following key in the registry

HKEY_LOCAL_MACHINE\Software\Data Pro Development (Pty) Ltd\Fleet Manager\SMS Processor

\Modem001

(if you want to add this to a second modem on the computer, go to "Modem002")

3. Now, on the right handside of the Registry, you will see a string value called "Port", and its value
can be anything from "COM1" to "COM4" to "UNUSED". All you need to do, to be able to select other
ports, such as COM5 or COM6 in this list, is change this value in the registry to "COM5" or "COM6".

----- STATUS -----

This is by design, and can be changed as described in this KBA.

------------------------------------------------------------------------------

KEYWORDS: SMS Processor FM2002 COM Port

1530
www.mixtelematics.com

1530
 1531
10.3.284 Knowledge Base Article 289

Article Number 289

Title Setting engine hours via GSM

Created 1/7/2003 11:38:09 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 1/7/2003 12:02:26 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002

· GSM Downloader GSMDl.exe version 7.02.0011

----- SUMMARY -----

When setting engine hours via GSM, the engine hours seems to be set to 0 instead of a specified
value (if set to anything other than 0).

----- MORE INFORMATION -----

When setting the engine hours with an Engine hours plug, the engine hours is set to the correct value,
but when attempting to do this with the GSM Downloader, the value the Engine hours is set to, seems
to be 0 regardless of what you set it to.

----- CAUSE -----

The GSM Downloader assumes the value entered is seconds instead of hours, while the Engine hours
plug assumes the value entered is hours.

----- SOLUTION -----

A current work around for this would be to use an Engine Hours plug when setting the engine hours of
a certain vehicle, or to convert the value for engine hours to seconds when using the GSM
Downloader to do this.

When using the GSM Downloader to set the engine hours, the "Engine hour value" will have to be
multiplied by 3600 to assume the correct HOUR value the Engine hours have to be set to.

For example:

If you want to set you engine hours to "10", you can use an engine hours plug and set it the engine
hour value to "10".

Alternatively, you can use the GSM Downloader, but will have to do the following calculation to ensure
that engine hours are set to "10":

10 hours x 3600 (to convert the hours to seconds) results in 36 000 seconds.

The engine hours value to be entered in the GSM Downloader, is therefore 36000 which will ensure

1531
www.mixtelematics.com

1531
 1532

that engine hours is set 10 hours.

----- STATUS -----

This will be fixed in the next version of the GSM Downloader. In the meantime, use the workaround
above when setting engine hours (via GSM).

------------------------------------------------------------------------------

KEYWORDS: GSM Downloader Engine Hours FM2002

1532
www.mixtelematics.com

1532
 1533
10.3.285 Knowledge Base Article 290

Article Number 290

Title Power management with the FM200PLUS unit and its positive drive

Created 1/10/2003 2:15:45 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 1/10/2003 2:15:45 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM200 PLUS unit and harness

· FMTerminal

· FMSplitter

----- SUMMARY -----

When using the positive drive of the FM200PLUS unit to control the power to devices (such as a GPS
unit, GSM/DECT or other serial device) connected to the FM200PLUS unit, it should be noted that the
positive drive will always shutdown the FMTerminal as well as the FMSplitter (by default) as a result of
the positive drive being switched off.

----- MORE INFORMATION -----

When connecting certain devices (such as a GPS unit and/or GSM unit, DECT unit, or other serial
device) to the FM200PLUS, the positive drive can be used to manage the power to these devices. The
use of the positive drive could be compared to the external relay of the FM200 unit.

The positive drive is directly connected to the FMTerminal and FMSplitter, and is controlled by a switch.
When this switch is turned off, the power to everything connected to the positive drive will be turned off
– this means that the FMTerminal and FMSplitter (and consequently anything connected to the splitter),
will always be turned off by default.

Therefore, in a case where the GPS has been connected to the positive drive, and a GSM modem
connected to the FMSplitter (on SB), the power of both these devices, as well as that of the FMTerminal
will be turned off when the positive drive is switched off.

It is important to remember this when you want to use the GSM modem for downloading of uploading
information to and from the FM200PLUS unit. If the GSM modem has been switched off it will not be
available for uploading or downloading of data (this shouldn’t be a problem though, as in most cases
the shutting down time for the GPS as well as the GSM are set to be the same and can also be
controlled by the user).

Devices installed on the other serial port (S2) will not be affected when shutting down the positive drive.

Managing power this way ensures optimal use of power, and reduces the risk of wasting it.

----- STATUS -----

1533
www.mixtelematics.com

1533
 1534

This is by design.

------------------------------------------------------------------------------

KEYWORDS: FM200PLUS FMTerminal FMSplitter Power Management Terminal Splitter Serial Device
GSM GPS DECT

1534
www.mixtelematics.com

1534
 1535
10.3.286 Knowledge Base Article 291

Article Number 291

Title FM-Terminal Custom Script Update

Created 1/28/2003 3:56:19 PM

Created By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Last Modified 2/18/2003 8:49:36 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Custom (client) FM-Terminal scripts that need to be updated to work with DDMs distributed with
FM2002SR1.

----- SUMMARY -----

FM-Terminal Script has a new structure.

----- MORE INFORMATION -----

FM-Terminal scripts has a new structure from FM2002 SR1. Older, custom, scripts will no longer
compile and run using the SR1 release. Custom scripts must be modified to use the new structure.

After upgrading the software to Fleet Manager 2002 SR1, the following message might be displayed
(indicating that custom FMTerminal script files was detected):

The format of the script files used by the FMTerminal scripts have been changed. The references to
the standard scripts have been changed.

The update detected customised script files. Please ensure that these scripts are updated.

This message will be displayed each time the/a database is upgraded, until the custom scripts have
been updated as described in this KBA.

----- SOLUTION -----

Please download (extract and read) the following document for detailed information on this:
ScriptEditor.zip.

----- STATUS -----

Refer to the FMTerminal Script Editor Software Development Kit User Guide version 1.05 or later, for
more information on how to update your custom scripts, or send us your script to be updated.

------------------------------------------------------------------------------

KEYWORDS: FMTerminal Terminal FM-Terminal script scripting FM2002 SR1 FM2002SR1

1535
www.mixtelematics.com

1535
 1536
10.3.287 Knowledge Base Article 292

Article Number 292

Title Reload DDMs after upgrading to FM2002 SR1

Created 1/29/2003 9:09:38 AM

Created By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Last Modified 1/29/2003 9:15:17 AM

Last Modified By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002 SR1 & FMTerminal

----- SUMMARY -----

After upgrading from a previous version of the Fleet Manager software, to Fleet Manager 2002 SR1, it is
necessary to reload the device drivers (modules) of the FMTerminal unit.

----- MORE INFORMATION -----

The reloading of the latest device drivers is necessary, as certain enhancements were made to the
FMTerminal DDMs for FM2002 SR1. Trying to upload a new Script onto the FMTerminal (by loading a
new event configuration, for example), before updating the device drivers, will fail, as the new Scripts
are dependent on certain enhancements made to the DDMs.

----- SOLUTION -----

Please upload the latest DDMs (Using the FMDealer) to each FMTerminal unit before trying to update
the event configuration. You can do this by creating a Vehicle plug from the FMDealer software, and
selecting "Load Device Drivers -> FMTerminal: Modules".

----- STATUS -----

The functionality is by design.

------------------------------------------------------------------------------

KEYWORDS: DDR DDM FM200 FM200e FM2002 SR1 FMTerminal

1536
www.mixtelematics.com

1536
 1537
10.3.288 Knowledge Base Article 293

Article Number 293

Title Error connecting to a DB without permission

Created 2/13/2003 12:29:55 PM

Created By Wesley De La Harpe (MiX Telematics - Stellenbosch)

Last Modified 3/14/2003 4:15:26 PM

Last Modified By Wayne Davies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM2001 to FM2002SR1

----- SUMMARY -----

If a User is created on the SQL Server that does not have permission to connect to it, the FMAdmin
gets an Unexpected error while trying to connect to it

----- MORE INFORMATION -----

The Error is:Error -2147023840 Service Control Error:An instance of the server is already running.
frmconnect.cmdok_click line 7540

----- CAUSE -----

The User does not have EXECUTE permissions in SQL

----- SOLUTION -----

Give the User FULL RIGHTS

----- STATUS -----

This should be fixed in a future version

------------------------------------------------------------------------------

KEYWORDS: -2147023840 Service Control Error:An instance of the server is already running.
frmconnect.cmdok_click line 7540 Error connecting to a DB without permission EXECUTE permissions

1537
www.mixtelematics.com

1537
 1538
10.3.289 Knowledge Base Article 294

Article Number 294

Title FM200 Plus Device Driver Upgrade

Created 2/13/2003 12:30:35 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 2/14/2003 9:02:02 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM200 Plus unit

· FMDealer version 2.9.6.0

· FM200 Plus Update CD

· i.e. FM200 Plus units containing device drivers from the FM200 Plus Update CD

----- SUMMARY -----

In certain cases the GSM Device Driver uploads to FM200 Plus units fail. This does not happen
consistently, but could happen when doing a GSM upgrade of units having device drivers from the
FM200 Plus Update (September 2002) CD (i.e. FMDealer version 2.9.6.0) to the FM2002 SR1 release
device drivers.

----- MORE INFORMATION -----

In most cases, this failure is specific to Device Drivers on the unit already, and requires a specific
procedure to do the replacement.

----- CAUSE -----

When a Device Driver upload is attempted via GSM, the vehicle configuration is checked for specific
information concerning the unit type and components thereof. This only applies to a specific setup, and
therefore is not always relevant. If the required information is not found the Device Driver update will fail.

----- SOLUTION -----

To ensure that a Device Driver upload does not fail (via GSM), you have two choices:

A. either upload Device Drivers manually (with a Device Driver or vehicle specific plug), or

B. GSM upload using the following specific procedure:

1. Schedule a Fleet Manager 2002 SR1 (version 7.10.0021) configuration update for the FM200 Plus
unit:

this configuration should NOT include any of the following devices or events for the specific unit: Dayton
device, FMTerminal device of Location events.

1538
www.mixtelematics.com

1538
 1539

2. After the configuration has been updated successfully as specified above, the Device Driver upload
can be scheduled from the GSM Downloader.

3. After the Device Driver upload succeeded, any changes to the configuration can be made and
uploaded.

In the case where the Device Driver upload via GSM still fails with the following message:

Unknown connected device

please use a Device Driver plug and upload the device drivers manually to the unit.

----- STATUS -----

This workaround should be used to avoid a situation where Device Drivers cannot be uploaded.

This has been catered for in the latest set of Device Drivers available (i.e. any FMDealer from the Fleet
Manager 2002 January 2003 release version and onwards). This ONLY applies to the FM200 Plus
Device Drivers released with the FMDealer version 2.9.6.0. on the FM200 Plus Update CD.

------------------------------------------------------------------------------

KEYWORDS: FM200 Plus Device Driver Upload GSM Downloader DDX

1539
www.mixtelematics.com

1539
 1540
10.3.290 Knowledge Base Article 295

Article Number 295

Title Data download stops at processing phase

Created 2/17/2003 4:39:19 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/25/2003 2:48:13 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002, January 2003 release

----- SUMMARY -----

When trying to download information into the Fleet Manager database, via Autopoll or Manually, the
download stops without displaying any significant error messages.

----- MORE INFORMATION -----

When doing a manual plug download, the download seems to stop at the Process phase of the
download, and the Cancel and Help command buttons are enabled, confirming that 0 trips and 0
events was downloaded.

In the case where download files are transferred via Autopoll to the database, these files seems to
be processed, but the information never appears in the database.

As the preprocess phase completes successfully, no data will be lost. After the patch has been
applied, any previously preprocessed data will then be processed correctly when the vehicle is
downloaded the next time.

Another symptom of this could be that when doing a status request via GSM, the following error is
recorded in the DlSchLog.txt:

ERROR: An unexpected error has occurred in GetFM200Status - 94 (5E): Invalid use of Null
occurred in FMParam.Calibrate (Line 1680). (Line 5810)

----- CAUSE -----

This problem was introduced in Fleet Manager 2001, but only discovered in the latest version of the
Fleet Manager 2002 (January 2003 release) software. It will therefore only occur in databases
upgraded from Fleet Manager 2001 versions under certain conditions.

----- SOLUTION -----

Please download and execute the patch as described below:

The updated install set for the FMDealer utility should be downloaded from the http://www.
mixtelematics.com website (from the Downloads\FM FM Accessories section).

Please note:

1540
www.mixtelematics.com

1540
 1541

* IMPORTANT: Patch 1 to 7 should NOT be applied after this update (Patch 8) has been installed.

* This patch supercedes all patches released since the release of the Fleet Manager 2002 SR1
software in January 2003.

* This upgrade should be done on each computer where the above-mentioned version of the Fleet
Manager software is installed (even though previous patches have been installed).

* All Fleet Manager software and components should be shut down before attempting the upgrade as
described below.

* The update is only applied to the currently selected database.

* In the case where the FM system has been set up as Client/Server, this patch should be applied to
the Server computer (where the Fleet Manager database is located) as well as to all Fleet Manager
Client computers, but for the client computers, the database upgrade should be canceled.

1. Download the following file, and save it to your hard disk: FleetManager2002SR1Patch8.exe (size:
12MB)

2. Please ensure that none of your Fleet Manager software or components are running.

3. To install the patch, double click the file (FleetManager2002SR1Patch8.exe).

4. The file will extract and overwrite some files in the Fleet Manager 2002 install directory, and will
then initiate a database upgrade. Please DO NOT interrupt the database upgrade at any stage.

After you've applied this patch, you can run your Fleet Manager software again, do a quick download
for affected vehicles to confirm that data is now downloaded correctly into the database (by doing a
download either manually or via Autopoll).

----- STATUS -----

This has been corrected by the patch supplied, and will be included in the following version of the
Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200PLUS Download Autopoll Manual Quick Full

RELATED KBAs: 299, 300, 306, 307, 308, 309

1541
www.mixtelematics.com

1541
 1542
10.3.291 Knowledge Base Article 296

Article Number 296

Title TCO 1319 & ELVIST

Created 2/24/2003 4:07:58 PM

Created By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Last Modified 2/24/2003 4:07:58 PM

Last Modified By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FMTCO Interface (ELVIST) & TCO 1319

----- SUMMARY -----

For ELVIST to work with a TCO 1319, the 1319 must be installed with it's IGNITION wire permanently
connected to BATTERY.

----- MORE INFORMATION -----

For ELVIST to work with a TCO 1319, the 1319 must be installed with it's IGNITION wire permanently
connected to BATTERY.

This is because the TCO 1319 does not communicate via it's INFO interface, when it's IGNITION is off.
This causes the FM200 / FM200Plus to miss information (driver modes etc.), which causes ELVIST to
malfunction.

----- SOLUTION -----

Install the TCO 1319 with it's IGNITION wire connected to BATTERY.

------------------------------------------------------------------------------

KEYWORDS: FMTCO Interface ELVIST TCO 1319 TCO1319 FTCO

1542
www.mixtelematics.com

1542
 1543
10.3.292 Knowledge Base Article 297

Article Number 297

Title FM200 Plus configuration uploaded to FM200 unit via GSM

Created 2/27/2003 11:32:48 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 2/27/2003 11:35:26 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 units

· FM2002 SR1

----- SUMMARY -----

It is possible to upload FM200 Plus configuration to FM200 units via GSM, causing these units to hang.

----- MORE INFORMATION -----

After uploading a FM200 Plus configuration to a FM200 unit, the unit seems to be hanging. The unit
responds to some plugs, but seems to go into a loop, and neither clearing the unit, or attempts of
reloading the firmware succeeds. (Please note: this is specific to FM200 units receiving a FM200 Plus
configuration, this will NOT affect all FM200 units). Care should be taken to ensure that a vehicle unit
and the unit type in the database corresponds to each other.

----- CAUSE -----

A certain vehicle is identified as a FM200 Plus vehicle in the Fleet Manager software, but the unit in the
vehicle (with this specific vehicle ID) is in actual fact a FM200 unit. If a configuration upload is
scheduled via GSM, the difference in unit type is not detected and the FM200 Plus configuration is
uploaded to the FM200 unit, causing the unit to hang.

----- SOLUTION -----

To reset your unit back to a working FM200 unit, please follow the procedure below:

1. In the Fleet Manager software, change the unit type to be FM200 instead of FM200 Plus.

2. Download and install the latest version of the FMDealer utility from the www.cidev.com

3. Format a 256KB vehicle plug as a FM200 Device Driver plug with this version of the FMDealer

4. Initialise this plug with the default FM200 Device Drivers (on the FMDealer -> Code Plug Functions ->
Load Device Drivers -> FM200 Device Drivers)

5. Insert this plug into the vehicle socket, and upload these device drivers to the FM200 unit.

6. After you've successfully uploaded the device drivers to this unit, try doing a full download to see
whether the data on the unit is still accessable.

1543
www.mixtelematics.com

1543
 1544

7. If the data on the unit is corrupt (which is highly likely, as the wrong configuration was uploaded),
please clear the unit, and do a swap unit for the specific unit in the database (as per KBA 41).

8. If it was necessary to clear the unit, reload the FM200 vehicle configuration from the database.

The unit should now be set up correctly to start recording data again.

----- STATUS -----

This is under investigation, and a preventative procedure for this will be set in place in the next software
release.

------------------------------------------------------------------------------

KEYWORDS: FM200 unit FM200 Plus FM200PLUS configuration upload FM2002 SR1 Fleet Manager
software

1544
www.mixtelematics.com

1544
 1545
10.3.293 Knowledge Base Article 298

Article Number 298

Title Importing suburb location data using the GPS Log Viewer

Created 3/17/2003 3:08:55 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 3/18/2003 9:26:14 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Fleet Manager 2002 SR1, January 2003 release

· South African FM GPS Logviewer (FMGPSCIS.dll) version 7.01.0091

· Australian FM GPS Logviewer (FMGPSCIA.dll) version 7.00.0005

· Location Reports extension (ProdRep.dll) version 7.00.0076

----- SUMMARY -----

It is possible to include suburb location data in Location Reports for South African and Australian
regions.

It is however necessary to import suburb location data using the GPS Log Viewer (South Africa /
Australia) before it will be displayed on the Location Reports. This KBA describes the process of
importing suburb location data into the Fleet Manager database using the GPS Log Viewer Extension.

----- MORE INFORMATION -----

To import suburb location data using the GPS Logviewer do the following:

1. Open the FM GPS Log Viewer (South Africa / Australia)

2. From the File menu, select Import System Locations.

3. Follow the instructions on the popup message boxes.

Please note: This process could take some time (in some cases up to an hour), and should not be
interrupted, as per the message displayed in the software.

After the import has completed successfully, suburb data can be used for location reports. When a trip
starts or ends outside of a user-defined location and the Use GIS data to try to find the names for
unidentified locations (slow) option is checked, the valid suburb name will be displayed in the location
report, instead of the normal "unidentified location".

For more specific information on displaying the suburb data in your Location Reports, please refer to
the Fleet Manager Location Reports Extension documentation. The documentation for this extension
can be found on the FMOffice SR1 (January 2003) CD or can be downloaded from the www.cidev.com
website under the FM FM Extensions section).

1545
www.mixtelematics.com

1545
 1546

----- STATUS -----

This is by design.

------------------------------------------------------------------------------

KEYWORDS: FMOffice Location Suburb Data GPS Log Viewer GIS

1546
www.mixtelematics.com

1546
 1547
10.3.294 Knowledge Base Article 299

Article Number 299

Title Downloaded data not showing in database

Created 4/3/2003 3:54:56 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/25/2003 2:43:43 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002, January 2003 release

----- SUMMARY -----

When downloading information into the Fleet Manager database, via Autopoll, the download stops
without displaying any error messages.

----- MORE INFORMATION -----

After the vehicle data has been transferred from either the plug or via the Autopoll Client, the vehicle
are not updated in the Fleet Manager Client software, as is expected. Some vehicles' Last Download
dates do not change, even though trip data exists on the plug/unit for a later date.

As the preprocess phase completes successfully, no data will be lost. After applying the patch as
described below, any previously preprocessed data will then be processed correctly when the vehicle
is downloaded the next time.

----- CAUSE -----

This is due to incorrect handling of a specific circumstance in the raw event data stream from the FM
Unit.

----- SOLUTION -----

It is necessary to upgrade the affected database with the updated FMDB7.zql file included in the patch
below.

To do this, please install the patch as described below:

The updated install set for the FMDealer utility should be downloaded from the http://www.
mixtelematics.com website (from the Downloads\FM FM Accessories section).

Please note:

* IMPORTANT: Patch 1 to 7 should NOT be applied after this update (Patch 8) has been installed.

* This patch supercedes all patches released since the release of the Fleet Manager 2002 SR1
software in January 2003.

* This upgrade should be done on each computer where the above-mentioned version of the Fleet

1547
www.mixtelematics.com

1547
 1548

Manager software is installed (even though previous patches have been installed).

* All Fleet Manager software and components should be shut down before attempting the upgrade as
described below.

* The update is only applied to the currently selected database.

* In the case where the FM system has been set up as Client/Server, this patch should be applied to
the Server computer (where the Fleet Manager database is located) as well as to all Fleet Manager
Client computers, but for the client computers, the database upgrade should be canceled.

1. Download the following file, and save it to your hard disk: FleetManager2002SR1Patch8.exe (size:
12MB)

2. Please ensure that none of your Fleet Manager software or components are running.

3. To install the patch, double click the file (FleetManager2002SR1Patch8.exe).

4. The file will extract and overwrite some files in the Fleet Manager 2002 install directory, and will then
initiate a database upgrade. Please DO NOT interrupt the database upgrade at any stage.

5. After the database upgrade have completed successfully, a quick download for each of the affected
vehicles should prompt the process phase of the unprocessed data to start, and all the information
downloaded thus far should appear in the database.

----- STATUS -----

This has been corrected by the patch supplied, and will be included in the following version of the
Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200PLUS Download Autopoll Manual Quick Full

RELATED KBAs: 295, 300, 306, 307, 308, 309

1548
www.mixtelematics.com

1548
 1549
10.3.295 Knowledge Base Article 300

Article Number 300

Title Maximum SMS sent when active tracking enabled event becomes true

Created 4/15/2003 2:32:02 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/11/2005 8:57:59 AM

Last Modified By Daniel Lehniger (Siemens FM Automotive - Switzerland)

Details
----- APPLIES TO ----

· Fleet Manager 2002 SR1 (January 2003) version 7.10.0024

· FMSvr7.dll version 7.10.0034

----- SUMMARY -----

When using a vehicle configuration that triggers active tracking when an event becomes true, the
maximum number of SMS is sent when the event becomes true.

----- MORE INFORMATION -----

This does not affect the Active Tracking triggered from the Active Tracking and Messaging Extension.

If an event is configured to put the unit into active track mode, (by using the Enable Active Tracking
option on the Active tab), then as soon as the event becomes true, the maximum number of SMS's
allowed per day will be sent - regardless of the Tracking delay or Tracking interval set.

----- CAUSE -----

This is caused by incorrect handling of Active Tracking Events in the Server component.

----- SOLUTION -----

Please download and install the patch as described below:

Please note:

* IMPORTANT: Patch 1 to 7 should NOT be applied after this update (Patch 8) has been installed.

* This patch supercedes all patches released since the release of the Fleet Manager 2002 SR1
software in January 2003.

* This upgrade should be done on each computer where the above-mentioned version of the Fleet
Manager software is installed (even though previous patches have been installed).

* All Fleet Manager software and components should be shut down before attempting the upgrade as
described below.

* The update is only applied to the currently selected database.

1549
www.mixtelematics.com

1549
 1550

* In the case where the FM system has been set up as Client/Server, this patch should be applied to
the Server computer (where the Fleet Manager database is located) as well as to all Fleet Manager
Client computers, but for the client computers, the database upgrade should be canceled.

1. Download the following file, and save it to your hard disk: FleetManager2002SR1Patch8.exe (size:
12MB)

2. Please ensure that none of your Fleet Manager software or components are running.

3. To install the patch, double click the file (FleetManager2002SR1Patch8.exe).

4. The file will extract and overwrite some files in the Fleet Manager 2002 install directory, and will then
initiate a database upgrade. Please DO NOT interrupt the database upgrade at any stage.

5. After you have completed this successfully, open the Fleet Manager client, and reload the vehicle
configuration(s) to the affected units (by reinitialising them in the software with the patch applied).

----- STATUS -----

This has been resolved with the patch supplied, and will be included in the next version of the Fleet
Manager software.

------------------------------------------------------------------------------

KEYWORDS:

Fleet Manager SMS Processor Active Events

RELATED KBAs: 295, 299, 306, 307, 308, 309

1550
www.mixtelematics.com

1550
 1551
10.3.296 Knowledge Base Article 301

Article Number 301

Title Ensuring successful remote vehicle configuration upload

Created 4/22/2003 3:58:20 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/7/2003 12:45:40 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002 SR1 January 2003 Release

· FM 200 Plus unit

----- SUMMARY -----

In some cases irregularities with regards to vehicle configuration uploads have been experienced.
These irregularities are limited to vehicle configurations uploaded remotely (i.e. when uploading
vehicle configuration via DECT or GSM, and usually only applies to Dayton/Location events). Some of
these irregularities could cause a vehicle configuration to get corrupted to the extent that the unit
does not recognise the configuration, and the vehicle configuration needs to be reloaded manually (i.
e. with a vehicle plug).

----- SOLUTION -----

To ensure successful remote vehicle configuration upload, download and install the latest version of
the FMDealer Utility (the latest version of the FMDealer Utility will install an updated DMI2.exe file that
will help ensure successful remote configuration upload).

The updated install set for the FMDealer utility should be downloaded from the http://www.
mixtelematics.com website (from the Downloads\FM FM Accessories section).

----- STATUS -----

This solution will included in the next release of the Fleet Manager software & components mentioned
above.

------------------------------------------------------------------------------

KEYWORDS: Fleet Manager 2002 SR1 Configuration Upload GSM DECT Downloader

1551
www.mixtelematics.com

1551
 1552
10.3.297 Knowledge Base Article 302

Article Number 302

Title FM Lite and USB Printer

Created 4/23/2003 3:12:56 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 4/23/2003 4:02:17 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FMLite version 2.5

----- SUMMARY -----

When trying to print a report from the FMLite software, it does not print correctly, when printing to a USB
Printer.

----- MORE INFORMATION -----

When trying to print a report from the FMLite software to a USB printer, the header information of the
report will print, but the rest of the data will not.

The report preview will generate and display without a problem. The only time the format of the report is
affected, is when it is physically printed.

----- CAUSE -----

The FMLite software uses a 16-bit reporting engine that does not support printing to a USB printer.

----- SOLUTION -----

To ensure correct printing of reports, the current workaround is to use a parallel printer instead of the
USB printer.

----- STATUS -----

This is beyond our control. Due to the fact that the FMLite system can currently be used on anything
from Windows 3.1 to Windows XP, it will not be possible to replace the reporting engine at this time.

------------------------------------------------------------------------------

KEYWORDS: FMLite FM Lite Report USB Printer

1552
www.mixtelematics.com

1552
 1553
10.3.298 Knowledge Base Article 303

Article Number 303

Title Updated DCOM Client/Server installation procedure

Created 5/9/2003 4:33:48 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/25/2003 2:30:29 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002 July 2002 release

· Fleet Manager 2002 SR1 January 2003 release

----- SUMMARY -----

Some enhancements have been made to the procedure of setting up the DCOM Network installation.
These improvements have been documented, and the new version of the Network Configurations
guide is available from the link below.

----- MORE INFORMATION -----

The updated procedure does not include hosting the FMSvr7.dll package by MTS or COM+. The
advantage of this is that some long running downloads used to stop in the Process phase if the
FMSvr7.dll file was hosted by MTS or COM+, and the new way of setting up the Network
Configurations Download, should prevent this from happening.

----- SOLUTION -----

Install the package provided with this KBA, and follow the steps below in cooperation with the new
Network Configurations guide provided with this patch.

Please note:

* IMPORTANT: Patch 1 to 7 should NOT be applied after this update (Patch 8) has been installed.

* This patch supercedes all patches released since the release of the Fleet Manager 2002 SR1
software in January 2003.

* This upgrade should be done on each computer where the above-mentioned version of the Fleet
Manager software is installed (even though previous patches have been installed).

* All Fleet Manager software and components should be shut down before attempting the upgrade as
described below.

* The update is only applied to the currently selected database.

* In the case where the FM system has been set up as Client/Server, this patch should be applied to
the Server computer (where the Fleet Manager database is located) as well as to all Fleet Manager
Client computers, but for the client computers, the database upgrade should be canceled.

1553
www.mixtelematics.com

1553
 1554

1. Download the following file, and save it to your hard disk: FleetManager2002SR1Patch8.exe (size:
12MB)

2. Please ensure that none of your Fleet Manager software or components are running.

3. To install the patch, double click the file (FleetManager2002SR1Patch8.exe).

4. The file will extract and overwrite some files in the Fleet Manager 2002 install directory, and will
then initiate a database upgrade. Please DO NOT interrupt the database upgrade at any stage.

5. Download the updated Fleet Manager Network Configuration Guide.pdf and use it as guide to set
up the FM Software as Client/Server using DCOM.

6. PLEASE NOTE: If you have a current DCOM Client/Server setup:

a. DELETE the Fleet Manager package created following the previous Network Configuration Guide
(or use view the following document: DELETE FMPackage.doc.

b. After the Fleet Manager package has been deleted successfully from MTS or COM+, follow the
instructions in the new Network Configurations guide from step 6.

(If you are doing the Client/Server setup for the first time, ignore this step).

----- STATUS -----

This document and attached file will be included in the FM release version following the FMOffice SR
January 2003 release.

------------------------------------------------------------------------------

KEYWORDS: DCOM Network Configuration Setup Client/Server Client Server FMServer FMSvr7.dll

1554
www.mixtelematics.com

1554
 1555
10.3.299 Knowledge Base Article 304

Article Number 304

Title Connecting devices to the FM200 Plus Serial cable

Created 5/21/2003 10:39:16 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 5/21/2003 1:14:59 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 Plus Serial cable

----- SUMMARY -----

When connecting devices to the FM200 Plus Serial cable, and problems are experienced, please
consult the documentation on connecting devices to either S1, S2 or S3.

On one batch of cables the labels of the S2 and S3 cables were inadvertently swapped around.
Please note that S2 is the longer of the two cables and should be connected to the GSM, while S3 is
the shorter of the two cables and should be connected to the Dayton. This is indicated correctly on the
documentation supplied with the FM200 Plus Serial cable.

----- MORE INFORMATION -----

In the case where a device is connected to S2, but it is set up in the Fleet Manager software to be
connected to S3, the device will not function at all. This could easily happen if a FM200 Plus Serial
cable was labeled incorrectly.

If this possibility has been ruled out, and devices are indeed connected correctly, use diagnostic code
plugs to determine the reason for the device not functioning correctly, or not functioning at all.

Also consider using another device to test whether the reason for the malfunctioning is device specific,
or setup specific (i.e. if you are connecting a GSM Modem to S2, and cannot get it to function
correctly, use another GSM Modem to rule out the possibility of the cause being the Modem itself
malfunctioning - if a second modem is working, and the first would not work, there either was a
problem with the modem, or the settings on the modem itself did not correlate with that of the
software).

Please note that if a FM Splitter cable is used instead of the FM200 Plus Serial cable, the appropriate
device should be selected in the Fleet Manager software on the Devices tab. (I.e the FM Splitter
should be connected to S1).

----- SOLUTION -----

Identify S2 and S3 as described above, or use the documentation supplied with the FM200 Plus cable
to determine whether the cable was labeled correctly.

------------------------------------------------------------------------------

KEYWORDS: FM200 Plus Serial Cable Dayton GSM Modem DECT S1 S2 S3

1555
www.mixtelematics.com

1555
 1556
10.3.300 Knowledge Base Article 305

Article Number 305

Title Additional Location Reports functionality

Created 5/22/2003 4:17:51 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 5/23/2003 2:56:45 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002 SR1 January 2003 release

· ProdRep.dll version 7.00.0076

----- SUMMARY -----

The Location Reports extension previously used to report on a drive through locations basis. This
was changed to report on a subtrip start and stop basis (with the Fleet Manager 2002 SR1 January
2003 release), i.e. a report would be generated to show stops made in locations instead of showing
all locations the vehicle drove through.

The Location Reports Extension has now been updated to include additional reports containing data
on a drive through basis as well as those only showing subtrip data.

----- MORE INFORMATION -----

This (May 2003) version of the Location Reports Extension includes two new reports: Vehicle
Location Report and Driver Location Report is accessed from the Reporting menu (Vehicle Reports
> Location Reports > Driving, Driver Reports > Location Reports > Driving respectively).

These reports base location visits on all GPS points recorded during the trip. A location visit is
reported when a vehicle drives through a location and at least one GPS point is recorded inside the
location. The time of the first GPS point is reported as the entry time, and that of the first GPS point
outside the location as the exit time.

NOTE: Because all GPS points for selected vehicles are checked against all selected locations, the
report can take some time to generate. Please be patient, or specify less vehicles/locations and/or
shorter time periods.

----- SOLUTION -----

Download the updated extension from the following link and install as described below:

Please note: before installing this update, make sure that the Location Reports extension from the
FMOffice 2002 SR1 January 2003 release is installed, and that the Fleet Manager software isn't
running.

1. Download the following file: LocationReports_Update.zip.

2. Extract this file to your Fleet Manager install directory, replacing and overwriting the previous

1556
www.mixtelematics.com

1556
 1557

ProdRep.dll file

3. The additional reports will be available the next time you run the Fleet Manager software.

----- STATUS -----

This updated version of the Location Reports will be included in the next software release, and is
downloadable from the link supplied in the SOLUTION section of this KBA.

------------------------------------------------------------------------------

KEYWORDS: Location Reports ProdRep.dll FM2002SR1

1557
www.mixtelematics.com

1557
 1558
10.3.301 Knowledge Base Article 306

Article Number 306

Title Driver Scoring Reports displays incorrect data

Created 6/5/2003 12:10:35 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/25/2003 2:28:20 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002 SR1 January 2003 release

----- SUMMARY -----

With the Fleet Manager 2002 SR1 January 2003 release, it has been noted that Driver Scoring
reports does not displaying accurate driver scores.

----- MORE INFORMATION -----

Low Driving Error scores usually results in High Driver Scores. This was not the case and after
downloading trip data, some drivers received rather low scores compared to their apparent lack of
driving errors.

When recalculating/reapplying the driver score parameter values from the Driver Scoring parameters
tab, and regenerating a Driver Scoring report thereafter, the scores displays correctly.

----- CAUSE -----

Driver scoring was not calculated correctly during the data download process.

----- SOLUTION -----

This has been corrected in the patch supplied below.

Please download and install as follows:

Please note:

* IMPORTANT: Patch 1 to 7 should NOT be applied after this update (Patch 8) has been installed.

* This patch supercedes all patches released since the release of the Fleet Manager 2002 SR1
software in January 2003.

* This upgrade should be done on each computer where the above-mentioned version of the Fleet
Manager software is installed (even though previous patches have been installed).

* All Fleet Manager software and components should be shut down before attempting the upgrade as
described below.

* The update is only applied to the currently selected database.

1558
www.mixtelematics.com

1558
 1559

* In the case where the FM system has been set up as Client/Server, this patch should be applied to
the Server computer (where the Fleet Manager database is located) as well as to all Fleet Manager
Client computers, but for the client computers, the database upgrade should be canceled.

1. Download the following file, and save it to your hard disk: FleetManager2002SR1Patch8.exe (size:
12MB)

2. Please ensure that none of your Fleet Manager software or components are running.

3. To install the patch, double click the file (FleetManager2002SR1Patch8.exe).

4. The file will extract and overwrite some files in the Fleet Manager 2002 install directory, and will
then initiate a database upgrade. Please DO NOT interrupt the database upgrade at any stage.

5. After the database upgrade completed successfully, open your Fleet Manager software, and on
the Organisation properties go to the Driver Scoring tab.

6. Change one of the parameters on the driver scoring tab, then change it back to what it was, and
apply this "change" by clicking OK. You will be given the option to recalculate the scores. Select the
criteria you prefer - if you have a big database, rather select a certain date range to be recalculated
than selecting the All trips option. (The recalculation should be done for all trips downloaded since the
installation of Fleet Manager 2002 SR1 January 2003 release, until the day this patch was installed).

Please note: Recalculating the driver scores for a large amount of data could take quite some time.
DO NOT interrupt this procedure at any stage.

Any data downloaded into the database after the patch has been applied, will be correctly calculated
according to the Driver Scoring parameters.

----- STATUS -----

This has been fixed in the patch supplied in the SOLUTION section of this KBA, and will be correct in
the following release of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: Driver Scoring Report Reports FM2002SR1 FM2002 SR1

RELATED KBAs: 295, 299, 300, 307, 308, 309

1559
www.mixtelematics.com

1559
 1560
10.3.302 Knowledge Base Article 307

Article Number 307

Title Fleet Manager 2002 SR1 January 2003 release patches and updates

Created 6/11/2003 10:41:45 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/25/2003 2:27:13 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002 SR1 January 2003 release

----- SUMMARY -----

This KBA contains a summary of all patches and updates released after the Fleet Manager 2002 SR1
January 2003 release. All patches have been superceded by Patch 8 available from KBA#309 or the
link to download this patch in the Solution

The list of Knowledge base articles including links to patches and updates for the Fleet Manager 2002
SR1 software include the following: 295, 299, 300, 301, 303, 306.

The solution section of most of the above mentioned KBAs as well as the links they point to are
included below. In cases where more specific information is needed, please have a look at the
respective Knowledge base articles themselves.

To ensure all patches are installed, and fixes applied, follow the instructions as they are given below.

----- PATCHES -----

The updated install set for the FMDealer utility should be downloaded from the http://www.
mixtelematics.com website (from the Downloads\FM FM Accessories section).

Please note:

* IMPORTANT: Patch 1 to 7 should NOT be applied after this update (Patch 8) has been installed.

* This patch supercedes all patches released since the release of the Fleet Manager 2002 SR1
software in January 2003.

* This upgrade should be done on each computer where the above-mentioned version of the Fleet
Manager software is installed (even though previous patches have been installed).

* All Fleet Manager software and components should be shut down before attempting the upgrade as
described below.

* The update is only applied to the currently selected database.

* In the case where the FM system has been set up as Client/Server, this patch should be applied to
the Server computer (where the Fleet Manager database is located) as well as to all Fleet Manager
Client computers, but for the client computers, the database upgrade should be canceled.

1560
www.mixtelematics.com

1560
 1561

1. Download the following file, and save it to your hard disk: FleetManager2002SR1Patch8.exe (size:
12MB)

2. Please ensure that none of your Fleet Manager software or components are running.

3. To install the patch, double click the file (FleetManager2002SR1Patch8.exe).

4. The file will extract and overwrite some files in the Fleet Manager 2002 install directory, and will then
initiate a database upgrade. Please DO NOT interrupt the database upgrade at any stage.

KBA 295 - Data download stops at processing phase & KBA 299 - Downloaded data not showing in
database

After the database upgrade completed successfully, a quick download for each of the affected vehicles
should prompt the process phase of the unprocessed data to start, and all the information downloaded
thus far should appear in the database.

KBA 300 - Maximum SMS sent when active tracking enabled event becomes true

After you have completed this successfully, open the Fleet Manager client, and reload the vehicle
configuration(s) to the affected units (by reinitialising them in the software with the patch applied).

KBA 306 - Driver Scoring Reports displays incorrect data

a. After the database upgrade completed successfully, open your Fleet Manager software, and on the
Organisation properties go to the Driver Scoring tab.

b. Change one of the parameters on the driver scoring tab, then change it back to what it was, and
apply this "change" by clicking OK. You will be given the option to recalculate the scores. Select the
criteria you prefer - if you have a big database, rather select a certain date range to be recalculated
than selecting the All trips option. (The recalculation should be done for all trips downloaded since the
installation of Fleet Manager 2002 SR1 January 2003 release, until the day this patch was installed).

Please note: Recalculating the driver scores for a large amount of data could take quite some time. DO
NOT interrupt this procedure at any stage.

Any data downloaded into the database after the patch has been applied, will be correctly calculated
according to the Driver Scoring parameters.

KBA 308 - Pulse count incorrect on F4

After the patch has been applied successfully, please reload the vehicle configurations to the affected
vehicles.

----- UPDATES -----

The following updated install sets should be downloaded from the http://www.mixtelematics.com
website (from the Downloads\FM FM Accessories section):

* FM Dealer utility

* GSM Downloader

* SMS Processor

* Location Reports extension

If you have the Fleet Manager system set up as client/server, please have a look at KBA 303 - Updated
DCOM Client/Server installation procedure for an updated version of the Network Configurations guide,

1561
www.mixtelematics.com

1561
 1562

and an updated DCOM Client/Server installation procedure.

------------------------------------------------------------------------------

KEYWORDS: FM2002SR1 Fleet Manager 2002 SR1 FM2002 Patch Patches Update Updates

RELATED KBAs: 295, 299, 300, 306, 308, 309

1562
www.mixtelematics.com

1562
 1563
10.3.303 Knowledge Base Article 308

Article Number 308

Title Pulse count incorrect on F4

Created 6/18/2003 3:07:16 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/25/2003 2:23:15 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002 SR1 January 2003 release

· FM200 Plus unit

----- SUMMARY -----

When connecting a pulse input to F4 on the FM200 Plus unit, the wrong value is recorded.

----- MORE INFORMATION -----

This can be seen on something like the fuel consumption reports, where an EDM has been
connected to F4, and the values for the volume of fuel used on the Fuel Consumption Reports,
seems to be abnormally high.

----- CAUSE -----

This is cause by a miscalculation in the subtrip data per trip.

----- SOLUTION -----

This has been corrected and included in the patch included in this KBA. Download and install the
patch as described below:

Please note:

* IMPORTANT: Patch 1 to 7 should NOT be applied after this update (Patch 8) has been installed.

* This patch supercedes all patches released since the release of the Fleet Manager 2002 SR1
software in January 2003.

* This upgrade should be done on each computer where the above-mentioned version of the Fleet
Manager software is installed (even though previous patches have been installed).

* All Fleet Manager software and components should be shut down before attempting the upgrade
as described below.

* The update is only applied to the currently selected database.

* In the case where the FM system has been set up as Client/Server, this patch should be applied
to the Server computer (where the Fleet Manager database is located) as well as to all Fleet

1563
www.mixtelematics.com

1563
 1564

Manager Client computers, but for the client computers, the database upgrade should be canceled.

1. Download the following file, and save it to your hard disk: FleetManager2002SR1Patch8.exe
(size: 12MB)

2. Please ensure that none of your Fleet Manager software or components are running.

3. To install the patch, double click the file (FleetManager2002SR1Patch8.exe).

4. The file will extract and overwrite some files in the Fleet Manager 2002 install directory, and will
then initiate a database upgrade. Please DO NOT interrupt the database upgrade at any stage.

5. After the patch has been applied successfully, please reload the vehicle configurations to the
affected vehicles.

Please note: This patch will unfortunately not correct existing data, but will ensure the correct data
is recorded after the patch has been applied and the vehicle configuration reloaded.

----- STATUS -----

This has been corrected and included in the patch supplied, as well as the next version of the Fleet
Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM200 Plus FM200Plus F4 Frequency Pulse Count EDM Fuel

RELATED KBAs: 295, 299, 300, 306, 307, 309

1564
www.mixtelematics.com

1564
 1565
10.3.304 Knowledge Base Article 309

Article Number 309

Title Fleet Manager 2002 SR1 Patch 8

Created 7/23/2003 3:11:52 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/25/2003 2:24:43 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002 SR1 only

----- SUMMARY -----

The Fleet Manager 2002 SR1 Patch 8 was created to include some improvements to the Fleet
Manager software, as well as all patches since the Fleet Manager 2002 SR1 software was released in
January 2003.

This document describes all improvements and other changes included in the patch supplied with this
Knowledge base article.

----- WHAT'S NEW -----

Firmware

A new version of the FMDealer is released in assosiation with this patch to enable support for the
following:

1. FM Impact sensor

2. Other FM related hardware devices

3. General optimisations for GPS and FMKeypad devices

It is recommended to take advantage of the above improvements by updating the device drivers in
any FM200 Plus and related units.

Software

Software support for the following has been included:

1. FM Impact Sensor

Software support for the FM Impact Sensor includes new devices, parameters and events created
specifically for the FM Impact Sensor. The Material Handling extension is available to maintain and
report on this data.

2. Cold Chain Monitoring

Devices and events have been included in the database for the monitoring of exceptions to a Cold

1565
www.mixtelematics.com

1565
 1566

Chain system.

Devices included are: Fridge Temperature, Fridge Door closed and Cooling Unit running.

Events included are: Cooling unit switched off while driving, Cooling unit not efficient and Fridge door
open too long and Cold chain broken.

----- PATCHES -----

The following knowledge base articles have been addressed and all patches released previously
updated to point to patch 8. For specific information on one of these issues, please have a look at the
specific knowledgae base article.

KBA 295 - Data download stops at processing phase

KBA 299 - Downloaded data not showing in database

KBA 300 - Maximum SMS sent when active tracking enabled event becomes true

KBA 301 - Ensuring successful remote vehicle configuration upload

KBA 303 - Updated DCOM Client/Server installation procedure

KBA 306 - Driver Scoring Reports displays incorrect data

KBA 308 - Pulse count incorrect on F4

Other fixes or improvements made include the following:

* database upgrades that initially reported Invalid use of null accessing parameters

* cancelling report generation could cause a code loop

* calibration for high resolution analogue lines were not displayed correcly on the Vehicle
Configuration Report

* elimination of excess GPS points when a vehicle is stationary

----- SOLUTION -----

The updated install set for the FMDealer utility should be downloaded from the http://www.
mixtelematics.com website (from the Downloads\FM FM Accessories section).

Please note:

* IMPORTANT: Patch 1 to 7 should NOT be applied after this update (Patch 8) has been installed.

* This patch supercedes all patches released since the release of the Fleet Manager 2002 SR1
software in January 2003.

* This upgrade should be done on each computer where the above-mentioned version of the Fleet
Manager software is installed (even though previous patches have been installed).

* All Fleet Manager software and components should be shut down before attempting the upgrade as
described below.

* The update is only applied to the currently selected database.

* In the case where the FM system has been set up as Client/Server, this patch should be applied to

1566
www.mixtelematics.com

1566
 1567

the Server computer (where the Fleet Manager database is located) as well as to all Fleet Manager
Client computers, but for the client computers, the database upgrade should be canceled.

1. Download the following file, and save it to your hard disk: FleetManager2002SR1Patch8.exe (size:
12MB)

2. Please ensure that none of your Fleet Manager software or components are running.

3. To install the patch, double click the file (FleetManager2002SR1Patch8.exe).

4. The file will extract and overwrite some files in the Fleet Manager 2002 install directory, and will
then initiate a database upgrade. Please DO NOT interrupt the database upgrade at any stage.

After the upgrade completed successfully, refer to the appropriate KBA (see PATCHES section above)
to correct specific issues (if necessary).

----- STATUS -----

KBA under construction - status will be updated after patch and FMDealer has been released.

------------------------------------------------------------------------------

KEYWORDS: FM2002 SR1 FM2002SR1 Patch

RELATED KBAs: 295, 299, 300, 306, 307, 308

1567
www.mixtelematics.com

1567
 1568
10.3.305 Knowledge Base Article 310

Article Number 310

Title SMS Processor terminates abnormally

Created 7/30/2003 3:24:43 PM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 7/30/2003 3:25:35 PM

Last Modified By Steve Crane (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager SMS Processor (all versions)

----- SUMMARY -----

The SMS Processor may terminate abnormally when the user requests to exit the program.

----- MORE INFORMATION -----

When the user clicks the Exit button or selects Exit from the system tray menu the program may
terminate abnormally and display an error message.

----- CAUSE -----

The abnormal termination occurs when the program is exited while the processor is running. There is
no danger of data being damaged by this termination.

----- SOLUTION -----

To avoid the problem the user should first stop the processor by clicking the Stop button or selecting
Stop from the system tray menu. The program can then be exited after a slight pause. If the user stops
the processor and then immediately exits the problem may still occur. A pause of 1 second should be
sufficient to ensure that the program terminates normally.

----- STATUS -----

This issue is under investigation.

------------------------------------------------------------------------------

KEYWORDS: SMS PROCESSOR GPF

1568
www.mixtelematics.com

1568
 1569
10.3.306 Knowledge Base Article 312

Article Number 312

Title F4/I8 input on the FM200 Plus unit

Created 9/2/2003 11:01:08 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 9/2/2003 12:03:44 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 Plus unit

· Fleet Manager 2002 SR1

----- SUMMARY -----

It is not possible to connect to all 8 digital/analogue inputs in the above version of the Fleet Manager
software.

----- MORE INFORMATION -----

The FM200 Plus unit allows 4 frequency inputs, and 8 digital/analogue inputs to be connected, but of
the 8 available, it is only possible to connect to 7 in the Fleet Manager software version mentioned
above.

The fourth frequency line (F4) is shared with the eigth digital/analogue line (I8). Firmware and
hardware wise it is possible to connect to I8, but in the current version of the software, it is not yet
possible.

----- CAUSE -----

This is by design in the software.

----- SOLUTION -----

Until the I8 input is available in the Fleet Manager software, it is advised F4 be used on this line, and in
the case where digital/analogue devices needs to be connected, the currently 7 available input lines (I1
to I7) be used.

----- STATUS -----

This is by design and will be changed in a future version of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM200 Plus I8/F4 F4 I8 input FM2002SR1 SR1 Fleet Manager 2002

1569
www.mixtelematics.com

1569
 1570
10.3.307 Knowledge Base Article 313

Article Number 313

Title HOW TO correct a date jump on an FM unit

Created 9/11/2003 2:59:55 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 5/10/2007 8:48:00 AM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM200 unit

· FM200 Plus series unit

· Fleet Manager 2002, all versions

· Fleet Manager Professional 8, all versions

----- SUMMARY -----

This KBA serves to describe a procedure of correcting a date jump problem on a FM200 or FM200 Plus.

Date jump problems do not occur that often, but when it occurs, it would be wise to follow the procedure
below to ensure minimum data loss, and the date/time is set right on the FM unit to ensure all future
data is recorded with the correct date/time.

----- CAUSE -----

The cause of a date jump on a FM unit could be one of many, though if the latest device drivers is
loaded, it is mostly limited to the date/time accidently set incorrectly. Other than that, outdated device
drivers in a unit is the main cause for date jumps occurring.

----- SOLUTION -----

Please find the procedure to reset the units & database to contain the correct date/time setting below.
Please note that unfortunately some trips may be lost, as they have been recorded at a "future" date:

(Before you get going - make sure you download and install the latest version of the FM Dealer from
the http://www.mixtelematics.com website.)

1. Ensure you have the latest software version & components installed (you can compare what you
have with what is available from the http://www.mixtelematics.com website).

2. Do a full download of all the vehicles, to ensure that you have as much data as posssible in the
database

3. Clear data in the database from *NOW* (after the latest download has been done), to a date later
than the "current" latest download date (i.e. if this is 01/05/2005, clear data until the year 2006). (To
clear data, go to the Organisation Properties -> Advanced Tab)

1570
www.mixtelematics.com

1570
 1571

4. Clear the FM unit itself (this applies to all FM units exhibiting this problem) - this is necessary, as the
incorrect data is stored on the unit, and if you download data from the unit even after the unit date has
been corrected, the later date will be displayed, until it is overwritten. (To clear the FM Unit, use the
functionality provided in the FM Dealer).

5. Execute the SWAP UNIT functionality in the database for each unit that has been cleared. (SWAP
UNIT can be executed from vehicle properties in the FM Software).

6. Reload the vehicle configuration for each unit.

7. Upload the latest device drivers from the FM Dealer.

8. Set the date/time to the correct date/time.

After you have done this, the units date/time will be set correctly & displayed correctly when
downloading into the database. Please note, that date jumps should not occur if you have these latest
device drivers loaded to the units.

----- STATUS -----

Date jumps should not occur if the latest device drivers have been loaded to the FM units.

------------------------------------------------------------------------------

KEYWORDS: HOWTO Date Jump Wrong date FM200 Plus FM200Plus Locator Communicator

1571
www.mixtelematics.com

1571
 1572
10.3.308 Knowledge Base Article 314

Article Number 314

Title Tips when using the Nokia D211

Created 11/7/2003 2:25:18 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/7/2003 3:11:18 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Nokia D211

· Fleet Manager GSM Downloader

· Fleet Manager SMS Processor

----- SUMMARY -----

This KBA contains information to ensure optimum performance of the Nokia D211 with the Fleet
Manager software and components.

----- MORE INFORMATION -----

If the GSM Downloader is used in conjunction with the Nokia D211 modem, and it is not behaving as
expected (i.e. downloading and uploading data as is to be expected), it could be necessary to update
your Nokia modem driver. Please find more information on this in the Solution section of this KBA.

When using the Nokia D211 in conjunction with the Fleet Manager SMS Processor, it is important to
keep the following in mind: due to the way Nokia implemented the AT commands for SMS messaging
in the Nokia D211, it is possible to send messages from the modem, but no messages can be
received (i.e. no messages or delivery reports). Therefore, when using the Nokia D211 in conjunction
with the Fleet Manager SMS Processor, it will also only be able to send messages, but none will be
received. If use of the SMS Processor is required (as described above), it is also necessary to update
the modem driver as per the Solution section below.

----- CAUSE -----

Any limitations in the Nokia D211 modem is due to its design by Nokia. The best way to work around
any of these is to ensure the latest available modem drivers are installed.

----- SOLUTION -----

Install the latest available drivers for the Nokia D211 modem. These can be obtained from your
modem supplier, or downloaded from the Nokia website. (Currently the latest available modem drivers
are BETA drivers, but have been tested, and works with the FM applications).

------------------------------------------------------------------------------

KEYWORDS: Nokia D211 NokiaD211 modem GSM Downloader SMS Processor

1572
www.mixtelematics.com

1572
 1573
10.3.309 Knowledge Base Article 315

Article Number 315

Title FM200 Plus calibration & GPS

Created 11/27/2003 3:46:54 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 12/9/2003 2:28:55 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 Plus unit

----- SUMMARY -----

This KBA describes what procedure to follow to ensure successful calibration & GPS setup with the
FM200 Plus unit.

----- MORE INFORMATION -----

Calibration

The FM200 Plus unit contains four possible RPM/Speed input signal options (listed below): big sine
wave, small sine wave, big square wave, small square wave.

When a new unit is received from the factory it is normally set to small sine wave. In most
circumstances this should work, but in some cases it is not possible to calibrate using this setting (i.
e. after calibration has been completed, the unit is still not calibrated, or frequency spikes are
experienced, or speed/rpm seems to be fine until a certain threshhold is reached -i.e. RPM and
speed seems to be calibrated fine until RPM/speed frequency reaches a certain value). This can be
caused by the signal being too weak for the input or by the speed voltage exceeding the hardware
capability of the signal type selected - i.e. the signal type not being appropriate for the jumper
setting.

The best option is to change the signal handling capability of the unit by first changing the jumper
settings to Small Square Wave, and if this is not successful, consider using the remaining settings
in the following order: Large Square Wave, Large Sine Wave, Small Sine Wave.

In the case where all possible jumper settings have been considered, and the calibration procedure
(as described in the FM documentation), followed correctly, and the unit cannot be calibrated
correctly, it is advisable to contact your local support team for further investigation/action to be
taken.

GPS connection

With the FM200 Plus unit it is possible to connect the GPS unit directly to the FM200 Plus unit
without using a GPS interface cable (as is needed with the FM200 unit). This can be done, by
applying the jumper settings as per the documentation.

If the jumper settings are correct, and the GPS unit is connected to the FM200 Plus unit directly, but
does not seem to work, test this with a GPS diagnostics plug, and if there is no response (i.e. GPS

1573
www.mixtelematics.com

1573
 1574

not working), set the jumper settings on F3 back to the factory default, and use a GPS Interface
cable to connect the FM200 Plus to the GPS unit. If the GPS unit will only work with the GPS
Interface cable, and not when it has been connected to the FM200 Plus unit directly, please contact
your local support team for further support in the matter.

----- STATUS -----

Circuit improvements are being implemented to ease the installation process of the FM200 Plus
unit, and ensure optimum performance of the unit.

------------------------------------------------------------------------------

KEYWORDS: FM200 Plus FM200Plus Calibration Speed RPM Jumper Settings GPS

1574
www.mixtelematics.com

1574
 1575
10.3.310 Knowledge Base Article 316

Article Number 316

Title GSM Downloader on faster computers

Created 12/1/2003 6:19:18 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 12/2/2003 2:35:09 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· GSMDl.exe version 7.02.0056

----- SUMMARY -----

This KBA describes an issue which may arise when running this specific version of the GSM
Downloader on faster computers.

----- MORE INFORMATION -----

When running this version of the GSM Downloader on faster computers, an intermittent problem
could occur where downloading fails with the following error:

An unexpected error has occurred in CallDMI - 53 (35): File not found (Line 18800)

----- CAUSE -----

This is caused by the fact that the GSM Downloader uses certain files during the download process,
but due to the speed of the computer, these have not yet been released from the DMI process by the
time the GSM Downloader tries to access them.

----- SOLUTION -----

Download and install the following fix as described below:

1. Download the follow update: GSMDl.exe (868KB, dated 1/12/2003).

2. Close all FM related applications

3. Copy/Save the file downloaded above to your GSM Downloader install directory and let this file
overwrite your current GSMDL.exe file.

----- STATUS -----

This has been catered for in the update supplied with this KBA, and will be included in the next full
release version of the GSM Downloader.

------------------------------------------------------------------------------

KEYWORDS: GSM Downloader callDMI "File not found" GSMDL.exe

1575
www.mixtelematics.com

1575
 1576
10.3.311 Knowledge Base Article 317

Article Number 317

Title Interval data on the FM200 and FM200 Plus

Created 12/4/2003 9:38:06 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 2/24/2004 3:10:50 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 and FM200 Plus units

----- SUMMARY -----

This article describes the availability of interval data on FM200 and FM200 Plus units.

----- MORE INFORMATION -----

Interval data is available on the following lines for the FM200 as well as the FM200 Plus units:

The first three frequency lines (F1, F2, F3), and the first four analogue lines (I1, I2, I3, I4).

------------------------------------------------------------------------------

KEYWORDS: Tacho data Interval FM200 FM200 Plus FM200Plus

1576
www.mixtelematics.com

1576
 1577
10.3.312 Knowledge Base Article 318

Article Number 318

Title Client appears to hang when saving tacho graph

Created 1/15/2004 11:44:52 AM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 1/15/2004 11:44:52 AM

Last Modified By Steve Crane (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Professional 2002

· Fleet Manager Professional 8

----- SUMMARY -----

When saving a tacho graph the Fleet Manager client may appear to hang.

----- MORE INFORMATION -----

A large amount of data is required to plot a tacho graph and this creates an accordingly large *.vtc
file when saved.

If a tacho graph is generated for a long period it may take several minutes to complete the save,
during which an hourglass mouse cursor is displayed and the client appears to be hanging.

----- CAUSE -----

Attempting to save a tacho graph for a lengthy period.

----- SOLUTION -----

Refrain from viewing and saving tacho graphs for long periods. We would suggest that you restrict
the period being viewed to no more than one hour.

------------------------------------------------------------------------------

KEYWORDS: FM2002 FM8

1577
www.mixtelematics.com

1577
 1578
10.3.313 Knowledge Base Article 319

Article Number 319

Title FM Dealer Utility versions

Created 2/12/2004 9:41:32 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 2/12/2004 3:22:27 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Dealer Utility version 2.10.1.0

· FM Dealer Utility version 2.10.2.0

----- SUMMARY -----

This KBA serves to clarify any confusion that might exist with regards to the two FM Dealer utility
versions mentioned above.

----- MORE INFORMATION -----

At the time of writing this KBA, the most current version of the FM Dealer utility is 2.10.1.0. This is also
the version available from the download section of www.cidev.com website, and contains the latest set
of device drivers to be used for any purposes.

A change was made for factory-production purposes only, which resulted in version 2.10.2.0, and
therefore any new units received from production may display this as the version of FM Dealer used to
load device drivers. This is NOT incorrect, and does NOT include any different device drivers
compared to those supplied with FM Dealer version 2.10.1.0.

In the vehicle, version 2.10.1.0 and 2.10.2.0 have the same functionality.

The client should use version 2.10.1.0 with confidence.

----- STATUS -----

The FM Dealer version available (and visible) on the www.cidev.com website is always the latest FM
Dealer to be used, and as per above comments, at time of writing this is FM Dealer version 2.10.1.0.

------------------------------------------------------------------------------

KEYWORDS: FM Dealer FMDealer Utility Device Drivers DDR DDX DDRs DDXs

1578
www.mixtelematics.com

1578
 1579
10.3.314 Knowledge Base Article 320

Article Number 320

Title FM and Siemens MC35i modem

Created 3/10/2004 3:39:53 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 3/10/2004 4:13:49 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Fleet Manager 2002 SR1

----- SUMMARY -----

This KBA includes an update for the SMS Processor to include support for the Siemens MC35i
modem.

----- MORE INFORMATION -----

When using the Siemens MC35i modem with the Fleet Manager 2002 SR1 and related SMS
Processor software, communications is not possible, as support for this modem was not included in
this version of the SMS Processor.

----- CAUSE -----

The SMS Processor recognises a modem by the model information available. The Siemens MC35i
modem was only developed after the release of this version of the SMS Processor, and consequently
this modem was not supported.

----- SOLUTION -----

The update available below includes support for this modem, and all other known modems.

Please download and install as described below:

1. Stop all FM related programs and components

2. Download the following update: SMSComm.dll version 1.2.17.6 (or later).

3. Search for the SMSComm.dll file on your computer (by default this will be in the C:\Program Files
\Fleet Manager SMS Processor folder. Replace this file with the downloaded one.

This should enable support for the Siemens MC35i modem with the FM2002 SR1 and related SMS
Processor software.

----- STATUS -----

Support for the Siemens 35i modem has been included in the update provided, as well as in the next
release of the Fleet Manager SMS Processor software (to be released with Fleet Manager 8 software).

1579
www.mixtelematics.com

1579
 1580

------------------------------------------------------------------------------

KEYWORDS: FM200 FM200 Plus Siemens MC35i modem SMS Processor

1580
www.mixtelematics.com

1580
 1581
10.3.315 Knowledge Base Article 321

Article
321
Number

Title FM unit current consumption

Created 3/23/2004 1:20:53 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 3/26/2004 8:27:59 AM

Last Modified
Ronel Spies (MiX Telematics - Stellenbosch)
By

Details ----- APPLIES TO ----

· FM200 Plus

· FM200 Communicator

· FM200 Locator

----- SUMMARY -----

This KBA contains information with regards to the current consumption of the FM 200 Plus units available

----- MORE INFORMATION -----

Unit type Operating mode Out of trip mode Sleep mode

FM200 Plus 14V – 155mA 14V – 35mA 14V – 28mA

28V – 88mA 28V – 27mA 28V – 22mA

FM200 Communicator (quick charge battery) 14V – 110mA 14V – 44mA

14V – 392mA 28V – 72mA 28V – 30mA

28V – 237mA

(trickle charge battery)

14V – 220mA

28V – 131mA

FM200 Locator 14V – 184mA 14V – 67mA 14V – 31mA

1581
www.mixtelematics.com

1581
 1582

28V – 129mA 28V – 61mA 28V – 22mA

------------------------------------------------------------------------------

KEYWORDS: Fleet Manager 200 Plus FM200Plus FM200 Plus FM Locator FM Communicator

1582
www.mixtelematics.com

1582
 1583
10.3.316 Knowledge Base Article 322

Article Number 322

Title FM GPRS Gateway

Created 3/24/2004 3:35:08 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 3/25/2004 8:33:53 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Professional, version 8

· GPRS

----- SUMMARY -----

The FM GPRS Gateway allows your FM units to connect to your GPRS Service, without requiring a
fixed public IP address.

----- MORE INFORMATION -----

The gateway is of interest to dealers and clients wishing to use the new GPRS functionality in the FM
system.

In essence, the gateway allows your FM units to connect to your GPRS Service, without the Service
computer requiring a fixed public IP address.

The GPRS Service as well as all GPRS enabled vehicles must be set up (configured) to point to the
gateway’s IP address.

Please refer to the FM Fleet Manager Documentation on your Fleet Manager Office CD for detailed
setup instructions. (Documentation to be found in the Comms Suite - GPRS Service section).

----- SOLUTION -----

Please note, to use the gateway, you will require the following:

1. A valid current FM Upgrade+ registration.

You must have a current, valid FM Upgrade+ registration code to make use of the FM GPRS Gateway.

2. You require a port open for UDP

The GPRS Service uses the User Datagram Protocol (UDP) to communicate with the Fleet Manager
units. The GPRS Service must be able to accept inbound and outbound UDP connections on a
specified port. By default the GPRS service will use port 2000, but you can configure it to use any port.
Please speak to your Internet Service Provider to obtain a suitable port number for use with the GPRS
Service and to ensure that their firewall is open for in and outbound UDP connections on that port.

The FM GPRS Gateway is located at IP address 196.38.36.181 port 2000. (These are the default

1583
www.mixtelematics.com

1583
 1584

values set by the FM Communications Suite, and can be used as is).

------------------------------------------------------------------------------

KEYWORDS: FM GPRS Gateway IP address UDP

1584
www.mixtelematics.com

1584
 1585
10.3.317 Knowledge Base Article 323

Article Number 323

Title Optimising location events

Created 4/16/2004 2:48:22 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 4/20/2004 9:09:56 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Fleet Manager 2002 SR1

----- SUMMARY -----

This KBA describes optimising the use of Locations when setting up events.

----- MORE INFORMATION -----

When creating events and combining speed and location as trigger values, the following should be
noted:

1. There is a limit to the number of triggers allowed per event. The limit is imposed by the size of the
triggers passed to the unit, where each 'trigger' is a different 'size' to the unit. The config can handle
approximately 16 location/speed combinations before this limit is reached.

2. The number of points per location has an effect on the event and consequently the config size. Try
reducing the number of polygon points per location, or use a circular/rectangular locations instead of
polygons.

3. If speed has to differ per location, consider using event per speed range.

If multiple locations are used in events, it is important to note the above to ensure successfull
configuration transfer.

----- SOLUTION -----

Listed below is an example of what is said in (3) above:

Instead of having an event where trigger values are specified as follows:

EVENT A:

(SPEED > X AND

At Location AAA) OR

(SPEED > X AND

At Location BBB) OR

1585
www.mixtelematics.com

1585
 1586

(SPEED > Y AND

At Location CCC)

Rather consider breaking the event up into two separate events as illustrated below:

EVENT A:

SPEED > X AND

(At Location AAA OR

At Location BBB)

EVENT B:

SPEED > Y AND

At Location CCC

Having an event broken down into smaller units (as illustrated above), will allow for the more efficient
running of the events.

----- STATUS -----

This is by design.

------------------------------------------------------------------------------

KEYWORDS: Locations speed events FM2002 SR1 FM2002SR1 Fleet Manager speed

1586
www.mixtelematics.com

1586
 1587
10.3.318 Knowledge Base Article 324

Article Number 324

Title One FM Upgrade+ NFR package per GPRS Gateway registration

Created 5/19/2004 1:42:29 PM

Created By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Last Modified 5/19/2004 2:05:57 PM

Last Modified By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Professional 8

· Fleet Manager Communications Suite (GPRS)

· Fleet Manager GPRS Gateway

----- SUMMARY -----

An FM Upgrade+ NFR package can only be used by one company on the GPRS gateway.

----- MORE INFORMATION -----

When setting up a GPRS Service from the Fleet Manager Professional 8 (or later) CD, you are
required to supply an FM Upgrade Plus package number. This is used to register your company
against the GPRS Gateway (The global routing system for all FM GPRS data.), allowing you to
transfer messages, events and trip data via the GPRS system.

However, once an FM Upgrade Plus package number has been used by one company, it can not be
re-used by another company.

----- SOLUTION -----

Dealers should use their own NFR package number for running their own fleet on the gateway.

Dealers should register additional NFR packages (in the customer's name) for customer trials using
the GPRS Gateway.

------------------------------------------------------------------------------

KEYWORDS: GPRS Gateway Upgrade Plus Upgrade+ Registration

1587
www.mixtelematics.com

1587
 1588
10.3.319 Knowledge Base Article 325

Article Number 325

Title Configuring FM GPRS to use the GPRS Gateway

Created 5/20/2004 9:39:06 AM

Created By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Last Modified 10/22/2004 8:46:08 AM

Last Modified By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Dealers installing FM GPRS Service for a client.

· Fleet Manager Professional 8.

· Fleet Manager GPRS Gateway.

----- SUMMARY -----

Many dealers pre-configure a client database in-house, before installing it at the client's site. This is
perfectly acceptable, but requires a detailed understanding of how the GPRS Gateway registers FM
Upgrade Plus registration codes.

Not understanding will cause problems for the installer.

----- SYMPTOMS -----

Many dealers report problems after moving the database to the client site. Whilst GPRS worked on the
pre-configured system (in-house), it stops working once it is moved to the client site.

----- MORE INFORMATION -----

To understand why this happens, one must understand how the GPRS Gateway registers FM Upgrade
Plus registration codes, and why:

----- GATEWAY REGISTRATION -----

The GPRS Gateway is a world-wide service, and must ensure that no two companies use the same
Company ID (Database ID). This is for data routing integrity and security. So, the Gateway always
forces companies to connect with unique Company ID's.

----- FOLLOW THIS PROCEDURE -----

So, if you wish to pre-configure a client's database before installing it at their premises, please follow
this procedure, to ensure minimal problems:

In-House (At your office):

NB: Always use the latest release of FM Professional (v8 or later).

1) Register a new FM Upgrade Plus Package for the client in the client's name. Do not use your own

1588
www.mixtelematics.com

1588
 1589

NFR package.

2) Using FM Pro 8, create the database with a unique Company ID.

3) Set up the GPRS Service to connect to the GPRS Gateway, making sure to use the client's Upgrade
Plus package number.

4) Create the vehicles in the database, set them up and load configurations to all.

5) Test the system to ensure it works.

6) NB: Now stop the GPRS Service.

7) Back-up the database, using the FM Administrator.

8) Take the database to the client site...

(From this point onwards, you should not re-start your in-house GPRS Service again - This could
cause loss of data at the client site.)

Client's Site:

9) NB: Restore the database at the client site, but do not change the Company ID when prompted. (If
you change the Company ID, the Gateway will think it is a new company, and will not allow it to use the
same FM Upgrade Plus package number anymore. If this happens, please contact MiX Telematics
support, who can reset the registartion details)

10) Install the GPRS Service and connect to the Gateway using the same (client's) Upgrade Plus
package number.

11) All vehicles should now connect to this (restored) database.

12) Check log files to ensure system works.

------------------------------------------------------------------------------

KEYWORDS: GPRS Gateway GPRSGateway Service FM8 Fleet Manager Professional 8

1589
www.mixtelematics.com

1589
 1590
10.3.320 Knowledge Base Article 326

Article Number 326

Title FM Client aborts after unloading extension

Created 5/21/2004 9:45:30 AM

Created By Steve Crane (MiX Telematics - Stellenbosch)

Last Modified 7/18/2006 3:13:34 PM

Last Modified By Warren Tieling (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· All extension capable Fleet Manager versions up to, and including Fleet Manager 8.

----- SUMMARY -----

If you unload an extension while it is processing the FM Client will abort.

----- MORE INFORMATION -----

After starting a long running report extract from an extension, it is possible to switch to the extension
manager and unload the extension. When the client subsequently tries to communicate with the
extension a fatal error occurs and the client aborts.

----- SOLUTION -----

Do not unload any extensions while reports are being processed.

----- STATUS -----

This will be corrected for later versions of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM client software fleet manager extension

1590
www.mixtelematics.com

1590
 1591
10.3.321 Knowledge Base Article 327

Article Number 327

Title Fleet Manager Trailer ID Odometer

Created 5/26/2004 3:33:06 PM

Created By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Last Modified 5/26/2004 3:47:20 PM

Last Modified By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Trailer ID

----- SUMMARY -----

Trailers that are not disconnected regularly, display old odometer readings.

----- MORE INFORMATION -----

When using the FM Trailer ID, most clients are interested in the odometer reading of the trailer!

Whilst the Fleet Manager System accurately logs the odometer of each trailer continuously, the
odometer reading is only updated (in the FM200 Plus) when the trailer is disconnected from the horse.

It is therefore important that a trailer is disconnected from its horse, from time to time.

However, if this is not possible, this work-around should be followed:

----- SOLUTION -----

Install the FM Trailer ID in the standard manner.

Before uploading the configurations to the vehicles, modify the Event Definitions of Trailer A,B,C & D to
include "In Trip (Drive)" = TRUE.

This change will cause the Trailer to virtually "disconnect" after every trip, thus ending the Detailed
Event, and storing the odometer.

----- HOW TO DO THIS -----

From the FM Client, click on the "Event Definitions" button. Click the "Events" tab and change the four
(4) Trailer ID events to include "In Trip (Drive) = TRUE". (Just click on the first empty line, to add the new
condition).

It should look like this:

(NOT(Trailer ID = 0) AND (In Trip Drive = TRUE))

Now, upload a new configuration to all the affected vehicles.

------------------------------------------------------------------------------

1591
www.mixtelematics.com

1591
 1592

KEYWORDS: Trailer TrailerID Odometer

1592
www.mixtelematics.com

1592
 1593
10.3.322 Knowledge Base Article 328

Article Number 328

Title The Significance of the Company ID in the FM system

Created 6/4/2004 8:39:20 AM

Created By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Last Modified 6/4/2004 8:45:46 AM

Last Modified By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· The significance of the Company ID in the FM system.

----- SUMMARY -----

The company id's primary function is to validate data transfer between the company database and the
vehicles. It ensures that company A can not download vehicles from company B, and vice versa!

----- MORE INFORMATION -----

The company id is automatically generated at installation and is stored in the database. It can be
edited through the Organisation Properties dialog in the FM software.

----- CONFIGURATION UPLOAD -----

When a configuration is uploaded to a vehicle, the company id is transferred in the process. It forms
part of the vehicle configuration data block, and is updated in the vehicle whenever a configuration is
uploaded.

----- DECT & GPRS -----

The exception is DECT & GPRS. When uploading a Config using these transports, the upload is not
performed if the company id in the vehicle is different from the company id in the database. This is
again for security reasons. You must, therefore, use either a Code Plug (physical access) or a GSM
Datacall (phone number) to change the company id of a vehicle.

----- FM GPRS GATEWAY -----

The FM GPRS Gateway uses the company id to route data between a company's database and its
vehicles. It is therefore essential that the company id's in the vehicles match the company id in the
database, when using the GPRS Gateway.

------------------------------------------------------------------------------

KEYWORDS: company id companyid gprs gateway config upload dect

1593
www.mixtelematics.com

1593
 1594
10.3.323 Knowledge Base Article 329

Article Number 329

Title FM 200 Communicator and GSM data download

Created 6/21/2004 12:51:00 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/22/2004 12:58:01 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 Communicator units

----- SUMMARY -----

In some cases it is not possible to download data via a GSM data call from some FM200
Communicator units. The call is answered, but dropped immediately and the GSM Downloader seems
to hang at the verifying Vehicle ID stage.

----- MORE INFORMATION -----

As per the description in the SUMMARY section of this KBA, the unit will answer the call, but drops it
immediately. The end result is that the GSM Downloader will show that the unit is connected and it will
start verifying Vehicle ID and then disconnects with GSM might have exited the GSM Coverage area
error.

----- CAUSE -----

This is caused by a modem setting that was set to a non-default value on some of the modems by the
GSM modem manufacturer.

----- SOLUTION -----

In order to correct this issue an AT command has been added to the modem setup routine that will
restore factory default settings.

This new setting has been included in the latest version of the Fleet Manager Device Drivers available
from the latest version of the FM Dealer Utility.

So if this behaviour is experienced, download and install the latest version of the FM Dealer, and
upload the latest device drivers included in this version of the FMDealer Utility to the FM Communicator
unit.

The latest version of the FMDealer Utility is available for download from the www.FMfm.com. website
under the Service -> Downloads -> Dealer Utility -> Fleet Manager Professional 8 section.

Download and install this version of the FM Dealer Utility (after uninstalling any previous versions of
this utility), and upload the device drivers included in this version of the FM Dealer Utility to the FM 200
Communicator where behaviour described in the DETAILED section of this KBA is occurring.

----- STATUS -----

1594
www.mixtelematics.com

1594
 1595

This is problem is overcome by uploading the device drivers from the latest FMDealer Utility available
(as per SOLUTIONS section of this KBA).

------------------------------------------------------------------------------

KEYWORDS: FM 200 Communicator GSM Data call FMDealer FM Dealer Utility

1595
www.mixtelematics.com

1595
 1596
10.3.324 Knowledge Base Article 330

Article Number 330

Title Controlling device power by Relay

Created 7/14/2004 12:44:13 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 7/21/2004 12:20:01 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Professional 8

----- SUMMARY -----

When controlling power of your modem or other device with the relay, it may not be powered after
loading Device Drivers to the FM unit, or the unit has been reset.

----- MORE INFORMATION -----

When the relay has been selected to control the power for a specific device, the device may not
function. After loading a configuration, the Relay will be left in the state before the configuration was
loaded. Once the unit is reset (which occurs when loading device drivers), the relay will not be
powered up again.

----- CAUSE -----

The configuration needed to turn the Relay drives on is not included unless the option to turn the
power off is configured.

----- SOLUTION -----

This will be changed in a following release of the Fleet Manager software, but to work around this
feature in the meantime, please do the following:

1. Go to the device properties of one of the devices that are powered by the Relay.

2. Go to the Power Settings tab for this device.

3. Select the option 'Enable automatic shutdown'. Set the number of hours to a value of 10000
hours, which is longer than 1 year.

----- STATUS -----

This will be changed in a following release of the Fleet Manager software. In the meantime use the
workaround described in the SOLUTION section of this KBA.

------------------------------------------------------------------------

KEYWORDS: FM200 Plus GSM Modem Device Power Control Relay

1596
www.mixtelematics.com

1596
 1597
10.3.325 Knowledge Base Article 331

Article Number 331

Title Loading FM Terminal scripts on Fleet Manager 8

Created 7/23/2004 9:47:30 AM

Created By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Last Modified 7/23/2004 9:49:20 AM

Last Modified By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Loading FM Terminal scripts on Fleet Manager 8.

----- SUMMARY -----

When loading a FM Terminal script from FM 8, this error is reported:

"An error occurred while compiling the FM Terminal Menu. Please check your configuration."

----- MORE INFORMATION -----

It is important, when this message is received, to view the "script.lst" (using Notepad), which can
usually be found under: "C:\Program Files\Common Files\Fleet Manager\FMTerminal"

This error may be reported: "Error 18 - FMTerminal memory capacity of 20480 exceeded".

----- CAUSE -----

This is caused by the FM Terminal not having enough memory to load the selected script and
language files.

----- SOLUTION -----

Unfortunately, there is not currently a permanent solution available, but these work-arounds can be
used:

1) Choose "English" as the second language. "English" is the smallest language file and should
reduce the total size of the scrip.

2) Load "_mlb", rather than "_alb" scripts, if possible. They are also smaller.

3) Select as few as possible events to display on the FM Terminal (like overspeeding etc.). This can
be set on the individual "Events" tabs under Vehicle Properties.

4) Customise your script (.fmt file) by removing sub-menus that may not be needed, for example,
Fuel Cost in "SA sent" may not be needed in some countries.

------------------------------------------------------------------------------

KEYWORDS: FM Terminal FMTerminal FM8 Fleet Manager 8 script

1597
www.mixtelematics.com

1597
 1598
10.3.326 Knowledge Base Article 332

Article Number 332

Title FM Professional 8 and MSDE

Created 7/27/2004 10:03:27 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 7/28/2004 10:13:23 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Professional 8 version 8.11.0017

----- SUMMARY -----

This KBA contains some known facts surrounding the Microsoft Database Engine (MSDE) installed
with the Fleet Manager Profesional 8 version 8.11.0017 software.

----- MORE INFORMATION -----

The MSDE installed with the version of the Fleet Manager Professional 8 software mentioned above, is
MSDE 2000 INCLUDING Service Pack 2. This might be an issue for some companies due to the
security rollup included in SQL Server 2000 Service Pack 3 and Service Pack 3a available from
Microsoft. If these Service Packs are required due to company or security policies, they can be
downloaded from Microsoft's website at www.microsoft.com.

It has also been determined that Microsoft's SP3 and SP3a installations will not upgrade the MSDE
installation that has been distributed with Fleet Manager Professional 8. If the SP3 or SP3a is required
due to security considerations on the network, it is advised that you do NOT install the MSDE as part
of the Fleet Manager Professional 8 installation, but rather install the latest MSDE 2000 engine that is
downloadable from www.microsoft.com. Alternatively you can connect to an Enterprise installation of
Microsoft SQL Server on your Network that already has the latest service packs applied to it.

Please note that according to the Microsoft EULA, the MSDE is recommended to be used on
Standalone computers only, and when planning to install the Fleet Management software on a
network, it is recommended that the full version of SQL Server be purchased and installed.

----- STATUS -----

This is by design. The next version of the Fleet Management software will however contain the latest
updates and service packs required by most companies.

------------------------------------------------------------------------------

KEYWORDS: FM FM8 FMPro8 FM Professional 8 MSDE Service Pack 2 SP2 MSDE2000 SQL Server

1598
www.mixtelematics.com

1598
 1599
10.3.327 Knowledge Base Article 333

Article Number 333

Title Installing the Fleet Manager Professional 8 Update

Created 9/3/2004 9:59:00 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 1/17/2007 9:32:02 AM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Professional 8 Update

----- SUMMARY -----

This KBA serves to describe the requirements for installing the Fleet Manager Professional 8
Update and updated components.

----- MORE INFORMATION -----

Fleet Manage Professional 8 sofware

To install the Fleet Manager 8 Update successfully, you need to have

1. the Fleet Manager Professional 8 software (release version) installed on the computer where you
are installing this.

2. the original source of installation available (i.e. access to the correct network path, or CD that
was used for the initial installation).

If this path is not available, you need to uninstall and reinstall the Fleet Manager software (initial
Fleet Manager 8 Professional version), and then run the update.

The original source is only needed when updating the main Fleet Manager software, this is not
required when updating the Fleet Manager Communications Suite, or the Fleet Manager Dealer
utility as well.

(The same requirements apply when modifying the installation to add or remove extensions or
other FM related components)

Fleet Manager Communications Suite

The Communications Suite Update, is ONLY an update, and requires the released version of the
Fleet Manager Communications Suite to be installed before running the update available.

Fleet Manager Dealer Utility

This is a standalone installset, and do not require a current installation of the FM Dealer to be
installed, but will update any current FM Dealer Utility.

----- CAUSE -----

1599
www.mixtelematics.com

1599
 1600

The reason for having the source of installation available for the Fleet Manager Professional 8
software, is that the update requires the initial files used for the FM installation, in order for it to
complete the update correctly.

----- SOLUTION -----

Insert the Fleet Manager Professional 8 CD before you attempt to run the update, or make sure the
original network path is available. If this is not available, you may need to uninstall and reinstall
from the original Fleet Manager Professional 8 CD.

All updates are available from the www.omnibridge.comdge.com website.

----- STATUS -----

This is by design.

------------------------------------------------------------------------------

KEYWORDS: FM8 Update Fleet Manager Professional 8 Communications Suite GSM DECT
GPRS Datatrak FMDealer Dealer Utility FM KBA333

1600
www.mixtelematics.com

1600
 1601
10.3.328 Knowledge Base Article 334

Article Number 334

Title Using GPS Velocity as speed

Created 11/12/2004 12:40:06 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/12/2004 1:26:14 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Fleet Manager Professional 8.11 (August) update (FMCli8.EXE version = 8.11.0026)

· FM 200 Communicator

----- SUMMARY -----

GPS Velocity can be used as speed, but depending on the filtering applied by the GPS unit, speed
can be picked up when the vehicle is not moving which may lead to confusion, and indicates a trip
when the vehicle was stationary/parked.

This KBA offers some tips on setting this up, and a workaround that can be used in these cases.

----- MORE INFORMATION -----

As per the information above, it is noted that 'trips' are recorded when no trips have been done, or
the vehicle was parked (i.e. speed was picked up during the time the vehicle was stationary). This
speed value picked up is normally very small (smaller than 10km/h).

Also note that in some cases, if the GPS and GSM antenna are installed too close together, they
could have an influence on the GPS Velocity as well - it is therefore recommended they be installed
some distance apart from each other (if the need for this arises).

----- CAUSE -----

This is due to the sensitivity of the GPS receiver.

----- SOLUTION -----

Download and install the file below, and follow the procedure set out below for the best results.

To download the file click here.

This file contains three files (FMPositionSvr.dll, TCOSvr.dll, FMDeviceSvr.dll). These three files
should be extracted to the "C:\Program Files\Common Files\Fleet Manager". These three files
should OVERWRITE the current files with these names -to ensure you copy this to the correct
directory, you can search for these files on the computer and ensure they are overwritten - they
should be in the directory mentioned above.

Please note:

1601
www.mixtelematics.com

1601
 1602

These files should only be applied to the Fleet manager 8.11 (August) update (FMCli8.EXE version
= 8.11.0026).

Once the three files are in place, you need to reset one value and then reload vehicle configuration:

1. Open specific vehicle's properties, go to DEVICE tab, go to the F1-GPS as velocity properties,
and to the 'Calibration' tab.

2. Set the value for 'Speed at which vehicle considered moving...' to a minimum of 7 - or see what
works for you. This has been tested and implemented successfully on 10km/h.

3. Now update your vehicles with the latest configuration, and monitor the vehicles to ensure this
has been applied correctly.

If this is deployed on a Fleet Manager network installation, it should be installed on each computer.

----- STATUS -----

The files available in this KBA will be included in the next update/release for the Fleet Manager
software.

------------------------------------------------------------------------------

KEYWORDS: GPS Velocity Speed F1 Ghost Trips FM200 FM200 Communicator FM 200 Plus

1602
www.mixtelematics.com

1602
 1603
10.3.329 Knowledge Base Article 335

Article Number 335

Title What's New in FM Dealer Utility (version number 2.11.2.0)

Created 11/16/2004 2:46:57 PM

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 11/17/2004 12:06:55 PM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Dealer Utility FM200 Plus Device Drivers

----- SUMMARY -----

The latest version of the FM Dealer Utility is available for download from the www.omnibridge.com.
website under the Service -> Downloads -> Dealer Utility -> Fleet Manager Professional 8 section.

The FM Dealer Utility version number is 2.11.2.0 and it contains updated FM200 Plus firmware set
version 4.10.21.0

Download and install this version of the FM Dealer Utility (after uninstalling any previous versions of
this utility), and upload the device drivers included in this version of the FM Dealer Utility to affected
vehicles.

The following is a list of what has been updated in the latest FM Dealer Utility firmware set.

1) FM200 Plus units with an EDM connected to the F3 input could record unrealistic values under
certain circumstances, resulting in incorrect values being shown in the consumption reports. This has
been corrected in the updated device drivers.

2) If a GPS is connected to the FM200 Plus, and an EDM is connected to one of the analogue lines,
then one of the other analogue lines could become a low resolution input (0-38V), if the input line the
EDM was connected to was set to I1 to I4, or I1 to I8 (for the FM200 Plus HV)

3) A Speed Calibration code-plug can be configured to learn the speed calibration of a vehicle. This
new feature previously only worked on a vehicle set to 0-65 500 pulses per Km, this has now been
improved to work on a vehicle set to up to 655 300 pulses per Km.

4) When connected to the FM200 Plus, a voice call with a Nokia 6090 car phone was terminated
after one minute. This has now been changed, and the call will no longer be terminated.

5) A filter algorithm has been added to the FM200 Plus firmware to ignore positions further north or
south than 80 degrees. The algorithm also suppresses sudden changes in latitude of 2 degrees or
more (unless the new value persists for 10 seconds or longer). This makes the system more resistant
to incorrect GPS signals being calculated by the GPS receiver or being sent to the FM200 Plus.

----- STATUS -----

Upload the device drivers from the latest FM Dealer Utility available (as per SUMMARY section of
this KBA).Use the FMDealer program to upload the latest device drivers for the appropriate devices

1603
www.mixtelematics.com

1603
 1604

connected to your FM200 Plus

------------------------------------------------------------------------------

KEYWORDS: FM8 FMDealer FM Dealer Utility Device Drivers

1604
www.mixtelematics.com

1604
 1605
10.3.330 Knowledge Base Article 336

Article Number 336

Title Force Fleet Manager database upgrade in network environment

Created 12/23/2004 2:18:50 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 12/23/2004 5:05:58 PM

Last Modified By Michael Chamberlain (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Professional 8.11 and later

----- SUMMARY -----

When the database connection is checked by FMCrtDB8.exe (the program launched by the install
set), from a network client, the database upgrade will only occur if the database version number is
different to that of the version of the client.

Below is a method to force the upgrade procedure when there are no Fleet Manager components
installed on the database server.

----- MORE INFORMATION -----

Some minor updates, 'hotfixes', or patches may be released without changing the version number
used to check against the database. In the case where there are no components installed on the
database server in a network, the database will not be upgraded.

----- CAUSE -----

This is by design to prevent a database from being updated multiple times when the Fleet Manager
system is installed on many client computers.

----- SOLUTION -----

To force the database upgrade the database version needs to be reset to a valid old version number.
This will ensure an 'outdated' version of the database is recognised, and an upgrade will be initiated.

To do this, please follow the steps below:

1. Please download the following file: FMPro8_ForceDBUpdate.zip.

2. Extract this to your the C:\Program Files\Common Files\Fleet Manager folder.

NOTE: this is not the folder selected when installing the Fleet Manager software. For non-English
versions of Windows, please use the OS specific path for "Program Files\Common Files".

3. Ensure that the FM Administrator is pointing to the correct database (i.e. the database in need of
an upgrade on the server).

4. Execute (double click) the FMPro8_ForceDBUpdate.BAT file.

1605
www.mixtelematics.com

1605
 1606

5. Run the FM Administrator utility again, open the connection settings and click OK. This will initiate
the database upgrade, and click OK to continue.

The database should now be upgraded and ready to use with the Fleet Manager system.

------------------------------------------------------------------------------

KEYWORDS: Fleet Manager FM8 FM database upgrade Update

1606
www.mixtelematics.com

1606
 1607
10.3.331 Knowledge Base Article 337

Article Number 337

Title Upgrading Fleet Manager Professional 8 database to FM8 Update

Created 12/24/2004 12:07:05 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 2/3/2005 1:46:48 PM

Last Modified By Jeremy Hartley (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Professional 8 Update (August 2004)

----- SUMMARY -----

When upgrading a Fleet Manager Professional 8 database with the FM8 Update (i.e. applying the
update released in August 2004 for a version 8 database to 8.11), configuration settings on vehicle
level is reset to that of the configuration group level.

----- MORE INFORMATION -----

During the upgrade of the database any changes made to the vehicle configuration on vehicle level
will be reset to what it is specified as on configuration group level.

Inputs affected by this upgrade include the calibration/settings of frequency and analogue devices
(excluding speed and RPM). This includes the following devices:

· Cold Chain - Cooling unit switch

· Cold Chain - Refrigerator door switch

· Cold Chain - Temperature sensor

· FM Impact Sensor integrity check, FM Impact Sensor Y-axis

· FM Impact Sensor X-axis, Extended Trip - PTO switch

· Extended Trip - Cruise control switch

· EDM (fuel flow meter)

· Sub-trip end button

· FM200e coolant level monitor

· FM200e engine temperature sender

· FM200e oil pressure sender

· FM200e PTO switch

1607
www.mixtelematics.com

1607
 1608

· User created Switches, example Door Switch

· User created pulse counters, example fuel flow meter

· User created Frequency sensors, example Secondary RPM

· User created Analogue sensors, example Temperature sensor

Changes made on vehicle level to the configuration should be checked before downloading data or
uploading new configurations, as it may have defaulted to the vehicle's configuration groups settings.

This does NOT affect any external device settings (such as GSM Numbers etc).

----- CAUSE -----

This is caused by the way the FM8 Update upgrades an existing FM8 database.

----- SOLUTION -----

After upgrading the database, ensure your configuration settings are correct before downloading or
uploading new vehicle configurations. If a general change is needed for a whole configurations group,
make the change on vehicle configuration group level and allow the change to escalate to vehicle
level as well.

----- STATUS -----

This will be solved in the following release of the Fleet Management software.

------------------------------------------------------------------------------

KEYWORDS: Fleet Manager 8 Update Database Configuration Consumption EDM Calibration

1608
www.mixtelematics.com

1608
 1609
10.3.332 Knowledge Base Article 339

Article Number 339

Title Event Mismatch Error Message

Created 1/13/2005 2:42:04 PM

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 9/1/2005 2:12:15 PM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM2002SR1 Fleet Manager Professional 8

----- SUMMARY -----

Data is referenced according to event sequence ID numbers, these numbers are on the units, as well
as in the database. If the event sequence number already exist in the database, and data is
downloaded that is not the same, it gets the error.

----- MORE INFORMATION -----

To determine whether the mismatch lies between the database and unit, you can do a full download of
the unit into a new database. If it downloads succesfully, it means the event sequence numbers on the
unit and database don’t correspond.

----- CAUSE -----

Event mismatch could occur when you have outdated device drivers loaded, or the unit was cleared or
swapped or the ID was changed without running the swap unit function in the software. It would be a
good idea to ensure that there are no vehicles with the same vehicle ID.

----- SOLUTION -----

The reason for the Event Mismatch message is that data is referenced according to event sequence ID
numbers, these numbers are on the units, as well as in the database, and this is how the database
links up existing data with what is on the unit - if the event sequence number already exist in the
database, and data is downloaded that is not the same, it gets the error.

To resolve this you consider the following:

1. you can either clear the unit, and run the swap unit functionality in the database, and can then be
sure that all data will record and download correctly. The downside of this is that some data will be lost.

2. alternatively you can run the swap unit functionality in the database, BUT if you do this, without
clearing the unit, your reports may include duplicate event/subtrip data. This way you will not lose data,
but your reports will not display accurately (as it may seem that in some cases there are duplicate data
for the same date/time).

------------------------------------------------------------------------------

KEYWORDS: FM8 FM2002SR1 Event Mismatch

1609
www.mixtelematics.com

1609
 1610
10.3.333 Knowledge Base Article 340

Article Number 340

Title Event consumption report - treeview explained

Created 2/24/2005 8:14:15 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 2/24/2005 1:26:01 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Event Consumption report extension, version 8.0.0.22 and earlier

----- SUMMARY -----

In the generated Event consumption report you will see a treeview of dates on the lefthand side of the
report. If these dates are expanded, you will see more dates underneath each date.

----- CAUSE -----

The treeview is a copy of the reporting engine (Crystal) table used to generate the report and the fuel
data that are displayed in the treeview are unfiltered, as opposed to what is displayed in the report.

----- SOLUTION -----

This is not an error in the software, and does not stop the program from functioning. It will be changed
in a future release to avoid confusion.

----- STATUS -----

This is by design, but we are investigating possible changes to this in the future.

------------------------------------------------------------------------------

KEYWORDS: Event Consumption report extension Eventconsumption Reports treeview FM8 Fleet
Manager 8

1610
www.mixtelematics.com

1610
 1611
10.3.334 Knowledge Base Article 341

Article Number 341

Title Event Consumption Report extension - closing report

Created 2/24/2005 10:55:59 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 3/3/2005 10:43:43 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Event Consumption report extension, version 8.0.0.22 and earlier

----- SUMMARY -----

Under special circumstances, an error may appear when closing the event consumption report.

----- MORE INFORMATION -----

In some cases, when an unlikely combination of sequences in the Criteria Wizard are used when
generating the Event Consumption report in the Fleet Manager, the following error could occur:

w Form_Unload Linia 2090.

: 91 (0x5B) Object variable or With Block variable not set.

Thereafter the report closes, and in some cases the Fleet Manager software as well.

----- CAUSE -----

This is caused by an unlikely combination of sequences in the Criteria Wizard.

----- SOLUTION -----

This does not happen very often, and will not affect the data of the Fleet Manager database or the
reporting functionality. A change has been made to cater for this in a next release. If this has
happened, you should be able to either continue working in the software. You may need to shut down
the Fleet Manager before continuing, but usually it will not be affected at all.

----- STATUS -----

This has been fixed in the next release of the Event Consumption Reports extension.

------------------------------------------------------------------------------

KEYWORDS: Fleet Manager 8 Event Consumption Report Error Closing

1611
www.mixtelematics.com

1611
 1612
10.3.335 Knowledge Base Article 342

Article Number 342

Title Typical Crystal reporting issues

Created 3/3/2005 11:32:56 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 11/6/2006 5:25:39 PM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 8, all versions

----- SUMMARY -----

From the initial Fleet Manager 8 release, Crystal Reports has been used as the reports engine.

----- MORE INFORMATION -----

A typical Crystal Reports message that may be received is the following:

Invalid Report Creation Keycode

----- CAUSE -----

This error message generated by the (Crystal Reports) report viewer is the result of a very specific
combination of software components on a machine. In short, if the System32 folder contains a file
named PsiKey.dll, the report viewer will (incorrectly) try to use it to validate its licence. The validation
fails because PSIKey.dll is not (nor has it ever been) part of the Crystal Reports engine or viewer.

To resolve the problem with the reporting, PSIKey.dll needs to be deleted from the System32 folder.

----- STATUS -----

This is by design in the Crystal Reports system.

PSIKey.dll is part of a software-licensing tool by Protexis - the most common source of the file is the
DivX 5.2.1 codec installation bundle: after deleting the DLL, it may be necessary to upgrade to a later
version of the DivX codec (or the freeware XVid codec) to ensure that the machine can play DivX-
encoded video. Later versions of the DLL do not seem to interfere with the Crystal Reports viewer
component, but this has not been tested exhaustively as of yet - please bear in mind that there is a
small chance that there may be other software packages that include PSIKey.dll.

------------------------------------------------------------------------------

KEYWORDS: Invalid Report Creation Keycode Fleet Manager 8 FM8 Crystal Reports PSIKey.dll

1612
www.mixtelematics.com

1612
 1613
10.3.336 Knowledge Base Article 343

Article Number 343

Title Reports hanging

Created 3/14/2005 7:44:51 AM

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 3/14/2005 10:12:53 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Fleet Manager 2002 Professional Version 7.11.0038 SR1, and earlier versions of the Fleet Manager
software

----- SUMMARY -----

When running a report, it seems as if the computer just “hangs”, it does not give you an error
message or process the report.

----- MORE INFORMATION -----

Fleet Manager 2002 and earlier use Microsoft Access Runtime 97 as the reporting engine. For various
reasons, especially on later operating systems (i.e. later than Windows 98 Second Edition), this could
hang, due to different component versions installed by different applications).

----- CAUSE -----

In some cases, some of the components of the Microsoft Access Runtime 97 could have been
replaced by later versions, or might not install successfully on some operating systems.

----- SOLUTION -----

There are two things you could try in this case (to get the Microsoft Access Runtime installed
successfully, and reports working again):

The first is uninstalling and reinstalling the Access Runtime:

1. Reboot your computer, so that you know no Fleet Manager or Office programs are running in the
background.

2. When you log in, hold the SHIFT key down after you typed your login information, and clicked "OK"
or "Login" to log in on your computer - this will stop the programs in your startup menu from loading
after logging in. This way you will know for sure there is nothing that will use MSAccess on startup.

3. Now go to Control Panel, and uninstall "Access Runtime".

4. After you have complete removed "Access Runtime", you can reinstall it from the Fleet Manager CD
- you will find the install set for this under the "Fleet Manager 2002 Professional\Setup Files\Access
Runtime\English" (or German) subdirectories of the FMOffice CD - to reinstall Access Runtime, double
click "setup.exe".

1613
www.mixtelematics.com

1613
 1614

After you have reinstalled the Access Runtime, please open the Fleet Manager software, and try to do
a Vehicle List Report for one vehicle - just to get the Access database engine up and running - leave it
for a while, and if it still doesn't generate reports, cancel the report, and close the FM Software and
restart the computer.

The next thing you can try is to copy the FMRpt.mde file from the Fleet Manager installation CD
(FMOffice 2002 January 2003 CD, if you were using FM2002SR1), and overwrite the current FMRpt.
mde file with it:

1. restart your pc (again to ensure that none of the reporting and related components are in use)

2. from your Fleet Manager CD, copy the following file to the Fleet Manager install directory:

FMRpt.mde (you will find this file in the "\Fleet Manager 2002\Setup Files\" directory.

Again, open the Fleet Manager software, and try to do a Vehicle List Report for one vehicle.

----- STATUS -----

To enhance report generation performance in general, Crystal Reports is being used as the reporting
engine from Fleet Mananager Professional 8 onwards.

------------------------------------------------------------------------------

KEYWORDS: Access Runtime Reports hang FM2002 FM2001

1614
www.mixtelematics.com

1614
 1615
10.3.337 Knowledge Base Article 344

Article Number 344

Title How to connect and setup a Pocket PC

Created 3/23/2005 1:22:50 PM

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 6/15/2006 2:34:14 PM

Last Modified By Michael Chamberlain (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM8, Pocket PC, iPAQ, PDA

----- SUMMARY -----

How to connect and setup a Pocket PC

----- SOLUTION -----

Your unit config must have the "Other Serial Device" connected to the ports (S2 or S3) you want to
use.

Use a NULL-MODEM cable (DB9 Female-crossover-Female) between the PDA and the FM200.

Instructions:

1. Download FM Comms SDK for Pocket Terminal.

2. Unzip this file into a temporary folder on your PC harddisk.

3. Then read the user manual.

4. Ensure you PocketPC is connected to your PC and that the latest MS ActiveSync is installed and
working.

5. Now run Setup.exe to install the FM Pocket Terminal application on you PC. This will then also offer
to install it on your PocketPC.

6. Configure your FM200 to have "Other Serial" connected to S2 or S3.

7. Ensure that you load Device drivers that include the SDK text. E.g. "SDK and Modem support" This
could be done using the FM Dealer Utility.

8. Remove you PocketPC from your HotSync cradle and connect it to the FM200 S2 or S3 using the
appropriate PDA serial cable and a null-modem cable.

9. Run the FM Terminal app on the PocketPC.

When you are prompted to overwrite the files during the installation it is important that you select 'NO
TO ALL' - i.e. the files should not be overwritten.

1615
www.mixtelematics.com

1615
 1616

Ensure you disable ActiveSync before starting the the Pocket Terminal application.

On the PDA browse to the \Program Files\FM Pocket Terminal directory you

will find the Registry.txt file. Open it by clicking on it and you will find 3 lines of text like this:

"0"

"0"

"4"

Change the last line to match the comm port your device is using. For COM1 you need:

"0"

"0"

"1"

Make sure you know what com port number the PDA is using, if you use the cradle port is should be
COM1 if you use a sleeve it may be COM4.

It works best with PPC2002.

------------------------------------------------------------------------------

KEYWORDS: Pocket PC iPAQ PDA

1616
www.mixtelematics.com

1616
 1617
10.3.338 Knowledge Base Article 345

Article Number 345

Title Setting up GPS velocity as speed on GARMIN GPS

Created 3/23/2005 3:15:13 PM

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 5/8/2007 11:18:19 AM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 Plus with an external GPS

----- SUMMARY -----

When an external/internal GPS is connected to an FM200 Plus unit, GPS Velocity can be selected as
the speed source. When using an external GPS, you may need to modify some settings to get speed
with your GPS unit.

This KBA describes how the GPS unit should be set up when using an external GPS and GPS Velocity
as a speed for the speed signal.

----- MORE INFORMATION -----

Using the FM200 Plus with an external GPS, with GPS velocity as speed, the detail on the activity
timeline shows speed, but on the graph, the light blue bar representing speed is not visible - it only
shows ignition on (the dark blue section) and not that the vehicle moving.

----- CAUSE -----

The problem might be that your Garmin GPS has not been configured to send out velocity readings.
And to enable this you need to set up the GPVTG string.

----- SOLUTION -----

To configure the GPS unit as suggested above, please follow the steps below:

1. Firstly you should download the latest version of the FM Dealer Utility from the www.ci-omnibridge.
com website and ensure you have the latest available device drivers loaded (for more information on
this, please see instructions in KBA #335).

2. Download the snsrcfg.exe utility to configure the Garmin 35 GPS.

3. Connect your GPS to a COM port on your PC. (If your Garmin GPS do not have a DB9 plug
connected you could solder the

white wire to pin 2, the blue wire to pin 3 and the black wire(ground) to pin 5).

4. Execute the snsrcfg.exe utility.

5. From the base model list select the GPS 25/35/46 option and click OK.

1617
www.mixtelematics.com

1617
 1618

6. Go to the Comms menu and click the setup entry.

7. Select 'manual' mode, and enter 4800 as the baud rate.

8. Select the relevant COM port that your GPS is connected to.

9. On the Comms menu, click on the Connect entry.

10. If the PC connected to the Garmin GPS successfuly you can go to the Config menu.

11. Select the NMEA Sentence Selections entry. (Or press F7 button)

12. Tick the GPVTG option. (The GPVTG string output is needed from the GPS to plot GPS velocity as
speed) If you experience slow GPS update rates, you could deselect some of the 'extra' strings.
(Ensure that the GPGGA and the GPVTG strings stay selected)

13. Click the OK button.

14. Under the Config menu, select the Send Configuration to GPS item.

15. After the successful update, you can exit the snsrcfg utility. (Do not worry to save the config when
exiting.)

17. Make sure that the GPVTG strings are actually transmitting.

18. You could test this by connecting the Garmin GPS to Hyperterminal and checking the resulting
strings on the screen. (There should be a string in the list that starts with GPVTG.)

Your GPS velocity as speed should now work in Fleet Manager.

----- STATUS -----

The GPS unit configuration is dependent on the manufacturer, and if needs be, should be set as per
instructions in the SOLUTION section of this KBA.

------------------------------------------------------------------------------

KEYWORDS: FM200 GPS velocity speed external GPS Garmin

1618
www.mixtelematics.com

1618
 1619
10.3.339 Knowledge Base Article 347

Article Number 347

Title Forcing device driver upload via GPRS/GSM

Created 6/27/2005 11:21:19 AM

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 8/5/2005 11:32:06 AM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Units using GPRS/GSM for communication

----- SUMMARY -----

Under certain conditions the remote device driver upload results in the follow error message in the
logfiles:

Communications error: DDRs upload failed

----- MORE INFORMATION -----

If a vehicle is in the process of sending active events while the device drivers are uploading (i.e. the
vehicle is out of trip and communication with the base station is established), the device driver data
gets corrupted and will then not load to the unit.

----- CAUSE -----

Data transfer can take place in one direction only, i.e. either sending active events (via GPRS), or
uploading data (such as device drivers).

----- SOLUTION -----

The workaround is to change the vehicle configuration and upload device drivers as specified below:

1. disable active events,

2. upload a new configuration to the vehicle,

3. then upload device drivers,

4. then re-enable the active events and

5. reload the vehicle configuration.

----- STATUS -----

The way of uploading device drivers will be enhanced to provision for this (dual data transfer) in a
next version of the FM unit firmware.

------------------------------------------------------------------------------

1619
www.mixtelematics.com

1619
 1620

KEYWORDS: FM200 GPRS GSM Device Drivers DDX DDR

1620
www.mixtelematics.com

1620
 1621
10.3.340 Knowledge Base Article 348

Article Number 348

Title DiagGPRSRouter.log - column heading definition

Created 8/8/2005 12:28:24 PM

Created By Michael Chamberlain (MiX Telematics - Stellenbosch)

Last Modified 1/17/2006 1:20:59 PM

Last Modified By Daniel Lehniger (Siemens FM Automotive - Switzerland)

Details ----- APPLIES TO ----

· Fleet Manager 8.12 DiagGPRSRouter.log

----- SUMMARY -----

This KBA explains the column heading in DiagGPRSRouter.log files and was developed for advanced
analyses/troubleshooting for the experienced FM User (i.e. dealer/developer) only.

----- MORE INFORMATION -----

This is additional logging which could be enabled in the Fleet Manager GPRS service.

This log file could be used in GPRS problem analysis.

----- SOLUTION -----

Column heading definitions:

1. AMemKB : Available physical memory in the specific computer system. (in Kilobytes)

2. MemKB : Memory being used by the GPRS service. (in Kilobytes)

3. Threads : Current number of threads open by the GPRS service.

---------------

4. LDB-ms : Average database access time in milliseconds to add an item to the schedule.

5. LDbCnt : Number of scheduled database logs executed since previous recorded value in
‘DiagGPRSRouter.log’

6. Logs : How many scheduled log entries outstanding(still to be added to database) at that point in
time.

---------------

7. AvDb-ms : Average time it takes to write one AVL in database(in milliseconds).

8. AvlCnt : How many AVL's added since previous recorded value in ‘DiagGPRSRouter.log’

9. Avls : How many AVL's outstanding(Not added to database yet).

1621
www.mixtelematics.com

1621
 1622

---------------

10. AcDb-ms : Time it takes to write one active event into the database (in milliseconds).

11. ActCnt : How many active events since previous recorded value in ‘DiagGPRSRouter.log’

12. Acts : How many outstanding active events that haven't been added to the database.

---------------

13. StDb-ms : Time it takes to save vehicle status in database (in milliseconds).

14. StaCnt : Amount of vehicle statuses that were saved in that timer tick.

15. Stat : Amount of vehicle statuses that were not saved in that tick(left over for next timer tick.)

---------------

16. Vehs : Number of possbile vehicles in schedule(Active & Inactive vehicles).

17. VehsCon : Number of vehicles that are connected(actively) to GPRS service.

---------------

18. Tck[ms] : Tick period. Should be 16 milliseconds. Best if value <= 55ms. How long it takes to
communicate(writing and reading).

19. Write : Amount of bytes written in IP(UDP).

20. Read : Amount of bytes read in IP(UDP).

----- STATUS -----

This is by design, and was developed for advanced analyses/troubleshooting for the experienced FM
User (i.e. dealer/developer) only.

------------------------------------------------------------------------------

KEYWORDS: FM8 logfile GPRS Diag

1622
www.mixtelematics.com

1622
 1623
10.3.341 Knowledge Base Article 349

Article Number 349

Title FMLite Report issue

Created 9/7/2005 9:31:41 AM

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 9/7/2005 3:47:19 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Lite version 2.52.0247 (March 2005)

----- SUMMARY -----

On some reports, the Fleet Manager Lite 2.52 produces an error message when generating a report in
FMLite, even though there is data in the database.

----- MORE INFORMATION -----

The error message received reads as follows:

An unexpected error has occurred in Process report - 50507: Invalid job number.

After receiving this message and closing it, the report is not generated.

----- CAUSE -----

In some cases the report files were not installed correctly.

----- SOLUTION -----

Download and install the following update:

1. Download the FMLite_252_Reports.zip file

2. Extract the files into the root directory of an existing FM100 installation (typically C:\FM100). This
will extract the relevant reporting files to the root folder as well as the letter reports folder (typically C:
\FM100\LTRRPT).

The reports should now generate successfully.

----- STATUS -----

All reporting files have been included in the update supplied with this KBA.

------------------------------------------------------------------------------

KEYWORDS: FM100 FMLite Reports Invalid Job Message

1623
www.mixtelematics.com

1623
 1624
10.3.342 Knowledge Base Article 350

Article Number 350

Title GPRS Service memory management

Created 9/7/2005 4:25:51 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 12/20/2005 8:36:53 AM

Last Modified By Marius van der Westhuizen (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager GPRS Service

----- SUMMARY -----

The FM GPRS Service uses increasingly more memory, which is only released with a restart of the
Service or PC.

----- MORE INFORMATION -----

When running the FM GPRS Service continuously for a period of time, it will use increasingly more
memory, which may degrade the performance of the PC. The memory is only released with a
restart of the Service or the PC. The length of time before degradation of performance occurs
depends on the specification of the PC, as well as the number of vehicles connecting to the
Service.

----- CAUSE -----

This problem is caused by an internal fault in the Microsoft Visual Basic ADO component, on which
the GPRS Service relies.

----- WORK AROUND -----

The best workaround is to restart the GPRS Service on a daily basis. You can do this either by

A. opening the GPRS Service to stop and restart it (see details below), or

B. you can use Windows Scheduler to restart the service once a day (see details below).

A. Manually stop and start the GPRS Service

(You will need to do this on a daily basis):

1. Open Control Panel (Click Start -> Control Panel)

2. Double click on FM Service Manager to open Fleet Manager Services available

3. Select the Fleet Manager GPRS Service, stop it, and start it (from within the Fleet Manager
Services dialog).

B. Using Windows Scheduler to restart the GPRS Service on a daily basis

1624
www.mixtelematics.com

1624
 1625

(This is a once off procedure to restart the service on a daily basis).

1. We've created a batch file to do this, so please download the RestartGPRSService.bax file and
save it to a location where it will not be deleted. (To download this file, right click on the link and
select the option to 'save target as').

2. Rename this file to "RestartGPRSService.bat".

3. Open Windows Scheduler (Start - All Program - Accessories - System Tools - Schedules Tasks).

4. Click Add Scheduled Task and click Next to continue

5. You should now see a list of applications to choose from. Click on the Browse command button
to browse to where the "RestartGPRSService.bat" is located.

6. Select the file, and click Open

7. Select option to Perform the task Daily and click Next.

8. Select the required time (we suggest to make this early in the morning i.e. 03:00 to reduce any
interruption with data transfer between vehicle and database). You will also need to select the start
date (today), and ensure the task is set to be performed Every day. Click Next.

9. Enter your Windows User Name and password. Type in the password again to confirm it. (Note:
You must enter your password or else the scheduled task will not run). Click Next.

10. On the last page of the Wizard, click Finish

Your GPRS Service should now be scheduled to restart daily.

----- STATUS -----

The GPRS Service is being rewritten in c++ to ensure optimised resource usage. This will be
included in the FM8.3 software to be released at the end of 2005.

------------------------------------------------------------------------------

KEYWORDS: GPRS Service Memory Performance FMGPRS

1625
www.mixtelematics.com

1625
 1626
10.3.343 Knowledge Base Article 351

Article Number 351

Title Enhancing FM Autopoll Client performance

Created 9/19/2005 2:26:51 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 2/6/2006 2:33:32 PM

Last Modified By Taryn Murray (MiX Telematics - Johannesburg)

Details ----- APPLIES TO ----

· Fleet Manager Autopoll Client release version 8 and later

----- SUMMARY -----

There has been a number of requests to run the Fleet Manager Autopoll Client as a service. This is
currently not possible, but there is a way to run the Autopoll Client without requiring a logged in user.
This is described in detail in the SOLUTION section of this KBA.

----- MORE INFORMATION -----

The procedure referred to is running the Autopoll Client every minute as a scheduled task.

The advantages of running the Autopoll Client this way are:

* a logged on user is not required

* memory usage is optimised, as it forces the Autopoll Client to process all folders and then exit

* if there is already an Autopoll instance running, it does not create another instance - avoiding
conflicts.

----- SOLUTION -----

To add the schedule to run the Autopoll Client as described above, please do the following:

1. Open Windows Scheduler (Start - All Programs - Accessories - System Tools - Schedules Tasks).

2. Click Add Scheduled Task and click Next to continue

3. You should now see a list of applications to choose from. Click on the Browse command button to
browse to where the "FMAPCPro.exe" is located.

4. Select the file, and click Open

5. Select option to Perform the task Daily and click Next.

6. You can set the required time to 01:00. You will also need to select the start date (today), and ensure
the task is set to be performed Every day. Click Next.

7. Enter your Windows User Name and password. Type in the password again to confirm it. (Note: You

1626
www.mixtelematics.com

1626
 1627

must enter your password or else the scheduled task will not run). Click Next.

8. On the last page of the Wizard, select Open advanced properties for this task when I click Finish.

9. Your scheduled task will open on the Task properties. Append the following to the path in the Run
section " /NOW" (i.e. a space, forward slash, and then the word NOW - without the inverted commas, i.
e. your string should now look like this:

"C:\Program Files\...\FMAPCPro.exe" /NOW (where '\...\' indicates the appropriate path to the file).

10. Click OK to save the scheduled task.

11. Right Click on the Autopoll Client schedule, and click Run.

12. Right Click on the Autopoll Client schedule, and click Properties Properties.

13. Click on the Schedule tab.

14. Click on the Advanced button.

15. Tick the Repeat Task block and select how often you would like the task to be run i.e. Every 1
minute.

16. Change the Duration to 24 hours.

17. Click OK.

18. Click OK.

----- STATUS -----

Including the Autopoll Client as a service is scheduled for a future release of the Fleet Manager
software. Until then it is recommended that the above procedure be used, should this be required.

------------------------------------------------------------------------------

KEYWORDS: FMAPC APC Autopoll Client Memory Scheduled Task /NOW

1627
www.mixtelematics.com

1627
 1628
10.3.344 Knowledge Base Article 352

Article Number 352

Title How to set up an FM300 unit in the Fleet Manager software prior to FM8.3

Created 10/5/2005 3:09:16 PM

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 10/5/2005 5:16:59 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM300 Communicator

· FM300 ComLink-GSM

· Fleet Manager 2002

· Fleet Manager Professional 8

----- SUMMARY -----

This document describes how to configure and setup an FM300 series unit to FM software prior to
Fleet Manager Professional 8.3 (FM 8.3).

----- MORE INFORMATION -----

The FM 8.3 software includes support for FM300 Communicator and FM300 ComLink-GSM as unit
types. Software prior to this (FM8.1x or FM2002) can also be configured to use FM300 units, even
though it does not appear in the unit type selection of the vehicle properties.

----- CAUSE -----

FM300 Communicator and FM300 ComLink-GSM are new unit types developed and released in
2005, and are fully supported from the FM8.3 software onwards.

----- SOLUTION -----

FM300 Communicator:

1. Download the FM Dealer from the www.FMfm.com website, for the latest set of device drivers.

2. Configure the FM300 Communicator as a FM200 Communicator in the vehicle properties (i.e. set
the unit type to FM200 Communicator).

Please note: No devices or events should switch off Relay Drive 2 – external drive.

FM300 ComLink-GSM:

1. Download the FM Dealer from the www.FMfm.com website, for the latest set of device drivers.

2. Configure the FM300 Comlink-GSM as an FM200 Plus unit on the vehicle properties (i.e. set the

1628
www.mixtelematics.com

1628
 1629

unit type to FM200Plus).

3. On device properties for this unit, connect GSM to S2.

3. On the Power tab of GSM, specify the 'Device will be powered via: Positive drive'.

Please note: No devices or events should switch off Relay Drive 2 – external drive.

----- STATUS -----

From FM8.3 onwards the FM300 unit types are available from the vehicle properties window, and do
not need this specific configuration.

------------------------------------------------------------------------------

KEYWORDS: FM300 FM8 FM2002 FM300 Comlink-GSM Comlink Communicator

FM300Communicator

1629
www.mixtelematics.com

1629
 1630
10.3.345 Knowledge Base Article 353

Article Number 353

Title Setting up WiFi

Created 11/22/2005 8:03:50 AM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/11/2007 10:26:50 AM

Last Modified By Michael Chamberlain (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM Wireless Kit

----- SUMMARY -----

Set up WiFi communications between FM200 Plus or FM300 and Database Server.

----- MORE INFORMATION -----

The FM200 Plus or FM300 can use IEEE802.11b/g Wireless Communications (aka WiFi), instead of
GPRS or DECT. This KBA describes how to setup the FM Wireless Kit for use with the FM200 Plus or
FM300.

----- SOLUTION -----

----- Access Point: -----

1. You should be able to use any Access Point hardware and antenna. For example, we use an "outdoor
packaged" AP/Bridge with PoE and an 8dBi omni-directional antenna on our office site.

2. Position the Access Point hardware as close to the antenna as possible. The antenna should be
mounted in an open area, for optimal coupling with the movable asset units. It is possible to mount the
antenna inside the office, close to the server, but then the RF signals have to travel a long way, past
many obstacles to reach the Movable Assets. The ideal is that the access point at the site is placed
inside the Parking Garage, close to all the vehicles. There is a signal loss dependent on the distance
and type of link between the antenna and the Access Point. It is best to have the Access Point located
next to the antenna and rather have them both far from the server, and close to the roaming units.

3. Setup the Access Point with a preferred SSID (Service Set IDentifier). Access Points can share the
exact same SSID. This enables you to build a mesh of Access Points on your site, which will improve the
likelihood of successful connection from the roaming devices. Multiple Access Points with a common
SSID, result in the wireless connection determining the optimum (nearest and strongest) connection
point.

4. Setup the Access Point with your Authentication method. The Wireless Kit only supports 64-bit or 128-
bit WEP encryption. Do not select any of the other types of security (such a WPA).

5. Ensure the Access Point is connected on the same sub-net as the GPRSService server, or make sure
the traffic entering via the Access Point, can be routed to the computer running the GPRSService server.
(Consult with your network administrator regarding this set-up.)

1630
www.mixtelematics.com

1630
 1631

----- FM Hardware: -----

1. Be sure you have loaded the correct Device driver set (modems & WLAN - version should be at least
v5.10.31.3)

2. Connect the FM Wireless Kit to one of the available serial ports (S2 or S3 for FM200 Plus; S3 for
FM300); Connect the power lines to the Positive Drive and Ground connections. Both a GSM and the FM
Wireless Kit can be connected (each to a different Serial Interface Line), and the FM OBC will determine
via which channel to communicate data.

3. Place your antenna initially in an area where there is a direct-view coupling possible between the FM
Wireless Kit antenna and the Access Point antenna (to ensure the best chance of establishing a link).
You may move the antenna to more covert locations, once you are able to establish a connection. The
location of the antenna will be determined by using an iterative approach:

- Start with a location that provides the best chance of establishing the connection. Once you have
success, then try alternative/preferred locations.

- Next try the location where you prefer the antenna to be located (e.g. inside the dashboard). If you
cannot establish a link from this location, try other locations.

The rules of RF communication dictates that the signal must have an unobstructed path between the two
antennas. Metal obstructions severely attenuates the signal, and thus reduces range of connection.
These obstructions include vehicle bodies, air conditioning ducts, building structures (concrete re-
inforcing), etc.

For best performance, the antenna should be mounted outside the movable asset, to ensure maximum
exposure to the medium in which the RF signals travel.

----- FM Software: -----

Refer to the FM Professional Documentation for more detailed descriptions of each item.

1. Add the Wireless Kit device to the serial port on which the physical connection was made (S2 or S3
for FM200 Plus; S3 for FM300)

2. On the Device Properties->Connection Tab, select "Use a specific network name (Service Set
Identifier)" and type in the name of your Acces Point(s)

(Note that all your Access Points can share the exact same name, e.g. FMWLAN. Avoid using names
such as "any" or "internet", unless you want the units to connect to these type of resources. Do make
sure you type in the name exactly as you have defined it in the Access Point - See Access Point Step 3
above.)

Type in the IP address of your database server. This is the IP address of the computer which will accept
the data you send via the Access Point, and is the address of the computer running the GPRSService
component, which collects the data and delivers it the the application that posts the data to the
database.

Select the enabled ports on each device. The default values are usually acceptable. Check with the
administrator of the GPRSService computer for the proper server IP port.

3. On the Device Properties->Network Tab you can specify how IP addresses are assigned. You can use
specific settings or use the DHCP facility of your network to automatically assign IP addresses for the
FM OBC. Confirm these settings with your network administrator.

4. On the Device Properties->Encryption Tab you can select the Authentication methods. You can select
the specific Mode, as defined in the Access Point, but Automatic should work. The FM Wireless Kit
supports 64-bit and 128-bit WEP key encryption. You must specify the key values as well. WEP key: The
5 or 13 ASCII digit password for the WEP security.

1631
www.mixtelematics.com

1631
 1632

5. Device Properties->Packet Comms and Device Properties->Database specify the type of traffic, the
amount of traffic and what you do with the data traffic. These are required to keep the link alive, if the IP
address can be re-assigned to another network node. This also specify if data should be transferred at
the start or end of trips, or not (in which case it can be extracted at a fixed scheduled time or manually).
Refer to the FM Professional documentation for more detail.

6. On the Device Properties->Transports Tab, select the Wireless Internet (GPRS, WiFi) as the default
Remote Data Transfer Transport. The FM Unit determines which link (GPRS or WLAN) to use, preferring
WLAN and using GPRS as backup option. You can specifiy Wi-Fi only, if you prefer.

The other options are available if you cannot link via Wireless LAN, but then you must select them here.
Again, refer to the FM Professional documentation for more detailed descriptions.

7. Refer to the documentation for details on the Device Properties->Roaming selections.

8. On the Device Properties->Power Tab, check the settings for power management and Battery voltage.
If the device detects battery input voltage below the threshold, it can disable the device, if powered via
Positive Drive. Also note that other devices may be powered from Positive drive as well, and these too
could disable Positive Drive and the Wireless Kit with it. Also double check the Automatic Shutdown
feature. If enabled, the Wireless Kit may be powered down after an amount of time.

----- Check the connection status: -----

1. By checking the LED status on the Wireless Kit (if it is accessible).

The Red LED blink if it is scanning for an Access Point, and stays lit if it is connected to (associated with)
an Access Point. The green LED is lit when an IP address is assigned to the Wireless Kit.

2. By checking the log files on the GPRSService computer. The log for each unit will indicate when a
connection was made and you can verify the assigned IP address, and unit information.

----- Troubleshooting: -----

1. The Wireless Kit antenna is located in a spot where there is no signal, e.g. inside the vehicle cabin or
boot.

2. The Wireless Kit is not powered up, either due to hardware failure (loose connection to Positive
Drive), or because the software is powering it down (Power Managment options for the devices)

3. The Wireless Kit has a communication failure, either due to hardware failure (the serial cable is
detached) or the Wireless Kit is assigned to the wrong port. It could also be due to a failure on the
antenna connection.

4. The Wireless Kit cannot log on to the Access Point. This could be due to authentication failure (wrong
method and/or password), wrong/mismatched SSID, wrong parameters on the Access Point settings.

5. The Server IP and/or port settings are wrong. Check the settings as defined in the FM Professional
device configuration dialog. Check the settings with the LAN administrator.

6. The server is not connected to the network. Check with the LAN administrator.

7. The GPRSService is not running. Check that the service is installed (part of the communications
Package) and enabled. Refer to the GPRSService documentation for details on setting up and operating
the GPRSService component.

8. The Wireless Kit is out of range of the Access Point. Under ideal conditions, a link can be established
at up to 500m. This requires a clear line-of-sight path. Any obstructions severely shortens this distance.
A safer margin would be 200m. If Wireless Kit units does not establish reliable connections, it would be
advisable to install more Access Points, evenly spaced on the site. The Wireless Kit firmware will
connect to the Access Point with the best signal strength. This enables a connection to complete data

1632
www.mixtelematics.com

1632
 1633

transfer, i.e. maintain the connection, even if the Wireless Kit unit is mobile between Access Points.

----- STATUS -----

FM Wireless Kit is supported from FM Professional V8.31 onwards.

------------------------------------------------------------------------------

KEYWORDS: CENTRE-POINT WiFi Wi-Fi Wireless IEEE802.11b IEEE802.11g Communication Link

1633
www.mixtelematics.com

1633
 1634
10.3.346 Knowledge Base Article 355

Article Number 355

Title FleetManager Professional 8.31 update 1

Created 12/2/2005 9:19:14 AM

Created By Jeremy Hartley (MiX Telematics - Stellenbosch)

Last Modified 1/31/2006 5:17:13 PM

Last Modified By Hans-Peter Schöpperle (MiX Telematics - Germany)

Details ----- APPLIES TO ----

· Fleet Manager Office 8.31 (October 2005)

· Fleet Manager Professional 8.31 (October 2005)

· Fleet Manager Communication Suite 8.31 (October 2005)

----- SUMMARY -----

This important update corrects several issues relating to vehicle configuration. This update should be
applied to all computers where the Fleet Manager Professional 8.31 or the Fleet Manager
Communication Suite 8.31 are installed.

----- MORE INFORMATION -----

The following issues have been identified and corrected in this update:

1. Configuration fails to generate after disabling GPRS from the GSM Modem properties.

2. No speed detected if GPS Velocity as Speed is 'only enabled while Ignition is on'.

3. 'Unknown Driver' listed against trips where a driver tag was used to identify the driver in the vehicle.

4. FM200 configuration fails to generate.

5. Unit configuration based Access Control may disarm if invalid plug removed too quickly while
checking access.

6. Changes to the roaming tab options are not saved when making changes to other tabs.

7. No speed or distance recorded when 'Copy vehicle as' function executed.

----- SOLUTION -----

The following steps should be followed to apply the update:

Download the FMOfficeKBA355.exe file.

Please note: BEFORE you install this update or update the database, please make sure that NONE of
the Fleet Manager components are running (I.e. ensure all the FM Downloaders, FM Services and
Autopoll are stopped and closed before installing this update).

1634
www.mixtelematics.com

1634
 1635

Ensure that the database settings are correct using the FM Administrator in Control Panel.

Run the downloaded executable file. This will install the update to the local computer and correct the
database being pointed to by the FM Administrator.

Important:

For a networked environment, the FMOfficeKBA355.exe should be copied to and executed on each
computer which has the Fleet Manager Professional 8.31 or the Fleet Manager Communication Suite
8.31 installed.

If there is more than one Fleet Manager database in use at a site, each database will need to be
updated.

In order to do this follow these steps:

1. Open Windows Explorer and navigate to the C:\Program Files\Common Files\Fleet Manager folder.

2. Open FM Administrator and modify the connection settings to point to the database to be updated

3. Find and execute the KBA355 FMPro8.31 Update 1.cmd file.

4. Repeat the two steps above for each database.

Notes:

1. The Program Files\Common Files is operating system language specific. (i.e. this applies to point 1.
above - i.e. in German, this would be Programme\Gemeinsame dateien etc).

2. If you have the 'Hide file extensions' feature of Windows Explorer turned on, please ensure you
execute the file of type 'Command Script'. (This applies to point 3. above).

Procedure to apply the update for specific issues

The following information only needs to be applied if you have experienced specific symptoms
mentioned in the More Information section of this KBA.

1. Configuration fails to generate after disabling GPRS from the GSM Modem properties.

After installing the Update, you need to reload the vehicle configuration for affected vehicles.

2. No speed detected if GPS Velocity as Speed is 'only enabled while Ignition is on'.

After installing the Update, you need to reload the vehicle configuration for affected vehicles.

3. 'Unknown Driver' listed against trips where a driver tag was used to identify the driver in the vehicle.

* Open the FM Software, and clear data for affected vehicles for the affected days (i.e. since the first
time ‘Unknown Driver’ was displayed erroneously until *today* (or the last time it was displayed
erroneously)) – to clear data for specific vehicles, use the ‘Clear Data’ function from the Organisation
Properties (Advanced tab).

* Then do a full download for affected vehicles

The correct driver should now be displayed.

4. FM200 configuration fails to generate.

This is rectified automatically with the installation of the Update.

1635
www.mixtelematics.com

1635
 1636

5. Unit configuration based Access Control may disarm if invalid plug removed too quickly while
checking access.

After installing the Update, you need to reload the vehicle configuration for affected vehicles.

6. Changes to the roaming tab options are not saved when making changes to other tabs.

This is rectified automatically with the installation of the Update.

7. No speed or distance recorded when 'Copy vehicle as' function executed.

* on vehicle properties (of for a group of vehicles, you can do this on a higher level - i.e. configuration
group level), go to the Devices tab, select a different speed input from the one you selected on F1,
apply this change. Then reselect the speed input you were using, and reapply your changes (if you did
this on a higher level than vehicle level, you have to cascade the applied changes to vehicles in that
group).

* reload the vehicle configuration

------------------------------------------------------------------------------

KEYWORDS: Communication Suite Professional Office 8.31 FM200 FM200Plus GPS Velocity Speed
Configuration Driver Identification

1636
www.mixtelematics.com

1636
 1637
10.3.347 Knowledge Base Article 356

Article Number 356

Title Modified GPRS Service for FM300 units

Created 1/11/2006 3:47:40 PM

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 1/19/2006 1:23:15 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM300 Communicator and FM300 Comlink-GSM units manufactured on or before week 2/06
(Please note: this does not affect FM300 Communicator units with battery).

----- SUMMARY -----

Part of the GUIDs written into the units on the production line have a fixed value which reduces the
uniqueness of the GUID and results in some duplication of GUIDs.

----- MORE INFORMATION -----

The FM GPRS Service is the only component of the FM solution that makes use of the GUID at this
time. The service utilises the GUID to uniquely identify a vehicle during a communications session.
There is a risk that two units with identical GUIDs connecting to the same GPRS Service may result in
data corruption (i.e. incorrect data being displayed in the database, or unit not downloading due to this
corruption).

----- CAUSE -----

Non-unique GUIDs on FM300 unit's firmware.

----- SOLUTION -----

1. A change has been made in the unit production process, and all units built on or after week 3/06 will
contain valid, unique GUIDs.

2. The GPRS Service has been modified to eliminate its dependency on GUIDs. Deploying the
modified GPRS Service provides an immediate solution to this problem. (Please download the new
GPRS service from the link below and follow the given instructions to ensure correct deployment of the
new service).

3. The modified GPRS service will be included in the FM Professional 8.3 Update 2 which is due for
release at the end of January 2006.

4. The FM device drivers will be modified to detect and correct corrupted GUIDs automatically. The
modified device drivers will be included in a new release of the FM Dealer Utility once they are
available. This will ensure that GUIDs are available for future use.

NEW FM GPRS Service

This section describes the deployment of the new GPRS Service

1637
www.mixtelematics.com

1637
 1638

Please note: This procedure should be repeated on all computers where the FM GPRS (WiFi) Service
is installed.

1. Ensure all services on the FM Service Manager is stopped (i.e. stop the "Fleet Manager Wireless
Data Processing Service" and "Fleet Manager Wireless Internet Service").

2. Please download the following file and extract it to a certain folder on your computer: KBA356.zip
(This zip contains three files: GPRSService.exe, FmDataProcessor.exe and FmSvrCpp.dll)

3a. Copy GPRSService.exe and FmDataProcessor.exe to the "C:\Program Files\Common Files\Fleet

Manager Services\GPRS Service\" folder (overwrite the existing two files with these two files).

3b. Copy FmSvrCpp.dll to the "C:\Windows\System32\" folder - also overwriting the existing file.

4. After successfully copying and overwriting these three files, please restart your GPRS service.

If any data corruption occurred in you database, please follow the instructions below to correct this.

Correcting corrupted data in database after deployment of new GPRS Service

You only need to follow these instructions if the data in your database has been affected (i.e. incorrect
data downloaded for specific vehicles).

1. Clear data for the affected vehicles for the affected time period (you can clear data in the database
by using the Clear data function from the Advanced section of the Organisation properties).

2. Once the affected data has been cleared, schedule a full data download for affected vehicles. All the
data in the FM unit will be downloaded correctly (provided the data is still in the unit -i.e. have not been
overwritten with new data yet).

----- STATUS -----

Only applicable to customers with affected units who do not subscribe to the Bureau service.

Only FM300 Communicator and FM300 Comlink-GSM units manufactured on or before week 2/06.

All units built on or after week 3/06 will contain valid, unique GUIDs.

The FM device drivers will be modified to detect and correct corrupted GUIDs automatically.

------------------------------------------------------------------------------

KEYWORDS: FM300 GUID GPRS Service

1638
www.mixtelematics.com

1638
 1639
10.3.348 Knowledge Base Article 357

Article Number 357

Title GPRS package number

Created 1/30/2006 4:57:47 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 1/30/2006 5:22:49 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Wireless Internet (GPRS) Service using FM GPRS Gateway

----- SUMMARY -----

This KBA describes the GPRS package number and how to use it.

----- MORE INFORMATION -----

When you are using the FM GPRS Gateway, it is necessary to have a valid GPRS Package number,
or your connection to the FM GPRS Gateway will not be successful.

If you do not have a valid FM GPRS Gateway package, please contact your dealer to purchase a new
GPRS Package.

Once you have your GPRS Package, you need to register it as described in the Solution section of this
KBA.

----- CAUSE -----

The FM GPRS Gateway has been updated to only allow users with a valid GPRS Package to connect
to the it.

----- SOLUTION -----

Once you have obtained your valid GPRS Package from your dealer, please register it as described
below:

1. go to the www.upgrade-plus.com website

2. select the option to View Package Information and use your own Upgrade-Plus package number to
enter the site and 'view' your own details.

3. now on the Add Extensions tab, enter the new GPRS package number and click Validate.

Once you have a valid GPRS Package registered, you can use any of the Upgrade-Plus package
numbers to connect to the GPRS Gateway (from the GPRS Service properties).

----- STATUS -----

This change was announced in June 2005, and has now been implemented on the FM GPRS

1639
www.mixtelematics.com

1639
 1640

Gateway.

------------------------------------------------------------------------------

KEYWORDS: FM GPRS Gateway Service Connecting

1640
www.mixtelematics.com

1640
 1641
10.3.349 Knowledge Base Article 358

Article Number 358

Title Timeout on device driver upload via GPRS

Created 1/31/2006 12:08:17 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 8/24/2007 8:52:06 AM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· Device drivers supplied with FM8.31 (FM Dealer version 8.3.1.0 and device driver sets version
5.10.31.x)

----- SUMMARY -----

Timeouts during GPRS data transfer sessions may be caused by the above-mentioned device driver
set.

----- MORE INFORMATION -----

If an FM unit experiences regular timeouts when connecting via GPRS, the above-mentioned device
driver set should be replaced.

Timeouts on GPRS communication is normal, but with the specified device driver set, a
communications timeout may occur more regularly.

----- CAUSE -----

Time before communications timeout is reported is too short.

----- SOLUTION -----

As a current workaround, you need to reinstall the device driver set released with FM8.12 (FM Dealer
version 2.11.5.0 with firmware set version 5.3.22.0).

If you do not have a copy of this version of the FM Dealer, please download it from www.omnibridge.
com.

Once you have this version of the FM Dealer installed, please do a manual (plug) upload of all your
device drivers to affected units.

Please note

This device driver set (version 5.3.22.0) does not include support for WiFi, but other than that should
be fine with the FM8.31 software.

----- STATUS -----

A new set of device drivers will allow for a longer timeout period before breaking off communications.

1641
www.mixtelematics.com

1641
 1642

------------------------------------------------------------------------------

KEYWORDS: GPRS Upload device drivers DDX DDR Config Configuration FM FM8 Wireless
Service

1642
www.mixtelematics.com

1642
 1643
10.3.350 Knowledge Base Article 359

Article Number 359

No speed recorded when 'only consider gps as speed when ignition is turned on'
Title
option is selected

Created 2/14/2006 6:19:42 PM

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 3/2/2007 10:30:30 AM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM8.21

· GPS velocity as speed

----- SUMMARY -----

When selecting "only consider gps as speed when ignition is turned on" option in the GPS velocity
as speed tab, no speed is recorded on a vehicle.

----- MORE INFORMATION -----

The device drivers installed with FM8.21 (version 5.8.4) does not record speed when selecting "only
consider gps as speed when ignition is turned on" with GPS velocity as speed.

The device drivers for FM8.12 (5.3.22) and FM8.31 (5.10.31) works correctly.

----- CAUSE -----

Version 5.8.4.0 is incompatible with this feature because the "ignition on" condition was introduced
to be supported by 5.10.31.0.

----- SOLUTION -----

The issue only exists with the option to disable GPS as velocity when the Ignition is off (preventing
trips from being recorded when the GPS signal is weak and calculated small speed readings) with a
device driver set older than 5.10.31.0. Sets older than 5.8.4.0 had less functionality and is not
influenced by this feature, so also worked.

----- STATUS -----

The ignition setting will only work if FM8.3 device drivers (5.10.3) are uploaded.

------------------------------------------------------------------------------

KEYWORDS: GPS velocity as speed Device Drivers Ignition

1643
www.mixtelematics.com

1643
 1644
10.3.351 Knowledge Base Article 360

Article Number 360

Title FM Terminal 2006

Created 3/7/2006 1:57:29 PM

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 4/3/2006 12:11:14 PM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

FM Terminals dated from January 2006. At the back of the terminal is a number, giving the
production week and year, for example 01-06 would be the first week of 2006.

----- SUMMARY -----

When the device drivers of FM8.31 (or prior version of the software) is loaded onto one of these new
terminals, the terminal shuts down, displaying the message "No ddr's loaded".

----- MORE INFORMATION -----

The firmware loaded onto the FM Terminals is not available in the device drivers set of FM8.31
dealer utility (or prior versions).

----- CAUSE -----

The FM Terminals produced in 2006 use firmware version 2. The device drivers in the current
released software contains FM terminal firmware version 1.6. If these device drivers are loaded onto
the FM Terminal, and overwrites the factory issue device drivers, the terminal can not be used.

----- SOLUTION -----

If the terminal displays the following message: "No ddr's loaded", download the plugdump from the
link below, restore this plugdump, and upload to the FM unit (and FM terminal).

1) Download the FMTerminal.zip file.

2) Unzip this file and restore to a green plug (see KBA#67 for more information on plugdumps).

3) Upload the drivers to the FM unit to update the FM Terminal (by inserting the plug into the
vehicle's socket).

----- STATUS -----

After you have successfully loaded the Drivers as per the above procedure, your FM Terminal should
function correctly.

These device drivers will be included in the next version of the FM software.

------------------------------------------------------------------------------

1644
www.mixtelematics.com

1644
 1645

KEYWORDS: FM Terminal Device drivers ddr

1645
www.mixtelematics.com

1645
 1646
10.3.352 Knowledge Base Article 361

Article Number 361

Title Specific Absorption Rate of Fleet Manager Products

Created 4/12/2006 4:49:18 PM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 4/18/2006 2:13:28 PM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Specific Absorption Rate (SAR) of all FM products incorporating GSM transmitters.

----- MORE INFORMATION -----

Transmitters incorporating a GSM module must be in accordance with the guidelines for human
exposure to radio frequency energy. This requires the Specific Absorption Rate (SAR) of handheld
applications to be evaluated for compliance with national and/or international regulations, provided
radiating parts are within 20cm of the human body under normal operating conditions.

----- STATUS -----

Due to the fact that FM products are not used within 20cm of the human body, this value has not been
determined.

------------------------------------------------------------------------------

KEYWORDS: FM300 FM200 Communicator SAR Radiating OET65 Specific Absorption Rate

1646
www.mixtelematics.com

1646
 1647
10.3.353 Knowledge Base Article 362

Article Number 362

Title Digital Hands Free Kit

Created 4/13/2006 10:34:33 AM

Created By Warren Tieling (MiX Telematics - Stellenbosch)

Last Modified 6/1/2006 12:21:02 PM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 and FM300 Series Units and Digital Hands Free Kit

----- SUMMARY -----

When making or receiving a call,the voice call tends to be ended unexpectedly.

----- MORE INFORMATION -----

Digital hands-free kits constantly need to be physically reset.When calls are ended ,kits seem to
freeze with one caller not hearing the other and vice versa -After unplugging and re-plugging it,phone
works again.

----- CAUSE -----

The cause was described as the "Brownout"

We have found that the DHFK (Digital Handsfree Kit) does not make proper use of "Brownout"
detection. The definition for this is:

"A condition where the voltage supplied to the system briefly falls below the specified operating
range, but above 0 Volt."

This brownout condition happens when you turn the key in the ignition.The standing voltage might be
12.5 volt, but when ignition and the engine is started the supply(battery) voltage will briefly drop to 7
volts (This is a result of high current required by the starting circuit of the vehicle. It varies from
vehicle to vehicle and would be worse in older vehicles.)

Please note that the voltage supplied from out FM unit to the DHFK is ~1 volt lower than the supply
voltage (battery).

----- SOLUTION -----

CI-MiX Telematics designed a cable known as the Junction Cable/Extender. The extender is
basically a straight through pin-to-pin configuration with just the Power line being routed externally.

Download the FM300VoiceHarnessExtender.zip file.

----- STATUS -----

The Junction Cable/Extender has been tested and confirmed to be acceptable work around.

1647
www.mixtelematics.com

1647
 1648

------------------------------

KEYWORDS: FM200 FM300 DHFK HFK Digital Hands Free Kit Handsfree kit voice calls

1648
www.mixtelematics.com

1648
 1649
10.3.354 Knowledge Base Article 365

Article Number 365

Title Changing From GSM or GPRS Modem Function Beneath Roaming

Created 9/26/2006 2:58:11 PM

Created By Warren Tieling (MiX Telematics - Stellenbosch)

Last Modified 10/25/2006 9:33:18 AM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM8.32 Vehicle Properties Roaming Functionality

----- SUMMARY -----

Error when making selection under the Roaming Tab within the FM8.32 software

----- MORE INFORMATION -----

When a user goes within the GSM Modem functionality "vehicle properties" & selects to either change
GSM or GPRS - modem functions.

----- CAUSE -----

1. Set up a new vehicle (FM300 Comm) within the FM8.32 software

2. Open the "Devices" tab, then the settings for the GSM modem

3. Chang to the "Roaming" tab

4.Select the option "Show all detailed options"

5.Unselect all options

6. Select just the option "GPRS" under "All GSM Modem functions" or "GSM" only

7. Then "ok" ; "Apply" and again "OK"

8. When the Vehicle settings menu was closed I opened it again and looked into the Roaming settings -
> Roaming settings were still ok (as selected before)

9. Close the "device window" and the "Vehicle properties window" with "ok"

10. When you now open the Vehicle properties and select "EDIT" GSM Modem - Select Roaming,other
functions are then too enabled.

----- SOLUTION -----

The workaround to get the options into the correct state:

1) Open the GSM Modem Device properties and go to the Roaming page.

1649
www.mixtelematics.com

1649
 1650

2) Mark ALL options on.

3) Click OK to close device, then APPLY to save options to database.

4) open the GSM Device properties again, and go to Roaming page.

5) uncheck any options required to be off (in this case all but the "All GSM Modem - GPRS" option.

6) Click OK to close device, then OK/Apply to save to database.

----- STATUS -----

Besides for the "workaround", this fix is under construction for future release

------------------------------------------------------------------------------

KEYWORDS: FM8.32 Fleet Manager Roaming Selection Vehicle Properties GSM GPRS Function

1650
www.mixtelematics.com

1650
 1651
10.3.355 Knowledge Base Article 366

Article Number 366

Title FM 100 device configuration does not reflect buzzer settings

Created 10/25/2006 10:34:31 AM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 10/25/2006 10:34:31 AM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details ----- THIS KBA IS CURRENTLY UNDER CONSTRUCTION -----

----- APPLIES TO ----

· Fleet Manager Professional 8.32

· FM100

----- SUMMARY -----

FM 100 device configuration does not reflect buzzer settings.

----- MORE INFORMATION -----

The FM 100 buzzer sounds continuously when the ignition is turned on, regardless of the
configured calibration settings. When changing the buzzer settings, it does not reflect on the
configuration script.

----- SOLUTION -----

FM-Lite should be used as a temporary work-around to effectively update the buzzer settings.

----- STATUS -----

This will be included in the next release of the software.

------------------------------------------------------------------------------

KEYWORDS: Fleet Manager FM8 FM100 buzzer calibration settings

1651
www.mixtelematics.com

1651
 1652
10.3.356 Knowledge Base Article 367

Article Number 367

Title FM Locator GPS issue

Created 10/25/2006 10:37:16 AM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 8/28/2007 11:15:40 AM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 Locator, FM8.32, Device driver version 6.6.14

----- SUMMARY -----

No GPS when uploading via GPRS using the FM Comms Scheduler.

When attempting to do an upload making use of the FM Locator via GPRS, no GPS points are
received. When an upload is performed by means of a code plug, GPS points are available.

----- MORE INFORMATION -----

Uploading the device driver of FM8.32 to the FM Locator unit via GPRS, causes the GPS to fail i.e.
the GPS diagnostics plug will not result in the required 2 beeps. The device drivers can however be
successfully uploaded by means of a green plug.

----- CAUSE -----

Upgrading DDR’s from FM8.12 (version 5.3.22) to FM8.32 (prior to version 6.7.6) via GPRS cause
the GPS to fail on FM200 locators.

----- SOLUTION -----

Please download the following: Locator Device Drivers.

On the PC that the GSM/GPRS service is installed, open the included ZIP file.

Navigate to the Fleet Manager directory that contains all the sets of firmware (.DDX files), and back
them up (a typical path to this directory is: “C:\Program Files\Common Files\Fleet Manager”)

Replace the contents of each of the relevant directories with the contents of the directories in the file
(just unzip the files into the parent directory).

Test by doing a GPRS/GSM upload to a FM Locator vehicle to ensure the procedure has been
followed correctly.

----- STATUS -----

The new FM Dealer was uploaded to www.omnibridge.com.

------------------------------------------------------------------------------

1652
www.mixtelematics.com

1652
 1653

KEYWORDS: FM200 Locator FM8.21 FM8.32 GPS GPRS Upload DDR Device Drivers

1653
www.mixtelematics.com

1653
 1654
10.3.357 Knowledge Base Article 368

Article Number 368

Title GSM downloader is causing a GPF if modems other than MC35 are used

Created 10/25/2006 10:39:36 AM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 4/24/2007 11:10:42 AM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager GSM Downloader, FM8.32

----- MORE INFORMATION -----

The GSM downloader is causing a General Protection Fault (GPF) if modems other than MC35 are
used. While in use, the GSM Modem shuts down unexpected.

----- SOLUTION -----

1. Stop the GSM downloader.

2. Rename the current FMDialer.dll (typical path: C:\Program Files\Common Files\Fleet Manager
\FMDialer.dll)

3. Download the new FMDialer.dll (ver 8.32.0.2) from the following link: FMDialer.zip.

4. Copy the downloaded file to the same location as where the original .dll is situated.

----- STATUS -----

By loading the above mentioned .dll the GSM downloader (version 8.31.0.5) will be compatible with
all modem types.

This functionality will be officially incorporated in the next release.

------------------------------------------------------------------------------

KEYWORDS: GPF MC35 FM GSM Downloader

1654
www.mixtelematics.com

1654
 1655
10.3.358 Knowledge Base Article 369

Article Number 369

Title Regional settings on Google Earth

Created 10/25/2006 10:42:06 AM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 10/27/2006 10:09:25 AM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details
----- THIS KBA IS CURRENTLY UNDER CONSTRUCTION -----

----- APPLIES TO ----

· Fleet Manager Professional 8, Mapviewer, Google Earth

----- SUMMARY -----

Google Earth may display incorrect behaviour if used with regional settings other than English.

----- MORE INFORMATION -----

English regional settings uses “.” as the decimal separator, where some other language settings have
“,” as a decimal separator. This may affect the functionality when Google Earth is used with Mapviewer.

----- SOLUTION -----

As a workaround, change the regional settings to English, or ensure “.” is selected as the decimal
separator.

Or download the Mapviewer dll from the following link: FMGPSCIR.dll

In the C:\Program Files\Fleet Manager Professional\ folder,

1. Unregister the FMGPSCIR.dll as follows: start -> run -> and type in -> regsvr32 /u "C:\Program Files
\Fleet Manager Professional\FMGPSCIR.dll"

2. Copy the attached dll into that folder

3. Register the new dll as follows: start -> run -> and type in -> regsvr32 "C:\Program Files\Fleet
Manager Professional\FMGPSCIR.dll"

4. Change the regional settings to the required language

5. Open FM Professional as listed above

6. The kml will successfully plot the route in Google Earth

----- STATUS -----

This will be corrected in the next release of the Fleet Manager software.

1655
www.mixtelematics.com

1655
 1656

------------------------------------------------------------------------------

KEYWORDS: FM8.32 Mapviewer Google Earth

1656
www.mixtelematics.com

1656
 1657
10.3.359 Knowledge Base Article 370

Article Number 370

Title Error when generating a locations report using reverse geo lookup

Created 10/25/2006 10:44:16 AM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 3/12/2007 11:48:42 AM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Professional 8.32, GPS Logviewer 8.3 (March 2006 release)

----- SUMMARY -----

When generating a Locations Report using Reverse geo lookup an error message is displayed.

----- MORE INFORMATION -----

When generating a Locations Report, on the “More Options” tab of Location Reports wizard: select "Use
GIS data to try to find names for unidentified locations". The following error message is displayed:

“An error occurred while initializing Microsoft Map Point. Map Point 2002 must be installed. The GIS
lookup function is disabled for this report.”

----- CAUSE -----

This is a generic message, with no actual reference to Microsoft Map Point. The GPS Logviewer is not
initialised via the Locations report, only when the maps are opened in the Logviewer.

----- SOLUTION -----

As a workaround, first open the Logviewer to view the maps. (You could minimise this). Then generate
the Location Report as usual. The other alternative is to download the new dll from the following link [
FMOfficeKBA370.zip] and then to overwrite the Logviewer FMGPSCIS.dll file.

----- STATUS -----

The functionality is correct using GPS Logviewer 8 (April 2005 release). This will be corrected in the
next release of the Fleet Manager software.

------------------------------------------------------------------------------

KEYWORDS: FM8.32 GPS Logviewer 8.3 March 2006 Location Report Reverse geo GIS Mappoint

1657
www.mixtelematics.com

1657
 1658
10.3.360 Knowledge Base Article 371

Article Number 371

Title DECT downloader issues

Created 10/25/2006 10:47:13 AM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 8/3/2007 9:37:29 AM

Last Modified By Portia Roro (MiX Telematics - Stellenbosch)

Details ----- THIS KBA IS CURRENTLY UNDER CONSTRUCTION -----

----- APPLIES TO ----

· Fleet Manager Communication Suite 8.32 (Dect Downloader, Autopoll)

----- SUMMARY -----

In some cases DECT data files do not get converted to Autopoll file format.

----- MORE INFORMATION -----

The following issues have been identified and corrected in version 8.31.0.7 of FMDectPro.exe:

1. In some cases the downloaded data files from the DECT are not converted to Autopoll file format.
The Autopoll directory is created successfully, however ‘tmp’ or ‘tmp.back’ files are created in the
Autopoll folder for the Dect e.g. DECTDL_c0_V1_12698.tmp

Only after stopping and starting the DECT, these files will disappear. These tmp files may randomly
reappear the next time a download is performed.

2. At times, when doing an upload via DECT, it may result in the following error while setting new
Tacho configuration: ERROR: FM_Comms_CommandToFm in UploadConfigToFM200 failed.
Error=FM_COMMS_ERR_COMMS_TIMEOUT

----- SOLUTION -----

The following steps should be followed:

Download the FMDECTPro.exe file.

Please note: BEFORE you install this , please make sure that NONE of the Fleet Manager
components are running (I.e. ensure the Dect Downloader, FM Professional and Autopoll are stopped
and closed before replacing the current FMDectPro.exe with this new one version 8.31.0.7).

1. If this behaviour is experienced, replace the FMDectPro.exe currently installed with the new
FMDectPro.exe version 8.31.0.7

2. Open Windows Explorer and navigate to the 'C:\Program Files\\Fleet Manager Communications
Suite\Fleet Manager DECT Downloader' folder and replace

the current FMDectPro.exe with the new FMDectPro.exe (version 8.31.0.7)

1658
www.mixtelematics.com

1658
 1659

Important :

Once the exe is replaced, the install might want to recover. Please CANCEL the attempted recovery,
to prevent it from reverting back to the original exe.

----- STATUS -----

This will be corrected and included in the next release of the software.

------------------------------------------------------------------------------

KEYWORDS: Communication Suite Professional Office 8.32 (FM Dect Downloader, Autopoll)

1659
www.mixtelematics.com

1659
 1660
10.3.361 Knowledge Base Article 372

Article Number 372

Title Issues while upgrading a FM2002 database

Created 10/25/2006 10:50:30 AM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 1/23/2007 3:52:44 PM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager 2002 Database, Fleet Manager Administrator, FM8.31 and FM8.32

----- SUMMARY -----

FM8.31 and FM8.32 cannot upgrade FM2002 databases.

----- MORE INFORMATION -----

The following error occurs when upgrading from a FM2002 database to a FM8.31 or FM8.32
database:

An unexpected error occurred:

Error -2147199229 - [SQL-DMO][Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object

name 'DeviceProperties'. occurred in FMDatabase.UpdateDatabase (Line 30600). The error has
been logged.

As a result, the will upgrade fail.

----- SOLUTION -----

This has been fixed for the next release of Fleet Manager Professional by amending the FMDB8.
ZQL

1. As a current workaround the FM2002 database can be restored to FM8.11, FM8.12 or FM8.21

2. Once the database was upgraded to any of the above mentioned versions, one should then be
able to restore this database to FM8.31 or FM8.32

----- STATUS -----

This will be corrected in the next release of Fleet Manager Professional.

------------------------------------------------------------------------------

KEYWORDS: FM 2002, FM 8.31, FM8.32 and Fleet Manager Administrator

1660
www.mixtelematics.com

1660
 1661
10.3.362 Knowledge Base Article 373

Article Number 373

Title FM300 GSM modem does not wake up

Created 11/14/2006 6:27:26 PM

Created By Winston Arendse (MiX Telematics - Stellenbosch)

Last Modified 11/14/2006 6:39:33 PM

Last Modified By Winston Arendse (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM300 Communicator, FM300 Communicator-Battery, FM300 GSM Comlink

----- SUMMARY -----

Modem does not wake up; Cannot connect to Device via GSM

----- MORE INFORMATION -----

This explicitly refers to cases where FM unit does not have Power Managment enabled and the vehicle
has stood for a number of days. not started. Modem does not power up, ie Red LED does not flash OR
unit does not upload/download OTA.

----- CAUSE -----

This occurs when "total unit shutdown" has not taken place for an excess amount of days while the
vehicle stood, not started, over the same period of time. The FM unit subsequently discharged the
vehicle's battery, then its own backup battery in the case of an FM300 Communicator-Battery. When the
vehicle is eventually started, due to the low voltage of the vehicle's battery, more current is required to
crank the motor causing a current spike to flow through the current-sensing circuitry of the FM unit. In
most cases, this causes the protection of the positive drive circuit to come into effect, constantly
switching power to the peripheral devices on the FM unit, including the GSM modem, causing the
modem to lose its firmware and fail to start.

However, in some occurrences, the current spike damages the current sensing circuit on positive drive.

----- SOLUTION -----

It is encouraged to enable the power management features of the FM units to avoid, amongst other
problems, vehicle battery discharge.

Where the GSM modem "lost" its Firmware, please reload the relevant device driver set using the Green
CodePlug.

----- STATUS -----

To date, the problem has only taken place at 1 site, where most of the units have been fixed by
reloading the device drivers.

1661
www.mixtelematics.com

1661
 1662
10.3.363 Knowledge Base Article 374

Article Number 374

FM300 Communicator stops running after attempting remote device drivers

Title
uploads

Created 11/16/2006 7:23:13 AM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 12/4/2006 2:33:51 PM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

Products most likely to be at risk are:

· 450FT0501-04 – FM300 Communicator: S/N: CGNA08369 Week: 29/2006 onwards

· 450FT0502-04 – FM300 Communicator – Battery: S/N: CGBA17196 Week: 30/2006 onwards

· 440FTT402-01 – Tripmaster 3310: S/N: T4020143 onwards

----- SUMMARY -----

A problem with the FM300 Communicator operating system firmware results in communication to
the unit to cease when remote device driver uploads is attempted. The unit is rendered in operating
system mode and must be restored with a manual re-upload of firmware using a code plug.

----- MORE INFORMATION -----

The problem is indicated by the following symptoms:

1) The Code Plug Socket LED flashing on for a second and off for an eighth of a second without
any buzzer beeps indicating that it has no device driver firmware loaded.

2) The vehicle unit stopped communicating soon after a recent device driver upload was
attempted.

----- CAUSE -----

The issue is caused by a FM300 Communicator operating system firmware problem. The device
driver uploads fail during the last stages preventing roll back of the unit and disabling all
communication to the unit.

----- SOLUTION -----

The solution is downloading FM Dealer Utility 8.3.2.2 or later, and following these instructions:

1) Isolate all faulty stock and upload the device drivers to all faulty units using a Device Driver
Code Plug only.

2) When possible upload device drivers to all installed faulty units using a Code Plug.

1662
www.mixtelematics.com

1662
 1663

3) Upload device drivers to all existing installations that have already lost its device drivers (long
flashing LED and communications lost).

4) Verify all units by checking that the Firmware-set Version is 6.11.16.x.

5) Clearly mark the updated units when returning it to stock.

----- STATUS -----

For vehicles units installed in vehicles that are difficult to reach an over-the-air workaround method
is being investigated.

------------------------------------------------------------------------------

KEYWORDS: Uploading Device Drivers, FM300 Communicator

1663
www.mixtelematics.com

1663
 1664
10.3.364 Knowledge Base Article 375

Article Number 375

Title General networking principles for Fleet Manager installations

Created 12/5/2006 10:58:17 AM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 4/4/2007 10:51:41 AM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- SUMMARY -----

This article includes some useful information for Fleet Manager installations and configurations in terms
of database permissions as well as some detailed security configuration steps.

----- MORE INFORMATION -----

MSDE is not required to be installed on the client PC. Only the SQL Client tools needs to be installed.
Please note that use of the MSDE in a networked client-server environment (as opposed to running with
FM on a single PC) is a technical violation of the Microsoft licensing agreement. SQL Standard edition
should be used for a distributed network as a minimum.

Connectivity on the client only requires the client software installation. MDAC should already be installed
on the PC. Currently the FMAdministrator (where one configures database connections) requires the
client connectivity tools to be installed on the desktop. To work around this, we need to redevelop the
FMAdministrator configuration tools to be SQL Native Client only.

Windows Firewall should not be switched off on a machine simply because the FM software is installed. It
does not need to be turned off on a 'server' running MSDE or a SQL Server. However, it would need to be
configured to allow TCP access to the server (and this can be limited to a specific subnet), as well as
allow incoming requests to the SQL Server.exe. In MSDE and other, the Default TCP Port is 1433 for
SQL. As this can be configured by any network administrator/DBA, the connectivity settings are the
responsibility of the user/network, and not the vendor (CI or FM).

The user does not need to be an administrator on the client PC where FM is installed to work with the
software (although it must be installed by an administrative account). Also note that read/write/delete
privileges will need to be given to the user to read and write from the registry hive
HKEY_LOCAL_MACHINE\SOFTWARE\Data Pro Development (Pty) Ltd. This does not include
communications suite software, which is an administrative function.

Members of the public role on any given database are sufficient for using the software. As previously
mentioned, administrative rights are not required or recommended. However, for system tasks such as
creating the database and/or upgrading the database, administrative rights will be needed.

For performing backups, the backup role is sufficient. Database restores also require explicit
permissions.

The windows user would ONLY require access to the Fleet Manager database.

There is some concern over dynamic SQL statements and the level of permissions required. By default,
the public role on the database will allow execution of these statements (the SDK wholly uses dynamic
SQL, and some extensions have these embedded). This is currently undocumented and non-specific.
Unfortunately this would be a trial and error approach, but it is anticipated that the impact of this would be

1664
www.mixtelematics.com

1664
 1665

almost negligible (and possibly none at all), if the windows user is a member of the public database role.

As previously noted, use of the MSDE in a distributed client-server environment violates the licensing
agreement with Microsoft. While there are tools available for administering the MSDE anyway (including
Microsoft utilities, such as Enterprise Manager for pre-2005 SQL versions and Management Studio for
SQL 2005 or later) this also violates the licensing agreement. The use of osql (a command-line utility
distributed with the MSDE) is supported, but knowledge of T-SQL is required for its use. Other utilities to
administer windows security are all part of the Active Directory tools that are part of standard windows AD
domain account administration.

------------------------------------------------------------------------------

KEYWORDS: MSDE OSQL Roles Networking principles Installations

1665
www.mixtelematics.com

1665
 1666
10.3.365 Knowledge Base Article 376

Article Number 376

Title How to enable WiFi Diagnostic information on the FM Terminal

Created 12/6/2006 4:17:57 PM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 1/26/2007 8:44:50 AM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· FM200 and FM300 series

· FM Wireless Kit

----- SUMMARY -----

This article briefly explains how to configure your FM Terminal to be able to display specific diagnostic
related information at the time of inserting the WiFi diagnostic plug into the code plug socket.

----- MORE INFORMATION -----

Please download the following: WiFi Diagnostic script & ddm.

(1) Setup your e.g. FM300 Communicator with a FM Terminal & WiFi kit (connected to S3 on FM300).
See KBA#353 for more info on setting up WiFi.

(2) Paste the CidevBig.fmt file into your FMTerminal folder (under C:\Program Files\Common Files
\Fleet Manager\).

(3) In the FM Software, under Devices, go to -> Terminal -> Script --Select the ‘CidevBig.fmt’ script from
the dropdown list.

(4) Load the config onto the unit by means of a vehicle plug.

(5) In the dealer utility:

- Format a Device Driver plug

- Go to 'Load Device Drivers' -> 'Browse' to the location where your SCRIPT.DDM file is saved, and
Load it onto the plug

(6) Load the drivers onto the unit by inserting the driver plug into the vehicle plug socket.

The last step is to create a WiFi diagnostics plug with the dealer utility and to insert it into the vehicle
plug socket.

On the Terminal, under menu option 6 ("Diagnostics"), the following fields will be displayed:

Diag Plug Type

1666
www.mixtelematics.com

1666
 1667

Signal Strength (Measured in dBm. The higher the number, the stronger the signal.)

Port Status -Current MAC Port Connection Status, where...

1 = disabled

2 = searching for initial connection

3 = Connected to IBSS

4 = Connected to ESS

5 = out of range (in ESS)

8 = started host AP

Link Status -Wireless Local Network Status, where...

0 = Association not yet completed

1 = Connected

2 = Disconnected

3 = AP change

4 = AP out of range

5 = AP in range

6 = Association failed)

DHCP Status

0 = DHCP is disabled

1 = DHCP is in the process of leasing an address

2 = DHCP has leased an address

Company ID

----- STATUS -----

This will be incorporated in the next release of the software.

------------------------------------------------------------------------------

KEYWORDS: FM200 FM300 Communicator Wireless kit WiFi diagnostics Terminal

1667
www.mixtelematics.com

1667
 1668
10.3.366 Knowledge Base Article 377

Article Number 377

Title Upgrade Plus Registration information and FAQ

Created 12/11/2006 1:09:41 PM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 12/12/2006 2:41:12 PM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· All FleetMananger Software Packages

----- SUMMARY -----

This article contains some guidelines on registering your new FM Software/Extensions, as well as a
number of related frequently asked questions (FAQ).

----- MORE INFORMATION -----

Go to www.upgrade-plus.com

1) Registering new FM software

1.1) Registering a new company from scratch:

Click on Activate Upgrade + Package -> select Activate your first FM Upgrade+ package -> type in the
package number -> submit & follow the prompts

1.2) Registering an existing company for additional vehicles or new version of the software:

Click on View Package information -> select I want to view Package Information for my Upgrade+
Package -> type in a previously registered package number -> click on Add Packages -> type in a
NEW package number -> submit.

2) Registering new extensions

2.1) Registering GPS Logviewers / Mapviewer / GPRS package:

Please ensure you have the Upgrade + (software package) registered. Click on View Package
information -> select I want to view Package Information for my Upgrade+ Package -> type in a
previously registered package number -> click on Add Extension -> validate -> select type of package.

2.2) Registering Remote Client:

Click on Activate FM Extension Package -> select I have not registered a FM Extension or Upgrade+
Package before -> type in the package number -> submit and follow the prompts.

----- FREQUENTLY ASKED QUESTIONS -----

Q: How do I register a new company from scratch?

1668
www.mixtelematics.com

1668
 1669

A: Click on Activate Upgrade + Package -> select Activate your first FM Upgrade+ package -> type in
the package number -> submit & follow the prompts.

Q: How do I register additional / new version packages on an existing company?

A: Click on View Package information -> select I want to view Package Information for my Upgrade+
Package -> type in a previously registered package number -> click on Add Packages -> type in a
NEW package number -> submit.

Q: How do I register my GPS Logviewers / Mapviewer / GPRS package?

A: Please ensure you have the Upgrade + (software package) registered. Click on View Package
information -> select I want to view Package Information for my Upgrade+ Package -> type in a
previously registered package number -> click on Add Extension -> validate -> select correct type of
package.

Q: How do I view my current registration?

A: Click on View Package information -> select I want to view Package Information for my Upgrade+
Package -> type in a previously registered package number -> click on Registration details -> type in a
package number -> submit.

Q: Why did the Extension package not register for a whole year?

A: You have entered a NEW package number before the existing package expired, i.e. you have
registered double the users for half the period.

Q: Why don’t the number of vehicles add up to the total number of packages registered?

A: You have registered packages for different versions of the software, i.e. only the number of vehicles
for the latest version of the software will be registered.

Q: When will the packages expire?

A: “Old” packages (versions prior to FM8.3) expire after 1 year, can be extended on the same version
of the software on request.

Version specific packages (FM8.3 onwards) expire after 3 years; can be extended on the same version
of the software on request.

GPS logviewer packages expire after 1 year can be extended with a RENEWAL package.

Mapviewer packages expire after 10 years.

GPRS packages expire after 1 year.

Q: What happens if the packages expire?

A: Dealer packages (NFR) will lock the software after expiry date.

GPS logviewer / Mapviewer packages will lock the software after expiry date.

Upgrade-plus packages will prompt the user to upgrade/extend after the expiry date.

Q: I receive an error message when typing in the registration details.

A: Please ensure you have entered the company name and unlocking code exactly as it appears on
the www.upgrade-plus.com website. This registration is case sensitive and does not allow for leading
or trailing spaces.

1669
www.mixtelematics.com

1669
 1670

Please ensure you have registered the correct version of the software.

Please ensure the Mapviewer registration code is linked to the Upgrade-plus registration.

Q: Who requires a GPRS package?

A: Only customers connecting via the GPRS gateway hosted by Control Instruments (CI).

Important: Bureau customers using FM Pro in Remote mode:

The software and mapviewers will be registered by CI, and can be opened by typing in the FM-Web
username and password only.

----------------------------------------------------------------------------------------

KEYWORDS: Upgrade plus registration FAQ GPS logviewer mapviewer package upgrade expire

1670
www.mixtelematics.com

1670
 1671
10.3.367 Knowledge Base Article 378

Article Number 378

Title Allowing a user with standard user permissions to use Fleet Manager 8 software

Created 4/20/2007 10:14:56 AM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 4/20/2007 10:27:37 AM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Office 8

----- SUMMARY -----

This article will aid as a step by step guide to help you (the administrator) to grant the essential file
permissions(without administrative rights) to a user for him/her to be able to access the Fleet Manager
8 software application.

----- SOLUTION -----

1.1 Make sure you are logged on with Administrator privileges.

1.2 Open file explorer

1.3 Browse to and right-click on: ‘C:\Program Files\Fleet Manager Professional’

1.4 Click on ‘Properties’

1.5 Select the ‘Security’ tab

1.6 Choose the user that you want to give access to

1.7 Click on ‘Full Control’ in the ‘allow’ column

1.8 Click on ‘Apply’

1.9 Then click on the ‘Advanced settings’ button on the lower right corner

1.10 Now select the two ‘check boxes’ at the bottom of the new window.

1.11 Click on ‘Apply’

1.12 Click on the ‘Yes’ button if/when prompted

1.13 Click on ‘OK’

1.14 Click on ‘OK’ again.

2. Next you’ll need to apply the above to the ‘C:\Program Files\Common Files\Fleet Manager’
folder as well (steps 1.4 – 1.14).

1671
www.mixtelematics.com

1671
 1672

3. The last step is to modify some of your registry permissions:

3.1 Click on ‘Start’

3.2 Go to ‘run’

3.3 Type in: ‘regedit32’ and click on ‘OK’

3.4 Browse to: “HKEY_LOCAL_MACHINE\SOFTWARE\Data Pro Development (Pty) Ltd”

3.5 Right-click and select ‘permissions’

3.6 Choose the user that you want to give access to

3.7 Click on ‘Full Control’ in the allow column.

3.8 Click on Apply

3.9 Then click on the ‘Advanced settings’ button on the lower right corner.

3.10 Now select the two ‘tick boxes’ at the bottom of the new window.

3.11 Click ‘apply’ button.

3.12 Click on the ‘yes’ button if/when it asks

3.13 Click on ‘OK’

3.14 Click on ‘OK’ again.

3.15 Exit the REGEDIT32 application.

--------------------------------------------------------------------------------------------------

KEYWORDS: Fleet Manager Professional access rights Allowing standard user permissions Registry
permissions

1672
www.mixtelematics.com

1672
 1673
10.3.368 Knowledge Base Article 379

Article Number 379

Title HOW TO connect both PDA and DTCO to the FM300 Communicator at the same time

Created 6/27/2007 3:28:49 PM

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 6/27/2007 4:25:06 PM

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details
----- THIS KBA IS UNDER CONSTRUCTION ----

----- APPLIES TO ----

· FM300 series units

· FM Professional 8.35 and later

----- SUMMARY -----

This article describes what is needed, and how to set up the FM system to enable the use of both PDA
and DTCO on a FM Communicator.

----- MORE INFORMATION -----

The FM300 Communicator unit uses the FM300 Serial cable, with RJ45 connector on S1, and DB9
connector on S3. In some cases it is necessary to connect both PDA and DTCO Interface to the serial
port of the FM300 Communicator.

A new serial cable has been produced to cater for the possibility of connecting both PDA and DTCO
interface to the serial ports, instead of the one or the other. Together with this specific device drivers, as
well as a specific configuration needs to be loaded to the FM300 unit to support this cable, and the
devices attached.

----- CAUSE -----

The default FM300 Serial cable was designed to have FM Terminal fixed on S1, and leave S3 for any
other serial device.

----- SOLUTION -----

To implement the solution to support both PDA and DTCO with the FM300 series unit, the following is
needed:

Hardware

1. A new Serial cable to be supplied by your local FM dealer.

2. Physically connect the PDA to S1, and the DTCO to S3 (of the new serial cable)

FM Software

1673
www.mixtelematics.com

1673
 1674

1. Open your FM Software and go to Vehicle properties (to do this: select vehicle - right click - select
properties)

2. On the Device tab, ensure you have nothing connected on S1, i.e. * Not Connected *, and on S3 you
should connect the DTCO.

3. Now upload Device drivers and configuration from the FM Software.

If the procedure above is followed, it should be possible to now have both PDA and DTCO connected to
the FM300 unit at the same time.

----- STATUS -----

The ability to connect both PDA and DTCO to FM30 series unit has been included in the FM8.35 and
later software using the new Serial cable and procedure above to set this up.

------------------------------------------------------------------------------

KEYWORDS: FM300 Communicator, Serial cable, PDA, DTCO, serial port, FM8.35

1674
www.mixtelematics.com

1674
 1675
10.3.369 Knowledge Base Article 380

Article Number 380

Title Free-Text messaging from Dayton to mobile phone

Created 6/28/2007 3:31:47 PM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 7/2/2007 1:48:40 PM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Office 8

----- SUMMARY -----

This article briefly explains how to set up your FM Unit to send a free-text message of up to 80
characters from the vehicle (Dayton Navigator interface) to a mobile phone, via GPRS.

----- MORE INFORMATION -----

To enable this functionality, remember to check the Enable free-text messages to be sent to mobile
phones option under the SMS tab (you’ll first need to enable SMS communications before this option
will be visible for selection).

Note: Remember to take the above into consideration when setting your daily SMS limit to mobile (in
this case, the limit specifically applies to the number of GPRS messages that can be sent to a mobile
phone per day).

The last step in terms of the vehicle setup is to upload the vehicle configuration, either by means of a
vehicle plug, or through a GPRS schedule.

To send a free-text message from your Dayton navigator to any mobile phone, follow the below steps:

(1) Enter the applicable mobile number (and nothing else) into Line 1 of your free-text message on the
Dayton Navigator

(2) Enter your text message into Lines 2 & 3 (each line can accommodate up to 20 characters
respectively)

(3) After choosing to Send the message, you will be prompted asking whether you wish to send the
message to the office or to the mobile number supplied --> select the latter option.

----- STATUS -----

This will also be documented in the next release of the Fleet Manager Professional software.

------------------------------------------------------------------------------

KEYWORDS: Free-text messaging Dayton Navigator 80 Character limit

1675
www.mixtelematics.com

1675
 1676
10.3.370 Knowledge Base Article 381

Article Number 381

Title No communication between OBC and PC5200PRO

Created 6/29/2007 12:32:46 PM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 7/2/2007 4:05:00 PM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· VDO Dayton PC5200PRO

----- SUMMARY -----

This only applies to the PC5200PRO, which now allows the sending of NMEA as opposed to the
CCI protocol.

The NMEA protocol field in the Diagnosis menu of the Dayton Navigator has to be disabled (red).
If this option is enabled (green), the Fleet Manager icon will not be available on the main screen -i.
e. no communication between the FM OBC and the PC5200 VDO Dayton Navigation computer.

----- MORE INFORMATION -----

To verify your currently configured mapping protocol, from the main menu, go to Settings ->
System Information -> Diagnosis and check the status of the "NMEA 9600, 8N1" field.

Green = enabled

Red = disabled (recommended)

----- STATUS -----

This will also be documented in the next release of the Fleet Manager Professional software.

-------------------------------------------------------------------------------------------------------------

KEYWORDS: NMEA protocol Dayton navigator PC5200pro

1676
www.mixtelematics.com

1676
 1677
10.3.371 Knowledge Base Article 383

Article Number 383

Title VDO Dayton Active Job Message corruption & guidance issues

Created 7/6/2007 2:58:38 PM

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 7/19/2007 10:09:25 AM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· VDO Dayton Navigator, combined with FM OBC device driver sets 6.6.14.x and 6.11.16.x

----- SUMMARY -----

This article addresses the issue of job message corruption between the Fleet Manager Professional
software application and the VDO Dayton Navigation computer.

----- MORE INFORMATION -----

Kindly note that device driver sets 6.6.14.x and 6.11.16.x are not recommended for sending active job
messages from office to vehicle, when used in conjunction with the VDO Dayton Navigation computer.
There have been reports of message corruption on the Dayton interface, as well as a lack of the
guidance functionality in certain instances.

----- SOLUTION -----

It is strongly advised to update the FM OBC with a newer version of device drivers for this purpose.

----- STATUS -----

This issue is confirmed to be resolved from DDR version 7.7.2.1 onwards.

The latest Dealer Utility is available to be downloaded from the MiX Telematics website.

-----------------------------------------------------------------------------------------------------------

KEYWORDS: Dayton navigator | Job message corruption | DDRs 6.6.14.1, 6.11.16.1 | Guidance

1677
www.mixtelematics.com

1677
 1678
10.3.372 Knowledge Base Article 384

Article Number 384

Title Active tracking - sort on 'Last GPS Point'

Created 7/11/2007 3:44:12 PM

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 7/12/2007 11:01:24 AM

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Professional version 8.32 and 8.35

----- SUMMARY -----

When sorting the 'Last GPS Point' column in the Active tracking extension, an error message
appears.

----- MORE INFORMATION -----

When sorting the 'Last GPS Point' column in the Active tracking extension (clicking on the header of
the column), an error message appears.

The error message reads as follows:

---------------------------

Active

---------------------------

Run-time error '35600':

Index out of bounds

---------------------------

OK

---------------------------

When clicking OK on the error message, the Active Tracking extension does not respond, and the
Active Tracking icon in the Fleet Manager Professional software is disabled (greyed out).

----- CAUSE -----

This will only occur if no Map Viewer for Tracking is selected.

----- SOLUTION -----

The workaround is as follows:

1678
www.mixtelematics.com

1678
 1679

Open the Active tracking extension

Click on the Options icon (or Tools -> Options)

Go to the Tracking tab

In the Active Map Display window -> Select Map Viewer for Tracking

Select the applicable maps to be displayed

Close the Active tracking extension

Exit Fleet Manager Professional

The next time Active Tracking is opened in Fleet Manager Professional, this will be correct.

----- STATUS -----

This will be corrected in the next release of FM Professional

------------------------------------------------------------------------------

KEYWORDS: Active Tracking Map Error GPS

1679
www.mixtelematics.com

1679
 1680
10.3.373 Knowledge Base Article 385

Article Number 385

Title New Mapset for FM8.3

Created 7/30/2007 1:02:15 PM

Created By Taryn Murray (MiX Telematics - Johannesburg)

Last Modified 7/30/2007 1:02:15 PM

Last Modified By Taryn Murray (MiX Telematics - Johannesburg)

Details ----- APPLIES TO ----

· Fleet Manager Professional 8.35 and higher,

----- SUMMARY -----

The new mapset may not be available once installed as no extension has been loaded.

----- SOLUTION -----

When installing the new mapsets, the Mapviewer extension needs to be installed with the FM
Professional software.

You can find the MapViewer extension, in the installset, under the Locations section.

----- STATUS -----

This is by design

------------------------------------------------------------------------------

KEYWORDS: FM8.35 Mapviewer Mapset

1680
www.mixtelematics.com

1680
 1681
10.3.374 Knowledge Base Article 386

Article Number 386

Title Wifi on S2 or S3 - Device drivers

Created 7/30/2007 1:09:53 PM

Created By Taryn Murray (MiX Telematics - Johannesburg)

Last Modified 7/30/2007 1:09:53 PM

Last Modified By Taryn Murray (MiX Telematics - Johannesburg)

Details ----- APPLIES TO ----

· FM Wireless Kit

----- SUMMARY -----

When selecting the serial port (S2 or S3) to connect the WiFi kit on, you have to load the specific
device driver for this port configuration.

----- MORE INFORMATION -----

These are two of the selectable device drivers from the Dealer Utility:

1) “Device Drivers for modems and Wireless LAN”

2) “Device Drivers for Wireless LAN and SDK”

----- SOLUTION -----

1) If you load device driver set #1 (“Device Drivers for modems and Wireless LAN”), your WiFi kit has
to be connected to S3 to work. (Your modem should then be connected to S2.)

2) If you load device driver set #2 (“Device Drivers for Wireless LAN and SDK”), your WiFi kit has to
be connected to S2 to work. (Your SDK connection will then work on S3.)

----- STATUS -----

FM Wireless Kit is supported from FM Professional V8.31 onwards.

------------------------------------------------------------------------------

KEYWORDS: WiFi Wi-Fi Wireless device drivers S2 S3

1681
www.mixtelematics.com

1681
 1682
10.3.375 Knowledge Base Article 387

Article Number 387

Title Spurious speed pulses when using Hunter CAN Bus

Created 7/31/2007 1:54:09 PM

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 7/31/2007 3:17:38 PM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM300 series OBC, with Hunter CB8

----- SUMMARY -----

Speed recorded when using certain Hunters CAN Bus cables may show spiking, harsh braking or
harsh acceleration.

----- MORE INFORMATION -----

When using the Hunters CAN Bus CB8 cable, the FM300 unit records speed spikes, resulting in
harsh braking or harsh acceleration events being triggered. This does not happen with CB5.

----- CAUSE -----

Speed spikes are caused by noise on the input lines. This could be caused by installation problems
or by a deteriorating installation environment, i.e. when the unit had been fitted for quite a while (a
few years), bad earth, battery clamps not secured, etc.

The FM200 series of units had jumpers which could be used to control the accepted input signal. On
the FM300 series these were eliminated to simplify the setup during installation. The FM300s was
pre-configured to work in most scenarios, but may not prevent certain types of spikes from
influencing the signal under certain conditions.

The CB5 provides a lower noise 5V output signal, whereas the CB8 produces a 12 Volt pulse signal
with a potentially higher noise level. This higher noise level, if excessive, may at times not be rejected
by the FM300 input circuit.

----- SOLUTION -----

Connect a 3K3 resistor from the output of the CB8 to the FM300 frequency input. Then connect a
5.1V Zener diode from the FM300 input to Ground, ensuring that the Zener cathode (the side with the
stripe) is on the input side. This will clamp the signal, eliminating the noise signal and thereby prevent
spikes from occurring in the data.

Note: You should place the Zener diode as close to the FM300 unit as possible, to make the system
less susceptible to noise.

----- STATUS -----

This functionality is by design.

1682
www.mixtelematics.com

1682
 1683

------------------------------------------------------------------------------

KEYWORDS: FM300 speed spikes filter Hunter CB8 Zener

1683
www.mixtelematics.com

1683
 1684
10.3.376 Knowledge Base Article 388

Article Number 388

Title EnP Extension RAG YTD

Created 8/3/2007 12:58:19 PM

Created By Portia Roro (MiX Telematics - Stellenbosch)

Last Modified 8/3/2007 2:03:27 PM

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- THIS KBA IS CURRENTLY UNDER CONSTRUCTION -----

----- APPLIES TO ----

· Fleet Manager Exploration and Production Safety Extension, Fleet Manager Professional 8.35

----- SUMMARY -----

In some cases EnP Extension give errors when generating reports or viewing Options and fails to open
the criteria wizard.

----- MORE INFORMATION -----

The following issues have been identified and corrected in version 8.35.0.9 of EnPExt.dll

1. EnP Extension raises an error when the Detailed Driving Hours and Errors Report is run: “An
unexpected error occurred in Load Report line 2555. Error Details: -2147217900 (0x80040E14) -
Could not find stored procedure 'cmdEnPExt_OBCReport'. occurred in FMDataSource.
IFMDataSource_GetRs (Line 48710). The error has been logged.”

2. EnP Extension fails to open the criteria wizard when running the Progressive YTD report

3. EnP Extension sometimes raises errors when viewing Options (FM Options-Selecting EnP
Extension and clicking Show Options) – “An unexpected error occurred in PopulateTab4 line 0.Error
Details: 3021 (0xBCD) - Either BOF or EOF is True, or the current record has been deleted.”

4. EnP Extension sometimes raises errors when viewing Options and clicking OK (FM Options-
Selecting EnP Extension -Clicking Show Options and clicking OK) –“An unexpected error occurred in
SaveOverTimeEvents line 3515.Error Details: 3265 (0xCC1) - Item cannot be found in the collection
corresponding to the requested name or ordinal.”

----- SOLUTION -----

The following steps should be followed:

Download the FMPro835Hotfix.zip file.

Please note: BEFORE you install this , please make sure that NONE of the Fleet Manager
components are running (i.e. ensure FM Professional is closed before replacing the current EnPExt.dll
with this new one ,version 8.35.0.9).

FMPro835_HotFix1 Usage:

1684
www.mixtelematics.com

1684
 1685

1) Extract all 11 files to %Common Files%\Fleet Manager (usually C:\Program Files\Common Files
\Fleet Manager)

2) Ensure FMAdministrator is pointing to correct database.

3) Execute FMPro835_HotFix1.cmd (note: in remote mode this will not execute – this is applied server
side by the Bureau Administrators)

FMPro835_HotFix2 Usage:

1) Close FMProfessional if running

2) Extract the EnPExt.dll to the same folder where FMProfessional is installed.

3) Run the FMProfessional software

Important :

Ensure FMAdministrator is pointing to correct database before executing FMPro835_HotFix1.cmd.

Should you change databases on same PC please execute the FMPro835_HotFix1.cmd again against
that database.

----- STATUS -----

This will be corrected and included in the next release of the software.

------------------------------------------------------------------------------

KEYWORDS: Fleet Manager Professional 8.35 EnP Extension RAG YTD

1685
www.mixtelematics.com

1685
 1686
10.3.377 Knowledge Base Article 389

Article Number 389

Title Back-up battery Information

Created 8/14/2007 1:56:48 PM

Created By Taryn Murray (MiX Telematics - Johannesburg)

Last Modified 8/14/2007 1:56:48 PM

Last Modified By Taryn Murray (MiX Telematics - Johannesburg)

Details ----- APPLIES TO ----

· FM 200 series OBC

· FM300 series OBC

----- SUMMARY -----

FM 200 Communicator back-up batteries are going “faulty” and the unit stops logging onto the
GSM network.

----- MORE INFORMATION -----

If the battery fails in a "short-circuit mode" (i.e. a deep dis-charge, or low voltage mode), it will
prevent the GSM from working, as long as the Battery Charging is enabled (connects the battery to
the GSM). This is unlikely to occur, since the battery itself contains protection circuitry, which
should disable/disconnect the battery when the voltage drops below the safe threshold.

----- CAUSE -----

- The battery voltage needs to be maintained above 2.4V.

- The GSM controls the battery charging. Charging function starts at 3V battery voltage. For
voltages below 3.6V, the FM OBC disconnects the battery from the GSM, and trickle-charges the
battery to the minimum voltage level. The GSM is run from the switch-mode power supply in this
condition.

- The GSM needs a minimum of 3.3V to operate (GSM/GPRS functions).

- The Li-Ion battery has a guarantee of 1 year, and 400 charge/discharge cycles. In real life, Li-Ion
batteries do not last much longer than 3 years from battery manufacture date. This is true for
unloaded, stored batteries too.

- In addition, high temperatures, such as found in vehicles, shorten the life-span of the battery
significantly. Any temperature exposure above 25C accelerates the decay.

- Given ideal circumstances, the GSM will theoretically operate for more than 5 years, with the
large capacity battery (1750mAh), and more than 3.5 years with the smaller capacity battery
(1200mAh). This exceeds the life expectancy of the battery pack.

- Adding GPRS transmissions naturally shortens the life expectancy. An AVL type of message
every 5 minutes, drops the calculated life-expectancy for the big battery to just below 5 years, and

1686
www.mixtelematics.com

1686
 1687

for the smaller battery the calculated life-expectancy goes to just over 3 years. This exceeds the
actual life expectancy of the battery pack.

- These calculations ignore the load the rest of the FM OBC circuit places on the battery, when the
unit switches off from the vehicle battery and enters "battery-backup mode". The battery would
supply backup voltage to the circuit, as long as the input supply (vehicle battery) is below 8V, and
the backup battery voltage is >3.6V. The backup battery will run the FM OBC unit while the vehicle
battery is removed. This includes GPS and GSM functionality, as well as data logging, serial data
interfaces (including CAN), code plug interface (with LED) and buzzer. It cannot power external
devices via the Positive Drive lines. Daughterboard devices, powered from Positive Drive, will not
operate from the backup-battery. Driving of External Relay loads/devices, including the Starter
Relay, is supported from the backup battery.

----- SOLUTION -----

Swapping faulty (old) batteries with fresh battery packs, should resolve the problem.

----- STATUS -----

FM OBCs with the Siemens MC55/MC56 GSM modems will not experience the described problem.
If the battery should fail, it will happen in a safe mode; the firmware will detect this and switch on
the switch-mode power supply unit to drive the GSM.

1687
www.mixtelematics.com

1687
 1688
10.3.378 Knowledge Base Article 390

Article Number 390

Title Vehicles not appearing on 'Live Tracking' window in FM-Web

Created 29/08/2007 15:49:13

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 03/09/2007 13:55:54

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

FM Professional FM-Web

----- SUMMARY -----

Vehicles which are enabled for Active Tracking appear on the Active Tracking window in FM
Professional, but not on the Live Tracking window in FM-web.

----- MORE INFORMATION -----

Even though a vehicles is enabled for Active Tracking, and is selected in the FM-Web selection
criteria, it does not appear on the Live Tracking window.

----- CAUSE -----

The FM-Web functionality determines whether the required logical devices are connect for a
vehicle, before the Tracking window is populated. this means a navigation device (e.g. GPS) and a
communication device (e.g. GPRS) have to be connected. If this is not the case, it appears as
though the vehicle can not be tracked in FM-web, although it can be tracked in FM Professional.

This is often caused if a backup of a database is restored, or the vehicles are created as part of a
specific configuration group, and the device configuration of the group is not cascaded properly.

----- SOLUTION -----

A workaround is as follows:

In the vehicle properties on FM Professional, open the GPS / GSM device. Uncheck one of the
options (for example on the GSM tab -> GPRS -> 'Enable GPRS communication'), click OK, select
the same option again, APPLY the configuration.

This will ensure the logical device is now recognised in FM Web.

This vehicle should now appear on the Live Tracking window in FM-Web.

------------------------------------------------------------------------------

KEYWORDS: Active Tracking Live Tracking FM Web FM Professional

1688
www.mixtelematics.com

1688
 1689
10.3.379 Knowledge Base Article 391

Article Number 391

Title Replacement of Hands Free Kit with the FM Voice Kit

Created 21/09/2007 14:51:27

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 29/01/2008 16:47:09

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Telicom Hands-free Kit

· FM Voice Kit

----- SUMMARY -----

This guide provides a guideline on how to remove the Telicom hands-free kit and replace it with the
FM Voice Kit. The following link will point you to the required documentation.

Note: The old Telicom modem was labeled a Hands Free Kit. The new MiX Telematics product is
called a Voice Kit.

----- MORE INFORMATION -----

Please follow the instructions as per the attachment.

PLEASE NOTE: Depending on external influences such as: Cabin size, microphone to speaker
proximity, or speaker volume, a slight echo may be noticed at times. This can be resolved by

· ensuring that the microphone and speaker are at least 1 meter apart and

· the following AT string can be used as an alternative

AT^SNFS=2;^SAIC=2,1,1;^SNFO=0,4685,6301,8500,11205,15115,4,0;^SNFI=3,32767;^SNFW

----- MODEM STRINGS FOR HFK -----

Telicom Hands Free Kit

Wavecomm modem string for FM200

AT+SPEAKER=1;+VGT=159;+SIDET=0;+ECHO=0;+WCDM=5,1

Use this string only if you require extra gain on the mic

AT+SPEAKER=1;+VGT=191;+SIDET=0;+ECHO=0;+WCDM=5,1

Siemens modem string for FM300

AT^SNFS=5;^SNFO=0,0,0,0,0,15115,4,0;^SNFI=5,32767;^SRTC=1,3

1689
www.mixtelematics.com

1689
 1690

MiX Telematics Voice Kit

Siemens MC55 (FM200 Communicator built after 2007 & FM300 series OBC)

AT^SNFS=2;^SAIC=2,1,1;^SNFO=0,8211,11599,16384,23143,32767,2,0;^SNFI=2,8212;^SRTC=1,
3

Falcom C2D-SI (FM200 Communicator built before 2007)

AT+SIDET=0;+VGT=25;+VGR=64;+ECHO=1,1,0,3,10,7;+WSVG=1;+WCDM=5,1

The OBC must be configured to use Channel 2 and voice communication must be checked in the
Vehicle Configuration GSM Settings.

------------------------------------------------------------------------------

KEYWORDS: Telicom Hands-free Kit FM Voice Kit

1690
www.mixtelematics.com

1690
 1691
10.3.380 Knowledge Base Article 392

Article Number 392

Title FM Lite with USB Download Module

Created 25/09/2007 11:07:40

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 26/09/2007 15:26:11

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Lite version 2.52.0247

· USB Download Module

· FM100

----- SUMMARY -----

FM Lite can now be used with an USB Download module! This KBA describes what needs to be
done to enable your FMLite installation to use the USB Download Module.

----- MORE INFORMATION -----

A FM Lite update has been created to install drivers for the USB Download module, as well as
some logic to "fool" the FMLite software in thinking it is using the LPT port, where it is in actual fact
connecting to the USB Download module.

----- CAUSE -----

FM Lite is designed with 16-bit reporting engine and hence issues has been experienced with
applications using 32-bit drivers (such as the USB Download module).

----- SOLUTION -----

To enable the FM Lite software to use the USB Download Module successfully, the following
update should be installed and implemented as described below.

1. Ensure you have the latest version of FM Lite installed (version 2.5.20247).

2. Download the update from the following link: FMLiteUSBUpdate.exe

3. Copy this to the computer where FM Lite is installed, and run the install set (double click the file
FMLiteUSBUpdate.exe). Follow the steps on the wizard to complete the install.

4. Open FM Lite, and go to the following Menu: SETUP -> OPTIONS, and select LPT2 as the port
where the download module is connected to.

You should now be able to use FM Lite with the USB Download module to configure plugs,
download information, or view plug information.

1691
www.mixtelematics.com

1691
 1692

Please note: There has been no change to the FM Lite Software interface, so even though you are
pointing the download module to the LPT2, it will still be connecting to the USB Download module,
if the procedure above was followed

----- STATUS -----

No changes will be made to the FM Lite software interface itself in the short term. If the USB
Downlaod module is needed, the update attached to this KBA should be used as described above.

------------------------------------------------------------------------------
KEYWORDS: FM Lite FMLite USB Download Module Pod FM100 Plug Upload

1692
www.mixtelematics.com

1692
 1693
10.3.381 Knowledge Base Article 393

Article Number 393

Title Analogue Inputs On FM200 Plus/FM300

Created 26/09/2007 10:05:26

Created By Warren Tieling (MiX Telematics - Stellenbosch)

Last Modified 26/09/2007 13:40:16

Last Modified By Warren Tieling (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM200 and FM300 Plus OBC

· FM200 and FM300 Plus HV OBC

----- SUMMARY -----

How to use the analogue input for the FM200 Plus inorder to record "weight" from a Kimax I using
its analogue output (0-5V), taking into account the non linearity of the input.

----- MORE INFORMATION -----

Upon developing a device to work with the FM using the analogue input (0-5V resolution),we have
noticed that it responded in non linear at small V values and hi V values.Is it supposed to be the
same for FM200 Plus and FM300?

----- CAUSE -----

The FM300 and FM200 Plus HV inputs are more linear than the FM200 Plus at the upper voltage
threshold due to it using an updated protection circuit for those inputs. Nonlinearity occurs on the
FM200 Plus between about 4.6V to 5V, and voltages that are near the upper threshold therefore
need to be reduced using an external potential divider circuit (eg a 10K in series and a 100K to
ground) for best accuracy or by using the FM200 Plus inputs set to th 0-38V range. The FM300 or
FM200 Plus HV can also be used to improve accuracy at those voltage levels. At lower voltages,
no significant differences should be seen between the FM200 Plus and the FM300 or FM200 Plus
HV.

----- SOLUTION -----

The FM200 Plus loses linearity above about 4.6V – this is near to the measurement limit. For best
linearity, one should ensure the input voltage is within the FM200 most linear range (from 0 to
about 4.6V). For Kimax, one needs to establish a few facts before one needs to take action:

1) What is the voltage output range that one is actually trying to measure (for the working weight of
the vehicle)? Chances are that a 4.6V and above will represent an unrealistic input voltage that is
well beyond the legal vehicles capacity in any event.

2) The Kimax II is also supported by the FM200 Plus/ FM300. This does not connect to an
analogue, but to S3 and up to 12 inputs can be logged. Measurements can be made a lot more
efficiently with this product as it is more advanced than the “Kimax I” with analogue outputs. Can
this product be used instead of the Kimax1 – it will be beneficial if it can be.

1693
www.mixtelematics.com

1693
 1694

Once we have established this, and if it is still necessary, one can simply build a potential divider
network as specified to cover a wider voltage range.

----- STATUS -----

Currently in this regard, it is suggested that the Kimax 2 be used instead because measurements
can be made a lot more efficiently with this product as it is more advanced than the “Kimax I” with
analogue outputs.

------------------------------------------------------------------------------
KEYWORDS: < FM200 FM300 PLUS Kimax Analogue Inputs Linear

1694
www.mixtelematics.com

1694
 1695
10.3.382 Knowledge Base Article 394

Article Number 394

Title How to set up FM Tracer unit with FM-Web

Created 28/09/2007 12:21:36

Created By Ronel Spies (MiX Telematics - Stellenbosch)

Last Modified 28/09/2007 15:02:49

Last Modified By Portia Roro (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Tracer

· FM3310i

· FM-Web

----- SUMMARY -----

The FM Tracer unit (FM3310i) can only be used with FM-Web solution, and not with FM
Professional in standalone mode. The document attached to this KBA explains how FM Tracer
units can be set up using FM Professional in remote mode, as well as the FM-Web interface. This
setup applies to units being set up for the first time.

----- SOLUTION -----

Please download the document from the following link and follow the instructions in the manual to
set up your FM Tracer unit(s): FMTracerunitFM-Web.pdf

----- STATUS -----

This functionality is by design. Once a FM Tracer unit is making contact to the FM-Web database,
configuration can also be uploaded remotely.

------------------------------------------------------------------------------
KEYWORDS: FM Tracer, FM3310i, FM-Web, FM Tracer setup

1695
www.mixtelematics.com

1695
 1696
10.3.383 Knowledge Base Article 395

Article Number 395

Title FM-Web - Google Earth Maps

Created 02/10/2007 15:48:08

Created By Portia Roro (MiX Telematics - Stellenbosch)

Last Modified 11/12/2007 15:36:24

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM-Web - Google Earth Maps

----- SUMMARY -----

In some cases when viewing Google Maps using FM-Web, a message is returned that Google
Earth does not have maps for that area.

----- MORE INFORMATION -----

The following issues have been identified:

Sometimes when viewing Google Maps in FM-Web the following message appears:

“We are sorry but we don’t have maps at this zoom level for this region.”

Try zooming out for a broader look and other times certain areas will come back with tiles.

This message sometimes appears when Google Maps makes requests for tiles. The requests
randomly go to different Google servers (mt0 – mt3 for Vector data and kh0 – kh3 for satellite
data), and sometimes only 1 or 2 of the servers will respond with tiles.

This error is returned by Google Earth servers and you could also more frequently notice this when
selecting ‘Hybrid maps’.

----- SOLUTION -----

You can usually zoom out a bit and slowly zoom in again and this normally sorts out this issue.

Important:

This is not caused by FM or the map engine, but Google.

Please also ensure that your network is not blocking any of the Google server URLs.

------------------------------------------------------------------------------

KEYWORDS: Google Earth Maps

1696
www.mixtelematics.com

1696
 1697
10.3.384 Knowledge Base Article 396

Article Number 396

Title FM Professional 8.35 Location Reports

Created 15/10/2007 12:59:21

Created By Riaan Serfontein (MiX Telematics - Stellenbosch)

Last Modified 07/01/2008 09:37:43

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

Applies to Fleet Manager Professional 8.35 Location Reports

----- SUMMARY -----

Location Report generates the incorrect information

----- MORE INFORMATION -----

When generating a Location Report in FM8.35 be it an ‘At Location’ or ‘Driving Report’ the incorrect
values are generated on the report.

----- CAUSE -----

With the release of FM8.35 the issue nested it self in the Prodrep.dll causing the incorrect report to
be generated.

----- SOLUTION -----

To resolve your location reporting issues:

Download the ProdRep.8.38.0.902.zip file.

Please do as follows:

1. Close the FM Pro software and all FM services running.

2. Rename the old 'ProdRep_OLD.dll', before you copy in the new supplied version.

3. Copy the dll link to 'C:\Program Files\Fleet Manager Professional'.

The FM Pro software can know be opened, and the new Prodrep.dll should automatically register
itself.

----- STATUS -----

IMPORTANT: Please note that the supplied 'ProdRep.dll' file is a BETA version, not an official
release and under no circumstances may it be redistributed. The correct Prodrep.dll will be in the
new release of FM Pro.

------------------------------------------------------------------------------

1697
www.mixtelematics.com

1697
 1698

KEYWORDS: Location Report

1698
www.mixtelematics.com

1698
 1699
10.3.385 Knowledge Base Article 397

Article Number 397

Title GPS VELOCITY AS SPEED

Created 16/10/2007 16:47:28

Created By Riaan Serfontein (MiX Telematics - Stellenbosch)

Last Modified 07/12/2007 13:09:25

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details GPS VELOCITY AS SPEED NOT SHOWING ON THE TIMELINE FOR BUREAU CLIENTS
HAVING DDR 7.7.2.6 ON THE FM UNIT.

----- APPLIES TO ----

This applies to vehicles that’s using DDR set 7.7.2.6 and the vehicle is setup for GPS Velocity as
Speed

----- SUMMARY -----

When using the Device Driver Set the speed does not show on the timeline

----- MORE INFORMATION -----

Vehicles that are setup with GPS Velocity as Speed and have DDR 7.7.2.6 will not record any
speed, but it does record the GPS positions successfully.

----- CAUSE -----

Uploading the Device Drivers remotely on the Bureau caused the FM unit DDR set to change to the
default DDR 7.7.2.6 that was loaded on the server

----- SOLUTION -----

Should the vehicle have no other Serial Device connected the following need to happen:

1. Open up the vehicle properties

2. Click on Devices and go to S3

3. Double click on S3, which opens up Devices that can be connected to this Serial Port

4. Select ‘Other Serial Devices’

5. Click Ok, then Apply and Ok again.

6. Once this is done schedule a remote DDR upload. The Bureau Server will then select a DDR set
suitable for the vehicle as per the Devices connected and or the default DDR set on the server.
Once the upload has been completed the DDR should have changed to the correct DDR set
7.7.2.3.

Note that the config does not need to be uploaded.

1699
www.mixtelematics.com

1699
 1700

The other alternative is to upload the latest DDR set 7.7.2.2 via Green Tag.

----- STATUS -----

Changes will be made to the Bureau servers to change the default version to 7.7.2.2

------------------------------------------------------------------------------

KEYWORDS: GPS Velocity as Speed

1700
www.mixtelematics.com

1700
 1701
10.3.386 Knowledge Base Article 398

Article Number 398

Title Cannot download BIN file from FM-Web

Created 05/12/2007 14:02:01

Created By Riaan Serfontein (MiX Telematics - Stellenbosch)

Last Modified 10/01/2008 11:52:34

Last Modified By Michael Chamberlain (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Professional and FM-Web

----- SUMMARY -----

Changing unit types and resetting the unit.

----- MORE INFORMATION -----

When the unit type is changed from a FM200 to a FM300 and the unit is not reset under the event
tab one can not initialize a plug or download a Bin file from FM-Web.

----- CAUSE -----

The unit types are different. The FM200 has two relay drives and the FM300 only one, and system
sees the difference and can’t create the relevant Config file.

----- SOLUTION -----

The issue has two solutions.

1. Generate a config report before hand and also remember the pin number. Then change the unit
type, do a ‘swap unit’ and also click the reset tab under devices and or events. Once this has been
completed make sure the pin number is correct and also compare the configs from that of the
config sheet before attempting to generate a bin and uploading it.

2. Create a new vehicle with the correct unit type. Decommission the old unit and use the Pin and
Data number of the old unit on the new unit. Generate the config and upload to the unit

----- STATUS -----

------------------------------------------------------------------------------

KEYWORDS:

1701
www.mixtelematics.com

1701
 1702
10.3.387 Knowledge Base Article 399

Article Number 399

Title Specific Absorbtion Rate (SAR) of FM Product

Created 09/01/2008 07:40:33

Created By Riaan Serfontein (MiX Telematics - Stellenbosch)

Last Modified 09/01/2008 07:40:33

Last Modified By Riaan Serfontein (MiX Telematics - Stellenbosch)

Details APPLIES TO

· Installation of all FM products incorporating GSM transmitters.

SUMMARY

GSM to be mounted 20cm away from the human body.

MORE INFORMATION

In order to comply with national and international regulations Specific Absorption Rate (SAR) “The
GSM antenna is to be mounted further than 20cm away from the human body under normal
operating conditions.”

This information needs to passed on to all installer/technicians for all future installations of FM
products incorporating GSM transmitters.

Installation manuals have been updated to reflect the above installation instruction.

STATUS

This is by Design.

------------------------------------------------------------------------------

KEYWORDS: Applies to FM200Communicator, FM300 and all FM units with GSM transmitters.

1702
www.mixtelematics.com

1702
 1703
10.3.388 Knowledge Base Article 400

Article Number 400

Title MapViewer in FM8.35 blocked after updating an older database

Created 04/02/2008 11:26:16

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 04/02/2008 11:26:16

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Fleet Manager Professional 8.35 onwards

· Mapviewer registration

----- SUMMARY -----

Database using the FM8.35 Mapviewer still requires an license code for this extension.

----- MORE INFORMATION -----

If a database was registered for the Mapviewer in versions prior to FM8.35, and is then upgraded to
Fm8.35, the user will be prompted to enter a registration code, even though the Mapviewer is free
of charge in FM8.35 onwards.

----- CAUSE -----

The Mapviewer was registered in the old versions, and the database still stores the registration
details, but can not retrieve the registration code, and can therefore not use the new functionality in
which the Mapviewer is already registered.

----- SOLUTION -----

In order to "reset" the registration details on a database please enter a '0' (zero) in the extension
dialog box of the Mapviewer.

Click on register, load.

----- STATUS -----

This is by design

------------------------------------------------------------------------------

KEYWORDS: FM8.35 Mapviewer registration

1703
www.mixtelematics.com

1703
 1704
10.3.389 Knowledge Base Article 401

Article Number 401

Title Windows Vista compatibility with Fleet Manager Professional

Created 19/02/2008 12:41:19

Created By Warren Tieling (MiX Telematics - Stellenbosch)

Last Modified 26/02/2008 13:06:59

Last Modified By Manfred Klausmann (MiX Telematics - Germany)

Details
----- APPLIES TO ----

· FM9 and FM8 Windows Vista compatibility tests

----- SUMMARY -----

The following documentation will supply you with further information on Windows Vista's
compatibility with FM Professional software.

----- MORE INFORMATION -----

You can try to disable your UAC (User Account Control) in Vista. This way you will be able to
enable most functions of FM8/9 in Vista, but that will make Vista as vulnerable as XP.

----- POSSIBLE WORKAROUND -----

All tests were done and repeated in the following FM and Vista Combinations:

· FM LOCAL mode: Vista Ultimate (with UAC ON)

· FM LOCAL mode: Vista Ultimate (with UAC OFF)

· FM Remote mode: Vista Ultimate (with UAC ON)

The results were as expected: General functionality seems to be working fine except where FM
needs to write a file or settings to its Program Files\Fleet Manager folder.

Some instability was also noted.

Please refer to the documentation on the following link for further test results.

----- SOLUTION -----

General workaround is to turn off UAC, but keep in mind that the ability to turn off UAC might be
disabled in the next official Vista Service Pack, therefore we cannot support Fleet Manager
Professional (as is) in Vista (all versions).

----- STATUS -----

Please note, Windows Vista is officially not supported with FM Professional, inclusive of the FM
Communications Suite.

1704
www.mixtelematics.com

1704
 1705

------------------------------------------------------------------------------

KEYWORDS: FM9 FM8 Fleet Manager Professional Windows Vista

1705
www.mixtelematics.com

1705
 1706
10.3.390 Knowledge Base Article 402

Article Number 402

Title Modem Initialisation Strings

Created 21/02/2008 10:38:35

Created By Warren Tieling (MiX Telematics - Stellenbosch)

Last Modified 17/03/2008 10:25:18

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· Roaming Strings and Mobile Network Codes in Sub Saharan Africa

----- SUMMARY -----

An explanation as to what the appropriate way is to entering a roaming string and examples of the
African country codes as an informative measure

Just a quick explanation as well:

AT+CPOL=1,2,”65510”;+CPOL=2,2,”65201”;+CPOL=3,2,”64901”;+CPOL=4,2,”65102”;+CPOL=5,2,
”65310”;

A string like the above would mean that the vehicle is based in SA and roams to Botswana,
Namibia, Lesotho, Swaziland.

----- MORE INFORMATION -----

Users often question as to what the correct format is for roaming modem strings when crossing
African borders and which mobile network codes represent which African Country. If theses
modem roaming strings are entered incorrectly, companies would not be able to get updated
positions of there vehicles once they cross the South African borders into neighboring African
Countries. This will ensure the preferred service provider in the country gets selected.

----- CAUSE -----

Upon configuring a vehicle, users tend to either enter these strings incorrectly or don’t enter them
at all when configuring client vehicle’s on the respective data bases inorder to prepair them for the
cross boarder African trips. To eliminate this occurrence, the document serves to inform the user
as to which code applies to which African country and what the format is that it should be entered
as.

I will also be attaching a document reflecting these codes and informing which code represents
which African country.

----- SOLUTION -----

As an example, the string must start with the AT+CPOL=; the next step is to insert the "code" for
the area that the vehicle travel’s to. It is not necessary to add AT+CPOL in front of each code.

So the correct modem string for Namibia should be AT+CPOL=1,2"64901" if this vehicle travel’s to

1706
www.mixtelematics.com

1706
 1707

Namibia and let say Botswana, but more to Namibia it will be

AT+CPOL=1,2"64901";+CPOL=2,2"65201"

A single string would look like - +CPOL=1,2,”65510” for MTN SA

Making use of all of them, would look like the below:

Modem string

+CPOL=1,2,”65510”;+CPOL=2,2,”65201”;+CPOL=3,2,”64901”;+CPOL=4,2,”65102”;+CPOL=5,2,”
65310”;

This will be entered within the vehicle properties - scroll down to select GSM and select Modem
from the tab options available.

Please also be informed that the quotes and the "AT" are compulsory.

Please refer to the documentation on the following link supplying an in depth explanation.

----- STATUS -----

Due to thorough testing and investigation, it can be informed that the information supplied in this
KBA resolves previous experienced situation of not being able to track vehicles once they have
crossed the South African border.

------------------------------------------------------------------------------

KEYWORDS: Roaming AT Command String Network

1707
www.mixtelematics.com

1707
 1708
10.3.391 Knowledge Base Article 403

Article Number 403

Title Comms Suite Fails In FM9.0

Created 17/03/2008 10:12:02

Created By Riaan Serfontein (MiX Telematics - Stellenbosch)

Last Modified 19/03/2008 12:43:15

Last Modified By Riaan Serfontein (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO -----

· Comms Suite failing to login when using it in FM9.0 in Remote mode.

----- SUMMARY -----

The Comms Suite in remote mode (specifically DECT, APC, GSM and SMS) will fail on login with
the upgrade to version 9.0

----- MORE INFORMATION -----

When trying to use the Autopoll Client, GSM, SMS and DECT downloader in Remote mode it will
not be able to login.

----- SOLUTION -----

Workaround:

Copy the Registry file: link to your desktop and double click to run. This will create the following
registry key

HKEY_LOCAL_MACHINE\SOFTWARE\Data Pro Development (Pty) Ltd\Fleet

Manager\9.0\Server\FMOXMLURL

Please note to change the URL to the FM Pro remote mode URL you are using. Currently it is
setup for the SA server ie; http://api.fm-web.co.za

The impact is that if the URL is changed in FM Administrator, the registry key must be changed
again.

This only applies to FM9.0 in Remote Mode for Bureau applications.

----- STATUS -----

The issue will be resolved in the release of FM9.1

------------------------------------------------------------------------------

KEYWORDS: FM 9.0 APC GSM SMS DECT FM-WEB Bureau

1708
www.mixtelematics.com

1708
 1709
10.3.392 Knowledge Base Article 404

Article Number 404

Title FM9 vehicle configuration upload fails

Created 17/03/2008 13:35:52

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 17/03/2008 13:42:12

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM Professional 9.0 device driver set 7.12.7.x

----- SUMMARY -----

Uploading vehicle configuration fails when the vehicle has device driver set 7.12.7.x loaded

----- MORE INFORMATION -----

When scheduling a configuration upload using any transfer method (GPRS / GSM) or doing a
manual plug upload, it will fail when the vehicle has device driver set 7.12.7.x loaded

----- SOLUTION -----

Upload the latest device drivers to the vehicle first, before attempting to upload the new vehicle
configuration. (released version with FM9 is ddr set 8.3.3.x)

----- STATUS -----

Any other device driver set before or after 7.12.7.x will work successfully.

This will not corrupt the FM unit, the current configuration will roll back.

This will be corrected in the next release of Fleet Manager Professional v 9.1

------------------------------------------------------------------------------

KEYWORDS: FM9.0 device driver set 7.12.7 configuration

1709
www.mixtelematics.com

1709
 1710
10.3.393 Knowledge Base Article 405

Article Number 405

Title GPRS mail notifications on FM9.0

Created 19/03/2008 13:45:09

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 19/03/2008 15:13:47

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

· FM9.0 E-mail notifications via GPRS service on standalone databases

----- SUMMARY -----

The Fleet Manager software uses an e-mail component to send notification e-mails for Active
Events.

In FM9.0 the e-mail component has been changed, and is not yet available in the FM9.0 installset.

----- MORE INFORMATION -----

If a Notify file has been setup to send e-mails for Active Events (downloaded via the GPRS
Service) this mail component has to be installed manually before the e-mails will be sent.

----- SOLUTION -----

Here is the link to the third-party "bmail" utility that is required for FM9.0 GPRS service to process
mail notifications.

(Also available from http://www.beyondlogic.org/solutions/cmdlinemail/bmailv107.zip)

This needs to be downloaded and copied to the same folder where the DataProcessor is installed.
Typical path would be C:\Program Files\Common Files\Fleet Manager Services\DataProcessor
Service

----- STATUS -----

The next release of Fleet Manager Professional 9 will include the mail component in the installset,
so it will not be necessary to download this manually.

This has already been deployed to the FM-Web Bureau servers, only required for standalone FM
installations.

------------------------------------------------------------------------------

KEYWORDS: Fleet Manager 9.0 FM9 email notification notify

1710
www.mixtelematics.com

1710
 1711
10.3.394 Knowledge Base Article 406

Article Number 406

Title FM9.0 Update

Created 28/03/2008 11:34:13

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 01/04/2008 10:52:51

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· These issues affect all customers, Standalone and Bureau.

· All users running FM Professional who need to generate vehicle configuration.

----- SUMMARY -----

This update has to be installed after the installation of FM9.0, to address certain configuration
issues.

----- MORE INFORMATION -----

This update addresses the following issues on FM Professional 9.0 installations:

1. Uploading of config to 7.12.7.x device driver sets is now supported. (refer KBA#404)

2. The conditions that caused configuration to fail to generate with specific complex boolean event
triggers, e.g. event which include the conditions:

Not (at location X OR at location Y OR at location Z).

3. DTCO device not working.

4. ECZ loader fails when receiving a new ECZ.

5. CAN1 configuration generation fails.

6. Garmin device not allowed on 3316.

7. HOS devices not allowed on 3316 (affected Tripmaster only).

----- SOLUTION -----

NOTE: If you have the MiX Telematics global unit support dll installed (for FM Tracer functionality)
you have to uninstall this first, then install the FM 9 update, then reinstall the global unit support dll.

STEP1: After all Fleet Manager 9.0 software has been installed, please download the following link.

STEP 2: The software simply needs to be installed on the required machine, as it will install all the
required components to the “Program Files\Common Files\Fleet Manager” folder.

1711
www.mixtelematics.com

1711
 1712

STEP 3 for STANDALONE USERS only: Run the FM9UpdateMarch2008.bat batch file in “Program
Files\Common Files\Fleet Manager” folder. This will perform an update to the Fleet Manager
database

----- STATUS -----

This will be corrected for the next release of FM9

------------------------------------------------------------------------------

KEYWORDS: FM9 Fleet Manager Professional 9.0 configuration

1712
www.mixtelematics.com

1712
 1713
10.3.395 Knowledge Base Article 407

Article Number 407

Title TM9.0 Update

Created 01/04/2008 15:44:28

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 01/04/2008 15:56:40

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

· All users running TM Professional who need to generate vehicle configuration.

----- SUMMARY -----

This update has to be installed after the installation of TM9.0, to address certain configuration
issues.

----- MORE INFORMATION -----

This update addresses the following issues on TM Professional 9.0 installations:

1. Uploading of config to 7.12.7.x device driver sets is now supported. (refer to KBA#404)

2. The conditions that caused configuration to fail to generate with specific complex boolean event
triggers, e.g. event which include the conditions:

Not (at location X OR at location Y OR at location Z).

3. DTCO device not working.

4. ECZ loader fails when receiving a new ECZ.

5. CAN1 configuration generation fails.

6. Garmin device not allowed on 3316.

7. HOS devices not allowed on 3316.

----- SOLUTION -----

NOTE: If you have the MiX Telematics global unit support dll installed (for TM Tracer functionality)
you have to uninstall this first, then install the TM 9 update, then reinstall the global unit support dll.

STEP1: After all Tripmaster 9.0 software has been installed, please download the following link.

STEP 2: The software simply needs to be installed on the required machine, as it will install all the
required components to the “Program Files\Common Files\Tripmaster” folder.

----- STATUS -----

1713
www.mixtelematics.com

1713
 1714

This will be corrected for the next release of TM9

------------------------------------------------------------------------------

KEYWORDS: TM9 configuration

1714
www.mixtelematics.com

1714
 1715
10.3.396 Knowledge Base Article 408

Article Number 408

Title FM9.0 GSM Downloader error

Created 10/04/2008 07:51:32

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 10/04/2008 14:29:32

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- THIS KBA IS UNDER CONSTRUCTION ----

----- APPLIES TO ----

FM9.0 GSM Downloader ActiveX

----- SUMMARY -----

After installing FM9.0, when trying to start the GSM downloader an error message appear. After
clicking OK, the GSM icon disappears.

----- MORE INFORMATION -----

This is the error message from the DlSchlog.txt:

---------- FMGSMPro.exe Version 9.0.1------------

ERROR: An unexpected error has occurred in Form_Load - 429 (1AD): ActiveX component can't
create object (Line 4380).

----- CAUSE -----

This error is caused by the FMDialer.dll not registered successfully. This is usually done on install.

----- SOLUTION -----

1) With English language and regional settings:

Click START -> RUN -> Type in: C:\WINDOWS\system32\regsvr32.exe "C:\Program

Files\Common Files\Fleet Manager\FMDialer.dll"

2) With any other language settings (i.e. "Program Files" is called something else):

- Download the following .bat file. link.

- Save this file to C:\Program Files\Common Files\Fleet Manager

- Double click on the file to execute and register the dll

When the dll is successfully registered the following message should appear:

---------------------------

1715
www.mixtelematics.com

1715
 1716

RegSvr32

---------------------------

DllRegisterServer in FMDialer.dll succeeded.

---------------------------

OK

---------------------------

----- STATUS -----

This registration will be automated with the installset for the next release of FM Professional

------------------------------------------------------------------------------

KEYWORDS: FM9.0 Fleet Manager Professional GSM Downloader FMDialer.dll

1716
www.mixtelematics.com

1716
 1717
10.3.397 Knowledge Base Article 409

Article Number 409

Title FM Garmin compatibility

Created 08/05/2008 16:02:50

Created By Francois Bonthuys (MiX Telematics - Stellenbosch)

Last Modified 05/06/2008 12:19:45

Last Modified By Zoe Jenkins (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

The following link shows the Garmin’s FMI enabled PNDs (Personal Navigation Devices): Click
here

----- SUMMARY -----

Not all Garmin PND’s are compatible with the Fleet Manager range of units.

----- MORE INFORMATION -----

Below is a list of the PND’s that have been tested with the FM range, and the outcome of each
test:

· Nuvi 600 series– FMI functionality operates correctly. Please note this model is now
discontinued and has been superceded by the Nuvi 700 series.

· Zumo 550 - FMI functionality operates correctly.

· Zumo 400 – FMI functionality does not work. Requires Garmin F/W upgrade - unavailable on
website.

· Zumo 500 – FMI functionality does not work. Requires Garmin F/W upgrade - unavailable on
website.

· Streetpilot 7000 series – Partial FMI functionality. Text Messaging from PND to office is not
functional.

· Nuvi 710 series – Part of the Nuvi 700 series. Full Job and Messaging functionality is supported
,with the exception of ETA status updates which are not sent through to the software. This
requires Garmin to resolve and they are investigating.

----- STATUS -----

This list will be updated regularly to ensure current information on latest releases

-----------------------------------------------------------------------------------------

KEYWORDS: FM300 | 3316 | garmin | PND | Zumo | Streetpilot

1717
www.mixtelematics.com

1717
 1718
10.3.398 Knowledge Base Article 410

Article Number 410

Title FM Professional 9 compatibility with XP SP3

Created 13/05/2008 10:42:49

Created By Warren Tieling (MiX Telematics - Stellenbosch)

Last Modified 10/06/2008 13:34:16

Last Modified By Ronel Spies (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

FM Professional 9 compatibility with XP SP3

----- SUMMARY -----

This KBA addresses incompatibility issues between Fleet Manager Professional (8.x and 9.00) and
the Windows XP Service Pack 3

----- MORE INFORMATION -----

The FMPro & FMComms suite install sets specifically check for SP2 when running on Windows
XP. This logic is in the uninstaller as well.

The error message (incorrectly) reads as follows:

Fleet Manager Professional can only be installed on Microsoft Windows 2000 or later.

This means that FM 8.x and FM9.00 cannot be installed nor uninstalled on Windows XP SP3.

----- CAUSE -----

FM Professional 9.0 and earlier were released before the official release of XP SP3, so the
installsets do not cater for this, and explicitly requires XP SP2

----- SOLUTION -----

The workaround would be to uninstall XP SP3. As the customers have to uninstall FM8.x (and
Satamatics from FM9.00) in order to upgrade to the next version of FM Office, it is important to
warn about this.

After the successful installation of FM Professional XP SP 3 can be reinstalled. However, when FM

is uninstalled, XP SP 3 has to be uninstalled first.

----- STATUS -----

FM9.R1 install set has been updated so it can be install on XP SP2 or SP3 (or later)

------------------------------------------------------------------------------

KEYWORDS: Fleetmanager FMProfessional 9 XP SP3 FMPro Win XP

1718
www.mixtelematics.com

1718
 1719
10.3.399 Knowledge Base Article 411

Article Number 411

Title Configuration error when uploading to CAN unit in FM9.0

Created 16/05/2008 11:19:18

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 09/06/2008 14:31:15

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

FM300 CAN FM 3316 TM 3315 FM9.0

----- SUMMARY -----

Error received when uploading a configuration to a plug for CAN units on FM9.0

----- MORE INFORMATION -----

While trying to create a vehicle config plug, you get the following error:

---------------------------------------------------------------------------

The following unexpected error/s occurred:

-2147211457 (0x8004273F): Functionality requires at least 8.03.03.x version of device drivers

occurred in UnitConfig.CreateUserActions (Line 20930).

The error has been logged.

---------------------------------------------------------------------------

----- CAUSE -----

In FM9.0 there is a device driver / configuration dependency, whenever a device is setup that uses
fuel from CAN. This includes the FM300 CAN unit, FM315 and 3316.

----- SOLUTION -----

1) In this situation, config cannot be generated until the vehicle plug is inserted into the unit
(already loaded with latest DDRs), and then doing a plug info within FM9 to ascertain the unit's
DDR set's version.

2) The other option is to run a script to apply a set version that will allow a new vehicle to generate
config.

The script will update ALL vehicles in the database which have not connected to have device
Driver set 8.3.4.x loaded on 2000/01/01 00:00:00.

The first connect with the vehicle will update with correct information.

1719
www.mixtelematics.com

1719
 1720

Please only apply this to databases that are having the problem to reduce confusion about the
driver set version number and date.

Download link.

3) An update patch was created to replace the SQL query, please download and install from the
following link:

FM900HotFix21May2008.zip

----- STATUS -----

Please note, we are in the process of testing a hot fix as well. So I would recommend waiting for
this. But in the meantime, you can deploy the script if urgent.

This will be resolved for the next release of FM9.

------------------------------------------------------------------------------

KEYWORDS: FM300 CAN FM 3316 TM 3315 FM9.0

1720
www.mixtelematics.com

1720
 1721
10.3.400 Knowledge Base Article 412

Article Number 412

Title WLAN modules not transmitting any trip data

Created 21/05/2008 15:48:11

Created By Michael Chamberlain (MiX Telematics - Stellenbosch)

Last Modified 09/06/2008 11:19:14

Last Modified By Michael Chamberlain (MiX Telematics - Stellenbosch)

Details ------ APPLIES TO ----

WLAN modules (WiFi technology)

----- SUMMARY -----

Certain released WLAN modules connects to the WLAN Access Point, but does not transmit any
FM data.

----- MORE INFORMATION -----

The WLAN module(s) could be pinged from the network but no trip or AVL data is transmitted.

----- CAUSE -----

This is applicable to FW(Firmware)version 4.3.0.15 loaded on the WLAN module(s).

----- SOLUTION -----

First determine the version of FW loaded on the WLAN module by doing the following:

1) Try and 'ping' the WLAN module. This could be done by opening a command prompt:

Start>>Run>>cmd

2)Then type in: ping [IP Address of WLAN]

3) If a ping reply is received open an internet browser window. Enter the IP Address of the WLAN
unit.

4) When asked for username type in: dpac

The password is also: dpac

5) On the status page the FW version will be displayed (Not the radio firmware).

6) If this version is 4.3.0.15, please download the 4.3.0.35 version from this link:

Airborne_UART_LEAP_4.3.0.35.bin

7) The downloaded .bin file should be uploaded using the same DPAC webpage from point 4
above. The rightmost link called 'Upload Firmware' should be used.

1721
www.mixtelematics.com

1721
 1722

8) After the upload of the firmware the DPAC webpage will not be accessible anymore. This feature
was removed in this version of firmware as it could pose a security risk with the new LEAP security
functionality.

9) Please note after loading the new firmware, the latest device drivers should be loaded on the FM
onboard computer(s). This Dealer Utility is available from the www.mixtelematics.com website.
Device driver version 8.5.16.x or newer.

----- STATUS -----

This issue will be resolved on all stock shipped after May 2008.

------------------------------------------------------------------------------

KEYWORDS: WiFi WLAN Wlan Wireless

1722
www.mixtelematics.com

1722
 1723
10.3.401 Knowledge Base Article 413

Article Number 413

Title How to install SQL with FM9.0 onwards

Created 04/06/2008 11:15:06

Created By Michael Chamberlain (MiX Telematics - Stellenbosch)

Last Modified 04/06/2008 15:05:22

Last Modified By Michael Chamberlain (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

Fleet Manager Professional 9.0 onwards.

----- SUMMARY -----

FM Administrator cannot connect to SQL database.

----- MORE INFORMATION -----

All FM Professional versions from v9.0 onwards do not ship with the MSDE version of SQL.

FM Professional v9.0 will only support SQL Server 2005 SP2 (Service Pack 2).

All editions of SQL Server 2005 will be supported, but must be SP2 to ensure compatibility.

(This includes SQL Express.)

The user will have to install SQL manually, either before or after the FM Professional installation.

----- SOLUTION -----

Please see the following document for more information on SQL Express:

SQL Express 2005.pdf

SQL Express should be included on your FM Professional 9 CD.

If it's not, you could download it from the following link:

http://www.microsoft.com/express/sql/download/default.aspx

------------------------------------------------------------------------------

KEYWORDS: SQL SQL2000 SQL2005 MSDE EXPRESS 2005

1723
www.mixtelematics.com

1723
 1724
10.3.402 Knowledge Base Article 414

Article Number 414

Title How to reformat csv files from FMWeb for calculation

Created 05/06/2008 11:45:55

Created By Juergen Isele (MiX Telematics - Germany)

Last Modified 05/06/2008 12:52:27

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ------ APPLIES TO ----

FMWeb 9 and later versions

----- SUMMARY -----

CSV files exported from FMWeb must be reformatted in e.g. Microsoft Excel before setting further
calculation steps

----- MORE INFORMATION -----

The CSV files exported from FMWeb provide raw data values, separated by a comma. Open the
file in e.g Microsoft Excel values may not be interpreted correctly due to automatic format settings.
Another issue is related to the Regional Settings provided by the Operation System. The CSV file
provides a "." as Decimal Separator, this characters must be adapted to the Regional Settings of
the Computer System.

----- CAUSE -----

This due to standard data format of a CSV file and its reduced format information

----- SOLUTION -----

For a detailed workaround download the document "How to reformat csv files from FMWeb for
calculation" from here

Guideline_to_Import_csv_files_from_FMWeb.pdf

----- STATUS -----

This is by design of a standard CSV file

------------------------------------------------------------------------------

KEYWORDS: FMWeb CSV Export Format FM-Web

1724
www.mixtelematics.com

1724
 1725
10.3.403 Knowledge Base Article 415

Article Number 415

Title Error 429 - FM 9.0 in Remote mode

Created 18/06/2008 12:11:33

Created By Hanli de Waal (MiX Telematics - Stellenbosch)

Last Modified 18/06/2008 12:21:49

Last Modified By Francois Bonthuys (MiX Telematics - Stellenbosch)

Details
----- APPLIES TO ----

FM9.0 Fleet Manager Professional in Remote mode

----- SUMMARY -----

When trying to login, the following errors appear:

(429) An unknown error occurred while attempting to login. Please enter valid credentials and try
again.

Error 429 - ActiveX component can't create object occurred in cXMLRequest.GetXMLNode(Line

970).The error has been logged.

----- MORE INFORMATION -----

The functionality requires the msxml4 that is usually installed with windows XP SP2.

----- SOLUTION -----

This is the msxml4 that is usually installed with windows XP SP2

If you have SP 2 installed, a reinstall of msxml4.dll should fix it anyway

Please Click here to download the msxml4.dll file

Please copy this file to C:\WINDOWS\system32

To register the new dll:

click on start -> run -> type in

regsvr32 "C:\WINDOWS\system32\msxml4.dll"
----- STATUS -----

The msxml4.dll for Windows XP SP2 is a prerequisite for FM9.0

------------------------------------------------------------------------------

KEYWORDS: FM9.0 Remote mode Error 429 ActiveX component GetXMLNode

1725
www.mixtelematics.com

1725
 1726

1726
www.mixtelematics.com

1726
 1727
10.3.404 Knowledge Base Article 416

Article Number 416

Title Uploading Extended Config using FM9.0

Created 18/06/2008 13:14:48

Created By Riaan Serfontein (MiX Telematics - Stellenbosch)

Last Modified 18/06/2008 13:14:48

Last Modified By Riaan Serfontein (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

FM9.0 Standalone mode

----- SUMMARY -----

The Extended Config tab is not visible when scheduling an upload via the Comms Scheduler

----- MORE INFORMATION -----

The Extended Config has been added to FM9 to enable the user to force the upload of Extended
Config for Devices where the SDK tool was used

----- CAUSE -----

We found that some units with DDR set prior to 8.5.16.x fail to upload the extended config and roll
back to the original states, with this function it can now be forced to be uploaded should you have
such an SDK script on the PC and it needs to be uploaded.

----- SOLUTION -----

The user should have Administrator Roles in the Fleet Manager Security Extension to make these
changes: Select Manage Roles/ Double click on Fleet Manager Communication Suite/Select the
Functions Tab/Drop Down on Communications and Active Tracking/Drop Down for Comms
Scheduler and select “Forced uploads of Extended Config” and click go. The Extended Config tab
will be visible under the Upload Tab when scheduling a Config Upload.

------------------------------------------------------------------------------

KEYWORDS: FM9.0 Standalone, Extended Config Uploads

1727
www.mixtelematics.com

1727
 1728
10.3.405 Knowledge Base Article 417

Article Number 416

Title FM9. Extended Config Uploads Via Comms scheduler

Created 30/06/2008 12:41:52

Created By Riaan Serfontein (MiX Telematics - Stellenbosch)

Last Modified 30/06/2008 15:15:07

Last Modified By Hanli de Waal (MiX Telematics - Stellenbosch)

Details ----- APPLIES TO ----

FM9. Extended Config Uploads Via Comms scheduler

----- SUMMARY -----

Extended configs, terminal modules, CAN firmware modules uploads via GPRS and WiFi ONLY

----- MORE INFORMATION -----

When trying to upload Extended configs, terminal modules, CAN firmware modules via GSM and
Dect the upload will fail.

The new uploading mechanisims such as CAN DDM, Extended Config and Terminal Modules can
only be done via GPRS and or Wifi.

Current SSC devices:

· Air Weigh truck scale

· DTCO+CANScript

· Trailer ID Script

· LoadTech IKON2000

· Serial TCO

· Kimax I

· Kimax II

· Euroscan/Transcan temperature sender

----- STATUS -----

This is by Design

------------------------------------------------------------------------------

KEYWORDS: FM9. Extended Config, GSM Uploads

1728
www.mixtelematics.com

1728