Is there a better way to do 'late' binding of HMI controls

[viScience]

Currently, if you want to programmatically bind HMI controls and indicators to network URL's you need to first set, at edit time, a fake

URL (example: \\192.168.0.3\cRIO-HPU\'PU.Accumulator_Dump_Valve') since the actual IP address may not be known at edit time.

If you leave the HMI 'unbinded' then the attempt to set the BindingPath properties will result in an error.

It would be nice if you had a generic option called 'late binding' that you could select with the expectation that the exact URL will be set

at runtime.  This would provide an additional benefit where the  PSP driver could wait for a BindingPath to be set before attempting

the first transaction.

[viScience]

Currently, if you want to programmatically bind HMI controls and indicators to network URL's you need to first set, at edit time, a fake

URL (example: \\192.168.0.3\cRIO-HPU\'PU.Accumulator_Dump_Valve') since the actual IP address may not be known at edit time.

If you leave the HMI 'unbinded' then the attempt to set the BindingPath properties will result in an error.

It would be nice if you had a generic option called 'late binding' that you could select with the expectation that the exact URL will be set

at runtime.  This would provide an additional benefit where the  PSP driver could wait for a BindingPath to be set before attempting

the first transaction.

[GoCougs]

There could be a better way to do this, but it depends on what you are trying to do.  Please explain your application and what you exactly want to do between the HMI and the cRIO.  Also, the exact hardware of the HMI and cRIO will be helpful as well.

[viScience]

Well Initially I set out to be able to programmatically retarget my HMI bindings while the HMI was running.  This required the ability to set the binding URL property for each control or indicator.

to be able to do this in runtime you first need to set each HMI control property to temp URL at edit time, so that it is classified as being bound when the runtime gets around to trying to retarget.

I just thought that there could be a boolean property 'late binding' lets say that would allow the runtime to be able to set the binding URL even if it was not set at edit time.  BTW, my HMI is on a windows pc and my RT targets are all cRIO's

[GoCougs]

I understand what you are asking, and at this point, you can only do the binding with having a "dummy" URL at edit time.  You can always submit a product suggestion and see if it gets included in the next versions of LabVIEW.  The Product Suggestion URL is http://digital.ni.com/applications/psc.nsf/default?OpenForm&temp1=&node= I hope that helps!