OpenTracker USB

OpenTracker USB User's Manual (PDF)

Despite the name, the OpenTracker USB is more closely related to the Tracker2 than the OpenTracker and OpenTracker+. It includes nearly all Tracker2 features with the exception of digipeater and Garmin protocol functions. It shares the same form factor as the OpenTracker+, with the addition of a USB type B connector on the front of the case.

USB Operation

The USB port on the OTUSB can be used for configuring the tracker with the otwincfg utility, accessing the command prompt, and connecting to a PC in KISS interface mode.

When the USB connection is in use, the tracker draws its power from the host system — no other connections are required for configuration of the unit.

Note: The OTUSB does not act as a USB host. It is only for connecting to a PC and cannot be used with a USB GPS receiver.

Windows

Windows 2000, XP, Vista, and 7 require the INF file linked here to properly recognize the device.

For help installing the INF driver, see: Windows INF File Installation (you'll need to manually link or convert this internal wiki page if porting it).

Linux

Most Linux distributions should recognize the OTUSB automatically and assign it a name like /dev/ttyACM0. If the device isn't recognized, try:

sudo modprobe usbserial vendor=0x134a product=0x9000

To exit KISS mode and return to command mode:

echo -ne '\xC0\xFF\xC0' > /dev/ttyACM0

Replace ttyACM0 with the actual port being used by your OTUSB.

Running otwincfg.exe under Wine

The configuration utility can be used under Linux with Wine and Winetricks. These steps were written for Ubuntu 11.10 but should apply to other distros as well.

Plug in the OTUSB and verify it's detected:

bash sudo lsusb

Look for: ID 134a:9000
Check for the device node:

bash ls /dev/ttyA*

You should see something like /dev/ttyACM0.
Create a symlink and set permissions:

bash sudo ln -s /dev/ttyACM0 ~/.wine/dosdevices/com1 sudo chmod 777 /dev/ttyACM0
Run the config utility:

bash wine otwincfg.exe

Select COM1 as the port.

If the program fails to run, make sure mfc42.dll is installed. Use winetricks to install it.

Mac OS X

macOS should recognize the OTUSB and assign a name like /dev/cu.usbmodemXXXX. If prompted to set up a dial-up device, just cancel.

Other Operating Systems

The OTUSB is a USB CDC ACM serial device with: - VID: 0x134A - PID: 0x9000

Most modern OSes have built-in drivers for this class.

Configuration

The tracker should always respond to the otwincfg utility, regardless of its current mode. If otwincfg is already running when the device is plugged in, it should auto-connect.

If your system assigns a COM port higher than COM16, you’ll need to reassign it in the Windows Device Manager.

A single setting controls the USB port mode. This appears as the "USB KISS" checkbox in otwincfg, or as the USBKISS command at the prompt.

Set USBKISS ON or check the box to enter KISS mode (for use with AGWPE, UI-View32, etc.).
If the host sends a KISS exit command, the tracker will return to command mode.

You can access the command prompt over USB the same way as the serial port. Note: Baud rate settings are ignored on USB.

When the USB port is connected and USBKISS is OFF, the command prompt is accessible only via USB — not through port A as usual.