From eb9598038af380e7002b73ebe9ff89fb21206227 Mon Sep 17 00:00:00 2001
From: eeff <33566201+eeff@users.noreply.github.com>
Date: Wed, 17 Jul 2024 17:17:57 +0800
Subject: [PATCH 1/2] add HollySys RTU doc
---
directory.json | 8 ++
.../modbus-hollysys-rtu.md | 106 ++++++++++++++++++
.../modbus-hollysys-rtu.md | 95 ++++++++++++++++
3 files changed, 209 insertions(+)
create mode 100644 en_US/configuration/south-devices/modbus-hollysys-rtu/modbus-hollysys-rtu.md
create mode 100644 zh_CN/configuration/south-devices/modbus-hollysys-rtu/modbus-hollysys-rtu.md
diff --git a/directory.json b/directory.json
index 8a7fccc8..e7b9aab5 100644
--- a/directory.json
+++ b/directory.json
@@ -99,6 +99,10 @@
}
]
},
+ {
+ "title": "HollySys Modbus RTU",
+ "path": "configuration/south-devices/modbus-hollysys-rtu/modbus-hollysys-rtu"
+ },
{
"title": "XINJE Modbus RTU",
"path": "configuration/south-devices/modbus-xinje-rtu/modbus-xinje-rtu"
@@ -769,6 +773,10 @@
}
]
},
+ {
+ "title": "HollySys Modbus RTU",
+ "path": "configuration/south-devices/modbus-hollysys-rtu/modbus-hollysys-rtu"
+ },
{
"title": "XINJE Modbus RTU",
"path": "configuration/south-devices/modbus-xinje-rtu/modbus-xinje-rtu"
diff --git a/en_US/configuration/south-devices/modbus-hollysys-rtu/modbus-hollysys-rtu.md b/en_US/configuration/south-devices/modbus-hollysys-rtu/modbus-hollysys-rtu.md
new file mode 100644
index 00000000..dd38944b
--- /dev/null
+++ b/en_US/configuration/south-devices/modbus-hollysys-rtu/modbus-hollysys-rtu.md
@@ -0,0 +1,106 @@
+# HollySys Modbus RTU
+
+The Neuron HollySys Modbus RTU plugin is for collecting HollySys PLC tags using the Modbus RTU protocol,
+
+
+## Add Device
+
+Go to **Configuration -> South Devices**, then click **Add Device** to add the driver. Configure the following settings in the popup dialog box.
+
+- Name: The name of this device node.
+- Plugin: Select the **HollySys Modbus RTU** plugin.
+
+## Device Configuration
+
+
+After clicking **Create**, you will be redirected to the **Device Configuration** page, where we will set up the parameters required for Neuron to establish a connection with the device. You can also click the device configuration icon on the southbound device card to enter the **Device Configuration** interface.
+
+| Parameter | Description |
+| -------------------------- | -------------------------------------------------------------------------------------- |
+| **Physical Link** | Selects the communication medium, either serial or Ethernet. |
+| **Connection Timeout** | The time the system waits for a device to respond to a command. |
+| **Maximum Retry Times** | The maximum number of retries after a failed attempt to send a read command. |
+| **Retry Interval** | Resend reading instruction interval(ms) after a failed attempt to send a read command. |
+| **Send Interval** | The waiting time between sending each read/write command. Some serial devices may discard certain commands if they receive consecutive commands in a short period of time. |
+| **Serial Device** | Only needed in **Serial** mode, the path to the serial device when using a serial connection, e.g., /dev/ttyS0 in Linux systems. |
+| **Stop Bits** | Only for the **Serial** mode, the serial connection parameter. |
+| **Parity** | Only for the **Serial** mode, the serial connection parameter. |
+| **Baud Rate** | Only for the **Serial** mode, the serial connection parameter. |
+| **Data Bits** | Only for the **Serial** mode, the serial connection parameter. |
+| **Connection Mode** | Only for the **Ethernet** mode, you can choose Neuron as the TCP client or server. |
+| **IP Address** | Only for the **Ethernet** mode, the IP address of the device when using TCP connection with Neuron as the client, or the IP address of Neuron when using TCP connection with Neuron as the server. The default value is 0.0.0.0. |
+| **Port** | Only for the **Ethernet** mode, the port number of the device when using TCP connection with Neuron as the client, or the port number of Neuron when using TCP connection with Neuron as the server. |
+| **Maximum Retry Times** | The maximum number of retries after a failed attempt to send a read command. |
+| **Retry Interval** | Resend reading instruction interval(ms) after a failed attempt to send a read command. |
+
+The HollySys Modbus RTU plugin configuration is similar to that of the [Modbus RTU driver module](../modbus-rtu/modbus-rtu.md).
+
+## Configure Data Groups and Tags
+
+After the plugin is added and configured, the next step is to establish communication between your device and Neuron by adding groups and tags to the Southbound driver.
+
+Once device configuration is completed, navigate to the **South Devices** page. Click on the device card or device row to access the **Group List** page. Here, you can create a new group by clicking on **Create**, then specifying the group name and data collection interval.
+
+Upon successfully creating a group, click on its name to proceed to the **Tag List** page. This page allows you to add device tags for data collection. You'll need to provide information such as the tag address, attributes, and data type.
+
+For information on general configuration items, see [Connect to Southbound Devices](../south-devices.md). The subsequent section will concentrate on configurations specific to the driver.
+
+### Data types
+
+* BIT
+* BOOL
+* INT16
+* UINT16
+* WORD
+
+### Address format
+
+> SLAVE!ADDRESS[#ENDIAN]
+
+The address format is nearly the same to that of the [Modbus RTU driver module](../modbus-rtu/modbus-rtu.md), the only difference is in the **ADDRESS** part.
+
+#### **SLAVE**
+
+Required, Slave is the slave address or site number.
+
+#### **ADDRESS**
+
+HollySys PLC maps data units onto the Modbus address space for access through the Modbus RTU protocol.
+The Neuron HollySys Modbus RTU plugin frees users from details of the address mapping, and designates the PLC data unit name as the **ADDRESS**.
+
+
+| Area | Data unit example | Attribute | Register Size | Data Type |
+| ------------------------------- | ------------------------------------------- | ---------- | ------------- | -------------- |
+| IX (Input) | IX0.0 ... IX0.7, IX1.0 ... IX1.7 ... | Read | 1Bit | BOOL/BIT |
+| IW (Input Registers) | IW0, IW1, ... | Read | 16Bit,2Byte | INT16/UINT16 |
+| QX (Coils) | QX0.0 ... QX0.7, QX1.0 ... QX1.7 ... | Read/Write | 1Bit | BOOL/BIT |
+| QW (Hold Registers) | QW0, QW1, ... | Read/Write | 16Bit,2Byte | INT16/UINT16 |
+| MX (Coils) | MX0.0 ... MX0.7, MX1.0 ... MX1.7 ... | Read/Write | 1Bit | BOOL/BIT |
+| MW (Hold Registers) | MW0, MW1, ... | Read/Write | 16Bit,2Byte | INT16/UINT16 |
+
+
+#### **#ENDIAN**
+
+Optional, byte order, applicable to data types int16/uint16, see the table below for details.
+| Symbol | Byte Order | Supported Data Types | Note |
+| ------ | ---------- | -------------------- | ----------------------------------- |
+| #B | 2,1 | int16/uint16 | |
+| #L | 1,2 | int16/uint16 | Default byte order if not specified |
+
+::: tip
+The byte order can be illustrated using the notation ABCD, which corresponds directly to the sequence 1234. As an example, the ABCD designation represents the standard or default Endianness 1234. (#LL).
+:::
+
+
+### Example Addresses
+
+| Address | Data Type | Description |
+| -------------- | --------- | -------------------------------------------------- |
+| 1!IX1.0 | bit | Data unit IX1.0 on slave 1, read only. |
+| 1!QW0 | int16 | Data unit QW0 on slave 1, support read/write. |
+| 2!MW1 | int16 | Data unit MW1 on slave 1, support read/write. |
+
+
+## Data Monitoring
+
+After completing the point configuration, you can click **Monitoring** -> **Data Monitoring** to view device information and control devices. For details, refer to [Data Monitoring](../../../admin/monitoring.md).
diff --git a/zh_CN/configuration/south-devices/modbus-hollysys-rtu/modbus-hollysys-rtu.md b/zh_CN/configuration/south-devices/modbus-hollysys-rtu/modbus-hollysys-rtu.md
new file mode 100644
index 00000000..afbc22ce
--- /dev/null
+++ b/zh_CN/configuration/south-devices/modbus-hollysys-rtu/modbus-hollysys-rtu.md
@@ -0,0 +1,95 @@
+# HollySys Modbus RTU
+
+Neuron HollySys Modbus RTU 插件使用 Modbus RTU 协议，用于采集和利时 PLC 标签的数据，支持 LK/LE 系列 PLC 型号。
+
+## 添加插件
+
+在 **配置 -> 南向设备**，点击**添加设备**来创建设备节点，输入插件名称，插件类型选择 **HollySys Modbus RTU** 启用插件。
+
+## 设备配置
+
+点击插件卡片或插件列，进入**设备配置**页。配置 Neuron 与设备建立连接所需的参数，下表为插件相关配置项。
+
+| 参数
| 说明 |
+| -------------------- | ---------------------------------------------------------------------------------------------- |
+| **物理链路** | 选择使用 Serial （串口）或者是 Ethernet（以太网）通信介质。 |
+| **连接超时时间** | 等待设备返回指令响应的时间。 |
+| **最大重试次数** | 发送读取指令失败后最大重试次数。 |
+| **指令重新发送间隔** | 发送读取指令失败后重新发送读指令时间间隔，单位为毫秒。 |
+| **指令发送间隔** | 发送每条读写指令之间的等待时间。某些串口设备在较短时间内接收到连续指令时，可能会丢弃某些指令。 |
+| **串口设备** | 串口模式下，串口设备的路径，如 Linux 系统中 /dev/ttyS0。 |
+| **停止位** | 串口模式下，串口连接参数。 |
+| **校验位** | 串口模式下，串口连接参数。 |
+| **波特率** | 串口模式下，串口连接参数。 |
+| **数据位** | 串口模式下，串口连接参数。 |
+| **连接模式** | Ethernet 模式下，可以选择 Neuron 作为 TCP 的客户端或是服务端。 |
+| **IP 地址** | Ethernet 模式下，设备的 IP 地址（Neuron 作为客户端）；或是 Neuron 本机的 IP 地址（Neuron 作为服务端），默认可填 0.0.0.0。 |
+| **端口** | Ethernet 模式下，设备的端口号（Neuron 作为客户端）；或是 Neuron 本机的端口（Neuron 作为服务端）。|
+| **最大重试次数** | 发送读取指令失败后最大重试次数。 |
+| **指令重新发送间隔** | 发送读取指令失败后重新发送读指令时间间隔，单位为毫秒。 |
+
+HollySys Modbus RTU 插件的配置与 [Modbus RTU驱动模块](../modbus-rtu/modbus-rtu.md)相似。
+
+## 设置组和点位
+
+完成插件的添加和配置后，要建立设备与 Neuron 之间的通信，首先为南向驱动程序添加组和点位。
+
+完成设备配置后，在**南向设备**页，点击设备卡片/设备列进入**组列表**页。点击**创建**来创建组，设定组名称以及采集间隔。完成组的创建后，点击组名称进入**点位列表**页，添加需要采集的设备点位，包括点位地址，点位属性，数据类型等。
+
+公共配置项部分可参考[连接南向设备](../south-devices.md)，本页将介绍支持的数据类型和地址格式部分。
+
+### 数据类型
+
+* BIT
+* BOOL
+* INT16
+* UINT16
+
+### 地址格式
+
+> SLAVE!ADDRESS[#ENDIAN]
+
+#### **SLAVE**
+
+必填，指从机地址或者是站点号。
+
+#### **ADDRESS**
+
+和利时 PLC 将数据单元映射到 Modbus 地址空间，以通过 Modbus RTU 协议进行访问。
+Neuron HollySys Modbus RTU 插件将 PLC 数据单元名称指定为 **ADDRESS**，用户不需要关心地址映射的细节。
+
+| 数据区 | Modbus 地址范围 | 属性 | 寄存器大小 | 数据类型 |
+| ------------------------------- | ------------------------------------------- | ---------- | ------------- | --------- |
+| IX (Input) | IX0.0 ... IX0.7, IX1.0 ... IX1.7 ... | Read | 1Bit | BOOL/BIT |
+| IW (Input Registers) | IW0, IW1, ... | Read | 16Bit,2Byte | INT16/UINT16 |
+| QX (Coils) | QX0.0 ... QX0.7, QX1.0 ... QX1.7 ... | Read/Write | 1Bit | BOOL/BIT |
+| QW (Hold Registers) | QW0, QW1, ... | Read/Write | 16Bit,2Byte | INT16/UINT16 |
+| MX (Coils) | MX0.0 ... MX0.7, MX1.0 ... MX1.7 ... | Read/Write | 1Bit | BOOL/BIT |
+| MW (Hold Registers) | MW0, MW1, ... | Read/Write | 16Bit,2Byte | INT16/UINT16 |
+
+#### **#ENDIAN**
+
+选填，字节顺序，适用于 int16/uint16 数据类型，详细说明见下表。
+
+| 符号 | 字节顺序 | 支持的数据类型 | 备注 |
+| ---- | -------- | ------------------ | ------------------ |
+| #B | 2,1 | int16/uint16 | |
+| #L | 1,2 | int16/uint16 | 不填，默认字节顺序 |
+
+::: tip
+字节顺序可能用 ABCD 表示，只需将 1234 对应 ABCD 即可。例如 ABCD 对应默认字节序 1234 (#LL)。
+:::
+
+
+### 地址示例
+
+| 地址 | 数据类型 | 说明 |
+| -------------- | --------- | -------------------------------------------------- |
+| 1!IX1.0 | bit | 指站号为 1，PLC 数据单元 IX1.0, 只读。 |
+| 1!QW0 | int16 | 指站号为 1，PLC 数据单元 QW0, 支持读写。 |
+| 2!MW1 | int16 | 指站号为 2，PLC 数据单元 MW1, 支持读写。 |
+
+
+## 数据监控
+
+完成点位的配置后，您可点击 **监控** -> **数据监控**查看设备信息以及反控设备，具体可参考[数据监控](../../../admin/monitoring.md)。
From c2147a12c35fb690b872f44831d8d1367b659391 Mon Sep 17 00:00:00 2001
From: eeff <33566201+eeff@users.noreply.github.com>
Date: Mon, 22 Jul 2024 11:35:58 +0800
Subject: [PATCH 2/2] add HollySys TCP doc
---
directory.json | 8 ++
.../modbus-hollysys-tcp.md | 98 +++++++++++++++++++
.../modbus-hollysys-tcp.md | 94 ++++++++++++++++++
3 files changed, 200 insertions(+)
create mode 100644 en_US/configuration/south-devices/modbus-hollysys-tcp/modbus-hollysys-tcp.md
create mode 100644 zh_CN/configuration/south-devices/modbus-hollysys-tcp/modbus-hollysys-tcp.md
diff --git a/directory.json b/directory.json
index e7b9aab5..9f854b75 100644
--- a/directory.json
+++ b/directory.json
@@ -121,6 +121,10 @@
}
]
},
+ {
+ "title": "HollySys Modbus TCP",
+ "path": "configuration/south-devices/modbus-hollysys-tcp/modbus-hollysys-tcp"
+ },
{
"title": "Inovance Modbus TCP",
"path": "configuration/south-devices/modbus-hc-tcp/modbus-hc-tcp",
@@ -795,6 +799,10 @@
}
]
},
+ {
+ "title": "HollySys Modbus TCP",
+ "path": "configuration/south-devices/modbus-hollysys-tcp/modbus-hollysys-tcp"
+ },
{
"title": "Inovance Modbus TCP",
"path": "configuration/south-devices/modbus-hc-tcp/modbus-hc-tcp",
diff --git a/en_US/configuration/south-devices/modbus-hollysys-tcp/modbus-hollysys-tcp.md b/en_US/configuration/south-devices/modbus-hollysys-tcp/modbus-hollysys-tcp.md
new file mode 100644
index 00000000..2212f510
--- /dev/null
+++ b/en_US/configuration/south-devices/modbus-hollysys-tcp/modbus-hollysys-tcp.md
@@ -0,0 +1,98 @@
+# HollySys Modbus TCP
+
+The Neuron HollySys Modbus TCP plugin is for collecting HollySys PLC tags using the Modbus TCP protocol,
+
+Modbus TCP is a version of the Modbus protocol based on Ethernet, which uses TCP/IP for communication. Unlike the traditional Modbus RTU protocol, Modbus TCP allows devices to be interconnected directly through Ethernet without any special hardware or communication interface. Therefore, Modbus TCP has higher communication speed and wider application range.
+
+
+## Add Device
+
+Go to **Configuration -> South Devices**, then click **Add Device** to add the driver. Configure the following settings in the popup dialog box.
+
+- Name: The name of this device node.
+- Plugin: Select the **HollySys Modbus TCP** plugin.
+
+
+## Device Configuration
+
+After clicking **Create**, you will be redirected to the **Device Configuration** page, where we will set up the parameters required for Neuron to establish a connection with the device. You can also click the device configuration icon on the southbound device card to enter the **Device Configuration** interface.
+
+| Parameter | Description |
+| -------------------- | ------------------------------------------------------- |
+| **Maximum Retry Times** | The maximum number of retries after a failed attempt to send a read command. |
+| **Retry Interval** | Resend reading instruction interval(ms) after a failed attempt to send a read command. |
+| **Endianness** | Byte order of tags with 32 bits, ABCD corresponds to 1234. |
+| **Send Interval** | The waiting time between sending each read/write command. Some serial devices may discard certain commands if they receive consecutive commands in a short period of time. |
+| **IP Address** | The IP address of the device when using TCP connection with Neuron as the client. |
+| **Port** | The port number of the device when using TCP connection with Neuron as the client. |
+| **Connection Timeout** | The time the system waits for a device to respond to a command. |
+
+## Configure Data Groups and Tags
+
+After the plugin is added and configured, the next step is to establish communication between your device and Neuron by adding groups and tags to the Southbound driver.
+
+Once device configuration is completed, navigate to the **South Devices** page. Click on the device card or device row to access the **Group List** page. Here, you can create a new group by clicking on **Create**, then specifying the group name and data collection interval.
+
+Upon successfully creating a group, click on its name to proceed to the **Tag List** page. This page allows you to add device tags for data collection. You'll need to provide information such as the tag address, attributes, and data type.
+
+For information on general configuration items, see [Connect to Southbound Devices](../south-devices.md). The subsequent section will concentrate on configurations specific to the driver.
+
+### Data types
+
+* BIT
+* BOOL
+* INT16
+* UINT16
+* WORD
+
+### Address format
+
+> SLAVE!ADDRESS[#ENDIAN]
+
+#### **SLAVE**
+
+Required, Slave is the slave address or site number.
+
+#### **ADDRESS**
+
+HollySys PLC maps data units onto the Modbus address space for access through the Modbus TCP protocol.
+The Neuron HollySys Modbus TCP plugin frees users from details of the address mapping, and designates the PLC data unit name as the **ADDRESS**.
+
+
+| Area | Data unit example | Attribute | Register Size | Data Type |
+| ------------------------------- | ------------------------------------------- | ---------- | ------------- | -------------- |
+| IX (Input) | IX0.0 ... IX0.7, IX1.0 ... IX1.7 ... | Read | 1Bit | BOOL/BIT |
+| IW (Input Registers) | IW0, IW1, ... | Read | 16Bit,2Byte | INT16/UINT16 |
+| QX (Coils) | QX0.0 ... QX0.7, QX1.0 ... QX1.7 ... | Read/Write | 1Bit | BOOL/BIT |
+| QW (Hold Registers) | QW0, QW1, ... | Read/Write | 16Bit,2Byte | INT16/UINT16 |
+| MX (Coils) | MX0.0 ... MX0.7, MX1.0 ... MX1.7 ... | Read/Write | 1Bit | BOOL/BIT |
+| MW (Hold Registers) | MW0, MW1, ... | Read/Write | 16Bit,2Byte | INT16/UINT16 |
+
+
+#### **#ENDIAN**
+
+Optional, byte order, applicable to data types int16/uint16, see the table below for details.
+
+| Symbol | Byte Order | Supported Data Types | Note |
+| ------ | ---------- | -------------------- | ----------------------------------- |
+| #B | 2,1 | int16/uint16 | |
+| #L | 1,2 | int16/uint16 | Default byte order if not specified |
+
+::: tip
+The byte order of a tag has a higher priority than the byte order configuration of a node. That is to say, once the byte order is configured for a tag, it follows the configuration of that tag and ignores the node configuration.
+The byte order can be illustrated using the notation ABCD, which corresponds directly to the sequence 1234. As an example, the ABCD designation represents the standard or default Endianness 1234. (#LL).
+:::
+
+
+### Example Addresses
+
+| Address | Data Type | Description |
+| -------------- | --------- | -------------------------------------------------- |
+| 1!IX1.0 | bit | Data unit IX1.0 on slave 1, read only. |
+| 1!QW0 | int16 | Data unit QW0 on slave 1, support read/write. |
+| 2!MW1 | int16 | Data unit MW1 on slave 1, support read/write. |
+
+
+## Data Monitoring
+
+After completing the point configuration, you can click **Monitoring** -> **Data Monitoring** to view device information and control devices. For details, refer to [Data Monitoring](../../../admin/monitoring.md).
diff --git a/zh_CN/configuration/south-devices/modbus-hollysys-tcp/modbus-hollysys-tcp.md b/zh_CN/configuration/south-devices/modbus-hollysys-tcp/modbus-hollysys-tcp.md
new file mode 100644
index 00000000..92839478
--- /dev/null
+++ b/zh_CN/configuration/south-devices/modbus-hollysys-tcp/modbus-hollysys-tcp.md
@@ -0,0 +1,94 @@
+# Modbus TCP
+
+Neuron HollySys Modbus TCP 插件使用 Modbus TCP 协议，用于采集和利时 PLC 标签的数据，支持 LK/LE 系列 PLC 型号。
+
+Modbus TCP 是一种基于以太网的 Modbus 协议版本，它使用 TCP/IP 协议进行通信。与传统的 Modbus RTU 协议不同，Modbus TCP 允许设备直接通过以太网互联，不需要任何专用的硬件或通信接口。因此，Modbus TCP 具有更高的通信速率和更广泛的应用范围。
+
+
+## 添加插件
+
+在 **配置 -> 南向设备**，点击**添加设备**来创建设备节点，输入插件名称，插件类型选择 **HollySys Modbus TCP** 启用插件。
+
+
+## 设备配置
+
+点击插件卡片或插件列，进入**设备配置**页。配置 Neuron 与设备建立连接所需的参数，下表为插件相关的配置项。
+
+| 字段
| 说明 |
+| -------------------- | ------------------------------------------------------- |
+| **最大重试次数** | 发送读取指令失败后最大重试次数。 |
+| **指令重新发送间隔** | 发送读取指令失败后重新发送读指令时间间隔，单位为毫秒。 |
+| **字节序** | 32 位数据类型字节序，ABCD 对应 1234。 |
+| **指令发送间隔** | 发送每条读写指令之间的等待时间。某些串口设备在较短时间内接收到连续指令时，可能会丢弃某些指令。 |
+| **IP 地址** | TCP 连接时，设备的 IP 地址（Neuron 作为客户端）。|
+| **端口号** | TCP 连接时，设备的端口号（Neuron 作为客户端）。|
+| **连接超时时间** | 等待设备返回指令响应的时间。 |
+
+
+## 设置组和点位
+
+完成插件的添加和配置后，要建立设备与 Neuron 之间的通信，首先为南向驱动程序添加组和点位。
+
+完成设备配置后，在**南向设备**页，点击设备卡片/设备列进入**组列表**页。点击**创建**来创建组，设定组名称以及采集间隔。完成组的创建后，点击组名称进入**点位列表**页，添加需要采集的设备点位，包括点位地址，点位属性，数据类型等。
+
+公共配置项部分可参考[连接南向设备](../south-devices.md)，本页将介绍支持的数据类型和地址格式部分。
+
+
+### 数据类型
+
+* BIT
+* BOOL
+* INT16
+* UINT16
+
+
+### 地址格式
+
+> SLAVE!ADDRESS[#ENDIAN]
+
+#### **SLAVE**
+
+必填，指从机地址或者是站点号。
+
+#### **ADDRESS**
+
+和利时 PLC 将数据单元映射到 Modbus 地址空间，以通过 Modbus TCP 协议进行访问。
+Neuron HollySys Modbus TCP 插件将 PLC 数据单元名称指定为 **ADDRESS**，用户不需要关心地址映射的细节。
+
+| 数据区 | Modbus 地址范围 | 属性 | 寄存器大小 | 数据类型 |
+| ------------------------------- | ------------------------------------------- | ---------- | ------------- | --------- |
+| IX (Input) | IX0.0 ... IX0.7, IX1.0 ... IX1.7 ... | Read | 1Bit | BOOL/BIT |
+| IW (Input Registers) | IW0, IW1, ... | Read | 16Bit,2Byte | INT16/UINT16 |
+| QX (Coils) | QX0.0 ... QX0.7, QX1.0 ... QX1.7 ... | Read/Write | 1Bit | BOOL/BIT |
+| QW (Hold Registers) | QW0, QW1, ... | Read/Write | 16Bit,2Byte | INT16/UINT16 |
+| MX (Coils) | MX0.0 ... MX0.7, MX1.0 ... MX1.7 ... | Read/Write | 1Bit | BOOL/BIT |
+| MW (Hold Registers) | MW0, MW1, ... | Read/Write | 16Bit,2Byte | INT16/UINT16 |
+
+
+#### **#ENDIAN**
+
+选填，字节顺序，适用于 int16/uint16 数据类型，详细说明见下表。
+
+| 符号 | 字节顺序 | 支持的数据类型 | 备注 |
+| --- | ------- | ------------------ | ----- |
+| #B | 2,1 | int16/uint16 | |
+| #L | 1,2 | int16/uint16 | 不填，默认字节顺序 |
+
+::: tip
+点位字节序优先级高于节点字节序配置。即点位配置字节序后，字节序按照点位的配置，忽略节点配置。
+字节顺序可能用 ABCD 表示，只需将 1234 对应 ABCD 即可。例如 ABCD 对应默认字节序 1234 (#LL)。
+:::
+
+
+### 地址示例
+
+| 地址 | 数据类型 | 说明 |
+| -------------- | --------- | -------------------------------------------------- |
+| 1!IX1.0 | bit | 指站号为 1，PLC 数据单元 IX1.0, 只读。 |
+| 1!QW0 | int16 | 指站号为 1，PLC 数据单元 QW0, 支持读写。 |
+| 2!MW1 | int16 | 指站号为 2，PLC 数据单元 MW1, 支持读写。 |
+
+
+## 数据监控
+
+完成点位的配置后，您可点击 **监控** -> **数据监控**查看设备信息以及反控设备，具体可参考[数据监控](../../../admin/monitoring.md)。