The VXI-1394/G front panel GPIB connector is supported under WindowsNT4.

Does it been supproted under Windows2000?

IEEE-1394 is not native to Windows NT. Because of this, there are a few 3rd party 1394 device drivers for Windows NT out there. However, there are frequently issues that arise because Windows NT does not support 1394. The NI-VXI driver included a 3rd party PCI-1394 driver to allow the VXI-1394 to be used under Windows NT.
Currently, the only NI-488.2 driver that supports the GPIB port on the VXI-1394/G is for Windows NT. R&D has considered making the investment of developing a new version of NI-488.2 that will support Windows 2000. However, I do not believe a decision has been made at this time. Since a PC is already a part of your system solution, we recommend using a PCI-GPIB card installed in the PC. There are also other GPIB so
lutions, such as the GPIB-ENET and GPIB-USB.
Julianna Forrest
Applications Engineer
National Instruments
www.ni.com/ask

Similar Messages

Front panel audio connectors

I have an msi 915p combo-fr mainboard and i am trying to connect it to my front panel audio connectors?do someone knows how to plug these cables?

Connect the front audio cable to this connector
Cheers

Problem with front panel USB connector

Motherboard: MS-6750
I have a problem with my front panel USB connector JUSB2 not working.
I have checked the connection to be sure that it is oriented correctly.
I also made sure that it was enabled in the BIOS.
Still no luck. There is not any voltage on this either.
I see a jumper or pin labeled JGS1 just below the JDLED1...do not know what this is and cannot find it in the manual.
Any ideas on what this is and how I might trouble shoot the USB connector?

Which 6570 MB do you have, if its the K7N2 Delta 2 Platinum and came with the Dled bracket try plugging that into that port on the mainboard and see if those usb ports work as it could be the usb hub itself not working on the front. Hope this helps Dok

~~KT4V~~ Front Panel Pin Connectors (USB + Audio)

Hello All
I have a few questions on setting up the front panel pin connectors from my case to my new KT4V board.
First question: USB
My case is usb 2.0 (Raidmax Scorpio)it has two seperate pin connectors a 4 pin and a 4 pin + GND pin on the second wire. I assume I put the GND in the JUSB1 #10 slot which is marked (USBOC) in my manual. Is this correct?
Second Question: Front Audio (Microphone, Headphones)
The front panel Audio Connector: JAUD1
The four pin connectors that my case has labeled is:
1. MIC DATA
2. MIC GND
3. EAR R
4. EAR L
I am pretty sure MIC DATA goes in pin #1, and MIC GND goes in pin #2. As far as both EAR pins, I am not sure and would appreciate some help in this.
Thanks in advance.
ncarme :D

I know, I have the book in front of me. But the names on the board and my case are different. Thanks for the info on the usb, how about the audio inputs.
Thanks.
ncarme

How do I get the Label for a Front Panel Control to appear in the Block Diagram but not on the Front Panel?

How do I get the Label for a Front Panel Control to appear in the Block Diagram but not on the Front Panel? On the Front Panel I am making a complex control that consists of a Slider and a Numerical Input box. Both Controls display the same information and either can be used for Input. When one changs, the other is made to display the same value.
But I only want the Slider to display the Label on the Front Panel, to avoid confusion. On the Block Diagram however, I want both controls to display their Labels so that I know what they are. How do I display the Label for a Control on the Block diagram, but not display its Label on the Front Panel?

No. The Label Visible property is separate for the front panel control label and the block diagram terminal label.
How did you start out with the block diagram's label not being visible? Whenever I drop a control or indicator, the label is always visible on both the FP and BD by default. Maybe there is a LabVIEW option that causes new controls/indicators not to have their labels visible by default, but I have yet to find it. I don't think an item should ever be dropped without the label visible, good LabVIEW coding practice demands that the labels for control terminals on the block diagram be visible so that you know what control or indicator a wire is going to.
That being said, I have seen a lot of VI's posted where the label for the terminal on the BD is not shown (against good programming practice.) I've gone to the BD and right clicked to show the label. Sometimes, the people have an empty label (which will turn off the visibility for both the FP and BD) and I'm forced to add some text of my own into the label so I can figure out what their code is doing. When I add some text to the label, at that time, I find both the BD and FP labels become visible.
Are you dealing with controls that have empty labels to start?
Good programming practices:
1. Always have a name for all of your controls, never use and empty label by deleting the text in the label.
2. Make the labels unique. For example, don't have two controls both called Stop. How do you know quickly know which terminal relates to which control?
3. Always show the labels on the block diagram, so you know the function of a control's terminal. If you want to hide the label on the FP, that's okay.
4. If you want a different label to appear on the FP than whatever you actually called the control, then use the caption. You can hide the label and show the caption. This is useful if you need to programmatically change what the "label" is on the front panel such if you are making an application that needs to change its user interface such as for a foreign language.

