DSC database

Hello,
I'm quite new to DSC and I'm facing a question I haven't found any answer to in documents or forums, I hope someone could give a clue. I'm developing a control application which runs embedded on a cFP-2120 using Labview 8.2.1 and I would like to have a user interface in a PC so that the user can connect to change some set-points and other options, so I have used the shared variable to communicate between PC and cFP. This shared variables are deployed in the FP so that way the user can turn off the PC (or unplug it from the network) and the control will go on working.
Now, I would like to log data from many channels and keep an alarm register of those channels and I been asked if I could use DSC module but looks like I can't use the capabilities of DSC module provides for database unless the library in which the shared variables are stored is deployed to a PC. If I rigth-click my .lvlib file (which is under the cFP) and choose properties I can't see neither "DSC settings: Database" nor "DSC settings: Data Access".
Could anyone tell me if there's any solution to this or suggest an alternative?
Thanks

That is true. If the shared variables are in a library in the cFP, they can't do the logging and alarm features. Shared variables stored on the PC can do all of the DSC functions.
You can create another library of the variables on the PC and turn on the desired features. Those variables could be bound to the cFP IO points, or to the shared variables that are stored on the cFP. Of course that means the PC has to be on and running, and the SV library on the PC deployed in order to be able to log those channels. But in the event someone turns off the PC or takes it off the network, the cFP will still run based on its SV library, you'll just lose the logging features.

Similar Messages

How to Setup Historical DSC Database on a standalone Server

Hey @all,
I am looking for documentation how to setup a standalone server for the DSC Module(Ver. 8) Historical Database.
My aim is to log all data to this server. The Server will be running Win2K.
Do I have to install the complete Labview 8 software and the DSC Module?
Does a walkthrough exist how to setup a DSC server?
Thx!
Carsten

After installing the runtime you should only have to reboot the computer in order to get the citadel service running. At the point, for citadel purposes, this machine will behave as though you had the DSC development system installed. The 8.0 runtime has no setup requirements...it should only need to be installed. Unlike previous versions, 8.0 requires you to build your application into an executable and the runtime should be invisible to you once you install it. If this is not the case, please post about it so it can be looked at.
If you have specific questions, please post them and I will either try and help you find the answers, get them posted, or answer them myself.
Regards,
Robert

How do I best upgrade a multiworkstation app using DSC from LV7.2 to 8.6?

I have an extended, properly functioning process control and data acquisition application running across multiple workstations (roughly 10). The workstations share information with each other and with process controllers via DSC and OPC.
We're currently running at version 7.1, and this spring we want to update to the current version of Labview (which, by then, will be 8.6.1; we are on the SSP).
I understand that the tag engine/database have changed significantly between 7.1 and the current version of the DSC, and wonder if there is a good roadmap for executing this upgrade to minimize downtime on our tool?
Kevin Roche
Advisory Engineer/Scientist
Spintronics and Magnetoelectronics group
IBM Research Almaden

