中文AXOS_8_4700924_02

合集下载

Ryacas0包的说明信息说明书

Package‘Ryacas0’January12,2023Version0.4.4Title Legacy'Ryacas'(Interface to'Yacas'Computer Algebra System)Maintainer Mikkel Meyer Andersen<*************.dk>Encoding UTF-8Description A legacy version of'Ryacas',an interface to the'yacas'computer algebra system(<http: ///>).Depends R(>=3.3.0)Imports methods,Rcpp(>=0.12.0),stats,settings,xml2LinkingTo RcppSuggests devtools,exams,knitr,Matrix,pkgload,rmarkdown,igraph,testthatLicense GPL-2URL https:///r-cas/ryacas0,BugReports https:///r-cas/ryacas0/issuesRoxygenNote7.2.3VignetteBuilder knitrNeedsCompilation yesAuthor Mikkel Meyer Andersen[aut,cre,cph],Rob Goedman[aut,cph],Gabor Grothendieck[aut,cph],Søren Højsgaard[aut,cph],Grzegorz Mazur[aut,cph],Ayal Pinkus[aut,cph],Nemanja Trifunovic[cph](UTF-8part of yacas(src/yacas/include/yacas/utf8*))Repository CRANDate/Publication2023-01-1209:50:05UTC12Ryacas0-package R topics documented:Ryacas0-package (2)as.Sym.character (3)as.Sym.matrix (4)bodyAsExpression (4)Eval (5)getSyms (6)get_output_width (6)root (7)Ryacas_options (7)set_output_width (8)stripvar (8)syacas (9)Sym (9)yacas (10)yacasTranslations (14)yacas_evaluate (15)yacmode (16)y_ls (17)Index18 Ryacas0-package R interface to yacas computer algebra packageDescriptionRyacas0allows one to use the yacas computer algebra package entirely from within R.It takes an R expression,an R one line function or a yacas string and returns an R expression or a variety of other formats.It can be used for symbolic mathematics,exact arithmetic,ASCII pretty printing and R to TeX conversions.The main command is yacas and?yacas provides some information on installation and startup.DetailsThe following are sources of information on"Ryacas0":DESCRIPTIONﬁle library(help=Ryacas0)List of demoﬁles demo(package="Ryacas0")Demoﬁle demo("Ryacas0")Demo demo("Ryacas0-PrettyPrinter")Demo demo("Ryacas0-Function")Demo demo("Ryacas0-Sym")Demo demo("Ryacas0-Expr")List Vignettes vignette(package="Ryacas0")Vignette vignette("Ryacas0")This File package?Ryacas0as.Sym.character3 Helpﬁles?yacas,?yacasTranslations,?yacmode,?SymHelpﬁles-Windows?yacasInstallNews RShowDoc("NEWS",package="Ryacas0")Acknowledgements RShowDoc("THANKS",package="Ryacas0")Wish List RShowDoc("WISHLIST",package="Ryacas0")Home page https:///r-cas/ryacas0/NoteThere is a note in the helpﬁle of the yacas command that discusses a number of installation and startup issues.Examplesprint(yacas(expression(integrate(1/x,x))))print(yacas("Integrate(x)1/x"))x<-Sym("x");Integrate(1/x,x)acos(Sym("1/2"))as.Sym.character Convert character vector to yacas objectDescriptionSimple and raw conversion to yacasUsage##S3method for class characteras.Sym(x,...)Argumentsx An R character vector....Not usedExamplesx<-c("a","2","4","c","d","6")xy<-as.Sym(x)yEval(y,list(a=3,c=3,d=3))4bodyAsExpression as.Sym.matrix Convert character matrix to yacas objectDescriptionSimple and raw conversion to yacasUsage##S3method for class matrixas.Sym(x,...)Argumentsx An R character matrix....Not usedExamplesx<-matrix(c("a","2","4","c","d","6"),3,2)xy<-as.Sym(x)yEval(y,list(a=3,c=3,d=3))bodyAsExpression Get body of function as an expression.DescriptionGet body of function as an expression.UsagebodyAsExpression(x)Argumentsx An R function.DetailsThis function is similar to the R body function except that function returns a call object whereas this one returns an expression usable in Ryacas calculations.Eval5 ValueAn expression.See AlsobodyExamples#construct an R function for the Burr probability density#function(PDF)given the Burr cumulative distribution function(CDF)BurrCDF<-function(x,c=1,k=1)1-(1+x^c)^-k#transfer CDF to yacasyacas(BurrCDF)#create a template for the PDF from the CDFBurrPDF<-BurrCDF#differentiate CDF and place resulting expression in bodybody(BurrPDF)<-yacas(expression(deriv(BurrCDF(x,c,k))))[[1]]#test out PDFBurrPDF(1)Eval Evaluate a yacas expression.DescriptionEvaluate a yacas expression.UsageEval(x,env=parent.frame(),...)Argumentsx Object to be evaluated.env Environment or list in which to perform evaluation....Not currently used.6get_output_widthExamplesEval(yacas(expression(x*x)),list(x=2))#samex<-2Eval(yacas(expression(x*x)))getSyms List Sym()objectsDescriptionLists all Sym()objects in the global environment(.GlobalEnv)UsagegetSyms(s=FALSE)Argumentss a logical value.If TRUE,all object names are returned.If FALSE,names which begin with a.are omitted.ExamplesgetSyms()xs<-Sym("x")getSyms()get_output_width Get width of yacas outputDescriptionGet width of yacas outputUsageget_output_width()root7 root Root functionDescriptionThe$y$’th root of$x$,i.e.$x^(1/y)$.Usageroot(x,y)Argumentsx Number to take$y$’th root ofy RootValueThe root y’th root of xRyacas_options Set or get options for the Ryacas packageDescriptionSet or get options for the Ryacas packageUsageRyacas_options(...)Arguments...Option names to retrieve option values or[key]=[value]pairs to set options. Supported optionsThe following options are supported•module_matvec_enabled(default TRUE):Print yacas List()’s as vectors and List(List(), ...)’s as matrices.•prettyform_default(default FALSE):Print yacas as PrettyForm()as default.8stripvar set_output_width Set width of yacas outputDescriptionSet width of yacas outputUsageset_output_width(w)Argumentsw Width in number of charactersstripvar Removes part of expression containing variableDescriptionYacas’Solve(eq,x)can return e.g.x==expr and{x==expr1,x==expr2,...}.Some usages are easier if the initial x==part is removed.This is the purpose of this function.Usagestripvar(expr,var)Argumentsexpr Expression where x==expr should be replaced to exprvar Name of variable,e.g.xValueExpression with left-hand side removedsyacas9 syacas yacas interface–silent versionDescriptionSimilar to yacas()but silent.This can be useful when working with yacas directly.Usagesyacas(x,...)Argumentsx A yacas character string or an R expression without terminating semicolon to be processed by yacas....Additional arguments ultimately passed down to yacas.character.See AlsoyacasSym SymDescriptionThe Symbol interface to yacas.UsageSym(...)Expr(x)Arguments...An R character string or object that can be coerced to a character string.x An R expression.10yacas DetailsAn object of class"Sym"is internally a yacas character string.An object of class"Expr"is in-ternally an R expression.One can combine such objects using the Math and Ops R operators (see help(Math)and help(Ops)for a list).Also there are methods for a number of R gener-ics:as.character.Sym,as.expression.Sym,determinant.Sym,deriv.Sym and print.Sym and yacas-oriented functions:Clear,Conjugate,Expand,Factor,Factorial,I,Identity,Inﬁnity,Integrate, Inverse,InverseTaylor,Limit,List,N,Newton,Pi,Precision,PrettyForm,PrettyPrinter,Set,Sim-plify,Solve,Subst,Taylor,TeXForm,Transpose,Ver and"%Where%"all of which have the same meaning as the corresponding yacas commands.Try vignette("Rycas-Sym")for many examples.Get Sym objects with getSyms().ValueSym returns a"Sym"object and Expr returns an"Expr"object.NoteCurrently the only Expr methods implemented are as.character.Expr,deriv.Expr,Math.Expr,Ops.Expr and print.Expr.See Alsoas.Sym.matrix()Examplesx<-Sym("x")x*xIntegrate(x*x,x)Sym("%")%Where%list(x=10)acos(Sym("1/2"))y<-Exprq(x)y*yderiv(y*y,y)Exprq(acos(1/2))yacas yacas interfaceDescriptionInterface to the yacas computer algebra system.Usageyacas(x,...)##S3method for class characteryacas(x,verbose=FALSE,method,retclass=c("expression","character","unquote"),addSemi=TRUE,...)Argumentsx A yacas character string or an R expression without terminating semicolon to be processed by yacas....Additional arguments ultimately passed down to yacas.character.verbose A logical value indicating verbosity of output or"input"to only show input to yacas but not output from yacas or"output"to only show output from yacasbut not input to yacas.method method used to communicate with yacas.If"socket"is speciﬁed then the same yacas session is used on a sequence of calls.If"system"is speciﬁedthen a new instance of yacas is used just for the period of that call."system"does not require that the system be conﬁgured to support telnet/sockets and somay be useful in some instances.If no value is speciﬁed the default is takenfrom getOption("yacas.method")and if that is not speciﬁed"socket"is used."socket"and"system"may be abbreviated.addSemi If TRUE a semicolon is added to the character string sent to yacas.This can be set to FALSE if its known that the character string already has a trailing semicolon.It is ignored if retclass="expression".retclass The class of theﬁrst component of the yacas structure.It defaults to"expression"but may be speciﬁed as"character"or"unquote"."unquote"is the same as"character"except that if the character string returned would have otherwisehad quotes in theﬁrst and and last positions then they are stripped.DetailsThe user supplies an R expression,an R function name corresponding to a function with a single line body,a formula or a yacas input string.In the case of a formula it is regarded as an expression represented by the right hand side of the formula while the left hand side,if any,is ignored.Note the silent version syacas().ValueAn R object of class"yacas"is returned.If PrettyPrinter("OMForm")is in effect,which it is by default,then theﬁrst component is an R expression and the OMForm component contains Open-Math XML code.In other cases theﬁrst component is NULL and the YacasForm or PrettyForm components have display information.Generally an expression.Refer to details.NoteWindows Installation.On Windows one can install Ryacas by issuing the commands:install.packages("Ryacas",dep=TRUE)library(Ryacas)yacasInstall()or by using the Packages|Install package(s)menu in place of theﬁrst command.The sec-ond command downloads scripts.dat and yacas.exe from the internet and installs them into R_HOME/library/Ryacas/yacdir where R_HOME is the location of your R installation.Normally the default locations of yacas,its initializationﬁle and the scriptsﬁle are sufﬁcient but, if necessary,they can be overridden via the environment variables:YACAS_HOME,YACAS_INIT and YACAS_SCRIPTS.The YACAS_INVOKE_STRING environment variable discussed in the next section overrides all three of these.All OS Installation.The YACAS_INVOKE_STRING environment variable can be used to override the invocation string for yacas.Normally it is not used.If it does need to be used then a typical use might be:library(Ryacas)#only need to do the file.copy command oncefile.copy(system.file("yacdir/R.ys",package="Ryacas"),"~/.yacsrc")#this needs to be done once per sessionSys.setenv(YACAS_INVOKE_STRING="yacas-pc--server9734")demo(Ryacas)#test it outyacmode.There is also a utility yacmode which is called without arguments and just turns R into a terminal into yacas until one quits out of it(and back to R)by entering stop,end,quit,exit or e.Startup.yacas starts up when yacasStart()is called or theﬁrst time yacas is called.yacas is shut down when yacasStop()is called or when the package is detached using the detach()R command.On Windows,when yacas is shut down,the yacas process is terminated on Windows XP Pro but not on other versions of Windows.In those cases there will be a dangling process that the user must terminate manually.Translation.The translation process occurs in several steps.If the input to the yacas function is an expression then it is translated to a valid yacas character string(otherwise,it is sent to yacas unprocessed).Yacas then processes the string and if retclass="expression"it is translated back to an R expression(otherwise it is sent back unprocessed).Examples of translations are:R yacassin(x)Sin(x)deriv(sin,x)Deriv(x)Sin(x)log(x)Ln(x)References/14yacasTranslations Examplesyacas(expression(Factor(x^2-1)))exp1<-expression(x^2+2*x^2)exp2<-expression(2*exp0)exp3<-expression(6*pi*x)exp4<-expression((exp1*(1-sin(exp3)))/exp2)print(yacas(exp4))print(yacas("Version()"))#yacas version#see demo("Ryacas-Function")yacasTranslations Yacas translationsDescriptionTranslations from R to the yacas computer algebra system.NoteThe translation process occurs in several steps.If the input to the yacas function is an expression then it is translated to a valid yacas character string(otherwise,it is sent to yacas unprocessed).Ya-cas then processes the string and if retclass="expression"it is translated back to an R expression (otherwise it is sent back unprocessed).Currently supported translations are:CONSTANTSR yacas======pi PiOPERATORSR yacas======7\%\%3Mod(7,3)7\%\/\%3Div(7,3)FUNCTIONSR yacas======sin(x)Sin(x)cos(x)Cos(x)yacas_evaluate15tan(x)Tan(x)asin(x)ArcSin(x)acos(x)ArcCos(x)atan(x)ArcTan(x)exp(x)Exp(x)sqrt(x)Sqrt(x)log(x)Ln(x)choose(n,k)Bin(n,k)gamma(x)Gamma(x)deriv(sin,x)Deriv(x)Sin(x)integrate(f,a,b)Integrate(x,a,b)f(x)list()List()factorial(n)n!Note the Limit example in demo(Ryacas0)for adding translations on theﬂy.The complete table under development.Author(s)Rob J GoedmanReferences/yacas_evaluate Evaluate yacas expressionDescriptionThis is a low-level function for evaluating yacas expression represented as string.Usageyacas_evaluate(expr)Argumentsexpr Yacas expressionValueResult of evaluating expr by yacas in OpenMath format and side-effects of the evaluationExamplesyacas_evaluate("D(x)Sin(x^2)")16yacmode yacmode yacmode interfaceDescriptionInteractive interface to the yacasUsageyacmode(enable_history=TRUE)Argumentsenable_history Use R history such that previous yacas commands can be used.Default is TRUE. DetailsThe user types valid yacas input and presses return.Type’quit’to return to R prompt.ValueOutput of yacas is returned.invisible NULLNoteNote that command will use R history()and modify it by default.Yacas is given a limited amount of time to complete,otherwise\[1\]CommandLine(1):User interrupted calculation is returned.E.g.Taylor(x,0,5)1/(1+x)will work,but Taylor(x,0,12)1/(1+x)is likely to take too long. References/Examples##Not run:yacmode()(x+y)^3-(x-y)^3Simplify(%)q##End(Not run)y_ls17 y_ls Get Yacas variablesDescriptionGet Yacas variablesUsagey_ls()ValueVector of variables deﬁned in yacasIndex∗programmingRyacas0-package,2∗symbolmathbodyAsExpression,4Eval,5stripvar,8Sym,9yacas,10yacasTranslations,14yacmode,16%Where%(Sym),9addSemi(yacas),10as.character.Expr(Sym),9as.character.Sym(Sym),9as.character.yacas(yacas),10 as.Expr.formula(Sym),9as.expression.Sym(Sym),9as.expression.yacas(yacas),10 nguage(bodyAsExpression),4 as.Sym(Sym),9as.Sym.character,3as.Sym.matrix,4as.Sym.matrix(),10body,5 bodyAsExpression,4 CharacteristicEquation(Sym),9 Clear(Sym),9Conjugate(Sym),9deriv.Expr(Sym),9deriv.Sym(Sym),9 determinant.Expr(Sym),9 determinant.Sym(Sym),9 EigenValues(Sym),9Eval,5Expand(Sym),9Expr(Sym),9Exprq(Sym),9Factor(Sym),9Factorial(Sym),9FindRoots(Sym),9get_output_width,6getSyms,6I(Sym),9Identity(Sym),9Infinity(Sym),9Integrate(Sym),9Inverse(Sym),9InverseTaylor(Sym),9Limit(Sym),9List(Sym),9Math.Expr(Sym),9Math.Sym(Sym),9N(Sym),9Newton(Sym),9OpenMath2R(Sym),9Ops.Expr(Sym),9Ops.Sym(Sym),9Ops.yacas.symbol(Sym),9Pi(Sym),9Precision(Sym),9PrettyForm(Sym),9PrettyPrinter(Sym),9print.Expr(Sym),9print.Sym(Sym),9print.yacas(Sym),9root,7Ryacas0-package,2Ryacas_options,718INDEX19 Set(Sym),9set_output_width,8Simplify(Sym),9Solve(Sym),9stripvar,8Subst(Sym),9syacas,9syacas(),11Sym,9SymExpr(Sym),9Taylor(Sym),9TeXForm(Sym),9trans(Sym),9Transpose(Sym),9transtab(Sym),9Ver(Sym),9y_ls,17yacas,3,10yacas(),9yacas.symbol.value(Sym),9yacas_evaluate,15yacasTranslations,14yacmode,16yAssignFunction(yacas),10yDeriv(Sym),9yFactorial(Sym),9yIntegrate(Sym),9yLimit(Sym),9ynext(yacas),10yparse(yacas),10yrewrite(Sym),9ySequence(yacas),10ysub(yacas),10yUnlist(Sym),9。

Solaris 8 (SPARC 平台版) 发行说明说明书

Solaris8(SP ARC平台版)10/00发行说明更新Sun Microsystems,Inc.901San Antonio RoadPalo Alto,CA94303-4900U.S.A.部件号码806-6267–102000年10月Copyright2000Sun Microsystems,Inc.901San Antonio Road,Palo Alto,California94303-4900U.S.A.版权所有。

本产品或文档受版权保护，其使用、复制、发行和反编译均受许可证限制。

未经Sun及其授权者事先的书面许可，不得以任何形式、任何手段复制本产品及其文档的任何部分。

包括字体技术在内的第三方软件受Sun供应商的版权保护和许可证限制。

本产品的某些部分可能是从Berkeley BSD系统衍生出来的，并获得了加利福尼亚大学的许可。

UNIX是通过X/Open Company,Ltd.在美国和其他国家独家获准注册的商标。

Sun、Sun Microsystems、Sun标志、、AnswerBook、AnswerBook2、Java,JDK,DiskSuite,JumpStart,HotJava,Solstice AdminSuite,Solstice AutoClient,SunOS,OpenWindows,XView,和Solaris是Sun Microsystems,Inc.在美国和其他国家的商标、注册商标或服务标记。

所有SPARC商标均按许可证使用，它们是SPARC International,Inc.在美国和其他国家的商标或注册商标。

带有SPARC商标的产品均以Sun Microsystems,Inc.开发的体系结构为基础。

PostScript是Adobe Systems,Incorporated的商标或注册商标，它们可能在某些管辖区域注册。

Netscape Navigator(TM)是Netscape Communications Corporation的商标或注册商标。

lx2160a-serdes-reconfiguration-user-说明书

1IntroductionThe device reference manual provides a list of all supported SerDes protocols.Only SerDes options that have been validated on silicon are documented in the reference manual. Custom SerDes configuration may be supported by reconfiguring the lanes for the desired settings if validated and approved by NXP. Any changes to configuration of default SerDes options require software reconfiguration.This document describes the sequence to reconfigure SerDes lanes from SGMII to USXGMII/XFI and two PCIe x2 lanes at Gen 1 or Gen 2 speeds for the LX2160A device. Subsequent reconfiguration from SFI/XFI to 10GBase-KR or USXGMII shall follow the sequence described in the LX2160A Reference Manual.2SerDes configuration requirementsThis document describes a use case requirement of four lanes of USXGMII/XFI and two PCIe x2 lanes at Gen 1 or Gen 2 speeds,shown as SerDes 1 protocol number 31 in Table 1. Protocol 31 is not one of the default SerDes options for the LX2160A, therefore,it is not documented in the LX2160A Reference Manual. However, standard MC firmware versions 10.24.1 and later add support for protocol 31.This document describes the sequence that results in the target configuration which can be summarized as:1.Start with SerDes protocol 11, which supports four lanes of SGMII on lanes F, E, B, and A, and two PCIe x2 lanes at Gen 3 speed on lanes H, G, D, and C.2.Reconfigure the SGMII lanes to USXGMII/XFI and limit the PCIe lanes to Gen 2 speed.3.Change the PLL assignment for USXGMII/XFI to PLLS since 10G Ethernet only runs on PLLS.4.Change the PLL assignment for PCIe to PLLF since it runs on 5 GHz VCO frequency so it cannot run on the same PLL as USXGMII/XFI.Table 1.SerDes 1 reconfigurationThe reconfiguration sequence assumes the following starting RCW settings:•SRDS_PRTCL_S1 = 5'b01011 to select protocol 11.Contents 1Introduction......................................12SerDes configuration requirements ........................................................13Software sequence.........................24RCWSR29 override. (65)Revision history (7)AN13022LX2160A SerDes 1 Lane Reconfiguration from 11 to 31Rev. 0 — 10/2020Application Note•SRDS_DIV_PEX_S1 = 2'b10 to configure PCIe to train up to a max rate of 5G (Gen 2).•SRDS_PLL_REF_CLK_SEL_S1 = 2'b mn, where m selects the reference clock for the PCIe lanes on PLLS and n selects the reference clock for USXGMII/XFI lanes on PLLF. Example:—m = 0 for 100 MHz PCIe reference clock—n = 1 for 161.1328125 MHz USXGMII/XFI reference clock•SRDS_PLL_PD_PLL1 = 0 and SRDS_PLL_PD_PLL2 = 0 so both PLLF and PLLS are powered up.•SRDS_REFCLKF_DIS_S1 = 0 to keep SD1_PLLF_REF_CLK enabled.•SRDS_INTRA_REF_CLK_S1 = 0 intra reference clock is not used.3Software sequenceThe reconfiguration sequence must be implemented in PBI and is shown below.1.Disable SGMII for lanes A, B, E, and F.•SD1: PCC8 (offset 0x10A0) = 0x0000_0000—SGMIIA_CFG = 0 disable SGMIIa—SGMIIB_CFG = 0 disable SGMIIb—SGMIIE_CFG = 0 disable SGMIIe—SGMIIF_CFG = 0 disable SGMIIf2.Enable XFI mode for lanes A, B, E, and F•SD1: PCCC (offset 0x10B0) = 0x9900_9900—SXGMIIA_XFI = 1 PCS operates in XFI/SFI mode—SXGMIIA_CFG = 001b enable SXGMIIa—SXGMIIB_XFI = 1 PCS operates in XFI/SFI mode—SXGMIIB_CFG = 001b enable SXGMIIb—SXGMIIE_XFI = 1 PCS operates in XFI/SFI mode—SXGMIIE_CFG = 001b enable SXGMIIe—SXGMIIF_XFI = 1 PCS operates in XFI/SFI mode—SXGMIIF_CFG = 001b enable SXGMIIf3.Assume 100 MHz reference clock for PLLF for the PCIe lanes•SD1: PLLFCR0 (offset 0x0404) = 0x0000_0000—REFCLK_SEL = 00000b for 100 MHz4.Configure 5G clock net frequency for PLLF•SD1: PLLFCR1 (offset 0x0408) = 0x9030_0008—SLOW_VCO_EN = 1 to enable the slower VCO—FRATE_SEL = 10000b for PCIe on PLLF—HI_BW_SEL = 1 to select higher PLL bandwidth—CLKD_RCAL_SLW_EN = 1 to enable resistor calibration for clock driver—RTMR_BYP = 1 to bypass retimer to clock driver and SSC phase interpolator—EX_DLY_SEL = 00b5.Set the recommended PLLF settings for PCIe 5G•SD1: PLLFCR3 (offset 0x0410) = 0x0000_3000—SSC_SEL = 00b no PLL modulation—SSC_SLP_OFF = 0000000000b for no slope offset—Bit 13 = 1—Bit 12 = 16.Set the recommended PLLF settings for PCIe 5G•SD1: PLLFCR4 (offset 0x0414) = 0x0000_0000—SSC_BIAS_BST = 000b SSC bias boost—SSC_SAW_MIN = 0000000000b SSC minimum sawtooth frequency offset—SSC_PI_BST = 00000b SSC phase interpolator Iqdiv2 boost—SSC_SAW_MAX = 0000000000b SSC maximum sawtooth frequency offset7.Assume 161.1328125 MHz reference clock for PLLS for 10GE operation•SD1: PLLSCR0 (offset 0x0504) = 0x0004_0000—REFCLK_SEL = 00100b for 161.1328125 MHz8.Configure 10.3125G clock net frequency for PLLS•SD1: PLLSCR1 (offset 0x0508) = 0x8610_0008—SLOW_VCO_EN = 1 to enable the slower VCO—FRATE_SEL = 00110b for XFI/SFI on PLLS—HI_BW_SEL = 0 to do not select higher PLL bandwidth—CLKD_RCAL_SLW_EN = 1 to enable resistor calibration for clock driver—RTMR_BYP = 1 to bypass retimer to clock driver and SSC phase interpolator—EX_DLY_SEL = 00b9.Set the recommended PLLS settings for XFI•SD1: PLLSCR3 (offset 0x0510) = 0x0000_3000—SSC_SEL = 00b no PLL modulation—SSC_SLP_OFF = 0000000000b for no slope offset—Bit 13 = 1—Bit 12 = 110.Set the recommended PLLS settings for XFI•SD1: PLLSCR4 (offset 0x0514) = 0x0000_1000—SSC_BIAS_BST = 000b SSC bias boost—SSC_SAW_MIN = 0000000000b SSC minimum sawtooth frequency offset—SSC_PI_BST = 00010b SSC phase interpolator Iqdiv2 boost—SSC_SAW_MAX = 0000000000b SSC maximum sawtooth frequency offset11.Change the PLL assignment for PCIe on the transmitter for lanes C, D, G, H from PLLS to PLLF•SD1: LNmTGCR0 (offsets 0x0A24 for lane C, 0x0B24 for lane D, 0x0E24 for lane G, 0x0F24 for lane H) = 0x0100_0200—USE_SLOW_PLL = 0 transmit uses PLLF—BY_N_RATE_SEL = 001b PCIe is half rate—CM_DLY_MATCH = 1 changes in LNmTRSTCTL[OUT_CM] are delay matched to changes in transmit data 12.Change the PLL assignment for PCIe on the receiver for lanes C, D, G, H from PLLS to PLLF•SD1: LNmRGCR0 (offsets 0x0A44 for lane C, 0x0B44 for lane D, 0x0E44 for lane G, 0x0F44 for lane H) =0x0100_0001—USE_SLOW_PLL = 0 receive uses PLLF—BY_N_RATE_SEL = 001b PCIe is half rate—PTRM_VCM_SEL = 01b Common mode is HiZ if PLLnRST[EN] or LNmRRSTCTL[EN] is negated.13.Change the protocol for lanes A, B, E, F from SGMII to XFI•SD1: LNmGCR0 (offsets 0x0800 for lane A, 0x0900 for lane B, 0x0C00 for lane E, 0x0D00 for lane F) =0x0000_0052—Bit 28 = 0 Must be 0 for all protocols—PORT_LN0_B = 0 Single-lane protocol—PROTO_SEL = 01010b for XFI—IF_WIDTH = 010b 20-bit interface width14.Set the PLL assignment for XFI on the transmitter for lanes A, B, E, F to PLLS•SD1: LNmTGCR0 (offsets 0x0824 for lane A, 0x0924 for lane B, 0x0C24 for lane E, 0x0D24 for lane F) =0x1000_0000—USE_SLOW_PLL = 1 transmit uses PLLS—BY_N_RATE_SEL = 000b 10G is full rate—CM_DLY_MATCH = 0 changes in LNmTRSTCTL[OUT_CM] are not delay matched to changes in transmit data15.Configure the transmit equalization for lanes A, B, E, F for XFI•SD1: LNmTECR0 (offsets 0x0830 for lane A, 0x0930 for lane B, 0x0C30 for lane E, 0x0D30 for lane F) =0x1080_8307—EQ_TYPE = 001b for 2-tap equalization—EQ_SGN_PREQ = 1 for positive sign for pre-cursor—EQ_PREQ = 0000b for 1.0x drive strength of transmit full swing transition bit to pre-cursor—EQ_SGN_POST1Q = 1 for positive sign for first post-cursor—EQ_POST1Q = 00011b for 1.14x drive strength of transmit full swing transition bit to first post-cursor—EQ_AMP_RED = 000111b for 0.585x overall amplitude reduction16.Set the PLL assignment for XFI on the receiver for lanes A, B, E, F to PLLS•SD1: LNmRGCR0 (offsets 0x0844 for lane A, 0x0944 for lane B, 0x0C44 for lane E, 0x0D44 for lane F) =0x1000_0000—USE_SLOW_PLL = 1 receive uses PLLS—BY_N_RATE_SEL = 000b 10G is full rate—PTRM_VCM_SEL = 00b Common mode impedance is always calibrated to SD_GND17.Set the recommended XFI settings for lanes A, B, E, F•SD1: LNmRGCR1 (offsets 0x0848 for lane A, 0x0948 for lane B, 0x0C48 for lane E, 0x0D48 for lane F) =0x1000_0000—RX_ORD_ELECIDLE = 0 Do not put into ordered idle state—Bit 28 = 1—ENTER_IDLE_FLT_SEL = 00b Bypass unexpected entrance into idle—EXIT_IDLE_FLT_SEL = 000b Force immediate exit from idle state AFTER order idle released and min time in idle—DATA_LOST_TH_SEL = 000b Disable loss of signal detection18.Disable receive equalization gain overrides for lanes A, B, E, F•SD1: LNmRECR0 (offsets 0x0850 for lane A, 0x0950 for lane B, 0x0C50 for lane E, 0x0D50 for lane F) =0x0000_000019.Set the recommended the receive equalization for XFI for lanes A, B, E, F•SD1: LNmRECR2 (offsets 0x0858 for lane A, 0x0958 for lane B, 0x0C58 for lane E, 0x0D58 for lane F) =0x8100_0020—Bit 31 = 1—EQ_BLW_SEL = 01b baseline wander for 10G—Bits 5:4 = 10bThe PBI sequence is shown below:.pbiwrite 0x01EA10A0,0x00000000write 0x01EA10B0,0x99009900write 0x01EA0404,0x00000000write 0x01EA0408,0x90300008write 0x01EA0410,0x00003000write 0x01EA0414,0x00000000write 0x01EA0504,0x00040000write 0x01EA0508,0x86100008write 0x01EA0510,0x00003000write 0x01EA0514,0x00001000write 0x01EA0A24,0x01000200write 0x01EA0A44,0x01000001write 0x01EA0B24,0x01000200write 0x01EA0B44,0x01000001write 0x01EA0E24,0x01000200write 0x01EA0E44,0x01000001write 0x01EA0F24,0x01000200write 0x01EA0F44,0x01000001write 0x01EA0800,0x00000052write 0x01EA0900,0x00000052write 0x01EA0C00,0x00000052write 0x01EA0D00,0x00000052write 0x01EA0824,0x10000000write 0x01EA0924,0x10000000write 0x01EA0C24,0x10000000RCWSR29 override write 0x01EA0D24,0x10000000write 0x01EA0830,0x10808307write 0x01EA0930,0x10808307write 0x01EA0C30,0x10808307write 0x01EA0D30,0x10808307write 0x01EA0844,0x10000000write 0x01EA0944,0x10000000write 0x01EA0C44,0x10000000write 0x01EA0D44,0x10000000write 0x01EA0848,0x10000000write 0x01EA0948,0x10000000write 0x01EA0C48,0x10000000write 0x01EA0D48,0x10000000write 0x01EA0850,0x00000000write 0x01EA0950,0x00000000write 0x01EA0C50,0x00000000write 0x01EA0D50,0x00000000write 0x01EA0858,0x81000020write 0x01EA0958,0x81000020write 0x01EA0C58,0x81000020write 0x01EA0D58,0x81000020.end4RCWSR29 overrideThe Reset Configuration Word Status Registers (RCWSR1:RCWSR32) are written with the RCW information that are read from flash memory by the device at power-on-reset. The RCWSR register values are read-only after exiting reset.Software (U-boot) reads the selected SerDes protocol from RCWSR29. It looks at the SerDes configuration table to find the entry for protocol 31 and its corresponding interfaces. In order for software (U-boot) to read the updated SerDes 1 protocol value of 31, the following steps must be performed:1.Add an entry for SerDes 1 protocol 31 in the SerDes configuration table in U-boot2.Override the RCWSR29 with the updated SerDes 1 protocol value of 31•Write to address 0x7_00100170 the new protocol SRDS_PRTCL_S1 = 31.•The SerDes 2 and SerDes 3 configuration fields should remain unchanged.•Note: The RCWSR29 cannot be updated from the PBI phase. The update must be done in the initial stages of the the board-specific U-boot code so that the correct SerDes protocol is read as U-boot continues execution.Table 2.Address 0x7_0010017031302928272625242322212019181716 SRDS_PRTCL_S3SRDS_PRTCL_S2SRDS_PRTCL_S1SRDS_REFCLKF_DIS_S11514131211109876543210Table continues on the next page...Table 2.Address 0x7_00100170 (continued)ReservedSRDS_PLL_P D_PLL6SRDS_PLL_P D_PLL5SRDS_PLL_P D_PLL4SRDS_PLL_P D_PLL3SRDS_PLL_P D_PLL2SRDS_PLL_P D_PLL1Any support, information, and technology (“Materials”) provided by NXP are provided AS IS, without any warranty express or implied, and NXP disclaims all direct and indirect liability and damages in connection with the Material to the maximum extent permitted by the applicable law. NXP accepts no liability for any assistance with applicationsor product design. Materials may only be used in connection with NXP products. Any feedback provided to NXP regarding the Materials may be used by NXP without restriction.5Revision historyThe table below summarizes the revisions to this document.Table 3.Revision history Revision historyHow To Reach Us Home Page: Web Support: /support Information in this document is provided solely to enable system and software implementersto use NXP products. There are no express or implied copyright licenses granted hereunderto design or fabricate any integrated circuits based on the information in this document. NXP reserves the right to make changes without further notice to any products herein.NXP makes no warranty, representation, or guarantee regarding the suitability of its products for any particular purpose, nor does NXP assume any liability arising out of the applicationor use of any product or circuit, and specifically disclaims any and all liability, includingwithout limitation consequential or incidental damages. “Typical” parameters that may be provided in NXP data sheets and/or specifications can and do vary in different applications, and actual performance may vary over time. All operating parameters, including “typicals,”must be validated for each customer application by customer's technical experts. NXP does not convey any license under its patent rights nor the rights of others. NXP sells products pursuant to standard terms and conditions of sale, which can be found at the following address: /SalesTermsandConditions.Security — Customer understands that all NXP products may be subject to unidentifiedor documented vulnerabilities. Customer is responsible for the design and operation of its applications and products throughout their lifecycles to reduce the effect of these vulnerabilities on customer’s applications and products. Customer’s responsibility also extends to other open and/or proprietary technologies supported by NXP products for use in customer’s applications. NXP accepts no liability for any vulnerability. Customer should regularly check security updates from NXP and follow up appropriately. Customer shall select products with security features that best meet rules, regulations, and standards of the intended application and make the ultimate design decisions regarding its products and is solely responsible for compliance with all legal, regulatory, and security related requirements concerning its products, regardless of any information or support that may be provided by NXP. NXP has a Product Security Incident ResponseTeam(PSIRT)(************************)thatmanagestheinvestigation, reporting, and solution release to security vulnerabilities of NXP products.NXP, the NXP logo, Freescale, the Freescale logo, CodeWarrior, Layerscape, and QorIQ are trademarks of NXP B.V. All other product or service names are the property of their respective owners. Arm and Cortex are registered trademarks of Arm Limited (or its subsidiaries) in the US and/or elsewhere. The related technology may be protected by any or all of patents, copyrights, designs and trade secrets. All rights reserved. The Power Architecture and word marks and the Power and logos and related marks are trademarks and service marks licensed by .© NXP B.V. 2020.All rights reserved.For more information, please visit: Forsalesofficeaddresses,pleasesendanemailto:**********************Date of release: 10/2020Document identifier: AN13022。

SIGALARM Model 210 MicroGuard 414 MicroGuard 414错误

SkyAzúl, Equipment Solutions301-371-61261FAULT REPORTING AND FAULT CODESSystem Fault Codes provide one of the most important ways to quickly locate and assess problems in your MicroGuard ®System. Please review this section carefully.FAULT DIAGNOSTIC PROCEDURESEach time the System is turned on, it goes through a self-testing process lasting two to three seconds that automatically detects any Faults in the System. During normal operation, a Self-Test can be initiated at any time by pressing the TEST button on the Display Console. Fault conditions in external sensors are detected without a System Self-Test.Faults detected in the System during Self-Test, are indicated on the Display Console in the following way:•The word FAULT will appear in the information area of the left Display.•The RED LAMP will illuminate and the AUDIBLE ALARM will sound.Diagnosis of a Fault is obtained by PRESSING and HOLDING the TEST button. The System will then go through a Self-Test followed by the appearance of a Fault Code screen. The Fault Code screen will remain visible as long as the TEST button is pressed. Information will be displayed on the screen in the four groups shown in Figure 5.0.Note: Always repair Analog Sensor Faults (AAA) prior to investigating other faults. A complete listing of all possible Fault Codes and the description of each is listed on the following pages.000 NO FAULTS001TX.0PISTON PRESSURE SENSOR002 TX.1 ROD PRESSURE SENSOR 004 AIN2 EXTENSION SENSOR 008 AIN3 BOOM ANGLE SENSOR 016 AIN4 S’STRUCTURE ANGLE SENSOR 032 AIN5 SWING POTENTIOMETER “A” 064AIN6SWING POTENTIOMETER “B”Group AAA Analog Sensors0 NO FAULTS1 1 DIGITAL INPUT AND OUTPUT2 2 ANALOG INPUT AND OUTPUT44DISPLAY UNITGROUP B IO FAULTS00 NO FAULTS 01 1 PROGRAM ROM 02 2 DUTY ROM 04 4 SCRATCHPAD RAM 088PERSONALITY ROMGROUP CC MEMORY FAULTS00 NO FAULTS 01 1 NO DUTY FOUND 022CURRENT DUTY BADGROUP DD GENERAL FAULTSFIGURE 5.0 FAULT CODES2SkyAzúl, Equipment Solutions 301-371-61263018 Fault 002 & 016 019 Fault 001, 002, & 016 020 Fault 004 & 016 021 Fault 001, 004, & 016 022 Fault 002, 004, & 016023 Fault 001, 002, 004, &016 024 Fault 008, & 016025 Fault 001, 008, & 016026 Fault 002, 008, & 016027 Fault 001, 002, 008, &016028 Fault 004, 008, & 016 029 Fault 001, 004, 008, &016 030 Fault 002, 004, 008, &016 031 Fault 001, 002, 004,008, & 016 032 Swing Pot “A” 033 Fault 001, & 032 034 Faults 002, & 032035Faults 001, 002, &AAA Fault Codes continuedFAULT No . DESCRIPTION036 Faults 004 & 32 037 Faults 001, 004, &032 038 Faults 002, 004, &032 039 Faults 001, 002, 004, & 032 040Faults 008, & 032 041 Faults 001 008, &032 042Faults 002, 008, &032 043Faults 001, 002, 008, & 032 044Faults 004, 008, &032 045Faults 001, 004, 008, & 032 046 Faults 002, 004, 008, & 032 047 Faults 001, 002, 004, 008, & 32048 Faults 016 & 032 049Faults 001, 016, &032 050 Faults 002, 016, &032 051 Faults 001, 002, 016, & 032 052Faults 004, 016, &AAA Fault CodesFAULT No. DESCRIPTIONFigure 5.2 AAA Analog Sensor Fault CodesNumbers 1-127 continuedSkyAzúl, Equipment Solutions 301-371-61264053 Faults 001, 004, 016,& 32 054 Faults 002, 004, 016,& 32 055 Faults 001, 002, 004,016, & 32 056 Faults 008, 016, &032 057 Faults 001, 008, 016,& 032 058 Faults 002, 008, 016,& 032 059 Faults 001, 002, 008,016, & 032 060 Faults 004, 008, 016,& 032 061 Faults 001, 004, 008,016, & 032 062 Faults 002, 004, 008,016, & 032 063 Faults 001, 002, 004, 008, 016, & 032 064 SWING POT “B” 065 Faults 001 & 064 066 Faults 002 & 064 067 Faults 001, 002, &064 068 Faults 004 & 064 069 Faults 001, 004, &064 070 Faults 002, 004, &064 071Faults 001, 002, 004,AAA Fault Codes continuedFAULT No . DESCRIPTION072 Faults 008, & 64 073 Faults 001, 008, & 64 074 Faults 002, 008, &064 075 Faults 001, 002, 008,& 064 076 Faults 004, 008, &064 077 Faults 001, 004, 008,& 064 078 Faults 002, 004, 008,& 064 079 Faults 001, 002, 004,008, & 064 080 Faults 016 & 064 081 Faults 001, 016 & 064 082 Faults 002, 016 & 064 083 Faults 001, 002, 016& 064 084 Faults 004, 016, &064085 Faults 001, 004, 016,& 064 086 Faults 002, 004, 016,& 064 087 Faults 001, 002, 004,016, & 064 088 Faults 008, 016, &064 089 Faults 001, 008, 016,& 064 090Faults 002, 008, 016,AAA Fault Codes continuedFAULT No . DESCRIPTIONFigure 5.2 AAA Analog Sensor Fault CodesNumbers 1-127 continuedSkyAzúl, Equipment Solutions301-371-61265091 Faults 001, 002, 008,016, & 064 092 Faults 004, 008, 016,& 064 093 Faults 001, 004, 008,016, & 064 094 Faults 002, 004, 008,016, & 064 095 Faults 001, 002, 004, 008, 016, & 064 096 Faults 032, & 064 097 Faults 001, 032, &064 098 Faults 002, 032, &064 099 Faults 001, 002, 032,& 064 100 Faults 004, 032, &064 101 Faults 001, 004, 032,& 064 102 Faults 002, 004, 032,& 064 103 Faults 001, 002, 004,032, & 064 104 Faults 008, 032, &064 105 Faults 001, 008, 032,& 064 106 Faults 002, 008, 032,& 064 107 Faults 001, 002, 008,032, & 064 108 Faults 004, 008, 032,& 064 109Faults 001, 004, 008,AAA Fault Codes continuedFAULT No . DESCRIPTION110 Faults 002, 004, 008,032, & 064 111 Faults 001, 002, 004, 008, 032, & 064 112 Faults 016, 032, &064 113 Faults 001, 016, 032,& 064 114 Faults 002, 016, 032,& 064 115 Faults 001, 002, 016,032, & 064 116 Faults 004, 016, 032,& 064 117 Faults 001, 004, 016,032, & 064 118 Faults 002, 004, 016,032, & 064 119 Faults 001, 002, 004, 016, 032, & 064 120 Faults 008, 016, 032,& 064121 Faults 001, 008, 016,032, & 064 122 Faults 002, 008, 016,032, & 064 123 Faults 001, 002, 008, 016, 032, & 064 124 Faults 004, 008, 016,032, & 064 125 Faults 001, 004, 008, 016, 032, & 064 126 Faults 002, 004, 008, 016, 032, & 064 127Faults 001, 002, 004,AAA Fault Codes continuedFAULT No . DESCRIPTIONFigure 5.2 AAA Analog Sensor Fault CodesNumbers 1-127 continuedSkyAzúl, Equipment Solutions 301-371-612660 No Faults1Digital Input and 2 Analog Input andOutput 3 Faults 1 & 2 4 Display Unit 5 Faults 1 & 4 6 Faults 2 & 47Faults 1, 2, & 4FAULT No .DESCRIPTION 00 No Faults01 Program ROM 02 Duty ROM 03 Faults 01 & 02 04 Scratchpad RAM 05 Faults 02 & 03 06 Faults 02 & 04 07 Faults 01, 02, & 04 08 Personality ROM 09Faults 01, & 08 10Faults 02 & 08 11Faults 01, 02, & 08 12Faults 04 & 08 13Faults 01, 04, & 08 14 Faults 02, 04, & 0815Faults 01, 02, 04, &FAULT No .DESCRIPTION 0No Faults01No Duty02 Current Duty Bad03Faults 01 & 02FAULT No .DESCRIPTIONFigure 5.3 B IO Fault CodesFigure 5.5 DD General Fault CodesFigure 5.4 CC Memory Fault Codes。

COGNOS_8_管理员使用手册[1]

COGNOS 8 管理员使用手册2006年11月2日目录COGNOS 8 管理员使用手册..................................................................... 错误!未定义书签。

1. Cognos8组件安装: ........................................................................ 错误!未定义书签。

Cognos SUNONE安装步骤: ...................................................... 错误!未定义书签。

Cognos PPSTU(Transformer)安装步骤: ...................................... 错误!未定义书签。

Cognos 8 Business Intelligence server安装步骤: ....................... 错误!未定义书签。

Cognos 8 Business Intelligence modeling安装步骤: .................. 错误!未定义书签。

Cognos 8 Business Intelligence Supplementary Lanuage安装步骤:错误!未定义书签。

2. SQL Server2000 SP4安装: .............................................................. 错误!未定义书签。

安装SQL Server2000: ............................................................... 错误!未定义书签。

3. Cognos8环境配置: ........................................................................ 错误!未定义书签。

IBM Cognos 8 软件开发工具版 8.4.1 安装与配置指南说明书

IBM Cognos8Software Development KitVersion8.4.1Installation and Configuration GuideProduct InformationThis document applies to IBM Cognos8Version8.4.1and may also apply to subsequent releases.To check for newer versions of this document, visit the IBM Cognos Information Centers(/infocenter/cogic/v1r0m0/index.jsp).CopyrightLicensed Materials-Property of IBM©Copyright IBM Corp.2005,2009.US Government Users Restricted Rights–Use,duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.IBM,the IBM logo,,and Cognos are trademarks or registered trademarks of International Business Machines Corp.,in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at /legal/copytrade.shtml.Microsoft,Windows,Windows NT,and the Windows logo are trademarks of Microsoft Corporation in the United States,other countries,or both. Linux is a registered trademark of Linus Torvalds in the United States,other countries,or both.UNIX is a registered trademark of The Open Group in the United States and other countries.Table of ContentsIntroduction5Installing and Configuring the SDK7Upgrading the SDK Software7Install the SDK8Configuring the SDK10Uninstall the SDK11Index13Licensed Materials–Property of IBM©Copyright IBM Corp.2005,2009.3Table of Contents4Software Development KitIntroductionThis document is intended for use with IBM Cognos 8software development kit (SDK).The SDK is a collection of cross-platform Web services,libraries,programming interfaces,and related APIs that you can use to access the full functionality of IBM Cognos 8.For more information,see the SDK Developer Guide .The IBM Cognos 8software development kit includes the IBM Cognos 8Mashup Service,which allows you to develop applications that expose IBM Cognos 8outputs,such as reports and analyses,as Web services (both SOAP and REST).You can also use the Mashup Service to create applications that use a structured view of IBM Cognos 8outputs as input.This document provides instructions for installing the SDK package from the IBM Cognos 8Software Development Kit CD.AudienceTo use this guide,you should have basic Windows,UNIX,and Linux administration skills.Related DocumentationOur documentation includes user guides,getting started guides,new features guides,readmes,and other materials to meet the needs of our varied audience.The following documents contain related information and may be referred to in this document.Note :For online users of this document,a Web page such as The page cannot be found may appear when clicking individual links in the following table.Documents are made available for your par-ticular installation and translation configuration.If a link is unavailable,you can access the document on the IBM Cognos Resource Center (/software/data/support/cognos_crc.html ).DescriptionDocument Installing,upgrading,configuring,and testing IBM Cognos 8,changing application servers,and setting up samplesIBM Cognos 8Installation and Configuration Guide Managing IBM Cognos 8processes and imple-menting custom reporting solutions by using acollection of cross-platform Web services,librar-ies,and programming interfaces provided withthe IBM Cognos 8SDKIBM Cognos 8Software Development KitDeveloper Guide Managing servers,security,reports,and portalservices;and setting up the samples,customizingthe user interface and troubleshooting IBM Cognos 8Administration and Security GuideLicensed Materials –Property of IBM5©Copyright IBM Corp.2005,2009.IntroductionDocumentDescriptionDeveloping applications with the IBM Cognos IBM Cognos8Mashup Service Developer Guide8Mashup Service that exposes IBM Cognos8BI outputs,such as reports and analyses,as Webservices(both SOAP and REST).Finding InformationProduct documentation is available in online help from the Help menu or button in IBM Cognosproducts.To find the most current product documentation,including all localized documentation andknowledge base materials,access the IBM Cognos Resource Center(/software/data/support/cognos_crc.html).You can also read PDF versions of the product readme files and installation guides directly fromIBM Cognos product CDs.Using Quick ToursQuick tours are short online tutorials that illustrate key features in IBM Cognos product components.To view a quick tour,start IBM Cognos Connection and click the Quick Tour link in the lower-right corner of the Welcome page.Getting HelpFor more information about using this product or for technical assistance,visit the IBM CognosResource Center(/software/data/support/cognos_crc.html).This site providesinformation on support,professional services,and education.Printing Copyright MaterialYou can print selected pages,a section,or the whole book.You are granted a non-exclusive,non-transferable license to use,copy,and reproduce the copyright materials,in printed or electronicformat,solely for the purpose of operating,maintaining,and providing internal training on IBMCognos software.6Software Development KitInstalling and Configuring the SDKAfter you install and configure IBM Cognos8,install and configure the IBM Cognos8softwaredevelopment kit(SDK)to enable developers and system integrators to extend the value of the coresolution of IBM Cognos8capabilities.This is achieved with the integration of external applicationsand environments and the development of custom unique capabilities.The IBM Cognos8SDK CD contains●the SDK software,including Web services,libraries,programming interfaces,and related APIs●the SDK Developer Guide●the Mashup Service Developer Guide●the Framework Manager script player●the Framework Manager modeling SDK●SDK samples●Mashup Service samplesYou must use the same versions of the IBM Cognos8software development kit(SDK)and IBMCognos8and Framework Manager.The process for installing the IBM Cognos8software development kit includes:❑Install the SDK(p.8).❑Configure the SDK(p.10).Upgrading the SDK SoftwareWhen you upgrade from an older version of the IBM Cognos8Software Development Kit,ensurethat you upgrade to the same version of IBM Cognos8and Framework Manager.If you have SDK applications that rely on a previous version of the report specifications,you cannotuse Framework Manager to publish your model without losing backward compatibility.For more information about upgrading IBM Cognos8and Framework Manager,see the IBMCognos8Installation and Configuration Guide.For information about changes that may affect the product during or after an upgrade,see therelease notes and upgrade sections of the IBM Cognos8Software Development Kit Installationand Configuration Guide.IBM Cognos8automatically upgrades the content store.If you upgrade from ReportNet,you must make some changes to your SDK program for it tofunction with the IBM Cognos8version of the WSDL file.Some methods,classes,and propertieshave been deprecated in IBM Cognos8.Deprecated features continue to function as before,but Licensed Materials–Property of IBM©Copyright IBM Corp.2005,2009.7Installing and Configuring the SDKwill be removed in future releases.Some other methods,classes,and properties are obsolete,andhave been removed from the IBM Cognos8SDK.For information about changes to methods,classes,properties,and enumeration sets,see the ReleaseNotes appendixes in the IBM Cognos8SDK Developer Guide.New report specifications have been added in IBM Cognos8.If you run a report that was createdin ReportNet or in a previous version of IBM Cognos8,it is automatically upgraded to the newIBM Cognos8format.After a report is upgraded to the new format,it cannot be returned to theReportNet or older IBM Cognos8format.Because of the potential for users to upgrade reportspecifications that SDK applications may depend on,we recommend that you set access permissionson those reports to limit user access.For more information about setting access permissions,seethe IBM Cognos8Administration and Security Guide.If you have SDK applications that create,modify,or save report specifications,do not upgrade yourreport specifications when you install the new version of IBM Cognos8.You must first updateyour SDK applications to comply with the IBM Cognos8report specifications schema.Otherwise,your SDK applications may not be able to access the upgraded report specifications.For informationabout upgrading report specifications,see the IBM Cognos8SDK Developer Guide.We recommend that you do not upgrade your report specifications if you are unsure about whetheryou have SDK applications that create,modify,or save report specifications.Contact your SDKadministrator for more information about your SDK applications.Install the SDKInstall the SDK files from the IBM Cognos8SDK CD on every computer where SDK applicationsare developed,and in the same installation location as IBM Cognos8.The IBM Cognos8SDK and some IBM Cognos8server components are available for installationon64-bit systems.Before you install the IBM Cognos8SDK on a64-bit system,check the Readmefor late-breaking information about where to install the components.You can view an up-to-date list of environments supported by IBM Cognos products,such asoperating systems,patches,browsers,web servers,directory servers,and database servers on theIBM Cognos Resource Center(/software/data/support/cognos_crc.html).It isimportant to note that the Linux operating system is available in a number of distributions andsupports a number of hardware platforms.Ensure that the Linux distribution and hardware com-bination you are using is a supported combination.It is important to apply all required operating system patches and to use only the versions of third-party software that are supported for an IBM Cognos product.Otherwise,your product may notwork properly.The IBM Cognos8SDK must be installed on a computer where IBM Cognos8is already installed.For information about deploying SDK applications,see IBM Cognos8SDK Getting Started.For more information about installing IBM Cognos8components,see the IBM Cognos8Installationand Configuration Guide.Before you install the IBM Cognos8SDK,ensure that IBM Cognos8BI components are installed. 8Software Development KitInstalling and Configuring the SDKIf you plan to use the Excel plug-in demo,you must have MSINET.OCX installed in the System32 sub-folder of your Windows folder.Steps for UNIX or Linux1.Mount the IBM Cognos8product disk or go to the directory where the installation files weredownloaded and extracted.Important:If you are installing on HP-UX,mount the IBM Cognos8SDK CD with Rock Ridge file extensions and do the following:●Add the pfs_mount directory in your path.For example,PATH=/usr/sbin/:$PATHexport PATH●To start the required NFS daemons and run the daemons in the background,typebg pfs_mountd and then type bg pfsd●To mount the drive,typepfs_mount-t rrip<device><mount_dir>-o xlat=unixFor example,pfs_mount/dev/dsk/c0t2d0/cdrom-o xlat=unixYou can now install or copy files as a non-root user using an IBM Cognos CD from this drive.●When the installation is complete,type pfs_umount/cdrom and kill the pfsd and pfs_mountddaemons to unmount the CD.2.Go to the directory that is appropriate for your operating system and start the installation:●If you use X Windows,type./issetup●Otherwise,you must run an unattended installation.For more information,see the IBMCognos8Business Intelligence Installation and Configuration Guide.3.In the Welcome page,select the language to use for the installation,and click Next.4.Follow the instructions to copy the required files to the same location where you installed IBMCognos8components.5.In the Finish page of the installation wizard:●If you want to view the transfer log or the summary-error log,click the appropriate Viewbutton.●If you want to see the readme file,select the View the Readme check box.Installation and Configuration Guide9Installing and Configuring the SDK6.Click Finish.Steps for Windows1.Insert the IBM Cognos8product disk or go to the directory where the installation files weredownloaded and extracted.The installation wizard starts automatically from the product disk.2.If the Welcome page does not appear,go to the operating system directory and double-clickthe issetup.exe file.3.Select the language to use for the installation,and click Next.4.Follow the instructions to copy the required files to the same location where you installed IBMCognos8components and Framework Manager.5.In the Finish page of the installation wizard:●If you want to view the transfer log or the summary-error log,click the appropriate Viewbutton.●If you want to see the readme file,select the View the Readme checkbox.6.Click Finish.You can access the SDK documentation using the shortcut in the Start menu.Configuring the SDKTo use the SDK,you must perform some configuration and set-up tasks.To configure the SDK,follow this process:❑If you want to run the Framework Manager script player from outside the bin directory,con-figure the FM_INI_FILE_PATH environment variable as a system variable on Windows.Theenvironment variable must point to the cognos8_location\configuration\fm.ini directory.❑To allow the browsing or import of system objects such as tables,views,synonyms,stored procedures,or functions from a relational database in Framework Manager,edit the entry forImportDatabaseSystemObjects in your fm.ini file.By default,ImportDatabaseSystemObjects is set to ers can see only the user tablesin the import and expression editor dialog boxes.To allow browsing or import of systemobjects,set the preference to TRUE.❑Set up the samples for IBM Cognos8and Framework Manager.For more information,see the Installation and Configuration Guide.❑Set up IBM Cognos8to use the SDK code samples.For more information,see the SDK Developer Guide.❑Set up IBM Cognos8to use the Mashup Service samples.10Software Development KitInstalling and Configuring the SDK For more information,see the Mashup Service Developer Guide.Uninstall the SDKUninstall the SDK if you no longer require IBM Cognos8or if you are upgrading the IBM Cognos8software.Steps for UNIX or Linux1.If the console attached to your computer does not support a Java-based graphical user interface,determine the process identification(pid)of the IBM Cognos8process by typing the followingcommand:ps-ef|grep cogbootstrapservice2.Stop the IBM Cognos8process:●If you run XWindows,start IBM Cognos Configuration,and from the Actions menu,clickStop.●If you do not run XWindows,type:kill-TERM pid3.To uninstall IBM Cognos8,go to the c8_location/uninstall directory and type the appropriatecommand:./uninst-u4.Follow the prompts to begin the uninstallation.5.When you are prompted to select the packages you want to uninstall,click the check box forIBM Cognos8Software Development Kit and then click Next.6.Continue following the prompts to complete the uninstallation.7.Delete all temporary Internet files.Steps for Windows1.From the Start menu,click Programs,IBM Cognos8,Uninstall IBM Cognos8.The Uninstall wizard appears.Tip:IBM Cognos8is the default name of the Program Folder that is created during theinstallation.If you chose another name,go to that folder to find the program.2.Follow the prompts to begin the uninstallation.3.When you are prompted to select the packages you want to uninstall,click the check box forIBM Cognos8Software Development Kit and then click Next.4.Continue following the prompts to complete the uninstallation.The Cognos_uninst_log.htm file records the activities that the Uninstall wizard performs whileuninstalling files.Installation and Configuration Guide11Installing and Configuring the SDKTip:To find the log file,look in the Temp directory.5.Delete all temporary Internet files.For more information,see your Web browser documentation.Uninstalling does not remove any files that changed since the installation,such as configurationand user data files.Your installation location remains on your computer,and you retain thesefiles until you delete them manually.12Software Development KitIndexAaudience of document,5Cconfiguring the SDK,10IIBM Cognos Resource Center,6installing the SDK,8Qquick toursusing,6SSDKconfiguring,10installing,8upgrading,7UUNIXinstalling the SDK,8upgrading the SDK software,7WWindowsinstalling the SDK,8Licensed Materials–Property of IBM©Copyright IBM Corp.2005,2009.13。

Moxa ioLogik 4000 Series模块化远程I O系统说明书

ioLogik4000SeriesModular remote I/OFeatures and Benefits•I/O expansion without a backplane•Active communication with MX-AOPC UA Server•Supports SNMP v1/v2c•Easy configuration with Modular ioAdmin utility•Friendly configuration via web browser•Simplifies I/O management with MXIO library for Windows or LinuxCertificationsIntroductionThe ioLogik4000Series is suitable for remote monitoring and alarm systems,such as those used for water treatment systems,water supply systems,wastewater treatment systems,and power monitoring systems.These kinds of applications need more I/O points and a variety of I/O types,including temperature sensors,gas detectors,and water quality detectors,all of which can benefit from the versatile mixture of I/O features supported by the ioLogik4000Series.Slice Form Factor and Flexible I/O VarietyThe unique modular construction of the ioLogik4000Series allows for mixing and matching of modules to achieve the best combination of I/O modules to meet the needs of a wide range of remote automation applications.An industrial modular housing enables I/O modules to be added to the base unit without a backplane.The ioLogik4000Series is perfect for space-limited applications,and high-density I/O points are provided for greater flexibility and expandability.Modules can connect to virtually any type of sensor,including but not limited to those for temperature, pressure,flow,voltage,current,and contact closure.Easy MaintenanceThe ioLogik4000Series comes with removable spring-type terminal blocks(RTBs)that allow you to conserve field wiring for future use.SpecificationsInput/Output InterfaceButtons Reset buttonControl LogicLanguage ioLogik E4200:Click&Go,NA-4010/4020/4021:NoneEthernet Interface10/100BaseT(X)Ports(RJ45connector)NA-4010:1ioLogik E4200:2,2MAC addressesEthernet Software FeaturesConfiguration Options NA-4010/ioLogik E4200:Web Console(HTTP)NA-4010/4020/4021:Windows Utility(ioAdmin)ioLogik E4200:Windows Utility(Modular-ioAdmin)Industrial Protocols NA-4010:Modbus TCP Server(Slave),MXIO LibraryNA-4020/4021:MXIO LibraryioLogik E4200:Modbus TCP Server(Slave),Moxa AOPC(Active Tag),MXIO Library,SNMPv1/v2c,SNMPv1TrapManagement NA-4010/ioLogik E4200:DHCP Client,HTTP,IPv4,TCP/IP,UDPNA-4010/4020/4021:ioAdminioLogik E4200:Modular-ioAdminSerial InterfaceConnector NA-4021:DB9femaleNA-4020:Terminal blockData Bits7,8No.of Ports1Parity None,Even,OddSerial Standards NA-4021:RS-232NA-4020:RS-485Stop Bits1,2Baudrate NA-4020/4021:1200,2400,4800,9600,19200,38400,57600,115200bpsSerial Software FeaturesIndustrial Protocols NA-4020/4021:Modbus RTU/ASCII SlaveSerial SignalsRS-232NA-4021:TxD,RxD,GNDRS-485-2w NA-4020:Data+,Data-,GNDDIP Switch ConfigurationSerial Interface Fixed baudrateModbus TCPMax.No.of Client Connections8Mode Client(Master)Power ParametersNo.of Power Inputs1System Power ParametersPower Connector Spring-type Euroblock terminalNo.of Power Inputs1Input Voltage11to28.8VDCPower Consumption NA-4010:60mA@24VDCNA-4020/4021:70mA@24VDCioLogik E4200:175mA@24VDCField Power ParametersPower Connector Spring-type Euroblock terminalNo.of Power Inputs1Input Voltage11to28.8VDCCurrent in Field Power Contact10A(max.)Physical CharacteristicsHousing PlasticDimensions45x99x70mm(1.77x3.90x2.76in)Weight NA-4010/4020/4021:150g(0.33lb)ioLogik E4200:180g(0.396lb)Installation DIN-rail mountingEnvironmental LimitsOperating Temperature-10to60°C(14to140°F)Storage Temperature(package included)-40to85°C(-40to185°F)Ambient Relative Humidity5to95%(non-condensing)Altitude2000m1Standards and CertificationsEMC EN61000-6-2/-6-4EMI CISPR22,FCC Part15B Class AEMS IEC61000-4-2ESD:Contact:4kV;Air:8kVIEC61000-4-3RS:80MHz to1GHz:10V/mIEC61000-4-4EFT:Power:2kV;Signal:1kVIEC61000-4-5Surge:Power:2kV;Signal:1kVIEC61000-4-6CS:10VIEC61000-4-8PFMFSafety UL508Shock IEC60068-2-27Vibration IEC60068-2-6DeclarationGreen Product RoHS,CRoHS,WEEEMTBFTime NA-4010:4,739,300hrsNA-4020:4,721,640hrsNA-4021:4,695,360hrsioLogik E4200:357,000hrsStandards Telcordia SR332WarrantyWarranty Period2yearsDetails See /warranty1.Please contact Moxa if you require products guaranteed to function properly at higher altitudes.Package ContentsDevice1x ioLogik4000Series remote I/OInstallation Kit1x terminal block,8-pin,3.81mmDocumentation1x quick installation guide(ioLogik E4200)1x warranty cardNote This product requires additional modules(sold separately)to function.DimensionsI/O Network Adapter I/O ModuleOrdering InformationModel Name Control Logic Ethernet Interface Serial Interface No.of Support I/O Modules ioLogik E4200Click&Go2x RJ45–16NA-4010–1x RJ45–32NA-4020––RS-48532NA-4021––RS-23232 Accessories(sold separately)I/O ModulesM-1450For the ioLogik4000Series,4DIs,110VACM-1451For the ioLogik4000Series,4DIs,220VACM-1600For the ioLogik4000Series,16DIs,24VDC,sink typeM-1601For the ioLogik4000Series,16DIs,24VDC,source typeM-1800For the ioLogik4000Series,8DIs,24VDC,sink typeM-1801For the ioLogik4000Series,8DIs,24VDC,source typeM-2450For the ioLogik4000Series,4relays,24VDC/230VAC,2AM-2600For the ioLogik4000Series,16DOs,24VDC,0.5A,sink typeM-2601For the ioLogik4000Series,16DOs,24VDC,0.5A,source typeM-2800For the ioLogik4000Series,8DOs,24VDC,0.5A,sink typeM-2801For the ioLogik4000Series,8DOs,24VDC,0.5A,source typeM-3802For the ioLogik4000Series,8AIs,4to20mA,12bitsM-3810For the ioLogik4000Series,8AIs,0to10V,12bitsM-4402For the ioLogik4000Series,4AOs,4to20mA,12bitsM-4410For the ioLogik4000Series,4AOs,0to10V,12bitsM-6200For the ioLogik4000Series,2AIs,RTD:PT100,JPT100M-6201For the ioLogik4000Series,2AIs,TCPower ModulesM-7001For the ioLogik4000Series,system power moduleM-7002For the ioLogik4000Series,field power moduleM-7804For the ioLogik4000Series,potential distributor module,0VDC8channelM-7805For the ioLogik4000Series,potential distributor module,24VDC,8channelSoftwareMX-AOPC UA Server OPC UA Server software for converting fieldbus to the OPC UA standard©Moxa Inc.All rights reserved.Updated Dec09,2020.This document and any portion thereof may not be reproduced or used in any manner whatsoever without the express written permission of Moxa Inc.Product specifications subject to change without notice.Visit our website for the most up-to-date product information.。

Mellanox ConnectX-4 ConnectX-4 Lx和Connect-IB发行版说

Mellanox Technologies Mellanox FlexBoot for ConnectX®-4 / ConnectX®-4 Lx and Connect-IB® Release NotesRev 3.5.109Mellanox Technologies350 Oakmead Parkway Suite 100Sunnyvale , CA 94085U.S.A. Tel: (408) 970-3400Fax: (408) 970-3403© Copyright 2017. Mellanox Technologies Ltd. All Rights Reserved.Mellanox®, Mellanox logo, Accelio®, BridgeX®, CloudX logo, CompustorX®, Connect -IB®, ConnectX®, CoolBox®, CORE-Direct®, EZchip®, EZchip logo, EZappliance®, EZdesign®, EZdriver®, EZsystem®, GPUDirect®, InfiniHost®, InfiniBridge®, InfiniScale®, Kotura®, Kotura logo, Mellanox CloudRack®, Mellanox CloudXMellanox®, Mellanox Federal Systems®, Mellanox HostDirect®, Mellanox Multi-Host®, Mellanox Open Ethernet®, Mellanox OpenCloud®, Mellanox OpenCloud Logo®, Mellanox PeerDirect®, Mellanox ScalableHPC®, Mellanox StorageX®, Mellanox TuneX®, Mellanox Connect Accelerate Outperform logo , Mellanox Virtual Modular Switch®, MetroDX®, MetroX®, MLNX-OS®, NP-1c®, NP-2®, NP-3®, Open Ethernet logo , PhyX®, PlatformX®, PSIPHY®, SiPhy®, StoreX®, SwitchX®, Tilera®, Tilera logo , TestX®, TuneX®, The Generation of Open Ethernet logo, UFM®, Unbreakable Link®, Virtual Protocol Interconnect®, Voltaire® and Voltaire logo are registered trademarks of Mellanox Technologies , Ltd.All other trademarks are property of their respective owners .For the most updated list of Mellanox trademarks, visit /page/trademarksNOTE:THIS HARDWARE, SOFTWARE OR TEST SUITE PRODUCT (“PRODUCT(S)”) AND ITS RELATED DOCUMENTATION ARE PROVIDED BY MELLANOX TECHNOLOGIES “AS -IS” WITH ALL FAULTS OF ANY KIND AND SOLELY FOR THE PURPOSE OF AIDING THE CUSTOMER IN TESTING APPLICATIONS THAT USE THE PRODUCTS IN DESIGNATED SOLUTIONS. THE CUSTOMER'S MANUFACTURING TEST ENVIRONMENT HAS NOT MET THE STANDARDS SET BY MELLANOX TECHNOLOGIES TO FULLY QUALIFY THE PRODUCT(S) AND/OR THE SYSTEM USING IT . THEREFORE, MELLANOX TECHNOLOGIES CANNOT AND DOES NOT GUARANTEE OR WARRANT THAT THE PRODUCTS WILL OPERATE WITH THE HIGHEST QUALITY. ANY EXPRESS OR IMPLIED WARRANTIES , INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY , FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT ARE DISCLAIMED. IN NO EVENT SHALL MELLANOX BE LIABLE TO CUSTOMER OR ANY THIRD PARTIES FOR ANY DIRECT, INDIRECT, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING, BUT NOT LIMITED TO, PAYMENT FOR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY FROM THE USE OF THE PRODUCT(S) AND RELATED DOCUMENTATION EVEN IF ADVISED OF THE POSSIBILITY OF SUCHDAMAGE.Doc #: N/A 2Mellanox TechnologiesRev 3.5.1093Mellanox Technologies Table of ContentsTable of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3List Of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release Update History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Chapter 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.1 Supported Adapter Cards and Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2 Supported Tools (MFT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3 Supported Operating Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.4Tested Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Chapter 2 Changes and New Features in Rev 3.5.109 . . . . . . . . . . . . . . . . . . . 9Chapter 3 Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Chapter 4 Bug Fixes History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Chapter 5 Changes and New Feature History . . . . . . . . . . . . . . . . . . . . . . . . . 17Rev 3.5.1094Mellanox Technologies List Of TablesTable 1:Release Update History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Table 2:Supported Adapter Cards and Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Table 3:Supported Tools (MFT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Table 4:Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Table 5:Tested Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Table 6:Changes and New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Table 7:Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Table 8:Fixed Bugs List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Table 9:Changes and New Feature History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Rev 3.5.1xx 5Mellanox Technologies Release Update HistoryTable 1 - Release Update HistoryReleaseDateDescriptionRev 3.5.1xx January 10, 2017Initial release of this FlexBoot version for Con-nectX-4/ConnectX-4 Lx/ConnectX-5/ConnectX-5 Ex adapter cards.Rev 3.5.1096Mellanox Technologies 1OverviewThese are the release notes for "Mellanox FlexBoot", the software for Boot over Mellanox Tech-nologies adapter devices supporting VPI. FlexBoot enables booting kernels or operating systems (OS) from remote servers in compliance with the PXE specification.This package is based on the open source project iPXE available at .1.1Supported Adapter Cards and FirmwareFor the complete list of supported cards, please refer to ConnectX-4 Lx EN/ConnectX-4 EN and ConnectX-5 web pages at .1.2Supported Tools (MFT)1.3Supported Operating SystemsTable 2 - Supported Adapter Cards and FirmwareAdapter CardsFirmware VersionConnectX-516.18.1000 [at Beta level]ConnectX-4 Lx EN 14.18.1000ConnectX-412.18.1000Connect-IB (OEM cards only)10.16.1020Table 3 - Supported Tools (MFT)ToolsVersionMFT (Mellanox Firmware Tools) 4.6.0All the Operating Systems below expect for RedHat 7.3 are supported in Ethernet protocol only. RedHat 7.3 is supported in both InfiniBand and Ethernet protocol.Table 4 - Supported Operating SystemsOSsVersionESXi 5.5ESXi 6.0ESXi 6.5RHEL 6.4RHEL 6.6RHEL 7.0RHEL7.1OverviewRev 3.5.1097Mellanox Technologies 1.4Tested PlatformsRHEL 7.2RHEL 7.3SLES 11.3SLES 11.4SLES 12SLES 12.1SLES 12.2Ubuntu 14.04Ubuntu 15.4Ubuntu 16.04Ubuntu 16.10Windows Server 2012Windows Server 2012 R2Windows Server2016Table 5 - Tested PlatformsVendorType of serverBios VersionDELL Dell PowerEdge R730xd 13G 2.3.4DELL Dell PowerEdge R630 13G 2.3.4DELL Dell PowerEdge R640 14G 0.3.6DELL Dell PowerEdge C6320p 1.1.3Quanta Yesomity F20_3A12 / F20_3A09Quanta Leopard A V A_3B08Supermicro SuperMicroX9DRW V3.2 Dell PowerEdgeR8201.6.6HPE ProLiant DL180 Gen9U20 v2.20 (05/05/2016)HPE ProLiant XL730f Gen9U18 v1.50 (08/04/2015)HPE ProLiant DL380 Gen9P89 v2.20 (06/02/2016)HPE ProLiant XL260a Gen9U24 v1.00 (05/18/2016)HPE ProLiant DL160 Gen9U20 v2.20 (05/05/2016)HPE ProLiant DL360 Gen10U32 v1.00 (12/31/2016)Lenovo 3650 M5 2.10 TCE124M (23/06/2016)Lenovo3650 M51.20 TCE108IUS (17/12/2015)Table 4 - Supported Operating SystemsOSsVersionRev 3.5.1098Mellanox Technologies Lenovo 3550 M5 1.20 TCE108IUS (17/12/2015)Table 5 - Tested PlatformsVendorType of serverBios VersionChanges and New Features in Rev 3.5.109Rev 3.5.1099Mellanox Technologies 2Changes and New Features in Rev 3.5.109Table 6 - Changes and New FeaturesCategoryDescriptionFlexBoot UI Added support for "Undi network wait timeout"Enhanced FlexBoot/firmware debug capability using Flexboot UI Performance Performance enhancements in Ethernet mode Upstream syncSynced the source with iPXE (upstream sync)Rev 3.5.10910Mellanox Technologies 3Known IssuesThe following is a list of general limitations and known issues of the various components of this FlexBoot release.Table 7 - Known IssuesInternal Ref.Description-Description: Several BIOS vendors have limited boot-vector space and may not display FlexBoot in their boot menu.WA : Disable the embedded NIC boot agent in BIOS Keywords: BIOS-Description: In several BIOS, the server might hang during FlexBoot booting due to wrong configuration of the PMM.WA : N/A Keywords: BIOS-Description: Only EBX, ESI, DS, ES registers can be saved in Boot Entry.WA : N/A Keywords: BIOS-Description: If a client returned control to the BIOS after a successful connection to an iSCSI target (but did not boot from it), then, unexpected behavior may occur.WA : Follow the instructions described in the FlexBoot UM for the proper iSCSI boot/installKeywords: BIOS673114/821899Description: FlexBoot banner might not be shown in some BIOSes.WA : N/A Keywords: BIOS-Description: In some cases, PXE boot will not work if the client was given only the file-name without next-server (siaddr).WA : N/AKeywords: PXE Boot-Description: PXE boot after iSCSI boot with static configuration is currently not sup-ported.WA : N/AKeywords: PXE BootKnown Issues Table 7 - Known IssuesInternal Ref.Description-Description: Boot over VLAN with IB port is currently not supported.WA: N/AKeywords: PXE Boot-Description: Some faulty boot loaders do not close the underlying UNDI device which may result in unexpected behavior and possible system crash after the OS starts to load.WA: N/AKeywords: PXE Boot-Description: Chain-loading gPXE stack may result in undesirable behavior.WA: N/AKeywords: PXE Boot647143Description: Executing a partial boot loop while only downloading the NBP and select-ing localboot is unsupported and may cause undefined behavior.WA: N/AKeywords: PXE Boot670421Description: Using filename for PXE boot with rootpath for hooking an iSCSI target (to install) is not supported when the PXE boot loader uses UNDI API, since all traffic mustget to the boot loader.WA: N/AKeywords: PXE Boot-Description: iSCSI over IB is not tested.WA: N/AKeywords: iSCSI-Description: iSCSI over DCB is not supported.WA: N/AKeywords: iSCSI-Description: FlexBoot supports only a single active iSCSI connection. Thus, wheniSCSI-boot via Port 1 succeeds to connect but fails to boot, it will fail to connect via Port2.WA: N/AKeywords: iSCSITable 7 - Known IssuesInternal Ref.Description-Description: Boot retries is currently not functional when booting from iSCSI.WA: N/AKeywords: iSCSI655800Description: IPv6 is not supported.WA: N/AKeywords: iSCSI-Description: Boot menu is displayed as READ ONLY if the HCA card does not support flash configuration.WA: N/AKeywords: User Interface-Description: FlexBoot Boot Menu will not be visible in serial output.WA: N/AKeywords: User Interface-Description: Large Receive Offload (LRO) and iSCSI may not interoperate due to a bug in current Linux kernel distributions.WA: Disable LRO in the IPoIB module when using iSCSI.See the Mellanox FlexBoot user's manual for details under the Diskless Machines chap-ter (InfiniBand Ports).Keywords: Networking-Description: FlexBoot supports only 2K MTU.WA: N/AKeywords: Networking-Description: 56Gb/s is currently not supported.WA: N/AKeywords: Link Speed-Description: Setting the number of Virtual Functions higher than the machine's memory capability may cause memory issues and system instability.WA: N/AKeywords: VirtualizationKnown Issues Table 7 - Known IssuesInternal Ref.Description-Description: SLAM, FTP, HTTPS and SRP are currently not supported.WA: N/AKeywords: Protocols-Description: Occasionally, using the Spanning Tree Protocol (STP) in the switches may cause packet drops and boot failure in the system.WA: Enable the "edgemode" if disabled on the switch, or use either portfast or edgemodefunctionality on the switch ports connected to the NICs.Keywords: Protocols-Description: FCoE, BCV are not supported.WA: N/AKeywords: Protocols655800Description: IPv6 can only run if a RADVD service is running in the network.WA: N/AKeywords: Protocols-Description: IPv6 over IB is not supported.WA: N/AKeywords: Protocols655800Description: IPv6 over WDS is not supported.WA: N/AKeywords: Protocols655800Description: Enabling IPv6 first and then IPv4 is currently not supported.WA: N/AKeywords: Protocols841198Description: FlexBoot fails to boot when the following occurs:•Boot priority is set to iSCSI•The iSCSI TCP/IP parameters via DHCP is disabled•iSCSI boot fails or iSCSI boot to target configuration is set to disableWA: N/AKeywords: PXE boot, iSCSI843377/849223Description: The physical MAC assigned via the boot menu is displayed as zeroes instead of the set MAC when ConnectX-4 VPI adapter card is configured as InfiniBand.WA : N/AKeywords: Physical MAC, Boot menu656001Description: Booting from WDS and Windows DHCP server when only Option 66 is enabled (without Option 67), is not supported.WA : N/A Keywords: DHCP776057Description: Citrix PVS boot is not supported.WA : N/AKeywords: Citrix PVS boot689460Description: FlexBoot uses system UUID to generate the client DUID-UUID as per RFC 6355, the data conveyed with DHCPv6 Code 1 (Option ID).WA : N/AKeywords: DUID-UUID928217Description: Installing ESXi 6.5/6.0 on iSCSI target is currently not supported.WA : N/AKeywords: ESXi 6.5/6.0, iSCSI target689460Description: To use the DHCP server to identify ipxe requests when using undi -only.kpxe or ipxe.pxe when booting over IB requires special configuration. (see the Workaround below).WA : Add to the DHCP host declaration the MAC identification alongside the option 61 DUID.For example:host ib-client1 {option dhcp-client-identifier =ff:00:00:00:00:00:02:00:00:02:c9:00:<Port-GUID> ;hardware ethernet <Port-MAC> ;fixed-address <IPoIB Address> ;filename "ipxe.pxe" ;if exists user-class and option user-class = "iPXE" { filename “pxelinux.0” ; }}Keywords: undionly.kpxe or ipxe.pxeTable 7 - Known IssuesInternal Ref.DescriptionBug Fixes History 4Bug Fixes HistoryTable 8 - Fixed Bugs ListInternalDescriptionRef.843209Description: Fixed and issue which cause the link not to raise in the second port which isset as IB when the first port is ETH in PXE.Keywords: Link up, PortsDiscovered in Release: 3.4.903Fixed in Release: 3.5.109847950Description: Fixed wrong default value of Boot-To-Target in FlexBoot configuration.Keywords: Boot-To-Target, FlexBoot configurationDiscovered in Release: 3.4.719Fixed in Release: 3.4.903691148Description: When connecting a pre-configured port with VLAN to an IB fabric, the portruns as Ethernet port with the VLAN tag.Keywords: VLAN, Port ManagementDiscovered in Release: 3.4.719Fixed in Release: 3.4.903792432Description: Booting PXE using Grub2.X over HP G9/G8 servers results in system hang.Keywords: PXE boot, Grub2.X, HP G9/G8Discovered in Release: 3.4.719Fixed in Release: 3.4.903690792Description: If the PMM fails to allocate memory, the system hangs since FlexBoot cannotload from the expansion ROM.Keywords: PMM, expansion ROMDiscovered in Release: 3.4.719Fixed in Release: 3.4.812697291Description: In ConnectX-4, the PXE boot time measurement over TFTP Ethernet is 1:30 min for image size of 1GB, TFTP InfiniBand is 1:20 min, and iSCSI boot time measure-ment is 8 seconds for image size of 25 MB.Keywords: PXE Boot Discovered in Release: 3.4.719Fixed in Release: 3.4.812689068Description: In hybrid BIOSes, if the BIOS loads legacy driver without closing the UEFI driver, the legacy driver fails to load.Keywords: BIOS, legacy mode Discovered in Release: 3.4.719Fixed in Release: 3.4.812634794Description: Enabled 'boot_pci_busdevfn' initialization when booting from UNDI loader.Keywords: UNDI loader Discovered in Release: 3.4.650Fixed in Release: 3.4.719-Description: Removed the instruction that enabled write-protected section modifications after POST.Keywords: PXE Boot Discovered in Release: 3.4.650Fixed in Release: 3.4.719Table 8 - Fixed Bugs ListInternal Ref.DescriptionChanges and New Feature History5Changes and New Feature HistoryTable 9 - Changes and New Feature HistoryRelease ChangesRev. 3.4.903iSCSI re-imaging Enables the user to install a new image on active ISCSI targetFlexBoot UI Added new configuration for network link type for supported cards(ConnectX-4 VPI cards)Enabled boot configuration menu in ConnectX-4 when the physical port is IB Booting Enabled booting with non-default Pkey in ConnectX-4 when the physical portis IBLink Status Removed link status line printout at boot timeBoot Menu Changed the Bus:Device:Function format in boot menu, from PCI-Bus:Dev.Func to 0000:Bus:Dev.FuncUpstream sync Synced the source with iPXE (upstream sync)Rev. 3.4.812FlexBoot UI Added debug prints option in the FlexBoot boot menu. For further information,please refer to FlexBoot and UEFI User Manual.System Diagnosis Added the ability to diagnose problems in released ROMs by enabling thedebug log levels for specific modules.Note: This ability should be used only when debug session is needed.Interrupts Added support for ConnectX-4/ConnectX-4 Lx interruptsUpstream sync Synced the source with iPXE (upstream sync)Rev. 3.4.719IPv6Added IPv6 supportx64 Architecture Added x64 architecture support in ConnectX-4 and Connect-IB adapter cardsSHELL CLI Removed support for the following SHELL CLI commands:•Non-volatile option storage commands•SAN boot commands•Menu commands•Login command•Sync command•DNS resolving command•Time commands•Image crypto digest commands•Loopback testing commands•VLAN commands•PXE commands•Reboot commandFor further information, please refer to: /cmdUpstream sync Synced the source with iPXE (upstream sync)Table 9 - Changes and New Feature HistoryRelease ChangesRev. 3.4.650Image size Added support for .mrom images larger than 128kBAdapter Cards Added support for ConnectX-4 EN and ConnectX-4 Lx ENFlat real mode Moved to flat real mode when calling INT 1a,b101 to avoid BIOSes issues Spanning Tree Protocol Added support for detecting Spanning Tree Protocol non-forwarding ports(RSTP/MSTP)Upstream sync Synced the source with iPXE (upstream sync)Changes and New Feature HistoryChanges and New Feature HistoryMellanox TechnologiesRev 3.5.10921。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

-----:,1 一．．a"XDs 8HAEFELY - HIPOTRONICS -USER MANUAL留！SURGEEFT I BURSTVOLTAGE OIPSMAGNETIC FIELDRING WAVETELECOM WAVESERVICES一一一&1&，、队．且L 凰』，’t』且......非哺⑥”’“ ⑥去；号⑥C 刷⑥-<.-。

&.(j←＠吨’ .D 叫prec r soo n ...，”’swi ss -made宫 H’ G H V 。

L TAG E民主运 T E S T SO L U T IONS前言感谢您选择Haefely 的AXOS8产品，请您略花时间通读使用手册以熟悉仪器的操作和一些潜在危险。

我们希望您通过Haefely 的AXOS8多功能抗扰度测试系统获得更多的运营经验。

HAEFELY TEST AG使用手册文件标题参考编号可扩展测试系统AXOS8 多功能抗扰度测试仪器4700924_02目录目录 (I)1安全 (1)1.1一般安全信息 (1)1.2安全标准 (1)2产品描述 (2)2.1基本信息 (2)2.2AXOS8 涵盖标准 (3)3技术参数 (4)3.1概述 (4)3.2浪涌 (4)3.3振铃波 (5)3.4通讯波 (5)3.5脉冲群 (5)3.6电压跌落& 中断 (6)3.7内置单相CDN (6)4初始操作 (7)4.1视觉检查 (7)4.2安装 (7)4.3接地 (7)EUT电源输入 (7)EUT连接 (8)4.6电压跌落输入 (8)5总体操作 (9)5.1前视..图.................................................................................................9.5.2后视图 (9)5.3设置菜单 (11)5.4预定义标准程序 (12)5.4.1AXOS定义要求 (13)5.5图标栏 (14)5.6测试报告数据 (14)6浪涌 (15)6.1概述 (15)6.2组合波发生器 (15)6.2.1开路电压(OCV) (15)6.2.2短路电流(SCC) (16)6.3浪涌菜单 (16)6.3.1特性 (19)6.3.2切换 (20)6.3.3触发 (20)6.3.4AC同步 (20)7磁场 (21)7.1概述 (21)7.2磁场菜单 (21)7.2.1天线因子 (22)7.2.2切换 (23)7.2.3特性 (23)8振铃波 (24)8.1概述 (24)8.1.1振铃波开路电压(OCV) (24)8.2振铃波菜单 (24)8.2.1特性 (26)8.2.2切换 (27)8.2.3触发 (27)8.2.4同步AC (28)8.2.5输出& 耦合路径 (28)9通讯波 (29)9.1概述 (29)9.1.1通讯波开路电压(OCV) (29)9.1.2通讯波短路电流(SCC) (29)9.2TW 8 模块 (30)9.3AXOS 8 + TW 8 (31)9.3.1输出& 耦合路径 (33)9.3.2特性 (34)9.3.3切换 (34)9.3.4触发 (35)10电快速瞬变脉冲 (36)10.1概述 (36)10.2脉冲群菜单 (36)10.2.1输出& 耦合路径 (37)AXOS8 Compact immunity test System10.2.2特性 (38)10.2.3切换 (38)10.2.4触发 (39)10.2.5同步 (39)10.2.6脉冲群模式 (39)11电压跌落& 中断 (40)11.1概述 (40)11.2中断 (40)11.3跌落 (40)11.3.1变压器DIP 116 (42)11.3.2外部变压器 (43)11.3.3特性 (43)11.3.4切换 (44)11.3.5触发 (44)12序列 (45)12.1概述 (45)12.2序列菜单 (45)12.2.1序列添加步骤 (47)12.2.2启动序列 (48)12.2.3手动设置& 序列完成结果 (49)12.2.4结果清算 (49)12.3数据报告 (51)13错误信息 (52)13.1错误信息 (52)13.2故障排除 (52)13.3逻辑错误 (53)14软件 (54)14.1远程软件 (54)14.1.1“点对点” 远程控制 (54)14.1.2“无线局域网” 远程控制 (56)14.2报告软件 (56)15服务 (57)15.1概述 (57)15.2验证 (57)浪涌开路电压OCV (57)浪涌短路电流SCC (57)15.2.3电快速瞬变/爆发 (58)15.2.4脉冲群验证适配器 (58)15.3校准 (58)15.4回收 (59)16附件和选件 (60)16.1AXOS8 附件 (60)17附加信息 (61)17.1地址 (61)17.1.1国际客户服务 (61)17.1.2美国客户服务 (61)17.1.3中国客户服务 (61)17.1.4印度客户服务 (61)17.2制造商 (62)17.3术语和缩写词 (62)17.4参考资料 (63)17.5图表 (64)17.6表格 (66)18附录 (67)18.1CE 整合 (67)AXOS8 Compact immunity test SystemAXOS 8Compact immunity test System71 安全1.1 一般安全信息重要:请在使用 AXOS 8前仔细阅读其安全要求！在设备上可以看见此警告标识。

意思是只有在仔细阅读使用手册后才能操作此设备。

AXOS 8里面会呈现危险的电源电压或高压。

AXOS8必须接地良好，如果在没有接地的情况按下触发器，可能发生触电！在移除任何覆盖物时，先移除外接电线。

AXOS 8只能由经过培训的人员进行维修。

禁止打开任何零部件因为AXOS 8不包括用户可替换零件。

当测试进行时，心脏起搏器用户应该远离测试范围。

如果存在爆炸危险请不要打开或者运行 AXOS 8系统。

该系统应在干燥的房间中操作。

如果能看见机器上有冷凝现象，应在操作前先将机器进行干燥处理。

当 AXOS 8运行时禁止触摸受试设备（EUT ），并在测试设置中设立一道安全屏障（如表 5-3闭合电路的引脚4和引脚5).如果 AXOS 8 中的任何部分受损或有可能被损，例如，在运输过程中，那么不要开启设备。

在打开任何零件前请迁离电源线。

在更换电源保险丝之前请迁离电源线保险丝应当更换相同的类型。

这份使用手册是测系统不可分割的一部分，Haefely 测试AG 及其销售人员对因不遵守此操作说明或进行不正确的操作所引起的伤害将拒绝接受任何直接或间接的责任。

当施加磁场后，测试运行时请勿触摸线圈。

只有直接输出和通讯必须使用连接线圈，并且线圈环（从高到通信）必须关闭。

请不要直接将电源电压连接到高输出电压，否则将损害系统部件，所以请使用合适的CDM.表1-1: AXOS 8安全要求当系统测试开始时，AXOS 8中的相关符号如图1-1显示在屏幕上。

图 1-1: 安全标记1.2 安全标准AXOS 8符合IEC 61010-1的要求。

AXOS 8Compact immunity test System22 2 产品描述2.1 基本信息AXOS 8多功能抗扰度测试仪器将我们的独立测试系统所有最优的测试单元集成为一套独立的经济解决方案。

AXOS 8包含5 kV 电快速瞬变脉冲群，7KV 浪涌组合波，7 kV 振铃波，7KV 通讯波（10／700），单相电压跌落和中断，内置集成单相耦合/去耦合网络（CDN ）。

该设备依据最常见的IEC 标准等执行快速完整的自动抗扰度测试。

AXOS 8能够通过前面板触屏图形用户界面中的“7” 进行运作或者远程计算机控制。

根据 IEC 标准 , 建立测试单元组合，使得测试易于进行，可靠性好，重复性好。

AXOS 8所有的测试参数可以在较广的范围内变动，并且具有在测试期间改变测试参数的能力。

AXOS 8不仅是理想兼容和预兼容预测产品，而且是助于监测和调试功能研发设计的理想测试工具。

AXOS 8具有一系列高性价比和方便用户的电源线，对称和非对称的数据线（信号）线的耦合/去耦网络作为选件。

图2-1显示了AXOS 8的开始菜单。

每一个指令都要通过触摸屏输入。

按下触摸屏上对应的不同键如浪涌，电快速瞬变脉冲，电压跌落，磁场，振铃波和通讯波，你能进入对应的特定功能操作区。

但是，AXOS8的可扩张测试版本在未扩展时图标会保存在灰影中，并且通过关键代码升级访问。

序列和设置将在第12章中进一步详细解释。

图 2-1:启动显示如图2-1所示选择其中一个功能后，一般出现两种可操作菜单模式。

只有在预兼容模式下有可能改变测试参数，即使设备正在运行测试。

通过输入一个功能参数就会弹开对应的基本描述包括特性。

参数值可以根据各个标准需要直接设定。

在标准操作模式下，类似的情况也是有可能的。

此外，EUT 电流的峰值和电压的峰值会显示在屏幕上。

如图2-1所示，当按下“主页”按钮时，就会从开始菜单中应用程序返回，任何测试程序也会立即停止。

当选定菜单上特定的线路输出路径时，每一个输出和耦合路径相对应的发光二极管都会发光。

AXOS 8Compact immunity test System32.2 AXOS 8 涵盖标准表 2-1: AXOS 8涵盖标准请仔细阅读IEC/EN 标准中对每一个特定的规范测试详细说明。

整体的规范是许多产品规范包括进一步的测试。

的确，产品规范中更详细描述许多产品要求。

注：产品规范将部分由AXOS8履行，请进一步联系以帮助销售代表或者HAEFELY 。

AXOS 8Compact immunity test System43 技术参数3.1概述表 3-1: 基本参数3.2 浪涌表3-2: 浪涌数据表 3-3 振铃波数据通讯波表 3-4 通信波数据脉冲群表 3-5 脉冲群数据3.6 电压跌落& 中断表-6: 电压跌落和暂降数据3.7 内置单相CDNAXOS8 为群脉冲和浪涌测试提供一个综合单相耦合/去耦合网络。

它通过综合保护电路防止过高电流带来的的损害。

在“特性”菜单里面，可选的电流限制在1A-16A 之间。

内置CDN 可能被用来与交流电源线或直流电源线使用。

内置CDN的输入（被测物体电源输入）必须与带有电源安全开关的电源线连接，或额定电流不超过 16A 和符合特征 B 或 C 的电流。

4 4 初步操作4.1 视觉检查在运输过程中A XOS8可能遭受很大的冲击和振动，即使HAEFELY Test AG采取合适的包装。