Subscribe: Lookout
Added By: Feedage Forager Feedage Grade B rated
Language: English
client process  client  data  direct  driver  lookout  modbus  plc  points  problem  process  running  server  time  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: Tue, 20 Feb 2018 00:18:30 GMT2018-02-20T00:18:30Z


Citadel Logging Frequency Limitation in Lookout 6.5 and 6.7.1

Tue, 13 Feb 2018 13:48:50 GMT2018-02-13T13:48:50Z

Usually, I don't push Lookout for data acquisition beyond once per second.  Recently, I had a request to push a Modbus TCP device communication with Lookout to as fast as possible.  I was able to get Lookout to receive data at 10 Hz without any Modbus errors.  The particular data being retrieved is integer between 1 and 32k.


I've connected the Modbus member to a data table and normally I only log to Citadel from the Datatables but this time, I setup logging to citadel from both entities (Modbus member directly and Datatable connected member).  The problem is that the logged values are always about one second (plus or minus) apart and I can see no change in Citadel logged frequency no matter what the Modbus poll rate is set to.  I can see live digital data displays changing at higher frequency when the Modbus poll rate is changed but nothing faster than ~1 Hz is actually logged to Citadel.


Is there something I'm missing here?  Is this an inherent timing limit of objects to log to Citadel within Lookout?  Can this be modified?

Direct logic driver addressing to Modbus addressing

Fri, 02 Feb 2018 06:03:21 GMT2018-02-02T06:03:21Z



 I have an older Lookout Direct 4.X system that needed to be updated. We have purchased a new Windows 10 computer and Lookout 6.7.1. My original system uses the Direct Plus driver to talk with the Automation Direct DL250 PLC system. I have since found out that the Direct Plus driver is obsolete and will not run on any Windows version above the Windows XP version. I have also found that there is a Modbus driver built into Lookout that will work with the H2-ECOM module I use in my system. The problem I am having is that I do not know how to figure out the new addressing the Modbus driver will use I.E. a Relay that was Address y340 under the Direct Plus driver what will its new address be with the Modbus driver? I have attached a PDF file that is a block diagram of my system with the address range of each of the input or output modules on it with the original Direct Plus driver. I have also attached an export of the Data Member configuration of the Direct Logic driver. Can anyone help me figure out the new addressing under the Modbus driver? Any suggestions on the best way to handle the conversion between the drivers in my Lookout application. Thank you for any help you can give me it will be very much appreciated!


Thank You


Lookout server modbus data collection question

Fri, 26 Jan 2018 14:15:45 GMT2018-01-26T14:15:45Z

Is there any way to determine how many bytes of data I am polling over an individual Modbus station in a month time frame? Can I run it through the Modbus statistics and calculate?

Upgrade LookOut 6.5 to 6.7

Thu, 25 Jan 2018 11:43:52 GMT2018-01-25T11:43:52Z

What is the cost of upgrading LookOut 6.5 to  6.7?

What are the significient changes?

What  are the requests for Server and Client computers?

LookOut 6.5 - server - client communication

Tue, 23 Jan 2018 12:04:15 GMT2018-01-23T12:04:15Z

I am using LookOut 6.5 already couple years. Recently I noticed a problem which was not expected at all.  There are three clients installed on Win7.  There are

8   Hitachi  PLCs communicating with Lookout server over Hitachi  OPC (just one OPC server). In last two  years I added about 10 Modbus devices and they are communicating over MODBUS Ethernet drivers.   That was the only change made on the SCADA and now I am monitoring 11 500 points. About 100  variables,  all


from one Hitachi PLC, cannot be monitored on clients. These  variables  can be monitored over server without any problems. We  monitor about 200 values from this particular PLC, but this 100 are for some reason a problem. If we start client and if we succeed to monitor these points, in very short time, the values of   these points will freeze.  If we start the .lks file,their values  will be set to 0. In same time, the server shows this values correctly and we can see how these values are changing it should have been (example:  electrical current, active power...)   all  clients are showing the same results...even development software.


What can be the cause of this problem and how we can solve it? License is for unlimited number of points.


Status of a counter in a DirectLogic PLC

Thu, 18 Jan 2018 20:57:34 GMT2018-01-18T20:57:34Z

The previous lookout I used you simply created an expression that read: "DL240.CT2A" for example to look at CNT2 in the PLC using a serial port connection.

Now Lookout says "Not a member of class DL205: CTA2".  If you take the "A" out of it and type "DL240.CT2" lookout takes it but it does not show counter correctly (just 0 all the time).  Am I not typing something correctly?

I need to program a pulse on time of day

Fri, 05 Jan 2018 15:53:47 GMT2018-01-05T15:53:47Z

I am needing to send a pulse out of the HMI ever morning at 02:05 ( 2:05 am) using the PC clock to the PLC clock.  Wanting to synchronize the PC and PLC clocks.

I need to know if Lookout 6.7.1 uses Microsoft SQL for it's Database.

Mon, 11 Dec 2017 21:54:52 GMT2017-12-11T21:54:52Z

My IT Department is asking if the Lookout is using a SQL Database that they can backup using simple SQL Queries. What should I tell them? 



Lookout feezing when com ports become unavailable

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


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?




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: ""

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

From address:""
SMTP server:

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.



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 ?