Smart Control Automotive
SCA exists to give car owners more knowledge, transparency and freedom of choice. A car is a long-term asset: understanding it better helps you make informed decisions about using and caring for it over time.
SC OBD2 puts that idea into practice today. This Android app reads the fault codes and data your car makes available. The app includes basic and paid features. You need an Android phone, an OBD2/EOBD-compatible vehicle and a suitable adapter, purchased separately.
The app remains useful after that first reading, whether your car is recent or one you have driven for years. Engine speed, temperature and load, where available, make more sense when viewed together. Choose useful parameters and follow their changes instead of relying on an isolated number.
For example, a temperature reading during engine warm-up has a different context from one taken with the engine already warm. SC OBD2 makes supported data visible so you can decide what to explore. Availability depends on the car and adapter; the app does not automatically determine whether a value indicates a fault.
Choose the readings to follow →When something changes, remembering that “it used less fuel before” may not be enough. A history of trips and data actually saved lets you revisit a specific period and compare it with another. You can distinguish a week of short urban journeys from a longer drive, for example, using available distance, duration and consumption information.
You do not need to wait for a problem to build that reference: readings that were never recorded cannot be recovered later. Configure the profiles and recording needed for your use and keep the sessions that matter. Comparisons help you ask better questions; consumption and performance depend on their conditions and are not certified measurements.
Learn how to use history →SC OBD2 is a native Android app. Your phone communicates with the adapter and keeps a local history. Once the connection is configured, you can read supported OBD data and view saved history without Internet access; these local features do not require an SCA account. Purchases, Google Play checks, web guides and online services have separate network requirements, covered alongside other processing in the privacy notice.
Free lets you check compatibility, read standard OBD codes and try basic parameters. Full becomes useful when you want to work with those records over time: eligible additional parameters, history beyond Free limits and CSV export from supported views. DTC clearing requires Full and vehicle support; clearing a code does not repair its cause.
Full is a one-time purchase for the life of the app, with no monthly or annual renewal. It does not promise perpetual compatibility, future SCA products or unlimited third-party services. Check the price and terms on Google Play; if you already hold a licence, check its recognition before buying again. Keep a copy of important data and review files before sharing them.
Compare Free and Full →Before choosing an adapter, check its exact model, your vehicle’s protocol and the connection supported by the app. An ELM327 label alone does not guarantee compatibility. The guide takes you from finding the diagnostic socket to connecting, without assuming you already know PIDs or protocols.
With the car stationary, connect the adapter following its manufacturer’s instructions, open SC OBD2 and check the connection status. Start with fault codes or a few available readings. When you want to keep their context over time, set up profiles and recording: not everything shown on screen is automatically saved.
See how to get started →One screen, one story: choose a view and select its glowing points to understand tools, values and differences.
Find the vehicle profile and the last session summary in one place.
Bench-test captures, edited demo illustrations and synthetic test entries, labelled for each view. This explanation does not connect to a car and is not an in-app demo mode.
All screens and their context →
Edited demo illustrations complete selected fields using example data: fuel €1.80/l, tank 50 l. They explain functions and are not real test results. Other images retain the context stated in their captions.
The SCA vision goes beyond a single app: making automotive technology and information more useful to people, so they can make better-informed choices. SC OBD2 puts that vision into practice today, with its own features and history.
SCA Runtime, SCAdia and SCAvia are distinct products and developments within this vision. Each has its own aims, features and availability, presented in the relevant sections. The project’s story, its founders and Smartino explain where it came from and where it is heading, while keeping the ecosystem’s future separate from what SC OBD2 offers today.
Explore the SCA project →Engine trends, fuel information and history: each view adds a different context.
Compare engine load, RPM and coolant temperature, reading each parameter’s value, unit and trend.
Live Data showing engine load, engine speed and coolant temperature with demonstration OBD data. English interface.
Despite the historical tab name, this graph is not a DTC view. Displayed frequency and latency describe a test sample, not a general guarantee.
Distinguish fuel quantity, tank level and consumption per unit distance.
Illustrative fuel example: 0.1 l rounded, €0.17 cost and 201 km estimated range. Edited image using stated assumptions.
The added fields are illustrative examples using fuel at €1.80/l and a 50 l tank. Cost uses unrounded fuel consumption; range uses the vehicle profile’s consumption. These are not real test results or guarantees of savings or accuracy.
Find several saved entries and compare the totals for a selected period.
App history populated with synthetic test entries: 6 demonstration trips, without real locations.
Pre-existing synthetic test entries, not real journeys or an integrated demo mode. Distances are in miles, not kilometres. Do not infer real-world efficiency from these synthetic entries.
From Smart Control to SCA · Vision
Safety and reducing environmental impact are essential. For SCA, progress must also consider the cost of mobility for people.
The project aims to help extend the useful life of cars that remain viable: understand their condition better, make use of their remaining mechanical capability and update their digital capabilities where possible.
This does not mean keeping every vehicle on the road at any cost. It means offering another choice when continued use makes sense.
A car’s digital evolution and its mechanical life need not share the same expiry date.
The idea: evolve the digital capabilities of a car that is still sound, where possible. This sketch does not show measured lifespans or guarantee updates for every vehicle.
Data close to the user; cloud services where they add value.
New digital capabilities for older vehicles too, within real limits.
Information that is accessible, understandable and clear about its source.
More choice in digital tools and services.
Open onboard experiences, with attention to driving first.
Systems and services able to work together.
Common foundations in development
Significant work on common foundations prepares the evolution of Smart Control and new products that are not tied to one operating system. The roadmap includes Android, iOS/iPadOS, macOS, Windows and Linux, with progressive releases through major stores and channels suited to each platform.
Smart Control for Android is available today. The other destinations are planned in the roadmap: supported systems, features and release status will be stated for each product.
Explore the roadmap →Smart Control is the starting point for SCA: a platform project to expand what a car can do, without making replacement the only route to new technology or tying that progress to a single digital ecosystem. The project →
Read the vision, reflect on its choices, try what is available and describe what works and what needs to improve. A different point of view can help, too.
How to participate →