Troubleshooting

The following commands are useful for low-level debugging.

1. telnet localhost 5001 and type ``register'', ENTER (taps data from CricketDaemon--you should see readable numbers and characters)
2. telnet localhost 2948 and type 'r' and ENTER (taps data from cricketd--you should see readable numbers and characters)
3. hyperterminal to COM1 (115200 baud 8N1) (taps data directly from listener)

Some common causes of errors are:

1. Low battery
2. Loose cable
3. Network connectivity or incorrect CRICKETD_IPADDR setting in launchall.sh
4. Running an incompatible version of cygwin (< 1.5.10). (Currently, there are some issues with cygwin. To detect this error, try telnetting from a Linux machine to cricketd running in the cygwin/Windows. If the Linux terminal produces garbage output, then the BeaconConfigDemo will crash, even if it runs on the same machine running cricketd. We are working to resolve this issue.)
5. Some lighting fixtures (especially flourescent tubes that are about to die) may produce noise in the ultrasonic range that interferes with Cricket and cause distance measurements to fluctuate rapidly. Turn off these fixtures to see if the distance measurements becomes more stable.
6. Although Cricket does not require line-of-sight for distance ranging, objects in the environment may deflect signals and cause a systematic error in distance ranging.