From bounce-aprsnews-839@lists.tapr.org Sat Dec 2 12:31:06 2000 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.13) with SMTP id MAA27671 for ; Sat, 2 Dec 2000 12:31:05 -0600 (CST) Message-Id: Subject: [aprsnews] aprs.net unavailable Date: Sat, 2 Dec 2000 12:14:25 -0500 From: Steve Dimse To: "APRS Announcements" Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio X-Message-Id: <200012021714.eB2HER316556@raptor.netrox.net> Sender: bounce-aprsnews-839@lists.tapr.org Precedence: bulk There seems to be a problem with the T1 line at the museum, their router and web server have been unreachable along with www.aprs.net since yesterday morning. It seems likely that it will be down for the remained of the weekend. Steve K4HG --- You are currently subscribed to aprsnews as: lyris.aprsnews@tapr.org To unsubscribe send a blank email to leave-aprsnews-839E@lists.tapr.org Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org From bounce-aprsnews-839@lists.tapr.org Tue Dec 5 18:55:11 2000 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.13) with SMTP id SAA02620 for ; Tue, 5 Dec 2000 18:55:07 -0600 (CST) Message-Id: Subject: [aprsnews] aprs.net/findu.com status Date: Tue, 5 Dec 2000 17:02:53 -0500 From: Steve Dimse To: "APRS Announcements" Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio X-Message-Id: <200012052202.eB5M2c301275@raptor.netrox.net> Sender: bounce-aprsnews-839@lists.tapr.org Precedence: bulk The problem with the net access of www.aprs.net is related to a paperwork error. When the museum renewed the contract for their T-1 line, the paperwork got lost (I bet the check got cashed!), and on the expiration date the line got turned off. Worse still, the ISP had BellSouth tear down the leased line. So, even though the paperwork was easily squared away, they have to wait for BellSouth to redo the line. They hope to be back on line sometime in the next 48 hours. As proof that when it rains, it pours, findu.com began having poblems this afternoon. According to Telocity, there are no problems in the network now. It is possible some changes I made to my router yesterday are to blame, if so look for things to improve sometime after 11PM when I get home. Steve K4HG --- You are currently subscribed to aprsnews as: lyris.aprsnews@tapr.org To unsubscribe send a blank email to leave-aprsnews-839E@lists.tapr.org Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org From bounce-aprsnews-839@lists.tapr.org Wed Dec 6 19:44:59 2000 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.13) with SMTP id TAA17468 for ; Wed, 6 Dec 2000 19:44:58 -0600 (CST) X-Authentication-Warning: arctic.usna.edu: bruninga owned process doing -bs Date: Wed, 6 Dec 2000 19:40:03 -0500 (EST) From: Bob Bruninga X-Sender: bruninga@arctic To: "APRS Announcements" Subject: [aprsnews] APRS Satellite Design Details Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio X-Message-Id: Sender: bounce-aprsnews-839@lists.tapr.org Precedence: bulk Now that the launch of the US Naval Academy student built Satellite project is announced for August 2001, here are some design details. This was presented at the annual AMSAT conference in Portland Maine in October 2000. The students call it "PCSAT" for Prototype Communications Satellite although it is designed for APRS digipeating. NOTE: Use a FIXED FONT for best formatting of tables... ------------------------------------------------------------------------ USNA PCSAT: The mission of PCsat is unique in the Amateur Satellite Service as it is designed to support the text messaging and position tracking needs of mobiles and handhelds only and to provide links into the worldwide internet linked APRS system. UPLINK/DOWNLINK QUALITIES: Typical uplink and downlinks fall into several different classes based on user ERP and receiver antenna gain as shown below. The column labeled Standby-receive gain is for the user who is not aware of, nor optimized for satellite reception. For example, an HT in a pocket, or mobile parked under trees. It is assumed that stations intending to transmit to the satellite will be in the clear. ERP ERP Rcv Rcv Rcv UHF VHF UHF VHF STBY USERS (W) (W) dBi dBi dBi Applications --------- --- ---- --- --- --- ------------------------------ HANDHELDS 3 5 3 3 -6 Sailboats, Hikers, Wilderness MOBILES 70 100 5 5 -6 Boats, Remote Travelers HOME STNS 700 1000 13 13 * Not intended for PCsat NETWORK IGATE RCV 7 5 Omni Internet receive site MSG NODE 70 100 Internet to user UPLINK site COMMAND 700 1000 13 13 US Naval Academy Ground Station Notice that this satellite is not designed nor intended for shack-to-shack communications. It is optimized for mobiles and handhelds with OMNI whip antennas. MISSIONS: Since several other digital amateur satellites have provided imaging and file store-and-forward for the last several years, PCsat concentrates on the popular trend towards personal real-time wireless communications using UI digipeating. In this context, the following list prioritizes these needs. 1) Handheld/Mobile message uplink to Internet (emergency and routine) 2) Handheld/Mobile message downlink delivery from Internet (paging) 3) Handheld/Mobile station-to-station digital communications 4) North American wide Bulletin delivery to all users (occassional) 5) Handheld/Mobile GPS position tracking to internet 6) GPS tracking of buoys, telemetry devices, wildlife, expeditions,etc 7) Other UI digipeating applications (TBD) 8) Message Store-n-forward (non HAM populated areas only, if at all) FUNDAMENTAL ASUMPTIONS DRIVING THE DESIGN: 1) Optimum ALOHA TDMA channel effeciency is about 18% due to collisions 2) VHF links have a 9 dB advantage over UHF links (omni to omni) 3) 1200 baud AFSK has a 7 dB advantage (measured) over 9600 baud FSK 4) T/R delays render 9600 only twice as fast as 1200 for short bursts 5) UHF uplinks require wide bandwith to avoid doppler (- 4 dB) 6) UHF downlinks require user tuning throughout pass (not desired) 7) There are now on the market off-the-shelf amateur digital handheld and mobile transceivers suitable for this SATELLITE mission. 8) Anyone can assemble a similar station from existing components readily available over the last 20 years for 1200 baud. REQUIREMENTS/CONSTRAINTS Design Drivers: The following are some of the obvious first-order alignments of these requirements to hardware and to frequencies. From these, then, we determined the optimum trade-offs to arrive at our final design and frequency requirements. 1) MSG delivery to HT in Standby requires best possible downlink (1200 baud VHF). Igate uplink is relatively unconstrained. 2) MSG receipt from HT requires best possible uplink (1200 baud VHF). Downlink to internet is relatively unconstrained. 3) Continent wide Bulletin Delivery requires downlink on existing dedicated terrestrial APRS frequency (144.39 in North America) 4) HT/Mobile real-time messaging requires same up/downlink baudrate 5) GPS GAIN-HT and Mobile tracking is relatively unconstrained. 6) Low power GPS tracking devices requires best uplink (1200 baud VHF) and the uplink must not be used by any other satellite uplink to avoid unintentional interference to other systems. 7) Other UI digipeating applications should be crossband full duplex and should use same up/downlink baud rates 8) Store-n-forward (rare) is unconstrained with equal baud rates 9) Applications should be spread among multiple receivers to minimize collisions. 10) Reundancy, Backups and Fail-Safe RESET timers are desired. 11) UHF downlinks are of little value due to poor link budget and doppler 12) UHF Uplinks without tuning can be compensated with a 30 Khz SAT RCVR 13) KISS applies (Keep it Simple, Stupid) HARDWARE ALIGNMENT: Using the above as the basis, our design evolved to a pair of dual-port KPC-9612 TNC's. Each KPC-9612 can cross relay from either of its two inputs to its two outputs. Since we only have two transmitters on VHF for best downlink, we can output both the 1200 and 9600 baud channels to the same transmitter (with appropriate PTT/DCD cross strapping to avoid colllisions). ALthough we do not yet have frequency coordination for our two 2m downlinks and two 2m uplinks and two 70cm uplinks, we have gone ahead and penciled in the SUNSAT APRS channel and North American 144.39 APRS channels that we hope to share. USERS UPLINK TNC DOWNLINK ---------------- ------- ------------ --------------------- KPC-9612 #1 HT-to-HT 145.825 ------> 1200 Baud -*-----> 145.825 (ITU Subband) \ / | / \ | Mobile-to-Mobile UHF-U1 ------> 9600 Baud -* KPC-9612 #2 Low Pwr Trackers VHF-U2 ------> 1200 Baud -*-----> 144.39 (over USA ) \ / | / \ | Igate Paging UHF-U2 ------> 9600 Baud -* Igates will monitor both downlinks to capture every packet heard anywhere and feed to the worldwide APRServe internet linked network for distribution everywhere. DISCUSSION OF THE FREQUENCIES:: 1) 145.825 could be a shared UI digipeating frequency for such low dutycycle operations in synergism with other similar satelltes on the same frequency with agreement amongst them. See my AMSAT SYMPOSIUM Paper 1999. 2) VHF UPLINK#2 on any 2m frequency hopefully not shared with any other satellite uplink so that we do not QRM any other sats. We have no objections if this frequeny is another satellite downlink. Our user uplinks on this frequency will be about 5W ERP only for special applications in remote areas and will have minimum terrestrial range. 3) UHF UPLINK#1. Any 20 KHz frequency in the ITU UHF satellite band 4) UHF UPLINK#2. Any other 20 KHz frequency in the ITU UHF sat band 5) 144.39 has been blessed in North America for APRS by TAPR, ARRL and AMSAT-NA and their Canadian counterparts. Downlink on this frequency over North America is a unique opportunity hopefully welcomed by all current users in the region. This downlink will only be SPARSELY USED by special authorized stations for special events or special comms needs or special messaging to users not reachable by the terrestrial system. CONCLUSION: We hope that other amateur satellites will consider adding a transponder of this simplicity to join our constellation in supporting handheld and mobile amateur radio operators throughout the world. The power of APRS is its use of generic digipeater callsigns. Thus it does not matter what satellite is in view, they all will function equally to link the users to the rest of the world. Secondly, each user's need is only a few 1 second packets. THus the throughput and number of users supported can be far greater than the other FM satellites (voice). Similarly there is no advantage to channel hogging. Each user only gets one POSITION, One STATUS packet and any one-line messages pending. For more information on operating the current APRS capable Satellites now in orbit * For info on APRS Satellites http://web.usna.navy.mil/~bruninga/astars.html * To see the LIVE worldwide APRS data, TELNET to 199.227.86.221 port 23. * To see a LIVE map, BROWSE www.aprs.net and click on the WORLD map. * To find any APRS Mobile/Handheld/Station BROWSE Steve Dimse, K4HG's, http://map.findu.com/CALLSIGN There were some problems over the weekend with these sites, but they should be OK now. See ya on the birds! de WB4APR, Bob --- You are currently subscribed to aprssig as: bruninga@usna.edu To unsubscribe send a blank email to leave-aprssig-20817K@lists.tapr.org Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org --- You are currently subscribed to aprsnews as: lyris.aprsnews@tapr.org To unsubscribe send a blank email to leave-aprsnews-839E@lists.tapr.org Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org From bounce-aprsnews-839@lists.tapr.org Fri Dec 8 13:39:36 2000 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.13) with SMTP id NAA24552 for ; Fri, 8 Dec 2000 13:39:35 -0600 (CST) From: "Rob Wittner" To: "APRS Announcements" Subject: [aprsnews] APRS/CE Build 943 Date: Fri, 8 Dec 2000 13:47:32 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio X-Message-Id: Sender: bounce-aprsnews-839@lists.tapr.org Precedence: bulk And you thought I had disappeared... I pretty much had disappeared... I am currently working on two full-time software development contracts, so my apologies if I'm not replying to your e-mails in a timely manner. Also, my sincere apologies for getting behind in this latest build of APRS/CE. As always, you, my users, make this all worthwhile and I appreciate your patience and feedback. Get build 943 at http://www.tapr.org/~aprsce/ . This release adds a weather status page on the station info screen, wind speed and direction display, mobile course and speed display, _sound!_ for new messages, and a little indicator at the top to show new incoming messages. I'm sure there's a bunch of other little things as well, you'll see them as you start to use the program again. APRS/CE is getting very close to becoming version 1.0. However, because of my schedule, I've set the expiration for this version to _next_ _December_. That's December _2001_! A few of you had asked why I put expirations on my builds. My logic was that it was beta code and probably shouldn't be hanging around on people's machines for long periods of time - that way I only have one version to support. When APRS/CE goes to 1.0 and beyond, the expiration "feature" will be removed, replaced with a feature that requires registration before it saves any of your settings. The registration fee will be nominal, similar to pocketAPRS. Thanks again for your continued interest. Please, everyone, give me some feedback on the install and the program itself. 73 -Rob KZ5RW --- You are currently subscribed to aprsnews as: lyris.aprsnews@tapr.org To unsubscribe send a blank email to leave-aprsnews-839E@lists.tapr.org Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org From bounce-aprsnews-839@lists.tapr.org Fri Dec 8 13:43:00 2000 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.13) with SMTP id NAA24923 for ; Fri, 8 Dec 2000 13:42:59 -0600 (CST) Message-Id: Subject: [aprsnews] Problem with aprs.net domain Date: Fri, 8 Dec 2000 14:28:56 -0500 From: Steve Dimse To: "APRS Announcements" Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio X-Message-Id: <200012081929.LAA02144@albatross.prod.itd.earthlink.net> Sender: bounce-aprsnews-839@lists.tapr.org Precedence: bulk The T-1 line to the museum is still down, and there is a new complication. Apparently, after a week of being unable to contact the primary servers, the secondary name servers stop serving the domain. The line went down last Friday at 11:15 AM, so the secondaries died earlier today, a week later. What this means is sometime between now and 20 hours from now (as your local name servers drop their 24 hour cached names, you will lose the ability to look up any name in the aprs.net domain. Bad news for those of you using second.aprs.net as the name for the internet server. I've tried but cannot seem to find a way to get the secondaries started again without the primary coming on line. If anyone knows how, please let me know. I'm on the road, so my email will be intermittant, and my time to work on the problem severely limited... Steve K4HG --- You are currently subscribed to aprsnews as: lyris.aprsnews@tapr.org To unsubscribe send a blank email to leave-aprsnews-839E@lists.tapr.org Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org From bounce-aprsnews-839@lists.tapr.org Fri Dec 8 17:30:16 2000 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.13) with SMTP id RAA20738 for ; Fri, 8 Dec 2000 17:30:16 -0600 (CST) Message-Id: Subject: [aprsnews] Re: [aprssig] Re: FW: Problem with aprs.net domain Date: Fri, 8 Dec 2000 16:59:51 -0500 From: Steve Dimse To: "APRS Announcements" Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio X-Message-Id: <200012082159.NAA01570@albatross.prod.itd.earthlink.net> Sender: bounce-aprsnews-839@lists.tapr.org Precedence: bulk On 12/8/00 4:34 PM Greg Noneman (greg@clubnet.net) wrote: >Actually, it appears that name server is again correctly pointing to the >secondary APRS server. I do not know why that is has resumed operation >or whether it will remain functioning. Brent is correct in that the >local address of aprs.socal.interworld.net can always be used as a backup >when the name server fails. As always, unbuffered data is available on >port 23, buffered data on port 10151 and map server on port 8000. > It appears that aprs.net came online briefly, I got a number of error messages sent to my pager from it, though again it appears unreachable. Perhaps the secondaries got refreshed in the interim, or perhaps (more likely) Jeff's fix worked. The only secondary I can check myself is findu.com, which now appears to have a problem with the DSL line...ARRRRGGGG!!! Steve K4HG --- You are currently subscribed to aprsnews as: lyris.aprsnews@tapr.org To unsubscribe send a blank email to leave-aprsnews-839E@lists.tapr.org Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org From bounce-aprsnews-839@lists.tapr.org Sun Dec 17 20:17:16 2000 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.13) with SMTP id UAA00566 for ; Sun, 17 Dec 2000 20:17:15 -0600 (CST) Message-ID: From: "Ron Reeves" To: "APRS Announcements" Subject: [aprsnews] APRS and SAR & Sheriffs Date: Sun, 17 Dec 2000 17:55:36 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001D_01C06852.8F3FBD60" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio X-Message-Id: <002001c06895$9da620e0$01f7a8c0@vncvr1.wa.home.1com> Sender: bounce-aprsnews-839@lists.tapr.org Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_001D_01C06852.8F3FBD60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have been asked to put on a APRS demo for 3 local Sheriff's = departments (how did they get my name?) They seem to have some of the = same interests that the Search and Rescue groups have. =20 Does anyone have any suggestions or tips for giving a presentation to = such a group? Does anyone have a website covering this topic? Also, I know that they will likely ask me questions such as: 1) Can we use this with the Sheriff's Radio System? 2) Will it work with FRS? 3) How can this really help us? 4) Can we use topographical maps with this software? I know that technically it would work with their system or FRS, but is = it legal? Do the authors consider such usage as commercial and wish to = sell them software through a separate channel? Any thoughts? Any other = questions that they will ask? Ron Reeves N7QXO aprssigs@home.com ------=_NextPart_000_001D_01C06852.8F3FBD60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have been asked to put on a APRS demo for 3 local = Sheriff's=20 departments (how did they get my name?)  They seem to have some of = the same=20 interests that the Search and Rescue groups have. 
Does anyone have any suggestions or tips for giving = a=20 presentation to such a group?  Does anyone have a website covering = this=20 topic?
 
