11898-1协议

ICS43.040.15Ref.No.ISO11898-1:2003/Cor.1:2006(E)©ISO2006–AllrightsreservedPublishedinSwitzerlandINTERNATIONALSTANDARDISO11898-1:2003TECHNICALCORRIGENDUM1Published2006-05-15INTERNATIONALORGANIZATIONFORSTANDARDIZATION•МЕЖДУНАРОДНАЯОРГАНИЗАЦИЯПОСТАНДАРТИЗАЦИИ•ORGANISATIONINTERNATIONALEDENORMALISATIONRoadvehicles—Controllerareanetwork(CAN)—Part1:DatalinklayerandphysicalsignallingTECHNICALCORRIGENDUM1Véhiculesroutiers—Gestionnairederéseaudecommunication(CAN)—Partie1:CoucheliaisondedonnéesetsignalisationphysiqueRECTIFICATIFTECHNIQUE1TechnicalCorrigendum1toISO11898-1:2003waspreparedbyTechnicalCommitteeISO/TC22,Roadvehicles,SubcommitteeSC3,Electricalandelectronicequipment.Page2,4.2:Replacedefinitionfor“bitstuffing”with:“framecodingmethodprovidingbusstatechangesrequiredforperiodicresynchronizationwhenusinganNRZbitrepresentation”Page2,4.8:Replacedefinitionfor“contention-basedarbitration”with:content-basedarbitrationCSMAarbitrationprocedureresolvingbus-contentionwhenmultiplenodessimultaneouslyaccessthebusISO11898-1:2003/Cor.1:2006(E)2©ISO2006–AllrightsreservedPage3,4.13:Delete:“NRZ”Page3,4.16:Replacedefinitionfor“receiver”with:anynodethatisnottransmitterwhenthebusisnotidlePage4,Clause5:Deleteafter“IDEidentifierextension”:flagPage4,Clause5:Addonthenextlineafter“RTRremotetransmissionrequest”:SAPserviceaccesspointPage5,6.1:Replace“contention-based”with:content-basedPage5,6.3:Replace“contention-based”with:content-basedPage6,6.12:Replacereference“(see13.1.4.3)”with:(see13.1.4.4)Page7,6.15:Replacethesecondsentencewith:Inthebusoffstate,anodeshallnotsendanydominantbit.ISO11898-1:2003/Cor.1:2005(E)©ISO2006–Allrightsreserved3Page8,Figure2:Replace“M-PC”with:M-PCIPage15,Table4:MoveTable4to8.4.2.3Page15,Figure4:Replacefiguretitlewith:Figure4—LLCremoteframePage24,10.4.2.2:Replacethirdparagraphwith:Ifanodewithapendingtransmissionsamplesadominantbitatthethirdbitofintermissionandiserroractiveorhasbeenthereceiverofthepreviousframe,withthenextbititshallstarttransmittingitsmessagewiththefirstbitofitsidentifierwithoutfirsttransmittingaSOFbitandwithoutbecomingreceiver.Page25,10.4.2.4:Replacethesecondsentenceofthesecondparagraphwith:Receiversshallacceptrecessiveanddominantbitsasreservedbitr0.Page27,10.4.4.2:Replacethefirstsentencewith:Twoformsoferrorflagmaybeused,theactiveerrorflagandthepassiveerrorflag,where⎯theactiveerrorflagshallconsistofsixconsecutivedominantbits,and⎯thepassiveerrorflagshallconsistofsixconsecutiverecessivebitsunlessitisoverwrittenbydominantbitsfromothernodes.andaddthefollowingtwosentences:Anerrorpassivenodetransmittingapassiveerrorflagwaitsforsixconsecutivebitsofequalpolarity,beginningatthestartofthepassiveerrorflag.Thepassiveerrorflagiscompletewhenthesesixequalbitshavebeendetected.Page28,10.4.5.1:Replace“overallflag”with:overloadflagISO11898-1:2003/Cor.1:2006(E)4©ISO2006–AllrightsreservedPage29,10.5:Replacethefirstsentencewith:TheframesegmentsSOF,arbitrationfield,controlfield,datafield,andCRCsequenceshallbecodedbythemethodofbitstuffing.Page30,Figure10:Replacefigurewith:Page30,Figure11:Replacefigurewith:Page30,10.7:Replacethereference“8.3.3”with:8.3.4Page31,10.8.4,10.8.6,and10.8.8:Replace“contention-based”with:content-basedPage31,10.8.5:Replacesecondsentencewith:AMACerrorframeshallbetransmittedasspecifiedin10.10.ISO11898-1:2003/Cor.1:2005(E)©ISO2006–Allrightsreserved5Page31,10.8.8:Replacesecondsentencewith:Withinonesystem,eachinformationshallbeassignedbyauniqueidentifier.Page33,10.11:Replace“Thestartofreactiveoverloadframesduetoconditiona)above”with:ThestartofLLC-requestedoverloadframesduetoconditiona)abovePage38,12.4.2.5:Replace“takeintoconsideration”inthesecondsentencewith:meetPage38,12.4.2.5:Delete:(bothshallbemet)Page38,12.4.2.5:Replacetheformulas1)and2)with:1)(_1,_2)min_22(13)PhaseSegPhaseSegbitPhaseSegtdftt≤××−2)20SJWbittdft≤×Page43,13.1.4.4:Replacethesecondandthirdparagraphswith:Anodewhichisinthebusoffstateshallhavenoinfluenceonthebus.Itshallnotsendanyframesnorsendacknowledgement,errorframes,overloadframes.Whethersuchanodeacceptsframesfromthebusdependsontheimplementation.Anodewhichisinthebusoffstatemaybecomeerror-active(nolongerbusoff)withitserrorcountersbothsettozero(0)afterhavingmonitoredonehundredandtwenty-eight(128)occurrencesofeleven(11)consecutiverecessivebitsonthebus(seeFigure16).Thestartoftherecoverysequencemaybeinitiatedbysoftwareorhardwaredependingontheimplementation.ISO11898-1:2003/Cor.1:2006(E)6©ISO2006–AllrightsreservedPage43,13.1.4.4:Replacereference“6.14”intheNOTEwith:6.15Page44,Figure16:Replace“User_Request”with:Recoverysequence