LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Intrument I/O Assistant don't work

I/O Assistant dosn't generate any output terminals,
after I have succesfully configured outputs (tokens).
I have also downloded Instrument_IO_Assistant.llb.
It has outputs allready, but when I open and close I/O-Assistant, the outputs are shown briefly as "Invalid Inputs" and then disappears!
I have seen the same problem on two different installations on diffrent machines.
The first time I try to use I/O-As. Labview says
it isn't installed properly, so I have installed the
IOAss. from drivers.
0 Kudos
Message 1 of 7
(3,451 Views)
I have run this on a few machines and not seen this beahvior. How exactly are you installing it the first time? You should be installing it from the Device Driver CD when you install LabVIEW. That is a separate CD from the LabVIEW 7.0 CD. Make sure you have selected it to be installed when you begin the LabVIEW installation and it should ask you for the Device Driver CD after LabVIEW has been installed. You typically get the "not installed properly" message when it was not installed in the first place. I hope this gets you started in the right direction.
J.R. Allen
0 Kudos
Message 2 of 7
(3,451 Views)
Maybe I was not clear about that I don't get
"not properly installed" any more.
Today I did a "Repair" Install on I/O Assistant
It didn't help!
I/O assistant still breaks 'Instrument_IO_Assistant.llb\Instrument IO Assistant.vi'
0 Kudos
Message 3 of 7
(3,451 Views)
Instead of a Repair install, do a full uninstall and then reinstall.
J.R. Allen
0 Kudos
Message 4 of 7
(3,451 Views)
Still error !
I did a complete uninstall of National Software
And a Install with default options ( including drivers).
I got no "not installed" message this time.
But it still removes all outputs when pressing OK
in I/O Assistant.
0 Kudos
Message 5 of 7
(3,451 Views)
Mighty odd! You might want to post something on the GPIB Discussion Forums, or actually contact NI's GPIB support.
J.R. Allen
0 Kudos
Message 6 of 7
(3,451 Views)
This is only a problem with some countries regional setting. If you change you regional setting to for example English US it should work just fine. This is a known issue and will be fixed with the next driver release.
0 Kudos
Message 7 of 7
(3,451 Views)