Why do multiple PXI modules in a chassis cause my PC to continually reset?

I have a PXI-1000 connected to my desktop PC via a MXI-3 interface. When I plug more than a couple of PXI modules into the chassis and switch on, my PC continually resets itself. Any idea what is wrong?

Dear Darren,
This sounds like there is a problem with your chassis supplying the power required for all of your PXI modules. This could indicate either a problem with the power supply on the chassis itself, a problem with the PXI backplane being shorted, or a problem with one or more of your modules. If possible, I recommend testing this system with a different PXI chassis.
If a second chassis works, then we know the problem is with the first chassis. In this case, I recommend checking for bent pins on the backplane. You can also send it in for repair.
If the second chassis does not work, then we know the problem probably is not with the chassis. I recommend testing each card. One of your modules could be shorting the backplane. I recommend testing the s
ystem with each module one at a time. Place each module in each slot in the chassis to see if any combination of modules and slots makes a difference. Once you verify that each module works, you can then test to see if a certain combination of modules causes the problem. The goal here is to determine which module or modules is causing the problem. We need to find out which module is either shorting out the backplane or is drawing too much power.
This could also be a problem with the MXI-3 connection or the PC. I recommend testing this system with a different PC. You may also consider upgrading your PC's BIOS.
If you want to send in your chassis or PXI modules for repair, you will need to call in. In this case, go to http://www.ni.com/support and generate a phone support request.
Regards,
David Shatila
Applications Engineer
National Instruments

Similar Messages

Simultaneously triggered acquisition: Multiple PXIe-7962R + NI-5734 cards, across multiple PXIe-1085 chasses

Hi all,
I need to do high-frequency, high-channel-count acquisition.
Specs
Signals: 10 MHz, 60 channels
Controller: PXIe-8135 (Windows 7)
Chasses: PXIe-1085 (2x)
Input cards: PXIe-7962R FlexRIO base with NI-5734 digitizer (15x)
Description
Each FlexRIO card will store data in circular buffers, and continuously monitor the voltage levels. When any one channel exceeds the user-defined threshold, all 60 channels need to be triggered simultaneously to pass waveform data (200 μs pre-trigger, 300 μs post-trigger) to the host OS for logging.
In other words, every FlexRIO card needs the ability to fire the trigger, which is then received by all 15 FlexRIO cards (the card that fires the trigger also needs to receive the trigger).
Question
Can I achieve this with only a single PFI line? Or do I need some other technique?
I've found some examples, but they only show single-source and single-card triggering, e.g. https://decibel.ni.com/content/docs/DOC-30182 uses one analogue input to trigger the acquisition of 2 channels on the same card.
Any advice would be much appreciated. Thanks!

Assuming you are using LV 2013 or 2014 you should download version 1.3.4 of the FlexRIO Instrument Development Library (FIDL). This will install 5734 Acquisition Engine examples which use the MultiRecord Library to stream data to the DRAM in a circular buffer, allowing you to recover pre-trigger samples. The example also demonstrate how to implement the Syncrhonization Library that synchronizes triggered acquisition to within a single sample period across multiple devices.
Getting the example to work across two chassis' may be difficult, but I believe it is possible. Though to do so you will need a timing and sync module in each chassis to distribute the triggers and reference clock that the sycnrhonization library requires.
National Instruments
FlexRIO Product Support Engineer

Communicating with modules in PXI-1042 via MXI-3 interface, all I get is PXI0::MEMACC appearing in MAX. I have OEM modules in the chassis, should these be displayed?

I have a PXI-1042 with PXI-MXI-3 interface kit. In the chassis I have inserted an OEM PXI module. When I run MAX, all I see is PXI System->PXI Bus 0->PXI0::MEMACC. Is this correct? How do I see the other modules?

Darren,
The only PXI modules that show up under the PXI System option in MAX are those cards that are registered with NI-PAL or NI-VISA. For 3rd party cards, it depends on how their particular driver functions. If the vendor creates their drivers based on NI-VISA, then the device will show up in MAX.
If the vendor created a Windows-specific driver, then there is no way that NI-VISA can find any information on the device, nor can it communicate with it. An example of this is a CompactPCI SCSI or Ethernet card, which is supported by a driver that is native to Windows. NI-VISA does not detect such devices.
It is important that you contact the manufacturer of your 3rd party modules and find out if they are NI-VISA complient devices.
Regards,
Andrew Mier
au
Applications Engineer
National Instruments

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

