Seven pins vs. five.
A lot of people will tell you an OBD scanner, but those can leave a lot to be desired... a good system, such as NexIQ ProLink IQ is a much better and more in-depth scan tool (plus it can scan OBDII, SAE J1708, and SAE J1939), but is extremely expensive. The best option would be a computer with the actual diagnostic software for that engine, but car manufacturers typically release that only to dealerships.
SAE J2210, which outlined the specifications for a certain type of vehicle communication protocol, was superseded by SAE J1939. The J1939 standard provides a more comprehensive framework for communication among vehicle components, particularly in heavy-duty vehicles, and is widely adopted in the industry for its robustness and scalability.
If there was no J1939 activity at all, nothing would happen... that's a multiplexed system, and everything on those is run through the ECM - either directly or through the chassis nodes. Is it telling you there's an abnormal update rate? If so, you've probably got a bad wire to something in your instrument cluster.
The service center of any Peterbilt dealership can provide those. You're really better off just to get an SAE J1708 compatible code reader, though... I use a NexIQ ProLink... less expensive ones are available. Flash codes are often very vague... it might tell you, for example, that there's a low coolant warning, but not whether there's a fault in the coolant sensor circuit or not.
Need year, make, and model. A semi truck from the 1970s is going to look a whole lot different than a current production truck with an SAE J1939 multiplex system.
Not unless it's an electronically actuated PTO system which is run through the ECM. Which is a bit unlikely, as a 1999 MY truck predates SAE j1939 multiplexing.
The fault code MID 137 for Volvo trucks typically refers to an issue with the communication between the engine control module (ECM) and the brake control module (BCM). This code indicates a problem with the J1939 data link, which is the communication network used by various modules in the vehicle. To diagnose and resolve this issue, technicians would need to perform a thorough inspection of the wiring, connectors, and components involved in the J1939 network, as well as potentially update software or replace faulty modules.
Traditional hot wiring doesn't work, especially in the cars which have chipped keys. Even in those which don't, SAE J1939 multiplexing makes traditional hot wiring ineffective.
7 per "Electronic Diesel Engine Diagnosis". Start of Frame Arbitration Field Control Field Data Field CRC Field Ack field End of Frame
You start by figuring out what's wrong with it. What you're talking about could be as simple as replacing the sealed beam, or it could get into a problem with the J1939 multiplexing system, or anything in-between. You need to diagnose before you'll know how to repair it.
These protocols are higher level CAN bus protocols. They both use the CAN 2.0B standard for the physical and data link layer. Each protocol, however, has different standards for the higher layers in the OSI model, and thus the way in which data is transmitted and interpreted is unique to each.
I want to say it's an SAE J1939 port, but I think that's wrong, because that year should only have the five pin port... it'll either be on the bottom of the dash on the driver side, or on the floor to the left of and behind the driver seat.