PXI-6602 is not detected by M&A

Hello,
I have a PXI-1033 (integrated MXIe card) chassis with a PXI-6602 module installed in it.
Measurement & Automation Explorer shows only PXI System (Undifined), please see attached file (1.jpg). In the list "Identify as" I can not see NI-1033 controller. Before that I have installed software form "NI PXI Platform Service". When I choose NI-1033 controller from CD the message "could not import controller information" is appeared, when I choose any other controller, Measurement & Automation Explorer shows "chassis" which I can identify as PXI-1033. But there is no possibility to detect PXI-6602 card by Measurement & Automation Explorer.
System information: Win XP, LabView 8.5.1,NIDAQ922f0 drivers are installed.
So, the questions:
1. Why there is no DAQmx branch in Measurement & Automation Explorer tree with PXI-6602 card?
2. How can I test my PXI-6602 card (it absolutely new, but...)?
3. How it is possible to install correct controller for PXI-1033 chassis?
Thank you.
Attachments:
1.jpg ‏141 KB

Hello,
the problem discussed in the previous message was fixed and here is the solution:
After additional investigation it was found that the issue is with "This device cannot find enough free resources that it can use. If you want to use this device, you will need to disable one of the other devices on this system. (Code 12)". This topic was discussed (http://digital.ni.com/public.nsf/allkb/04C12CB4A5143ECC862572DC007B8DF6). But it did not help. I updated the BIOS in my Laptop (Dell Vostro 3300) from A05 to A09 version. But it did not help again.
After that I found a "MSI-Express BIOS Compatibility Software". Installation this software fixed the problem.
Hope this information will be helpful.

Similar Messages

PXIe-1073 sytem not detected

I connected a PXIe-1073 system (PXIe-6363 and PXI-2567 connected) to the PC (running Windows 7) and the PC does not detect the chassis. It started happening when I recently upgraded to LabVIEW 2013 and NI-DAQmx 9.7.5.
I also installed the MXI BIOS compatibility software Ver 1.4, changed the DIP switch1 to ON position on the MXI express card 8361 and rebooted the computer. That did not solve the problem.
Then, I upgraded to PXI Platform services 3.2.3 and restarted the computer. I still don't see PXI system recognized in NI MAX. When the computer was restarted, the 8361's MXI card's switch 1 was still in ON position.
Any ideas on how to fix this issue ?
Thanks
Jeet

Hi Matt
Sorry for delay in replying.
After a lot of uninstallation/installation/repair of different driver versions, i have currently got the following software (see attached pic): NI-DAQmx 9.5.5, Ni PXI platform services 3.2.1.
In the picture, you can see that all my cards are detected in NI-DAQmx devices as Dev1, Dev2 etc.
My PXIe-1073 is not detected or listed in MAX. I expect to see chassis controller detected and all the cards listed under the chassis controller as "PXI2slot2" device or "PXI2slot4" device etc.
The attached pic shows NI-MAX and device manager snap shot.
Please advise.
Thanks
Jeet
Attachments:
nimax dev man.jpg ‏316 KB

MXI3 (NI PXI-8330) board not detected. Not powering up, no link light.

MXI3 (NI PXI-8330) board not detected. Not powering up, no link light. Cable looks fine. Any ideas?

PeteMan,
I will need to know in more detail how your system is behaving to give you better tips, so please feel free to send me more information.
For now, let me send you a couple of troubleshooting tips:
Cable connection
Make sure both ends of the copper cable are well connected to the PCI-MXI-3 and the PXI-MXI-3 boards. Be careful when disconnecting the copper connectors. you need to push down the plastic connector so it does not get damaged. Damaged connectors could result in bad MXI-3 links.
If the connector has not been used properly, it could be broken (this rarely happens). Make sure you are not connecting the cable backwards.
Power - Up order.
It seems you are controlling your PXI chassis using a PCI-to-PXI extender (copper cable). Make sure you are powering up the PXI chassis BEFORE powering up the PC.
PXI is built on top of the CompactPCI spec, so it uses the PCI high speed bus. The MXI-3 extender is really a PCI-to-PCI bridge toyour computer, so for your PC, all the slots in the PXI chassis look like more PCI slots. In other words, your computer suddenly has more PCI slots.
It is very important to power up the PXI chassis first before powering up the computer, because at power up the PC enumerates all PCI slots. If the PXI chassis is OFF during boot up, the slots in the PXI chassis will never get enumerated and your PC will never see the board installed in the PXI chassis.
Normal Power up LED sequence
Each MXI-3 board has four LED light on its front panel: two green lights (POWER and LINK) and two orange lights (Tx and Rx). When you power up the PXI chassis you should see one green light and one orange light ON steadily (POWER and ). Then, when you power up the PC, both green lights shoudl be ON steadily and the orange lights shoudl flicker.
If you do not see this behaviour at power up, most probably one of your boards its damage.
If you have another MXI-3 extender kit, try to set up the system mixing the boards from the two kits to try isolate which board is the one that is damaged.
Run the MXI-3 Optimization Software
The MXI-3 Optimizaton Software makes sure that the link between the PC and the PXI chassis has been set up properly. It will show you an error otherwise.
MXI-3 Software Version 1.15 for Windows 95/98/NT/2000/ME
The PC powers up fine if the PXI chassis is OFF, but if I turn on the PXI chassis first and then try to power up my PC, my PC does not boot
There are several things that could be causing this behaviour:
It could be that your PC has an old BIOS that has issues detecting PCI-to-PCI bridges. You could try upgrading the BIOS.
A part of the hardware could be damaged. If you have a main-stream computer (like a DELL or HP PC, for example), test your MXI-3 extender in it to make sure that the hardware is in good conditions. Main-stream computers tend to use new Motherboards with good BIOS.
There are more tips in the following KnowledgeBase:
KB 267FAS5P : MXI-3 Troubleshooting Guide
Hope this helps,
Claudia Lorente
Applications Engineer
National Instruments
http://www.ni.com/ask

NI PXIe 8361 card not detected

Hello,
I have a problem with a NI card.
I had my NI PXIe 8361 card mounted on a windows XP, connected to a PXIe1073 frame. It all worked fine.
Since then, I changed my PC, I now have a new one with windows 7.
I've installed LabView, DAQmx but when I insert the card into the computer and connect it to the frame, nothing happens.
-> on the card the green leds are on
-> on the frame the green power led is on but the link led is off
-> in the device manager of NI MAX I don't see any NI PXIe 8361
despite various attempts it won't work, did I missed something? something more to install?
Thanks in advance for your help.

Pierre24 wrote:
There was nothing in the slot before, first use of it.
There are other slots and I've already tried them, same result.
I don't have any other card to test :/
But what can be the problem with the PC ? I think everything is installed, lights on the card are green and the PC is new with much higher performances than the old one.
Looks like you need to install PXI Platform Services. http://www.ni.com/download/pxi-platform-services-14.0/4897/en/

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 cards on 1000b cahssis not detected under windows 98

my mxi-3 card is being detected on windows startup (mxi-3 optimization software is running correctly) but all other pxi cards on my 1000b pxi chassis are not detected.

Anis,
Well, I always prefer to try the simplest things first. In this case, that would be fully powering down the chassis and the computer. Then powering on the chassis first, and a few seconds later, powering on the computer. If this doesn't help, then you would probably want to try any or all of the following troubleshooting steps to try and isolate the problem:
- Try removing all but the mxi-3 and one other card from chassis and then try booting up.
- Try placing the pci mxi-3 card in a different slot in the computer.
- Try uninstalling and reinstalling all the NI software on your computer. (better yet, format and reinstall).
- Try the pci mxi-3 card in a different computer.
- Try a different set of mxi-3 cards (if available)
- Check
device manager to see if there are any errors or warnings.
So those are the things that I would try. If after all that you still have no luck connecting you may have a hardware problem and need to RMA (Return Materials Authorization) your hardware.
Please post back with what you find.
Regards,
Jed R.
Applications Engineer
National Instruments

NI Scope Sorf Front Panel will not detect NI PXI-5122

Hello,
I am trying to use NI Scope Soft Front Panel 2.7f0 to acquire simple waveforms;
however it will not detect my NI PXI-5122. I have confirmed that the digitizer
works under MAX 4.2.1 and can see waveforms under the test panel. I have
installed NI Scope 3.3.1 on my machine and have updated the driver on the PXI
to version 3.3.1. Any ideas on what is wrong?
~Buck

It is unclear from your post whether or not the 5122 is on the same physical device as you are running the soft front panel (SFP). The SFP only works on local devices. It does not have the capability to attach to RT or remote systems (MAX does). However, if you are running Windows on your PXI controller or are using MXI to control the chassis, there is another issue.
This account is no longer active. Contact ShadesOfGray for current posts and information.

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

NI PXI-1033 not detected if turned on after PC

Hi,
I noticed that MAX does not detect the presence of the NIPXI-1033 if it is turned on after the PC.
There is a programmatic solution to resynchronize the device? My application using C # and C + +.
thanks
Roberto Guerzoni
Solved!
Go to Solution.

Thank you Roberto
It is normal what happens. Your PC has to see the device during the boot up. It is a BIOS matter.
Have a great weekend!
Antonios

NI PXIe devices cannot be detected

Hello, I am 1-year-user of NI instrument. I am using NI PXIe-1062Q. I have some problems with several NI PXI devices installed on this NI PXIe1062Q. My devices are:
1. NI PXIe-8115
2. NI PXI-4071
3. NI PXIe-6556
4. -
5. NI PXI-5922
6. NI PXI-4132
7. NI PXI-6541
8. NI PXI-6602
As attached in the pictures, only the NI PXIe-6556 are detected and the green LED is on. But the other devices are not detected and their green LEDs are off.
I have used these NI PXI-4071 and NI PXI-5922 before for measurement and they worked well. Several days ago I replaced NI PXIe-6556 with NI switch NI PXIe 2527, and the new device are detected.
But after I want to use other devices again, I found that other devices cannot be detected.
Could anybody help me to solve this problem?
Thank you before
Attachments:
NI error 2.JPG ‏116 KB
20150413_120628.jpg ‏2743 KB

Hello bilox,
This is certainly strange and unexpected, so let's see what other information we can dig up about your system to identify the root cause of this issue, as there could be many different possibilities to sort through.
The first thing NI support will typically ask from you is a MAX report that details the system software and the hardware as reported by MAX. You can find out how to generate the report here: Using MAX Technical Report to Document Measurement & Automation Explorer (MAX) Configuration Informa...
Besides this, I'll go through a checklist of items to help narrow down the reason for this issue.
Check your device manager to see if the instruments not detected by MAX are identified by your OS. If so, it could indicate MAX is not appropriately displaying your instruments. You can also check here if the system is identifying the devices and their appropriate device drivers correctly.
Speaking to device drivers, are they up to date for the OS you are using? The version of MAX? Are you coming off an image or a clean machine that used to have device drivers on it? Did you uninstall any SW lately? The device drivers are required to identify SW in your machine.
If you remove all the HW in your chassis and add each instrument one at a time, are they detected? This takes some time, so if it were me, I'd remove the 6556 to see if any other instrument is detected. If so, then take those results and mix/match to try and identify if a particular instrument is causing the behavior.
If you have a spare chassis, try changing it out to see if the issue follows the chassis, the controller, or the instrument.
Hopefully, this provides enough information to continue troubleshooting and finding the answer to the issue. If you need more online resources, you may always visit ni.com and ni.com/support for more help online. If you continue having issues, you may want to email/call one of our Application Engineers to assist you with further troubleshooting steps for your system.
Thank you for the follow up information.
Kyle A.
National Instruments
High Speed Digital I/O Product Support Engineer - R&D

PXI 6602 - Retriggerable Finite Pulse Train Generation

Hi,
I have a VI in LV7.1 where I configure PXI 6602 to generate finite pulses whenever a trigger is received. And the Retriggerable Property is set to TRUE. I look for the task to complete in order to proceed with the other operations.. This actually works. As soon as the pulses are generated DAQmx Task Done becomes TRUE.
The same VI I upgraded to LV 2011but this time the 'DAQmx Task Done?' never becomes TRUE even after the trigger is received and pulses are generated.
Does anyone know if the 'DAQmx Task Done?' functionality is changed in higher version of LabVIEW so that it no more works as it was in LV 7.1?
Is yes, then do you know what property to use to know that the operation is done?
Any help is highly appreciated.
Thanks.

CORRECTION TO PREVIOUS POSTING THERE WAS AN ERROR IN HOW I DESCRIBED THE PROBLEM:
I have a problem using a retriggerable finite pulse train as in the NI example Retriggerable_Finite_Pulse_Train. I use ACTOUT to gate the first re-triggerable pulse control and the second pulse control generates the continuous pulse train which is gated by the first retriggerable pulse control. The ACTOUT signal is generated by an AI control which senses a crank trigger (Hall Sensor). The re-triggerable pulse train is used to modulate a fuel injector in sync with ignition timing and RPM. If the period of the ACTOUT signal changes due to a change in RPM, the pulse train is recalculated. It works OK with one hitch. Even at constant RPM, after about 15 re-triggerer pulse trains the final pulse of the train does not complete. This leaves the signal high in-between successive re-triggerer pulse trains. This incorrect high signal between re-triggerer pulse trains means that the fuel injector is incorrectly left on in-between pulse trains. This incorrect high signal goes on for about 10 pulse train events and then returns to normal. This pattern repeats. I use the ActualPeriod of the second control's continuous pulse train to ensure the pulse train ends correctly within window of the first re-triggerable pulse. This work but with time this pulse train seem to shift slightly. Is there another way to create a different type of re-triggerable pulse train that overcomes this problem?

RPM Measurement using Quadrature Encoder and PXI 6602 counter

Hi,
I am on a project at work where I need to verify the speed (in RPM) of an unloaded motor which can operate up to 1400 rpm. After doing some research, i determined that a quadrature encoder could be used to make the measurement. I am looking at this encoder http://sine.ni.com/nips/cds/view/p/lang/en/nid/205321.
I have a PXI 6602 counter/timer module in which I would like to interface to the quadrature encoder. I would like to create a VI that allows me to calculate the speed using the encoder. Can someone provide me with details of what needs to be in the VI or an example which can do this? At the most basic level, i want to calculate the speed on demand. After doing this, i would like to figure out how to quickly calculate the speed so that i can determine response time of the speed changing within sub-millisecond resolution (1 ms resolution max).
Further, i created a VI that allows me to change the pulse width of a 100 Hz pulse train at run-time which tells the motor controller the desired speed. I would like to be able to use this VI to change the speed of the motor and the first VI (that I am seeking help about) to calculate the response time (time between the initial speed and settling at the new setpoint).
I am familiar with the NI example finder, but have not been able to find an example that I can use.
Thanks,
Gary

Hey Gary,
I think for you setup, you should try using the Meas Dig Frequency - Low Freq 1 ctr. You can find it by searching example finder with 'low freq'. This vi tells you the frequency of a digital signal by sampling between two pulses and inverting the time between pulses. If you hook up your encoder to a counter and have that counter specified in the vi, it will be able to give you on demand readings of frequency (you can do some multiplication to get the rpm value, freq*60/pulses per revolution of encoder). A simple way to take continuous readings is to put a while loop around the daqmx read and the data output of the read. You can also replace the numeric indicator to a waveform chart to graphically display the change of frequency or rpm readings over time.
You should be able to integrate this as two separate tasks with the pulse train vi you created earlier.
Hope this helps
Luke W

Error when trying to use DO as "open collector" on PXI-6602

When I try to configure a DO of my PXI-6602 as "open collector" I receive the error -200452 ("Measurements: Specified property is not supported by the device or is not applicable to the task."). This is completely mysterious to me since the PXI-6602 should have this feature and my code (see attachment) is practically identical to any of the numerous examples for this topic. Am I overlooking anything really stupid? (LV 8.5, PXI-8145RT) Cheers, uli
Solved!
Go to Solution.
Attachments:
openCollectorTest.vi ‏14 KB

Hi uli,
Did you try setting DO.Tristate while the task is running? There are a few DAQmx devices that do not support setting DO.Tristate while the task is running, but I don't think that the PXI-6602 is among them. I don't have an actual 6602 installed but with a simulated PXI-6602 and DAQmx 8.9, setting DO.Tristate while the task is running does not error.
Using external hardware is perfectly fine, and should also work for timing I/O (whereas using DO.Tristate would only work for single-point digital I/O).
I don't see the text that you quoted in the NI 660x Specifications, so I don't know what context it was in, and apparently it has been reworded since then. Note that devices that support open collector output say "open collector (open-drain)" in their specifications; for an example, see the NI USB-6008/6009 User Guide and Specifications.
Brad
Brad Keryan
NI R&D

PXI 6602 and encoder reading with two counters

I'm reading three encoders with 2000 pulses for each revolution with a PXI 6602. As the loads are connected to the motors through a transmission ratio of 200 I need to count both the encoder pulses in each revolution and the number of revolutions.
I think I could use one counter, with the standard connections, to count the number of pulses in each revolution and another counter, with the source connected to the Z index signal and the up/down connected to the B channel, to count the number of revolutions.
Does somebody know if there is a simpler solution or a solution that needs only one counter?
Thanks

You can do this with one counter. Since you know the relationship between counts and revs (2000:1), you don't really have to count the index pulse separately. Just take the total count and divide by by the counts per rev. The quotient is the number of revs and the remainder is the position within a particular revolution. Make sure to turn off Z indexing with Counter Set Attribute (attribute 20), so that the counter does not reset each revolution.
Take a look at the NI-DAQ shipping examples in LabVIEW 6.1\examples\daq\counter\ni-tio.llb or at the example linked below. Just add the division operation to get the number of revs.
http://zone.ni.com/devzone/explprog.nsf/6c163603265406328625682a006ed37d/8bebc7cce0aa65f686256866005e411b?OpenDocument
This
seems like a fairly simple solution. Please let me know if I have misunderstood the question.
Good luck,
Brent R.
Applications Engineer
National Instruments

Routing signals PXI-6602

I'm trying to route a single input to more than one counter. I've been wading through the routing signals options with no success. I have a PXI-6602 and using LabView 8.20. I have a single input that I want to measure the period and pulse width on. Hooking up multiple external lines is an option, but I'm converting from fiber to the input so it would be much easier to route the signals internally.
My 6602 is Dev1. I can't seem to nail down how to use the route signals vi. I've looked at some examples with no more clarity. What's the easiest way to accomplish this task internally and is there a simple clear example?

I would wire to the PFI pins associated with the Gate input of either Ctr0 or Ctr1. These PFI pins are *not* shared with DIO functions so there's no chance of conflict with future DIO usage.
Both period and pulse width measurements should allow you to successfully specify any of the Gate input PFI pins as the signal source. You shouldn't need to call any explicit signal routing functions if you're using DAQmx -- it handles most stuff auto-magically.
Another option may be to configure for semi-period measurement. Depending on the polarity setting, the pulse widths will be either the even or the odd values in the measurement data. The periods will simply be the sum of adjacent pairs of values, though you may need to ignore the very first value in a buffered measurement -- it represents the (meaningless) time from starting the task until the first active edge.
Sorry, not at a LV machine to create & post an example...
-Kevin P.

PXI-6602 is not detected by M&A

Similar Messages

Maybe you are looking for