Modified on 2018/06/12 10:04 by Jeff Palmer — Categorized as: Uncategorized

For general information about setting up IDP service, please refer to the IsatData Pro (IDP) page.

Message Sizes


Standard AVL positions are 15-18 bytes, depending on whether any optional fields are included.

FieldSize (bits)Optional
Maximum size144 = 18 bytes
Minimum size113 = 15 bytes

SkyWave IDP-680/690

IDP-680 Hardware Guide

SkyWave IDP-780

GPRS Setup

Connect to the terminal via serial and issue the following command

Garmin Setup


By default, it is expected that the Garmin FMI cable will be connected to the main RS-232 port. However, if it is connected to the auxiliary RS-232 port then SIN 125 (GarminFMI) PIN 2 (DebugLevel) must be set to "4".


The "Submit Form As File" property must be set to true for form submissions to work. This property can be accessed on the Garmin Parameters tab under the Send Command item.

Please ensure your terminal has the latest firmware and package files as well. Forms will not work with the 3.x package series.


Refer to the Fuel Management page for information on integrated fuel sensors. For weight sensor, see Vulcan Scale.


RTD Agent

Serializes bytes received on the serial port or from a Lua User service and transports them, in order, over the IDP network (and vice versa for RTD data received over the air)

AVL Agent

Provides various automatic vehicle location and fleet management features related to tracking, vehicle utilization, driver behavior and vehicular sensor monitoring.

Garmin FMI API Agent

Provides a Lua application programing interface to communicate between an IDP terminal and third party devices supporting the Garmin FMI protocol

Garmin Dispatch Agent

Provides a human machine interface via supported Garmin devices for application including text messaging, driver ID and status, and navigation. Garmin Dispatch Agent requires the use of Garmin FMI API agent

ARC Agent

Provides alerts, reports, and control of simple sensor and actuators using the IDP terminal's general purpose I/O's for applications such as compressor monitoring, portable generator tracking, tank level monitoring, and flow metering

J1939 Agent

Extracts J1939 Bus data from fixed and mobile assets and provides it to the user application or SkyWave's Analytics Agent for processing

Analytics Agent

Transforms raw data into valuable information used for monitoring driver and asset performance

SkyWave DMR 800

Configuring your SkyWave DMR800

  1. If you haven't already, contact SkyWave to activate the terminal. The default Control Station ID should be set to 57985327. Please keep a copy of the Terminal ID as you will use this ID to register your device with the tracking platform.
  2. Download the DMR800 Configuration Script and DMR800 Message Definitions files attached to this document.
  3. Connect the DMR800 to your computer and power and open the Scope program provided with the IsatM2M Developer's Toolkit.
  4. Choose File->Connect to connect to the device.
  5. After the program has connected to the device, choose the File->Load Files... menu.
  6. Under Script Designer File:, load the DMR800 Configuration Script. Under the Message Designer File:, load the DMR800 Message Definitions file. Click OK.
  7. Add the device to the tracking portal using the Terminal ID you received above and selecting SkyWave M2M as the device type.

Default Configuration Behavior

The devices are set to report its position on five different events:

  1. Power On - When the device is first powered on or reset and acquires a GPS lock, it will report its Powered On position. It will also assume it is currently stationary and enter the Stationary Reporting mode.
  2. Stationary Reporting - When the device is stationary, it is set to report its position every four hours.
  3. Moving Reporting - When the device is moving, it is set to report its position every two hours.
  4. Start Movement - If the device moves more than 100 meters from its stationary position, it will issue a Start position report and enter the Moving Reporting mode.
  5. Stopped Movement - If the device does not move more than 5 kph over a one hour period, it will issue a Stop position report and enter the Stationary Reporting mode.

Changing Reporting Behavior

There are a few changes you can make to the reporting configuration once you have added the DMR800 to the tracking portal. These configuration parameters can be found by clicking on the asset's context menu item and choosing "Send Command":

  1. Movement reporting interval - Change the number of minutes between reports while the device is moving. The default is 120 minutes (2 hours).
  2. Stationary reporting interval - Change the number of minutes between reports while the device is stationary. The default is 240 minutes (4 hours).
  3. Stop duration - The number of minutes the device must remain under the stop speed threshold before it is no longer considered moving. The default is 60 minutes (1 hour).
  4. Stop speed threshold - The speed under which the device is no longer considered moving. This is not set to zero because there can be GPS jitter. The default is 5 kph.


DMR800 Configuration Script 4 hrs not moving 2 hrs moving.dsd

DMR800 Configuration Script.dsd

DMR800 Message Definitions.dmd



CANbus Testing

CAN bus testing