NI OPC server communication with B&R plc

hi,
I have a NI OPC server in my lab . I want to send the data from B&R plc to the OPC server. I have tried to search for a solution but could not find any.
Kindly help me in establisihng a communication between the B&R plc and the OPC server.
Regards

Did you try installing the B&R PLC OPC server on a computer and then see if the NI OPC server can connect to it? It might not be the most elegant soloution, but it might work.
We were having problems with some siemens wincc software that would not connect to the Think&Do OPC server. So I had to bring the Think&Do OPC tags into LabVIEW and then have LabVIEW broadcast the data so the Semens OPC software could see it. I did not like doing it, but it worked.
Other than that, maybe someone else will have more to offer.

Similar Messages

Tag engine to opc server communication protocol

When the tag engine talks direct to a plc with modbus rtu, there is a CRC checksum built into the communication protocol to provide reliable data transfer. When the tag engine talks directly to an opc server program, what protocol is used?? Is there any kind of checksum to verify data integrity??

OPC Client to OPC Server communication protocol is based on Microsofts DCOM architecture, which is an object model oriented communication mechanism based on RPC (TCP/IP). I as know, there is no checksum verification specifically as known in PLC protocols. However, there are some mechanism to support fault tolerance better. (see DCOM Technical Overview, section, Fault Tolerance)
You could find more info from Microsofts MSDN library e.g. Serach from MS MSDN Library on "DCOM", or DCOM Overview.
The OPC specification could be downloaded from the ion.org>OPC Foundation, specifically you could find a white paper on OPC, DCOM and Security as pdf file.
Hope this helps
Roland
PS: If someone needs more info on Modbus specification you might find it on Modbus.org

OPC Server Issues with Lookout 6.1

Hello All,
I have an application, using Lookout V 6.1. I have copied the files from a Lookout V 6.0 application that all ready works. The Lookout package is communicating using the Helmholz Step 5/Step 7 OPC Server to a Siemens S7-414H processors (a redundant system).
The previous application worked fine, but it was done by another engineer who is no longer with our company. The new application, I keep getting the following message:
"PC/OLE error (1): Configuring OPC server (10): The item ID is not defined in the server address space or no longer exists in the server address space. (C0040007): Item (PRO1.HMI.PCV_PB_CLOSE_12)."
I have checked this item out using the Helmholz OPC Test Client, the tag does exist inside the PLC and the OPC Test Client can read the data just fine, however Lookout does not appear to be communicating with the OPC server.
Any help would be greatly appreciated. Like I said, I can get the OPC Test Client to communicate, but not the Lookout project.
Thanks for the help.
Best Regards,
John Blaser
Design Engineer
Mcaps Inc.
[email protected]

Have a look at the OPCClient object, as well as some expressions on the panel in the previous application. Did the previous application use any customized Access Path for the items like the attachments?
Also try "Flat", instead of "Hierachical" for browsing option. After you change to Flat, refresh the object in Object Explorer.
Message Edited by Ryan.S on 05-27-2007 10:21 PM
Ryan Shi
National Instruments
Attachments:
untitled2.JPG ‏7 KB
untitled1.JPG ‏45 KB

OPC server error with Lookout 5.1 that was working with Lookout 4.5

I was running a file on Lookout 4.5 with Field Point explorer 3.0 with field point objects. I recently upgraded the Lookout to 5.1 and Field Point Explorer was uninstalled. Now when I try to open my old Lookout file, I cannot control through the field point objects and I am getting the following error: OPC/OLE error. OPC server not registered properly (63). Invalid class string 800401F3.