Multiple output modules cause render to fail?

Is anybody else having trouble with using multiple output modules in after effects? Let me elaborate: so I'm working on a 3d film, and my worflow is to simply work with the footage side by side in a single comp (we're at HD, so the comp size is 3840x1080). Very often, I need to fire off a quick render to show to the director. Most of the time, I just do the left eye by cropping to that 1920x1080 area in the output module. Other times I need to deliver both eyes, so instead of cropping to 1920x1080, I resize the frame in the output module to 1920x1080. Yea, we lose half of our horizontal resolution, but that's not such a big deal for us when just working on approvals.
Here's the thing: sometimes I like to export multiple variations of this at once (ie one output module for the left eye, one for the right eye, and another for the squished side-by-side left-right video). Whenever I try to output multiple modules with quicktime, it fails. Every time.
When it fails, I get two messages: the first (a warning) says "After Effects warning: last frame was written to one or more output modules, but not all! ( 26 :: 153 )"
The second message (an error) shows up once for each output module: "After Effects error: Rendering error while writing to file "C:\blahh blah blah\whereIputmyfiles\the_render.mov". An output module failed. The file may be damaged or corrupted. (-1610153464)." Once it fails, I cannot output to quicktime AT ALL (multiple output modules, or not) without restarting After Effects.
I tried outputting multiple modules as a PNG sequence... and that worked just fine (if "slow as hell" can ever be called "fine" .... but it worked! )
I tried outputting to the multiple formats I wanted with one output module per render item (rather than having one render item with multiple modules) as quicktime, and that worked just fine (of course... it takes N times as long though... for N number of outputs).
I am on Windows 7 64-bit... running After Effects CC 2014... I never had this trouble back when I was working on the CC version (the not 2014 cc version... that is too confusing...). However, I just went back and tried it with the older version, and it no longer works there either! What gives?
When outputting quicktime, I'm using the h.264 codec.
And before anybody suggests it, no I can't just use AME because that can't resize video (it forces you to keep the aspect ratio through letterboxing) or crop video.

>The most likely culprit is the h.264 Quicktime. It should have never been included as an option. It doesn't even work well in Quicktime Pro or in Final Cut...
I'll come to Apple's (partial) defense here:
Their H.264 codec was written and released at a time when it was difficult to imagine that mainstream computers would have as many CPUs as they do now, so it's somewhat understandable that the severe failures that this codec has with large numbers of threads occurs. Of course, we may all wish that Apple hadn't decided to end development on the QuickTime platform, since this has meant that bugs like this are likely to persist.
That said, this is why we increasingly recommend that people use other H.264 codecs and not use QuickTime for such things. See the H.264 options currently in Adobe Media Encoder.

Why the multiple selection can't work in sub screen

hi experts:
     when i try to use the sub-screen in the report,why the multiple selection function(SO_BCTXT) can't work normally in screen 1095:
the coding as below.will reward points if solve this issue
the main program in Subscreen:
PROCESS BEFORE OUTPUT.
module status_1005.
CALL SUBSCREEN area INCLUDING sy-repid lv_tab_number.
PROCESS AFTER INPUT.
MODULE cancel AT EXIT-COMMAND.
CALL SUBSCREEN area.
MODULE user_command_1005.
module user_command_1005 input.
my_ok = ok_code.
clear ok_code.
case my_ok.
    when 'TAB1'.
      mytabstrip-activetab = my_ok .
      lv_tab_number = 1095.
    when 'TAB2'.
      mytabstrip-activetab = my_ok .
      lv_tab_number = 1096.
    when 'CRET' or 'ONLI'.
      perform get_bc_set
             using
                so_chanb[]
             changing
                <fs_bcsetfield> .
      leave to screen 0.
