ADLINK PXIe-3985 Controller - NI PXIe-1062Q Chassis Compatibility

Hello forum members!
we recently purchased a PXIe-3985 ADLINK PXIe Embedded controller to be installed in a NI PXIe-1062Q PXIe chassis. In our system is also present a NI PXIe-6672 Timing Module, installed in the chassis timing slot (4). Windows 7 installation, NI MAX toolsuite and NI PXIe-6672 Timing Module driver installation worked fine, but we discovered that the CPU is not able to recognize the TIMING SLOT. We cannot generate any PXI STAR signal with our NI PXIe-6672 Timing Module because it appears that the TIMING SLOT is recognized as normal peripheral slot. The PXI trigger lines and clocks are working well and usable, but not the PXI STAR signals.
I also tried to install the PXIe Chassis in the NIMAX toolsuite as explained in the PXIPLATFORM _50-17049-100_200.pdf document from ADLINK.
basically in the NIMAX device and interface tab I right click and try to add the pxie chassis.
First it is not understandable how can I find the bus identifier root of the chassis. There is a PXI bus tree, but no evidence of the PXI bus related to the chassis.
Furthermore even if I select one PXI bus, the NI PXIe-1062Q PXIe chassis is not listed and trying to load the corresponding .ini file from C://programs/nationl instruments/PXI/PXIe Chassis/ returns the error “Could not import Chassis information. Error Code 0xFFFB380E”
is the ini file working at all for my PXIe chassis? is there another procedure that I must follow to have my timing controller working or the chassis installed?
We definitely need this capability to test our equipment and I would like to know if there are known incompatibility issues between these three devices:
PXIe-3985 ADLINK PXIe Embedded controller
NI PXIe-1062Q PXIe chassis
NI PXIe-6672 Timing Module
And in case if there is an update or workaround which solves the issue.
The system has Win7 32bit installed.
Many thanks to every answering user

Hi emanuele83,
which version of PXI Platform Service do you use?
Can you please upgrade to a current version?
Here is a download link:
PXI Platform Services 14.1 - National Instruments
http://www.ni.com/download/pxi-platform-services-14.1/5230/en/
This may solve the issue.
Best regards,
Andi

Similar Messages

Problem with PXI-8145RT Controller.

Hi All,
I am preetam.
I am using PXI-8145RT controller in PXI-1011 Chassis.
My controller is having 64MB of Compact Flash and 128MB of SDRAM.
I configured the Chassis through host PC using MAX.
But if i restart the controller the configuration is going off and we have to reconfigure the controller again.
How can i store the configuration permenently?
thanks in advance and awaiting for ur reply
Preetam

line 16 on the Access List refers to allow ICMP Pakets on the whole network.
Line 16 does not cause the DHCP Problem. When we remove line 16 from the ACL the DHCP problem persists.
It doesen´t matter what changes we apply on the ACL. We have the DHCP Problem since from the start when we added the ACL.
When the ACL is removed, we don´t have any DHCP Problems.
Thank you

PXIe 8262 streaming performance with HDD 8264 on a PXIe 1062Q chassis

Hello,
I have a PXIe 1062Q chassis, running Win XP, with one 8262 connected to an HD8264 and two PXIe 6537 installed, all the three board being on the express slots (3, 4 and 5). Running the benchmark application for testing the streaming speed (Win32FileIO) I get something like 100 MB/s with data chunks of about 4 MB, and around 140 MB/s with chunk of 64 M. How can improve these results toward the theoretical limit off 600 MB/s? Is there any software/driver trick to be applied?
And, in case, which is the best way to exploit the 8262 from C++ written code (using the NI libraries)? Is there anything similar to the Win32FileIO library? I tried using the RAID system from a c++ test program, and the performance seems very poor, while I would need, if not the 600 MB/s rate, at least something around 200 MB/s of continuous streaming.
Thanks in advance,
Piero.
Solved!
Go to Solution.

