Telemetry Tab

This topic covers all topics related to the installation, configuration and usage of Telemetry and is intended to be used by the following audiences:

• Hardware and Vehicle Installers should read the following sections:
  • Telemetry Verification Kit: describes the kit used to verify which vehicle parameters can be read by Telemetry for a particular vehicle.
  • Telemetry Hardware: describes the hardware and installation process.
• System Administrators should read: Configuring Telemetry for an MP70, Configuring Telemetry on an MG Gateway for Light-duty Vehicles, Configuring HD Telemetry on an MG Gateway for Heavy-duty Vehicles which describe how to configure telemetry on gateways and the AMM, and how to set up user accounts and thresholds so that telemetry information is available to fleet operators.
• Fleet Operators should read Operation, which describes how to view telemetry information.

It is assumed that the reader has access to the appropriate account and password on the gateway and AMM to configure telemetry.

Telemetry is designed for fleet managers, service managers and technicians, human resource managers, and other personnel who manage fleets, fleet personnel and associated data.

Telemetry is applicable to vehicles equipped with Onboard Diagnostics Version 2 (OBD-II) data bus connections, which are typically light truck and passenger vehicles.

Telemetry information may be limited to specific makes and models of vehicles. For more information contact your vehicle’s manufacturer or Sierra Wireless sales representative.

• OBD-II diagnostic cable: connects to the vehicle OBD-II socket and one side of the OBD-II scan tool.

• Scanner.
• Scanner-to-serial port cable: cable for connecting between the serial port on the scanner and the serial port on the laptop.
• USB-to-serial converter cable: optional cable for USB connectivity between the scanner and a USB port on the laptop.
• USB stick: contains the self-booting software utility to be run on a laptop which is used for verifying compatibility.

• Heavy-duty diagnostic cable: connects to the vehicle’s Deutsch socket and one side of the scan tool.

• AutoTap Scanner.
• Scanner-to-serial port cable: cable for connecting between the serial port on the scanner and the serial port on the laptop.
• USB-to-serial converter cable: optional cable for USB connectivity between the scanner and a USB port on the laptop.
• USB stick: contains the self-booting software utility to be run on a laptop which is used for verifying compatibility.

Connect the scanner to the laptop as follows:

1. Plug the male end of the scanner-to-serial port cable into the scanner. Do not plug the other end into the laptop at this point.
2. (Optional) For USB connectivity, plug the serial end of the USB-to-serial converter cable into the scanner-to-serial port cable. This will enable a laptop to communicate using USB instead of serial.
3. Connect the vehicle to the scanner:
   • Light-duty vehicles: Plug the serial end of the OBD-to-serial cable into the other end of the scanner. Do not plug in the OBD end of the cable into the vehicle at this point.
   • Heavy-duty vehicles: Plug the serial end of the Deutsch-to-serial cable into the other end of the AutoTap scanner. Do not plug in the Deutsch end of the cable into the vehicle at this point.

Note: This topic assumes that the you have a laptop on which you can access the BIOS.

1. Input the vehicle information and click Next:
   
2. Connect the OBD end of your serial-to-OBD cable to the vehicle and click Next on the Scantool page:
   
3. Start the vehicle when prompted and click Next:
   
4. Connect the serial or USB end of the cable from the scanner to the computer on the Scantool page and click Next.
   
   
5. Select the USB port where the scanner is connected to and click Next. Alternatively, if using a serial cable, select Customize device path and enter the gateway’s path (e.g. /dev/ttyS0):
   
6. The compatibility check process will run:
   
   The final report is saved in /Desktop on the USB stick in HTML format. Each time the utility is run, a new entry is added to the files, allowing for information from an entire fleet to be saved and reloaded.
7. To view the report click Full Report, or click on Finish to exit:
   

The report is displayed:

Note: if a vehicle parameter is shown as “Not Found” in the report, this means that the vehicle does not support it and it will not be available to the AMM.

1. Input the vehicle information and click Next:
   
2. Connect the OBD end of your serial-to-OBD cable to the vehicle and click Next on the Scantool page:
   
3. Start the vehicle when prompted and click Next:
   
4. Connect the serial or USB end of the cable from the scanner to the computer on the Scantool page and click Next.
   
5. Select the USB port where the scanner is connected to and click Next. Alternatively, if using a serial cable, select Customize device path and enter the gateway’s path (e.g. /dev/ttyS0):
   
