Okay, here are the results!

After spending an hour figuring out what coax went to the antenna on the roof, I
was able to hook up the radio and hear good sounding strong packets.  The
problem was still present.  I decided to skip comparing to the other TNC/Radio
for now because of the time it would take to get that put back together.

To get the demodulator section reflowed I had to get out the flux and I used a
fine tip and did each solder point individually. I put The T2-135 back in the
radio and it worked great.  I proceeded to finish this same reflow process on
the rest of the board, cleaned the board with some alcohol, and reinstalled
again.  I was able to throw in 20dB of attenuation before I started to have
problems decoding packets.  At this point the signal was not showing up on the
radio's meter and sounded very weak. Seems like it was indeed the solder
process.

Thanks for the help guys.

73,
Scott - kb9szw

Glad that fixed it for you.  There was something definitely weird with
the assembly of that batch.  I just got a new batch of bare boards in,
but I'm not using that place for assembly again.

Scott

Scott Brock wrote:
>
>
> Okay, here are the results!
>
> After spending an hour figuring out what coax went to the antenna on the
> roof, I was able to hook up the radio and hear good sounding strong
> packets. The problem was still present. I decided to skip comparing to
> the other TNC/Radio for now because of the time it would take to get
> that put back together.
>
> To get the demodulator section reflowed I had to get out the flux and I
> used a fine tip and did each solder point individually. I put The T2-135
> back in the radio and it worked great. I proceeded to finish this same
> reflow process on the rest of the board, cleaned the board with some
> alcohol, and reinstalled again. I was able to throw in 20dB of
> attenuation before I started to have problems decoding packets. At this
> point the signal was not showing up on the radio's meter and sounded
> very weak. Seems like it was indeed the solder process.
>
> Thanks for the help guys.
>
> 73,
> Scott - kb9szw
>
>

Hello, I have most of the pins determined with making my cable that
goes from the icom 2100 mike port to the 9 pin female port on the
tracker2

What I am confused about is how to connect the PTT and PTT ground
connections to the tracker 2's PTT in and PTT out connections.

Any help is sure appreciated.

thanks
stephen KC8WQL

I have a cable wired for the IC-2200 works fine, same pins?  Ron

On Jul 29, 2008, at 11:10 PM, sprovost64 wrote:

> Hello, I have most of the pins determined with making my cable that
> goes from the icom 2100 mike port to the 9 pin female port on the
> tracker2
>
> What I am confused about is how to connect the PTT and PTT ground
> connections to the tracker 2's PTT in and PTT out connections.
>
> Any help is sure appreciated.
>
> thanks
> stephen KC8WQL
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Bill KB1MOV wrote...

> I am beating my head against a brick wall trying to get UI-View to see
> position packets being sent by another tracker. UI-View is connected
> to a DR-135 and T2-135. I have tried placing the primary port (AMODE)
> into KISS and leaving no commands for the KISS setup in UI-View.

I had poor results by putting a T2-135 in KISS mode ahead of time. I
would suggest AMODE AUTO.

> I also tried the KISS commands shown below. In all cases I cannot see
> the signal.  Now, I have tried the system set up with an alternative
> radio and that seems to like KISS. That was a Kenwood TM-G707
> connected to a KPC3+ connected to UI-View. That seemed to read the
> signal just fine. Any suggestions?

The reason the KPC3+ works fine in KISS mode because UI-View
knows how to put it in KISS mode and how to take it out of KISS mode
if you close the program or the com port.

> 1: 003,003,003
> 2: INT 0 (so it won't beacon on its own)
> 3: AMODE KISS
>
> Exit KISS...
> 003,003,003

It was actually me who posted those settings back on Feb 13 2008.
Originally, I just had "AMODE KISS" for the into KISS settings and
"003,003,003" for the exit KISS mode settings. The "003" is HEX for
control-C. By May 15, I was suggesting using "003,003,003" for the start
of the into KISS settings as well. It should work as long as you didn't
have it set for AMODE GARMIN ahead of time. Make sure you aren't
using any profile switching. while you are at it, make sure none of the
digi aliased are enabled unless you specifically want it to digipeat
independently from UI-View. The INT 0 in the "into KISS" settings
should stop it from beaconing independently from UI-View.

Do this test. Set UI-View to com port none, or close the program. Run
otwincfg.exe and make sure you aren't using profile switching and it
isn't set for Garmin mode. Then fire up a terminal program. Make sure
you get a cmd: prompt. Type MON ON and hit enter. Observe it copying
received packets. Type AMODE KISS and hit enter. You should see some
"garbage" on the screen when you receive a packet. Send three control-Cs
to the T2-135. You should get a cmd: prompt every time. Turn MON OFF.

Then go back to UI-View and open the terminal window. Under options, I
set it to exclude Internet traffic. If UI-View doesn't have a TCPIP
connection, it won't make any difference. Enable the com port again. You
should observe received packets if there is any activity. Hitting F9,
you should see it transmit.

73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"

I've got an Alinco DR-135/T2-135 combo that has been working happily
until a few weeks ago. A friend of mine who lives near me alerted me
to a dead carrier he was receiving on 144.390 right about the time I
left for work, I couldn't check it until I got to work, and sure
enough it was me.

I'm not sure what's causing it, but it is related to the T2-135. I
removed it, powered the radio back up and it's not stuck in transmit.
I was also hopeful that by removing the T2-135 that it would clear
itself up, but I didn't get that lucky.

Any ideas? Could it be corrupt firmware or bad hardware? I have been
running this in my vehicle since I bought it last fall, no problems
until now, not sure what firmware revision is on the board, I updated
it to whatever revision was the latest at the time, installed it and
forgot about it.

tnx and 73,
Stephen

--
Stephen Brown - ARS K1LNX
Johnson City, TN EM86
http://www.k1lnx.net

Stephen K1LNX wrote...

> I've got an Alinco DR-135/T2-135 combo that has been working happily
> until a few weeks ago. A friend of mine who lives near me alerted me
> to a dead carrier he was receiving on 144.390 right about the time I
> left for work, I couldn't check it until I got to work, and sure
> enough it was me...

I'm not sure what would be causing it either, but you could enable the
TOT (time out timer) on the radio to limit the time it would stay on
transmit.

73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"

I seem to remember someone reporting that their nuvi dropped out of FMI
mode and wouldn't work again, but I can't find it in the archives.  Who
was that, and what model was it?  I'm hearing reports from another FMI
integrator that some nuvi 760s stop working after a little while due to
some sort of hardware problem.

Scott

It's only stuck in transmit when the T2-135 is installed?  What about if
it's not in digital mode?

Either way, I'd like to take a look at it and dump the firmware, see if
it's a hardware problem or if there was a glitch in the flash memory.

Scott

Stephen - K1LNX wrote:
>
>
> I've got an Alinco DR-135/T2-135 combo that has been working happily
> until a few weeks ago. A friend of mine who lives near me alerted me
> to a dead carrier he was receiving on 144.390 right about the time I
> left for work, I couldn't check it until I got to work, and sure
> enough it was me.
>
> I'm not sure what's causing it, but it is related to the T2-135. I
> removed it, powered the radio back up and it's not stuck in transmit.
> I was also hopeful that by removing the T2-135 that it would clear
> itself up, but I didn't get that lucky.
>
> Any ideas? Could it be corrupt firmware or bad hardware? I have been
> running this in my vehicle since I bought it last fall, no problems
> until now, not sure what firmware revision is on the board, I updated
> it to whatever revision was the latest at the time, installed it and
> forgot about it.
>
> tnx and 73,
> Stephen
>
> --
> Stephen Brown - ARS K1LNX
> Johnson City, TN EM86
> http://www.k1lnx.net <http://www.k1lnx.net>
>
>

> It's only stuck in transmit when the T2-135 is installed? What about if
> it's not in digital mode?

Correct. I haven't tried it without it being in digital mode, but I'll
test that and post the results here shortly.....

> Either way, I'd like to take a look at it and dump the firmware, see if
> it's a hardware problem or if there was a glitch in the flash memory.

I'd be glad to send it to you :) I should also mention (not sure that
this matters) that I run it in KISS mode and it talks to a HamHUD. I
originally thought the 'HUD might be the problem, but I disconnected
that first and the problem remained which led me to the conclusion of
the T2 being the issue.

