Teltonika Networks Wiki

Changes

Template:Networking rut manual modbus (view source)

Revision as of 09:51, 2 April 2019

5,917 bytes added ,  09:51, 2 April 2019
no edit summary
Line 48: Line 48:     
[[File:{{{file_add_new_slave}}}]]
 
[[File:{{{file_add_new_slave}}}]]
 +
 +
<ul>
 +
    <li><b>Alarms</b> - Redirects you to the slave's alarm configuration page (more information in [[{{{name}}} Modbus#Alarm_configuration|section 3.3)</li>
 +
    <li><b>Clone</b> - Creates an identical slave configuration</li>
 +
</ul>
 +
<table class="nd-othertables_2">
 +
    <tr>
 +
        <th>Button</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Alarms</td>
 +
        <td>Redirects you to the slave's alarm configuration page (more information in [[{{{name}}} Modbus#Alarm_configuration|section 3.3)</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Clone</td>
 +
        <td>Creates an identical slave configuration</td>
 +
    </tr>
 +
</table>
    
===Slave device configuration===
 
===Slave device configuration===
Line 156: Line 175:  
         <td>- (interactive button)</td>
 
         <td>- (interactive button)</td>
 
         <td>Adds a new request request</td>
 
         <td>Adds a new request request</td>
 +
    </tr>
 +
</table>
 +
 +
===Alarm configuration===
 +
----
 +
<b>Alarms</b> are way of
 +
 +
[[File:{{{file_alarms}}}]]
 +
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field name</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Enabled</td>
 +
        <td>yes | no; Default: <b>no</b></td>
 +
        <td>Turns the alarm ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Function code</td>
 +
        <td>Read Coil Status (1) | Read Input Status (2) | Read Holding Registers (3) | Read Input Registers (4); Default: <b>Read Coil Status (1)</b></td>
 +
        <td></td>
 +
    </tr>
 +
    <tr>
 +
        <td>Register</td>
 +
        <td>integer [0..65535]; Default: <b>none</b></td>
 +
        <td></td>
 +
    </tr>
 +
    <tr>
 +
        <td>Condition</td>
 +
        <td>More than | Less than | Equal to | Not Equal to; Default: <b>Equal to</b></td>
 +
        <td></td>
 +
    </tr>
 +
    <tr>
 +
        <td>Value</td>
 +
        <td>various; Default: <b>none</b></td>
 +
        <td></td>
 +
    </tr>
 +
    <tr>
 +
        <td>Action</td>
 +
        <td>SMS | Trigger output | Modbus Request; Default: <b>SMS</b></td>
 +
        <td></td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: #0054a6;">SMS: Message</span></td>
 +
        <td>string; Default: <b>none</b></td>
 +
        <td>SMS message text</td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: #0054a6;">SMS: Phone number</span></td>
 +
        <td>phone number; Default: <b>none</b></td>
 +
        <td>recipient's phone number</td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: red;">Trigger output: Output</span></td>
 +
        <td>Open collector output | Relay output | Both; Default: <b>Open collector output</b></td>
 +
        <td>Which output will be triggered</td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: red;">Trigger output: I/O Action</span></td>
 +
        <td>Turn On | Turn Off | Invert; Default: <b>Turn On</b></td>
 +
        <td>Action that will taken on the specified output</td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: purple;">Modbus Request: IP address</span></td>
 +
        <td>ip | host; Default: <b>none</b></td>
 +
        <td>Modbus slave's address</td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: purple;">Modbus Request: Port</span></td>
 +
        <td>integer [0..65535]; Default: <b>none</b></td>
 +
        <td>Modbus slave's port</td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: purple;">Modbus Request: Timeout</span></td>
 +
        <td>integer [1..30]; Default: <b>5</b></td>
 +
        <td>Maximum time to wait for a response</td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: purple;">Modbus Request: ID</span></td>
 +
        <td>integer [1..255]; Default: <b>none</b></td>
 +
        <td>Modbus slave ID</td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: purple;">Modbus Request: Modbus function</span></td>
 +
        <td>Read Coil Status (1) | Read Input Status (2) | Read Holding Registers (3) | Read Input Registers (4) | Force Single Coil (5) | Preset Single Register (6) | Force Multiple Coils (15) | Force Multiple Registers (16); Default: <b>Force Single Coil (5)</b></td>
 +
        <td></td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: purple;">Modbus Request: First register</span></td>
 +
        <td>integer [0..65535]; Default: <b>none</b></td>
 +
        <td>Begins reading from the register specified in this field</td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: purple;">Modbus Request: Number of registers</span></td>
 +
        <td>integer [0..65535]; Default: <b>none</b></td>
 +
        <td></td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
Line 161: Line 279:  
==Modbus Data to Server==
 
==Modbus Data to Server==
   −
A Modbus <b>master</b> device can request data from Modbus slaves. The Modbus TCP Master section is used to configure Modbus TCP slaves. To add a new slave, enter a custom name, slave's ID, IP address and port and click the "Add" button:
+
The Modbus <b>Data to Server</b> function provides you with the possibility to set up senders that transfer data collected from Modbus slaves to remote servers. To add a new data sender, enter the server's address, specify the data sending period and click the "Add" button:
    
[[File:{{{file_add_new_sender}}}]]
 
[[File:{{{file_add_new_sender}}}]]
 +
 +
===Data sender configuration===
 +
----
 +
When you add a new data sender, you will redirected to its configuration window. The figure below is an example of that window and the table below provides information on the fields that it contains:
    
[[File:{{{file_sender_configuration}}}]]
 
[[File:{{{file_sender_configuration}}}]]
 +
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Enabled</th>
 +
        <th>yes | no; Default: <b>no</b></th>
 +
        <th>Turns the data sender ON or OFF</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Name</td>
 +
        <td>string; Default: <b>none</b></td>
 +
        <td>Data sender's name. used for easier management purposes</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Protocol</td>
 +
        <td>HTTP(S); Default: <b>HTTP(S)</b></td>
 +
        <td>Data sending protocol</td>
 +
    </tr>
 +
    <tr>
 +
        <td>JSON format</td>
 +
        <td>string; Default: <b>{"ID":"%i", "TS":"%t","ST":"%s","VR":"%a"}</b></td>
 +
        <td></td>
 +
    </tr>
 +
    <tr>
 +
        <td>Segment count</td>
 +
        <td>1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10; Default: <b>1</b></td>
 +
        <td></td>
 +
    </tr>
 +
    <tr>
 +
        <td>URL</td>
 +
        <td>host | ip; Default: <b>none</b></td>
 +
        <td>Address of the server to which the data will be sent</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Period</td>
 +
        <td>integer [1..6400]; Default: <b>none</b></td>
 +
        <td>Data sending frequency (in seconds)</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Data filtering</td>
 +
        <td>All data | By slave ID | By slave IP; Default: <b>All data</b></td>
 +
        <td></td>
 +
    </tr>
 +
    <tr>
 +
        <td>Retry on fail</td>
 +
        <td>yes | no; Default: <b>no</b></td>
 +
        <td>Specifies whether the data sender should retry failed attempts</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Custom header</td>
 +
        <td>string; Default: <b>no</b></td>
 +
        <td></td>
 +
    </tr>
 +
</table>
    
==See also==
 
==See also==
Retrieved from "https://wiki.teltonika-networks.com/view/Special:MobileDiff/31592"