Hello,
Thanks for contacting National Instruments. There are three known reasons that you may get this error.
1. IAK file not setup or it has been moved or is missing.
This error is easy to reproduce. In order for the OPC FieldPoint Server to work, it has to launch the FieldPointOPC2.exe which has looks at a registry key for FieldPoint Explorer. In this registry key is the path to the last saved or loaded IAK file. If this file has moved or has been deleted, then you will get this error. This also happens to customers that have upgraded their FP Explorer and haven't opened up their IAK file and saved it.
2. OPCproxy is not registered. Which means the opcproxy.dll or opccomn_ps.dll are not registered or are version 1.0 (can be registered by running "regsvr32 opcprox
y.dll" and "regsvr32 opccomn_ps.dll". The opcproxy.dll and the opccomn_ps.dll are located in the system32 folder in the WINNT directory.
3.OPCserver is not registered (can be accomplished by running the .exe with a /regserver switch) . The Fieldpoint OPC server is located in the following path: [drive letter]:\Program Files\National Instruments\FieldPoint. From a DOS prompt you can manually register the EXE by going to that directory and typing FieldPointOPC2.exe /RegServer. In a dos prompt the command line looks like this (also see attached picture):
c:\cd c:\Program Files\National Instruments\FieldPoint
c:\Program Files\National Instruments\FieldPoint\FieldPointOPC2.exe /RegServer
Hope this works. If it doesn't, then I suggest that you uninstall all NI software and try to do a fresh install. This will properly ensure that all the services and servers are registered.
A Saha
Applications Engineer
National Instruments
Anu Saha
Academic Product Marketing Engineer
National Instruments

Modbus communication with Modicon premium PLC

Is it possible to communicate modicon premium plc(P574634M) and Lab view through modbus.
If possible how?

First, do a search for Modbus. There are several options available for communicating with Modbus devices from LV.
Then, if you have a more specific question, you can post it to the LabVIEW board (you posted to the feedback board by accident).
Try to take over the world!

Trouble reading OPC Server values with Labview

Hello there,
I am currently working with Siemens Equipment : a Simatic Microbox with an OPC Server.
I would like to read some variables' values provided by the OPC server with Labview 2012 (and DSC module), but I'm experiencing some difficulties.
I have set up my OPC Server as an I/O Server in a Labview projet. Then, I have created some Shared Values to treat them in Labview.
In the Distributed System Manager, I can read NI OPC Client Status :
Active -> true
Connected -> false
Enable logging diagnostic information -> false
OPC interface version -> OPC DA-3
Server ProgID -> OPC.SimaticNet.1
When I want to check any Shared Value, I have the comment : Server Failure.
I think DCOM/COM configuration of the client and the server are good (I can correctly read values with Siemens OPC Scout).
Maybe the issue comes from the connection between the OPC Server and Labview.
Has anyone had a similar problem ?
Thanks in advance,
Jeremy

You don't specify whether the server and the client are on the same PC or not.
I recently run in a situation where the Matrikon client was able to read from a remote server while the Labview program (using Datasocket) could not.
I suggest to try with Datasocket vi's to see what happens.
Paolo
LV 7.0, 7.1, 8.0.1, 2011
Attachments:
Read OPC variant.vi ‏17 KB

Rmi server communicating with client

Is there any way for an rmi server to communicate back to the client? What I mean is, the client connects to the server and calls some method x(). One of the arguments of x() is the client(x(AClient ac)). Assume that AClient is a JFrame and has a method y() which adds a button to the frame or something. If the server calls ac.y(), in my understanding/experience, the server would actually create a local copy of AClient and add the button to the local copy, not to the frame that the client user is looking at.Is this correct? {
If so, is there any way to have ac.y() add the button to the client user's frame?
If not, does anyone have any ideas for how to implement something like this relatively easily?
If not, does anyone have any ideas why it's not responding that way for me?I'm trying to avoid programming socket connections for this, and would love to be able to do it with rmi.
Thanks in advance,
m

Not sure exactly what your starting point is. But:
1. The client must be a UnicastRemoteObject.
2. If your client is behind a firewall, then the scheme probably won't work. (Explored exhaustively in this forum.)

Has anyone used Ethernet Gateway and LabVIEW, communicating with Ethernet/IP protocol ?

I have a PLC system (Jokab Safety B20) together with Ethernet Gateway (also Jokab Safety type E1).
What I want to do is to communicate with this unit using LabVIEW Ethernet/IP.
Read a couple of data and write a couple.
Has anyone anything like this with LabVIEW and Ethernet/IP ?
I'm completely new to using PLC's, but I have made a minimum PLC application, but can't get communication to work with LabVIEW (+ Ethernet/IP).

i generally use an OPC server to talk to he PLC and then use Datasocket to talk to the OPC server tags.
if that gaetway thing is an OPC server then you maybe abel to do data socket R/W via it.
Otherwise the NI OPC server may support that widget and (at the rate I bill out) is a good deal in the eyes of most of my customers.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Communication with modbus devices

Hello All,
My name Peter, I am currently exploring what LabVIEW has for instrument communication. I have explored a little on NI-Visa and used it for instrument communication through USB and Ethernet. My next task just now is to see how I can communicate with Modbus devices. I have done some background reading on modbus communication protocol and now have some level of understanding of what it is about. I hope to understand more as I continue to read more materials.
I came across an NI-Tutorial titled Connect LabVIEW to any PLC with Modbus. It is about communicating with a networked PLC using modbus. I followed all the steps described for creating Modbus master I/O Server, Binding shared variables to Modbus Address through the I/O Server and writing to Modbus Addresses in LabVIEW. On running my VI to deploy the shared variable, the following error occured.
Can anyone please guide me on what to do because I do not know exactly what is going ON. I engaged in this excercise with the hope of getting to understand more about Modbus communication and then see how I can apply thesame idea to communicate with the Modbus device available in my Laboratory. Please note that I do not yet know much about modbus communication and I am just learning about it now. I do not have any PLC connected to the network. Could that be the reason for the error? If anyone has got any other relevant document to help me get started with modbus communication I will be happy to have them posted here.
Thanks very much for taking time to read through my post message. Hope to hear a quick response from you.
Regards
Peter

Hi SmithD,
I would like to say thank you very much for making out time to respond to my queries. I have done as directed but still not getting result. Following the wire mode port setting configuration, I stopped the process and then selected the RS485/wire4 as the wire mode. On running the VI, an error pops up with the information that the Visa resource is Valid but the port cannot be accessed. I noticed that If I undeploy the shared bound variable the error does not pop up anymore. I concluded that maybe I was not supposed to have added the VISA configure Serial port in the first place.
Kindly tell me what to do.
My task is to read the holding register from a Modbus device. I have the register map with me, and know the TCP and RTU settings for this device. After the attempts I have made so far I was forced to believe that perhaps the device was not responding. I then resolved to using the QModbusMaster which was previously used to read the holding register. For reasons I don’t not know, It worked well with the TCP communication and returned an error that read " slave threw exception > unknown error". With that, I am now sure that the device is functioning properly, at least with the TCP.
Having obtained result from the TCP using QModbusMaster application, I want to simply do the same using LabVIEW.
Some few questions for which I would want to ask for clarification are:
1.) When using the Modbus Library, do I need to create both master and slave instance to be able to read the holding register? My attempt was to create a Master instance with the RTU parameters. The starting address and number of registers were specified at the input terminals of the Read Holding Register VI. This VI immediately followed the Create Master Instance VI. I was expecting that that would read the information contained in the specified registers and output it at the register value terminal. One challenge with this attempt was that with RTU it didn't work. I tried selecting TCP as the VISA resource. But the device was not showing on the list. I went to MAX to create a new VISA TCP/IP resource under the network devices but MAX could not detect the presence of the device. I am now thinking maybe the device is not supported by NI-VISA and so it will not be possible to use the Modbus Library with it.
2.) If the device is actually not compatible with NI-VISA, can DSC I/O server be used to read the information on the holding register?
3.) Do I need an intermediate device between a Modbus device and the PC to be able to read its holding register?
Please if anybody has got a good suggestion as to what to do to get my task achieved, kindly leave me a post.
Thanks
PETER