tnx
Stephen
K1LNX


On Wed, Jul 30, 2008 at 1:37 PM, Scott Miller <scott@...> wrote:
> It's only stuck in transmit when the T2-135 is installed? What about if
> it's not in digital mode?
>
> Either way, I'd like to take a look at it and dump the firmware, see if
> it's a hardware problem or if there was a glitch in the flash memory.
>
> Scott
>
> Stephen - K1LNX wrote:
>>
>>
>> I've got an Alinco DR-135/T2-135 combo that has been working happily
>> until a few weeks ago. A friend of mine who lives near me alerted me
>> to a dead carrier he was receiving on 144.390 right about the time I
>> left for work, I couldn't check it until I got to work, and sure
>> enough it was me.
>>
>> I'm not sure what's causing it, but it is related to the T2-135. I
>> removed it, powered the radio back up and it's not stuck in transmit.
>> I was also hopeful that by removing the T2-135 that it would clear
>> itself up, but I didn't get that lucky.
>>
>> Any ideas? Could it be corrupt firmware or bad hardware? I have been
>> running this in my vehicle since I bought it last fall, no problems
>> until now, not sure what firmware revision is on the board, I updated
>> it to whatever revision was the latest at the time, installed it and
>> forgot about it.
>>
>> tnx and 73,
>> Stephen
>>
>> --
>> Stephen Brown - ARS K1LNX
>> Johnson City, TN EM86
>> http://www.k1lnx.net <http://www.k1lnx.net>
>>
>>
>
>



--
Stephen Brown - ARS K1LNX
Johnson City, TN EM86
http://www.k1lnx.net

I seem to remember someone reporting that their nuvi dropped out of FMI
mode and wouldn't work again, but I can't find it in the archives. Who
was that, and what model was it? I'm hearing reports from another FMI
integrator that some nuvi 760s stop working after a little while due to
some sort of hardware problem.

Scott

-- Jim Tolbert
RiverRidge Consulting, LLC
PO Box 536
Webster, WI 54893
715-866-4398 home office
RiverRidge@...

Ok.  You can send it to:

Argent Data Systems
PO Box 579
Santa Maria, CA 93456-0579

Make sure you include a note about the problem and a return address.

Scott

Stephen - K1LNX wrote:
>
>
>  > It's only stuck in transmit when the T2-135 is installed? What about if
>  > it's not in digital mode?
>
> Correct. I haven't tried it without it being in digital mode, but I'll
> test that and post the results here shortly.....
>
>  > Either way, I'd like to take a look at it and dump the firmware, see if
>  > it's a hardware problem or if there was a glitch in the flash memory.
>
> I'd be glad to send it to you :) I should also mention (not sure that
> this matters) that I run it in KISS mode and it talks to a HamHUD. I
> originally thought the 'HUD might be the problem, but I disconnected
> that first and the problem remained which led me to the conclusion of
> the T2 being the issue.
>
> tnx
> Stephen
> K1LNX
>
> On Wed, Jul 30, 2008 at 1:37 PM, Scott Miller <scott@...
> <mailto:scott%40opentrac.org>> wrote:
>  > It's only stuck in transmit when the T2-135 is installed? What about if
>  > it's not in digital mode?
>  >
>  > Either way, I'd like to take a look at it and dump the firmware, see if
>  > it's a hardware problem or if there was a glitch in the flash memory.
>  >
>  > Scott
>  >
>  > Stephen - K1LNX wrote:
>  >>
>  >>
>  >> I've got an Alinco DR-135/T2-135 combo that has been working happily
>  >> until a few weeks ago. A friend of mine who lives near me alerted me
>  >> to a dead carrier he was receiving on 144.390 right about the time I
>  >> left for work, I couldn't check it until I got to work, and sure
>  >> enough it was me.
>  >>
>  >> I'm not sure what's causing it, but it is related to the T2-135. I
>  >> removed it, powered the radio back up and it's not stuck in transmit.
>  >> I was also hopeful that by removing the T2-135 that it would clear
>  >> itself up, but I didn't get that lucky.
>  >>
>  >> Any ideas? Could it be corrupt firmware or bad hardware? I have been
>  >> running this in my vehicle since I bought it last fall, no problems
>  >> until now, not sure what firmware revision is on the board, I updated
>  >> it to whatever revision was the latest at the time, installed it and
>  >> forgot about it.
>  >>
>  >> tnx and 73,
>  >> Stephen
>  >>
>  >> --
>  >> Stephen Brown - ARS K1LNX
>  >> Johnson City, TN EM86
>  >> http://www.k1lnx.net <http://www.k1lnx.net> <http://www.k1lnx.net
> <http://www.k1lnx.net>>
>  >>
>  >>
>  >
>  >
>
> --
> Stephen Brown - ARS K1LNX
> Johnson City, TN EM86
> http://www.k1lnx.net <http://www.k1lnx.net>
>
>

Thanks Scott.... I'll get it out in the mail NLT tommorow....

73
Stephen
K1LNX

On Wed, Jul 30, 2008 at 1:56 PM, Scott Miller <scott@...> wrote:
> Ok. You can send it to:
>
> Argent Data Systems
> PO Box 579
> Santa Maria, CA 93456-0579
>
> Make sure you include a note about the problem and a return address.
>
> Scott
>
> Stephen - K1LNX wrote:
>>
>>
>> > It's only stuck in transmit when the T2-135 is installed? What about if
>> > it's not in digital mode?
>>
>> Correct. I haven't tried it without it being in digital mode, but I'll
>> test that and post the results here shortly.....
>>
>> > Either way, I'd like to take a look at it and dump the firmware, see if
>> > it's a hardware problem or if there was a glitch in the flash memory.
>>
>> I'd be glad to send it to you :) I should also mention (not sure that
>> this matters) that I run it in KISS mode and it talks to a HamHUD. I
>> originally thought the 'HUD might be the problem, but I disconnected
>> that first and the problem remained which led me to the conclusion of
>> the T2 being the issue.
>>
>> tnx
>> Stephen
>> K1LNX
>>
>> On Wed, Jul 30, 2008 at 1:37 PM, Scott Miller <scott@...
>> <mailto:scott%40opentrac.org>> wrote:
>> > It's only stuck in transmit when the T2-135 is installed? What about if
>> > it's not in digital mode?
>> >
>> > Either way, I'd like to take a look at it and dump the firmware, see if
>> > it's a hardware problem or if there was a glitch in the flash memory.
>> >
>> > Scott
>> >
>> > Stephen - K1LNX wrote:
>> >>
>> >>
>> >> I've got an Alinco DR-135/T2-135 combo that has been working happily
>> >> until a few weeks ago. A friend of mine who lives near me alerted me
>> >> to a dead carrier he was receiving on 144.390 right about the time I
>> >> left for work, I couldn't check it until I got to work, and sure
>> >> enough it was me.
>> >>
>> >> I'm not sure what's causing it, but it is related to the T2-135. I
>> >> removed it, powered the radio back up and it's not stuck in transmit.
>> >> I was also hopeful that by removing the T2-135 that it would clear
>> >> itself up, but I didn't get that lucky.
>> >>
>> >> Any ideas? Could it be corrupt firmware or bad hardware? I have been
>> >> running this in my vehicle since I bought it last fall, no problems
>> >> until now, not sure what firmware revision is on the board, I updated
>> >> it to whatever revision was the latest at the time, installed it and
>> >> forgot about it.
>> >>
>> >> tnx and 73,
>> >> Stephen
>> >>
>> >> --
>> >> Stephen Brown - ARS K1LNX
>> >> Johnson City, TN EM86
>> >> http://www.k1lnx.net <http://www.k1lnx.net> <http://www.k1lnx.net
>> <http://www.k1lnx.net>>
>> >>
>> >>
>> >
>> >
>>
>> --
>> Stephen Brown - ARS K1LNX
>> Johnson City, TN EM86
>> http://www.k1lnx.net <http://www.k1lnx.net>
>>
>>
>
>



