青少年活动中心2015年秋季学期汇报演出%e——【演出活动 精品策划文案】

文章标题：深度解读：GOST 33259-2015标准书1. 介绍GOST 33259-2015标准书GOST 33259-2015标准书是俄罗斯联邦颁布的国家标准，它包含了各种物品的标准名称、数量、质量和其他规范。

该标准书具有权威性和普适性，对于俄罗斯产品的生产、流通以及国际贸易都具有重要意义。

2. 深度解析GOST 33259-2015标准书的内容和规范GOST 33259-2015标准书总共包含了多个部分和章节，其内容涵盖了各个行业和领域的产品标准规范。

从产品的分类、命名规范到质量要求和测试方法，都有详细的规定和说明。

这些规定不仅保障了产品的质量和安全，也为俄罗斯产品的国际贸易提供了依据。

3. 对GOST 33259-2015标准书的理解和见解作为一个与产品质量和标准规范相关的标准书，GOST 33259-2015的发布对俄罗斯的经济发展和贸易合作有着重要的意义。

它不仅提高了俄罗斯产品的质量水平，也为俄罗斯与其他国家的贸易合作提供了基础和保障。

4. 总结与回顾GOST 33259-2015标准书的出台，标志着俄罗斯在产品标准化和质量监管上迈出了重要的一步。

这对于俄罗斯产品的国际竞争力和贸易合作具有深远的影响。

我们相信，在全球化的背景下，GOST 33259-2015将会进一步推动俄罗斯与世界各国的经济合作，促进经济的繁荣和发展。

5. 个人观点和理解在全球化的浪潮中，各国的产品标准和质量监管愈发重要。

GOST 33259-2015的出台，不仅是俄罗斯产品质量提升的体现，也为俄罗斯在国际贸易中树立了更高的标准和信誉。

我相信，GOST 33259-2015的实施将进一步提升俄罗斯产品在国际市场的竞争力，为俄罗斯经济的发展注入新的活力和动力。

总结：本文对GOST 33259-2015标准书进行了深度解读，从内容和规范到对其意义和影响的分析，全面阐述了该标准书的重要性和价值。

笔者也通过自己的观点和理解，展示了对GOST 33259-2015的认同和支持。

A10 DatasheetV1.002011-8-221.IntroductionWith ARM Cortex A8 core, A10 will drive SoC into a brand new era of connected Smart HD which can enhance the application of connected HD SOC as well as user experiences of consumer electronics like multimedia products. Due to its outstanding connected HD video performance and cost efficiency, the highly integrated A10 is target at cool HD pad which can bring end-users better experiences of surfing, watching, gaming and reading.The A10 is dedicated to furthering the development of connected HD video CODEC application, and 1080P H.264 high profile encoding technology can become one of the benchmarks. Besides its remarkable super HD 2160p video decoding capability, A10 can stream smoothly HD video over internet, including FLASH10.3/HTML5/3RD APK.Besides self-developed display acceleration frame, MALI400 2D/3D GPU has also been introduced to strengthen the connected smart HD SOC in terms of high profile display so that it can support popular smart systems such as Android2.3/3.0 better and improve the performance of Android-loaded products as well as user experience.There is no doubt that low power consumption and excellent user experience will be always on the top of end-users’ wish list. A10 has adoped Allwinnertech’s most advanced technology of video CODEC and power consumption is much lower during 1080p decoding process. What’s more, Allwinnertech will keep applying progressive VLSI design under new process so that end products can become even more competitive with shorter R&D cycle and easier production advantages.2.FeatureCPU●ARM Cortex-A8 Core●32KB I-Cache/32KB D-Cache/256K L2 Cache●Using NEON for video, audio,and graphic workloads eases the burden of supporting moredelicated accelerators across the SoC and enable the system to support the standards oftomorrow●RCT JA V A-Accelerations to optimize just in time(JIT) and dynamitic adaptivecompilation(DAC), and reduces memory footprint up to three times●Trustzone technology allows for secure transactions and digital right managements(DRM)GPU3D●support Open GL ES 2.0 / open VG 1.12D●support BLT / ROP2/3/4●Rotation 90/180/270 degree●Mirror / alpha (including plane and pixel alpha) / color key support●Scaling function with 4*4 taps and 32 phase●Support format conversionVPU●Video Decoding (Super HD 2160P)Support all popular video formats, including VP8,A VS, H.264, H.263,VC-1, MPEG-1/2/4Support 1920*1080@60fps in all formats●Video EncodingSupport encoding in H.264 High Profile format1080p@60fps720p @100fpsDisplay Processing Ability●Four moveable and size-adjustable layers●Support 8 tap scale filter in horizontal and 4 tap in vertical direction for scaling●support Multi-format image input●support Alpha blending / color key / gamma●support Hardware cursor / sprite●support Vertical keystone correction●support Output color correction (luminance / hue / saturation etc)●support motion adaptive de-interlace●support Video enhancement●support 3D format content input/output format convert/display (including HDMI)Display Output Ability●Support HDMI V1.3/V1.4●Flexible LCD interface (CPU / Sync RGB / LVDS) up to 1920*1080 resolution●CVBS / YPbPr up to 1920*1080 resolutionImageInput Ability●Dual camera sensor interface (CSI0 supports ISP function)Memory●16/32-bits SDRAM controllersupport DDR2 SDRAM and DDR3 SDRAM up to 800MbpsMemory Capacity up to 16 G-bits●8-bits NAND Flash Controller with 8 chip select and 2 r/b signalsSupport SLC/MLC/TLC/DDR NANDECC up to 64bitPeripherals● 1 USB 2.0 OTG controller for general application/2 USB2.0 EHCI Controller for HOSTapplication● 4 high-speed Memory controller supports SD version 3.0 and MMC version 4.2●8 UARTs with 64 Bytes TX FIFO and 64 Bytes RX FIFO,1 UART with full modem function2 UARTs with RTS/CTS hardware flow control5 UARTs with two wires● 4 SPI controller1 dedicated SPI controller for serial NOR Flash boot application3 SPI for general applications● 3 Two-Wire Interfaces up to 400Kbps●Key Matrix (8x8) with internal debounce filter●IR controller supports MIR, FIR and IR remoter●2-CH 6-bits LRADC for line control●Internal 4-wire touch panel controller with pressure sensor and 2-point touch●I2S/PCM controller for 8-channel output and 2-channel input●AC97 controller compatible with AC97 version 2.3 standard●Internal 24-bits Audio Codec for 2 channel headphone, 2 channel microphone, 2 channel FMinput and Line input● 2 PWM controllerSystem●8 channel normal DMA and 8 channel dedicateed DMA●Internal (32K+64K) SRAM on chip● 4 timer, 1 RTC timer and 1 watchdogSecurity●Security SystemSupport DES, 3DES, AES encryption and decryption.messagedigestSHA-1,MD5SupportSupport hardware 64-bit random generator●128-bits EFUSE chip IDPackage●TFBGA441package●0.8mm pitch3.Functional Block DiagramDisplayHead PhoneMicrophoneAC AdapterPowerManagementPMU System PowerPlug AC LineSupport 4.1V/4.2V/4.36V USB1,2 HOSTUSB0 OGTUSB1,2 ControllerUSB0 Controller Display3G4.Pin Assignments4.1.DimensionFigure 4-1 A10 TFBGA441 Package Dimension4.2.Pin MapThe following pin maps show the top view of the 441-pin FBGA package pin assignments in fourquadrants (A, B, C, D).Figure 4-2 TFBGA441 Pin Map-Top View [Quadrant A]Figure 4-3 TFBGA441 Pin Map-Top View [Quadrant B]Figure 4-4 TFBGA441 Pin Map-Top View [Quadrant C]Figure 4-5 TFBGA441Pin Map-Top View [Quadrant D]5.Pin Description5.1.Pin Characteristics1.BALL#: Ball numbers on the bottom side associated with each signals on the bottom.2.Pin Name: Names of signals multiplexed on each ball (also notice that the name of the pin is thesignal name in function 0).3.Function: Multiplexing function number.Function 0 is the the default function, but is not necessarily the primary mode.Functions 1 to 5 are possible modes for alternate functions.4.Type: signal direction-I =Input-O =Output-I/O =Input/Output- A = Analog-AIO =Analog Input/Output-PWR =Power-GND =Ground5.Pin Reset State: The state of the terminal at reset (power up).-0: The buffer drives VOL(pull down/pull up resistor not activated)-0 (PD): The buffer drives V OL with an active pull down resistor.-1: The buffer drives VOH (pull down/pull up resistor not activated).- 1 (PU): The buffer drives V OH with an active pull up resistor.-Z: High-impedance-L: High-impedance with an active pull down resistor.-H: High-impedance with an active pull up resistor.6.Pull Up/Down: Denotes the presence of an internal pull up or pull down resister. Pull up and pulldown resistor can be enabled or disabled via software.7.Buffer Strength: Drive strength of the associated output buffer.Table 5-1 Pin Characteristics (FBGA441)Table 5-1BALL# Pin Name Function Type ResetStatePullUp/DownBufferStrength(mA)AB4 SDQ0 I/O AC7 SDQ1 I/OAC4 SDQ2 I/OAB8 SDQ3 I/OAC8 SDQ4 I/OAB5 SDQ5 I/OAB7 SDQ6 I/OBALL# Pin Name Function Type ResetStatePullUp/DownBufferStrength(mA)AC3 SDQ7 I/OAB2 SDQ8 I/OY1 SDQ9 I/OAC2 SDQ10 I/OY2 SDQ11 I/OAA1 SDQ12 I/OAB3 SDQ13 I/OW2 SDQ14 I/OAC1 SDQ15 I/ON1 SDQ16 I/OT2 SDQ17 I/ON2 SDQ18 I/OU1 SDQ19 I/OU2 SDQ20 I/OP1 SDQ21 I/OT1 SDQ22 I/OM2 SDQ23 I/OL1 SDQ24 I/OH1 SDQ25 I/OL2 SDQ26 I/OH2 SDQ27 I/OJ1 SDQ28 I/OM1 SDQ29 I/OG2 SDQ30 I/OK2 SDQ31 I/OH3 SVREF0 IH4 SVREF1 IY5 SVREF2 I AA8 SVREF3 I AB6 SDQS0 I/O AC5 SDQS0# OW1 SDQM0 O AB1 SDQS1 I/O AA2 SDQS1# OW1 SDQM1 O R2 SDQS2 I/O P2 SDQS2# OH4 SDQM2 O K1 SDQS3 I/O J2 SDQS3# OG1 SDQM3 OBALL# Pin Name Function TypeState Up/Down Strength (mA)V2 SCK# OV1 SCK OJ4 SCKE1 ON3 SCKE0 O W4 SA0 OR4 SA1 OU4 SA2 OM4 SA3 OY4 SA4 ON5 SA5 OV4 SA6 OM3 SA7 OAA3 SA8 OP4 SA9 OL3 SA10 OW3 SA11 OP3 SA12 OY3 SA13 OR3 SA14 OK3 SBA0 OL4 SBA1 OK4 SBA2 OT3 SWE OU3 SCAS OT4 SRAS OV3 SCS0 OAA4 SCS1 O AA5 SDOT0 OJ3 SDOT1 O AA7 SZQAA6 SRST O N8/P8/R8 NCM8/N9/P9 VDD_DLL P M9/N10/P10 GND_DLL PPA0 0/1I/OERXD3 2SPI1_CS0 3D5UART2_RTS 4PA1 0/1I/OERXD2 2E5BALL# Pin Name Function TypeState Up/Down Strength (mA)UART2_CTS 4PA2 0/1I/OERXD1 2SPI1_MOSI 3D6UART2_TX 4PA3 0/1I/OERXD0 2SPI1_MISO 3E6UART2_RX 4PA4 0/1I/OETXD3 2D7SPI1_CS1 3PA5 0/1I/OETXD2 2E7SPI3_CS0 3PA6 0/1I/OETXD1 2D8SPI3_CLK 3PA7 0/1I/OETXD0 2E8SPI3_MOSI 3PA8 0/1I/OERXCK 2D9SPI3_MISO 3PA9 0/1I/OERXERR 2E9SPI3_CS1 3PA10 0/1I/OERXDV 2D10UART1_TX 4PA11 0/1I/OEMDC 2E10UART1_RX 4PA12 0/1I/OEMDIO 2UART6_TX 3D11UART1_RST 4PA13 0/1I/OETXEN 2UART6_RX 3E11BALL# Pin Name Function TypeState Up/Down Strength (mA)PA14 0/1I/OETXCK 2UART7_TX 3D12UART1_DTR 4PA15 0/1I/OECRS 2UART7_RX 3E12UART1_DSR 4PA16 0/1I/OECOL 2CAN_TX 3D13UART1_DCD 4PA17 0/1I/OETXERR 2CAN_RX 3C13UART1_RING 4PB0 0/1I/O A15TWI0_SCK 2PB1 0/1I/O B15TWI0_SDA 2PB2 0/1I/O A14PWM0 2PB3 0/1I/OIR_TX 2NC 3B14EINT16 5PB4 0/1I/O A13IR_RX 2PB5 0/1I/OI2S_MCLK 2B13AC97_MCLK 3PB6 0/1I/OI2S_BCLK 2A12AC97_BCLK 3PB7 0/1I/OI2S_LRCK 2B12AC97_SYNC 3PB8 0/1I/OI2S_DO0 2A11AC97_DO 3BALL# Pin Name Function TypeState Up/Down Strength (mA)I2S_DO1 2PB10 0/1I/O C11I2S_DO2 1PB11 0/1I/O C10I2S_DO3 1PB12 0/1I/OI2S_DI 2AC97_DI 3C9NC 4PB13 0/1I/OSPI2_CS1 2B11NC 4PB14 0/1I/OSPI2_CS0 2A10JTAG_MS0 3PB15 0/1I/OSPI2_CLK 2B10JTAG_CK0 3PB16 0/1I/OSPI2_MOSI 2A9JTAG_DO0 3PB17 0/1I/OSPI2_MOSO 2B9JTAG_DI0 3PB18 0/1I/O A8TWI1_SCK 2PB19 0/1I/O B8TWI1_SDA 2PB20 0/1I/O C8TWI2_SCK 2PB21 0/1I/O C7TWI2_SDA 2PB22 0/1I/OUART0_TX 2A7IR1_TX 3PB23 0/1I/OUART0_RX 2B7IR1_RX 3PC0 0/1I/ONWE# 2M23BALL# Pin Name Function TypeState Up/Down Strength (mA)PC1 0/1I/ONALE 2M22SPI0_MISO 3PC2 0/1I/ONCLE 2L23SPI0_CLK 3PC3 0/1I/ONCE1 2L22SDC1_CMD 3 Pull Up (default)PC4 0/1I/O K23NCE0 1 Pull Up (default)PC5 0/1I/ONRD 1K22SDC1_CLK 2PC6 0/1I/ONRB0 2J23SDC2_CMD 3 Pull Up (default)PC7 0/1I/ONRB1 2J22SDC2_CLK 3 Pull Up (default)PC8 0/1I/OND0 2H23SDC2_D0 3PC9 0/1I/OND1 2H22SDC2_D1 3PC10 0/1I/OND2 2G23SDC2_D2 3PC11 0/1I/OND3 2G22SDC2_D3 3PC12 0/1I/OND4 2H21SDC1_D0 3PC13 0/1I/OND5 2H20SDC1_D1 3PC14 0/1I/OND6 2G21BALL# Pin Name Function TypeState Up/Down Strength (mA)PC15 0/1I/OND7 2G20SDC1_D3 3PC16 0/1I/O M21NWP 1 Pull Down (default)PC17 0/1I/O F23NCE2 1 Pull Up (default)PC18 0/1I/O F22NCE3 1 Pull Up (default)PC19 0/1I/ONCE4 1SPI2_CS0 2L21EINT12 5PC20 0/1I/ONCE5 1SPI2_CLK 2K21EINT13 5PC21 0/1I/ONCE6 1SPI2_MOSI 2J21EINT14 5PC22 0/1I/ONCE7 1SPI2_MISO 2J20EINT15 5PC23 0/1I/O G19SPI0_CS0 2 Pull Up (default)PC24 0/1I/O F21NDQSPD0 0/1I/OLCD0_D0 2AB15LVDS0_VP0 3PD1 0/1I/OLCD0_D1 2AC15LVDS0_VN0 3PD2 0/1I/OLCD0_D2 2AB14LVDS0_VP1 3PD3 0/1I/OLCD0_D3 2AC14BALL# Pin Name Function TypeState Up/Down Strength (mA)PD4 0/1I/OLCD0_D4 2AB13LVDS0_VP2 3PD5 0/1I/OLCD0_D5 2AC13LVDS0_VN2 3PD6 0/1I/OLCD0_D6 2AB12LVDS0_VPC 3PD7 0/1I/OLCD0_D7 2AC12LVDS0_VNC 3PD8 0/1I/OLCD0_D8 2AB11LVDS0_VP3 3PD9 0/1I/OLCD0_D9 2AC11LVDS0_VN3 3PD10 0/1I/OLCD0_D10 2Y15LVDS1_VP0 3PD11 0/1I/OLCD0_D11 2AA15LVDS1_VN0 3PD12 0/1I/OLCD0_D12 2Y14LVDS1_VP1 3PD13 0/1I/OLCD0_D13 2AA14LVDS1_VN1 3PD14 0/1I/OLCD0_D14 2Y13LVDS1_VP2 3PD15 0/1I/OLCD0_D15 2AA13LVDS1_VN2 3PD16 0/1I/OLCD0_D16 2Y12LVDS1_VPC 3PD17 0/1I/O AA12BALL# Pin Name Function TypeState Up/Down Strength (mA)LVDS1_VNC 3PD18 0/1I/OLCD0_D18 2Y11LVDS1_VP3 3PD19 0/1I/OLCD0_D19 2AA11LVDS1_VN3 3PD20 0/1I/OLCD0_D20 2Y10CSI1_MCLK 3PD21 0/1I/OLCD0_D21 2AA10SMC_VPPEN 3PD22 0/1I/OLCD0_D22 2AB10SMC_VPPPP 3PD23 0/1I/OLCD0_D23 2AC10SMC_DET 3PD24 0/1I/OLCD0_CLK 2Y9SMC_VCCEN 3PD25 0/1I/OLCD0_DE 2AA9SMC_RST 3PD26 0/1I/O LCD0_HSYNC 2AB9SMC_SLK 3PD27 0/1I/O LCD0_VSYNC 2AC9SMC_SDA 3PE0 0/1I/OTS0_CLK 2E23CSI0_PCK 3PE1 0/1I/OTS0_ERR 2E22CSI0_CK 3PE2 0/1I/OTS0_SYNC 2D23CSI0_HSYNC 3BALL# Pin Name Function TypeState Up/Down Strength (mA)TS0_DVLD 2CSI0_VSYNC 3PE4 0/1I/OTS0_D0 2C23CSI0_D0 3PE5 0/1I/OTS0_D1 2C22CSI0_D1 3PE6 0/1I/OTS0_D2 2B23CSI0_D2 3PE7 0/1I/OTS0_D3 2B22CSI0_D3 3PE8 0/1I/OTS0_D4 2A23CSI0_D4 3PE9 0/1I/OTS0_D5 2A22CSI0_D5 3PE10 0/1I/OTS0_D6 2B21CSI0_D6 3PE11 0/1I/OTS0_D7 2A21CSI0_D7 3PF0 0/1I/OSDC0_D1 2M20JTAG_MS1 4PF1 0/1I/OSDC0_D0 2M19JTAG_DI1 4PF2 0/1I/OSDC0_CLK 2L20UART0_TX 4PF3 0/1I/OSDC0_CMD 2L19JTAG_DO1 4PF4 0/1I/OSDC0_D3 2K20BALL# Pin Name Function TypeState Up/Down Strength (mA)PF5 0/1I/OSDC0_D2 2K19JTAG_CK1 4PG0 0/1I/OTS1_CLK 2CSI1_PCLK 3F20SDC1_CMD 4PG1 0/1I/OTS1_ERR 2CSI1_MLCK 3E21SDC1_CLK 4PG2 0/1I/OTS1_SYNC 2CSI1_HSYNC 3E20SDC1_D0 4PG3 0/1I/OTS1_DVLD 2CSI1_VSYNC 3D21SDC1_D1 4PG4 0/1I/OTS1_D0 2CSI1_D0 3SDC1_D2 4D20CSI0_D8 5PG5 0/1I/OTS1_D1 2CSI1_D1 3SDC1_D3 4C21CSI0_D9 5PG6 0/1I/OTS1_D2 2CSI1_D2 3UART3_TX 4E19CSI0_D10 5PG7 0/1I/OTS1_D3 2CSI1_D3 3UART3_RX 4C20CSI0_D11 5PG8 0/1I/O D19BALL# Pin Name Function TypeState Up/Down Strength (mA)CSI1_D4 3UART3_RTS 4CSI0_D12 5PG9 0/1I/OTS1_D5 2CSI1_D5 3C19UART3_CTS CSI0_D134 5PG10 0/1I/OTS1_D6 2CSI1_D6 3UART4_TX 4D18CSI0_D14 5PG11 0/1I/OTS1_D7 2CSI1_D7 3UART4_RX 4C18CSI0_D15 5PH0 0/1I/OLCD1_D0 2ATAA0 3UART3_TX 4EINT0 6A6CSI1_D07PH1 0/1I/OLCD1_D1 2ATAA1 3UART3_RX 4EINT1 6B6CSI1_D17PH2 0/1I/OLCD1_D2 2ATAA2 3UART3_RTS 4EINT2 6C6CSI1_D27PH3 0/1I/OLCD1_D3 2ATAIRQ 3UART3_CTS 4A5EINT3 6BALL# Pin Name Function TypeState Up/Down Strength (mA)CSI1_D37PH4 0/1I/OLCD1_D4 1ATAD0 2UART4_TX 3EINT4B5CSI1_D4PH5 0/1I/OLCD1_D5 2ATAD1 3UART4_RX 4EINT5 6C5CSI1_D57PH6 0/1I/OLCD1_D6 2ATAD2 3UART5_TX 4MS_BS 5EINT6 6A4CSI1_D67PH7 0/1I/OLCD1_D7 2ATAD3 3UART5_RX 4MS_CLK 5EINT7 6B4CSI1_D77PH8 0/1I/OLCD1_D8 2ATAD4 3KP_IN0 4MS_D0 5EINT8 6C4CSI1_D87PH9 0/1I/OLCD1_D9 2ATAD5 3KP_IN1 4MS_D1 5EINT9 6D4CSI1_D97BALL# Pin Name Function TypeState Up/Down Strength (mA)PH10 0/1I/OLCD1_D10 2ATAD6 3KP_IN2 4MS_D2 5EINT10 6A3CSI1_D107PH11 0/1I/OLCD1_D11 2ATAD7 3KP_IN3 4MS_D3 5EINT11 6CSI1_D117B3PH12 0/1I/OLCD1_D12 2ATAD8 3PS2_SCK1 4EINT12 6C3CSI1_D127PH13 0/1I/OLCD1_D13 2ATAD9 3PS2_SDA1 4SMC_RST 5EINT13 6A2CSI1_D137PH14 0/1I/OLCD1_D14 2ATAD10 3PS2_KP_IN4 4SMC_VPPEN 5EINT14 6B2CSI1_D147PH15 0/1I/OLCD1_D15 2ATAD11 3KP_IN5 4SMC_VPPPP 5A1EINT15 6BALL# Pin Name Function TypeState Up/Down Strength (mA)CSI1_D157PH16 0/1I/OLCD1_D16 2ATAD12 3KP_IN6 4SMC_DET 5EINT16 6B1CSI1_D167PH17 0/1I/OLCD1_D17 2ATAD13 3KP_IN7 4SMC_VCCEN 5EINT17 6C1CSI1_D177PH18 0/1I/OLCD1_D18 2ATAD14 3KP_OUT0 4SMC_SLK 5EINT18 6C2CSI1_D187PH19 0/1I/OLCD1_D19 2ATAD15 3KP_OUT1 4SMC_SDA 5EINT19 6D1CSI1_D197PH20 0/1I/OLCD1_D20 2ATAOE 3CAN_TX 4EINT20 6D2CSI1_D207PH21 0/1I/OLCD1_D21 2ATADREQ 3CAN_RX 4EINT21 6D3CSI1_D217BALL# Pin Name Function TypeState Up/Down Strength (mA)PH22 0/1I/OLCD1_D22 2ATADACK 3KP_OUT2 4CSI1_D225E2SDC1_CMD7PH23 0/1I/OLCD1_D23 2ATACS0 3KP_OUT3 4SDC1_CLK5E3CSI1_D237PH24 0/1I/OLCD1_CLK 2ATACS1 3KP_OUT4 4SDC1_D05E3CSI1_PCLK7PH25 0/1I/OLCD1_DE 2ATAIORDY 3KP_OUT5 4SDC1_D15E4CSI1_FIELD7PH26 0/1I/OLCD1_HSYNC 2ATAIORDY 3KP_OUT6 4SDC1_D25F3CSI1_HSYNC7PH27 0/1I/OLCD1_VSYNC 2ATAIOW 3KP_OUT7 4SDC1_D35F4CSI1_VSYNC7PI0 0/1I/OA20NC 2PI1 0/1I/OB20NC 2A19 PI20/1I/OBALL# Pin Name Function TypeState Up/Down Strength (mA)NC 2PI3 0/1I/O B19PWM1 2PI4 0/1I/O A18SDC3_CMD 2PI5 0/1I/O B18SDC3_CLK 2PI6 0/1I/O A17SDC3_D0 2PI7 0/1I/O B17SDC3_D1 2PI8 0/1I/O A16SDC3_D2 2PI9 0/1I/O B16SDC3_D3 2PI10 0/1I/OSPI0_CS0 2UART5_TX 3C17EINT22 6PI11 0/1I/OSPI0_CLK UART5_RX 2 3D17EINT23 6PI12 0/1I/OSPI0_MOSI 2UART6_TX 3C16EINT2 6PI13 0/1 I/OSPI0_MISO 2UART6_RX 3D16EINT25 6PI14 0/1 I/OSPI0_CS1 2PS2_SCK1 3TCLKIN0 4A18EINT26 6PI15 0/1 I/OSPI1_CS1 2PS2_SDA1 3TCLKIN1 4B18EINT27 6BALL# Pin Name Function TypeState Up/Down Strength (mA)PI16 0/1 I/OSPI1_CS0 2UART2_RTS 3A17EINT28 6PI17 0/1 I/OSPI1_CLK 2UART2_CTS 3B17EINT29 6PI18 0/1 I/OSPI1_MOSI 2UART2_TX 3A16EINT30 6PI19 0/1 I/OSPI1_MISO 2UART2_RX 3B16EINT31 6PI20 0/1 I/OPS2_SCK0 2UART7_TX 3E14HSCL 6PI21 0/1 I/OPS2_SDA0 2UART7_RX 3E13HSDA 6NC I pull-upT9 GNDW8 UBOOT_SEL I pull-upT10 JTAG_SEL0/1I/O pull-upH16 TEST 0I/O pull-downF5 NMI#AC14 RESET# 0AN20 DM0 0/1 ION21 DP00/1 IOP20 DM10 PWR- - - P21 DP10 GND- - - L16 UVCC_C 0 PWR- - - L14 UGND_C 0 GND- - - L15 UVCC_T 0/1 PWRL13 UGND_T 0/1 GNDBALL# Pin Name Function TypeState Up/Down Strength (mA)K16 ULVDD PWRK14 ULGND GNDR20 DM2 IOR21 DP2 IOY22 XP_TP 0AIAA22 XN_TP 0AIY23 YP_TP 0AIAA23 YN_TP 0AIAC23 MIC1OUTN 0AC22 MIC1OUTP 0Y21 FMINR0Y20 FMINL0AA21 VMIC0 - -AC21 MICIN20 - -AC20 MICIN10 - -W20 VRA10V20 VRA20T19 A VCC 0W21 VRP0AB21 LINEINR0 - -AB20 LINEINL0U19 AGND 0W19 HPR 0Y19 HPL 0V19 HPGND 0AA20 HPCOMFB 0AC19 HPVCC 0Y19 HPL 0AB23 LRADC0 0AIAB22 LRADC1 0AIAC16 TVOUT0 0AOAB16 TVOUT1 0AOAC17 TVOUT2 0AOAB17 TVOUT3 0AOW15 VCC33_TVOUT0 PWR- - - W18 GND33_TVOUT0 GND- - - AC18 NC 0AB18 NC0AA17 NC0Y17 NC0W16 NC 0BALL# Pin Name Function TypeState Up/Down Strength (mA)Y18 NC 0W17 NC 0AA18 NC 0AA16 NC 0Y16 NC 0V23 TX0P_HDMI 0V22 TX0N_HDMI0U23 TX1P_HDMI0U22 TX1N_HDMI0T23 TX2P_HDMI0T22 TX2N_HDMI0W23 TXCP_HDMI0W22 TXCN_HDMI0T13 VP_HMDI 0P13/R13/P14 GND_HDMI 0R23 SCL_HDMI 0R22 SDA_HDMI0P22 HPD_HDMI0P23 CEC_HDMI0R14/T14 NCT20 NC0T21 NC0U21 NC0U20 NC0V21 NC0P19/R19 NC0M16/M15 NC0N15/N16 NC 0M14/N13 NC 0F1 CLK32K_INAF2 CLK32K_OUT0 AK8 RTC_VDDPWR-- - N23 CLK24M_IN 0 AN22 CLK24M_OUT 0 AR16/T16/R15/T15 NC0 PWR- - - P16 PLLVP25 0P15 PLLGND 0GND-- - H8/H9/H10J8/J9/J10 J14/H15 VCC(8) 0PWR- - -BALL# Pin Name Function TypeState Up/Down Strength (mA)N19 VCC_CARD 0PWR- - - H19/J19 VCC_NAND(2) 0 PWR- - -G5/H5/L5/M5/R5/T5/W5/W6/W7/Y7/ VCC_ DRAM(10)0 PWR- - -J5/k5/N5/P5/U5/V5/Y7/Y8/G3/G4GND_DRAM (10)0 GND- - - L8/L9/K9/K10/T8/R9/R10/ K15/J15/J16 VDD(10) 0PWR- - -J12/J13/H11/H12/H13/H14VDD2（6）H11/H12/H13/H14J12/J14VDDCPU(6) T8/R9/R10L8/L9/K9/K10K15/J15/J16VDD_INT(10)L10/L11/L12/K11/K12/K13/J11/M10/M11/M12/M13/N11/N12/ P11/P12/R11/R12/T11/T12 GND(19) 0GND- -W12/W13/W14 VCC_ LVDS (3) 0 PWR- - -W9/W10/W11 GND_LVDS(3) 0 GND- - -F19 VCC_CSI0E18 VCC_CSI1。

