OpenStage HFA_SIP_Data Sheet_Issue 8
Digi ESP for Python 用户指南说明书
Quick Note 059Use Digi ESP for Python on a TransPort router to upload PPP Stats to Digi Remote Manager as DataPoints.19 September 20171 Introduction (3)1.1Outline (3)1.2Assumptions (4)1.3Corrections (4)1.4Version (4)2 Digi ESP For Python Installation (5)3 Digi ESP Configuration (6)3.1 Device Manager Configuration (6)3.2 Create a new Project (8)3.3 Download and Copy the PPP Stats device (10)4 Configure Digi ESP Project (13)4.1 Add the new PPP stats device in the project (13)5 Run DIA Project on the TransPort Router (15)6 Verify DATA STREAMS on Remote Manager (18)7 Notes (19)1.1OutlineThis document will describe how to push mobile statistics (ppp stats) as Data Points to Remote Manager using Digi ESP for Python. The example will use the PPP statistics but most other values can be used by modifying the driver. This will be described in the document.The PPP statistics consist of the cellular mobile data IN and OUT combined. This is useful to show the amount of cellular data used by a device.Please note: The document will assume that a Remote Manager account has previously been created and a Digi TransPort router has been added to this account.To create a developer test account on Remote Manager, please use the following URL:/For help on configuring a Digi TransPort router for Remote Manager, please visit the following page: /articles/Knowledge_Base_Article/Configuring-a-Digi-TransPort-router-for-Remote-Manager-connectivity-Web-User-Interface-WebUI-method1.2AssumptionsThis guide has been written for use by technically competent personnel with a good understanding of the communications technologies used in the product and of the requirements for their specific application.This quick note applies only to:Model: Digi TransPort WR11, WR21, WR31, WR441.3CorrectionsRequests for corrections or amendments to this documentation are welcome and should be addressed to: *********************Requests for new quick notes can be sent to the same address.1.4VersionDownload Digi ESP for Python from the Digi Support Web site:https:///support/productdetail?pid=3632&type=driversStart the installation and follow the instructions on the screen.When requested to select the “workspace” make sure to note the location as it will be required to navigate to that directory in the next steps.3.1Device Manager ConfigurationStart Digi ESP for PythonOn the top toolbar, click on Device Options and click Device ManagerClick on New Remote ConfigurationEnter a name for this configuration, in this example, a TransPort WR21 will be used so “WR21” is used for Name.Chose TransPort WR21 for the device type and Local Area Network for the Connection ModeUnder LAN Connection, enter the IP Address of the TransPort router.Under Authentication, enter the username and password for this device. By default, “username/password”Please note: It is possible to do the above steps via Remote Manager by selecting “Connect to device using Device Cloud by Etherios” under the General tab.Click on Set Current3.2Create a new ProjectClick on File > New > DIA ProjectGive the project a name, in this example: PPPstatsSelect the location where this project will be saved (typically the default workspace, please note this path as it will be needed in the next step)Make sure to check the box “Include DIA source code in project”Click NextIn the next screen, select “Use Current Remote Device”Click Finish3.3Download and Copy the PPP Stats devicePlease note: Make sure to c lose Digi ESP for Python before proceeding below.Download the following python file (or copy the content shown below) and paste it into the “devices” folder on the previously created project. In this example: C:\Temp\PPPstats\src\devices\/support/documentation/ppp_stats.zipContent of the python file below to create it manually:############################################################################ # # # Copyright (c)2008, 2009, Digi International (Digi). All Rights Reserved. # # # # Permission to use, copy, modify, and distribute this software and its # # documentation, without fee and without a signed licensing agreement, is # # hereby granted, provided that the software is used on Digi products only # # and that the software contain this copyright notice, and the following # # two paragraphs appear in all copies, modifications, and distributions as # # well. Contact Product Management, Digi International, Inc., 11001 Bren # # Road East, Minnetonka, MN, +1 952-912-3444, for commercial licensing # # opportunities for non-Digi products. # # # # DIGI SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED # # TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A # # PARTICULAR PURPOSE. THE SOFTWARE AND ACCOMPANYING DOCUMENTATION, IF ANY, # # PROVIDED HEREUNDER IS PROVIDED "AS IS" AND WITHOUT WARRANTY OF ANY KIND. # # DIGI HAS NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, # # ENHANCEMENTS, OR MODIFICATIONS. # # # # IN NO EVENT SHALL DIGI BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, # # SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, # # ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF ## DIGI HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. # # # ############################################################################ # importsfrom devices.device_base import DeviceBasefrom settings.settings_base import SettingsBase, Settingfrom channels.channel_source_device_property import *from common.shutdown import SHUTDOWN_WAITimport threadingimport timeimport sarcli# constants# exception classes# interface functions# classesclass PPPStatsDevice(DeviceBase, threading.Thread):"""This class extends one of our base classes and is intended as anexample of a concrete, example implementation, but it is not itselfmeant to be included as part of our developer API. Please consult thebase class documentation for the API and the source code for this filefor an example implementation."""def __init__(self, name, core_services):self.__name = nameself.__core = core_services## Settings Table Definition:settings_list = [Setting(name='update_rate', type=float, required=False,default_value=1.0,verify_function=lambda x: x > 0.0),]## Channel Properties Definition:property_list = [# gettable propertiesChannelSourceDeviceProperty(name="pppdata", type=str,initial=Sample(timestamp=0, value=""),perms_mask=DPROP_PERM_GET, options=DPROP_OPT_AUTOTIMESTAMP,), ]## Initialize the DeviceBase interface:DeviceBase.__init__(self, self.__name, self.__core,settings_list, property_list)## Thread initialization:self.__stopevent = threading.Event()threading.Thread.__init__(self, name=name)threading.Thread.setDaemon(self, True)## Functions which must be implemented to conform to the DeviceBase## interface:def start(self):threading.Thread.start(self)return Truedef stop(self):self.__stopevent.set()self.join(SHUTDOWN_WAIT)if self.isAlive():raise RuntimeError("Could not stop %s" % self.__name)return True## Locally defined functions:# Property callback functions:# Threading related functions:def run(self):while 1:if self.__stopevent.isSet():self.__stopevent.clear()break# increment counter property:pppStats = getpppStats()self.property_set("pppdata", Sample(0,pppStats))time.sleep(SettingsBase.get_setting(self,"update_rate"))# internal functions & classesdef getpppStats():cli = sarcli.open()cli.write("at\mibs=ppp.1.dlim.totdata")ppp1totalstr = cli.read()beginningofppp1total = ppp1totalstr.find(".totdata = ")endofppp1total = ppp1totalstr.find("\n", (beginningofppp1total))ppp1total = ppp1totalstr[(beginningofppp1total+11):(endofppp1total-1)] cli.close()return ppp1totalRe-Open Digi ESP for Python4.1Add the new PPP stats device in the projectIn the Smart Project Editor, click on the Xbee Device Manager and Delete as this will not be needed.By default, the copied device will not be available.Now, click on Source to manually add the PPP stats device.In the “devices:” section, add the following:- name: pppstatsdriver: devices.ppp_stats:PPPStatsDevicesettings:update_rate: 60.0Make sure to keep the same indenting.Switch back to the “Graphic Editor”. A device named “PPPStatsDevice” should now be shown under “Devices”Please note: If Digi ESP shows an error message when switching back to the Graphic Editor, this is because the indenting has not been kept properly. Make sure to use only spaces and not tabs.Click on Run > Run As > Remote DIAThe left panel will show a progress barOnce the router has rebooted, the following will be displayed:In the URL bar on the center page, change the url to point to:/idigi_dia.htmlIn this example, http://192.168.1.22/idigi_dia.htmlThis will show the DIA Web presentation which is a simple web page showing the ppp stats value.The Right panel shows a Telnet Command Line interface allowing the user to see the CLI output of the same information shown on the web page. This is done by issuing a “channel_dump” command:Welcome to the Device Integration Application CLI.=>> channel_dumpDevice instance: edp_upload0Channel ValueUnit Timestamp------------------------ -------------------------- -------------------upload_samples (N/A)upload_snapshot (N/A)Device instance: pppstatsChannel ValueUnit Timestamp------------------------ -------------------------- -------------------pppdata 02017-06-21 09:20:40=>>Please note: For the value to increase and new data to be uploaded, the router must have a SIM card inserted and be configured to establish a cellular connection.The PPPstats Console is a debugging console showing the python’s script activity. Every 60sec (default value) it will show a message that data has been uploaded to Remote Manager:DEBUG:edp_upload0:Output List (1): {'pppstats.pppdata': (<type 'str'>, [<Sample: 0 at 2017-06-21T09:23:40Z>])}DEBUG:edp_upload0:<?xml version="1.0"?><idigi_data compact="True" version="1.1"><sample name="pppstats.pppdata" value="0" unit="" type="str"timestamp="2017-06-21T09:23:40Z" /></idigi_data>DEBUG:edp_upload0:Starting upload to Device CloudDEBUG:edp_upload0:Attempting to upload file_name19.xml to Device CloudDEBUG:edp_upload0:Successfully uploaded file_name19.xml to Device CloudLogin to: https:///login.do using the credentials from the created account. Navigate to Data Services > Data StreamsData Streams starting with “dia” show be shown:The “current value” field is the pppdata from the router sent by the python script.Clicking on one of the stream also allows showing this in a charts format:While this example shows the cellular data used, it is possible to modify it to use various other information.The key part of the script that actually pulls the data from the Command Line interface of the router is found at the bottom of ppp_stats.py:def getpppStats():cli = sarcli.open()cli.write("at\mibs=ppp.1.dlim.totdata")ppp1totalstr = cli.read()beginningofppp1total = ppp1totalstr.find(".totdata = ")endofppp1total = ppp1totalstr.find("\n", (beginningofppp1total))ppp1total = ppp1totalstr[(beginningofppp1total+11):(endofppp1total-1)]cli.close()return ppp1totalThis line is the CLI command sent to the router:cli.write("at\mibs=ppp.1.dlim.totdata")You can get the list of available commands on the router by issuing at\mibsThe number of character calculation as well as the characters to search for will need to be modified to suit the CLI command used.Once modified, run the project as a Remote DIA like in section 5 and the new values will be available on the DIA page as well as on Remote Manager.。
opensips 安装及基本配置
opensips 安装及基本配置.txt人生在世，难敌宿命，沉沦其中。
我不爱风尘，似被前缘误！！我只为我最爱的人流泪“我会学着放弃你，是因为我太爱你”赢了你,我可以放弃整个世界opensips 安装及基本配置1 . 官方网站 / 的 download 中下载 opensips 软件包2 . 编译：Java代码1. tar zxvf opensips-1.6.2-tls_src.tar.gz2. cd opensips-1.6.2-tlstar zxvf opensips-1.6.2-tls_src.tar.gzcd opensips-1.6.2-tls3 . 安装之前更改 makefile ：删除 Makefile 中的 exclude_modules 的 db-mysql,使opensips使用mysql数据4. 安装make all可能会缺少一下工具，缺少什么装什么就是了。
另外可能提示找不到mysql.h等文件，只要把文件拷贝到对应的地方就行了。
make install默认安装路径 /usr/local 下5. 配置 vim /usr/local/etc/opensips/opensipsctlrc，把 mysql 的相关的注释去掉Java代码1. ## database type: MYSQL, PGSQL, ORACLE, DB_BERKELEY, or DBTEXT, by default noneis loaded2. # If you want to setup a database with opensipsdbctl, you must at least specify3. # this parameter.4. DBENGINE=MYSQL5. ## database host6. DBHOST=localhost7. ## database name (for ORACLE this is TNS name)8. DBNAME=opensips9. # database path used by dbtext or db_berkeley10. DB_PATH="/usr/local/etc/opensips/dbtext"11. ## database read/write user12. DBRWUSER=opensips13. ## password for database read/write user14. DBRWPW="opensipsrw"15. ## database read only user16. DBROUSER=opensipsro17. ## password for database read only user18. DBROPW=opensipsro19. ## database super user (for ORACLE this is 'scheme-creator' user)20. DBROOTUSER="root"21. # user name column22. USERCOL="username"## database type: MYSQL, PGSQL, ORACLE, DB_BERKELEY, or DBTEXT, by default none is loaded# If you want to setup a database with opensipsdbctl, you must at least specify # this parameter.DBENGINE=MYSQL## database hostDBHOST=localhost## database name (for ORACLE this is TNS name)DBNAME=opensips# database path used by dbtext or db_berkeleyDB_PATH="/usr/local/etc/opensips/dbtext"## database read/write userDBRWUSER=opensips## password for database read/write userDBRWPW="opensipsrw"## database read only userDBROUSER=opensipsro## password for database read only userDBROPW=opensipsro## database super user (for ORACLE this is 'scheme-creator' user)DBROOTUSER="root"# user name columnUSERCOL="username"6. 执行 opensips/sbin/ 下的 opensipsdbctlJava代码1. ./opensipsdbctl create ( 生成 opensips 数据库 )./opensipsdbctl create ( 生成 opensips 数据库 )7. 这个时候如果重新登录phpmyadmin，会看到已经新建了opensips数据库8. opensips的运行Java代码1. /usr/local/sbin/下的opensipsctl start来启动opensips2. ps aux | grep opensips 检查应该已经运行了。
IMS网络AGCF技术要求V2.0-2011920
IMS 网络综合接入控制设备AGCF 技术要求Technical Requirements of AGCF in IMS（V2.0）中国电信集团公司 发布保密等级：公开发放目录目录 (1)前言 (3)IMS网络综合接入控制设备AGCF技术要求 (1)1 范围 (1)2 引用标准 (1)3 缩略语 (1)4 AGCF在网络中的位置 (2)5 业务和功能要求 (2)5.1 业务要求 (2)5.2 功能要求 (3)6 操作维护和网管要求 (7)6.1 维护界面 (7)6.2 配置管理 (7)6.3 维护管理 (7)6.4 故障管理 (8)6.5 业务量统计和测量 (8)6.6 协议跟踪与监视 (10)6.7 安全管理 (10)6.8 人-机系统 (10)7 接口要求 (10)7.1 以太网接口 (10)7.2 本地维护接口 (11)7.3 与网管中心接口 (11)7.4 端口配置要求 (11)8 协议要求 (11)8.1 H.248 协议要求 (11)8.2 SIP 协议要求 (11)9 主要通信流程示例 (11)10 性能及可靠性指标 (11)10.1 系统容量 (11)10.2 系统处理能力 (11)10.3 呼叫建立时延 (11)10.4 时延 (11)10.5 系统可靠性和可用性 (11)11 系统安全性 (12)12 定时和同步要求 (12)12.1 同步方式 (12)12.2 外定时方式 (12)13 硬件要求 (12)13.1 硬件系统基本要求 (12)13.2 对处理机的要求 (12)13.3 对输入、输出设备的基本要求 (12)14 软件要求 (12)14.1 基本要求 (12)14.2 软件功能要求 (13)14.3 软件维护管理功能要求 (13)15 机械结构和工艺要求 (13)16 环境要求 (13)17 电源及接地要求 (13)附录A（规范性附录）信令流程要求 (14)A.1 概述 (14)A.2媒体网关注册注销流程 (14)A.3 AGCF用户注册注销流程 (15)A.4 呼叫建立流程 (18)A.5 传真和MODEM处理流程 (24)A.6 补充业务实现流程 (29)附录B 接入和接入控制设备加插P-Access-Network-Info头域的要求 (29)前言本标准依据ITU-T和3GPP制定的相关标准，结合有关国内标准和中国电信其它企业标准，基于中国电信中国电信IMS总体技术要求和实际需求而拟定，充分考虑了网络的平滑演进能力，为中国电信中国电信IMS的技术试验、网络建设和运行维护提供技术依据。
H3C SIP命令
目录第1章 SIP配置命令................................................................................................................1-11.1 SIP配置命令.......................................................................................................................1-11.1.1 display voice sip call-statistics.................................................................................1-11.1.2 display voice sip reason-mapping...........................................................................1-41.1.3 display voice sip register-state................................................................................1-71.1.4 outband sip..............................................................................................................1-81.1.5 privacy.....................................................................................................................1-81.1.6 proxy........................................................................................................................1-91.1.7 reason-mapping pstn............................................................................................1-101.1.8 reason-mapping sip...............................................................................................1-121.1.9 register-enable......................................................................................................1-141.1.10 registrar ipv4........................................................................................................1-151.1.11 remote-party-id....................................................................................................1-161.1.12 reset voice sip.....................................................................................................1-171.1.13 sip........................................................................................................................1-171.1.14 sip-comp..............................................................................................................1-181.1.15 sip-comp agent....................................................................................................1-181.1.16 sip-comp server...................................................................................................1-191.1.17 sip-domain...........................................................................................................1-201.1.18 source-bind..........................................................................................................1-211.1.19 user.....................................................................................................................1-211.1.20 wildcard-register enable......................................................................................1-23第2章 SIP本地业务存活命令.................................................................................................2-12.1 SIP本地业务存活命令........................................................................................................2-12.1.1 area-prefix...............................................................................................................2-12.1.2 authentication..........................................................................................................2-22.1.3 call-route..................................................................................................................2-22.1.4 call-rule-set..............................................................................................................2-32.1.5 srs............................................................................................................................2-42.1.6 display voice sip-server register-user.....................................................................2-52.1.7 display voice sip-server resource-statistic..............................................................2-62.1.8 expires.....................................................................................................................2-62.1.9 mode.......................................................................................................................2-72.1.10 number..................................................................................................................2-82.1.11 probe remote-server..............................................................................................2-92.1.12 register-user..........................................................................................................2-92.1.13 trunk....................................................................................................................2-102.1.14 rule......................................................................................................................2-112.1.15 service.................................................................................................................2-122.1.16 server-bind ipv4...................................................................................................2-132.1.17 server enable.......................................................................................................2-14 2.1.18 sip-server.............................................................................................................2-15 2.1.19 trusted-point........................................................................................................2-15本文中标有“请以实际情况为准”的特性描述，表示各型号对于此特性的支持情况可能不同，本节将对此进行说明。
ISaGRAF PAC FRnet AI AO模块使用说明说明书
How to use the FRnet AI/AO module with the ISaGRAF PACIntroduction ：It is a document about how to read/write the status of FRnet AI(FR‐2024iT)/AO(FR‐2017iT) module with the ISaGRAF PAC.The following ISaGRAF driver supports to operate the FRnet AI/AO moduleThe link to download this document and demo programs :https:///en/faq/index.php?kind=280#751 > FAQ‐154 .The link to download ISaGRAF drivers :/en/download/show.php?num=368&nation=US&kind1=&model=&kw=isagraf The product data sheet:/en/download/index.php?nation=US&kind1=6&kind2=15&model=&kw=isagraf More information about I‐8172W and FRnet I/O module: /en/product/I‐8172W/en/product/guide+Remote__I_O__Module__and__Unit+FRnet__I_O__Modules +The FAQ about how to operate the FRnet DI/DO module with the ISaGRAF PACISaGRAF PAC VersionWP‐8xx7/8xx6 1.48VP‐25W7/23W7/25W6/23W6 1.40XP‐8xx7‐CE6/XP‐8xx6‐CE6 1.28Restore the demo project “faq154.pia” :1342123 45 61.2. Introduction of FR‐2017iT:●Hardware description:The FR‐2017iT is a 16‐bit (1 channel) and 12‐bit (8‐channel differential or 16‐channel single‐ended) analog inputs module that provides two ways to select input range (+/‐150mV, +/‐500mV, +/‐1V, +/‐5V, +/‐10V, +/‐20mA, 0~20mA and 4~20mA).The refresh rate by each channel status is different, due to the channel mode of the FRnet module.The refresh rate of one channel mode is 100ms/time. The refresh rate of 8 channel mode is250ms/time. The refresh rate of 16 channel mode is 500ms/time. But the refresh rate is notchanged when add more and more modules to the FRnet bus.More detail description about FR‐2017iT, please refer to the following website:/en/product/FR‐2017iT●Hardware setting:●SW1 : The SW1 can be used to configure the module to 8‐ch differential/16‐ch single‐ended,12/16‐bit resolution and individual/all Channel mode.Pin1 Pin2 Pin3 Type code: 000~111, for +/‐500mV, +/‐1V, +/‐5V, +/‐10V+/‐20mA (requires optional external 125ohm resistor)Pin4 SE/DF ON→16 Single‐endedOFF→8 DifferentialPin5 Resolution ON→16‐bitOFF→12‐bitPin6 Configuration ON→Software SelectableOFF→Switch SelectableType SW1 Min Max1 2 30 ~ 20mA ON ON ON 000 (0mA) FFF (20mA)4 ~ 20mA OFF ON ON 000 (4mA) FFF (20mA)+/‐10V ON OFF ON 800 (‐10V) 7FF (+10V)+/‐5V OFF OFF ON 800 (‐5V) 7FF (+5V)+/‐1V ON ON OFF 800 (‐1V) 7FF (+1V)+/‐500mV OFF ON OFF 800 (‐500mV) 7FF (+500mV)+/‐150mV ON OFF OFF 800 (‐150mV) 7FF (+150mV)+/‐20mA OFF OFF OFF 800 (‐20mA) 7FF (+20mA)Dip switch: The dip switch can be used to configure the module address and the speed of FRnet bus.Wire connection:The wiring of 8‐ch differential analog inputs The wiring of 16‐ch single‐ended analog inputsHardware setting:The SW3 can be used to configure the output type or enable/disable the safe value mode.Type code: 000~111, for 0~20mA, 4~20mA, 0~5V, +/‐5V, 0~10V, +/‐10VTypeSW3Min Max 1 2 30 ~ 20mA ON ON ON 000 (0mA) FFF (20mA)4 ~ 20mA OFF ON ON 000 (4mA) FFF (20mA)0V ~ +10V ON OFF ON 000 (0V) FFF (+10V)‐10V~+10V OFF OFF ON 800 (‐10V) 7FF (+10V)0V ~ +5V ON ON OFF000 (0V) FFF (+5V)‐5V ~ +5V OFF ON OFF800 (‐5V) 7FF (+5V) Dip Switch : The dip switch can be used to configure the module address and the speed of FRnet bus.LED MappingPWR Power LEDRUN Communication Run LEDERR Communication Error LEDEND Terminal resistor OnSW2 SwitchInt.pwr Internal PowerExt.pwr External PowerDIP SwitchPin1 Module Address:0~7Pin2Pin3Pin4 ReservedPin5 ReservedPin6 ReservedPin7 Speed:ON → 250k bpsOFF→ 1M bpsPin8 ReservedCOM0Each analog channel is allowed toconfigure an individual range by CA‐0904cable.Wire connection:SW2: it can be use to set the module using internal or external power.The connection of internal power: The connection of external power:1.4. The description of C‐function block “fr_16ai”:●Parameter：Name Type descriptionSlot_ integer The slot which plugged the I‐8172W related to the FRnet AI.WP‐8xx7: max. 8 pcs. of I‐8172W; can be slot 0~7VP‐25W7/23W7: max. 3 pcs.; can be slot 0~2XPAC‐8xx7: max. 7 pcs.; can be slot 1~7Port_ integer The I‐8172W port that link to the FRnet AI (0 or 1 )Addr_ integer Module address. AI module: 8 ~ 15Type_ integer Set up the output type:16#00 : ‐15mV→+15mV ( Val is ‐32768 to 32767 )16#01 : ‐50mV→+50mV ( Val is ‐32768 to 32767 )16#02 : ‐100mV→+100mV ( Val is ‐32768 to 32767 )16#03 : ‐500mV→+500mV ( Val is ‐32768 to 32767 )16#04 : ‐1V → +1V ( Val is ‐32768 to 32767 )16#05 : ‐2.5V → +2.5V ( Val is ‐32768 to 32767 )16#06 : ‐20mA → 20mA ( Val is ‐32768 to 32767 ),with 125 ohm16#07 : 4mA → 20mA ( Val is 0 to 32767 ), with 125 ohm16#08 : ‐10V → 10V (Val is ‐32768 to 32767 )16#09 : ‐5V → 5V (Val is ‐32768 to 32767 )16#0A : ‐1V → 1V (Val is ‐32768 to 32767 )16#0B : ‐500mV → 500mV (Val is ‐32768 to 32767 )16#0C : ‐150mV → 150mV (Val is ‐32768 to 32767 )16#0D : ‐20mA → 20mA (Val is ‐32768 to 32767 )16#1A : 0mA → 20mA ( Val is 0 to 32767 ), with 125 ohm IN1_~IN16_ integer The related variable names of the 16 AI channels.Please declare a "Dump_ai" integer internal variable name andassigned it to those none‐using channels.＊ Please do not assign the constant to the none‐using channels.●ReturnName Type DescriptionQ_ Boolean Always return True.1.5. The description of C‐function block “fr_8ao”:●Parameter：Name Type DescriptionSlot_ integer The slot which plugged the I‐8172W related to the FRnet AO.WP‐8xx7: max. 8 pcs. of I‐8172W; can be slot 0~7VP‐25W7/23W7 : max. 3 pcs.; can be slot 0~2XPAC‐8xx7: max. 7 pcs.; can be slot 1~7Port_ integer The I‐8172W port that link to the FRnet AO (0 or 1)Addr_ integer Module address. AO module: 0~7Type_ integer Set up the output type:16#30 : 0mA ‐‐‐> 20mA ( Val is 0 to 32767 )16#31 : 4mA ‐‐‐> 20mA ( Val is 0 to 32767 )16#32 : 0V ‐‐‐> 10V ( Val is 0 to 32767 )16#34 : 0V ‐‐‐> 5V ( Val is 0 to 32767 )16#33 : ‐10V ‐‐‐> 10V ( Val is ‐32768 to 32767 )16#35 : ‐5V ‐‐‐> 5V ( Val is ‐32768 to 32767 )Out1_~Out8_ integer The related variable names of the 8 AO channels.Please declare a "Dump_ao" integer internal variable name andassigned it to those none‐using channels.＊ Please do not assign the constant to the none‐using channels.●ReturnName Type DescriptionQ_ Boolean Always return true●Notice about using FRnet AI/AO module:Fast I/O scan, it is about 3 ms per FRnet I/O scan. But it can be only got one channel status per scan.(This depends on your program’s PLC scan time, for ex, if the ISaGRAF PLC program scan time is about 15 ms, then the scan time for one AI/AO channel will be 15 ms, not 3 ms.)FR‐2017iT/FR‐2024iTSet the bus speed of FR‐2017iT,FR‐2024iT as 1MIn the same bus, the speed of the FRnet modules must be the same. Or the communication between module and module will not work.)FR‐2017iT FR‐2024iTHow to operate the demo project FAQ1541.Recompile the ISaGRAF project and download it into the ISaGRAF PAC. If you are not familiar tothe ISaGRAF software, please refer to “ISaGRAFUser’s manual” Chap.1.1~1.2 and Chap.2. canbe got from the following website./en/download/show.php?num=333&nation=US&kind1=&model=&kw= isagrafer can observe the change of AO_voltage_1~4 and AI_voltage_1~4 from +10V to +10V inthe spy list, just like the figure below.1.7. Description of Demo Program “faq154”● ISaGRAF Project Architecture ：This project contains two LD programs(LD1、timer_tr), an ST program(ST1), and two User define C‐function(eng_To_V 、V_To_eng)● The setting of FRnet module in this demo project● ISaGRAF variablesName Type Property DescriptionInit Boolean InternelSet to true at Init, for initializing the FRnet module AI_connection Boolean InternelThe connection status of FRnet AI module AO_1_event Boolean InternelThe event to change the status of AO1 AO_2_event Boolean InternelThe event to change the status of AO2 AO_3_event Boolean InternelThe event to change the status of AO3 AO_4_event Boolean InternelThe event to change the status of AO4 AI_01~AI_04 Integer InternelThe AI status of FR‐2014iT Dump_AI Integer InternelTo connect the none‐using channels of FRnet AI module AO_01~AO_04 Integer InternelThe AO status of FR‐2017iT Dump_AO Integer InternelTo connect the none‐using channels of FRnet AO module AI_voltage_1~4 Real Internel The status of AI channel. The unit is volt .AO_voltage_1~4 Real InternelThe status of AO channel. The unit is volt T1 Timer InternelSet to 500ms at init, for generating the pulseFR‐2017iT FR‐2024iT Address 1 2 Type +‐10V(ON OFF ON) +‐10V(OFF OFF ON) Speed 1M bps 1M bpsAssign the variable“AI_connection” to thesecond channel, forgetting the status of theconnection.The description of “LD1” program：(* Set the variable “INIT” as false in the first scan, *)(* for initializing the FRnet modules. *)(* Please do not use the C function block “Fr_16ai” and “Fr_8ao”(* in the other program. *)(* Do not use the array variable in the C‐function block “FR_8ao” *)(* and “FR_16ai”. *)Attention：Please declare a "Dump_ai" integer internal variable name and assign it to those none‐using channels.Please do not assign the constant to the none‐using channels.Attention：Please declare a "Dump_ao"integer internal variable name and assignit to those none‐using channels.Please do not assign the constant to thenone‐using channels.The description of “timer_tr” program：AO_voltage_1 := AO_voltage_1 + 0.01;if AO_voltage_1 > 10.0 thenAO_voltage_1 := ‐10.0;AO_01 := V_To_eng(AO_voltage_1);(* while getting the trigger event of AO channel2, add 0.05V to it *) (* If its value is over +10V, set it as ‐10V *)if AO_2_event thenAO_voltage_2 := AO_voltage_2 + 0.05;if AO_voltage_2 > 10.0 thenAO_03 := V_To_eng(AO_voltage_3);(* while getting the trigger event of AO channel4, add 0.5V to it *) (* If its value is over +10V, set it as ‐10V *)if AO_4_event thenAO_voltage_4 := AO_voltage_4 + 0.5;if AO_voltage_4 > 10.0 thenAO_voltage_4 := ‐10.0;AO_04 := V_To_eng(AO_voltage_4);Classification ISaGRAF English FAQ‐154 Author Grady Dun Version 1.0.0 Date Aug.2012 Page21 / 21。
opensearch-best-practice-cn-zh-2020-11-05说明书
开放搜索最佳实践1.2.最佳实践功能篇相关性实战分词、匹配、相关性、排序表达式针对目前若干用户遇到的搜索结果与预期不符合的问题进行统一详细说明，并以此为话题展开说明下OpenSearch在搜索效果方面的功能和后续一些工作方向。
首先，对于搜索来讲，最常见的有两种做法：数据库的like查询，可以理解为简单的包含关系；百度、google等搜索引擎，涉及到分词，将查询词根据语义切分成若干词组term（这个是搜索引擎重难点之一），通过term组合匹配给相应文档进行打分，根据分值排序，并最终返回给用户。
OpenSearch采用的方式与上述搜索引擎做法基本一致。
那这里就有三部分内容会影响搜索效果：1，分词方式；2，匹配方式；3，相关性算分。
我们来分别说下这三部分在OpenSearch上的行为和表现。
接下来，我们详细说明下各个字段的展现效果及适用场景，供大家参考。
分词方式 熟悉各类分词是本篇操作的前提，请务必先查阅 内置分析器 文档。
匹配方式原理分完词后得到若干term，如何召回文档，就涉及到匹配方式。
目前OpenSearch内部默认支持的是AND，即一篇文档中包含全部的term才能被搜索出来。
当然这是对同一关键词而言的，除此之外系统还支持多种匹配方式，如AND、OR、RANK、NOTAND以及()，优先级从高到低为()，ANDNOT，AND，OR，RANK。
举例案例问：我文档中包含“吃饭了”，我搜索“吃饭”、“吃饭了”都能召回，搜索“吃饭了吗”没结果？答：因为目前OpenSearch是要求全部的分词结果都匹配才能召回文档，上面的“吗”在文档中没有出现，所以无法召回。
但可以通过查询分析解决。
问：我只想查找某些词排在最前面的文档，比如以“肯德基”开头的文档；答：目前不支持位置相关召回。
相关性算分上面提到的都是跟召回相关的技术，召回文档之后，究竟文档如何排序就涉及到相关性。
目前OpenSearch有sort子句来支持用户自定义排序。
opensips安装及配置
一、opensips安装1.更新系统yum –y updateyum install gcc makeyum install flex bison ncurses libncurses-dev ncurses-devel yum install mysql mysql-server mysql-libs mysql-devel2.将安装包放入/var/local目录下面3.tar –zxvf opensips-1.9.1_src.tar.gz4.cd opensips-1.9.1-tls5. make menuconfig如图：往下执行选择mysql数据库模块制定安装目录 /usr/local/opensips_proxy/如上图：红色部分为指针选择，蓝色部分为指定程序安装目录提示：程序安装目录最好指定到公共文件目录中，据测试放到用户目录中，启动会出问题，个人出现过BUG，故作此提示配置完成之后需要对配置进行保存，如下图最后在主菜单里选"Compile And Install Opensips"安装时界面如下：出现上图内容部分表示安装已经成功完成，配置完成之后需要对配置进行保存，。
二、opensips-cp安装1. yum install httpd php php-mysql php-xmlrpc php-pearpear install MDB2pear install MDB2#mysqlpear install MDB2#mysqlipear install log2. 将opensips-cp_5.0.tgz上传opensip-cp到/var/www目录中tar zxvf opensips-cp_5.0.tgzmv 5.0 opensips-cp3.检查M4是否安装yum install m4三、stop-daemon安装将apps-sys-utils-start-stop-daemon-IR1_9_18-2.tar.gz安装包放入/var/local目录下面，并执行下列命令yum install gcc gcc-c++ m4 make automake libtool gettext openssl-develtar xvfz apps-sys-utils-start-stop-daemon-IR1_9_18-2.tar.gzmv apps/sys-utils/start-stop-daemon-IR1_9_18-2/ ./rm -rf appscd start-stop-daemon-IR1_9_18-2/gcc start-stop-daemon.c -o start-stop-daemoncp start-stop-daemon /usr/sbin/四、opensips配置1.进入sbin目录，并配置cd /usr/local/opensips_proxy/sbin/./osipsconfig进入Generate OpenSIPS Script-> Residential script->Configure Residential Script最后选择Generate Residential Script，保存之后再退出。
西门子HiPath 4000
通信无界限上海西门子数字程控通信系统有限公司/open400024000150080400040003004000HiPath 8000HiPath 2000HiPath 4000生产率HiPath ComAssistant联系中心HiPath ProCenter状况HiPath OpenScape会议配置警报通信HiPath XpressionsOpenStageoptiPointDECToptiClientVoWLANDECTAC-Win IP手机连接桌面工作效率OpenStage OpenStage 系列具有直观的功能和GUI 界面，可与其他设备进行交互操作，并且通过其多模态特性，可访问各种有线和无线服务及应用。
OpenStage 系列具有出色的用户友好设计，并简化了功能的实现。
基于先进技术解决方案的感知界面（触摸键、嵌入式彩色LED 、用于音量控制的TouchSlider 和TouchGuide 导航器）以及使用TFT 技术的大屏幕背光彩色图形显示器方便了用户交互。
可对贴有软标签的触摸键进行轻松编程，以实现特定话机功能，线路/功能访问或按姓名速拨。
通过固定的功能按键（如掉话/释放、重拨、呼叫转移、静音、扬声器）和专用触摸功能键（如电话呼叫视图、电话号码簿、呼叫日志、消息等待，应用程序），可轻松访问需频繁使用的话机功能。
OpenStage 使用最先进的声学技术，确保传递的声音质量最佳（G.722宽带编解码器支持手柄、扬声器和耳机通信）。
所有型号话机按标准内置一个高质量扬声器。
HiPath 4000 V5支持各个OpenStage 系列：OpenStage T(TDM)、OpenStage HFA (HiPath Feature Access)和OpenStage SIP (功能减少)。
OpenScape 个人版 (用于HiPath 4000)HiPath ComScendo 软件组合为HiPath 4000集成系统提供了一整套企业级通信功能。
Silicon Labs 芯片评估板 套件说明书
EVALUATION BOARD/KIT IMPORTANT NOTICESilicon Laboratories Inc. and its affiliated companies ("Silicon Labs") provides the enclosed evaluation board/kit to the user ("User") under the following conditions:This evaluation board/kit ("EVB/Kit") is intended for use for ENGINEERING DEVELOPMENT, TESTING, DEMONSTRATION, OR EVALUATION PURPOSES ONLY and is not a finished end-product fit for general consumer use. ANY OTHER USE, RESALE, OR REDISTRIBUTION FOR ANY OTHER PURPOSE IS STRICTLY PROHIBITED. This EVB/Kit is not intended to be complete in terms of required design-, marketing-, and/or manufacturing-related protective considerations, including product safety and environmental measures typically found in end products that incorporate such semiconductor components or circuit boards. As such, persons handling this EVB/Kit must have electronics training and observe good engineering practice standards. As a prototype not available for commercial reasons, this EVB/Kit does not fall within the scope of the European Union directives regarding electromagnetic compatibility, restricted substances (RoHS), recycling (WEEE), FCC, CE or UL, and therefore may not meet the technical requirements of these directives or other related directives.Should this EVB/Kit not meet the specifications indicated in the User's Guide, the EVB/Kit may be returned within 30 days from the date of delivery for a full refund. THE FOREGOING WARRANTY IS THE EXCLUSIVE WARRANTY MADE BY SILICON LABS TO USER, IS USER'S SOLE REMEDY , AND IS IN LIEU OF ALL OTHER WARRANTIES, EXPRESSED, IMPLIED, OR STATUTORY , INCLUDING ANY WARRANTY OF MERCHANTABILITY , NONINFRINGEMENT, DESIGN, WORKMANSHIP , OR FITNESS FOR ANY PARTICULAR PUR-POSE.User assumes all responsibility and liability for proper and safe handling of the EVB/Kit. Further, User indemnifies Silicon Labs from all claims arising from User's handling or use of the EVB/Kit. Due to the open construction of the EVB/Kit, it is User's responsibility to take any and all appropriate precautions with regard to electrostatic discharge.EXCEPT TO THE EXTENT OF THE INDEMNITY SET FORTH ABOVE, NEITHER PARTY SHALL BE LIABLE TO THE OTHER FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CON-SEQUENTIAL DAMAGES.Neither Silicon Labs nor User is obligated to perform any activities or conduct any business as a consequence of using the EVB/Kit, and neither party is entitled to any form of exclusivity with respect to the EVB/Kit.Silicon Labs assumes no liability for applications assistance, customer product design, software performance, or infringement of patents or services described herein.Please read the User's Guide and, specifically, the Warnings and Restrictions notice in the User's Guide prior to handling the EVB/Kit. This notice contains important safety information about temperatures and voltages. For additional environmental and/or safety information, please contact a Silicon Labs application engineer or visit /support/quality.No license is granted under any patent right or other intellectual property right of Silicon Labs covering or relating to any machine, process, or combination in which the EVB/Kit or any of its components might be or are used.User's use of this EVB/Kit is conditioned upon acceptance of the foregoing conditions. If User is unwilling to accept these conditions, User may request a refund and return the EVB/Kit to Silicon Labs in its original condition, unopened, with the original packaging and all documentation to:Mailing Address:400 W. Cesar Chavez Austin, TX 78701Copyright © 2012 by Silicon Laboratories Rev. 0.2 7/12P R E C I S I O N 32™ M C U D E V E L O P M E N T K I T Q U I C K -S T A R T G U I D E F O R K I T S F E A T U R I N G T H E U N I F I E D D E V E L O P M E N T P L A T F O R M (U D P )T h e P r e c i s i o n 32™ M C U D e v e l o p m e n t K i t s a r e a v a i l a b l e i n a l o w c o s t D e v e l o p m e n t K i t a n d a f u l l y f e a t u r e d E n h a n c e d D e v e l o p m e n t K i t . K i t c o n t e n t s a r e d e s c r i b e d b e l o w . A l l d e v e l o p m e n t k i t s c o m e w i t h a n M C U c a r d , U S B D e b u g A d a p t e r , a n d a l l n e c e s s a r y c a b l e s a n d p o w e r s u p p l i e s n e e d e d t o e v a l u a t e h a r d w a r e a n d d e v e l o p c o d e . T h e E n h a n c e d D e v e l o p m e n t K i t s a d d i t i o n a l l y c o n t a i n a U D PM o t h e r b o a r d a n d o n e o r m o r e I /O c a r d s t o e n h a n c e t h e u s e r e x p e r i e n c e .D e v e l o p m e n t K i t•U D P M C U c a r d•S i l i c o n L a b o r a t o r i e s U S B D e b u g A d a p t e r •S u p p o r t i n g C a b l e s a n d P o w e r S u p p l i esE n h a n c e d D e v e l o p m e n t K i t•U D P M C U c a r d•U D P M o t h e r b o a r d •U D P I /O c a r d (s )•S i l i c o n L a b o r a t o r i e s U S B D e b u g A d a p t e r •S u p p o r t i n g C a b l e s a n d P o w e r S u p p l i e sA. Install SoftwareB. Hardware Setup (Steps 1, 4, and 5 Only Apply to Enhanced Development Kits)C. Documentation12Click the large Download Button to initiate the Precision32 web install.Navigate to the Precision32 software download website.3Start the Installer and allow it to run in the background. Advance to Step 4 while the Precision32 Development Suite andAppBuilder are being installed./32bit-software1Connect the USB Debug Adapter ribbon cable to the MCU card.2Connect the USB Debug Adapter to thePC using the standard USB cable.I/O cardMCU card45If Enhanced DK, apply power to the UDP Motherboard using 1 of 4 power options,Power Options1: 9 V Universal Adapter (J20)2: Standard USB (J16) 3: Mini USB (J1)4: 6 V Battery Pack (J11)then set power switch (S3) to the ON Position.If Development Kit, apply power to the MCU Card using 1 of 2 power options.Power Options1: Mini USB – For USB MCUs2: 9 V Universal Adapter – For Non-USB MCUsIf Enhanced DK, update the motherboardfirmware using the UDP MotherboardFirmware Update Utility./udpMCU card321412Note: If Enhanced DK, the MCU Card is powered from the motherboard.36If Enhanced DK, connect the MCU card and I/O card to the UDP Motherboard.1Download the User’s Guide for EachBoard in the Development Kit.Where to Find DocumentationData Sheet:/32bit-mcu →Choose Product Family →Documentation tab Reference Manual:/32bit-mcu →Choose Product Family →Documentation tab Hardware User's Guide:/32bit-mcu →Design Resources →Unified Development Platform OR /udp Application Notes:/32bit-mcu →Design Resources →Application Notes Software Development Kit Documentation:C:\Silabs\32bit\si32-{revision}\Documentation\si32Hal.chm Quality Documents:/qualityE . U s i n g t h e P r e c i s i o n 32 D e v e l o p m e n t S u i t eT h e P r e c i s i o n 32 D e v e l o p m e n t S u i t e i s a c o m p l e t e d e v e l o p m e n t s y s t e m f o r S i l i c o n L a b s 32-b i t M C U s . T h e D e v e l o p m e n t S u i t e c o n s i s t s o f t h r e e p a r t s : t h e U n i f i e d D e v e l o p m e n t P l a t f o r m (U D P ) h a r d w a r e , t h e S o f t w a r e D e v e l o p m e n t K i t (S D K ), a n d t h e P C d e v e l o p m e n t t o o l s i n c l u d i n g A p p B u i l d e r a n d t h e I n t e g r a t e d D e v e l o p m e n t E n v i r o n m e n t (I D E ). S e e t h e a p p l i c a t i o n n o t e s l i s t e d b e l o wf o r c o m p l e t e d e t a i l s .t h e p r o g r a m . T h e L E D b l i n k . P a u s e p r o g r a R u nl i n e s o f c o d e a n d s e l e c t T o g B r e a k p o i n t t o a d d a b r e a k p o T h e n p r e s s R u n t o r u n t o b r e a k p o i c o d e .S t e p I n t o o r S t e p O v e r V i e w o r m o d i f y P e r i p h e r a R e g i s t e r s , o r M e m o i a b l e , r i g h t -c l i a n d s e l e c t A d d W a t c h E x p r e t o a d d i t t o t h e E x p r e s s i o n s w A p p B u i l d e r I D E•A N 675: P r e c i s i o n 32 D e v e l o p m e n t S u i t e O v e r v i e w•A N 667: G e t t i n g S t a r t e d w i t h t h e S i l i c o n L a b s P r e c i s i o n 32 I D E•A N 670: G e t t i n g S t a r t e d w i t h t h e S i l i c o n L a b s P r e c i s i o n 32 A p p B u i l d e r•A N 678: P r e c i s i o n 32 s i 32F l a s h U t i l i t y C o m m a n d -L i n e P r o g r a m m e r U s e r 's G u i d e•A N 719: P r e c i s i o n 32 I D E a n d A p p B u i l d e r D e t a i l e d T u t o r i a l a n d W a l k t h r o u g hW h e r e t o F i n d S u p p o r tM C U K n o w l e d g e B a s e :w w w .s i l a b s .c o m →S u p p o r t →K n o w l e d g e B a s eV i d e o T r a i n i n g M o d u l e s :w w w .s i l a b s .c o m →S u p p o r t →T r a i n i n g a n d R e s o u r c e sC o n t a c t a n A p p l i c a t i o n s E n g i n e e r :w w w .s i l a b s .c o m →S u p p o r t →C o n t a c t T e c h n i c a l S u p p o r tD . U s i n g t h e P r e c i s i o n 32 I DE f o r t h eF i r s t T i m e2R e g i s t e r t h e I D E u s i n g t h e s t e p s l i s t e d o n t h e W e l c o m e p a g e .1O p e n t h e P r e c i s i o n 32 I D E a n d s e l e c t t h e p r o j e c t w o r k s p a c e .313456S e l e c t j u s t t h e s i m x x x x x _B l i n k y c h e c k b o x ,e n s u r e C o p y p r o j e c t s i n t o w o r k s p a c e i s s e l e c t e d , a n d p r e s s F i n i s h .S e l e c t t h e I m p o r t S I 32 S D Ke x a m p l e (s ) l i n k i n t h e Q u i c k s t a r t w i n d o w .S e l e c t t h e s i m x x x x x _B l i n k yp r o j e c t i n t h e P r o j e c t E x p l o r e r a n d p r e s s B u i l d ‘B l i n k y ’ [D e b u g ] i n t h e Q u i c k s t a r t w i n d o w .S t a r t a D e b u g s e s s i o n b yc l i c k i n g D e b u g ‘B l i n k y ’ [D e b u g ] i n t h e Q u i c k s t a r t w i nd o w .。
exoSip开发手册
WFM200S Wi-Fi Expansion Kit 用户指南说明书
UG407: WFM200S Wi-Fi® Expansion Kit User's GuideThe WFM200S Wi-Fi Expansion Kit is an excellent way to ex-plore and evaluate the WFM200S Wi-Fi Transceiver Module with a Raspberry Pi or an EFM32 MCU for your embedded applica-tion.The WFM200S Wi-Fi Transceiver Module is an easy to use and easy to interface Wi-Fi Network Co-Processor (NCP). Most of the associated complexity of Wi-Fi and the pro-tocol stack is offloaded to the NCP and allows for easy Wi-Fi integration into any em-bedded system.The kit easily integrates and brings Wi-Fi connectivity to a compatible Silicon Labs MCU Starter Kit through the EXP header. The WFM200S Wi-Fi Expansion Kit has also been designed after the Raspberry Pi Hardware Attached on Top (HAT) board specifi-cation, allowing the WFM200S Wi-Fi Expansion Kit to connect to a Raspberry Pi.WFM200S EXPANSION BOARD FEATURES•Selectable SPI or SDIO host interface •EXP connector for interfacing Silicon Labs Starter Kits•Allows board detection andidentification•Raspberry Pi compatible HAT•40-pin header•HAT EEPROM for identificationTable of Contents1. Introduction (3)1.1 Kit Contents (4)2. Hardware Overview (5)2.1 Hardware Layout (5)3. WFM200S Wi-Fi NCP Expansion Kit (6)3.1 Host Interfaces (6)3.2 Power-on and Manual Reset Circuit (7)4. Connectors (8)4.1 EXP Header (9)4.1.1 Pass-through EXP Header (9)4.1.2 EXP Header Pinout (10)4.2 Raspberry Pi Connector (11)4.2.1 Raspberry Pi Connector Pinout (12)4.3 External FEM Connector (13)4.3.1 External FEM Connector Pinout (13)4.4 PTA Connector (14)4.4.1 PTA Connector Pinout (14)4.5 Secondary RF Connector (14)4.6 Power Supply (15)5. Schematics, Assembly Drawings, and BOM (16)6. Kit Revision History (17)6.1 SLEXP8023A Revision History (17)6.2 SLEXP8023C Revision History (17)7. Document Revision History (18)1. IntroductionThis user guide describes the WFM200S Wi-Fi Expansion Kit. The kit connects to either a Silicon Labs EFM32 MCU starter kit (STK), a Silicon Labs EFR32 wireless starter kit (WSTK) or a Raspberry Pi equipped with the 40-pin Raspberry Pi hardware-attached-on-top (HAT) connector. SDIO support is available only with selected hosts.Figures 1.1 and 1.2 shows the kit connected to a Silicon Labs MCU STK through the Expansion Header and a Raspberry Pi, respec-tively.Figure 1.1. WFM200S Wi-Fi Expansion Kit Connected to a Silicon Labs EFM32GG11 MCU STKFigure 1.2. WFM200S Wi-Fi Expansion Kit Connected to a Raspberry Pi Note: Do not connect the kit to both a Silicon Labs MCU STK and a Raspberry Pi at the same time.1.1 Kit ContentsThe WFM200S Wi-Fi Expansion Kit comes in two versions, which differs in what's included in the box:•SLEXP8023A:•BRD8023A WFM200S Wi-Fi EXP Board•8 GB Micro-SD card with software image for Raspberry Pi 2•SLEXP8023C:•BRD8023A WFM200S Wi-Fi EXP Board•8 GB Micro-SD card with software image for Raspberry Pi 2•Raspberry Pi 2 Model B Single-Board Computer•Raspberry Pi Power Supply 5.1 V, 2.5 A2. Hardware Overview2.1 Hardware LayoutThe layout of the WFM200S Wi-Fi Expansion Kit is shown in the figure below.EXP-header for Starter Kits Power source select switchPass-through EXP-header Not mountedRaspberry Pi connectorOn bottom sideCurrent consumptionmeasurement headerNot mountedWFM200S Wi-FiExpansion BoardHost interfaceselect switchSecondary RF outputcoaxial connectorExternal FEM headerNot mountedPTA headerNot mountedReset buttonFigure 2.1. WFM200S Wi-Fi Expansion Kit Hardware LayoutHardware Overview3. WFM200S Wi-Fi NCP Expansion KitThe WFM200S Wi-Fi Transceiver Module is a Wi-Fi Network Co-Processor (NCP) transceiver from Silicon Labs.3.1 Host InterfacesSPI and SDIO are the two available host interfaces (HIF) on the WFM200S Wi-Fi Expansion Kit. A slide switch, whose state is sampled during power-on reset or manually issued reset is used to select the interface. The slide switch must remain in the same position throughout the duration of the session since it also controls HIF selection multiplexer circuits.When the WFM200S Wi-Fi Expansion Kit is connected to an EFM32/EFR32 starter kit through the EXP header, the state of the HIF selection switch can be read (but not controlled) by the kit mcu through a GPIO pin.The WFM200S Wi-Fi Expansion Kit incorporates a set of multiplexer circuits which allows the user to use the same kit for evaluating the WFM200S in both applications requiring SPI or SDIO connectivity to the host. These circuits will normally not be needed in an end-user application since in most cases the interface to use will be fixed.A simplified circuit diagram showing the host interface multiplexer circuits is shown below. The EXP_HEADER9 signal is connected to pin 9 on the EXP header, while the HIF_OEn output enable signal is controlled by the power-on reset circuit (explained later).Figure 3.1. Host Interface Multiplexer Circuit3.2 Power-on and Manual Reset CircuitTo ensure that the state of the host interface selection signal is sampled correctly at the rising edge of the WFM200S RESETn signal, a power-on reset circuit has been added to the WFM200S Wi-Fi Expansion Kit. This circuit achieves this by•Adding a delay of 1ms to the rising edge of the RESETn signal with respect to the rising edge of the power supply•Isolating the host from the WFM200S DAT2/HIF_SEL pin during the rising edge of the RESETn signalThe figure below shows the circuit diagram for the power-on and manual reset circuit. Its functionality is as follows:•NCP_RESETn is the active-low reset signal of the WFM200S. The WFM200S RESETn pin has an internal pull-up of approximately43 kOhms. The on-board reset button is connected to this signal.•HIF_SEL_CTRL is the signal from the HIF selection switch•HIF_OEn is the active-low output enable signal of the HIF multiplexer circuits•WF_DAT2_HIF_SEL is the combined SDIO DAT2 signal and HIF selection signal of the WFM200S•U114 is an open-drain active low output reset monitor which with the installed capacitor connected to the CD pin keeps NCP_RE-SETn tied to ground for about 1 ms after VMCU_NCP has exceeded the threshold voltage of 0.9 V•U115 is a tri-state output buffer with an active low output enable signal connected to NCP_RESETn which pulls the CD pin of U116 low while NCP_RESETn is low•U116 is a push-pull active high output reset monitor which drives HIF_OEn high for 1 ms after the output of U115 is disabled•U109 is a tri-state output buffer with an active high output enable signal which connects the HIF_SEL_CTRL signal to the WF_DAT2_HIF_SEL signal as long as HIF_OEn is highThe NCP_RESETn signal is available on both the EXP header and the Raspberry Pi connector and can be used for issuing a manual reset sequence by pulling it low for at least 1 ms.Note: Reset button is effective when board is not connected to MCU or Raspberry Pi boards. When connected, change of host inter-face is effective after reboot.Figure 3.2. Power-on and Manual Reset Circuit Diagram4. ConnectorsThis chapter gives an overview of the WFM200S Wi-Fi Expansion Kit connectivity and power connections.Pass-through EXP Header(Bottom side)External FEM connector Figure 4.1. WFM200S Wi-Fi Expansion Kit Connector Layout4.1 EXP HeaderOn the left-hand side of the WFM200S Wi-Fi Expansion Kit, a right-angle female 20-pin EXP header is provided to connect to one of Silicon Labs’ supported Starter Kits. The EXP header on the Starter Kits follows a standard which ensures that commonly used periph-erals such as an SPI, a UART, and an I 2C bus, are available on fixed locations on the connector. Additionally, the VMCU, 3V3 and 5 V power rails are also available on the expansion header. For detailed information regarding the pinout to the expansion header on a specific Starter Kit, consult the accompanying user’s guide.The figure below shows how the WFM200S Wi-Fi Transceiver Module is connected to the connector and the peripheral functions that are available.VMCUSPI_MOSI / SDIO_DAT1SPI_MISO / SDIO_DAT0SPI_SCLK / SDIO_CMD SPI_CS / SDIO_CLK SPI_WIRQ / SDIO_DAT3SDIO_DAT2Not Connected (NC)5V3V3GNDGPIO_WUP Not Connected (NC)RESETnHIF_SEL_CTRL Not Connected (NC)Not Connected (NC)Not Connected (NC)BOARD_ID_SDA BOARD_ID_SCL Reserved (Board Identification)WFM200S I/O PinFigure 4.2. Expansion Header4.1.1 Pass-through EXP HeaderThe WFM200S Wi-Fi Expansion Kit features a footprint for a secondary EXP header. All signals from the EXP header, including those that are not connected to any features on the WFM200S Wi-Fi Expansion Kit, are directly tied to the corresponding pins in the footprint,allowing daisy-chaining of additional expansion boards if a connector is soldered in.4.1.2 EXP Header PinoutThe table below shows the pin assignments of the EXP header.Table 4.1. EXP Header Pinout4.2 Raspberry Pi ConnectorOn the bottom side of the WFM200S Wi-Fi Expansion Kit, a dual row, female socket, 0.1" pitch connector is installed to allow the WFM200S Wi-Fi Expansion Kit to act as a Raspberry Pi Hardware Attached on Top (HAT) board.The figure below shows how the WFM200S Wi-Fi Transceiver Module is connected to the connector and the peripheral functions that are available.Reserved (Board Identification)WFM200S I/O PinGNDSDIO_DAT2Not Connected (NC)RESETnGPIO_WIRQNot Connected (NC)RPI_ID_SDGND SPI_SCLKSPI_MISO Not Connected (NC)Not Connected (NC)SPI_WIRQGNDGPIO_WUP GNDRPI_ID_SC Not Connected (NC)SDIO_DAT1SPI_CSSPI_MOSI 3V3SDIO_CLKSDIO_DAT3 Not Connected (NC)GNDNot Connected (NC)Not Connected (NC) Not Connected (NC)3V3GNDSDIO_DAT0SDIO_CMD GNDNot Connected (NC)GPIO_FEM_5GPIO_FEM_6GND5V 5VFigure 4.3. Raspberry Pi Connector4.2.1 Raspberry Pi Connector PinoutThe table below shows the pin assignments of the Raspberry Pi connector, and the port pins and peripheral functions that are available on the WFM200S Wi-Fi Expansion Kit.Table 4.2. Raspberry Pi Connector Pinout4.3 External FEM ConnectorThe WFM200S Wi-Fi Expansion Kit features a 2x5-pin 0.1" pitch connector exposing the WFM200S Wi-Fi Transceiver Module's exter-nal front-end module (FEM) interface, which allows the connection of an external FEM board using a ribbon cable.The WFM200S Wi-Fi Expansion Kit also features a TX/RX activity indicator LED which is connected to the FEM_5 signal. By default, to optimize power consumption, TX/RX activity LED is not enabled. PDS sections PROG_PINS_CFG and FEM_CFG should be updated to enable this functionality.The pinout of the connector is illustrated in the figure below.GNDFEM_PDETFEM_6FEM_5VMCU_NCPFEM_4FEM_3VMCU_NCPFEM_2FEM_1Figure 4.4. External FEM Connector4.3.1 External FEM Connector PinoutThe pin assignment of the external FEM connector on the board is given in the table below.Table 4.3. External FEM Connector Pin Descriptions4.4 PTA ConnectorThe WFM200S' packet transfer arbitration (PTA) interface for managing coexistence in a multi-transceiver application is exposed on a 1x5-pin 0.1" pitch header on the WFM200S Wi-Fi Expansion Kit.The pinout of the connector is illustrated in the figure below.PTA_STATUS / PRIORITY PTA_RF_ACT / REQUESTPTA_FREQ / RHOPTA_TX_CONF / GRANT GNDFigure 4.5. PTA Connector4.4.1 PTA Connector PinoutThe pin assignment of the PTA connector on the board is given in the table below.Table 4.4. PTA Connector Pin Descriptions4.5 Secondary RF ConnectorThe WFM200S' secondary RF output is exposed on the WFM200S Wi-Fi Expansion Kit through a Hirose u.FL coaxial connector.For connecting the secondary RF output to an RF measurement instrument, 50 ohms resistor R641 shall be removed and a u.FL to SMA adapter cable (not included with the kit) can be used. Examples of such adapter cables are the Taoglas CAB.721 (100 mm) or CAB.720 (200 mm) cable assemblies.4.6 Power SupplyThere are two ways to provide power to the kit:•The kit can be connected to, and powered by, a Silicon Labs MCU STK •The kit can be connected to, and powered by, a Raspberry PiNote: Connecting the WFM200S Wi-Fi Expansion Kit to both an EFM32/EFR32 STK and a Raspberry Pi at the same time is not a valid option.When connected to a Silicon Labs MCU STK, the WFM200S Wi-Fi Transceiver Module can either be powered by the VMCU rail present on the EXP header or through an LDO regulator on board the WFM200S Wi-Fi Expansion Kit. If connected to the VMCU rail of the starter kit, the current consumption of the WFM200S Wi-Fi Transceiver Module will be included in the starter kit's on-board Ad-vanced Energy Monitor (AEM) measurements. The LDO regulator draws power from the 5V net, and, hence, the power consumption of the WFM200S Wi-Fi Transceiver Module will not be included in any AEM measurements performed by the MCU STK.A mechanical power switch on the WFM200S Wi-Fi Expansion Kit is used to select between Low Power (AEM) mode and High Power (LDO) mode. When the switch is set to Low Power (AEM) mode, the WFM200S Wi-Fi Transceiver Module is connected to the VMCU net on the Expansion Header. When the switch is set to High Power (LDO) mode, the WFM200S Wi-Fi Transceiver Module is connec-ted to the output of the LDO. For applications requiring high power consumption or when the WFM200S Wi-Fi Expansion Kit is connec-ted to a Raspberry Pi, the power switch must be set to High Power (LDO) mode.A 0.1 ohm current sense resistor accompanied by a 2x2-pin 0.1" unpopulated header is provided to measure the current consumption of the WFM200S Wi-Fi Transceiver Module whenever AEM is not available or when the current consumption exceeds the measure-ment range of AEM.The power topology is illustrated in the figure below.Expansion HeaderRaspberry Pi ConnectorFigure 4.6. WFM200S Wi-Fi Expansion Kit Power TopologySchematics, Assembly Drawings, and BOM 5. Schematics, Assembly Drawings, and BOMSchematics, assembly drawings, and bill of materials (BOM) are available through Simplicity Studio when the kit documentation pack-age has been installed. They are also available from the Silicon Labs website and kit page.6. Kit Revision HistoryThe kit revision can be found printed on the kit packaging label, as outlined in the figure below.SLEXP8023A WFM200S Wi-Fi Expansion Kit194000022401-11-19A01Figure 6.1. Kit Label6.1 SLEXP8023A Revision History6.2 SLEXP8023C Revision History Kit Revision HistoryDocument Revision History 7. Document Revision HistoryRevision 1.02019-11-01•Initial document revision.Simplicity StudioOne-click access to MCU and wireless tools, documentation, software, source code libraries & more. Available for Windows, Mac and Linux!IoT Portfolio /IoTSW/HW/simplicityQuality/qualitySupport and CommunitySilicon Laboratories Inc.400 West Cesar ChavezAustin, TX 78701USADisclaimerSilicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using or intending to use the Silicon Labs products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and "Typical" parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Labs reserves the right to make changes without further notice to the product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Without prior notification, Silicon Labs may update product firmware during the manufacturing process for security or reliability reasons. Such changes will not alter the specifications or the performance of the product. Silicon Labs shall have no liability for the consequences of use of the information supplied in this document. This document does not imply or expressly grant any license to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any FDA Class III devices, applications for which FDA premarket approval is required or Life Support Systems without the specific written consent of Silicon Labs. A "Life Support System" is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons. Silicon Labs disclaims all express and implied warranties and shall not be responsible or liable for any injuries or damages related to use of a Silicon Labs product in such unauthorized applications.Trademark InformationSilicon Laboratories Inc.® , Silicon Laboratories®, Silicon Labs®, SiLabs® and the Silicon Labs logo®, Bluegiga®, Bluegiga Logo®, Clock B uilder®, CMEMS®, DSPLL®, EFM®, EFM32®, EFR, Ember®, Energy Micro, Energy Micro logo and combinations thereof, "the world’s most energy friendly microcontrollers", Ember®, EZLink®, EZRadio®, EZRadioPRO®, Gecko®, Gecko OS, Gecko OS Studio, ISOmodem®, Precision32®, ProSLIC®, Simplicity Studio®, SiPHY®, Telegesis, the Telegesis Logo®, USBXpress® , Zentri, the Zentri logo and Zentri DMS, Z-Wave®, and others are trademarks or registered trademarks of Silicon Labs. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. Wi-Fi is a registered trademark of the Wi-Fi Alliance. All other products or brand names mentioned herein are trademarks of their respective。
OpenScape 4000 V8 - Portfolio Presentation - What's new - V8 R0 and V8 R1_JJT
OpenScape Access SLU
1 planned
OpenScape Access SLC-M
2 planned
for December 2017
for March 2018
Copyright © Unify Software & Solutions GmbH & Co. KG 2017. All rights reserved.
Small
Branch
Large
OpenScape 4000 OpenScape Access modules or virtual machine OpenScape Enterprise Gateway
OpenScape 4000 SoftGate
OpenScape 4000 V8 R1
Copyright © Unify Software & Solutions GmbH & Co. KG 2017. All rights reserved.
5
New hardwant
Subscriber Line Module Cordless (SLMC) Successor of SLC24 to connect DECT base stations, same capacity (24 ports, 16 base stations) Offers integrated Inter System Synchronization interfaces (SLCSS sub board no longer needed) Base station BS3 not supported anymore
March 2018 OpenScape Access SLC-M2
Atmel CryptoAuthentication AT88CK101 开发套件硬件用户指南说明书
AT88CK101 Atmel CryptoAuthentication Development KitHARDWARE USER GUIDEAtmel CryptoAuthentication AT88CK101 DaughterboardAtmel-8726A-CryptoAuth-AT88CK101-Hardware-UserGuide_112015AT88CK101 Development Kit [HARDWARE USER GUIDE] Atmel-8726A-CryptoAuth-AT88CK101-Hardware-UserGuide_11201522IntroductionThe Atmel ®CryptoAuthentication™ AT88CK101 is a daughterboard that interfaces with a MCU board via a 10-pin header. The daughterboard has a single 8-pin SOIC socket which can support the AtmelATSHA204A, ATAES132A, ATECC108A, and ATECC508A crypto element devices. The daughter board comes in two different variations with a socket that supports either an 8-lead SOIC or an 8-leadUDFN/XDFN. This kit uses a modular approach, enabling the daughterboard to connect directly to an STKseries Atmel AVR ® or Atmel ARM ®development platform to easily add security to applications. An optional adapter kit is also available when the 10-pin header on the daughterboard is incompatible. The AT88CK101provides a test point header for the I 2C, SWI, and SPI signals. The AT88CK101 is sold with the Atmel AT88Microbase module to form the Atmel AT88CK101-XXX Starter Kit. The AT88Microbase AVR-based base board comes with a USB interface that lets designers learn and experiment on their PCs.Contents∙ Atmel AT88CK101 DaughterboardFeatures∙ 8-lead SOIC and UDFN/XDFN Socket∙ Supports the ATSHA204A, ATAES132A, ATECC108A, and ATECC508A Devices ∙Supports Communication Protocols: – I 2C– SWI (Single-Wire Interface) – SPI ∙ Power LED ∙Test Points HeaderFigure 1.AT88CK101 DaughterboardPin 1 Indicator HeaderStandoff HoleStandoff HoleProtocolTable of ContentsAT88CK101 Starter Kit (4)Development Kit Configuration (5)10-pin Interface Header (5)6-pin Test Header (5)Supports 8-lead SOIC and SPI Interfaces (5)Configurations (6)References and Further Information (7)Revision History (8)AT88CK101 Development Kit [HARDWARE USER GUIDE]Atmel-8726A-CryptoAuth-AT88CK101-Hardware-UserGuide_1120153 3AT88CK101 Development Kit [HARDWARE USER GUIDE] Atmel-8726A-CryptoAuth-AT88CK101-Hardware-UserGuide_11201544AT88CK101 Starter KitThe AT88CK101 is sold with the Atmel AT88Microbase module to form the AT88CK101-XXX Starter Kit. For additional information on the AT88Microbase, refer to the Atmel AT88Microbase Hardware User Guide .Figure 2.AT88CK101STK8 Starter KitFigure 3.AT88CK101 Daughterboard with AT88MicrobaseAT88CK101 Development Kit [HARDWARE USER GUIDE]Atmel-8726A-CryptoAuth-AT88CK101-Hardware-UserGuide_11201555 Development Kit Configuration10-pin Interface HeaderTable 1-1. 10-pin Interface Header (1)(2)Notes: 1. I C Pins:SCL, SDA2. SPI Pins:/CS, SCLK, MOSI, MISO6-pin Test HeaderTable 1-2.6-pin Test HeaderSupports 8-lead SOIC and SPI InterfacesThe AT88CK101 supports 8-lead SOIC and SPI Interfaces with the following pinout configuration.Figure 4.Pinout ConfigurationsNote:Drawings are not to scale.Top View 8-lead SOICNC NC NC NCV CC NC SCL SDA12348765Top View8-lead SOIC/CS SO NC GNDV CC NC SCK SI12348765ConfigurationsThe below table describes the how to configure the AT88CK101 with respect to the AT88Microbase and the STK/EVK development platforms.Table 1. AT88CK101STK8 Starter Kit Configuration GuideNote: X = Don’t CareFigure 5. AT88CK101 Adapter Board Mounted to STK600AT88CK101 Development Kit [HARDWARE USER GUIDE]Atmel-8726A-CryptoAuth-AT88CK101-Hardware-UserGuide_11201566Figure 6. Atmel AT88CK301ADP Adapter KitTable 2. 10-pin Squid CableReferences and Further InformationSchematics, Gerber files, Bill Of Materials (BOM), development and demonstration software is conveniently downloadable from the Atmel website at /cryptokits.ATMEL EVALUATION BOARD/KIT IMPORTANT NOTICE AND DISCLAIMERThis evaluation board/kit is intended for user's internal development and evaluation purposes only. It is not a finished product and may not comply with technical or legal requirements that are applicable to finished products, including, without limitation, directives or regulations relating to electromagnetic compatibility, recycling (WEEE), FCC, CE or UL. Atmel is providing this evaluation board/kit “AS IS” without any warranties or indemnities. The user assumes all responsibility and liability for handling and use of the evaluation board/kit including, without limitation, the responsibility to take any and all appropriate precautions with regard to electrostatic discharge and other technical issues. User indemnifies Atmel from any claim arising from user's handling or use of this evaluation board/kit. Except for the limited purpose of internal development and evaluation as specified above, no license, express or implied, by estoppel or otherwise, to any Atmel intellectual property right is granted hereunder. ATMEL SHALL NOT BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMGES RELATING TO USE OF THIS EVALUATION BOARD/KIT.ATMEL CORPORATION1600 Technology DriveSan Jose, CA 95110USAAT88CK101 Development Kit [HARDWARE USER GUIDE]Atmel-8726A-CryptoAuth-AT88CK101-Hardware-UserGuide_1120157 7AT88CK101 Development Kit [HARDWARE USER GUIDE] Atmel-8726A-CryptoAuth-AT88CK101-Hardware-UserGuide_11201588Revision History。
OpenStage 20 HFA_HiPath 4000_用户手册(中文显示)_Issue 3_080718
关于本手册......................................................................................... 8 服务 ................................................................................................... 8 话机用途 ............................................................................................ 9 话机型号 ............................................................................................ 9 免提音质和显示屏清晰度 ................................................................... 9
2
话机放置
z 话机正常工作的环境温度为 5°C 到 40°C间。 z 为保证扬声效果，话机正面传声器处应保持干净。最佳的受话距离为50 cm。 z 请不要把话机安装于有大量灰尘积聚处，否则会缩短话机的使用寿命。 z 请不要将话机置于阳光暴晒处或热源附近，否则电子器件或塑料成分会受到损坏。 z 请不要在潮湿环境，如浴室中，使用此话机。
切换到免提模式................................................................................ 20 切换到手柄模式................................................................................ 20 开放式聆听....................................................................................... 20 打开/关闭麦克风............................................................................... 21 结束通话 .......................................................................................... 21
GSF-CANopen操作手册说明书
Code 85204 Edition 12-20151 Safety Instruction2 Introduction3 Electrical Connections4 Network Management (NMT)5 Baude Rate6 Node-ID7 Parameter Settings 8 Restore Default Parameter 9 Heartbeat 10 Error Handling 11 SDO Communication12 PDO Communication and Length Calculation 13 CANopen Features SummaryCANopen GSFdigital outputIf total failure or malfunction of the sensor can cause danger or injury to the operator or damage to the machinery or equipment it is recommended that additional safety measures should be incorporated into the system.Any alteration, reconstruction or extension of the sensor is not allowed. Sensor must be operated only within values specified in the datasheet.Connection to power supply must be performed in accordance with safety instructions for electrical facil-ities and performed only by trained staff.Disregard of this advice can lead to malfunctions, damage to property or personal injury and releases the manufacturer from product liability.Do not open sensorRelease of spring under tension can result in injury!Do not snap cableUncontrolled cable retraction can break off cable fixing. Broken fixing and cable can result in injury. Also sensor will be damaged!Do not travel over rangeUncontrolled cable retraction can result in injury. Also sensor will be damaged!Special attention during mounting and operation of metal cable sensorsRisk of injury by the measuring cable!Sensors without cover / housing (OEM sensors)Risk of injury by moving parts. Mounting and operation of the sensor only with appropriate safety equipment that an injury is impossible!Do not exceed maximum operating voltage listed in the catalogRisk of injury. Sensor will be damage●Before connecting the sensor to the CANbus the devices have to be checked for correct bitrateand unique node-IDs. Both parameters are configurable by Layer-Setting-Service (LSS) or by Service Data Object (SDO).●After power-on the sensor will enter pre-operational state and send a bootup message being re-ady for configuration by Service Data Objects. Parameters configured by the user can be stored nonvolatile by SAVE command.●On receiving… …NMT-Node-Start“the sensor transits to operational state and starts process datatransmission.●When …Auto-Start“is configured the sensor will automatically transit to operational after boot-up without a need for the Node-Start message. Node monitoring is supported by Heartbeat protocol.The Heartbeat protocol provides automatic transmission of the node status (heartbeat messa-ge) by the slave within producer heartbeat time window.●Following the CAN example protocols included in this manual the sensor may be used withoutCANopen master device.●Do not damage cable!●Cable must not be oiled or lubricated!●Do not snap cable!●Do not travel over range!●Do not crack cable!.●Cable travel should be axial to the cable outlet (no misalignment allowed!)●Do not drag cable along objects!PrecautionsDo not let snap the cableUncontrolled retraction of cable may damage sensor.No warranty will be granted for snapped cables.Mounting hints for unfavorable conditionsIf possible fasten cable fixing with cable in retracted position.For example, fit a mounting loop and put it around your wrist.Do not remove the mounting loop before the cable ist fastened.The cable clip may be opened for easy attachment.MountingTo ensure proper operation, install the sensor only as described in this manual.The purpose of GSF position sensors is to transform position of a linear and guided movement into an electrical signal. Specifications of measuring range, environment, handling and connections as specified in the catalog, must be followed. The catalog is part of this instruction manual. If the catalog is not available it may be requested by stating the respec-tive model number. Linear motion of the measuring cable (flexible stainless steel) is converted into rotation by means of a precision cable drum. A spring motor provides torque for the cable retraction. Special design assures precise and reproducible winding of the measuring cable. Cable extraction or retraction is transformed into an electrical signal. The sensor is based on state-of-the-art multiturn potentiometric technology implementing the functions of a CAN BUS network slave device conforming to standard CANopen protocol proposed by C.i.A. (Can in Automation) and described in the document entitled “CANOpen Application Layer and Communication Profile DS 301 v. 4.2” and in other documents mentioned below. Other reference documents used are C.i.A. DS-410 Device Profile for inclinometer and C.i.A. DSP-305 Layer Setting Services and Protocol V1.1.1.This document describes the standard CANopen implementations created. It is addressed to CANopen network system integrators and to CANopen device designers who already know the content of the above-mentioned standards defined by C.i.A... The details of aspects defined by CANopen do not pertain to the purpose of this text.For further information on the protocol you can also contact us via e-mail: at or contact the GEFRAN office nearest to you.Definition and ShorteningCAN: Controller Area Network.Describes a serial communication bus that implements the “physical” level 1 and the “data link” level 2 of the ISO/OSI reference model.CAL: CAN Application Layer.Describes implementation of the CAN in the level 7 “application” of the ISO/OSI reference model from which CANopen derives.CMS: CAN Message Specification.CAL service element. Defines the CAN Application Layer for the various industrial applications.COB: Communication Object.Unit of transport of data in a CAN network (a CAN message). A maximum of 2048 COBs may be present in a CAN net-work, each of which may transport from 0 to a maximum of 8 bytes.COB-ID: COB Identifier.Identifying element of a CAN message. The identifier determines the priority of a COB in case of multiple messages in the network.D1 – D8: Data from 1 to 8.Number of bytes in the data field of a CAN message.DLC: Data Length code.Number of data bytes transmitted in a single frame.ISO: International Standard Organization.International authority providing standards for various merchandise sectors.NMT: Network Management.CAL service element. Describes how to configure, initialize, manage errors in a CAN network.PDO: Process Data Object.Process data communication objects (with high priority).RXSDO: Receive SDO.SDO objects received from the remote device.SDO: Service Data Object.Service data communication objects (with low priority). The value of this data is contained in the “Objects Dictionary” of each device in the CAN network.TXPDO: Transmit PDO.PDO objects transmitted by the remote device.TXSDO: Transmit SDO.SDO objects transmitted by the remote device.N.B.: The numbers followed by the suffix “h” represent a hexadecimal value, with suffix “b” a binary value, and with suffix “d” a decimal value. The value is decimal unless specified otherwise.CONNECTIONS 1. +SUPPLY2. GROUND3. OUTPUT4. n.c.CONNECTIONS 1. + SUPPLY 2. GROUND 3. OUTPUT 14. n.c.5. + SUPPLY6. GROUND7. OUTPUT 28. n.c.CONNECTIONS 1. + SUPPLY 2. GROUND 3. CANH 14. CANL 15. + SUPPLY 6. GROUND 7. CANH 28. CANL 2CONNECTIONS 1. +SUPPLY 2. GROUND 3. CANH 4. CANLThe device supports CANopen network management functionality NMT Slave (Minimum Boot Up):Node ID can be configurable via SDO communication object 0x20F2 and 0x20F3 (see communication examples at the end of this document).The default Baud rate is 250kbit/s.Important Note:Changing this parameter can disturb the network! Use this service only if one device is connected to the network!Node ID can be configurable via SDO communication object 0x20F0 and 0x20F1 (see communication examples at the end of this document).The default Node-ID is 7F.Important Note:Changing this parameter can disturb the network! Use this service only if one device is connected to the network!All object dictionary parameters (objects with marking PARA) can be saved in a special section of the internal EEPROM and secured by checksum calculation. The special LSS parameters (objects with marking LSS-PARA), also part of the object dictionary, will be also saved in a special section of the internal EEPROM and secured by checksum calculation. Due to the internal architecture of the microcontroller the parameter write cycles are limited to 100,000 cycles.Not supported.The heartbeat mechanism for this device is established through cyclic transmission of the heartbeat message done by the heartbeat producer.One or more devices in the network are aware of this heartbeat message. If the heartbeat cycle fails from the heartbeat producer the local application on the heartbeat consumer will be informed about that event. The implementation of either guarding or heartbeat is mandatory.The device supports Heartbeat Producer functionality. The producer heartbeat time is defined in object 0x1017.Heartbeat MessagePrincipleEmergency messages (EMCY) shall be triggered by internal errors on device and they are assigned the highest possible priority to ensure that they get access to the bus without delay (EMCY Producer ). By default, the EMCY contains the error field with pre-defined error numbers and additional information.Error Behavior (object 0x4000)If a serious device failure is detected the object 0x4000 specifies, to which state the module shall be set: 0: pre-operational1: no state change (default) 2: stoppedEMCY MessageThe EMCY COB-ID is defined in object 0x1014. The EMCY message consists of 8 bytes. It contains an emergency error code, the contents of object 0x1001 and 5 byte of manufacturer specific error code. This device uses only the 1st byte as manufacturer specific error code.10. ERROR HANDLINGSupported Manufacturer Specific Error Codes (object 0x4001)The device fulfils the SDO Server functionality.Transmit PDO #0 – Length calculation GSF-xxxThis PDO transmits the length value of the position sensor. The Tx PDO #0 shall be transmitted cyclically, if the cyclic timer (object 0x1800.5) is programmed > 0. Values between 4ms and 65535 ms shall be selectable by parameter settings. The Tx PDO #0 will be transmitted by entering the "Operational" state.12.1 EXAMPLE 1: TPDO #0 length 0.0 mmIn the following figures an example of PDO mapping is reported in the case of:●Node-ID = 7Fh●Baude-rate = 250 kBaud●Linear-encoder Cia406 setting as follow:Ⅰ. Total Measuring Range (object 0x6002.0) = 8000 mm (800 steps x 10 mm)Ⅱ. Preset Value (object 0x6003.0) = 0 mm (0 steps x 103nm)Ⅲ. Measuring Step (object 0x6005.0) = 0.5 mm (500 steps x 103 nm)Ⅳ. Position Value (object 0x6004.0):8000.0 mmPosition Value:Byte 1 LSB (00h) = 00h Byte 2 = 00h Byte 3 = 00hByte 4 (MSB) = 00hPosition Value = 00000000h to decimal 0d (resolution 0.5 mm) = 0 mm12.2 EXAMPLE 2: TPDO #0 length 2000.0 mmIn the following figures an example of PDO mapping is reported in the case of:●Node-ID = 7Fh●Baude-rate = 250 kBaud ●Linear-encoder Cia406 setting as follow:Ⅰ. Total Measuring Range (object 0x6002.0) = 8000 mm (800 steps x 10 mm)Ⅱ. Preset Value (object 0x6003.0) = 0 mm (0 steps x 103 nm)Ⅲ. Measuring Step (object 0x6005.0) = 0.5 mm (500 steps x 103 nm)Ⅳ. Position Value (object 0x6004.0):Position Value:Byte 1 (LSB) = A0h Byte 2 = 0Fh Byte 3 = 00hByte 4 (MSB) = 00hPosition Value = 00000FA0h to decimal 4000d (resolution 0.5 mm) = 2000.0 mm12.3 EXAMPLE 3: TPDO #0 length 4800.0 mmIn the following figures an example of PDO mapping is reported in the case of:●Node-ID = 7Fh●Baude-rate = 250 kBaud ●Linear-encoder Cia406 setting as follow:Ⅰ. Total Measuring Range (object 0x6002.0) = 8000 mm (800 steps x 10 mm)Ⅱ. Preset Value (object 0x6003.0) = 0 mm (0 steps x 103 nm)Ⅲ. Measuring Step (object 0x6005.0) = 0.5 mm (500 steps x 103 nm)Ⅳ. Position Value (object 0x6004.0):Position Value:Byte 1 (LSB) = 80hByte 2 = 25hByte 3 = 00hByte 4 (MSB) = 00hPosition Value = 00002580h to decimal 9600d (resolution 0.5 mm) = 4800.0 mmCommunication ProfileThe parameters which are critical for communication are determined in the Communication profile. This area is common for all CANopen devices.Ro = the parameter can be read onlyRw = the parameter can be read and also writtenWo = the parameter can be written onlyManufacturer Specific Profile ObjectsIn this section you will find the manufacturer specific profile indices for the transducer.A change of the Node ID is only accepted if the entries 20F0 and 20F1 contain the same changed value.Values below 1 / above 127 are not accepted; the existing setting remains valid.After setting the new entries a reset must be made so that the new entries become valid (switch off the module for a shorttime).A change of the Baude rate is only accepted if the entries 20F2 and 20F3 contain the same changed value.Values above 7 are not accepted; the existing setting remains valid.After setting the new entries a reset must be made so that the new entries become valid (switch off the module for a short time).Manufacturer Specific Profile ObjectsIn this section you will find the manufacturer specific profile indices for the transducer.Manufacturer Specific Profile Objects (according to CiA DS-406)In this section you will find the manufacturer specific profile indices for the transducer as LINEAR ENCODER.Rw = the parameter can be read and also writtenIn this section you will find the manufacturer specific profile indices for the transducer as CAM (optional functions NOT )activated in standard versionRw = the parameter can be read and also written Wo = the parameter can be written only(*)Operating Parameters (Object 0x6000)SF= 0/1 Scaling Function DISABLE/ENABLEGSF Cams functionality (optional functions NOT activated in standard version)Each Cam has parameters for the minimum switch point, the maximum switch point and setting a hysteresis to the switch points.Possible usage of cam’s and switch points:1) How to change the Baud Rate Setting from 250 kbaud to 500 kbaudWith Service Data Object (S.D.O.) the access to entries of a device Object Dictionary is provided. As these entries may contain data of arbitrary size and data type SDOs can be used to transfer multiple data sets from a client to a server and vice versa.Structure of SDO-request by the MasterStructure of SDO-answer by the SlaveWrite first SDO (in the example the Node-ID = 0x7F)Write second SDO (in the example the Node-ID = 0x7F)Object:The supported baudrate are listed in the following table:The answer after successful storing you will receive is:andIMPORTANT NOTE:A change of the Baud rate is only accepted if the entries 0x20F2 and 0x20F3 contain the same changed value. Values above 7 are not accepted; the existing setting remains valid.After setting the new entries a reset must be made so that the new entries become valid (switch off the module for a short time).2) How to change the ID-Node from 0x7Fh (127d) to 0x06h (6d)With Service Data Object (S.D.O.) the access to entries of a device Object Dictionary is provided. As these entries may contain data of arbitrary size and data type SDOs can be used to transfer multiple data sets from a client to a server and vice versa.Structure of SDO-request by the MasterStructure of SDO-answer by the SlaveWrite first SDO (in the example the Node-ID = 0x7F)Write second SDO (in the example the Node-ID = 0x7F)Object:The supported Node-ID are 0x01 to 0x7FThe answers after successful storing you will receive is:IMPORTANT NOTE:A change of the Node ID is only accepted if the entries 0x20F0 and 0x20F1 contain the same changed value. Values below 1 / above 127 are not accepted; the existing setting remains valid. After setting the new entries a reset must be made so that the new entries become valid (switch off the module for a short time).3) How to change the PDO rate (time interval) from 100 ms to 20 msWith Service Data Object (S.D.O.) the access to entries of a device Object Dictionary is provided. As these entries may contain data of arbitrary size and data type SDOs can be used to transfer multiple data sets from a client to a server and vice versa.Structure of SDO-request by the MasterStructure of SDO-answer by the SlaveWrite (in the example the Node-ID = 0x7F)Object:The answer after successful storing you will receive is:With the aim to save functionality write the “save” command as below:Write (in the example the Node-ID = 0x7F)Note: save command is given by sending the code:Where:73h = ASCII code “s”61h = ASCII code “a”76h = ASCII code “v”65h = ASCII code “e”The answer after successful storing you will receive is:IMPORTANT NOTE:After setting the new entries a reset must be made so that the new entries become valid (switch off the module for a short time).4) H ow to activate an automatic NMT Start after Power ON(the PDO will be send automatically after power ON)With Service Data Object (S.D.O.) the access to entries of a device Object Dictionary is provided. As these entries may contain data of arbitrary size and data type SDOs can be used to transfer multiple data sets from a client to a server and vice versa.Structure of SDO-request by the MasterStructure of SDO-answer by the SlaveWrite (in the example the Node-ID = 0x7F)Object:The answer after successful storing you will receive is:With the aim to save functionality write the “save” command as below:Write (in the example the Node-ID = 0x7F)Note: save command is given by sending the code:Where:73h = ASCII code “s”61h = ASCII code “a”76h = ASCII code “v”65h = ASCII code “e”The answer after successful storing you will receive is:IMPORTANT NOTE:After setting the new entries a reset must be made so that the new entries become valid (switch off the module for a short time).5) H ow to Preset the Position Value (via object 0x6003.0) to 0.0 mmThe value "...Preset Value" (object 0x6003.0) affects the display of the Position Value. The value entered in "...Preset Value" immediately corrects the measured value of the sensor cell at the instant tacc. A typical application is the compen-sation of display errors due to mounting (e.g. sensor zeroing).The sensor must first be brought to a defined position.With Service Data Object (S.D.O.) the access to entries of a device Object Dictionary is provided. As these entries may contain data of arbitrary size and data type SDOs can be used to transfer multiple data sets from a client to a server and vice versa.Structure of SDO-request by the MasterStructure of SDO-answer by the SlaveWrite (in the example the Node-ID = 0x7F)Object:The answer after successful storing you will receive is:With the aim to save functionality write the “save” command as below:Write (in the example the Node-ID = 0x7F)Note: save command is given by sending the code:Where:73h = ASCII code “s”61h = ASCII code “a”76h = ASCII code “v”65h = ASCII code “e”The answer after successful storing you will receive is:IMPORTANT NOTE:After setting the new entries a reset must be made so that the new entries become valid (switch off the module for a short time).GEFRAN spavia Sebina, 74 - 25050 PROVAGLIO D’ISEO (BS) - ITALIA tel. 0309888.1 - fax. 0309839063 Internet: 。
丝琳基尔实验室开发的OpenThread 2.3.0.0 产品说明书
Silicon Labs OpenThread SDK 2.3.0.0 GA Gecko SDK Suite 4.3June 7, 2023Thread is a secure, reliable, scalable, and upgradeable wireless IPv6 mesh networking Array protocol. It provides low-cost bridging to other IP networks while optimized for low-power /battery-backed operation. The Thread stack is designed specifically for Connected Homeapplications where IP-based networking is desired and a variety of application layers maybe required.OpenThread released by Google is an open-source implementation of Thread. Googlehas released OpenThread in order to accelerate the development of products for the con-nected home and commercial buildings. With a narrow platform abstraction layer and asmall memory footprint, OpenThread is highly portable. It supports system-on-chip (SoC),network co-processor (NCP), and radio co-processor (RCP) designs.Silicon Labs has developed an OpenThread-based SDK tailored to work with Silicon Labshardware. The Silicon Labs OpenThread SDK is a fully tested enhanced version of theGitHub source. It supports a broader range of hardware than does the GitHub version,and includes documentation and example applications not available on GitHub.These release notes cover SDK version(s):2.3.0.0 GA released on June 7, 2023Compatibility and Use NoticesFor information about security updates and notices, see the Security chapter of the Gecko Platform Release notes installed with this SDK or on the TECH DOCS tab on https:///developers/thread . Silicon Labs also strongly recommends that you subscribe to Security Advisories for up-to-date information. For instructions, or if you are new to the Silicon Labs OpenThread SDK, see Using This Release.Compatible Compilers:GCC (The GNU Compiler Collection) version 10.3-2021.10, provided with Simplicity Studio.Contents1New Items (1)1.1New Components (1)1.2New Features (1)1.3New Radio Board Support (1)2Improvements (2)3Fixed Issues (3)4Known Issues in the Current Release (4)5Deprecated Items (5)6Removed Items (6)7Multiprotocol Gateway and RCP (7)7.1New Items (7)7.2Improvements (7)7.3Fixed Issues (7)7.4Known Issues in the Current Release (8)7.5Deprecated Items (8)7.6Removed Items (8)8Using This Release (9)8.1Installation and Use (9)8.2OpenThread GitHub Repository (9)8.3OpenThread Border Router GitHub Repository (9)8.4Using the Border Router (9)8.5NCP/RCP Support (10)8.6Security Information (10)8.7Support (11)New Items 1 New Items1.1 New ComponentsNone1.2 New FeaturesAdded in release 2.3.0.0•The versions of OpenThread and the OpenThread Border Router have been updated. See sections 8.2 and 8.3.•Thread 1.3.1 (experimental)o IPv4/v6 public internet connectivity: NAT64 improvements, optimization of published routes and prefixes in network data o DNS enhancements for OTBRo Thread over Infrastructure (TREL)•Network Diagnostics Improvements (experimental)o Child supervision by parento Additional link quality information in child tableo Uptime for routers•Support for the ot-cli sample application with CPC on Android Hosto The ot-cli sample application can now be used with CPC on an Android host. To build, download the Android NDK toolchain, define the environment variable "NDK" to point to the toolchain, and run the script/cmake-build-android script instead of script/cmake-build.1.3 New Radio Board SupportAdded in release 2.3.0.0Support has been added for the following radio boards:•BRD4196B - EFR32xG21B•BRD2704A - Sparkfun Thing Plus MGM240PImprovements 2 ImprovementsChanged in release 2.3.0.0•Support for “diag cw” and “diag stream”o diag cw start - Start transmitting continuous carrier waveo diag cw stop - Stop transmitting continuous carrier waveo diag stream start - Start transmitting a stream of characters.o diag stream stop - Stop transmitting a stream of characters.•Bootloader support for sample applicationso The bootloader_interface component has been added to the Thread sample apps. The component introduces support for bootloaders and also results in the creation of GBL files when building.•Reduction to code size of Certified OpenThread Librarieso The pre-built certification libraries no longer include JOINER functionality.Fixed Issues 3 Fixed IssuesFixed in release 2.3.0.01023725 Fixed an issue where detached MTDs on the Thread network hit an assert while re-attaching to the OTBR after the OTBR is rebooted.1079667 Fixed an issue where devices can no longer communicate after reporting transient out-of-buffers condition.1084368 Fixed failing HomeKit HCA test when using board 4186c and the DMP application.1095059 Added openthread 'diag stream' and 'diag cw' CLI commands. See Improvements section for additional details.1113046 Radio PAL now maintains max channel power table.1126570 Addressed a memory leak associated with PSA keys which occurs when otInstanceFinalise() is called without power cycling.1133240 Fixed a bug in setting link parameters in the meshcop forwarding layer.1139318 Request to Reduce Codesize of Certified OpenThread Library. See Improvements section for additional details. 1139449 Fixed an issue where devices stopped receiving during Tx storm.1142231 Radio SPINEL no longer asserts when no entries are available in source match table.Known Issues in the Current Release 4 Known Issues in the Current ReleaseIssues in bold were added since the previous release. If you have missed a release, recent release notes are available on https:///developers/thread in the Tech Docs tab.482915 495241 A known limitation with the UART driver can causecharacters to be lost on CLI input or output. This canhappen during particularly long critical sections thatmay disable interrupts, so it can be alleviated byrepeating the CLI or waiting long enough for statechanges.No known workaround754514 Double ping reply observed for OTBR ALOC address. No known workaround815275 Ability to modify the Radio CCA Modes at compile-time using a configuration option in Simplicity Studio is cur-rently not supported. Use the SL_OPENTHREAD_RADIO_CCA_MODE configuration option defined in openthread-core-efr32-config.h header file included with your project.1041112 OTBR / EFR32 RCP can miss forwarding packets froma CSL child if it configures an alternate channel for CSLcommunication.Due to this issue, OTBRs based on GSDK 4.2.0.0 arenot expected to pass Thread 1.2 certification unless thecustomer use cases demand a waiver to exclude alltests that require changing the primary channel. Avoid configuring alternate CSL channels until this issue is addressed.1094232 Intermittently, ot-ctl terminates after a factoryresetwhen using a CPCd connection.No known workaround1064242 OpenThread prefix commands sometimes fail to addprefix for OTBR over CPC.No known workaround1117447 Outgoing key index can be set to 0 under unknowncircumstances.No known workaround1132004 RCP can become unresponsive when receiving excessive beacon requests. This issue was seen with 3 devices sending beacons requests every 30 ms. Workaround is to reduce the number of beacon requesters and/or increase time between the requests.1143008 The OTBR can sometimes fail to transmit a CSL packet with the error "Handle transmit done failed:Abort". This could happen ifOPENTHREAD_CONFIG_MAC_CSL_REQUEST_AHEAD_US is set to low. SetOPENTHREAD_CONFIG_MAC_CSL_REQUEST_AHEAD_US to 5000.For the OTBR, you can either:1. Modify the value ofOPENTHREAD_CONFIG_MAC_CSL_REQUEST_AHEAD_US in ot-br-posix/third_party/openthread/repo/src/core/config/mac.hor2. Pass the value during setup as follows:sudo OTBR_OPTIONS="-DCMAKE_CXX_FLAGS='-DOPENTHREAD_CONFIG_MAC_CSL_REQUEST_AHEAD_ US=5000'" ./script/setup1148720 Intermittently, SED current draw is too high. No known workaroundDeprecated Items 5 Deprecated ItemsNone.Removed Items 6 Removed ItemsRemoved in release 2.3.0.0•The ot-remote-cli component has been removed. There is no replacement for this component because the functionality provided by the component is no longer required.•The Silicon Labs HomeKit extension is no longer included with this release.7 Multiprotocol Gateway and RCP7.1 New ItemsAdded in release 2.3.0.0Added a new application z3-light_ot-ftd_soc that demonstrates Zigbee and OpenThread Concurrent Multiprotocol functionality. It features a router on the Zigbee side and a Full Thread Device (FTD) on the OpenThread side. See the project description or app/framework/sce-narios/z3/z3-light_ot-ftd_soc/readme.html for details.First GA-quality release of CPC GPIO Expander module. The Co-Processor Communication (CPC) General Purpose Input/Output (GPIO) Expander is a software component designed to enable a Host device to utilize a Secondary device's GPIOs as if they were its own. With the CPC GPIO Expander, the Host device can seamlessly integrate with the Secondary device and make use of its GPIO capabilities. See https:///SiliconLabs/cpc-gpio-expander/README.md for documentation.Added antenna diversity and coex EZSP command support to Zigbeed.Added better assert reporting to Zigbeed.Added bt_host_empty application (option: -B for the run.sh script) to the multiprotocol docker container.Zigbeed now includes an implementation of emberGetRestoredEui64() which loads the CREATOR_STACK_RESTORED_EUI64 token from the host_token.nvm file.The multiprotocol container now sets the size of syslog to 100 MB by default. Users are able to change the size by modifying the "/etc/logrotate.d/rsyslog" and "/etc/rsyslog.d/50-default.conf" files and restarting the rsyslog service inside the container.7.2 ImprovementsChanged in release 2.3.0.0Reduced CPC Tx and Rx queue sizes to fit the DMP NCP on the MG13 family.Configured options on the multiprotocol RCP projects to provide ~3.3k in RAM savings, particularly for the MG1 part. This was accom-plished by•Reducing•The number of user CPC endpoints to 0•Tx CPC queue size to 15 from 20•Rx buffer count to 15•Disabling OpenThread RTT logsFor further savings, customers can look into reducing the Tx and Rx queue sizes further. Note that the downside to this change would be a reduction in message throughput due to added retries. Also, customers can look into reducing the NVM cache size based on need. As a last resort, customers may also choose to disable CPC security on both the RCP and the host. We do not recommend the last option.Changed zigbee_ble_event_handler to print scan responses from legacy advertisements in the DMPLight(Sed) app.The rcp-xxx-802154 apps now by default support 192 µsec turnaround time for non-enhanced acks while still using 256 µsec turnaround time for enhanced acks required by CSL.7.3 Fixed IssuesFixed in release 2.3.0.01078323 Resolved issue where Z3GatewayCPC asserts when there is a communication failure with the NCP during address table initialization. We will now try to reconnect to the NCP upon failure.1080517 Z3GatewayCPC now automatically handles a reset of the NCP (CPC secondary).1117789 Fixed an issue where modifying OPENTHREAD_CONFIG_PLATFORM_RADIO_SPINEL_RX_FRAME_BUFFER_SIZE caused a linker error when building Zigbeed.1118077 In the CMP RCP, Spinel messages were being dropped under heavy traffic load due to CPC not keeping up with the incoming packets. Fixed this by bundling all Spinel messages ready to be sent over CPC into one payload on the RCP and unbundling them on the host. This dramatically improves the efficiency of CPC so that it can keep up with the incoming radio traffic.1129821 Fixed null pointer dereference in Zigbeed in an out-of-buffer scenario while receiving packets.1139990 Fixed an assert in the OpenThread Spinel code that could be triggered when joining many Zigbee devices simultaneously.1144268 Fixed an issue where excessive radio traffic can cause the Zigbee-BLE NCP to get into a state where it continually executes the NCP and CPC initialization.1147517 Fixed an issue with Z3GatewayCPC on startup that could cause the reset handling of the secondary to not work correctly.7.4 Known Issues in the Current ReleaseIssues in bold were added since the previous release. If you have missed a release, recent release notes are available on https:///developers/gecko-software-development-kit.811732 Custom token support is not available when using Zigbeed. Support is planned in a future release.937562 Bluetoothctl ‘advertise on’ command fails with rcp-uart-802154-blehci app on Raspberry Pi OS 11.Use btmgmt app instead of bluetoothctl.1074205 The CMP RCP does not support two networks on the same PAN id. Use different PAN ids for each network. Support is planned in a future release.1122723 In a busy environment the CLI can become unresponsive in the z3-light_ot-ftd_soc app. This app is released as experimental quality and the issue will be fixed in a future release.1124140 z3-light_ot-ftd_soc sample app is not able to form theZigbee network if the OT network is up already.Start the Zigbee network first and the OT network after.1129032 Experimental concurrent listening feature on xG24 de-vices is disabled in this release.Support is planned in a future release.1143857 Antenna Diversity is not available on the CMP RCP forxG21 and xG24 parts, since the antenna diversityhardware is used for concurrent listening.Intended behavior.7.5 Deprecated Items None7.6 Removed Items None8 Using This ReleaseThis release contains the following•Silicon Labs OpenThread stack•Silicon Labs OpenThread sample applications•Silicon Labs OpenThread border routerFor more information about the OpenThread SDK see QSG170: Silicon Labs OpenThread QuickStart Guide. If you are new to Thread see UG103.11: Thread Fundamentals.8.1 Installation and UseThe OpenThread SDK is part of the Gecko SDK (GSDK), the suite of Silicon Labs SDKs. To quickly get started with OpenThread and the GSDK, start by installing Simplicity Studio 5, which will set up your development environment and walk you through GSDK installation. Simplicity Studio 5 includes everything needed for IoT product development with Silicon Labs devices, including a resource and project launcher, software configuration tools, full IDE with GNU toolchain, and analysis tools. Installation instructions are provided in the online Simplicity Studio 5 User’s Guide.Alternatively, Gecko SDK may be installed manually by downloading or cloning the latest from GitHub. See https:///Sili-conLabs/gecko_sdk for more information.The GSDK default installation location has changed beginning with Simplicity Studio 5.3.•Windows: C:\Users\<NAME>\SimplicityStudio\SDKs\gecko_sdk•MacOS: /Users/<NAME>/SimplicityStudio/SDKs/gecko_sdkDocumentation specific to the SDK version is installed with the SDK. API references and other information about this release are available on https:///openthread/2.1/.8.2 OpenThread GitHub RepositoryThe Silicon Labs OpenThread SDK includes all changes from the OpenThread GitHub repo (https:///openthread/openthread) up to and including commit dae3ff2c5. An enhanced version of the OpenThread repo can be found in the following Simplicity Studio 5 GSDK location:<GSDK Installation Location>\util\third_party\openthread8.3 OpenThread Border Router GitHub RepositoryThe Silicon Labs OpenThread SDK includes all changes from the OpenThread border router GitHub repo (https:///openthread/ot-br-posix) up to and including commit de7cd7b20. An enhanced version of the OpenThread border router repo can be found in the following Simplicity Studio 5 GSDK location:<GSDK Installation Location>\util\third_party\ot-br-posix8.4 Using the Border RouterFor ease of use, Silicon Labs recommends the use of a Docker container for your OpenThread border router. Refer to AN1256: Using the Silicon Labs RCP with the OpenThread Border Router for details on how to set up the correct version of OpenThread border router Docker container. It is available at https:///r/siliconlabsinc/openthread-border-router.If you are manually installing a border router, using the copies provided with the Silicon Labs OpenThread SDK, refer to AN1256: Using the Silicon Labs RCP with the OpenThread Border Router for more details.Although updating the border router environment to a later GitHub version is supported on the OpenThread website, it may make the border router incompatible with the OpenThread RCP stack in the SDK.8.5 NCP/RCP SupportThe OpenThread NCP support is included with OpenThread SDK but any use of this support should be considered experimental. The OpenThread RCP is fully implemented and supported.8.6 Security InformationSecure Vault IntegrationWhen deployed to Secure Vault High devices, sensitive keys are protected using the Secure Vault Key Management functionality. The following table shows the protected keys and their storage protection characteristics.Thread Master Key Exportable Must be exportable to form the TLVsPSKc Exportable Must be exportable to form the TLVsKey Encryption Key Exportable Must be exportable to form the TLVsMLE Key Non-ExportableTemporary MLE Key Non-ExportableMAC Previous Key Non-ExportableMAC Current Key Non-ExportableMAC Next Key Non-ExportableWrapped keys that are marked as “Non-Exportable” can be used but cannot be viewed or shared at runtime.Wrapped keys that are marked as “Exportable” can be used or shared at runtime but remain encrypted while stored in flash.For more information on Secure Vault Key Management functionality, see AN1271: Secure Key Storage.Security AdvisoriesTo subscribe to Security Advisories, log in to the Silicon Labs customer portal, then select Account Home. Click HOME to go to the portal home page and then click the Manage Notifications tile. Make sure that ‘Software/Security Advisory Notices & Product Change Notices (PCNs)’ is checked, and that you are subscribed at minimum for your platform and protocol. Click Save to save any changes.8.7 SupportDevelopment Kit customers are eligible for training and technical support. Use the Silicon Laboratories Thread web page to obtain infor-mation about all Silicon Labs OpenThread products and services, and to sign up for product support.You can contact Silicon Laboratories support at /support.Silicon Laboratories Inc.400 West Cesar Chavez Austin, TX 78701USA IoT Portfolio /IoT SW/HW /simplicity Quality /quality Support & Community /communityDisclaimerSilicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software imple-menters using or intending to use the Silicon Labs products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and “Typical” parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Labs reserves the right to make changes without further notice to the product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Without prior notification, Silicon Labs may update product firmware during the manufacturing process for security or reliability reasons. Such changes will not alter the specifications or the performance of the product. Silicon Labs shall have no liability for the consequences of use of the infor -mation supplied in this document. This document does not imply or expressly grant any license to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any FDA Class III devices, applications for which FDA premarket approval is required or Life Support Systems without the specific written consent of Silicon Labs. A “Life Support System” is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons. Silicon Labs disclaims all express and implied warranties and shall not be responsible or liable for any injuries or damages related to use of a Silicon Labs product in such unauthorized applications. Note: This content may contain offensive terminology that is now obsolete. Silicon Labs is replacing these terms with inclusive language wherever possible. For more information, visit /about-us/inclusive-lexicon-projectTrademark InformationSilicon Laboratories Inc.®, Silicon Laboratories ®, Silicon Labs ®, SiLabs ® and the Silicon Labs logo ®, Bluegiga ®, Bluegiga Logo ®, EFM ®, EFM32®, EFR, Ember ®, Energy Micro, Energy Micro logo and combinations thereof, “the world’s most energy friendly microcontrollers”, Redpine Signals ®, WiSeConnect , n-Link, ThreadArch ®, EZLink ®, EZRadio ®, EZRadioPRO ®, Gecko ®, Gecko OS, Gecko OS Studio, Precision32®, Simplicity Studio ®, Telegesis, the Telegesis Logo ®, USBXpress ® , Zentri, the Zentri logo and Zentri DMS, Z-Wave ®, and others are trademarks or registered trademarks of Silicon Labs. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. Wi-Fi is a registered trademark of the Wi-Fi Alliance. All other products or brand names mentioned herein are trademarks of their respective holders.。
Open Stage 40 HFA 用户操作指南(中文)
16
七. 呼叫转移
• 编辑呼叫转移 1）打开 Program/Service 菜单
Destinations
Call forwarding
Enter Destination 输入转移选择目的地号码，外线需要加拨出局号 不同类型的呼叫转移可以通 Next 过 forwarding type 进行选择 * 呼叫转移类型： All Calls 所有呼叫转移，Busy 遇忙呼叫转移，No reply 无应答呼叫转移 • 开启呼叫转移
打开/关闭麦克风（静音键）：按
结束通话：按 键或按
键。
键 或 放回手柄。
Copyright © Unify. All rights reserved
13
四. 呼叫转接
通话状态下，选择 Consultation 输入转接目的地号码，并按OK键确认。
目的地方应答： 您可以告知对方您将要转接一个电话给他，然后挂机，完成转接。 目的地方无应答： 您无需等待对方接起，在听到回铃后挂机，也可以完成转接。
按
键开启
• 取消呼叫转移 按 键，LED 灯熄灭
Copyright © Unify. All rights reserved
17
八. 电话列表
进入电话列表： 按 键： 屏幕显示：未接 呼入 呼出 通过上下键选择所需查询的项目 Output 拨号：选择 查看具体信息：直接选择并按OK进入 删除：选择
19
十.速拨
• 有以下两种方式：
1）按话机第三个可编程键+速拨号码+分机号码 2）拨*800+速拨号码+分机号码
速拨号码
391 411 412 491 492 493 494
opensips文档
1.下载安装文件通过svn下载源码#svn co https:///svnroot/opensips/trunk opensips_head2.基本安装需求库libmysqlclient-devmysql-client-5.1mysql-server-5.1bisonflexlibncurses5-dev3.安装#make#make all include_modules="db_mysql";#make install include_modules="db_mysql"安装成功的安装目录，默认为/usr/local/etc4.配置配置opensipsctlrc文件位置/usr/local/etc/opensips/opensipsctlrc，增加对数据库支持# $Id: opensipsctlrc 8289 2011-08-23 14:13:17Z razvancrainea $## The OpenSIPS configuration file for the control tools.## Here you can set variables used in the opensipsctl and opensipsdbctl setup# scripts. Per default all variables here are commented out, the control tools # will use their internal default values.## your SIP domain# SIP_DOMAIN=## chrooted directory# $CHROOT_DIR="/path/to/chrooted/directory"## database type: MYSQL, PGSQL, ORACLE, DB_BERKELEY, or DBTEXT,## by default none is loaded# If you want to setup a database with opensipsdbctl, you must at least specify # this parameter.DBENGINE=MYSQL## database hostDBHOST=localhost## database name (for ORACLE this is TNS name)DBNAME=opensips# database path used by dbtext or db_berkeleyDB_PATH="/usr/local/etc/opensips/dbtext"## database read/write userDBRWUSER=opensips## password for database read/write userDBRWPW="opensipsrw"## database super user (for ORACLE this is 'scheme-creator' user) DBROOTUSER="root"# user name columnUSERCOL="username"# SQL definitions# If you change this definitions here, then you must change them# in db/schema/entities.xml too.# FIXME# FOREVER="2020-05-28 21:32:15"# DEFAULT_ALIASES_EXPIRES=$FOREVER# DEFAULT_Q="1.0"# DEFAULT_CALLID="Default-Call-ID"# DEFAULT_CSEQ="13"# DEFAULT_LOCATION_EXPIRES=$FOREVER# Program to calculate a message-digest fingerprint# MD5="md5sum"# awk tool# AWK="awk"# grep tool# GREP="grep"# sed tool# SED="sed"# Describe what additional tables to install. Valid values for the variables# below are yes/no/ask. With ask (default) it will interactively ask the user# for an answer, while yes/no allow for automated, unassisted installs.## If to install tables for the modules in the EXTRA_MODULES variable.# INSTALL_EXTRA_TABLES=ask# If to install presence related tables.# INSTALL_PRESENCE_TABLES=ask# Define what module tables should be installed.# If you use the postgres database and want to change the installed tables,# then you must also adjust the STANDARD_TABLES or EXTRA_TABLES variable# accordingly in the opensipsdbctl.base script.# opensips standard modules# STANDARD_MODULES="standard acc domain group permissions registrar usrloc # msilo alias_db uri_db speeddial avpops auth_db pdt dialog # dispatcher dialplan drouting nathelper load_balancer"# opensips extra modules# EXTRA_MODULES="imc cpl siptrace domainpolicy carrierroute userblacklist b2b"## type of aliases used: DB - database aliases; UL - usrloc aliases## - default: none# ALIASES_TYPE="DB"## control engine: FIFO or UNIXSOCK## - default FIFO# CTLENGINE=xmlrpc## path to FIFO file# OSIPS_FIFO="/tmp/opensips_fifo"## MI_CONNECTOR control engine: FIFO, UNIXSOCK, UDP, XMLRPC# MI_CONNECTOR=FIFO:/tmp/opensips_fifo# MI_CONNECTOR=UNIXSOCK:/tmp/opensips.sock# MI_CONNECTOR=UDP:192.168.2.133:8000生成数据库脚本# opensipsdbctl createMySQL password for root:INFO: test server charsetINFO: creating database opensips ...INFO: Core OpenSIPS tables succesfully created.Install presence related tables? (y/n): yINFO: creating presence tables into opensips ...INFO: Presence tables succesfully created.Install tables for imc cpl siptrace domainpolicy carrierroute userblacklist? (y/n): y INFO: creating extra tables into opensips ...INFO: Extra tables succesfully created.配置opensips.cfg文件位置/usr/local/etc/opensips更改监听网卡接口# $Id: opensips.cfg 8758 2012-02-29 11:59:26Z vladut-paiu $## OpenSIPS residential configuration script# byOpenSIPSSolutions<***************************>## This script was generated via "make menuconfig", from# the "Residential" scenario.# You can enable / disable more features / functionalities by# re-generating the scenario with different options.### Please refer to the Core CookBook at:# /Resources/DocsCookbooks# for a explanation of possible statements, functions and parameters.######## Global Parameters #########debug=3log_stderror=nolog_facility=LOG_LOCAL0fork=yeschildren=4/* uncomment the following lines to enable debugging */#debug=6#fork=no#log_stderror=yes/* uncomment the next line to enable the auto temporary blacklisting of not available destinations (default disabled) */#disable_dns_blacklist=no/* uncomment the next line to enable IPv6 lookup after IPv4 dns lookup failures (default disabled) */#dns_try_ipv6=yes/* comment the next line to enable the auto discovery of local aliases based on revers DNS on IPs */auto_aliases=no#listen=udp:127.0.0.1:5060 # CUSTOMIZE MElisten=udp:172.16.1.12:5060 # CUSTOMIZE MEdisable_tcp=yesdisable_tls=yes####### Modules Section #########set module pathmpath="/usr/local/lib/opensips/modules/"#### SIGNALING moduleloadmodule "signaling.so"#### StateLess moduleloadmodule "sl.so"#### Transaction Moduleloadmodule "tm.so"modparam("tm", "fr_timer", 5)modparam("tm", "fr_inv_timer", 30)modparam("tm", "restart_fr_on_each_reply", 0) modparam("tm", "onreply_avp_mode", 1)#### Record Route Moduleloadmodule "rr.so"/* do not append from tag to the RR (no need for this script) */ modparam("rr", "append_fromtag", 0)#### MAX ForWarD moduleloadmodule "maxfwd.so"#### SIP MSG OPerationS moduleloadmodule "sipmsgops.so"#### FIFO Management Interfaceloadmodule "mi_fifo.so"modparam("mi_fifo", "fifo_name", "/tmp/opensips_fifo")#### URI moduleloadmodule "uri.so"modparam("uri", "use_uri_table", 0)#### USeR LOCation moduleloadmodule "usrloc.so"modparam("usrloc", "nat_bflag", 10)modparam("usrloc", "db_mode", 0)#### REGISTRAR moduleloadmodule "registrar.so"modparam("registrar", "tcp_persistent_flag", 7)/* uncomment the next line not to allow more than 10 contacts per AOR */ #modparam("registrar", "max_contacts", 10)54,1 18%#modparam("registrar", "max_contacts", 10)#### ACCounting moduleloadmodule "acc.so"/* what special events should be accounted ? */modparam("acc", "early_media", 0)modparam("acc", "report_cancels", 0)/* by default we do not adjust the direct of the sequential requests.if you enable this parameter, be sure the enable "append_fromtag"in "rr" module */modparam("acc", "detect_direction", 0)modparam("acc", "failed_transaction_flag", 3)/* account triggers (flags) */modparam("acc", "log_flag", 1)modparam("acc", "log_missed_flag", 2)####### Routing Logic ######### main request routing logicroute{if (!mf_process_maxfwd_header("10")) {sl_send_reply("483","Too Many Hops");exit;}if (has_totag()) {# sequential request withing a dialog should# take the path determined by record-routingif (loose_route()) {if (is_method("BYE")) {setflag(1); # do accounting ...setflag(3); # ... even if the transaction fails107,1 36%setflag(1); # do accounting ...setflag(3); # ... even if the transaction fails} else if (is_method("INVITE")) {# even if in most of the cases is useless, do RR for# re-INVITEs alos, as some buggy clients do change route set# during the dialog.record_route();}# route it out to whatever destination was set by loose_route()# in $du (destination URI).route(1);} else {if ( is_method("ACK") ) {if ( t_check_trans() ) {# non loose-route, but stateful ACK; must be an ACK after# a 487 or e.g. 404 from upstream servert_relay();exit;} else {# ACK without matching transaction -># ignore and discardexit;}}sl_send_reply("404","Not here");}exit;}# CANCEL processingif (is_method("CANCEL")){if (t_check_trans())t_relay();exit;}t_check_trans();if ( !(is_method("REGISTER") ) ) {if (from_uri==myself){} else {# if caller is not local, then called number must be localif (!uri==myself) {send_reply("403","Rely forbidden");exit;160,5-33 55%send_reply("403","Rely forbidden");exit;}}}# preloaded route checkingif (loose_route()) {xlog("L_ERR","Attempt to route with preloaded Route's [$fu/$tu/$ru/$ci]");if (!is_method("ACK"))sl_send_reply("403","Preload Route denied");exit;}# record routingif (!is_method("REGISTER|MESSAGE"))record_route();# account only INVITEsif (is_method("INVITE")) {setflag(1); # do accounting}if (!uri==myself) {append_hf("P-hint: outbound\r\n");route(1);}# requests for my domainif (is_method("PUBLISH|SUBSCRIBE")){sl_send_reply("503", "Service Unavailable");exit;}if (is_method("REGISTER")){if ( 0 ) setflag(7);if (!save("location"))sl_reply_error();exit;}if ($rU==NULL) {# request with no Username in RURI213,5-33 73%if ($rU==NULL) {# request with no Username in RURIsl_send_reply("484","Address Incomplete");exit;}# do lookup with method filteringif (!lookup("location","m")) {t_newtran();t_reply("404", "Not Found");exit;}# when routing via usrloc, log the missed calls alsosetflag(2);route(1);}route[1] {# for INVITEs enable some additional helper routesif (is_method("INVITE")) {t_on_branch("2");t_on_reply("2");t_on_failure("1");}if (!t_relay()) {send_reply("500","Internal Error");};exit;}branch_route[2] {xlog("new branch at $ru\n");}266,2-9 91%}onreply_route[2] {xlog("incoming reply\n");}failure_route[1] {if (t_was_cancelled()) {exit;}# uncomment the following lines if you want to block client# redirect based on 3xx replies.##if (t_check_status("3[0-9][0-9]")) {##t_reply("404","Not found");## exit;##}}启动和停止服务# opensipsctl startINFO: Starting OpenSIPS :INFO: started (pid: 28301)# opensipsctl stopINFO: Stopping OpenSIPS :INFO: stopped。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
OpenStage HFA/SIPThe Open Unified Communications telephonesOpenStage is a new generation of phones which sets the benchmark for open and unified communications. These stylish devices provide an intuitive and engaging communication experience, incorporating innovative features.OpenStage is the prelude of a new era of high value in people-centric communication solutions.Siemens Enterprise CommunicationsOverview of OpenStageThe OpenStage family is intuitive in func-tionality and interface, integrated through interoperability with other devices, and multimodal to allow access to various ser-vices and applications.The OpenStage family is designed to be extremely user friendly and simplify fea-ture implementation. Sensorial interfaces based on advanced technology solutions (touch keys, embedded color LEDs, Touch-Slider for volume control and TouchGuide navigator) as well as large, tiltable, backlit color graphical displays in TFT technology facilitate user interaction.Soft-labeled (paperless phone) touch sen-sor keys can be easily programmed for spe-cific phone functions, line/feature access or speed dial by name. An ideal solution for office applications where mobility and flex-ibility are important factors.Fixed feature/function keys enable easy access to frequently used phone functions such as Drop/Release, Call Forwarding, Speaker and dedicated applications such as Phonebook, Call Log/History, Answering Machine.OpenStage incorporates the latest develop-ments in leading edge acoustics to ensure delivery of the very best voice quality on the handset and speakerphone (thanks to the handset design, speaker model, hous-ing dimensions and G.722 wideband codec). A high quality speakerphone is built in as standard in all models (exception OpenStage 20E).OpenStage design highlights include varia-tion of materials and colors (from molded plastic in ice blue or lava to high-end silver blue metallic lacquering and brushed alu-minum).The OpenStage IP phone family comprisesthe following models:•OpenStage 15 (ice blue or lava)•OpenStage 20E (ice blue or lava)•OpenStage 20 (ice blue or lava)•OpenStage 40 (ice blue or lava)•OpenStage 60 (ice blue or lava)•OpenStage 80 (silver-blue metallic)Each model is available as a phone variantwith the open standards for SIP voice com-munication or with the proprietary proto-col of Siemens Enterprise Communications(CorNet-IP, also known as HFA = HiPathFeature Access).In addition to the standard-based SIP(RFC 3261) VoIP protocol, OpenStage SIPphones support even more features such asconsultation, local 3-way conference, mul-tilines and team features that allow a highdegree of flexibility in your IT strategy.The OpenStage CorNet-IP variants provideaccess to the feature rich HiPath platforms2000, 3000, 4000, 5000 and HiPath Ope-nOffice EE, ME with the benefit of an intui-tive user interface.Each OpenStage IP phone provides an inte-grated Ethernet switch. The network isaccessed by 10/100 Base-T or as a variantvia Gigabit Ethernet (exceptions:OpenStage 15 and OpenStage 20E).All phones support 802.3af Power overLAN.OpenStage is easy to deploy and ongoingadministration is simple.OpenStage devices can be centrally man-aged as part of an IT environment.OpenStage 15 E is a universal solution forefficient and professional telephony. Eachsucceeding model has increased featurecapabilities and perceived value culminat-ing in the high-end OpenStage 80 modeltargeted at top level managers and execu-tives.Product familyOpenStage 15OpenStage 15 is a full-featured speaker-phone with display and eight function keyswith LEDs that could be used for line keyswhen operated as a multi-line telephone,for example.Display•Graphical display, 2 lines monochrome(not tiltable)Keys•Keypad• 3 fixed function keys with red LEDs•8 freely programmable keys with redLEDs (upgradeable with Key Module)•Paper labels•Control keys +/-•3navigation keysAcoustics•Hands free talking (full duplex)Wall-mountableOpenStage 15OpenStage 15ice bluelavaOpenStage 20, 20EOpenStage 20 is a well equipped speaker-phone. is a universal solution for efficient and professional telephony.Display•Tiltable graphical display, 2 lines mono-chrome Keys•Keypad•7 fixed function keys (partly equipped with red LEDs)•Control keys +/-•3-way navigatorAcoustics•Hands free talking (full duplex, Open-Stage 20 only)•Open listening (OpenStage 20, 20E)Wall-mountableOpenStage 40Customizable for various workplace envi-ronments OpenStage 40 is recommended for use as an office phone, e.g. for desk sharing, people working in teams or call center staff.Display•Tiltable graphical display, 6 lines mono-chrome, backlit •Optical call alertKeys•Keypad•8 fixed function keys (partly equipped with red LEDs)• 6 freely programmable touch keys (illu-minated) with red LEDs (function, speed dial or line keys)•Controlkeys+/-•5-way navigatorAcoustics•Hands free talking (full duplex)Interfaces•Headset jack Wall-mountableOpenStage 60 and 80OpenStage 60Offers top-notch functionality and innova-tions, combining a maximum of usability with a clear, intuitive and sleek design. An open application platform and personaliza-tion options make this phone the first choice for boss-secretary environments and people interacting with lots of other devices.OpenStage 80Premium features, materials and compo-nents turn this device into an extraordinary user experience. The best in class LCD dis-play and an open platform for productivity enhancing applications unlock the full business potential of the phone. Open interfaces for easy synchronization with other devices, like PDA and mobile phone are specially designed with the needs of the top level manager and executive in mind.OpenStage 20OpenStage 20ice bluelavaOpenStage 20E ice blueOpenStage 20ElavaOpenStage 40OpenStage 40ice bluelavaOpenStage 60OpenStage 60ice bluelavaOpenStage 80Display•OpenStage 60: Tiltable graphical color TFT display, 320 x 240 pixel (QVGA),backlit•OpenStage 80: Tiltable graphical color TFT display, 640 x 480 pixel (VGA), back-lit•Optical call alertKeys•Keypad• 6 fixed function keys (partly equipped with blue LEDs)•8 (OpenStage 60) and 9 (OpenStage 80) freely programmable touch keys (illumi-nated) with blue LEDs (function, speed dial or line keys)• 6 mode keys (touch keys, illuminated) with blue or blue/white LEDs (e.g. tostart applications)•TouchSlider for volume adjustment with blue/white LEDs•TouchGuide for navigationAcoustics•Hands free talking (full duplex)•Polyphonic ring tonesInterfaces•Headset jack•Bluetooth•USB MasterAccessoriesFor the respective OpenStage models a comprehensive range of accessories will be released separately. Here is a complete list of accessories:OpenStage Key Module 15•18 additional freely programmable keys with LEDs; function, speed dial or •line keys•Paper labels•In ice blue or lava•For OpenStage 15/40 (up to 1 unit can be connected)OpenStage KeyModule 40, 60, 80•12 additional freely programmable keys with LEDs; function, speed dial or linekeys (two-level)•Large graphical display for key labeling •In ice blue, lava or silver blue metallic •For OpenStage 40, 60, 80 (up to 2 units can be connected)OpenStage Busy Lamp Field 40•90 additional freely programmable keys with LEDs; function-, speed dial- or line keys•Paper labels•OpenStage 40 HFA only (not on HiPath4000)•In ice blue or lava•For OpenStage 40 (up to 1 unit can be connected)Wall mount kit•In ice blue or lava•For OpenStage 20, 20E, 40 OpenStage ManagerFor administration of OpenStage 80 and 60 the OpenStage Manager can be used:•Administer OpenStage Phone Book –Synchronize contacts–Edit PhoneBook–Add pictures•Manage polyphonic ring tones•Load screen saver pictures•Configure OpenStage phone•Backup/restore user dataOpenStage applicationsOpenStage is an extremely powerful plat-form for efficient business applications.The following applications are availablewith OpenStage 60, 80:•Graphical Call Handling–Context-sensitive menus–Simple use of complex phone fea-tures•Personal Phone Book–Enter up to 1,000 personal contactswith different telephone numbers–Combine Contacts into Groups–Add a picture to favorite contacts•Call Log/History–See the list of missed, forwarded,dialed and received calls–Dial from the Call Log List•Directory access (LDAP client)–Query corporate directories usingLDAP–Quick search and advanced searchwith various search criteria•Graphical voicemail control–Message Waiting Indication via LEDand icon on idle screen–Intuitive user interface with taperecorder look & feel–Support with HiPath Xpressions V5.0,V6.0•Bluetooth V2.0–Object Push Profile: Send and receivebusiness cards/vCards–Headset Profile: Connect a Bluetoothheadset•Application Platform for customer spe-cific workflow integration–OpenStage 60/80 allows the cus-tomer to integrate own XML applica-tions using the phone as an universalinput/output deviceHiPath SupportOpenStage SIP phones are supported by OpenScape Voice and Asterisk. OpenStage CorNet IP phones are supported by HiPath 2000, HiPath 3000, HiPath 4000, HiPath 5000, HiPath OpenOffice EE and HiPath OpenOffice ME.Public TelephoneNetwork Access/acoustics/speech quality•FCC Part 68/CS-03 (Technical Require-ments for Connection of Terminal Equip-ment to the Telephone Network)•TIA/EIA-810A (Transmission Require-ments for Narrowband VoIP and Voiceover PCM Digital Wireline Telephones)•TBR8 (Telephony 3.1 kHz teleservices;attachment requirements for handsetterminals)•Hearing aid capability (HAC) accordingTIA/EIA-504A (Electronic industriesassociation recommended standardRS-504 magnetic field intensity criteriafor telephone compatibility with hearingaids)Technical DataOpenStage 15OpenStage 20OpenStage 20EOpenStage 40OpenStage 60OpenStage 80 DisplayTiltable display (pixels, type) 2 lines,205*41 pixels(not tiltable, fixedviewing angle of30°)2 lines,205 x 41 pixels6 lines,240 x 128 pixels320 x 240 pixels(QVGA)color TFT 5.7”640 x 480 pixels(VGA)color TFT 6.4”Backlit––Yes Yes Yes Keys/LEDsFixed function keys (pushbuttons, partly illuminated)33 red LEDs75 red LEDs86 red LEDs65 blue LEDs65 blue LEDsFreely programmable touch keys (illuminated)8 keyswith red LEDs–6keyswith red LEDs8 keyswith blue LEDs9 keyswith blue LEDsMode keys(touch keys, illuminated)––– 6 with blue orblue/white LEDs6 with blue orblue/white LEDsOptical call alert––red blue blueVolume adjustment+/- key+/- key+/- key TouchSliderblue/white LEDTouchSlider blue/white LEDNavigation element 3 keysfor navigation3-waynavigator5-waynavigatorTouchGuide TouchGuideInterfacesBluetooth V2.0(vCard support and headset profile)–––Yes Yes Headset jack for corded/cordless headsets––Yes Yes Yes USB Master–––Yes Yes OpenStage Key Module Yes (max. 1)–Yes (max. 2)Yes (max. 2)Yes (max. 2) OpenStage Busy Lamp Field (not forHiPath 4000, OpenStage 40 HFA only)––Yes(max.1)––Integrated Ethernet switch 10/100 Base-T10/100 Base-TorGigabit Ethernet(notOpenStage 20 E)(optionalvariant)10/100 Base-TorGigabit Ethernet(optionalvariant)10/100 Base-TorGigabit Ethernet(optionalvariant)10/100 Base-TorGigabit Ethernet(optionalvariant)CertificationsCE Mark, EMC EN55022 Class B, EN55024, EN61000-4-11, EN61000-3-2,Safety EN60950-1,North America EMC (FCC) Part 15 (CFR 47) Class B, Safety UL60950-1/CSA 22.2 No950 AudioG.711 (64 kbit/s a/µ-law) G.722 (64 kbit/s)G.729AB (8 kbit/s)YesYesYesYesYesYesYesYesYesYesYesYesYesYesYesOpen listening Yes Yes Yes Yes Yes Full duplex hands-free Yes Yes(notOpenStage 20 E)Yes Yes YesEcho canceling for local echo (AEC)full duplex YesYes (notOpenStage 20 E)YesYesYesApplicationssee section "OpenStage applications"–––Yes Yes Security featuresLayer 2 authentication (802.1x)Yes Yes Yes Yes Yes Network IEEE802.1QYes Yes Yes Yes Yes QoS(DIFFSERV and IEEE802.1p)Yes YesYesYesYesPower supplyExternal power supply unit (EU, US or UK)Yes Yes Yes Yes Yes Power over LAN: IEEE 802.3af Yes Yes Yes Yes Yes PoL class Class 1Class 1Class 2Class 3Class 3Technical dataDimensions(height x breadth x length [mm])70 x 240 x 22170 x 240 x 22070 x 270 x 22070 x 300 x 22070 x 300 x 220Weight (kg)0.7830.834 1.068 1.245 1.435Colorsice blue or lavaice blue or lavaice blue or lavaice blue or lavasilver blue metallicStorage conditions -40 °C to +70 °C (ETSI EN300 019-2-2)Operating conditions+5 °C to +40 °COpenStage 15OpenStage 20OpenStage 20E OpenStage 40OpenStage 60OpenStage 80Communication for the open mindedSiemens Enterprise CommunicationsSiemens Enterprise Communications is a premier provider of end-to-end enterprise communications solutions that useopen, standards-based architectures to unify communications and business applications for a seamless collaboration experi-ence. This award-winning “Open Communications” approach enables organizations to improve productivity and reduce costs foundation for the company’s OpenPath commitment that enables customers to mitigate risk and cost-effectively adopt uni-managed and outsource capability. Siemens Enterprise Communications is owned by a joint venture of The Gores Group and Siemens AG. The joint venture also encompasses Enterasys Networks, which provides network infrastructure and security systems, delivering a perfect basis for joint communications solutions.For more information about Siemens Enterprise Communications or Enterasys, please visit /open or Note: Siemens Enterprise Communications & Co K.G. is a trademark licensee of Siemens AG.respective holders.©Siemens EnterpriseCommunications GmbH & Co. KG Siemens EnterpriseCommunications GmbH & Co. KGis a Trademark Licensee of Siemens AG Hofmannstr. 5181359 Munich, GermanyThe information provided in this brochure contains merely general descriptions or characteristics of performance which in case of actual use do not always apply as described or which may change as a result of further development of the products. An obligation to provide the respective characteristics shall only exist if expressly agreed in the terms of contract. Availability trademarks of Siemens Enterprise Communications GmbH & Co. KG. All other company, brand, product and service names are trademarks or registered trademarks of their respective holders.。