Description

National Instruments CAN 2009 User Manual – OEM Factory Documentation

I’ve torqued more head bolts than most techs have had hot meals, and I’ve seen diag sessions go sideways because someone grabbed a third-party summary instead of the real protocol specs. That’s why I’m telling you: if you’re working with National Instruments CAN 2009 User Manual on any NI hardware, this is the source. Published December 2009, 334 pages, straight from the factory floor. No aftermarket edits, no condensed reprints – just the OEM document that tells you exactly how the KWP2000, UDS, and OBD services are supposed to behave. You want to diagnose a CAN bus correctly? Start here.

KWP2000, UDS, OBD: Protocol Coverage in One Manual

Chapter 1 gives you the full breakdown of each diagnostic service format. Key Word Protocol 2000 – that’s the older standard you still see on European cars – and Unified Diagnostic Services (UDS), which is the modern replacement. On-Board Diagnostics (OBD) for emissions systems. Each protocol has its own connect/disconnect, seed/key, read/write memory, and trouble code procedures. Page 26? No, that’s not the torque spec I’d give you on a head bolt, but it’s where the diagnostic service format tables start. You need to know the exact byte sequence for a GetSeed request? It’s in there. The manual doesn’t guess; it prints the hex frames you send over the CAN bus. I’ve got zero patience for techs who skip that part and then wonder why the ECU won’t unlock.

Does This Manual Cover the CAN Bus Physical Layer?

Not directly – it assumes you already have the CAN hardware running. This is the software/command-set layer. But if you’re using NI CAN interfaces (NI-CAN, NI-XNET), the installation and configuration steps in Chapter 2 will save you from plugging in a cable and hoping. Hardware and software requirements are listed, including LabVIEW Real-Time (RT) configuration. No vague recommendations. If you need the physical wiring specs, grab a separate CAN physical layer spec, but for the diagnostic commands, this manual is the only game in town.

334 Pages of Factory Documentation – No Reprints

That page count matters. 334 pages means every VI in the LabVIEW API gets its own description – input, output, format, purpose. Chapter 5 alone has more than 70 VIs listed, from Close Diagnostic.vi to OBD Request Vehicle Information.vi. Each one is documented with the exact wire terminals and data types. You won’t find a single “see generic example” cop-out. This is the kind of documentation you pay for when you buy NI hardware – except now you can get it standalone. I’ve seen Hitachi ZAXIS225US-3 2007 Operators Manual | OEM Factory Specs and Schneider Electric Masterpact NW08-63 User Manual – Factory Specs on this site; same level of detail. When you need the actual spec, you go OEM.

LabVIEW API: The VIs You Need for KWP2000 and UDS

Chapter 5 is the meat. If you’re writing diagnostic code in LabVIEW, you need the VI list and the exact property nodes. Table 5-1 lists every VI. Want to read DTCs by status? Use ReadDTCByStatus.vi. Need to reset an ECU? ECUReset.vi. Each one has a format section showing the connector pane and the required inputs. I’ve debugged UDS sessions where the problem was a wrong byte order in the routine control command – the manual’s description of UDS RoutineControl.vi saved me two hours of staring at a logic analyzer. The General Functions section includes Diag Set Property.vi and Diag Get Property.vi for tweaking transport layer parameters. If you skip reading those, you’ll be guessing timeouts. Astra Veicoli Industriali HD8 2005 User Manual – OEM Factory Specs has similar rigor for a different system.

Understanding the Diagnostic Service Format Before You Write Code

Page 1? No. Page 26 is where the service format tables live. But the real warning label is the WARNING REGARDING USE OF NATIONAL INSTRUMENTS PRODUCTS in the Important Information section. That’s not fluff – it’s a legal and safety notice about using these products in critical systems. If you’re developing a diag tool for a customer vehicle, you need to understand the liability. The manual also includes compliance notes. Don’t ignore that page. I’ve seen techs rush into coding, skip the transport protocol tweaks in Chapter 4, and then wonder why the connection drops. The manual’s section on “Tweaking the Transport Protocol” tells you exactly how to adjust block sizes and timeouts for KWP2000 and UDS. If you don’t set those right, the ECU will time you out. Period.

Is this manual good for diagnosing CAN hardware failures, or just software?

It covers the software command set. For hardware troubleshooting, you need a separate CAN physical layer spec. This manual tells you what commands to send, not how to fix a shorted transceiver.

Does it include wiring diagrams or pinouts for NI CAN interfaces?

No. Pinouts are in the NI CAN hardware manuals. This User Manual focuses on the Automotive Diagnostic Command Set API. For installation, it lists hardware requirements but assumes standard NI CAN modules.

Can I use this manual with third-party CAN interfaces, like Kvaser or Peak?

Technically no. The command set is designed for NI hardware and NI software stacks (LabVIEW, LabWindows/CVI). The protocol definitions (KWP2000, UDS, OBD) are universal, but the VI wrappers are NI-specific. If you’re writing raw CAN frames yourself, you can adapt the service formats – but you’ll need the NI documentation to understand the exact framing. The manual also references NI’s Transport Protocol layers that may not exist on other hardware.

What about OBD-II generic codes? Does this manual cover them?

Yes, Chapter 5 has a full OBD (On-Board Diagnostics) Services section. It covers all service IDs from OBD Request Supported PIDs to OBD Request Vehicle Information. The manual includes example request/response formats for emission-related DTCs, freeze frame data, and monitor test results. If you’re building a generic OBD-II scanner on NI hardware, this is your reference.

If you’re serious about diagnostic development on NI hardware, you stop guessing and get the factory documentation. Automotive Industry Overview covers the bigger picture of CAN diagnostics in the industry, but when you need to code a specific service, this manual is the only source that hasn’t been condensed or misinterpreted. Manual Transmission? Not relevant – stay focused on the electronic side. Access the Factory Manual now and keep it on your bench next to the oscilloscope.