Hi Neil,
I actually have a 8130 controller, and in fact that was not the problem: I found the problem being the file-caching performed by Windows file system. If you use standard fstream calls from C source code you cannot bypass it, but by using Windows native call (CreateFile(...), WriteFile(...) APIs) and setting the flag for no data caching or buffering inside the call, I managed to get the full bandwith of 600 MBytes/s.
Anyway thanks for the quick reply!
Piero
I'm guessing you have a controller that only
supports x1 PCI Express. The PXIe-8130 is our highest-bandwidth
controller, with four x4 links going to the chassis. In the case of
the 1062, each of slots 3, 4 and 5 get a dedicated link from the
controller. x1 links max out at about 200 MB/s and x4 links max out at
800 MB/s.
So your first step is to use an embedded
controller or use MXI Express x4 instead of x1 back to a host
computer. While the PXIe-8130 is the best for high-bandwidth data
transfers, the PXIe-8106 should also be sufficient for your needs.
If
you want to stream data to disk from a PXIe-6537, it is already built
into DAQmx. You simply specify a file name, and the data goes to
disk. If you want to stream *from* disk, you'll have to do that on
your own. Here is a C/CVI example for streaming digitizers to disk
using a C API and the Windows File I/O functions.
Neil
Principal Engineer
National Instruments

How to use TRG pine in PXI-8176 controller

Dear All,
        I have Thermocouple data acquisition system. In which there are 2 chassis, (1) PXI 1002 with
PXI8176 controller with RT, PXI 6071E DAQ card (2) SCXI 1001 with SCXI 1125 card and SCXI1327 block.
PXI 6071E connected to SCXI 1125 with SH1006868 cable and adapter SCXI1349.
I am using Labview 8.6 , DAQmx9.0
I have develop program for continuous thermocouple acquisition. Now i want to make program on trigger based data acquisition. When trigger pulse comes system starts to acquire data ( and log in file) for userdefine time and stop acquisition. Again when trigger pulse comes   system again starts to acquire and stop at define time.
There is one TRG pin on PXI-8176 controller, Can i use that one and how i can use it? Or i have to use separate DIO line for trigger?
Can you guide me how i can develop such system.
Thank you.
--Vishnu
Solved!
Go to Solution.

Thanks Shreyas,
Once again you help me to solve my problem.
   As i have already mention you i have develop temperature measurement system with-out trigger. Here i am attaching my project. Now, how i can make it trigger based, means when trigger pulse comes acquisition start and target send data after some time for example 5minutes stop acquisition and restart acquisition again when next trigger pulse comes and so on.
Thanks
--Vishnu
Attachments:
host_target.zip ‏81 KB

How to use PXI Star Trigger for PXIe-5663 in PXIe-1075 chassis

