http://wiki.argentdata.com/api.php?action=feedcontributions&user=VE6SRV&feedformat=atomArgentWiki - User contributions [en]2024-03-28T18:21:22ZUser contributionsMediaWiki 1.24.4http://wiki.argentdata.com/index.php?title=Telemetry&diff=50533Telemetry2023-11-04T18:00:08Z<p>VE6SRV: /* Telemetry Equations, Units, Parameters, and Labels */</p>
<hr />
<div>All tracker models have the ability to send telemetry information from on board sensors, as well as external input sources. [[File:OT2m Reporting Options.png|128px|thumb|right|Reporting options section from OTWINCFG]]<br />
<br />
Some of the telemetry information can be embedded into the comment section of a packet, or you can configure the tracker to send separate packets in the APRS telemetry defined format.<br />
<br />
T#sss,aaa,bbb,ccc,ddd,eee,76543210<br />
<br />
"sss" is a sequence number which increments upon each telemetry report sent, wrapping at 999 back to 000. "aaa,bbb..." are analog values between 0 and 255. Their conversions are given in the table below. 0-7 are are binary bits, either 0 or 1. The currently active configuration profile may be reported as a telemetry bit.<br />
<br />
A digital counter input is available on some tracker models. The counter value can be reported in status packets and in some models as a telemetry value.<br />
<br />
For some models, the commands [[ANALOG]] and [[GPIO]] can be used to read specified analog inputs and read or set general-purpose digital I/O pins. The pin assignments for these commands are shown below.<br />
<br />
== Pin Assignments by Device ==<br />
<br />
This information reflects current firmware versions and production hardware. Beta hardware and older firmware versions may have different assignments.<br />
<br />
=== OT3m ===<br />
<br />
{| class="wikitable" border=1 <br />
! Pin<br />
! Function<br />
! Value<br />
|- <br />
| Supply Voltage<br />
| Telemetry aaa, ANALOG 0<br />
| Volts * 10 (Max 20v)<br />
|- <br />
| Terminal Block A1<br />
| Telemetry bbb, ANALOG 1<br />
| Volts * 10 (Max 20v)<br />
|- <br />
| Terminal Block A2<br />
| Telemetry ccc, ANALOG 2<br />
| Volts * 10 (Max 20v)<br />
|- <br />
| Terminal Block A3<br />
| Telemetry ddd, ANALOG 3<br />
| Volts * 10 (Max 20v)<br />
|- <br />
| Terminal Block A4<br />
| Telemetry eee, ANALOG 4<br />
| Volts * 10 (Max 20v)<br />
|- <br />
| Radio Pin 9 (AUX_IO)<br />
| GPIO 0<br />
| ON = High, OFF = Low<br />
|- <br />
| Terminal Block IO<br />
| Telemetry bit 1, GPIO 1, Profile Jumper<br />
| ON = High, OFF = Low<br />
|- <br />
| Terminal Block CT<br />
| Counter Input (if enabled) or Beacon Trigger<br />
| Pull to ground to activate<br />
|- <br />
| Active Profile<br />
| Telemetry bit 0<br />
| ON = Profile 2, OFF = Profile 1<br />
|}<br />
<br />
=== OpenTracker USB ===<br />
<br />
{| class="wikitable" border=1 <br />
! Pin<br />
! Function<br />
! Value<br />
|- <br />
| Supply Voltage<br />
| Telemetry aaa, ANALOG 0<br />
| Volts * 10 (Max 20v)<br />
|- <br />
| CN4 Pin 3<br />
| Telemetry bbb, ANALOG 1<br />
| Volts * 10 (Max 20v)<br />
|- <br />
| CN4 Pin 4<br />
| Telemetry ccc, ANALOG 2<br />
| Volts * 10 (Max 20v)<br />
|- <br />
| CN4 Pin 5<br />
| Telemetry ddd, ANALOG 3<br />
| Volts * 10 (Max 20v)<br />
|- <br />
| CN4 Pin 6<br />
| Telemetry eee, ANALOG 4<br />
| Volts * 10 (Max 20v)<br />
|- <br />
| Radio Pin 9 (AUX_IO)<br />
| GPIO 0, Power Relay<br />
| ON = High, OFF = Low<br />
|- <br />
| CN4 Pin 7<br />
| Telemetry bit 1, GPIO 1, Profile Jumper<br />
| ON = High, OFF = Low<br />
|- <br />
| Active Profile<br />
| Telemetry bit 0<br />
| ON = Profile 2, OFF = Profile 1<br />
|}<br />
<br />
== OT2m Telemetry elements ==<br />
<br />
{| class="wikitable" border=1 <br />
! Entry #<br />
! Description<br />
! Sensor input<br />
|- <br />
| aaa<br />
| Temperature as reported by an on board LM335D sensor. (U5)<br />
| [[File:OT2m Temperature Sensor.png|64px|thumb|center|LM335D temperature sensor chip]]<br />
|- <br />
| bbb<br />
| Source voltage being provided to the OT2m, measured by a voltage divider. (R16 / R17)<br />
| [[File:OT2m Voltage Divider.png|64px|thumb|center|Voltage divider circuit]]<br />
|- <br />
| ccc<br />
| Read from pin 10 (PTA0/ADC0) on the MON08 header on the circuit board. Allowable voltage input range is between 0 and 5 volts.<br />
| [[File:OT2 MON08.png|128px|thumb|center|MON08 header]]<br />
|- <br />
| ddd<br />
| Counter value, with the counter input on pin 1 (IRQ1) of the accessory port, also available from pin 6 (IRQ/counter/transmit-now input) on the MON08 header on the circuit board. Counter can be incremented by grounding this input. Software debounce settings are available.<br />
| [[File:OT2 Accessory.png|128px|thumb|center|Accessory Port]]<br />
|- <br />
| eee<br />
| HDOP value reported by an attached GPS.<br />
|<br />
|-<br />
| xxxxxxxx<br />
| Only the last 2 binary bits are used on the OT2m.<br />
Bit 7 reports the current status of the jumper input located on pin 6 (CFG) of the accessory port. Grounding this input reports a bit state of 1.<br />
<br />
Bit 8 reports the current profile in use.<br />
|<br />
|}<br />
<br />
== T3-301 Telemetry elements ('''UNDER CONSTRUCTION''') ==<br />
<br />
{| class="wikitable" border=1 <br />
! Entry #<br />
! Description<br />
! Sensor input<br />
|- <br />
| aaa<br />
| <br />
| <br />
|- <br />
| bbb<br />
| <br />
| <br />
|- <br />
| ccc<br />
| <br />
| <br />
|- <br />
| ddd<br />
| <br />
| <br />
|- <br />
| eee<br />
| <br />
|<br />
|-<br />
| xxxxxxxx<br />
| <br />
|<br />
|}<br />
<br />
== MON08 pinout ==<br />
<br />
{| class="wikitable" border=0 <br />
|<br />
1 - PTB7/T2CH1 (digital I/O or timer channel)<br />
2 - GND<br />
3 - PTB5/T1CH1<br />
4 - Reset<br />
5 - No connection<br />
6 - IRQ (counter/transmit-now input)<br />
7 - No connection<br />
8 - PTA3/ADC3 (digital I/O or ADC input)<br />
9 - No connection<br />
10 - PTA0/ADC0<br />
11 - No connection<br />
12 - PTA2/ADC2<br />
13 - Clock oscillator (32.768 kHz)<br />
14 - PTA1/ADC1<br />
15 - +5V<br />
16 - PTB0 (digital I/O)<br />
| [[File:OT2 MON08 pinout.png|185px|thumb|left|MON08 header]]<br />
|}<br />
<br />
== Telemetry Equations, Units, Parameters, and Labels ==<br />
<br />
APRS telemetry reports contain only raw values, and it is up to the user interface software to display the information in a human readable format, with appropriate calculations performed to provide corrected values.<br />
<br />
In order to do this, the software needs to have some information provided to it so that it can do the appropriate conversions, display each value with the required units, properly labelled.<br />
<br />
There are 4 sentences that provide this required information.<br />
<br />
<br />
* A Parameter Name message.<br />
<br />
PARM.Temp.,Bat.,Extrn,Count,HDOP,NA,NA,NA,NA,NA,NA,JU,CF<br />
<br />
The original DosAPRS program was limited to 80 characters per line, and to fit those limits, arbitrary parameter name lengths were chosen. If you wish to stay compatible with DosAPRS, the paramater name lengths for the 5 analog channels are 7, 6, 5, 5 and 4 characters. The lengths for the 8 digital bits are 5, 4, 3, 3, 3, 2, 2, and 2 characters respectively. <br />
<br />
* A Unit/Label message.<br />
<br />
UNIT.Deg.,Volts,Volts,NUM,HDOP,,,,,,,ON,NUM<br />
<br />
Sets the labels associated with the analog values, and for the digital bits, a label to association with the digital state.<br />
<br />
* An Equation Coefficients message.<br />
<br />
EQNS.0,1.9608,-273,0,0.07843,0,0,0.07843,0,0,1,0,0,0,0<br />
<br />
There are three coefficients for each analog channel, a,b,and c. These three coefficients get plugged into a quadratic equation along with the reported analog value x. The result is calculated from this equation where FINAL VALUE = a*x^2 + b*x + c<br />
<br />
* A Bit Sense/Project Name message.<br />
<br />
BITS.11111111,Your Telemetry Name<br />
<br />
BITS format specifies which bit state is associated with the label. You can also specify a title for your telemetry page.<br />
<br />
APRS telemetry definition sentences simply need to be sent to the target callsign as an APRS message.</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=Radio_Wiring&diff=3334Radio Wiring2012-08-20T01:40:49Z<p>VE6SRV: Packet data port wiring added.</p>
<hr />
<div>All Argent tracker products with a 9-pin radio connector (with the exception of the [[T2-301]]) use the same pinout for all basic radio interface signals:<br />
<br />
<table border=1><tr><th>Pin</th><th>Function</th></tr><br />
<tr><td>1<td>Audio output (tracker to radio)</td></tr><br />
<tr><td>2<td>Squelch input</td></tr><br />
<tr><td>3<td>PTT output</td></tr><br />
<tr><td>5<td>Audio input (radio to tracker)</td></tr><br />
<tr><td>6<td>Ground</td></tr><br />
<tr><td>7<td>Power input</td></tr><br />
<tr><td>8<td>PTT input (for mic encoder use only)</td></tr><br />
</table><br />
<br />
For most applications, the only connections to the radio required are audio in and out, PTT, and ground. Most handheld radios (Kenwood models being the most significant exception) don't require a separate PTT signal, and instead signal PTT through the mic audio input. For these radios, the 'HT' jumper should be set in the tracker and the PTT line left unconnected.<br />
<br />
While the [[Tracker2]] has a separate power input, other tracker models require power to be provided through the radio connector.<br />
<br />
== Yaesu and Vertex Standard Radios ==<br />
<br />
Handheld models including the FT-10R, FT-60R, VX-1R, VX-2R, VX-3R, VX-5R, VX-110, VX-150, and all models that include the CT-44 adapter in their accessory list use a 4-conductor, 3.5mm plug (available [https://www.argentdata.com/catalog/product_info.php?products_id=68 here]).<br />
<br />
The VX-6R, VX-7R, VX-120, VX-127, VX-170, VX-177 and all models that include the CT-91 adapter in their accessory list use a threaded, waterproof version of the same 3.5mm plug (available [https://www.argentdata.com/catalog/product_info.php?products_id=67 here]).<br />
<br />
Pinouts for both, starting from the tip, are as follows:<br />
<br />
{| class="wikitable" border=1 <br />
! Pin<br />
! Function<br />
|- <br />
| Tip<br />
| Mic<br />
|- <br />
| R2<br />
| Cloning<br />
|- <br />
| R1<br />
| Speaker<br />
|- <br />
| Sleeve<br />
| Ground<br />
|- <br />
|}<br />
<br />
<br />
<br />
Handhelds using the 3.5mm/2.5mm 2 prong connector including the FT-411, FT-470 , FT-530, FT-51R, FT-11R, FT-41R, FT-23R, FT-203R, FT-416, FT-703R, FT-109R, FT-109RH, FT-209R, FT-209RH, FT-709R, FT-709RH, FT-727R, (available [https://www.argentdata.com/catalog/product_info.php?cPath=21&products_id=30 here]).<br />
<br />
<table border=1><tr><th>Pin</th><th>Function</th></tr><br />
<tr><td>3.5 Ring<td>Ground</td></tr><br />
<tr><td>3.5 Tip<td>Rx audio</td></tr><br />
<tr><td>2.5 Ring<td>Ground</td></tr><br />
<tr><td>2.5 Tip<td>Mic Audio</td></tr><br />
<br />
</table><br />
<br />
<br />
<br />
Handheld models including the FT-10R, FT-40R, FT-50R, FT-60R, VX-1R, VX-2R, VX-3R, VX-5R, VX-110, VX-150, and any other model including the CT-44 adapter and MH34b4b speaker microphone in their accessory list utilize the non-threaded 4 conductor 3.5mm type microphone plug which is (available [https://www.argentdata.com/catalog/product_info.php?cPath=21&products_id=68 here]).<br />
<br />
== Baofeng Radios ==<br />
<br />
The Baofeng handheld radios use the same 4 pin plug as the Yaesu radios but they have a seperate PTT and Mic pins. The pin outs are as follows, from tip to sleeve.<br />
<br />
{| class="wikitable" border=1 <br />
! Pin<br />
! Function<br />
|- <br />
| Tip<br />
| Mic<br />
|- <br />
| R2<br />
| Speaker<br />
|- <br />
| R1<br />
| PTT<br />
|- <br />
| Sleeve<br />
| Ground<br />
|- <br />
|}<br />
<br />
== Packet Data Port ==<br />
<br />
A number of mobile radios manufactured come with a data port on them. This port provides access to a number of signals that are of interest to the APRS user.<br />
<br />
{| class="wikitable" border=1<br />
! Pin<br />
!Function<br />
|-<br />
|1<br />
| SQC squelch signal output<br />
|-<br />
|2<br />
| 9600 bps data out<br />
|-<br />
|3<br />
| 9600 bps data in<br />
|-<br />
|4<br />
| 1200 bps data out<br />
|-<br />
|5<br />
| Ground<br />
|-<br />
|6<br />
| N/C<br />
|-<br />
|7<br />
| PTT input<br />
|-<br />
|8<br />
| 5.0V dc max 50mA output<br />
|-<br />
|9<br />
| 1200 bps data in<br />
|-<br />
|}<br />
<br />
Given that information it is easy to match up the Open Tracker pinout to the data port pinout as follows: <br />
<br />
<table border=1><tr><th colspan=2>Tracker</th><th colspan=2>Radio</th></tr><br />
<tr><th>Pin</th><th>Function</th><th>Pin</th><th>Function</th></tr><br />
<tr><td>1<td>Audio output (tracker to radio)</td><td>9</td><td>1200 bps data in</td></tr><br />
<tr><td>3<td>PTT output</td><td>7</td><td>PTT input</td></tr><br />
<tr><td>5<td>Audio input (radio to tracker)</td><td>4</td><td>1220 bps data out</td></tr><br />
<tr><td>6<td>Ground</td><td>5</td><td>Ground</td></tr><br />
</table><br />
<br />
== Motorola Radios ==<br />
<br />
Argent Data products to Motorola 16 pin accessory port wiring diagram can be found on this page: [[OT-Moto]]<br />
<br />
<br />
The Motorola 16 pin accessory connector can provide all of the signals necessary to interface to an OT product, including providing enough current to power the unit.<br />
<br />
<br />
<br />
Some Motorola radios have other pins as programmable options beyond what the diagram shows. All radios I have run across so far have been able to be programmed to match the pin out provided. I have successfully interfaced to Radius SM-50, Radius SM-120, and Radius M1225 units. I have provided a COR signal connection, although I run the RX audio output on pin 11 in an unsquelched mode, providing live audio 100% of the time, and set the OT2 for software carrier detect.<br />
<br />
This type information also applies to the Maxtrac, Maxtrac 50, Maxtrac 100, Maxtrac 300, Radius M100, M214, M216 Mobiles, and the venerable GM300.<br />
<br />
<br />
<br />
<br />
Currently we have an M120 and GM300 that have both worked well with this setup. I am running an M120 currently with an ot2m and it is a great setup. We also are fielding an M120 with an OT1+ connected through the front panel microphone jack. <br />
<br />
<br />
Please note: it may be necessary to reprogram your radio and change the settings of the multi pin connector prior to successful operation of your APRS setup. WE STRONGLY RECOMMEND RETUNING YOUR RADIO FOR AMATEUR USE. <br />
<br />
<br />
<br />
<br />
<br />
<br />
The Waris mobiles (CDM750, CDM1225, CDM1550)use a similar connector with 20 pins. We are working on the proper pin outs for the Waris series.<br />
<br />
<br />
The GP300, P110, GP350, GP600, P1225, P50+, and Triton portables use the Motorola 2 pin type connector (available [https://www.argentdata.com/catalog/product_info.php?cPath=21&products_id=71 here]).</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:Interface.jpg&diff=789File:Interface.jpg2011-09-27T04:03:19Z<p>VE6SRV: Backside I/O connections.</p>
<hr />
<div>Backside I/O connections.</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:Config.jpg&diff=786File:Config.jpg2011-09-27T02:00:43Z<p>VE6SRV: Configuration input</p>
<hr />
<div>Configuration input</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:Voltage_divider.jpg&diff=785File:Voltage divider.jpg2011-09-27T01:59:03Z<p>VE6SRV: Added resistors to create a second voltage divider.</p>
<hr />
<div>Added resistors to create a second voltage divider.</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=Digipeater_Setup&diff=685Digipeater Setup2011-07-03T19:50:09Z<p>VE6SRV: /* Digipeater Basics */ Removed some misleading information about i-gates only acting once the path was used up.</p>
<hr />
<div>[[File:Digisettings.png|thumb|Digipeater Settings Dialog]]<br />
<br />
The [[Tracker2]]'s digipeater settings can be configured either through the Digipeater Settings dialog in OTWINCFG or through the command line.<br />
<br />
=== Digipeater Basics ===<br />
<br />
The job of an APRS digipeater is to receive packets from other APRS stations and repeat them, while limiting the number of hops traveled by any packet and not repeating the same packet twice.<br />
<br />
By default, the Tracker2 will repeat packets having the tracker's own callsign as the next unused callsign in the path. This way, a tracker not explicitly configured as a digipeater can be used to relay packets if necessary, but it requires the sending station to modify their path.<br />
<br />
For normal operation, [[APRS digipeaters]] respond to generic aliases rather than their actual callsigns. The most common is WIDEn-N, used by most APRS stations. 'n' indicates the number of hops requested by the sending station, and 'N' the number of hops remaining. For example, a packet sent with a path of WIDE2-2 will be repeated by the first digipeater with the path changed to WIDE2-1. The next digi will use up the last hop and change it to WIDE2-0, which is displayed as WIDE2.<br />
<br />
<pre><br />
cmd:digi on<br />
DIGI ON<br />
</pre><br />
<br />
The DIGI command enables or disables repeating of packets with the tracker's own callsign in the path.<br />
<br />
=== Aliases ===<br />
<br />
The Tracker2 supports up to 8 digipeater aliases. If the HOPLIMIT is set to 0, only an exact match will trigger use of the alias. For example, with an alias of SAR and hop limit 0, the Tracker2 will repeat packets sent via SAR, or SAR-N, but not SARn-N. It will forward the packet replacing SAR with it's MYCALL. If hop limit is greater than 0, then the alias will be matched in all cases of SAR, SARn-N, SAR1-1, SAR2-1, SAR2-2. It will become fully traceable. The HOPLIMIT will trap SARn-'''N''' greater than the HOPLIMIT. An incoming packet of SAR3-3 and HOPLIMIT of '''2''' would trap the incoming packet to SAR3-'''2''', the trapped packet is then forwarded SAR3-'''1'''. A similar packet SAR3-3 with HOPLIMIT increased to '''3''' will not be Trapped. Any incoming packet larger than SARn-3 will be trapped and forwarded SARn-'''2''', allowing two more digi hops. This Trapping doesn't affect multiple digi paths, like if an abuser was running WIDE1-1,WIDE3-3. only the first un-used path is potentially trappable. <br />
<br />
An alias of WIDE and HOPLIMIT of '''2''' will repeat any packets sent via any WIDEn-N (even obsolete "WIDE"). These packets are fully traceable. In populated areas an incoming abusive packet of WIDE3-3, or higher, will be treated as if it was a WIDEn-2. The tracker2 will forward any WIDEn-N larger than WIDEn-1 as WIDEn-1. This will allow the abuser one more hop. A HOPLIMIT setting of '''2''' won't trap normal paths: WIDE1-1,WIDE2-1, WIDE1-1,WIDE2-2, or WIDE2-2. It also won't trap the following abusive packet WIDE2-2,WIDE3-3 since it processes the first path WIDE2-2, not the second path of WIDE3-3. <br />
<br />
The alias TEMP is enabled by default with a hop limit of 2. The tracker2 will digipeat any TEMP, or TEMPn-N, allowing one additional hop on packets TEMPn-2 or larger. This alias is intended to be used for special events (e.g., Field Day) and for emergencies. APRS stations should not routinely transmit with TEMP in their path.<br />
<br />
Fill-in digi's are the most courteous [http://www.aprs.org/fix14439.html New Paradigm] digi's. They only forward fresh first hop from WIDE1-1 mobiles. The used up WIDE1 is replaced with MYCALL, and any additional paths are forwarded. Mobiles running the recommended new paradigm path of WIDE1-1,WIDE2-1 benefit from Fill-in's. All other WIDEn-N's are ignored to limit forwarding stale QRM. Fill-in's won't clog up the network forwarding old stale WIDE2-N digi id's, beacons, WX, stale mobile traffic, and abusive paths. Fill-in digi's can be added into a busy APRS area without much adverse impact to the network load. The beacon PATH should be left blank, when possible, so as to not add QRM to the network. If the fill-in is not heard directly by an I-gate, a PATH of WIDE2-1 is usually acceptable. Especially if [[scripting]] is used to only send a WIDEn-1 path once, or twice an hour, to keep it on the maps. Local beacons are OK every 10 minutes, advertise your accepted path, local systems, and information. Keep your local info "local" for folks traveling nearby. See [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin], or [http://www.aprs.org/kpc3/kpc3+WIDEn.txt WIDEn-N] for more up to date recommended settings.<br />
To setup a fill-in set: ALIAS 1 WIDE1, HOPLIMIT 1 0, USEALIAS 1 on, DIGI on, DIGIID 1 on, PATH -. <br />
<pre><br />
cmd:alias 1 wide1<br />
ALIAS 1:WIDE1 <br />
cmd:alias 2 temp<br />
ALIAS 2:TEMP <br />
cmd:alias 3 sar<br />
ALIAS 3:SAR <br />
cmd:alias<br />
ALIAS 1:WIDE1 2:TEMP 3:SAR <br />
cmd:alias 4:foo 5:bar<br />
ALIAS 1:WIDE1 2:TEMP 3:SAR 4:FOO 5:BAR <br />
cmd:alias 2 -<br />
ALIAS 1:WIDE1 3:SAR 4:FOO 5:BAR <br />
</pre><br />
<br />
As shown in the example above, the ALIAS command can accept one numbered entry at a time or, using a colon to separate the entry number and alias, several entries at once. Entering '-' for an alias erases that alias. This scheme is used for all alias-related options.<br />
<br />
<pre><br />
cmd:hoplimit 1 0<br />
HOPLIMIT 1:0 <br />
</pre><br />
<br />
The HOPLIMIT command sets the acceptable number of hops for each alias. In this example, alias 1 (set to WIDE1 Fill-in in the previous example) is limited to 0 additional hops.<br />
<br />
<pre><br />
cmd:usealias<br />
USEALIAS 1:OFF 2:OFF 3:ON 4:OFF 5:OFF 6:OFF 7:OFF 8:OFF <br />
cmd:usealias 1 on<br />
USEALIAS 1:ON <br />
</pre><br />
<br />
The USEALIAS command determines which aliases are enabled. Here, alias 1 is enabled. Alias 3 was already active.<br />
<br />
=== ID Insertion ===<br />
<br />
If the ID option is enabled for an alias, when the Tracker2 repeats a packet using that alias, the tracker's own callsign is inserted into the path to show the actual path taken by the packet. This is standard practice in the US for WIDE digipeaters. For private systems or where trace information isn't important, the ID option can be disabled to keep packets short.<br />
<br />
<pre><br />
cmd:digiid 1 on<br />
DIGIID 1:ON <br />
</pre><br />
<br />
This example enables ID insertion for alias 1.<br />
<br />
=== Duplicate Elimination ===<br />
<br />
The Tracker2 keeps track of the last several packets repeated and will not repeat a duplicate packet within the configured dupe check time, which defaults to 30 seconds.<br />
<br />
<pre><br />
cmd:dupetime 30<br />
DUPETIME 30<br />
</pre><br />
<br />
=== Preemption ===<br />
<br />
Ordinarily, only a packet's next unused path entry is examined. If a packet is sent with a path of WIDE1-1,WIDE2-1,SAR a digipeater using only the alias SAR will not repeat the packet until the WIDE1-1,WIDE2-1 portion has used all of its hops and been marked as used. The preemption option changes this behavior, and an alias with preemption enabled will match <i>any</i> unused path option.<br />
<br />
A typical use for this option is a restricted digipeater network. For example, a search and rescue team could deploy a number of digipeaters using the SAR alias with preemption enabled, and then transmit using a path of WIDE1-1,WIDE2-1,SAR. When out of range of the SAR digipeaters, regular WIDE digipeaters and fill-in's will still repeat the packets. When in range, the SAR digipeaters will match the SAR alias and repeat the packets, but will <i>not</i> respond to packets from the general public without SAR in the path.<br />
<br />
<pre><br />
cmd:alias 3<br />
ALIAS 3:SAR <br />
cmd:preempt 3 on<br />
PREEMPT 3:ON <br />
</pre><br />
<br />
== Recommended Settings ==<br />
<br />
Recommended APRS path settings vary by country and region.<br />
<br />
=== North America - Widen-N ===<br />
<br />
1) RELAY, WIDE and TRACE are obsolete.<br />
<br />
2) Use WIDE2-1, or WIDE2-2, or SSn-N for fixed stations.<br />
<br />
3) Use "WIDE1-1,WIDE2-1" for mobiles. ''Commuters in busy areas could use a single hop WIDE1-1, or "WIDE1-1,SSn-N" to contain to a Section or State.''<br />
<br />
4) Use "WIDE1-1,WIDE2-2" for mobiles. ''Use only in areas that are lacking I-gates, where three hops are needed to get to intended target. Potential to QRM local and distant networks.''<br />
<br />
See http://aprs.org/fix14439.html for more information.</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:OT2-Moto.png&diff=631File:OT2-Moto.png2011-04-01T02:09:03Z<p>VE6SRV: uploaded a new version of "File:OT2-Moto.png": Changed audio input from pin 2 Ext Mic Audio to pin 5 Flat TX Audio Input. Pin 2 has 500 ohm input impedence, and OT2 is not able to drive the input level high enough to create more than 2 kHz deviation. </p>
<hr />
<div>OT2 to Motorola 16 pin accessory port connector.</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:Nuvilist.png&diff=230File:Nuvilist.png2009-10-30T14:51:46Z<p>VE6SRV: APRS station list on the Nuvi 350</p>
<hr />
<div>APRS station list on the Nuvi 350</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:Nuvimap.png&diff=229File:Nuvimap.png2009-10-30T14:50:48Z<p>VE6SRV: Sample Nuvi Map screen with APRS icons</p>
<hr />
<div>Sample Nuvi Map screen with APRS icons</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:OT2_MON08_pinout.png&diff=181File:OT2 MON08 pinout.png2009-09-03T20:20:15Z<p>VE6SRV: OT2 MON08 pinout diagram</p>
<hr />
<div>OT2 MON08 pinout diagram</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:OT2m_Reporting_Options.png&diff=179File:OT2m Reporting Options.png2009-09-03T18:56:20Z<p>VE6SRV: OT2m Reporting options section from OTWINCFG.</p>
<hr />
<div>OT2m Reporting options section from OTWINCFG.</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:OT2_Accessory.png&diff=178File:OT2 Accessory.png2009-09-03T17:54:47Z<p>VE6SRV: Accessory port on the front panel of the OT2m.</p>
<hr />
<div>Accessory port on the front panel of the OT2m.</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:OT2_MON08.png&diff=176File:OT2 MON08.png2009-09-03T16:06:09Z<p>VE6SRV: Close up photo of the MON08 pin header on the OT2m.</p>
<hr />
<div>Close up photo of the MON08 pin header on the OT2m.</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:OT2m_Voltage_Divider.png&diff=175File:OT2m Voltage Divider.png2009-09-03T15:56:14Z<p>VE6SRV: Close up of the voltage divider circuit on the OT2m.</p>
<hr />
<div>Close up of the voltage divider circuit on the OT2m.</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:OT2m_Temperature_Sensor.png&diff=174File:OT2m Temperature Sensor.png2009-09-03T15:49:26Z<p>VE6SRV: Closeup photo of the LM335D temperature sensor chip used on the OT2m.</p>
<hr />
<div>Closeup photo of the LM335D temperature sensor chip used on the OT2m.</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:Otplus-smt.jpg&diff=99File:Otplus-smt.jpg2009-03-02T04:18:28Z<p>VE6SRV: OT+ SMT</p>
<hr />
<div>OT+ SMT</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:Otplus-rev1_1.jpg&diff=98File:Otplus-rev1 1.jpg2009-03-02T04:16:47Z<p>VE6SRV: OT+ rev 1.1</p>
<hr />
<div>OT+ rev 1.1</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:Otplus-case.jpg&diff=97File:Otplus-case.jpg2009-03-02T04:15:35Z<p>VE6SRV: OT+ case</p>
<hr />
<div>OT+ case</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:Opentracker-t2-135-installed.jpg&diff=96File:Opentracker-t2-135-installed.jpg2009-03-02T04:13:44Z<p>VE6SRV: T2-135 installed</p>
<hr />
<div>T2-135 installed</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:Opentracker-t2-135.jpg&diff=95File:Opentracker-t2-135.jpg2009-03-02T04:11:07Z<p>VE6SRV: T2-135</p>
<hr />
<div>T2-135</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:Opentracker-ot2m-rear.jpg&diff=94File:Opentracker-ot2m-rear.jpg2009-03-02T04:09:54Z<p>VE6SRV: OT2m rear</p>
<hr />
<div>OT2m rear</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:Opentracker-ot2m-board.jpg&diff=93File:Opentracker-ot2m-board.jpg2009-03-02T04:08:31Z<p>VE6SRV: OT2m board</p>
<hr />
<div>OT2m board</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=File:Opentracker-ot2m.jpg&diff=92File:Opentracker-ot2m.jpg2009-03-02T04:07:50Z<p>VE6SRV: OT2m</p>
<hr />
<div>OT2m</div>VE6SRVhttp://wiki.argentdata.com/index.php?title=OT-Moto&diff=30OT-Moto2009-02-22T23:39:45Z<p>VE6SRV: First draft at the Motorola wiring page.</p>
<hr />
<div>The Motorola 16 pin accessory connector can provide all of the signals necessary to interface to an OT product, including providing enough current to power the unit.<br />
<br />
[[File:OT2-Moto.png|300px|thumb|left|Motorola 16 pin accessory port connection diagram]]<br />
<br />
Some Motorola radios have other pins as programmable options beyond what this diagram shows. All radios I have run across so far have been able to be programmed to match the pin out provided. I have successfully interfaced to Radius SM-50, Radius SM-120, and Radius M1225 units. I have provided a COR signal connection, although I run the RX audio output on pin 11 in an unsquelched mode, providing live audio 100% of the time, and set the OT2 for software carrier detect.</div>VE6SRV