AF100 OPC Server with Intouch
AF100 OPC Server with Intouch, Application area: Metals.
Unable to overwrite a value via SDP which is sent by the controller from the HMI (Intouch) - Intouch shows the value which was entered, but not the one on the bus/in the controller. The HMI value is overwritten imediately by the controller, but Intouch does not realize that. The value is displayed correctly after the next signal change in the controller.
AF100 OPC Server with Intouch, AF100 OPC Server 1.0 and AC110.
The first thing to do is check that you have the latest OPC link driver from Intouch - this is one of the main sources of the problem.
Also use ProcesX Explorer from Matrikon to check that your OPC Server configuration is correct. (free download from www.matrikon.com). This product is used in the example in 'Advant OPS Server for Advant Fieldbus 100 User's Guide'. We used this product to test our configuration and it was easy to use (follow the steps in the AF100 OPS Server user's guide)
One of the things that they didn't get to work is sending commands from MMI to the PLC using SDP to DAT elements. This is a serious problem when using AC70, where only DAT elements is used.
It worked fine with extended elements (AIS, DIS, ..... ect.). The only thing to remember is to block the input (AIS, DIS) before writing to it, just like in the AC400 series.
Please be aware that the AF100 OPC Server 1.1 has solved many of the problems that they had in the PLC part. (according to the new functions and fixed problems part in the release note)
Here is a list of more advise if needed:
This is a short explanation of how they configured the OPC-link and Intouch.
First you should make tagnames in the PLC program the following way, for example PLC1TAG1, PLC1TAG2.....and so on. If you have more than one Node (PLC) use PLC2TAG1, PLC2TAG2.....for the second node and so on. This will help you a lot in the configuration of the OPC-link.
When you open the ProcessX Explorer you can see the tags as follows
You are able to use PLC1, PLC2 in the beginning of the tagname so you can make a topic of each node (PLC) in the OPC link and I don't need to configure all tags in the OPC link (it's not even possible to configure more than approx.100 topics in the OPC-link). With the opc path you are able to 'cut' and make groups of your tagnames. Of course you can chose a different beginning of the tagname but 3-4 letters/numbers are good as a 'common' name for the node
So now it's time to start the OPC-link.
Go to CONFIGURE/TOPIC DEFINITION/NEW
As topic name it is smart to use the same as the opc path, in this case PLC1, opc server name should be ABB.AF100 and the opc path as they mentioned PLC1. The OPC-link will now 'cut' away PLC1 and you will be able to group the tagnames in the OPC-link
For best performance, according to the tests and configuration, only poke asynchronously should be marked of the three boxes .
Make topics for the rest of the nodes (PLC1, PLC2.....) the same way.
No other configuration is needed in the OPC-link.
Go to the configuration in Intouch, start the Window Maker
Go to SPECIAL/TAGNAME CONFIGURATION
Make a new tag and name it (in this example as TAG1)
Choose I/O REAL as type (if your tag is discrete choose I/O DISCRETE and so on)
Click on ACCESS NAME and choose ADDto make a new access name
As Access Name you are able to chose the same as Topicname in the OPC Link (in this example PLC1)
Leave Node Name empty
For Application Name write OPCLINK and for Topic Name PLC1
Suitelink or DDE doesn't really matter if you have the OPC server on the same computer. DDE is according to the manual faster but with less tagnames than 10 000 I don't think you can see any difference.
Advice: all Items should on the other hand be marked.
Back in the tagname definition box, write in the Item Name field your tagname as follows:
r stands for real value and then your tagname from the plc, after that a dot and the type you want to display (in this case the value of the tag). For discrete values just use a d in front of the tag. For a I/O Message use m.
You should now have a working 'link' up to the screen.
Start the Window Viewer and you should see the different topics in the OPC link window + status, items, errors and write status.
(OPC link should always be started manually before you start Window Viewer)
One hint if you run on to problems, always check with the ProcessX Explorer the status of the tags. If you can see a tagname in the PXExplorer the problem is always in either the OPC-link or in the Intouch configuration.
And remeber to use MMI Use Yes in the plc program.
If you don't want to reboot the computer everytime you make a change in the PLC program just go to START/ADVANT/OPC SERVER FOR AF100/PROPERTIES and DATABASE. Empty the BCD Path and press OK and go back and write in the correct path again and you should have the server running on the new program. If this dosn't work, go to Services in NT Control Panel and start and stop the OPC service.
In the Bus configuration builder (if you have the ACC 1.6) remeber to have Bus Configuration Database and Generate Boil File marked in the Generate Information for HMI box