deviation固件说明书
DEVO系列遥控器在线升级使用手册中文

使用手册如何使用Devention DfuSe USB升级工具―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――1. 目录1. 目录 (1)2. 介绍 (1)3. 系统要求 (2)4. 如何进入程序升级 (3)4.1 devention DfuSe USB升级工具安装 (3)5. 用户使用界面详解 (7)5.1 固件升级界面 (7)5.2 固件升级操作 (9)5.3 配置升级界面 (13)5.4 配置升级操作 (14)5.5 库文件升级界面 (18)5.6 库文件升级操作 (19)5.7 重要提示 (26)6. 修正历史 (26)2. 介绍devention DfuSe USB升级包分为三类:固件、配置、库文件。
“固件”是指基于控制器的程序文件;“配置”是指各个模型模块的配置参数;“库文件”是指主要的图标、语言包以及语言文本。
本工具主要用于升级devention 2.4G遥控器产品的固件、配置和库文件。
本文详细描述如何安装devention DfuSe USB的驱动,以及如何使用此升级工具。
devention DfuSe USB升级包可在官方网站下载。
3. 系统要求为了在Windows操作系统上使用devention DfuSe USB升级工具,您必须在电脑上安装常用的Windows版本,如Windows 98SE,Millennium,2000,XP,或VISTA。
您可以在桌面上右击“我的电脑”,然后点击弹出菜单的“属性”,查看Windows操作系统的版本。
在“系统属性”的“常规”中显示操作系统类型。
如图1。
图1:系统属性对话框4. 如何进入程序升级4.1 devention DfuSe USB升级工具安装l软件安装运行DevoDfuSe_V1.0_Setup.exe 文件:安装向导将指导您安装Devention DfuSe USB 升级工具。
DeviceDrive Wi-Fi模块说明书

