AMX编程软件介绍语法说明及实例

matlab基础语法Matlab是一种高级的计算机编程语言和环境，广泛应用于科学、工程和数据分析领域。

它具有强大的数值计算能力和丰富的函数库，可以用于解决各种数学问题、数据处理和可视化等任务。

本文将介绍Matlab的基础语法，包括变量定义、运算符、控制流程、函数定义等内容。

# 1. 变量定义在Matlab中，可以使用等号（=）来定义变量，并且无需指定变量类型。

例如：```x = 10;y = 'Hello, world!';```上述代码定义了一个整型变量x，并赋值为10；同时也定义了一个字符串变量y，并赋值为'Hello, world!'。

# 2. 运算符Matlab支持常见的数学运算符，如加法（+）、减法（-）、乘法（*）、除法（/）等。

还有一些特殊的运算符需要注意：## 2.1 矩阵运算符Matlab中矩阵是一种重要的数据结构，因此提供了矩阵专用的运算符。

使用*可以进行矩阵乘法操作：```A = [1, 2; 3, 4];B = [5, 6; 7, 8];C = A * B;```上述代码定义了两个2x2的矩阵A和B，并将它们相乘得到结果矩阵C。

## 2.2 逻辑运算符Matlab提供了逻辑运算符用于比较和组合逻辑表达式。

常用的逻辑运算符有等于（==）、大于（>）、小于（<）、与（&&）、或（||）等。

例如：```a = 5;b = 10;c = (a > b) && (b < 20);```上述代码定义了两个变量a和b，并使用逻辑与运算符判断a是否大于b并且b是否小于20，结果赋值给变量c。

# 3. 控制流程控制流程是编程中常用的结构，用于根据不同条件执行不同的代码块。

Matlab提供了if语句、for循环和while循环等用于控制流程的语句。

## 3.1 if语句if语句用于根据条件选择性地执行不同的代码块。

AMX中控主机使用Xpanel Pro 控制操作说明一、Xpanel Pro的功能简介Xpanel Pro是一款第三方的iPhone&iPad端的控制软件，并提供接口，兼容各种品牌的可编程中控系统。

使用户可以将Apple iPad当触摸屏使用。

无论身处何处,只要轻击Apple平板触摸屏，就可以实时控制中控控制系统，如投影，灯光，信号切换、音响等。

二、Xpanel Pro的安装Xpanel Pro可以在App Stroe中免费下载。

只需在App Store中搜索Xpanel Pro 就能下载到iPad&iPhone中。

Xpanel Pro支持按钮、进度条、滑动条（AMX称拉条）、网页、天气预报、实时视频、动画、语音控制等功能。

Xpanel Pro自带演示界面，您也可以通过Xpanel Designer界面编写软件自行编写合适的界面。

关于Xpanel Designer 软件的使用说明，请参考<<Xpanel Designer 使用方法>>一文。

这里不详细介绍Xpanel Designer的使用方法。

三、无缝控制AMX NetLinx主机我们提供了AMX的模块包。

只需导入模块包，就可以实现通过Xpanel Pro软件控制AMX主机。

操作过程如下:1、运行NetLinx Studio AMX中控主机程序编写软件。

点击“File->New”,在弹出的窗口中选择新建一个Source。

并点击OK按钮，输入工程名称及保存路径后软件就会自动生成主机程序的框架。

2、根据实际情况添加设备。

（注意红色部份）3、定义端口变量（我们这里使用了15000这个端口）这个端口必须要和Xpanel Pro中设置的中控主机端口相同。

4、定义拉条、按钮的通道数。

（Xpanel_Pro暂时只支持999个按钮及999个拉条）经过上面4步，我们就实现了Xpanel_Pro模块的无缝接入了。

可编写按钮事件或拉条事件。

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这个关键字规定了一个数据事件的处理。

AM检列简单中文操作手册本操作手册适用于AM麻列模拟矩阵设备实现本地化（300米范围内）控制，用户端通过OSCARI单对服务器进行操作访问。

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或机房内的服务器）。

连接示意图，如下：1） 双击“ CTRL”键，击活 AMX 的OSCAR 菜单;2） 输入用户名和密码（用户帐号由系统管理员分配）3）点击“ok”登陆系统，出现 OSCAR 用户菜单界面。

2.2 OSCAR!单介绍登陆AMX 系统后，出现 OSCAR 菜单界面，基本切换操作--选择相应的服务器，用鼠 标点击"Connect”按钮或按键盘的回车键即可（见下图）。

OSCA 麋单还具有其它一些功能，具体分为五个页面 ："Target” 、"User”、"Console ”、2、 OSCAR On-Screen Configuration and Activity Reporting单介绍2.1登陆系统（初始状态没有设定登陆界面）如下图所示： interface"Admin”和"？"下面分别做一一介绍:2.2.1 Target 选项在此页面为OSCA麋单的主控界面，用户用键盘、鼠标在列表中选择服务器，左边栏显示所连接服务器的AMIQ的UID编码（此编码为出厂时所烧录的唯一编码，用户可根据需要对名称进行更改，将在后面做详细说明）；在右边栏选择相应的模式（4种）点击“Connect”切换连接；（如果列表中服务器很多，可直接在键盘上敲击所想要寻找的已经修改过的服务器的名称，系统会将自动选中所键入服务器名称并快速锁定服务器）。

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 MOD X DocumentationScripting Tutorial (Introduction & Pawn Language Basics)–Translated by Shaman.Kaler介绍Pawn是一种“脚本”语言，用于将各种功能嵌入其他程序。

这种语言共有两种，一种类似C或C++，是“汇编”语言，通常是用于输出可执行二进制文件；另一种是“解释”语言，通过虚拟机动态地运行代码（VB那样的—译者注）。

AMX Pawn是两者的混合体：写AMX 是解释型的，但编译过程是汇编的。

（说明了为什么amxx文件没法打开，因为是汇编语言—译者注）在你开始编程之前你要知道一些重要的结构。

第一是“变量”。

变量可以说是含有数据的一个符号或记号（symbol or marker，中文太相似了—译者注）。

比如，变量a可能会含有值2、16、0等等等等。

变量是一个程序创造的存储空间，在使用前必须声明它们的名字（和类型）。

给予变量数据称为“赋值”。

变量的赋值使用的是一个等号：new a,b,c,d //这里是声明a=5 //把a赋值为5b=16c=0d=500另一个重要的概念是函数。

函数是完成某种功能时引用的符号或记号。

这意味着当你使用它们时，它们会处理你所给的数据（“传递”的数据）。

函数有几种，但是使用方法是一致的。

例如，”show”函数把一个数字显示在屏幕上：show(56) //启动”show”函数, 并传递数据”56”。

show() //启动”show”函数, 没有数据（或不需要数据）。

show(a) //启动”show”函数, 并传递变量a包含的数据。

注意任何前面带有”//”符号的文字都属于“注释”，不是真正的代码。

任何传递给函数的数据都被称为“参数”，一个函数可能有任意多的参数，你必须保证你所传递的每个参数的正确性。