What future features would you like to see in groov View?

groov View
203

It would be good if the clearing events logs were restricted for kiosk user

In the Current version clear vent log has not restrictions,

Application alarms can be cofigured as events, for example product hight level alarm and spill, if event logs is cleared, It would be difficult to analyze what happened.

204

I’m delighted with my groov epic system, and (coming from an entirely separate industry from industrial controls) my first go-round getting a system like this up and running has been a very fun and surprisingly painless experience – excepting a few items. I performed the clean-sheet trade study for my company to down-select to groov EPIC from a wide range of options, and feel very vindicated. So, these requests are in a constructive spirit, but some of these are at the start of this seven-year-old thread.

Critical Priority:

  • Grouping and layers for gadgets. So many of recommended solutions to various UI requests involve having stacked gadgets whose visibility is toggled via a tag – so it’s agonizing to then try to make changes to something midway through a stack by picking through it.

  • Is there really not an undo button? Or even just a way to discard build mode changes and revert to the last saved state? This is not good – tell me I’m missing something.

Medium Priority:

  • The sundry features for which OPC-UA is the limiting factor, like the inability to save tag data with an exported page (json) or find/replace tag names and the various other tag organization issues. It seems from the start of the thread that OPC-UA is the reason here, and that enumeration would take too long for certain customers. Can a system-wide setting be made available to perform enumeration at startup, and customers with 10,000+ tags can just choose not to use it (and opt out of the features that everyone else wants?)

Low Priority:

  • Any further support for using tags to drive gadget appearance properties
    • Our use case involves scenarios where we may be altering the aforementioned red/yellow limits on the fly, or switching between regimes of limits. In a very general sense, I should be able to make a computed tag that spits out a color value, and just assign the text color to that tag. If I have a gadget based on a numeric value range, the range limits should also be able to be assigned to a numeric tag instead of a static value.
205

Funnily enough, Undo / Redo and gadget grouping are exactly what I’m working on right now. I’m hoping to have a release coming up towards the end of the summer.

5 Likes
206

Dropdown gadget would very helpful for space limited HMI screens.
Undo button

1 Like