French developer Paul Le Gall removed the electronic modules from his first Saab 9-3, rebuilt the car’s network on a cabinet, and used the resulting test bench to develop WIS, EPC, diagnostic, and Tech2 tools that run through a modern web browser.
The green display at the right edge of Paul Le Gall’s cabinet is warning, in French, that the remote control battery is weak. Beside it, a Saab 9-3 instrument cluster is awake, the center display is powered, and a trail of wiring connects the CIM, MIU, BCM, ECM, and other modules that once belonged to a complete car. The arrangement looks improvised because it is, but electronically it behaves like a stripped 9440 platform.
This is the development bench behind Saabiste.net, a browser based technical platform created by Le Gall, a 29 year old developer in France who is known as oamne in the Saab community. His first car was a 2003 Saab 9-3 NG. When that car later became a donor, he kept around a dozen of its electronic modules and connected them on his living room furniture. The result gave him a working network that could answer real diagnostic requests without requiring a complete 9-3 in the driveway.
That distinction matters. Saabiste was not assembled only by copying old workshop pages into a new interface. Paul used the bench to observe GMLAN traffic, study CAN frames, compare module responses, and test communication through the OBD connection. He then built the web platform around those findings, with the 9-3 NG as the first serious diagnostic target.
A Saab 9440 Network Without the Bodywork
The 9-3 NG divides its electronic traffic between high speed CAN and low speed single wire CAN. Powertrain and chassis controllers communicate on the 500 kbps network available through OBD pins 6 and 14, while many body and comfort modules use the 33.3 kbps single wire network on pin 1. A basic consumer interface can therefore reach only part of the car unless its hardware can switch to the second bus.
Paul’s bench allowed him to work through this division with actual Saab components. The CIM could act as a gateway, the MIU could display the consequences of commands, and the surrounding modules could provide the identification data and fault responses expected from the car. More importantly, unsuccessful experiments could be repeated without immobilizing a daily driven Saab.
The bench also explains why the project currently concentrates on the 9440. Saabiste contains resources for several generations, but its most ambitious electronic functions depend on a detailed understanding of the 2003 to 2012 9-3 network. Paul says ECU reflashing and module pairing already work in this controlled environment. His current task is decoding the Tech2 option configuration strings well enough to make replacement module programming predictable through the browser.
Three Months of Development on a Damaged Celeron Laptop
Paul says the initial platform was built during three months of concentrated development. The machine in his photograph is an aging Intel Celeron laptop with several missing keys, not a carefully arranged prop for the launch. According to Paul, the Saabiste codebase has grown beyond 190,000 lines. That number is his own measurement, but the visible scope of the site confirms that the project extends far beyond a static documentation archive.
The development process also included AI pair programming, which Paul openly acknowledges on the site. The published technical utilities use C, Java, and Python, while the web platform presents the resulting data and services through a Next.js interface. The meaningful test is therefore not whether every line was entered manually, but whether the tools can communicate with the hardware, preserve the structure of the factory data, and produce repeatable results. The test bench and the recorded vehicle demonstrations provide the first evidence for that.
WIS and EPC Without a Legacy Windows Installation
For most owners, the immediately useful part of Saabiste is not module programming. It is the ability to open Saab WIS and the Saab EPC in a current browser without preparing a Windows XP machine, mounting an old disc image, or maintaining a virtual machine only for workshop software.
SaabPlanet previously reviewed the available free online Saab WIS and EPC resources. Saabiste belongs in that practical lineage, but it adds its own interface and links the documentation to other parts of the platform. WIS procedures can be searched by component, repair term, or DTC, and internal references can lead directly to associated operations. EPC diagrams retain clickable callouts for original part numbers, while model, year, engine, and transmission filters reduce the chance of selecting a similar but incorrect component.
The public model selectors cover the 900 and 9000 in EPC, both generations of the 9-3, and the original and final 9-5. WIS coverage follows the models represented in Saab’s digital workshop system, with the classic 900 remaining outside that software architecture. English, French, and Russian interfaces make the information easier to use beyond the markets where surviving workshop installations are still common.
Registered users can connect the research to a virtual garage. A YS3 VIN identifies the vehicle, after which the owner can save WIS procedures, part references, maintenance entries, invoices, and diagnostic reports. That turns the site from a temporary lookup page into a working record for one or several cars. It also means owners should read the site’s privacy policy before storing VIN linked documents or security related diagnostic data.
When the Browser Starts Talking to the Car
The diagnostic section is where Saabiste moves beyond the familiar concept of online workshop documentation. Its console can identify control units, read and clear diagnostic trouble codes, show module part numbers and software identifiers, and save a scan as a PDF report. Paul has demonstrated these functions on a 2006 Saab 9-3 through both WebSerial and a J2534 PassThru interface.
In WebSerial mode, a Chromium based browser such as Chrome or Edge receives permission to communicate with a USB serial device. Saabiste was developed primarily around the OBDLink SX USB interface. That adapter can scan the high speed bus, including the engine controller, ESP, transmission controller, and the relevant gateway responses. Standard OBDLink SX and ELM327 USB cables do not contain the hardware switching needed to reach the single wire bus on pin 1, so the body modules remain outside a complete scan.
The J2534 route addresses that limitation with professional workshop hardware. Since a browser cannot load a Windows diagnostic DLL directly, Paul’s lightweight background agent runs locally and passes commands through a WebSocket connection on the same computer. The agent detects installed J2534 drivers, translates the browser requests into PassThru calls, and returns the module responses to the web interface. Testing has centered on the Scanmatik 2 Pro, including its physical support for single wire CAN. VXDiag VCX Nano has also received limited high speed testing, while compatibility with other interfaces depends on both their drivers and their actual pin 1 circuitry.
This is also the point where the development status must remain visible. Saabiste’s documentation labels the live diagnostic console an experimental feature. Standard fault reading is non destructive, but raw CAN commands and unfinished sequences deserve the same caution expected from any engineering tool. The car should be stationary, the battery stabilized, and the connection left untouched during an active session.
Tech2 Security Access Without Rebuilding the Entire Workshop Server
Basic DTC reading does not require Saab Security Access. Key learning, CIM and ECM pairing, and the marriage or divorce of protected modules are different operations. On the 9-3 NG, Tech2 normally obtains a temporary authorization through TIS2000 or GlobalTIS before it can enter those menus. That old process also expects the correct PC environment, Java components, serial connection, and a functioning Tech2 or Tech2Win installation.
Saabiste’s Tech2 and Security hub separates several of those tasks into browser tools. It can manage the security area on a Tech2 PCMCIA card, calculate Seed and Key responses, and provide VIN to PIN decoding for the 9-3 NG. That last function is limited to the YS3F 9440 platform and should not be presented as a general Saab immobilizer calculator.
For owners confronting a failed CIM or a car with missing keys, these functions sit close to issues SaabPlanet has covered in its guides to lost Saab keys and the 9-3 steering lock, CIM, and ISM relationship. Saabiste can shorten the route to the required authorization data, but it does not remove the need to understand which module is being added, what must be divorced, and how the immobilizer chain will react.
Binary Tools for Work That Cannot Be Done Through OBD
The Binary Explorer is intended for a smaller and more experienced group. EEPROM contents cannot usually be extracted through the diagnostic socket because the control module isolates that memory from ordinary K Line or GMLAN services. A failed MIU, CIM, PSG16, or engine controller may therefore require an external programmer, a verified bench power supply, and sometimes direct access to the memory chip.
Saabiste provides tools for analyzing and preparing those files. The MIU editor can identify VIN and part number data and align a replacement cluster with the vehicle’s documented mileage. The CIM utility can process a Delphi 93C66 dump, remove donor key data, reset lockout information, and recalculate checksums. Other sections expose SPS calibration files extracted from TIS databases, assemble fragmented GMLAN firmware, and prepare DPS utility archives for certain module operations.
These are not casual download and flash functions. Saabiste itself instructs users to read a chip twice, compare file hashes, retain the untouched original dump, and verify the hardware part number before writing anything back. That discipline is essential. A bad connection or incompatible binary can turn a repairable module into a non responding one, while mileage and immobilizer data also carry legal and security consequences outside the purely technical problem.
Does Saabiste Replace GlobalTIS?
Paul describes the new workflow as making GlobalTIS and TIS2000 obsolete for a 9-3 NG owner who needs SPS files or Security Access. The direction is understandable, but the present distinction is narrower. Saabiste already removes the old server from several common 9440 tasks, including access to calibration data, security calculations, and parts of the Tech2 authorization process. It does not yet replace every GlobalTIS, TIS2000, Tech2, or SPS function across every Saab generation.
The platform’s own documentation still contains installation guides for GlobalTIS, TIS2000, Tech2Win, GM DPS, Windows XP virtual machines, and the original WIS and EPC applications. Those guides remain useful because some owners and workshops need a known offline environment, and because the browser based programming workflow is still being completed. The most accurate description is therefore that Saabiste is reducing dependence on legacy workshop software, beginning with specific 9-3 NG procedures.
Five Supporting Tools Are Already Open on GitHub
Paul has published five supporting projects under the MIT license through his GitHub profile. The J2534 WebSocket agent connects the site to native PassThru drivers, while a separate sniffer records high speed and single wire CAN traffic and decodes GMLAN and ISO TP messages. Two Java tools extract SPS calibration data from the Transbase databases used by TIS2000 and GlobalTIS. A Python utility converts the proprietary EPC UMF diagrams into PNG images and retains the clickable hotspot coordinates.
Those repositories do not necessarily make the complete Saabiste platform open source, but they make several of its most important conversion and communication components inspectable and reusable. That can matter later if the main service changes, if another developer wants to extend hardware support, or if the community needs to preserve the data extraction path independently of the website.
An AI Workshop Assistant, With the WIS Still in Charge
Saabiste also includes an AI assistant intended to search its technical material, connect a DTC with the relevant WIS procedure, and help users locate an EPC entry. Paul plans a specialized local and open source Saab model that could eventually run without dependence on a remote service. For now, the useful editorial distinction is that the assistant is a navigation and interpretation layer. Factory tightening values, electrical measurements, and programming sequences should still be checked against the underlying WIS page before work begins.
The same caution applies to account data. Saabiste says VIN to PIN calculations run in temporary memory and are not stored, while its broader privacy policy explains how account, garage, diagnostic, and API information may be processed. Owners using the platform only for WIS and EPC lookup face a different exposure from those uploading invoices, saving scan histories, or submitting security requests. The service provides its privacy and liability terms publicly, and advanced users should read them before connecting a car or storing records.
The Roadmap Begins by Finishing the 9440
Paul’s immediate objective is not to add every Saab model at once. He wants to finish the 9-3 NG workflow first, including browser based flashing, module pairing, and reliable extraction of the configuration strings that Tech2 uses when a controller is replaced. Only after that suite is stable does the roadmap move toward deeper diagnostic support for the original 9-5 and 9-3.
A later offline application is planned for Windows, Linux, and macOS. That version would matter to workshops that cannot depend on an internet connection while a vehicle is being programmed, and to a community that has already learned how quickly online manufacturer services can disappear. Voluntary contributions currently support hosting, test hardware, and the computing capacity required for further development.
A Workshop Project That Can Be Judged by What Already Works
Saabiste.net is strongest when its available tools and its roadmap are kept separate. The WIS and EPC interfaces can be used now. The virtual garage can organize the results. DTC reading has been demonstrated on a real 9-3 through WebSerial and J2534 hardware. The security and binary sections already expose utilities that normally require several pieces of aging workshop software. Web flashing and seamless module pairing remain the next major engineering test.
The photograph of the living room bench summarizes the project better than a polished product graphic could. It contains the electronic remains of Paul’s first Saab, still communicating years after they left the car. Saabiste is his attempt to make that communication understandable and usable through equipment that current owners can still obtain. Whether it becomes a complete workshop environment will depend on testing, documentation, and outside contributions, but the foundation is already public enough for Saab owners to examine rather than merely take on trust.
