Lookout 6.2 Bugs

I found a couple of small bugs in the DataTable object.
1. Whenever you first "Edit Data Member Configuration" of a new DataTable object, the default data member is logical. That is ok, but when you change the pulldown type to numeric, the display does not expand to show historical, filter and alarm options as it should. You need to quit the configuration and re-enter to get the proper setup and options for numeric data members.
2. The DataTable allows import of bad "Alias" fields. I had a few fields in several hundred that were imported with a space at the end of the alias name. They all imported just fine. The problem comes when you want to edit or delete those bad entries...you CAN'T do it interactively. More importantly, you can't make a connection to these bad entries, so my guess is that although they exist in your display, they are likely totally non-funtional! The only way to remove the bad data members is to import a "delete" entry with the same alias field error.
Ed
Message Edited by erblock on 01-14-2009 05:04 PM

Ryan,
Lookout 6.1 command window test:
1. Edit default.lks object "Pb1" name to "Pb0" and save file.
2. Run cbl.exe to attemp compile: See copied command window history below in blue.
C:\Program Files\National Instruments\Lookout 6.1>cbl default.lks default.
l4p
Lookout Process File Compiler Version 6.1 (build 3)
Copyright National Instruments 1992-2007 All rights reserved.
default.lks
default.lks(53): error: Object is not defined: Pb1
C:\Program Files\National Instruments\Lookout 6.1>
3. cbl.err file is NOT written to file and error IS listed in command window.
Additionally, I tried this on Lookout 6.2 (cbl build 49153) on a different machine than the machine used to originally report this issue and it gives nearly the same results in blue below.
C:\Program Files\National Instruments\Lookout 6.2>cbl default.lks default.l4p
Lookout Process File Compiler Version 6.2 (build 49153)
Copyright National Instruments 1992-2008 All rights reserved.
default.lks
default.lks(239): error: Object is not defined: Pb1
C:\Program Files\National Instruments\Lookout 6.2>
Ironically, the above behaviors are as expected, and contradict both my original issue and your last post.
Now I am officially confused!
Ed

Similar Messages

Height of row in hw_ila changes

From time to time I encounter this problem in Vivado 2015.1 and 2015.2, without a clear cause.
The height of the row "Name" gets smaller (or the font gets smaller), leading to the "Name" column not being aligned anymore with the "Value" colum or the displayed data.
I have not found out how to reverse this, except for restarting Vivado.
I added this as a question in another thread, but did not get any answer to it there.

Hello Vinay,
as I said, I see this behaviour "from time to time", not often enough to track down the issue, and not to be reproducable by any steps I tried to take.
I saw it happening with 5anything from 4 to 45 signals in the waveform viewer.
Unfortunately I can not give you any more input on this, but maybe your programmers can take the hint and be on the lookout for a bug in the source.
Best regards
Johannes

Connection for panel stops working

I activate a panel from several pushbuttons by setting Panel.activate=Pb1 or Pb2 or Pb3 or ...
This seems to work until I close the process and then open it again - the panel will not activate. When I rebuild the above statement from scratch, it works again? What am I doing wrong? Is this a Lookout (5.1) bug?

Sometimes Lookout "forgets" things it's supposed to do when done through expressions. The proper way to do this would be to (in object explorer), right click your panel and go to edit connections. Select the activate data member (I prefer to use the maximize data member instead), and make your connection "pb1 or pb2 or pb3" then click accept and you are in business.

Lookout 6.1 Edit Mode Bug

I don't remember seeing this in older versions of Lookout, but in 6.1:
Edit mode allows you to open a second session of object editing. It used to be you had to close an open object edit (connections, data member configuration, etc) before opening another.
Well in 6.1, it will let you open a second one....and Lookout will always crash after you close them and save the process (sometimes it will crash before you try to save).
Ed

Ryan,
Windows XP SP2 32-bit, fully updated. Dell Precision 690 with single Xenon 5160 dual core @ 3.0GHz
I sent you an email with more details....
I have not restored to original release 6.1 only. I will progress the entire upgrade path scenario when I have time to reload the machine in question and I'll test each phase.
Ed
Message Edited by erblock on 03-31-2008 01:38 AM

IOS 5.1 Bug Found!

