From bounce-mic-e-2619@lists.tapr.org Mon May 3 13:48:12 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id NAA11699 for ; Mon, 3 May 1999 13:48:09 -0500 (CDT) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: Date: Mon, 3 May 1999 13:46:54 -0500 To: "TAPR MIC-E & PIC-E Special Interest Group" From: Greg Jones Subject: [mic-e] General Announcement on APRS Working Group Meeting List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk General Announcement on APRS Working Group Meeting Bob Bruninga, WB4APR, Steve Dimse, K4HG, Keith Sproul, WU2Z, Greg Jones, WD5IVD, and John Ackermann, N8UR met near Baltimore, Maryland on Saturday May 1st and Sunday May 2nd to hold an in-person meeting concerning the recent issues of importance related to the future of APRS. The main issues discussed were: * Determine process to open APRS development. * Determine the management process for the APRS protocols. * Determine the publication process for the APRS protocol standard. * Determine and publish a certification/validation process for APRS items and programs. The meeting was very productive with substantial and positive progress made on these issues. The group developed a working plan and a task list for continued discussion and closure before Dayton. Deliberation on the working plan will occur this week to allow the participants who were not available (Authors Mark Sproul, KB2ICI, will be out of town, Brent Hildebrand, KH2Z, and Mike Musick, N0QBF) to have input on the working plan as developed at the meeting. All involved were pleased with the outcome of the meeting and the working plan that resolved outstanding issues. The group is now focused on the positive and growing aspects of APRS and creating a process that will open the development of APRS hardware and software. Over the next 10 days the group will finalize the remaining details and will make a formal announcement on substantive decisions and plans before Dayton HamVention. Greg Jones, WD5IVD for the APRS Working Group ----- Greg Jones, WD5IVD Austin, Texas wd5ivd@tapr.org http://www.tapr.org/~wd5ivd --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Wed May 5 23:47:43 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id XAA17054 for ; Wed, 5 May 1999 23:47:42 -0500 (CDT) Date: Wed, 5 May 1999 23:47:32 Subject: [mic-e] converting an existing repeater to receive MIC-E APRS transmissions To: "TAPR MIC-E & PIC-E Special Interest Group" From: "Tom Smith" List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" Sender: bounce-mic-e-2619@lists.tapr.org Message-Id: Precedence: bulk Where can I find information about the procedures and the hardware it will take to convert an existing 2M repeater to receive MIC-E APRS transmissions? I would like to talk the local repeater into APRS support but need more info. Thanks, Tom KD6SOJ --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Thu May 6 09:33:42 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id JAA15075 for ; Thu, 6 May 1999 09:33:40 -0500 (CDT) From: austin@magicnet.net Organization: Custom Micro Systems To: "TAPR MIC-E & PIC-E Special Interest Group" Date: Thu, 6 May 1999 10:34:00 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: [mic-e] Re: converting an existing repeater to receive MIC-E APRS Reply-to: "TAPR MIC-E & PIC-E Special Interest Group" Priority: normal In-reply-to: X-MDaemon-Deliver-To: mic-e@lists.tapr.org X-Return-Path: austin@pop3.magicnet.net Message-ID: 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-mic-e-2619@lists.tapr.org Precedence: bulk > Subject: converting an existing repeater to receive MIC-E APRS > transmissions From: "Tom Smith" Date: Wed, 5 May 1999 > 23:47:32 X-Message-Number: 1 > > Where can I find information about the procedures and the hardware it will > take to convert an existing 2M repeater to receive MIC-E APRS > transmissions? I would like to talk the local repeater into APRS support > but need more info. Thanks, Tom KD6SOJ Aaron (AE4KO) and I (KD4ZDD) have fabricated a APRS MIC-E crossband repeater (from 442.25/447.25) in Orlando. We are currently documenting our installation but have not yet finalized the article. I would be glad to help you with any direct questions regarding our installation. Your situation will be slightly tougher since you are inbanding to APRS. I suspect that the Digi radio will be forced to have at least two cans of a duplexer inline on TX/RX . Hopefully your voice repeater is operating in the upper end of the 2m band :) Both sides of your system will have to have well tuned duplexers! In brief, our system uses two Kantronics TNCs that feed the same VHF Mitrek radio on 144.39 The first TNC is configured as a typical full service digi on 2m. It is a KPC3+ The second TNC is an old KPC-9612 and is wired to listen for packets received on the 70cm input frequency of the voice repeater. This TNC is modified to provide a "packet detected" or mute signal. I believe that the current firmware for the KPC3+ now supports this signal out of the box. Each TNC feeds the other TNC's XCD pin from their respective PTT lines. The XCD input is configured in "Hold Off" mode. This allows collision detection between the two bands. Each TNC PTT output is "diode-ORed" to the PTT of the Mitrek. In your situation, you could feed the voice repeater's PTT line to the XCD input if you don't want both transmitters up at the same time. My modification to the KPC-9612 is simple-- a single transistor wired open collector style to the 1200 baud port "RX" LED. The TNC is set for CD SOFTWARE mode (for open squelch). When a packet is detected by this TNC, the derived mute signal is used to remove the "PL active" line from the voice repeater controller. That in turn causes the voice repeater to drop prior to the actual loss of PL. The voice repeater controller is in AND-PL mode. The audio delay board in the voice repeater "buys" us just enough time for the controller to drop the voice repeater signal path before the packet burst is heard. The result is that MIC-E packets are never heard on the voice repeater. The only detectable difference is a slight change in the time delay before the courtesy beep is fired. You will need to instruct your MIC-E enabled folks to not use PL when they are in MIC-E AUTO mode. This mode will kerchunk the voice repeater endlessly! I have set aside a memory in my MIC-E mobile to have the same configuration as normal for repeater operation, BUT without PL encode enabled. This way I can monitor the repeater activity and still be a MIC-E tracker. Warren Merkel KD4ZDD --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Thu May 6 10:54:43 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id KAA17118 for ; Thu, 6 May 1999 10:54:42 -0500 (CDT) Message-ID: Date: Thu, 06 May 1999 08:52:24 -0700 From: George Carr MIME-Version: 1.0 To: "TAPR MIC-E & PIC-E Special Interest Group" CC: Bill Hurd Subject: [mic-e] Re: converting an existing repeater to receive MIC-E APRS References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: <3731BAB8.8DA8C8B4@telebyte.com> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk I HAVE A MIC E DIGIPEATER QUESTION. MAYBE SOMEONE CAN HELP. We have a brand new KPC-9612 1200/9600/1200 [using the two 1200 ports] hooked between a UHF receiver monitoring our local UHF repeater and a VHF transmitter set to send the APRS packets into 144.390MHz. We suspect that the Mic E data bursts on not being re-transmitted through the 9612 because we may have the software not configured properly. Anyone willing to take a look? I can forward the 9612 internal settings in any document format you can read, including fax. George, N7GME austin@magicnet.net wrote: > > Subject: converting an existing repeater to receive MIC-E APRS > > transmissions From: "Tom Smith" Date: Wed, 5 May 1999 > > 23:47:32 X-Message-Number: 1 > > > > Where can I find information about the procedures and the hardware it will > > take to convert an existing 2M repeater to receive MIC-E APRS > > transmissions? I would like to talk the local repeater into APRS support > > but need more info. Thanks, Tom KD6SOJ > > Aaron (AE4KO) and I (KD4ZDD) have fabricated a APRS MIC-E > crossband repeater (from 442.25/447.25) in Orlando. We are > currently documenting our installation but have not yet finalized the > article. I would be glad to help you with any direct questions > regarding our installation. > > Your situation will be slightly tougher since you are inbanding to > APRS. I suspect that the Digi radio will be forced to have at least > two cans of a duplexer inline on TX/RX . Hopefully your voice > repeater is operating in the upper end of the 2m band :) Both > sides of your system will have to have well tuned duplexers! > > In brief, our system uses two Kantronics TNCs that feed the same > VHF Mitrek radio on 144.39 The first TNC is configured as a > typical full service digi on 2m. It is a KPC3+ > > The second TNC is an old KPC-9612 and is wired to listen for > packets received on the 70cm input frequency of the voice > repeater. This TNC is modified to provide a "packet detected" or > mute signal. I believe that the current firmware for the KPC3+ now > supports this signal out of the box. > > Each TNC feeds the other TNC's XCD pin from their respective PTT > lines. The XCD input is configured in "Hold Off" mode. This allows > collision detection between the two bands. Each TNC PTT output > is "diode-ORed" to the PTT of the Mitrek. In your situation, you > could feed the voice repeater's PTT line to the XCD input if you > don't want both transmitters up at the same time. > > My modification to the KPC-9612 is simple-- a single transistor > wired open collector style to the 1200 baud port "RX" LED. The > TNC is set for CD SOFTWARE mode (for open squelch). When a > packet is detected by this TNC, the derived mute signal is used to > remove the "PL active" line from the voice repeater controller. That > in turn causes the voice repeater to drop prior to the actual loss of > PL. The voice repeater controller is in AND-PL mode. > > The audio delay board in the voice repeater "buys" us just enough > time for the controller to drop the voice repeater signal path before > the packet burst is heard. > > The result is that MIC-E packets are never heard on the voice > repeater. The only detectable difference is a slight change in the > time delay before the courtesy beep is fired. > > You will need to instruct your MIC-E enabled folks to not use PL > when they are in MIC-E AUTO mode. This mode will kerchunk the > voice repeater endlessly! I have set aside a memory in my MIC-E > mobile to have the same configuration as normal for repeater > operation, BUT without PL encode enabled. This way I can monitor > the repeater activity and still be a MIC-E tracker. > > Warren Merkel > KD4ZDD > > --- > You are currently subscribed to mic-e as: SEMCOR@TELEBYTE.COM > To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Thu May 6 22:40:51 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id WAA08699 for ; Thu, 6 May 1999 22:40:51 -0500 (CDT) Message-ID: From: "Wes Johnston" To: "TAPR MIC-E & PIC-E Special Interest Group" Subject: [mic-e] Re: converting an existing repeater to receive MIC-E APRS transmissions Date: Thu, 6 May 1999 23:42:39 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: <00f101be983b$a978a0e0$0300a8c0@bbyfce> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk Depends on what you want to do.... there are two ways to go.... 1. A simple digipeater that will only get mic-e packets from your repeater's audio to the aprs 2m frequency. 2. A full service digipeater at the same site as the repeater that will *also* get mic-e packets over to 2m. Method 1 requires only a kpc3 or kpc3plus. You hook up the RX audio (kpc pin 5) to the repeater's audio. hook up the PTT , TX audio and XCD pins (3, 1, and 2) to the 144.39 transciever. and the grounds too. Here is where it get's *interesting*. Since the TNC is listening to the repeater audio for a packet, it can't hear 144.39. Since it can't hear 144.39, it could tx at the same time as another packet on 144.39. The XCD pin needs to be hooked to a squelch indicator on your 144.39 radio. It must be high when the squelch is open (not muted). Kenwood radios are upside down.. they are low when not muted.... but that is another matter. On many new radios, you will find a squelch indicator in the mic jack, and on the older (mid 1980's) you will find a LED around the front panel. All that matters is that you get 0v when the radio is quiet, and 5 or more volts when the radio is not muted. The kpc3+ v8.3 has a MUTE function also.... one of it's pins will pull low when packet racket is heard on the repeater... this can be tied into your COR or PL tone enable inputs on your repeater cotroller to mute the packets on the output of the repeater. Method #2 requires a kpc4 (dual port 1200 tnc), a kpc9612 with the additional 1200 modem, or two TNCs with either stealthdigi or aprsdigi software. Wes - kd4rdb@qsl.net http://www.qsl.net/kd4rdb Where am I? http://map.aprs.net/kd4rdb-9 http://map.aprs.net/kd4rdb-10 CW - the code that stops up your node. -----Original Message----- From: Tom Smith To: TAPR MIC-E & PIC-E Special Interest Group Date: Thursday, May 06, 1999 12:48 AM Subject: [mic-e] converting an existing repeater to receive MIC-E APRS transmissions >Where can I find information about the procedures and the hardware it will >take to convert an existing 2M repeater to receive MIC-E APRS >transmissions? I would like to talk the local repeater into APRS support >but need more info. Thanks, Tom KD6SOJ > >--- >You are currently subscribed to mic-e as: KD4RDB@bellsouth.net >To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org > > --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Fri May 7 09:13:49 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id JAA10563 for ; Fri, 7 May 1999 09:13:49 -0500 (CDT) Sender: bounce-mic-e-2619@lists.tapr.org Date: Fri, 7 May 99 10:13:34 EDT From: Alan Crosswell To: "TAPR MIC-E & PIC-E Special Interest Group" Subject: [mic-e] Re: converting an existing repeater to receive MIC-E APRS transmissions In-Reply-To: Your message of Thu, 6 May 1999 23:42:39 -0400 Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" Message-ID: List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio X-Message-Id: Precedence: bulk >additional 1200 modem, or two TNCs with either stealthdigi or aprsdigi >software. Or my setup: Two TNCs wired back to back with a null-terminal cable. The TNC lisenting to the repeater is running a KISS EPROM. The other TNC is running TheNet X1J4 with L2 digipeating enabled and the host interface running in KISS mode. All packets received by the KISS TNC are retransmitted by the X1J4 TNC and, the X1J4 performs basic digipeating functions. It supports multiple aliases by husing the alias, hostalias, etc. 73 de Alan N2YGK PS: And we already had cavities on the repeater input/output and added a cavity on the 144.39 digipeater. This is at a high-RF site (County radio tower with several commercial paging and broadcast tenants in addition to public safety agencies). --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Fri May 7 09:14:54 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id JAA10619 for ; Fri, 7 May 1999 09:14:53 -0500 (CDT) Message-ID: Date: Fri, 07 May 1999 07:11:11 -0700 From: George Carr MIME-Version: 1.0 To: "TAPR MIC-E & PIC-E Special Interest Group" CC: Bill Hurd Subject: [mic-e] Re: converting an existing repeater to receive MIC-E APRS transmissions References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: <3732F47F.E651F6E6@telebyte.com> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk Wes, We have a Mic E digipeater we are trying to get to work which includes a KPC-9612 Plus 1200/9600/1200 and a UHF receiving Mic E data bursts from our local mountain top repeater with an Alinco VHF packet transmitter sending out to 144.390MHz APRS. Our problem is that we don't think our software is setup correctly. Can you tell us more about Method #2 and the APRSdigi software you spoke of? Thanks in advance for any help. George, N7GME Wes Johnston wrote: > Depends on what you want to do.... there are two ways to go.... > > 1. A simple digipeater that will only get mic-e packets from your repeater's > audio to the aprs 2m frequency. > > 2. A full service digipeater at the same site as the repeater that will > *also* get mic-e packets over to 2m. > > Method 1 requires only a kpc3 or kpc3plus. You hook up the RX audio (kpc > pin 5) to the repeater's audio. hook up the PTT , TX audio and XCD pins (3, > 1, and 2) to the 144.39 transciever. and the grounds too. Here is where it > get's *interesting*. Since the TNC is listening to the repeater audio for a > packet, it can't hear 144.39. Since it can't hear 144.39, it could tx at > the same time as another packet on 144.39. The XCD pin needs to be hooked > to a squelch indicator on your 144.39 radio. It must be high when the > squelch is open (not muted). Kenwood radios are upside down.. they are low > when not muted.... but that is another matter. On many new radios, you will > find a squelch indicator in the mic jack, and on the older (mid 1980's) you > will find a LED around the front panel. All that matters is that you get 0v > when the radio is quiet, and 5 or more volts when the radio is not muted. > > The kpc3+ v8.3 has a MUTE function also.... one of it's pins will pull low > when packet racket is heard on the repeater... this can be tied into your > COR or PL tone enable inputs on your repeater cotroller to mute the packets > on the output of the repeater. > > Method #2 requires a kpc4 (dual port 1200 tnc), a kpc9612 with the > additional 1200 modem, or two TNCs with either stealthdigi or aprsdigi > software. > > Wes - kd4rdb@qsl.net > http://www.qsl.net/kd4rdb > > Where am I? > http://map.aprs.net/kd4rdb-9 > http://map.aprs.net/kd4rdb-10 > > CW - the code that stops up your node. > -----Original Message----- > From: Tom Smith > To: TAPR MIC-E & PIC-E Special Interest Group > Date: Thursday, May 06, 1999 12:48 AM > Subject: [mic-e] converting an existing repeater to receive MIC-E APRS > transmissions > > >Where can I find information about the procedures and the hardware it will > >take to convert an existing 2M repeater to receive MIC-E APRS > >transmissions? I would like to talk the local repeater into APRS support > >but need more info. Thanks, Tom KD6SOJ > > > >--- > >You are currently subscribed to mic-e as: KD4RDB@bellsouth.net > >To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org > > > > > > --- > You are currently subscribed to mic-e as: SEMCOR@TELEBYTE.COM > To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Fri May 7 16:01:25 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id QAA22727 for ; Fri, 7 May 1999 16:01:24 -0500 (CDT) Message-ID: From: "Wes Johnston" To: "TAPR MIC-E & PIC-E Special Interest Group" Subject: [mic-e] Re: converting an existing repeater to receive MIC-E APRS transmissions Date: Fri, 7 May 1999 17:02:01 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: <005101be98cc$e42f2d80$0300a8c0@bbyfce> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk GREAT SOLUTION!! I'd thought about back to back KISS tncs.. but there is no way to ID them... you have a really good solution... except for one thing that just came to mind as I wrote this... x1j 's beacon texts are not able to be plotted on winaprs maps.... winaprs won't decode them due to xtra characters that x1j puts in them. Wes - kd4rdb@qsl.net http://www.qsl.net/kd4rdb Where am I? http://map.aprs.net/kd4rdb-9 http://map.aprs.net/kd4rdb-10 CW - the code that stops up your node. -----Original Message----- From: Alan Crosswell To: TAPR MIC-E & PIC-E Special Interest Group Date: Friday, May 07, 1999 10:14 AM Subject: [mic-e] Re: converting an existing repeater to receive MIC-E APRS transmissions >>additional 1200 modem, or two TNCs with either stealthdigi or aprsdigi >>software. > >Or my setup: Two TNCs wired back to back with a null-terminal cable. >The TNC lisenting to the repeater is running a KISS EPROM. The other >TNC is running TheNet X1J4 with L2 digipeating enabled and the host >interface running in KISS mode. All packets received by the KISS TNC are >retransmitted by the X1J4 TNC and, the X1J4 performs basic digipeating >functions. It supports multiple aliases by husing the alias, hostalias, etc. > >73 de Alan N2YGK >PS: And we already had cavities on the repeater input/output and added a >cavity on the 144.39 digipeater. This is at a high-RF site (County >radio tower with several commercial paging and broadcast tenants in >addition to public safety agencies). > >--- >You are currently subscribed to mic-e as: KD4RDB@bellsouth.net >To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org > > --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Fri May 7 16:09:20 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id QAA23169 for ; Fri, 7 May 1999 16:09:13 -0500 (CDT) Message-ID: From: "Wes Johnston" To: "TAPR MIC-E & PIC-E Special Interest Group" Subject: [mic-e] Re: converting an existing repeater to receive MIC-E APRS transmissions Date: Fri, 7 May 1999 17:09:30 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: <005601be98cd$f118bb00$0300a8c0@bbyfce> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk you put your TNC into KISS mode, and hook it up to an old PC running APRSDIGI. You can setup access to just the two 1200 baud ports with the PORTA command in it's ini file.... www.qsl.net/kd4rdb/aprsdigi.htm .... download version 11, and let me know if you have any problems. Wes - kd4rdb@qsl.net http://www.qsl.net/kd4rdb Where am I? http://map.aprs.net/kd4rdb-9 http://map.aprs.net/kd4rdb-10 CW - the code that stops up your node. -----Original Message----- From: George Carr To: TAPR MIC-E & PIC-E Special Interest Group Cc: Bill Hurd Date: Friday, May 07, 1999 10:15 AM Subject: [mic-e] Re: converting an existing repeater to receive MIC-E APRS transmissions >Wes, > >We have a Mic E digipeater we are trying to get to work which includes a >KPC-9612 Plus 1200/9600/1200 and a UHF receiving Mic E data bursts from our >local mountain top repeater with an Alinco VHF packet transmitter sending out to >144.390MHz APRS. Our problem is that we don't think our software is setup >correctly. Can you tell us more about Method #2 and the APRSdigi software you >spoke of? > >Thanks in advance for any help. > >George, N7GME > >Wes Johnston wrote: > >> Depends on what you want to do.... there are two ways to go.... >> >> 1. A simple digipeater that will only get mic-e packets from your repeater's >> audio to the aprs 2m frequency. >> >> 2. A full service digipeater at the same site as the repeater that will >> *also* get mic-e packets over to 2m. >> >> Method 1 requires only a kpc3 or kpc3plus. You hook up the RX audio (kpc >> pin 5) to the repeater's audio. hook up the PTT , TX audio and XCD pins (3, >> 1, and 2) to the 144.39 transciever. and the grounds too. Here is where it >> get's *interesting*. Since the TNC is listening to the repeater audio for a >> packet, it can't hear 144.39. Since it can't hear 144.39, it could tx at >> the same time as another packet on 144.39. The XCD pin needs to be hooked >> to a squelch indicator on your 144.39 radio. It must be high when the >> squelch is open (not muted). Kenwood radios are upside down.. they are low >> when not muted.... but that is another matter. On many new radios, you will >> find a squelch indicator in the mic jack, and on the older (mid 1980's) you >> will find a LED around the front panel. All that matters is that you get 0v >> when the radio is quiet, and 5 or more volts when the radio is not muted. >> >> The kpc3+ v8.3 has a MUTE function also.... one of it's pins will pull low >> when packet racket is heard on the repeater... this can be tied into your >> COR or PL tone enable inputs on your repeater cotroller to mute the packets >> on the output of the repeater. >> >> Method #2 requires a kpc4 (dual port 1200 tnc), a kpc9612 with the >> additional 1200 modem, or two TNCs with either stealthdigi or aprsdigi >> software. >> >> Wes - kd4rdb@qsl.net >> http://www.qsl.net/kd4rdb >> >> Where am I? >> http://map.aprs.net/kd4rdb-9 >> http://map.aprs.net/kd4rdb-10 >> >> CW - the code that stops up your node. >> -----Original Message----- >> From: Tom Smith >> To: TAPR MIC-E & PIC-E Special Interest Group >> Date: Thursday, May 06, 1999 12:48 AM >> Subject: [mic-e] converting an existing repeater to receive MIC-E APRS >> transmissions >> >> >Where can I find information about the procedures and the hardware it will >> >take to convert an existing 2M repeater to receive MIC-E APRS >> >transmissions? I would like to talk the local repeater into APRS support >> >but need more info. Thanks, Tom KD6SOJ >> > >> >--- >> >You are currently subscribed to mic-e as: KD4RDB@bellsouth.net >> >To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org >> > >> > >> >> --- >> You are currently subscribed to mic-e as: SEMCOR@TELEBYTE.COM >> To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org > > > > >--- >You are currently subscribed to mic-e as: KD4RDB@bellsouth.net >To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org > > --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Fri May 7 16:57:29 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id QAA24379 for ; Fri, 7 May 1999 16:57:28 -0500 (CDT) Sender: bounce-mic-e-2619@lists.tapr.org Date: Fri, 7 May 99 17:57:16 EDT From: Alan Crosswell To: "TAPR MIC-E & PIC-E Special Interest Group" Subject: [mic-e] Re: converting an existing repeater to receive MIC-E APRS transmissions In-Reply-To: Your message of Fri, 7 May 1999 17:02:01 -0400 Message-ID: List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: Precedence: bulk >that just came to mind as I wrote this... x1j 's beacon texts are not able >to be plotted on winaprs maps.... winaprs won't decode them due to xtra You may have occassionally seen me refer to broken APRS implementations in my rants on this list. This is what I mean by a broken APRS implementation. Protocol.txt clearly allows for a position in a BTEXT to start at other than the first character position. This is there to accomodate TheNet digis that force that junk into the btext. I looked at modifying TheNet source code to not print that junk but I didn't have the right C compiler and didn't feel like spending money on one. I guess I was too lazy to try and just write a binary patch in... And, mostly, it works for aprsdos, and, IDing the digi is only a secondary feature anyway. First and foremost it is a digi. Thenet still lacks all the other nice features of aprsdigi, etc. though. 73 de Alan N2YGK --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Fri May 7 17:48:59 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id RAA25908 for ; Fri, 7 May 1999 17:48:57 -0500 (CDT) Date: Fri, 7 May 99 18:48:49 EDT From: Alan Crosswell To: "TAPR MIC-E & PIC-E Special Interest Group" Subject: [mic-e] ANNOUNCE: Linux APRS Digipeater 2.0 Message-ID: List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk [I've been sitting on this a while waiting for beta-tester feedback.] Announcing N2YGK's Linux aprsdigi-2.0. April 2, 1999 Several hams have been using my original Linux APRS(tm) digipeater, aprsdigi, for a couple of years now. It was found in the arpsmon.zip package (don't ask) on ftp.tapr.org. Release 2.0 of this advanced APRS digipeater is now available for free under the terms of the GNU Public License (GPL) at http://www.users.cloud9.net/~alan/ham/aprs/. Major features of this release of aprsdigi: - MYCALL substitution. - WIDE, WIDEn-n, TRACE, and TRACEn-n. - As many radio interfaces as you can plug into your Linux machine with flexible gatewaying between them. - Special handling for Mic-Encoder, Kenwood TH-D7, and TheNet X1J4, including SSID-based digipeating. - Suppression of duplicate and looping packets. - Works with Linux 2.2 kernel AX.25 network stack. This means any AX.25 interface supported by the kernel will work, not just a TNC2 clone. Examples include all the BAYCOM interfaces (BAYPAC, PICPAR, PICSER, etc.), soundcards, 8530 SCC cards, etc. This distribution also includes an updated version of aprsmon, but, unless you require support for other than a TNC-2, I recommend using WA4DSY's aprsd instead. 73 de Alan N2YGK --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Fri May 7 18:17:11 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id SAA26812 for ; Fri, 7 May 1999 18:17:08 -0500 (CDT) Message-ID: From: "Wes Johnston" To: "TAPR MIC-E & PIC-E Special Interest Group" Subject: [mic-e] Re: ANNOUNCE: Linux APRS Digipeater 2.0 Date: Fri, 7 May 1999 19:17:30 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: <009e01be98df$d4827140$0300a8c0@bbyfce> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk ut ohhhh..... now we're gunna have confusion.... I didnt know that there was a linux version of aprsdigi when I wrote my DOS version..... hope this doesn't cause too much confusion. The linux version sounds great! Now if I only ran linux..... ;) Wes - kd4rdb@qsl.net http://www.qsl.net/kd4rdb Where am I? http://map.aprs.net/kd4rdb-9 http://map.aprs.net/kd4rdb-10 CW - the code that stops up your node. -----Original Message----- From: Alan Crosswell To: TAPR MIC-E & PIC-E Special Interest Group Date: Friday, May 07, 1999 6:49 PM Subject: [mic-e] ANNOUNCE: Linux APRS Digipeater 2.0 >[I've been sitting on this a while waiting for beta-tester feedback.] > >Announcing N2YGK's Linux aprsdigi-2.0. April 2, 1999 > >Several hams have been using my original Linux APRS(tm) digipeater, >aprsdigi, for a couple of years now. It was found in the arpsmon.zip >package (don't ask) on ftp.tapr.org. Release 2.0 of this advanced >APRS digipeater is now available for free under the terms of the GNU >Public License (GPL) at http://www.users.cloud9.net/~alan/ham/aprs/. > >Major features of this release of aprsdigi: > >- MYCALL substitution. >- WIDE, WIDEn-n, TRACE, and TRACEn-n. >- As many radio interfaces as you can plug into your Linux machine > with flexible gatewaying between them. >- Special handling for Mic-Encoder, Kenwood TH-D7, and TheNet X1J4, including > SSID-based digipeating. >- Suppression of duplicate and looping packets. >- Works with Linux 2.2 kernel AX.25 network stack. This means any AX.25 > interface supported by the kernel will work, not just a TNC2 clone. > Examples include all the BAYCOM interfaces (BAYPAC, PICPAR, PICSER, etc.), > soundcards, 8530 SCC cards, etc. > >This distribution also includes an updated version of aprsmon, but, >unless you require support for other than a TNC-2, I recommend using >WA4DSY's aprsd instead. > >73 de Alan N2YGK > > >--- >You are currently subscribed to mic-e as: KD4RDB@bellsouth.net >To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org > > --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Sat May 8 06:41:43 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id GAA28643 for ; Sat, 8 May 1999 06:41:42 -0500 (CDT) X-Authentication-Warning: cannac.ampr.org: k5di owned process doing -bs Date: Sat, 8 May 1999 05:48:36 -0600 (MDT) From: "Karl F. Larsen" Sender: bounce-mic-e-2619@lists.tapr.org To: "TAPR MIC-E & PIC-E Special Interest Group" cc: mic-e@tapr.org, aprssig@tapr.org Subject: [mic-e] Re: ANNOUNCE: Linux APRS Digipeater 2.0 In-Reply-To: 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 Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: Precedence: bulk Alan, I have no idea what a APRS Digipeater is or what "aprsd" is but it sounds like an "aprs demon". Where do I get maps for your system? Has anyone got a GPS attached to your aprs in Linux? Here in New Mexico Paul WA5IKL has 18 sites he owns for commercial radio. At each of these he has Ham radio repeaters and a box on 144.39 MHz that "does packet". As mobile stations with a radio and GPS and the DOS aprs, any "user" can display these mobile stations moving across the map with aprs at home listening to 144.39. If it sounds like I am ignorant your right. How do I fix this condition? And why did you make a .zip Linux package? ... duck and run. On Fri, 7 May 1999, Alan Crosswell wrote: } [I've been sitting on this a while waiting for beta-tester feedback.] } } Announcing N2YGK's Linux aprsdigi-2.0. April 2, 1999 } } Several hams have been using my original Linux APRS(tm) digipeater, } aprsdigi, for a couple of years now. It was found in the arpsmon.zip } package (don't ask) on ftp.tapr.org. Release 2.0 of this advanced } APRS digipeater is now available for free under the terms of the GNU } Public License (GPL) at http://www.users.cloud9.net/~alan/ham/aprs/. } } Major features of this release of aprsdigi: } } - MYCALL substitution. } - WIDE, WIDEn-n, TRACE, and TRACEn-n. } - As many radio interfaces as you can plug into your Linux machine } with flexible gatewaying between them. } - Special handling for Mic-Encoder, Kenwood TH-D7, and TheNet X1J4, including } SSID-based digipeating. } - Suppression of duplicate and looping packets. } - Works with Linux 2.2 kernel AX.25 network stack. This means any AX.25 } interface supported by the kernel will work, not just a TNC2 clone. } Examples include all the BAYCOM interfaces (BAYPAC, PICPAR, PICSER, etc.), } soundcards, 8530 SCC cards, etc. } } This distribution also includes an updated version of aprsmon, but, } unless you require support for other than a TNC-2, I recommend using } WA4DSY's aprsd instead. } } 73 de Alan N2YGK } } Best wishes - Karl F. Larsen, k5di@totacc.com (505) 524-3303 - --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Tue May 11 22:27:59 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.9) with SMTP id WAA26105 for ; Tue, 11 May 1999 22:27:59 -0500 (CDT) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: Date: Tue, 11 May 1999 21:54:45 -0500 To: "TAPR MIC-E & PIC-E Special Interest Group" From: Greg Jones Subject: [mic-e] TAPR Dayton Activities 1999 List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk TAPR Dayton Activities 1999 for details visit: http://www.tapr.org/tapr/html/Fdayton.html We will be at our normal booth spaces (542 & 543) Come on by and say hi! Friday Morning - TAPR Digital Forum Friday Evening - TAPR PACK*BASH ------------------------------ TAPR Digital Forum on Friday The schedule for the TAPR digital forum is: 10:00 - 10:05am (5 min) Introduction to Forum, John Ackermann, N8UR 10:05 - 10:30am (25min) TAPR Update, Greg Jones, WD5IVD 10:30 - 11:00am (30 min) Linux AX.25 Update, John Ackermann, N8UR 11:00 - 11:30am (30 min) PIC Development Update, Steve Bible, N7HPR and John Hansen, W2FS 11:30 - 12:00noon (30 min) GPS Projects, Steve Bible, N7HPR 12:00noon - 12:30pm (30 min) Compact Flash Card Project, John Koster, W9DDD 12:30 - 1:00pm (30 min) TAPR APRS News, Steve Dimse, K4HG and Stan Horzepa, WA1LOU 1:00pm - 1:45pm (45 min) FHSS Radio Project Update, Tom McDermott, N5EG ------------------------------ Attending the 1999 Dayton Hamvention? Then don't miss out on PACK*BASH! What? An event for the digitally-inclined ham, featuring: * Buffet dinner * "A Little Technology Goes a Long Way" -- Keynote address by Dave Pederson, N7BHC * TAPR special interest group meetings * "Birds of a Feather" gatherings When? Friday evening, May 14, 1999 Doors open at 7:00 pm; dinner served at 7:30 pm Speaker and meetings after dinner Where? NCR "Sugarcamp" Conference Center, 101 W. Schantz Ave. -- South of downtown Dayton, just west of Main St. (Rt 48). Maps available on the TAPR web site (www.tapr.org) or at the TAPR booth. How? Dinner requires advance registration and payment through TAPR. Tickets will be available at the TAPR booth on Friday. The cost is $20.00 per person, tax and tip included. All amateurs are welcome to attend, enjoy the speaker, and particpate in the meetings, although only those purchasing a dinner can eat. Who? PACK*BASH is co-sponsored by TAPR -- Tucson Amateur Packet Radio, the national leader in digital communication -- and the Miami Valley FM Association, Dayton's packet radio club. For more information (including maps), go to http://www.tapr.org/tapr/html/dayton.html, or send email to tapr@tapr.org. ----- Greg Jones, WD5IVD Austin, Texas wd5ivd@tapr.org http://www.tapr.org/~wd5ivd --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Mon May 17 10:29:43 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id KAA08557 for ; Mon, 17 May 1999 10:29:41 -0500 (CDT) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: Date: Mon, 17 May 1999 10:29:10 -0500 To: "TAPR MIC-E & PIC-E Special Interest Group" From: Greg Jones Subject: [mic-e] General Announcement APRS Working Group (APRS-WG) List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk General Announcement regarding the formation of the APRS Working Group (APRS-WG) As a result of the dialog held among the primary authors of APRS, the APRS Working Group (APRS-WG) is being founded to aid with the development and growth of APRS. What follows is information on the APRS-WG and initial plans for the next eight months. As promised in the initial agreement between the authors this announcement covers the substantive outcomes that have occurred in private on-line discussion and at the in-person meeting held on May 1-2, 1999. The APRS-WG would like to thank all those involved and the APRS community as a whole for allowing this process to happen in the manner that it did. The results we fell will benefit the APRS community as a whole. Greg Jones, WD5IVD for the APRS Working Group ================================================== APRS Working Group ------------------ Mission Statement APRS, developed by Bob Bruninga, WB4APR, is an Amateur Radio digital infrastructure for realtime and tactical digital communications. It is designed to provide communications during emergencies, but it is recognized to support routine round-the-clock global communications as well. Its applications include mapping, messaging, telemetry, and tracking. It uses a standard protocol over RF links, supplemented by alternate communication methodologies. The APRS Working Group ---------------------- The APRS Working Group ("Group)" is an unincorporated association whose members undertake to further the use and enhance the value of the APRS protocols by (a) maintaining and publishing a formal APRS Protocol Specification; (b) publishing validation tests and other tools to enable compliance with the Specification; (c) supporting an APRS Certification program; and (d) generally working to improve the capabilities of APRS within the Amateur Radio community. This document describes the organization and operation of the Group. Although the Group may receive support from TAPR or other organizations, it is an independent body and is not affiliated with any organization. The Group will have no budget, collect no dues, and own no assets. Statement of Principles ----------------------- At a meeting near Baltimore, Maryland on May 1-2, 1999, and in email communications in the days following, the Group members agreed to the following principles that will govern their behavior and that of the Group: 1. Bob Bruninga has been the primary developer of the APRS concept. He owns the APRSdos computer program, the APRSdos documentation, and the APRS trademark, and retains the right to license these items to others. 2. All Group members agree that in the spirit of Amateur Radio, the on-air protocols themselves should be open to general Amateur Radio development and not be restricted by copyright. 2. Existing agreements between or among APRS developers are unaffected by this Charter. 3. The Group will formalize the APRS on-air Protocol Specification and publish a definitive APRS protocol document. Present plans are to make the specification in book and diskette form, and possibly to provide it via electronic distribution. 4. A process will be put in place to define how changes to the protocol specification are made, and that process will permit input, review, and comment by the Amateur Radio public. 5. The Group will put a voluntary APRS certification process in place, to be managed by Bob Bruninga with Group oversight. The process will include a publicly available validation suite. Protocol Committee ------------------ The APRS Protocol Specification is the formal definition of the data elements and message formats used to communicate between APRS devices via wireless or wired (e.g., Internet) connections. It does not include user interface or other elements that do not affect the content or format of these interface components. The Protocol Committee, which presently consists of all APRS-WG Members, is responsible for the APRS Protocol Specification. It manages the process for publishing and updating the Specification, and for receiving public comment on proposed changes. The Protocol Committee intends to publish Version 1.0 of the APRS Protocol Specification by the end of October 1999. The first draft of the Specification will be made available to the Amateur Radio community by the end of June 1999, and comments will be accepted as defined below. Committee Operations and Community Input Input from the APRS user community, other APRS developers, and the amateur community at large is a key component of the protocol development process. Once the process has been formally defined it will be announced and published. Certification Committee ----------------------- The Group wants to encourage the development of products that properly implement the APRS protocols. To that end, the Certification Committee, which is initially composed of all Group members, will establish a Certification Program. Certification is wholly voluntary on the part of an APRS product developer, and the Certification Program is available on an equal basis to any developer. The full certification process and schedule will be announced and published shortly after Dayton. Some of the points of certification include: 1. The Committee will develop and approve a Validation Suite, which will be the primary basis for Certification. The Suite will consist of test inputs and a description of how a product complying with the Protocol Specification should react to each of these inputs. The suite will be based on the TAPR TNC-2 packet display format. The Validation Suite will be made available to the public without charge. 2. Bob Bruninga will manage the Certification Program on behalf of the Committee, subject to oversight by the Committee. 3. Subject to compliance with a Certification Agreement that must be signed before Certification is granted, Certified Products will be permitted to display or be advertised in conjunction with an "APRS Certified" trademark and logo. The trademark and logo are owned by Bob Bruninga and are licensed subject to the Certification Agreement. 4. Certified Products must successfully complete the Validation Suite, but applicants must acknowledge that additional testing may be necessary to ensure that a given Product properly implements the Protocol Specification, and agree to reasonably cooperate with such testing. 5. The Certification process is largely self-managed. The applicant must run the validation suite and submit results with the application. The Committee will conduct such testing as it deems necessary to verify the Product's conformance to the Protocol Specification. ------- Full details regarding membership to APRS-WG, meeting and voting process, protocol committee, and the certification process will be made available once the rules have been fully developed. ================================================== --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Mon May 17 10:44:34 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id KAA08957 for ; Mon, 17 May 1999 10:44:33 -0500 (CDT) Message-ID: From: "Dave VanHorn" To: "TAPR MIC-E & PIC-E Special Interest Group" References: Subject: [mic-e] Re: General Announcement APRS Working Group (APRS-WG) Date: Mon, 17 May 1999 10:31:48 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: <00b901bea07a$620e2120$0200a8c0@xemu> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk Congratulations! This looks VERY good. --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Thu May 20 11:48:21 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id LAA26857 for ; Thu, 20 May 1999 11:48:19 -0500 (CDT) Message-ID: Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" From: "Chuck Hodell" To: "TAPR MIC-E & PIC-E Special Interest Group" References: Subject: [mic-e] Help with Mic-E settings Date: Thu, 20 May 1999 12:47:05 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio X-Message-Id: <008201bea2e0$67668aa0$1552c0d8@chuckh> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk I have recently put a Mic-e online in my vehicle and I would appreciate any help available for setting it up correctly. Especially helpful would be settings for the path statements and timing parameters. At present it transmits about every 10 - 15 minutes unless I do it manually. I am guessing that 2-5 minutes is probably standard when you are actually moving. I have the path presently set to relay, wide, wide. I am relatively new to APRS and ceratinly to the Mic-e, so I hope the questions aren't something I should have caught in the literature. Thanks. chuck N8ADN on Kent Island, Maryland --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Thu May 20 20:56:50 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id UAA14280 for ; Thu, 20 May 1999 20:56:46 -0500 (CDT) Message-ID: From: "Wes Johnston" To: "TAPR MIC-E & PIC-E Special Interest Group" Subject: [mic-e] Re: Help with Mic-E settings Date: Thu, 20 May 1999 21:55:50 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: <001c01bea32d$143620a0$0300a8c0@bbyfce> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk I set my "base" unit of time to one minute... you can spin the knob to 16 minutes if you wish to reduce the rate. When parked I spin the knob to 16 minutes, one minute when traveling. Wes - kd4rdb@qsl.net http://www.qsl.net/kd4rdb Where am I? http://map.aprs.net/kd4rdb-9 http://map.aprs.net/kd4rdb-10 Hookt on fonix werkt fer me! -----Original Message----- From: Chuck Hodell To: TAPR MIC-E & PIC-E Special Interest Group Date: Thursday, May 20, 1999 12:48 PM Subject: [mic-e] Help with Mic-E settings >I have recently put a Mic-e online in my vehicle and I would appreciate any >help available for setting it up correctly. Especially helpful would be >settings for the path statements and timing parameters. At present it >transmits about every 10 - 15 minutes unless I do it manually. I am >guessing that 2-5 minutes is probably standard when you are actually moving. >I have the path presently set to relay, wide, wide. > >I am relatively new to APRS and ceratinly to the Mic-e, so I hope the >questions aren't something I should have caught in the literature. > >Thanks. > >chuck N8ADN on Kent Island, Maryland > > >--- >You are currently subscribed to mic-e as: KD4RDB@bellsouth.net >To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org > > --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Wed May 26 02:25:08 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id CAA28116 for ; Wed, 26 May 1999 02:25:07 -0500 (CDT) Message-ID: From: "kd5abq" To: "TAPR MIC-E & PIC-E Special Interest Group" Subject: [mic-e] TripMate Date: Wed, 26 May 1999 02:22:07 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01BEA71E.8D570360" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: <000801bea748$7728d080$5273bdcc@vvm.com> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BEA71E.8D570360 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable OK our club recently purchased 4 Mic-E's. One of these is hooked up to a = Delorme Tripmate GPS. This GPS has already been modified for external = power via cigarette lighter with the cable set purchased from Delorme. = It has also been modified to be always on and receiving without having = to be interfaced to a computer.=20 Now the problem is, it seems that the MIC-E is not receiving this data. = I can hook it up to my laptop and street atlas 5.0 and instant fix. I = unplug it and plug it into the MIC-E and the Mic-e sends:=20 KD5ABQ-5>PP0PPP-9:'vX=1Cl =1C_/ Any ideas would be greatly appreciated. If it is not to much trouble = please send response to kd5abq@vvm.com Gary ------=_NextPart_000_0005_01BEA71E.8D570360 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
OK our club recently purchased 4 Mic-E's. One of = these is=20 hooked up to a Delorme Tripmate GPS. This GPS has already been modified = for=20 external power via cigarette lighter with the cable set purchased from = Delorme.=20 It has also been modified to be always on and receiving without having = to be=20 interfaced to a computer.
 
