Lookout opc problems

I am using Lookout 6.0.2 on a new Win XP desktop. The Lookout OPC client object is used for communications via Rockwell Software RSLinx's (Professional Rev 2.43.01.23) OPC server to ControlLogix PLC's over ethernet. In other words, the Lookout communicates with RSLinx by OPC, and the RSLinx communicates with PLC's by ControlNet.
We have 3 Lookout processes, one which is the "server" process, and contains the OPC Client object. The other 2 process files are "client" processes, and reference the OPC Client object by symbolic link.
We have many Lookout switches in the "client" processes, that are remoted to a tag in the ControlLogix PLC using symbolic link. A typical link for a remoted switch is:
..\..\[Link_to_Drivers]\OPCclient1.PLC_12.Online.SWITCH_TAGNAME
OR IF USING ABSOLUTE REFERENCE: \\ComputerName\ProcessName\[Link_to_Drivers]\OPCclient1.PLC_12.Online.SWITCH_TAGNAME
In this way, the Lookout switch object has a read/write link.
The problem is this: Periodically the write link will stop working. When this happens, all the Lookout switches and even the Lookout pots will lose ability to write to PLC, but the read links are still working. We can read the data and the switch positions, but the changing setpoints with the pots and operating equipment with the switches is then impossible. This "lock up" can be fixed by closing down all the Lookout processes (but not Lookout), and then restarting the Lookout processes.
This problem is intermittant and not repeatable. Does anyone have idea how to troubleshoot this problem, or have an way to isolate and fix this problem?

doug:
You may want to repost in the Lookout board:
http://forums.ni.com/ni/board?board.id=190
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Similar Messages

Lookout opc or link problems

I am using Lookout 6.0.2 on a new Win XP desktop. The Lookout OPC client object is used for communications via Rockwell Software RSLinx's (Professional Rev 2.43.01.23) OPC server to ControlLogix PLC's over ethernet. In other words, the Lookout communicates with RSLinx by OPC, and the RSLinx communicates with PLC's by ControlNet.
We have 3 Lookout processes, one which is the "server" process, and contains the OPC Client object. The other 2 process files are "client" processes, and reference the OPC Client object by symbolic link.
We have many Lookout switches in the "client" processes, that are remoted to a tag in the ControlLogix PLC using symbolic link. A typical link for a remoted switch is:
..\..\[Link_to_Drivers]\OPCclient1.PLC_12.Online.SWITCH_TAGNAME
OR IF USING ABSOLUTE REFERENCE: \\ComputerName\ProcessName\[Link_to_Drivers]\OPCclient1.PLC_12.Online.SWITCH_TAGNAME
In this way, the Lookout switch object has a read/write link.
The problem is this: Periodically the write link will stop working. When this happens, all the Lookout switches and even the Lookout pots will lose ability to write to PLC, but the read links are still working. We can read the data and the switch positions, but the changing setpoints with the pots and operating equipment with the switches is then impossible. This "lock up" can be fixed by closing down all the Lookout processes (but not Lookout), and then restarting the Lookout processes.
This problem is intermittant and not repeatable. Does anyone have idea how to troubleshoot this problem, or have an way to isolate and fix this problem? Thanks!

This problem is fixed by lookout 6.0.2 updates. It can be downloaded from http://joule.ni.com/nidu/cds/view/p/id/506/lang/en
You need first to login MyNI, and then download lo602_updates.zip. Unzip it and copy all files to lookout folder.
This update is applied to Lookout 6.0.2 server system. You don't need to copy these files to client system.
Ryan Shi
National Instruments

How can I edit the database in Lookout OPC Modbus driver OPC sever with the address that has a write attribute?

When I use Lookout Modbus driver OPC to communicate with my instrumnets, I edited the database number such as 41202 that has a Write attribute in my instrumnet manual, the OPC explorer got bad data, and the OPC server gave the illegal address alarm, when I input the address such as 41203 that has R/W attribute, it worked very well. Is there a way to fix this problem. When I used other OPC server, there was no this kind of problem. Thanks!

Thanks for your suggestion. I checked the Modbus manual of my instrument, the register is 16 bit. I tried to edit the data according to the Modbus data member in lookout modbus drivere server for several different member, but the OPC still gave me the illegal address. I think the problem may be produced by their attribute, for the address 1201 and 1202, they have the write attribute, for other addresses, they have W/R attribute, and they can be read or write through Lookout OPC server perfectly. when I used the demo OPC server from other company, it can work well, but it is not convinient for me to use Labview when I use that software. I prefer NI Lookout OPc server. I am using the Lookout 4.5. I am wondering whether the Lookout has some shortcoming when I
use the Modbus driver. Please give me any suggestion, is there any newest version of Lookout OPC sever? Thanks!

Lookout OPC reads A-B PLC Output word bit 15 as negative.

