From kd4rdb@usa.net Tue Oct 06 22:26:51 1998 Received: from eagnet.com (eagnet.com [199.76.206.51]) by tapr.org (8.8.5/8.8.5) with SMTP id WAA29472 for ; Tue, 6 Oct 1998 22:26:50 -0500 (CDT) Received: from wes (unverified [199.76.206.179]) by eagnet.com (EMWAC SMTPRS 0.83) with SMTP id ; Tue, 06 Oct 1998 23:23:08 -0400 Message-Id: <3.0.32.19981006232048.0072ad04@butler> X-Sender: kd4rdb#mail.eagnet.com@butler X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 06 Oct 1998 23:20:50 -0400 To: mic-e@tapr.org From: Wes Johnston Subject: proper care and feeding of the mic-e Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Now that I'm kinda settled into my new home, I have more and more time in the evening to tinker. I need to know about powering the mic-e. How serious is the note about 7.2v in the docs? My radio can supply 8v at the mic plug, but I do not want to exceed the specs and blow my MIC-E up. Also, how much current can be drawn from the typical mic plug? Certainly a mic-e and a 150mA for the GPS is LOADS more than the DTMF encoder in my stock mic. Wes Email: mailto:kd4rdb@eagnet.com AlphaPager: mailto:kd4rdb@eagnet.com - subject line: PAGER APRS: http://www.qsl.net/kd4rdb/aprs.htm Santa's elves are just a bunch of subordinate Clauses. From n2ygk@weca.org Tue Oct 06 22:40:57 1998 Received: from watsol.cc.columbia.edu (cu41854@watsol.cc.columbia.edu [128.59.39.139]) by tapr.org (8.8.5/8.8.5) with ESMTP id WAA29749 for ; Tue, 6 Oct 1998 22:40:55 -0500 (CDT) Received: (from alan@localhost) by watsol.cc.columbia.edu (8.8.5/8.8.5) id XAA26965 for mic-e@tapr.org; Tue, 6 Oct 1998 23:40:54 -0400 (EDT) Sender: Alan Crosswell Date: Tue, 6 Oct 98 23:40:54 EDT From: Alan Crosswell To: mic-e@tapr.org Subject: Re: [MIC-E:1722] proper care and feeding of the mic-e In-Reply-To: Your message of Tue, 6 Oct 1998 22:28:04 -0500 (CDT) Message-ID: > Now that I'm kinda settled into my new home, I have more and more time in > the evening to tinker. I need to know about powering the mic-e. How > serious is the note about 7.2v in the docs? My radio can supply 8v at the > mic plug, but I do not want to exceed the specs and blow my MIC-E up. > Also, how much current can be drawn from the typical mic plug? Certainly a > mic-e and a 150mA for the GPS is LOADS more than the DTMF encoder in my > stock mic. > Wes > Email: mailto:kd4rdb@eagnet.com > AlphaPager: mailto:kd4rdb@eagnet.com - subject line: PAGER > APRS: http://www.qsl.net/kd4rdb/aprs.htm > > Santa's elves are just a bunch of subordinate Clauses. > If your stock Mic is on a kenwood like my TM-733 (8V sounds familiar) just be forewarned that you will "get" to do some surface mount work to replace the fuse if you short that +8 pin like I did:-) The worst part was losing all the freqs I had programmed in! I don't think you want to mess around with drawing that much current from the mic plug. The limit should be in the specs for your rig -- don't forget that the mic is still there and still drawing it's usual load. 73 de Alan N2YGK PS: I don't remember the exact details (my docs were for the beta unit) but I think 7.2 was the minimum voltage if you are using the unit's 7805 which regulates it at +5. Anyway, I powered mine external to the rig -- let's the GPS operate even if the rig is turned off.... From larry@soma.net Tue Oct 06 23:12:33 1998 Received: from soma.net (ns.soma.net [157.22.222.11]) by tapr.org (8.8.5/8.8.5) with ESMTP id XAA01161 for ; Tue, 6 Oct 1998 23:12:31 -0500 (CDT) Received: from [181.100.100.101] (1Cust116.tnt2.lax1.da.uu.net [208.251.141.116]) by soma.net (8.8.6/8.9.0) with ESMTP id VAA28184 for ; Tue, 6 Oct 1998 21:12:28 -0700 (PDT) X-Sender: larry@soma.net (Unverified) Message-Id: In-Reply-To: <8825668E.0050B8A5.00@csc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 6 Oct 1998 21:11:56 -0700 To: mic-e@tapr.org From: Larry Mollica Subject: Re: [MIC-E:1721] MIC-E Telemetry Circuits rdrumhel@csc.com writes: >Greetings; > >Does anyone out there have come circuits that can be used as analog >input to the mic-e? I understand that there are three input ports >available >for use. I would like to put my mic-e to some use, since I do not know of >any repeaters in the San Diego area that have mic-e capabilities. Bear in mind the mic-e can be used as a stand-alone tracker on the standard APRS channels, ie 145.79. That's what I use mine for. >I was wondering if the mic-e can be used as a stand-alone tnc to provide >such functions as temperature, wind speed, logic on/off for devices. Um, yes, if you want to SEND some telemetry like that. It has no receive capability (other than audio-detect so it doesn't xmit when the channel is in use). It is not a TNC. Also note, while you can hook up things to encode temperature and other weather data on the analog inputs, this doesn't mean it will show up on APRS maps as a weather station. I see in a reade file that comes with DOS APRS, "TELEMTRY.TXT", that APRSDOS can be setup to decode received the mic-e data in to "real-world values" such as temperature. But as far as I know the Mac/WinAPRS version does not have the capablity to display mic-e telemetry, other than the message knob/alarm setting (yet). The telemetry section of the mic-e manual has a temperature circuit, BTW. Sorry I don't have any experience with actual telemetry on it, which is probably what you really wanted to hear about... likewise if I'm telling you stuff you already know! ---] Larry Mollica WA6FSJ ---] Suspect's last whereabouts: http://map.aprs.net/wa6fsj-12 From kc5ejk@onramp.net Wed Oct 07 00:57:57 1998 Received: from mailhost.onramp.net (mailhost.onramp.net [199.1.11.3]) by tapr.org (8.8.5/8.8.5) with ESMTP id AAA12687 for ; Wed, 7 Oct 1998 00:57:56 -0500 (CDT) Received: from [206.50.200.250] (ppp13-58.dllstx.onramp.net [206.50.200.250]) by mailhost.onramp.net (8.8.7/8.8.7) with ESMTP id AAA08094 for ; Wed, 7 Oct 1998 00:57:52 -0500 (CDT) X-Sender: kc5ejk@mailhost.onramp.net Message-Id: In-Reply-To: <8825668E.0050B8A5.00@csc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 7 Oct 1998 00:59:55 -0600 To: mic-e@tapr.org From: Robert Winingham Subject: Re: [MIC-E:1721] MIC-E Telemetry Circuits >Greetings; > >Does anyone out there have come circuits that can be used as analog >input to the mic-e? I understand that there are three input ports >available >for use. I would like to put my mic-e to some use, since I do not know of >any repeaters in the San Diego area that have mic-e capabilities. > >I was wondering if the mic-e can be used as a stand-alone tnc to provide >such functions as temperature, wind speed, logic on/off for devices. > >Any help with info, circuits, and experience would be greatly appreciated. > >Ron Drumheller, K3NXF >Ramona, CA Don't forget the TAPR e-mail archives can be searched by subject and content . I remember several postings on this subject. The KPC-3 Plus TNC has binary input ports and a pulsed output port. Bob answered part of this is a message last week. 73 Bob - Dallas,TX --- kc5ejk@onramp.net or kc5ejk@amsat.org --- From bruninga@nadn.navy.mil Wed Oct 07 08:22:16 1998 Received: from arctic.nadn.navy.mil (arctic.nadn.navy.mil [131.121.8.1]) by tapr.org (8.8.5/8.8.5) with ESMTP id IAA00432 for ; Wed, 7 Oct 1998 08:22:15 -0500 (CDT) Received: from localhost (bruninga@localhost) by arctic.nadn.navy.mil (8.8.5/8.8.5) with ESMTP id JAA03472 for ; Wed, 7 Oct 1998 09:22:51 -0400 (EDT) X-Authentication-Warning: arctic.nadn.navy.mil: bruninga owned process doing -bs Date: Wed, 7 Oct 1998 09:22:50 -0400 (EDT) From: Bob Bruninga X-Sender: bruninga@arctic To: mic-e@tapr.org Subject: Re: [MIC-E:1724] Re: MIC-E Telemetry Circuits In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 6 Oct 1998, Larry Mollica wrote: > >Does anyone out there have come circuits that can be used as analog > >input to the mic-e? I understand that there are three input ports Yes, 3 analog inputs in Mic-E mode or 5 in MIM mode plus 8 on/off switches. For a schematic for a temperature sensor, run MIC-TEMP.BAS. It will show you how to hook up a thermister as one of the sensors. Also, the Mic-E has a built in voltage divider to read the battery voltage. Just enable jumper JP2 in the pin 1 position. APRSdos will display these values on its TELEMETRY page. (alt-T) de WB4APR, bob From bruninga@nadn.navy.mil Wed Oct 14 12:05:34 1998 Received: from arctic.nadn.navy.mil (arctic.nadn.navy.mil [131.121.8.1]) by tapr.org (8.8.5/8.8.5) with ESMTP id MAA17241 for ; Wed, 14 Oct 1998 12:05:24 -0500 (CDT) Received: from localhost (bruninga@localhost) by arctic.nadn.navy.mil (8.8.5/8.8.5) with ESMTP id NAA07557 for ; Wed, 14 Oct 1998 13:05:58 -0400 (EDT) X-Authentication-Warning: arctic.nadn.navy.mil: bruninga owned process doing -bs Date: Wed, 14 Oct 1998 13:05:58 -0400 (EDT) From: Bob Bruninga X-Sender: bruninga@arctic To: mic-e@tapr.org Subject: Mic104d.exe In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII ARGH! My mic-e beta just lost its brains and I cannot find a copy of Mic104d.exe anywhere. My main PC of that era died months ago. ANyone have a copy of Mic104d.exe that they can post so I can get back on line? bob From kkelly@radix.net Wed Oct 14 12:44:22 1998 Received: from news1.radix.net (news1.radix.net [209.48.224.41]) by tapr.org (8.8.5/8.8.5) with ESMTP id MAA17891 for ; Wed, 14 Oct 1998 12:44:22 -0500 (CDT) Received: from saltmine.radix.net (saltmine.radix.net [209.48.224.40]) by news1.radix.net (8.8.7/8.8.7) with ESMTP id NAA18151 for ; Wed, 14 Oct 1998 13:43:30 -0400 (EDT) Received: from radix.net (dialin5.annex5.radix.net [209.48.227.10]) by saltmine.radix.net (8.8.7/8.8.7) with ESMTP id NAA11674 for ; Wed, 14 Oct 1998 13:43:38 -0400 (EDT) Message-ID: <3624E47F.84F492F4@radix.net> Date: Wed, 14 Oct 1998 13:50:55 -0400 From: Kevin Kelly X-Mailer: Mozilla 4.5b2 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: mic-e@tapr.org Subject: Re: [MIC-E:1727] Mic104d.exe References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Bob, I have 104e. Will that help you? Bob Bruninga wrote: > ARGH! > > My mic-e beta just lost its brains and I cannot find a copy of Mic104d.exe > anywhere. My main PC of that era died months ago. ANyone have a copy of > Mic104d.exe that they can post so I can get back on line? > > bob -- 73, Kevin Kelly/N6QAB http://www.qsl.net/n6qab/index.htm From kd4zdd@amsat.org Wed Oct 14 12:54:52 1998 Received: from clientprofiles.com ([12.8.193.2]) by tapr.org (8.8.5/8.8.5) with SMTP id MAA18120 for ; Wed, 14 Oct 1998 12:54:51 -0500 (CDT) Received: from warren by clientprofiles.com with SMTP (MDaemon.v2.7.SP4.R) for ; Wed, 14 Oct 1998 13:54:09 -0400 From: "Warren A. Merkel" Organization: Custom Micro Systems To: mic-e@tapr.org Date: Wed, 14 Oct 1998 13:54:43 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Mic104d.exe Reply-to: kd4zdd@amsat.org Priority: normal In-reply-to: <199810141708.MAA17338@tapr.org> X-mailer: Pegasus Mail for Win32 (v3.01b) X-MDaemon-Deliver-To: mic-e@tapr.org X-Return-Path: austin@pop3.magicnet.net Message-ID: > > > My mic-e beta just lost its brains and I cannot find a copy of Mic104d.exe > anywhere. My main PC of that era died months ago. ANyone have a copy of > Mic104d.exe that they can post so I can get back on line? Have you tried 1.07? See the software lib at TAPR, ftp://ftp.tapr.org/tapr/mic-e/software/pc.zip Warren A. Merkel kd4zdd@amsat.org Orlando, FL From bruninga@nadn.navy.mil Wed Oct 28 11:34:07 1998 Received: from arctic.nadn.navy.mil (arctic.nadn.navy.mil [131.121.8.1]) by tapr.org (8.8.5/8.8.5) with ESMTP id LAA14412; Wed, 28 Oct 1998 11:34:03 -0600 (CST) Received: from localhost (bruninga@localhost) by arctic.nadn.navy.mil (8.8.5/8.8.5) with ESMTP id MAA28494; Wed, 28 Oct 1998 12:35:54 -0500 (EST) X-Authentication-Warning: arctic.nadn.navy.mil: bruninga owned process doing -bs Date: Wed, 28 Oct 1998 12:35:54 -0500 (EST) From: Bob Bruninga X-Sender: bruninga@arctic To: Jeff King cc: aprssig@tapr.org, mic-e@tapr.org Subject: Mic-E Protocol In-Reply-To: <3636B20C.F63AF7B2@aerodata.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 28 Oct 1998, Jeff King wrote: > On another topic, got a e-mail from John Hansen and he was saying the > MIC-E protocol would/is changing *(and you had a hand in it). Any > idea were the new protocol might be and what enhancements might > be in it? There were three additions based on the needs of the Kenwood HT. These are backwards compatible, so all old TAPR Mic-E's continue to work. 1) Provision was made to permit an additional 6 custom messages in addition to the original built-in seven. THey simply are "C0" through "C6". No text. You just agree with your friends or local network what "C0" to "C6" mean beforehand. 2) The first letter of the STATUS text from a Kenwood HT will always be a ">". This allows us to know which Mic-E's are message capable. 3) Provision was made for position ambiguity. This way you will be able to enter a manual posit without having to be precise to the nearest 60 feet. Thus you can enter a position of approximately where you are and know that it will not be missinterpreted on the other end. Example: You arrive in Baltimore from California. You start using your HT to send and receive messages, but you dont have your GPS or are inside all day. You want to enter a posit in Baltimore so it doesnt look like you are in LA. So you enter 3910.__N and 07640.__W. In APRSdos, you will be displayed normally in Baltimore, but if one zooms below the 4 mile range, your ICON becomes a 1 mile circle to show that your position is somewhere near there. If you only entered 391_.__N and 0764_.__W then your ICON will appear normally in Baltimore, but if someone zooms below the 64 mile range, then your ICON becomes a 10 mile circle. Again, clearly showing the viewers that your position is somewhere in that circle. With the world-wide messaging capability of APRS, a message without a posit could be from anywhere on the planet. But sometimes you dont know exactly where you are. So position ambiguity allows you to enter an in-precise position so that others know about where you are... For my Kenwood HT, I will enter a position about half way between work and home with a 10 mile ambiguity. THus people will always see me in Maryland, but I could be anywhere in that circle. On those days when I plug in the GPS, of course, then they will see exactly where I am. This position ambiguity is important to distinguish between positions that are known precisely (to the accuracy of GPS ) and those that are estimates and should not be precisely plotted. I have requested the other authors to also convey position ambiguity whenever digits in the position are the SPACE character instead of digits. So again, all old TAPR Mic-E's will still work as before. THese are just enhancements to optimize the protocol towards the Kenwood HT's vast potential as a world-wide APRS message communicator. de WB4APR, Bob