Output transfer tag doesn't work
Dear experts, in our powe plant we have following configuration for ONET:
-two main servers, named 10OS11 and 10OS12 which have communication to HPC800 controllers
-two interfaces servers named 10IS01 and 10IS02 for communication with other systems over Modbus RTU/TCP, IEC101,IEC104
Some values should be sent from process so we are sending data from 10OS11/12 to 10IS01/02. That part works normal. Problem is that when value of tag from process needs to be copied into another tag which is configured to be sent over communication it doesn't work. This is happening on 10IS02, while working normally on 10ISO1. I checked setting in System Setup under Apps and everything looks ok.
-two main servers, named 10OS11 and 10OS12 which have communication to HPC800 controllers
-two interfaces servers named 10IS01 and 10IS02 for communication with other systems over Modbus RTU/TCP, IEC101,IEC104
Some values should be sent from process so we are sending data from 10OS11/12 to 10IS01/02. That part works normal. Problem is that when value of tag from process needs to be copied into another tag which is configured to be sent over communication it doesn't work. This is happening on 10IS02, while working normally on 10ISO1. I checked setting in System Setup under Apps and everything looks ok.
Answers
How is your otxprc system setup configured? What S+O version are you running? Are you using extended redundancy? Is output transfer is working fine on one of the redundant servers, but not on the other server? If using extended redundancy is may be that you have to set OutputOnlyIfMaster=No. There was an bug in previous versions of S+O, problem was that extended redundancy master and otx master could be on different servers, setting OutputOnlyIfMaster=No should fix that. (could also be that this it is fixed in newer versions of S+O, have not checked) Have you also looked into this existing forum question? https://forum-controlsystems.abb.com/...
Ba also aware of that there is limits on how many signals that should be sent using OTX(check your S+O version release notes)
Ba also aware of that there is limits on how many signals that should be sent using OTX(check your S+O version release notes)
The details remain same as explained in similar question earlier by me. Link provided below:
https://forum-controlsystems.abb.com/...
Version detail: Unknown.
Reference: Operations Engineering guide
In addition to that, refer to the release notes, regarding the allowed range of signals with specific time span.
https://forum-controlsystems.abb.com/...
Version detail: Unknown.
Reference: Operations Engineering guide
In addition to that, refer to the release notes, regarding the allowed range of signals with specific time span.
Source: Operations Engineering guide
Add new comment