您的位置：360文档中心› 1_NMTM basics

1_NMTM basics

合集下载

TRIO BASIC中文手册

TRIO BASIC中文手册

描述 ERROR_LINE 包括最后 BASIC 程序出错的行数
PMOVE 包括任务缓存的状态 PROC 获得特定过程参数 PROC_LINE 返回特定程序的当前行 PROCNUMBER 包括当前被选择运行的任务数 PROC_STATUS 返回特定过程的状态
RUN_ERROR 包括在特定任务产生的 BASIC 错误数 TICKS 包括当前任务时钟脉冲
描述
页数
8 轴参数
以下列表概述了轴的参数，详细描述参考特定页。
命名
ACCEL ADDAX_AXIS ATYPE AXISSTATUS CLOSE_WIN CLUTCH_RATE CREEP DATUM_IN DECEL DEMAND_EDGES DPOS DRIVE_STATUS D_GAIN ENCODER ENDMOVE ERRORMASK FAST_JOG FASTDEC FE FE_LIMIT FERANGE FEMIN FHOLD_IN FHSPEED FS_LIMIT FWD_IN FWD_JOG
描述 任何两个有效表达式的加 任何两个有效表达式的减 任何两个有效表达式的乘积 任何两个有效表达式的除 如果表达式 1 等于表达式 2 返回真，否则返回假 如果表达式 1 不等于表达式 2 返回真，否则返回假 如果表达式 1 大于表达式 2 返回真，否则返回假 如果表达式 1 大于等于表达式 2 返回真，否则返回假 如果表达式 1 小于表达式 2 返回真，否则返回假 如果表达式 1 小于等于表达式 2 返回真，否则返回假 返回表达式的绝对值 返回表达式的反余弦 两有效 BASIC 表达式在整数部分的相应位执行与操作 返回表达式的反正弦 返回表达式的正切值 返回非零表达式的反正切值 清除特定 VR 变量的特定位

QBasic命令大全

QBasic命令大全

QBasic命令大全Basic是一门很老的编程语言，据说比尔?盖茨当年上大学时和朋友就曾用basic编了一个系统，卖了不少钱，还有每制造一台用那系统的电脑就给他一些钱，后来他就不上学了。

这里是关于QBasic的命令，方便广大编程初学者参考。

QBasic虽然不再列入计算机考试范围，但它的魅力依旧。

ABSy=ABS(n)得到n的绝对值ASCy=ASC(S$)得到字符串头一个字符的ASCII码ATNy=ATN(n)得到反正切值(单位是弧度)CDBLy=CDBL(n)把n转化为双精度浮点格式CHR$S$=CHR$(n)得到ASCII码n对应的字符CINTy=CINT(n)对n进行舍入取整(奇凑偶CLNGy=CLNG(n)把一个数n转化为长整数COMMAND$S$=COMMAND$在DOS下启动程序时,获得命令行中的其余信息COSy=COS(n)得到自变量n的余弦值CSNGy=CSNG(n)把一个数值转化为单精度数CSRLINy=CSRLIN返回光标行数位置CVIV%=CVI(2字节的串)字符串转换为整型数CVSV!=CVS(4字节的串)字符串转换为单精度数CVLV&=CVL(4字节的串)字符串转换为长整数CVDV#=CVD(8字节的串)字符串转换为双精度数CVSMBFV!=CVSMBF(4字节MS字符串)转换成IEEE格式单精度数CVDMBFV#=CVDMBF(8字节MS字符串)转换成IEEE格式双精度数DATE$S$=DATE$把系统日期赋给变量S$ENVIRON$S$=ENVIRON$(X$)S$=ENVIRON$(n)得到环境表中的参数EOFy=EOF(filenum)遇到文件结束则返回真,否则为假ERDEVy=ERDEV返回设备驱动器错误码ERDEV$S$=DEDEV$返回设备驱动器错误信息ERRy=ERR返回错误的错误号ERLy=ERL返回出错处最近的行号EXPy=EXP(X)指数函数y=exFILEATTRy=FILEATTR(filenum,attr)返回打开文件的信息FIXy=FIX(n)截掉小数部分进行取整FREy=FRE({S$|-1|-2})得到可以被程序使用的剩余内存空间的大小FREEFILEy=FREEFILE返回下一个自由BASIC文件号HEX$S$=HEX$(n)把十进制数转换成相应十六进制格式字符串INKEY$S$=INKEY$从键盘上读数据但不显示INPy=INP(portno)从一个I/O端口读入一个字节INPUT$S$=INPUT$(m[,[#]n])从键盘或文件中读入指定数量的字符 INSTRy=INSTR([n,]targetstring, patternsttring)字符串查找INTy=INT(n)得到一个不大于n的最大整数IOCTL$S$=IOCTL$[#]n从一个设备驱动器程序接收数据LBOUNDy=LBOUND(array[,n])返回数组array第n维的最小下标LCASE$S$=LCASE$(X$)把字符串X$的大写字母全变为小写LEFT$S$=LEFT$(X$,n)得到字符串X$最左边的n个字符LENy=LEN(S$)得到字符串S$的长度LOCy=LOC(n)得到文件中现在所处的位置(当前位置)LOFy=LOF(n)得到磁盘文件的长度或通讯缓冲区剩余空间大小LOGy=LOG(x)自然对数y=InXLPOSy=LPOS(printer)得到打印缓冲区中当前的位置LTRIM$S$=LTRIM$(x$)返回去掉前导空格的字符串复制品MID$S$=MID$(X$,n[,m])从X$的第n个字符开始取m个字符;省略m,则取完MKD$S$=MKD$(V#)把双精度数值转化为随机文件中输出字符串MKI$S$=MKI$(V%)把整数转换为字符串MKL$S$=MKL$(V&)把长整数转换为字符串MKS$S$=MKS$(V!)把单精度数转换为字符串MKSMBF$S$=MKSMBF$(V!)把单精度数转换为MS格式字符串MKDMBF$S$=MKDMBF$(V#)把双精度数转换为MS格式字符串OCT$S$=OCT$(n)得到数值n的八进制形式字符串,负数为其补码形式PEEKy=PEEK(offset)得到指定存储单元的值PENy=PEN(option)读取光笔状态PLAYy=PLAY(x)得到后台音乐缓冲区音符个数PMAPy=PMAP(i,option)把图形屏幕的物理坐标变为实用坐标或反之POINTcolor=POINT(x,y)y=POINT(n)得到一个象素的颜色得到前一个点的坐标POSy=POS(x)得到光标的列数位置RIGHT$S$=RIGHT$(x$,n)从字符串X$的右边取n个字符RNDy=RND(n)得到0到1之间的随机数,n=0则得到前一个RND值RTRIM$S$=RTRIM$(X$)返回一个去掉X$尾随空格的字符串SADDy=SADD(S$)返回S$字符串的地址SCREENy=SCREEN(row,column[,option])得到屏幕上指定字符的ASCII或属SEEKy=SEEK(filenum)返回当前文件位置SETMEMy=SETMEM(n)改变远堆集使用的内存大小SGNy=SGN(n)输出n的符号SINy=SIN(x)正弦值y=SinXSPACE$S$=SPACE$(n)输出长度为n的空格字符串SPCSPC(n)在PRINT语句中跳过n个空格SQRy=SQR(n)给出n的平方根STICKy=STICK(n)返回两个操纵杆的坐标STR$S$=STR$(n)返回一个表示n值的字符串STRIGy=STRIG(n)返回操纵杆触发状态STRING$S$=STRING$(n,x$)返回n个x$第一个字符组成的字符串TABTAB(column)将输出位置移到column列TANy=TAN(x)正切值y=tgXTIME$S$=TIME$获得当前时间TIMERy=TIMER输出自午夜开始后流逝的秒数UBOUNDy=UBOUND(array[,n])输出数组array第n维最大下标UCASE$S$=UCASE$(x$)把字符串x$中所有小写字母变成大写 VALy=VAL(S$)输出字符串S$的相应数值VARPTRy=VARPTR(variable)返回变量的偏移地址VARSEGy=VARSEG(variable)返回变量的段地址VARPTR$S$=VARPTR$(variable)返回变量地址的字符串表示语句名语句格式功能BEEP BEEP 使喇叭发声BLOAD BLOAD filespc[,address] 把用BSAVE语句存贮的文件装入内存 BSAVE BSAVE filespc,address,length 把某一内存区域中的内容存入磁盘形式参数表)] 调用一个过程 CALL CALL 过程名[(CALLS CALLS 过程名[形式参数表] 把控制传给非BASIC语言写的过程 CALL ABSOLUTE CALL ABSOLUTE address [(参数表)] 传送控制给一个机器语言过程CALL INT86OLD CALL INT86OLD(int_no, in_array(), out_array()) CALL INT86XOLD(int_no,in_array(), out_array()) 实现DOS功能调用 CALL INTERRUPT CALL INTERRUPT(int_no, inregs, outregs)CALL INTERRUPTX(int_no, inregs, outregs) 结构化的DOS功能调用 CHAIN CHAIN filespec 将控制由当前程序转到别的程序CHDIR CHDIR path 改变现行的目录(相当于DOS的CD) CIRCLECIRCLE(x,y),r,[,c[,start,end,[,aspect]]] 画圆或圆的一部分 CLEAR CLEAR 重新初始化全部变量,关闭文件和设置堆栈的大小 CLOSE CLOSE [[#]n[,[#]n]...] 关闭文件。

IBM Cognos TM1商品说明书

IBM Cognos TM1商品说明书

Leveraging IBM Cognos TM1for Merchandise Planning at Tractor Supply CompanyDan Thomas –Architect, Financial Systems Tractor Supply CompanyRicky Rielly –Implementation Manager QueBIT ConsultingAgenda✓Introductions and Company Overviews✓TSC Merchandise Planning Solution Overview ▪Prior State▪Solution and Implementation✓Tips & Tricks for TM1 Perspectives Templates ✓Q&AQueBIT OverviewRicky Rielly –Implementation ManagerAbout QueBIT▪Trusted Experts in Analytics▪15+ years in business with managers on the team who have been working in area of Analytics for 20+ years ▪Full Offerings -Advisory & Implementation Services, Reseller of IBM Software and Developer of Solutions ▪900+ successful Analytics Projects▪450+ analytics customers in all types of industries▪100+ employees with HQ in New York▪Building an experienced team from the ground up▪Deep Expertise in Financial Analytics, Advanced Analytics, Business Intelligence, and DHW ▪Strong focus in Financial Services sector▪Multi-Year Award WinnerQueBIT: Trusted Experts in AnalyticsWe’re driven to help organizationsimprove their agility to makeintelligent decisions that createvalue.This is why we’re committed toexcellence in analytics strategy andimplementation.Tractor Supply Company OverviewDan Thomas –Architect, Financial SystemsTractor Supply Company Overview•Founded in 1938 as a mail order catalog business offering tractor parts to American farmers•Today operating in over 1600 stores in 49 states, annual revenue of $6.8B •Stores primarily located in towns outlying major metropolitan markets and in rural communities•Customers include farmers, horse owners, ranchers, part-time and hobby farmers, and suburban and rural homeowners, as well as contractors and tradesmen•Selling products relating to animal care, truck tool and hardware, seasonal and agricultural products, clothing and giftsRicky Rielly –Implementation ManagerTractor Supply Company and QueBIT •Initial Merchandise Planningmodel implemented in 2014•Core focus on future scalabilityand knowledge transfer•New models and enhancementssince thenTractor Supply Prior State Overview•Primarily Cognos Enterprise Planning solution •Supplemented with manual Excel work•Lack of scalability and manual workarounds •Inflexibility and difficulty with multiple concurrent users •Time consuming to administrate and maintain•Granular, SKU level data loaded to a staging cube▪This data then feeds downstream modules and is used in calculations •Planning occurs on a rolling basis at a Category level•Key Item Planning and other additional modules•Architecture leaves room for future growth▪More products/channels▪Additional modules•Actuals automatically loaded by SKU daily•Significant time savings•Greater scalability•Streamlined process for Merch Planners•Automated handling of 53rd week comparisons in calculations•Can handle restatement of Plan and Forecast based on annual hierarchy realignment•Flexible and streamlined reporting interface•Robust and intuitive Planning user experienceDan Thomas –Architect, Financial SystemsVisual Presentation Tips•Don’t underestimate the importance of the visual aspects within your templates•Use outside sources for inspiration (business journals, other BI / analytic tools, etc.)•If graphic design is not one of your skills, partner with someone who has a talent for that•Incorporating your company logo into templates is a small thing that can make a big perceived difference•You can use gradient shading to give your headers more “pop”Format cells> Fill Effects> Gradient: Two Colors, Horizontaluse a differential of at least two tones, lighter color on top•Add alternate row shading in Active Forms containing a large number of rows and columnsYou can add additional levels within the format area.Here we have added “M” to serve as the alternating format for “N”, and “P” for the total.You can change the formula for the format identifier in the first column of the first row containing data. Make the cell references to be relative, not absolute, so that each row of the Active Form is compared to the row above it.Dan Thomas –Architect, Financial SystemsTSC Forecast Template –Unique Features•Drop downs in Excel for product selection instead of the Subset Editor Less clicks for the end user to get where they want to goShould only be used with reasonably sized subsets because there are calculations which add some overheadUser types in the name of a Product dimension subset (cell A15 in the example below), which powers the available selections within the drop down menu in cell A14TSC Forecast Template –Unique Features Drop Downs (2)To derive the drop down list, hard code a list of index numbers (column B in the example below) Use the DIMSIZ function to evaluate whether the index number is valid within the dimensionIf it is, use the SUBNM function to list the name of the element with that index numberTSC Forecast Template –Unique FeaturesDrop Downs (3)Leverage naming conventions for product codes within the dimension to indent based upon the hierarchy level. Use this output for the drop down.For product codes within our product hierarchy, Categories start with “C”, Departments start with “D” and buyers start with “B”. We used IF formulas to indent a certain number of spaces when the first letter of the element met that condition.There are no product codes in the Go_New_Stores library (only product names), so the example below used the result of the ELLEV function instead.•Used conditional formatting to alert users when they are in a sandbox version This may require VBA to determine the name of the active sandbox for that user. If it’s not equal to “Base” (or blank), then the user is in a sandbox and you can display the conditional formatting. We chose to use a bright blue bar.Not in a sandbox version:In a sandbox version:•User Defined Consolidations (UDCs)User Defined Consolidations allow end users to create a Private customized rollup of elements. This parameter must be set in the Config file: UserDefinedCalculations=T To create a User Defined Consolidation:Step 1 –Create a private subset of elements. We recommend to our users prefixing that name with “udc_” .User Defined Consolidations (2)Step 2 –Insert that private subset into a new one to create a rollup.a) Launch the Subset Editor and remove all visible elements (select all elements in the view and then Delete).b) Go to Edit>Insert Subset from the top of the Subset Editor. Use the Select Subset drop down to choose theprivate subset you had created and click OK.A rollup for the elements in that subset is then created (udc_Golf Clubs in the example below).The name of the rollup is the same as the subset you inserted.c) Save this new subset that contains the rollup (expand before saving). We recommend to our users that theyname this the same as their private subset, without the “udc_” prefix.Quirks: If you modify your original subset,the rollup will not automatically update withthose changes.Depending on how your security is setup,users might be able to spread from therollup.User Defined Consolidations (3)We modified the formulas for the product selection drop downs so that they can handle UDCs.The rollup element in the UDC does not have an index number within the dimension, so you can modify the formula for the first element to be equal to the subset name the user enters (the value in cell A15 in the template example).The UDC rollup is immediately available to the user in the template.•User can change the Year (cell P14 below) so that they can easily access historical data•Dynamic Actual / Forecast period headers determined by Time Control values•Conditional formatting used to display cells with Write access in white•Autocalc VBA to use Perspectives in Manual Calculation mode but behave like Automatic Calculation modeEvery time there’s a change it executes F9 behind the scenes for the userAutomatic calculation mode was exponentially slower with our models•Button that uses VBA to export the template to Excel as flat data Loops through the elements of the active product subset, pastes as values in new file Creates a separate tab for each element•To reduce overhead, most variance calculations only exist in Excel •Assigned a shortcut icon for Perspectives that’s different than Excel so that users can easily distinguish which Excel session is in Manual calc. mode Excel 2010 Example (this will launch the TM1 add-in within a new Excel session):Target: "C:\Program Files (x86)\Microsoft Office\Office14\EXCEL.EXE" "C:\Program Files\ibm\cognos\tm1\bin\tm1p.xla"Dan Thomas –Architect, Financial SystemsOther Tips•Use SUMIF or SUMIFS with Active Forms to create custom subtotals If you add a string element within a cube and Active Form, it can be used to store descriptions which can then be leveraged by SUMIF or SUMIFS formulas. These can be used to create “on the fly” customized subtotals in Excel. Since these descriptions are stored within the cube, the user only needs to enter them once and they are recalled any time they come back to the Active Form.Step 1 -Create a string element. This will need to be within the dimension ordered last within the cube. In this example I have added the “Group” element to the Store Sales Plan dimension (Go_New_Stores sample model).Step 2 -Add attributes relating to the appropriate number of groups you wish end users to be able to utilize. In this example, I have added Group 01, Group 02…Group 05 attributes to the Retailers dimension, in order to give end users the ability to see customized subtotals for up to 5 different product groups by Retailer.Other TipsUse SUMIF or SUMIFs with Active Forms (2)Step 3 -Add the string element to the Active Form with DBRWs so that any entry will be stored within the cube. In this example I have added a column for the Group element within an existing Active Form pointing to the Store Sales Plan cube. Step 4 –Several rows below the Active Form, add a section for the customized subtotals. Let the values of each row represent one of the attribute groups that you created, and add a DBRW to the attribute cube so that the end user can assign a value for each group as needed.In this example I have created 5 rows representing each of the 5 Group attributes. The Group column contains DBRWs which point to their corresponding group attribute (Group 01 -05) within the }ElementAttributes_Retailers cube.Other TipsUse SUMIF or SUMIFs with Active Forms (3)Step 5 -Use SUMIF or SUMIFS formulas to sum the values within the Active Form if it matches the description entered for each group attribute. The formulas must extend from the first data row within the Active Form through one line below the last data row. Use relative, not absolute references so that it becomes dynamic and adjusts to the changing number of rows as the Active Form is rebuilt.This becomes a much more powerful feature when a dimension representing context, such as an event, is present within the cube. In that case the subtotals are event specific, since the data represents the intersection of that particular product group within that event (using the Retailers dimension in the Go_New_Stores example was a less than ideal substitute).Other Tips•You can use Excel and VBA along with TM1 data to create Heat Maps by state, or any other geographic division in PerspectivesQ&ACopyright ©2017by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission from IBM.ernment Users Restricted Rights—use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM. Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors.IBM shall have no responsibility to update this information. This document is distributed “as is” without any warranty, either express or implied. In no event shall IBM be liable for any damage arising from the use of this information, including but not limited to, loss of data, business interruption, loss of profit or loss of opportunity. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided.IBM products are manufactured from new parts or new and used parts. In some cases, a product may not be new and may have been previously installed. Regardless, our warranty terms apply.”Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice. Performance data contained herein was generally obtained in a controlled, isolated environments.Customer examples are presentedas illustrations of how those customers have used IBM products and the results they may have achieved.Actual performance, cost, savings or other results in other operating environments may vary.References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business.Workshops, sessions and associated materials may have been prepared by independent session speakers,and do not necessarily reflect the views of IBM.All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation.It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as tothe identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actionsthe customer may need to take to comply with such laws.IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law.continuedInformation concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources.IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM’s products. IBM expressly disclaims all warranties, expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular, purpose.The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right.IBM, the IBM logo, ,Aspera®, Bluemix, Blueworks Live, CICS, Clearcase, Cognos®, DOORS®, Emptoris®,Enterprise Document Management System™, FASP®, FileNet®, Global Business Services®, Global Technology Services®, IBM ExperienceOne™, IBM SmartCloud®, IBM Social Business®, Information on Demand, ILOG, Maximo®, MQIntegrator®,MQSeries®,Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®,pureScale®, PureSystems®,QRadar®, Rational®, Rhapsody®, Smarter Commerce®, SoDA, SPSS, Sterling Commerce®, StoredIQ, Tealeaf®, Tivoli®Trusteer®, Unica®,urban{code}®, Watson, WebSphere®, Worklight®,X-Force®and System z®Z/OS, are trademarks of International Business Machines Corporation, registered 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 "Copyright and trademark information" at: /legal/copytrade.shtml.Thank you!。

