-
-
Notifications
You must be signed in to change notification settings - Fork 568
TPMS Cars
Tire Pressure Monitoring System (TPMS) operate in the ISM Licence free bands. In USA and most of the world they use 315MHz, in Europe the frequency is 433.92MHz. The TPMS App work well with many common standards used in the automotive industry particularly from Schrader TPMS sensors., and this seems a common standard used in the automotive industry.
The TPMS App display is configured to display the decoded data received from the tire pressure sensors. The interval of the data being sent by each tire varies from every few seconds to minutes depending on the car and sensors, often triggered by wheel movement or rapid pressure changes. Most Schrader sensors can also be triggered to transmit data using a TPMS test tool (which transmits a signal on 125 kHz).
The Key Items on the App that can be selected with the cursor and changed with the encoder knob are: Title bar: The usual Items may be changed and displayed.
- Frequency: Either 315MHz or 433.92MHz
- kPa/PSI : By highlighting this item the units of pressure displayed can be changed between kPA and PSI.
- C/F : By highlighting this item the units of temperature displayed can be changed between Celsius and Fahrenheit.
- Gain: Setting are shown in order of Amp 0=0db or 1=14dB, LNA(IF) (0-40) and VGA (Baseband Gain) (0-62).
-
Tp: This is the type of the tire sensor decoded the following are coded in the App. Some types of TPMS sensors are not supported.
- 0 = None
- 1= FLM_64
- 2= FLM_72
- 3= FLM_80
- 4= Schrader
- 5= GMC_96
- ID: The ID of the tire sensor being 8 hexadecimal characters. Note that sometimes the label printed on the actual temperature sensor is in decimal format.
- Pres: This is the pressure in either kilo Pascals (kPa) or Pounds Per Square Inch (PSI).
- Temp: The temperature of the tire in either degrees Celsius (C) or Fahrenheit (F). Note Spurious data has been seen and may be due to receive errors, unsupported protocols, or failed sensors. Pressure and temperature ranges may vary depending on sensor model, so best to compare to dash readings, if available.
- Cnt: This is the count of messages received from each sensor.
- Flags: Information on the type of sensor is only for Schrader and have decode for: fsk_19k, ook_8k192, ook_8k4.
If a FAT-formatted micro SD card is present when this mode is entered, the receiver will log received packets to a file named "TPMS.TXT". The log file contains one line per packet received. Each line consists of a timestamp in sortable "YYYYMMDDHHMMSS" format, receiver frequency, modulation, deviation, symbol rate, and data. The data field consists of Manchester-decoded data bits, a "/", and a per-bit Manchester coding error indicator ("1" if the data bit is in error).
Note
The wiki is incomplete. Please add content and collaborate.
Important
- This is a public wiki. Everything is visible to everyone. Don't use it for personal notes.
- Avoid linking to external tutorials/articles; they may become outdated or contain false information.
How to collaborate
How to ask questions correctly
- First steps
- Usage cautions
- Intended use and Legality
- Features
- PortaPack Versions (which one to buy)
- HackRF Versions
- Firmware update procedure
- Description of the hardware
- User interface
- Powering the PortaPack
- Troubleshooting
- Applications
-
Compilation of the firmware
- Compile on WSL with ninja
- How to compile on Windows faster with WSL 2
- Using Docker and Kitematic
- Docker command-line reference
- Using Buddyworks and other CI platforms
- Notes for Buddy.Works (and other CI platforms)
- Using ARM on Debian host
- All in one script for ARM on Debian host
- Compile on Arch based distro (exclude Asahi)
- Dev build versions
- Notes About ccache
- Create a custom map
- Code formatting
- PR process
- Description of the Structure
- Software Dev Guides
- Tools
- Research
- UI Screenshots
- Maintaining
- Creating a prod/stable release (Maintainers only)
- Maintaining rules
- Development States Notes