6. The compatibility check process will run:
   
   
   The final report is saved in /Desktop on the USB stick in HTML format. Each time the utility is run, a new entry is added to the files, allowing for information from an entire fleet to be saved and reloaded.
7. To view the report click on Full Report, or click Finish to exit:
   

The report is displayed:

*Note: if a PID is shown as “Not Found” in the report, it means the vehicle does not support the PID and therefore it will not be available to the AMM.

The following Sierra Wireless hardware components are required to enable and use telemetry on a gateway:

1. An MP70 with a minimum software release of 4.12.0 or, an MG gateway with a minimum software release of 2.8.5 or greater is recommended.
2. Scan tool kit (supplied by Sierra Wireless) which includes:
   • Light-duty Vehicle: 15’ OBD cable that connects the scan tool to the vehicle OBD port.
   • Heavy-duty Vehicle: 25’ OBD cable that connects scan tool to vehicle HDOBD port (there are two formats for this connector: 6-pin and 9-pin. Check with your vehicle manufacturer prior to ordering from Sierra Wireless).
   • Telemetry scan tool.
   • Custom 10’ RS232 cable (containing female DB9 connectors on both ends) that connects the scan tool to the gateway.

This section assumes that the gateway is properly installed and configured with a network service card. Refer to the appropriate hardware guide for the gateway for more information on configuration. Hardware guides and other resources for currently supported gateways can be found using the following links:

• MP70
• MP90
• oMG2000
• oMG500

The installer is expected to be familiar with the location of the OBD-II or Deutsch connector in the vehicle.

1 Power on the gateway, and verify it can connect to a WAN service (a steady green light should show)

2 Verify that the gateway meets the software requirements for telemetry. In the event that the gateway requires a new version, please contact Support to schedule an over-the-air software upgrade

Note: you must have a valid support plan in place in order to receive this upgrade.

3 Locate the OBD-II or Deutsch port in the vehicle. The port is an electrical socket most commonly located under the vehicle dashboard on the driver’s side near the center console

4 Install the Sierra Wireless-supplied scan tool:

• Light-duty vehicles: Attach the male SAE J1962 16-pin connector of the scan tool to the vehicle’s OBD-II port on the light-duty vehicle. SAE J1962 is the technical name for OBD-II connectors.
• Heavy-duty vehicles: Attach the Deutsch connector to the vehicle’s Deutsch port and the other end of the cable to the scanner.

5 Depending on the particular vehicle, you may wish to tie-wrap the cable in place to ensure the cable and scan tool do not disconnect as a result of vibration during subsequent operations.

6 Attach the Sierra Wireless-provided custom serial cable connecting the male serial connector of the scan tool, and the serial connector of the gateway.

Follow the steps below to configure Telemetry for an MP70:

1. Configure data streaming for the gateway as described here .
2. Install AVTC on the gateway to allow for transmission of proprietary data as described in the AirLink Vehicle Telemetry Configuration Application.
3. The scanner can be connected directly to the serial port or into a USB port (requires a USB-to-Serial adaptor).

Use the following steps to enable Telemetry on an MG gateway:

1 Connect to the MG gateway’s LAN. In a web browser, go to http://welcome.to.inmotion/MG-LCI and log in as administrator.

2 Navigate to Devices > Serial, use the drop down menu to select Application from the default SerialConsole. This will allow the rear panel serial port to be used for communication with the scan tool.

3 Navigate to Applications > Telemetry.

Note: if the Telemetry Configuration tab is not available, then the Telemetry Application has not been installed on the gateway. If this is the case, call Support to request a software upgrade.

4 Under Master Options, check Enable and click on Submit. This configures the OBD-II agent service to run automatically whenever the gateway reboots.

5 Navigate to Telemetry > Telemetry Status to set the Odometer value.

a Under Odometer Reference Update, enter the current odometer value in the Current Odometer field. Note that the vehicle’s engine must be turned ON for this step. If required, this step can be completed at a later time.

b Select km or mi for the Current Odometer field’s units.

c Click Submit.

Note: when the vehicle is serviced, the Current Odometer value may need to be reconfigured.

6 The scanner can be connected directly to the serial port or into a USB port (requires a USB-to-Serial adaptor). If the default serial connector is not used, select the appropriate gateway from the list under OBDII Adapter Attachment.

The default PIDs should not be changed unless authorized by Sierra Wireless, as they represent the underlying Telemetry data reported to the AMM. For more information about changing these values, contact Support.

Use the following steps to enable telemetry on an MG gateway:

1 Connect to the gateway’s LAN. In a web browser, go to http://welcome.to.inmotion/MG-LCI and log in as administrator.

2 Navigate to Devices > Serial, use the drop down menu to select Application from the default SerialConsole. This will allow the rear panel serial port to be used for communication with the scan tool.

3 Navigate to Applications > HD Telemetry.

Note: if the Telemetry tab is not available, then the Telemetry Application has not been installed on the gateway. If this is the case, call Support to request a software upgrade.

4 Under Master Options, check Enable to activate the HD Telemetry application.

5 In most cases, setting the Scanner Type to AutoTap will work. However if your vehicle supports both J1708 and J1939 and you want to ensure that a specific protocol is used, select if from the list.

6 The scanner can be connected directly to the serial port or into a USB port (requires a USB-to-Serial adaptor). If the default serial connector is not used, select the appropriate gateway from the list under Adapter Attachment. The default PIDs should not be changed unless authorized by Sierra Wireless, as they represent the underlying Telemetry data reported to the AMM. For more information about changing these values, contact Support. Note that some vehicles may use the term SPN (Suspect Parameter Number) in place of PID.

7 Click Submit to save the configuration changes.

Telemetry thresholds corresponding to telemetry stats, are used for displaying alerts both on the Dashboard and Telemetry dashboard tabs.

Thresholds are usually created by Sierra Wireless during the provisioning stage of the AMM, but may need to be created by an AMM’s administrator. For more information about creating and configuring thresholds, see Thresholds .

Note: the availability of Telemetry Stats is based on whether those Stats have been reported by the gateway(s) associated with the AMM.
Note: when operating on a hosted AMM, the available Stat types may include those not reported by your current fleet. This occurs because the hosted AMM software lists all Stats types available including those reported by other fleets.

For a complete list of items which can be reported as Stats, see Telemetry Parameters and Summary of HD Telemetry PID/SPNS.

AirLink Vehicle Telemetry Configuration (AVTC) is an AAF application that allows convenient distribution of proprietary vehicle configuration information to supported AirLink gateways.

AVTC consists only of vehicle-specific data. There is nothing to configure on the app itself. When installed on a supported AirLink gateway running ALEOS 4.12.0 or later, it enables the gateway to collect proprietary vehicle data parameters. AVTC enables reporting of proprietary vehicle information to the AMM (with AMMER installed).

Note: The AVTC app only applies to ALEOS gateways that are directly connected to the vehicle bus (e.g., MP70).

For information on setting up AVTC via the AMM, see the AirLink Vehicle Telemetry Configuration Application.

Ensure that the HD Telemetry scanner is properly connected. If the scanner is not connected, the AMM should report that the scanner is disconnected.

If the scanner is not physically connected to the HDODB port or if the HDODB port on the vehicle is defective, the Telemetry panel will show 0 (zero) or N/A.

When the scanner is not connected or the engine is OFF, navigate to the Telemetry Status tab (for light-duty vehicles) or the Heavy Duty Telemetry status tab (for heavy-duty vehicles) in the LCI, to verify the state of the scanner. If the scanner is operating normally, the State field should indicate ACTIVE_SCAN as shown below. If the scanner is disconnected it should display INIT. If the scanner is connected but the engine is off it should display INVALID_ECU_CONNECTION. A disconnected message indicates that the scanner is not physically connected to the Deutsch port or the Deutsch port on the vehicle may be defective.

When the odometer is set manually via the LCI, the odometer will increment based on the Distance since codes cleared PID. If the Distance since codes cleared PID is reset during maintenance of the vehicle or if the battery is removed, the odometer value may need to be re-entered via the LCI.

Some vehicles may not support all PIDs or may use a proprietary method that is not supported by Sierra Wireless. In such a case, the AMM Dashboard or Telemetry dashboard may not display this PID or may show N/A rather than a value. To check which ID’s are being reported by a vehicle, use the verification kit.

The following list describes the ODB-II light-vehicle vehicle parameters which can be reported as Telemetry Stats to the AMM. A full list of ODB-II PIDs is available at: http:// en.wikipedia.org/wiki/OBD-II_PIDs.

Note that some parameters may not be available on some vehicles. Also, the parameters are measured in metric units on the gateway, but can be reported in either metric or imperial units on the AMM depending on the measurement units selected in the AMM’s user preferences. If imperial is selected as the display unit on the AMM, then the AMM will automatically convert the values from metric.

The following list describes the heavy-duty vehicle parameters which can be reported as Telemetry Stats to the AMM.