How does the Global Variable work in the FP window?

[ASIC_LabRat]

I wanted to get the "instrument reply string into a variable display in the FP window. so I assumed the Create>Global variable would do the job. When I run the panel in interactive execution, the reply in the box is "no variable!" ? i wa looking to see the entire *IDN? query string

Thanks

ChipB 

Message Edited by ASIC IIBU Tech on 11-14-2007 01:54 PM

[Albert.Geven]

Why not use an indicator. Or are you talking about a FP of another vi?
Then a global could be used. But if you want the display in the same vi an indicator is perfect.

[ASIC_LabRat]

vi? are you talking LabVIEW? No I am refering to the instrument Function panel (fp) in the LabWindows CVI enviroment and the want to create a global string that I don't have to declare.

[nickb]

Hi Chip,

Have you written the *IDN? query string to the global variable that you are referrencing on the function panel?  This will only display the value of a current global variable in a function library.  If this is not the case you will need to write the string that you want to see to the global variable that you are referencing from the function panel.

NickB  
National Instruments
Applications Engineering

[ASIC_LabRat]

I put a PPT file up there. not sure if this is a Classic/Intergrated view problem. I am using the Classic view.

Thanks

ChipB @TI

[nickb]

Chip,

The global variable  control that you are using will only display variables declared in both the .c and .h file of the function that you are currently working on ( where at86100x_initilize() is declared in this case).  In the c file, it should be declared as a char, and in the h file, it should be declared as an external char.  Once these two things have been done, it should work.

Nick Beer
National Instruments
Applications Engineering

[ASIC_LabRat · Accepted solution]

Thanks Nick.

That did the trick

With the additional Fmt added to the instrument reply, I have a clean instrument reply string that has all of the model/serial/firmware and revision string... It also did not change any of the instrument driver init callback so as far as the users are aware... nothing has changed!

Cheers!

ChipB