If you are in need of a paid programmer to write your Unitronics’ project, post here to look for someone in your area. **Disclaimer: Unitronics bears no responsibility. This is just a place for people to find each other**
If you are a Unitronics programming guru looking for projects, post here to look for someone in your area. **Disclaimer: Unitronics bears no responsibility. This is just a place for people to find each other**
Yes the analog input settings are set correctly, both 0-10v as well as the outputs. The ranges are also the same on all.
I have since tried wiring the outputs straight into the inputs and giving the output a number. The input is reading is different to what i am giving the output which is strange
Yes, it's clear how it works on the PLC at runtime, I was referring to the editor, how to manage all the pop-up windows since they'll be placed over other HMI elements (at least in my case) and in the Unilogic editor that would cause some trouble in case the underneath HMI elements need to be accessed for editing.
I have made a quick test and placing pop-ups on a dedicated layer seems to be a nice practice, if that layer is hidded then the "regular" HMI screen is all accessible for editing.
Said so, this solution is a workaround for my initial quesion, I still hope that Unilogic staff will introduce native supporto for pop-ups one day...
Correct.
I place all the controls stacked on top of each other. By pressing the motor image (or the button or whatever you use to pop-up the control), reset all visibility tags and set the desired one.
I see, thanks.
So if I need to add a pop-up window on every motor on a synoptic screen I'll have to place all the custom controls on screen and associate tags for animation/logic.
In this case, to avoid an over crowded HMI screen in the Unilogic editor what's the best strategy?
Place all the pop-ups on a dedicated layer as suggested by @Joe Tauser to show/hide on necessity while editing the regular HMI elements?