"History of Labview DSC"

Where I can find out more information on the history of Labview DSC? I would like to know when the module was developed and the reasons for its development.

It came from BridgeVIEW.
LV started growing out and greatly over-lapped BV functions. The dev of the two was stream'lined and DSC was introduce soon after LV 6.0.
Just to get started,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Similar Messages

LabVIEW DSC: Migration from 6.1 to 8.6 problems

Colleagues,
I need help from someone who experienced with LabVIEW DSC. I would like to recompile pretty old application written in LabVIEW 6.1/DSC 6.1 to LabVIEW 8.6, and got lot of troubles with this.
At the first I have tried to migrate my old scf file as described here: "Migrating from LabVIEW DSC 7.1 to 8.0".
Well, it seems to be OK, and LabVIEW.lvlib library with variables was created, but when I tried to double click on the some items, then exception occurred in LabVIEW (see dsc_exception.png in attachment).
Can you please open test project (attached to this post) and double-click on the Slave005_A0 Item? Is crash happened only by me or by someone else?
The second problem with understanding.
In LabVIEW DSC 6.1 I have used "Read Tag.vi" / "Write Tag.vi" vis for accessing the items. When my VI opened in LabVIEW/DSC 8.6, then these calls replaced with "legacy_Write_Tag_(analog)7x.vi" (see screenshot). I'm unable to found according VIs in DSC 8.6. How can I write/read my tags in the latest version? As far as I can understand, I can use Shared Variables directly. Is this correct? But then how can I read multiple tags? Through DataSocket VIs?
The same with "legacy_Get_Tag_List7x.vi". How can I get items list in DSC 8.6 programmatically?
Or should I leave all legacy* vis in my application?
thanks in advance and best regards,
Andrey.
Attachments:
dsc_exception.png ‏26 KB
dsc_legacy_Write_Tag.png ‏3 KB
TestProject.zip ‏4 KB

Hi Andrey,
Yes, my LabVIEW crashes as well. As you may have noticed, a lot has changed in LabVIEW 8.0 with regards to DSC, the most important being that tags are replaced with Shared Variables. I would recommend that you go through each variable and create them by yourself to ensure the most reliable performance.
If you are interested in reading 'tags', then you just need to drag the Shared Variable and place it on the block diagram (that's the direct way). If you are interested in doing this programatically, then have a look at the DSC Module -> Engine Control -> Variables & I/O Servers -> Get Shared Variable List palette on the block diagram. You can then use DataSocket to access the Shared Variables.
Don't leave the legacy VIs on your block diagram. Upgrade your whole project; shared variables are here to stay. Have a look at the following article to get a thorough understanding of them:
Using the LabVIEW Shared Variable
Let us know if you have more questions.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

What are the steps necessary to create an EXE using LabVIEW DSC ?

I´m developing an application in LabVIEW 7.0 using the LabVIEW DSC 7.0 Toolkit. I´d like to know the steps I should take to cretae an EXE for this application.

There is information regarding building a LVDSC .exe at
http://zone.ni.com/devzone/conceptd.nsf/webmain/2f7cf918f3b412db86256a1c006af25f?OpenDocument
It's from the time of LV6, but contains some useful info.
=====================================================
Fading out. " ... J. Arthur Rank on gong."

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.

Installing LabVIEW DSC 8.6 Run Time on Windows XP Embedded flash memory

I'm trying to install LabVIEW DSC 8.6 Run Time on an embedded PC running Windows XP Embedded. This has a small local disk (c), so I would like to install DSC Run Time on a secondary flash memory drive (d). The installer tells me that I don't have enough free space on drive c, but I cannot browse to select drive d. What do I need to do to get this installed?
Thanks,
Josh

The DSC module can't easily be installed to external flash memory. You'll want to move any extra data onto the flash drive to free up space on the internal memory for installing the DSC module.
Mark E.
National Instruments
Schedule a Free 1-Hour online LabVIEW Tutorial with an NI Applications Engineer

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

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.

What is the best way to put LabVIEW DSC data into an Oracle database?

I have been collecting data using LabVIEW DSC 7.0 for several years and have always accessed the data from the Citadel database via the Historical Data Viewer. I would now like to begin putting this data into an Oracle database. My company stores all their data in Oracle and it would provide me all the benefits of their existing infrastructure such as automated backups, data mining tools, etc.
My initial thought is to use "Read Trace.vi" in LabVIEW to pull historical data from the citadel database at regular intervals (e.g. 1 minute) and insert this data into Oracle via ODBC. In this way, I do not need to track the value changes in order to know when to write to Oracle. I also considered replicating the citadel database using some other method, but I recall that the tables used by citadel are somewhat complicated. I only need a simple table with columns for channel, timestamp, and data. The "Read Trace.vi" will provide me data in this format.
I do not need to update the Oracle database in real time, a few minute delay is acceptable. If anyone has a better idea or additional insight please let me know. Thanks.

In terms of connectivity, you want to use ADO, not ODBC. Beyond that, it all depends on the structure of the data and what you are going to want to do with it. This is a very big question that you need to be getting some in-depth assistance.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Where can I get the password for unzipping LabVIEW DSC RTS 6.0 ?

no additional text

The installation files are password protected.
ONLY LabVIEW DSC RTS 6.0 CUSTOMERS ARE ELIGIBLE FOR A FREE DOWNLOAD
(contact National Instruments Technical Support to obtain the password).
Note: this is a complete installer. Unlike DSC 6.0.2 development system
that requires LabVIEW 6.0.2 and DSC 6.0 prior updating to 6.0.2, this
installation does not have such requirements.

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.

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

Can LabVIEW DSC Run on XP Embedded

cross posted to LAVA
Hi
Does anyone knows if LabVIEW DSC works on XP embedded?
These two posts are interesting: WinCE post cRIO post
Regards
JG
Message Edited by jg code on 03-04-2009 07:16 PM
Certified LabVIEW Architect * LabVIEW Champion
Solved!
Go to Solution.

Hello jg-code,
XP Embedded is not a supported Operating System for running LabVIEW developement environment or the DSC Module. This does not mean that it will not work, only that we do not guarantee that it will work. One reason for this is that XP Embedded can be made into any variety of installations. The following link may provide some useful information.
Running LabVIEW on Windows XP Embedded
http://zone.ni.com/devzone/cda/tut/p/id/4011
Regards,
Charlie Piazza
Staff Product Support Engineer, RF
National Instruments

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.

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

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

"History of Labview DSC"

Similar Messages

Maybe you are looking for