AMX模块使用说明

AMX编程软件介绍+语法说明+实例x2 新建主机程序设计文件简介通过NetLinx Studio 新建程序选择New选择Source File，其它的为模块及包含文件设计，我们暂不管它。

Workspace Wizard是一个工程项目管理，可以把整个项目所涉及的文件管理起来，方便您查找，单独的Source File文件也是可以用的，我们先选择Source File是否创建新文件，选择Yes选择，主机的标准模版，网络型主机则选择NetLinx Standard Template输入文件名选择要保存的路径，按下一步。

点击完成，创建出新文件。

把蓝色的字给收起来，总体上我们可以看出分如下几块:PROGRAME_NAME为文件DEFINE_DEVICE为定义要控制设计的控制接口 DEFINE_CONSTANT为定义常量DEFINE_TYPE为定义类型文件DEFINE_VARIABLE为定义变量DEFINE_LATCHING为定义锁住键DEFINE_MUTUALLY_EXCLUSIVE为定义互锁DEFINE_START定义启动时需要执行的程序DEFINE_EVENT为定义事件语句DEFINE_PROGRAME为定义实时的程序语句所有的程序必须放在固定的定义下，如变量必须放在DEFINE_VARIABLE下，事件语句必须放在DEFINE_EVENT如何设置连接并设置固定IP 如何实现NetLinx Studio软件与中控主机的第一次连接:我们可以通过如下几种方式来进行连接:1. TCP/IP2. COM3. Moderom4. USB由于设备的出厂IP地址是设置为DHCP的，所以刚开始我们无法用网络来连接，如果您可以用分配IP的式给中控主机分配一个IP，就可以用刚络连上主机，再对主机进行固定IP设置，就可以直接用网络进行连接，因为通过串口或其它方式，在遇到大文件时传输得太慢，或者可能因为传输文件太大而导致传输失败。

AMX M‎o d Me‎t aMod‎半条命游戏‎(CS)插‎件是‎一个Met‎a Mod插‎件，允许你‎为游戏半条‎命和它的M‎o ds定义‎脚本，使用‎C ompu‎p hase‎'s Sm‎a llC脚‎本语言。

‎ 1. ‎介绍：关于‎1)‎AMX ‎M od X‎AM‎X Mod‎X是致力‎于服务器管‎理领域而开‎发的多功能‎半条命-M‎e tamo‎d插件。

‎它有强大的‎脚本兼容性‎，你可以按‎个人要求自‎己编写“插‎件” 或添‎加文件增加‎模块功能。

‎插件有如下‎种类:管理‎服务(增加‎新的管理命‎令)、各项‎统计(St‎a tsX)‎，娱乐附件‎(无敌模式‎等)，游戏‎方式更改(‎W C3, ‎C SDM)‎，当然还有‎很多其他种‎类！此外，‎你也可以编‎写模块来扩‎展AMX ‎M od X‎的功能。

‎2‎) AMX‎Mod ‎X and‎AMX ‎M od‎AMX ‎M od X‎的前身是‎A MX M‎O D——由‎O LO编写‎的同类半条‎命MOD。

‎但不幸的是‎，AMX ‎M OD项目‎后来陷入了‎一场所有人‎都不愿看到‎的危机（缺‎少公众参与‎，不公开源‎代码，没有‎专人来维护‎核心代码）‎。

而随着‎开发人员一‎个又一个失‎望而去，A‎M X MO‎D也显得死‎气沉沉，有‎鉴于此，一‎个新的项目‎A MX M‎O D X在‎万众期待中‎顺利开展。

‎从那时起‎，AMX ‎M OD X‎项目经历了‎无数的风风‎雨雨。

AM‎X MOD‎中几乎每一‎个部分不是‎从零做起，‎就是大幅‎改动以适应‎新的系统机‎制。

AMX‎MOD ‎X已不是昔‎日的AMX‎MOD,‎与其前身相‎比，AMX‎MOD ‎X肯定要更‎胜一筹，更‎为重要的是‎，它具有良‎好的向下兼‎容性。

‎ 2.介绍‎:特性‎a) ‎特性‎管理系统‎脚本‎/插件系统‎模‎块扩展系统‎基‎本管理命令‎，比如：‎封人‎，踢人‎打耳光‎/处死玩家‎聊‎天‎预留通道‎灌水‎保护‎武器禁用‎各‎项统计 (‎同Stat‎s Me) ‎动态‎菜单系统‎b)‎开发者特‎性A‎M X Mo‎d X 有‎一整套完善‎的API供‎开发者使用‎，借此你可‎以将模块与‎Meta‎m od 还‎有 AMX‎Mod ‎X联系起来‎。

AMX软件使用说明-bakAMX软件使用说明一、介绍AMX软件是一款功能强大的计算机辅助设计工具，用于创建和管理各种项目。

本文档将详细介绍AMX软件的安装、配置和使用方法。

二、安装1、确保计算机满足最低系统要求。

2、AMX软件安装程序。

3、执行安装程序并按照提示完成安装。

三、配置1、打开AMX软件。

2、在设置菜单中，选择适当的语言和界面选项。

3、设置用户权限和访问控制。

4、配置数据库连接，以便AMX软件可以连接到您的项目数据库。

四、创建项目1、在AMX软件中，“新建项目”按钮。

2、输入项目名称、描述和其他相关信息。

3、选择适当的项目类型。

4、配置项目属性和设置。

五、管理项目1、在项目列表中，选择要管理的项目。

2、在项目管理界面中，可以进行项目文件的、和删除操作。

3、添加和管理项目成员及其权限。

4、跟踪项目进度和任务分配。

六、导入和导出数据1、在AMX软件中，选择“导入”或“导出”选项。