Just updated to ios 5.1 on an iPhone 3GS and found a bug, when removing apps from folders, the second to the last app removed will crash the springboard, and respring... why!? im not sure why but is it comon for iphones to respring? even when they are not jailbroken? ive done a clean restore from ios 5.0.1 to ios 5.1 there should be nothing there to cause a springboard restart.. right? or is this a way of the iphone protecting itself? (like safe mode for example) but thats not fair for me, what of i was in the middle of a serious situation and my iPhone crashes into a respring? im trying to record a number, or a note, or even make a phone call, will i have an issue with resprings all the time or is this a once in a lifetime thing? im actually concerned. tho absolutlly thankfull for the battery fix, it has proved its self worthy. please let me know what you think, will apple release a fix for the crash?

Hi there,
I can't seem to recreate this issue myself, but please report it to Apple here: apple.com/feedback, they are always on the lookout for bugs which they can fix.
Remember to include a detailed description of the error, including a step by step process on how to recreate.
If you have any other questions, do ask, if not, have a great day,
Nathan

Bug in SQL Developer 1.5 SQL Worksheet

Hello,
did any of you already encounter the following effect in version 1.5's SQL Worksheet?
When I try to execute the following statement in version 1.5:
select (1 +
2 -
3 +
4)
from dual;
I get the error: ORA-00907 missing right parenthesis
With more complex statements I also get an 'unimplemented feature' error.
When I put the operators in front like this:
select (1
+ 2
- 3
+ 4)
from dual;
i get the correct answer '4' as result. Seems to be clearly a bug for me. In version 1.2 both versions work perfectly well.
Does anyone know whether there's already some bug filed for this or whether there's a patch around?
Regards Holger

Hi Dieter W.
It looks like the command does work in sqlplus , from what I can see only the first line (and continued first line) has continuation character facility. (I am working on an other related SQLDeveloper bug).
i.e. No continuation character (10.2XE)
SQL> select (1 +
2 -
3 +
4)
from dual;
2 3 4 5
(1+2-3+4)
4
Continuation character:
SQL> select (1 -
1 -
1 -
3)
from dual
2 3 select (1 1 1 3)*
ERROR at line 1:
ORA-00907: missing right parenthesis
I am on the lookout for more information...
-Turloch

Lookout 4.5.1 slow

Over the past several days, Lookout 4.5.1 (build 19) started to run very slow. The PC is running fine, any application I open runs normal. Lookout is running about 1/3 to 1/4 speed. It's not using any processor time, and the drive isn't full. Inputs (external pushbuttons) have to be held 3 - 4 times longer to take affect. The process are running, but are slow also. I tried closing the server / client and open the LKS files, but they run the same way. This PC has been running flawless for 8+ yrs with no monitor, KB, or mouse, so there are no bugs to contend with. Any ideas would be helpful. Thanks, Mark

Memory usage for lookout.exe, lkcitdl.exe
CPU Usage seems fine. I have had issues where the process slow to a crawl when Citadel was loading the database. Even citadel 5 slows down a bit.
Guess we need Ryan in here
Mike
Mike Crabtree - Lead Developer
Destek of Nevada, Inc. / Digital Telemetry Systems, Inc.
(866) 964-6948 / (760) 247-9512

LR Preferences - Data Entry Bug?

Can anyone supply me with a list, or cite to a list, of preferences in the file "com.adobe.Lightroom2.plist?" I am asking this because no one answered my question about the space bar zoom toggle problem I get from time to time. It stops working every once in a while and I think it happens when I've inadvertently typed a letter that shuts off this function when entering a City or Country name in the Metatdata and the text box de-selects unexpectedly (allowing the letters I'm typing to be used to trigger commands rather than enter text). It starts working again when I substitute my most recently saved backup Preferences file, leading me to believe that I've somehow changed a preference by whatever letters I've entered (not illogical, but not proven). Since I usually don't notice this for a while, I'm not sure what names I've typed so I can't figure out what letters were entered. This is not a biggie but is annoying though it has the side benefit of making me learn things about LR I have chosen to ignore in the past. Another question is whether the de-selection of the City or Country field while I'm typing is a bug or just a way to make me use the accumulated names pop up I've previously entered in these fields with LR presuming this is a good shortcut? iMac 24;3.06 ghz;Snow Leopard.

