DAWNTM Users Guide

Mini Logger Family Overview

Revision: September, 2015

Copyright 1998-2015 by HEM Data Corporation

17320 West Twelve Mile Road Southfield, Michigan 48076-2105 U.S.A.
Voice (248) 559-5607 Fax (248) 559-8008
http://www.hemdata.com

1-1

Table of Contents
1. Introduction & Overview
Section Title
1.1
1.2
1.3
1.4

Page

Introduction and Overview

Included Materials
Software Installs
Operating Modes (Lights)

1-3
1-4
1-4
1-5

2. J1939 & ODB Mini Loggers

2.1
2.2
2.3
2.4
2.5
2.6
2.7

Configuring the Unattended Data Logger with DawnEdit

Converting Message Files to Scaled Data
Sample Data File
Messages
Accelerometer
Vehicle Connectors
OBD & J1939 Mini Logger Specifications

2-2
2-6
2-9
2-10
2-12
2-13
2-15

3. GPS

3-1

4. ADAQ Mini Logger

4-1

4.1
4.2
4.3

Configuring the Analog Input Channels

Configuring the Vehicle Parameters
Connectors

4-1
4-2
4-2

5. Reflashing the Mini Loggers Firmware

5-1

6. Advanced Logger Settings

6-1

7. Wireless Data Transfers from DAWN Mini Loggers

Section Title
7.1
7.2
7.3
7.4
7.5
7.6

Page

Description of WiFi on DAWN Mini Loggers

Preferences File Description
Transferring Data to the Local Server
Apache Software Download
Debug Commands
Router / Access Point Settings

8. Alerts

7-1
7-2
7-4
7-5
7-5
7-6

8-1

9. Helpful Hints

1-2

DAWN Mini Logger Family Overview

HEM Data Corporation

1. Introduction & Overview

TM

DAWN (Data Acquisition With In-Vehicle Networks) is HEM Datas in-vehicle network data
acquisition and analysis software and hardware solution. It acquires data from cars, as well as
light, medium, heavy duty trucks, and off-road vehicles.
DAWN is a versatile tool that acquires parameters and messages from in-vehicle networks
conforming to CAN, SAE J1939, J1708/J1587, SAE J1979, J1850, ISO15765, ISO9141,
ISO14230, and OBD-II. This means you can acquire network data from any automobile on the
road today from model year 1996 up to present and future models. In particular, the CAN
(Controller Area Network) protocol is now the most important protocol. Since 2008, all cars and
light trucks are using CAN.
DAWN also acquires J1939 CAN and J1708 data from heavy-duty vehicles such as trucks and
buses and off-road vehicles for agriculture, construction and marine applications. Sensor data
can also be acquired simultaneously.
The OBD Mini Logger family consists of four models as shown below. They are described in this
document. The number in the table below refers to the chapter where each is described.

1.1 Description of DAWNTM

DAWN OBD Mini Logger
Automotive,
Light Duty, Medium Duty
Trucks, CAN/OBD-II

DAWN ADAQ Mini Logger

Variety of analog inputs
plus signal conditioning

DAWN J1939 Mini

Logger Heavy Duty
Trucks and Off-road,
CAN/J1939

DAWN

TM

is an integrated software and hardware solution that includes:

Vehicle Interface Hardware shown above

Database Editor + Sample Database (OBD-II, J1939 or custom database)

1 year Support & Warranty on hardware and software

DawnPlot

Optional 1 or 2 day training class. Topics (defined by the user) range from product
training to application support. Material from the SAE seminar conducted by HEM Data
entitled Acquiring and Analyzing Data from Sensors and In-Vehicle Networks can also be
included. See details at:
http://www.sae.org/servlets/pdEvent?PAGE=getPDEventInfo&OBJECT_TYPE=PDEventI
nfo&EVT_NAME=C0522&COMMON_SUCCESS=TRUE.

TM

software (option)

1-3

1.2 Included Materials

The Mini Loggers have the following accessories:

a USB cable

a microSD card (insert card with writing on the outside)

a USB microSD card reader

1.3 Software Installs

Install the software in the following order.

A. Install DawnEdit
To run the installer for DawnEdit, run DawnEdit Installer.msi on the CD. This dialog shows the
initial install screen.

B. Install Hardware Drivers

NOTE: You do not need to install the hardware driver unless updating the logger firmware.

Connect the logger to the PC via the shipped USB cable.

When Windows ask for the driver location, point to the directory c: \dawn\Drivers

1-4

1.4 Operating Modes

When you plug in the logger, you should see a blinking blue LED which indicates that the vehicle
is off and the logger is waiting for commands. There are five operating modes indicated as
follows:

1) Flashing Blue LED - Ready/Idle/Command Mode

This mode shows the logger is connected but idle. After you turn off the vehicle, please wait until
the logger LED flashes blue before disconnecting the logger. Some vehicles transfer messages
up to a minute or more after turning off the ignition, especially hybrids. Opening the vehicle door
or locking the door may expedite the vehicles ECUs going to sleep and therefore not sending any
more messages to the logger.

2) Flashing Green LED - Acquisition Mode

In this mode, the vehicle is on and the logger is collecting vehicle data.
***DO NOT DISCONNECT THE LOGGER WHEN FLASHING GREEN .***

3) Flashing Red LED - Transition Mode

