HIEE320639R1自动化卡件
测量值可能不正确。配置已更改配置已更改，因此主机应检查配置，并通过发送命令#38清除位。现场设备通电时第一个事务的冷启动设置。更多可用状态主机应发出命令#48以读取更多状态信息。模拟输出固定输出已设置为固定值进行测试。该位仅适用于模拟输出#1。在多点输出设备中，命令#48可以返回其他输出的类似状态信息。模拟输出饱和模拟输出#1超出范围。主要变量超出极限主要测量值超出传感器工作极限。HART命令读取的模拟信号和数字信号可能不正确。PACSystems*RX3i系统手册第12节GFK-2314T 2019年9月带HART通信的模拟模块565非一次变量超出限值非一次测量超出传感器操作限值。HART命令读取的模拟信号和数字信号可能不正确。命令#48可以提供更多信息。PACSystems*RX3i系统手册第12节GFK-2314T 2019年9月带HART通信的模拟模块566 11.6.7.4多含义命令代码第一个命令响应字节中命令代码8-15和28的解释取决于发出的命令。这些命令的第一个字节中的代码代码8（警告）的含义1、2、3、33、60、62、110更新失败34、55、64设置为最接近的可能值48更新进行中9（错误）35、65下限值过高36、37、43、52应用过程过高45、46、67、68不处于正确的电流模式（固定为4或20mA）10（错误）6不支持多点35、65量程值过低36、37，43，52应用过程过低11（错误）35，65量程上限值过高40，45，46，66，67，68在多点模式53变送器变量代码12（错误）无效35，65范围上限值过高53，66，66，68无效单元代码13（错误），35，65两个量程值均超出限制69无效传递函数代码14（警告）35，36，65量程太小37推动的量程上限值超过极限15（错误）65、66、67、68，69无效的模拟输出编号代码28（错误）65无效的量程单位代码PACSystems*RX3i系统手册第12节GFK-2314T 2019年9月带有HART通信的模拟模块567 11.7用于读取HART数据的功能块Proficy机器版本5.5包括两个用于梯形逻辑应用程序的自定义HART功能块。这些功能块可用于为HART数据输入或HART获取设备信息响应数据分配变量名称，从第3字开始。▪ DYN_HART_STRUCT解释通道HART数据映射的前36个字节。如果模块配置为HART数据扫描控制设置为“动态数据”，则该功能块按需读取将自动扫描的相同数据。▪ ALL_HART_STRUCT解释通道的整个HART数据，包括DYN_HART_STRUCT功能块解释的数据。如果模块配置为HART数据扫描控制设置为“所有数据”，则该功能块按需读取将自动扫描的相同数据。这些功能块读取的数据不是读入指定的CPU参考地址，而是放入功能块定义的参考地址。HART功能块位于工具箱中“HART实用程序”文件夹下。要创建这些功能块之一的实例，请将所需的功能从Toolbox文件夹拖放到LD逻辑中。11.7.1 DYN_HART_STRUCT DYN_HART_STRUCT功能块解释通道HART数据图数据（偏移量0x0000至0x0023）的前36个字节。请参阅本节中的示例。不需要使用此功能块。它只提供了一种为HART数据分配变量名称的机制。当DYN_HART_STRUCT函数执行（接收功率流）时，参考存储器中的每个HART变量都分配给DYN_HART_STRUCT实例变量。实例变量名称与表中列出的名称非常匹配。它们可以用作其他函数的输入，或用于调试目的。可以将整个实例添加到数据监视窗口，以便轻松查看HART数据。实例数据变量仅在功能块接收到潮流时更新。每个需要自动分配的HART通道都需要一个功能块实例。参数类型：IN-类型=WORD，长度=18，通过=参考11.7.1.1使用DYN_HART_STRUCT功能块获得的数据字节偏移字段描述数据类型开始结束0x0000 0x0003 HART主变量，CMD#3，字节5-8 REAL PACSystems*RX3i系统手册第12节GFK-2314T 2019年9月带HART通信的模拟模块568 0x0004 0x0007 HART次变量CMD#3，字节10-13 REAL 0x0008 0
Measurements may not be correct. Configuration changed The configuration has been changed, so the master should check the configuration, and clear the bit by sending Command #38. Cold start Set for the first transaction when a field device is powered up. More status available The master should issue Command #48 to read more status information. Analog output fixed The output has been set to a fixed value for testing. This bit applies only to analog output #1. In a multi-drop output device, command #48 may return similar status information for the other outputs. Analog output saturated Analog output #1 is out of range. Primary variable out of limits The primary measurement is outside the sensor operating limits. The analog signal and the digital signal read by HART commands may be incorrect. PACSystems* RX3i System Manual Section 12 GFK-2314T Sept. 2019 Analog Modules with HART Communications 565 Non-primary variable out of limits A non-primary measurement is outside the sensor operating limits. The analog signal and the digital signal read by HART commands may be incorrect. Command #48 may provide more information. PACSystems* RX3i System Manual Section 12 GFK-2314T Sept. 2019 Analog Modules with HART Communications 566 11.6.7.4 Command Codes with Multiple Meanings The interpretation of Command Codes 8-15 and 28 in the first Command Response byte depends on the command that was issued. Code in First Byte For these Commands Meaning of the Code 8 (warning) 1, 2, 3, 33, 60, 62, 110 Update failure 34, 55, 64 Set to nearest possible value 48 Update in progress 9 (error) 35, 65 Lower range value too high 36, 37, 43, 52 Applied process too high 45, 46, 67, 68 Not in proper current mode (fixed at 4 or 20mA) 10 (error) 6 Multi-drop not supported 35, 65 Lower range value too low 36, 37, 43, 52 Applied process too low 11 (error) 35, 65 Upper range value too high 40, 45, 46, 66, 67, 68 In multi-drop mode 53 Invalid transmitter variable code 12 (error) 35, 65 Upper range value too high 53, 66, 67, 68 Invalid units code 13 (error) 35, 65 Both range values out of limits 69 Invalid transfer function code 14 (warning) 35, 36, 65 Span too small 37 Pushed upper range value over limit 15 (error) 65, 66, 67, 68, 69 Invalid analog output number code 28 (error) 65 Invalid range units code PACSystems* RX3i System Manual Section 12 GFK-2314T Sept. 2019 Analog Modules with HART Communications 567 11.7 Function Blocks to Read HART Data Proficy Machine Edition release 5.5 includes two custom HART function blocks for use in ladder logic application programs. These function blocks can be used to assign variable names to HART data inputs or on HART Get Device Information response data, beginning at word 3. ▪ DYN_HART_STRUCT interprets the first 36 bytes of the HART data map for a channel. This function block reads on demand the same data that would be automatically scanned if the module were configured for HART Data Scan Control set to “Dynamic Data”. ▪ ALL_HART_STRUCT interprets the entire HART data for a channel, including the data interpreted by the DYN_HART_STRUCT function block. This function block reads on demand the same data that would be automatically scanned if the module were configured for HART Data Scan Control set to “All Data”. Instead of being read into an assigned CPU reference address, the data read by these Function Blocks is placed into a reference address that is defined by the Function Block. The HART function blocks are located in the Toolchest under the folder "HART Utilities". To create an instance of one of these function blocks, drag and drop the desired function from the Toolchest folder into LD logic. 11.7.1 DYN_HART_STRUCT The DYN_HART_STRUCT function block interprets the first 36 bytes on the data (offsets 0x0000 to 0x0023) of the HART data map for a channel. Refer to the example in this section. Use of this function block is not required. It only provides a mechanism to assign variable names to the HART data, When the DYN_HART_STRUCT function executes (receives power flow), each of the HART variables in reference memory is assigned to DYN_HART_STRUCT instance variables. The instance variable names closely match the names listed in the table. They can be used as input to other functions, or for debugging purposes. The entire instance can be added to a Data Watch window so that HART data is easily viewed. The instance data variables are only updated when the function block receives power flow. An instance of the function block is needed for each HART channel on which automatic assignment is desired. Parameter types: IN - Type = WORD, Length = 18, Pass-by = Reference 11.7.1.1 Data Obtained with the DYN_HART_STRUCT Function Block Byte Offset Field Description Data Type Begin End 0x0000 0x0003 HART Primary Variable, CMD#3, Bytes 5-8 REAL PACSystems* RX3i System Manual Section 12 GFK-2314T Sept. 2019 Analog Modules with HART Communications 568 0x0004 0x0007 HART Secondary Variable CMD#3, Bytes 10-13 REAL 0x0008 0x000b HART Tertiary Variable CMD#3, Bytes 15-18 REAL 0x000c 0x000f HART Fourth Variable CMD#3, Bytes 20-23 REAL 0x0010 0x0013 Slot 0 value. CMD#33, Bytes 2-5 REAL 0x0014 0x0017 Slot 1 value CMD#33, Bytes 8-11 REAL 0x0018 0x001b Slot 2 value CMD#33, Bytes 14-17 REAL 0x001c 0x001f Slot 3 value CMD#33, Bytes 20-23 REAL 0x0020 HART communication status byte from the last HART command response. Refer to Section 11.6.7. BYTE 0x0021 HART device status byte from the last HART command response. (Dynamic Data) BYTE 0x0022 Spare for alignment. (Dynamic Data) BYTE*2 11.7.2 ALL_HART_STRUCT The ALL_HART_STRUCT function block interprets the entire HART data map for it is created (for example, "ch1,g" creates a global instance named "ch1"). If the instance data is not global, the instance can only be used in the program block where the ALL_HART_STRUCT or DYN_HART_STRUCT function block is executed. Figure 326: Ladder Logic using ALL_HART_STRUCT & DYN_HART_STRUCT PACSystems* RX3i System
