Changement de slot sur chassis PXI

Quelle est la procédure à suivre pour changer une carte sur un chassis PXI et que quand je redémarre le PC je voye que le slot de la carte a été changé.
Merci

Bonjour Lunik,
Je ne suis pas sûr de ce que tu veux, mais première chose : les cartes PXI ne se changent qu'à l'arrêt du chassis.
A ce moment-là, si tu changes le slot du 2 au 5 par exemple, au redémarrage, dans MAX, la carte apparaîtra sous PXI1Slot5. Il suffit alors de changer l'alias de la carte à sa valeur précédente en prenant soin de supprimer la carte "fantôme" PXI1Slot2.
Autre solution : exporter+importer la conffiguration du chassis (Fichier -> Importer/Exporter).
Cordialement,
Eric M. - Application Engineering Specialist
Certified LabVIEW Architect
Certified LabWindows™/CVI Developer

Similar Messages

How to change the battery in the PXI 1002 chassis

I need to change the battery inside the PXI 1002 chassis. How to do it?

Hello,
Where is the battery in the controller?
Thanks.
J. Frantz

Chassis PXI (question débutant)

Bonjour a tous,
Voila j'aurais une petite question concernant le développement d'application avec un chassis PXI.
Hbituellement pour la réalisation de mes banc de test, je controle des appareils "standard" mais la pour mon nouveau projet je me suis dit que j'allais passé par un chassis PXI-e.
Donc voila, je dispose d'un chassis PXIe-1071 équipé d'une carte scope, une carte géné et d'une matrice.
Comme je n'ai encore jamais travaillé avec ce type de matériel, je me demande quelle méthode appliquer pour développer mon application. Es ce que je dois installer l'abview directement sur le chassis PXI le temps du développement du soft et une fois le développement figé, créer un exécutable et désinstaller labview du chassis ou alors connecter mon chassis a mon PC habituel de labview et controler mon chassis a partir de celui ci? dans ce cas, serais je obligé d'installer les drivers de mes carte (scope, géné matrice) sur mon PC de développement habituel?
Ces question vont peute etre vous paraitres stupide mais comme je débute avec ce type de matériel j'aimerais avoir l'avis, la méthode de travail de personne plus expérimenté.
Merci d'avance pour vos réponses.
Résolu !
Accéder à la solution.

Salut,
As-tu un contrôleur dans ton chassis (dans le slot de gauche) ? Si oui, l'utiliseras-tu sous Windows, ou sous OS temps réel ?
Si tu l'utilises sous Windows, installe LabVIEW dessus, sans quoi, tu n'auras pas la possibilité de visualiser les variables avec des sondes d'observation.
Une fois ton projet finalisé, la license de développement n'est plus nécessaire. Tu pourras donc la supprimer, et te contenter du moteur d'exécution de LVet d'un exécutable
A+
Mathieu Steiner, Test System Engineer, Safran Engineering
CLD, ISTQB

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

How to determine what card is in what slot of a PXIe-1073 unit programmable

How can i programmable determine what card is in what slot of a PXIe-1073 unit I have a PXI-4063 and a PXI-2503 in a 1073 chassis. I use the DAQmx Device Product Type to to find the 2503 matrix card but it woun't return the 4065 product type.

Hi cjp1,
The KnowledgeBase article Programmtic PXI Slot Detection walks you through the steps to do this. There is also a community example called Read PXI an PXIe Card Serial Numbers Programatically that demonstrates the type of LabVIEW architecture you can use to do it.
You should first ensure that all of your modules can be identified and self-test in MAX.
In case the above hyperlinks don't work, you can copy-paste the addresses below:
http://digital.ni.com/public.nsf/allkb/2342900AED02975A86256BD800764C8B
https://decibel.ni.com/content/docs/DOC-20207
Jeff Munn
Applications Engineer
National Instruments

How to change a blade of chassis in safe mode

Hi there guys!
I'm triying to change a blade of chassis, but everytime that we make the change the OS into the blade its deleted; this is hapenning with all the blades that are trying to move. We don't have any Scrub policy applied.
Anyone has idea of what is happening?

