txlogger and Trionic 7/8 Explained: OpenBIN, OpenSID, Sensors, and How It Stacks Up Against a Tech2

ByKenji Alvarez

What txlogger actually is

txlogger is a free, open-source data logging application for Saab cars running Trionic 5, 7, and 8 ECUs. Built by community developer roffe and hosted on GitHub, it speaks directly to the ECU over CAN bus, sidesteps the limitations of generic OBD2 PIDs, and pulls data at rates older logging tools cannot match — up to 100 samples per second on Trionic 7, around 25 per second on Trionic 8. For context, older suites typically returned a shaky 6–10 data points per second.

To run it you need a Windows 10 64-bit PC or tablet (the interface is OpenGL-rendered, so a capable GPU matters), a compatible CAN bus adapter, and the right cable into the OBD port. The adapter list is broad: CANUSB, OBDLink SX/EX, Just4Trionic, CombiAdapter, Canable, and several J2534-compatible devices including the Drewtech Mongoose GM2/3, Kvaser, OBDX Pro, and SM2 PRO all work.

OpenBIN and OpenSID are not the same thing

This is the most common point of confusion for people arriving at Trionic logging fresh, and it is worth being precise about.

OpenSID is a feature you activate through T7 Suite without replacing the ECU binary. It unlocks the Saab Information Display — the small text panel in the dash cluster — as a real-time diagnostic readout. Once enabled, you hold the + and – buttons on the SID simultaneously to enter the OpenSID menu. No reflash required. Over 40 parameters become available: RPM, boost pressure, coolant and intake temperatures, knock events, catalyst temperature, battery voltage, fuel adaptations, exhaust temperature, gear selection, and more. It is an excellent solution for ongoing monitoring without any additional hardware.

OpenBIN is a different animal entirely. It is a modified ECU binary that you actually flash to the ECU. The key distinction is that it stores maps in RAM during operation rather than in flash memory, which is what enables live tuning: fuelling, ignition, and boost maps can be changed in real time while the engine is running, and the ECU picks up those changes within milliseconds. OpenBIN also unlocks advanced logging modes in txlogger that allow map values to be pushed back to the ECU on the fly. If you are on a stock or conventionally reflashed bin, you still get excellent data logging — you just do not get the live map-editing capability.

What sensors and parameters can actually be logged

This is where txlogger genuinely separates itself from generic diagnostic tools.

A standard OBD2 reader communicates in generic PIDs — a small set of standardised values the ECU translates for any compliant scanner. The Trionic 7 ECU contains roughly 4,000 internal symbols representing the actual variables the unit works with: sensor readings, calculated values, adaptation counters, error registers, and so on. txlogger exposes that entire pool directly.

In practice that means you can log manifold pressure, mass air flow, throttle position, boost target versus actual boost, knock counts per cylinder, ignition advance, injector pulse width, lambda, idle air control valve position, turbocharger pressure control duty cycle, and a great deal else. The software ships with presets covering the most commonly watched tuning parameters, so you are not starting from a blank slate, but custom layouts are straightforward to build around whatever your situation calls for.

One thing worth knowing: Trionic 7 and 8 are mass air flow systems, not MAP-based like the earlier Trionic 5. The primary load signal the ECU uses for fuelling comes from the MAF sensor. Manifold pressure is still measured and loggable — it is just not the primary input the ECU is computing from.

Does txlogger need a Windows laptop, or can it run on an external display?

As of 2024, txlogger is a Windows-only application — specifically Windows 10 64-bit or newer with OpenGL support for its GPU-rendered gauge and dashboard interface. A full laptop or Windows tablet is the requirement to run the software directly.

There is no official Android or iOS companion app. A small Windows tablet permanently mounted in the cabin is the most common in-car solution people land on when they want gauges visible while driving. Workarounds involving network streaming or secondary displays exist but sit outside txlogger itself and require additional tooling.

If the desire is gauges without carrying a laptop, OpenSID on the factory SID is actually a cleaner answer for day-to-day monitoring — it runs without any extra hardware at all once activated.

How txlogger compares to a Tech2

Tech2 and txlogger are doing related but different things, and the comparison is worth unpacking carefully rather than treating them as direct alternatives.

The Tech2 is GM’s proprietary dealer-level diagnostic platform. For Saab Trionic vehicles it provides access to diagnostic trouble codes across all modules — engine, transmission, ABS, SID, and others — along with live data from predefined PID sets, bi-directional controls for active testing, module programming, security functions, key cloning, speedometer recalibration, and service reset procedures. It speaks Saab’s proprietary bus protocol and reaches parts of the car a generic scanner simply cannot.

What it does not do well is high-speed performance logging. Pulling live data on a Tech2 delivers a handful of parameters at a few samples per second. Fine for fault diagnosis. Not fine for catching a knock event on a boost spike.

txlogger approaches the car from the opposite direction. It is not a diagnostic platform in the traditional sense — it does not handle module programming, security chip operations, or cross-module fault codes. What it does is give fast, broad access to the ECU’s internal symbol table at sample rates Tech2 cannot approach, with a logging and visualisation layer designed for performance tuning rather than fault finding.

The practical overlap is a small core of basic engine parameters: RPM, temperatures, a few pressures. Outside that overlap the tools are complementary. Diagnosing a fault in the ABS module or cloning a key, Tech2 is what you need. Tuning boost response or watching knock in real time under load, txlogger is the right tool.

Sources


Similar Posts