NI PXI-8101 RT

Hi!
There are two version of this controller:
780955-33 NI PXI-8101 Celeron 575 2.0 GHz Real-Time Embedded SW
and
780956-33 NI PXI-8101 Celeron 575, 4 GB (or Greater) Flash HD, RT SW
What is the difference between its?
Is the "4GB flash" in the 780956-33 controller a "regular" CF card. Can I replace it by the CF card with 64GB capacity?
Jury

Hello Poklad,
Thank you for bring this issue to the forums. The difference between the two are as follows:
1. 80955-33 NI PXI-8101 Celeron 575 2.0 GHz Real-Time Embedded SW
This will have an 80 GB Serial ATA Hard Drive minimum.
2. 780956-33 NI PXI-8101 Celeron 575, 4 GB (or Greater) Flash HD, RT SW
This will have a 4GB Flash Drive minimum.
Everything else between these to controllers are the same and yes, you can upgrade the 4 GB Flash Drive to a higher volume drive
Thank you,
Vimal Fernandez
Applications Engineer
National Instruments

Similar Messages

PXIe-8101 Unable To Compile Code

Hello,
My system is a PXIe-1065 chassis (I've also had the same issue in the PXIe-1082 chassis), PXIe-8101 controller with Windows 7 installed by NI, and the following instruments:
DMM PXI-4071, Power Supply PXI-4110, DAQ PXIe-6356, Timing Card PXIe-6674T, and Motion Control PXI-7332.
I also have a PXIe-8361 which I will use on occasion and will be what I use in the long term.
Now for the actual problem. What happens is I'll put together some code in labview using the instrument driver VI's and everything will work fine. I can make VI's that call subVI's that call the instrument VI's and it works great, but if I double click on an instruments VI and then try to look at the block diagram, for example, opening "DAQmx Create Channel (AI-Voltage-Basic).vi" it seems to break the code. Initially it won't say anything but once I hit the run button the arrow will change to the broken gray arrow and will state that the code failed to compile (this is without actually changing anything with the VI, I open it and look at what it is doing).
Also any code I've written that called that VI will now get the same error, if I click show error it will bring up whatever window I was looking at last, so if I was looking at the front panel, then clicked show error it would just bring up the front panel again without highlighting anything. If I create a new file and build a small vi that uses the instrument drivers it works fine, if I copy the vi's from the broken code and paste it into the new file it will fail with the same error.
It doesn't have this behavior with all the instrument VI's but will happen with some. I mentioned it happens with "DAQmx Create Channel (AI-Voltage-Basic).vi" but then it doesn't happen with "DAQmx Timing(Sample Clock).vi". I haven't gone through and checked exactly which VI's it happens with but it seems to happen with other instruments drivers as well, not just for the DAQ. It also only seems to happen when using the PXIe-8101. If I connect it to a computer this issue doesn't pop up. My company primarily controls the chassis using MXI cards so we don't have any available embedded controllers I could swap in to see if it still happens.
It's not a big issue as looking into the instrument vi's isn't necessary for me to do my job, I just do it to try to better understand what exactly is happening but it is something I'm curious about.
DISCLAIMER: I'm a hardware engineer so I may not be familiar with some concepts/terminology/best practices so... patience is appreciated
Solved!
Go to Solution.

At the time I first noticed this error I was just starting to use labview, so I simply avoided opening that vi, now I've been working with labview for about 9 months. I haven't been working with it consistently, not all my projects require it, but I would say I've spent at least half my time working with it.
Well I seem to have recorded it slightly off. So when I looked into the DAQmx vi it gave an error and when I clicked show details it gave the following:
When I tried to exit it asked me if I wanted to save the changes, I chose defer decision and eventually chose do not save. I closed labview and reopened the VI, tried to run it and it gave the error:
I selected show error and it gave:
Then where it said it failed to compile was within another vi in the same project. When I first opened it it said SubVI is not executable. When I clicked show error it took me to a VI that had the DAQmx vi in it and it was saying VI failed to compile.
I've attached the SubVI from which I opened the DAQmx. It's a basic vi to read analog data. Is that what you meant for screenshots?
DISCLAIMER: I'm a hardware engineer so I may not be familiar with some concepts/terminology/best practices so... patience is appreciated
Attachments:
DAQaread.vi ‏27 KB

How to connect a Compact RIO to a PXI System

Hello,
I want to connect my cRIO-9074 with my PXI System.
First of all my Hardware configuration:
1. "PXI-1036" Chassis with "PXI-8101" Embedded Controller and "PXI-8231" Ethernet
2. "cRIO 9074" Integrated 400 MHz Realt-Time Controller
3. "NI 9144" EtherCAT slave chassis
The PXI System is connected with my Network through the Ethernet-Port on the "PXI-8101" Controller. The "NI 9144" is connected with the "cRIO 9074" through their EtherCAT Ports. That works without a problem.
Now I want to connect my "cRIO-9074" with my PXI-System through the Ethernet Port on the "PXI-8321", but I can't find a way to get this work.
In MAX I configured the second Ethernet Port on the PXI as "TCP/IP" with a IP and Subnet. Then I connected the cRIO and turned it on.
But I can't find the cRIO anywhere in MAX or in a LabView Realtime Project.
When I configure the "PXI-8321" as a EtherCAT Port, I can connect my "NI 9144" with it and use it in a LabView Project. But configured as Ethernet and connected with the "cRIO 9074" it doesn't works.
Is there any way to get this working? Or is this not possible with my Hardware?
I know I could connect the cRIO and PXI through a Switch with my Network and then use both in a LabView Real-Time Project. But I want to build a mobile Measurement-Station with as few devices as possible. If there is no other way I will use a Switch, but without would be better.
Thankful
Daniel Löffler

Hi Daniel,
it is not possible to connect cRIO-9074 Controller with the PXI System through the Ethernet-Port, because the RT cRIO Controller can not behave as a slave. cRIO Controller is always configured as a master, never as slave. The extension Chassis 9144 is configured as a slave, so you can use it with your cRIO Ctrl or with PXI Ctrl as well. Connection PXI-Ctrl, cRIO-Ctrl, NI 9144 is not possible.
Best regards,
ENIA
NI Germany

PXI-6509 Error occurred at Reset Device

Greetings Everyone,
     I recently had three (3) PXI-6509's fail in one of my Test Stations. I tried to reset them in MAX and received the following message: "The device reset has failed. The error report from the device driver is as follows: Error -224903 occurred at Reset Device.". I also received "Error -50152". After that while I had the stores list up of all installed boards, the three (3) PXI-6509's removed themselves from the list.  I'm wondering what these error codes are telling me.  The pop up error dialogue box stated that the "Possible Reason(s): Internal Software Error occurred in Static_Digital_software". I'm also curious as to what this is relating to. I replaced all three (3) board from a NEW chassis that I'm bringing up for use and everything thing is fine. I tried plugging these failed boards into my other chassis and the computer will not even boot up. Thank you in advance for any information that you provide that will help me in understanding what may have caused this to happen. The system was working fine up to lunch time and after lunch is when the problems started.
Regards,
Scott
Solved!
Go to Solution.

Greetings Nick,
Here is the course of events that led up to the problem being described.
While testing UUT’s (Company Product): (PXI-1044 with PXI-8101(XP), GPIB Controller and various PXI cards installed)
Before Lunch everything was working well. It was after lunch that the following events took place.
a)     Test Sequence hung up during External Power Supply ramp up in which the D-I/O are used to switch relays inside the ITA (Interface Test Adaptor) to connect the DMM to the Power Supply that is in use at the particular time in the test sequence. This has happened a couple times before, but NO error ever happened and just re-booting the system cleared it.
b)     The next thing that was performed was shutting down TestStand and Labview.
c)     The next thing that was performed was executing “MAX”.
d)    Once in “MAX”, I normally try to RESET all of the PXI cards, which is usually successful, but not in this case. The error pop up came up with the two (2) different error codes (-224903 and -50152). Please explain what the “Static-Digital Software is?
e)     I shutdown “MAX” and Re-Booted the system.
f)      After Re-Boot completed, I executed “MAX” once again and clicked My System, Devices and Interfaces and PXI-1044 “Chassis 1”.
g)     I tried to reset the NI PXI-6509 “PXI1Slot7” and received the pop-up error as described.
h)    Upon clicking OK. The PXI1Slot7 and PXI1Slot8 removed themselves from the stores list of cards installed and the icon next to NI PXI-6509 “PXI1Slot9” changed from a little green board icon to a white board icon with a little red ‘x’ inside it.
i)      Next, I removed all three (3) PXI-6509 from a NEW chassis in a NEW TestStand that I planned to bring on line in a couple of weeks. I placed these boards into the TestStand that is failing and everything is working well once again. I ran some diagnostics and everything checks out OK.
j)      Next, I took the failing boards and placed them into the NEW chassis and the computer wouldn’t even boot up.
k)    Next I removed two (2) (PXI1Slot7 and PXI1Slot8) of the boards and tried to boot the computer and the computer booted up.
l)      I proceeded to execute “MAX” and check the stores list only to find that the board (PXI1Slot9) was not even in the category of the PXI-1044 Chassis1 but outside it and it also had the white icon with a little red ‘x’. It also affected the PXI-2575 in PXI1Slot10, which had a white icon and little red ‘x’. I removed the board from PXI1Slot9 and re-booted the system and PXI1Slot10 recovered with the normal green icon that is usually next to it.
What I need to understand is what “Static-Digital software” is and what the errors are telling me. The fact that three (3) NEW board installed into the chassis and function 100% tells me that there is something wrong with the three (3) boards that I removed from the chassis and that nothing else seems to be wrong with the chassis.
The fact that installing the three (3) boards into a NEW chassis and the computer not booting is something of concern. I’m trying to understand what could have caused this to happen in the first place so I can be prevented in the future.
Regards,
Scott