力士乐减速机样本

力士乐减速机样本

INDICE INDEX INHALTSVERZEICHNISA Informazionigenerali GeneralinformationAllgemeineInformationen1SIMBOLOGIA SYMBOLS VERWENDETE SYMBOLE A-2 2IDENTIFICAZIONE DELPRODOTTOPRODUCT IDENTIFICATION PRODUKTKENNZEICHNUNG A-4 3CARATTERISTICHE TECNICHE TECHNICAL CHARACTERISTICS TECHNISCHE BESCHREIBUNG A-84SELEZIONE DEI RIDUTTORI RUOTA SELECTION OF THE WHEELGEARSAUSWAHL VOM RADNABEN-GETRIEBEA-185SCELTA DEL MOTORE IDRAU-LICO CHOOSING THE HYDRAULICMOTORAUSWAHL VOM HYDRAULIK-MOTORA-286VERIFICHE CHECKS KONTROLLEN A-30 7LUBRIFICAZIONE LUBRICATION SCHMIERUNG A-328IMBALLO, MOVIMENTAZIONE E STOCCAGGIO PACKING, HANDLING ANDSTORINGVERPACKUNG, TRANSPORTUND LAGERUNGA-389MONTAGGIO ASSEMBLY MONTAGE A-42 10CONTROLLI CHECKS KONTROLLEN A-46 11DISINNESTO DISENGAGEMENT AUSKUPPLUNG A-48 12MANUTENZIONE MAINTENANCE WARTUNG A-48 13INCONVENIENTI E RIMEDI TROUBLESHOOTING FUNKTIONSSTÖRUNGEN UNDBEHEBUNGA-52 14COPPIE IN USCITA OUTPUT TORQUES AUSGANGSDREHMOMENTE A-54B Dati tecnici edimensionali Technical and size data Technische Daten undAbmessungenRRTD RRTD RRTD B-3 RRWD RRWD RRWD B-15C Configurazioni entratae accessori iningresso Inlet configurations andaccessories in inputEingangskonfigurationund Zubehör im Eingang15FLANGIATURA PER MOTORE A NORME SAEJ 744C FLANGING FOR MOTOR TOSAEJ 744C STANDARDSFLANSCHUNG FÜR MOTOR NACHNORM SAEJ 744C C-216CONNESSIONE MOTORI CONNECTION OF MOTORS ANSCHLUSS MOTOR C-3 17RUOTE SPECIALI CUSTOMIZED WHEEL GEARS SONDERNGETRIEBE C-41SYMBOLES SIMBOLOGÍA SIMBOLOGIA A-32IDENTIFICATION DU PRODUIT IDENTIFICACIÓNDEL PRODUCTOIDENTIFICAÇÃODO PRODUTOA-53CARACTERISTIQUES TECHNIQUES CARACTERÍSTICASTÉCNICASCARACTERÍSTICASTÉCNICASA-94CHOIX DES REDUCTEURS ROUE SELECCIÓN DE LOS REDUC-TORES DE RUEDA SELECÇÃO DOS REDUTORESDA RODAA-195CHOIX DU MOTEUR HYDRAU-LIQUE SELECCIÓN DEL MOTORHIDRÁULICOESCOLHA DO MOTOR HI-DRÁULICOA-296VERIFICATIONS COMPROBACIONES VERIFICAÇÕES A-31 7 LUBRIFICATION LUBRICACIÓN LUBRIFICAÇÃO A-338EMBALLAGE, MANUTENTION ET STOCKAGE EMBALAJE, DESPLAZA-MIENTO Y ALMACENAMIENTOEMBALAGEM, MOVIMENTA-ÇÃO E ARMAZENAGEMA-399MONTAGE MONTAJE MONTAGEM A-43 10CONTROLES COMPROBACIONES CONTROLES A-47 11DEBRAYAGE DESEMBRAGUE DESENGATE A-49 12ENTRETIEN MANTENIMIENTO MANUTENÇÃO A-49 13INCONVENIENTS ET REMEDES INCONVENIENTES Y REMEDIOS INCONVENIENTES E SO-LUÇÕESA-53 14 COUPLES EN SORTIE PARES EN SALIDA PARES À SAÍDA A-54B Données techniqueset dimensionnelles Datos técnicos ydimensionalesDados tècnicos edimensŏesRRTD RRTD RRTD B-3 RRWD RRWD RRWD B-15C Configurations enentrée et accessoiresd’entrée Configuraciones deentrada y accesorios enentradaConfigurações à entradae acessórios à entrada15BRIDAGE POUR MOTEUR AUX NORMES SAEJ 744C BRIDAS PARA MOTOR SEGÚNNORMAS SAEJ 744CENTREAJUDAS PARA MOTORDE ACORDO COM AS NORMASSAEJ 744CC-216CONNEXION MOTEURS CONEXIÓN MOTORES CONEXÃO MOTORES C-3 17ROUES PERSONNALISÉES RUEDA PERSONALIZADOS RODA ESPECIAL C-4A Informazioni generaliGeneral information Allgemeine Informationen Informations générales Información generalInformações gerais1 SIMBOLOGIA 1 SYMBOLS 1 VERWENDETE SYMBOLE2 IDENTIFICAZIONE DEL PRODOTTO 2.1 Composizione di montaggio 2 PRODUCT IDENTIFICATION2.1 Assembly composition2 PRODUKTKENNZEICHNUNG2.1 Montage2.2 DesignazioneI riduttori ruota Reggiana Riduttori ven-gono identificati mediante una sigla com -posta nel seguente modo:2.2 DesignationThe Reggiana Riduttori wheel gears are identified by an acronym made up in the following way:2.2 BezeichnungDie Radnabengetriebe von Reggiana Riduttori sind durch einen Code gekenn-zeichnet, der folgende Bedeutung hat:2.3 Marcatura del prodotto e designazione del tipoTutti i prodotti Reggiana Riduttori sono dotati di targhetta metallica di identifica -zione, posizionata in modo da risultare facilmente leggibile, anche dopo l’instal-lazione.La seguente figura mostra un esempio di targhetta.LegendaLegendLegendeA Tipo di riduttore ruota (sigla)Wheel gear type (acronym)Typ Radnabengetriebe (Kürzel)B Codice identificativo di ordi -nazioneID code for ordering Identifizierungscode der BestellungC Rapporto di riduzione Reduction ratio UntersetzungsverhältnisD Coppia frenante Braking torqueBremsmomentE N° di ordine Order NumberAuftragsnummerN° progressivo di matricola e Progressive serial number Fortlaufende Seriennummer2.3 Product marking and type designationAll Reggiana Riduttori products have a metal id plate positioned so as to be eas-ily readable also after installation.The following figure shows an example of a plate.2.3 Produktkennzeichnung und TypenschildAlle Produkte von Reggiana Riduttori weisen ein Typenschild aus Metall auf, das so angebracht ist, dass es auch nach der Installation leicht abgelesen werden kann.Die Abbildung unten zeigt ein Beispiel.Leistungen Negativbremse Ohne Negativbremse Prefisso invariabile / Invariable prefix / Fixes Vorzeichen RR = REGGIANA RIDUTTORI2.3 Marquage du produitet désignation du typeSur tous les produits Reggiana Riduttori, une plaquette métallique d’identification est appliquée. Elle est positionnée de manière à être facile à lire, même une fois le réducteur installé.La figure suivante montre un exemple de la plaquette.2.3 Marcado del productoy denominación del tipoTodos los productos Reggiana Riduttorillevan una placa metálica de identifica-ción, colocada de manera que resultefácilmente legible, también después dela instalación.La siguiente figura presenta un ejemplode placa.2.3 Marcação do produtoe designação do tipoTodos os produtos Reggiana Riduttorisão munidos de placa metálica de iden-tificação, colocada de modo a ser lidacom facilidade, também depois da insta-lação.A seguinte figura ilustra um exemplo deplaca.Légende Leyenda LegendaA Type de réducteur roue (sigle)Tipo de reductor (sigla)Tipo de redutor (referência)B Code d’identification de lacommandeCódigo identificador depedidoCódigo identificativo deencomendaC Rapport de réduction Relación de reducción Relação de reduçãoD Couple freinant Par frenador Par de freioE N° de commande N° de pedido N° de ordemF N° progressif de série et année N° progresivo de matrícula y N° progressivo de matrículaPréfixe invariable / Prefijo invariable / Indicativo invariável RR = REGGIANA RIDUTTORI3 CARATTERISTICHE TECNICHE3.1 Funzioni generali, gamma di appli- cazioni e utilizzo previstoI riduttori ruota Reggiana Riduttori sono progettati per realizzare la trasmissione di potenza all’interno di macchine opera-trici. Essi possono essere collegati diret-tamente ad un motore di tipo elettrico o idraulico.I riduttori ruota vengono utilizzati nell’am-bito di diverse applicazioni, sia industriali che mobili, tra le quali: industria mecca-nica, industria chimica e plastica, indu-stria alimentare, edilizia e costruzioni, industria estrattiva, agricoltura e foreste, trasporti e sollevamento, settore marino, generatori eolici di energia.Utilizzare il riduttore soltanto per gli usi previsti in fase di progetto. L’impiego per usi impropri può essere causa di pericolo per la sicurezza e la salute delle persone. Gli usi previsti sono quelli industriali e mobili per i quali sono stati sviluppati e costruiti i riduttori.3.2Coppia in uscitaT2n[Nm]È il valore di coppia trasmissibile, in funzionamento continuo e uniforme, pari ad una durata teorica di 30000 n2.h. I valori di T2sono riportati nelle schede tecniche di ogni riduttore ruota. La coppia T2 è limitata dalla resistenza a flessione o dalla resistenza superficiale dei denti degli ingranaggi, in accordo con la norma ISO 6336.3.3Coppia in uscita massimaT2max [Nm]Rappresenta il valore di coppia massi-ma applicabile in uscita al riduttore ruota per brevi durate o per picchi occasiona-li, senza il verificarsi di danneggiamenti permanenti agli elementi più sollecitati.3.4Coppia in uscita richiestaT2r [Nm]È il valore di coppia in uscita che si inten-de applicare al riduttore ruota, in base ai dati di funzionamento dell’applicazione.3 TECHNICAL CHARACTERISTICS3 TECHNISCHE BESCHREIBUNG 3.1 General functions, range ofapplications and intended useThe Reggiana Riduttori wheel gears aredesigned for transmitting power insideoperating machines. They can be con-nected directly to either an electric or hy-draulic motor.The wheel gears are used for many dif-ferent types of application, both indus-trial and mobile some of which are: themechanical industry, the chemical andplastics industry, the food industry, build-ing and constructions, mining industry,agriculture and forestry, transporting andlifting, marine sector, wind generators ofenergy.Use the reduction gear only for the usescontemplated in the project phase. Usingit improperly can be the cause of dangerfor the safety and health of people.The reduction gears have been designedand made for the industrial and mobileuses.Die Radnabengetriebe dürfen nur für denvom Hersteller vorgesehenen Zweck ver-wendet werden. Bei unsachgemäßemGebrauch kann die Sicherheit und Ge-sundheit von Personen gefährdet werden.Unter vorgesehenem Gebrauch werdendie industriellen und mobilen Anwendun-gen verstanden, für die die Getriebe ent-wickelt und gebaut worden sind.3.1 Allgemeine Funktionen, Anwen-dungsbereiche und vorgeseheneAnwendungDie Radnabengetriebe von Reggia-na Riduttori werden für die Leistungs-übertragung im Inneren von Arbeits-maschinen konzipiert und gefertigt.Sie können direkt an einen Elektromotoroder einen Hydraulikmotor angeschlos-sen werden.Die Radnabengetriebe werden sowohlin der Industrie, als auch im Fahrzeug-bau in verschiedenen Anwendungeneingesetzt, darunter: Maschinenbau,chemische und Kunststoff verarbeitendeIndustrie, Lebensmittelindustrie, Bau-wirtschaft, Bergbau, Land- und Forst-wirtschaft, Transport- und Hubtechnik,Schiffbau, Windkraftanlagen.3.2 Output torqueT2n [Nm]This is the value of the torque which canbe transmitted in continuous and uniformoperation equalling a theoretical life of30000 n2.h. The T2values are given inthe technical data sheets of each wheelgear. T2torque is limited by resistanceto bending or by the surface resistanceof gear teeth, in agreement with the ISO6336 standard.3.3 Maximum output torqueT2max [Nm]It is the maximum torque value applicableto wheel gear output for short lengths oftime or for occasional peaks, without anypermanent damage to the most stressedelements.3.4 Required output torqueT2r[Nm]It is the torque value in output you intendapplying to the wheel gear, based on theapplication’s operating data.3.2AusgangsdrehmomentT2n[Nm]Dabei handelt es sich um das übertrag-bare Drehmoment bei gleichmäßigemDauerbetrieb, das einer theoretischenDauer von 30000 n2.h entspricht. DieWerte vom Drehmoment T2sind in dentechnischen Datenblättern der einzel-nen Radnabengetriebe angegeben. DasDrehmoment T2wird nach Vorgabe derNorm ISO 6336 vom Biegewiderstandoder vom Oberflächenwiderstand derZähne vom Getriebe begrenzt.3.3Maximales AusgangsdrehmomentT2max [Nm]Dabei handelt es sich um den Wertvom Drehmoment, das maximal amAusgang des Radnabengetriebes fürkurze Zeit oder gelegentliche Spitzenangelegt werden kann, ohne dass dieszu einer dauerhaften Schädigung deram stärksten Belasteten Bauteile führt.3.4Verlangtes AusgangsdrehmomentT2r [Nm]Dabei handelt es sich um das Ausgangs-drehmoment, das an das Radnabenge-triebe je nach Funktionswerten der An-wendung angelegt werden soll.applications, aussi bien dans le domaine industriel que mobile, parmi lesquelles: l’industrie mécanique, l’industrie chimi-que et plastique, l’industrie alimentaire, le bâtiment et les constructions, l’industrie extractive, l’agriculture et la sylviculture, le transport et les systèmes de levage, la marine, les générateurs éoliens.N’utiliser le réducteur que pour les usa-ges pour lesquels il a été projeté. Son utilisation impropre peut être cause de danger pour la sécurité et la santé des personnes.Les usages prévus sont les emplois in-dustriels et mobiles pour lesquels les ré-ducteurs ont été élaborés et fabriqués.3.2 Couple de sortie T 2n [Nm]C’est la valeur du couple qui peut être transmis dans des conditions de fonc-tionnement continu et uniforme équiva-lant à une durée théorique de 30000 n 2xh. Les valeurs de T 2 sont indiquées sur les fiches techniques de chaque réducteur roue.Le couple T 2 est limité par la résistance à la flexion ou par la résistance de la sur -face des dents des engrenages, confor-mément à la norme ISO 6336.3.3 Couple à la sortie maximum T 2max [Nm]Il représente la valeur de couple maxi-mum applicable à la sortie au réducteur pour de courtes durées ou pour des pics occasionnels, sans provoquer de dom-mages permanents aux éléments les plus sollicités.3.4 Couple de sortie demandé T 2r [Nm]C’est la valeur de couple de sortie qu’on souhaite appliquer au réducteur roue, en fonction des données de fonctionnement de l’application.el ámbito de distintas aplicaciones, tanto industriales como móviles, entre las cua-les: industria mecánica, industria quími-ca y del plástico, industria alimentaria, de la construcción, industria minera, agricul-tura y forestal, transportes y elevación, sector marítimo, generadores eólicos deenergía.Utilizar el reductor sólo para los usos pre-vistos en la fase de proyecto. La utiliza-ción para usos no adecuados puede cau-sar peligros para la seguridad y la salud de las personas.Los usos previstos son aquellos indus-triales y móviles para los cuales han sido desarrollados y construidos los reducto-res.Usar o redutor exclusivamente para os usos previstos na fase de projecto. O emprego em usos impróprios pode ser causa de perigo para a segurança e a saúde das pessoas.Os usos previstos são aqueles industriais e móveis para os quais os redutores fo-ram concebidos e construídos.âmbito de várias aplicações, quer indus-triais quer móveis, entre as quais: indús-tria mecânica, indústria química e dos plásticos, indústria alimentar, constru-ção civil, indústria minerária, agricultura e florestas, transportes e levantamento, sector marítimo, geradores eólicos de energia.3.2 Par en salida T 2n [Nm]Es el valor del par transmisible en fun-cionamiento continuo y uniforme, equi-valente a una duración teórica de 30000 n 2 x h. Los valores de T 2 son indicados en las fichas técnicas de cada reductor de rueda.El par T 2 está limitado por la resistencia a la flexión o por la resistencia superficial de los dientes de los engranajes, según la norma ISO 6336.3.3 Par en salida máximo T 2max [Nm]Representa el valor de par máximo apli-cable en salida al reductor de rueda por breves duraciones o por picos ocasio-nales, sin que se produzcan daños per-manentes a los elementos mayormente bajo esfuerzo.3.4 Par en salida requerido T 2r [Nm]Es el valor de par en salida que se de-sea aplicar al reductor de rueda, sobre la base de los datos de funcionamiento de la aplicación.3.2 Par à saída T 2n [Nm]É o valor de par transmissível, em fun-cionamento contínuo e uniforme,igual a uma duração teórica de 30000 n 2.h .Os valores de T 2 são indicados nas fi -chas técnicas de cada redutor da roda.O par T 2 é limitado pela resistência à flexão ou pela resistência superficial dos dentes das engrenagens, de acordo com a norma ISO 6336.3.3 Par em saída máximo T 2max [Nm]Representa o valor de par máximo aplicá-vel em saída ao redutor por breves perío-dos ou por picos ocasionais, sem que se verifiquem danos permanentes nos ele -mentos mais solicitados.3.4 Par à saída exigido T 2r [Nm]É o valor de par à saída que se tenciona aplicar ao redutor da roda, com base nos dados de funcionamento da aplicação.3.5 Velocità in entrata n 1 [min -1]È la velocità del motore collegato in in-gresso al riduttore ruota.3.6 Velocità in uscita n 2 [min -1]È la velocità in uscita del riduttore, fun-zione della velocità in entrata n 1 e del rapporto di riduzione effettivo i.3.7 Rapporto di riduzione iIndica l’effettivo rapporto tra la velocità in entrata n 1 e la velocità in uscita n 2 del riduttore ruota:I rapporti di riduzione disponibili sono riportati nella tabella dei dati tecnici per ogni grandezza di riduttore ruota. Su ri-chiesta è possibile ottenere ulteriori rap-porti di riduzione.3.8 Velocità in entrata massima n 1max [min -1]Indica la velocità massima ammessa in entrata per brevi durate o in funziona-mento intermittente; la velocità in entrata del riduttore ruota è limitata dalla velocità periferica degli ingranaggi, dai cuscinetti e dalle tenute.3.9 Verso di rotazioneIn generale, per ogni riduttore ruota di questo catalogo, l’uscita gira in senso opposto all’albero entrata. Fa eccezione il riduttore ruota RRWD270/B nel quale, a causa del particolare funzionamento interno, l’uscita gira nello stesso senso dell’ingresso.3.10 Potenza in entrata P 1 [kW]È la potenza applicata in ingresso al ri-duttore ruota, mediante collegamento diretto di un motore.3.5 Input speed n 1 [min -1]It is the speed of the motor connected to the wheel gear at input.3.6 Output speed n 2 [min -1]It is the reduction gear’s output speed as a function of the input speed n 1 and of the actual reduction ratio i.3.7 Reduction ratio iIt indicates the actual ratio between the wheel gear’s input speed n 1 and output speed n 2:The reduction ratios available are given in the technical data table for each wheel gear size. Other reduction ratios can be obtained on request.3.8 Maximum input speed n 1max [min -1]It indicates the maximum permitted input speed for short lengths of time or intermit-tently; the wheel gear’s input speed is lim-ited by the peripheral speed of the gears, by the bearings and by the seals.3.9 Rotation directionGenerally, for each wheel gear in this cat-alogue, the output turns in the opposite direction to the input shaft. An exception to this rule is wheel gear RRWD270/B where, due to its particular internal work-ing, the output turns in the same direction as the input.3.10 Input power P 1 [kW]It is the power applied to the wheel gear at input by means of the direct connec-tion of a motor.3.5 Eingangsgeschwindigkeit n 1 [min -1]Dabei handelt es sich um die Geschwin-digkeit vom Motor, der am Eingang vom Radnabengetriebe angeschlossen ist.3.6 Ausgangsgeschwindigkeit n 2 [min -1]Dabei handelt es sich um die Geschwin-digkeit der Ausgangswelle vom Radna-bengetriebe, die sich aus der Eingangs-geschwindigkeit n 1 und dem effektiven Untersetzungsverhältnis i ergibt.3.7 Untersetzungsverhältnis iDabei handelt es sich um das effektive Verhältnis von Eingangsgeschwindigkeit n 1 zu Ausgangsgeschwindigkeit n 2 vom Radnabengetriebe:Die verfügbaren Untersetzungsverhält-nisse sind für jede Größe vom Radna-bengetriebe in der Tabelle mit den tech-nischen Daten zusammengestellt. Auf Wunsch sind weitere Untersetzungsver-hältnisse erhältlich.3.8 Maximale Eingangsgeschwindigkeit n 1max [min -1]Dabei handelt es sich um die maximal zulässige Eingangsgeschwindigkeit für kurze Dauer oder bei unterbrochenem Betrieb. Die Eingangsgeschwindigkeit vom Radnabengetriebe ist durch die Pe-ripheriegeschwindigkeit von Zahnrädern, Lagern und Dichtungen beschränkt.3.9 RotationsrichtungAllgemein gilt für jedes Radnabengetrie-be des vorliegenden Katalogs, dass sich der Ausgang in die entgegen gesetzte Richtung dreht wie die Eingangswelle. Eine Ausnahme bildet das Radnaben-getriebe RRWD270/B, bei welchem sich aufgrund der speziellen Bauweise der Ausgang in die gleiche Richtung wie die Eingangswelle dreht.3.10 Eingangsleistung P 1 [kW]Dabei handelt es sich um die Leistung, die am Eingang vom Radnabengetriebe durch den direkten Anschluss an einen Motor angelegt wird.du réducteur, en fonction de la vitesse à l’entrée n 1 et du rapport de réduction ef-fectif i.3.7 Rapport de réduction iIl indique le rapport effectif entre la vites-se à l’entrée n 1 et la vitesse à la sortie n 2 du réducteur roue:Les rapports de réduction existants sont indiqués dans le tableau des caractéris-tiques techniques pour chaque grandeur de réducteur roue. Sur demande, il est possible d’obtenir des rapports de réduc-tion supplémentaires.3.8 Vitesse à maximum à l’entrée n 1max [min -1]Elle indique la vitesse maximum admise à l’entrée pour de courtes durées ou en fonctionnement intermittent; la vitesse à l’entrée du réducteur roue est limitée par la vitesse périphérique des engrenages, par les roulements et les garnitures.3.9 Sens de rotationEn général, pour tous les réducteurs roue de ce catalogue, l’arbre de sortie tourne dans le sens inverse de celui de l’arbre d’entrée, à l’exception du réducteur roue RRWD270/B dans lequel, en raison du fonctionnement interne particulier, l’arbre de sortie tourne dans le même sens que l’arbre d’entrée.3.10 Puissance à l’entrée P 1 [kW]C’est la puissance appliquée à l’entrée du réducteur roue, par un raccord direct d’un moteur.función de la velocidad en entrada n 1 y de la relación de reducción efectiva i.3.7 Relación de reducción iIndica la efectiva relación entre la veloci-dad en entrada n 1 y la velocidad en sali-da n 2 del reductor de rueda:Las relaciones de reducción disponibles se indican en la tabla de los datos técni-cos para cada talla de reductor de rueda. Bajo demanda es posible obtener ulterio-res relaciones de reducción.3.8 Velocidad en entrada máxima n 1max [min -1]Indica la velocidad máxima admitida en entrada por breves duraciones o en fun-cionamiento intermitente; la velocidad en entrada del reductor de rueda está limitada por la velocidad periférica de los engranajes, por los cojinetes y por las estanqueidades.3.9 Sentido de giroEn general, para cada reductor de rueda de este catálogo, la salida gira en senti-do opuesto al eje de entrada.La excepción es el reductor de rueda RRWD270/B en el cual, debido al funcio-namiento interno particular, la salida gira en el mismo sentido que la entrada.3.10 Potencia en entrada P 1 [kW]Es la potencia aplicada en entrada al re-ductor de rueda, mediante conexión di-recta de un motor.tor, função da velocidade em entrada n 1 e da relação de redução efetiva i.3.7 Relação de redução iIndica a efectiva relação entre a veloci-dade em entrada n 1 e a velocidade em saída n 2 do redutor da roda:As relações de redução disponíveis es-tão indicadas na tabela dos dados téc-nicos para cada grandeza do redutor da roda. A pedido, é possível obter outras relações de redução.3.8 Velocidade em entrada máxima n 1max [min -1]Indica a velocidade máxima admitida em entrada por breves períodos ou em funcionamento intermitente; a veloci-dade em entrada do redutor da roda é limitada pela velocidade periférica das engrenagens, pelos rolamentos e pelas vedações.3.9 Direcção de rotaçãoEm geral, para cada redutor da roda des-te catálogo, a saída rodeia em sentido contrário à árvore da entrada.Com excepção do redutor da roda RRWD270/B no qual, devido ao funcio-namento especial interno, a saída rodeia no mesmo sentido da entrada.3.10 Potência em entrada P 1 [kW]É a potência aplicada à entrada ao redu-tor da roda, mediante ligação directa de um motor.3.12 Rendimento ηE' un coefficiente adimensionale dato dal rapporto tra la potenza in uscita P 2 e quella in entrata P 1:Il valore di rendimento di un singolo sta-dio di riduzione, in condizioni medie di velocità e coppia, è pari a 0.975; tale valore decresce nel caso di: incremento della velocità, diminuzione della coppia trasmessa, aumento della temperatura ambiente.3.13 Carico radiale in uscita F r2 [N]In corrispondenza di ogni singola sche-da tecnica è riportata la curva dei carichi radiali ammissibili F r,2 in funzione della ascissa x (distanza da un riferimento op-portuno). Il valore di carico radiale am-missibile è riferito ad una durata dei cu-scinetti, calcolata in base alla norma ISO 281, pari a 300000 n 2.h.Tutte le curve dei carichi radiali ammis-sibili sono state fatte imponendo che i carichi assiali F a,2 siano nulli.3.14 Carico assiale in uscita F a,2 [N]Su tutte le tipologie di riduttore ruota è ammessa la presenza di un carico assia-le in verso entrante o uscente.In presenza di carico assiale, verificare l’idoneità del riduttore ruota contattando il Servizio Tecnico Reggiana Riduttori.3.12 Efficiency ηIt is a dimensionless coefficient given by the ratio between the output powerP 2 and input power P 1:The efficiency value of a single reduction stage under average speed and torque conditions, is equivalent to 0.975; this value decreases if: speed increases, transmitted torque diminishes, ambient temperature increases.3.13 Radial load in output F r2 [N]The curve of the permissible radial loads F r,2 as a function of abscissa x (distance from a suitable reference) is given whe-re each single technical datasheet is. The permissible radial load value refers to bearing life calculated on the basis of the ISO281 standard which is equal to 300000 n 2.h.All curves of the permissible radial loads have been done taking the axial loads F a,2 as nil.3.14 Output axial load F a,2 [N]An axial load, in input or output, is al-lowed on all wheel gear types.When there is an axial load check that the wheel gear is suitable, contacting the Reggiana Riduttori Technical Service.3.12 Wirkungsgrad ηDabei handelt es sich um einen dimen-sionslosen Wert, der sich aus dem Ver-hältnis der Ausgangsleistung P 2 zur Eingangsleistung P 1 ergibt:Der Wert vom Wirkungsgrad einer ein-zelnen Untersetzungsstufe bei mittle-rer Geschwindigkeit und Drehmoment entspricht 0.975. Dieser Wert nimmt bei zunehmender Geschwindigkeit, abneh-mendem anliegendem Drehmoment und zunehmender Umgebungstemperatur ab.3.13 Querlast am Ausgang F r2 [N]In den einzelnen technischen Datenblät-tern ist die Kurve der zulässigen Quer-lasten F r,2 in Abhängigkeit der X-Achse (Abstand von einem geeigneten Bezugs-punkt) abgetragen. Der Wert der zuläs-sigen Querlast bezieht sich auf eine Le-bensdauer der Lager von 300000 n 2.h., die nach Vorgabe der Norm ISO 281 be-rechnet wird.Alle Kurven der zulässigen Querlasten wurden unter der Voraussetzung erstellt, dass die Achslasten F a,2 gleich Null sind.3.14 Achslast am Ausgang F a,2 [N]An allen Radnabengetrieben ist eine Achslast in Eingangs- oder Ausgangs-richtung zulässig.Bei Achslast die Eignung vom Radna-bengetriebe prüfen und dazu den Tech-nischen Kundendienst von Reggiana Ri-3.11 Potenza in uscita P 2 [kW]È la potenza richiesta dall’utilizzatore col-legato in uscita al riduttore ruota. Si può calcolare come: 3.11 Output power P 2 [kW]It is the power required by the user con-nected to the wheel gear in output. It can be calculated as:3.11 Ausgangsleistung P 2 [kW]Dabei handelt es sich um die Leistung, die vom Abnehmer verlangt wird, der am Ausgang vom Radnabengetriebe an-geschlossen ist und wie folgt berechnet wird:。