Before removing a blade always run a decommision, even if you are going to use the same service profile:
Server - General - Server Maintenance.
When you insert it in another slot, it will run a re-acknowldge. If you are going to apply the same service profile with the local disk configuration that you mention, the data should stay there.
If the Protect Configuration box is checked, the server retains the configuration in the local disk configuration policy even if the server is disassociated from the service profile.
When a service profile is disassociated from a server and a new service profile associated, the setting for the Protect Configuration property in the new service profile takes precedence and overwrites the setting in the previous service profile.
Note
If you disassociate the server from a service profile with this option enabled and then associate it with a new service profile that includes a local disk configuration policy with different properties, the server returns a configuration mismatch error and the association fails.

Chassis PXI 1044 est connecté à mon PC : le PC ne boot plus !!

Bonjour,
Si je met sous tension mon chassis PXI (avec des cartes 4472B) et que je le connecte à mon PC via une liaison fibre optique : le PC bloque pendant le boot ( problème de configuration )
Si je ne connecte pas le chassis , le PC boot mais le PC ne reconnait plus le chassis !!
QuiZZZ?

Bonjour
Cdaubol,
Merci
d'avoir posté sur le forum National Instruments.
Est-ce que si tu démarre le châssis PXI sans la carte 4472 puis tu lance
ton PC tu observe le même comportement? Peux-tu nous indiquer les éléments de
l'ensemble de ton système (OS, version des drivers, pont MXI...).
Benjamin R.
R&D Software Development Manager
http://www.fluigent.com/

Impossible de changer ma CB sur itune car il est ecrit que le mode de paiment n'est pas valide. Or les coordonnes sont bonne, j'e suis passé d'un pc a un mac. C'est pour ça?

Impossible de changer ma CB sur itune car il est ecrit que le mode de paiment n'est pas valide. Or les coordonnes sont bonne, j'e suis passé d'un pc a un mac. C'est pour ça?

Non ça n'a rien à voir. Il se peut que ta banque ne permet pas d'ajouter ta CB, moi j'ai du passer un coup de fil à la mienne pour qu'ils me permettent d'afficher ma carte sur mon compte iTunes. Essaie voir si ça marche?

Bonjour, comment changer l'identifiant sur mon iphone, j'ai modifie mon identifiant sur itunes et je ne sais pas comme le faire sur mon mobile. merci pour la reponse, kikimtp

bonjour, comment changer l'identifiant sur mon iphone, j'ai modifie mon identifiant sur itunes et je ne sais pas comme le faire sur mon mobile. merci pour la reponse, kikimtp

thank you, I did not find the Apple ID "in store on the apple site? I thought I should make amanipulation on the iphone. I already changed my ID on apple, it worked but not on the iphone,there is always ncienne my email address. I use a translator so I do not know if my question is clear in English. thank you for the answer kikimtp

J'ai changé mon identifiant sur mon Mac, mais ne fonctionne pas sur mon iCloud toujours l'ancien

J’ai changé mon identifiant sur mon Mac, mais ne fonctionne pas sur mon iCloud, toujours l’ancien

thank you, I did not find the Apple ID "in store on the apple site? I thought I should make amanipulation on the iphone. I already changed my ID on apple, it worked but not on the iphone,there is always ncienne my email address. I use a translator so I do not know if my question is clear in English. thank you for the answer kikimtp

Changing PCI slots...of a card...?

If I load a driver it works fine. When i poweroff and change slot should I have to reload the driver.
Why is minor device getting created only at add_drv, even though the driver is loaded after change of slot only add_drv really does it.
Thanx in advance.

run
devfsadm -v -i name_of_your_driver
and the new device nodes for the adapter in the new pci slot
should be created (unless there are bug in the pci driver).

NiDMM IVI Error Converter Fails at launch after changing from PXI Chassis PXI-1042Q to PXI-1031. None of the congiguration setup parameters work so the VI won't work

