Process file generated with Lookout 6.5 CBL compiler not retaining the variable last values

[Lookout Controller]

we have lookout 5.1 integrator license and we are doing all the modifications with this license. now we had purchased the lookout 6.5 run time server only. We want to use the CBL compiler to compile lookout 5.1 file to get the lookout6.5 file. we are able to convert the file with the CBL compiler and generated the l4p, L4t & LKA file also. there is no error in the error file generated by the CBL compiler. but we are not able to retain the value in the lookout 6.5 file and all the values are switched to default while restarting the process file. please suggest the solution to get reatined last values in this case.

[Ryan.S]

The cbl just compiles the .lks file and gerenate a default l4t file. You can try to copy the old .l4t file to overwrite the one generated by cbl. To use the old version l4t file directly is not a suggested practice, but it probably works.

[Lookout Controller]

By placing the old .l4t also it is not able to store the changes. please suggest. 

[Ryan.S]

Can you upload the 6.5 process file and the 5.1 l4t file to ftp://ftp.ni.com/incoming?

[Lookout Controller]

pls find the files at ftp://ftp.ni.com/incoming with the name process file.zip.

[Ryan.S]

The process files.zip contains two files, batch2.l4p and batch2.l4t. They seem to be the lookout examples... I open the l4p file in 6.5 and it loads the status from l4t well.

[Lookout Controller]

yes these are the lookout example file. it upload the values from the L4T but any changes made during the running of the process are resetes to the initial values after restart of lookout process.

[Lookout Controller]

dear Ryan,

waiting for the resolution of the said issue.

[Ryan.S]

I find a solution.

The problem is the database parameters in .lks file. Before you use cbl to compile the 5.1 .lks file, open it by notepad, you see

#dbasecomputer "xxxx"
#dbasepath "xxx"

You need to add two lines

#dbasename "xxxx"
#dbaselifespan "365.000000"

The database path and the database name can be the one configured in MAX, or it can be a new database with any name.

Without these two lines, the compiled .l4p file has the database name missing. When you open it, lookout will think of it as an error, then it will switch to the default database. But if anything is changed, it is a new process. A new process cannot be saved in Runtime only software, that's why the state file will not be saved after you close the process.

If your .lks file uses the default database, the codes look like below

#dbasecomputer "<default>"
#dbasepath "<default>"
#dbasename "<default>"
#dbaselifespan "365.000000"

[Lookout Controller · Accepted solution]

Thanks for the solution.