Lookout 4.0 w/Fieldpoint

Installed Fieldpoint 1.7 after Lookout 4.0 and restarted PC. Lookout no longer
ran due to missing "lkhist.dll" file. Reinstalling Lookout solved problem.
Anyone else seen this yet?

David,
You're very right. At the time that I made that post, it was valid information.
In the mean-time, the version of lksock.dll on the ftp site has changed,
and it references parts of the new lkdynam.dll (not on the ftp site).
We will be releasing a maintenence update to Lookout at the end of this month
that will resolve all of these inconsistencies.
Obviously, with file versions on the ftp site changing frequently in this
interim time period, I do not want to give directions on how to "fix" this
until the maintenence release (lest my advice once again become invalid before
someone else reads it).
For anyone else who experiences similar problems, please go to our Ask an
Engineer site at http://www.ni.com/ask
and provide the details as David did. You will receive a reply from one
of our Applications Engineers who will help you get a consistent combination
of files.
I apologize for the inconvience during this interim time before the maintenence
release. David, I will send the current instructions to you after posting
this message.
Anita Anderson
support wrote:
>Anita,>>I followed your instructions and downloaded the updates from the
FTP>site.>One of that was "lksock.dll".>However if you use this version the
following error message is generated>when starting the Citadel services.>>"The
LKSOCK.DLL file is linked to missing export>LKDYNAM.DLL:ThreadStartup">>Does
this mean that the updated "LKDYNAM.DLL" is missing from the FTP>site.>>David
Crofts>Acquisition Systems Ltd>>>Anita Anderson wrote> >> "Todd Buchholz"
wrote> >>Installed Fieldpoint 1.7 after Lookout
4.0 and restarted PC. Lookout no>> longer>ran due to missing "lkhist.dll"
file. Reinstalling Lookout solved>> problem.> Anyone else seen this yet?>>
>> Todd,>> >> I tried to replicate your problem on a newly reformatted NT
machine. My>> lkhist.dll was on my machine, both before & after. Lookout
ran fine so I'm>> not sure why your machine experienced the problem. There
are a few other>> things you should be aware of.>> >> Fieldpoint Explorer
1.7 is an older version of the software, designed prior>> to Lookout 4.0.
It will run with Lookout 4.0, but there are a few reasons>> for why you
should install the current version (2.0) when using Lookout 4.0.>> When
you install version 1.7, it will actually overwrite the fpoint.cbx>> in the
Lookout 4.0 directory with an older version. The main reason to upgrade>>
your FieldPoint software is that there is a crash associated with using the>>
old fpoint.cbx with Lookout 4.0. Also, the older version of the FieldPoint>>
software does not support the FP-1600 network module. I'm guessing that>>
you aren't using this network module, but if you decide to use it in the>>
future, you would need to upgrade anyway.>> >> The most recent version (2.0)
is available in a zip file from our ftp site>> at>> ftp://ftp.ni.com/support/fieldpoint/Server/>>
>> After you install that software, you can go to the site below and download>>
a couple of fixes available for Lookout 4.0. Among them is a newer version>>
of fpoint.cbx which fixes the crash problem.>> >> ftp://ftp.ni.com/support/lookout/Lookout4fixes/>>
>> Anita Anderson>> National Instruments

