Cross talk in BNC 2090

Thanks for the information provided. I followed your advice by connecting
DGND1 with a wire to USER1 and DGND2 to USER2. But I still get cross talk.
It also puzzles with a fact that when I connect a signal source (from a
functional generator) to ACH1 but in fact the signals show up on the
Biobench screen as ACH0 as defined. So my hunch is that something wrong
happens to BNC 2090 or the PCI-MIO-16XE-50 board installed in the computer.
Would it be possible for me to send in the BNC2090 for a check? If so, what
are the procedures to follow.

We handle all repair requests over the phone. The procedure is as follows:
1. Go to www.ni.com/ask to create your own Service Request number (SR#). Choose the Phone NI option. Fill in the form with the appropriate information.
2. Call the support number that is given to you and enter in your SR#. You will be directed to an Applications Engineer (AE) that will assist you through the process. The AE will be able to answer any questions you may have about the repair process.
Have a great day.

Similar Messages

Can I use a SH68-68EPM cable to connect a PXI-6704 with a BNC-2090?

Hi,
I was wondering if I could use a SH68-68-EPM cable to connect a PXI-6704 (sitting in a PXI-1002 Chassis and talking to my (Windows 7) PC via a PCI-8331) with a BNC-2090-box.The manual suggests to use a D1-cable but maybe it is possible to still get the analog outputs from the BNC-box although the cable is different?
Thanks for your help!

Hi cars10,
The BNC-2090 is not compatible with the NI 6704 due to pin mapping. You can use BNC connections via the CA-1000 or use a card from the analog output series family with the BNC-2090A or BNC-2110 as described in the user manual.
Regards,
h_baker
National Instruments
Applications Engineer
Digital Multimeter Resources

RE: local variable cross-talk?

Jeff
A global can be considered as a variable to the entire code, where lots of
different vi's can operate it. Locals only have any meaning within their
own vi, or instances of their own vi.
If anything writes to a particular global, whether in reenterent vi's or
not, it's available everywhere in the code.
What you were asking was about locals though. If a vi is non-renentrant
(i.e. as they come out of the box) then the values in the locals are vi
specific, no matter where the vi is, where it was last used, it retains the
data from it's last operation. If it is re-entrant, then the values in the
locals for each occurance of the vi are its own for EACH instance, i.e. just
like different locals in different vi's, it doesn't matter where else the vi
is used, the data held is that from the last operation of that specific
instance.
Simple way to demonstrate this. Make a vi that has one numeric control,
then code in +1 and get it to write to a local variable for that control.
Throw in an indicator to wire out the result of what is written to the local
for the control.
Then take this vi, put it in a for loop, then put another copy in the for
loop as well. Wire the indicators to the side of the for loop and create
indicator arrays for them. Get the loop to run 6 times say. Now try
running this with the vi in the for loop non-reentrant and then reenterrant.
One way the arrays will contain either all the odd no.s 1,3,5,7,9,11 and
then the other array 2,4,6,8,10,12 (don't know which array will be which,
depends which executes first in the for loop of this example). The other
way they will both be 1,2,3,4,5,6. In the first example, the same vi has
run 12 times, i.e. one copy of the vi which retains its info and is called
in many places and therefore only has one set of values, and the other with
two re-enterant copies where they have their information specific to that
instance of them i.e. effectively they are different vi's. Both ways are
useful, depends what you want.
If you're looking for a use for non-reenterant vi's then consider this:-
For instance. Supposing you get many things to try to write to a global
array of numbers, and you have two vi's one "A" writes to the first element
in the array and the other "B" writes to the second element. Because in LV
you have to read a global first and then write to it to perform a change,
these independant vi's "A" and "B" (be they re-enterant versions of the same
vi, or different vi's), can be performing the tasks simultaneously in the
code. I.e. "A" reads, "B" reads, "A" writes, and "B" writes over the top
with a modified version of what it read, and "A"'s changes are lost. This
is what's known as a "race condition" as "A" hadn't finished and "B" needed
to know what "A" was going to write before "B" performed "A" read. Try it,
hours of fun if you code this kind of thing in inadvertantly!
If the same vi is used, and is not re enterant, it can only run in one
instance at a time, hence two read / write operations cannot be performed
together, problem solved. Unless that gives you timing issues of course,
waiting for one to finish, to write the other......but that's another whole
can of worms.
cheers
Tim Price
This e-mail, its content and any files transmitted with it are intended
solely for the addressee(s) and are confidential and may be legally
privileged. Access by any other party is unauthorised without the express
prior written permission of the sender. If you have received this e-mail in
error you may not copy, disclose to any third party or use the contents,
attachments or information in any way.
-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Jeffrey W Percival
Sent: 29 November 2001 21:12
To: [email protected]
Subject: Re: local variable cross-talk?
Another useful reply! What a great news group this is.
One last thing I wanted to ask about, though, is global vs. local. I see
you talk about globals, but in fact the variables in my subVI's were locals.
I can easily understand the behavior I observed accompanying the use of
global variables, But I guess the use of the word "local" stumped me.
Should I interpret "local" in LabVIEW's sense to mean "local to all
instances of this VI"? And global to mean "visible to all instances of this
VI as well as other VI's"?
-Jeff
Tim Price wrote:
This facility is actually very useful, for instances where you want to
encapsulate some code so that it can only run in one place at a time,
i.e.
global arrays that are written to in more than one place. This method
can
eradicate race conditions completely for example when used like this.
There
are multiple other uses as well.
However, using a vi as a module of code, to run in more than one
instance at
a time simultaneously, re-entrant is the way to go. Just make sure you
debug it first!!!
Remember though, just because a vi may be re-eneterant, doesn't mean
that
everything inside is; sub-vi's, Globals etc. The classic one I've seen
is
where people think that a re-enterant vi is talking to it's own copy of
any
Globals used within it, i.e. counters etc., where in actual fact of
course,
they are all using the same Globals.
Worth playing with a few examples to get familiar with it.
Tim Price
Jeffrey W Percival, Senior Scientist and Associate Director
Space Astronomy Laboratory, University of Wisconsin - Madison
1150 University Ave, Madison, WI 53706 USA
608-262-8686 (fax 608-263-0361) [email protected]
http://www.sal.wisc.edu/~jwp

Tim Price wrote:
Tim, thanks very much. I'll try the experiment you suggest.
Thanks for taking the time.
-Jeff
Jeffrey W Percival, Senior Scientist and Associate Director
Space Astronomy Laboratory, University of Wisconsin - Madison
1150 University Ave, Madison, WI 53706 USA
608-262-8686 (fax 608-263-0361) [email protected] http://www.sal.wisc.edu/~jwp

Using PFI1-PFI9 on BNC-2090 to trigger recording on a PCI-MIO-16-XE-50

Hi there,
I've got another question about triggering using the BNC-2090. Now I can get an output of a particular digital line from the DIO-96 I'm using using a ribbon connector connected to CB-50 Connector block. This connector block has individual line outputs, so is it possible to take one of these individual lines, plug it into PFI1-PFI9 of the digital connection area of the BNC-2090 and have the PCI-MIO-16-XE-50 use the appropriate digital PFI line as a trigger? I ask this because I assume the default trigger line whey I click "Use external trigger" in NIDAQ Tools for Igor Pro is PFI0, so I was wondering if there's a way to change that. Thanks a lot!
Arul Thangavel

Arul,
Yes, you can connect the dio line of the dio-96 to any of the PFI lines that are located in the pinout of the bnc-2090. The default line to be used for triggering an acquisition is PFI0,but you can modify that.
In LabVIEW, you can select the proper PFI line by configuring it in the "AI Start.VI", or by using the "AI Trigger Config.VI" before using the latter VI.
In LW/CVI, you can also select the proper PFI line by configuring it with the "DAQ_Config" function call and with the "Select Signal" function call.
Hope this information is helpful.
L Aguila
Applications Engineer
National Instruments

CROSS TALK - VIC FXO

Hi all,
I am facing the problem of cross call.
What happen is that,when someone is in a call and other people need to make a new call it dial to get voice tone, but it receive the cross talk (not the voice tone).
Someone known what could this?
The configuration is following:
voice-port 2/0
input gain 10
output attenuation 10
no vad
cptone BR
timeouts initial 4
timeouts call-disconnect 5
timeouts ringing 20
timeouts wait-release 5
timing sup-disconnect 1500
voice-port 2/1
input gain 10
output attenuation 10
no vad
cptone BR
timeouts initial 4
timeouts call-disconnect 5
timeouts ringing 20
timeouts wait-release 5
timing sup-disconnect 1500
Thanks

Please attach your entire running configurations. What version of IOS do you have? You may want to check CSCsg47594.

Cross talk

Hi,
I am trying to figure out cross-talk data for the different USRPs. I have seen some figures in this forum of ca -30 dB between Tx and Rx. Is this correct? In principle I am mostly interested in the coupling from Rx to Tx and -30 dB would be acceptable for my application, but I would like to have this confirmed.
BR,
Robert

This sounds in line with my experience. This post may help too.
I've tried things like transmitting with one USRP, and receiving on another...but it's not like you turn the Tx1/Rx1 chain 'off' if you just want to receive on the Rx2 path. So...you'll likely see the crosstalk anyway if you desire to transmit and receive on the same frequency.

How to count TTL pulse by DAQ through BNC 2090?

I'm trying to count the TTL pulse from a APD by DAQ. There are some very nice discussions about this issue in this board. However, I am a novice and not sure about the hardware connection. The signal from APD is delievered out through a BNC cable and I'm trying to deliever this signal to DAQ through BNC 2090. I tried just simply connect the BNC cable to ACH0 and tried running the vi's, such as "Count_Edges.vi" and "Count_Events.vi". But I got no counts. I noticed that both these vis are actually reading signal from PFI port. That could explain why I got not counts.
So now the problem is how should I connect my signal in a BNC cable to the DAQ and have the counting working? Thank you for your help.

Hi Opal,
Here is what you should do for the hardware connections with these devices:
- connect your external signal to the BNC-2090
- connect the 68 pin connector on the BNC-2090 to the 68 pin connector on your DAQ board. You should have a 68 to 68 pin cable for this.
That is all that is involved with the hardware connections. After this, you should be able to read your signal. Here is the link to a helpful DAQ manual with in depth getting started information: DAQ Getting Started Guide. I hope that you find this information helfpul.
Regards,
Hal L.

No BNC-2090 Accessory Option in MAX/No Signal

I'm using an AT-MIO-64E-3 card for A/D signal collection, with the card connected to a BNC-2090 signal box. The Measurement and Automation Explorer doesn't have an accessory selection for the BNC-2090, when I try to run the test panel I get no signal, and VI's give the error -10003 from AI Hardware Config. I'm running Windows 2000, and this problem arose when I upgraded from NT to 2000. Is there an easy fix for this, or will I need a newer A/D card? Signal is getting to the BNC-2090, it's just getting lost somewhere between the 2090 and Labview.

Hello Dstockw,
Are you using AC Coupling with this application? If so, E-series cards do not support it and will give error -10003 from AI Hardware Config.
What version of the NI-DAQ device driver are you using? NI-DAQ 7.0 is a fairly recent version that supports that board (using Traditional DAQ). If you are using an older version of NI-DAQ, try updating it and run the test panel again. NOTE: If you update the driver, be sure to uninstall your previous version of NI-DAQ first.
Check to be sure that you have properly installed the BNC 2090. Information about installing and configuring this device can be found at:
http://www.ni.com/pdf/manuals/321183a.pdf
Also, be sure that you are using a proper cable to connect to your AT-MIO-64E-3 card. Th
e recommended cable is the SH 1006868 shielded cable. Try double-checking the installation/configuration of this DAQ card by looking at:
http://www.ni.com/pdf/manuals/320517g.pdf
You may also want to try running the E-Series Diagnostic Tool. This tool will test the functionality of your card and run a self-calibration on it. You can find this test at:
http://www.ni.com/support/selftest/
Try these steps and let me know if you have any further questions.
Scott Romine
National Instruments

Strange voltage observed in NI BNC 2090

Hi all, I have a BNC 2090 and AT-MIO-16O-2 DAQ board. I am recently
(starting this morning) experiencing strange voltage readings from the
ACH1, 2,3,4and 5. The voltage input from ACH0 is about -.2V; and range
from -1 to -3 in other channels. These happens even when nothing is
plugged into the BNC other than the its connection to the DAQ in the
computer.
any suggestion on what might be happening?
Roshan.

This is actually very common. When nothing is connected to the pins the voltage will charge up on the leads. Sense the lines are not connected to anything and the voltage has no where to go the lines will normally completely saturate the capacitors on the board.
This is not a bad thing and it should not affect your measurements, if you do not scan the channels that are not connected. If you are worried about the unused floating signals, you can wire the unused inputs to ground.
If you are performing measurements and notice that the inputs are floating you should check your grounding methods. In general use RSE for floating sources, NRSE and DIFF for grounded signal sources. If you want to use NRSE or DIFF on a floating signal you will need to add a 10-
100kOhm bias resistor from the negative lead to AIGND to reference the signal. Refer to this KB for more help.
http://digital.ni.com/public.nsf/websearch/DF70FCE03D397BFE86256A3700780FFA?OpenDocument
I hope this helps,
Joshua

Socket cross-talk.... multiplex read buffer?

i am using only 1 socket:
[pc #1] <--- socket ---> [pc #2]
concurrently:
the [pc #1] thread is sending input data to the [pc #2] thread.
and
the [pc #2] thread is reading input data from the [pc #1] thread.
this is of course, ok
the [pc #2] thread is sending results data to the [pc #1] thread
and
the [pc #1] thread is reading results data from the [pc #2] thread
some times "cross-talk" depending on timing
[pc #2] will read the output it sent to [pc #1] as if it
were input from [pc #1]
maybe multiplex the read buffer?
how to do that?
other ideas?

i am using only 1 socket:
[pc #1] <--- socket ---> [pc #2]You are using two sockets, one at each end. You are using one connection.
concurrently:Bilaterally, or in full-duplex mode:
the [pc #1] thread is sending input data to the [pc #2] thread.No it's not, it's sending data to the connection.
and the [pc #2] thread is reading input data from the [pc #1] thread.No, it's reading data from the connection.
this is of course, okIt's OK once you describe it correctly.
the [pc #2] thread is sending results data to the [pc #1] thread and the [pc #1] thread is reading results data from the [pc #2] threadNo, see above.
some times "cross-talk" depending on timing
[pc #2] will read the output it sent to [pc #1] as if itwere input from [pc #1]
TCP/IP doesn't do that. Any 'crosstalk' is due to a programming error on your part.
maybe multiplex the read buffer?Maybe fix your code?
other ideas?Maybe show us your code here?

BNC-2090 & PCI-6036E: MIO power or LPM power?

Which power mode do I choose?
There's a choice of "MIO-16" and "LPM-16" on the back of the BNC-2090.
Neither the string "MIO" nor the string "LPM" appears in the owner's manual for the PCI-6036E [322339c.pdf].

The PCI-6036 is an MIO board so you'll want to use the "MIO-16" selection. The MIO boards are our newer series of boards whereas LPM series is our older legacy boards.
Erick D.
NI Applications Engineer

Floating voltage in BNC 2090, PCI 6024E

Hi experts, I have a single ended connection on a BNC 2090 connected to PCI 6024E board. However, when I leave it connected(without any input) I see that the voltage gradually increases to +10V. Even when I input a signal, I see that the 10V forms a baseline, which hinders any measurement. Is this some sort of grounding problem? Kindly post any helpful thoughts on this matter. thanks. Roshan.

Roshan,
I believe that the 2090 has a switch for each channel which configures the inputs for either Single Ended configuration (AI channel is read with respect to your 6024's Analog Input Ground) or Differnetial configuration (AI channel reads signal on BNC connector differentially). Ensure that the terminal configuration you have programmed for you channel matches the terminal configuration selected by the switch on the 2090. If you do not make any explicit setting, the 6024 will default to differential mode.
I hope this helps,
Dan

Bnc 2090 offset and other errors

I have a bnc 2090 plugged into a pci 6070e. The BNC is currently plugged into a DC variable power supply. Right now, when I change the voltage on the power supply, the other channels reflect this change even though it is only plugged into one channel. I have read about ghosting and even when I lower the sampling rate, the problem is not fixed. There is also an offset that is showing up on the MAX test panels and in my VI. This offset steadily decreases and seems to arbitrarily change. Whats going on here?

About the offset another point, I assume you use a measurment on one coax connector (+ and - in one connector), in that case your switch should be set to RSE.
In MAX this should be set as well (and in your VI) instead of the default differential measurement.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Compatibility between BNC-2090 and PXI-6541

Can we use BNC-2090 terminal with HS-DIO PXI-6541 ?
John Doe

Hello,
As it said in the BNC-2090 documentation :
BNC-2090 – A shielded, rack-mountable adapter with 22 signallabeled
BNC connectors and 28 spring terminal blocks to simplify
connections to your I/O signals. The BNC-2090 includes component
locations for passive signal conditioning and connects to any 68-pin
M Series, S Series, E Series, or B Series DAQ device.
So your card isn't a DAQ card but a HS-DIO card, so it doesn't appear in the supported cards list.
So it shouldn't be compatible.
Please contact your commercial contact at NI France for more informations.
Regards,
Pierre R...
Certified LabVIEW Developer

68-pin connector on BNC-2090

Can either of the 68-pin connectors on the BNC - 2090 be used for input?

The 68-pin connectors essentially feedthrough the BNC-2090 and the BNC channels are tied to these pins in parallel. This document explains this in a little more detail:
http://digital.ni.com/public.nsf/websearch/FDE04C8A1E4481B486257199005D71A7?OpenDocument
So you do have access to those pins on the front and the back of the 2090. You just have to be careful that you don't double-drive the same line.
Garrett H
National Instruments

Cross talk in BNC 2090

Similar Messages

Maybe you are looking for