Revised 1-7-99 to add KPC3+ software use. See revisions at the end of this text file for KPC3+ version 8.3 firmware. The following is a description to set up a stand alone tracker for APRS use. The commands shown are for a KPC3, but are the same for all the Kantronics that have GPS compatible software. (KPC3+ too) For the KPC3 et al: <<< you must have at least Version 6.0 software in <<< a KPC3 to make these work. Unsure? type VER <<< at the CMD: prompt, or turn off/on the tnc <<< and read the signon message. You need to set these commands before GPS use. GPSHEAD - this command tells the tnc what ASCII string to look for from the GPS unit. The typical setting are $GPRMC ,$GPGLL and $GPGGA. Note, you must use upper case, as this command is case sensitive. There are four (4) buffers that can be captured. Here is an example of capturing all four buffers. Try this: GPSHEAD 1 $GPRMC GPSHEAD 2 $GPGLL GPSHEAD 3 $GPGGA GPSHEAD 4 $GPRMC Also, you could have put $GPRMC or any of the other choices in all four positions. I used a different one in each to show that you could. You should be aware that since there are four (4) buffers, there are also 4 different routes to be able to beacon. If you want a specific $GPxxx string to go a specific route you will want to make sure the path in LTP matches the same number in GPSHEAD x. LTP - This command specifys routes the data in each buffer (LTx x=1-4) will be take. The data gets captured in buffers (LT1, LT2, LT3, LT4) which were captured with GPSHEAD x (x=1,2,3,4). Try this: LTP 1 APRS via RELAY,WIDE,WIDE LTP 2 APRS via RELAY LTP 3 APRS via TRACE,TRACE LTP 4 APRS via WR6ABD,K6IXA-3,WA6JJA-3,WIDE,W6APA,WIDE Note: be careful of the number of paths in your LTP statement. If it is too long, like the last one shown, it will cause "comma not found" error in APRS, [note - this was fixed in APRS827 version] since the number of characters that make up the DIGI path plus the GPS data string is very long, causing APRS not to be able to find the end of the GPS line. Also you don't have to use all 4 buffers. If you dont want to use a specific buffer, issue a LTP x NONE to turn it off. BLT - This command tells how often to send each one of the four LTx buffers via the LTP x paths. To set timer do this: BLT 1 EVERY 00:03:00 BLT 2 EVERY 00:04:00 BLT 3 EVERY 00:05:00 BLT 4 EVERY 00:06:00 The first example transmits the first LT1 buffer down the LTP 1 path "every 3 minutes" There are a few options, like, have the beacon go out starting a certain time. See the manual for complete options for this setting. The above settings are mostly typical. ABAUD - You will want to set this to match the baud rate that your GPS outputs. Typically this is 4800 baud. I have seen other makes of GPS use baud rates other than this. The baud rate will take effect once you turn the tnc off and then back on. Your current baud rate will be in effect till then. INT GPS - [mandatory in versions 6.0 and 8.2 - available in 8.3 KPC3+] Do this command before you power down the tnc and turn it back on. When you do, the TNC will be at the ABAUD rate, and be listening to the RS232 port where you have the data from the GPS connected to. To return the TNC back to TERMINAL mode, you will have to match the baud rate as set to ABAUD with your terminal, and issue three CONTROL C's. The tnc will revert the GPS mode back to TERMINAL. You will have to manually reset INT GPS to go back if you desire. RTEXT - Input a ASCII string to enable remote control of your tracker. Since you were able to set the paths, and timers with your terminal you didn't need this. But now that you have installed the TNC in the vehicle, you will want to be able to "remotely" set the values (like change times, and paths). This text will be used to allow access. When you connect to the MYREMOTE call sign, the TNC will send you three strings of numbers. You have the option to use any one of the three lines to respond. The text you input will have a character positional relationship to the text itself. MARY HAD A LITTLE LAMB 1111111111222 1234567890123456789012 If the TNC sends 7,3,17,21,10 you would respond with AREMA These characters are what make up the 7th, 3rd,17th,21st, and 10th character into the string. Make sure you answer back with the same CASE, as the string is case sensitive. See the book for more details if desired. MYREMOTE Set this to a callsign, or verbiage (like CAR) so that you have a callsign to connect to for remote commanding. This HAS to be different than the MYCALL in the TNC. CONOK Set this to off. You dont want anyone to connect to the tracker. As an alternate to the OFF setting, you could setup a Ctext, with a message stating something about this being a tracker, and then set the CMSG to DISC. Some users put their EMAIL address in the CTEXT. Beacon Set this to a value to beacon the BText. You will want to put something in BTEXT, as this shows up as a Status page on APRS. A typical setting is BEACON Every 3 BTEXT Some users put a Email address in this string. Some also put some kind of data like radio type GPS model etc. Remember to keep it short, as APRS only uses about 45 characters of this text on the L page. Also as an alternative, you can change the character of your vehicle by placing a APRS character in curly brackets in the very beginning of the Beacon text. {/} Byrons truck tracker. wa6ylb at theworks.com would be a DOT character instead of the truck symbol that the SSID of -12 produces by default. See F1 Symbols and or SYMBOLS.TXT in C:\APRS\README directory for choices. HID Set to Off. Your tracker is sending your callsign every so many minutes. You wont need this. LEDS If your running on batteries and want to turn the LEDS off on the front panel of the TNC, set this to OFF. Unproto This is where you place a path for the BEACON text to travel. A typical setting is Unproto APRS via WIDE,WIDE. ----------------------------------------------------------------------------- Powering the TNC and GPS from a KPC3 -or- KPC3+. It is possible to "rob" power from the TNC itself to power the GPS. I have successfully done this on my KPC3 & KPC3+. On the KPC3, 12 volt power for operating the GPS will be available on pin 25 of the DB25 connector, where the data to / from the GPS connects. To enable the power in the TNC to come out this pin, you must solder a jumper across two sets of pads. Take the cover off the tnc and look in the top left corner, as the leds on the front panel are down. Look for J8 and J9, which are real close to the edge of the DB25 and the power plug. Here is a map which shows the connections. +12v-------2 O O 2----Goes to pin 7 of DB9 Radio connector KPC3 only common O----O common 1 O O 1-----Goes to pin 25 of DB25 J8 J9 for KPC3... To route power to pin 25 of the DB25, add a jumper from the #2 pad to the center common of J8. Then add a jumper from the center common pad of J9 to #1 pad of J9. In my application, I was able to obtain power from the radio, and I ran it down the same wire leads as the PTT, tx and rx audio. I added another jumper to J9, from the center common pad of J9, to both pins pads of #1 and #2 of J9 (all three pads soldered together). When the radio goes off, the tnc and GPS shut off. Works nice. Power connection to the radio is on the radio connection DB9 pin 7. for KPC3+... On the KPC3+, the power can be routed in a similar fashion. According to the schematic here, the power can be had when J7 common (middle pad) is connected to #1 pad of J7, and the center common pad of J6 is connected to #2 pad of J6. (there is a common circuit connection between the center pads of J6 and J7 just like there is for the KPC3 J8 and J9). This runs the power out pin 13 on the DB25. This is different than pin 25 on the KPC3. You might want to add a jumper between pin 13 and pin 25 in your male DB25 data cable to the GPS, in case you want to use the tracker with a KPC3 or KPC3+ (the target tnc will need the internal jumpers added - they dont come from the factory this way). To obtain power from the radio connector, add another (in addition to the jumper just described) jumper from pad #2 of J7 to the center common of J7. connection. This also allows power to be sourced from the Radio connector to run both the TNC and GPS. Power connection to the radio is on the radio connection DB9 pin 7. -------------------------------------------------------------------------- Connecting the data out of a Garmin data cable to the KPC3 DB25 port. My Garmin data power cable has four wires in it. They are as follows Red with fuse holder ----> goes to pin 25 on the male DB25 connector. Black ----> goes to pin 7 on the male DB25 connector. White data fm tnc to gps ----> goes to pin 3 on the male DB25 connector. Brown data fm gps to tnc ----> goes to pin 2 on the male DB25 connector. --------------------------------------------------------------------------- The setup for Tripmate is very similar, but you must use a pullup resistor (R48 4.7k in KPC3 ) inside the TNC, to make the DSR line positive on the TNC to connect to the DTR line on the Tripmate. The DTR acts like a on/off for the Tripmate. Make the following connections for a Tripmate to a kpc3 DB25 male KPC3 DB9 male for tripmate 2-------------------------------2 and 3 7-------------------------------5 gnd 6-------------------------------4 Warning - the tripmate needs regulated voltage. Dont just use the 12 Volts on pin 25 (kpc3) or pin 13 (kpc3+) straight into the Tripmate. You will need to make a 6 volt regulator that *can* get its power from here though. ---------------------------------------------------------------------------- Also, some GPS units ( Oncore?) need ASCII characters sent to the the GPS to get it operating as desired. See the GPSINIT string command. If your tnc needs these characters sent, you will need to make sure that the data out of the TNC to the GPS exists. This would be a wire from pin 3 of the DB25 on the TNC, to the GPS data input. ---------------------------------------------------------------------------- Setting in the GPS itself. For GPS II+, I have set the following data. On the MENU page - select INTERFACE Highlight the top line, and hit enter. Use the cursor pad to select NMEA/NMEA Hit ENTER key to set this mode. The baud rate is fixed at 4800 baud. Hit QUIT to return to the MENU screen. Select DATUM with the cursor key, and change it to NAD27 CONUS. Most maps for APRS are made from this DATUM. All the CD-ROM maps are NAD27. Hit ENTER to select this mode. Move the cursor back to POSN: and hit ENTER. Select the hddd mm.mmm' format. Hit ENTER to set it. Since your here, you might as well go down to the HEADING line and change it to TRUE. Hit Enter and choose TRUE. Hit ENTER button to set it. Hit QUIT to return to the MENU screen. Go to SYSTEM SETUP and select it. Hit ENTER to select it. Move the cursor to OFFSET. Hit enter to choose it, and change it to +00.00. Set it with the ENTER key. Do the same for HOURS, but set it to 24. Hit the Quit to return to the MENU screen. Choose the screen you desire with the PAGE button. I normally choose the blank looking screen as it will show a bread crumb trail of where you have been. Connect the data cable, tnc cable, and radio cable and your all set. ----------------------------------------------------------------------------- Revisions for KPC3+ with version 8.3 firmware EPROM installed. This doesn't apply to a KPC3. This is only for a KPC3+ with 8.3. Version 8.3 firmware allows for a "second" serial port to be used to capture GPS raw data. This differs from the original settings as described above by having the serial data applied to pin 2 (data in) and pin 6 (ground) in the DB9 radio interface connector. NOTE: if you jumper J5 to "center and 1" this will supply another ground point on pin 9 in this same DB9 radio connector. This will certainly make it easier to solder the ground from the GPS data leads to an unused pin in the DB 9 instead of trying to add this wire to pin 6 which already has a wire in it. I still obtain 12v power from pin 7 of the DB9 radio connector as described above. The old method (versions 6.0 and 8.2 firmware) required the GPS data be presented via the DB25 connector, and the INT GPS command be issued to cause the tnc to gather the raw GPS data from this same DB25 serial port. The INT GPS command still exists, but you wont want to use it now and it wont work if you have your GPS data coming in this new software serial port input. If your old setup needed GPSINIT string to be send, this wont work with the software serial port, as there isn't any place for the serial INIT string to come out of to get to the GPS input. By having the data come in the "software" serial port, this allows the regular serial port to connect to the serial port on a laptop. This is what I have done in my own tracker and below is the settings I used to do so. First off, make sure the settings in the KPC3+ (v8.3 firmware) are as listed below. INT TERM This was INT GPS. Now leave the TNC in regular mode. Dont leave it in the GPS mode. GPSPORT 4800 NORMAL CHECKSUM Use the above string as a starting point. This setting assumes your gps is sending data at 4800 baud, with normal data polarity (alternate setting is INVERTED) CHECKSUM causes the tnc not to load the data into its buffers unless the checksum is "correct". If your GPS doesn't generate a checksum, use NOCHECK instead of CHECKSUM. A setting of 0 for the baud rate turns this function off. Note The LT buffers, as specified by the GPSHEAD settings are filled with GPS data as found on this software serial port. If you only have one GPSHEAD buffer defined, then only one LT buffer that's associated with it will be filled. GPSTIME ON RMC This sets the clock in your TNC via a valid GPS RMC message. This isn't required to be present in your setup at all but it doesn't hurt. Alternate to RMC is GGA, GLL and ZDA. If you happen to do a MHeard command (O C T mode) then the time stamp will be correct in the tnc. LGETCHAR $05 This is a CONTROL E character that a laptop can send to get the TNC to send the contents of the LT buffers to your LAPTOP. It should be defaulted to 05 hex, and set it to 05 if it isn't. The setup for BLT and LTP is the same as described in the old settings for 6.0 and 8.2 trackers above. Using this new second software serial port allows the TNC to be stand alone and change over to laptop tracker automatically. Here is how that works. The tnc will still send out the contents of the LT buffers if the LTP and BLT are still set. This means, that if you have your laptop setup running APRS, and have it sampling the gps data via the second "software" serial port the tnc will be sending raw GPS beacons out, because there are valid BLT timer settings and LT buffers contain some data. The second serial port GPS data will continue to fill the LT buffers of the TNC with valid GPS data and will beacon this data as a standalone tracker unless you either turn off the BLT timers or turn off data to the TNC and clear the LT buffers [see CLEAR command as an option to the BLT timer statement]. I have added code to the INITKAN.TNC file to do this. Edit your INITKAN.TNC file (in C:\APRS\system\ directory and add the following: blt 1 e 00:00:00 clear blt 2 e 00:00:00 clear blt 3 e 00:00:00 clear blt 4 e 00:00:00 clear This turns off the raw packets and lets your LAPTOP send the positions packets. One other "trick" to do, is to specify a special path that's above and beyond the setting within the laptop tracker. In my special case, I wanted a "GATE" beacon to still occur and as such I added (or changed) the following data: blt 4 e 00:05:00 clear LTP 4 GPSLJ via WA6YLB-2,GATE GPShead 4 $GPRMC This allowed one raw packet to be sent while the LAPTOP is running. I dont have to specify a gate path within APRSdos to get the mobile to be gated. --------------------------------------------------------------------- In RESTORE.TNC I added code to turn the tnc back into a standalone (such as the laptop is OFF, or disconnected from the TNC) tracker. Insert this code into the file RESTORE.TNC, which is set to the TNC when the laptop is properly shut down. gpshead 1 $GPRMC gpshead 2 $GPRMC gpshead 3 $GPRMC gpshead 4 $GPRMC LTP 1 GPSLJ via LOCAL LTP 2 GPSLJ via WIDE,WIDE LTP 3 GPSLJ VIA WIDE3-3 LTP 4 GPSLJ VIA WA6YLB-2,GATE BLT 1 EVERY 00:00:20 clear BLT 2 EVERY 00:02:00 clear BLT 3 EVERY 00:02:30 clear BLT 4 EVERY 00:02:45 clear bt Byron's truck (laptop off line) tracker wa6ylb at theworks.com b e 3 gpsport 4800 normal checksum gpstime valid rmc ------------------------------------------------------- To setup APRSdos, start APRS as normal. Only tell APRSdos you have just the KPC3+ on a single serial port. To get the GPS data to start happening, Do an ALT S (G)ps (M)ode (E)sp to start the ESP. APRS will flash the message about needing a GPS # in a yellow box in the middle of your screen. Do an ALT S S to enter your main APRSdos registration #, and then the GPS registration #. Make sure you save your settings with ALT S S when your done with APRS. One caution. If your setting in GPSHEAD within the tnc is $GPGGA and you have the GPS MODE of RMC selected in APRSdos, you wont ever get a position of your location showing in APRSdos. This is due to the data coming from the TNC being GGA data and APRSdos is looking for RMC data. You might want to set the INITKAN.TNC file up to include: GPSHEAD 1 $GPRMC GPSHEAD 2 $GPGGA so that no matter which mode you have APRS setup for, APRSdos will be supplied with a gps packet from the TNC that matches the mode APRSdos your set to. Questions? Email me at wa6ylb at remove this yahoo.com