Lookout 4.5 Upgrade

Hello all,
A customer called that is running Lookout 4.5 on Windows 2000 and would like my company to provide an updgrade. They of course want to spend as little money as possible on development, so asked us to see what version of Lookout (and Windows) that we can basically take the 4.5 database and load it into a newer version of Lookout without any (or as little as possible) development work. Say for entence could we get a WIndows 7 machine install Lookout 6.6 and import our project and everything be fine? Thanks for the help in advance.

From 4.5 to 6.7 should not be too much headache, depending on ActiveX and drivers used.
Archive database to external drive
Open processes to recompile on NEW machine
Open MAX on NEW computer, move database to new computer
Rename to match machine name if needed.

Similar Messages

Is there a free upgrade from Lookout 5.0 to 5.1?

Folks:
I just got handed a project that uses Lookout. My customer currently has 5.0 and I was wondering if I should upgrade to 5.1 and how. Is there a free upgrade patch or something to do this?
Also, I am running on Win XP Pro (SP2); are there any major issues with 5.x on XP Pro?
thanks in advance,
Kevin C. Rea
http://kevincrea.com/

hello sirs
i want to implement modbus ethernet. what are the steps required for doing settings in LPD file of industrial automation
vijeta

Lookout Upgrade Dev/Server-Client Licensing

Hello!,
WE recently upgraded from Lookout 4.5.1 Enterprise Dev./Server Unlimited I/O License and Unlimited Client License to Lookout 6.0.2 Dev/Server Unlimited I/O License- one client license. Are we not entitled to an unlimited client license as an upgrade? Thanks.
Sugarman

You'd better call NI's customer service.
Ryan Shi
National Instruments

Proceedure to upgrade from lookout 6.0.0 to 6.0.2

I am looking for some direction on the proper proceedure to upgrade an
existing 6.0 installation to the newly released 6.0.2 version.
The readme file says to remove the previous installation of lookout and
to refersto the release notes. The release notes do not give any
specific instalation instructions other than to install on a clean
computer.
Is there are proceedures that will fully back up my data and
configurations that will restore the proceses and data when the upgrade
is done?
Thanks in advance.

Hi Alan,
If you images were just images from the default Graphics directory, you should have no problem. However, if you used images from the Image Navigator or imported custom graphics, these will need to be added to your new installation. You can either create a subdirectory in the Lookout/Graphics directory, put your images there, and relink all your images to look at the new folder, then copy this folder and put it back to that same location after reinstalling. However, if you are simply upgrading on the same computer, it's probably easier to copy your entire Graphics directory to a safe location, then uninstall/upgrade, then copy the backup Graphics folder over the new Graphics folder after reinstalling. See the following KB
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me

Upgrading to Lookout 6.7.1 from version 5.1 on new computer

Hi
We recently upgraded to Lookout 6.7.1 from version 5.1 (build 8). We copied the
database, Source Files, Process Files from the old computer to the new
computer. We also attached the database in NI Max. We then updated the files
when we opened them in the new version 6.7.1. We now are missing data and we
are experiencing issues with the following:
1. No Trends are trending
2. We have a screen named Instruments Settings but the numeric values are not
displaying
3. We have tried changing the numeric values for the Instruments Settings but
they will not write to the database
4. We have tried the Revise Potentionmeter but it is not writing to the Remote
URL
5. The Data Member Configuration is not editable
Below are screen shots:
Thank you for any assistance you can provide.

HI Bob
The database conversion did complete successfully. The alarms are showing because the datapoints are not registering correctly and such the min and max are setting off the alarms. Some devices are working while others are not. Seems to be about half of the devices are working. I have little Lookout experience. I have enough knowledge to put up a Lookout PC and move the data/files. The last move went okay but this one has been difficult at best. Luckily I still have the "old" setup working and can fall back when the attempts to get the new one does not work successfully.I have found the proper way to edit the data points individually but this would be very tedious and prone to errors. I would like to think there is some connetion that has not converted to the new version and I need to find and fix that connection, but again I don't have the required knowledge for that.
Your thoughts?
Thank you for your reply.
Lynn

Lookout Upgrade Compatibility

We just received Lookout 5.1. Our dedicated SCADA computer is an older machine, using Windows 95 and running Lookout 4.5.1 (build 19). Is there going to be a problem if I install the upgrade onto this Windows 95 machine?