U S E R M A N U A LDeviceDrive clickDeviceDrive click is a complete Cloud-on-M odule solution with Wi-Fi functionality and an integrated PCB antenna. The onboard WRF01-M 24A module comes preloaded with DeviceDrive firmware.To our valued customersI want to express my thanks to you for being interested in our products and for having confidence in Mikroelektronika.The primary aim of our company is to design and produce high quality electronic products and to constantly improve the performance thereof in order to better suit your needs.Nebojsa MaticCEOTable of ContentsIntroduction 4 1. Set up your product in the cloud 59SimulatortheClient2. InstallingDeviceDrive10clickup3. Set103.1. Connect DeviceDriveclick3.2 Connecting to PC over USB/UART converter113.3 Setting up DeviceDrive click with LinkUp 134. Device Simulator 15polling 16 Data4.1.5. Advanced 176. Upgrade demo board 19IntroductionWRF01 is a Wi-Fi (802.11B/G/N) module from DeviceDrive. By using the DeviceDrive click, you can connect it to your PC and simulate real device behaviour, to learn how the device works and how it communicates to the cloud and to the app.This document introduces the WRF01 Client Simulator and aims at giving you a quick start for developing with the DeviceDrive click. The program communicates with the DeviceDrive click trough the serial ports and is suited for acting as a client and for prototyping IoT-Products.The following sections give the steps how to get started:∫ Section 4: Set up your product in the cloud∫ Section 5: Installing the software∫ Section 6: Set up DeviceDrive click∫ Section 7: Simulate IoT device∫ Section 8: Send custom DeviceDrive click messages∫ Section 9: Upgrading your WRF011. Set up your product in the cloudIn order to use the DeviceDrive click with the DeviceDrive cloud and the client simulator you need to sign up on the DeviceDrive management portal. If you already have an account, you can just sign in and create a new product on your account. Goal: Get a valid product key to use with this tutorialProcedure for signing up:1.S ign up at https://2.P ress email signup3. E nter your email address and press“Send verification code”4. Y ou will receive an email with your verification code. Copy this code to your clipboard and paste into the registration form. Then click “Verify code”.5. E nter your preferred password and your name.Then press “Create”.6. R egister your company name. This is the name of your DeviceDrive management account. It can contain several users and several products.7. R egister your test product. Enter a name for your product and select “Internal agent”. Then copy the product key to your clip board and press“Save”.8. P aste the product key somewhere (e.g. Notepad) so that you can use it later.2. Installing the Client SimulatorIf your Antivirus complains that the software package is not signed, please ignore and run the install anyway. Download the software from https:///downloadsRun the installer. This will install the software and add the examples folder to the program folder. After the install is finished, you can launch the program from the start menu or the desktop icon.3. Set up DeviceDrive clickThis section describes how to connect your DeviceDrive click to the network and configure your product key.3.1 Connect DeviceDrive clickConsidering that DeviceDrive click is a board withUART interface you will need additional board to make it working. There are severals ways that you can put in use your DeviceDrive click board.Option 1 – click USB adapter (or any USB to UART converter)Option 2 – clicker 2 (or any other development system with mikroBUS™ socket). 2 13.2 Connecting to PC over USB/UART converter Array Your computer will recognize the device, and designate a COM port for it. As soon this is done, will see the COM port in the dropdown (1) in the picture above.If the connection is successful, the color of the Connection Status Indicator (2) will change from Red to Green. The Host port communication window will give you the exact communication log between the Simulator and WRF01. Use this to learn about how the WRF01 behaves in a normaloperating cycle.It is possible to mix up the host port and the log port in the two windows. It is recommended to plug in the HOST port first, and then select the port in the host communication window before connecting the log port.When DeviceDrive click is connected, enter the product key (the one from the management portal) in to the field marked “Product Key” (3). If you want the device online right away enter the network ssid and password in their fields. If your product key is defined as a “Forwarding product”, you can enter these right away, and start sending data, but if you have an “Internal product” and wish to use the mobile app SDK’s, you should LinkUp using the app. In addition, you can attach the log port to your computer with an USB mini cable. This will also register as a COM port in your system. In the “Log port Output” window, select the new COM port. Check the status indicator on the right-hand side to see that the connection is successful.When you are ready, press “Init” (4). This will initiate the WRF01. You should see the message “Response OK” in the Serial output window, and if you attached the Log port, you should see the WRF01 internal workings while connecting to your access point (router).Hold your mouse over the quick commands to get more information about them.3.3 Setting up DeviceDrive click with LinkUpLinkup is only required if your device is an “Internal product” in the DeviceDrive system.To make the DeviceDrive click ready for LinkUp, use the “Show Device” (1)button to enable the local AP.You can also use SmartLinkup to initiate the SmartLinkup procedure. This procedure lets the user connect the device withouthaving to use the Soft AP.The DeviceDrive Playground App is available on Apple Store and Android Play. When you are using the LinkUp procedure, the SSID and password for your network is sent, along with the security token for your device. This is the reason that you need to use the LinkUp system when working with Internal Products. For more information about how to use the DeviceDrive Playground app and the internal product, please see this video and the documentation.The screenshots below show how the Playground app lets you link up your new device and show the simulated data from the device simulator.The device state is shown in the app after the introspect and current state have been sent to the cloud. The next section describes how to simulate device behavior.4. Device Simulator Array On the top of the DeviceDrive WRF01 Client Simulator, you will find the Device Simulator tab. This tab gives you the opportunity to test the introspection functionality and lets you integrate the DeviceDrive click with an app with our SDK or the DeviceDrive Playground app.Before you can start simulation, please make sure that you followed the steps in chapter Feil! Fant ikke referansekilden., 6.1 and 6.2.To be able to send a status update, first press the “Send Introspect” (1) button. This sends a message to the cloud with the “capabilities” of your product. See the Serial specification documentation or this video about more information about the introspection document. This is a prerequisite for the APP you’re using to control your device.When the introspection document is sent you can click the temperature or light controller to send devicedata to the cloud. The app will automatically updatewith the new device data.4.1 Data pollingapp to the device. If you are using the DeviceDrivePlayground app, try to flip the button marked“Light”.Press the “Poll” (1) button to read pending statusupdates from the app. You can check “Auto poll” tolet this happen automatically at the given interval.The simulated state will be updated according tothe received messages.∫ Polling requires SSL to be enabled on the WRF01 (versions below 4.0). Please press “Init” again if the system does not receive messages.∫ Version 4.0 supports MQTT, so if the WRF01 is already connected to the server, the messages from the app will appear asynchronously without polling.∫ There is no queue system in this software, so if you try to send or receive a lot of messages in rapid succession, you might experience the “System busy” error message. To resolve this, wait for the WRF01 to complete the current operation. This can be seen in the Log window. In a real application you can use our client SDK source code where a queue is implemented.5. Advanced Array Use the Advanced screen to send custom messages and choose from a set of predefined message templates.This screen is suited for those who wish to tweak the messages sent to the server, or to test the whole range of the available commands for the WRF01. By default, the two drop-down menus should point to the folder that came bundled with the installation. To use the WRF01 commands, select “wrf01 commands” (1) in the first dropdown. In the second, you will be able to see the available commands. These match the “Serial specification documentation” and you can enter, or change the properties / values in the text field below.Before pressing send, make sure that there is an EOT character at the end of your transmission. Itwill be marked with a small rectangle after yourlast bracket.If there is no EOT char, press the “Add EOT” button.command to the device.In addition to all of the available WRF01 commands,this software comes with some examples ofintrospection and status messages you can try.In the text field you can add your own text or messagesand send to the WRF01. If you are using your owncloud and require special messages, this is where youcan send them.The “Browse” (2) button lets you select the base folderto show template messages from.This software strips your message of all <CR> <LF> characters before sending them to the WRF01. In a real-world application, do not use these characters in a WRF01 command. They have to comply exactly with the serial specification. If a command does not start with exactly {"devicedrive": the message will be interpreted as a cloud message transfer, and not a WRF01 command.6. Upgrade demo board The upgrade pane lets you easily experiment with upgrading and downgrading your WRF01 module on DeviceDrive click.Notice that the upgrade itself has to be defined in the management portal.Perform each of the steps manually or just press “Do all” (1) to upgrade automatically (but you still need to define the upgrade in the managementportal).Define the upgrade in the management portal (click the link in point 1) (2).Click each of point 2-4 or just press “Do all” to run automatically.You should see that the current version field updates to the selected version (3).DISCLAIMERAll the products owned by MikroElektronika are protected by copyright law and international copyright treaty. Therefore, this manual is to be treated as any other copyright material. No part of this manual, including product and software described herein, may be reproduced, stored in a retrieval system, translated or transmitted in any form or by any means, without the prior written permission of MikroElektronika. The manual PDF edition can be printed for private or local use, but not for distribution. Any modification of this manual is prohibited. MikroElektronika provides this manual ‘as is’ without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties or conditions of merchantability or fitness for a particular purpose. MikroElektronika shall assume no responsibility or liability for any errors, omissions and inaccuracies that may appear in this manual. In no event shall MikroElektronika, its directors, officers, employees or distributors be liable for any indirect, specific, incidental or consequential damages (including damages for loss of business profits and business information, business interruption or any other pecuniary loss) arising out of the use of this manual or product, even if MikroElektronika has been advised of the possibility of such damages. MikroElektronika reserves the right to change information contained in this manual at any time without prior notice, if necessary.HIGH RISK ACTIVITIESThe products of MikroElektronika are not fault – tolerant nor designed, manufactured or intended for use or resale as on – line control equipment in hazardous environments requiring fail – safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life support machines or weapons systems in which the failure of Software could lead directly to death, personal injury or severe physical or environmental damage (‘High Risk Activities’).MikroElektronika and its suppliers specifically disclaim any expressed or implied warranty of fitness for High Risk Activities.TRADEMARKSThe MikroElektronika name and logo, mikroC, mikroBasic, mikroPascal, Visual TFT, Visual GLCD, mikroProg, Ready, MINI, mikroBUS™, EasyPIC, EasyAVR, Easy8051, Click boards™ and mikromedia are trademarks of MikroElektronika. All other trademarks mentioned herein are property of their respective companies.All other product and corporate names appearing in this manual may or may not be registered trademarks or copyrights of their respective companies, and are only used for identification or explanation and to the owners’ benefit, with no intent to infringe.The FTDI Chip® and Windows® logos and product names are trademarks of FTDI Chip and Microsoft® in the U.S.A. and other countries.Copyright © 2019 MikroElektronika. All Rights Reserved.If you want to learn more about our products, please visit our website at If you are experiencing some problems with any of our products or just need additional information, please place your ticket at /supportIf you have any questions, comments or business proposals, do not hesitate to contact us at*****************Designed by Mikroelektronika Ltd.。
MGate MB3660系列固件发布说明书

