Identification of a PXI-8420

Hi,
I am using RS232 cards like the PXI/PCI-8420/2 in some (not in all) of our systems. To identify which system it is I have to find out which card is available. I can see the card in the MAX but I didn't find a solution to find it from the software
- How can I identify from my software if such a card is available in the system ?
- Can I differ with the software if it is a PXI-8420/2 or a PXI-8430/8 ?
Thanks in advance
Oliver

The reason why this is not so easy is the fact that DAQ boards are accessed through an NI driver but the COM ports of the 84xx devices are accessed through operating system functions (even VISA doesn't talk to the ports directly but through the Windows API). With DAQ it's easy for us to implement a function to identify devices but this feature is not available for serial devices.
Here are some other ideas:
1. Open and close VISA sessions to a list of ports in an initialization step in your program. If you don't receive an error you know that the port is present.
2. Check the registry for instances of the devices you are looking for. I don't have a 84xx device here but I would expect it to show up somewhere here: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\.
Find out where the key for your hardware is located and use the Windows Registry Access VIs from the Advanced palette to read it.
Best regards,
Jochen Klier
National Instruments Germany

Similar Messages

Considering the PXI-8420/16 as a solution for running one application to communicate to multiple devices.

I am developing an application that needs to communicate through a serial interface to several devices under test at the same time.Would the PXI-8420/16 be a solution??

If the NI serial cards do not do concurrent communication, then how do they work? I have a similar application but the communication doesn't necessarily need to be concurrent. It just cannot be sequential. Maybe the NI serial cards will suit my needs but I need an explanation of their operation before I can determine that.

PXI-8420

Can a PXI-8430/8 be used to replace a PXI-8420/8 in an automated test bench? I have existing software written in LabView for a PXI-8420/8 for which I do not have source code. I only have an execuatable.

Hi bsexton,
The only thing you might have to change between the PXI-8420/8 and the PXI-8430/8 would be the ports. Is the executable set up to allow you to select ports? Otherwise the PXI 8420/8 is discontinued and the recommended replacement is the PXI 8430/8.
Andy K.
Applications Engineer
National Instruments

Need std and non-std baud rates on PXI-8420 (16 channel RS232)

I found a similar request on the knowledge base, and the resolution was possibly NI would make a card on a case-by-case basis.
I need the forementioned PXI card to support std and non-std baud rates (i.e. not a simple xtal change, and the software sets up for 57.6 Kbaud, and it is really 62.5 Kbaud) that is easily configured in LabVIEW/VISA.
The rates I need are as follows:
All std rates (i.e. 1200,2400,4800,9600,...)
10.4K (possible with std ports, but unsure about NI hardware and VISA).
62.5K
Thanks.
62.5K

The golden rule in serial (UART) communication, is that if two communicating partners are within +-2% of each other, they'll happily communicate error-free. Since you often only know one side of the equation, the window narrows to +-1%.
Next, take a look at how baud rates are calculated. On most NI-Serial hardware, there is a 7.3728 MHz oscillator that is divided by 16 (to create the what I'll call the 'base' frequency), and then divided again by a divisor latch. A divisor latch value of 1 yields 460800, 2 = 230400, 3 = 153600, etc. This is where the 'standard' baud rates come from.
However, on some OS's, we divide the clock source again by 4 before it hits the divisor latch. This means 1 = 115200, 2 = 57600, etc. While this does creat
e a set of 'standard' baud rates, it also limits the number of possible baud rates. This is something that will be fixed in the future.
Now hopefully the following table will make sense. In systems that have a base of 460800, we support baud rates that are within +-1% of the following (baudrates marked with * are supported in 115200 base systems):
110-9216*, 9404, 9600*, 9804, 10017, 10240, 10472*, 10716, 10971, 11239, 11520*, 11815, 12126, 12454, 12800*, 13165, 13552, 13963, 14400*, 14864, 15360, 15889, 16457*, 17066, 17723, 18432, 19200*, 20034, 20945, 21942, 23040*, 24252, 25600, 27105, 28800*, 30720, 32914, 35446, 38400*, 41890, 46080, 51200, 57600*, 65828, 76800, 92160, 115200*, 153600, 230400, 460800.
10.4k is supported in both systems at the baud rate 10472.
If you're running at 62.5k when set to 57.6k, then you're likely using a 8 Mhz Oscillator. In this case, you have a base of 500000, and with a divisor latch value of 48 you'll be running at 10416. This cor
responds to a 'normal' baud rate setting of 9600. So if you set your modified card to 9600, you should get 10.416k.

After upgrading PXI controller, all PXI slots show "0" in MAX

I recently upgraded from the PXI-8176 controller to the PXI-8187 controller and all of the PXI slots now show "0" in the PXI slot value within MAX (under "Traditional NI-DAQ Devices"). I am using the PXI-1006 chassis.
What's the problem there? I have all 18 slots full with three different types of cards and I'd like to be able to tell which is which without having to hunt for it each time I swap out a card.
Thanks,
rgames

Hi,
MAX is reading the former configuration of your sys.ini file for the PXI chassis. So we need to delete that and create a new one.
The best way to solve your problem would be to right-click on PXI System under Devices and Interfaces in MAX. Choose "Delete All Identifications". Your PXI system should then say "unidentified" by it. Right-click again and choose "Identify As", then choose your controller. All your modules and an unidentified chassis should show up. Then right-click on the unidentified chassis and choose the chassis you have. Once it's been identified, press F5 to refresh MAX and then all your devices under Traditional NI-DAQ should have the correct slot number by them.
Let me know if that doesn't work!
Brian Spears
Applications Engineer

Programmatically identifying com ports by their physical port number

I have a system with a NI PXI 8420/16 card. Once in a while a glitch in my PXI system occurs such that my physical RS-232 ports get re-assigned different com port numbers. Then I have to go into MAX and reassign my aliases to re-align my LabVIEW application with my port hardware. Is there a way to stop these glitches from happenning? OR is there a way to programmatically identify a physical port's com number?
Solved!
Go to Solution.

See if this helps: http://forums.ni.com/ni/board/message?board.id=170&message.id=490257#M490257

Program identifies the pxi chassis

I have a utility in Lab Windows CVI 2012 that runs on a PC, PXI or PXIe. I would like the program to be able to identify which of these it is running on.
Right now we have a read of a device in the PXI chassis, just initialize a switch card, if it is successful, we have the PXI or the PXIe. My concern is if that one card is not present, also this results in a run time error if the card is not there, or if it is a PC.
I would really like something to read directly from the PXi, a serial or device number or something. Sort of like we have in our code to read the type of CAN device, first we get the CAN device number, then the device type:
/* find "can_num" for NI CAN device (just not USB) */
Status = ncGetHardwareInfo(can_num, 1, NC_ATTR_HW_FORMFACTOR, 4, port_check);
/* use "can_num" from PCI, PXI, or PCMCIA Device to get port number */
Status = ncGetHardwareInfo(can_num, 1, NC_ATTR_INTERFACE_NUM, 4, port_check);
Is there any such function to read the PXI chassis?

Hi Ken-this-...,
I think what you want is DAQmxGetDeviceAttribute(). Here is a link to a similar post:
http://forums.ni.com/t5/LabWindows-CVI/How-to-detect-PXI-chassis-cards-and-their-serial-numbers-in-C...
Peter T
Applications Engineer
National Instruments

PXI-8630, PXIe-1078 non identifiés dans MAX

Bonjour,
J'ai un chassis PXI-1078 contenant des PXI (4110, 4130, 4132, 2532) et contrôler par un pc portable en utilisant PXI-8360.
Mon Problème est que sur le gestionnaire des periphériques le pont PCI vers PCI standard ne montre aucun problème mais, sur MAX quand je veux ajouter un chassis j'obtient dans la liste de "remote controller" : NI PXI 8310 au lieu de 8360. En plus de ça mon PC ne detecte pas les PXI existants dans le chassis comme des nouveaux periphériques dans le géstionnaire des periphériques.
Que puis-je faire pour résourdre ce problème.
sachant que j'ai effectué tous les mis à jours possible qui existent sur Ni support:
MAX --> 5.0
NI PXI Platform services --> 3.0.1
NI VISA --> 5.1.1
en plus des update des drivers pour le mois d'Aout
Merci d'avance
TheShadowx
Solved!
Go to Solution.

Hello,
And thank you for posting here.
What is your OS, your LabVIEW version and the model of your computer?
Did you respect the order of Installation for our products?
http://digital.ni.com/public.nsf/allkb/779E54A45478FA2C86256D0500774FCB?OpenDocument
Is your BIOS version not to old? It could fixes some PXI problems. If you BIOS is updated, you can try the NI MXI-Express BIOS Compatibility Software 1.4 which is still in Beta but which work fine. You can find it here :
http://digital.ni.com/betaprogram/mainbetacust.nsf/main.htm
Here two links to other posts where the problem is quite similar. There as useful links contained in those posts :
http://forums.ni.com/t5/PXI/Express-card-MXI-laptop-compatibility-1033-and-8360/m-p/697994?requireLo...
http://forums.ni.com/t5/NI-Applications-Engineers/PXIe-1073-via-MXIe-8360-not-visible-in-MAX/td-p/14...
Regards,
Jérémy C.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Travaux Pratiques d'initiation à LabVIEW et à la mesure
Du 2 au 23 octobre, partout en France

Why can't LabVIEW 2011 find my PXI?

I'm migrating some real-time Projects from older versions of LabVIEW (8.6 and 2010) to LabVIEW 2011. For the older systems, I installed the appropriate Real-Time software (matching version numbers) on a PXI controller, which MAX saw just fine. When I opened my Project, I chose a New Target and had it look for an existing Real-Time PXI -- it always found the PXI without trouble.
I've just taken another PXI controller (8176) and installed LabVIEW 2011 RT on it. Curiously, during the installation process, MAX identified it (and still does) as a Generic Desktop PC, and when it finds it, gives it a PC-looking icon instead of a PXI chassis icon. When I open my Project in 2011 and try to add this PXI as a target, it finds no Real-Time PXIs. Why is this?
There's a VI called RT Ping Controllers that can find all the PXI controllers -- it finds my PXI, and identifies it (correctly) to me by the name I assigned it, so LabVIEW 2011 can definitely "see" this controller, even if Project (apparently) cannot.
I'm beginning some tests involving TCP/IP (and Network Streams) with this controller and configuration. I've had success with doing this in LabVIEW 2010, but in a (single!) test I've done with this new LabVIEW 2011 RT system, I couldn't "connect". I haven't beaten this system enough, nor done a side-by-side comparison of equivalent code on a LabVIEW 2010 and LabVIEW 2011 system, but would appreciate it if anyone (else) has had issues (or, better, successes) with PXI-related Real-Time in LabVIEW 2011.

Hello,
What version of Measurement Automation Explorer and the NI-DAQmx driver do you have? Also, here is article that you may find of some use:
Why can't I add my Real-Time Target in Project Explorer?
http://digital.ni.com/public.nsf/allkb/40BF6300E77E8AD4862574EF006F2793?OpenDocument
Regards,
Patricia B.
National Instruments
Applications Engineer

PXIe 8108 Rebooting whenever i connected to Max

Hi,
Iam Using PXIe 1082 chassis and pxie8108 controller. Pxi system having Dual Mode boot configuration (Windows/Other os boot and Labview RT Boot).If i boot with windows then no problem it is detecting in Max. If i trying to boot in Labview RT, monitor which is connected with Pxi system shows the following message
Transferring Control to user program
Can't find suitable device for drive C
LabVIEW Real - Time Boot Loader
Build Time: Oct 22 2009 11:01:12
(C) Copyright 2002 - 2007 National Instruments Corporation
Error booting hard drive boot program.
Max system identification name:Ni - PXIe8108-2F12CD1D
LabVIEW Real-Time Single-Core Kernel found '2' CPU cores.
Consider installing NI RT Extensions for SMP (Multicore Support) module from MAX
Initializing network... Link Local IP address assigned.
Device 1 - MAC address:00:80:2f:12:cd:1d: - 169.254.103.152 (primary)
System state: No software installed
if i connect Pxi with other PC MAX then Pxi system is rebooting...
in above Pxi message it is showing" Error booting hard drive boot program". This is the problem for Pxi Reboot ?
Can any one help me to solve the issue...
Vijay

Hi Vijay,
I suspect that this issue is because your system does not contain an RT compatible partition for installing LabVIEW RT.
If your system is configured for dual booting Windows and RT, then you need to have two partitions on your disk, one for Windows (typically NTFS) and a second for LabVIEW RT (either FAT32 or Reliance).
Since you already have windows on the target, you should first boot into Windows and attempt to create a second FAT32 partition for RT if you have some unpartitioned space available on your disk (depending on the version of Windows, they may require 3rd party tools). Another option is to freshly install Windows on the disk using the NI-provided OS Recovery media, which has installation options for configuring a disk to support dual-boot Windows and RT.
As to your original issue as described I have forwarded on your problem internally for further investigation - in general simply lacking a formatted partition should not cause RT safemode to reboot. In your specific situation, however, it would still be best for you to configure the paritions from within Windows anyway instead of using the tool in MAX to ensure that the Windows partition is correctly preserved.
Cheers,
JoshH

Identification NI PXI1042

Bonjour a tous .
Je suis entrain de procéder a une identification du système PXI (Châssis 1042) sous MAX, en utilisant la rubrique
Identifying a PXI châssis Connected by a Third-Party-Bridge (Lien MXI Express X1, NI PXI-PCI 8361 Coté Ordinateur, NI PXI-8360 Express Card coté PXI1042 Emplacement 1).
Je sais que dans ce cas de figure MAX ne détecte pas automatiquement la carte et il va falloir le faire manuellement et la je rencontre des problémes.
Car en affichant les bus SHOW PXI BUSES, la carte ne figure pas non plus sur la liste des bus pour définir et identifier le bus en tant que châssis.
Ma question est la suivante: - La carte doit elle s afficher automatiquement sur la liste des bus ou dois-je le faire manuellement ..?
- Dans le cas contraire c est a dire la carte ne sera pas détectée automatiquement ;
comment choisir le bon bus ( numérotés de 0 ....a 6) pour le définir en tant que châssis PXI 1042 ( voir pièces jointe)?
Pouvez - vous m'éclaircir sur ces points? Avec mes remerciements Anticipés

Duplicate Post
National Instruments
Applications Engineer

PXI-4462 - Radio Sound Environment

Hi, everyone.
I have a PXI-4462 audio card.
Is it possible to use the card to analyze and measure the Sound Environment Settings (eg, Jazz, Rock, Classical, and etc) of a radio audio outputs?
20Hz and 20kHz is the range of the interest frequency for plotting a graph of Gain (dBr) vs freq.
As I know, I may need to sweep the freq range of 20Hz to 20kHz for obtaining the curve.
Hope someone can help to advise.
Attached is the example of the EQ measurement in graph.
Thanks in advance.
Attachments:
800px-Peaking-eq.svg.png ‏20 KB

Hi Karthik,
Can you share the image of the noise signal if you have?
One possible cause i can think of is the High frequency noise source nearby. Have you analyzed the Noise characteristic? You can perform simple FFT to identify the noise source by switching ON and OFF of the nearby lights or machines etc...
One more way is to move the measurement setup out of the current location.
I guess there shall be a better way of identifying the Microphone connectivity rather than comparing the floating signal RMS with the sound pressure threshold level for identification.
Thanks,
Vijay.

Teststand pxi instrument id between embedded and extended chassis

I would like to establish reuse of TestStand LabVIEW Steps between an embedded controller PXI chassis and an extended PXI chassis (that uses a MXI 3). How can I best manage and programably establish instrument or device identification to the VI's without hardcoding the different device id's into the test steps. Is there a feature of MAX that would allow a common naming convention or can I programmably get each card's identification and use global variables? I am lost as to what is the best strategy in dealing with varying instrument identification and wanting to reuse VI's.

the DAQ function on the pallet that will return the device name for each device number. use this to create an abstraction manager to reference named devices. Keep going with the approach of reuse without hardcoding info. It will be worth it.
Stu McFarlane
Viewpoint Systems, Inc.

Slot Detection of PXI Modules, More details

I read the knowledge base titled: Slot Detection of PXI Modules but have a few questions about it. How often to I have to do this? When I insert or remove a board from the PXI chassis? When I insert or remove an additional chassis in daisy chain? With Multiple chassis in Daisy chain. How do I know which device number is which card? ie if I have 2 of the same model of cards both in slot 5 but in different chassis. If I remove a card, am I guarranted that other cards device numbers will not change?

John,
The Knowledge Base (KB) "Slot Detection of PXI Modules" says that the PXI Initialization File (PXISYS.INI) file must be saved in the systems directory in order for the system to be able to identify the slot where a board is located. This is because every slot in a PCI Bus (a PXI system uses a PCI bus) has a PCI Device Number and PCI Bus Number associated with it. The PXISYS.INI file describes the architecture of the chassis and the controller, and has the appropiate PCI Device Number and PCI Bus Number for every slot. There is a unique PXISYS.INI file for every combination of PXI chassis and PXI controller.
How often to I have to do this? When I insert or remove a board from the PXI chassis?
Currently you do not need to edit the PXISYS.INI file. You can download the PXISYS.INI file from our website and use it as it is (see link in the KB you were reading). So you only need to save once the appropiate PXISYS.INI file to the Windows Systems directory, regardless of whether you change the PXI board in your system.
When I insert or remove an additional chassis in daisy chain? With Multiple chassis in Daisy chain?
If you are daysi-chaining chassis, keep in mind that the current PXI Standard DOES NOT support daysi-chaining. However, in previous PXI configurations, I have successfully edited a PXISYS.INI file so I can do Slot Identification in daysi-chained chassis (not in star configuration, though). The steps I followed are in the text file attach to this e-mail.
How do I know which device number is which card? ie if I have 2 of the same model of cards both in slot 5 but in different chassis. If I remove a card, am I guarranted that other cards device numbers will not change?
Finally, if you are using NI DAQ boards, NI-DAQ driver will assign a Device Number to the boards that correspond to the Slot Number, and the Slot Number is described in the PXISYS.INI file that you edited following the instructions in the text file attached below.
If your boards do not use the NI-DAQ driver, but support NI-VISA, you can use the PXI VISA Instrument Descriptor to find out the Slot they are installed in. See the KB "Programmatic Slot ID" linked below for more information. It has an Example Program linked to it too:
KnowledgeBase 2MDFG2WD - Programmatic PXI Slot Detection
Let me know if I can be of further assistance,
Claudia Lorente
Applications Engineer
National Instruments
http://www.ni.com/
Attachments:
PXISYS_for_Daysi_Chain.txt ‏4 KB

Poor PXI IO performance on Latitude E6410 with ExpressCard 8360

Hello,
I have a Dell Latitude E6410 with a Core-i5 M520 which is giving me very poor io performance when using an ExpressCard 8360 card to connect to a PXI Rack.
The sustained IO rate that I can get appears to be about 1/3 of that that I can get using the same ExpressCard on a Dell Latitude E6400 (with a Core2Duo processor).
I am using the A05 bios (latest at time of writing) on the E6410.
Wade.

I am running Windows XP (32 bit) sp3 in both cases.
The E6410 has 4GByte of memory fitted.
The E6400 has 2GByte of memory fitted.
I have also use the same ExpressCard 8360 via a PXIe to ExpressCard Adaptor in a Desktop machine with similar performance figures to the E6400 - i.e. much better than the E6410.
The Desktop Machine is an HP Compaq D7900 with 4GByte of memory, Core2Duo E8500 also running Windows XP sp3 (32 bit).
Also, on the Desktop, I am running NI PXI Platform Services 2.3.2 and NI-Visa runtime version 4.3.
On the E6410, I am running NI PXI Platform Services 2.5.2 and NI-Visa runtime version 4.6.
I no longer have access to the E6400 so I am not sure what sofware versions were installed. However, they are unlikely to be new than the versions installed on the E6410.
Wade.

Identification of a PXI-8420

Similar Messages

Maybe you are looking for