Synchronize 2 PXI Systems through GPS using PXI 6552

I want to synchronize two PXI systems separated by a distance of 5kms through GPS.
PXI 6682 is a timing and synchronization card which can be used to achieve this. I also have a requirement to use PXI 6552 HSDIO in my application. Few channels in PXI 6552 are free. So i want to know if it is possible to achieve GPS Synchronization of the two PXI systems using PXI 6552.
Regards,
Sundar Ganesh

Hi Ryan,
This is a system configuration which i am doing for a requirement. The requirement is RF Generation in one PXI system and RF Acquisition in another PXI system separated by a distance of 2kms. The applications that will be running at both these PXI systems may be started at different times. So i am thinking of using a PXI card in both the chassis to synchronize them through GPS.
Regarding this, i have already contacted the local NI FSE and together with him only we have decided to go ahead with PXI 6552 for GPS Synchronization. But i started doubting the usage of 6552 for GPS synchronization when i couldnt see the card in the list of Timing and Synchronization cards.
I have attached a schematic of the configuration. Let me know which PXI card should be used for synchronising these two systems.
Regards,
Sundar
Attachments:
PXI Configuration.JPG ‏21 KB

Similar Messages

How to upload a file in R/3 system through RFC using WebDynpro Java

Hi There,
we need to pass a file(mostly xml) using file upload feature in Webdynpro and then need to pass the file in R/3 system using RFC. What should be importing parameters for RFC and how should i implement the fileUploadUi in this case.
I have already seen example of how to add this in a table input form.
Any pointers will be great help.
Regards,
Sudhir