Hi Ben -- we do not log history or events in the DSC, so that is not an issue.
The application is controlling a multi-chamber (7 connected vacuum chambers arranged in a star configuration) thin film deposition system. The basic control, interlocks, and safety/process security of the vacuum components is done via a series of Opto22 "brains", which are essentially simple processors running programs to control IO for valves and temperature control systems. They communicate with each other via Ethernet.
There is an OPC server for the Opto22 brains, which runs on one workstation dedicated to use as a gateway between LabVIEW and the network of brains. A DSC tag database is set up on that machine to access some of the IO states and variables in the brains, and then the other workstations have tag databases that reference those tags (the brains' communications interfaces can be overwhelmed if too many workstations access them simultaneously, so we use a single workstation as the gateway). Via the gateway, a workstation may read/manipulate some of the io states directly, and make other requests of the brains' software by setting flag variables in the strategies running therein.
Each chamber also has a complex motion control system for process manipulation, as well as extensive serial/parallel communications to control the gas systems, deposition power supplies, etc. The process software on each workstation makes available a "snapshot" of its process state available via memory tags in the DSC, so that the workstation controlling the central chamber can detect when a task in an outer chamber is completed and move samples between the different chambers.
All the workstations, brains, and motion control systems are interconnected via an Ethernet network independent of our building intranet. There is one additional workstation that maintains a process database, where each workstation can record each process task and the samples affected by it.
Everything is working at this point, but we recognize that we are overdue to bring the system up to the current level.
In particular, guidance as to a possible way to upgrade the gateway tag DSC database and then the others referencing it in advance of recompiling all the software, if that is possible.
Kevin Roche
Advisory Engineer/Scientist
Spintronics and Magnetoelectronics group
IBM Research Almaden

Archive citadel database in MAX hangs

I am trying to Archive a 4.13 GB uncompressed DSC database on LabVIEW 2013 SP1 (although the database was started with LabVIEW 2013). I have tried twice and it gets stuck (new location folder size is at 151 MB both times). The progress bar says "Archiving database=20.5%" and "Copying Data=83.0%". I have chosen the option "Destroy source data after it has been archived (local computer only)". The status says "copying data" and I no timestamps of files in the new folder have changed after about 9 hours of waiting. If I cancel, MAX cannot display any Citadel databases. This is fixed if i reboot.
Any ideas?

Hello barkeram,
Where are you storing the archive (locally or remote)?
Are you following the steps in one of the following documents?
http://digital.ni.com/public.nsf/allkb/E076A0661E03F1EB862571A800079E7B
http://digital.ni.com/public.nsf/allkb/2B0C74744BB37391862571F500067C64
Can you try to navigate to the file path of the database and duplicate the file? Afterward, manually add the new database to MAX and try to Archive the new file.
Regards,
Thomas C.
Applications Engineer
National Instruments

When writing DSC-tags, MSDE causes 100% CPU load

I have a number of shared variables configured to be logged in the DSC database. When I'm writing to these repeatedly the SQL-server (MSDE) loads the CPU with 100%. Why is that? Even when I've stopped, it “hangs” at 100% for quite some time. Eventually this stalls all other applications and the whole machine. What is DSC doing in the SQL-server? Is there a way to configure the behaviour?

Why are you concatenating an empty string to all of your strings?
You don't need to have multiple index arrays. Use one index array and resize the bottom of it downward. You won't need to wire up any indices either. By default, the top one will be index zero, and each one below that will be +1 the one above.
How does it behave when you run it with highlight execution? Does that give you an idea where it is hanging?
Also, your connection string as several backward apostrophe accent characters rather than regular apostrophes. See here.

Write traces to spreadsheet file mis-wiring

I want to extract the data from the DSC database based on a user- or program- defined time range and write that data to a text file. I have the first stages of that set up here, but there is a broken wire (cluster type) that I don't understand what about it is broken.
According to the help dialog for "Write Traces to Spreadsheet File", the trace information cluster shown in the vi should be correct. But it is not and is marked as a false connection. What is wrong???
Attachments:
extract_data_from_database_-_sent_to_NI.vi ‏52 KB

Change the order of the objects inside your cluster. Disconnect the cluster wire from the write traces to spreadsheet file vi. Right click on the terminal and select create constant. Turn on the context help window and move the cursor to both wires and note the order of the items in the datatype of the wire.

Older versions of toolkits

Hello,
is there a site from which I can download older versions of toolkits. At my workplace, I am eligible to use some of the tool kits (DSC, Database connectivity toolkit, etc). Since we are using older version (2009) of LabVIEW, I cannot use the toolkit versions available on the NI evaluation site. I could not find the older version also in ftp site. Could you tell me where I can download the older versions of the tool kits.
Many thanks in advance,
Zacharia

Hi Zacharia,
Thanks for your post.
Unfortunately only the latest versions of the toolkits are available to download via the NI website. However I would encourage you to get in touch with your local NI office for further assistance as they may be able to provide you with a copy.
Hope that helps!
Tori
Student

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

How do you change values after logging data to the citadel database (DSC)?

How would one go about changing values that already exist in the citadel database. So say I were logging a numeric value with a timestamp for 1 year and then wanted to change a few values for the month of June because my sensor wasn't working at that time. How could I do this? Is it possible without re-creating the whole database over?
Thanks
Matt

mattyk wrote:
Hey Ben,
Thanks for the quick response. I called NI and asked about this because this would be a big show stopper for me. Their applications engineer said that the best way to change previous data would be to read in the trace that you want to change, modify it and save it as a new trace. I am also looking into SQL querying. I was able to connect to the citadel database by setting up a ODBC data source and using the database connectivity toolkit to query the database. This worked. Now I am trying to come up with a statement in SQL to change previously saved data. I'll Keep you posted.
Thanks
Matt
That reinforces my suspicions.
I have an app running for about 8 years now that keeps a paper trail to enusr ethe cartdiges used in respirators (operated NIOSH National Institute of Occupational Safety and Health par teh CDC) that use DSC to enusre nobody can ever falsify those records. If they can be hacked I my customer and anyone using a respirator with a NIOSH sticker on the side of it, want to know.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Trouble with database path (DSC)

Hello,
I use DSC and LabVIEW 2009 in my application, and I created programmatically Shared variables, which have to be logged in Citadel database. For that, I create a database with Create Database VI with a specified path , and afterwards I use Configure Process Log State VI to bind values from my shared variables to the database.
The problem I have is the following: the database is created as expected in the correct path ( I have a folder created, with some .cdih , .cdin file), but after, on MAX, when I want to see trendings, i notice my database appears under Citadel 5, but nothing is inside. Actually, all my shared var are log in Default_database, the default database of DSC...Moreover, I have this event in Event Viewer (see attached image), which says
I don't understand why i have such error...The problem is the final purpose is to create a standalone app with installer, and clients want to choose where they store their data...
thanks for your help
Antoine

Hi Antoine,
could you please post you code and your LabVIEW Version?
Kind regards
Carsten

DSC 7.1 - Compact Database is SLOW

Another time DSC shows how slow it really is.
I need to compact my database since it is holding 5 months of data (configured to hold 90 days)
So I load MAX and ask it to compact the database. ERROR "unspecified error"
ok shut down the tag engine - I can live with no fresh data being logged for an hour.
Start the compact - oooh 50% almost immediatly
OK lots of activity on my SCSI RAID 0 (two Seagate 76gig 15krpm drives on adaptec dual channel raid board)
the computer is working pretty good (1% in 15 minutes) CPU usage (Dual 3.0ghz Xeon) is only 7%
file manager shows there are files being added (70+)
hmmm finally done after 1 hour 17 minutes
file manager still shows 5 months of data (was 15gig now 14.7gig)
use MAX to see how much data is there
-LOTS of SCSI activity
-ta da MAX shows all the data is still there
-MAX shows the "lifespan" of the data equals 90 days
This may seem to be another DSC "rant" and it probably is. I just want the software to do what it is advertised to do. If Compact does not work "don't include a menu for it" - If Archive takes 18 hours to extract some data "fix it" - If the database is corrupt "TELL US! don't make us look at CPU Usage to find out when it finishes"
OK I am done with the rant.
How do I remove the expired data?

Hello,
To remove expired data, you can do destructive archiving. Unfortunately it is slow and we are addressing this issue. I am sure you know how to do destructive archiving but to the benefit of others who might come across this discussion, here it is.
1. In MAX, under Historical Database, select Citadel 5 Universe. This brings up all the databases on the right handside.
2. Right click on the database you want to archive and select Archive.
3. In the wizard, select the data you want to archive and hit next.
4. Select the destination datbase you want the data to be archived and hit next
5. In this final step, please make sure that you have selected the option of destroying the data after it has been archived.
Regards,
Arun V
National Instruments

How to archive citadel database. we have DSC 6.0.2

we have LabView 6i & DSC 6.0.2 . we develop a application using tags. we want to log our data to citadel database but some time the data is lost for some reason (like system hank or restart).so we want to take a backup of our citadel database.how it will possible.

Pilla,
Unfortunately, 6.0.2 does not have the capability. This was one of the new 6.1 features. Check Table 3 on page 7 in this manual. The Archive Database is what you need for programmatic archive. In 6.1 there is also a new utility called Historical Data Viewer, that allows you to do it manually.
http://www.ni.com/pdf/manuals/322955b.pdf
I remember seeing some online document about archiving Citadel database. ... oh, ya, here it is (I searched ni.com for "archiving citadel" and it was the first hit):
http://zone.ni.com/devzone/conceptd.nsf/webmain/2F24997EAD7C53A686256B6E00686D64?opendocument
Have a good weekend.
Dr.Tag

DSC 8.6.1 doesn't log alarms

My alarms are not being logged in DSC 8.6.1.
I can tell that the alarms are being properly generated when I monitor them in the Distributed System Manger. In keeping with previous posts, I know that the MSSQL server is running in the taskbar. I've also tried changing the permissions for NETWORK SERVICE in the citadel directory.
When I try to monitor alarms in LV, it returns error code 1967386611: HIST_RunAlarmQueryCORE.vi, Citadel: (Hex 0x8ABC100D) The given Citadel database is not currently configured to log alarms to a relational database.
I also notice that the time stamp on all of the citadel files is not being updated with each alarm, so it really seems like the alarms not being logged.
I have alarm logging enabled in all the appropriate places (at the variable, and in the library properties).
When I check the alarm log history in MAX, there is nothing there.
Thanks,
Charlie

Hello David,
I have the same Problem with LabVIEW and DSC8.5.1 and, yes, SQL-Server 2000 was installed before I tried to install DSC the first time.
But after I uninstalled the DSC, SQL-Server-Express 2005 and the old 2000-Version and reinstalled the complete DSC-Module it still didn't work. MAX doesn't display any error message but doesn't also show any data. ldf- and mdf-Files are not contained in the database folder.
Right after installation and first reboot I get an Error-Message: IN MSDE Security Setup Error „NI MSDE is not accessable or currently logged
user doesn't have sysadmin permissions“. I found a post for this issue, but the suggested solutions didn't work for me too ( http://forums.ni.com/ni/board/message?board.id=170&message.id=243298). And if I try to use the DSC's alarm-loging feature I end up with the Error:"...database is not currently configured to log alarms...".
The DSC and the application we developed work fine on two other
XP-Pro-PC's and I was surprised to get in trouble with installing it on
the customers PC.
The Windows XP Pro has been installed by our customer and I don't want to touch that installation. My user account has admin permissions. I have no clue how to fix this and I hope you have an idea what to try next.
Thanks in advance,
Thomas

Is there a way to force the Tag Engine to dump its input buffer to the database?

I have an application where I start a process and log the data, and then call a subVI that uses the Read Historical Trend VIs to get all of the data from when the process started until now. The problem is that the Historical Trend VIs only read from the database on disk, and the Tag Engine's buffer doesn't write to disk until it's full (or possibly times out; I'm not sure about that, though). Is there a way to force the Tag Engine to write to disk, so that the Historical Trend VIs will return the most recent data?
Shrinking the buffer will help a little, but that will only result in missing less of the most recent data. One possible hack is to have a dummy tag that I simply write enou
gh data to that will cause the buffer to be written to the database. I was hoping for something more elegant, though.

That's a good question.
The control about the datalogging and the DSC Engine is all done (more or less) automatically - you feel the NI ease-of-use idea
That means the Citadel service (one of the NI Services installed by LabVIEW DSC) is responsible of taking care about the datahandling (writing to and reading from the database files including caching some data e.g. index files, frequently used data...).
The DSC Engine makes a request to the Citadel service that this data has to be logged. Everything else is handled by the Citadel service. Internally, there are two kinds of logging periods handled through the Citadel service. One for traces being viewed (a small period: 200ms) and one for traces not being viewed (slow (big) log period: 20000ms). That
means, if Citadel gets a request to store a value it will buffer it and store it as soon as possible depending on other circumstances. One depends on the fact if this trace data is being viewed (e.g. with Read Histroical Trend.vi) If you request/read to view a trace you should pretty much see the current values because citadel should use the fast log period.
The Citadel service takes care as well about setting priorities e.g. the writes before the reads (We don't want to loose data - right?). That means if you really stuff the system by writing a lot of data the CPU might get overloaded and the reads will happen less often.
If you really want to see "real-time" data I would recommend to use the "Trend Tags.vi". With this approach you avoid the chain DSCEngine-Output Buffer-CitadelService-InputBuffer-File-HD... and back.
I hope this info helps.
Roland
PS: I've attached a simple VI that has a tip (workaround) in it which might do what you are looking for... However, Nationa
l Instruments cannot support this offically because the VI being used are internally DSC VIs that certainly change in the next version of LV DSC... and therefore you would need to "re-factor" your application.
Attachments:
BenchReadHistTrend.llb ‏104 KB

How can I prevent NULLs from appearing in my HyperTrend graph when restarting DSC engine?

I am continuously logging data to a citadel database using DSC 7.0. Occasionally I need to restart the DSC engine because of a computer reboot, changes to SCF file, etc. Whenever I do this, and then review the data in HDV or with a HyperTrend graph in LV, there is a discontinuity in the traces during the time the DSC engine was not running. Using the cursors, you can see the value during this time is NULL. Generally this is desirable behavior since it indicates that no data was collected during this time period. However, I would like to know if there's setting to just "connect the points" instead of having a NULL in between. The reason is that some memory tags are updated very
infrequently, so the discontinuity appears much longer than just the time the DSC engine was not running. I want to connect the line to make the graph look nicer.

I assume that you mean pop-up windows that might be left unnoticed when they are opened behind the current Firefox window.
You can modify the behavior and change these prefs to open all links in tabs:
*http://kb.mozillazine.org/browser.link.open_newwindow<br />1: current tab; 2:new window; 3:new tab;
You can change the value of the browser.link.open_newwindow.restriction pref to 0 to open all JavaScript window.open() calls in a tab
*http://kb.mozillazine.org/browser.link.open_newwindow.restriction
You can open the <b>about:config</b> page via the location bar and accept the warning and click "I'll be careful" to continue.
*http://kb.mozillazine.org/about:config

DSC database

Similar Messages

Maybe you are looking for