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

RE: [tracker2] remote cmd

Expand Messages
  • scott@opentrac.org
    I ve got the ack thing fixed - it works fine now with no {. I actually did that a while ago, but haven t put the new firmware up yet. I ve tested a few
    Message 1 of 15 , Aug 27, 2006
    • 0 Attachment
      I've got the ack thing fixed - it works fine now with no {.  I actually did that a while ago, but haven't put the new firmware up yet.  I've tested a few commands from converse mode, and it seems to work.
       
      Scott


      From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of Mark Miller
      Sent: Saturday, August 26, 2006 2:16 PM
      To: tracker2@yahoogroups.com
      Subject: RE: [tracker2] remote cmd


      >There is mostly good news. Remote commands are working as long as I use
      >XASTIR (and I presume any other legitimate APRS node) and also use a
      >radio, antenna, and tnc that produces signals that the OT2 decoder reads
      >reliably. I think my problems were mostly associated with decode errors.

      I broke out my TNC220 with version 5 firmware and sent some messages
      manually. My TNC220 has a mycall of N5RFX, the OT2 has a mycall of
      N5RFX-6. Below is the TNC220 screen capture.

      :N5RFX-6 :cmd power{
      N5RFX-6>APOT2A, WIDE1-1:: N5RFX :ack

      N5RFX-6>APOT2A, WIDE1-1:: N5RFX :POWER ON{al
      N5RFX-6>APOT2A, WIDE1-1:: N5RFX :POWER ON{al
      :N5RFX-6 :ackal

      You have to have the curly bracket at the end of the command text,
      otherwise the response will be INVALID message.

      73,

      Mark N5RFX

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