RE: [tracker2] Prototype rev B changes
- Here's the deal with the pin header - I need about 14 pins for expansion anyway, and it's mostly generic I/O and power/ground, so I'm using the layout of the typical HD44780 LCD header and adding a space for a contrast adjust resistor. The second serial interface is on the header mostly so you can plug in a GPS module there.The I2C port is also on the pin header, so that could be used for expansion of some sort.Scott
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Wes Johnston
Sent: Monday, June 12, 2006 6:45 AM
Subject: Re: [tracker2] Prototype rev B changesMute pin can be allocated in the kpc3 software to two pins.... pin 8 and I think pin 4. I use pin 8. Pin 7 is power. Pin 2 is XCD.I like the idea of a serial port for an LCD.... HOWEVER.. it seems that it would be pretty easy to make a serial lcd controller for a pic that would catch packets going to the GPS on the normal serial port. I find myself wondering (when using a GPS to display data) which station has updated. If a serial LCD would simply display a chronological list of the callsigns of stations heard, that would go a long long way.Wes----- Original Message -----From: scott@...Sent: Sunday, June 11, 2006 6:36 PMSubject: [tracker2] Prototype rev B changes
I'm hoping to finish up the next revision of the through-hole (OT2m) board
soon and get it submitted in the next couple of days. I think I've fixed
all of the silkscreen problems, and I improved the component layout in the
demodulator section to make it more clear what goes where.
Pin 6 on the RJ12 jack is now connected to the configuration jumper input
for convenience. The CTS and RTS handshaking signals on the serial port are
connected to the second serial interface, and could be used either as a
second serial port (with an appropriate cable) or for hardware flow control
(good for the HamHUD.) I couldn't find space for a MAX202 without totally
changing the board layout, so that won't be in this version.
The single-row 10-pin header has been replaced with a dual-row 14-pin
header. I think I might try to lay it out so that it could be used with an
LCD module, and I'll see if I can get the second serial interface on it.
I need to allocate a pin for a mute output - I think that goes to pin 2 of
the radio connector on the KPC-3? Might also need a TTL level squelch/COR
Is there anything I'm forgetting?
Oh, the order has been place for the cases. They'll be done in 4 or 5
weeks. There have been no changes in the board footprint, so the beta OT1m
and OT2m boards will fit. Or they'd better, anyway, with what I paid for
the first batch!
- I kind of lost track with the thread, but are you
looking to put both serial ports on the same physical
DB9? If so, no big deal, we can just make up a Y
cable with the individual DB9 connectors for each
--- scott@... wrote:
> Getting the second port to work for GPS should behttp://us.click.yahoo.com/DHchtC/3FxNAA/yQLSAA/ELTolB/TM
> pretty easy. KISS too. I
> think the console will probably be confined to one
> port for simplicity.
> I'm going to get a board submitted this week
> (honest!) with a 10-day
> turnaround. Assuming no major problems, that'll
> probably be pretty much the
> board that goes into initial production. Cases will
> be available in a few
> weeks and I want to have something ready to go then.
> I'll likely be doing just kits to start with, but
> I'd rather have a bit of a
> slow start to help iron any bugs out before it
> really goes into mass
> production. I'm sure people will be finding quirks
> with various GPS
> receiver models and that sort of thing.
> > -----Original Message-----
> > From: firstname.lastname@example.org
> > [mailto:email@example.com] On Behalf Of
> Mike Fenske
> > Sent: Monday, June 12, 2006 12:56 PM
> > To: firstname.lastname@example.org
> > Subject: Re: [tracker2] Prototype rev B changes
> > I'll second Curts request. I'd love to see one
> serial port
> > for GPS and the
> > other for TNC (KISS or otherwise). Then, if we had
> the GPS
> > sentences (maybe
> > just $GPMRC) sent out the TNC port, the Tracker 2
> would work
> > with SmartPalm
> > or PocketAPRS.
> > What's the latest estimate on Tracker2
> > Mike Fenske
> > VE7MKF
> > At 10:45 AM 12/06/06 -0700, you wrote:
> > >
> > >On Sun, 11 Jun 2006 scott@... wrote:
> > >
> > >> Pin 6 on the RJ12 jack is now connected to the
> > configuration jumper input
> > >> for convenience. The CTS and RTS handshaking
> signals on
> > the serial port
> > are
> > >> connected to the second serial interface, and
> could be
> > used either as a
> > >> second serial port (with an appropriate cable)
> or for
> > hardware flow control
> > >> (good for the HamHUD.)
> > >
> > >I'd really like to see both of these
> > >
> > >The feature I'd like most would be to have the
> GPS or the KISS port
> > >on that 2nd interface (don't care which). I
> could then build the
> > >unit into the Jeep as a tracker/digipeater (for
> SAR), but still hook
> > >up a HamHUD or a laptop to it when needed without
> disconnecting the
> > >GPS. Of course we'd then need a way of getting
> the GPS data to the
> > >laptop or hamhud as well. I think for a HamHud
> you'd use a y-cable.
> > >For the laptop you'd need the control-E function
> in TNC
> > >command-mode, or MKISS with another port number
> for KISS mode?
> > >
> > >--
> > >Curt, WE7U. APRS Client Comparisons:
> > ------------------------ Yahoo! Groups Sponsor
> > --------------------~-->
> > Home is just a click away. Make Yahoo! your home
> page now.
> > ------~->http://us.click.yahoo.com/DHchtC/3FxNAA/yQLSAA/ELTolB/TM
> > Yahoo! Groups Links
> ------------------------ Yahoo! Groups Sponsor
> Home is just a click away. Make Yahoo! your home
> page now.
> Yahoo! Groups Links
- On Mon, 12 Jun 2006 scott@... wrote:
> I'm sure people will be finding quirks with various GPS receiverHave you seen binary zeropadding in Magellan's waypoint names ?
Someone local tells me his magellan doesn't work with our tracker
thingie, but has not provided dumps. "platinium.txt" (googles)
shows _nasty_ characters, which I suspect is the cause. It only
affected (blocked) GPRMB parsing.
Another "in case it matters",
> Have you seen binary zeropadding in Magellan's waypoint names ?Not that I recall. I'll probably see if I can round up a few more models
that I haven't tested yet (Garmin and otherwise) before the release.
- On Mon, 12 Jun 2006 scott@... wrote:
> Here's the deal with the pin header - I need about 14 pins for expansionA few thoughts: For the 14-pin header, you can talk to the LCD in
> anyway, and it's mostly generic I/O and power/ground, so I'm using the
> layout of the typical HD44780 LCD header and adding a space for a contrast
> adjust resistor. The second serial interface is on the header mostly so you
> can plug in a GPS module there.
> The I2C port is also on the pin header, so that could be used for expansion
> of some sort.
8-bit mode or 4-bit mode. If one were to use 4-bit mode, could you
still use the second serial port for the GPS?
If not, might you consider using the 1-pin circuit for talking to an
LCD using a Dallas one-wire part so that we _could_ hook both an LCD
and a GPS to that port? One of their app-notes describes this,
you've probably seen it.
Perhaps also a couple of switches and a rotary encoder, you get the
Curt, WE7U. APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto: A tax on people who are bad at math." -- unknown
"Windows: Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"