2、选择要导入或导出的文件类型。

3、配置文件路径和其他相关参数。

4、执行导入或导出操作。

七、其他功能1、AMX软件提供了丰富的图形绘制和编辑工具，可以使用这些工具创建和编辑项目图表。

2、支持多种数据分析和报表功能，可根据需要进行统计和分析。

3、提供了协作和通信工具，方便项目团队成员之间的交流和协作。

附件：- AMX软件安装包- AMX软件用户手册法律名词及注释：1、著作权：指作者对其原创作品所享有的权利。

2、商标：指用于区别商品来源的标识、名称、符号或设计。

3、许可证：指授权他人使用特定权利或执行特定行为的证书。

4、法律责任：指依法承担因违反法律规定而产生的法律责任。

特别符号{ }大括号多条命令集的结合[ ]中括号设备,通道号[DEVICE,CHANNEL];数组的定义,如:INTEGER VOL[NUMBER];SYSTEM_CALL系统调用,如:SYSTEM_CALL[1] 'COSX'(45) ( )小括号IF条件语句；定义互锁语句(* *)或/* */注释对程序的必要说明,在程序中不起任何作用//注释单句注释运算符号常用关键字ON[DEVICE,CHANNEL] // 开OFF[DEVICE,CHANNEL] // 关PULSE[DEVICE,CHANNEL] // 发送脉冲TO [DEVICE,CHANNEL]// 按住多长时间执行多长SEND_COMMAND DEV, '<command string>'SEND_STRING DEV, '<string>'事件处理：BUTTON_EVENT这个关键字规定了一个按钮事件的处理。

它包括按下、释放、持续三个事件，在一个指定的设备通道上，这三个事件与按下和释放按钮是紧密相连的，按钮事件包含一个可选择的反馈信息处理，它在事件处理完成之后立即运行。

在任何时候主线运行了，这个反馈信息处理也被执行。

定义格式如下：BUTTON_EVENT [<device>,<channel>]{PUSH:{/* 当按钮按下去时执行的动作*/}RELEASE:{/* 当按钮松手时执行的动作*/}HOLD [<time>,[REPEAT]]:{/* 当按钮按住时过了多长时间/或每隔多长时间重复执行的动作*/}}Example：BUTTON_EVENT[TP,1]{PUSH: /* 按下触摸屏第一个通道时执行的动作*/{ON[RELAY,1]}}BUTTON_EVENT特性描述表：DATA_EVENT这个关键字规定了一个数据事件的处理。

Quick Start GuideMounting Options for V Style Mod ulesOverviewThis Quick Start Guide covers the four versatile mounting kit options that are availablefor mounting AMX V Style Modules of various heights and widths, including variousTransmitters, Receivers, Converters, DADs (Distribution Amplifier Drivers), andICSLan Device Control Boxes.•FG1010-720AVB-VSTYLE-RMK-1U, V Style Module Rack Mounting Tray KitRack mount various size modules side by side in a single rack unit.•FG1010-721AVB-VSTYLE-RMK-FILL-1U, V Style Module Tray with Fill Plates KitRack mount with blank fill plates (1 each: 1/12, 1/6, 1/4, 1/3 rack width).•FG1010-722AVB-VSTYLE-SURFACE-MNT, V Style Single Module Surface Mount KitMount a single module to the wall, under a desk, etc.•FG1010-723AVB-VSTYLE-POLE-MNT, V Style Single Module Pole Mounting KitMount a single module to a projector pole or other 2 inch diameter pipes.This Quick Start Guide contains complete information for installing these mountingkits.Note:Pictorial drawings with dimensions are available at .Tray (FG1010-720) and Tray with Fill Plates (FG1010-721)The Tray Kit can be ordered with or without fill plates. The Tray with Fill Plates Kitcontains a tray and plates in sizes that will fill out the tray for a professional lookinginstallation (fill plates come in 1/12, 1/6, 1/4, and 1/3 rack width sizes).Modules can be mounted in a tray facing either direction as illustrated in FIG. 1.Tip: If multiple fill plates are required, use a minimum of fill plates by selecting thelargest sizes that will fill the space first.To mount modules in a tray:1.Invert the module and the module rack mounting tray for ease of installation.2.Attach the rack mounting tray to the bottom of the module using the #4-403/16 inch undercut flat head screws (provided). Note that only two screws arerequired.3.Install the tray in a standard EIA 19 in. (48.26 cm) rack and secure with rack-mounting screws.4.Optional – attach fill plates using the #4-40 3/16 inch undercut flat head screws(provided). Be sure to use the screw holes closest to the front of the tray.Surface Mount (FG1010-722)Attaching bracketsThe Surface Mount Kit is designed for mounting a single module (to the wall, on orunder a desk, etc.) The kit contains brackets and screws. The brackets may beattached to mount the top or the bottom flush with the mounting surface.Important: Be careful not to block vent holes on the module when mounting.The following instructions can be used for attaching brackets when surface mountingor for pole mounting.Tip: Laying the module and brackets on a flat surface when you attach the bracketshelps align them.To attach brackets to a module:1.Insert the #4-40 3/16 inch pan head screws (provided) per FIG. 4 and tighten.Brackets can either align flush with the top or with the bottom.FIG. 1 Options for placing modules in the tray (shown with fill plates)FIG. 2Invert tray and module (and fill plates if applicable) for ease of installationFIG. 3 Attach brackets in either top or bottom position (various size modules shown)FIG. 4Insert screws and tightenFor full warranty information, refer to 10/11©2011 AMX. All rights reserved. AMX and the AMX logo are registered trademarks of AMX.AMX reserves the right to alter specifications without notice at any time.3000 RESEARCH DRIVE, RICHARDSON, TX 75082 • 800.222.0193 • fax 469.624.7153 • technical support 800.932.6993 • 93-1010-02REV: BMounting on SurfaceNote: The #8 x 1/2 inch tapping pan head screws provided for mounting to a flat surface are designed for wood. If the module needs to be mounted on a different type of surface, use the appropriate type of fastener, e.g., dry wall anchors (not provided).To mount a module with brackets to a flat surface:1.Place the module in the desired final position on the mounting surface and mark the screw position as indicated in FIG. 5.Important: The mark for the screw’s position in each of the mounting holes needs to be made in the end of the slots (all marks to either the top of the slots or all marks to the bottom).2.Set the module aside. If using the wood screws provided, drill pilot holes (drill size 29; hole diameter 0.136 in.) for the screws 1/2 inch (1.27 cm) deep. Start the screws in the holes. Do not tighten completely.3.Align the module with the center of the double key-hole slots over the screws and slide into place as indicated in FIG. 7.4.Tighten the screws.Pole Mount (FG1010-723)The Pole Mount Kit is designed for mounting a single module to a projector pipe (or other 2 inch diameter pipes). The kit contains all the mounting hardware for the assembly in FIG. 9.To mount a module using brackets and bolts:1.Attach the mounting brackets to the module according to the instructions for surface mounting (see FIG. 4).2.Insert the first u-bolt around the pole/pipe and through the bracket and plate according to FIG. 9.3.Fasten securely with the hex nuts.4.Repeat Steps 2 and 3 using the remaining u-bolt, bracket, plate, and hex nuts.FIG. 5 Mark screw positionsFIG. 6 Drill pilot holes and start screws, but do not tightenAlign module over screws and slide into place FIG. 8Tighten screwsFIG. 9 Mount to projector pipe with bolts through brackets。

