Opc server 2011 V5.5 in Lookout 6.6

Hello,
I am using Lookout 6.6 with the OPC-Server 2011 V5.5.
The NI-Server is reachable via Lookout and via the integrated OPC-Quick-Client. But if I am using an other Client such as the OPC Data-Spy or PROFILAB,
the server is not reachable, the server name is displayed in the list, but can not be accessed. Other installed OPC-Servers on my PC can be accessed by every client. Do I need to have a special licence for the NI OPC Server that came with the Lookout 6.6 Software Package? I am using Windows 7 Home 32bit.
Thank you for any advice
Greetings
Claude
Solved!
Go to Solution.

Hello,
Thanks for the reply, I found now the information to in the Licence Manager.
It is a pity , but I have to accept.
(Even my Labview 2009 Educational Version can not connect)
Greetings
Claude

Similar Messages

Windows 7 lookout opc server problems

Hello,
I am not able to successfully read from my OPC server 2011 within Lookout 6.6 on one of my pcs. I had built a process on a different pc that worked. Now on a new pc, after installing NiMax and configuring a NIDAQ PCI-6052E device and building the NI-DAQmx Global virtual channels using AI1-AI8 points then installing and configuring Lookout and building up a process, I can see the AI1 - AI8 points in lookout when I traverse the object browser and find process1>OPCClient1>computername>system>DAQmx>AI1 (for example). Once I do that, lookout alarms with priority-8, object name ...OPCclient1, area-comm description - Internal error (2): Processing read data (50): Can't convert data to Lookout format (00000004).
This has worked on a different pc, when I run lookout as Administrator... Any help would be appreciated.
David Istre

Hello, I replied once, but my response did not show up on the discussion forum.
Both PCs are running Windows 7.
I have placed the opcclient.ini file within the Lookout folder and then ran lookout 2 times. The first time I ran lookout, I was getting data from my opc client. The log file shows that (from 8:11am). I closed lookout and did some other things for about an hour and then ran lookout again. This time I could not get data from my opc client. Again, the log shows that (around 9:50am).
Is there a way to use a NIDAQ card within lookout 6 without having to use OPCClient? Also, is there a way to get better lookout support than through these forums?
David
Attachments:
OPCclient1log.txt ‏64 KB

OPC server for DCS

Is any OPC server is available for communicating Lookout with devices which use CS-275 protocol
Thanks in Advance

National Instruments does not have an OPC server that communicates with the CS-275 protocol. You will have to find a third party vendor that provides an OPC server for that protocol.
If you have a device that uses that protocol, the manufacturer may know of an OPC server for cs-275.
Green Rives
National Instruments
Industrial Automation Support Team

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

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

Omron OPC Server with Lookout 5.0

I am trying to set up a Lookout 5.0 application using the OPC Client, connecting to the Omron OPC server, CX ServerOPC. When I add the OPC Client, I find the server on the drop down list, but when I click 'OK' to create the OPC client object, once it connects to the OPC server, Lookout crashes. I get the message that Lookout.exe has encountered a problem and has to close. Has anybody used this server before and seen this problem? Any hints as to what could be incorrect in the client or server settings?

Hi,
What happens if you connect to the Omron OPC server from the National Instruments Server Explorer? Do you access to the OPC items succesfuly in Server Explorer?
Please also check the Tutorial linked below:
http://zone.ni.com/devzone/conceptd.nsf/webmain/B0CC5FE5CBC5727F86256808006AD802?opendocument
Hope this helps.
Best Regards,
Remzi A.
National Instruments

Can Labview v7.0 talk to a Micrologix 1100 PLC via Lookout Protocol Drivers OPC Server v4.5?

