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

Similar Messages

LabVIEW DSC Client\Server application. How to install executable on client.

Hello all,
I'm currently programming a Client\Server application. The server application should host shared variables and the client application should read them. The client application reads the shared variable in the indicator by binding them with the indicator properties. I started the programming, and the client and server application are in the same project. In the client application I'm binding the indicator to the library in my project which has the "My Computer" as the address. My question is how I will tell the executable installed on any computer I desired to used the shared variables on the server? I have LabVIEW DSC 2009.
Thanks,
Solved!
Go to Solution.

Hi, since we are talking about executables...all targets require both LabVIEW (which includes the shared variable engine)and DSC (a bit more complicated, here is an insight) Run-Time engines, otherwise the stand alone application won't run. Now, assuming that everything is on the same network and all executables are suppose to clients, or at least access the already created variables hosted on your PC, I believe it would be easier to find programmatically the available resources than create/deploy new libraries. If you find your self in troubles here is a guide to troubleshoot applications that uses shared variables.
Alejandro | Academic Program Engineer | National Instruments

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.

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

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.

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.

Client-Server with LabVIEW

I have the following Situation , I want to Setup the Labview College License at a Server and make some Clients (the Students) fully accessing the labview on this server Simultaneously, How can i do this?

Hello Ahmed,
There are two ways to increase the number of licenses available in VLM.
1.) Obtain a new license file from National Instruments. In addition to the information specified in the linked KB, also include the changes you want to make to you license (add X number of seats). Then you install this new license file and you will be able to check out more licenses.
2) Enable Overdraft in Volume License Manager. Go to Options»Preferences»Policies, and enable the overdraft policy for VLM. This will allow you to check out more licenses than you have, but you will have to pay for all of the extra usage when you send in your activity log at the end of the yearly contract period.
Also in relation to the previous question you asked about the installation of LabVIEW. I would recommend looking at this article on Volume License Installers, which gives you a nice way to install software from a central location (network) and ensure that the clients who install it will automatically begin checking out their licenses from the VLM server.
John B.
Applications Engineer
National Instruments

Does LabVIEW DSC 8.5 support Windows Server 2008?

Hi,
I am developing a SCADA system using LabVIEW DSC 8.5. Apparently, customer wants the Server Computer to be latest Windows Server 2008 operating System.
But the Release and Upgrade note specify that DSC Module does not support Windows NT/Me/98/95/Server 2003. (System Requirement section)
Does it support Windows server 2008?
Any feedback most appreciated.
Message Edited by Vsh on 09-28-2009 08:56 AM

Hi Vsh
Sadly no version of LabVIEW (and therefor no modules like DSC either) officially supports Server 2008. That has however not stopped people from trying and I've seen both cases were it has worked fine and cases were it has not worked. This thread might be of interest to you.
Best Regards
David
NISW

Has somebody already used Applicom PCI2000ETH Card or Applicom SW1000ETH software to communicate with ETHERNET bewteen siemens s7-300 and LabVIEW DSC ?

I want to use ETHERNET and not PROFIBUS to communicate and I think you can do that with only the applicom software SW-1000ETH. You must just have an ethernet card on your PC. So, you could use a notebook with an
ethernet card. You can also use Applicom PCI2000ETH for better performance.

Hi,
You might be able to get the configuration listed above working as long as you can get from Siemens/Applicom or any other third party provider a OPC Server that communicates with the S7-300. Since LabVIEW DSC is a OPC client, you would be able to establish connection.
The National Instruments driver for the S7-300 (Containnned in the product called "IA OPC Server CD") does not support communication through ethernet directly, you would either have to have a Profibus board or use a serial port with a Siemens HMI Adapter.
I hope it helps
Best Regards
Andre Oliveira

Crash with labview DSC

