Subscribe: Lookout
http://forums.ni.com/rss/board?board.id=190
Added By: Feedage Forager Feedage Grade B rated
Language: English
Tags:
client  error invalid  error  invalid object  lks  lookout  object pathname  object  problem  process  running  server  version 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Lookout

Lookout topics



Lookout topics



Published: Fri, 24 Nov 2017 19:10:03 GMT2017-11-24T19:10:03Z

 



Lookout feezing when com ports become unavailable

Tue, 07 Nov 2017 22:32:06 GMT2017-11-07T22:32:06Z

Hello,

I am running Lookout v6.7.1.

 

lookout is controlling 30 temperature controllers on 8 virtual com ports using Modbus. When the power to the temperature controllers is lost there are many alarms that are causing lookout to freeze. I have used a monitor function block to unload the process in this event, but I cannot figure out how to have it automatically re-load the process when the power returns, as the monitor function can no longer see the Modbus function (that process has been unloaded).

Is there another way to prevent lookout from freezing if there are too many alarms?

 

Thanks




PLAYWAVE

Sun, 29 Oct 2017 22:39:10 GMT2017-10-29T22:39:10Z

I have a strange problem that I can not seem to figure out. We are using National Instruments Lookout for WIN32 Version 6.7.1 Build 49152. We have always used Playwaves to play recorded DTMF tones to dial telephone numbers. The problem is that Lookout will only play certain DTMF wave files! The computer plays all of the recorded DTMF wave files with no problem. Windows Media player plays all of the recorded DTMF wave files with no problem. I am using the correct file locations (c:\WAVE\TONE1.wav) for the Playwave. I know for sure that TONE1.wav is recorded and is of good quality. TONE's 1,4,7,9 & 0 will not play in Lookout. TONE's 2,3,5,6,& 8 will play. All of the DTMF tones are about 1/2 sec. long and about 11kb. I have tried renaming the playwaves and the DTMF wave files, no help. Please try to simulate this problem to provide a reasonable solution, unless this problem has already been addressed and a solution was found. Thanks




Getting 50 points from 10 points

Fri, 22 Sep 2017 08:50:12 GMT2017-09-22T08:50:12Z

I I'm having a IV curve their points are max 20 and I wanted to expand the points in more than 20 points, having same curve.Can someone please help me with that




Mailer object stops after two tries

Wed, 13 Sep 2017 22:22:09 GMT2017-09-13T22:22:09Z

I am trying to create a mailer object that sends out emails but it stops after sending it two times. Please help. I am using Lookout for Win32 Version 6.7 (build 49153)
Mailer Object:
Name: H2S_Alarm_Mailer

Recipients: "myemail@do-main.ca"

Subject: "H2S Alarm "&H2S_Accum_5min
Message: "H2S Alarm triggered "&..\board1.H2S
Send: TRUE

From address:"no_reply@do-main.ca"
SMTP server: smtp.do.ma.in

Generate event on successful send is checked

Timeout: 30 seconds

Mailer alarm priority:10




Clients losing connection to server

Fri, 04 Aug 2017 16:42:42 GMT2017-08-04T16:42:42Z

This issues has been happening about once a week, my clients are losing connection to my server randomly at any time. When i view the client connection monitor, my list is blank. Sometimes when i open my server file i get an error "process registration failed". Only way for me to get the clients back is to restart the computer. I have already tried to repair lookout program by reinstalling and tried changing the National Instruments PSP Server Located to automatic in services. http://digital.ni.com/public.nsf/allkb/622F4C13A00A4C6786256DC600571783.

 

 (image)




Lookout 6.7.1 not connecting to GE 90-30 PLC

Sun, 30 Jul 2017 12:48:17 GMT2017-07-30T12:48:17Z

We have Lookout 6.7.1 running on a Windows 10 PC, trying to connect to a GE Fanuc 90-30 PLC.  The PLC software (VersaPro) connects to the PLC in a XP virtual machine, but Lookout running in the (Win10) host does not connect, even if VersaPro is not running.

 

I tried a few different CPUs, networking modules and even cables, and tried some changes to the networking settings in Windows, but couldn't get it to connect.  Not even one time.  Using a serial connection to the PLC, Lookout is able to connect, but when switching back to Ethernet, it fails and I get the following alarm: "Error connecting: Unknown port name specified".

 

We have Lookout 6.6 running on Windows 7 on another machine, connecting to the same type of PLC hardware, and it connects and runs fine.




How to change a value based on the time?

Tue, 25 Jul 2017 12:03:32 GMT2017-07-25T12:03:32Z

Using Lookout 4.01:

 