Hi,
R&D has researched this issue with the pot object. They have edited the pot object to try to fix this problem. So I will post the fixed pot CBX file on our FTP site. We would like it if you could please test this with your applications and ensure that it works okay. If it does work, then we will integrate this new pot CBX in our next fix.
So its absolutely imperative that we get feedback from you on this fix and whether it works well.
To get this fix, go to:
ftp://ftp.ni.com/outgoing and download the file called pot.cbx. Then copy this file to "C:\Program Files\National Instruments\Lookout 6.0". The last part may be different based on your version of Lookout. NOTE: Backup the existing pot.cbx file to another folder in case you need to revert back. This fix has been created for the latest Lookout version (v6.0), but I have tested it successfully in v5.1 and v6.0. We always implement fixes on the latest version of our software, but I think it should work with your version too.
Once this new pot.cbx has been verified by you, we will implement it in our fix. I would recommend re-downloading the fix when it releases. This is why I'm placing the pot.cbx file in the FTP site as a temporary download location.
Thank you for all your help!
Anu Saha
Academic Product Marketing Engineer
National Instruments

Having trouble converting lookout 4.5.1 database to lookout 6.1

I am trying to import my Citadel 4? database (Lookout v4.5.1) to Citadel 5 so that I can use the historical data viewer in Lookout 6.1 to export some of the data to a spreadsheet. When I tried to create a new database in MAX and chose "Convert Citadel 4 Database to Citadel 5," the older database file is not recognized. I then navigate to the database location manually and get the following error "There are no Citadel 4 databases to convert."
Any ideas? I've tried converting the database on machines running Windows XP and Windows 2000 running Lookout 6.1. Do I need to do an interim conversion with Lookout 5?
I don't think the database is corrupt because I am currently able to log and view it in Lookout v4.5.1.
Also, How can I verify that my database is v4?

This is a know bug. After you install Lookout 6.1, you may not be able to create Citadel 4 database. We will give out a fix.
For now, please unzip the attached file and copy to <National Instruments>\MAX\UI Providers. Then you will be able to create/attach the old Citadel 4 database, and convert it.
Ryan Shi
National Instruments
Attachments:
niCitadelUI.zip ‏414 KB

Lookout 6.6 - No Trends On 6.6 Client or NIMax

Today I upgraded my Lookout computer running my server process file from 6.5 to 6.6. I then upgraded one other computer running development version (which is also the backup to the server) to 6.6 from 6.5. Now, I am unable to get trends from the server on this machine when i open any of my client files. And, when I go to Max and try to access the database on the server machine (PRIMARY1) by clicking on the + sign next to the 6.6 database, it will not expand. (see attachment)
However, on my laptop that is runnning the development version of 6.5 I have trends on my process files and can access the database on the server from NIMax. Also, I can open these client files on my server computer and I get trends as well.
I have the firewall turned off on all machines and all 3 machines are running Windows 7 SP1.
Any ideas would be appreciated.
Thanks
Jason Phillips
Attachments:
NIMax pic.jpg ‏147 KB

Since I am not getting any responses from NI related to my earlier posts, can someone from NI just tell me when installing Lookout on a computer running Windows 7 are there any guidelines as far as disbaling/enabling certain things in windows 7 (other than the firewall).
I am still having the issue with my clients all being disconnected from my server at random times, and when I restart my server process file I get a "process registration failed" error if I do not stop the lkads service before restarting the server file. I can duplicate this problem over and over again. I have done repair install and full reinstalls - problem still exists. I changed my server computer - problem still exists. All I can figure is bug in Lookout 6.5/6.6 or Windows 7 issue.
I cannot go back to Windows XP so this problem needs to be solved. Any immediate help from NI would be appreciated.
Thank you.
Jason Phillips

Lookout locks up upon startup

Hi and Happy Holidays
I have just changed computers (upgrade) from older computer running windows xp home to newer computer with windows xp pro. I am using the same version of lookout with same process file. When the computer starts up from boot up and launchs lookout it freezes and goes into a state that only ctrr-alt-delete can be used to dump lookout program. Since the process uses OPC client, my first thought is serial port conflict with RS Linx. I also notice that in the earlier computer RS Linx had to be running in back ground before process would work correctly. Lookout for some reason starts OPC client automatically. This may be causing some problem as well.
If I disconnect the serial cable and allow lookout to fully load and wait for the missing serial cable alarm in lookout, then reconnect the serial cable the process works normal as long as the computer is up and running.
Info windows XP pro, Service Pack 2, Lookout 6.01 build 1, RS Linx 2.30.02 build 79
RS232 cable is connected to 1747-pic adapter to SLC503
I sorry if this has been discussed before, I did not see any recent activity.
Thanks Dan

I suggest you to upgrade toLookout 6.0.2 and its updates
It has fixed some OPC client's bugs.
Message Edited by Support on 02-04-2009 04:46 PM
Ryan Shi
National Instruments