产品目录列表FTALK-CA001B-EN-P – 2008年8月代替FTALK-CA001A-EN-P – 2007年11月目录品牌–R o c k w e l l S o f t w a r e和FactoryTalk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i v折扣计划表. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .i vF a c t o r y T a l k?服务平台应用表. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v设计和组态. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Arena? ......................................................... (1)R S L i n x?C l a s s i c/R S L i n x?Enterprise .................................................... (2)R S L o g i x?Architect ..................................................... (2)R S L o g i x? Micro ......................................................... . (2)R S L o g i x?5 ............................................................. . (3)R S L o g i x? 500............................................................ .. (3)R S L o g i x? 5000........................................................... . (4)R S L o g i x?捆绑包............................................................. . (5)RSNetWorx? .................................................... .. (6)通讯捆绑包............................................................. . (6)R S T u n e?和R S L o o p Optimizer? .................................................... (7)R S F i e l d b u s?组态软件............................................................. (7)生产管理. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9F a c t o r y T a l k?Batch ......................................................... (9)F a c t o r y T a l k B a t c h服务器......................................................... (9)F a c t o r y T a l k?H i s t o r i a n C l a s s i c f o rBatch (10)iF a c t o r y T a l k? ProductionCentre ................................................. .. (10)F a c t o r y T a l k?ProductionCentre ............................................. (10)F a c t o r y T a l k?P r o d u c t i o n C e n t r e应用............................................................ (10)F a c t o r y T a l k?P r o d u c t i o n C e n t r e数据管理..............................................................10F a c t o r y T a l k?P r o d u c t i o n C e n t r e报表和分析 (11)F a c t o r y T a l k?P r o d u c t i o n C e n t r e系统支持..............................................................1 1 F a c t o r y T a l k? Scheduler ........................................................ .. (11)F a c t o r y T a l k?S c h e d u l e r专业版..............................................................................1 1F a c t o r y T a l k?S c h e d u l e rViewer..............................................................................1 1F a c t o r y T a l k?S c h e d u l e r标准版..............................................................................1 1 数据管理. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13F a c t o r y T a l k?Gateway .......................................................... (13)F a c t o r y T a l k?H i s t o r i a n S i t eEdition..................................................................................1 3F a c t o r y T a l k?H i s t o r i a n S i t e E d i t i o n服务器 (1)4F a c t o r y T a l k?H i s t o r i a n客户端工具.....................................................................1 4第三方H i s t o r i a n接口............................................................ (14)F a c t o r y T a l k?H i s t o r i a n Classic .......................................................... ...............................1 5F a c t o r y T a l k?H i s t o r i a n C l a s s i c服务器..................................................................1 5F a c t o r y T a l k?H i s t o r i a n C l a s s i c A u t h o r i n g客户端 (16)FactoryTalk? Metrics/FactoryTalk? Historian Classic Runtime客户端许可.......1 6 F a c t o r y T a l k? Integrator ....................................................... .. (17)F a c t o r y T a l k?T r a n s a c t i o n Manager .......................................................... (17)F a c t o r y T a l k?T r a n s a c t i o n M a n a g e r专业版............................................................18F a c t o r y T a l k?T r a n s a c t i o n M a n a g e r标准版............................................................18F a c t o r y T a l k?T r a n s a c t i o n M a n a g e r连接器............................................................18 质量和规范化遵守. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19纠正措施/预防措施(CAPA) ........................................................... (19)R S B i z W a r e?eProcedure? ....................................................... (19)资产管理. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..............2 1F a c t o r y T a l k?AssetCentre....................................................... (21)R S M A C C?服务器和客户端................................................................ ............................2 2iiR S M A C C?企业级在线状态监视................................................................ ....................2 2 Emonitor? ......................................................... .. (2)2E m o n i t o r?–资产健康状态模块............................................................................2 3E m o n i t o r?W e b客户端............................................................ (23)F i e l d c a r e Hart ............................................................. . (23)RSEnergyMetrix?.................................................... . (24)R S P o w e r?32................................................................ . (24)R S P o w e r? Plus ............................................................. (25)绩效和可视化. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27F a c t o r y T a l k?Metrics .......................................................... (27)F a c t o r y T a l k?M e t r i c s服务器............................................................ (27)F a c t o r y T a l k?M e t r i c s A u t h o r i n g客户端............................................................ (28)FactoryTalk? Metrics/FactoryTalk? Historian Classic Runtime客户端 (29)F a c t o r y T a l k?Portal............................................................ (29)F a c t o r y T a l k?M a c h i n eEdition(ME) ...................................................... (30)F a c t o r y T a l k?V i e w M a c h i n e E d i t i o n S t a t i o nRuntime (30)F a c t o r y T a l k?V i e wStudio........................................................ (30)F a c t o r y T a l k?V i e w S i t e Edition(SE)....................................................... .. (30)F a c t o r y T a l k?V i e w S i t e E d i t i o n服务器............................................................ (30)F a c t o r y T a l k?V i e w S i t e E d i t i o n客户端...................................................................3 1F a c t o r y T a l k?V i e w S i t e E d i t i o n工作站...................................................................3 1 K E P S e r v e r Enterprise........................................................ . (31)RSView?32 ......................................................... .. (32)R S V i e w?32M e s s e n g e rPro .......................................................... .........................3 3 R S V i e w?32A c t i v e D i s p l a y System........................................................ ..............3 3 R S V i e w?3 2 WebServer .................................................... . (33)iiiRSAdvantage? FactoryTalk?ProductionCentre生产管理Propack Data? PMX RS PMX? MES 生产管理Propack Data? PMX CTM RS PMX? CTM 质量和规范化遵守FactoryTalk? Automation Platform FactoryTalk? ServicesPlatformFactoryTalk?服务平台FactoryTalk? Live Data FactoryTalk?服务平台RSAssetSecurity? FactoryTalk? Security FactoryTalk?服务平台FactoryTalk? Audit FactoryTalk?服务平台RSAssetSecurity? FactoryTalk? Security FactoryTalk?服务平台FactoryTalk? Audit FactoryTalk?服务平台FactoryTalk? Directory FactoryTalk?服务平台FactoryTalk? Diagnostics FactoryTalk?服务平台FactoryTalk? Alarms andEventsFactoryTalk?服务平台FactoryTalk? HighAvailabilityFactoryTalk?服务平台iv集成化生产和绩效套件FactoryTalk?服务平台应用表v vi集成化生产和绩效套件设计和组态设计和组态Arena?Arena仿真软件不由罗克韦尔自动化销售渠道直接销售。