endcase.
endmodule.
in the screen 1095:
PROCESS BEFORE OUTPUT.
MODULE %_INIT_PBO_J.
MODULE %_PBO_REPORT.
MODULE %_PF_STATUS.
MODULE %_SO_BCTXT.
MODULE %_END_OF_PBO.
PROCESS AFTER INPUT.
MODULE %_INIT_PAI_J.
CHAIN.
FIELD SO_BCTXT-LOW.
FIELD SO_BCTXT-HIGH.
MODULE %_SO_BCTXT.
ENDCHAIN.
FIELD !INCBCTY1 MODULE %_INCBCTY1 .
FIELD !INCBCTY2 MODULE %_INCBCTY2 .
FIELD !INCBCTY3 MODULE %_INCBCTY3 .
FIELD !INCBACT MODULE %_INCBACT .
FIELD !INCBINAC MODULE %_INCBINAC .
FIELD !INCLMAND MODULE %_INCLMAND .
FIELD !INCLOPTI MODULE %_INCLOPTI .
CHAIN.
FIELD SO_BCTXT-LOW.
FIELD SO_BCTXT-HIGH.
FIELD INCBCTY1 .
FIELD INCBCTY2 .
FIELD INCBCTY3 .
FIELD INCBACT .
FIELD INCBINAC .
FIELD INCLMAND .
FIELD INCLOPTI .
MODULE %_BLOCK_1095001.
ENDCHAIN.
CHAIN.
FIELD SO_BCTXT-LOW.
FIELD SO_BCTXT-HIGH.
FIELD INCBCTY1 .
FIELD INCBCTY2 .
FIELD INCBCTY3 .
FIELD INCBACT .
FIELD INCBINAC .
FIELD INCLMAND .
FIELD INCLOPTI .
MODULE %_END_OF_SCREEN.
MODULE %_OK_CODE_1000.
ENDCHAIN.
in the main report
selection-screen begin of screen 1095 as subscreen.
enquire Data
data l_text       type as4text.
selection-screen begin of block b1 with frame title text-024.
select-options :
so_bctxt     for l_text .
selection-screen skip 1 .
parameters:
incbcty1    type c as checkbox default abap_true ,
incbcty2    type c as checkbox default abap_true ,
incbcty3    type c as checkbox default abap_true .
selection-screen skip 1 .
parameters:
incbact      type c as checkbox default abap_true ,
incbinac     type c as checkbox default abap_true .
selection-screen skip 1 .
parameters:
inclmand     type c as checkbox default abap_true ,
inclopti     type c as checkbox default abap_true .
selection-screen end of block b1.
selection-screen end of screen 1095 .

Hiii
    In main program you have dclared subscreen area.
now First of all you have to declare a selection screen in your main program
selection-screen begin of screen 1005 as subscreen.
SELECT-OPTIONS s_bukrs1 for v_bukrs.   "whatever you want in selection screen
selection-screen end of screen 1005.
IN PBO of your main screen (not in 1005) write
call subscreen SUB1 including sy-repid '1005'.
where SUB1 is your subscreen area name. And remember don't touch PBO or PAI of your 1005 screen, otherwise it will give you error. Yuo can just put text in layout of 1005 screen. but don't disturb other things.

Question about multiple application modules.

Hello,
Suppose I have 2 database schema’s. For both schemas I have 1 application module. All view objects are in the same project.
For each application module I have an application definition.
Is it possible to link between these two applications? Because sometimes these database schema’s link to each other and you would like to jump from one application directly to the other.
For example you have orders locates in 1 DB schema and customers in another DB schema.
You would want to jump from the order directly to the customer details in the second schema.
Is this possible? Or do I need to make nested application modules etc?
I can find very little info about this; the JHS def guide does not offer much information about multiple application modules etc.
-Anton

Anton,
Yes, you can jump aroundd as you like.
You just can't use view links between VO's based on different db schema tables.
Nesting AM's doesn't help there, the DB connection of the top-level AM will be used.
Why don't you create synomyms for the tables in the other schema?
Steven Davelaar,
JHeadstart Team.

Release date for PXIe Modules

