• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 259 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/LAUNCHXL-CC1310: Where can I find the latest/complete document for "IoT-Gateway and Collector Application Interface API"?

Adam Wu
Intellectual 740 points
Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: CC1310

Tool/software: Code Composer Studio

Dear Sir,

I discovered a related document as the hyper-link below.

http://www.ti.com/lit/ug/tiduci9c/tiduci9c.pdf?ts=1590386183657 

(The subject of the document is Sub-1 GHz Sensor-to-Cloud Industrial Internet-of-Things (IoT)

Gateway Reference Design)

By tracing the "ti154stack_linux_x64_4_10_00_06" SDK code, I found there is inconsistency in the packet format.

For example, an inconsistency happens on  the description regarding "APPSRV_DEVICE_DATA_RX_IND" command.

 In "3.1.2.9.2.1.2 Parameter List" Table 10, the fields srcAddr (uint32) and Rssi (sint32) are inconsistent.

By tracing the SDK file <SDK root>/example/gateway/appClient/appclient.js:

1) There is one byte called 'addrMode' preceding the srcAddr which is either short (2 bytes) or extend(8 bytes) depending on 'addrMode'.

2) Rssi is just one byte instead of sint32.

Furthermore, the document does NOT describe all of the commands, for example, APPSRV_RMV_DEVICE_REQ.

I need to know the packet detail (the SDK does NOT complete the code  either) in order to fire the command to the co-processor CC1310.

Do you have a latest and comprehensive document for addressing my question?

Thank you very much.

BR,

Adam

  • 0
    TI__Mastermind 25810 points

    Hey Adam,

    The latest documentation for the 15.4 linux sdk is located here in TIREX: http://dev.ti.com/tirex/explore/node?node=ABIZFjEYRCbdsticRjM4Jw__oGlG4RW__LATEST

    Adam Wu said:
    I need to know the packet detail

    What are you trying to accomplish? I.e. what command would you like to send to the co-processor?

  • 0 in reply to Ammar N
    Intellectual 740 points

    Dear Ammar,

    I am exercising the host side programming (as the host of the CC1310 co-processor) upon Ubuntu Linux.

    The "host_collector" process which comprises the collector and npi_server functions runs successfully on my Ubuntu.

    I know there is a socket server port 5000 against which I can read and write.

    Thus, I got APPSRV_DEVICE_DATA_RX_IND command by the blocking read, whenever the sensor sends temperature data.

    The document I mentioned is NOT up to date. I realized the correct format by tracing appclient.js.

    I also need to send APPSRV_RMV_DEVICE_REQ command (for removing a device) by write operation.

    Unfortunately, the sample client program "<SDK root>/example/gateway/appClient/appclient.js" does NOT address this,

    therefore I don't know the command packet detail.

    BR,

    Adam

  • 0 in reply to Adam Wu
    TI__Mastermind 25810 points

    Hey Adam,

    The .js files are in the application layer and can be modified to support the command to dissociate a device from the collector.

  • 0 in reply to Ammar N
    Intellectual 740 points

    Dear Ammar,

    Yes, I knew it. But I need to know the packet format regarding the "remove device" command.

    I still can't find the proper document for the detail.

    Thank you

    BR,

    Adam

  • 0 in reply to Adam Wu
    TI__Mastermind 25810 points

    Hey Adam,

    In this instance I would refer to the code. You'll see that the remove device command is only used in appsrv.c and not passed up to the webserver/appclient.js.

    You can add that functionality, but I would use one of the existing commands as an example (maybe sendToggle).

    Follow the remove device command logic in appsrv.c and you'll find what's needed to send a disassociate command. You can also look at the disassociateReq structure in api_mac.c to find what is required at the stack level to perform this operation.

    Unfortunately there isn't a document that details every function exposed. I hope I addressed your question in regards to the packet format.