How can I fix the section of a front panel?

Hi all
My problem is that way that I'm not able to adjust the section of the front panel which should be displayed very time exactly like before.
So every time I modify my front panel it look slightly different afterward when it's running.
Therefore I'm wondering if there's any possibility to fix the section of a front panel which should be displayed while the VI is running.
Every suggestions are welcome
Ben
Stay Hungry, Stay Foolish
Solved!
Go to Solution.

Hi Ben,
This is a common issue that NI LabVIEW does not address.
The good news is that OpenG provides a function to do just what you need.
See this article: Resize Front Panel to largest decoration
The way to get the OpenG functions is to use the JKI VI Package Manager (VIPM).
In addition to the OpenG functions there are several other community provided tools avaliable through VIPM.
For a quick test, I'm attaching these files (LV version 2010 sp1):
Fit VI window to Largest Dec__ogtk.vi and the required sub vi Current VIs Parents Ref__ogtk.vi.
You should really use VIPM to get the full OpenG library - there are many gems in there.
steve
Help the forum when you get help. Click the "Solution?" icon on the reply that answers your
question. Give "Kudos" to replies that help.
Attachments:
Fit VI window to Largest Dec__ogtk.vi ‏29 KB
Current VIs Parents Ref__ogtk.vi ‏9 KB

MS6117 Front Panel Pin Connectors

Can anyone help me? I have a old MS6117 MOBO and I need to connect the front panel connectors. I looked for a manual but could not find one. I know where the pins are located in the board but no idea which are the pwr switch pins etc. (The MOBO has no markings as to what pins to use for what) . Thankyou

Hello! Welcome to the forum!
The Internet got its advantages:
http://www.flexbeta.net/forums/lofiversion/index.php/t3822.html

How can I make sure the text size on front panel will be adjusted by itself from PC to PC?

In my VIs under VI Properties -- Window Size, I checked the two boxes:
--Maintain proportions of window for different monitor resolutions
--Scale all objects on front panel as the window resizes
It seems that it worked for everything on front panel except the pure text wording that I put there for instruction purpose. The size of those text stuff didn't get changed proportionally after my application was built and run on different machines so some of them got cut off and looked messy.
Does anyone know how to fix this problem?
Thanks very much!

Hi Andrew,
Thank you for looking at my problem!
Both my development system and test system are Window XP. The font size are all set to Normal. What other details do you need to know?
The text on front panel shows well on my development machine. But when the .exe runs on my test machine, the text size was not adjusted by itself so the text body got cut off.
I found a way to "fix" this problem: I had to drag the text box down and right so there is enough magin between the text body and the box on the right and at the bottom. I had to try it a few times until it finally shows well on my test machine. However, with those magins, it doesn't look nice on my development machine anymore. Also, I only tried on one test machine, if it looks good on one test machine, will it look good on all the other machines? Eventually my app is going to run on Window 7. I'll have to test that out and find out if it's still going to be a problem. Anyway, I don't feel this is the right way to do it. I hope someone knows what I'm talking about and have a soluction to it.
Thanks very much!

Edit Disable Panel Grid Alignment does not affect the Positioning of Front Panel Labels

In LabVIEW 2010, when I choose Edit>> Disable Panel Grid Alignment the positioning of Front Panel objects gets much finer so that I can make small adjustments. Put it does not seem to affect the positioning of front panel object labels. These object labels still move in very coarse increments and do not allow me to position them carefully.
How do I turn off the Grid Panel alignment for Front Panel Labels?

The positioning of labels you encounter has not so much to do with any grid, but with the fact that for labels, LabVIEW attempts to snap them to one of the control corners if you get close enough to the owning control. Outside of a certain range of the owning control you should be able to place them easily on any pixel. The snap behaviour of owned objects is not configured through the panel grid option. I'm not aware of an option to disable this behaviour, but usually find it rather handy instead of annoying. If it happens to not be exactly as desired, I adjust with the label selected and using the cursor keys.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Publishing VI's on the Internet without open front panels

