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

Re: [tracker2] Telemetry

Expand Messages
  • Scott Miller
    Not yet, there s not. If you have a suggestion on how you d like that to work, let me know. I m thinking maybe a special parameter for the BEACON command...
    Message 1 of 8 , Feb 4, 2011
    • 0 Attachment
      Not yet, there's not. If you have a suggestion on how you'd like that
      to work, let me know. I'm thinking maybe a special parameter for the
      BEACON command...

      Scott

      On 2/2/2011 11:00 PM, vk6mt wrote:
      > Is there a way to send a telemetry packet in isolation (in other words
      > separate from a standard location packet)? It seems that I can only sent
      > a telemetry packet immediately after a location packet. And when these
      > packets get digipeated down the line the latter gets clobbered and does
      > not make it to the iGate.
      >
      > Can I use scripting to solve this problem by send a telemetry only
      > packet and if so how?
      >
      > Mal
      >
      >
    • vk6mt
      I think the simplest way would be to introduce a TELEmetry command that operates just like the `BEAcon one. A line in the script that looks like:- Exec
      Message 2 of 8 , Feb 4, 2011
      • 0 Attachment
        I think the simplest way would be to introduce a' TELEmetry' command that operates just like the `BEAcon' one. A line in the script that looks like:- Exec "TELE", would then do the trick. It would then also be possible to request the Telemety from the OT2 remotely! Is this possible?

        Mal


        --- In tracker2@yahoogroups.com, Scott Miller <scott@...> wrote:
        >
        > Not yet, there's not. If you have a suggestion on how you'd like that
        > to work, let me know. I'm thinking maybe a special parameter for the
        > BEACON command...
        >
        > Scott
        >
        > On 2/2/2011 11:00 PM, vk6mt wrote:
        > > Is there a way to send a telemetry packet in isolation (in other words
        > > separate from a standard location packet)? It seems that I can only sent
        > > a telemetry packet immediately after a location packet. And when these
        > > packets get digipeated down the line the latter gets clobbered and does
        > > not make it to the iGate.
        > >
        > > Can I use scripting to solve this problem by send a telemetry only
        > > packet and if so how?
        > >
        > > Mal
        > >
        > >
        >
      • tkomljan
        I have to agree. I ve experienced the same issue resulting in perhaps 70% loss of TELEmetry packets. The beacon and telemetry packets cannot be sent
        Message 3 of 8 , Feb 5, 2011
        • 0 Attachment
          I have to agree. I've experienced the same issue resulting in perhaps 70% loss of TELEmetry packets. The beacon and telemetry packets cannot be sent sequentially without some random pause in between, or if I understand Mal, separate the two and let beacon and telemetry operate on independent timers.

          --- In tracker2@yahoogroups.com, "vk6mt" <vk6mt@...> wrote:
          >
          >
          >
          > I think the simplest way would be to introduce a' TELEmetry' command that operates just like the `BEAcon' one. A line in the script that looks like:- Exec "TELE", would then do the trick. It would then also be possible to request the Telemety from the OT2 remotely! Is this possible?
          >
          > Mal
        • vk6mt
          On thinking about it I realise that there is already a TELEMETRY command for switching it on and off so it would need to be called something else, BTELEM for
          Message 4 of 8 , Feb 6, 2011
          • 0 Attachment
            On thinking about it I realise that there is already a TELEMETRY command for switching it on and off so it would need to be called something else, BTELEM for Beacon Telemetry or something like that.

            I don't know how hard it would be, but if you had the ability to add an optional path to the command you could then request a telemetry packet and have that packet digied back to you via your selected path. Something like BTELEM <path>. Without the optional parameter it would default to the path set in the active profile. But just to have the ability in the scripting to send the telemetry by itself would be a great leap forward.

            It sounds so easy when you don't have to write the code!

            Just dreaming Scott, no pressure!!



            Mal



            --- In tracker2@yahoogroups.com, "tkomljan" <tkomljan@...> wrote:
            >
            > I have to agree. I've experienced the same issue resulting in perhaps 70% loss of TELEmetry packets. The beacon and telemetry packets cannot be sent sequentially without some random pause in between, or if I understand Mal, separate the two and let beacon and telemetry operate on independent timers.
            >
            > --- In tracker2@yahoogroups.com, "vk6mt" <vk6mt@> wrote:
            > >
            > >
            > >
            > > I think the simplest way would be to introduce a' TELEmetry' command that operates just like the `BEAcon' one. A line in the script that looks like:- Exec "TELE", would then do the trick. It would then also be possible to request the Telemety from the OT2 remotely! Is this possible?
            > >
            > > Mal
            >
          • Steve
            Hello everyone I m wondering how to send telemetry only, not with position. Does a command exist for the OT3m? Thanks Steve VE2BSB
            Message 5 of 8 , May 19 9:33 AM
            • 0 Attachment
              Hello everyone


              I'm wondering how to send telemetry only, not with position.
              Does a command exist for the OT3m?




              Thanks
              Steve
              VE2BSB
            Your message has been successfully submitted and would be delivered to recipients shortly.