Normally, red is displayed when the file is closing. The logger will attempt to resync for a few
seconds. After a few seconds, it will transition to ready mode (blinking blue LED). If the logger
blinks red when plugged-in, this means the logger failed to read the microSD card. Un-power the
logger and reinsert the card, and then try again.
***DO NOT DISCONNECT THE LOGGER WHEN FLASHING RED.***

4) Flashing Light Blue - Low Power Mode

There is a fourth mode. After the logger is dormant for several seconds, it will move to a lower
power mode and blink light blue. This mode is safe to disconnect the logger.

5) Flashing White - Wireless Transfers Mode

There is a fifth mode if your unit has WiFi or a cellular modem. It will blink white while transferring
data. After it blinks red, it will then blink white while it is attempting to perform a data transfer. See
Section 6 for details.
In summary, remove the logger or its microSD card only when it is flashing blue or light
blue.

1-5

2. OBD & J1939 Mini Loggers

DAWN OBD Mini Logger

TM

In the left picture, the left slot is for the microSD card. This card can be as large as 32 GB. The middle
connector is the USB connector. The serial connector is on the right.

DAWN J1939 Mini Logger

TM

In the picture on the left, the microSD slot is on the top left. The connector on the bottom left is
the TTL serial connector. The USB connector is on the upper right.
The microSD card can be as large as 32 GB.
The 2 GB card should be sufficient for your application. If you believe you need a higher capacity
card, contact HEM Data.

2-1

2.1 Configuring the Unattended Data Logger with DawnEdit

DawnEdit is the only DAWN software that you need to acquire data with the OBD and J1939 Mini
Loggers. Open DawnEdit at C:\DAWN. Create a shortcut to this program.
This section will get you started with the DAWN Mini Loggers. Appendix A is a reference
document that describes the features of DawnEdit in detail. It is located on the DAWN CD in the
Users Guide directory.
There is a 6 minute video on the HEM Data website that covers the following steps. It is available
at http://www.hemdata.com/demo/DawnEditDemo.html.

Step 1: Building a Database with Available Parameters

The first step is to determine the parameters that are actually on the vehicle you want to test. If
you already know this, or want to bypass this step, you can move to Step 2.
For Automotive OBD:
If you are using the OBD Mini-logger, there is an extra step for determining the available
parameters. First open the database OBD Mini from c:\dawn\database. Then make sure the
parameters, Available Parameters $1-20 through Available Parameters $81-A0, are enabled.
Create a new config.txt file and put it on the loggers microSD card.
For Automotive Enhanced OBD (EOBD):
This is if you are using an OEM specific database provided by HEM Data (except Toyota). First
create the database using Make OEM Database. Create a new config.txt file using the option
Logger > Create Config for Available EOBD.
For Toyota (EOBD):
Place the config.txt file onto the microSD card from c:\dawn\configurations\toyota a8.
Connect the logger to the vehicle. (For J1939 look at the microSD card to be sure there is no
config.txt file on it.) Take data for about a minute on the vehicle with the engine running.
Remove the microSD card from the logger and insert it into the reader. Use the microSD to USB
reader supplied with the logger if your computer doesnt have a microSD slot.
Note: the config file must be on the root of the microSD card (not a subdirectory) and have the
name config.txt in order for the logger to read it.

2-2

Use File>Open to select the database you want to use. If you are using the J1939 Mini Logger it
is suggested that you start with the database J1939 Mini. For the OBD Mini Logger, it is
suggested that you start with OBD Mini. A more complete database exists called OBD Full or
J1939 Full. Use this database if you want to take DTCs or think your vehicle supports specific
parameters that are not listed in OBD Mini.xml.
To have DawnEdit determine the Available Parameters, select one of the following under the
Make menu depending on the logger you are using:

Protocol

Selection

J1939
OBD
EOBD

Extract J1939 Messages to Database

Extract OBD PIDs to Database
Extract Toyota EPIDs or Extract EOBD Parameters (for all other OEMs)

This will compare the data file you just acquired to the master database, strip out the parameters
whose messages are not detected, and allows you to save the result as a new database.
Therefore, you can easily create a database that is specific to each vehicle you are testing.

Step 2: Selecting (Enabling) Parameters to Acquire

The next step is to Enable the parameters you want to acquire by checking the box in the second
column. The OBD Mini Logger will acquire a maximum of 50 messages. If more than one
parameter is in a message then you can acquire more than 50 parameters. The J1939 Mini
Logger can acquire all transmitted messages (default with no config.txt file).
The following are some handy, advanced features of DawnEdit:

Highlight a group of rows in the Enable column to enabled/disable that group.

Click on the Enable column heading. This will sort the parameters by which ones are
enabled. Click on the Name header to sort by name again.
2-3

Step 3: Writing Configuration File

Click on the Mini Logger icon
or use the Menu option Logger > Create Mini Logger Config
File. Use the following dialog to define the sample rate and where you want to store this config
file. For J1708, do not create a config file. Instead create a prefs file using the Enable J1708
checkbox.

Sample Rate
The OBD sample rate is generally limited to 80 samples/second aggregate (number of messages
x sample rate). For legislated OBD (not enhanced), there is generally one parameter per
message.
***NOTE: If you have an older model logger (data is stored in text files not binary), the sample
rate will be off by a factor of 10. For example, to take 1 sample/second enter 10.
Directory
For the directory, there are some options:
Browse: This can be a local directory or the MicroSD card.
The button Set to DB Directory keeps a record of the config file that corresponds to the
database. This is handy if you have several configurations.
File Name
The Mini Logger will only use the file config.txt. You have a few options in creating a configuration
file.
Write the file as config.txt
Write it with the database name; this is handy if you have many configurations and want
to keep track of them.
The simplest choices are to point to the microSD card root directory and select the option to write
config.txt.
Configure OBD logger for J1939
The OBD Mini Logger is capable of logging J1939 messages. Use this checkbox if you wish to
use the OBD logger for this purpose. In addition you will need to set the baud rate to 250k in the
2-4

