CC3220SF: TIDA-010007 Grid IoT reference design connecting circuit breakers and sensors to other equipment using WiFi

Exactly.

Thanks,
Massimo

Hello Jesu,

my interest born after reading this part of the description: "The design enables  the capability to setup a Wi-Fi network or connect to an external network, transfer data and optimize power. Data transfer scheme includes sending/receiving control, status, settings, firmware updates over the air between devices or to the cloud. Switching the device between always connected, intermittently connected, and hibernate mode optimizes power consumption for grid applications."

Another point I am interested too (that is not related to the application note) is about how connecting to different MQTT brokers with the same MQTT client as TI MQTT  implementation or IBM-Paho implementation. I mean that the same application may choose to connect to AWS or IBM-Watson or Microsoft Azure and so on.

Massimo

Hi Massimo,

Before I get into the SW specifics so you can test/run these features for yourself please make sure you have followed the getting started guide to get setup. 

To learn how to setup a WiFi network (AP mode) or connect to one (station mode) the "network_terminal" example in the SDK is a good place to start. This application has a CLI that allows you to use commands like wlan_ap_start to configure and start an network as well as wlanconnect to connect to an external network.

You can find a tutorial for the "network_terminal" on SimpleLink academy here. 

For over the air (OTA) we also have a "cloud_ota" example along with a SimpleLink academy tutorial here.

For power consumption our "power_measurement" example provides a CLI to configure the power mode you wish to use.

Regarding MQTT we have examples for all the mentioned cloud platforms here. You can only have one MQTT client at a time. 

These examples should allow you to setup and run most of these features with little effort.

I know this is a lot of information. If you have need more details or have any questions let me know.

Jesu

Hi Jesu,

I am already working with CC32xx MCUs and modules and I know the docs you pointed to me, thanks.

Any news?

Massimo

Hi Massimo,

I have sent them another email - hopefully they get back to me soon. Just in case they cannot release the example I should note I doubt the software example for this TI design is using additional features that I did not point out from examples earlier.

Jesu

Hi Massimo,

What type of end equipment are you considering our product for?

Jesu

OK, thanks.

Hi Jesu,

mainly I am working on 3 different devices. The first is  an update on a medical device based on CC3100/CC3200, it is a gateway between a sub-GHz sensor network and the cloud. The second is  the base for a common HW platform used in an application of ubiquitous computing that will be used in museums, archeologila sites and art-galleries and the third is an IIoT application client. The lsat 2 are based on CC3220 but may be ported to CC3235.

At the moment for the last 2 projects I am investigating the possibility to port some code from the first project (mainly a interface layer) but seems that SimpleLink releases are too different to justify the port, seems better just maintain only the SW interface and rewrite the source code function by fuinction where needed.

Massimo

Hi Massimo,

Thanks for sharing. It is true, vast changes have been made to our SDK going from gen 1 to gen 2. However we do have a software migration guide that goes over all the steps to update the SW for said medical device. Sharing if with you below in case you reconsider.

http://dev.ti.com/tirex/content/simplelink_cc32xx_sdk_1_40_00_03/docs/simplelink_mcu_sdk/SimpleLink_Gen1_to_Gen2_SDK_Migration_Guide.html

I received the software example from the TI design. It looks like they used the mqtt_client example as a base to build their example. 

I'm going to send you a request to send it privately.

Any further questions?

Jesu

Hi Jesu,

there are many differences, some also in the HW (and these can not be solved) but many seems to be just different define labels and others API changes. What I do not understand is why you did not update the examples, now there are different examples between Gen1 and Gen2 and they are not compatible. But if I uinderstand well the source code, seems to be possible to merge/modify some source code to correct errors or modify the behaviour in the parts I am more interested as the secure file system and certificate management.