Function control of the PXI system

Hi All!
We order NI PXI-1036DC + PXI-4462 + PXI-6682 GPS + PXI-6653 + PXI-8101.
Is it possible to control:
1. DC voltage and current?
2. GPS coordinates of the system?
3. Accuracy (or quality) of the 10 MHz clock disciplining by the 6682 GPS? It may be accuracy of the GPS positioning or number of satellites.
4. Temperature? It may be processor temperature.
Jury

Hello Jury,
Thank you for bringing this issue to the forums.
Regarding your questions:
1. What do you want to control the DC voltage and current of? Which card exactly?
2. I am not exactly sure what you mean by controlling the GPS coordinates of the system. Can you please explain further?
3. You can find the specifications of 10 MHz clock and accuracy of the GPS on page A-5 and A-6 of the PXI-6682 GPS Manual: http://www.ni.com/pdf/manuals/372292b.pdf
The 10 MHz clock accuracy is +/- 1 ppm, you cannot change this value. The accuracy of the GPS is within 15 ns, you cannot change this value as well. Once again all this information can be found on page A-5 and A-6 of the PXI-6682 GPS Manual.
About the number of satellites, the more satellites available to the receiver, the more precisely it can determine time and location. Therefore, the location of the antenna should be such that it will receive signals from the greatest number of satellites possible.
4. The +/- 1 ppm accuracy of PXI-6682 is specified in the range of 0 to 55 C.
Thank you,
Vimal Fernandez
Applications Engineer
National Instruments

