DSC - Event triggering for Single Process Shared Variables

Hello,
I understand how to set up a Value Change Notification for Network Published Shared Variables so that an event will trigger when that particular Shared Variable changes. However, I can't figure out how to do the same for Single Process Shared Variables. Is this even possible? Can someone shine a light on this, please?
Thanks in advance.
- James Pham
Solved!
Go to Solution.

VRspace4,
Hello! It is not possible to enable alarming for Single Process Shared Variables. A workaround to setup a Value Change Notification would be to create a network shared variable that reads from your Single Process Variable, but at that point in time it might be worth just replacing your variable with a networked shared variable.
Ben Sisney
FlexRIO V&V Engineer
National Instruments

Similar Messages

Using a 2-D array Single Process Shared Variable w/ RT FIFO for comm between a Deterministic and non-deterministic loop on an RT Target

Our problem is that we currently use a 2D array to store CAN data on a Real-time Target. The array is 20 elements of 3 byte elements as so:
                0              1              2
0              [byte]   [byte]   [byte]
19           [byte]   [byte]   [byte]
These values are passed between a Deterministic Timed (DT) loop where they are set and a Non-Deterministic Timed (NDT) loop where they are read and passed into a Network Published Shared Variable (NPSV) for communication across the network to a Host PC. I have insrted an image for illustration, pardon the size.
Currently to pass the data between the DT and NDT loop we are using a Global Variable (GV). To improve the system we have attempted to replace these GVs with Single Process Shared Variables (SPSV) with an RT FIFO enabled.
To create the shared variable I simply right clicked the GV of interest and selected create Shared Variable Node form the drop downs. At this point LabVIEW presented me with a 2D NPSV within a new Library hosted on the RT Target. I then selected this new NPSV from the Project, changed it to a SPSV, and enabled a single element FIFO. This variable was initialized with a default value for the size described above and then used in our code for the DT to NDT communication, and conversion to a corresponding NPSV for sending to the Host.
When I went to run the code I noticed that the variable was in fact 2D, however its size was only 2 elements of three bytes each, in other words only two of the row indices were populated and the other appeared as uninitialized. in addition, this data had no resemblance to the set initilazation value. This was also how the variable was presented on the host side of the network after tranfer into a NPSV.
The peculiar part is that If I change this SPSV to a NPSV and then try to change it back, I receive an error saying the type is not supported for SPSV with an RT FIFO enabled. I have to disable the FIFO (which defeats the entire purpose) in order to successfully compile! I am unclear as to what is the bug in this case. Should I not be allowed to create the original 2D SPSV with a single element RT FIFO enabled without receiving an error? Or if this is okay how do I fix the problems associated with the variable after being allowed to create it?
I have found the following discussion in which a user states “The only limitations for custom controls is the ability to use it with RT FIFO enabled on a network-published shared variable”. Is this also true for SPSV? I have not found any documentation explicitely stating this for SPSV, though it is stated for the NPSVs.

Martin,
RT FIFOs don't support Multi-Dimensional Arrays, which would corroborate the issues you're seeing. You can break up the 2D array into 1D arrays by reshaping the array, then you'll be able to use the RT FIFO enabled variable, just set the array size to the total number of elements (20*3 = 60).
You can also pass the 2D array via pre-allocated queue, or using a Functional Global. We have a reference example for a circular buffer using Functional Globals here.

Why do Single-Process shared variables create a single variable VI in my dir.

I'm creating an application VI following the example which is created by starting a two loop Real-Time project which creates a Single-Process shared variable and a Network-Published shared variable for each variable that needs to be sent to a non-Realtime host VI. Each of the Single-Process variables shows up as a VI file with the following format: <variable library>_<variable name>.vi. The VI has one control which is the shared variable. I have a large number of variables and this creates a lot of clutter in the directory. I expected them to be rolled up into the library file. Is this expected behavior? I'm attaching a screen shot to show the behavior.
Attachments:
Shared Variables in Directory.JPG ‏383 KB

Hi davidreed10,
This is a known issue with single process variables that are saved in a
project that has the .lvproj and .lvlib files initially saved in different
locations, as is the case with Real-Time projects. This has been
previously reported to our R&D department with the ID #56580, and
is being worked on for a fix in a future release of LabVIEW.
This should be only a problem for Single-Process variables, and not
Network-Published variables, so if you want to keep your folder from
getting cluttered up, changing the variable types to Network-Published
should get you around the problem for now.
Regards,
Stephen S.
National Instruments
Applications Engineering

Can't set intial value for cRIO boolean shared variable

LabVIEW 8.0 gives me a configuration error when I try to force an inital value for a Boolean shared variable in my cRIO library. Is that a bug, or am I overlooking some (probably obvious!) limitation of the cRIO hardware?
Jeff
Climbing the Labview learning curve!
Sanarus Medical
Pleasanton, CA

There are 3 screenshots attached to this post. Suppose I create a Boolean shared variable under My Computer in the project directory, then set the inital value as shown in BooleanInitialValue.gif.
If I drag a copy of that Boolean shared variable to my RT target block diagram, the run arrow breaks and I get the error shown in ErrorList.gif.
If I create a Boolean shared variable under my Real Time target (Compact RIO) in the project directory, then set the initial value and hit OK, I get the error shown in FixConfiguration.gif.
Message Edited by Jeff in Pleasanton on 07-19-2006 03:42 PM
Message Edited by Jeff in Pleasanton on 07-19-2006 03:44 PM
Jeff
Climbing the Labview learning curve!
Sanarus Medical
Pleasanton, CA
Attachments:
FixConfiguration.gif ‏6 KB
BooleanInitialValue.gif ‏13 KB
ErrorList.gif ‏13 KB

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

How to determine the source of Events triggered in a process chain

Hi ,
We have almost a 100 process chains, and of these approx 20-30 local process chains are triggered by events raised within other process chains. These events are raised via BP_EVENT_RAISE using the ABAP process type.
However, our problem is to identify the source of these event trigger - i.e. which process chain triggered this event ?
Looking at SM64, the event history does not display the source for these events.
Is there any table or program that we can use to determine the source of these events which are triggered.
Any help is much appreciated and points awarded.
thanks
BK

Hi,
do check in the program /SSA/BWT . or TCODE - ST13 -- enter BW-TOOLS and execute. -- Choose Process chains and execute --- Select the date and time for which you want to see the process chains and execute again.
This will give you the entire list of process chains triggered, status, timings(start, end, overall runtime). Once clicked on the process chains it will show you the steps in theprocess chains, data loaded in the data targets, source system, etc...
hope it helps.

Event triggered for checkbox in cl_gui_alv_grid

Hi All ,
I have a requirement like ,i give PO number on selection-screen.After execution, the items should be displayed on second screen ,which has some options on the top like before GR or after GR .(custom screen designed with cl_gui_alv_grid for display)
I desgined checkboxes for each row of the line item.user can click on multiple rows and click on EXECUTE button on the screen.After that smartform should trigger and print .
Now my query is how to capture the checkboxes which the user has entered (thru cl_gui_alv_grid) . Is there any event that gets triggered upon clicking the checkboxes?? I need the data of the corresponding row to process further .User can click on multiple items.
Please respond
Thanks

Hi Hemanth
You should have a field in your internal table matching the checkbox column in ALV.
Call method CHECK_CHANGED_DATA of CL_GUI_ALV_GRID on user command for execute button,
it will set the field = 'X' for ticked lines in your internal table.
Then use a loop on your internal table and find selected lines.
You don't need an event triggered when user clicks.
Edited by: Bulent Balci on Aug 3, 2010 4:42 PM

RSPPFPROCESS - mail not triggering for incorrectly processed PO

Hi All,
I tried executing the RSPPFPROCESS by giving a variant but I am not able to get the details of any incorrectly processed purchase orders in the output.
The RSPPFPROCESS program functions in such a way that if a PO is unsuccessfully processed, then on executing the RSPPFPROCESS program with status "Unsuccessfully Processed" a mail will be triggered to the creators whose POs were incorrectly processed.
But this is not happening in my case, the mail is not getting triggered at all.
The variant details are:
Application : BBP_PD
Action Profile : BBP_PD_PO
Action Definition : STANDARD_PO
Promotion status : 2 (ie)incorrectly processed
Processing type : MET
Time of Processing : Processing when saving document
The radio buttons: Ignore "Repeat" flag and Ignore "Generated Manually" flag are checked.
The check box "Number of Actions Outputted" is checked.
Please help.
Thanx in advance.
Regards,
Mary Catherine

Hello Prasath,
Please check your configuration on ERP/ECC
side in transaction SWETYPV. Here you can enable or disable the
event type linkage for BUS2012 and for CL_SE_PUR_PO_WF_OUT or any
customer-specific business object related to Purchase Orders which might
be in use. If you disable the event linkage for CREATE and/or change
event, no message will be triggered upon PO creation.
If this is not sufficient for your business process the usual logic is
that all Purchase Order message are being sent out when the event
linkage is active (e.g. you want to send out only some of the message
types possible). In this case you might want to make use of BAdI
PUR_SE_PO_INTERFACE_OUT_SELECT (enhancement spot / BAdI)."
Enhancement Spot: PUR_SPOT_SE_PURCHASE_ORDER
BAdI Definition: PUR_SE_PO_INTERFACE_OUT_SELECT
Interface:        IF_PUR_SE_PO_IF_OUT_SELECT
BADI definition   PUR_APPL_SE_POCONF_IN_ASYN
Also in the standard, for the following messages
   PurchaseOrderChangedInformation_Out
   PurchaseOrderERPRequest_Out_V1
   PurchaseOrderERPConfirmation_Out
we are sending out these information as soon as a purchase Order is
created. We do not distinguish between the services all of them will be
triggered.
Hope this hepls
Ray

Event Used For Return Processing Through Transaction Code-FP09

Hi Experts,
I am facing the following problem in FP09:- After creating a return lot, when i provide return reason code for returning payments, event 1073 is not getting triggered.
So, can you please provide the event that will be used for return processing after supplying the reason code for return.
Else, could you please tell me the event which will be triggered by transaction FP09... so that i will catch return reason code in its parameter.
Regards,
Sumit

Hi Experts,
Thanks for your valuable replies .
But my exact requirement is like:- i need to first check the flag for "Inform Accounting Clerk" in SPRO configuration :customizing (financial accounting)-> contract account receivables and payable -> business transactions -> returns -> configure reason codes.
Field for this flag check is V_TFK045E-BSNTE for the Reason Code-02 , now there is dependency mentioned in SAP like "You can only use this option if event 1073 has a function module defined".
After attaching my Z-function module in FQEVENTS , when i run transaction FP09, it doesn't stop at the set breakpoint of my function module, so what i suppose is that may be event 1073 is not the suited event or transaction FP09 is not the required transaction.
please help me in this regard.
Regards,
Sumit

Events triggered for the infotypes

Good day everybody,
I would like to know which events are triggered for the following infotypes:
1. PA0105.
2. PA0000.
3. PA0002.
4. PA0001.
5. PA0185.
Or can you please advice as to where to look or how to look for it
Thanks in advance,
Themba

Hi...
1) place a break point in FM "BF_FUNCTIONS_READ".
2) excute your infotypes so that execution stops at this FM and gave the event triggered.
Regards,
Lokeswari.

DSC VI won't connect to shared variable outside of project

My main VI will start up and connect to shared variable if I first have my project open. It will not connect to them if I try to run it by itself. I am deploying the library programmatically, but that doesn't seem to help.
Also, I can't get the main VI to run on startup.
Thanks

Hi Brian,
Thank you for the additional information. Let's put aside the run when opened issue and try to work on having your variables deploy and connect successfully.
When you run the VI within the project, are the variables successfully deployed as well?
Where are you seeing that the path to the library is blank? Where do you see that the data binding path for the variable in the working VI gets changed?
It would be quite useful for you to post a small example project, with one library, and we can tackle these questions individually, as with so many configurations (in project, not in project, running when opened, deploying successfully), I am having a little trouble keeping them straight.
Trying my best to help,
-Sam F, DAQ Marketing Manager
Learn about measuring temperature
Learn how to take voltage measurements
Learn how to measure current

Multiple triggers for single popup

Maybe it is dumb question to ask... sorry if that is so but...
Is it possible to have several triggers in different parts of page for the same action? E.g. I want to open one lightbox by means of five different buttons. How to do that?
Thanks.