Micrologix 1100 <-> Lookout Protocol Drivers v4.5 <-> Labview v7.0
Hello all,
I am helping a local company to use their existing seat of Labview v7.0 to talk over Ethernet with a new Micrologix 1100 PLC. We were hoping to use their existing OPC server that came with Labview (circa 2000) so that they do not have to purchase a new OPC server. Their Labview package is the "NI Developer Suite Professional v7.0 Control Edition" which comes with a "DSC Module" which contains an OPC server called "Lookout Protocol Drivers OPC Server v4.5 (build7)". This software came out several years before the Micrologix 1100 was born, but OPC is supposed to be a cross-platform, cross-generation standard isnt it?
So, when I set-up the OPC server, it asks me which type of PLC I have and the only choices are AB_Logix (Micrologix 1500), AB_PLC2, AB_PLC5 (15 different flavors), and AB_SLC500 (5 different flavors). Can I use one of these that might be similar to the ML1100? I definitely want to use ethernet, not serial.
My application is just reading and writing a couple of variables from/to the Binary, Integer and Float data storage locations approx once per second.
Does anyone see a problem doing this without having to upgrade the OPC server to something that "officially supports" the ML1100 (Like Kepware)?
Thank you very much!!
frenchy

Hi Frency,
You can always just try the 1500 and cross your fingers! We could try to speculate on the forum, but a quick test would certainly be a better use of time. However, I do recommend that if you can upgrade the OPC server to one that supports the 1100 driver you should do so. Kepware and NI-OPC Servers both support this device.
Cheers,
Brian A.
National Instruments
Applications Engineer

LabVIEW DSC 2011 / OPC Client IO Server / Can I write to the OPC Server using OPC Groups?

Hi
I am using LabVIEW DSC module as a OPC client. My Shared Variables are binded to automation system OPC Server via "OPC Client IO Server".
On the OPC Server side it seems that the every write commands comes like one item at time, not like grouped.
Now I have tested this with the NI OPC Server as server and KepServer and LabVIEW DSC IO Server as OPC Clients.
When I use the NI OPC Server : OPC Diagnostics there are different events messages when the update request comes from KepServer or LabVIEW DSC.
There are log files on attachements for both write events.
Attachments:
Data from the KepServer.txt ‏6 KB
Data from the LabVIEW DSC OPC Client.txt ‏18 KB

