Communication over the PXI-1010 backplane

How do I route the SCXI mux analog data to a PXI-6030 in slot 8. What is the routing syntax ?x! scy! mdz! CH.

Larry,
After you have configured the 1010, you can access the SCXI channel string using the following syntax,
obx!scy!mdz!CH
If you have not configured the chassis, go to this page on NI's site,
Configuring a PXI-1010 or PXI-1011 Chassis
AndrewM

Similar Messages

SAP PCK communication over the internet

Dear All,
Could you please give detailed information on SAP XI PCK and SAP XI communication over the internet?
1. I know there are few certificate issuing authority like DUNB..etc.
2.How SAP will identify the SAP PCK on WWW? will unique ip will be given to both the system.
3. If we need to contact these certificate,issuing authority,then how to proceed about it.
Thanks & Regards,
Himanshu Gaur

Hi Himanshu,
Please check the following links, they talk about Communication Between SAP XI Landscapes:
http://help.sap.com/saphelp_nw04/helpdata/en/7e/d7d43fb9490c65e10000000a114b1d/frameset.htm
also Integrating Smaller Business partners with PCK:
http://help.sap.com/saphelp_nw04/helpdata/en/32/92e5bced6cb441af4360cfcb8142f3/content.htm
and,
PCK Highlight:
http://help.sap.com/saphelp_nw04/helpdata/en/99/115281baba404890d2561617a78409/frameset.htm
I hope it helps,
Thanks & Regards,
Varun Joshi

Synchronous communication over the internet

Hi Experts,
I need a server-client based application model which:
- communicates over the Internet (both server and client could be behind a firewall/router).
- is capable of passing objects by reference (like Java's RMI-JRMP/RMI-IIOP).
- can handle client side call-backs.
- is part of the standard Java API.
I thought about RMI-IIOP.
Can RMI-IIOP handle all of the criterias in the list?
Is there any other way to implement such an application in Java?
Thank you very much in advance!

ejp wrote:
- is capable of passing objects by reference (like Java's RMI-JRMP/RMI-IIOP).That is meaningless and impossible.That is meaningful and possible and implemented since Java 1.1 for remote objects which have been exported. That is the essence of RMI and RMI/IIOP.Nope. No way to move the actual instance of an object from one application to another.
Conceptually it is. Which is exactly what RMI does. And exactly what I meant.
- can handle client side call-backs.That doesn't make much sense. Did you mean server side call backs? Where the server is attempting to initiate (start) a connection with a client? If so that is almost always a bad idea.A callback is a callback into the originating client. I don't know why you're making such a fuss about that. I wouldn't call it a server-side callback myself.Because there is no need to differentiate that requirement unless it means something different than a standard type of RMI call.
Then you are going to need to write a lot of code for a real application.
Nothing canRMI and RMI/IIOP can do all that. They can do everything the OP specified except callback through client-side callbacks, and there are commercial solutions available for that.Again - moving the instance. Not the data. Not simulating it via a behavior interface.

DataInputStream communicating over the socket BUT reading Garabage

I have written client/server applications. The client is written in Java and the Server in c++. There is a problem when I send data from the server to the client. Initially, I can recieve the data fine, however on the second read, I start to get all these garbage values. I'm not sure why this could be. Here is a look at the Java code. ostream1 and istream1 are used from the DataInputStream class. Can anybody give me any suggestions. Thanks.
     addr=Address.toString();
     ostream1.writeLong(addr.length());
     ostream1.writeBytes(addr);
     ostream1.flush();
while(istream1.readInt() != -100000); //used as handshake with c++
ostream1.writeLong(-9999); //used as handshake with c++
ostream1.flush(); //two previous lines work fine.
w=npanele.getWidth();
     h=npanele.getHeight();
     ostream1.writeLong(4);
     ostream1.writeLong(w); //send the width and height in pixels
     ostream1.writeLong(h);
     ostream1.flush();
while(istream1.readInt() != -100000); //starts to read garbage here
//never reads the -100000 sent by the server.
ostream1.writeLong(-9999);
ostream1.flush();

No, that cannot be it because it reads in all the previous information fine. And I used the same data types through out my code. It seems as though java client and c++ server are not synchronized with one another. That is why I check for the -100000. It's a sort of handshake implementation.... I send one long value from c++ and then in the java code I had to call the readInt() in a while loop as opposed to calling it just one time and getting the correct value which is what should happen. It calls the readInt() function maybe 12 times before exiting the program and everytime it calls the function, I get some wierd value. Anyway, I guess I will just keep on running thru the code until I can figure out what's going on.

Error-200284 for PXI-1010 MXI-3 fiberoptic connection to a PXI-6533.

In the instruction lab in which I work, we have two types of systems:
1)SCXI-1000 chassis connected by copper to a PXI-6035E card in a PC.
2)PXI-1010 chassis connected by fiberoptic from a MXI-3 to a PXI-6030E card in a PC. A PXI-6533 handles the digital I/O.
We have LabVIEW8.5.1 running on both types of systems. On the SCXI-1000 system, the LabView example Acq&GraphVoltage-IntClk-DigStart.vi runs just fine. It does not run on the PXI-1010 systems. Instead, I eventually get Error-200284. In both cases we use PFI0 or PFI1, and digital ground, for the triggers, connected to lines 38, 39, and 33, respectively, in the SCXI-1302 terminal block, which connects to an SCXI-1180 feedthrough panel.
I searched the forums and all ni.com for information on this problem, and have not been able to find any relevant information.
Joseph D. Rudmin

