Having two panel screens??

[ChristianRoth]

I have many differnt gauges as well as a large chart that needs to be displayed while aquiring data. Is it possible to have two panels active during this process?

[DaveR]

ChristianRoth wrote:
> I have many differnt gauges as well as a large chart that needs to be
> displayed while aquiring data. Is it possible to have two panels
> active during this process?

Hi,
have you tried the Tab Control (Array and Cluster Controls Palette). I
actually prefer the one from the classic Controls Palette because it's
easier to look at! It's a very easy way of creating as much space as you
need on the panel.

Regards,
Dave.

[Ben]

HI Christian,

I recently developed an app that had (3) screens open at one time (if the user desired).

All of the HS DAQ was on one screen.
All of the Serial tranactions where shown on another.
A third gave the user acces to the RT system.

This allowed the user to put what he wanted on the primary monitor and allowed the others to be moved over to the second monitor.

Yes you can. Make sure they "all play nice together" (i.e. no one hogs the CPU etc).

Ben

P.S. If you just interseted in grouping related controls and do not for-see a need to watch values from different screens at the same time, look into the tab control.

[bertrandl]

Hi Ben,

I'm building an application that will have three screens. But the three screens are diplaying the same VI and use the same diagram.

How can I fix my elements in my front panel ?

thank for your answer.

sorry for my language, I'm french and son't speak english very well

Bertrand

[Ben]

Hi Bertrand!

Feel free to post your own question in french. Some of our best Enthusiats speak french. I said some of our "best". Not me! I took french for 5 years in high school and never passed french 2!

It sounds like your case is different from the case I mentioned above because I was running three DIFFERENT VI's.

LabVIEW only allows one copy of a VI in memory at a time. This is entirely based on the name of the VI. You may be able to adapt to this restriction by copying your VI as three distint names e.g. VI_1.vi VI_2.vi, VI_3.vi.

This is the easiest approach and will work provided your sub-VI's do not have any trouble being called by different "main" VI's.

If the simple "re-naming" works for you good!

If not, I suggest you po
st a new question and include a copy of your VI so we can look and advise.

I hope this helps,

Ben

[PJM_Labview]

Bertrand

Utilise un fichier VIT [juste renome ton VI en vit] (VI Template). Chaque instance devient une interface reutilisable (code et UI). A chaque fois tu auras une copie differente en memoire. Tu peux aussi passer des parametres par l'intermediare de VI server.

And now the english version 🙂

I Told Bertrand to use VI Template. Every instance is basically a reusable User Interface. Parameters can be passed via VI server.

Cheer

PJM

[Ben]

Like " I said some of our "best". "

Ben