Making own pxi system?

I currently am working on a project in which i am going to be placing a pxi system with some components inside a larger box with some other hardware connected to it. Basicly what i want to do is to get rid of my chassis. I would like to have my pxi cards just connected striaght to the backplane i believe, no shell/caseing. NI does not offer anyhting like this but I was wondering how I would go about it and what would i need. I found this backplane: http://www.comtel-online.com/pxi.htm but still im not sure if thats all I would need or what. I know PC hardware really well, but when it comes to PXI im a little foggy. Please let me know how i can accomplish this. I thank you for any help you can give.
Thank you very much!
-Mark

Similar Messages

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

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 System does not appear in MAX 4.0

Hello,
My system comprises LabVIEW RT 7.0, target PXI-8176 controller in PXI-1000B chassis, PXI-6608, PXI-6711, NI-4472, PXI-6704, PXI-6527, PXI-8423/4, PXI-8422/4. This has been stable for two years. I recently solved an RS-485 2-wire mode configuration problem, using information in a discussion forum thread, by upgrading to NI-VISA 3.4.1 and NI-Serial 2.5.5. MAX 4.0 was installed as part of this process. Everything seemed to work fine. I instructed a distant customer to do the same, but they experienced some difficulty. To ensure we were working from the same starting point, I re-initialized my PXI system, using PXI Format Hard Drive Disk, version 7.0, from MAX 4.0. I configured TCP IP address, and re-installed the RT software on the PXI controller.
Next, I attempted to configure the PXI controller and chassis, in MAX, to update the pxisys.ini file, but the PXI System (Unidentified) does not appear under Remote System>>IP address>>Devices and Interfaces. Similarly for the serial ports. This worked before, but I cannot get this back. What is wrong?
Best regards,
RonC