Similar Messages

  • FieldPoint Explorer genera errores de Lookout Services

    Realicé un programa ejecutable con LabVIEW 6.1 y FieldPoint 3.0, cuando se enciende el computador en el cual esta instalado dicho programa se presentan dos dialog box con el siguiente mensaje:
    Lookout Services:
    Lookout Citadel Server was not loaded
    y
    Lookout Services:
    Lookout Time Synchronization was not loaded
    Yo no estoy utilizando Lookout, solamente LabVIEW, FieldPoint Explorer y un driver de una tarjeta serial PCI-485. Estoy utilizando la instalación de FieldPoint explorer básica y Si desinstalo el FieldPoint Explorer del computador ya no aparecen estos cuadros de diálogo de error.

    Hola,
    Tengo algunas sugerencias. Puedes intentar reinstalar los servicios de Lookout (un componente del Fieldpoint Explorer) siguiendo las direcciones en este Knowledgebase:
    http://digital.ni.com/public.nsf/websearch/90F854DBAE26BE6C86256A010050A06B?OpenDocument
    Otra opcion es actualizar Fieldpoint desde 3.0 a 4.1. Si haces esto, tienes que construir otra vez tu ejecutable con la nueva version de Fieldpoint. Puedes descargar el driver aqui:
    http://digital.ni.com/softlib.nsf/websearch/7CF3FDE2EC1C043D86256EBC006FC786?opendocument&node=132060_US
    Avisame si todavia tienes problemas.
    Saludos,
    Erin

  • How to convert FP-1000 to FP-1601 in Lookout 5.0

    I'm in the process of switching over my FP-1000 serial interface modules with FP-1601 Ethernet modules on our HemoDialysis water system control with LookOut 5.0 so that we can set up redundancy.  My process in Lookout has been running without problems for the last few years.  After swapping the FP-1000 modules for FP-1601 modules, I configured my two FieldPoint banks containing FP-110 Analog Input modules, FP-422 relay modules, FP-420 relay modules, & FP-301 Discrete Input modules with FieldPoint Explorer.  I then opened up the process in Lookout & changed my existing FieldPoint objects from serial connections to ethernet, entered the correct I.P. address for each one, & imported the new IAK Configuration file.  My switch objects in the process linked to the relay channels of the 420 & 422 modules worked correctly.  However, none of my expressions for any of the Analog Inputs (which are all 4-20mA)showed up correctly.  Also I got a "Bad Quality from Network" error message in the alarms window for one of the two FP-1601's.  I'm assuming the problem is in the configuration of my Lookout process, but have not been able to find anything in the manuals to correct the problem.  Any thoughts?

    I can't use the current online AI-110 because I would have to replace the current FP-1000 serial module (in which everything is working correctly) with the FP-1601.  When I power down to swap interface modules, my pumps supplying water to the dialysis patients stop.  For that reason I can only try to swap & debug the current setup from serial to ethernet at night for a couple of hours when there aren't patients being treated.  However, if I purchase another AI-110 & connect it to the FP-1601 by itself, I can create a seperate process & only work with those two modules while my water system control process & modules run unaffected.  I wouldn't have any time constraints & would be able to learn how to correctly set up the FP-1601 & AI-110 using the OPC Fieldpoint driver regardless of the patients being treated.  Once I have it working correctly & know how to make the changes on the water system process, I can make the changes at night when the patients are back off.  I was able to use the OPC Fieldpoint driver to create a process using the FP-1601, a RLY-420, and a switch object in a seperate process & turn on/off a relay with the switch.  However, when I tried to do the same thing with the water system control project, I still was unable to read any data in Lookout from the AI-110 modules.  I could see the current changing in FieldPoint Explorer, but not in my Lookout expressions.
    David Simpson

  • How do I move Lookout 5 w/ Fieldpoint 3 to a new PC

    I want to move my install of Lookout 5 from an old, slow computer to a newer, faster one. Both machines run Windows 2000 SP4. I have a clean install of Lookout 5 and Fieldpoint 3 on the new machine, and the old machine still works and is running on the same network subnet. In addition to lookout.sec (in the Windows system folder), what else do I need to move to bring up my system on the new machine? Are there registry keys that need export/import? Which folders (by default, at least) need to be copied?
    Thanks!!

    Besides .l4p .l4t .lks .lka files, you need to copy the database folder to the new machine. And then create a new database on the new machine with the data.
    Ryan Shi
    National Instruments

  • Lookout communication with FieldPoints

    I have taken over this location and I have very little to no documentation as to what does what on the Fieldpoint I/O's. I am up against the Software license limit of 100 I/O points. Currently my process is outdated and I have a need to add I/O's for additional functions. I tried to delete unused/un-needed Lookout control panel objects in order to reduce the I/O count but was not successful. Most objects could not be deleted "due to dependencies". In some cases, I was able to delete objects but the I/O count stayed at 100. The manual offered no help.
      New plan: start a new process.
    I copied the syntax for each of the Lookout control panel objects that I wanted to keep from the old process that I wanted to use in the new process. I did this for each control panel in my new process to get the functionality just the way I needed it.
    When done, having eliminated all of the no-longer needed I/O's, I had expected to see the I/O count around 50 which would allow for new required functionality. This all sounded good on paper.
      However, my new process will not communicate with any FieldPoint I/O's, (I/O count =0), unless I have the old process and the new process running simultaneously. Then the I/O count is 100 and my new process communicates just fine, but having the old process running defeats the purpose of creating the new process. That is to eliminate un-used I/O points to make room for new I/O functionality and stay under the 100 I/O limit. Although, I am able to save my new process, (which is less than 100 I/O), when it runs simultaneously with the old process, the 100 I/O limit is exceeded and Lookout defaults to Demo Mode, which is limited to 60 minutes of operation.
      Obviously somewhere in the old process is some kind of enable instruction for the Field points, that I don't have in the new process, but I do not have a clue as to where to look or what to look for. Again the manual did not offer any help.
      The FieldPoint units that we are using are: FP DI 301, 330, FP DO 401, and FP AI 110, along with the FP 1001 serial network modules 
      Desperate in Denver.
    Need answers fast!
    thanks

    KDVR,
    To get the best support for lookout check out these places:
    www.ni.com/ask
    and submit a new email support request with Lookout selected for the Software Platform.
    Lookout Discussion forums
    Regards,
    Peter Flores
    Applications Engineer

  • Lookout (fieldpoint object) does not list any connection to fp aio 600 (outputs)

    The fieldpoint object in lookout reports that all channels in FP AIO 600 are inputs.
    To fix this go to "edit data member configuration" and select the "output" channels of the AIO 600 and change the "member" prefix to "AO". Save and you now have access (can connect to) the channels in "edit connections"

    Hi Rahul,
    this question does not seem to be related to SQL and PL/SQL forum.
    I guess you could use {forum:id=64} or {forum:id=61} forums.
    Regards.
    Al

  • Fieldpoint object in Lookout

    Hello
    I have set up my FP1601 with a AI card and a TC card in MAX and saved the configuration to the .iak file. When I create an FieldPoint object in Lookout there is this option to import the iak file. If i choose not to import the file, but rather configure all the seperate channels on the cards in Lookout, which settings are the present ones? And if the FieldPoint for some reasen looses power, will the settings in Lookout be applied again?

    Ok. Thanks for the answer
    But do I really have to configure the IO cards at all in MAX or Fieldpoint explorer? What I`m a little confused about is the relationship between the Lookout settings and the configuration in the IO cards.
    Lets take this ex.: I put up a new FP1601 with 5 TC cards. Configure the FP module with the right IP etc. I dont do anything with the TC cards... Then I Start Lookout and configure each TC card in there.
    Will that work or do I have to first configure the TC cards in MAX\FP explorer?

  • FieldPoint real-time controller or Ethernet interface

    Good Afternoon,
    The first feature listed on the FP-2000 product page is:
    Stand-alone embedded real-time controller or Ethernet interface for PC-based distributed I/O.
    Has anybody successfully implented a FP-2000 as an Ethernet interface for PC-based distributed I/O?  In other words, have the FP-2000 act like a FP-1600?
    There are some discussion forum threads that dance around the subject but I have not found one that really answers it.
    Thanks,
    Ed
    Solved!
    Go to Solution.

    Hi edlad,
    After playing around with a FP-2010 for a while, I do believe that you need to install LabVIEW Real-Time on the controller in order for it to work, even if you are technically not using it because you are not running a VI/executable on the controller. As far as your issue with installing LabVIEW 8.5.1 on a FP-2000, that is troubling because there should not be an issue doing this at all. In fact, I have personally been able to install LabVIEW 8.5.1 on many FP-2000s. For that issue, I would suggest reformatting the FP-2000 from MAX and try again.
    ThinkG: Regarding your question about using a cFP-2220 to communicate with Lookout, I am not sure because Lookout support is handled by our Shanghai branch via email only. However, I do know that you can use that second ethernet port to communicate with another FieldPoint network module (cFP-180x) using the FieldPoint drivers. Here are a couple good KnowledgeBase articles regarding that configuration. I hope they are helpful.
    http://digital.ni.com/public.nsf/allkb/F602F6F1B243282686257495007695BB?OpenDocument
    http://digital.ni.com/public.nsf/allkb/67F94BB93BCE32CF86257367006B3659?OpenDocument
    Thank you for choosing National Instruments.
    Aaron Pena
    National Instruments
    Applications Engineer
    http://www.ni.com/support 

  • Too much zooming in NI-HyperTrend locks lookout process.

    I'm using lookout 5.0 over W2K. When I try to zoom-in too much in NI-HyperTrend (Activex control object) Lookout locks and hence I have to end process using the Windows Task Manager. I'm using '+' icon to zoom in. Any idea? (urgent)

    Hello Patrick R.
    thank you for your message. The pc on which the lookout process (only one process) runs, is dedicated for a Fieldpoint string. Pc communicates with FP-1600 (ethernet comm module) directly. FP string we have 8 modules(2 x AI-100, 1x RLY-420 and 5x RTD-122). Total I/O number is 55. Several NI-hypertrend objects (activex control objects) display several (4 to 36) signals. The signals are logged to the citadel database at local hd. There is no other application running meanwhile.
    Cliking frequency of zoom button is normal (2-4 Hz). It doesn't matter if we stop the graph or not. after zooming the cpu usage peaks to 98-99 percent and then we are to end the lookout application.
    The system is on site. I tried also in office using lookout5.0/examples/ap
    plications/batch2.l4p . I create a new NI-hypertrend and insert several traces. it locks up after deep zoming. This phenomena repeats itself randomly. I tried after once more but I was unable to lock it. I think that the trend chart cannot follow the fast changing data.
    thanks for your action.
    kemal (knk).

  • Could you please tell me, how can you, using Lookout and Field Point, program on/off relay actions using a calendar?

    It´s a on/off illuminating ssystem control. Shure the user will need a calendar programing tool to program weekdays, holidays, etc. on of functions.

    Hi Galileo,
    See the following for Lookout side of things:
    http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000DBE90000&USEARCHCONTEXT_CATEGORY_0=_9_&USEARCHCONTEXT_CATEGORY_S=0&UCATEGORY_0=_9_&UCATEGORY_S=0
    As for FieldPoint, you can talk to it from Lookout in couple of ways -- either directly using the native FieldPoint object, or via OPC using the OPCFieldPoint object.
    Based on the timers from above, you would turn On/Off the relays (on the RLY-420 module of your FieldPoint).
    That's in a nutshell. Write back if you have specific questions.
    Good luck!
    Khalid

  • OPC server error with Lookout 5.1 that was working with Lookout 4.5

    I was running a file on Lookout 4.5 with Field Point explorer 3.0 with field point objects. I recently upgraded the Lookout to 5.1 and Field Point Explorer was uninstalled. Now when I try to open my old Lookout file, I cannot control through the field point objects and I am getting the following error: OPC/OLE error. OPC server not registered properly (63). Invalid class string 800401F3.

    Hello,
    Thanks for contacting National Instruments. There are three known reasons that you may get this error.
    1. IAK file not setup or it has been moved or is missing.
    This error is easy to reproduce. In order for the OPC FieldPoint Server to work, it has to launch the FieldPointOPC2.exe which has looks at a registry key for FieldPoint Explorer. In this registry key is the path to the last saved or loaded IAK file. If this file has moved or has been deleted, then you will get this error. This also happens to customers that have upgraded their FP Explorer and haven't opened up their IAK file and saved it.
    2. OPCproxy is not registered. Which means the opcproxy.dll or opccomn_ps.dll are not registered or are version 1.0 (can be registered by running "regsvr32 opcprox
    y.dll" and "regsvr32 opccomn_ps.dll". The opcproxy.dll and the opccomn_ps.dll are located in the system32 folder in the WINNT directory.
    3.OPCserver is not registered (can be accomplished by running the .exe with a /regserver switch) . The Fieldpoint OPC server is located in the following path: [drive letter]:\Program Files\National Instruments\FieldPoint. From a DOS prompt you can manually register the EXE by going to that directory and typing FieldPointOPC2.exe /RegServer. In a dos prompt the command line looks like this (also see attached picture):
    c:\cd c:\Program Files\National Instruments\FieldPoint
    c:\Program Files\National Instruments\FieldPoint\FieldPointOPC2.exe /RegServer
    Hope this works. If it doesn't, then I suggest that you uninstall all NI software and try to do a fresh install. This will properly ensure that all the services and servers are registered.
    A Saha
    Applications Engineer
    National Instruments
    Anu Saha
    Academic Product Marketing Engineer
    National Instruments

  • HAD PROBLEM INSTALLING LOOKOUT 6.0.2. LOST ADMIN PASSWORD.

    I have been emailing Ryan Shi about a Lookout OPC fieldpoint problem where
    OPC fieldpoint stops communicating.  He has informed me that there is a patch  but  I have to install lookout6.0.2.  I had a problem doing this.
    I was able to load the new version of lookout  but the  administrator password was  altered  during the install.  I  restored my system to an earlier version.  How can I perform this  update without this problem occuring?
    Thanks,
    Gene

    Gene,
    What's your current lookout version?
    If it is 6.0.0 or 6.0.1, you'd better install 6.0.2 first and then apply the patch. Before you install 6.0.2, backup this file C:\WINDOWS\system32\lookout.sec and then delete it. The installation will generate a new lookout.sec file with empty password. The admin password by default is empty. What you need to do next is to reset all the users and passwords.
    In general, the password is stored in lookout.sec and won't be changed during uninstall and install, however maybe your lookout.sec is corrupted.
    Ryan Shi
    National Instruments

  • Fieldpoint FP-1600 Data Display Problem

    I'm building a new system using the following devices:
    Fieldpoint Ethernet module (FP-1600)
    Analog input module (FP-AI-111)
    Fieldpoint Explorer (V.2.0 build 91)
    Lookout (V4.5 build 9, for Win32)
    When I use Fieldpoint explorer I have no trouble displaying the data from
    the one analog input module; However, when I attempt to display the data in
    Lookout I receive a box with a zero and red X. The alarm also alerts a "Bad
    quality received from network module" alarm.

    Never mind - operator error!
    I did not check over the IP addresses correctly.
    > I'm building a new system using the following devices:
    > Fieldpoint Ethernet module (FP-1600)
    > Analog input module (FP-AI-111)
    > Fieldpoint Explorer (V.2.0 build 91)
    > Lookout (V4.5 build 9, for Win32)
    >
    > When I use Fieldpoint explorer I have no trouble displaying the data from
    > the one analog input module; However, when I attempt to display the data
    in
    > Lookout I receive a box with a zero and red X. The alarm also alerts a
    "Bad
    > quality received from network module" alarm.
    >
    >

  • Bridgeview and Lookout Protocol Driver

    I am a Bridgeview 2.1.1 Full Dev. System user - was shipped an upgrade disk
    w/out the IA Server disk (4.0?). Now as I wait for it, I was trying to look
    for the driver set I had on my previous set of dsiks (Bridgeview 2.1 and
    IA Server 2.1) - and I cant find it, although I have installed it from my
    previous set before. What am I doing wrong here? Thanks.
    Sudhi

    Sudhi,
    I assume finally you got the the National Instruments IA Server CD. If not, you might contact your N.I. sales representative.
    Actually, the IA Servers (aka IAK Servers based on the configuration through NI Server Explorer) is not available anymore and is an obolete NI product. However, if you want to communicate with PLC and other 3rd party hardware, I would recommend to get an OPC server from the manufacturer of the hardware. Another option would be to get the Lookout Protocol Drivers from National Instruments which allows you to communicate through the OPC interface to different PLCs (P/N: 777616-01, Industrial Automation Servers with OPC Interface, Win NT/98/95,CD). Those drivers are included in the Control Edtion Packages for LabVIEW. Check it out: ht
    tp://amp.ni.com/niwc/suite/control.jsp?node=10418
    National Instruments has as well hardware with FREE drivers and OPC servers to make the communication between LabVIEW and the hardware very easy. E.g. the widley known distributed Fieldpoint devices and the well-known DAQ/SCXI systems will come with OPC servers.
    Please check it out: www.ni.com/opc
    Hope this helps
    Roland

  • Logos for communication between Fieldpoint modules?

    I have a system with two Fieldpoint network modules: one FP2000 and one FP1601. I am presently using datasocket calls using the lookout protocol for the FP2000 to read/write the I/O items on the FP1600. There is normally no PC connected to the two. Our NI salesperson visited today and told me that the recommended means of communication between Fieldpoint network modules is using Logos. He also mentioned using the "FieldPoint Publish Data" vi. I searched all the documentation I have and can't find anything on Logos, or any way to make any sense out of what he said. Can someone please tell me exactly what he meant and how I would implement it? I have LabView RT and FieldPoint Explorer, but no other software.

    Richard,
    Logos is the name for the NI Ethernet Protocol. It was originally developed for networking of computers using Lookout. Using DataSocket with the Lookout URL specifier, is instructing the DataSocket client to use the logos protocol or lookout protocol (the terms are interchangeable). The FieldPoint Publish Data.vi is a VI that can be run on embedded targets (e.g. (c)FP-20xx series) that can be used to make data available via the NI Ethernet protocol. For example, if you measured two sensors and calculated a value from the two sensors, you could use the Publish Data.vi to make the calculation result available from the FP-2000.
    Regards,
    Aaron

Maybe you are looking for