Firmware for MGate MB3660 Series Release NotesSupported Operating SystemsNotesChangesApplicable ProductsBugs Fixed• Vulnerability issues (higher level or above) have been fixed, following a Nessus and Defensics scan.• Supports MXconfig v2.6 and MXview v3.1.8.• Enhanced the System Log display.• Strengthened the TLS cipher suite for security enhancement.• Enhanced MOXA commands under the account login process.• Adjusted Telnet default settings from enable to disable.• Disabled unsecure TLS 1.0 and TLS 1.1.• Enhanced Accessible IP List feature.• Added CSRF attack protection for login webpage.• Serial parameters might have been incorrect when switching between ASCII and RTU modes.• Fixed the incomplete display in the web console.• Fixed SNMPv3 issues.• Fixed the MGate's failure to get an IP address under DHCP mode.• Fixed https connections that might have caused the web service to stop working.EnhancementsN/AN/AN/ANew FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/AN/AEnhancementsN/AN/ASupports MGate MB3660I-8-2AC and MGate MB3660I-16-2AC new hardware version v1.1.New FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs Fixed• Accessible IP List supports denying Web/Telnet console access.• In Agent mode as a Modbus ASCII master, MGate would hang after plugging and unplugging a serial cable.EnhancementsN/AMGate MB3660-8-J-2AC, MGate MB3660I-16-2AC, MGate MB3660-16-J-2AC, MGate MB3660-8-2AC, MGate MB3660-8-2DC, MGate MB3660I-8-2AC, MGate MB3660-16-2AC, MGate MB3660-16-2DC• Supports security features based on IEC-62443.New FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs Fixed• Enhanced the complexity of token generation to protect against CSRF attacks.• Enhanced the complexity of the key for password encryption in the web console login process.• Encrypts sensitive information in exported configuration file.• Enhanced the display of auto detection results in MODBUS transparent mode.• Firmware version check problem when upgrading firmware for MGate MB3660I-16-2AC, MB3660-8-J-2AC, and MB3660-16-J-2AC.• Modbus RTU communication would fail if FIFO was disabled.• The FIFO setting would not be activated after clicking the “Submit” button.• Stack-based buffer overflow issue in web console which may cause web service corruption.• Challenge ID generation problem which may cause web console login failure.EnhancementsN/AMGate MB3660-8-J-2AC, MGate MB3660I-16-2AC, MGate MB3660-16-J-2AC, MGate MB3660-8-2AC, MGate MB3660-8-2DC, MGate MB3660I-8-2AC, MGate MB3660-16-2AC, MGate MB3660-16-2DCN/ANew FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs Fixed• Improved security of the TCP sequence number.• Improved beeper behavior in DHCP mode.• Modbus RTU diagnose error in agent mode.• Initial error relay state when powered on.EnhancementsN/AMGate MB3660-8-J-2AC, MGate MB3660I-16-2AC, MGate MB3660-16-J-2AC, MGate MB3660-8-2AC, MGate MB3660-8-2DC, MGate MB3660I-8-2AC, MGate MB3660-16-2AC, MGate MB3660-16-2DC• Supports MGate MB3660I-16-2AC, MGate MB3660-8-J-2AC, MGate MB3660-16-J-2AC models.New FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs Fixed• The Modbus master in agent mode supports up to 256 commands for each serial port.• Supports multi-master in "routing by IP address" and "routing by TCP port" modes.• Supports sorting of commands in the I/O mapping page.• Supports auto internal memory assign in the command page.• Supports Modbus slave ID 255 in transparent mode.• User password and SNMP community name may be exposed by a buffer overflow issue.EnhancementsN/AMGate MB3660-8-2AC, MGate MB3660-8-2DC, MGate MB3660I-8-2AC, MGate MB3660-16-2AC,MGate MB3660-16-2DC• Supports Auto Device Routing in Modbus transparent mode.• Supports Modbus TCP traffic logs.New FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Bug in Modbus Master mode which may cause the MGate to reboot under some conditions.EnhancementsN/AMGate MB3660-8-2AC, MGate MB3660-8-2DC, MGate MB3660I-8-2AC, MGate MB3660-16-2AC,MGate MB3660-16-2DCN/ANew FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Initial delay issue which would stop Modbus communication.EnhancementsN/AMGate MB3660-8-2AC, MGate MB3660-8-2DC, MGate MB3660I-8-2AC, MGate MB3660-16-2AC,MGate MB3660-16-2DCN/ANew FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Fix the algorithm which may cause Modbus transparent mode to stop communication.• Serial port 13 interface initialization problem.• Modbus traffic exceptions in the serial port are not handled well, which might cause the serial port to stop transmitting data.• When the "Read memory address" is greater or equal to 8192 for the "01 - Read Coils" or "02 -Read Discrete Inputs" functions, data will be written to the wrong internal memory address.EnhancementsN/AMGate MB3660-8-2AC, MGate MB3660-8-2DC, MGate MB3660I-8-2AC, MGate MB3660-16-2AC,MGate MB3660-16-2DCN/ANew FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/AN/AEnhancementsN/AMGate MB3660-8-2AC, MGate MB3660-8-2DC, MGate MB3660I-8-2AC, MGate MB3660-16-2AC,MGate MB3660-16-2DC• First release.New FeaturesN/AN/A。
MTL Tofino 9211-ET硬件版本1.8.0的安全应用程序固件升级说明说明书

Eaton Electric Limited,Great Marlings, Butterfield, LutonBeds, LU2 8DL, UK.Tel: + 44 (0)1582 723633 Fax: + 44 (0)1582 422283 E-mail:********************© 2016 EatonAll Rights ReservedPublication No. TSN700 Rev 2 241016October 2016EUROPE (EMEA):+44 (0)1582 723633********************THE AMERICAS:+1 800 835 7075*********************ASIA-PACIFIC:+65 6 645 9888***********************The given data is only intended as a productdescription and should not be regarded as a legalwarranty of properties or guarantee. In the interestof further technical developments, we reserve theright to make design changes.MTL security appliance firmware upgradeMTL Tofino TM 9211-ETRelease 02.2.00• PurposeThis release note describes the firmware upgrade available for version 1.8.0 of the MTL Tofino 9211-ET hardware. This firmware upgrade is permanent and persists across factory resets of MTL Tofino 9211-ET security appliance.• ImpactThis package upgrade is a major upgrade. The upgrade process takes up to 5 minutes. Limit network traffic prior to running the upgrade, as the device can drop network traffic during the upgrade process.• Upgrade Files• appliance_config• ARGON 100_to_v02.2.00.tar.sec•Required Equipment• MTL Tofino 9211-ET running version 1.8.0 firmware • USB storage device (formatted as FAT32)• Upgrade filesNote: The ACA22-USB storage device has been tested by MTL Tofino and is therefore recommended. For ordering ACA22-USB, see “Accessories“ in the Installation Guide.• Procedure: Upgrade via USBFollow the steps below to upgrade MTL Tofino 9211-ET using a USB storage device.• Copy the appliance_config and ARGON 100_to v02.2.00.tar.sec into the root directory of anempty USB storage device.• Verify the MTL Tofino 9211-ET is powered on for at least 1 minute.• Insert a USB storage device into one of theUSB ports.• Press and hold the “Config“ button for 5 seconds.Note: The “Mode“, “Event“ and “Fault“ LEDs begin to flash, in an upward sequence, to indicate Load.• Wait for the flashing sequence to stop.• Remove the USB storage device.• Disconnect the power supply of MTL Tofino 9211-ET and r econnect t o r eboot t he M TL T ofino 9211- ET.• Reapply the configuration from the MTL Tofino Configurator software.Note: Refer to Chapter 9 in the MTL Tofino Configurator 02.2.00 User Manual for detailed instructions.• Verify the UpgradeAfter the upgrade procedure you can find ${TOFINO_ID}_ARGON 100_to_v02_2_00.log file on the USB storage device. Open this file using a text editor such as WordPad. The text editor displays 1 of the following messages:• Successful Update...Rebooting Device into02.2.00 software, if the upgrade is successful.• Update Failed...Reverting to original state, if the upgrade is unsuccessful.**For migration from 9510-CMP Tofino Central Management Platform to Tofino Configurator (TC) please view the documents below on our website at /product/9202-ets_mtl_tofino_ network_security_solution/• MTL Tofino Configurator 02.2.00 Licensing Guide • Section 14 'Converting CMP License to a TC License' on the 'MTL Tofino Configurator 2.2'manual。
devolo dLAN Audio extender Starter Kit 产品说明书

