Opc server on compact fieldpoint 2100

Dear all
I am having a bit of trouble on where to start with setting up OPC tags for the customer to view.  I have a cFP-2100 in machine which is installed at a power station.  It isconnected by ethernet back to a PC in a server room.
All outputs are normally hardwired using an analogue output card to give the values, but this customer has requested I use OPC.
They browse the available OPC servers on the network and find
National Instruments.Variable EngineNational Instruments.Variable Engine.1National Instruments.OPCFieldPointNational Instruments.LookoutOPCServer  
Now I can easily change the code to ouput the instruments values to some new shared variables, but how do I go about creating a tag name?
Another question I have the NI devloper suite (NI professional devlopment system) with teh datalogging and supervisory control module 8.2.1 and the labview industrial automation OPC servers 5.1.  But i cant find which disk they are on?  any ideas?
any help would be much appriciated.
regards,
Chris

Dear Monkins
Please see this webcast of how to create custom tags through our National Instruments LabVIEW software and programmable automation
controllers-to any PLC using the new NI OPC servers
http://zone.ni.com/wv/app/doc/p/id/wv-263
Just as a note, from a performance standpoint, there is no difference between these two
methods when the DataSocket is configured correctly. At run time,
accessing the tags will happen at the same rate and with the exact same
behavior. To configure the DataSocket connection correctly, ensure that
you open and close a connection to your tag only once when reading or
writing from it iteratively, as shown in the following screenshot. From an implementation standpoint, there is an important difference
between the two methods. The shared variable method uses an OPC client
that is built into the shared variable engine. This OPC client is added
by the DSC module. In order to bind shared variables to OPC tags, you
must have the DSC module installed. The DataSocket method uses a
different OPC client built into the DataSocket implementation in
LabVIEW. Because DataSockets are a standard part of LabVIEW, you do not
need any special software modules to access your OPC tags with this
method.
Please see the KB below which describes how to use the OPC server in Labview through using Datasocket.
http://digital.ni.com/public.nsf/websearch/EA15F53DB6FECCA5862567240064DF09?OpenDocument
Also, the below link, describes methods for binding a shared variable to a FP channel; please see method 1 which utilizes this NOT using the DSC module.
http://digital.ni.com/public.nsf/allkb/FA610367EC62574186257118005089F2?OpenDocument
Many thanks for using the NI forums and I look forward to your reply.
Kind regards
David
Applications Engineer
National Instruments UK

