![]() There is no technical issues preventing us doing this - it all comes down to resources and prioritization, thus I'd recommend contacting Dave to put in a vote for enhancing the Kingfisher driver. Thus to utilize this approach you would need to put the RTU into DNP3 mode.Īlternately you could contact David Sorkovsky, the Product Manager responsible for drivers and request that the Kingfisher driver be updated to use the new interfaces. This does not rely on any tag naming conventions - it actually parses the runtime databases and matches up the alarm / trend configuration.Īt the moment the main drivers being released with v7.20 that support these new interfaces are DNP3 and OPC. OPC DA Servers will not have a cluster name. You don't need to run any cicode and all events are automatically back-filled into time-stamp digital alarms, time-stamped analog alarms and event trends and it all supports full redundancy switchovers etc. Citect runtime was searching for the setting to be configured with a cluster name of blank, which is incorrect. It can be a plain display client, which only requires data for displaying graphic pages, or occasionally alarm or trend pages. ![]() In v7.20 with drivers that support some of the new interface we have created you only need to create a single tag for each RTU point and all the quality and timestamp information will flow strait through. While this might not be any 'easy' option I would consider using DNP3 to communicate with the RTU with v7.20. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |