PXI-6255 not identified in MAX as DAQmx

We recently purchased a PXI-8108 controller for use as a spare and I'm having difficulty getting it to play well with our existing hardware and software. The controller we have been using is an older PXI-8106.
The new controller has Windows 7 where the old had XP, so I had to use more recent versions of PXI Platform Services and MAX, as well as DAQmx. The versions I've installed are: PXI Platform Services 3.0.4, MAX 5.3.1, DAQmx 9.2.2. I can't use more recent version of DAQmx because our we are using LabVIEW 8.5.1 and anything more recent doesn't support that.
The 6255 is showing up in the device manager under Windows, and the properties show that it is using the same hardware driver (nixsrkw.sys, rev. 1.13.0f4) as we use on the old controller. The 6255 also shows up in MAX, with a device identifier of PXI13::15:INSTR, but not listed as a DAQmx device. So, when I import the MAX settings file, the defined tasks won't run.
I haven't found any postings in the forum that quite match this scenario. Anyone have any ideas?
Thanks,
Mike

Mike,
Firstly, I want to let you know that you will have problems using LabVIEW 8.5 with Windows 7. The oldest version of LabVIEW supported in Win 7 is LabVIEW 2009 SP1:
http://digital.ni.com/public.nsf/allkb/B972242574D4BB99862575A7007520CB
About seeing your device in MAX, can you post a screenshot of what it looks like?
Jon F.
Applications Engineer
National Instruments

Similar Messages

PXI 7314 not seen in MAX

I also use PXI 7314 module. But module not seen in MAX.
The module seen in Device Manager but not seen in MAX.
In device manager it seen National Instrument Motion Controller - PXI-7314
but not seen in MAX.

Please follow a single thread, if you start multiple threads then the other users having similar problem may not be able to get proper solution.
As already asked did you install the driver properly, you need to have the LabVIEW RT and device drivers installed to have the hardware availabke in MAX.
The best solution is the one you find it by yourself

PXI 8252 not seen in MAX

I have PXI 8252 1394 Host Adapter in my PXI 1000B chassis. PXI is controlled using MXI-3 fiber optical communication.
NI PXI 8252 is not seen in MAX.
I want to program the 8252 using LabVIEW but it is not seen in MAX.
Thanking You
Kiran Patel

Are you able to see the PXI chassis in MAX?
The best solution is the one you find it by yourself

Goepel PXI-3220 not visible in MAX

I have installed 2 goepel pxi-3220 cards into a NI PXI-chassis. But there arent visible in MAX. The drivers in the windows device manager are present and working fine. I would like to have these two cards visible in MAX. Does anyone have any experience with these analogue output cards?

Hello,
Only devices that were produced using the VISA driver development Wizard are viewable in MAX. If the 3rd party manufacturer did not use our driver wizard, then the device will not show up in MAX. If that is the case, the card must come with a programming API and also some sort of configuration program. It sounds as though the drivers and are installed correctly since you see them in the device manager.
Regards,
Andrew M
National Instruments

Mightex camera not identified by max or Imaq usb enumerate camera vi

Hi all,
I am using Mightex S-Series Ultra-Compact USB2.0 camera, I am finding it difficult to identify the camera in MAX or with IMAQ usb enumerate camera vi, I do have loaded the drivers but still couldnt get the camera working , please let me know if there is anything else I need to upload.
Thanks,
Ankit Gupta

Hi AnkitG,
Sorry to hear that you are having problems with your camera. We have recently seen several other instances of Mightex's cameras causing issues when trying to interface with it through IMAQdx, and have been in touch with Mightex regarding these issues. We suspect that the issues all come from differences in the way NI and Mightex handle DirectShow compliance. I'll make sure to communicate this issue to them as well, and I'll let you know what we find.

PXI - DAQmx tasks will not export to MAX 5.4

I am in the process of upgrading a PXI 1050 with an 8176 to an MXI bridge. The latest headache is that the CVI program had several DAQmx (tasks) defined in MAX 3.1.1 which will not export to MAX 5.4. I have been posting these additional questions on my original thread MXI not visible in MAX. I have many tasks for installed PXI cards. I was trying to make simple tasks just defining these cards to change the errors I receive in CVI. I do not have the option to define a task for some of these cards like the 4070 DMM. I did not generate the original CVI code. I am not sure what is defined the DAQmx. Can someone provide some insight ? I have viewed the suggested videos and white paper links. They were instructive but of little help.

