DeviceSupervisor Agent
The software described in this manual is according to the license agreement, can only be used in accordance with the terms of the agreement.
© 2024 InHand Networks All rights reserved.
The InHand logo is a registered trademark of InHand Networks.
The company reserves the right to change this manual, and the products are subject to subsequent changes without prior notice. 9. We shall not be responsible for any direct, indirect, intentional or unintentional damage or hidden trouble caused by improper installation or use.
Protocol Name | Interface Type | note |
DLT645-1997 | Serial port | Chinese standards for electric power meters |
DLT645-2007 | Serial port | Chinese standards for electric power meters |
DLT645-2007 over TCP | Ethernet | Chinese standards for electric power meters |
*DLT698 | Serial port | - |
DNP3 TCP | Ethernet | - |
DNP3 UDP | Ethernet | - |
DNP3 RTU | Serial port | - |
IEC 101 | Serial port | - |
IEC 103 (NR Electric) | Serial port | NR Electric |
IEC 104 | Ethernet | - |
IEC61850 | Ethernet | - |
Interface Type |
note |
|
Northbound Cloud Service
List:
Northbound
Protocol Conversion List:
SparkplugB is an industrial IoT data transfer specification built on MQTT 3.1.1. |
|
Docking with Siemens' MindSphere IoT platform. Internal beta, some issues may exist. |
Fast function processing module:
Northbound protocol conversion:
Turn on the power to the gateway and connect the IG gateway to the PLC according to the topology using an Ethernet cable/serial cable.(The topology diagrams for the EC and IG series are the same, using the IG502 as an example.)
The wiring instructions for the IG502 serial port are as follows:
For details about the default IP address of the InGateway network port, see the IP address information on the nameplate. In order for the InGateway to access the Ethernet PLC through the network port, the network port must be in the same network segment as the PLC.
When using DSA, the firmware version should be 'V2.0.10' or later for the EC942 and 'V2.0.1' or later for the EC312
Update the firmware version as shown in the figure (the firmware version will take effect after the firmware version is restarted):
When using DSA, the SDK version should be py3sdk-V1.4.5 or later. Please refer to the table for the minimum firmware version requirements:
IG Series | The firmware version number of the lowest legacy naming convention | The firmware version number of the minimum new version of the naming convention |
IG974 | V2.0.0.r14106 | V2.0.3 |
IG902 | V2.0.0.r14047 | V2.0.3 |
IG532 | V2.0.0.r14238 | V2.0.1 |
IG504 | none | V2.0.5 |
IG502 | V2.0.0.r14045 | V2.0.5 |
Update the SDK as shown in the image:
Please refer to the following procedure to install and run DSA in EC series:
Click the "Add" button and select the DSA package file to be installed, then click Confirm.
After a successful import, you can view the imported App as shown in the following diagram:
If the installed App supports modifying the runtime method by importing a configuration file, you can follow the process below to update the App's runtime configuration:
After a successful import, it will run according to the imported configuration file.
To update the DSA version simply import the new version of the DSA package on the following page as shown below:
After the update is completed, it will appear as shown below:
View/download the logs during the DSA run in the screen shown:
After selecting the log level in "Level", logs lower than this level will not be displayed and saved. Log level sorting: ERROR>WARN>INFO>DEBUG>All.
To download the log, click the "Download" button.
Refer to the following procedure to install and run DSA in IG Series:
You need to ensure that the Python SDK is installed and the Python Edge Engine is enabled before installing the DSA, as shown below:
Click the "Add" button and select the App package file you need to install, then click confirm.
After a successful import, you can view the imported DSA as shown in the diagram below:
Check the “Enable” box to run the App.
Once enabled, the App will run on IG series products and automatically run every time the device is powered on.
If you need to update the global configuration file of the DSA, you can refer to the following procedure:
Restart the DSA after a successful import and it will run according to the imported configuration file after the restart is complete.
To update the version of DSA, you typically only need to import the new version of the App.
After the update is completed, the interface will appear as shown in the diagram below:
View/download the logs during the running of the DSA in the interface as shown:
After setting the log level, logs higher than this level will be displayed and saved. The log level is set in the Parameter Settings interface, and the log level is sorted: ERROR>WARN>INFO>DEBUG.
This tutorial takes the Modbus TCP protocol as an example to get a quick start on the simple and practicalities of using the DSA to capture ModRSsim2 analogue device data and upload the data directly to the EMQX MQTT public cloud service and convert it to Modbus TCP slaves for Modbus poll collection, as well as edge measurement data processing. The overall flow of the configuration is shown below:
The tutorial uses ModRSsim2 as the Modbus TCP Slave. Run the ModRSsim2.exe software and configure the port number as shown in the diagram:
After running device_supervisor, add a southbound controller. In the controller protocol, select the Modbus TCP protocol and configure the relevant parameters.
In the list of measuring points, add the device measuring points needed for collection and configure the measuring point's name, address, data type, etc., as shown in the diagram below:
Once configured, click “Confirm” to add the measuring points. After creating the measuring points, wait a few seconds; if the controller connection status is still disconnected, perform the following actions to find the reason:
After the southbound acquisition configuration is complete, you can see the status and acquisition data of the controller and the measurement point in the measurement point monitoring page, as shown in the following figure:
Enable the MQTT cloud service and configure the server address, MQTT client ID, port number, and other parameters as shown in the diagram:
If the connection drops after a while, check if the MQTT client ID has been used, or consider changing the client ID.
After the MQTT connection is successful, add a publishing script as shown below:
As shown in the figure below, add a subscription script:
# Enter your python code.
import json
from common.Logger import logger
from quickfaas.measure import write_plc_values
def write_callback(message, userdata):
logger.debug("write plc response: %s, userdata:%s" % (message, userdata))
def main(topic, payload, cloudName):
logger.debug("subscribe topic: %s, payload: %s, cloudName: %s" % (topic, payload, cloudName))
write_plc_values(message=json.loads(payload), callback=write_callback, userdata="")
The tutorial uses the client tool provided by the EMQX official website to connect to the public EMQX broker to view the data uploaded by the gateway to the MQTT Broker.
On the EMQX official website (https://www.emqx.com/en/mqtt/public-mqtt5-broker), choose to use the MQTT client tool online for testing
Click "New Connection" in the pop-up window that opens. After filling in the Name field in the pop-up interface, the rest of the configuration does not need to be modified. Finally, click "Connect".
In the MQTT client, write the value of the simulator collected by the gateway, as shown in the following figure, modify the value of the measurement point "WORD" collected by the gateway to 10, Paylaod:{"WORD": 10}
Click Protocol Conversion, find the Modbus TCP Slave menu bar, select "Configuration", set the information and submit. As shown in the figure below:
Adopt the default slave address 1, click "Batch Add", set the starting mapping address, select the measurement point under the corresponding controller and click submit, as shown in the following figure:
When the addition is complete, it is shown in the following figure:
The Mapped Address column shows the register address information for the corresponding measurement point.
Use Modbus Poll software as Master to collect the data from the gateway, set the connection information to the IP address and port number of the gateway, the slave address is set to 1, the start address of the register read is 40001, and the length of the register is 4, as shown in the following figure:
The data read after successful setup is the same as the data seen on the page of the Measure Monitor, as shown in the figure below:
In the Custom QuickFunctions menu bar, click to add a "Periodic trigger" QuickFunctions, set to run in 10-second cycles, the function code for the recall of a southbound collection of data, as shown in the figure below:
# Enter your python code.
from common.Logger import logger
from quickfaas.measure import recall2
def recall2_callback(message, userdata):
logger.info("recall2 response message: %s, userdata:%s" % (message, userdata))
def main():
logger.info("Timer start")
recall2(callback=recall2_callback, userdata="")
logger.info("Timer end")
In the Custom QuickFunctions menu bar, click to add a "Local Subscription Message Trigger" quickfunction, subscribe to the theme is: ds2/eventbus/south/read/+, the theme is the south to the driver to release the controller measurement point value of the message bus, used to get to the south of the cycle acquisition data, as follows shown in the figure:
After the settings are completed, submit. Each time a round of data is collected in the southward direction, this script will be triggered once and the collected data will be output to the log.
In the Custom QuickFunctions menu, click to add a "Power trigger" quickfunction to indicate that the script will be triggered once when the DSA starts up, as shown in the following figure:
Once set up, the script is triggered to run once when the DSA starts.
Name | Description |
Controller | The controller refers to the component on the gateway page that enables and manages various collection protocols. |
(Southbound) Driver | The (southbound) driver refers to the software program in the gateway that communicates with PLC devices. It is usually developed specifically for certain manufacturers or device types and communicates using the device manufacturer's management protocols or APIs, such as Modbus, OPC, etc. |
Measuring Point | A measuring point refers to a collection point for PLC devices configured on the gateway. |
Grouping | Grouping refers to dividing measuring point data or alarm items into different groups within the gateway according to different needs and application scenarios for easier management. |
Historical Database | Store the historical collected data of the measurement points in the sqlite3 database. |
QuickFunction | The publishing, subscribing and custom quick functions configured in DSA are executed in the form of independent threads. |
Protocol Conversion | Protocol conversion refers to forwarding data collected from the southbound direction through other protocols. |
Alarm | An alarm refers to the configuration of alarm conditions for collected data within the gateway, which triggers an alarm when activated. |
Event Bus | The event bus refers to the message channel used for communication between various services within the gateway using MQTT messages. |
Data Transformation | The collected data can configure data operations and mapping values in the gateway. |
In the "Monitoring List" interface, you can add controllers and measuring points to collect PLC data, and view the status and configuration information of the controller as well as data collection information.
On the current page, the controller can be edited, copied, deleted, etc.; the measuring points can be added, imported, exported, deleted, etc.
The page display of the monitoring list is as shown in the figure:
Click the "Add"/"Edit" button, select the controller protocol, such as Modbus RTU, and configure the controller's slave address, communication method, polling cycle and other parameters on the add controller page. Note: Controller names cannot be repeated.
In the advanced settings, the controller's message processing can be configured. For example, in the advanced settings of the Modbus RTU controller, parameters such as byte order, timeout time, and communication time can be configured.
In industrial settings, there are often many similar PLC configuration parameters and measuring point configurations. To achieve rapid configuration, we have introduced the "Copy Controller" function. This feature allows us to quickly add controllers and measurement point configurations with similar settings, avoiding repetitive configuration tasks. Click on the "..." in the top right corner of the controller card to display more controller actions, then click "Copy". After configuring one controller, you can quickly add a second one; the copy controller will duplicate all the measurement points under the controller.
After clicking the "Copy" button, you can modify the differing configurations as needed, such as the controller name, slave address, etc., and then submit.
Upon completion of the copy, as shown in the diagram, the system will automatically generate measurement points and controller information identical to the first controller:
When collecting data from multiple PLC devices and the gateway controller status or collected data is abnormal, we enable only the problematic controller for easy log viewing and real-time communication packet inspection. Click on the "..." in the top right corner of the controller card to display more controller actions, and select "Disable". After that, the controller will no longer perform data collection and reporting.
After disabling, the controller card will turn gray, as shown in the diagram.
When you want to re-enable the controller, click on the "..." in the top right corner of the controller card and select "Enable". The controller will then resume data collection and reporting.
When the controller status displays as abnormal or there is abnormal data collection, viewing the real-time communication messages between the gateway controller and the PLC devices becomes crucial. DSA supports displaying channel real-time communication messages. Select a controller at will, click "..." in the upper right corner of the controller card, and click "Real-time Communication Messages" to display all communication message interactions of the current channel.For example, if two Modbus RTU protocol controllers are enabled and both use an RS485 communication port, the real-time communication messages will show the communication messages of both controllers.
The display effect of real-time communication messages is as follows (Note: If you need to download communication messages, you need to enable "Store Communication Messages" in the advanced settings of the controller configuration before the "Download" button will be displayed. Communication messages of all controllers The text is displayed and saved in HEX format):
In the "Measuring Point List," you can add measuring points to collect data from PLC devices. Click the "Add" button, and in the pop-up box, configure the measuring point parameters, such as adding a measurement point under a Modbus RTU protocol controller and configuring the measurement point name, address, data type, etc. (Note: The measurement point name must be unique within its controller).
In the "Measuring Point List," the "Import" button allows you to import the measurement points from a CSV file into the current gateway; the "Export" button enables you to export the current gateway's measurement point configurations to a CSV file. For details on the specific measurement point CSV file, refer to the Measuring Point CSV File Parameter Description.
Group allows you to manage measuring points in the monitoring list by dividing them into groups. After the measuring points are grouped, the storage of historical data and measuring point reporting intervals are managed according to the configured groups. If you need to configure different reporting intervals for the measuring points or need to report corresponding data of the measuring points according to different MQTT topics, you can add a new group to manage the measuring points with different requirements. (Note: The default group cannot be deleted)
The group interface is shown in the figure:
For specific group CSV files, please refer to the Grouping CSV File Parameter Description
Add a new group on the group page. The interface is as follows:
Add group parameters Introduction:
- Max Number: The maximum number of historical data stored in a single group.
- Storage policy: Storage interval of historical data
- Same AS the Reporting Interval: Store historical data according to reporting interval.
- Independent Storage Interval: customize the storage interval of historical data.
- Storage Method: The storage method of historical data. Switching the storage path will clear the stored historical data
- Gateway Storage: Historical data is stored in the storage space of the gateway itself.
- USB: Historical data is stored in a USB storage space external to the gateway.
- SD Card: Historical data is stored in the SD card storage space external to the gateway.
After adding a group, when adding a measuring point, you can choose to associate the measuring point with the group or select the measuring point in the list of measuring points to add to the specified group. The measuring points in the group will report data according to the reporting interval of the group.
Click "Export Historical Data" to export the group's historical data in CSV format
Click "Clear Historical Data" to clear the historical data stored in this group.
The historical database is used to store the historical data of the measuring points. After enabling the "Store Historical Data" function in the configuration of the measuring points, the data of the measuring points can be stored in the historical database. The historical data of measuring points is stored according to the groups they belong to. This arrangement makes it more convenient to locate and export historical data for specific measuring points.
After configuring alarm rules and when alarms are triggered, the real-time alarm page will display all triggered alarm items.
In the real-time alarm table, some parameters from the alarm configuration, such as "Name," "Controller," "Alarm Level," etc., will be shown.
Below is an example of a real-time alarm display interface.
Alarm rules can help us monitor the value of measuring points on the gateway side, and remind us in time when it exceeds the normal range. For example, in industrial scenarios, the range of voltage and current values and the start and stop status of some equipment need to be focused on. When we configure the alarm rules for collecting these data measuring points on the gateway side, if an alarm is triggered, the MQTT cloud service can be used to report the notification in time to avoid unnecessary losses.
On the alarm rules page, configure the alarm rules by clicking the "Add" button. In the pop-up box, set up the alarm rule parameters. The parameters include:
- Judgment condition: Support "=", "! = ", ">", "≥", "<", "≤"
- Logical conditions:
- No logic condition: The alarm is judged only by a single judgment condition
- && : Judging an alarm by two judging conditions
- | | : To determine an alarm, use a logical OR relationship between two conditions. This means that the alarm is triggered if either of the two conditions is met.
The following picture shows an alarm with alarm level of alert, which belongs to the default tag. This alarm is generated when the value of the measuring point is >30 and <50; When it is not in this range, no alarm will be generated or the alarm will be eliminated.
In the "Alarm Rules" page, "Import" and "Export" CSV files of alarm rules refer to the Alarm Rules CSV file parameter description
The "Add to Label" function can help us quickly switch multiple alarm items to the alarm label. The following picture is the batch addition of alarm items to the "group_test" alarm label.
The historical alarms page can help us view the history of all alarm items, including triggered and recovered alarms. This function can help us understand the reason and time when the gateway side triggers/recovers the alarm items.
In the current page, you will see information about all the historical alarms that have been triggered and recovered.
The current page displays parameters that include those configured on the "Alarm Rules" page, such as "Name," "Controller," "Alarm Level," and "Alarm Content." Other parameters in the table are as follows:
The alarm label can help us manage the alarm items. When the alarm item triggers an alarm, the MQTT message needs to be reported. Directly selecting the alarm label can quickly include all the alarm items under the alarm label. And when we need to report MQTT messages with different topics, we can add an alarm label to group different alarm items, and then select the corresponding label in different MQTT topics.
Go to the alarm label page to view the content of the alarm label.
In the table on the current page, there will be an alarm label named "default" by default (Note: this label cannot be deleted, and the rest of the added alarm labels can be deleted).
After clicking the "Add" button, configure the name of the alarm label in the pop-up box. (Note: This name is unique throughout the alarm label and cannot be repeated).
In the "Alarm Label" page, "Import" and "Export" Alarm rule CSV files, please refer to the Alarm label CSV file parameter introduction
Note: When deleting a label, the alarm items belonging to the current label in the "Alarm Rule" will be deleted together
In industrial scenarios, the collected data needs to be reported to the cloud platform to help enterprises achieve centralized management, intelligent analysis and remote management of data. In DSA, we can enable and configure corresponding cloud services in the cloud service interface to help customers quickly connect to use mainstream cloud services.
In the current page, you can view the connection status and configuration information of the current MQTT cloud service, and you can edit, import, export and other operations on the MQTT cloud service. Click the "Add" button to add a new MQTT cloud platform. For example, when we need to report data to multiple cloud platforms at the same time, we can add a new MQTT platform to connect to the cloud platform to report data. (Note: the name of the MQTT platform cannot be repeated, and the name of the default MQTT cloud platform is "Default"). As shown in the figure, add an MQTT platform with the name "test" :
The interface after adding is as shown in the figure:
After checking Enable cloud services, MQTT cloud services can be selected in the "Cloud Types" of the configuration interface. "Cloud Types" : The currently supported cloud platforms are "MQTT", "MQTT SparkPlugB", "iSCADA Cloud", "Eagle Energy Manager", "Alibaba Cloud", "AWS IoT", "Azure IoT".
In industrial settings, data often exhibits diversity and complexity, and different application scenarios may require different communication protocols to meet their specific needs. DSA's protocol conversion functionality enables data to be uploaded in various application scenarios through different protocols. For example, using the Modbus TCP Slave protocol, data collected by controllers can be forwarded to SCADA servers.
The status page allows you to view the connection and running status of the current protocol (Note: not all protocols have status pages, such as BACnet Server protocol)
The configuration page can configure and view the connection parameters and add the mapping table function for the current protocol. For example, in the Modbus TCP Slave configuration interface, you can configure the Modbus TCP Slave port number, the maximum number of connections and other parameters. In the mapping table, you can perform add/edit, import/export and other operations.
For the specific mapping table CSV file, please refer to the Mapping table CSV file parameter introduction
For specific protocol configuration, please refer to the Appendix: Protocol conversion
In the parameter setting screen, you can configure the general Settings of the gateway. Such as setting gateway serial port parameters, storage configuration and custom parameters.
In the serial port Settings page, you can configure the parameters of the serial port, such as the configuration of the serial port baud rate, data bits, etc.
The parameters of serial port Settings are shown in the figure:
The parameters are explained as follows (same for RS232 and RS485) :
Click the "Submit" button to save your configuration after you've modified it.
In the storage configuration interface, you can configure the log storage of the gateway, the MQTT offline data storage and the communication packet storage of the controller.
The parameters of storage configuration are shown in the figure:
The parameters are explained as follows:
After modifying the configuration, click the "Submit" button to save the configuration. If you do not want to save the current changes, click the "Reset" button to restore the last saved configuration
Custom parameters are to define some global parameters, which can be used in cloud service configuration, fast function scripts. Set a global parameter to use, you can modify it more conveniently and quickly. For example, when a parameter needs to be used in multiple custom fast functions, if a custom parameter is used, then when the parameter value is changed, only the parameter value of the custom parameter interface is changed.
The parameters for custom parameters look like this:
By default, there are two parameters (note: these two parameters cannot be deleted or modified) :
If you want to add custom parameters, click the "Add" button, fill in the "Parameters" and "Parameters value" in the pop-up window, and click the "Confirm" button to add the modified value.
The "Import" and "Export" buttons can import the custom parameter configuration file to the current gateway and export the custom parameter of the current gateway into a configuration file respectively. For the specific CSV file, please refer to: Custom parameters CSV file parameter introduction
You can add your own common parameters in custom parameters to be used as wildcards in cloud services and custom fast functions. The method is ${parameter name}, as shown in the following figure:
Custom parameters can also be used in scripts to get all custom parameters via the get_global_parameter() function.
An example script is as follows: (This script can output all the custom parameters in a log)
from common.Logger import logger
from quickfaas.global_dict import get_global_parameter
def main():
logger.debug('get global dict: %s' % get_global_parameter())
The output will be:
In the custom quickfunctions screen, you can add Python scripts to implement private logic (new scripts are enabled in a threaded manner). Custom fast function scripts support three trigger modes: periodic trigger; Local Subscription Message Trigger; QuickFunction start trigger.
The custom quick function interface button is introduced as shown below:
A period-triggered quickfunction will trigger the script to run after the period ends
Below is a custom quickfunction that adds a 10-second cycle trigger, using the default script. This script will log "Timer start" and "Timer end" every 10 seconds.
The instructions for each parameter are as follows:
Local subscribe message trigger triggers the run script once when subscribed to the Topic that needs to be subscribed. The Topic on the gateway Event Bus can be looked from the Event BUS
Below is the local subscribe message fast function that adds a subscribe controller write value message. This script will be triggered when a value is written to the controller. With the default script, the write value message will be printed to the log
The parameters are described as follows:
The QuickFunction start trigger, only when the fast function start is complete, triggers the run script once.
The diagram below shows how to add a quickfunction in the QuickFunction Start Trigger mode. Using the default script, "QuickFunction start" will be printed in the logs when the quickfunction is initiated.
The parameters are described as follows:
This feature is only supported on IG. The third-party libraries and the description file lib.info are packaged and compressed together on the IG gateway, and can be imported and installed at this page. lib.info describes the information of the library file in the format of json as follows:
{
"name": "rsa", //library name
"version": "4.9", //library version number
"desc": "", //library descriptive information
"files": "rsa" //library file paths, more than one separated by spaces
}
Then put the lib.info file and the library file information together in a compressed package as a .zip or .tar.gz file, and then import and install it.
*ABB Robot
ABB Robot is a range of industrial robotic products manufactured by ABB for use in a variety of applications on automated production lines.ABB Robot communicates with external devices, control systems or host computers via the TCP/IP protocol for data exchange, control and monitoring functions.
EtherNet/IP is an industrial Ethernet protocol, which is used to realize communication and data exchange between devices in industrial control systems. It is based on the standard TCP/IP protocol stack, and added to it the application layer protocol used in the field of industrial automation, providing the support of real-time, reliability and security.
- Timeout: The timeout time for the device to respond after the reading request is initiated to the device when the measuring point is collected. If the device does not respond to the reading request within the set collection timeout time, it is still the failure of this collection.
- Connect Timeout: the timeout time for establishing the connection.
- Store Communication Messages: The controller with this function enabled will store communication messages. The storage path and number can be set in the "Default Parameters" of the "Parameter Settings" page. If you need to download the stored communication message, you can enter the " Realtime Communication Message " page of the specified controller in the "Measure Monitor" page, and click the "Download" button to download.
A1: Consistent with the PLC address, pay attention to the data type should also be consistent;
Program:MainProgram.A1: If the variable is local, prefix it with the program name;
slot=2; A1: Addresses can also carry additional slot information;
i=A[0] : If A in PLC is based on A bool array of uint type, each bit in A can be accessed using this way;
B[0] : If B is an array, each element can be accessed using an index
EtherNet/IP (Micro) is a variant of the EtherNet/IP protocol designed for smaller devices and resource-constrained environments. Compared with the standard EtherNet/IP protocol, EtherNet/IP (Micro) uses a more simplified message format and lightweight communication mechanism in the communication process to reduce resource consumption and communication overhead.
- Timeout: The timeout time for the device to respond after the reading request is initiated to the device when the measuring point is collected. If the device does not respond to the reading request within the set collection timeout time, it is still the failure of this collection.
- Connect Timeout: the timeout time for establishing the connection.
- Store Communication Messages: The controller with this function enabled will store communication messages. The storage path and number can be set in the "Default Parameters" of the "Parameter Settings" page. If you need to download the stored communication message, you can enter the " Realtime Communication Message " page of the specified controller in the "Measure Monitor" page, and click the "Download" button to download.
Adding measuring points
A1: Consistent with the PLC address, pay attention to the data type should also be consistent;Program:MainProgram.A1: If the variable is local, prefix it with the program name;slot=2; A1: Addresses can also carry additional slot information;i=A[0] : If A in PLC is based on A bool array of uint type, each bit in A can be accessed using this way;B[0] : If B is an array, each element can be accessed using an index
EtherNet/IP (MicroLogix) refers to the use of EtherNet/IP protocol for communication in the MicroLogix controller family
- Timeout: The timeout time for the device to respond after the reading request is initiated to the device when the measuring point is collected. If the device does not respond to the reading request within the set collection timeout time, it is still the failure of this collection.
- Connect Timeout: the timeout time for establishing the connection.
Store Communication Messages: The controller with this function enabled will store communication messages. The storage path and number can be set in the "Default Parameters" of the "Parameter Settings" page. If you need to download the stored communication message, you can enter the " Realtime Communication Message " page of the specified controller in the "Measure Monitor" page, and click the "Download" button to download.
A9:0: ASCII
B2:0: Bit
N2:0:Integer
L17:0:Long Integer
ST2:0:String
F8:5:Floating
S:1/15:Status
C2:0:Counter
T2:0:Timer
I:0/15:Input
O:0/15:Output
EtherNet/IP (Unconnected) refers to a method of communication used in the EtherNet/IP protocol. Unconnected means that there is no need to establish a persistent connection when communicating, and each communication is independent and immediate. This method is similar to the connectionless communication method in the UDP protocol, which is more lightweight and flexible, and is suitable for some scenarios with less stringent real-time requirements.
- Timeout: The timeout time for the device to respond after the reading request is initiated to the device when the measuring point is collected. If the device does not respond to the reading request within the set collection timeout time, it is still the failure of this collection.
- Connect Timeout: the timeout time for establishing the connection.
- Store Communication Messages: The controller with this function enabled will store communication messages. The storage path and number can be set in the "Default Parameters" of the "Parameter Settings" page. If you need to download the stored communication message, you can enter the " Realtime Communication Message " page of the specified controller in the "Measure Monitor" page, and click the "Download" button to download.
Adding measuring points
A1: Consistent with the PLC address, pay attention to the data type should also be consistent;
Program:MainProgram.A1: If the variable is local, prefix it with the program name;
slot=2; A1: Addresses can also carry additional slot information;
i=A[0] : If A in PLC is based on A bool array of uint type, each bit in A can be accessed using this way;
B[0] : If B is an array, each element can be accessed using an index
SLC Net stands for "Symbian Limited Compatibility Network" and it is the network communication protocol for Symbian OS. Symbian OS is a kind of operating system that has been widely used in smart phones and mobile devices. It provides a wealth of functions and application support.
- Timeout: The timeout time for the device to respond after the reading request is initiated to the device when the measuring point is collected. If the device does not respond to the reading request within the set collection timeout time, it is still the failure of this collection.
- Connect Timeout: the timeout time for establishing the connection.
- Store Communication Messages: The controller with this function enabled will store communication messages. The storage path and number can be set in the "Default Parameters" of the "Parameter Settings" page. If you need to download the stored communication message, you can enter the " Realtime Communication Message " page of the specified controller in the "Measure Monitor" page, and click the "Download" button to download.
A9:0: ASCII variable
B2:0: Bit variable
N2:0: Integer variables
F8:5: Floating point
S:1/15: Status variable
ST2:0: String
C2:0: Counter
I:0/15: Input
O:0/15: Output
R9:0: Control
T2:0: Timer
L9:0: Long Integer
BACnet is a communication protocol used in building automation and control systems for data communication and control between building devices. Communication is based on the Internet Protocol (IP).BACnet IP uses a standard IP network as the communication medium to connect building devices via network devices such as Ethernet or Wi-Fi for data exchange and control between devices.
Advanced Settings:
BACnet MS/TP (Master-Slave/Token-Passing) is a variant of the BACnet protocol used to communicate in serial networks in building automation systems.MS/TP is a common BACnet physical layer protocol typically used to connect building devices such as sensors, actuators, and controllers via serial communication for data exchange and control.
Advanced Settings:
A communication protocol and communication mechanism commonly used in Beckhoff industrial automation systems, ADS is a high-performance, real-time communication protocol for communication between Beckhoff controllers, Engineering Stations and other ADS-enabled devices.
Advanced Settings:
CJT188-2004 is a Chinese communication standard for data transmission and communication in monitoring and control systems. This standard is mainly applicable to monitoring and control systems in the fields of electric power systems, power transmission and distribution equipment, substations, etc., in order to realise data exchange, monitoring and control between equipment.
Advanced Settings:
Delta TCP refers to the communication method based on the TCP/IP protocol used by Delta Electronics.Delta TCP can be used for data acquisition and processing applications. By connecting to a data acquisition device or database system, real-time acquisition, storage and analysis of equipment data can be achieved to monitor and optimise the production process.
Advanced Settings:
Delta Serial refers to the serial communication method used by Delta Electronics. It can be used for data acquisition and processing applications. By connecting with data acquisition equipment or database systems, real-time acquisition, storage and analysis of equipment data can be achieved to monitor and optimise production processes.
Delta Serial refers to the serial communication method used by Delta Electronics. It uses ASCII code as the encoding format for data. It can be used for data acquisition and processing applications. By connecting to a data acquisition device or database system, real-time acquisition, storage and analysis of equipment data can be achieved to monitor and optimise the production process.
Delta Serial over TCP is a method of transmitting Serial Communication over a TCP/IP network. Delta Electronics typically uses this method for remote monitoring, remote control, and data acquisition of its equipment.
Advanced Settings:
DLT645-1997 is a version of the Chinese national standard GB/T 645-1997 "Multi-function Meter Communication Protocol". This standard specifies the communication protocol and data format between the multi-function meter and the external equipment, which is used for data exchange and communication between the meter and the monitoring system.
DLT645-2007 is a version of the Chinese national standard GB/T 645-2007 "Multi-function Meter Communication Protocol". This standard is an important version of the DLT645 series of standards, which is used to specify the communication protocol and data format between the multifunctional electric energy meter and the external equipment.
- WORD: 16-bit unsigned integer
- INT: 16-bit signed integer
- DWORD: 32-bit unsigned integer
- DINT: 32-bit signed integer
- FLOAT: 32-bit floating point number
- DOUBLE: A 64-bit floating point number
- STRING: 8-bit string
- Read: read-only, not writable
- Read/Write: Readable and writable
- Periodic: Periodically reports data according to the reporting period of the group it belongs to
- Onchange: When the value of the measuring point changes, the data will be reported periodically according to the reporting period of the group
- Never: Only used locally, no need to upload data from the cloud
- Decimal Places: The number of decimal places that need to be retained after the operation
- Data High Limit: The upper limit of the data of the measuring point
- Data lower Limit: the lower limit of the data at the measuring point
- High Limit Of Proportion: the upper limit of the data after the proportion operation
- Lower Limit Of Proportion: The lower limit of the data after the scale operation
- Decimal Places: The number of decimal places to be retained after the operation
- Magnification: The multiplier that needs to be scaled up or down
- Offset: The data value that needs to be increased or decreased after the multiplier operation
- Start Bit: The bit offset at which the intercept of the original data begins
- End Bit: The bit offset that ends the interception of the original data
- Decimal Places: The number of decimal places that need to be retained after the operation
- Magnification: The multiplier that needs to be scaled up or down
- Offset: The data value that needs to be increased or decreased after the multiplier operation
- PT: Additional PT multiplier
- CT: Additional CT magnification
- Source Value: The raw value of the collected measuring point.
- Target Value: The expected value of the converted measuring point.
DLT645-2007 over TCP refers to the DLT645-2007 communication protocol applied to TCP/IP network communication mode. DLT645-2007 is a version of the multi-function meter communication protocol, and TCP is a common transmission control protocol used to achieve reliable data transmission in the network. The communication mode of DLT645-2007 over TCP can make full use of the reliability and stability of TCP protocol to ensure the safe transmission and reliable reception of data. This method is suitable for remote monitoring and management of electric energy data scenarios, such as power system monitoring, energy management systems, etc.
Advanced Settings:
- Timeout: The timeout time for the device to respond after the reading request is initiated to the device when the measuring point is collected. If the device does not respond to the reading request within the set collection timeout time, it is still the failure of this collection.
- Connect Timeout: the timeout time for establishing the connection.
- Initialize activation: Whether to activate the command when opening the serial port. After opening, add FE FE FE FE to the packet frame header.
- Communication Timing Settings:
- Communication Interval: The interval time between message exchanges, i.e., after receiving a response from the device, it will wait for a communication interval before sending the next request message.
- Communication Message Settings:
- Storage of communication messages: The controller with this function enabled will store communication messages. The storage path and number can be set in the "Default Parameters" of the "Parameter Settings" page. If you need to download the stored communication message, you can enter the " Realtime Communication Message " page of the specified controller in the "Measure Monitor" page, and click the "Download" button to download.
DLT698 is an implementation of Chinese national standard GB/T 26880-2011 "Power information acquisition system communication protocol", it is based on the IEC 62056 series standard (DLT645) power information acquisition system communication protocol. DLT698 is mainly used for data acquisition, transmission and management in electric power information acquisition system. It is a general communication protocol in electric power industry.
DNP3 TCP (Distributed Network Protocol 3 over TCP/IP) is a reliable and efficient communication protocol for remote monitoring and control systems, and is oriented towards communication protocols for remote monitoring and control systems, which are applicable to the automation of infrastructure such as electric power systems and water systems.
Advanced Settings:
DNP3 UDP is an application of the DNP3 protocol on the transport layer of the UDP network.UDP is a connectionless oriented transport protocol that provides simple data transfer services and is usually used in scenarios that require high real-time performance, small data transfer volumes, and low data reliability requirements. For example, in applications such as remote monitoring, telemetry, and remote control, DNP3 UDP can be used for data transmission for real-time monitoring and control.
Advanced Settings:
In DNP3 RTU, RTU is a kind of remote terminal unit, which is used for tasks such as data acquisition, monitoring and control, etc. DNP3 RTU is an RTU device based on the DNP3 protocol, which is usually used for real-time monitoring and control of electric power systems, water systems, gas systems and other industrial control fields.
Advanced Settings:
EFORT Robot is a series of industrial robots produced by EFORT Intelligent Equipment Co., Ltd. which can exchange data, control, monitor and access the robot remotely via TCP/IP protocol.
Advanced Settings:
Adding measuring points
Euromap-63 is a standard protocol for communication between industrial robots and injection moulding machines. The injection moulding machine can send relevant data of the injection process to the industrial robot, such as information on mould opening and closing status, injection speed, temperature, etc. The industrial robot can perform corresponding actions based on these data, such as adjusting the gripping position and speed of action in time, in order to achieve efficient operation of the automated production line.
Advanced Settings:
FANUC Robot is a series of industrial robot products produced by Japan's FANUC company, its robot products are widely used in automotive manufacturing, electronics manufacturing, metal processing, logistics and other fields.
Advanced Settings:
FANUC CNC 0i is a type of numerical control system manufactured by FANUC Corporation in Japan. This type of CNC system is mainly used to control metalworking machine tools, such as CNC lathes, CNC milling machines, CNC grinding machines, etc., so that they can automate machining operations.FANUC CNC 0i CNC systems usually have a network communication function, allowing data monitoring and communication through the TCP/IP protocol. The TCP/IP protocol allows the user to establish a network connection with the FANUC CNC 0i system, monitor its status, read data, and send commands.
Advanced Settings:
The Programe Port provides a physical connection, usually a port, through which communication with the FATEK PLC can take place. This programming port is the interface used to connect the PLC to a programming device (e.g. a programmer or PC) for programming, debugging and data transfer.
Advanced Settings:
FATEK PLC products typically support a variety of communication methods, including programming and data communication over Ethernet (TCP/IP). By mapping the FATEK Programe Port onto a TCP/IP network, users can connect to the PLC over the network and use the appropriate programming software or tools to program, monitor and debug with the PLC.
Advanced Settings:
The SPB series PLCs are a series of programmable logic controller (PLC) products manufactured by Fuji.The SPB series PLCs usually support a variety of communication protocols and network connections, such as Ethernet, serial communications, etc., to facilitate data exchange and communication with other devices or higher-level systems.
Advanced Settings:
A communication method that encapsulates communication data from Fuji SPB series programmable logic controllers (PLCs) using serial communication protocols (e.g., RS-232, RS-485) and transmits it over a TCP/IP network.
Advanced Settings:
Fuji's SPH Net is one of Fuji Electric's (Fuji Electric) product lines, and it is a proprietary communication protocol.SPH Net is typically used to connect PLCs (Programmable Logic Controllers) and other automation equipment for data exchange and control.
Advanced Settings:
SRTP is a specific sub-protocol of the SNP protocol, which stands for Real-Time Protocol of SNP (Series Network Protocol).SRTP is usually used for real-time data transmission with high speed and low latency, and is suitable for application scenarios with high real-time requirements, such as control systems and data acquisition, and so on.
Advanced Settings:
HJ212-2005 is the earliest version of the HJ212 standard, which was released in 2005. It defines the communication protocol between the monitoring equipment and the data acquisition system, including data frame format, data transmission method, communication parameters, etc.
Advanced Settings:
HJ212-2017 is an update and improvement of the original HJ212 standard, released in 2017. It optimises and extends the 2005 protocol, making data transmission more stable, reliable and efficient.
Advanced Settings:
IEC 101 is a standard protocol developed by the International Electrotechnical Commission (IEC) for telecommunication. It is a communication protocol for monitoring and control of power systems, which is mainly used for applications such as remote monitoring, control, data acquisition and protection in power systems.