OPC/DSC/Kepware Server

When I attempt to deploy my application, I receive "Deployment failed: The client process cannot communicate with the configuration server process....."
I have DSC Run Time module on the target machine and I can read the OPC tags on the Kepware Quick Client so I narrowed it down to something to do with LV. I've read about the "identity of interactive user" and I do have that checked in the DCOM for the client server.
Thanks in advance for the help/ideas.

Daniel, here is the error message I receive.
The OPC server is located on 192.168.1.10 so it is the same subnet
Attachments:
deploymenterror.JPG ‏43 KB

Similar Messages

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/63C043359F1E12538625726E005BCD0C?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.

LabVIEW DSC 2011 / OPC Client IO Server / Write by OPC Group...

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/63C043359F1E12538625726E005BCD0C?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.

Error when trying to set up OPC I/O server with LabView 2009

Hi.I get an error when I try to set up OPC I/O server with LabView 2009 and the DSC module. If I open an empty project, right click ”My Computer”. Select new / I/O Server… and then OPC Client, the following error appears: Unable to browse OPC Server from the selected machine.Error -2147467262 occurred at GetOPCServerList.viPossible reason(s):LabVIEW: (Hex 0x80004002) No such interface supported. I have tried to repair LabView, but with no luck. Any idea what it could be?

The problems are not related to each otherOk then. Lets try getting this solved. Lemme dig......

DSC Pull Server functional description

I am trying to find a functional description of how a DSC Pull Server fits into the model.
My understanding is that if I place a Custom Resource Module in the \WindowsPowerShell\Modules folder of the DSC Pull Server and I use Import-DscModule in the configuration that the file will be downloaded to the client auto-magically and used.
But what I am not clear on is MSI and EXE files with the Package Provider.
Do I place those some place onto he Pull Server and they magically get downloaded?
Do I need to define in the configuration that they need to be explicitly downloaded and placed in a particular path?
If so, is there some path they should exit in on the client (expected location)?
I am just trying to wrap my head around dealing with DSC and 3rd party software and the Pull Server model.
Thanks!
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.

Hi BrianEh,
Based on my research, to add content in Pull server, we need to Package each custom resource into its own ZIP file and copy it to Folder location (e.g $env:PROGRAMFILES\WindowsPowerShell\DscService\Modules), which has been defined during the Pull
server configuration, and also need to create a checksum file for each of the above ZIP files.
After configure the pull server and the DSC client, with patiently minutes the configuration should be downloaded to your client, however, you can also force this with powershell script.
For more detailed information to configure powershell DSC pull mode, please refer to these articles:
How to Deploy and Discover Windows PowerShell Desired State Configuration Resources
PowerShell DSC Resource for configuring Pull Server environment
Configuring PowerShell DSC Pull Mode
If I have any misunderstanding, please let me know.
If you have any feedback on our support, please click here.
Best Regards,
Anna
TechNet Community Support

Kepware Server OPC

Bonjour,
au sein de notre établissement (IUT) nous souhaitons mettre en place un serveur OPC pour réaliser une supervision globale du batiment (GTC + Supervision de systèmes de prod automatisés) à l'aide de LabVIEW. Nous avons acheté le Serveur OPC Kepware (KEPServer V5).
Le serveur OPC est installé sur notre "serveur de manip" appartenant à un VLAN de classe 3. Lorsque j'essaye de créer un client OPC (appartenant au même VLAN) sous labview en suivant cette procédure : http://www.kepware.com/Support_Center/SupportDocuments/KTSM00032_LabVIEW_Connectivity_Guide.pdf , tout se passe bien jusqu'à l'étape 3.2.2 lorsque j'interroge les variables liées leur valeur reste à 0 en permanence.
Pour m'assurer que le paramétrage du serveur OPC était OK j'ai interrogé le serveur OPC KEPserver grace à l'OPC Quick Client (sur un PC client du même du VLAN) et là les données interrogées sont bien actualisées... Donc à priori la config DCOM+pare feu est bonne.
Que dois je faire ?
Config Server :
Windows server 2008
Labview 2010SP1 + Module DSC
OPC KEPServer V5
Config client :
Windows 7 Pro
Labview 2010SP1 + Module DSC
Merci d'avance pour vos réponses.

