Blog

  • Some Recent Research With OBD-II

    I have this personal project that I am doing which right now is in the research and learning phase. To make a long story short, it implies a mobile app making calls to a vehicles ECU or computer to get the vehicles information, but not Maintenace data, but regular car data that would be displayed on a car’s dashboard. Why? Because sometimes vehicles have the hardware to do things, but not the software to display them. Such as my car. It is classified as containing a Tire Pressure Monitoring System with Easy Fill Alert. Meaning, my car monitors the tire pressure and alerts me when its low, and gives me a notification when the tire is full while filling it via the hazards and a beep of the horn. However, my car does not display the tire pressure anywhere on the machine. Same can be said with the “trip computer” and the cars MPG tracker. First off, my car displays two values on the trip views, which is time, and mileage. Not exactly what I want to know out of a trip, and my MPG tracker, displays the lifetime or since last reset. The app I want to make would improve the user’s knowledge on their vehicle’s performance. After recent searches online and conversations with ChatGPT, tracking accurate MPG or an odometer value is going to make the application a lot harder to tailor to all vehicles with an OBD-II port which is almost all American vehicles since 1998 at least. Reason being is the computer does not specifically report odometer milage or fuel usage at nearly any capacity, which means complex formulas and a little hope is all the app can do and just hopefully be accurate.

  • Hello world!

    Welcome to WordPress. This is your first post. Edit or delete it, then start writing!