Hi Joseph,
I think I'm starting to understand the problem you are having. Unfortunately, since on a SCXI module, all channels are generally multiplexed through AI0, the PXI/SCXI backplane only shares the necessary channels i.e. one AI channel and any required timing signals. Therefore, even if though you are using the SCXI-1180 module with a SCXI-1349 communicating adapter, you will not be able to access the other channels on your PXI-6030E since there is no physical connections being made to those channels in the backplane. There are 2 solutions around this problem:
1. You can use an SCXI-1349 cable assembly to connect the front of the PXI-6030E module to the back of the SCXI-1349 adapter. This way the unused pins on the DAQ module can be accessed through the SCXI-1180.
2. You can decide not to use the SCXI-1180 and simply use a standard 68-pin terminal block with your PXI-6030E and connect your 5V sync pulse to the PFI pins. This will still allow you to sample off of the SCXI-1100 since those channels are connected via the backplane.
Here's a link to our online KnowledgeBase article which talks about this issue.
Can I Connect The SCXI-1180 To An SCXI Module In A PXI-1010 To Use The Additional Analog Input Chann...
Please let me know if this answers your question.
S_Hong
National Instruments
Applications Engineer

PXI 1010 Chassis power failed.

Now one PXI 1010 backplane power failed on PXI section, but SCXI side can power on.I ever checked nad reset circuit breaker, no help. I need your help! Who will give me a kind hand?

Roger,
If you have already checked the circuit breaker and have verified that it is not tripped, more than likely there is a power failure with the PXI portion of the power supply. I would create a phone service request at www.ni.com/ask. We can only handle returns through our phone support. At that point, if you indicate that you have a damaged product, we can work with you to get it fixed.
Regards,
Andrew M
National Instruments

Process Failure when communicating over MODBUS using LabVIEW 2011 and DSC

I'm currently trying to read from a PLC's holding registers using MODBUS/TCP. I've confirmed that the PLC is updating the values and responding to MODBUS communication correctly using a third party program called Modbus Poll. However, when I try to poll the PLC using LabVIEW's shared variable engine, I am unable to read any values from the same addresses that I'm viewing with Modbus Poll.
My setup simply consists of a PC connected directly to the PLC over Ethernet, with no router in between. I am using LabVIEW 2011 SP1 with the DSC module.
I opened the NI Distributed Systems Manager to view the status of all shared variables in the Modbus library that I created and I've noticed that the CommFail bit is permanently set to "true". All other variables with a "read" access mode report "Process Failure". I've tried restarting the process as well as stopping and starting the local variable engine with no success. I've also restarted my computer several times to see if any services were failing, but this does not seem to have fixed the problem.
I finally resorted to monitoring communications over the network card that I have the PLC plugged into via Ethernet using Wireshark and I've found that while Modbus Poll is communicating with the PLC, many MODBUS and TCP packets are sent and received. However, when solely using LabVIEW or the NI DSM to communicate with the PLC, there does not appear to be any communication over the network card.
Something that may be worth noting is that I was able to communicate with the PLC and read values from it with the DSM on just one occasion, when I first figured out which addresses I should be reading from. It all stopped working shortly thereafter. Prior to this, "CommFail" was not usually set to "true" with my current configuration. Thinking that it was my firewall, I have since turned my firewall off, but this seems to have had no effect on the problem either.
Any help on this matter would be appreciated.
Solved!
Go to Solution.

Just a thought but I think the register addresses used by LabVIEW are one off of the actual register #. I was using a CRIO as a modbus IO Server and had to shift the register addresses by 1 to get things to work correctly (can;t recall if it was +1 or -1). This is documented somewhere on ni.com but can;t seem to find it now. But here is another link that may help:
http://zone.ni.com/reference/en-XX/help/371618E-01/lvmve/dsc_modbus_using/
Dan

Communication between the secondary community VLANs hosts

Hi Guys,
The hosts in the secondary community private VLANs are permitted to talk each other. If there is no promiscuous port/host defined, will the community VLAN hosts be able to talk each other?
Or all the intra-community VLAN traffic is routed via promiscuous port?
CF