There should not be any problem to use Lookout 5.1 on Windows 95. However, I think National Instruments obsolete support for Windows 95, therefore you should consider to upgrade your OS as well (asap).
I highly recommend to use at least Windows 2000 or XP (or XP Home Edition) to build up a SCADA/HMI system.
The Lookout 5.1 installer installes per default into an new NI\Lookout 5.1 folder. Don't forget to copy over all the .ini files you have in your Lookout 4.5.1 folder to keep the settings/behavior.
Hope this helps
Roland

Problem upgrading to Lookout 6.6

I have a Lookout application running in an older version and I'm trying to upgrade it to 6.6 because I ran out of I/O. When I open the lks file get a Compile Failed error, with the following messages: "...1417: error: Class not found: GE_Series90", and "...18: error: Object is not defined PLC_GE1". What is the problem?

I had no issue opening a 5.1 process with the GE object on 6.2. I have attached a simple process, driver with nothing connected.
Lookout 6.2 (Latest version I use):
GE1 = new GE_Series90 ("90-30", "", 8, 4, 5, 500, "COM1", 19200, "odd", 0, 8, , "SNPX");
Lookout 5.1:
GE1 = new GE_Series90 ("90-30", "", 8, 4, 5, 500, "COM1", 19200, "odd", 0, 8, , "SNPX");
Forshock - Consult.Develop.Solve.
Attachments:
ge test 51.lks ‏2 KB

What are the steps involved in upgrading a lookout 4.0 application to the newest version 6.2??

I have an application of Lookout 4.0 running and the customer has asked for a spare HMI. What is the easiest way to get them what they are asking for? Can I buy a PC with NT loaded and purchase another runtime application of the Lookout runtime software? Is it buying another PC with XP/Vista and upgrading the development software as well as the application and the runtime software. What would be the best?

Download the latest evaluation of Lookout and test it the process files.
This will let you you know what to expect.
Mike
Mike Crabtree - Lead Developer
Destek of Nevada, Inc. / Digital Telemetry Systems, Inc.
(866) 964-6948 / (760) 247-9512

Upgrade issues for Lookout v3.8 to 6

I am going to upgrading Lookout from version 3.8 on a stand alone win 98 pc, to Lookout 6, a client / server enviroment, hopefully using win 2003. Are there any particular hardware requirements, and will Lookout 6 run on Win 2003 server?
Any other notes of interest, for my upgrade would be appreciated.

Hi,
I agree with what others have said thus far, and although NI never throws in support for servers, so far I have never had an issue with Lookout running on NT 4.0 Server, Windows 2000 Server, or Windows 2003 Server Standard Edition.
There are some major consideration to get your new Lookout up and running. Please read and compare the Lookout Developers Manual for your new and old versions to study some of these issues. A little planning will go a long way.
The 3.8 method of efficient remote data retrieval was through DDE and not TCP/IP. DDE was much more efficient for low bandwidth (or even high bandwidth for that matter). Hypertrends with DDE links on remote clients in 3.8 stored their own database to display the trends, so you could not maintain a contigious history without running the client all the time. DDE had its issues when clients outside local subnets were necessary, so TCP/IP had to be the future. All new hypertrends use URL's for their link and Symlinks provide a two-click change of addresses for an entire process of object links, instead of changing each individual object link.
I had to revamp all my processes to get things running smoothly. The advantage with the new Hypertrend/Symlink combo is that the data display is always from the server citadel database so you have contigious history available at the client. They have improved some early performance issues with hypertrend updates and screen writing, but I would not expect to run hypertrends with constanly changing data on a dialup line....broadband only. If you run multiple traces in remote machine hypertrend objects/displays, I would NOT upgrade to Lookout 6.0 at this time. Lookout 5.1 is much better for this. I think Lookout 6 and the new citadel have several months of grin-and-bear-it development and bug fixing before it is worthy of its calling.
Notice major changes in server/client process ideal configuration and programming methods. The way the clients should be developed has totally changed since Lookout 3.8. Save all your lookout 3.8 stuff including lookout.ini, lookout.sec etc. You will have to import your security files and convert to new versions which now get stored in system32 directory of windows. They get overwritten along with lookout.ini if you reinstall or repair the newer versions so make backups anytime you mess with the installer. Start with a clean install and one at a time, import your old .lks files and recompile. Then save all. Now you can go through the new .lks files and clean up issues. You will have to do some major search and replaces on the old client .lks to work well with new server processes. The server processes will need work too, because you will be deleting all the graphic objects and eliminating any user interface. Only the clients processes which link to the server for their displays, should need graphics and user interface.
Running out of time..that's all for now..
Cheers,
Ed
Message Edited by erblock on 08-24-2005 05:35 PM