Hello,
You can Simply do that by creating copy of single trigger light-box slideshow widget, Please find below the step by step suggestions.
1. Create a light-box slideshow and Design it as per your requirement (Create it with a single trigger)
2. Go to the options and uncheck "Show light-box parts while editing"
3. By doing this you will be able to see only the trigger on the page.
4. Now copy that (Slideshow) and paste it on the desired locations.
5. It would look like its launching same light-box for each trigger as they all are the same copy.
Regards
Vivek

Changing shared variable reference modes for all nodes in application. Shortcut?

I have a large application which makes extensive use of both network-published and single-process shared variables. I want to change the reference mode of every such node in the application from absolute to target-relative. Is there any way to do this without having to open every subVI in the application and use the right-click menu on every node?
Sean

I don't know of any shortcut, but if you want to change the reference node of everything in the application you could probably script it. I was thinking something similar to what I have below where you traverse the BD of a specific VI for all SharedVariableNodes and change the relative mode to Target Relative.
Depending on how your project is organized you can add some additional functionality before the open VI reference to go through and open the reference of every VI in your project.
Matt J
Professional Googler and Kudo Addict
National Instruments

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

Shared Variables vs Globals

   I started a large project recently and decided to make use of Shared Variables. :I need some network communication between LV apps, so that is the main reason, but I decided to put them to the test by also using single-process Shared Variables instead of globals. (Yeah, yeah, globals are evil. blah blah blah. I'm not really interested in dogma here. Suffice it to say that, IMHO, there are still a few times and places where globals are appropriate and useful.)
   My project is fairly modular, and the main control program launches numerous other top-level programs. The problem is that whenever one of these top--level programs (or the main program) is launched, the Shared Variable deployment window pops up and does its several second initialization.; If this happened just once, when the top level program launched, it would probably be acceptable. But having each dynamic VI go through this gets annoying.
   I'm using 8.2.1. I haven't tried 8.5 much yet, but at least in 8.0 and 8.2, you can't search for Shared Variables. That is also annoying and can lead to maintenance issues.
   So now I am considering replacing all the single-process Shared Variables with good-ole Globals. A couple of the VIs in the system will still use networked Shared Variables, so they will still cause the deployment window to pop up, but it will be much less frequent. And I'll be able to search for the globals and make sure I'm using them responsibly.
   Does anyone have any other ideas on how to minimize the deployment window? Or ideas on development patterns using Shared Variables? Preferences for Shared Variables vs Globals?
Thanks,
    Dave
David Thomson Original Code Consulting
www.originalcode.com
National Instruments Alliance Program Member
Certified LabVIEW Architect
There are 10 kinds of people: those who understand binary, and those who don't.

Ben,
   Wow, you are quick. And thanks. Good catch. Turning off the auto-deploy removes the dialog. Nice, but now I have to figure out how the SV's are going to get deployed on each installation... I haven't fully digested how SV's really work, especially how to best handle the deployment issues. This project will be installed on a number of computersand used by scientists, not LV programmers. So I need a reliable way of setting up the deployment. Perhaps it is just one more step in the installation process.. That assumes that all the SV's are defined when the program is first installed The program is very modular, so the end-user will be able to copy new modules into a certain directory and be able to use them right off the bat, no extra programming. But if a new module contained a new SV, it wouldn't be deployed...
   Any suggestions for searching? I haven't tried it yet, but it seems that deleting a SV from the project is the only way. That causes an error to occur at each instance of the SV. Assuming all the project VIs are in memory, you can then use the error finding to locate every instance of where the SV was. Of course, it isn't there anymore. Minor issue...
Graziano,
   Thanks for the ideas. I do use functional globals a lot as well. Very nice tools.
   I was really trying to transition to SV's so that I could use the Networked version. I was using Single Process SV's instead of globals just as an experiment and to potentially leverage other SV features for them in the future.
Regards,
   Dave
David Thomson Original Code Consulting
www.originalcode.com
National Instruments Alliance Program Member
Certified LabVIEW Architect
There are 10 kinds of people: those who understand binary, and those who don't.

DSC - Event triggering for Single Process Shared Variables

Similar Messages

Maybe you are looking for