PXI-5610 Specification

Hi,
Does anyone have NI PXI-5610 Up-Converter Specification? The link on NI web http://sine.ni.com/nips/nisearchservlet?nistype=psrelcon&sortby=localesort&nid=13478&lang=US&filter=... seems to point to PXI-567X specification.
Thanks.

Luyy,
Thanks for contacting National Instruments. This is correct, the 5610 is part of the 567X RFSG unit. Those specifications are the correct ones for that device. There are 5610 specific data in that pdf. Is there something in particular you are looking for?
Regards,
Kenn North
Senior Product Manager - Search, Product Data
http://ni.com/search

Similar Messages

NI PXI 5610 procedure in Cal Executive

I am currently working with the calibration executive software version 3.3 to calibrate some PXI-5610 cards. For the AmplitudeAccuracy_Super10MHz it has me manually input two measurements. In turn it appears to perform a calculation to determine the As found dB reading on the calibration report. However, I cannot seem to understand why two measurements are made and why the calculations appear inconsistent. For the same test at frequencies from 20MHz to 2.7GHz with a power level of -50dBm I input similar numbers for both values on all frequencies but received vastly different values.
Here is a specific example:
1005MHz @ -50dBm 256average 1st value: -50.54dBm 2nd value: -65.17 As found reading on report: -.5837
1500MHz @ -50dBm 256average 1st value: -50.67dBm 2nd value: -65.12 As found reading on report: -.8231
Does anyone know what the calculations are for this procedure and why/what I might be doing incorrectly to make my measurements inconsistent?

Hi Jerimiah,
I am taking a look into your question and I wanted to clarify a few things. What hardware are you using to make the measurements? Is it the recommended hardware or an unsupported model? Could you provide a screenshot of a couple rows of the AmplitudeAccuracy_Super10MHz section of the calibration report if you have it? It would also be helpful to have a screenshot of the prompts to enter the two measurements. I am not sure of the calculation that is made based on your inputs, however I suspect the difference may be related to the passband flatness. Let me know what other information you can provide and I will continue looking into an answer.
Steve B

Fail to calibrate PXI-5610

Sory if this isn't the correct Board to post this question but I couldn't find a Calibration Executive Board
I'm trying to calibrate a PXI-5610 with the Calibration Executive 3.4.1 and I have the latest drivers instaled on my pc, the probem is that the calibration doesn't start and it gives this error:
"Open VI Reference in cex_Instr_RFSigGen_Init.vi->_NI 5610_RFSigGen Setup.vi->_NI 5610_RFSigGen Setup.vi.ProxyCaller
VI Path: C:\Program Files\National Instruments\Calibration Executive\InstrumentDrivers\LabVIEW\RFSigGen\rssma\cex_Instr_LabVIEW_RFSigGen_rssma_Init.vi
LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Open the VI in LabVIEW using File>>Open and verify that it is runnable."
What can I do to fix this?
ps: I had to perform the calibration with Calibration Executive 3.2.1 because the client had some urgency...
Can anybody help
Thank's in advance
Bruno Ranhel

Hi BRanhel,
Please take a look at this knowledge base. This is for Calibration Executive 3.3.1 but it could work for the 3.4.1
Best Regards,
Vincent.O
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Été de LabVIEW 2014
12 présentations en ligne, du 30 juin au 18 juillet

Error 200617 on every usage of NI PXI-5610 that was previously working

Hello,
I have been trying to use the NI PXI-5610 RF upconverter (associated with a NI PXI-5441) with VIs that were previously working, including the NI GPS toolkit and RFSG example VIs. However, with the same setups as were working previously and the examples every time I now receive the following error
niRFSG
Commit.vi<ERR>The upconverter reported the following
error:
DAQmx Error
-200617 occurred:
Measurements: Output generation was aborted by the reverse
power protection circuitry of the device. Either the output signal exceeded the
output power limit, or power was being driven back into the output of the device
by an external source. Correct the problem, then generate the signal
again.
I have tried restarting, allowing 30 minutes warmup time before trying to use the RFSG and ensuring that the chassis fans are set to high with no change in the result.
I have also tried doing a self test on the RFSG unit in MAX which fails with error 200020.