PXI 8105 with Windows7

Is PXI 8105 compatible with Windows 7? And also what will be the cause of hardware malfunction? Mine kept telling me hardware malfunction? It keep shutting down by itself.

Hello Jesusisjenny,
Hope you're having a great week. When you install your own Operating System on one of our controllers, you also have to install the Peripherial Device Drivers. These are the drivers that support the chipset of that particular controller and are needed to recognize your peripherial devices such as USB and PXI cards. We have a compatibility chart that lists which OS's are compatible with our controllers, but the 8105 only lists Windows XP and Vista:
http://digital.ni.com/public.nsf/allkb/E4503CC7E8BB41BA86256F7F006CBE8D
So it doesn't look like we officially support Windows 7 for this controller. Your best option would be to move to a newer PXI controller such as the PXI-8101:
http://sine.ni.com/nips/cds/view/p/lang/en/nid/207072
or the PXI-8820:
http://sine.ni.com/nips/cds/view/p/lang/en/nid/211700
If these are beyond your budget and you are feeling ambitious, another option would be to install Windows 7 on you 8105 then try to use the Vista Peripherial Device Drivers for the 8105. It may turn out that the drivers developed for Windows Vista work under 7, but NI doesn't guarantee the functionality and we wouldn't be able to offer you support for this configuration. Another consideration is that the PXI-8105 is an older controller that may not have the best performance under Windows 7, especially with the standard 0.5 GB of RAM it came with. Even if you get Windows 7 installed, the performance may be too slow to be acceptable.
Regards,
Mason
Applications Engineer
NI
Mason M
Applications Engineer
National Instruments

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 "

Code could not be generated because an external component or driver is missing