Unfortunately; no updates without dollars. While we all work for the same company, we must contract work between departments. There was no defect with the software as delivered. Old age crept in to the hardware. Any upgraded hardware, it turns out, requires updating of the software. The unit had operated reasonably well, until a couple years ago. An unfortunate selection of network security software caused massive headaches. The software chosen assumed a more advanced level of hardware. Mandatory installation on all network computers rendered these controller inoperable. Our local IT guys shaved down the install to minimal components but the controller lost all available ram to this software, NI-MAX requires 20 minutes to build it's database on reboot. The computer controllers struggle to function. They periodically get lost and require a reboot, causing 30 minutes or more to restart. This is driving a replacement. We decided that it would be more cost effective to move to a standard computer interface. With the MXI, we could have a much more friendly and versatile interface. The upgrade is with a different "color" of corporate money. There isn't enough funding to contract a software upgrade. It is feasible to complete the upgrade in house, once we can identify the players and their function. Second we need the necessary time and access to the equipment. I do not have the ability to expend too many extra hours at work. So it takes time. I have been able to piece together the following. In the development stage back in 2004 - 2005, the developers used both Traditional DAQ and DAQmx. They build tasks for the SCXI in CVI. They have toolboxes making calls to Traditional DAQ. Also at some point in time they must have used the option in 3.1.1 to Convert Traditional NI-DAQ(Legacy)Configuration to NI-DAQmx, which built all the extra DAQmx devices we see in the device tree in the MAX 3.1.1. So beyound the errors there appears to be a few red herrings, just for fun. So there is no tasks to convert from 3.1.1, everything is contained in the CVI code. I have to find a way to use the CVI debugger to lead me to the nested, buried code causing the errors, and simply correct them. Just for another layer of complexity, they are probably logic errors, not syntax errors, or updated code errors where the legacy code no longer functions with the updated drivers. Or, hey, it could be the beta version of NI-DAQ, because it is the only one working with Windows 7 (32).

PXI System does not appear in MAX 4.0

Hello,
My system comprises LabVIEW RT 7.0, target PXI-8176 controller in PXI-1000B chassis, PXI-6608, PXI-6711, NI-4472, PXI-6704, PXI-6527, PXI-8423/4, PXI-8422/4. This has been stable for two years. I recently solved an RS-485 2-wire mode configuration problem, using information in a discussion forum thread, by upgrading to NI-VISA 3.4.1 and NI-Serial 2.5.5. MAX 4.0 was installed as part of this process. Everything seemed to work fine. I instructed a distant customer to do the same, but they experienced some difficulty. To ensure we were working from the same starting point, I re-initialized my PXI system, using PXI Format Hard Drive Disk, version 7.0, from MAX 4.0. I configured TCP IP address, and re-installed the RT software on the PXI controller.
Next, I attempted to configure the PXI controller and chassis, in MAX, to update the pxisys.ini file, but the PXI System (Unidentified) does not appear under Remote System>>IP address>>Devices and Interfaces. Similarly for the serial ports. This worked before, but I cannot get this back. What is wrong?
Best regards,
RonC

