Basic Information

Troubleshooting

  1. Verify your TI-Nspire CX II or TI-Nspire CX II CAS handheld is running OS version 6.2.0 or newer.
  2. Verify you are using a supported Go Direct sensor that is fully charged.
  3. If connecting via Bluetooth®, make sure the TI Bluetooth Adapter is updated with the latest firmware.
  4. If the sensor fails to connect when using Bluetooth®, try connecting using USB.
  5. If the sensor fails to connect when using USB, try connecting using Bluetooth®.
  6. If you continue to have connection issues, try connecting the sensor to a computer, Chromebook, phone, or tablet using our Graphical Analysis app.

For additional assistance, contact us at 888-837-6437 or support@vernier.com.

Frequently Asked Questions

A: Sensors marked as “Generally Supported” will not have the typical default setup applied when the sensor is connected. Below is the default setup details for “Generally and Minimally Supported” sensors (any of which can be manually changed as needed for your experiment):

  • Sensor Channel (when applicable):
    Sensor Channel 1 (for that sensor) 1
  • Data collection
    Mode: Time Based
    Rate: 50 samples per second
    Duration: 10 seconds
  • Display Precision
    Time: Two decimal places
    Sensor: One decimal place
  • Graphs: Graph 1 only
    X-axis range: [0, 10]
    Y-axis range: [0, 5]

Note: “Generally and Minimally Supported” sensors all have the option to zero and reverse the sensor reading, which may not make sense for some sensors.

A: No.
Only TI-Nspire CX II and TI-Nspire CX II CAS handhelds support data collection with Go Direct sensors. (For images of older TI calculators, see What Texas Instruments calculators do you sell?)

A: No.
Only TI-Nspire CX II and TI-Nspire CX II CAS handhelds are supported. In the future, TI may add support for Go Direct sensor data collection to their TI-Nspire computer software.

A: No.
TI does not support sensor data collection using any of their Online Calculator apps.

A: Use a projector connected to a document camera aimed at your TI-Nspire handheld.
Because neither the TI-Nspire student nor teacher software supports data collection with Go Direct sensors, you cannot use the software to demonstrate data collection to your class. Your best option is to use a document camera with a TI-Nspire handheld to project the screen of the calculator to your class.

A: Yes.
However, multiple Go Direct sensors are only supported when connecting the sensors wirelessly using the TI Bluetooth Adapter.

Data collection via a USB connection supports only one sensor at a time.

A: No.
EasyLink, EasyTemp and CBR 2 sensors must connect to the USB port on the TI-Nspire handheld. Go Direct sensors must either connect directly to the USB port or connect wirelessly to the TI Bluetooth Adapter that must connect to the handheld USB port.

A: Yes. However, this is largely untested.
You can expect a lag in data coming from the sensors connected to the TI-Nspire Lab Cradle compared to the data coming from the Go Direct sensors. The Go Direct sensors can be connected using the TI Bluetooth Adapter or via USB (connected to the handheld not to the Lab Cradle).

A: Unfortunately, there is no easy way.
The best way 2 to ensure you are using the most up-to-date firmware (Sketch) is to update the firmware yourself.

A: No
The DataQuest app will not provide notifications when a Go Direct sensor has an available firmware update. To check for firmware updates, connect your Go Direct sensor to a device running our Graphical Analysis app. 3

A: No.
You can expect to see ~0.3 s lag 4 in data collected from a pair of Go Direct sensors. When collecting data from two Go Direct sensors, set the Rate to 2 samples per second (Interval: 0.5 s) to reduce the noticeable lag on your collected data.

Each additional sensor adds ~0.3 s more lag. When collecting data with three or four sensors, set the Rate to 1 sample per second (Interval: 1.0 s) or slower.

A: Yes. However, sometimes it does not appear to.
When collecting data from a single Go Direct sensor (with no more than two sensor channels selected), the graphs update in real time. When there are more than two sensor channels (or more than two sensors), data will be added to the graphs in chunks with an increase in noticeable delays between added chunks the longer data are collected.

Data Collection Specifications

Maximum Sample Rate
(DataQuest App limitation for Go Direct Sensors)
200 samples per second (some sensors/sensor channels cannot sample that fast)
Maximum Number of Samples 2500 (any number of sensors/sensor channels)
Maximum number of Sensors 4 via Bluetooth
1 via USB
Maximum number of Sensor Channels
(per sensor)
4 via Bluetooth
no limit via USB (but more than 4 slows the app)
Sensor Calibration Not supported 5

Additional Links

  1. For Go Direct Sensors with multiple sensor channels, Sensor Channel 1 is the first sensor shown in the list of available sensor channels. If a sensor typically defaults to a different sensor channel (or uses more that one sensor channel), you will need to manually change the sensor channel selection in the DataQuest App. ↩︎
  2. If you never see any available Go Direct sensors when attempting to connect, it is likely you are running firmware v1.0.0. If when trying to use non-default sensor channels (for example the Motion-Cart for a Go Direct Motion) and your graphs appear shaded because of periodic (and unexpected) near-zero sensor readings, it is likely you are running firmware v1.1.0. ↩︎
  3. Go Direct Firmware updates can only be applied when the sensor is connected via USB to a computer or Chromebook running our Graphical Analysis app. ↩︎
  4. The lag is related to the time it takes the TI Bluetooth Adapter to get the data from each connected sensor. Future updates to the TI Bluetooth Adapter may address this lag. A similar lag happens with multiple Go Direct sensors when using the Graphical Analysis app (USB or Bluetooth connection), but that lag is significantly less (around 10 – 20 milliseconds). ↩︎
  5. Go Direct sensor calibration must be done using our Graphical Analysis or LabQuest Apps. Go Direct sensor calibrations are always stored directly on the sensor, so once a sensor is calibrated, the new calibration will be used when collecting data using the DataQuest App. ↩︎