OS Awareness Manual AMX Release 09.2023OS Awareness Manual AMXTRACE32 Online HelpTRACE32 DirectoryTRACE32 IndexTRACE32 Documents ......................................................................................................................OS Awareness Manuals ................................................................................................................OS Awareness Manual AMX (1)History (4)Overview (4)Brief Overview of Documents for New Users5 Supported Versions5Configuration (6)Manual Configuration6 Automatic Configuration7 Quick Configuration Guide7 Hooks & Internals of AMX8Features (9)Display of Kernel Resources9 Task Stack Coverage9 Task-Related Breakpoints10 Task Context Display11 Dynamic Task Performance Measurement12 Task Runtime Statistics13 Task State Analysis14 Function Runtime Statistics15 AMX specific Menu17AMX Commands (18)TASK.DBPool Display buffer pools18 TASK.DEVent Display event groups18 TASK.DEXChange Display message exchanges18 TASK.DMailBoX Display mailboxes19 TASK.DMPool Display memory pools20 TASK.DSEMaphore Display semaphores21 TASK.DSYStem Display system state21 TASK.DTask Display tasks22 TASK.DTIMer Display timers23AMX PRACTICE Functions (24)TASK.CONFIG()OS Awareness configuration information24OS Awareness Manual AMXVersion 09-Oct-2023 History04-Feb-21Removing legacy command T ASK.T ASKState.OverviewThe OS Awareness for AMX contains special extensions to the TRACE32 Debugger. This manual describes the additional features, such as additional commands and statistic evaluations.Brief Overview of Documents for New UsersArchitecture-independent information:•“Training Basic Debugging” (training_debugger.pdf): Get familiar with the basic features of a TRACE32 debugger.•“T32Start” (app_t32start.pdf): T32Start assists you in starting TRACE32 PowerView instances for different configurations of the debugger. T32Start is only available for Windows.•“General Commands” (general_ref_<x>.pdf): Alphabetic list of debug commands.Architecture-specific information:•“Processor Architecture Manuals”: These manuals describe commands that are specific for the processor architecture supported by your Debug Cable. T o access the manual for your processorarchitecture, proceed as follows:-Choose Help menu > Processor Architecture Manual.•“OS Awareness Manuals” (rtos_<os>.pdf): TRACE32 PowerView can be extended for operating system-aware debugging. The appropriate OS Awareness manual informs you how to enable theOS-aware debugging.Supported VersionsCurrently AMX is supported for:•AMX Version 3.04a on the Freescale Semiconductor 68332•AMX on the ARM 7•AMX on Freescale Semiconductor PowerPCConfigurationThe TASK.CONFIG command loads an extension definition file called “amx.t32” (directory“~~/demo/<processor>/kernel/amx”). It contains all necessary extensions.Automatic configuration tries to locate the AMX internals automatically. For this purpose all symbol tables must be loaded and accessible at any time the OS Awareness is used.If a system symbol is not available or if another address should be used for a specific system variable then the corresponding argument must be set manually with the appropriate address. In this case, use the manual configuration, which can require some additional arguments.If you want to display the OS objects “On The Fly” while the target is running, you need to have access to memory while the target is running. In case of ICD, you have to enable SYStem.MemAccess orSYStem.CpuAccess (CPU dependent).Manual ConfigurationFormat:TASK.CONFIG amx.t32 <magic_address> <args><magic_address>Specifies a memory location that contains the current running task. Thisaddress can be found at “cj_kdata+14”.<args>The configuration requires one additional argument that specifies an AMXinternal pointer. Give the label “cj_kdatp”.Manual configuration for the OS Awareness for AMX can be used to explicitly define some memorylocations. It is recommended to use automatic configuration.; manual configuration for AMX supporttask.config amx.t32 cj_kdata+14 cj_kdatpSee Hooks & Internals for details on the used symbols.Automatic ConfigurationFormat:TASK.CONFIG amx.t32For system resource display and trace functionality, you can do an automatic configuration of the OSAwareness. For this purpose it is necessary that all system internal symbols are loaded and accessible at any time, the OS Awareness is used. Each of the TASK.CONFIG arguments can be substituted by '0', which means that this argument will be searched and configured automatically. For a fully automatic configuration omit all arguments:; fully automatic configuration for AMX supporttask.config amxIf a system symbol is not available, or if another address should be used for a specific system variable, then the corresponding argument must be set manually with the appropriate address (see Manual Configura-tion).See also “Hooks & Internals” for details on the used symbols.Quick Configuration GuideT o get a quick access to the features of the OS Awareness for AMX with your application, follow the following roadmap:1.Copy the files “amx.t32” and “amx.men” to your project directory(from TRACE32 directory “~~/demo/<processor>/kernel/amx”).2.Start the TRACE32 Debugger.3.Load your application as normal.4.Execute the command “TASK.CONFIG ~~/demo/<cpu>/kernel/amx/amx.t32”(See “Automatic Configuration”).5.Execute the command “MENU.ReProgram ~~/demo/<cpu>/kernel/amx.men”(See “AMX Specific Menu”).6.Start your application.Now you can access the AMX extensions through the menu.In case of any problems, please carefully read the previous Configuration chapters.Hooks & Internals of AMXAll kernel resources are accessed through the kernel data pointer “cj_kdatp”.The magic location is calculated from “(*c_kdatp+0x14)”.For detecting a message exchanger task, the entry point of that task is compared to the message exchanger task entry point “cj_kpmxtask”). If this symbol is not available, the message exchanger tasks won’t be detected.In the statistics evaluations, the kernel state is derived from the location at “(*cj_kdatp)”.FeaturesThe OS Awareness for AMX supports the following features.Display of Kernel ResourcesThe extension defines new commands to display various kernel resources. Information on the following AMX components can be displayed:TASK.DSYStem system stateTASK.DTask T asksTASK.DTIMer TimerTASK.DMailBoX MailboxesTASK.DESChange Message exchangesTASK.DSEMaphor SemaphoresTASK.DEVent Event groupsTASK.DBPool Buffer poolsTASK.DMPool Memory poolsFor a description of the commands, refer to chapter “AMX Commands”.If your hardware allows memory access while the target is running, these resources can be displayed “On The Fly”, i.e. while the application is running, without any intrusion to the application.Without this capability, the information will only be displayed if the target application is stopped.Task Stack CoverageFor stack usage coverage of tasks, you can use the TASK.STacK command. Without any parameter, this command will open a window displaying with all active tasks. If you specify only a task magic number as parameter, the stack area of this task will be automatically calculated.T o use the calculation of the maximum stack usage, a stack pattern must be defined with the command TASK.STacK.PATtern (default value is zero).T o add/remove one task to/from the task stack coverage, you can either call the TASK.STacK.ADD or TASK.STacK.ReMove commands with the task magic number as the parameter, or omit the parameter and select the task from the TASK.STacK.* window.It is recommended to display only the tasks you are interested in because the evaluation of the used stack space is very time consuming and slows down the debugger display.Task-Related BreakpointsAny breakpoint set in the debugger can be restricted to fire only if a specific task hits that breakpoint. This is especially useful when debugging code which is shared between several tasks. T o set a task-related breakpoint, use the command:•Use a magic number, task ID, or task name for <task>. For information about the parameters, see “What to know about the Task Parameters” (general_ref_t.pdf).•For a general description of the Break.Set command, please see its documentation.By default, the task-related breakpoint will be implemented by a conditional breakpoint inside the debugger. This means that the target will always halt at that breakpoint, but the debugger immediately resumes execution if the current running task is not equal to the specified task.On some architectures, however, it is possible to set a task-related breakpoint with on-chip debug logic that is less intrusive. T o do this, include the option /Onchip in the Break.Set command. The debugger then uses the on-chip resources to reduce the number of breaks to the minimum by pre-filtering the tasks.Break.Set <address>|<range>[/<option>] /TASK <task>Set task-related breakpoint.NOTE:T ask-related breakpoints impact the real-time behavior of the application.For example, on ARM architectures: If the RTOS serves the Context ID register at task switches, and if the debug logic provides the Context ID comparison, you may use Context ID register for less intrusive task-related breakpoints:When single stepping, the debugger halts at the next instruction, regardless of which task hits this breakpoint. When debugging shared code, stepping over an OS function may cause a task switch andcoming back to the same place - but with a different task. If you want to restrict debugging to the current task, you can set up the debugger with SETUP .StepWithinTask ON to use task-related breakpoints for single stepping. In this case, single stepping will always stay within the current task. Other tasks using the same code will not be halted on these breakpoints.If you want to halt program execution as soon as a specific task is scheduled to run by the OS, you can use the Break.SetTask command.Task Context DisplayY ou can switch the whole viewing context to a task that is currently not being executed. This means that all register and stack-related information displayed, e.g. in Register , Data.List , Frame etc. windows, will refer to this task. Be aware that this is only for displaying information. When you continue debugging the application (Step or Go ), the debugger will switch back to the current context.T o display a specific task context, use the command:•Use a magic number, task ID, or task name for <task>. For information about the parameters, see “What to know about the Task Parameters” (general_ref_t.pdf).•To switch back to the current context, omit all parameters.T o display the call stack of a specific task, use the following command:If you’d like to see the application code where the task was preempted, then take these steps:eContextID ONEnables the comparison to the whole Context ID register.Break.CONFIG.MatchASID ONEnables the comparison to the ASID part only.TASK.List.tasks If TASK.List.tasks provides a trace ID (traceid column), thedebugger will use this ID for comparison. Without the trace ID,it uses the magic number (magic column) for comparison.Frame.TASK [<task>]Display task context.Frame /Task <task> Display call stack of a task.1.Open the Frame /Caller /Task<task> window.2.Double-click the line showing the OS service call.Dynamic Task Performance MeasurementThe debugger can execute a dynamic performance measurement by evaluating the current running task in changing time intervals. Start the measurement with the commands PERF.Mode TASK and PERF.Arm, and view the contents with PERF.ListTASK. The evaluation is done by reading the ‘magic’ location (= current running task) in memory. This memory read may be non-intrusive or intrusive, depending on the PERF.METHOD used.If PERF collects the PC for function profiling of processes in MMU-based operating systems(SYStem.Option.MMUSPACES ON), then you need to set PERF.MMUSPACES, too.For a general description of the PERF command group, refer to “General Commands Reference Guide P” (general_ref_p.pdf).Task Runtime StatisticsNOTE:This feature is only available, if your debug environment is able to trace taskswitches (program flow trace is not sufficient). It requires either an on-chip tracelogic that is able to generate task information (eg. data trace), or a softwareinstrumentation feeding one of TRACE32 software based traces (e.g. FDX orLogger). For details, refer to “OS-aware Tracing” (glossary.pdf).Based on the recordings made by the Trace (if available), the debugger is able to evaluate the time spent ina task and display it statistically and graphically.T o evaluate the contents of the trace buffer, use these commands:Trace.List List.TASK DEFault Display trace buffer and task switchesTrace.STATistic.TASK Display task runtime statistic evaluationTrace.Chart.TASK Display task runtime timechartTrace.PROfileSTATistic.TASK Display task runtime within fixed time intervalsstatisticallyTrace.PROfileChart.TASK Display task runtime within fixed time intervals ascolored graphTrace.FindAll Address TASK.CONFIG(magic) Display all data access records to the “magic”locationTrace.FindAll CYcle owner OR CYcle context Display all context ID records The start of the recording time, when the calculation doesn’t know which task is running, is calculated as “(unknown)”.Task State AnalysisThe time different tasks are in a certain state (running, ready , suspended or waiting) can be evaluated statistically or displayed graphically .This feature requires that the following data accesses are recorded:•All accesses to the status words of all tasks •Accesses to the current task variable (= magic address)Adjust your trace logic to record all data write accesses, or limit the recorded data to the area where all TCBs are located (plus the current task pointer).NOTE:This feature isonly available, if your debug environment is able to trace task switches and data accesses (program flow trace is not sufficient). It requires either an on-chip trace logic that is able to generate a data trace, or a softwareinstrumentation feeding one of TRACE32 software based traces (e.g. FDX orLogger ). For details, refer to “OS-aware Tracing” (glossary.pdf).Example: This script assumes that the TCBs are located in an array named TCB_array and consequently limits the tracing to data write accesses on the TCBs and the task switch.Break.Set Var.RANGE(TCB_array) /Write /TraceDataBreak.Set TASK.CONFIG(magic) /Write /TraceDataT o evaluate the contents of the trace buffer, use these commands:Trace.STATistic.TASKState Display task state statisticTrace.Chart.TASKState Display task state timechartThe start of the recording time, when the calculation doesn’t know which task is running, is calculated as “(unknown)”.Function Runtime StatisticsNOTE:This feature is only available, if your debug environment is able to trace taskswitches (program flow trace is not sufficient). It requires either an on-chip tracelogic that is able to generate task information (eg. data trace), or a softwareinstrumentation feeding one of TRACE32 software based traces (e.g. FDX orLogger). For details, refer to “OS-aware Tracing” (glossary.pdf).All function-related statistic and time chart evaluations can be used with task-specific information. The function timings will be calculated dependent on the task that called this function. T o do this, in addition to the function entries and exits, the task switches must be recorded.T o do a selective recording on task-related function runtimes based on the data accesses, use the following command:; Enable flow trace and accesses to the magic locationBreak.Set TASK.CONFIG(magic) /TraceDataT o do a selective recording on task-related function runtimes, based on the Arm Context ID, use the following command:; Enable flow trace with Arm Context ID (e.g. 32bit)ETM.ContextID 32T o evaluate the contents of the trace buffer, use these commands:The start of the recording time, when the calculation doesn’t know which task is running, is calculated as “(unknown)”.Trace.ListNesting Display function nestingTrace.STATistic.FuncDisplay function runtime statistic Trace.STATistic.TREEDisplay functions as call tree Trace.STATistic.sYmbol /SplitTASKDisplay flat runtime analysis Trace.Chart.FuncDisplay function timechart Trace.Chart.sYmbol /SplitTASK Display flat runtime timechartAMX specific MenuThe menu file “amx.men” contains a menu with AMX specific menu items. Load this menu with theMENU.ReProgram command.Y ou will find a new menu called AMX.•The Display menu items launch the kernel resource display windows.•The Stack Coverage submenu starts and resets the AMX specific stack coverage and provides an easy way to add or remove tasks from the stack coverage window.In addition, the menu file (*.men) modifies these menus on the TRACE32 main menu bar:•The Trace -> List submenu is changed. Y ou can additionally choose if you want a trace list window to show only task switches (if any) or task switches and defaults.•The Perf menu contains the additional submenus for task runtime statistics, task-related function runtime statistics and statistics on task states. For the function runtime statistics, a PRACTICEscript file called “men_ptfp.cmm” is used. This script file must be adapted to your application.AMX CommandsTASK.DBPoolDisplay buffer poolsDisplays a table with all created AMX buffer pools.TASK.DEVentDisplay event groups Displays a table with all created AMX event groups.TASK.DEXChangeDisplay message exchangesDisplays a table with all created AMX message exchanges.Format:TASK.DBPool Format:TASK.DEVent Format:TASK.DEXChangeTASK.DMailBoX Display mailboxes Format:TASK.DMailBoXDisplays a table with all created AMX mailboxes.TASK.DMPool Display memory pools Format:TASK.DMPoolDisplays a table with all created AMX memory pools.TASK.DSEMaphore Display semaphores Format:TASK.DSEMaphoreDisplays a table with all created AMX semaphores.TASK.DSYStem Display system state Format:TASK.DSYStemDisplays a system state summary for the current AMX system state.TASK.DTaskDisplay tasksDisplays a table with all AMX tasks or one task in detail.Without any parameters, a summary table of all created tasks is shown.The magic number is a unique ID to the OS Awareness to specify a specific task. It is notequal to the AMX task ID. A double click on the magic number or on the tag opens the detailed task window.If you specify a task magic number, a task ID or a task tag as parameter, this task is shown in detailed. Enclose a task tag in quotation marks. If a numerical parameter is detected to be a AMX task ID, this one will be used. All other numerical parameters are supposed to be a task magic number and are not checked for validation.Format:TASK.DispTask [<task >]<task >:<task_magic> | <task_id> | <task_name>TASK.DTIMer Display timers Format:TASK.DTIMerDisplays a table showing all defined AMX timers.Double click on the parameter to see a dump window on this address. Double click on the procedure to seea list window on this address.AMX PRACTICE FunctionsThere are special definitions for AMX specific PRACTICE functions.See also general TASK functions.TASK.CONFIG()OS Awareness configuration information Syntax:TASK.CONFIG(magic | magicsize | kdata)Parameter and Description:magic Parameter Type: String (without quotation marks).Returns the magic address, which is the location that contains thecurrently running task (i.e. its task magic number).magicsize Parameter Type: String (without quotation marks).Returns the size of the task magic number (1, 2 or 4).kdata Parameter Type: String (without quotation marks).Returns the address of the kernel data area.Return Value Type: Hex value.。