Bonjour,
Je vais vous fournir une quantité d'information qui devrait être capable de vous aider.
Je ne suis pas sur que tous les liens vous soit utiles, néanmoins ils devraient vous apporter des éléments de réponses.
Vous trouverez les liens ci dessous :
1) How Do I Configure My Windows Firewall to Allow OPC Server Communication?
http://digital.ni.com/public.nsf/allkb/8FB44A1162DE1B5F862574440072CF0B
2) How Can I Connect to Remote OPC Servers from LabVIEW Using DataSockets or an OPC Client?
http://digital.ni.com/public.nsf/allkb/862567530005F09C862567660047D840?OpenDocument
3) Using OPC Client I/O Servers (DSC Module)
http://zone.ni.com/reference/en-XX/help/371618F-01/lvdscconcepts/access_opc_servers/
4) Setting Proper Access for Remote OPC Server When Using National Instruments OPC Clients
http://digital.ni.com/public.nsf/allkb/5C8A90CD57B279F286256C2C006F1EB4?OpenDocument
5) Why Can't LabVIEW DSC Connect to My OPC Server When Server Explorer and DataSocket Can?
http://digital.ni.com/public.nsf/allkb/9D1690C5B1CE1D25862572FA0053150D?OpenDocument
6) What Tools are Available for Debugging NI OPC Servers with DSC and DataSockets?
http://digital.ni.com/public.nsf/allkb/DB0594FAB81229818625756400018D37?OpenDocument
7) How do I Connect to The LabVIEW OPC UA Server VIs Using OPC Quick Client?
http://digital.ni.com/public.nsf/allkb/26767EBA64F112AF862579E9004BD679?OpenDocument
8) Connect LabVIEW to Any PLC Using OPC
http://www.ni.com/white-paper/7450/en/
+ Quelques liens que j'ai trouvé sur le même sujet qui pourrait être également intéressant :
=> http://www.automatedsolutions.com/technotes/opcserverconnectivity/Default.asp#DCOM%20Step%201
=> Unable to Connect with Remote OPC Client to KEPServerEX
http://www.kepware.com/KEP_KB/?solution=/_ui/selfservice/pkb/PublicKnowledgeSolution/d?&id=501400000...
=> http://www.kepware.com/KEP_KB/?solution=/_ui/selfservice/pkb/PublicKnowledgeSolution/d?&id=501400000...
=> http://www.automation.com/pdf_articles/Troubleshooting_OPC_and_DCOM.pdf
Je vous souhaite une bonne journée,
Cordialement,
Matthieu RICORD
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Été de LabVIEW 2014
12 présentations en ligne, du 30 juin au 18 juillet

Create OPC I/O server and front panel data socket problem

Hi all!
I installed the NI OPC server. When I try to create a new server I/O in a LabVIEW project I don't see the "OPC client" possibility.
Is something software missing?
Other question: I tryed to connect to OPC server using front panel data socket but my problem is same. When I click the numeric control and I go to the "data operation" menu there is no possibility to make data socket connection.
I don't know what is the problem.
I attached two pictures about my problem.
Solved!
Go to Solution.

Dear vajasgeri1,
do you have LabVIEW DSC module installed? Without it you will not have the OPC client funtionality.
And to configure DataSocket binding you need to go to the Data Binding tab in the Properties of a control.
BR,
Mateusz Stokłosa
Applications Engineer
National Instruments

DSC, SQL Server 2012 Enterprise sp2 x64, SQL Server Failover Cluster Install not succeeding