Page 1Ultra96 Getting Started GuideVersion 1.0Document ControlDocument Version: 1.0Document Date:27 June 2018Page 2Contents1Getting Started with Ultra96 (5)2What’s Inside the Box? (5)2.1Optional add-on items: (5)3What’s on the Web? (6)3.1Official Documentation: (6)3.2Tutorials and Reference Designs: (6)3.3Trainings and Videos: (6)4Ultra96 Key Features (7)5Ultra96 Basic Setup and Operation (9)6Example Design (10)7Hardware Setup (10)8Connect to Webserver (11)9Ultra96 GPIO LEDs Example Project (13)10OpenAMP Matrix Multiplication (14)11Additional Example Projects (14)12Custom Content Tutorial (15)13Smart Tutorial (16)14Using Ultra96 Tutorial (16)15Access Ultra96 Linux Terminal over SSH (17)16INA226 Current Sensor (19)17Power Off (20)18Getting Help and Support (21)18.1Avnet Support (21)18.2Xilinx Support (22)19Installing and Licensing Xilinx Software (23)19.1Install Vivado Design Suite, Design Edition (23)20Certification Disclaimer (27)21Safety Warnings (27)22RF Certification (27)Page 3FiguresFigure 1 – Ultra96 (5)Figure 2 – Ultra96 Block Diagram (8)Figure 3 – Ultra96 Topology (9)Figure 4 – Ultra96 Switch Location (10)Figure 5 – MicroSD Card Boot Mode (11)Figure 6 – Connect to Ultra96 Webserver (12)Figure 7 – Ultra96 GPIO LEDs (13)Figure 8 – OpenAMP Matrix Multiplication (14)Figure 9 – Ultra96 Tutorials/Guides (15)Figure 10 – TeraTerm New Connection (17)Figure 11 – SSH Terminal Settings (18)Figure 12 – SSH Authentication (18)Figure 13 – Ultra96 Terminal (19)Figure 14 – I2Cdetect (19)Figure 15 – Reading INA226 Device (20)Figure 16 – Voucher Confirmation (24)Figure 17 – Generate Node-Locked (24)Figure 18 – Select Host Information (25)Page 4Page 5 1 Getting Started with Ultra96The Avnet Ultra96 enables hardware and software developers to explore the capabilities of the Zynq® UltraScale+™ MPSoC . Designers can create or evaluate designs for both the Zynq Processor Subsystem (PS) and the Programmable Logic (PL) fabric.Figure 1 – Ultra96This Getting Started Guide will outline the steps to setup the Ultra96 hardware. It documents the procedure to run a PetaLinux design running on the Quad-core ARM Cortex-A53 MPCore Processing System (PS).2 What’s Inside the Box?∙Ultra96 development board ∙Pre-programmed 16GB microSD card with SD adapter and jewel case ∙Voucher for SDSoC license from Xilinx ∙Quick Start Instruction card 2.1 Optional add-on items: ∙External 96Boards compliant power supply kit (12V, 2A, US plug) (AES-ACC-U96-PWR) ∙USB-to-JTAG/UART pod for Ultra96 (AES-ACC-U96-JTAG) ∙∙3 What’s on the Web?Ultra96 is a community-oriented kit, with all materials being made available through the community website.3.1 Official Documentation:∙Getting started guide∙Hardware user guide∙Schematics∙Bill of materials∙Layout∙PCB net lengths∙Mechanical drawing∙3D Model∙Board definition files for Vivado integration∙Programmable logic (PL) master user constraints3.2 Tutorials and Reference Designs:∙Ultra96 Bare Metal Hardware Platform Creation∙Ultra96 Bare Metal Microchip USB-UART∙Ultra96 Bare Metal Test Application Development∙Ultra96 Bare Metal Boot Techniques∙Ultra 96 Factory Restore Image∙Ultra96 Accelerated Image Classification3.3 Trainings and Videos:∙Introduction to Ultra96Page 64 Ultra96 Key Features∙Zynq UltraScale+ MPSoC ZU3EG SBVA484∙Memoryo Micron 2 GB (512M x32) LPDDR4 Memoryo MiroSD SocketShips with Delkin Utility MLC 16GB card∙ Wi-Fi / Bluetooth∙ DisplayPort∙ 1x USB 3.0 Type Micro-B upstream port∙ 2x USB 3.0 Type A downstream ports∙ 40-pin Low-speed expansion header∙ 60-pin High speed expansion header∙ Mounted on thermal bracket with fanNote that there is no on-board, wired Ethernet interface. All communications must be done via USB, Wi-Fi, JTAG, or expansion interface.Page 7Page 9 5 Ultra96 Basic Setup and OperationThe functionality of the Ultra96 is determined by the application booted from the non-volatile memory – by default that is the SD Card. This Getting Started Guide allows system developers to exercise and demonstrate multiple circuits through PetaLinux, including:∙SSH Terminal Access ∙GPIO LEDs ∙Wi-Fi ∙ I2C Sensor DetectIn addition to the items included in the kit, you will also need the following to complete the exercises in this tutorial.∙ Wi-Fi connectionAn Ultra96 image in its expected out-of-box configuration is shown below along with various topology components highlighted.Figure 3 –Ultra96 Topology6 Example DesignThe Ultra96 ships with an example image loaded in the 16GB microSD Card. If your microSD Card image has been corrupted or deleted, there is Ultra 96 Factory Restore available at that will go into detail on how to restore your factory image.7 Hardware Setup1. A terminal program is required. TeraTerm was used in this example which can bedownloaded from the TeraTerm project on the SourceForge Japan page:ttssh2.sourceforge.jp Install TeraTerm or another terminal program of your choice.2. Plug in your 12V Barrel Jack power supply into a wall outlet and then connect the barreljack to J5 on your Ultra96. Your Ultra96 should be powered down at this point. Note: DC power supply is not included in the Ultra96 kit but can be purchased separately.3. Set the Ultra96 boot mode switch SW2 to SD Card boot mode as shown below.Figure 4 – Ultra96 Switch LocationPage 108 Connect to Webserver1. Press and release the power button (SW3). The Green Power On LED (DS9), RedINIT_B LED (DS7) and the Green User LEDs should illuminate. After a few seconds, INIT_B LED will turn off and the Green DONE LED (DS6) will illuminate. At 15 seconds, the Blue Bluetooth Enable LED (DS1) will illuminate. At 30 seconds, the Yellow Wireless LAN Enable LED (DS8) will illuminate.2. After about 40 seconds, a new Wi-Fi SSID will be discoverable, named“Ultra96_<MAC_ID>” which is unique for each board. Connect the Wi-Fi on your PC to this SSID.Page 11Figure 6 – Connect to Ultra96 Webserver3. Now that we are connected to the Ultra96, we should open up the webserver. Open aninternet browser window and navigate to the following address : http://192.168.2.14. You will be directed to the webserver’s home page for Ultra96. Here you will be able toview example projects, custom contents and various tutorials for Ultra96.Page 129 Ultra96 GPIO LEDs Example Project1. Next we want to access the Ultra96 GPIO LEDs example project. From the Ultra96 homepage select Ultra96 GPIO LEDs example projectFigure 7 – Ultra96 GPIO LEDs2. All LEDs will be at an unknown state to begin with. Select the drop down menus andbegin changing the status of the GPIO LEDs. You will notice that the four LEDs (located in between the two USB connectors J8/J9) update in real time.3. Scroll to the bottom of the webpage and you will see a definition table for various LEDselection options.4. Something of interest may be setting LEDs 0 and LEDs 1 to phy0tx and phy0rxrespectively.5. Now as you navigate throughout this webserver you will notice the Wi-Fi transmitting andreceiving LEDs flickering as you are sending and receiving data from the Ultra96.Page 1310 OpenAMP Matrix Multiplication1. Select Example Projects up at the top of the page. You will see a list of projects alongwith descriptions of each.2. Select OpenAMP Matrix Multiplication which is the second in the list.Figure 8 – OpenAMP Matrix Multiplication3. Read through the description which goes over what is going to happen in the OpenAMPMatrix Multiplication Design and then select Run Project4. In the Output section you will see the two input matrices and then the matrix multiplicationresults.11 Additional Example Projects1. Return back to the Example Projects page by selecting the Example Project tab at thetop.2. As you can see there are seven additional example projects available to you. Feel freeto explore them. However some require additional hardware such as the Grove Starter Kit to complete.Page 1412 Custom Content Tutorial1. Now select the Tutorial tab at the top of the page. You will be directed to aTutorials/Guides pageFigure 9 – Ultra96 Tutorials/Guides2. This sections goes into how to get started with the out of box microSD card image wehave been exploring up to this point. As of now we have explored the Run Example Projects section.3. Let’s take a look at the Custom Content tutorial. Select Custom Content.4. This Tutorial goes over the three different ways custom content can be added to this outof box image. The three different ways being1) Uploading custom files2) Making custom webpages3) Making custom projects5. To access these options select the Custom Content tab at the top of the webpage.Page 1513 Smart Tutorial1. Now return back to the Ultra96 Tutorials page. This time select Smart from the tutoriallist2. This tutorial goes into explaining how to use the Smart Package Manager (smart) toupdate/install packages.3. This tutorial also provides an example that you can follow along with that will showcasea use case of how to write a simple “Hello World” application, compile it, create a RPMpackage with CMake, install/remove it with smart, and then run it.14 Using Ultra96 Tutorial1. Return back to the Tutorials page and now select the Using Ultra96 tutorial2. This tutorial goes over the various ways you can interact with the Ultra96. As of now wehave only done this using the Webapp.3. We will not be exploring accessing your Ultra96 over miniDP or UART since by defaultyou would need additional hardware to access it through these two peripherals.4. Read through the SSH section, it states we can access the Ultra96 terminal usingTeraTerm or a PuTTY terminal application.5. Since we have already downloaded and installed TeraTerm at the beginning of this guidelet’s access the Ultra96’s Linux terminal over SSH using TeraTermPage 1615 Access Ultra96 Linux Terminal over SSH1. Verify that your PC is still connected to the Ultra96 Websever by checking your wirelessnetwork.2. Open TeraTerm and then select File New connection… as seen in the image below.Figure 10 – TeraTerm New ConnectionPage 17Page 183. A new TeraTerm: New connection window will open. We now want to connect to Ultra96over SSH, select TCP/IP and then configure your Terminal settings the same as the below figure.Figure 11 – SSH Terminal Settings4. Select OK5. You will then be prompted to enter SSH Authentication information. In our case it islooking for the Linux terminal ’s user name and passphrase which are root and root .6. Please type in root for the User name and then type in root for the Passphrase as well.Then select OK .Figure 12 –SSH Authentication7. You now have access to the Ultra96 Terminal!Figure 13 – Ultra96 Terminal16 INA226 Current Sensor1. Now that we have access to the Linux Terminal let’s try and read from the INA226 CurrentSensor on our board.2. Type in your console i2cdetect –y –r 1Figure 14 – I2Cdetect3. As you can see some devices are coming back as unavailable under I2C detect, thismeans they may already be monitored by some other driver within the system. That is the case for the INA226 Current Sensor on Ultra964. It turns out there is a Linux sysfs drive for INAxxx devices that is already built into thekernel:Page 19https:///pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/hwmon/ina2xx5. Based on this it turns out that you can actually just read the system current from theINA226 device by using the sensor command.6. In your terminal type sensorsFigure 15 – Reading INA226 Device7. As you can see the current, voltage, and temperature measurements are reported back.8. This is one of the lesser known but highly useful Linux subsystems.17 Power Off1. When you are done experimenting with your Ultra96 and wish to power off the board,press and release the Power button (SW3) located on the top side of your Ultra96 next to the barrel jack.2. You will notice your board does not power down immediately. It will take roughly 10-20seconds for your board to completely power down. The reason behind this is it is adhering to the various power down sequencing requirements.3. Please note, if you do not let your Ultra96 power off as per the power down sequencingrequirements (such as unplugging the barrel jack), your SD Card may get corrupted or damaged.4. To power off the Ultra96 you can also press and hold Sw3 for 10 seconds to force apower off. This is useful for when the soft power-off appears to no work.Page 2018 Getting Help and Support18.1 Avnet SupportThe Ultra96 is a versatile development kit that allows evaluation of the Zynq MPSoC, which can help you adopt Zynq into your next design. All technical support is offered through website support forums. Ultra96 users are encouraged to participate in the forums and offer help to others when possible./forums/zed-english-forumTo access the most current collateral for Ultra96 please visit the community support page at: /content/support –Hardware/Vivado Support–Software SupportOnce on the support page:To access the latest Ultra96 documentation, click on the Documentation link:To access the latest reference designs for Ultra96, click on the following link:To access the Ultra96 technical forums, click on the following link:Page 21To view online training and videos, click on the following link:18.2 Xilinx SupportFor questions regarding products within the Product Entitlement Account, visit the Contact Support site for Xilinx:https:///support/service-portal/contact-support.htmlFor technical support including the installation and use of the product license file, contact Xilinx Online Technical Support at /support. The following assistance resources are also available on the website:∙Software, IP and documentation updates∙Access to technical support web tools∙Searchable answer database with over 4,000 solutions∙User forumsPage 2219 Installing and Licensing Xilinx Software19.1 Install Vivado Design Suite, Design EditionThe Zynq device on the Ultra96 is supported in Vivado Design Suite, Design Edition. Version 2018.1 or later is required to use the pre-installed board definition file.You must license your Vivado Design Suite, Design Edition with the license that came with your Ultra96. To obtain your free license, visit the following website and insert the voucher code from the certificate included in your kit:/getlicense1. Log in2. Fill out information at Product Licensing - Name and Address Verification, then clickNext3. Select your Account4. Enter your voucher code here, then click Redeem Now.Page 235. At the confirmation screen, click Yes.Figure 16 – Voucher Confirmation6. Under Certificate Based Licenses, find OEM Zynq ZU3 Ultra96 Vivado Design EditionVoucher pack and check the box. Now click Generate Node-Locked License.Figure 17 – Generate Node-LockedPage 247. Create or select your Host ID. Click Next.Figure 18 – Select Host InformationPage 258. Review the license request, then click Next again.If a full seat of Vivado System or Design Edition has already been installed, then no further software will be needed. Please check online for any updates at:/support/download/index.htmFor detailed instructions on installing and licensing the Xilinx tools, please refer to the latest version of Vivado Design Suite User Guide Release Notes, Installation, and Licensing (UG973).Page 2620 Certification DisclaimerBoth CE and FCC certifications are necessary for system level products in those countries governed by these regulatory bodies.Because Avnet boards are intended for evaluation kits only and destined for professionals (you) to be used solely at research and development facilities for such purposes, they are considered exempt from the EU product directives and normally are not tested for CE or FCC compliance.If you choose to use your board to transmit using an antenna, it is your responsibility to make sure that you are in compliance with all laws for the country, frequency, and power levels in which the device is used. Additionally, some countries regulate reception in certain frequency bands. Again, it is the responsibility of the user to maintain compliance with all local laws and regulations.This board should be used in a controlled lab environment by professional developers for prototype and development purposes only. The board included in the kit is not intended for production use unless additional end product testing and certification is performed.21 Safety WarningsThis product shall only be connected to an external power supply that is 96boards compliant.Only compatible plug-in modules shall be connected to Ultra96. The connection of incompatible devices may affect compliance or result in damage to the unit and void the warranty.This product shall be operated in a well-ventilated environment. If a case is used, it shall have adequate ventilation.22 RF CertificationThe frequency range is 2.4 to 2.4835GHz.The max power complies with 802.11b, which is 17dBm (typ).More information on RF certification for the TI WiLink8 module is available here:/index.php/WL18xxMOD_Regulatory_Product_Certification#Countri es_Accepting_FCC.2FIC.2FCE.2FMIC_ReportsPage 27。

