PXI controller

Similar Questions

• Installtion of Labview RT on the PXI controller

  We have a 8106 controller PXI that runs on the Windows operating system. We want to make it work on real-time OS of NOR. What are the steps I need to do to install this. Vascular when I boot in the BIOS of fron LabView RT, it displays "control transfer to the user program. System not configured, restart... ». I am able to connect it to MAX by the host PC and able to install Veristand 2011. But it does not reflect while the boot controller.

  Converting Windows a RT, there are some very important things that you must do to handle the conversion. big is your hard drive.  Your hard drive needs to be formatted with a FAT32 partition - probably formatted Windows NTFS, RT cannot read or use.  Convert your drive will be a manual step for you; If you follow these steps, you can use a disk RT PC Desktop Utility to perform the Exchange against (these instructions with a PXI-8106 module):

  First of all, must be a FAT32 partition on it and the format.

  1. Acquire a drive Flash USB 256 MB or more.  Plug it into your host computer.
  2. Image/Format the USB Flash drive via MAX
     • Under tools of-> creating USB utility MAX desktop PC
  3. Plug the USB key into 8106
  4. Enter the BIOS of 8106 using the "Delete" key
  5. Go to the menu "LabVIEW RT" and "Priming" the value "" Windows / other OS '. "
  6. Press F10 to save and exit, restart the controller.
  7. Enter the BIOS of 8106 using the "DELETE" key (we had to put the controller for Windows / Other and restart the computer to enable USB be detected/used)
  8. In the 'Boot' menu, make sure that "USB HDD" (probably also has your mfg of the inserted USB) option is #1 in the startup list (using keys + /)
  9. In 'Advanced-> Integrated Peripherals' ensure 'Legacy USB Support' is [ENABLED].
  10. Press F10 to save and exit, restart the controller.
  11. The startup controller using the USB flash drive.
  12. In the USB Flash Drive Options, choose the 6 'Options of Format' option (according to the image of the flash player, can say another thing, but option # is the same).
  13. Choose to format the drive, use the Option #2 in the format "Erase all Partitions on the disk and create a new single Partition" - This clears the disk partition information and creates a single FAT32 partition on the drive.
  14. FAT32 format (DO NOT use the use of a 8106 - BIOS does not include the system of dependency files).
  15. Once completed, restart the controller (to do this, you can use Option 9).

  Now, we must get the controller to think that it is a PXI and not a desktop RT PC controller

  1. Enter the BIOS of 8106 using the "Delete" key
  2. Go into the menu "LabVIEW RT" and "Boot" "LabVIEW RT safe mode" value
  3. Press F10 to save and exit, restart the controller.
  4. In MAX, find the device to remote systems.  Right click on the device and choose "format disk".
  5. Once you format the disk, the controller will think it is a PXI controller.
  6. (You may need to remove the MAX controller and press F5 to detect again for updated images)

  Now we are going to put the controller in RT mode so we can use it.

  1. Enter the BIOS of 8106 using the "Delete" key
  2. Go to the menu 'LabVIEW RT' and 'Start Configuration' value 'LabVIEW RT'
  3. Press F10 to save and exit, restart the controller.

  There you go.  Now you are ready to rule the world in a deterministic way.

  -Danny

• Remote control of the instsrument of the PXI controller

  Can you suggest the best method to control PXI instruments with an external controller?  I have two machines.  A standard desktop system and a PXI chassis with controller and installed instruments.  I can the remote desktop for the PXI chassis.  I expecting MAX to recognize instruments in my desktop computer PXI chassis and use VISA address as if it were local.  If possible give examples for a starting point.

  Thank you!

  The Keysight support team helped me to solve this problem.  They showed me MAX remote system control and walked me through the Setup program.  The link they sent me from the site NEITHER.

  http://digital.NI.com/public.nsf/allkb/F3AB0B5D7DBA367C86257982005BBF2C

  Thanks Keysight!

• NOR-RIO Patch Nov 2013 on the PXI controller

  Hello

  We use SMU controllers like the LV RT 2012 SP1 8115. We have also a card FlexRIO in the chassis, and we use FIFO write often.

  From what I've read on the November 2013 Patch NOR-RIO (http://digital.ni.com/public.nsf/allkb/95CF25A09DB91FEE86257BE8006193B7?OpenDocument), we should update the systems of RT, but I do not see this option in MAX.

  After you have installed the patch, I have the documents mentioned 12.1.1 with a file mite.cdf inside. But Max, I don't see any updates to the target. I still have a single NOR-RIO mentioned 12.1 which is already installed on the RT system.

  So, how to install this hotfix on the SMU-8115 OR with LV RT 2012 SP1 and 12.1 OR RIO?

  Also strange: when using the OR update service again and expand the updates and Service Packs the Patch OR-RIO reappears in the list of critical updates.

  Thank you

  Daniel

  The component listed in the patch updated is unfortunately a component hidden which is automatically installed when you install your system remotely RIO.  Relocation of the NOR-RIO of MAX component to your remote system should be sufficient to force the patch to apply.

  Note recommended sets of software are not supported under PXI, where is expected.

• How to configure a PXI controller - 8106 RT with DAQ traditional channels?

  I have a few tips that are not compatible DAQmx and do not appear in MAX (4.6). I want to configure them to traditional DAQ, but if following the instructions (Tools / traditional DAQ/Remote Configuration) the error "connection to the remote computer XXX error. Make sure that the GDR server is running on the remote computer, and that both computers are connected to the internet. "They are connected with a crossover cable, and the machine rises to the MAX. I can run the server of the GDR on the local computer, but don't see no way to start it on the remote control of the RT. Right click on the machine of MAX and say 'Create New' do not have the traditional DAQ option, only items DAQmx. And MAX takes forever with this controller and often crashes... I made sure the software on the controller corresponds to that of the local computer (LV 2009 with RT).

  Lauréla,

  Please post on the Forums of NOR. It seems as if you do not see MAX devices, then you do not have the driver installed on your computer. I recommend to install the driver traditional DAQ 7.4.4 on your Windows machine, then you can install the T-data acquisition driver on your RT system. From there, you should be able to see your T-materials under your remote systems.

• Can I use PXI embedded controller connected to the PC under LINUX operating system

  Hi all

  We ara tries to connect to PXI8106 (in 1042 chassis) to PC under LINUX via ethernet (cable cross at the moment), is the version of labview 8.5.

  Can I use PXI embedded controller connected to the PC under LINUX operating system?

  If Yes, where can I find its configuration in the .ini file?

  Thanks in advance.

  Hello bachir_elec,

  I'm sending you two links that I don't provide the information you need.

  Using Linux on an Embedeed PXI controller:

  http://digital.NI.com/public.nsf/allkb/821E0C115A3B4EF286257069004B8352?OpenDocument

  Configuration of your PXI Linux system:

  http://digital.NI.com/public.nsf/allkb/5CEEC941FB7B0488862573F700653B21?OpenDocument

  You can take a look?

• Remote access for PXI with DAQmx

  I have a PXI chassis with a real-time embedded (PXI-8186) controller and some modules DAQ (PXI-6259) x 2. I've been programming this via LabWindows with a kind of client-server of RT - UI thing by using network variables and others. For some applications, it would be enough and more convenient to be able to interact with the PXI hardware directly from a connected PC network DAQ.

  The controller running a VISA server, it seems that I could connect to a remote machine with a kind of viOpen ("visa://pxi.somewhere.com//PXI0::15:INSTR"); ") and then contact a particular data acquisition card. But I can't find any information on the programming of the 6259 in any way other than DAQmx or similar.

  First question then: is the interface PXI - 6259 VISA described anywhere?

  More practical would be to continue to use DAQmx, through something like DAQmxCreateDOChan (taskHandle,"pxi.somewhere.com//Dev1/port0/line0:4",...)

  I found references to what we call 'Remote access appliance', for example:

  http://digital.NI.com/public.nsf/allkb/5CC9792C6CD4A34C862565BC0072D5DF

  that seems to put in place something equivalent, but I don't find it to watch it in MAX:

  Start-> all programs-> National Instruments-> NI - DAQ-> the remote device access server

  and I've seen suggestions that maybe it isn't that for traditional DAQ or only pre 7.0, or in any other way was no longer applicable.

  Second question: "Remote device access" are always and how to I install/activate it on my PXI controller?

  Someone at - it clues as to the foregoing, or any other way to get the same kind of features?

  Thank you

  Mike Schacht

  LANL

  Hello Mike,.

  Remote device access was a feature in NOR-DAQ traditional long just now.  This feature was not worn on OR-DAQmx because the framework it was built on does not really correspond with the need of modern times for network security.

  Unfortunately, there is no functionality you describe by saying to DAQmx.  Currently, this type of control is limited to deploying applications to the target of RT.  While the VISA is used for some parts of the DAQmx interaction, these function calls are not documented.  Someone else on the forums may be able to help if they tried to implement something like this in the past.

  Good luck!

• 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

• PXI-8110 update to Windows 7 image

  I was wondering if someone has updated their controllers to a new OS?  Specifically, we received earlier this year a couple of PXI-8110 controllers incorporated with the gradient to XP option.  But now we wish we had Windows 7.  I was jumping that NEITHER would be able to provide the Windows 7 CD recovery of for this controller (because Windows 7 is an option) and I would have to pay the Bill for a license of Windows 7.  However, they said that it was not possible (OR - Please correct me if I'm wrong) and I have to install it myself.  So, any advice on this process would be appreciated.

  Thank you

  Paul

  Here are two INF files for drivers who have not installed correctly the first time.  Sara had sent to you about a month, there are and said they worked for you.  I am posting here in case someone else needs them as well.

  Note: This is not the ideal way to install drivers for a PXI controller.  The controller should come image correctly with all necessary drivers and the recovery disc as well.  If however you encounter the same situation, then you can try these.  They are drivers for the delivery of trigger PXI and WatchDog Timer for Windows 7 on the PXI-8110.

• Try to install the software on target RT PXI 1082

  Hello

  I try to run a chassis PXI-1082 (recovered with factory settings), but I have some problems when I try to install softawre through NOR-MAX on it from another PC connected with the ethernet cable.

  First of all, I saw a PXI chassis BIOS problem when I started PXI chassis in RT mode: "ph_exec.exe is missing". PXI chassis started in SafeMode to RT.

  Secondly, I detected correctly chassis with MAX on PC with the correct IP address but when I tried to install the software on it, an error message resembles what occurred: ' no more space in the hard disk or input output error occurred. " I think that there is a consequence to the previous "ph_exec.exe is missing" message

  Could you please help me for this disorder?

  Thank you.

  ARM

  Hi Alexis,.

  Thanks for your reply. I am not able to open your link, but I found a solution on site OR: «Dual-boot Windows and Labview RT on a PXI controller»

  My problem is that my hard drive on the PXI controller is configured in NTFS mode and no partition in FAT32 mode existed. The reason why my PC says "no more space available" because it seemed to drive FAT32 partition. I am surprised that NEITHER do not included the partition FAT32 for RT. I've probably missed something. In any case, it seems to work fine now with disc FAT32 partition.

  I install the software on my lens PXI know.

  Thank you

  BR

  Vincent.

• NI PXI - 8108 RT with real-time compatibility 2009 and PXI-1050

  
  

  Hello

  The PXI-8108 should work just fine with the PXI-1050 chassis. The only requirement is a chassis PXI uses a PXI controller and a SMU chassis uses a controller SMU. Since the 8108 both 1050 use the PXI standard, they should work very well together.

  Eric

• How to get MAC address of a PXI in a dll

  Hello

  I'm looking for a way get a RT PXI controller MAC address. I know that there is a VI to do this, but I'm looking for a solution for a dll (Code C).

  I use the 'call library node' to call this dll and want to ensure that it is used on a specific PXI system.

  Since the VI provides the feature, I wonder if it is also available from C-Code?

  Thank you

  Christian

  
  

• PXI-8512 software compatibility issues

  I have a PXI-8512 CAN module high speed in my system. My PXI controller a real-time OS. I'm having some problems and tried to identify the problem.

  My question:

  Are there known problems with the PXI-8512 compaitbility using the NI-CAN 2.7.4 software installed on a system in real-time?

  It was a problem with my code. I announced my CAN messages to a queue and it sometimes took a long time for the message BOX to be actually defined. Never understood why the 2012 of LAbWindows/CVI has worked better than the 2013 but found a work around so my problem is solved.

• Unable to connect to targets PXI - 8196 RT in MAX

  I'm trying to set up the initial connection to my goal of RT (it is a model used, configured by an engineer OR running LabVIEW RT front arrived at our laboratory), but did not have much success.  I have connected the target RT, a PXI-8196, directly on my Windows computer using an Ethernet cable and manually set an IP address for this connection in Windows Network & Sharing Center.  When I try to connect to the target of RT in NOR-MAX, I do the following:--> create a new--> remote device (not on the local subnet) enter the IP address I specified manually.  When I type "Finish", however, I get the following error message: "failed to initialize the remote connection or targets.

  I have disabled the Windows Firewall on the Ethernet port and also downloaded and re-installed PXI Platform Services.  Is there a step I'm missing, or anyone any suggestions of what else to try?

  I use NI MAX version 5.6, Windows 8 running on the host computer and the on-board computer is a PXI-8196.  Thanks in advance!

  I just went through this with another PXI controller.  Absolutely, you don't want the PXI to reach a binding address local 169.254.x.x, because this will allow you to force MAX to connect.

  Start by setting is using your PXI controller upwards with a monitor, so you can see what is happening, and that it address and a keyboard, if you need to enter the BIOS of the controller.

  On your PC, connect an Ethernet cable from the NETWORK adapter that you use for communication PXI for PXI.

  Assuming that your PXI has a 169.254.x.x address, configure your NETWORK card to also have a similar (but different) address, by using a subnet mask of 255.255.0.0 (so the 169,254 pieces must match, but the other two numbers is not guaranteed).

  Now open MAX.  Click on remote systems.  I guess you don't show anything there, and the right pane is empty.  In the right pane, click on «Create a new...» "and select"remote device (not on the local subnet).  Yes, it is on the local subnet, but never mind.  When it prompts you for the IP, put the IP address that the PXI monitor shows like PXI IP.  He must find the controller almost instantly.

  What I'd do next is to configure the IP address that you want to use.  In my case, I use addresses from 10.0.x.x for both my network cards that "speaks" my PXI and PXI.  While MAX talk to your PXI, you can set the IP address, and then restart the PXI - you should see it happen to the new IP address you specified.  Of course, if you change its IP address to a 10.0.x.x address, you will need to change your NETWORK card to also use an address in this range.  Once both have been reset, MAX should be able to find the PXI under remote systems.

  Now, all you have to do is add/remove software and you should be good-to-go.

  Bob Schor

• Problem with the RTEXE file on PXI system

  I have attached the image of the comic to a very simple code that illustrates a problem with a file RTEXE on PXI system.

  If the VI (LabVIEW 2011) is started on the target of the RT of a LabVIEW project, no problem.

  If the code (with the shared variable linked to a typedef of indicator I32, lvlib being on target and ctl files) is compiled and run in starting my PXI system, it does not (message = "bad state" or something equivalent in french)!

  But when the shared variable is disconnected the typedef, the RTEXE file runs correctly in starting...

  No explanation for this strange behavior?

  A way to execute a RTEXE file on a PXI controller with shared variables typedefs?

  Thanx & BR,

  HL

  I have an answer on the french section of the forum: it's a LabView2011 bug, fixed in LabVIEW2012.

  LabVIEW2011 the only solution is to disconnect the shared variable the typedef

  Kind regards

  HL