That's for the OT1+.  On the OT2m you'd use CMD POWER ON, CMD POWER OFF,
or CMD PULSE xx.

Scott

Mike Zwingl oe3mzc wrote:
> would this work with an OT1+ or with an OT2m only??
>
> ----- Original Message -----
> From: "Scott Miller" <scott@...>
> To: <opentracker@yahoogroups.com>
> Sent: Tuesday, November 24, 2009 6:32 PM
> Subject: Re: [opentracker] Controlling PTB2 pin remotely
>
>
>> Try sending it an APRS message starting with ON or OFF.  That should
>> toggle the power control pin.  Maybe.  It's been a long time since I
>> tested it.
>>
>> Scott
>>
>> Christopher Snell wrote:
>>>
>>>
>>> Hi,
>>>
>>> How would I go about toggling the PTB2 pin remotely? I would like to
>>> use this to trigger a cutdown mechanism for a balloon.
>>>
>>> Thanks,
>>>
>>> Chris
>>>
>>>
>>
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Hoping that there's a way to do it with the OT1+.  Maybe with a firmware mod?

I'd originally planned to send my OT2m up with my balloon but I'm
leaning towards the OT1+ SMT because of weight savings.

Chris

On Wed, Nov 25, 2009 at 9:14 AM, Mike Zwingl oe3mzc <oe3mzc@...> wrote:
> would this work with an OT1+ or with an OT2m only??
>
> ----- Original Message -----
> From: "Scott Miller" <scott@...>
> To: <opentracker@yahoogroups.com>
> Sent: Tuesday, November 24, 2009 6:32 PM
> Subject: Re: [opentracker] Controlling PTB2 pin remotely
>
>
>> Try sending it an APRS message starting with ON or OFF.  That should
>> toggle the power control pin.  Maybe.  It's been a long time since I
>> tested it.
>>
>> Scott
>>
>> Christopher Snell wrote:
>>>
>>>
>>> Hi,
>>>
>>> How would I go about toggling the PTB2 pin remotely? I would like to
>>> use this to trigger a cutdown mechanism for a balloon.
>>>
>>> Thanks,
>>>
>>> Chris
>>>
>>>
>>
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

would this work with an OT1+ or with an OT2m only??

----- Original Message -----
From: "Scott Miller" <scott@...>
To: <opentracker@yahoogroups.com>
Sent: Tuesday, November 24, 2009 6:32 PM
Subject: Re: [opentracker] Controlling PTB2 pin remotely


> Try sending it an APRS message starting with ON or OFF.  That should
> toggle the power control pin.  Maybe.  It's been a long time since I
> tested it.
>
> Scott
>
> Christopher Snell wrote:
>>
>>
>> Hi,
>>
>> How would I go about toggling the PTB2 pin remotely? I would like to
>> use this to trigger a cutdown mechanism for a balloon.
>>
>> Thanks,
>>
>> Chris
>>
>>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Hi Keith..

The OT+ Manual says that 2 blinking red leds indicate no GPS lock or invalid
GPS data.