伊斯姆兹（Isuzu）中型货车和拖车产品目录说明书

伊斯姆兹（Isuzu）中型货车和拖车产品目录说明书

4HK1-TCC / -TCS 6HK1-TCN / -TCS910 Visibility and protection from every angleEnhanced brakingExtra-large front and rear drum brakes improve braking performanceand are carefully matched to meet the requirements of each model.Designed for easy maintenanceWhen there is a big job, FORWARD will be ready.The quick access front panel facilitates routine replenishment of clutchand washer fluids as well as brake valve maintenance.Cleaning the windshield is a snapA full-length bumper step and hand grips take the hard work out ofcleaning the windshield. The bumper step and grips also offer steadysupport for adjustment of mirrors. For remote adjustment from insidethe cab, power mirrors are available.Simplified fluid inspection and other service workChecking fluids is simple. An engine oil inspection port is located at theback of the cab, along with brake fluid and long-life coolant reservoirs.The relay box is also conveniently placed at the back of the cab forstraightforward inspection. Even fuse replacement inside the cab belowthe instrument panel is easy, thanks to a cartridge-type fuse box.Backing safety systemIn reverse gear, the backing safety system is triggered automatically;lamps flash and a buzzer sounds to warn pedestrians and other vehicles.Safe stopping and parking at all timesOptional exhaust braking guarantees safe stopping even when fully loaded,while the parking brake lever locks wheels firmly in place.Greater illumination from headlamps / fog lampsLarger headlamp bulbs provide better forward illumination during nighttime operation,while fog lamps increase the level of safety in bad weather.The exceptional visibility of highly rigid FORWARD cabs is due in part to their boxy design,which increases window area. Upward and downward forward visibility is first-rate,and large side mirrors give excellent rear views. Defrosters keep side windows clear.1112 3,700mm wheelbase (FSR model)Easy handling and precision controlTight turning radiusWith a maximum steering angle of 57 degrees and reduced front overhang,FORWARD can maneuver with precision in congested areas and tight quarters.Power steering / adjustable columnPower steering and tilt / telescopic column adjustment are standard,helping to reduce driver fatigue.Suspended brake pedalSuspending the brake pedal provides a more natural, car-like driving experience.It also allows the brake valve to be placed in the quick access area for easiermaintenance without tilting the cab.High-visibility meters, simple operationMeters are located in the center for superior visibility,allowing drivers to confirm vehicle status at a glance.Surrounding switches are designed for easy control.FORWARD takes handling and control to the next level.Chassis and drivetrain enhancements work together with easy-to-read indicators andswitches to give unmatched control over vehicle operations.Day in and day out, drivers will appreciate the flawless handling and easy operation.Crawler gear to move big loadsOn higher GVM models equipped with the ZF9S1110 transmission,a crawler gear provides the power to move heavy, oversize loads.Smooth and effortless shiftingRefinements to the master cylinder reduce the effort involved inmanual shifting and ensure a smooth ride.Reliability and durability are also enhanced.Inter differential lock /center differential lock /4WD switchesFor maximum drive-axle traction in extreme conditions, two separatedifferential locks are available along with a 4WD driving system.Just flip the dash-mounted switches when conditions call fora sure grip in slippery spots.70°1718 Line upGVM 10.4ton4x2 DRIVING SYSTEM6x2 DRIVING SYSTEM6x4 DRIVING SYSTEMFRR4x4 DRIVING SYSTEMGVM 25.0tonFVM GVM 25.0tonFVZGVM 13.0tonFTS4HK1-TCC, 4HK1-TCS, 6HK1-TCN, 6HH1-S4HK1-TCS6HK1-TCN, 6HK1-TCS6HK1-TCS4HK1-TCS, 6HK1-TCN, 6HH1-S6HK1-TCN, 6HH1-SGVM 11.0ton/13.0tonFSR4x4 DRIVING SYSTEMGVM 10.0tonFSS4x2 DRIVING SYSTEM*Disc wheel step is optionalBumper headlamps (FVR33 model)。

融合多源数据与元胞传输模型的高速公路交通状态估计方法

融合多源数据与元胞传输模型的高速公路交通状态估计方法

第21卷第4期2023年12月交通运输工程与信息学报Journal of Transportation Engineering and InformationVol.21No.4Dec.2023文章编号：1672-4747（2023）04-0103-12融合多源数据与元胞传输模型的高速公路交通状态估计方法易术*，黄丹阳（四川智能交通系统管理有限责任公司，成都610200）摘要：针对高速公路管控和决策应对交通状态进行准确、可靠和精细化估计的需求，本文提出了一种基于多源数据+元胞传输模型（Multi-Source Data Cell Transmission Model，MD-CTM）的交通状态估计方法。

该方法针对传统CTM模型要求元胞长度必须一致的局限性，提出了一种元胞长度划分的优化方法，能够灵活调整元胞长度和数量。

同时，应用卡尔曼滤波技术，将ETC门架流量、稀疏视频检测器流量和样本车辆平均速度数据融合，并与CTM模型相结合，实现高速公路元胞级交通状态估计。

为了验证本文提出方法的有效性和准确性，我们利用VISSIM软件构建了长度5km的高速公路仿真场景。

仿真案例结果表明，本文提出的MD-CTM模型能够较为准确地反映不同流量需求下交通流状态的时空演化特征，且相较于CTM模型，其元胞密度估计精度提高12.59%~36.26%。

此外，本文选取了成都市绕城高速路段实际场景，对模型的运行效果进行了展示。

关键词：智能交通；交通状态估计；卡尔曼滤波；元胞传输模型；多源数据融合中图分类号：U495文献标志码：A DOI:10.19961/ki.1672-4747.2023.08.001Freeway traffic state estimation based on multi-source data andcell transmission modelYI Shu*,HUANG Dan-yang（Sichuan Intelligent Transport System Management Co.,Ltd.,Chengdu610200,China）Abstract：Accurate,reliable,and efficient traffic state estimation is essential for effective freeway management and decision-making.This study presents a traffic state estimation method called MD-CTM,which combines multi-source data and the cell transmission model(CTM).As the traditional CTM has limitations owing to fixed cell lengths,we propose a cell division approach that allows for flexible lengths and numbers.To enhance the accuracy of traffic state estimation,we utilize the Kal-man filtering technique to fuse different types of traffic data,including traffic flow from the electron-ic toll collection system and sparse video detectors,and an average link speed with the CTM to achieve cell-level traffic state estimation on freeways.To evaluate the performance of the proposed approach,we conducted simulations using VISSIM on a freeway section of5km.The simulation re-sults show that the proposed MD-CTM model improves the accuracy of cell density estimation by12.59%~36.26%compared with the CTM model.Furthermore,our model effectively captures thespatio-temporal evolution characteristics of traffic flow states under different traffic demand condi-收稿日期：2023-08-07录用日期：2023-08-25网络首发：2023-09-12审稿日期：2023-08-07~2023-08-09；2023-08-17~2023-08-25基金项目：国家重点研发计划项目（2021YFB1600100）作者简介：黄丹阳（1988—），男，硕士，高级工程师，研究方向为交通智能控制、内模与预测控制，E-mail:****************通信作者：易术（1970—），男，硕士，高级工程师，研究方向为交通工程、智慧交通，E-mail:****************引文格式：易术，黄丹阳.融合多源数据与元胞传输模型的高速公路交通状态估计方法[J].交通运输工程与信息学报，2023，21(4)：103-114.YI Shu,HUANG Dan-yang.Freeway traffic state estimation based on multi-source data and cell transmission model[J].Journal of Transportation Engineering and Information，2023，21(4)：103-114.104交通运输工程与信息学报第21卷tions.Moreover,a real-world scenario of Chengdu city is used to further demonstrate the effective-ness of our proposed approach.Key words：intelligent transportation;traffic state estimation;Kalman filter;cell transmission model;multi-source data fusion0引言高速公路交通状态估计是交通领域中的一个重要研究方向。

Native Instruments MASCHINE MIKRO MK3用户手册说明书

Native Instruments MASCHINE MIKRO MK3用户手册说明书

The information in this document is subject to change without notice and does not represent a commitment on the part of Native Instruments GmbH. The software described by this docu-ment is subject to a License Agreement and may not be copied to other media. No part of this publication may be copied, reproduced or otherwise transmitted or recorded, for any purpose, without prior written permission by Native Instruments GmbH, hereinafter referred to as Native Instruments.“Native Instruments”, “NI” and associated logos are (registered) trademarks of Native Instru-ments GmbH.ASIO, VST, HALion and Cubase are registered trademarks of Steinberg Media Technologies GmbH.All other product and company names are trademarks™ or registered® trademarks of their re-spective holders. Use of them does not imply any affiliation with or endorsement by them.Document authored by: David Gover and Nico Sidi.Software version: 2.8 (02/2019)Hardware version: MASCHINE MIKRO MK3Special thanks to the Beta Test Team, who were invaluable not just in tracking down bugs, but in making this a better product.NATIVE INSTRUMENTS GmbH Schlesische Str. 29-30D-10997 Berlin Germanywww.native-instruments.de NATIVE INSTRUMENTS North America, Inc. 6725 Sunset Boulevard5th FloorLos Angeles, CA 90028USANATIVE INSTRUMENTS K.K.YO Building 3FJingumae 6-7-15, Shibuya-ku, Tokyo 150-0001Japanwww.native-instruments.co.jp NATIVE INSTRUMENTS UK Limited 18 Phipp StreetLondon EC2A 4NUUKNATIVE INSTRUMENTS FRANCE SARL 113 Rue Saint-Maur75011 ParisFrance SHENZHEN NATIVE INSTRUMENTS COMPANY Limited 5F, Shenzhen Zimao Center111 Taizi Road, Nanshan District, Shenzhen, GuangdongChina© NATIVE INSTRUMENTS GmbH, 2019. All rights reserved.Table of Contents1Welcome to MASCHINE (23)1.1MASCHINE Documentation (24)1.2Document Conventions (25)1.3New Features in MASCHINE 2.8 (26)1.4New Features in MASCHINE 2.7.10 (28)1.5New Features in MASCHINE 2.7.8 (29)1.6New Features in MASCHINE 2.7.7 (29)1.7New Features in MASCHINE 2.7.4 (31)1.8New Features in MASCHINE 2.7.3 (33)2Quick Reference (35)2.1MASCHINE Project Overview (35)2.1.1Sound Content (35)2.1.2Arrangement (37)2.2MASCHINE Hardware Overview (40)2.2.1MASCHINE MIKRO Hardware Overview (40)2.2.1.1Browser Section (41)2.2.1.2Edit Section (42)2.2.1.3Performance Section (43)2.2.1.4Transport Section (45)2.2.1.5Pad Section (46)2.2.1.6Rear Panel (50)2.3MASCHINE Software Overview (51)2.3.1Header (52)2.3.2Browser (54)2.3.3Arranger (56)2.3.4Control Area (59)2.3.5Pattern Editor (60)3Basic Concepts (62)3.1Important Names and Concepts (62)3.2Adjusting the MASCHINE User Interface (65)3.2.1Adjusting the Size of the Interface (65)3.2.2Switching between Ideas View and Song View (66)3.2.3Showing/Hiding the Browser (67)3.2.4Showing/Hiding the Control Lane (67)3.3Common Operations (68)3.3.1Adjusting Volume, Swing, and Tempo (68)3.3.2Undo/Redo (71)3.3.3Focusing on a Group or a Sound (73)3.3.4Switching Between the Master, Group, and Sound Level (77)3.3.5Navigating Channel Properties, Plug-ins, and Parameter Pages in the Control Area.773.3.6Navigating the Software Using the Controller (82)3.3.7Using Two or More Hardware Controllers (82)3.3.8Loading a Recent Project from the Controller (84)3.4Native Kontrol Standard (85)3.5Stand-Alone and Plug-in Mode (86)3.5.1Differences between Stand-Alone and Plug-in Mode (86)3.5.2Switching Instances (88)3.6Preferences (88)3.6.1Preferences – General Page (89)3.6.2Preferences – Audio Page (93)3.6.3Preferences – MIDI Page (95)3.6.4Preferences – Default Page (97)3.6.5Preferences – Library Page (101)3.6.6Preferences – Plug-ins Page (109)3.6.7Preferences – Hardware Page (114)3.6.8Preferences – Colors Page (114)3.7Integrating MASCHINE into a MIDI Setup (117)3.7.1Connecting External MIDI Equipment (117)3.7.2Sync to External MIDI Clock (117)3.7.3Send MIDI Clock (118)3.7.4Using MIDI Mode (119)3.8Syncing MASCHINE using Ableton Link (120)3.8.1Connecting to a Network (121)3.8.2Joining and Leaving a Link Session (121)4Browser (123)4.1Browser Basics (123)4.1.1The MASCHINE Library (123)4.1.2Browsing the Library vs. Browsing Your Hard Disks (124)4.2Searching and Loading Files from the Library (125)4.2.1Overview of the Library Pane (125)4.2.2Selecting or Loading a Product and Selecting a Bank from the Browser (128)4.2.3Selecting a Product Category, a Product, a Bank, and a Sub-Bank (133)4.2.3.1Selecting a Product Category, a Product, a Bank, and a Sub-Bank on theController (137)4.2.4Selecting a File Type (137)4.2.5Choosing Between Factory and User Content (138)4.2.6Selecting Type and Character Tags (138)4.2.7Performing a Text Search (142)4.2.8Loading a File from the Result List (143)4.3Additional Browsing Tools (148)4.3.1Loading the Selected Files Automatically (148)4.3.2Auditioning Instrument Presets (149)4.3.3Auditioning Samples (150)4.3.4Loading Groups with Patterns (150)4.3.5Loading Groups with Routing (151)4.3.6Displaying File Information (151)4.4Using Favorites in the Browser (152)4.5Editing the Files’ Tags and Properties (155)4.5.1Attribute Editor Basics (155)4.5.2The Bank Page (157)4.5.3The Types and Characters Pages (157)4.5.4The Properties Page (160)4.6Loading and Importing Files from Your File System (161)4.6.1Overview of the FILES Pane (161)4.6.2Using Favorites (163)4.6.3Using the Location Bar (164)4.6.4Navigating to Recent Locations (165)4.6.5Using the Result List (166)4.6.6Importing Files to the MASCHINE Library (169)4.7Locating Missing Samples (171)4.8Using Quick Browse (173)5Managing Sounds, Groups, and Your Project (175)5.1Overview of the Sounds, Groups, and Master (175)5.1.1The Sound, Group, and Master Channels (176)5.1.2Similarities and Differences in Handling Sounds and Groups (177)5.1.3Selecting Multiple Sounds or Groups (178)5.2Managing Sounds (181)5.2.1Loading Sounds (183)5.2.2Pre-listening to Sounds (184)5.2.3Renaming Sound Slots (185)5.2.4Changing the Sound’s Color (186)5.2.5Saving Sounds (187)5.2.6Copying and Pasting Sounds (189)5.2.7Moving Sounds (192)5.2.8Resetting Sound Slots (193)5.3Managing Groups (194)5.3.1Creating Groups (196)5.3.2Loading Groups (197)5.3.3Renaming Groups (198)5.3.4Changing the Group’s Color (199)5.3.5Saving Groups (200)5.3.6Copying and Pasting Groups (202)5.3.7Reordering Groups (206)5.3.8Deleting Groups (207)5.4Exporting MASCHINE Objects and Audio (208)5.4.1Saving a Group with its Samples (208)5.4.2Saving a Project with its Samples (210)5.4.3Exporting Audio (212)5.5Importing Third-Party File Formats (218)5.5.1Loading REX Files into Sound Slots (218)5.5.2Importing MPC Programs to Groups (219)6Playing on the Controller (223)6.1Adjusting the Pads (223)6.1.1The Pad View in the Software (223)6.1.2Choosing a Pad Input Mode (225)6.1.3Adjusting the Base Key (226)6.2Adjusting the Key, Choke, and Link Parameters for Multiple Sounds (227)6.3Playing Tools (229)6.3.1Mute and Solo (229)6.3.2Choke All Notes (233)6.3.3Groove (233)6.3.4Level, Tempo, Tune, and Groove Shortcuts on Your Controller (235)6.3.5Tap Tempo (235)6.4Performance Features (236)6.4.1Overview of the Perform Features (236)6.4.2Selecting a Scale and Creating Chords (239)6.4.3Scale and Chord Parameters (240)6.4.4Creating Arpeggios and Repeated Notes (253)6.4.5Swing on Note Repeat / Arp Output (257)6.5Using Lock Snapshots (257)6.5.1Creating a Lock Snapshot (257)7Working with Plug-ins (259)7.1Plug-in Overview (259)7.1.1Plug-in Basics (259)7.1.2First Plug-in Slot of Sounds: Choosing the Sound’s Role (263)7.1.3Loading, Removing, and Replacing a Plug-in (264)7.1.4Adjusting the Plug-in Parameters (270)7.1.5Bypassing Plug-in Slots (270)7.1.6Using Side-Chain (272)7.1.7Moving Plug-ins (272)7.1.8Alternative: the Plug-in Strip (273)7.1.9Saving and Recalling Plug-in Presets (273)7.1.9.1Saving Plug-in Presets (274)7.1.9.2Recalling Plug-in Presets (275)7.1.9.3Removing a Default Plug-in Preset (276)7.2The Sampler Plug-in (277)7.2.1Page 1: Voice Settings / Engine (279)7.2.2Page 2: Pitch / Envelope (281)7.2.3Page 3: FX / Filter (283)7.2.4Page 4: Modulation (285)7.2.5Page 5: LFO (286)7.2.6Page 6: Velocity / Modwheel (288)7.3Using Native Instruments and External Plug-ins (289)7.3.1Opening/Closing Plug-in Windows (289)7.3.2Using the VST/AU Plug-in Parameters (292)7.3.3Setting Up Your Own Parameter Pages (293)7.3.4Using VST/AU Plug-in Presets (298)7.3.5Multiple-Output Plug-ins and Multitimbral Plug-ins (300)8Using the Audio Plug-in (302)8.1Loading a Loop into the Audio Plug-in (306)8.2Editing Audio in the Audio Plug-in (307)8.3Using Loop Mode (308)8.4Using Gate Mode (310)9Using the Drumsynths (312)9.1Drumsynths – General Handling (313)9.1.1Engines: Many Different Drums per Drumsynth (313)9.1.2Common Parameter Organization (313)9.1.3Shared Parameters (316)9.1.4Various Velocity Responses (316)9.1.5Pitch Range, Tuning, and MIDI Notes (316)9.2The Kicks (317)9.2.1Kick – Sub (319)9.2.2Kick – Tronic (321)9.2.3Kick – Dusty (324)9.2.4Kick – Grit (325)9.2.5Kick – Rasper (328)9.2.6Kick – Snappy (329)9.2.7Kick – Bold (331)9.2.8Kick – Maple (333)9.2.9Kick – Push (334)9.3The Snares (336)9.3.1Snare – Volt (338)9.3.2Snare – Bit (340)9.3.3Snare – Pow (342)9.3.4Snare – Sharp (343)9.3.5Snare – Airy (345)9.3.6Snare – Vintage (347)9.3.7Snare – Chrome (349)9.3.8Snare – Iron (351)9.3.9Snare – Clap (353)9.3.10Snare – Breaker (355)9.4The Hi-hats (357)9.4.1Hi-hat – Silver (358)9.4.2Hi-hat – Circuit (360)9.4.3Hi-hat – Memory (362)9.4.4Hi-hat – Hybrid (364)9.4.5Creating a Pattern with Closed and Open Hi-hats (366)9.5The Toms (367)9.5.1Tom – Tronic (369)9.5.2Tom – Fractal (371)9.5.3Tom – Floor (375)9.5.4Tom – High (377)9.6The Percussions (378)9.6.1Percussion – Fractal (380)9.6.2Percussion – Kettle (383)9.6.3Percussion – Shaker (385)9.7The Cymbals (389)9.7.1Cymbal – Crash (391)9.7.2Cymbal – Ride (393)10Using the Bass Synth (396)10.1Bass Synth – General Handling (397)10.1.1Parameter Organization (397)10.1.2Bass Synth Parameters (399)11Working with Patterns (401)11.1Pattern Basics (401)11.1.1Pattern Editor Overview (402)11.1.2Navigating the Event Area (404)11.1.3Following the Playback Position in the Pattern (406)11.1.4Jumping to Another Playback Position in the Pattern (407)11.1.5Group View and Keyboard View (408)11.1.6Adjusting the Arrange Grid and the Pattern Length (410)11.1.7Adjusting the Step Grid and the Nudge Grid (413)11.2Recording Patterns in Real Time (416)11.2.1Recording Your Patterns Live (417)11.2.2Using the Metronome (419)11.2.3Recording with Count-in (420)11.3Recording Patterns with the Step Sequencer (422)11.3.1Step Mode Basics (422)11.3.2Editing Events in Step Mode (424)11.4Editing Events (425)11.4.1Editing Events with the Mouse: an Overview (425)11.4.2Creating Events/Notes (428)11.4.3Selecting Events/Notes (429)11.4.4Editing Selected Events/Notes (431)11.4.5Deleting Events/Notes (434)11.4.6Cut, Copy, and Paste Events/Notes (436)11.4.7Quantizing Events/Notes (439)11.4.8Quantization While Playing (441)11.4.9Doubling a Pattern (442)11.4.10Adding Variation to Patterns (442)11.5Recording and Editing Modulation (443)11.5.1Which Parameters Are Modulatable? (444)11.5.2Recording Modulation (446)11.5.3Creating and Editing Modulation in the Control Lane (447)11.6Creating MIDI Tracks from Scratch in MASCHINE (452)11.7Managing Patterns (454)11.7.1The Pattern Manager and Pattern Mode (455)11.7.2Selecting Patterns and Pattern Banks (456)11.7.3Creating Patterns (459)11.7.4Deleting Patterns (460)11.7.5Creating and Deleting Pattern Banks (461)11.7.6Naming Patterns (463)11.7.7Changing the Pattern’s Color (465)11.7.8Duplicating, Copying, and Pasting Patterns (466)11.7.9Moving Patterns (469)11.8Importing/Exporting Audio and MIDI to/from Patterns (470)11.8.1Exporting Audio from Patterns (470)11.8.2Exporting MIDI from Patterns (472)11.8.3Importing MIDI to Patterns (474)12Audio Routing, Remote Control, and Macro Controls (483)12.1Audio Routing in MASCHINE (484)12.1.1Sending External Audio to Sounds (485)12.1.2Configuring the Main Output of Sounds and Groups (489)12.1.3Setting Up Auxiliary Outputs for Sounds and Groups (494)12.1.4Configuring the Master and Cue Outputs of MASCHINE (497)12.1.5Mono Audio Inputs (502)12.1.5.1Configuring External Inputs for Sounds in Mix View (503)12.2Using MIDI Control and Host Automation (506)12.2.1Triggering Sounds via MIDI Notes (507)12.2.2Triggering Scenes via MIDI (513)12.2.3Controlling Parameters via MIDI and Host Automation (514)12.2.4Selecting VST/AU Plug-in Presets via MIDI Program Change (522)12.2.5Sending MIDI from Sounds (523)12.3Creating Custom Sets of Parameters with the Macro Controls (527)12.3.1Macro Control Overview (527)12.3.2Assigning Macro Controls Using the Software (528)13Controlling Your Mix (535)13.1Mix View Basics (535)13.1.1Switching between Arrange View and Mix View (535)13.1.2Mix View Elements (536)13.2The Mixer (537)13.2.1Displaying Groups vs. Displaying Sounds (539)13.2.2Adjusting the Mixer Layout (541)13.2.3Selecting Channel Strips (542)13.2.4Managing Your Channels in the Mixer (543)13.2.5Adjusting Settings in the Channel Strips (545)13.2.6Using the Cue Bus (549)13.3The Plug-in Chain (551)13.4The Plug-in Strip (552)13.4.1The Plug-in Header (554)13.4.2Panels for Drumsynths and Internal Effects (556)13.4.3Panel for the Sampler (557)13.4.4Custom Panels for Native Instruments Plug-ins (560)13.4.5Undocking a Plug-in Panel (Native Instruments and External Plug-ins Only) (564)14Using Effects (567)14.1Applying Effects to a Sound, a Group or the Master (567)14.1.1Adding an Effect (567)14.1.2Other Operations on Effects (574)14.1.3Using the Side-Chain Input (575)14.2Applying Effects to External Audio (578)14.2.1Step 1: Configure MASCHINE Audio Inputs (578)14.2.2Step 2: Set up a Sound to Receive the External Input (579)14.2.3Step 3: Load an Effect to Process an Input (579)14.3Creating a Send Effect (580)14.3.1Step 1: Set Up a Sound or Group as Send Effect (581)14.3.2Step 2: Route Audio to the Send Effect (583)14.3.3 A Few Notes on Send Effects (583)14.4Creating Multi-Effects (584)15Effect Reference (587)15.1Dynamics (588)15.1.1Compressor (588)15.1.2Gate (591)15.1.3Transient Master (594)15.1.4Limiter (596)15.1.5Maximizer (600)15.2Filtering Effects (603)15.2.1EQ (603)15.2.2Filter (605)15.2.3Cabinet (609)15.3Modulation Effects (611)15.3.1Chorus (611)15.3.2Flanger (612)15.3.3FM (613)15.3.4Freq Shifter (615)15.3.5Phaser (616)15.4Spatial and Reverb Effects (617)15.4.1Ice (617)15.4.2Metaverb (619)15.4.3Reflex (620)15.4.4Reverb (Legacy) (621)15.4.5Reverb (623)15.4.5.1Reverb Room (623)15.4.5.2Reverb Hall (626)15.4.5.3Plate Reverb (629)15.5Delays (630)15.5.1Beat Delay (630)15.5.2Grain Delay (632)15.5.3Grain Stretch (634)15.5.4Resochord (636)15.6Distortion Effects (638)15.6.1Distortion (638)15.6.2Lofi (640)15.6.3Saturator (641)15.7Perform FX (645)15.7.1Filter (646)15.7.2Flanger (648)15.7.3Burst Echo (650)15.7.4Reso Echo (653)15.7.5Ring (656)15.7.6Stutter (658)15.7.7Tremolo (661)15.7.8Scratcher (664)16Working with the Arranger (667)16.1Arranger Basics (667)16.1.1Navigating Song View (670)16.1.2Following the Playback Position in Your Project (672)16.1.3Performing with Scenes and Sections using the Pads (673)16.2Using Ideas View (677)16.2.1Scene Overview (677)16.2.2Creating Scenes (679)16.2.3Assigning and Removing Patterns (679)16.2.4Selecting Scenes (682)16.2.5Deleting Scenes (684)16.2.6Creating and Deleting Scene Banks (685)16.2.7Clearing Scenes (685)16.2.8Duplicating Scenes (685)16.2.9Reordering Scenes (687)16.2.10Making Scenes Unique (688)16.2.11Appending Scenes to Arrangement (689)16.2.12Naming Scenes (689)16.2.13Changing the Color of a Scene (690)16.3Using Song View (692)16.3.1Section Management Overview (692)16.3.2Creating Sections (694)16.3.3Assigning a Scene to a Section (695)16.3.4Selecting Sections and Section Banks (696)16.3.5Reorganizing Sections (700)16.3.6Adjusting the Length of a Section (702)16.3.6.1Adjusting the Length of a Section Using the Software (703)16.3.6.2Adjusting the Length of a Section Using the Controller (705)16.3.7Clearing a Pattern in Song View (705)16.3.8Duplicating Sections (705)16.3.8.1Making Sections Unique (707)16.3.9Removing Sections (707)16.3.10Renaming Scenes (708)16.3.11Clearing Sections (710)16.3.12Creating and Deleting Section Banks (710)16.3.13Working with Patterns in Song view (710)16.3.13.1Creating a Pattern in Song View (711)16.3.13.2Selecting a Pattern in Song View (711)16.3.13.3Clearing a Pattern in Song View (711)16.3.13.4Renaming a Pattern in Song View (711)16.3.13.5Coloring a Pattern in Song View (712)16.3.13.6Removing a Pattern in Song View (712)16.3.13.7Duplicating a Pattern in Song View (712)16.3.14Enabling Auto Length (713)16.3.15Looping (714)16.3.15.1Setting the Loop Range in the Software (714)16.3.15.2Activating or Deactivating a Loop Using the Controller (715)16.4Playing with Sections (715)16.4.1Jumping to another Playback Position in Your Project (716)16.5Triggering Sections or Scenes via MIDI (717)16.6The Arrange Grid (719)16.7Quick Grid (720)17Sampling and Sample Mapping (722)17.1Opening the Sample Editor (722)17.2Recording Audio (724)17.2.1Opening the Record Page (724)17.2.2Selecting the Source and the Recording Mode (725)17.2.3Arming, Starting, and Stopping the Recording (729)17.2.5Checking Your Recordings (731)17.2.6Location and Name of Your Recorded Samples (734)17.3Editing a Sample (735)17.3.1Using the Edit Page (735)17.3.2Audio Editing Functions (739)17.4Slicing a Sample (743)17.4.1Opening the Slice Page (743)17.4.2Adjusting the Slicing Settings (744)17.4.3Manually Adjusting Your Slices (746)17.4.4Applying the Slicing (750)17.5Mapping Samples to Zones (754)17.5.1Opening the Zone Page (754)17.5.2Zone Page Overview (755)17.5.3Selecting and Managing Zones in the Zone List (756)17.5.4Selecting and Editing Zones in the Map View (761)17.5.5Editing Zones in the Sample View (765)17.5.6Adjusting the Zone Settings (767)17.5.7Adding Samples to the Sample Map (770)18Appendix: Tips for Playing Live (772)18.1Preparations (772)18.1.1Focus on the Hardware (772)18.1.2Customize the Pads of the Hardware (772)18.1.3Check Your CPU Power Before Playing (772)18.1.4Name and Color Your Groups, Patterns, Sounds and Scenes (773)18.1.5Consider Using a Limiter on Your Master (773)18.1.6Hook Up Your Other Gear and Sync It with MIDI Clock (773)18.1.7Improvise (773)18.2Basic Techniques (773)18.2.1Use Mute and Solo (773)18.2.2Create Variations of Your Drum Patterns in the Step Sequencer (774)18.2.3Use Note Repeat (774)18.2.4Set Up Your Own Multi-effect Groups and Automate Them (774)18.3Special Tricks (774)18.3.1Changing Pattern Length for Variation (774)18.3.2Using Loops to Cycle Through Samples (775)18.3.3Load Long Audio Files and Play with the Start Point (775)19Troubleshooting (776)19.1Knowledge Base (776)19.2Technical Support (776)19.3Registration Support (777)19.4User Forum (777)20Glossary (778)Index (786)1Welcome to MASCHINEThank you for buying MASCHINE!MASCHINE is a groove production studio that implements the familiar working style of classi-cal groove boxes along with the advantages of a computer based system. MASCHINE is ideal for making music live, as well as in the studio. It’s the hands-on aspect of a dedicated instru-ment, the MASCHINE hardware controller, united with the advanced editing features of the MASCHINE software.Creating beats is often not very intuitive with a computer, but using the MASCHINE hardware controller to do it makes it easy and fun. You can tap in freely with the pads or use Note Re-peat to jam along. Alternatively, build your beats using the step sequencer just as in classic drum machines.Patterns can be intuitively combined and rearranged on the fly to form larger ideas. You can try out several different versions of a song without ever having to stop the music.Since you can integrate it into any sequencer that supports VST, AU, or AAX plug-ins, you can reap the benefits in almost any software setup, or use it as a stand-alone application. You can sample your own material, slice loops and rearrange them easily.However, MASCHINE is a lot more than an ordinary groovebox or sampler: it comes with an inspiring 7-gigabyte library, and a sophisticated, yet easy to use tag-based Browser to give you instant access to the sounds you are looking for.What’s more, MASCHINE provides lots of options for manipulating your sounds via internal ef-fects and other sound-shaping possibilities. You can also control external MIDI hardware and 3rd-party software with the MASCHINE hardware controller, while customizing the functions of the pads, knobs and buttons according to your needs utilizing the included Controller Editor application. We hope you enjoy this fantastic instrument as much as we do. Now let’s get go-ing!—The MASCHINE team at Native Instruments.MASCHINE Documentation1.1MASCHINE DocumentationNative Instruments provide many information sources regarding MASCHINE. The main docu-ments should be read in the following sequence:1.MASCHINE MIKRO Quick Start Guide: This animated online guide provides a practical ap-proach to help you learn the basic of MASCHINE MIKRO. The guide is available from theNative Instruments website: https:///maschine-mikro-quick-start/2.MASCHINE Manual (this document): The MASCHINE Manual provides you with a compre-hensive description of all MASCHINE software and hardware features.Additional documentation sources provide you with details on more specific topics:►Online Support Videos: You can find a number of support videos on The Official Native In-struments Support Channel under the following URL: https:///NIsupport-EN. We recommend that you follow along with these instructions while the respective ap-plication is running on your computer.Other Online Resources:If you are experiencing problems related to your Native Instruments product that the supplied documentation does not cover, there are several ways of getting help:▪Knowledge Base▪User Forum▪Technical Support▪Registration SupportYou will find more information on these subjects in the chapter Troubleshooting.Document Conventions1.2Document ConventionsThis section introduces you to the signage and text highlighting used in this manual. This man-ual uses particular formatting to point out special facts and to warn you of potential issues.The icons introducing these notes let you see what kind of information is to be expected:This document uses particular formatting to point out special facts and to warn you of poten-tial issues. The icons introducing the following notes let you see what kind of information canbe expected:Furthermore, the following formatting is used:▪Text appearing in (drop-down) menus (such as Open…, Save as… etc.) in the software andpaths to locations on your hard disk or other storage devices is printed in italics.▪Text appearing elsewhere (labels of buttons, controls, text next to checkboxes etc.) in thesoftware is printed in blue. Whenever you see this formatting applied, you will find thesame text appearing somewhere on the screen.▪Text appearing on the displays of the controller is printed in light grey. Whenever you seethis formatting applied, you will find the same text on a controller display.▪Text appearing on labels of the hardware controller is printed in orange. Whenever you seethis formatting applied, you will find the same text on the controller.▪Important names and concepts are printed in bold.▪References to keys on your computer’s keyboard you’ll find put in square brackets (e.g.,“Press [Shift] + [Enter]”).►Single instructions are introduced by this play button type arrow.→Results of actions are introduced by this smaller arrow.Naming ConventionThroughout the documentation we will refer to MASCHINE controller (or just controller) as the hardware controller and MASCHINE software as the software installed on your computer.The term “effect” will sometimes be abbreviated as “FX” when referring to elements in the MA-SCHINE software and hardware. These terms have the same meaning.Button Combinations and Shortcuts on Your ControllerMost instructions will use the “+” sign to indicate buttons (or buttons and pads) that must be pressed simultaneously, starting with the button indicated first. E.g., an instruction such as:“Press SHIFT + PLAY”means:1.Press and hold SHIFT.2.While holding SHIFT, press PLAY and release it.3.Release SHIFT.1.3New Features in MASCHINE2.8The following new features have been added to MASCHINE: Integration▪Browse on , create your own collections of loops and one-shots and send them directly to the MASCHINE browser.Improvements to the Browser▪Samples are now cataloged in separate Loops and One-shots tabs in the Browser.▪Previews of loops selected in the Browser will be played in sync with the current project.When a loop is selected with Prehear turned on, it will begin playing immediately in-sync with the project if transport is running. If a loop preview starts part-way through the loop, the loop will play once more for its full length to ensure you get to hear the entire loop once in context with your project.▪Filters and product selections will be remembered when switching between content types and Factory/User Libraries in the Browser.▪Browser content synchronization between multiple running instances. When running multi-ple instances of MASCHINE, either as Standalone and/or as a plug-in, updates to the Li-brary will be synced across the instances. For example, if you delete a sample from your User Library in one instance, the sample will no longer be present in the other instances.Similarly, if you save a preset in one instance, that preset will then be available in the oth-er instances, too.▪Edits made to samples in the Factory Libraries will be saved to the Standard User Directo-ry.For more information on these new features, refer to the following chapter ↑4, Browser. Improvements to the MASCHINE MIKRO MK3 Controller▪You can now set sample Start and End points using the controller. For more information refer to ↑17.3.1, Using the Edit Page.Improved Support for A-Series Keyboards▪When Browsing with A-Series keyboards, you can now jump quickly to the results list by holding SHIFT and pushing right on the 4D Encoder.▪When Browsing with A-Series keyboards, you can fast scroll through the Browser results list by holding SHIFT and twisting the 4D Encoder.▪Mute and Solo Sounds and Groups from A-Series keyboards. Sounds are muted in TRACK mode while Groups are muted in IDEAS.。