I had a couple of questions about PXIe:
1) I see that a controller and chassis have been released, when will Digitizers and DAQ cards be released?
2) It is my understanding that a PXI card that is plugged into the PXIe
chassis will work, but NOT receive the 1GB/s bandwidth, is this
true? In other words, PXI cards do not get the bandwidth upgrade,
just PXIe cards.
3) I saw in the PXIe tutorial that PXI cards can be sent in and the J2
pin port will be replaced to make it into a PXIe hybrid card.
Would this card gain the benefit of the 1GB/s bus speed?
Thank you in advance,
Austin McElroy

I'll answer your last two questions:
>>It is my understanding that a PXI card that is plugged into the PXIe
chassis will work, but NOT receive the 1GB/s bandwidth, is this
true? In other words, PXI cards do not get the bandwidth upgrade,
just PXIe cards.
There are different types of slots in PXI Express chassis. A PXI card can be plugged into a hybrid slot or a PXI slot. A PXI slot can only accept a PXI card. A hybrid slot can accept a PXI card or a PXI Express card. In order to insert a PXI card into a hybrid slot, it must have the J2 connector replaced as you stated. Some PXI cards do not have a J2 connector and these need no modification.
PXI and PXI Express cards use different types of busses to connect to the system. PXI cards use only the PXI (PCI) bus while PXI Express cards use a PCI Express link. Electrically, the two busses are not compatible or interchangeable. Hybrid slots support both busses, but a card only uses one or the other. The bandwidth available to a PXI card does not increase if it is plugged into a hybrid slot as the PXI card will only use the PXI bus, not the PXI Express bus.
>>I saw in the PXIe tutorial that PXI cards can be sent in and the J2
pin port will be replaced to make it into a PXIe hybrid card.
Would this card gain the benefit of the 1GB/s bus speed?
No, this card still connects using the PXI (PCI) bus. The PXI Express bus in the hybrid slot will not be connected to the PXI card. The PXI card will not be able to access the bandwidth provided by the PXI Express bus.
This is a subtle point, but a PXI card that has been modified to work in a PXI Express hybrid slot is known as a "hybrid slot-compatible PXI module". A "PXIe hybrid card" seems to imply a card that uses both the PXI Express and PXI busses. I doubt such a card would ever be designed.

Fan module failures in chassis

I have two chassis almost fully populated with B200M2 blades with the cahssis cabled up to 2 6120xp fabric interconnects. I'm continually getting Fan Modules in both chassis's saying that they are degraded because a fan is inoperable. This happens about 20 times a day. They clear themselves almost immediately, but I'm wondering why this is occurring. If it was normal operation for the fans to stop working than these shouldn't be faults. Has anybody else experienced this?

Will be hard to diagnose without tech-support files, but the defect they are probably referring to is this one.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl43716
There are some workarounds for this in the defect description.
There are also still working to fix this defect in 1.4.

One task control multiple DAQ modules

Is it possible to have one task control 2 or 3 DAQ modules? I do not seem to have luck in doing so.
Also, for a digital output NI device that sources voltage, if I hook up 10v to it and the module has 10 channels, how on earth are the 10 channels each able to source 10V, when I only supply one 10v power supply.
Does it just send extremely small amounts of current per channel versus sending a decent amount of current per channel if I just had one output on?

Hey all,
This is a crosspost, I posted somewhere else after posting this post, just because I did not know whether I posted in the right place, here is the link to the other in case anyone else comes across this problem: http://forums.ni.com/t5/Multifunction-DAQ/one-task-control-multiple-DAQ-modules/td-p/3170766 Sorry about that.
Anyways, I have
NI 9401,
NI 9403,
NI 9474,
NI 9375,
I am using a
NI cDAQ-9184 chassis
I believe these are all compactDAQ.
I would like to combine the 9401 and 9403 into 1 task, and the 9474 and 9375 into 1 task.
Also, I am having issues with one of the modules, the 9375. When I wire False data to the Write DAQ on LabVIEW it seems that the 9375 is still sourcing some voltage. I cannot remember the difference in voltage of then I wire true data versus false, But I believe they were somewhat close. Has anyone came across a problem like such?

PXI Module Information Scan

Hi,
I'm planning to develop a labview program thats scans information from all PXI module present in the chassis(like calibration dates, module description, etc..). Need some advice which Labview VI is capable of scanning above mentioned information wherein output is in "string" so that I could
manipulate it in the labview program itself. As I scan for VI, one option I see is the "MAX Generate Report", but results are in html or xml(plus my PXI
hangs when I use this function).
Appreciate any inputs on this.
Thanks,
Versil1
Solved!
Go to Solution.