Use this code to convert the file content to bytes in WDJ:
Apart from the resource context attribute create a context attribute of type binary.
get the data from resource & convert it to binary & pass that to RFC. U can use this code for conversion
byte fileData[] = null;
try{
InputStream fileIs = wdContext.currentAttachCVElement().getFileData().read(false);
ByteArrayOutputStream bOut = new ByteArrayOutputStream();
int length;
byte[] part = new byte10 * 1024;
while ((length = fileIs.read(part)) != -1) {
bOut.write(part, 0, length);
fileIs.close();
fileData = bOut.toByteArray();
bOut.close();
} catch (Exception e) {
wdComponentAPI.getMessageManager().reportSuccess(e.toString());
Here getFileData reffers to the attribute of type resource. rest of the code u can use directly.
Use this code in your R/3 function module to convert the data.
*" VALUE(XCONTENT) TYPE XSTRING OPTIONAL
OUTSTRING TYPE STRING,
CONV TYPE REF TO CL_ABAP_CONV_IN_CE.
Convert data passed from WD Application.
CONV = CL_ABAP_CONV_IN_CE=>CREATE( INPUT = XCONTENT ).
CONV->READ( IMPORTING DATA = OUTSTRING ).
SPLIT OUTSTRING AT CL_ABAP_CHAR_UTILITIES=>CR_LF INTO TABLE IT_DATA.
DELETE ADJACENT DUPLICATES FROM IT_DATA.
Let me know if you run into issues, please award points accordingly.

Using Fieldpoint from Labview RT on a PXI System

I have a PXI system with Labview RT (PXI 8186 controller with LVRT ver 7.1).
I wanted to connect a FP remote I/O system to this controller. The Fieldpoint system I have has a FP-1000 RS-232 Network module.
I was hoping to be able to connect the FP-1000 to the serial port of the PXI-8186, and use the standard Fieldpoint VIs to write/read data (as you would from a Windows-based Labview app).
It doesn't seem to be that easy, trying to download any code with a Fieldpoint VI down to my RT target gives an error ("failed to load shared library FPLVMgr.dll on RT target device"). Looking through MAX I see that Fieldpoint drivers are not loaded on the RT target, and there is no option to load them there either.
So: Ho
w do I control my Fieldpoint units from my PXI System using Labview RT?
Any help would be much appreciated.
Thanks,
Ravid

Hi, Ravid.
Effectively, under LabVIEW RT, you cannot use the standard FieldPoint VIs to communicate to a FieldPoint module, since they are not supported. If you have a serial module, like the FP-1000 or FP-1001, you need to use Optomux commands to interface and communicate to it. You can find great examples on how to do the communication in the Example Finder of LabVIEW >> Hardware Input and Output >> FieldPoint >> Optomux >> and use any of the examples that use VISA to communicate to the modules. To run the examples, first target LabVIEW to your 8186 and open the example. Before running it, match the baud rate and address specified in your FP-1000 with the controls in the Front Panel. Also, verify that you have either an alias defined for COM1, or use AS
RL::INSTR1 for the VISA resource name. You will need to have VISA RT installed on your RT Target to be able to run this examples.
You can find the Optomux commands in LabVIEW under the Advanced FieldPoint palette. For more information on Optomux commands, you can take a look at the FP-1000/1001 Programmer Reference Manual
Let me know if you have further questions. I hope this helps!
Gustavo Valdes
Applications Engineer

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

Accessing a SWTICH and DMM cards in a PXI System remotely

Hi everybody,
I use a PXI system with a NISwitch PXI-2503 and NiDMM PXI-4070. The embedded controller PXI-8176 is running WinXP.
From a client machine I want to access remotely this cards. Via VISA Server it is possible to interact with the Switches using NI's driver NiSwitch. On the ther hand, I did not succeed so far to access remotely the DMM using the driver software NiDMM. I receive always the following error:
"Error -1074135030 occurred at niDMM Initialize.vi
Possible reason(s):
Error: (Hex 0xBFFA000A) Failure loading driver module."
My Software Versions are:
Labview 7.1, VISA 3.1, NI-DAQ 2.10, NiSwitch 2.20, NI-DMM 2.2.1
I have read that there are some incompatibilities between VISA and RDA conc
erning the TCP-IP port, but this problem should be solved in the versions I currently use.
Anybody out there who knows a workaround?
Thanx for any help in advance
Hannes Schmidt, Swiss Federal Institute of Technology, Lausanne

Hannes,
Unfortunately I don't think anybody here knows of a workaround because the application is not one that anybody has recently tested using NI-DMM. The easiest work around to me would be to use LabVIEWs remote front panels to do the acquisition. The only reason why using this might cause a problem is if you need to save data to file on a remote PC. So the only consideration to work with is to save the file on the host PC and then grab the file saved using FTP or something along those lines. That may be a much easier work around than trying to figure out what is going on with the low level DMM driver call. Hope this helps. Good luck with your application.
Best Regards,
Jeremy Ross
NI - Applications Engineer

Trans-receiver system using PXI

Hi,
I need to build a trans-receiver system using PXI. For the transmission part I can use a PXI 5652 to generate a single tone continuous waveform.
For the receiver part, I need an antenna to capture the signal transmitted by 5652 (which will have a transmission antenna ). The received signal will then be down converted by PXI 5601 (RF OUT of 5652 is connected to LO IN of 5601). The intermediate frequency will be then digitized by PXI 5622 (IF OUT of 5601 is connected to IF IN of 5622).
But my question is these connections are already there between the slots/chassis.(The next stage has I/Q demodulation but I want to get clear on this part first). But there is not output port on the PXI 5622, so how can I check the digitized output?
I have attached a file for reference.
Thanks,
Sharmi
Attachments:
Ref.docx ‏689 KB

Hi Sharmi,
To address your questions:
Is the data, after it is down converted and digitized by the 5622 is automatically sent to 5450?
No, the data is not automatically sent to the 5450. The digitized data is sent to the backplane and can be accessed on your controller/laptop through LabVIEW or the RFSA Soft Front Panel. The 5450 is used to take digital signals generated by LabVIEW and turn them into an analog signal. It is not used in any part of the downconversion process.
If you want to take the data that you receive from your 5663 VSA and send it to your 5673 VSG, you will need to do so using software. There are RFSA and RFSG examples that ship with the driver that you can use as a starting point on how to acquire a signal and send a signal using LabVIEW. These examples can be found by going to Start » All Programs » National Instruments » NI-RFSA (or NI-RFSG for generation examples) » Examples.
5450 has “400 MS/s I/Q Signal Generator” written on it, so does it generate I and Q channel data separately?
The 5450 does generate IQ data on 2 separate channels. LabVIEW is used to generate an IQ bit stream. The IQ data is combined after being upconverted with the 5611.
Also 5611 has “I/Q Vector Modulator” written. So, can it demodulate a signal (after it is split into I and Q components by 5450) and then combine the resultant output?
The 5611 is an upconverter and is used to take the IQ signals generated by the 5450, combine them, upconvert them from some IF frequency to an RF frequency and transmit them. It can be used to do some basic types of modulation, but not demodulation. The NI RF Signal Generators Help ( Start » All Programs » National Instruments » NI-RFSG » Documentation) has a section about the 5611 that includes the hardware block diagram and a more detailed explanation about each part of the block diagram. This is where you can find out more about what basic types of modulation the 5611 is capable of performing.
Let me know if you have more questions, I'd be happy to help.
Sarah Y
SDR Product Manager
National Instruments | Ettus Research

How to implement a dual booting PXI system using windows 7 and labview RT

Good Day
My name is Mariano Ocana from the University of Manitoba, and I want to implement a dual system using windows 7 and labview RT in a PXIe-1082 chassis with a PXIe-8102 embedded controlled (the chassis came with windows 7 installed). What are the steps to use both systems (windows and RT) in the same chassis?, in the NI help comes an example implementing a dual system using windows xp and RT, it is the same procedure?.
Thank you in advance for all your help.
Regards
M. Ocana

Greetings, Mariano.
The real issue you have to contend with is whether or not you have a LabVIEW RT license. If the 8102 controller was purchased Windows-Only, you likely do not have a license to run LabVIEW RT on the controller - you can purchase one, I think it's about $500, and at that point you can request a LabVIEW RT Configuration CD (that's not what it's called, but the sales guy will know what I'm talking about). The Config CD is a CD that will partition your controller correctly with both FAT32 and NTFS filesystems (in the appropriate way) to allow you to run Windows 7 and LabVIEW Real-Time on the controller correctly. Once done, you can then switch within the BIOS between LabVIEW Real-Time and Windows in order to dual-boot.
Either way, you likely need to contact NI sales to either purchase an RT license (if one was not received at the time of purchase) or to request a Configuration CD (it might also be called a dual-boot install CD or similar).
-Danny

PXI system configuration using GPIB interface

Being new to PXI systems, I'm trying to determine if there is a need to have a PXI-GPIB controller if I am configuring a PC(PCIe) controlled MXI Express kit???

Sorry if I wasn't clear before but you probably will not want to connect both a PCI-GPIB card and your PXI-GPIB card to your instrument. You will probably only want to use one or the other. I was just saying that you could have 2 different cards in your system to connect to different instruments if you wanted. MAX recognizes that there are 2 different GPIB cards and you choose which card to use before you communicate with an instrument. So if you are just wanting to communicate with a single instrument there is no need to have 2 GPIB cards unless you just want your GPIB card to be in your PXI chassis.
Brian Platt

I am using XNET CAN on a PXI system. When I modify the can database I get the error "the interface has already been opened.."

I have tried both building the XNET session from project explorer and by building a signal list in the VI.
Any suggestions? Thanks in Advance.

Thanks for the reply. I don't think I have any interface open. But to be sure, I rebooted everything - same result.
Is there some step in the project config that I am failing to do? In the PXI systems I had before XNET, I had to setup some CAN configuration stuff in MAX to get it to work, but I don't see that option anymore with XNET....
I have been sucessful in running XNET CAN VIs reading and writing the data from my database, but I stumble every time I add a signal or rename the database.
I made a simplified VI to illustrate, using a previously working database I now get the empty name message.(screen capture attached)
This is connected to a working CAN link, and I can see these signals in MAX properly.
Thanks in advance for your assistance!
Attachments:
vi_issue1.jpg ‏136 KB

Unable to connect to ECC system through stand alone JAVA program using JCO.

Hi All,
I want to connect to ECC system through standalone JAVA program using jco.while executing my java program it is saying that connection refused.
I am getting the error as shown below.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: CMALLC : rc=20 > Co
nnect from SAP gateway to RFC server failed
Connect_PM GWHOST=192.168.10.99, GWSERV=sapgw01, SYSNR=01
LOCATION    SAP-Gateway on host igm501 / sapgw01
ERROR       partner '192.168.10.99:sapgw01' not reached
TIME        Mon Sep 1 15:00:37 2008
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2821
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       239
ERRNO TEXT Connection refused
COUNTER     2
        at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeConnect(Native Method)
        at com.sap.mw.jco.rfc.MiddlewareRFC$Client.connect(MiddlewareRFC.java:11
25)
        at com.sap.mw.jco.JCO$Client.connect(JCO.java:3138)
        at JConnector_frmDesk.<init>(JConnector_frmDesk.java:91)
        at JConnector_frmDesk.main(JConnector_frmDesk.java:141)
I have already configured SAPDP01,SAPGW01 in my services file in windows\system32\drivers\etc\services.
What else i need to do to connect to ECC system through my JAVA program.Please help me in this regard.
Regards,
Ramana.

Hi !
Check this to verify that you are correctly using JCO:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8e7daa90-0201-0010-9499-cd347ffbbf72
Try to give in ashost="/H/saprouter/H/sap".
Regards,
Matias.

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.

Possible to start MXI-3/PXI system after PC booted?

Hi,
I'm new here, so I just asked this question in another thread through a reply. I didn't notice that it was already marked as solved, so I'm going to ask again in my own thread.
My problem may seem very related to the one of Kobi, but there are some differences which are holding my hopes up that the problem could be solved. The system setup summarized:
- PC (MXI-3)
->PXI1002 (Chassis1)
   ->PXI8335 (port1 - in)
   ->PXI8335 (port2 - out)
   ->PXI5122 (measurement)
     ->PXI1002 (Chassis2)
      ->PXI8335 (port1 - in)
      ->PXI5122 (measurement)
The aim is, as it is easily guessed, to be able to start the additional measurement devices at any time, even while the pc is already running.
The situation differs to Kobis' in one specific point: in my case the cards and all the equipment is at all times visible in MAX, even though I startet it after the pc booted. What does change is the pattern of the leds, and that the PXI cards don't pass the self test in MAX. The following screenshot shows the konfiguration of the system how it is observed after both ways of starting the complete system (pc first or PXI first).
(Even though I'm using an english labview version my MAX partialy remains german, I hope this is no problem.)
I tried to identify the PXI system and chassis, but couldn't get a different result. The NIscope VIs are orderly initialising and resetting all the sessions, but only if I switch on the PXI systems first.
So what do you think, could it be possible to achieve the goal of making it work, or should i stick to booting the pc after switching on the PXIs? I did some research and I know, that the installation guides do specify the order of switching the devices on, but I thought that this was only meant for installation/first run.
I would be really thankfull for any advice in this.
Regards
Max1744
Solved!
Go to Solution.

Hi Max,
there is no way around to first start the PXI. You always have to start the PXI System an d then the PC.
regards
Tobias

How to Generate Synchronized pulses across two separate cards on a PXI system

Hey,
I'm trying to generate three pulses from my PXI System for triggering purposes. I have two cards (PXI 6259 and PXI 6115) , each with two counter/timers on them. The 6259 has 32 bit timers, and the 6115 has 24 bit timers.
Up until now, I only needed two pulses. One was 180us long at 20 Hz, and the other is 5us at 20 Hz, starting 150us after the beginning of the first pulse. I was able to achieve this by generating both pulses on my 6115 card by triggering the shorter pulse off of the rising digital edge of the longer pulse and giving the DAQmx Counter/Timer task an initial delay of 150us.
The third pulse needs to be identical to the short pulse, only it needs to occur 20us early (130us after the start of the wide pulse). I tried to generate it using the same technique as I used when generating the short pulse, only generating the pulse and reading in the rising digital edge trigger on my 6259 card instead of the 6115.
The result was that my pulse trains were asynchronous and the pulse generated on the 6259 card was constantly shifting to the left.
This puzzled me, so I wrote up a little dummy program to test generating triggered pulses. The results were that when I generated two pulses on the same card, they were always synchronized; however when I generated pulses on separate cards, one of the pulses always shifted.
I was hoping somebody could suggest a reason that the pulses across cards are asynchronous even though I'm reading in a digital trigger and hopefully a way to rectify the situation and synchronize all of my pulses.

The problem, in a nutshell, is that the timebases on the two boards have manufacturing tolerances that will cause them to differ from one another. The accuracy error is a small fraction of a percent, but the effect on the phasing of your pulses will be cumulative. That's why you saw the one set of pulses "shifting to the left."
The solution is to make sure each board derives its pulse timing from a single common timebase. Fortunately, this is pretty easy to specify with DAQmx, just a little tricky to find. In the chain of VI's you call to configure the counter pulses, insert a DAQmx Channel property node. From memory, I *think* you should be looking under something similar to "Counter Output->General->Timebase->Timebase.Src"
Right click and create a constant or control to define the timebase source. You should get a dropdown list that includes a wide variety of choices. Among them are each of the boards' 20 MHz clocks. By default each task will use a timebase from its own board but this technique lets you route one board's timebase over the PXI backplane with that single property node setting. DAQmx does most of the dirty work behind the scenes.
-Kevin P

Soft-reset PXI-System

Good morning,
I try to execute a "soft-reset" on a PXI-System, but I can't found any nodes to do this.
With "soft-reset" I mean a function like the ABORT and the RUN button in a VI. More precise, if you connect to the real-time target via "debug application" you get the normal frontpanel of the VI which is actual executed. With abort/run buttons now you can "restart" this VI, so you don't need a hard reboot of the whole PXI-System which take a long time to get a "clean" system state.
Is this posible?!
Thanks a lot
Heiko

I'm wrestling with a similar problem, but I think I know how to fix it (just haven't had the time ...).
Background -- I "inherited" a LabVIEW RT program written using LabVIEW 7 (well before LabVIEW Project). The PXI code was packaged into an LabVIEW Library (.llb) file and copied by FTP to a known location on the PXI's disk. We used VI Server to locate the top-level VI on the PXI side and simply start it running. At the end of the routine, we stopped the code on the PXI. In this mode, the code was always present on the PXI, "ready to run", and we rarely had to reboot the PXI. As a side benefit, we could have multiple PXI routines sitting on the PXI, each matched to a particular routine on the Host, with each Host routine starting (and stopping) its appropriate RT "partner".
I'm currently working on the much-revised, much-improved version of this program running on LabVIEW 2012 under LabVIEW Project. My RT code is built as a Start-up Executable (.rtexe) and deployed to the RT Target as a Startup as part of the Build. At the conclusion of the Host program, the RT program also exits, which (as you note) causes the PXI to reboot, meaning we cannot restart for a minute or so. We also can't (easily) have multiple "pairs" of Host/RT routines that link themselves together at run-time (at least, not with a lot of extra work!).
I've been thinking about how to implement an "auto-restart" method for the RT code. I don't think it would be too difficult, but have not yet tried to implement it. My RT program consists of multiple parallel loops, with some initialization code at the beginning of the program (before the loops run) and some finalization code at the end. The main idea is to get the program simplified to a single loop (in my case, a Queued State Machine/Message Handler) that internally starts and stops the other parallel loops (probably through a Start Asynchronous Call and a local Shared Variable "Stop Loops"). My current Exit State sets "Stop Loops" to True, breaks the connections with the Host, and exits the QSM, leading to the termination of the RT code.
One idea I'm planning to try is to add an additional State, "Restart", that is called by Exit instead of exiting the QSM. This state would wait a few seconds (to let the other loops finish) and then perform (again) the initialization code that preceded the entrance to the QSM. Note that this inevitably sets the initial QSM State, so on finishing the Restart State, the QSM's Initialization State should be next, "... and away we go!"
If you try this and it works, please post a followup here. I'm anxious to try this, myself, but I've got other bugs to fix in this code before I can worry about "improving it" ...
Bob Schor

Using PXI-6682(H) in PXI Express chassis to replace backplane clock

I have a PXI-6682H in a PXIe-1075 which I use for event timestamping. I also have a PXIe-6672 card in the timing slot.
I would like to replace the 10 MHz backplane clock to use the 6682 as a GPS disciplined oscillator and synchronize multiple PXI chasses.
I understand from the block diagram in the manual that the PXI-6682H does not possess the connection to directly replace the backplane clock as the PXI-6682 does in a PXI chassis.
Is there any way for me to replace this clock? Perhaps using an external connection? If so could you briefly explain how this would work and what software steps would be required?

Hello Gregoryng,
It might work since the PXIe-6672 and the PXIe-6674T are both timing and synchronization modules, but the best option would be the PXIe-6674T, which is able to work with other protocols such as GPS while the other cannot. It seems that in the video they use GPS.
I think the PXIe-6672 will not work for this with the PXI-6682H, but you can give it a try.
The one in the video seems to be a PXIe-6674T.
Regards.
Ernesto.

Synchroniz​e 2 PXI Systems through GPS using PXI 6552

Similar Messages

Maybe you are looking for

Synchronize 2 PXI Systems through GPS using PXI 6552