Front Panel Mass Binding Project Variables Issue

[decroosj]

Hello -

When attempting to bind controls to shared variables through the front panel mass binding option, there is an issue where you can not seem to bind a "project item" to the control. The method of binding I am using is to export a text list of control names, urls, mode, and function to a text editor utilizing the front panel binding mass configuration options.  The text editor shows, in the fourth column, a "0" for no function, a "1" for network item, and a "2" for project item. when attempting to import the list back into the front panel binding mass configuration, all "2" indications become "1", as all items are treated as network. Thus one can not effectively bind to a project shared variable item.

The binding works fine manually by means of utilizing the properties selection of the control, but it is difficult to do this for 821 controls, as in my application.

My application is based on a OPC served group of 821 variables which are linked to controls and indicators through the shared variable representation for each item created in the multiple variable editor.

Does anyone have a work around for this issue, as it is a showstopper right now, ie, you can not effectively bind a large quantity of controls or indicators to project located shared variables as required.

The rationale behind utilizing project located variables instead of network located variables is to reduce the amount of calls to the OPC server which was causnig a large latency in the refresh of the 821 items. With the items defined as shared variables within the project, a single call is issued, which has tremendously sped up the refresh cycle for the list of variables.

Thank you in advance for your insight in this matter,

John DeCroos

[Efosa O.]

John, how are you?

Sorry for just now answering this post. Are you still having this problem?

Are you able to start a new project and use Front Panel Mass binding on just a couple of shared variables?

Please let us know if you are still having issues regarding this.

E.O
NIAE

Message Edited by Efosa O. on 06-20-2006 03:55 PM

[mbtoday]

I'm about to start using Front Panel Mass Binding in LV 8.5.1 with DSC.  Has this issue been resolved by now?

[Brinoceros]

Hi mbtoday,

I just gave this a try and was not able to recreate the issue brought up by John.  It seems that either this issue was fixed, or there was some other cause that was not completely assessed at the time this thread started (in 2006, and John did not follow up with any more information for Efosa).  Hopefully this puts your concern at ease!

If you have any more questions or concerns, please make a new thread so the community can better support you.  It really does make a difference!

Regards,

[decroosj]

Hello Brian A.,

In response to you comment --

"in 2006, and John did not follow up with any more information for Efosa"

 -- a great deal of information was provided to NI (Efosa and many, many others, up to the product manager for the DCS module). I have never heard back on a fix for this bug for the identified version of LabVIEW. The reply by Efosa here was well after we had shipped our product -- (please see date + Efosa's apology) -- we had found our own solution as is identified in the original post.

My solution was, as is also indicated in my original post, to manually bind each variable. This was unbelievably time consuming, but was all I had.

The version of software I am now working on uses far less variables, manually bound to avoid the multiple binding issue we had in the past.

I have checked the mass binding function in LV 8.5.1, it works fine now. I guess it would have been nice to have had a reply that the bug had been resolved ---- would have helped me out a bit.

Thank you,

John DeCroos

[mbtoday]

I'm glad for the confirmation that it is working now, but sorry for the pain you had to endure.  I think I'm going to take a different route and bind the controls programmatically from a configuration file at program startup time. 

[Brinoceros]

Hi John,

I retract my comment and apologize!  The only information I had was this thread, so I did not know about any other follow-ups.  I do apologize for my error!

I am also sorry for what you had to deal with regarding this issue.  It's never any fun dealing with bugs, especially something that's such a showstopper!  We do often try to let people on the forums know when a bug they have dealt with is fixed, but we don't always find all of the threads once the fix has been made.  In any case, we always appreciate your feedback and your efforts made to help us work on any bug-type issues.

On the bright side, at least it seems to be fixed now!