LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Graph property node


@Carlz wrote:
Hi

The problem is that in this VI I cant switch into block diagram view, and Im not sure how to switch to start using the new properties Xscale and Yscale.

What do you mean you can't switch to block diagram view? Is the VI protected? Or, was it saved without a block diagram. If it's the former, then you need to get the password. If it's the latter, then there's nothing you can do other than to try to get the original code.
0 Kudos
Message 11 of 19
(1,948 Views)
The key to the problem is why you can't open the block diagram. What happens when you try? If it's password protected, then your only options are to find the password or to rewrite the code.
0 Kudos
Message 12 of 19
(1,947 Views)

Hey again, thank you for trying to help me, I really appreciate it 😃

The option "Show block diagram" is grayed out so it cant be choosen from the drop down menu. Does that mean there is no block diagram or that it is protected somehow?

Is it possible for me to just "recode" the front panel by exchanging the Xscaleinfo and Yscaleinfo into Xscale and Yscale + other corresponding properties? And in that case, what is the most simple way of doing that?

Cheers

 

 

0 Kudos
Message 13 of 19
(1,930 Views)
Hi Carlz,

when that option is grayed out then the block diagram is missing (it was removed when saving the vi). You need to get the original development vi with it's (not password protected) block diagram!

"just "recode" the front panel" - you have to recode the block diagram, changes to the frontpanel will not help you (will only result in broken vis...).
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 14 of 19
(1,922 Views)
I think I actually managed to solve the problem by changing the property node output xscaleinfo and y scaleinfo with all the corresponding properties for 8.2. I then bundled them exactly the same way as the x/y-scaleinfo was done. I also changed x0 and delta x to offset and multiplier on the front panel. Atleast I dont get any warnings, do you think it works as it should?
 
I also ran across another issue. The GPIB write/read doesnt work on an instrument connected to my USB GPIB interface. VISA write/read seem to work. Why is this the case?
 
And another thing: one of my 3 instruments is giving these really long strings with random symbols as answer to any query. eg. IDN?  Im gonna try to connect it to and classic GPIB PCI card and see how it responds. Anyone have any idea what could be the problem? Could it even be a software error?
 
Cheers
0 Kudos
Message 15 of 19
(1,900 Views)
Hi Carlz,

when you rebuild the older scaleinfo cluster your vi should work as before - you have to test it, we cannot check this without actual code...

USB/GPIB uses different drivers than "standard" GPIB cards, I had such a problem too. Well, you should prefer VISA anywaySmiley Wink It will make your programs (more) independent of the used bus system!

One of your instruments is making problems. OK. How can we help, when we don't know anything about the instrument nor your program?
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 16 of 19
(1,897 Views)

And another thing: one of my 3 instruments is giving these really long strings with random symbols as answer to any query. eg. IDN?  Im gonna try to connect it to and classic GPIB PCI card and see how it responds. Anyone have any idea what could be the problem? Could it even be a software error?

I have usually seen this when 2 instruments had the same GPIB address.
0 Kudos
Message 17 of 19
(1,882 Views)
It says that they are on different adresses, so I dont think that is the problem. Im confused on what to do with the instrument, but I'll leave that for later right now.
 
A new problem has come up for me:
 
What is the corresponding visa function for triggering several instruments (adress list) that can be done with the "Trigger multiple istruments" in GPIB 488?
 
Im remaking this huge program built up by gpib write and read into using visa instead. So I ran across this function and now im not sure what to do...
 
Cheers
0 Kudos
Message 18 of 19
(1,863 Views)
You can use the VISA GPIB Command to send GPIB commands that don't have a VISA function provided. The command you want is GET for Group Execute Trigger. Unfortunately, while the NI-488.2 manual defines the command, I have no idea how to specify the list of addresses for the VISA GPIB Command. In C you would just pass an array of addresses.

An alternate, but clumsy solution, is to extract the addresses from the VISA resource name references and use the regular GPIB function, like so:



Like I said, clumsy, but it should work.


Message Edited by smercurio_fc on 06-27-2008 09:19 AM
0 Kudos
Message 19 of 19
(1,850 Views)