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.

SimpliciTI 1.1.0 proposed features - New

Other Parts Discussed in Thread: SIMPLICITI, CC2500TI is in the process of defining SimpliciTI 1.10 and we we like to get your inputs. Please comment on the proposed features for SimpliciTI 1.1.0. Let us know which feature is the highest priority for you and how you would use it.
 
Security
–   Support AES on devices with hardware encryption
–   Support XTEA on devices without hardware encryption

 
NV storage of link tables
–   Allows link tables to be restored after power loss

 
Unlink
–   Allows unused links to be removed to free up RAM

 
Auto acknowledge
–   Network level acknowledge

 
CCE support
–   Support for TI’s CCE environment. Free version allows up to 16KB applications
 
Listen Before Talk
–   CCA mechanism for European markets
  •  I would like to see support for Security and TI CCE. 

    LPRF_Rocks

  • I would request TI's CCE environment;

    Reasons- I have rf2500 board, and no examples can be compiled under IAR; kinda defeats purpose of a demo.

    Regards

  • Have you given any thought to adding support for 6lowpan?

  • Kobus:

    Full CCE support is needed the most, the whole development process is crippled by the 4k IAR limit and need to change to an only partially supported programming environment for larger programs.  If I start development in IAR my learning curve is essentially wasted.  I presently program the '430 in 'C' with CCE and am very pleased with the results and set-up there.  I originally chose CCE because it allowed enough programming space (16k) to actually get something done.  I honestly cannot tell whether you are selling IAR programs or TI chips the way this is now set up because almost all documents refer to a programming environment in which I have to remove functions just to get it to run and no space for my app at all.  I've read just about all of the E2E Community comments and from my own experience and what I've seen on E2E I think you rather desperately need to do the following:

    Provide a shell for all those users who cannot fluently program either in IAR or CCE.  That shell should begin with something which really is simple and that would be a requester that asks:

    "What kind of project are you developing?"

             1.  Simple communication between two MSP430/CC2500 boards?

                      a.  repeat toggle on receive board that is applied to send board?  Simply attach switches, contacts, on/off style sensors to the port connectors already available on the board.

                      b.  send data through the same connectors?  Click for bytes, message size, etc.

              2. Hijack the temperature demo.  Just expand it as we add connectors, sensors, etc.  Each of these turns up next to the temp demo circle that identifies the temperature ED.  Temperature and battery are an excellent start but it should be easy to see switch closures and analog voltages right next to the circle.  The A-D in the ED should be usable to convert any analog voltages I apply to specified pins.  Those should show up next to the GUI sphere too.  I should just click on a requester and the pins I want to be analog detection are changed to just that.  Then run the project through to my PC where I can easily direct the closures to something real besides a screen someone would have to watch all the time.  This could also toggle directly off the receiving board. Just set it up so I can duplicate closures to ground or VCC on the receiving board which in the present configuration has the same number of port pins available as the send board does because they're identical boards.  That covers a huge number of applications.  Analog covers many more. 

              3.  Each input should have a selectable Tx trigger and analog requesters should let me set limits beyond which the trigger activates and causes the ED xmtr to send notice of that change.

      That's a sample, I think it conveys the basic philosophy.  The point to me is that you will sell a LOT more chips if you get rid of the need for raw programming for the largest number of very basic apps.

      Yes, there are many fully licensed IAR users out there but LPRF is new and you are essentially limiting the increase in LPRF usage by making the first step so large a lot of people are going to check it out and forget it knowing that even if they do start in IAR unless they can justify a large investment in IAR before doing much more than a temp. demo management is going to get pretty antsy.

       I know this is asking quite a bit but if you are going to call it Simpliciti you are actually going to have to make it simple and not just hope everyone knows all that you do about the subject and 'C' or assembly besides.  As it is I think the title is pretty lame because tucked behind the title are needs to pick up IAR or CCE programming and lots of stuff that just is not simple at all.  Then I have to add the dodges to IAR mem size limitations or hope someone comes out with the Simpliciti OS done in assembly so I can do more than sit and watch boards blink at each other and discover room temperature.  CCE at least, please. 

    I am also aware that you face limited resources and time but so do we and TI  is  the one hawking chips and they've got to commit to really supporting this product or many of us will simply find some other LPRF source that will do the same thing more easily.  That may be difficult now but other manufacturers are working this area.  By reducing your own effort in this you are increasing ours and each of us is under the same kinds of pressures you are to show performance and not just sit and read problems from other folks on E2E all day.  These are to say the least trying times and TI is laying off people.  That is when you have to go into mental overdrive, at least two gallons of Jolt Cola consumed each hour at the computer, and work, work, work until an eight year old could build a radio controlled or sensed science project from the requesters without even knowing programming details.  Just like PCs and MACs.  Then you will sell mucho more chips over time and gain many more loyal users.  Since LPRF is in its infancy this is the exact time you need to pull ahead and establish a rep as the best, easiest to use and most effective LPRF anywhere.  The temp demo is great but everything else has to be that easy to work with.  

    I am a VERY loyal '430 and TI parts user and I must say that studying the problems folks are having getting into LPRF is draining that loyalty severely because I too thought that the temp demo showed that LPRF could be something practical to use but now I'm not so sure.  It's a matter of time, hour after hour, and a crashed economy means every minute I spend must be efficiently used.  I don't think it is using the present approach to designing with Simpliciti.  If I could simply take two of those amazing little boards, dash through some setup requesters and get on to my demo maybe I could avoid the next round of pink slips!

    Is this a route other new LPRF users would like Simpliciti to take?  Can we hear some additional comments?

    Larry

     

  • I would be pleased if you could make better examples for the free version of IAR... to make mi ez430-rf2500 bidirectional I even had to add lines to the nwk_types.h because they just weren't there! exactly these two:

      IOCTL_ACT_RADIO_RXON,
      IOCTL_ACT_RADIO_RXIDLE,

    I had to search in the examples and in the forum (Thanks for those who reply, you help me a lot)

    Believe me, everything I've learned up until now took me one week! (And I have my limitations with this code) when it could be learned in two days! (though I really get bidirectional communication)

    If this is a complete wireless enviroment it should be easy to follow the examples, no the other way around.

    Other thing maybe a true interrupt, not the callback function. AND if not using FRECUENCY_AGILITY some kind of function that allows to "chose channels" for selecting and end device (I had to create my own code for that, since I can't use FRECUENCY_AGILITY due the free IAR).

    Discounts in IAR for stundents would be wonderfull...

    Thanks in advance.

  • Larry,

    Here is the final list of features that will go into SimpliciTI 1.1.0 due for release at the end of Q1.

    Security
    –   Support XTEA on all devices

    NV storage of link tables
    –   Allows link tables to be restored after power loss

    Unlink
    –   Allows unused links to be removed to free up RAM
     
    Auto acknowledge
    –   Network level acknowledge
     
    CCE support
    –   Support for TI’s CCE environment. Free version allows up to 16KB applications

    IAR  will soon have a Kickstart version that will also allow up to 16kB compilation

    We would like to get your feedback on the improvements that we have made once SimpliciTI 1.1.0 is released.

    Regards Kobus

     

     

  • Kobus:

    Thank you for asking for feedback on SimpliciTI 1.1.0.  Also, thank you for adding CCE (now becoming CCS?) support.

    The other upgrades look good too. {:})

    I'll let you know as soon as I've got something.

    Thanks again.

    Larry

  • The new version will probably be announced here on the forum, but keep an eye here: http://www.ti.com/simpliciti

    Should not be too long until the new version is ready.

    Kjetil

     

  • Hi

    thank you for the new release, its best timing for me as i have to start writing code for a new application now.

    i tried to download the release at http://www.ti.com/simpliciti but still get swrc099b.zip containing v1.06.

    is there a ftp site to download the new release ? or is the new release hidden in the site above ?

    regards Friedrich