Revision as of 21:30, 31 March 2011

Polhemus Patriot Wireless

Tracker Startup

Instructions differ somewhat for the single vs. dual receptor configurations. Each will be covered separately:

Single Receptor

Determine TTY device name for base unit
- (for Keyspan, search dmesg output)
- (list files "/dev/tty*" -- if only one, that's probably it)
Turn on base unit
Turn on markers (switch to the left) numerically ascending order
Arrange markers ~6" from receptor (such that axis pictures align)
Test with Kermit
1. % kermit -l /dev/tty<XX> -b 115200 -C"set flow-control none,set carrier-watch off,connect"
2. Get signal strength: @s/n
3. Launch Markers for receptor #1: l1/n
4. Verify launch of markers: ^u0/n
  - for 3 markers, response should be 00u 00070007
    - (ie. one bit set per marker)
  - if not all markers successfully launched, try turning the unlaunched markers off and then on in numerically ascending order and then go back to the launch step
  - another thing to try is to do a soft-reset (^Y/n) and then relaunch
  - another thing to try is to move the markers closer to the receptor (but not too close -- they are too close if the signal strength is reported as nearly zero)
Now you are ready to try with fastraktest

Dual Receptor

...

Testing with FastrakTest

The fastracktest program is a utility program that comes with the FreeVR integration library. You may have to specifically compile it in the FreeVR src directory.

The fastracktest program works with both the original Polhemus Fastrak devices (and those based on the same protocol such as the IS-900) as well as the Polhemus Patriot devices (both the Wired and Wireless, which differ slightly). By default, running fastraktest will attempt to use the Fastrak device protocol, and will assume a serial port connection at /dev/input/fastrak. To run fastraktest with the Patriot Wireless, perhaps on a different TTY, use these environment variables:

FASTRAK_TTY -- set to the TTY device connected to the base unit
FT_PATRIOT -- just set it to inform the program to use the PATRIOT protocol (fastraktest will automatically determine whether it is a wired or wireless system.

...

Configuring for FreeVR

...

@@ Line 1: / Line 1: @@
-===Polhemus Patriot Wireless===
+=Polhemus Patriot Wireless=
 ==Tracker Startup==
 Instructions differ somewhat for the single vs. dual receptor configurations.
-Each will be covered separately.
+Each will be covered separately:
-=Single Receptor=
+===Single Receptor===
 #Determine TTY device name for base unit
-#*(for Keyspan, search dmesg output)
+#*(for Keyspan, search <CODE>dmesg</CODE> output)
-#*(list files "/dev/tty*" -- if only one, that's probably it)
+#*(list files "<CODE>/dev/tty*</CODE>" -- if only one, that's probably it)
 #Turn on base unit
 #Turn on markers (switch to the left) numerically ascending order
 #Arrange markers ~6" from receptor (such that axis pictures align)
 #Test with Kermit
-##% kermit -l /dev/tty<XX> -b 115200 -C"set flow-control none,set carrier-watch off,connect"
+##<CODE>% kermit -l /dev/tty<XX> -b 115200 -C"set flow-control none,set carrier-watch off,connect"</CODE>
-##Get signal strengh: @s/n
+##Get signal strength: <CODE>@s/n</CODE>
-##Launch Markers for receptor #1: l1/n
+##Launch Markers for receptor #1: <CODE>l1/n</CODE>
-##Verify launch of markers: ^u0/n
+##Verify launch of markers: <CODE>^u0/n</CODE>
 ##* for 3 markers, response should be <CODE>00u  00070007</CODE>
-(ie. one bit set per marker)
+##**(ie. one bit set per marker)
 ##* if not all markers successfully launched, try turning the unlaunched markers off and then on in numerically ascending order and then go back to the launch step
 ##* another thing to try is to do a soft-reset (<CODE>^Y/n</CODE>) and then relaunch
-##* another thing to try is to move the markers closer to the receptor (but not too close -- they are too close if the signal strengh is reported as nearly zero)
+##* another thing to try is to move the markers closer to the receptor (but not too close -- they are too close if the signal strength is reported as nearly zero)
-##Now you are ready to try with <CODE>fastraktest</CODE>
+#Now you are ready to try with <CODE>fastraktest</CODE>
-=Dual Receptor=
+===Dual Receptor===
 ...
 ==Testing with FastrakTest==
+The <CODE>fastracktest</CODE> program is a utility program that comes with the FreeVR integration library.  You may have to specifically compile it in the FreeVR <CODE>src</CODE> directory.
+The <CODE>fastracktest</CODE> program works with both the original Polhemus Fastrak devices (and those based on the same protocol such as the IS-900) as well as the Polhemus Patriot devices (both the Wired and Wireless, which differ slightly).  By default, running <CODE>fastraktest</CODE> will attempt to use the Fastrak device protocol, and will assume a serial port connection at <CODE>/dev/input/fastrak</CODE>.  To run <CODE>fastraktest</CODE> with the Patriot Wireless, perhaps on a different TTY, use these environment variables:
+* <CODE>FASTRAK_TTY</CODE> -- set to the TTY device connected to the base unit
+* <CODE>FT_PATRIOT</CODE> -- just set it to inform the program to use the PATRIOT protocol (<CODE>fastraktest</CODE> will automatically determine whether it is a wired or wireless system.
+...
+==Configuring for FreeVR==
 ...

Difference between revisions of "PatriotWireless"