HI all,
I have this sytem configuration:
PXIe-8135 controller. Windows 7 64-bit, RFSA 2.7.5. NI-SYNC 3.4.1
PXIe-1075 chassis
PXIe-5663 (2x)
PXIe-6672 Timing & Sync Card (slot #10)
I want to trigger the recording of my Digitizer with an external trigger.
The External Trigger is connected to PFI0 of the PXIe-6672 Timing card.
Then, the PXIE-6672 card routes the trigger to the backplane of the PXIe-1072 (Destination "NISYNC_VAL_PXITRIG0")
The PXIe-5663 are triggered with “NIRFSA_VAL_PXI_TRIG0_STR” as the source.
The trigger fires my PXIe-5663 correctly, but the timing is not tight (> 5ns).
I would like to use the PXI Star trigger instead, I think that I should be able to acheive much better synchronization with this.
But NI-RFSA won't let me do this:
When I try to call
"niRFSA_ConfigureDigitalEdgeStartTrigger(rfsa_session, NIRFSA_VAL_PXI_STAR_STR , NIRFSA_VAL_RISING_EDGE)", I get the error:
"Specified Route Cannot Be Satisfied, Because the Hardware Does Not Support It"
I don't understand why the PXIe-5663E would not be able to use that Route.
Any idea?
Regards,
Serge
Serge Malo, ing.
Concepteur logiciel
Software Developer
T (514) 842-7577 x648 | [email protected]

That explanation isn't quite right. Usually, even PXIe modules have a connection to PXI_Star. The PXIe standard added the PXIe_DStar trigger buses, and it also preserved the PXI_Star bus from the PXI standard.
However, there is an additional twist in this situation. I'm assuming that your PXIe-5663 includes a PXIe-5622 as the digitizer. It turns out that a synchronization technique called NI-TClk has eliminated the need for our more recent digitizers to rely on triggering from PXI_Star. I was able to find some documentation that includes this information, here and here. Given that, I think you have two options that should result in better synchronization.
The first option is to use TClk; I found an example program that demonstrates using TClk to acheive phase coherent signal acquisition across two 5663s. The second option is to use cables of matched length to connect two PFI front panel terminals of the timing board (6672) to the PFI1 front panel terminals of the digitizers (5622). The timing board would accept the external trigger on PFI0 and then issue triggers on PFI1 and PFI2 with around 500 ps of skew (manual, page A-4) . The digitizers would use NIRFSA_VAL_PFI1_STR as the trigger. I hope one of these solutions will meet the demands of your particular application.
I will also follow up with the owners of the RFSA product documentation to see if we can include a note about why PXI_Star is not supported in some cases.
James Blair
NI R&D

How do I calculate the max latency of a PXI 8135 (controller) to PXI 6528 (DIO) output?

We are using a PXIe- 8135 Controller and a PXI-6528 DIO module in a PXIe-1082 chassis. We are sending DIO input and output commands using Powershell in Windows 7 on the controller. Due to tight requirements I need to know what is the max latency from when the Powershell command is issued to when the read input or write output command will take place in the DIO I/Os.
If this should be in a different Community Board Location please let me know.
Thanks for the help in advance,
Dan_F

Hello dan_f,
As the latency of Powershell and Windows are not tested, it is hard to determine the latency of your setup. The latency from the PXIe-8135 to the PXI-6528 should be in the realm of nanoseconds. The PXI-6528 does have a couple of latency numbers that can be found within the user manual on Page 24, and they are as follows:
Minimum pulse-width for change detection - 150 µs
Propagation delay - 65 µs, typical
You may be able to do some testing to ballpark the latency of the controller OS/software side of the input/output commands, but depending on how critical this latency is to your measurements, you may want to look into using a real-time OS instead.
Chris H
Applications Engineer
National Instruments

After upgrading PXI controller, all PXI slots show "0" in MAX

I recently upgraded from the PXI-8176 controller to the PXI-8187 controller and all of the PXI slots now show "0" in the PXI slot value within MAX (under "Traditional NI-DAQ Devices"). I am using the PXI-1006 chassis.
What's the problem there? I have all 18 slots full with three different types of cards and I'd like to be able to tell which is which without having to hunt for it each time I swap out a card.
Thanks,
rgames

Hi,
MAX is reading the former configuration of your sys.ini file for the PXI chassis. So we need to delete that and create a new one.
The best way to solve your problem would be to right-click on PXI System under Devices and Interfaces in MAX. Choose "Delete All Identifications". Your PXI system should then say "unidentified" by it. Right-click again and choose "Identify As", then choose your controller. All your modules and an unidentified chassis should show up. Then right-click on the unidentified chassis and choose the chassis you have. Once it's been identified, press F5 to refresh MAX and then all your devices under Traditional NI-DAQ should have the correct slot number by them.
Let me know if that doesn't work!
Brian Spears
Applications Engineer

Convert PXIe-8135 controller to dual-boot Windows 7 and LabVIEW RT

Hello. I have a PXIe-8135 controller that originally was just running Windows 7. We are trying to convert it to a dual boot system to also run LabView Real Time. (There is host computer that will run LabVIEW 2014 with the RT module, and the controller will become a target).
I have created a FAT32 partition on the hard drive of the controller. Now, I’m trying to install the real-time OS with a USB flash drive made using the MAX utility, but I cannot boot using the USB drive for some reason. I keep getting the message “waiting for USB device to initialize”.
In BIOS, legacy USB support is [ENABLED] and boot configuration is set to [Windows/other OS]. I’ve tried removing the drive, waiting, and reinserting. I’ve tried two different USB drives (both 8 GB, different brands).
I’m not sure what to do next. Apart from the USB boot issue, is converting the PXIe-8135 even possible? I read about SATA/PATA hard drive issues with older controllers, but I don't know about this one.
Thanks, in advance, for your help!
-Jeff
Solved!
Go to Solution.

Per Siana's licensing comment, more information on purchasing a deployment license if you do not have one for this target can be found here.
The RT Utility USB key is used to set up non-NI hardware with LabVIEW Real-Time, but you should not need it in this situation to convert to dual-boot (*). Try this:
1. Since you already have a FAT32 partion created, go into BIOS setup and change to booting 'LabVIEW RT'.
2. The system will attempt to boot LabVIEW RT, see that the partition is empty, and switch over into LabVIEW RT Safe Mode. (this safemode is built into the firmware, which is why you don't really need the USB key).
3. The system should come up correctly and be detectable from MAX, and you can proceed with installing software.
4. To switch back to Windows, go back to BIOS setup and choose 'Windows/Other OS'
(*) One area where the USB key is helpful on a dual boot system is with formatting the disk. If you want to convert from FAT32 to Reliance on the partition designated for LabVIEW RT, the USB key lets you attempt to format a single parition and leave the rest of the disk untouched. If you format from MAX, the standard behavior is to format only one RT partition if found, but if not found, it will format the entire disk. Formatting from MAX on a dual boot system is consequently riskier and you could lose your Windows partition.

Memory upgrade on PXI-8105 and PXI-8106 controllers

Hi,
I've recently upgraded the memory of three PXIs; one with a PXI-8105 controller and two with PXI-8106 controllers. Both the 8105 and 8105 can take a maximum of 4GB (2x2GB) of DDR2-677 (PC2-5300) memory (see links below). However, on all three systems, both the BIOS and the O/S only see 3.3GB. Any idea why this might be the case?
I've tried flashing the BIOS (v1.4 on both PXIs), but with no success.
We're using COTS memory (i.e. not bought from NI) but I'd be hard pushed to believe that that is the cause of the problem.
Thanks.
Links;
Max memory capacity of PXI-8105 http://sine.ni.com/nips/cds/view/p/lang/en/nid/202630
Max memory capacity of PXI-8106 http://sine.ni.com/nips/cds/view/p/lang/en/nid/203442
BIOS upgrade page: http://digital.ni.com/public.nsf/allkb/9C9362590B05CD6E86256B270082164A
Solved!
Go to Solution.

Are these controllers running Windows? If so, this is normal expected behavior. I think it might have something to do with the fact that Windows reserves the rest of the memory for driver addressing (could be totally wrong there). The same thing happens on my Dell desktop PC with 4GB of memory in it.
Jarrod S.
National Instruments

No. of Channels in a PXI Embedded Controller

How many DMA channels are present in the NI PXI 8105 controller ? I have read that in NI PXI 7831 r, there are a total of 3 DMA channels, So if I am using 3 such cards I need to have 9 DMA channels in my controller for sending the data to these cards simultaneously.

I would rank your options this way (with #1 being the least demanding on your controller's memory):
1. FTP from the PC to the controller's hard drive, copy over the data, and then delete it. This way, the PC is doing all the work, and the controller is left to just gather data and do its own processing. The catch is that your network capabilities will determine how fast you can do this. Also, you'd have to make sure you aren't deleting data the controller hasn't processed yet.
2. Store the data in Shared Variables, so that both the controller and the PC can see and use the variables in real-time as they are updated. However, lots of shared variables = very messy code.
3. TCP/IP is your last option for transferring data. It will be the most demanding on the controller since it will need to open and close ports and handshake.
With all of these, you shouldn't lose any data if it's programmed properly.
Product Support Engineer
National Instruments

Motion control: PXI 7350 controller and UMI 7774 to interface with third-party driver UDK5114NW2

Dear community,
This is about Motion control in Labview: I try to control a step motor by using a PXI 7350 controller and UMI 7774 to interface with third-party driver UDK5114NW2. The problem is 5 Disable LEDS on UMI 7774 board always lit even when I check "enable" on "Motion I/O setting" in configuration of PXI 7350 motion controller. Furthermore, when I start to control step motor, it is not working and I found disable LED on UMI board still lit. I don't know how to solve this problem. Can someone help me to figure out? Thank you in advance!
Hau Nguyen.

Dear Community,
I said wrong, 4 disable LEDS on UMI 7774 Board instead of 5 as my previous post. Why nobody help me to solve this problem. I can not turn off disable LEDs on UMI 7774 Board so I can not start the strp motor. Please help me!
Hau Nguyen.

Pxi-8176 controller to read data from an instrument controlled by another controller

can i use pxi-8176 controller to read instrument data on the gpib bus from an instrument controlled by another pc gpib controller?

Thanks.
I understand what you're saying, but I'm also trying to understand why the following is not possible or is not more readily available:... Just as NI IO Trace (NI Spy) listens/eavesdrops to the GPIB real time, one would think that Labview would be able to do it also. One would think that just as NI IO Trace (NI Spy) publishes to a window/file/memory it shouldn't be impossible to publish to a string so that it can be processed real-time by some VI algorithm. If I think about NI IO Trace as a VI, I would think that it is already in a string format before it is published to the NI IO Trace window... why isn't that string available to Labview VIs block diagram?

How to configure Intel Pro/100 ethernet in PXI-8176 controller for RedHat Linux kickstart installation?

I have trouble configuring the Intel Pro/100 ethernet for the PXI-8176 controller during the kickstart installation. Did anyone have better luck?

Not with Linux but...
I had trouble setting it up for RT.
There is an issue with the chipsets used and the firmware of the 8176 when sizing the bus.
There was a KB article.
NI support should be able to chase down your details for you.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

What is it "USB-USB Network Bridge Adaptor" in my NI PXI-8106 controller?

What is it "USB-USB Network Bridge Adaptor" in my NI PXI-8106 controller?
Could I disable this device in "Device Manager". Because it is generating new network card and same application which is using PC information is using this "interface" to generate PC information for licensing.
I am using TestStand 4.01 and LabVIEW 8.5 and Acculogic ScanNavigator
Solved!
Go to Solution.

Hi JCC,
I don't think that's an NI software/driver, you can certainly try and disable it in Device Manager and see what effect it has. You can always enable it again if it causes problems when disabled.
Regards,
Imtiaz Chowdhury
Head of Digital Technologies
Brand786

Battery replacement in PXI-8187 controller (part no./procedure)

I need to replace the BIOS battery in a PXI-8187 controller (I am getting CMOS errors on boot). What is the part number for the battery and is there a suggested removal and replacement procedure (space is tight)?

Hi,
I believe the following KB should help answer your question. Thanks!
Replacing the CMOS Battery on a PXI or PXI Express Controller: http://digital.ni.com/public.nsf/allkb/64D90D3DE7ACFAA686256C550063C774
Cheers,
Carisa Leal
Applications Engineer
National Instruments

ADLINK PXIe-3985 Controller - NI PXIe-1062Q Chassis Compatibility

Similar Messages

Maybe you are looking for