Mux80 AIN Expansion Board Datasheet

The Mux80 AIN Expansion Board serves to provide an additional 80 analog inputs to any compatible LabJack.  It uses 10 multiplexer chips connected to AIN4-AIN13 and splits each channel into 8 additional channels.  When a specific extended analog input channel is read on a U6, UE9, or T7, the digital output MIO lines are automatically set and the correct analog channel is read.  The Mux80 has a built-in DC-DC converter which provides the upper and lower rail voltages necessary for powering the multiplexer chips.

Three vertical DB37 connectors provide an easy interface to connect 24 AIN channels each. The remaining connector brings out unused connections (FIO, DAC, etc) from the LabJack, along with the last 8 AIN channels. There are a total of 84 available analog inputs when used in conjunction with a U6, UE9, or T7.

For screw-terminal access, connect a CB37 Terminal Board and reference the chart printed at the top of the Mux80 for connections. 

Subsections

Features

• 80 Multiplexed Channels (or 40 Differential Pairs)

• Built-In DC-DC Converter

• OEM Capability

• Easy-To-Use High Density Connectors

• Snaptrack/DIN-rail compatible, with TE Connectivity P/N TKAD

Connection Options

The Mux80 can be connected several ways.  The images below demonstrate use with the CB37 Terminal Board, and several 3ft DB37 Cables.

When connected to a CB37, there is a quick way to determine which screw terminals can be used as analog inputs; reference the chart printed on the top of the Mux80, also shown below for reference.

Table 1. CB37 to MUX80 connection chart

_{* When taking differential measurements, this channels negative is on a different MUX80 connector.}

