I have 3 channels on my NI OPC server, I need to pass one word and two Boolean between channels. any help would be appreciated.
↧
I'm trying to pass data from one channel to another in NI OPC server. any help would be appreciated.
↧
Lookout Direct to Lookout
I am migrating an older Lookout Direct (Automation Direct) SCADA system to NI Lookout 6.7.1. Is there a conversion that needs to be done to the Lookout Direct files? Are there any "gotchas" that I should be aware of prior to undertaking this migration? Thanks in advance for your help.
↧
↧
Lookout not trending
Hello all,
I recently had to purchase a new laptop to replace one whose screen is rapidly dying. I have transferred all of the Lookout folders over that I can, but am having an issue with it not showing trends when I hook into the LAN. All of the other objects are operating properly- counts, alarms, et al. but it is just not showing any lines on the trend screen. I am running Lookout 6.7.1 on a Intel Corei5 laptop with Windows 7. Can anyone offer any advice? Thanks.
Sincerely,
Tim Sievers
↧
Lookout 6.7.1
hello
I am new to Lookout application deployment..
The client have an old Lookout 6.1 that got converted to 6.7.1 but it crashed
We installed Lookout 6.7.1 on windows 7 machine, then I copied the Source Code File (LKS), Process File (L4P), State File (L4T), and Security File (LKA) and Graphics to the directory but the graphics are showing small question marks. How to resolve it? and how can I check the database?
↧
Lookout 6.7.1 Slowness after Migration
I have an old computer with Lookout 6.1 that crash. A new computer has been rebuilt with Lookout 6.7.1 and I tried copying the existing LKS, LKA, L4P, L4T. The Process File opens but it is very very slow to open, it takes roughly 30 mins. is there a way to speed this up? or what could be the cause?
I was able open it relatively fast before..before I installed the OPC driver. The slowness only occur after I installed the drivers for GE and AB PLC
↧
↧
No communication from Lookout 6.5 with NI OPC Server 2016
Hi Everyone: I am using Lookout 6.5. It works with OPC server 2009 but when I install NI OPC Server 2016, the OPC client objects can not see the directories of the channel in OPC server 2016. How to config OPC server 2016 to work with Lookout 6.5?
↧
Error when compiling .lks file from version 4.0.1 on 6.7 error: Invalid object pathname
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 compiling .lks file from version 4.0.1 on 6.7 error: Invalid object pathname
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 compiling .lks file from version 4.0.1 on 6.7 error: Invalid object pathname
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
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
↧
Error when compiling .lks file from version 4.0.1 on 6.7 error: Invalid object pathname
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
↧
NI Lookout communicating w/ DirectSoft and AutomationDirect 06 PLC's
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.
↧
Lookout 6.6 slow response
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.
↧
↧
CB-50LP with 6025E
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.
↧
Difficulty with modem communication
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.
↧
Help With Scales
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
↧
New Server, Old Client
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
↧
↧
Lookout and Motorola ACE-1100 FEP / Counter
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
↧
reconocimiento de proyecto en lookout v6.7.1
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 6.6 server/client process not working across network
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?
↧