Hi CF,
If there is no promiscuous port/host defined, will the community VLAN hosts be able to talk each other?
I suppose you want to ask whether hosts in different community VLANs will be able to talk to each other if there is no promisc port defined. The answer is - no, they will not be able to communicate, but they would not be able to communicate even if the promisc port was created. Their communication over the promisc port would be allowed only if the device connected to that promisc port was willing to do hairpin routing - that is, receive and forward a packet back the same interface. Usually, you do not want your different community VLANs to communicate to each other - that is why you created them in the first place - so you'd usually make sure that whatever device is connected to a promisc port, it does not do routing or is prevented from hairpin routing via an ACL, for example.
With respect to mutual communication of hosts in a single community VLAN - these hosts will be able to communicate to each other just as if it was a totally normal VLAN. The existence or non-existence of a promisc port has no influence on this.
Feel welcome to ask further!
Best regards,
Peter

QoS for IP Communicator over WLAN

Hi, We are in the process of deploying Cisco IP Communicator 2.1.1.0 but we are having voice quality issues when use IP COmmunicator over the wireless...We want to know if the AP 1200 series can be configured for QoS or the configuration has to be done only the switch port level..Thanks in advance..Our laptops are 802.1p enabled. Raj.

depends if you're using vlans on the ap or not (if yes configure qos on the ap, if no configure them on the switch.
the following is a useful resource on wireless qos...
http://www.cisco.com/en/US/customer/products/ps6441/products_configuration_guide_chapter09186a00805d9209.html

Zones networking over the wire

Currently Zones talk to each other using the loopback. In doing so this way, it will bypass the firewall settings, because it is talking over the loopback.
To prevent two zones from talking to each other, you add a route rule which totally blocks ALL communication between the two zones.
This is a MAJOR weakness. If there a way , or does Sun have plans to allow you to block traffic between two zones, and force communication over the wire? That way it can't talk over the loopback, and will send the traffic to the default route, thus when it goes to the other zone it will have to go through the firewall rules.
I am really suprised this was not how zones worked in the first place. Going over loopback is fast, but very unsecure. Blocking them completely is too restrictive.

Currently Zones talk to each other using the loopback. In doing so this way, it will bypass the firewall settings, because it is talking over the loopback.
To prevent two zones from talking to each other, you add a route rule which totally blocks ALL communication between the two zones.
This is a MAJOR weakness. If there a way , or does Sun have plans to allow you to block traffic between two zones, and force communication over the wire? That way it can't talk over the loopback, and will send the traffic to the default route, thus when it goes to the other zone it will have to go through the firewall rules.
I am really suprised this was not how zones worked in the first place. Going over loopback is fast, but very unsecure. Blocking them completely is too restrictive.

SX-20 Camera Communication Over UTP

We are using an SX20 codec with the PrecisionHD 1080p4xS2. As our camera and codec are more than 3 metres apart, we are using 2 breakout cables (one on the codec, one on the camera) for the proprietary HDMI/control plug (instead of using the supplied cable). The breakout cables are CAB-PHD4XS2-SPLIT=. Getting an image over HDMI through the breakout is working. Using the remote to dial a number, access menus etc is not working. There does not seem to be any communication over the UTP cable that carries the IR requests back to the codec. We are using a power supply to power the camera, but when this is removed the camera still seems to be powered via POE.
Do we need a custom pin UTP cable between the breakout devices? We have used a standard CAT6e cable and a standard cross-over cable. We have also tried swapping pins 3 and 7, and pins 3 and 6, as we have seen to be possible solutions posted on the web.

Questions about the SX20 codecs are probably better asked in the TelePresence section of the forums, so you may wish to move your discussion to there.
In any case, the maximum supported distance for the Visca Control (serial cable) is 20m / 65.6 ft, so you shouldn't have issues extending it to only 3m.
It is recommended that the camera is powered separately when using such an extension to the cable, and that the +12V pin on the Visca Control cable is not connected, apart from that, a straight through cable is required.
Wayne
Please remember to rate responses and to mark your question as answered if appropriate.

Can I use "Getting_Started_with_SCXI-153X" with the NI PXI-1010 ?

I have the NI SCXI-1530 and the NI PXI-1010 and I'm having trouble getting the "Getting_Started_with_SCXI-153X" software to work with this arrangement. Can these devices use the NI software or will it have to be modified or rewritten for this specific situation?