Is it possible to set the value of a gauge or pot based on the system time? Starting at midnight with value 0%, then increment the value each hour (on the hour) to 100% at midday and then reduce it back to zero. The increment is always the same (±8.3%). Repeating this process every day.

 

The aim is to control a light to simulate the sun.

 

Many thanks.




Trends stopped working

Thu, 20 Jul 2017 23:41:55 GMT2017-07-20T23:41:55Z

Can anyone tell me what would cause all trends to stop after a lookout 6.6 process has been running for years and trending fine?




Lookout 6.1, Modbus Protocol Statistics

Thu, 13 Jul 2017 17:04:17 GMT2017-07-13T17:04:17Z

Under "Options" - "Modbus" - "Statistics", what does all this information mean. We have been getting a lot of "Response too short" and "No response" errors. Just trying to figure out what all these errors mean under "Total errors". Thank you in advance for your help.




Lookout 6.6 server/client process not working across network

Wed, 12 Jul 2017 20:36:05 GMT2017-07-12T20:36:05Z

I have a server and client process setup in Lookout 6.6 using a symbolic link in the client process for all of my data members, switches, etc.  If I have the client process running on the same PC as the server process, everything works fine.  When I open the client process in a client version of Lookout 6.6 on a remote computer, none of my links work.  Everything has a red "X" over it.  Both PC's showing on my network.  What am I missing?




reconocimiento de proyecto en lookout v6.7.1

Wed, 12 Jul 2017 16:15:36 GMT2017-07-12T16:15:36Z

hola buen dia a todos, tengo una situacion y me enviaron a esta liga lo que sucede es que se esta haciendo la migracion de un proyecto, este proyecto esta en lookout, se compro el software lookout version 6.7.1 (licencia runtime only) para unas pantallas touch, realizamos las modificaciones del proyecto en una laptop en la cual contamos con el version lookout 6.7.1 (con la licencia para el hambiente de desarrollo) se crearon unos usuarios en el proyecto al momento de abrir el proyecto a la pantalla touch los usuarios que se crearon no aparecen y en la pantalla no se pueden realizar cambios ya que solo contamos con la licencia para el run time only, se supone que no deveria de haber ningun problema ya que son la misma veresion lo unico que es diferente son las licencias, les adjunto la informacion de la pantalla touch para ver que mas opciones tengo para resolver este problema!!

 

Hi everyone, I have a situation and I was sent to this league what happens that a project migration is being done, this project is in lookout, I bought the software lookout version 6.7.1 (license run time only) for some Touch screens, we made the modifications of the project in a laptop in which we have the lookout version 6.7.1 (with the license for the development helper) some users were created in the project at the moment of opening the project in the touch screen Users that were created do not appear and the screen can not make changes since we only have the license for run time only, it is assumed that there should be no problem since they are the same version the only thing that is different are the Licenses, I attach the touch screen information to see what more options I have to solve this problem !!

 

 




Lookout and Motorola ACE-1100 FEP / Counter

Sat, 08 Jul 2017 17:51:22 GMT2017-07-08T17:51:22Z

Lookout / Motorola FEP/1000 RTU.

 

 Has anyone worked with the ACE1000 and counter input's we are new to Motorola ACE-1000 product. We have a couple systems deployed

however have not worked with any counters for flow reading and totalizer.

Does the RTU need configured for counter inputs via the STS programmer ?

Are there registers enabled that we can access directly threw the FEP and how are they addressed ?

Thanks

 

WirelessOne

 




New Server, Old Client

Tue, 20 Jun 2017 16:47:55 GMT2017-06-20T16:47:55Z

Hello again, all.

 

I recently had a bad hack and had to format my server computer.  I have FINALLY got it up and operating like it was, but now need it to talk to the client computers.  I still have to old client.l4p program in the client computer.  Is there a way to link that up to the server computer, or do I need to start a new client.l4p, etc?

Windows 7 O/S

Running Lookout 6.7.1

 




Help With Scales

Fri, 16 Jun 2017 13:54:05 GMT2017-06-16T13:54:05Z

Good Afternoon Friends,

 

I work in an IT department and we have hit some issues after restoring an old Lookout Project file used to control some lab equipment.

 

We are reading three digital scales (measuring the weight of three cylinders holding liquid) and controlling three pumps to amend flow rates over time. Our lab technicians believe that after the restore, the weight displayed on the laptop running Lookout is reading 2.5 KG for example, but it should be reading to a much finer resolution and displaying units down to 2,500,00 mg.

 

Could there be some kind of setting that needs amending within the software, or an incorrect setup on the COM port reading the digital scales output?

 