Hello Pentsi,
I have received confirmation (from the PSE in the US) that DSC doesn't support group writes
There however work-arounds that might provide a solution:
- The first solution I had in mind was like this. Update the 50 OPC items as fast as possible.
Then use a 51st item as synchronization OPC item to check/indicate if new data has arrived/has been set/is available.
So LabVIEW sets 50 OPC values as fast as possible. The 51st value becomes goes from false to true when the first 50 values are written.
When this (51st) value is true on the OPC server you can read out the first 50 values (from the non-LabVIEW side). When you've read out these values, then you can set the 51st value back to false (from the non-LabVIEW side).
In the meanwhile at the LabVIEW side you wait until the 51st value goes back from true to false.
When it becomes false, then you write again those 50 values and afterwards set the 51st synchronization value from false to true.
And this keeps on going...
Note: Keep in mind that you only have to monitor one event at the side of the Automation System OPC Server in this case (the 51st) and based on an event occuring over there you can just do a group read of the 50 others. Also keep in mind that the maximum rate (6500 updates per second) from inside LabVIEW with the DSC Module OPC client I/O server was also mentioned in this document (http://digital.ni.com/public.nsf/allkb/63C043359F1E12538625726E005BCD0C?OpenDocument).
Could this be a possible solution for your problem?
If you're using one of the OPC servers in this list (http://zone.ni.com/devzone/cda/tut/p/id/6417#toc19), then you can also use NI OPC Servers to update tags instead, which supports a faster update rate.
Kind Regards,
Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
CLD, CTA
If someone helped you, let them know. Mark as solved and/or give a kudo.

Problems using Modbus TCP accessed by NI OPC Server

Hi there,
i'm using NI OPC-Server to access a measurement module. The buildup is quite easy, my system with NI OPC, a modbus gate and there the module connected with RS485.
There's a thermocouple to provide me some sample data.
But there's the point. I know, my data is in the Holding Registers and I can access them, but every data type I'm trying doesn't bring my my data out, just any other (sometimes Huge with e34, sometimes very small like e-13...) sorts, i can't understand.
The type provided by the module should be single precision.
In Lookout the address used to be is 41000 in Labview it's just 999 and in the "target" OPC-Server I get some values at 401000 but not useful.
I also get the same results accessing 301000 in different types.
Read/Write or Read Only is equal.
I've tried to tell my OPC that the values are Strings, Floats, Words, BCD and all other possible ways OPC offers me, but nothing results in a usable temperature.
I hope I missed something and you could suggest it.
Cateros
Solved!
Go to Solution.

Thanks for your reply.
in LabVIEW I'm using the provided Modbus Libraries. If I unbundle the Holding registers, my value appears at Holding Register [0], I'm type casting it to single and get the sample temperature. (Address 999->unbundle->typecast->value)
In NI OPC, I'm reading ( [depends on zero based addressing] 300999/301000 equal to 400999/401000) an already typecasted Holding Register [1] compared to LabVIEW (and the value changes in the second or third digit behind the comma and they are changing at the same time). Data type in the tag is float.
Another disturbing thing is even if I change in the options "using zero-based addressing in registers" my value does not change.
If I'm reading two addresses close to each other (as you mentioned 401000-401001) I'm getting an unknown data type and no results. How do I read multiple addresses without such errors? And how do I specify a special register to read?
Scaling should not be the problem, I am having three ways to get my value (FTP-Server on the gate (just a *.dat file with correct type), software the the module manufacturer (while measuring and configuring the module) and LabVIEW(as can be seen above)) .
Sadly, I have not found any useable modbus documentation about the module (just it can use modbus, you have the registers, you could read/write and fine)
When I'm adding a second couple to the module, in LabVIEW Values in Holding Register [2] and Holding Register [3] appear and are changing.
Cateros

How to understand the Error message of the connection of OPC server

hi guys, one issue need your help
when I run the NI OPC servers, one error message will appear in the process information.
Just like as followed:
===========================================================================
2011-6-23   11:50:05   Default User   NI OPC Servers   Stopping Simulator device driver.
2011-6-23   11:50:05   Default User   NI OPC Servers   Closing project D:\National Instruments\Shared\NI OPC Servers\projects\simdemo.opf
2011-6-23   11:50:25   Default User   NI OPC Servers   NI OPC Servers
2011-6-23   11:50:25   Default User   NI OPC Servers   Unable to load driver DLL 'D:\National Instruments\Shared\NI OPC Servers\drivers\dataforth_isolynx_u.dll'
more messages
=============================================================================
how to understand "2011-6-23   11:50:25   Default User   NI OPC Servers   Unable to load driver DLL 'D:\National Instruments\Shared\NI OPC Servers\drivers\dataforth_isolynx_u.dll'??????
Thanks

Hi!
I have the same problem when opening the OPC Server.
Unfortunately I have no solution, but I think it has something to do with incorrect Certificates and is more of a Windows Problem.
If anybody can help, please let us know!
Best Regards
Martin

Interfacing PLC siemens S7_300 and LabVIEW DSC using siemens OPC server

Does anyone already interface Siemens PLC S7_315-2-DP with LabVIEW DSC using Siemens OPC server?
Is that a good solution? Are there any hidden problems?

The use of an OPC Server is the way to go when dealing with LV. If you already have Siemens OPC Server then use that. Otherwise, NI has a product called IA Severs/Lookout Protocol Drivers (LPD), which has a large selection of drivers for PLC's. After configuring the driver, LPD is the OPC Server for the device.

OPC Server PLC

Hallo,
I am doing right now the tutorial from NI " Connect LabVIEW to Any PLC Using OPC". And the first capital was everything richt, "View Existing PLC Tags with NI OPC Servers 2012".
But in the second capital "Connect LabVIEW to OPC Tags by Creating an I/O Server" I can't get the picture as the 4. step "Select OPC Client in the Create New I/O Server Window and click Continue. ".
The problem is, there is no option for "National Instruments.NIOPCServers.V5" to choose by me. How can I get the pic as the tutorial?? Why I can't get the "configure OPC Client I/O setup" menu??
My system:
LV 2012, Win7,
Does somebody know the problem??
Thanks a lot!
Cabio

But I think my OPC Server is running, the tool OPC Quick Client can connect to server "National Instruments.NIOPCServers.V5", it is also showed in the Pic.
And I have fund a VI "C:\Program Files (x86)\National Instruments\LabVIEW 2011\vi.lib\variable\tagger\opcClient\GetOPCServerList.vi", this VI can find the "National Instruments.NIOPCServers.V5". But NI-DSM cant find it.
I am confused~~~
Attachments:
OPC_Quick_Client_2014-01-21_14-58-00.jpg ‏342 KB
GetOPCServerList_VI _2014-01-21_15-45-33.jpg ‏45 KB

Error 1101 - Cannot communicate with Experion OPC Server

Hello,
I am having an issue whereby I cannot Read/Write to an Experion OPC Server through Labview and Datasocket, and get Error 1101.
The Program is below.
- I have been able to connect to Experion with another OPC Client (INAT) without any issues.
- The error says I lack the privaleges, but if I follow the instructions and change these priviledges via Datasocket Server Manager, it makes no difference.
- We are trying to run this program on a Labview 2011 and Windows 7 system.
- I have tried running this same program on a WinXP computer with Labview 2009. I had to save it for previous versions, but when I run it, it comes back with a 'Generic Error', whatever that means.
Can anyone help me solve this problem and steer me in the right direction.
Kind Regards,

Have any users found a remedy for this issue?
I am having the same problem. I have a very simple network set up where I want to use DS in LabView on one computer (192.168.1.101) to read from an OPC server on another computer (192.168.1.1). The OPC server, DCOM permissions, etc. are all correctly configured, as I can use a third party OPC client to view the server tags and values on the remote PC from my LabView PC.
I am using the "Monitor OPC Items with DataSocket.vi" example VI, just specifying a tag from my existing remote OPC server as an initial test. I can browse to and select the tag on the remote computer that I wish to read in LabView using the "DataSocket Select URL.vi". However, after selecting the tag and passing the URL to the "DataSocket Open" block, I receive Error 1101. (Same occurs if I just directly pass the URL string to the DS Open block.)
I have added "localhost", "everyhost" and "192.168.1.1" to "DefaultReaders", "DefaultWriters", and "Creators" groups in the DataSocket Server Manager. I have stopped and re-started the DataSocket Server, and even rebooted the entire PC, but the error persists.
The specific error text is:
Error 1101 occurred at DataSocket Open
LabVIEW: (Hex 0x44D) Insufficient privileges to read, write, or create an item in the DataSocket Server. Use the DataSocket Server Manager to configure these privileges.
It seems as though this should be an easy fix, given that the OPC server is readily readable by an OPC client. I would appreceate any help, as would mkenneday, if they haven't already solved their issue.
Thanks,
-Brandon

NI OPC server vs. KEPDIRECT

I am in the process of setting up an industrial PLC project. I am wanting to use Labview for communication with my Automation Direct PLC system. Automation Direct offers an OPC server KEPDIRECT for $295.00. NI OPC server is quoted at nearly $2,600.00. Money is not a factor in my situation and I want to purchase the best and most efficient server. Can someone explain to me the difference in the two servers (why one is more expensive than the other) and which one is better for working with labview and a PLC. I currently have my system programmed with Automation Directs Direct Soft 5 and Lookout Direct and want to completly switch over to Labview if this makes any difference. Thanks for any input and help.
Solved!
Go to Solution.

Blue Ridge Test, a certified NI Alliance Partner, has successfully implemented a control / monitoring system with LabVIEW which interfaces to networked Automation Direct PLCs through ethernet (ECOM modules) and OPC. If you are interested, we would like to talk with you about your application to see how we might partner together to achieve an elegant, cost effective solution which meets your goals while removing months from your timeline.
If you decide to approach this on your own, there will be configuration challenges (e.g. extracting the correct tags from DirectSOFT 5, setting up OPC, etc.). Before addressing those, though, you may want to think through your programming requirements such as those listed below.
After the setup phase of your project (i.e. configuring hardware & signal conditioning, verifying connectivity, demonstrating various portions in LabVIEW, etc.), you might consider your architecture before moving forward. How will you store your data? How will you view / analyze the data later? Is the architecture readable, scalable, and maintainable? What will happen when you want new features (e.g printing reports, user logins, or controlling other external equipment or processes while saving data and displaying results)? What kind of user interface will you use?
Set yourself up for success long term by thinking about the right architecture today. We frequently have customers whose "simple engineering experiment" grew on them. And, interpreting bad LabVIEW code a year into a project can be a lot like deciphering abstract art (and equally expensive).
Jason B
434-525-7312 x114
Message Edited by Support on 02-10-2009 05:17 PM
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs

OPC Server Remote Connection LabVIEW 8

Hi
Currently I am trying to access a VI with a Shared Variable from a remote computer using an OPC Client. I haven´t succeed on this becasue I cannot find the OPC Server on the Host Computer.
Here is what I am using:
Host Computer:
Windows XP SP2
NI Developer Suite November 2005
LabVIEW 8 with DSC Module.
Remote Computer: The same as above.
Here´s what I have done.
I created a new project with a library that included a Network Published Shared Variable. The VI is quite simple it just generates a number that is written to the Shared Variable. Once the VI was running I opened the Server Explorer on the host computer, browsed My PC and connected to the server Variable.Engine in which I was able to see my shared variable. Then on the Remote Computer I opened the Server Explorer and browsed on my Network Places and when I tried to access the Host Computer I got the following error: "Unable to connect to \\HOST! Make sure that this computer is on the network, has remote administration enabled, and that both computers are running the remote registry service"
I have tried by using the Matrikon OPC Server Explorer and I got the same results. I read many documents that refer tis problem as a DCOM setting because of the firewall fo XP SP2.
Here´s a list of the NI documents I reviewed.
How Can I set up LabVIEW, LabVIEW DSC, and Lookout to work with the windoes XP firewall
URL: http://digital.ni.com/public.nsf/websearch/0D7B86F4B4D19A5E86256F9A006EECB1?OpenDocument
Setting Proper Access for Remote OPC Server When Using National Instruments OPC Clients
URL: http://digital.ni.com/public.nsf/allkb/5C8A90CD57B279F286256C2C006F1EB4
I never got the results I expected. Then I tried the Matrikon OPC Simulation Server and the Matrikon OPC Server Explorer(Client) and I Succesfully connected between Matrikon servers and clients.
My project is based in accesing the LabVIEW OPC server with a generic OPC client but I cannot get the client to connect to the server.
I will apreciate some advice on this issue.
Marcos

Marcos,
If you are using two instances of LabVIEW 8, I would first take the OPC part out and just try viewing Shared Variables on the remote computer. This needs to work. One document to check is the following KB: http://digital.ni.com/public.nsf/websearch/6E37AC5435E44F9F862570D2005FEF25?OpenDocument. I would also make sure the opcenum.exe service is running on both machines.
Once browsing to Shared Variables works, you can test the OPC aspect of the Shared Variable Engine. Server Explorer is an older OPC 2 client, but should work in most cases to browse to OPC Servers -- you'll need to make sure the registry settings on the host computer are set up correctly as per the KB you mentioned, and also make sure to connect to the OPC Server, add a group, and add items manually from within Server Explorer, rather than using the Wizard.
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me

Opc server 2011 V5.5 in Lookout 6.6

Similar Messages

Maybe you are looking for