Hello bhooks,
I would highly reccomend that you avoid using the Getting Started with
SCXI 153x VI as it is written in Traditional DAQ. There is a buch
better VI written using DAQmx that can be found in the NI Example
Finder. There are 2 ways to open up the NI Example Finder:
1) On the LabVIEW startup screen select the down arrow next to the "Open" button and select "Examples..."
2) If you have a VI open, go to the Menu Bar and select Help>>Find Examples...
Once the Example Finder is open, click on the Search tab. Type in
"1530" as your keyword and then double-click on "1530" when it appears
in the "Double-click keyword(s)" box. There should be an example
in the examples box called "Cont Acq Accel Samples-Int Clk-Analog
Start-SCXI 153x.vi". Double-click on it to open it.
Alternatively, you can find this example at the following file path:
C:\Program Files\National Instruments\LabVIEW 7.1\examples\DAQmx\Analog In\Measure Acceleration.llb
Once this is open you can find instructions by turning on Context Help
and hovering over the icon of the VI in the upper right-hand corner OR
you can go to the Menu Bar and select File>>VI Properties.
When the VI Properties window pops up, select "Documentation" for the
category. The Example Finder will also have these instructions in
the Information Box when you select the example.
I hope this helps!
Eric
DE For Life!

How to use the PXI's 10MHz backplane clock to synchronize two or more 6031E boards?

Hi,
I'm trying to use two 6031E boards to acquire multiple channels Analog Inputs, and I'd like to sync them with the PXI backplane clock (not the RTSI bus). I found an example from NI, "Two E-Series Shared ScanClk.vi", and modified it a bit. But I'm wondering if the two boards must have the same acqusition rate? e.g. Can I have 1 board acquiring at 1kHz while the other one at 20Hz? and if yes, how do I do it?
Your input will be very much appreciated. Thanks!
Dan
Attachments:
mod_Two_E-Series_Shared_ScanClk.vi ‏148 KB

Unfortunately, E Series boards cannot synchronize with the 10 MHz PXI backplane clock. They do, however, have access to the PXI trigger lines, which are basically the RTSI lines. Except for line 6 which is the star trigger line. They can only read from this line.
The example program you have selected will definitely be part of your solution. It allows you to share the scan clock timing signal between two boards. If you would like the slave board to acquire at a slower scan rate, you could always route the master's scan clock to one of the slave's on-board counters which can act as a frequency divider. The output of this counter can become the new slower scan clock for the slave board. Use the Generate Pulse Train shipping example VI as your frequency d
ivider. Finally, make sure you route the signals appropriately and you'll be in business.
I hope this helps!
Russell McMurtrey
Applications Engineer
National Instruments
http://www.ni.com/support

Anyone know what can cause the MXI-3 and PXI-1010 chassis to prevent PC bootup?

Situation: The PC locked up with the display blank. The PC would not bootup (not even POST) after power was cycled (several attempts).
Resolution: Simple. The chassis power was cycled and the PC was fully operational.
Background: The PC is a Dell Dimension 733 running WIN98 and used daily for production test. The test program is a combination of TestStand, instrument dll's and Labview.

Hi,
If the pci-mxi-3 is locking up the computer the most common cause for this is a bad mxi-3 card. To check this you will want to try the mxi-3 card and chassis with another type of computer. If it doesn't boot in more than one computer of different types you will want to return the board to national instruments for repair.
Another thing that we have seen in some computers is interference or noise from the power supplies interrupting communication through the mxi-3 devices. The only thing you can really try in this case is to move the pci-mxi-2 card to another slot in the pc and see if it works, or try using a different type of pc.
Power cycling the chassis is not a valid solution as this will drop the mxi-3 link and then you will no longer be able to talk to de
vices in the pxi system. You always need to successful power the pxi-mxi-2 card and chassis before you power up your pc.
Best Regards,
Amy Hindman
Applications Engineer
National Instruments

How to send a SQUARE WAVE to PXI-6259 over the LAN

howcan I send a SQUARE WAVE to PXI-6259 over the LAN, is
there any example or link any one can send me , thanx in advance.

Dear HaI L,
I managed to send a test signal (sine wave) to the device by choosing
the test panel option and choosing Analog output. In the analog output
I could many channels to choose from. ai0, ai1.ai2 and ai3.
I did this by right clicking NI PXI-6259, in the NI DAQmx devices
located in the Devices and Interfaces and choosing test and saw it on
an Oscilloscope without using the NI DAQ OPC capabilities, and I cannot
understand this thing.
1)How can it be possible without making a NI DAQmx channel and Variable?
2) I cannot create any channels in the devices and interfaces located
in My system but I can create NI DAQmx Global Virtual channels easily
in Data neighbourhood in the remote system, Plz tell me why?
3) I want to create a program and choose a channel to send the
signal, can I choose the channel that i create in the remote
system device ? and if yes how can I choose this ?
Thanx in advance.
Sincerely,
Munir Afzal Bhatti.
Attachments:
max.jpg ‏2305 KB

Communication over the PXI-1010 backplane

Similar Messages

Maybe you are looking for