关闭

关闭

封号提示

内容

首页 SEMI E04 - 0699.pdf

SEMI E04 - 0699.pdf

SEMI E04 - 0699.pdf

上传者: alai7150 2014-03-30 评分1 评论0 下载2 收藏0 阅读量36 暂无简介 简介 举报

简介:本文档为《SEMI E04 - 0699pdf》,可适用于电子通讯领域,主题内容包含SEMIESEMI,SEMIESEMIEQUIPMENTCOMMUNICATIONSSTANDARDMESSAGETRANSFER(SECSI)Th符等。

SEMIESEMI,SEMIESEMIEQUIPMENTCOMMUNICATIONSSTANDARDMESSAGETRANSFER(SECSI)ThisstandardwastechnicallyapprovedbytheGlobalInformationControlCommitteeandisthedirectresponsibilityoftheNorthAmericanInformationControlCommitteeCurrenteditionapprovedbytheNorthAmericanRegionalStandardsCommitteeonFebruary,InitiallyavailableonSEMIOnLineMaytobepublishedJuneOriginallypublishedinpreviouslypublishedJanuaryIntroductionRevisionHistoryThisisthefirstmajorrevisionsincetheoriginalreleaseofSECSIinVerylittleoftheoriginalintentofSECSIhasbeenaltered,althoughthereareafewsignificantadditionsThechangesaresummarizedinAppendixThisspecificationhasbeendevelopedincooperationwiththeJapanElectronicIndustryDevelopmentAssociationCommitteeonEquipmentCommunicationsScopeTheSECSIstandarddefinesacommunicationinterfacesuitablefortheexchangeofmessagesbetweensemiconductorprocessingequipmentandahostSemiconductorprocessingequipmentincludesequipmentintendedforwafermanufacturing,waferprocessing,processmeasuring,assemblyandpackagingAhostisacomputerornetworkofcomputerswhichexchangeinformationwiththeequipmenttoaccomplishmanufacturingThisstandardincludesthedescriptionofthephysicalconnector,signallevels,datarateandlogicalprotocolsrequiredtoexchangemessagesbetweenthehostandequipmentoveraserialpointtopointdatapathThisstandarddoesnotdefinethedatacontainedwithinamessageThemeaningofmessagesmustbedeterminedthroughsomemessagecontentstandardsuchasSEMIEquipmentCommunicationsStandardE(SECSII)IntentThisstandardprovidesameansforindependentmanufacturerstoproduceequipmentandorhostswhichcanbeconnectedwithoutrequiringspecificknowledgeofeachotherLayeredProtocolTheSECSIprotocolcanbethoughtofasalayeredprotocolusedforpointtopointcommunicationThelevelswithinSECSIarethephysicallink,blocktransferprotocol,andmessageprotocol(SeeRelatedInformationR)SpeedItisnottheintentofthisstandardtomeetthecommunicationneedsofallpossibleapplicationsForexample,thespeedofRSmaybeinsufficienttomeettheneedsoftransferringmassamountsofdataorprogramsinashortperiodoftime,suchasmightberequiredbyhighspeedfunctionaltestapplicationsNetworkSupportThemethodbywhichblocksofdataareroutedtoapieceofequipmentorfindtheirwaybacktotheproperhostapplicationisnotspecifiedbySECSIInanetwork,therolesofhostandequipmentmightbeassumedbyanypartyinthenetworkInthissituation,oneendofthecommunicationslinkmustassumetheroleoftheequipmentandtheothertheroleofthehostApplicableDocumentsElectronicsIndustriesAssociationStandardsEIARSCInterfacebetweenDataTerminalEquipmentandDataCommunicationEquipmentEmployingSerialBinaryDataInterchangeEIARSBSynchronousSignalingRatesforDataTransmissionEIARSSignalQualityatInterfaceBetweenDataProcessingTerminalEquipmentandSynchronousCommunicationEquipmentforSerialDataTransmissionEIARSElectricalCharacteristicsofBalancedVoltageDigitalInterfaceCircuitsEIARSElectricalCharacteristicsofUnbalancedVoltageDigitalInterfaceCircuitsEuropeanComputerManufacturingAssociationECMATC"NetworkLayerPrinciples,"FinalDraft(April,)JapaneseIndustrialStandardsCommitteesJISC"TheInterfacebetweenDataCircuitTerminatingEquipment(DCE)andDataTerminalEquipment(DTE)(pinInterface)"InternationalOrganizationforStandardizationEIAEngineeringDepartment,StandardsSalesOffice,EyeStreet,NW,Washington,DCEuropeanComputerManufacturingAssociation,RueduRhone,Geneva,SwitzerlandJapaneseStandardsAssociation,,AkasakaChome,Minatoku,Tokyo,JapanANSI,Broadway,NewYork,NYSEMIESEMI,ISODataCommunications,InterfaceConnectorsandPinAssignmentSEMISpecificationsSEMIESEMIEquipmentCommunicationsStandardMessageContent(SECSII)SEMIESEMIFacilitiesInterfaceSpecificationFormatOverviewofSECSITheSECSIstandarddefinespointtopointcommunicationofdatautilizingasubsetoftheinternationalstandardknownintheUSAasEIARSCandinJapanasJISCfortheconnectorandvoltagelevelsTheactualtransmissionconsistsofbitbytessentseriallywithonestartandonestopbitThecommunicationisbidirectionalandasynchronous,butflowsinonedirectionatatimeThedirectionisestablishedbyspecialcharactersandahandshake,afterwhichthedataitselfissentDataissentinblocksofbytesorlessEachblockconsistsofabyteheaderfollowedbydataAmessageisacompleteunitofcommunicationinonedirectionandconsistsofto,blocksEachblockheadercontainsinformationforidentifyingtheblockaspartofaspecificmessageMessagesarepairedbyarequestanditsreplywhichtogetherarecalledatransactionStructureofDocumentThisdocumentisdividedintosectionswhichcorrespondtomajoraspectsofthestandardThesectionsoutlinerequirementsaswellasimplicationsoftherequirementsThestandardmaybeimplementedinavarietyofways,dependinguponthecomputerenvironmentwhereitisplacedImplementationisnotpartofthestandardInformationwhichmaybeusefulforimplementationisincludedintheformofRelatedInformationTerminologyThefollowingbriefdefinitionsrefertosectionsprovidingfurtherinformationACK"CorrectReception"handshakecode(SeeSection)applicationsoftwarethesoftwareperformingthespecifictaskoftheequipmentorthehostblockheaderplusuptobytesofdata(SeeSections,)blocklengththenumberofbytessentintheblocktransferprotocol(SeeSection)blocknumberabitfieldintheheaderfornumberingblocksinamessage(SeeSections)characterabytesentontheSECSIserialline(SeeSection)checksumabitnumberusedtodetecttransmissionerrors(SeeSection)communicationfailureafailureinthecommunicationlinkresultingfromafailedsend(SeeSection)deviceIDabitfieldintheheaderusedtoidentifytheequipment(SeeSection)Ebitabitintheheaderidentifyingthelastblockofamessage(SeeSection)ENQ"RequesttoSend"handshakecode(SeeSection)EOT"ReadytoReceive"handshakecode(SeeSection)equipmenttheintelligentsystemwhichcommunicateswithahostexpectedblocktheblockofamessagewhichisexpectedbythemessageprotocol(SeeSection)headerabytedataelementusedbythemessageandtransactionprotocols(SeeSection)hosttheintelligentsystemwhichcommunicateswiththeequipmentlengthbytethecharacterusedtoestablishtheblocklengthduringtransmission(SeeSection)linecontrolaportionoftheblocktransferprotocol(SeeSection)mastertheblocktransferdesignationfortheequipment(SeeSection)messageacompleteunitofcommunication(SeeSection)messageIDabitfieldintheheaderusedintheprocessofmessageidentification(SeeSections,)multiblockmessageamessagesentinmorethanoneblock(SeeSections,)NAK"lncorrectReception"handshakecode(SeeSection)openmessageamultiblockmessageforwhichnotalloftheblockshavebeenreceived(SeeSection)opentransactionatransactioninprogress(SeeSection)primarymessageamessagewithanoddnumberedmessageIDAlsothefirstmessageofatransaction(SeeSection)SEMIESEMI,primarysecondaryattributetheleastsignificantbitofthelowermessageIDwhichindicateswhetherablockbelongstoaprimaryorsecondarymessageRbitabitintheheadersignifyingthedirectionofthemessage(SeeSection)receivertheendoftheSECSIlinkreceivingamessage(SeeSection)replytheparticularsecondarymessagecorrespondingtoaprimarymessage(SeeSection)replylinkingtheprocessofformingatransactionoutofaprimaryandasecondarymessage(SeeSection)retrycountthenumberofunsuccessfulattemptstosendablockintheblocktransferprotocol(SeeSection)RTYtheretrylimitorthenumberoftimestheblocktransferprotocolwillattempttoretrysendingablockbeforedeclaringafailedsend(SeeSection)secondarymessageamessagewithanevennumberedmessageIDAlsothesecondmessageofatransaction(SeeSection)sendertheendoftheSECSIlinksendingmessage(SeeSection)slavetheblocktransferdesignationforthehost(SeeSection)systembytesabytefieldintheheaderusedformessageidentification(SeeSection)Treceiveintercharactertimeoutintheblocktransferprotocol(SeeSection)Tprotocoltimeoutintheblocktransferprotocol(SeeSection)Treplytimeoutinthemessageprotocol(SeeSections,)Tinterblocktimeoutinthemessageprotocol(SeeSection)transactionaprimarymessageanditsassociatedsecondarymessage,ifany(SeeSection)Wbitabitintheheadersignifyingthatareplyisexpected(SeeSection)CouplingCouplingreferstothephysicalinterfaceattheequipmentThehostwillprovidecompatiblesignalsatthispointNorestrictionsareimpliedforanyinterfaceotherthanforequipmentcoveredbythisstandardElectricalInterfaceTheconnectionwillincludeaserialinterfaceaccordingtoEIAStandardRSCforinterfaceTypeE,fullduplexcommunication,modifiedbythedeletions,additionsandexceptionsdescribedinthissectionConnectorEitherthepinorpinconnectordescribedintheEIARSmaybeusedInthecaseofthepinconnectorafemaleconnectorwillbemountedontheequipmentandamaleconnectorwillbemountedonthecablefromthehostInthecaseofthepinconnectorthemaleconnectorwillbemountedontheequipmentandafemaleconnectorwillbemountedonthecableTheconnectorontheequipmentwillhavefemalethreadedjackscrewlocksNOTE:SuitablepinconnectorsknownasType"D"aresimilartoAmphenolMINRACserieswithjackscrewlocksSuitablepinconnectorisalsoType"D"withjackscrewlocksItisthetypecommonlyimplementedondesktopandnotebookPCsSignalPinsPinsontheconnectorhavefunctionsasdefinedinTablePins,,,andofthepinconnectororpins,,andofthepinconnectorarerequiredforallequipmentcomplyingwithSECSIWhenusingapinconnector,thetwopowersupplypins,and,areoptionalasindicatedAnyotherpins,ifused,shallcomplywiththeRSCstandardTableSignalConnectionsPinPinRSCCircuitCircuitDescriptionAAShieldBADatafromEquipmentBBDatatoEquipmentABSignalGroundtovolts(optforthepinconnector)tovolts(optforthepinconnector)LogicLevelsForthesignalpinsand,thelogiclevelwillbeavoltagelessthanvoltsandthelogiclevelwillbeavoltagegreaterthanvoltsVoltageswillneverexceedvoltsThesevaluescorrespondtothosespecifiedbytheRSCstandardPowerSuppliesWhenusingapinconnector,pinsandareoptionalpowersuppliesfordrivingexternalisolationcircuitsWhenprovided,bothshallbepresentandmustbeabletosupplyatleastmA(SeeRelatedInformationRforexampleuse)SEMIESEMI,DataRateThesupporteddataratesonsignalpinsshallbe,,,,andbaudThesamedatarateshallapplyfordatasenttoandfromtheequipmentThedatarateshallbecontrolledtobetterthan(SeeRSBandRS)Optionalratesof,andbaudmaybesuppliedifdesiredPhysicalMediumTheconnectionwiththehostmayinvolveanymediumthatprovidestherequiredRSCquality,signallevelsanddatarateattheequipmentconnectorThequalityofsignalshouldbesuchthattheeffectivebiterrorrateislessthanThisratecanbeachievedeasilywithhardwiredsystemsThedistancelimitsspecifiedinRSCapplyonlytosystemsusingthewiringtechniquedescribedinRSCSinceanymethodmaybeusedinSECSIaslongasRSCsignalsaresuppliedattheconnector,thedistanceandisolationisdependentuponthedesignofthephysicalmediumwhichisexternaltotheSECSIstandard(SeeRelatedInformationR)CharacterStructureCharactersDatawillbetransmittedorreceivedinaserialbitstreamofbitspercharacteratoneofthespecifieddataratesThestandardcharacterhasonestartbit(),databitsandonestopbit()AllbittransmissionsareofthesamedurationThedatabitsarenumberedfromtointheordersent(seeFigure)ThetimingbetweencharactersisasynchronouswithrespecttothedatarateThedatabitsmaybeanyarbitrarycodeTheeightdatabitswillhereafterbereferredtoasabyteFigureCharacterStructureWeightedCodesForbyteshavingweightedcodes,bitoneistheleastsignificantandbiteightisthemostsignificantThemostcommonweightedcodeisbinaryNonWeightedCodesForcodeswithoutnumericvaluesuchasASCII,thebitnumberswillbeusedastheentryintoastandardcodetableforinterpretationofthecodeSECSIperformsnoparityorotherverificationofthecontentsofindividualbytesBlockTransferProtocolTheprocedureusedbytheseriallinetoestablishthedirectionofcommunicationandprovidetheenvironmentforpassingmessageblocksiscalledtheblocktransferprotocolMostoftheprotocolisaccomplishedwithahandshakeofsinglebytesWhenbothendsofthelinetrytosendatthesametime,aconditionknownaslinecontentionexistsTheprotocolresolvescontentionbyforcingoneendoftheline,designatedastheslave(alwaysthehost),topostponeitstransmissionandenterthereceivemodeRetransmissionofblocksisusedtocorrectcommunicationerrorsTheblocktransferprotocolisshowninflowchartforminFigure,anddescribedbelowAdditionalinformationisalsocontainedinRelatedInformationRandRHandshakeBytesThefourstandardhandshakecodesusedintheblocktransferprotocolareshowninTableThethreeletternames,ENQ,EOT,ACK,andNAKcorrespondtotheASCIIcodehavingthesamepatternTableHandshakeCodesNameCodebbbFunctionENQRequesttoSendEOTReadytoReceiveACKCorrectReceptionNAKIncorrectReceptionTimeoutParametersTimeoutsareusedtodetectcommunicationsfailuresAtimeoutoccurswhenthemeasuredtimebetweentwoeventsexceedsapredeterminedlimitGenerally,thelengthoftimethatmustpassbeforeitcanbeassumedthatanerrorhasoccurreddependsupontheparticularsystemsinvolvedThetimerequiredinonesituationmightbeexcessivelylonginanotherThus,thetimeoutvaluesmustbe"tuned"tomeettheapplicationIntheblocktransferprotocol,therearetwosituationsrequiringtimeoutvaluesThetwotimeoutvaluesarecalledparametersTandTInterCharacterTimeout,TTheintercharactertimeout,T,limitsthetimebetweenreceiptofcharacterswithinablockafterthelengthbytehasbeenreceivedanduntilthereceiptofthesecondchecksumbyteProtocolTimeout,TTheprotocoltimeout,T,limitsthetimebetweensendingENQandreceivingEOT,sendingEOTandreceivingthelengthbyte,andsendingthesecondchecksumbyteandreceivinganycharacterSEMIESEMI,RetryLimit,RTYTheretrylimit,RTY,isthemaximumnumberoftimestheBlockTransferProtocolwillattempttoretrysendingablockbeforedeclaringafailedsend(SeeSection)MasterSlaveThemasterslaveparameterisusedintheresolutionofcontention(seeSection)ThehostisdesignatedastheslaveTheequipmentisdesignatedasthemasterThisconventionisbasedupontheassumptionthattheequipmentislessabletostoremessagesthanthehostBlockLengthsTheunsignedintegervalueofthefirstbytesentafterreceiptofEOTisthelengthoftheblockbeingsentThelengthincludesallthebytessentafterthelengthbyte,excludingthebytesofthechecksumThemaximumblocklengthallowedbySECSIisbytes,andtheminimumisbytesChecksumThechecksumiscalculatedasthenumericsumoftheunsignedbinaryvaluesofallthebytesafterthelengthbyteandbeforethechecksuminasingleblockThechecksumissentasbitsintwobytesfollowingthelastbyteoftheblockdataThehighordereightbitsofthechecksumwillbesentfirst,followedbythelowordereightbitsThechecksumisusedbythereceivertocheckfortransmissionerrorsThereceiverperformsthesamechecksumcalculationonthereceivedheaderanddataAlgorithmTheoperationoftheblocktransferprotocolisbestunderstoodbyfollowingthelogicflowinFigureThisflowchartdepictstheoperationofthefivestatesoftheprotocolReceive,Idle,SendLineControl,andCompletionTheflowchartshowninFigureisnotmeanttoimplythataparticularimplementationisrequiredunderthisstandardHowever,anySECSIblocktransferprotocolimplementationmustincludeallthelogicdescribedinFigureThesamealgorithmisexecutedoneachendoftheSECSIcommunicationslinkIdleStateBothendsofthecommunicationslinkareassumedtostartintheIdlestateTherearetwoprimaryactivitiesoftheprotocolsignifiedbythetwoexitsfromtheIdlestateTheseare:ASENDamessageblockistobesentBRECEIVEtheotherendofthecommunicationslinkhasamessageblocktosendLineControlThelinecontrolsectionestablishesthetransmissiondirection,resolvescontention,andhandlesretriesWhenanENQisreceivedintheIdlestate,theLineControlrespondswithanEOTiftheBlockTransferProtocolisreadytoreceiveTheBlockTransferProtocolthengoestotheReceivestateIfamessageblockistobesent,thenanENQissentIfanEOTisreceivedinresponsetotheENQwithinthetimelimitT,theBlockTransferProtocolgoestotheSendstateIftheslavereceivesanENQinresponsetotheENQ,contentionhasoccurredTheslavepostponesthesendofitsblockunt

类似资料

编辑推荐

《人类简史》读后感2000字.docx

2017国考申论.docx

博士毕业论文写作的十个策略.docx

《合法性与正当性》中对魏玛时代的理论危机解读.docx

中国戏曲音乐的艺术特征分析.docx

职业精品

精彩专题

中秋节除了赏月,你还想怎么过?

“仰头望明月,寄情千里光”,算算你有多久没回家了。庆幸这个中秋节赶上了国庆节,不用悲伤“故乡再无春夏,只有秋冬”,独自一人赏月,8天长假,回家一趟,妥妥的!

用户评论

0/200
    暂无评论
上传我的资料

精选资料

热门资料排行换一换

  • A theory of bind…

  • 神经科学百科全书.pdf

  • 高德拉特-目标.txt

  • [二十世纪儒学研究大系.10.儒…

  • [二十世纪儒学研究大系.09.儒…

  • [二十世纪儒学研究大系.08.儒…

  • [二十世纪儒学研究大系.07.儒…

  • [二十世纪儒学研究大系.13.儒…

  • [二十世纪儒学研究大系.16.儒…

  • 资料评价:

    / 20
    所需积分:1 立即下载

    意见
    反馈

    返回
    顶部