DU-05348-001_v7.5 | September 2015Installation and Verification on Mac OS XTABLE OF CONTENTS Chapter 1. Introduction (1)1.1. System Requirements (1)1.2. About This Document (2)Chapter 2. Prerequisites (3)2.1. CUDA-capable GPU (3)2.2. Mac OS X Version (3)2.3. Xcode Version (3)2.4. Command-Line T ools (4)Chapter 3. Installation (5)3.1. Download (5)3.2. Install (5)3.3. Uninstall (6)Chapter 4. Verification (8)4.1. Driver (8)4.2. Compiler (8)4.3. Runtime (9)Chapter 5. Additional Considerations (11)CUDA® is a parallel computing platform and programming model invented by NVIDIA. It enables dramatic increases in computing performance by harnessing the power of the graphics processing unit (GPU).CUDA was developed with several design goals in mind:‣Provide a small set of extensions to standard programming languages, like C, that enable a straightforward implementation of parallel algorithms. With CUDA C/C++, programmers can focus on the task of parallelization of the algorithms rather than spending time on their implementation.‣Support heterogeneous computation where applications use both the CPU and GPU. Serial portions of applications are run on the CPU, and parallel portions are offloaded to the GPU. As such, CUDA can be incrementally applied to existingapplications. The CPU and GPU are treated as separate devices that have their own memory spaces. This configuration also allows simultaneous computation on the CPU and GPU without contention for memory resources.CUDA-capable GPUs have hundreds of cores that can collectively run thousands of computing threads. These cores have shared resources including a register file and a shared memory. The on-chip shared memory allows parallel tasks running on these cores to share data without sending it over the system memory bus.This guide will show you how to install and check the correct operation of the CUDA development tools.1.1. System RequirementsTo use CUDA on your system, you need to have:‣ a CUDA-capable GPU‣Mac OS X 10.9 or later‣the Clang compiler and toolchain installed using Xcode‣the NVIDIA CUDA Toolkit (available from the CUDA Download page)Introduction T able 1 Mac Operating System Support in CUDA 7.5Before installing the CUDA Toolkit, you should read the Release Notes, as they provide important details on installation and software functionality.1.2. About This DocumentThis document is intended for readers familiar with the Mac OS X environment andthe compilation of C programs from the command line. You do not need previous experience with CUDA or experience with parallel computation.2.1. CUDA-capable GPUTo verify that your system is CUDA-capable, under the Apple menu select About This Mac, click the More Info … button, and then select Graphics/Displays under the Hardware list. There you will find the vendor name and model of your graphics card. If it is an NVIDIA card that is listed on the CUDA-supported GPUs page, your GPU is CUDA-capable.The Release Notes for the CUDA Toolkit also contain a list of supported products.2.2. Mac OS X VersionThe CUDA Development Tools require an Intel-based Mac running Mac OSX v. 10.9 or later. To check which version you have, go to the Apple menu on the desktop and select About This Mac.2.3. Xcode VersionA supported version of Xcode must be installed on your system. The list of supported Xcode versions can be found in the System Requirements section. The latest version of Xcode can be installed from the Mac App Store.Older versions of Xcode can be downloaded from the Apple Developer Download Page. Once downloaded, the Xcode.app folder should be copied to a version-specific folder within /Applications. For example, Xcode 6.2 could be copied to /Applications/ Xcode_6.2.app.Once an older version of Xcode is installed, it can be selected for use by running the following command, replacing <Xcode_install_dir> with the path that you copied that version of Xcode to:sudo xcode-select -s /Applications/<Xcode_install_dir>/Contents/DeveloperPrerequisites 2.4. Command-Line T oolsThe CUDA Toolkit requires that the native command-line tools are already installed on the system. Xcode must be installed before these command-line tools can be installed. The command-line tools can be installed by running the following command:$ xcode-select --installNote: It is recommended to re-run the above command if Xcode is upgraded, or an older version of Xcode is selected.You can verify that the toolchain is installed by running the following command:$ /usr/bin/cc --version3.1. DownloadOnce you have verified that you have a supported NVIDIA GPU, a supported version the MAC OS, and clang, you need to download the NVIDIA CUDA Toolkit.The NVIDIA CUDA Toolkit is available at no cost from the main CUDA Downloads page. The installer is available in two formats:work Installer: A minimal installer which later downloads packages required forinstallation. Only the packages selected during the selection phase of the installer are downloaded. This installer is useful for users who want to minimize download time.2.Full Installer: An installer which contains all the components of the CUDA Toolkitand does not require any further download. This installer is useful for systemswhich lack network access.Both installers install the driver and tools needed to create, build and run a CUDA application as well as libraries, header files, CUDA samples source code, and other resources.The download can be verified by comparing the posted MD5 checksum with that of the downloaded file. If either of the checksums differ, the downloaded file is corrupt and needs to be downloaded again.To calculate the MD5 checksum of the downloaded file, run the following:$ openssl md5 <file>3.2. InstallUse the following procedure to successfully install the CUDA driver and the CUDA toolkit. The CUDA driver and the CUDA toolkit must be installed for CUDA to function. If you have not installed a stand-alone driver, install the driver provided with the CUDA Toolkit.If the installer fails to run with the error message "The package is damaged and can't be opened. You should eject the disk image.", then check that your security preferences are set to allow apps downloaded from anywhere to run. This setting can be found under: System Preferences > Security & Privacy > GeneralChoose which packages you wish to install. The packages are:‣CUDA Driver: This will install /Library/Frameworks/CUDA.framework and the UNIX-compatibility stub /usr/local/cuda/lib/libcuda.dylib that refers to it.‣CUDA Toolkit: The CUDA Toolkit supplements the CUDA Driver with compilers and additional libraries and header files that are installed into /Developer/ NVIDIA/CUDA-7.5 by default. Symlinks are created in /usr/local/cuda/pointing to their respective files in /Developer/NVIDIA/CUDA-7.5/. Previous installations of the toolkit will be moved to /Developer/NVIDIA/CUDA-#.# to better support side-by-side installations.‣CUDA Samples (read-only): A read-only copy of the CUDA Samples is installed in /Developer/NVIDIA/CUDA-7.5/samples. Previous installations of the samples will be moved to /Developer/NVIDIA/CUDA-#.#/samples to better support side-by-side installations.A command-line interface is also available:‣--accept-eula: Signals that the user accepts the terms and conditions of the CUDA-7.5 EULA.‣--silent: No user-input will be required during the installation. Requires --accept-eula to be used.‣--install-package=<package>: Specifies a package to install. Can be used multiple times. Options are "cuda-toolkit", "cuda-samples", and "cuda-driver".‣--log-file=<path>: Specify a file to log the installation to. Default is /var/log/ cuda_installer.log.Set up the required environment variables:export PATH=/Developer/NVIDIA/CUDA-7.5/bin:$PATHexport DYLD_LIBRARY_PATH=/Developer/NVIDIA/CUDA-7.5/lib:$DYLD_LIBRARY_PATHIn order to modify, compile, and run the samples, the samples must also be installed with write permissions. A convenience installation script is provided: cuda-install-samples-7.5.sh. This script is installed with the cuda-samples-7-5 package.T o run CUDA applications in console mode on MacBook Pro with both an integratedGPU and a discrete GPU, use the following settings before dropping to console mode:1.Uncheck System Preferences > Energy Saver > Automatic Graphic Switch2.Drag the Computer sleep bar to Never in System Preferences > Energy Saver3.3. UninstallThe CUDA Driver, Toolkit and Samples can be uninstalled by executing the uninstall script provided with each package:T able 2 Mac Uninstall Script LocationsAll packages which share an uninstall script will be uninstalled unless the --manifest=<uninstall_manifest> flag is used. Uninstall manifest files are located in the same directory as the uninstall script, and have filenames matching .<package_name>_uninstall_manifest_do_not_delete.txt.For example, to only remove the CUDA Toolkit when both the CUDA Toolkit and CUDA Samples are installed:$ cd /Developer/NVIDIA/CUDA-7.5/bin$ sudo perl uninstall_cuda_7.5 \--manifest=.cuda_toolkit_uninstall_manifest_do_not_delete.txtBefore continuing, it is important to verify that the CUDA toolkit can find and communicate correctly with the CUDA-capable hardware. To do this, you need to compile and run some of the included sample programs.Ensure the PATH and DYLD_LIBRARY_PATH variables are set correctly.4.1. DriverIf the CUDA Driver is installed correctly, the CUDA kernel extension (/System/ Library/Extensions/CUDA.kext) should be loaded automatically at boot time. To verify that it is loaded, use the commandkextstat | grep -i cuda4.2. CompilerThe installation of the compiler is first checked by running nvcc -V in a terminal window. The nvcc command runs the compiler driver that compiles CUDA programs. It calls the host compiler for C code and the NVIDIA PTX compiler for the CUDA code. The NVIDIA CUDA Toolkit includes CUDA sample programs in source form. To fully verify that the compiler works properly, a couple of samples should be built. After switching to the directory where the samples were installed, type:make -C 0_Simple/vectorAddmake -C 0_Simple/vectorAddDrvmake -C 1_Utilities/deviceQuerymake -C 1_Utilities/bandwidthTestThe builds should produce no error message. The resulting binaries will appear under <dir>/bin/x86_64/darwin/release. To go further and build all the CUDA samples, simply type make from the samples root directory.4.3. RuntimeAfter compilation, go to bin/x86_64/darwin/release and run deviceQuery. Ifthe CUDA software is installed and configured correctly, the output for deviceQuery should look similar to that shown in Figure 1.Figure 1 Valid Results from deviceQuery CUDA SampleNote that the parameters for your CUDA device will vary. The key lines are the first and second ones that confirm a device was found and what model it is. Also, the next-to-last line, as indicated, should show that the test passed.Running the bandwidthTest sample ensures that the system and the CUDA-capable device are able to communicate correctly. Its output is shown in Figure 2Figure 2 Valid Results from bandwidthT est CUDA SampleNote that the measurements for your CUDA-capable device description will vary from system to system. The important point is that you obtain measurements, and that the second-to-last line (in Figure 2) confirms that all necessary tests passed.Should the tests not pass, make sure you have a CUDA-capable NVIDIA GPU on your system and make sure it is properly installed.If you run into difficulties with the link step (such as libraries not being found), consult the Release Notes found in the doc folder in the CUDA Samples directory.To see a graphical representation of what CUDA can do, run the particles executable.Now that you have CUDA-capable hardware and the NVIDIA CUDA Toolkit installed, you can examine and enjoy the numerous included programs. To begin using CUDA to accelerate the performance of your own applications, consult the CUDA C Programming Guide.A number of helpful development tools are included in the CUDA Toolkit to assistyou as you develop your CUDA programs, such as NVIDIA® Nsight™ Eclipse Edition, NVIDIA Visual Profiler, cuda-gdb, and cuda-memcheck.For technical support on programming questions, consult and participate in the Developer Forums.NoticeALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATEL Y, "MATERIALS") ARE BEING PROVIDED "AS IS." NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSL Y DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE.Information furnished is believed to be accurate and reliable. However, NVIDIA Corporation assumes no responsibility for the consequences of use of such information or for any infringement of patents or other rights of third parties that may result from its use. No license is granted by implication of otherwise under any patent rights of NVIDIA Corporation. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all other information previously supplied. NVIDIA Corporation products are not authorized as critical components in life support devices or systems without express written approval of NVIDIA Corporation.TrademarksNVIDIA and the NVIDIA logo are trademarks or registered trademarks of NVIDIA Corporation in the U.S. and other countries. Other company and product names may be trademarks of the respective companies with which they are associated. Copyright© 2009-2015 NVIDIA Corporation. All rights reserved.。

