[CENTER][URL='https://www.opensaab.com/'][IMG width="220px"]https://www.opensaab.com/static/t2/open-connection-icon.png[/IMG][/URL]

[SIZE=6][B]Introducing OpenSAAB T2[/B][/SIZE]
[SIZE=4]Original Tech 2 diagnostic menus on Android, macOS and Windows[/SIZE]

[B]Developer preview • Chipsoft Pro USB[/B]
[I]Updated 4 October 2026[/I]

[SIZE=4][B][URL='https://www.opensaab.com/static/t2/download.html']Downloads, installation and release notes[/URL][/B][/SIZE][/CENTER]

I wanted to use a Tech 2 on my phone. That turned into OpenSAAB T2—and a lot of late nights.

It’s an open-source emulator running the original diagnostic software, with familiar Tech 2 menus, touch or keyboard controls and a direct USB connection to your adapter.

[B]A quick thank-you[/B]

OpenSAAB owes a lot to the SAAB community that came before it. Thanks to [B]Matthias Claesson[/B], creator of TrionicCANFlasher, for his pioneering work on community SAAB tools; [B]Bojer[/B] for his mentorship; and [B]roffe84[/B] and [B]rogue33[/B] for their advice.

Special thanks also to [B]tpw_rules[/B] for his earlier Tech2Win for SAAB work, including addressing the “I-Bus Missing” communication problem on 2003+ 9-3s. Work like this helped show what was possible and inspired others to keep going.

These thanks recognise their independent work and guidance—not a claim that they developed or endorse OpenSAAB.

[ATTACH]322572[/ATTACH]

[SIZE=5][B]What’s working?[/B][/SIZE]

Our NG 9-3 testing has included:
[LIST]
[*]VIN and vehicle identification.
[*]Fault-code reading and saved reports.
[*]Engine Data.
[*]Security access—including re-adding the reverse parking sensors on my own car.
[/LIST]

Most completed vehicle testing has been on Android, including a Pixel 7 and Huawei Mate 20 X. Mac and Windows previews are also available, with different levels of testing and feature coverage.

[B]This is a developer preview. Results from one device or vehicle don’t establish that every module or procedure works.[/B]

[SIZE=5][B]Published Android 64-bit: 0.1.0-preview.29[/B][/SIZE]

[B]Preview.29 improves report review and session handling:[/B]
[LIST]
[*]The reviewed report stays open through rotation and can be restored after a cold relaunch.
[*]Sending requires separate consent for that exact report. Rotation keeps consent for the same open review; dismissal or a cold relaunch resets it.
[*]Confirmed sent reports show [B]Already sent[/B] with their receipt when restored.
[*]When emulation ends, the live display clears and the reason remains visible.
[*]Offline Actions now includes [B]ECU information[/B]. Diagnostic shortcuts explain when a supported adapter and freshly identified vehicle are required.
[/LIST]

The installed version and optional daily idle update checks from preview.28 are included. Nothing downloads or installs automatically, and active diagnostics aren’t interrupted. Older installations need one manual update to gain the reminders. Install over the existing app to keep your software and settings.

It also includes the richer reviewed reports and security-handoff alert correction from preview.27. [B]Reporting while emulation runs remains a later step: stop first.[/B] If an upload response is lost, retrying the same prepared report returns the same receipt. Preparing a new report can create a separate receipt for the same incident.

[B]Checked on this exact package:[/B] offline menus and report review on a Pixel 7, plus two read-only HS-CAN identification and Trionic 8 DTC reads using Chipsoft Pro firmware 1.5.2 on an ECM bench. This does not establish full original-menu ECU information, SW-CAN, security access or complete vehicle coverage on preview.29. The 32-bit head-unit release is unchanged.

[B]Field reports from some Samsung and Motorola phones remain under investigation.[/B] That does not establish a device-specific cause or mean every reported crash is fixed.

[SIZE=5][B]Bluetooth development[/B][/SIZE]

Local development builds now include direct Android Bluetooth connections. On a Pixel 7 with Carista EVO firmware MIC3413 V2.0.84, preview.43 completed fresh VIN reads, seven Trionic 8 ECM identifiers and a complete current/history engine-code report. The saved code report reopened in the phone. No codes were cleared.

[B]These builds are not yet public downloads.[/B] The tested preview.43 APK is a debug build. Release-package checks and fresh Chipsoft and vLinker MC+ regression tests remain pending. Bluetooth currently covers the separate VIN/HS-CAN ECM probes; the full original Tech 2 menu transport, SW-CAN/body modules and broader adapter coverage are still being developed.

[ATTACH]322574[/ATTACH]

[SIZE=5][B]Phones, head units and desktops[/B][/SIZE]

[LIST]
[*][B]Android:[/B] compatible ARM devices running Android 8 or newer, with USB host support.
[*][B]32-bit head units:[/B] a separate experimental release. Startup has improved in our tests, but memory, USB support and performance vary. A 64-bit processor can still run 32-bit Android.
[*][B]macOS:[/B] separate Apple silicon and Intel downloads for macOS 12 or newer. The public 0.2.8 package has narrower coverage than our development builds; a fresh Chipsoft test and native Intel run on that exact package remain pending.
[*][B]Windows:[/B] an x64 preview tested on Windows 10. Use Direct USB/CDC, the default. The OEM comparison route is experimental, and an intermittent Chipsoft receive-parser stop remains under investigation.
[/LIST]

