Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

Lookout project file loading error

Solved!
Go to solution

Hi folks,

 

I've got this problem.

I migrate a project to Lookout 6.1 to Lookout 6.5 opening the .lks file an generating the .l4p file.

I made lots of modification using the symbolic link objects with the dynamical option to point to communication objects data members (OPC client objects) and to internal object (Data table ojects data members).

Usually, after lots of modification, I reopen a project using .lks file to recompile it.

Now rises the problem.

If I load the  lks file, lookout compile the source file without errors, but when it load the process file it goes in error after a little while and the usual error windows appears. In the event viewer I find this information:

 

Event Type:    Error
Event Source:    Application Error
Event Category:    None
Event ID:    1000
Date:        27/05/2011
Time:        15.25.40
User:        N/A
Computer:    VM-TEST-AB
Description:
Faulting application lookout.exe, version 6.5.0.49153, faulting module unknown, version 0.0.0.0, fault address 0x00005f6f.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 6c 6f 6f   ure  loo
0018: 6b 6f 75 74 2e 65 78 65   kout.exe
0020: 20 36 2e 35 2e 30 2e 34    6.5.0.4
0028: 39 31 35 33 20 69 6e 20   9153 in 
0030: 75 6e 6b 6e 6f 77 6e 20   unknown 
0038: 30 2e 30 2e 30 2e 30 20   0.0.0.0 
0040: 61 74 20 6f 66 66 73 65   at offse
0048: 74 20 30 30 30 30 35 66   t 00005f
0050: 36 66 0d 0a               6f..  

 

If I load the process file .l4p, the project are correctly loaded and run.

I try to compile manually the source project using cbl. After, when I load the .l4p file, the error rises.

 

I check the symbolic links and It seems they are correct. I defined data members to point to obviate to point to a non existing object. In this way, the symbolic links always point to existing objects.

 

Any ideas?

 

Thanks to all

 

Mario Fanelli

 

0 Kudos
Message 1 of 12
(7,545 Views)

Please upload your process to ftp://ftp.ni.com/incoming

 

If there are any client process, please also give us the client process file.

 

If we cannot reproduce the crash with your files, we will need you to generate the memory dump.

Ryan Shi
National Instruments
0 Kudos
Message 2 of 12
(7,537 Views)
Hi Ryan, I download the project in your ftp. It's in the 1118NI.rar file. I developed the project under a VirtualBox WinXP sp3 virtual machine running on Ubuntu 9.10, but I've had the same problem on a real WinXP sp3 OS running on another PC. Bye, Mario Fanelli
0 Kudos
Message 3 of 12
(7,532 Views)
Hi Ryan I forgot an information. For the communication with the field, I use RSLinx 2.57.00 CPR9 SR3 from Rockwell.
0 Kudos
Message 4 of 12
(7,531 Views)

There are several problems in the process.

 

1. line 142549

I see "MOTORE PRINCIPALE >> C macchina >> Scalatura an velocit?, 0,

The string doesn't end with quote. It will cause the crash in compiling.

It's probably because this title name of the panel is too long.

 

2. line 18032

 "stampi_lubrificazione_centralina_anteriore_T_ritardo_iniziale_BC_alto_catena_ugello_01"

This is an alias name of datatable cell. The name has more than 80 characters, but we cannot handle more than 64 characters correctly. It's a bug in lookout.

The difficulty is that there are a lot of such kind of long alias name. I'm not sure if it's easy for you to make all of them shorter.

Another way is to modify the lookout code by us. If you need it, I can make a temporary fix for you.

 

 

 

Ryan Shi
National Instruments
0 Kudos
Message 5 of 12
(7,508 Views)

This is due to lookout crash sometimes happened when you try to save the project after:

- moving a panel to a path to another inside the process;

- deleting all the object on a panel;

- create a new panel and copy the object fron another panel to this one.

 

In the first project these links are correct defined.

 

What kind of problems rises when I use a symbolic name for an object if the name is too long?

 

Mario Fanelli

 

NB: Excuse me if my answer is a little late from your reply (I was in holiday)

 

 

0 Kudos
Message 6 of 12
(7,473 Views)

The crash happens on the long name of datatable cell's alias name.

 

In most other cases, the long name doesn't matter. The implementation in the datatable has problem which has the 64 characters limit but allows user inputing more.

Ryan Shi
National Instruments
0 Kudos
Message 7 of 12
(7,470 Views)

The prolem with the lomg name is only for the object's data members or is for the object's name too?

0 Kudos
Message 8 of 12
(7,466 Views)

It's only for datatable object's data member.

Ryan Shi
National Instruments
0 Kudos
Message 9 of 12
(7,455 Views)

Now I rename all the data member names too long into one short. It's a long work. In the projects made under lookout 6.1 I had no problems with recompile and load using the data members names too long. Could be possible that a dynamic symbolic link causes a crash during the loading after the compiling phase? How the dynamic symbolic links are generated when a project starts? I have found a strange mode of operation about the dynamic symbolic links (an example is attached). When you define a symbolic link, you can generate an expression dragging the symbolic link on a panel (in the example is the expression in the high left side of the panel). When you reload the project, go into edit mode operation and try to drag a new expression with the symbolic link, you can't define it. It seems a dongle symbolic link. Only if you rewrite the expression inside the symbolic link, you can drag the new expression. Anyway, the symbolic link works correctly.

 

Mario Fanelli

0 Kudos
Message 10 of 12
(7,450 Views)