Hello S. Bassett
The controller is definitely booting in RT mode -- I can still run my applications on the RT target. VISA seems configured properly also, I can make VISA calls without error in the application.
In fact, the RT system seems to work correctly, and I contemplated leaving it as it is. However, the fact that MAX does not recognize the PXI system makes me nervous, and I cannot do some of the things I may want to do, for example independently configure RS-485 port wire mode in MAX (the ports do not show up either). Traditional DAQ configuration in MAX works.
After your last post, I found a brief reference in MAX Help that indicated "PXI Services" had to be downloaded before the chassis could be configured. But there are no other mentions of what PXI Services is, what it does, or how to install them. PXI Services does not show up as RT Software in MAX. In the Windows Add/Remove Programs control panel in Windows, in the National Instruments software section, there are two apparently related entries:
- NI PXI Platform Services for LabVIEW Real-Time 1.5.1
- NI PXI Platform Services for Windows 1.5.1
But, I cannot get these to install on the RT target. Not knowing what was causing the problem, I uninstalled everything from National Instruments, deleted all folders, and reformatted the PXI platform. There was one problem during this process -- after uninstalling NI-Serial 2.5.5, it does not get removed from the Add/Remove programs control panel. There is still a registry key that the uninstaller did not remove -- presumably this is the problem.
I have rebuilt everything, but could not get NI-Serial to install -- the installer thinks there is a newer installed on the RT target (there isn't) and refuses to install NI-Serial 2.5.5. So right now, I cannot install NI-SERIAL (any version), or remove the 'existing' NI_SERIAL, because it isn't actually there, and there is no uninstaller.
Otherwise, everything seems to be back to where it was before I "upgraded" to NI-VISA 3.4.1. This was NI-VISA 3.0, LV RT 7.0, and MAX 3.0.2. I have not yet been able to install NI-Serial, so I cannot yet see if I have also restored my original problem -- the one that led me to have to upgrade NI-VISA and NI-SERIAL in the first place.
Most importantly, there is now a "PXI Services v1.1.2" installed on the RT target. I am quite sure the problem with MAX 4.0 not recognizing my PXI system has to do with the absence of this driver on the RT target.
Thanks again for your interest and help,
RonC

PXI-8532 DNET card is not detected in MAX

Hi all,
I'm using NI PXI-1031(4 slot PXI chassis). I have the following cards in the respective slots
Slot 1= PXI-8106 Controller
Slot 2= PXI-6259 card(AI)
Slot 3= PXI-6509 card(DI,DO)
Slot 4= PXI-8532 Card(DNET)
In MAX(Measurement & Automation Explorer), I was expecting all the above cards(PXI 6259, 6509 & 8532) to be detected under Devices and Interfaces. But only the AI and DIO cards are detected in MAX under Remote Systems>>PXI>>Devices and Interfaces.
PXI-6259 (PXI1 Slot2)
PXI-6509 (PXI1 Slot3)
The device net card, PXI-8532 is not detected in MAX. Does MAX shows/detects the DNET card?
In MAX, I selected Tools menu>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, I pressed OK. A message appears that no device is found.
Can any one help me how to detect the DNET card in MAX and do the DNET port configuration?
DNET driver version - 1.6.4
Thanks,
Raja
Solved!
Go to Solution.

Dirk,
Thanks for the reply. After updating the new driver, I am able to detect the DNET card PXI-8532 in MAX
New driver - NI-Industrial Communications for DeviceNet 2.1
But Im not able to configure the Device Net port. In MAX, I selected the menu option Tools>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, a message appears that no device interface is found.
By default, the DNET0 port is configured for the card in MAX. So I tried to communicate from LabVIEW using DNET0 port.
After installing Devicenet 2.1, an additional function palette has been added for DNET in LabVIEW.
Old DNET function palette - Instrument IO>>DNET
New DNET function palette - Industrial Communications
My original application was written with old function palette VIs which corresponds to DNET 1.6.4 version. In the download link that you shared has a description about the driver compatibility. The description says still the DNET card PXI-8532 is compatible with NI-DNET 1.x LabVIEW VIs.
With the old DNET VIs, I tried to establish communication with DNET interface port "DNET0". But it shows error while opening the interface.
Error Code ="-1074388957" - The Interface is invalid or unknown. Solution: Verify that the interface is assigned to a specific port within the Devices and Interfaces branch of the Measurement and Automation Explorer (MAX).
With the new DNET VIs(DNET 2.1.0), Im able to open the DNET interface successfully. But my original application was written in Old DNET VIs (DNET 1.6.4).
1. Do you know why the DNET 1.6.4 LabVIEW VIs are not working with PXI-8532 DNET card?
2. Can you help me how to configure DNET port in MAX for PXI-8532 DNET card?
Thanks,
Raja
LV 2009, Windows XP

PXI-1052 not detecting SCXI chassis

Full disclosure: I've submitted a support request on this too, but knowing that it may take some time to go through I thought I'd ping the discussion boards for any ideas people here might have as well.
I have a PXI-1052 PXI/SCXI combo chassis with a PXI-6289 card serving as the SCXI controller. Up to this point, the chassis has been controlled by a PXI-8105 embedded controller running WinXP. We are changing this. The PXI-8105 controller is being removed and instead we will use an MXI card (PXI-8360) to allow us to control the chassis via an external computer running Win7 32-bit.
With the chassis on and connected, using the Win7 computer I can see the PXI slots and the cards in them are correctly identified by model number. However, I cannot see the SCXI portion of the chassis, and when I try to manually add an SCXI chassis I am told that there is no DAQ device installed to serve as the SCXI controller. In addition, the PXI-GPIB card which is also installed is acting a little strangely. It allows me to scan for instruments, and it sees all of my GPIB instruments OK, but I don’t see a GPIB bus defined separately under Devices and Interfaces the way I did on the old controller—the instruments just show up listed under the PXI card.
I have read the Knowledgebase article on auto-detecting SCXI instruments, but it doesn’t seem to offer anything helpful. Everything works fine if I put the old controller back in and use it again, so this isn’t an issue of a bad card/chassis or the wrong card or a blown fuse or SCXI power not being on/set correctly or the DAQ being in the wrong slot. (The ONLY hardware difference is the controller being replaced by MXI; everything else is exactly the same.) All NI software on the Win7 machine is installed and up-to-date, and I even reinstalled everything just to make sure I hadn’t gotten a bad install. It seems to me like it must be either a driver or a configuration issue, but I’ve combed through the Windows Device Manager and the settings for all cards involved and can’t find any differences.
Screen shots attached. Any ideas?
Solved!
Go to Solution.
Attachments:
Win7.png ‏109 KB
winXP.PNG ‏73 KB

Hello Sara_J,
I'm going to post to the forums with my suggestions from my email so that if we find the answer it will be available to the community as well.
As long as the 6289 is showing up incorrectly you're not going to be able to use the SCXI side of the chassis. The problem looks like your 6289 is not being associated as a DAQmx device. The alias it has in MAX is showing it as a generic VISA device. You'll have to manually associate the 6289 in device driver. Normally it would show up under Data Acquisition Devices with the NI logo in Device Manager. Since its not showing up correctly it may be located elsewhere, most likely under a PCI Standard PCI-to-PCI bridge (this is how the MXI card looks in Device Manger).
Once you find it, right click and select Update Driver Software...>>Browse my computer for driver software>>Let me pick from a list of device drivers on my computer. You should then be able to pick the appropriate driver from the list.
If this does not fix the issue then I believe there may be a corruption in your installation of DAQmx. You can download the newest version (9.9) here: http://www.ni.com/download/ni-daqmx-9.9/4707/en/ .
Jonathan L.
Applications Engineer
National Instruments

PXIe-1073 not detected

I'm trying to install a PXIe-1073 chassis on a new Dell system running Windows 7 x64. I have the latest version of Labview, NI-DAQmx, etc. The PCI express controller shows as properly installed in the Device Manager ("PCI standard PCI-to-PCI bridge"). The chassis and installed DAQ card are not detected in MAX.
I am actually transferring this system from an older computer. I recall having exactly the same problem before, and I'm fairly certain I solved it by installing the "MXI-Express BIOS Compatability Software". There was never any way to actually identify the "PXI System" as anything other than "External PC" even when it was working properly.
After installing the current version of the MXI-Express software, I rebooted and was able to load MAX briefly before Windows BSODed with an error involving "niraptrk.dll". This proceeded to occur every time I tried to load Windows. I was able to start in safe mode, but attempting to uninstall any NI software gave me an "error 1601". I was finally able to load the last known good configuration and uninstall the software.
When I checked MAX again, the chassis was still unrecognized, but there were multiple broken entries for the DAQ card installed in it, so I assume it was detected at some point. It looks like the MXI-Express software worked, but it's obviously unusable if it causes the computer to BSOD every time Windows starts. Why is the computer unable to recognize the chassis without it? What else can I do to solve the problem?

Hello Bob_mcbob,
After looking over this issue, I think we have a problem with the Windows installer on your machine. I have found a KnowledgeBase about the Error 1601 stating that this is a Microsoft Windows installer error and that the installer will need to be reinstalled. The Knowledgebase explains how to do this.
As for the BSOD, do you have any more information that it provided when this occurred like the address line, etc? Did you do something in MAX before it crashed?
Since accessing MAX now gives you a BSOD, I think it would be best to uninstall/reinstall the drivers to fix the issue. What cards do you have in this system?
Jim St
National Instruments
RF Product Support Engineer

Counter value jumps on occasion (PXI 6255)

I am using a PXI 8108 controller (Windows) with a PXI 6255 AI card. A pulse generator (1 KHz) is incrementing the hardware counter of that AI card in order to have an external reference clock, i. e. having a timestamp for each AI sample value.
I am reading 1000 AI values from several channels (together with 1000 counter values) via DAQmx blocks with a higher frequency than the external clock's 1 KHz (e.g. AI Rate 5 KHz-> reading every counter value approx. 5 times). Every now an then I am losing counter values, e. g. counter value 6789 is followed by 6823.
Shouldn't be the PXI card's counter buffer independant of Window's CPU load? Getting 1000 values from the card buffer, the jumps are even located in the middle of the 1000 values. Maybe there's a problem with atomicity while reading from the buffer, so that I get 500 values from the buffer, (pause), and 500 more values from a later point in time. Is this possible?
I am sure, I can not blame the digital pulse generator (from Hameg Instruments) for dropping pulses.
Attachments:
counter-daq.png ‏20 KB

Hello,
If the first scan only places 4 samples in the AI FIFO (2 less than the number of channels requested), then I would expect this loop to run forever in aiex1.cpp (I added some debugging prints to make it easier to see the channels that should be getting returned).
       while ( m < numberOfChannels )
        if(!board->AI_Status_1.readAI_FIFO_Empty_St())
            value = board->AI_FIFO_Data.readRegister ();
            aiPolynomialScaler (&value, &scaled, &scale);
            printf ("Channel %d: %e,\n", m, scaled);
            m++;
    printf("\tEnd of Sample %d\n", n);
How is the example able to proceed past this loop?
I have checked the code for FIFO flushes and resets between aiStartOnDemand (board); and when the FIFO gets read. I have also run the example with 6 channels, this time on Windows.
To proceed we would need these items:
1) We would need the exact output (with my added debug prints).
2) A complete dump of all registers accessed during the example.
Steven T.

