LabVIEW
Logic Gates & Sequential Logic
@Mark_Yedinak wrote:
You should also be aware that LabVIEW has a context sensative help which is very useful for folks new to LabVIEW. Simply hit Ctrl-H on your keyboard to display the help. It will update with th eappropriate help information for whatever is currently under the mouse pointer.
I was always annoyed that if you wanted to see the "Click here for more help" that by the time your mouse pointer got to the context help box, it invariably rolled over something, changing the contents of the box! Sometimes the detailed help that you need is available by right-clicking and selecting "Help" from the pop-up menu, but what if it isn't? I solved that by right-clicking to bring up the pop-up menu. Leave it open. That takes the mouse focus off of LabVIEW, allowing you to move the mouse to the context box unmolested so you can click on the link...
P@Anand wrote:
@billko wrote:
@Mark_Yedinak wrote:
You should also be aware that LabVIEW has a context sensative help which is very useful for folks new to LabVIEW. Simply hit Ctrl-H on your keyboard to display the help. It will update with th eappropriate help information for whatever is currently under the mouse pointer.
I was always annoyed that if you wanted to see the "Click here for more help" that by the time your mouse pointer got to the context help box, it invariably rolled over something, changing the contents of the box! Sometimes the detailed help that you need is available by right-clicking and selecting "Help" from the pop-up menu, but what if it isn't? I solved that by right-clicking to bring up the pop-up menu. Leave it open. That takes the mouse focus off of LabVIEW, allowing you to move the mouse to the context box unmolested so you can click on the link...
You know you can lock the help for the one you have kept your mouse pointer focused. So until you release the lock the help will be showing the item you selected until you close that vi.
Interesting. Now that you mention it, that may have been one of the first things we learned in what was called BASICS I and II way back when...
P@Anand wrote:
@billko wrote:
I was always annoyed that if you wanted to see the "Click here for more help" that by the time your mouse pointer got to the context help box, it invariably rolled over something, changing the contents of the box! Sometimes the detailed help that you need is available by right-clicking and selecting "Help" from the pop-up menu, but what if it isn't? I solved that by right-clicking to bring up the pop-up menu. Leave it open. That takes the mouse focus off of LabVIEW, allowing you to move the mouse to the context box unmolested so you can click on the link...You know you can lock the help for the one you have kept your mouse pointer focused. So until you release the lock the help will be showing the item you selected until you close that vi.
Interesting. Now that you mention it, that may have been one of the first things we learned in what was called BASICS I and II way back when...
For your information I haven't gone thorugh the materials. Its glad that you already know and sorry to point that out. I wonder why you annoyed.
It's because i *forgot* about it until you reminded me, and don't be sorry because now that you reminded me, I can place (back) into my bag of tricks. 🙂
nkrajoo wrote:1. I notice the wire is always in GREEN color. Is there a feature in Labview which can change the wire color in the block diagram for e.g. RED if a given condition is met?
2. Is there a relay function (e.g. like a contactor) with auxillary contacts i.e. when operated it will close or open the associated contacts?
You still seem stuck at looking at the LabVIEW diagram as a circuit simulator, it is not! The diagram is the graphical code of a program designed to be operated from the front panel.
(1) A green wire is a boolean and the value is typically not know at compile time. Why should the code change during running? You can place an LED indicator on the front panel to indicate the current state of that wire to the user.
If you want to see the value of a wire during debugging, you can place a probe on it.
(2) The boolean palette has a rich set of functions that allow you to change states as a function of other boolean states.
