YuDash
  • Welcome
  • YuDash IoT Devices
    • LYNX User Manual
      • Terminals and Wiring
      • LYNX Configuration
      • Network Settings
      • LYNX Settings
        • Modbus RS485
        • Analog Inputs
        • Data Scaling
        • Advance Feature Settings
        • Cloud and Payload Settings
        • Ethernet Settings
        • Modbus TCP/IP
        • HTML Parser Settings
        • Digital Sensors Settings
    • ZENYX User Manual
      • Terminals and Wiring
      • ZENYX Configuration
      • Network Settings
      • ZENYX Settings
        • Modbus RS485
        • Analog Inputs
        • Data Scaling
        • Advance Feature Settings
        • Cloud and Payload Settings
        • Ethernet Settings
        • Modbus TCP/IP
    • QUBIX User Manual
    • ONYX User Manual
  • Device Configuration
    • Device Configuration
    • Device Features
      • Network
      • Modbus/RS485
        • Modbus Poll Tutorial
      • Modbus TCP/IP
      • Modbus Server
        • Analog to Modbus/RS485 Server (Slave)
        • Analog to Modbus/TCP-IP Server
      • Ethernet
      • Data Logging
  • Firmware
    • Firmware release notes
    • Firmware upgrade
  • YuDash JSON API
    • Modbus Settings
    • Analog Settings
    • Data Scale Settings
  • DEVICE TO CLOUD API
    • YuDash IIoT Stack
    • Cloud Protocols
      • MQTT
      • HTTP
      • FTP
      • SSL/TLS
    • Payload Formats
      • JSON Payloads
      • YuTGT: YuDash Text Generator
    • Network Connectivity
    • Industrial Protocols
      • Modbus
  • YuDash IoT Platform
    • YuReCon
  • Integration Guides
    • IoT Platform Integration
      • Ubidots
      • TagoIO
      • Losant
      • Datacake
      • Eagle.io
      • Boodskap
      • Statstream
      • Qubitro
      • Thingsboard
    • Industrial Instruments
      • Energy
        • SE EM6400NG+
        • Selec MFM376
        • L&T WL 4040
        • Entes MPR-46S
        • Selec EM4M
        • Secure Elite 100
        • Siemens Smart 7KT
        • Selec EM2M
      • Process Control
        • Selec FLEX2MV3 6AII
        • Selec MiBRX 2M PLC
        • Temp+Humidity XY-MD02
        • PPI AIMS 4/8X
    • Environment/Emission
      • Air & Water
      • Weather
    • Industrial PLCs
  • Use Cases
    • Environment
      • Ground Water Compliance
      • Continuous Emission Monitoring System (CEMS)
    • Smart Building
      • IoT based Building Monitoring Solution
      • Tenant Energy Sub-metering and Billing System
    • Asset Management
      • Centralized Monitoring System for Gas Plant OEM
Powered by GitBook
On this page
  1. YuDash IoT Devices
  2. LYNX User Manual
  3. LYNX Settings

Modbus TCP/IP

PreviousEthernet SettingsNextHTML Parser Settings

Last updated 1 month ago

YuDash LYNX supports Modbus TCP/IP to read various PLC/HMIs through ethernet. In principle, following are the pre-requesites for using Modbus TCP/IP:

  1. Valid Ethernet settings of YuDash LYNX for communication over TCP/IP.

  2. LYNX is Modbus Client, who request the data. The given PLC is Modbus server, who will provide the data. LYNX can read multiple Modbus TCP/IP servers.

  3. Following details of a given Modbus Server (PLC) are required for communication:

  • IP address of PLC. For example: 192.168.1.100

  • IP Port on which Modbus server is running. For example: 502 (standard port). Or 8888 (any port being used by PLC)

  • Modbus Server ID as per protocol. For example: 1 (The Server ID of Modbus is similar to slave ID of Modbus RS-485)

  • Modbus Registers and Data Types The mapping of registers and selection procedure is similar to Modbus RS-485

There are different network topology possible for interfacing PLC/HMI with LYNX using Modbus TCP/IP. For example:

A) Peer to Peer Direct Connection

B) Through Ethernet Switch

C) Through LAN Router with Static IP

D) Through LAN Router with Dynamic IP

All the scenarios of Modbus TCP/IP are covered in the video below.