AMX系列简单中⽂操作⼿册AMX系列简单中⽂操作⼿册本操作⼿册适⽤于AMX系列模拟矩阵设备实现本地化（300⽶范围内）控制，⽤户端通过OSCAR菜单对服务器进⾏操作访问。

1、硬件连接AMX系列设备硬件包括三个组成部分：1）AMIQ-（PS/2、USB、VSN、WSN、SRL）服务器接⼝线缆2）AMX5000、AMX5010、AMX5020模拟矩阵交换机3）AMX5110、AMX5120⽤户⼯作站硬件安装步骤：1)把AMIQ-xxx服务器接⼝线缆与机房内的被控服务器的键盘、⿏标、显⽰器或console⼝相连；2)把AMIQ-xxx服务器接⼝线缆⽤普通五类线连接到AMX5000/AMX5010/AMX5020模拟矩阵交换机的被控端服务器端⼝；3)把AMX5000/AMX5010/AMX5020模拟矩阵交换机的⽤户控制端⼝⽤普通五类线连接到AMX5110/AMX5120⽤户⼯作站两个端⼝中的任意⼀个端⼝；4)把AMIQ-xxx服务器接⼝线缆与本地PC的键盘、⿏标、显⽰器；5)把（4）中的AMIQ-xxx服务器接⼝线缆⽤普通五类线与AMX5110/AMX5120的另⼀端⼝相连接；6)把控制终端（键盘、⿏标、显⽰器）连接到AMX5110/AMX5120⽤户⼯作站的控制端⼝，提供⽤户操作访问（本地PC或机房内的服务器）。