3GPP 5G基站(BS)R16版本一致性测试英文原版(3GPP TS 38.141-1)

3GPP 5G基站(BS)R16版本一致性测试英文原版(3GPP TS 38.141-1)

4.2.2
BS type 1-H.................................................................................................................................................. 26
4.3
Base station classes............................................................................................................................................27
1 Scope.......................................................................................................................................................13
All rights reserved. UMTS™ is a Trade Mark of ETSI registered for the benefit of its members 3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM Association

IBM Cognos TM1 GDPR准备指南说明书

IBM Cognos TM1 GDPR准备指南说明书

IBMIBM Cognos TM1 considerations for GDPR readinessFor PID(s): 5724-W49 (No longer being sold)Notice:This document is intended to help you in your preparations for GDPR readiness. It provides information about features of IBM Cognos TM1 that you can configure, and aspects of the product's use, that you shouldconsider to help your organization with GDPR readiness. This information is not an exhaustive list, due to the many ways that clients can choose and configure features, and the large variety of ways that the product can be used in itself and with third-party applications and systems.IBM Cognos TM1 Clients are responsible for ensuring their own compliance with various laws andregulations, including the European Union General Data Protection Regulation. Clients are solelyresponsible for obtaining advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulations that may affect the clients' business and any actions the clients may need to take to comply with such laws and regulations.The products, services, and other capabilities described herein are not suitable for all client situations and may have restricted availability. IBM does not provide legal, accounting, or auditing advice orrepresent or warrant that its services or products will ensure that clients are in compliance with any law or regulation.Table of Contents1. GDPR2. Product Configuration for GDPR3. Data Life Cycle4. Data Collection5. Data Storage6. Data Access7. Data Processing8. Data Deletion9. Data Monitoring10. Responding to Data Subject RightsGDPRGeneral Data Protection Regulation (GDPR) has been adopted by the European Union ("EU") and applies from May 25, 2018.Why is GDPR important?GDPR establishes a stronger data protection regulatory framework for processing of personal data ofindividuals. GDPR brings:New and enhanced rights for individualsWidened definition of personal data1New obligations for processorsPotential for significant financial penalties for non-complianceCompulsory data breach notificationRead more about GDPREU GDPR Information Portal GDPR websiteProduct Configuration - considerations for GDPR ReadinessThe following sections provide considerations for configuring IBM Cognos TM1 to help your organization with GDPR readiness.Configuration to support data handling requirementsThere are no specific GDPR product configuration requirements. IBM Cognos TM1 does not collect privatedata without Administrator or Modeler input.Configuration to support Data PrivacyThe IBM TM1 Server is by default SSL enabled for all communication in and out of the server. SSL is enabled using a 2048bit AES 256 algorithm. IBM TM1 Server provides pre-configured signed certificated with theabove level of encryption. All clients, provided or custom built, require use of the secured certificate toauthenticate and present IBM TM1 Server data. Custom certificates can also be deployed.Configuration to support Data SecurityIBM TM1 Server protects data access in multiple methods. Users can access the data with properauthorization and authentication to objects as defined by the security administrator. Data can be secured at a model, cube, dimension, element or cell level providing a very robust set of capabilities to secure content.Data is accessed via either Microsoft Windows based thick clients, such as IBM TM1 Perpectives, or through web based clients. IBM TM1 Server data is available via API's. Two sets of API's are provided. A proprietary c-API and a web RESTFul API.Data Life CycleIBM Cognos TM1 stores data in may different locations as it is populated into the system. Primarily datastored is specific to effort an administrator or modeler has committed. Locations to be aware of are listedbelow:TM1 Server}Clients dim - May contain the UID as defined in the LDAP or an alias based on the CAMID taken from Cognos Analytics.}ElementAttributes_}clients - This control cube may contain a caption value as entered by an modeler, todelete this value either remove the caption as entered or delete the element name in the }clients dimension. 2}PerfClients - This control dim may contain the names from the }clients dim entries which could be user name specific. This may be considered personal data. To delete this simple delete the element name from thedimension itself.Transaction log - tm1s.log logs cube value changesAudit Log - Changes to data and metadataTM1 ArchitectTM1 Architect will not programmatically capture personal data on an end user either through logging or not.All content created and committed via TM1 Architect is captured and stored at the TM1 Server level.TM1 PerspectivesTM1 Perspectives will not programmatically capture personal data on an end user either through logging or not. All content created and committed via TM1 Perspectives is captured and stored at the TM1 Server level. A model developer may populate any metadata within the Excel sheet referencing personal data. An example isa hidden sheet that drives a value elsewhere in the form. This metadata is a Microsoft Excel cell which maycontain any detail entered by the sheet editor.TM1 Application WebTM1 Applications will not programmatically contain personal data specific to a user. If a user has beengranted access to a node in a Application Web application, deleting the user from the node access level will remove any reference points.TM1 Applications allow document attachment, and node level commentary. Both of these items may contain personal information as they allow free form text entry.TM1 Performance ModelerTM1 Performance Modeler will not programmatically capture personal data on an end user either throughlogging or not. All content created and committed via TM1 Performance Modeler is captured and stored at the TM1 Server level.Data CollectionTM1 Server Cube data can keep any text based data, and it may retain user detail. An example would be aHeadcount forecast model with a dimension that has an element of Name. This is not something capturedautomatically, but like any database it may contain personal information as entered in a field by anadministrator. Detail can also be written to alias values, or they can be dimension element names. Anything that can be named or typed into a cell can have personal information about an individual. Another example a Salary Planning cube, this may have user name, userId, employee #, salary, location, band, etc So in thisexample any dimension, or any cube may contain this information. Information created by anadministrator/modeler for a TM1 Server model is stored in the data directory in a set of proprietary files. For more information, see Data directory overview.Data StorageIBM Cognos TM1 data is stored within a set of proprietary files. These files are located within either the data or data and logs directory as defined by the administrator. Both the data and logs directory are defined in the3tm1s.cfg file. Access to these locations should be secured by using the Operating Systems file system access security mechanisms using properly defined access controls.Data AccessIBM TM1 Server protects data access in multiple methods.Users can access the data with proper authorization and authentication to objects as defined by the security administrator. Data can be secured at a model, cube, dimension, element or cell level providing a very robust set of capabilities to secure content. Data is accessed via either Microsoft Windows based thick clients, such as IBM TM1 Perpectives, or through web based clients. IBM TM1 Server data is available via API's. Two sets of API's are provided. A proprietary c-API and a web RESTFul API.Data ProcessingThe IBM TM1 Server is by default SSL enabled for all communication in and out of the server. SSL is enabled using a 2048bit AES 256 algorithm. IBM TM1 Server provides pre-configured signed certificated with theabove level of encryption. All clients, provided or custom built, require use of the secured certificate toauthenticate and present IBM TM1 Server data. Custom certificates can also be deployed.Data DeletionIBM TM1 ServerFrom the Current Application (.dim / .cub / etc)Personal Data can be removed by manually removing by an authorized user from the element or cubeintersections that contain the Personal Data. Using the example above for a Salary Forecast cube the rowwithin the cube, including potentially the element name would have to be manually deleted. Manually deleted can mean an admin developing a TI script that reads metadata or data looking for specific name references and deleting or overwriting them.}ElementAttributes_}clients - This control cube may contain a caption value as entered by a modeler, to delete this value either remove the caption as entered or delete the element name in the }clients dimension.}PerfClients - This control dim may contain the names from the }clients dim entries which could be user name specific. This may be considered personal data. To delete this, delete the element name from the dimension.From archivesPersonal Data can be removed from archived by restoring the archive and much like Current Applicationsmanually removing the element or cube intersections that contain the Personal Data. Using the exampleabove for a Salary Forecast cube the row within the cube, including potentially the element name would have to be manually deleted. Manually deleted can mean an admin developing a TI script that reads metadata and data looking for specific name references and deleting or overwriting them.From LogsPersonal Information from logs can be removed by either destroying the log files, or due to log files being text based in nature, opening the files and searching/deleting the entries containing personal information.IBM TM1 Application Web4As Application Web content can contain both attached documents and text driven commentary anAdministrator of the application will be required to open the individual applications to determine if theattached or custom commentary text contains personal information. This is a manual effort that will need to be executed for each application.Data MonitoringIBM TM1 provides mechanisms to monitor user activity within the Server with tools such as TM1 Top or IBM TM1 Operations Console. This does not provide monitoring of the dataflow. All data monitoring capabilities are via the audit or transaction logs listed above, and can be controlled with the guidance provide there. Responding to Data Subject RightsSince IBM Cognos TM1 stores data at rest both in log files and in the model structure of Cognos TM1Databases. The administrator must be aware of and remove any personal data based on Data Subjectrequests.5。

