Loss of Data in DNP3 Networks

Sdílet
Vložit
  • čas přidán 9. 10. 2021
  • DNP3-based networks can be very powerful in managing an industrial network, with its timestamping, messaging, and historic archiving features being highly configurable to suit specific requirements. However, if configured improperly, valuable data can be lost.
    In this video, we show how data can be lost in a DNP3-based industrial network, its' impact to operations, and three areas that you can investigate to resolve such issues.
    If you have any questions, Contact us any time via this link
    www.acectrl.com/contact-us/
    or simply leave a comment in the comment section below!
    ✨ And if you like this video, consider subscribing to Australian Control Engineering using this Link! ⤵️
    / @acectrl
    Thanks for watching!
    ********************
    🎬 Welcome to the CZcams Channel of Australian Control Engineering 🇦🇺
    On this Channel, we promote knowledge sharing on IIOT, Telemetry, SCADA, Automation, data analytics, and more 🔝
    ➡️ Australian Control Engineering delivers the best Instrument, Electricals, and Automation technology focused on the utility SCADA, IIOT, and control systems environment.
    Starting from an initiative to fill a gap in the IT/OT, Communications, and manufacturing technology
    space in Australia, ACE has grown organically over the past years by recruiting engineers with Australian Control Engineering an entrepreneurial mindset, thinking outside the box to deliver the best possible solutions for our customers ✅
    Our team of experts provides innovative solutions to improve efficiency and lower risks for niche industries in Australia, delivered within an ISO 9001:2015 quality framework 🌏
    ➡️ If you are SCADA, Control System and Communication enthusiast, Cloud computer geeks, 5G fanatics, and technology investors with a mindset of entrepreneurship, who have an aspiration to be a part of technology ventures you should subscribe to the Channel and be enlightened!
    💯
    ********************
    ✨ Connect with Australian Control Engineering on Social Media:
    Facebook ➡️ AustralianCo...
    Instagram ➡️ / ace_ctrl
    LinkedIn ➡️ / acectrl
    Twitter ➡️ / acectrl
    Pinterest ➡️ / acectrl
    🖥 And don’t forget to check out our Website!
    www.acectrl.com/
    ********************
    #DNP3 #IndustrialNetworks #SCADA
  • Věda a technologie

Komentáře • 2

  • @stevebjee
    @stevebjee Před měsícem +1

    Seems like the SCADA server should be checking the timestamps of the events and alerting if event(s) are in the past (outside an acceptable window) and not writing the erroneous data to the historical database. Simply store them to some anomaly event log and not corrupt the historical database data.

    • @acectrl
      @acectrl  Před měsícem

      You've raised a good point. The historic data is one of the DNP3 feature as an industrial communication protocol. It mitigates the risk of comms failure by storing events in the outstation controller and upload the event data the SCADA server (DNP master). Depending on the server software, for example, GeoSCADA (ClearSCADA) can be configured to ignore the historic events passed a certain period. However, most of the application servers are configured to accept the events to avoid loss of data. We share another video with you: czcams.com/video/SmRI4H1LqsQ/video.html