Now the problem is, it seems that the MIC-E is not = receiving=20 this data. I can hook it up to my laptop and street atlas 5.0 and = instant fix. I=20 unplug it and plug it into the MIC-E and the Mic-e sends:
 
KD5ABQ-5>PP0PPP-9:'vX=1Cl =1C_/
 
Any ideas would be greatly appreciated. If it is not = to much=20 trouble please send response to kd5abq@vvm.com
 
Gary
------=_NextPart_000_0005_01BEA71E.8D570360-- --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Wed May 26 06:37:44 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id GAA12413 for ; Wed, 26 May 1999 06:37:41 -0500 (CDT) Message-ID: From: "Wes Johnston" To: "TAPR MIC-E & PIC-E Special Interest Group" Subject: [mic-e] Re: TripMate Date: Wed, 26 May 1999 07:37:22 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A3_01BEA74A.97707260" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: <00a801bea76c$1f74afc0$0300a8c0@bbyfce> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_00A3_01BEA74A.97707260 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have only had a problem with my mic-e accepting data from an older = GPS10.... and I suspect a voltage problem. I don't think this is your = problem, because my tripmate works fine with my mic-e. In your case, = have you checked to be sure that the MIC-e "adaptor" cable has pins 2 = and 3 wired correctly? Try switcheing them around. Wes - kd4rdb@qsl.net http://www.qsl.net/kd4rdb Where am I? http://map.aprs.net/kd4rdb-9 http://map.aprs.net/kd4rdb-10 Hookt on fonix werkt fer me!=20 -----Original Message----- From: kd5abq To: TAPR MIC-E & PIC-E Special Interest Group Date: Wednesday, May 26, 1999 3:12 AM Subject: [mic-e] TripMate =20 =20 OK our club recently purchased 4 Mic-E's. One of these is hooked up = to a Delorme Tripmate GPS. This GPS has already been modified for = external power via cigarette lighter with the cable set purchased from = Delorme. It has also been modified to be always on and receiving without = having to be interfaced to a computer.=20 =20 Now the problem is, it seems that the MIC-E is not receiving this = data. I can hook it up to my laptop and street atlas 5.0 and instant = fix. I unplug it and plug it into the MIC-E and the Mic-e sends:=20 =20 KD5ABQ-5>PP0PPP-9:'vX=1Cl =1C_/ =20 =20 Any ideas would be greatly appreciated. If it is not to much trouble = please send response to kd5abq@vvm.com =20 Gary ------=_NextPart_000_00A3_01BEA74A.97707260 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have only had a problem with my = mic-e=20 accepting data from an older GPS10.... and I suspect a voltage = problem.  I=20 don't think this is your problem, because my tripmate works fine with my = mic-e.  In your case, have you checked to be sure that the MIC-e=20 "adaptor" cable has pins 2 and 3 wired correctly?  Try = switcheing=20 them around.
 
 
Wes -  kd4rdb@qsl.net
  http://www.qsl.net/kd4rdb
 