dLAN Audio extender Starter KitCaractéristiques techniquesStandards dLAN Audio extender :▪Standard HomePlug 1.0dLAN duo :▪Standard HomePlug 1.0▪Spécification Ethernet IEEE 802.3, IEEE 802.3x, IEEE 802.3u▪Auto MDI / X▪Spécification USB, Rév. 1.1Protocoles CSMA/CD via le réseau électriqueTaux de transfert 14 Mbits/sTaux binaire audio Qualité CD stéréo 16 Bit, 44,1 KHzMode de transmission asynchrone via le réseau électriqueBuffer réseau dLAN Audio∅ 1 sec.extenderModulation OFDM - 84 Carrier (Orthogonal Frequency Division Multiplexing) via le réseauélectriquePortée 200 mSécuritéCryptage DES pro via le réseau électriqueTémoins lumineux dLAN Audio extender :▪ Marche▪ dLAN▪Sound LinkdLAN duo :▪ 3 connecteurs (Link/Act 10 Ethernet, Link/Act 100 Ethernet, USB)▪ 3 état dLAN (Power, Act, Link)Port dLAN fiche EUROType de connexion dLAN Audio extender :▪Line-Out : 2 x cinch, 1 x jack∙Rapport signal/bruit analogique sortie : 87db(AT)∙Taux de distortion harmonique (THD) : 0.01% @ 1kHz∙RL > 3k OhmdLAN duo :▪Prise USB – type B▪Interface Ethernet RJ45Consommation dLAN Audio extender :▪ 4 W (max.)dLAN duo :▪4,5 W (max.), 3 W en veilleAlimentation électrique Alimentation intégrée via la prise de courant :▪Tension nominale : 110 - 240 V AC▪Courant nominal : 50 mA / 230V + 80 mA / 110V▪Fréquence nominale : 50/60 HzTempérature Stockage : -25°C – 70°CExploitation : 0°C – 40°CDimensions dLAN Audio extender : 80 x 65 x 40 mm (hauteur x profondeur x longueur)dLAN duo : 80 x 63 x 37 mm (hauteur x profondeur x longueur)Poids dLAN Audio extender : 158 gdLAN duo : 130 gdLAN Audio extender Starter KitConditions ambiantes Humidité de l'air 10–90% (sans condensation)Systèmes d'exploitation Logiciel de configuration et logiciel Plug-In pour Windows® XP32bit,Windows® Vista32bit,Homologations Conforme aux exigences techniques CE pour tous les pays de l'Unioneuropéenne et la Suisse :dLAN Audio extender :▪EN 60950 -1:2001+ A11:200455022:2006▪ EN▪ EN50412-2-1:2006dLAN duo :55022▪ EN55024▪ EN60950▪ ENInformations commercialesN° de référence 01199 (EU / CH / NO), 01212 (FR), 01206 (UK)Code EAN 4250059611993 (EU / CH / NO), 4250059612129 (FR),4250059612068 (UK)Garantie 3 ansSAV et assistance technique Support téléphonique et par courrier électronique. Vous trouverez les numéros detéléphone et les adresses de courrier électronique sur le prospectus d'assistancetechnique fourni avec le produit et sur le site Internet devolo.Boîtier Boîtier en plastique avec prise murale (grand)Poids 730 gDimension de l'emballage 188.5 x 231 x 78.5 mm (hauteur x profondeur x longueur)Accessoires ▪Câble stéréo cinch▪Câble USB (USB A - USB B)▪Câble Ethernet RJ45/RJ45▪Documentation : guide d'installation en version imprimée▪CD-ROM : manuel PDF, Logiciel de configuration pour Windows® XP32bitet Windows® Vista32bit, outil de supervision devolo Informer, Informations suppl. WEEEPoids WEEE 503 gPapier (point vert) 302 gMetière plastique (point vert) 18 gDivers (point vert) 0,4 g。
Odyssey7Q+固件更新说明说明书

