OTWINCFG Connection Troubleshooting
Please read this before posting connection related problems to the support mailing lists!
The OTWINCFG program is used to configure all models of OpenTracker, OpenTracker+, and Tracker2. The configuration options vary, but the connection process is the same for all models.
When you start OTWINCFG, select a COM port, and click 'connect', the program attempts to send a reset command to the tracker. If the tracker receives the command, it will reset and send an acknowledgement to the program and enter bootloader mode. Once the connection is made, the configuration screeen will be displayed.
If the tracker doesn't respond right away, you'll see a message prompting
you to reset the tracker. This can be done by disconnecting and reconnecting
power. Because the tracker could be in any of several different modes and
baud rate settings, OTWINCFG cycles continuously through many different
possibilities to try to connect. It may take a few seconds before it
happens upon the right combination and makes the connection, but
regardless of mode and speed, the tracker should be able to connect when it
is first powered on.
Here are the most common sources of problems when attempting to connect to a tracker:
Wrong connections. With the exception of the T2-135, all OT, OT1+, and T2 models require a null modem connection. This means that pins 2 and 3 of the serial cable are swapped - pin 2 on the PC is connected to pin 3 on the tracker, and vice versa. The only other connection required is pin 5 for ground. The T2-135 requires a standard, straight through serial cable.
No power. The tracker requires an external power source during configuration - it's not able to draw enough power from the serial port to run.
Wrong COM port. Be sure you're selecting the proper COM port number, especially if you're using a USB to serial adapter that might change port numbers.
Incompatible USB to serial adapter. Some USB adapters have timing problems or behave strangely when switching baud rates, which can cause the connection to fail. Adapters based on FTDI or Prolific chips usually work. When in doubt, try using a true serial port.
Dead tracker. Did this tracker ever work, or is it newly built? Every model
should produce at least one LED blink when it's powered on. If you don't see
this blink, the processor is not starting. See the tracker manual for
troubleshooting information.
Deaf tracker. This problem is usually encountered with older OT1x boards,
or early OT1+ SMT boards. Both of these have static-sensitive parts on the
data input line that can be destroyed if mishandled. A tracker with this
problem can be identified by the fact that if it is powered off and on a few
times, OTWINCFG will report an error. This is because OTWINCFG can hear the
tracker resetting, but the tracker isn't responding to its commands. If the
tracker is not one of the previously mentioned models, check that you haven't
inadvertently switched the LM335Z temperature sensor with one of the 2N7000
transistors - this will cause the same symptoms.
If you're able to connect to the tracker successfully but get errors when trying
to write the configuration or update the firmware, it may be due to faulty
wiring or excessive noise. Loose connections or excessive crosstalk are
common causes of this problem. Try different cables, and keep cable runs as
short as possible. Also try using the 'disable turbo' option - this will
reduce the baud rate and make the signal more immune to noise.