Also, I know that they will likely ask me questions = such=20 as:
1) Can we use this with the Sheriff's Radio=20 System?
2) Will it work with FRS?
3) How can this really help us?
4) Can we use topographical maps with this=20 software?
 
I know that technically it would work with their = system or=20 FRS, but is it legal?  Do the authors consider such usage as = commercial and=20 wish to sell them software through a separate channel?  Any = thoughts? =20 Any other questions that they will ask?
 
Ron Reeves
N7QXO
aprssigs@home.com
 
 
------=_NextPart_000_001D_01C06852.8F3FBD60-- --- You are currently subscribed to aprsnews as: lyris.aprsnews@tapr.org To unsubscribe send a blank email to leave-aprsnews-839E@lists.tapr.org Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org From bounce-aprsnews-839@lists.tapr.org Thu Dec 21 21:16:26 2000 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.13) with SMTP id VAA21770 for ; Thu, 21 Dec 2000 21:16:22 -0600 (CST) Message-Id: Subject: [aprsnews] Tracking pages on findu Date: Thu, 21 Dec 2000 20:19:15 -0500 x-sender: sdimse@netrox.net From: Steve Dimse To: "APRS Announcements" Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio X-Message-Id: <200012220119.eBM1Jj317804@raptor.netrox.net> Sender: bounce-aprsnews-839@lists.tapr.org Precedence: bulk Stan's nice article about findu has caused many people to investigate the track page shown in QST. As I mentioned in my unofficial release of these, they are not ready for prime-time. When more than one request is pending at a time, the server starts thrashing on the requests, and the result is a noticible slowdown. Three times today people have noted the page not loading fast, and kept resending the page request, with the result that dozens of these requests queued up and brought the server to a standstill. I've had to manually retart the MySQL server to restore service. Until I am able to set up a new table that can handle these track requests more efficiently, the track pages are offline. Sorry for the inconvenience. No other pages are affected. Steve K4HG --- You are currently subscribed to aprsnews as: lyris.aprsnews@tapr.org To unsubscribe send a blank email to leave-aprsnews-839E@lists.tapr.org Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org From bounce-aprsnews-839@lists.tapr.org Mon Dec 25 07:41:23 2000 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.13) with SMTP id HAA07590 for ; Mon, 25 Dec 2000 07:41:19 -0600 (CST) Message-Id: Subject: [aprsnews] tracks available on findu Date: Mon, 25 Dec 2000 05:09:27 -0500 x-sender: sdimse@netrox.net From: Steve Dimse To: "APRS Announcements" Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio X-Message-Id: <200012251009.eBPA9e302739@raptor.netrox.net> Sender: bounce-aprsnews-839@lists.tapr.org Precedence: bulk Those of you with nothing better to do Christmas Eve/Morning may have noted that findu was offline for 5 hours. I took advantage of a slow night at work to rebuild the position database to make the position queries efficient for the track cgis. The improvements were all I had hoped they would be. As a result, the two track cgi's are now online, most likely permanently. http://www.findu.com/cgi-bin/track1.cgi?call=k4hg-8 This one places a red dot on each position heard. http://www.findu.com/cgi-bin/track.cgi?call=k4hg-8 This is the one most people are likely to use, it is the one displayed in Stan's article. However there is still a problem with this one. I build a URL request for MapBlast with each of the points for which a position was received. However, MapBlast tries to fit these points into a road route, often with unrealistic results. I'd like MapBlast to simply draw lines between the points, but so far I have been unable to figure out if this is possible. MapBlast releases no documentation on their map parameters, everything you see is reverse engineered. If anyone wants to dig in and try to find something that works, I'd love it... Both tracks go back 2 days or 190 points, whichever is less. Most likely I will make the time to search backward a parameter, but the number of points is limited by MapBlast. Steve K4HG --- You are currently subscribed to aprsnews as: lyris.aprsnews@tapr.org To unsubscribe send a blank email to leave-aprsnews-839E@lists.tapr.org Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org