Exporting Shared Variables to csv

When I try and export SV information to csv, LV (2009, DSC) doesn't seem to recognize any variables that are located within virtual folders in the library. Does anyone know a work-around to get that data tabulated short of cycling through the whole library writing values from SharedVariableIO property nodes to file?
Thanks,
Kyle
CLD using LV, DSC 8.5-2009, RT 8.5
Ghoti!

muks wrote:
Have you seen this?
Yep. That's the problem. The shared variable library I'm working with contains well over 1000 variables that are organized into a few dozen virtual folders within the library. When I use the Export Variables function you linked to, it doesn't "see" any variables in folders, only those in the library root.
CLD using LV, DSC 8.5-2009, RT 8.5
Ghoti!

Similar Messages

Vestigial fields when exporting shared variables

Hello,
Is this a bug? I have a network-published shared variable that used to have aliasing enabled. After I cleared the "Bind to:" field and disabled aliasing, I exported its library into CSV mode. However, it still contained the columns (among others):
NetworkrojectBinding = TRUE
NetworkrojectPath = <old variable that it was bound to>
The extra columns messed up my CSV parser. The only way I could find to prevent their appearance was to delete all the variables that used to have project binding, and re-create them

JKSH,
I was able to reproduce the same issue here. I'll look into this a little more and see if this may in fact be a bug.
James K.
National Instruments
Applications Engineer

CR XI R3: Issue exporting shared variable to Excel - with workaround

Hi,
I have a report that uses a subreport to calculate a field based on the existance (or not) of data in a database other than the main report database. When I use a shared variable to pass this field back to the main report and display it on a detail line (in the main report), it works fine - until I try to export the report to Excel. When exported, the value that gets exported on all detail lines of the report is the final non-blank value of the shared variable, not the value that it contained when the detail line was initially generated. I am using a shared variable because there are multiple values that I want to pass back to the main report.
Luckily, only one of the shared variables are being printed, so the workaround that I am using is to use the subreport to print the field instead of passing the value back in a shared variable and displaying that (and hiding the subreport on a separate format).
Is this a known issue with R3 exporting to Excel? (It was happening in R2 as well...)
HTH,
Carl

Simplified somewhat, what this report is doing is looking up open orders in one database and checking to see if something specific happened to it in another database. If so, it generates the XML that needs to be applied to the first database to update it. The XML references the order number and line number. What I mean is that instead of the data coming out as
Order Line XML Snippet
12345 1234 ...<order>12345</order><line>1234</line><status>received</status>...
22345 2234 ...<order>22345</order><line>2234</line><status>received</status>...
32345 3234 ...<order>32345</order><line>3234</line><status>received</status>...
42345 4234 ...<order>42345</order><line>4234</line><status>received</status>...
I get
Order Line XML Snippet
12345 1234 ...<order>42345</order><line>4234</line><status>received</status>...
22345 2234 ...<order>42345</order><line>4234</line><status>received</status>...
32345 3234 ...<order>42345</order><line>4234</line><status>received</status>...
42345 4234 ...<order>42345</order><line>4234</line><status>received</status>...
I have Base Column Widths on Details, so there should be no merging attempted, but I'll check and make sure.
It seems to me, though, that the DLL is being told the wrong value to export...
Carl

Bug? Cannot export shared variable, if it's in a virtual folder within an .lvlib

Hello,
I was trying to keep my libary of shared variables organized by categorizing the variables into different virtual folders. However, it turns out that variables in virtual folders are excluded from exports, even though they (and their folders) are visible in the Multiple Variable Editor.
Is this by design (in LabVIEW 2012)? If so, what's the rationale?
Thanks!

Hi,
When there are variables inside nested virtual folders within a Library, the multiple variable editor does not work. If you select several variables in a virtual folder and right-click and select Multiple variable editor, the editor opens but you cannot change anything.
Workaround: Convert folders to libraries or move variables under a single folder.
Regards,

Export multiple variables to csv

