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
  • 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
  • A) Sample Communication of Instrument with Laptop
  • B) Integration of YuDash LYNX with the instrument
  • C) Enabling HTML Parser Settings in LYNX
  • D) HTML Parser Settings
  1. YuDash IoT Devices
  2. LYNX User Manual
  3. LYNX Settings

HTML Parser Settings

PreviousModbus TCP/IPNextDigital Sensors Settings

Last updated 1 year ago

There are many legacy instruments or systems which does not support standard industrial protocols like Modbus/Analog outputs. In many cases, there is a HTTP/web server running in the instrument, which can be accessed over Ethernet LAN. Historically, the instruments were connected to PC/laptop directly to PC (or in local LAN). The web pages were manually read by users and the current readings were manually recorded in registers or ERP.

YuDash LYNX supports advanced HTML parsing for IoT enabling of legacy instruments. The feature is explained using a representative instrument with in-built web server.

A) Sample Communication of Instrument with Laptop

A representative instrument within inbuilt HTTP server is connected to laptop through Ethernet cable. The target HTML page (API) will open in the web browser. Please refer to instrument TCP/IP settings and documentation to reach to this point. Typically, the HTTP/web servers are running on IP port 80 and default page of index.html.

B) Integration of YuDash LYNX with the instrument

The HTML file of instrument will be processed by LYNX to extract applicable tags from HTML tables. The fetched data points will be treated similar to any Modbus/Analog values in rest of flow.

C) Enabling HTML Parser Settings in LYNX

D) HTML Parser Settings

3) The Server settings of the instrument has to be filled within Read HTML Settings block. Click on Read HTML Settings to get present settings. Click on Update HTML Settings after updating settings of Server IP and API (as per below image).

4) The HTML tags have to be configured as per HTML page of the instrument. The Tag Name is the tag within HTML table, the value of which has to captured.

The value is assigned to Variable Name, which will be used in the LYNX data flow.

Besides default HTML parsing in this tutorial, YuDash LYNX supports advanced HTML parsing features. It includes capturing any HTML tags/tables based on the web page. It is done by configuring custom Prefix and Suffix tags for Keys and Values. Please contact us as sales@yudash.com for more help.

The laptop is now replaced with YuDash LYNX with similar topology. LYNX work as HTTP client (similar to web browser). Direct peer-to-peer connection is shown below. In practice, it can be connected to instrument (or a server/PC/SCADA) over various topologies, as explained in section.

1) Within , Ethernet/LAN and HTML parser is enabled.

2) The has to configured as per selected topology. In this example, Static IP settings are being used.

Modbus TCP/IP
Ethernet Settings
613B
html_snippet.json
Sample HTML parsing block to be used in lynx.json configuration
Feature Settings