Similar Messages

  • Ftp server on compact fieldpoint

    How
    do I reconfigure the FTP server running on a cFP-2000? For security
    purposes, our IT people want us to get rid of the anonymous FTP login,
    or to disable the FTP server entirely. I need to create user/password
    permissions. A thread in 2004 discussed options, but nothing seems to
    work.  Thanks

    No worries David, you were right, this is a more appropiate forum in general for those questions, but not a big deal if it is handled else where. I threw up that link so that others would know that it is being discussed in a seperate thread. But like I said no worries
    -GDE

  • Why does my Fieldpoint OPC server time out?

    I'm using Fieldpoint Explorer 3.01 with 1600 ethernet modules. I'm using Wellspring Solutions' Object Automation as an OPC client to read and write to I/O. Everything works fine on one computer running Win NT 4.0. Another computer, however, is running NT Server 4.0, and the OPC reads/writes from Object Automation work for exactly 1759 seconds (or approx. 121 minutes), and then the Fieldpoint Server "times out", and the only way to get it to work again is by shutting down and restarting Object Automation, assumedly this somehow reinitializes communication with the server. This is a repeatable error that occurs at exactly the same time, every time. This only happens with the National Instruments Fieldpoint OPC server (I'm
    using several) on one of the machines. I tried reinstalling the Fieldpoint OPC Server several times to no avail. I've used other OPC clients (from OPTO22, or Rockwell, Matrikon, Kepware) and can't communicate until Object Automation is shutdown and restarted. Any help or ideas on how to further troubleshoot would be appreciated, thanks.

    Aaron, attached are 3 log files generated in a test that I ran. The test used Object Automation to turn on and off a relay channel (OPC item: Common FP Res\FP-RLY-420 @4\Channel 1) every 10 seconds. I used the Matrikon OPC delegator with the OPTO22 Test Client (written by Rockwell) to monitor the channel at the same time (the delegator would NOT work with Object Automation directly). The OPCDelegatorOPTO22TestClient.txt file is the log file for this client. Basically, the test started around 13:07 and lasted the usual 121 minutes. Then the OPC writes stopped around 15:08, at which time I tried to manually read and write to the channel using the OPTO22 client, generating the errors towards the end of the logfile. Incidentally, I don't k
    now what the errors at the beginning of the file are, but there are no noticable problems until after 121 minutes. I then tried to use the Kepware OPC test client with delegator to read and write to the channel but this also did not work, and the logfile OPCDelegatorKepwareTestClient.txt is for that test. The other logfile (OAlogfile.txt) is the logfile generated by OA, see the end of file for the error. They should all be text files, not sure why one of them is listed as binary below. Let me know if this helps or if there is anything else I can provide.
    Attachments:
    OAlogfile.txt ‏526 KB
    OPCDelegatorKepwareTestClient.txt ‏50 KB
    OPCDelegatorOPTO22TestClient.log ‏517 KB

  • Communication from a fieldpoint also acting as a OPC server to a simatic 545 through serial?

    Hi...
    I'm supose to control a breweri, and right now it is controlled by a simatic 545.
    Is it possible for fieldpoint and connect directly to the PLC with OPC using serial?
    I have the software to run NI's OPC server, but haven't bought a fieldpoint yet.
    So i was wondering if this is possible to reuse the I/O oirts of the PLC instead of buying new I/O boards for the fieldpoint, which is very expensive.
    Thanks..
    Carsten Toft
    Aalborg University Esbjerg, DK

    The easy scenario is to use FieldPoint with the OPC server to provide distributed I/O for your HMI/SCADA application.  The same HMI/SCADA application can communicate via OPC to the Simatic 545 thru serial.  In this scenario, the data move from FieldPoint to Windows XP to Siemens.  For slow processes and current computing technology, this scenario typically works well. 
    If you need FieldPoint to communicate directly over serial to the Siemens Simatic, you will need communications support in LabVIEW RT for the Simatic PLC.  Typically what is recommended is to use a Modbus gateway and the LabVIEW RT modbus VIs to communicate Modbus protocol from Fieldpoint to the gateway, and the gateway then communicates over serial to the Simatic. 
    here are the modbus vis
    http://sine.ni.com/nips/cds/view/p/lang/en/nid/201711
    here is a reference for gateways
    http://www.woodhead.com/products/automation/gateways/
    Preston Johnson
    Principal Sales Engineer
    Condition Monitoring Systems
    Vibration Analyst III - www.vibinst.org, www.mobiusinstitute.com
    National Instruments
    [email protected]
    www.ni.com/mcm
    www.ni.com/soundandvibration
    www.ni.com/biganalogdata
    512-683-5444

  • Fieldpoint OPC server freezes up

    A Honeywell DaVinci system communicates with Fieldpoint OPC server. After working properly for hours, the analog outputs would not respond to write updates from DaVinci system. I tried to use FactorySoft OPC client to connect to the Fieldpoint OPC server and also could not manipulate the analog outputs. However, I could still change the outputs using the Fieldpoint explorer. Please advise how to fix this problem.

    What version of the Fieldpoint OPC server are you using? There was a memory leak issue in 3.0.2.177 (I think that was the rev.). Is the opc server memory usage increasing?
    See also:
    http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=137&HOID=5065000000050000000DF60000&HTHREAD=000062989&UCATEGORY_0=_18_%24_17_&UCATEGORY_S=0
    Matt

  • OPC Server for Labview/PXI-RT

    Hi all,
    can i access Labview on a PC/WinXP or a PXI/RT System  with a
    OPC-Client (eg.:WinCC/Siemens) like a Compact Fieldpoint over the NI
    OPC Server (NationalInstruments.OPCFieldPoint). Exist a OPC-Server for
    Labview/PC/PXI?
    Thanks
    Achim

    Here you can find information concerning this issus:
    http://digital.ni.com/public.nsf/websearch/CC9CDD577F041786862572120061EB5A?OpenDocument
    Hope this helps!

  • DSC for compact fieldpoint​(cFP)

    which IO server type should be used for building DSC application for compact fieldpoint target?
    when i use my computer as target then i get various options for IO server type like custom VI,opc client,epics,data set marker,modbus.But when i choose compact fieldpoint as target i got only epics and modbus options.Is there any problem with my HW/SW or with my concept?
    kindly clearify.....
    regards
    vks

    Hi,
    if you just wanna use Labview for logging and graphics (using Ethernet) AND you do NOT use a Real-Time cFP-Controller then you do not need Labview Real Time.
    E.g. if you use NI cFP-1804 - Ethernet/Serial Interface for Compact FieldPoint.
    (http://sine.ni.com/nips/cds/view/p/lang/en/nid/202527) 
    If you are using a Real Time Controller than you will NEED Labview Real-Time. 
    You cannot work without it!!!
    Best regards
    Dippi 

  • Compact FieldPoint and Shared Variables

    Hi Real-Time community,
    let me first to describe my problem: I have a project running perfectly on Windows XP machine. The Real-Time Target (compact FieldPoint) is acquiring a data from different sensors and sends them via Shared Variables to the host machine (WinXP). Now this host application has to migrate to Windows 7 machine, which second Ethernet port is also connected to the compact FieldPoint's network. I have created an installer, it run on Win 7 computer but I I see no data there. Shared Variables are standart network-published. What else I need to configure to get Shared Variables visible over there? Thank you in advance for any helpful hint.
    Armen

    Hi,
    we do have the full edition of Signal Express, this is not the problem. We are already logging the information comming from our cFP-1808 : TC-120 and AI-111 module. The problem is that the AI-111 module is a 4 to 20mA module, and we have thermocouple connect to it. We want to read temperature in Signal Express instead of mA.
    There's a option in MAX where you can add scaling to a cFP module. This scaling work in MAX, in the OPC server of the cFP, but not in Signal Express. In Signal Express, you still read the mA value.
    I know we can add a formula in Signal Express, but we don't want to do that, when there is an other option in MAX.
    Thanks

  • How to install "Compact FieldPoint Embedded Data Logger Example Program" on cfp2200

    i finally managed to get max to see the devices of my cfp2200.
    (i had to disable every unused networkadapter due to overlapping subnets)
    now i want to deploy the example programm "Compact FieldPoint Embedded Data Logger Example Program"
    http://zone.ni.com/devzone/cda/epd/p/id/3221
    i therefor have tried to install the runtime 8.5 on the target. however this is not possble, because i have labview 2010 installed and it gives the message:
    "the host has a newer version available"
    ok. runtime 2010 should work to - not?
    i open a new project - import my *.iak-file and drag-n-drop the content of "cfp_data_logger_source.zip" onto the target.
    now if i open the file cFPEmbeddedDataLogger.vi the run-button is cracked and by pressing it an errorlist opens.
    the errors say stuff like:
    target does not support this function/subvi
    and
    vi has been modified with a different applicationinstance
    please help me to make this work.
    i know that it is possible to get the programm to run on the cfp2200 even dough it is primaly designed for the   cFP-2000, cFP-2010, cFP-2020, cFP-2100, cFP-2110,
    cFP-2120.
    big THANX already for you help !!!!!

    Hi, thanks for your help=) I've manage to drag the file into my targeted controller. I am now doing the setting of the data logger program, but there's one thing I'm unsure of. May I know what does it mean by the cFP controller clock? http://zone.ni.com/devzone/cda/tut/p/id/3219 . Thanks. =)
    Log On Startup
     Start logging when the controller powers up.
    Start Log Time
     The time to start logging.
    Stop Log Time
    The time to stop logging.
    Note: Make sure the clock is set correctly on the controller. The settings described above refer to the cFP controller clock.
    Log Rate
    The number of milliseconds to wait between each acquisition.
    FP Drive For Data Files
    The drive to store the log files in. The C: drive is the default for all cFP controllers. If you want to save to the removable CompactFlash drive on the cFP controller, select the D: drive.
    Digital "Pause" Line
    The Digital Input item to use as a "pause" button for data logging. Logging pauses when the signal is high. When the signal goes low again, a new file is created and logging continues if appropriate.
    Note: Use only Digital Input items for the Digital "Pause" Line.
    Tip: You can use DIP Switch 3 to block the current data from being logged. This switch works the same way as the Digital "Pause" line.
    Logging Session Tag
    Is stamped on the spreadsheet that the data logger creates.

  • Launch DS in compact fieldpoint

    Hi,
    I have two simple VIs that uses datasocket, Write DS.vi and Read DS.vi.
    I'm using the function  Launch DS Server if Local URL.
    In my computer works ok, but when I execute my VI in a compact FIeldPoint (cFP-2020), DS server don't works. It appears the messsage "Launching the DataSocket Server is currently not supported on non-windows platforms. Please try connecting to a DataSocket Server running on windows." (application TargetOS is FALSE).
    Are there any solution?
    Thank you.
    Vicen
    WinXP / LV 7.1
    Attachments:
    Launch DS Server if Local URL.vi ‏66 KB
    Write DS.vi ‏70 KB
    Read DS.vi ‏67 KB

    Look for "Publish.vi" in the FP palettes.
    That VI and its associates will deploy a DS Server and allow you to read and write from same on a FP unit.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • 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

  • Internet connection of Compact Fieldpoint controller

    Hi all, I have this Compact Fieldpoint controller of cFP-2120, I need to make it stand-alone & also to be able to get my data directly from internet. Is there anyone who know's how to do it? Thanks=) For the controller's mannual I came across this sentence of "In order to configure the cFP-21xx, it must reside on the same subnet as the host PC. If you want to use the FP-21xx on a subnet other than the one the host PC is on, first connect and configure it on the same subnet as the host PC, then reassign a static IP address for the subnet where you want it to be
    and physically move it to the other subnet." Do you all know what does it mean? Is this feature for stnad-alone or for internet connection?=)

    Hi!
       You seem a little confused about networks, am I right?
       The thing is that to configure your cFP, it must reside on the same subnet as your PC.  I make an example: you can assign your PC a static IP address, example 192.168.168.1, subnet mask 255.255.255.0, then your cFP-2120 will have to be inside this subnet, that is 192.168.168.2 to 192.168.168.254.   If you connect your PC to cFP-2120 through a cross ethernet cable, you can set your PC IP address to 192.168.168.1 and cFP-2120 to 192.168.168.2.   With this gear, you configure, program, and test your cFP application.
       If I understood your needs, you need to place the cFP-2120 remotely, and collect data over Internet, isn't that?  If so, one way for doing this is activating a web server on the cFP-2120, for which you can find examples.
       The next step is to be able to view your cFP-2120 remotely, because of course you can't keep IP addresses you used for configuring cFP-2120.  When placed remotely, cFP-2120 will reside on a different LAN, I suppose, and you need to access it from your PC.  Unfortunately, I have no experience on this, but I think that once you configure cFP-2120, create application, create the web server, then you can turn to remoting cFP-2120.
       Some useful application notes are here, in particular take a look at links at the bottom of the page.
      Hope this helps!
    graziano

  • Write JPEG file error on Compact FieldPoint

    Hello!
    I'm using Compact FieldPoint 2120 and LabVIEW 8.2. I'm trying to capture an image of a front panel and to save it into Compact FieldPoint using the "Write JPEG file". Unfortunately, it gives the error 1.
    I indicated c:\<jpeg_file_name.jpg> for the path.
    I switched the target to "My computer" and the code works correctly.
    Is that a problem of the path or VI Write JPEG file cannot be impemented on Real-Time target, such as Compact FieldPoint?
    Thank you!

    Well, that's true that Real-Time does not support Write JPEG file (this is the first problem). I'm using now Write BMP file insteed. The second problem, verified also in my practice, is that the Front Panel does not exist too on Compact FieldPoint.
    My aim is to develop web-interface to deal with the Compact FieldPoint from any computer. That is true that it has its own built-in Web-Server, but it doesn't have a script-executive environement. My idea was to create a custom "web" server running in parallel with the principal Web-Server to execute VI scripts.
    For that purpose I used TCP Listen -> TCP Read -> TCP Write runing on the port 82. I can send from any browser the request http://<IP address>/<script.vi>?<params> and my custom server parses the request and executes the <script.vi>. Then to avoid the problems with HTTP protocol I write the redirecting request to the port 82 like <meta http-equiv="Refresh" content="0; URL=<result_page.html">. So, It works.
    The result_page.html must represent the acquired data from the Compact FieldPoint channels. So, I execute a requested script to show the specified data into Graph waveform and then to take a snapshot and to save to the Compact FieldPoint. Then the result_page.html contains the link to the saved snapshot picture.
    Once executing the requested VI script, the Invoke Node gives the error 1003 stating that "the VI is broken etc...". I think that is because of the script attempts to take a snapshot of a panel which doesn't exist...
    Maybe somebody has an idea how to view the acquired data in browser ?
    Message Edited by Mons on 07-10-2008 06:06 AM

  • How to read enumerated values from an OPC server via Datasocket

    Hi Labviewers,
    I am using LV8.2 and I am trying to find if it is possible to read enumerations from an OPC server via Datasocket, not just the values.
    I can successfully read a value for an OPC server via Datasocket and I get a value for example 3, is it possible to get the enumeration/string that corresponds to this value i.e. "Open".
    Many thanks in advance
    Dimitris

    Hi Sarah,
    With the input type as variant I get the following response:
    1                                     <-This is the current numeric value of the parameter
    4 Attribute(s):
       'Quality' -> 192
       'TimeHigh' -> 29861723
       'TimeLow' -> -665408304
       'Timestamp' -> 39.238E+3
    With the Input set to         Enum constant I get no values or strings coming back. With the Input set to                Ring constant I just get the numeric value   
    Dimitris   

  • Problems using Modbus TCP accessed by NI OPC Server

    Hi there,
    i'm using NI OPC-Server to access a measurement module. The buildup is quite easy, my system with NI OPC, a modbus gate and there the module connected with RS485.
    There's a thermocouple to provide me some sample data.
    But there's the point. I know, my data is in the Holding Registers and I can access them, but every data type I'm trying doesn't bring my my data out, just any other (sometimes Huge with e34, sometimes very small like e-13...) sorts, i can't understand.
    The type provided by the module should be single precision.
    In Lookout the address used to be is 41000 in Labview it's just 999 and in the "target" OPC-Server I get some values at 401000 but not useful.
    I also get the same results accessing 301000 in different types.
    Read/Write or Read Only is equal.
    I've tried to tell my OPC that the values are Strings, Floats, Words, BCD and all other possible ways OPC offers me, but nothing results in a usable temperature.
    I hope I missed something and you could suggest it.
    Cateros
    Solved!
    Go to Solution.

    Thanks for your reply.
    in LabVIEW I'm using the provided Modbus Libraries. If I unbundle the Holding registers, my value appears at Holding Register [0], I'm type casting it to single and get the sample temperature. (Address 999->unbundle->typecast->value)
    In NI OPC, I'm reading ( [depends on zero based addressing]  300999/301000 equal to 400999/401000) an already typecasted Holding Register [1] compared to LabVIEW (and the value changes in the second or third digit behind the comma and they are changing at the same time). Data type in the tag is float.
     Another disturbing thing is even if I change in the options "using zero-based addressing in registers" my value does not change.
    If I'm reading two addresses close to each other (as you mentioned 401000-401001) I'm getting an unknown data type and no results. How do I read multiple addresses without such errors? And how do I specify a special register to read?
    Scaling should not be the problem, I am having three ways to get my value (FTP-Server on the gate (just a *.dat file with correct type), software the the module manufacturer (while measuring and configuring the module) and LabVIEW(as can be seen above)) .
    Sadly, I have not found any useable modbus documentation about the module (just it can use modbus, you have the registers, you could read/write and fine)
    When I'm adding a second couple to the module, in LabVIEW Values in Holding Register [2] and Holding Register [3] appear and are changing.
    Cateros

Maybe you are looking for