LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Dynamic creation of LV2 global

No probelm Ace.

Side note:

The contributors to this exchange "wear their hearts on their sleeves" well actually it is their "bar"s.

What I mean by that is the first of the three bars you see under a user names represents their average rating they recieve for the answers. Well when the exchange was first developed someone decided that get the frist bar to be a solid gold color ("Proven") the user must have a 4.5 average. Anything less than that and they are down graded to pale gold (Trusted).

So what this means is anything less than a "5-star" rating is actually a negative rating (Yes we all agree that does not make sense!). Smiley Sad

So....

If you want thank someone for what they have done, give them a 5-star rating.

Otherwise, just say thank you and resist the temptation to give anything other than a 5-star.

This can really hurt the new contributors where they have not accumulated a lot of rating yet.

Still trying to help!

Ben

Now lets see if I can get some help on fixing things Smiley Wink

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 11 of 19
(1,629 Views)

Hi Ben,

      This is an interesting subject.  I think the named-queue approach is clean and straight-forward.  But since you mentioned loading/saving VIs with unique names, I'm curious whether you might have considered launching multiple copies of one reentrant [LV2global] VI - each instance with a unique reference.  Seems like it might be simpler, but things are not always as they seem! Smiley Happy

?

When they give imbeciles handicap-parking, I won't have so far to walk!
0 Kudos
Message 12 of 19
(1,604 Views)
Ooops, sorry - no negativity intended.  Any way to change a rating once submitted?
0 Kudos
Message 13 of 19
(1,594 Views)

Hi Dynamik,

You asked

"I'm curious whether you might have considered launching multiple copies of one reentrant [LV2global] VI - each instance with a unique reference. "

I can't say I remember actully do that. That is an idea that I have toyed with but generally leaves my head spinning trying to keep track of which memory space I am working in at the moment.

More often that not I have been going the queue route when ever I have data that starts somewhere and has to end up in the inbox of a single entity. Ever since the queue data types could be defined and we did NOT have to flatten to string then un-flatten, the queue performance out classes anything else I can code up.

They are particularly powerful if you want to establish high speed data paths between entites that know nothing about each other at development time. Jim Kring once published a desgn pattern that combined queues and notifiers to send command from dynamic entities to a single server and then notify the consumer the request was completed. I have carried that another step farther by putting a queue ref inside a queue. This architiecture works a lot like a "mass mailing" with "self-address stamped envelopes". Lets see if I can elaborate and stiull get the idea across.

A seperate proccess creates a named queue into which servers can submit entires.

When entries are recieved the messgae is added to a list kept in a LV2.

When a client want to know what services are available it looks in the LV2 and finds one it likes.

The entry that it picked has a queue in it. The client submits an entry to that queue to request it be included in future updates.

The server detects the request from the client when it discovers the new entry in the queue and adds the include queue in its list of clients to update.

The client then watches its queue for the updates.

I expect the above is very clear.

The above structure allows me to develop generic "viewers" that allow the user to choose a value they want to monitor and a request is sent to the entity that serves that data to be included in its updates.

Enough rambling for now,

Ben

BTW: Occationally Molly will re-boot the server of the Developer Exchange. After that happens, the Exchange "forgets" about who rated what answer and they can be "re-rated".

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 14 of 19
(1,580 Views)

Hi Ben,

Need to study this, I do.  Hope Jim's work is easy to find - have to admit I was a bit fuzzy on your "mass-mailing" section.  (partly lack of sleep.) Smiley Happy

Your multiple-VI-copies idea peeked my interest because reentrant VIs, while not a good solution here, can work well when  multiple identical objects are needed.

Thanks, Cheers.

Message Edited by Dynamik on 04-27-2006 12:43 PM

When they give imbeciles handicap-parking, I won't have so far to walk!
0 Kudos
Message 15 of 19
(1,561 Views)

Here is the URL for Jim's design pattern

http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3D9CD56A4E034080020E74861&p_...

RE: My mass mailing with self-addressed-stamped-envelope

You should have seen the looks on my developers faces when I first explained to to them. Smiley Surprised

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 16 of 19
(1,554 Views)

Excellent, Thank you!

When they give imbeciles handicap-parking, I won't have so far to walk!
0 Kudos
Message 17 of 19
(1,549 Views)

Hey Ben,

     FYI, Twice downloaded the zip, but Winzip says the file is corrupted!

 

 

When they give imbeciles handicap-parking, I won't have so far to walk!
0 Kudos
Message 18 of 19
(1,518 Views)
0 Kudos
Message 19 of 19
(1,509 Views)