I'd appreciate any help on this.

 

Thanks in advance 

 

Jason 

 




Difficulty with modem communication

Fri, 09 Jun 2017 21:57:37 GMT2017-06-09T21:57:37Z

I was recently hacked bad.  I had to totally format my hard drive.  I reinstalled Windows 7 and Lookout 6.7.1 as well as appropriate .l4p, .l4t, lka and lks files, which pretty much brought me back to where I was before the hack.  However, my phone communications are failing.  We use both Direct Logic D340 and M340 modicoms in the field.  Lookout is occasionally communicating with the M340's, but it is erratic.  It is not talking AT ALL to the D340 and the modems keep getting stuck whenever they try.  We use a variety of modems in the field, but most are Sixnet VT-MODEM-1WW.  Oddly enough, I thought my radio communications would be the issue, but they are all communicating perfectly.

I have checked the settings on all 8 of my NI PCIe 8430/8 (RS-232) comm devices and the BPS, Data bits, parity, stop bits and flow control all match what is on Lookout.  The comm ports also match to what we had before the hack.  They are running the same driver as they were before the hack (NI 3.9.0.49154).  I had tried the newer version of the driver (15), but it was having the exact same issues, which is why I downgraded to the version we were originally running, HOPING that was the issue.

Anyone have any ideas?  I have been plugging away at this for the better part of a week and have hit a steel reinforced brick wall.  Thanks.

 




CB-50LP with 6025E

Thu, 08 Jun 2017 20:54:12 GMT2017-06-08T20:54:12Z

Looking to use an existing setup with a slightly newer PCI card.  Just wondering how I can setup PCI-6025E to work with accessory CB-50LP when it is not in the list of Accessories when setting it up?  If None is selected for accessory, will it work?

 

Going from PCI-1200 to 6025e with the adapter.  Just wondering what to do with the accessory setting.

 

 




Lookout 6.6 slow response

Wed, 07 Jun 2017 21:01:48 GMT2017-06-07T21:01:48Z

Lookout 6.6 has started running very slow, 30+ seconds to change screens or enter numbers.  There is a "Serial port could not be opened (COM12)" alarm that can't be cleared.  I assume this may be the problem but the values from that device seem to be updating.  Anyone have this experience?  This description is second hand from a plant operator, he has restarted Lookout a few times and rebooted the computer and says Lookout is now almost unusable because of response. 




NI Lookout communicating w/ DirectSoft and AutomationDirect 06 PLC's

Fri, 12 May 2017 20:44:10 GMT2017-05-12T20:44:10Z

Thinking of purchasing NI Lookout for the 1st time (very familiar w/ old Automation Direct Lookout packages).  I primarily use DirectLogic 06 PLC's (DirectSoft Software).  I do NOT have a copy of the the old PC-DL-PLUS driver from AutomationDirect (is this required?)  I am wanting to run Microsoft Windows Embedded 7 E (64-bit) on my SCADA PC (is this compatible?)  I connect to the PC through either port 1 on 06 PLC (RS232) to serial port on PC or through HO-ECOM100 module and to ethernet port on PC.  Wondering if latest NI Lookout rev's have solved any or all issues I've seen posted here.

Any insight/advice greatly appreciated.




Error when compiling .lks file from version 4.0.1 on 6.7 error: Invalid object pathname

Thu, 11 May 2017 17:54:31 GMT2017-05-11T17:54:31Z

Lookout Process File Compiler Version 6.7 (build 49153)
Copyright National Instruments111 1992-2013 All rights reserved.

F:\Software\Software\Lookout 6.75 Server\Import\default.lks
F:\Software\Software\Lookout 6.75 Server\Import\default.lks(2327): error: Invalid object pathname: ..\Timers\Timer_10_Second
F:\Software\Software\Lookout 6.75 Server\Import\default.lks(2540): error: Invalid object pathname: ..\Timers\Timer_10_Second
F:\Software\Software\Lookout 6.75 Server\Import\default.lks(2924): error: Invalid object pathname: ..\Timers\Timer_10_Second
F:\Software\Software\Lookout 6.75 Server\Import\default.lks(3086): error: Invalid object pathname: ..\Timers\Timer_10_Second
F:\Software\Software\Lookout 6.75 Server\Import\default.lks(3944): error: Invalid object pathname: ..\Timers\Timer_10_Second




Error when opening lks

Thu, 11 May 2017 17:46:42 GMT2017-05-11T17:46:42Z

Can someone help me figure out what's wrong when I open Lookout 4.0.1 lks file in 6.75?

 

default.lks(2327): error: Invalid object pathname: ..\Timers\Timer_10_Second