连接⽰意图，如下：2、OSCAR（On-Screen Configuration and Activity Reporting interface）菜单介绍2.1登陆系统（初始状态没有设定登陆界⾯）如下图所⽰：1)双击“CTRL”键，击活AMX的OSCAR菜单；2)输⼊⽤户名和密码（⽤户帐号由系统管理员分配）；3)点击“ok”登陆系统，出现OSCAR⽤户菜单界⾯。

2.2OSCAR菜单介绍登陆AMX系统后，出现OSCAR菜单界⾯，基本切换操作--选择相应的服务器，⽤⿏标点击“Connect”按钮或按键盘的回车键即可(见下图)。

AMX-FX2N系列使用手册[第3版]艾莫迅自动化科技（东莞）有限公司一、产品概叙 (1)二、产品型号 (2)三、产品图片 (2)3.1、产品图片 (2)3.2、AMX-FX2N-26MT-2AD-1DA电气接线图 (2)3.3、AMX-FX2N-26MT-2AD-1DA端子功能说明 (3)3.4、AMX-FX2N-26MT-2AD-1DA产品参数 (5)四、应用说明 (6)4.1、1路模拟输出 (6)4.2、2路模拟输入转换 (7)4.3、RS485口功能说明 (8)4.4、文本显示器 (8)4.5、MCGS触摸屏通讯 (9)4.6、Pro-face触摸屏通讯 (11)4.7、MODBUS485主站通讯 (13)4.8、MODBUS485从站通讯 (21)4.9、高速计数功能 (25)4.10、高速脉冲输出功能 (27)4.10.1、相关操作指令 (27)4.10.2、相关操作元件 (27)4.10.3、使用说明 (26)五、软元件列表 (28)5.1、元件说明 (28)5.2、特殊D寄存器说明 (29)5.3、特殊M元件说明 (34)六、指令表 (35)6.1、支持指令表 (35)6.2、暂不支持指令说明 (38)●MCU采用ARM32位工业处理器,可支持8000步程序。