The OT+ is currently running in fixed mode without the GPS attached and the
SSID I have setup for fixed is vk2crt
(http://www.findu.com/cgi-bin/find.cgi?call=VK2CRT) . Normally I use a
Kenwood TMD700 with a Garmin Nuvi 350 attached with an SSID of VK2CRT-9
(indicating mobile).

The GPS35-PC does have a configuration program, and it reports no fix.
Thanks for software tip on "VisuapGPS" Looks good!

I have tried a more sensitive GPS (yes a third one) and it struggled to get
a fix from the same location as the other to Garmin units.

I'll just have to pull the radio, OT+, and GPS out off the office and set it
up in the car and see what I get. I think it will fire up normally.

Many thanks and 73

Col
(aka VK2CRT)



-----Original Message-----
From: opentracker@yahoogroups.com [mailto:opentracker@yahoogroups.com] On
Behalf Of Keith VE7GDH
Sent: Tuesday, 24 November 2009 11:04 AM
To: opentracker@yahoogroups.com
Subject: Re: [opentracker] OT1+ and Garmin GPS35-PC setup

Col VK2CRT wrote...

> 1st was the GPS35-PC, and it still is not sending NEMA data to the
> OT+, A double flashing red led tells me so. (according to the manual)

Actualy, that's NMEA. Could could you make up an adapter so you could
p;ower up one of the GPS receivers and feed it to a PC running a
terminal program, or better yet, something like VisuapGPS?

> I then tried a Garmin Streetpilot III and still go the flashing red
> led. I took the SPIII out to the car and got a satallite lock in
> seconds. So I now think that it's the location I am testing the OT+
> in. I am in an office, between two tallish buildings in Sydney. I have
> previously got lock on the GPS unit's I test so I sort of didn't think
> it could be the location.

It's certainly possible that the office location just isn't seeing
enough of the sky to get a lock.

> I have reset the comments / status to every 5 packets and with the
> transmission rate set to 30 minutes I think that  works out to be
> every 2.5 hours.

That certainly won't overwhelm the local RF network! Don't forget - you
can temporarily enter a fixed position for testing. Ultimately, you will
want to get the GPS receiver going though. Right now, VK2CRT-9 hasn't
been heard for nearly 4 days.

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



------------------------------------

Yahoo! Groups Links

Try sending it an APRS message starting with ON or OFF.  That should
toggle the power control pin.  Maybe.  It's been a long time since I
tested it.

Scott

Christopher Snell wrote:
>
>
> Hi,
>
> How would I go about toggling the PTB2 pin remotely? I would like to
> use this to trigger a cutdown mechanism for a balloon.
>
> Thanks,
>
> Chris
>
>

Col VK2CRT wrote...

> 1st was the GPS35-PC, and it still is not sending NEMA data to the
> OT+, A double flashing red led tells me so. (according to the manual)

Actualy, that's NMEA. Could could you make up an adapter so you could
p;ower up one of the GPS receivers and feed it to a PC running a
terminal program, or better yet, something like VisuapGPS?

> I then tried a Garmin Streetpilot III and still go the flashing red
> led. I took the SPIII out to the car and got a satallite lock in
> seconds. So I now think that it's the location I am testing the OT+
> in. I am in an office, between two tallish buildings in Sydney. I have
> previously got lock on the GPS unit's I test so I sort of didn't think
> it could be the location.

It's certainly possible that the office location just isn't seeing
enough of the sky to get a lock.

> I have reset the comments / status to every 5 packets and with the
> transmission rate set to 30 minutes I think that  works out to be
> every 2.5 hours.

That certainly won't overwhelm the local RF network! Don't forget - you
can temporarily enter a fixed position for testing. Ultimately, you will
want to get the GPS receiver going though. Right now, VK2CRT-9 hasn't
been heard for nearly 4 days.

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

Sorry for the off-topic post, but this is the most likely place I could
think to find something on short notice.  And to keep it more on-topic,
I'll be happy to send free trackers to anyone who can help out with this.

My parents (KK6AD and KB6VAA) made it as far as Morgantown, West
Virginia on their way to Iowa for Thanksgiving, pulling a 29' fifth
wheel, when they blew the engine on their truck (which incidentally
served them for 18 solid months of RVing with hardly a hiccup).
Replacement is going to take several days.  My uncle in Iowa may very
well not be around next holiday season, so this is an important trip for
them.

My sister and I are hoping to find someone in the area who's got a 5th
wheel tow rig they can rent out for several days, that they can deliver
to Morgantown.  Today, if possible.  A 1-ton truck with 5th wheel hitch
is not something you usually find at Hertz, though.  I'll be the one
paying - an early Christmas present for my parents if we can find something.

If you've got something available or know someone who does, let me know.

Thanks,

Scott
N1VG

Hi,

How would I go about toggling the PTB2 pin remotely?  I would like to
use this to trigger a cutdown mechanism for a balloon.

Thanks,

Chris

Someone as a link to download the Deluo GPS Diagnostics 1.7  ?

The Deluo site ( support ) seem to have error on is page

Thanks

Thank You
That worked the other one didn't, and the ones I compiled didn't work either. 
Now all I have to do is get this into the I2CTX and 9600NMEA on the SMT board to
work together and I should be set.


--- In opentracker@yahoogroups.com, Scott Miller <scott@...> wrote:
>
> So it turns out the 9600 baud firmware was out there on the website
> already, it just wasn't in the index file.  I just uploaded a new
> version that's not very well tested, but it seemed to be working at 9600
> baud.  Just hit the 'web' button, it's the last one on the list.
>
> Scott
>
> epic_audio wrote:
> >
> >
> > Ok I found the 9600 setting but confused about the "#ifndef BAUD9600" do
> > i need to add a BAUD=9600 at top of software?
> > I found the 9600baud.s19 file on your server and loaded that and it
> > didn't work, unit just blinked red(mabey 4hz)and sometimes after
> > transmit it flashed fast green then returned to the blinky red. GPS had
> > a 3D fix confirmed by flashing green led and computer.
> > Is there a way to send a serial command(initialization string) at start
> > of program to change baud rate each time it powers on and every so often
> > to make sure gps is at 4800? The unit I have does 4800 but it is only
> > ROM based and no way to save settings. If I hook to computer and change
> > to 4800 and then plug back into open tracker I am good to go, until I
> > loose power. I also thought about programming a small PIC chip to send
> > serial commands to change baud rate after power on.
> > I found the I2CTX and I will try that later this weekend when I recieve
> > my MX146.
> > Thanks you have been a great help with support.
> > --- In opentracker@yahoogroups.com
> > <mailto:opentracker%40yahoogroups.com>, Scott Miller <scott@> wrote:
> >  >
> >  > The baud rate setting should be in hardware.c, and to compile in the
> >  > MX146 support you need to change the compile target to I2CTX.
> >  >
> >  > It's been a long time since I've tried 9600 baud, though, and I can't
> >  > promise it'll work. It may not be buffering enough data to avoid
> >  > missing characters while it's processing stuff.
> >  >
> >  > Scott
> >  >
> >  > epic_audio wrote:
> >  > >
> >  > >
> >  > > I am trying to hook up a gps that only has 9600NMEA output, I am so
> >  > > confused with the source code, edit this, compile that. I was also
> >  > > wondering what I need to do(firmware/software) for MX146 transmitter
> >  > > support on the SMT.
> >  > > Thanks Jason
> >  > >
> >  > >
> >  >
> >
> >
>

So it turns out the 9600 baud firmware was out there on the website
already, it just wasn't in the index file.  I just uploaded a new
version that's not very well tested, but it seemed to be working at 9600
baud.  Just hit the 'web' button, it's the last one on the list.

Scott

epic_audio wrote:
>
>
> Ok I found the 9600 setting but confused about the "#ifndef BAUD9600" do
> i need to add a BAUD=9600 at top of software?
> I found the 9600baud.s19 file on your server and loaded that and it
> didn't work, unit just blinked red(mabey 4hz)and sometimes after
> transmit it flashed fast green then returned to the blinky red. GPS had
> a 3D fix confirmed by flashing green led and computer.
> Is there a way to send a serial command(initialization string) at start
> of program to change baud rate each time it powers on and every so often
> to make sure gps is at 4800? The unit I have does 4800 but it is only
> ROM based and no way to save settings. If I hook to computer and change
> to 4800 and then plug back into open tracker I am good to go, until I
> loose power. I also thought about programming a small PIC chip to send
> serial commands to change baud rate after power on.
> I found the I2CTX and I will try that later this weekend when I recieve
> my MX146.
> Thanks you have been a great help with support.
> --- In opentracker@yahoogroups.com
> <mailto:opentracker%40yahoogroups.com>, Scott Miller <scott@...> wrote:
>  >
>  > The baud rate setting should be in hardware.c, and to compile in the
>  > MX146 support you need to change the compile target to I2CTX.
>  >
>  > It's been a long time since I've tried 9600 baud, though, and I can't
>  > promise it'll work. It may not be buffering enough data to avoid
>  > missing characters while it's processing stuff.
>  >
>  > Scott
>  >
>  > epic_audio wrote:
>  > >
>  > >
>  > > I am trying to hook up a gps that only has 9600NMEA output, I am so
>  > > confused with the source code, edit this, compile that. I was also
>  > > wondering what I need to do(firmware/software) for MX146 transmitter
>  > > support on the SMT.
>  > > Thanks Jason
>  > >
>  > >
>  >
>
>

Colin VK2CRT wrote...

> I have a OT1+ with a Garmin GPS35-PC and a Yaesu FT-1802M setup. I
> made my own cable and all seems to be working OK.

Did you ever get a reply? I couldn't see one.

> Should the Garmin GPS35-PC be setup to 4800 baud in NEMA or Garmin
> output? The reason I ask is that if I set it to NEMA output I get a
> flashing LED on the OT1+

Actually, that's NMEA. According to Garmin's site...

https://buy.garmin.com/shop/shop.do?pID=62

      All serial inputs on all versions are compatible with either
      true RS-232 or TTL/CMOS voltage levels. Port 1 uses
      NMEA 0183 data format. Port 2 transmits binary position
      and raw measurement data and receives RTCM SC-104
      differential corrections data, message types 1, 2, 3, and 9.
     **GPS35PC does not implement Port 2.

That takes care of that. The one you have outputs NMEA 0183.
According to the specs, the factory default is the usual 4800 bps.

http://www8.garmin.com/manuals/GPS35LPSeries_TechnicalSpecification.pdf

> I am getting mixed transmission times on the FT-1802M. What I mean by
> this is that sometimes it will transmit a short packet, less than a
> second. And at other times it will transmit for almost 6-10 seconds. I
> do have the OT1+ set to send some status text every 2 transmissions.
> Does this sound right?

The best way to see what is going on would be to listen with another
radio that was connected to a TNC and actually see what it decodes when
the OT1+ transmits. The long transmissions could be explained by the
long strings of garbage seen below.

> Here is a copy of the packets that are being transmitted... (From
http://aprs.fi/?c=raw&call=VK2CRT-9&limit=50)

2009-11-19 03:51:34 UTC:
VK2CRT-9>APOTC1,TCPIP*,qAS,vk2hl
:wÑdl<0x01>@p?©´kkïB»£¨<0x0b>|<0x09>BÇð?°<0x08>{à<0x08>Ij¬-3<0x12>Ç!?V<0x0f>
ä?<0x08>ä­??Px9<0x09>`ÓZá°Ü?<0x13><0x08>?²Éµ¥h<0x01><0x10><0x08><0x01>Û<0x08>´n1\
?<0x03>ßBXÎmÿ<<0x01>%aexl<0x09>aÇ7|!3%Ç<0x08>%?<0x0e><0x1e><0x0c>
[Unsupported packet format]

Obviously, not correct. Was RF perhaps getting into the OT1+ and
corrupting the tones, or was it happening elsewhere?

Also, why does TCPIP show up in the path? Was someone gating
it back out to RF again?

http://aprs.fi/?c=raw&call=VK2CRT-9&limit=1000

However, you seemed to have solved the original problem about 2009-11-19
04:24:45 UTC.

2009-11-19 04:13:26 UTC:
VK2CRT-9>APOTC1,VK2US-1,VK2RGL-1*,WIDE2-1,qAR,VK2ZEN-5
:(|- g _ J@ 'l( ! b 4 N T!, )d F a ^ K < > ` @ x > J [Unsupported packet
format]

2009-11-19 04:13:33 UTC:
VK2CRT-9>APOTC1,TCPIP*,qAS,vk2hl
:>NM Mitsubishi Pajero - ARB38B - In the Burbs

2009-11-19 04:13:33 UTC:
VK2CRT-9>APOTC1,VK2US-1*,WIDE2-2,qAR,VK2ZEN-5:>

2009-11-19 04:19:51 UTC:
VK2CRT-9>APOTC1,VK2US-1,VK2RTZ-1*,WIDE2-1,qAR,VK2ZEN-5
: ` W + , ) @ 4 D ~ d O !B@B C ! ;! w > c 4M i [Unsupported packet
format]

2009-11-19 04:24:45 UTC:
VK2CRT-9>APOTC1,VK2US-1*,WIDE2-2,qAR,VK2IN-5
:>NM Mitsubishi Pajero - ARB38B - In the Burbs

2009-11-19 04:24:45 UTC:
VK2CRT-9>APOTC1,VK2US-1*,WIDE2-2,qAR,VK2ZEN-5
:!3352.00S/15111.00E> 08.2V 28C

Regarding sending the following as status text...

NM Mitsubishi Pajero - ARB38B - In the Burbs

It is unchanging information. If you really feel you need to send it,
perhaps send it just every 10 (or more) transmissions. It will never
contain new information.

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

I think the reasoning was that some people want to use power control for
the GPS as well, and it needs to stay on until it gets a fix.  Ideally
it'd have two separate power control outputs... maybe in the next iteration.

The one that really drives me nuts is dealing with the low-voltage
inhibit.  The voltage will be OK until you turn the radio on with a low
battery, and then it drops below the threshold.  There's no easy way to
deal with it without adding some sort of retry delay or hysteresis
mechanism.

Scott

rds_6 wrote:
>
>
> One of the problems I've had with a competing tracker is that its power
> control leaves power applied to the radio indefinitely when (1) no valid
> GPS data is present or (2) during a "busy" indication. The second
> problem can be solved by tightening the radio's squelch setting enough
> that it is not overly sensitive for local RF conditions. However, the
> first problem has drained my car's battery on several occasions and can
> result from numerous causes, such as the GPS receiver losing power and
> not being manually turned on again, the GPS RS-232 connector working
> itself loose, or parking inside a parking garage that blocks GPS reception.
>
> Does the OT+'s Power Control feature prevent the radio from being
> powered up (or at least from staying on indefinitely) for lack of valid
> GPS data and for indefinite "busy" indication? Thanks.
>
>

Joseph G1XZL ZL2SCI wrote...

> Yes ok fine, considering the same as well looks an ok deal even at $75
> or so! wonder which part of Canada you are from. Spent time on the
> Prairies a long hot dusty summer on bucking combines etc etc lol ciao

I have three of the radios on the way for now and will order an OT2m
when in stock. I was only on the prairies once for a visit. Hot and
flat! I'm on the west coast, about as far as you can get from the
prairies without heading east. http://aprs.fi/VE7GDH

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

One of the problems I've had with a competing tracker is that its power control
leaves power applied to the radio indefinitely when (1) no valid GPS data is
present or (2) during a "busy" indication.  The second problem can be solved by
tightening the radio's squelch setting enough that it is not overly sensitive
for local RF conditions.  However, the first problem has drained my car's
battery on several occasions and can result from numerous causes, such as the
GPS receiver losing power and not being manually turned on again, the GPS RS-232
connector working itself loose, or parking inside a parking garage that blocks
GPS reception.

Does the OT+'s Power Control feature prevent the radio from being powered up (or
at least from staying on indefinitely) for lack of valid GPS data and for
indefinite "busy" indication?  Thanks.

I also find the post about searching for 6E1319 and about how it should occur
twice.
Replace 13 with one of the following:
> 12 - 9600 baud
tried and no luck, might be a buffer issue.
--- In opentracker@yahoogroups.com, "epic_audio" <epic_audio@...> wrote:
>
> Ok I found the 9600 setting but confused about the "#ifndef BAUD9600"  do i
need to add a BAUD=9600 at top of software?
> I found the 9600baud.s19 file on your server and loaded that and it didn't
work, unit just blinked red(mabey 4hz)and sometimes after transmit it flashed
fast green then returned to the blinky red.  GPS had a 3D fix confirmed by
flashing green led and computer.
> Is there a way to send a serial command(initialization string) at start of
program to change baud rate each time it powers on and every so often to make
sure gps is at 4800?  The unit I have does 4800 but it is only ROM based and no
way to save settings.  If I hook to computer and change to 4800 and then plug
back into open tracker I am good to go, until I loose power.  I also thought
about programming a small PIC chip to send serial commands to change baud rate
after power on.
> I found the I2CTX and I will try that later this weekend when I recieve my
MX146.
> Thanks you have been a great help with support.
> --- In opentracker@yahoogroups.com, Scott Miller <scott@> wrote:
> >
> > The baud rate setting should be in hardware.c, and to compile in the
> > MX146 support you need to change the compile target to I2CTX.
> >
> > It's been a long time since I've tried 9600 baud, though, and I can't
> > promise it'll work.  It may not be buffering enough data to avoid
> > missing characters while it's processing stuff.
> >
> > Scott
> >
> > epic_audio wrote:
> > >
> > >
> > > I am trying to hook up a gps that only has 9600NMEA output, I am so
> > > confused with the source code, edit this, compile that. I was also
> > > wondering what I need to do(firmware/software) for MX146 transmitter
> > > support on the SMT.
> > > Thanks Jason
> > >
> > >
> >
>

Ok I found the 9600 setting but confused about the "#ifndef BAUD9600"  do i need
to add a BAUD=9600 at top of software?
I found the 9600baud.s19 file on your server and loaded that and it didn't work,
unit just blinked red(mabey 4hz)and sometimes after transmit it flashed fast
green then returned to the blinky red.  GPS had a 3D fix confirmed by flashing
green led and computer.
Is there a way to send a serial command(initialization string) at start of
program to change baud rate each time it powers on and every so often to make
sure gps is at 4800?  The unit I have does 4800 but it is only ROM based and no
way to save settings.  If I hook to computer and change to 4800 and then plug
back into open tracker I am good to go, until I loose power.  I also thought
about programming a small PIC chip to send serial commands to change baud rate
after power on.
I found the I2CTX and I will try that later this weekend when I recieve my
MX146.
Thanks you have been a great help with support.
--- In opentracker@yahoogroups.com, Scott Miller <scott@...> wrote:
>
> The baud rate setting should be in hardware.c, and to compile in the
> MX146 support you need to change the compile target to I2CTX.
>
> It's been a long time since I've tried 9600 baud, though, and I can't
> promise it'll work.  It may not be buffering enough data to avoid
> missing characters while it's processing stuff.
>
> Scott
>
> epic_audio wrote:
> >
> >
> > I am trying to hook up a gps that only has 9600NMEA output, I am so
> > confused with the source code, edit this, compile that. I was also
> > wondering what I need to do(firmware/software) for MX146 transmitter
> > support on the SMT.
> > Thanks Jason
> >
> >
>

Something like that.  It's not as precise as the DS18S20, anyway.

Scott

KC9GPS wrote:
> yes, It does respond.   Its currently inside my house so it varies a few
> degrees F, so every once in a while it moves 2 degrees C, But not very
> often.  I was just wondering if it was only accurate to +- 2 degrees C.
>
> Scott Miller wrote:
>>
>>
>> Does it respond at all? I usually hit them with component cooler spray
>> to make sure they're working.
>>
>> Scott
>>
>> daevans315 wrote:
>> >
>> >
>> > This is digging up a very old post but I'm noticing this behavior on
>> the
>> > current code on my OT1+. I'm only getting odd readings in degrees from
>> > the onboard temp sensor, even after removing my fairly large correction
>> > (-9). Is this 'normal'?
>> >
>> > http://aprs.fi/?c=raw&call=KC9GPS-2&limit=300
>> <http://aprs.fi/?c=raw&call=KC9GPS-2&limit=300>
>> > <http://aprs.fi/?c=raw&call=KC9GPS-2&limit=300
>> <http://aprs.fi/?c=raw&call=KC9GPS-2&limit=300>>
>> >
>> > --- In opentracker@yahoogroups.com
>> <mailto:opentracker%40yahoogroups.com>
>> > <mailto:opentracker%40yahoogroups.com>, <scott@...> wrote:
>> > >
>> > > Sorry, catching up on email...
>> > >
>> > > The first versions that reported temperature just multiplied the
>> > reading by
>> > > 2, so it was slightly off and depending on the offset would have been
>> > always
>> > > odd or always even.
>> > >
>> > > Scott
>> > >
>> > > -----Original Message-----
>> > > From: Tapio Sokura [mailto:oh2kku@...]
>> > > Sent: Wednesday, November 10, 2004 1:24 AM
>> > > To: opentracker@yahoogroups.com
>> <mailto:opentracker%40yahoogroups.com>
>> <mailto:opentracker%40yahoogroups.com>
>> > > Subject: Re: [opentracker] Temperature instability
>> > >
>> > >
>> > >
>> > > sv1iw wrote:
>> > > > does anybody else observes temperature instability of the onboard
>> > > > sensor since the last two updates?
>> > > > I can see up to 2 degrees diference between transmissions (1200
>> sec).
>> > >
>> > > At some point I noticed that the temperature was always an odd number,
>> > > like 25, 23, 21 deg C. I think this was with the firmwares published
>> > > late summer, I haven't checked the later versions.
>> > >
>> > > Tapio
>> > >
>> > >
>> > >
>> > >
>> > > Yahoo! Groups Links
>> > >
>> >
>> >
>>
>
>
> --
> <http://www.trillianstatus.com/profile.php?uuid=190>
> <http://www.trillianstatus.com/profile.php?uuid=190>

The baud rate setting should be in hardware.c, and to compile in the
MX146 support you need to change the compile target to I2CTX.

It's been a long time since I've tried 9600 baud, though, and I can't
promise it'll work.  It may not be buffering enough data to avoid
missing characters while it's processing stuff.

Scott

epic_audio wrote:
>
>
> I am trying to hook up a gps that only has 9600NMEA output, I am so
> confused with the source code, edit this, compile that. I was also
> wondering what I need to do(firmware/software) for MX146 transmitter
> support on the SMT.
> Thanks Jason
>
>

Hi there one and all...

I have a OT1+ with a Garmin GPS35-PC and a Yaesu FT-1802M setup. I
made my own cable and all seems to be working OK.

A few questions...

Should the Garmin GPS35-PC be setup to 4800 baud in NEMA or Garmin
output? The reason I ask is that if I set it to NEMA output I get a
flashing LED on the OT1+

I am getting mixed transmission times on the FT-1802M. What I mean by
this is that sometimes it will transmit a short packet, less than a
second. And at other times it will transmit for almost 6-10 seconds. I
do have the OT1+ set to send some status text every 2 transmissions.
Does this sound right?

Here is a copy of the packets that are being transmitted... (From
http://aprs.fi/?c=raw&call=VK2CRT-9&limit=50)

2009-11-19 03:51:34 UTC:
VK2CRT-9>APOTC1,TCPIP*,qAS,vk2hl:wÑdl<0x01>@p?©´kkïB»£¨<0x0b>|<0x09>BÇð?°<0x08>{\
à<0x08>Ij¬-3<0x12>Ç!
?V<0x0f> ä?<0x08>ä­??Px9<0x09>`ÓZá°Ü?<0x13><0x08>
?²Éµ¥h<0x01><0x10><0x08><0x01>Û<0x08>´n1?<0x03>ßBXÎmÿ<<0x01>%aexl<0x09>aÇ7|!3%Ç<\
0x08>%?<0x0e><0x1e><0x0c>
[Unsupported packet format]
  2009-11-19 03:54:04 UTC:
VK2CRT-9>APOTC1,VK2US-1,VK2RGL-1*,WIDE2-1,qAR,VK2ZEN-5: 0 s b 7# % a %
w Y` [Unsupported packet format]
  2009-11-19 03:54:05 UTC:
VK2CRT-9>APOTC1,VK2US-1,VK2AMW-1,VK1RGI-1,WIDE2*,qAR,VK1NPW-1:Ç<0x09>0<0x08><0x0\
b>s<0x01>?ç«<0x10><0x10><0x10>àb?<0x14>7#Ç%»a?¯%Ó<0x01>w??ÇY`<0x08>
[Unsupported packet format]
  2009-11-19 03:54:58 UTC:
VK2CRT-9>APOTC1,VK2US-1,VK2RGL-1*,WIDE2-1,qAR,VK2ZEN-5: Z ~ ( @ @ { _
.X .?4 ? k @ ) _ !n{ F ~` Q: ``< [Unsupported packet format]
  2009-11-19 03:56:14 UTC: VK2CRT-9>APOTC1,TCPIP*,qAS,vk2hl:>
  2009-11-19 03:59:02 UTC:
VK2CRT-9>APOTC1,VK2US-1,VK2RAG-1*,WIDE2-1,qAR,VK2ZEN-5: b ! B o? 1% @]
` [Unsupported packet format]
  2009-11-19 03:59:30 UTC:
VK2CRT-9>APOTC1,TCPIP*,qAS,vk2hl:%Ó<0x01><0x08><0x13>é&­¨?d³!#³<0x07>{ã
?xBN­<0x0b>??ù?ÏB<0x06>Vê?²É÷??ää@BBB<0x10><0x06>!<0x01>???'@ùB??v@<0x03>ßÇ?Ç><0\
x0c>¾
?]ÓÓ [Unsupported packet format]
  2009-11-19 03:59:49 UTC:
VK2CRT-9>APOTC1,VK2US-1,VK2RTZ-1*,WIDE2-1,qAR,VK2ZEN-5:>
  2009-11-19 03:59:52 UTC:
VK2CRT-9>APOTC1,VK2US-1,VK2RAG-1*,WIDE2-1,qAR,VK2ZEN-5:>NM Mitsubishi
Pajero - ARB38B - In the Burbs
  2009-11-19 04:01:44 UTC: VK2CRT-9>APOTC1,TCPIP*,qAS,vk2hl:>NM
Mitsubishi Pajero - ARB38B - In the Burbs
  2009-11-19 04:04:51 UTC: VK2CRT-9>APOTC1,TCPIP*,qAS,vk2hl:>

Any advise is always welcome.

Regards and 73 to all

Col
(aka VK2CRT)

Waiting on PCBs and cases both.  The PCBs should be here any time now,
and they'll be going right out for assembly.

Scott

Keith VE7GDH wrote:
>
>
> Joseph ZL2SCI wrote...
>
>  > Hey are the up graded tested opentrackers back in stock yet?
>  > mmmmmmmmm the px777 sounds a good one !
>
> Scott said a day or two back that he's still waiting for the cases.
> Hopefully not too much longer. I'm going to grab one too. I ordered
> some PX-777s too!
>
> 73 es cul - Keith VE7GDH
> --
> "I may be lost, but I know exactly where I am!"
>
>

Hi Keith
well i think that we are many to have ordered some of these Px,s
:-)))))))))))
73/s
gervais ve2ckn


