i709X Data Sheet v2.0(2)
NVIDIA DOCA Tools MLNX-15-060529 _v2.0.2 使用说明书
OverviewTable of ContentsChapter 1. Introduction (1)Chapter 2. DOCA Tools (2)2.1. Comm Channel Admin Tool (2)2.2. DPA HART Management Tool (2)2.3. DPACC Compiler (2)2.4. DPI Compiler (2)2.5. FlexIO Build (3)2.6. RXP Compiler (3)2.7. RXPBench (3)2.8. Socket Relay (3)Chapter 1.IntroductionDOCA tools are a set of executables/scripts that are needed to produce inputs to some of the DOCA libraries and applications.All tools are installed with DOCA, as part of the doca-tools package, and can either be directly accessed from the terminal or can be found at /opt/mellanox/doca/tools. Refer to NVIDIA DOCA Installation Guide for Linux for more information.List of tools for both the host and the NVIDIA® BlueField® DPU:‣DPI compiler‣RXP compiler (rxpc)‣RXPBenchChapter 2.DOCA Tools2.1. Comm Channel Admin ToolCLI name: doca_comm_channel_admin_toolThe Comm Channel Admin Tool is used to monitor Comm Channel services and connections on both the DPU and the host.2.2. DPA HART Management ToolCLI name: dpahartmgmtThe DPA HART management tool allows users to manage the DPA's HARTs which are the basic resource of the DPA. The tool enables the resource control of HARTs to optimize the usage of computation resources of the DPA. Using this tool, users may query, create, and destroy HART partitions and groups, thus ensuring proper HART allocation between devices.2.3. DPACC CompilerCLI name: dpaccDPACC is a high-level compiler for the DPA processor. It compiles code targeted for the DPA processor into an executable and generates a DPA program.The DPA program is a host library with interfaces encapsulating the DPA executable. This DPA program can be linked with the host application to generate a host executable where the DPA code is invoked through the FlexIO runtime API.2.4. DPI CompilerCLI name: doca_dpi_compilerThis tool is used to create one of the necessary inputs to the DOCA DPI library.DOCA ToolsThe DPI compiler is used to compile a signature file which is loaded into the BlueField RegEx HW accelerator using a dedicated API (doca_dpi_load_signatures(cdo_file)). The output for the DPI compiler is a JSON-based CDO file.2.5. FlexIO BuildCLI name: build_flexio_deviceThe FlexIO Build tool is used to build and compile FlexIO device code into a static library. It is designed to generate a host library that encapsulating DPA execution. This tool relies on DPACC.2.6. RXP CompilerCLI name: rxpcThis tool is used to generate a ROF file that can be used by a customer application to program the NVIDIA® RXP® accelerator rules memories.The RXP compiler is used to compile RegExes into RXP Object Format (ROF) to be executed on the RXP accelerator.The DOCA RegEx library can be used to load the binary ROF file into the RXP.2.7. RXPBenchCLI name: rxpbenchRXPBench is a tool that allows performance comparison between the NVIDIA® RXP®hardware RegEx acceleration engine, found in the NVIDIA® BlueField® DPU, and the Intel®Hyperscan software library. It provides a comprehensive set of options and facilitates ingress of data from live network ports or previously recorded PCAP files.It is designed to provide a real-world comparison of these technologies and present the results customers could expect to receive after implementing either technology in their products.2.8. Socket RelayCLI name: doca_socket_relayDOCA Socket Relay allows Unix Domain Socket (AF_UNIX family) server applications to be offloaded to the DPU while communication between the two sides is proxied by DOCA Comm Channel.NoticeThis document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. NVIDIA Corporation nor any of its direct or indirect subsidiaries and affiliates (collectively: “NVIDIA”) make no representations or warranties, expressed or implied, as to the accuracy or completeness of the information contained in this document and assume no responsibility for any errors contained herein. NVIDIA shall have no liability for the consequences or use of such information or for any infringement of patents or other rights of third parties that may result from its use. This document is not a commitment to develop, release, or deliver any Material (defined below), code, or functionality.NVIDIA reserves the right to make corrections, modifications, enhancements, improvements, and any other changes to this document, at any time without notice.Customer should obtain the latest relevant information before placing orders and should verify that such information is current and complete.NVIDIA products are sold subject to the NVIDIA standard terms and conditions of sale supplied at the time of order acknowledgement, unless otherwise agreed in an individual sales agreement signed by authorized representatives of NVIDIA and customer (“Terms of Sale”). NVIDIA hereby expressly objects to applying any customer general terms and conditions with regards to the purchase of the NVIDIA product referenced in this document. No contractual obligations are formed either directly or indirectly by this document.NVIDIA products are not designed, authorized, or warranted to be suitable for use in medical, military, aircraft, space, or life support equipment, nor in applications where failure or malfunction of the NVIDIA product can reasonably be expected to result in personal injury, death, or property or environmental damage. NVIDIA accepts no liability for inclusion and/or use of NVIDIA products in such equipment or applications and therefore such inclusion and/or use is at customer’s own risk.NVIDIA makes no representation or warranty that products based on this document will be suitable for any specified use. Testing of all parameters of each product is not necessarily performed by NVIDIA. It is customer’s sole responsibility to evaluate and determine the applicability of any information contained in this document, ensure the product is suitable and fit for the application planned by customer, and perform the necessary testing for the application in order to avoid a default of the application or the product. Weaknesses in customer’s product designs may affect the quality and reliability of the NVIDIA product and may result in additional or different conditions and/or requirements beyond those contained in this document. NVIDIA accepts no liability related to any default, damage, costs, or problem which may be based on or attributable to: (i) the use of the NVIDIA product in any manner that is contrary to this document or (ii) customer product designs.No license, either expressed or implied, is granted under any NVIDIA patent right, copyright, or other NVIDIA intellectual property right under this document. Information published by NVIDIA regarding third-party products or services does not constitute a license from NVIDIA to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property rights of the third party, or a license from NVIDIA under the patents or other intellectual property rights of NVIDIA.Reproduction of information in this document is permissible only if approved in advance by NVIDIA in writing, reproduced without alteration and in full compliance with all applicable export laws and regulations, and accompanied by all associated conditions, limitations, and notices.THIS DOCUMENT AND ALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, “MATERIALS”) ARE BEING PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL NVIDIA BE LIABLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF ANY USE OF THIS DOCUMENT, EVEN IF NVIDIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Notwithstanding any damages that customer might incur for any reason whatsoever, NVIDIA’s aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the Terms of Sale for the product.TrademarksNVIDIA, the NVIDIA logo, and Mellanox are trademarks and/or registered trademarks of Mellanox Technologies Ltd. and/or NVIDIA Corporation in the U.S. and in other countries. The registered trademark Linux® is used pursuant to a sublicense from the Linux Foundation, the exclusive licensee of Linus Torvalds, owner of the mark on a world¬wide basis. Other company and product names may be trademarks of the respective companies with which they are associated.Copyright© 2023 NVIDIA Corporation & affiliates. All rights reserved.NVIDIA Corporation | 2788 San Tomas Expressway, Santa Clara, CA 95051。
Fluke 709H HART Communication Loop Calibrator说明书
Technical Data Hart communications The 709H adds HART communica-tions and supports a select set of the HART universal and common practice commands. This makes the 709H unique as both an affordable, compact loop calibrator and powerful HART communica-tion troubleshooting tool.In the communicator mode the user will be able to read basic device information, perform diagnostic tests, and trim the mA output on most HART enabled transmitters. In the past, this could only be done with a dedicated communicator, a high-end mul-tifunction calibrator, or a laptop computer with HART modem. Fluke 709H will allow virtually any technician to service and sup-port HART devices.Saving time, getting answersIn addition, the 709H offers:•Logging of HART data in the field. Once recorded by the 709H in the field, the 709H/TRACK software can upload the HART configuration of up to (20) HART devices in your plant and output data in either (.csv) or (.txt) format.•Data logged mA loop mea-surements and HART data can be recorded from a particular transmitter for troubleshooting and loop tuning. The data log feature offers selectable cap-ture with recording intervals of 1 to 60 seconds and a log-ging capacity of 9800 records or 99 individual sessions. Each data sample contains the 709H mA measurement, all four process variables, and the Fluke 709/709H Precision Current Loop Calibrator with HART communicationProduct highlights•Best-in-class accuracy at 0.01% reading•Compact rugged design•Intuitive user interface with Quick-Set knob for fast setup, easy use •24 V DC loop power with mA measure mode (-25% to 125%)•Resolution of 1 µA on mA ranges and 1 mV on voltages ranges •Built in selectable 250 Ω resistor for HART communications •Simple two wire connection for all measurements•Auto shutdown to conserve battery life•Variable step and ramp time in seconds•Valve test (source and simulate defined mA values with % keys SpecificationsOrdering informationFLUKE-709Precision Loop CalibratorFLUKE-709H Precision HART Loop Calibrator Fluke Corporation PO Box 9090, Everett, WA 98206 U.S.A.Fluke Europe B.V. PO Box 1186, 5602 BD Eindhoven, The NetherlandsFluke. The Most Trusted Tools in the World.For more information call: In the U.S.A. (800) 443-5853 or Fax (425) 446-5116 In Europe/M-East/Africa +31 (0) 40 2675 200 or Fax +31 (0) 40 2675 222 In Canada (800)-36-FLUKE or Fax (905) 890-6866 From other countries +1 (425) 446-5500 or Fax +1 (425) 446-5116 Web access: ©2012 Fluke Corporation. Specifications subject to change without notice. Printed in U.S.A. 12/2012 4287255A_ENModification of this document is not permitted without written permission from Fluke Corporation.HART communicationThe Fluke 709H offers a built-in HART modem for communication capability to perform the following commands:•Read message•Read tag, descriptor, calibration date•Read sensor PV information•Read PV output information•Read long tag•Write PV ranges (upper and lower)•Enter/exit fixed current mode•Set zero offset•Trim DAC zero (mA output 4 mA)•Trim DAC gain (mA output 20 mA)•The Fluke 709H also offers ability to store up to twenty HART device configuration files for uploading via 709H/TRACK software. via the 709H/TRACK software. Configurations can be stored as .csv or .txt files. This allows the end user to document plant HART easily.Configurations can be stored as .csv or .txt files. This feature gives the technician direct access to key device parameters, allowing better troubleshooting, calibrating and maintaining of plant assets. Standard equipment•Two AC72 alligator clips (709)•TL75 test leads (709)•Extended tooth alligator clip set (709H)•75X-8014 stackable lead set (709H)•TP220 test probes (709H)•AC280 SureGrip™ hook clips (709H) •HART cable (709H only) •Soft case•Six AAA batteries (installed)•709/709H Product manual CD-ROM•709/709H Quick reference guide•709/709H Safety informationOptional software •709H/TRACK software/cable。
USB接口以太网控制器IC 9700 datasheet
深圳市和芯润德科技9700说明书USB接口以太网控制电路概述9700是一个高集成度、低功耗、单芯片USB接口以太网控制电路。
9700内部集成USB收发器、以太网PHY 模块、以太网MAC模块、内存控制模块。
9700完全兼容IEEE802.3u协议，并支持IEEE 802.3x流量控制协议。
9700支持USB接口以太网适配器和CD-ROM复合设备，通过外接SPI Flash可实现USB接口以太网适配器自带驱动程序功能。
外接SPI Flash内也可存放除驱动程序之外的其他应用功能软件程序。
应用范围●USB接口以太网适配器●USB接口以太网适配器和CD-ROM复合设备主要特点●支持USB1.1、USB2.0 全速模式●支持USB挂起模式●支持USB标准命令●支持用户自定义命令●支持USB接口以太网适配器和CD-ROM复合设备功能●支持外接最大16M Byte的SPI Flash●支持自动从EEPROM中加载ID用其它信息●支持93C46/56/66、24C系列的EEPROM●兼容IEEE802.3系列协议●兼容IEEE802.3x流量控制协议●支持低功耗电源管理● 3.3V单电源供电，内部集成1.8V LDO●采用小型LQFP32L-07x07、SSOP24L封装内部框图深圳市和芯润德科技9700说明书管脚排列图R X PG N DR E FO S C OO S C IV C C 33G N DG N DRXN GND VCC18VO18GND VCC33NC VCC33VCC33GPIO5TEST GPIO6DM DP TXP TXNG N DV C C 33V C C 18G P I O 0G P I O 1G P I O 2G P I O 3G P I O 4GPIO5GND DP DM GPIO2GPIO1VCC18VCC33GND GND VCC18VO18VCC33VCC33GNDRXN RXP XTALOREF GND XTALI VCC33TXN TXP深圳市和芯润德科技9700说明书管脚定义I=输入, O=输出, I/O=输入/输出, I/PU=输入带上拉, P=电源注1 ：SSOP24L封装只支持外接24Cxx系列EEPROM。
Fluke 709、709H 中文使用说明书
i
709/709H
用户手册
自动斜坡时间 ............................................................................................................ 自动步进时间 ............................................................................................................ 步进和斜坡操作 .................................................................................................... 自动步进和斜坡 .................................................................................................... 电子管测试 ................................................................................................................ HART 250Ω 电阻器 ................................................................................................... mA 跨度 .................................................................................................................... 对比度 ....................................................................................................................... Auto Shutdown Time（自动关机时间） .................................................................... HART Write Enable（启用 HART 写操作） .............................................................. HART 装置通信功能 ...................................................................................................... HART 连接 ................................................................................................................ 位于电路之中，外部回路电源............................................................................... 位于电路之中，本产品回路电源 ........................................................................... 位于电路之间，仅限通信器 .................................................................................. 通信设置和选择 ......................................................................................................... 模式 ...................................................................................................................... 250Ω 电阻器......................................................................................................... HART 连接 ........................................................................................................... 轮询回路 ............................................................................................................... 标签选择 ............................................................................................................... 数据采集 ............................................................................................................... 从回路中断开........................................................................................................ Function Select Menu（功能选择菜单） ................................................................... 装置设置和数据 ......................................................................................................... 写入 LRV 和 URV 数值 .................................................................................................. 写入 LRV ................................................................................................................... 写入 URV .................................................................................................................. 微调、设置及归零菜单 ................................................................................................... 17 17 18 18 19 20 20 21 21 22 23 23 24 25 26 27 28 28 29 29 30 30 31 31 32 33 33 34 34
RBK40 全家型 AC2200 三带 WiFi 系统说明书
Data SheetRBK40Whole Home AC2200 Tri-band WiFi SystemOverviewThis Orbi WiFi System comes with an Orbi WiFi Router and Satellite that deliver unparalleled WiFi coverage. It covers homes up to 4,000 square feet with strong WiFi signals. Innovative Tri-band WiFi helps maximize the Internet speeds available in your home.Enjoy better WiFi. Everywhere.FeaturesSingle Network Name.One WiFi name and seamless roaming for your whole home to enjoy.Max Internet Speeds.Innovative Tri-band WiFi helps deliver fast Internet speeds even as more devices connect.Your Home. Covered.This kit of two covers up to a 4,000 sq ft † home with high-performance AC2200 WiFi.Simple & Secure.Use the Orbi app or a web browser to create secure whole home WiFi in minutes. With no accounts to set up.Data SheetRBK40Whole Home AC2200 Tri-band WiFi SystemHouse DiagramD E D I CA T E DT R I-B AN DC O N N EC T I ONINTERNETOrbi SatelliteOrbi Router4,000 Square Feet of Orbi WiFi CoverageDedicated Tri-band Connection ensures devices connect directly to maximum Internet speeds1Internet plan and devices that support these speeds are required.Simple setup from your smartphone or tablet.Use the Orbi app to set up and manage your network. To find the app, scan one of the following QR codes or search for NETGEAR Orbi in the Apple App Store or Google Play Store.Data SheetRBK40 Whole Home AC2200 Tri-band WiFi SystemOrbi Router (RBR40)Sync buttonPower buttonPlugs intoexisting modemPlugs into Ethernet-enabled devicesSync buttonPower buttonPlugs into Ethernet-enabled devicesOrbi Satellite (RBS40)Data SheetRBK40Whole Home AC2200 Tri-band WiFi SystemTechnical Specifications• O rbi AC2200 Router & AC2200 Satellite (866+866+400Mbps)†• Simultaneous Tri-band WiFi- R adio 1: IEEE ® 802.11b/g/n 2.4GHz–256QAM support - R adio 2: IEEE ® 802.11a/n/ac 5GHz–256QAM support - R adio 3: IEEE ® 802.11a/n/ac 5GHz–256QAM support • Dedicated Backhaul Technology• F our (4) high-performance antennas with high-power amplifiers • I mplicit/Explicit Beamforming for 2.4 & 5GHz bands (866+866+400Mbps)†• M U-MIMO capable for simultaneous data streaming on multiple devices • F our (4) 10/100/1000Mbps Gigabit Ethernet ports - O rbi Router (RBR40): 1 WAN & 3 LAN - O rbi Satellite (RBS40): 4 LAN • S ecurity- W PA/WPA2-PSK support- G uest WiFi Network is easy to setup separate& secure Internet access for guestsThis product comes with a limited warranty that is valid only if purchased from a NETGEAR authorized reseller.* 90-day complimentary technical support following purchase from a NETGEAR authorized reseller.† M aximum wireless signal range derived from IEEE standard 802.11 specifications. Actual data throughput and data over distance will vary. Network conditions and environmental factors, including volume of network traffic, building material and construction, and network overhead, result in lower actual data throughput rate and wireless coverage.1Internet plan and devices that support these speeds are required.For indoor use only.For regulatory compliance information, visit /about/regulatoryNETGEAR, the NETGEAR Logo, and Orbi are trademarks and/or registered trademarks of NETGEAR, Inc. Any other trademarks mentioned herein are for reference purposes only. ©2017 NETGEAR, Inc.NETGEAR, Inc. 350 E. Plumeria Drive, San Jose, CA 95134-1911 USA, /supportD-RBK40-2Physical Specifications• Orbi Router (RBR40)- D imensions: 6.4 x 3.1 x 8.0 in - W eight: 1.65 lb • Orbi Satellite (RBS40)- D imensions: 6.4 x 3.1 x 8.0 in - W eight: 1.65 lbWhat’s In the Box?• One (1) Orbi Router (RBR40)• One (1) Orbi Satellite (RBS40)• One (1) 2m Ethernet cable • Two (2) 12V/2.5A power adapters • Quick start guideWhat Do I Need for Orbi to Work?• High-speed Internet connection • Connect to existing modem or gateway。
NVIDIA DOCA DMA Copy应用指南说明书
Application GuideTable of ContentsChapter 1. Introduction (1)Chapter 2. System Design (2)Chapter 3. Application Architecture (3)Chapter 4. DOCA Libraries (5)Chapter 5. Configuration Flow (6)Chapter 6. Dependencies (8)Chapter 7. Running the Application (9)Chapter 8. Arg Parser DOCA Flags (11)Chapter 9. References (13)Chapter 1.IntroductionDOCA DMA (direct memory access) Copy application transfers files (data path) up to 1MB in size between the DPU and the x86 host using the DOCA DMA library which provides an API to copy data between DOCA buffers using hardware acceleration, supporting both local and remote memory.DOCA DMA allows complex memory copy operations to be easily executed in an optimized, hardware-accelerated manner.Chapter 2.System DesignDOCA DMA Copy is designed to run on both the instances of the BlueField-2 DPU andx86 host. The DPU application must be the first to spawn as it opens the Comm Channel (CC) service between the two sides on which all the necessary DMA library configuration files (control path) are transferred.Chapter 3.Application ArchitectureDOCA DMA Copy runs on top of DOCA DMA to read/write directly from the host's memory without any user/kernel space context switches, allowing for a fast memory copy.1.The two sides initiate a short negotiation in which the file size and location aredetermined.Application Architecture2.Host side creates the export descriptor with doca_mmap_export() and sends itwith the local buffer address and length on the Comm Channel to the DPU sideapplication.3.DPU side application uses the received export descriptor to create a remote memorymap locally with doca_mmap_create_from_export() and the host buffer information to create a remote DOCA buffer. From this point on, the DPU side application has all the needed memory information and the DMA copy will take place.Chapter 4.DOCA LibrariesThis application leverages following DOCA libraries:‣DOCA Comm Channel‣DOCA DMA Programming GuideChapter 5.Configuration Flow1.Parse application argument.a).Initialize arg parser resources and register DOCA general parameters.doca_argp_init();b).Register application parameters.register_dma_copy_params();c).Parse app flags.doca_argp_start();2.Initialize DOCA App Shield lib context.init_cc();a).Create Comm Channel endpoint.b).Parse user PCIe address for Comm Channel device.c).Open Comm Channel DOCA device.d).Parse user PCIe address for Comm Channel device representor (on DPU side).e).Open Comm Channel DOCA device representor (on DPU side).f).Set Comm Channel endpoint properties.3.Open the DOCA hardware device from which the copy would be made.open_dma_device();a).Parse the PCIe address provided by the user.b).Create a list of all available DOCA devices.c).Find the appropriate DOCA device according to specific properties.d).Open the device.4.Create all required DOCA core objects.create_core_objects();5.Initiate DOCA core objects.init_core_objects();6.Start host/DPU DMA copy.a).Host-side application:host_start_dma_copy();i.Start negotiation with the DPU side application for the location and size of thefile.ii.Allocate memory for the DMA buffer.Configuration Flowiii.Export the memory map and send the output (export descriptor) to the DPU side application.iv.Send the host local buffer memory address and length on the Comm Channel to the DPU side application.v.Wait for the DPU to notify that DMA Copy has ended.vi.Close all memory objects.vii.Clean resources.b).DPU-side application:dpu_start_dma_copy();i.Start negotiation with the host side application for file location and size.ii.Allocate memory for the DMA buffer.iii.Receive the export descriptor on the Comm Channel.iv.Create the DOCA memory map for the remote buffer on the host.v.Receive the host buffer information on the Comm Channel.vi.Create two DOCA buffers, one for the remote (host) buffer and one for the local buffer.vii.Submit the DMA job into the work queue.viii.Send a host message to notify that DMA copy ended.ix.Clean resources.7.Destroy Comm Channel.destroy_cc();8.Destroy DOCA core objects.destroy_core_objects();9.Arg parser destroy.doca_argp_destroy();Chapter 6.Dependencies The minimum required firmware version is 24.32.1010.Chapter 7.Running the Application1.Refer to the following documents:‣NVIDIA DOCA Installation Guide for Linux for details on how to install BlueField-related software.‣NVIDIA DOCA Troubleshooting Guide for any issue you may encounter with the installation, compilation, or execution of DOCA applications.‣NVIDIA DOCA Applications Overview for additional compilation instructions and development tips of DOCA applications.2.The DMA Copy example binary is located under /opt/mellanox/doca/applications/ dma_copy/bin/doca_dma_copy. To build all the applications together, run:cd /opt/mellanox/doca/applications/meson buildninja -C build3.To build only the DMA Copy application:a).Edit the following flags in /opt/mellanox/doca/applications/meson_options.txt:‣Set enable_all_applications to false‣Set enable_dma_copy to trueb).Run the commands in step 2.Note: doca_dma_copy is created under ./build/dma_copy/src/.Application usage:Usage: doca_dma_copy [DOCA Flags] [Program Flags]DOCA Flags:-h, --help Print a help synopsis-v, --version Print program version information-l, --log-level Set the log level for the program<CRITICAL=20, ERROR=30, WARNING=40, INFO=50, DEBUG=60>Program Flags:-f, --file Full path to file to be copied/created aftera successful DMA copy-p, --pci-addr DOCA Comm Channel device PCI address-r, --rep-pci DOCA Comm Channel device representor PCI address (needed only on DPU)Running the Application 4.Running the application on BlueField, CLI example:/opt/mellanox/doca/applications/dma_copy/bin/doca_dma_copy -p 03:00.1 -r b1:00.1 -f /tmp/file_to_read.txt5.Running the application on the host, CLI example:/opt/mellanox/doca/applications/dma_copy/bin/doca_dma_copy -p b1:00.1 -f /tmp/ file_to_create.txtNote: Refer to section "Running DOCA Application on Host" in NVIDIA DOCA VirtualFunctions User Guide.6.To run doca_dma_copy using a JSON file:doca_dma_copy --json [json_file]For example:cd /opt/mellanox/doca/applications/dma_copy/bin./doca_dma_copy --json /root/dma_copy_params.jsonChapter 8.Arg Parser DOCA Flags Refer to NVIDIA DOCA Arg Parser Programming Guide for more information.Arg Parser DOCA FlagsChapter 9.References ‣/opt/mellanox/doca/applications/dma_copy/src/NoticeThis document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. NVIDIA Corporation nor any of its direct or indirect subsidiaries and affiliates (collectively: “NVIDIA”) make no representations or warranties, expressed or implied, as to the accuracy or completeness of the information contained in this document and assume no responsibility for any errors contained herein. NVIDIA shall have no liability for the consequences or use of such information or for any infringement of patents or other rights of third parties that may result from its use. This document is not a commitment to develop, release, or deliver any Material (defined below), code, or functionality.NVIDIA reserves the right to make corrections, modifications, enhancements, improvements, and any other changes to this document, at any time without notice.Customer should obtain the latest relevant information before placing orders and should verify that such information is current and complete.NVIDIA products are sold subject to the NVIDIA standard terms and conditions of sale supplied at the time of order acknowledgement, unless otherwise agreed in an individual sales agreement signed by authorized representatives of NVIDIA and customer (“Terms of Sale”). NVIDIA hereby expressly objects to applying any customer general terms and conditions with regards to the purchase of the NVIDIA product referenced in this document. No contractual obligations are formed either directly or indirectly by this document.NVIDIA products are not designed, authorized, or warranted to be suitable for use in medical, military, aircraft, space, or life support equipment, nor in applications where failure or malfunction of the NVIDIA product can reasonably be expected to result in personal injury, death, or property or environmental damage. NVIDIA accepts no liability for inclusion and/or use of NVIDIA products in such equipment or applications and therefore such inclusion and/or use is at customer’s own risk.NVIDIA makes no representation or warranty that products based on this document will be suitable for any specified use. Testing of all parameters of each product is not necessarily performed by NVIDIA. It is customer’s sole responsibility to evaluate and determine the applicability of any information contained in this document, ensure the product is suitable and fit for the application planned by customer, and perform the necessary testing for the application in order to avoid a default of the application or the product. Weaknesses in customer’s product designs may affect the quality and reliability of the NVIDIA product and may result in additional or different conditions and/or requirements beyond those contained in this document. NVIDIA accepts no liability related to any default, damage, costs, or problem which may be based on or attributable to: (i) the use of the NVIDIA product in any manner that is contrary to this document or (ii) customer product designs.No license, either expressed or implied, is granted under any NVIDIA patent right, copyright, or other NVIDIA intellectual property right under this document. Information published by NVIDIA regarding third-party products or services does not constitute a license from NVIDIA to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property rights of the third party, or a license from NVIDIA under the patents or other intellectual property rights of NVIDIA.Reproduction of information in this document is permissible only if approved in advance by NVIDIA in writing, reproduced without alteration and in full compliance with all applicable export laws and regulations, and accompanied by all associated conditions, limitations, and notices.THIS DOCUMENT AND ALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, “MATERIALS”) ARE BEING PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL NVIDIA BE LIABLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF ANY USE OF THIS DOCUMENT, EVEN IF NVIDIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Notwithstanding any damages that customer might incur for any reason whatsoever, NVIDIA’s aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the Terms of Sale for the product.TrademarksNVIDIA, the NVIDIA logo, and Mellanox are trademarks and/or registered trademarks of Mellanox Technologies Ltd. and/or NVIDIA Corporation in the U.S. and in other countries. The registered trademark Linux® is used pursuant to a sublicense from the Linux Foundation, the exclusive licensee of Linus Torvalds, owner of the mark on a world¬wide basis. Other company and product names may be trademarks of the respective companies with which they are associated.Copyright© 2023 NVIDIA Corporation & affiliates. All rights reserved.NVIDIA Corporation | 2788 San Tomas Expressway, Santa Clara, CA 95051。
M7 MIMIC模式指南说明书
M7 MIMIC Mode By John Sonnenberg Raveon Technologies Corporation OverviewA MIMIC mode allows two or more M7s to mimic each other ’s digital I/O. The M7 radio must have software version C13 or higher to work in the MIMIC mode. When in the MIMIC mode, the M7 will periodically transmit its digital status. The M7 will also continue to operate as a radio modem, sending/receiving data using pins 2&3 of the DB9, but the other I/O pins of the DB9 will be used for digital input/output.Normally, the Serial I/O connector operates like an RS232 serial interface. If the MIMIC mode is enabled, the operation of the radio is modified to transmit the digital status of the INPUT0 and INPUT1 pins across the radio link, and output their status on the OUT0 and OUT1 pins. There are two aspects to the MIMIC mode:1. The transmitter that sends the status of its digital inputs. This is enabled with the MIMIC X Ycommand. 2. The unit that receives the over-the-air MIMIC message, and sets its digital outputs to match the inputs of the sending station. This function is enabled with the ATIO 1command. ATIO 1 configures the DB9 serial port to operate with RS232 signal levels, and use the digital control lines for digital I/O instead of RS232 flow control. ATIO 0 turns off MIMIC reception ability, and the digital I/O pins will operate as flow control signals.The goal of the MIMIC mode is quite simple: Flip a switch at one location, and have something at another location turn on or off.Technical BriefAN161 Rev A2DB9 Connector Pin-OutThe RS232 9-pin serial I/O connector on the M7 radio is a female 9-pin D-subminiature connector having the following pins configuration. It is pinned out so that it may be plugged-pin COM port.directly into a computer or a PC’s 9Note: RS-232 signals use positive and negative voltages to represent digital 1s and 0s. A positive voltage is a 0, and a negative voltage is a digital 1.The Raveon M7 data radio modem uses a special RS232 driver/receiver IC chip to condition and protect all of the data pins on the DB9 RS232 port. The chip used is an ICL3238. Refer to the datasheet on this chip for information about its capabilities, voltages, and thresholds. Its data sheet is available here: /products/deviceinfo.asp?pn=ICL3238. Configuring an M7 for MIMIC modeMIMIC transmissions are enabled with the MIMIC X Y command. MIMIC 0 disables MIMIC mode and puts the unit in standard radio modem operation mode. MIMIC X Y with X and Y being any positive number will enable the MIMIC feature. The MIMIC X Y command sets the unit to transmit a MIMIC over-the-air message every X seconds when INPUT0 is low, and to every Y seconds when INPUT0 is high.MIMIC Command settingsIf digital input INPUT0 is low, every X seconds, the M7 will automatically transmit the digital status of both the the INPUT0 and INPUT1 pins. If INPUT0 is high, every Y seconds, the M7 will automatically transmit the digital status of the INPUT0 and INPUT1 pins. For example, MIMIC 2 60 configures the radio to send the state of INPUT0 and INPUT1 pins every 2 seconds if INPUT0 is low, and every minute if INPUT0 is high.Radio addressing operates as it does in the standard mode. When a unit receives a MIMIC transmission intended for its ID, it will set its OUT0 and OUT1 pins as determined by the sending stations INPUT 0 and INPUT1.When the unit is in the Command mode, MIIC transmissions will not take place. The command mode is entered by sending +++ into the serial port. See the M7 Technical Manual for information on how to configure the M7 using the built-in commands.The MIMIC transmissions are the same over-the-air format as a standard data transmission from an M7 radio modem, except they contain no user-data, only digital I/O information. AnM7 radio modem configured as a repeater will repeat the MIMIC messages.Failsafe SettingsTo ensure failsafe operation, a FAILSAFE A B command sets the minimum message interval, and the default digital output state if an over-the-air MIMIC message is not received within the failsafe period. A is the minimum period, and B is the ASCII hex value of the digital outputs if the failsafe interval passes and no MIMIC messages are receive. B is also the power-on default value of the digital outputs.For example, FAILSAFE 60 1 configures the unit to require a MIMIC message at least every minute. If one is not received within 60 seconds, OUT0 will go high (open drain), and OUT1 will go low (below ground).It is recommended that the A value for the FAILSAFE command be about 2.5 times longer than the largest of the X and Y values of the MIMIC command. This allows for one MIMIC message to be missed. For example if MIMIC transmissions are set to MIMIC 2 60, a reasonable FAILSAFE A B setting would be a value of 150 for A. This will allow one MIMIC message to be missed and the FAILSAFE value not kick in. If more than two MIMIC messages did not get received, after 150 seconds, the M7 would revert to the failsafe values.To disable failsafe operation, issue the FAILSAFE 0 command. This disables failsafe operation. In this case, the outputs will stay latched at the last condition that was received over the air. The power-on condition of the OUT0 and OUT1 are indeterminate.You will need to set the MIMIC and FAILSAFE values to match the needs of your system. Configuring A One-Way MIMIC LinkTo setup a MIMIC radio link from one point to another, follow these steps:On the transmitting M71. Connect a terminal to the M7, and put it into the command mode (+++).2. Enter the command MIMIC X Y where X is the transmission rate when INPUT0 is low,and Y is the transmission rate when INPUT0 is high.3. Exit the command mode. The M7 will begin automatically transmitting every X/Yseconds.On the Receiving M71. Connect a terminal to the M7, and put it into the command mode (+++).2. Enter the ATIO 1 command. This tells the M7 to reconfigure its serial IO port to allowthe digital outputs to be controlled via over-the-air messages.3. Enter the FAILSAFE A B command. The A parameter will be the maximum amount oftime that should ever pass without receiving a MIMIC message. The B parameter is the digital output state if the time set by A passes and no MIMIC messages are received.4. Exit the command mode. The unit is ready to receive MIMIC messages from thetransmitting station.Wiring a MIMIC LinkTo wire an M7 with a switch that will be “MIMICed”, follow the diagram below:When switch S1 is closed, the M7 will transmit at the X rate, and when it is open, it will transmit at the Y rate. INPUT0 uses RS232 level, and a connection to ground is considered a “low”. Anopen circuit or any voltage above about 1V is considered a high. R1 is shown to ensure that the input goes high when S1 opens. A DPDT switch could be used instead.To wire an M7 to receive MIMIC digital signals, follow the diagram below:When a MIMIC signal is received over the air, OUT0 will follow INPUT0 on the sending station. OUT1 will follow INPUT1. This will cause the 12V lamp to light, or the relay to close if a relay is used. Do not load the OUT0 with a device that will draw more than 100mA. NEVER connect OUT0 to a power source.Optional MOSFET DriverThe M7 radio modem has an optional MOSFET output driver on the OUT0 output. (Only the OUT0,, not the OUT1 output). If this option is installed, OUT0 will be pulled to ground to energize an external relay or lamp whenever OUT0 was supposed to go low. So closing S1 on the sending station will cause OUT0 to go low, energizing the relay/lamp/led…The MOSFET that drives OUT0 is a 2N7002 type device. Do not connect a lamp/relay that draws more than 100mA to OUT0. Also, if OUT0 is driving an inductive load, use a surge-protection diode such as a 1N4001 across the load to prevent high-voltage transients.If the optional MOSFET driver is not installed, OUT0 will simply follow INPUT0 with RS232 signal levels.Two-Way MIMIC using Master-SlaveIn the Master-Slave configuration, one “Master” unit transmits is MIMIC digital data to a Slave unit. This configuration is ideal for point-to-point two-way MIMIC ing.Remember to configure the addressing (ATDT, ATMY, and ATMK parameters), so that the M7 radio modems communicate to the units with the correct IDs. See the M7 Technical Manual for information about addressing and IDs.The Slave is configured to respond with an ACK packet each time it receives an over-the-air message from the Master, and embedded in the ACK packet is the digital status of the Slave. The ATRB command configures the ability to send ACK packets. When the Master receives the ACK packet back from the Slave, it updates its output pins OUT0 and OUT1 to match the values of the Slave INPUT0 and INPUT1.Configure the ”Master” as follows1. Set ATRB 1 to configure the M7 to send messages that will require an ACK back fromthe Slave. By default ATRB is 0 (no ACK transmissions).2. Configure the MIMIC X Y command where X is the transmission rate when INPUT0 islow, and Y is the transmission rate when INPUT0 is high. These are the rates at which the master will transmit.3. Set the FAILSAFE A B parameter. The A parameter will be the maximum amount oftime that should ever pass without the Master receiving a MIMIC message from theSlave. The B parameter is the digital output state if the time set by A passes and noMIMIC messages are received.4. Execute the ATIO 1 command. This tells the Master M7 to reconfigure its serial IO portto allow the digital outputs to be controlled via over-the-air messages.On the “Slave” M7, as follows:1. Set ATAK 1 to enable the Slave unit to send ACK packets back to the Master wheneverit receives a message from the Master. Embedded in these ACK packets are theSlave’s digital I/O status bits.2. Execute the ATIO 1 command. This tells the Slave M7 to reconfigure its serial IO portto allow the digital outputs to be controlled via over-the-air messages from the Master.3. Set the MIMIC X Y parameters to something very long. The Slave will respond totransmissions from the Master, so the X Y settings should not be set too short.MIMIC 120 120 will tell the Slave to send its input status every 2 minutes. But it will only send its I/O status automatically if the Master has not sent MIMIC data to it, causing the Slave to send and ACK and the I/O status. If the Master fails to send, then this X Ysetting will determine how often the Slave transmits.4. Set the FAILSAFE A B parameter. The A parameter will be the maximum amount oftime that should ever pass without the Master receiving a MIMIC message from theSlave. The B parameter is the digital output state if the time set by A passes and noMIMIC messages are received.Autonomous Two-Way MIMICWhen configured for autonomous MIMIC transmissions, all M7 radios will transmit the digitalI/O status at the preset intervals as configured with the MIMIC X Y command. When operating in a multi-point configuration, this type of setup is probably preferable to the Master-Slave configuration described above.Remember to configure the addressing (ATDT, ATMY, and ATMK parameters) of all M7 radios, so that the M7 radio modems communicates to the units with the correct IDs. See the M7 Technical Manual for information about addressing and IDs.Configure the M7 radio mode as follows1. Configure the MIMIC X Y command where X is the transmission rate when INPUT0is low, and Y is the transmission rate when INPUT0 is high. These are the rates atwhich the master will transmit at. In systems with many radios, you should consider setting X and Y to different values for each radio.2. Set the FAILSAFE A B parameter. The A parameter will be the maximum amountof time that should ever pass without the Master receiving a MIMIC message from the Slave. The B parameter is the digital output state if the time set by A passes and no MIMIC messages are received.3. Execute the ATIO 1 command. This tells the Master M7 to reconfigure its serial IOport to allow the digital outputs to be controlled via over-the-air messages.4. You may want to enable “Busy Channel Defer”. Set ATBC 1 to enable Busy ChannelDefer. When ATBC is set to 1, the M7 radio will check to make sure the radiochannel is not busy before it transmits, and if it is, it will defer until the channel is clear. If ATBC is set to 0, then this feature is off, and the M7 will transmit when it needs to transmit, regardless of the channel status. By default, ATBC is 0 (unit does not defer to other radios on the channel).Raveon Technologies Corporation2320 Cousteau CourtVista, CA 92081********************760-444-5995。
National LM709 数据手册
TA e 25 C
0 25
0 25
0 25
V ms
Input Offset Voltage RS s 10 kX
30
60
10 mV
Average Temperature RS e 50X
TA e 25 C to TMAX
1 8 10
30
Coefficient of
TA e 25 C to TMIN
1 8 10
Input Offset Voltage Input Bias Current Input Offset Current Input Resistance Output Resistance Supply Current Transient Response
Risetime Overshoot
TA e 25 C RS s 10 kX TA e 25 C TA e 25 C TA e 25 C TA e 25 C TA e 25 C VS e g15V VIN e 20 mV CL s 100 pF TA e 25 C
External components are used to frequency compensate the amplifier Although the unity-gain compensation network specified will make the amplifier unconditionally stable in all feedback configurations compensation can be tailored to optimize high-frequency performance for any gain setting