●编程软件兼容三菱的Works2/Works3/GxDeveloper（支持在线写入）。

●编程线兼容三菱PLC下载线，方便快捷；连接触摸屏也兼容三菱通讯线。

●所有关键电子元器件均采用进口大品牌，质保3年。

●所有IO口用光电隔离器传输信号，有效滤除各种电磁干扰。

●输出晶体管采用高速大电流三极管，可以直接驱动各种直流电磁阀。

●输入支持共阴或共阳接法，方便使用；输出为NPN型集电极开路输出。

●2路12位模拟量输入（A/D），支持0~10V电压或0~20ma电流；拨码开关切换。

●1路12位模拟量输出(D/A)，同时输出0~10V电压和0~20ma电流，方便用户选择使用。

DXFP-RX-4K60 | 1 ○c 2021 AMX. All rights reservedDXLink TM 4K60 HDMI Fiber Receiver ModuleDXFP-RX-4K60 (FG1010-565-01)DXFP-RX-4K60-TAA (FG1010-565-02)OverviewThe DXLink 4K60 Fiber Receiver is HDMI 2.0 and HDCP 2.2 compliant. It supports 4K60 4:4:4 video and High Dynamic Range (HDR) for pixel-for-pixel image reproduction without chroma subsampling. It receives audio, video, control, USB 2.0, and Ethernet over duplex fiber from a DXLink 4K60 Fiber transmitter up to 550 meters away. This module includes a Multi-Mode Duplex (MMD) SFP+ module, which can be replaced with a Single-Mode Duplex (SMD) SFP+ module if needed.Common ApplicationsFiber uses light to distribute data, rather than electric signals making it both the highest quality and most secure way to route video as it is not susceptible to electronic noise or non-intrusive physical wiretapping. This module is compatible with DGX DXLink 4K60 Fiber output cards and DXLink 4K60 Fiber transmitters. It is ideal for applications where the demands of high-resolution video clarity, long distance transmission, and maximum security need to be met without compromise, including campus-wide distribution of sources that are shared between classrooms, secure military applications, casinos, arenas, and museums.Features•4K@60Hz 4:4:4 8bit and HDCP 2.2 with Display Stream Compression (DSC) - Visually lossless compression and future-proof support. •Only one cable - Receive audio, video, control, USB 2.0, and Ethernet over one optical cable up to 300m for OM3 and 550m for OM4. •Industry Leading Data Rate – DXLink is leading the way with an optical transport rate of 10 Gbps. • SmartScale Technology - Works to automatically recognize any device’s supported resolutionsand signal type parameters, allowing switching out source and destination devices without manual setup. Also included is the ability to control detailed timing parameters for customizedvideo output formats. (SmartScale is the ability to configure the scaling output by automaticallyDATA SHEET。

DATA SHEET HydraPort® 9 Module Connection PortsHPX-900SL, Brushed Aluminum (FG560-02-SL)HPX-900BL, Black Anodized (FG560-02-BL)OverviewThe HPX-900 / HydraPort® 9 Module Connection Port is a modular AV table box for connecting mobile devices to projectors or displays in a conference room or classroom. This sleek, flush-mount table box is typically installed in a conference room or classroom table, featuring a uniquely-designed lid that conveniently opens in both directions to provide a clean, unobtrusive look.No matter how you bring in your content - via HDMI, VGA, USB and other popular formats - you have access to the cable or connection you need, whenever you need it. The HydraPort Architectural Connectivity System uses simple, interchangeable modules to put together the exact future-proof configuration you need today and tomorrow.Common Applications∙With 9 available modules, the HPX-900 is perfect for mid-sized rooms that need the capability to connect several different device types to the AV system, or to provide AC power to several different devices∙The HPX-900 is designed for any conference room, classroom or boardroom that requires the capability to connect several device types, with an unobtrusive style∙With the capability to accommodate AMX Metreau Keypads, the HPX-900 is ideal for large rooms that require an additional control interface at the table or lectern, or for small huddle spaces where the Metreau Keypads are the primary control interfaceFeatures∙Future-Proof Modular Design – Features an assembly with the flexibility to change the modules to meet current and future needs∙Elegant and Unobtrusive – Flush-mount design installs cleanly into a lectern or table and the lid conveniently opens in both directions providing a sleek look∙No Electrician Required – HydraPort power modules can be connected directly to a wall or floor outlet eliminating the need for an electrician∙Control The Room – Add Metreau® or Novara® Keypad modules to control AV devices, lighting or shades as well as to initiate pre-programmed events∙Anodized Aluminum – These stylish, low profile connectivity ports have the same contemporary brushed aluminum enclosure as the higher-end office furniture manufacturers at the same price as most competitive painted metal modelsHPX-AV102A-DP-R (FG552-38)HPX-N102-ETH-R (FG552-34)HPX-AV103-RGB+A-R (FG552-35)RGB with Stereo Module with Retractable MyTurn-Ready CableHPX-AV102A-MDP-R (FG552-39)Mini DisplayPort 4K60 Module with Retractable MyTurn-Ready CableHPX-AV102-USB-R (FG552-37)USB 3.0 Module with Retractable MyTurn-Ready Cable HPX-N100-SRJ45 (FG536-03)Single Shielded Cat6 Ethernet ModuleHPX-N102-SRJ45 (FG563-04)Dual Shielded Cat6 Ethernet Module HPX-N100-RJ45 (FG553-01)Single Cat6 Ethernet ModuleHPX-N102-RJ45 (FG553-02)Dual Cat6 Ethernet ModuleHPX-N100-USB (FG553-11)Single USB Module with Integrated CableHPX-N102-USB (FG553-12)Dual USB Module with Printed USB SymbolHPX-N102-USB-PC (FG553-13)Dual USB Power Module with Printed Charging SymbolHPX-U100-2BTN (FG554-02) HydraPort 2-Button Keypad ModuleHPX-U100-BTN (FG554-01)Single Button Module with LEDHPX-U400-R-MET-6NE (FG565-11-BL) Metreau 6-Button Ethernet Keypad Ramp KitHPX-U400-R-MET-13E (FG565-12-BL)HPX-U400-R-MET-6N (FG564-11-BL) Metreau 6-Button Keypad Ramp Mount Kit HPX-U400-R-MET-7 (FG564-13-BL) Metreau 7-Button Keypad Ramp Mount KitHPX-U400-R-MET-13 (FG564-12-BL) Metreau 13-Button Keypad Ramp Mount Kit HPX-U400-SP-08-E (FG555-51-BL)HPX-U400-SP-08-AX (FG554-51-BL)Novara 8-Button Keypad with AxLink (US) ModuleHPX-P200-PC-US (FG561-01) Power Outlet (US) Module with CordHPX-P250-PC-UK (FG561-11) Power Outlet (UK) ModuleHPX-P200-PC-EU (FG561-21) Power Outlet (EU) ModuleHPX-P200-PC-AU (FG561-31) Power Outlet (AU) ModuleHPX-P250-PC-IN (FG561-41)Power Outlet (IN) ModuleHPX-P200-PC-BR (FG561-71) HydraPort Power Outlet (BR) ModuleHPX-P200-PC-EU2 (FG561-61) HydraPort Power Outlet (EU) ModuleHPX-P200-PC-ITY (FG561-81)HPX-AV101-HDMI (FG552-24)Single HDMI Module with Integrated CableHPX-AV101-DVI+A (FG552-22)DVI-D with Stereo Module with Integrated Cables HPX-AV100-CS+A (FG552-10)Composite with Stereo ModuleHPX-AV102-RGB+A (FG552-25)RGB with Stereo Module with Integrated Cables HPX-AV100-RGB+A (FG552-11)RGBHV with Stereo ModuleHPX-CPT200-W (FG562-41)Cable Pass-Thru Well ModuleHPX-CPTS100-W (FG562-42)Spacer, Cable Pass-Thru Well ModuleHPX-CPTS300-W (FG562-42K)Cable Pass-Thru Well Module and Spacer KitHPX-B050 (FG558-01)1/2 M Blank PanelHPX-B100 (FG558-02)1 M Blank PanelHPX-B200 (FG558-03)2 M Blank PanelHPX-B050-L (FG558-11)1/2 M Custom Label PanelFor a more detailed pictorial drawing please visit: /products/HPX-900.aspAbout AMX by HARMANFounded in 1982 and acquired by HARMAN in 2014, AMX® is dedicated to providing AV solutions for an IT World. AMX solves the complexity of managing technology with reliable, consistent and scalable systems comprising control, video switching and distribution, digital signage and technology management. AMX systems are deployed worldwide in conference rooms, classrooms, network operation/command centers, homes, hotels, entertainment venues and broadcast facilities, among others. AMX is part of the HARMAN Professional Group, the only total audio, video, lighting, and control vendor in the professional AV market. HARMAN designs, manufactures and markets premier audio, video, infotainment and integrated control solutions for the automotive, consumer and professional markets. Revised 2.1.17. ©2017 Harman. All rights reserved. Specifications subject to change. | +1.469.624.7400 |800.222.0193。

AMXModX之系列说明（配置和管理之二）配置和管理之二4.管理员以下说明适用于存储在addons\amxmodx\configs\users.ini文件中的管理员信息。

如果你使用SQL，请参照SQL章节。

用你常用的文本编辑器打开该文件。

在添加用户时需要用到4个参数：验证方式，密码，权限，连接标志一般情况下，users.ini中的表项如下："STEAMID" "" "abcdefghijklmnopqrstu" "ce"以下是一个具体的例子"STEAM_0:0:123456" "" "abcdefghijklmnopqrstu" "ce"这表示：验证方式：STEAM_0:0:123456密码：无 (已通过SteamID验证)权限：a～u所有权限连接标志： SteamID + 无密码一般来说使用如上范例就已足够。

极少情况下你需要通过密码＋用户名来进行验证。

这样的话你需要参考如下范例："Bread" "mypass" "abcdefghijklmnopqrstu" "a"之后，为了标明自己的身份，你需要编辑mod文件夹下的“autoexec.cfg”文件(没有的话就创建一个)，在其中添加如下内容：setinfo "_pw" "mypass"其中“_pw”由amxx.cfg中的amx_password_field指令定义以下是可用的权限以及连接标志。

注意：不要为管理员添加“z”权限权限标志用途a 赦免权（不会被踢除/封禁/处死/打耳光也不会受其他命令所影响）b 预留权限（可以使用贵宾预留通道）c 可使用amx_kick指令d 可使用amx_ban 和 amx_unban 指令e 可使用amx_slay 和 amx_slap 指令f 可使用amx_map指令g 可使用amx_cvar指令 (不是所有的CVAR参数都可以使用)h 可使用amx_cfg指令i 可使用amx_chat 和其他聊天指令j 可使用amx_vote 和其他投票指令k 可修改sv_password 参数 (使用amx_cvar指令)l 可使用amx_rcon command指令并可修改rcon_password参数(使用amx_cvar指令)m 自定义权限A （为非官方插件准备）n 自定义权限Bo 自定义权限Cp 自定义权限Dq 自定义权限Er 自定义权限Fs 自定义权限Gt 自定义权限Hu 可使用菜单z 普通用户权限 (无任何管理员权限)连接标志用途a 密码不符则断开用户连接b 通过战队标志验证c 通过steamid/wonid验证d 通过IP地址验证e 不检测密码（只检测名字/IP/steamid）5.SQLAMX Mod X 拥有一整套可被所有SQL连接器使用的通用变量。