Merge pull request #570 from hxy7yx/main-2.12

modbus:support 8-byte Endianness

Author: QQDQ

en_US/configuration/south-devices/modbus-hc-tcp/modbus-hc-tcp.md

@@ -18,7 +18,8 @@ After clicking **Create**, you will be redirected to the **Device Configuration*
 
 | Parameter                  | Description                                                    |
 | -------------------- | ------------------------------------------------------- |
-| **Endianness** | Byte order of tags with 32 bits, ABCD corresponds to 1234. |
+| **4-byte Endianness**    | Byte order of tags with 32 bits, ABCD corresponds to 1234. |
+| **8-byte Endianness**    | Byte order of tags with 64 bits, with each number representing one byte. |
 | **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. |
 | **PLC IP Address** | The IP address of the device. |
 | **PLC Port** | The port number of the device.|
@@ -120,6 +121,14 @@ Optional, byte order, applicable to data types int16/uint16/int32/uint32/float,
 | #BL | 1,2,3,4 | int32/uint32/float | |
 | #BB | 2,1,4,3 | int32/uint32/float | |
 
+Byte order also applies to int64/uint64/double data types. Each digit represents one byte. See the following table for detailed information.
+| Symbol | Byte Order | Supported Data Types | Note |
+| --- | ------- | ------------------ | ----- |
+| #LL | 12,34,56,78 | int64/uint64/double | Default byte order if not specified |
+| #LB | 21,43,65,87 | int64/uint64/double | |
+| #BL | 78,56,34,12 | int64/uint64/double | |
+| #BB | 87,65,43,21 | int64/uint64/double | |
+
 ::: 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.
 :::

en_US/configuration/south-devices/modbus-rtu/modbus-rtu.md

@@ -22,7 +22,8 @@ After clicking **Create**, you will be redirected to the **Device Configuration*
 | **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. |
-| **Endianness**    | Byte order of tags with 32 bits, ABCD corresponds to 1234. |
+| **4-byte Endianness**    | Byte order of tags with 32 bits, ABCD corresponds to 1234. |
+| **8-byte Endianness**    | Byte order of tags with 64 bits, with each number representing one byte. |
 | **Start Address** | Address starts from 1 or 0. |
 | **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. |
@@ -109,6 +110,14 @@ Optional, byte order, applicable to data types int16/uint16/int32/uint32/float,
 | #BL | 3,4,1,2 | int32/uint32/float | |
 | #BB | 4,3,2,1 | int32/uint32/float | |
 
+Byte order also applies to int64/uint64/double data types. Each digit represents one byte. See the following table for detailed information.
+| Symbol | Byte Order | Supported Data Types | Note |
+| --- | ------- | ------------------ | ----- |
+| #LL | 12,34,56,78 | int64/uint64/double | Default byte order if not specified |
+| #LB | 21,43,65,87 | int64/uint64/double | |
+| #BL | 78,56,34,12 | int64/uint64/double | |
+| #BB | 87,65,43,21 | int64/uint64/double | |
+
 ::: 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).

en_US/configuration/south-devices/modbus-tcp/modbus-tcp.md

@@ -25,7 +25,8 @@ After clicking **Create**, you will be redirected to the **Device Configuration*
 | **Connection Mode** | Only for **TCP** mode, When selecting TCP, you can choose Neuron as the TCP client or 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. |
-| **Endianness**    | Byte order of tags with 32 bits, ABCD corresponds to 1234. |
+| **4-byte Endianness**    | Byte order of tags with 32 bits, ABCD corresponds to 1234. |
+| **8-byte Endianness**    | Byte order of tags with 64 bits, with each number representing one byte. |
 | **Start Address** | Address starts from 1 or 0. |
 | **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, or the IP address of Neuron when using TCP connection with Neuron as the server. The default value is 0.0.0.0. <!--to be confirmed--> |
@@ -111,6 +112,14 @@ Optional, byte order, applicable to data types int16/uint16/int32/uint32/float,
 | #BL | 3,4,1,2 | int32/uint32/float | |
 | #BB | 4,3,2,1 | int32/uint32/float | |
 
+Byte order also applies to int64/uint64/double data types. Each digit represents one byte. See the following table for detailed information.
+| Symbol | Byte Order | Supported Data Types | Note |
+| --- | ------- | ------------------ | ----- |
+| #LL | 12,34,56,78 | int64/uint64/double | Default byte order if not specified |
+| #LB | 21,43,65,87 | int64/uint64/double | |
+| #BL | 78,56,34,12 | int64/uint64/double | |
+| #BB | 87,65,43,21 | int64/uint64/double | |
+
 ::: 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).

zh_CN/configuration/south-devices/modbus-hc-tcp/modbus-hc-tcp.md

@@ -18,7 +18,8 @@ Neuron 的 Inovance Modbus TCP 插件适配汇川 PLC 点位。
 
 | <div style="width:100pt">字段</div> | 说明                                                    |
 | -------------------- | ------------------------------------------------------- |
-| **字节序** | 32 位数据类型字节序，ABCD 对应 1234。 |
+| **4 字节字节序**   | 32 位数据类型字节序，ABCD 对应 1234。 |
+| **8 字节字节序**   | 64 位数据类型字节序，每个数字代表一字节。 |
 | **指令发送间隔** | 发送每条读写指令之间的等待时间。 |
 | **PLC IP 地址** | TCP 连接时，设备的 IP 地址。|
 | **PLC 端口号** | TCP 连接时，设备的端口号。|