Summary: DSC fails to fully install the SQL Server 2012 Failover Cluster, but the identical code snippet below run in powershell ise with administrator credentials works perfectly as does running the SQL server install interface.
In order to develop DSC configurations, I have set up a Windows Server 2012 R2 failover cluster in VMware Workstation v10 consisting of 3 nodes. All have the same Windows Server 2012 version and have been fully patched via Microsoft Updates.
The cluster properly fails over on command and the cluster validates. Powershell 4.0 is being used as installed in windows.
PDC
Node1
Node2
The DSC script builds up the parameters to setup.exe for SQL Server. Here is the cmd that gets built...
$cmd2 = "C:\SOFTWARE\SQL\Setup.exe /Q /ACTION=InstallFailoverCluster /INSTANCENAME=MSSQLSERVER /INSTANCEID=MSSQLSERVER /IACCEPTSQLSERVERLICENSETERMS /UpdateEnabled=false /IndicateProgress=false /FEATURES=SQLEngine,FullText,SSMS,ADV_SSMS,BIDS,IS,BC,CONN,BOL /SECURITYMODE=SQL /SAPWD=password#1 /SQLSVCACCOUNT=SAASLAB1\sql_services /SQLSVCPASSWORD=password#1 /SQLSYSADMINACCOUNTS=`"SAASLAB1\sql_admin`" `"SAASLAB1\sql_services`" `"SAASLAB1\cubara01`" /AGTSVCACCOUNT=SAASLAB1\sql_services /AGTSVCPASSWORD=password#1 /ISSVCACCOUNT=SAASLAB1\sql_services /ISSVCPASSWORD=password#1 /ISSVCSTARTUPTYPE=Automatic /FAILOVERCLUSTERDISKS=MountRoot /FAILOVERCLUSTERGROUP='SQL Server (MSSQLSERVER)' /FAILOVERCLUSTERNETWORKNAME=SQLClusterLab1 /FAILOVERCLUSTERIPADDRESSES=`"IPv4;192.168.100.15;LAN;255.255.255.0`" /INSTALLSQLDATADIR=M:\SAN\SQLData\MSSQLSERVER /SQLUSERDBDIR=M:\SAN\SQLData\MSSQLSERVER /SQLUSERDBLOGDIR=M:\SAN\SQLLogs\MSSQLSERVER /SQLTEMPDBDIR=M:\SAN\SQLTempDB\MSSQLSERVER /SQLTEMPDBLOGDIR=M:\SAN\SQLTempDB\MSSQLSERVER /SQLBACKUPDIR=M:\SAN\Backups\MSSQLSERVER > C:\Logs\sqlInstall-log.txt "
Invoke-Expression $cmd2
When I run this specific command in Powershell ISE running as administrator, logged in as domain account that is in the Node1's administrators group and has domain administrative authority, it works perfectly fine and sets up the initial node properly.
When I use the EXACT SAME code above pasted into my custom DSC resource, as a test with a known successful install, run with the same user as above, it does NOT completely install the cluster properly. It still installs 17 applications
related to SQL Server and seems to properly configure everything except the cluster. The Failover Cluster Manager shows that the SQL Server Role will not come on line and the SQL Server Agent Role is not created.
The code is run on Node1 so the setup folder is local to Node1.
The ConfigurationFile.ini files for the two types of installs are identical.
Summary.txt does have issues..
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred during the setup process of the feature.
Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name:                SQL Server Database Engine Services Instance Features
Component error code:          0x86D8003A
Error description:             The cluster resource 'SQL Server' could not be brought online. Error: There was a failure to call cluster code from a provider. Exception message: Generic
failure . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation. .
It feels like this is a security issue with DSC or an issue with the setup in SQL Server, but please note I have granted administrators group and domain administrators authority. The nodes were built with the same login. Windows firewall
is completely disabled.
Please let me know if any more detail is required.

Hi Lydia,
Thanks for your interest and help.
I tried "Option 3 (recommended)" and that did not help.
The issue I encounter with the fail-over cluster only occurs when trying to install with DSC!
Using the SQL Server Install wizard, Command Prompt and even in Powershell by invoking the setup.exe all work perfectly.
So, to reiterate, this issue only occurs while running in the context of DSC.
I am using the same domain login with Domain Admin Security and locally the account has Administrators group credentials. The SQL Server Service account also has Administrators Group Credentials.

Labview dsc client server

Hi,
I use LV7 and labview dsc.
I would like to read historical traces from a client PC. my database is saved on a server PC. I'm using "Read Traces.vi". It works well but i have to wait 10 or 20 seconds to have results (for only 100 points).
I have no problem for reading tags in real time but it is very too slow for reading historical data.
I would like to know if there is a solution to minimise time for echanging historical data.
Thanks.
Alexis de la fontaine
SECMAI

Hi Alexis,
Are you observing the same delay with Read Traces.vi when you read traces locally? 100 points means 100 I/O points (tags) ?
Remzi A.
Applications Engineering
National Instruments

DSC Modbus Server

Hello there,
I have an upcoming project where I will use DSC and Modbus for the first time. My sensor network will be Modbus over RS485 but the piece of plant I need to talk to is Modbus over RS232.
When in a LabVIEW project I create a new Modbus I/O Server, I have the option to select Modbus Serial or Modbus Ethernet.
My question is - does Modbus Serial support RS232 and RS485?
Thank you,
Martin

Here are a few more links that you may find useful.
Connect LabVIEW to Any PLC With Modbus - http://www.ni.com/white-paper/13911/en
Using Touch Screens with LabVIEW through Modbus Serial Devices - http://www.ni.com/white-paper/4722/en#toc2
Best Regards
Paul
Applications Engineer
NIUK
I accept Kudos and BTC Tips :-D
Address: 1NyXnWf9kdjVzjWcW5w4P1V3b1EY4yXP12

OPC Alarm Event server connectivity?

Hi guys,
Can Lookout connect to OPC Alarm / Event servers? It is very important for me that I can do this.
OPC Data Access servers is no problem, but i don't want to redifine my 1000's of alarms that are already in the controller for the HMI in lookout.
Lookout is my favourite HMI application of all time, but if it can't access AE servers and DA servers at the same time then I'll have to use another software.
Many thanks,
Trev.

Hi Ryan,
Thanks for your response. Is there a political or technical reason for this?
I thought that OPC AE connectivity would be the most fundamental thing in a HMI/SCADA system.
I have no possibility to read the internal controller alarms, events and trips on the SCADA system without altering the controller code to write them out to another interface (eg. Modbus).
I see it as a total waste of resources to have one interface for AE and another for DA.
Do you think this will change in the future? Your competitors offer AE.
Thanks,
Trev.

Dsc opc shared variables yields Server Failure

I've been struggling with the transition from DSC 7.1 to 8+ ever since the release of version 8. I use the Allen Bradley OPC server supplied with the DSC module (Industrial Automation OPC Servers v 5.1) to communicate with a PLC 5/30 via Ethernet, or at least I did when I was using 7.1.
Prior to today I always failed to get the shared variables that were bound to addresses in the OPC server to deploy, usually getting an error number that started with -19. However today I finally got it to deploy by keeping the I/O server and the shared variables in separate libraries within my project. Now that they deploy I find that I am unable to monitor them. I keep getting a Server Failure. I have browsed the forums here heavily, and the documentation all relates to remote OPC, which is not what I'm doing here (OPC client and server are on the same machine). I tried changing the login account for the Variable Engine service anyway, but that doesn't help, so I put it back.
I have had some luck simply binding my front panel objects to the OPC server addresses using Datasockets, so it appears that my OPC server is working. However, Datasockets is not a viable option for me because there are times when my project needs to write to a large number of addresses in the PLC sequentially, which never works over datasockets (in my experience).
We have continued to work in version 7.1 because of the challenges of moving to 8+, but since we can no longer purchase DSC runtime licenses for version 7.1 in order to deploy, it seems that we MUST move forward to 8+ or abandon LabVIEW altogether (which is certainly an option).
For clarification, I am now working with version 8.2 (but I've been fighting with it since 8.0 without much success). If anybody out there can think of a critical step that I might have missed that might cause this, or if there is a known solution, I could really use (and would greatly appreciate) the help. Thanks!

Nobody out there seems to have any answers for this, so I kept pounding on it (and pulling my hair out). In the end I finally succeeded in getting one of my old 7.1 DSC projects to run on 8.2. Here's what I did:
1. I begin with a fresh installation of Windows. I tested it with both 2000 and XP Pro. Vista RC1 will absolutely NOT work!
2. Install LabVIEW 8.2, DSC 8.2, and just the OPC server that I need from the IA OPC CD (in my case the Allen Bradley server)
3. Open the IA OPC server editor, and create a new file with an object in it for my PLC (PLC 5/30, Ethernet in my case)
4. Save, set it as the startup file
5. Run LabVIEW, create an empty project
6. Add an IO server
7. Launch Multi Variable Editor, load project file created in step 6, and bind one variable to PLC address
8. Save all. Uncheck auto deploy for the library, and deploy all.
9. Launch variable monitor, browse to new variable, double click to monitor.
10. This will ALWAYS fail with "server failure". Don't worry, just exit completely out of LabVIEW.
11. Stop the Variable Engine service.
12. Run OPC server editor again, and load up the lpd file from your old project. Modify if needed, save, and set as startup
13. Start the Variable Engine service again.
14. Launch LabVIEW
15. Create a new empty project (I created mine in the same directory as my old 7.1 project resided)
16. Add an IO server, and uncheck auto deploy for its library
17. Save all
18. Run Tools->DSC->Migrate->import scf
19. Convert your old SCF file
20. Add the new library to your project (it will be named LabVIEW)
21. Uncheck auto deploy for the "LabVIEW" library you just added
22. Right click on the "LabVIEW" library and do deploy all
23. Save, and open the variable monitor
24. Browse to a tag in the LabVIEW library, and double click
25. This time it will actually monitor the variable, with a status of "Good"
26. Now you can add your main front panel VI to your project, open it and run it
27. Version 8.2 will select the proper legacy tag read/write VI's, whereas 8.0 does not. The writes however do not work. Replace them with shared variable writes. The reads work fine.
28. The empty project that you created in step 5 is a throw away. It will never work anyway.
29. So far the only variables that I can get to work at all are the ones that I import from an scf file, which is a pain, but if I must create all my tags in 7.1 and import them into 8.2 I will (for now). I may try exporting to Excel and copying variables that work in order to get functional new variables, since binding them in the editor does not work.
I hope this helps anybody else out there struggling with moving to 8+ DSC. I saw a few posts with similar issues, but without ANY answers at all. It's a convoluted solution that doesn't make a lot of sense, but for me it is repeatable.

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

Problem with opc server 2012

I use LabVIEW 2010. I installed OPC Server 2012. Configure DCOM. Create OPC tags in Server
Create project and create opc client
But i didn`t see tags in bound variables:
Can somebody help me, why i didn`t see tags?
Solved!
Go to Solution.

What's underneath the OPC2 folder?
Also, I checked my OPC 2012 Server readme (Start >> All Programs >> National Instruments >> OPC 2012 Server >> Readme) and it says:
"You can use NI OPC Servers with the following software applications:
LabVIEW 2011 SP1 Full or Professional Development System
LabVIEW DSC Module 2011 SP1"
This might mean it's not compatible with your version of LabVIEW.

Dsc - programmaticly create IO server?

Is it possible to programmaticly create IO-servers in my project (I use LabView 8.0)? I can programmaticly create libraries with folders and shared variables, but I havent found a way to programmaticly create a IO-server in my project (that for ex. points to a FieldPoint OPC server)... So I wonder if this is possible at all?
Thanks in advance!
-Cornelis

Corny wrote:
Is it possible to
programmaticly create IO-servers in my project (I use LabView 8.0)? I
can programmaticly create libraries with folders and shared variables,
but I havent found a way to programmaticly create a IO-server in my
project (that for ex. points to a FieldPoint OPC server)... So I wonder
if this is possible at all?
Thanks in advance!
-Cornelis
Mmmh, this is more or less a
two step process and you can't exactly do everything programmatically.
First you would need to get the DSC device registry updated for the IO
server in question. You would do this with the DSC Module VIs->DSC
Module Server Development->DSC Module Server Registration VIs. But I
have no idea if this would work with OPC too since I have only used NI
hardware or my own VI based IO servers with LabVIEW DSC until now.
These VIs are mainly meant to be used if you develop your own VI based
IO server and there is a chance that the internal database organziation
has been extended with additional attributes or tables for OPC servers,
but that those VIs do not give you access to those attributes and
tables. But I would try it out by first creating an OPC server
interactively, then using the "Get" VIs retrieve the information for
that server through those VIs to see what is what, and then try to
create my own server through the "Add" VIs of that library and see if
it works.
The next step would be to create the tags in the SCF file but as far as
I know there is no documented API access to the SCF file so this will
have to be done interactively through the Tag Configuration Editor
anyhow.
Rolf Kalbermatter
Message Edited by rolfk on 04-23-2006 04:06 PM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

OPC/DSC/Kepware Server

Similar Messages

Maybe you are looking for