赛米控丹佛斯 SEMITRANS 3 IGBT模块 SKM600GB12E4D1 数据表

赛米控丹佛斯 SEMITRANS 3 IGBT模块 SKM600GB12E4D1 数据表

Absolute Maximum Ratings Symbol Conditions Values UnitIGBTV CES T j = 25 °C 1200 V I C T j = 175 °CT c = 25 °C 860 A T c = 80 °C702 A I Cnom 600 A I CRM1800 A V GES -20 (20)V t psc V CC = 800 V V GE ≤ 15 V V CES ≤ 1200 VT j = 150 °C10 μs T j-40 (175)°C Inverse diodeV RRM T j = 25 °C1200V I F Continuous DC forward current 600A I FRM 1200A I FSM 10 ms, sin 180°, T j = 25 °C2736A T j-40 ... 175°C Module I t(RMS)500 A T stg module without TIM-40 ... 125 °C V isolAC sinus 50 Hz, t = 1 min4000VCharacteristics Symbol Conditions min. typ. max. UnitIGBTV CE(sat)I C = 600 A V GE = 15 V chiplevel T j = 25 °C 1.80 2.05 V T j = 150 °C 2.05 2.42 V V CE0chiplevel T j = 25 °C 0.80 0.90 V T j = 150 °C 0.75 0.80 V r CE V GE = 15 V chiplevelT j = 25 °C 1.67 1.92 mΩ T j = 150 °C2.2 2.7 mΩ V GE(th)V GE = V CE , I C = 24 mA55.86.5 V I CES V GE = 0 V, V CE = 1200 V, T j = 25 °C5mA C ies V CE = 25 V V GE = 0 Vf = 1 MHz37.2 nF C oes f = 1 MHz 2.32 nF C res f = 1 MHz2.04 nF Q G V GE = - 8V ... + 15 V 3400 nC R Gint T j = 25 °C 1.3 Ω t d(on)V CC = 600 V I C = 600 AV GE =+15/-15V R Gon = 1.8 Ω R Goff = 1.2 Ωdi/dt on = 8050 A/µs di/dt off = 4100 A/µs dv/dt = 3500 V/µs L s = 25 nH T j = 150 °C 175 ns t r T j = 150 °C 75 ns E on T j = 150 °C 55 mJ t d(off)T j = 150 °C 530 ns t f T j = 150 °C 120 ns E off T j = 150 °C80mJ R th(j-c)per IGBT0.049K/W R th(c-s)per IGBT, (λgrease = 0.81 W/(m*K))0.032K/WIGBT4 ModulesSKM600GB12E4D1Features*∙IGBT4 = 4th generation medium fast trench IGBT (Infineon)∙ CAL4HD = 4th generation high density (HD) CAL-diode optimized for low static losses∙ Insulated copper baseplate using DBC technology (Direct Bonded Copper)∙ Increased power cycling capability ∙ With integrated gate resistor∙ For higher switching frequencies up to 8kHz∙ UL recognized, file no. E63532Typical Applications∙ AC inverter drives ∙ UPS∙ Electronic welders ∙ Wind power ∙ Public transportRemarks∙ Case temperature limited to T c = 125°C max, recomm.T op = -40... +150°C, product rel. results valid for T j = 150°C ∙ Max. operating DC link voltage limited to 800VGBSEMITRANS 3Characteristics Symbol Conditions min. typ. max. UnitInverse diodeV F = V EC I F = 600 A V GE = 0 V chiplevel T j = 25 °C 1.80 2.13 V T j = 150 °C 1.83 2.17 V V F0chiplevel T j = 25 °C 1.19 1.40 V T j = 150 °C 0.97 1.10 V r F chiplevelT j = 25 °C 1.02 1.21 mΩ T j = 150 °C1.44 1.79mΩ I RRM V CC = 600 V I F = 600 AV GE = -15 Vdi/dt off = 9200 A/µs T j = 150 °C 680 A Q rr T j = 150 °C130 µC E rr T j = 150 °C 60mJ R th(j-c)per diode0.095K/W R th(c-s)per diode, (λgrease = 0.81 W/(m*K))0.039 K/W ModuleL CE 15nH R CC’+EE’measured per switchT j = 25 °C0.55mΩ T j = 150 °C0.85 mΩ R th(c-s)1calculated without thermal coupling (λgrease =0.81 W/(m*K)) 0.0088 K/W R th(c-s)2including thermal coupling,Ts underneath module (λgrease =0.81 W/(m*K)) 0.014K/W M s to heat sink M63 5 Nm M t to terminal M62.55 Nm -Nm w325 gSEMITRANS ® 3 IGBT4 ModulesSKM600GB12E4D1Features*∙IGBT4 = 4th generation medium fast trench IGBT (Infineon) Exciter module∙ CAL4HD = 4th generation (HD) CAL-diode optimized for low static losses∙ Insulated copper baseplate using DBC technology (Direct Bonded Copper)∙ Increased power cycling capability ∙ With integrated gate resistor∙ For higher switching frequencies up to 8kHz∙ UL recognized, file no. E63532Typical Applications∙ AC inverter drives ∙ UPS∙ Electronic welders ∙ Wind power ∙ Public transportRemarks∙ Case temperature limited to T c = 125°C max, recomm.T op = -40... +150°C, product rel. results valid for T j = 150°C ∙ Max. operating DC link voltage limited to 800VGBFig. 1: Typ. output characteristic, inclusive R CC'+ EE'Fig. 2: Rated current vs. temperature I C = f (T C )Fig. 3: Typ. turn-on /-off energy = f (I C ) Fig. 4: Typ. turn-on /-off energy = f (R G )Fig. 5: Typ. transfer characteristic Fig. 6: Typ. gate charge characteristicFig. 7: Typ. switching times vs. I C Fig. 8: Typ. switching times vs. gate resistor R GFig. 9: Transient thermal impedance Fig. 10: Typ. CAL diode forward charact., incl. R CC'+ EE'Fig. 11: Typ. CAL diode peak reverse recovery current Fig. 12: Typ. CAL diode peak reverse recovery chargePinout and DimensionsGBThis is an electrostatic discharge sensitive device (ESDS), international standard IEC 60747-1, chapter IX.*IMPORTANT INFORMATION AND WARNINGSThe specifications of SEMIKRON products may not be considered as guarantee or assurance of product characteristics ("Beschaffenheitsgarantie"). The specifications of SEMIKRON products describe only the usual characteristics of products to be expected in typical applications, which may still vary depending on the specific application. Therefore, products must be tested for the respective application in advance. Application adjustments may be necessary. The user of SEMIKRON products is responsible for the safety of their applications embedding SEMIKRON products and must take adequate safety measures to prevent the applications from causing a physical injury, fire or other problem if any of SEMIKRON products become faulty. The user is responsible to make sure that the application design is compliant with all applicable laws, regulations, norms and standards. Except as otherwise explicitly approved by SEMIKRON in a written document signed by authorized representatives of SEMIKRON, SEMIKRON products may not be used in any applications where a failure of the product or any consequences of the use thereof can reasonably be expected to result in personal injury. No representation or warranty is given and no liability is assumed with respect to the accuracy, completeness and/or use of any information herein, including without limitation, warranties of non-infringement of intellectual property rights of any third party. SEMIKRON does not assume any liability arising out of the applications or use of any product; neither does it convey any license under its patent rights, copyrights, trade secrets or other intellectual property rights, nor the rights of others. SEMIKRON makes no representation or warranty of non-infringement or alleged non-infringement of intellectual property rights of any third party which may arise from applications. Due to technical requirements our products may contain dangerous substances. For information on the types in question please contact the nearest SEMIKRON sales office. This document supersedes and replaces all information previously supplied and may be superseded by updates. SEMIKRON reserves the right to make changes.。

FORD福特汽车研发流程介绍

FORD福特汽车研发流程介绍

