Instrument I/O Assistant with PXIe-1062Q

Hello,
I'm using a PXIe-1062Q with LabVIEW 2009 installed on it. In the Measurement & Automation Explorer the chassis is visible, as well as the two PXIe-6363 cards I built in. Even th self test of the 6363 works without any failures.
My Problem is, that after if I insert an Instrument I/O Assistant 1.01 in LabVIEW, and click on Select an instrument, the two PXIe-6363 don't appear in the list. Only Com1 and LTP1 is listed.
What shall I do? Thank you very much for your support!
Kind regards, Michael
Solved!
Go to Solution.

The 6363 is programmed with DAQmx functions. You would use the DAQ Assistant.

Similar Messages

PXI-4070 with PXIe-1062Q+NIe-8360+Labtop Why? Max not found instrument.

Dear all
my condition
PXI-4070 with PXIe-1062Q+NIe-8360+Labtop
Window XP SP3
NI-DMM 3.1
Why? Max not found instrument.
found PCI Device "PXI10:15::INSTR
see picture
How to fix this problem?
Best Regard,
Sermsak.
Attachments:
PXI-4070.jpg ‏42 KB

Hello,
Is it possible to take another picture of MAX? That one is very pixilated and I can't quite make out the configuration/error. Does the chassis show up? Every now and then MXI compatibility software is needed for certain BIOS versions so this may be the cause. Did the system work ever before?
Thanks,
Eric E.

Using Instrument I/O Assistant

trying to use Instrument I/O Assistant with my rs232 connection but i dosnt pick up a respone from my device can anyone help!!

Everything is working fine with the coms. i have check it in termial. all i want to do is have it sit there and wait for the message when in get one send it of and wait for the next time. I have got it working to some extent but if it dont get a swip in the timeout time it errors the code. see attached
http://forums.ni.com/attachments/ni/170/246328/1/labview%20photo1.JPG
Message Edited by Ajb181 on 05-08-2007 10:11 PM
Attachments:
labview photo1.JPG ‏1452 KB

PXIe 8262 streaming performance with HDD 8264 on a PXIe 1062Q chassis

Hello,
I have a PXIe 1062Q chassis, running Win XP, with one 8262 connected to an HD8264 and two PXIe 6537 installed, all the three board being on the express slots (3, 4 and 5). Running the benchmark application for testing the streaming speed (Win32FileIO) I get something like 100 MB/s with data chunks of about 4 MB, and around 140 MB/s with chunk of 64 M. How can improve these results toward the theoretical limit off 600 MB/s? Is there any software/driver trick to be applied?
And, in case, which is the best way to exploit the 8262 from C++ written code (using the NI libraries)? Is there anything similar to the Win32FileIO library? I tried using the RAID system from a c++ test program, and the performance seems very poor, while I would need, if not the 600 MB/s rate, at least something around 200 MB/s of continuous streaming.
Thanks in advance,
Piero.
Solved!
Go to Solution.

Hi Neil,
I actually have a 8130 controller, and in fact that was not the problem: I found the problem being the file-caching performed by Windows file system. If you use standard fstream calls from C source code you cannot bypass it, but by using Windows native call (CreateFile(...), WriteFile(...) APIs) and setting the flag for no data caching or buffering inside the call, I managed to get the full bandwith of 600 MBytes/s.
Anyway thanks for the quick reply!
Piero
I'm guessing you have a controller that only
supports x1 PCI Express. The PXIe-8130 is our highest-bandwidth
controller, with four x4 links going to the chassis. In the case of
the 1062, each of slots 3, 4 and 5 get a dedicated link from the
controller. x1 links max out at about 200 MB/s and x4 links max out at
800 MB/s.
So your first step is to use an embedded
controller or use MXI Express x4 instead of x1 back to a host
computer. While the PXIe-8130 is the best for high-bandwidth data
transfers, the PXIe-8106 should also be sufficient for your needs.
If
you want to stream data to disk from a PXIe-6537, it is already built
into DAQmx. You simply specify a file name, and the data goes to
disk. If you want to stream *from* disk, you'll have to do that on
your own. Here is a C/CVI example for streaming digitizers to disk
using a C API and the Windows File I/O functions.
Neil
Principal Engineer
National Instruments

Instrument I/O Assistant Task with Device Driver

