npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

obd-ii-decoder

v0.0.3

Published

A node module that decodes responses from OBD-II vehicle queries.

Downloads

12

Readme

OBD-II Decoder

A node module that decodes responses from OBD-II vehicle queries.

NPM

NodeJS based Decoder for OBD-II (Car Diagnostics) PID's. OBD-II PIDs (On-board diagnostics Parameter IDs) are codes used to request data from a vehicle, used as a diagnostic tool.

SAE standard J/1939 defines many PIDs, but manufacturers also define many more PIDs specific to their vehicles. All light duty vehicles sold in North America since 1996, as well as medium duty vehicles beginning in 2005, and heavy duty vehicles beginning in 2010, are required to support OBD-II diagnostics, using a standardized data link connector, and a subset of the SAE J/1979 defined PIDs (or SAE J/1939 as applicable for medium/heavy duty vehicles), primarily for state mandated emissions inspections.

There are 2 modes of operation described in the latest OBD-II standard SAE J1979 that will be supported by this module.

Mode Description

  • 01 Show current data
  • 03 Show stored Diagnostic Trouble Codes

Decoding a Single Vehicle Response

The following methods can be used to decode a single response from the vehicle, where the inut parameter data is the data part of the response from the vehicle. Eg.The response 41 0C 23 or 410C23 is in the format MODE-PID-DATA. Passing in the data section for a given PID will decode it sucessfully.

  • decodeCalculatedEngineLoad(data)
  • decodeTemperature(data)
  • decodeShortTermFuelTrim(data)
  • decodeFuelPressure(data)
  • decodeIntakeManifoldAbsolutePressure(data)
  • decodeEngineRPM(data)
  • decodeVehicleSpeed(data)
  • decodeTimingAdvance(data)
  • decodeMafAirFlowRate(data)
  • decodeThrottlePosition(data)
  • decodeOxygenSensorVoltage(data)
  • decodeOxygenSensorShortTermFuelTrim(data)
  • decodeRunTimeSinceEngineStart(data)
  • decodeDistanceTravelledMilOn(data)
  • decodeFuelRailPressure(data)
  • decodeFuelRailGaugePressure(data)
  • warmupsSinceCodesCleared(data)
  • decodeDistanceTraveledSinceCodesCleared(data)

Example Usage