08-17-2025 03:23 AM
Hello everyone,
I recently tried out xControl.
I had an application that could be adapted (at least I think so...).
In a few words, I need a control called “Valve” that allows me to:
- Have a Boolean that activates a DO output - the actuator
- Have a Boolean that allows the limit switch contact to be shown as open on a DI input - the CPO
- Have a Boolean that allows the limit switch contact to be shown as closed on a DI input - the CPF
And, of course, some logic:
- The controls on the front panel must be DataBinded (actuator, CPO, and CPF)
- A deactivation logic when automatic operations are launched (ideally in DataBinding, but I didn't really succeed... so it's a property that is written in the user VI).
- A color change logic via properties (adapt the color of the fluid to the control)
- A normally open or normally closed valve logic via properties.
In short, everything works fine when I test it!
But when I put two xControl Valves on the same front panel VI: Both indicators are bound to the same URL... Even though I only bound one.
I feel like I can't unbind them.
Below are the two xControl valves on the same VI:
The first one is correctly bound via this property, as we can see from the small green indicator above it.
The second one appears to be unbound, but that's not the case. When I change the states for valve 1, valve 2 is bound directly and is no longer “independent.”
Basically, I have the impression that xControl uses the same databinding reference, but that's not what I want...
Do you have any ideas on how to avoid or fix this problem?
I've looked into QControl, but I'd like to see if I can solve the problem with xControl because maybe the problem can be exported to QControl... ?
I hope I've been clear...
Thank you very much in advance!
I'm running Windows 10 and using LabVIEW 2024 Q1.