Hello All,
I got some messag pop-up hint while using Tools»Create Instrument I/O Task in Labwindow/CVI.
=> "The feature requires the Instrument I/O Assistant.
=> Please install the Instrument I/O Assistant from the NI Device Drivers CD..
I want to practive to create Instrument I/O Task.
Is there any download entry on NI's web site for this?
Much thanks,
nonomiya

Hi Nonomiya,
You simply need to install the Instrument I/O assistant from the device
driver CD that ships with CVI. It should allow you to use these tasks.
As far as something that will act like the assistant and let you create
those tasks in CVI without actually installing the Instrument I/O
Assistant from the device driver CD, there's not much available.
Hope this is helpful,
Regards,
Matt S.
LabVIEW Integration Engineer with experience in LabVIEW Real-Time, LabVIEW FPGA, DAQ, Machine Vision, as well as C/C++. CLAD, working on CLD and CLA.

GPIB vi created with Instrument I/O assistant not timing out

I am new to Labview and I am trying to write a
program to control a HiPot tester via GPIB. This HiPot tester is used
on several other projects, so its GPIB address can vary. I want to use
Labview to scan for this device on the bus and then configure it.
I used the Instrument I/O Assistant to create a subVI that can query
the device for its manufacturer and model information. In this VI I
created some connectors that allow an outside program to input the bus
and device number. These numbers are formatted into a string and then
used to send commands to the GPIB device.
If I use this vi and specify the correct bus and device IDs for the
hipot tester, I get back the expected data. However if I send in the
wrong device ID (or wrong bus), the program hangs.
The Instrument I/O Assistant creates a timeout value of 2000 msec for
the operations. The *RST and *IDN? commands are sent first and then the
VI performs read operations to fill 128 bytes. So I figure that the
longest this should take to timeout is 2000*130 msec = 4.3 minutes. But
10 minutes later the VI is still running.
Why does this operation not timeout if the device and bus IDs on GPIB are not correct?
Brian Rose

Hi Brian
the first problem would appear to be that you send a reset command. But you only give the instrument
100ms to reset/reboot before your query its identify. If you have the instrument manual check to see actual timing
of bus etc.
As a rule of thumb I wait 300ms - If you run NI spy you will be able to see exactly when processes occur.
Add a sequence frame between reset command and id command.Place a
wait icon in the frame with a control on the input time so that you can
adjust time from front panel.
Initially set time to 400msand see what NI spy reveals.
Go for it
chow xseadog
Message Edited by xseadog on 09-10-2005 01:47 AM
Attachments:
wait.PNG ‏11 KB

Can I use the instrument I/O assistant express vi to communicate with a USB connected instrument ?

Can I use the instrument I/O assistant express vi to communicate with a USB connected instrument ? My PC is running Windows 2000 et Labview7 express.
where can I get information or examples on the assistant and USB communication ?

Yes you can - the Instrument I/O Assistant communicates with message-based instruments through VISA. VISA 3.0 supports USB instruments and VISA 3.0 is the version of VISA that installs with the Assistant.

Help with Instrument I/O Assistant

I am trying to control an Instrument with 'Instrument I/O Assistant. The control commands that the instrument expects are a ASCII character immediatly followed by a 'nul' character.
If the instrument does not see the null character then it will not run the command. Is there a way of entering a 'null' character as ACSII?
Also with 'Instrument I/O Assistant, What is the termination character \n? What do the termination characters do?

Unless there have been changes to the assistant in LabVIEW 8.x, you can't use it to send a NULL character. The termination character input is where you tell the assistant to append a specific control character at the end of each command and what character will terminate a read. The only options are \r (Carriage Return), \n (Line Feed), or \t (Tab). You need \00 which is the same as hex 00 and is the ASCII NULL character. You can create an assistant task and then convert to a regular subVI or just use the lower level VISA Write in the first place. There is a couple of shipping examples for serial communication. One has the front panel string control set for '\' Codes Display which does allow you to enter \00. The other sets the termination character with a VISA property node.

I want to communicate a RS485/2-wire device through COM1. I tried Instrument I/O Assistance to write to COM1(hex string with or without end bye:0D0A), something happened on the bus, but is not defirrential signal, and device didn't recognised them.

I am new to LabView, so please bear with me...
I tried to communicate with an RS485/2-wire device through COM1. I used Instrument I/O Assistant (and Advanced/Basic Serial Write and Read examples) to write command (HEX string) to COM1,
tried writing HEX strings with and withour end bye (is 0D0A the correct end signal for HEX string?). Both didn't get device's responce. Looks like the device didn't recognize the command.
I monitored the transmitted signals on the bus, they were not differential as supposed to be.....
What is the possible reason to cause this? Please help...
The hardware connection is OK, because I am able to communicate with the device through COM1 (with the same command) using different software application.

