您好,欢迎访问三七文档
当前位置:首页 > 商业/管理/HR > 质量控制/管理 > A-Comparison-of-J1939-&-ISO15031
AComparisonofJ1939&ISO15031JeffCraigVectorCANtech,Inc.Agenda–Diagnostic Standards–Physical Interface–Connectors–Terminology–Protocol Overview–Fault CodesHistory Lesson•What is this??•1980’s Automotive Diagnostic ToolMajor DifferencesJ1939 (MD & HD Truck)ISO 15031 (Pass Car & LD Vehicles)All standards defined in SAE J1939 partsISO 15031 is harmonized with several SAE stds.29 bit identifiers11 bit identifiersUsed for normal communications & diagnosticsUsed only for diagnosticsFault status broadcast regularly (e.g. DM1)No broadcast messagesPrimary functionality defined using Diagnostic Messages (DMs)Primary functionality defined using unique communication Service IDs (SIDs)3 byte fault codes + occurrence counter3 byte fault codesFour warning lamps definedOne warning lamp defined250 Kbps bus speed500 Kbps bus speedNine pin diag connector standard(J1939‐13)Sixteen pin diagconnector standard (ISO15031‐3 /J1962)Diagnostic StandardsDiagnostic Standards: Car/Truck –SAE/ISOSAEISOPass Car & LD VehJ1930 ‐terms & defnsJ1962 ‐connectorJ1978 ‐scan toolJ1979 ‐diag servicesJ2012 ‐fault codesJ2186 ‐link securityJ2534 ‐pass thruJ1699 ‐OBD conformanceISO11898 (5 parts) ‐CANISO15765 (4 parts) ‐Diagnostics on CANISO15031 (7 parts) ‐Legislated OBD on CANMD & HD VehJ1939 (Multiple parts)J2403 ‐terms & defnsN/AInsomecasesmultiplestandardswillbemixedonthesamevehicleApples –to ‐ApplesOSI LayerMD & HD Standards & OBD LegislatedPass Car & LD OBD LegislatedN/ADiagnosticConnectorSAE J1939‐13ISO 15031‐37ApplicationSAE J1939‐71/73SAE J1939‐81ISO 15031‐5(SAE J1979)6PresentationISO 15031‐5(SAE J1979)5SessionISO 15765‐44TransportProtocolSAE J1939‐21ISO 15765‐23NetworkLayerSAE J1939‐31ISO 15765‐42Data LinkSAE J1939‐21(ISO 11898‐1)ISO 15765‐4(ISO 11898‐1)1Physical LayerSAE J1939‐11/15ISO 15765‐4(ISO 11898‐2)ISO 15031 Mapping to SAE StandardsHARMONIZEDISO15031J1930Terms&DefinitionsSAERecommendedPracticeJ1962DiagnosticConnectorJ1978DiagToolReqmntsJ1979DiagnosticServicesJ2012FaultCodeDefinitionsJ2186DataLinkSecurity234567Physical InterfacePhysical InterfaceJ1939 –11 or 15ISO 15031‐3, ISO 11898‐2 & ISO 15765‐4250 Kbps 500 KbpsTwisted Shielded Pair (11)Twisted Unshielded Pair (15)Twisted Pair –no shieldMax 30 ECUs (11)Max 10 ECUs (15)No Max Defined40 m Total NW Length40 m @ 1Mbps –Longer allowed at lower speeds1 m Stub Length (11)3 m Stub Length (15).3 m @ 1Mbps –Longer allowed at lower speedsConnectorsConnectors12345678910111213141516ISO15031–3(J1962)J1939-13ABCDEFGHJTerminologyTerminology –Just a FewJ1939ISO 15031ACL = Address ClaimingBAM = Broadcast Announce MessageDM = Diagnostic MessageDP = Data PageDTC = Diagnostic Trouble CodeECU = Electronic Control UnitEDP = Extended Data PageFMI = Failure Mode IdentifierNACK = Negative AcknowledgementPDU = Protocol Data UnitPG = Parameter GroupPGN = Parameter Group NumberSLOT = Scaling, Limit, Offset & TransferSPN = Suspect Parameter NumberDLC = Data Length CodeDTC = Diagnostic Trouble CodeECM = Engine Control ModuleECU = Electronic Control ModuleFTB = Failure Type ByteKWP = Key Word Protocol (ISO 14230)MIL = Malfunction Indicator LampNRC = Negative Response CodePCI = Protocol Control InformationPID = Parameter ID (similar to DID or LID)SID = Service IDProtocol OverviewCAN Message Structure11bitor29bitStandard CAN Format: 11‐Bit Identifier•Usage for OBD: ECU IdentificationFunctional Request ID for OBD diagnostic requests (source address not required since only one diagnostic tester is allowed on the bus at one time)Source ECU ID for diagnostic responsesMost OEMs have their own ID assignment standardsJ1939 Extended CAN Format: 29‐Bit Identifier•Three Components –as defined by J1939:Message PriorityParameter Group Number (Defines the data in the DATA area –SAE standardized & proprietary PGNs possible) Source Address•Interpretationof29BitCANExtendedIdentifierinJ1939•PDUFormat0xF0definesmessageasPeer-to-Peer.PDUSpecificwillbeaDestinationAddress•PDUFormat=0xF0identifiesmessageasbroadcast.PDUSpecificwillbeaGroupExtensionEDP(1Bit)Priority(3Bit)DP(1Bit)PDUFormat(8Bit)PDUSpecific(8Bit)SourceAddress(8Bit)Bit28Bit0PGNJ1939 29‐Bit Identifier DefinedTesterECUCyclicDiagnosticMessages(e.g.DM1)J1939[[Prio+RequestPGN+DestAddr+SrcAddr][RequestedPGN]]-or-ECUTesterISO15031[[TargetID][RequestedService+RequestedData]][[SourceID][RequestedServiceID+RequestedData]](Servicescanbedatarequests,faultcoderequests,outputcontrol,specialtestrequests,securityaccess,reprogrammingrequests,etc.)[[Prio+RequestedPGN+DestAddr+SrcAddr][PGNData]]Diagnostic Message Structure ComparisonFault Codes87654321876543218765432187654321DTCByte1Byte2Byte3Byte4SPNFMICMOCMSBLSBLowByteSPNMidByteSPNMSBLSB3MSBofSPN+FMIConversionMethod+OccuranceCountConversionMethodBitAffectstheInterpretationoftheByteOrderingoftheSPN(0since1996)J1939 Diagnostic Trouble CodeISO 15031 Diagnostic Trouble Code876543218765432187654321DTCByte1Byte2Byte3SAECodeNumberFTB1stCharacterofSAECode(P,C,B,U)2ndCharacterofSAECode(0,1,2,3)3rdCharacterofSAECode(0-F)4thCharacterofSAECode(0-
本文标题:A-Comparison-of-J1939-&-ISO15031
链接地址:https://www.777doc.com/doc-6169237 .html