NI OPC server no DSC

I have been digging around for a while and am having difficulty finding anything that shows me how to get my tags into LabVIEW. I have the OPC drivers for numersou PLCs and are connecting to a GE 9030 (specifically a 341 model). I have set it up in the NI OPC servers and can communicate.
How the heck to I get the tags into LabVIEW. Everything I find using IO Server which is part of DSC which I do not have (and do not plan on getting). I was led to beleive this would not be difficult to read tags in any PLC using these drivers... Any help is greatly appreciated.

The link that Brian provided:
http://digital.ni.com/public.nsf/allkb/DD1E23328AF0A303862570A4006F4134
states the following:
"If your application uses a subset of the DSC Module that does not
require the RTS, it is still necessary to include the Enhanced DSC
Deployment Support in your installer.  For more information about which
DSC functionality requires the RTS and which does not, refer to the
related links."
One of those links was this one:
http://zone.ni.com/devzone/cda/tut/p/id/3061
Which states:
"The LabVIEW DSC Run-Time System correctly installs the necessary and
additional software as well as provides all the configuration tools,
the Tag Engine, historical data logging, network data access, security,
and other features provided by the LabVIEW DSC Module."
There seem to be 4 components here:
DSC Development System (~$2600)
DSC Run-Time System (~$800)
Enhanced DSC Deployment Support for LabVIEW 8.x (free add on installer when you have DSC Development System)
Enhanced DSC Run-Time Support  (Can be checked inside LabVIEW project when you're building an application)
Which features can be used in a deployed application (EXE) without purchasing the $800 DSC RTS (Run-Time System)?
When do I check the "Enable Enhanced DSC Run-Time Support" box when I build the EXE?
When do I include "Enhanced DSC Deployment Support for LabVIEW 8.x" when I build my installer?
OPC is not listed above with "configuration tools,
the Tag Engine, historical data logging, network data access, security".
Can I bind a Shared Variable to an OPC tag without DSC Development System or DSC RTS?
I seem to be able to deploy a library with my OPC I/O server (which I created with my DSC Development System) and a library with my shared variables to the target PC.  However, when browsing with DSM (Distributed System Manager -- which I downloaded and installed on the PC), while I can see both server and variable processes, the I/O server is not listed under the server process.  The dependent shared variables are listed in the variable process.  There are no variables included in the server LVLIB.  All dependencies reside in the variable library -- which seems to be deploying fine, despite some admonitions indicating the contrary.  The library with the server may not be deploying because I need the DSC RTS to deploy an OPC I/O server.  This same behavior has been duplicated on a PC with LabVIEW without DSC installed.
Clear as mud?  Thanks for the help!
Message Edited by LabBEAN on 02-13-2009 05:31 PM
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs

Similar Messages

  • Communicate With OPC Server

    I am Using the PLC of Unitronics they have there OPC server called uniOPC sever i need to communication the OPC server using DSC what are the steps to communication.I am new with Labview.

    How Do I Connect to an OPC Server Using DataSocket?

  • Interfacing PLC siemens S7_300 and LabVIEW DSC using siemens OPC server

    Does anyone already interface Siemens PLC S7_315-2-DP with LabVIEW DSC using Siemens OPC server?
    Is that a good solution? Are there any hidden problems?

    The use of an OPC Server is the way to go when dealing with LV. If you already have Siemens OPC Server then use that. Otherwise, NI has a product called IA Severs/Lookout Protocol Drivers (LPD), which has a large selection of drivers for PLC's. After configuring the driver, LPD is the OPC Server for the device.

  • Unable to access only Read Write addresses of AB Micrologix 1400 PLC using NI DSC and NI OPC server

    Hi,
    I have been using NI DSC and OPC servers (NI and Kepware) to communicate with Allen Bradley Micrologix 1400 PLC (1766-L32BXB). Recently at one  site I found that I could access Process values from the PLC correctly (Read Only tags) but could not access the Read Write Tags at all. The latter are addresses to which it should be possible to write Set (i.e., references) values from MMI or PC software. I am able to do so from the MMI not from the PC software. I get communication error message on the MMI and PC, mentioning the PLC address being accessed (e.g. N7:0).
    Support from the supplier is not available. Hence can anyone let me know if ladder logic could have been written to prevent PC software based access of Read/write addresses (N7:0 to 9 in this case), while permitting access to Read only addresses? Is the problem at the PLC end or OPC server end? Is there a way to get around this?
    Thanks in advance.

    The OPC Server cannot force Outputs so if th registers in question are the outputs of ladder rungs you cannot write to them via the server. The controller will accept the write from the server but will not execute the write. In some cases the server event log will post an error if it is the PLC. Do you get errors when you try to write and if so what are the posted error messages.
    Fred Loveless
    Kepware Technologies
    http://www.kepware.com

  • Is it possible to connect labview with opc server without using NI dsc Module ?

    Hellow sir,
    I want to get data over labview using OPC server and i am not using any dsc module vi (Alams, print, GUI, security).I am using share variable to get data from OPC server to labview. Now i want to deploy that application to third party computer. (where there is no NI software is installed)
    i am using labview 8.6 and 2009.
    Many ? like....
    1) what is the procedure to install that application in third party computer.
    2) Do i need to use my dsc run time licence..?
    waiting for your valuable feed back.
    Thank you.
    CLAD
    Labiew programmer

    Hi, When you connect to NI OPC Server by creating New I/O Server > OPC Client. You will see all registered OPC Servers running on local machine or remote machine. I used KepServerEx from Kepware and LSIS OPC Server from LG with no problems. Just make sure that the OPC server is running.
    Hope it helps
    Waleed El-Badry MSc.,MCPD, ISTQB Certified Tester
    Assistant Lecturer
    Mechatronics Department
    Faculty of Engineering
    Misr University for Science & Technology
    Attachments:
    LG.png ‏57 KB

  • What is the best way to detect loss of OPC Server connection when using DSC Tags?

    I'm using the DSC Module on a new project and I'm pretty impressed so far. The HMI Wizard has saved me quite a bit of time.
    My application is configured where the DSC Tags are connected to remote OPC Server Tags.
    The issue I'm having is that I cannot detect a loss of the OPC Server when the application is running. Read's of the front panel controls/indicators still return values and the little "connection" icon next them is still green. Even if the connection icon turned red it wouldn't help since the Front Panel is not visible when the main application is running. It is a Sub-VI that's in charge of OPC Data Interfacing. The rest of the application uses the data from the OPC Sub-
    VI.
    I cannot effect a change on the OPC Servers, so I need a method of detection when the Server is lost on my end.
    Any ideas on the best way to do this?
    Thanks,
    Jim

    Hi Jim,
    Ideally, error-reporting and -handling should be the way to handle this. However, if errors are not reported/handled as is sometimes the case with OPC, a quick-n-dirty way to do this would be to check for a "heartbeat" signal from your OPC Server. This could be a boolean tag which toggles On and Off (or a counter ticking). You then read this Tag in DSC in a slow loop using the Read Tag VI (not the front-panel control). And keep track of the Changed? output from this Read Tag VI.
    As long as the 'Changed?' output is true, you are receieving data from the OPC Server, and hence it's alive. You may add some deadband logic to wait for a specific period of time before declaring the Server's really dead!
    Hope this helps,
    K
    halid

  • Are there any example vi's for implementing a circular buffer between a plc, opc server, and labview dsc??

    I am storing a block of data inside plc registers and reading this group into labview as a continuous set of datapoints. I am counting the number of scans in the plc and sometimes the number of points collected inside labview doesn't match.

    To explain a a little bit about tag updating:
    The LabVIEW DSC tag engine is not just updated on any change of the value within the plc. There are, in fact, several "deadbands" that must be crossed before those tags are updated:
    1) The OPC Server has a deadband - where the plc register value has to change a certain % before it is recorded.
    2) In the LabVIEW DSC moduel, there is an I/O Group Deadband that determines when the tag engine is actually updated.
    Both of these deadbands must be satisfied before a new "value" is recorded in the LabVIEW DSC tag engine.
    Therefore, I would check your OPC Server's deadband (configurable in the OPC Server configuration utility) and also the I/O Group deadband for those tags (configurable in the tag configuration
    editor).
    If this doesn't resolve the issue, please let me know. Thanks.

  • Has anybody used DSC or the OPC server to access DNP 3.0 devices

    I have a potential client that has some devices that communicate using DNP 3.0. I see that DNP is supported in OPC server 5.1. I have zero experience using DSC and OPC, but I want to send this client a small demo app so he can see LabVIEW working with his equipment.
    If anybody has done this, could you please give me some pointers on where to start, or better yet, some example code.
    This will be on WinXP, LabVIEW 7, OPC 5.1 and if needed, DSC 7.
    Thanks
    Ed
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

    Thanks Robert,
    We already have DSC 7, so if it�s easier and/or quicker, I�ll probably end up using that. I guess what I need to do run through the Introduction to DSC so I at least know the basics of it.
    One question, do I need to have the customer�s equipment to configure the DNP connection so I can test communication with the Server Explorer? Or do I just need to know the format of the Tags to configure so he can test it.
    Thanks Again
    Ed
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

  • OPC server items not found with NI DSC nor datasocket

    Hi,
    I am using LabVIEW 2009 SP1 and an OPC server from ifak (isPro Multiserver v 2.5.1) on a windows XP professional SP3 platform.
    If i use the datasocket vi "browse for URL" then I can navigate to the server, it starts the server (I can see the hardware "coming to live" and logging on to the UUT -the network is a profibus network with 1 USB/profibus gateway as master and 1 UUT profibus slave. However, when navigating through the branches of the server I can not navigate to the OPC items. I can navigate to the point where they should be, but then the browser waits a few seconds and then displays "no items" and places a red cross through the icon.
    When using the manufacturer OPC client, I can navigate to the items and I can see them, read them or write them. The funny thing is that I can also browse to these items using the NI Quick OPC client(!) When using datasocket VIs, or when configuring a project using the DSC module --> new I/O server --> OPC client --> browse to OPC server and then trying to configure the labview library to hold the OPC items, I never get to see the actual items.
    This seems to be a DCOM problem but I can not believe that, since
    1) the manufacturer OPC client sees the items
    2) the NI Quick OPC client sees the items
    3) I followed all guidelines from
    http://www.automation.com/pdf_articles/OPC_and_DCOM_5_things_you_need_to_know.pdf
    and
    http://www.automation.com/pdf_articles/Troubleshooting_OPC_and_DCOM.pdf
    and I also set the OPC server access to "the interactive user", as recommended by NI.
    The OPC server and OPC client reside on the same computer, but in any case I also disabled the windows firewall. There are no other firewalls running.
    I am completely stuck in this application, since I can access the OPC items using any client, but I can not access them via LabVIEW
    If anybody has a suggestion, please help me.
    best regards,
    Stijn

    Hi Stijn Schacht
    These seems to be some bugs with OPC Client instances created using LabVIEW 2009 SP1,  when we tried to communicate to Siemens S7 PLC. 
    Basically when deploying the shared variable library configured with OPC Client instance, it crashes the SVE.
    From all your observations, what i can suggest is, try with LabVIEW 2009 along with DSC 2009.
    Thanks,
    Vijay Jayabalan.

  • DSC toolkit and OPC server

    Can I datalogging data from OPC server directly to SQL without "datasocket", and how, example maybe?
    Thanks
    Rookie; LV 2011 on WIN 7

    Dear hlod,
    Can you provide me more information about your application, and why it is'nt possible for you to use DataSockets?
    If you want to use OPC servers for connecting to PLCs, I can recommend the followings:
    Here is a great tutorial, how to work with OPC Server to connect to PLCs: 
    Connect LabVIEW to Any PLC Using OPC http://zone.ni.com/devzone/cda/tut/p/id/7450 
    After the tutorial you're able to communicate with PLCs through NI OPC server, using I/O Server instead of DataSockets.
    Datalogging into Databases are also made easy with LabVIEW DSC Module. Look at the following tutorial:
    Data logging Options Using the LabVIEW DSC Module http://zone.ni.com/devzone/cda/tut/p/id/12525
    For more specific solutions, feel free to browse either the LabVIEW DSC Module Help from LabVIEW, or Online: http://zone.ni.com/reference/en-XX/help/371618G-01/
    If you have different, more custom application, which I can help you with, please post on forum some more specification of your task you want to do.
    Best Regards,
    Tamas Szekely
    Applications Engineer
    National Instruments

  • Response time between LabVIEW w/DSC module and RSLinx OPC server hosting FlexLogix PLC tags too long

    We are experiencing communication response time delays between LabVIEW with DSC module and RsLinx OPC Server hosting all FlexLogix PLC tags (around 500-600 tags).
    The nominal response time for the system watchdog is < 500ms, but we occasionally have spikes of up to 1.5 seconds once every few days even when the system is idling.
    Changing more than six PLC connected shared variables at the same time from LabVIEW also causes the watchdog response times to spike above 500ms.
    Our watchdog is programmed so that LabVIEW toggles the watchdog bit to 1 as soon the shared variable event detects that the PLC has toggled it to 0. The PLC, however, waits 300 ms until it toggles it.
    Our system:
    Windows XP SP3
    LabVIEW 9 F3
    RSLinx Opc Server v2.54
    Allen Bradley FlexLogix PLC

    What is your update rate set for in the RSLink OPC server?
    You aren't toggling the same flag from both ends are you?
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • LabVIEW DSC 2011 / OPC Client IO Server / Can I write to the OPC Server using OPC Groups?

    Hi
    I am using LabVIEW DSC module as a OPC client. My Shared Variables are binded to automation system OPC Server via "OPC Client IO Server".
    On the OPC Server side it seems that the every write commands comes like one item at time, not like grouped.
    Now I have tested this with the NI OPC Server as server and KepServer and LabVIEW DSC IO Server as OPC Clients.
    When I use the NI OPC Server : OPC Diagnostics there are different events messages when the update request comes from KepServer or LabVIEW DSC.
    There are log files on attachements for both write events.
    Attachments:
    Data from the KepServer.txt ‏6 KB
    Data from the LabVIEW DSC OPC Client.txt ‏18 KB

    Hello Pentsi,
    I have received confirmation (from the PSE in the US) that DSC doesn't support group writes
    There however work-arounds that might provide a solution:
    - The first solution I had in mind was like this. Update the 50 OPC items as fast as possible.
    Then use a 51st item as synchronization OPC item to check/indicate if new data has arrived/has been set/is available.
    So LabVIEW sets 50 OPC values as fast as possible. The 51st value becomes goes from false to true when the first 50 values are written.
    When this (51st) value is true on the OPC server you can read out the first 50 values (from the non-LabVIEW side). When you've read out these values, then you can set the 51st value back to false (from the non-LabVIEW side).
    In the meanwhile at the LabVIEW side you wait until the 51st value goes back from true to false.
    When it becomes false, then you write again those 50 values and afterwards set the 51st synchronization value from false to true.
    And this keeps on going...
    Note: Keep in mind that you only have to monitor one event at the side of the Automation System OPC Server in this case (the 51st) and based on an event occuring over there you can just do a group read of the 50 others. Also keep in mind that the maximum rate (6500 updates per second) from inside LabVIEW with the DSC Module OPC client I/O server was also mentioned in this document (http://digital.ni.com/public.nsf/allkb/63C043359F1​E12538625726E005BCD0C?OpenDocument).
    Could this be a possible solution for your problem?
    If you're using one of the OPC servers in this list (http://zone.ni.com/devzone/cda/tut/p/id/6417#toc19), then you can also use NI OPC Servers to update tags instead, which supports a faster update rate.
    Kind Regards,
    Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
    CLD, CTA
    If someone helped you, let them know. Mark as solved and/or give a kudo.

  • How can I write to a Siemens S7-300 PLC tag from OPC Server.vbai page by using a Knob object ?

    I am using NI OPC Server and I can read Siemens S7-300 PLC tags such as thermocouple values from the PLC. Additonally I can write manually a constant value to that tag by selecting it in the NI Distributed System Manager. And I can read the written value from NI Distributed System Manager or from NI OPC Server. But I can not write any value to the S7300 PLC tags such as by using a knob object at the NI Vision Builder AI Inpection (.vbai) page.
    Any help is welcomed. Thanks in advance.
    Attachments:
    manual_writing_to_plc.png ‏298 KB

    The tutorial at the following location explains how to use Vision Builder AI as a OPC server.
    https://decibel.ni.com/content/docs/DOC-18647
    http://www.ni.com/white-paper/13574/en
    To allow VBAI to connect to an OPC Server (i.e. act as an OPC client), you need to purchase and install the DSC Run-time System.
    Once installed, you can create an OPC I/O client using the Distributed System Manager, create variables bound to OPC tags, then create VBAI network variables that are bound to these variables.
    Another possible technical solution to connect to OPC Servers supporting Data Access 2.0 is to use the datasocket API in a Run LabVIEW step.
    http://forums.ni.com/t5/Machine-Vision/Read-and-Write-with-OPC-through-NI-Vision/m-p/2048278/highlig...
    Hope this helps.
    -Christophe

  • How to make SVE a visible OPC server to third party OPC clients?

    I've read SVE works as an OPC sever, but when I try to browse it with a third-party OPC client I get no items.
    Is there any configuration needed? Is DSC needed?
    http://zone.ni.com/reference/en-XX/help/371361E-01/lvconcepts/opc_conn_from_tpclients/

    Hi Keptat
    DCOM shouldn’t be the problem because you are not using the OPC server from an external computer or from other PC user, nevertheless, you can always try to do it.
    I’m attaching some links with information about the DCOM privileges and how to configure de SVE.
    Are you able to see others OPC servers with your clients?
    http://zone.ni.com/devzone/cda/tut/p/id/3371
    http://zone.ni.com/devzone/cda/tut/p/id/4679#toc3
    http://digital.ni.com/public.nsf/allkb/5C8A90CD57B279F286256C2C006F1EB4?OpenDocument
    Coamín Cruz
    NI México
    Mensaje editado por Coamín

  • How to create a OPC Server

    I must create a OPC serveur to distribute any value to other automation application.
    I now how to access to a OPC server (like the NI Demo server) but this time i must do my hown OPC server
    Thanks in advance and best regards
    (sorry for my english but i speek usually french!)
    Yves

    Yves
    Two possible solution come into my mind:
    1) You could use the LabVIEW DSC module, which is also an OPC Server. Then you define so-called "memory tags" within DSC and access them from your LabVIEW code using the read and write tag VI's or the logos protocol. What is annoying with that solution, is that DSC has no programmatic tag creation, so you must setup the tags manually outside of your code.
    2) Search the net for the "FactorySoft OPC Server Rapid Development Kit". Using that toolkit, a few years ago we programmed an OPC Server which can be embedded into LV code using the "Call Library Function Node". I am still using it. The advantages are that tags can be programmatically created in the LV code, the OPC server can be distributed royalty free (DSC=$$)and the OPC server will consist just of 3 small dll's which are easy to install. However some C/C++ knowledge and a compiler will are required.
    J' espère, que ces informations sont utiles pour toi
    Alexandre

Maybe you are looking for