stoic-one (Customer) asked a question.
Tri-State Switch Color for OFF/Reset State
Looks like the Tri-state switch has been replaced with Multi-button/Indicator which can be made to look the same but appears to require an additional bit to do so.
I use a lot Tri-state's for OHA/HOA's(Off-Hand-Auto) or where I enter bits for the 2 later states. My problem is there doesn't appear to be a way to illuminate the reset button on the Multi-state without assigning a bit to it that is associated with a tag.
In the picture is a Tri-State in the off state, there is no tag associated with that state, any way around this besides assigning an internal or PLC tag and using it for that state?
The best approach is a radio button, no reset flag, and assign a placeholder internal tag for the reset state.
While I agree that will work, especially since I already tried that, if I have a screen full of motor OHA's that's a unique internal tag for every motor, no?
Correct. Early in the design phase, we noticed this and decided the effort to add a tag is about the same as the effort to configure an On state for the reset button, plus having a tag to show the control is active or not may be useful - so we left this as is. I'm happy to reconsider if we missed something, do you have concerns about lots of extra tags, or is it just more work to set the buttons up this way?
If that was the the design consideration, it is what it is.
I just wanted to verify that that is a setup feature/anomaly of that particular object which has essentially been obsoleted by converting that object to a Multi Button.
For now that is the case. We will not claim that we're perfect. I've been retesting this scenario this morning and see that while the radio button works, the conversion isn't as automatic as we'd like. I'll get with the dev team and see what it would take to add an "on state" setup for the reset button so that the conversion will be exact. At this stage, the window for changes is closing, so it may or may not make V9.0 - it depends on the development effort.
Thank you for bringing this to our attention.
Fair enough, and thanks.
Any idea when the approximate release date will be?
Also, as an aside, I just wanted to comment on the speed of this version. As it stands, it doesn't just render graphics screens faster, it's also significantly faster and more responsive when using the app and the remote HMI desktop connection. I use both of those methods a lot during testing and commissioning. Might want to toss that nugget into the features list.
I can't provide an exact date, but soon. When we started this process, we also decided to overhaul the help files. It doesn't matter how good the product is if you don't tell people how to use it. At this stage the code is substantially done - maybe time for a few final changes. The documentation is coming along but we have a few more weeks of work to tie it all together. There is always a caveat, that we may find something critical that causes an unexpected delay, but I think we are close.
Too late to fix a misspelled word?
Thanks - we'll get that taken care of.