How difficult would it be to upgrade from Lookout 5.1 to 6.5?

Hello, I was told that Lookout 6.5 works with Windows 7. Before I purchase 6.5 I need to know how difficult it will be to move from 5.1 to 6.5. Has anyone done this move? If I am going to have to redraw, or do numerous changes to the Database then I won't do it and I'll start from scratch with Cimplicity or ClearSCADA.
Thanks.
SCADA Programmer at the Coachella Valley Water District.

We use a custom SCADA designed by SCIPAR out of Buffalo New York. We've had a SCADA System here for about 28 Years. I have small standalone SCADA Systems running Lookout.
Another Question, because I can't get the Database Converted for one of my systems, I'm wondering if it is ever needed. This is a small system and the operator's use Trending and Alarm Functions but they never look at historical archives. I do have the Object Members set up to Log, is that needed for Trending to function? I wonder if I can get by without the conversion since it doesn't look like I'm ever going to get it to work.
SCADA Programmer at the Coachella Valley Water District.

Two processes running at the same time in Lookout

I have installed Lookout 5.0 with 200 I/O Points onto our server computer. The application of motion control is next to the 200 I/O points through OPC PMAC server/client. Now I would like to have a second process in the same server for trouble shooting and testing without stopping the motion control process. However, this second testing process could have also many I/O points through Serial and USB ports. I assume that the total amount of I/O points of both processes will be greater than 200.I prefer to have independent processes for control and testing because access levels. Can I have these two processes running at the same time when needed?

Hi,
From your description you are using a third party OPC server for the motion application. You could have a second Lookout process communicating with the same OPC server with no problems, as long as you do not exceed the number of I/O points your license supports.
Also, the process you are using for testing obviously could not overwrite datamembers (or registers if you will) that would interfere in the overall application, in other words you can test your application as long as you keep the coherency of the test.
So the answer would be, yes it is possible, however you are still limited to the number of I/O's your license supports... You may even consider upgrade the number of I/O's you have in your license.
Best Regards
Andre Oliveira

Iphoto on ipad no longer sees my photostream since IOS 7 upgrade

iPhoto on my ipad no longer sees my photostream in the albums page of the iPhoto app since IOS 7 upgrade??
I can see my photostream and shared photostreams in the ordinary Apple photo app on the iPad. Prior to IOS 7, all these photostreams were visible in the iPhoto app's albums page. What has changed? Its' most annoying as I was relying on my photostream in the iPhoto app as my source of photos for my journals.
Any suggestions please???

I've just had a long chat with Applecare in Colorado. Very helpful they were.
I can confirm that the "new" IOS 7 version of iPhoto app on all IOS devises does not support your my photostream nor any of your pre IOS 7 upgrade shared photostreams.
Any new post IOS 7 upgrade shared photostreams will be visible in the iphoto app. I have tested it and it works fine. But all your pre IOS 7 shared photostreams and existing my photostream remain invisible to post IOS 7 iPhoto app.
This "improvement" to iPhoto on IOS devises is now a lame duck. Why ! I'm now on the lookout for a better photo journalling app for my iPad.

Upgrade from 9.2.0.2 to 9.2.0.3 to 9.3.1

Hello. We are upgrading our Essbase/BI environment from 9.2.0.2 to 9.3.1 so that we can take advantage of a few key improvements in BI and the essbase kernel (ASO data slices, BSO selective exports). We have run into a bug that the BI+ repository cannot be upgraded to 9.2.0.3. Our only choice it seems is to export all our objects, perform a clean install, and import one by one and rebuild the structures.
Has anyone done this upgrade before and do you have any workarounds for our problem? Do you know of any other problems with this upgrade path that we should be on the lookout for?
Thanks