I am a bit lost in adding my results to a csv.
I tried several way, but the objects are not written to csv.
# Var
$wdb = Read-Host "Enter Mailbox Database"
add-pssnapin microsoft.exchange.management.powershell.e2010
Import-Module ActiveDirectory
$ADSettings = Get-adserversettings
If ($AdSettings.ViewEntireForest -ne $true) {
Set-AdServerSettings -ViewEntireForest $true
function Get-ADUserLastLogon([string]$userName)
$dcs = Get-ADDomainController -Filter {Name -like "*"}
$time = 0
foreach($dc in $dcs)
$hostname = $dc.HostName
$user = Get-ADUser $userName | Get-ADObject -Properties lastLogon
if($user.LastLogon -gt $time)
$time = $user.LastLogon
$dt = [DateTime]::FromFileTime($time)
$AdvStats = Get-mailbox $U.SamAccountName | Get-MailboxStatistics
Write-Host "$($username) last logged on at: $($dt), the Mailbox was last accessed on $($AdvStats.LastLogOffTime) by $($AdvStats.LastLoggedOnUserAccount).
The mailboxsize is $($Advstats.TotalItemSize) and contains $($AdvStats.ItemCount)."
$Item = {
$Item.UserName = $userName
$Item.LastLogonAD = $dt
$Item.LastMailboxLogoff = $AdvStats.LastLogOffTime
$Item.LastLoggedOnMailbox = $AdvStats.LastLoggedOnUserAccount
$Item.MailboxTotalItemsize = $Advstats.TotalItemSize
$Item.MailboxItemCount = $AdvStats.ItemCount
$Collection = $Item.toString()
$DisAcc = Get-Mailbox -database $wdb -resultsize Unlimited | ? {$_.Identity -like "*/Disabled_Accounts/*"}
Foreach ($U in $DisAcc) {Get-AdUserLastLogon $U.SamAccountName}
$Collection | Export-Csv -Path C:\Temp\DisabledAcc_$($wdb).csv
# End
I also tried with select-Object ... | Export-csv -Path ... -append
Answers provided are coming from personal experience, and come with no warranty of success. I as everybody else do make mistakes.

Thanks for your reply, it is greatly appriciated. I am not a native scripter, but am working on automating more via powershell and get some more decent experience on the subject.
The idea of the script is to get the last logon to AD for users in a Exchange database, in addition it shows the last logon to the mailbox and the user who logged on last to that mailbox. As aditional information I also added the Mailbox size and Item Count.
The script i created runs in which it displays the requested information.
Write-Host "$($username) last logged on at: $($dt), the Mailbox was last accessed on $($AdvStats.LastLogOffTime) by $($AdvStats.LastLoggedOnUserAccount).
The mailboxsize is $($Advstats.TotalItemSize) and contains $($AdvStats.ItemCount)."
In addition i wanted to export that information to a csv, which i can again use for information and maybe even further in the eventual cleaning process. However that is failing.
The scriptlet you created only looks at lastlogon to the mailbox and not on the AD object. It could be that the account is still used, while the mailbox is not, therefore I want to collect all that information.
Answers provided are coming from personal experience, and come with no warranty of success. I as everybody else do make mistakes.
Nope
Actually, i retreive information from ADuser
$user = get-aduser $mbx.name
-properties enabled,lastlogondate
You can simply add lines for get-mailboxfolderstatistics
$user = get-aduser $mbx.name
-properties enabled,lastlogondate
$mbxstat = get-mailboxfolderstatistics $mbx |select itemsinfolder ... whatever you want
Then add rows to the table
Itemsinfolder = $mbxstat.itemsinfolder
Got the idea? You can combine any cmdlets and put them into one table
At this moment im kinda busy doing my work, but later i can modify my script to get exact output you need.
In your script, your primary source of data is AD user, i use maibox instead and get the Aduser info from there
Modified my script (few lines above) .. it should work for you (i would run it over all mailboxes though: get-mailbox -resultsize unlimited)

Shared Variables - Properties

Hello,
I have a couple of questions about properties of Shared Variables (SV). They can be configured either by using the dialog box (right-click on SV -> Properties), or programmatically via the "SharedVariableIO" property node. Have a look at the NI-Examples to see how SV can be created programmatically by using the DSC module.
1) The dialog box offers a property "Variable Type" which can be "Network-published", "Single-Process" or "Time-Triggered". The "SharedVariableIO" property node gives no access to this property. Does anybody know why? The same question can be rephrased: How can I create a "Single-Process" SV programmatically?
2) The "SharedVariableIO" property node has two items, "Network.OnScan" and "Network.ConnectionType", which have no direct correspondance to any of the properties available in the dialog box. What is the exact meaning of those properties? The on-line help isn't of much use here...
3) Mutliple SV can be edited by using the Multiple Variable Editor (Tools->Shared Varaible->Multiple Variable Editor). A cool feature is the import/export of CSV-files. I am interested in programmatically creating SVs from the information stored in such a CSV-file. Reading the file is no problem, but connecting the file entries to the properties of the "SharedVariableIO" property node would be quite some job. In principle NI has already solved that within the Multiple Variable Editor. I guess there is a bunch of VIs somewhere below "....Program Files/NI/.../vi.lib that do exactly this thing. Does anybody know, if these (which ones?) are available for public use?
Regards,
Dietrich