How are you sending the hex? Is your string control set for hex display or normal? If it's set for normal, then if you send something like 'AD', then you aer sending the ASCII characters 'A' and 'D' and that's not the same thing. I don't believe the I/O assistant can send hex but you can modify the basic serial write and read to do so. Just right click on the string control and select 'Hex Display'. You can also enter the data in a numeric control (set for dex display) and use a type cast or an array of U8's and use the Byte Array to String function. Hex data usually doesn't use any kind of termination characters such as CR/LF.
If communication is working with another app, then as you said, the hardware is okay and it's not a problem with differential signaling.

ADLINK PXIe-3985 Controller - NI PXIe-1062Q Chassis Compatibility

Hello forum members!
we recently purchased a PXIe-3985 ADLINK PXIe Embedded controller to be installed in a NI PXIe-1062Q PXIe chassis. In our system is also present a NI PXIe-6672 Timing Module, installed in the chassis timing slot (4). Windows 7 installation, NI MAX toolsuite and NI PXIe-6672 Timing Module driver installation worked fine, but we discovered that the CPU is not able to recognize the TIMING SLOT. We cannot generate any PXI STAR signal with our NI PXIe-6672 Timing Module because it appears that the TIMING SLOT is recognized as normal peripheral slot. The PXI trigger lines and clocks are working well and usable, but not the PXI STAR signals.
I also tried to install the PXIe Chassis in the NIMAX toolsuite as explained in the PXIPLATFORM _50-17049-100_200.pdf document from ADLINK.
basically in the NIMAX device and interface tab I right click and try to add the pxie chassis.
First it is not understandable how can I find the bus identifier root of the chassis. There is a PXI bus tree, but no evidence of the PXI bus related to the chassis.
Furthermore even if I select one PXI bus, the NI PXIe-1062Q PXIe chassis is not listed and trying to load the corresponding .ini file from C://programs/nationl instruments/PXI/PXIe Chassis/ returns the error “Could not import Chassis information. Error Code 0xFFFB380E”
is the ini file working at all for my PXIe chassis? is there another procedure that I must follow to have my timing controller working or the chassis installed?
We definitely need this capability to test our equipment and I would like to know if there are known incompatibility issues between these three devices:
PXIe-3985 ADLINK PXIe Embedded controller
NI PXIe-1062Q PXIe chassis
NI PXIe-6672 Timing Module
And in case if there is an update or workaround which solves the issue.
The system has Win7 32bit installed.
Many thanks to every answering user

Hi emanuele83,
which version of PXI Platform Service do you use?
Can you please upgrade to a current version?
Here is a download link:
PXI Platform Services 14.1 - National Instruments
http://www.ni.com/download/pxi-platform-services-14.1/5230/en/
This may solve the issue.
Best regards,
Andi

How do I program Instrument I/O Assistant to read a variable in the input string?

How do I program the Instrument I/O Assistant to read a variable in the input string? I can manually type in the string using the Instrument I/O Assistant using the "Write" or "Query" tools but I do not know how to send a variable input to the Instrument I/O Assistant so that variable can be used inside the "Write" string. For example, I have a power supply whose current I want to set to X Amps. I can type the command "PC10" to program the current to 10 Amps, however I want to be able to program it at any arbitrary current. How do I feed the value X into the code for this purpose?

You can't. The assistant was designed to be a quick and dirty way to do some basic communication with an instrument. You can turn it into a VI (right click and select Open Front Panel) and modify it so that your write string is an input to the VI or use it as a template and create your own code with VISA Read and Write primatives.

How to send multiple commands throught the Instrument I/O Assistant

I am using the Instrument I/O Assistant to set up an instrument driver. I am only using two rs 232 commands. The way I have the Instrument I/O Assistant setup is: first I have a default instrument setup step then I use a write step with the first command, then I read and parse, then I do a write command again with the second command and finally I read and parse again. All of this works fine inside the window but when I run it in my program only the first command's response it outputed . The second command's response is not outputted it just sends a null. Can the Instrument I/O Assistant only handle one read and write, or is my logic wrong?
Thanks for your help
Ian