Rev. 3.0–23.09.20211SEMiX ®3pGBTrench IGBT ModulesSEMiX703GB12M7p Features*•Homogeneous Si•Trench = Trenchgate technology •V CE(sat) with positive temperature coefficient•High overload capability •Low loss high density IGBTs•Press-fit pins as auxiliary contacts •UL recognized, file no. E63532Typical Applications•AC inverter drives •UPS•Renewable energy systemsRemarks•Product reliability results are valid for T j =150°C (recommended T j,op =-40...+150°C)•V isol between temperature sensor and power section is only 2500V•For storage and case temperature with TIM see document “TP(*) SEMiX 3p”Absolute Maximum Ratings SymbolConditions Values UnitIGBT V CES T j =25°C 1200V I C T j =175°CT c =25°C 863A T c =80°C656A I Cnom 700A I CRM1400A V GES -20 (20)V t psc V CC =800V V GE ≤ 15V V CES ≤ 1200 VT j =150°C8µs T j -40...175°C Inverse diodeV RRM T j =25°C 1200V I F T j =175°CT c =25°C 796A T c =80°C593A I FRM 1400A I FSM t p =10ms, sin 180°, T j =25°C3456A T j -40...175°C Module I t(RMS)600A T stg module without TIM -40...125°C V isolAC sinus 50Hz, t =1min4000VCharacteristics SymbolConditionsmin.typ.max.UnitIGBT V CE(sat)I C =700A V GE =15V chiplevel T j =25°C 1.55 1.94V T j =150°C 1.81V V CE0chiplevel T j =25°C 0.860.96V T j =150°C 0.75V r CE V GE =15V chiplevelT j =25°C 0.99 1.41m ΩT j =150°C1.51m ΩV GE(th)V CE = 10 V, I C =69mA5.466.6V I CES V GE =0V,V CE =1200V, T j =25°C 5mA C ies V CE =10V V GE =0Vf =1MHz 132.0nF C oes f =1MHz 4.14nF C res f =1MHz1.62nF Q G V GE =-8V ... + 15V 6150nC R Gint T j =25°C 0.7Ωt d(on)V CC =600V I C =700AV GE =+15/-15V R G on =1.5ΩR G off =1.5Ωdi/dt on =5850A/µs di/dt off =5450A/µs dv/dt =5400V/µs L s =25nH T j =150°C 390ns t r T j =150°C 130ns E on T j =150°C 83mJ t d(off)T j =150°C 530ns t f T j =150°C 110ns E off T j =150°C 77mJR th(j-c)per IGBT0.058K/W R th(c-s)per IGBT (λgrease =0.81 W/(m*K))0.035K/W R th(c-s)per IGBT, pre-applied phase change material0.025K/W2Rev. 3.0–23.09.2021© by SEMIKRONSEMiX ®3pGBTrench IGBT ModulesSEMiX703GB12M7p Features*•Homogeneous Si•Trench = Trenchgate technology •V CE(sat) with positive temperature coefficient•High overload capability •Low loss high density IGBTs•Press-fit pins as auxiliary contacts •UL recognized, file no. E63532Typical Applications•AC inverter drives •UPS•Renewable energy systemsRemarks•Product reliability results are valid for T j =150°C (recommended T j,op =-40...+150°C)•V isol between temperature sensor and power section is only 2500V•For storage and case temperature with TIM see document “TP(*) SEMiX 3p”Characteristics SymbolConditionsmin.typ.max.UnitInverse diodeV F = V EC I F =700AV GE =0V chiplevelT j =25°C 2.20 2.59V T j =150°C 2.25 2.53V V F0chiplevel T j =25°C 1.39 1.59V T j =150°C 1.08 1.18V r FchiplevelT j =25°C 1.16 1.42m ΩT j =150°C1.67 1.93m ΩI RRM I F =700A di/dt off =6300A/µs V GE =-15VV CC =600VT j =150°C 510A Q rr T j=150°C110µC E rr T j =150°C 50mJR th(j-c)per diode0.073K/W R th(c-s)per diode (λgrease =0.81 W/(m*K))0.039K/W R th(c-s)per diode, pre-applied phase change material0.031K/W Module L CE 20nH R CC'+EE'measured per switchT C =25°C 0.8m ΩT C =125°C1.1m ΩR th(c-s)1calculated without thermal coupling 0.009K/W R th(c-s)2including thermal coupling,T s underneath module (λgrease =0.81 W/(m*K))0.014K/W R th(c-s)2including thermal coupling,T s underneath module, pre-applied phase change material 0.011K/WM s to heat sink (M5)36Nm M t to terminals (M6)36Nm Nm w350g Temperature Sensor R 100T c =100°C (R 25=5 k Ω)493 ± 5%ΩB 100/125R (T)=R 100exp[B 100/125(1/T-1/T 100)]; T[K];3550 ±2%K© by SEMIKRON Rev. 3.0–23.09.202134Rev. 3.0–23.09.2021© by SEMIKRONThis is an electrostatic discharge sensitive device (ESDS) due to international standard IEC 61340.*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.6。

TRVV标准什么是TRVV标准？TRVV标准是一种用于评估和量化一个系统的可靠性、可用性、可维护性和性能的标准。

TRVV是指Total Reliability, Availability, Maintainability and Performance的首字母缩写。

可靠性(Reliability)的定义和重要性可靠性是指在给定的时间内，系统能够持续提供正常的服务而不出现故障的能力。

在TRVV标准中，可靠性是衡量系统质量的一个重要指标。

可靠性的好坏直接影响到用户对系统的信任度和满意度。

一个高可靠性的系统可以确保用户在使用过程中不会遇到意外的中断或故障，提高用户体验，并增加用户的忠诚度。

可靠性评估指标1.MTBF：平均无故障时间，是指平均故障发生时间间隔。

2.MTTR：平均修复时间，是指故障修复的平均时间。

3.故障率：是指单位时间内出现故障的次数。

提高可靠性的方法•设备和材料的选型要合理，要选择具有较高可靠性的设备和材料。

•加强预防性维护，定期检查和保养设备，及时发现和排除潜在故障。

•进行可靠性测试，通过模拟真实的使用环境和条件，测试系统的可靠性。

•在设计阶段考虑冗余和备份机制，以便在故障发生时能够快速切换和恢复。

可用性(Availability)的定义和重要性可用性是指系统能够按照用户的需求和期望，以及在特定要求或工作条件下，持续提供所需服务的能力。

在TRVV标准中，可用性是衡量系统可靠性的一个重要指标。

可用性的好坏直接关系到用户的满意度和系统的稳定性。

一个高可用性的系统可以确保用户能够随时随地访问所需的服务，提高用户的工作效率和便捷性。

1.Uptime：系统的正常运行时间占总运行时间的比例。

2.Downtime：系统的停机时间，即系统无法提供服务的时间。

3.Mean Time to Repair (MTTR)：平均修复时间，是指系统停机后恢复正常运行所需要的平均时间。

改善可用性的方法•提供冗余和备份机制，以保证在设备故障时能够快速切换至备份设备。

