Skip to content

Commit

Permalink
Update south-devices.md
Browse files Browse the repository at this point in the history
  • Loading branch information
QQDQ authored Jul 4, 2024
1 parent c5cb0dc commit b41845a
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions en_US/configuration/south-devices/south-devices.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,17 +89,17 @@ Select the **Create** icon to enter the tag page.

![tags-add](./assets/tags-add.png)

* **Name**: This is a unique identifier that you provide for the point, such as point-1.
* **Attribute**: Dropdown to select the point attribute, for example, read, write, subscribe, static, supporting the configuration of multiple point types.
* **Name**: This is a unique identifier that you provide for the tag, such as tag1.
* **Attribute**: Dropdown to select the tag attribute, for example, read, write, subscribe, supporting the configuration of multiple point types.
* Read: Used to read data
* Write: Used to write data
* Subscribe: Only sends messages when data changes. For example, the default data is 0, when the data changes to 2, a message will be sent
* Static: Requires a value to be assigned at configuration, and the assigned value can also be seen on the monitoring page after configuration
* **Type**: The type of data stored at this tag. This could be integer, float, string, or boolean. Choose the type according to your device data.
* **Address**: Fill in the driver address, for example, 1!40001. 1 represents the point site number set in the Modbus simulator, and 40001 represents the point register address. For detailed instructions on how to use the driver address, please refer to [South Device - Modbus TCP](./modbus-tcp/modbus-tcp.md#examples).
* **Decimal**: Default is not filled; when the tag attribute includes write, you can set the Decimal. In this case, device value * decimal = display value. If the point Decimal is 0.1, and the value written into the device is 234, the display value is 23.4.
* **Address**: Fill in the tag address, for example, 1!40001. 1 represents the tag site number set in the Modbus simulator, and 40001 represents the tag register address. For detailed instructions on how to use the driver address, please refer to [South Device - Modbus TCP](./modbus-tcp/modbus-tcp.md#examples).
* **Decimal**: not filled in by default; when the tag attribute includes read, you can set the Decimal. In this case, device value * decimal = display value.
* **Bias**: not filled in by default; when the tag attribute is read, it supports setting Bias. At this time, device value + Bias = display value.
* **Precision**: Configure the precision when the point type is float or double. The precision range is 0 to 17.
* **Description**: Default is not filled.
* **Description**: not filled in by default.

::: tip
Once the tag is created and the equipment card is operational, the connection status should display as **Connected**. If the status remains as **Disconnected**, please execute the following commands in the terminal of the Neuron runtime environment. This will help verify if the Neuron runtime environment can access the appropriate IP address and port.
Expand Down Expand Up @@ -139,4 +139,4 @@ Key field descriptions are as follows:

### Troubleshooting

If there are any issues with device operation, you can click on the DEBUG log chart. The system will automatically print DEBUG level logs for that node and switch back to the system default log level after ten minutes. Later, you can click on **System Information** -> **Logs** at the top of the page to view logs and perform troubleshooting. For a detailed interpretation of system logs, see [Managing Logs](../../admin/log-management.md).
If there are any issues with device operation, you can click on the DEBUG log chart. The system will automatically print DEBUG level logs for that node and switch back to the system default log level after ten minutes. Later, you can click on **System Information** -> **Logs** at the top of the page to view logs and perform troubleshooting. For a detailed interpretation of system logs, see [Managing Logs](../../admin/log-management.md).

0 comments on commit b41845a

Please sign in to comment.