Hi Ian,
You should be able to perform multiple reads/writes with the Instrument IO Assistant. What termination character are you using? I have seen cases where different termination results in different parsing, which may explain why you're only receiving a null character on your second read. Thanks!
Regards,
Anna M.
National Instruments

Instrument I/O Assistant Help - Parsing Errors

Hello All -
I am having trouble working with a TSI DustTrak DRX - which does not have its own driver so I had to make one. At this point, all I want to do is send a command to the instrument and get an indicator to repeat what the output is. So far no luck.
1) I think my driver works. The instrument is connected via ethernet. The instrument has a static IP. In MAX when I look under "Network -Devices" it appears there. "Validate" results in a successful connection. If I click on "Open VISA Test Panel/Input/Output" I am able to enter commands (e.g., rdmn\r returns the instrument number) and "Query" and the correct answer comes up. It should be noted that the number of bytes returned for different commands are different, and also that the measurement data is always of variable length, so I often get the "Timeout expired before operation completed" error. For a simple read instrument number command, the number of bytes is predictable, but for the measurement data, it is not, unfortunately.
2) When I put an "Instrument I/O assistant" on the block diagram of a new VI, and add a "Query and Parse" step with the same command (rdmn - no \r this time), I again get the expected value (or when I query the measurement, rmmeas, I get the expected output string). Again, it should be noted I get the "Timeout expired before operation completed. VISA Status code : bfff0015" error. Once I close then reopen the Instrument I/O Assistant configuration window (though not before) I can parse the data, and the token appears as a potential output of the VI. Here I can declare the output as either String or Number.
a) If I declare the output as a string and create a string idicator, an empty string is returned.
b) If I declare the output as a number (it is "8533", so this should be OK), I get the following error (even without creating an indicator before running): "Error 1 occurred at Scan From String (arg 1) in Untitled 5:Instance:0->Untitled 5 Possible reason(s): LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @." I know from MAX that the returned value is actuall 8 bytes: \r\n8533\r\n . So, there are no unallowed characters here. And there are no paths involved - no read/write.
Some other info:
1) If I send start or stop commands to the instrument in MAX or the Instrument IO Assistant, I can get the instrument to turn on/off as it should, so I'm clearly comunicating to the instrument correctly.
2) I get the same behavior if I parse the returned measurement string - \r\n385,0.013,0.014,0.015,0.020,0.035,\r\n from MAX - as a set of numbers (that is, with "Error 1 occurred at Scan From String (arg 1) in Untitled 5:Instance:0->Untitled 5 Possible reason(s): LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.")
Any help would be appreciated!
Thanks.

Hi James - Thank you very much. I actually found the problem and was able to fix by changing how the output text was parsed - the \r\n in front and back was confusing it - and making sure that I flushed the read buffer after reading, just in case. I also had to modify so that the first character was read and discarded before reading (and using) the rest of the output string.
Now for a rookie question: I've got it set up as a working VI now - how do I declare which variables are inputs and outputs when I put it in another vi?
Thanks.

Instrument I/O Assistant (sending command from labview to arduino)

Hi,
I am a beginner in Labview. I would like to control the intensity of AC loads using labview. In this case, i would prefer to use instrument I/O assistant. The instrument I/O assistant in labview will have to send a command to Arduino. The intensity will be controlling by using slider in labview. How to write the vi for this example? Please advice.

feliciacpw92 wrote:
Hi,
I am a beginner in Labview. I would like to control the intensity of AC loads using labview. In this case, i would prefer to use instrument I/O assistant. The instrument I/O assistant in labview will have to send a command to Arduino. The intensity will be controlling by using slider in labview. How to write the vi for this example? Please advice.
In the thread for your other post, you were told that LabVIEW installs by default example programs on how to use LabVIEW with serial port.
Have you bothered looking at that?
You need to do some work on your own.

Instrument I/O Assistant and Graphing

Does anyone know how to use data taken from an Instrument I/O Assistant Input and put it into the y values of a graph?? I'm having issues with this because it returns values like "v 0" and "v 256" but I need just the number value to get a graph to work. Any advice would be very much appreciated. Thanks in advance!
Solved!
Go to Solution.

Hi Rach_77,
In order to get rid of the "v ", you can use the String Subset Function and set the offset to 2. This will take away the first two values and just give you the number. From there, you will just have to convert the value to whatever type you would like. I hope this helps!
Kim W.
Applications Engineer
National Instruments

Instrument I/O Assistant with PXIe-1062Q

Similar Messages

Maybe you are looking for