U009B
Vehicle Communication Bus I
U009B addresses Vehicle Communication Bus I overall, the ninth network letter. Which network sits behind I is left to the manufacturer and not named in any public bulletin; U009B itself is not documented publicly by any maker. CARB requires that a lost digital input be detected with a separate code, which is the role of this group. Bus I has no wire-level codes of its own in the list, so U009B must also cover line faults. One cause is easy to overlook: a single module with a fault in its controller can hold the bus dominant. NXP's TJA1042 and TJA1051 transceivers counter this with a time-out that switches off the transmitter, so that the remaining nodes keep talking. Unplugging modules one by one finds such a node.
Possible causes
- Open or shorted wire on Bus I high
- One module holding the bus dominant medium
- Missing supply or ground at a Bus I module medium
Symptoms
- Functions of Bus I modules fail or act erratically
- Lost-communication codes in several modules
Inspection / repair
- Difficulty: hard
- DIY: shop recommended
What Pro shows you for U009B
Before you go to the garage: roughly what the repair costs, how long it takes and which components are involved.
- Repair cost (estimate)(visible in Pro mode)
- Labour time(visible in Pro mode)
- 2 affected components(visible in Pro mode)
- 1 warning for driving and inspection(visible in Pro mode)
See repair cost, labour time and components?
One key opens all tools by Fabian Brose.