Telemetry Not Feeding Goals

Overview

Goals rely on telemetry data to evaluate asset performance. If telemetry devices aren't communicating, are misconfigured, or are reporting incomplete data, goals can't function correctly. This guide covers the entire telemetry troubleshooting process, from basic connectivity to advanced CAN bus diagnostics.

Understanding the Telemetry-to-Goal Data Flow

Here's how telemetry data reaches your goals:

Problems at any step prevent goals from working correctly. This guide addresses each step.

Quick Diagnostic Steps

Start here to quickly identify which step is failing:

Step 1: Is Device Communicating?

1. Open asset detail page
2. Check "Last Telemetry Update" timestamp
3. If <5 minutes ago: Device is online → Proceed to Step 2
4. If >1 hour ago: Device offline → See Connectivity Issues

Step 2: Is Basic Data Present?

1. Check if location (GPS coordinates) is current
2. Check if connectivity status is "Online"
3. If yes: Device transmitting → Proceed to Step 3
4. If no: Transmission problem → See Transmission Delays

Step 3: Is Operational Data Present?

1. Check if runtime, distance, or other goal-monitored fields show values
2. If yes: Full telemetry working → Issue is goal configuration (see Goals Not Triggering Alerts)
3. If no: CAN bus or data collection issue → See CAN Bus Problems

Connectivity Issues

Device Completely Offline (No Communication)

Diagnostic checklist:

Check	How to Verify	Solution
Power	Check asset battery voltage; device LED indicators	Verify power wiring, check fuses, ensure battery charged
Cellular Signal	Check if asset is in remote area with no coverage	Move asset to area with signal, or install external antenna
Subscription	Verify data plan is active (contact billing/admin)	Renew subscription or activate SIM card
Device Fault	LED indicators show error pattern	Contact Support for RMA/replacement

Power Issues

Common power problems:

• Battery disconnected: Device has no power when asset is off. Check battery terminals and wiring.
• Blown fuse: Inspect fuse panel for blown fuses in telemetry circuit.
• Voltage too low: Weak or dying battery can't power device. Test battery voltage: should be >12V for 12V systems, >24V for 24V systems.
• Installation error: Device wired to ignition-switched power instead of constant power; only works when asset is running.

Solution steps:

1. Verify device power LED is illuminated (refer to device manual for LED indicators)
2. Use multimeter to test voltage at device power connector: should match asset battery voltage
3. Check ground connection is secure and making good contact with chassis
4. If device is powered but still offline, proceed to cellular checks

Cellular Signal Issues

Signal strength indicators:

Bars	RSSI (dBm)	Status	Impact
5/5	-50 to -75	Excellent	Real-time data transmission
3-4/5	-75 to -90	Good	May have occasional delays
1-2/5	-90 to -105	Weak	Batched transmissions, delays
0/5	<-105	No signal	No transmission possible

Solutions for weak signal:

• Relocate internal antenna: Move antenna away from metal obstructions; place higher on equipment
• Install external antenna: Upgrade to magnetic mount or permanent mount external antenna
• Check carrier coverage: Verify carrier (AT&T, Verizon, etc.) has coverage in operating area
• Switch carriers: Some carriers have better coverage in rural areas - contact Support about carrier options

Subscription and SIM Card Issues

Common problems:

• Data plan expired or suspended due to non-payment
• SIM card not activated when device was installed
• SIM card damaged or improperly seated

How to verify:

1. Contact ARMOR Support or your account manager
2. Provide asset name/ID and device serial number
3. Request subscription status check

If SIM issue suspected:

1. Power off equipment completely
2. Remove telemetry device (or access SIM card slot)
3. Remove and reseat SIM card (ensure proper orientation)
4. Reinstall device and power on
5. Wait 5-10 minutes for device to register on network

Data Transmission Delays

Understanding Batched Transmissions

When signal is weak, devices use an adaptive strategy:

• Strong signal: Transmit every 1-5 minutes (near real-time)
• Weak signal: Queue data, transmit every 30-60 minutes
• No signal: Store up to 24-48 hours of data, transmit when signal returns

Impact on Goals

Delays affect different goal types differently:

Goal Frequency	Check Time	Impact of Delays
Daily	2:00 AM	High risk: If data arrives after 2 AM, appears as 0 for previous day
Weekly	End of week	Medium risk: Usually data arrives before week ends
Monthly	End of month	Low risk: Data catches up before month ends

Solutions

• Improve signal: Relocate antenna or upgrade to external antenna (see above)
• Adjust goal frequency: For assets in poor signal areas, use weekly instead of daily goals
• Accept delays: Data will backfill; alerts may be delayed but will arrive
• Monitor trends: Use weekly/monthly reporting instead of real-time goals

CAN Bus Integration Problems

What is CAN Bus?

Controller Area Network (CAN bus) is the communication protocol that equipment uses to share data between electronic control units (ECUs). ARMOR telemetry devices tap into this bus to read:

• Engine hours / runtime
• Distance / odometer
• Speed
• Fuel level
• Engine RPM, temperature, pressure
• Production metrics (loads, cycles, etc.)

CAN Bus Diagnostic Steps

1. Verify Physical Connection

CAN harness connects device to equipment:

• OBD-II port (light-duty vehicles): Usually under dashboard, near steering column
• J1939 connector (heavy equipment): 9-pin or 6-pin Deutsch connector, often near ECU
• Direct wiring (custom installations): CAN-H and CAN-L wires spliced into CAN bus

Check:

1. Harness is firmly connected (no loose connectors)
2. Pins are not bent or damaged
3. No corrosion in connector
4. CAN wires (if direct wired) are properly twisted pair

2. Confirm ECU Compatibility

Not all equipment has compatible ECUs:

Equipment Age	CAN Support	Alternatives
2008+	✅ Usually has J1939/OBD-II	N/A
2000-2007	⚠️ May have proprietary protocols	Check manufacturer specs, may need adapter
Pre-2000	❌ Usually no CAN bus	Use GPS-only mode, external sensors, or equipment upgrade

How to check compatibility:

1. Identify equipment make, model, and year
2. Contact ARMOR Support with equipment details
3. Support will confirm if equipment ECU is supported
4. If not supported, discuss alternative data collection methods

3. Check Device CAN Configuration

Device needs correct CAN settings:

• Baud rate: 250k (most common), 500k (some manufacturers)
• Protocol: J1939, OBD-II, CANopen, manufacturer-specific
• Data mappings: Which CAN PIDs map to which telemetry fields

Configuration is usually automatic when you provide equipment make/model during setup. If CAN isn't working, device may have wrong configuration.

Solution: Contact ARMOR Support to verify/update device CAN configuration.

4. Test with Known-Good Equipment

To isolate device vs. equipment issue:

1. Move telemetry device to a different asset (known to have working CAN)
2. If CAN data appears on new asset: Original equipment ECU has compatibility issue
3. If CAN data still missing: Telemetry device may need replacement

CAN Troubleshooting Examples

Example 1: Forklift Shows Location but No Runtime

Example 2: Excavator Shows Intermittent Data

Data Field Mapping Issues

Example Scenarios

• Goal monitors distanceToday, but asset reports odometerValue (lifetime total, not daily)
• Goal expects runTimeToday, but device reports engineHoursTotal
• Custom production fields (e.g., loadCount) aren't mapped in asset configuration

Solution

1. Contact ARMOR Support with:
• Asset name/ID
• Data field goal is trying to monitor
• Screenshot showing available fields on asset detail page
2. Support will update asset telemetry configuration to map fields correctly
3. After update, wait for next telemetry transmission (5-60 minutes) to see corrected data

Real-Time vs. Aggregated Data

ARMOR processes telemetry data in two ways:

Real-Time Data

• What: Current sensor readings (speed, battery level, temperature)
• Update frequency: Every 1-5 minutes (depending on signal)
• Use case: Live monitoring, immediate alerts

Aggregated Data

• What: Calculated summaries (runtimeToday, distanceWeek)
• Update frequency: Once per hour, finalized at midnight
• Use case: Goals, reporting, trends

Why This Matters for Goals

Goals typically use aggregated data (Today, Week, Month fields):

• This data is calculated from raw telemetry over time
• If raw telemetry is missing/delayed, aggregated values won't update
• Daily goals check at 2 AM, using aggregated data finalized at midnight

Preventive Maintenance for Telemetry

Reduce telemetry issues with regular checks:

Monthly Checks

• Review "Last Telemetry Update" for all assets - flag any >24 hours old
• Verify CAN connectors are secure (vibration can loosen them)
• Clean corrosion from connectors (especially in humid environments)

Quarterly Checks

• Test device power voltage - should match asset battery
• Inspect antenna mounting - ensure secure and no damage
• Review cellular signal strength - consider antenna upgrades if consistently weak

Annual Checks

• Firmware updates - contact Support to ensure devices have latest firmware
• Subscription renewal - verify data plans are active
• Hardware inspection - look for physical damage, water intrusion, worn wiring

Creating a Telemetry Health Goal

Monitor telemetry health automatically with a goal:

This proactively catches offline devices before they impact operational goals.

When to Contact Support

Contact ARMOR Support if:

• Device is powered and has signal, but no data is transmitting
• CAN connection is secure but no engine data
• Data was working and suddenly stopped
• Multiple assets have same telemetry issue (suggests systemic problem)
• Goal evaluations show "No Data" but you can see data on asset pages

Information to provide:

• Asset name/ID
• Telemetry device serial number
• Equipment make, model, and year
• Screenshot of asset detail page showing "Last Telemetry Update" and data fields
• Description of installation (OBD port, J1939, direct wire, etc.)
• When telemetry last worked (if known)

Advanced Diagnostics (For Support)

ARMOR Support has access to advanced diagnostics:

• Device logs: View raw transmission logs to see what device is sending
• CAN PID monitoring: Capture raw CAN messages to diagnose protocol issues
• Signal strength history: Review cellular signal trends over time
• Data processing logs: See if data is arriving but failing validation/processing

Related Topics

• Missing Goal Data - When data fields show 0 or "No Data"
• Goals Not Triggering Alerts - Full goal troubleshooting
• How to Improve Goal Accuracy With Telemetry - Data quality best practices

Getting Help

For persistent telemetry issues, contact the ARMOR Support Team with asset details, device serial numbers, and screenshots of the issue.