Trouble connecting to an OPC server

Hi guys,
The problem is connecting to a mass spectrometer, for which I have a dedicated LAN cable connection and an IP address. I can ping the device, and connecting to the OPC server works with the Softing OPC client, by manually entering the IP address of the server. However it does not show up in the remote machines list when I try to connect to it with via new I/O server. Is there a way to connect directly to an OPC server having only it's IP address?

Our lab was shut down for the holidays period, so I couldn't try anything for a while. Back on it now though.
Thanks for your suggestions! However, I still can't reach the server. Some more details in this post.
The server explorer doesn't see the device either. I think both the
server explorer and LabVIEW actually browse the network looking for
machines running some kind of Samba (SMB) server? That's at least
suggested by the characteristic '\\' added to the machine name I put in
there. I don't think the Mass Spectrometer is running an SMB server. It
does run http and OPC servers, and I believe that's it. So it's not 'visible' on
the Windows network. Is that a problem?
When I enter the IP address of the machine at the new IO server window,
it automatically adds the '\\' in front and gives the 'No such
interface supported' error described in the previous post. When I put
in the IP address of a non-existing machine it gives a different error
('The RPC server is unavailable') after a few seconds. So it does seem
to know there is a machine there, just it can't interface with it.
Reconfiguring the client side DCOM settings according to recipe above didnt seem to make a difference.
Anyone?

CRIO communicating as PLC with NI-OPC-Server

Hi there,
i have the task to implement a communication between multiple cRIO's and the NI-OPC-Server. The NI-OPC-Server has to act as data handler for a complex frontend.
I tried out the NI-OPC-Server and i was successful in communicating with the NI-OPC-Server as OPC-Client in Windows using an IO-Server and Shared Variables. But the task is to do this on a cRIO. I tried to open a data socket connection from a cRIO to the NI-OPC-Server using a specific URL using "DataSocket Select URL.vi". But as long i do not activate simulation in the NI-OPC-Server i get errors on opening the data socket connection. If i do activate the simulation, which is not the solution, i can write some data without error but the Quick Client of the NI-OPC-Server sees no changes for that data tag.
I have the feeling i am not at a good way to get this working. Is there anybody having experiences with this? Is data socket a possible way at all? Is it possible at all? Do i need to implement a cRIO-OPC-driver?
Thank you.
Solved!
Go to Solution.