Hi,
If I understand your issue correctly, this is not a bug. It is not possible to restore a BI+ repository. You will get an "Invalid schema" error or similar in the config utility. There used to be a document to twick the tables to restore early system 9 repositories but I m not sure this document would still work for 9.2.0.3 or 9.3.1.
You will need to use the migration utility to migrate all your artifacts. It works pretty well. If upgrading to 9.3.1 you can also use the Life Cycle Management (LCM) utility available from the e-delivery website.
If you havent got many objects in your repository, you may want to export them all (you can only export 1 object at a time until 9.3.1). You can for example export 10 FR reports. Then zip them all up into 1 file and import the zip file in your new repository. You will need to recreate the datasource connections for these reports in the new environment if they do not already exist.
This may not apply if you got your issue wrong...
Seb

Problem with Lookout 6.5 tag sharing

This is a WHOPPER, although a weird one...
I have one grad student grabing shared variables from my Lookout server processes for inclusion in his LabVIEW implementation.
After I upgraded the server's Lookout to 6.5, he reported problems reading values from one of the four processes running on my server.
1. Oddly enough, he had no problem displaying the tags in Max or in Activex Hypertrend within his LabVIEW executable, but he could not map the variables to his shared variables and thus he could not display them or include them in his Citadel.
2. Using Tag Monitor, all the values from the "troubled" process on my Lookout server, come up as "access denied".
3. Using Tag Monitor on the Lookout server (while all four processes were running in Lookout), I had the same results...."access denied".
4. All Lookout clients (both 6.5 and 6.2) have no problems accessing the troubled process tags both by expression and Lookout Hypertrend.
The troubled process, has the last alphabetical process name and the last alphabetical file name. All four processes are loaded using the startup settings in Lookout.ini. Lookout runs as a service on WIndows 2008 x86 Hyper-V virtual machine.
Because the processes are all production, I have not yet been able to mess with process names and loading order to possibly elaborate on the symptom.
It is "maybe" and issue that Lookout 6.5 can't properly share out (via shared variable engine) variables from more than 3 processes at a time???
Please advise ASAP.
Ed

The access denied error is more like a security issue. In Lookout Object Explorer, right click on process, and select Configure Network Security. If I give Everyone "No Access", or I just remove any permissions, I will get the access denied error in Tag Monitor.
Actually Lookout has no limitation on the number of exported processes or tags. All the tags in each process are the tags in Logos Server. The LabVIEW access these tags by Logos protocol. If Lookout set the security, and the LabVIEW doesn't have enough access level, it will get access denied error. For example, lookout gives no access to the process.
You can configure the Network Security for process, as well as any objects. By default, Everyone has Read&Write permission.
Ryan Shi
National Instruments

Lookout 5.1 & 6.1 locking up

During last two weeks, lookout Ver 5.1 which has been running without problems for a couple of years started locking up with out warning usually around midnight or shortly after.
Attempted all recommended fixes that I could find from the website and forum and even moved it to a new computer but problem is still occuring.
Upgraded to 6.1 and problems still exists. After approx 5 mins of
runtime, lookout.exe drives CPU to 50% (dual core processor), the menu bar on the
screen disappears and the system locks.
Have to reboot computer to get back system.
Running brand new computer with Win XP Pro SP3.
Need some help quickly!!!
Runing AVG FREE antivirus - nothing found with any scan.

First, you need to check if Lookout reads the good value from PLC. If the communication stops or the data has bad quality, Lookout won't log and no data on Hypertrend. So, make sure the communication to PLC is good and data is good during the period when hypertrend shows nothing. For example, if PLC1.data1 stops updating on Hypertrend, check if PLC1.data1 stops updating or red X on it. Also notice if there are any alarms during that time.
Then, go to MAX to see if the data is logged into Citadel. In MAX, create View to display the trend. Check if the data is there or not. If the data is logged, the problem is in Hypertrend. But if there are no trend either in MAX during the gap, it means the logging has problem.
After you create the View, you can "Export to Text". Refer to the attached pic. In the txt file, there are the raw data from Citadel. If there is no data logged during a certain period, you will see the blank in data column.
For example,
183 9:58:26.316 AM 123
184 9:59:37.490 AM
185 9:59:37.490 AM 123
This means from 9:58:26.316 to 9:59:37.490, there is no data logged.
So, we need to check if the data from PLC is good and if the data is logged.
Ryan Shi
National Instruments
Attachments:
untitled6.JPG ‏95 KB

Lookout 4.5 Upgrade

Similar Messages

Maybe you are looking for