Hi Versil1,
I would recommend using niModInst, DAQmx device node, and DAQmx system node. Examples for how to use those functions can be found here:
niModInst: Programmatically Query Device Name or Other Information Using NI-ModInst API http://decibel.ni.com/content/docs/DOC-7454
DAQmx device and system node: Programmatically Get DAQ Device Product Names http://decibel.ni.com/content/docs/DOC-3716
For outputs that are not in string format (i.e. DevNames), you can use the flatten to string function to convert them to strings.
Regards,
Andrew M.
Applications Engineer
National Instruments

How to keep multiple function modules under one Web service

Hi Experts,
I have Three RFC function modules and i need to create one web service for these three RFC function modules. I know How to crearte a web service for one function module.
please suggest me How to keep multiple function modules under one Web service.
Thanks in advance
Lakshminarayana

Hi Lakshmi,
The best way to do it is to assign all the three RFC Enabled FM's to one function group. Later on the top menu in Utilities you get an option to Create a Webservice from a Function Group.
You can create one single Webservice using all the the 3 FM's.
I hope this helps.
Thanks,
Manu

Direct connect to my PXI module

Hi,
my problem is, that I don´t know how I can direct "speak" whit my PXI module.
I need some information about revisions-number and so on...
whit the DAQ I can find serial-number and device-type, but I need some specific informations.
If I look to GPIB ther are the kommand "*IDN?". Is ther some way to connect my PXI module like GPIB? Or with VISA?
My application (in CVI) must read some information about the actual PXI system. I can´t use drivers from a specific module, then I don´t know what modul are in the system.
I hope someone can help me

You will be able to the get this information using the VISA Driver Development Wizard. You can read more about this tool at the following link:
http://zone.ni.com/devzone/conceptd.nsf/webmain/ADF3152837E2B4A486256B5600642AC7?opendocument
This document explains in detail the process required.

How to use the Keying of CompactPCI in my own designed PXI-module?

as title.
I've designed a own PXI-module.Since I havn't seen the CompactPCI Keying in J1 before, I don't know how to use it, or it is just necessary for special application field?

Hello,
Please refer to the link below, I think it will have all of the information that you need concerning keying of CompactPCI and PXI modules:
http://digital.ni.com/public.nsf/websearch/98907157CE1428A286256BC900607485?OpenDocument
Regards,
Andrew Mierau
Applications Engineer
National Instruments

Multiple ejb modules

Welcome evry body, i need your help since i am new to ejb technology.
I have a J2EE application with multiple ejb modules, my problem is how to
make ejb1 located in ejb-module1 instantiate ejb2 located in ejb-module2
in my ejb-module1 ejb-jar.xml deployment descriptor i put this :
<session>
   <ejb-name>ejb1</ejb-name>
   <local-home>....</local-home>
   <local>...</local>
   <ejb-local-ref>
        <ejb-ref-name>ejb/ejb2</ejb-ref-name>
        <ejb-ref-type>Entity</ejb-ref-type>
        <local-home>....</local-home>
        <local>...</local>
        <ejb-link>ejb-module2.jar#ejb2</ejb-link>
   </ejb-local-ref>
</session>When i deploy my application and try to access it i get this exception :
javax.naming.NamingException: No EJB found at location 'ejb-module2.jar_ejb2'So is there any way to fix this problem?

Hi Javist,
Assuming you've double-checked that the target module(ejb-module2.jar) and
target ejb-name (ejb2) are correct, and that both ejb-jars are packaged at the same level in the .ear, everything looks fine to me. Which J2EE implementation are you using? It's possible it's a bug. You can also try the shorthand of just
<ejb-link>ejb2</ejb-link>
If there's only one ejb with that name in the entire .ear, that should work even without the explicit ejb-jar path reference.
--ken

Why do multiple PXI modules in a chassis cause my PC to continuall​y reset?

Similar Messages

Maybe you are looking for

Why do multiple PXI modules in a chassis cause my PC to continually reset?