--
Stephen Brown - ARS K1LNX
Johnson City, TN EM86
http://www.k1lnx.net

I guess that wasn't it... I could swear someone had a unit that just
wouldn't work at all after it dropped out of FMI mode.

Scott

Jim Tolbert wrote:
>
>
> My nuvi 350 dropped out of FMI mode after I loaded a "pre-nuvi" version
> of T2 firmware.  After I again loaded a version of the firmware that
> supported the nuvi, it again jumped into FMI mode.   It only happened
> the one time.
>
> Is there any other info I can provide?
>
> I "believe" that I am operational now and only suffering from the "one
> walki-talki" problem -- that is, if there was anyone else or an igate
> close to me, I could send & receive.
>
> Later..................... Jim, KC9MXT
>
> Scott Miller wrote:
>
>> I seem to remember someone reporting that their nuvi dropped out of FMI
>> mode and wouldn't work again, but I can't find it in the archives. Who
>> was that, and what model was it? I'm hearing reports from another FMI
>> integrator that some nuvi 760s stop working after a little while due to
>> some sort of hardware problem.
>>
>> Scott
>>
>
> --
> Jim Tolbert
> RiverRidge Consulting, LLC
> PO Box 536
> Webster, WI 54893
>
> 715-866-4398 home office
>
> RiverRidge@...
>
>

Ron-thanks for replying.
I can use your pinout for the IC2200 if you would be kind to reply
with your pinout of the cable.
I need to know how the PTT cabling works.
thanks
stephen KC8WQL

--- In tracker2@yahoogroups.com, Ron N9QGS <APRSdash9@...> wrote:
>
> I have a cable wired for the IC-2200 works fine, same pins?  Ron
>
> On Jul 29, 2008, at 11:10 PM, sprovost64 wrote:
>
> > Hello, I have most of the pins determined with making my cable
that
> > goes from the icom 2100 mike port to the 9 pin female port on the
> > tracker2
> >
> > What I am confused about is how to connect the PTT and PTT ground
> > connections to the tracker 2's PTT in and PTT out connections.
> >
> > Any help is sure appreciated.
> >
> > thanks
> > stephen KC8WQL
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
>

I have posted diagrams of a number of OT and TT interfaces to
http://garlandr.s412.sureserver.com/graces/Tech-Info.html . Most have been
inplementedb, but as always Murphy is still around. (2100 is included)

73, John - N5TIM

sprovost64 wrote:
>
>
> Ron-thanks for replying.
> I can use your pinout for the IC2200 if you would be kind to reply
> with your pinout of the cable.
> I need to know how the PTT cabling works.
> thanks
> stephen KC8WQL
>
> --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>, Ron
> N9QGS <APRSdash9@...> wrote:
>  >
>  > I have a cable wired for the IC-2200 works fine, same pins? Ron
>  >
>  > On Jul 29, 2008, at 11:10 PM, sprovost64 wrote:
>  >
>  > > Hello, I have most of the pins determined with making my cable
> that
>  > > goes from the icom 2100 mike port to the 9 pin female port on the
>  > > tracker2
>  > >
>  > > What I am confused about is how to connect the PTT and PTT ground
>  > > connections to the tracker 2's PTT in and PTT out connections.
>  > >
>  > > Any help is sure appreciated.
>  > >
>  > > thanks
>  > > stephen KC8WQL
>  > >
>  > >
>  > > ------------------------------------
>  > >
>  > > Yahoo! Groups Links
>  > >
>  > >
>  > >
>  >
>
>

--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
John Galvin - N5TIM
http://www.qsl.net/n5tim for Public Service Info
http://www.garlandraces.net/

JUNK - Stuff we throw away ... STUFF - Junk we keep!

Concur with Keith,
Eventhough I never had this TX-lockup situation with T2 boards, I always set TOT
on the DR-135 radio to 30 seconds (way long enough to send a packet, but would
prevent locking-up the frequency).

Procedure:
- press and hold FUNC button for more than 2 seconds
- press UP or DOWN until TOT is shown on the screen
- twist the knob till TOT-30 is shown
- press UP or DOWN to save the new setting
- press any button, except SQL/UP/DOWN, to exit from the menu

73 de Paulus N5SNN / YD0NXX

--- On Wed, 7/30/08, Keith VE7GDH <ve7gdh@...> wrote:

> From: Keith VE7GDH <ve7gdh@...>
> Subject: Re: [tracker2] T2-135 causing TX to hang
> To: tracker2@yahoogroups.com
> Date: Wednesday, July 30, 2008, 12:21 PM
> Stephen K1LNX wrote...
>
> > I've got an Alinco DR-135/T2-135 combo that has
> been working happily
> > until a few weeks ago. A friend of mine who lives near
> me alerted me
> > to a dead carrier he was receiving on 144.390 right
> about the time I
> > left for work, I couldn't check it until I got to
> work, and sure
> > enough it was me...
>
> I'm not sure what would be causing it either, but you
> could enable the
> TOT (time out timer) on the radio to limit the time it
> would stay on
> transmit.
>
> 73 es cul - Keith VE7GDH
> --
> "I may be lost, but I know exactly where I am!"
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Okay I am going to admit I'm starting to get frustrated..  I went from
a Yaesu FT-1500 and TinyTrak to an Alinco DR-135 and the T2-135.  I
spent many hours when I got the radio and board getting stuff to work
finally I put it a side and today I got my 5 Volt Garmin 18 from GPS
City, it required me to program it to send NMEA, all good and tested
and no matter how I configure everything I still cant get it to work.
I got one transmission at some point that seemed to work, and Im not
sure why that was but I cant get it to do anything useful, even if I
set it to transmit every 10 seconds with no GPS fix required, it
doesn't key up every ten seconds just the first time you power the
radio up.

Has anyone remotely had the issues I am going through setting up there
tracker using the Alinco and T2-135?  Oh it works great with decoding
in APRS+SA by the way, I can't get it to work in WinAPRS yet, I can
switch between the programs and I have I swear the setting correct.
The other day it worked fine with WinAPRS.  I almost feel like I have
concept of how to configure this thing, even when I load the firmware
fresh I put my call in and restart the unit with the GPS plug in the
front , nothing...  ever...

Can anyone help me debug what I am doing wrong?  Its probably
something smaking me right in the face and I dont know it cause Im
proably not understanding something, a mode or something.  Im going
back to starting at the manual..

Ron

The most common thing that'll cause that is having SmartBeaconing turned
on.  Since you're (presumably) sitting still when you're testing on the
bench, it'll transmit at the low beacon rate, which might be every 15
minutes by default.

For testing, the first thing you should do is disable SmartBeaconing and
see if it makes a difference.

Scott

Ron N9QGS wrote:
>
>
> Okay I am going to admit I'm starting to get frustrated.. I went from
> a Yaesu FT-1500 and TinyTrak to an Alinco DR-135 and the T2-135. I
> spent many hours when I got the radio and board getting stuff to work
> finally I put it a side and today I got my 5 Volt Garmin 18 from GPS
> City, it required me to program it to send NMEA, all good and tested
> and no matter how I configure everything I still cant get it to work.
> I got one transmission at some point that seemed to work, and Im not
> sure why that was but I cant get it to do anything useful, even if I
> set it to transmit every 10 seconds with no GPS fix required, it
> doesn't key up every ten seconds just the first time you power the
> radio up.
>
> Has anyone remotely had the issues I am going through setting up there
> tracker using the Alinco and T2-135? Oh it works great with decoding
> in APRS+SA by the way, I can't get it to work in WinAPRS yet, I can
> switch between the programs and I have I swear the setting correct.
> The other day it worked fine with WinAPRS. I almost feel like I have
> concept of how to configure this thing, even when I load the firmware
> fresh I put my call in and restart the unit with the GPS plug in the
> front , nothing... ever...
>
> Can anyone help me debug what I am doing wrong? Its probably
> something smaking me right in the face and I dont know it cause Im
> proably not understanding something, a mode or something. Im going
> back to starting at the manual..
>
> Ron
>
>

I do have that unchecked...  and this is how it defaults when I reload
the firmware.  Is it possible that I can call you at some convenient
point and discuss this with you?  Ron



On Jul 31, 2008, at 12:14 AM, Scott Miller wrote:

> The most common thing that'll cause that is having SmartBeaconing
> turned
> on.  Since you're (presumably) sitting still when you're testing on
> the
> bench, it'll transmit at the low beacon rate, which might be every 15
> minutes by default.
>
> For testing, the first thing you should do is disable SmartBeaconing
> and
> see if it makes a difference.
>
> Scott
>
> Ron N9QGS wrote:
>>
>>
>> Okay I am going to admit I'm starting to get frustrated.. I went from
>> a Yaesu FT-1500 and TinyTrak to an Alinco DR-135 and the T2-135. I
>> spent many hours when I got the radio and board getting stuff to work
>> finally I put it a side and today I got my 5 Volt Garmin 18 from GPS
>> City, it required me to program it to send NMEA, all good and tested
>> and no matter how I configure everything I still cant get it to work.
>> I got one transmission at some point that seemed to work, and Im not
>> sure why that was but I cant get it to do anything useful, even if I
>> set it to transmit every 10 seconds with no GPS fix required, it
>> doesn't key up every ten seconds just the first time you power the
>> radio up.
>>
>> Has anyone remotely had the issues I am going through setting up
>> there
>> tracker using the Alinco and T2-135? Oh it works great with decoding
>> in APRS+SA by the way, I can't get it to work in WinAPRS yet, I can
>> switch between the programs and I have I swear the setting correct.
>> The other day it worked fine with WinAPRS. I almost feel like I have
>> concept of how to configure this thing, even when I load the firmware
>> fresh I put my call in and restart the unit with the GPS plug in the
>> front , nothing... ever...
>>
>> Can anyone help me debug what I am doing wrong? Its probably
>> something smaking me right in the face and I dont know it cause Im
>> proably not understanding something, a mode or something. Im going
>> back to starting at the manual..
>>
>> Ron
>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Possibly, but I'm not sure when will be convenient until roughly
Saturday at this rate.

Also make sure you've got all of the profile switching options
unchecked.  If you're using port B (the front panel jack) for the GPS,
keep the PC connected to the rear panel and use the POSITION command to
see if it's getting accurate data from the GPS.

If you can send me your configuration file (use the 'save' option in
otwincfg and send it to me off-list) I'll take a look at it.

Scott

Ron N9QGS wrote:
>
>
> I do have that unchecked... and this is how it defaults when I reload
> the firmware. Is it possible that I can call you at some convenient
> point and discuss this with you? Ron
>
> On Jul 31, 2008, at 12:14 AM, Scott Miller wrote:
>
>  > The most common thing that'll cause that is having SmartBeaconing
>  > turned
>  > on. Since you're (presumably) sitting still when you're testing on
>  > the
>  > bench, it'll transmit at the low beacon rate, which might be every 15
>  > minutes by default.
>  >
>  > For testing, the first thing you should do is disable SmartBeaconing
>  > and
>  > see if it makes a difference.
>  >
>  > Scott
>  >
>  > Ron N9QGS wrote:
>  >>
>  >>
>  >> Okay I am going to admit I'm starting to get frustrated.. I went from
>  >> a Yaesu FT-1500 and TinyTrak to an Alinco DR-135 and the T2-135. I
>  >> spent many hours when I got the radio and board getting stuff to work
>  >> finally I put it a side and today I got my 5 Volt Garmin 18 from GPS
>  >> City, it required me to program it to send NMEA, all good and tested
>  >> and no matter how I configure everything I still cant get it to work.
>  >> I got one transmission at some point that seemed to work, and Im not
>  >> sure why that was but I cant get it to do anything useful, even if I
>  >> set it to transmit every 10 seconds with no GPS fix required, it
>  >> doesn't key up every ten seconds just the first time you power the
>  >> radio up.
>  >>
>  >> Has anyone remotely had the issues I am going through setting up
>  >> there
>  >> tracker using the Alinco and T2-135? Oh it works great with decoding
>  >> in APRS+SA by the way, I can't get it to work in WinAPRS yet, I can
>  >> switch between the programs and I have I swear the setting correct.
>  >> The other day it worked fine with WinAPRS. I almost feel like I have
>  >> concept of how to configure this thing, even when I load the firmware
>  >> fresh I put my call in and restart the unit with the GPS plug in the
>  >> front , nothing... ever...
>  >>
>  >> Can anyone help me debug what I am doing wrong? Its probably
>  >> something smaking me right in the face and I dont know it cause Im
>  >> proably not understanding something, a mode or something. Im going
>  >> back to starting at the manual..
>  >>
>  >> Ron
>  >>
>  >>
>  >
>  >
>  > ------------------------------------
>  >
>  > Yahoo! Groups Links
>  >
>  >
>  >
>
>

You may have helped me, okay the front port is BMODE, I believe that
defaults to FLOW and A is AUTO.  Do I need to set AMODE and BMODE to
AUTO? for the tracker to work off the front port?

I did not think to check the position command.
On Jul 31, 2008, at 12:28 AM, Scott Miller wrote:

> Possibly, but I'm not sure when will be convenient until roughly
> Saturday at this rate.
>
> Also make sure you've got all of the profile switching options
> unchecked.  If you're using port B (the front panel jack) for the GPS,
> keep the PC connected to the rear panel and use the POSITION command
> to
> see if it's getting accurate data from the GPS.
>
> If you can send me your configuration file (use the 'save' option in
> otwincfg and send it to me off-list) I'll take a look at it.
>
> Scott
>
> Ron N9QGS wrote:
>>
>>
>> I do have that unchecked... and this is how it defaults when I reload
>> the firmware. Is it possible that I can call you at some convenient
>> point and discuss this with you? Ron
>>
>> On Jul 31, 2008, at 12:14 AM, Scott Miller wrote:
>>
>>> The most common thing that'll cause that is having SmartBeaconing
>>> turned
>>> on. Since you're (presumably) sitting still when you're testing on
>>> the
>>> bench, it'll transmit at the low beacon rate, which might be every
>>> 15
>>> minutes by default.
>>>
>>> For testing, the first thing you should do is disable SmartBeaconing
>>> and
>>> see if it makes a difference.
>>>
>>> Scott
>>>
>>> Ron N9QGS wrote:
>>>>
>>>>
>>>> Okay I am going to admit I'm starting to get frustrated.. I went
>>>> from
>>>> a Yaesu FT-1500 and TinyTrak to an Alinco DR-135 and the T2-135. I
>>>> spent many hours when I got the radio and board getting stuff to
>>>> work
>>>> finally I put it a side and today I got my 5 Volt Garmin 18 from
>>>> GPS
>>>> City, it required me to program it to send NMEA, all good and
>>>> tested
>>>> and no matter how I configure everything I still cant get it to
>>>> work.
>>>> I got one transmission at some point that seemed to work, and Im
>>>> not
>>>> sure why that was but I cant get it to do anything useful, even
>>>> if I
>>>> set it to transmit every 10 seconds with no GPS fix required, it
>>>> doesn't key up every ten seconds just the first time you power the
>>>> radio up.
>>>>
>>>> Has anyone remotely had the issues I am going through setting up
>>>> there
>>>> tracker using the Alinco and T2-135? Oh it works great with
>>>> decoding
>>>> in APRS+SA by the way, I can't get it to work in WinAPRS yet, I can
>>>> switch between the programs and I have I swear the setting correct.
>>>> The other day it worked fine with WinAPRS. I almost feel like I
>>>> have
>>>> concept of how to configure this thing, even when I load the
>>>> firmware
>>>> fresh I put my call in and restart the unit with the GPS plug in
>>>> the
>>>> front , nothing... ever...
>>>>
>>>> Can anyone help me debug what I am doing wrong? Its probably
>>>> something smaking me right in the face and I dont know it cause Im
>>>> proably not understanding something, a mode or something. Im going
>>>> back to starting at the manual..
>>>>
>>>> Ron
>>>>
>>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Yes, BMODE should be AUTO if you're using the front panel.  The T2-135
isn't even supposed to take FLOW as an option - I'm going to have to
check on that.  Also check that BBAUD is 4800, assuming you didn't
change the baud rate of the GPS.

AMODE can be something other than AUTO, but unless it's plugged into a
Garmin or PC running KISS, you should just leave it set to AUTO.

Scott

Ron N9QGS wrote:
>
>
> You may have helped me, okay the front port is BMODE, I believe that
> defaults to FLOW and A is AUTO. Do I need to set AMODE and BMODE to
> AUTO? for the tracker to work off the front port?
>
> I did not think to check the position command.
> On Jul 31, 2008, at 12:28 AM, Scott Miller wrote:
>
>  > Possibly, but I'm not sure when will be convenient until roughly
>  > Saturday at this rate.
>  >
>  > Also make sure you've got all of the profile switching options
>  > unchecked. If you're using port B (the front panel jack) for the GPS,
>  > keep the PC connected to the rear panel and use the POSITION command
>  > to
>  > see if it's getting accurate data from the GPS.
>  >
>  > If you can send me your configuration file (use the 'save' option in
>  > otwincfg and send it to me off-list) I'll take a look at it.
>  >
>  > Scott
>  >
>  > Ron N9QGS wrote:
>  >>
>  >>
>  >> I do have that unchecked... and this is how it defaults when I reload
>  >> the firmware. Is it possible that I can call you at some convenient
>  >> point and discuss this with you? Ron
>  >>
>  >> On Jul 31, 2008, at 12:14 AM, Scott Miller wrote:
>  >>
>  >>> The most common thing that'll cause that is having SmartBeaconing
>  >>> turned
>  >>> on. Since you're (presumably) sitting still when you're testing on
>  >>> the
>  >>> bench, it'll transmit at the low beacon rate, which might be every
>  >>> 15
>  >>> minutes by default.
>  >>>
>  >>> For testing, the first thing you should do is disable SmartBeaconing
>  >>> and
>  >>> see if it makes a difference.
>  >>>
>  >>> Scott
>  >>>
>  >>> Ron N9QGS wrote:
>  >>>>
>  >>>>
>  >>>> Okay I am going to admit I'm starting to get frustrated.. I went
>  >>>> from
>  >>>> a Yaesu FT-1500 and TinyTrak to an Alinco DR-135 and the T2-135. I
>  >>>> spent many hours when I got the radio and board getting stuff to
>  >>>> work
>  >>>> finally I put it a side and today I got my 5 Volt Garmin 18 from
>  >>>> GPS
>  >>>> City, it required me to program it to send NMEA, all good and
>  >>>> tested
>  >>>> and no matter how I configure everything I still cant get it to
>  >>>> work.
>  >>>> I got one transmission at some point that seemed to work, and Im
>  >>>> not
>  >>>> sure why that was but I cant get it to do anything useful, even
>  >>>> if I
>  >>>> set it to transmit every 10 seconds with no GPS fix required, it
>  >>>> doesn't key up every ten seconds just the first time you power the
>  >>>> radio up.
>  >>>>
>  >>>> Has anyone remotely had the issues I am going through setting up
>  >>>> there
>  >>>> tracker using the Alinco and T2-135? Oh it works great with
>  >>>> decoding
>  >>>> in APRS+SA by the way, I can't get it to work in WinAPRS yet, I can
>  >>>> switch between the programs and I have I swear the setting correct.
>  >>>> The other day it worked fine with WinAPRS. I almost feel like I
>  >>>> have
>  >>>> concept of how to configure this thing, even when I load the
>  >>>> firmware
>  >>>> fresh I put my call in and restart the unit with the GPS plug in
>  >>>> the
>  >>>> front , nothing... ever...
>  >>>>
>  >>>> Can anyone help me debug what I am doing wrong? Its probably
>  >>>> something smaking me right in the face and I dont know it cause Im
>  >>>> proably not understanding something, a mode or something. Im going
>  >>>> back to starting at the manual..
>  >>>>
>  >>>> Ron
>  >>>>
>  >>>>
>  >>>
>  >>>
>  >>> ------------------------------------
>  >>>
>  >>> Yahoo! Groups Links
>  >>>
>  >>>
>  >>>
>  >>
>  >>
>  >
>  >
>  > ------------------------------------
>  >
>  > Yahoo! Groups Links
>  >
>  >
>  >
>
>

what is the POSITION Command suppose to show me when I typed it it
just says GPS, I was maybe expecting coordinates?  Also should I get
some flashing light from the T2-135 board as it see NMEA data, Im not
seeing this.  No I left the GPS at 4800 baud sending nmea every second
and I selected two statements to send RMC and GGA I believe ,  Could
it be looking for some other NMEA sentence?

Ron


On Jul 31, 2008, at 12:36 AM, Scott Miller wrote:

> Yes, BMODE should be AUTO if you're using the front panel.  The T2-135
> isn't even supposed to take FLOW as an option - I'm going to have to
> check on that.  Also check that BBAUD is 4800, assuming you didn't
> change the baud rate of the GPS.
>
> AMODE can be something other than AUTO, but unless it's plugged into a
> Garmin or PC running KISS, you should just leave it set to AUTO.
>
> Scott
>
> Ron N9QGS wrote:
>>
>>
>> You may have helped me, okay the front port is BMODE, I believe that
>> defaults to FLOW and A is AUTO. Do I need to set AMODE and BMODE to
>> AUTO? for the tracker to work off the front port?
>>
>> I did not think to check the position command.
>> On Jul 31, 2008, at 12:28 AM, Scott Miller wrote:
>>
>>> Possibly, but I'm not sure when will be convenient until roughly
>>> Saturday at this rate.
>>>
>>> Also make sure you've got all of the profile switching options
>>> unchecked. If you're using port B (the front panel jack) for the
>>> GPS,
>>> keep the PC connected to the rear panel and use the POSITION command
>>> to
>>> see if it's getting accurate data from the GPS.
>>>
>>> If you can send me your configuration file (use the 'save' option in
>>> otwincfg and send it to me off-list) I'll take a look at it.
>>>
>>> Scott
>>>
>>> Ron N9QGS wrote:
>>>>
>>>>
>>>> I do have that unchecked... and this is how it defaults when I
>>>> reload
>>>> the firmware. Is it possible that I can call you at some convenient
>>>> point and discuss this with you? Ron
>>>>
>>>> On Jul 31, 2008, at 12:14 AM, Scott Miller wrote:
>>>>
>>>>> The most common thing that'll cause that is having SmartBeaconing
>>>>> turned
>>>>> on. Since you're (presumably) sitting still when you're testing on
>>>>> the
>>>>> bench, it'll transmit at the low beacon rate, which might be every
>>>>> 15
>>>>> minutes by default.
>>>>>
>>>>> For testing, the first thing you should do is disable
>>>>> SmartBeaconing
>>>>> and
>>>>> see if it makes a difference.
>>>>>
>>>>> Scott
>>>>>
>>>>> Ron N9QGS wrote:
>>>>>>
>>>>>>
>>>>>> Okay I am going to admit I'm starting to get frustrated.. I went
>>>>>> from
>>>>>> a Yaesu FT-1500 and TinyTrak to an Alinco DR-135 and the
>>>>>> T2-135. I
>>>>>> spent many hours when I got the radio and board getting stuff to
>>>>>> work
>>>>>> finally I put it a side and today I got my 5 Volt Garmin 18 from
>>>>>> GPS
>>>>>> City, it required me to program it to send NMEA, all good and
>>>>>> tested
>>>>>> and no matter how I configure everything I still cant get it to
>>>>>> work.
>>>>>> I got one transmission at some point that seemed to work, and Im
>>>>>> not
>>>>>> sure why that was but I cant get it to do anything useful, even
>>>>>> if I
>>>>>> set it to transmit every 10 seconds with no GPS fix required, it
>>>>>> doesn't key up every ten seconds just the first time you power
>>>>>> the
>>>>>> radio up.
>>>>>>
>>>>>> Has anyone remotely had the issues I am going through setting up
>>>>>> there
>>>>>> tracker using the Alinco and T2-135? Oh it works great with
>>>>>> decoding
>>>>>> in APRS+SA by the way, I can't get it to work in WinAPRS yet, I
>>>>>> can
>>>>>> switch between the programs and I have I swear the setting
>>>>>> correct.
>>>>>> The other day it worked fine with WinAPRS. I almost feel like I
>>>>>> have
>>>>>> concept of how to configure this thing, even when I load the
>>>>>> firmware
>>>>>> fresh I put my call in and restart the unit with the GPS plug in
>>>>>> the
>>>>>> front , nothing... ever...
>>>>>>
>>>>>> Can anyone help me debug what I am doing wrong? Its probably
>>>>>> something smaking me right in the face and I dont know it cause
>>>>>> Im
>>>>>> proably not understanding something, a mode or something. Im
>>>>>> going
>>>>>> back to starting at the manual..
>>>>>>
>>>>>> Ron
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------
>>>>>
>>>>> Yahoo! Groups Links
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

POSITION will report GPS followed by the coordinates if it has a valid
fix.  GPS just means it's set to use the GPS, but isn't getting a valid fix.

RMC and GGA are the two you need.  It'll take GLL, but there's no need
for it if you have either of the other two.

Can you hear a faint noise every second as it sends data?  Most DR-135s
seem to have an audio crosstalk problem and you can hear the GPS data on
the speaker.  Are you sure the GPS is wired correctly?  Off the top of
my head, I think it should be white -> tip, red -> ring, black -> sleeve
for the GPS 18 LVC.

Hmm... the power output on the DR-135 isn't quite 5 volts.  I wonder if
that might be marginal for the GPS 18.  I've wired a few that way, but
it's not nearly as common as the SiRF receivers (Deluo or ADS-GM1) and
if a certain percentage don't like that voltage, I might not have seen a
problem yet.  If you're able, it probably wouldn't hurt to try hooking
it up to an external 5 volt supply to rule out that as a problem.

Scott

Ron N9QGS wrote:
>
>
> what is the POSITION Command suppose to show me when I typed it it
> just says GPS, I was maybe expecting coordinates? Also should I get
> some flashing light from the T2-135 board as it see NMEA data, Im not
> seeing this. No I left the GPS at 4800 baud sending nmea every second
> and I selected two statements to send RMC and GGA I believe , Could
> it be looking for some other NMEA sentence?
>
> Ron
>
> On Jul 31, 2008, at 12:36 AM, Scott Miller wrote:
>
>  > Yes, BMODE should be AUTO if you're using the front panel. The T2-135
>  > isn't even supposed to take FLOW as an option - I'm going to have to
>  > check on that. Also check that BBAUD is 4800, assuming you didn't
>  > change the baud rate of the GPS.
>  >
>  > AMODE can be something other than AUTO, but unless it's plugged into a
>  > Garmin or PC running KISS, you should just leave it set to AUTO.
>  >
>  > Scott
>  >
>  > Ron N9QGS wrote:
>  >>
>  >>
>  >> You may have helped me, okay the front port is BMODE, I believe that
>  >> defaults to FLOW and A is AUTO. Do I need to set AMODE and BMODE to
>  >> AUTO? for the tracker to work off the front port?
>  >>
>  >> I did not think to check the position command.
>  >> On Jul 31, 2008, at 12:28 AM, Scott Miller wrote:
>  >>
>  >>> Possibly, but I'm not sure when will be convenient until roughly
>  >>> Saturday at this rate.
>  >>>
>  >>> Also make sure you've got all of the profile switching options
>  >>> unchecked. If you're using port B (the front panel jack) for the
>  >>> GPS,
>  >>> keep the PC connected to the rear panel and use the POSITION command
>  >>> to
>  >>> see if it's getting accurate data from the GPS.
>  >>>
>  >>> If you can send me your configuration file (use the 'save' option in
>  >>> otwincfg and send it to me off-list) I'll take a look at it.
>  >>>
>  >>> Scott
>  >>>
>  >>> Ron N9QGS wrote:
>  >>>>
>  >>>>
>  >>>> I do have that unchecked... and this is how it defaults when I
>  >>>> reload
>  >>>> the firmware. Is it possible that I can call you at some convenient
>  >>>> point and discuss this with you? Ron
>  >>>>
>  >>>> On Jul 31, 2008, at 12:14 AM, Scott Miller wrote:
>  >>>>
>  >>>>> The most common thing that'll cause that is having SmartBeaconing
>  >>>>> turned
>  >>>>> on. Since you're (presumably) sitting still when you're testing on
>  >>>>> the
>  >>>>> bench, it'll transmit at the low beacon rate, which might be every
>  >>>>> 15
>  >>>>> minutes by default.
>  >>>>>
>  >>>>> For testing, the first thing you should do is disable
>  >>>>> SmartBeaconing
>  >>>>> and
>  >>>>> see if it makes a difference.
>  >>>>>
>  >>>>> Scott
>  >>>>>
>  >>>>> Ron N9QGS wrote:
>  >>>>>>
>  >>>>>>
>  >>>>>> Okay I am going to admit I'm starting to get frustrated.. I went
>  >>>>>> from
>  >>>>>> a Yaesu FT-1500 and TinyTrak to an Alinco DR-135 and the
>  >>>>>> T2-135. I
>  >>>>>> spent many hours when I got the radio and board getting stuff to
>  >>>>>> work
>  >>>>>> finally I put it a side and today I got my 5 Volt Garmin 18 from
>  >>>>>> GPS
>  >>>>>> City, it required me to program it to send NMEA, all good and
>  >>>>>> tested
>  >>>>>> and no matter how I configure everything I still cant get it to
>  >>>>>> work.
>  >>>>>> I got one transmission at some point that seemed to work, and Im
>  >>>>>> not
>  >>>>>> sure why that was but I cant get it to do anything useful, even
>  >>>>>> if I
>  >>>>>> set it to transmit every 10 seconds with no GPS fix required, it
>  >>>>>> doesn't key up every ten seconds just the first time you power
>  >>>>>> the
>  >>>>>> radio up.
>  >>>>>>
>  >>>>>> Has anyone remotely had the issues I am going through setting up
>  >>>>>> there
>  >>>>>> tracker using the Alinco and T2-135? Oh it works great with
>  >>>>>> decoding
>  >>>>>> in APRS+SA by the way, I can't get it to work in WinAPRS yet, I
>  >>>>>> can
>  >>>>>> switch between the programs and I have I swear the setting
>  >>>>>> correct.
>  >>>>>> The other day it worked fine with WinAPRS. I almost feel like I
>  >>>>>> have
>  >>>>>> concept of how to configure this thing, even when I load the
>  >>>>>> firmware
>  >>>>>> fresh I put my call in and restart the unit with the GPS plug in
>  >>>>>> the
>  >>>>>> front , nothing... ever...
>  >>>>>>
>  >>>>>> Can anyone help me debug what I am doing wrong? Its probably
>  >>>>>> something smaking me right in the face and I dont know it cause
>  >>>>>> Im
>  >>>>>> proably not understanding something, a mode or something. Im
>  >>>>>> going
>  >>>>>> back to starting at the manual..
>  >>>>>>
>  >>>>>> Ron
>  >>>>>>
>  >>>>>>
>  >>>>>
>  >>>>>
>  >>>>> ------------------------------------
>  >>>>>
>  >>>>> Yahoo! Groups Links
>  >>>>>
>  >>>>>
>  >>>>>
>  >>>>
>  >>>>
>  >>>
>  >>>
>  >>> ------------------------------------
>  >>>
>  >>> Yahoo! Groups Links
>  >>>
>  >>>
>  >>>
>  >>
>  >>
>  >
>  >
>  > ------------------------------------
>  >
>  > Yahoo! Groups Links
>  >
>  >
>  >
>
>

Thank you Scott,  It seems that I should lean back to inspecting the
GPS and wiring.  It doesnt hurt for me to concentrate in that area.  I
will report back tomorrow.  Have a great evening.   I did use the
voltage from the Alinco front port to power the GPS as the 2nd ground
and data wires were wired to PC DB-9 and the GPS functioned fine under
those conditions.  voltage also is 4.65v on the alinco which is well
within operating spec of the 18.  But let me go play around with it.
I have ways of testing this further.  I will report back tomorrow


Ron

On Jul 31, 2008, at 1:01 AM, Scott Miller wrote:

> POSITION will report GPS followed by the coordinates if it has a valid
> fix.  GPS just means it's set to use the GPS, but isn't getting a
> valid fix.
>
> RMC and GGA are the two you need.  It'll take GLL, but there's no need
> for it if you have either of the other two.
>
> Can you hear a faint noise every second as it sends data?  Most
> DR-135s
> seem to have an audio crosstalk problem and you can hear the GPS
> data on
> the speaker.  Are you sure the GPS is wired correctly?  Off the top of
> my head, I think it should be white -> tip, red -> ring, black ->
> sleeve
> for the GPS 18 LVC.
>
> Hmm... the power output on the DR-135 isn't quite 5 volts.  I wonder
> if
> that might be marginal for the GPS 18.  I've wired a few that way, but
> it's not nearly as common as the SiRF receivers (Deluo or ADS-GM1) and
> if a certain percentage don't like that voltage, I might not have
> seen a
> problem yet.  If you're able, it probably wouldn't hurt to try hooking
> it up to an external 5 volt supply to rule out that as a problem.
>
> Scott
>
> Ron N9QGS wrote:
>>
>>
>> what is the POSITION Command suppose to show me when I typed it it
>> just says GPS, I was maybe expecting coordinates? Also should I get
>> some flashing light from the T2-135 board as it see NMEA data, Im not
>> seeing this. No I left the GPS at 4800 baud sending nmea every second
>> and I selected two statements to send RMC and GGA I believe , Could
>> it be looking for some other NMEA sentence?
>>
>> Ron
>>
>> On Jul 31, 2008, at 12:36 AM, Scott Miller wrote:
>>
>>> Yes, BMODE should be AUTO if you're using the front panel. The
>>> T2-135
>>> isn't even supposed to take FLOW as an option - I'm going to have to
>>> check on that. Also check that BBAUD is 4800, assuming you didn't
>>> change the baud rate of the GPS.
>>>
>>> AMODE can be something other than AUTO, but unless it's plugged
>>> into a
>>> Garmin or PC running KISS, you should just leave it set to AUTO.
>>>
>>> Scott
>>>
>>> Ron N9QGS wrote:
>>>>
>>>>
>>>> You may have helped me, okay the front port is BMODE, I believe
>>>> that
>>>> defaults to FLOW and A is AUTO. Do I need to set AMODE and BMODE to
>>>> AUTO? for the tracker to work off the front port?
>>>>
>>>> I did not think to check the position command.
>>>> On Jul 31, 2008, at 12:28 AM, Scott Miller wrote:
>>>>
>>>>> Possibly, but I'm not sure when will be convenient until roughly
>>>>> Saturday at this rate.
>>>>>
>>>>> Also make sure you've got all of the profile switching options
>>>>> unchecked. If you're using port B (the front panel jack) for the
>>>>> GPS,
>>>>> keep the PC connected to the rear panel and use the POSITION
>>>>> command
>>>>> to
>>>>> see if it's getting accurate data from the GPS.
>>>>>
>>>>> If you can send me your configuration file (use the 'save'
>>>>> option in
>>>>> otwincfg and send it to me off-list) I'll take a look at it.
>>>>>
>>>>> Scott
>>>>>
>>>>> Ron N9QGS wrote:
>>>>>>
>>>>>>
>>>>>> I do have that unchecked... and this is how it defaults when I
>>>>>> reload
>>>>>> the firmware. Is it possible that I can call you at some
>>>>>> convenient
>>>>>> point and discuss this with you? Ron
>>>>>>
>>>>>> On Jul 31, 2008, at 12:14 AM, Scott Miller wrote:
>>>>>>
>>>>>>> The most common thing that'll cause that is having
>>>>>>> SmartBeaconing
>>>>>>> turned
>>>>>>> on. Since you're (presumably) sitting still when you're
>>>>>>> testing on
>>>>>>> the
>>>>>>> bench, it'll transmit at the low beacon rate, which might be
>>>>>>> every
>>>>>>> 15
>>>>>>> minutes by default.
>>>>>>>
>>>>>>> For testing, the first thing you should do is disable
>>>>>>> SmartBeaconing
>>>>>>> and
>>>>>>> see if it makes a difference.
>>>>>>>
>>>>>>> Scott
>>>>>>>
>>>>>>> Ron N9QGS wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Okay I am going to admit I'm starting to get frustrated.. I
>>>>>>>> went
>>>>>>>> from
>>>>>>>> a Yaesu FT-1500 and TinyTrak to an Alinco DR-135 and the
>>>>>>>> T2-135. I
>>>>>>>> spent many hours when I got the radio and board getting stuff
>>>>>>>> to
>>>>>>>> work
>>>>>>>> finally I put it a side and today I got my 5 Volt Garmin 18
>>>>>>>> from
>>>>>>>> GPS
>>>>>>>> City, it required me to program it to send NMEA, all good and
>>>>>>>> tested
>>>>>>>> and no matter how I configure everything I still cant get it to
>>>>>>>> work.
>>>>>>>> I got one transmission at some point that seemed to work, and
>>>>>>>> Im
>>>>>>>> not
>>>>>>>> sure why that was but I cant get it to do anything useful, even
>>>>>>>> if I
>>>>>>>> set it to transmit every 10 seconds with no GPS fix required,
>>>>>>>> it
>>>>>>>> doesn't key up every ten seconds just the first time you power
>>>>>>>> the
>>>>>>>> radio up.
>>>>>>>>
>>>>>>>> Has anyone remotely had the issues I am going through setting
>>>>>>>> up
>>>>>>>> there
>>>>>>>> tracker using the Alinco and T2-135? Oh it works great with
>>>>>>>> decoding
>>>>>>>> in APRS+SA by the way, I can't get it to work in WinAPRS yet, I
>>>>>>>> can
>>>>>>>> switch between the programs and I have I swear the setting
>>>>>>>> correct.
>>>>>>>> The other day it worked fine with WinAPRS. I almost feel like I
>>>>>>>> have
>>>>>>>> concept of how to configure this thing, even when I load the
>>>>>>>> firmware
>>>>>>>> fresh I put my call in and restart the unit with the GPS plug
>>>>>>>> in
>>>>>>>> the
>>>>>>>> front , nothing... ever...
>>>>>>>>
>>>>>>>> Can anyone help me debug what I am doing wrong? Its probably
>>>>>>>> something smaking me right in the face and I dont know it cause
>>>>>>>> Im
>>>>>>>> proably not understanding something, a mode or something. Im
>>>>>>>> going
>>>>>>>> back to starting at the manual..
>>>>>>>>
>>>>>>>> Ron
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------
>>>>>>>
>>>>>>> Yahoo! Groups Links
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------
>>>>>
>>>>> Yahoo! Groups Links
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

> 1. first off regardless if GPS is hooked p or not, when I issue the
> ABAUD GARMIN command I get a foreign character on the screen and I no
> longer have any functionality of the T2-135 until I erase and load the
> firmware back in. What is the proper way to exit Garmin mode so that I

That's the expected behavior - it switches to 9600 baud and starts
trying to speak Garmin.  I think the ctrl-C exit function has been
disabled in the beta version because it was getting false hits
sometimes.  Once I'm sure I've got a good fix for it, I'll re-enable it.
   I figured it was better to put up with some inconvenience when
switching modes than to have it just stop working sometimes.

To exit, you can always turn the radio on AFTER you've started the
configuration program and clicked 'connect'.  It always starts the
bootloader and looks for the config program before switching port modes.

> 2. When I put it in GARMIN mode, I checked symbols, etc. I have symbols
> loaded, I am not getting any icons or waypoints being created on my
> device, and I am not sure how to confirm this, but I don't think the
> unit is getting GPS data either from the unit. With the smart tracker
> options set there is nothing transmitting.

Even if you don't have the custom symbols loaded, you should at least
get a generic symbol.  Sounds like it's not talking to the GPS properly.
   It's a little hard to debug on the T2-135 since you don't have another
port that you can get a serial console on.

I'd say pull the GPS cable from the 60C and check the data in line (the
one from the T2-135) with an oscilloscope (or logic probe, or voltmeter)
and see if you're getting a burst of data every few seconds.  That'll
tell you if it's trying to talk to the Garmin.

Oh, and of course you'll need to make sure the 60C is set to Garmin
protocol in the interface menu.  I don't think the 60C will let you
change the baud rate, but if it does, it's 9600.

Scott

> hooked up. :-( However if I switch the GPS to NMEA the green LED light
> flashes every
> second, so I think I figured out that you can send NMEA in the front or
> back? I was only

NMEA will work in front or back, Garmin in the back only.  Sounds like
you might be running into the profile switching bug, where you're
setting AMODE to Garmin while the PC is plugged in, and then it's
switching back when it's disconnected.  Make sure all profile switching
options are off.

Scott

Im going to play around more with it in the morning, but I easily
confirmed I do hear the nmea over the speaker when I unplugged the
head phone jack just to mute the popping as others suggested.  I have
other GPS and test leads that I can easily feed valid nmea into the
front port and try to get a coordinates in the POSITION field and
different behavior.  You left me with enough good information to even
try debugging the 60C again as well...  Ive got all day tomorrow to
make this work. :-)

Ron



On Jul 31, 2008, at 1:10 AM, Scott Miller wrote:

>> hooked up. :-( However if I switch the GPS to NMEA the green LED
>> light
>> flashes every
>> second, so I think I figured out that you can send NMEA in the
>> front or
>> back? I was only
>
> NMEA will work in front or back, Garmin in the back only.  Sounds like
> you might be running into the profile switching bug, where you're
> setting AMODE to Garmin while the PC is plugged in, and then it's
> switching back when it's disconnected.  Make sure all profile
> switching
> options are off.
>
> Scott
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Sorry for not getting the 60C information out earlier... as always, I'm
fighting an email backlog.  I've got a lot of notes on things that need
to be documented, so hopefully that'll help, if I ever get time to work
on it.

Scott

Ron N9QGS wrote:
>
>
> Im going to play around more with it in the morning, but I easily
> confirmed I do hear the nmea over the speaker when I unplugged the
> head phone jack just to mute the popping as others suggested. I have
> other GPS and test leads that I can easily feed valid nmea into the
> front port and try to get a coordinates in the POSITION field and
> different behavior. You left me with enough good information to even
> try debugging the 60C again as well... Ive got all day tomorrow to
> make this work. :-)
>
> Ron
>
> On Jul 31, 2008, at 1:10 AM, Scott Miller wrote:
>
>  >> hooked up. :-( However if I switch the GPS to NMEA the green LED
>  >> light
>  >> flashes every
>  >> second, so I think I figured out that you can send NMEA in the
>  >> front or
>  >> back? I was only
>  >
>  > NMEA will work in front or back, Garmin in the back only. Sounds like
>  > you might be running into the profile switching bug, where you're
>  > setting AMODE to Garmin while the PC is plugged in, and then it's
>  > switching back when it's disconnected. Make sure all profile
>  > switching
>  > options are off.
>  >
>  > Scott
>  >
>  >
>  > ------------------------------------
>  >
>  > Yahoo! Groups Links
>  >
>  >
>  >
>
>