dietrich wrote:
1) The dialog box offers a property "Variable Type" which can be "Network-published", "Single-Process" or "Time-Triggered". The "SharedVariableIO" property node gives no access to this property. Does anybody know why? The same question can be rephrased: How can I create a "Single-Process" SV programmatically?
You can't. The single-process shared variable is an old style LabVIEW global placed under the shared variable abstraction. There is currently no way to create those on the fly. Time-triggered also cannot be created programmatically. I confess I don't know enough about them to know the reason why.
dietrich wrote:
2) The "SharedVariableIO" property node has two items, "Network.OnScan" and "Network.ConnectionType", which have no direct correspondance to any of the properties available in the dialog box. What is the exact meaning of those properties? The on-line help isn't of much use here...
Network.On Scan = read/write hardware? - this allows you to programmatically control when you are reading from or writing to configured hardware.
Network.ConnectionType = connect to hardware even when no one is viewing me? - this has 2 choices, UpFront & OnDemand, UpFront means that the variable will be connected to hardware even when no one is connected to the variable. This is useful when you want to reserve hardware or when logging is enabled. OnDemand means that you disconnect from hardware whenever no one is reading the variable.
dietrich wrote:
3) Mutliple SV can be edited by using the Multiple Variable Editor (Tools->Shared Varaible->Multiple Variable Editor). A cool feature is the import/export of CSV-files. I am interested in programmatically creating SVs from the information stored in such a CSV-file. Reading the file is no problem, but connecting the file entries to the properties of the "SharedVariableIO" property node would be quite some job. In principle NI has already solved that within the Multiple Variable Editor. I guess there is a bunch of VIs somewhere below "....Program Files/NI/.../vi.lib that do exactly this thing. Does anybody know, if these (which ones?) are available for public use?
I would advise against using any of these. National Instruments can change, or remove, those underlying files at any time as a result of modifications to the MVE. That could cause issues for any code using those sub-VIs.
Regards,
Robert

Migrating large project from DSC 7.1 to LabView 2009 Shared Variables ... What's the next step after recreating my variables?

