Announcement

Collapse
No announcement yet.

HS3, xAP transmitting wrong ID? (Netiom boards)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • HS3, xAP transmitting wrong ID? (Netiom boards)

    Under HS2, all worked fine. When switching a device Off via HS web page, the xAP tx message looked like this.

    xap-header
    {
    v=13
    hop=1
    uid=FF.000E:0000
    class=xapBSC.Cmd
    source=mcs.Xap.tv
    target=phaedrus.netiom.Location2:Output.6
    }
    output.state.1
    {
    State=OFF
    ID=16
    }
    Checksum
    {
    Length=0180
    }


    under HS3, the same action generates this message sent from HS

    xap-header
    {
    v=13
    hop=1
    uid=FF.000D:0000
    class=xapBSC.Cmd
    source=mcs.XapHS3.tv
    target=phaedrus.netiom.Location2:Output.6
    }
    output.state.1
    {
    ID=3516
    state=On
    }


    The ID under HS2 is "16", but "3516" under HS3. Therefore the Netiom board ignores it. HS3 does react properly to received xAP messages-if I switch the device off in HS2, then the device switches off in HS3.

    How do I get mcsXAP to send ID=16 under HS3?
    Last edited by apluck; April 17th, 2014, 04:30 AM.

  • #2
    It has to do with schema v=12 vs. v=13. V .39 corrected this.

    Comment


    • #3
      Thanks Michael. I upgrade to .39 and all working fine.

      Comment

      Working...
      X