Ok, well we can take the first steps via this forum post. If we need to RMA the PXI-board we can follow up on the created service request.
First I want to start troubleshooting the Self Test error.
I have attached a application which goes through all of the tests separately so we can determine where this error is coming from. Please run all of the test provide by this application.
Thank you in advance.
With kind regards,
Casper
Attachments:
Self Test Internal.zip ‏32 KB

Calibration Executive error during PXI-5610 sequence.

When running the PXI-5610 procedure in Calibration Executive, I get the prompt "NI-FGEN Create Arbitrary Waveform - Cannot write Real data when Data Processing Mode is Complex. Disable OSP or set Data Processing Mode to Real." The procedure the errors out with the same message when I click 'Continue'. I am using the NI PXI-5441 AWG (in place of the NI PXI-5421), but it is a selectable source during the initial configuration of the sequence.
Am I missing something? Am I doing something wrong? Is there a hiccup in the Calibration Executive software when PXI-5441 is selected?
Any help would be appreciated.

Hi DaRock,
We do not recommend making any changes to any of the test code for calibration as these may cause problems in your test sequence. We are still currently looking into the issue, however, in the meantime, if you would like to try and experiment some changes in the test code, please make sure to backup any original versions of the files you edit so you can load them back in they cause any problems.
Just for your information, in a standard NI-FGEN application, you can manually disable OSP by accessing the OSP Enabled property from the NI-Fgen property node under Arbitrary Waveform Output»Onboard Signal Processing.
Regards,
S_Hong
National Instruments
Applications Engineer

Using Calibration Executive for PXI-5610 using PXI-5124

Hi guys,
We've been trying to calibrate PXI-5610 but the Calibration Executive software pop up an error of PXI-5122 requirement but we don't have the module, we have the PXI-5124 instead. We have tried to use the unsupport but it's not working too.
We have found that their resolutions are different
PXI 5124 http://sine.ni.com/nips/cds/view/p/lang/en/nid/14231
PXI 5122 http://sine.ni.com/nips/cds/view/p/lang/en/nid/12615
Is this the cause of error? Is it possible to use PXI-5124 instead of PXI-5122?
FYI about our system
Chassis PXI-1010
Software: Calibration Executive 3.3
For any further recommendations, please let us know, thanks in advance.

Hi, somebody here?
I'm not sure if we have specified forum for this issue, please help let me know.
Thanks...

PXI 5610 problem

When running the PXI-5610 adjustment procedure in Calibration Executive , the main power suddenly shut off . then what problem will happen to the PXI 5610?

Thanks a lot for your reply.
After the PXI controller 's suddenly power off when performing adjustment , we restart the OS and found the PXI 5610's error infomation in the MAX : Error -200437,External calibration constants are invalid,and he card cannot be used in our Auto-Test-System anymore. I guess the calibration data in the EEPROM was missed or uncompleted,but i have no relevant softwre tools to read or write PXI-5610's EEPROM.
Could you give me some suggestions to solve this BIG problem? Thanks.

PXI 5610 Error -200437

The card shows the error infomation:Error -200437,External calibration constants are invalid. Whether performing an external calibration would solve the problem?
Thanks.
Attachments:
pxi 5610.jpg ‏124 KB

Which version of NI-RFSG driver are you using?According to this KB, you can upgrade to the latest NI-RFSG driver and solve the problem.
Thanks,
NI AE Emily

PXI-5610 RF Frequency Response adjustment

Hello,
I have noticed that adjustment for 5610 in RF frequency response is taking long time (about 2-3hr) with Cal exec 3.5, and I have tried to get the PXI chassis in a good enviroment and with some extra fans around since the adjustment has the legend "RF Freq. Response accumulated Meas. (Normalized to 45°C)
I am wondering if the enviroment has some important point here or it needs some update in a particular application inside Cal Executive 3.5?
I also have this question, Win7 has some advantage over WinXP in this particular or general adjustment?.
Br,
Omar

