LabVIEW
Logic within an array of clusters
Solved!
At this point I'm not sure its the best approach, plus its apparently not possible to do it as someone else pointed out. But I'll show you what I had in mind. At this point I would gladly implement int through any other mean. One thing I was trying to accomplish was to make the interface as simple as possible.
The logic part would be like this:
The frequency gauge has a minimum and maximum set by the values of the bin cluster. The frequency cluster indicates the "center frequency" (in the first element its 1) and the range where its deviation would be considered a failure (1-0.4 and 1+0.4). Those ranges are shown colored with high saturation yellow, before reaching the 0.6 and 1.4 range there is a white to yellow gradient. The amplitude Gauge has its minimum value set by the basal control of the amplitude cluster, and has in a analog fashion, the "failure" range yellowy colored.
The spectrum would probably be something like this:
Of course there would be redundancy between the gauges and the spectrum, but I was trying to make it friendlier
@Neuromodulator wrote:
At this point I'm not sure its the best approach, plus its apparently not possible to do it as someone else pointed out. But I'll show you what I had in mind. At this point I would gladly implement int through any other mean. One thing I was trying to accomplish was to make the interface as simple as possible.
The logic part would be like this:
The frequency gauge has a minimum and maximum set by the values of the bin cluster. The frequency cluster indicates the "center frequency" (in the first element its 1) and the range where its deviation would be considered a failure (1-0.4 and 1+0.4). Those ranges are shown colored with high saturation yellow, before reaching the 0.6 and 1.4 range there is a white to yellow gradient. The amplitude Gauge has its minimum value set by the basal control of the amplitude cluster, and has in a analog fashion, the "failure" range yellowy colored.
The spectrum would probably be something like this:
Of course there would be redundancy between the gauges and the spectrum, but I was trying to make it friendlier
Ok, so we have an upper limit of 5 clusters with identical logic.
Ideal for subpanels running a single reenterant vi.
Asynchronously launch n clones of limit.vi ( pass in index, process event refnum <of data type DVR of new spectral data> and an exit event refnum <book> is fine but you can get fancy and a notifier refnum to pass status back to main. Load n clone instances in n subpanels on screen and kind of hide a few "expansion subpanels.
Bonus for horizontal resizing the subpanels and the visible pane of the clones based on n (use vert splitters) for a nice UX.
The logic is all the same! Just a few parameters need to be configured per monitor instance.
You did not mention alarm response or logging requirements so you are on your own to get the "User Story" there. But you are definitely not at a brick wall!
One note further. Really do talk to the user. Giving a user that much control of limit changes is often a mistake. That GUI you show and describe looks like an advanced engineering turning utility that helps create a configuration file for daily production or normal operations.
