Recommended
More Related Content
Featured
Featured (20)
Disturbance Monitoring Equipment Presentation
- 1. Disturbance Monitoring Equipment Record Downloading and DFR/SER Management Prepared by Rohit Das
- 3. Record Tracking Sheet File can be found at: K:DFR15 Records
- 4. Remote Connecting to the Download Computers
- 7. PSDR Tesla
- 8. Wavewin DFR Record Analysis Latest Version is Wavewin GC
- 11. DFR Triggering Tests NMS Live Values Triggered Record
- 12. PCMIS
Editor's Notes
- -introduce self -how records downloaded -where stored and how they are read -DFR/SER maintenance
- -first analyze IOIs i.e the automatic outages and the forced outages -all faults except feeders -elements recorded for stations with DFRs/SERs only, after practice easy to memorize stations with DME -lines -> NODS and operating diagram analyzed to see if any other stations on that line have any DFRs that could have triggered the record -sometimes indicated sometimes not
- -file titled 2015 Daily Downloading contains sheets of reported faults for every month and summary sheets with all DFR and SER general information and other information updated during maintenance -columns: fault date accurate to the millisecond, the element(s) associated with fault, the voltages of the elements, the station, the DFR manufacturer, the status of the record, the same for the SERs, then comment sections which are filled after DFR and SER records are analyzed
- -actual downloading software exists on computers in the downloading room -the remote desktop application is available on all of the computers used to connect to the computers to connect to the various DFRs and SERs, the computers can be remotely accessed by anyone so long as they know the name of the computer they wish to access and know the user name and associated password -the password may vary since they need to be changed routinely, however the DME manual does include the names of the computers and the username
- -115 active DFRs are accessed through the Mehta Tech and Qualitrol software called polycomm and replay plus respectively -the primary difference between various station DFRs is that some of the stations are accessed through a LAN connection while most of them are accessed through a phone connection -autopolling feature enabled for Mehta Tech currently only -the DFR records must be analyzed using Wavewin
- -Automatec and Harris collector programs are used to connect to all 46 SERs, for other stations RTUs may perform SER function and is indicated in the TOF files -for new RTUs going into service if the TOF indicates that SER function is performed a link device is created on PCMIS to point to the TOF device under the SER bucket -SER records are text based and sample the timestamped points triggered during a fault, can be opened by notepad/wordpad (text editors) -SER connections are poor, downloading is fast once connected
- -PSDR records are still downloaded upon request, routinely checked to make sure that there is adequate memory for the latest records, the records can be opened by the same software used to connect and download -records indicate frequency data
- -after downloading I use wavewin to analyze the records indicated by the IOI reports -things checked for: existence of record, record isn't glitched, desired element data is present -fault details are noted in the comment section of Daily Downloading spreadsheet, details include type of fault and duration of fault -wavewin software analog channel feature help document is being created -document entails operators/syntax used, examples, and contains definitions and formulas for relevant power theory concepts -copy of the document will be available in NOEA drive DFR15 folder
- -the SER triggered records show a chronological list of events and for these records I simply check to see that the records are not corrupt and that the elements in question have had the appropriate operations recorded at the stated time -For example if a fault was stated to occur on a line I would check the SER record to see if the line protection operation was indicated etc
- -the procedure for troubleshooting and maintenance was developed over time -all DFRs are connected to and checked one week and the SER testing is done the following week -DFR check: successful connection, if the station recording time corresponds to the clock on the computer in the downloading room, to see if there were any outstanding records that have not been downloaded by the autopoll feature and confirm successful downloading, and to see if there is sufficient memory space of at least 100 MB per DFR to be prepared for the case where multiple records are triggered in rapid succession -SER Check: I am just checking to see that a successful connection can be established since records are automatically downloaded once connected to a device -any issues are noted and basic troubleshooting is performed from our end, any unresolved issues are informed to Florian so he can decide if a DR is necessary -SAP is also checked to verify existing or missing DRs
- -new process to test accuracy of DFRs to ensure records are reliable -records are manually triggered from a DFR and data from the triggered record is cross referenced with values listed on NMS to measure accuracy of DFR readings and to identify possible issues with CT/PT ratios -phase current values are used to perform test -data values and the percentages in error are noted and all information is included in a sheet titled triggering test in the daily downloading spreadsheet -this procedure will be updated in the DME manual so future students can perform this test with a few stations every month -any test that yields significant percentages of error will be double checked and DFR settings may be reviewed
- -lastly I just wanted to remind everyone that if there are any requests for setting files or triggering configurations or SER points and the downloader is absent or is unable to retrieve the desired files immediately all active DME equipment is currently on PCMIS and the files listed on PCMIS reflect the latest settings -any changes made to settings are reflected on PCMIS immediately