This *Off The Wall* Question is more meant for our Resident SME on PID Monitoring, Interpretation and Programming via @TJBaker57. It occurred to me that since Post 2002 Trucks & SUVs use the PWM Based IPCs that a Custom PID for Cell Phones and Tablets could be made to intercept the IPC Speedometer DATA Stream (or the VSS on the 4L60E Transmission) and using the proper math formulae...inhale the network streams and produce a Spot-On Read Out that would be accurate enough to report the actual Road Speed based on the collection of the Vehicle Tire Size and "Pumpkin" Differential Gearing to produce a useful Cell Phone or Tablet Speedometer.
TROLL ALERT: I know this is already being done easily with Cell Phone GPS...but THAT is not the issue or the Question here... they can be "Spoofed" or Jammed!
I made an inquiry of my "GPT4ALL* Reasoner-1 GURU about this idea and this was *IT* s Reply (Note... THIS LLM produces a "Chain of Thought" that I am able to capture in Text without "IT" knowing that its *Thoughts* are very transparent here... which helps in checking on its honesty and confirming that it is not merely hallucinating its response):
Prompt: Would it be possible to produce a useful "Speedometer PID" for the Torque Automotive Diagnostic APP used on Cell Phones via a Wireless USB Dongle that plugs into the DLC under-dash ports on vehicles that use the OBD 2 Protocols? The idea is to be able to capture the PWM ( Pulse Width Modulation) signal coming to the IPC (Instrument Panel Cluster) and controlling the Speedometers on General Motors Trucks and SUVs that have Over-sized Tires that will mis-report the actual road speed of the vehicle in combination with the VSS (Vehicle Speed Sensor) using the ubiquitous 4L60E 4 speed automatic transmissions. Can you create or outline the math that would include all of the dimension inputs and parameters needed to calculate these events to include information like the wheel base, the outside tire diameter, the rear differential gear box ratios, etc, that could be included as a New PID for the Torque Program?
Response: Okay, so I'm trying to figure out how to create a Speedometer PID for the Torque app. The goal is to correct the speed reading on GM trucks and SUVs with over-sized tires using a wireless USB dongle that connects via OBD2.
First, I need to understand why there's an issue. Over-sized tires can cause the speedometer to misreport because it relies on wheel rotations. If the tire diameter is larger than standard, each rotation covers more distance, so the ECU thinks you're going slower than you actually are. That’s dangerous because it underestimates your speed.
I know that Torque already uses OBD2 via a dongle, but I want to add a new PID (Parameter ID) specifically for this correction. The user mentioned capturing PWM signals from the IPC and using VSS data. So maybe combining these inputs can help calculate the correct speed.
Let me break down what's needed:
1. **Understanding the Problem**: Over-sized tires make each rotation cover more ground, so the ECU calculates a lower speed than actual because it thinks each revolution is shorter (based on tire size). To fix this, we need to adjust based on actual wheel diameter and other factors.
2. **Inputs Needed**:
- Actual Tire Diameter: This is crucial because larger tires mean fewer rotations for the same distance.
- Differential Gear Ratio: Affects how engine RPM translates to wheel speed.
- Vehicle Speed Sensor (VSS) Output: The current, possibly incorrect speed reading from the ECU.
3. **Mathematical Approach**:
I think we need a formula that adjusts the VSS output based on tire size and gear ratio. Maybe something like:
Corrected Speed = (VSS * Tire Diameter / Standard Tire Diameter) / Gear Ratio
But wait, how does differential gear ratio affect this? The gear ratio affects how many times the wheels turn per engine revolution. So if the gears are lower (numerically higher), each wheel rotation corresponds to fewer engine RPMs.
4. **Data Collection**:
To get these values into Torque, we might need new PIDs for tire diameter and differential ratio. But GM vehicles probably don't have these parameters stored in OBD2; they're usually hard-coded or require manual input. So the user would need to enter their truck's specific data.
5. **Implementation Steps**:
- Modify Torque app to accept a new PID that takes VSS, tire diameter, and gear ratio as inputs.
- Calculate corrected speed using these values.
- Display both original and corrected speeds for comparison.
6. **Potential Challenges**:
- Some vehicles might not expose the necessary data via OBD2, requiring additional hardware or software to capture it.
- Real-time calculations need to be efficient enough not to lag.
- Ensuring accuracy across different models and tire sizes could be tricky.
7. **Testing**:
After implementation, testing with known good setups would help verify if the corrected speed matches actual conditions (like using a GPS for reference).
I'm probably missing some details about how OBD2 works or specific GM protocols, but this seems like a logical starting point. To address the issue of inaccurate speedometer readings in General Motors trucks and SUVs with over-sized tires, we propose creating a new Speedometer PID within the Torque app. This solution involves capturing vehicle data to correct the reported speed based on tire size and drive-train parameters.
### Solution Overview:
1. **Problem Understanding**:
- Over-sized tires cause each rotation to cover more distance than standard tires, leading the ECU to under-report speed as it miscalculates rotations.
2. **Key Inputs Required**:
- Actual Tire Diameter: Essential for adjusting the perceived number of wheel rotations.
- Differential Gear Ratio: Influences how engine RPM translates into wheel speed.
- Vehicle Speed Sensor (VSS) Output: The current, possibly incorrect speed reading from the ECU.
3. **Mathematical Formula**:
Corrected Speed = (VSS * Actual Tire Diameter / Standard Tire Diameter) / Differential Gear Ratio
4. **Implementation Steps**:
- Modify Torque to accept new PIDs for tire diameter and gear ratio.
- Calculate corrected speed using the formula above.
- Display both original VSS speed and corrected speed.
5. **Challenges Considered**:
- Some data may not be available via OBD2, necessitating manual input or additional hardware.
- Ensuring real-time efficiency to avoid lag is crucial.
- Accuracy must be validated across various models and tire sizes through testing.
6. **Testing Protocol**:
Use a GPS reference for accurate speed comparison during testing phases to verify the corrected speed's accuracy
### Conclusion:
By integrating these inputs into Torque, users can achieve more accurate speed readings, enhancing safety by correcting underestimations from over-sized tires. This approach leverages existing data and user input to provide an effective solution within the app's framework.
TROLL ALERT: I know this is already being done easily with Cell Phone GPS...but THAT is not the issue or the Question here... they can be "Spoofed" or Jammed!
I made an inquiry of my "GPT4ALL* Reasoner-1 GURU about this idea and this was *IT* s Reply (Note... THIS LLM produces a "Chain of Thought" that I am able to capture in Text without "IT" knowing that its *Thoughts* are very transparent here... which helps in checking on its honesty and confirming that it is not merely hallucinating its response):
Prompt: Would it be possible to produce a useful "Speedometer PID" for the Torque Automotive Diagnostic APP used on Cell Phones via a Wireless USB Dongle that plugs into the DLC under-dash ports on vehicles that use the OBD 2 Protocols? The idea is to be able to capture the PWM ( Pulse Width Modulation) signal coming to the IPC (Instrument Panel Cluster) and controlling the Speedometers on General Motors Trucks and SUVs that have Over-sized Tires that will mis-report the actual road speed of the vehicle in combination with the VSS (Vehicle Speed Sensor) using the ubiquitous 4L60E 4 speed automatic transmissions. Can you create or outline the math that would include all of the dimension inputs and parameters needed to calculate these events to include information like the wheel base, the outside tire diameter, the rear differential gear box ratios, etc, that could be included as a New PID for the Torque Program?
Response: Okay, so I'm trying to figure out how to create a Speedometer PID for the Torque app. The goal is to correct the speed reading on GM trucks and SUVs with over-sized tires using a wireless USB dongle that connects via OBD2.
First, I need to understand why there's an issue. Over-sized tires can cause the speedometer to misreport because it relies on wheel rotations. If the tire diameter is larger than standard, each rotation covers more distance, so the ECU thinks you're going slower than you actually are. That’s dangerous because it underestimates your speed.
I know that Torque already uses OBD2 via a dongle, but I want to add a new PID (Parameter ID) specifically for this correction. The user mentioned capturing PWM signals from the IPC and using VSS data. So maybe combining these inputs can help calculate the correct speed.
Let me break down what's needed:
1. **Understanding the Problem**: Over-sized tires make each rotation cover more ground, so the ECU calculates a lower speed than actual because it thinks each revolution is shorter (based on tire size). To fix this, we need to adjust based on actual wheel diameter and other factors.
2. **Inputs Needed**:
- Actual Tire Diameter: This is crucial because larger tires mean fewer rotations for the same distance.
- Differential Gear Ratio: Affects how engine RPM translates to wheel speed.
- Vehicle Speed Sensor (VSS) Output: The current, possibly incorrect speed reading from the ECU.
3. **Mathematical Approach**:
I think we need a formula that adjusts the VSS output based on tire size and gear ratio. Maybe something like:
Corrected Speed = (VSS * Tire Diameter / Standard Tire Diameter) / Gear Ratio
But wait, how does differential gear ratio affect this? The gear ratio affects how many times the wheels turn per engine revolution. So if the gears are lower (numerically higher), each wheel rotation corresponds to fewer engine RPMs.
4. **Data Collection**:
To get these values into Torque, we might need new PIDs for tire diameter and differential ratio. But GM vehicles probably don't have these parameters stored in OBD2; they're usually hard-coded or require manual input. So the user would need to enter their truck's specific data.
5. **Implementation Steps**:
- Modify Torque app to accept a new PID that takes VSS, tire diameter, and gear ratio as inputs.
- Calculate corrected speed using these values.
- Display both original and corrected speeds for comparison.
6. **Potential Challenges**:
- Some vehicles might not expose the necessary data via OBD2, requiring additional hardware or software to capture it.
- Real-time calculations need to be efficient enough not to lag.
- Ensuring accuracy across different models and tire sizes could be tricky.
7. **Testing**:
After implementation, testing with known good setups would help verify if the corrected speed matches actual conditions (like using a GPS for reference).
I'm probably missing some details about how OBD2 works or specific GM protocols, but this seems like a logical starting point. To address the issue of inaccurate speedometer readings in General Motors trucks and SUVs with over-sized tires, we propose creating a new Speedometer PID within the Torque app. This solution involves capturing vehicle data to correct the reported speed based on tire size and drive-train parameters.
### Solution Overview:
1. **Problem Understanding**:
- Over-sized tires cause each rotation to cover more distance than standard tires, leading the ECU to under-report speed as it miscalculates rotations.
2. **Key Inputs Required**:
- Actual Tire Diameter: Essential for adjusting the perceived number of wheel rotations.
- Differential Gear Ratio: Influences how engine RPM translates into wheel speed.
- Vehicle Speed Sensor (VSS) Output: The current, possibly incorrect speed reading from the ECU.
3. **Mathematical Formula**:
Corrected Speed = (VSS * Actual Tire Diameter / Standard Tire Diameter) / Differential Gear Ratio
4. **Implementation Steps**:
- Modify Torque to accept new PIDs for tire diameter and gear ratio.
- Calculate corrected speed using the formula above.
- Display both original VSS speed and corrected speed.
5. **Challenges Considered**:
- Some data may not be available via OBD2, necessitating manual input or additional hardware.
- Ensuring real-time efficiency to avoid lag is crucial.
- Accuracy must be validated across various models and tire sizes through testing.
6. **Testing Protocol**:
Use a GPS reference for accurate speed comparison during testing phases to verify the corrected speed's accuracy
### Conclusion:
By integrating these inputs into Torque, users can achieve more accurate speed readings, enhancing safety by correcting underestimations from over-sized tires. This approach leverages existing data and user input to provide an effective solution within the app's framework.
Last edited:
