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
serial port.

Jason KE4NYV
RPC Electronics
www.rpc-electronics.com

--- scott@... wrote:

> Getting the second port to work for GPS should be
> 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.
>
> Scott
>
> > -----Original Message-----
> > From: tracker2@yahoogroups.com
> > [mailto:tracker2@yahoogroups.com] On Behalf Of
> Mike Fenske
> > Sent: Monday, June 12, 2006 12:56 PM
> > To: tracker2@yahoogroups.com
> > 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
> availability?
> >
> > 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
> capabilities.
> > >
> > >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:
> http://www.eskimo.com/~archer
> >
> >
> >
> > ------------------------ 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.
>
http://us.click.yahoo.com/DHchtC/3FxNAA/yQLSAA/ELTolB/TM
>
--------------------------------------------------------------------~->
>
>
>
> Yahoo! Groups Links
>
>
>     tracker2-unsubscribe@yahoogroups.com
>
>
>
>
>
>

---

From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of Wes Johnston
Sent: Monday, June 12, 2006 6:45 AM
To: tracker2@yahoogroups.com
Subject: Re: [tracker2] Prototype rev B changes

Mute 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@...

To: tracker2@yahoogroups.com

Sent: Sunday, June 11, 2006 6:36 PM

Subject: [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
input.

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!

Scott

On Mon, 12 Jun 2006 scott@... wrote:

> I'm sure people will be finding quirks with various GPS receiver

Have 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",
Juha OH5NXO

> 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.

Scott

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the tracker2
group.

   File        : /Tracker2.txt
   Uploaded by : n1vg <scott@...>
   Description : Tracker2 documentation

You can access this file at the URL:
http://groups.yahoo.com/group/tracker2/files/Tracker2.txt

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/help/us/groups/files

Regards,

n1vg <scott@...>

POSITION command is now implemented to set fixed position.  You'll need the
new otwincfg.exe - the fixed position is now in a different storage
location, so using it doesn't cut into the available comment space.  It's
picky about entry format - see the tracker2.txt file for details.

CALIBRATE now lets you adjust transmit level on the fly to set deviation.  [
and ] are the coarse adjustments, and - and + are the fine adjustments.  The
new level will automatically be written to flash when you exit calibrate
mode.

Scott

I've updated the firmware again - that last release had a glitch that would
cause the DISPLAY command to enter calibrate mode.

Fixed that, and modified the SMARTBCON command so that it now takes the
SmartBeaconing settings.  The format is:

SMARTBCON <low speed> <high speed> <low rate> <turn angle> <minimum
interval>
or
SMARTBCON OFF

Speed units aren't converted yet, so the settings accept native units which
work out to about 1/1.397 mph.  The high speed transmit rate is just the
INTERVAL setting and is omitted here.

Scott

On Mon, 12 Jun 2006 scott@... wrote:

> 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.

A few thoughts:  For the 14-pin header, you can talk to the LCD in
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
picture...

--
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!"

This one is something of an experiment.  The only change is that now in
Garmin mode the tracker will respond to a product request packet.  This is
what a PC mapping program uses to identify the device it's connected to.

The big question here is which mapping programs will display incoming
waypoints when they haven't specifically been requested.  I was able to get
USAPhotoMaps to plot waypoint by selecting the 'receive waypoints' option.
However, there's no guarantee that'll work properly with all mapping
programs.  When a program requests a waypoint dump, it expects a count of
the records, followed by the waypoints themselves, followed by an
end-of-transfer packet.  In this case, it's only getting waypoint records.
What happens depends entirely on how the mapping program was written.

This should be a good application for the optional FRAM memory.  The tracker
could write all waypoints to memory, and then send them using the normal
Garmin transfer protocol when requested.  Any mapping program that supports
Garmin waypoint downloads should then be able to do APRS, but it'll require
user intervention.  Still, it'll greatly expand your choices for APRS
mapping.

Anyway, if you've got a favorite mapping program, fire it up and try it out,
let me know what happens.

Scott

Scott, when I issue a DISPLAY command there are
several spots where there is a blank line or lines.
Is this intentional?  I thought you might be trying to
split up blocks of like commands, but near the top of
the list is about a 6 line space.  Just curious.

So far, the lastest seems stable and working fine.

Jason KE4NYV
RPC Electronics
www.rpc-electronics.com

--- scott@... wrote:

> This one is something of an experiment.  The only
> change is that now in
> Garmin mode the tracker will respond to a product
> request packet.  This is
> what a PC mapping program uses to identify the
> device it's connected to.
>
> The big question here is which mapping programs will
> display incoming
> waypoints when they haven't specifically been
> requested.  I was able to get
> USAPhotoMaps to plot waypoint by selecting the
> 'receive waypoints' option.
> However, there's no guarantee that'll work properly
> with all mapping
> programs.  When a program requests a waypoint dump,
> it expects a count of
> the records, followed by the waypoints themselves,
> followed by an
> end-of-transfer packet.  In this case, it's only
> getting waypoint records.
> What happens depends entirely on how the mapping
> program was written.
>
> This should be a good application for the optional
> FRAM memory.  The tracker
> could write all waypoints to memory, and then send
> them using the normal
> Garmin transfer protocol when requested.  Any
> mapping program that supports
> Garmin waypoint downloads should then be able to do
> APRS, but it'll require
> user intervention.  Still, it'll greatly expand your
> choices for APRS
> mapping.
>
> Anyway, if you've got a favorite mapping program,
> fire it up and try it out,
> let me know what happens.
>
> Scott
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor
> --------------------~-->
> Great things are happening at Yahoo! Groups.  See
> the new email design.
>
http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/ELTolB/TM
>
--------------------------------------------------------------------~->
>
>
>
> Yahoo! Groups Links
>
>
>     tracker2-unsubscribe@yahoogroups.com
>
>
>
>
>
>

> Scott, when I issue a DISPLAY command there are
> several spots where there is a blank line or lines.
> Is this intentional?  I thought you might be trying to
> split up blocks of like commands, but near the top of
> the list is about a 6 line space.  Just curious.

That's an artifact of how it handles the 'array' type commands.  One call to
ALIAS causes it to spit out the whole list, and to do that it bypasses the
usual output mechanism.  That's where the extra line break comes in, and it
means those commands don't return anything when used remotely.  Still
looking for a more elegant solution.

Ideally, you should be able to paste the output of the DISPLAY command to
another tracker and effectively clone the configuration.  There might wind
up being some exceptions to that, though.

Scott

I'm going to try to implement a rotor control function for the T2.  The
Rotor-EZ controller supports a very simple command interface, so I'll
probably go with that, unless someone can suggest another.  The command
would probably be something like this:

ROTOR <degrees>  (for remote manual control)
ROTOR TRACK <callsign>  (for automatic tracking)

Hopefully I won't have to implement dead reckoning for the automatic
tracking.  It should be useful for things like air-to-ground ATV.

The distance and bearing code is already there, as is the position parsing,
so this really shouldn't take a lot of extra work.

Is there anyone out there who has a suitable rotor setup and would be
interested in testing it?

Scott

What you gunna do when it tracks past a limit?  If you run a az/el setup, it
only has to go 180degrees and flip the beam upside down... a little faster cycle
time.  I know you are considering serial output, but have you thought about PWM
servo control?  Just throwing things out there to "sounding board".

Wes

----- Original Message -----
From: scott@...
To: tracker2@yahoogroups.com
Sent: Mon, 19 Jun 2006 13:13:32 -0700
Subject: [tracker2] Rotor control


> I'm going to try to implement a rotor control function for the T2.  The
> Rotor-EZ controller supports a very simple command interface, so I'll
> probably go with that, unless someone can suggest another.  The command
> would probably be something like this:
>
> ROTOR <degrees>  (for remote manual control)
> ROTOR TRACK <callsign>  (for automatic tracking)
>
> Hopefully I won't have to implement dead reckoning for the automatic
> tracking.  It should be useful for things like air-to-ground ATV.
>
> The distance and bearing code is already there, as is the position parsing,
> so this really shouldn't take a lot of extra work.
>
> Is there anyone out there who has a suitable rotor setup and would be
> interested in testing it?
>
> Scott
>
>
>
>
>

I'd rather not get into the mechanics of rotor control at this point.  The
Rotor-EZ takes serial commands that specify a pointing direction in degrees,
and the controller takes care of the rest.  Maybe if it turns out to be a
major application I'll look at it more in the future, but for now the serial
output is a quick way to get it to do something useful.

Scott

> -----Original Message-----
> From: tracker2@yahoogroups.com
> [mailto:tracker2@yahoogroups.com] On Behalf Of Wes Johnston
> Sent: Monday, June 19, 2006 4:16 PM
> To: tracker2@yahoogroups.com
> Subject: Re: [tracker2] Rotor control
>
> What you gunna do when it tracks past a limit?  If you run a
> az/el setup, it only has to go 180degrees and flip the beam
> upside down... a little faster cycle time.  I know you are
> considering serial output, but have you thought about PWM
> servo control?  Just throwing things out there to "sounding board".
>
> Wes
>
> ----- Original Message -----
> From: scott@...
> To: tracker2@yahoogroups.com
> Sent: Mon, 19 Jun 2006 13:13:32 -0700
> Subject: [tracker2] Rotor control
>
>
> > I'm going to try to implement a rotor control function for
> the T2.  The
> > Rotor-EZ controller supports a very simple command
> interface, so I'll
> > probably go with that, unless someone can suggest another.
> The command
> > would probably be something like this:
> >
> > ROTOR <degrees>  (for remote manual control)
> > ROTOR TRACK <callsign>  (for automatic tracking)
> >
> > Hopefully I won't have to implement dead reckoning for the automatic
> > tracking.  It should be useful for things like air-to-ground ATV.
> >
> > The distance and bearing code is already there, as is the
> position parsing,
> > so this really shouldn't take a lot of extra work.
> >
> > Is there anyone out there who has a suitable rotor setup
> and would be
> > interested in testing it?
> >
> > Scott
> >
> >
> >
> >
> >
>
>
>
> ------------------------ Yahoo! Groups Sponsor
> --------------------~-->
> Yahoo! Groups gets a make over. See the new email design.
> http://us.click.yahoo.com/XISQkA/lOaOAA/yQLSAA/ELTolB/TM
> --------------------------------------------------------------
> ------~->
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>

I made my longest trip yet with a (working) T2 prototype yesterday, and it
worked well.  I drove from Santa Maria to Long Beach, up to Simi Valley, and
back to Santa Maria.  Total trip was a bit over 400 miles.

The GPS recorded 187 received waypoints.  It's still out there in the car,
and has decoded about 9000 packets in 48 hours or so.  No lockups or
glitches at all, as far as I can see.

There IS something wrong with SmartBeaconing, though.  I'm not sure if it's
specific to Garmin mode or not, but I'll find out.  I also identified a
parsing problem on FindU - it doesn't always process compressed positions
properly.  No word from Steve yet on that one.  It's very possible that the
T2 is the only thing out there reporting the position source as 'other' (in
Garmin mode) rather than GPRMC, GPGLL, or GPGGA.  That could explain why the
problem hasn't shown up before.

If anyone's interested in experimenting with command gating, let me know and
I'll add you to the authlist.  And if anyone's got a running unit they don't
mind me poking around in, let me know and I'll try it out from the other
direction.

OT2m Proto 'B' went to the board house yesterday.  They *might* make it here
by the end of next week, but I'll be out of town for the holiday weekend.

Scott

On Wed, 21 Jun 2006 scott@... wrote:

> T2 is the only thing out there reporting the position source as 'other' (in
> Garmin mode) rather than GPRMC, GPGLL, or GPGGA

I read the spec so that it's GLL, when there is no course/speed
nor altitude in the cs-bytes, NMEA or not.
Would be nice to be able to report all 3 cse, spd and altitude at once.
'source other' == next 3 bytes are ANOTHER csT ;)


Juha, OH5NXO

> Would be nice to be able to report all 3 cse, spd and
> altitude at once.
> 'source other' == next 3 bytes are ANOTHER csT ;)

Yeah, it has its deficiencies.  I'm still considering a protocol that'd be
basically a stripped-down version of OpenTRAC with FEC and optional
encryption for commercial users.  Rather than having all of the element tag
data of OpenTRAC, it'd have a fixed set of required elements (3D position,
velocity, symbol, etc) plus a few validity bits, and THEN optional
extensions.

Since it'd be T2-specific (to start with anyway) it wouldn't even have to be
based on AX.25.  A complete packet might be 20 bytes.  Expand that to 30
with FEC and you've still got a short packet that's less likely to get
clobbered by noise, and able to tolerate some damage if it is.

Scott

>
> If anyone's interested in experimenting with command
> gating, let me know and
> I'll add you to the authlist.  And if anyone's got a
> running unit they don't
> mind me poking around in, let me know and I'll try
> it out from the other
> direction.


Hi,

Apologies I've not being contributing much of late,
I'm swamped in work.  I'm hoping one of the T2's goes
online in the next week or so at a site where we
previously had no APRS coverage.

The second one I have I'll update it tonight and
switch it on.  What do you need to play from the other
end?

de John
EI7IG






___________________________________________________________
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of
use." - PC Magazine
http://uk.docs.yahoo.com/nowyoucan.html

> Apologies I've not being contributing much of late,
> I'm swamped in work.  I'm hoping one of the T2's goes
> online in the next week or so at a site where we
> previously had no APRS coverage.

Ok, make sure you've got the lastest firmware.  Though I haven't touched the
digipeating much recently.

> The second one I have I'll update it tonight and
> switch it on.  What do you need to play from the other
> end?

I mostly want to see what the latency is like, see if the ACK timing is
adequate and that sort of thing.  I'll just run some STATUS and VERSION
commands, probably.

Scott

>
> Ok, make sure you've got the lastest firmware.
> Though I haven't touched the
> digipeating much recently.
He just made a liar out of me.  Its switched on
(EI7TRG-2) and running since about an hour ago, though
I'm not sure how reliable the path to it is.

He's off on holidays for about a week, so it'll stay
running in that configuration until he gets back.

>
> > The second one I have I'll update it tonight and
> > switch it on.  What do you need to play from the
> other
> > end?
>
> I mostly want to see what the latency is like, see
> if the ACK timing is
> adequate and that sort of thing.  I'll just run some
> STATUS and VERSION
> commands, probably.
>
I'll get a cable made up tomorrow evening or over the
weekend.. and I'll update the second one to the latest
firmware.

Regards
de John
EI7IG




___________________________________________________________
Inbox full of spam? Get leading spam protection and 1GB storage with All New
Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html

Power control is now working.  The command has been changed a bit, though.
It's a single commmand now, 'POWER', and it can be ON, OFF, or a delay.

ON forces the power output on, OFF forces it off.  This lets you use the
high side switch to manually control a DC load.  Setting it to a numeric
value makes the radio power control option function as usual, where it waits
the specified number of seconds for the radio to power up before
transmitting.

The Garmin protocol handler has been restructured - parts of it that were
executed in interrupt context got too big and slow and needed to be executed
in the main program loop.

Scott

> I mostly want to see what the latency is like, see
> if the ACK timing is
> adequate and that sort of thing.  I'll just run some
> STATUS and VERSION
> commands, probably.
>
Hi,

How're you getting on with this?  I've been swamped in
work.  I got a cable made up last night to go to the
rig I have in the shack, I just need to update the
firmware now (Note to self, keyboard cables don't have
the ground wire and also PTT IN != PTT :) ).

Do I recall correctly that I can update the firmware
using xmodem?  the Windows Laptop that I had is no
more, so I only have zterm here on the MAC for sending
up the new firmware.

Regards
John




___________________________________________________________
The all-new Yahoo! Mail goes wherever you go - free your email address from your
Internet provider. http://uk.docs.yahoo.com/nowyoucan.html

Has anyone used this successfully?

Has anyone used this succesfully with zterm on a Mac?

Cheers
John






___________________________________________________________
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of
use." - PC Magazine
http://uk.docs.yahoo.com/nowyoucan.html

I've had a couple of reports of people (besides me) using it, but I don't
recall if any were on a Mac.  You need to use the .bin file, not the .s19
file.  I haven't been updating the .bin version because I haven't written a
translator program yet - preparing the .bin file is a multi-step process
that requires some manual editing.  Once I get a chance to automate it, I'll
make sure it's kept up to date.

The XMODEM support should be the standard, ancient version of the protocol -
128-byte blocks, not XMODEM-CRC or XMODEM-1k.  Just about any comm program
should be able to do that.

If the bootloader doesn't see the proper signature in the first block, it'll
just stop what it's doing.  You'll see 128 bytes transferred, and it'll
hang.

Scott

> -----Original Message-----
> From: tracker2@yahoogroups.com
> [mailto:tracker2@yahoogroups.com] On Behalf Of Jon
> Sent: Wednesday, July 05, 2006 10:14 AM
> To: tracker2@yahoogroups.com
> Subject: [tracker2] Xmodem firmware update.
>
> Has anyone used this successfully?
>
> Has anyone used this succesfully with zterm on a Mac?
>
> Cheers
> John
>
>
>
>
>
>
> ___________________________________________________________
> All new Yahoo! Mail "The new Interface is stunning in its
> simplicity and ease of use." - PC Magazine
> http://uk.docs.yahoo.com/nowyoucan.html
>
>
> ------------------------ Yahoo! Groups Sponsor
> --------------------~-->
> Check out the new improvements in Yahoo! Groups email.
> http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/ELTolB/TM
> --------------------------------------------------------------
> ------~->
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>

Got a Linux box started up and minicom on it
> .bin file, not the .s19
the .bin file is what I'm using
> file.  I haven't been updating the .bin version
> because I haven't written a
> translator program yet - preparing the .bin file is
> a multi-step process
> that requires some manual editing.  Once I get a
> chance to automate it, I'll
> make sure it's kept up to date.
>
Ah.. ok. its behind a bit...
> The XMODEM support should be the standard, ancient
> version of the protocol -
> 128-byte blocks, not XMODEM-CRC or XMODEM-1k.  Just
> about any comm program
> should be able to do that.
>
I'm trying minicom now


> If the bootloader doesn't see the proper signature
> in the first block, it'll
> just stop what it's doing.  You'll see 128 bytes
> transferred, and it'll
> hang.
oh oh.

got several NAK on sector messages...

It seems to be hung.. alternating between green & red
in the led... briefly blinking green

:(




___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo!
Security Centre. http://uk.security.yahoo.com

I think it was just stuck..

I borrowed my neighbours laptop and programmed it
succesfully with that...

After the next ISS pass I'll plug it into the RIG and
it'll be back online again..



___________________________________________________________
Try the all-new Yahoo! Mail. "The New Version is radically easier to use" – The
Wall Street Journal
http://uk.docs.yahoo.com/nowyoucan.html

Ok.  I'll try to get an updated .bin done today - the last one is pretty
old.

You should get a green-green-green-green-red sort of blink pattern.  Red
blinks are page erases, green blinks are row writes.  There are 128 bytes to
a row (and to an XMODEM block) and 512 bytes to a page.

Scott

> -----Original Message-----
> From: tracker2@yahoogroups.com
> [mailto:tracker2@yahoogroups.com] On Behalf Of Jon
> Sent: Wednesday, July 05, 2006 11:06 AM
> To: tracker2@yahoogroups.com
> Subject: RE: [tracker2] Xmodem firmware update.
>
> I think it was just stuck..
>
> I borrowed my neighbours laptop and programmed it
> succesfully with that...
>
> After the next ISS pass I'll plug it into the RIG and
> it'll be back online again..
>
>
>
> ___________________________________________________________
> Try the all-new Yahoo! Mail. "The New Version is radically
> easier to use" - The Wall Street Journal
> http://uk.docs.yahoo.com/nowyoucan.html
>
>
> ------------------------ Yahoo! Groups Sponsor
> --------------------~-->
> Great things are happening at Yahoo! Groups.  See the new
> email design.
> http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/ELTolB/TM
> --------------------------------------------------------------
> ------~->
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>

Apologies for the previous blank email..

Just back from a club meeting,

The power switch is cool, very cool.. now I need
something to switch on with it :)

My voltage reading seems low, measuring R6 and R7.. R7
Seems low in value, though being in circuit, i'm not
sure how that would affect the readings.

Callsign of this one is EI7IG-14.

Cheers
John






___________________________________________________________
All New Yahoo! Mail – Tired of Vi@gr@! come-ons? Let our SpamGuard protect you.
http://uk.docs.yahoo.com/nowyoucan.html

It doesn't seem to operate remotely (neither does digi
on/off).  I've added EI7IG (and N1VG) to the authlist,
I'm wondering if it should be EI7IG-7 (which won't
add).

I couldnt' find the email with the command summary so
I looked in the files section, it probably should be
in there.. also I couldn't download "Tracker2.txt"
either.

I'm off for zzz's... talk tomorrow.










___________________________________________________________
Now you can scan emails quickly with a reading pane. Get the new Yahoo! Mail.
http://uk.docs.yahoo.com/nowyoucan.html

The voltage reading is limited in accuracy by the voltage regulator, since
it provides the 5 volt reference.  How far off is the reading?

> -----Original Message-----
> From: tracker2@yahoogroups.com
> [mailto:tracker2@yahoogroups.com] On Behalf Of Jon
> Sent: Wednesday, July 05, 2006 2:09 PM
> To: tracker2@yahoogroups.com
> Subject: [tracker2] Power Switch
>
> Apologies for the previous blank email..
>
> Just back from a club meeting,
>
> The power switch is cool, very cool.. now I need
> something to switch on with it :)
>
> My voltage reading seems low, measuring R6 and R7.. R7
> Seems low in value, though being in circuit, i'm not
> sure how that would affect the readings.
>
> Callsign of this one is EI7IG-14.
>
> Cheers
> John
>
>
>
>
>
>
> ___________________________________________________________
> All New Yahoo! Mail - Tired of Vi@gr@! come-ons? Let our
> SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html
>
>
> ------------------------ Yahoo! Groups Sponsor
> --------------------~-->
> Yahoo! Groups gets a make over. See the new email design.
> http://us.click.yahoo.com/XISQkA/lOaOAA/yQLSAA/ELTolB/TM
> --------------------------------------------------------------
> ------~->
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>