Create Mini Logger Prefs File Dialog. It is also recommended to use the Do NOT Request VIN
Checkbox in the same dialog.
Configure OBD for legacy
Use this checkbox if you are taking legacy OBD data (some vehicles before 2008, and all before
2003).
After making your selections, click on the button Create.
If you did not directly store the config.txt file on the microSD card, then use Windows
Explorer to do so.
You should now have transferred the configuration to the MicroSD card. The configuration file is
entitled config.txt. You can double click on it to see its contents. A sample config.txt file is shown
below. This example file specifies 9 OBD parameters starting with B. J designates the sample
period.

Step 4: Logging Data

When you change config.txt make sure that you repower the logger since it only reads this file on
start-up.
Insert the microSD card into the logger. Plug the Mini Logger into the vehicle. For the J1939
Logger, make the turn to lock the unit on the connector. Logging will start a few seconds after
ignition and stop when the ignition is turned off. Note the logger colors as described in Section
1.3. If there are no lights, check your connection.
If the logger blinks red immediately, this means there is a problem reading the MicroSD card.
Unpower the logger, remove the MicroSD card and then reinsert the card before trying again.

2-5

2.2 Converting Message File to Scaled Data

Remove the logger from the vehicle. Insert the microSD card into the computer using the supplied
USB adapter or equivalent. Before inserting the microSD card, you may find it helpful to blow on
each so the reader will work better.
You have the option to work directly with files on the card or you can copy the files to another
directory. The latter is recommended since it provides a backup and doesnt clutter the card with
the converted files.
The files are organized in folders by date. The binary .IOS files contain the stored messages. The
next step is converting these messages to scaled engineering parameters.

2.2.1 Date and Time in File Name

The start date and time of the trip are encoded in the file name. The file encoding is the following:
st
1 digit is the year; 2011 is 1
nd
2 digit is a letter that designates the month, e.g. March is C.
rd
th
3 and 4 is the day of the month.
th
th
5 and 6 is the hour in military time. Unless you set the time, it is eastern time in the US
th
th
7 and 8 is minutes.
th
For example a file name 1C051350 means March 5 , 2011 at 13:50.
To change the time of the logger, refer to a subsequent section on Advanced Logger Settings.

2.2.2 Procedure to Convert Files