Greetings All,
     I've using Labview for a little over a year and I have an interesting situation with regards to Labview that I came across today. When I left off yesterday (01/11/12) my TestStand sequence was compiling fine. Today for some reason the compiler told me that one of the VI was broken or missing a sub vi. When I made my way through all the sub vi's in the vi that seemed to be a problem I came across "Code could not be generated because an external component or driver is missing".
     The problem started on the computer (NI PXI-8101 with WinXP and Labview 2010) located in a PXI-1044 that is in my Test Stand.  I have a complete backup on my laptop and my desktop computer which both compiling successfully with no errors. I tried installing the directory on another PXI-8101 and got a different set of results.  The first PXI-8101 gave 100+ errors in TestStand pointing to one of my vi's and the other PXI-8101 reported only one (1) error. The vi is basically using DAQmx vi's to create a "write to one line" action. I'm kind of stumped as to why it works on the laptop/desktop and not the PXI computers. All four computer are WinXP professional and Labview 2010. I saw somethings through google search engine but nothing conclusive. I'm hoping that someone can give me an explaination as to what is causing the error as described. Even if I copy over the directory it doesn't fix the problem. Thank you in advance for an information you provide with this rather interesting problem that I've encountered. If you require addition information let me know.
Regards,
Scott
Solved!
Go to Solution.

Greetings Beau,
     Thank you for the reply.
     I loaded the offending VI into Labview (2010) with TestStand inactive. Of course this was after I completely shutdown the computer and re-booted to ensure that nothing was resident in memory. I've included a couple of the error list boxes in this post.
     It comes down to a subvi that is two (2) subvi's deep. All these vi's are doing is commanding a write or read to and from the PXI-6509. When I check the VI at the level that has no broken run arrows (named below), nothing in the block diagram looks out of place as it should since these were installed by Labview installation. The vi that uses these vi's looks total normal and its block diagram doesn't have anything out of the ordinary yet the run arrow is broken. The odd part of this is that the top of the window that states the filename of the vi has an astrex at the end of the filename, even though nothing has changed in that vi.
Here is a list of the deepest level that has no broken run arrow:
DAQmx Create Channel (DI-Digital Input).vi
DAQmx Start Task.vi
DAQMX Read (Digital Bool 1Line 1Point).vi
DAQmx Clear Task.vi
DAQmx Create Channel (DO-Digital Output).vi
DAQmx Write (Digital U8 1Chan 1Samp).vi
     I guess the real question is what is the error message ("External component or driver missing") really telling me if all of the vi's look right. I appreciate any information you can send my way that will give me a better understanding of where this error is coming from. The program I developed had been running without a hitch for a month an all of sudden crash.
Thank you for your time in this matter.
Scott
Attachments:
Write to one port broken VI error list.JPG ‏47 KB
Readfrom one line broken VI error list.JPG ‏46 KB
Broken_VI_Error_Screen.JPG ‏56 KB

SIT Real-time data logging and passing data

Hello all,
I am pretty new to LabView real-time, so I just want to confirm a few things. I am also using the Simulation Interface Toolkit.
Let's take the Sinewave.vi from the SIT examples. I have modified it to use sinewave.dll, and run on PXI-8101. If my understanding is correct, when I click "Play", the entire Sinewave.vi is deloyed into PXI-8101, and therefore the entire VI is running at the same pace. The front panel I see on my desktop is slower snapshots of what is actually happening?
1) Let's pretend now that the sinewave model is time critical and must run every 10ms. How do I do that? I have noticed that within the "SIT_Indicator_Indices" loop, there is a Wait 50ms block. Is that accurate?
2) I have also added a time elapsed block that will change the Frequency and Amplitude inputs as a function of time. I made them update every 2ms. What clock are we running on? If my sinewave.mdl suddenly calculate integration (time dependent), can I use that elapsed time block as my timer to pass into the model?
3) How fast is the sinewave.vi running anyways?
4) Let's say I want a log of the sinewave output (a data point every 10ms). I don't need the log in real-time, I just want to do some analysis on it later. How do I do it?
Thanks.
Attachments:
Sine Wave.vi ‏104 KB

Hi Bladhart,
When running the in the Development Environment (pressing the run button on the Real-Time vi) there will be an extra thread to handle the front panel you see. This thread will be handled just like any other thread in Real-Time and will take processor time, thus slowing down your entire application to a certain extent.
1. You would need to make sure everthing inside the loop can execute within 10ms and change the wait time to 10ms. Or you can use a timed loop set to run every 10ms and get rid of the wait time but again you would need to ensure everything in the loop can execute in under 10ms.
2. The elapsed time should be running off the Real-Time system clock.
3. The time that the Sinewave.vi is running is system dependent, there is no set speed.
4. You can log the data by saving to a *.tdms file. You can then use the data from the *.tdms file to do processing later.
<Brian A | Applications Engineering | National Instruments>