I am using LabVIEW and Lookout OPC driver to read an output word from an Allen-Bradley PLC and display the bit values as booleans. When bit 15 goes to a logic one, the value the opc driver reads goes negative. this causes the Labview Number to boolean array converter to 'mis-read' the bit values. How can I prevent this mis-read?

I dealt with this problem a couple of years ago.
I had to write a VI that decode the bits and fixed it.
THe VI just checked the MSB and acted accordingly.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Can I write a data to intrument through Lookout OPC driver sever?

I can read data from intruments through Lookout OPC driver sever, how can I write data to instruments? Can I still use the dataSocket to find the address and send the data through Lookout OPC driver sever? Thanks!

The write should work just like the read. The OPC server will let you write as well as read.

Lookout OPC Client – Asynchronous I/O and Update Rate serious problems (Sequence of data)

I am using the Lookout OPCClient driver to connect to AB PLCs (EtherNet/IP protocol) and power measurement equipment (Modbus TCP protocol). The OPC server is the NI OPC Servers. The data that are read out from PLCs and PMs are energy meter readings, energy counters, power, voltage, current, frequency, power factor and el. energy quality measurements (THD). That energy meter readings are being stored in SQL database.
I am experiencing a serious problem regarding the accuracy of the meter readings. Several times per day, randomly, meter readings are losing the time sequence. For example, sequence is: 167, after few seconds 165, 166. In other words, present value followed by two previous old values. That generates a serious problem in our application that is expecting a naturally rising sequence of counter values.
Analyzing further, I isolated the problem to the connection between Lookout OPCClient and OPC Server. I made a simple application in Lookout 6.7 (opcproc.lkp, attached) with OPCClient parameters: NIOPCServers, OPC2, Asynchronus I/O, Update rate: 10000, Deadband: 0.0, that is reading just one tag from NI OPC Servers demo application (simdemo.opf).
By using OPC diagnostic tool from NI OPC Servers I record the sequence of OPC requests and responses. I found out that OPCClient sends every 2.5 sec “IOPCAsyncIO2::Refresh2()” call that is request for refreshing of all items in one OPC group. Few milliseconds later OPC Sever responds with callback function “IOPCDataCallback:: OnDataChange()(Device Refresh)” that actually refresh the data.
This periodic sequence is intrinsic to the OPCClient and cannot be disabled or changed (by my knowledge). This sequence is periodically interrupted by “IOPCDataCallback:: OnDataChange()” caused by update rate parameter of OPCClient (client is subscribed to server for periodic update of changed items).
In the case of demo application on every 4 refresh callbacks caused by refresh requests (2.5 sec) there is one update subscription callback determined by Update rate (10 sec).
QUESTION 1:
What is the purpose of update sequence and update rate when we have every 2.5 sec fresh values?
PROBLEM
The problem arises when we have a large number of items in OPC group. In that case the OPC Server starts to queue refresh requests because they cannot be fulfilled in 2.5 sec time because of large number of I/O points that must be scanned. At the same time update subscription callbacks are running at the period determined by Update rate. I observed in my production system that regular update callbacks has higher priority than refresh callbacks from the queue. That causes the loosing of timed sequence of data. After the update callback with fresh data, sometimes follow one or two refresh callbacks from queue with old (invalid) data. By adjusting Update rate parameter (1 hour, 2hours …) I can postpone the collision of data refreshes but I cannot eliminate it. Furthermore, the 2.5 sec automatic refresh are large burden for systems with many I/O points.
QUESTION 2:
Is there a way to disable automatic refresh request every 2.5 sec and just use update requests determined by Update rate?
QUESTION 3:
Is there a way (or parameter) to change the period of automatic refresh (2.5 sec)?
This problem is discovered for Lookout 6.5, 6.6 and 6.7 so I could say it is intrinsic to OPCClient. If I use synchronous I/O requests there is not an automatic refresh, but that is not an option for large systems.
Thanks!
Alan Vrana
System engineer
SCADA Projekt d.o.o.
Picmanova 2
10000 ZAGREB
CROATIA
T +385 1 6622230
F +385 1 6683463
e-mail [email protected]
Alan Vrana
SCADA Projekt d.o.o.
ZAGREB, Croatia
Attachments:
opcproc.zip ‏4 KB