Hello S. Bassett
The controller is definitely booting in RT mode -- I can still run my applications on the RT target. VISA seems configured properly also, I can make VISA calls without error in the application.
In fact, the RT system seems to work correctly, and I contemplated leaving it as it is. However, the fact that MAX does not recognize the PXI system makes me nervous, and I cannot do some of the things I may want to do, for example independently configure RS-485 port wire mode in MAX (the ports do not show up either). Traditional DAQ configuration in MAX works.
After your last post, I found a brief reference in MAX Help that indicated "PXI Services" had to be downloaded before the chassis could be configured. But there are no other mentions of what PXI Services is, what it does, or how to install them. PXI Services does not show up as RT Software in MAX. In the Windows Add/Remove Programs control panel in Windows, in the National Instruments software section, there are two apparently related entries:
- NI PXI Platform Services for LabVIEW Real-Time 1.5.1
- NI PXI Platform Services for Windows 1.5.1
But, I cannot get these to install on the RT target. Not knowing what was causing the problem, I uninstalled everything from National Instruments, deleted all folders, and reformatted the PXI platform. There was one problem during this process -- after uninstalling NI-Serial 2.5.5, it does not get removed from the Add/Remove programs control panel. There is still a registry key that the uninstaller did not remove -- presumably this is the problem.
I have rebuilt everything, but could not get NI-Serial to install -- the installer thinks there is a newer installed on the RT target (there isn't) and refuses to install NI-Serial 2.5.5. So right now, I cannot install NI-SERIAL (any version), or remove the 'existing' NI_SERIAL, because it isn't actually there, and there is no uninstaller.
Otherwise, everything seems to be back to where it was before I "upgraded" to NI-VISA 3.4.1. This was NI-VISA 3.0, LV RT 7.0, and MAX 3.0.2. I have not yet been able to install NI-Serial, so I cannot yet see if I have also restored my original problem -- the one that led me to have to upgrade NI-VISA and NI-SERIAL in the first place.
Most importantly, there is now a "PXI Services v1.1.2" installed on the RT target. I am quite sure the problem with MAX 4.0 not recognizing my PXI system has to do with the absence of this driver on the RT target.
Thanks again for your interest and help,
RonC

Error in installing NI 488.2 in PXI system

Hi, all
We have a VA-HR instrument and agilent power supplies, which we are being controlled through USB interface in one computer. all the supplies and VA-HR are controlled via single USB.
Now we want to controll these instruments from another computer which is a PXI system with NI PXI 8105 Embedded controller. (PXI system contains Windows XP service Pack 2)
When the USB cable was plugged into PXI system, it gave folowing message:
Found new hardware, USB serial controller D, and also the GPIB-USB-HS.
So we came to conclusion that it requires USB serial controller D drivers as well as GPIB-USB-HS(GPIB-USB-B) drivers.
For that i did download NI 488.2 2.7.3 from NI website and tried to install that into PXI SYSTEM. But during installation, the process rolled back from driver installation and gave an error. i tried this for atleast three times. In other PC the same .exe source of NI 488.2, successfully installed NI 488.2 software without any error.
I can't understand why this NI 488.2 is not being installed.
LABview 8.6 is already installed in the system.
In short i want to connect my Power supplies and VA-HR to PXI system. Please help me out in this installation error.
thanks and regards,
vishal sakarvadiya

muks
Proven Zealot
What is the error you are getting?
HI, muks
Now I have attached the images with this message which shows sequence of process that was followed during installation of NI 488.2 in PXI system.
STEP-1...
STEP-2...
STEP-3....
STEP-4.....
STEP-5.....

SAP XI 3.0 - Error while reading the ID of own business system from the SLD

Error while reading the ID of own business system from the SLD for system Quality (QOC) and Client 100.
I get this error in the SXMN_MONI. The business process is that the Interface to send master schedule and finished inventory from the legacy system to SAP to create planned orders in SAP for all Plants.
I could able to get "SUCCESSFULLY PROCESSED" in development and production. But only in Quality I getting this error. Could anyone help me to fix this issue.
thanks...

Probably, its due to incorrect RFC Adapter properties in config.
Go to Integration COnfiguration. Double Click on the Business System for your R/3 system. On the right hand screen, Click on Service-->Adapter Specific Parameters.
Check whether the Logical System Name comes up as SAP<SID> and whether R/3 system ID and Client are appropriate.
If these values are inappropriate, make changes to the corresponding Technical System defined in the SLD. After you have made the necessary corrections, come back to Integration COnfiguration, Double click on Business SYstem for R/3. Switch to Edit Mode. Click on Service-> Adapter Specific Parameters and then click on the Icon between Apply and Cancel buttons, inorder to compare with SLD and make those values reflect in config. Then click on Apply and Save the Business System.
After this, you can retry sending the message.
Rgds
R Chandrasekhar

Error while reading the ID of own business system from the SLD for system

Hello,
I try to send master material data from a 4.7 system via XI 3.0 to an autoID Infrastructure system 2.1. All Communication Channels, Receiver Agreements, Receiver and Interface Agreements are configured. The IDOC gets propper into the XI, Inbound Message is "green". Now, I get the following message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
<SAP:P1>ZTA</SAP:P1>
<SAP:P2>013</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading the ID of own business system from the SLD for system ZTA and client 013</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anybody help me?

Probably, its due to incorrect RFC Adapter properties in config.
Go to Integration COnfiguration. Double Click on the Business System for your R/3 system. On the right hand screen, Click on Service-->Adapter Specific Parameters.
Check whether the Logical System Name comes up as SAP<SID> and whether R/3 system ID and Client are appropriate.
If these values are inappropriate, make changes to the corresponding Technical System defined in the SLD. After you have made the necessary corrections, come back to Integration COnfiguration, Double click on Business SYstem for R/3. Switch to Edit Mode. Click on Service-> Adapter Specific Parameters and then click on the Icon between Apply and Cancel buttons, inorder to compare with SLD and make those values reflect in config. Then click on Apply and Save the Business System.
After this, you can retry sending the message.
Rgds
R Chandrasekhar

Error while reading ID of own business system from the SLD

HI guys when trying to send Idoc from my R/3 system to SUS i am getting the following error in XI
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
<SAP:P1>DSM</SAP:P1>
<SAP:P2>900</SAP:P2>
<SAP:Stack>Error while reading ID of own business system from the SLD for system DSM and client 900</SAP:Stack>
I checked in sxmb_adm on both the ends on Xi as well as on my SUS server in Xi the role is the Integration server and on the SUS it is Application server also checked SLDAPICUST which is configured rite. Plz help me to come out of the problem.
Regards,
Anand

Hi Anand,
check the two thing's in XI.
1. First created technical system in XI to identify your XI server (Web as ABAP and Web AS Java)
2. Create the business system based on above technical system and select the role of business system is Integration server.
URL : http://<hostname>:<ICM Port>/sap/xi/engine?type=entry.
3. Create the technical system based on your SAP R/3 system.
4. Create the business system based on your SAP R/3 system.
here you need to select role of business system : Application system.
related integration server is : <XI System SID has to come>
and try to refresh the initical cache once ...
http://<hostname>:<j2ee stack port>/CPACache/refresh?mode=full
after all the things post what is the problem you are faceing.
Regards,
Venu.

Error while reading ID of own business system from the SLD for system D18

Dear guru's,
I have almost completed a file2proxy scenario but I'm stuk on the following.
When sending a message the outbound adapter says:
<b>Error while reading ID of own business system from the SLD for system D18 and client 200</b>
What's the problem? I'm using a HTTP connection in the comm. channel. In this http connection a user with SAP_ALL is defined.
Any suggestions?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
<SAP:P1>D18</SAP:P1>
<SAP:P2>200</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading ID of own business system from the SLD for system D18 and client 200</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Login to system D18 and client 200 and check the TC SLDCHECK and also as per my pervious message check the entries in the SLDAPICUST, it should point to the Server on which SLD is present usually XI server https.
Actually what happens in this error is when you are done with the configuration part in the ID, you are trying to eceute the scenario File to proxy, when it comes to identify the receiver system which is D18 clnt 200, it goes to SLD to check it and SLD is trying to ping to the machine D18 this connection is set from the TC SLDAPICUST on the machine D18.
here the problem is that either the D18 is not able to ping to the SLD and also try refreshing the SLD cache.
Hope you problem is fixed

Error while reading ID of own business system from the SLD for system DPI

Hi All,
My sceanrio is Proxy to JDBC. and its B2B. am sending the data from BI system and based on the country field from the source, table is decided and value is updated in the table.
In RWB->Component Monitoring->Adapter Engine->Test Message, I have given the Sender component,Receiver Party,Receiver component,Interface,Interface Namespace,userid and password,Quality of Service and pasted the payload.
Now I am getting the error :Error While Sending Message: Error stack from response: Error while reading ID of own business system from the SLD for system DPI and client 001 Internal error in Landscape Directory
Please help me out.
Thanks
Kiruthi
Edited by: kiruthiga balusamy on Nov 24, 2009 4:02 PM

Hi,
Check transaction SLDAPICUST for correct SLD configuration.
http://help.sap.com/saphelp_nw70/helpdata/EN/0b/8512417301ee6fe10000000a1550b0/content.htm
~Sanv...

RPM_FIN02 - Receiver of IDoc is its own logical system

For one particular portfolio item, I run the RPM program RPM_FIN02.
This results in an IDoc creation.
Next, I checked the status of the IDoc (RPM > Base System Interfaces > SAP Financial and Controlling Integration > Data Distribution From SAP FI-CO to SAP xRPM > Check Inbound Processing).
This shows the status "29 - Receiver of IDoc is its own logical system".
As a result, the Internal Order costs (including the ones posted from cProjects) do not get pulled into RPM Financial Planning.
Please advise.
I do not have the technical understanding of this issue, and would therefore need a little more than the mere technical jargons and terms to be able to resolve this.
Thanks for understanding.

Hi,
Very briefly,
-Assuming your RPM system is independent of your ECC box. But RFC connected.
-RPM_FIN02 is for pulling in financial data onto RPM item from (object linked) Internal Order(IO)/PS Project(PSP).
-RPM_FIN02 do not recognize/goto cProjects for financials.
-cProjects can have its own account assigned IO/PSP
-cProjects Dashboard, (if all is well incl. evaluation) should display costs from assigned IO/PSP
-This cost does not reach RPM item
-Source of cProjects- if it is created within cProjects or from RPM Item, does not matter.
thanks,Mathavan

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

IDOC error - Receiver of IDoc is its own logical system

hi,
i have a requiremnt to generate the IDOC for the same and same client. actually i have to get the data from application server and i have to generate the IDOC.
for this i have created a Zreport and passed the data from application server to segment and i called the
FM "MASTER_IDOC_DISTRIBUTE". after executing the Zreport, IDOC is generated and show the error
status as 29.i.e. Receiver of IDoc is its own logical system.
my logic is as follows.
MOVE 'LS' TO w_edidc-rcvprt.
MOVE 'SBECLNT130' TO w_edidc-rcvprn.
MOVE 'ISU_MR_UPLOAD' TO w_edidc-mestyp.
MOVE 'ISU_MR_UPLOAD01' TO w_edidc-idoctp.
pls let me know the solution for this problem.
Regards,
Balu

Hi Reddy,
please let me know how did u solve this issue, even i have the same requirement and am gettign status 29.
Thanks
Rakesh

ERROR B191 - IDoc has its own logical system as receiver

I everybody, i'm tryng to execute a package to charge a ODS from another ODS (Datamart) but the process ends with the error "IDoc has its own logical system as receiver", can you help me with is?
What should be the reason for this error? What can i make to solve it?
Thanks to all

Hi Reddy,
please let me know how did u solve this issue, even i have the same requirement and am gettign status 29.
Thanks
Rakesh

Making own pxi system?

Similar Messages

Maybe you are looking for