_{##N: When taking differential measurements, this denotes the negative channel for ##. For example, AIN56 (48N) is the negative channel for AIN48.}

The table above defines the pinouts of X2-X5 in terms of a CB37.  If you are not using a CB37, see the CB37 Datasheet to translate the CB37 terminals to DB37 pin numbers and/or Appendix A.

X2

Connector X2 is essentially a duplicate of the DB37 connector on the main device, except AIN4-AIN11 are instead AIN120-AIN127, and AIN12-AIN13 are not connected to anything. On connector X2, AIN0-AIN3 are duplicates of the main device, as well as FIO, DAC, etc.

AIN0-AIN3 are available on the built-in terminals of the T7 and also on AIN0-AIN3 of a CB37 connected to X2.

AIN120-AIN127 are available on X2, along with the DACs and DIO.

X3

AIN48-AIN71 appear on the AIN0 through FIO7 terminals of a CB37 connected to X3.  Note that terminals labeled DACx and FIOx on the CB37 are used as analog inputs.

X4

AIN72-AIN95 appear on the AIN0 through FIO7 terminals of a CB37 connected to X4.  Note that terminals labeled DACx and FIOx on the CB37 are used as analog inputs.

X5

AIN96-AIN119 appear on the AIN0 through FIO7 terminals of a CB37 connected to X5.  Note that terminals labeled DACx and FIOx on the CB37 are used as analog inputs.

Example

A signal is connected to FIO6 on a CB37.  The CB37 is connected to X4 on the Mux80, so on the chart, under X4 and FIO0-7, locate AIN88-95.  So the signal is connected to AIN94.  To read AIN94 simply perform a standard AIN read for analog input number 94.

Using Differential Analog Inputs with the MUX80

Built-in

The built-in analog inputs AIN0 through AIN3 can be used normally when using the Mux80 (but AIN4 through AIN13 are not available). This allows:

• Positive channel = AIN0 paired with negative channel = AIN1

• Positive channel = AIN2 paired with negative channel = AIN3

See 14.0 AIN of the T-Series Datasheet for more details on built-in AIN.

Extended Range

For extended channels, the positive channel can be any channel (even or odd) listed as a positive channel in the chart below. The negative channel number is the positive channel number plus 8 (listed under the “Negative Channel” the chart below).

Example 1: The positive channel is connected to AIN102 (AIN6 on the CB37 connected to X5). The corresponding negative channel is AIN110 (DAC0 on the CB37 connected to X5).

Example 2: The positive channel is connected to AIN64 (FIO0 on the CB37 connected to X3). The corresponding negative channel is AIN72 (AIN0 on the CB37 connected to X4).

Note that for some differential pairs, the positive and negative are located on different connectors.

Table 2. Channel numbers for analog inputs based on differential connection and CB37 connector

See 14.2 Extended Channels of the T-Series Datasheet for more details on extended ranges.

Specifications

Ground Offsets

A single-ended analog input measurement is the voltage difference between the analog input and ground at the A/D chip on the main device (e.g. U6 or T7).  If the voltage provided by a given signal is different than the voltage at the A/D chip, that results in error.

Suppose, for example, a thermocouple is connected to AIN0 and the adjacent GND terminal on a CB37, that is connected to X3 on a Mux80 via a 3 foot cable, and that is connected to a T7.  Suppose the remote end of thermocouple is at a temperature such that it is creating a voltage difference of 1600 µV between the AIN0 and GND terminals on the CB37.  Typically, the voltage at the CB37-AIN0 terminal will be the same voltage presented to the A/D chip, but the voltage at the CB37-GND terminal might be 280 µV higher than ground at the A/D chip due to other currents flowing on ground.  That means the A/D chip will see 1880 µV rather than 1600 µV, which is an error of roughly 7 degrees C.

Voltage drop on the AIN connection is not a concern as the only current on the AIN connection is the bias current.  The typical AIN bias current of the U6 or T7 is 20 nA, so even if the path from terminal to A/D chip had a high resistance of 10 ohms that would only be 200 nV of error.

Voltage drop on the ground connection can sometimes be a concern and is called ground offset error.  Just the normal power supply current of the Mux80 and CB37 can cause GND terminals on the CB37 to be 100s of microvolts higher than ground back at the A/D chip.  Any current sunk to GND by user connections will increase this difference.

One solution is to use the AGND terminal on the CB37.  AGND has its own dedicated path back to the main device, so as long as the user does not sink any current into AGND it will be at the same voltage as ground at the A/D chip.

To measure how much offset exists from a particular GND terminal to ground at the A/D chip, simply jumper the GND terminal in question to an unused AIN terminal and measure the single-ended voltage from that AIN channel.

Suggestions & Solutions:

A.  Use differential analog inputs.  Differential readings take the difference between 2 AIN lines and thus are not affected by ground offset.  For example with a thermocouple, connect thermocouple+ to a positive channel (AIN48 for example) and connect thermocouple- to a negative channel (AIN56 for example).  A resistor (100k would be typical e.g. CF14JT100K) from the negative channel to GND is also required, as the thermocouple cannot be totally floating (see the Differential Readings App Note).  Now configure and read AIN48 as differential.

B.  Use AGND for all passive sensors such as thermocouples.  Make sure not to connect anything to AGND that will sink/source any substantial current to AGND or offset will be created from AGND versus A/D chip ground.

C.  Use an extra AIN channel on the CB37 in question and jumper it to GND on the CB37 to measure the GND offset so it can be accounted for in software.

D.  Get rid of or at least reduce GND offset by minimizing connections (minimizing resistance) between the signal terminals and A/D chip, avoiding sourcing/sinking current to GND on the CB37, and adding a big fat wire from CB37-GND to U6-GND or T7-GND.

E.  Use a star ground, and have a single solid connection from that star ground to U6-GND or T7-GND.  For example, connect the negative leads of all signals to an external grounding post or grounding bar, and run a big fat wire from there to a GND on the main LabJack.

Software

The Mux80's extended channels (AIN48-AIN127) act just like normal channels (AIN0-AIN13) and are read the same way.  For example, one of the T7's built-in analog inputs can be sampled by reading "AIN0". To sample an analog input on the Mux80, you can read "AIN48". Similarly, AIN configurations like range and resolution are configured in the same way for extended channels as they are for normal channels.  Configurations that apply to ALL channels do include normal and extended.

Most of our customers write their own software, but there are various software options:

• T-series software options

• UD software options

Our LJLog and LJStream example programs allow you to read any 16 channels.  So they can read any channels on the Mux80, but not all of them at the same time.  There is a beta version of LJLogM that does allow lots of channels (up to 255), so that is a reason for some customers to consider the newer LJM devices (e.g. T7) rather than UD devices (U3, U6, UE9).

Another option for non programmers is DAQFactory, but the free Express version is limited to 8 channels.

Troubleshooting

MIO0-2 are used to control the MUX80 multiplexers; ensure the MIO are not being used as normal DIO while trying to take readings from the MUX80.

For initial testing, the same steps that are described in our Test an AIN application note can be performed. With T-series devices, the extended AIN registers (whose hardware mapping is described in Table 1, Table 2, and on the pinout page) can be read directly in Kipling using the register matrix tab. For UD devices, see the "U6 or UE9 only" guide below.

If there seem to be problems with incorrect readings, also check that VMUX+ and VMUX- are within specified limits by measuring the test points with respect to GND. The Mux80 does not use VM+/VM- from the main device at all, but rather has its own power supply circuit to convert 5V (VS) to ±13V (VMUX+ and VMUX-) for the mux chips. Note that with a CB37 connected to any of X2-X5, the screw terminals labeled VM+/VM- are actually connected to VMUX+ and VMUX-, so this is a another way to measure besides the test points on the PCB.

Troubleshooting - U6 or UE9 Only

It is possible to check Mux80 functionality in LJControlPanel by performing the following steps:

1. Open LJControlPanel

2. Select UD device and click Test

3. On test pane, locate MIO 00, MIO 01, MIO 02 checkboxes for both Digital Direction and Digital State

4. Check the boxes for all 3 MIO lines under Digital Direction

5. Check desired boxes under Digital State according to the following table.  Find the extended channel number to investigate, then trace across the row to the Digital State of MIO0, MIO1, and MIO2.  Set the output state to high (checked) for 1 and low (un-checked) for 0.

6. Trace the column up to AIN#, this is the analog input that your analog signal will appear on. 

Table 3. Channel selection based on mux input

For example:  I have connected an analog signal to AIN65.  If I am using a CB37 Terminal Board, this will mean that the CB37 is connected to X3 on the Mux80, and the signal is wired to FIO1 on the CB37.  Looking at the above chart I note that 65 shares a row with MIO Output States of 1,0,0.  I then set MIO0 checked, MIO1 unchecked, and MIO2 unchecked.  Next I follow the column for 65 up to AIN6, so that is the analog input where I will see my analog signal with this MIO configuration.

Notes:

• Ensure your device has the latest firmware.  There is a known U6 firmware issue concerning MIO lines in v1.26 and older.  See revision history for more info. U6 firmware v1.40 and newer is able to stream differential channel pairs with the Mux80.

• On the U6 and U6-Pro, the digital lines CIO0-2 and MIO0-2 are shared.  This means that changing the state of MIO0-2 will also change the state of CIO0-2.  Therefore, anyone using a Mux80 with a U6 needs to be aware that digital lines CIO0-2 are not usable.