Where am I?
   http://map.aprs.net/kd4rdb-9  =20 http://map.aprs.net/kd4rdb-10<= /FONT>
 
Hookt on fonix werkt fer me! =
-----Original = Message-----
From:=20 kd5abq <kd5abq@vvm.com>
To: = TAPR MIC-E=20 & PIC-E Special Interest Group <mic-e@lists.tapr.org>
D= ate:=20 Wednesday, May 26, 1999 3:12 AM
Subject: [mic-e]=20 TripMate

OK our club recently purchased 4 Mic-E's. One of = these is=20 hooked up to a Delorme Tripmate GPS. This GPS has already been = modified for=20 external power via cigarette lighter with the cable set purchased = from=20 Delorme. It has also been modified to be always on and receiving = without=20 having to be interfaced to a computer.
 
Now the problem is, it seems that the MIC-E is = not=20 receiving this data. I can hook it up to my laptop and street atlas = 5.0 and=20 instant fix. I unplug it and plug it into the MIC-E and the Mic-e = sends:=20
 
KD5ABQ-5>PP0PPP-9:'vX=1Cl = =1C_/
 
Any ideas would be greatly appreciated. If it is = not to=20 much trouble please send response to kd5abq@vvm.com
 
Gary
------=_NextPart_000_00A3_01BEA74A.97707260-- --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Wed May 26 10:10:16 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id KAA17645 for ; Wed, 26 May 1999 10:10:16 -0500 (CDT) Content-return: allowed Date: Wed, 26 May 1999 08:13:10 -0700 From: "Borcher, David (NG-EX)" Subject: [mic-e] RE: TripMate To: "TAPR MIC-E & PIC-E Special Interest Group" Message-id: MIME-version: 1.0 Content-type: text/plain; charset="iso-8859-1" List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk ...Now the problem is, it seems that the MIC-E is not receiving this data. - - - - - I believe that the TripMate does not send ordinary NMEA 0183 data, but uses a proprietary DeLorme format. It may not be compatible with the MIC-E. This was discussed about a week ago on the APRS SIG. Dave K7NG --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Wed May 26 10:31:43 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id KAA18209 for ; Wed, 26 May 1999 10:31:41 -0500 (CDT) Message-Id: X-Sender: hansen@oak.ait.fredonia.edu Date: Wed, 26 May 1999 11:37:14 -0400 To: "TAPR MIC-E & PIC-E Special Interest Group" From: John Hansen Subject: [mic-e] RE: TripMate In-Reply-To: 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 Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: <4.1.19990526113627.01422cd0@oak.ait.fredonia.edu> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk At 08:13 AM 5/26/99 -0700, you wrote: >...Now the problem is, it seems that the MIC-E is not receiving this data. > >- - - - - >I believe that the TripMate does not send ordinary NMEA 0183 data, but >uses a proprietary DeLorme format. It may not be compatible with the MIC-E. > >This was discussed about a week ago on the APRS SIG. > This is true of the new Earthmate, but not the Tripmate. The Tripmate does NEMA. I have interfaced it successfully with a PIC-E, though I've not tried it on a MIC-E. John, W2FS --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Wed May 26 10:38:15 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id KAA18327 for ; Wed, 26 May 1999 10:38:07 -0500 (CDT) Content-return: allowed Date: Wed, 26 May 1999 08:41:35 -0700 From: "Borcher, David (NG-EX)" Subject: [mic-e] RE: TripMate & NMEA To: "TAPR MIC-E & PIC-E Special Interest Group" Message-id: MIME-version: 1.0 Content-type: text/plain; charset="iso-8859-1" List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk Isn't there some command you have to send to the unit to change from proprietary to NMEA? Is the data output setting non-volatile? Thanks for the correction. Dave K7NG --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Wed May 26 10:44:42 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id KAA18697 for ; Wed, 26 May 1999 10:44:38 -0500 (CDT) Message-Id: Subject: [mic-e] RE: TripMate & NMEA Date: Wed, 26 May 1999 11:43:41 -0400 From: Steve Dimse K4HG To: "TAPR MIC-E & PIC-E Special Interest Group" 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 Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: <199905261544.KAA18691@tapr.org> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk On 5/26/99 11:41 AM Borcher, David (NG-EX) (DBorcher@GI.com) wrote: >Isn't there some command you have to send to the unit to change from >proprietary to NMEA? Is the data output setting non-volatile? > >Thanks for the correction. > Is this the tripmate, or the Earthmate. The Tripmate puts out NMEA, while the Earthmate puts out Rockwell, and is incompatible with the D7. No one has found any command to switch the Earthmate into NMEA, the usual Rockwell command does not work... Steve K4HG --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Wed May 26 12:36:03 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id MAA22089 for ; Wed, 26 May 1999 12:36:00 -0500 (CDT) Message-Id: From: "Zhahai Stewart" Organization: Highly Interactive Systems To: "TAPR MIC-E & PIC-E Special Interest Group" Date: Wed, 26 May 1999 11:36:16 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: [mic-e] RE: TripMate & NMEA Priority: normal In-reply-to: List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: <199905261735.LAA17074@chevalier.rmi.net> Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk > Isn't there some command you have to send to the unit to change from > proprietary to NMEA? Is the data output setting non-volatile? The Tripmate defaults to NMEA but can be switched back and forth between Rockwell binary format and NMEA (each protocol contains a command to switch to the other). The setting (NMEA or Rockwell binary) seems to be volatile; the Tripmate always powers up in NMEA mode. The newer Earthmate is always in Rockwell Binary mode, and cannot be changed to NMEA mode; the Rockwell switch-to-NMEA command doesn't work. (A few of the normal Rockwell binary packet formats are also unavailable). Delorme claims this is because firmware enhancements more ROM space in the Rockwell chip set, so the internal binary to NMEA translation routines were among the things sacrificed. Some people believe this, some think it was an excuse. The Earthmate DOES perform somewhat better, however, so maybe they really did substantially improve the GPS firmware, and this used up more ROM space. Both have a Delorme proprietary startup thing, where they initially output a string (ASTRAL for the tripmate, EARTHA for the earthmate) repeatedly, and do not become functional until they receive the same string. This can be done simply by looping the output back to the input, or can be done in software. Delorme software (like Street Atlas) does this. You might try tapping into the communications line (RS-232) between the Mic-E and the Tripmate, and passivly watching what is sent each way (by changing which line is tapped, TXD or RXD) on a computer running a simple terminal program. Sounds hard, but it just takes a ground and a data jumper and some DE-9 (or DB-25) connectors. That way you can confirm that the Tripmate sent and received "ASTRAL" and then began to deliver NMEA data - or not. The Windows terminal program will work. Zhahai @ Zhahai Stewart zhahai@hisys.com @ A Meme Gardener http://rainbow.rmi.net/~hisys/zhahai.html @ Standard Disclaimer YMMV - Your Maya May Vary --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Wed May 26 13:57:33 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id NAA24345 for ; Wed, 26 May 1999 13:57:28 -0500 (CDT) Sender: bounce-mic-e-2619@lists.tapr.org Date: Wed, 26 May 99 14:57:12 EDT From: Alan Crosswell To: "TAPR MIC-E & PIC-E Special Interest Group" Cc: "TAPR MIC-E & PIC-E Special Interest Group" Subject: [mic-e] RE: TripMate In-Reply-To: Your message of Wed, 26 May 1999 11:37:14 -0400 Message-ID: List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: Precedence: bulk I've used the tripmate with Mic-E and TH-D7. Mic-E notes here (or read your back issues of PSR): http://www.weca.org/wecagram/9707/wecagram.html#APRS Almost 2 years ago. 73 de Alan N2YGK PS: For TH-D7 use: make a DB9-to-mini cable and short pins 4&9 together. Then, inside tripmate case, short right two pins of the battery connector together. This will put +V out on pin 9 so it can get shorted back in on pine 4 to assert DTR:-) --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Wed May 26 15:10:04 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id PAA26331 for ; Wed, 26 May 1999 15:09:56 -0500 (CDT) Mime-Version: 1.0 Message-Id: Date: Wed, 26 May 1999 15:10:12 -0500 To: "TAPR MIC-E & PIC-E Special Interest Group" From: Robert Winingham Subject: [mic-e] RE: TripMate xmit/rec line 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 Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk The wire with the wiggle that makes your voltmeter jiggle is the GPS out xmit line. 73 ----- kc5ejk@onramp.net or kc5ejk@amsat.org ----- --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org From bounce-mic-e-2619@lists.tapr.org Mon May 31 13:15:12 1999 Received: from lists.tapr.org (lists.tapr.org [204.17.217.24]) by tapr.org (8.9.3/8.9.3/1.10) with SMTP id NAA09026 for ; Mon, 31 May 1999 13:15:08 -0500 (CDT) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: Date: Mon, 31 May 1999 13:14:11 -0500 To: "TAPR MIC-E & PIC-E Special Interest Group" From: Greg Jones Subject: [mic-e] 1999 TAPR Digital Forum @ HamVention List-Unsubscribe: List-Software: Lyris Server version 3.0 List-Subscribe: List-Owner: X-List-Host: Tucson Amateur Packet Radio Reply-To: "TAPR MIC-E & PIC-E Special Interest Group" X-Message-Id: Sender: bounce-mic-e-2619@lists.tapr.org Precedence: bulk The audio from the TAPR Digital Forum held during the 1999 Dayton Hamvention is now available for listening. If you couldn't make the forum this year, you can catch up on all the talks. http://www.tapr.org/tapr/html/Fdayton99.html Welcome to the TAPR Digital Forum John Ackermann, AG9V, Forum Moderator TAPR Kit/Project/Organizational Update Greg Jones, WD5IVD (www) Linux AX.25 John Ackermann, N8UR PIC-E Developments Steve Bible, N7HPR (www) and John Hanson, W2FS GPS Projects Steve Bible, N7HPR (www) Compact Flash Adapter John Koster, W9DDD APRS Update Steve Dimse, K4HG and Stan Horzepa, WA1LOU TAPR 900Mhz FHSS Radio Project Tom McDermott, N5EG in addition Dave Pedersen, N7BHC, talk on "A Little Technology Goes a Long Way" during the TAPR PacketBASH on Friday is available. Cheers - Greg Jones, WD5IVD ---------------------------------------------------------------------------- Tucson Amateur Packet Radio 8987-309 E Tanque Verde Rd #337 * Tucson, Az * 85749-9399 ---------------------------------------------------------------------------- e-mail: tapr@tapr.org web: ftp: ftp.tapr.org phone: 940-383-0000 fax: 940-565-2544 ---------------------------------------------------------------------------- --- You are currently subscribed to mic-e as: lyris.mic-e@tapr.org To unsubscribe send a blank email to leave-mic-e-2619I@lists.tapr.org