Ver
ific
ati
11
ons
Phased PPAP与PPAP的比较
交运制造
PPAP
Phased PPAP
Phase 0
Phase 1
START NPRTSmJpai[scfcrp[c([(pfQPPprP&IRoci[ospPPTVwdnphlR#oulo#dne#fNreu#uoosyiaouuarrrrrrieptorlornsaauaxf@ nboin8cqe1acooapoo5bernonorPswGlpdeltestmrl]eslaltlf-ea,in,alu,rdddt:updd-tsuecce1Ut2rni1spe6esarRaa)ounargmarlssnesiefemuuuadoruu,dR6A,ufeoerlutITCsousT)3ctrAmtsisLn0ci&iesms-FetcccccriaNtieduieienqlscltSegtiiaoeoporun&sRtmstatordttdtttrelii&qtertnypudegpiiiiooesiierrptgccYta7ie3DNNNNnrooooosrOtuoedsir@ thil-aatilrne1opmtolv]rtrhap0teiCghl&nnnC4nnPoopciaaxsfW WW iooooepnnDaesEitmihsRu7esefr?rfno0ceYYYbatnmyeR]oirimopereetVemoie]lrtateaeee,roolcpeet&ayuey?dnae(npsdilYercEEthentc-ssslvosrrdsnreiscttsedeertovuNLloeence)oeeaSwerCrnW uSPADtseutaetnpIoditCtldtSChTtmhtttbnsTodchlnieuanicpfirlhh?nsoauu:meAuoeeipemaedotttnfaterPpeeprbcudrisTaniads1fmu4?dlcRernknoltiaptyuemsUb?bsanhtioustupmcsnioltapnlhnSTee0cmiineNlunststral:detgeayaemeuepnatedccodrrtmatnebek41reiqebtPQndsruCAp---------IFpPtehgumiiorahrmopaDMSPASMCaraoerrapstsineapuplinteadaameimsmrsotsrtsdpttesfiuuoyPtrni1oeeeeeftpsoctpvrPe1urnVrfnatatolmaiipAmrieieetrannsc&lomsalPisrleaetiapoPPnnieaPcsRHTrlPfadnn2ar4nrPrmaoicNehepocPsocSsacrotaethbsraottAathrocepdvipYrtlritwusasosytceoceSeeePseulmfDCeisErTPW SPcecr[is[tco:inascPncSCet#e[#idtaeuoThshsatthe0#minhtPuasidut1Afe1silrtamait0va([ti1euAtorabso8rfsc?o4T#Pssieasrm0ocios4btpPnem]eU]aanPu1ptRoo2][rnalTnA#5elraSe1tP1emim[ysrethtn]#cP1:ttaaqemehkoeetpt21)rcuosdaatrn]k3luesie42gtrbie]nasneteieimtmngosPPe[gne#hrne[o#1anod9sRa(1tHaRfvne0Pesu]s]ateus-a)N[h-ect#2tIPcOo1mioohu7Ynnap]tecsposVeuureSrtCtSPD2PWr[arts#eoThaihSCnafaAana1mtaiuatutncurrTat8ssbsraendlpsebUe]yatmtoloasinTSeP223oitamrsiftt:hetanetea:aicetdsloskrlfeiiIe3nn3dgpmfdccAfBSfrcduPCPPWtoSoreuharecrlQtoPhohhaaurlarqesasnhfahapwtaambiiuptoaunrareennafossscPaaaRehrCDkansenoAliRagArdPeeseeneoalrscmflqtaoTsinrnVearueeeefrhuaddecrdinsrtpui3e23oettNeNnddteirteRtpelhaaloYtyfimvocPuceepeei0i&(attptuVrrlsesropiotopnTWoCCoDtylscE-crdDfvxhirieemVhteCalYeesesnDnlmtxnrtPn.lcpValenoaoiaanmi)eseeProauradiaepdesM1etdrPvprtstcEi,rnristrRVs,umdufr?orsuneerleeSicoVaNatpiC&dtoDAfSPWee,s?u[scdntdtetePhyicpe#heuTo2hclachTpaancptuihearACt1aatctcp:tesmaeooao&itcayrhuiatts8tTvEasdloalrfrtiidisayeepsbee]nUNopaotib?neaonsulanannTSrleDc3ipnecsse3Rrtcf:ctealeoqieuaeptcdlduycpnalkoeitmriranwt

IBM Cognos TM1版本10.2.2快速入门指南说明书

IBM Cognos TM1版本10.2.2快速入门指南说明书

IBM Cognos TM1Version 10.2.2Quick Start GuideThe Quick Start Guide gets you started with IBM Cognos TM1.Translated Versions:To obtain the Quick Start Guide in other languages,access the PDF and HTML from the Quick Start CD.Product OverviewIBM ®Cognos ®TM1®integrates business planning,performance measurement,scorecarding,and multiple sources of data.Cognos TM1provides immediate visibility into data,accountability within a collaborative process,and a consistent view of information.Cognos TM1helps managers quickly identify and stabilize operational fluctuations to take advantage of new opportunities.v Cognos TM1Webv Cognos TM1Operations Consolev Cognos TM1Architectv Cognos TM1Perspectivesv Cognos TM1APIsv Cognos TM1Applicationsv SamplesThe following components are optional and may be added during the initial installation or later:v Cognos TM1Performance Modeler (includes Cognos TM1Scorecarding)v Cognos Insight (web-based client).Cognos Insight can be installed as a stand-alone component or as part of your Cognos TM1installation.For more information,see the Cognos Insight website.v Translated documentation.To display the Help documentation in a language other than English,select the additional languages you want from the Translated Documentation list during installation.English documentation is installed by default.Vista,Windows7,or Windows Server2008operating system software,right-click the issetup.exe file and click Run as Administrator.For all other Windows operating system software,double-click issetup.exe.4.Select the components that you want to install:Installing on a single computerThe components that you need to install Cognos TM110.2.2on a single computer are selected by default.Accept the default selections.Installing across multiple computersTo distribute the Cognos TM1components across different computers,run the installation and select only thecomponents you need for this computer.Then move to the other computers and select the other componentsyou need during the installation.For detailed instructions on how to install different components on separatecomputers,see the IBM Cognos TM1Installation and Configuration Guide.v Start the IBM Cognos TM1Admin Server and the IBM Cognos TM1Applications server.v Start at least one Cognos TM1server,such as one of the default sample databases.v If you plan to use the Cognos TM1Operations Console,start the SData server.Cognos TM1on a computer with a Microsoft Windows operating system,edit the services so that the user account that runs the service has the administrative privileges that are needed by Cognos TM1.For more information,see the IBM Cognos TM1Installation and Configuration Guide.This requirement applies only to services on the Microsoft Windowsoperating system.Cognos TM1services that are installed on UNIX always run as ROOT.More informationFor more technical resources,see:v Cognos TM1product and feature information(/software/data/cognos/products/tm1)v Product support(/support/docview.wss?uid=swg27040698)Licensed Materials-Property of IBM©Copyright IBM Corp.2007,2014.US Government Users Restricted Rights–Use,duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.IBM,the IBM logo,®,TM1and 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 Copyright and trademark information(/legal/copytrade.shtml)Part Number:CF44CMLPrinted in Ireland。

femfat的basic模块

femfat的basic模块

femfat的basic模块
FEMFAT是一种用于疲劳分析的软件，它包含多个模块，其中之
一是Basic模块。

Basic模块是FEMFAT的核心模块之一，它提供了
基本的疲劳分析功能和工具，用于评估零件和结构在实际工作条件
下的疲劳性能。

Basic模块的主要功能包括：
1. 应力计算，Basic模块可以根据有限元分析的结果，计算零
件或结构在不同载荷条件下的应力分布。

这对于疲劳寿命的评估至
关重要，因为疲劳寿命通常与应力分布密切相关。

2. 疲劳寿命预测，基于应力历史和材料的疲劳性能曲线，
Basic模块可以预测零件或结构在实际工作条件下的疲劳寿命。

这
对于评估零件的可靠性和耐久性非常重要。

3. 材料数据库，Basic模块通常包含了广泛的材料数据库，用
户可以从中选择适合其应用的材料，以便进行疲劳分析和寿命预测。

4. 后处理和结果可视化，Basic模块还提供了丰富的后处理功
能，用户可以对疲劳分析的结果进行可视化和分析，以便更好地理
解零件或结构的疲劳性能。

总的来说，FEMFAT的Basic模块为工程师提供了一套完善的工具，帮助他们进行疲劳分析和寿命预测，从而确保产品的可靠性和
耐久性。

通过Basic模块，工程师可以更好地理解零件和结构在实
际工作条件下的疲劳行为，从而优化设计并提高产品的性能和寿命。

IBM Cognos Transformer V11.0 用户指南说明书

IBM Cognos Transformer V11.0 用户指南说明书
Dimensional Modeling Workflow................................................................................................................. 1 Analyzing Your Requirements and Source Data.................................................................................... 1 Preprocessing Your ...................................................................................................................... 2 Building a Prototype............................................................................................................................... 4 Refining Your Model............................................................................................................................... 5 Diagnose and Resolve Any Design Problems........................................................................................ 6

Sennheiser SR IEM G4 半机械式立体音频传输器说明书

Sennheiser SR IEM G4 半机械式立体音频传输器说明书

FEATURES• Half-rack stereo transmitter in a full-metal housing with OLED display for full control• Easy and flexible wireless synchronization between transmitter and receiver via infrared• Compatible with Sennheiser WSM control software for flexible frequency allocation• Up to 16 compatible channels• Up to 42 MHz bandwidth with 1680 selectable frequen-cies, fully tunable in a stable UHF range• Transmission Range: up to 100 meters / 300 feet• High RF output power (up to 50 mW) depending on country regulations DELIVERY INCLUDES• SR IEM G4 stereo transmitter • rod antenna• power supply• GA 3 rackmount set• quick guide• safety guide• manufacturer declaration sheetHalf-rack stereo transmitter in a full-metal housing with OLED display for full control delivering clarity along the whole frequency spectrum for daily use on stage with evolution wireless G4 In Ear Monitoring systems.PRODUCT VARIANTSMade in GermanySR IEM G4-A1470 - 516 MHz Art. no. 507842 SR IEM G4-A516 - 558 MHz Art. no. 507843 SR IEM G4-GB606 - 648 MHz Art. no. 507844 SR IEM G4-G566 - 608 MHz Art. no. 507845 SR IEM G4-B626 - 668 MHz Art. no. 507846 SR IEM G4-C734 - 776 MHz Art. no. 507847 SR IEM G4-E823 - 865 MHz Art. no. 507848Assembled in USASR IEM G4-A1470 - 516 MHz Art. no. 508181 SR IEM G4-A516 - 558 MHz Art. no. 508182 SR IEM G4-AS520 - 558 MHz Art. no. 508183 SR IEM G4-G566 - 608 MHz Art. no. 508184 SR IEM G4-B626 - 668 MHz Art. no. 508185 SR IEM G4-C734 - 776 MHz Art. no. 508186 SR IEM G4-D780 - 822 MHz Art. no. 508187SPECIFICATIONSRF characteristicsModulation Wideband FM stereo(MPX pilot tone) Frequency ranges A1: 470 - 516 MHzA: 516 - 558 MHzAS: 520 - 558 MHzG: 566 - 608 MHzGB: 606 - 648 MHzB: 626 - 668 MHzC: 734 - 776 MHzD: 780 - 822 MHzE: 823 - 865 MHz Transmitting frequencies Max. 1680 frequencies,adjustable in 25 kHz steps20 frequency banks, eachwith up to 16 factory-presetchannels, no intermodula-tion6 frequency banks withup to 16 programmablechannelsSwitching bandwidth up to 42 MHzNominal/peak deviation±24 kHz / ±48 kHzMPX pilot tone(frequency/deviation)19 kHz/±5 kHz Frequency stability±10 ppmAntenna output BNC socket, 50 ΩRF output power at 50 Ωswitchable:Low: typ. 10 mWStandard: typ. 30 mWHigh: typ. 50 mWAF characteristicsCompander system Sennheiser HDXAF frequency response25 Hz to 15 kHzAF inputBAL AF IN L (I) + MONO/BAL AF IN R (II)2x XLR-3/¼" (6.3 mm) jackcombo socket, electroni-cally balancedMax. input level+22 dBuTotal harmonic distortion(THD)<0.9 %Signal-to-noise ratio (atnominal load and peakdeviation)>90 dBAF outputLOOP OUT BAL L (I)/LOOP OUT BAL R (II)¼" (6.3 mm) stereo jacksocket,balancedOverall deviceTemperature range-10 °C to +55 °CPower supply12 V DCCurrent consumption max. 350 mA Dimensions Approx. 202 x 212 x 43 mm Weight Approx. 980 gCONNECTIONSDIMENSIONSARCHITECT‘S SPECIFICATIONThe wireless stereo rack-mount transmitter shall be for use with a companion receiver as part of a wireless RF monitoring system.The transmitter shall operate within nine UHF frequency ranges, with a switching bandwidth of up to 42 MHz: 470 –516 M Hz, 516 – 558 M Hz, 520 – 558 M Hz, 626 – 668 M Hz, 734 – 776 M Hz, 780 – 822 M Hz, 823 – 865 M Hz, 566 – 608 MHz, 606 – 648 M Hz; transmitting frequencies shall be 1,680 per range and hall be tunable in 25 kHz steps. The transmitter shall feature 20 fixed frequency banks with up to 16 compatible frequency presets and 6 user banks with up to 16 user programmable frequencies.The transmitter shall be menu-driven with a backlit OLED display showing the current frequency, frequency bank and channel number, metering of AF level, transmission status, transmission power, equalizer setting, input sensitivity, and lock status. An auto-lock feature shall be provided to prevent settings from being accidentally altered.The parameters of associated receivers shall be configurable in the transmitter menu and synchronized with the receivers via an integrated infrared interface.Frequency stability shall be ±10 ppm. RF output power at 50 Ω shall be switchable between 10 mW (low), 30 mW (stan-dard) and 50 mW (high).The stereo audio input shall utilize two discrete (left/right) electronically balanced ¼" (6.3 mm) jack/XLR-3F combo sockets; the audio output shall utilize a balanced ¼" (6.3 mm) jack socket; an audio loop output shall be provided utilizing two balanced ¼" (6.3 mm) jack sockets. A headphone output with headphone volume control shall be provided and shall utilize a ¼" (6.3 mm) stereo jack socket. The transmitter shall have an Ethernet port (RJ-45) for remote network-based monitoring and control using the Sennheiser Wireless System Manager software. One 50 Ω BNC-type input socket shall be provided for connecting the antenna.Nominal/peak deviation shall be ±24 kHz/±48 kHz. The transmitter shall incorporate the Sennheiser HDX compander system and shall include a 19-kHz MPX pilot tone with a ±5 kHz deviation. The audio frequency response shall range from 25 –15,000 Hz. Maximum input level shall be +22 dBu. Total harmonic distortion (THD) at 1 mV and nominal deviation shall be < 0.9 %. Signal-to-noise ratio at nominal load and peak deviation shall be > 90 dB.The transmitter shall operate on 12 V power supplied from the NT 2-3 mains unit (for 100 – 240 V AC, 50/60 Hz). Power consumption shall be 350 mA. The transmitter shall have a rugged metal housing; dimensions shall be approximately 202 x 212 x 43 mm (7.95" x 8.35" x 1.69"). Weight shall be approximately 980 grams (2.16 lbs). Operating temperature shall range from −10 °C to +55 °C (+14 °F to +131 °F).The transmitter shall be the Sennheiser SR IEM G4.Sennheiser electronic GmbH & Co. KG · Am Labor 1 · 30900 Wedemark · Germany · 。

MTTLER TOLEDO TLX Basic DWS系统快速指南说明书

MTTLER TOLEDO TLX Basic DWS系统快速指南说明书
The weigh cells of the scale belt are a very sensitive precision measuring instrument and must therefore be handled with care:
• Shocks, jamming, or objects falling on the scale belt conveyor must be avoided. • Never put tools on the weighing belt conveyor.
Laser Safety......................................................................................................................................3
The Dimensioner and the Barcode readers operate using laser beams.......................................................3
4.
Diagnostics and Maintenance ........................................................................... 9
Status and error codes .......................................................................................................................9

Mobile Trusted Module (MTM) - an introduction(NRC-TR-2007-015)

Mobile Trusted Module (MTM) - an introduction(NRC-TR-2007-015)

Mobile Trusted Module(MTM)-an introductionJan-Erik Ekberg,Markku Kyl a np a aNokia Research Center Helsinki,FinlandNovember14,2007Abstract:This paper provides a brief overview of the Mobile Trusted Module(MTM),its features and capabilities with respect to TPMs.The viewpoint is the device manufacturer's,i.e.the functionalities de ned by the Remote Owner MTM(MRTM)pro le of the speci cation.Additionally the paper presents a few use cases related to the technology,the implementation of a MRTM emulator and a proposal for an API to control MTM functionality.Index Terms:platform securitymobile phones1IntroductionThe Mobile Trusted Module(MTM)is a security element and a newly approved TCG speci cation[1], [2]for use in mobile and embedded devices.Its origin lies in the TPM v.1.2,but the mobile speci cation signi cantly di ers from the original speci cation on a few issues:1.The concept of secure boot is introduced.Many embedded devices and handsets in particular aresubject to regulatory approval.That in turn motivates the need for enforced integrity protection of software in elded devices,and secure boot,i.e.,a boot sequence not only measured,but also aborted on any non-approved state transition,is a vital building block for this security service.2.The speci cation explicitely supports implementation of the MTM as a functionality rather thanas a physical implementation in hardware.This makes it possible for device manufacturers to add the MTM as an add-on to already deployed,proprietary security solutions.3.In addition,the reference architecture takes into account the support of several parallel MTMinstances in the same device.Some will be discretionary(MTM exposed to user applications) whereas e.g.the Device Manufacturer MTM by de nition enforces security policy(mandatory access control).This paper introduces the new features of MTM in the context of a reference implementation.MTM de nes two interleaving pro les depending on the entity that holds ownership of the functionality-Mobile Remote Owner Trusted Module(MRTM)and the Mobile Local Owner Trusted Module(MLTM). We have focused on the former pro le(MRTM),since the Remote Owner speci cation nicely contains all the new functionality of the MTM with respect to TPMv1.2.Intended to be used either by the device manufacturer or a carrier operator,the MTRM de nes the security architecture and interfaces to implement an integrity-protected device.The paper starts by introducing the main system components and interfaces that make up the secure boot concept in MTM-in particular the Reference Integrity Metric(RIM)certi cates and their enforce-ment.Then we propose new additions to the TSS interface for managing system parameters and the secure boot concept in MTM.Our reference implementation is described in its own section.We conclude with a few general ideas on how to use RIM certi cates for a variety of security-related purposes and nally sum up the lessons learned in a conclusion section.2MTM setup and stateThe MTM standard is exible enough to accommodate several di erent architectures for guaranteeing the integrity of the MTM in the scope of secure boot,and the mechanisms used to provide root secrets and immutable data to it.In this section we give a description of one setup that is acceptable within the context of the MTM standard,while at the same time describing the essentials of some MRTM functions and parameters.Please refer to the standards text for an exhaustive coverage of the secure boot phase.2.1Initial boot stepsFor secure boot to be enforced,the system must have passed through two discrete states-the Engine Reset and Engine Root-of-Trust Initialization phases prior to activating the MTM.The reset state simply describes the fact that no software is running on the device prior to rst MTM setup.The initialization phase in which the software MTM is set up is in the standards context de ned by a set of\Roots of Trust",each of which describes a necessary security precondition to be satis ed in order for the MTM security to be complete.The Root of Trust for Enforcement(RTE)essentially states that platform-speci c mechanisms must be used to guarantee the integrity and authenticity of the MTM code and its execution environment.Some form of device secret will be needed to establish a Root of Trust for Storage (RTS),and some immutable or similarly protected code will constitute the Root of Trust for Veri cation (RTV),an engine that makes the initial measurements to be added to MTM prior to the MTM being fully functional.A Root of Trust for Reporting(RTR)holds the secrets to sign PCR measurements for attestation purposes.An RTS with suitable statefulness guarantees can be considered to contain also the RTR and RTV.Figure1:Our reference architectureFigure1shows the reference model that we are targeting in this paper.The device has its own, proprietary way of ensuring boot integrity.That concept is used to protect the initial boot sequence up to the place where the MTM is loaded into a secure environment,e.g.to some on-processor memory. We also assume the presence of at least one device secret(a.k.a.RTS),passed to the MTM when loaded,to be used as a seed for con dentiality services in the MTM(e.g.the seed for the SRK). Additionally,immutable information for verifying veri cation keys and further RIM certi cates,called the Root Veri cation Authority Information(RVAI)needs to be presented to the MTM.Furthermore the continued computational isolation of the MTM function with respect to e.g.the OS being loaded and run must be ascertained in order for the architecture to be secure.2.2MTM internal stateIn comparison to a TPM,MTM requires some additional persistent state information.Most of this is stored in a new data structure speci ed by the standard,called MTM PERMANENT DATA.Most parameters and attributes will be elaborated on in later sections,but a brief overview follows. The structure begins with a storage area for the attestation key AIK,used if it is pre-assigned to an MRTM during manufacuring.The boolean ag structure veri edPCRs indicates the set of PCRs constrained to b extended only by means of RIM certi cate.The value of the bootstrap counter is located in the permanent data,along with the unique identi ers of the two other mandatory counters. The bits of loadVeri cationKeyMethods eld specify what validation methods are supported when loading veri cation keys.The eld integrityCheckRootData is used to store a value that can is used to bind the value of a root veri cation key to the MTM.The value is proprietary and can e.g.be a hash of the root veri cation key.The eld internalVeri cationKey,typically a HMAC key,is used to sign and validate internal RIM certi cates.The veri cationAuth value is used for authorization of the MTM InstallRIM command.An additional bit,the loadVeri cationRootKeyEnabled is also part of the global state,but located in the MTM STANY FLAGS structure.2.3Initial keyingFor a MRTM the concept of\Taking Ownership"of the functionality cannot be allowed if secure boot is used.This option can therefore be disabled,and the SRK can be generated at manufacturing time and inserted into the device.Also,in a typical TPM,the process of enrolling identities to it is achieved through the EK and AIK keys.As privacy is not necessarily a consideration e.g.,for an MRTM,the identity is allowed to be pre-set during manufacturing.In other words the EK is not necessary included in the MTM,and the AIK and related certi cates are pre-installed and cryptographically bound to the device before reaching the customer.Secure boot relies on a third semi- xed con guration-the de nition of the PCR types.Each PCR can be restricted to be updatable only by means of an update matching and validated by a RIM certi cate. The bit eld de ning this restriction for the individual PCRs can be updated only by the owner of theMTM(which in the MRTM case is the manufacturer,so the PCR updates in this aspect are\remotelyFigure2:Secure boot operation(from spec.)controlled").This feature will be used as the basis for secure boot after the initial MRTM has been activated.2.4MTM operation and RIM certi catesAt a high level of abstraction the MTM runs in one of three states during the boot phase.Figure2shows that the device boots into an initialization state,governed by the(non MTM)security of the platform. On successful initialization the operation moves to a success state where it stays as long as the PCR updates done using RIM certi cates match a known state as given by the RIMs.On failing to reach such a state the MTM moves to a failed state,becomes inoperational,and stays that way until a device reboot.Additionally,when disabling the MTM the device may forcefully reboot,lock up,disable some hardware interfaces or take any other approach necessary for preserving device security and integrity.3MRTM-the Device Manufacturer's MTMTo best illustrate the scope of the MTM from a device manufacturer's perspective,the minimal function-ality of\a software"MRTM is next presented.As an illustration,the secure boot process is explained embedded into the discussion.During manufacturing,let's assume that there is no incentive for a device manufacturer to enroll new identities to a deployed unit,so no endorsement key EK is installed in the device.Instead,the device manufacturer decides on the AIK,SRK and RVAI keys,and con gures them into the MRTM,e.g.,by means of a secure storage de ned by the secure bootstrap.Also the veri edPCRs list of PCRs that only can be updated using RIM certi cates is de ned,and the loadVeri cationRootKeyEnable ag is set to false-this disables updates to veri edPCRs list and the RVAI.Thus,during MRTM operation,certain, prede ned PCRs can only be modi ed using RIM certi cates.The certi cates are bound to so called integrity keys positioned in a key hierarchy under the installed RVAI.Let us assume that the MRTM is software.Thus,the device is assumed to contain the secure bootstrap de ned as RTE,and RTS can be extracted as part of the same bootstrap.The rst part of RTV boots in this context(e.g.from a ROM),launches the MRTM and its associated state.Then RTV according to the speci cation makes diagnostic measurements regarding itself and the roots-of-trust,and feeds this information(using e.g.MTM VerifyRIMCertAndExtend)into PCRs0and1.It also measures and extends into PCRs the next code to be run,this presumably being some form of bootloader.The secure boot illustration( gure3)shows the boot steps in a graphical form.An important feature of the RTV is the termination of execution(or the forceful execution of some other action)if any invocation of VerifyRIMCertAndExtend fails.This is the essence of the secure boot feature,and essentially what sets the MTM apart from a traditional TPM.3.1CountersCounters are included in the MTM speci cation to achieve freshness guarantees(rollback protection)forthe secure boot procedure.No speci c counters for data/key protection are mandatory.Figure3:Secure bootThree counters need to be managed by the underlying platform architecture.The bootstrap counter is initialized to0,and runs up to a minimum of31steps.This counter is intended to protect the MTM bootstrap,and there must be a one-to-one correspondence between a RIM certi cate for the bootstrap (the\ rmware"in g.3)and a speci c code version.It is critical for the integrity of rmware upgrades in secure boot systems that this correspondence holds and the small range of values makes it possible to implement the counter as(31)one-time programmable bits in hardware.The implementation of a separate RIMProtect counter(running up to a minimum of4095steps)is also required.Even if any RIM certi cate can be bound to the bootstrap version,binding certi cates to RIMProtect enables a higher resolution of(software)upgrades.Still,the RIMprotect counter is singular, i.e.any security-relevant upgrade needed by any functionality bound to this counter induces the need for renewal of all other RIM certi cates bound to RIMprotect,an issue that is partially solved by the introduction of RIM internal certi cates.A third mandatory counter,the StorageProtect counter,is intended to serve as state-protection for the RTS-protected storage.It is not addressed in any MTM interface function,and its minimal size (4095bytes)implies restrictions in use frequency.The RIMProtect counter is updated by the possibly user-authenticated TPM IncrementCounter,whereas the Bootstrap counter can only be updated by the MTM IncrementBootstrapCounter command,its use governed by a RIM certi cate.This is in line with the estimated use of the Bootstrap counter -it is used when a security breach in the bootstrap is found whereby the authorization secret of a TPM IncrementCounter command could have been compromized.In addition to RIM certi cates,veri -cation keys can also be bound to the abovementioned counters.To be noted is that the MTM speci cation is somewhat lax on the platform support needed for counter protection,but intends to be more strict in future standard versions.For implementations of the v1.0speci cation,the statefulness guarantees provided by the counters will vary between devices.3.2RIM Certi catesThe trust bindings related to the RIM certi cates is multi-faceted.A certi cate is typically bound to a counter and one or more PCR values.An external certi cate is signed by a veri cation key,whereas internal ones are essentially tickets for the same data structure,produced by the MTM instance itself for future reference regarding the validity of the certi cate.These two mechanisms are examined in thefollowing:Figure4:State update with external RIM certi cates3.2.1External RIM certi catesThe ver cation keys form a hierarchy with respect to the MTM-the root key of the hierarchy is bound to the root veri cation authority identi er(RVAI),which depending on the MTM implementation can vary,but typically would be a hash of the root veri cation key.The RVAI can be made unmodi able by the MTM LoadVeri cationRootKeyDisable command,turning the internal loadVeri cationRootKeyEnabled ag to false.The same internal state bit disables the MTM SetVeri edPCRSelection command, xing the set of PCR registers only modi able by the use of RIM certi cates.Neither command will ever be needed in an MRTM that is factory-initalized with pre-set values in the RVAI and veri edPCRSelection parameters and the loadVeri cationRootKeyEnabled bit permanently set to false.When loading a veri cation key(using LoadVeri cationKey)either a signature that is part of the veri cation key structure is validated against the key indicated by the parent key handle of the veri cation key being loaded,or,in case of the loaded key being the root key,against the RVAI in any appropriate manner.Thus every successfully loaded veri cation key is guaranteed to be part of a veri cation key hierarchy.When a PCR update is initiated by a MTM VerifyRIMCertAndExtend,the signature on the external RIM certi cate is checked by a loaded veri cation key indicated by a key handle in the command.If the signature matches,and the preconditions,counter value equivalence and PCR contents match,a given PCR is updated with a value stated in the RIM certi cate.A managerial function MTM VerifyRIMCert is included to check a certi cate against a veri cation key and the fact that the counter constraint of the certi cate satis es either the current or any future counter value for the referred counter.In the same manner,a RIM certi cate is also used for the authorization of an MTM IncrementBootstrapCounter command,which sets the bootstrap counter value to the value indicated in the RIM certi cate on the condition that the veri cation key referenced by the certi cate is a key that by parametrization is allowed to control bootstrap counter updates.3.2.2Internal RIM certi catesExternal certi cates can be\internalized",i.e.,rather than validating the certi cate against a veri cation keys on every load,the validation can be done once,whereafter the MTM can convert the external certi cate into an internally validated certi cate.The constraining relations of an internally validated certi cate are similar to an external one,but the signature is a HMAC on a key only known to the MTM, present for the singular purpose of signing internal certi cates.The conversion process is executed usingthe MTM InstallRIM command.Internal certi cates can only be tied to the RIMprotect counter.A couple of details regarding certi cate internalization are worthy of explanation.First,the autho-rization of the InstallRIM command is not based on veri cation keys,but on a TPM authentication token on a key veri cationAuth,assumed to be placed into the MRTM at the time of manufacture-there is no way to modify or change this symmetric key.Additionally,the veri cation process is assumed to be completed by an MTM-external component(knowing the veri cationAuth)validating the key hierarchy needed for the external certi cate to be internalized.The MRTM can be used as\an oracle"for this-on accepting integrity keys,their validity is assured.Also,the validity check of the external certi cate can make use of the MTM VerifyRIMCert command,and deduce correctness from return parameters.Only after these checks,the external party is assumed to produce the authenticated MTM InstallRIM command for RIM certi cate internalization.Thus the validity of the certi cate installation is not guaranteed by the MTM itself,but rather by any entity with knowledge of veri cationAuth.A second detail regarding the internalization of certi cates is that the internal certi cate will have a counter binding of the current RIMProtect counter value plus one,independently of the counter reference value of the external certi cate.Omitting counter checks during the install command is in line with the trust model of the command,and setting the counter reference to one more than the current counter value makes it possible to install many certi cates and make them all usable with one update of the RIMProtect counter.The process of installing RIM certi cates into MTM can be governed by a revocation mechanism built around RIM Auth Validity Lists and RIM Validity Lists[1].The rst one is a fresh list of currently valid veri cation keys that are signed by a given,higher-level veri cation key.If a key is not on the list,it must be assumed to be revoked.A similar construct is available for the actual certi cates in the form of the RIM validity lists,maintained by the authorities behind the ver cation keys that sign the certi cates.These lists are based on the notion of universal time,and it is assumed that the device managing the validity lists has a reasonably accurate and secure clock to support the decisions based on these lists.4Supporting multiple MTMs in a deviceThe reference architecture[1]strongly brings forward the idea of interlocked MTMs in a single device, based on three intehrity-protected lists-the device manufacturer's mandatory engines,the device owner's mandatory engines,and the device owner's discretionary engines.The basic assumption is that all mandatory engines should be securely activated as part of a proper boot,and failure to do so should be treated as a boot error.The integrity-protected lists would be controlled by the device manufacturer and owner respectively.For software implementaitions,it is also to be assumed that the local security(RTV, RTS)of all engines are boostrapped from the device MRTM whereas the identity-related roots-of-trust may and probably should vary between engines.This architecture makes it possible to have separate MTM service domains,where unique engines intended to serve di erent stakeholders and applications are co-located in the same device.In a general sense,the same architectural ideas have already been presented in the TPM domain,a good example being research conducted around virtual TPMs,e.g.,by IBM Research[7].5Other MTM commandsThe MRTM inherits a fair bit of mandatory functionality from TPMv1.2.The basic storage functions related to binding and sealing are all supported,and since the PCRs de ned in veri edPCRs also can be used for the PCR binding,a new(higher)dimension of con gurability for services like secure storage is achieved.Signing and key certi cation are also supported.Veri cation keys can be evicted using TPM FlushSpeci c.For PCR updates in the non-veri ed set the basic TPM Extend is available,and for reporting at least TPM Quote is present in all MTMs.However,especially in MRTMs there may be no EK(no support for provacy CA:s)and AIKs might be pre-installed,so the attestation function might be limited to one certifying authority.In general,delegation,timing,non-volatile memory services and migration,as well as most administrative maintenance commands are declared optional in the context of MTMv1.6MTM implementationFor validating the MTM speci cation we have added MTM speci c functions to an open source TPM emulator[4]and made some modi cations to existing TPM routines as speci ed in[2].The code implements the mandatory command set of an MRTM,as well as optional MRTM and MLTM functions inherited from[4].6.1TSS APITCG has not de ned any new TSS functions for the MTM-functionality.The main reason for this is that the MTM engines are primarily targeted for embedded environments and for the booting phase (MRTM),where consistent and standardized APIs are of less relevance than for TPMs,which primarily are intended to be used by applications.Even so,a consistent API is valuable also in closed environments if it represents a known good design,and in the context of MLTMs RIM certi cates might also be used by applications.We here propose an API for this purpose,which has emerged from the need to test our own MTM implementation.We have extended the TCG standardized TSS API with necessary functions to access MTM func-tionality.This could be a starting point for de ning mobile speci c TSS(MTSS)or merging these functions to TSS.In this work,we have intentionally avoided to de ne new types in TSS level,instead MTM speci c types(RIM certi cates and veri cation keys)are transferred as raw bu ers,the contents re ecting the byte structures de ned by the MTM speci cation.The following new TSS functions have been de ned:TSS_RESULT Tspi_MTM_InstallRIM(TSS_HTPM hTPM,//inUINT32ulRimCertSize,//inBYTE*rimCertData,//inUINT32*outCertSize,//outBYTE**outCertData//out);TSS_RESULT Tspi_MTM_VerifyRIMCert(TSS_HTPM hTPM,//inUINT32ulRimCertSize,//inBYTE*rimCertData,//inUINT32hVerificationKey//in);TSS_RESULT Tspi_MTM_VerifyRIMCertAndExtend(TSS_HTPM hTPM,//inUINT32ulRimCertSize,//inBYTE*rimCertData,//inUINT32hVerificationKey,//inTCPA_PCRVALUE*pPcrValue//out);TSS_RESULT Tspi_MTM_LoadVerificationKey(TSS_HTPM hTPM,//inUINT32hParentKey,//inUINT32verificationKeySize,//inBYTE*verificationKeyData,//inUINT32*hVerificationKey,//outBYTE*loadMethod//out);Figure5:Architecture of the MTM emulator implementationTSS_RESULT Tspi_MTM_LoadVerificationRootKeyDisable(TSS_HTPM hTPM//in);TSS_RESULT Tspi_MTM_SetVerifiedPCRSelection(TSS_HTPM hTPM,//inTCPA_PCR_SELECTION*selection//in);TSS_RESULT Tspi_MTM_IncrementBootstrapCounter(TSS_HTPM hTPM,//inUINT32ulRimCertSize,//inBYTE*rimCertData,//inUINT32hKey//in);The respective purpose of each command is self-explanatory,as the commands re ect MTM func-tions in a one-to-one manner.Error values or command success is indicated by the TSS RESULT pa-rameter.For each command above,a corresponding tpm tools user command has been written.These are tpm setveri edpcrselection,tpm incrementbootstrapcounter,tpm installrim,tpm loadveri cationrootkeydisable, tpm loadveri cationkey as well as tpm verifyrimcert that also executes the extend operation conditional to an input parameter.6.2Implementation detailsThe original open source TPM emulator[4]is a Unix daemon process that can be controlled using either Unix domain socket or by accessing/dev/tpm device.The device interface is provided mainly for backwards compatibility.The emulator has been written using C programming language.The software has its own small cryptographic library that is based on open source MP library[5].The original code contains a few Linux dependencies(macros from Linux kernel source)and there is an option to build a Linux kernel module that provides the device/dev/tpm.In our implementation all Linux dependenices have been removed and the modi ed MTM/TPM emulator can also use Internet domain sockets,as shown in g5.MTM speci c data structures have been added alongside TPM permanent data structures in the TPM emulator.Additionally utility functions to marshal and unmarshal MTM speci c data structures were de-veloped and command handlers have been extended to include the new MTM functionality.Test utilities have been developed to create,sign and display TPM VERIFICATION KEY and TPM RIM CERTIFICATE structures.There are also test utilities for MTM speci c commands.The emulator has been connected to a modi ed TrouSerS[6]TSS stack using a socket interface.Unit test tools and commands have been written in the spirit of the TrouSerS tpm-tools test commands for testing and using the new MTM interfaces and functions in the emulator.The implementation has been validated in Linux,but porting the emulator to other POSIX-compliant architectures is straight-forward.As the MTM speci cation contains lots of optional functionality and features,a policy le has been added for con guring the overall MTM functionality of the emulator for any given purpose or to match a given architecture.6.3Example architecture for use-cases discussionThe following listing contains a simple example session.The MTM emulator mtmd is rst started together with the TrouSerS daemon tcsd.The MTM emulator is connected to tcsd using socket interface and the tpm-tools commands connect to tcsd using a socket interface as well.PCR9is included in the veri edPCRs list.Thus an attempt to extend this PCR with tpm extend fails.The command tpm loadveri cationkey is used to load one TPM VERIFICATION KEY into MTM.The command returns a handle.The command tpm verifyrimcert is used to verify a RIM certi cate using the veri cation key handle as a parameter(-r option)and to extend a PCR register(-e option).The PCR register to be extended is speci ed in the RIM certi cate.$service start mtmd$service start tcsd$tpm_readpcr-n9PCR[09]:0xf443319695979917a03b717049235423874d2716$tpm_extend-n9-e0xae97c310289ce1eb417f6edbfe47ba091eda4467PCR extend failed.$tpm_loadverificationkey-i test.keyHandle is0x123Verification key installed$tpm_verifyrimcert-i test.cert-r123-eRIM certificate successfully verified.PCR extended.$tpm_readpcr-n9PCR[09]:0x2b289e32d928a75e08fc01e730dec3135dc8c6807Examples and Use CasesBy inclusion of the RIM certi cates,the MTM is more capable than a securely booted TPM.This section motivates this statement by introducing a few examples related to an imaginary embedded device depicted in gure6-something akin to a mobile phone.The device deploys secure boot with a trusted domain consisting of at least a bootloader,whereafter a customer might deploy his or her own OS,although the device comes with a certi ed OS and applications as well.The example is mirrored to use the underlying security architecture of Texas Instruments M-shield[3],but similar services can be found with many(mobile)core and chip vendors.An important part of a mobile chip(set)is the HW part of the radio stack-sometimes little more the A/D converters but typically a fair bit of algorithms and state-machine logic as well.If the radio (frequency)is regulated,the access to this functionality should be restricted to the software certi ed for the purpose.This can be achieved by1.wiring the radio enable/disable operation(I/O addresses)to be part of the secure processingenvironment address space(and thus be visible only for programs in that space)2.de ning the extension of one prede ned PCR to also trigger the activation of the radio(as theMTM is software to be run in the secure environment,this is trivially achieved)3.locking the PCR in question to be in the veri edPCRs set and4.issuing a RIM certi cate from the aggregate PCR set of the approved software stack(up to OSand application)to extend the PCR in questionThe example shows that enforcement is trivial to achieve-one simple hardware constraint(item (1))which is reasonable to implement with or without MTM,and a\non-standard"modi cation to the MTM implementation(item(2)).All software can use the MTM interfaces as is,and the enforcement policy is software agnostic in the sense that OS upgrades and old-version revocation using the MTM counters can be de ned in MTM terms over MTM interfaces.The same logic can be transported to a di erent aspect of hardware con guration.In contemporary manufacturing,the price per unit drops as quantities go up.On the other hand,market segmentation。

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

Simplicity of NMTM with TOF-Watch
o
connect the stimulation leads
Basic Anesthesia Training 2002, Monitoring basics-6
Simplicity of NMTM with TOF-Watch
attach the transducer
o
Basic Anesthesia Training 2002, Monitoring basics-4
Simplicity of NMTM with TOF-Watch
place the electrodes
o
Basic Anesthesia Training 2002, Monitoring basics-5
Why to monitor NMB?
%
60 50 40
30 20 10 0 20 30 40 50 60 70 80 Other patients
Pancuronium TOF < 0.7
Age
o
Berg H et al Acta Anaesth Scand 1997; 41: 1095-1103 Basic Anesthesia Training 2002, Monitoring basics-29
Basic Anesthesia Training 2002, Monitoring basics-15
o
Monitoring basics
Neuromuscular Transmission Monitoring (NMTM)
o
Basic Anesthesia Training 2002, Monitoring basics-16
time
Basic Anesthesia Training 2002, Monitoring basics-21
Why monitoring NMB?
Monitoring indicates
• • • • • • • Time for intubation Degree of relaxation Time for additional dose NMBA Time for reversal agent Time for extubation Possible dual block Possible residual curarisation
o
switch on
Basic Anesthesia Training 2002, Monitoring basics-10
Simplicity of NMTM with TOF-Watch
o
calibrate (optional)
Basic Anesthesia Training 2002, Monitoring basics-11
Operating room
o
Basic Anesthesia Training 2002, Monitoring basics-14
Training modules NMTM
• • • • • • Basics Techniques Clinical practice Hands on Frequently Asked Questions TOF-Watch as selling tool
110
100
Inspiratory force (cm H 0)
2
90
80
70
60 Control TOF 0.6 TOF 0.7 TOF 0.8 TOF 0.9 TOF 1.0
o
Degree of Neuromuscular block
Ali HH et al BJA 1975; 47: 570-574
Basic Anesthesia Training 2002, Monitoring basics-26
Safety (Postoperative Residual Curarisation)
Why to monitor NMB?
patients reversed TOF < 0.7 TOF < 0.6 No heal, Anesthesiology 1995;82:404
Why to monitor NMB?
Safety
(complications)
35 30 25 20 15 10 5 0 Induction Maintenance Recovery
o
Patients Admitted to ICU after Anaesthesia Complications
Simplicity of NMTM with TOF-Watch
o
activate TOF mode
Basic Anesthesia Training 2002, Monitoring basics-12
Simplicity of NMTM with TOF-Watch
o
Basic Anesthesia Training 2002, Monitoring basics-13
Cooper AL et al Anaesthesia 1989; 44: 953-958
Basic Anesthesia Training 2002, Monitoring basics-25
Why to monitor NMB? Safety
(postoperative residual curarisation)
o
Basic Anesthesia Training 2002, Monitoring basics-17
Introduction
Monitoring basics
o
Basic Anesthesia Training 2002, Monitoring basics-18
Monitoring basics
1979: 72 50
42% 30% 24%
1990: 80 all
44% 12.5%
Viby-Mogensen
o
Basic Anesthesia Training 2002, Monitoring basics-27
Safety (Postoperative Residual Curarisation)
Simplicity of NMTM with TOF-Watch
o
Hand adapter = transducer + finger fixation
Basic Anesthesia Training 2002, Monitoring basics-9
Simplicity of NMTM with TOF-Watch
Control
(timing)
100 75
50 25 0
o
• • • • • • •
Time for intubation Degree of relaxation Time for additional dose NMBA Time for reversal agent Time for extubation Possible dual block Possible residual curarisation
o
Basic Anesthesia Training 2002, Monitoring basics-3
Selling tool
• No need to be afraid of NMTM
• Just take it serious: it helps you building a good relation with your customer and selling NMBA
Safety (Oesophageal Sphincter Tone)
Introduction
Monitoring basics
• Objective neuromuscular transmission monitoring is the continuous measurement of the effect of muscle relaxants on the muscles in the human body. • To do this appropriately, a motor nerve is stimulated and the muscle contraction, which follows, is objectively evaluated.
o
Des
Desflurane potentiates the effect of vec more than isoflurane Other examples: - antibiotics - anti epileptica Iso - volatile agents
Basic Anesthesia Training 2002, Monitoring basics-24
Objective
Neuromuscular Transmission Monitoring
TOF-Watch
o
Basic Anesthesia Training 2002, Monitoring basics-1
Training on Neuromuscular Transmission Monitoring
Control (medication interaction)
Why to monitor NMB?
100 75 Twitch depression 50 (% control) 25 0
Response to fixed dose of vecuronium in 8 young people
相关文档
最新文档