Hello Omar_Rdz,
Thanks for using NI forums! Calibration Executive usually takes a considerable amount of time for some of the PXI modules. By reviewing the Cal Exec manual it says that for the 5610 module it could take up to 240 mins (around 4 hrs). But definitely the temperature is a factor that can affect the performance not only of the calibration procedure but the whole system. Have you tried to execute the calibration when the controller and the chassis are cold? Also try to avoid dust accumulation in both the modules and the chassis because these can impact on the general performance of the system.
Answering your question regarding the OS, Win7 has a better performance compared to WinXP but it will also depend on what type of controller you are using. In order to give you a better answer, could you please tell me what controller and chassis are you using?
Regards,

PXI-9 specification

Does NI support the PXI-9 Trigger Management Specification? If not (what I actually see), is there any time frame when it will be available? Or maybe I just need to download some extension?
I got the latest software installed (VISA 5.4 & NIDAQmx 9.8), but there is no PXI-9 DLL module registered in the system. In my Registry I see just:
HKLM\Software\PXISA\Services\System Modules
HKLM\Software\Wow6432Node\PXISA\Services\Chassis
HKLM\Software\Wow6432Node\PXISA\Services\Peripheral Modules
HKLM\Software\Wow6432Node\PXISA\Services\Resource Managers
HKLM\Software\Wow6432Node\PXISA\Services\System Modules
There are no anticipated:
HKLM\Software\PXISA\Services\Trigger Managers
HKLM\Software\Wow6432Node\PXISA\Services\Trigger Managers
And obviously the system description file created by the PXI resource manager does not contain the [TriggerManager] tag.

NI supports the PXI-9 Trigger Manager specification with PXI Platform Services versions 4.0 and newer. What version do you have installed?
If you don't have it, you can download it here http://www.ni.com/download/pxi-platform-services-4.0/4353/en/

PXI-6608 specifications

Hi,
I have a question about the performance verification of the PXI 6608.
This is what I was able to perceive from the manual.
We have two modules:
CTR0: referenced to an external clock that has a minimum uncertainty of 0.75 ppb and generates a 400 s pulse to CRT1.
CTR1: is referenced to the internal 10 MHz OCXO and counts the number of cycles in that 400 s window: 400 * 10 MHz=4*10^9 . Any result different from this means an error.
Now to my understanding the performance verification is comparing the 10 MHz OCXO with the external clock. So by looking at the manual we have a uncertainty of 75ppb when the 10 MHz OCXO is on the slot 2: 0.75ppb * 10 MHz = +/- 0.75 Hz. BUT the performance verification assumes a tolerance of 0.1 Hz (10,000,000.1 < Hz < 9,999,999.9 Hz)
The calibration execute has the same approach as the performance verification,
Why does the PXI 6608 have a tolerance different from the manual?
Are we not testing the 10 MHz OCXO?

Hello,
In order to set the counter source to the timebase, you can use the the get/set/reset CI_CtrTimebaseSrc in order to set this in CVI. Please consult the DAQmx C reference Help for more information. Here are the functions if you can't find it in the help.
int32 __CFUNC DAQmxGetCICtrTimebaseSrc(TaskHandle taskHandle,
const char channel[], char *data, uInt32 bufferSize);
int32 __CFUNC DAQmxSetCICtrTimebaseSrc(TaskHandle taskHandle,
const char channel[], const char *data);
int32 __CFUNC DAQmxResetCICtrTimebaseSrc(TaskHandle taskHandle,
const char channel[]);
As for performing a loopback test to test its accuracy, this isn't the best way to do this because the source is creating a signal with relatively the same accuracy as you are reading in back on the same device. Knowing that this signal is accurate down to .7ppm, we need to apply a source for the counter that is much more accurate than this. First way to do this is to change the timebase source to the 10MHz clock like I mentioned above. The other way is to place the PXI-6608 in slot 2 so that it overwrites the 10MHz clock on the backplane. This 10MHz clock is used with PLLing the 80MHz clock that is normally used in counter tasks. Which slot do you have the PXI-6608 in? Could it be placed in this slot?
Jim St
National Instruments
RF Product Support Engineer

