S/W-chassis PXI RTOS by MAX load

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,

• PXI-6682 shows Max, but not in DAQmx

  Hello

  I recently received a new chassis with some rare cards and I am relatively new to everything related to NEITHER.

  In any case, I also had a new PC (because they asked me to start from scratch)

  So I installed the following:

  1. NOR-Daqmx 9.0
  2. NOR-Sync 3.1
  3. MAX 4.6.1f0

  Later, I plugged my chassis and got all my cards to register automatically... except for the PXI-6682.

  Subsequently, I've traveled to find the pilot who has worked and myself (in the Setup OR Sync). MAX is now able to test it, read it and all that.

  Now the problem is that I need to know my C program run-time if the device is there or not...

  To achieve this effect, I used this: DAQmxGetSysDevNames

  It returns all devices except the PXI-6682.

  I can "cheat death" using the name provided in MAX ("Dev11") and use my calls OR Sync in this way... but it's terribly static.

  Y at - it no probable cause why a DAQmx call would not have recognized a device?

  Tips:

  1. http://forums.NI.com/NI/board/message?board.ID=80&message.ID=1257 : does not really give a solution
  2. The pilot seems weird... "Device Manager" name is "NI PXI-6682" instead of "PXI-6682" ' "."
  3. If I call DAQmxGetDevProductCategory it returns DAQmx_Val_Unknown (so that he knew the unit is plugged... but he can't read it)
  4. My NO-Sync calls are able to control the PXI-6682 very well

  Thanks in advance for any help,

  Sébastien Dupéré

  Hello Sebastian,.

  The NI PXI-6682 does not appear as a NOR-DAQmx device because it is not controlled by the driver OR DAQmx.  Instead, all commands and communication are through the NO-SYNC driver.  The "DAQmxGetSysDevNames" NOR-DAQmx function returns only the names of devices that can be controlled by the DAQmx driver.  To and from this device function calls will go through NOR-SYNC.  I'm not too familiar with this driver (I work with DAQmx) but they may have a function to return the names of similar to the DAQmx devices.

  (Incidentally, in the forum post you linked, the aircraft was a DMM which is controlled by the driver OR DMM and the explanation above also applies for him.)

  Kind regards

• USB-5133 appearing does not in MAX, "loader" shows driver in Device Manager.

  I have a USB-5133 can I use it on several computers. I'm putting it on another PC (XP Pro). The device is recognized by windows and it goes to install the drivers. When it's done, in the Device Manager-> data acquisition devices, I see "NI USB-5133 Loader. On other computers, he said only: "NI USB-5133. The green light on the device is NOT on, and the device does not appear in Measurement & Automation Explorer.

  No idea why the appropriate driver is not loaded? I have NO-SCOPE 3.5.2.

  Hello Gallamine,

  The NI USB-5133 Digitizer is a plug-and-play device, try removing the device in MAX.  Then, unplug the device and plug it in again.  The computer should record the device of MAX as "NI USB-5133.  If this does not work, the data base of the MAX could be damaged.  To resolve this problem, see the following link:

  http://digital.NI.com/public.nsf/allkb/2C7480E856987FFF862573AE005AB0D9

  Finally, if the database setting does not resolve this problem, try to reinstall the latest version of OR-SCOPE.

  Kind regards

  Roman S

• facing problem in communicating with chassis cRIO-9104 NI Max

  I tried to communicaste with my cRIO-9004 using the ethernet cable that is connected to the same subnet as the PC master. It is mounted on the cRIO-9104 chassis that has a reconfiurable FPGA and 8 slots.

  But I could not find cRIO-9004 in the specified window NOR MAX chassis as unknown.

  I am new user of this module and the software. Help, please

  Hey, Vinayak,.

  I'm not sure that there is a problem here. Usually, you'd do anything with Max modules are you able to add them to your project in LabVIEW?

• Install NI Veristand Engine on PXI via error MAX

  I get the error message that I have attached.

  I have avoided this problem by letting someone else install the software on the PXI system for me, but I really need this feature.

  When the error occurs, all the software on the PXI system packages is removed, this occurs for all users.

  I tried this on two different PXI system and the same thing happens.

  Am I missing some package? Or someone has a suggestion?

  Best regards

  Jørgen

  I found a solution that works. Do not know why these files were missing and / or why MAX could not just create them himself.

  I did the following:

  Created a folder + file text for what has been reported missing.

  This resulted in the following structure:

  D:\National Instruments\Shared\Errors\English

  D:\National Instruments\Shared\Errors\French

  D:\National Instruments\Shared\Errors\German

  D:\National Instruments\Shared\Errors\Japanese

  I then added two files for each folder:

  NIVS-modelframework - errors.txt

  NEITHER VeriStand - errors.txt

  And now it seems to work.

• PXI: no device (MAX), fail to connect or deploy

  Hello

  I tried to use an SMU-8135 and MAX status is "connected - Running ', but once I try to connect or to deploy from the project it opens a box dialog saying"fail to connect to the target. Also, I don't see no modules currently in PXI on MAX under devices and Interfaces.

  Note: I use LabVIEW Professional 14.

  Thanks for the help!

  I just wanted to update this discussion because I finally solved my problem and it can help people in the future.

  Here's what I did to make it work:

  (1) traded on the SMU ethernet cables

  (2) checked with the cmd I could ping the target

  using MAX:

  (3) uninstalled all the software that was already on the SMU (because I had some questions of dependencies)

  (4) reinstalled the LabVIEW RT module on the system (ensuring that download the PXI components)

  (5) installed the necessary components on the SMU (check that the two LabVIEW RT on the target and the host have the same version)

  After all these, I added the target of a project and could connect without problem.

  I hope that helps!

• 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

  
  

• Download Serial settings saved in Max loaded in LabVIEW

  Is there a simple way to obtain or retrieve Configurations saved in MAX in LabVIEW series?

  We have several devices that communicate well RS - 232 that require different settings. The connection of these devices agreement can change from one test to the other. I want to do it is using MAX to determine what equipment is connected to which serial ports, record communications at MAX settings and load them in LabVIEW to make the connection. I could write some code to allow the user to do this, but why reinvent the wheel.

  I have attached to my list of software incase a new version might be able to do.

  No indication in it would be greatly appreciated.

  Thank you

  Tessa

  You don't have to do anything to get the parameters set in LabVIEW. As long as you do not use the VISA to configure the Serial Port, the settings will persist and you have to just do your reads and writes with the correct resource. In other words, if you set baud rate to MAX for Com1 to 56000, in LabVIEW if you write to Com1, it will happen at 56000 baud.

  This has been the case for versions of VISA much older than what you show.

• The a6 - 5400 k in my hp p7 - 1436 max loads to 64 degrees celsius

  the A4-3420 in my p6 2316 s past 40 degrees Celsius maximum to the maximum load with the temperature of 46 degrees Fahrenheit air. My p7 - 1436 s is still under warranty, what do I do?

  I downclocked just my APU and it reaches the temperature of 10 degrees Celsius since AMD K-series is made crazy overclock / turbocore manufacturer.

  Right click on desktop-> AMD Catalyst Control Center-> the (power) processor-> Adjust power

  I lost time return the computer to HP.  I should have ask just how downclock on HP forums since that was all I wanted to know anyway.

  

• Chassis PXI MXI timeout

  
  
  

• PXI-6527 and PXI - 6025E unrecognized in MAX (RT - PXI)

  These maps to an older system that ran Labview 7.1, now installed in a new PXI RT, but they show NO-max.

  2015-Labview and NOR-DAQmx 15.1, using Windows 7-64 bit

  I tried everything so far, you just can't get them to show.

  Can not install traditional DAQ, cause 64-bit OS does not support it.

  My guess is that NEITHER-DAQmx 15.1 does not support these cards?

  Solved!

  It turns out that the PXI controller was not compatible with the chassis PXI, the local agent of OR made a mistake.

  NEITHER replaces the chassis for me now

• 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?

• Not displaying data acquisition devices is not under the chassis to MAX after updating drivers OR

  We use a PXI-1031 chassis and 3 PXI-6143 devices to our MetalMapper of the geometry. Also the chassis appears only in MAX as "unidentified" and PXI-1031 is not displayed in the list "identify as".

  Thanks for your reply... uh... PeanutButterOven

  After having looked in the information requested for our controller, we realized that we had a wrong model for our controller number.

  After we have determined the correct model number (NI PXI-8108), we could assign to the unidentified PXI system in the "identify as" drop-down list in MAX > my system > devices and Interfaces and then select our chassis model number (PXI-1031DC).

  After we did it, a new object was automatically created called PXI-1031DC 'Châssis 1' and our devices were already provided in a drop down of this frame object.

  Thanks for your help!

  We now live a new show with our custom software that seems bound to not find .NET drivers even if they exist on our computer.  This seems to be a separate problem and we will publish it to a new discussion if we're stuck.

  Thanks again

• 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?