– The INA-BTA was improved to Auto-ID and started shipping around Oct 1, 2009.

– It won’t be fully functional in our software until Logger Pro 3.8.2 and LabQuest App 1.4, January 2010. However, it can be used successfully in Logger Pro 3.8 or LabQuest App 1.3, with the following direction:

1. Logger Pro 3.8 using LabQuest connected to a computer via USB:
– AutoID information is retrieved correctly on all 6 settings.
– The only minor flaw is the in the Logger Pro Sensor Setup dialog, the sensor is misidentified as “Unknown Analog” with no icon. But again, it retrieves the correct calibration, and unit (mV) and works just fine.

2. LP 3.8 using Go!Link connected to a computer via USB:
– AutoID information is retrieved correctly on all 6 settings.
– The only minor flaw is the in the Logger Pro Sensor Setup dialog, the sensor is misidentified as “Unknown Analog” with no icon. But again, it retrieves the correct calibration, and unit (mV) and works just fine.

3. LabQuest App v.1.3 (LabQuest standalone):
– No sensor recognized. This is treated like a non-autoID sensor until v.1.4.
– To use it successfully in v. 1.3,
a. Choose Sensor Setup from the Sensor menu,
b. Pull down the menu of the channel to which the INA-BTA is connected,
c. Scroll Down to the Instrumentation Amplfier, and the switch setting you are using on the INA-BTA to choose it.
d. Tap OK.
You will now be ready to take data.

4. Logger Pro 3.8 and LabPro configuration:
– Logger Pro appears to work, but does not. It recognizes a new sensor but does not load the calibration from the sensor.
– So it needs to be set up manually:
a. Tap on the LabPro icon on the toolbar.
b. Tap on the “unknown Analog” icon for the channel to which the sensor is connected, to see the list of possible sensors.
c. From the list, choose Instrumentation Amplifier, and the range switch setting you are using.
Alternatively, you can open an Experiment File from the Probes and Sensors folder in Logger Pro/Instrumentation Amplifier folder/proper switch setting file.

The problem is mostly with LabPro, or with LabQuest used free-standing. You can completely solve the problem by updating Logger Pro or LabQuest App in January 2010.