The following procedure describes how to convert the message files stored on the logger to a
CSV file containing scaled engineering parameters.
In DawnEdit, open the database you used to create the config.txt file. Select the menu option
Convert Mini Logger Data File to CSV to open the following dialog: (or click:

2-6

Location of Files to be Converted and Saved

First select the directory where the files are located that are to be converted.
Second define where the CSV files are to be stored. It is simplest if you use the checkbox
Save to Same as Directory as Source files, which is the default. This will save CSV files
in the same directory as the message files. If the box is unchecked then all resulting CSV
files will be saved in the same specified directory.
Conversion Settings
Dialog Option

Description/Comments

Default

Use absolute time stamp

Absolute Time is the date and time using

military time.

Relative Time

Convert to local time

Only use if you are using built-in GPS on the

DAWN Mini Logger where time is set to UTC /
Greenwich Mean Time.

Unchecked

Append each data file to a

single CSV

Appending means combining files, e.g.

several trips can be combined into one file for
the entire day. Only works when not
converting subdirectories.

Individual Files

Use file naming seed

CSV files are named with a seed followed by

a count number.

Unchecked

Merge GPS Files into CSV

If the logger took GPS data, it is also written to

the CSV file as additional columns.

Checked

Calculate fuel economy

For OBD only. If Air Flow Rate from Mass Air

Flow Sensor and Vehicle Speed Sensor are
available, fuel economy will be calculated in
the CSV file

Unchecked

Calculate engine idle time

Calculates engine idle time in the CSV file

based on RPM and vehicle speed.

Unchecked

Dialog Option

Description/Comments

Default

Convert individual ACC

Files

Converts ACC files from the built in

accelerometer. Sampled at 100Hz. Contact
HEM Data for this advanced feature.

Unchecked

Merge ACC files into CSV

Coverts and merges ACC files. This option

also rotates the axes if necessary so that the
normal force of gravity acts on only one axis.

Unchecked

Create message file from

binary IOS

Converts the binary IOS data file to an ASCII

message log file.

Unchecked

Automatically convert files

in this folder

If DawnEdit is open, any IOS files added to

the IOS Files Directory will be automatically
converted and saved with the current settings.

Unchecked

Use alarms/conditions

Only converts files where certain conditions

are met. Use with the Automatically convert
setting above and receive email/text message
notifications. See section 8 for details.

Unchecked

Additional File Conversion

2-7

Sample Rate
The dialog will show the sample rate used in the message file if it is known. You have the option
to override the rate or define it if it is unknown. It only makes sense to use a sample rate that is
equal to or less than the rate used to acquire the data.
When done defining the options, click on the Convert button.
After creating the CSV file the options for reviewing the data are to use:
A spreadsheet
Another data analysis software tool
DawnPlot which is an option. See Appendix B.
Below is an example file showing appended/concatenated/combined data files using Absolute
Time. Notice the jump in time between lines 292 and 293.

To show the Absolute Time in Excel: highlight the time column, right click, and select Format
Cells, then select Time. Select 3/14/01 13:30. Since there is not an option to show seconds
with our previous selection we need to Select Format Cells again and select Custom. Then add
:ss so the Type: reads m/d/yy h:mm:ss.

2-8

2.3 Sample Data File

An example CSV file with Relative Time is shown below. To make the display of the titles more
manageable, you have two options:

In DawnEdit, you can rename a parameter using the far right column named Label. The
Label is what is used in the data files.

Use word wrap in Excel to keep the cell width to a minimum.

2-9

2.4 Messages
The message files are intermediate files. You dont need to know their format, but if you are
interested they are now explained.
The message files are in different formats for the various Mini Loggers. There is no message file
for the ADAQ and GPS units. The OBD Mini Logger messages are stored as .IOS files. The older
model J1939 Mini Logger stores the messages in a .LOG file, but newer versions use the binary
IOS format. Each of these two formats will now be explained.

2.4.1 Binary Mini Logger Message Format (.IOS File)

The .IOS file written to the OBD Mini Loggers microSD card contains the messages received by
the logger. An example message created by using the Create message file from binary IOS
convert checked box is below:

Each line contains the following:

1. Timestamp.
2. Engine Controller. The last two digits designate the responding engine controller.
3. Test Mode.
4. OBD message ID (PID/PGN #).
5. Data.
The first line contains the ASCII codes for the VIN as transmitted by the vehicle.

2-10

2.4.2 Legacy 1939 Mini Logger Message Format (.LOG File)

The .LOG file written to the J1939 Mini Loggers microSD card contains the messages received
by the logger. An example file is now shown. The first column is the time. Second is the CAN ID.
The middle four characters of the CAN ID are the PGN number. The rest of the message has 8
bytes of data.
The first two characters (byte) define the priority. The last two characters (byte) define the
controller ID that sent the message.
0.0052 0CF00400 F0 7D 7D 00 00 FF FF 7D
0.0155 0CF00203 C0 00 00 FF F7 00 00 03
0.0200 0CF00400 F0 7D 7D 00 00 FF FF 7D
0.0319 0CF00203 C0 00 00 FF F7 00 00 03
0.0357 0CF00400 F0 7D 7D 00 00 FF FF 7D
0.0355 0CF00300 DF 00 00 FF FF FF FF FF
0.0481 0CF00203 C0 00 00 FF F7 00 00 03
0.0497 0CF00400 F0 7D 7D 00 00 FF FF 7D
0.0643 0CF00203 C0 00 00 FF F7 00 00 03
0.0651 0CF00400 F0 7D 7D 00 00 FF FF 7D
0.0806 0CF00400 F0 7D 7D 00 00 FF FF 7D
0.0804 0CF00300 DF 00 00 FF FF FF FF FF
0.0812 0CF00203 C0 00 00 FF F7 00 00 03
0.0824 18F00029 FF FF FF FF FF FF FF FF
0.0822 18FEF200 00 00 00 00 7F 02 FF FF
0.0830 18FEF000 FF FF FF FF FF 00 00 FF
0.0844 18FEF100 FF 00 00 C0 00 00 1F FF
0.0947 0CF00400 F0 7D 7D 00 00 FF FF 7D
0.0973 0CF00203 C0 00 00 FF F7 00 00 03
0.0982 18F00503 7D 00 00 7D 4E 20 4E 43
0.0991 18FE4A03 0F 1F 4F FF FF FF FF FF
0.1101 0CF00400 F0 7D 7D 00 00 FF FF 7D
0.1151 0CF00203 C0 00 00 FF F7 00 00 03
0.1245 0CF00400 F0 7D 7D 00 00 FF FF 7D

2.4.3 Why Binary?

Binary files are 1/3 the size of their ASCII counterpart. This increases efficiency of data storage
and data transfer time, especially over WiFi and cellular. Less data means less cost over cellular.
The following describes the length in bytes for common messages using the binary format
(Timestamp + Address + Data):
OBD-II
11 or 12 bytes
J1939
16 bytes
Normal
Generally 14 bytes
EPID
Generally longer. ~16-32 bytes

2-11

2.5 Accelerometer
To enable the accelerometer you must put a prefs.txt file onto the logger. Use the checkbox in the
Create Mini Logger Prefs File Dialog.
ACC files are converted in DawnEdit along with the in-vehicle data files. In DawnEdit, open the
database you used to create the config.txt file. Select the menu option Convert Mini Logger Data
File to CSV (or click:

).

There are two options for ACC conversion.

1. Convert individual ACC files: Converts the ACC file to its own CSV file.
2. Merge ACC files into CSV: Merges the ACC data with the corresponding IOS data. This
option also corrects the axes so that the normal force of gravity only acts on one of the
axes.
For OBD, after rotation the axes correlate to the following:
X: Up and Down (Up is positive)
Y: Left and Right (Right is positive)
Z: Forward and Back (Forward is positive)

Accelerometer Direction
OBD

J1939

2-12

2.6 Vehicle Connectors

2.6.1 Sixteen Pin J1962 Automotive Connector

OBD Mini Logger

Vehicle Connector

Has power and CAN pins

in this picture

J1962 Pin

Has two grounds, power

and CAN in this picture

J1962 Pin Description

1

Discretionary* (GMLAN SW CAN Line)

+ line of SAE J1850

CAN2+, (GMLAN MS CAN H),

Chassis/Case Ground

Signal Ground

CAN+, GMLAN HS CAN H

K Line of ISO 9141-2

Discretionary*

Discretionary* (GM ALDL)

10

- line of SAE J1850

11

CAN2-, (GMLAN MS CAN L), Short to ground

12

Discretionary*

13

Discretionary*

14

CAN- (GMLAN HS CAN L), Short to ground

15

L line of ISO 9141-2

16

Unswitched Vehicle Battery Positive

* Discretion of OEM since specification does not define these pins.

2-13

2.6.2 Nine Pin J1939 Heavy Truck Connector to the Adapter

Logger

Truck Adapter

Shows J1939, J1708

and power pins

Shows only the power pins

in this adapter

Note: the connection between CAN HI and

CAN LO must have a 120 Ohm resistance.

J1939 Truck Adapter

2.6.3 Six Pin J1708 Connector

Female

Male

2-14

2.7 OBD & J1939 Mini Logger Specifications

OBD Mini Logger Specifications
Protocols

Real-time clock

ISO 15765-4 (CAN, 11- Yes

/29-bit, 250/500 kbps)

Analog Inputs

Yes

Cabin Temperature
Sensor

Option

3-axis MEMS
Accelerometer

Option

Vehicle Battery
Voltage

Option

Expansion

Optional 8 channel
ADAQ Mini Logger

SAE J1850 PWM &

VPW

Check with HEM Data for

availability

ISO 9141-2

Check with HEM Data for

availability

ISO 14230-4 (KWP)

Check with HEM Data for

availability

No. of Protocol Ports

(Channels)

Two CAN channels (250 or

500kbps)

Real-time PC data

Option

Connections to PC

WiFi

Stand-alone Logger

Yes

Store Messages

Yes

Supply Current:

80 mA. Up to 200mA
with WiFi

On-board Storage

Micro SD card 2GB

standard. Up to 32 GB
allowed.

Operating
Temperature C

-40 to +70

Auto Start-up

Yes

Operating voltage

4 to 36V

LEDs for status

RGB

Power Draw while

sleeping

3 mA

Operating system

Proprietary RTOS
Warranty

1 Year

GPS (NMEA 0183)

Option. Internal to Mini

Logger.

Wireless (WiFi)

Option. Internal to Mini

Logger.

Cellular modem
(External)

Option. Connects with WiFi

or serial cable.

Cellular modem
(Internal)

Check with HEM Data for

availability.

Operating system

Proprietary RTOS

Environment
Size (inches)

OBD Connector:
1.9W x 0.70H x 1.5L

Size (mm)
48W x 18H x 38L

2-15

J1939 Mini Logger Specifications

Protocols
SAE J1939 CAN

Yes

SAE J1708/1587

Yes, supported in h/w. Needs firmware update.

No. of Protocol Ports (Channels)

One CAN channel and one for J1708.

Real-time PC data

Option

Connections to PC

WiFi

Stand-alone Logger

Yes

Store Messages

Yes. Convert to scaled engineering parameters as a post process

On-board Storage

Micro SD card 2GB standard. Up to 32 GB allowed.

Auto Start-up

Yes

LEDs for status

RGB

Operating system

Proprietary RTOS

GPS (NMEA 0183)

Option. Internal to Mini Logger.

Wireless (Wi-Fi) or equivalent

Option. Internal to Mini Logger

Cellular modem

Option. Connects with WiFi or serial cable.

Wake-up Input

Yes

Real-time clock

Yes

Analog Inputs
Cabin Temperature Sensor

Option

3-axis MEMS Accelerometer

Option

Expansion

Optional 8 channel ADAQ Mini Logger

Environment
Size (inches)

J1939 Connector: 1.5 Diameter x 2.3 Long

Size (mm)

38.1 Diameter x 58.4 Long

Supply Current:

80 mA. Up to 200mA with WiFi

Operating Temperature C

-40 to +70

Operating voltage

6 to 36V

Power Draw while sleeping

3 mA

Warranty

1 Year

2-16

3. GPS
If you have ordered a Mini-Logger + GPS from HEM Data, the GPS is built into the logger.
The Mini-Logger writes the GPS data to a CSV file. The file uses the same naming convention as
the other files (IOS, ACC, LOG) and has as .GPS extension.
To merge the GPS data with the in-vehicle data, use the Merge GPS files into CSV setting in the
Convert Mini Logger Data File to CSV dialog. See section 2.2 for more information on file
conversion.

3.1 Data Format

The GPS data is stored as a CSV file with the extension .GPS. A sample of the GPS data file is:

A sample GPS data file

To import into Excel use the wizard settings Delimited, Comma. The first column is the time in
milliseconds since the start of the test. The second column is the delta time between readings in
msec.
Columns C, D & E are the Latitude, Longitude, and Altitude (m). Columns F & G are the vehicle
velocity (kph) and heading (deg from N).
Column H & I is the UTC date and time. This is the same as Greenwich Mean Time (GMT)
without Daylight Savings.
Date above is Feb 17, 2010.
Time above is 3:40.49 pm.

3-1

Column J is the fix quality:

0 = invalid
1 = Time fix only
2 = Poor GPS with time
3 = High resolution GPS
The last column is the number of satellites transmitting data to the GPS unit.

3.2 GPS Specifications

GPS Solution
Frequency
Sensitivity
Acquisition
Tracking
Position Accuracy
Without aid
DGPS (SBAS(WAAS,EGNOS,MSAS))
TTFF (Time to First Fix)
Cold Start
Warm Start
Hot Start
Protocol
DGPS
Update Rate
Current Consumption
Acquisition
Tracking
Working Temperature

MTK MT3329, 66 Channels

L1, 1575.42 MHz ; C/A Code
-148 dBm
-165 dBm
3.0 m 2D-RMS
2.5 m 2D-RMS
<35 Seconds (Typical)
<34 Seconds (Typical)
<1 Seconds (Typical)
NMEA 0183
SBAS [WAAS, EGNOS, MSAS,GAGAN]
1 ~ 10 Hz
48 mA
37 mA
-40 C to +85 C

3-2

4. ADAQ Mini
The DAWN Mini ADAQ measures a variety of input types including voltage, current,
temperature, digital, frequency, PWM, and inclination. It outputs measured data to a CAN
network.
The Mini ADAQ is used with either the OBD or J1939 Mini Logger to store the data or transfer
data via cellular or WiFi to a website, PC or mobile application.
The figure below shows a schematic of the DAWN Mini system to acquire both in-vehicle network
and analog data. The system uses two CAN networks that are independent. One is the standard
in-vehicle network acquiring heavy duty or light duty vehicle data. The other is an instrumentation
network using the Mini ADAQ to acquire analog data. The vehicle network will not see the
instrumentation network; only the Mini Logger will. It is not required to acquire in-vehicle network
data to acquire analog data.

Vehicle and analog CAN network diagram

Networks are independent; The Mini Logger stores the data from both networks.

4.1 Configuring the Analog Input Channels

The ADAQ units will be shipped pre-configured by HEM Data. The installation will include a
DawnEdit database already set up for your application.
The DawnEdit database will include the analog channels specified by the user including the
conversion factors. Feel free to rescale the units using the Offset and Factor columns.
For example to rescale C to F where the factor is .03125 and offset -273, change
the factor to .05625 and offset to -459.4. (.03125 * 1.8 = .05625 and -273C = 459.4F) Then change the unit column to F.

4-1

4.1.2 Configuring the Vehicle Parameters

Either a standard OBD or J1939 database will come with your DAWN Installation merged with the
analog channels specified. Simply check the parameters you wish to acquire as described in
Step 2 in Section 2.1. Then choose the menu option Logger > Create Mini Logger Config File...
or click the

button. Make sure to choose the Configure for ADAQ checkbox.

Choose the desired directory under Save Directory.

When finished, click the Create button.
Next, copy the config file onto the OBD or J1939 microSD card root (not a subdirectory). Note
that the logger will only use the file named config.txt.

4.1.3 Prefs.txt File

If using the OBD Mini Logger with the ADAQ, the second CAN channel must be set to 250kbaud.
This is done by having a prefs.txt file on the loggers microSD card with the following line of text:
CAN2Baud=250000
The logger may be shipped with this file already on the card. If not, if must be created. The logger
will blink blue-green if the baud rate is incorrect.

4.2 Converting Message File to Scaled Data

See Section 2.2.

4.3 Connectors
See Appendix D ADAQ Wiring Guide

4-2

5. Reflashing the Mini Loggers Firmware

DO NOT reflash the mini logger unless instructed by HEM Data! It may cause your logger to
become inoperable.
The reflashing procedure for any of the mini loggers can be divided into three major steps:
A. PC connection to the logger
B. Putting the logger in Program mode
C. Initiating the reflashing program with a DOS command
To flash the device, use the following procedure.

A. PC Connection to Logger
1. Plug the device into the USB port
2. If not previously installed, Windows will ask for a driver, locate the driver in
C:\DAWN\Drivers.
3. The device will be assigned a COM port by Windows. Look in Windows Device Manager
for the COM port number. The COM Port will also be displayed in ecTerm in the next
step.

B. Putting the logger in Program Mode with ecTerm or HyperTerminal

4. Open the program ecTerm.exe. ecTerm is located in C:\Dawn\Reflashing Files. This
software allows you to communicate with the logger.
5. Hit the COM Setup button. For Port select the port seen in Device Manager.
6. Baud rate settings, etc. are not important.
7. Click the Configure Terminal button and check the Append line feeds to incoming
carriage return box and hit OK.
8. Connect by clicking on the icon of a phone off the hook. Click on the large black area to
get a cursor.
9. Type program and hit Enter
10. The device will enumerate as an HID-class device in Device Manager
11. If there is a question mark on the icon in Device Manager (may happen the first time you
enter flash mode), unplug and repeat from step 1. OBD & J1939 Loggers flash blinking
green and red when it is OK. ADAQ unit LED turns off.

5-1

C. Initiating the Reflashing with the DOS Command (CMD)

12. Open a DOS command prompt with administrator privileges (Start->Run...->'cmd' on XP,
or Start->All Programs->Accessories->Command).
13. Prompt->Right click (Run as Administrator on Vista/7)
14. Make sure the .hex file is in C:\DAWN\Reflashing Files. Change to this directory by typing
the following command: cd C:\DAWN\Reflashing Files. These steps are shown in the
figure below.
15. Type the following command depending on which unit you are reflashing and then hit
Enter
OBD Mini Logger:

mphidflash -w OBD-3.hex -n -r

J1939 Mini Logger:

mphidflash -w J1939-3.hex -n r

ADAQ Mini Logger:

mphidflash -w DAQ-Module-3.hex -n r
Make sure the name you type for the hex
file matches the file you are actually using
which may not be the one shown in the
above examples

16. You should see: USB HID device found: 503808 bytes free
Erasing...
Writing hex file 'OBD-II.hex':.............[many dots] Resetting device... This will take about
a minute.
17. If the flashing completes correctly, the device is ready to go. It should flash blue.
18. If there is any error, please re-run the above command and alert HEM Data if the error
repeats.

5-2

19. To reflash additional loggers:

a. plug the new unit into the USB cable.
b. ecTerm should reconnect automatically. If not hit the connect button; type
Program and hit Enter.
c.

Return to cmd window and click the up arrow to get the previous command to
reflash the device.

5-3

6. Advanced Logger Settings

There are commands that can be issued by ecTerm to change advanced settings.
Follow the first 9 steps for the procedure as described above to reflash a logger. Do not issue the
Program command. Make sure to click on the large black area to get cursor.

Applies to All Loggers

The following commands apply to all loggers.

Setting Date and Time

Type settime & hit Enter
Answer the questions. Your answer will be displayed after you click Enter. You'll need to
synchronize the seconds to the appropriate clock. Once you hit Enter after entering the seconds,
the clock will be set.

Other Commands
Other commands are listed below. Follow instruction listed above.
getnvm
prefs

Displays non-volatile memory including serial number. This is also a good command to
be sure the logger is responding to your commands.
Summary of Preference Settings

ADAQ Only
snap

Returns one measured value for each channel. The value type displayed is set in
the firmware by HEM Data.

i2c

Returns internal logger temperature and time

ch3val

Returns values of channel 3 in this example. Use channel number of interest.

Returns values for three various voltage ranges, current, temperature.

ch3valavg

Return average values

WiFi
startwifi

Start the WiFi process to transfer data to a target web page. This allows you to test
WiFi without being in the vehicle. Also valuable to debug wifi settings defined in
prefs.txt file.
6-1

7. Wireless Data Transfers from DAWN Mini Loggers

7.1. Description of WiFi on DAWN Mini Loggers
WiFi is a convenient way to transfer data from the logger to a local network or internet server.
Program each logger to work with one user-specified WiFi access point (AP). Each logger can
have a different AP. These settings are described in Section 2 below.
Whenever the vehicle returns to the depot, then the logger will start to transfer data to the server.
The logger initiates a connection as needed to keep power consumption to a minimum. The
logger should be within 40 yards of the AP. (The AP must have a signal of -80dBm or stronger at
the loggers position.) Use repeaters to gain extended range.
After the logger changes colors from dark blue (standby) to green (actively logging) to red
(closing the file) and before it returns to dark blue, it will blink light blue to designate that it is
transferring the file(s) using WiFi.
The logger has an 802.11b/g/n chip and should be compatible with most hotspots.
The loggers communicate with a proprietary PHP script running from an Apache server as
described in Section 3 below. Active Directory is not supported and is not involved. The
destination server should have this script.
The logger communicates with a Microsoft Windows Server file using HTTP. It does not use
SMB/CIFS.
The logger is not FIPS 140.2 http://en.wikipedia.org/wiki/FIPS_140-2 compliant. This could be
supported if needed, but significant cost will be added if certification needs to be acquired.
The following is a chart of the Mini Loggers capabilities using Ad Hoc mode (logger is hotspot)
and Infrastructure mode (external hotspot).

Real-Time Data
Automatic File Upload

Ad Hoc
Yes. With DawnPlot or smartphone
Yes. Upload to smartphone

6-2

Infrastructure
No
Yes. To Apache server

7.2 Preferences File Configuration

To configure a preferences file in DawnEdit2, click the menu option Logger > Create Mini
Logger Prefs File or click the
they define different settings.

button. The prefs.txt file does not replace the config.txt file as

This dialog also allows the user to Enable the Accelerometer, Disable GPS, and Enable J1708. If
logging J1708, do not create a config file from the J1708 database: use a config file only if you
also are using J1939.
The example settings will transfer the data files to the website
http://www.hemdata.com/loggerUpload/uploads/. You can change this to go to your own web
server. It is recommended that you first transfer files to the HEM Data site to test your WiFi
settings, and then to your own web server. You are free to use our test server, but please send us
7-2

an email at support@hemdata.com letting us know. You can also define a computer on your
network as the destination as long as it has the Apache software.

7.2.1 WiFi Router (Access Point) Settings

Your WiFi router may use some non-standard settings. If you follow the instructions listed below
and still have problems, then try using the routers default settings. Consult your routers user
manual for details. The router settings are accessed by typing in the routers IP address. Common
default IP addresses are: http://192.168.1.1/ or http://10.0.0.1. An example of a router user
interface is shown at the end of this section.
Channel
Set channel on router to 1, 6, or 11. These are the only valid channels.
Router Name - SSID
Maximum 32 characters, no spaces or tabs or newlines.
Wifi Encryption
There are 4 options supported for encryption with one of the four being no encryption. They are:
None - no encryption/authentication

WEP Open

WEP Shared

WPA - WPA-PSK Personal or WPA2-PSK Personal (TKIP or AES)

If you are not sure whether to use wepopen or wepshared, start with wepopen.
Password
If you are using wepopen or wepshared, then enter the WepKey from your router. It is in hex and
is either 10 nibbles (64-bit) or 26 nibbles (128-bit). If you are using WPA, this password has a
maximum of 32 characters, without spaces, tabs or newlines. If none is selected, then this entry is
ignored.

7.2.2 Upload Settings

Server Name
The server name is where you want the logger to transfer the data. It must have a maximum 25
characters, without spaces, tabs or new lines. To easily find the IP of a server you can ping it
from the command prompt. (Press Window + R to open the Run dialog and type cmd to open
the command prompt). Type ping servername.com and the prompt will return the IP address in
[square brackets]. If you wish to simplify your initial testing, you could have a WiFi connection
between the logger and a local computer. In this case, you would use the local computers IP
address.
Server Port
This can be an integer value from 1-65535 and is typically 80.
Server URL
It must have a maximum 25 characters, without spaces, tabs or new lines. Note the upload.php
does not have an s at the end of upload. This upload php file is described in the next section.
The HEM Data website where the data is sent according to the settings above is
http://hemdata.com/loggerUpload/uploads/
7-3

7.2.3 Upload Interval

Maximum File Duration
Set a maximum file duration in seconds to cap file size and/or create near real-time data uploads.
Once you have all the settings, click the Create button. A file prefs.txt will appear in the Save
Directory at the top of the dialog.

7.2.4 Additional Options

CAN1/CAN2 Baud Rate
Set custom baud rates for CAN buses 1 and 2. J1939 default is 250kbaud and OBD is 500kbaud.
Do NOT Request VIN (OBD Logger only)
Check this box to stop the OBD Mini Logger from automatically requesting the VIN. Normally
used when using the OBD logger for Heavy Duty vehicles or raw CAN.

7-4

7.3 Transferring Data to the Local Server

The following are sample scripts for local web server that uploads the data using WiFi. Exhibit 1
uploads the data. The connection is initiated by the logger. Exhibit 2 is a web form for testing an
upload without using the logger. The unit communicates with a proprietary PHP script running
from an Apache web server.

Upload.php
<?php
$uploaddir = "uploads/";
$uploadfile = $uploaddir . $_POST['VIN'] . "-" . basename($_FILES['datafile']['name']);
if (move_uploaded_file($_FILES['datafile']['tmp_name'], $uploadfile)) {
echo "File is valid, and was successfully uploaded.\n";
chmod($uploadfile, 0666);
} else {
echo "Possible file upload attack!\n";
}
?>
<html><head></head><body>
Done.
</body></html>
Exhibit 1 Manages communication with Logger

Index.php
<html><head>
<title>Upload</title>
</head><body>
<form enctype="multipart/form-data" action="upload.php" method="POST">
VIN: <input name="VIN" type="text" /><br>
Send this file: <input name="datafile" type="file" />
<input type="submit" value="Send File" />
</form>

</body></html>
Exhibit 2 Web form for uploading a file without using the logger

7.4 Apache Software Download

To download the apache software, go to the XAMPP website at:
http://sourceforge.net/projects/xampp/

7-5

7.5 Debug Commands

To better understand the Wi-Fi process, hook up the logger to the USB cable and PC and use
ecTerm.exe or HyperTerminal.exe. Refer to Section 4. Commands are:
prefs
printout of the prefs.txt
startwifi
Start the WiFi process to transfer data to a target web page. This allows you to
test WiFi without being in the vehicle. Use this command in Step 16 in Section 4.
From the DOS CMD prompt, you can use the command ipconfig to obtain IP information as
shown below.

7-6

7.6 Router / Access Point Settings

Examples of two router screens that work with the Mini Loggers are shown below for reference.
The router channel must be 1,6,or 11.

7-7

8. Alerts
DawnEdit Alerts serve two functions.
1.) Convert only the files that meet a certain criteria.
2.) Automatically receive email/text notifications when conditions are met.
To access alerts check the Use Alarms/conditions button in the Convert Mini Logger Data File to
CSV dialog. (If it is already checked, double-click).

