Difference between revisions of "Modbus TCP Server Send SMS example"
m (Dziugas.Syminas moved page Modbus TCP Slave Send SMS example to Modbus TCP Server Send SMS example) |
|||
(21 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | + | ==Introduction== | |
− | = | + | <p style="color:red">The information on this page is updated in accordance with [https://wiki.teltonika-networks.com/view/FW_%26_SDK_Downloads'''00.07.03.2'''] firmware version. .</p> |
'''Modbus''' is a serial communications protocol. Simple and robust, it has become a de facto standard communication protocol and is now a commonly available means of connecting industrial electronic devices. | '''Modbus''' is a serial communications protocol. Simple and robust, it has become a de facto standard communication protocol and is now a commonly available means of connecting industrial electronic devices. | ||
− | In this configuration example, we will configure Modbus TCP Slave and Modbus TCP | + | In this configuration example, we will configure Modbus TCP Slave and Modbus TCP Master. We will send a Set Parameters request from Modbus TCP Master to Modbus TCP Slave, which will send an SMS message provided in the Modbus TCP Master Set PArameter request. |
+ | |||
+ | If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should '''turn on "Advanced WebUI" mode'''. You can do that by clicking the "Basic" button under "Mode", which is located at the top-right corner of the WebUI. | ||
− | + | [[File:Networking rutx manual webui basic advanced mode v1.gif|border|class=tlt-border]] | |
− | [[File: | ||
== Prerequisites == | == Prerequisites == | ||
Line 16: | Line 17: | ||
* One Mobile Phone in order to test the configuration | * One Mobile Phone in order to test the configuration | ||
− | == Configuring Modbus TCP | + | == Configuring Modbus TCP Slave and Modbus TCP Master == |
− | Firstly, we will configure '''Modbus TCP | + | Firstly, we will configure '''Modbus TCP Slave''' on the router and then on the same device we will configure '''Modbus TCP Master''' in order to send Modbus requests to the same device. |
---- | ---- | ||
− | ===Configuring Modbus TCP | + | ===Configuring Modbus TCP Slave=== |
− | In order to start our configuration you will need to open your device's WebUI (by entering the device's IP address of your device), then navigate to '''Services → Modbus → Modbus TCP | + | In order to start our configuration you will need to open your device's WebUI (by entering the device's IP address of your device), then navigate to '''Services → Modbus → Modbus TCP Slave'''. |
− | In order to configure Modbus TCP | + | In order to configure Modbus TCP Slave follow the steps provided below: |
− | [[File: | + | [[File:Networking rut configuration modbus tcp slave v2.png|border|class=tlt-border|1100px]] |
'''Explanation:''' | '''Explanation:''' | ||
− | # Enable the Modbus TCP | + | # Enable the Modbus TCP Slave |
− | # Select the port on which Modbus TCP | + | # Select the port on which Modbus TCP Slave will communicate with the Modbus TCP Master (for this example: 502) |
# Enable persistent connection (not mandatory) | # Enable persistent connection (not mandatory) | ||
# Save the configuration | # Save the configuration | ||
---- | ---- | ||
− | ===Configuring Modbus TCP | + | ===Configuring Modbus TCP Master=== |
− | Lets continue with the configuration, now we will configure Modbus TCP | + | Lets continue with the configuration, now we will configure Modbus TCP Master on the same device. Navigate to '''Services → Modbus → Modbus TCP Master'''. Press the button '''ADD''' and follow the steps provided below: |
− | [[File: | + | [[File:Networking rut configuration modbus tcp master v2.png|border|class=tlt-border|1100px]] |
'''Explanation:''' | '''Explanation:''' | ||
# Enable the instance | # Enable the instance | ||
− | # Create a name for Modbus TCP | + | # Create a name for Modbus TCP Master |
− | # Provide the | + | # Provide the Slave ID (in this case: 1) |
− | # Provide IP address of the | + | # Provide IP address of the Slave ID, in this case, this router's IP (192.168.1.1) |
− | # Provide Modbus TCP | + | # Provide Modbus TCP Slave ID (in this case 502) |
+ | # In this part we will configure two different SMS messages (hex and ASCII formats) and one send a request to send those messages, we will configure it a little bit later, so leave this part empty for now. | ||
+ | # Save the configuration | ||
---- | ---- | ||
− | ===Configuring Modbus TCP | + | ===Configuring Modbus TCP Master Request Configuration=== |
− | Now that we have '''Modbus TCP | + | Now that we have '''Modbus TCP Master''' and '''Modbus TCP Slave''' configurated, we will need to create '''Request Configuration'''. The Request configuration will be used to store the SMS message and the number of the recipient. Lastly, we will send the SMS message to the recipient with the set Command. |
− | To store Phone numbers and SMS messages we will use '''ASCII''' and | + | To store Phone numbers and SMS messages we will use '''ASCII''' and '''HEX''' Data Types, you can configure either one of them, and both of them will work. |
---- | ---- | ||
So first of all, we will create a Request in which we will store the Recipient number and SMS message, we will use '''ASCII Data Type''', '''Set Multiple holding registers(16) Function''' and '''398 Register'''. | So first of all, we will create a Request in which we will store the Recipient number and SMS message, we will use '''ASCII Data Type''', '''Set Multiple holding registers(16) Function''' and '''398 Register'''. | ||
− | [[File: | + | [[File:Networking rut configuration modbus tcp master request v1.png|border|class=tlt-border|1100px]] |
Line 63: | Line 66: | ||
− | The first 10 registers are reserved for the phone number ('''1 register = | + | The first 10 registers are reserved for the phone number ('''1 register = 4 symbols''') additionally you will require to put in front '+' which is equal to 00 here. If your number (together with 00) does not take 10 registers we will require you to fill out the left registers with 0 values, thats why we use the '''\u0000 symbol''', which means 0 value. |
− | |||
− | |||
+ | Example Message request: | ||
---- | ---- | ||
− | |||
− | |||
− | |||
003706xxx1594\u0000\u0000\u0000\u0000\u0000\u0000\u0000test | 003706xxx1594\u0000\u0000\u0000\u0000\u0000\u0000\u0000test | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 13:20, 31 January 2023
Main Page > General Information > Configuration Examples > Modbus > Modbus TCP Server Send SMS exampleIntroduction
The information on this page is updated in accordance with 00.07.03.2 firmware version. .
Modbus is a serial communications protocol. Simple and robust, it has become a de facto standard communication protocol and is now a commonly available means of connecting industrial electronic devices.
In this configuration example, we will configure Modbus TCP Slave and Modbus TCP Master. We will send a Set Parameters request from Modbus TCP Master to Modbus TCP Slave, which will send an SMS message provided in the Modbus TCP Master Set PArameter request.
If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Basic" button under "Mode", which is located at the top-right corner of the WebUI.
Prerequisites
- At least one TRB/RUT device with the SIM card, for this example we will be using one device
- One end device (PC, Laptop, Tablet, Smartphone) to configure the router
- One Mobile Phone in order to test the configuration
Configuring Modbus TCP Slave and Modbus TCP Master
Firstly, we will configure Modbus TCP Slave on the router and then on the same device we will configure Modbus TCP Master in order to send Modbus requests to the same device.
Configuring Modbus TCP Slave
In order to start our configuration you will need to open your device's WebUI (by entering the device's IP address of your device), then navigate to Services → Modbus → Modbus TCP Slave.
In order to configure Modbus TCP Slave follow the steps provided below:
Explanation:
- Enable the Modbus TCP Slave
- Select the port on which Modbus TCP Slave will communicate with the Modbus TCP Master (for this example: 502)
- Enable persistent connection (not mandatory)
- Save the configuration
Configuring Modbus TCP Master
Lets continue with the configuration, now we will configure Modbus TCP Master on the same device. Navigate to Services → Modbus → Modbus TCP Master. Press the button ADD and follow the steps provided below:
Explanation:
- Enable the instance
- Create a name for Modbus TCP Master
- Provide the Slave ID (in this case: 1)
- Provide IP address of the Slave ID, in this case, this router's IP (192.168.1.1)
- Provide Modbus TCP Slave ID (in this case 502)
- In this part we will configure two different SMS messages (hex and ASCII formats) and one send a request to send those messages, we will configure it a little bit later, so leave this part empty for now.
- Save the configuration
Configuring Modbus TCP Master Request Configuration
Now that we have Modbus TCP Master and Modbus TCP Slave configurated, we will need to create Request Configuration. The Request configuration will be used to store the SMS message and the number of the recipient. Lastly, we will send the SMS message to the recipient with the set Command. To store Phone numbers and SMS messages we will use ASCII and HEX Data Types, you can configure either one of them, and both of them will work.
So first of all, we will create a Request in which we will store the Recipient number and SMS message, we will use ASCII Data Type, Set Multiple holding registers(16) Function and 398 Register.
In the Register Count / Values field we will be written the ASCII format (human-readable format) and in the Data Type we will select ASCII format, so there will be no data conversion that it is why we will be writing in the human-readable format.
The first 10 registers are reserved for the phone number (1 register = 4 symbols) additionally you will require to put in front '+' which is equal to 00 here. If your number (together with 00) does not take 10 registers we will require you to fill out the left registers with 0 values, thats why we use the \u0000 symbol, which means 0 value.
Example Message request:
003706xxx1594\u0000\u0000\u0000\u0000\u0000\u0000\u0000test