I want the specification manual for NI PXIe 5611

i want the specification manual for NI PXIe 5611

You can adjust the PXI-5610 IF input signal to fall between 15-35 MHz. The IF input range of the PXI-5610 cannot be changed from this 15-35 MHz span.
The PXI-5610 would be controlled via calls to the NI-RFSG instrument driver for NI's RF signal generator products.
There is no PXI-5610 only manual. The PXI-5610 is part of NI's PXI-5670, 5671, and 5672 2.7 GHz RF signal generators, whose manuals are available here:
http://sine.ni.com/nips/cds/nisearchservlet?nistype=psrelcon&nid=13478&lang=en&q=FQL:%28%28nilangs:e...
Regards,
Andy Hinde
RF Systems Engineer
National Instruments

PXIe acquiring and disk streaming speed

Good evening,
I need to acquire and stream to disk the status of N.8 digital lines at 100 MHz clock, idest 100MBytes/sec data rate, in continuously mode (without data loss) for five minutes.
I've thought to a PXIe configuration with:
PXIe 6544 High speed DIO,
PXIe 1071 Chassis,
PXIe Controller with solid state H.D. option.
Is that configuration enough?
Thanks.
Natalino Roberto

Hello Roberto,
According to NI PXIe-6544 specifications, you should be able to achieve typical data streaming rates 400 MB/s for acquisition and 400 MB/s for generation. So, you shouldn't face with any issue from this side.
Does your application provide an host interface communicating with embedded application? If doing so, you may need to design your application according real time guidelines.
Let me know if you need help or additional assistance.
Have a nice day.
Matteo C. - Test Engineer

How can i find out the resolution and accuracy of PXI-6602 module?

I have a 32 bit 8 channel PXI-6602 counter module. PXI card is interfaced to PC with MXI-4 link. How can i find out the resolution and accuracy of this system.What is the maximum accuracy and resolution i will get from this system. Because optical signal to cmos conversion signal is given as a input to the counter.

Hi chandhu,
Were you referring to the accuracy of the count register or the timing clock?
PXI-6602 specifications can be found in the NI 660x Specifications. The resolution of the count register is, as you’ve noted, 32 bits. This corresponds to a maximum count value of 4,294,967,295. As long as all of the edges are in accordance with TTL specifications, the accuracy of the count register is 100%.
On the other hand, the PXI-6602 baseclock accuracy takes on the baseclock accuracy of the PXI CLK 10 signal. Again, this is all found in the specifications.
You may also want to check out the NI 660x User Manual – it contains a lot of details on the operation of these counter/timer devices.
I hope this helps. Please post back if you have further questions.
Ed W.
Applications Engineer
National Instruments

PXI-7854R: how many times can bitfile be loaded to FPGA?

How many times can I reload bit file to my FPGA PXI-7854R?
I found a related question/answer for 783x but I'd like to know the limitation for PXI-7854R, specifically.
PXI-7831R http://digital.ni.com/public.nsf/allkb/91DE0C3B7740C287862574D300646369

For additional "you'll never wear it out fodder": we use Xilinx FPGAs, so their documentation will be the real source of the answer.
http://forums.xilinx.com/t5/Spartan-Family-FPGAs/How-many-times-I-can-reprogram-my-Spartan-6-device/...
and, slightly more entertaining discussion on the matter:
http://forums.xilinx.com/t5/Spartan-Family-FPGAs/How-many-times-can-you-re-program-a-Spartan-device/...
I guess it's not really "official documentation", but it's the right answer. I couldn't find anything more substantial in the ~10 minutes I looked.
Cheers!
TJ G

PXI-5610 Specification

Similar Messages

Maybe you are looking for