-
Notifications
You must be signed in to change notification settings - Fork 0
/
blueprint.yaml
39 lines (36 loc) · 1.57 KB
/
blueprint.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
slug: particle-blueprint-tracker-can
type: Tutorial
category: "Tracker projects"
expertiseLevel: "Intermediate"
tags: ["Tracker", "Automotive", "Industrial", "Communication"]
icon: assets/tracker-can-bus-integration.svg
gitrepo: https://github.com/particle-iot/blueprint-tracker-can
name: "Tracker CAN bus integration"
shortDescription: "Connecting the Tracker One to a vehicle CAN bus."
version: 1.0.0
models: []
language: ["C++"]
cloudServices:
- name: Integrations
- name: Logic
- name: Ledger
integrations: []
supportedDevices:
- name: Tracker One
link: https://www.particle.io/tracker-one/
- name: T-SoM
link: https://www.particle.io/tracker-som/
hardwareDependencies:
- name: Supported device
- name: M8 cable with OBD-II connector
introduction: |
This application note shows how to use the CAN bus for OBD-II to retrieve engine RPM
description: |
This application demonstrates how to connect the Particle Tracker One to a vehicle’s CAN bus using the OBD-II (J1962) interface to retrieve engine RPM and other data.
Key Features:
- Configure CAN bus parameters and request data such as engine RPM from the vehicle.
- Add vehicle data to location publishes.
- Aggregate frequently changing data and upload metrics (minimum, average, and maximum) alongside location data.
- Dynamically adjust the location publish rate based on conditions (e.g., when the engine is running above idle).
This example uses the Particle CAN library [can-mcp25x](https://github.com/particle-iot/can-mcp25x) and includes a CAN bus simulator for easier testing.
additionalResources: