How to Write on harmony opc server 7.0
I installed Harmony opc server version 7.o.
I want write to block Remset and Analog from harmony OPC server but I cannot write the value on SPC700.
Anybody can help me how to solve the problem
I want write to block Remset and Analog from harmony OPC server but I cannot write the value on SPC700.
Anybody can help me how to solve the problem
Asked 6 months ago
Answers
1
Hi,
Is the problem with creating tags or connecting an OPC client to the OPC server? If everything appears ok otherwise. I.E. Reads work OK and the logs don't indicate a major problem.
The OPC server configuration (general tab) has an option to globally disable command writes. Ensure this is unchecked.
Every HOPC tag with writable atoms has a Command Write Disable checkbox available in the HOPC tag edit dialogue. If this is checked, command writes will not be allowed for the tag.
HOPC Analog tags have no writable atoms (tuning aside), as all analog tag atoms originate from the function code. If you want to write to an analog maybe use an AnalogEx HOPC tag to export the analog value from the HOPC ICI and then add logic (FC121) to the controller to import the AnalogEx value. The FC121 can then be connected to the AO/L. If you have redundant HOPC you will need to import the AnalogEx value into a controller and use logic to select the value to connect to the AOL. If the AnalogEx is non-redundant and just for a HMI, maybe just point the HMI tags to the AnalogEx block address.
The HOPC RMSC/REMSET .PV/SIG atom can be written to if Command writes are enabled and the /TRACKING atom is off in the function code, again controlled by the controller configuration. Note that writing to the REMSET is not really suitable for transferring data that changes regularly, it is more for operator entered values. Every write to a REMSET adds a load to the checkpointing between primary and backup controllers, for Harmony Rack controllers at least. The BRC controllers have a limit of 80 per second before generating NVRAM Overrun alarms but I don't know how this translates to the SPC/HC controllers.
Cheers,
Alan
Is the problem with creating tags or connecting an OPC client to the OPC server? If everything appears ok otherwise. I.E. Reads work OK and the logs don't indicate a major problem.
The OPC server configuration (general tab) has an option to globally disable command writes. Ensure this is unchecked.
Every HOPC tag with writable atoms has a Command Write Disable checkbox available in the HOPC tag edit dialogue. If this is checked, command writes will not be allowed for the tag.
HOPC Analog tags have no writable atoms (tuning aside), as all analog tag atoms originate from the function code. If you want to write to an analog maybe use an AnalogEx HOPC tag to export the analog value from the HOPC ICI and then add logic (FC121) to the controller to import the AnalogEx value. The FC121 can then be connected to the AO/L. If you have redundant HOPC you will need to import the AnalogEx value into a controller and use logic to select the value to connect to the AOL. If the AnalogEx is non-redundant and just for a HMI, maybe just point the HMI tags to the AnalogEx block address.
The HOPC RMSC/REMSET .PV/SIG atom can be written to if Command writes are enabled and the /TRACKING atom is off in the function code, again controlled by the controller configuration. Note that writing to the REMSET is not really suitable for transferring data that changes regularly, it is more for operator entered values. Every write to a REMSET adds a load to the checkpointing between primary and backup controllers, for Harmony Rack controllers at least. The BRC controllers have a limit of 80 per second before generating NVRAM Overrun alarms but I don't know how this translates to the SPC/HC controllers.
Cheers,
Alan
Answered 6 months ago
Source: 2VAA008521-7*
Add new comment