The physical connection from LV to the switch is (I believe) copper crossover to fiber converter into a switch. Then, fiber from the switch to the end device (relay). The relay has all of the typical modbus registries and has been verified by inducing signals in to the system and measured/polled in LabVIEW and observed Variable Monitor. I am working with LV 8.2 and 8.5.
An OPC server would only add an additional translation of addressing within the configuration. The only real draw back would be the network overhead required to do this processing and not being representative of the end design configuration.
I will reiterated my question in another way:
I must answer the question to management that relates to data collection, test results and analysis; how often are you polling the client in relation to the outcomes measured? At this time I can not point at any configuration in the set up and execution that directs the data framing rate. I only measure the traffic and work with results. This needs to be clearly identified based on the relay modbus/tcp design capability of supporting an fixed number of client requests per second.
For testing purposes, I would like to be able to stress the system to failure and have prove capabilities with measured data. The present problem is that I have no basis to establish varying polling rates that effect the measured data transmission.
This raises another question. What handles the Variable Monitor data requests and how is this rate determined?
Thanks for your interest in my efforts.
Steve

Lookout OPC Communication Problems

I am running a Lookout process with an OPC server to connect to a
ControlLogix PLC. My Lookout process will not always reflect the
current state of hardware, i.e. simple Boolean objects do not update
on the display control panel. I can, in some cases cause the display
to change by changing the state of my hardware manually (actuating a
limit switch for example) thus Lookout sees an event and updates the
display. But this does not work in all cases so I have no way of
knowing if the display is accurate.
Similary, changing the position of Lookout switches and pushbuttons
on the control panel will be reflected in the plc ladder logic but not
write back to Lookout to report the change. This is true for both
local and remote position source
s. I should add that switching from
OPC1 to OPC2 or OPC2 to OPC1 can cause some signals to reflect what
hardware is doing but there is no definite consistency that one can
point to that will identify the problem.
Finally, communication between the OPC Server and the PLC is fully
functional and verifiable. So there seems to be a fundamental flaw in
my design any advice on this issue would be greatly appreciated.
Leo

Hello Leo,
Have you tried turning On the Force refresh after write setting?
Also, try polling the device periodically to force the updates.
Regards,
Khalid

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

Dsc opc problem

Hi!
Im trying to connect Labview to Siemens S7-200 with PC-Access OPC server. I tried to use IO Serer and connect it to PCAccess, to PLC. Then I tried to connect it with datasocket to PC Access, and both times i had the same problem. Communication was too slow. For example, when i changed some value in labview, opc server reached that value in 5 seconds. How can i solve this problem?
Thanks

This problem could be because either the scan rate from the PC-access OPC server is too slow, the client program is reading data too slow, or both.
Are you using Shared Variables or Datasocket?
Have you checked the Tag properties on the OPC server? There should be a scan rate from the PC-access OPC server and you can set that rate.
Also, you can check in the tag or variable manager how fast the data is updating.
Regards,
Juan Galindo
Applications Engineer
National Instruments

Datasocket - OPC Problem

Hello
I have a problem with Datasocket, when I try to read from the "NI OPC Servers", I can't. But, if I execute the program with the option "Highlight Execution", there are not problems. I've already tried to put a "Wait" between readings, but the problem doesn't disappear.
Thanks for your comments
Solved!
Go to Solution.

Thanks NitinD and billko for your answers.
I've already solve the problem, i'll try to explain it (excuse my English please).
Before, I put "DataSocket Open", "DataSocket Read" and "DataSocket Close" in the same loop iteration, without time between open the connection and read from the OPC Server. This made than the result of the reading was '0' all the time. Here we can see a screenshot:
To solve this, I've separated the "DataSocket Open", the "DataSocket Read" and the "DataSocket Close" in three diferents loops, and I've added a wait in the first loop:
No problems now, I think there wasn't enough time between open the connection and read from the OPC Server.
Regards

LookOut expression problems

Hello guys,
I've encountered a very strange situation today. I created an expression in a server file which then be used for another calculation. To be sure that my expression was working fine, I dragged the expression out to a panel to see if I could get a number, and I did. The strange thing was that expression was X out as if there was no connection, but my number was still updated. I could see my number correctly changing up and down, but the whole thing just X out. I've tried to reboot the server to no available. I assume that LookOut might take correct parts and leave the wrong one out which resulted in the X. However if something in my expression was wrong (such as mistyping), LookOut wouldn't even take it at all. I've tried to break that long expression down to piece by piece, and every single one was working fine. What would be the problem here?
Frank Nguyen
Solved!
Go to Solution.

I tried to create an expression = Pot1.value+FieldPoint1.AI000.00.
The FieldPoint module doesn't exist. So, I got alarm on the FieldPoint1 object.
I saw X on the expression, and when I control Pot1, the expression value changes.
So, it looks like the same behaviour. Take a look at the expression, does it read any data from driver object?
Another way is to replace every single part of the expression with a constant value one by one.
Ryan Shi
National Instruments

Nipalsm ans OPC problems

I have just taken delivery of a cFP-180 network interface and after installing the software, the PC reports an NIPALSM.EXE application error on start up. Also, when I try to run the National Inst Server Explorer it too crashes. I can however read from the cFP-180 using MAX.
I have uninstalled and re-installed the software and it is the same.
nipalsm.exe is Ver 1.15.39.3.0
nipximu.dll is Ver 1.0.0.49153
I am using Windows XP
Any ideas what could be wrong?

