Chassis PXI MXI timeout



Tags: NI Hardware

Similar Questions

  • Is it possible to route signals of relaxation between two chassis PXI-1002 with the PXI-8335?

    Hello

    as the subject says, I am interested in the delivery of a signal to trigger between two chassis PXI-1002. At present, these two chassis are connected by a MXI - 3 system using maps PXI-8335. The software is Labview 2010 sp1 and 380 NIScope drivers.

    We want to keep (a PXI-5122 by chassis) scanners supply separated due to the requirements of our measure! The chassis are connected via cable to fiber optic. This explains why I can not just use the shutter release in Star, or connect via 'Trigger' or 'clk' cards (the inputs / outputs to the front of the cards).

    I found a few examples, but they seem to all be designed for use with a chassis only, I'll call later to the examples that inspired me to this point. Each guide explaining the synchronization of several chassis systems seems to use another material or VI is not accesible to me. This makes me wonder if my hardware has the capacibilities I need.

    The first picture shows approximately where I started from (sorry I can't post VI, confidential...):

    Only the middle part is interesting. Two sessions are initialized and manipulated parallel, trigger too. This has led to delays in the signals and should now be fixed. This apart from the VI works fine.

    Goal is to trigger only on one channel but both devices! If possible, the device will trigger must be chooseable.

    I started to rebuild the VI using the "EX Synchronization.vi 5xxx niScope' seeming spontaneity. The result is shown in the following image:

    I tried different RTSI lines, but had no positive results. only the main channel has triggered.

    After this first approach, I looked in the "niScope EX .vi multi-Device configured Acquisition (TClk)" and other examples of TClk which seem to work for similar problems. The VI of reconstruction can be seen in the following images:

    (Sorry, I had to use two photos..)

    In this case, I didn't have no choice for trigger lines, it would automatically set the VI TClk. I tried to trigger on both devices, though. This second approach seemed promising to me, but it was an error:

    "niTClk Synchronize.vi:1".

    Index (starting at zero) of the session: 1

    The error reported by the pilot of the instrument:

    No registered trigger could be found between the
    devices on the route.

    If you have a PXI chassis, the chassis correctly identify in
    MAX and make sure that it has been configured correctly. If you use PCI
    devices, make sure they are connected with a RTSI cable and that the cable RTSI
    is saved to the MAX. Otherwise, make sure that there is an available trigger line
    the trigger bus shared between devices.

    Source device: PXI1Slot4

    Target unit: PXI2Slot4

    Status code:-89125niTClk Synchronize.vi:1

    Index (starting at zero) of the session: 1

    The error reported by the pilot of the instrument:

    No registered trigger could be found between the
    devices on the route.

    If you have a PXI chassis, the chassis correctly identify in
    MAX and make sure that it has been configured correctly. If you use PCI
    devices, make sure they are connected with a RTSI cable and that the cable RTSI
    is saved to the MAX. Otherwise, make sure that there is an available trigger line
    the trigger bus shared between devices.

    Source device: PXI1Slot4

    Target unit: PXI2Slot4

    "Status code:-89125"

    This error came back even after I've identified this drug as possible to the MAX, as shown in the screenshot:

    In some of the textbooks, they showed how to get the MAX trigger lines, but as you can see, there is only booking options in my MAX. Whatever I do, I can't find options to define how to get my trigger signals...

    In principle, it is possible to trigger instruments in different chassis, which is indicated in this Guide and others... the question that remains is can it be done with my set of components?

    I understand that the use of multichassis compromised the integrity of the lines very adjusted as trigger in Star etc., so the configuration should be taken into account in some way, that my approach does not, I knew... But there must be a way to do this? And to start: to get just any signal from one device to the other trigger!

    For any advice on this issue, I would be very thanfull!

    Concerning

    Max1744

    Hi Max,.

    Thanks for the detailed post and explanations of your application and requirements. You're right using TClk, because this is the optimal method to synchronize the 5122 digitizers. The original VI you worked with is unique for some of the legacy scanners and does not directly work with scanners based on the most recent CMS (for example the 5122). The good news is that you can synchronize these cards to separate chassis, but it will use the calendar 66xx and synchronization (T & S) cards in the chassis of the master and the slave, as indicated in the guide that you have accessed. These are needed because a common reference clock must be shared between them as well as a couple of tripping. MXI itself can not handle export triggers and clocks, so there is no way to do this without physically wiring between the chassis with cards T & S. Unfortunately, regardless of what specific method, you use for synchronization, it will take a material extra beyond what you currently have.

    As one of your needs looks like it is necessary to retain wiring between the chassis directly, you may need to consider to synchronize using 1588 or GPS protocols. 1588 Protocol is a system for synchronization on the network while GPS course use antennas and locks for a common wireless signal. Although these synchronization methods may allow you to keep your chassis isolated, they will also require some manual configuration because you would be able to use the TClk synchronization and so the level of synchronization you can get between the cards may not be as good that can physically wire signals between the chassis using T & S cards.

    Hope this helps,

  • S/W-chassis PXI RTOS by MAX load

    I have a chassis PXI with LAbview 2016 RT OS on it with Windows 7. When turn the PXI chassis, I get a message that "no software is installed. When I try to intall software via MAX from a remote computer, I get the following message. Can someone tell me what this means? If I have to install the software locally (IE bunch the PXI chassis in WIndows), where can I install the software (C:\ drive, which Windows or the drive D:\, which has the RT operating system on him)?

    Bob,

    Thanks for the help.

    In the end, had to reformat the drive controller and who took care of the issue.

  • 1010 chassis PXI-6052E. to access the unused channels to HAVE

    Hello people,

    I have a 1010 (combo PXI/SCXI) chassis with a PXI-6052E installed in slot 8.  The 6052E connector is connected to a terminal block of 68 pins.  If I use the mulitplexed mode scxi modules, can I use the other 6052E analog inputs to measure other signals?

    I saw documents to direct wiring to a chassis scxi "separated" directly connected to a data acquisition card, but I have not found no information on the chassis of 1010 and the availability of channels daq (probably) not used.

    All documentation regarding this would be greatly appreciated!

    Best regards

    Chris


  • Looking for a replacement of a copper PXI MXI - 4 lost PCI cable, a 1:1 cable RS232 work?

    Hi all

    is anyone able to help me out of this misery?

    Thank you very much!
    Jürgen

    Hello Juergen,

    Unfortunately you cannot substitute an RS-232 cable instead of the standard MXI-4 cable.  While both use a DB-9 connector, the pinout of each cable is different.  Even if you were to manually change a standard serial cable, that you could have interference problems of noise due to the higher frequency MXI-4 compared to the RS-232 signaling.

  • Can I connect a link more MXI for PXI-1033 card in order to work with it

    Ladies and gentlemen,

    Tell me please that I can plug a card of MXI link more in the PXI-1033 chassis in order to work with it.

    In other words, I don't use the built-in controller for MXI and want to work with the NI PXI-8366 MXI-Express and PXI-1033.

    Thank you.

    The answer to your question is no. The question that must be taken into consideration is the type of housing, we have access to on the PXI-1033. To use a PXI MXI card for control purposes in a PXI system, we need to use the card in a slot of system controller (denoted by a triangle around the number of slots on the chassis). With the 1033 however, we have no access to slots control. Because of the connection of controller MXI incorporated, we only have access to a calendar/trigger and devices slots.

    Is there a particular reason you don't want to use on the 1033 MXI connection, or you just want to avoid having to change the connection to another computer?  Single MXI cards which would depend on the space available on the PXI-1033 would be something along the lines of the 8367 and 8367, who are used to the Garland of a separate chassis.

  • PXI-1045 chassis with controller PXI-8110 failed to boot RT LabVIEW 8.6 when the device inserted to any Slot13-17

    Hello

    Please see the attached photos.

    failed.jpg showed that the system could not start when a device is slot in slot13

    OK.jpg showed that the system is properly start. No device is inserted between slot13 to slot17.

    1. place a PXI (PXI-8433/4, PXI-8250) to any location 13-17 chassis will cause LabVIEW RT 8.6 could not start.

    2. remove the brackets slot PXI 6-10, place the device from PXI to slot 6 slot 13 is originally from LabVIEW RT 8.6 could not start.

    Help is appreciated. Thanks in advance.

    Failed:

    Ok:

    Thank you.

    BR, engwei

    Hello

    Tested with kit card PXI MXI - Express 8360. 13-17 still doen't work location. So I suspect something wrong with the chassis.

    Contact FOR support.

    BR, engwei.

  • PXI-8360 (MXI-Express) PCI-8361 + Dell OptiPlex 9020 = "device cannot start." (Code 10) »

    Hello

    I have a chassis PXI-1050, conencted to a Dell OptiPlex 9020 via a PXI-8360 and a PCI-8361 (identified as 199392B - 01L). It is Windows 7 64-bit. I can't start Windows very well, but MAX can't see all my PXI hardware. The Device Manager has also 2 inputs "PCI standard PCI to PCI bridge" with exclamation points.

    I placed an old FireWire PCI card in the same dwelling and recognized PC. Thus, the slot went very well.

    I transferred the PCI-8361 to an old PC that contains older drivers, and he acknowledged all my PXI hardware. For example, PXI gear works fine.

    What could be the problem? Here's a screenshot of my software OR installed. I think I installed all the drivers I need. I checked NI Update Service; There is no update of Critcal, and only updates and Service Packs listed are 2013 LabVIEW and TestStand 2013.

    JKSH,

    I look in that little bit more and think that I now know enough to be dangerous.

    The BIOS allows the PCI Express native control mode in Windows.  PCIe natively do not like some of the architecture when you use the PCI card version, so it disables the bridges on the PXI card.  I can tell that your OS is PCIe natively because it lists one of the ports as "PCI standard PCI Express to PCI/PCI-X bridge" Device Manager like you posted.

    I found that you can disable PCIe native mode, if you want to try it (but in general using the card PCIe is a better option).  Here are the steps:

    -Open the start menu and type "cmd" in the search box; Right click on "cmd.exe" and run as administrator.

    -In the command window, type "bcdedit/set pciexpress forcedisable.

    -Reboot.

    I don't think it would break anything (it doesn't have on a system I've tried).  If you want to reverse the trend, the command is ' bcdedit/set pciexpress by default'

    -Robert

  • Computer will turn off when the PXI chassis is turned off

    Hello

    I realized that my computer is shut down properly if I disable my chassis PXI-1036, until the computer is turned off. Is this a normal behaivour?

    As I remember, the chassis PXI-1036 must be turned on until the computer is power on, and I think that maybe on turn it off I have to follow the same procedure.

    Thanks a lot for your advice,

    Hector

    The chassis must be on anytime on the PC is.  Then it turn on before the PC and turn it off after the PC.

    This is because the chassis is an extension of the PC's PCI bus, so he expects everything to be available all the time the PC is powered on, as would be a PCI expansion card.

    -Robert

  • PXI-8115 controller incompatible with the PXI-1050 chassis?

    I replaced two XP based PXI controllers with two controllers, PXI-8115 with WIN7 installed on them. System #1 has combined PXI-1010 chassis and System #2 has a combo chassis PXI-1050 chassis. The two 8115 controllers work correctly when it is installed in the #1 system (chassis 1010) do not produce but no video output when it is installed in the #2 system (chassis 1050). I use the same monitor on both systems, as well as the same adapter DisplayPort to VGA supplied with controllers. This suggests some kind of incompatibility between the 8115 and the 1050, but I can't believe I'm the first to connect a 8115 a 1050. Everyone knows about this problem? Y at - it solution or workaround? Is there something I forgot?

    Thank you

    PMAC

    OK, I found a solution but I still don't know why it is the solution.

    Each controller had a "Bizlink" adapter DisplayPort to VGA bundled with it. Of course, I tried two adapters with the same results on both systems. I tried a "Startech" DP to VGA that is used elsewhere in the installation and the system worked well. Why a brand different adapter works is quite confusing.

    For anyone else having this problem try Startech manufacturer DP2VGA.

    PMAC

  • Modules in the PXI-1033 chassis detection problem

    Hello

    I met difficulties in operating my PXI-1033, which installed two strips of XIA Pixie-4. Until recently the system was working properly, but now I am unable to detect and use modules using software of XIA, although according to Windows both modules are "working properly". Nothing has changed between the time it was working and now (that I know)!

    I suspect the problem involves the chassis, since when I place a module in slot 6, the chassis will not be powered. It will power-up with any other occupied housing.

    Any help would be appreciated.

    See you soon.

    Hello jnod,

    At these modules never appear in measurement and Automation Explorer (MAX), if so they appear actually now?

    Also if you have other material, I'd be interested to know if the PXI chassis will start when you have a module IN slot 6.

    The chassis won't start when either module Pixie-4 is in slot 6?

    You probably already know, but turn you on the chassis PXI before you have activated on your computer?

  • Analysis of resources of RIO PXI chassis

    Hello

    I am trying to find a way to analyze all the resources of RIO in a PXI chassis programmatically.

    In my chassis PXI-1085, there FlexRIOs (7975R), but also the VSTs (5644R and 5646R).

    Using communication NI-VISA, I was able to communicate with all these modules, but only if an Alias is defined in NOR-MAX.

    I have'nt bee able to get RIO associated modules found resource name using 'VISA find resource' VI.

    Also, I have 2 questions:

    -Is it possible to communicate with my modules without defining an Alias in NOR-MAX?

    -How can I get the name of RIO resource programmatically?

    (I could put as an alias of VISA in NOR-MAX the same name as the resource name of RIO but it is very restrictive, the deployment of the application to other configurations)

    Thank you

    I'm guessing a bit here - but is it possible with the System Configuration screws? It's the library/tool box that allows you to get various information about a system (for example cRIOs - installed software) - there is a 'material to find' VI-I suppose you can point to your PXI and it will give you some information?

  • Running out of 400 Hz PXI chassis

    Has anyone tried running an off AC running at 400 Hz PXI chassis?  We have problems with the power supply for our location data acquisition system in an aircraft and 400 Hz seems to be the best option for a continuous power.

    Matt

    Hi Matt,

    On what chassis? My guess would be that we cannot, simply because the numbers for all of our power switchable are different, however, I'd be happy to look into the issue for you.

    The following link has a list of all our chassis PXI with swapable power supplys:

    However if the DC is an option, I would recommend one of our DC power chassis.

    PXI - 1031 DC

    PXI - 1036 DC

    PXI - 1000B

    Thank you

    Scott M

  • PXI-ExpressCard8360 on laptop Linux

    A PXI-ExpressCard8360 is usable on a laptop with Linux?

    Is this possible? All the world does?

    I have a laptop that uses the PXI-ExpressCard8360 to connect to a chassis PXI-1036 MXI express with Windows 7. My client asked to bring the app to Linux and I found some information on the modules I use, but nothing about anyone using the ExpressCard connection.

    Matt,

    The PXI-ExpressCard8360 kit you mentioned will work as well in Linux as "regular" kits planned MXI that you do not use NI MXI-Express BIOS software compatibility to work around BIOS problems.

    "" If you don't know if you use it, look for "all programs" National Instruments "Configuration of the ExpressCard-8360 card" on a working system (Windows).  If it is not installed, then you should be good.  If this is the case, start to check the configuration of your card ExpressCard (see the Readme with the software for further instructions).  If you can disable compatibility mode, uninstall software compatibility OR MXI - Express BIOS, reboot and run normally then you should be good.

    -Robert

  • PXI-1042 q with controller 8331

    HI........

    I want to configure a single chassis PXI-1042 q with controller PXI-8331. I have connected 2 I\O Digital Digital card (PXI-6515) and 1 card(PXI-6514) I\O to this chassis. And I have connected this chassis to my PC with the serial cable (OR standard cable on COM 1) on my PC. But the problem is when I opened and Measurment Automation explore it dose not detect chassi eithre or any card I\O.

    I installed OR version 4.6.1 platform services.

    An obsrevation is led RX ON Chassi and dose led TX ON PC does not illuminate.

    Please guide me step by step configuration.

    Thank you

    Pravin.

    PBL,

    The PXI-8331 is not a serial interface, even if the connector looks like it, so it should not be connected to COM1.  It works when it is connected to a PCI-8331 in your host PC.  The cable must be a MXI-4 cable, for example 190957-03, not a cable series.

    If that's what you do, please report the LEDs on the two cards.

    -Robert

Maybe you are looking for