Hi,
There's one pretty good tutorials and one webcast. Have you already study them?
Connect LabVIEW to Any PLC Using OPC (Tutorial)
http://www.ni.com/white-paper/7450/en
Connect LabVIEW to Any PLC Using OPC (Webcast)
http://zone.ni.com/wv/app/doc/p/id/wv-263
Chers,
Philip

How does labview opc communication with plc affect timing for the actual plc application

Hi Everyone,
I have a doubt and thus want to start a discussion regarding communication with PLC's from NI OPC server.
Let's imagine you have a production machine like a caping machine for a bottle production line, let's say the PLC on this machine is a Siemens S7300 which according to NI is compatible with NI OPC server.
The PLC would have already been programmed by the company who sells the machine to control it correctly.
The question is, if you'd like to add an interface, and all the capabilities that LabVIEW offers to this machine by controlling/monitoring its PLC, returning its alarms etc...
In that configuration is there a possibility that the LabVIEW application you would devellop affects the PLC's Behaviour and thus the machine functionality or yield and thus would have a negative impact?
Thanks a lot for your answers.
Best Regards,

Hi Olivioloyer Good Morning:
The issue here is that if you want to control, display and log data and funcionality from that PLC through LabVIEW you will have to change the program on the PLC to work correctly with your Interface and Alarming program that you will create in LabVIEW. If you develop a well designed architecture and an efficient code there will be no negative impact on yout PLC, on the contrary you will expand the funcionality and capability of your application.
Note: You will need to change your PLC program to achieve correct functionality with what your LabVIEW code will do.(Send and receive control commands). If you just want to monitor your PLCs behaviour, your code will be much more simple and maybe no change will be required on the PLCs program.
Juan Arguello
National Instruments México y Latinoamérica
Applications Engineer

Communication Problem in Mitsubushi PLC A2SH with OPC 4.5.1

While communicating with Mitsubushi PLC A2SH thru OPC 4.5.1 , it displays time out error , the settings of the Com port of the system is Baud = 9600, Parity = odd
Data bits = 8 Stop bits = 2, Flow Control = None . The same setting is done in the OPC & Mistubushi PLC Comm protocol. Iam using Labview DSC to communicate with PLC with OPC 4.5.1. How do i solve this Comm Problem in what steps.

You might increase the 'Recieve timeout' from 250ms to some higher values on the object (driver) and you might increase in Options >> Serial Ports... >> Receive Gap from 20 to a bigger value like 50.
Hope it helps.
Roland
PS: I've not tried it with this particular PLC, though.

Hello!!!how can I control an omron plc (sysmac cqm1)with an OPC server?I want to adquire a signal controlling its amplitude and frecuency.How can it be done with OPC server?I already have the NI CD of OPC drivers.Thank you

Hello!!!how can I control an omron plc (sysmac cqm1)with an OPC server?I want to adquire a signal controlling its amplitude and frecuency.How can it be done with OPC server?I already have the NI CD of OPC drivers.Thank you

Hola Jose David, que OPC estas utilizando?, Si tienes comunicación entre tu computadora y PLC pero falla la comunicación entre el OPC y el PLC? La configuración y direcciones entre los dos es correcta? La comunicación es por cable serial?
Espero tus respuestas
Saludos
Benjamin C
Senior Systems Engineer // CLA // CLED // CTD

How to setup and configure NI OPC Server to OMRON PLC (CJ2H model) using FINS Ethernet communication protocol?

Hi,
Could someone help me in the setup and configuration of NI OPC server to OMRON PLC (CJ2H model) using FINS Ethernet communication protocol? I already read some materials available in the web but it uses a different PLC and communication protocol. The OPC server is installed in my laptop and I'm using Windows 8 as my OS. I used a cross over RJ45 LAN cable and connected to the ETN21 module of the PLC. I was able to confirmed the communication of my laptop and PLC by pinging the ip address of the ETN21. I also tried to configure the OPC server based on the documents I just read online. I created a channel, device and tag to the OPC server. By the way, I just need to read the data from the tag I created. Can someone also tell me how to monitor the data on the tag? I hope that you could help me. Thank you in advance.

Good day,
Try following the instructions on the driver’s help, take a look at the attach picture. It should be a good starting point. After the PLC is configured you can use this tutorial (Connect LabVIEW to Any PLC Using OPC » http://www.ni.com/white-paper/7450/en/) for a guide on how to monitor the tags.
I hope this helps
Alejandro | Academic Program Engineer | National Instruments
Attachments:
OPC Server Help.JPG ‏237 KB

NI OPC server communication with B&R plc

Similar Messages

Maybe you are looking for