PXI computer

Dear sir,
My test stand sw is working normally on Windows XP also PXI cards but when I turn off my computer (when the windows message is " you can turn off the computer safely) led on the PXI computer does not turn off so that to I can use the computer again I need the to pull out the power cable. How can I solve this led problem? Could you help me?
Best regards...

Hey behluls,
There is a great Logic Analyzer example that ships with LabVIEW. Unfortunately it is with our NI-HSDIO driver that is only supported by 654x, 655x, and 656x cards. The NI-SCOPE software isn't really used as a Logic Analyzer so I am not sure if there are any specific examples available for that. I would still check in LabVIEW's Example Finder to see if anything looks like a good start.
Regards,
Erik

Similar Messages

Streaming using ethernet

Hello
i looking for a suggestion a practical one. i want to stream data using ethernet cable from controller pxie 8130 ethernet slot,i have connected the controller to my PC using an ethernet cable(like form pxi 5142 digitizer onbord memory to controller 8130 memory and then from controller memory to my PC).
1-Can i make an application for acqusition on my PC labview, then using this can i acquire the data direct form controller
memory to PC memory.
2- Or i have to store my data first form digitizer to controller Hardisk and then from controller hardisk to pc i can move
it using some other application like clint/server since it then would be a file to transfer.
3- what can be the bottleneck's if the memory of PC,controller,digitzer is 256Mb each.
Regards

Hello COMSIS,
Let's brake this down into small parts here and step through the data as it goes from signalall the way back to host computer. I'll assume that you are sampling on one channel at the full rate. Since we can sample at 100 MS/s and each sample is streamed back as 2 Bytes of data, we would be streaming at 200 MB/s whichshould work with your chassis (should be a 250 MB/s limit as per PCIe spec's). So, your card will not be a bottle neck.
Once you bring the data back into LabVIEW, you will more than likely have to use a producer/consumer architecture. Your producer loop will put your data into a queue that will be read out in your consumer queue. In the consumer queue you will want to use TCP comunication to stream your data back to your non PXI computer. This DevZone outlines how you would do it in an embedded application, but you can also use it with a Windows based PXI system.
Here my knowledge of LabVIEW memory allocation and TCP communication speeds is a little lacking, so we might not be able to keep up with the data rates and so you may need to go with your other idea of storing it to a disk and then FTP'ing it back to your host computer. To get the best answers, I would post the second half of your question on a LabVIEW board and just include a link back to this thread. Once you post there, post back on this thread with a link to the LabVIEW post so that anyone who comes onto this post later can get the complete answer.
Message Edited by ColeTrain on 01-27-2010 05:52 PM
ColeR
Field Engineer

TDMS file error occurs after several hours

I have a compiled LabVIEW 2010 SP1 executable running on a Windows 7 PXI computer that is occasionally producing the following error message:
"LabVIEW: LabVIEW could not load the TDMS file component.
The top-level VI <my VI's name> was stopped at unknown on the block diagram of <my VI's name>"
This program is interfacing with equipment under test over a number of PXI cards and ethernet connections. It alters inputs to the system based on script commands, while receiving and displaying outputs. During testing, state changes are sent to a TDMS file. The system can run for hours but will usually produce the above error message... eventually.
The error seems to indicate that a LabVIEW file is missing, but the TDMS files are being created, so I may not be understanding the meaning of the error. Does anyone know what the actual cause(s) of this error message are?

The code writes to the TDMS file using the "TDMS Write" VI from the TDM Streaming Palette. These write VIs are located in 12 different sub VIs in a program loop within my main VI. Every 50ms they execute, service the I/O, and write to the TDMS file if data in the particular sub VI has changed state. Some are writing floating point numbers, most are writing strings. There are about 750 total channels being written. I know that posting the code would be more usefull than describing it, but I think posting the source code would be frowned upon by my company. There are over a hundred custom VIs and external hardware connections that are required to effectively run this code anyway.
Regarding timing, there doesn't seem to be a particular amount of time that has to pass before this issue occurs. I was given a screenshot that shows the error occured after 11 hours of running. I was also told that the same error had occured about 6+ hours into a test once. I can say that this error doesn't seem to occur quickly, as in within the first hour or so. It seems to require long duration tests.

UMI-7774 - Setting default Power up outputs?

Hi,
I'm using a UMI7774, PXI7350, NI Motion 7.4.0.3002, and LV 8.2 I have a 24 V power supply connected to Viso on the UMI. When the PXI computer boots the general purpose digital output lines (table 3-9 in the UMI manual) on the 25-pin D-sub go to 24V and stay there until the board is initialized. Is there a way to set the default power up state to 0V?
Thanks,
Richard

Hi Richard,
Here is a knowledgebase document regarding how to change the
power up state
KB 2HA8B9YJ: How Do I Change the
Default Power Up State of the DIO Lines on the NI 733x, 734x, and 7...Based on the setup configuration you have described, there
is currently no direct method for accessing the DPull pin. One work-around
would be to create your own custom cable in order to ground this pin. Here is
another document regarding how to do this:
KB 47FARV4M: Creating custom cables
for NI Motion controllers (733x, 734x, 735x) I
hope this helps. Please let us know if
you would like further clarification or assistance regarding this issue.
Best
regards,
Vu

Deploying teststand V3 - mdac98 error on target machine

Thank you in advance.
I have two PXI computer that I'll like to deploy sequence file to, from a development machine, I have successfully create the installer using tool>>deploy test stand system but I get error message "mdac98" required when I attempt to install it to win98 target machine. I have been to the windows website to download and install "mdac98.exe" but I still get the error.
I have read some literature on this issue but got no where. Out of curiosity what is the different between "disturbing test stand" and "deploying test stand". anyone?

Rash,
I just answered a question you posted on DCOM that was nearly identical. Are you also having problems with mdac or was this question supposed to be on DCOM?

Unable to see PXIe-8133 in MAX on host computer

Hi,
I seem to be running into a very basic problem. I'm trying to use the PXIe-8133 system in Real-Time but I am unable to detect the system in MAX. I can't even see an "Unconfigured RT System" with IP Address of 0.0.0.0 as it shows in the documentation. I've installed all of the drivers for the PXIe 8133 on my host computer found here:
http://joule.ni.com/nidu/cds/view/p/id/2030/lang/en, but this has not solved the problem.
One thing to note, when I attach a monitor to the PXIe-8133, it says: "System State: No Software Installed" and also "Can't Find Suitable Device for Drive C". But only one of our 2 PXIe-8133's is displaying this and we are not able to see the PXIe-8133 system in MAX even in the system which does not display these warning messages.
Thanks very much in advance for your help!
Steven

Hey Steven,
So a couple things to make sure of:
1. Reboot your PXI and when it is rebooting up keep hitting the delete key until you see an output on your screen that gives you different options to select.
2. Go over to Real Time menu (think it is like the fourth option from the left on the top).
3. Once in here the first option is what mode of Real-Time do you want to access. Select LabVIEW Real-Time Safe Mode.
4. Go to the last menu option and save changes. This will reboot into the mode we just set.
Once it is rebooted, go into MAX on your computer that is on the same subnet as this PXI and refresh remote systems. You should now see a device with an IP address of 0.0.0.0. Make the changes to the IP address that you want. Once you save those changes it will reboot the PXI. If you are still not able to get the target showing, try to go back into the bios and there is also another option to choose under the Real-Time heading to reset IP by hardware switch, software or none. Change that to software. Save again and then it will reboot and see if you can now see it in MAX and make the corresponding IP changes.
David A.
National Instruments
Applications Engineer

Computer does not boot when pxi 1033 is connected

hiiiiii...........i am using NI pxi-1033 for my application & this pxi is connected to my system through PCIe-8361. i am using it from last 10 months, now suddenly my computer does not boot up. i start pxi first then start the computer but computer screen shows no signal. there is no blue screen error.
can you give me any point to troubleshoot the problem.

This probably doesn't help, since your setup used to work, but I have had to run the MXI Compatibility Tool on more than one PC.
http://joule.ni.com/nidu/cds/view/p/id/3119/lang/en
One PC would only boot one time in ten, before running the tool.

Can I communicate single PXI chassis with multiple computer using MXI

Can I communicate single PXI chassis with multiple computer using multiple MXI cards
we are using cvi with MXI we want to share channels for other computers Can we do with mxi

Yes this is possible when you use a PXI controller. Attached is a screenshot showing a possible configuration.
Jacob K || Applications Engineer || National Instruments
Attachments:
PXIMaster.png ‏20 KB

CNVString - Sending Strings from a PXI chassis over ethernet to a labWindows application on another computer

I have a PXI chassis with a PXI-8101 controller. It is set up with a realtime operating system. I am communicating to it with a PC with a Windows operating system. I am trying to send variable length string messages from my PXI system to my PC.
On the PC I have a LabWindows application which can send and receive data with the PXI system. I am attempting to send error messages from the PXI system to the PC on ethernet. I am able to send numerical data between them but not the string messages. The PXI software runs to the function call CNVCreateArrayDataValue() and steps into it but never returns. It only has this problem when the parameter CNVDataType is CNVString; when I change CNVDataType to CNVBool it does not have this problem. I am new to this PXI realtime so would appreciate the help. Below is the code on my PXI system which sends these text messages.
In the beginning of RTMain I create the Writer
      CNVCreateBufferedWriter("\\\\localhost\\system\\" REG_CAL_ERROR_STRING, 0, 0, 0, 64, 5000, 0, &gErrorPublisher);
Then I call a function with a string in the parameter list:
void SendRT_ErrorMessage(char* message)
      CNVData data=0;
      int error;
      char error_str[256];
      int i;
      char out_str[ERROR_STRN_SIZE*4];
      strcpy(out_str,message);
      size_t arrayDims= ERROR_STRN_SIZE;
      arrayDims= strlen(message) +1;
      error = CNVCreateArrayDataValue(&data, CNVString, out_str, 1, &arrayDims);
      if(error<0)
            strncpy(error_str, CNVGetErrorDescription(error),256);
//    CNVPutDataInBuffer(gErrorPublisher, data, 1000);
      CNVSetArrayDataValue(data,CNVString,out_str,1,&arrayDims);
      CNVPutDataInBuffer(gErrorPublisher, data, 1000);
      CNVDisposeData(data);
Solved!
Go to Solution.

I've changed things around and now the application on the realtime operating system on the PXI-8101 does not hang but my host computer does not see the message correctly. It sees some characters but they are not what I sent.
I don't seem to be able to get message out of CNVData data properly. Below is the new code for the PXI-8101 controller and the Host computer LabWindows application.
Here is the code in the PXI-8101 controller now:
CNVCreateWriter("\\\\localhost\\system\\" REG_CAL_ERROR_STRING, 0, 0, 5000, 0, &gErrorPublisher);
void SendRT_ErrorMessage(char* message)
CNVData data=0;
int error;
char error_str[256];
int i;
char out_str[ERROR_STRN_SIZE*4];
strcpy(out_str,message);
size_t arrayDims= ERROR_STRN_SIZE;
arrayDims= strlen(message) +1;
error = CNVCreateScalarDataValue( &data,CNVString,out_str);
if(error<0)
  strncpy(error_str, CNVGetErrorDescription(error),256);
CNVWrite(gErrorPublisher, data, 1000);
CNVDisposeData(data);
And here is the code in the Host computer LabWindows application:
sprintf(path, "\\\\%s\\system\\%s", address, REG_CAL_ERROR_STRING);
CNVCreateSubscriber(path, ErrorMessageCallback, 0, 0, 10000, 0, &gErrorMessageSubscriber);
static void CVICALLBACK ErrorMessageCallback(void * handle, CNVData data, void * callbackData)
char message[ERROR_STRN_SIZE];
CNVGetScalarDataValue(data,CNVString,(void *)message);
(void)SetCtrlVal(panelHandle,PANEL_TEXTBOX_DEBUG_MSG,"got something\n");
(void)SetCtrlVal(panelHandle,PANEL_TEXTBOX_DEBUG_MSG,message);
(void)SetCtrlVal(panelHandle,PANEL_TEXTBOX_DEBUG_MSG,"\n");
CNVDisposeData(data);
You can see that I output a message "got something" so that I know I got the callback but the next line is a gibberish message "HÊl "

Disconnected PXI locking up computer

I have an issue when an otherwise working PXI with PXI-5922 installed connected to a PCIe slot in my host computer by an optical cable. Everything works great if I boot up the computer with the chassis powered, but if the chassis loses power or for some reason the data link is physically disconnected, if any software tries to communicate with the chassis, the computer locks up completely. Mouse movements or keyboard presses do not register and I have to do a hard-reset.
Is this a known issue?
It can be reproduced in NI-MAX by verifying a successful connection to the device and then disconnecting the device and refreshing the connected devices in NI-MAX.

Hello Allman,
The behavior is totally expected. That is NOT a correct use of the PXI. You did not mention what PXI you are using or what MXI connection you are using, but you can find in the manual the instructions to power up the system and you need to power on the chassis first, then you power on the host. If you are going to power down the system, power down the host first, finally the chassis.
Because of this, BIOSes and operating systems make the assumption that all PCI devices in the entire hierarchy will be available as soon as code execution begins at power-up time. This assumption means that all of the expansion chassis must be turned on before the host PC for the BIOS and OS to correctly configure a MXI-Express system.
Regards
Frank R.

Computer doesn't shut down when PXI Chasis is turned off

Hello,
I have realized that my computer doesn't shut down propertly if I turn off my PXI-1036 chasis before the computer is turned off. Is this a normal behaivour?
As far as I remember, the PXI-1036 chasis must be turned on before the computer is power on, and I think that maybe on the turning off I have to follow the same procedure.
Thank you very much for your advice,
Héctor
Solved!
Go to Solution.

Yeah, Robert's correct and I was backwards. I haven't used my 1033 chassis for years. Guess I should have tried it before answering.
Using LabVIEW: 7.1.1, 8.5.1 & 2013

Windows "Blue screen of Death" when booting computer attached to LabVIEW PXI realtime system

Good Morning (at least in the western hemisphere)!
I'm having a problem on two test systems where intermittently, at least on one machine, I get a Windows "Blue Screen of Death" error message when booting the machine connected to a PXI RT system. I reloaded the RT systems software yesterday (LV RT 7.1.1, NI-VISA 3.3.1) and am having this problem on two different setups, two laptops, two PXI chassis. Our short term work around has been to boot with the network cable removed at one end or the other, but these are the baseline models for a larger test system in the design/construction stage that will not be used by knowledgeable engineers but by (probably more knowledgeable!) technicians. Any ideas would be a help
Thanks again,
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Blue screens are almost always caused by drivers and not by applications, so chances are there's a problem on the driver level. The crash log file will be instrumental to diagnosing this problem.
Turn on the crash event logging as described in this Microsoft KB:
http://support.microsoft.com/kb/314084/EN-US/
...and then post the details from the crash found in the Windows Event Viewer here. That will help us narrow the problem down.
--Paul Mandeltort
Automotive and Industrial Communications Product Marketing

PXI-6115 & PXI-6143 on Same Computer, RDA's Future

Today I installed several PXI-6115 cards and realized that they are only
supported with traditional DAQ under version 7.2. This is OK for now
because I'm already limited to traditional DAQ to be able to use RDA.
However, I was considering adding the new inexpensive S board, the PXI-6143,
to my system. According to the list of supported boards this board is only
supported by DAQmx. Questions:
1. How can these two S boards be used by the same system if programming with
LabVIEW?
2. Any guesstimate on if or when the PXI-6115 will be supported by DAQmx?
3. Any guesstimate on if or when RDA will be supported by DAQmx? RDA
(remote data acquisition) is an extremely valuable DAQ method and I hope it
will be supported by D
AQmx soon!

Hello,
You are correct about the support of both boards. The 6143 is only supported in DAQmx, and the 6115 is only supported in Traditional DAQ. Here is the best that I can do for the other questions.
1. You can program each card in a different driver. This is not a problem at all. The only conflict occurs when you try and program a card in both drivers at the same time. Such as trying to do analog output in Traditional DAQ and analog input in DAQmx.
2. This is internal information only. For further information I would contact your local sales representative, she/he might be able to assist you further.
3. Again, if and when is internal information. It is not currently supported. At the moment, you can use remote front panels, or create y
our own server/client VIs to control a remote DAQ board.
These are excellent pieces of feedback for our R&D department. I highly encourage anyone who reads this thread to submit product feedback using this link.
Best regards,
Justin T.
National Instruments

Computing Requirements in Multiple PXI Chassis System

I have acquired a two PXI Chassis system, each with their own embedded controller (PXIe-8108 and PXIe-8130). I would like to control all instruments (simultaneously) in both chassis from a central location (either a laptop or one of the embedded controllers). What is the best configuration for this and will using one controller have enough power to drive two fully populated PXIe-1065 chassis?
(I am aware of the different configurations for control (MXI, etc.) and am more concerned with instrument performance, data buffers become full quickly etc., in using one PC controller)
THANKS!

Hi JMU_ISAT,
The PXIe-1065 chassis uses a four link configuration where there is an x4 link going to slots 7, one to slot 8, another to slots 9-14. There are also an x1 link converted to PXI that goes to slots 2-7 and another x1 link converted to PXI that goes to slots 11-13 and 15-18. Each x4 link gives 1 GB/s of bandwidth and each x1 link converted to PXI will provide 125 MB/s of bandwidth. These bandwidths are theoretical maximums where overhead and chip design reduces the bandwidth somewhat.
The PXI-8130 has four x4 links with the four link configuration so it will be able to get the full chassis bandwidth. The PXIe-8108 has four x1 links which will limit the bandwidth to 250 MB/s for slot 7, slot 8, and slot 9-14.
To synchronize the measurements across both chassis you will need a timing and synchronization module such as the PXIe-6672 in the timing slot of each chassis. This will allow you to route the clock of one timing module to the other and then use that clock to override the backplane reference clock of each chassis. Now each module can use the 10 MHz reference clock to synchronize to each other.
In order to control both chassis from one controller, you can run windows on one controller and LabVIEW RealTime on the other controller allowing you to distribute code from the windows controller to the LabVIEW RealTime controller. The other method would be to run a MXI connection from one chassis to the other to daisy chain the chassis. Since the most you can get out of a single slot of the PXIe-1065 is an x4 link, this would limit the total bandwidth of the daisy chained chassis to 1 GB/s theoretical maximum.
I hope this information is helpful!
Andy K.
Applications Engineer
National Instruments

I am using NI PXIe-1073 with Labview-2014.After deploying the VI how can i read the data through host computer?

sankar,new delhi

PIB. I want to read the data from the GPIB after the operation complete. I am using *opc? command, which should set the status register bit after the completion of the operation, but this is not working. How to know that the Operation is complete"-Thanks.The NI-488 global status variables ibsta, ibcnt, and iberr is what you are looking for. Look into the 4882 help file for details. Also NI-Spy, http://www.ni.com/support/gpib/nispy.htm, is a good debug util. There is a website that lists common GPIB error codes and solutions. You may check there for some things to try. You'll find the link at ni.com > Support > Troubleshooting > Installation/Getting Started > GPIB, titled "GPIB Error Codes and Common Solutions".
You could find a driver for this instrument at http://www.ni.com/devzone/idnet/default.htm . If it's not listed there, it leaves you with one of a couple options. First, I would like you to submit a request for this driver at: http://zone.ni.com/idnet97.nsf/instrumentdriverrequest/
We develop dri
vers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
If you would like to try developing your own instrument driver (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at :
http://www.ni.com/devzone/idnet/development.htm
We also have a syndicate of third party vendors that specialize in National Instruments' products and services. Some of the vendors specialize in driver development. I would suggest contacting one of the Alliance members at:
http://www.ni.com/alliance
Hope this helps.

PXI computer

Similar Messages

Maybe you are looking for