• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 54 subscribers
  • Views 710 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.

CC1310: Getting started with Wireless M-Bus?

AnBer
Mastermind 30210 points
Part Number: CC1310
Other Parts Discussed in Thread: WMBUS, CC1350

Team,

Wireless M-bus does not seem to be included in the CC1310 Simplelink academy training 4.20 (here).
Is it plan to at least include a getting started example?

It could be useful to get a list of the different Simplielnk academy labs that could make sense to do before starting at all with the Wireless M-bus stack (here):
-What portion of the CC1310 simplink academy do you advise to look at before starting with Wireless M-Bus stack?
Is the Free RTOS relevant or only the TI RTOS?
Does project Zero matches the way the SW drivers lib are used in the Wireless M-Bus stack examples?
....
-Are there other additional and relevant Simplelink academy training if you start with CC1312 instead?

-As part of the TI Wireless M-bus stack itself:
is there a kind of getting started for people that newer used TI Simplelink IC and tools?

Thanks in advance!

A.

  • 0
    TI__Guru 58425 points

    Hi AnBer,

    There is unfortunately no "Getting started" material as of today, we are aware of this gap. The wmbus stack is developed by a third-party company (StackForce) and the project structure and feel does not really follow any TI SDK standard. This is also why the wmbus is not part of the SDK, it is currently a standalone install with dependencies on older CC1310 SDKs.

    There is not many examples available but there are some in the documentation shipped from StackForce together with information on how to use the serial interface. As it stands today, this documentation and E2E is the "best" there is in terms of resources.

  • 0 in reply to IUsedToBeARealPerson (M-W)
    TI__Mastermind 30210 points

    Hi Max,

    Thanks for the answer.

    I understand that the W-MBUS stack does not follow the traditional TI SDK standard. Looking at the W-MBUS release notes the dependencies are on SDK v.2_20_00_38 which still include a Simplelink academy training (2.20.03.05):
    https://dev.ti.com/tirex/explore/node?a=eCfARaV__2.20.00.38&node=AFUdF2MFjhZ-sEr1NZrjvw__eCfARaV__2.20.00.38
    https://dev.ti.com/tirex/explore/node?a=eCfARaV__2.20.00.38&node=ACWKlMgmt3t0rDA6.a7c8Q__eCfARaV__2.20.00.38

    -Wich one of those training modules would be suited to do if you plan to develop App SW with the WMBUS stack?
    -Is the TI RTOS portion and POSIX portion relevant?
    -Can the 15.4 portion help to understand how the TI RF works and help to relate to Wireless Mbus?
    -Can the TI drivers be used or is it being used in the Wireless Mbus stack?
    -Could you give a list of what Simpllelink academy module you think are relevant in the context of Wireless M-bus app devlopment?
    -which one of the module  or tools are not needed or show incompatibility with the W-Mbus stack?

    Thanks in advance!

    A.

  • 0 in reply to AnBer
    TI__Guru 58425 points

    Hi AnBer,

    I would say that from a development perspective, you could look at the TI-RTOS and drivers (as needed) basics, that is about it. Non of the RF stacks would really help you understand the wmbus solution. 

    In most cases the wmbus stack is operated as a network processor and no development is required (as images for this is supplied). If you would need to change pin-out, that would be possible but again, not a lot of development and in that case, the driver modules would be the best suited if you want to understand drivers and configuring them better.

    If wanting to do wmbus "embedded" then you go with the TI-RTOS trainings (as the stack trainings does not really help you much). Potentially also the sensor controller modules but you are running quite low on RAM and FLASH in this "mode" depending on the wmbus setup so you could be a bit limited in what type of application you could fit on the device alongside the wmbus stack. 

  • 0 in reply to IUsedToBeARealPerson (M-W)
    TI__Mastermind 30210 points

    Hi max,

    Thanks, it is helping me to understand where to start!

    About SmartRF studio 7.0 and W-MBUS:
    -Can smartRF studio be used as well used for W-MBUS?
    -For example can the RX sniffer be used?
    -Does the RadioTestLibrary support W-MBUS?

  • 0 in reply to AnBer
    TI__Mastermind 30210 points

    Hi Max,

    Another question:
    I looked at the "TI wireless M-Bus stack_2.0.0_manifest" from wmbus :

    it specifies the below:

    Does it means that the stack .lib files in wmbus-cc13xx-rtos-2.0.0\lib) are provided for evaluation only and the production license need to be sorted with Stackforce?
    Or are the stack (ie lib files) provided for production and for free?

    I assume as well that paid technical support is available from Stackforce. Correct?
    Or is the source code of the CC1310 application example available for free from Stackforce on request?

    Thanks !

    A.

  • 0 in reply to AnBer
    TI__Guru 58425 points

    Hi AnBer,

    The stack as delivered on TI.com includes the TI Commercial license and should be OK for production as far as I'm aware. There is no royalties for CC1310 and CC1350. 

    As for support, yes you should be able to get paid support from SF but hopefully we (apps) in TI could answer typical questions the user might have. As for the source code, this is not available for free.