Posts tagged with: auto-id

The most common cause to this problem is unsupported software. The first thing to try would be upgrading to the newest version of the software......
Continue Reading →
If the LabQuest doesn’t detect a sensor when the sensor is plugged into the LabQuest this could be caused by the sensor or the LabQuest.......
Continue Reading →
It is possible for a Motion Encoder to incorrectly announce its name to the software, causing the Auto-ID feature to fail. This issue is likely......
Continue Reading →
When using a Digital Control Unit (DCU) with LabQuest 2, automatic identification of sensors is disabled for the port used by the DCU. This is......
Continue Reading →
The first batch of had a firmware bug that affected how the device reads the auto-ID resistors in our sensors. If the Go Wireless Link......
Continue Reading →
In general, older sensors that connected directly to ULIs and Serial Boxes can be used with new interfaces using an adapter that costs $5. As......
Continue Reading →
The Projectile Launcher can be used with or without an interface. If you are using the launcher with an interface, the speed of the ball......
Continue Reading →
Note: the instructions below refer to using CH 1 for clarity; however, any channel can be used. Instructions for LabQuest 2 1) Connect the sensor......
Continue Reading →
First test: Check to see if you have an original Go! Link. The old units are labeled “Go! Link” and the newer style read “Go!......
Continue Reading →
There are three possible explanations: 1) It was manufactured before 2008, which is when it became auto-id. 2) If you are trying to use a......
Continue Reading →