Thanks for your reply (and your patience), it is much appreciated. The Keithley driver is available from:
http://www.keithley.com/support/data?asset=50494
The release notes for the above (http://www.keithley.com/support/data?asset=50493) say that the Keithley drivers actually use the NI-VISA runtime so I would be very interested in discovering what is involved in using this directly, rather than using Keithley's IVI. I will check this out.
The notes also refer to know issues with NIPALSM but I dont know if this is relavent.
I am not able to access the equipment today but I will find out the software info you have requested tomorrow.
Thanks again
Message Edited by Tony Dean on 05-23-2007 09:15 AM

HAD PROBLEM INSTALLING LOOKOUT 6.0.2. LOST ADMIN PASSWORD.

I have been emailing Ryan Shi about a Lookout OPC fieldpoint problem where
OPC fieldpoint stops communicating. He has informed me that there is a patch but I have to install lookout6.0.2. I had a problem doing this.
I was able to load the new version of lookout but the administrator password was altered during the install. I restored my system to an earlier version. How can I perform this update without this problem occuring?
Thanks,
Gene

Gene,
What's your current lookout version?
If it is 6.0.0 or 6.0.1, you'd better install 6.0.2 first and then apply the patch. Before you install 6.0.2, backup this file C:\WINDOWS\system32\lookout.sec and then delete it. The installation will generate a new lookout.sec file with empty password. The admin password by default is empty. What you need to do next is to reset all the users and passwords.
In general, the password is stored in lookout.sec and won't be changed during uninstall and install, however maybe your lookout.sec is corrupted.
Ryan Shi
National Instruments

Lookout Logos ressource problem

Hi,
I have encountered a very weird behaviour using Lookout. We have a server (quad xeon 700) using a dual port intel networking card. Since we had some problems with one of the server we tried to use a backup server that is identical. Once we'd setup it (same configuration as the old server) we had a problem with Logos ressources.
- The first time we boot the computer Lookout was working. We have a monitor interface and everything was running, the console were communicating with the server.
- We use a Datasocket link between a LabVIEW server and the Lookout server on the same computer. When we start the communication between them Lookout crash randomly, no error messages.
- After a crash there is "red X" on the monitor screen and the
Lookout server Logos ressources are not accessible. What I have tried to do is to re-link the object that as "red X". It worked but when I restart Lookout the new objects have "Red X" on top of them.
- The following action make Lookout works again : Change the Network configuration (Unregister and register them back to the domain), Re-install Lookout, Re-install LOGOS. But when LabVIEW communicate with Lookout the same problem occur again.
I know that it looks very strange and I don't expect that someone else had this problem before. This system works on the other server (we have put it back and everything works fine except for some bugs). I wonder if someone could have an idea of items I could check.
Any help appreciated!
Thanks a lot!
Thrawn

Thrawn,
We need a little more information on your situation. Please indicate your software versions (Lookout and Logos) and Operating System of both PCs. Was the Datasocket connection in LabVIEW DSread, DSwrite, or front panel? Are you using the OPC protocol or the Lookout (logos) protocol? If you have not already, try connecting to the Lookout OPC server using Server Explorer. What is the result?
Regards,
Michael Shasteen
Applications Engineering
National Instruments
www.ni.com/ask
1-866-ASK-MY-NI

Lookout executable encountered problem

Hi guys,
We have lookout 5.0 installed(one server and 3 clients). Before all systems were working ok. But last one month, im facing several issues like:
1. one or two clients get stucked.And when i Restart the server all start working again.
2. Sometimes graphs are not get plotted then again restarting the server solve the problem. But restarting server everyday or two!!!! I reformated the server but same problem persists. system specs are 3 gb ram, 500 gb harddisk and win xp.
3. another issue im facing since yesterday whenever i try to make changes and save them... it get stucked and message pops up lookout encountered problem and needs to close......
please help me its quite urgent

Thank you for this update, Ryan.
The OS on this PC is WindowsXP Pro, with the lastest SP3. It has just updated Windows few weeks ago.
I thought that the problem might be with this oleaut32.dll, but if you don't recommend replacing it I will not do it.
One additional comment regarding this error: I have noticed some time ago that when I use AB driver (OPC) the process edits faulted very often. It was happening often when I tried to create a new object with AB OPC driver. I thought at that time that the issue might be with OPC driver, but I was never sure of that. Now I use Automation Direct OPC driver and it also stops running, but less often. My OPC servers run fine as far as I can see it. This might be just a coincidence, you might be more familiar with Lookout and errors. If it comes from Windows I will try to create a new process and follow your recommendations.
Darek

Lookout opc problems

Similar Messages

Maybe you are looking for