1 / 32

Modbus to DNP3 Protocol Converter

Modbus to DNP3 Protocol Converter. Group 24: Joshua Daly, CpE Daniel Doherty, CpE Mac Lightbourn , EE Joseph Wilkinson, EE. Modbus vs. DNP3. Project motivation: MPE needs to allow for communication between network nodes that are using these different protocols. . Four-Semester Plan.

lei
Télécharger la présentation

Modbus to DNP3 Protocol Converter

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. Modbus to DNP3 Protocol Converter Group 24: Joshua Daly, CpE Daniel Doherty, CpE Mac Lightbourn , EE Joseph Wilkinson, EE

  2. Modbus vs. DNP3 Project motivation: MPE needs to allow for communication between network nodes that are using these different protocols.

  3. Four-Semester Plan Phase I Device Build User Interface Initialization Phase II Network Communications Security

  4. Key Specs • Operates between -10 and 80 degrees Celsius • Protects against surges of 120 V • MCU clock has a backup battery that can power the MCU for 12 hours if power is lost • Sends alarm to master device when power is lost • Takes Ethernet input and gives Ethernet output • Allows user to view and change networking parameters • Logs 20,000 events, even when power is lost, with 98% fidelity • Records date and time of each event to millisecond accuracy • Notifies master device of all events with 95% fidelity

  5. Four-Layer PCB Design

  6. Choosing an MCU

  7. ENC28J60 J00-0045NL

  8. Push Buttons and LEDs

  9. Firmware Overview • Menu system • Allows user to adjust stored parameters • Strict requirements from the sponsor • Creation of data Structs to maintain parameters • Initializing the device • Handle all button functionality

  10. Coding Environments • Visual Studio • Used while PCB board was in development • Familiar environment • Code Warrior • Freescale MCU • Optimization of .s19 file

  11. Data Storage • Stored in the EEPROM • Storage requirements • Factory defined • User defined

  12. Initializing the Device

  13. Buttons • Required Guidelines • Button Functionality • Menu Navigation • Time Delayed press

  14. Button Logic Flow Chart

  15. Screen • Display Screen • 3 7-segement displays • Mimic the current display used by MPE • Allows user to visually navigate and set parameters

  16. Power Subsystem

  17. Power Supply Requirements Takes in 24 V DC • This supply is shared with other components in the lift station control panel • This is a low voltage in comparison to other devices being used in industrial applications • The low voltage bypasses some of the testing requirements for meeting UL standards

  18. Power Supply Requirements Surge Protection • Must handle currents up to 80 mA • Must correct irregular voltages • Multiple devices are connected in a shunt configuration for combined benefits

  19. Power Supply Requirements

  20. Input Surge Protection

  21. Power Supply Requirements Must be fed through a DIN rail mount • All devices in the lift station control panel attach to one rail • Mount also serves as chassis ground for added surge protection

  22. DC/DC Converter • Voltage is stepped down to 3.3 V and then fed to the power plane • To conserve power, a passive switching regulator was chosen • Our configuration is a common circuit with extensive application notes

  23. Testing Why do we test?

  24. Testing • Power Up • The three 7-segment LEDs must synchronously display each number for 100 (+/- 25) milliseconds from 0-9 in ascending order within 2 seconds after power up. • The menu scroll LED must illuminate for 1 (+/- 0.1) second within 2 seconds after power up. • The value change LED must illuminate for 1 (+/- 0.1) second within 2 seconds after power up. • The power LED must illuminate within 1 second after power up.

  25. Testing • Button Scroll • When operating in menu scroll mode, the three 7-segment LEDs must display the parameter number with the following format where XX is a parameter number between 00 and 99: P.XX. • The displayed parameter list must circle to the beginning of the list when cycled up at d.06 • The displayed parameter list must circle to the end of the list when cycled down at E.01

  26. Testing • Sleep/Wake • The user interface LEDs must not remain illuminated if all user interface inputs are inactive for 120 (+/- 2) seconds. • When in a state of inactivity, the unit must transition to a state of activity • The state of user action must be preserved when the user interface LEDs are extinguished due to inactivity. • The state of user action must be reinstated when the unit returns from an inactive state.

  27. Challenges • How does it all work • Hardware challenges • Firmware challenges

  28. Financials

  29. Questions

More Related