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

Similar Messages

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

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

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

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 - 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).

RIO not seen by project

I have a 7133 RIO FPGA PXI card. It is seen by MAX but not available through "my computer" in a project. The card may have been moved to a different PXI slot after initial installation. Any suggestions?
Solved!
Go to Solution.

Hi Ken,
do you have any other cards installed in your pxi?
I'm asking because we had the same problem with an 7131. It didn't work as long as we had an 6653 Timing Module installed.
NI-Support delivered some information to the problem:
http://digital.ni.com/public.nsf/allkb/ECD4F3D186F9C60B862574890050C8D4?OpenDocument
As a quick solution we uninstalled the 6653, but we still have an open issue with this.
Regards,
Thomas

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

Ipod not seen by windows or itunes

Hello, I'm totally frustrated and have been searching for hours. Please someone help.
- Nano 8 gb
- Windows xp
Neither Windows (my computer) nor Itunes sees my ipod. Ipod is working fine: did the menu/select thing, cable is good.
When I plug the ipod in the usb port I hear a bleep and I get a message bottom right "new hardware found ipod"and the icon is a usb cable. Ipod is not in My computer window. Ipod is not seen by Itunes
Tried Device Manager/I see Ipod with a ? Yellow. If i right click on it and do update driver the ms computer management system crashes and sends error report.
I tried dowloading the USB driver and placing it in the directory, but I got stuck because there is no windows/inf directory. I tried to update the usb driver with the same ms crash.
I'm completely frustrated, please can someone help me.

I was having the same problem the other day. I'm not sure what it was but I think it has something to do with the i tunes and i pod 1.2 update.
What I did was:
1. Uninstall i tunes
2. Restart my computer
3. pluged my ipod in a slow usb line
4. waited until my pc recognized it in there. It took a little while.
5. re installed i tunes from apple.com
6. waited until i tunes recognized my ipod
7. updated my i pod with my library it took a long time because i was in the slow usb plug.
8. re plugged my ipod into a 2.0 usb line
9. i tunes recognized it.
10. I then updated my ipod to the new 1.2 version
11. The problem started happening again
12 I repeated what I did before and now it is working.
It was very frustrating! I hope it works for you.1

5th Gen IPOD - Won't Sync and Not Seen by Windows

Help!!!
Tried the 5 R's. I have the IPOD in Disk Mode but whilst it will happily charge, it still is not seen by ITunes or Windows Explorer (though is visible inDisk Defragmenter). I have already un-installed and re-installed ITunes etc.
Prior to putting it into Disk Mode the IPOD still had my library on it and owuld happily work.

Have you had a chance to look at these troubleshooting pages? They may be of some help:
iPod missing in My Computer and in iTunes
iPod is not recognized properly by computer when USB drivers are not installed properly or are out of date
If you are using a laptop, this page might help: iPod not recognized when connected to Windows laptop over USB

IPod touch: Seen by XP, not seen on OSX.

Strange one.
1st Gen ipod Touch with latest software(think its 3.3), latest version of itunes.
Its seen and works perfect with Windows XP.
I plug it into my Mac Book Pro, running Lion and its not seen. nothing happens wihen i plug it in.
I have reset, restored and wiped the ipod from the device itself and its still not seen.
I also tried it on a Win 7 machine and its NOT seen either.
Is this something crazy to do with 32bit architecture. Its seen on Win XP which is 32 but not by 64bit Lion and Win 7.
Any suggestions?

Have a Look Here
Device Not Recognised
For PC
http://support.apple.com/kb/TS1538
For Mac
http://support.apple.com/kb/ts1591

HT4356 My iPad does not find the printer. I have tried the HP app and it works, but in any other app the printer is not seen. How do I get this printer visible to the iPad. All my other network computers find and print with out a problem.

My iPad does not find the printer. I have tried the HP app and it works, but in any other app the printer is not seen. How do I get this printer visible to the iPad. All my other network computers find and print with out a problem.

hi
could you tell us what the other app is please

Attachments and history of my emails are not seen by Windows users

attachments and history of my emails are not seen by Windows users

Just guessing at what you mean, try this:
In Mail, while composing a message, go to Mail's menu and click:
Edit > Attachments > Always send Windows-friendly attachments

In my iPad mini some apps are not seen (voice recorder, calculator, compass etc)

in my iPad mini some apps are not seen (voice recorder, calculator, compass etc)er

Those apps aren't included in iOS on iPads
iPad Mini built-in apps : http://www.apple.com/ipad-mini/built-in-apps/
iPad manual (which has a chapter on each of the built-in apps) : http://support.apple.com/manuals/ipad/

PXI 7314 not seen in MAX

Similar Messages

Maybe you are looking for