That’s when he looked back at the Delphi DS100E. It was sitting on the van’s greasy floor, half-submerged in a puddle of antifreeze and rainwater that had leaked under the side door. The screen was still on. The fan was still humming. It didn’t care.
“Talk to me, old friend,” he muttered, tapping the glove-friendly touchscreen with his thumb. The DS100E hummed, its fan spinning up despite the dust and grime caked into its bezels. On screen, the software populated a list of ECUs—Engine, Transmission, ABS, Airbags. One by one, green checkmarks appeared. Except one. delphi ds100e
The customer, a nervous woman named Mrs. Alvarez, peered into the van. “Is it fixed? The dealer said they’d need three weeks for a ‘network diagnosis.’” That’s when he looked back at the Delphi DS100E
Elias sighed. On a modern Audi, that wasn’t just a loose wire. That was a gateway issue. It could be a bad module, a chewed harness, or—as he suspected—the owner’s attempt to replace the steering wheel himself and botch the clock spring. The fan was still humming
He navigated not with a mouse, but with the physical buttons along the bottom edge. He launched the oscilloscope function—something his dead laptop couldn’t even do without a separate $800 module. He clipped the DS100E’s included breakout box into the Audi’s CAN bus network. Within three minutes, he saw the problem: the clock spring signal was intermittent, but more importantly, the showed a voltage drop on pin 6 of the OBD-II port. Not a module failure. A corroded ground behind the kick panel.
Forty-five minutes later, he had the ground cleaned, the clock spring bypassed (temporarily), and the airbag light cleared. He unplugged the Delphi. The tablet was warm, grimy, and still had a smear of his breakfast sandwich on the screen.