OWNER MANUALTOYOTAHILUX REVO 2015+This manual contains the Toyota HILUX REVO +2015 ƒVVKPI KPUVTWEVKQPU HQTSump Guard Skid Plate Ref.: 48002297 Gearbox Skid Plate Ref.: 48002298 Transfer Skid Plate Ref.: 48002299 Fuel Tank Skid Plate Ref.: 48002300The CompanyFounded in 1995, AFN - 4x4 Accessories dedicates itself to the production and commerce of all-terrain accessories. Its constant concern in its customers total satisfaction, and in the ideals of innovation and transformation have granted a position of notability both in the national and international panorama.The only company in Portugal in the mass production of 4x4 accessories, relies on specialized and experienced techni-cians, with the most adequate knowled-ge, to an efficient response capability to its customers demands.Thanks to the specialization in the several areas of design and manufacture and to a constant investment in techno-logy, AFN has been broadening its wide range of products, without ever neglec-ting the quality factor.4x4 AccessoriesIn its diversity of products we can include,with all-terrain quality, protection, safetyand aesthetic accessories.And it is here that AFN invest on the besttechnology, the best cut precision of theraw material, and the transformation ofproducts with the quality recognized inthe marketplace.AFN has, at its disposal, resources totest and analyse the resistance of itsproducts and stands in the front rowregarding the European homologationof materials dedicated to all terrain.The contact with the most importanttest laboratories for vehicles, both inEngland, Spain and Germany, providesAFN with the know-how to manufacturea wide range of quality products.Our Design ApproachAFN designs each accessorie taking intoconsideration the original model lines and fi -xing points. We refuse to have a “one designfits all” solution and we are always lookingfoward to embrace new challenges on howto adjust a new product into a new model!The days of just throwing on a bit of steeltogether to form a protection system aregone. AFN is leading the way modern vehicleprotection components are manufactured.Other will follow, and it won’t be long wherethe AFN approach to Styling, Fit, Form andFunction will become the benchmark for allother manufacturers.1 INTRODUCTIONAFN 4x4 AccessoriesProduct: Sump Guard Skid PlatePart Ref.: 48002297Product: Gearbox Skid PlatePart Ref.: 48002298Product: Transferbox Skid PlatePart Ref.: 48002299Product: Fuel Tank Skid PlatePart Ref.: 48002300Product: Rear Axle Skid PlatePart Ref.: 48002301Introduction1 Checklist Products 48002297, 48002298, 48002299, 48002300, 480023012 Fitting Instructions3 Hilux REVO Catalogue4 Warranty Terms5 AFN 4x4 Partners247131415- In this section you have a checklist with all parts included for the installation of your AFN product- This product should be installed as demonstrated in the product fi tting instructions- If veri fied that any component is damaged, please contact your nearest AFN distributor - The specified parts will onlyfi t in the models specifi ed by AFN - Do not modify any component of the productPlease note that the following checklists are divided by each Underbody Protection reference . With that in mind, if you are using the full Underbody Protections , there are some part numbers that will be duplicated, just put them aside .1 CHECKLISTX1X4X6X1X8X1Ref.: 46006474Ref.: 46006475Ref.: 46006409Ref.: 45000044M8Ref.: 45000043M6x20Ref.: 45000011M8Ref.: 45000312Ref.: 46006412Ref.: 45000036Ref.: 45000074M6Ref.: 45000066X4X1X8X4X4Zinc Plated Zinc Plated Zinc PlatedZinc Plated Zinc Plated Zinc PlatedZinc Plated48002298 - Gearbox Skid Plate48002297 - Sump Guard Skid PlateRef.: 45000011M8Ref.: 45000008M8x30Ref.: 47001717Ref.: 45000312M12x130x40Ref.: 45000036M12Ref.: 45000017M10Ref.: 45000010M10Ref.: 45000069M10x35Ref.: 45000066M12Ref.: 46006416Ref.: 46006414Ref.: 46006413X2X2X2X1X2X4X8X6X10X4X4X1Zinc Plated Zinc PlatedZinc Plated Zinc Plated Zinc Plated Zinc PlatedZinc Plated Zinc Plated48002299 - Transferbox Skid PlateRef.: 46006417Ref.: 45000011X5X148002300 - Fuel Tank Skid PlateRef.: 47001855Ref.: 46006421Ref.: 45000113M6x15Ref.: 45000008M8x30Ref.: 45001721Ref.: 46006419Ref.: 45000044M6Ref.: 46006476Ref.: 45000011M8Ref.: 46007003Ref.: 46006418Ref.: 45000018M8X1X2X1X1X13 X1X1X1X6X1X1X6Zinc PlatedZinc PlatedZinc PlatedZinc PlatedZinc PlatedZinc PlatedZinc PlatedSizeM6M8M10M12Torque Nm9 Nm22 Nm44 Nm77 NmTorque lbft7 lbft16 lbft32 lbft57 lbft- Wrench- Ratchet wrench- Allen wrench- Lift- 2 hours (All underbody protections)- 1 person (recommended)Tools RequiredMouting Time2 FITTING INSTRUCTIONSStep 2Before fi tting the Front SkidPlate -48002297, place it on a working surface and fi t 46006474.Bolts needed:1 - 45000043; 45000044 x2; 45000074; M6x20Repeat this step on the other side for part number 46006475.Give the fi nal torque.It must look like as showed in the image on the right.Fit the Front Skid Plate -48002297 on the vehicle chassis.Bolts needed:1 - OEM* bolts; 45000011; M82 - OEM* bolts; 45000011; M8Give the fi nal torque .Step 3Fit the bottom of the Front Skid Plate -48002297 to the chassis.Bolts needed:1 - OEM* bolts; 45000011; M8Be in mind that if you have more underbody protections to be fi tted, do NOT FULL TIGHT .Give the fi nal torque .1211Step 5Step 6Fit the bottom of the Gearbox Skid Plate - 48002298 in the chassis.Bolts needed:1 - 45000312; 45000036 x2; 45000066; M12x130x40Repeat this step on the other side of the Gearbox Skid Plate .Give the fi nal torque .Fit part number 47001717 on the vehicle chassis.Then, fi t part number 46006416. It must enter from the outer side of vehicle.Parts needed:1 - 46006416;2 - 45000069; 45000010 x2; 45000017; M10x35Repeat this step on the other side of part number 46006416.Give the fi nal torque .Fit the Gearbox Skid Plate -48002298 in the chassis. This one must be fi tted above the Transferbox Skid Plate - 48002297. Bolts needed: 1 - OEM* bolts; 45000011; M82 - 45000008; 45000011; M8Tip : you may use a jack to hold the protection in place.Give the fi nal torque .21212*OEM - Original Equipment Manufacturer1Be in mind that there are some cables in this area, so be careful they don’tbe crushed.Step 9Step 8Fit the Transferbox Skid Plate -48002299 in the chassis. This one must be fi tted as showed in the image on the right.If you have the Gearbox Skid Plate - 48002298 mounted on the vehicle, use its bolts and nuts (see #step5)Parts needed: 1 - 46006414;2 - 45000312; 45000036 x2; 45000066; M12x130x403 - 45000110; 45000010; 45000017; M10x25Give the fi nal torque .Fit the Fuel Tank Skid Plate - 48002300 as showed in the image.It must be fi tted fi rst on the side, then in the bottom.Bolts needed:1 - 45000011; OEM* Nut; M8Remove the OEM* Fuel Tank Protection as showed in the image.Be aware that you must save the OEM* Nuts, you’ll use them later in the AFN Fuel Tank Skid Plate - 48002300.1 - OEM* Nut;11123Step 10Step 11The following step may very depending on which version of vehicle you have, so be aware that:- European Version:Join 47001855 with 46007003.- Tropicalized Version:Join 47001721 with 46006421.Before fi tting the Rear Axle Skid Plate - 48002301 in the chassis, take on part number 47001721/47001855and fi t it to part number 46006421/46007003.Parts needed:1 - 46006421 / 46007003;2 - 45000113; 45000044; M6x153 - 47001721 / 47001855;4 - 46006476;5 - 45000120; 45000011; M8x15Give the fi nal torque .Once the Fuel Tank Skid Plate- 48002300 is in place, fi t the other 4OEM* nuts, as showed in the image on the right.Bolts needed: 1 - 45000011; M8Give the fi nal torque .Put the Rear Axle Brackets - 46006419, one on each side as showed in the image.Fit the Rear Axle Skid Plate - 48002301 in the Rear Axle Brackets - 46006419.Bolts needed:1 - 45000008; 45000011 x2; M8x30Repeat this step on the other side .1124513Reminder !Maintenance | CareBefore operating a vehicle fi tted with an AFN Underbody Protections:- Make sure all fi ttings are tightenedPeriodically check and tighten all nuts. Stripped, fractured or bent bolts or nuts need to be replaced.Step 13Your new AFN UNDERBODY PROTECTIONS are now installed on your Toyota Hilux REVO !Have Fun!Fit the Rear Axle Skid Plate -48002301 to the 47001721 / 47001855.Bolts needed:1 - 45000008; 45000011 x2; 48000018; M8x30Give the fi nal torque .113Ref.: 48002297 - Sump Guard Skid Plate (*Al)Ref.: 48002470 - Front Bumper Ref.: 48002304 - Rear Step Bar w/ trailer hitch Ref.: 48002323 - Nerf Bars Ref.: 48002295 - Bull Bar with fog lights Ref.: 48002296 -Rear Bumper w/ Wheel and Jerry-can carrierRef.: 48002302 - Side StepsRef.: 48002299 - Transfer Box Skid Plate (*Al)Ref.: 48002298 - Gearbox Axle Skid Plate (*Al)Ref.: 48002300 - Fuel Tank Skid Plate (*Al)*Al - AluminiumAFN 4x4 Accessories is becoming a well known brand for its products due to its quality, design and safety which arechallenged for thousands of people everyday, worldwide.In its diversity of products we can include, with all-terrain quality, protection, safety and aesthetic accessories. With that being said, AFN 4x4 has some other accessories that every offroad passionate would like to have, such are Body Pro-tections , Underbody Protections , Light Holders , Storage (Wheel Supports and Jerry-can carriers) and others related to the Aesthetics .We have some 4x4 accessories that combine with the original model lines that if you take a closer look you will see that they don't appear to be an accessorie, but a must-have.Please be in mind that some accessories are available only to some models.Feel free to check all the products that may interest you in our website at: www.afn.pt3 Hilux REVO CATALOGUE4 WARRANTY TERMSAFN4x4 products are warranted free from defects in materials and workmanship for a period of two (2) years from thedate of initial retail purchase. Third-party components are delivered under the original manufacturer warranty.Under the present warranty, AFN4x4 obligation shall be limited to repairing, replacing or crediting, at its option, any partfound to be defective.AFN4x4 does not warrant or make any representations concerning its goods when:a) The products are purchased used, scratch and dent or when the box was opened.b) The products are not installed, used, and maintained strictly in accordance with AFN4x4’s instructions.c) The products are installed in vehicles that are used in competition.d) The products are installed in vehicles fi tted with aftermarket non-standard tires with diameters in excess of OEM*specifi cations.e) The products are installed in vehicles with engines that have been modifi ed to increase performance.AFN4x4 will not be responsible for goods damaged in transit. If any goods arrive damaged, please contact the AFN4x4as soon as possible. AFN4x4 will assess and may arrange to have the damaged goods returned to a AFN4x4 Distributorand arrange for a replacement of the goods. Damaged goods must be returned in the condition received by you with alloriginal packaging, accessories and/or manuals. If they are not returned in same condition sent there may be an additio-nal fee charged.To fi le a claim under this warranty please contact AFN4x4 at +351 256 808 300 or via email at ************ to request aReturned Goods Authorization (RGA) number and instructions for returning the defective component.*OEM - Original Equipment ManufacturerEspanhaCarretera de Moledo 8 36214, Vigo (Pontevedra)T:(0034) 986 378338********************** Austrália19 Flinders Parade North lakesQLD 4509T:(0061) 1300 236 494 ****************.au .auPortugalRua da Madeira, 113Z. Industrial das Travessas 3700-176 S. João da Madeira T:(00351) 256 838 300/7 ************* Costa RicaFort overlanding CR, Alajuela T:(0011) 506 8430 0211************************5 AFN 4x4 PARTNERSOwner Manual | Fiting Instructions Owner Manual u | F it t in g n In st t ru r u ct c t io nsOw w O ne n r Ma a M u nu n al l a n e l w Ow O ne r Ma M a nu n al awww.afn.pt|************|/AFN4x4D O N ’T JU S T S E TT L E F O RT H E S A ME O L D B U LL。

汽车尾部的字母SUV、CRV 、RAV、HRV 等都表示什么意思？TSI涡轮增压(T)+机械增压(S)+燃油缸内直喷(I)，TFSI是涡轮增压(T)+燃油分层喷射燃烧技术(FSI)，可是这个技术引进中国后就因为中国的烂油给简配了，就成了中国特色的“TSI’’。

SUV的全称是Sport Utility Vehicle，即“运动型多用途车”，20世纪80年代起源于美国，是为迎合年轻白领阶层的爱好而在皮卡底盘上发展起来的一种厢体车。

离地间隙较大，在一定的程度上既有轿车的舒适性又有越野车的越野性能。

CRV是本田的一款车，国产的版本叫做东风本田CR-V，取英文City Recreation Vehicle之意，即城市休闲车。

SRV的英文全称是Small Recreation Vehicle，翻译过来的意思是“小型休闲车”，一般指两厢轿车，比如上海通用赛欧SRV。

RAV源于丰田的一款小型运动型车，RAV4。

丰田公司的解释是，Recreational(休闲)、Activity(运动)、Vehicle(车)，缩写就成了RAV，又因为车是四轮驱动，所以又加了个4。

HRV源于上海通用别克凯越HRV轿车，取Healthy(健康)、Recreational(休闲)、Vigorous(活力)之意，和上面的“V”不同，纯粹玩的是一个概念。

MPV的全称是Multi-Purpose Vehicle(或Mini Passenger Van)，即多用途汽车。

它集轿车、旅行车和厢式货车的功能于一身，车内每个坐椅都可调整，并有多种组合的方式。

近年来，MPV趋向于小型化，并出现了所谓的S-MPV，S是小(Small)的意思，车身紧凑，一般为5～7座。

CUV是英文Car-Based Utility Vehicle的缩写，是以轿车底盘为设计平台，融轿车、MPV 和SUV特性为一体的多用途车，也被称为Crossover。

CUV最初于20世纪末起源日本，之后在北美、西欧等地区流行，开始成为崇尚既有轿车驾驶感受和操控性，又有多用途运动车的功能，喜欢SUV的粗犷外观，同时也注重燃油经济性与兼顾良好的通过性的这类汽车用户的最佳选择。

CHAPTER 1: IRIS认证程序1.前言“国际铁路工业标准” (以下简称IRIS) 是由欧洲铁路工业联盟(UNIFE)研究工作组所建立。

国际铁路工业组织期望成为在铁路工业中以安全第一考量的全球性非营利组织。

藉由铁路设备供应商通过认证的标准可加强铁路工业在国际性竞争力。

国际铁路工业组织的目标是在发展及运用全球性系统以使铁路工业的供应商有更明确的指标，如下:●铁路产业中企业管理系统的国际标准，其也与标准●评估过程所需的指导方针●国际铁路工业标准网络数据库及稽核工具书软件此系统是为取得全球认可，及逹成稽核要求，及避免多次稽核所造成高效益成本。

国际铁路工业组织可确保稽核能符合铁路工业的要求(以下统称为”标准”). 稽核记录及稽核结果应该适当存放在资料中心。

国际铁路工业标准组织的决策是取决于国际铁路工业组织委员会。

其也引导国际铁路工业组织管理人(和中心小组人员)来逹成以上所说明的期望及目标。

国际铁路工业组织并不是评鉴稽核评价的过程而是应该辅导及准许验证公司确保发证过程的公信力。

国际铁路工业标准组织赞同验证公司主导稽核活动来辅导铁路工业局(此文章所称之”客户”是为铁路业者).2.验证公司的要件验证公司必需经由国际铁路工业标准组织授权发证。

取得授权发证须符合以下规定:●验证公司申请授权发证前需符合国际标准EN 45012:1998及ISO/IECGuide 62逹3年期以上●根据IAF准则申请的ISO/IEC Guide 62:1996,附件1可以允许铁路工业的合作●验证公司必需是全球性认可的公司●验证公司可展现铁路工业的专业知识及能力●验证公司有经验足够的稽核员3.稽核员的基本要件稽核员必需要有以下的知识: ISO 9001, IRIS 及附件1里其中一项的产业经验。

稽核员对于IRIS标准要有充足的稽核经验，当稽核员第一次申请IRIS标准登入时应举证出相关的稽核背景。

稽核员须为验证公司所认可合格，但不可同时为其他验证公司所雇用。

From The FIA Formula One Race Director To All Teams, All Officials Document 2Date09 April 2015Time 09:012015 C HINESE G RAND P RIXThe FIA Formula One Race DirectorTitle Event NotesDescription Event NotesEnclosed Event Notes 09-04-2015_V1.pdfCharlie Whiting2015C HINESE G RAND P RIXFrom The FIA Formula One Race Director Document 2To Formula One Team Managers Date9 April 2015Time09.00E VENT N OTES9A PRIL 20151) Issues arising from the Malaysian Grand Prix2) Changes to the circuit2.1The run-off area has been changed from gravel to asphalt in the pit entry.2.2The race control CCTV system has been upgraded to high definition cameras and screens. 2.3 A debris fence has been installed in the pit entry to protect marshals.3) Pit lane map3.1Safety Car lines.3.2The location of the pit entry and the pit exit.3.3Designated garage areas.3.4Safety Car position for first lap and rest of race.3.5Blue flag marshal.3.6Safety Car “arrow man”.4) Weighing and weighing platform4.1The weighing platform will be open between the following times, each visit should last nomore than 10 minutes unless no other team is waiting in the pit lane :a) From 09.00 Thursday until 14.30 on Saturday (between 13.00 and 14.30 each visit will berestricted to five minutes).b) From when the cars are returned to the teams after qualifying until 19.30 on Saturday.c) From 09.00 until 13.00 on Sunday.Any team found to be abusing the time limits set out above, which we will be enforced by FIA security personnel and our own CCTV, will not be permitted to use the weighbridge againduring the Event.4.2Please ensure your staff treat all equipment in the FIA garage as if it was their own, theyshould also leave the area clean and tidy and keep their numbers within the garage to aminimum. Again, in the event of any reported abuse the team concerned will not bepermitted to use the weighbridge again during the Event.5) Practice starts5.1Practice starts may only be carried out on the left (in the fast lane) at the pit exit before theend of the pit wall. Drivers must leave adequate room on their right for another driver to pass.5.2During the time that the pit exit is open for reconnaissance laps (13.30-13.45 on Sunday)practice starts should be carried out on the track after leaving the pit lane, but withoutcrossing the dotted white line referred to in 6.3 below. Drivers wishing to carry out a startshould stop on the right in order to allow other cars to pass on their left.During this time any driver passing a car which has stopped to carry out a practice start may cross the white line that is referred to in 6.1 below. Any driver crossing this line must move back to the right of it as quickly as possible.6) Lines, bollards and flags at the pit entry and pit exit6.1In accordance with Chapter 4 (Section 5) of Appendix L to the ISC drivers must keep to theright of the white line at the pit exit when leaving the pits.6.2For safety reasons drivers must keep to the right of the bollard at the pit entry.6.3The dotted white line across the pit exit is the track edge.6.4If there is a yellow flag waved on the driver’s right at the beginning of the pit entry it will bewarning of an incident around the corner of the pit entry. This flag is not intended for drivers staying on the track and competing a lap.7) Light panels7.1 The FIA light panels have been installed in the positions shown on the circuit map. Inaccordance with Appendix H to the ISC the light signals have the same meaning as flag signals.8) DRS8.1DRS will be globally disabled if panels 1, 16, 17, 19 or 20 are displaying yellow.8.2Detection will be automatically disabled if the light panels below are displaying yellow :Zone 1: Panels 13, 14 or 15.Zone 2: Panel 18.8.3If automatic detection is not working , and permission has been given by race control to usemanual detection, DRS should not be used in the relevant zone if panels 13, 14, 15 or 18 are displaying yellow.9) Drivers leaving their pit stop position in the pit lane9.1For safety reasons, no car should be driven from its pit stop position at any time unless :a) It has first been driven into the pit stop position having just entered the pit lane fromthe track, and ;b) It is then driven immediately back onto the track from the pit stop position.10) Fire extinguishers around the circuit10.1 Indicated by small fluorescent orange boards.11) Places to remove cars from the track11.1 Indicated by fluorescent orange panels on the walls or guardrails.12) Support races12.1Teams are asked to keep their barriers no more than five metres from the garages during thesupport race sessions and races.13) Post qualifying parc fermé13.1The cameras should be installed and operated in the same way as 2014.14) Removing cars from the grid14.1Two gates in the pit wall, beside grid positions 5 and 18.15) Car number boards for the starts15.1On the driver's right.16) Post race parc fermé16.1All cars must enter the pit lane and proceed directly to the weighing area.17) Any other business17.1DRS disabling and re-enabling during and after a VSC period.17.2The new track camera system and possible effects on the “follow car” system.Charlie WhitingFIA Formula One Race DirectorV e r s i o n 1 –9 A p r i l 2015PI T L A N E S T A R T S PI T L A N E E N D S SAF ET YCA RLINE2。