I'm using LabVIEW 6.02 and are publishing VI's on the Internet. I'm wondering if it is possible to publish VI's without having the front panels open when you are running the program?Or do they have to be open to be in memory and to be able to get updated front panels?
(I use the .snap command so it is possible to refresh and get updated VI panels.)
I also wondering if the only difference between .snap and .monitor command is that you can use the refresh command with monitor so the labVIEW display will automatic updated itself. This is not possible with the .snap command?
Thanksregards Anne

I've never tried to exactly what you are talking about but a similar issue comes up when printing. A front panel normally won't update unless it's open. The way to insure that it does is to have at least one property node on the routine's block diagram. When LV sees the property node, it goes ahead and updates the front panel even when it's closed.
Hope this helps...
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

What can affect the size of a front panel object between versions of Windows?

Greetings, all!
I have a client that wants to use a piece of LabVIEW code on Windows XP, Vista, and 7. The application was originally written to run on XP machines, so everything looks OK there. However, on Vista or 7, certain front panel objects appear larger than they do on the XP machine (in one example, all of the string fields in an array of strings are taller). Other objects (such as a text label) appear smaller.
The machines in question all appear to have comparable DPI settings, and monitor resolution does not seem to be a factor. The application uses Application Font in various sizes in the cases of interest. Can anyone suggest some other things we can check?
Thanks!

This issue is coming up more and more lately. Particularly as people move to Win7 machines. I've seen differences between my home Vista machine and my work XP machine.
It comes down to the system fonts used by the different OS's. XP's basic font is Tahoma. Vista uses Segoe. I believe Win7 is the same as Vista, but I'm not sure. The fonts appear similar, but one font or the other is slightly larger. So any features that are based on a font size will change. This includes the sizing of labels. Text within local, shared, global variables, and references. Enough that it can cause wires to move a few pixels on a BD, and objects that are aligned on one system to look slightly misaligned on another.
I think that if you set the fonts you use to a specific font, rather than Application font (which is taken from one of the current Windows font settings, you will avoid the issue. The other possibility is to define which font is used for the application font within your LabVIEW.ini. (Or the application's .ini file if it is built into an .exe.)
Do some searching on the forums for application font, system font, dialog font, windows versions. You'll find quite a few threads where people had different variations of this problem.

Example on how to use the NI "saving a front panel img to file" on a prog.

New to the labview program - I'm trying to save the front panel of the displayed output to file. I downloaded "Panel_Image_to_File.zip" from the NI site. But I'm having problem using the code to our program so as to save the image as a jpeg.
A simple example on how to use the code or any other code that will be able to save the front panel to a specified folder will be great.

All you should need is an invoke node of VI class and the the method Get Panel Image. Wire the Image Data output to the Write JPEG File on the Graphics & Sound>Graphics Formats palette. The Invoke Node is on the application Control palette. When it's on the diagram, right click and select Class>VI Server>VI. Right click on it again and select Methods>Get Panel Image.
Attachments:
Save to jpg.jpg ‏10 KB

Front panel led connectors cables problem

Anyone knows how to connect the cables for the front panel power and hdd switches and leds to the jumpers on the board? The cables have wordings printed on one side of the cables (power led.. hdd led.. etc).. i'm not sure which side should be facing up on the board ... is it the side with the wordings facing up or the opposite side without the printed wordings ? i'm worried that i may end up short circuiting the board if i connec them the wrong way round ... thanks

The are just switches, so there is no polarity to worry about. the led's are polarity sensitive, so If they don't work, just reverse the connection; no damage will occur.

About Front Panel Audio Connector: JAUD1

In the User Manual for the K9N6PGM2 nVIDIA chipset mainboard, you are advised that pins 5, 6, 9 & 10 must be jumpered if you do not want to use the front panel audio but you want to use the back panel Line-Out instead, otherwise it won't function.
My question is (sorry if this is a silly question, only I'm new to building PC's ), if you want to use both the front and back panel audio slots, as I do for my current system that I want to replace, will the Line-Out at the back work automatically (i.e. connecting up the front panel audio is enough), or do you have to set something else in addition.

Of course, silly me Thanks for clearing that up

What is the maximun number of front panel objects in LabVIEW 7

I need to know what is the maximun number of indicators in a panel control, LabVIEW 7.0

According to the post here the 555 limit in LabVIEW 6.1 is no longer in 7.0 but I don't know if there's a much higher limit or if you limited only by the amount of memory in the computer. How many do you have? By using clusters and arrays, you should be able to dramtically reduce the number. You might also want to think about moving seldom used indicators to subVIs that pop-up on demand.

The VXI-1394/G front panel GPIB connector is supported under WindowsNT4.

Similar Messages

Maybe you are looking for