Loading ...
Sorry, an error occurred while loading the content.

Re: [aprsisce] Re: Telemetry decode

Expand Messages
  • Lynn W. Deffenbaugh
    Fixed in the latest development version (2010/05/15 15:00). I was defaulting the bit-sense to 0xFF but defaulting the string to off . So when a bit was set,
    Message 1 of 5 , May 15, 2010
    • 0 Attachment
      Fixed in the latest development version (2010/05/15 15:00). I was
      defaulting the bit-sense to 0xFF but defaulting the string to "off". So
      when a bit was set, and the same bit was set in the sense, the string
      was "off". This was only an issue with telemetry coming from a station
      that had not yet sent a definition. I've changed the default bit-sense
      to 0x00 so a 1 will say "on" and a 0 will say "off".

      Thanks for noticing and reporting the discrepancy!

      Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

      gsdatplace wrote:
      > Sorry Lynn, James has been typing beside me for a bit here...
      > The package is going to fly as VE6ATV-11 on one callsign, there are 2 or 3 more calls that are going to be on that balloon, james is writting a post for the balloon sched as I type.
      > We don't require a fix right this sec, but its just a observation.
      > Here's a little snippit, it will be on and off as well during the day.
      > 2010-05-15 12:29:30 UTC: VE6ATV-11>APOTC1,qAS,VE6RKY-5:/122928h5246.39N/10815.34WO240/000/A=001794 23C 23C HDOP01.4 SATS08
      > 2010-05-15 12:29:30 UTC: VE6ATV-11>APOTC1,qAS,VE6RKY-5:T#003,151,155,255,255,151,00000010
      > 2010-05-15 12:29:41 UTC: VE6ATV-11>APOTC1,qAS,VE6RKY-5:/122938h5246.39N/10815.34WO233/000/A=001791 23C 23C HDOP01.3 SATS08
      > 2010-05-15 12:29:41 UTC: VE6ATV-11>APOTC1,qAS,VE6RKY-5:T#004,151,151,255,255,151,00000010
      > 2010-05-15 12:29:52 UTC: VE6ATV-11>APOTC1,qAS,VE6RKY-5:/122948h5246.39N/10815.33WO011/000/A=001781 23C 23C HDOP01.2 SATS09
      > 2010-05-15 12:29:52 UTC: VE6ATV-11>APOTC1,qAS,VE6RKY-5:T#005,151,151,255,255,151,00000010
      > 2010-05-15 12:30:03 UTC: VE6ATV-11>APOTC1,qAS,VE6RKY-5:/122959h5246.39N/10815.34WO007/000/A=001784 23C 23C HDOP01.4 SATS08
      > 2010-05-15 12:30:03 UTC: VE6ATV-11>APOTC1,qAS,VE6RKY-5:T#006,151,151,255,255,151,00000010
      > 2010-05-15 12:30:12 UTC: VE6ATV-11>APOTC1,qAS,VE6RKY-5:/123008h5246.39N/10815.34WO335/000/A=001781 23C 23C HDOP02.2 SATS08
      > 2010-05-15 12:30:12 UTC: VE6ATV-11>APOTC1,qAS,VE6RKY-5:T#007,151,154,255,255,151,00000010
      > Garrett
      > VE6RKY
      > --- In aprsisce@yahoogroups.com, "Lynn W. Deffenbaugh" <kj4erj@...> wrote:
      >> What callsign and what timestamp at aprs.fi's raw display is it? (Or
      >> just e-mail the raw packet) And have you sent out a telemetry
      >> definition that APRSISCE/32 could have heard. I'd like to check it out
      >> and get it fixed for you.
      >> Lynn (D) - KJ4ERJ
      >> James Ewen wrote:
      >>> Lynn,
      >>> We're preparing for Le Grand Saut, and just set our RTrak. Looking at
      >>> the telemetry strings, we noticed that the bits don't get displayed
      >>> properly. Out bit 7 is set, but APRSISCE/32 shows all bits at zero...
      >>> James
      >>> VE6SRV
    Your message has been successfully submitted and would be delivered to recipients shortly.