Interior Materials and ComponentsA INDEXA IndexB ScopeC ObjectD ReviewE Related DocumentsF RequirementsZ Change HistoryB SCOPEApplicable to all surface materials on the interior of the vehicle with a surface area exceeding 100 cm2 (all colours). Materials and components that may affect the cabin odour are also applicable to this standard. Trim and Final production materials and the specific components identified in sectionF are also required to meet the requirements of this standard.C OBJECTThe purpose of this standard is to ensure that our vehicle interiors meet the continuing demand for reduced Volatile Organic Compound (VOC) and hazardous material emissions.D REVIEWThis document is to be reviewed at least every three years from the date of the last review or update.E RELATED DOCUMENTSTPJLR.52.458 STJLR.99.9999SAE J1756 TÜV TOXPROOF Criteria CatalogueTPJLR.52.104 VDA 277TPJLR.52.107 TPJLR.52.109Interior Materials and ComponentsF REQUIREMENTS1 All materials and components must comply with Jaguar Land Rover's restricted substancemanagement requirements, STJLR.99.9999.2 Standard Materials Requirements2.1 Applicable to materials such as surface materials (leathers, PVC’s, painted plastics), NVHmaterials, carpets, seat foams, SMC, laminar materials (veneers, parcel trays, load floor,headlining).2.2 All colours are required to be tested.2.3 8 off A5 samples for hard trim materials, or 0.5 m2 samples for soft trim materials, shall berequired for analysing materials to section F2.2.4 Hard trim samples shall be provided in plaque form (in certain cases, where the componentmeets the dimensional requirements of the test apparatus, components may be analysed).2.5 Materials shall be analysed before <VP> gateway.2.6 Components shall be tested before <FEC> gateway2.7 It is the responsibility of the Component Engineer to provide samples 4 weeks before therelevant deadlines.Interior Materials and ComponentsTable 1 - Requirements for interior trim materials(1) Substances marked as 'Information Only' may be subject to restrictions in future versions of this standard.(2) 50 µgm-2hr-1 styrene limit for tailgate and roof materials only.(3) 150 µgm-2hr-1 styrene limit for all other interior materials.Interior Materials and ComponentsTable 2 – Supplementary requirements for specific materials(1) If the fogging value according to SAE J1756 exceeds 4 mg a photometric measurement must be done. The photometric value (3 hrs at 100 °C ± 2 °C, 21 °C ± 2 °C cooling plates. 1 hr and 16 hrs post test conditioning) must not be lower than 70.(2) 16 hrs at 100 °C ± 2 °C. 21 °C ± 2 °C cooling plates. 4 hrs post-test conditioning.(3) VOC result to exclude butane emissions.(4) VOC result to exclude ethanol and isopentane emissions.Interior Materials and Components3 Emission Requirements for specific parts and assemblies3.1 The following parts are required to meet the requirements in Table 3:Topper pad, door casings, pillar trims.3.2 Only 1 colour requires testing.3.3 Components shall be tested before <FEC> gateway3.4 It is the responsibility of the Component Engineer to provide samples 4 weeks before therelevant deadlines.Table 3 – Requirements for selected components(1) Substances marked as 'Information only' will be subject to restrictions in future versions of this standard.Interior Materials and Components Z CHANGE HISTORY。

F G H J K代表的年份
代表车架号生产日期的是车架号第十位的字符，代表年份的字符为1、2、3、4、5、6、7、8、9、A、B、C、D、E、F、G、H、J、K、L、M、N、P、R、S、T、V、W、X、Y这30个字符，30年一个轮回周期，从2001年起为1。

比如说，车架号第十位如果是F G H J K的话，对应年份就是2015、2016、2017、2018、2019。

代表年份的英文字母“I”、“O”、“Q”、“Z”“U”在车架号上都不被使用，是为了避免与1、0、2、V混淆。

车辆识别号码（Vehicle Identification Number,或车架号码），简称VIN，是一组由十七个英数组成，用于汽车上的一组独一无二的号码，可以识别汽车的生产商、引擎、底盘序号及其他性能等资料。

VIN中的每个字符都具有特定的含义，而且整个VIN分为多个部分。

第一位标识原产国/地区，第二位分标识车辆的制造商，接下来的三位对所有制造商都是一致的，第九位始终为校验位，第十位是车型年码（每年都有一个代码字符），地第十一位是工厂代码（表示车辆的组装工厂），最后六位是产品序列号。

vctf电缆标准的相关信息：
* VCTF电缆是电梯电缆，也被称为电梯电气导轨。

* VCTF电缆标准是电梯电缆的标准，涵盖了电缆的结构、材料、尺寸、电气性能和机械性能等方面的要求。

具体内容如下：
1. VCTF电梯电缆型号：包括SVV、YTTW、ZR-SVV、NH-SVV等型号。

2. 结构：外护套和内部的芯线之间由聚氯乙烯绝缘，核心的导体绞合构成。

3. 尺寸要求：包括电缆最小厚度、最小外径、绝缘线股的线规、导体最小直径等要求。

4. 电气性能要求：包括绝缘电阻、工作电容、耐电压强度、电气稳定性等要求。

5. 机械性能要求：包括抗拉强度、弯曲半径、耐环境应力开裂等要求。

6. 环境条件要求：包括温度和湿度、腐蚀环境、污染等级等方面的要求。

此外，还规定了电缆和设备的质量等级，如电缆不得有损伤、扭曲、变形等现象，外护套应光滑、色泽均匀，护套断裂伸长率应大于500%，电缆应具备良好的阻燃性，符合有关环保规定等。

同时，还规定了有关试验方法，以确保电缆和设备的各项性能指标均符合标准要求。

总之，VCTF电缆标准对电梯电缆的结构、材料、尺寸、电气性能和机械性能等方面提出了具体要求，以确保电梯的安全运行。