Diagnostics shows the integrity of every IO point, whether good or bad. One can drill down to the DST and see a status parameter that indicates what is the error. Is there a way to export this information or generate a report for all IO or only bad IO?
The short answer is no. DeltaV reports impactful conditions through the Hardware Alerts of each node, with additional runtime status conditions reported through overall integrity that bubbles up to the Node level in both Diagnostics and Explorer. Signal integrity reports into the modules that use the signals which would report in the module as configured by the module (i.e PV Bad alarm etc). The IO Status field mentioned here holds the most relevant status condition for the channel and must be referenced somehow to be seen. Diagnostic Explorer provides a built in tool to view the status and other conditions of any channel, but there is no database view where this information is collected and stored.
The Event Chronicle will contain IO related status conditions as reported by Control Modules that use these signals. A Bad status, such as Open Loop Detected would not be seen if the channel is not referenced by a module. But then, there is no control issue to report if the signal is not used by a control module.
Diagnostic Explorer has a few additional features that may help.
1. The Integrity History can be saved
The integrity History walks the DeltaV hardware tree and reports items that have a bad Integrity, including nodes, IO channels, Ethernet Ports etc.
This gives you a list of all the channels with a path to go and gather more detailed in formation.
By opening Diagnostic Explorer, and letting it complete its pass, you get a list of all items with BAD integrity reported. Notice that "PW2-CIOC1/CAHMS/CHM1-08" is also shown under the controller it is assigned to as "PO_BOP/REMIO/PW2-CIOC1/CHM1-08"
Below is the text export of the history, with the CHARM 1-08 highlighted in both the Controller and the CIOC nodes.
The CIOC Node;s channel path of PW2-CIOC1/CHARMS/CHM1-08 can be appended with the field "/STATUS" and you can read the diagnostic value in question:
However, the Controller reference as shown in the History file does not work as written. The CIOC name must be replaced with the CIOC's NODE ID
PO_BOP/REMIO/306446346/CHM1-08/STATUS. My point is use the CIOC based IO reference and avoid the need to know the Node ID number.
Where am I going with this? If you used Excel, you could parse pass the Integrity History to an Excel Sheet, parse out all the IO channel paths and append /STATUS to them and read the current status of all BAD IO. If they are not BAD, they are GOOD.
On my system, I had 8 BAD CHARMS. The other items were EIOC LDT related. Which I could also get the /STATUS of those.
2. The other feature of Diagnostic Explorer is the Find Nex Fault:
;This quickly walks you through the hardware tree with Ctrl+F to quickly see what BAD status you have, instead of tracing the yellow question marks through the folders of the tree.
The Save Integrity History provides a source of information for a report. Via Excel and the Excell AddIn, you can extract additional details on the items listed.
This does require an interactive session with DeltaV Diagnostic Explorer to generate the integrity History, or to view faults interactively. But you save yourself creating some sort of report or display that would have to explicitely read every IO channel to gather their status detail. This approach reduces the load to just the channels that are bad, and provides you with some statistics for your reports.
Andre Dicaire