No DMM functions in functions palette

Good Morning,
I'm VERY new to labview but I'm starting to get the hang of it. Anyway i've been searching for hours and have been unable to find a solution to my issue.
I'm running a NI PXIe-1078 chassis with PXIe-8101 controller
I'm trying to program data aquisition for my PXI-4071 DMM in my Labview project but there are no functions in the functions palette.
I installed the NI-DMM 3.0.5 driver and can see the device connected in MAX. I can even use the soft panel and take measurements from the PXI-4071.
For the other devices i have installing the driver put the functions in the functions palette but for some reason they are all missing for the DMM.
I've tried using the DAQmx and searching for an analog input channel but it is not on the list.
please help!
Sincerely,
Michael Reed

It sounds like a "corrupt" installation of NI DMM (see paragraph below).
Please note that NI DMM 3.0.5 is out-dated, so you should get a more recent version.
When installing a new system, NI recommends to start with the developement environments and in the last step to install all desired drivers. Following this ensures that the installer of the drivers can detect the installed ADEs and select to install the APIs for these. If you swap install order, the APIs are not installed with the driver, leaving the ADE blank (no examples, no palettes).
You can install the APIs in a second iteration, but that is an effort you should only put into the system when installing a new version of an ADE.
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

RT File Size issues

We are running PXI 8101 RT on LabView 2011 August release.
Occasionally we find the free space is gone and our data dir is corrupted.
We are storing 50k/Sec*8channels for 8 hours in TDMS format. This is probably about 80+GBytes. We were doing it in 1 TDMS file. We have been doing 1,2,4G byte files now. However sometimes we find the free space is gone and the files are corrupted or destroyed, requiring a reformat and reinstall of the RT.
We are finding that we can do 1-2Gigabyte files forever. The software checks for free space, deletes some old data, and starts a new file. It checks to make sure it has 100G free. This works. We are putting the data into a subdir under www so its easy to find for ftp'ing.
I suspect we can only do up to, but not including, 4Gigabytes for one TDMS file. Is this true? Or do we have some other issue? TIA
www.certtech.com

your right. RT is FAT32 and its max'd at 4G per file.
So I was wrecking the File alloc table (FAT) and blowing up the system. Thought about using a external USB drive that was NTFS but RT won't recognize it per NI's website. Looks like we are just going to do 20 minute chunks of TDMS files (3.6G) and that probably helps with the FTP as well. 80G files won't FTP well anyways.
I wonder if anyone will really look at all of that data anyways
www.certtech.com

Problem connecting to Realtime system to download or run in debug mode

I have updated my LabWindows\CVI to 2013. I have a PXI system with a PXIe-8101 controller. The PXIe-controller has a real-time OS installed. I have been programming this system for a while now so I am not exactly a novice anymore. The first time I tried to install the program to my real-time target I got a message which said "LabWindows/CVI cannot connect to the real-time target." It also said " .... The version of the LabWindows/CVI Run-Time Engine for RT must be compatible with the version of the LabWindows/CVI development environment."
So I figured that was the problem. My next step was to go into MAX and sure enough was getting all sorts of flags and errors when I used the real-time software Wizard in MAX by right clicking on the Remote software and clicking on Add/Remove Software. And like I suspected there were several flags indicating a software differences. My next step was to update the software in my real-time target to resolve the problem. After I did that I compiled the code and installed it on my remote system. Everything seemed OK.
The following Monday I restarted LabWindows/CVI and made a couple of changes and tried to build and install to my real-time target. I get that same message as in the first paragraph. So I thought I might not have real-time system booted up correctly or something like that so I checked all of that and it looked OK. Next I opened up MAX and it could see my real-time target just fine.
When I had my LabWindows/CVI 2012 I did not have this problem. I think maybe there is some incompatibliity issues with my LabWindows 2013; has anyone had a similar problem? I am able to get around the problem by building the release version and copying it to the PXI with CuteFTP V9.0 but I cannot do run my program in debug mode with my LabWindows/CVI and if you may have noticed I have other problems which is in another post I put in next week. I am hoping the problems are connected and I can kill two birds with one stone LOL.
I appreciate any suggestions.
Thanks,
Don Pearce