[B][URL='https://www.opensaab.com/static/t2/download.html']Choose your platform and follow its installation guide[/URL][/B]

That page keeps the current builds, checksums, source links and known limitations together. The platforms have separate release schedules and do not yet have complete feature parity.

[SIZE=5][B]Which adapter?[/B][/SIZE]

[B]Chipsoft Pro is the current tested adapter path. Please use genuine hardware.[/B]

VCX Nano remains experimental on Android, with channel initialization unresolved. MDI, Mongoose and other adapters do not currently have a supported public OpenSAAB connection.

NG 9-3 procedures can need both HS-CAN and SW-CAN on OBD pin 1. An ECM-only bench may read a VIN while lacking the network needed for other functions.

[B]A VIN read does not establish full module access. A J2534 or SW-CAN label alone does not establish OpenSAAB compatibility.[/B]

[SIZE=5][B]Getting started and security access[/B][/SIZE]

Install the appropriate app, choose your diagnostic software, connect Chipsoft Pro and turn the key to [B]ON[/B] before identification. Start with vehicle information and fault-code reading.

You can explore the menus without a car using [B]Run without an adapter[/B]. Installed local USB diagnostics can work offline; downloads, online lookups, report uploads and security processing need internet.

Security access has worked in our Android vehicle tests. Windows includes processing and firmware continuation; broader desktop vehicle testing remains ongoing. Follow the app’s collection, password and ignition prompts.

[B]POST-AUTH means processed security data was imported into the emulator’s working card.[/B] The vehicle must still accept the requested operation.

OpenSAAB is contacted first. Bojer fallback requires your permission; the OpenSAAB password is not forwarded. The fallback outage path has not been live-qualified.

Processing shares the VIN and required security data with the selected service. Review the in-app disclosure and [URL='https://www.opensaab.com/static/t2/privacy.html']privacy information[/URL].

[SIZE=5][B]Help us investigate a problem[/B][/SIZE]

On current Android, stop emulation first, then use [B]Report issue → Prepare report → Review → confirm consent → Send to OpenSAAB[/B]. Windows has its own review and Send controls. An internet connection is enough; no email app is needed. This feature is not included in the public Mac 0.2.8 release.

[B]Please write what happened in the description field.[/B] Include:
[LIST]
[*]Your app version, device and operating-system version.
[*]Adapter model and firmware version, if known.
[*]The exact menu or button, expected result and visible error.
[*]Whether you were using a car, bench ECM or offline mode.
[/LIST]

Share the receipt number privately instead of posting raw logs, VINs or security data. Successful tests are welcome too—say exactly what worked.

Saved DTC reports can include the VIN and indicate partial capture. A saved list does not establish that every module was scanned; review it before sharing.

[ATTACH]322576[/ATTACH]

[SIZE=5][B]Help develop another adapter[/B][/SIZE]

[B]OpenSAAB Collector[/B] is a separate Windows tool for people with an existing working Tech2Win and adapter-driver setup.

[B]Collector 0.5.5 fixes adapter selection behind USB hubs.[/B] Earlier versions could hide the adapter and leave only the hub available. An upload could complete successfully while containing hub traffic rather than the adapter session. The new version keeps those adapters in the device list.

[B][URL='https://github.com/djfremen/OpenSAAB-Collector/releases/tag/v0.5.5-preview.1']Download Collector 0.5.5 — Windows EXE, instructions, checksums and source[/URL][/B]

Run Collector as administrator and select the [B]adapter itself[/B], not Generic USB Hub, the mouse or the keyboard. Start capture before starting Tech2Win or opening its adapter connection.

Record a short initialization or read-only session, then [B]Stop capture[/B]. Nothing uploads automatically. You can optionally use [B]Sanitize capture[/B] to create a separate copy and review the changes before choosing [B]Upload[/B].

The sanitizer handles supported text matches; it cannot guarantee removal of every identifier or security exchange. Keep raw captures out of public posts.

[B]What is verified?[/B] Windows build and regression checks passed, including adapter selection through USB hubs. A fresh capture on Windows 8 Pro 32-bit with MongoosePro GM II is still needed. Collector helps develop adapter support; it does not establish a working Mongoose connection in OpenSAAB T2.

[B][URL='https://www.opensaab.com/static/t2/download.html#collector']Collector download, instructions and privacy limits[/URL][/B]

[SIZE=5][B]More to follow[/B][/SIZE]

Next priorities are field-report investigations, head-unit reliability and broader vehicle testing. Additional adapters, Linux and older SAAB/pre-CANdi support remain development work.

[URL='https://www.opensaab.com/#watch']Introduction videos[/URL] are on the website. They show an earlier build; updated walkthroughs and vehicle demonstrations will follow.

Developers and testers are welcome. You don’t have to write code—a clear description of what worked, what failed and how to repeat it is valuable.

[CENTER][B][URL='https://www.opensaab.com/']OpenSAAB website[/URL] • [URL='https://github.com/djfremen/OpenSAAB-T2']Source & releases[/URL] • [URL='https://www.opensaab.com/static/t2/community.html']Community & social links[/URL][/B][/CENTER]

If it helps you and you’d like to [URL='https://ko-fi.com/djfremen']buy me a beer[/URL], thank you. Testing, feedback and contributions are equally welcome. Donations do not unlock features or guarantee compatibility.

[I]The emulator code is open source. Original diagnostic firmware has separate licensing terms. OpenSAAB is independent and is not affiliated with SAAB, GM, Bosch, Vetronix or adapter manufacturers.[/I]