PXI-6255 Channel Configuration

The documentation for the PXI-6255 is VERY unclear (to me) on configuration. I found the attached sample VI and modified it to test my new card. The VI runs to make the relay connections (without the ~), but when I add the "~" to disconect, the attached error results. The error refers to "channels" and I can find NO documentation on how to set up "channels" for this card. The documentation seems to freely switch syntac between channels and com1 for example? What am I missing.
Attachments:
Switch Connect-Mult Channel working.vi ‏26 KB
PXI-2566 error.jpg ‏19 KB

Hi Alyeska,
When you say that you modified the example so as to test your new card, I am unclear as to what you are trying to do. What functionality do you want to test? The example that you attached configures the device, makes all the connections on the scan list, waits for those connections to settle, and then disconnects all the connections listed on the scan list returning to the original position, and waits for that to settle.
Now to address your confusion about “channels” and “com”s. Your PXI-2566 switch module is “Single Pull Double Throw (SPDT).” This can be seen in the attached image from the excellent NI-SWITCH Help that installs on your computer with the drivers. While most switch modules have a large number of input channels that can be connected one at a time to one outgoing common or “com” pin, your module has 16 common outputs, each of which has only two inputs. The two input channels are labeled “NC” for normally closed (connected) and “NO” for normally open.
The cause of your error message could be two things. The message states that it does not understand the “~” symbol, since it looks for a channel name (for example: ch0 or com0 or nc0) following the specified device. In order to disconnect, the “~” has to come before the device name, so your scan list would look like “~/RelayDevice/no0->com0.”
However, even when the “~” is in the correct location, you still may have difficulties. This is because DAQmx’s Scan mode is by default “Break Before Make” which means that the hardware will break one connection before making another. The only time the “~” disconnect needs to be used is when “No Action” mode is engaged and connections are not broken unless explicitly told to do so. This example program first connects the channels on the scan list, so when it begins to run through the list and sees the “~” it will throw an error. If you look at the block diagram, the disconnect function follows the connect, so every connection that was made on the scan list is then disconnected for you and the relays will return to their default NC position.
I am unsure of how you want to test your new card, but there are a number of great example programs included in LabVIEW with the switch driver. These can be found by navigating to the Help Menu>> Find Examples>> expanding the Hardware Input and Output folder>>expanding the Modular Instruments folder>> and then looking in the NI-SWITCH file. When you click on an example VI, a brief description will appear in the Information box to the right of the Example Finder. You might want to look at Controlling an Individual Relay.vi, Making Connections on a Switch.vi, and Software Scanning.vi. The other examples are for using switch modules with Digital Multimeters and Thermocouples.
Also, when you find some documentation unclear, I find the NI-SWITCH Help to be very useful. It can be found by going Start>> Programs>> National Instruments>> NI-SWITCH>> Documentation>> NI Switches Help. Here you can see the pinouts for your specific device and find explanations of syntax, scanning, and triggering.
I hope this explanation helps, Mallori M.
Message Edited by mallorim on 01-16-2008 07:28 PM
Mallori M
National Instruments
Global Customer Education Program Mananger
Calculate the time you will save with NI Training
Attachments:
single pull double throw.PNG ‏4 KB