I am in the process of migrating a large distributed (multi-workstation) automation system from the LabVIEW 7.11 DSCEngine on Windows XP to the LabVIEW 2009 Shared Variable Engine on Windows 7.
I have about 600 tags which represent data or IO states in a series of Opto22 instruments, accessible via their OptoOPCServer. There are another 150 memory tags which are used so the multiple workstations can trade requests and status information to coordinate motion and process sequencing. Only one workstation may be allowed to run the Opto22 server, because otherwise the Opto22 instruments are overwhelmed by the multiple communications requests; for simplicity, I'll refer to that workstation as the Opto22 gateway.
The LabVIEW 2009 migration tool was unable to properly migrate the Opto22 tags, but with some help from NI support (thank you, Jared!) and many days of pointing and clicking, I have successfully created a bound shared-variable library connecting to all the necessary data and IO. I've also created shared variables corresponding to the memory tags. All the variables have been deployed.
So far, so good. After much fighting with Windows 7 network location settings, I can open the Distributed System Manager on a second W7/LV2009 machine (I'll refer to it as the "remote" machine henceforth) and see the processes and all those variables on the Opto22 gateway workstation. I've also created a few variables on the remote workstation and confirmed that I can see them from the gateway workstation.
Now I need to be able to use (both read and write) the variables in VIs running on the remote workstation machine. (And by extension, on more remote workstations as I do the upgrade/migration).
I have succeeded in reading and writing them by creating a tag reader pointed at the URL for the process on the Opto22 gateway. I can see a way I could replace the old DSC tag reads and writes in my applications using this technique, but is this the right way to do this? Is this actually using the Shared Variable Engine, or is it actually using the DataSocket? I know for a fact that attempting to manipulate ~800 items via Datasocket will bog down the systems.
I had the impression that I should be able to create shared variables in my project on the remote workstation that link to those on the Opto22 gateway workstation. When, however, I try to browse to find the processes on that workstation, I get an error saying that isn't possible.
Am I on the right track with the tag reader? If not, is there some basic step I'm missing in trying to access the shared variables I created on the gateway workstation?
Any advice will be greatly appreciated.
Kevin
Kevin Roche
Advisory Engineer/Scientist
Spintronics and Magnetoelectronics group
IBM Research Almaden

I have found the answer to part of my question -- an relatively easy way to create a "remote" library of shared variables that connect to the master library on my gateway workstation.
Export the variables from the master library as a csv file and copy that to the remote machine.
Open the file on the remote machine (in excel or the spreadsheet app of your choice) and (for safety's sake) immediately save it with a name marking it as the remote version.
Find the network path column (it was "U" in my file).
replace the path for each variable (which will be either a long file path or a blank, depending on the kind of variable) with \\machine\'process name'\variable name
where machine is the name or ip address of the master (gateway) workstation (I used the ip address to make sure it uses my dedicated automation ethernet network rather than our building-wide network)
and process name is the name of the process with the deployed variables visible in the Distributed System Manager on the gateway machine.
NOTE the single quotes around the process name; they are required.
The variable name is in the first ("A") column, so in Excel, I could do this for line 2 with the formula =CONCATENATE("\\machine\'process name'\",A2)
Once the formula worked on line 2, I could copy it into all the other lines.
Save the CSV file.
Import the CSV into the remote library to create the variables.
Note: at this point, if you attempt to deploy the variables, it will fail. The aliases are not quite set properly yet.
Open the properties for the first imported variable.
There is probably an error message at the bottom saying the alias is invalid.
In the alias section, you'll see it is set to "Project Variable" with the network path from step 4.
Change the setting to "PSP URL" with the same path and the error message should disappear.
Close the properties box, save the library, and then export the variables to a new CSV file.
Open the new CSV file in Excel, and scroll sideways to the NetworkrojectBound field.
You'll notice it is False for the first variable, and true for the rest. Set the field FALSE for all lines in the spreadsheet.
Scroll sideways... you'll notice there are two new columns between NetworkrojectPath and Network:UseBinding
The first one is NetworkingleWriter; it should already be FALSE for all lines.
The second one is Network:URL. That needs to be set equal to the value for each line of NetworkrojectPath.
You can accomplish this with a formula like in step 4. In Excel it was =U2 for line 2, and then cut and paste into all lines below it.
There is a third new field, Path, which should already be set to the location of the variable library. You don't need to do anything with it.
Save the edited CSV file.
Go back to the remote library, and import variables from the just-edited remote library CSV file.
Once you have imported them and the Multiple Variable Editor opens, click on done.
You should now be able to deploy the remote variable library without error. (Make sure to open the Distributed System Manager and start the local variable engine. It took me a few failures before I realized I had to do that before attempting a deployment).
Voila! You now have a "remote" library of shared variables that references all the shared variables on the master machine, and which should be deployable on other machines with very little difficulty.
It actually took longer to write out the process here than to perform these steps once I figured it out.
Kevin Roche
Advisory Engineer/Scientist
Spintronics and Magnetoelectronics group
IBM Research Almaden

DSC: Importing Shared Variables results in error -1950679010

This post is more of an "FYI" rather than a question. I am using LV DSC 8.2.
ASIDE: I ran into this problem because I was trying to solve a related problem with Deploy Library.vi (I had dependant libraries that deployed manually, but not programmatically). Eventually, I found the answer in http://digital.ni.com/public.nsf/allkb/8EF71E1DDDC36C908625716900594B50 (not a very satisfactory answer however, IMHO).
During my solution search, another hint was provided with http://forums.ni.com/ni/board/message?board.id=170&message.id=177268&requireLogin=False which hints that using a "Network" defined SV, as opposed to a "Project" defined SV, could help. Then I discovered the difference between NetworkrojectPath and Network:URL in the SV property definition. Then I realized that NetworkrojectBinding is exposed in the Import fields (using the Multiple Variable Editor to do the importing of course), and this gave me the idea of being able to define a Network SV using the Import function.
Unfortunately, it does not work. In the csv file I set NetworkrojectBinding to FALSE, Network:UseBinding to TRUE and provide a valid Network SV path, but this results in error -1950679010: "Shared variable is bound but path or URL is not specified", which occurs when trying to save the LVLIB. It would be nice to know why this doesn't work, as I think it should. I think it is a problem with the SV import mechanism.
David Moerman
TruView Technology Integration Ltd.

Yes, you can do this programatically. I've attached a small chunk of example code (LV 8.5) that creates just 1 variable, as well as an image of it in case you are using an earlier version of LV. If you want to create multiple variables for the same library just put the "AddSharedVariableToLibrary" in a loop, of course.
David Moerman
Attachments:
Create Library and SV.PNG ‏48 KB
Create Library of SVs - BASIC.vi ‏24 KB

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.

Get data in a subreport based on a shared variable from the main report.

Goodd morning,
My question/problem is how to manage this scenario.
I am transfering 2 shared variables (pereiod from /period To, ) from the main report to a subreport and now i would like to get data in this subreport based on these 2 variables...
The problem is that i can not find the shared one in select expert icon...
Could anyone point me to solve this issue?
Thks for any help.
Jose Marin
Crystal Report XI SR3

Hello Jos,
I recommend to post this query to the [Crystal Reports Design|SAP Crystal Reports; forum.
This forum is dedicated to topics related to the creation and design of Crystal Report documents. This includes topics such as database connectivity, parameters and parameter prompting, report formulas, record selection formulas, charting, sorting, grouping, totaling, printing, and exporting but also installation and registering.
It is monitored by qualified technicians and you will get a faster response there.
Also, all Crystal Reports Design queries remain in one place and thus can be easily searched in one place.
Best regards,
Falk

How can I use an Access front end and Access button to control a LabView Shared variable boolean?

My company has invested a lot of money on the office network to write many many access databases and front ends. I'm looking for a way to tie a button on an access front end to toggle a LabView boolean shared variable to notify me when they changed something on their side of the network. I'm not seeing anything that helps on a web or forum search. They don't like the idea of a separate labview control that they have to push a button on to let me know.
Thanks
Solved!
Go to Solution.

Hi Patrick,
While this is not the intended purpose of Network-Published Shared Variables, you might be able to accomplish this by writing separate accessor VIs for reading from and writing to the variable, making sure to wire the inputs and outputs. Then, you could build a DLL, making sure that you include the accessor VIs as Exported VIs and include the DLL Library in the Always Included section of the DLL Build Specifications. During this process, you will define the function prototype, which will provide the function call, required parameters, and return values. Once the DLL is created, you can then call it and its functions from another programming language (C, C++, C#, VB, etc.). This may or may not work, but it is the only way that I can think of at this point. I have included some references that may help you in this process.
Building a Shared Library in LabVIEW (White Paper)
Calling LabVIEW VIs from Other Programming Languages (White Paper)
Calling LabVIEW DLL From C# (Forum with Examples)
I hope this helps.
Regards,
Mike Watts
Product Marketing - Modular Instruments

How to export data to multiple csv files?

Hey Scripting Guys,
As stated by the name I'm a novice at scripting. Typically I'm able to resolve most of my scripting challenges by reading through your site or scouring the internet. This challenge I haven't been able to resolve. Please help!!
I'm running a script (posted below) to grab data and export it to a csv file. My challenge is that I want to run the script daily via task manager and have it create a new csv file either daily or weekly. I'm having trouble with the scripting
creating a new csv file. How do I resolve this?
It would be beneficial to append the date to a standard file name, ex. c:\exportedcsv7-11-2014.csv; the next day it would be c:\exportedcsv7-12-2014.csv; and so on.
Thank you in advance to any assistance.
Respectfully,
ScriptingNovice
Get-Datastore -Name "*DS*" | Sort $_.name | Get-View | Select -ExpandProperty Summary | `
Select Name,
@{N=”FreeSpaceGB”;E={[Math]::Round($_.FreeSpace/1GB,2)}},
@{N=”CapacityGB”; E={[Math]::Round($_.Capacity/1GB,2)}},
@{N=”UncommittedGB”; E={[Math]::Round($_.Uncommitted/1GB,2)}},
@{N=”ProvisionedGB”;E={[Math]::Round(($_.Capacity – $_.FreeSpace + $_.Uncommitted)/1GB,2)}},
@{N=”Over-Provisioned-DS”;E={([Math]::Round($_.Capacity/1GB,2)) – ([Math]::Round(($_.Capacity – $_.FreeSpace + $_.Uncommitted)/1GB,2))}}| `
select Name,CapacityGB,FreespaceGB,ProvisionedGB,UncommittedGB,Over-Provisioned-DS | export-csv -notype c:\vmds.csv

Thank you for the information and the tip. I took your advice and did some research on Strings, something that I do have trouble grasping. I'm familiar with variables already and feel comfortable using them. I also need to study .Net which
I totally don't understand.
Since I appreciate your advice and guidance I'd like to know if I'm on the correct track. Please look at my breakdown to see if I'm explaining it correctly.
$d=Get-Date
Here a variable is being created using the Get-Date cmdlet, if we execute $d the date will appear
$d.ToString('dd-MM-yyyy')
This converts the date into the format dd-MM-yyyy.
I took the information and tips you provided then came up with this after reading about strings.
export-csv -notype "c:\folder\vmds_$($d.ToString('MM-dd-yyyy')).csv"
The double quotes evaluate the variables. The single quotes do not evaluate anything they just show what's inside of them (a.k.a. literal string). The $() evaluate the expression in ('MM-dd-yyyy') before writing it.
You are correct I definitely need to strengthen the foundation of my basics. Thank you for the direction and advice.

Shared variable engine OPC delay

Hello All,
I've got a bit of a problem with the delay time of updates between a non NI OPC server and a shared variable engine OPC client. I am using the redion OPC software OPCWorx with a database of around 120 tags to monitor and log data from a small pilot plant. The OPCWorx server has been configured with a 500ms update rate and the NI OPC client as the same. So here is my problem; logged updates occur no faster that 2.5s which is fine as we are exporting in 3 sec intervals (would still like to increase the performance of this to around 1 sec) but the main nuisance is the delay in changing control registers in the PLCs. The controls and indicators are directly bound to the shared variable items where by a change in a boolean control on the front panel to the indicated response can range from 5 to sometimes 15 seconds delay. If I bind the same control and indicator directly to the OPC item through the data socket the delay in response is almost unnoticeable at around 1 sec. I have increased the update/logging dead bands of the shared variables which seemed to help but only by a second or so.
Im wondering what the limitations of using an OPC shared variable engine is and if this is expected or have I gone wrong somewhere. All the variables are configured as non buffered and to have single writers.
A few changes have been suggested;
- Upgrading the PC. The current hardware is AMD Phenom 2 3.21GHz processor, 4GB of ram running windows XP.
- Using Modbus over ethernet instead of OPC.
This is the first major use of the DSC module and using the shared variable engine as an OPC client so any information or insight to help with this would be much appreciated.

Hi Kallen,
The Shared Variable Engine can become bogged down when there are more than 100 shared variables. This may be what you are experiencing. We can check buffering for the variables and disable it, and that should improve performance slightly. As it is, using datasockets may be the best method for over 100 shared variables. I apologize for the inconvenience.
Here are some KnowledgeBase articles that can be of use with regards to this issue:
How Does Buffering Work for Shared Variables?
http://digital.ni.com/public.nsf/allkb/5A2EB0E0BC56219C8625730C00232C09?OpenDocument
Why Is Accessing IO Variables Through The Shared Variable Interface So Slow?
http://digital.ni.com/public.nsf/allkb/F18AEE4BE7C9496B86257614000C43DF?OpenDocument
Matt S.
Industrial Communications Product Support Engineer
National Instruments

Creating and loading 4000 shared variables

I need some help laying out the design of this system. The data is coming over reflective memory. I've written a dll and a simple server to do the interface between the reflective memory and shared variable engine. Everything seems to be working. The problem I am having is with scaling the application up to handle approximately 4000 variables. I have a spreadsheet to manage the reflective memory allocation and can use it to import the shared variable definitions with the names from the system that is writing the data.
I am having trouble deciding on the best way to proceed. I would like to read a buffer from reflective memory instead of reading 4000 times. I also would like the server to read in a file that defines the association between the shared variable and reflective memory address. The problem I am having is getting the data out of an array into each of the shared variables. I don't see a way to load the value of a shared variable using the property node (so that I can do this inside a loop). I also can't setup an alias that would access an array element. I don't want to manually create 4000 variables.
Any ideas would be appreciated. Thanks.

I have never had to resort to creating Shared variables programatically so I will leave that for others.
I would cheat.
In LV 7.1 DSC i could import my tag config from a csv file. After importing and saving in LV 7.1 I could let LV create the SV's when the code is updated.
THat all assumes I will only have to do that one.
I have used the interupts fired when SCRAMNet locations update to "steer" the value to appropriate code which could then in turn update the SV using a datasocket write since I can compose the URL for the SV dynamically.
Just sharing ideas,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Error -1950679007 when I try to create shared variable binding automatically

Hi All,
I'm using LV 8.5 with DSC.
My aim is build shared variable library automatically. A program read variable name, data type and network binding address from .CSV file. Program works well untill I add this "bind to source" property. I don't know what goes wrong. Does anyone else have found this same issue?
Picture about problem is in attachment.
The error codes are found here:
http://zone.ni.com/reference/en-XX/help/371361D-01/lverror/shared_variable_error_codes/
Other useful information:
http://digital.ni.com/public.nsf/websearch/2E8BAD0EA218A7558625712E0003F044?OpenDocument
Thanks,
Attachments:
error_19506790071.jpg ‏88 KB

Hi,
Now i able to attach the file, While creating Shared Variable,Enable the options which i given in the image by same order. So i think it will solve this problem. If it cont., i will give some more suggestion.
With Regards,
vijay_Conz
Attachments:
Creating SV lib.JPG ‏28 KB

Exporting Shared Variables to csv

Similar Messages

Maybe you are looking for