@@ -115,6 +116,14 @@ M、I、Q 区域有多种寻址方式，支持如下寻址方式：（M|I|Q）X
 | #BL | 1,2,3,4 | int32/uint32/float | |
 | #BB | 2,1,4,3 | int32/uint32/float | |
 
+字节顺序同样适用于 int64/uint64/double 数据类型，每个数字代表一字节，详细说明见下表。
+| 符号 | 字节顺序 | 支持的数据类型        | 备注 |
+| --- | ------- | ------------------ | ----- |
+| #LL | 12,34,56,78 | int64/uint64/double | 不填，默认字节顺序 |
+| #LB | 21,43,65,87 | int64/uint64/double | |
+| #BL | 78,56,34,12 | int64/uint64/double | |
+| #BB | 87,65,43,21 | int64/uint64/double | |
+
 ::: tip
 点位字节序优先级高于节点字节序配置。即点位配置字节序后，字节序按照点位的配置，忽略节点配置。
 :::

zh_CN/configuration/south-devices/modbus-rtu/modbus-rtu.md

@@ -18,7 +18,8 @@ Modbus RTU 协议采用二进制编码，可以在 RS-232、RS-485 或其他串
 | **连接超时时间** | 等待设备返回指令响应的时间。 |
 | **最大重试次数** | 发送读取指令失败后最大重试次数。 |
 | **指令重新发送间隔** | 发送读取指令失败后重新发送读指令时间间隔，单位为毫秒。 |
-| **字节序**   | 32 位数据类型字节序，ABCD 对应 1234。 |
+| **4 字节字节序**   | 32 位数据类型字节序，ABCD 对应 1234。 |
+| **8 字节字节序**   | 64 位数据类型字节序，每个数字代表一字节。 |
 | **开始地址** | 点位起始地址从 1 开始或从 0 开始。 |
 | **指令发送间隔** | 发送每条读写指令之间的等待时间。某些串口设备在较短时间内接收到连续指令时，可能会丢弃某些指令。 |
 | **串口设备** | 串口模式下，串口设备的路径，如 Linux 系统中 /dev/ttyS0。 |
@@ -103,6 +104,14 @@ Modbus RTU 协议采用二进制编码，可以在 RS-232、RS-485 或其他串
 | #BL | 3,4,1,2 | int32/uint32/float | |
 | #BB | 4,3,2,1 | int32/uint32/float | |
 
+字节顺序同样适用于 int64/uint64/double 数据类型，每个数字代表一字节，详细说明见下表。
+| 符号 | 字节顺序 | 支持的数据类型        | 备注 |
+| --- | ------- | ------------------ | ----- |
+| #LL | 12,34,56,78 | int64/uint64/double | 不填，默认字节顺序 |
+| #LB | 21,43,65,87 | int64/uint64/double | |
+| #BL | 78,56,34,12 | int64/uint64/double | |
+| #BB | 87,65,43,21 | int64/uint64/double | |
+
 ::: tip
 点位字节序优先级高于节点字节序配置。即点位配置字节序后，字节序按照点位的配置，忽略节点配置。
 字节顺序可能用 ABCD 表示，只需将 1234 对应 ABCD 即可。例如 ABCD 对应默认字节序 1234 (#LL)。

zh_CN/configuration/south-devices/modbus-tcp/modbus-tcp.md

@@ -22,7 +22,8 @@ Neuron 的 Modbus TCP 插件除了支持以 TCP 客户端的模式主动接入
 | **连接模式** | 选择以太网 TCP 连接时，可以选择 Neuron 作为 TCP 的客户端或是服务端。|
 | **最大重试次数** | 发送读取指令失败后最大重试次数。 |
 | **指令重新发送间隔** | 发送读取指令失败后重新发送读指令时间间隔，单位为毫秒。 |
-| **字节序**   | 32 位数据类型字节序，ABCD 对应 1234。 |
+| **4 字节字节序**   | 32 位数据类型字节序，ABCD 对应 1234。 |
+| **8 字节字节序**   | 64 位数据类型字节序，每个数字代表一字节。 |
 | **开始地址** | 点位起始地址从 1 开始或从 0 开始。 |
 | **指令发送间隔** | 发送每条读写指令之间的等待时间。某些串口设备在较短时间内接收到连续指令时，可能会丢弃某些指令。 |
 | **IP 地址** | TCP 连接时，设备的 IP 地址（Neuron 作为客户端）；或是 Neuron 本机的 IP 地址（Neuron 作为服务端），默认可填 0.0.0.0。|
@@ -104,6 +105,14 @@ Neuron 的 Modbus TCP 插件除了支持以 TCP 客户端的模式主动接入
 | #BL | 3,4,1,2 | int32/uint32/float | |
 | #BB | 4,3,2,1 | int32/uint32/float | |
 
+字节顺序同样适用于 int64/uint64/double 数据类型，每个数字代表一字节，详细说明见下表。
+| 符号 | 字节顺序 | 支持的数据类型        | 备注 |
+| --- | ------- | ------------------ | ----- |
+| #LL | 12,34,56,78 | int64/uint64/double | 不填，默认字节顺序 |
+| #LB | 21,43,65,87 | int64/uint64/double | |
+| #BL | 78,56,34,12 | int64/uint64/double | |
+| #BB | 87,65,43,21 | int64/uint64/double | |
+
 ::: tip
 点位字节序优先级高于节点字节序配置。即点位配置字节序后，字节序按照点位的配置，忽略节点配置。
 字节顺序可能用 ABCD 表示，只需将 1234 对应 ABCD 即可。例如 ABCD 对应默认字节序 1234 (#LL)。