1 / 12

Monitoring infrastructure

Monitoring infrastructure. A case study. Graphical monitoring application (web browser). Datalog analysis (through web browser). f lot – javascript plotting library for jQuery Select up-to 8 variables fro plotting Select variables to be logged in a RD

jessie
Download Presentation

Monitoring infrastructure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Monitoring infrastructure A case study

  2. Graphical monitoring application (web browser)

  3. Datalog analysis(through web browser)

  4. flot – javascript plotting library for jQuery • Select up-to 8 variables fro plotting • Select variables to be logged in a RD • Scanning period – multiples of 5 seconds

  5. Technology monitoring schema 496 binary signals 500 analog signals 16 bits Up to 500 integer signals 16 bits PLC PLC PLC Modbus RTU (slave) 19920 bits/sec 1 start bit, 8 data bits, 1parity bit (even), 1 stop bit RS-485 bus unitId=2 unitId=3 unitId=1 UNIX (uUnix) SSH client/server Modbus master SSL client/server Programmableconvertor(freescale microprocessor) Ethernet, TCP/IP

  6. Monitoring technology • PLC • Programmable Modbus RTU / Ethernet convertor

  7. The convertor inside SSH client Modbus RTU master Modbus TCP slave SSH server RS-485 Ethernet DHCP client Serial port TCP/IP interface SSL client NTP client SSL server

  8. Problem definition I Convertor Web browser Convertor ??? On-line monitoring Convertor Web browser Data log analysis cca 1800 pieces Web browser Convertor Diagnostics

  9. Problem definition II • The convertor must not require a fixed IP address • The data transmission must be secured (e.g. a SSL tunnel) • Data is logged in parallel with monitoring • Obsolete data is deleted (history depth is configurable) • Connection recovery (e.g. forced convertor reboot to recover the correct functionality) • Remote firmware upgrade/downgrade • Remote convertor re-configuration • => convertor controlled through kind of control channel? • Possible extension to another protocol than Modbus

More Related