--------------------------------------------------
From: "Keith VE7GDH" <ve7gdh@...>
Sent: Wednesday, November 18, 2009 5:02 PM
To: <opentracker@yahoogroups.com>
Subject: Re: [opentracker] PX-777 and OT2m?

> Joseph ZL2SCI wrote...
>
>> Hey are the up graded tested opentrackers back in stock yet?
>> mmmmmmmmm the px777 sounds a good one !
>
> Scott said a day or two back that he's still waiting for the cases.
> Hopefully not too much longer. I'm going to grab one too. I ordered
> some PX-777s too!
>
> 73 es cul - Keith VE7GDH
> --
> "I may be lost, but I know exactly where I am!"
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Joseph ZL2SCI wrote...

> Hey are the up graded tested opentrackers back in stock yet?
> mmmmmmmmm the px777 sounds a good one !

Scott said a day or two back that he's still waiting for the cases.
Hopefully not too much longer. I'm going to grab one too. I ordered
some PX-777s too!

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

 

Does it respond at all? I usually hit them with component cooler spray
to make sure they're working.

Scott

daevans315 wrote:
>
>
> This is digging up a very old post but I'm noticing this behavior on the
> current code on my OT1+. I'm only getting odd readings in degrees from
> the onboard temp sensor, even after removing my fairly large correction
> (-9). Is this 'normal'?
>
> http://aprs.fi/?c=raw&call=KC9GPS-2&limit=300
> <http://aprs.fi/?c=raw&call=KC9GPS-2&limit=300>
>
> --- In opentracker@yahoogroups.com
> <mailto:opentracker%40yahoogroups.com>, <scott@...> wrote:
> >
> > Sorry, catching up on email...
> >
> > The first versions that reported temperature just multiplied the
> reading by
> > 2, so it was slightly off and depending on the offset would have been
> always
> > odd or always even.
> >
> > Scott
> >
> > -----Original Message-----
> > From: Tapio Sokura [mailto:oh2kku@...]
> > Sent: Wednesday, November 10, 2004 1:24 AM
> > To: opentracker@yahoogroups.com <mailto:opentracker%40yahoogroups.com>
> > Subject: Re: [opentracker] Temperature instability
> >
> >
> >
> > sv1iw wrote:
> > > does anybody else observes temperature instability of the onboard
> > > sensor since the last two updates?
> > > I can see up to 2 degrees diference between transmissions (1200 sec).
> >
> > At some point I noticed that the temperature was always an odd number,
> > like 25, 23, 21 deg C. I think this was with the firmwares published
> > late summer, I haven't checked the later versions.
> >
> > Tapio
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
>
>

--

I am trying to hook up a gps that only has 9600NMEA output,  I am so confused
with the source code, edit this, compile that.  I was also wondering what I need
to do(firmware/software) for MX146 transmitter support on the SMT.
Thanks Jason