How to make a virtual channel in MAX using DAQmx ?

I want to measure the CJC temperature on the TBX 1328 ( attached to SCXI 1121). I want to create a virtual channel in MAX using DAQmx. I have right clicked on DAQmx but there is no option for virtual channel. Ther is the option of 'Traditional virtual channel' which i dont want.
I used the VI to make the virtual channel but i want to knowhow to doit inMAX.
thanks

Here are 2 ways that you can create a DAQmx channel that appears in MAX.
1) In MAX, right click on "Data Neighborhood" and select "Create New...". Then click "NI-DAQmx Global Channel" (or "NI-DAQmx Task" -- a task contains the channel(s) and triggering/timing information) and click "Next". This launches the DAQ Assistant that will guide you in creating the channel or task.
2) In LV, place a NI-DAQmx Global Channel control on your panel or constant on your diagram. Right click on the control/constant and select "New Channel(DAQ Assistant)..." (Note: You can do the same from the NI-DAQmx Task control/constant to create a NI-DAQmx Task.)
Deborah

Serial ports not appearing in MAX - VISA installed.

Hi All,
Had a rather strange issue today that I couldn't resolve with serial ports not appearing in MAX (and hence being inaccessible to LabVIEW). Under the windows device manager it shows 4 COM ports and I have verified with an external program that they are functioning correctly.
I had the LabVIEW 2011 SP1 f2 runtime installed, DAQmx 9.6.1 and NI-VISA 5.3 (5.2 also didn't work).
Things I have tried:
- Updating VISA from 5.2 to 5.3
- Reinstalling the COM port devices under device manager
- Changing the COM port numbers
- Verifying that the COM ports are functioning correctly
- Tried adding a USB to Serial converter as a new COM port
- Reinstalling MAX
- Reinstalling NI-VISA
- Reinstalling everything (reboot each time when prompted)
- Resetting the hardware configuration from within MAX
- Run installers / MAX as administrator (this is running from the local admin account)
- Checked that NI-VISA appears under software in MAX
- Repaired MAX/NI-VISA
Is there anything else that could cause the COM ports not to appear in MAX when they appear (and work correctly) in device manager when a reinstall of NI VISA / MAX won't solve?
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets
Solved!
Go to Solution.

I found the solution - it turns out that the serial ports were available to LabVIEW, they just didn't show up in MAX because installing just the runtime does not show the devices in MAX.
Despite doing a lot of googling earlier, it didn't throw up this knowledgebase article until I searched for it under a different phrase - http://digital.ni.com/public.nsf/allkb/766FD80DAE42E52886256A0200619CFE?OpenDocument
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Tektronix TDS 220 Oscope not found by MAX using USB GPIB HS

Max 5.4 will not identify my Tk TDS 220 for any GPIB address I set it to.
THANKS for any help!
I've already tried everything from these links:
http://www.ni.com/download/ni-488.2-3.1.1/3786/en/
http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=289
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=047216EC20B66FABE0440003BA7CCD...

Hi VISluth!
Is your instrument set to allow external control? You can find information about this in the instrument manual.
Also, while looking into the TDS 220, I found the following webpage which could suggest that you have defective hardware:
http://www.tek.com/service/safety/tds210-tds220
You could also check for IP between the instrument and your computer.
Applications Engineer
National Instruments

PXI-6255 not identified in MAX as DAQmx

Similar Messages

Maybe you are looking for