Alert Settings File

The default is called default.alm. The user may either start with the default settings file or use
New to create new file with a unique name.
Conditions Table Columns
Define conditions in the table provided. Once data is put into a cell, the table automatically adds
an additional row.
Each row is an ANY/OR conditioning meaning that any one can individually trigger the alert.
The Group column allows grouping rows into ALL/AND conditions. In the example above, the
alert is triggered either by (Vehicle Speed being greater than or equal to 120km/hr for 5 seconds)
or both (Engine RPM and Engine Coolant Temperature) reaching their conditions.
The Parameter column is populated by the DawnEdit database parameters that are Enabled.
Choose the appropriate Operator for your condition (<, , =, , >).
7-8

Define an appropriate numerical Limit or threshold for the condition.

The Severity is optional. It is used in the alert description for reference.
The Delay is optional. The condition must occur for this number of seconds in order for the alert
to trigger.
Send Alerts
Use Send Alerts with the Automatically Convert Files setting to receive alerts when a condition is
met. Enter the recipient email addresses separated by commas. The email will come from the
email address alerts@hemdata.com with the name DawnEdit Alert.
To send text messages, phone numbers can be texted through email using a service providers
services. Simply take the 10 digit phone number and add the correct domain name. For example,
2485595607@vtext.com. Below is a list of domain names for common providers.
Verizon:
AT&T:
Sprint:
T-Mobile:
Virgin Mobile:
Cingular:
Nextel:

@vtext.com
@txt.att.net
@messaging.sprintpcs.com
@tmomail.net
@vmobl.com
@cingularme.com
@messaging.nextel.com

9. Helpful Hints
The following are helpful hints:

Before inserting the microSD card, you may find it helpful to blow on the card and reader
so the reader will work better.

When you change config.txt or prefs.txt, make sure that you repower the logger since it
only reads this file on start-up.

8-2