LabVIEW 7.1
LabVIEW DSC 7.1
Citadel 5
Hi,
I've developed an application with Labview 7.1... I'm using a customer/server structure.
I'm using a fieldPoint to acquire analog values trough labview DSC.
When only the server runs, i've no problem. I can read and display all the tags i want in historical graphs.
On the Computer "customer", I imported network tags through the "Tag Configuration Editor".
Sometimes, when i want to read historical datas, Windows (XPSP2) kills my application on the customer. (I'm using the VI "read traces" ).
I saw errors in the "windows events viewer" : wrong execution of nicitmid.dll
I don't know how to solve this problem. Any help ?
(sorry for my poor english )
regards,
Alexis de La Fontaine

Bonjour,
Je constate que vous êtes de NI france donc je me permet de m'exprimer dans ma langue...
Oui, cette dll est installée avec Labview DSC.
Ce que j'ai pu constater :
J'ai un PC serveur qui tourne et qui centralise toutes les données reçues d'un fieldpoint. Ces données sont stockées dans la base de données gérée par citadel. Lorsque je demande des courbes d'historique de mes voies de mesures depuis le PC serveur, je n'ai aucun problème (j'utilise les Vis NI pour obtenir ces historiques).
Par contre j'ai un deuxième logiciel utilisé en tant que client sur des postes distants. Lorsque je fais des demandes d'historiques de données.... le client va chercher ces données sur le poste serveur... Dans la très grande majorité des cas, celà fonctionne très bien ! par contre, dans certains cas (aléatoires à mon sens), l'application cliente OU maitre plante avec une erreur windows. C'est alors que la dll nicitmid.dll est mise en cause par windows.
D'après moi, cette erreur est peut-être dûe au fait de demander simultanement des courbes d'historique à la fois depuis un poste client et depuis le poste maitre....
Avez-vous des idées, des suggestions ?
Cordialement,
Alexis de La Fontaine
ASSYSTEM FRANCE.

LabView DSC, RSLinx, SLC505 and Data transfer (Best way for large blocks of data?)

I am currently programming in Labview 6.1 with the Datalogging and
Supervisory Control module to transfer 720 floating point numbers to a
SLC505 Allen Bradley PLC (with ethernet) using RSLinx as an OPC server. I
have found that using the Datasocket Write takes about 30 - 40 seconds, and
making the tags and writing to them takes about the same amount of time. Is
it possible to transfer this data faster?
Thanks,
Michael Thomson (Surcher)

Cyril,
I was just experimenting with different ways to transfer the data from the
computer to the PLC. In the past I have built large tag databases with
specific tag names. This made the code rather cumbersome when you wanted to
write to a large group of tags with descriptive names. I was just using
datasocket write as a way to transfer the data to the plc using code to
build the url and without having the DSC engine running. I have found that
importing the tags right from the tag configuration editor with the names
being simply the PLC addresses and then accessing them with the tag write is
considerably faster (under 5 seconds). I can then build the names in an
embedded for/next loop and change them to a tag name before I write to each
one. The appli
cation is a user interface that allows the machine operator
to pick what kind of arch to put on cabinet door part. With the selections
chosen I calculate the servo moves and download the data to the PLC.
Thanks for the link!
Michael Thomson
"Cyril" wrote in message
news:[email protected]..
> Michael,
>
> I am a little bit confused about the configuration here and the
> programming here: why are you using Datasocket Write if you are using
> tags? Are the 720 floating numbers written to 720 different I/O
> Points(registers). If so this shouldn't be that slow especially with
> DSC
> I would strongly encourage you contact the support at National
> Instruments for LabVIEW DSC, either by phone or e-mail and give a
> detailed description of the issue:
> www.ni.com/ask, and communication method phone NI or e-mail NI.

Problem using the File Dialog Box in a Client/Server application

I am developping a client-server application using Labview 5.1 . The application on the server acquires data from some instruments and saves it on file, while the application on the clients displayes such acquired data. For doing this I call some routines on the server via the "Open Application vi" (remote connection). All goes well except when I open on the server the "File Dialog Box vi" : in this case the application on the clients is blocked (is blocked the execution of the called vi on the server). Only when
the File Dialog Box on the server is closed, the execution of the called vi on the server starts again.
I need to use the File Dialog Box on the server, but I don' t want to stop at the same time
the clients !!
I need help for resolving such problem.
Many thanks in advance !!!

Hi!
waldemar.hersacher wrote:
"It seems that the VIs called by the clients are running in the user interface thread.
A call to the file dialog box will call a modal system dialog. So LV can't go on executing VIs in the user interface thread."
Are you sure? I think, that File Dialog, called by LabVIEW File Dialog from Advanced File Functions Palette doesn't blocking any cycles in subVI, which running in UI Thread. Look in my old example (that was prepared for other topic, but may be good for this topic too).
2 linus:
I think, you must a little bit reorganize you application for to do this. You must put your File Dialog into separated cycle. This cycle, of course, will be blocked when File Dialog appear on the screen. But other cy
cle, which responsible for visualization will run continuosly at the same time...
Attachments:
no_block_with_file_open_dialog.zip ‏42 KB

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

Establish a connection through RF modem's on client & server side & to set up PPP communication for data transfer

hi
can any1 over here help me out in how to establish connection between 2 RF modem's for data transfer , between client & server USing LABVIEW?
I want to establish a connection between 2 PC's through RF modem on client & server side & to set up PPP communication for data transfer.
(I have tried data transfer through RS-232 using TCP/IP whn the 2 PC's are connected over ethernet... which is working.
I also tried connecting loopback cable between 2 PC's COM port & geting data transfer using VIsa configure serial port & other visa functions ... which is working)
can u guide me how to establish connection between 2 RF modem's using LABview?
& how does the data transfer take place between 2 RF modems through RS-232?
is it using TCP/IP?
If you got any links to go abt this issue do send me related links .. or any examples .....
I am currently using Labview version 8.
Waiting in anticipation.. reply ASAP..
thanking you
Regards
Yogan..

Howdy yogan,
Maybe you could clarify a few things for me, and we'll see how we can help ya. TCP/IP protocol occurs through an ethernet connection; RS-232 communication occurs through an RS-232 serial connection, typically through a cable that has a DB9 connector on both ends. Do you mean that the RF modems in question have the option to communicate via RS-232 and/or via TCP/IP ethernet? Specific information like the manufacturer of your RF modems, the model number of your RF modems, and how you connect the modems to the PC would enable us to give you more efficient support.
You can check our Instrument Driver Network (IDNet) to see if a plug-and-play/IVI driver already exists for your RF modem. (You'll need to know its manufacturer and model number.) In the case that you do find an IDNet driver for your modem, you can use this KnowledgeBase article for instructions on how to use the driver.
Another excellent resource to consider is the NI Example Finder. You can access this within LabVIEW by navigating to Help»Find Examples and then searching for serial or TCP/IP examples.
Message Edited by pBerg on 03-10-2008 04:35 PM
Warm regards,
pBerg

Labview dsc client server

Similar Messages

Maybe you are looking for