1.-Se me perdió el CD de Lookout para Win 32 version 5.0 (build 7) (Adjunto

1.-Se me perdió el CD de Lookout para Win 32 version 5.0 (build 7) (Adjunto
archivo) y el manual del curso.
¿Cómo puedo conseguir ambas cosas:una copia nueva (Un CD) de esta versión
de Lookout y el manual?.
Alguna persona del foro puede enviarme una copia??

>
Error in: gllchd
Function return status: 0
Function Err Message: Executing hd_prep
Function warning number: -1
sqlcaid: sqlabc: 0 sqlcode: -1422 sqlerrml: 70
sqlerrmc:
ORA-01422: la recuperación exacta devuelve un número mayor de filas qu
sqlerrp: sqlerrd: 0 0 0 12 0 538976288
sqlwarn: sqltext:
>
Pl post details of OS, database and EBS versions. This may possibly be a bug - has an SR been opened. Two similar errors listed below are fixed via patches
R12: When Uploading STAT Data get ORA-01458: Invalid Length Inside Variable Character String (Doc ID 603053.1)
Journal Import Fails With Error: Ora-1400 : Cannot Insert Null and SHRD0105 (Doc ID 300393.1)
HTH
Srini

Lookout's Modbus Slave Address

Hi,
It appears that the Modbus Slave (Ethernet) Object in Lookout (6.0.1) doesn't work with an Address (or "Identifier") greater than 127.
I tried a simple test with the Modbus Object in one process with an address of 128. And a ModbusSlave Object in another process with its address as 128. There's no communication. However, when I make the addresses 127 (or lower), they yak like nobody's business!
I haven't tested the Serial version though.
Est-ce un bug?
-Khalid

Hi Khalid,
I think I was overlooking the Lookout 6.01 version that you mentioned earlier in your post ! I was able to recreate the issue that you are facing if I create a modbus slave object in Lookout 6.01 version. Thats a bug! And version 6.02 has a fix for it!
Have a great day!
Regards,
Prashanth

Lookout .WMF Graphics & Print Panel

Bug???
Lookout 6.1: In addition to graphic object layering display problems in panels, detailed WMF graphic objects to not print close to properly when "Print Panel" action is used. I have some maps, and no matter whether they are arranged in front or back of other display objects on the panel, only a few remnants of the maps actually print.

Actually, I was too quick to report this one.... I've been testing from home a lot lately and it was a cheesy, older laser home printer that does not do well with the detailed WMF files. Our better printers at work had no problems.
On screen issues persist on even the best/latest video cards, however.
See: http://forums.ni.com/ni/board/message?board.id=190&view=by_date_ascending&message.id=5348#M5348
I'd really like to see that fixed! Related to this... even pop-up windows positioned over or dragged across over a panel with a WMF image, render the WMF image missing lots of information. It takes a manual refresh to get the underlying image back to normal.
Cheers...
Message Edited by erblock on 03-10-2008 02:04 PM
Message Edited by erblock on 03-10-2008 02:07 PM

Lookout displays wrong graphics

Lookout 4.5.1 (18 & 19) sometimes
displays wrong graphics upon
opening a process.
For example it can display 'knifeup'
instead of cumstom .bmp or standard
switches pictures instead of custom
ones, etc.
At the same time .lks is OK.
I have Win98 system running on HP Omnibook XE3
Notebook.
Did anyone experienced the same
unpredictable Lookout behavior?
Sergei

Tommy,
Obviously you got the NI advise on
not using nested aggregates at the
time they were investigating the problem.
Meantime I got a couple of similar replies
from NI as well.
Finally when I asked them to tell me if I can
expect the fix in near future (my project was
at high risk because I noticed the bug too late),
they sent me lkworks.dll for testing.
It all works fine now. I must admit that
NI 'saved' our project (we successfully launched it
at our plant last week).
I can send you the fix so you could test
it with your project. It would be interesting
to compare our results.
Please let me have your email so I could
send you the file.
Best regards,
Sergei
tommy_scharmann wrote:
> Sergi,
>
> I would like to know who you spoke with at
NI. It was very clearly
> told to me via the NI help line that nested aggregates are not to be
> used with Lookout and that if you use nested aggregates you will get
> unexpected behaviors. Unexpected behaviors included the graphics
> issues, amongst other things, that were not made clear to me. I was
> explicitly told that the help file mention of nested aggregates is
> erroneous!
>
> Please help me to get to the bottom of this issue.
>
> Regards,
> Tommy Scharmann
>

Lookout 6.2 Bugs

Similar Messages

Maybe you are looking for