I have changed a PXI system from the development system with a contoller PXI-1042Q to a PXI-1031 chasis using MMI-4 comunications with a XP based commputer. When I try to run my application none of the configutation files for niDMM load. the error I obtain is: "LabView Load error code 3 could not load front panel" Also niDMM IVI Error Converter.vi for Powerline Frequecny, auto zero, ADC calibration,Measurement Digits, offset comp Ohms, multi point, Meas complete dest, Meas complete slope, and fetch multipoint won't load.
Does anyone know what my problem is. I have made sure that the handles I am using in the software match the PXI chassis handles. When I search for the niDMM IVI Error Converter.vi I can't find it on either system.

Hi Foxy-
One thing to make sure is that the driver version on the new system is not older than the driver on the old system. Make sure you have at least the same versions between the two and all should load just fine.
I hope this helps. Let us know if you have any additional questions.
Gary P.
Applications Engineer
National Instruments
Visit ni.com/gettingstarted for step-by-step help in setting up your system.

I need help changing a VI from NI PXI-1042Q to USB-6210

Hello all. This is my first post, and I apologize ahead of time if it's in the wrong place or is inappropriate... I was instructed to come here for help.
I am working on changing a VI that is functioning perfectly with an NI PXI-1042Q over to a much smaller unit, the USB-6210. Supposedly the USB-6210 can handle the same inputs/outputs that I need (one analog input read at 30 kHz, 2 digital outputs written at 10 kHz), however I am having a bit of trouble getting it to work properly. The outputs seem to go where they are supposed to, but the new system is orders of magnitude slower than the original, and for the system I am using this is unacceptable.
I'm sure I'm doing something wrong, but I'm about as new to LabView as you can get so I have no idea where to start. Any help would be appreciated.
Additional info you might need:
LabVIEW 2010
The VI is attached.
Respectfully,
Emrys Maier
University of Texas at Arlington Research Institute
Research Assistant
Solved!
Go to Solution.
Attachments:
Need_to_work_on_USB-6210.vi ‏250 KB

one is using the PCI bus the other is using USB
(And probably has some power management problems and a 1.0 device on the hub)
A Quick link to USB FAQs- pay attention to FAQ2 1-3
USB Plug-n-Play Devices (Windows)
Options
Mark as New
Bookmark
Subscribe
Highlight
Print
Email to a Friend
Report to a Moderator
‎01-22-201202:20 PM
In this topic we will discuss some of the common problems that have been observed using USB devices with LabVIEW on Windows operating systems. Many of these points are also applicable to other environments but the examples will be use the Windows 7 OS.
FAQ 1 : My USB device stops working unexpectedly.
The first thing to look at is the OS power saving options. There is a global trend towards developing "Green" electronics and energy star ratings are getting fairly common. "If its not being used shut it off" is nothing new. Cavemen learned how to bank a fire to preserve energy that would otherwise be wasted. Likewise, the Windows OS has a power saving feature to shut down power to the USB hubs when no user activity is present. In Automated systems this feature can cause problems since removing USB hub power will shut down the USB device. Solution: Use the device manager to change the USB hub Power Options.
FAQ2: I set the power options and my device connection is still unreliable: Remember, those computer USB ports are often the cheapest that can be mounted on the chassis and share the PC system power supply to supply USB Power. Most uses of USB are temporary connections like a thumb drive or a camera. These connections do not require high reliability since the user is right there interacting with it. Power surges and fault tolerance at worst cause the operator to retry the data transfer. Automated systems require a bit more robustness. Solutions:
1) ALWAYS use an external self powered hub. Perform your engineering due diligence and inspect the devices specifications too- If you can't find them for that device that should clue you to seek an product from a vendor that WILL publish their specs.
2) High noise environments require the use of ferrites on the USB cable- and don't buy the cheapest cable either! The cheap ones are poorly shielded.
3) PROTECT the HUB connections- If you have a USB2.0 device and Joe User plugs in a 1.0 device in a open slot managed by the same hub- Bingo every port on the hub may back convert to USB1.0. WORSE there are a lot of damaged or marginally engineered USB devices out there. Joe User's device may cause power fluctuations when it is inserted or removed from the hub just don't let it happen!
FAQ3: I am testing USB devices and the OS can't find them anymore.
This is a Plug-n-Play feature that deserves some exposure. When you connect a P-n-P device the OS remembers its serial number in a HKEY (Hive-Key) registry entry. This is helpful when (for example) you want a specific instrument, Say an NI-USB-6008, to show up as a DAQmx Device with VISA Alias "MyDAQ1" every time it is plugged it. On the other hand, If you want to test a line of USB-Serial converters this can be problematic since the P-n-P driver will mount the first serial number as "COM3" and the next as "COM4" add infinitum until the enumerator controller in the registry and VISA recognized aliases get used up. Solution: Use the Windows registry API and the Hardware Configuration API in LabVIEW to clear unused VISA Aliases and HKEY entries. Speak with your staff IT professional about HKEY structure and possible side effects before developing a plan to edit registry entries.
Jeff