Updated February 23, 2015 | Firmware Release v5.10.1004K Apple ProRes 4096x2160 / 24p 3840x2160 / 23.98,25,29.97HD Apple ProRes 422(HQ) 1080p23.98,24,25,29.97,50*,60*720p50/60*only supported on 7Q+GH4Odyssey7Q+Odyssey7QSETUP GUIDENOTES ABOUT USING THE ODYSSEY WITH THE GH44K or 1080p50/60 over HDMI is only supported on the Odyssey7Q+, to record 1080p50/60 on an Odyssey7 or Odyssey7Q you must use an HDMI to SDI converter. Odyssey7/Odyssey7Q are limited to 1080p30 over HDMI due to a hardware constraint.PRORES RECORD TIMESNote: 4K and 1080p50/60 over HDMI is only supported on the 7Q+, to record 1080p50/60 on an Odyssey7 or Odyssey7Q you must use a HDMI to SDI converter, as 7/7Q are limited to 1080p30 over HDMI due to a hardware constraint.Note: Odyssey 7 only has 1 SSD slotFORMAT DETAILSFRAME RATE SUPPORTThe following rame rates are supported on the Odyssey from the GH4• 4K 23.98-30Odyssey7: Not supported.Odyssey7Q: YAGH SDI Outputs 1-4Odyssey7Q+: YAGH SDI Outputs 1-4 or HDMI• 1080p59.94/50Odyssey7: Not supported.Odyssey7Q: YAGH SDI or HDMI to SDI converterOdyssey7Q+: YAGH SDI or HDMI• 1080i50/59.94 : HDMI or SDI• 1080p25/29.97 : HDMI or SDI• 1080p23.98 (24p output and 3:2 pulldown) : HDMI or SDI•720p50/59.94 : HDMI or SDICAMERA SETTINGS (SECTION 1 - HDMI OUTPUT)1. SWITCH CAMERA TO VIDEO MODEROTATE THE MODE DIAL TO THE POSITION.2. SET INTERNAL RECORDINGMENU » (5) » SYSTEM FREQUENCY » (59.94/50/24)MENU » (1) » REC QUALITY » (4K 100MB**/FHD 60/** FHD 30/FHD 24)Note: 4096x2160 (C4K) can only be selected with 24p.3. SET HDMI OUTPUTMENU » (4) » HDMI REC OUTPUT » BIT MODE » (4:2:2 10-BIT*/4:2:2 8-BIT)* Note when set to 4:2:2 10 bit, the camera will not record internally**When wish to record 4K you must first plug a 4K rated HDMI cable into the odyssey to get the 4K output menu, and ensure 4K Down Convert is OFF.MENU » (4) » HDMI REC OUTPUT » 4K DOWN CONVERT » (AUTO/OFF)4. SET HDMI TIMECODE/CAMERA TRIGGERNote: HDMI Timecode/Camera Trigger requires GH4 firmware version 2.1 or higher.MENU » (4) » TIMECODE (2) » HDMI TIME CODE OUTPUT » ONThis will output timecode to the Odyssey, which will be recorded with your video signal.MENU » (4) » HDMI REC OUTPUT » HDMI RECORDING CONTROL » ONThis allows you to start/stop recording on the Odyssey with the record button on the GH4.5. SET CLEAN HDMI OUTPUTMENU » (4) » HDMI REC OUTPUT » INFO DISPLAY » OFF** Note that 4K and 1080p50/60p over HDMI is only supported on the Odyssey7Q+ 1080p50/60 is supported on any Odyssey with the use of a HDMI to SDI converter. CAMERA SETTINGS (YAGH OUTPUT)This section covers the use of the GH4 with the YAGH Interface (Panasonic DMW-YAGH).1. CONNECT THE YAGH TO THE CAMERA2. CONNECT THE ODYSSEY TO THE YAGHVIA HDMIConnect the HDMI output from the YAGH to the HDMI input of the Odyssey.VIA SDIConnect each of the four BNC outputs on the YAGH to the SDI ports on the OdysseySDI OUT 1 » SDI A INSDI OUT 2 » SDI B INSDI OUT 3 » SDI A IOSDI OUT 4 » SDI B IO3. SETUP THE YAGH FOR TRIGGERING VIA SDIMENU then Motion Picture then Interface unit and set SDI Remote Recording to ONMENU » (1) » INTERFACE UNIT» SDI REMOTE RECORDING » ON4. SET 4K DOWN CONVERT (IF YOU ARE RECORDING HD)When using the YAGH for HD Recording you must set the 4K down convert to 1080p.MENU » (4) » HDMI REC OUTPUT » 4K DOWN CONVERT » 1080P5. SWITCH CAMERA TO VIDEO MODEROTATE THE MODE DIAL TO THE POSITION.(See diagram in Section 1)6. SET INTERNAL RECORDINGMENU » (5) » SYSTEM FREQUENCY » (59.94/50/24)MENU » (1) » REC QUALITY » (4K 100MB**/FHD 60/** FHD 30/FHD 24)7. SET HDMI OUTPUTMENU » (4) » HDMI REC OUTPUT » BIT MODE » (4:2:2 10-BIT*/4:2:2 8-BIT)* Note when set to 4:2:2 10 bit, the camera will not record internally**When wish to record 4K you must first plug into the odyssey to get the 4K output menu, and ensure 4K Down Convert is OFF.MENU » (4) » HDMI REC OUTPUT » 4K DOWN CONVERT » OFF8. SET HDMI TIMECODE/CAMERA TRIGGERNote: HDMI Timecode/Camera Trigger requires GH4 firmware version 2.1 or higher.MENU » (4) » TIMECODE (2) » HDMI TIME CODE OUTPUT » ONThis will output timecode to the Odyssey, which will be recorded with your video signal.MENU » (4) » HDMI REC OUTPUT » HDMI RECORDING CONTROL » ONThis allows you to start/stop recording on the Odyssey with the record button on the GH4.9. SET CLEAN HDMI OUTPUTMENU » (4) » HDMI REC OUTPUT » INFO DISPLAY » OFF** Note that 4K and 1080p50/60p over HDMI is only supported on the 7Q+ 1080p50/60 is supported on 7Q/7 with the use of a HDMI to SDI converter.ODYSSEY CONFIGURATION1. SET ODYSSEY RECORD MODEHD RECORDING☼4K PRORES RECORDING (ODYSSEY7Q+)☼4K HDMI TO 2K PRORES RECORDING (ODYSSEY7Q+)☼Camera must be set to 4096x2160UHD HDMI TO HD PRORES RECORDING (ODYSSEY7Q+)☼Camera must be set to 3840x21602. MAKE GH4 THE RECORD TRIGGERNote: Camera Record Trigger requires GH4 firmware version 2.1 or higher.☼3. SET TIMECODE SOURCENote: HDMI/SDI Timecode requires GH4 firmware version 2.1 or higher.☼The HDMI input is automatically detected when connected to the Odyssey.** Note the HDMI input is on the right side of the unit, on the Odyssey7Q+ but is at the bottom of the unit for Odyssey7 and 7Q.4. SELECT CODEC☼(PRORES HQ | PRORES 422 | PRORES LT)5. FORMAT SSDs☼ » ODYSSEY » SSD’S » FORMAT BOTH(or FORMAT SSD1 if you do not have a second SSD drive installed.)6. CONNECT TO CAMERA AND VERIFY STATUS INPUTCONNECT GH4 HDMI OUTPUT TO ODYSSEY HDMI INPUTThe status on your Odyssey will display your camera’s output.Example:UHD 23P 4:2:2PANASONIC3840 x 2160PRORES4K/UHD7. SET HDMI CADENCEConnect HDMI input, and verify the camera internal record rate matches the input indicator on the Odyssey. If it does not a Cadence may be needed to correctly reflect the format in which you wish to record.☼ » SETUP » VIDEO CADENCE » PROGRESSIVEPROGRESSIVEUse this setting for 720p50/60, 1080p24**, 25*,30**Note typically the camera will need to be set to record 1080p25/30 internally, and the output is set to 1080i.**Note that when wishing to record 1080p24, HDMI output can be set to “Auto” or 1080i, therefore Progressive should be used when auto is selected.INTERLACEDUse this setting for 1080i50, 1080i59.94 recording3:2 PULLDOWN*/**Use this setting for 1080p24 recording when the camera only has a output setting of 1080i, also note the camera must be set to record 1080p24 or 1080p23.98 internally, **Note that when wishing to record 1080p24, HDMI output can be set to “Auto” or 1080i, therefore 3:2 pulldown should be used when 1080i is selected.COPYING FILES TO YOUR COMPUTER1. CONNECT SSD DRIVE TO ADAPTERConnect the Convergent Design 2.5” Premium SSD Media to any off-the-shelf 2.5” SATA adaptor (example: Seagate GoFlex Thunderbolt Adaptor or USB 3.0 Adaptor)2. CONNECT ADAPTER TO COMPUTERThe SSD will mount within 10-20 Seconds. (You will see this mount on the desktop or within finder on MAC, or within My Computer on Windows machines).3. COPY FILES FOR PLAYBACK/EDITINGAll Clips or Takes are located within the “Clips” directory, navigate to this and copy all of your files to a local or external drive or RAID for playback and/or editing.SOFTWARE UTILITIES (FREE DOWNLOAD FROM WEBSITE)CD CLIP MERGER (RAW/DPX)Use the Clip Merger for any Raided Record (ie if your recorded clip required more than one SSD).CD APPLE PRORESS TRANSFER TOOL (FREE DOWNLOAD FROM WEBSITE) Use to combine clips into a single fileUse to copy all files to a single directory without folder structure.Required in order to transfer markers to your NLE.CD DATA UNPACKER (DPX)Use CD Data Unpacker to convert “packed” files to “unpacked” data.ALL UTILITIES CAN BE DOWNLOADED FROM THE FIRMWARE/DOWNLOADSAREA OF OUR WEBSITE: C /support/firmware-downloads.htmlATTENTION MAC OSX USERSBefore installing Convergent Design Software on Mac OSX You must first change the following settings.1) Navigate to Applications» Utilities» System Preferences2) Select Security and privacy3) Under General » Allow applications downloaded from: Select Anywhere.Apple ProRes 422 (HQ/422/LT)The Odyssey 7 and 7Q records in Apple ProRes HQ, 422 or LT which are 10 bit 4:2:2 compressed codecs. This will allow for high quality recording while avoiding high data rates of working with uncompressed video. (DPX)APPLE PRORES BITRATESApple ProRes 422 (HQ): 220Mb Apple ProRes 422 140Mb Apple ProRes 422 (LT) 100MbNATIVE APPLE PRORES 422 SUPPORTAdobe CC 2014Apple FCP X, Aperture Cineform Studio Final Cut Pro 7 Black Magic DaVinci Resolve The Foundry Nuke Autodesk Smoke Sony VegasWORKING WITH RECORDED FILESThere are numerous post systems and NLEs that can read natively the various file formats recorded by the Odyssey. Some NLEs may require plug-ins in order to read certain file formats. Blackmagic Design Resolve software is available for free and can read all formats recorded by the Odyssey.FILE STRUCTURENote: To combine files into a single directory use our ProRes Utility.++(720)221-3861✉ *******************************☁ 。
意法半导体DFUSe USB设备固件升级入门说明书

UM0412User manualDfuSe USB设备固件升级意法半导体扩展入门引言本文档介绍了演示用户界面,该界面专为介绍STMicroelectronics设备固件升级库的开发而设计。
该库的描述(包括其应用编程接口)包含在“DfuSe应用编程接口”文档中,并随DfuSe软件一起安装。
2019年3月Doc ID 13379 Rev 1 [English Rev 4]1/22目录UM0412目录1入门指南 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1系统要求 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2演示程序的组成部分 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3DfuSe演示程序安装 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3.1软件安装 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3.2硬件安装 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62DFU文件 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123用户界面说明 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.1DfuSe演示 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.2DFU文件管理器 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2.1“想要执行”对话框 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2.2“文件生成”对话框 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2.3“文件提取”对话框 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174分步流程 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.1DfuSe演示步骤 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.1.1如何上传DFU文件 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.1.2如何下载DFU文件 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.2DFU相关文件生成步骤 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.2.1如何从S19/Hex/Bin文件生成DFU文件 . . . . . . . . . . . . . . . . . . . . . . . . . . 204.2.2如何从DFU文件提取S19/Hex/Bin文件 . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5版本历史 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212/22Doc ID 13379 Rev 1 [English Rev 4]UM0412表格索引表格索引表1.“DfuSe演示”对话框说明 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14表2.“文件生成”对话框说明. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16表3.“Multi bin injection”对话框说明 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17表4.“文件提取”对话框说明. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18表5.文档版本历史 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21表6.中文文档版本历史. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Doc ID 13379 Rev 1 [English Rev 4]3/22图片索引UM0412图片索引图1.系统属性对话框. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5图2.选择安装位置 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7图3.驱动选择选项 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8图4.驱动选择. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9图5.从磁盘安装 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10图6.进度消息. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10图7.警告消息. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11图8.安装完成. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11图9.“DfuSe演示”对话框. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13图10.“编辑选项字节”对话框. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15图11.“想要执行”对话框 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15图12.“生成”对话框. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16图13.“Multi bin injection”对话框. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17图14.“提取”对话框. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4/22Doc ID 13379 Rev 1 [English Rev 4]UM0412入门指南Doc ID 13379 Rev 1 [English Rev 4]5/221入门指南1.1 系统要求为了在Windows 操作系统上使用DfuSe 演示程序,PC 上的Windows 必须是较新的版本,例如Windows 98SE 、Millennium 、2000、XP 或VISTA 。
deviation固件说明书解析

DEVIATION说明书第一版前言年初购入devo10,那个论坛成为神控的遥控器。
神控处了这个控的硬件可圈可点外,最重要的一点就是刷入deviation(官网,英文的)这个固件后兼容dsm2等多种主流的制式,实现一控多种接收共用。
而且其开放的平台,能够不断升级增加功能,更有suv等大大的不断奉献,至此deviation 版本走了3.1版,链接/thread-241130-1-1.html感谢各位模友大大的无私奉献,我有幸用上这个神器。
经过一番专研,翻阅说明书后终于大概了解如何设置和运用,deviation的自由度很高,各个通道均可以自定义,让你打造属于自己的控,用起来随心所欲。
里面的混控器是属于底层的混控,自由度很高,不过的确需要一段时间来理解,如果学会了会觉得很好用的,想怎混就怎混。
由于官方说明书是英文的,而且不是说得很明白,加上经常有模友问及如何设置,于是本人萌生出写一下中文说明书的念头,再加点应用例子,务求各位模友更易明白上手,而且通过大家的讨论还能加深本人对这个固件的认识,达到共同进步的目的。
一下都是本人自己的认识跟见解,如有问题请提出来大家切磋讨论。
hilitiQ群:2954863552013年8月22日主界面这个是开机后的主界面,在这里吐槽一下我见过的devo10屏幕贴上都是有灰的,难道厂里贴膜的那个车间就在矿里?至少这一点学一下天地飞吧,出厂膜漂亮得很。
以下是菜单设置,首先是主菜单,这个没什么好说的,很简单明白通用模式进入模型设置,如果之前接触过遥控的话,这些名词也是很清楚明白的,如果还没有搞明白的话,潜水去吧骚年~~好了,现在进入模型设置里面的模型设置菜单(控上是这样写的,不要怪我),第一个模型文件那里,看到黑色部分左右会有箭头的是可以进行左右选择,这里会有读取,复制,模板,重置4个选项。
读取完后不用重启就可以马上工作了。
复制就是把现有模型设置拷贝到另一个模型文件,模板是控自带的设置模板,里面已经有一些预先调好的参数,重置就是格式化~~这个模型文件恢复出厂设定模型类型那个选项可以选择固定翼跟直升机,如果选择直升机的话可以按ent 进入进行斜盘设置跟斜盘的混控比率调节功率调节,越大就越远(傻子都懂),原厂最大好像是100mw,华科尔提供的小日本版本固件的最大10mw。
- 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。
DEVIATION说明书第一版前言年初购入devo10,那个论坛成为神控的遥控器。
神控处了这个控的硬件可圈可点外,最重要的一点就是刷入deviation(官网,英文的)这个固件后兼容dsm2等多种主流的制式,实现一控多种接收共用。
而且其开放的平台,能够不断升级增加功能,更有suv等大大的不断奉献,至此deviation 版本走了3.1版,链接/thread-241130-1-1.html感谢各位模友大大的无私奉献,我有幸用上这个神器。
经过一番专研,翻阅说明书后终于大概了解如何设置和运用,deviation的自由度很高,各个通道均可以自定义,让你打造属于自己的控,用起来随心所欲。
里面的混控器是属于底层的混控,自由度很高,不过的确需要一段时间来理解,如果学会了会觉得很好用的,想怎混就怎混。
由于官方说明书是英文的,而且不是说得很明白,加上经常有模友问及如何设置,于是本人萌生出写一下中文说明书的念头,再加点应用例子,务求各位模友更易明白上手,而且通过大家的讨论还能加深本人对这个固件的认识,达到共同进步的目的。
一下都是本人自己的认识跟见解,如有问题请提出来大家切磋讨论。
hilitiQ群:2954863552013年8月22日主界面这个是开机后的主界面,在这里吐槽一下我见过的devo10屏幕贴上都是有灰的,难道厂里贴膜的那个车间就在矿里?至少这一点学一下天地飞吧,出厂膜漂亮得很。
以下是菜单设置,首先是主菜单,这个没什么好说的,很简单明白通用模式进入模型设置,如果之前接触过遥控的话,这些名词也是很清楚明白的,如果还没有搞明白的话,潜水去吧骚年~~好了,现在进入模型设置里面的模型设置菜单(控上是这样写的,不要怪我),第一个模型文件那里,看到黑色部分左右会有箭头的是可以进行左右选择,这里会有读取,复制,模板,重置4个选项。
读取完后不用重启就可以马上工作了。
复制就是把现有模型设置拷贝到另一个模型文件,模板是控自带的设置模板,里面已经有一些预先调好的参数,重置就是格式化~~这个模型文件恢复出厂设定模型类型那个选项可以选择固定翼跟直升机,如果选择直升机的话可以按ent 进入进行斜盘设置跟斜盘的混控比率调节功率调节,越大就越远(傻子都懂),原厂最大好像是100mw,华科尔提供的小日本版本固件的最大10mw。
官网有下载,喜欢的可以去试一下。
教练功能暂缺,没有试过,不会用也就不会教了,见谅。
欢迎补充。
再下面是重点功能之一,通讯协议选择,可以选devo,wk系列,dsm2,ppm 等,选择好对应的协议后对频前把固定id吗那个删掉,我知道的devo接收不删掉是对不上频的。
玩模拟器用ppm模式。
设置界面会有通用模式,高级1,高级2选择,各界面的功能大部分都是共用的,也就是大部分功能你用哪种界面都能设置,只是位置跟设置方式不一样。
喜欢用那个界面就随便了,反正习惯就好。
这里有一个疑问,从高级界面调到通用界面的时候有时候会提示“无效的通用模型设置,是否重设”,选确定的话会有些设置恢复到初始设定,例如飞机类别,通道顺序,所以这个选项一定要小心,我试过调机时按确定后油门马上上来了,幸好是涵道机,否则就会光荣负伤了。
这个是通用模式的舵量/曲线菜单,第一项是通道选择,副翼,升降,方向,往下依次是各个飞行模式下的舵量曲线调节,飞行模式的切换默认是右边角的fmod开关。
通用模式下的混控菜单输入是指信号的输入通道,只可以是摇杆,开关通道,这里有一点,开关通道会有AIL DR0,AIL DR1这些,意思是AIL这个开关在0的位置上,AIL DR0这个输入会是100,而AIL DR1输入是-100,如果AIL开关在1位置上,AIL DR0的输入是-100,AIL DR1输入是100。
也可以这样理解,开关在哪个位置,哪个位置的输入就是100,相同开关的其他位置输入则是-100,刚接触的朋友可能要花点时间理解。
因为一个开关可以映射成2个甚至3个输入通道。
输出通道就是指信号混控后的输出通道,很好理解开关就是指这个混控生效的开关,无就是指一直生效。
保存后到这个界面,曲线有两段跟9点两种。
两段就是把输入信号从0点分开,负数就固定输出一个值,正数就输出另一个值。
屏幕第一行显示输入通道跟输出通道的名称还有相对应的数值。
9点曲线就跟舵量曲线差不多了,可以设置混控的比率,而且比率可以随便调节,不像两段曲线那样是固定的值了。
那个坐标横轴代表输入通道,纵轴表示输出通道,黑点表示当前的位置。
这里输入通道是副翼,我打一下副翼摇杆,坐标点就跟随运动,注意屏幕第一行数值的变化定时器有3种,倒计时是可以设置提醒功能的,差不多了就会响跟振动,秒表跟持续计时的确别好像是秒表能清零(倒计时跟秒表在主界面时按右边的L键就会清零),且持续计时关控再开是不会清零的,清零要到计时器那里按重置。
定制主页面微调有4内,4外,6微调显示,是指微调那个指示器位于主界面的位置。
6微调多出来的2个微调项是什么,我至今仍未搞明白,望赐教。
第一至第八栏就是显示一些通道信息,回传信息,定时器之类的,如果5-8不设置的话右边会显示飞机的图标,如果有设置的话飞机图标就没了,那个位置就显示5-8项的内容。
开关那里可以自己选择需要显示的开关跟对应状态的图标,进去选择菜单那里,up,dn按钮选择开关的状态,L,R按钮选择对应状态的图标。
还有补充一点,那个尾舵的意思是指GEAR那个开关。
刚开始我也搞不懂,什么尾舵0,尾舵1。
就是指GEAR的0跟1状态。
快捷菜单是指屏幕在主菜单时,长按up或者dn键就会直接弹出快捷菜单了,方便大家调用一些常用的设置界面。
高级模式1这里开始就是介绍高级模式1的菜单了首先是混控功能,高级菜单1的混控功能是以输出通道为菜单的,例如升降通道,1-升降那里是调节升降通道的基础参数,如:正反转,内微调,舵机行程等,后面多段式那个是调节混控的,进去后会有:无,一段式,三段式,多段式,ccpm1-3等选择。
本人未曾使用过这个混控,所以不便教授大家。
希望会用的人补充。
高级模式1的微调,我这里拿出来说是因为我发现有一个特别的功能。
有模友说刷固件后微调好像不起作用。
其实微调作用是有的,只是微调的幅度太小了,一直微调打到底行程仍然未够,如果觉得微调幅度小的朋友吧这个微调幅度调大,我习惯调到0.5,就会发现微调好很多了。
高级模式2混控我这个比较上手,就拿这个来说,左边的通道是输出通道,devo接收对应的是升降,副翼,油门方向;dsm2接收对应的是油门,副翼,升降,方向。
所以如果换接收类型后需要调整通道顺序。
右边的是现在该通道对应的输入,下图是devo接收的默认输入顺序。
选择通道1,进入混控菜单。
默认是有几个混控菜单的,那个是大小舵用的,不喜欢可以删掉。
这里新建一个混控,出现下图的界面,输入通道是指这个通道(下图是指通道1,devo接收的升降通道)的信号源通道,可以是摇杆,开关,也可以是其他输出通道,例如通道2。
为什么会有通道2,后面再用例子讲解。
输出通道是固定的,不能更改,要更改输出通道就请回上一级菜单。
开关是指这个混控生效的开关。
Ccpm应该是直升机斜盘的混控,我没试过。
保存后会到下图的界面,输入,开关也可以重新更改曲线是指混控的比例,有等比例,固定,上下限等很多种,具体要看用途选择作用有替换:如果这个通道上存在其他混控的话,只运行这个混控,其他的失效。
相乘:通道的输出值会是这个混控的值跟上一个混控的值相乘。
附加:通道的输出值是这个混控的值加上上一个混控的值。
最大:通道的输出值取这个混控跟上一个混控的最大那个。
最小:通道的输出值取这个混控跟上一个混控的最小那个。
I/O:实时显示输入跟输出的值是否微调:是的话,输入信号的微调也会应用于输出信号上,否的话,输入信号微调并不影响输出信号。
比例:输入跟输出信号的比率,需要结合曲线,正数是正比例,负数是反比例偏移:整个混控曲线往一个方向移动。
例如:等比例的曲线,比例为50,不偏移的情况下I是-100,0,100 对应的O的值是-50,0,50。
如果偏移25,那么相同的I值对应的O值是-25,0,75。
速率:舵机动作的快慢,0是不改变速率,1舵机动作最慢,250动作最快关于虚拟通道:个人理解,虚拟通道应该是作为混控的一个中间通道来使用,由于虚拟通道并没有实际输出,他的输出值只能是作为其他实体通道的输入数值来使用,也就是两个混控叠加的使用使用的。
我的飞机还没有这么高级别去使用虚拟通道混控啊。
有使用例子的请告诉我。
Devo接收通道2对应副翼的摇杆,那么混控输入选副翼跟选通道2有什么不同呢?这里举一个例子:某飞机的升降舵是分左右两个舵面的,需要2只舵机控制,这两个舵机接的通道1跟通道5,通道5混控通道1来实现。
由于2个舵机安装位置限制,只能采取反向信号,也就是通道1跟通道5的比例需要-100,通道1值是100时通道5的值是-100。
如果用升降作为通道5的输入的话,正常情况下没有问题的。
但如果升降进行微调的话,比如调高10,那么通道1跟通道5都是同时调高10,注意:通道5也是调高10,微调并没有应为通道5跟升降的-100比例而成为微调-10。
这样通道1微调后中位会是10,而通道5也是10。
当通道1满舵数值最大时110(100+微调10),通道5的数值是-90(-100+10)。
具体就是按微调的话左右两个舵面并不会同时上升或下降,而是错开,微调越多,错开越多了。
如果用通道1作为通道5的输入的话,那么通道1微调10后的值是10,通道5跟通道1比例是-100,这样通道5的值会是-10。
满舵时通道1的值是110,对应的通道5的值是-110。
具体就是左右舵面微调时会同时上升跟下降了。
这个例子说明了,微调的数值并不会因为混控的关系而改变,而是单独附加在混控后的数值上的。
通道基本设置的菜单,没什么好说的,只有一点,那个通道2前的感叹号表示的是这个通道是反的。
调整通道顺序,up,dn键调左边,r,l键调右边。
那个通道数表示的是输出的通道,也就是接收机的通道,括号那个是输入信号的通道。
下图表示接收机的1,2通道都是接收副翼的信号。
左边中间那个通道1是指要被复制的输出通道,例子:如果通道1需要改为油门通道作为输入,那么可以把右边光标移到油门,按一下通道1下面的复制,那么通道1的输入就会变成油门了。
不过这样做的话通道1本来的输入通道会没有了。
如果你只想调整通道顺序的话就不要用复制,直接上移下移就可以了。
调好顺序后记得按保存才会生效,不保存退出的话就是白干了。
后话好了,写了这么多,本人懂的已经是奉献完毕了。
不懂的,不对的还望大家赐教。
遥控的设置部分比较通俗易懂,暂不打算写说明了。
不明白的同学潜水去吧。
或者问我也是可以的,我会知无不言,言无不尽。
这是第一版,赶了个晚上搞出来的。