Ever wondered why your Fixd Obd2 Scanner works the way it does? You might have noticed it needs logins and sometimes network access, which can be different from those cheap, basic scanners. As developers deeply involved in automotive diagnostics, we want to shed some light on the intricate world of OBD2 and explain the technology that powers your FIXD scanner, making car repair more accessible and understandable.
The reality is, OBD2 and CAN systems are far more complex than they initially appear. Those budget-friendly $15 scanners often come with significant limitations. They typically rely on small, on-device code databases, frequently scraped from wikis, and offer support for only single protocols and modules. These basic tools often lack sophisticated error filtering or advanced frame parsing necessary to gather data from vehicles with complex issues. Moreover, they usually operate using static, one-size-fits-all scripts on a very restricted set of vehicle addresses.
The complexity escalates dramatically when you move beyond just engine diagnostics. Consider supporting non-engine modules like airbags, TPMS, seatbelts, or transmissions. These often involve multi-protocol communication, requiring the scanner to switch protocols mid-stream and negotiate communication uniquely for each make, model, and year. Different modules can also operate at specific baud rates, adding another layer of intricacy. Anything beyond basic Mode 3/7/9 hexadecimal to code parsing quickly becomes incredibly challenging.
Storing the vast and varied data branches required for every vehicle directly within an app is simply impractical. To further complicate things, some diagnostic commands and instruction steps are licensed and proprietary to specific manufacturers, meaning car companies charge substantial fees for access.
This is where FIXD takes a different approach. Instead of housing a multi-gigabyte database on your phone, FIXD scanners intelligently assess your car’s capabilities upon connection. They then download the latest, customized command list specifically tailored to your vehicle. We have a dedicated team of engineering interns who focus on specific modules, such as airbags in 2008-2012 Toyota models. They develop test scripts, gather data, write custom parsers, and continuously deploy updates to our system.
Because these scripts are refreshed and fetched every time you log in, your FIXD app benefits from new code capabilities each launch, even without a traditional app update. This dynamic system, however, necessitates API calls, which in turn require network access and authentication tokens. While we do cache these scripts locally for efficiency, the initial download requires a network connection.
Regarding logins, we understand the user feedback. As a startup that began with just four people, our infrastructure was initially built around account-based access. We are currently undergoing a significant overhaul to streamline the signup process, including implementing auto-account generation. This is a major undertaking and will take time to fully implement.
In the interim, we’ve introduced an “offline mode.” If you’ve logged in successfully at least once and the necessary information is cached, you can access the app even without an active internet connection. This mode may feature an “OFFLINE MODE” banner to indicate reduced functionality, primarily concerning features that require up-to-date vehicle-specific data fetching.
It’s important to note that network access is not required for Live Data once you are logged in and the initial data is downloaded. You only need the network for the initial authentication, login process, and fetching the latest diagnostic scripts upon launch. Once these steps are completed, live gauges and real-time data within your car function independently of network connectivity.
However, due to the reasons outlined above, scanning and reading codes will likely always require an internet connection to ensure access to the most accurate and vehicle-specific diagnostic information. To mitigate potential connectivity issues during scans, our system includes a network error prompt that saves your scan data. If you initiate a scan, lose internet connectivity, and then regain it, a popup will appear allowing you to “Retry.” Tapping this will resubmit the raw data for parsing and allow the scan to continue seamlessly.
Finally, let’s address FIXD Premium. FIXD Premium is an optional subscription service offering enhanced features that incur ongoing costs for us. For example, our confirmed fixes feature is powered by a third-party company that compensates mechanics for their diagnostic data. We pay them per API call to access this valuable information. Similarly, our issue forecasting feature, which involves issue aggregation, machine learning analysis, and substantial backend infrastructure, represents a significant ongoing investment. These advanced features are simply not sustainable to offer without a subscription model. We are continually working to improve our messaging and clearly differentiate between free and premium features to ensure transparency for our users.
Thank you for your valuable feedback. We are committed to continuous improvement and are excited about the new features on our roadmap for this year, both for free and premium users. Stay tuned for updates as we continue to enhance your car diagnostic experience with FIXD.
EDIT: We are pleased to announce that Offline Mode is now live! Please update to version 7.1.1 to access this new feature. Remember, you need to log in successfully at least once for “Offline Mode” to activate. You can now also view basic codes from a scan even in offline mode via the network error popup. This is just the beginning, and we are dedicated to further refining and improving Offline Mode over time to provide you with even greater diagnostic capabilities, even when you’re off the grid.
