Innovate Motorsports DL-32 - Manual (Page 4)

- 4 -
1. Overview
The DL-32 is a data logger with 5 general purpose inputs. It can record these inputs on a SD
memory card. In addition to its own native 5 inputs the DL-32 can record data from other Innovate
MTS (Modular Tuning System) devices up to a total of 32 recorded channels. A 32-channel
recording requires a memory space of 1Mbyte in the SD card every 17 minutes. A 16Mbyte card
therefore can record 272 minutes or about 4-1/2 hours. If less channels are recorded, the
recording time is proportionally larger. So for 16 channels on a 16Mbyte card the recording
capacity would be 9 hrs.
Each recording is organized in logs and sessions. The DL-32 contains a real-time clock that
allows it to time-stamp each log and session it recorded.
Most of the functionality of the DL-32 regarding its internal channels is identical to the LMA-3
product from Innovate Motorsports.
This manual is primarily organized into 3 parts:
1. Description of the capability and setup of the internal channels
2. Programming the DL-32 with a computer
3. Recording data to the SD-card
2. The Innovate Log-Chain concept
LogWorks 2.0 has the capability to log, display and analyze up to 32 engine parameters. Most
users will use less though. Each of the MTS components reads between 1 and 6 engine
parameters. To interface a multitude of MTS components to LogWorks with a single connection,
the Innovate LogChain concept was introduced.
The DL-32 can be used as a MTS component in a Log-Chain. Each of the MTS components has
two serial ports (except the LM-1, which has only one). One serial port is designated as IN-port,
the other as OUT port. The OUT-port of one device is connected to the IN-port of the next device
and so on. This way devices can be ‘daisy-chained’ to build a log-chain for up to 32 channels
total. The OUT-port of the last device is connected to the computer for logging or downloading of
logged data.
The device that’s first in the chain is special. It determines the logging sample rate. The first
device in the chain sends a data packet containing its channel data (a sample) to the next device
(downstream, left to right in the diagram) every 81.92 milliseconds. The next device appends its
data to that packet and hands that packet to the next device downstream and so on. At each
device the packet grows in length. The devices in the chain synchronize their sampling of the
engine parameters to the packets, so that all the channels in a packet together represent the
same instance in time. At the downstream end of the log chain (OUT-port of the last device) a
computer or external logger can be connected to store or display the stream data. The XD-16 (or
XD-1) display is such a device.
This also means that the complete channel data set is ONLY available at the end of the
log-chain. A datalogger capable of recording the log-chain data-stream therefore MUST be
placed at the end of the log-chain. This includes lap-top computers or other loggers.
Commands for individual devices are sent ‘upstream’. A device (incl. a computer or an XD-16)
can send commands to the devices upstream of itself, but not downstream. Commands can
include start-stop recording, calibration/configuration commands and so on. Only the device
directly upstream of the command originator of course will receive the command. This device
then decides, depending on the command, whether to execute the command and whether to