Hello,
I want to make sure I'm understanding what you are doing in the LabVIEW project. According to the Getting Started with the LabWindows /CVI Real-Time Module manual, these are the steps to install software on the RT target:
1. Launch MAX.
2. Find and expand your RT target under the Remote Systems item in the MAX configuration tree, right-click Software, and select Add/Remove Software. When you select Add/Remove Software, MAX launches the LabVIEW Real-Time Software Wizard. This displays all the National Instruments software and drivers installed on the host computer that you can install on a selected RT target.
3. Select the software you want to install on the RT target, click the icon next to the software, and select Install the feature.
You need to install LabWindows/CVI Run-Time Engine for RT to add support for LabWindows/CVI RT applications on the RT target. This component is required for all LabWindows/CVI RT applications.
The forum post here solved this same issue by installing missing drivers based on this KnowledgeBase article.
Also, LabWindows/CVI 2013 SP1 has been released. Service Pack 1 (SP1) has many useful bug fixes (listed here), so I recommend upgrading to LabWindows/CVI 2013 SP1 if possible.
Taylor B.
National Instruments

LV RT - String to double conversion

Hello,
I want to convert a string to a double on my Real Time device (PXI-8101. When I use the "scan value" or "Fract/Exp String To Number Function" VI the numbers after comma dissapear. This does not happen on the Host (PC).
So for example on the host vi, the string "2121,3" gives the number 2121,3. If I do the same thing on the Real Time, the string "2121,3" returns the number 2121.
How can I fix this?
Thanks in advance,
Regards,
Dries
Solved!
Go to Solution.
Attachments:
String2Number.vi ‏7 KB

Hello,
Thanks for the reply, but scan from string also does not return the correct number on the RT device. The VI returns the number after comma as the remaining string. Any other suggestions?
Best regards,
Dries
Attachments:
String2Number.vi ‏8 KB

Two PXI systems in MAX

Hi!
I have PXI 1036DC system with 8101 RT controller. In MAX I see some second PXI system with the same name (see dup.jpg). Why it occures and what it means?
Jury
Attachments:
Dup.JPG ‏176 KB

I'm not so familiar with your hardware. However, the 6682, among other things, is designed to let you synchronize hardware with another PXI, perhaps reached through its Ethernet port. Your picture seems to show a second PXI (PXI2) that has a 4462 card in it (why it shows as a VISA connection is beyond me, but that may be the method of communication).
You appear to have hardware capable of "reaching out" to other systems. If so, MAX will show all of the systems it can reach. For example, I have a single camera in my office that I use with IMAQ, yet MAX shows me something like 30 cameras because they are all on the network and, potentially, MAX (and I) can "reach" them.
You might be able to temporarily edit MAX's internal file and "remove" that 4462 card from your display, but if my understanding of MAX is right, the next time it starts up, it will survey its surroundings, and if the device is there, it will show it.
Bottom line -- MAX is showing you what is available. It does not mean you need to (or even can) use it.

Poor PXI IO performance on Latitude E6410 with ExpressCard 8360

Hello,
I have a Dell Latitude E6410 with a Core-i5 M520 which is giving me very poor io performance when using an ExpressCard 8360 card to connect to a PXI Rack.
The sustained IO rate that I can get appears to be about 1/3 of that that I can get using the same ExpressCard on a Dell Latitude E6400 (with a Core2Duo processor).
I am using the A05 bios (latest at time of writing) on the E6410.
Wade.

I am running Windows XP (32 bit) sp3 in both cases.
The E6410 has 4GByte of memory fitted.
The E6400 has 2GByte of memory fitted.
I have also use the same ExpressCard 8360 via a PXIe to ExpressCard Adaptor in a Desktop machine with similar performance figures to the E6400 - i.e. much better than the E6410.
The Desktop Machine is an HP Compaq D7900 with 4GByte of memory, Core2Duo E8500 also running Windows XP sp3 (32 bit).
Also, on the Desktop, I am running NI PXI Platform Services 2.3.2 and NI-Visa runtime version 4.3.
On the E6410, I am running NI PXI Platform Services 2.5.2 and NI-Visa runtime version 4.6.
I no longer have access to the E6400 so I am not sure what sofware versions were installed. However, they are unlikely to be new than the versions installed on the E6410.
Wade.

NI PXI-8101 RT

Similar Messages

Maybe you are looking for