Advice on arranging modules in a 2-chassis PXIe system

Hello,
System contents
We have a system that consists of:
2 PXIe-1085 chasses, connected via a PXIe-8384/PXIe-8360
15 FlexRIO cards (PXIe-7962R + NI-5734), to acquire data at 10 MHz
1 function generator (PXIe-5412)
1 timing card (PXIe-6672)
Other cards (switches and low-speed I/O)
Use cases
In one mode of operation, we need 60 FlexRIO channels to listen at all times. When any one channel exceeds the threshold, all 60 channels must be simultaneously acquired and logged to disk (i.e. every FlexRIO card must be able to trigger acquisition in in all 15 cards)
In the other mode of operation, we need to generate a pulse from the PXIe-5412, and simultaneously acquire from all 60 FlexRIO channels from the instant the pulse fires.
Question
Essentially, we have 17 timing-sensitive cards (15 FlexRIOs + 1 function generator + 1 timing card), but only 16 cards can fit in one chassis (because 2 slots are ocupied by the embedded controller and the MXI-Exprress card). So, one of these need to be on the other chassis. The two obvious options then are:
FlexRIOs plus the function generator on the 1st chassis, timing card on the 2nd chassis.
FlexRIOs plus the timing card on the 1st chassis, function generator on the 2nd chassis.
Does it matter which option we go for? Do we get any performance benefits and/or ease of coding either way?
Thanks in advance!
Solved!
Go to Solution.

If all you care about it the clock accuracy, there is an input on the back of the PXIe-1085 for an external 10MHz clock and an output of the 10MHz clock. So everybody can use the same clock.
But you care more about triggering. So I see two real options:
1. Put everything that must trigger each other in the same chassis. This would mean putting the timing source in the second chassis and using the reference clock I/O on the chassis to share clocks.
2. Get a second timing module. The module should have PFI lines so that you can share trigger signals. I would still use the refernce clock I/O on the chassis just to make sure everybody is using the same clock.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Programmatically get the PXI slot that the PXI-4070 (DMM) is in?

I am looking for a way to find out what slot my DMM's are in and their model and S/N.
So far I have been able to get back the info for NI-Switch devices, DAQs and a range of Pickering Cards.
For the NI-DMM’s I have so far only been able to get the S/N model and name via the IVI Drivers.
I have attached the code I have so far so you can get a better idea of what I am trying to achieve.
Solved!
Go to Solution.
Attachments:
Get PXI Card ID.vi ‏29 KB

Use "niModInst Open Installed Devices Session" for NI-DMM
Then use "niModinst Get Installed Device Attribute" to get the slot number
Returns an integer attribute specified by the attribute ID parameter for a device specified by the session in and index in parameters.
Valid Values
Slot Number—the slot (for example, in a PXI chassis) in which the device is installed. This attribute can only be queried for PXI devices installed in a chassis that has been properly identified in MAX.
Chassis Number—the number of the chassis in which the device is installed. This attribute can only be queried for PXI devices installed in a chassis that has been properly identified in MAX.
Bus Number—the bus on which the device has been enumerated.
Socket Number—the socket number on which the device has been enumerated.
Omar

Changement de slot sur chassis PXI

Similar Messages

Maybe you are looking for